So what should be the reason for the "terminated" subscription state header of that single notify, "timeout"?
Eduardo Martins PT Inovação On 4/12/06, Paul Kyzivat <[EMAIL PROTECTED]> wrote: > > > Eduardo Martins wrote: > > Hi, i'm developing a SIMPLE service and how should I handle the SIP > > SUBSCRIBE request with an Expires header of 0? Should I handle it > > like: > > > > Option 1) A new subscription with a 0 sec duration if no such > > subscription exists or a subscription refresh with a 0 sec duration if > > such subscription exists. This way it will always returns 1 Response > > and 2 NOTIFY Requests. > > > > Option 2) A special Fetch operation if no such subscription exists or > > a Subscription Removal if such subscription exists. This way it will > > only return 1 Response and 1 Notify (with SS Header 's status as > > "terminated"). > > Whether there is an existing subscription or not, this subscribe should > result in a 200 response as well as an immediate single NOTIFY > indicating that the subscription has been terminated. While this may be > used as a "fetch" operation, its behavior isn't special. > > Paul > > > Thanks in advance for your help. Best regards, > > > > Eduardo Martins > > PT Inovação > > > > _______________________________________________ > > 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
