Gary,
Maybe take a look at the 0x02 flag for t_relay() :
http://www.opensips.org/html/docs/modules/1.12.x/tm.html#id294571
by default, t_relay() is internally sending a negative reply if not able
to send the request out (like DNS failure, bad IP, network error, etc).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 16.07.2014 10:43, Liviu Chircu wrote:
Hello,
t_relay() will only "fail" because of internal reasons (e.g. out of
mem, max number of branches exceeded, transaction has 6XX status...).
It looks like you need to use a *failure_route* [1] for your
transaction, and perform your error handling when it eventually
expires, because no replies are being sent back. You can control the
transaction timeout with the timeout variables from the TM module [2].
[1]: http://www.opensips.org/Documentation/Script-Routes-1-12#toc3
[2]: http://www.opensips.org/html/docs/modules/1.12.x/tm.html#id295701
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 07/15/2014 10:20 PM, Gary Nyquist wrote:
Hi,
Looking for some insight into the t_relay().
I am using the t_relay() to route INVITE to the Callee device (sip
client running on a mobile device).
I was expecting the t_relay() to fail (returning a -ve number), when
the sip client is not running on the mobile device.
But I find that t_relay() is not failing in this scenario.
Is this the normal behavior of t_relay()?
Thanks
-Gary
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
