similar to: chan_capi install problems

Hello, I have an issue getting the chan_capi module to load in asterisk cvs from today. Plain 2.4.20 kernel with melware patches for the Eicon Diva Server Bri card. I load the modules with: modprobe -v divas divacapi I load the firmware with: divactrl load -c 1 -f ETSI -vd6 Output in /var/log/messages is: Nov 9 19:26:26 voice kernel: Eicon DIVA - DIDD table (http://www.melware.net) Nov 9

I am trying to understand the difference between the divas4linux available from the Eicom/Dialogic website and the melware version. Am I right in thinking that the melware version is for Trixbox or Asterisk but the Dialogic version is for Asterisk only (i.e. will not work with Trixbox?). I've noticed that some of the things mentioned on the Dialogic web site as included with Divas e.g.

Hi (Armin?) ! Today I had a problem with Diva Server 4BRI-8M 2.0. Asterisk 1.2.12.1 chan_capi-cm-0.6.5 divas4linux-melware-3.0.f-106.622-1 Asterisk could not receive and make calls on the BRI ports, although the ports looked fine within Asterisk. I usually use "/usr/lib/divas/divactrl dchannel -c 1" to test line activity. This time there was no activity (cryptic log

Hi, I'm trying to get an Eicon Diva Server4BRI card running under Ubuntu 6.06 - by downloading the v3 driver package from Melware and compiling everything. Yet, after activating the necessary modules (divas and divadidd) and interactively configuring the card (/usr/lib/divas/Config), starting up the adapter fails! The error "/usr/lib/divas/divactrl load -c 1 -Debug" produces

Hi, I am trying to configure a Diva Server 4BRI to work with chan_capi. Here are the steps that I took: - compiled fresh kernel with new-style CAPI support: i4l_divas_1.2 - got the divactrl_1.2 utilities, configured the card startup scripts, - rebooted, card firmware loaded properly, "capiinfo" displays detailed info on 4 controllers, however there is an error message: FAC REQ -

Hi list, Does chan_capi work with kernel 2.6? The Eicon Diva server card loads fine judging from /var/log/messages but Asterisk gives an error when trying to load the chan_capi module. I'm using chan_capi-0.3.5, zaptel-1.0.0, libpri-1.0.0 and asterisk-1.0.0 on a Fedora box with kernel 2.6.8-1.584. Zaptel and ilbpri work fine as does *. I have seen a msg that may be related and don't know

Hi Armin! I have problems on debian sarge with standard 2.6.8-2-386 kernel. I've installed the packages: kernel-headers-2.6.8-2 kernel-headers-2.6.8-2-386 kernel-image-2.6.8-2-386 kernel-kbuild-2.6-3 kernel-source-2.6.8 Then I unpacked the kernel sources into /usr/src/kernel-source-2.6.8 and made a symlink from /usr/src/linux --> kernel-source-2.6.8 Then I entered

On 09/03/2016 10:56 AM, Etienne Dechamps wrote: > C will still need keys in order to establish metaconnections with A and B (as > well as a few other things). However there is no need for C to own any > "Subnets" at all. If somebody breaks into C, he could get access to the vpn network, right? Because the keys are there, it will be possible to use them to get access. Even if

Hi! This weekend we had a problem with our Asterisk Box which ran flawlessly for nearly 4 weeks. The Asterisk server sits between the PSTN and a Siemens PBX and bridges 2 BRI lines. No calls, not incoming, not outgoing. The admin rebooted the Dell Box and then everything worked fine again. Now, I'm analyzing log files to find the cause. During the Asterisk outage the logfiles only show

Hi everybody. I'm trying to setting up a V4 BRI EICON card on ASTERISK 1.0.7 My linux is a debian. It was working during a few days an suddenly (after a lot of reboot) I've got this error message that seems to be very popular but I couldn't find any answer on the net : ==============================================. Asterisk Dynamic Loader Starting: == Parsing

On 09/02/2016 08:51 PM, Etienne Dechamps wrote: > What version of tinc are you using? tinc 1.1 already does what you want out of > the box: packets sent from node A to node B through node C will use a key that > A and B will negotiate between themselves. C doesn't have the key, and will > act as a blind relay. C will not be able to decipher the packets flowing > between A and B.

Hi Armin! I want to backup my Eicon Diva configuration (I'm using melware v3 drivers), but I could not find them. Where does Config Wizard stores the configuration? thanks klaus

Hi Everybody, Has anybody tried the above (or indeed any other 4XBRI cards) successfully with Asterisk. As far as I can see the above mentioned card is an active ISDN card but supported by it's own I4L driver. This leads to interesting questions particularly regarding echo cancellations (which usually doesn't work on the cheap passive cards with one exception as far as I can see).

Hello everyone, I'm having some errors while compiling the source code for an Eicon Diva BRI card. I am using Fedora Core 6 with a compiled from source Linux kernel 2.6.19. I have downloaded the Eicon Diva source RPM (divas4linux_EICON-106.12-1.i386.rpm) and installed it already. When I go to /usr/lib/eicon/divas/src/ and run ./Build, everything starts correctly until that part where it has

Hi all, on sourceforge.net I added the fixup release 0.5.4 of chan_capi-cm driver. The changes from 0.5.3 to 0.5.4 are: - fixed 'group' setting according to Asterisk defaults. - use SetCallerPres(prohib_not_screened) instead of CallingPres(32) for CLIR. - full CallingPres support added. - use mutex when debug/verbose messages are printed. - set dnid on incoming call. - catch errors in

Hi; I've got an AAH installation where a customer wants to install an active Eicon DIVA BRI card. AAH is built on Centos 3.5 which is currently at kernel 2.4.21.37. Support for Eicon active cards is built-in. I've debugged and run the A@H install-Eicondiva script but when I try to run divactrl load -c 1 -f ETSI -Debug I get a response : A: can't get card type for DIVA adapter

Hi all, it took a while, but on sourceforge.net I added the new release 0.6 of chan_capi-cm driver. Note: dial string and capi.conf has changed. The main changes are: - added 'relaxdtmf'. - more BSD compatibility - correct PROGRESS handling - added verbose text for capi info/reason error messages. - use correct facility-selector for echo-cancel - added application capicommand() for CAPI

I want to capture all my Asterisk traffic (including RTP) and then analyse it. My plan was to use tcpdump and then analyse with Wireshark. The following works: tcpdump -i eth0 -s 0 -w /tmp/tcpdump.1 But I want to be a bit more selective: tcpdump -C 100 -W 10 -w /tmp/tcpdump -i eth1 -s 0 udp and dst port >= 5060 This doesn't capture the RTP traffic. Could anyone advise what I'm

Heya Mark (and others), Here's an update on my adventures while trying to debug the Zaptel-related panics, as discussed on this list a while back. While debugging the problem, I completely swapped the machine for an entirely different model (Supermicro dual Xeon 2.4GHz with 2Gb of RAM), put the cards in, recompiled * + Zaptel and administered my stress-test. The machine stayed up in excess

Are there any step by step instrunctions on how to install drivers and I guess bristuff for this card? Just need to use it to handle voice on 2 BRI circuits (UK) then utilise with Asterisk and some Digium cards handling POTS phones (and some VoIP out the back). It's the EICON card stuff and how to make it all work I'm finding confusing? Steve -- NetTek Ltd UK mob +44-(0)7775 755503