Yes, RFC 3265 does hints enabling subscriptions using non SIP mechanism. Many Voice mail application servers do implement this mechanism. Usually, this is more suitable for integrating application servers as part of your own network where the application servers know where to send NOTIFY which is in most of the cases a configured information. This should not be allowed for end-points outside the networks.
On 2/23/07, Brett Tate <[EMAIL PROTECTED]> wrote: > > 1) Cisco is using "unsolicited Notify" for MWI or > > SIP trunk. Is there any case to use this ? > > For "unsolicited", no. However rfc3265 allows non sip messaging to > enable the subscription. Thus if a phone wants to support such behavior > for some event packages, they should allow the NOTIFY for the package > without the typical related SUBSCRIBE or REFER. > > _______________________________________________ > 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
