Digit prefix for Outgoing called number on CUCM with MGCP gateway

[m1xed0s]

Hey,

I have some trouble understanding this: How to do Digit prefix for Outgoing called number on CUCM with MGCP gateway?

My scenarior is:

There is a inter-cluster setup between our CUCM (DN 2XXX) and sister company CUCM(DN 3XXX) via SIP trunk and failover to PSTN using route list/route group. Both sites have MGCP gateways. We manually defined 3XXX parttern in our CUCM and pointed to the redundant route list.

If Inter-cluster trunk failed, call from 2XXX to 3XXX should be re-routed to PSTN via MGCP Gateway. However how should I OR where should I do digit prefix for called number? What should I prefix, 91560123 OR 1560123? (I think there is no need for the '9' with MGCP)...

I can not find a place on CUCM v8.6 (related to MGCP gateway) to define the prefix for outgoing called number...

Please advise.

/S

[William Bell]

Shuai,

I would do it at the RL/RG level. For example:

SisterCompany_RL

(1) Route Group 1: SisterCompany_RG   (ICT to Sister Company)

(2) Route Group 2: PSTN_RG  (MGCP gateway to PSTN)

If you go to the route list (SisterCompany_RL), you will see hyperlinks at the bottom of the page for each of the route groups. Select the PSTN_RG. You will see options to perform Calling and Called Party transformations. You will see a field for prefixing called party information. You can use that to specify the digit string that your PSTN carrier expects.

HTH

-Bill
(b) http://ucguerrilla.com
(t) @ucguerrilla

Please remember to rate helpful responses and identify helpful or correct answers.

[m1xed0s]

Thanks, that is pretty much the same as our setup now and can not believe I missed the transformation mask and prefix digits option on that page...

One last thing: should I prefix 91560123 or just 1560123? I think 9 is not required for MGCP gateway setup but I am not sure.

[William Bell]

You have to send the carrier what they expect to see. In my experience, the only time I have ever had to send the off net prefix (e.g. "9") in the DNIS is when the carrier was offering a Centrex service. That was a unique situation.

So, I'd say that you most likely only need to prefix 1560123.

HTH

-Bill
(b) http://ucguerrilla.com
(t) @ucguerrilla

Please remember to rate helpful responses and identify helpful or correct answers.

[m1xed0s]

Thanks for the thought.

But Correct me if I am wrong: the reason I think access code 9 is not needed is because of the MGCP gateway setup. If we had h323 gateways instead of MGCP gateways, I would configure 91560123 as the called number prefix. So H323 gateway knows how to match the dial-peer to route outgoing calls.

Since Our setup is using MGCP gateway and CUCM controls the T1 interface directly, I think access code 9 is not needed.

[William Bell]

Shuai,

You are not wrong. I am merely saying that the digits you present to the MGCP gateway should match what the carrier expects to see. If they don't want to see the "9" then don't send it.

I agree that your carrier most likely doesn't want to see the "9". I don't have enough information about how your trunk is configured to give you a definitive "YES".

It is easy enough to test for yourself. You are most likely using that PRI for other calls. Check to see what you are sending to the carrier for those calls and then you will have your answer.

HTH

-Bill
(b) http://ucguerrilla.com
(t) @ucguerrilla

Please remember to rate helpful responses and identify helpful or correct answers.

[mahmoodmkl]

Hi Willaim,

Actually i was also looking for the above solution and have the similar doubts as Shuai has.

Regarding using the calling/called party transformation and prefixing the digits.

I want to know whether the transforamtion is performed after the call routing decision or before.

Moreover i want to know the significance of gateway configuration page in CUCM.

Thanks

[m1xed0s]

The translate happens before call routing engine and transformation happens after the routing decision.

The significant digit is a field on the gateway/gateway endpoint configure page, especially the mgcp gateway.