cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Walkthrough Wednesdays
342
Views
5
Helpful
1
Replies
froigbor23
Beginner

Jabber for Windows 10.5 with separte domains - Service discovery not working

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

1 ACCEPTED SOLUTION

Accepted Solutions

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.

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.

Sorry, there is no work around for this.

Please rate all useful posts

View solution in original post

1 REPLY 1

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.

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.

Sorry, there is no work around for this.

Please rate all useful posts

View solution in original post

Content for Community-Ad

Spotlight Awards 2021