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? <br><br>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.
<br><br><div><span class="gmail_quote">On 2/15/06, <b class="gmail_sendername">Wes Sisk</b> <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
AAR will auto reroute to PSTN if WAN is OoBandwidth. However, FAC<br>does not work on trunk to trunk calls (or didn't when I wrote the<br>networks presentation last year) i.e. cluster1---->(ICT)cluster2<br>(mgcpgw)--PSTN.
<br><br>scenario that does work:<br>remote site has all calls default route to local gateway through a<br>route pattern that uses FAC<br>calls to central site route over ICT with AAR (use special CSS to<br>match a RP that does not use FAC) make your local gw be the 2nd
<br>member in the route group to cover the case where the central site<br>does not respond at all (WAN down).<br><br>/Wes<br><br><br>On Feb 13, 2006, at 5:01 PM, Ed Leatherman wrote:<br><br>I'm trying to build a scenario in the lab that functions like this:
<br><br>Remote site (seperate CCM 4.1) has intercluster trunk to Main Campus<br>CCM 4.1. Also has PRI to PSTN.<br><br>If a remote site user dials an extension for the main campus, it will<br>hit a route pattern/Route List that has a route group containing the
<br>ICT first, and then a route group containing the PSTN Gateway as the<br>second item. So if the WAN connection is down or out of bandwidth it<br>translates the called number and sends it out the PSTN gateway<br>instead. So far so good.
<br><br>What the remote site has now asked is to have forced auth. codes on<br>long distance PSTN calls. Is there a way to configure it such that<br>for calls to the main site callmanager only asks for a FAC if the<br>call gets directed to the PSTN? It seems i have to specify the FAC
<br>from route pattern page, which will ask for a FAC every time even on<br>ICT calls. I wasnt sure if there was a more clever way to do it and<br>get the desired effect.<br><br>I took a look at AAR, but it mentioned that it was for intrA-cluster
<br>calls rather than intER-cluster calls.. and i'm not sure it would<br>help me out anyway since calls aren't re-routed in the event of WAN<br>failure.<br><br>Thanks!<br>--<br>Ed Leatherman<br>IP Telephony Coordinator<br>
West Virginia University<br>Telecommunications and Network Operations<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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>IP Telephony Coordinator
<br>West Virginia University<br>Telecommunications and Network Operations