I've noticed this weird problem in xlog for several years/several versions
and it just happened to me again.
It could catch someone out so I thought I should report it:

xlog("L_WARN", "NAT detected in request from $si.  Call-ID=$ci\n");
...opensips will fail to start

xlog("L_WARN", "NAT detected in request from $si   Call-ID=$ci\n");
...it will start with no problem

The difference is the full stop after the $si
I think the same happens if you put a full stop after any other core pseudo
variable in the text of an xlog.

John Quick
Smartvox Limited
Web: www.smartvox.co.uk



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

Reply via email to