[asterisk-dev] [Code Review] Don't miss control frames if a call is answered and hung up very quickly

[reviewboard at asterisk.org]

> On 2010-10-13 17:15:32, David Vossel wrote:
> > DO IT!
> 
> prado wrote:
>     This change breaks the transfer capability when using FOP. (FOP uses manager to transfer calls, I could not verify the exact command yet). 
>     Reverting this patch brings transfer capability again. FOP in this case was just a tool, the point it that this patch has side effects related to call transfer. I'll do more testing about it as soon as possible and post here.
>     
>     Prado

Don't post here with new info, instead create an issue in the bug tracker.


- Terry


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


On 2010-10-13 12:30:46, Terry Wilson wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/740/
> -----------------------------------------------------------
> 
> (Updated 2010-10-13 12:30:46)
> 
> 
> Review request for Asterisk Developers, Russell Bryant and David Vossel.
> 
> 
> Summary
> -------
> 
> When an outgoing call is answered and hung up by the far end *very* quickly, we may not read any frames and therefor end up with a call that displays the wrong disposition/DIALSTATUS. The reason is because ast_queue_hangup() immediately sets the _softhangup flag on the channel and then queues the HANGUP control frame, but __ast_read refuses to read any frames if ast_check_hangup() indicates that a hangup request has been made (which it will if _softhangup is set). So, we end up losing control frames.
> 
> This change makes __ast_read continue to read frames even if a soft hangup has been requested. I believe this should be safe as we actually check farther down in __ast_read for HANGUP frames and return NULL just like we would have if we skipped the read via the goto done statement, and we don't call into any of the channel tech callbacks unless the readq is empty.
> 
> 
> This addresses bug 16946.
>     https://issues.asterisk.org/view.php?id=16946
> 
> 
> Diffs
> -----
> 
>   /branches/1.4/main/channel.c 291108 
> 
> Diff: https://reviewboard.asterisk.org/r/740/diff
> 
> 
> Testing
> -------
> 
> I have verified via sipp that when placing an outbound call that is answered and immediately hung up that the call shows up as answered (where it doesn't w/o the patch). I have also run the testsuite and verified that all tests continue to pass.
> 
> 
> Thanks,
> 
> Terry
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20101110/1234dda2/attachment.htm