[OpenSIPS-Users] Query about avp in siptrace module
Ramachandran, Agalya (Contractor)
Agalya_Ramachandran at comcast.com
Mon Mar 21 16:46:29 CET 2016
Hi All,
Anyone can help me out for the below issues and questions I have?
Regards,
Agalya
From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Ramachandran, Agalya (Contractor)
Sent: Thursday, March 17, 2016 10:28 AM
To: users at lists.opensips.org
Subject: [OpenSIPS-Users] Query about avp in siptrace module
Hi,
Am Agalya and we are using opensips for our project and using "siptrace" module to trace and duplicate the sip packets to another server.
When trying to do so, am getting the below error.
Mar 2 14:48:21 poc-opensip-cmc-e-001 /usr/local/sbin/opensips[27754]: DBG:siptrace:trace_onreq_in: trace on req in
Mar 2 14:48:21 poc-opensip-cmc-e-001 /usr/local/sbin/opensips[27754]: DBG:siptrace:trace_onreq_in: nothing to trace...
I thought adding "traced_user_avp" parameter might solve the issue. I have added the below line and tested the same.
But I didn't get through the error and was still seeing the same error.
modparam("siptrace", "traced_user_avp", "$avp(traced_user)")
As a workaround, I commented the below lines in "siptrace.c" file in function trace_onreq_in(), and it worked for me.
Packets are sent to another server. Following the same I have commented the same line of code wherever it is failing for me.
By adding some debugging statements I found AVP is NULL and (!flag_trace_is_set(msg)) returns 1.
/*if( (avp==NULL) && !flag_trace_is_set(msg))
{
LM_DBG("nothing to trace...\n");
return;
}*/
Query : What is avp? And when avp is returned NULL?
What should I do in order to avoid that error without commenting the code?
Why is "traced_user_avp" parameter is used in config file?
It would be great if you help me to come out of this issue. Also am curious what causes this error message.
Regards,
Agalya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160321/7b96c156/attachment-0001.htm>
More information about the Users
mailing list