Saturday, May 3, 2014

Setting up E1 on Rhino Digital Cards

Introduction:
The basic principle is that we need set E1 mode at the driver level. There are no jumpers or any other physical changes that need to be made for Rhino OST PCI Digital Cards to work in E1 mode.
 
1) Install the Digital PCI card into your server, If you are unclear on how to install your PCI card into your server please see the appropriate documentation located at:
 
 
1. log in to the server
2. Install the Rhino drivers
Elastix users please build the latest package:
3. yum install dahdi-devel kernel-devel gcc make
4. wget http://ftp.rhinoequipment.com/Drivers/Beta/rhino-linux-0.99.3-beta2.tbz2
5. tar -xjvf rhino-linux-0.99.3-beta2.tbz2
6. cd rhino-linux-0.99.3-beta2
7. make && make install
8. depmod -a
9. Edit the modprobe.rhino (or rhino.conf) for E1 mode as the article states
10. reboot
Trixbox users please use the setup-rhino command,
Alternatively the latest package is located at
http://downloads.rhinoequipment.com/Drivers/RPMS/trixbox/
All other distrobutions please use the package located in the trixbox repo:
yum install -y rhino-$(uname -r)
Alternatively you can also manually intstall the latest RPM from the following location:
http://downloads.rhinoequipment.com/Drivers/rhino -current.tbz2
rpm -ivh rhino-current.rpm
 
3) Either insmod or modprobe with E1:
 
NOTE: Make sure that the r1t1 or rxt1 drivers are not loaded when trying to switch to E1
modprobe r1t1 e1=1
In most kernels you can have this parameter set by adding the following to modprobe.conf or changing it in modprobe.rhino if it exists:
Generally you will need to have the modprobe r1t1 e1=1 in whatever file that you set to call the module on system start up.
R1T1
modprobe r1t1 e1=1
R2T1 or R4T1
modprobe rxt1 t1e1override=15
or you may have to use the following if the above does not work R1T1 modprobe r1t1 e1=1 R2T1 or R4T1 modprobe rxt1 t1e1override=15
vi /etc/modprobe.conf
#add drivers to blacklist to prevent the kernels AUTO LOAD
blacklist rcbfx
blacklist r1t1
blacklist r4fxo
blacklist rxt1
#dahdi_cfg after modprobe...
install r1t1 modprobe --ignore-install r1t1 && dahdi_cfg -vvv || /bin/true
install rxt1 modprobe --ignore-install rxt1 && dahdi_cfg -vvv || /bin/true
install rcbfx modprobe --ignore-install rcbfx && dahdi_cfg -vvv || /bin/true
install r4fxo modprobe --ignore-install r4fxo && dahdi_cfg -vvv || /bin/true
#set options for drivers
options r1t1 e1=1 ec_disable=0 debug=0
options rxt1 t1e1override=0 ec_disable_1=0 ec_disable_2=0 ec_disable_3=0 ec_disable_4=0 debug=0
options rcbfx debug=0
4) Next, make sure that you now have 31 channels on your zaptel span
cat /proc/dahdi/*
5) Configuring of the card is now necassary, lets edit vi /etc/dahdi/system.conf
loadzone = uk
defaultzone = uk
span = 1,1,1,ccs,hdb3,crc4
bchan = 1-15,17-31
dchan = 16
6) Now configure vi /etc/asterisk/chan_dahdi.conf
[trunkgroups]
[channels]
context=from-pstn
switchtype=euroisdn
pridialplan=unknown
;prilocaldialplan=unknown
;overlapdial=yes
signalling=pri_cpe
;rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
;transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=no
echocancelwhenbridged=no
rxgain=0.0
txgain=0.0
group=1
inbanddisconnect=yes
callgroup=1
pickupgroup=1
immediate=no
channel => 1-15,17-31
7) Now define your trunks, dialing routes and test.
If you are still experiencing difficulties please contact Rhino Support immediately and we will get you setup right away!
clip_image002

No comments:

Post a Comment