Changes between Initial Version and Version 2 of Ticket #1873
- Timestamp:
- Oct 8, 2015 7:35:22 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1873
- Property Status changed from new to closed
- Property Resolution changed from to fixed
-
Ticket #1873 – Description
initial v2 2 2 3 3 Scenario: 4 1. Registration refresh for account A is on progress, and somehow another registration of the same account is issued (e.g: manually by app).5 1. First registration is sent successfully and account transport ({{{pjsua_acc.auto_rereg.reg_tp}}}) is updated properly, but the second one fails (due to another registration pending) so account transport stays NULL (not updated).4 1. Registration for account A is in progress, and DNS is in the process of resolving the hostname, hence TCP transport is not created yet and account transport ({{{pjsua_acc.auto_rereg.reg_tp}}}) is set to NULL. 5 1. Transport eventually gets created, but account transport is not updated. 6 6 1. Transport disconnection occurs, normally pjsua will release the disconnected transport from the account, however as transport pointer of account A is NULL, pjsua fails to detect and release it immediately. 7 7 - Note that the transport stays not released/destroyed until a new registration by account A (using a new transport) is issued or the account is deleted.