[OpenSER-Users] Failure route after parallel forking (was "Problem with redirection (302 Moved temporarly)")

[Bogdan-Andrei Iancu]

Hi Antonio,

The problem is that you miss-understand the the parallel forking and the 
failure route mechanism. Failure route is called only when the 
transaction is completed and this means when all the branches are 
completed. So, if one of your SPAs is sending 302, this will not hit 
failure route as you still have the second branch still ringing. Only if 
the second branch will fail too, the whole transaction will fail and the 
failure route will be called.

For a better understanding, see:
    http://www.voice-sistem.ro/downloads/2007.08.29-Admin-Course/

There is detailed explanation about openser routes.

Regards,
Bogdan

Antonio Reale wrote:
> Sorry for resuming the post..
> I can't understand how to handle failure messages after parallel 
> forking. I need a particular configuration or OpenSER must handle them 
> the same way of a single message?
> I'm using OpenSER 1.2.3-tls and also using debug mode I can't see 
> nothing special.
> Thanks.
>
> Regards,
> Antonio.
>
> 2008/4/15, Antonio Reale <ant.reale at gmail.com 
> <mailto:ant.reale at gmail.com>>:
>
>     Hi all,
>     I have a Linksys SPA2102 with 2 phones configured with the same
>     account/number. If I call that number both phones ring and all is OK.
>     The problem is that if I set a call forwarding on one of the two
>     line on the SPA only one phone rings.
>     Openser receives the 302 message from the SPA but the failure
>     route that contains t_check_status("302") is not called.
>     The forwarding works if only one line is connected.
>     How can I handle the 302 in this situation?
>     Thanks in advance.
>
>     Regards,
>     Antonio.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>