[asterisk-bugs] [JIRA] (ASTERISK-21954) Local channel optimization needs to take into account frame hooks on the local channels.
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Sun Jul 7 19:55:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207755#comment-207755 ]
Matt Jordan commented on ASTERISK-21954:
----------------------------------------
Should a framehook simply prevent optimization?
> Local channel optimization needs to take into account frame hooks on the local channels.
> ----------------------------------------------------------------------------------------
>
> Key: ASTERISK-21954
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-21954
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Core/Bridging
> Reporter: Richard Mudgett
> Labels: Asterisk12
>
> When a local channel determines that it can optimize, it needs to do something about any frame hooks on the local channels.
> A - bridge - L;1 -- L;2 - bridge - B
> Any frame hooks on L;1 need to be moved to B.
> Any frame hooks on L;2 need to be moved to A.
> Note:
> A frame hook moved during optimization could miss a frame from the destination channel. The frame may already be read by the destination channel because the channel thread is blocked trying to write that frame into the bridge.
> Note:
> A frame hook moved during optimization could process a variable number of frames to the destination channel again. The already processed frames could still be waiting in the write queue from the bridge for the destination channel.
> If the optimization involves multi-party bridges, the presence of frame hooks may prevent optimization.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list