04-08-2011 05:06 AM - edited 03-16-2019 04:25 AM
Hi,
I have CUCM 7.1.3 I installed the 6901-911 device enabler sftware and firmare version 9.1.1 for the 6901 & 6911 phones. I can't seem to get the phones to register. There are on the same voice subnet as 6921 phones which are registered ok so I know the network is ok. I can see from the console logs attached that the phone is getting the config file and its software load file of the publisher. It also recognises that the phone is non secure mode because there is no ctl file.
I have also attached the traces from the call manager which is giving an registration alarm with reason code 10, I have looked up this on a call manager events doc and reason code 10 is an authentication error. I copied the device security profile for this phone and made a new one just to elimiate any possible bugs with the security profile configuration but this didn't work. I also checked the device enabler and firmware and there are compatable with my version of CUCM
Has anyone had this problem before?
Thanks
Regards
Neil
Solved! Go to Solution.
04-08-2011 05:13 AM
Neil,
I had this problem before with 6945 phones within TAC. The phone downloaded the configuration file just fine but CUCM rejected the registration with an a similar cause. In our cause we had to install the enabler on every node of the cluster and perform a cluster wide reboot afterwards.
I hope this helps.
04-08-2011 05:13 AM
Neil,
I had this problem before with 6945 phones within TAC. The phone downloaded the configuration file just fine but CUCM rejected the registration with an a similar cause. In our cause we had to install the enabler on every node of the cluster and perform a cluster wide reboot afterwards.
I hope this helps.
04-08-2011 05:37 AM
Hi Robert,
I did install the enabler on every node in the cluster but I didn't do a reboot. I'll try that at the weekend and see how I get on.
Thanks for the quick reply
Neil
04-14-2011 01:21 AM
Hi Rob,
The reboot did the trick.
Thanks very much for the info
Regards
Neil
06-06-2011 06:27 AM
Robert,
With your 6945 phones, did you show registered in CUCM but "Phone not registered" displayed on the phone? That is what I am seeing.
I'm running CUCM 8.0(3)
8.0.3.22900-5
The phone load is 9.1.1
Thanks,
Mark
01-05-2012 01:26 AM
Hi everyone,
i have the same issue with registering the 6921 phone on one remote location.
Phone displays "phone not registered", in the CUCM 7.1.5-34063-1 the 6921 phone has "unknown" status and IP.
There are a few 7941 phones on that location that are fully registered and working.
The 6921 phone was rebooted and was factory reset many times but none seems to do any changes on the registering issue.
if i change localization on the phone, do a phone reboot, the phone gets the proper localization, but still does not register to CUCM.
Checking the switch, i see that the phone gets an IP address, after checking the phones web page i noticed that the phone gets all the tftp info that he needs..
Phone console log states a few error messages regarding the timezone authentication failing..
1) TID: 0x95bfc6f0 task name: PtROVISION tag name: dateTemplate value : D.M.Y is error format
2) ERROR: Authenticating configuration file tzdatacsv.csv.sgn
download_configuration_process 1530: Auth tzdatacsv.csv.sgn fails
We also have a TAC case opened, but for now no usefull info provided from them..
Did you Mark solved your issue with the 6945 phone?
Thanks for any information provided!
01-05-2012 05:16 AM
Ales,
We had a work around for this issue. The issue happens on the 6945 when a phone button template is used. To get around this issue we assigned the phone button template and then click "modify button items". We would then move a speed dial item from the assigned to unassigned and then move it back. This would make it an individual phone button template. After a couple of upgrades, we tried using the phone button template again, but it still didn't work, or worked intermittently.
I don't know if this is the same issue you are seeing though. With this issue, the phone displayed not registered, but it showed registered in callmanager. You could reset the phone from the device page as well.
Mark
01-10-2012 01:40 AM
Mark,
Thank you for your reply.
We solved the issue, now i'm just posting for others, that might encounter the issue.
The error messages were related to security profiles. We haven't been able to solve the registering issue by deleting the security configuration manually on the 6921 or by doing the factory reset nor by changing the security profile on the phone.
The issue was finally solved by upgrading the phones firmware from SCCP.9-1-1-0 to SCCP.9-2-2-0.
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