Odin TeleSystems, OTX, RTP Bridge, RTP Streamer, Alvis-CSI, Alvis-PBX, Alvis-PCIe, Alvis-ASM, the Odin
Logo, are trademarks of Odin TeleSystems Inc., which may be registered in some jurisdictions. Other trademarks
are the property of their respective companies.
Changes
The material in this document is for information only and is subject to change without notice. While reasonable
efforts have been made in the preparation of this document to assure its accuracy, Odin TeleSystems Inc., assumes
no liability resulting from errors or omissions in this document, or from the use of the information contained herein.
Odin TeleSystems Inc. reserves the right to make changes in the product design without reservation and notification
to its users.
Warranties
THE PRODUCT AND ITS DOCUMENTATION ARE PROVIDED “AS IS” AND WITHOUT WARRANTY OF
ANY KIND. ODIN TELESYSTEMS EXPRESSLY DISCLAIMS ALL THE WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR PARTICULAR PURPOSE. ODIN TELESYSTEMS DOES NOT WARRANT THAT THE
FUNCTIONALITY OF THE PRODUCT WILL MEET ANY REQUIREMENTS, OR THAT THE OPERATIONS
OF THE PRODUCT WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS WILL BE
CORRECTED. FURTHERMORE, ODIN TELESYSTEMS DOES NOT WARRANT OR MAKE ANY
REPRESENTATIONS REGARDING THE USE OF THE PRODUCT OR ITS DOCUMENTATION IN TERMS
OF THEIR CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN
INFORMATION OR ADVISE GIVEN BY ODIN TELESYSTEMS OR ODIN TELESYSTEMS’ AUTHORIZED
REPRESENTATIVE SHALL CREATE A WARRANTY. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY.
UNDER NO CIRCUMSTANCE SHALL ODIN TELESYSTEMS INC., ITS OFFICERS, EMPLOYEES, OR
AGENTS BE LIABLE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES (INCLUDING
DAMAGES FOR LOSS OF BUSINESS, PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS
INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT AND ITS DOCUMENTATION, EVEN IF ODIN TELESYSTEMS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. IN NO EVENT WILL ODIN TELESYSTEMS’ LIABILITY FOR ANY REASON EXCEED THE
ACTUAL PRICE PAID FOR THE PRODUCT AND ITS DOCUMENTATION. SOME JURISDICTIONS DO
NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL AND CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY.
The RTP Bridge is a universal streaming media gateway application running on the top of
TDM (E1/T1) and RTP media streams designed for the industry's award-winning Odin
Telecom frameworX (OTX) hardware. This document provides detailed information
about the RTP Bridge product.
1.1 Description
The RTP Bridge solution provides data transfer between various E1/T1 timeslots and
RTP end-points in simplex or duplex directions. Voice data could be additionally
transcoded between each of G.711 (a-law, u-law) / G.711.1 / G.711.2 E1/T1 timeslots
and RTP end-points (G.711, G.723, G.726, G.729, GSM-FR, G.722 / G.722.1 / G.722.2
(AMR-WB)) in any order. (See Figure 1)
It is also possible to use the
case the RTP Bridge connects data from one IP-Address:Port to another IP-Address:Port,
with transcoding options.
RTP Bridge product without E1/T1 TDM streams. In that
Figure 1 The universal streaming media gateway on the OTX Hardware
The RTP Bridge is targeted to use DaVinci™-enabled products of Odin TeleSystems like
Alvis-CSI, Alvis-PBX, Alvis-PCIe, Alvis-ASM. It runs on the embedded TI DM64XX
SoC processors.
The RTP Bridge uses the OtxRtp Library on the DM6443 SoC ARM core. Also there are
Win32/64 and Linux versions of the OtxRtp Library available.
The RTP Bridge application could be remotely controlled in real-time by the Telnet
interface; it is possible to make connect / disconnect, status monitoring, etc. Connections
could be also taken from the configuration file at startup.
Multi-party conferences support. (According to RFC 3550/3551 each RTP
session (listened port) could be connected to some other remote systems. I.e. we
could stream one E1/T1 timeslot to different remote locations at the same time.)
N64 Streaming support (The RTP Bridge allows to send E1 super channels over
UDP to PC, and backwards, to receive UDP packets with E1 data and to send
them to E1 as super channels).
Integrated SNMP monitoring
LED Alarms indication.
Possibility to send OTX Events over UDP.
DSP C64+ powered built-in configurable jitter buffer of incoming RTP packets.
TDM Passive monitoring provides the ability to stream E1/T1 spans to the RTP
end-points in a non-intrusive mode.
Optimized data processing using multi-core DaVinci™ architecture with
offloading of all real-time operations on the powerful C64+ DSP core.
Compatible with the OTX DaVinci driver.
Compatible with the OTX XDM SDK API.
Multi-session mode; the user can create any numbers of listening ports on one
system.
Real-time statistics for RTP sessions is available.
Customizable RTP streams parameters: packetizing time, packet size, adjustable
codec parameters, etc.)
Optimized RTP monitoring mode allows to listen RTP streams coming with
different IP-addresses and ports.
Supports IETF RFC 3550, RFC 3551 RTP/RTCP Transport protocols.
A variety of optional decoding / encoding Plugins are available (ATM/AAL5,
HDLC/SS7, TRAU, H.324M).
1
using the OtxSNMP Library (SNMP Layer1) and
1
For more detailed information on SNMP monitoring settings please refer to Alvis-CSI Technical
The T1/E1 channels configuration before running the RTP Bridge is optional. It is set in
“OtxHwLayer.conf” file in a case of RTP Bridge uses T1/E1 streams.
The structure of the OtxHwLayer configuration file should be composed from the
parameters provided by line. Each parameter is initialized with the name and the value
represented on a single line through any number of spaces.
Example: T1E1LiMode E1
The configuration file can also contain comments. The comment line begins with ‘#’
character and ends with the end of line. If you need to allocate a few lines for comment,
you should put a ‘#’ character at the beginning of each line.
Example: # Line termination mode
Most of the parameters are set by default; all you need is to define a number of key
parameters: the type of board (BoardType), the index of board (BoardNo), etc.
Please see the full list of configuration file parameters in Table 1.
It is recommended to install the RTP Bridge on Alvis-4-CSI board with firmware
package version 2.11.12 or later. For more information of firmware upgrade, please refer
to Alvis-CSI Firmware Upgrade HOW TO
1.1).
To install the OTX RTP Bridge from rpm repository please follow these steps:
1. Update the rpm repository packets list:
apt-get update
2. Install RTP Bridge package with a command:
apt-get install rtpbridge
(Odin document #1712-1-HCA-1020-1.0-
3. Reboot the board (Alvis-CSI):
sync & reboot
The RTP Bridge will automatically start at system start-up (daemon mode). You can
connect it via Telnet. If you want to start with CLI, then issue the commands:
service rtpbridge stop
/opt/rtpbridge/rtpbridge
If you will get a “No license found” message please follow the instructions in Chapter 9 The RTP Bridge License.
This command establish a simplex cross-connect between an incoming and outgoing
stream. To do a duplex connection, one more connection needs to be done separately.