[cisco-voip] toll bypass route lists - 9.@ with route filter ormultiple regexp

[Kris Seraphine]

In the situation I'm thinking of the limited resource is the WAN.  A smaller
site may only be provisioned for 5 concurrent calls.  In order to provide
local re-route in the case of WAN congestion you need route
pattern-route-list-route-groups created for every remote location calls
could be routed through.  If the WAN were not an issue I could re-route
calls through a centralized LD circuit and reduce the administration
overhead to a manageable level.

I think Cisco could solve this problem by introducing a "local route group"
parameter on the device pool where you could specify a real route group.
Then in a route list you could choose "local route group" as an option for
the ordered list of route groups.  That would greatly simplify dial plans.

But you're right; LD rates are low enough (and this particular customer
bills LD calls back to their clients anyway) where it's not worth the effort
as it stands.

On 2/20/07, Jason Aarons (US) <jason.aarons at us.didata.com> wrote:
>
>  In a large scale TEHO how do you plan resources ? I'm sure COs and Bells
> do a lot of planning that during X hour X number of people will likely be
> calling a city, and to have a lot of spare capacity to avoid busy signals.
>
>
>
> I know at Cisco when I get a call from San Jose, CA they don't send the
> call our their local Florida office.
>
>
>
> In the past I've negotiated a better rate for a LD PRI (2-3 cents minute)
> then it was to implement TEHO. Troubleshooting was a pain in TEHO.
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Kris Seraphine
> *Sent:* Tuesday, February 20, 2007 3:02 PM
> *To:* Lelio Fulgenzi
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] toll bypass route lists - 9.@ with route
> filter ormultiple regexp
>
>
>
> I don't know of any way to simplify to do toll bypass/teho in CCM.  It
> becomes unmanageable very quickly with more than a few locations; especially
> if you need to provide for re-routing out of the local gateway.
>
> On 2/19/07, *Lelio Fulgenzi* <lelio at uoguelph.ca> wrote:
>
> Just wondering what others have done for toll bypass route lists. I have
> to create a route list which drops the 91 from calls from a remote site that
> are local to our gateways, but there are a significant number of exchanges,
> most of which are not in any particular range (while some are). I'd rather
> not mix and match, i.e. some route patterns with regexp and others with
> 9.@ and a route filter.
>
>
>
> What are others doing?
>
>
> --------------------------------------------------------------------------------
> Lelio Fulgenzi, B.A.     Network Analyst (CCS)
> University of Guelph     Guelph, Ontario     N1G 2W1
> (519) 824-4120 x56354     (519) 767-1060 FAX
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Sanity First : Number of days with less than
> 50 messages in my inbox at the end of the day:    buffer overrun
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
> --
> kris seraphine
>
> ------------------------------
>
> * 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. *
>



-- 
kris seraphine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070220/6731f423/attachment.html