FXO Backup

[pluft]

Currently have full SIP inbound/outbound. Wanting to setup call routing to auto detect if a failed SIP registration ofprovider and route to FXO lines. Please advise how I might set this up.


Thanks

[davrays]

Which calls do you want to route through FXO - the incoming or outgoing ones?


With incoming, I guess, you'll need to do something on the ITSP side, as if device lost registration, you'll just not receive any call from ITSP, so no config on the Quadro can help.


With outgoing calls, you need to know how your ITSP reacts on them if your device lost registration. If there is no network connection, or ITSP rejects the calls, you need to use "Fail Reason" field on the routing table. Also "Activity Timeout" on the rule could be used, if there is no network, and you want fast failover.


Best regards,


DVR

[Hati_]

Could you give us some instructions on this please?

[davrays]

Hi Hati_,


well, I am not really good in explaining things :) If you mean incoming calls, obviously I cannot give any instruction there...


Concerning outgoing ones - when you adding a routing rule in the "Call Routing Table", on the second page of the wizard, there is a combobox called "Fail Reason: ". There you can choose a failure type. If that specific failure appears when calling through that routing rule, the device will not stop there, and will try to call using another matching routing rule. If call through that rule also fails, and rule has "Fail Reason:" set, device will search for next matching rule etc. You can choose "Any" fail reason, if you want to failover always, regardless of the type of error.


The "Activity Timeout: " option exists for IP (SIP, IP-PSTN) calls only. Using that you can specify the maximum time (in seconds) system tries to call using that record. If during that time system receices ringing indication, the call will go through. If not (if there is no answer from part, or DNS server doesn't answer for long time or something else), system will try to call using another matching record.


Maybe a better explanation could be found in online help or manuals...


Best regards,


David

[pluft]

Understand on the inbound ones and will coordinate with our itsp on those calls which I belive we can. I am trying to do a couple of things on the FXO side.


1. Failover in the event of a sip failure on both ITSP's


2. Use the fxo's on local calls as extra lines for outbound use.


My initial thoughts were I need to set the fxo on both inbound/outbound to cover the failover scenerio. And I also need to provide some local area code routing as I dont want to pay for the LD on the fxo only local area dialing pattern, however we have a number of them and I am trying to noodle on the best way to handle all the scenerios without confusing the system or myself.

[awhite]

The Call Routing table will determine the best entry to use based on a couple of rules:


1. It will look for the digit pattern that best matches the dialed number. An entry of 9972* will be used if the dialed number was 99721234567 rather than a 2nd entry with a pattern of 9*.


2. The order of the entries in the table is important since the entries listed at the top of the table will be used first using a top->down search.


Your entries might look like the following in the order listed if you use a prefix code of 9 with a local number of 972-xxx-xxxx:


9972 Call Type: FXO Failover= Any


9* Call Type: SIP -> ITSP-A Failover= Any


9* Call Type: SIP -> ITSP-B Failover= Any


9* Call Type: FXO


In this scenario a local number with 972 will go out on the FXO port and any other 9 + 10 digits will first try to go to ITSP-A, then ITSP-B and lastly on the FXO.


Note: There are other options to determine the correct Call Routing entry and they are listed in the help and manuals.