search

RestComm / jain-sip

Disclaimer: This repository is a git-svn mirror of the project found at http://java.net/projects/jsip whose original repository is developed collaboratively by the Advanced Networking Technologies Division at the National Institute of Standards and Technology (NIST) - an agency of the United States Department of Commerce and by a community of individual and enterprise contributors. TeleStax, Inc. will perform some productization work, new features experimentation branches, etc for its TelScale jSIP product that doesn't concern the community from the main repository hence this git repository.
http://www.restcomm.com/
142 stars 151 forks source link

183 Session Progress and UPDATE concurrently handling sometimes fails #61

Open andrew-ber opened 8 years ago

andrew-ber commented 8 years ago

App send INVITE and receives 100, 183 and UPDATE in short time. Sometimes UPDATE handling ends with "sipServerTransaction::sendMessage SIP/2.0 481 Call leg/Transaction does not exist". According to logs UPDATE handling occurs before 183 handling finally ends. While UPDATE handling SIPTransactionStack looks for dialogID calculated using toTag from UPDATE packet, but at that moment dialog stays in NULL state and it hasn't toTag part in its id. After UPDATE had been handled with error, app continued 183 processing and changed dialogId.

deruelle commented 8 years ago

Thanks @andrew-ber for reporting the issue. Which version of the stack do you use from https://mobicents.ci.cloudbees.com/job/JAIN-SIP/ ? Do you have a test case reproducing the issue ? Do you have DEBUG logs for the issue ? Do you want to work on a fix and do a pull request ?

andrew-ber commented 8 years ago

1) #259, Implementation-Version: 1.2.259 2) I don't have, but I think it can be created with use of attached logs.
3) debug log and net dump are attached to the comment. 4) thx, but I don't have such opportunity. net_dump_K12.txt DEBUG.txt

jaimecasero commented 8 years ago

I think this is related to CallID ordering enforce, we had similar issue with SUBS/NOT