[OpenSIPS-Users] Pending OpenSIPS minor release
Ravi Patel
ravi.patel at ecosmob.com
Tue Aug 29 04:03:35 EDT 2017
Hi Razvan,
Thanks for your reply.
Apologize for asking in another thread.
It doesnot solve by putting t_on_failure("missed_call");
I will continue on the initial thread with the outcome.
Regards,
Ravi Patel
On Tue, Aug 29, 2017 at 1:08 PM, Răzvan Crainea <razvan at opensips.org> wrote:
> Hi, Ravi!
>
> I think Bogdan already responded you in this thread related to your
> problem[1]. This doesn't seem a bug it's just that you need to arm failure
> route inside failure_route for sequential failovers. Simply add
> t_on_failure("missed_call") before t_relay().
>
> For further discussions, please reply to the initial thread, to avoid
> poluting the release one.
>
> [1] http://lists.opensips.org/pipermail/users/2017-July/037813.html
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutionswww.opensips-solutions.com
>
> On 08/29/2017 09:26 AM, Ravi Patel wrote:
>
> Hi Team,
> I would like to add this issue to be taken care.
>
> I am facing issue with the Call Forwarding.
> I tried with the basic default config file of OpenSIPS.
>
> What I want to achieve is multi level forwarding.
> For EX: 1111 --> 2222(forward on NOANSWER) --> 3333(Forward on NOANSWER)
> --> 4444
>
> Please find the below failure_route
> failure_route[missed_call] {
> if (t_was_cancelled()) {
> exit;
> }
>
> if($rU == "2222")
> {
> $ru = "sip:3333 at XXX.XXX.XXX.XXX"
> <sip:3333 at XXX.XXX.XXX.XXX>; # It will dial 3333 when 2222 fails
> }
> else
> {
> $ru = "sip:4444 at XXX.XXX.XXX.XXX"
> <sip:4444 at XXX.XXX.XXX.XXX>; # It will dial 4444 when 3333 fails
> }
> t_relay();
> }
>
>
> So, Here 1111 --calls--> 2222 --Forward on no answer --> 3333 --Forward on
> no answer --> 4444.
> default timeout is 30 secs.
>
> 1111 to 2222: NOANSWER at 30 sec forwarded to 3333
> to 3333: NOANSWER at 30 sec forwarded to 4444
> to 4444: immidiately CANCEL the request, does not wait for timeout.
>
> At SIP client I found a quick miss call only,Here Timeout fails.
>
> Is this the default behaviour of OpenSIPS??
> or Do I need to modify something in config to achieve 2nd level forwarding?
> I have tested it with OpenSIPS 2.2.3 and 2.3.0
>
> Please Guide.
>
>
> Thanks,
> Ravi Patel
>
> On Mon, Aug 28, 2017 at 8:10 PM, Liviu Chircu <liviu at opensips.org> wrote:
>
>> Hi all,
>>
>> An OpenSIPS 2.3 minor release bump has been scheduled for Thursday, Aug
>> 31st. If you happen to have any GitHub OpenSIPS issues or mailing list bug
>> threads that have not been answered yet, please let us know as soon as
>> possible so they make it onto the fix checklist.
>>
>> Best regards,
>>
>> --
>> Liviu Chircu
>> OpenSIPS Developer
>> http://www.opensips-solutions.com
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170829/02a99fd5/attachment.html>
More information about the Users
mailing list