<div>This is a fairly well known work around, but the major limitation being it only supports 5 circuits or gateways...</div>
<div>So it's ok for small installs.</div>
<div> </div>
<div>I'd still prefer H323 for partials</div>
<div> </div>
<div>I wonder if they are finally supporting this properly with MGCP in CUCM 7?</div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div>Tim</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 8/22/08, <b class="gmail_sendername">Darren</b> <<a href="mailto:darren@dnsl.com">darren@dnsl.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Hi, I recently got the TAC to confirm this, and after some back and forth the TAC DO support fraction E1's using MGCP, as long as you do below, I got confirmation in an email so I'm all good there. Also of interest I'm not 100% sure you have do below, I had an 10channel E1 configured and used asscending and descending and I couldn't get it to fail, so I suspect its not an issue anymore, also I had the call manager config enabled and it never broke during testing, however TAC guy told me to do the following:</div>
<div> </div>
<div>Darren</div>
<div> </div>
<div>****************************</div>
<div>1.<br><br>From CCMAdmin pages go to System > Service Parameters > Service Parameter Configuration > Clusterwide Parameters (Device - PRI and MGCP Gateway) -> Change B-Channel Maintenance Status 1<br><br>
B-Channel maintenance status for PRI and CAS interfaces in real time for troubleshooting.<br>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.<b> In the case of PRI, the last bit specifies the D-Channel</b>, which does not get affected. <b>In this example, the 5th through 8th B-Channels are out of service.</b>)<br>
or,<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:S1/DS1-0@DLS2-CM136-VG200-2.SELSIUSCMLAB.CISCO.COM" target="_blank">S1/DS1-0@DLS2-CM136-VG200-2.SELSIUSCMLAB.CISCO.COM</a> = 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 the D-Channel. The last bit does not affect any channel. In this example, the 25th through 31st channels are marked out of service.)<br>
Explanation:<br><b>The Device Name as specified in the Gateway Configuration page in Cisco CallManager Administration MUST exactly match the gateway name that this field specifies.</b> To avoid any manual inputting mistake, copy the Device Name from Cisco CallManager Administration and paste it into this service parameter. "=" is mandatory and unique to distinguish the Device Name and B-Channel Maintenance Status fields.<br>
BCHANNEL MAINTENANCE STATUS = xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx<br>Where x can be:<br><b>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.)<span></span> </b><br>Because values other than 0,1, or 2 are invalid, the system ignores them. 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>PRI Specific:<br>
To use this feature, the Enable status poll check box must be checked on the PRI Gateway Configuration window. If it is not, you need to check the check box, click Update, and reset the gateway for the service parameter change to take effect.<br>
Maximum length: 255 <br><br>2. Make sure you will not use it with the CCM config server option as the<br>call manager will reset the B channel service parameter status and overwrite<br>the configuration on the router, so calls will then be attempted on the<br>
unconfigured B channels. <br><br>For your interest:<br>Defect CSCdw78580 describes the issue with fractional PRI and MGCP.<br>************************************</div>
<div><span class="e" id="q_11be7a23141f3665_1">
<div> </div>
<div> </div>
<div><br><br> </div>
<div><span class="gmail_quote">On 8/22/08, <b class="gmail_sendername">Kris Seraphine</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:baryonyx5@gmail.com" target="_blank">baryonyx5@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">If you have any analog DID trunks or fractional PRIs you'll want to<br>stay H.323. Those are not support as MGCP in CM.<br>
<br>If you decide to convert, take into consideration your digit discard<br>settings on the route lists. Likely you are currently passing the<br>prefix digit to the gateway. If you convert to MGCP you'll want to<br>
strip it on the route list.<br><br>Personally, I prefer H.323 for remote site PSTN trunks when SRST is<br>involved. It's much less buggy more flexible and easier to<br>troubleshoot. If you use MGCP you still have to configure H.323 for<br>
fallback so you gain very little.<br><br>On Tue, Aug 19, 2008 at 12:23 PM, Matthew Loraditch<br><<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:MLoraditch@heliontechnologies.com" target="_blank">MLoraditch@heliontechnologies.com</a>> wrote:<br>
> All,<br>><br>> In the past I have had MGCP setup for my gateways but recently took over a<br>> system with h.323 for the gateways. The gateways are only connected to and<br>> used by CCM and I like the MGCP abilities to control the various ports<br>
> directly in CM. Is there any benefit to keeping them as H.323? If not is it<br>> difficult to convert between one or the other?<br>><br>> Thanks!<br>><br>><br>><br>><br>><br>> Matthew Loraditch<br>
> 10944 Beaver Dam Road, Suite A<br>> Hunt Valley, Maryland 21030<br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:support@heliontechnologies.com" target="_blank">support@heliontechnologies.com</a><br>
> (p) (410) 252-8830<br>> (F) (443) 541-1593<br>><br>> Visit us at <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.heliontechnologies.com/" target="_blank">www.heliontechnologies.com</a><br>
> Support Issue? Email <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:support@heliontechnologies.com" target="_blank">support@heliontechnologies.com</a> for fast assistance!<br>><br>><br>><br>
> _______________________________________________<br>> cisco-voip mailing list<br>> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> <a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>><br>><br><br><br>
<br>--<br>kris seraphine<br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br></span></div>
<br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>