Created attachment 157038 [details]
tar.bz2 file containing logs described above

The bug is encountered under debian testing/squeeze, as well as ubuntu
10.4 beta1, though I now have only debian installed on the machine. The debian packages are 0.8-1 for network-manger, and 0.3-2 for modemmanager.

The e1550 modem functions normally under Windows 7, and also under my debian
installation when using umtsmon. The modem was flashed with
recent firmware from www.dc-files.com, but the same problem was
present with the firmware that was installed when I bought it (I am
happy to dig out the version numbers, but I doubt that they are
relevant).  As far as I can tell, modemmanager fails to connect to the
network at all; i.e., things go wrong *before* pppd is even started.
All is fine on the kernel side, i.e., the modem is recognized correctly.

I followed the steps desribed at
http://live.gnome.org/NetworkManager/Debugging and will attach the
following files: modemmanager.log , networkmanager.log, output from dmesg
proving my assertion that the kernel side is fine, and a (verbose) log
from a successful connection using umtsmon. Note that pppd never even gets
started; thus, I believe that this problem is distinct from other seemingly
related reports (but I maybe wrong of course). 

In the log files, the pin has already been sent earlier (again,
network-manager/modemmanager manages basic communication with the
e1550) Possibly the only curious thing I can think of about my setup
is the provider (www.bob.at), which is the 'outlet-store' of Austria's
largest provider, A1.  Bob 'piggybacks' on the A1 network, e.g., on
the windows7 side the Huawei communication manager reports 'connected
to A1 (roaming mode)'

Content of huawei1550.tar.bz2
syslog.txt            snippet from dmesg after plugging in the modem
modem-manager3.log    debug log from modemmanager when trying to build up
                      a connection
network-manager3.log  same for network-manager (note that it also contains
                      the connection to my wireless access point which I
                      separated before attempting connecting via 3G
umtsmon.log           log of successful connection with umtsmon