[asterisk-bugs] [Asterisk 0013028]: [patch] Add support to handle incoming out-of-dialog SIP NOTIFY requests for "message-summary" event package

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13028 
====================================================================== 
Reported By:                AsteriskRocks
Assigned To:                otherwiseguy
====================================================================== 
Project:                    Asterisk
Issue ID:                   13028
Category:                   Channels/chan_sip/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-08 15:34 CDT
Last Modified:              2008-12-10 11:28 CST
====================================================================== 
Summary:                    [patch] Add support to handle incoming out-of-dialog
SIP NOTIFY requests for "message-summary" event package
Description: 
The existing Asterisk code rejects all incoming out of dialog SIP NOTIFY
requests with a "489 Bad Request" response. This feature adds support for
handling NOTIFY requests with "message-summary" event package. This will
allow third party telephone switches and voicemail systems to set and clear
MWI lamps to SIP phones configured on Asterisk.

With this change, Asterisk code will not reject an incoming out of dialog
NOTIFY
request by default. It will examine the "Event" header and "Content-Type"
header
before sending a response. If the event package is "message-sumary" and
the content type is "application/simple-message-summary", then Asterisk
will process the request further. Asterisk will attempt to ascertain if the
intended 
destination has subscribed for "message-summary". If an active
subscription is 
found, a NOTIFY request will be generated based on the subscription
dialog. If 
no subscription is found, then an unsolicited NOTIFY request will be
generated. 
In both cases, a successful response to the original NOTIFY requested will
be 
sent. Asterisk will continue to reject the request with 489 "Bad event"
for all 
out of dialog NOTIFY request with event package other than
"message-summary. 
Additionally, it will reject the NOTIFY request with 400 "Bad request" if
the 
message body is not formatted per RFC 3842. On receiving a NOTIFY request
for an
extension that is not currently registered, Asterisk will respond with 404
"Not 
found".

====================================================================== 

---------------------------------------------------------------------- 
 (0096112) oej (manager) - 2008-12-10 11:28
 http://bugs.digium.com/view.php?id=13028#c96112 
---------------------------------------------------------------------- 
No, I think this is inline with what we want to do in regards to clustering
and scaling. I haven't reviewed the code, so I can't make any comment in
regards to the actual implementation. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-10 11:28 oej            Note Added: 0096112                          
======================================================================