Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Talk Detection:</strong></p> <p>While setting talk_detection_events=yes will enable sending AMI events out denoting when a user begins/ends talking, that may not be sufficient to configure your ConfBridge depending on several other factors.</p> <p>Whether or not a user is determined to be 'talking' depends on combinations of the dsp_talking_threshold and dsp_silence_threshold settings. If you are not receiving the talk detection events that you expect, then you may need to tweak these settings to match the audio properties that ConfBridge is receiving from its participants.</p> <p>Alternatively, you should ensure that your AMI account has sufficient class permissions to receive the Talk Detection events. The event has the EVENT_FLAG_CALL class permission, and you should be listening for the event ConfbridgeTalking.</p> <p><strong>DTMF</strong></p> <p>dtmf_passthrough has nothing to do with the actual raising of the DTMF AMI event, which is done by the channel read/write routines. dtmf_passthrough allows the DTMF key presses to be sent to the other channels in the bridge - typically, the ConfBridge application absorbs the DTMF key presses.</p> <p>With this enabled, you should see DTMF events - at a minimum - on the Bridging channel. If you aren't seeing events of any kind, you most likely don't have the appropriate class permissions set on the AMI account.</p> <p>All of that being said, I have to wonder why you're looking for the DTMF key presses. In general, actions on channels in ConfBridge should take place using the menu system implemented in ConfBridge, or using the AMI/CLI commands. You'd be hard pressed to accurately intercept and handle a channel's DTMF while it was still in the conference bridge - the channel, at that point, is in owned by the bridge layer, and anything you choose to do to that channel is almost certainly unsafe.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COHi Matt, Thanks for your response. It worked perfectly. Now I am facing another challenge. I have 20 channels in a conference so at one time 2 channels are unmuted and other 18 are muted, after after few minutes of conference I want to unmute a channel who is trying to speak, now the challenge is the person who is trying to speak is muted and I can't detect his talk events either so that I can unmute him. So is there anyway such that I can detect the talk events of a muted channel/person in confbridge.
      singulars
    2. CONo, that isn't currently possible. The TalkDetect events will fire for those channels whose audio frames are being mixed by the bridging layer - if a channel is muted, its audio frames never get to that point. To some extent, you could run into problems with that feature anyway - if someone is muted and someone else starts talking and you unmute them, why have them muted? You'd be bound to lose some of their audio in the process, which means they'd have to repeat what they said. A better process may be to give them a mechanism via a DTMF menu to notify the speaker that they'd like to talk.
      singulars
    3. COThen, you could have the speaker acknowledge them by having them unmute them. If you wanted that controlled via AMI and not by the speaker, you could have the DTMF menu bounce out to the dialplan and raise a UserEvent. You could then programmatically unmute the participant.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload