<div dir="ltr">Well, you could simply create an LD H.323 pattern (1st and 2nd pref to pub and sub and 3rd to PSTN) and let CCM decide where to send the LD calls for TEHO... make a specific TEHO pattern for locally used toll bypass.<br>
<br><br><br>Jonathan<br><br><div class="gmail_quote">On Thu, Aug 21, 2008 at 9:12 PM, Carter, Bill <span dir="ltr"><<a href="mailto:bcarter@sentinel.com">bcarter@sentinel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p>Kind of a theoretical design question here. I'm
interested in the wisdom of the masses here.</p>
<p> </p>
<p>New CallManager Deployment</p>
<p style="margin-left: 38.25pt; text-indent: -0.25in;"><span style="font-family: Symbol;"><span>·<span>
</span></span></span>2 GWs at HQ</p>
<p style="margin-left: 38.25pt; text-indent: -0.25in;"><span style="font-family: Symbol;"><span>·<span>
</span></span></span>15 remote sites</p>
<p> </p>
<p>Requirements</p>
<p style="margin-left: 38.25pt; text-indent: -0.25in;"><span style="font-family: Symbol;"><span>·<span>
</span></span></span>SRST at all locations, requires H323
configurations at each site</p>
<p style="margin-left: 38.25pt; text-indent: -0.25in;"><span style="font-family: Symbol;"><span>·<span>
</span></span></span>In SRST mode, all locations should be able to
dial all other locations via 4-digit</p>
<p style="margin-left: 38.25pt; text-indent: -0.25in;"><span style="font-family: Symbol;"><span>·<span>
</span></span></span>Toll bypass Tail End Hop Off (each site is in a
different area code)</p>
<p> </p>
<p>Since SRST is required everywhere might as well have H323
gateways for each site. TEHO would normally require complex dial-plan on CallManager.
So I'm thinking H323 Gatekeeper would make this configuration much easier.
My questions center around the CallManager Dial Plan and its interaction with
Gatekeeper.</p>
<p> </p>
<p>Here is what I am thinking for the CM Dial-Plan Deployment</p>
<ul style="margin-top: 0in;" type="disc">
<li>I will create a H323
Gatekeeper/Gateway network</li>
<li>CallManager Trunk/GK to
the GK network</li>
<li>Site specific 911 PT and route
patterns pointing to local GWs (RL, RG, H323-GW)</li>
<li>Site specific 7-digit
route patterns normalized to 10-digit (RL, RG, GK)</li>
<li>General 11-digit (Toll
Free and LD) (RL, RG, GK)</li>
</ul>
<p> </p>
<p>Questions</p>
<ul style="margin-top: 0in;" type="disc">
<li>Should I create a CallManager
GK/Trunk to the gatekeeper</li>
<li>Should CallManager Dial-Plan
point to GK/Trunk (RP, RL, RG-GK)</li>
<li>Should CallManager Dial-Plan
point to GK/Trunk the H323 Gateways for redundancy (RP, RL, RG-GK/RG-H323</li>
<li>Basically, could my CM
dial-plan consist of site-specific 911 patterns and Local and LD patterns
point to GK</li>
</ul>
<p> </p>
<p>I look forward to the discussion... <span style="font-family: Wingdings;">J</span></p>
</div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>