Guest

Preview Tool

Cisco Bug: CSCvs56049 - DNA shows incorrect calling party transformation mask

Last Modified

Dec 27, 2019

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(2.14900.16)

Description (partial)

Symptom:
Mismatch between the calling party transformation selected according to the Dialed number analyzer and actual behaviour

Please refer to the example below  for better understanding:


++ There are two calling party transformations configured on CUCM with the following patterns
1) *641002
2) 1002
++ We make an outbound call with calling number 1002. The calling number is transformed at route pattern due to a calling party transformation mask prefix *64. So the calling party number now becomes *641002
++ In the DNA, I see that the calling party transformation *641002 is selected 
++ But the observed behaviour is that calling party transformation mask 1002 is selected
Please find below the configuration done in lab

Call Flow:

IP Phone >> CUCM1 >> SIP trunk >> CUCM2 >> IP Phone

Calling number: 1002
Called number 4444
CUCM1 configuration:
Route pattern: 4444
Prefix digits: *64
Under the SIP Trunk Outbound Calls, we have configured Calling party Transformation CSS as "Lab_Transformation_CSS" 
Lab_transformation_CSS has access to Partition Lab_transformation

We have the following calling party transformations created on CUCM1
Transformation mask 1 pattern: 1002 (Partition: Lab_transformation)  (Calling party transformation mask: 123)
Transformation mask 2 pattern: *641002 (Partition: Lab_transformation) (Calling party transformation mask: 456)
According to the Lab behaviour and customer environment behaviour, the transformation mask 123 is getting applied
According to Dialed number analyzer, the transformation mask 456 is getting applied 
Troubleshooting Performed: 
++ Recreated the same behaviour in lab
++ Log analysis from lab
 
++ Incoming invite from IP Phone 1002
06053911.002 |13:12:53.062 |AppInfo  |SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.106.88.252 on port 51094 index 35 with 1825 bytes:
[44195,NET]
INVITE sip:4444@192.168.100.220;user=phone SIP/2.0
Via: SIP/2.0/TCP 10.106.88.252:51094;branch=z9hG4bK4a147525
From: "1002" <sip:1002@192.168.100.220>;tag=b000b4d9e8d1387617a3d200-78956e3c
To: <sip:4444@192.168.100.220>
Call-ID: b000b4d9-e8d10029-79a2e30d-4c3cfbc9@10.106.88.252
Max-Forwards: 70
Session-ID: 1540351700105000a000b000b4d9e8d1;remote=00000000000000000000000000000000
Date: Tue, 17 Dec 2019 07:42:59 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CP8841/12.0.1
Contact: <sip:accbdb7e-939e-4ae8-b30d-568131283e75@10.106.88.252:51094;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEPB000B4D9E8D1"
Expires: 180
Accept: application/sdp
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "1002" <sip:1002@192.168.100.220>;party=calling;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
Recv-Info: conference
Recv-Info: x-cisco-conference
Content-Length: 553
Content-Type: application/sdp
Content-Disposition: session;handling=optional
v=0
o=Cisco-SIPUA 8924 0 IN IP4 10.106.88.252
s=SIP Call
b=AS:4064
t=0 0
m=audio 29188 RTP/AVP 114 9 124 0 8 116 18 101
c=IN IP4 10.106.88.252
b=TIAS:64000
a=rtpmap:114 opus/48000/2
a=fmtp:114 maxplaybackrate=16000;sprop-maxcapturerate=16000;maxaveragebitrate=64000;stereo=0;sprop-stereo=0;usedtx=0
a=rtpmap:9 G722/8000
a=rtpmap:124 ISAC/16000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv


++ Calling party transformation selection:

06053954.007 |13:12:53.066 |AppInfo  |SPROC  DATransformMatch - matchNumber [1002] transformCSSPkid [51e8b8f4-656f-921d-55f4-e96f47e075e0] transformationCss [Lab_transformation] patternUsage [15] paternNodeID [ad421745-1f8e-c90f-0b81-a3c4690726ab] OutpulsedNum.nd [123] tn  [0] pi [1] npi [0] isNonPreemptable [0]
06053954.008 |13:12:53.066 |AppInfo  |SIPCdpc(52) - LocalizeOutpulsedNumber: SIPCdpc on device 226trunk , CSS = 51e8b8f4-656f-921d-55f4-e96f47e075e0,useDevicePoolCgpnCss =0 AlternateCgpn(global)=1002  cgpn=123, cdpn=4444, mUpdateInstruction=3
 
 
++ Outgoing invite to CUCM2

06053980.001 |13:12:53.069 |AppInfo  |SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.106.88.226 on port 5060 index 38
[44197,NET]
INVITE sip:4444@10.106.88.226:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.100.220:5060;branch=z9hG4bKbb211ac6fc
From: <sip:123@192.168.100.220>;tag=14621~89abb3e9-c225-4745-aac9-4442c10bf54e-32475893
To: <sip:4444@10.106.88.226>
Date: Tue, 17 Dec 2019 07:42:53 GMT
Call-ID: d3dd0200-df8186fd-34-dc64a8c0@192.168.100.220
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:192.168.100.220:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 1540351700105000a000b000b4d9e8d1;remote=00000000000000000000000000000000
Cisco-Guid: 3554476544-0000065536-0000000033-3697584320
Session-Expires:  1800
P-Asserted-Identity: <sip:123@192.168.100.220>
Remote-Party-ID: <sip:123@192.168.100.220>;party=calling;screen=yes;privacy=off
Contact: <sip:123@192.168.100.220:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="SEPB000B4D9E8D1"
Max-Forwards: 69
Content-Length: 0

++ As you can see in the outgoing invite, the calling number is changed to 123

############ DNA #################
Results Summary
Calling Party Information
Calling Party = *641002
Partition =
Device CSS =
Line CSS =
AAR Group Name =
AAR CSS =
Transformed Calling Party = 456
Dialed Digits = 4444
Match Result = RouteThisPattern
Matched Pattern Information
Pattern = 4444
Partition =
Time Schedule =
Called Party Number = 4444
Time Zone = Etc/GMT
Call Classification = OffNet
InterDigit Timeout = NO
Device Override = Disabled
Outside Dial Tone = NO
Call Flow
Route Pattern :Pattern= 4444
Positional Match List = 4444
DialPlan =
Route Filter
Filter Name =
Filter Clause =
Require Forced Authorization Code = No
Authorization Level = 0
Require Client Matter Code = No
Call Classification =
PreTransform Calling Party Number = 1002
PreTransform Called Party Number = 4444
Calling Party Transformations
External Phone Number Mask = NO
Calling Party Mask =
Prefix = *64
CallingLineId Presentation = Default
CallingName Presentation = Default
Calling Party Number = *641002
ConnectedParty Transformations
ConnectedLineId Presentation = Default
ConnectedName Presentation = Default
Called Party Transformations
Called Party Mask =
Discard Digits Instruction = None
Prefix =
Called Number = 4444
Device :Type= SIPTrunk
Transformed Calling Party = 456
End Device Name = 226trunk
PortNumber =
Device Status = UnKnown
AAR Group Name =
AAR Calling Search Space =
AAR Prefix Digits =
Call Classification = Use System Default
Calling Party Selection = Originator
CallingLineId Presentation = Default
CallerID DN =
Alternate Matches
Note: Information Not Available

Conditions:
++ Found on CUCM version 10.5 SU4
++ Other vresions also affected
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.