The mechanism is such that the PUA passes the eTag that should be updated in the database into a main Kamailio process via a header in the PUBLISH. It is made aware of the new eTag by the main Kamailio process in the 200 OK.

In the scenario when the PUA has not received the 200 OK for the Trying PUBLISH before it sends the early PUBLISH, it will send the early PUBLISH with no eTag. This results in both Trying and early being inserted into the database. Only the early is updated, as it is the most recent, meaning the Trying will stick around in the table until it expires.


You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/724

Commit Summary

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.