<div>like Wes said, get the provider to re-route your DID down another PRI, then just remove the VGW from your Route Group.</div>
<div> </div>
<div>then you should be good</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Wed, Apr 1, 2009 at 5:42 AM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div text="#000000" bgcolor="#ffffff">your first challenge is that the carrier controls the inbound routing. if CM brings up the d-ch and b-ch the carrier will present calls inbound on that circuit. Best case scenario your carrier would switch the order of your circuits to make another circuit higher in the inbound hunt group.<br>
<br>otherwise you can reduce impact. use cm service parameter to busy out all but 1 b-ch on that ds1. This will allows 1 call inbound/outbound. Carrier will see the other 22 b-ch as out of service and hunt to the next circuit.<br>
<br>/wes
<div>
<div></div>
<div class="h5"><br><br>On Wednesday, April 01, 2009 8:34:57 AM, Jacquie Manick <a href="mailto:Jacquie.Manick@polarisind.com" target="_blank"><Jacquie.Manick@polarisind.com></a> wrote:<br></div></div>
<blockquote type="cite">
<div>
<div></div>
<div class="h5">
<p dir="ltr"><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="ltr"><span lang="en-us"></span><span lang="en-us"><font size="2">Is there a simple way to</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font size="2">take a gateway out of service in CallManager</font></span><span lang="en-us"></span><span lang="en-us"><font size="2"> (or router)</font></span><span lang="en-us"></span><span lang="en-us"><font size="2"> that is MGCP</font></span><span lang="en-us"></span><span lang="en-us"><font size="2">? It is on</font></span><span lang="en-us"></span><span lang="en-us"> <font size="2">3825 router</font></span><span lang="en-us"></span><span lang="en-us"><font size="2"> with 3 other gateways</font></span><span lang="en-us"></span><span lang="en-us"><font size="2">.</font></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="ltr"><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="ltr"><span lang="en-us"></span><span lang="en-us"><font size="2">Yesterday had an issue with a DID circuit bouncing every five minutes up/down. We wanted to take it out of</font></span><span lang="en-us"></span><span lang="en-us"> <font size="2">service</font></span><span lang="en-us"></span><span lang="en-us"><font size="2"> for DID calls, but</font></span><span lang="en-us"></span><span lang="en-us"><font size="2"> still allow carrier to have it up for testing. </font></span><span lang="en-us"></span><span lang="en-us"> <font size="2">We did a shut on the interface</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"></span><span lang="en-us"> <font color="#000000" size="2">0/0/0:23, shutting down the signaling port for ISDN</font></span><span lang="en-us"></span><span lang="en-us"><font color="#000000" size="2"> -</font></span><span lang="en-us"></span><span lang="en-us"><font color="#000000" size="2"> which really shuts down the whole circuit</font></span><span lang="en-us"></span><span lang="en-us"><font size="2">, but</font></span><span lang="en-us"></span><span lang="en-us"> <font size="2">a few moments later it came back online because CallManager controls the circuit and expected it online.</font></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="ltr"><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="ltr"><span lang="en-us"><font size="2">Shutting down the</font></span><span lang="en-us"></span><span lang="en-us"><font size="2"> controller for the interface doesn</font></span><span lang="en-us"></span><span lang="en-us"><font size="2">’</font></span><span lang="en-us"></span><span lang="en-us"><font size="2">t allow the carrier to test all the way through.</font></span><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="ltr"><span lang="en-us"></span><span lang="en-us"></span></p>
<p dir="ltr"><span lang="en-us"></span><span lang="en-us"></span><a name="12061b57b40500fc_"><span lang="en-us">Any help would be appreciated. </span></a><span lang="en-us"></span><span lang="en-us"> Jacquie Manick</span></p>
<p dir="ltr"><span lang="en-us"></span></p>CONFIDENTIAL: The information contained in this email communication is confidential information intended only for the use of the addressee. Unauthorized use, disclosure or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by return email and destroy all copies of this communication, including all attachments. </div>
</div><pre><hr width="90%" size="4">
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre></blockquote><br></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>