Issue 362: Incorrect Session Invalidation for SUBSCRIBE/NOTIFY
http://code.google.com/p/mobicents/issues/detail?id=362
New issue report by jean.deruelle:
The sip sessions are invalidated when the 200 OK to a NOTIFY comes back but
and so when all sip sessions have been invalidated the sip app session is
also invalidated, thus if a NOTIFY comes back after that the sip app
session cannot be found leading to the error described in the following
thread (start to read from narfice's message)
http://groups.google.com/group/mobicents-public/browse_thread/thread/aecd3553e5d9183c/
But from the RFC 3265 :
A subscription is destroyed when a notifier sends a NOTIFY request with a
"Subscription-State" of "terminated". If a subscription's destruction
leaves no other application state associated with the dialog, the dialog
terminates.
which means that sip sessions should keep track of the Subscription-State
and only be invalidated when it is "terminated". Thus the invalidation
process should be ok.
Issue attributes:
Status: Accepted
Owner: jean.deruelle
Labels: Type-Defect Priority-Medium Sip-Servlets-Milestone-0.7
Sip-Servlets-Subcomponent-Core-Impl Component-Sip-Servlets
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
