Different DTMF per leg on same Call

[rodrigopassos]

Hi everyone, we have an yate server, and have two clients running with different DTMF types. A side A uses Inband, and side B uses RFC 2833 because the type os your cpe. Side B have a IVR, and when Side A calls to B, Yate need to offer RFC2833 because the limitantion of this IVR Server. Yate, is a B2BUA server on this scenario. Could Yate support  different DTMF Types for each call leg? Receive from A inband and send to B RFC2833? Today, we can't see it woking correctly. Inband clients work only Inband and RFC with RFC. Anyone could help about this scenario?

BR,
Rodrigo Passos

[rodrigopassos]

Only to clarify, this about dtmf transcoding.
Br,

Rodrigo

[rodrigopassos]

In yate log I could see:
2023-05-20_10:30:36.072021 <sip/1515732:NOTE> Failed to send tones '4' methods=rfc2833 [0x7f847c01fc40]
Returned false 'chan.dtmf' delay=0.003155
  thread=0x28755e0 'Engine Worker'
  data=0x7f874c0dced0
  retval='(null)'
  param['id'] = 'sip/1515731'
  param['text'] = '4'
  param['detected'] = 'inband'
  param['handlers'] = 'sip:10,pbxassist:15,conf:75,sip:100,dumb:100,callfork:100,filetransfer:100,wave:100,iax:100,jingle:100,analog:100,mgcpgw:100,sig:100,yrtp:150'
  param['sequence'] = '1'
  param['duplicate'] = 'false'
  param['module'] = 'sip'
  param['status'] = 'answered'
  param['address'] = '10.11.255.249:64989'
  param['targetid'] = 'sip/1515732'
  param['billid'] = '1677205349-772582'
  param['peerid'] = 'sip/1515732'
  param['lastpeerid'] = 'sip/1515732'
  param['answered'] = 'true'
  param['direction'] = 'incoming'
  param['domain'] = '10.11.255.131'
  param['callid'] = 'sip/R3ArPBnexQwoArpH35rEcA../7665b20a/1797993596'

[rodrigopassos]

Solved!

Code: [Select]

msg["odtmfmethods"]="rfc2833";
msg["tonedetect_in"]="yes";
msg["tonedetect_out"]="yes";