[reSIProcate] [PATCH] reSUBSCRIBE will fail if the server fails to send NOTIFY

[Aron Rosenberg]

If you are using subscriptions there is a chance that the stack will not
issue a reSUBSCRIBE. The main way this can happen is if the presence
server does NOT issue a NOTIFY upon resiprocate sending out a
reSUBSCRIBE and no NOTIFY's are issued during the time of the
subscription.

 

This patch adds the reSUBSCRIBE timer upon receiving the 200 OK to the
SUBSCRIBE request instead of only adding the timer upon receipt of a
NOTIFY.

 

The OpenSER presence server currently exhibits this broken behavior.

 

There doesn't appear to be any harm to adding the timer on the 200 OK
instead of waiting for the NOTIFY and it fixes the bug of the
subscription not getting renewed later.

 

 

Aron Rosenberg

SightSpeed Inc.

http://www.sightspeed.com <http://www.sightspeed.com/> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070123/94597838/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: resiprocate_subscribe_timer.diff
Type: application/octet-stream
Size: 1246 bytes
Desc: resiprocate_subscribe_timer.diff
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070123/94597838/attachment.obj>