[asterisk-bugs] [JIRA] (ASTERISK-26370) bridge_softmix: softmix_bridge_write_voice doesn't handle dsp_talking_threshold correctly

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232476#comment-232476 ] 

Asterisk Team commented on ASTERISK-26370:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> bridge_softmix: softmix_bridge_write_voice doesn't handle dsp_talking_threshold correctly
> -----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26370
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26370
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_softmix
>    Affects Versions: 13.9.0
>         Environment: Any
>            Reporter: Chris Cox
>            Assignee: Chris Cox
>            Severity: Trivial
>
> The implementation currently (13.9.1) bases the return to talking state on whether or not the time being silent is less than the silence_threshold, meaning that changes to the dsp_talking_threshold in confbridge.conf have no effect here and the conference talking event gets sent too soon. I'm looking at using these talk events to send a special push-to-talk signal (voxing ptt) to a transmitter, so I am adjusting the talking threshold to try to prevent this voxing-ptt from being too sensitive (Is there a talking energy threshold somewhere that I can adjust as well?)



--
This message was sent by Atlassian JIRA
(v6.2#6252)