Retrieve inital configuration for Cisco phone 7942 from Asterisk TFTP server

We have problem for those Cisco phone 7942 to retrieve the configuration from the Centos TFTP server which Asterisk is running on it. Do you have any idea how to debug and fix the problem ?

Thanks
AXISHKAsked:
Who is Participating?
 
Ernie BeekConnect With a Mentor ExpertCommented:
Ok,

Any firewall running on the server which might block it?
Anything showing in the tftp log?
0
 
Ernie BeekExpertCommented:
You are using DHCP option 150 to define the tftp server?
0
 
AXISHKAuthor Commented:
Yes.
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
AXISHKAuthor Commented:
How to see the log in Centos TFTP ?

Tks
0
 
AXISHKAuthor Commented:
What firewall setting do I need to check in Centos , Tks
0
 
Ernie BeekExpertCommented:
For logging try:
cd /var/log
grep tftp messages


For iptables, just stop it and see if you get through first: /etc/init.d/iptables stop
0
 
AXISHKAuthor Commented:
Seem like it is not related to filewall, the centos could download  a configuration file to Cisco phone, but not sure why it keep asking tftp for the file.

My Cisco phone is 7942. Any idea ?

Mar 15 21:26:17 ippbx in.tftpd[15666]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:26:17 ippbx in.tftpd[15667]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
Mar 15 21:26:41 ippbx in.tftpd[15670]: RRQ from 192.168.1.190 filename CTLSEP108CCF75C9A8.tlv
Mar 15 21:26:41 ippbx in.tftpd[15670]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:26:41 ippbx in.tftpd[15671]: RRQ from 192.168.1.190 filename ITLSEP108CCF75C9A8.tlv
Mar 15 21:26:41 ippbx in.tftpd[15671]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:26:41 ippbx in.tftpd[15672]: RRQ from 192.168.1.190 filename ITLFile.tlv
Mar 15 21:26:41 ippbx in.tftpd[15672]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:26:41 ippbx in.tftpd[15673]: RRQ from 192.168.1.190 filename SEP108CCF75C9A8.cnf.xml
Mar 15 21:26:48 ippbx in.tftpd[15674]: RRQ from 192.168.1.193 filename CTLSEP108CCF74A9C8.tlv
Mar 15 21:26:48 ippbx in.tftpd[15674]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:26:48 ippbx in.tftpd[15675]: RRQ from 192.168.1.193 filename ITLSEP108CCF74A9C8.tlv
Mar 15 21:26:48 ippbx in.tftpd[15675]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:26:48 ippbx in.tftpd[15676]: RRQ from 192.168.1.193 filename ITLFile.tlv
Mar 15 21:26:48 ippbx in.tftpd[15676]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:26:48 ippbx in.tftpd[15677]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
Mar 15 21:27:12 ippbx in.tftpd[15678]: RRQ from 192.168.1.190 filename CTLSEP108CCF75C9A8.tlv
Mar 15 21:27:12 ippbx in.tftpd[15678]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:27:13 ippbx in.tftpd[15679]: RRQ from 192.168.1.190 filename ITLSEP108CCF75C9A8.tlv
Mar 15 21:27:13 ippbx in.tftpd[15679]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:27:13 ippbx in.tftpd[15680]: RRQ from 192.168.1.190 filename ITLFile.tlv
Mar 15 21:27:13 ippbx in.tftpd[15680]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:27:13 ippbx in.tftpd[15681]: RRQ from 192.168.1.190 filename SEP108CCF75C9A8.cnf.xml
Mar 15 21:27:19 ippbx in.tftpd[15682]: RRQ from 192.168.1.193 filename CTLSEP108CCF74A9C8.tlv
Mar 15 21:27:19 ippbx in.tftpd[15682]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:27:19 ippbx in.tftpd[15683]: RRQ from 192.168.1.193 filename ITLSEP108CCF74A9C8.tlv
Mar 15 21:27:19 ippbx in.tftpd[15683]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:27:19 ippbx in.tftpd[15684]: RRQ from 192.168.1.193 filename ITLFile.tlv
Mar 15 21:27:19 ippbx in.tftpd[15684]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:27:19 ippbx in.tftpd[15685]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
Mar 15 21:27:44 ippbx in.tftpd[15688]: RRQ from 192.168.1.190 filename CTLSEP108CCF75C9A8.tlv
Mar 15 21:27:44 ippbx in.tftpd[15688]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:27:44 ippbx in.tftpd[15689]: RRQ from 192.168.1.190 filename ITLSEP108CCF75C9A8.tlv
Mar 15 21:27:44 ippbx in.tftpd[15689]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:27:44 ippbx in.tftpd[15690]: RRQ from 192.168.1.190 filename ITLFile.tlv
Mar 15 21:27:44 ippbx in.tftpd[15690]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:27:44 ippbx in.tftpd[15691]: RRQ from 192.168.1.190 filename SEP108CCF75C9A8.cnf.xml
Mar 15 21:27:50 ippbx in.tftpd[15692]: RRQ from 192.168.1.193 filename CTLSEP108CCF74A9C8.tlv
Mar 15 21:27:50 ippbx in.tftpd[15692]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:27:50 ippbx in.tftpd[15693]: RRQ from 192.168.1.193 filename ITLSEP108CCF74A9C8.tlv
Mar 15 21:27:50 ippbx in.tftpd[15693]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:27:50 ippbx in.tftpd[15694]: RRQ from 192.168.1.193 filename ITLFile.tlv
Mar 15 21:27:50 ippbx in.tftpd[15694]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:27:50 ippbx in.tftpd[15695]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
Mar 15 21:28:15 ippbx in.tftpd[15698]: RRQ from 192.168.1.190 filename CTLSEP108CCF75C9A8.tlv
Mar 15 21:28:15 ippbx in.tftpd[15698]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:28:15 ippbx in.tftpd[15699]: RRQ from 192.168.1.190 filename ITLSEP108CCF75C9A8.tlv
Mar 15 21:28:15 ippbx in.tftpd[15699]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:28:15 ippbx in.tftpd[15700]: RRQ from 192.168.1.190 filename ITLFile.tlv
Mar 15 21:28:15 ippbx in.tftpd[15700]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:28:16 ippbx in.tftpd[15701]: RRQ from 192.168.1.190 filename SEP108CCF75C9A8.cnf.xml
Mar 15 21:28:21 ippbx in.tftpd[15702]: RRQ from 192.168.1.193 filename CTLSEP108CCF74A9C8.tlv
Mar 15 21:28:21 ippbx in.tftpd[15702]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:28:21 ippbx in.tftpd[15703]: RRQ from 192.168.1.193 filename ITLSEP108CCF74A9C8.tlv
Mar 15 21:28:21 ippbx in.tftpd[15703]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:28:21 ippbx in.tftpd[15704]: RRQ from 192.168.1.193 filename ITLFile.tlv
Mar 15 21:28:21 ippbx in.tftpd[15704]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:28:21 ippbx in.tftpd[15705]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
Mar 15 21:28:47 ippbx in.tftpd[15706]: RRQ from 192.168.1.190 filename CTLSEP108CCF75C9A8.tlv
Mar 15 21:28:47 ippbx in.tftpd[15706]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:28:47 ippbx in.tftpd[15707]: RRQ from 192.168.1.190 filename ITLSEP108CCF75C9A8.tlv
Mar 15 21:28:47 ippbx in.tftpd[15707]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:28:47 ippbx in.tftpd[15708]: RRQ from 192.168.1.190 filename ITLFile.tlv
Mar 15 21:28:47 ippbx in.tftpd[15708]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:28:47 ippbx in.tftpd[15709]: RRQ from 192.168.1.190 filename SEP108CCF75C9A8.cnf.xml
Mar 15 21:28:52 ippbx in.tftpd[15717]: RRQ from 192.168.1.193 filename CTLSEP108CCF74A9C8.tlv
Mar 15 21:28:52 ippbx in.tftpd[15717]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:28:52 ippbx in.tftpd[15718]: RRQ from 192.168.1.193 filename ITLSEP108CCF74A9C8.tlv
Mar 15 21:28:52 ippbx in.tftpd[15718]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:28:52 ippbx in.tftpd[15719]: RRQ from 192.168.1.193 filename ITLFile.tlv
Mar 15 21:28:52 ippbx in.tftpd[15719]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:28:52 ippbx in.tftpd[15720]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
Mar 15 21:29:18 ippbx in.tftpd[15721]: RRQ from 192.168.1.190 filename CTLSEP108CCF75C9A8.tlv
Mar 15 21:29:18 ippbx in.tftpd[15721]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:29:18 ippbx in.tftpd[15722]: RRQ from 192.168.1.190 filename ITLSEP108CCF75C9A8.tlv
Mar 15 21:29:18 ippbx in.tftpd[15722]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:29:18 ippbx in.tftpd[15723]: RRQ from 192.168.1.190 filename ITLFile.tlv
Mar 15 21:29:18 ippbx in.tftpd[15723]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:29:19 ippbx in.tftpd[15724]: RRQ from 192.168.1.190 filename SEP108CCF75C9A8.cnf.xml
Mar 15 21:29:23 ippbx in.tftpd[15725]: RRQ from 192.168.1.193 filename CTLSEP108CCF74A9C8.tlv
Mar 15 21:29:23 ippbx in.tftpd[15725]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:29:23 ippbx in.tftpd[15726]: RRQ from 192.168.1.193 filename ITLSEP108CCF74A9C8.tlv
Mar 15 21:29:23 ippbx in.tftpd[15726]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:29:23 ippbx in.tftpd[15727]: RRQ from 192.168.1.193 filename ITLFile.tlv
Mar 15 21:29:23 ippbx in.tftpd[15727]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:29:23 ippbx in.tftpd[15728]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
Mar 15 21:29:50 ippbx in.tftpd[15732]: RRQ from 192.168.1.190 filename CTLSEP108CCF75C9A8.tlv
Mar 15 21:29:50 ippbx in.tftpd[15732]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:29:50 ippbx in.tftpd[15733]: RRQ from 192.168.1.190 filename ITLSEP108CCF75C9A8.tlv
Mar 15 21:29:50 ippbx in.tftpd[15733]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:29:50 ippbx in.tftpd[15734]: RRQ from 192.168.1.190 filename ITLFile.tlv
Mar 15 21:29:50 ippbx in.tftpd[15734]: sending NAK (1, File not found) to 192.168.1.190
Mar 15 21:29:50 ippbx in.tftpd[15735]: RRQ from 192.168.1.190 filename SEP108CCF75C9A8.cnf.xml
Mar 15 21:29:54 ippbx in.tftpd[15736]: RRQ from 192.168.1.193 filename CTLSEP108CCF74A9C8.tlv
Mar 15 21:29:54 ippbx in.tftpd[15736]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:29:54 ippbx in.tftpd[15737]: RRQ from 192.168.1.193 filename ITLSEP108CCF74A9C8.tlv
Mar 15 21:29:54 ippbx in.tftpd[15737]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:29:54 ippbx in.tftpd[15738]: RRQ from 192.168.1.193 filename ITLFile.tlv
Mar 15 21:29:54 ippbx in.tftpd[15738]: sending NAK (1, File not found) to 192.168.1.193
Mar 15 21:29:55 ippbx in.tftpd[15739]: RRQ from 192.168.1.193 filename SEP108CCF74A9C8.cnf.xml
0
 
Ernie BeekExpertCommented:
Well that could mean there is something wrong with the config file......
0
 
AXISHKAuthor Commented:
Any idea what configuration file , image should be placed on the tftp ? Any templates that I could download for testing ?

Thanks
0
 
Ernie BeekExpertCommented:
0
 
AXISHKAuthor Commented:
Already watched that but doesn't help.
It come out with "Error Verifying Config Info". Believe there is something wrong on the configuration file.

Is there any workable template for Cisco 7942 that I could start with ?

Thanks
0
 
Ernie BeekExpertCommented:
Give this a try:

 
<device>  
<Default>   
<callManagerGroup>   
<members>   
<member priority="0">   
<callManager>   
<ports>   
<ethernetPhonePort>2000</ethernetPhonePort>   
<sipPort>5060</sipPort>  
<securedSipPort>5061</securedSipPort>  
</ports>   
<processNodeName>!!!!! SIP SERVER !!!!!</processNodeName>   
</callManager>   
</member>   
</members>   
</callManagerGroup>  
<loadInformation434 model="Cisco 7942"></loadInformation434>  
</Default>   
<deviceProtocol>SIP</deviceProtocol>  
<sshUserId>admin</sshUserId>  
<sshPassword>admin</sshPassword>  
<devicePool>  
<dateTimeSetting>  
<dateTemplate>D/M/Y</dateTemplate> ; by adding a after the Y shows time in 12 hour mode i.e. D/M/Ya  
<timeZone>!!!!! TIME ZONE !!!!!</timeZone>  
<ntps>   
<ntp>   
<name>!!!!! NTP SERVER !!!!!</name>   
<ntpMode>Unicast</ntpMode>   
</ntp>   
</ntps>   
</dateTimeSetting>  
<callManagerGroup>  
<members>  
<member priority="0">  
<callManager>  
<ports>  
<ethernetPhonePort>2000</ethernetPhonePort>  
<sipPort>5060</sipPort>  
<securedSipPort>5061</securedSipPort>  
</ports>  
<processNodeName>!!!!! SIP SERVER !!!!!</processNodeName>  
</callManager>  
</member>  
</members>  
</callManagerGroup>  
</devicePool>  
<sipProfile>  
<sipProxies>  
<backupProxy></backupProxy>   
<backupProxyPort></backupProxyPort>   
<emergencyProxy></emergencyProxy>   
<emergencyProxyPort></emergencyProxyPort>   
<outboundProxy></outboundProxy>   
<outboundProxyPort></outboundProxyPort>   
<registerWithProxy>true</registerWithProxy>   
</sipProxies>  
<enableVad>false</enableVad>  
<preferredCodec>g729a</preferredCodec>  
<natEnabled>!!!!! TRUE/FALSE !!!!!</natEnabled>   
<natAddress></natAddress>   
<phoneLabel>!!!!! LINE LABEL !!!!!</phoneLabel>  
<sipLines>  
&bull;   
<featureID></featureID>  
<featureLabel></featureLabel>  
<proxy>!!!!! SIP SERVER !!!!!</proxy>  
<port>5060</port>  
<name>09518096</name>  
<displayName>V-Spec</displayName>  
<autoAnswer>  
<autoAnswerEnabled>2</autoAnswerEnabled>  
</autoAnswer>  
<callWaiting>3</callWaiting>  
<authName>!!!!! USERNAME !!!!!</authName>  
<authPassword>!!!!! PASSWORD !!!!!</authPassword>  
<sharedLine>false</sharedLine>  
<messageWaitingLampPolicy>3</messageWaitingLampPolicy>  
<messagesNumber>!!!!! SIP PHONE NUMBER!!!!!</messagesNumber>  
<ringSettingIdle>4</ringSettingIdle>  
<ringSettingActive>5</ringSettingActive>  
<contact>!!!!! SIP PHONE NUMBER !!!!!</contact>  
<forwardCallInfoDisplay>  
<callerName>true</callerName>  
<callerNumber>false</callerNumber>  
<redirectedNumber>false</redirectedNumber>  
<dialedNumber>true</dialedNumber>  
</forwardCallInfoDisplay>  
</line>  
</sipLines>  
<voipControlPort>5060</voipControlPort>   
<dscpForAudio>184</dscpForAudio>   
<ringSettingBusyStationPolicy>0</ringSettingBusyStationPolicy>   
</sipProfile>  
<loadInformation>SIP42.8-5-2S</loadInformation>  
<directoryURL></directoryURL>  
<messagesURL>!!!!! SIP SERVER !!!!!</messagesURL>  
<servicesURL></servicesURL>  
<networkLocale>!!!!! LOCALE !!!!!</networkLocale>   
<networkLocaleInfo>   
<name>!!!!! LOCALE !!!!!</name>   
</networkLocaleInfo>   
</device>

Open in new window


Take in to account though that the phones are very picky. One wrong character and they start to protest. Oh, it's also case sensitive.
0
 
AXISHKAuthor Commented:
Doesn't work.

Do I need to reload the image file to the phone first. Do I need to change it to SIP phone as I have saw some article that is is not come with SIP bey default ? What other files should there be beside the SEP<MAC>.xml.cnf ?
0
 
Ernie BeekExpertCommented:
0
 
AXISHKAuthor Commented:
Doesn't help. Actually, the steps is not really up-to-date as some and applicable to Cisoc 7942. eg. OS79xx.txt don't need any more.

Actually, which file should be in place before we load the configuration. Really want to some step by step to check and make sure none is missing before loading the configuration.

Tks
0
 
AXISHKAuthor Commented:
FYI, here is the XML configuration that I try to load to the phone.

After reboot the phone, it still return with "Unprovisioned".

When I check the firmware on the phone :
1. Load File  term42.default
2. App Load ID jar42sip.9-0-3TH1-22.sbin
3. JVM Load ID cvm42sip.9-0-3TH1-22.sbin
4. OS Load ID cnu42.9-0-3TH1-22.sbn
5. Boot Load ID tnp42.8-3-1-21a.bin
6. dsp42.9-0-3TH1-22.sbn

So, suppose my firmware SIP42.9-0-3S should be retrevied, correct ? Anything missing...

Thanks

<device> 
<Default>   
<callManagerGroup>   
<members>   
<member priority="0">   
<callManager>   
<ports>   
<ethernetPhonePort>2000</ethernetPhonePort>   
<sipPort>5060</sipPort>  
<securedSipPort>5061</securedSipPort>  
</ports>   
<processNodeName>192.168.1.32</processNodeName>   
</callManager>   
</member>   
</members>   
</callManagerGroup>  
<loadInformation9 model="IP Phone 7942G"></loadInformation9>  
</Default>   
<deviceProtocol>SIP</deviceProtocol>  
<sshUserId>admin</sshUserId>  
<sshPassword>admin</sshPassword>  
<devicePool>  
<dateTimeSetting>  
<dateTemplate>D/M/Y</dateTemplate> 
<timeZone>China Standard/Daylight Time</timeZone>  
<ntps>   
<ntp>   
<name>hk.pool.ntp.org</name>   
<ntpMode>Unicast</ntpMode>   
</ntp>   
</ntps>   
</dateTimeSetting>  
<callManagerGroup>  
<members>  
<member priority="0">  
<callManager>  
<ports>  
<ethernetPhonePort>2000</ethernetPhonePort>  
<sipPort>5060</sipPort>  
<securedSipPort>5061</securedSipPort>  
</ports>  
<processNodeName>192.168.1.32</processNodeName>  
</callManager>  
</member>  
</members>  
</callManagerGroup>  
</devicePool>  
<sipProfile>  
<sipProxies>  
<backupProxy></backupProxy>   
<backupProxyPort></backupProxyPort>   
<emergencyProxy></emergencyProxy>   
<emergencyProxyPort></emergencyProxyPort>   
<outboundProxy></outboundProxy>   
<outboundProxyPort></outboundProxyPort>   
<registerWithProxy>true</registerWithProxy>   
</sipProxies>  
<enableVad>false</enableVad>  
<preferredCodec>g729a</preferredCodec>  
<natEnabled>FALSE</natEnabled>   
<natAddress></natAddress>   
<phoneLabel>ABC</phoneLabel>  
<sipLines> 
<featureID></featureID>  
<featureLabel></featureLabel>  
<proxy>192.168.1.32</proxy>  
<port>5060</port>  
<name>09518096</name>  
<displayName>V-Spec</displayName>  
<autoAnswer>  
<autoAnswerEnabled>2</autoAnswerEnabled>  
</autoAnswer>  
<callWaiting>3</callWaiting>  
<authName>2884</authName>  
<authPassword>8888</authPassword>  
<sharedLine>false</sharedLine>  
<messageWaitingLampPolicy>3</messageWaitingLampPolicy>  
<messagesNumber>2884</messagesNumber>  
<ringSettingIdle>4</ringSettingIdle>  
<ringSettingActive>5</ringSettingActive>  
<contact>2884</contact>  
<forwardCallInfoDisplay>  
<callerName>true</callerName>  
<callerNumber>false</callerNumber>  
<redirectedNumber>false</redirectedNumber>  
<dialedNumber>true</dialedNumber>  
</forwardCallInfoDisplay>  
</line>  
</sipLines>  
<voipControlPort>5060</voipControlPort>   
<dscpForAudio>184</dscpForAudio>   
<ringSettingBusyStationPolicy>0</ringSettingBusyStationPolicy>   
</sipProfile>  
<loadInformation>SIP42.9-0-3S</loadInformation>  
<directoryURL></directoryURL>  
<messagesURL>192.168.1.32</messagesURL>  
<servicesURL></servicesURL>  
<networkLocale>United_States</networkLocale>   
<networkLocaleInfo>   
<name>United_States</name>   
</networkLocaleInfo>   
</device>

Open in new window

0
 
AXISHKAuthor Commented:
Tks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.