<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>A PRI group will have an upper limit on the number of inbound calls available, so even though you have 5 PRIs (5x23=115 calls assuming no shared D channels) the group might have an upper limit of 95 inbound calls in order to always have 20 outbound calls.<br><br>Something to consider...<br><span><br><span name="x"></span>---<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>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Dave Wolgast" <dwolgas1@rochester.rr.com><br><b>To: </b>"Cisco VOIP Newsletter - puck.nether.net" <cisco-voip@puck.nether.net><br><b>Sent: </b>Thursday, August 5, 2010 9:14:26 AM<br><b>Subject: </b>[cisco-voip] Carrier routing issue?<br><br>I am pretty confident that this does not have to do with CallManager (6.1.4, MGCP PRI GWs with lots o' DIDs), but I am wondering if someone might help me put together a method for approaching the issue...<br><br>Sporadically, for what seems like about a minute at a time, some callers to our DIDs (mostly cellular callers) report getting a network message that the call cannot be completed, or for Verizon Wireless callers, "the Verizon Wireless customer you called is not available at this time." My personal experience is that I retry 2-4 times, and end up getting through. It doesn't happen often, but does seem to occur as things are starting to get busy on the trunks. That said, I never see blocking on the trunks when I monitor using RTMT, even though utilization is fairly high.<br>
<br>The DIDs are on a trunk group of 5 Verizon PRIs, and in 2008, were ported by Verizon to a different CO when headquarters moved a few miles down the road.<br><br>Any ideas for things I should look at/for? Should I be calling Verizon, or any of the cell carriers on which the issue was reported?<br>
<br>Thanks for any suggestions you might offer!<br clear="all"><br>-- <br>Dave Wolgast<br>Livonia, NY<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>