From: Mikko Lehto [msle...@gmail.com]
Let's say I want to have incoming media delivered straight to my RTP
capable household appliance (loudspeakers, TV, playstation), while
signaling is handled entirely by mobile device.
In that case, the mobile device uses SIP to contact the media source,
On 1/31/2011 6:06 PM, Mikko Lehto wrote:
I fail to understand why DTMF delivery methods in signaling path are not as
stabilized as RFC 2833/4733 is.
There are many use cases where nice features can be enabled with events
while dedicated event detector is not feasible in media path.
Paul Kyzivat pkyzi...@cisco.com wrote:
Very early on there were proprietary INFO-based DTMF methods.
For fairly good reasons, those techniques were found wanting.
Rather than do another INFO-based mechanism, KPML was defined. But it
has not never gotten traction. Meanwhile other mechanisms
From: sip-implementors-boun...@lists.cs.columbia.edu
[sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Mikko Lehto
[msle...@gmail.com]
With INFO mess, few NOTIFY event mechanisms, RFC 2833/4733 and RFC 4730
in mind, what do you think is the
Worley, Dale R (Dale) dwor...@avaya.com wrote:
2833-style DTMF is very common in pure SIP situations and is supported by
many telephone models.
Sure.
But what can you do when you have a requirement to 1) allow direct RTP
and 2) to capture keyevents for middlebox services?
--
Mikko
On Mon, Jan 31, 2011 at 6:36 PM, Mikko Lehto msle...@gmail.com wrote:
Worley, Dale R (Dale) dwor...@avaya.com wrote:
2833-style DTMF is very common in pure SIP situations and is supported by
many telephone models.
Sure.
But what can you do when you have a requirement to 1) allow direct RTP
From: Mikko Lehto [msle...@gmail.com]
2833-style DTMF is very common in pure SIP situations and is supported by
many telephone models.
Sure.
But what can you do when you have a requirement to 1) allow direct RTP
and 2) to capture keyevents for
Hi
I wish things would turnout to be more simple for INFO based events,
but it looks like DTMF Info-Package proposal¹ is not² going³ to fly.
With INFO mess, few NOTIFY event mechanisms, RFC 2833/4733 and RFC 4730
in mind, what do you think is the best practice for maximun interoperability?
I
-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Mikko Lehto
Sent: Monday, January 31, 2011 5:35 AM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Telephony DTMF adaptation
Hi
I wish things would turnout to be more simple for INFO based events, but it
looks like DTMF Info
