I would agree with Charlie, you might be jumping to conclusions,
but then you might be right

If the logs don't show you anything obvious... try listening to
the train. Does it sound wierd, perhaps constantly retraining?
If you can't hear it, try adding a M2 to the dial string, that will
force the speaker on, even after they connect. If you want, stick
a mic up to the speaker and make a sound file (WAV, au, etc.) of
the training and email it to me (make it a med/low sample rate so
it isn't huge).
The other thing you can try is to use a term program and dial
your ISP manually (atdt.....). Does it train then return a connect
message? If all works well, at least on most ISP NASs, it will
return a login screen a few seconds after connect, and there
should not be any "garbage" on the screen (lots of garbage is
usually a sign of trouble negotiating error correction between
the modems and a sign of trouble). Do note, garbage can also
be caused by PPP negotiation, and not be a problem, but most
NASs won't do that without client initiation, so it is a valid
warning sign.
If you do find it is a handshake problem, the first thing to try
is to disable V.90 (the command varies modem to modem). If
that solves it (but you only get V.34), then yes, a 3Com/USR
modem is an excellent choice. Might I recommend the 3Com/USR
PCI Internal Data/fax, it has been an excellent modem for me.
Also, and this should be obvious in the logs, look for authentication
problems. Your symptoms so far could point to that to.
Hope this helps,
JP