Re: ttyACM0, ttyUSB0, usb0 ???

[José Queiroz <zekkerj gmail com>]

Good news: I finally got NM working with my Onda MSA405HS modem.

When you told about modem-manager, I thought on trying to trace it. I
started it with "--debug" option, and it said:

(...)
** Message: (ttyUSB2) opening serial device...
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state
changed (disabled -> enabling)
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'ATE0 V1<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CPIN?<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+CPIN:
READY<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'ATZ E0 V1 X4 &C1
+CMEE=1;+CFUN=1;<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state
changed (enabling -> enabled)
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CPIN?<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+CPIN:
READY<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+COPS=0,,<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CREG?<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+CREG:
0,1<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: Registration state changed: 1
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state
changed (enabled -> registered)
** (modem-manager:24805): DEBUG: (ttyUSB2): -->
'AT+COPS=3,2;+COPS?<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+COPS:
0,2,"72402",0<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: (ttyUSB2): -->
'AT+COPS=3,0;+COPS?<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+COPS:
0,0,"TIM BRASIL",0<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CSQ<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+CSQ:
15,99<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CGDCONT?<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+CGDCONT:
1,"IP","www.tim.com.br","0.0.0.0",0,0<CR><LF>+CGDCONT:
2,"IP","www.tim.com.br","0.0.0.0",0,0<CR><LF>+CGDCONT:
3,"IP","bandalarga.claro.com.br","0.0.0.0",0,0<CR><LF><CR><LF>OK<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state
changed (registered -> connecting)
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'ATD*99***1***1#<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <--
'<CR><LF>ERROR<CR><LF>'
** (modem-manager:24805): DEBUG: Got failure code 100: Unknown error
** (modem-manager:24805): DEBUG: (ttyUSB2): --> 'AT+CEER<CR>'
** (modem-manager:24805): DEBUG: (ttyUSB2): <-- '<CR><LF>+CEER: No
cause information available<CR><LF><CR><LF>OK<CR><LF>'
** Message: Modem /org/freedesktop/ModemManager/Modems/0: state
changed (connecting -> registered)
(...)

That's when I saw that NM was dialing "*99***1***1#", instead of
"*99***1#", as I configured the connection.

So I had the idea of changing the dial number to "*99#", as I saw in
some documentations (despite the fact that I use "*99***1#" in
wvdial), and it worked.

Wow!

Now, only two questions arise:

1) Why was NM addind "**1" to the dial number? It didn't done that on
the other connection, using the Sony MD300 modem.

2) I had to use my chipmunk brain a little more than usual, to
activate the debug mode of modem-manager, because just stopping it
whilst NetworkManager was active was of no use --- NM restarted it
immediately. So I had to first stop NM, then stop modem-manager.

Maybe there should be a way to do that directly from NM. And if there
is such a way, knetworkmanager should implement it...