Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Prefix calling party - CUCM 9.1, SIP gateways

Having issues prefixing 9, 91, etc. on inbound calling parties from our gateways into CUCM.  Until recently, we had it setup under the service parameters to use 9 for 'unknown' numbers under the device - phone section.  Due to some other issues, we had to remove that, but left the 91 for national, 9011 for international, but the prefix stopped showing up.  The gateways have PRIs coming in from PSTN, and are SIP to CUCM.

 

I'm wondering how others have addressed this issue -- transform patterns, translations on the gateway, translations in CUCM, other ideas...?  I'm looking for the best solution with the least amount of admin overhead (aka risk of breaking other stuff in the process...) but one that can give my users the best experience.

 

Thanks all

 

SJ

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Silver

With SIP there is no way to

With SIP there is no way to distinguish local vs. LD vs International calls as the SIP message does not include that into, so your best bet would be to prefix 91 only for example at the SIP trunk level in CUCM under incoming section.

6 REPLIES
Hall of Fame Super Silver

With SIP there is no way to

With SIP there is no way to distinguish local vs. LD vs International calls as the SIP message does not include that into, so your best bet would be to prefix 91 only for example at the SIP trunk level in CUCM under incoming section.

New Member

Thanks Chris.  Kind of

Thanks Chris.  Kind of thought that might be the case...one thing i thought about trying was to modify the calling party on the VoIP dial-peers going to CM...have to brush up on my RegEx, though.  Am I wasting time with that?  Or could it be viable?

New Member

You could do something along

You could do something along these lines inside the ingress gateway. SIP won't preserve the call types, but you can get the correct prefixes on the ANI for callback (assuming the PRI provider is actually sending the correct call type).

voice translation-rule 999
 rule 1 /\(.\)*/ /9011\0/ type international international
 rule 2 /\(.\)*/ /91\0/ type subscriber subscriber
 rule 3 /\(.\)*/ /91\0/ type national national
voice translation-profile PrefixInbound
 translate calling 999
dial-peer voice 1 pots
  incoming called-number .
  direct-inward-dial
  translation-profile incoming PrefixInbound
  trunkgroup PSTN

 

 

New Member

Awesome.  I'll try it out.  I

Awesome.  I'll try it out.  I'm finding little differences in how things were setup between my gateways by my vendor...some of them have translations on the voice-port, some in the DPs, etc.

 

Thanks Nick!

New Member

No problem man, hope it helps

No problem man, hope it helps a little bit. I've always been a fan of putting translations on the dial-peers... I'm not sure why, it just stuck with me.  

 

One that burned me a couple of weeks ago was when the translation was placed on a trunk group as well as several other places. I removed all of them, except the trunk group, and it kept showing up wrong when the call arrived. Note to self: check trunk group because some vendor probably applied a TP there :)

New Member

Ah!  That sucks...I agree on

Ah!  That sucks...I agree on putting them on the DPs...one of those things that I learned initially and it just worked better.  I'll have to make a note to check my trunk groups too.

205
Views
0
Helpful
6
Replies
CreatePlease to create content