Hi Mickael,
On the second opensips (used for capturing), you should not use the
sip_capture() function - this instance will receive the HEP traffic from
the first opensips (doing the sip tracing), traffic that is
automatically detected and consumed by the sipcatpure module without
getting to the actual script.
Once again, on the opensips running sipcapture, set debug=4 and post the
output for handling the HEP package (you should see a lot of logs with DBG)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 10.12.2013 16:23, Mickael Hubert wrote:
Hi,
bad news, when I comment sip_capture() command, I have the same errors
logs.
For me, isn't sipcapture module error, no ?
_*My opensips.log:*_
/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:
<sip:[email protected]
<mailto:sip%3A%[email protected]>>;tag=3595673778-759875#015#012To: <sip:[email protected]
<mailto:sip%3A%[email protected]>;user=phone>;tag=pt49Sp92X5U3c#015#012Call-ID:
[email protected]#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>
Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[20395]:
ERROR:core:receive_msg: parse_msg failed
Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[20368]:
ERROR:core:receive_msg: parse_msg failed
Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[17228]:
ERROR:core:receive_msg: parse_msg failed
Dec 10 15:16:20 sipcapture1 /usr/local/sbin/opensips[20346]:
ERROR:core:receive_msg: parse_msg failed/
_*My opensips.cfg*_
/route {
if (!(method =~ "^(OPTIONS|NOTIFY|SUBSCRIBE)$")) {
if($si =~ "^10\.84\.8\.2")
{
xlog("L_INFO","icid ebug 4 avec si = $si\n");
#setdebug(4);
}
#sip_capture();
}
drop;
}
onreply_route {
if(!($rm =~ "^(NOTIFY|SUBSCRIBE|OPTIONS|)$")) {
#sip_capture();
}
drop;
}/
I don't understand :(
2013/12/9 Bogdan-Andrei Iancu <[email protected]
<mailto:[email protected]>>
Hello Mickael,
Somehow, the HEP messages gets into the SIP stack - it is not
consumed by the sipcapture callbacks.
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.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 09.12.2013 16:05, Mickael Hubert wrote:
Hi list,
I have an issue with sipcapture module in capture server.
When client send HEP message to capture server, I have this
message in Opensips.log:
--
Cordialement
HUBERT Mickaël
Ingénieur VOIP - Hexanet
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
