cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4967
Views
0
Helpful
7
Replies

Cisco Jabber not showing the display name with no presence status

vinoth777
Level 1
Level 1

Hi All,

 

I am facing issue in my cisco jabber 12.1 and previous version 

 

The Jabber is not displaying the name of the user and instead it shows as "Display name" with no presence status.

 

And when i checked in show connection status it says presence status as "unknown" and Address as "CUP (IPV4)" instead of IM&P server IP Address.Attaching snip of the error status.

 

Post resetting the Jabber by deleting cache in local and roaming folder it resolves the issue but still the issue reoccurs in the Jabber.

 

 

Thanks,

Vinoth.

7 Replies 7

Hi @vinoth777,

 

 first of all, collect the logs of your Jabber ... take a look at How to Collect Logs for UC Application.

 

Best regards. 

Prashant Sharma
Cisco Employee
Cisco Employee

Hello Vinoth,

 

What is the IM&P version and type of service discovery you are using?

Do you have to reset the Jabber frequently to make it work?

Is it possible for you to share the Jabber PRT?

 

 

Regards,

Prassha3

 

Rate if you find this helpful

Hi Prashant,

 

1. we are using IM&P Version 11.5 SU3 and type of service discovery through UDS by pointing the Hostname by UC service.

2. yes. We are frequently reset the jabber as workaround temporarily.

3. Please let us know what kind of error you are looking for. Since we cannot share the complete logs in forums.

 

 

 

Regards,

Vinoth.

HARIS_HUSSAIN
VIP Alumni
VIP Alumni

As Suggested collec the PRT Logs and Also try to downgrade Jabber Client to 11.x version and test.

 

DaviRocK!
Level 1
Level 1
Trunk between CUCM and IMP is correctly configured?

Do you have uploaded jabber-config file?

JJMakowski
Level 1
Level 1

We had a case open with Cisco about this and the result of the case is that it is a Bug:

 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk59161/?rfs=iqvred

 

Our 11.9.3 users experience it.  The bug states it's fixed in 12.1.2.24692.

 

Regards,

Jim

Thanks!

Finally, Really Appreciated.