Remote Trunk Call Routing Problem...

[ega218]

Hello,

I have several offices setup in a SCN. Everything is working wonderfuly. I am able to setup users in the US to use the lines in Panama when dialing a Panama telephone number and vice versa. I am using shortcodes to do this and when it works it is fine.

The problem is when the VPN lines are down, if someone tries to make a call to Panama or the other way around, then they get a busy signal becuase the line is down, but I neeed to find a way so that calls that are not able to be routed throug the SCN connection, becuase it is down, are instead routed through the local trunk lines on the IP office.

If any one can point to where I could find such a solution I would appreciate it.

The ability to use a remote trunk is wonderful, but I still need a backup plan for when it does not work.

Thanks in advance.

 

[ega218]

Never mind...I found the answer from a previous post from "dgilson"

dgilson (TechnicalUser) 16 Nov 10 13:22
We did this with two IPO's with SCN between them. We had to make ARS routes for each office code and we set up a backup route to do LD calling from the local IPO to the numbers if the SCN went down. We have three ARS routes, 50:Main, 51:Cottonwood Local and 52:Alternate.In 50: code: 1928300N TN: 928300N Dial Line Grp ID: 51In 51: code: 928300N Tn: 9928300N Dial Line Grp ID: 30 (SCN line)In 52: 928300N Tn: 1928300N Dial Line Grp ID: 1 (local tks)The 9N short code strips off the 9 and sends the area code and office code to ARS route 50. ARS route 50 strips the 1 and sends the area/office code to 51. 51 inserts a 9 in front of the area/office code and sends it out the SCN to the far IPO. ARS 52 is set as the alternate in 51; if the SCN is down, the call is sent to 52. In 52 a 1 is inserted in front of the area/office code and the call is sent out over the local trunks as a long distance call.