Hello,
I have come across this behavior in Kamailio 3.1.5 version. The proxy is behind a Firewall and uses the advertised IP to communicate to sipclients. I have used the "dlg_match_mode", as the record_route_preset() does not include the DID during call initiation. modparam("dialog", "dlg_match_mode", 2)
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 I see that the dialog is being created, and the pua_dialoginfo publishes with state "trying" and "confirmed". When the call is cancelled/408 request is generated, the pua_dialoginfo generates the xml with state=terminated.
But when the call is answered, the dialog module updates the dialog to state=4, according to the documentation mentioned below state=4 --> Terminated. 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). 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.
I have attached a log for a call, please find the attached document. I have come across a documentation about dialog module: http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-d...
Regards Gnaneshwar
Hello,
On 12/15/11 1:32 AM, Gnaneshwar Gatla wrote:
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.
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?
Cheers, Daniel
Hello Daniel,
Please find the attached patch. This patch was already submitted to Kamailio 3.1.5 by Timo Reimann. The patch was designed that if "override_lifetime" is not used, the value of the expires is taken from dialog module. FS#159 - Default expires value in dialog-info.
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. We use Kamailio just as a simple proxy, registrar and presence server.
My apology, I might have read the wrong documentation about the dialog module design.
Regards Gnani
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, December 15, 2011 1:42 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List Cc: Gnaneshwar Gatla; Cody Herzog Subject: Re: [SR-Users] Bug: Dialog State=*Teminated* even when the call is active
Hello,
On 12/15/11 1:32 AM, Gnaneshwar Gatla wrote: Hello,
I have come across this behavior in Kamailio 3.1.5 version. The proxy is behind a Firewall and uses the advertised IP to communicate to sipclients. I have used the "dlg_match_mode", as the record_route_preset() does not include the DID during call initiation. modparam("dialog", "dlg_match_mode", 2)
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 I see that the dialog is being created, and the pua_dialoginfo publishes with state "trying" and "confirmed". When the call is cancelled/408 request is generated, the pua_dialoginfo generates the xml with state=terminated.
But when the call is answered, the dialog module updates the dialog to state=4, according to the documentation mentioned below state=4 --> Terminated. 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.
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?
Cheers, Daniel
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). 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.
I have attached a log for a call, please find the attached document. I have come across a documentation about dialog module: http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-d...
Regards Gnaneshwar
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda
-
Daniel-Constantin Mierla -
Gnaneshwar Gatla -
Timo Reimann