I know that, but it's a bad idea. Regards, Brian
> -----Original Message----- > From: Sumit Garg [mailto:[EMAIL PROTECTED] > Sent: Monday, October 22, 2007 8:36 AM > To: Stucker, Brian (RICH1:AR00); Dean Willis; Christer Holmberg > Cc: sip; Adam Roach; Paul Kyzivat; Michael Procter; Elwell,John > Subject: RE: [Sip] INFO > > Unsolicited NOTIFYs are widely used for Voicemail and are allowed in > RFC3265 > Please refer to the following section.... > > > 3.2. Description of NOTIFY Behavior > NOTIFY messages are sent to inform subscribers of changes > in state to > which the subscriber has a subscription. Subscriptions > are typically > put in place using the SUBSCRIBE method; however, it is > possible that > other means have been used. > > 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. > > A NOTIFY does not terminate its corresponding > subscription; in other > words, a single SUBSCRIBE request may trigger several NOTIFY > requests. > > > > "The reasonable man adapts himself to the world; the > unreasonable one persists in trying to adapt the world to > himself. Therefore all progress depends on the unreasonable man." > -- George Bernard Shaw > > -----Original Message----- > From: Brian Stucker [mailto:[EMAIL PROTECTED] > Sent: Monday, October 22, 2007 4:24 AM > To: Dean Willis; Christer Holmberg > Cc: sip; Adam Roach; Paul Kyzivat; Michael Procter; Elwell,John > Subject: RE: [Sip] INFO > > Let me send you my "Twinkle, twinkle, MWI" script. A few > hours of having the right people's phones blinking like > they're possessed will fix that. > If not, you can still use it to create the most complicated > set of Christmas tree lights ever assembled. > > Regards, > Brian > > > -----Original Message----- > > From: Dean Willis [mailto:[EMAIL PROTECTED] > > Sent: Sunday, October 21, 2007 7:38 PM > > To: Christer Holmberg > > Cc: Paul Kyzivat; sip; Elwell, John; Michael Procter; Adam Roach; > > Stucker, Brian (RICH1:AR00) > > Subject: Re: [Sip] INFO > > > > > > On Oct 20, 2007, at 1:08 AM, Christer Holmberg wrote: > > > > > Hi Paul, > > > > > > I am talking about a proxy. > > > > > > So, you are saying that the proxy would always forward > the NOTIFY, > > > even if it does not have any state of a subscription dialog, or > > > subscription usage within a dialog? > > > > > > > Many proxies blindly forward NOTIFY. I know this because > certain very > > popular phone adapters with blue boxes use unsolicited NOTIFY for > > their message waiting indicators, and many operators seem to have > > deployed them with some success, despite much gnashing of > teeth on my > > part. > > > > -- > > Dean > > > > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol Use > [EMAIL PROTECTED] for questions on current sip > Use [EMAIL PROTECTED] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
