https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-10-5-with-separte-domains-service-discovery/m-p/2597446#M17475 <P>The pin point sub domain is no longer supported. This was used with older Jabber clients. This has been replaced by the "voiceservicedomain" feature. The problem with voice services domain is that once you configure it, your jabber client load this in its boostrap file and will always use that domain regardless of the location. Eg if you have set this to be your example.local, then when jabber client is outside your organisation it will still look for example.local and it will fail because that domain is not routable.</P><P>Your deployment will not work unless you implement a SPLIT DNS domain. With SPLIT DNS domain you host a copy of that routable example.com internally and you can use a single domain.</P><P>Sorry, there is no work around for this.</P> Mon, 24 Nov 2014 17:22:44 GMT Ayodeji Okanlawon 2014-11-24T17:22:44Z https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-10-5-with-separte-domains-service-discovery/m-p/2597445#M17474 <P>Hi all,</P><P>We are deploying Jabber 10.5 with two domains, internal domain and an external domain<BR />Internal DNS authoritative for : example.local<BR />External DNS authoritative for : example.com</P><P><BR />To workwaround this I have configured internal pintpoint subdomain zone according to the guide:<BR /><A href="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" target="_blank">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</A></P><P>Based on this, the client queries&nbsp; _cisco-uds._tcp.cisco-internal.example.com when it does not get any respond from</P><P>&nbsp;&nbsp; _cisco-uds._tcp.example.com<BR />&nbsp;&nbsp; _cuplogin._tcp.example.com<BR />&nbsp;&nbsp; _collab-edge._tls.example.com</P><P>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.<BR />Is there any configuration required to trigger this behavior?</P><P>Many thanks in advance,<BR />Frances</P> Sun, 17 Mar 2019 23:40:35 GMT https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-10-5-with-separte-domains-service-discovery/m-p/2597445#M17474 devnetjmt 2019-03-17T23:40:35Z https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-10-5-with-separte-domains-service-discovery/m-p/2597446#M17475 <P>The pin point sub domain is no longer supported. This was used with older Jabber clients. This has been replaced by the "voiceservicedomain" feature. The problem with voice services domain is that once you configure it, your jabber client load this in its boostrap file and will always use that domain regardless of the location. Eg if you have set this to be your example.local, then when jabber client is outside your organisation it will still look for example.local and it will fail because that domain is not routable.</P><P>Your deployment will not work unless you implement a SPLIT DNS domain. With SPLIT DNS domain you host a copy of that routable example.com internally and you can use a single domain.</P><P>Sorry, there is no work around for this.</P> Mon, 24 Nov 2014 17:22:44 GMT https://community.cisco.com/t5/collaboration-applications/jabber-for-windows-10-5-with-separte-domains-service-discovery/m-p/2597446#M17475 Ayodeji Okanlawon 2014-11-24T17:22:44Z