[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DataCall -> PC (ISDN, Modem)
From: |
Aart Koelewijn |
Subject: |
Re: DataCall -> PC (ISDN, Modem) |
Date: |
Sat, 27 Sep 2003 10:43:18 +0200 (CEST) |
Op 2003-09-26 om 16:44 schreef Ekkard Gerlach:
>
> Well, now I know that I have to reboot linux oftenly when using
> mgetty. Sometimes it hungs somewhere an mgetty doesn't react.
The last time I rebooted the computer on which mgetty runs was about half
a year ago and in that time I must have made at least a hundred calls from
my laptop with my 6110
>
> I reached to connect two PC's X75 by using minicom on the one side
> and mgetty on the other (but not by my handy, thats my aim):
>
>
> And now that's what obscure: Making a data-call from my 6130-Handy
> to the same MSN (nothing changes on the other PC!) the other
> PC irgnores the call:
>
> Sep 26 13:44:27 ama isdnlog: Sep 26 13:44:27 * Call to tei 127 from +49
> 178/7602986,
> Deutschland
> Mobilfunk E1/Deutschland Mo on +49 7xx/8307936, Karlsruhe RING (Data)
> Sep 26 13:44:27 ama kernel: isdn_net: call from 1787602xxx -> 0 8307936
> ignored
> Sep 26 13:44:27 ama kernel: isdn_tty: call from 1787602xxx -> 8307936 ignored
> Sep 26 13:44:30 ama isdnlog: Sep 26 13:44:30 * Call to tei 127 from +49
> 178/7602xxx,
> Deutschland
> Mobilfunk E1/Deutschland Mo on +49 7xx/8307936, Karlsruhe RING (Data)
> Sep 26 13:44:30 ama kernel: isdn_net: call from 1787602xxx -> 0 8307936
> ignored
> Sep 26 13:44:30 ama kernel: isdn_tty: call from 1787602xxx -> 8307936 ignored
> Sep 26 13:45:26 ama isdnlog: Sep 26 13:45:26 Call to tei 127 from +49
> 178/7602xxx,
> Deutschland
> Mobilfunk E1/Deutschland Mo on +49 7xx/8307936, Karlsruhe HANGUP (Timeout)
>
> WHY???
A piece from my logfile from the start of the call:
kernel: isdn_net: Incoming call without OAD, assuming '0'
kernel: isdn_net: call from 0 -> 0 123456789 ignored
kernel: isdn_tty: Incoming call without OAD, assuming '0'
kernel: isdn_tty: call from 0, -> RING on ttyI8
isdnlog: Aug 22 19:20:20 * Call to tei 127 from ? on 123456789 RING
(Data)
isdnlog: Aug 22 19:20:21 Call to tei 96 from ? on 123456789 CONNECT
(Data)
pppd[25068]: pppd 2.4.1 started by a_ppp, uid 0
The difference is in the second line with isdn_tty. In your case it states
"ignored", in my case it is recognized as a call on ttyI8. So this is the
point where things go wrong. It seems mgetty is not connected to your
ttyI1 device. I think you should have a look at your mgetty logfile, in my
case that is /var/log/mgetty.ttyI[linenumber].
An example from my mgetty.ttyI8 logfile:
07/04 21:54:26 yI8 waiting...
07/04 22:54:26 yI8 checking if modem is still alive
07/04 22:54:26 yI8 makelock(ttyI8) called
07/04 22:54:26 yI8 do_makelock: lock='/var/lock/LCK..ttyI8'
07/04 22:54:26 yI8 lock made
07/04 22:54:26 yI8 mdm_send: 'AT'
07/04 22:54:26 yI8 mdm_command: string 'AT'
07/04 22:54:26 yI8 mdm_command: string 'OK' -> OK
07/04 22:54:26 yI8 waiting for line to clear (VTIME), read:
07/04 22:54:27 yI8 removing lock file
07/04 22:54:27 yI8 waiting...
07/04 23:51:28 yI8 checking lockfiles, locking the line
07/04 23:51:28 yI8 makelock(ttyI8) called
07/04 23:51:28 yI8 do_makelock: lock='/var/lock/LCK..ttyI8'
07/04 23:51:28 yI8 lock made
07/04 23:51:28 yI8 wfr: waiting for ``RING''
07/04 23:51:28 yI8 got: [0a][0d][0a]CALLER NUMBER: 0[0d]
07/04 23:51:28 yI8 got: [0a]RING[0d]
07/04 23:51:28 yI8 wfr: rc=0, drn=0
07/04 23:51:28 yI8 send: ATA[0d]
07/04 23:51:28 yI8 waiting for ``CONNECT''
07/04 23:51:28 yI8 got: ATA[0d][0d][0a]CONNECT ** found **
07/04 23:51:28 yI8 send:
07/04 23:51:28 yI8 waiting for ``_''
07/04 23:51:28 yI8 got: 64000/V110/9600[0d][0a] ** found **
07/04 23:51:28 yI8 waiting for line to clear (VTIME), read:
07/04 23:51:29 yI8 utmp + wtmp entry made
07/04 23:51:29 yI8 tio_set_flow_control( HARD )
07/04 23:51:29 yI8 print welcome banner (/etc/issue)
07/04 23:51:29 yI8 getlogname (AUTO_PPP), read:~[ff]}#[c0]!
07/04 23:51:33 yI8 input finished with '\r', setting ICRNL ONLCR
07/04 23:51:33 yI8 tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
07/04 23:51:33 yI8 match: user='/AutoPPP/', key=''
07/04 23:51:33 yI8 match: user='/AutoPPP/', key=''
07/04 23:51:33 yI8 match: user='/AutoPPP/', key=''
07/04 23:51:33 yI8 match: user='/AutoPPP/', key='/AutoPPP/'*** hit!
07/04 23:51:33 yI8 login: utmp entry: a_ppp
07/04 23:51:33 yI8 utmp + wtmp entry made
07/04 23:51:33 yI8 calling login: cmd='/usr/sbin/pppd', argv[]='pppd
auth'
07/04 23:51:33 ##### data dev=ttyI8, pid=17525, caller='0',
conn='64000/V110/9600', name='', cmd='/
usr/sbin/pppd', user='/AutoPPP/'
I wonder how your logfile looks.
> I made the the test to configure mgetty.config like
> described in
> http://mail.nongnu.org/archive/html/gnokii-users/2002-07/msg00165.html
> pointed out in the Doku of gnokii-packet:
If I remember well, that is the message I wrote.
Hope this helps.
Aart
- DataCall -> PC (ISDN, Modem), Ekkard Gerlach, 2003/09/25
- Re: DataCall -> PC (ISDN, Modem), Aart Koelewijn, 2003/09/26
- Re: DataCall -> PC (ISDN, Modem), Ekkard Gerlach, 2003/09/26
- Re: DataCall -> PC (ISDN, Modem),
Aart Koelewijn <=
- Re: DataCall -> PC (ISDN, Modem), Ekkard Gerlach, 2003/09/27
- Re: DataCall -> PC (ISDN, Modem), Aart Koelewijn, 2003/09/27
- Re: DataCall -> PC (ISDN, Modem), Ekkard Gerlach, 2003/09/28
- Re: DataCall -> PC (ISDN, Modem), Aart Koelewijn, 2003/09/29
- Re: DataCall -> PC (ISDN, Modem), BORBELY Zoltan, 2003/09/29