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

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:

1:

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.

2:

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:

Elastix

trixbox CE 2.4 (Beta for Cent 5)

RhinOSterisk (Alpha)

NEW Driver Release Party!!!

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:

ftp://ftp.rhinoequipment.com/Drivers/rhino-current.

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.

https://support.rhinoequipment.com/blog/2007/09/14/r4t1-ec-hardware-upgrade/

Configuring Your Rhino Digital Card For E1 Signalling

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:

ftp://ftp.rhinoequipment.com/Documentation

2) Install the Rhino drivers

trixbox CE users please use an updated package that is located at ftp://ftp.rhinoequipment.com/Drivers/RPMS/trixbox/

All other distrobutions please use the package located at ftp://ftp.rhinoequipment.com/Drivers/Beta/rhino-2.2.1beta2.tbz2

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

span=1,1,0,ccr,hdb3,crc4

(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)

bchan=1-15,17-31

dchan= 16

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

signalling=pri_cpe

context=from-zaptel

channel=>1-15,17-31

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!

Security Advisory

October 25th, 2007

People are scanning port 22 and doing dictionary attacks. Log in to a console or ssh session and change your root password to a non dictionary word with the command passwd

Read the rest of this entry »

Known Issues:

October 23rd, 2007

As of last testing we have observed the following issues. This list is as of 10/23/2007. Please note user experience may vary and some of these issues may have been resolved in later builds and only apply to the versions listed.

trixbox CE

2.2.3 - genzaptelconfig does not recognize our cards.

2.2.x> the 2.6.9 kernel does not properly implement apic and has poor IRQ managemen. Use of multiple high interrupt devices like Digital Cards in combination with each other, extra network devices or RAID will cause interrupt issues and instability.

2.2.4 Zaptel does not install. You can run yum -y install zaptel-*

Digital cards shipped after 10/05/2007 require a new driver use the 2.2.1 package in the beta directory of our ftp. If you recieved a digital card in a ceros this update has been made.

Zaptel version 1.4.2.1 Does not build correctly. This seems isolated to this version

Some Qwest and Ameritech lines are not sending voltages across correctly. This issue may also occur in other AT&T regions. This issue can be overcome by upgrading your rcbfx firmware to 1.11.

Rhinosterisk 70021008-0917may not have an extensions.conf. You can correct this by rerunning install_amp

Some netgear routers will randomly reboot with qos and vlan enabled causing SIP delays.

Atacomm Customers

September 26th, 2007
Rhino currently does not have any outstanding orders from Atacomm for
equipment. If you have placed an order and paid Atacomm for Rhino
products and have not recieved the product please email
sales@rhinoequipment.com with your orders details.

zaptel 1.4.2.1

September 25th, 2007

Zaptel 1.4.2.1 Does not compile correctly and is missing calls required by our drivers. This has been observed in this version and appears to be resolved in other versions. If you have the kernel headers, and zaptel installed and linked per our instructions you should be able to simply make and make install. If the dependencies are met and the build fails try a higher or lower version of zaptel and it should clear up.

GenZaptelConf

September 25th, 2007

The trunk version of genzaptelcon does not work with rhino cards, However genzaptelconf can be adjusted to work with any card. Read the rest of this entry »

Rhino Equipment Corp announces EchoClearTM

September 21st, 2007

R1T1 EC

Rhino Equipment Corp. is pleased to announce the release of the EchoClearTM plug-in PCI and PCI Express digital echo cancellation daughter card, which can be simply plugged-in to upgrade our Rhino line of digital telephony cards. The Rhino digital telephony product line consists of three T1/E1/J1/ISDN/PRI PCI digital cards, the R1T1, R2T1 and R4T1, that all interface with Asterisk-based PBX systems. Each card can now be upgraded with the Rhino EchoClearTM echo cancellation system with the addition of the Rhino Echo Cancellation (REC1) card.

Read the rest of this entry »

Calling Linux and Asterisk Gurus

September 20th, 2007

Be part of the next big thing… well sorta…… Read the rest of this entry »