How do I change the call 'type' from international to national

[evanrichards]

I have a call manger 4.0 setup. The gateways are MGCP on Cisco 2800 routers.

The switch type is NI2. When I try to make outbound international calls the call fails. Time Warner says it is because I need to send them 'national' instead of 'international' type calls on an NI2 connected PRI. All of my call manager settings are set to 'national.' Is there a way on the 2800 to force calls to be tagged as national, even if they are dialed with a 011 and are intended to go international? I've searched through all of the isdn config information I can find and don't see the answer here.

[fred.s.mollenkopf]

I have never tried this with MGCP but the Voice-Translation rule allows you to change the ISDN type. You can try applying the corresponding profile to the MGCP dial-peer though I don't know how it would like it. Again I've never used this like this but you can have multiple rules but unsure how you would apply it for a various range of dial patterns unless I did it in a lab.

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a0080325e8e.shtml

Please rate any helpful posts

Thanks

Fred

[evanrichards]

Related to a problem I had a few months ago, I was trying to block incoming calls on an MGCP gateway with translation rules and profile. It ended up that this can't be done on MGCP, but it does work on H323.

[keithpotter]

Evan

I have successfully make INTL calls on a MGCP Gateway. Some carriers require you send 011, some do not. Have you tried stripping 011 from the call? My route patterns look like 9.011! and 9.011!#, stripping Pre-DOT unless I am using AT&T. At that point I strip 011

Keith

[evanrichards]

The Time Warner tier 2 tech as adamant that I send the entire digit string, including 011, but that it be tagged as 'national.'

[keithpotter]

Are you sending this to a PBX or directly to the carrier?

[evanrichards]

carrier

[keithpotter]

Try stripping 011 from the call. Are you sending this to AT&T or a different carrier. If you have a pots line from the same carrier try dialing a INTL from it. This carrier you are using, is it the carrier for INTL calls or do you PIC a different carrier.

[noelger]

On your serial PRI interface, try something like the following:

interface Serial0/1/0:23

no ip address

isdn switch-type primary-ni

isdn incoming-voice voice

isdn map address 011* plan national type national

isdn bind-l3 ccm-manager

Other settings that sometimes work depending upon carrier are:

isdn map address 011* plan unknown type unknown

You can turn on Q931 debugs and see the reject reason where their switch is barking at you. Sometimes you just have to play with it until you hit the right combination.

If this helps, please rate this post.

Thanks,

Neal

[evanrichards]

After add this command:

interface Serial0/0/0:23

no ip address

no ip proxy-arp

no logging event link-status

isdn switch-type primary-ni

isdn incoming-voice voice

>>>isdn map address 011* plan national type national<<<

isdn bind-l3 ccm-manager

isdn send-alerting

no cdp enable

I still get the same error. The router is still trying to send international.

Here's the debug:

Aug 18 18:12:24: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0112

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Calling Party Number i = 0x2181, '4804672770'

Plan:ISDN, Type:National

Called Party Number i = 0x91, '0118704421234'

Plan:ISDN, Type:International

Aug 18 18:12:25: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8112

Cause i = 0x809C - Invalid number format (incomplete number)

[jamtran]

In CallManager, MGCP Gateway Configuration, Call Routing Information, Outbound Calls,

change the following to UNKNOWN (instead of Cisco CallManager):

1. Called party IE number type unknown*

2. Called Numbering Plan*

Good luck,

James Tran

[voipis4me]

I agree with James. I've seen this before and what James is suggesting was the fix. Here is a good doc for looking up q931 cause codes:

http://www.cisco.com/en/US/customer/tech/tk801/tk379/technologies_tech_note09186a008012e95f.shtml