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

Terry Wilson twilson at digium.com
Wed Oct 13 12:30:46 CDT 2010

This is an automatically generated e-mail. To reply, visit:

(Updated 2010-10-13 12:30:46.870006)

Review request for Asterisk Developers, Russell Bryant and David Vossel.


David suggested that instead of the END_READ sentinel frame, we could just use the AST_CONTROL_HANGUP frame. I'm still not sure why ast_softhangup() queues an ast_null_frame instead of a HANGUP, but I agree that this seems like a better way to do things.


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.

Diffs (updated)

  /branches/1.4/main/channel.c 291108 

Diff: https://reviewboard.asterisk.org/r/740/diff


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.



More information about the asterisk-dev mailing list