Robert R writes:
> Adding the above line does not log the reply message number (180 or 183 or
> 200, ...).
perhaps you don't activate the on_reply route by calling t_on_reply on
it.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-user
t_on_reply is being used only in the following block:
route[RELAY] {
# enable additional event routes for forwarded requests
# - serial forking, RTP relaying handling, a.s.o.
if (is_method("INVITE|SUBSCRIBE")) {
t_on_branch("MANAGE_BRANCH");
t_on_reply("MANAGE_REPLY");
}
Are you firing t_on_reply? Is it being called?
Sent from my iPhone
On May 15, 2013, at 11:04 AM, Robert R wrote:
> Hi,
>
> I am trying to add a log when receiving 1xx or 2xx reply message:
>
> # manage incoming replies
> onreply_route[MANAGE_REPLY] {
>xdbg("incoming reply\n");
>if(st
Hi,
I am trying to add a log when receiving 1xx or 2xx reply message:
# manage incoming replies
onreply_route[MANAGE_REPLY] {
xdbg("incoming reply\n");
if(status=~"[12][0-9][0-9]")
{
xlog("L_INFO","reply message: $T_reply_code ci:$ci");
route(NATMANAGE);
}
}
Adding the
