Showing results for 
Search instead for 
Did you mean: 

Changing voice service domain compromised jabber IM ability


we have our main domain our jabber login domain is also , we have an expressway infrastructure in UK supporting MRA with a different domain, We have jabber on cloud(webex messenger). I followed below step to change the voice service domain which worked fine and i connected to the voice services VPN-lessly over, but i lost the ability to IM


The user always logs in with userid@domain4, as there should be no difference in user
experience when inside or outside. This means that if domain1 is different from domain4, you
must configure the voice services domain in the Jabber client. This is because the domain portion
of the login is used in order to discover the Collaboration Edge services using Service (SRV)
record lookups.
The client performs a Domain Name System (DNS) SRV record query for _collabedge._
tls.<domain>. This implies that when the domain from the login user ID is different than
the domain from the Expressway E, you must use the voice service domain configuration. Jabber
uses this configuration in order to discover the Collaboration Edge and the UDS.
There are multiple options that you can use in order to complete this task:
Add this as a parameter when you install Jabber via the Media Services Interface (MSI):
msiexec /i CiscoJabberSetup.msi VOICE_SERVICES_DOMAIN=domain1 CLEAR=1


since we are changing the voice service domain, am not sure why IM ability will go away. attaching the screenshot of jabber


1 Reply 1

Jaime Valencia
Hall of Fame Cisco Employee Hall of Fame Cisco Employee
Hall of Fame Cisco Employee
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers