I realize you mentioned the IP addresses of the communications manager servers were listed in the phone's trust list however; keep in mind that if DNS/FQDNs are being used, the phones will also have to be able to resolve those FQDNs (otherwise, you'd likely experience something very similar to this).
If you have verified from the individual phone, that all registerable nodes are listed in the trust list, verify those nodes are also in the CM Server Group. You might also check on this server node that did not except phone registrations, that CM services and TFTP services are enabled. -Ryan On Jan 30, 2017, at 2:15 AM, Nathan Reeves <[email protected]<mailto:[email protected]>> wrote: Which Servers are included in the Server Group which is selected in the Device Pool assigned to the Phones? When you mention 'TFTP Server lists', I'm assuming you mean the IP Addresses included in DHCP Option 150? This is seperate to the CUCM Servers that are pushed to the phones. But assuming all servers are included in the CUCM Server Group assigned to the Device Pool, the phones should have failed over upon loss of communication with their primary (and possibly) secondary CUCM Server. Take a look at the web page of a phone and under the 'Network Setup' page, see what are set for 'Unified CM 1', 'Unified CM 2' and 'Unified CM 3' are. On Mon, Jan 30, 2017 at 2:52 PM, Gary_Bates_Command_Solutions <[email protected]<mailto:[email protected]>> wrote: My client had an issue where the 2nd sub did not register any phones when the Pub and primary Sub failed. This is a 1500 seat call centre so it caused a massive problem. All phones have the IP addresses of both subs in their TFTP server lists. Network routing confirmed ok. Call Manager / TFTP service running on both Subs. DB replication status good. Could someone confirm that if Pub / Sub 1 go down, Sub 2 should allow phone/ device registration and calls to still work ? Regards Gary Bates Voice and Network Specialist CCIE #53842 [cid:[email protected]] Mobile 0424 229 995 ( + 61 424 229995<tel:+61%20424%20229%20995> ) Email: [email protected]<mailto:[email protected]> _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
