DID is not working in incoming calls

Sanjay Bishnoi · ‎10-11-2016

Hello,

I need your help as I have one setup CUCM>CUBE>ISP.

phone DID is not working in incoming calls and all calls delivered on pilot number but in outgoing calls all DID working fine.

same we discussed with ISP team and they suggested that my CUBE router sending pilot number instead of DID number towards to CUCM.

DID number is - 6253XXX

Extension - 87003XXX

i have made to dial peer one from ISP and second is towards CUCM

dial-peer voice 1 voip
description **INBOUND FROM ISP**
session protocol sipv2
session transport udp
incoming called-number .
voice-class codec 1
voice-class sip profiles 2
voice-class sip copy-list 1
voice-class sip bind control source-interface GigabitEthernet0/0/2
voice-class sip bind media source-interface GigabitEthernet0/0/2
dtmf-relay rtp-nte sip-notify

dial-peer voice 3 voip
description ***Outbound to CUCM Publisher***
translation-profile outgoing incoming
destination-pattern 6253...$
session protocol sipv2
session target ipv4:X.X.X.X
session transport udp
voice-class sip profiles 1
voice-class sip options-keepalive profile 1
voice-class sip copy-list 1
dtmf-relay rtp-nte sip-notify
no vad

Aseem Anand · ‎10-11-2016

Hi,

Can you send us the running configuration and collect the output if the following debugs

Debug ccssip messages

Debug voice ccapi input

Aseem

Sanjay Bishnoi · ‎10-11-2016

Hi Aseem,

Thanks for update,

Please find attached required logs.

Sanjay Bishnoi · ‎10-12-2016

Hello,

Can anyone help me out of this.

Aseem Anand · ‎10-12-2016

Hi Sanjay,

CUBE is sending 87003600 to CUCM. What number should the CUBE be sending to CUCM?

Sent: 
INVITE sip:87003600@10.13.84.3:5060 SIP/2.0
Via: SIP/2.0/UDP 10.13.84.9:5060;branch=z9hG4bK9AC1DB0
From: "09873305718" <sip:9873305718@10.13.84.9>;tag=7E79999-1660
To: <sip:87003600@10.13.84.3>
Date: Wed, 12 Oct 2016 04:54:08 GMT
Call-ID: BEA490EF-8F6E11E6-A315AB3A-9FE6AA9@10.13.84.9
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3198376095-2406355430-2735713082-0167668393
User-Agent: Cisco-SIPGateway/IOS-15.5.3.S2
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1476248048
Contact: <sip:9873305718@10.13.84.9:5060>
Call-Info: <sip:10.13.84.9:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 7
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 262

v=0
o=CiscoSystemsSIP-GW-UserAgent 4464 593 IN IP4 10.13.84.9
s=SIP Call
c=IN IP4 10.13.84.9
t=0 0
m=audio 8176 RTP/AVP 18 101
c=IN IP4 10.13.84.9
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Sanjay Bishnoi · ‎10-12-2016

Hi Robert/Aseem,

thanks for update

I have changed the suggested changes but when i interchange translation profile incoming incoming in dial peer 1 then my incoming calls are not working .

cube router sending only one number 87003600 and it should be send according to translation rule :-

voice translation-rule 20
rule 1 /^.*$3...$$/ /8700\1/

whether any number received fro ISP this should be converted according last 4 digit.

extension range 87002600-3799

DID - 1246253600-3799

kindly suggest where can I change to deliver calls according to translating rule 20.

screen shot also attached.

Aseem Anand · ‎10-12-2016

Hi,

Your translation rule is correct. As per the debugs you sent earlier the provider is sending 6253600 to the CUBE.

Received: 
INVITE sip:6253600@10.50.128.58:5060 SIP/2.0

CUBE further changes the called number to 87003600 based on the translation rule 20. Can you tell me the exact number you dialed for the testing? It could be that the provider is always sending out 6253600 to the CUBE. I would suggest you to make another call and collect debug ccsip messages and debug voice ccapi inout. Also send me the calling and called number.

Aseem

Sanjay Bishnoi · ‎10-12-2016

Hi Aseem,

thanks for update,

Please find attached required logs.

calling number 9873305718

called number is - 1246253601

Aseem Anand · ‎10-12-2016

This seems to be a service provider issue. The number you are getting from the device with IP address 10.50.128.2 is always 62536000, no matter what you dial. What is this device? Is this a device within your setup or its with the provider? If its with the provider then you can simply share the SIP messages with them and have them checked.

*Oct 12 14:38:41.779: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
INVITE sip:6253600@10.50.128.58:5060 SIP/2.0
Via: SIP/2.0/UDP 10.50.128.2:5060;branch=z9hG4bK91bc8c8a53d64bde81ebtaN0
To: "1246253601"<sip:1246253601@10.50.128.2>
From: "09873305718"<sip:9873305718@10.50.128.2>;tag=aa2c106-KtDn2f5496803
Call-ID: 2a922f54969-0003-0100@10.162.193.6
CSeq: 21137 INVITE
Max-Forwards: 8
Contact: <sip:9873305718@10.50.128.2>
Supported: 100rel
User-Agent: ZTE Softswitch/1.0.0
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,REFER,NOTIFY,SUBSCRIBE,PRACK,UPDATE
Content-Type: application/sdp
Content-Length: 178

v=0
o=ZTE 352 6600 IN IP4 10.50.128.2
s=phone-call
c=IN IP4 10.50.128.2
t=0 0
m=audio 52752 RTP/AVP 8 0 18 97
a=rtpmap:97 telephone-event/8000
a=fmtp:97 0-15
a=ptime:20

Aseem

(Please rate if useful)

Sanjay Bishnoi · ‎10-12-2016

I have already discussed with them they are saying we are sending DID number (1236253601) in TO sip header with the IP 10.50.128.2

 "1246253601"<sip:1246253601@10.50.128.2>

and 10.50.128.58 is the customer site IP provided by SP

they are also saying that your CUBE router sending only 87003600 towards CUCM whatever we dialed DID number.

and also confirm that should it received DID number 1246253601 with 10.50.128.58 as it is provided by SP customer site IP Address.

Aseem Anand · ‎10-12-2016

Well, in SIP the calls are not routed based on what you specify in to field but it depends on the SIP URI which clearly as per the SIP messages is coming as "INVITE sip:6253600@10.50.128.58:5060 SIP/2.0". Can you ask them to check why the SIP URI is always 6253600 when call is coming from 10.50.128.2?

Aseem

Vivek Batra · ‎10-12-2016

Friends,

Just adding a point here. Service provider is sending Pilot Number in Request-URI and DID number in To field. By default, CUBE/CUCM fetches the called number from Req-URI however that is not the case here since we are getting DID number in To field. This is common implementation with many service providers.

With reference to following document, you need to use SIP profiles to get the correct DID number for further call routing.

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/copy_sip_headers.pdf

I can see that you have already added those commands in the config but somehow that is not working. These commands are bit new hence you need to check carefully about their operation.

request INVITE peer-header sip TO copy "sip:(.*)@" u01

The above command should copy the To field and store in the variable.

request INVITE sip-header SIP-Req-URI modify ".*@(.*)" "INVITE sip:\u01@\1"

The above command should copy the To field to Req-URI if I understand correctly hence Req-URI will become what you got in To field viz 1246253601. This should be the number passed to outbound call leg.

If my understanding with respect to above command is correct, now you should have outbound dial peer (towards CUCM) matching actual DID range viz 1246253600-3799. Further to this, apply translation profile to outbound dial peer to convert DID number to extension range 87002600-3799.

PS: Remove voice class sip-copylist 1 command form inbound dial peer as I don't see any reason to pass To field to outbound dial peer in this particular case.

- Vivek

Robert Shaw · ‎10-12-2016

Hi Sanjay,

It looks like your Dial-Peer 7 is incorrectly set for the Translation-profile. You have,

Translation-Profile outgoing incoming

Normally this would be set on the inbound Dial-Peer from the ISP, in your case Dial-peer 1.

Also the syntax is

Translation-Profile direction profile-name

So for you should be - Translation-Profile incoming incoming

Try removing this line from Dial-Peer 7 and add it correctly to Dial-Peer 1.

Thanks

Rob