This is non-standard unsolicited NOTIFY. You may accepts it for
"message-summary" Event as many Voice Mail Servers are sending this
unsolicited NOTIFY request.


~Vikram
www.veraznetworks.com
On Dec 11, 2007 10:39 AM, 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" <sip:[EMAIL PROTECTED]>;tag=as50084360
>
>         To: <sip:[EMAIL PROTECTED]>
>
>         Contact: <sip:[EMAIL PROTECTED]>
>
>         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
> [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

Reply via email to