Question about route priority and failover

Hi,

I think we will be deploying ProSBC soon but I'm stuck on one routing issue.

Here's a screenshot of our routes. I've simplified it the routes a bit.



We have FreeSBC in front of two Asterisk servers (in the NAPs and routes, they are named SERVER_0, SERVER_1 or SIP_SERVER_0, SIP_SERVER_1). We have one SIP domain and have both set up as a registrar:



As you can see, we have an open NAP to each and we accept calls from NAPs for trunks such as Thinktel, voip.ms and a PSTN gateway.

I need the calls to reach the Asterisk server because we are currently using the Asterisk CDR for call records and billing. A script on the Asterisk servers determines if the number dialed belongs to a customer by querying our customer accounting database and returning a list of endpoints to call (ATAs, etc). If it is a customer number, then it sends the call back to the SBC over SIP_SERVER_X_NAP_0 which matches the route SERVER_X_TO_REMOTE. This works and isn't what I need help with.

If the call isn't one of our numbers then it's sent to SBC over SIP_SERVER_X_NAP_1 where I want it to:

- Route to the PSTN gateway if it is a local number (using label routing)
- if it is not a local number or the PSTN gateway is unavailable, then route to voip.ms
- if voip.ms fails, then we can't do anything so drop the call

This works mostly but if voip.ms fails, then it fails over to the next Asterisk server then tries the above again.

ie. The call is routed like this:

REMOTE_TO_SERVER_0
SERVER_0_TO_PSTN
SERVER_0_TO_VOIPMS
REMOTE_TO_SERVER_1
SERVER_1_TO_PSTN
SERVER_1_TO_VOIPMS

Since the call hits both Asterisk servers, then two CDR entries are created. Both Asterisk servers are sharing the same database for the CDR.

Is there a way for the call to end after trying voip.ms but still be able to have failover in case SERVER_0 is down?

Let me know if you need more information or if any of my post is confusing.

Thanks

Hi

For routing configuration, you can check the following link; https://docs.telcobridges.com/tbwiki/Tmedia_Routing. For more details please contact support@telcobridges.com.

It looks like I was able to solve this by changing the Route retry action for cause code 16 (Q850 normal call clearing) to "Stop call".

The first attempt of REMOTE_TO_SERVER_X ends with reason "16_NORMAL_CALL_CLEARING".

I'm hoping this doesn't break anything else.

Thanks