Changes between Initial Version and Version 1 of Ticket #1060


Ignore:
Timestamp:
Apr 27, 2010 10:29:26 PM (15 years ago)
Author:
bennylp
Comment:

Looking at the log sent by the user, this is not related to branch param generator at all.

What happened was the call is hangup by user (presumably due to TCP disconnection) which caused CANCEL to be sent. Then shortly after that, the stack is shutdown by the application, and PJSUA-LIB hangs up all active calls, causing another CANCEL to be sent. Since the first CANCEL transaction has not been completed, the second CANCEL would fail with that "key exists" error.

I think this is fine, unless it caused crash or similar problems.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1060 – Description

    initial v1  
    44 
    55It has been reported that this happened in this scenario: 
    6  - in simulated very bad network conditions, with modified Wifi router's iptable to reject certain TCP packets. When TCP disconnect event is received, renew the registration if account id is valid or start SIP registration from the beginning 
     6 - in simulated very bad network conditions, with modified Wifi router's iptable to reject certain TCP packets. When TCP disconnect event is received, renew the registration if account id is valid or start SIP registration from the beginning. Thanks Tamàs Solymosi for the report.