Hi Jack, As per the RFC 3265 section 3.2.2 Subscription-State header is mandatory in NOTIFY message. So, if Subscription-State header is not present, the endpoint is not conforming to RFC 3515 / RFC 3265
Thanks Somesh S. Shanbhag "Jack W. Lix" <[EMAIL PROTECTED]> wrote: Hi, The REFER rfc3515 indicates that refer creates a subscription. The far side sends NOTIFY messages to inform the referring party of the status of the call. Per RFC3265, a NOTIFY MUST include a subscription-state header. I'm seeing several implementations that do not include the subscription-state header. Actually, I don't have a single SIP device that DOES include the header. Further, these devices do not advertise compliance with RFC 4488. Can anyone give me a clue as to what is happening here? Thanks, Jack W. Lix RiverNet Design _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors ----------------------------------------- SIMPLICITY IS THE BEAUTY. BE NATURAL LIVE NATURAL. ----------------------------------------- Somesh S. Shanbhag Focus Area - VoIP Team (FA-VoIP) Mascon Global Limited #59/2, 100Ft Ring Road Banashankari II stage Bangalore-560070 Karnataka INDIA Website: http://www.mgl.com/ ----------------------------------------- --------------------------------- Do you Yahoo!? Get on board. You're invited to try the new Yahoo! Mail Beta. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
