From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: RE: [RFC 3/5] voicecall: Add ofono_voicecall_tty_notify api
Date: Wed, 12 Jan 2011 08:48:46 -0800 [thread overview]
Message-ID: <1294850926.3873.101.camel@aeonflux> (raw)
In-Reply-To: <B668883EB5DD7144ADFC248A72176EA802D59EA2@fioues07.ebgroup.elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Hi Jeevaka,
> >> Main reason for separate notification function is to avoid going
> >> through all the cases handled inside voicecall_notify. TTY field in
> >> ofono_call is basically for the GetProperties.
> >
> > I see. So here is the main question that comes from this now.
> > This seems to be a bit IFX specific driven API. I still have
> > no idea why they can not just indicate this via +CRING and
> > have to use CTM CALL for it.
> >
> > Are we expecting that all modems will just establish a normal
> > voice call and only later on signal that it is a TTY call?
> > Any input from different vendors other than IFX. What about STE, ISI?
>
> This notification is to inform the ME that the call is accepted as a TTY
> call
> on the remote side.
I see. Using a +X... IFX style notification would have been much nicer,
but so be it. The question still remains if all other modems do it
similar.
Btw. can you provide the mailing list with an example OFONO_AT_DEBUG=1
trace for a TTY call on IFX. I really like to see one of these.
Denis, do you want an extra voicecall_tty_notify() callback or just have
it go through the voicecall_notify() one?
Regards
Marcel
next prev parent reply other threads:[~2011-01-12 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 14:01 [RFC 0/5] Add support for TextTelephony call notifications Jeevaka Badrappan
2011-01-10 14:01 ` [RFC 1/5] types: add tty flag to ofono_call Jeevaka Badrappan
2011-01-10 14:01 ` [RFC 2/5] voicecall: Add tty property support Jeevaka Badrappan
2011-01-10 14:01 ` [RFC 3/5] voicecall: Add ofono_voicecall_tty_notify api Jeevaka Badrappan
2011-01-12 6:03 ` Marcel Holtmann
2011-01-12 8:27 ` Jeevaka.Badrappan
2011-01-12 16:29 ` Marcel Holtmann
2011-01-12 16:42 ` Jeevaka.Badrappan
2011-01-12 16:48 ` Marcel Holtmann [this message]
2011-01-13 5:19 ` Denis Kenzior
2011-01-13 9:15 ` Kai.Vehmanen
2011-01-13 9:43 ` Jeevaka.Badrappan
2011-01-13 11:08 ` Kai.Vehmanen
2011-01-10 14:01 ` [RFC 4/5] ifxmodem: Add support for tty call notifications Jeevaka Badrappan
2011-01-13 5:23 ` Denis Kenzior
2011-01-10 14:01 ` [RFC 5/5] doc: Describe TextTelephony property Jeevaka Badrappan
2011-01-12 6:00 ` Marcel Holtmann
2011-01-13 5:20 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1294850926.3873.101.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox