Changes between Initial Version and Version 2 of Ticket #1311


Ignore:
Timestamp:
Feb 25, 2016 4:39:52 AM (9 years ago)
Author:
nanang
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1311

    • Property Status changed from new to closed
    • Property Summary changed from Locking account to specific TCP/TLS transport will cause registration loop (thanks Tony Million for the report) to Locking account to specific TCP/TLS listener will cause registration loop (thanks Tony Million for the report)
    • Property Milestone changed from Known-Issues-and-Ideas to release-2.5
    • Property Resolution changed from to fixed
    • Property Backported unset

  • Ticket #1311 – Description

    initial v2  
    1 When PJSUA-LIB account is locked to a specific TCP or TLS transport, re-registration will occur in a loop. This happens because when specific transport is requested, TCP/TLS listener will always create a new transport for each registration request, and PJSUA-LIB will keep detecting IP address changed for the account, causing continuous reregistration. 
     1When PJSUA-LIB account is locked to a specific TCP or TLS listener, re-registration will occur in a loop. This happens because when specific listener is requested, TCP/TLS listener will always create a new transport for each registration request, and PJSUA-LIB will keep detecting IP address changed for the account, causing continuous reregistration. 
    22 
    33Note: