Re: [PATCH 1/2] linktop: reimplemented linktop plugin based on mbm

[Denis Kenzior <denkenz@gmail.com>]

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

Hi Amit,

> 
> The windows driver files have some references to ST-Ericsson and the AT
> commands
> looks more like as subset of ST-Ericsson commands then Huawei.
> 
> I have cross check the listed commands
> with http://natisbad.org/E4300/Dell_Wireless_5530_AT_cmd_ref.html and
> found lots of AT*E**** commands which are Ericsson extensions.
>  

Ok, then forget what I said earlier.  This indeed looks like an MBM clone.

>     Same with radio-settings and voicecall.
> 
> 
> I have tested redio-settings and is required to switch to edge to umts. 
> 

Fair enough.

> The device supports voice call but I am unable to test with
> test-voicecall script ast it fails with 
> `Method "GetCalls" with signature "" on interface
> "org.ofono.VoiceCallManager" doesn't exist` error.
> 
> Looking at windows driver log, the device issues AT*ECAV command
> to initiate voice call like this:
> 
> AT*ECAV: 1,1,1,,,"1503",129

Then you will have to trace why the voicecall atom never registers.  Do
note that unless the linktop supports some way of obtaining audio, we
prefer not to enable the voicecall driver and associated interfaces.
Pretty much every single usb datacard on the market can make calls, but
95% of them do not support audio.

Also, I notice that the device reports support of *ENAP, which is used
for high-speed context activation.  Is the kernel detecting a high-speed
interface (e.g. ethernet) when you insert the linktop device?  Or is
this device only capable of PPP?

Regards,
-Denis