Diagnose Modem Issues
The information included her is geared towards Windows, but the concepts can be applied to Macintosh computers too.
What type of modem is in your computer is one of the most important pieces of information you must have. It must be said that if a modem cannot connect, it doesn't mean that the modem is bad. It might just mean that our system couldn't establish a solid connection with it. Of course, sometimes a modem is bad, but you should never automatically make that assumption. Although an LT Winmodem or a Conexant HCF is considered a "lower quality" modem, many of our customers have success with it. Also, several customers might have trouble with a "good" modem but not a bad one. There are two major categories of modems, hardware and software. It's very important to figure out in which category the modem in question belongs.
These type modems (HSP) use a lot of your computers memory. Unless you have a lot of excess memory, they will cause problems.
As you can see, the type of modem is amazingly important. Most of the time, you can deduce the problem (even if its wrong) just from the modem type. Here are some basic problems that you might see regarding modem issues:
These types of problems might or might not be modem related. Certain clues will lead you to the assumption that the phone line or something else is not the problem and that the modem is (NOTE: When we say that the modem is the problem, we don't mean that the modem is bad. We just mean that the problem will lie with configuring the modem in some way or another). The first clue will be which type of the two categories the modem falls in. If it falls in the software category, it is highly possible that the modem is either the whole problem or part of the problem. If it falls the hardware category, you will need to rule out phone line or other issues.
If you have a good feeling that the problem with connecting is because of the modem, we need to start thinking about how you are going to fix it. First of all, we need to get actually connected. This usually involves manipulating the modem settings. The first step is to find out what type of modem the computer is actually using. To find this out for sure, go to the "Control Panel", then to "Modems". (Win XP - "Control Panel" then to "Phone and Modem Options")

To change the settings for this modem, click on the "Properties"
button. The first window will have the general properties for this modem.
Usually "Connection Speed" is set to 115200. To ensure proper
functioning, set this to 57600 for a 56K modem. (This should be set lower than
the speed of your modem so if yours is a 33.6 modem you should use 19200 etc.). Be assured, this doesn't affect the connection
speed but only the connection speed from the actual modem to the rest of the
computer.
Be sure to click OK after making changes.

Click on the "Connection" tab. The default settings for Data Bits, Parity, and Stop Bits should be fine. Click on the "Port Settings" button.

The default settings are shown below. It might help the connection if these "FIFO" buffers are lowered. Try to lower them by one setting at the time and see if it helps. If not, set them back to default. Click "OK" to return to the "Connection" tab.

Click on the "Extra Settings" button. This window will allow you to
make significant changes that will either help or hinder connection to PVNS.Net.
The first thing we want to make sure of is that "Use Error Control" is
checked and that underneath that "Compress Data" is also checked.
These two are checked by default. Under "Use flow control", set this
dependent upon what TYPE of modem you are using (HCF and HSP should be
set as software, USR win and LT win should be hardware). The "Modulation
type" should be set to "Standard" and (by default) the
"Extra Settings" box should be blank. This is where you would enter in
an Initialization (init) String if necessary. Please see the next section for
detailed information on Initialization Strings.
For Windows XP find Phone and Modem Options - Click Modems - Advanced

Before your modem software dials a phone number, it initializes (inits) the modem by sending it a series (string) of commands, typically Hayes commands. These commands configure the modem's options for things like error correction, data compression, flow control, and many other parameters. The modem manual should list the Hayes commands the modem recognizes, and what effect each command has.
The important thing about modem init strings is that having the right one often makes the difference between connecting and not. Init strings are fairly specific to each modem. The string that made your friend's modem fly may not work at all for your modem.
For Windows 95/98/2000/ME/XP, the Initialization String goes into the "Extra Settings" box under the "Modem Properties".
The best time to use an initialization string is when a connection cannot be established. This can be because your computer's modem is just unable to communicate well with our modems. It must be said that using an initialization string for a problem such as this is a good way to get your computer online, but is only a "Band Aid" for the problem. The problem will most likely be alleviated by downloading the most current drivers/firmware available for the particular modem you are dealing with. Until we can get it that far, we need to use a specific "protocol" to connect. The protocols that modems use are considered connection "standards". At this time, there are three standards that our server supports. These are V.90, K56 Flex, and V.34 (V.92 modems will work with our servers, but we may not support the changes at all locations).
Init strings are almost always dependent upon which "chipset" is in your modem. The strings that will have the best results are the ones that specifically disable protocols for the modem. If a modem cannot connect, it is because the your modem cannot talk with ours. In this case, we want to revert back to an older protocol (such as K56 Flex or v.34) in hopes that they will be able to understand each other better.
Of the Big Four software modems.... the following is a process for getting them online:
| Modem | Disable x2 | Disable v.42 | Disable V.90 | Disable V.90 & x2 |
| Sportster/USR | S32=34 | S15=128 | S32=66 | S32=98 |
| Courier | S58=1 | S27=32 | S58=32 | S58=33 |
| Cirrus MD56xx | +MS=V90,0 | +ES=4, 4, 6 %C1 | +MS=X2,0 | +MS=V34,1,0,33600 |
| ESS/Teledrive | +MS=17,0 | \N5 | +MS=12,0 | +MS=11,0 |
| Disable KFlex | Disable V90 | Disable V90 & Flex | Disable v.42 | |
| Rockwell Dual * | +MS=12 | +MS=56 | +MS=11 | &Q6 |
| Rockwell HCF & Soft56 | +MS=V90,0 | +MS=K56,0 | +MS=V34 | +ES=1,0,1; |
| Lucent LT | s38=0 | -v90=0 | s38=0-v90=0 | \n2 |
| Lucent Venus | s109=2 | s109=0 | s38=0 | \n2 |
| PCTel HSP | n0s37=14 | n0s37=13 | n0s37=12 | \N5 |
| Motorola SM56 | *MM15 -or- +MS=V90,0 | *MM13 -or- +MS=K56FLEX,0 | *MM12 -or- +MS=V34 |
Click HERE for new info about PCTel HSP modems from Modem Help.Net
Scroll to bottom of page for more modem-specific information. This will hopefully be updated as more special fixes for certain modems are found. You can usually find the chipset of the modem in question on Google by searching on the modem name (which, if not listed blatantly, can often be found in Modems (in the Control Panel) on the Diagnostics tab by clicking on More Info...it's usually listed on ATI3 or ATI5).
Adding Init strings to the modem settings is a trial and error process. Decide, based upon the evidence, which one you want to try. Enter it in and attempt a connection. This will usually result in one of three possibilities:
Keep in mind that Init strings are used for a specific purpose. They are not always the answer to the problem. There are no "Secret Strings" that will all the sudden make the modem connect great. It is a troubleshooting process and we have to treat it as such. Make sure you know exactly what string you are putting in and why. NOTE: If you have a name brand computer, chances are some of the strings may not work and/or the generic drivers (if available) will only cause problems. These customers may need to check with their computer manufacturer to find updates for their specific modem.
NOTE: PVNS can suggest installing modem drivers, but we can NEVER EVER EVER tell someone to download a specific driver. Nor can we assist in installing them, or generally reinstalling the modem. There is too much liability involved in manipulating a customer's drivers in any way beyond modem strings. PVNS strongly suggests that modem issues be directed to a qualified technician and/or the computer or modem manufacturer.
BCM v.90 (Broadcom) modems
Use string s51=63 for disabling v.90 and to disable X2 use S51=95
Disable x2 before trying v.90.
http://808news.com/56k/x2-linklimit.htm#BCM
http://www.808news.com/56k/TROUBLE2.HTM
Other strings:
S51=127 - use all modulations (including V.90)
S51=31 - use only V.34 or slower (limit to 28,800/33,600bps)
S51=15 - use only V.32 or slower (limit to 9600/14,400bps)
S51=3 - use only V.22 or slower (limit to 1200bps)
HaM modems
HaM modems are based on the MD563X chipset from Intel (formerly Ambient Technologies). It is designed as a replacement of the Cirrus Logic MD562X.
The init string that you need depends on your application. The list below includes common init strings and settings used for applications. If these strings don't work, you need to contact the provider of the application to see what type of setup is required.
AT &F E0 V1 W2 &D2 &C1 S0=0 -C1
AT&F E0 Q0 X4 S0=0 &D2 &C1 &S0 V1 W2
AT&F &C1 &D2 "H0 %C0 W2
How to disable V.90 and enable V.34 on the modem - If you have a 56K modem and want to disable V.90 and enable V.34, try the following commands in your init string:
AT+MS=V34,1,0,0
AT+MS=V34,1,300,28800
http://developer.intel.com/design/modems/products/md563x.htm
Other possible strings:
Disable X2: +MS=V90,0
Disable v.42: +ES=4, 4, 6 %C1
Disable v.90: +MS=X2,0
Disable v.90 & X2 (force v.34): +MS=V34,1,0,33600
PCTel Platinum V90 modem
&F1S32=82
HSP chipset
Viking 56k AKY
Lucent chipset -- s38=0
Wisecom Accelerator Pro 56k
AT&F+MS=11,0 and/or AT&F+MS=11,1
both are to disable K56
Various Modem Chipsets
MDP 7800-U is a Lucent Winmodem
MDP 3800-U is an HCF
MDP V-U is an HCF
Ambient HaM use HCF strings
Motorola SM56 try *mm12 or *mm15 (in that order)
PCTel Platinum v.90 use HSP strings
Viking 56k AKY use LT strings
SupraMax HCF try +ms=k56,0
BCM v.90 try s51=63 or s51=95 (in that order)
Sportster try s32=34
Eigercom 56k is an LT Winmodem
Compaq Presario 56k DF is an LT Winmodem
Gateway telepath modems are USR winmodem
GTW v.92 modem (in Gateway)
S50=23S51=31 (force v.34)
SupraMAX 56i Voice PCI
CHIPSET: CONEXANT/ROCKWELL HCF
Z+MS=K56,0