<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>for MGCP gateways you can check out the CallManager service parameter: "Change B-Channel Maintenance Status". for H323, there are some IOS commands - sorry, they escape me right now.<br><br>but this might help<br><br>https://supportforums.cisco.com/docs/DOC-4989;jsessionid=BFF2F0C5CC2BFC0BDE6C10508B0C8A4C.node0<br><br>this is for v4.1(3) but I suspect something similar is available for v5,6,7<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: "tmdvoip" <tmdvoip@gmail.com><br>To: "Jason Shearer" <jshearer@amedisys.com>, cisco-voip@puck.nether.net<br>Sent: Wednesday, January 6, 2010 11:10:22 AM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] PRI 's Roll<br><br>Jason S.<br><br>I liked your idea about testing each channel.<br><br>These are your words below.<br><br>"You can test each channel if you would like by shutting #2 & #3 down and<br>busying out all channels but one on #1. Place test call. Rinse and repeat<br>till you have tested all channels."<br><br>I hate being so ignorant on this topic, but how would I busy out all the<br>other channels?<br><br>For example, just keep dialing in bound calls from various phones?<br><br>I do know how to shut down PRI/GW #2 and #3.<br><br>Also, let me make sure I have my terminology right.<br><br>The PRI/GW contains the channels IE 23 usable for ea PRI.<br>I have 3 PRI's/GW equals 69 channels. Right?<br><br><br>Thanks, TMD<br><br>-----Original Message-----<br>From: Jason Shearer [mailto:jshearer@amedisys.com] <br>Sent: Tuesday, January 05, 2010 3:03 PM<br>To: tmdvoip; cisco-voip@puck.nether.net<br>Subject: RE: [cisco-voip] PRI 's Roll<br><br>Ask these questions:<br><br>1) What order are they rolling in?<br>2) What distribution algorithm are they using? (top down, circular, etc)<br><br>You can test each channel if you would like by shutting #2 & #3 down and<br>busying out all channels but one on #1. Place test call. Rinse and repeat<br>till you have tested all channels.<br><br>I typically request top down from the provider and do just the opposite<br>outbound. If they are going top down 1,2,3 I will go outbound bottom up<br>3,2,1.<br><br>Jason<br><br>-----Original Message-----<br>From: cisco-voip-bounces@puck.nether.net<br>[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of tmdvoip<br>Sent: Tuesday, January 05, 2010 1:56 PM<br>To: cisco-voip@puck.nether.net<br>Subject: [cisco-voip] PRI 's Roll<br><br>Guys:<br><br>This is my configuration<br>CUCM 4.2(3)sr4a (2) Cm in cluster<br>Cisco Unity 4.0(5.0)<br>Cisco 2851 Routers<br><br><br>Here is the situation: My client complains that external callers sometime<br>get an error message from our Telco Provider AT&T saying (all circuits are<br>busy).<br><br>I opened a ticket with the provider and they confirmed that there was a<br>power outage at one of their locations. Therefore, the Telco Provider AT&T<br>circuit has no power and our PRI goes down.<br><br>My client has 3 PRI's configured and they are supposed to roll from one PRI<br>to the next as call volume increases. The thing of it is my client has 3<br>PRI's with 23 channels each that are way-way under utilize. My question is<br>should the incoming calls just transition to the next PRI in the group? Am I<br>missing something? Is my Telco sales person says we are configured to roll<br>to the PRI. Why is it not rolling?<br><br>Sincerely,<br>Thomas Dooley<br>Cisco Telecommunications Administrator<br>Triad NC<br>Desk: 336-917-7125<br><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>*** NOTICE--The attached communication contains privileged and confidential<br>information. If you are not the intended recipient, DO NOT read, copy, or<br>disseminate this communication. Non-intended recipients are hereby placed on<br>notice that any unauthorized disclosure, duplication, distribution, or<br>taking of any action in reliance on the contents of these materials is<br>expressly prohibited. If you have received this communication in error,<br>please delete this information in its entirety and contact the Amedisys<br>Privacy Hotline at 1-866-518-6684. Also, please immediately notify the<br>sender via e-mail that you have received this communication in error. ***<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>