Date: Wed, 3 Oct 2001 09:54:08 +0100 From: "Simon Griffiths" <simon.g@claycrossbs.co.uk> To: "Andrew Gordon" <arg-bsd@arg1.demon.co.uk> Cc: <freebsd-isdn@freebsd.org> Subject: RE: Identifying where the problem lies. (We have a winner) Message-ID: <NEBBJFKEHEOLHKCGOHFOKEEPDFAA.simon.g@claycrossbs.co.uk> In-Reply-To: <20011002234412.F78997-100000@server.arg.sj.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Andrew it seems this is what was causing the problem, wow. > > I have had trouble on one particulary clueless ISDN provider (Cambridge > Cable, now part of NTL) when the 'local-phone-dialout' was unset or set to > the wrong value (where 'wrong' varied over time!). Try setting this to > the full phone number of your ISDN line (including STD and the leading > zero). Once i'd set the dialout number everything seems to have sprung back to life. Thanks, Si.-- Simon Griffiths Systems Administrator - Clay Cross Building Society Tel:+44(0)1246 862120 - Fax: +44(0)1246 250397 -- "If you give a million monkeys root access to your systems, they sure as hell aren't going to be writing any Shakespeare..." 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?NEBBJFKEHEOLHKCGOHFOKEEPDFAA.simon.g>