Displaying 2 results from an estimated 2 matches for "t_on_reply".
2005 Jan 25
1
SER Prob
...uot;);
break;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
#inserted by klaus
if (method == "INVITE"){
record_route();
force_rtp_proxy();
/* set up reply processing*/
t_on_reply("1");
};
# forward to current uri now; use stateful forwarding; that
# works reliably even if we forward from TCP to UDP
if (!t_relay()) {
sl_reply_error();
};
}
#insert by klaus
onreply_route[1]{
if (status=~"[12][0-9][0-9]")
force_rtp_proxy();
}
#route[1]
#{
#if client or...
2005 Aug 29
1
SER NAT any additional requirement
...("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
#inserted by klaus
if (method=="INVITE") {
record_route();
force_rtp_proxy();
/* set up reply processing */
t_on_reply("1");
};
# forward to current uri now; use stateful
forwarding; that
# works reliably even if we forward from TCP to UDP
if (!t_relay()) {
sl_reply_error();
};
}
#inserted by klaus
# all incoming replies for t_onrepli-ed transactions
enter here
onreply_route[1] {...