[Kamailio-Users] [presence] use case of a user that doesn't un-REGISTER and un-PUBLISH

[Pascal Maugeri]

I've much better results forcing an unregister of my user before doing the
register.

                unregister("location", "$fu");
                if (!save("location"))
                        sl_reply_error();

It looks that the unregister() cleans the presence tables.

I'm not sure if this is the proper way to proceed by at least it works for
me :-)

Any suggestion are welcome!
Pascal



On Thu, Jan 22, 2009 at 8:50 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:

> El Jueves, 22 de Enero de 2009, Pascal Maugeri escribió:
> > Well not really : if we use long publish expiration such as 3600s, we may
> > have no presence update during 1 hour. Solution may be to reduce expires
> to
> > few minutes but this generate a lot more SIP traffic.
>
> Could you please paste the NOTIFY sent by the presence server after user B
> has "crashed" and the restarted again (sending a new PUBLISH)?
>
> I expect that NOTIFY will contain two status and it depends on the client
> implementation which one to select for that AoR (not sure anyway, a NOTIFY
> capture would be great).
>
>
>
> --
> Iñaki Baz Castillo
>
> _______________________________________________
> Kamailio (OpenSER) - Users mailing list
> Users at lists.kamailio.org
> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20090123/041a6449/attachment.htm>