id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,backport_to_milestone,backported 959,Assertion upon receiving malformed SIP messages (thanks Andrey Kovalenko for the report),bennylp,bennylp,"Several cases of malformed incoming SIP messages will cause assertion to be raised when it should be handled as error condition: 1. Receiving ACK for non-INVITE UAS transaction will trigger '''tsx->method.id == PJSIP_INVITE_METHOD''' assertion in {{{pjsip/src/pjsip/sip_transaction.c:2978}}}. Sample output: {{{ Assertion failed: tsx->method.id == PJSIP_INVITE_METHOD, file c:\users\benny\project\pjproject\pjsip\src\pjsip\sip_transaction.c, line 2978 }}} 2. Receiving SIP response message with invalid status code (for example, ""SIP/2.0 4"") will trigger '''!""Unexpected event""''' assertion in {{{pjsip/src/pjsip/sip_transaction.c:2808}}}. Sample output: {{{ Assertion failed: !""Unexpected event"", file c:\users\benny\project\pjproject\pjsip\src\pjsip\sip_transaction.c, line 2806 }}} ",defect,closed,critical,release-1.5,pjsip,trunk,fixed,,,,