<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
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<br>
<br>
On Wednesday, April 01, 2009 8:34:57 AM, Jacquie Manick
<a class="moz-txt-link-rfc2396E" href="mailto:Jacquie.Manick@polarisind.com"><Jacquie.Manick@polarisind.com></a> wrote:<br>
<blockquote
cite="mid:23149_1238589295_n31CYpSv012738_F4F02F327FDB004A89D41950B639A1260358CEB4@MPL1ITSEVS002.polarisind.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator"
content="MS Exchange Server version 6.5.7654.12">
<title>Take incoming MGCP gateway out of production but keep up for
testing?</title>
<!-- Converted from text/rtf format -->
<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
moz-do-not-send="true" name=""><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.
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>