[sr-dev] Kamailio presence and internal triggering (publishing)
Anca Vamanu
anca.vamanu at 1and1.ro
Tue Mar 6 16:40:10 CET 2012
Hi Janson,
Sorry, I skimmed through your e-mail and understood something else :).
One option to achieve this is to change the state in database with
sqlops module (eg: update presentity set body='' where username='' ).
And then you should also call the function I mentioned -
pres_refresh_watchers() .
Regards,
Anca
On 03/06/2012 05:26 PM, Jason Penton wrote:
> Hi Anca,
>
> Thanks, but not quite what I'm looking for......
>
> Cheers
> Jason
>
>
>
> On Tue, Mar 6, 2012 at 4:28 PM, Anca Vamanu <anca.vamanu at 1and1.ro
> <mailto:anca.vamanu at 1and1.ro>> wrote:
>
> Hi Jason,
>
>
> There is a way to do this - call
> *pres_refresh_watchers("sip:user at domain", "presence", "1") *from
> the script.
>
> http://www.kamailio.org/docs/modules/3.2.x/modules_k/presence.html#id2495087
>
> Regards,
> Anca
>
>
>
> On 03/06/2012 02:35 PM, Jason Penton wrote:
>> Hi All,
>>
>> Was wondering if there was a mechanism to internally (ie via
>> another module) trigger notifies on a particular presentity?
>> Looking at presence module I see there is only a handle_publish
>> (called from cfg file on PUBLISH request). I would imagine it
>> would be useful to add to the presence API a mechanism to update
>> a presentity from within Kamailio as opposed to relying on a
>> publish. I understand there is the PUA modules but from what I
>> can see these explicitly send a PUBLISH to a presence server and
>> is not what I am looking for.
>>
>> My scenario:
>> I need to implicitly register a user and send notifies to all
>> subscribed watchers (from another module).
>>
>> Cheers
>> Jason
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org <mailto:sr-dev at lists.sip-router.org>
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20120306/feecc00f/attachment.htm>
More information about the sr-dev
mailing list