Re: No AVM active ISDN controllers found

Hans Petter Selasky <[email protected]>
Newsgroups gmane.os.freebsd.devel.isdn
Message-ID <[email protected]>
On Friday 09 February 2007 11:27, [email protected] wrote:
> > On Tuesday 06 February 2007 11:54, [email protected] wrote:
> >> > Hi
> >> >
> >> > [email protected] wrote:
> >> >> I am using a Fritz Card under FreeBSD 6.0. I have already precompiled
> >>
> >> my
> >>
> >> >> kernel. During the start of the system I receive:
> >> >
> >> > [...]
> >> >
> >> > Also from the i4bcapimgr I get :
> >> >> Feb  2 14:38:06 fritz kernel: i4bcapimgr: No CAPI controllers
> >>
> >> installed
> >>
> >> > Nothing is wrong, your card is recognised and probably working, but
> >> > FreeBSD doesn't have a CAPI implementation for passive cards out of
> >>
> >> the
> >>
> >> > box. If you need CAPI, eg. to get Asterisk running, I'd suggest you
> >> > start here: http://www.turbocat.net/~hselasky/isdn4bsd/ and get the
> >> > newest version of it by svn (subversion). You'll find some more posts
> >> > about installation and that in a few messages posted around 4.1.07 and
> >> > 6.1.07 by HPS any me in the thread "ISDN4BSD by HPS - Some more
> >> > instructions needed"
> >> >
> >> > I hope you don't have the Version 2 card, otherwise you might have
> >>
> >> some
> >>
> >> > problems with it.
> >> >
> >> > Oliver
> >>
> >> Hi,
> >>
> >> I installed the package by HPS and try to build a new kernel.
> >> I have added to the config
> >>
> >> options IPR_VJ
> >> device "i4bdss1"
> >> device "i4b"
> >> device "i4btrc"
> >> device "i4bctl"
> >> device "i4brbch"
> >> device "i4btel"
> >> device "i4bipr"
> >> device "i4bisppp"
> >>
> >> When I tried to build it , I get :
> >> ../../../dev/sound/pcm/channel.h:69:24: channel_if.h: No such file or
> >> directory
> >>
> >> I tried adding also :
> >> device pcm
> >> to my configuration, but then I got
> >> no such device
> >>
> >> Without the lines for the i4b module, I do not receive the error.
> >>
> >> Do you have any idea, how can I fix this ?
> >
> > Hi,
> >
> > You probably need "device sound" in your kernel config file.
> >
> > --HPS
>
> Hi,
>
>
> this is a part of the message file :
>
> ihfc0: <AVM Fritz!Card PCI> port 0xd000-0xd01f mem 0xee000000-0xee00001f
> irq 17 at device 6.0 on pci0
> ihfc0: Attaching I4B controller 0.
> ihfc0: Creating /dev/ihfc0.X.
> capi: CAPI call control device attached, v2.09
> i4btrc: 64 ISDN trace device(s) attached
> i4brbch: 8 raw B channel access device(s) attached
> i4btel: 8 ISDN telephony interface device(s) attached
> i4bipr: 8 IP over raw HDLC ISDN device(s) attached (VJ header compression)
> i4bisppp: 8 ISDN SyncPPP device(s) attached
> i4bctl: ISDN system control port attached
>
> When I try to register an application ( capi20_register ) , I get:
>
> capi error -  0x1009
> The CAPI driver is not ready.
>
> I also run 'capitest -i 42 -o 42'
>
> main.c: capi_send_listen_request: sending listen request for incoming_calls
> main.c: capi_send_listen_request: sending listen request for incoming_calls
> main.c: capi_send_listen_request: sending listen request for incoming_calls
> dialing out, 1 / 1 ...
>

"capitest" seems to work. Remember that your card, ihfc0, is CAPI controller 
0, and not CAPI controller 1.

> Any ideas what the problem is ?

Do you run the application as the "root" user? Currently capi20_register() 
will only work if you invoke it as root. After this you can drop privileges.

See "man capi20":
     CAPI_ERROR_CAPI_NOT_INSTALLED = 0x1009
                   The CAPI20 device, /dev/capi20, cannot be opened.

Also see "man isdnconfig". Depending on your line you might have to set a 
different D-channel protocol.

--HPS
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.