[asterisk-users] Cisco 7965 SIP Firmware

[Razza]

I have 7965 and am trying to convert the firmware to SIP (SIP45.8-3-4SR1S).
Does anyone have a valid XMLDefault.cnf.xml they could share?
I have tried the version at
voip-info<info.org/wiki/view/Asterisk+phone+cisco+79x1+xml+configuration+files+for+SIP&view_comment_id=14768#Troubleshooting>for
the 7941/7961 but unfortunately /var/log/messages shows
in.tftp stops sending after XMLDefault.cnf.xml (see below), so i'm assuming
the 7965 doesn't like my XMLDefault.cnf.xml.

Mar 31 21:34:47 fsvr dhcpd: DHCPACK on 192.168.10.174 to 00:1f:6c:61:1f:72
via eth0
Mar 31 21:34:47 fsvr in.tftpd[3577]: RRQ from 192.168.10.174 filename
CTLSEP001F6C611F72.tlv
Mar 31 21:34:47 fsvr in.tftpd[3577]: sending NAK (1, File not found) to
192.168.10.174
Mar 31 21:34:47 fsvr in.tftpd[3578]: RRQ from 192.168.10.174 filename
SEP001F6C611F72.cnf.xml
Mar 31 21:34:47 fsvr in.tftpd[3578]: sending NAK (1, File not found) to
192.168.10.174
Mar 31 21:34:47 fsvr in.tftpd[3579]: RRQ from 192.168.10.174 filename
XMLDefault.cnf.xml

Thanks in advance.

[J. Oquendo]

Post by Razza
I have 7965 and am trying to convert the firmware to SIP
(SIP45.8-3-4SR1S). Does anyone have a valid XMLDefault.cnf.xml they
could share?
I have tried the version at voip-info
<info.org/wiki/view/Asterisk+phone+cisco+79x1+xml+configuration+files+for+SIP&view_comment_id=14768#Troubleshooting>
for the 7941/7961 but unfortunately /var/log/messages shows in.tftp
stops sending after XMLDefault.cnf.xml (see below), so i'm assuming the
7965 doesn't like my XMLDefault.cnf.xml.

YMMV Change to reflect your firmware (e.g. P003-07-4-xx)
.. Line 20 and 21 are one line...


<Default>
<callManagerGroup>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
<mgcpPorts>
<listen>2427</listen>
<keepAlive>2428</keepAlive>
</mgcpPorts>
</ports>
<processNodeName></processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
<loadInformation8 model="IP Phone 7940">P003-07-4-00</loadInformation8>
<loadInformation7 model="IP Phone 7960">P003-07-4-00</loadInformation7>
<loadInformation6 model="IP Phone 7970">term71.default</loadInformation6>
<authenticationURL></authenticationURL>
<directoryURL></directoryURL>
<idleURL></idleURL>
<informationURL></informationURL>
<messagesURL></messagesURL>
<servicesURL></servicesURL>
</Default>
--
====================================================
J. Oquendo

SGFA #579 (FW+VPN v4.1)
SGFE #574 (FW+VPN v4.1)

wget -qO - www.infiltrated.net/sig|perl

http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3AC173DB

[Razza]

Post by J. Oquendo
YMMV Change to reflect your firmware (e.g. P003-07-4-xx)

8<-------- SNIP -------->8

I removed the following lines:
<loadInformation8 model="IP Phone 7940">P003-07-4-00</loadInformation8>
<loadInformation7 model="IP Phone 7960">P003-07-4-00</loadInformation7>
And tried both of these:
<loadInformation6 model="IP Phone 7965">term65.default</loadInformation6>
and
<loadInformation6 model="IP Phone 7965">SIP45.8-3-4SR1S</loadInformation6>
But again I get no further than /var/log/messages showing in.tftp stops
sending after XMLDefault.cnf.xml

Any suggestions?

[Greg Oliver]

Post by J. Oquendo
YMMV Change to reflect your firmware (e.g. P003-07-4-xx)
8<-------- SNIP -------->8
<loadInformation8 model="IP Phone
7940">P003-07-4-00</loadInformation8>
<loadInformation7 model="IP Phone
7960">P003-07-4-00</loadInformation7>
<loadInformation6 model="IP Phone
7965">term65.default</loadInformation6>
and
<loadInformation6 model="IP Phone
7965">SIP45.8-3-4SR1S</loadInformation6>
But again I get no further than /var/log/messages showing in.tftp
stops sending after XMLDefault.cnf.xml
Any suggestions?

For a 7965, you might try loadinformation to be 335.. I have had to
match up CCM tk.prod values to match on newer phones in the past to be
what cisco uses in their internal database before I could get them to
work. Although, leaving those lines out completely will work as well
assuming they already have the SIP firmware loaded..

-Greg

[Razza]

Post by Greg Oliver
For a 7965, you might try loadinformation to be 335.. I have had to
match up CCM tk.prod values to match on newer phones in the past to be
what cisco uses in their internal database before I could get them to
work. Although, leaving those lines out completely will work as well
assuming they already have the SIP firmware loaded..

8<-------- SNIP -------->8

My modified base XMLDefault.cnf.xml is detailed below. But still I get no
further than /var/log/messages showing in.tftp stops sending after
XMLDefault.cnf.xml.

I have tried it with loadInformation as follows:
<loadInformation335 model="IP Phone 7965">SIP45.8-3-4SR1S
</loadInformation335>
<loadInformation335 model="IP Phone 7965">term65.default
</loadInformation335>
<loadInformation335>SIP45.8-3-4SR1S</loadInformation335>
<loadInformation335>term65.default</loadInformation335>

I also notice in the voip-info article (admittedly for 79x1 phones) the xml
stats and ends in <device> and </device> - is this correct?

<Default>
<callManagerGroup>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
<mgcpPorts>
<listen>2427</listen>
<keepAlive>2428</keepAlive>
</mgcpPorts>
</ports>
<processNodeName></processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
<loadInformation335 model="IP Phone 7965">SIP45.8-3-4SR1S
</loadInformation335>
<authenticationURL></authenticationURL>
<directoryURL></directoryURL>
<idleURL></idleURL>
<informationURL></informationURL>
<messagesURL></messagesURL>
<servicesURL></servicesURL>
</Default>

[Razza]

For interested parties....
It would appear I didn't need to had anything between the
<loadInformation></loadInformation> tags in XMLDefault.cnf.xml and/or
SEP{MAC Addr}.cnf.xml to force the upgrade, although the correct version of
firmware needs to be present between the tags once it is converted.

When I factory reset the phone (power-off the device, power-on the device,
hold down the # key for a few seconds, then type 1,2,3,4,5,6,7,8,9,*,0,#),
it looks for term65.default.loads, which in turn instructs the phone to load
the appropriate images/apps.