cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2114
Views
5
Helpful
1
Replies

Jabber 12.5 ignoring UC Service Profile

Hi,

 

CUCM 12.5 phone mode required (no IMP)

Jabber 12.5.

 

No DNS so cannot use service discovery. I've manually installed Jabber with the parameters (AUTHENTICATOR=CUCM,TFTP=X.X.X.X).

 

I've configured the UC service Profile to exclude WEBEX discovery, TelephonyOnlyDiscovery and TFTPServer1 and applied this to the Users UC Profile in CUCM.

 

But when I login I get this in the debug and its clearly ignoring the UC Service

 

Failed to download TFTP config. No TFTP server address available in server queue.
Excluded ServicesNone

 

What am I missing?

Rich

1 Accepted Solution

Accepted Solutions

OK after lots of pointless reading and mainly testing:

 

The UC Service parameters are only used if _cisco-uds is successfully resolved.

If you have a scenario where DNS Service Discovery isn't an option then the Jabber-config.xml file is your only option. Configure the parameters you need eg. (there are other parameters you can use too)

 

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
<Options>
<StartCallWithVideo>false</StartCallWithVideo>
</Options>
<Client>TelephonyOnlyDiscovery</Client>
<Voicemail>
<VoicemailPrimaryServer>192.168.1.4</VoicemailPrimaryServer>
<VoiceMailService_UseCredentialsFrom>phone</VoiceMailService_UseCredentialsFrom>
</Voicemail>
<Phone>
<TftpServer1>192.168.1.2</TftpServer1>
<TftpServer2>192.168.1.3</TftpServer2>
<CtiServer1>192.168.1.2</CtiServer1>
<CtiServer2>192.168.1.3</CtiServer2>
<CcmcipServer1>192.168.1.2</CcmcipServer1>
<CcmcipServer2>192.168.1.3</CcmcipServer2>
</Phone>
<Policies>
<ServiceDiscoveryExcludedServices>WEBEX</ServiceDiscoveryExcludedServices>
<EnableSIPURIDialing>true</EnableSIPURIDialing>
</Policies>
</config>

 

Upload that file to all CUCM nodes and restart TFTP services.

 

Then install Jabber using the following command:

 

msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 AUTHENTICATOR=CUCM TFTP=192.168.1.2

 

Boom

Go Warriors

View solution in original post

1 Reply 1

OK after lots of pointless reading and mainly testing:

 

The UC Service parameters are only used if _cisco-uds is successfully resolved.

If you have a scenario where DNS Service Discovery isn't an option then the Jabber-config.xml file is your only option. Configure the parameters you need eg. (there are other parameters you can use too)

 

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
<Options>
<StartCallWithVideo>false</StartCallWithVideo>
</Options>
<Client>TelephonyOnlyDiscovery</Client>
<Voicemail>
<VoicemailPrimaryServer>192.168.1.4</VoicemailPrimaryServer>
<VoiceMailService_UseCredentialsFrom>phone</VoiceMailService_UseCredentialsFrom>
</Voicemail>
<Phone>
<TftpServer1>192.168.1.2</TftpServer1>
<TftpServer2>192.168.1.3</TftpServer2>
<CtiServer1>192.168.1.2</CtiServer1>
<CtiServer2>192.168.1.3</CtiServer2>
<CcmcipServer1>192.168.1.2</CcmcipServer1>
<CcmcipServer2>192.168.1.3</CcmcipServer2>
</Phone>
<Policies>
<ServiceDiscoveryExcludedServices>WEBEX</ServiceDiscoveryExcludedServices>
<EnableSIPURIDialing>true</EnableSIPURIDialing>
</Policies>
</config>

 

Upload that file to all CUCM nodes and restart TFTP services.

 

Then install Jabber using the following command:

 

msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 AUTHENTICATOR=CUCM TFTP=192.168.1.2

 

Boom

Go Warriors

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: