Hi,
In my organisation we have internal.domain and external.domain
_cisco-uds._tcp exists ONLY in internal.domain DNS
_collab-edge._tls exisits ONLY in external.domain DNS
Our mobile Jabber clients login with username@external.domain and connect via MRA - no problems
Our Laptop Jabber clients login with username@internal.domain and connect directly to CUCM / IMP
The problem is we want our users to be able to login with one account which should be username@external.domain
With our current setup if laptop users login with username@external.domain then they will connect via MRA which is not desirable when connected via VPN or LAN
I read about using the voice service domain parameter and I believe we can use this to solve the problem
Can anyone tell me if what I say below sounds correct and will work and allow our users to login with external.domain service domain for the username format but then fallback and connect them internally instead of via MRA
1)We install the Jabber package on the laptops using the below parameter
msiexec /i CiscoJabberSetup.msi VOICE_SERVICES_DOMAIN=internal.domain CLEAR=1
2)Laptop users login to Jabber with external service domain login format username@external.domain
3)We use firewall to block LAN clients and VPN firewall to block VPN clients from resolving the _collab-edge._tls.external.domain SRV record
4) Laptop Jabber runs service discovery against _cisco-uds._tcp.external.domain which does not exist
5) Laptop Jabber runs service discovery against _collab-edge._tls.external.domain but the client is blocked from resolving this
6) Laptop Jabber then falls back to the voice service domain which is specified as the internal.domain containing the record _cisco-uds._tcp.internal.doman and the client then connects internally.
Thanks
