i have in failure route:
t_on_branch("0"); $du = "sip:127.0.0.1:5070"; xlog("L_INFO", "Pseudo variable du has value <$du>\n"); t_relay("0x01");
and i get to syslog:
Nov 6 16:33:15 test /usr/sbin/kamailio[22539]: Pseudo variable du has value sip:127.0.0.1:5070
but wireshark shows that the invite is sent according to uri host of the branch added in failure route and not to 127.0.0.1:5070.
is this a bug or is it so that $du is not supposed to have any effect in failure route?
-- juha
Hello,
On 11/06/08 16:33, Juha Heinanen wrote:
i have in failure route:
t_on_branch("0"); $du = "sip:127.0.0.1:5070"; xlog("L_INFO", "Pseudo variable du has value <$du>\n"); t_relay("0x01");
and i get to syslog:
Nov 6 16:33:15 test /usr/sbin/kamailio[22539]: Pseudo variable du has value sip:127.0.0.1:5070
but wireshark shows that the invite is sent according to uri host of the branch added in failure route and not to 127.0.0.1:5070.
is this a bug or is it so that $du is not supposed to have any effect in failure route?
set the $du before appending the branch.
Cheers, Daniel
btw: Is it really necessary to keep the old branches as "terminated" branches and make new branches in failure route? Why not reuse the same branch again?
klaus
Daniel-Constantin Mierla schrieb:
Hello,
On 11/06/08 16:33, Juha Heinanen wrote:
i have in failure route:
t_on_branch("0"); $du = "sip:127.0.0.1:5070"; xlog("L_INFO", "Pseudo variable du has value <$du>\n"); t_relay("0x01");
and i get to syslog:
Nov 6 16:33:15 test /usr/sbin/kamailio[22539]: Pseudo variable du has value sip:127.0.0.1:5070
but wireshark shows that the invite is sent according to uri host of the branch added in failure route and not to 127.0.0.1:5070.
is this a bug or is it so that $du is not supposed to have any effect in failure route?
set the $du before appending the branch.
Cheers, Daniel