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

New IM&P and Jabber deployment, getting "Cannot communicate with the server"

jasonnash1
Level 1
Level 1

I recently migrated our UC system from 8.6 to 11.5 and that went well enough.

We had not been using CUP or IM&P before, so just installed IM&P Publisher server, so we can start using Jabber clients. And eventually I'll add our VCS/Expressway servers for VPN-less phone access.

I've read the Cisco deployment guides, watched YouTube videos, and more. I think I'm doing everything I need to do. But for days I'm getting stuck with an error when trying to login to the Jabber client, "Cannot communicate with the server".

At one point I was able to successfully login with Jabber, but couldn't make outbound calls. While trying to solve that problem I must have done something, because now I can't login at all.

I'm trying to login to Jabber with advanced settings, Account Type CUCM, Login server manually set to my CUCM Publisher. Username is my ID@domain name (matches IM&P > Presence > Settings > Advanced Configuration > Default Domain). It seems to be authenticating correctly, because if I put in a wrong username or password I get a different error telling me I used the wrong username or password. 

I created a lab environment with a CUCM and IMP server and created a basic setup and performed the same IMP and Jabber setup and ran into the same error (no DNS/LDAP in the lab environment)

Below are the configuration setups I went through for the CUCM and IMP servers in our production environment. I did configure the SRV records on our DNS server for .cisco-uds (pointing to CUCM Publisher) and .cuplogin (pointing to IMP Publisher).

CUCM Setup
- Create SIP Trunk Security Profile
-- CUCM > System > Security > SIP Trunk Security Profile
--- Name: CM-IMP Trunk Profile
--- Accept presence, Accept out-of-dialog, Accept unsolicited, Accept replaces
- Create SIP Trunk
-- CUCM > Device > Trunk
--- SIP Trunk, SIP, None
--- Name: CM-IMP-SIP-Trunk
--- Device Pool: Default
--- Inbound Calls: check Redirecting Diversion Header Delivery - Inbound
--- Outbound Calls: check Redirecting Diversion Header Delivery - Outbound
--- Destination: XXX.XX.XX.27
--- SIP Trunk Security Profile: CM-IMP Trunk Profile
--- SIP Profile: Standard SIP Profile
- Create UC Services
-- CUCM > User Management > User Settings > UC Service
--- IM and Presence
---- Host Name/IP Address: XXX.XX.XX.27
--- Directory
---- Host Name/IP Address: XXX.XX.XX.23
--- CTI
---- Host Name/IP Address: XXX.XX.XX.10
---- Host Name/IP Address: XXX.XX.XX.20
--- Voicemail
---- Host Name/IP Address: XXX.XX.XX.21
---- Host Name/IP Address: XXX.XX.XX.22
- Create Service Profile
-- CUCM > User Management > User Settings > Service Profile
--- Name: Jabber Service Profile
--- Make this the default service profile for the system
--- Select Voicemail Profiles
--- Select LDAP Profile
---- Username: phoenix\um
---- Password
---- Search Base 1: ou=Domain Users,dc=phx,dc=ndchealth,dc=com
--- Select IM and Presence Profile
--- Select CTI Profiles
- Setup User
-- CUCM > User Management > End User
--- Service Settings: Enable User for Unified CM IM and P
--- Select UC Service Profile: Jabber Service Profile
--- Device Information: Associate Jabber CSF device with user
--- Permissions Information: Confirm user in Standard CCM End Users and Standard CTI Enabled
- Setup CSF Device
-- CUCM > Device > Phone
--- Product Type: Cisco Unified Client Service Framework
--- Owner: Associate with User
--- Digest User: Associate with User
- Setup Extension
-- CUCM > Device > Phone > CSF Device > Line
--- Users Associated with Line: Associate with User

IM&P Setup
- Enable Services
-- IMP (CUCMIMP Serviceability) > Tools Service Activation
--- Select CUCMIMP Server
---- Activate All Services
- Set CUCM IM and Presence Publish Trunk
-- IMP > Presence > Standard Configuration
--- CUCM IM and Presence Publish Trunk: CM-IMP-SIP-Trunk
- Add Presence Gateway
-- IMP > Presence > Gateways
--- Presence Gateway Type: CUCM
--- Description: Gateway to CUCM
--- Presence Gateway: XXX.XX.XX.10
- Set Preferred Proxy Listener
-- IMP > Presence > Routing > Settings
--- Preferred Proxy Listener: Default Cisco SIP Proxy TCP Listener
- Set TFTP Servers
-- IMP > Application > Client Settings
--- Primary TFTP Server: XXX.XX.XX.10
--- Backup TFTP Server: XXX.XX.XX.20
- Create CCMCIP Profile
-- IMP > Application > CCMCIP Profile
--- Name CCMCIP Profile
--- Primary CCMCIP Host: XXX.XX.XX.10
--- Backup CCMCIP Host: XXX.XX.XX.20
--- Server Certificate Verification: Any Certificate
--- Make this the default CCMCIP Profile for the system
--- Add Users to Profile


CUCM Publisher = XXX.XX.XX.10
CUCM Subscriber = XXX.XX.XX.20
CUC Publisher = XXX.XX.XX.21
CUC Subscriber = XXX.XX.XX.22
Domain Controller = XXX.XX.XX.23
IM&P Publisher = XXX.XX.XX.27

2 Replies 2

Hi,

try to login and immediately after failure navigate to  C:\Users\######\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs and upload jabber.log

Deepak Rawat
Cisco Employee
Cisco Employee

I am assuming that you have not configured any DNS / Domain name for your CM server. If this is correct can you please check how have you defined CM in CM Administration >> System >> Server. If by any chance you have done it using just the hostname then please change it to IP Address or preferably FQDN if you have configured DNS for your CM servers. Rest as Mohammed said, please reset your Cisco Jabber and delete the Jabber folder from both the below locations, recreate the issue and provide jabber.log file:

C:\Users\######\AppData\Local\Cisco\Unified Communications\

C:\Users\######\AppData\Roaming\Cisco\Unified Communications\

Also, when you enter the userid@domain name does it change just to the userid or not. If it is changing to userid and then you are getting the error message that means Auto discovery is working fine and issue is with Jabber registration and is most likely between CM and Jabber client. If it stays on userid@domain name only that means auto Discovery itself is not working

Regards

Deepak