Ticket #4 (new defect)

Opened 12 years ago

Last modified 8 years ago

Bug in message framing detection

Reported by: bennylp Owned by: bennylp
Priority: major Milestone: Known-Issues-and-Ideas
Component: pjsip Version:
Keywords: Cc:
Backport to 1.x milestone: Backported:

Description (last modified by bennylp) (diff)

For TCP, if the remainder of a message contains garbage, it will cause the next valid message to be discarded. For example, consider the following:

INVITE sip:user@company.com SIP/2.0
To: sip:j.user@company.com
From: sip:caller@university.edu
Call-ID: 0ha0isndaksdj@10.0.0.1
CSeq: 8 INVITE
Via: SIP/2.0/TCP 135.180.130.133
Content-Type: application/sdp
Content-Length: 138

v=0
o=mhandley 29739 7272939 IN IP4 126.5.4.3
c=IN IP4 135.180.130.88
m=audio 49210 RTP/AVP 0 12
m=video 3227 RTP/AVP 31
a=rtpmap:31 LPC/8000
asdpasd08asdsdk:;;asd
 a0sdjhg8a0''...'';;;;

With current parsing, the garbage will be prepended to the next message, and it will cause the parsing of the next message to fail.

Change History

comment:1 Changed 12 years ago by bennylp

  • Description modified (diff)

comment:2 Changed 8 years ago by bennylp

  • Milestone changed from unassigned to Known-Issues
Note: See TracTickets for help on using tickets.