Version: OpenSip 1.4.2 
OS: CentOS release 5 (Final)  x64

Under decent load, we're seeing more than a few parsing exceptions
where it appears as though some of the memory is getting overrun 
 
Examples are 
 
Feb 28 08:03:17 sip101 /usr/local/sbin/opensips[11614]:
ERROR:core:parse_via: invalid port number
<5060branch=z9hG4bK49a93615-0234-0065adf8-8162901a-4330cddf>

Since the ; has been replaced with another character, the parsing tries
to cast the string to an unsigned short, and hence the error. 
 
The via appears to come in correctly, but something is corrupting it 
 
Via: SIP/2.0/UDP 
XX.XXX.XX.XXX:5060;branch=z9hG4bK49a93615-0234-0065adf8-8162901a-4330cddf 
 
More problematically, we're seeing the same corruption take place in our 
responses to our media server, which is causing the sip parser on our media 
server to crash. 
 
Any thoughts or ideas would be appreciated? Would upgrading to 1.4.3 or 1.4.4 
resolve the issue? 
 
Thanks in advance.
Joel

p.s. more errors are attached.

Feb 28 12:03:24 sip101 /usr/local/sbin/opensips[11607]: ERROR:core:parse_cseq: 
no method found 
Feb 28 12:03:24 sip101 /usr/local/sbin/opensips[11607]: ERROR:core:parse_cseq: 
bad cseq 
Feb 28 12:03:24 sip101 /usr/local/sbin/opensips[11607]: 
ERROR:core:get_hdr_field: bad cseq 
Feb 28 12:03:24 sip101 /usr/local/sbin/opensips[11607]: ERROR:tm:t_check: reply 
cannot be parsed 
Feb 28 12:03:32 sip101 /usr/local/sbin/opensips[11607]: 
ERROR:core:parse_first_line: bad reply(status) first line 
Feb 28 12:03:32 sip101 /usr/local/sbin/opensips[11607]: 
ERROR:core:parse_first_line: at line 0 char 12:  
Feb 28 12:03:32 sip101 /usr/local/sbin/opensips[11607]: 
ERROR:core:parse_first_line: parsed so far: SIP/2.0 18  
Feb 28 12:03:32 sip101 /usr/local/sbin/opensips[11607]: ERROR:core:parse_msg: 
message=<SIP/2.0 18 Ringing
 Via: SIP/2.0/UDP x.xx.xx.xx;branch=z9hG4bK6a2e.6b4ecbb6.0
 Via: SIP/2.0/UDP 
xx.xxx.xx.xxx:5060;branch=z9hG4bK49a96e61-03c7-0004b28b-ae4f84cb-15db62d0
 From: <sip:[email protected]:5060>;tag=telstage-49b-49a96e61
 To: sip:[email protected];tag=gK0ad68245
 Call-ID: [email protected]
 CSeq: 25605 INVITE
 Record-Route: <sip:x.xx.xx.xx:5060;lr;ftag=telstage-49b-49a96e61>
 Contact: <sip:[email protected]:5060>
 Allow: INVITE,ACK,CANCEL,BYE,PRACK,UPDATE
 Content-Length: 0
 
 > 
Feb 28 12:03:32 sip101 /usr/local/sbin/opensips[11607]: ERROR:core:receive_msg: 
parse_msg failed 
Feb 28 12:04:00 sip101 /usr/local/sbin/opensips[11610]: ERROR:core:parse_via: 
bad char <
Feb 28 12:04:00 sip101 /usr/local/sbin/opensips[11610]: ERROR:core:parse_via:  
<SIP/2.0/UDP> 
Feb 28 12:04:00 sip101 /usr/local/sbin/opensips[11610]: ERROR:core:parse_via: 
parsed so far:<SIP/2.0/UDP> 
Feb 28 12:04:00 sip101 /usr/local/sbin/opensips[11610]: 
ERROR:core:get_hdr_field: bad via 
Feb 28 12:04:00 sip101 /usr/local/sbin/opensips[11610]: ERROR:core:parse_msg: 
message=<SIP/2.0 183 Session Progress
 Via: SIP/2.0/UDP> 
Feb 28 12:04:00 sip101 /usr/local/sbin/opensips[11610]: ERROR:core:receive_msg: 
parse_msg failed 
Feb 28 12:05:20 sip101 /usr/local/sbin/opensips[11608]: ERROR:core:parse_via: 
bad char <> on state 106 
Feb 28 12:05:20 sip101 /usr/local/sbin/opensips[11608]: ERROR:core:parse_via:  
<SIP/20/UDP 
xx.xxx.xx.xx:5060;branch=z9hG4bK49a96ecc-0106-006c4545-54be772d-6cb0b91f
 From: <sip:[email protected]:5060>;tag=telstage-710-49a96ecc
 To: sip:[email protected];tag=gK068761a3
 Call-ID: [email protected]
 CSeq: 16141 INVITE
 Record-Route: <sip:xxx:5060;lr;ftag=telstage-710-49a96ecc>
 Contact: <sip:+18473231...@xx:5060>
 Allow: INVITE,ACK,CANCEL,BYE,PRACK,UPDATE
 Content-Length: 0
 
 > 
Feb 28 12:05:20 sip101 /usr/local/sbin/opensips[11608]: ERROR:core:parse_via: 
parsed so far:<SIP/2> 
Feb 28 12:05:20 sip101 /usr/local/sbin/opensips[11608]: 
ERROR:core:get_hdr_field: bad via 
Feb 28 12:05:20 sip101 /usr/local/sbin/opensips[11608]: ERROR:tm:t_check: reply 
cannot be parsed 
Feb 28 12:05:20 sip101 /usr/local/sbin/opensips[11608]: ERROR:core:parse_via: 
bad char <> on state 106 
Feb 28 12:05:20 sip101 /usr/local/sbin/opensips[11608]: ERROR:core:parse_via:  
<SIP/20/UDP xx:5060;branch=z9hG4bK49a96ecc-0106-006c4545-54be772d-6cb0b91f
 From: <sip:8886087...@xx:5060>;tag=telstage-710-49a96ecc
 To: sip:+18473231...@xx;tag=gK068761a3
 Call-ID: 49a96ecc-0106-006c4544-54be772d-6cb0b...@xx
 CSeq: 16141 INVITE
 Record-Route: <sip:xx:5060;lr;ftag=telstage-710-49a96ecc>
 Contact: <sip:+18473231...@xx:5060>
 Allow: INVITE,ACK,CANCEL,BYE,PRACK,UPDATE
 Content-Length: 0
 
 > 
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to