[asterisk-bugs] [Asterisk 0012962]: [patch] Change the "sip notify" CLI to allow for adding message body to the SIP NOTIFY message (Patch submission)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12962 
====================================================================== 
Reported By:                AsteriskRocks
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12962
Category:                   Channels/chan_sip/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
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:             06-30-2008 17:27 CDT
Last Modified:              07-08-2008 15:30 CDT
====================================================================== 
Summary:                    [patch] Change the "sip notify" CLI to allow for
adding message body to the SIP NOTIFY message (Patch submission)
Description: 
The existing CLI for sending NOTIFY requests to SIP peers does not allow
for adding message body. It allows for adding various SIP headers only. The
"sip notify" CLI can be used for sending MWI messages using unsolicited SIP
NOTIFY requests. This feature will allow legacy third party telephony
switches and / or voicemail systems to dial feature codes and have the
Asterisk set or clear MWI lamps on its extensions.

This change introduces a special tag in the "sip_notify.conf". By making
use of "Notify-Body" tag, Asterisk can be programmed to add one or more
lines in the outgoing NOTIFY message body.

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

---------------------------------------------------------------------- 
 AsteriskRocks - 07-08-08 15:30  
---------------------------------------------------------------------- 
I'm not familiar with AMI but a brief look at the AMI interface suggests
that it is not SIP driven. This patch allows an administrator to program
the Asterisk to react to the incoming SIP INVITE message that correspond to
a "star code" or a "Feature Access code". Also, this patch is an attempt to
fit Asterisk in a huge deployment where Asterisk is NOT the main telephony
or voice mail service provider. As an example, please consider the
following environment:

A huge corporation has a non Asterisk PBX with thousands of phones at its
corporate headquarters. This PBX also hosts a centralized voice mail. This
corporation has numerous small locations spread across a vast geographical
area. Each of the remote locations is locally serviced by an Asterisk PBX
which, in turn, is connected to the central PBX through SIP trunks. This
allows users at a remote local location stay connected and reachable to
users at the central (and other remote) location. Since the voice mail
service is also located at the central location, it should have an ability
to set / clear MWI lamps on phones located at remote locations that are
reachable only through the Asterisk PBX. The central voice mail service can
perform MWI over SIP using two different methods, a) sending unsolicited
SIP NOTIFY requests or b) sending SIP INVITE requests containing a
predefined "star code". This patch adds support to the second option where
a command line option can be used to generate a SIP NOTIFY message with an
appropriate message body to support "message summary" event package.

I hope this scenario helps justify the need for this patch to allow the
Asterisk PBX fit into complex telephony networks.

P.S. I'm in the process of submitting another patch to add support for
unsolicited NOTIFY requests for "message-summary" event package. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-08-08 15:30  AsteriskRocks  Note Added: 0089908                          
======================================================================