CLI Intermittent issue on CUBE router

[sarwarm123]

Hi Akon as you know, we recently configured CUBE (ip2ip) gateway for the new SIP link but caller-id is not working properly. It works for some outbound calls and does not work for some outbound calls.

I noticed a pattern when it CLI works and and when it doesn't work in the ccsip debug. I have attached ccsip messages debug results. Please help to figure out issue.

[Ayodeji Okanlawon]

Muhammad,

What is this ip address: 10.60.34.98 ? The calls that work with CLI present this IP address...

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[sarwarm123]

Aok,

10.60.34.98 is a CUBE WAN interface, I also noticed one thing more, the time CLI doesn't appear I see a Ringing message in debug

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.116.143.151:5060;branch=z9hG4bK50B1418
From: <44043>;tag=B6D0904-EC8
To: <07967999481>
Date: Sat, 30 Mar 2013 15:58:31 GMT
Call-ID: 810BF04D-988911E2-909E81CF-F82D39B1@10.116.143.151
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0

CDC-CUBE#
044223: Mar 30 15:58:38.540: //1358/A9CAF3000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.116.143.151:5060;branch=z9hG4bK50B1418
From: <44043>;tag=B6D0904-EC8
To: <07967999481>;tag=2875388~867df168-c5c9-4b90-8b3a-75c7400ce77b-44181198
Date: Sat, 30 Mar 2013 15:58:31 GMT
Call-ID: 810BF04D-988911E2-909E81CF-F82D39B1@10.116.143.151
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: <07967999481>
Remote-Party-ID: <07967999481>;party=called;screen=no;privacy=off
Contact: <07967999481>
Content-Length: 0

The time CLI works ok no Ringing message in debug BUT I can see session in progress

044110: Mar 30 15:55:31.563: //1345/3E8121000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.60.34.98:5060;received=10.60.34.98;branch=z9hG4bK4F9103D
From: <44043>;tag=B6A4930-21C1
To: <07967999481>
Call-ID: 15A42C59-988911E2-907A81CF-F82D39B1@10.60.34.98
CSeq: 101 INVITE
Timestamp: 1364658931
Content-Length: 0

044111: Mar 30 15:55:31.591: //1345/3E8121000001/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 183 Session Progress
Require: 100rel
Via: SIP/2.0/UDP 10.60.34.98:5060;received=10.60.34.98;branch=z9hG4bK4F9103D
RSeq: 1
To: <07967999481>;tag=3573647731-589353
From: <44043>;tag=B6A4930-21C1
Call-ID: 15A42C59-988911E2-907A81CF-F82D39B1@10.60.34.98
CSeq: 101 INVITE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <07967999481>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 208

[Ayodeji Okanlawon]

Muhammad,

The problem is because we dont have any bind commands configured. The challenge is that you have two different interfaces for sip traffic.

Lets try and configure bind commands on the WAN interface and test..

voice service voip

sip

bind all source-interface gig0/1 (replave gig0/1 with the wan interface)

Now do test calls  and send me debug ccsip messages...

Test both outbound and inbound calls

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[sarwarm123]

Aok,

As you said I have applied bind commands on the WAN interface but now I cannot make any calls and also I cannot get any ccsip debug from the router. I have also attached updated config

[sarwarm123]

I also tried to make inbound call which also doesn't work but I can collect ccsip messages debug. For outbound calls I don't see debug and calls fails also.

Please see attached debug for inbound calls

[sarwarm123]

Hi Aok,

CLI issue was happening because of matching incorrect dial-peer. When I did debug ccapi inout I was seeing working cli was matching correct outgoing to ITSP dial-peer, the time CLI was not displaying it was matching outgoing to CCM dial-peer.

After modified dial-peers more precisely issue has resolved. Bundle of thanks for your help mate.

Aok. I need another favour from you regards to voice translation rules

If you could guide me what translation rule would be correct for this

DDI 024760126XX needs to translate to 5 digit VOIP number 526XX

H323 gateway can do this by num-exp

num-exp  0247601.... 526..

How can I do same in SIP gateway using voice translation rule

Currernt Rule: 02476012665 is translated to 44043

rule 1 /^02476012665/ /44043/

[Ayodeji Okanlawon · Accepted solution]

Ok, happy to know its working. Have you removed the bind commands?

Here is the translation rule...You can dd this to your existing rule...Adjust the numbering accordingly..I mean rule 1 or rule 2, i have used rule 4 here

voice translation-rule 1

rule 4 /^0247601\(26..\)/ /5\1/

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[sarwarm123]

Hi Aok,

As usual you are star mate.

Yes I have removed bind commands. I also tried to use bind commands on individuals dial-peers, I mean outgoing dial-peer to CCUM bind with CUBE LAN interface and outgoing dial-peer to ITSP bind with CUBE WAN interface. I worked but not properly so I removed all bind commands

[Ayodeji Okanlawon]

Happy to be of help. Glad its all working for you.

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[sarwarm123]

Hi Aok,

Need your help, we just decided to block Caller ID for all of our users. I cannot use 141 as ITSP does not support this. They wanted us to modify SIP headers.

I have tried command clid strip pi-restrict all globally and on dial-peer leve but that doesn't work either. Will you please help me how can I restrict OUTGOING caller id through modification of SIP header

[Ayodeji Okanlawon]

We use remote party-id with this profile

voice class sip-profiles 1 (or 2 or anynumber)

request INVITE sip-header Remote-Party-ID modify "<>;party=calling;screen=no;privacy=off" "<>;party=calling;screen=no;privacy=full"

where X.X.X.X is the External interface of your CUBE facing the ITSP.

I observed that in your previous trace you have removed remote-party-id. You need to enable it for this profile to work. You then apply the profile in the outbound dial-peer to your ITSP

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[sarwarm123]

HI Aok,

Thanks for your reply, as you said I have applied the config. It Blocks CLI on the CUBE-1 but does not work on CUBE-2. Basically ITSP provided two links going to each data centers for the redundancy purpose.

As you said I have attached ccsip debug please have a look where the issue is. I can see in logs both SIP headers are modifying on the both CUBE routers but its BLOCK CLI on one router and doesn't BLOCK on second one

[Ayodeji Okanlawon]

Please post the config you used becuase your Remote-Party-ID header is not properly formatted.

Sent:

INVITE sip:02476016423@10.128.0.1:5060 SIP/2.0

Via: SIP/2.0/UDP 10.60.34.98:5060;branch=z9hG4bK10A1D54

Remote-Party-ID: <>;party=calling;screen=yes;privacy=full

It should be 

Remote-Party-ID: <42375>;party=calling;screen=yes;privacy=full

do you have the "<sip:\1@X.X.X.X>;party=calling;screen=no;privacy=full"

on the right hand side of the profile..NB the sip:\1

The second CUBE on the non working CLI has this

Remote-Party-ID: <>;party=calling;screen=yes;privacy=full

Is  10.60.34.106 the right ip address? the other one is using 10.60.34.98

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[sarwarm123]

Hi Aok,

1)     Is  10.60.34.106 the right ip address? the other one is using 10.60.34.98

Yes that correct this is a right ip address of CUBE WAN interface 10.60.34.98

#####################################################################################

CUBE-A - CLI BLOCK - Working

WAN Interface:10.60.34.98

voice class sip-profiles 3

request INVITE sip-header Remote-Party-ID modify "<>10.60.34.98>;party=calling;screen=yes;privacy=off" "<1>10.60.34.98>;party=calling;screen=yes;privacy=full"

Applied on Oubound Dial-Peer

################################################################################################

CUBE-B CLI Not Blocking - Not Working

WAN Interface: 10.60.34.106

voice class sip-profiles 3

request INVITE sip-header Remote-Party-ID modify  "<>10.60.34.98>;party=calling;screen=yes;privacy=off"  "<1>10.60.34.98>;party=calling;screen=yes;privacy=full"

Applied on Oubound Dial-Peer