[OpenSIPS-Users] corrupted header
Jan D.
j-doedel at zonnet.nl
Wed Aug 26 08:58:43 CEST 2009
Looks like Iñaki Baz Castillo is right, could be a buggy Sip ALG, the client
is using a Zyxel P660.
Still, I want to 'catch' the frame as a 'normal' error, also because it
floods my log files with a lot of error lines. I just want to log one line,
so I added a error_route at the end of my script:
########################################################################
# Error route
########################################################################
error_route
{
xlog("L_ERROR","--- error route class=$(err.class)
level=$(err.level) info=$(err.info) rcode=$(err.rcode)
rreason=$(err.rreason) ---\n");
xlog("L_ERROR","--- error from [$si:$sp]\n+++++\n$mb\n++++\n\n");
sl_send_reply("$err.rcode", "$err.rreason");
exit;
}
But the logfile is still full of errors, the error route does not kick in:
Aug 25 14:24:43 sip3 /usr/sbin/opensips[***]: ERROR:core:parse_via: bad port
Aug 25 14:24:43 sip3 /usr/sbin/opensips[***]: ERROR:core:parse_via:
<SIP/2.0/UDP
145.*.*.22:23102:1;branch=z9hG4bK1505e2940e3e30927.2fc2d921ec4e7e4c7;rport#015#012Route:
<sip:77.*.*.104;lr;ftag=25d7b2df4a;did=5d.65ed5d61;vsf=czFwOhcxPzMxIHBzM3g9Ihg9aCxiPC5vKmIQPmZaHg-->#015#012Max-Forwards:
70#015#012From: 31***285
<sip:username0023 at my.sipserver.com>;tag=25d7b2df4a#015#012To:
<sip:05***79 at my.sipserver.com>;tag=9D821F9C-C66#015#012Call-ID:
16b79f8c2c80a9cd#015#012CSeq: 18992 BYE#015#012Authorization: Digest
username="username0023",realm="my.sipserver.com",nonce="4a93d91f0001382fafda66c1***52",uri="sip:31****79 at 212.*.*.245:5060",response="da7fdedfec2df8798ca3559f0b4cfd9e"#015#012Reason:
Q.850; cause=16; text="Normal call clearing"#015#012Supported:
timer#015#012User-Agent: HiPath 3000 V7.0 M5T SIP
Stack/4.0.26.26#015#012Content-Length: 0#015#012#015#012>
Aug 25 14:24:43 sip3 /usr/sbin/opensips[***]: ERROR:core:parse_via: parsed
so far:<SIP/2.0/UDP 145.*.*.22:23102>
Aug 25 14:24:43 sip3 /usr/sbin/opensips[***]: ERROR:core:get_hdr_field: bad
via
Aug 25 14:24:43 sip3 /usr/sbin/opensips[***]: ERROR:core:parse_msg:
message=<BYE sip:31****79 at 212.*.*.245:5060 SIP/2.0#015#012Via: SIP/2.0/UDP
145.*.*.22:23102:1;branch=z9hG4bK1505e2940e3e30927.2fc2d921ec4e7e4c7;rport#015#012Route:
<sip:77.*.*.104;lr;ftag=25d7b2df4a;did=5d.65ed5d61;vsf=czFwOhcxPzMxIHBzM3g9Ihg9aCxiPC5vKmIQPmZaHg-->#015#012Max-Forwards:
70#015#012From: 31***285
<sip:username0023 at my.sipserver.com>;tag=25d7b2df4a#015#012To:
<sip:05***79 at my.sipserver.com>;tag=9D821F9C-C66#015#012Call-ID:
16b79f8c2c80a9cd#015#012CSeq: 18992 BYE#015#012Authorization: Digest
username="username0023",realm="my.sipserver.com",nonce="4a93d91f0001382fafda66c1***52",uri="sip:31****79 at 212.*.*.245:5060",response="da7fdedfec2df8798ca3559f0b4cfd9e"#015#012Reason:
Q.850; cause=16; text="Normal call clearing"#015#012Supported:
timer#015#012User-Agent: HiPath 3000 V7.0 M5T SIP
Stack/4.0.26.26#015#012Content-Length: 0#015#012#015#012>
Aug 25 14:24:43 sip3 /usr/sbin/opensips[***]: ERROR:core:receive_msg:
parse_msg failed
Is there a way I can just 'drop' the INVITE (or whatever corrupt header is
sent) and log a normal error? I hoped the error_route could do this.
Jan
--
View this message in context: http://n2.nabble.com/corrupted-header-tp3487025p3514297.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
More information about the Users
mailing list