<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>so much for the <STRONG><EM>graceful</EM></STRONG></FONT><FONT
size=2> option, eh? ;)</FONT></DIV>
<DIV><FONT size=2> </DIV></FONT>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an<BR>IP phone on a long haul 10base2
connection"
LFJ</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=rratliff@cisco.com href="mailto:rratliff@cisco.com">Ryan Ratliff</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=PRuttman@foley.com
href="mailto:PRuttman@foley.com">Ruttman, Peter G.</A> ; <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, December 21, 2005 10:23
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] Busy out
channels on an mgcp gateway</DIV>
<DIV><BR></DIV>Those will work but require the gateway be reset to take
affect.<BR><BR>-Ryan<BR><BR>On Dec 21, 2005, at 9:55 AM, Lelio Fulgenzi
wrote:<BR><BR>I've heard people use the following service parameter to do what
you <BR>are asking. There are five of them available I
think.<BR><BR><BR>Change B-Channel Maintenance Status 1 :This parameter allows
Cisco <BR>CallManager to change individual B-Channel maintenance status
for PRI <BR>interface in real time for troubleshooting. Input
Format:<BR>Device Name = B-channel Maintenance Status<BR>Example:<BR><A
href="mailto:S0/DS1-0@SDA123456789ABC">S0/DS1-0@SDA123456789ABC</A> = 0000
1111 0000 0000 0000 0001(24 bits for <BR>T1. Channel number begins with
1 to 24 from left to right. The last <BR>one specifies the D-Channel,
which does not get affected. In this <BR>example, 5th-8th B-Channels are
out of service).<BR>or,<BR><A
href="mailto:S1/DS1-0@DLS2-CM136-VG200-2.SELSIUSCMLAB.CISCO.COM">S1/DS1-0@DLS2-CM136-VG200-2.SELSIUSCMLAB.CISCO.COM</A>
= 0000 0000 0000 <BR>0000 0000 0000 1111 1111(32 bits for E1. B-Channel
number begins with <BR>1 to 32 from left to right. The 16th channel
specifies D-Channel. The <BR>last bit does not affect any channel. In
this example, 25th-31st <BR>channels are marked out of
service).<BR>Explanation:<BR>The DEVICE NAME MUST exactly match the gateway
name on the top of the <BR>gateway configuration web page. Copy and
paste that field into this <BR>service parameter to avoid any manual
inputting mistake. Ensure '=' <BR>is mandatory and unique to distinguish
the DEVICE NAME and BCHANNEL <BR>MAINTENANCE STATUS fields. BCHANNEL
MAINTENANCE STATUS = xxxx xxxx <BR>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 <BR>ends if an active call
exists on that channel)<BR>2 -- Forceful out of service (Tear down active call
first; then, <BR>change channel status immediately if an active call
exists on that <BR>channel).<BR>The system treats any other value as
invalid and the value does not <BR>take effect. Make sure that the total
number of ‘x’ is either 24 for <BR>T1 or 32 for E1. Any other invalid
length or mismatch (for example, <BR>24 for E1) gets treated as error,
and no action gets taken for that <BR>device.<BR>SPACE: Optional.<BR>The
spaces between device name and '=', between ‘=’ and BCHANNEL
<BR>MAINTENANCE STATUS, and between x and x, are all optional. You
cannot <BR>use any space inside the DEVICE NAME field.<BR>To use this
feature, the "Enable Status Poll" flag on the gateway <BR>configuration
page must be checked and updated, then the gateway must <BR>be reset for
the first time.After this, changing service parameter <BR>will take
effect without resetting the gateway.<BR>Maximum length:
255.<BR>------------------------------------------------------------------------
<BR>--------<BR>Lelio Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of
Guelph * Guelph, Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>"I
had a coffee and Coke at lunch today...and now, I've got more <BR>jitter
than an<BR>IP phone on a long haul 10base2
<BR>connection"
LFJ<BR>----- Original Message -----<BR>From: Ruttman, Peter G.<BR>To: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Sent:
Wednesday, December 21, 2005 9:43 AM<BR>Subject: [cisco-voip] Busy out
channels on an mgcp gateway<BR><BR>I need to reset an mgcp gateway PRI that
has inbound DIDs associated <BR>with it. Is it possible to busy
out the channels on it so that new <BR>calls do not get pinned up on
it? Then I can safely reset the <BR>gateway during work
hours.<BR><BR>Pete<BR><BR><BR>The preceding email message may be confidential
or protected by the <BR>attorney-client privilege. It is not intended
for transmission to, or <BR>receipt by, any unauthorized persons. If you
have received this <BR>message in error, please (i) do not read it, (ii)
reply to the sender <BR>that you received the message in error, and
(iii) erase or destroy <BR>the message. Legal advice contained in the
preceding message is <BR>solely for the benefit of the Foley &
Lardner LLP client(s) <BR>represented by the Firm in the particular
matter that is the subject <BR>of this message, and may not be relied
upon by any other party.<BR><BR><BR>Internal Revenue Service regulations
require that certain types of <BR>written advice include a disclaimer.
To the extent the preceding <BR>message contains advice relating to a
Federal tax issue, unless <BR>expressly stated otherwise the advice is
not intended or written to <BR>be used, and it cannot be used by the
recipient or any other <BR>taxpayer, for the purpose of avoiding Federal
tax penalties, and was <BR>not written to support the promotion or
marketing of any transaction <BR>or matter discussed
herein.<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>_______________________________________________<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><BR></BLOCKQUOTE></BODY></HTML>