<div>As I recall there are a handful of 4.x bugs related to location-based CAC, which are indeed fixed with a resync. I haven't run into those defects in later versions.</div>
<div> </div>
<div>This is one of the few cases where "cisco math" is straightforward - G.711 consumes 80kbps and G.729 consumes 24kbps of location bandwidth.</div>
<div><br clear="all">Matthew Saskin<br><a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a><br>203-253-9571<br><br><br></div>
<div class="gmail_quote">On Mon, Jan 4, 2010 at 4:22 PM, Jason Aarons (US) <span dir="ltr"><<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang="EN-US" vlink="purple" link="blue">
<div>
<p class="MsoNormal"><span style="COLOR: #1f497d">To add to this back in the 4.1.3 days I had several site with 2 7940s using G711 nothing less than a T1 with Location Bandwidth set to 786K that would get Not Enough Bandwidth. I’m sure it was a bug as re-sync would fix it for awhile. I finally quit using the Locations bandwidth unless we were really overwhelming the link, then changed the message to Try Later or something else like Not Enough Lines or Contact Helpdesk.</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"> </span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">To this day I still don’t trust it as I can’t figure out Cisco math sometimes.</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"> </span></p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt">From:</span></b><span style="FONT-SIZE: 10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Matt Slaga (US)
<div class="im"><br><b>Sent:</b> Monday, January 04, 2010 1:57 PM<br></div><b>To:</b> Huffman, Tim; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] Call Routing Problems</span>
<p></p></p></div></div>
<div>
<div></div>
<div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="COLOR: #1f497d">‘Not enough bandwidth’ only is sent to a device when the ‘location’ bandwidth is overrun. Check your location bandwidth settings (System -> Locations).</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"> </span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"> </span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"> </span></p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt">From:</span></b><span style="FONT-SIZE: 10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Huffman, Tim<br>
<b>Sent:</b> Monday, January 04, 2010 1:47 PM<br><b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> [cisco-voip] Call Routing Problems</span></p></div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">All,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We have a Subscriber and Publisher at our main location. We have another subscriber at one of our remote office that is associated with the publisher at the main location.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I made a route pattern on our Publisher that would allow for some of the calls that are incoming at our main site’s T1s, to go outbound our remote sites’ T1s so we can free up some channels on our T1s at the main site. Once I made this change, it worked with no issues until we hit a certain call volume (not sure how many). Once it went haywire phones at our remote location started saying “not enough bandwidth.” It also caused issues trying to call inter-office from our main location to our remote location. How would I tell what the limitation is of simultaneous calls from our main location to our remote location?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I did already confirm that we did not saturate our WAN connection between the two sites.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><i><span style="FONT-SIZE: 13.5pt; COLOR: #1f497d">Tim Huffman</span></i><span style="FONT-SIZE: 12pt; COLOR: #1f497d; FONT-FAMILY: 'Times New Roman','serif'"></span></p>
<p class="MsoNormal"> </p>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<hr align="center" width="100%" size="1">
</span></div>
<p><strong>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. </strong></p>
</div></div></div></div>
<div>
<div></div>
<div class="h5">
<div>
<p>
<hr size="1">
<p></p>
<p><strong>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. </strong></p>
</p></div></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a 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>