8 Dec
2011
8 Dec
'11
8:33 p.m.
Hey Timo,
I had this resolved. Problem was "record_route_preset" was deleting the dialog
"did" cookie. Making the Kamailio harder to sense the end of the dialog.
And the pua_dialog did not update the presentity table with the state information.
I had disabled the use of "did" param in the config. To fix this issue.
Regards
Gnaneshwar
-----Original Message-----
From: Timo Reimann [mailto:sr@foo-lounge.de]
Sent: Tuesday, November 01, 2011 4:40 PM
To: Gnaneshwar Gatla
Cc: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List;
Cody Herzog
Subject: Re: [SR-Users] Presence Dialog not being created
Hey Gnaneshwar,
sorry for not replying for such a long time. Real life has been keeping me busy. :)
Am 25.10.2011 um 03:04 schrieb Gnaneshwar Gatla:
I have installed the patch to the kamailio source and
compiled it. Thing is it does work fine to create a presentity with the obtaining the
dialog-expires from the session created.
It drops down to the one last problem.
The presentity information is not deleted when the user hangs-up even before the
"dialog-expires". This presence is maintained until the "Exipres"
timer, for my x-lite client that's 7200secs.
I have attached the log about this scenario.
Without knowing too much about pua_dialoginfo, I can tell from your logs that no dialog
termination was observed, therefore no "terminated" state was published. Are you
possibly not running completely stateful dialogs, e.g., replying statelessly to INVITE
requests? The dialog module cannot handle such cases yet, you need to be stateful all the
times.
Cheers,
--Timo
-----Original Message-----
From: Timo Reimann [mailto:sr@foo-lounge.de]
Sent: Saturday, October 22, 2011 2:12 AM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List
Cc: Cody Herzog; Gnaneshwar Gatla
Subject: Re: [SR-Users] Presence Dialog not being created
Hello Gnaneshwar,
Am 21.10.2011 um 22:57 schrieb Gnaneshwar Gatla:
Kamailio version: 3.1.5
I have been trying to use presence for Event:Dialog. I have used PUA_Dialoginfo module to
accomplish this task.
The PUA_dialoginfo module states that if "override_lifetime" is not used, the
value of the expires is taken from dialog module.
I have tried the module without the "override_lifetime" which did not create
the dialog in the presentity.
When used debug, I did see the xml being generated but finds the dialog
"expires=0" and deletes the xml(please find the log below).
How do I get this module working without the "override_lifetime" being used.
The problem seems to stem from the dialog module: Apparently, all dialog parameters
(including lifetime) are set during the creation of a dialog only after create callbacks
have been executed. This is why a lifetime of zero is always available to callback
functions, including the one from pua_dialoginfo, no matter what the configured lifetime
is.
I have created a little patch for 3.1 that changes the dialog module such that dialog
variables are set prior to calling creation callbacks. It's attached in this email --
would you mind giving it a try and see if it helps? In order to apply the patch, all you
need to do is check out the 3.1 branch (unless you already did so) doing
git clone --depth 1 -b 3.1 git://git.sip-router.org/sip-router sip-router
and apply the patch inside that directory like this:
cd sip-router
patch -p 1 < /patch/to/patch
Now recompile and run as usual. Please let me know if things work now.
Thanks a lot and
cheers,
--Timo