[cisco-voip] Call Routing Problems

[Jason Shearer]

Locations determine how much bandwidth is available between one site and another.  Regions determine what voice codec (codec = per call bandwidth) is used between one site and another.

Hope this helps.

Jason

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Huffman, Tim
Sent: Monday, January 04, 2010 12:47 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Call Routing Problems

All,

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.

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?

I did already confirm that we did not saturate our WAN connection between the two sites.

Thanks,

Tim Huffman


________________________________
*** NOTICE--The attached communication contains privileged and confidential information. If you are not the intended recipient, DO NOT read, copy, or disseminate this communication. Non-intended recipients are hereby placed on notice that any unauthorized disclosure, duplication, distribution, or taking of any action in reliance on the contents of these materials is expressly prohibited. If you have received this communication in error, please delete this information in its entirety and contact the Amedisys Privacy Hotline at 1-866-518-6684. Also, please immediately notify the sender via e-mail that you have received this communication in error. ***
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100104/745f1cc8/attachment.html>