Alright, I hope the attached TXT file clarifies the situation I am facing.
Looks to me like the driver in question does not have the necessary PCI-ID
listed.
On Thu, Jun 1, 2023 at 4:33 PM Tahiro Hashizume <tah...@hashizumes.net>
wrote:
> Hi Michael,
> The telephone service provided by the local telco (NTT East of Japan) is
> based on a very standard format (SIP+RTSP with SIP session timer of 300
> seconds) provided on a closed network over fiber.
> Yet I still consider the interfacing of asterisk with the local telco via
> ISDN to be a valid option for the following reasons:
> A.) The information required for SIP registration incl. account, domain
> and SIP server address(es) are provided via vendor-specific options of
> DHCPv4+DHCPv6-PD.
> Given the format of the service (as mentioned above), direct-interfacing
> of asterisk with telco is no rocket science in principle, but doing so with
> some reliability is another thing.
> While there is sip-proxy software (non-OSS) available for Linux which also
> functions as a DHCP client, I find it rather silly to use it.
> B.)The local telco also requires that any non-hardware/non-certified
> IP-PBXes directly interfaced with their VoIP servers via IPv4/IPv6 to be
> inspected for security and compatibility. In terms of direct-interfacing
> asterisk with the telco, this means having asterisk config files checked by
> telco's engineers (AND THE INSPECTION COSTS A LOT!!!). The aforementioned
> sip-proxy is certified-compatible with the telco and effectively eliminates
> the need for inspection.
>
> Given that B400P available through the local distributor is a
> telco-certified device and the telco also provides a ISDN gateway for the
> service (which has either two or four BRIs and ethernet), ISDN-interfacing
> of asterisk is a seemingly decent choice. Yes, it's a problem so easy to
> solve in principle but not so in reality.
>
> Now, the card is listed in lspci, but is not visible from DAHDI utilities.
> My guess is that it's due to the PCI VID&PID of B400P that is not listed in
> "modinfo wcb4xxp". Documentation by OpenVox also says that a little
> patching is necessary, so things make sense overall.
>
> I'll include the PID and VID with the next email should there be a demand
> for it.
>
> Any comments and ideas are appreciated.
>
> Tahiro
>
> On Mon, May 29, 2023 at 6:38 PM Michael Keuter <li...@mksolutions.info>
> wrote:
>
>>
>>
>> > Am 29.05.2023 um 07:39 schrieb Tahiro Hashizume via Astlinux-users <
>> astlinux-users@lists.sourceforge.net>:
>> >
>> > Dear whom it may concern.
>> >
>> > I've recently got my hands on a OpenVox B400P ISDN BRI card.
>> > It seems that DAHDI included with Astlinux isn't built to support the
>> card and I'm now trying to figure out how to build the image with the
>> support included.
>> > It's been a while since I started fiddling with OSS and I have been
>> fairly comfortable building stuff from sources although I am not yet able
>> to write my own Makefile and so on.
>> > Any ideas on how I should get started?
>> >
>> > P.S.-I have managed to build the toolchain and Astlinux image by
>> default config for Asterisk 18.x.
>> >
>> > Regards.
>>
>> Hi Tahiro,
>>
>> the only BRI driver in DAHDI is the WCB4XXP for 2-8 port HFS-chip cards.
>>
>> https://doc.astlinux-project.org/userdoc:dahdi
>>
>> So in principle this should work for your card:
>>
>> DAHDIMODS="wcb4xxp dahdi_echocan_oslec"
>>
>> I have switched all my ISDN based installations to berofix cards/boxes
>> over 10 years ago.
>> And now none is still in production :-).
>>
>> Michael
>>
>> http://www.mksolutions.info
>>
>>
>>
>>
>>
>> _______________________________________________
>> Astlinux-users mailing list
>> Astlinux-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>
>> Donations to support AstLinux are graciously accepted via PayPal to
>> pay...@krisk.org.
>>
>
A.)"lspci -vvv" shows:
01:0a.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller
[HFC-4S] (rev 01)
Subsystem: Cologne Chip Designs GmbH HFC-4S [Cologne Chip HFC-4S Eval.
Board]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 4
Region 0: I/O ports at dc00 [size=8]
Region 1: Memory at feaff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+
B.)"dahdi_hardware" shows:
pci:0000:01:0a.0 qozap- 1397:08b4 Generic Cologne ISDN card
C.)"modinfo wcb4xxp" shows:
filename: /lib/modules/5.10.162-astlinux/dahdi/wcb4xxp/wcb4xxp.ko
license: GPL
description: B410P & Similars multi-port BRI module driver.
author: Digium Incorporated <supp...@digium.com>
alias: pci:v0000D161d00008017sv*sd*bc*sc*i*
alias: pci:v0000D161d00008016sv*sd*bc*sc*i*
alias: pci:v0000D161d00008015sv*sd*bc*sc*i*
alias: pci:v0000D161d00008014sv*sd*bc*sc*i*
alias: pci:v0000D161d0000B410sv*sd*bc*sc*i*
depends: dahdi
name: wcb4xxp
vermagic: 5.10.162-astlinux SMP preempt mod_unload modversions
parm: persistentlayer1:int
parm: debug:bitmap: 1=general 2=dtmf 4=regops 8=fops 16=ec 32=st
state 64=hdlc 128=alarm (int)
parm: spanfilter:debug filter for spans. bitmap: 1=port 1, 2=port 2,
4=port 3, 8=port 4 (int)
parm: milliwatt:1=replace outgoing S/T data with mu-law milliwatt
(int)
parm: pedanticpci:1=disable PCI back-to-back transfers and flush all
PCI writes immediately (int)
parm: teignorered:1=ignore (do not inform DAHDI) if a red alarm
exists in TE mode (int)
parm: alarmdebounce:msec to wait before set/clear alarm condition
(int)
parm: vpmsupport:1=enable hardware EC, 0=disable hardware EC (int)
parm: timer_1_ms:NT: msec to wait for link activation, TE: unused.
(int)
parm: timer_3_ms:TE: msec to wait for link activation, NT: unused.
(int)
parm: companding:Change the companding to "alaw" or "ulaw"(alaw by
default) (charp)_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
