<p>By searching in the code, I found that the error message I had <em>no valid dlg uuid (0: - 0:)</em> is found only in the function tps_storage_update_dialog.</p>
<p>From my log file, I can say that this error message was showing during the handling of the 200 OK (of the RE-INVITE). Hence I suppose that the error message was logged by the call to the function tps_storage_update_dialog inside the function tps_response_received (tps_msg.c:900).</p>
<p>Inside the function tps_response_received , the function <em>tps_storage_update_branch</em> is called before the function <em>tps_storage_update_dialog</em>. The fact that <em>tps_storage_update_dialog</em> got called meant that the call to <em>tps_storage_update_branch</em> had succeeded.</p>
<p>In order for the function <em>tps_storage_update_branch</em> to succeed, the dialog must have been found from database.  I don't understand <strong>why tps_storage_update_branch found the dialog but tps_storage_update_dialog didn't</strong> (they use the same conditions to check for dialog validity).</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1496#issuecomment-380735829">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZVMhGiSm0uvfruTmgE7Gra-g6dUKks5tnxvbgaJpZM4TQIEB">mute the thread</a>.<img src="https://github.com/notifications/beacon/AF36ZQfmdYTkBpHuI9_iPahJLwDg68rkks5tnxvbgaJpZM4TQIEB.gif" height="1" width="1" alt="" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/kamailio/kamailio/issues/1496#issuecomment-380735829"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@qmphan in #1496: By searching in the code, I found that the error message I had *no valid dlg uuid (0: - 0:)* is found only in the function tps_storage_update_dialog.\r\n\r\nFrom my log file, I can say that this error message was showing during the handling of the 200 OK (of the RE-INVITE). Hence I suppose that the error message was logged by the call to the function tps_storage_update_dialog inside the function tps_response_received (tps_msg.c:900).\r\n\r\nInside the function tps_response_received , the function *tps_storage_update_branch* is called before the function *tps_storage_update_dialog*. The fact that *tps_storage_update_dialog* got called meant that the call to *tps_storage_update_branch* had succeeded.\r\n\r\nIn order for the function *tps_storage_update_branch* to succeed, the dialog must have been found from database.  I don't understand **why tps_storage_update_branch found the dialog but tps_storage_update_dialog didn't** (they use the same conditions to check for dialog validity).\r\n"}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1496#issuecomment-380735829"}}}</script>