[SR-Users] pua_usrloc, PUBLISH not send when contact is deleted or expires

[Giacomo Vacca]

Hi Daniel,
This is just great. I'll test asap and report back.

Cheers,
Giacomo

From: Daniel-Constantin Mierla [mailto:miconda at gmail.com]
Sent: 27 January 2012 09:03
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List
Cc: Giacomo Vacca
Subject: Re: [SR-Users] pua_usrloc, PUBLISH not send when contact is deleted or expires

Hi Giacomo,

I patched few days ago to make pua_usrloc sending the PUBLISH also for location record expiration.

http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=bdbacf559134022856f5723a91fe7e130ceada29
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=266fa4e2cd62f58ee1f2eec2a5a83bc3028d194a

The idea is to set a branch flag for marking the contact for publishing -- pua_set_publish() can be still used actually, it sets also the branch flag internally, if the module parameter specifying the flag is set -- alternative is to use directly setbflag(index).

I was out of office and couldn't try it yet, maybe you can test and report if it is working fine.

You have to install devel version, either from git or from nightly debs:

http://www.kamailio.org/wiki/packages/debs#kamailio_development_-_nightly_builds

Cheers,
Daniel

On 1/20/12 12:56 PM, Giacomo Vacca wrote:
Thanks Daniel.
What I'd like to achieve is this: given a cluster of kamailio-based proxy/registrar, notify a separate entity whenever a contact is inserted or removed (either by deletion or expiration).

I'd like this separate entity to be stateless (i.e. don't manage expiry time), avoid using a DB as shared information and have asynchronous notifications.

This is why I thought pua_usrloc could help me, without the need of a full presence server in the architecture to manage expiry times for presentities.

What do you think could be used to achieve this?