<br><div class="gmail_quote">On Fri, Mar 18, 2011 at 10:38 AM, Vlad Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div text="#000000" bgcolor="#ffffff"><div><div class="h5"><blockquote type="cite"><br>
<div class="gmail_quote">On Fri, Mar 18, 2011 at 8:47 AM, Vlad Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org" target="_blank">vladpaiu@opensips.org</a>></span>
wrote:
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div text="#000000" bgcolor="#ffffff">Still, I cannot understand
why the BYE is logged first into the DB.
Both the CDR type of accounting and the regular type of accounting are
triggered when the proxy receives the BYE, only that the CDR accounting
is triggered internally if you set the cdr_flag on the initial invite,
so by all means the CDR accounting should be first in the database.<br>
<br>
</div>
</blockquote>
<div><br>
</div>
<div>Vlad,</div>
<div>To me, this meant that it didn't see the BYE as part of the
*dialog*. Right?<br>
<br>
</div>
<div>So I've been digging on this, this morning and so far what I see
is that the client (originator) is not keeping the did tag on the
Record-Route headers in place. So when we get the BYE where we are
expecting the did tag on the Record-Route, there is *no tag at all*.</div>
<div><br>
</div>
<div>So I'm switching the dialog matching mode to DID_FALLBACK to see
if this fixes the issue. What do you think?</div>
<div><br>
</div>
<div>One way or another I'll post my findings..</div>
<div>-Brett</div></div></blockquote></div></div></div></blockquote><div><br></div><div><br></div><div>Vlad,</div><div>DID_FALLBACK did the trick! Thanks for your help.</div><div>-BRett</div><div> </div></div><br>