Opened 15 years ago

Last modified 14 years ago

#1060 closed defect

Unable to register transaction (key exists) error message — at Version 1

Reported by: bennylp Owned by: bennylp
Priority: normal Milestone: release-1.7
Component: pjsip Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported:

Description (last modified by bennylp)

Transaction may fail to be created/registered to the hash table with the following error message:

"Unable to register transaction (key exists)"

It has been reported that this happened in this scenario:

  • 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.

Change History (1)

comment:1 Changed 15 years ago by bennylp

  • Description modified (diff)

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.

Note: See TracTickets for help on using tickets.