The 4733 is just an update to 2833 and its basically the same in terms of our usage so you can consider the names interchangeable.
There is no way to negotiate SIP INFO DTMF so you can enable it as needed.
If you want to send INFO DTMF you can set the variable dtmf_type=info in the outbound dial string.

INFO is the most reliable when used with TCP, 2833 is more reliable over UDP.
INFO traverses the signaling patch where 2833 traverses the media so there are considerations to make.  There is no best.


On Thu, Jan 5, 2017 at 10:49 AM, Mimiko <vbvbrj@gmail.com> wrote:
Hello.

What is better to use as standard for DTMF: SIP Info or rfc2833 ? In sip
profile I can set <param name="liberal-dtmf" value="true"/> so, FS will
accept both types of DTMF standard, while FS always send rfc2833. Why FS
always send in rfc2833 and not the agreed with client like is the case
of audio codecs? Is rfc2833 in FS a rfc4733 in the code, and is named
rfc2833 in wiki?

--
Mimiko desu.

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Anthony Minessale II       ♬ @anthmfs  ♬ @FreeSWITCH  ♬

ClueCon Weekly Development Call 
☎ sip:888@conference.freeswitch.org  ☎ +19193869900