Archive for November, 2007

HDLC and FCS abort errors with Rhino T1/E1 Cards and PRI

Tuesday, November 20th, 2007

If you are seeing HDLC and FCS aborts in your logs. This is could be due to one of the following reasons:


Make sure that your T1/E1 cards are at the following revisions and have the apropriate drivers installed on your system.

R1T1 -EC and Non-EC models must be at Hardware version 37 or above

R2T1 and R4T1 must be at Hardware version 36 or above

Driver revision must be at 2.0 and above.

If the above criteria is not met then you may see the aborts in your logs.


If you are using CentOS4 and are using SATA drives you may see this issue.

You must use a kernel greater than 2.6.9.

By upgrading to an asterisk distribution with an updated kernel such as CentOS5 will alleviate these issues.

Please try one of the following systems:


trixbox CE 2.4 (Beta for Cent 5)

RhinOSterisk (Alpha)

NEW Driver Release Party!!!

Tuesday, November 13th, 2007

We have just released a new set of Drivers. Driver package rhino-2.2.1

You can get the latest and greatest Rhino Drivers today from the following location:

NOTE: If you are using Rhino Digital PCI cards that were purchased prior to 10/15/07 you MUST

upgrade your hardware revision. To do this please read the blog listed bellow, or contact

Rhino technical support for assistance.

Configuring Your Rhino Digital Card For E1 Signalling

Friday, November 2nd, 2007

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. Everything is done at the driver level.

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 following documentation:

2) Install the Rhino drivers

trixbox CE users please use an updated package that is located at

All other distrobutions please use the package located at

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

insmod /lib/module/`uname -r`/extra/r1t1.ko e1=1

or you should be able to just modprobe with the settings

modprobe r1t1 e1=1

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.

If you are using an r1t1 then use:

modprobe r1t1 e1=1

For an r2t1 or r4t1 use:

modprobe rxt1 e1=15

4) Next, make sure that you now have 31 channels on your zaptel span

cat /proc/zaptel/*

5) Configuring of the card is now necassary, lets edit /etc/zaptel.conf

NOTE: This is just a generic view of what the zaptel.conf should look like


(NOTE- the framing is dependent on what your carrier uses Rhino has no knowledge of what you should be specifically using for your telephony system)


dchan= 16

6) Now configure /etc/asterisk/zapata.conf or zapata-auto.conf or you may even be using zapata-channels.conf




7) Now define your trunks and dialing routes and test.

If you are still experiencing difficulties please contact Rhino Support immediately and we will get you setup right away!