Date: Wed, 23 Feb 2000 21:31:24 +0100 From: Gary Jennejohn <garyj@peedub.muc.de> To: tobi@physcip.uni-stuttgart.de (Tobias Ernst) Cc: freebsd-isdn@FreeBSD.org Subject: Re: early hangup causing exorbitant telecom fees Message-ID: <200002232031.VAA47853@peedub.muc.de> In-Reply-To: Your message of "Wed, 23 Feb 2000 17:26:14 %2B0100." <MSGID_242=3A7600=2F1_38b416d2@Fido.DE>
next in thread | previous in thread | raw e-mail | index | archive | help
Tobias Ernst writes: >Hallo All! > >Could you please tell me, what was happening here (see below)? See below. >And do you see any chance that I could argue the Telekom into not >having to pay this abhorrent sum? (The remote site is an Ascend router >run *by the Telekom* for our University, so if it is an error on the >remote site, this could help a lot) > Maybe you can convince someone at the Uni that the Telekom is at fault. With a little backing from the Uni you might be able to get the Telekom to admit that they made a mistake (hah !). >02.02.2000 02:03:15 CHD 00333 UNIHOME dialing out from 8700334 to >07116870180 >02.02.2000 02:03:15 CHD 00333 UNIHOME outgoing call proceeding (ctl 0, >ch 0) >02.02.2000 02:03:16 CHD 00333 UNIHOME outgoing call active (ctl 0, ch >0, isp0) >02.02.2000 02:03:16 DBG isp0: switched to state 3 >02.02.2000 02:03:17 CHD 00333 UNIHOME outgoing call disconnected >(local) >02.02.2000 02:03:17 CHD 00333 UNIHOME cause 0: normal call clearing >(I4B) >02.02.2000 02:03:17 CHD 00333 UNIHOME charging: 0 units, 1 seconds >02.02.2000 02:03:17 CHD 00333 UNIHOME accounting: in 94, out 84 (in 0, >out 0) Looks like the authentication is failing (that's what phase 3 is). The small number of bytes exchanged seems to corroborate that. Maybe they changed something on their end and didn't tell you. The best way to confirm that is to turn on debugging (ifconfig isp0 debug) and make a connection. Examine the output from the connection attempt, which shoukd be in /var/log/messages. It should be pretty clear whether the authentication failed from the trace. The local disconnect would happen as a result of an authentication failure. There was obviously something happening on your machine which was causing the connects. Mail delivery, perhaps ? --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002232031.VAA47853>