2009/3/17 <javier.ferreirogar...@telefonica.es>: > 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)
Yes, this is correct and should work since subscriptions and registrations are completely independent. Just one consideration. You saiD: ->automatic refresh REGISTER feature-tag B I'm not sure if a REGISTER refresh would work since the Contact URI is in fact the same (the old and new Contact URI's match even if they have different params). So if you just perform a refresh REGISTER (same Call-ID, CSeq+1 and same new Contact), then most probably the registrar will not update the stored Contact URI so it would remain using the old one (feature-tag A). To avoid it you can send a REGISTER with different Call-ID. Then, since Contact matches the stored URI in the registrar, it should update the entire location. Again, it could leave untouched the URI anyway.... A des-registration and new-registration would be, for sure, the most robust aproach. Regards. -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
