Changes between Initial Version and Version 1 of Ticket #718
- Timestamp:
- Feb 6, 2009 8:35:16 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #718
- Property Summary changed from Segmentaion fault when handling incoming request without rport (thanks Norma Steveley and Seth Hinze for the report) to Crash when handling incoming request without rport (thanks Norma Steveley and Seth Hinze for the report)
-
Ticket #718 – Description
initial v1 1 The Microsoft RTC stack does not put a rport in its request via which causes pjsip_get_response_addr() to set the res_addr.transport to NULL. tsx_on_state_proceeding_uas() then dereferences the transport w/o checking for NULL, which, of course, causes the exception.1 The Microsoft RTC stack does not put a rport in its request via which causes pjsip_get_response_addr() to set the res_addr.transport to NULL. tsx_on_state_proceeding_uas() then dereferences the transport w/o checking for NULL, which, of course, causes the unhandled exception/segmentation fault. 2 2 3 3 The crash occurs when 1) pjsip responds to a BYE it received from the UDP transport, where the remote SIP stack that sent the BYE does not include the rport in the Via header and 2) the UDP transport's sendto call in pjsup that sends the 200 Response returns pending. Here is the sequence of events: