cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4325
Views
10
Helpful
5
Replies

CUBE +1 E.164 change header to drop +1

john boxold
Level 1
Level 1

Afternoon, everyone.

I have been trying to strip the e.164 numbers to just send 10 digits to the UCM.

I have a CUBE that is receiving +1 and 10 digits.I am looking to strip the =1 on the

I have configured translation rule that strips the +1. Rule 1 /.+1/ //. when I run the voice translation rule, the +1 is stripped. I apply the rule to a translation profile and apply to inbound dial-peer using incoming number.

The rules do not seem to apply and the debug s show calling and called with +1 and number.  I have tried to use a SIP Profile to strip out the +1 in the header.

voice class sip-profiles 1
 response ANY sip-header Allow-Header modify "UPDATE," ""
 request ANY sip-header From modify "ip:+1" "ip:

voice translation-rule 1
 rule 1 /\+1./ //
!
!
voice translation-profile IN
 translate calling 1
 translate called 1

If anyone can look at my configuration and provide any pointers i would appreciate it.

5 Replies 5

Deepak Mehta
VIP Alumni
VIP Alumni

Hi John,

I believe you just need to put the rule as below without a dot as dot is removing an extra digit.

rule 1 /\+1/ //

Also make sure you are applying this correct direction .thanks

Hi, Deepak.

Thanks, I tried the settings and I have adjusted the rule.

When I run a test voice translation-rule 1

the +1 is stripped.

I placed the rule in the following manner.

voice translation-profile IN
translate called 1
!
dial-peer voice 1000 voip
translation-profile incoming In
incoming number .

Running the following debugs:

debug voice ccapi inout

debug ccsip mess

debug voic dial-p

I can verify the gateway receives the call via SDP messages. I do not see that it looks for an outbound dial-peer.

To me this is something basic I am missing.

Hi John,

I can see translation profile "IN" is in caps and the one you have defined in dial-peer is using small letter "In". It has to match otherwise it wont take affect.

Also attach above debug's if still no go.thanks

Hi, Deepak.

I ended up preforming a reload of the gateway. The gateway began working correctly afterwards.

Good job and thank you for update.