Re: Huawei E156 - Not receiving calls
gilberto dos santos alves <[email protected]>
| Newsgroups | gmane.linux.drivers.gammu |
|---|---|
| Message-ID | <CAP9G-N+tUaBYxYB8B5g6z8f9eBGPDiaDPXBBbGssiQ4aWAGbCw@mail.gmail.com> |
hummm. in this case for PC, IMO is better using loglevel = 255 and see fragment that apply to timestamp where call is going on. e220 is a very good chipset and standards features. For Raspberry we need what shell, build etc because there are many alternatives, options, processors, etc. .ps imei many times is a private information to post on these lists. is better change posts to some fake numbers. 2016-07-26 20:34 GMT-03:00 Paulo Roberto <[email protected]>: > Gilberto, > > I'm not using Windows. The 2 machines where I'm running my application are > Linux machines. > One is a PC and the other is a Raspberry Pi. > > I didn't understand the "log commands with IMEI scrambled". > > The Dmesg output from the PC: > > [46854.112178] usb 1-1.6: new high-speed USB device number 7 using ehci-pci > [46854.215462] usb 1-1.6: New USB device found, idVendor=12d1, > idProduct=1003 > [46854.215470] usb 1-1.6: New USB device strings: Mfr=2, Product=1, > SerialNumber=0 > [46854.215474] usb 1-1.6: Product: HUAWEI Mobile > [46854.215477] usb 1-1.6: Manufacturer: HUAWEI Technology > [46854.216828] usb-storage 1-1.6:1.0: USB Mass Storage device detected > [46854.217610] scsi host10: usb-storage 1-1.6:1.0 > [46854.426170] usb 1-1.6: USB disconnect, device number 7 > [46860.768192] usb 1-1.6: new high-speed USB device number 8 using ehci-pci > [46860.871452] usb 1-1.6: New USB device found, idVendor=12d1, > idProduct=1003 > [46860.871459] usb 1-1.6: New USB device strings: Mfr=2, Product=1, > SerialNumber=0 > [46860.871463] usb 1-1.6: Product: HUAWEI Mobile > [46860.871466] usb 1-1.6: Manufacturer: HUAWEI Technology > [46860.873194] usb-storage 1-1.6:1.0: USB Mass Storage device detected > [46860.873562] usb-storage 1-1.6:1.1: USB Mass Storage device detected > [46860.873850] usb-storage 1-1.6:1.2: USB Mass Storage device detected > [46860.874593] scsi host10: usb-storage 1-1.6:1.2 > [46860.874867] usb-storage 1-1.6:1.3: USB Mass Storage device detected > [46860.875388] scsi host11: usb-storage 1-1.6:1.3 > [46860.972162] usbcore: registered new interface driver usbserial > [46860.972173] usbcore: registered new interface driver usbserial_generic > [46860.972181] usbserial: USB Serial support registered for generic > [46861.037105] usbcore: registered new interface driver option > [46861.037118] usbserial: USB Serial support registered for GSM modem > (1-port) > [46861.037210] option 1-1.6:1.0: GSM modem (1-port) converter detected > [46861.037307] usb 1-1.6: GSM modem (1-port) converter now attached to > ttyUSB0 > [46861.037325] option 1-1.6:1.1: GSM modem (1-port) converter detected > [46861.037399] usb 1-1.6: GSM modem (1-port) converter now attached to > ttyUSB1 > > > lsusb output: > Bus 001 Device 008: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA > Modem / E230/E270/E870 HSDPA/HSUPA Modem > > ls -lh /dev/ttyUSB0 /dev/ttyUSB1 > crw-rw---- 1 root dialout 188, 0 Jul 26 20:24 /dev/ttyUSB0 > crw-rw---- 1 root dialout 188, 1 Jul 26 20:30 /dev/ttyUSB1 > > The user have the right permissions. > > > > On Tue, Jul 26, 2016 at 2:10 PM, gilberto dos santos alves < > [email protected]> wrote: > >> Hi. please could you post details about your windows driver for your >> modem? like this sample for mf190 v: >> >> id hardware: USB\VID_19D2&PID_0117&REV_0000&MI_02 >> >> log commands with >> imei scrambled >> >> ATQ0V1E0 - OK >> AT+GMM - MF190 >> AT+FCLASS=? - +FCLASS: (0-1) >> AT#CLS=? - COMANDO SEM SUPORTE >> AT+GCI? - COMANDO SEM SUPORTE >> AT+GCI=? - COMANDO SEM SUPORTE >> ATI1 - Manufacturer: ZTE CORPORATION >> Model: MF190 >> Revision: BD_MF190V1.0.0B22 >> IMEI: 121212121212121 >> +GCAP: +CGSM,+DS,+ES >> ATI2 - Manufacturer: ZTE CORPORATION >> Model: MF190 >> Revision: BD_MF190V1.0.0B22 >> IMEI: 121212121212121 >> +GCAP: +CGSM,+DS,+ES >> ATI3 - Manufacturer: ZTE CORPORATION >> Model: MF190 >> Revision: BD_MF190V1.0.0B22 >> IMEI: 121212121212121 >> +GCAP: +CGSM,+DS,+ES >> ATI4 - Manufacturer: ZTE CORPORATION >> Model: MF190 >> Revision: BD_MF190V1.0.0B22 >> IMEI: 121212121212121 >> +GCAP: +CGSM,+DS,+ES >> ATI5 - Manufacturer: ZTE CORPORATION >> Model: MF190 >> Revision: BD_MF190V1.0.0B22 >> IMEI: 121212121212121 >> +GCAP: +CGSM,+DS,+ES >> ATI6 - Manufacturer: ZTE CORPORATION >> Model: MF190 >> Revision: BD_MF190V1.0.0B22 >> IMEI: 121212121212121 >> +GCAP: +CGSM,+DS,+ES >> ATI7 - Manufacturer: ZTE CORPORATION >> Model: MF190 >> Revision: BD_MF190V1.0.0B22 >> IMEI: 121212121212121 >> +GCAP: +CGSM,+DS,+ES >> >> >> 2016-07-26 12:31 GMT-03:00 gilberto dos santos alves <[email protected]>: >> >>> yes now i understand. i will search/test this with one zte mf190 and >>> compare with your huawei e156. thanks. >>> >>> 2016-07-25 22:21 GMT-03:00 Paulo Roberto <[email protected]>: >>> >>>> Sorry, >>>> I'm going to try to clarify things: >>>> >>>> I have a modem Huawei E156 connected to my PC. Within the modem there >>>> is a SIM Card from a certain Telecom. >>>> I wish to make a call to the phone number of this SIM Card and using >>>> Gammu I'd like to detect this call, register the caller id (phone number) >>>> and hang up (finish call without answering it). >>>> >>>> This workflow is working fine when I use as a modem a Motorola EX108 >>>> (same SIM CARD) instead of the E156. >>>> I can call the phone number of this SIM Card, the Gammu starts my >>>> callback function and it does what it should do. >>>> >>>> When I use the E156, I'm not even able to complete the call. The >>>> telecom instantly starts a voice message telling me it cannot complete my >>>> call. >>>> >>>> Was I clear, this time? >>>> >>>> Sorry for the confusion and thanks again. >>>> >>>> >>>> On Mon, Jul 25, 2016 at 8:49 PM, gilberto dos santos alves < >>>> [email protected]> wrote: >>>> >>>>> sorry i do not understand well. >>>>> "but when I try to call it, the operator didn't let the call even >>>>> finish saying that the number is not available" >>>>> your cell is ring and you left it with this state until your inbox >>>>> record message is started or you want trigger one event "finish call" and >>>>> after make a call to number that was registered? >>>>> your operator is your telecom company? >>>>> is this correct? please clarify what is workflow intended. >>>>> >>>>> 2016-07-25 20:07 GMT-03:00 Paulo Roberto <[email protected]>: >>>>> >>>>>> Hello. >>>>>> >>>>>> I have a 3G modem model: Huawei E156 that I would like to use to >>>>>> detect received calls. >>>>>> I don't want to answer the call, just identify it and hung up. Using >>>>>> the GSM_SetIncomingCallCallback and a respective callback. >>>>>> I can get information as model, Manufacturer, signal strength and >>>>>> even receive SMS messages, but when I try to call it, the operator didn't >>>>>> let the call even finish saying that the number is not available. >>>>>> >>>>>> When using a mobile phone (Motorola EX108) as the modem everything >>>>>> works fine. >>>>>> >>>>>> How do I know for sure if the problem is the support of the device >>>>>> for receiving calls or is something I'm not doing right, or maybe any extra >>>>>> configuration? >>>>>> I appreciate any help. >>>>>> >>>>>> Thanks in advance. >>>>>> >>>>>> When running a simple C code to get Manufacturer and model with debug >>>>>> enabled I got the following output: >>>>>> >>>>>> [Gammu - 1.37.3] >>>>>> [Connection - "at"] >>>>>> [Connection index - 0] >>>>>> [Model type - ""] >>>>>> [Device - "/dev/ttyUSB0"] >>>>>> Serial device: DTR is up, RTS is up, CAR is up, CTS is up >>>>>> Setting speed to 115200 >>>>>> [Module - "auto"] >>>>>> Escaping SMS mode >>>>>> SENDING frame type 0x00/length 0x02/2 >>>>>> 1B |0D >>>>>> .. >>>>>> Sending simple AT command to wake up some devices >>>>>> SENDING frame type 0x00/length 0x03/3 >>>>>> 41A|54T|0D >>>>>> AT. >>>>>> 1 "AT" >>>>>> 2 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x09/9 >>>>>> 41A|54T|0D |0D |0A |4FO|4BK|0D |0A >>>>>> AT...OK.. >>>>>> Enabling echo >>>>>> SENDING frame type 0x00/length 0x05/5 >>>>>> 41A|54T|45E|311|0D >>>>>> ATE1. >>>>>> 1 "ATE1" >>>>>> 2 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x0B/11 >>>>>> 41A|54T|45E|311|0D |0D |0A |4FO|4BK|0D |0A >>>>>> ATE1...OK.. >>>>>> Trying Motorola mode switch >>>>>> SENDING frame type 0x00/length 0x0A/10 >>>>>> 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D >>>>>> AT+MODE=2. >>>>>> 1 "AT+MODE=2" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x13/19 >>>>>> 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D |0D |0A |45E|52R|52R|4FO >>>>>> AT+MODE=2...ERRO >>>>>> 52R|0D |0A >>>>>> R.. >>>>>> Seems not to be supported >>>>>> Enabling CME errors >>>>>> SENDING frame type 0x00/length 0x0A/10 >>>>>> 41A|54T|2B+|43C|4DM|45E|45E|3D=|311|0D >>>>>> AT+CMEE=1. >>>>>> 1 "AT+CMEE=1" >>>>>> 2 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x10/16 >>>>>> 41A|54T|2B+|43C|4DM|45E|45E|3D=|311|0D |0D |0A |4FO|4BK|0D |0A >>>>>> AT+CMEE=1...OK.. >>>>>> SENDING frame type 0x00/length 0x09/9 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3F?|0D >>>>>> AT+CSCS?. >>>>>> 1 "AT+CSCS?" >>>>>> 2 "+CSCS: "IRA"" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x1F/31 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3F?|0D |0D |0A |2B+|43C|53S|43C|53S >>>>>> AT+CSCS?...+CSCS >>>>>> 3A:|20 |22"|49I|52R|41A|22"|0D |0A |0D |0A |4FO|4BK|0D |0A : >>>>>> "IRA"....OK.. >>>>>> SENDING frame type 0x00/length 0x0A/10 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3D=|3F?|0D >>>>>> AT+CSCS=?. >>>>>> 1 "AT+CSCS=?" >>>>>> 2 "+CSCS: ("IRA","GSM","UCS2")" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x2F/47 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3D=|3F?|0D |0D |0A |2B+|43C|53S|43C >>>>>> AT+CSCS=?...+CSC >>>>>> 53S|3A:|20 |28(|22"|49I|52R|41A|22"|2C,|22"|47G|53S|4DM|22"|2C, S: >>>>>> ("IRA","GSM", >>>>>> 22"|55U|43C|53S|322|22"|29)|0D |0A |0D |0A |4FO|4BK|0D |0A >>>>>> "UCS2")....OK.. >>>>>> Chosen GSM as normal charset >>>>>> Chosen UCS2 as unicode charset >>>>>> SENDING frame type 0x00/length 0x0E/14 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3D=|22"|47G|53S|4DM|22"|0D >>>>>> AT+CSCS="GSM". >>>>>> 1 "AT+CSCS="GSM"" >>>>>> 2 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x14/20 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3D=|22"|47G|53S|4DM|22"|0D |0D |0A >>>>>> AT+CSCS="GSM"... >>>>>> 4FO|4BK|0D |0A >>>>>> OK.. >>>>>> SENDING frame type 0x00/length 0x09/9 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3F?|0D >>>>>> AT+CSCS?. >>>>>> 1 "AT+CSCS?" >>>>>> 2 "+CSCS: "GSM"" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x1F/31 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3F?|0D |0D |0A |2B+|43C|53S|43C|53S >>>>>> AT+CSCS?...+CSCS >>>>>> 3A:|20 |22"|47G|53S|4DM|22"|0D |0A |0D |0A |4FO|4BK|0D |0A : >>>>>> "GSM"....OK.. >>>>>> Getting model >>>>>> SENDING frame type 0x00/length 0x08/8 >>>>>> 41A|54T|2B+|43C|47G|4DM|4DM|0D >>>>>> AT+CGMM. >>>>>> 1 "AT+CGMM" >>>>>> 2 "E156" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x16/22 >>>>>> 41A|54T|2B+|43C|47G|4DM|4DM|0D |0D |0A |45E|311|355|366|0D |0A >>>>>> AT+CGMM...E156.. >>>>>> 0D |0A |4FO|4BK|0D |0A >>>>>> ..OK.. >>>>>> Unknown model, but it should still work >>>>>> [Model name: `E156'] >>>>>> [Model data: `'] >>>>>> [Model data: `unknown'] >>>>>> [Connected model - "E156"] >>>>>> SENDING frame type 0x00/length 0x08/8 >>>>>> 41A|54T|2B+|43C|47G|4DM|49I|0D >>>>>> AT+CGMI. >>>>>> 1 "AT+CGMI" >>>>>> 2 "huawei" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x18/24 >>>>>> 41A|54T|2B+|43C|47G|4DM|49I|0D |0D |0A |68h|75u|61a|77w|65e|69i >>>>>> AT+CGMI...huawei >>>>>> 0D |0A |0D |0A |4FO|4BK|0D |0A >>>>>> ....OK.. >>>>>> Manufacturer info received >>>>>> [Manufacturer: Huawei] >>>>>> Checking for OBEX support >>>>>> SENDING frame type 0x00/length 0x0B/11 >>>>>> 41A|54T|2B+|43C|50P|52R|4FO|54T|3D=|3F?|0D >>>>>> AT+CPROT=?. >>>>>> 1 "AT+CPROT=?" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x14/20 >>>>>> 41A|54T|2B+|43C|50P|52R|4FO|54T|3D=|3F?|0D |0D |0A |45E|52R|52R >>>>>> AT+CPROT=?...ERR >>>>>> 4FO|52R|0D |0A >>>>>> OR.. >>>>>> Checking for SYNCML/OBEX support >>>>>> SENDING frame type 0x00/length 0x0C/12 >>>>>> 41A|54T|2B+|53S|59Y|4EN|43C|4DM|4CL|3D=|3F?|0D >>>>>> AT+SYNCML=?. >>>>>> 1 "AT+SYNCML=?" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x15/21 >>>>>> 41A|54T|2B+|53S|59Y|4EN|43C|4DM|4CL|3D=|3F?|0D |0D |0A |45E|52R >>>>>> AT+SYNCML=?...ER >>>>>> 52R|4FO|52R|0D |0A >>>>>> ROR.. >>>>>> SENDING frame type 0x00/length 0x0D/13 >>>>>> 41A|54T|24$|54T|53S|53S|50P|43C|53S|57W|3D=|3F?|0D >>>>>> AT$TSSPCSW=?. >>>>>> 1 "AT$TSSPCSW=?" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x16/22 >>>>>> 41A|54T|24$|54T|53S|53S|50P|43C|53S|57W|3D=|3F?|0D |0D |0A |45E >>>>>> AT$TSSPCSW=?...E >>>>>> 52R|52R|4FO|52R|0D |0A >>>>>> RROR.. >>>>>> [Module - >>>>>> "A2D|iPAQ|at|M20|S25|MC35|TC35|C35i|S65|S300|5110|5130|5190|5210|6110|6130|6150|6190|6210|6250|6310|6310i|6510|7110|8210|8250|8290|8310|8390|8850|8855|8890|8910|9110|9210"] >>>>>> Escaping SMS mode >>>>>> SENDING frame type 0x00/length 0x02/2 >>>>>> 1B |0D >>>>>> .. >>>>>> Sending simple AT command to wake up some devices >>>>>> SENDING frame type 0x00/length 0x03/3 >>>>>> 41A|54T|0D >>>>>> AT. >>>>>> 1 "AT" >>>>>> 2 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x09/9 >>>>>> 41A|54T|0D |0D |0A |4FO|4BK|0D |0A >>>>>> AT...OK.. >>>>>> Enabling echo >>>>>> SENDING frame type 0x00/length 0x05/5 >>>>>> 41A|54T|45E|311|0D >>>>>> ATE1. >>>>>> 1 "ATE1" >>>>>> 2 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x0B/11 >>>>>> 41A|54T|45E|311|0D |0D |0A |4FO|4BK|0D |0A >>>>>> ATE1...OK.. >>>>>> Trying Motorola mode switch >>>>>> SENDING frame type 0x00/length 0x0A/10 >>>>>> 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D >>>>>> AT+MODE=2. >>>>>> 1 "AT+MODE=2" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x13/19 >>>>>> 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D |0D |0A |45E|52R|52R|4FO >>>>>> AT+MODE=2...ERRO >>>>>> 52R|0D |0A >>>>>> R.. >>>>>> Seems not to be supported >>>>>> Enabling CME errors >>>>>> SENDING frame type 0x00/length 0x0A/10 >>>>>> 41A|54T|2B+|43C|4DM|45E|45E|3D=|311|0D >>>>>> AT+CMEE=1. >>>>>> 1 "AT+CMEE=1" >>>>>> 2 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x10/16 >>>>>> 41A|54T|2B+|43C|4DM|45E|45E|3D=|311|0D |0D |0A |4FO|4BK|0D |0A >>>>>> AT+CMEE=1...OK.. >>>>>> SENDING frame type 0x00/length 0x09/9 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3F?|0D >>>>>> AT+CSCS?. >>>>>> 1 "AT+CSCS?" >>>>>> 2 "+CSCS: "GSM"" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x1F/31 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3F?|0D |0D |0A |2B+|43C|53S|43C|53S >>>>>> AT+CSCS?...+CSCS >>>>>> 3A:|20 |22"|47G|53S|4DM|22"|0D |0A |0D |0A |4FO|4BK|0D |0A : >>>>>> "GSM"....OK.. >>>>>> SENDING frame type 0x00/length 0x0A/10 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3D=|3F?|0D >>>>>> AT+CSCS=?. >>>>>> 1 "AT+CSCS=?" >>>>>> 2 "+CSCS: ("IRA","GSM","UCS2")" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x2F/47 >>>>>> 41A|54T|2B+|43C|53S|43C|53S|3D=|3F?|0D |0D |0A |2B+|43C|53S|43C >>>>>> AT+CSCS=?...+CSC >>>>>> 53S|3A:|20 |28(|22"|49I|52R|41A|22"|2C,|22"|47G|53S|4DM|22"|2C, S: >>>>>> ("IRA","GSM", >>>>>> 22"|55U|43C|53S|322|22"|29)|0D |0A |0D |0A |4FO|4BK|0D |0A >>>>>> "UCS2")....OK.. >>>>>> Chosen GSM as normal charset >>>>>> Chosen UCS2 as unicode charset >>>>>> SENDING frame type 0x00/length 0x08/8 >>>>>> 41A|54T|2B+|43C|47G|4DM|49I|0D >>>>>> AT+CGMI. >>>>>> 1 "AT+CGMI" >>>>>> 2 "huawei" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x18/24 >>>>>> 41A|54T|2B+|43C|47G|4DM|49I|0D |0D |0A |68h|75u|61a|77w|65e|69i >>>>>> AT+CGMI...huawei >>>>>> 0D |0A |0D |0A |4FO|4BK|0D |0A >>>>>> ....OK.. >>>>>> Manufacturer info received >>>>>> [Manufacturer: Huawei] >>>>>> Checking for OBEX support >>>>>> SENDING frame type 0x00/length 0x0B/11 >>>>>> 41A|54T|2B+|43C|50P|52R|4FO|54T|3D=|3F?|0D >>>>>> AT+CPROT=?. >>>>>> 1 "AT+CPROT=?" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x14/20 >>>>>> 41A|54T|2B+|43C|50P|52R|4FO|54T|3D=|3F?|0D |0D |0A |45E|52R|52R >>>>>> AT+CPROT=?...ERR >>>>>> 4FO|52R|0D |0A >>>>>> OR.. >>>>>> Checking for SYNCML/OBEX support >>>>>> SENDING frame type 0x00/length 0x0C/12 >>>>>> 41A|54T|2B+|53S|59Y|4EN|43C|4DM|4CL|3D=|3F?|0D >>>>>> AT+SYNCML=?. >>>>>> 1 "AT+SYNCML=?" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x15/21 >>>>>> 41A|54T|2B+|53S|59Y|4EN|43C|4DM|4CL|3D=|3F?|0D |0D |0A |45E|52R >>>>>> AT+SYNCML=?...ER >>>>>> 52R|4FO|52R|0D |0A >>>>>> ROR.. >>>>>> SENDING frame type 0x00/length 0x0D/13 >>>>>> 41A|54T|24$|54T|53S|53S|50P|43C|53S|57W|3D=|3F?|0D >>>>>> AT$TSSPCSW=?. >>>>>> 1 "AT$TSSPCSW=?" >>>>>> 2 "ERROR" >>>>>> Checking line: ERROR >>>>>> AT reply state: 3 >>>>>> RECEIVED frame type 0x00/length 0x16/22 >>>>>> 41A|54T|24$|54T|53S|53S|50P|43C|53S|57W|3D=|3F?|0D |0D |0A |45E >>>>>> AT$TSSPCSW=?...E >>>>>> 52R|52R|4FO|52R|0D |0A >>>>>> RROR.. >>>>>> Getting firmware versions >>>>>> SENDING frame type 0x00/length 0x08/8 >>>>>> 41A|54T|2B+|43C|47G|4DM|52R|0D >>>>>> AT+CGMR. >>>>>> 1 "AT+CGMR" >>>>>> 2 "11.604.09.01.149" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x22/34 >>>>>> 41A|54T|2B+|43C|47G|4DM|52R|0D |0D |0A |311|311|2E.|366|300|344 >>>>>> AT+CGMR...11.604 >>>>>> 2E.|300|399|2E.|300|311|2E.|311|344|399|0D |0A |0D |0A |4FO|4BK >>>>>> .09.01.149....OK >>>>>> 0D |0A >>>>>> .. >>>>>> Received firmware version: "11.604.09.01.149" >>>>>> Number version is "11,604090" >>>>>> [Firmware version - "11.604.09.01.149"] >>>>>> [Connected] >>>>>> Entering GSM_GetManufacturer >>>>>> SENDING frame type 0x00/length 0x08/8 >>>>>> 41A|54T|2B+|43C|47G|4DM|49I|0D >>>>>> AT+CGMI. >>>>>> 1 "AT+CGMI" >>>>>> 2 "huawei" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x18/24 >>>>>> 41A|54T|2B+|43C|47G|4DM|49I|0D |0D |0A |68h|75u|61a|77w|65e|69i >>>>>> AT+CGMI...huawei >>>>>> 0D |0A |0D |0A |4FO|4BK|0D |0A >>>>>> ....OK.. >>>>>> Manufacturer info received >>>>>> [Manufacturer: Huawei] >>>>>> Leaving GSM_GetManufacturer >>>>>> Manufacturer : Huawei >>>>>> Entering GSM_GetModel >>>>>> Getting model >>>>>> SENDING frame type 0x00/length 0x08/8 >>>>>> 41A|54T|2B+|43C|47G|4DM|4DM|0D >>>>>> AT+CGMM. >>>>>> 1 "AT+CGMM" >>>>>> 2 "E156" >>>>>> 3 "OK" >>>>>> Checking line: OK >>>>>> AT reply state: 1 >>>>>> RECEIVED frame type 0x00/length 0x16/22 >>>>>> 41A|54T|2B+|43C|47G|4DM|4DM|0D |0D |0A |45E|311|355|366|0D |0A >>>>>> AT+CGMM...E156.. >>>>>> 0D |0A |4FO|4BK|0D |0A >>>>>> ..OK.. >>>>>> Unknown model, but it should still work >>>>>> [Model name: `E156'] >>>>>> [Model data: `'] >>>>>> [Model data: `unknown'] >>>>>> [Connected model - "E156"] >>>>>> Leaving GSM_GetModel >>>>>> Model : unknown (E156) >>>>>> [Terminating] >>>>>> [Closing] >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>>>>> traffic >>>>>> patterns at an interface-level. Reveals which users, apps, and >>>>>> protocols are >>>>>> consuming the most bandwidth. Provides multi-vendor support for >>>>>> NetFlow, >>>>>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>>>>> planning >>>>>> reports.http://sdm.link/zohodev2dev >>>>>> _______________________________________________ >>>>>> Gammu-users mailing list - >>>>>> https://lists.sourceforge.net/lists/listinfo/gammu-users >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> gilberto dos santos alves >>>>> +55(11)9-8646-5049 >>>>> sao paulo - sp - brasil >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>>>> traffic >>>>> patterns at an interface-level. Reveals which users, apps, and >>>>> protocols are >>>>> consuming the most bandwidth. Provides multi-vendor support for >>>>> NetFlow, >>>>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>>>> planning >>>>> reports.http://sdm.link/zohodev2dev >>>>> _______________________________________________ >>>>> Gammu-users mailing list - >>>>> https://lists.sourceforge.net/lists/listinfo/gammu-users >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>>> traffic >>>> patterns at an interface-level. Reveals which users, apps, and >>>> protocols are >>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >>>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>>> planning >>>> reports.http://sdm.link/zohodev2dev >>>> _______________________________________________ >>>> Gammu-users mailing list - >>>> https://lists.sourceforge.net/lists/listinfo/gammu-users >>>> >>>> >>> >>> >>> -- >>> gilberto dos santos alves >>> +55(11)9-8646-5049 >>> sao paulo - sp - brasil >>> >>> >>> >>> >>> >> >> >> -- >> gilberto dos santos alves >> +55(11)9-8646-5049 >> sao paulo - sp - brasil >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning >> reports.http://sdm.link/zohodev2dev >> _______________________________________________ >> Gammu-users mailing list - >> https://lists.sourceforge.net/lists/listinfo/gammu-users >> >> > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Gammu-users mailing list - > https://lists.sourceforge.net/lists/listinfo/gammu-users > > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Gammu-users mailing list - https://lists.sourceforge.net/lists/listinfo/gammu-users