Hi Stanislav,
On Fri, May 18, 2018 at 10:07:47PM +0200, Stanislav Sinyagin wrote:
> Simcom seems to be quite consistent in their support for this feature:
> it's available in 3 latest models, the 7100, 7500, and 7600 series,
> and they share the same AT command set for this.
Thanks a lot for
Hi Bob,
On Wed, May 16, 2018 at 04:10:55PM +0100, Bob Ham wrote:
> On 12/05/18 08:37, Harald Welte wrote:
>
> > As there are no modems that reliably can deliver the actual audio data via
> > USB
> > (aside some non-supported outdated experimental firmwares), we're only
> > testing
> > the
Hi Stanislav,
On Wed, May 16, 2018 at 05:15:07PM +0200, Stanislav Sinyagin wrote:
> also most mPCIE modems deliver PCI voice over dedicated wires on their
> mPCIE socket. These wires are standardized as "reserved" and most
> standard boards with mPCIE don't connect them anywhere.
This is the
On 12/05/18 08:37, Harald Welte wrote:
As there are no modems that reliably can deliver the actual audio data via USB
(aside some non-supported outdated experimental firmwares), we're only testing
the signaling plane so far.
Hi Harald,
I'm alarmed to see this statement. Can I ask what you
Hi Alexander, Joey,
On 05/12/2018 09:19 AM, Alexander Couzens wrote:
Hi Joey,
nice to hear, somebody else is using it.
The voicecall driver needs to be refactored as Denis already pointed
out on the mailinglist before it can go upstream.
If it wasn't clear from my earlier mail, I would like
Hi!
> nice to hear, somebody else is using it.
>
> The voicecall driver needs to be refactored as Denis already pointed
> out on the mailinglist before it can go upstream.
>
> The original idea of the voice_generated.c/h files was to create a
> prototype how qmi generated files should look like
Hi Joey,
> nice to hear, somebody else is using it.
>
> The voicecall driver needs to be refactored as Denis already pointed
> out on the mailinglist before it can go upstream.
>
> The original idea of the voice_generated.c/h files was to create a
> prototype how qmi generated files should look
Hi Joey,
nice to hear, somebody else is using it.
The voicecall driver needs to be refactored as Denis already pointed
out on the mailinglist before it can go upstream.
The original idea of the voice_generated.c/h files was to create a
prototype how qmi generated files should look like and then
Hi!
> > It looks like the QMI voicecall driver is just a stub with no operations
> actually implemented.
>
> I hope I'm not stealing their thunder, but Alexander Couzens at sysmocom
> seems to be working on implementing it [0]. Last fall, I had
> incoming/outgoing calls in oFono working on my
Hi Denis, Pavel, Marcel,
On Fri, May 11, 2018 at 08:02:01PM -0500, Denis Kenzior wrote:
> This reminds me... Weren't you the one who mentioned that you got voicecalls
> working on QMI devices? Does that include the circuit switched control
> operations (e.g. dial, etc) as well? Any chance that
Hi Denis and Pavel,
> It looks like the QMI voicecall driver is just a stub with no
operations actually implemented.
I hope I'm not stealing their thunder, but Alexander Couzens at sysmocom
seems to be working on implementing it [0]. Last fall, I had
incoming/outgoing calls in oFono working
Hi Harald,
ofono supports voice calls over qmi, right? Is it possible that
mdm6600 does not support them?
This reminds me... Weren't you the one who mentioned that you got
voicecalls working on QMI devices? Does that include the circuit
switched control operations (e.g. dial, etc) as
Hi Pavel,
ofono supports voice calls over qmi, right? Is it possible that
mdm6600 does not support them?
It looks like the QMI voicecall driver is just a stub with no operations
actually implemented.
Regards,
-Denis
___
ofono mailing list
Hi!
> > More explanation needed it seems:
> >
> > I can already do USB with AT commands, no multiplexer needed. We'd
> > actually prefer to go over serial (with multiplexer), because USB
> > needs to be powered down in idle, and you still need communication
> > ovre serial to know that wakeup of
14 matches
Mail list logo
