11-24-2014 07:30 AM - edited 03-17-2019 04:40 PM
Hi all,
We are deploying Jabber 10.5 with two domains, internal domain and an external domain
Internal DNS authoritative for : example.local
External DNS authoritative for : example.com
To workwaround this I have configured internal pintpoint subdomain zone according to the guide:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide_chapter_010.html
Based on this, the client queries _cisco-uds._tcp.cisco-internal.example.com when it does not get any respond from
_cisco-uds._tcp.example.com
_cuplogin._tcp.example.com
_collab-edge._tls.example.com
But checking the traces there is no _cisco-uds._tcp.cisco-internal.example.com request. So Jabber is not able to complete the service discovery.
Is there any configuration required to trigger this behavior?
Many thanks in advance,
Frances
Solved! Go to Solution.