Thread View: comp.os.linux.networking
1 messages
1 total messages
Started by Olivier Alessandri
Tue, 27 May 1997 00:00
Probleme avec mgetty+olitec
Author: Olivier Alessandri
Date: Tue, 27 May 1997 00:00
Date: Tue, 27 May 1997 00:00
283 lines
10925 bytes
10925 bytes
Avec un - OLITEC self memory 33600 - et sa passerelle - mgetty1.0.0 -
(sous linux 2.0.29) je n'arrive pas � configurer mgetty pour que le
faxmodem fonctionne en mode fax et modem .
Le r�elle probleme serait de trouver la bonne chaine d'initialisation
qui se trouve dans policy.h ou dans le fichier
"/usr/local/etc/mgetty+senfax/mgetty.config" du style at&f&k6s25=20 ???
Cela fait d�j� un bon moment que je cherche sans trouver le moyen de le
faire fonctionner !!!
Si une ame charitable voulait bien m'aider ???
D'autant plus que j'ai des erreurs du type "/usr/local/sbin/senfax:cannot
set fax station ID" ; meme en changeant le numero de fax la meme erreur
revient ???
****************
J'ai �galement plusieurs erreurs dans le fichier log_mg.ttyS1:
--
05/27 10:11:02 yS1 mgetty: official release 1.0.0
05/27 10:11:02 yS1 check for lockfiles
05/27 10:11:02 yS1 locking the line
05/27 10:11:03 yS1 WARNING: DCD line still active, check modem settings
(AT&Dx)
05/27 10:11:03 yS1 lowering DTR to reset Modem
05/27 10:11:04 yS1 send: ATZ[0d]
05/27 10:11:04 yS1 waiting for ``OK'' ** found **
05/27 10:11:05 yS1 send: AT&F&K6V0S25=20[0d]
05/27 10:11:05 yS1 waiting for ``OK''
05/27 10:11:25 yS1 timeout in chat script, waiting for `OK'
05/27 10:11:25 yS1 init chat timed out, trying force-init-chat
05/27 10:11:25 yS1 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
05/27 10:11:29 yS1 waiting for ``OK'' ** found **
05/27 10:11:29 yS1 send: ATZ[0d]
05/27 10:11:29 yS1 waiting for ``OK'' ** found **
05/27 10:11:31 yS1 send: AT&F&K6V0S25=20[0d]
05/27 10:11:31 yS1 waiting for ``OK''
05/27 10:11:51 yS1 timeout in chat script, waiting for `OK'
05/27 10:11:51 yS1 init chat failed, exiting...: Interrupted system call
05/27 10:11:51 ##### failed in mg_init_data, dev=ttyS1, pid=1401
--
05/27 10:11:51 yS1 mgetty: official release 1.0.0
05/27 10:11:51 yS1 check for lockfiles
05/27 10:11:51 yS1 locking the line
05/27 10:11:51 yS1 WARNING: DCD line still active, check modem settings
(AT&Dx)
05/27 10:11:51 yS1 lowering DTR to reset Modem
05/27 10:11:52 yS1 send: ATZ[0d]
05/27 10:11:52 yS1 waiting for ``OK'' ** found **
05/27 10:11:53 yS1 send: AT&F&K6V0S25=20[0d]
05/27 10:11:53 yS1 waiting for ``OK''
05/27 10:12:13 yS1 timeout in chat script, waiting for `OK'
05/27 10:12:13 yS1 init chat timed out, trying force-init-chat
05/27 10:12:13 yS1 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
05/27 10:12:17 yS1 waiting for ``OK'' ** found **
05/27 10:12:18 yS1 send: ATZ[0d]
05/27 10:12:18 yS1 waiting for ``OK'' ** found **
05/27 10:12:19 yS1 send: AT&F&K6V0S25=20[0d]
05/27 10:12:19 yS1 waiting for ``OK''
05/27 10:12:39 yS1 timeout in chat script, waiting for `OK'
05/27 10:12:39 yS1 init chat failed, exiting...: Interrupted system call
05/27 10:12:39 ##### failed in mg_init_data, dev=ttyS1, pid=1435
--
05/27 10:12:39 yS1 mgetty: official release 1.0.0
05/27 10:12:39 yS1 check for lockfiles
05/27 10:12:39 yS1 locking the line
05/27 10:12:40 yS1 WARNING: DCD line still active, check modem settings
(AT&Dx)
05/27 10:12:40 yS1 lowering DTR to reset Modem
05/27 10:12:41 yS1 send: ATZ[0d]
05/27 10:12:41 yS1 waiting for ``OK'' ** found **
05/27 10:12:42 yS1 send: AT&F&K6V0S25=20[0d]
05/27 10:12:42 yS1 waiting for ``OK''
--
... En re�ssayant plus tard sans rien changer :
05/27 10:58:55 yS1 mgetty: official release 1.0.0
05/27 10:58:56 yS1 check for lockfiles
05/27 10:58:56 yS1 locking the line
05/27 10:58:56 yS1 WARNING: DCD line still active, check modem settings
(AT&Dx)
05/27 10:58:56 yS1 lowering DTR to reset Modem
05/27 10:58:57 yS1 send: AT&F&K6V0S25=20[0d]
05/27 10:58:57 yS1 waiting for ``OK''
05/27 10:59:17 yS1 timeout in chat script, waiting for `OK'
05/27 10:59:17 yS1 init chat timed out, trying force-init-chat
05/27 10:59:17 yS1 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
05/27 10:59:21 yS1 waiting for ``OK'' ** found **
05/27 10:59:22 yS1 send: AT&F&K6V0S25=20[0d]
05/27 10:59:22 yS1 waiting for ``OK'' ** found **
05/27 10:59:32 yS1 send: AT&F&V[0d]
05/27 10:59:32 yS1 do_stat: expect 'OK' ** found **
05/27 10:59:32 yS1 mdm_send: 'AT+FCLASS=2.0' -> OK
05/27 10:59:32 yS1 mdm_send: 'AT+FAA=1;+FCR=1' -> OK
05/27 10:59:32 yS1 mdm_send: 'AT+FBO=1' -> ERROR
05/27 10:59:32 yS1 cannot set bit order, trying +BOR=0
05/27 10:59:32 yS1 mdm_send: 'AT+FBO=0' -> ERROR
05/27 10:59:32 yS1 mdm_send: 'AT+FNR=1,1,1,0' -> ERROR
05/27 10:59:32 yS1 mdm_send: 'AT+FLI="55"' -> ERROR
05/27 10:59:32 yS1 cannot set local fax id. Huh?
05/27 10:59:33 yS1 mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> ERROR
05/27 10:59:33 yS1 mdm_send: 'AT+FCC=1,3,0,2,0,0,0,0' -> ERROR
05/27 10:59:33 yS1 huh? Cannot set +FDCC parameters
05/27 10:59:33 yS1 waiting...
05/27 10:59:56 yS1 lock not made: lock file exists
***************************************************************
Que veulent dire ces erreurs et comment les corriger ???
"init chat failed, exiting...: Interrupted system call"
"failed in mg_init_data, dev=ttyS1, pid=1435"
'AT+FBO=1' -> ERROR
cannot set bit order, trying +BOR=0
'AT+FBO=0' -> ERROR
'AT+FNR=1,1,1,0' -> ERROR
'AT+FLI="55"' -> ERROR
cannot set local fax id. Huh?
(pourquoi il ne prend pas ce numero de fax ???
'AT+FCC=1,5,0,2,0,0,0,0' -> ERROR
'AT+FCC=1,3,0,2,0,0,0,0' -> ERROR
huh? Cannot set +FDCC parameters
****************************************************************
***************
En changeant de chaine d'initialisation dans mgetty.config :
init-chat "" AT&F&K3V0S25=20S95=47 OK
(chaine trouvee dans un fichier texte sous Window95 pour olitec)
Le fichier log_msg.ttyS1 prend cet forme :
05/27 11:01:19 yS1 timeout in chat script, waiting for `OK'
05/27 11:01:19 yS1 init chat timed out, trying force-init-chat
05/27 11:01:19 yS1 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
05/27 11:01:23 yS1 waiting for ``OK'' ** found **
05/27 11:01:23 yS1 send: AT&F&K6V0S25=20[0d]
05/27 11:01:23 yS1 waiting for ``OK''
05/27 11:01:43 yS1 timeout in chat script, waiting for `OK'
05/27 11:01:44 yS1 init chat failed, exiting...: Interrupted system call
05/27 11:01:44 ##### failed in mg_init_data, dev=ttyS1, pid=1801
--
05/27 11:06:45 yS1 mgetty: official release 1.0.0
05/27 11:06:45 yS1 check for lockfiles
05/27 11:06:45 yS1 locking the line
05/27 11:06:45 yS1 WARNING: DCD line still active, check modem settings
(AT&Dx)
05/27 11:06:45 yS1 lowering DTR to reset Modem
05/27 11:06:46 yS1 send: AT&F&K3V0S25=20S95=47[0d]
05/27 11:06:46 yS1 waiting for ``OK'' ** found **
05/27 11:07:03 yS1 send: AT&F&V[0d]
05/27 11:07:03 yS1 do_stat: expect 'OK' ** found **
05/27 11:07:03 yS1 mdm_send: 'AT+FCLASS=2.0' -> OK
05/27 11:07:04 yS1 mdm_send: 'AT+FAA=1;+FCR=1' -> OK
05/27 11:07:04 yS1 mdm_send: 'AT+FBO=1' -> ERROR
05/27 11:07:04 yS1 cannot set bit order, trying +BOR=0
05/27 11:07:04 yS1 mdm_send: 'AT+FBO=0' -> ERROR
05/27 11:07:04 yS1 mdm_send: 'AT+FNR=1,1,1,0' -> ERROR
05/27 11:07:04 yS1 mdm_send: 'AT+FLI="55"' -> ERROR
05/27 11:07:04 yS1 cannot set local fax id. Huh?
05/27 11:07:04 yS1 mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> ERROR
05/27 11:07:04 yS1 mdm_send: 'AT+FCC=1,3,0,2,0,0,0,0' -> ERROR
05/27 11:07:04 yS1 huh? Cannot set +FDCC parameters
05/27 11:07:04 yS1 waiting...
05/27 11:07:37 yS1 lock not made: lock file exists
A premi�re vue il met les meme erreurs qu'avec la chaine pr�c�dente,
donc que dois- je faire pour que cela marche ????
***************
Dans mgetty.config
Est-ce que ceci est correct ????
# mgetty configuration file
#
# this is a sample configuration file, see mgetty.info for details
#
# comment lines start with a "#", empty lines are ignored
# ----- global section -----
#
# In this section, you put the global defaults, per-port stuff is below
# set the global debug level to "5" (which is quite verbose)
# debug 5
# set the local fax station id
# ceci est un numero de fax local
fax-id 55
# access the modem(s) with 38400 bps
speed 115200
# the /dev/tty-device is owned by uucp.uucp and mode "rw-rw-r--" (664)
port-owner uucp
port-group uucp
port-mode 0664
# incoming faxes are owned by "root.uucp" and mode "rw-r-----" (640)
fax-owner root
fax-group uucp
fax-mode 0640
# ----- port specific section -----
#
# Here you can put things that are valid only for one line, not the others
#
# Zoom V.FX 28.8, connected to ttyS0: don't do fax, less logging
#
#port ttyS0
# debug 3
# data-only y
# ZyXEL 2864, connected to ttyS1: maximum debugging, grab statistics
#
port ttyS1
# debug 8
# init-chat "" ATZ OK AT&F OK
init-chat "" AT&F&K6V0S25=20 OK
# statistics-chat "" ATI6 OK
# statistics-file /tmp/statistics.2864
# modem-type c2.0
****************
Dans /etc/inittab
j'ai ceci lancement de mgetty pour l'utiliser en mode automatique fax ou
modem .
Est-ce correct ???
s1:456:respawn:usr/local/sbin/mgetty ttyS1 vt100
****************
Et dans le fichier /tmp/statistiques.2864
je vous c�de la configuration du modem OLITEC Self Memory 33600:
--- Tue May 27 10:59:32 1997 ---
AT&F&V
ACTIVE PROFILE:
B00 E1 L2 M1 Q0 T V1 W2 X4 &A0 &C1 &D2 &G2 &K3 &Q5 &R1 &S0 &X0 %C3 \N3 &Y0
S00:000 S01:000 S02:043 S03:013 S04:010 S05:008 S06:007 S07:140 S08:002
S09:006
S10:014 S11:070 S12:020 S18:000 S25:005 S26:001 S36:007 S37:000 S38:020
S44:020
TELEPHONE NUMBERS:
0= 1=
2= 3=
OK
Je vous remercie d'avance pour vos r�ponses.
Olivier ALESSANDRI.
-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads