Automatic switch between trunks when one becomes unavailable
NewY:
hi, I use one Obi110 and one Linksys PAP2. My provider is callwithus. My obi110 SP1 is google and SP2 is callwithus. I use google to make domestic calls and use callwithus to make international calls. However, Callwithus' registration is not stable on Obi110 but is very stable on Linksys PAP2. So I hook PAP2's phone line to Obi110's line port as a backup.
My questions is how to set up on Obi110 so that when i make international call with SP2 and SP2 fails to register with Callwithus, it automatically switches to PSTN port (here it is PAP2)?
My thinking is to set up outbound call route configuration. But each rule seems independent. Or I need to work on TrunkGroup?
Please help. Thanks.
xibai:
I understand somebody posted similar questions here athttp://www.obitalk.com/forum/index.php?topic=2390.msg15480#msg15480.
However, my need is not to switch all calls to the primary line, but only international calls.
Thanks.
xibai:
To make it clearer: I want to keep sp1 as my primary line, while have the ability to automatically switch between sp2 and PSTN. How to set up? Thanks.
ianobi:
NewY,
I’m starting with some assumptions: I’m guessing that sp1 (GV) is your PrimaryLine and you dial **2 to get to Callwithus on OBi sp2 and **8 to get Callwithus via the OBi Line Port and the PAP2. What you would like to do is dial **2 and if Callwithus is failed on sp2, have the call automatically forward to the OBi Line Port.
Trunk Groups are the only way to create a “step-over failed/busy route” facility in an OBi. Please be aware that the OBi sometimes takes a few minutes to realise that it has lost registration with a Service Provider.
Something like this may work for you:
Physical Interfaces -> PHONE Port -> PrimaryLine: SP1 Service
Voice Service -> Auto Attendant -> PrimaryLine: SP1 Service
Physical Interfaces > Phone Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Mtg1)|**8(Mli)|**9(Mpp)|(Mpli))
Physical Interfaces > Phone Port > OutboundCallRoute
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Mtg1)):tg1},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Voice Services > Gateways and Trunk Groups > Trunk Group1
TrunkList > sp2,li
DigitMap > ((Msp2)|(Mli))
There are other ways of arranging the trunk group, say by using **6 to access the trunk group, which would leave you free to choose sp2 via **2 when you wanted to. Any of my assumptions at the start of this post might be wrong, so let me know if you want to modify my suggestion.
Always with Trunk Groups, be very careful where 911 is being routed.
Ostracus:
Quote from: ianobi on February 01, 2013, 06:28:07 am
Trunk Groups are the only way to create a “step-over failed/busy route” facility in an OBi. Please be aware that the OBi sometimes takes a few minutes to realise that it has lost registration with a Service Provider.
Doesn't apply to the Obi100/110, but does X_NoRegNoCall shorten that process?
Navigation
[0] Message Index
[#] Next page