<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>I think this is what you are looking for:</DIV>
<DIV> </DIV>
<DIV>Service Parameters > Call Manager > Advanced > CTRL-F >
"maintenance"</DIV>
<DIV> </DIV>
<DIV>This is a 3.3.4sr2 helpfile snippet:</DIV>
<DIV> </DIV>
<DIV>
<HR>
</DIV>
<DIV>
<TABLE cellSpacing=1 cellPadding=9 border=0>
<TBODY>
<TR>
<TD vAlign=top><A name=ChangeBChannelMaintenanceStatus1><B>Change
B-Channel Maintenance Status 1 :</B></A></TD>
<TD>This parameter allows Cisco CallManager to change individual B-Channel
maintenance status for PRI interface in real time for troubleshooting.
Input Format:<BR>Device Name = B-channel Maintenance
Status<BR>Example:<BR>S0/DS1-0@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).<BR>or,<BR>S1/DS1-0@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).<BR>Explanation:<BR>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 <BR>Where x can be: <BR>0 -- In service <BR>1 -- Graceful out of
service (Change channel status until active call ends if an active call
exists on that channel) <BR>2 -- Forceful out of service (Tear down active
call first; then, change channel status immediately if an active call
exists on that channel).<BR>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. <BR>SPACE: Optional.<BR>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.
<BR>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. <BR>Maximum length: 255.<BR></TD></TR>
<TR>
<TD vAlign=top><A name=ChangeBChannelMaintenanceStatus2><B>Change
B-Channel Maintenance Status 2 :</B></A></TD>
<TD>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. <BR>Maximum length:
255.<BR></TD></TR>
<TR>
<TD vAlign=top><A name=ChangeBChannelMaintenanceStatus3><B>Change
B-Channel Maintenance Status 3 :</B></A></TD>
<TD>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.
<BR>Maximum length: 255.<BR></TD></TR>
<TR>
<TD vAlign=top><A name=ChangeBChannelMaintenanceStatus4><B>Change
B-Channel Maintenance Status 4 :</B></A></TD>
<TD>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.
<BR>Maximum length: 255.<BR></TD></TR>
<TR>
<TD vAlign=top><A name=ChangeBChannelMaintenanceStatus5><B>Change
B-Channel Maintenance Status 5 :</B></A></TD>
<TD>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.
<BR>Maximum length: 255.<BR></TD></TR></TBODY></TABLE></DIV>
<DIV>
<HR>
</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=David.Sullivan@barnet.ac.uk
href="mailto:David.Sullivan@barnet.ac.uk">David Sullivan</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, July 13, 2005 6:33
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Catalyst 6608 -
Configuring channels not in service</DIV>
<DIV><BR></DIV>A while back I found a webpage ( possibly among the voip pages
on <BR>tamu.edu ) which outlined how to mark channels on an PRI out of
<BR>service in the gateway configuration for a 6608 using a numeric <BR>string
but I can't find the page anymore.<BR><BR>We've recently had an issue on an
ISDN line where we were having <BR>problems with certain channels which we
were having trouble <BR>diagnosing and we're possibly considering whether we
need so many <BR>ISDN channels now that we've moved all of our sites over to
IP <BR>telephony but because of the "you can only have an ISDN line with all
<BR>channels in use" standard answer we're feeling a bit
constrained.<BR><BR>Does anyone still have this information
around?<BR><BR>David Sullivan<BR>IT Services<BR>Barnet
College<BR>==============================================================<BR>This
communication may contain privileged or confidential information which<BR>is
for the exclusive use of the intended recipient. If you are not
the<BR>intended recipient, please note that you may not distribute or use
this<BR>communication or the information it contains. If this e-mail has
reached you<BR>in error, please delete it and any attachment.<BR><BR>Internet
communications are not secure and Barnet College does not accept<BR>legal
responsibility for the content of this message. Any views or
opinions<BR>expressed are those of the author and not necessarily those of
Barnet College.<BR><BR>Please note that Barnet College reserves the right to
monitor the<BR>source/destinations of all incoming or outgoing e-mail
communications.<BR>==============================================================<BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>