<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Yes, that's the kicker, you need to have that option enabled first then restart the gateways.<br><br>It was like QuattroPro in the old days, you had to enable the "undo" function before you could use it. <br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Dane" <dane@pktloss.net><br>To: "Wes Sisk" <wsisk@cisco.com><br>Cc: cisco-voip@puck.nether.net, "FrogOnDSCP46EF" <ciscoboy2006@gmail.com><br>Sent: Monday, March 30, 2009 12:38:04 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] Stop new calls but preserve existing on CMM-6T1?<br><br>Ok so from the comments so far and from what I have found while<br>googling it seems the service parameter that I was looking for was the<br>"Change B-Channel Maintenance Status 1 - 5".<br><br>Apparently this should allow you to take the B-channels out of service<br>for up to five MGCP gateways without disrupting calls.<br><br>Source: Cisco CallManager Best Practices<br>Google Book Search Preview: http://tinyurl.com/c5lop7<br><br><br>Catch is the PRI's have to be pre-configured with "unchecking the<br>inhibit restarts at PRI intialization and check enable status poll<br>then restart the gateway.<br><br>This Cisco doc seems to explain it fairly well.<br><br>Busy-Out ISDN B-Channels in Cisco CallManager Configuration Example<br>Source Cisco Website: http://tinyurl.com/2675fo<br><br><br><br><br><br><br><br>On Mon, Mar 30, 2009 at 10:30 AM, Wes Sisk <wsisk@cisco.com> wrote:<br>> the service param works on any mgcp gw.<br>> if using h.323 gw, then you can busy out the b-ch individually. it has been<br>> covered on this list previously.<br>> /wes<br>> On Mar 28, 2009, at 8:36 PM, FrogOnDSCP46EF wrote:<br>><br>> AFAIK, busy out parameter in CCM service parameter is only for 6608, coz<br>> 6608 doesn't have anything to connfigure like IOS gw has for example:<br>> 'pri-group timeslot 1-31.<br>><br>> CMM module is IOS based. So CCM service parameter is not relivent. it does<br>> it by default.<br>><br>> on top of that, the original poster said there are 8T1's while in CCM<br>> service parameter only has upto 3 b-chan rows to put in. what about if there<br>> are more than 3 t1's and want to busy out htem.? it can't be done on ccm<br>> service parameter but the solution i would think would be turn MGCP gw to<br>> H323 gateway. H323 gateway has call presevation option.<br>><br>> So in a nutshell, IOS gateway should have default behavour for call<br>> preservation without busying-out them in ccm-service parameter<br>><br>> Please correct me if I am wrong.<br>><br>><br>><br>><br>> Message: 17<br>> Date: Fri, 27 Mar 2009 22:09:45 -0400 (EDT)<br>> From: Lelio Fulgenzi <lelio@uoguelph.ca><br>> Subject: Re: [cisco-voip] Stop new calls but preserve existing on<br>> CMM-6T1?<br>> To: Matthew Loraditch <MLoraditch@heliontechnologies.com><br>> Cc: cisco-voip@puck.nether.net<br>> Message-ID:<br>> <1469835665.124761238206185226.JavaMail.root@simcoe.cs.uoguelph.ca><br>> Content-Type: text/plain; charset="utf-8"<br>><br>> There's a enterprise or service parameter that allows you to "busy" out<br>> channels. This should help. Basically allows you to put them in maintenance<br>> mode or something.<br>><br>><br>> ---<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> "Bad grammar makes me [sic]" - Tshirt<br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>><br>><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>