Re: [OpenSIPS-Users] Siptrace Issue

Seth Schultz Wed, 06 Feb 2013 08:25:47 -0800

Bogdan-Andrei,

Thank you for the reply. I have seen this error occur in both 1.8.2 and1.9.0. Would you please explain exactly how I can catch the error andcall abort()? Also, is there anything else I can enable which wouldhelp us track down the cause?


Thanks,
Seth

Seth Schultz
E-Mail: sschu...@scholarchip.com
Phone: 212.255.8005 x 124
Fax: 212.255.8091

On 2/6/2013 11:09 AM, Bogdan-Andrei Iancu wrote:

Hi Seth,

That is really strange - using 1.9 or 1.8 ?
Do make it short, could you put an "abort()" when the error istriggered ? -> we could look into backtrace to see where the faultystring comes from.
Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


On 02/06/2013 01:09 AM, Seth Schultz wrote:
Hello,
Could someone please help me resolve the following error message"ERROR:siptrace:pipport2su: no port specified". This error onlyhappens on some of the sip packets, but I can't determine why. Whenthis error occurs, the trace for those packets never make it to myhomer capture server (I have to use ngrep to see them).
Furthermore, I modified siptrace.c to output the value of pipport andthe error message returned this "ERROR:siptrace:pipport2su:udp:172.16.1.115 no port specified". I am just not sure where it isgetting the udp:172.16.1.115 value from.
Thanks in advance,
Seth

Here are my module parameters.
...
port=5060
listen=udp:172.16.1.115:5060
...

loadmodule "siptrace.so"
modparam("siptrace", "enable_ack_trace", 1)
modparam("siptrace", "trace_flag", "TRACE")
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "traced_user_avp", "$avp(called)")
modparam("siptrace", "hep_version", 2)
modparam("siptrace", "hep_capture_id", 338)
modparam("siptrace", "duplicate_uri", "sip:172.16.1.99:9060")
modparam("siptrace", "duplicate_with_hep", 1)

and here is how I am using siptrace in my script.

route{
...
    setflag(TRACE);
    sip_trace();
...

}

Below is a capture (from ngrep) of a packet that through this error.

INVITE sip:12063430...@yyy.yyy.yyy.yyy SIP/2.0.
Record-Route:<sip:xxx.xxx.xxx.xxx;lr;ftag=0m15597FNecKe;schip=d4c.b840a454>.
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK0533.69b5df66.1.
Via: SIP/2.0/UDP172.16.1.105;received=172.16.1.105;rport=5060;branch=z9hG4bK3Uj0ye5ve15SK.
Max-Forwards: 69.
From: "Unknown" <sip:9999999999@172.16.1.115>;tag=0m15597FNecKe.
To: <sip:19999999999@172.16.1.115>.
Call-ID: a7747eca-ea88-1230-e489-57cd493474a3.
CSeq: 39716116 INVITE.
Contact: <sip:gw+opensips@172.16.1.105:5060;transport=udp;gw=opensips>.
User-Agent: FS.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO,REGISTER, REFER, NOTIFY.
Supported: timer, precondition, path, replaces.
Allow-Events: talk, hold, refer.
Session-Expires: 120;refresher=uac.
Min-SE: 120.
Content-Type: application/sdp.
Content-Disposition: session.
Content-Length: 247.
P-Call-Type: Notification.
X-FS-Support: update_display,send_info.
Remote-Party-ID: "Unknown"<sip:9999999999@172.16.1.115>;party=calling;screen=yes;privacy=off.
.
v=0.
o=FreeSWITCH 1360080758 1360080759 IN IP4 zzz.zzz.zzz.zzz.
s=FreeSWITCH.
c=IN IP4 zzz.zzz.zzz.zzz.
t=0 0.
m=audio 29516 RTP/AVP 0 8 3 101.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=silenceSupp:off - - - -.
a=ptime:20.
a=schipmangled:yes.

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



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

Re: [OpenSIPS-Users] Siptrace Issue

Reply via email to