Re: [Astlinux-users] Hello all and I need help.

[Lonnie A. <li...@lo...>]

Hi Tahiro,

A quick look at the dahdi-linux code for the "wcb4xxp", the PCI-ids appear to be defined here [1]

But my gut feeling, there may be more to it than simply adding a line to DEFINE_PCI_DEVICE_TABLE

Question, are Digium wcb4xxp ISDN cards available on the used market at a reasonable price?

Lonnie

[1] https://github.com/asterisk/dahdi-linux/blob/4397c55319154a8dc89022f6f75c683d6af12d54/drivers/dahdi/wcb4xxp/base.c#LL3642C1-L3651C3



> On Jun 5, 2023, at 2:51 AM, Tahiro Hashizume via Astlinux-users <ast...@li...> wrote:
> 
> 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 <ta...@ha...> 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...@mk...> wrote:
> 
> 
> > Am 29.05.2023 um 07:39 schrieb Tahiro Hashizume via Astlinux-users <ast...@li...>:
> > 
> > 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