1. Manuals
  2. Brands
  3. Digium Manuals
  4. Switch
  5. R800
  6. Administrator's manual

Digium R800 Administrator's Manual

R-series
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
R-Series
Administrator Manual
601-00018
Rev. A1

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the R800 and is the answer not in the manual?

Questions and answers

Related Manuals for Digium R800

Summary of Contents for Digium R800

  • Page 1 R-Series Administrator Manual 601-00018 Rev. A1...
  • Page 2 Digium, Inc. Digium, Inc. has made every effort to ensure that the instructions contained in this document are adequate and error free. The manufacturer will, if necessary, explain issues which may not be covered by this documentation.
  • Page 3 EMC: 47 CFR Part 15, Subpart B / 47 CFR Part 15, Subpart B, Class A EN55022:2010 IEC CISPR22:2009 Class A IEC 61000 EN 61000-3-2:2006 +A1 & A2 EN 61000-3-3:2008 EN 55024:2010 CNS13438:2006 VCCI V-3 2010.04 Digium, Inc. Page 3...
  • Page 4 This device complies with part 15 of FCC rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. Digium, Inc. Page 4...
  • Page 5 State Descriptions Describes the states supported by the unit. Pin Assignments Lists the connectors and pin assignments. License Agreement Digium End-User Purchase and License Agreement Glossary and Defines terms related to this product. Acronyms Digium, Inc. Page 5...
  • Page 6 (ESD) wrist strap while handling the device. The Electrical Hazard Symbol indicates a possibility of electrical shock when operating this unit in certain situations. To reduce the risk of damage or injury, follow all steps or procedures as instructed. Digium, Inc. Page 6...

  • Page 7: Important Safety Instructions

    To reduce the risk of damaging the unit or your equipment, do not attempt to open the enclosure or gain access to areas where you are not instructed to do so. Refer servicing to qualified service personnel. Save these instructions for future reference. Digium, Inc. Page 7...

  • Page 8: Table Of Contents

    R-Series Control Utility ........34 Automatic Failover Configuration ......39 Digium, Inc. Page 8...
  • Page 9 Glossary and Acronyms ........123 Digium, Inc.
  • Page 10 Basic Application Sequence ....13 Figure 2: R800 Analog Unit ......20 Figure 3: R850 Digital Unit .
  • Page 11 RJ11 Port Connector ......108 Table B-2: RJ45 Port Connector ......110 Digium, Inc. Page 11...

  • Page 12: Overview

    Chapter 1 Overview The Digium Redundancy Series of products, R-Series, are versatile devices used to facilitate physical layer switching of PSTN interfaces for Asterisk based redundant PBX configurations. R-Series is among several key technologies Digium is introducing to empower Asterisk integrators to create advanced high-reliability failover solutions.

  • Page 13: Figure 1: Basic Application Sequence

    Chapter 1: Overview Figure 1: Basic Application Sequence There are a variety of applications where the R-Series units can prove useful. Digium, Inc. Page 13...

  • Page 14: What Is Asterisk

    Asterisk as a Gateway It can also be built out as the heart of a media gateway, bridging the legacy PSTN to the expanding world of IP telephony. Asterisk’s modular Digium, Inc. Page 14...

  • Page 15: Asterisk In The Call Center

    Exchange Carriers (CLECs) and even first-tier incumbents have discovered the power of open source communications with Asterisk. Feature servers, hosted services clusters, voicemail systems, and pre-paid calling solutions, all based on Asterisk have helped reduce costs and enabled flexibility. Digium, Inc. Page 15...

  • Page 16: Asterisk Everywhere

    Chapter 1: Overview Asterisk Everywhere Asterisk has become the basis for thousands of communications solutions. If you need to communicate, Asterisk is your answer. For more information on Asterisk, visit http://www.asterisk.org or http:// www.digium.com. Digium, Inc. Page 16...

  • Page 17: Unit Installation

    Hardware Installation on page 25  Software Installation on page 30  Note: The R-Series unit installation instructions are written so that they will apply to any model in the series. Examples and model specific information are included as needed. Digium, Inc. Page 17...

  • Page 18: Unpacking The Unit

    If damage is suspected, file a claim with the carrier and contact the reseller from which the unit was purchased. If the unit was purchased direct from Digium, contact Digium Technical Support at +1.256.428.6161. Keep the original shipping container to use for future shipment or proof of damage during shipment.

  • Page 19: Shipment Inspection

     Quickstart Guide  Note: After inspecting the shipment, Digium highly recommends that you register the unit for support eligibility. Please refer to Free Installation Support on page 104 for additional information on how to obtain assistance from Digium Technical Support.

  • Page 20: Front Panel Identification

    Secondary Primary Input Input (RJ21) Secondary USB Device Status Secondary Status Device ID Primary USB USB Console Primary Status Figure 2: R800 Analog Unit Passthrough Input Secondary Primary Input Secondary USB Device Status Secondary Status Device ID Primary USB USB Console...
  • Page 21 Device ID - This dial should be set to a number which is unique across  all R-Series units that co-exist in an installation. The Device ID assignment for your first device should be 0, second device should be 1, third device should be 2, and so on. Digium, Inc. Page 21...
  • Page 22 PBX, powering the R-Series unit, and accessing ASCII Mode. A USB A-B cable should be connected from this port to a USB port on the Secondary PBX. See ASCII Mode on page 87 for more informa- tion. Digium, Inc. Page 22...

  • Page 23: Unit Identification

    RJ21 for an alternate input method. See Table 1 for a list of the various models. Table 1: R-Series Models Model Type Ports Passthrough RJ21 Input R800 POTS R850 T1/E1/BRI Not Applicable Note: Passthrough is reserved for future use. Caution Only qualified service personnel should continue with hardware installation and configuration of the R-Series unit.

  • Page 24: Usb Requirements

    The servers which connect to an R-Series unit using the USB Console, Primary USB, and Secondary USB ports must support USB 1.1 or greater for compatibility. If either server does not support at least USB 1.1, an R- Series unit will not work. Digium, Inc. Page 24...

  • Page 25: Hardware Installation

    Note: Taking into consideration the requirements of all equipment that is connected to or sharing the rack, the server rack should be properly grounded. Refer to the manufacturer of the rack for instructions on how to properly ground the rack. Digium, Inc. Page 25...
  • Page 26 Front Panel Identification on page 20. Please refer to that section to determine what should be connected to each connector. Connections to an R-Series unit should be made in the following order. 1. Primary 2. Secondary Digium, Inc. Page 26...
  • Page 27 A generator may also be used as an alternate means of powering the servers while mains power is out. Digium, Inc. Page 27...
  • Page 28 R-Series unit. In addition, all command-line applications mentioned in this manual must be executed as the root user. Log in and execute the following command to list the devices detected by the USB controller: # lsusb Digium, Inc. Page 28...

  • Page 29: Table 2: Unit Identifiers

    R850 ea60 A Digium R-Series (R800 / R850) unit identifier should be listed. If a matching unit identifier is not listed, then your machine is not USB 1.1 (or higher), and the unit will not work with your motherboard.

  • Page 30: Software Installation

    R-Series unit. Digium hardware which relies on DAHDI requires drivers and libraries that are not integrated with the Linux kernel. Digium hardware is only supported under Linux. Digium recommends CentOS, Debian, Red Hat, and Ubuntu distributions of Linux. However, many other distributions are supported by Digium Technical Support.

  • Page 31: Chapter 3

    Chapter 2: Unit Installation To install your R-Series unit for use with other Digium hardware that relies on DAHDI, you will need: Linux 2.6 kernel headers  Development libraries and headers for ncurses  Development libraries and headers for zlib and openssl ...

  • Page 32: Configuration

    Each section explains basic options as examples. Once you have familiarized yourself with the examples, you can modify them to meet your specific needs. Digium, Inc. Page 32...

  • Page 33: Understanding Serial Device Assignments

    For example, an R-Series unit with a Device ID Dial assignment of 0 will have a device file associated at /dev/rseries0. We highly recommend referencing /dev/rseries[#] instead of /dev/ttyUSB[#] where possible. The rctl utility will be installed at a later point in the manual. Digium, Inc. Page 33...

  • Page 34: R-Series Control Utility

    Chapter 3: Configuration R-Series Control Utility Digium provides the source code for the R-Series control utility. This software should be installed on both the primary and secondary node. In the examples shown throughout this manual, substitute the X.X.X in rseries-X.X.X with the version of the R-Series source package.
  • Page 35 Primary. Lastly, it will change the state of each relay, one at a time, and verify that the state change was successful. Execute the following command to test relay state changes for the R-Series unit. # ./rtest.sh tests /dev/rseries[#] Digium, Inc. Page 35...
  • Page 36 Switching relays one at a time Getting control and setting port 1 to secondary...Success! Getting control and setting port 1 to primary...Success! Getting control and setting port 2 to secondary...Success! Getting control and setting port 2 to primary...Success! Digium, Inc. Page 36...
  • Page 37 Getting control and setting port 5 to primary...Success! Getting control and setting port 6 to secondary...Success! Getting control and setting port 6 to primary...Success! Getting control and setting port 7 to secondary...Success! Getting control and setting port 7 to primary...Success! Digium, Inc. Page 37...
  • Page 38 Chapter 3: Configuration Getting control and setting port 8 to secondary...Success! Getting control and setting port 8 to primary...Success! Digium, Inc. Page 38...

  • Page 39: Automatic Failover Configuration

    Automatic Failover Configuration This section describes a particular method for configuring an R-Series unit for automatic failover which is supported by Digium. This method provides automatic failover for the following situations. A software failure resulting in Asterisk no longer running.

  • Page 40: Figure 4: Automatic Failover Scenario

    PBX at any given time. This scenario describes what happens when a fatal hardware failure is experienced on the machine acting as the primary node. Actors PSTN  R-Series unit (digital version)  PBX A  PBX B  Figure 4: Automatic Failover Scenario Digium, Inc. Page 40...
  • Page 41 3. The host software on PBX B activates the floating IP address locally 4. The host software on PBX B starts Asterisk 5. PBX A comes back online and rejoins the cluster as a standby for PBX B Digium, Inc. Page 41...
  • Page 42 A configuration and statistics in-memory database that provides the  ability to set, retrieve, and receive change notifications of information. A quorum system that notifies applications when quorum is achieved  or lost.” - www.corosync.org Digium, Inc. Page 42...
  • Page 43 DRBD - “DRBD refers to block devices designed as a building block to form high availability (HA) clusters. This is done by mirroring a whole block device via an assigned network. DRBD can be understood as network based raid-1.” - www.drbd.org Digium, Inc. Page 43...
  • Page 44 The cluster messaging layer, Corosync, is in charge of determining cluster membership. If it loses contact with another node for any reason, it will decide that it has failed and failover will be initiated. Digium, Inc. Page 44...

  • Page 45: Digium, Inc

    Resource Agents Description Asterisk ocf:Digium:asterisk Asterisk RA Asterisk ocf:linbit:drbd DRBD link to share a filesystem ocf:heartbeat:Filesystem filesystem with configuration/log/spool directories and astdb. PSTN ocf:Digium:rseries Handled via R-Series connections hardware Floating IP ocf:heartbeat:IPaddr2 For VoIP connectivity address Digium, Inc. Page 45...
  • Page 46 Warning! The automatic failover scenario described in this chapter supports an Asterisk setup that uses Asterisk Business Edition, Skype for Asterisk, Fax for Asterisk, G.729, HPEC, and any other Digium product that requires registration using the Digium register utility only when additional licenses have already been purchased and registered on the secondary node.
  • Page 47 First, locate the device file that is created for each USB flash drive by executing dmesg on both the primary and secondary node. Look through the output of dmesg to locate the USB flash drive device file assignment. Digium, Inc. Page 47...
  • Page 48 The output shown above for this example identifies the USB flash drive being assigned a device file at /dev/sdb. The data on both USB flash drives must be “zeroed out” before initializing DRBD. Execute the following command on both the primary Digium, Inc. Page 48...
  • Page 49 USB flash drives that are of identical size and completely empty. The disk partition type must be Linux (0x83). Note: It is highly recommended that the partition for DRBD be 1GB or larger. Digium, Inc. Page 49...
  • Page 50 If both USB flash drives are of identical size, press Enter for last cyl-  inder. If the are of differing size, use a variation of the example “+1024M” for a 1,024MB (1GB) partition. Press w to write changes.  Digium, Inc. Page 50...
  • Page 51 # ls /dev/[USB_flash_device]* Note: The device file assigned to the USB flash drive’s partition will be referenced at a later point in the manual. It is important to take note of this assignment. Digium, Inc. Page 51...
  • Page 52 # apt-get install corosync pacemaker Red Hat Enterprise Linux 5 / CentOS 5 Note: The clusterlabs.org repository requires a package that is in the EPEL repository. Digium recommends installing the individual package manually, rather than setting up the EPEL repo. Replace Digium, Inc.
  • Page 53 [arch] with either i386 or x86_64, depending on your system’s architecture. # wget http://download.fedora.redhat.com/pub/epel/ 5/[arch]/libesmtp-1.0.4-5.el5.[arch].rpm # rpm -Uvh libesmtp-*.rpm # wget -O /etc/yum.repos.d/pacemaker.repo http:// clusterlabs.org/rpm/epel-5/clusterlabs.repo # yum install pacemaker corosync Note: Do not start the Pacemaker or Corosync service at this time. Digium, Inc. Page 53...
  • Page 54 Chapter 3: Configuration Digium Resource Agents Digium provides the source code for the resource agents for the R-Series unit and Asterisk, as well as sample configuration files for DRBD and Corosync. The sample configuration files will need to be modified, but should help you to get started.
  • Page 55 The e-mail address on the split-brain line is where e-mail will be sent  when DRBD detects a conflict that resulted in a split-brain (refer to DRBD project documentation for details on split-brain). The value Digium, Inc. Page 55...
  • Page 56 The IP address on the address lines must be changed to the real (non-  floating) IP addresses of each node. Execute the following command on both the primary and secondary node to create metadata on disk for DRBD. # drbdadm create-md asterisk Digium, Inc. Page 56...
  • Page 57 Depending on the Linux distribution, the iptables configuration file may be located at /etc/sysconfig/iptables or /etc/ network/interfaces. Then execute the following command on both the primary and secondary node to start the DRBD service. # /etc/init.d/drbd start Digium, Inc. Page 57...
  • Page 58 Note: This should be done only on the primary node. # drbdadm disconnect asterisk # drbdadm -- --clear-bitmap new-current-uuid asterisk # drbdadm -- --overwrite-data-of-peer primary asterisk # mkfs.ext3 -m0 [drbd_device] # drbdadm secondary asterisk # drbdadm detach asterisk # drbdadm up asterisk Digium, Inc. Page 58...
  • Page 59 # drbdadm primary asterisk # mkdir /mnt/asterisk # mount -t ext3 [drbd_device] /mnt/asterisk # cd /mnt/asterisk # touch test # ls Confirm that the file ‘test’ exists. # cd # umount /mnt/asterisk # drbdadm secondary asterisk Digium, Inc. Page 59...
  • Page 60 Confirm that the file ‘test’ exists. If the ‘test’ file exists, file replication to the secondary node was successful. The ‘test’ file is the same ‘test’ that was created on the primary node. # cd # umount /mnt/asterisk # drbdadm secondary asterisk Digium, Inc. Page 60...
  • Page 61 Asterisk is installed on the secondary node. Note: For the sake of convenience, DAHDI will be installed and configured in this section. DAHDI configuration files are not replicated between nodes. In addition, DAHDI is not handled by this failover scenario. Digium, Inc. Page 61...
  • Page 62 Moving /etc/asterisk/ to /mnt/asterisk/ etcasteriskdir/ mkdir: cannot create directory `/mnt/asterisk/ etcasteriskdir': File exists Moving /var/log/asterisk to /mnt/asterisk/logdir/ mkdir: cannot create directory `/mnt/asterisk/ logdir': File exists Moving /var/spool/asterisk/ to /mnt/asterisk/ spooldir/ mkdir: cannot create directory `/mnt/asterisk/ spooldir': File exists Digium, Inc. Page 62...
  • Page 63 /mnt/asterisk. This can be accomplished by executing the following command. # ls -alh /mnt/asterisk/ The output from this command should show that at least the following directories exist. etcasteriskdir  logdir  spooldir  Digium, Inc. Page 63...
  • Page 64 Red Hat based distributions and update-rc.d -f asterisk remove on Debian based distributions. If the DAHDI init script is not already installed (/etc/init.d/dahdi),  execute make config in the DAHDI source directory to install it. Execute drbdadm secondary asterisk.  Digium, Inc. Page 64...
  • Page 65 Expand the downloaded file, compile its contents, and install the libraries. Substitute the version of Libpri for the X.X and X.X.X.X in the command-lines below. # tar -zxvf libpri-X.X-current.tar.gz # cd libpri-X.X.X.X/ # make # make install Digium, Inc. Page 65...
  • Page 66 Then configure DAHDI according to the instructions provided in the product manual(s) for the installed Digium hardware. After configuring DAHDI, load the DAHDI kernel modules according to the instructions provided in the product manual(s) for the installed Digium hardware. Digium, Inc. Page 66...
  • Page 67 Note: Do not run “make config” for the Asterisk installation on the primary node. The automatic failover setup described in this chapter can start and stop Asterisk without the init script provided by “make config”. The init script may conflict with the automatic failover setup. Digium, Inc. Page 67...
  • Page 68 If your installation has failed, it may be because you are missing one or more of the build dependencies, the kernel headers, or the development tools. Contact your reseller where the unit was purchased, or call Digium Technical Support at 1.256.428.6161 for assistance. Please refer to Free Installation Support on page 104 for additional information on how to obtain assistance from Digium Technical Support.
  • Page 69 Output similar to the following is normal after executing the last command. mkdir: cannot create directory `/mnt/asterisk/ etcasteriskdir': File exists mkdir: cannot create directory `/mnt/asterisk/ logdir': File exists mkdir: cannot create directory `/mnt/asterisk/ spooldir': File exists Digium, Inc. Page 69...
  • Page 70 Substitute the version of Libpri for the X.X and X.X.X.X in the command-lines below. # tar -zxvf libpri-X.X-current.tar.gz # cd libpri-X.X.X.X/ # make # make install Download the latest DAHDI drivers with tools. DAHDI is available for download from: http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete # wget http://downloads.asterisk.org/pub/telephony/ dahdi-linux-complete/dahdi-linux-complete- current.tar.gz Digium, Inc. Page 70...
  • Page 71 Digium hardware. After configuring DAHDI, load the DAHDI kernel modules according to the instructions provided in the product manual(s) for the installed Digium hardware. Download the latest release version of Asterisk. Substitute the version of Asterisk for the X.X.X in the command below.
  • Page 72 If your installation has failed, it may be because you are missing one or more of the build dependencies, the kernel headers, or the development tools. Contact your reseller where the unit was purchased, or call Digium Technical Support at 1.256.428.6161 for assistance. Please refer to Free Installation Support on page 104 for additional information on how to obtain assistance from Digium Technical Support.
  • Page 73 Note: On Debian-based systems, set the value of START to yes (i.e. “START=yes”) in the /etc/default/corosync file on both the primary and secondary node in order for Corosync to start at boot time. On both the primary and secondary node, start the Corosync service. # /etc/init.d/corosync start Digium, Inc. Page 73...
  • Page 74 Note: Modifications to the Pacemaker configuration file should be made on only the primary node. Digium, Inc. Page 74...
  • Page 75 IP address or list of IP addresses to ping. Refer to Table 2 on page 76 for more details. Under “primitive rseries ocf:Digium:rseries”, the value for tty may  need to be changed. Refer to Table 2 on page 76 to determine this.

  • Page 76: Table 2: Resource Configuration

    “dmesg | grep cp210x”. deviceid Sanity check for ensuring we're acting on the correct unit. Not yet implemented. ocf:pacemaker:ping host_list List of IP addresses to ping. Recommended setting: IP address of gateway multiplier Score multiplier. Recommended setting: ocf:heartbeat:IPaddr2 Digium, Inc. Page 76...
  • Page 77 /dev/drbd0 on some Linux distributions. The value of this setting must be the same on all nodes. directory Directory on which to mount DRBD filesystem. Sample config uses /mnt/ asterisk/ fstype DRBD filesystem type. Sample config uses ext3 Digium, Inc. Page 77...
  • Page 78 WARNING: Asterisk_fs: default timeout 20s for stop is smaller than the advised 60 WARNING: GatewayStatus: default timeout 20s for start is smaller than the advised 60 WARNING: GatewayStatus: specified timeout 10 for monitor is smaller than the advised 60 Digium, Inc. Page 78...
  • Page 79 If propagation to the secondary node was successful, the Pacemaker configuration will be output to the console. Everything required for automatic failover, including DAHDI and Asterisk, should be loaded and running. Automatic failover configuration is now complete for the R-Series unit. Digium, Inc. Page 79...
  • Page 80 If SIP phones were registered, verify that they are now functioning  with the primary node. Verify that an inbound call over the PSTN lines connected to the R-  Series unit is successful. This confirms automatic failover to and from the primary and secondary node. Digium, Inc. Page 80...

  • Page 81: Chapter 4 Troubleshooting

    This chapter provides information regarding troubleshooting tools, frequently asked questions, and possible resolutions as identified by Digium Technical Support. Multiple resources are available to obtain more information about Asterisk and Digium products. Please visit both www.digium.com and www.asterisk.org for more information. Digium, Inc.

  • Page 82: Terminal Emulation Program Setup

    Table 3: Terminal Emulation Settings Option Value Bits Per Second 115,200 Data Bits Parity Bits None (N) Stop Bits Hardware Flow Control None Software Flow Control None Emulation VT102 or VT100 Digium, Inc. Page 82...

  • Page 83: Figure 5: Minicom Main Menu

    In order to begin configuring Minicom, execute the following command. # minicom -s -c on Note: If your terminal does not support color, omit the “-c on” arguments. You will be presented with the following menu. Figure 5: Minicom Main Menu Digium, Inc. Page 83...

  • Page 84: Figure 6: Minicom Serial Port Setup

    R-Series unit that you wish to configure. Then verify that the other settings are configured to match the values shown in the screenshot above. Press Esc to return to the main menu. Figure 7: Minicom Save as Default Digium, Inc. Page 84...

  • Page 85: Figure 8: Minicom Exit

    R-Series unit by executing the following command. # minicom -c on Note: If your terminal does not support color, omit the “-c on” arguments. In order to exit Minicom, the default command sequence requires you to press Ctrl + a, then x. Digium, Inc. Page 85...
  • Page 86 R-Series unit, that argument will need to be modified to reflect the correct serial device file. In order to exit Picocom, the default command sequence requires you to press Ctrl + a, then Ctrl + x. Digium, Inc. Page 86...

  • Page 87: Ascii Mode

    Please refer to Table 1 for other keyboard commands in ASCII Mode. Table 1: ASCII Mode Keyboard Command List Action Arrow Up Navigate Up Arrow Down Navigate Down Arrow Left Navigate Left Arrow Right Navigate Right Navigate Left Navigate Down Digium, Inc. Page 87...
  • Page 88 Chapter 4: Troubleshooting Table 1: ASCII Mode Keyboard Command List Action Navigate Up Navigate Right Enter Select Toggle operational state Apply Settings (save) Refresh (revert unsaved changes) Exit ASCII Mode menu Digium, Inc. Page 88...

  • Page 89: Figure 9: Ascii Mode Menu For Analog

    R-Series unit. The setting in the first configurable row of each column allows the same value to be applied across all ports for that column. Additional components of the ASCII Mode Menu are described below. Digium, Inc. Page 89...
  • Page 90 Primary USB Power - Indicates whether the Primary server is on.  Secondary USB power - Indicates whether the Secondary server is  Device ID - Indicates the device ID dial assignment for the R-Series  unit. Digium, Inc. Page 90...

  • Page 91: Figure 10: Ascii Mode Menu For Digital

    R-Series unit. The setting in the first configurable row of each column allows the same value to be applied across all ports for that column. Additional components of the ASCII Mode Menu are described below. Digium, Inc. Page 91...
  • Page 92 Primary heartbeat - Reserved for future use.  Secondary heartbeat - Reserved for future use.  Primary USB Power - Indicates whether the Primary server is on.  Secondary USB power - Indicates whether the Secondary server is  Digium, Inc. Page 92...
  • Page 93 Chapter 4: Troubleshooting Device ID - Indicates the device ID dial assignment for the R-Series  unit. Digium, Inc. Page 93...

  • Page 94: R-Series Command-Line Utility

    --get-product-number Read product number/SKU. --get-port-count Read number of telephony ports on unit --get-current-ctlport Read USB port # from which the request was made --get-master-ctlport Read # of the USB port that is currently in master mode Digium, Inc. Page 94...
  • Page 95 Request control of the unit. Required to modify USB port settings. See --get-master- ctlport --control-release Release control of the unit --get-port-status Read telephony port status --set-port-status Set telephony port status. Status can be 0/ 'primary' or 1/'secondary'. Digium, Inc. Page 95...
  • Page 96 # ./rctl -t /dev/rseries0 --get-firmware-version Firmware version: 2 Get serial number: # ./rctl -t /dev/rseries0 --get-serial-number Serial number: dm96132120003 Get port count: # ./rctl -t /dev/rseries0 --get-port-count Ports: 8 Get product name: # ./rctl -t /dev/rseries0 --get-product-number Product number: R850 Digium, Inc. Page 96...
  • Page 97 Firmware Update If an R-Series unit is behaving unexpectedly, its firmware may need to be updated. Please contact Digium Technical Support to obtain the latest R- Series firmware image. The firmware update must be performed using the Primary port on the R-Series unit. It is recommended to reference the ttyUSB device assignment of the R-Series unit when performing a firmware update.
  • Page 98 There is no need to power cycle the R-Series unit after a firmware update. You can verify that the firmware update was successful by executing the following command and examining the output. # ./rtest.sh info /dev/rseries[#] Digium, Inc. Page 98...

  • Page 99: Frequently Asked Questions

    Can I connect to a USB port on an R-Series unit from Microsoft Windows? Yes, this is possible. Keep in mind that this method is not supported by Digium. You will need to install the CP210x USB to UART Bridge Virtual COM Port (VCP) drivers which are freely available from http:// www.silabs.com/products/mcu/Pages/ USBtoUARTBridgeVCPDrivers.aspx.
  • Page 100 Secondary PBX. Amber - Heartbeats from the Secondary USB port have ceased, but  the heartbeat timeout has not been reached. Red - Power is present on the Secondary USB port and no heartbeat is  present. Digium, Inc. Page 100...
  • Page 101 A straight-through RJ45 cable is needed for connecting to the RJ45 ports on an R-Series digital unit. Which analog and digital protocols are supported by the R-Series units? The R-Series units will passthrough any protocol that they receive. They are not protocol dependent. Digium, Inc. Page 101...
  • Page 102 If you experience a slight echo from a line that is connected to an R-Series unit, please refer to the manual of the hardware product which is connected to the R-Series unit for troubleshooting information regarding echo. Digium, Inc. Page 102...
  • Page 103 There are several places to inquire for more information about Asterisk Digium products: 1. Digium Technical Support (+1.256.428.6161), or Toll Free in the U.S. (+1.877.344.4861), is available 7am-8pm Central Time (GMT -6), Monday - Friday. Please refer to Free Installation Support on page 104 for additional information on how to obtain assistance from Digium Technical Support.

  • Page 104: Free Installation Support

    Asterisk experts. Pricing on Subscription Services may be obtained from your nearest reseller or you may call Digium Sales for referral to your nearest reseller at +1.256.428.6000 or send an e-mail to sales@digium.com...

  • Page 105: Appendix A State Descriptions

    Input to Primary - All signals are routed through the Primary ports.  This is one of the two basic modes of operation and is available on all models. Note: This state is the default mode of operation and is available on all models. Digium, Inc. Page 105...

  • Page 106: Figure 2: Input To Secondary State

    Figure 2: Input to Secondary State Input to Secondary - All signals are routed through the Secondary  ports. Note: This state is one of the two basic modes of operation and is available on all models. Digium, Inc. Page 106...

  • Page 107: Figure 3: Loopback State

    Appendix A: State Descriptions Figure 3: Loopback State Loopback - Carrier signals are looped back (receive to transmit).  Note: This state is reserved for digital models of the R-Series unit, and is not supported in BRI mode. Digium, Inc. Page 107...

  • Page 108: Appendix B Pin Assignments

    All RJ11 ports labeled Input, Passthrough Input, Primary, and Secondary on the R-Series unit are 6-pin. The pin assignments are identified in Table B-1. Table B-1: RJ11 Port Connector Description Not used Not used Pin 1 Pin 6 Ring Not used Not used Digium, Inc. Page 108...
  • Page 109  Input 3RUW  3LQV   Input 3RUW  3LQV   ,QSXW 3RUW  Figure B-1: RJ21 Port Connector Pins 1-8 are ‘tip’ for Input ports 1-8. Pins 26-33 are ‘ring’ for Input ports 1-8. Digium, Inc. Page 109...

  • Page 110: Table B-2: Rj45 Port Connector

    All RJ45 ports labeled Input, Passthrough Input, Primary, and Secondary on the R-Series unit are 8-pin. The pin assignments are identified in Table B-1. Table B-2: RJ45 Port Connector T1 / E1 Unused Unused Unused Pin 1 Pin 8 Unused Unused Unused Unused Unused Digium, Inc. Page 110...

  • Page 111: Appendix C License Agreement

    (“Hardware”), entitlements granted pursuant to a Subscription Agreement, and related manuals (collectively the "Products"). Affiliates means an entity which is (a) directly or indirectly controlling Digium; or (b) which is directly or indirectly owned or controlled by Digium. By downloading or installing the Software or installing the Hardware, you agree to and accept the terms and conditions of this Agreement.
  • Page 112 “Software” shall include any upgrades, updates, bug fixes or modified versions (“Upgrades”) or backup copies of the Software supplied to you by Digium or an authorized reseller, provided you hold a valid license to the original Software and have paid any applicable fee for Upgrades.
  • Page 113 Failure to notify Digium that you do not agree to allow the collection of the listed information will be deemed consent to allow Digium to collect all listed information.
  • Page 114 HPEC for Asterisk 3. RESERVATION OF RIGHTS. Except for the limited license rights expressly granted in this Agreement, Digium reserves all rights in and to the Software and any modifications thereto, including title, ownership, trademark, copyright, patent, trade secret and any other rights and interests.
  • Page 115 Digium. 4. EMERGENCY CALLS. The Product Skype For Asterisk is excluded from this Section 4. Skype For Asterisk does not support any emergency...
  • Page 116 Products is in compliance with any applicable laws and regulations. 5. LIMITATION OF LIABILITY. To the maximum extent permitted by law, Digium is not liable under any contract, negligence, strict liability or other legal or equitable theory for Digium, Inc.
  • Page 117 Products, relating to warranty service, or arising out of any breach of this Agreement, even if Digium has been advised of the possibility of such damages. The sole remedy for a breach of the foregoing limited warranty is repair, replacement or refund of the defective or non-conforming Product(s).
  • Page 118 EXTENT OTHERWISE SPECIFICALLY AGREED IN WRITING BY SUCH PERSON OR ENTITY. TO THE MAXIMUM EXTENT ALLOWED BY APPLICABLE LAW, IN NO EVENT SHALL DIGIUM, ITS THIRD PARTY LICENSORS OR SUPPLIERS, NOR ITS DIRECTORS, OFFICERS, EMPLOYEES, AFFILLIATES OR LICENSORS BE LIABLE...
  • Page 119 7.2 You will not (except with regard to fair use or nominative use) without Digium written consent, use the name, trademarks, trade names or logos of Digium, or the name of any product or service of Digium, in any manner. If Digium grants you a right to use the aforementioned, you will do so only in strict compliance with Digium trademark policies.
  • Page 120 10. TRANSFER AND ASSIGNMENT. This Agreement and the rights and obligations under it are not assignable by you without the prior written approval of Digium, voluntarily or by operation of law. Any attempt by you to assign this Agreement without such approval shall be void. This Agreement shall inure to the benefit of the successors and assigns of Digium.
  • Page 121 Digium and you agree to attempt to resolve any dispute by direct communication between representatives of each party who are authorized to finally resolve the dispute.
  • Page 122 Appendix C: License Agreement Digium EUPLA 08132010 Digium, Inc. Page 122...

  • Page 123: Appendix D Glossary And Acronyms

    The dissipation of a transmitted signal’s power as it travels over a wire. bandwidth The capacity to carry traffic. Higher bandwidth indicates the ability to transfer more data in a given time period. Digium, Inc. Page 123...
  • Page 124 A generic term for an individual data stream. Service providers can use multiplexing techniques to transmit multiple channels over a common medium. Cat5 Category of Performance for wiring and cabling. Cat 5 cabling support applications up to 100 MHz. Digium, Inc. Page 124...
  • Page 125 Digium Asterisk Hardware Device Interface A telephony project dedicated to implementing a reasonable and affordable computer telephony platform into the world marketplace. In addition, the collective name for the Digium-provided drivers for Digium telephony interface products. Digium, Inc. Page 125...
  • Page 126 The European equivalent of North American T1, transmits data at 2.048 Mbps, up to 32 channels (DS0s). The European equivalent of North American T3, transmits data at 34.368 Mbps, up to 512 channels (DS0s). Equivalent to 16 E1 lines. Electromagnetic Interference Unwanted electrical noise. Digium, Inc. Page 126...
  • Page 127 G.729a A recommendation by the Telecommunication Standardization Sector (ITU-T) for an algorithm designed to transmit and receive audio at 8 kbps. H.323 A recommendation by the Telecommunication Standardization Sector (ITU-T) for multimedia communications over packet-based networks. Digium, Inc. Page 127...
  • Page 128 A point of contact between two systems, networks, or devices. International Standards Organization Interactive Voice Menu An interactive technology that allows a telephone system to detect voice and keypad input. Digium, Inc. Page 128...
  • Page 129 TDM separates signals by interleaving bits one after the other. multiplexer A device which transmits multiple signals over a single communications line or channel. See multiplexing. node A terminal in a computer network. Digium, Inc. Page 129...
  • Page 130 PSTN is now almost entirely digital, and now includes mobile as well as fixed telephones. Point-to-Point Protocol Type of communications link that connects a single device to another single device, such as a remote terminal to a host computer. Digium, Inc. Page 130...
  • Page 131 The creation of Regional Bell Operating Companies were a result of AT&T's telephone monopoly being broken up in 1983. Ringer Equivalence Number An arbitrary value which denotes the electrical load a telephone ringer has on a line. Digium, Inc. Page 131...
  • Page 132 Terminal Equipment A device that is established as a point of termination of a communications circuit or channel. Terminal equipment comprises all customer premises equipment (CPE). TE devices are connected to NT devices. Digium, Inc. Page 132...
  • Page 133 The wires are wrapped loosely around each other to minimize radio frequency interference or interference from other pairs in the same bundle. Volts VoIP Voice over Internet Protocol Technology used for transmitting voice traffic over a data network using the Internet Protocol. Digium, Inc. Page 133...

This manual is also suitable for:

R850

Table of Contents