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"); } if (is_method("INVITE")) { t_on_failure("MANAGE_FAILURE"); }

if (!t_relay()) { sl_reply_error(); } exit; }

On Wed, May 15, 2013 at 2:08 PM, Brandon Armstead brandon@cryy.com wrote:

Are you firing t_on_reply? Is it being called?

Sent from my iPhone

On May 15, 2013, at 11:04 AM, Robert R rob1485@gmail.com 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(status=~"[12][0-9][0-9]") { xlog("L_INFO","reply message: $T_reply_code ci:$ci"); route(NATMANAGE); } }

Adding the above line does not log the reply message number (180 or 183 or 200, ...).

Thanks, R

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users