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

Configure: Forward a remote site main number to a greeting at head office

Hello all,

Here is IPT network information:

. Head office:
CCM v.4 server & Unity v.4 server->WAN->Remote site VGW, running MGCP

. Outside callers dial remote site main number, call flow is
carrier T1 CAS link ->Remote site VGW->Greeting->IP phone at remote site
(A call handler, which is created in Unity server at head office, will play the greeting)

My questoin is:
how can i configure VGW to make it work?

My thought is :
create translation rule on VGW-> main number replaced by the call handler extention number xxxx(eg. 1111), here how can the VGW be configured to forward the incoming call to 1111?

Thanks in advance,

Howard

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Configure: Forward a remote site main number to a greeting

Since the gateway is configured as a MGCP gateway all the configurations will be handled by the Call Manager server at the head office.  Basically all you need to do is create the AA in Unity and assign it an extension.  Then you can create a CTI Route Point that does a forward all to Voicemail.  The CTI Route Point should match the extension assigned to the AA in Unity.  This keeps you from having to configure a call route in unity.  If the extension doesn't match the DID coming into the remote site, then create a translation rule in Call Manager to translate the called number to the CTI Route Point that you created.

I hope this helps.

Please be sure to rate any post that is helpful....

4 REPLIES

Re: Configure: Forward a remote site main number to a greeting

Since the gateway is configured as a MGCP gateway all the configurations will be handled by the Call Manager server at the head office.  Basically all you need to do is create the AA in Unity and assign it an extension.  Then you can create a CTI Route Point that does a forward all to Voicemail.  The CTI Route Point should match the extension assigned to the AA in Unity.  This keeps you from having to configure a call route in unity.  If the extension doesn't match the DID coming into the remote site, then create a translation rule in Call Manager to translate the called number to the CTI Route Point that you created.

I hope this helps.

Please be sure to rate any post that is helpful....

New Member

Re: Configure: Forward a remote site main number to a greeting

Thanks for your reply, Kelvin.

As I mentioned, a call handler was created and extension 1111 was assigned to that call handler.

When the caller dials  remote site main number, (eg.123-4567) ,  the call flow is :   T1 link at remote site --> remote VGW--> Unity greeting rings.

In this case,  do I need to create a translation rule in CCM instead of VGW?   And that translation rule will translate 123-4567 to 1111, so that the incoming call will be forwarded to the call handler which is AA (automated attendant) in Unity, is this correct?

Thanks again,

Cisco Employee

Re: Configure: Forward a remote site main number to a greeting

That's correct. Translation rules are for H323 deployments. MGCP relies on CUCM for any kind of transformation.

You'll need a translation pattern to turn the DN into 1111 and also a forwarded call routing rule in Unity to catch those calls.

That, or modify the CH DN to match the phone number you're turning into 1111.

Unity uses the original called number to route calls, so you need to use any of the above.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Re: Configure: Forward a remote site main number to a greeting

Thanks Java. Finally it is working.....

The additional and last change I made is:

On CCM, --> remote voice gateway->Add remote site main#(123-34567) to E&M Port prefix DN

I have to made lots of testing calls and try everything I can , finally figure out the above solution. 

I am still wondering why the remote site main# has to added to prefix DN manually.  

Thanks in advance.

313
Views
5
Helpful
4
Replies