SIP redundancy

User avatar
CR0673
Member
Posts: 8
Joined: 10 Mar 2010 09:53

Re: SIP redundancy

Post by CR0673 »

Hi,

check the trunk COS of your SIP Trunk group. (It should be 31). Then in External services -> Trunk COS 31 try to play with parameter Timer T310 (by default 20s).
This is the timer use to overflow from one route to another one in ARS table.
thanzeel

Re: SIP redundancy

Post by thanzeel »

Dear CR0673,

Thanks a lot for your reply... Even i got the same reply from Tech support. but since the customer also using a live call centre i havent had chance to test it. Will update once its done
picki2

Re: SIP redundancy

Post by picki2 »

beirut wrote: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..
I did it in the same manner and it works but in the way I wanna change a little bit. I mean calls are directed to both external gateways alternately. How to configure the system to direct calls to 1st ext gw always, and to 2nd ext gw only when 1st is unavailable (when its state is out after OPTIONS probe)?
picki2

Re: SIP redundancy

Post by picki2 »

Problem solved. The reason call were directed to both SIP Ext GW alternately is that both were in the same Pool. Calls were load balanced. After change, and set different pool number to each SIP Ext GW everything is as I expected. Route 1 is used and route 2 only when SIP Ext GW is out of service (OPTIONS probe has no response).
Post Reply

Return to “SIP”