we have major problems with the "D211" multimode card.
We can only succeed to establish a dial up connection via (GSM / HSCSD) to any ISP a very few times.
The "D211" is dialing properly but for some reasons a connection cannot be established. The line will be dropped.
We are working with different types of "Sony Vaio" notebooks and we have tried several OS's like "'98 / ME / W2K / XP" but all with the same result.
The newest driver (rel. 433) for the "D211" have been applied but with no success.
As we changed all our notebooks to the "D211" any help is highly appreciated.
First thing is to view modem log via modem properties. It might give you a lead where the problem is.
In windows 98SE/ME:
Go to My Computer -> dial-up Networking -> right click the connection which you are using and select properties. In the properties go to general tab and choose configure. New dialog opens, go to connection tab and choose advanced. Advanced Connection Settings dialog opens, choose view log and log window opens.
In windows 2000/XP:
Go to control panel and choose phone and modem options. Dialog opens, choose modems tab. Right-click modem from the list and choose view log. Modem log window opens.
For trouble shooting, try the following:
a) Check if the modem is used by another application.
b) Use another COM port. COM port can be changed from the modem properties and advanced port settings.
c) Remove and Install Nokia D211 again
AT commands can be found from D211 Developer Manual, which is available at Forum Nokia. Here are the commands you requested:
+DS Data Compression
This command controls the V.42bis and MNP5 data compression functions. V.42bis can be used with transparent and non-transparent data services and MNP5 can be used only with transparent data service. The data service is selected with the command AT+CBST. (V.25ter section 6.6.1.)
[,<P2>]]]] Set compression parameters.
AT+DS? Query current setting.
Response is +DS: <dir>,<neg>, <P1>,<P2>.
AT+DS=? Show supported values.
Response is +DS: (list of supported <dir>'s), (list of supported <neg>'s), (list of supported <P1>'s), (list of supported <P2>'s).
0 no compression (V.42bis P0=0)
1 V.42bis transmit only or MNP5
2 V.42bis receive only or MNP5
3 V.42bis both directions or MNP5
0 do not disconnect if compression is not negotiated by the remote DCE as specified in <direction>
1 disconnect if compression is not negotiated by the re-mote DCE as specified in <direction>
<P1> maximum number of dictionary entries which should be negotiated, 512 to 2048
<P2> maximum string length to be negotiated, 6 to 32, de-fault 20 (V.42bis P2).
+ES Error Control Selection
This command controls the V.42 error control protocol which can be used with transparent data service (see command +CBST). When mobile originated calls are made the transparent data mode must be selected with the command AT+CBST. The requested mode and the acceptable fallback mode of operation for an initiated call are selected with parameters <orig_rqst> and <orig_fbk>. The third parameter, <ans_fbk>, defines the acceptable fallback mode of operation when a call is answered. (V.25ter section 6.5.1.)
,<orig_fbk>,<ans_fbk> Set error control parameters.
The default options are 4, 0, 2.
AT+ES? Query current setting.
Response is +ES: <orig_rqst>, <orig_fbk>, <ans_fbk>.
AT+ES=? Show supported values.
Response is +ES: (list of supported <orig_rqst>'s), (list of supported <orig_fbk>'s), (list of supported <ans_fbk>'s).
0 direct mode 1 initiate call with buffered mode (flow control used)
2 initiate V.42 without detection phase
3 initiate V.42 with detection phase
4 initiate MNP protocol
0 error control optional, use buffered mode if error control not established
2 error control required, disconnect if error control not es-tablished
3 LAPM error control required, disconnect if error control not established
4 MNP error control required, disconnect if error control not established
0 direct mode
1 error control disabled, use buffered mode
2 error control optional, use buffered mode if error control not established
4 error control required, disconnect if error control not es-tablished
5 LAPM error control required, disconnect if error control not established
6 MNP error control required, disconnect if error control not established
Without knowing the details of the script it is hard to say anything. I would advice first to try to establish the connection manually. When that works it is easier to try to figure out how to write the script for D211.
Have you tried web pages / D2 support for finding out correct settings? Unfortunately I don't have a 'data base' for the settings of all operators for all possible connection types.
Unfortunately screen shots cannot be included here so you need to type them to your answer, sorry. However, knowing the settings won't help much if we don't know what settings service provider recommends for establishing connection to service. Since making connection can be only done with a script it means that the handshake is the issue here. It is possible that wrong settings may result hang up while establishing connection with the script but the correct settings should be available from the service provider. These settings can be then set to Nokia D211 UI settings so the connection is established with preferred settings without the need to modify them with extra AT commands. Then running the script should enable succesful handshake if the script is correct. It is then always possible that service is busy and denies access because of that.
Here is the explanation you requested:
+CBST Select Bearer Service Type
Set command selects the bearer service <name> with data rate <speed>, and the connection element <ce> to be used when data calls are originated (GSM02.02). Values may also be used during mobile terminated data call setup, especially in case of single numbering scheme calls (see the command +CSNS). Test command returns values supported by the TA as compound values. (GSM 07.07 section 6.7.)
AT+CBST=<speed>, <name>, <ce> Select bearer service type. The default option is 0, 0, 1.
AT+CBST? Query current setting.
Response is +CBST: <speed>, <name>, <ce>
AT+CBST=? Show supported values.
Response is +CBST: (list of supported <speed>'s), (list of supported <name>'s), (list of supported <ce>'s)
0 autobauding (automatic selection of the speed; this setting is possible in case of 3.1 kHz modem and non-transparent service)
1 300 bps (V.21)
2 1200 bps (V.22)
3 1200/75 bps (V.23)
4 2400 bps (V.22bis)
5 2400 bps (V.26ter)
6 4800 bps (V.32)
7 9600 bps (V.32)
12 9600 bps (V.34)
14 14400 bps (V.34)
15 19200 bps (V.34)
16 28800 bps (V.34)
34 1200 bps (V.120)
36 2400 bps (V.120)
38 4800 bps (V.120)
39 9600 bps (V.120)
43 14400 bps (V.120)
47 19200 bps (V.120)
48 28800 bps (V.120)
49 38400 bps (V.120)
50 48000 bps (V.120)
51 56000 bps (V.120)
65 300 bps (V.110)
66 1200 bps (V.110)
68 2400 bps (V.110 or X.31 flag stuffing)
70 4800 bps (V.110 or X.31 flag stuffing)
71 9600 bps (V.110 or X.31 flag stuffing)
75 14400 bps (V.110 or X.31 flag stuffing)
79 19200 bps (V.110 or X.31 flag stuffing)
80 28800 bps (V.110 or X.31 flag stuffing)
81 38400 bps (V.110 or X.31 flag stuffing)
82 48000 bps (V.110 or X.31 flag stuffing)
83 56000 bps (V.110 or X.31 flag stuffing)
115 56000 bps (bit transparent)
116 64000 bps (bit transparent)
also all other values below 128 are reserved
0 data circuit asynchronous (UDI or 3.1 kHz modem)
1 data circuit synchronous (UDI or 3.1 kHz modem)
2 PAD Access (asynchronous) (UDI)
3 Packet Access (synchronous) (UDI)
4 data circuit asynchronous (RDI)
5 data circuit synchronous (RDI)
6 PAD Access (asynchronous) (RDI)
7 Packet Access (synchronous) (RDI)
also all other values below 128 are reserved
2 both, transparent preferred
3 both, non-transparent preferred
We went through the log file but unfortunately we could not find any specific cause for the error. Since the connection can be opened the Nokia D211 card is functioning OK. We suspect the hang-up is caused by the PPP. Probably the problem will be solved by trying different dial-up settings. Unfortunately that is something we cannot do from here. If the problem remains unsolved we suggest contacting the service provider and trying to sort the dial-up settings with them. They know the requirements of their service. I regret to say we could not solve your problem despite the effort and material you have provided for us.