Mike (sorry, missed to copy the list on first try), You are missing one option, which is the one I like most.
For almost all situations, I would go about using Calling Party Transformations and Called Party Transformations. Since these are device specific, you would make a Called Party Transformation that would be used only by the H323 gateway, and there prepend a 9. Then, on the gateway, you would stick with just one set of dial-peers which are the same used for SRST. On Sun, Mar 21, 2010 at 2:39 PM, Mike Brooks <[email protected]> wrote: > Just want to know how most would handle this type of scenario. It appears > there are multiple ways to configure this. > > > 9.[2-9]XXXXXX -> Standard Local RL (must strip predot because HQ is mgcp > gw) > > *HQ Device Pool:* > Standard Local Route Group: HQ-MGCP-RG > > *BR1 Device Pool:* > Standard Local Route Group: BR1-H323-RG > > > If either an HQ or BR1 phone makes a local call 9.[2-9]XXXXXX we must strip > the 9, regardless of which gateway it goes to because HQs standard local > route group is an MGCP gateway. > > So on the BR1-H323 gateway you have 2 options: > > 1. make 2 sets of dial-peers with a leading "9" (for SRST) and without a > leading "9". > > 2. on the inbound voip dial-peer preprend a "9" to the called number using > a translation pattern. > > > Which option seems to be the best choice and why ? Are there any other > options ? > > Thank you, > > Mike Brooks > CCIE#16027 (R&S) > > > > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
