[cisco-voip] Busy out channels on an mgcp gateway
Lelio Fulgenzi
lelio at uoguelph.ca
Wed Dec 21 10:48:56 EST 2005
I'd like to say I could test it on one of our test PRI ports - but I've seen wierd things with our 6608 that ends up resetting all our PRI ports. :(
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter than an
IP phone on a long haul 10base2 connection" LFJ
----- Original Message -----
From: Ryan Ratliff
To: Lelio Fulgenzi
Cc: Ruttman, Peter G. ; cisco-voip at puck.nether.net
Sent: Wednesday, December 21, 2005 10:47 AM
Subject: Re: [cisco-voip] Busy out channels on an mgcp gateway
I was debating internally whether the reset of the MGCP gateway would
drop active calls or not.
I know for sure that when you reset a phone (ccmadmin reset) it will
not actually reset until the active call is torn down.
I'd like to think an MGCP gateway would behave the same. Even if it
does so, would the change to inactive channels take immediately or
would all of them go to graceful out of service only when all active
calls have been torn down?
I just did a quick test with a CM 4.1 mgcp gateway with an FXS port.
The reset did indeed knock the FXS end of the call off when the
gateway unregistered and Temp Fail showed on the IP phone.
I don't have a gateway with a PRI handy to test with unfortunately.
-Ryan
On Dec 21, 2005, at 10:35 AM, Lelio Fulgenzi wrote:
so much for the graceful option, eh? ;)
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more
jitter than an
IP phone on a long haul 10base2
connection" LFJ
----- Original Message -----
From: Ryan Ratliff
To: Lelio Fulgenzi
Cc: Ruttman, Peter G. ; cisco-voip at puck.nether.net
Sent: Wednesday, December 21, 2005 10:23 AM
Subject: Re: [cisco-voip] Busy out channels on an mgcp gateway
Those will work but require the gateway be reset to take affect.
-Ryan
On Dec 21, 2005, at 9:55 AM, Lelio Fulgenzi wrote:
I've heard people use the following service parameter to do what you
are asking. There are five of them available I think.
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.
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more
jitter than an
IP phone on a long haul 10base2
connection" LFJ
----- Original Message -----
From: Ruttman, Peter G.
To: cisco-voip at puck.nether.net
Sent: Wednesday, December 21, 2005 9:43 AM
Subject: [cisco-voip] Busy out channels on an mgcp gateway
I need to reset an mgcp gateway PRI that has inbound DIDs associated
with it. Is it possible to busy out the channels on it so that new
calls do not get pinned up on it? Then I can safely reset the
gateway during work hours.
Pete
The preceding email message may be confidential or protected by the
attorney-client privilege. It is not intended for transmission to, or
receipt by, any unauthorized persons. If you have received this
message in error, please (i) do not read it, (ii) reply to the sender
that you received the message in error, and (iii) erase or destroy
the message. Legal advice contained in the preceding message is
solely for the benefit of the Foley & Lardner LLP client(s)
represented by the Firm in the particular matter that is the subject
of this message, and may not be relied upon by any other party.
Internal Revenue Service regulations require that certain types of
written advice include a disclaimer. To the extent the preceding
message contains advice relating to a Federal tax issue, unless
expressly stated otherwise the advice is not intended or written to
be used, and it cannot be used by the recipient or any other
taxpayer, for the purpose of avoiding Federal tax penalties, and was
not written to support the promotion or marketing of any transaction
or matter discussed herein.
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20051221/5cc75520/attachment.html
More information about the cisco-voip
mailing list