[OpenSER-Users] PUA/PUA_MI: More than one Publish sent

[Anca Vamanu]

Hello Sebastian,

Indeed sometimes more that one Publish messages are sent. I will explain 
when and why.
It is possible for someone to request through the MI command to publish 
a state that should be active for 5000 seconds (you probably know that 
-1 in expires filed means infinite time). But the max expires in 
presence server is lets say 3600 sec. If no other publish request is 
received before the first one expires, the record is deleted. So, to 
respect the requested time, the pua module generates itself another 
publish when the first one is close to expire just to update the 
validity time.
Now, if for a subsequent mi command you do not sent the etag parameter ( 
set it to '.' value), the most recent etag will be found in pua module, 
and a correct Publish message will be sent.
I have just now tried the scenario you described and it works perfectly 
for me.
So, I want to ask you to say exactly what you are doing because there 
must be something you have missed out. Is the presentity uri exactly the 
same for the first and the subsequent mi requests? After how much time 
have you sent the mi request that fails?

Regards,
Anca Vamanu

Schumann Sebastian wrote:
> Dear all
>  
> I am using OpenSER 1.3.1 branch release R3936. I face some bad 
> behaviour using pua and pua_mi modules.
>  
> I publish presence states via the management interface. Sometimes, it 
> happens that multiple PUBLISH message are sent by one request. 
> Unfortunately, there is no "system" or oder when this occurs. It just 
> happens after some publications.
>  
> In case of an expiration (Expires=0, E-Tag .) it is not that bad, I 
> receive the log message: ERROR:presence:update_presentity: No E_Tag match.
>  
> In case of publication (Expires=-1, E-Tag .) it is very bad: After 
> publication, he receives also two similar messages, and threats both 
> PUBLISH messages as two different ones. Thus, creates two different 
> presentity entries with different E-Tags. If the state is expired now 
> via MI (Expires: -1, E-Tag .) only one of the E-Tags is removed. The 
> second stays in the presentity table and the user still appears online.
>  
> Any ideas what can be the reason and how to solve it?
>  
> Best regards
> Sebastian
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>