section 3.2 of rfc 3265 says - "If any non-SUBSCRIBE mechanisms are defined to create subscriptions,it is the responsibility of the parties defining those mechanisms to ensure that correlation of a NOTIFY message to the corresponding subscription is possible. Designers of such mechanisms are also warned to make a distinction between sending a NOTIFY message to a subscriber who is aware of the subscription, and sending a NOTIFY message to an unsuspecting node. The latter behavior is invalid, and MUST receive a "481 Subscription does not exist" response (unless some other 400- or 500-class error code is more applicable), as described in section 3.2.4. In other words, knowledge of a subscription must exist in both the subscriber and the notifier to be valid, even if installed via a non-SUBSCRIBE mechanism". So sending 481 in this case is the correct behaviour .... "Jack W. Lix" <[EMAIL PROTECTED]> wrote: Hi all,
Please confirm my understanding of subscribe for MWI. NOTIFY should not be sent to a UA unless a SUBSCRIBE has been sent to it. I'm doubting my understanding because I just got an asterisk server running and it immediately sends a NOTIFY after I REGISTER with it. The NOTIFY does not have "Subscription-State" header. Request-Line: NOTIFY sip:[EMAIL PROTECTED] SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.1.57:5060;branch=z9hG4bK03865702;rport From: "asterisk" ;tag=as50084360 To: Contact: Call-ID: [EMAIL PROTECTED] CSeq: 102 NOTIFY User-Agent: Jacks_Asterisk Max-Forwards: 70 Event: message-summary Content-Type: application/simple-message-summary Content-Length: 92 Message body Messages-Waiting: no\r\n Message-Account: sip:[EMAIL PROTECTED] Voice-Message: 0/0 (0/0)\r\n How do other UA's handle such a situation. I'm currently responding with 481. TIA, Jack _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors --------------------------------- Save all your chat conversations. Find them online. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
