cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1309
Views
0
Helpful
5
Replies

Need help to find out how the called numbers from a jabber client is altered by the CUCM

Difan Zhao
Level 5
Level 5

Happy holidays!

I am testing Jabber client. I gave it DN of 1111. I am calling number 75874343162. the first 7 is number to call external. I have PR 7.@ and I do predot discard. I use local route-group and I have a SIP trunk to an ISR router for external calls. 

When I run debug ccsip message on the ISR router, I see the to number was prepended with + sign and the 7 was not removed.

From: <sip:1111@10.92.3.225>;tag=2619673~5c58f295-18b8-4630-9958-741cab756838-28798998
To: <sip:+75874343162@172.19.254.16>

 

However it does not happen when I make call from existing video endpoints like SX80 which has 

From: <sip:4001@10.92.3.225>;tag=2609725~5c58f295-18b8-4630-9958-741cab756838-28798957
To: <sip:5874343162@172.19.254.16>

 

They should be routed the same way.

 

I also did an analysis on the jabber client. Everything looks normal to me. Please see the attached picture for details. I just don't know what altered the numbers that would add the +sign and keep the 7...

 

Thanks

Difan

 

 

1 Accepted Solution

Accepted Solutions

Difan Zhao
Level 5
Level 5

So had to open up a TAC case and it turned out to be Application Dial Rules. I never knew that existed...

View solution in original post

5 Replies 5

Hi,

Start with debug ccsip mess on the voice gateway and see what is the
received called number. This will help to identify if the problem with cucm
or voice gateway.

If cucm is the problem look at dna to make sure that both calls are
following the same path.

Next check if you are hitting a transformation pattern with the video
endpoint which you aren't hitting with jabber

Hi Mohammed,  I did include the debug message in my post. It is with the + sign and with the 7

Yes I also did the DNA and I see the exactly the same result between the jabber and the sx80. I used a diff tool. the only difference is the calling number which is 1111 vs 4001. Please see the attached picture for the DNA details.

As per the DNA, there is no transformation pattern being hit except the predot discard that was configured in the pattern 7.@. 

 

Here is the texts from the DNA

Results Summary
Calling Party Information
Calling Party = 1111
Partition = on-cluster_PT
Device CSS = device-nanp-outgoing_CSS
Line CSS = line-restriction-nanp-none_CSS
AAR Group Name =
AAR CSS =
Dialed Digits = 75874343162
Match Result = RouteThisPattern
Matched Pattern Information
Pattern = 7.@
Partition = pstn-nanp_PT
Time Schedule =
Called Party Number = 5874343162
Time Zone = America/Denver
End Device = pstn-local_RL
Call Classification = OffNet
InterDigit Timeout = NO
Device Override = Disabled
Outside Dial Tone = NO
Call Flow
Route Pattern :Pattern= 7.@
Positional Match List = 587:434:3162
DialPlan = North American Numbering Plan
Route Filter
Filter Name =
Filter Clause =
Require Forced Authorization Code = No
Authorization Level = 0
Require Client Matter Code = No
Call Classification = OffNet
PreTransform Calling Party Number = 1111
PreTransform Called Party Number = 75874343162
Calling Party Transformations
External Phone Number Mask = NO
Calling Party Mask =
Prefix =
CallingLineId Presentation = Default
CallingName Presentation = Default
Calling Party Number = 1111
ConnectedParty Transformations
ConnectedLineId Presentation = Default
ConnectedName Presentation = Default
Called Party Transformations
Called Party Mask =
Discard Digits Instruction = PreDot
Prefix =
Called Number = 5874343162
Route List :Route List Name= pstn-local_RL
RouteGroup :RouteGroup Name= PSTN Local Route Group (calgary-temp-RG)
PreTransform Calling Party Number = 1111
PreTransform Called Party Number = 75874343162
Calling Party Transformations
External Phone Number Mask = Default
Calling Party Mask =
Prefix =
Calling Party Number = 1111
Called Party Transformations
Called Party Mask =
Discard Digits Instructions =
Prefix =
Called Number = 75874343162
Device :Type= SIPTrunk
End Device Name = vrt01-03difan
PortNumber = 0
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
Partition :Name= pstn-nanp_PT
Pattern
Pattern = 7.@
Pattern = (7)([2-9][0-9][02-9])([2-9][0-9][0-9])([0-9][0-9][0-9][0-9])
Tags List = ACCESS-CODE:LOCAL-AREA-CODE:OFFICE-CODE:SUBSCRIBER
Pattern Type = National
Call Classification = OffNet
CallManager Device Type = AccessDevice
PatternPrecedenceLevel = PlDefault
PatternRouteClass = RouteClassDefault

 

On your local route group assigned to device pool can you make sure that
all transformations are either empty or set to default (dont select on/off)
for any setting. Same thing on route list.

Why dont you use predot:nanp

Both the SX80 and the Jabber are in the same device pool. I just checked and I don't see anywhere I can specify transformation in the DP or in the RG... Where do I see the setting?

I don't see Predot:nanp.. I just tried predot 10-10-Dialing and I got the same result...

Thanks,

Difan Zhao
Level 5
Level 5

So had to open up a TAC case and it turned out to be Application Dial Rules. I never knew that existed...