[OpenSIPS-Devel] [ opensips-Bugs-2791077 ] presence: wrong NOTIFY with "reason=timeout"

[SourceForge.net]

Bugs item #2791077, was opened at 2009-05-13 12:23
Message generated for change (Comment added) made by anca_vamanu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2791077&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Iñaki Baz Castillo (ibc_sf)
Assigned to: Nobody/Anonymous (nobody)
Summary: presence: wrong NOTIFY with "reason=timeout"

Initial Comment:
OpenSIPS trunk rev 5694.

I'm experimienting some issues in NOTIFY's from presence server module. "Sometimes" (but really often) when a refresh PUBLISH arrives (matching "SIP-If-Match") presence module generates a NOTIFY with:
  Subscription-State: terminated;reason=timeout

This forces the client to terminate the current subscription dialogs and resend a new initial SUBSCRIBE. Unfortunatelly some clients (as Qutecom) seem to react wrongly when this issue. Anyhow, I think there is some bug in the presence module behaviour.

I attach a SIP trave very simple:

- Just one user 30000 at domain.org.
- It publishes its state and subscribes to its state.

Note how the NOTIFY in line 428 has a strange header value:
  Subscription-State: terminated;reason=timeout
After it, Twinkle (which recats well on it) generates a new out-of-dialog SUBSCRIBE. But if Qutecom is being used, it doesn't generate the SUBSCRIBE (probably a bug inQutecom) and the subscription dissapear from "active_watchers" table.


----------------------------------------------------------------------

>Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-05-13 14:12

Message:
Hi Inaki,

Thanks for the detailed report.
I have found the bug - the expires value was not updated in database when
a refresh Subscribe was received - and since you are using the fallback2bd
mode it caused that erroneous ending of dialog.
Please update and test again.

Thanks and regards,
Anca 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2791077&group_id=232389