Daniel,

thank you, that works! But then, currently it does not make any sense to call t_relay() with a parameter when $du is set, because the parameter is going to be ignored. The priority of either $du or the parameter of t_relay() is not really clear from the documentation. But, IMHO, the parameter of t_relay function has to have greater priority then $du. Any comments? Should I open a bug report for this?

-------- Anatoly

Hello,

it is about routing priorities. loose_route() sets the outbound proxy address. You need to reset it, so use: $du = null;

before t_relay("udp:myd...");

Cheers, Daniel

On 06/09/08 20:19, Anatoly Pidruchny wrote:

...

Hi All,

I have something like this in my script:

... if (loose_route()) { ... t_relay("udp:mydomain2.com"); ... } ...

The idea is that the initial INVITE message can be relayed to one destination (mydomain1.com). But later, for the BYE message, if that destination becomes unavailable and we know about that, then we send the message to mydomain2.com. The problem is that it does not work that way. Even if mydomain2.com is passed to t_relay, the message is still sent to mydomain1.com. It looks like the parameter is ignored when loose routing is done. Is it a bug or a feature? If it is a feature, then the documentation for the t_relay function should mention that the parameter is ignored when loose routing is done.

Another question is, how to make it send the message to mydomain2.com? Do I have to modify the message (like, modify the Route header)?

Thanks,

---

Anatoly.

---

Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users

Iñaki Baz Castillo wrote:

I agree with you. It makes sense that a explicit destination set as "t_relay()" parameter should be the final destination instead of Route headers.

Please, report a bug about it :)

Iñaki, thanks. I opened the bug report: http://sourceforge.net/tracker/index.php?func=detail&aid=1989917&gro...

--------- Anatoly