Asterisk Eicon Diva CAPI ISDN

VoIP Hardware Solutions
Provider Solution Details
VoIP Hardware Zycoo UC Solutions
  • Modular Design IP PBX for SMB
  • Remote office Centralized Management solution
  • 3rd party app integration, Enterprise Billing, Android & iOS client
Details
Yeastar Communications Solutions
  • Cost-effective IP-PBX Solution for SMB
  • FXS, FXO, GSM, BRI and PRI VoIP Gateways
  • Rich features and reliable performance
Details

Dialogic Diva Server drivers


(Dialogic was formerly known as Eicon Networks).

There are different ways to use the Dialogic Diva cards. YMMV depending on config.

Option 0 Suitable for ALL Kernel Versions

This is the easiest way to get your Dialogic Diva Card installed under Asterisk.

If you have any problems please contact the Dialogic support Helpdesk in either EMEA, America or Asia Pacific

Please note, that whilst Dialogic can offer support on the Dialogic-specifc parts of the installation, if your problem is more general such as unable to compile asterisk, or unable to compile chan_capi, then we recommend you contact the support forum for that particular package


First download the latest driver for your system from the Dialogic website. The best way is to download the latest source driver of the DivaServer4Linux code. This is available through this page

You should not have the ISDN4Linux driver installed as the Diva Server for Linux drivers includes the Melware CAPI driver. You should also not have the HiSax driver installed.

This code is suitable for all kernel versions including 2.6.X and for all Diva Server cards.
Note : The latest driver available (divas4linux_EICON-106.10-1) can't be compiled on a 2.6.17 and more (DevFS was removed). Use 2.6.16.37

Once you have filled in this form you will be able to download the source driver.

Then follow the instructions on this page to build the driver:

http://www.dialogic.com/support/helpweb/slnxen/Install-FromSource.asp

Then, follow the instructions to configure your card. Make sure that as part of the configuration you specify that you want to use the CAPI Interface.

http://www.dialogic.com/support/helpweb/slnxen/default.htm


After installing your card, you then need to install the chan_capi driver from sourceforge. This will require that you have a file called capi20.h available on the system. To do this just make sure that you install the
isdn4k-utils-devel
package on your system.


Then edit your capi.conf. The following example shows a system with two cards installed - a Diva Server PRI 30M, and also a Diva Server V-Analog 8P card.

fedcore2:/root# more /etc/asterisk/capi.conf
;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
alaw=yes

[PRI30M]

;Define CAPI Controller Interface for PRI-30M
;mode=immediate
isdnmode=DID
ntmode=yes;
incomingmsn=*
controller=2
softdtmf=0
accountcode=
context=isdn
callgroup=1
devices=30
echocancel=yes

[V-Analog8P]
;Define CAPI Controller Interface for V-Analogue 8P
;mode=immediate
isdnmode=DID
ntmode=yes;
incomingmsn=*
controller=1
softdtmf=0
accountcode=
context=analog
callgroup=1
devices=2
echocancel=yes


In you extensions.conf file you can then include lines such as

exten =>_NXXXXX,1,Ringing
exten =>_NXXXXX,2,Dial(CAPI/contr2/b${EXTEN}|30)
exten =>_NXXXXX,2,Dial(CAPI/contr2/b${EXTEN})

Analog Controller for 2 Digit Extensions!
exten =>_XX,1,Ringing
exten =>_XX,2,Dial(CAPI/contr1/b${EXTEN}|30)

Option 1

Download rpm from Dialogic
On redhat 9, the modules are compiled for the default kernel.
The config program sets everything up and loads the required drivers. Reasonably straight forward but restricts you to an older kernel.

Option 2


Kernel 2.6


As of now (linux kernel 2.6.8) the melware drivers for the Dilaogic Diva Server PRI-30M are unusable (at least in my setup ;-).. for the ones interested: Lots of "Badness "* messages on firmware load and consecutively failing hardware access, events [eg. ringing], ..).

Update: At least Dialogic Diva Server BRI seems to work fine with linux kernel 2.6.10. Just compile Dialogic ISDN kernel drivers provided with vanilla kernel as modules, get divactrl ftp://ftp.isdn4linux.org/pub/isdn4linux/utils/eicon/, copy the required firmware ftp://ftp.isdn4linux.org/pub/isdn4linux/utils/eicon/firmware/ to /usr/share/eicon and start the card with "divactrl -c 1 -f ETSI" (assuming EURO isdn protocol and 1 card). Afterwards the asterisk CAPI module chan_capi.so from http://www.melware.org/ChanCapi fully works.

It will also work with Kernel 2.6.9. Compile with the latest drivers, then downloaded firmware and divactrl as above. I am in Australia and I found that I could NOT get the card to work with a simple 'divactrl -c 1 -f AUSTRAL' - All that happens is you will get layer one, but no layer two. You need to edit all the config scripts in the /usr/share/eicon folder and correct the paths for your version of Linux (I used FC2 with Kernel 2.6.9), I had to modify most of the paths inside the scripts. Once you have the scripts working, run ./Config in /usr/share/eicon and configure your ports and settings. Config will output a startup script for the card containing your settings. I have got this successfully running with DID.

Note that the drivers seem to be at least partially broken in 2.6.11, 2.6.12 and at least up to 2.6.13rc3 (not tested any further than that). The symptoms are that when you dial out, when the other party picks up, the driver doesn't notice that they have done so so the caller keeps on hearing ringing.

Kernel 2.4


Things needed to get it running with linux kernel 2.4.x (tested with a vanilla 2.4.27):


The firmware files should be placed in /usr/share/eicon It used to be /usr/lib/isdn/eicon for previous releases.

Some READMEs that may be helpful:

  • Melware's Guide to installing the Dialogic Diva CAPI driver on Debian (most of the things said are applicable on other distributions, too)
  • README, accompanied with the Dialogic Diva Server firmware.

Since you will be using the (Kernel-)CAPI driver of your Diva Server card Asterisk needs support for that as well.. See here.

A little sidenote: Make sure you're setting the msn/incomingmsn to at least * or Asterisk won't accept any call(s).
If you do so (as in "use only * as msn") make sure you're checking for valid numbers in extensions.conf .


"CAPI Not Installed" error


If you get "CAPI Not Installed", try the following:

modprobe capi
modprobe kernelcapi
modprobe divacapi
modprobe divas


...and then load divactrl.

you should also check the permissions on /dev/capi20. it should be read and writeable by asterisk

Compressed/distorted audio in the US

(thanks to Armin from Melware for this)

chan_capi uses alaw (Europe) by default.

To switch to ulaw, set the define in the Makefile of chan_capi-cm.

According to Armin:

Latest version (on http://www.chan-capi.org), you can specify ulaw=yes in the file capi.conf and no compile-time switch is necessary.

...although I just edited the Makefile and did a make clean;make;make install and it worked.


Back to Asterisk How to connect with CAPI






Dialogic Diva Server drivers


(Dialogic was formerly known as Eicon Networks).

There are different ways to use the Dialogic Diva cards. YMMV depending on config.

Option 0 Suitable for ALL Kernel Versions

This is the easiest way to get your Dialogic Diva Card installed under Asterisk.

If you have any problems please contact the Dialogic support Helpdesk in either EMEA, America or Asia Pacific

Please note, that whilst Dialogic can offer support on the Dialogic-specifc parts of the installation, if your problem is more general such as unable to compile asterisk, or unable to compile chan_capi, then we recommend you contact the support forum for that particular package


First download the latest driver for your system from the Dialogic website. The best way is to download the latest source driver of the DivaServer4Linux code. This is available through this page

You should not have the ISDN4Linux driver installed as the Diva Server for Linux drivers includes the Melware CAPI driver. You should also not have the HiSax driver installed.

This code is suitable for all kernel versions including 2.6.X and for all Diva Server cards.
Note : The latest driver available (divas4linux_EICON-106.10-1) can't be compiled on a 2.6.17 and more (DevFS was removed). Use 2.6.16.37

Once you have filled in this form you will be able to download the source driver.

Then follow the instructions on this page to build the driver:

http://www.dialogic.com/support/helpweb/slnxen/Install-FromSource.asp

Then, follow the instructions to configure your card. Make sure that as part of the configuration you specify that you want to use the CAPI Interface.

http://www.dialogic.com/support/helpweb/slnxen/default.htm


After installing your card, you then need to install the chan_capi driver from sourceforge. This will require that you have a file called capi20.h available on the system. To do this just make sure that you install the
isdn4k-utils-devel
package on your system.


Then edit your capi.conf. The following example shows a system with two cards installed - a Diva Server PRI 30M, and also a Diva Server V-Analog 8P card.

fedcore2:/root# more /etc/asterisk/capi.conf
;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
alaw=yes

[PRI30M]

;Define CAPI Controller Interface for PRI-30M
;mode=immediate
isdnmode=DID
ntmode=yes;
incomingmsn=*
controller=2
softdtmf=0
accountcode=
context=isdn
callgroup=1
devices=30
echocancel=yes

[V-Analog8P]
;Define CAPI Controller Interface for V-Analogue 8P
;mode=immediate
isdnmode=DID
ntmode=yes;
incomingmsn=*
controller=1
softdtmf=0
accountcode=
context=analog
callgroup=1
devices=2
echocancel=yes


In you extensions.conf file you can then include lines such as

exten =>_NXXXXX,1,Ringing
exten =>_NXXXXX,2,Dial(CAPI/contr2/b${EXTEN}|30)
exten =>_NXXXXX,2,Dial(CAPI/contr2/b${EXTEN})

Analog Controller for 2 Digit Extensions!
exten =>_XX,1,Ringing
exten =>_XX,2,Dial(CAPI/contr1/b${EXTEN}|30)

Option 1

Download rpm from Dialogic
On redhat 9, the modules are compiled for the default kernel.
The config program sets everything up and loads the required drivers. Reasonably straight forward but restricts you to an older kernel.

Option 2


Kernel 2.6


As of now (linux kernel 2.6.8) the melware drivers for the Dilaogic Diva Server PRI-30M are unusable (at least in my setup ;-).. for the ones interested: Lots of "Badness "* messages on firmware load and consecutively failing hardware access, events [eg. ringing], ..).

Update: At least Dialogic Diva Server BRI seems to work fine with linux kernel 2.6.10. Just compile Dialogic ISDN kernel drivers provided with vanilla kernel as modules, get divactrl ftp://ftp.isdn4linux.org/pub/isdn4linux/utils/eicon/, copy the required firmware ftp://ftp.isdn4linux.org/pub/isdn4linux/utils/eicon/firmware/ to /usr/share/eicon and start the card with "divactrl -c 1 -f ETSI" (assuming EURO isdn protocol and 1 card). Afterwards the asterisk CAPI module chan_capi.so from http://www.melware.org/ChanCapi fully works.

It will also work with Kernel 2.6.9. Compile with the latest drivers, then downloaded firmware and divactrl as above. I am in Australia and I found that I could NOT get the card to work with a simple 'divactrl -c 1 -f AUSTRAL' - All that happens is you will get layer one, but no layer two. You need to edit all the config scripts in the /usr/share/eicon folder and correct the paths for your version of Linux (I used FC2 with Kernel 2.6.9), I had to modify most of the paths inside the scripts. Once you have the scripts working, run ./Config in /usr/share/eicon and configure your ports and settings. Config will output a startup script for the card containing your settings. I have got this successfully running with DID.

Note that the drivers seem to be at least partially broken in 2.6.11, 2.6.12 and at least up to 2.6.13rc3 (not tested any further than that). The symptoms are that when you dial out, when the other party picks up, the driver doesn't notice that they have done so so the caller keeps on hearing ringing.

Kernel 2.4


Things needed to get it running with linux kernel 2.4.x (tested with a vanilla 2.4.27):


The firmware files should be placed in /usr/share/eicon It used to be /usr/lib/isdn/eicon for previous releases.

Some READMEs that may be helpful:

  • Melware's Guide to installing the Dialogic Diva CAPI driver on Debian (most of the things said are applicable on other distributions, too)
  • README, accompanied with the Dialogic Diva Server firmware.

Since you will be using the (Kernel-)CAPI driver of your Diva Server card Asterisk needs support for that as well.. See here.

A little sidenote: Make sure you're setting the msn/incomingmsn to at least * or Asterisk won't accept any call(s).
If you do so (as in "use only * as msn") make sure you're checking for valid numbers in extensions.conf .


"CAPI Not Installed" error


If you get "CAPI Not Installed", try the following:

modprobe capi
modprobe kernelcapi
modprobe divacapi
modprobe divas


...and then load divactrl.

you should also check the permissions on /dev/capi20. it should be read and writeable by asterisk

Compressed/distorted audio in the US

(thanks to Armin from Melware for this)

chan_capi uses alaw (Europe) by default.

To switch to ulaw, set the define in the Makefile of chan_capi-cm.

According to Armin:

Latest version (on http://www.chan-capi.org), you can specify ulaw=yes in the file capi.conf and no compile-time switch is necessary.

...although I just edited the Makefile and did a make clean;make;make install and it worked.


Back to Asterisk How to connect with CAPI






Created by: macky, Last modification: Mon 11 of Jun, 2012 (02:53 UTC) by admin
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+