12-24-2024 11:02 AM
Hello,
i am trying to register some new phones to CUCME, and they are stuck on registering looking for these files
CUCME#
*Dec 24 19:14:06.219: TFTP: Looking for CTLSEP2C01B5E6E361.tlv
*Dec 24 19:14:07.599: TFTP: Looking for ITLSEP2C01B5E6E361.tlv
*Dec 24 19:14:08.987: TFTP: Looking for ITLFile.tlv
*Dec 24 19:14:10.679: TFTP: Looking for SEP2C01B5E6E361.cnf.xml
*Dec 24 19:14:12.039: TFTP: Looking for XMLDefault.cnf.xml
*Dec 24 19:14:12.039: TFTP: Opened system:/its/vrf1/XMLDefault.cnf.xml, fd 10, size 3626 for process 126
*Dec 24 19:14:12.043: TFTP: Finished system:/its/vrf1/XMLDefault.cnf.xml, time 00:00:00 for process 126
*Dec 24 19:14:14.255: TFTP: Looking for AppDialRules.xml
*Dec 24 19:14:14.799: TFTP: Looking for CTLSEP2C01B5E6E361.tlv
*Dec 24 19:14:15.671: TFTP: Looking for defaultheadsetconfig.json
*Dec 24 19:14:16.247: TFTP: Looking for ITLSEP2C01B5E6E361.tlv
*Dec 24 19:14:17.259: TFTP: Looking for ITLFile.tlv
*Dec 24 19:14:18.307: TFTP: Looking for SEP2C01B5E6E361.cnf.xml
*Dec 24 19:14:19.507: TFTP: Looking for XMLDefault.cnf.xml
*Dec 24 19:14:19.507: TFTP: Opened system:/its/vrf1/XMLDefault.cnf.xml, fd 10, size 3626 for process 126
*Dec 24 19:14:19.511: TFTP: Finished system:/its/vrf1/XMLDefault.cnf.xml, time 00:00:00 for process 126
*Dec 24 19:14:21.551: TFTP: Looking for AppDialRules.xml
CUCME config
voice service voip
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
bind control source-interface GigabitEthernet0/0
bind media source-interface GigabitEthernet0/0
registrar server expires max 1200 min 300
asserted-id pai
conn-reuse
!
!
!
!
voice register global
mode cme
source-address 172.16.100.1 port 5060
max-dn 25
max-pool 25
load 8851 sip88xx.12-8-1-0201-486
load 8865 sip8845_65.12-8-1-0101-482
authenticate register
authenticate realm all
tftp-path flash:
create profile sync 0000446416248343
auto-register
!
!
voice register dn 1
number 1000
name Admin
no-reg
!
voice register pool 1
busy-trigger-per-button 2
id mac 2C01.B5E6.E361
type 8865
number 1 dn 1
username admin password cisco123
codec g711ulaw
!
!
tftp-server flash:RingList.xml
tftp-server flash:boot1288xx.BE-01-007.sbn alias boot1288xx.BE-01-007.sbn
tftp-server flash:fbi88xx.BE-01-012.sbn alias fbi88xx.BE-01-012.sbn
tftp-server flash:kern88xx.12-8-1-0201-486.sbn alias kern88xx.12-8-1-0201-486.sbn
tftp-server flash:kern288xx.12-8-1-0201-486.sbn alias kern288xx.12-8-1-0201-486.sbn
tftp-server flash:kern388xx.12-8-1-0201-486.sbn alias kern388xx.12-8-1-0201-486.sbn
tftp-server flash:m0patch288xx.BE-01-001.sbn alias m0patch288xx.BE-01-001.sbn
tftp-server flash:preloader88xx.BE-01-006.sbn alias preloader88xx.BE-01-006.sbn
tftp-server flash:rootfs88xx.12-8-1-0201-486.sbn alias rootfs88xx.12-8-1-0201-486.sbn
tftp-server flash:rootfs288xx.12-8-1-0201-486.sbn alias rootfs288xx.12-8-1-0201-486.sbn
tftp-server flash:rootfs388xx.12-8-1-0201-486.sbn alias rootfs388xx.12-8-1-0201-486.sbn
tftp-server flash:sb288xx.BE-01-026.sbn alias sb288xx.BE-01-026.sbn
tftp-server flash:sb2288xx.BE-01-013.sbn alias sb2288xx.BE-01-013.sbn
tftp-server flash:sb2388xx.BE-01-028.sbn alias sb2388xx.BE-01-028.sbn
tftp-server flash:sip88xx.12-8-1-0201-486.loads alias sip88xx.12-8-1-0201-486.loads
tftp-server flash:ssb288xx.BE-01-007.sbn alias ssb288xx.BE-01-007.sbn
tftp-server flash:vc488xx.12-8-1-0201-486.sbn alias vc488xx.12-8-1-0201-486.sbn
tftp-server flash:fbi8845_65.BEV-01-006.sbn alias fbi8845_65.BEV-01-006.sbn
tftp-server flash:kern8845_65.12-8-1-0101-482.sbn alias kern8845_65.12-8-1-0101-482.sbn
tftp-server flash:rootfs8845_65.12-8-1-0101-482.sbn alias rootfs8845_65.12-8-1-0101-482.sbn
tftp-server flash:sb28845_65.BEV-01-015.sbn alias sb28845_65.BEV-01-015.sbn
tftp-server flash:sip8845_65.12-8-1-0101-482.loads alias sip8845_65.12-8-1-0101-482.load
tftp-server flash:vc48845_65.12-8-1-0101-482.sbn alias vc48845_65.12-8-1-0101-482.sbn
!
telephony-service
max-ephones 25
max-dn 25
ip source-address 172.16.100.1 port 2000
max-conferences 8 gain -6
transfer-system full-consult
Solved! Go to Solution.
12-27-2024 01:36 AM
Hello @suya2024
On your voice register global process delete these command:
authenticate register
authenticate realm all
Re create profiles and reboot your Phone since all security settings are deleted.
12-25-2024 02:25 PM - edited 12-25-2024 02:26 PM
Hello @suya2024
This issue occurs because Cisco IP phones, by default, attempt to register securely by looking for specific trust-related files: CTL (Certificate Trust List) and ITL (Identity Trust List) files. These .tlv
files are used for secure communication between the phone and the call manager (in your case, CUCME). If these files are not available, or if there is a mismatch in the trust setup, the phones may fail to register.
So, hard reset IP Phones and see if registering is OK after that.
12-25-2024 02:31 PM
Thanks, I have gone to admin settings and reset the phone several times, phone still looking for those files
12-25-2024 03:13 PM
To recover from this situation, the ITL file on the phone can be deleted or erased via the phone’s administrative menu options.
12-25-2024 07:29 PM
No ITL file on the phone, all security settings deleted
12-27-2024 01:36 AM
Hello @suya2024
On your voice register global process delete these command:
authenticate register
authenticate realm all
Re create profiles and reboot your Phone since all security settings are deleted.
12-27-2024 07:10 AM
Thank you, removing the authenticate commands allowed phones to register
12-25-2024 09:26 PM
It appears that the phone is unable to find the configuration file. If you are manually configuring the voice register pool, remove the auto-reg command. Additionally, after adding the configurations, make sure to issue the command create profile. If the phones and CME are on the same network subnet, you can avoid the authentication command under voice register global and use of the username/password on the voice register pool.
12-26-2024 06:19 AM
Ok I will try removing the authenticate, username and password commands since CME and phones are in the same subnet. How will this help with the phones looking for files that I don’t have on the CME based on my original post? Thanks
12-28-2024 10:05 PM
I hope you have used the "create profile" command, which creates the necessary files in the flash for the phones to register. The "authenticate" command is recommended when the CME is in one subnet and the phones are in another.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide