<div dir="ltr"><div><div>Hi,<br><br></div>bad news, when I comment sip_capture() command, I have the same errors logs.<br></div><div>For me, isn't sipcapture module error, no ?<br></div><div><br></div><u><b>My opensips.log:</b></u><br>
<div><br><div><div><i>Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[20532]: ERROR:core:parse_msg: message=<#001#020#002#001#023�#023�#012T#010#024#012T#010#012SIP/2.0 487 Request Terminated#015#012Via: SIP/2.0/UDP 10.84.8.10:5060;branch=z9hG4bKf998c339ae21d6ae6bc3bc0d477c979e#015#012From: <<a href="mailto:sip%3A%2B33XXXXXX@10.84.8.10">sip:+33XXXXXX@10.84.8.10</a>>;tag=3595673778-759875#015#012To: <<a href="mailto:sip%3A%2B33XXXXXX@10.84.8.20">sip:+33XXXXXX@10.84.8.20</a>;user=phone>;tag=pt49Sp92X5U3c#015#012Call-ID: 1648336-3595673778-759872@asbc1b.hexavoip.local#015#012CSeq: 1 INVITE#015#012User-Agent: I-SBC 2 HEXANET#015#012Accept: application/sdp#015#012Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY#015#012Supported: timer, precondition, path, replaces#015#012Allow-Events: talk, hold, conference, refer#015#012Content-Length: 0#015#012#015#012><br>
Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[20395]: ERROR:core:receive_msg: parse_msg failed<br>Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[20368]: ERROR:core:receive_msg: parse_msg failed<br>Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[17228]: ERROR:core:receive_msg: parse_msg failed<br>
Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[20346]: ERROR:core:receive_msg: parse_msg failed</i><br><br><u><b>My opensips.cfg</b></u></div><div><br><i>route {<br><br> if (!(method =~ "^(OPTIONS|NOTIFY|SUBSCRIBE)$")) {<br>
if($si =~ "^10\.84\.8\.2")<br> {<br> xlog("L_INFO","icid ebug 4 avec si = $si\n");<br> #setdebug(4);<br> }<br>
<br> #sip_capture();<br> }<br> drop;<br>}<br><br>onreply_route {<br><br> if(!($rm =~ "^(NOTIFY|SUBSCRIBE|OPTIONS|)$")) {<br> #sip_capture();<br> }<br> drop;<br>
}</i><br><br></div><div>I don't understand :(<br></div><div><br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/9 Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Mickael,<br>
<br>
Somehow, the HEP messages gets into the SIP stack - it is not consumed by the sipcapture callbacks.<br>
<br>
Try running in debug 4 mode and see if there are any messages from the sipcature module when the HEP messages is received by opensips.<br>
<br>
Regards,<br>
<br>
Bogdan-Andrei Iancu<br>
OpenSIPS Founder and Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><div class="HOEnZb"><div class="h5"><br>
<br>
On 09.12.2013 16:05, Mickael Hubert wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi list,<br>
I have an issue with sipcapture module in capture server.<br>
<br>
When client send HEP message to capture server, I have this message in Opensips.log:<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Cordialement<br><br>HUBERT Mickaël<br>Ingénieur VOIP - Hexanet<br></div>
</div>
<br>
<img src="http://www.hexanet.fr/sites/files/hexanet/files/20130205_signature_hexanet.gif">