[cisco-voip] Take incoming MGCP gateway out of production but keep up for testing?

[Wes Sisk]

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.

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.

/wes

On Wednesday, April 01, 2009 8:34:57 AM, Jacquie Manick 
<Jacquie.Manick at polarisind.com> wrote:
>
> Is there a simple way to take a gateway out of service in CallManager 
> (or router) that is MGCP?  It is on 3825 router with 3 other gateways.
>
> Yesterday had an issue with a DID circuit bouncing every five minutes 
> up/down.  We wanted to take it out of service for DID calls, but still 
> allow carrier to have it up for testing.  We did a shut on the 
> interface 0/0/0:23, shutting down the signaling port for ISDN - which 
> really shuts down the whole circuit, but a few moments later it came 
> back online because CallManager controls the circuit and expected it 
> online.
>
> Shutting down the controller for the interface doesn't allow the 
> carrier to test all the way through.
>
> Any help would be appreciated.  Jacquie Manick
>
> 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.
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090401/47777100/attachment.html>