05-20-2020 03:09 PM
I am trying to get an 8841 to register with a CUCME server, but it's not working. The phone stays stuck at "phone is registering". I have two 7821 phones that are working properly on this CUCME server. Here's what I get when I debug tftp events. It just loops through these. I'm not sure what's up with the sgn (I assume that means signed). My 7821 phones don't request a .xml.sgn; just a regular .xml. I think this may be the issue, but I'm not sure what to do about it.
*May 20 20:57:47.921: TFTP: Looking for CTLSEP00EBD5CC0D11.tlv
*May 20 20:57:49.169: TFTP: Looking for ITLSEP00EBD5CC0D11.tlv
*May 20 20:57:50.349: TFTP: Looking for ITLFile.tlv
*May 20 20:57:52.397: TFTP: Looking for SEP00EBD5CC0D11.cnf.xml.sgn
*May 20 20:57:53.489: TFTP: Looking for XMLDefault.cnf.xml.sgn
*May 20 20:57:56.989: TFTP: Looking for AppDialRules.xml
*May 20 20:57:58.221: TFTP: Looking for SK0a51cee6-08b5-5f8e-af70-370f82a5dc8a.xml.sgn
*May 20 20:57:59.529: TFTP: Looking for CTLSEP00EBD5CC0D11.tlv
*May 20 20:58:00.581: TFTP: Looking for ITLSEP00EBD5CC0D11.tlv
*May 20 20:58:01.681: TFTP: Looking for ITLFile.tlv
*May 20 20:58:03.725: TFTP: Looking for SEP00EBD5CC0D11.cnf.xml.sgn
*May 20 20:58:04.881: TFTP: Looking for XMLDefault.cnf.xml.sgn
*May 20 20:58:08.045: TFTP: Looking for AppDialRules.xml
*May 20 20:58:09.385: TFTP: Looking for SK0a51cee6-08b5-5f8e-af70-370f82a5dc8a.xml.sgn
Solved! Go to Solution.
05-21-2020 04:36 PM
That's a good point, and I have missed that when I was just starting out a couple of months ago. In this case, that wasn't the problem. It was a previous configuration in the phone. I had to go in and reset the security settings. I had already done that, I thought, but I wasn't pressing the correct button. And then I had to put in the administrator password, which was the default Cisco with a capital C.
05-21-2020 01:00 PM
@Chris Campbell When you added Cisco 8841 phones, did you enter create profile command under voice register global.
voice register global create profile
05-21-2020 04:36 PM
That's a good point, and I have missed that when I was just starting out a couple of months ago. In this case, that wasn't the problem. It was a previous configuration in the phone. I had to go in and reset the security settings. I had already done that, I thought, but I wasn't pressing the correct button. And then I had to put in the administrator password, which was the default Cisco with a capital C.
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