SIP redundancy

[beirut]

I have 2 SBC SIP external gateways, and I want to configure a redundancy, in case of fail over of one of them, system switch the second.
I created 2 SIP external gateways, and put them in the same pool number. But when one SBC is disconnected, 50% of outbound calls are successful.
What is the best way to configure the redundancy?

Thanks

[Turlupin]

Hi beirut,

Maybe you can configure your SBC in cluster : on the OXE you'll have only one external gateway composed by your two SBC ...
Do you have such functionality in your SBC (HA/Cluster/Stacking) ?
Can you give us the brand/model of yor SBC ?

Regards,

Turlupin

[beirut]

Model for the AudioCodes is M1000

[beirut]

So the configuration I am trying, is one SIP trunk group, with 2 ext gateways. And 2 ars routes, each associated to a gateway. I hope that works.

[thanzeel]

How do u do this configuration?

[beirut]

I create 2 Ext SIP gateway, one TG. The gateways belongs to same pool number. And I create 2 translation command table under ARS. each is associated to a gateway.
And ARS prefix, with 2 routes, will do the job, and it works..

[thanzeel]

I have 6 ext gateways... The problem i'm facing is if one gateway is not pingable it takes 20 seconds to go to the next one. And as it goes by the time also increase. Is there any solution for it..

[MrAnMo]

Hi you could use SIP option to detect if the ext gateway is still in service.

In external gateway there is a option : supervision timer. If you put a value like 10 is sends every second a option message to the gateway. The gateway has to respond with a 200 ok. If not then the gateway will put out of service and then that route can´t be used any more.

[thanzeel]

I have put a value there.... but still it shows me the same behaviour....

[MrAnMo]

I know that in R10 there is some improvement about the overflow to a other ext sip gateway when SIP options detects that there is a failure. But that information won´t help you for now.

From R10 product presentation.
Faster overflow when “SIP option” detects failure
When SIP option message is used for keep alive with external SIP gateway, it requires to send SIP option message several times (SIP standard is 5). Before that OXE puts the gateway Out Of Service (typically 32 seconds). So, Calling User has to wait a too long time before overflow to an available route occurs