[cisco-voip] Route Pattern/FAC question

[Wes Sisk]

"if it goes to the PSTN" - if WAN is down between the CM's then only  
alternative is PSTN.

I have not tested AAR to a FAC enabled RP, so in uncharted territory  
just now
I only expect AAR to engage if we get an OOB either from GK or by  
locations CAC.  AAR allows us to use a different CSS to attempt to  
route the call, so we could match a new routepattern with whatever  
settings we want (FAC?)

For the case of WAN being down, I think we are stuck using the route  
pattern we have already matched so only option is to send the call  
out the local gateway with whatever number modifications we desire.   
If you're using an h323 gateway you could use the TCL script calling  
card application, but that would produce another data source to have  
to incorporate into your reporting and billing.

sounds like time for a recreate. where's chris?

/Wes

On Feb 15, 2006, at 9:38 AM, Ed Leatherman wrote:

If I understand how that would work, it would not prompt the user for  
a FAC in the event that the ICT was OoBandwidth or WAN was down - it  
would just roll over to the PSTN gateway. Is that right?

What I've been asked to do is make sure it prompts for a FAC code if  
it goes to the PSTN. So if the ICT is up and available, no FAC is  
needed but if its unavailable and the call needs to go out the PSTN,  
they need the FAC code for billing/tracking.

On 2/15/06, Wes Sisk <wsisk at cisco.com> wrote:
AAR will auto reroute to PSTN if WAN is OoBandwidth.  However,  FAC
does not work on trunk to trunk calls (or didn't when I wrote the
networks presentation last year) i.e.   cluster1---->(ICT)cluster2
(mgcpgw)--PSTN.

scenario that does work:
remote site has all calls default route to local gateway through a
route pattern that uses FAC
calls to central site route over ICT with AAR (use special CSS to
match a RP that does not use FAC)  make your local gw be the 2nd
member in the route group to cover the case where the central site
does not respond at all (WAN down).

/Wes


On Feb 13, 2006, at 5:01 PM, Ed Leatherman wrote:

I'm trying to build a scenario in the lab that functions like this:

Remote site (seperate CCM 4.1) has intercluster trunk to Main Campus
CCM 4.1. Also has PRI to PSTN.

If a remote site user dials an extension for the main campus, it will
hit a route pattern/Route List that has a route group containing the
ICT first, and then a route group containing the PSTN Gateway as the
second item. So if the WAN connection is down or out of bandwidth it
translates the called number and sends it out the PSTN gateway
instead. So far so good.

What the remote site has now asked is to have forced auth. codes on
long distance PSTN calls. Is there a way to configure it such that
for calls to the main site callmanager only asks for a FAC if the
call gets directed to the PSTN? It seems i have to specify the FAC
from route pattern page, which will ask for a FAC every time even on
ICT calls. I wasnt sure if there was a more clever way to do it and
get the desired effect.

I took a look at AAR, but it mentioned that it was for intrA-cluster
calls rather than intER-cluster calls.. and i'm not sure it would
help me out anyway since calls aren't re-routed in the event of WAN
failure.

Thanks!
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip




-- 
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060215/8dd0b91a/attachment.html