[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [telepathy] [Bug 311643] when using the call-ui to make a voip audio call there is no dialpad availa
From:       George Kiagiadakis <kiagiadakis.george () gmail ! com>
Date:       2014-05-04 22:22:42
Message-ID: bug-311643-17878-JUYLXTvprp () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=311643

--- Comment #6 from George Kiagiadakis <kiagiadakis.george@gmail.com> ---
(In reply to comment #5)
> TODO:
>  - Check with upstream (or George) as to what's going on with 
> http://telepathy.freedesktop.org/spec/Call_Content_Interface_DTMF.html
> http://telepathy.freedesktop.org/spec/Channel_Interface_DTMF.html
> 
> and whether TpQt should support both, or that ChannelInterface is legacy.
> There's a line in the spec: "The only part of this spec that should be used
> with a Call1 channel is the "InitialTones" property." Implying both are used.

Right. My interpretation of this is that in Call1 you always send DTMF tones
using the Call1.Content interface and not the Channel one. The Channel one is
used only for its InitialTones property, which is a Requestable and Immutable
property, i.e. you set it when you create the channel request and it never
changes. This interface & property is only for immediately dialing a number
using DTMF after the audio session has been established, which could be useful
for programmatically going through voice menus directly from the channel
request, or for programmatically dialing a number on an analog telephone line
that is exported through a SIP server.

So, yes, the bug is in rakia according to the spec.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]