Yes, in this case you are out of luck. You can't get back to that
subscription.
Paul
Frank Shearar wrote:
> Following on from my previous question, say I send A a REFER. A tells me the
> subscription's duration. I'm too lazy to respond quick enough with a
> resubscription, and A sends me a NOTIFY with "Subscription-State:
> terminated;reason=timeout".
>
> How can I resubscribe?
>
> Remember that RFC 3515 says "follow the procedure in RFC 3265". RFC 3265
> says in section 3.2.4 "Subscriber NOTIFY Behavior"
>
> timeout: The subscription has been terminated because it was not
> refreshed before it expired. Clients MAY re-subscribe
> immediately. The "retry-after" parameter has no semantics for
> "timeout".
>
> Of course, if you try that with a REFER you end up creating a SUBSCRIBE with
> "Event: refer" that does not match any existing subscription, and A rightly
> rejects the SUBSCRIBE with a 403 Forbidden (as per RFC 3515 section 2.4.4).
>
> Is it simply the case that you CAN'T resubscribe this implicit REFER? If I
> sent another REFER, it's not quite the same as a normal SUBSCRIBE. (I'm not
> asking for state change notifications, I'm asking A to do something.)
>
> frank
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
