updateDisplayInfoAndSendMsg: Change in caller info detected in CcNotifyReq

Jon Clark1 · ‎01-13-2016

Deji or anyone...

Our client is complaining that every call from their new Cluster in Canada shows the name "Diane D" as the caller ID. They had several users test.No one knows who Diane D is.

Call Flow USER 1 -> CUCM 10.5(CLUSTER 1 IN CANADA) -> SIP TRUNK ->ITSP -> PSTN -> MGCP PRI -> CUCMBE 8.6(CLUSTER 2 IN BOSTON) -> USER 2 (SIP 8811 PHONE)

I GRABBED TRACES FROM CLUSTER 2 BOSTON CLUSTER.

CUCMBE = 172.23.180.10

MGCP PRI VGW = 172.23.180.1

INVITE sip:b14f14ec-e14e-b9b2-30de-db12b452f5ff@172.23.180.71:51014;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.23.180.10:5060;branch=z9hG4bK297167029acee
From: <sip:81647.......@172.23.180.10>;tag=5750907~9cb37824-c52c-47cb-b26c-3e25a55681c2-26180178
To: <sip:4919@172.23.180.10>
Date: Tue, 12 Jan 2016 19:36:29 GMT
Call-ID: c568e200-695155bd-db16-ab417ac@172.23.180.10
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM8.6
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= NotAuthenticated; orientation= from; gci= 1-16555529; call-instance= 1
Send-Info: conference, x-cisco-conference
Alert-Info: <file://Bellcore-dr2/>
Remote-Party-ID: <sip:81647.......@172.23.180.10;x-cisco-callback-number=81647.......>;party=calling;screen=yes;privacy=off
Contact: <sip:81647.......@172.23.180.10:5060;transport=tcp>
Max-Forwards: 70
Content-Length: 0

SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.23.180.10:5060;branch=z9hG4bK297167029acee
From: <sip:81647.......@172.23.180.10>;tag=5750907~9cb37824-c52c-47cb-b26c-3e25a55681c2-26180178
To: <sip:4919@172.23.180.10>
Call-ID: c568e200-695155bd-db16-ab417ac@172.23.180.10
Date: Tue, 12 Jan 2016 19:36:38 GMT
CSeq: 101 INVITE
Server: Cisco-CP8811/10.2.2
Contact: <sip:b14f14ec-e14e-b9b2-30de-db12b452f5ff@172.23.180.71:51014;transport=tcp>
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0

SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 172.23.180.10:5060;branch=z9hG4bK297167029acee
From: <sip:81647.......@172.23.180.10>;tag=5750907~9cb37824-c52c-47cb-b26c-3e25a55681c2-26180178
To: <sip:4919@172.23.180.10>;tag=88908d736f2f9a0e53d88691-54182af3
Call-ID: c568e200-695155bd-db16-ab417ac@172.23.180.10
Date: Tue, 12 Jan 2016 19:36:38 GMT
CSeq: 101 INVITE
Server: Cisco-CP8811/10.2.2
Contact: <sip:b14f14ec-e14e-b9b2-30de-db12b452f5ff@172.23.180.71:51014;transport=tcp>
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "JOHN DOE" <sip:4919@172.23.180.10>;party=called;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0

*********************** HERE'S WHAT TAKES PLACE JUST BEFORE THE UPDATE.

(Is this coming from the Telco,VGW, OR ORIGINATING CALLER?)

14:36:29.382 |NAMEQSIGASN -
StructuredOutput:value CallingNameRose ::= callingNameInvoke :
{
    invokeID 1,
    operationValue localValue : 0,
    argument name : namePresentationAllowed : namePresentationAllowedSimple : '44696E6773204469616E6520202020'H
}|*^*^*

14:36:29.382 |Cdcc - (1397957) - dumpSecureStatus - sideA=(cap=1,1, media=0,0, feature=0,0), sideB=(cap=1,1 media=0,0, feature=0,0)|1,100,160,1.480922^172.23.180.1^*

14:36:29.382 |Cdcc - (1397957) - dumpSecureStatus - sideA=(cap=1,1, media=0,0, feature=0,0), sideB=(cap=1,1 media=0,0, feature=0,0)|1,100,160,1.480922^172.23.180.1^*

14:36:29.382 |LineCdpc(1398118): -dispatchToAllDevices-, sigName=CcNotifyReq, device=SEP88908D736F2F|1,100,160,1.480922^172.23.180.1^*
14:36:29.382 |LineCdpc(1398118): -dispatchToAllDevices-, sigName=CcNotifyReq, device=SEP88908D7374A0|1,100,160,1.480922^172.23.180.1^*
14:36:29.383 |//SIP/SIPCdpc(1,74,19117)/ci=26180178/ccbId=5750907/scbId=0/handTOMutCallPreActiveCcNotifyReq: mediaStatus=1, mRel1xxRequired=0, media_info_present = false|1,100,160,1.480922^172.23.180.1^*

********** FIRST TIME DIANE D SHOWS UP IN THE TRACES
14:36:29.383 |//SIP/SIPCdpc(1,74,19117)/ci=26180178/ccbId=5750907/scbId=0/processLocalIdentityInfo: name=D Diane    ,localCnName=;NamePi=0,localCnNamPi=1;|1,100,160,1.480922^172.23.180.1^*

14:36:29.383 |//SIP/SIPCdpc(1,74,19117)/ci=26180178/ccbId=5750907/scbId=0/processLocalIdentityInfo: identityFlag=[Changed:- Name;Name PI;]|1,100,160,1.480922^172.23.180.1^*

14:36:29.383 |//SIP/SIPCdpc(1,74,19117)/ci=26180178/ccbId=5750907/scbId=0/updateDisplayInfoAndSendMsg: Change in caller info detected in CcNotifyReq bitmask 80000000 |1,100,160,1.480922^172.23.180.1^*

14:36:29.383 |//SIP/SIPCdpc(1,74,19117)/ci=26180178/ccbId=5750907/scbId=0/processOutgoingUserAgentHeader: UAPT: passthrough value is not present|1,100,160,1.480922^172.23.180.1^*

14:36:29.383 |//SIP/SIPCdpc(1,74,19117)/ci=26180178/ccbId=5750907/scbId=0/updateDisplayInfoAndSendMsg: Updating cached copy of contact header [FROM ccNotifyReq] = []|1,100,160,1.480922^172.23.180.1^*

14:36:29.383 |//SIP/SIPCdpc(1,74,19117)/ci=26180178/ccbId=5750907/scbId=0/updateDisplayInfoAndSendMsg: handle CcNotifyReq, Sending msgType 4 for call_info_present 0x80000000 newprecedence_info_present 0x0 callinfoChanged 0 identityCngFlag 0x18 mSendSecurityStatus 0, mSendGeoloc[0], mRemoteTransparencyInfo is Null, userAgentChanged=0|1,100,160,1.480922^172.23.180.1

************************ "DIANE D" BECOMES REMOTE PARTY ID ******************
UPDATE sip:b14f14ec-e14e-b9b2-30de-db12b452f5ff@172.23.180.71:51014;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.23.180.10:5060;branch=z9hG4bK2971822642392
From: <sip:81647.......@172.23.180.10>;tag=5750907~9cb37824-c52c-47cb-b26c-3e25a55681c2-26180178
To: <sip:4919@172.23.180.10>;tag=88908d736f2f9a0e53d88691-54182af3
Date: Tue, 12 Jan 2016 19:36:29 GMT
Call-ID: c568e200-695155bd-db16-ab417ac@172.23.180.10
User-Agent: Cisco-CUCM8.6
Max-Forwards: 70
Supported: timer,resource-priority,replaces
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 102 UPDATE
Call-Info: <urn:x-cisco-remotecc:callinfo>; security= NotAuthenticated; orientation= from; gci= 1-16555529; call-instance= 1
Remote-Party-ID: "D Diane    " <sip:81647.......@172.23.180.10>;party=calling;screen=yes;privacy=off
Contact: <sip:81647.......@172.23.180.10:5060;transport=tcp>
Content-Length: 0

Thanks
JG

Jon Clark1 · ‎01-13-2016

****** DIGIT ANALYSIS

Jon Clark1 · ‎01-13-2016

*********** JUST BEFORE DIGIT ANALYSIS (FQCN IS BLANK)

14:36:29.198 |Digit Analysis: star_DaReq: Matching Legacy Numeric, digits=4919|1,100,160,1.480921^172.23.180.1^*
14:36:29.198 |Digit Analysis: getDaRes data: daRes.ssType=[0] Intercept DAMR.sstype=[16777222], TPcount=[0], DAMR.NotifyCount=[1], DaRes.NotifyCount=[0]|1,100,160,1.480921^172.23.180.1^*
14:36:29.198 |Digit analysis: match(pi="2", fqcn="", cn="81647726....",plv="5", pss="All_DN_PT:HQ_Lcl_PT", TodFilteredPss="All_DN_PT:HQ_Lcl_PT", dd="4919",dac="0")|1,100,160,1.480921^172.23.180.1^*
14:36:29.198 |Digit analysis: analysis results|1,100,160,1.480921^172.23.180.1^*
14:36:29.198 ||PretransformCallingPartyNumber=81647726....

Mohammed al Baqari · ‎01-14-2016

Hi,

Can you check the SIP trunk and MGCP gateway on both clusters. Make sure that CallerID filed is empty.

Jon Clark1 · ‎01-14-2016

Mohammed,

Thank you for responding. I attached a screenshot of the calling party's SIP trunk. Can you explain what those fields mean?

Where should I look next?

Thanks!

JG

Jon Clark1 · ‎01-14-2016

Update: Our in house team suggested to the client they open a Trouble Ticket with the PRI provider.

We checked the Canada SIP Trunk and found that CUCM was passing the correct P Asserted ID to the SIP CUBE.

We believe the Telco is responsible for the UPDATE method after the 180 Ringing. I will keep everyone up to date with part 2. THE TELCO WAR...

Jon Clark1 · ‎01-15-2016

The SIP trunk caller ID field is empty but i dont see this field on the MGCP page. Do you have the exact name? I tried Cntrl + F for CallerID but no matches.

Thanks