<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hello Daniel,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Please find the attached patch. This patch was already submitted to Kamailio 3.1.5 by Timo Reimann.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The patch was designed that if “override_lifetime” is not used, the value of the expires is taken from dialog module.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>FS#159 - Default expires value in dialog-info.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>But still, I feel that there is something wrong in Event:dialog when the session ends with a BYE. I have used tm module to state-fully reply to all messages.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>We use Kamailio just as a simple proxy, registrar and presence server.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>My apology, I might have read the wrong documentation about the dialog module design.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Regards<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Gnani<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Daniel-Constantin Mierla [mailto:miconda@gmail.com] <br><b>Sent:</b> Thursday, December 15, 2011 1:42 AM<br><b>To:</b> SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List<br><b>Cc:</b> Gnaneshwar Gatla; Cody Herzog<br><b>Subject:</b> Re: [SR-Users] Bug: Dialog State=*Teminated* even when the call is active<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hello,<br><br><br>On 12/15/11 1:32 AM, Gnaneshwar Gatla wrote: <o:p></o:p></p><p class=MsoNormal>Hello,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I have come across this behavior in Kamailio 3.1.5 version.<o:p></o:p></p><p class=MsoNormal>The proxy is behind a Firewall and uses the advertised IP to communicate to sipclients.<o:p></o:p></p><p class=MsoNormal>I have used the “dlg_match_mode”, as the record_route_preset() does not include the DID during call initiation.<o:p></o:p></p><p class=MsoNormal style='text-indent:.5in'>modparam("dialog", "dlg_match_mode", 2)<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I’m also using pua_dialoginfo to notify users about the “Event:dialog”. I have used the attached patch to make pua_dialog info aware of the dialog<o:p></o:p></p><p class=MsoNormal>I see that the dialog is being created, and the pua_dialoginfo publishes with state “trying” and “confirmed”. <o:p></o:p></p><p class=MsoNormal>When the call is cancelled/408 request is generated, the pua_dialoginfo generates the xml with state=terminated.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>But when the call is answered, the dialog module updates the dialog to state=4, according to the documentation mentioned below state=4 --> Terminated.<o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>in which documentation says state=4 is terminated? The one for the new dialog design? If yes, that is not yet implemented. In current dialog module, the state=4 is CONFIRMED.<br><br>I checked the logs and the bye is processed by the dialog module, but there is no callback to pua_dialoginfo executed. You mention above about a patch to pua_dialogninfo, but it is not attached, only test.zip which has the debug logs. Can you send the patch or be sure it does not break registering the callbacks for pua_dialoginfo?<br><br>Cheers,<br>Daniel<br><br><br><o:p></o:p></span></p><p class=MsoNormal>I’m not aware of the event types that fires the state to termination (I have not found the documentation about events in the dialog module).<o:p></o:p></p><p class=MsoNormal>When a BYE is received to the same call, the BYE is processed and the dialog is cleared from the memory. But the pua_dialoginfo never gets the callback for the termination and the xml is never updated.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I have attached a log for a call, please find the attached document.<o:p></o:p></p><p class=MsoNormal>I have come across a documentation about dialog module:<o:p></o:p></p><p class=MsoNormal><a href="http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-design">http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-design</a><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Regards<o:p></o:p></p><p class=MsoNormal>Gnaneshwar<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br><br><o:p></o:p></span></p><pre>_______________________________________________<o:p></o:p></pre><pre>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<o:p></o:p></pre><pre><a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><o:p></o:p></pre><pre><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><o:p></o:p></pre><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br><o:p></o:p></span></p><pre>-- <o:p></o:p></pre><pre>Daniel-Constantin Mierla -- <a href="http://www.asipto.com">http://www.asipto.com</a><o:p></o:p></pre><pre><a href="http://linkedin.com/in/miconda">http://linkedin.com/in/miconda</a> -- <a href="http://twitter.com/miconda">http://twitter.com/miconda</a><o:p></o:p></pre></div></body></html>