[cisco-voip] calls to uccx trigger fail after enabling dns clients on cucm

[Ryan Huff]

- Check that forward and reverse DNS is working for ALL UC server FQDNs on your DNS server
- Have a look in CUCM Unified reporting and make sure you don't have any DB replication issues
- Look at the local voice network the phone is on; is it getting a DNS server that is able to resolve the FQDN of the UC servers?

Cheers,

-Ryan

From: Edward.Countryman at PresenceHealth.org
To: cisco-voip at puck.nether.net
Date: Thu, 18 Jun 2015 18:58:30 +0000
Subject: [cisco-voip] calls to uccx trigger fail after enabling dns clients	on cucm














Hello,  We’ve run into a very odd problem which I want to share and see if anyone might have any insight to share..
 
Let me describe the situation:
 
-New cucm 10.5.2 cluster, set up with DNS client enabled. (domain is: 
mycompanyname.net)
-New uccx 10.6.1 server (still in demo mode) setup and integrated with the new cucm cluster.  DNS client enabled.  (domain is:
mycompanyname.net)
 
When a phone (registered to new cucm cluster) calls a trigger on new uccx server it fails
IF THE PHONE HAS mycompanyname.net as the domain name indicated..
 
HOWEVER:  if we change the domain name to something else, even something fake like BOGUS.NET, then calls complete normally.
 
I don’t understand what could be happening here, any ideas?
 









_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150618/a91bc203/attachment.html>