[cisco-voip] Catalyst 6608 - Configuring channels not in service
Ortiz, Carlos
CORTIZ at broward.org
Wed Jul 13 08:52:04 EDT 2005
Does this mean you can do this on 5 different PRI's at a time?
________________________________
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Wednesday, July 13, 2005 8:36 AM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Catalyst 6608 - Configuring channels not in
service
I think this is what you are looking for:
Service Parameters > Call Manager > Advanced > CTRL-F > "maintenance"
This is a 3.3.4sr2 helpfile snippet:
________________________________
Change B-Channel Maintenance Status 1 :
This parameter allows Cisco CallManager to change individual B-Channel
maintenance status for PRI interface 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. The last one
specifies the D-Channel, which does not get affected. In this example,
5th-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 D-Channel. The last bit
does not affect any channel. In this example, 25th-31st channels are
marked out of service).
Explanation:
The DEVICE NAME MUST exactly match the gateway name on the top of the
gateway configuration web page. Copy and paste that field into this
service parameter to avoid any manual inputting mistake. Ensure '=' is
mandatory and unique to distinguish the DEVICE NAME and BCHANNEL
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).
The system treats any other value as invalid and the value does not take
effect. 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.
To use this feature, the "Enable Status Poll" flag on the gateway
configuration page must be checked and updated, then the gateway must be
reset for the first time.After this, changing service parameter will
take effect without resetting the gateway.
Maximum length: 255.
Change B-Channel Maintenance Status 2 :
This parameter allows Cisco CallManager to change individual B-Channel
maintenance status for PRI interface in real time for troubleshooting.
The description duplicates the preceding one.
Maximum length: 255.
Change B-Channel Maintenance Status 3 :
This parameter allows Cisco CallManager to change individual B-Channel
maintenance status for PRI interface in real time for troubleshooting.
The description duplicates the one for Change B-Channel Maintenance
Status 1.
Maximum length: 255.
Change B-Channel Maintenance Status 4 :
This parameter allows Cisco CallManager to change individual B-Channel
maintenance status for PRI interface in real time for troubleshooting.
The description duplicates the one for Change B-Channel Maintenance
Status 1.
Maximum length: 255.
Change B-Channel Maintenance Status 5 :
This parameter allows Cisco CallManager to change individual B-Channel
maintenance status for PRI interface in real-time for troubleshooting.
The description duplicates the one for Change B-Channel Maintenance
Status 1.
Maximum length: 255.
________________________________
----- Original Message -----
From: David Sullivan <mailto:David.Sullivan at barnet.ac.uk>
To: cisco-voip at puck.nether.net
Sent: Wednesday, July 13, 2005 6:33 AM
Subject: [cisco-voip] Catalyst 6608 - Configuring channels not
in service
A while back I found a webpage ( possibly among the voip pages
on
tamu.edu ) which outlined how to mark channels on an PRI out of
service in the gateway configuration for a 6608 using a numeric
string but I can't find the page anymore.
We've recently had an issue on an ISDN line where we were having
problems with certain channels which we were having trouble
diagnosing and we're possibly considering whether we need so
many
ISDN channels now that we've moved all of our sites over to IP
telephony but because of the "you can only have an ISDN line
with all
channels in use" standard answer we're feeling a bit
constrained.
Does anyone still have this information around?
David Sullivan
IT Services
Barnet College
==============================================================
This communication may contain privileged or confidential
information which
is for the exclusive use of the intended recipient. If you are
not the
intended recipient, please note that you may not distribute or
use this
communication or the information it contains. If this e-mail
has reached you
in error, please delete it and any attachment.
Internet communications are not secure and Barnet College does
not accept
legal responsibility for the content of this message. Any views
or opinions
expressed are those of the author and not necessarily those of
Barnet College.
Please note that Barnet College reserves the right to monitor
the
source/destinations of all incoming or outgoing e-mail
communications.
==============================================================
_______________________________________________
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/20050713/145759d6/attachment-0001.html
More information about the cisco-voip
mailing list