[asterisk-dev] [Code Review]: Add chan_dahdi Who Hung Up? implementation for analog and PRI/ISDN

rmudgett reviewboard at asterisk.org
Mon Jun 18 10:30:50 CDT 2012



> On June 15, 2012, 12:29 p.m., rmudgett wrote:
> > trunk/channels/sig_pri.c, lines 7286-7291
> > <https://reviewboard.asterisk.org/r/1953/diff/3/?file=28931#file28931line7286>
> >
> >     pri_event2str() is in libpri so you cannot depend upon it for strings that you are hacking like this.
> 
> opticron wrote:
>     What do you mean?  The string is not being modified.

You are assuming that the strings it gives you will be of the form "PRI_EVENT_xxx".  Why not just take the string as is?  Similarly, for sig_analog, why not take the string as is?


- rmudgett


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


On June 18, 2012, 9:22 a.m., opticron wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/1953/
> -----------------------------------------------------------
> 
> (Updated June 18, 2012, 9:22 a.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> This adds Who Hung Up? implementations for analog (not all that useful) and PRI/ISDN DAHDI technologies.
> 
> 
> This addresses bug SWP-4222.
>     https://issues.asterisk.org/jira/browse/SWP-4222
> 
> 
> Diffs
> -----
> 
>   trunk/channels/sig_analog.c 369042 
>   trunk/channels/sig_pri.c 369042 
> 
> Diff: https://reviewboard.asterisk.org/r/1953/diff
> 
> 
> Testing
> -------
> 
> Ran calls through analog and PRI/ISDN to ensure that cause codes were showing up where expected and that the HANGUPCAUSE hash was being updated as expected.
> 
> 
> Thanks,
> 
> opticron
> 
>

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


More information about the asterisk-dev mailing list