Changes between Initial Version and Version 2 of Ticket #1875
- Timestamp:
- Aug 6, 2015 6:34:39 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1875
- Property Status changed from new to closed
- Property Resolution changed from to fixed
- Property Summary changed from Fixed asertion in rescheduling PJSIP retransmission to Fixed assertion in rescheduling PJSIP retransmission
-
Ticket #1875 – Description
initial v2 6 6 5. 401/407 is received again as a response to packet retransmitted in step 2 7 7 6. PJSIP tries to send REGISTER with authorization again and it hit an assertion: 8 {{{pj_assert((tsx->transport_flag & TSX_HAS_PENDING_TRANSPORT) == 0);}}} 8 {{{ 9 pj_assert((tsx->transport_flag & TSX_HAS_PENDING_TRANSPORT) == 0); 10 }}} 9 11 10 12 stack trace: … … 19 21 }}} 20 22 21 The assertion is caused because in sip_transaction.c, if there is pending send and reschedule, the pending send may cause the flag TSX_HAS_PENDING_TRANSPORT to be set when sending the pending message (in tsx_send_msg()).23 The assertion is caused because in sip_transaction.c, if there is pending send and reschedule, the pending send may cause the flag TSX_HAS_PENDING_TRANSPORT to be set when sending the pending message (in {{{tsx_send_msg()}}}).