Bogdan,
I set the flag with t_relay and it resolved the issue. I am able
to handle failure from t_relay now.
Thanks,
Amit
On Mon, Mar 21, 2011 at 10:33 PM, Bogdan-Andrei Iancu
bog...@opensips.org wrote:
Hi Amit,
have you set the 0x02 flag for t_relay ? See:
Hi Amit,
have you set the 0x02 flag for t_relay ? See:
http://www.opensips.org/html/docs/modules/1.6.x/tm.html#id293378
This flag will prevent the t_relay() function do internally deal with
errors (by sending back a negative reply).
Regards,
Bogdan
Amit Sharma wrote:
I tried the fix
I tried the fix from the 1.6 branch. The issue I still face is that now
t_relay returns with a value of 1 even when the relaying has failed.
How do you figure out if t_relay has failed (!t_relay()) does not work in
this case? Does a return value 1 also signify an error?
-Amit
On Tue, Mar 15,
Hi Amit,
Following your report, Anca did a fix on SVN - see:
http://lists.opensips.org/pipermail/devel/2011-March/007893.html
Please update from SVN and try again.
Regards,
Bogdan
Amit Sharma wrote:
I am facing an issue similiar to the one outlined in the thread
I am facing an issue similiar to the one outlined in the thread
http://lists.opensips.org/pipermail/users/2010-April/011783.html
I am using the latest stable version of opensips (1.6.4) and tried the
solution outlined in the thread above.
The issue I have observed is that t_relay function
