Doug Lytle wrote:
Keep in mind, you need to include both the
P003-07-3-00 and P0S3-07-3-00 in the SIPDefault.cnf and OS79XX.txt
You need the P003-07-3-00 in OS79XX.TXT as it contains the application
loader and P0S3-07-3-00 in the SIP(Default|MAC).cnf as it contains the
actual sip firmware.
Hi all,
Gene pointed out that the OS79XX.TXT and the SIP*.cnf files have to be
in Unix format without CR/LF. This got me to the point where the phone
requests and retrieves the OS79XX.TXT file, and downloads the firmware
specified from the tftpd server... only thing is, the phone never
I was spending about six hours on my Cisco phones to work out this
issue. You need to upgrade first to version 2 then you can go to six
and on.
On Thu, 10 Feb 2005 09:11:40 -0800, Max Clark [EMAIL PROTECTED] wrote:
Hi all,
Gene pointed out that the OS79XX.TXT and the SIP*.cnf files have to
Hi all,
So I have been reading through the docs available online and the
different threads on this list, but I cannot seem to get this phone to work.
I have configured the OS79XX.TXT and SIP/SEP*.cnf files (see attached),
when I configure the phone to point to my tftp server and reboot it I
You're probably going to want to go ahead and remove the SEPmac
address.cnf.xml file from the TFTP server and leave the SIPmac
address.cnf file in place.
I think with version 6 or 7 of the firmware (don't recall which one -
probably the one that starts using the Universal App Loader) the phone
BJ,
I tried removing the SEP* files and changing the OS79XX.TXT to the 7.3
version of the firmware and then got the message below in my tftpd server.
How do I check the version of the Firmware that the phone is running?
Based on what you said I have a feeling that I need to go way back in
What I don't understand is that the phone will request and download the
SIP/SEP*.cnf files which are well over 8.3, and if I change the file
name to an 8.3 format the phone doesn't even attempt to download the
firmware.
-Max
Max Clark
max [at] clarksys.com
http://www.clarksys.com
BJ
I'm not sure of your configuration but last time I looked there
wasn't a SIP v8.3. Unless that has changed I'd suggest getting
the correct version of SIP if that is what you'd like to test.
Max Clark wrote:
What I don't understand is that the phone will request and download
the SIP/SEP*.cnf
Steve,
No, not SIP version 8.3, but the SIP firmware in an 8.3 formatted file
name (i.e. DOS).
-Max
Max Clark
max [at] clarksys.com
http://www.clarksys.com
Steve Blair wrote:
I'm not sure of your configuration but last time I looked there
wasn't a SIP v8.3. Unless that has changed I'd
Steve Blair wrote:
I'm not sure of your configuration but last time I looked there
wasn't a SIP v8.3. Unless that has changed I'd suggest getting
the correct version of SIP if that is what you'd like to test.
He was talking about 8.3 filename formats not firmware versions.
Following a top
On Wed, 09 Feb 2005 12:20:01 -0800, Max Clark [EMAIL PROTECTED] wrote:
Which lead me to believe that there was an 8.3 naming issue when using a
windows based tftpd server. So I changed the file names of my image to
an 8.3 structure, updated the configuration files and rebooted. After I
do that
Shaun Ewing wrote:
You need to do an incremental upgrade - eg: SIP 2.3 - SIP 4.4 - SIP 7.3.
The ealier images can be obtained from Cisco if you have a valid CCO login.
Actually, you need to go from earlier version to version 5. This is the
version Cisco started using an encrypted firmware.
Dave Green wrote:
Following a top posted thread is a pain.
not trimming the useless part of a reply is another pain...
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE
13 matches
Mail list logo
