cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1985
Views
0
Helpful
1
Replies

Cisco Jabber And Unity Connection Issue

jsmcniel88
Level 4
Level 4

Good Day,

Currently running CUCM 8.5, CUPS 8.6 and Cisco Jabber for OSX 8.6.2.

I have a issue with Cisco Jabber for OSX connecting to my unity connection server (8.5). For whatever reason it will intermittently connect and disconnect.

Looking at the diagnostics shows:

 Voicemail Server

    Unity Address:         172.29.4.17

    Port:             80

    Protocol:             HTTP

    Message Store:         172.29.4.17

    Port:             --

    Protocol:             TCP

    User ID:            jmcniel

    Secure messaging:     Not available

    Connection type:    Unsecure

    Status:             Connecting

Everything else as far as CUCM, Presence, CTI and Meeting Place is connected so this is that last piece of the pie.

Here is the odd thing. Windows CUPC connects just fine with no issues.

Has anyone ran into this before or know where I can check to dig into the root cause?

Thanks

1 Accepted Solution

Accepted Solutions

johammon
Cisco Employee
Cisco Employee

We were able to get this corrected by changing the LDAP Authentication port on Unity Connection to 3268.  The root cause is that the default LDAP authentication port on both CUCM and UConn is 389.  This port is notoriously slow with authentication.  This is why we were seeing the "Connecting" message because we were waiting for a response on the authentication attempt.  Changing this port to 3268 is faster for authentication, which allowed us to connect.(Restart of IMAP is needed after this change)

View solution in original post

1 Reply 1

johammon
Cisco Employee
Cisco Employee

We were able to get this corrected by changing the LDAP Authentication port on Unity Connection to 3268.  The root cause is that the default LDAP authentication port on both CUCM and UConn is 389.  This port is notoriously slow with authentication.  This is why we were seeing the "Connecting" message because we were waiting for a response on the authentication attempt.  Changing this port to 3268 is faster for authentication, which allowed us to connect.(Restart of IMAP is needed after this change)

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: