Re: API Call proposal

2015-05-11 Thread Riccardo Vangelisti
We added on voicecall branch a working version of mm that implements all voice call functionalities. The voice capability is implemented on mm core but the only state permitted on an outgoing call is MM_CALL_STATE_ACTIVE because MM_CALL_STATE_DIALING and MM_CALL_STATE_RINGING_OUT states are no

Re: Modem not disconnecting when deleting current bearer (ref bug #17414)

2015-05-11 Thread Aleksander Morgado
On Sat, May 9, 2015 at 4:47 PM, Aleksander Morgado wrote: > On Fri, May 8, 2015 at 11:00 AM, Torsten Hilbrich > wrote: >> Version of modemmanager: 1.4.6 >> Version of libmbim: 1.12.2 >> Version of libqmi: 1.12.4 >> >> I noticed some unexpected behaviour of the modem manager when deleting a >> bea

Re: API Call proposal

2015-05-11 Thread Aleksander Morgado
> > We have tested new mm with these modems: > * Simcom SIM7250E > * Telit GT863-PY > * Falcom Twist > * Huawei MU709S-2 > > all modems works ! :) > Quick question; how do all these modems implement the actual voice channel? Is it a physical audio channel? Is it an audio channel going through

Re: API Call proposal

2015-05-11 Thread Riccardo Vangelisti
Il 11/05/2015 17:19, Aleksander Morgado ha scritto: We have tested new mm with these modems: * Simcom SIM7250E * Telit GT863-PY * Falcom Twist * Huawei MU709S-2 all modems works ! :) Quick question; how do all these modems implement the actual voice channel? Is it a physical audio chan