Subject: [MEDIACTRL] MRB: DTMF Support

From: Eric Burger <[email-masked]>
Date: Tue, 23 Feb 2010 04:27:47 -0800

A question came up during the review of MRB.  Currently, one of the values for DTMF support in the consumer and media server interface API is "INFO".  There are at least three incompatible INFO usages for transporting DTMF and we are about to get a fourth.  More importantly, I am not aware of any media server that can consume or generate INFO's for DTMF transport.  Anyone mind if we drop the "INFO" value for DTMF support?  The editors put it in just because they were thinking, "how does DTMF go through networks?" not "how do media servers see and handle DTMF?"

Note that by "INFO for DTMF," we mean the use of an INFO method to transport the digit information.  We do NOT mean the use of a media control protocol over INFO.  Thus, while both MSCML and MSML use INFO to *report* digits, they do NOT use INFO to *transport* digits.

So, a quick poll (responses requested!):

1. Does your media server accept or generate INFO for DTMF transport?
1a. If Yes to #1, what INFO payload format and how do you determine what payload to receive / send?

2. Would you miss removing INFO as a value for DTMF transport?