Hi. I read in "t_relay" doc:
-------- 0x02 - do not internally send a negative reply in case of failure. It applies only when the transaction is created. By default one is sent. Useful if you want to implement a serial forking in case of failure. --------
Could you please explain it a little more? I use failure_route with append_branch and before it OpenSer doesn't send back a negative reply to caller (in fct it would end the transaction). What the purpose of this bit option?
Thanks a lot.
Hi Iñaki,
by "failure" it means a failure of the "relay" action - so, if t_relay() is not able to forward the request (due internal error, bad RURI, bad message, etc), with no 0x02 flag, the t_relay() function will automatically send back a negative reply and return true in script. Of course, this behaviour does not allow you to do any kind of failure.
So, the idea is about the type of failure - it is a forward error (when nothing was put on network) and not a SIP failure (negative reply or timeout).
Regards, Bogdan
Iñaki Baz Castillo wrote:
Hi. I read in "t_relay" doc:
0x02 - do not internally send a negative reply in case of failure. It applies only when the transaction is created. By default one is sent. Useful if you want to implement a serial forking in case of failure.
Could you please explain it a little more? I use failure_route with append_branch and before it OpenSer doesn't send back a negative reply to caller (in fct it would end the transaction). What the purpose of this bit option?
Thanks a lot.
Hello all,
I updated the README file for this particular flag.
Regards, Ovidiu Sas
On Thu, May 29, 2008 at 11:15 AM, Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Iñaki,
by "failure" it means a failure of the "relay" action - so, if t_relay() is not able to forward the request (due internal error, bad RURI, bad message, etc), with no 0x02 flag, the t_relay() function will automatically send back a negative reply and return true in script. Of course, this behaviour does not allow you to do any kind of failure.
So, the idea is about the type of failure - it is a forward error (when nothing was put on network) and not a SIP failure (negative reply or timeout).
Regards, Bogdan
Iñaki Baz Castillo wrote:
Hi. I read in "t_relay" doc:
0x02 - do not internally send a negative reply in case of failure. It applies only when the transaction is created. By default one is sent. Useful if you want to implement a serial forking in case of failure.
Could you please explain it a little more? I use failure_route with append_branch and before it OpenSer doesn't send back a negative reply to caller (in fct it would end the transaction). What the purpose of this bit option?
Thanks a lot.
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hi Ovidiu,
Thanks for that!
Regards, Bogdan
Ovidiu Sas wrote:
Hello all,
I updated the README file for this particular flag.
Regards, Ovidiu Sas
On Thu, May 29, 2008 at 11:15 AM, Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Iñaki,
by "failure" it means a failure of the "relay" action - so, if t_relay() is not able to forward the request (due internal error, bad RURI, bad message, etc), with no 0x02 flag, the t_relay() function will automatically send back a negative reply and return true in script. Of course, this behaviour does not allow you to do any kind of failure.
So, the idea is about the type of failure - it is a forward error (when nothing was put on network) and not a SIP failure (negative reply or timeout).
Regards, Bogdan
Iñaki Baz Castillo wrote:
Hi. I read in "t_relay" doc:
0x02 - do not internally send a negative reply in case of failure. It applies only when the transaction is created. By default one is sent. Useful if you want to implement a serial forking in case of failure.
Could you please explain it a little more? I use failure_route with append_branch and before it OpenSer doesn't send back a negative reply to caller (in fct it would end the transaction). What the purpose of this bit option?
Thanks a lot.
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Iñaki Baz Castillo -
Ovidiu Sas