Problem with I-modem

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Gert Doering wrote:

> Well, I did, indeed - one of my customers (medat.de) is using I-Modems
> for remote dialin atj customer sites, and ISDN login for data download
> purposes.  They do not get *that* many calls, but about 100 calls per
> day is what a few of those I-Modems will get.
> 
> I did not hear any negative reports recently, and since "modem dialup" is
> mostly my responsibility, I assume that this means "this problem didn't
> happen".

I'm getting maximum of 10 calls a day. As long as the I-modem
works (might be a couple of days) it works fine. But when the 
problem arises it always reports busy until I command atz! 
(which is hardware reset).

> Which firmware version is that? To what kind of ISDN line is it
> connected? In-house PABXs tend to be "strange" in kind of ISDN
> protocols, and some of them are pretty unreliable sometimes.

I don't know technical things about ISDN, but it is a standarnd
ISDN terminal device with 2 B-channels, which is widely used in 
Finland. It is a white box which is connected by telephone line 
to the phone company. The ISDN D-channel protocol is also a 
standard one. It might be different from the protocol which is 
used in Germany.

ati7
USRobotics Courier I-Modem with ISDN/V.34 Configuration Profile...

Product type           Sweden External
Options                HST,V32bis,Terbo,V.FC,V34+,x2
Fax Options            Class 1/Class 2.0
Clock Freq             20.16Mhz
Eprom                  768k
Ram                    256k

Supervisor date        10/10/97
DSP date               09/29/97

Supervisor rev         2.2.2
DSP rev                2.2.2

Serial Number          21XID2A8HL32

OK

> [..]
> > 11/13 15:15:44 yS1  wfr: waiting for ``RING''
> > 11/13 15:15:44 yS1  send: ATA[0d]
> > 11/13 15:15:44 yS1  waiting for ``CONNECT''
> > 11/13 15:17:04 yS1  timeout in chat script, waiting for `CONNECT'
> > 11/13 15:17:04 ##### failed timeout dev=ttyS1, pid=4677, caller='none',
> > conn='',
> >  name=''
> 
> I have seen such reports on this list.  It seems to mean "some other
> device on the same ISDN bus took the call, and the I-Modem did not
> realize" (which would mean "ISDN D-Channel protocol bug").

I have three other devices but two of them are analog so 
I don't think they cause trouble. (Anyway, they are connected
to the ISDN terminal box.) But then I have a Teles passive ISDN 
card which is used by BBBS software. But in /var/log/messages 
I can see all incoming calls and which calls are answered by 
this device and which not. When a call comes to the number where 
the I-modem is, the Teles ISDN card always just ignores it, 
according to this log file.

Of course, I could try detaching the Teles card from the bus 
but it would block BBBS's ISDN calls.

But because atz! seems to always solve the problem, I still
think the problem is in Courier.

> gert

Mikael Jokela