Comment 34 for bug 1057186

@hanynowsky:

I 've been looking at both logs from you, the one from 0.5 and the one from 0.6, and the main difference I find is just in the APN being used to connect. With MM 0.5 you're using:

debug_log(): (ttyUSB0): --> 'ATD*99***1#<CR>'
debug_log(): (ttyUSB0): <-- '<CR><LF>CONNECT 7200000<CR><LF>'
mm_port_set_connected(): (ttyUSB0): port now connected

CID '1' corresponds to the "internet1.meditel.ma" APN.

While in the failing MM 0.6 you're using:
debug_log(): (ttyUSB0): --> 'ATD*99***2#<CR>'
debug_log(): (ttyUSB0): <-- '<CR><LF>ERROR<CR><LF>'

CID '2' corresponds to the "internet2.meditel.ma" APN.

This info comes directly from the NM settings used. In the 0.5 case you used:
              simple_connect(): (ttyUSB0): number => "*99#"
              simple_connect(): (ttyUSB0): username => "MEDINET"
              simple_connect(): (ttyUSB0): password => "MEDINET"
              simple_connect(): (ttyUSB0): apn => "internet1.meditel.ma"
              simple_connect(): (ttyUSB0): network_mode => 6
              simple_connect(): (ttyUSB0): allowed_mode => 2

While in the failing 0.6 case you used:
              simple_connect(): (ttyUSB0): number => "*99#"
              simple_connect(): (ttyUSB0): username => "MEDINET"
              simple_connect(): (ttyUSB0): password => "MEDINET"
              simple_connect(): (ttyUSB0): apn => "internet2.meditel.ma"
              simple_connect(): (ttyUSB0): network_mode => 0
              simple_connect(): (ttyUSB0): allowed_mode => 0

In addition to these differences, I can see that in the MM06 run I get 4 ttyUSB ports (ttyUSB0 to ttyUSB3), while in the MM05 run I only see 2 (ttyUSB0 and ttyUSB1). This is very very weird, as it is the kernel the one making the ports show up, not MM. So if the test is done in exactly the same setup just with 2 different MM versions, this should never happen.

More weird things: GETPORTMODE in MM 06 tells us that the PCUI port is the one with usbif 2; and also it doesn't report any MDM (modem) port. At the end it ends up being useless as of the 4 serial ports found only one of them (ttyUSB0) responds to AT. A wrong ttyUSB port used is probably not the issue here as in both runs ttyUSB0 is being used.

So, no clear idea the reason for the issue.

@hanynowsky or anyone else: can you run MM in debug mode in *exactly* the same setup but just with different MM versions (0.5 and 0.6)?