<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>Thank you all for your contributions to this thread. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>If I understood correctly.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>All DTMF signals defined in RFC4733 are supported, and similarly
they are supported to RFC2833. There are other signals defined in RFC4733
that are not implemented.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>The note from Michael “</span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:#002060'>strict in what we send and loose
in what we accept</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>” is a useful clarification. </span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#0070C0'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>Regards<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>Richard Lamkin<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'>Mettoni Group<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#0070C0'><a href="mailto:richard.lamkin@mettoni.com">richard.lamkin@mettoni.com</a>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Arsen Chaloyan [mailto:achaloyan@yahoo.com]
<br>
<b>Sent:</b> 23 April 2009 19:50<br>
<b>To:</b> freeswitch-users@lists.freeswitch.org<br>
<b>Subject:</b> Re: [Freeswitch-users] Is RFC 4733 supported ?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>> I should clarify that we support the
dtmf tones plus flash but no other tones at this time.<br>
<br>
Seems you have not to support other tones, because they are declared as
deprecated in RFC4733 (See also a companion RFC4734). Flash is deprecated
either, however supporting flash ensures backward compatibility. Anyway it's
used only by a few gateways. <br>
<br>
RFC 2833 caused me a lot of headaches in the past, there were 13 drafts over
2833, if I'm not mistaken, before they finally published 4733.<br>
It indeed contains some clarifications, while it's mostly backward compatible
with 2833.<br>
The most ridiculous part in out of band implementation is robustness against
network conditions and interference of in-band and out-of-band tones (SIP ->
PSTN) , surely not counting robustness against broken implementations (from
Asterisk 1.2 times).<br>
<br>
Anyway, section "2.5.2.2. Playout of Tone Events in RFC4733" deserves
careful reading.<br>
<br>
Regards,<br>
Arsen.<o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Date: Thu, 23 Apr 2009 11:48:39 -0400<br>
From: Michael Jerris <<a href="mailto:mike@jerris.com">mike@jerris.com</a>><br>
Subject: Re: [Freeswitch-users] Is RFC 4733 supported ?<br>
To: <a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a><br>
Message-ID: <<a href="mailto:909FF661-266E-47D1-A881-52D54C99ACCB@jerris.com">909FF661-266E-47D1-A881-52D54C99ACCB@jerris.com</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<br>
<br>
I should clarify that we support the dtmf tones plus flash but no <br>
other tones at this time.<br>
<br>
Mike<br>
<br>
On Apr 23, 2009, at 11:17 AM, Steve Underwood wrote:<br>
<br>
> Michael Jerris wrote:<br>
>> rfc 4733 attempts (and fails miserably) to clarify rfc2833. It<br>
>> doesn't "really" change anything of any real
substnace. Our handling<br>
>> of these packets tries very hard to be strict in what we send and<br>
>> loose in what we accept and we tend to interoperate pretty well with<br>
>> most endpoints. That being said, there are some very
broken <br>
>> endpoints<br>
>> out there (such as sonus) that require special hacks, some are<br>
>> automatic, some require settings. All that being said, we should
be<br>
>> very compliant with both 2833 and 4733, although you will generally<br>
>> see references in settings refer to 2833.<br>
> RFC4733 largely tries to clarify RFC2833 for the DTMF features. <br>
> However,<br>
> for most other signal it is very incompatible with RFC2833.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<PRE>*************************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager. http://www.mettoni.com
Mettoni Ltd
Registered in England and Wales: 4485956
9400 Garsington Road, Oxford Business Park, Oxford, OX4 2HN
*************************************************************************
</PRE></body>
</html>