I made an interesting observation here. Aircard creates three USB serial ports when its driver gets loaded by the kernel.
/dev/ttyUSB1 does not work with any of the AT commands at all (returns nothing)
/dev/ttyUSB2 seems to work fully and gives the following output:
AT
OK
AT+CGDCONT?
+CGDCONT: 1,"IP","ISP.CINGULAR","",0,0
+CGDCONT: 16,"IP","isp.cingular","",0,0
OK
AT+CGDCONT=?
+CGDCONT: (1-16),"IP",,,(0,1),(0,1)
+CGDCONT: (1-16),"PPP",,,(0,1),(0,1)
it is possible to directly dial without (re)setting the AP
ATD*99#
CONNECT
/dev/ttyUSB0 partially works:
(local echo needs to be activated)
AT
OK
AT+CGDCONT?
ERROR
AT+CGDCONT=?
ERROR
however, its possible to set the AP manually and dial
AT+CGDCONT=1,"IP","ISP.CINGULAR"
OK
ATD*99#
CONNECT
Network Manager seems to use /dev/ttyUSB0 by default which could be a reasons things do not work.
I made an interesting observation here. Aircard creates three USB serial ports when its driver gets loaded by the kernel.
/dev/ttyUSB1 does not work with any of the AT commands at all (returns nothing)
/dev/ttyUSB2 seems to work fully and gives the following output: "ISP.CINGULAR" ,"",0,0 ,"isp.cingular" ,"",0,0
AT
OK
AT+CGDCONT?
+CGDCONT: 1,"IP",
+CGDCONT: 16,"IP"
OK "IP",,, (0,1),( 0,1) "PPP",, ,(0,1), (0,1)
AT+CGDCONT=?
+CGDCONT: (1-16),
+CGDCONT: (1-16),
it is possible to directly dial without (re)setting the AP
ATD*99#
CONNECT
/dev/ttyUSB0 partially works:
(local echo needs to be activated)
AT
OK
AT+CGDCONT?
ERROR
AT+CGDCONT=?
ERROR
however, its possible to set the AP manually and dial 1,"IP", "ISP.CINGULAR"
AT+CGDCONT=
OK
ATD*99#
CONNECT
Network Manager seems to use /dev/ttyUSB0 by default which could be a reasons things do not work.