On Tue, 2009-03-17 at 23:29 +0100, javier.ferreirogar...@telefonica.es wrote: > > Thanks, Dale > > I meant subscriptions. The current sequence is > > User logs-in in operational mode A: > ->Initial REGISTER feature-tag A > ->subscription to N different event packages (common no matter which > operational mode selected) > User changes operational mode on the fly > ->automatic unsubscription to N event-packages > ->automatic deregistration feature-tag A > ->automatic initial registration feature-tag B (new Call-Id, CSeq is > set to 1) > ->automatic subscription to N event-packages > > The sequence we are wondering to explore is > > User logs-in in operational mode A: > ->Initial REGISTER feature-tag A > ->subscription to N different event packages (common no matter which > operational mode selected) > User changes operational mode on the fly > ->automatic refresh REGISTER feature-tag B > > i.e. reuse "old" subscriptions (i should have better said keep)
As you have written the question, of course you can reuse the "old" subscriptions, because the information returned to a subscription is independent of the registration status of the element that has made the subscription. Certainly, un-registering will not terminate the registration (unless you have a security mechanism that couples the two, which is not a good idea). Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
