Hi
I have 2 x ASBCEs (software ver 7.0) being used to secure SIP trunks to two separate IP Offices at separate sites. The SIP trunks are supplied to each site in an active/passive mode. This is supposed to allow all inbound calls to target the primary active SIP trunk initially. If for any reason the SIP provider cannot reach the active primary SIP endpoint then calls are targeted to the passive secondary SIP trunk. The SIP provider relies on receiving no response from the primary active SIP endpoint after 2 secs or some sort of response like a 503 Service Unavailable response code before it will send calls to the secondary passive SIP trunk.
On testing, I am able to get calls to fail over to the secondary/passive SIP trunk when the Primary ASBCE and IP Office are both down. In this scenario calls almost immediately fail over to the secondary/passive SIP trunk and work correctly as expected.
The problem I have is that when the primary ASBCE remains up but the primary IP Office is down, calls do not fail over to the passive SIP trunk.
Traces are showing that in this scenario when the primary IPO is down but the ASBCE remains up an inbound call from the SIP provider produces a SIP invite to the primary ASBCE. the SBC responds with a 100 TRYING and nothing else. The SIP provider then cannot fail over the call to the secondary SIP trunk so after 15 sec the call just disconnects and fails.
Is there any way that I can configure the primary ASBCE to respond to the SIP trunk provider with a custom response code (503 or other) after a few seconds when it gets no response from the primary IPO?
I have 2 x ASBCEs (software ver 7.0) being used to secure SIP trunks to two separate IP Offices at separate sites. The SIP trunks are supplied to each site in an active/passive mode. This is supposed to allow all inbound calls to target the primary active SIP trunk initially. If for any reason the SIP provider cannot reach the active primary SIP endpoint then calls are targeted to the passive secondary SIP trunk. The SIP provider relies on receiving no response from the primary active SIP endpoint after 2 secs or some sort of response like a 503 Service Unavailable response code before it will send calls to the secondary passive SIP trunk.
On testing, I am able to get calls to fail over to the secondary/passive SIP trunk when the Primary ASBCE and IP Office are both down. In this scenario calls almost immediately fail over to the secondary/passive SIP trunk and work correctly as expected.
The problem I have is that when the primary ASBCE remains up but the primary IP Office is down, calls do not fail over to the passive SIP trunk.
Traces are showing that in this scenario when the primary IPO is down but the ASBCE remains up an inbound call from the SIP provider produces a SIP invite to the primary ASBCE. the SBC responds with a 100 TRYING and nothing else. The SIP provider then cannot fail over the call to the secondary SIP trunk so after 15 sec the call just disconnects and fails.
Is there any way that I can configure the primary ASBCE to respond to the SIP trunk provider with a custom response code (503 or other) after a few seconds when it gets no response from the primary IPO?