[asterisk-bugs] [Asterisk 0013028]: [patch] Add support to handle incoming out-of-dialog SIP NOTIFY requests for "message-summary" event package
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 27 08:35:19 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=13028
======================================================================
Reported By: AsteriskRocks
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 13028
Category: Channels/chan_sip/NewFeature
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Target Version: Feature Tracker
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-07-08 15:34 CDT
Last Modified: 2009-10-27 08:35 CDT
======================================================================
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".
======================================================================
----------------------------------------------------------------------
(0112808) svnbot (reporter) - 2009-10-27 08:35
https://issues.asterisk.org/view.php?id=13028#c112808
----------------------------------------------------------------------
Repository: asterisk
Revision: 226060
U trunk/CHANGES
U trunk/channels/chan_sip.c
U trunk/configs/sip.conf.sample
------------------------------------------------------------------------
r226060 | file | 2009-10-27 08:35:17 -0500 (Tue, 27 Oct 2009) | 11 lines
Add support for receiving unsolicited MWI NOTIFY messages.
This change adds a configuration option to SIP peers, unsolicited_mailbox,
which
configures a virtual mailbox to use for received new/old MWI information.
This
virtual mailbox can then be used by any device supporting MWI.
(closes issue https://issues.asterisk.org/view.php?id=13028)
Reported by: AsteriskRocks
Patches:
bug_13028_chan_sip_external_mwi_20090707.patch uploaded by cmaj
(license 830)
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=226060
Issue History
Date Modified Username Field Change
======================================================================
2009-10-27 08:35 svnbot Note Added: 0112808
======================================================================
More information about the asterisk-bugs
mailing list