Sebastian Report post Posted 02/17/2015 03:24 PM I have a problem with the option OTHER_LEG. For example, if the other party connection chooses {*} should be directed to the appropriate part of the script. However, we do not attempt to select DTMF on the other side. The name of the module, which supports this is "switch_disconnect_recorded_call". I send the log files. VG-logs.zip Share this post Link to post
SupportTeam Report post Posted 02/18/2015 12:26 AM Attached trace captures two * key-presses: Line 20272: 154356.535 21 13 5 ev dtmf * (45876059,42,0) ConfOtherLeg=160 Line 41970: 154709.671 21 10 4 ev dtmf * (45876082,42,0) ConfOtherLeg=169 In both cases that keypress is made while script is in module [Wait till end of recorded call], not in module [switch_disconnect_recorded_call] : 154355.340 7 13 5 state [Wait till end of recorded call] Playing wav () 154644.820 7 10 4 state [Wait till end of recorded call] Playing wav () Share this post Link to post
Sebastian Report post Posted 02/18/2015 01:15 PM Sorry for the mistake. The module, which performs this is [switch_disconnect_not_recorded_call].In the module, in the "Path" tab, we have:on {OTHER_LEG_0} goto [some_module]on {OTHER_LEG_*} goto [some_module]However, when the other side will select 0 or *, nothing happens.In VG.ini file, in section [PBX], I removed the line HangupOnDtmf. Could this be the reason? Share this post Link to post
SupportTeam Report post Posted 02/18/2015 06:12 PM Trace supplied does not capture any * presses while system is in module [switch_disconnect_not_recorded_call] : Line 97746: 155206.859 7 28 10 state [switch_disconnect_not_recorded_call] Number Input In the supplied trace there are 2 cases where * was pressed. Each time the script was is in module [Wait till end of recorded call] at the time. Share this post Link to post
Sebastian Report post Posted 02/19/2015 09:26 AM That's right, unfortunately, does not detect DTMF on the other side. Perhaps I should change some settings in the file VG.ini? Share this post Link to post
SupportTeam Report post Posted 02/19/2015 09:36 AM When DTMF keys are pressed by the person on the outgoing leg of the call? Are any keys pressed on the outgoing leg of the call detected? Or is it only that * is not detected when pressed on outgoing leg of tromboned conference call? Share this post Link to post
Sebastian Report post Posted 02/19/2015 12:22 PM DTMF keys are pressed during the call. Unfortunately, none of the keys is detected. Only the keys pressed by a caller, are working properly. Share this post Link to post
SupportTeam Report post Posted 02/27/2015 09:08 AM DTMF tone detection on outgoing legs of transferred call should work. DTMF detection events should be passed as "OTHER_LEG_X" type events to the script running on the original leg of the call. (the leg connected to originating caller). We have just setup a test on an E1 ISDN test system with a JCT series card (to replicate what you are using) and the DTMF tones from second (outgoing) leg of call are being forwarded to the original leg of call with no problems, appearing there as "OTHER_LEG_X" type events. So not sure what the issue is on your system Can you perhaps try to create a simple test situation where there is a simple 'dial and conference' transfer module and have recipient of the second leg of the call press keys after connection is made and check in traces afterwards to confirm whether you are seeing these DTMF events or not. Please try with different destination telephone numbers/handsets. Share this post Link to post
Sebastian Report post Posted 03/06/2015 04:23 PM I noticed that DTMF works on other side when I record the call. Share this post Link to post
SupportTeam Report post Posted 03/09/2015 10:51 PM DTMF event forwarding should work regardless of whether the conferenced call is being recorded or not. Share this post Link to post