Re: [OpenSIPS-Users] Failover in case of 408 - Request Timeout

[Miteshkumar Thakkar via Users]

Thank you Bogdan,

I was experimenting with the same.
The new destination can be pre-configured destination in dispatcher module,
if I am not wrong.
Is there any way to select another destination which is received from DNS
response. Basically, I want to avoid pre-configuration of destinations.

Mitesh


On Sat, Jan 4, 2020 at 8:28 PM Bogdan-Andrei Iancu 
wrote:

> Hi Miteshkumar,
>
> To achieve failover for 408, you need to arm a failure route for your
> INVITE, see https://www.opensips.org/Documentation/Script-Routes-3-0#toc3
>
> This failure route will be trigger whenever your INVITE transaction will
> complete with a negative reply. In the failure route you can check what was
> the final negative reply (with t_check_status() from  TM module) and if
> 408, you can set a new destination and t_relay() again.
>
> Best regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit, Amsterdam, May 2020
>   https://www.opensips.org/events/Summit-2020Amsterdam/
> OpenSIPS Bootcamp, Miami, March 2020
>   https://opensips.org/training/OpenSIPS_Bootcamp_2020/
>
> On 12/26/19 12:12 PM, Miteshkumar Thakkar via Users wrote:
>
> Thanks for your response. I will try it. But, that cannot be done using
> DNS failover of TM module by any means, right?
>
> On Thu, Dec 26, 2019 at 3:17 PM David Villasmil <
> david.villasmil.w...@gmail.com> wrote:
>
>> Have you tried using the dispatcher module? Does exactly what you want.
>>
>> On Thu, 26 Dec 2019 at 08:41, Miteshkumar Thakkar via Users <
>> users@lists.opensips.org> wrote:
>>
>>> Hi,
>>>
>>> I want to achieve failover in case of 408 - Request timeout.
>>>
>>> One option I can see is DNS failover of TM Module. But, it does
>>> failover in case of 503 as well. I do not want that.
>>>
>>> I do not want failover in case of 503. I just want it, in case of 408 -
>>> Request timeout.
>>> How can I achieve this?
>>>
>>> Any help is appreciated.
>>>
>>> Thank You,
>>> Mitesh
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>> --
>> Regards,
>>
>> David Villasmil
>> email: david.villasmil.w...@gmail.com
>> phone: +34669448337
>>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] openSIPS - Dialog Replication Error

[Sharad Kumar via Users]

Hi Diptesh,


Thank you for the valuable information. I have already set 
net.ipv4.ip_nonlocal_bind =1 but still it's not working. So what I did, 
I set that value and then I added one IP to listen on both openSIPS 
instances.


listen:udp:10.10.10.111:5060

listen:tcp:10.10.10.111:5060


But what's going on is, after this openSIPS is giving me weird error  
messages. Because both servers are on AWS and are on different regions. 
So they can't be on same subnet. First server is on 10.0.0.0/24 subnet. 
And other one is on 10.0.1.0/24. Both subnets can ping each other tho. 
So what I am thinking is that instead of replicating dialogs and 
profiles, I will just store those in the database so that when first 
node fails, other one can get those from the database. I know this 
process will add some I/O on the database. But there is no work around I 
guess.



Thanks  and regards

Sharad Kumar



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users