Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix presence race 2 #726

Merged
merged 4 commits into from
Aug 22, 2016
Merged

Conversation

phil-lavin
Copy link
Contributor

presentity: don't update terminated presentity entries in the database

Phil Lavin added 4 commits July 22, 2016 10:49
…rting

- The presence implementation is a little dubious, to say the least.
  It probably wants re-writing at some stage. However, this fixes a
  race condition that could have a number of causes in which the PUA
  is unaware of the eTag at the point it sends the PUBLISH.
- Fixes a race condition caused by, for example, the call being answered
  at almost exactly the same time as the caller cancels. This causes
  a terminated state to change back to completed. The dialog is then
  removed from the database and the presentity entry stays in place
  until it expires.
- This fix explicitly prevents terminated entries being updated as the
  state machine in RFC 4235 prohibits this behaviour.
@miconda
Copy link
Member

miconda commented Aug 22, 2016

Thanks!

@miconda miconda merged commit 5ebbe8d into kamailio:master Aug 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants