[asterisk-dev] [Code Review] 2623: New SIP Channel Driver - Add CLI/AMI initiated NOTIFY requests

Joshua Colp reviewboard at asterisk.org
Thu Jun 20 07:45:48 CDT 2013


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2623/#review8920
-----------------------------------------------------------



./trunk/res/res_sip_notify.c
<https://reviewboard.asterisk.org/r/2623/#comment17541>

    Building on my framework comments since this is also used for AMI where you can pass all these variables in... you may just end up having two functions.



./trunk/res/res_sip_notify.c
<https://reviewboard.asterisk.org/r/2623/#comment17542>

    This is incorrect. This is NOTIFY yarrrr.


- Joshua Colp


On June 14, 2013, 4:05 p.m., Kevin Harwell wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2623/
> -----------------------------------------------------------
> 
> (Updated June 14, 2013, 4:05 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Bugs: ASTERISK-21436
>     https://issues.asterisk.org/jira/browse/ASTERISK-21436
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> Added the ability to send unsolicited NOTIFY requests to a particular endpoint with a configured payload.  Added both CLI and AMI support.  For a given endpoint, this module will iterate over all its contacts sending the appropriate NOTIFY request to each.
> 
> 
> Diffs
> -----
> 
>   ./trunk/res/res_sip_notify.c PRE-CREATION 
>   ./trunk/res/res_sip/sip_options.c 391775 
>   ./trunk/res/res_sip/sip_configuration.c 391775 
>   ./trunk/res/res_sip/include/res_sip_private.h 391775 
>   ./trunk/res/res_sip.exports.in 391775 
>   ./trunk/include/asterisk/res_sip.h 391775 
> 
> Diff: https://reviewboard.asterisk.org/r/2623/diff/
> 
> 
> Testing
> -------
> 
> From the CLI issued the command to send a NOTIFY request to an endpoint with payload data that had been configured in sip_notify.conf.  Also connected via AMI and initiated an action to send a NOTIFY request to an endpoint with a given event type.
> 
> 
> Thanks,
> 
> Kevin Harwell
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130620/24573878/attachment.htm>


More information about the asterisk-dev mailing list