cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5869
Views
0
Helpful
2
Replies

Cisco Jabber for Windows 9.6.1 - Installer switches

hanlykent
Beginner
Beginner


Hi All,

I am attempting to use the _cisco-uds SRV record to auto discover services in Jabber for Windows 9.6.1 using CUCM/IM&P 9.1.1


Our internal DNS servers are on a internal AD domain (example.local) which is different to our SIP (sipdomain.com.au) or Email domain (company.com.au) Based on the Cisco Jabber for Windows 9.6 installation and configuration documentation, I believe I should be using the SERVICES_DOMAIN installer switch

"Use the SERVICES_DOMAIN installer switch to specify the value of the domain where DNS records reside if you wish users to bypass the email screen during the first login of a fresh installation".

I uninstalled a previous Cisco Jabber for Windows 9.2.4 on the PC, therefore I used the "CLEAR" installer switch to remove any previous bootstrap information that might have been on the PC

"CLEAR=1

Specifies if the client overrides any existing bootstrap file from previous installations. The client saves the arguments and values you set during installation to a bootstrapfile.The client then loads settings from the bootstrap file at startup"

"If you do not specify CLEAR, the client checks for existing bootstrap files during installation

  • If no bootstrap file exists, the client creates a bootstrap fileduring installation
  • If a bootstrap file exists,the client does not override that bootstrap file and preserves the existing settings".

Opened a command prompt

Changed the prompt to the location of the jabber msi file and performed the following command:

msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 SERVICES_DOMAIN=example.local

After installation and launch of Jabber for Windows, I receive "Cannot communicate with the server" on the Jabber for Windows client

I ran wireshark during the launch of Jabber for Windows and I see ONLY the following DNS queries to the name server:

  • _cisco-uds._tcp.sipdomain.com.au
  • _cisco-uds._tcp.cisco-internal.sipdomain.com.au

The SIP domain, which I suspect is cached from the previous install is being used instead of the SERVICES domain.

Am I doing something wrong?

Any assistance is appreciated.

NSlookup seems to show the SRV is setup correct.

>nslookup
Default Server:  nameserver.example.local
Address:  10.1.1.10

> set type=srv
> _cisco-uds._tcp.example.local

_cisco-uds._tcp.example.local  SRV service location:

          priority       = 1

          weight         = 5

          port           = 8443

          svr hostname   = cucm2.example.local

_cisco-uds._tcp.internal.local  SRV service location:

          priority       = 2

          weight         = 20

          port           = 8443

          svr hostname   = cucm3.example.local

_cisco-uds._tcp.internal.local  SRV service location:

          priority       = 6

          weight         = 30

          port           = 8443

          svr hostname   = cucm1.example.local