cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

239
Views
0
Helpful
4
Replies
Highlighted
Participant

Calling Party Number disappearing

Hello all,

 

today I encountered a strange issue which I haven't seen before. Inbound calls coming from the PSTN (SIP trunk via a CUBE) lose the calling party number.

 

The setup

 

Provider - CUBE - CUCM (11.5su2 or 5, have to check)

 

The CUBE traces show that the calling party number is present (in from and PAI fields). The CUCM traces shows the same when the call goes to the phone (7841). Let's say we call a DDI. The translation patterns adds a 0 as prefix and translates the caled party to the internal extension. The phone displays this (calling party 0612345678, internal extension 5004):

 

0612345678

0

 

It should display:

 

0612345678

00612345678

 

The customer is using MiaRec and the software only registers 0 as the calling party.

 

The SDL trace says this:

 

36192116.002 |12:25:51.713 |AppInfo |SIPStationCdfc: CcSetupReq - unicodeConnectedUnicodeDisplayName='' asciiConnectedDisplayName='0612345678'
36192116.003 |12:25:51.713 |AppInfo |SIPStationCdfc: CcSetupReq - unicodeCallingPartyName='' asciiCallingPartyName='0612345678' callingParty='0' cgIP=192.168.252.253 unicodeCalledPartyName='John Doe' asciiCalledPartyName='John Doe' calledParty='5004'

 

I'm a bit baffled because the setup is pretty straight forward. The trunk is not doing any digit manipulation that happens only on the translation pattern. This the invite going to the phone:

 

INVITE sip:5d735fd0-89dd-9424-0bc1-064ee5a518a9@192.168.2.105:51622;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.0.23:5060;branch=z9hG4bK10c1e1285c8ac3
From: "0612345678" <sip:0@192.168.0.23>;tag=2239913~fcbb960e-a802-4954-8961-0674a88e8ef8-31645632
To: <sip:5004@cmp1>
Date: Wed, 05 Jun 2019 10:25:51 GMT
Call-ID: 49742700-cf7198af-83c42-1700a8c0@192.168.0.23
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
Call-Info: <urn:x-cisco-remotecc:callinfo>; security= Unknown; orientation= from; gci= 1-2202897; isVoip; call-instance= 1
Send-Info: conference, x-cisco-conference
Alert-Info: <file://Bellcore-dr2/>
Session-ID: 21228926047f961b28a2870ab2239912;remote=00000000000000000000000000000000
Remote-Party-ID: "0612345678" <sip:0@192.168.0.23;x-cisco-callback-number=0>;party=calling;screen=yes;privacy=off
Contact: <sip:0@192.168.0.23:5060;transport=tcp>
Max-Forwards: 27
Content-Length: 0

 

As far as I can see all seems right. Going to dig further tomorrow and open a TAC case.

 

I've change the External phone maks settings to all possible combinations on the translation pattern. Also the calling line ID setting has been changed several times.

 

 

I was wondering if anyone encountered this strange behavior.

 

With kind regards,

 

Marcel Tempelman.

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Participant

Re: Calling Party Number disappearing

Problem solved. Looking back it was quite obvious but I'd like to share it anyway.

 

I was looking through the SDL trace and I found this:

36192083.017 |12:25:51.710 |AppInfo |DbMobility: getMatchedRemDest starts: cnumber = @customername.ispname.nl
36192083.018 |12:25:51.710 |AppInfo |DbMobility SelectByDestination: no matching RemDestDynamic record exists for remdest [@customername.ispname.nl]
36192083.019 |12:25:51.710 |AppInfo |DbMobility: can't find remdest @customername.ispname.nl in map
36192083.020 |12:25:51.710 |AppInfo |DbMobility: remdest with uri = @customername.ispname.nl not foun

 

I was expecting to see 0612345678@customername.ispname.nl

 

So I gave the (CUCM) SIP trace a second loop and found this:

 

From: "0612345678" <sip:customername.ispname.nl>;tag=5E68BA84-249C

 

Wait a sec this should be : <sip:0612345678@customername.ispname.nl>. The ISP side of the trace had the correct header so it should be something that's happening on the CUBE. And this was what was causing the problem:

 

A misconfigured translation-rule

 

Translation-profile SIP-to-CUCM

 translate calling 1501

!

voice translation-rule 1501
rule 1 /\+31/ /0/
rule 2 /\+/ /00/
rule 15 /.*/ //

!

Dial-peer 100

 translation-profile outgoing SIP-to-CUCM

!

Rule 15 was wiping the calling party id.....

 

And now I need coffee...

 

With kind regards,

 

Marcel Tempelman.

 

View solution in original post

4 REPLIES 4
Participant

Re: Calling Party Number disappearing

Problem solved. Looking back it was quite obvious but I'd like to share it anyway.

 

I was looking through the SDL trace and I found this:

36192083.017 |12:25:51.710 |AppInfo |DbMobility: getMatchedRemDest starts: cnumber = @customername.ispname.nl
36192083.018 |12:25:51.710 |AppInfo |DbMobility SelectByDestination: no matching RemDestDynamic record exists for remdest [@customername.ispname.nl]
36192083.019 |12:25:51.710 |AppInfo |DbMobility: can't find remdest @customername.ispname.nl in map
36192083.020 |12:25:51.710 |AppInfo |DbMobility: remdest with uri = @customername.ispname.nl not foun

 

I was expecting to see 0612345678@customername.ispname.nl

 

So I gave the (CUCM) SIP trace a second loop and found this:

 

From: "0612345678" <sip:customername.ispname.nl>;tag=5E68BA84-249C

 

Wait a sec this should be : <sip:0612345678@customername.ispname.nl>. The ISP side of the trace had the correct header so it should be something that's happening on the CUBE. And this was what was causing the problem:

 

A misconfigured translation-rule

 

Translation-profile SIP-to-CUCM

 translate calling 1501

!

voice translation-rule 1501
rule 1 /\+31/ /0/
rule 2 /\+/ /00/
rule 15 /.*/ //

!

Dial-peer 100

 translation-profile outgoing SIP-to-CUCM

!

Rule 15 was wiping the calling party id.....

 

And now I need coffee...

 

With kind regards,

 

Marcel Tempelman.

 

View solution in original post

VIP Advisor

Re: Calling Party Number disappearing

Do you mean that the phone is show double zero instead of single zero at
the beginning. Why don't you use DNA to confirm what is happening in cucm
Participant

Re: Calling Party Number disappearing

Hello Mohammed,

 

DNA would have told me everything is ok because the CUCM part was configured right, the CUBE was stripping the caller ID.

 

With kind regards,

 

Marcel Tempelman.

VIP Advisor

Re: Calling Party Number disappearing

So is it fixed now?
CreatePlease to create content
Content for Community-Ad
FusionCharts will render here