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

Fri May 20 08:41:25 EDT 2011

Go to service parameters  select the call manager and select ciso
callmanager service

Select ADVANCED

Change B-Channel Maintenance Status 1:  This parameter allows Cisco
CallManager to change individual B-Channel maintenance status for PRI and
CAS interfaces in real time for troubleshooting.
Input Format:
Device Name = B-channel Maintenance Status
Example:
S0/DS1-0 at SDA123456789ABC = 0000 1111 0000 0000 0000 0001 (24 bits for T1.
Channel number begins with 1 to 24 from left to right. In the case of PRI,
the last bit specifies the D-Channel, which does not get affected. In this
example, the 5th through 8th B-Channels are out of service.)
or,
S1/DS1-0 at DLS2-CM136-VG200-2.SELSIUSCMLAB.CISCO.COM = 0000 0000 0000 0000
0000 0000 1111 1111 (32 bits for E1. B-Channel number begins with 1 to 32
from left to right. The 16th channel specifies the D-Channel. The last bit
does not affect any channel. In this example, the 25th through 31st channels
are marked out of service.)
Explanation:
The Device Name as specified in the Gateway Configuration page in Cisco
CallManager Administration MUST exactly match the gateway name that this
field specifies. To avoid any manual inputting mistake, copy the Device Name
from Cisco CallManager Administration and paste it into this service
parameter. "=" is mandatory and unique to distinguish the Device Name and
B-Channel Maintenance Status fields.
BCHANNEL MAINTENANCE STATUS = xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx 
Where x can be: 
0 -- In service 
1 -- Graceful out of service (Change channel status until active call ends
if an active call exists on that channel.) 
2 -- Forceful out of service (Tear down active call first; then, change
channel status immediately if an active call exists on that channel.)
Because values other than 0,1, or 2 are invalid, the system ignores them.
Make sure that the total number of 'x' is either 24 for T1 or 32 for E1. Any
other invalid length or mismatch (for example, 24 for E1) gets treated as
error, and no action gets taken for that device. 
SPACE: Optional.
The spaces between device name and "=", between '=' and BCHANNEL MAINTENANCE
STATUS, and between x and x, are all optional. You cannot use any space
inside the DEVICE NAME field. 
PRI Specific:
To use this feature, the Enable status poll check box must be checked on the
PRI Gateway Configuration window. If it is not, you need to check the check
box, click Update, and reset the gateway for the service parameter change to
take effect.

Randy Homyk
CCIE Voice #14584
Homyk Systems
mailto:  rhomyk at homyk.net
mailto:  rhomyk at bellsouth.net
Phone: +786-269-5175
Fax: +305-258-9156
Mobile: 786-269-5175
www.homyk.net

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Paul
Sent: Friday, May 20, 2011 8:03 AM
To: Peter Pauly; ccieid1ot
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Limiting outbound ISDN calls to a limited set of
channels?

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

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip