http://support.red-fone.com/index.php?

_m=knowledgebase&_a=viewarticle&kbarticleid=20

DAHDI Installation and Configuration

Author:

Redfone Communications
Created On: 30 Nov 2008 10:20 PM

DAHDI Installation and Configuration Instructions for Asterisk-1.4.22 and Asterisk-1.6

Applies to the following foneBRIDGE2 Models: 750-5000, 750-5000-EC, 750-5050, 750-5050-EC, 750-5050-Single, 750-5050-EC-Single

Updated December 1, 2008 Asterisk-1.6 no longer supports Zaptel. It only contains support for DAHDI. See the following link for complete details; http://www.asterisk.org/node/48539 General update instructions for migrating from Zaptel to DAHDI can be found here;http://svn.digium.com/svn/dahdi/tools/tags/2.0.0/UPGRADE.txt The Redfone TDMoE driver has been ported to the new DAHDI framework and can be installed using the following instructions.
Download and Install Dahdi
1. Download and untar dahdi-linux and dahdi-tools # wget http://support.red-fone.com/downloads/dahdi/dahdi-linux-redfone-2.1.0.4.tar.gz
Page 1/8 Powered By Kayako SupportSuite

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

# wget http://support.red-fone.com/downloads/dahdi/dahdi-tools-redfone-2.0.0.tar.gz # tar -xzvf dahdi-linux-redfone-2.1.0.4.tar.gz # tar -xzvf dahdi-tools-2.0.0.tar.gz 2. Patch dahdi-tools # cd dahdi-tools # wget 'http://bugs.digium.com/file_download.php?file_id=20121&type=bug' -O - | patch -p0 3. Build dahdi-linux # cd dahdi-linux-2.1.0.4 # make clean # make # make install 4. Build dahdi-tools # cd dahdi-tools-2.0.0 # ./configure # make # make install # make config

Download and Install fonulator (RPM) configuration utility The following instructions explain how to install the fonulator for Redhat based systems such as CentOS, Fedora Core and others. 1. Download rpm # wget http://support.red-fone.com/downloads/fonulator/fonulator-2.0.0-36.i386.rpm 2. Install RPM # rpm -ivh fonulator-2.0.0-36.i386.rpm 3. Confirm fonulator has been installed properly by executing it from the command line # fonulator -V fonulator 2.0.0 Copyright (C) 2007 Redfone Communications, LLC. Build Number: 36 For advanced fonulator command line options execute with the --help flag. # fonulator --help Configuring foneBRIDGE Redfone.conf 1. Download sample redfone.conf file to your /etc/ directory; # cd /etc/
Page 2/8 Powered By Kayako SupportSuite

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

# wget http://support.red-fone.com/downloads/fonulator/redfone.conf 2. The Fonebridge MOD-B firmware now uses IP based communication for sending updates to the device. The default IP address of FB1 and FB2 are as follows: a. FB1=192.168.1.254 b. FB2=192.168.1.253 3. Configure the server's Ethernet interface used to communicate with the Fonebridge with an IP address from the same 192.168.1.X range. Ex; # ifconfig eth1 192.168.1.200 Alternatively an alias IP address can be assigned to an existing IP interface; # ifconfig eth1:0 192.168.1.200 NOTE: This IP should be made permanent and done with your Linux distro's normal utilities for setting IP addresses. 4. Edit the redfone.conf file with your favorite text editor (nano,pico,vi, etc.) 5. Under the [globals] section change the server= MAC address to reflect the MAC address of your server's Ethernet card that will be communicating with the Fonebridge. You can determine the MAC address of your interface by issuing the ifconfig ethN command in Linux. Ex; # ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:16:36:76:09:91 6. The port= parameter designates which foneBRIDGE Ethernet port will be used to communicate with your Asterisk server. Valid options are 1 or 2 and correspond to FB1 and FB2 on the device Ex; port=1 7. [spanN] parameters are used to set the individual configurations of each T1/E1 port on the Fonebridge. Options per span include; framing= ccs,esf,sf,cas encoding=b8zs,hdb3 crc4= (used on some E1 lines) rbs= Used for CAS/RBS type lines on Channel Banks, E&M, etc. shorthaul=0-4 longhaul=0-3 (See LBO explanation at end of document)
Page 3/8 Powered By Kayako SupportSuite

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

loopback= Loopback to far end telco equipment for line testing NOTE: MFC/R2 requires 'framing=cas' A sample Quad T1 PRI redfone.conf might look like this; [globals] fb=192.168.1.254 port=1 server=00:11:22:33:44:55 [span1] framing=esf encoding=b8zs [span2] framing=esf encoding=b8zs [span3] framing=esf encoding=b8zs [span4] framing=esf encoding=b8zs A sample Quad E1 PRI redfone.conf might look like this; [globals] fb=192.168.1.254 port=1 server=00:11:22:33:44:55 [span1] framing=ccs encoding=hdb3 [span2] framing=ccs encoding=hdb3 [span3] framing=ccs encoding=hdb3 [span4] framing=ccs encoding=hdb3

Page 4/8 Powered By Kayako SupportSuite

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

Advanced Settings Longhaul and Shorthaul LBO Overview The 'longhaul' and 'shorthaul' parameters can be added under the [spanN] block of each span. These values should only be changed under advise from your TELCO. Aything with longhaul means the Adaptive Equalizer is ON! You can only choose longhaul or shorthaul, you cannot have both. Longhaul Values (longhaul='value') 0 => 0dB (No Attenuation, just turns on Adaptive Equalizer) 1 => -7.5dB 2 => -15.0dB 3 => -22.5dB Shorthaul Values (shorthaul='value') 0 => 0-133 feet 1 => 133-266 feet 2 => 266-399 feet 3 => 399-533 feet 4 => 533-655 feet Loopback The 'loopback' parameter, placed under the [spanN] block places that span in a loopback mode to be utilized by the Telco to test the T1/E1 circuit all the way to the fonebridge device. It is not useful for testing or debugging the Asterisk side of the connection or for running a local loopback. Echo Cancellation On EC enabled foneBRIDGE2 the Echo Cancellation hardware is automatically configured based on the span information in redfone.conf. If it is an E1, it will be configured for EC on E1 lines and the same for T1. The foneBRIDGE2 normally ships with the uLaw companding mode enabled in the DSP. When configuring E1 spans the first time it may cycle power to the foneBRIDGE2 core
Page 5/8 Powered By Kayako SupportSuite

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

in order to reset the DSP to aLaw companding which is the default for E1. This is a one-time occurrence. 8. Power on the fonebridge and once your redfone.conf file is complete you will update the fonebridge by executing the fonulator utility. The fonulator utility will read the information contained in your redfone.conf and provided all IP addressing is correct, send it to the fonebridge which will configure all of its spans as per your parameters, come on line and begin transmitting TDMoE traffic. Execute the fonulator utility from the Linux command line. Ex; # fonulator By default the fonulator will look for /etc/redfone.conf. You can specify an alternative file name by affixing the full file name path after fonulator. Ex; # fonulator /etc/redfone2.conf You can also query the device with fonulator to determine what the current running configs are. Ex; # fonulator -vq Please note that if power is cycled to the fonebridge it will loose its current configuration and you will need to fonulate again. Configuring /etc/dahdi/system.conf The system.conf file follows all standard rules and syntax as other zaptel based hardware with the only exception being the use of the dynamic= parameter. NOTE: If using a Quad port Fonebridge you must always specify 4 dynamic spans in system.conf even if you have only configured a single span on the device. The same applies on the Dual port. Two dynamic spans must always be specified even if only 1 span has been configured in redfone.conf. dynamic=ethmf,<ethN>,/<FB MAC address>,/<span number>,<numchans>,<timing>

Page 6/8 Powered By Kayako SupportSuite

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

A sample 4x T1 PRI configuration would like the following; dynamic=ethmf,eth1/00:50:C2:65:D0:70/0,24,0 dynamic=ethmf,eth1/00:50:C2:65:D0:70/1,24,0 dynamic=ethmf,eth1/00:50:C2:65:D0:70/2,24,0 dynamic=ethmf,eth1/00:50:C2:65:D0:70/3,24,1 # bchan=1-23 dchan=24 bchan=25-47 dchan=48 bchan=49-71 dchan=72 bchan=73-95 dchan=96 # loadzone = us defaultzone=us In the above example, the Asterisk server is communicating on its eth1 with the fb address of 00:50:C2:65:D0:70. Span numbers start at 0. It has 24 channels (E1 would be 31) and timing begins at 4. A sample 2x E1 PRI configuration would look like the following; dynamic=ethmf,eth1/00:50:C2:65:D0:70/0,31,2 dynamic=ethmf,eth1/00:50:C2:65:D0:70/1,31,1 # bchan=1-15,17-31 dchan=16 bchan=32-46,48-62 dchan=47 # # NOTE: Most E1 use alaw codec and this must be specified. alaw=1-62 # loadzone = us defaultzone=us Starting dahdi After successfully installing dahdi, configuring redfone.conf and system.conf you can now load the necessary dahdi modules. 1. Load modules # modprobe dahdi # modprobe dahdi_dynamic_ethmf

Page 7/8 Powered By Kayako SupportSuite

http://support.red-fone.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=20

2. Confirm modules loaded properly with dahdi_tool # dahdi_tool If you do not see any spans you may need to execute 'dahdi_cfg' and then check 'dahdi_tool'. Once the Fonebridge device has been configured via the fonulator tool you should see a YEL alarm (as shown above) at a minimum in dahdi_tool. If your PRI or other telco equipment is already cabled and the Fonebridge has been updated with the proper configuration parameters then you should see an OK state in dahdi_tool. 6. Download and Install libpri and Asterisk 1.6 7. Edit /etc/dahdi/system.conf 8. Edit redfone.conf

Page 8/8 Powered By Kayako SupportSuite