[OpenSER-Users] openser 1.3.0 and presence module

[Anca Vamanu]

I have now read your previous comment.
It is clear that if you use anther process to modify the content of 
database, you should set the 'fal;back2db' parameter to 1 to make this 
effective in real time.
please see the documentation here:  
http://www.openser.org/docs/modules/1.3.x/presence.html

Anca Vamanu wrote:
> Hi Sigrid,
>
> First, a Notify with no body is sent in two cases:
> 1. the status of the subscription is 'pending' or 'rejected'
> 2. the server has no published information made by the user the 
> subscription is addressed to (for example, if a user subscribes to 5, 
> from which only one is registered at the time, he will receive Notifies 
> with no body for the other four ) .
>
> Second, the presence server works by default in a cache mode with 
> periodical updated in database. If a fallback to database is desired for 
> any storing or querying operation, then the "fallback2db" parameter 
> should be set. It useful only in the case of using more presence servers 
> that share the same database. In this situation it is possible not to 
> have a required info in cache, but it might have been processed by 
> another server and might be present in database.
> I think it is a wrong observation that there are no more Notifies with 
> no body if this parameter is set. The real determinant factor is whether 
> the buddies have issued a Publish before the Subscription arrives at the 
> server.
> But, if you do see a record in 'presentity' table for a user and a 
> corresponding Notify, having in its From header the uri of the 
> presentity, with no body, then there might be a bug there.
> I have to mention that I have tested this scenario right now and it 
> works for me.
>
> Regards,
> Anca Vamanu
>
> Sigrid Thijs wrote:
>   
>> Sigrid Thijs wrote:
>>
>>   
>>     
>>> Furthermore I noticed that sometimes, the presence NOTIFY requests do
>>> not contain a body. I checked the database, and there was data in the
>>> body column in the presentity table for the presence resource.
>>> The value in the status column of the watchers/active_watchers table is
>>> 1. When I restart openser, the presence descriptions are added to the
>>> NOTIFY requests again (the entry in the database did not change).
>>>
>>> I have to say that we insert some presence states directly in the 
>>> database via another process. But this is nothing more than an INSERT or 
>>> UPDATE statement on the presentity table.
>>>
>>> Do you have any idea why a NOTIFY without body is sent? Do i need to
>>> configure something extra? And why does it seem to work after openser
>>> has restarted?
>>>
>>>     
>>>       
>> Apparently there's a configuration option "fallback2db" in the presence 
>> module. When I set this value to 1, the problem is solved.
>>
>> kind regards,
>>
>> Sigrid
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.openser.org
>> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>>
>>   
>>     
>
>
> _______________________________________________
> Users mailing list
> Users at lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>
>