Brad Stockdale
2007-Mar-29 09:18 UTC
[asterisk-users] Re: Problem converting a Cisco 7960 to SIP
Hello all, I've got myself into a bizzare situation that I can't seem to get myself out of... Was wondering if anyone had some advice that might get me 'over the hill' on this... Some background: PBX consists of an Asterisk box (running TrixBox), 4 Cisco 7960's, 2 Polycom IP500's, and now an additional Cisco 7960. The phones are all on a separate LAN. There is no VLAN configuration. The Asterisk box also is running a TFTP server and DHCP server. The 4 original Cisco's work fine still. The Polycom IP500's work fine. The problem is with trying to get this new Cisco 7960 online... It came pre-loaded with the SCCP image and I cannot get it to convert to SIP. Currently it is running the following versions: App Load ID: P0030301MFG2 Boot Load ID: PC0303010200 Version: 3.1(MF.G2) The phone contacts the DHCP server and gets an IP successfully. The dhcpd.conf file: ############################################################################## # dhcpd.conf - dhcp config file for eth1 / sip phones ############################################################################## authoritative; ddns-update-style interim; ignore client-updates; local-address 192.168.1.1; option tftp-boot-server code 150 = ip-address; option tftp-boot-server 192.168.1.1; subnet 192.168.1.0 netmask 255.255.255.0 { option routers 192.168.1.1; option subnet-mask 255.255.255.0; option domain-name-servers 192.168.1.1; option time-offset -18000; # Eastern Standard Time option ntp-servers 192.168.1.1; option tftp-server-name "192.168.1.1"; default-lease-time 43200; max-lease-time 86400; pool { range 192.168.1.100 192.168.1.150; } } Then the phone contacts the TFTP server. Below are the logs: Mar 29 12:09:15 asterisk1.local atftpd[32276.-1208575056]: Serving OS79XX.TXT to 192.168.1.144:49427 Mar 29 12:09:16 asterisk1.local atftpd[32276.-1208575056]: Serving SEP001795B05B1D.cnf.xml to 192.168.1.144:49428 Mar 29 12:09:16 asterisk1.local atftpd[32276.-1208575056]: Serving XMLDefault.cnf.xml to 192.168.1.144:49429 Mar 29 12:09:16 asterisk1.local atftpd[32276.-1208575056]: Serving SEP001795B05B1D.cnf to 192.168.1.144:49430 OS79XX.TXT contains: P003-08-6-00 Originally the SEP001795B05B1D.cnf file didn't exist. Since it was for CallManager, I didn't bother to configure it and just setup the SIPmac.cnf file instead. The phone never requested the SIPmac.cnf file... I found a trick via google that uses the SEPmac.cnf file to change firmware. The SEP file now contains: <Default> <callManagerGroup> <members> <member priority="0"> <callManager> <ports> <ethernetPhonePort>2000</ethernetPhonePort> </ports> <processNodeName>192.168.1.1</processNodeName> </callManager> </member> </members> </callManagerGroup> <loadInformation6 model="IP Phone 7910"></loadInformation6> <loadInformation124 model="Addon 7914"></loadInformation124> <loadInformation9 model="IP Phone 7935"></loadInformation9> <loadInformation8 model="IP Phone 7940"></loadInformation8> <loadInformation7 model="IP Phone 7960">P003-08-6-00</loadInformation7> <loadInformation20000 model="IP Phone 7905"></loadInformation20000> <loadInformation30008 model="IP Phone 7902"></loadInformation30008> <loadInformation30007 model="IP Phone 7912"></loadInformation30007> </Default> The TFTP directory contains: 0004f20049bc-app.log 0004f20049bc-boot.log SEP001795B05B1D.cnf polycom_brad.cfg sip.cfg WORKING_POLYCOM_sip.cfg WORKING_POLYCOM.cfg phone1.cfg 0004f20049bc.cfg 0004f20049bc-phone.cfg 0004f20049bc-appFlash.log SoundPointIPLocalization 000000000000.cfg 000000000000-directory~.xml SoundPointIPWelcome.wav sip.ld sip.ver bootrom.ld SIP001795B05B1D.cnf snom.cnf SIP0012DABF2AAA.cnf SIP0012D9B94C72.cnf SIP001280B9D6E1.cnf SIP001280F3AFC7.cnf SIPDefault.cnf DSM2ColorLogo_3.bmp OS79XX.TXT P003-08-6-00.bin P003-08-6-00.sbn P0S3-08-6-00.loads P0S3-08-6-00.sb2 797x_template.cnf.xml cisco_util Desktops dialplan.xml merlin2.pcm RINGLIST.DAT syncinfo.xml All other phones work fine. Therefore, I assume all the firmware is in the right place... They all converted to SIP firmware fine... When I try to do the **# unlocking, it does nothing... Everything still shows locked. The phone doesn't have an Unlock Settings function (assuming firmware is too old) The phone, when it boots, goes through an endless loop consisting of: Configuring VLAN Configuring IP Then it starts over. What in the heck am I doing wrong? I thought that the OS79XX.TXT file should have taken care of pushing out the new image. And the phone is grabbing the file via TFTP, but it's like it ignores the idea of changing firmware. Also, when I try to do a factory reset (holding down #, power cycling) it never asks for the reset key sequence and never said it detected the key sequence. Any advice would be appreciated. Thanks, Brad -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
David Boyd
2007-Mar-29 10:27 UTC
[asterisk-users] Re: Problem converting a Cisco 7960 to SIP
On Thu, 2007-03-29 at 12:16 -0400, Brad Stockdale wrote:> Hello all, > > I've got myself into a bizzare situation that I can't seem to get myself > out of... Was wondering if anyone had some advice that might get me 'over the > hill' on this... > > Some background: PBX consists of an Asterisk box (running TrixBox), 4 Cisco > 7960's, 2 Polycom IP500's, and now an additional Cisco 7960. The phones are > all on a separate LAN. There is no VLAN configuration. The Asterisk box also > is running a TFTP server and DHCP server. The 4 original Cisco's work fine > still. The Polycom IP500's work fine. > > The problem is with trying to get this new Cisco 7960 online... It came > pre-loaded with the SCCP image and I cannot get it to convert to SIP. > Currently it is running the following versions: > > App Load ID: P0030301MFG2 > Boot Load ID: PC0303010200 > Version: 3.1(MF.G2) > > The phone contacts the DHCP server and gets an IP successfully. The > dhcpd.conf file: > > ############################################################################## > # dhcpd.conf - dhcp config file for eth1 / sip phones > ############################################################################## > > authoritative; > ddns-update-style interim; > ignore client-updates; > local-address 192.168.1.1; > > option tftp-boot-server code 150 = ip-address; > option tftp-boot-server 192.168.1.1; > > subnet 192.168.1.0 netmask 255.255.255.0 { > option routers 192.168.1.1; > option subnet-mask 255.255.255.0; > option domain-name-servers 192.168.1.1; > option time-offset -18000; # Eastern Standard Time > option ntp-servers 192.168.1.1; > option tftp-server-name "192.168.1.1"; > default-lease-time 43200; > max-lease-time 86400; > > pool { > range 192.168.1.100 192.168.1.150; > } > > } > > > > > Then the phone contacts the TFTP server. Below are the logs: > > Mar 29 12:09:15 asterisk1.local atftpd[32276.-1208575056]: Serving OS79XX.TXT > to 192.168.1.144:49427 > Mar 29 12:09:16 asterisk1.local atftpd[32276.-1208575056]: Serving > SEP001795B05B1D.cnf.xml to 192.168.1.144:49428 > Mar 29 12:09:16 asterisk1.local atftpd[32276.-1208575056]: Serving > XMLDefault.cnf.xml to 192.168.1.144:49429 > Mar 29 12:09:16 asterisk1.local atftpd[32276.-1208575056]: Serving > SEP001795B05B1D.cnf to 192.168.1.144:49430 > > OS79XX.TXT contains: > > P003-08-6-00 > > Originally the SEP001795B05B1D.cnf file didn't exist. Since it was for > CallManager, I didn't bother to configure it and just setup the SIPmac.cnf > file instead. The phone never requested the SIPmac.cnf file... > > I found a trick via google that uses the SEPmac.cnf file to change > firmware. The SEP file now contains: > > <Default> > <callManagerGroup> > <members> > <member priority="0"> > <callManager> > <ports> > <ethernetPhonePort>2000</ethernetPhonePort> > </ports> > <processNodeName>192.168.1.1</processNodeName> > </callManager> > </member> > </members> > </callManagerGroup> > > <loadInformation6 model="IP Phone 7910"></loadInformation6> > <loadInformation124 model="Addon 7914"></loadInformation124> > <loadInformation9 model="IP Phone 7935"></loadInformation9> > <loadInformation8 model="IP Phone 7940"></loadInformation8> > <loadInformation7 model="IP Phone 7960">P003-08-6-00</loadInformation7> > <loadInformation20000 model="IP Phone 7905"></loadInformation20000> > <loadInformation30008 model="IP Phone 7902"></loadInformation30008> > <loadInformation30007 model="IP Phone 7912"></loadInformation30007> > </Default> > > The TFTP directory contains: > > 0004f20049bc-app.log > 0004f20049bc-boot.log > SEP001795B05B1D.cnf > polycom_brad.cfg > sip.cfg > WORKING_POLYCOM_sip.cfg > WORKING_POLYCOM.cfg > phone1.cfg > 0004f20049bc.cfg > 0004f20049bc-phone.cfg > 0004f20049bc-appFlash.log > SoundPointIPLocalization > 000000000000.cfg > 000000000000-directory~.xml > SoundPointIPWelcome.wav > sip.ld > sip.ver > bootrom.ld > SIP001795B05B1D.cnf > snom.cnf > SIP0012DABF2AAA.cnf > SIP0012D9B94C72.cnf > SIP001280B9D6E1.cnf > SIP001280F3AFC7.cnf > SIPDefault.cnf > DSM2ColorLogo_3.bmp > OS79XX.TXT > P003-08-6-00.bin > P003-08-6-00.sbn > P0S3-08-6-00.loads > P0S3-08-6-00.sb2 > 797x_template.cnf.xml > cisco_util > Desktops > dialplan.xml > merlin2.pcm > RINGLIST.DAT > syncinfo.xml > > All other phones work fine. Therefore, I assume all the firmware is in the > right place... They all converted to SIP firmware fine... > > When I try to do the **# unlocking, it does nothing... Everything still > shows locked. The phone doesn't have an Unlock Settings function (assuming > firmware is too old) > > The phone, when it boots, goes through an endless loop consisting of: > > Configuring VLAN > Configuring IP > > Then it starts over. > > What in the heck am I doing wrong? I thought that the OS79XX.TXT file > should have taken care of pushing out the new image. And the phone is > grabbing the file via TFTP, but it's like it ignores the idea of changing > firmware. > > Also, when I try to do a factory reset (holding down #, power cycling) it > never asks for the reset key sequence and never said it detected the key > sequence. > > Any advice would be appreciated. > > Thanks, > Brad >Apologies in advance if this is a stupid comment, but don't you have to convert to SIP at a much lower version than 8. I had to go all the way back to version 3.? if I remember correctly to convert from SCCP to SIP. dave
Ron Wellsted
2007-Mar-29 11:29 UTC
[asterisk-users] Re: Problem converting a Cisco 7960 to SIP
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brad Stockdale wrote:> Hello all, > > I've got myself into a bizzare situation that I can't seem to get myself > out of... Was wondering if anyone had some advice that might get me 'over the > hill' on this... > > Some background: PBX consists of an Asterisk box (running TrixBox), 4 Cisco > 7960's, 2 Polycom IP500's, and now an additional Cisco 7960. The phones are > all on a separate LAN. There is no VLAN configuration. The Asterisk box also > is running a TFTP server and DHCP server. The 4 original Cisco's work fine > still. The Polycom IP500's work fine. > > The problem is with trying to get this new Cisco 7960 online... It came > pre-loaded with the SCCP image and I cannot get it to convert to SIP. > Currently it is running the following versions: > > App Load ID: P0030301MFG2 > Boot Load ID: PC0303010200 > Version: 3.1(MF.G2) > > The phone contacts the DHCP server and gets an IP successfully. The > dhcpd.conf file:To convert a version that old will require you going through at least 3-4 downloads: First convert to SIP 3.3, then to SIP 5.2 then probably to SIP 7.x before finally to SIP 8.6. You may have to convert to a SIP 6.x image in between. After the first conversion, you should be able to set the password etc via the SIPDefault.cfg file. HTH - -- Ron Wellsted ron@wellsted.org.uk http://www.wellsted.org.uk N 52.567623, W 2.137621 Linux Counter No. 202120 FWD:519961 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRgwFdEtP/KMNOfRbAQIewgf/cJjP9/wvbFp7ibkWgrvKTjY4k4vdhVF2 B5w5INJNjmxSaaC8JsCviglz7+HjFnKoEYd+eIOBYdmzoxGGPNEZLHGqXXd1vqHv EpdxstUZITOdv/gH5TRRzrlzbGWWtyGG8iHC7DftMeBGLyiO1W5/LZDdnpSylD3P NslzlNRQNSPPHjGClBTL3Y1Bsu2MEonICnGoVSyt9g8kHTLpkgeMLJiWWyoKNUcn Uz7Ub1chg8EkV7MgN2veAUKTcLCDIE7kluGC5To22SbcUxwTRnl+IKuE7CgZ+dJN l6zGYyBVdO+hndagOTeBotk2z0xt5D664Fq7NxjkVjUHJTip+nkd9g==/R9w -----END PGP SIGNATURE-----
Lacy Moore - Aspendora
2007-Mar-29 11:57 UTC
[asterisk-users] Re: Problem converting a Cisco 7960 to SIP
On 3/29/07, Brad Stockdale <brad_lists@greenepa.net> wrote:> Hello all, > > > <loadInformation7 model="IP Phone 7960">P003-08-6-00</loadInformation7>Should be POS03-08-6-00. The same as your .loads file. Also change this in the OS79XX file.> P003-08-6-00.bin > P003-08-6-00.sbn > P0S3-08-6-00.loads > P0S3-08-6-00.sb2