[cisco-voip] Limiting outbound ISDN calls to a limited set of channels?

[Paul]

partial PRI with MGCP isn't supported.

just use H.323 and chop up the PRI into separate channels that way.


----- Original Message -----
From: Peter Pauly <ppauly at gmail.com>
To: ccieid1ot <ccieid1ot at gmail.com>
Cc: cisco-voip at puck.nether.net
Sent: Friday, May 20, 2011 3:38 AM
Subject: Re: [cisco-voip] Limiting outbound ISDN calls to a limited set of channels?

When I change the controller to your recommendation and save the
config, and then powercycle the gateway, the config goes back to 1-24.
Very strange. I assume that's because CallManager is "in charge" with
MGCP? If that's the case, how do I limit the channels in CallManager
(7.1.5)?


On Tue, May 17, 2011 at 11:46 AM, ccieid1ot <ccieid1ot at gmail.com> wrote:
> T1 0/0/0
> Pri-group time 18-23 service mgcp
>
> Try that.
>
> duy
> ccie #27737 voice
>
> tmobile g2
>
> On May 17, 2011 6:54 AM, "Peter Pauly" <ppauly at gmail.com> wrote:
>> We have a new IVR type server from a vendor that both receives calls
>> from CallManager and makes calls on an ISDN trunk (internal, no
>> telco). Think of it as both an IVR and a dialer. For example:
>>
>> Channels 1-6 - receive calls from CallManager
>> Channels 7-17 - Unused
>> Channels 18-23 send calls to CallManager
>>
>>
>> Our problem is CallManager is attempting to send calls to all 23
>> channels, when only 6 channels are really available to receive calls.
>> Can I limit calls that originate from CallManager to a subset of
>> channels while still having the other channels active to receive
>> calls?
>> _______________________________________________
>> 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