Jabber Caller IDI number twice

[Pragash22]

Hi Guys

Jabber shows the caller id twice for internal calls, instead showing the name of the user. All the users in CUCM affected

Thanks and regards

Pragash

[Jonathan Schulenberg]

For an internal call from another user? What does the calling DN have for an Alerting and Display Name value? Also, does the calling number resolve to a user account in the Contact Source (ie LDAP or UDS), after accounting for Directory Lookup Rule transformations? If Jabber found a user account with this info it would supersede the Alerting/Display Name attributes.

[Pragash22]

Hi Jonathan

Thank you for your reply.

Yes for the internal calls. Each DN given a alerting name. I do see below on PRT logs.

2019-01-08 15:35:56,289 DEBUG [0x0000dbf8] [\core\sipstack\ccsip_platform_tcp.c(671)] [csf.sip-call-control] [sip_tcp_newmsg_to_spi] - SIP : sip_tcp_newmsg_to_spi : Sip message rcv: message=

2019-01-08 15:35:56,289 DEBUG [0x0000dbf8] [p\sipcc\core\sipstack\ccsip_debug.c(326)] [csf.sip-call-control] [platform_print_sip_msg] - sipio-recv<--- INVITE sip:b9dadb1f-ee2e-7e7f-af16-ef8637853aef@10.10.11.39:51429;transport=tcp SIP/2.0

Via: SIP/2.0/TCP 192.168.100.188:5060;branch=z9hG4bK1d0ecd7a5861c8

From: "XXXXX3555 XXXXX3555" <sip:00XXXXX3555@192.168.100.188>;tag=3910588~4afba2b6-afa4-6684-7b55-4aaf6722d387-19021274

To: <sip:3570@AA.BB.local>

Date: Tue, 08 Jan 2019 04:35:56 GMT

Call-ID: e2526380-c34128ac-19db3c-bc64a8c0@192.168.100.188

Supported: timer,resource-priority,replaces

Min-SE:  1800

User-Agent: Cisco-CUCM10.5

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence

Call-Info: <urn:x-cisco-remotecc:callinfo>; security= Unknown; orientation= from; gci= 1-2723284; isVoip; call-instance= 2

Send-Info: conference, x-cisco-conference

Alert-Info: <file://Bellcore-dr2/>

Remote-Party-ID: "XXXXX3555 XXXXX3555" <sip:XXXXX3555@192.168.100.188;x-cisco-callback-number=00XXXXX3555>;party=calling;screen=yes;privacy=off

Contact: <sip:00XXXXX3555@192.168.100.188:5060;transport=tcp>

Max-Forwards: 27

Content-Length: 0

[Jonathan Schulenberg]

The only time I have seen a number with an actual X in it was calls to voicemail when the Voicemail Profile had a longer mask on it than the calling/forwarding DN. In that instance the extra X characters were passed literally. Did this call pass through CUC for some reason?

[Pragash22]

Hi Jonathan

I guess I have misleaded by changing into XXXXX, change all XXXXX to 12345. I am sorry about that.

Kind regards

pragash