Rhino® Open Source Telephony PCI and PCI Express Cards for Linux User Manual Models: T1/E1 Models: •R1T1, R1T1e: Single port T1 PCI card •R2T1, R2T1e: Dual port T1 PCI card •R4T1, R4T1e: Quad port T1 PCI card Fixed Analog Models: •R4FXOEC: Quad FXO Channels with Echo Cancellation •R24FXSEC: 24 port FXS Channels with Echo Cancellation •R24FXOEC: 24 port FXO Channels with Echo Cancellation Modular Analog Models: •R8FXX: Modular Octal FXS/FXO with Echo Cancellation •R24FXX: Modular 24 FXS/FXO with Echo C
Managing your open source telecommunication needs has never been easier than with Rhino products. Rhino PCI plugin cards satisfy the needs of Open Source Telephony (OST) applications, no matter how stringent the requirement. Rhino Open Source Telephony PCI cards feature Asterisk* and Linux tested software. Knowing that Rhino products are ready to perform right out of the box means that you can spend more time developing important customer relationships. Rhino Equipment Corp.
* Asterisk is a registered trademark of Digium. Software License All Rhino OST PCI cards require Linux module software to operate. We distribute our software under the GNU General Public License, which is enclosed here for your review.(as obtained from http://www.gnu.org/copyleft/gpl.html) GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1.
. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6.
User Information for FCC Part 68 Products: R1T1, R1T1e, R2T1, R3T1e, R4T1, R4T1e, R4FXO, R8FXX, R24FXX, R24FXS, and R24FXO models This equipment complies with Part 68 of the FCC rules and the requirements adopted by the ACTA. On the bottom of this equipment is a label that contains, among other information, a product identifier in the format US: AAAEQ##TXXXX (where “X’s” are shown will represent product number, for example R1T1). If requested, this number must be provided to the telephone company.
User Information for FCC Part 15 THIS DEVICE COMPLIES WITH PART 15 OF THE FCC RULES. OPERATION IS SUBJECT TO THE FOLLOWING TWO CONDITIONS: 1(1) THIS DEVICE MAY NOT CAUSE HARMFUL INTERFERENCE, AND 2(2) THIS DEVICE MUST ACCEPT ANY INTERFERENCE, RECEIVED, INCLUDING INTERFERENCE THAT MAY CAUSE UNDESIRED OPERATION. NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules.
This page intentionally left blank. Rhino Equipment Corp. • 8240 S. Kyrene Rd.
Table of Contents: Rhino® Open Source Telephony PCI and PCI Express Cards .......................................................................................................................................1 for Linux.........................................................................................................................................................1 Software License.........................................................................................................................
1. PREINSTALLATION Rhino OST PCI cards are easy to setup and use, which will make your telephony life easier! Please spend a few minutes reviewing these instructions to ensure a successful installation. 1.a Warranty Rhino OST PCI cards are covered by a 5year limited factory warranty. The warranty statement is available on the Rhino web site, the Rhino CDROM, the Rhino Public FTP, or by request. Please note that damage caused by improper installation or acts of nature are not covered by this warranty. 1.
2. INSTALLATION 2.a Site Selection The selected installation site should provide a stable operating environment. The area around the installation site should be clean and free from extremes of temperature, humidity, shock, and vibration. The operating temperature should be kept below 100 degrees F (38° C). The Rhino OST PCI card is designed to be used on T1/DS1/ISDNPRI/E1 services for a T1 card, or to be connected to the PSTN when using and analog card.
2.c Physical Installation Before removing the card from its packaging, ensure that you are grounded. To ground yourself please use an AntiStatic wrist band. While removing the Rhino OST PCI card take care to only handle the mounting bracket, avoid making contact with any of the PCI card circuitry. The Rhino OST PCI card is intended to be installed in an ATX form factor motherboard, the chassis housing the Rhino OST PCI card should also be an ATX form factor chassis.
3. INSTALLATION FOR T1 OST CARDS 3.a Connecting the Rhino T1 Card to T1/E1/PRI The Rhino OST T1 cards (DS1) interface is an industrystandard RJ48C eight pin connector with its connections described below. The T1 is usually connected to a Rhino CB24 channel bank or the telecommunications carrier demarcation point. If the T1 is coming from a Rhino CB24 channel bank, the T1 cable must be a crossover T1 cable. Figure 2 shows the pin out for building a T1 crossover cable.
If the T1 is coming from the demarcation point please use a straight thru T1 cable to connect to the Rhino OST T1 card. In some cases additional cable must be run from the carrier’s demarcation point to the customer’s suite or nearby “phone room”.
3.b Hardware Configuration Fig 3 Normally, no other configuration is necessary to get a Rhino digital telephony card to operate in a system. In cases where multiple cards are used within the same system, or mixed E1 and T1 modes are needed on the same card, additional configuration may be necessary. Timing Cable A special 20 pin ribbon cable can be used to connect multiple Rhino digital telephony cards to provide a common clocking source to all spans. In Fig.
R2T1 and R4T1 E1 Configuration: insmod /lib/modules/`uname r`/extra/rxt1.ko t1e1override=15 (if this does not work try: insmod /lib/modules/`uname r`/extra/rxt1.ko e1=15) Load Identifier (Module Instance Load order) Normally Linux loads PCI devices in the order that they are found on the PCI bus, most likely from the PCI slot closest to the CPU on the motherboard, and outward from that position.
ln s /usr/src/zaptelversion.number.tar.gz /usr/src/zaptel >6. Change your present working directory to /usr/src/zaptel cd /usr/src/zaptel >9. Compile Zaptel make && make install 10. In the “/usr/src/” directory please do the following ONLY IF your zaptel directory is different than “/usr/src/zaptel”: ln s /usr/src/zaptelxxx /usr/src/zaptel (where”/usr/src/zaptelxxx” is the path of your installed zaptel directory.) 11. Download the Rhino drivers in a single package: wget ftp://ftp.rhinoequipment.
For R2T1, and R4T1 type: modprobe rxt1 16. Move on to configuring the zaptel interface. For more information on span and channel configuration please refer to sections 3.d & 3.e. For configuration examples for Rhino analog PCI cards please refer to section 4.c For TrixBox Specific Installations: 1. Boot the PC and log in as “root” or other user that has appropriate software build privileges. 2. Install the Rhino RPM's: yum y install rhino`uname r` press ENTER 3.
3.d Rhino OST T1/E1 PCI card Port and Span configurations The first lines of the zaptel configuration file (comments excluded) will be the span definitions for T1/E1 interfaces. A span definition is in this format: span=(spannum),(timing),(LBO),(framing),(coding) (see next page for more examples) Spannum: Spannum defines the number assigned to the span these definitions apply to.
Tip: Problems with timing manifest themselves in different ways with static, pops, and channels or calls regularly dropping. LBO: Line Build Out (LBO) is taken from the table below. 0: 0 db (CSU) / 0133 feet (DSX1) 1: 133266 feet (DSX1) 2: 266399 feet (DSX1) 3: 399533 feet (DSX1) 4: 533655 feet (DSX1) 5: 7.5db (CSU) 6: 15db (CSU) 7: 22.5db (CSU) Framing: For T1 Framing is either d4 or esf. Coding is either ami or b8zs. For E1 – Framing is either cas or ccs. Coding is either ami or hdb3.
zaptel.conf ;Span 1 span=1,0,0,esf,b8zs ; First 4 channels are the FXO modular card fxsks=14 ; Next 16 channels are the 4 modular FXS cards fxols=520 zapata.conf ;First 4 channels are the FXO modular card signalling = fxs_ks channel => 14 ;Next 16 channels are the 4 modular FXS cards signalling = fxo_ks channel => 520 Once zaptel.conf and zapata.conf are configured, initialize the card with the new configuration values by running “ztcfg” from the Linux command prompt.
4. INSTALLATION FOR Rhino OST Analog CARDS 4.a Connecting Rhino Analog cards to telco/extensions. The Rhino OST PCI analog cards use an industry standard RJ11 four pin plug for the R4FXO quad port FXO card, with pin lay out shown below. And an industry standard RJ14 four pin plug for all octal modular cards (R8FXX), pin lay out is also shown below.
Rhino Equipment Corp. • 8240 S. Kyrene Rd.
4.c Rhino OST PCI Analog card Channel configurations Rule of Thumb: Have you ever heard someone say “Opposites attract”? The same is true when configuring Zaptel and Zapata for your Rhino OST PCI card. When configuring the signaling for your interface channels remember that physical FXO channels require FXS signaling and physical FXS channels require FXO signaling.
This assures that the firmware file will be updated the next time the Rhino module is loaded, which normally happens when the PC boots. You can manually force this event using: rmmod rcbfx modprobe rcbfx or to force the uploading of the any version of firmware to the rcbfx analog card, which is the last version that was “installed” using the install command: rmmod rcbfx insmod /lib/modules/`uname r`/extra/rcbfx.
4.f Connecting Power to the Rhino R8FXX, R24FXX, and R24FXS Analog card installations Remember that the Rhino R8FXX card has only four physical connections on the back of the card, and eight total analog line connections. This is accomplished by using BOTH of the wire connections on a RJ11 plug. The center two pins are line 1, and the outside two pins are line 2, on the top or first jack. Look on the back of the card to identify the channels: 12 are on the top, and 78 are on the bottom.
There are two locations to look for FXS power indication. A board level power indicator is located at the connector end, and is a green LED. Each FXS board also has a single LED that can be seen off the reflection of the main board, at the top of the card. Rhino Equipment Corp. • 8240 S. Kyrene Rd.
4.g Rhino R4FXO (Rev. C and higher) and R8FXX LED Codes There are eight status LEDs located on the top right of the R8FXX board that depicts channel status. GREEN STATE Off On Rapid Flash Slow Flash Ramp On/Off Line not in use Line in use Line ringing Line is in the process of being connected LED FXO line does not see battery You can also use zttool to show the raw signaling data.
5.0 Rhino FTP Site Please note that Rhino Equipment Corp. maintains a FTP site where all of the latest information is always available. ftp.rhinoequipment.com All rhino card drivers are provided within one installation package. When navigating to the Rhino FTP site, click on drivers and locate the updated package that you wish to install. It is simple to update your local copy of any Rhino driver by using wget, like this: wget ftp://ftp.rhinoequipment.com/Drivers/rhinoversion.#.
6.0 Useful LinuxAsterisk Commands (for CentOS, RedHat, and Fedora based systems) Commands from the Linux command line Tab key use this to “auto complete” command line entries, very useful! uname –r displays the kernel version cat /proc/zaptel/* shows the installed zaptel compatible cards and channels modinfo “driver name” shows information about the associated linux driver modprobe “driver name” load a module, in this case the rcbfx module, using the rules in /etc/modprobe.conf (i.e.
Commands to use from the Asterisk CLI zap show channels – shows the installed zap channels, this should mirror the zapata.conf channel configuration extensions reload – used to load changes made to any dial plan file without having to restart Asterisk service zaptel restart – reloads the zaptel modules and dependencies.
Set master password for GUI Set password for amp only Set password for Web MeetMe only Set root password for console login Set admin password for checking system mail Create a SIPDefault.cnf in /tftpboot Create a aastra.
Call Forward Busy Activate Call Forward Busy Deactivate *90 *91 Call Forward Busy Prompting Deactivate *92 Call Forward No Answer/Unavailable Activate *52 Call Forward No Answer/Unavailable Deactivate *53 Call Waiting Activate Call Waiting Deactivate DND Activate DND Deactivate My Voicemail Dial Voicemail Save Recording Check Recording Directory Call Trace Echo Test Speaking Clock Speak Your Exten Number ChanSpy Intercom Prefix *70 *71 *78 *79 *97 *98 *77 *99 # *69 *43 *60 *65 555 *80 Rhino Eq
Contact: Attn: Rhino Equipment Corp. CUSTOMER SERVICE DEPT. 8240 S. Kyrene Rd. Suite 107 Tempe, AZ 85284 Ph 4809401826, Fax 4809611826 Email support@rhinoequipment.com Phone (480) 9401826 or (800) 7857073 Thank you for choosing Rhino Equipment. Version 1.50 4/2007 Rhino Equipment Corp. • 8240 S. Kyrene Rd.
