Date: Thu, 15 Oct 1998 07:25:44 +0200 (MEST) From: Martin Husemann <martin@rumolt.teuto.de> To: helbig@Informatik.BA-Stuttgart.DE (Wolfgang Helbig) Cc: freebsd-isdn@FreeBSD.ORG, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: no call outgoing Message-ID: <199810150525.HAA02614@rumolt.teuto.de> In-Reply-To: <199810142318.BAA08746@RVC1.Informatik.BA-Stuttgart.DE> from "Wolfgang Helbig" at Oct 15, 98 01:18:48 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > b) was caused by the remote site not being available at that time > > or there wasn't a B channel available at my site locally. > > No B channel available. Local and/or remote. Or somewhere between on the network: we used to see this quite often on several long distance connections via an overrun call-by-call provider. A few Instant redials got the call through, most of the time. > Possibly the buffer queue allocated to the interface by the > IP subsystem is filled with undeliverable IP datagrams. To do > a "ifconfig ipr0 down" followed by an "ifconfig ipr0 up" (substitute > ipr0 by isppp0 if you use PPP) should suffice. If not, you'll need to > debug. Yes, this should solve the problem (worked for us). Btw.: same happened back in the bisdnd days. I think we should somehow arrange isdnd to flush outgoing interface queues when it gives up an outgoing call attempt. Is there a special ioctl for this, or should it SIOCSIFFLAGS to toggle IFF_UP down and back up? Martin 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?199810150525.HAA02614>