Re: Forcing 9600 or less kbps on modem - URGENT HELP!
On Thu, Jun 06, 2002 at 05:50:38PM -0700, curtis wrote:
> What do I need to do in order to set up the modem on a dial-in server so
> that the maximum speed is no greater than 9600?
>
> I would have thought that the parameters in /etc/mgetty/mgetty.config
> would be sufficient (yes, I am using mgetty), but apparently not.
>
> Also, is there a way to set the connection preferenced to 8 data bits,
> no parity and stop bits: 1. But where?
>
> I'd really appreciate any help!!!
>
> Thanks
>
> Curtis
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Following is extracted from info mgetty pages:
- `init-chat' [-m] EXPECT SEND EXPECT SEND ...
Tells mgetty the chat sequence to use for initializing the modem.
*Warning*: the sequence starts with *expect*, which will in most
cases be `""' (nothing). This ordering was chosen because UUCP
does it this way, and I wanted to avoid confusion here.
Example:
init-chat "" ATQ0E1V1H0 OK ATL0M0S0=0 OK AT&K3 OK
^^^^^^^^^^
Above AT strings are Hayes command strings to modem that program its
various parameters. For various modems there are various ways to
program. I own Microcom deskporte modem and speed is setup not by
AT&N command but by setting registers S36 and S37.
You should have manual for Your modem and consult there how to set
for speed required.
Using minicom allows you to actualy experiment with your modem by
sending it commands and see response. Typing ATS0? will respond with
001 or some other number. Substituing for 0 any other S-register
number will show they content.
AT&F and AT&W commands seems to be quite consistent for all modems
i come across so far. First set's modem to factory defaults other
stores your setup.
As far as setting of No of data bits ,parity and stop bits is concerned
this is possible also from minicom and IMHO belonging more to setup of
serial port instead of modem.
- `force-init-chat' EXPECT SEND EXPECT SEND ...
In some cases, the modem can get stuck in a mode where it won't
react to a simple `AT' command. Usually this happens because the
modem is set to ignore a DTR drop and still has a data connection
to the other side. If you use a voice modem, it could be stuck in
voice mode.
In these situations, the normal `init-chat' will time out, because
the modem won't send the proper responses back.
To get the modem back into a sane state, you can use the
`force-init-chat' chat sequence. The default setup will send the
DLE ETX characters, to get voice modems back to life, and then the
`(pause)+++(pause)ATH0' sequence to get the modem back from data
mode to command mode.
You could prepend this sequence to `init-chat' (it wouldn't harm),
but especially the pauses around the +++ sequence makes this
undesirable slow.
- `post-init-chat' EXPECT SEND EXPECT SEND ...
Some modems forget parts of their settings when going from data to
fax mode and back during modem initialization. For example, some
USR models forget the settings of "Caller ID delivery" (AT#CID=1),
and some ELSA modems forget their current DTE port speed when
going from voice to data mode, thus leading to RING messages being
delivered with the wrong baud rate.
For those modems, you can use this command to set up some AT
commands that are executed after all other fax and voice
initialization has been done. Be careful with what you do! If
you send an ATZ (modem reset) or something similar here, all your
fax/voice settings will be lost!
Regard Mick
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: