[cisco-voip] Use Gatekeeper for Tall Bypass

[Manoj Kalpage]

We use "0" for PSTN dialing. Can I still use translation patterns when use
"0" for outgoing call? I thought translation pattern is for incoming calls.

This is what I want to do.

Branch A Phone B extension : 75341212
Branch A Phone B DID : 0345671212

Branch C Phone D extension : 75351313
Branch C Phone D DID : 0457731313

When Branch A Phone B call to Branch C phone D via PSTN, phone B dial
00457731313.
I need these calls convert to extension number (75351313) and route through
VoIP.

Thanks,
MK
On Mon, Feb 22, 2010 at 4:07 AM, Ahmed Elnagar
<ahmed_elnagar at rayacorp.com>wrote:

>  I think yes it is better to use CM translation patterns for this, you can
> have one translation for each site that match DID range for remote sites and
> convert it to internal DN.
>
>
>
>   Best Regards;
>
>   Ahmed Elnagar
>
>   Senior Network PS Engineer
>
>
>
> [image: raya_corp_logo]IT Line of Business
>
>   RAYA Building El Motamiez District, 6th of October, Egypt
>
>
>
>   Mob: +2019-0016211
>
>   Phone: +202 3827 6000 Ext.2475
>
>   Website: www.rayacorp.com
>
>   E-mail: ahmed_elnagar at rayacorp.com
>
>  [image: ccie_voice_large.gif][image: ccvp_voice_large.gif]
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Patrick Fischer
> *Sent:* Sunday, February 21, 2010 7:25 PM
> *To:* Kalpage Manoj Perera
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Use Gatekeeper for Tall Bypass
>
>
>
> Hi MK
>
>
>
> There are several ways to solve this issue. Just think about translation
> patterns. But yes: a GK could also do the trick.
>
>
>
> Regards
>
> Patrick
>
> 2010/2/20 Kalpage Manoj Perera <manoj.kalpage at gmail.com>
>
> Hi All,
>
> We have central CUCM cluster and 50 SRST sites. We have announced users to
> use extension dialling when call between SRST sites and head office but they
> still call via PSTN. I am wonder we can deploy gatekeeper and automatically
> re-route PSTN call for SRST branch offices to VOIP. Is this possible with
> gatekeeper or any other piece of hardware ?
> Any information would be greatley appreciated.
>
> Thanks
> MK
>
> Sent from my iPhone
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> Disclaimer: NOTICE The information contained in this message is
> confidential and is intended for the addressee(s) only. If you have received
> this message in error or there are any problems please notify the originator
> immediately. The unauthorized use, disclosure, copying or alteration of this
> message is strictly forbidden. Raya will not be liable for direct, special,
> indirect or consequential damages arising from alteration of the contents of
> this message by a third party or as a result of any malicious code or virus
> being passed on. Views expressed in this communication are not necessarily
> those of Raya.If you have received this message in error, please notify the
> sender immediately by email, facsimile or telephone and return and/or
> destroy the original message.
>



-- 
Best Regards,
Manoj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100222/07b65efc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1363 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100222/07b65efc/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1806 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100222/07b65efc/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1801 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100222/07b65efc/attachment-0002.jpe>