[OpenSER-Devel] PUA/PUA_MI Error:

[Anca Vamanu]

Hello,

If you set the etag parameter when sending the "Expires: 0 " command, it 
might be that it is no longer valid. This happens if you first give a 
command with Expires value grater than the maximum accepted value by 
presence module. Then, the pua will generate itself updates such that 
the cumulated period of validity to equal the Expires in the first 
request.  And for each new publish a different etag is replied.This is 
especially true if you have previously used an Expires: -1.
On the other hand, if you do not set the etag param, there was a bug in 
the hash table searching function that was fixed in version 2993, that 
applied for the commands with no etag. Have you tested with this version?

regards,
Anca Vamanu
 
Schumann Sebastian wrote:
> Dear all
>  
> After long evaluation I still have the following error and no solution 
> yet to solve it.
>  
> I am using OpenSER current trunk version, but also with older versions 
> (e.g. 2597, 2619) I am having the problem.
>  
> With version 2404 it seems to work, although I cannot use that version 
> and have to upgrade OpenSER to a newer release due to table consistencies.
>  
> When I use PUA_MI to create a Publish, everything works fine. 
> "Expires: -1" works for infinite state. But when I want to expire this 
> state ("Expires: 0"), the PUA replies:
> search_htable: record not found and later
> send_publish: request for a publish with expires 0 and no record found
>  
> There is most likely a problem in pua/hash.c or pua/send_publish.c but 
> I cannot find it.
>  
> Can anyone help?
>  
> Regards
> Sebastian
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel at lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/devel
>