All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Problems with voice call.
Date: Tue, 14 Jul 2009 10:34:18 -0500	[thread overview]
Message-ID: <200907141034.19444.denkenz@gmail.com> (raw)
In-Reply-To: <4A5C1CA4.8060204@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]

Hi Marko,

> Hi denkenz,
>
> thanks for the reply. I was not sure about the voice call features of
> the modem. Now when I searched the answer I found out that the modem
> does not in fact support voice calls.

Yes, oFono's current implementation does not understand hardware specifics.  
The current atmodem driver assumes a fully featured modem with perfect fluency 
in 27.007 & 27.005.  Obviously this is wrong for real modems.  Mostly this is 
because we were concentrating on getting the high level features working, 
before delving into hardware specifics.

>
> I did not realize this at first, because ofono offered the possibility
> for voice calls (loaded for example the VoiceCallManager interface). For
> SMS ofonod says
>
> ofonod[7906]: SMS not supported by this modem.  If this is in error
> please submit patches to support this hardware
>
> however the modem has a support for SMS, which I also tested with the
> windows drivers that were delivered with the modem.
>

I've seen this reported at least twice now.  Which means that my SMS support 
detection in atmodem driver is probably not quite correct.  Would you be able 
to report at which point in the drivers/atmodem/sms.c initialization that this 
fails?

> Maybe there could be similar "not supported" feature for the voice call
> plugins?

27.005 defines at least some rudimentary way to detect whether SMS is supported 
by the modem or not.  Unfortunately 27.007 doesn't have an equivalent for 
voice calls.  The generic driver will do its best to figure out what is 
supported or not supported, but it will be up to the device-specific driver to 
have the final say.

Regards,
-Denis

  parent reply	other threads:[~2009-07-14 15:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  6:13 Problems with voice call Marko Saukko
2009-07-13  9:01 ` Li, Zhigang
2009-07-13 11:25 ` Marcel Holtmann
2009-07-13 15:47 ` Denis Kenzior
2009-07-14  5:50   ` Marko Saukko
2009-07-14  6:17     ` Marcel Holtmann
2009-07-14 15:34     ` Denis Kenzior [this message]
2009-07-15  5:56       ` Marko Saukko
2009-07-15 16:51         ` Denis Kenzior
2009-07-16  5:36           ` Marko Saukko
2009-07-16 14:47             ` Juha Korpi
2009-07-16 16:46               ` Denis Kenzior
2009-07-16 18:36                 ` Juha Korpi
2009-07-16 15:08             ` Denis Kenzior
2009-07-17  6:51               ` Marko Saukko
2009-07-17 15:48                 ` 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=200907141034.19444.denkenz@gmail.com \
    --to=denkenz@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.