> if the subscriber receives a NOTIFY with > Subscription-State: active or pending and 0 expires, > should it consider the subscription terminated?
Basically yes; however it is an atypical situation usually caused when using small expiration values and vendors allowing the expiration value to decrease with delivery time. > The actual problem I'm dealing with is of even > wider scope. Our existing code was relying on > receiving NOTIFY with Subscription-State: terminated > to terminate subscriptions, which resulted in > memory leaks if the final NOTIFY is lost on the > network or is never sent, and I'm trying to plug > those leaks. Your cannot rely upon receiving SIP messages. The network and devices can always have issues keeping messages from being delivered. RFC 6665 introduced Timer N to help deal with missing NOTIFY situations. -- This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
