Cisco 7962 and 7942 Phone Registration issue

[toddbengen]

Preface with new to VoIP and am trying to create a small lab environment for students to get a little bit of exposure to VoIP and QoS as part of a networking course.

Using a 2901 with CUCME 10.5.  Have 4 phones registered and working fine - 2 7962's and 2 7940's. When checking the boot load ID - phones that work have a tnp62.9-3-1-57.bin.  Phones that fail have a tnp62.8-3-1-21a.bin.  Thinking the issue has to be related to this in some way but haven't been able to find a working combination.  Below are config file, flash contents and tftp debug messages.  Hoping someone can give me a nudge in the right direction to get the lab up and operational for students to learn with.

Thanks

Debug tftp events for a successful 7962 and 7940 load:

* * * * * Successful from 7962
*Nov 18 14:39:46.962: TFTP: Looking for CTLSEP34DBFDCD4861.tlv
*Nov 18 14:39:47.066: TFTP: Looking for ITLSEP34DBFDCD4861.tlv
*Nov 18 14:39:47.174: TFTP: Looking for ITLFile.tlv
*Nov 18 14:39:47.410: TFTP: Looking for SEP34DBFDCD4861.cnf.xml
*Nov 18 14:39:47.410: TFTP: Opened system:/its/vrf1/XMLDefault7962.cnf.xml, fd 10, size 1258 for process 132
*Nov 18 14:39:47.414: TFTP: Finished system:/its/vrf1/XMLDefault7962.cnf.xml, time 00:00:00 for process 132

*Nov 18 14:39:50.094: TFTP: Looking for English_United_States/mk-sccp.jar
*Nov 18 14:39:50.458: TFTP: Looking for United_States/g3-tones.xml

*Nov 18 14:39:51.674: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-4:SEP34DBFDCD4861 IP:192.168.150.36 Socket:3 DeviceType:Phone has unregistered abnormally.
*Nov 18 14:39:52.314: %IPPHONE-6-REGISTER: ephone-4:SEP34DBFDCD4861 IP:192.168.150.36 Socket:5 DeviceType:Phone has registered.

* * * * * Successful from 7940
*Nov 18 14:41:20.698: TFTP: Looking for CTLSEP001B53B8D938.tlv
*Nov 18 14:41:20.838: TFTP: Looking for SEP001B53B8D938.cnf.xml
*Nov 18 14:41:20.838: TFTP: Opened system:/its/vrf1/XMLDefault7940.cnf.xml, fd 10, size 1066 for process 119
*Nov 18 14:41:20.846: TFTP: Finished system:/its/vrf1/XMLDefault7940.cnf.xml, time 00:00:00 for process 119

*Nov 18 14:41:21.402: %IPPHONE-6-REG_ALARM: 16: Name=SEP001B53B8D938 Load=8.1(SR.2) Last=CM-NAKed
*Nov 18 14:41:21.402: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-5:SEP001B53B8D938 IP:192.168.150.39 Socket:2 DeviceType:Phone has unregistered abnormally.
*Nov 18 14:41:21.402: %IPPHONE-6-REGISTER: ephone-5:SEP001B53B8D938 IP:192.168.150.39 Socket:3 DeviceType:Phone has registered.

*Nov 18 14:41:21.794: TFTP: Looking for SEP001B53B8D938.cnf.xml
*Nov 18 14:41:21.794: TFTP: Opened system:/its/vrf1/XMLDefault7940.cnf.xml, fd 10, size 1066 for process 119
*Nov 18 14:41:21.798: TFTP: Looking for RINGLIST.XML
*Nov 18 14:41:21.890: TFTP: Looking for DISTINCTIVERINGLIST.XML
*Nov 18 14:41:21.890: TFTP: Finished system:/its/vrf1/XMLDefault7940.cnf.xml, time 00:00:00 for process 119

Here is a log associated with an unsuccessful 7962 load:

* * * * * Unsuccessful from 7962
*Nov 18 14:32:56.334: TFTP: Looking for CTLSEP24B6574456AB.tlv
*Nov 18 14:32:56.438: TFTP: Looking for ITLSEP24B6574456AB.tlv
*Nov 18 14:32:56.546: TFTP: Looking for ITLFile.tlv
*Nov 18 14:32:56.814: TFTP: Looking for SEP24B6574456AB.cnf.xml.sgn
*Nov 18 14:32:56.994: TFTP: Looking for XMLDefault.cnf.xml.sgn

Here is the show run from the 2911 router:

R1_2911#show run
Building configuration...
Current configuration : 3396 bytes
!
! Last configuration change at 14:11:08 UTC Fri Nov 18 2022
!
version 15.5
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1_2911
!
boot-start-marker
boot-end-marker
!
! card type command needed for slot/vwic-slot 0/3
!
no aaa new-model
ethernet lmi ce
!
ip dhcp excluded-address 192.168.10.1 192.168.10.31
ip dhcp excluded-address 192.168.10.250 192.168.10.254
ip dhcp excluded-address 192.168.150.1 192.168.150.31
!
ip dhcp pool DATA10
network 192.168.10.0 255.255.255.0
default-router 192.168.10.1
!
ip dhcp pool VOICE150
network 192.168.150.0 255.255.255.0
default-router 192.168.150.1
option 150 ip 192.168.150.1
!
no ip domain lookup
ip cef
no ipv6 cef
multilink bundle-name authenticated
!
voice-card 0
voice register global
default mode
!
license udi pid CISCO2911/K9 sn xxxxxxxxx
hw-module pvdm 0/0
redundancy
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0.10
encapsulation dot1Q 10
ip address 192.168.10.1 255.255.255.0
interface GigabitEthernet0/0.150
encapsulation dot1Q 150
ip address 192.168.150.1 255.255.255.0
interface GigabitEthernet0/0.199
encapsulation dot1Q 199 native
ip address 192.168.199.1 255.255.255.0
!
interface GigabitEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1/0
no ip address
shutdown
clock rate 2000000
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
tftp-server system:/its/SEPDEFAULT.cnf alias XMLDefault.cnf
tftp-server flash:voiptest/jar42sccp.9-4-2ES26.sbn alias jar42sccp.9-4-2ES26.sbn
tftp-server flash:voiptest/term42.default.loads alias term42.default.loads
tftp-server flash:voiptest/term62.default.loads alias term62.default.loads
tftp-server flash:voiptest/SCCP42.9-4-2SR3-1S.loads alias SCCP42.9-4-2SR3-1S.loads
!
control-plane
!
mgcp behavior rsip-range tgcp-only
mgcp behavior comedia-role none
mgcp behavior comedia-check-media-src disable
mgcp behavior comedia-sdp-force disable
!
mgcp profile default
!
gatekeeper
shutdown
!
telephony-service
max-ephones 6
max-dn 6
ip source-address 192.168.150.1 port 2000
max-conferences 8 gain -6
transfer-system full-consult
create cnf-files version-stamp Jan 01 2002 00:00:00
!
ephone-dn 1
number 1010
ephone-dn 2
number 1020
ephone-dn 3
number 1030
ephone-dn 4
number 1040
ephone-dn 5
number 1050
ephone-dn 6
number 1060
!
ephone 1
mac-address 44E4.D945.63D8
type 7942
button 1:1
!
ephone 2
mac-address 24B6.5744.5CB4
type 7962
button 1:2
!
ephone 3
mac-address 34DB.FDCD.46E0
type 7962
button 1:3
!
ephone 4
mac-address 34DB.FDCD.4861
type 7962
button 1:4
!
ephone 5
mac-address 001B.53B8.D938
type 7940
button 1:5
!
ephone 6
mac-address 001B.53B8.D935
type 7940
button 1:6
!
line con 0
logging synchronous
line aux 0
line vty 0 4
login
transport input none
!
scheduler allocate 20000 1000
!
end

And finally the show flash:

R1_2911#show flash:
-#- --length-- -----date/time------ path
2 12 Sep 20 2019 10:02:00 +00:00 System Volume Information/WPSettings.dat
3 76 Sep 20 2019 10:02:00 +00:00 System Volume Information/IndexerVolumeGuid
4 108886252 May 29 2019 08:49:48 +00:00 c2900-universalk9-mz.SPA.155-3.M3.bin
5 2196 Nov 10 2022 21:27:58 +00:00 Baseline
6 1763397 Nov 18 2022 11:46:48 +00:00 voiptest/jar42sccp.9-4-2ES26.sbn
7 2869 Nov 15 2022 09:18:42 +00:00 BackupConfig_1115
8 0 Nov 18 2022 11:31:20 +00:00 voiptest
9 668 Nov 18 2022 11:49:04 +00:00 voiptest/term42.default.loads
10 668 Nov 18 2022 11:49:24 +00:00 voiptest/term62.default.loads
11 672 Nov 18 2022 13:24:42 +00:00 voiptest/SCCP42.9-4-2SR3-1S.loads

[Maren Mahoney]

Crap. I'm an idiot. Try the load command for the 7942/62 without the ".loads" at the end. The .loads command does automatic TFTP bndings based on the cnf-file locations command (in CME 7 and later). You have the TFTP bindings explicit in the config, which are in a directory in the flash.

elephony-service
max-ephones 6
max-dn 6
ip source-address 192.168.150.1 port 2000
cnf-file location flash:
load 7960-7940 jar42sccp.8-5-4TH1-6
load 7942 SCCP42.8-5-4S
load 7962 SCCP42.8-5-4S

I can't believe I didn't notice that before.

Maren

[toddbengen]

Hey Maren - it's making progress and I greatly appreciate it.  We've all looked over config errors many times.  I incorporated the adjusted load lines - worked perfect.

R1_2911(config-telephony)#load 7942 SCCP42.8-5-4S
Updating CNF files
CNF files update complete for phonetype(7942)

R1_2911(config-telephony)#load 7962 SCCP42.8-5-4S
Updating CNF files
CNF files update complete for phonetype(7962)

Had my fingers crossed. Activated the switchports connected to my old 7942 and 7962 with the old firmware - the only two phones causing me issues.

With debug tftp events turned on, those two phones are still looking for the exact same files they were looking for previously - thus not working and ultimately not registering.

7942 with TNP42.8-3-1-21a.bin firmware - fails.
Dec 22 12:13:37.020: TFTP: Looking for CTLSEP44E4D94563D8.tlv
Dec 22 12:13:37.120: TFTP: Looking for ITLSEP44E4D94563D8.tlv
Dec 22 12:13:37.232: TFTP: Looking for ITLFile.tlv
Dec 22 12:13:37.504: TFTP: Looking for SEP44E4D94563D8.cnf.xml.sgn
Dec 22 12:13:37.680: TFTP: Looking for XMLDefault.cnf.xml.sgn

7962 with TNP62.8-3-1-21a.bin firmware - fails.
Dec 22 12:10:21.312: TFTP: Looking for CTLSEP24B657445CB4.tlv
Dec 22 12:10:21.436: TFTP: Looking for ITLSEP24B657445CB4.tlv
Dec 22 12:10:21.548: TFTP: Looking for ITLFile.tlv
Dec 22 12:10:21.852: TFTP: Looking for SEP24B657445CB4.cnf.xml.sgn
Dec 22 12:10:22.016: TFTP: Looking for XMLDefault.cnf.xml.sgn

These two phones remain unregistered.  So it seems the firmware can't be getting updated.  The non-working phones search for mac address specific .tlv and cnf.xml.sig files that are obviously not getting created.  There are no .sig files anywhere in flash that I can locate.

The working phones search for mac address specific .tlv and cnf.xml files that do exist in flash0:/its/vrf1.  These files have a current date/timestamp so I know these were just created when I ran the create cnf-files command.

Not sure what that means - just trying to help connect a few dots.  Thanks for help Maren - hope you are not yet wishing you had never responded.  I appreciate you.

[Maren Mahoney]

Do you still have both sets of firmware files for the 7942/62 in flash? I'm wondering if they are still reaching out to the 9.4.2 files. I'm grasping for straws a bit here, but if both sets are on your router at the moment would it be possible to delete the 9.4.2 files and upload them after the interim upgrade is done? Both the 8.5.4 and the 9.4.2 have the "term62.default.loads" file in the set.

Maren

(I was a math major, so finding a solution to a problem is a 'dog with a bone' thing for me.)

[Adam Pawlowski]

I believe the phones can go right to the later rev with the 3491672850*# reset code, but it depends on the term default and TFTP options being set right, otherwise the phone just looks bricked. It's been a way long time for me on that one, but I think that was one way to get around the auth fail boot loop chaos in the field.

[toddbengen]

I appreciate the tenacity!!!  I too being a lifelong IT guy can't seem to rest or just move on until resolved.  This one is particularly challenging as I have not worked with VoIP at all.  Been a Cisco guy for a long time but focus on routing and switching.  So the phones doing everything via TFPT is a challenging maze for me.  Will keep researching and posting findings.

As to your suggestion - anything that is not related to firmware 8.5 is completely gone and has been.  I moved them to a TFTP server and removed from flash with that potential conflict in mind.  

[Maren Mahoney]

Well, shoot. You've done a lot of troubleshooting so far. It occurs to me that I'm pretty sure the phones should register with their existing firmware, even if they aren't getting the new (middle) firmware. Or are you aware of a version issue?

My next thought would be to work through the troubleshooting steps in this doc. You've done most of these things already, but it has very specific steps and we are obviously missing something. Take a look and let me know what you think:

Troubleshooting Phone Registration in Cisco Unified CME 

Maren

[toddbengen]

Thanks maren - will work through that.  This case has the same issue and same output for file names. https://community.cisco.com/t5/ip-telephony-and-phones/7962-sccp-phone-registration-to-cme/td-p/4012051 

One solution was to delete the ITL file - this document describes that process.  https://community.cisco.com/t5/collaboration-knowledge-base/delete-itl-file/ta-p/3114410 .   

I am working on this lab remote over break - so do not have the ability to physically touch the phone to go through this but will  give it a try when I can.  And of course will keep digging in the meantime.  Thanks again and happy holidays.

[Maren Mahoney]

AFAIK CME does not issue an ITL file like CUCM does. But a factory reset of the phones would delete it and I assume you've already tried that. If not....

Maren

[toddbengen]

Some of the phones did come from our CIS department which uses CUCM.  I was told phones were factory reset before being donated to our department.  I will cross my fingers and hope that maybe a few phones were NOT factory reset and this whole thing might just go away!            So there's a chance!!