From owner-freebsd-isdn  Tue Oct  2  6:52:17 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41])
	by hub.freebsd.org (Postfix) with ESMTP id F1A6237B406
	for <freebsd-isdn@freebsd.org>; Tue,  2 Oct 2001 06:52:09 -0700 (PDT)
Received: from claycross.demon.co.uk ([194.222.107.197] helo=netops)
	by finch-post-12.mail.demon.net with smtp (Exim 2.12 #1)
	id 15oPxv-000DDq-0C
	for freebsd-isdn@freebsd.org; Tue, 2 Oct 2001 13:52:08 +0000
From: "Simon Griffiths" <simon.g@claycrossbs.co.uk>
To: <freebsd-isdn@freebsd.org>
Subject: Identifying where the problem lies.
Date: Tue, 2 Oct 2001 14:52:08 +0100
Message-ID: <NEBBJFKEHEOLHKCGOHFOMECJDFAA.simon.g@claycrossbs.co.uk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

Hi There,

We've been using isdn, i4b and freebsd for around ~6months now with a fair
few problem, i.e. its just not stable and now this morning the things died
yet again.  This time things are different I want to clearly identify where
the problem lays so if it is our telco or isp we can go and hit them hard.
A brief description, we are using i4b with userland ppp coupled with natd
and ipfw.  I hope someone out there can help us iron out whats going on.

Whats happening is that the AVM!FRITZ PCI card goes off to dial our isp,
Demon Internet and fails with

Oct  2 12:02:14 nas ppp[283]: Phase: PPP Started (auto mode).
Oct  2 12:02:17 nas natd[113]: Aliasing to 172.16.0.1, mtu 1500 bytes
Oct  2 12:02:17 nas ppp[283]: Phase: bundle: Establish
Oct  2 12:02:17 nas ppp[283]: Phase: deflink: closed -> opening
Oct  2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: dial req from rbch,
unit 0
Oct  2 12:02:17 nas isdnd[260]: DBG find_by_device_for_dialoutnumber: entry
0, cdid in use
Oct  2 12:02:17 nas ppp[283]: Phase: deflink: Connected!
Oct  2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: config entry reserved
or no match
Oct  2 12:02:17 nas ppp[283]: Phase: deflink: opening -> dial
Oct  2 12:02:17 nas ppp[283]: Phase: deflink: dial -> carrier
Oct  2 12:02:23 nas ppp[283]: Phase: deflink: /dev/i4brbch0: No carrier
(increase ``set cd'' from 6 ?)
Oct  2 12:02:23 nas ppp[283]: Phase: deflink: Disconnected!
Oct  2 12:02:23 nas ppp[283]: Phase: deflink: carrier -> hangup
Oct  2 12:02:23 nas ppp[283]: Phase: deflink: Connect time: 6 secs: 0 octets
in, 0 octets out
Oct  2 12:02:23 nas ppp[283]: Phase: deflink: : 0 packets in, 0 packets out
Oct  2 12:02:23 nas ppp[283]: Phase:  total 0 bytes/sec, peak 0 bytes/sec on
Tue Oct  2 12:02:23 2001
Oct  2 12:02:23 nas ppp[283]: Phase: deflink: hangup -> opening
Oct  2 12:02:23 nas ppp[283]: Phase: deflink: Enter pause (3) for redialing.
Oct  2 12:02:25 nas ppp[283]: Phase: Signal 15, terminate.
Oct  2 12:02:25 nas ppp[283]: Phase: deflink: Disconnected!
Oct  2 12:02:25 nas ppp[283]: Phase: deflink: opening -> closed
Oct  2 12:02:25 nas ppp[283]: Phase: bundle: Dead
Oct  2 12:02:25 nas ppp[283]: Phase: PPP Terminated (normal).

It's this line which is catching me out and making me think this is a
configuration error.
Oct  2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: config entry reserved
or no match

Attached below is our configuration.

Oct  2 12:43:03 nas /kernel: ifpi0: <AVM Fritz!Card PCI> port 0xff80-0xff9f
mem 0xffbeec00-0xffbeec1f irq 9 at device 15.0 on pci0
Oct  2 12:43:03 nas /kernel: ifpi0: ISAC 2085 Version A1/A2 or 2086/2186
Version 1.1 (IOM-2)
Oct  2 12:43:03 nas /kernel: ifpi0: passive stack unit 0

Oct  2 12:43:03 nas /kernel: i4b: ISDN call control device attached
Oct  2 12:43:03 nas /kernel: i4btel: 2 ISDN telephony interface device(s)
attached
Oct  2 12:43:03 nas /kernel: i4brbch: 4 raw B channel access device(s)
attached
Oct  2 12:43:03 nas /kernel: i4bipr: 4 IP over raw HDLC ISDN device(s)
attached (VJ header compression)
Oct  2 12:43:03 nas /kernel: i4bctl: ISDN system control port attached
Oct  2 12:43:03 nas /kernel: IP packet filtering initialized, divert
enabled, rule-based forwarding enabled, default to deny, unlimited logging

-- isdnd.rc

system

# accounting
# ----------

acctall         = on                    # generate info for everything
acctfile        = /var/log/isdnd.acct   # name & location of accounting file
useacctfile     = yes                   # generate accouting info to file
isdntime = on
monitor-allowed = no                    # global switch: monitor on/off

#=================================================================
# User-ppp example
#=================================================================
entry
name                    = userppp0
usrdevicename           = rbch
usrdeviceunit           = 0
isdncontroller          = 0
isdnchannel             = -1
local-phone-incoming    = *
remote-phone-incoming   = *
local-phone-dialout     = *
remote-phone-dialout    = *     # ppp(8) will override this
remdial-handling        = first
dialin-reaction         = ignore
dialout-type            = normal
b1protocol              = hdlc
idletime-incoming       = 400           # Should be larger than ppps timeout
idletime-outgoing       = 400           # Should be larger than ppps timeout
ratetype                = 0
unitlength              = 90
unitlengthsrc           = rate
dialretries             = 1
dialrandincr            = on
recoverytime            = 1             # Should be smaller than ppps redial
usedown                 = off
downtries               = 2
downtime                = 30
direction               = out

-- ppp.conf

isdn:
 set phone 0845212xxxx  # Purple
 # set phone 0845350xxxx        # Black
 # set phone 0845212xxxx        # Green

 set authname xxxxxxxxx # Replace these with your login name & password.
 set authkey xxxxxx     # This profile assumes you're using PAP or CHAP.

 set reconnect 3 5
 set redial 3 10
 set timeout 60 500     # The minimum charge period is 5 minutes, so don't
                        # hangup before then
 # We have no chat scripts in the ISDN world (yet)
 set dial
 set login
 set logout
 set hangup
 set device /dev/i4brbch0               # Raw B-channel devices
 set speed sync                                 # ISDN is synchronous
 # Take a wild guess at an IP number and let the other side decide
 set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0
 add! default hisaddr
 set mrru 1500                          # Multilink mode please
 set mru 1504                           # Room for the MP header
 set server /tmp/ppp-isdn "" 0177       # The diagnostic port (-rw-------)

As you can see these are basically hacks from the examples which were
working once upon a time.  We also quite often have problems after a couple
of days of use and just reboot the machine to bring everything back into
order but this time he still doesnt want to dial up.

Thanks in advance.

--
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


From owner-freebsd-isdn  Tue Oct  2 10:38:41 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from astra.bignet.ru (mail.bignet.ru [80.82.160.5])
	by hub.freebsd.org (Postfix) with SMTP id E359B37B403
	for <freebsd-isdn@FreeBSD.ORG>; Tue,  2 Oct 2001 10:38:35 -0700 (PDT)
Received: (qmail 1814 invoked from network); 2 Oct 2001 17:38:33 -0000
Received: from ppp24.dialup1.bignet.ru (HELO 80.82.160.88) (80.82.160.88)
  by astra.bignet.ru with SMTP; 2 Oct 2001 17:38:33 -0000
Date: Tue, 2 Oct 2001 21:38:31 +0400
From: mails2@bignet.ru
X-Mailer: The Bat! (v1.52f)
Reply-To: mails2@bignet.ru
X-Priority: 3 (Normal)
Message-ID: <1811717820.20011002213831@bignet.ru>
To: freebsd-isdn@FreeBSD.ORG
Subject: Zyxel Omni.net TA
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

stay turned freebsd-isdn

  Hello!

  I need very urgent help, pls.

  I need to setup ISDN access to internet for one company, but i have
  no yet contacted with this technology.

  What do i need to do it? The modem is external, understand "AT"
  commands, but dialing (atdp/atdt) is failed with "NO CARRIER".
  I need to configure it as an internet interface, all the same i can do
  myself.

  Under Win2000 all ok.

  Thanks.

-- 
Yours faithfully,
mails2@bignet.ru


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Tue Oct  2 16:28:21 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166])
	by hub.freebsd.org (Postfix) with ESMTP id BA62837B405
	for <freebsd-isdn@freebsd.org>; Tue,  2 Oct 2001 16:28:15 -0700 (PDT)
Received: by arg1.demon.co.uk (Postfix, from userid 1002)
	id 2F39F9B20; Wed,  3 Oct 2001 00:28:13 +0100 (BST)
Received: from localhost (localhost [127.0.0.1])
	by arg1.demon.co.uk (Postfix) with ESMTP
	id 26B8F5D24; Wed,  3 Oct 2001 00:28:13 +0100 (BST)
Date: Wed, 3 Oct 2001 00:28:13 +0100 (BST)
From: Andrew Gordon <arg-bsd@arg1.demon.co.uk>
X-X-Sender:  <freebsd@server.arg.sj.co.uk>
To: Simon Griffiths <simon.g@claycrossbs.co.uk>
Cc: <freebsd-isdn@freebsd.org>
Subject: Re: Identifying where the problem lies.
In-Reply-To: <NEBBJFKEHEOLHKCGOHFOMECJDFAA.simon.g@claycrossbs.co.uk>
Message-ID: <20011002234412.F78997-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

On Tue, 2 Oct 2001, Simon Griffiths wrote:

> Hi There,
>
> We've been using isdn, i4b and freebsd for around ~6months now with a fair
> few problem, i.e. its just not stable and now this morning the things died
> yet again.

You don't say which version you have been running.  The version in -stable
(and all releases for the last year or so) until shortly before
4.4-release was not in fact very stable; the version from -current
installed over a 4.x system has been much more reliable. However, 4.4 is
now OK.

> A brief description, we are using i4b with userland ppp coupled with natd

Any good reason for using separate natd rather than the nat built-in to
PPP? (not that this is at all relevant to your problem)

> Whats happening is that the AVM!FRITZ PCI card goes off to dial our isp,
> Demon Internet and fails with

I have been using the same configuration (and ISP) without significant
problem, though on my home system I can't use the AVM PCI due to a bug
where it corrupts the other B channel and so interferes with voice calls
on the same S-bus.


> Oct  2 12:02:14 nas ppp[283]: Phase: PPP Started (auto mode).
> Oct  2 12:02:17 nas natd[113]: Aliasing to 172.16.0.1, mtu 1500 bytes
> Oct  2 12:02:17 nas ppp[283]: Phase: bundle: Establish
> Oct  2 12:02:17 nas ppp[283]: Phase: deflink: closed -> opening
> Oct  2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: dial req from rbch,
> unit 0
> Oct  2 12:02:17 nas isdnd[260]: DBG find_by_device_for_dialoutnumber: entry
> 0, cdid in use
> Oct  2 12:02:17 nas ppp[283]: Phase: deflink: Connected!
> Oct  2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: config entry reserved
> or no match
>
> It's this line which is catching me out and making me think this is a
> configuration error.
> Oct  2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: config entry reserved
> or no match

That line is explained by the immediately preceding one - isdnd thinks
that the entry for rbch0 is already in use.  I assume you don't have two
copies of PPP running?


It's not immediately clear if you just don't have a useful set of logging
turned on, or there really is virtually nothing happening at all at the
isdn level.  Do you see any activity on the isdnd display?

> system
>
> # accounting
> # ----------
>
> acctall         = on                    # generate info for everything
> acctfile        = /var/log/isdnd.acct   # name & location of accounting file
> useacctfile     = yes                   # generate accouting info to file
> isdntime = on
> monitor-allowed = no                    # global switch: monitor on/off
>
> #=================================================================
> # User-ppp example
> #=================================================================
> entry
> name                    = userppp0
> usrdevicename           = rbch
> usrdeviceunit           = 0
> isdncontroller          = 0
> isdnchannel             = -1
> local-phone-incoming    = *
> remote-phone-incoming   = *
> local-phone-dialout     = *

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).

> -- ppp.conf
>
> isdn:
>  set phone 0845212xxxx  # Purple
>  # set phone 0845350xxxx        # Black
>  # set phone 0845212xxxx        # Green

I'm currently using the 08440416672 surftime number; previously I was
using 08452120667 (green).

>  # Take a wild guess at an IP number and let the other side decide
>  set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0

For Demon, the far end will always be 158.152.1.222, and the near end will
always be whatever yourname.demon.co.uk resolves to.  Your configuration
should work, but it's tidier (and I believe fractionally faster to sign
on) if you use the right values.  However, again irrelevant to your
current problems.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Wed Oct  3  1:37:26 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20])
	by hub.freebsd.org (Postfix) with ESMTP id A885A37B405
	for <freebsd-isdn@freebsd.org>; Wed,  3 Oct 2001 01:37:20 -0700 (PDT)
Received: from claycross.demon.co.uk ([194.222.107.197] helo=netops)
	by tele-post-20.mail.demon.net with smtp (Exim 2.12 #2)
	id 15ohWj-000N8m-0K; Wed, 3 Oct 2001 08:37:14 +0000
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.
Date: Wed, 3 Oct 2001 09:37:15 +0100
Message-ID: <NEBBJFKEHEOLHKCGOHFOOEEODFAA.simon.g@claycrossbs.co.uk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <20011002234412.F78997-100000@server.arg.sj.co.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

Thanks for your prompt reply, see comments inline.

> -----Original Message-----
> From: owner-freebsd-isdn@FreeBSD.ORG
> Sent: 03 October 2001 00:28
> Subject: Re: Identifying where the problem lies.
>
> You don't say which version you have been running.  The version in -stable
> (and all releases for the last year or so) until shortly before
> 4.4-release was not in fact very stable; the version from -current
> installed over a 4.x system has been much more reliable. However, 4.4 is
> now OK.
>

Sorry, 4.4-RC cvsup'd from not so long back.  the version of isdnd is
01.00.1.  I hope this isnt an isdnd issue as atm I cant cvsup ;-)

> > A brief description, we are using i4b with userland ppp coupled
> with natd
>
> Any good reason for using separate natd rather than the nat built-in to
> PPP? (not that this is at all relevant to your problem)

We are, personally i dont like the inbuilt nat functions of ppp and have
long since moved to using natd and ipfw.
>
> > Whats happening is that the AVM!FRITZ PCI card goes off to dial our isp,
> > Demon Internet and fails with
>
> I have been using the same configuration (and ISP) without significant
> problem, though on my home system I can't use the AVM PCI due to a bug
> where it corrupts the other B channel and so interferes with voice calls
> on the same S-bus.
>

We dont really use the second channel here, the sales bods at seem gave us a
distinct impression that dual channel SDU would work, suffice to say it
doesnt and now they've finally withdrawn it.

>
> > Oct  2 12:02:17 nas isdnd[260]: DBG
> find_by_device_for_dialoutnumber: entry
> > 0, cdid in use
> > Oct  2 12:02:17 nas ppp[283]: Phase: deflink: Connected!
> > Oct  2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: config
> entry reserved
> > or no match
>
> That line is explained by the immediately preceding one - isdnd thinks
> that the entry for rbch0 is already in use.  I assume you don't have two
> copies of PPP running?

Hmm, nope, no two copies running.  Its bizarre as it gives out those two on
boot up as well when ppp is started up.
>
>
> It's not immediately clear if you just don't have a useful set of logging
> turned on, or there really is virtually nothing happening at all at the
> isdn level.  Do you see any activity on the isdnd display?

Yep, on the console monitor we get that its trying to dial out and just sits
there for ~30 seconds then hangs up.


> 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).
>

Great, I'll find its proper cid and set that up.

> > -- ppp.conf
> >
> > isdn:
> >  set phone 0845212xxxx  # Purple
> >  # set phone 0845350xxxx        # Black
> >  # set phone 0845212xxxx        # Green
>
> I'm currently using the 08440416672 surftime number; previously I was
> using 08452120667 (green).
>

Were business here so no surftime :(  Also green and black are having
troubles apparently atm.

> >  # Take a wild guess at an IP number and let the other side decide
> >  set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0
>
> For Demon, the far end will always be 158.152.1.222, and the near end will
> always be whatever yourname.demon.co.uk resolves to.  Your configuration
> should work, but it's tidier (and I believe fractionally faster to sign
> on) if you use the right values.  However, again irrelevant to your
> current problems.

Fair comment, We normally use an RFC1918 for our side of the tunnel on
startup for things like ipfw rules before ppp has be started.  Now were on
an isp with static IP's I probably should re-code all the rules.  Having
time as always isnt it ;-)

Thanks again for your reply,

Si.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Wed Oct  3  1:54:11 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20])
	by hub.freebsd.org (Postfix) with ESMTP id 868EA37B403
	for <freebsd-isdn@freebsd.org>; Wed,  3 Oct 2001 01:54:08 -0700 (PDT)
Received: from claycross.demon.co.uk ([194.222.107.197] helo=netops)
	by tele-post-20.mail.demon.net with smtp (Exim 2.12 #2)
	id 15ohn5-0001Lk-0K; Wed, 3 Oct 2001 08:54:07 +0000
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)
Date: Wed, 3 Oct 2001 09:54:08 +0100
Message-ID: <NEBBJFKEHEOLHKCGOHFOKEEPDFAA.simon.g@claycrossbs.co.uk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <20011002234412.F78997-100000@server.arg.sj.co.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

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


From owner-freebsd-isdn  Wed Oct  3  2: 9: 0 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166])
	by hub.freebsd.org (Postfix) with ESMTP id 4E7A437B403
	for <freebsd-isdn@freebsd.org>; Wed,  3 Oct 2001 02:08:57 -0700 (PDT)
Received: by arg1.demon.co.uk (Postfix, from userid 300)
	id 2DC0D9B20; Wed,  3 Oct 2001 10:08:55 +0100 (BST)
Received: from localhost (localhost [127.0.0.1])
	by arg1.demon.co.uk (Postfix) with ESMTP
	id 262A35D24; Wed,  3 Oct 2001 10:08:55 +0100 (BST)
Date: Wed, 3 Oct 2001 10:08:55 +0100 (BST)
From: Andrew Gordon <arg-bsd@arg1.demon.co.uk>
X-X-Sender:  <arg@server.arg.sj.co.uk>
To: Simon Griffiths <simon.g@claycrossbs.co.uk>
Cc: <freebsd-isdn@freebsd.org>
Subject: RE: Identifying where the problem lies.
In-Reply-To: <NEBBJFKEHEOLHKCGOHFOOEEODFAA.simon.g@claycrossbs.co.uk>
Message-ID: <20011003100123.H80870-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org



On Wed, 3 Oct 2001, Simon Griffiths wrote:
>
> > -----Original Message-----
> > From: owner-freebsd-isdn@FreeBSD.ORG
> > Sent: 03 October 2001 00:28
> > Subject: Re: Identifying where the problem lies.
> >
> > I'm currently using the 08440416672 surftime number; previously I was
> > using 08452120667 (green).
> >
>
> Were business here so no surftime :(  Also green and black are having
> troubles apparently atm.

Surftime is definitely available on business lines - see the official BT
pricelist at:

http://www.serviceview.bt.com/list/current/docs/Customer_Options/12461.htm

You may have trouble persuading BT sales to take an order for it, but this
is normal for any service more complex than a POTS line.  Perserverence
brings results.

My (BT) ISDN line is categorized as 'business' even though it's at home
(it was installed so long ago that BT didn't recognize the posibility of
residential ISDN, and I've never fought the battle to get it changed).
This is the line on which I have surftime.  And Demon's service
description specifically states that they don't limit online time.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Wed Oct  3  9:22:25 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1])
	by hub.freebsd.org (Postfix) with ESMTP id BF0AC37B401
	for <freebsd-isdn@freebsd.org>; Wed,  3 Oct 2001 09:22:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hcshh.hcs.de (Postfix) with ESMTP
	id 82B14BA08; Wed,  3 Oct 2001 18:22:18 +0200 (CEST)
Received: from hcswork.hcs.de (hcswork.hcs.de [172.24.124.5])
	by hcshh.hcs.de (Postfix) with ESMTP
	id 549A7BA07; Wed,  3 Oct 2001 18:22:17 +0200 (CEST)
Received: by hcswork.hcs.de (Postfix, from userid 200)
	id 3A3D1566; Wed,  3 Oct 2001 18:22:17 +0200 (METDST)
Subject: Re: Identifying where the problem lies. (We have a winner)
In-Reply-To: <NEBBJFKEHEOLHKCGOHFOKEEPDFAA.simon.g@claycrossbs.co.uk>
 "from Simon Griffiths at Oct 3, 2001 09:54:08 am"
To: Simon Griffiths <simon.g@claycrossbs.co.uk>
Date: Wed, 3 Oct 2001 18:22:17 +0200 (METDST)
Cc: Andrew Gordon <arg-bsd@arg1.demon.co.uk>,
	freebsd-isdn@freebsd.org
Reply-To: hm@hcs.de
Organization: HCS Hanseatischer Computerservice GmbH
X-Mailer: ELM [version 2.4ME+ PL84 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20011003162217.3A3D1566@hcswork.hcs.de>
From: hm@hcs.de (Hellmuth Michaelis)
X-Virus-Scanned-HCS: by AMaViS perl-11
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org


> > 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.

It seems we are really spoiled by the german Telecom over here .... :-)

hellmuth
-- 
Hellmuth Michaelis                                    Tel   +49 40 55 97 47-70
HCS Hanseatischer Computerservice GmbH                Fax   +49 40 55 97 47-77
Oldesloer Strasse 97-99                               Mail  hm [at] hcs.de
D-22457 Hamburg                                       WWW   http://www.hcs.de

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Wed Oct  3  9:53:17 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by hub.freebsd.org (Postfix) with SMTP id DCDCA37B401
	for <freebsd-isdn@freebsd.org>; Wed,  3 Oct 2001 09:53:12 -0700 (PDT)
Received: (qmail 21907 invoked by uid 0); 3 Oct 2001 16:51:22 -0000
Received: from pc19eaa1c.dip.t-dialin.net (HELO nordstern.own) (193.158.170.28)
  by mail.gmx.net (mp004-rz3) with SMTP; 3 Oct 2001 16:51:22 -0000
Received: (from klaus@localhost)
	by nordstern.own (8.11.6/8.11.6) id f93GqWx00630;
	Wed, 3 Oct 2001 18:52:32 +0200 (CEST)
	(envelope-from klaus.herrmann@gmx.net)
X-Authentication-Warning: nordstern.own: klaus set sender to klaus.herrmann@gmx.net using -f
Subject: problems after upgrading freebsd/i4b
From: Klaus Herrmann <klaus.herrmann@gmx.net>
To: freebsd-isdn@freebsd.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-3Bqad1dbXOUOEstk206v"
X-Mailer: Evolution/0.14 (Preview Release)
Date: 03 Oct 2001 15:51:57 -0100
Message-Id: <1002127917.497.5.camel@nordstern.own>
Mime-Version: 1.0
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org


--=-3Bqad1dbXOUOEstk206v
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi!

I just upgrade freebsd from 4.3 to 4.4-stable, but i have trouble with
the new i4b version included: whenever i do an "ifconfig isp0 up", i4b
does nothing for a few minutes, then tells me it just started isdnd (but
isdnd has already been started at boot time). then it starts dialing.
i did switch to ispppcontrol and changed the kernel driver to the new
Fritz!Card PCI module.
acually, it is working. but this time delay sucks....
do i have to change anything else in the setup? how can i help myself?

thanks in advance!
regards,
	Klaus


--=-3Bqad1dbXOUOEstk206v
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQA7u0ItP+5iE7UMdgARAjVaAJ41Xjv4ckIg8rbUROnc/VtBILRuBgCgzXhw
/owgmEcCaxuFtZ8TWoAETPQ=
=4q26
-----END PGP SIGNATURE-----

--=-3Bqad1dbXOUOEstk206v--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Wed Oct  3 12:56:58 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from mailout04.sul.t-online.de (mailout04.sul.t-online.com [194.25.134.18])
	by hub.freebsd.org (Postfix) with ESMTP id 8504037B408
	for <freebsd-isdn@freebsd.org>; Wed,  3 Oct 2001 12:56:49 -0700 (PDT)
Received: from fwd03.sul.t-online.de 
	by mailout04.sul.t-online.de with smtp 
	id 15os3Q-0007yJ-09; Wed, 03 Oct 2001 21:51:40 +0200
Received: from peti.cryp.to (520030447190-0001@[217.0.88.51]) by fmrl03.sul.t-online.com
	with esmtp id 15os3G-05ONTEC; Wed, 3 Oct 2001 21:51:30 +0200
Received: (from simons@localhost)
	by peti.cryp.to id f93JpEn01812;
	Wed, 3 Oct 2001 21:51:14 +0200
Date: Wed, 3 Oct 2001 21:51:14 +0200
Message-Id: <200110031951.f93JpEn01812@peti.cryp.to>
From: Peter Simons <simons@cryp.to>
To: freebsd-isdn@freebsd.org
Subject: Does i4b support the new AVM!Fritz card?
X-Sender: 520030447190-0001@t-dialin.net
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

Hi,

I recently bought an AVM!Fritz card for the PCI bus. The card says
"version 2.0" and I had some serious trouble getting it to work under
Linux with anything but the latest kernel. Now I wonder whether i4b
supports it, so that I would be able to use it in my BSD box rather
than using the beta kernel on my Linux box. Any comments are highly
appreciated.

Please Cc your answer directly to me because I am not subscribed to
this list.

Thanks!

        -peter

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Wed Oct  3 13:58:26 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from ns.raditex.se (mail.raditex.se [192.5.36.21])
	by hub.freebsd.org (Postfix) with ESMTP id A686737B403
	for <freebsd-isdn@FreeBSD.ORG>; Wed,  3 Oct 2001 13:58:22 -0700 (PDT)
Received: from gandalf.raditex.se (gandalf.raditex.se [192.5.36.18])
	by ns.raditex.se (8.9.3/8.9.3) with ESMTP id WAA05722;
	Wed, 3 Oct 2001 22:58:19 +0200 (CEST)
	(envelope-from gh@raditex.se)
Date: Wed, 3 Oct 2001 22:58:19 +0200 (CEST)
From: G Hasse <gh@raditex.se>
X-Sender: gh@gandalf.sickla.raditex.se
To: Peter Simons <simons@cryp.to>
Cc: freebsd-isdn@FreeBSD.ORG, bus@stacken.kth.se
Subject: Re: Does i4b support the new AVM!Fritz card?
In-Reply-To: <200110031951.f93JpEn01812@peti.cryp.to>
Message-ID: <Pine.BSF.4.21.0110032256390.40702-100000@gandalf.sickla.raditex.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

On Wed, 3 Oct 2001, Peter Simons wrote:

> Hi,
> 
> I recently bought an AVM!Fritz card for the PCI bus. The card says
> "version 2.0" and I had some serious trouble getting it to work under
> Linux with anything but the latest kernel. Now I wonder whether i4b
> supports it, so that I would be able to use it in my BSD box rather
> than using the beta kernel on my Linux box. Any comments are highly
> appreciated.

Noop... It is not supported. This is sad because I hade very good
experience with version 1.0 of this card. 

> 
> Please Cc your answer directly to me because I am not subscribed to
> this list.
> 
> Thanks!
> 
>         -peter
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isdn" in the body of the message
> 

----------------------------------------------------------------
Göran Hasse            email: gh@raditex.se     Tel: +46 8 694 92 70
Raditex AB             http://www.raditex.se    Fax: +46 8 442 05 91
Sickla Alle 7, 1tr                              Mob: 070-5530148
131 34  NACKA, SWEDEN



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Wed Oct  3 14:36:23 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from mailout03.sul.t-online.de (mailout03.sul.t-online.com [194.25.134.81])
	by hub.freebsd.org (Postfix) with ESMTP id 9E01B37B403
	for <freebsd-isdn@freebsd.org>; Wed,  3 Oct 2001 14:36:19 -0700 (PDT)
Received: from fwd01.sul.t-online.de 
	by mailout03.sul.t-online.de with smtp 
	id 15otWl-0000US-05; Wed, 03 Oct 2001 23:26:03 +0200
Received: from peedub.muc.de (520017439985-0001@[217.2.57.23]) by fmrl01.sul.t-online.com
	with esmtp id 15otWY-1bpZr6C; Wed, 3 Oct 2001 23:25:50 +0200
Received: by peedub.muc.de (8.11.6/8.11.1) id f93LPbC67478;
	Wed, 3 Oct 2001 23:25:37 +0200 (CEST)
	(envelope-from garyj)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Gary Jennejohn <garyj@jennejohn.org>
Reply-To: garyj@jennejohn.org
To: Peter Simons <simons@cryp.to>, freebsd-isdn@freebsd.org
Subject: Re: Does i4b support the new AVM!Fritz card?
Date: Wed, 3 Oct 2001 23:25:37 +0200
X-Mailer: KMail [version 1.2]
References: <200110031951.f93JpEn01812@peti.cryp.to>
In-Reply-To: <200110031951.f93JpEn01812@peti.cryp.to>
MIME-Version: 1.0
Message-Id: <01100323253700.00560@peedub.muc.de>
Content-Transfer-Encoding: 8bit
X-Sender: 520017439985-0001@t-dialin.net
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

On Wednesday 03 October 2001 21:51, Peter Simons wrote:
> Hi,
>
> I recently bought an AVM!Fritz card for the PCI bus. The card says
> "version 2.0" and I had some serious trouble getting it to work under
> Linux with anything but the latest kernel. Now I wonder whether i4b
> supports it, so that I would be able to use it in my BSD box rather
> than using the beta kernel on my Linux box. Any comments are highly
> appreciated.
>

This card is not supported at this time and there's no guess as to when it 
will be. Stick with Linux.

-- 
Gary Jennejohn garyj@jennejohn.org gj@freebsd.org

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message


From owner-freebsd-isdn  Thu Oct  4  8:58:12 2001
Delivered-To: freebsd-isdn@freebsd.org
Received: from mail.teligent.se (mail.teligent.se [212.209.126.130])
	by hub.freebsd.org (Postfix) with ESMTP id 94CCA37B401
	for <freebsd-isdn@freebsd.org>; Thu,  4 Oct 2001 08:58:07 -0700 (PDT)
Received: from senyapp01 (senyapp01.teligent.se [172.18.11.7])
	by mail.teligent.se (8.11.1/8.11.1) with SMTP id f94FjxC52729
	for <freebsd-isdn@freebsd.org>; Thu, 4 Oct 2001 17:45:59 +0200 (CEST)
	(envelope-from jakob.alvermark@teligent.se)
Message-ID: <00e201c14ced$7a94b250$070b12ac@teligent.se>
From: "Jakob Alvermark" <jakob.alvermark@teligent.se>
To: <freebsd-isdn@freebsd.org>
Subject: ISDN <-> H.323
Date: Thu, 4 Oct 2001 17:58:58 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00DF_01C14CFE.3DFE88A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

This is a multi-part message in MIME format.

------=_NextPart_000_00DF_01C14CFE.3DFE88A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello!

I have looked around and found that there is a few ISDN to H.323 =
gateways around for Linux, but not for FreeBSD.
I have search the mailing list archives and found nothing.
Do you know of any?
Is someone working on a port?
Could it be hard to port?
What differs in the Linux vs. FreeBSD implementation of ISDN drivers?

Thanks,
Jakob Alvermark

------=_NextPart_000_00DF_01C14CFE.3DFE88A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello!</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have looked around and found that =
there is a few=20
ISDN to H.323 gateways around for Linux, but not for =
FreeBSD.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I have search the mailing list archives =
and found=20
nothing.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Do you know of any?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Is someone working on a =
port?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Could it be hard to port?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>What differs in the Linux vs. FreeBSD=20
implementation of ISDN drivers?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Jakob =
Alvermark</FONT></DIV></BODY></HTML>

------=_NextPart_000_00DF_01C14CFE.3DFE88A0--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message