[cisco-voip] PRIs using MGCP

[Jason Burns]

Part of this depends on the provider.

I've tried this with both SIP (on the GW) and MGCP (in CUCM as Eric
mentioned) controlled gateways with mixed results.

When the provider honors the busy status of your channel via the in / out
of service message it works great.

ATT in Atlanta does not honor the busy status unless you order that
specific service from them. You can set all your channels to busy and
they'll still send calls in if the D channel is up and they haven't logged
calls on those channels. It was a HUGE pain because we were trying to use
the SIP busyout keepalive function, but wound up having to use a script to
just take down the whole D-channel instead for inbound call failover.

Verify with 'show isdn status' and 'show isdn service'. If your channels
are in the busy state but you're still getting inbound calls then check
with your provider.

-Jason

On Fri, Apr 20, 2012 at 1:43 PM, Erick Wellnitz <ewellnitzvoip at gmail.com>wrote:

> It's only supposed to be for troubleshooting but look at 'change b-channel
> maintenance status' in CallManager service parameters
>
> On Fri, Apr 20, 2012 at 12:34 PM, Tim <bcchimp at gmail.com> wrote:
>
>>  I'm using quite a few PRIs via MGCP to CUCM.  I'm wondering if there's
>> a way to busy up the PRI channels so that they'll start using the other
>> PRIs on the other router.  Trying to reload one of my routers, but can't
>> stop the inbound calls from coming in on the certain PRIs.  I was thinking
>> it's possible, but maybe not.****
>>
>> ** **
>>
>> Thanks,****
>>
>> Tim****
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
> _______________________________________________
> 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/20120420/626da83b/attachment.html>