From e879c53bb6bf1930a4d71d2c8472048286fe04ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Olivier=20Cr=C3=AAte?= Date: Wed, 6 Oct 2010 12:36:45 -0400 Subject: [PATCH] StreamHandler: Add signals specifying the type of DTMF event to send Some protocols specify the type of DTMF event send and the payload type just at the time when the are sent. These signals should make these easier to implement. https://bugs.freedesktop.org/show_bug.cgi?id=30662 --- spec/Media_Stream_Handler.xml | 40 ++++++++++++++++++++++++++++++++++++++-- 1 files changed, 38 insertions(+), 2 deletions(-) diff --git a/spec/Media_Stream_Handler.xml b/spec/Media_Stream_Handler.xml index c9ae78f..ee59d94 100644 --- a/spec/Media_Stream_Handler.xml +++ b/spec/Media_Stream_Handler.xml @@ -513,9 +513,9 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - + - A telephony event code as defined by RFC 4733. + A telephony event code. @@ -523,6 +523,42 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. + + + + A telephony event code as defined by RFC 4733. + + + + + The payload type to use when sending events. The value 0xFFFFFFFF + means to send with the already configured event type instead of using + the specified one. + + + + Request that a telephony event (as defined by RFC 4733) is transmitted + over this stream until StopTelephonyEvent is called. This differs from + StartTelephonyEvent in that you force the event to be transmitted + as a RFC 4733 named event, not as sound. You can also force a specific + Codec ID. + + + + + + A telephony event code as defined by RFC 4733. + + + + Request that a telephony event (as defined by RFC 4733) is transmitted + over this stream until StopTelephonyEvent is called. This differs from + StartTelephonyEvent in that you force the event to be transmitted + as sound instead of as a named event. + + -- 1.7.2.3