[OpenSIPS-Users] Cancel branch before failover on timeout
Ronald Cepres
rbcepres at gmail.com
Thu Jul 4 18:41:01 CEST 2013
Bogdan,
Thanks for the informative reply.
What I really want to solve is a problem I encounter when the first GW
doesnt respond after a defined timeout then Opensips does failover to next
GW. A few seconds after the call is routed to second GW, the first GW
responds with 200 OK, which may cause problems. It seems that the first GW
has a slow response time.
The solution I am thinking of to prevent this is to send a cancel to the
first GW before doing failover to next gateway. Does this make sense or is
there a better solution?
Thanks.
-Ronald
On Jul 4, 2013 11:58 PM, "Bogdan-Andrei Iancu" <bogdan at opensips.org> wrote:
> **
> Hello Ronald,
>
> When you hit the failure route, there is no ongoing branch left (doesn't
> matter how many you previously created) - so you should not worry about
> this.
>
> By SIP definition, a transaction fails (and OpenSIPS gets into failure
> route) only when all branches failed.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
>
> On 07/03/2013 10:43 PM, Ronald Cepres wrote:
>
> Hi all,
>
> Is there a way I can cancel a pending branch before doing a fail-over to
> next gateway (due to timeout from previous gateway)? This way I can make
> sure that the call to the previous gateway will not go through anymore
> after fail-over to the next gateway, thus preventing us "double-charged"
> situations if the previous gateway and the new gateway both answered the
> call.
>
> Thanks in advance.
>
>
> --
>
> Regards,
>
> Ronald
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130705/8c557185/attachment.htm>
More information about the Users
mailing list