Archive for the ‘PCI Cards’ Category

Rhino Package Release 2.2.6

Tuesday, May 13th, 2008

We have released our 2.2.6 driver package. The change log is below. Rpm’s are also availible to trixbox users wh have he rhino-util package via setup-rhino

May 09, 2008    brycec    2.2.6
Version 2.2.6 released. This includes all the below fixes.

May 08, 2008    brycec    2.2.5.5
Resolved bug when unloading the R1T1 “dirty” causing a kernel
panic.
This is the sixth beta release before 2.2.6

May 01, 2008    brycec    2.2.5.4
Fixed the soft-lockup during firmware updating.
Several E1 audio fixups.
This is the fifth beta release before 2.2.6

Apr 09, 2008    brycec    2.2.5.3
TDM/DSP bus routing changes to resolve echo on SIP-Zap calls.
Increased error-resiliency for digital EC cards.
This is the fourth beta release before 2.2.6

Apr 04, 2008    brycec    2.2.5.2
Resolved lockup issues with Trixbox 2.6 (and others sharing its kernel)
Reworked DSP communications to be more CPU-friendly. This is a result
of fixing a bug causing lockups in Trixbox 2.6.
This is the third beta release before 2.2.6

Mar 28, 2008    brycec    2.2.5.1
Resolved issue when using the REC on an E1. The symptom was garbled audio.
Several tweaks in the Makefile to keep up with the changing Kernel and
Zaptel layouts.
Updated IRQ routines for the current Zaptel/Kernel versions.
This is the second beta release before 2.2.6

Feb 25, 2008    brycec    2.2.5.0
First public changelog.
Resolved an issue in which under certain circumstances, when a call was hung
up and echo cancellation disabled, the echo cancellation was actually disabled
on another channel. This issue only affected the rxt1 driver on cards with EC.
This is a the first beta release before 2.2.6

2.6.18+ kernel users

Wednesday, December 26th, 2007

I have put together a modprobe for users of hot-plugging kernels like 2.6.18 that use modprobe.

(more…)

trixbox CE 2.2 zaptel delemma

Wednesday, December 26th, 2007

A trixbox user has done a full post on preventing issues seen with zaptel when you run yum update in 2.2 while booted to a non smp kernel. Basically add to your the trixbox yum repo file a exclude=*smp. A full explanation is at http://blogx.co.uk/Comments.asp?Entry=679 . Please note his article is for a specific issue but covers a broader scope.

Elastix Now Supported!!!

Monday, December 17th, 2007

Rhino Equipment is pleased to announce the availability of Elastix on our Rhino Ceros line of equipment.

Elastix allows us to gain a stable platform that is fully compatible out of the box with modern hardware such as PCI Express and SATA. This allows for proper use of interrupt management features like ACPI. All of this without losing the PBX features you have come to love.

You also gain new features such as an integrated HylaFax server, Communications and more flexibility through the web UI.

This system has been fully tested and integrated into our Rhino Ceros product. We recommend the 2.6.18 and above kernel for boxes that contain multiple network cards, digital cards used in conjunction with other digital or analog cards, and PCI-E cards. This kernel is native to the Elastix distrobution.

For more information please visit:

http://www.elastix.org

http://www.rhinoequipment.com

yum update -y

Monday, December 10th, 2007

FYI all trixbox CE users

Just to give everyone a heads up from the Rhino’s mouth. Rhino products are proud to continually work with trixbox CE and future trixbox distributions. We also take great pride in our customers and realize that the more information that is posted the better informed we all are. That is why we take it very seriously to keep our customers informed of any ongoing issues with our hardware and distributions that we recommend.

The following issue has been popping up all over so please be aware of what you are installing at all times.

Please note that if you do a yum update for any of the following systems we cannot support your system until the system has been completely restored to factory settings.

trixbox CE 2.2

trixbox CE 2.2.1

trixbox CE 2.2.2

trixbox CE 2.2.3

trixbox CE 2.2.4

trixbox CE 2.2.5

trixbox CE 2.2.6

trixbox CE 2.2.7

trixbox CE 2.2.8

trixbox CE 2.2.9

This includes any future releases on the trixbox CE 2.2.x branch

This is due to errors in the trixbox repositories and this leads to corruption to your trixbox system.

The repositories for the upcoming trixbox 2.4 will be updated from what our trixbox sources have said, but for the trixbox 2.2.x repository this is not something that they can currently fix.

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:

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!!!

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:

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

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:

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!

zaptel 1.4.2.1

Tuesday, 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

Tuesday, September 25th, 2007

The trunk version of genzaptelcon does not work with rhino cards, However genzaptelconf can be adjusted to work with any card. (more…)