If you wait until the expiration time has expired before resubscribing,
and you attempt the resubscribe within the old dialog (as you should),
then it will likely (should) be rejected with a 481. And it may well
pass on the wire a notify telling you that the old subscription expired.
So what you got may be entirely correct.
You should resubscribe well before the old subscription expires.
Paul
[EMAIL PROTECTED] wrote:
> From: "Hagai Sela \(TA\)" <[EMAIL PROTECTED]>
>
> I have a subscribe / notify based DTMF relay mechanism, in which I am
> the UAC (I send SUBSCRIBE).
> I have the following situation: I send an outbound SUBSCRIBE, and it
> receives 200 OK with an "expires" value. I then re-subscribe when that
> time has elapsed, and then I get some error code.
> Now I get NOTIFY, which I shouldn't get because the subscription request
> has failed. Which response code should I return for this NOTIFY request?
>
> You should get a NOTIFY right at the end of the subscription,
> informing you that the subscription is ended. I suppose this might
> arrive slightly after the scheduled end of the subscription.
>
> Of course, you should re-SUBSCRIBE well before the end of the
> subscription time.
>
> If you receive a NOTIFY for a subscription that has just expired, you
> should probably respond with 481 (meaning, subscription does not
> exist), although 200 seems plausible as well.
>
> Dale
> _______________________________________________
> 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
