06-26-2013 02:03 PM - edited 03-16-2019 06:06 PM
Hi guys,
I am deploying about 1500 6921 phones and 200 7962 phones.
All of the 7962 phones follow registration based on the device pool, which is Sub 02, Sub 01 then Publisher.
The 7962's register without a problem.
The 6921's are ONLY going to the publisher and will not go to any subsribers. Device pools, network settings, etc... are identical. This happens even if the phones are in the same VLAN and location.
Running CUCM 8.6 and the 6921's are running the latest version of FW, which I belive is 9.3...something.
Any ideas?
06-26-2013 02:25 PM
Hi
DB replications to sub are ok? can you check with rtmt?
Sent from Cisco Technical Support iPhone App
06-26-2013 02:31 PM
Verified DB replication with quick audit, everything is okay.
06-26-2013 02:29 PM
Are your CUCM servers defined with hostname or IP addresses?
Chris
06-26-2013 02:31 PM
The servers are configured with hostnames, DNS is okay everywhere.
When looking through the config on the 6921, it says primary server is CUCMPUB and that the standby is CUCMSUB01 but it won't join it.
06-26-2013 02:33 PM
Change it to IP as that is best practice as stated in SRND, that should fix your problem.
HTH,
Chris
07-01-2013 09:44 AM
Thanks Chris. I will make the change after hours.
What's involved exactly? Change the names under SERVERS to IP Addresses and restart the CUCM services on all nodes?
Thanks!
07-01-2013 09:49 AM
Simply change the hostnames to IPs in the config, no need to restart anything except for rebooting the phones.
Chris
07-01-2013 04:03 PM
Changed all the servers to IP addresses in the configuration, restarted all the phones.
All the 7962's went to their correct subscriber, ALL of the 6921's went straight to the publisher....
07-01-2013 04:03 PM
DB Audit comes back good:
Getting content from PUB
Comparing content in SUBs
checking: cucmsub01
--> OK
checking: cucmsub02
--> OK
No Mismatches were found
07-02-2013 03:36 AM
Can you pull one XML files of both the working and non-working phones and post?
Tapan
07-02-2013 06:48 AM
This has been resolved -
This is a bug in 69XX firmware 9-3-3-2
Downgrading to the previous release fixes the isssue.
07-02-2013 01:48 PM
Can you share the bug id?
Chris
07-03-2013 05:42 AM
I'm not sure if there is one.. I downgraded them and everything worked great afterwares.
Can Cisco pitch in on this?
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