[cisco-voip] MGCP PRI Busy-Out

Jason Shearer jshearer at amedisys.com
Mon Jan 18 19:56:18 EST 2010


If you busy them out in the GW on a MGCP controlled trunk UCM will not know about it.  Use B channel maintenance in service parameters and enable status polling on the GW port.

Jason

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mark Holloway
Sent: Monday, January 18, 2010 6:42 PM
To: Nikola Stojsin
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] MGCP PRI Busy-Out

You can either busy-out the channels in Call Manager or you can do it directly on the router's PRI interface.

HQ_Rtr(config)#int serial 0/0/0:23
HQ_Rtr(config-if)#isdn service b_channel 0-23 state ?
  <0-2>  Valid states are 0=Inservice 1=Maint 2=Outofservice



On Jan 18, 2010, at 4:51 PM, Nikola Stojsin wrote:

> A quick question ? is there a way to ?busy-out? specific channels on a PRI while using MGCP (I vaguely remember reading about it somewhere, but I cannot remember where).
>
> Thank you, as always,
> Nikola
> _______________________________________________
> 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

*** NOTICE--The attached communication contains privileged and confidential information. If you are not the intended recipient, DO NOT read, copy, or disseminate this communication. Non-intended recipients are hereby placed on notice that any unauthorized disclosure, duplication, distribution, or taking of any action in reliance on the contents of these materials is expressly prohibited. If you have received this communication in error, please delete this information in its entirety and contact the Amedisys Privacy Hotline at 1-866-518-6684. Also, please immediately notify the sender via e-mail that you have received this communication in error. ***


More information about the cisco-voip mailing list