Thanks for yor help, Dale
I am afraid we are testing through an SBC that does not allow SUBSCRIPtios if the user is not previously registered; with an active "expires". It does also not keep "old" subscriptions if we deregister (i.e. send Expires=0) and perform an initial registration (it considers old subscriptions linked to the old registration)

 
-----"Dale Worley" <dwor...@nortel.com> escribió: -----

Para: javier.ferreirogar...@telefonica.es
De: "Dale Worley" <dwor...@nortel.com>
Fecha: 18/03/2009 19:59
cc: sip-implementors@lists.cs.columbia.edu
Asunto: Re: [Sip-implementors] Feature tags register modification



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



_____________________________________________________________________
Mensaje analizado y protegido por Telefonica Empresas
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to