Odin TeleSystems RTP Bridge User Manual

Odin TeleSystems Inc.
RTP Bridge
User’s Guide
Rev. 1.9
pyright © Odin TeleSystems Inc, 2010 www.odints.com
Co
December 20, 2010
RTP Bridge User’s Guide 2(36)
Copyright
© Copyright 2010, Odin TeleSystems, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of Odin TeleSystems Inc., 800 East Campbell Road, Suite 334, Richardson, Texas 75081, U. S. A.
Trademarks
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 DOCU­MENTATION, 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 CONSE­QUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY.
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 3(36)
Table of Contents
1 Introduction.........................................................................................................................................4
1.1 Description .........................................................................................................................................4
1.2 Features .............................................................................................................................................. 5
2 T1/E1 Channels Configuration..........................................................................................................6
3 The RTP Bridge Installation and Running.......................................................................................9
4 Command Line Arguments..............................................................................................................10
5 The RTP Bridge Commands............................................................................................................11
5.1 Running RTP Bridge Commands from a Configuration File........................................................... 18
5.2 Running RTP Bridge Commands from a Command Line................................................................ 18
5.3 Running RTP Bridge Commands via Telnet Interface..................................................................... 18
6 Transcoding Operation.....................................................................................................................19
7 Multi-conferences support................................................................................................................22
8 Testing Verification Procedure........................................................................................................25
8.1 Testing Scheme 1 .............................................................................................................................25
8.2 Testing Scheme 2 .............................................................................................................................26
9 The RTP Bridge License...................................................................................................................29
10 References .......................................................................................................................................30
11 Product Versions History...............................................................................................................31
12 Document History...........................................................................................................................34
13 Glossary...........................................................................................................................................36
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 4(36)
1 Introduction
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.
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 5(36)
1.2 Features
Simultaneous bi-directional data transfer between E1/T1 spans and various RTP
remote nodes.
Uses a Telnet interface for E1/T1 timeslot–to-RTP endpoints mapping
configuration.
Transcoding of voice data between any of G.711 (a-law, u-law) / G.711.1 /
G.711.2, G.723, G.726, G.729, GSM-FR, G.722 / G.722.1 / G.722.2 (AMR-WB) codecs.
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
Description (version 1.5 and later), chapter 8.
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 6(36)
2 T1/E1 Channels Configuration
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.
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 7(36)
Parameter Name
Termination OTX_T1E1_TERM_120_OHM,
OTX_T1E1_TERM_100_OHM, OTX_T1E1_TERM_75_OHM, OTX_T1E1_TERM_75_OHM_BALANCED, OTX_T1E1_TERM_300_OHM, OTX_T1E1_TERM_HIGHZ
RxThreshold
Positive integer, defaults to
OTX_HWLAYER_DEFAULT_RX_THRESHOLD: 500
SetMonitorMode FrontEndAmplifier
BoardType BoardNo
T1FrameFormat OTX_T1_FF_F12, OTX_T1_FF_F4,
T1LineCode E1FrameFormat OTX_E1_FF_DOUBLE_FRAME,
Boolean value P_BOOL
Boolean value P_BOOL: OFF
A2, A2P, A4, A8, A4M, A8M, AA
The index of board, defaults to 0
OTX_T1_FF_ESF, OTX_T1_FF_F72, OTX_T1_FF_F12_J1, OTX_T1_FF_F4_J1, OTX_T1_FF_ESF_J1, OTX_T1_FF_F72_J1, OTX_T1_FF_UNFRAMED OTX_T1_LC_AMI, OTX_T1_LC_B8ZS
OTX_E1_FF_CRC4_MULTIFRAME, OTX_E1_FF_CRC4_MULTIFRAME_G706,
OTX_E1_FF_UNFRAMED E1LineCode T1E1LiMode
OTX_E1_LC_AMI, OTX_E1_LC_HDB3
T1, E1
Possible Values
2
3
: NO
4
Table 1 The full list of OtxHwLayer configuration file parameters
Note: The default values are marked bold.
2
Line termination mode can be one of the following:
OTX_T1E1_TERM_120_OHM – Span is terminated for 120 ohm twisted pair (balanced
differential signal)
OTX_T1E1_TERM_100_OHM – Span is terminated for 100 ohm twisted pair (balanced
differential signal)
OTX_T1E1_TERM_75_OHM Span is terminated for 75 ohm coax (unbalanced unipolar
signal)
OTX_T1E1_TERM_HIGHZ – Span is not terminated (Balanced, High impedance, for
monitoring scenarios when short (<2 meters) monitor taps are used)
OTX_T1E1_TERM_75_OHM_BALANCED – Span is terminated for 75 ohm balanced
differential signal (for special monitoring conditions)
OTX_T1E1_TERM_300_OHM – Span is terminated for 300 ohm twisted pair (balanced
differential signal)
3
Possible values for P_BOOL: TRUE, T, 1, YES, ON, FALSE, F, 0, NO, OFF.
4
Explanation of abbreviations for the BoardType parameter:
A2 - OTX_DEVICE_DMP_ALVIS_2_CSI, A2P - OTX_DEVICE_DMP_ALVIS_2_PBX, A4 - OTX_DEVICE_DMP_ALVIS_4_CSI, A8 - OTX_DEVICE_DMP_ALVIS_8_CSI, A4M - OTX_DEVICE_DMP_ALVIS_4M_CSI, A8M - OTX_DEVICE_DMP_ALVIS_8M_CSI, AA
- OTX_DEVICE_DMP_ALVIS.
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 8(36)
Example (Alvis-4-CSI):
--------------------------------------------- OtxHwLayer.conf --------------------------------------
E1FrameFormat OTX_E1_FF_CRC4_MULTIFRAME
# Line termination mode Termination OTX_T1E1_TERM_100_OHM
# Receive threshold (in mV) RxThreshold 500
# Set Monitor (-20dB) mode (YES/NO) SetMonitorMode NO
# Turning front end Amplifier ON/OFF FrontEndAmplifier OFF
T1E1LiMode E1
# Board type BoardType A4
# Board No BoardNo 0
-------------------------------------------------- EOF --------------------------------------------------
Doc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9 Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 9(36)
3 The RTP Bridge Installation and Running
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.
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 10(36)
4 Command Line Arguments
The RTP Bridge accepts several command line arguments:
--help or -h
Displays help with command line arguments available.
--daemon or -d
Runs the RTP Bridge in a daemon mode.
--pid <file_name> or -p <file_name>
Changes the name of pid-file (where process identifier is stored). By default it is ‘/var/run/rtpbridge.pid’.
--port or -P
Changes port for Telnet interface. By default it is 10000.
--burst or -b
Uses Burst events instead of Core-to-Core mechanism.
--packetsize <msec> or -s <msec>
Sets the default size of RTP packets (in milliseconds) in TDM->RTP Mode.
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
Copyright © Odin TeleSystems Inc., 2010
RTP Bridge User’s Guide 11(36)
5 The RTP Bridge Commands
There are several commands available to control / get status of connections between the RTP and TDM media streams (or mixed):
CONNECT MCONNECT LIST DISCONNECT DSP LOAD DSP LOAD EX BURST STATS CONSTAT JITTER BLOCKS READCONFIG SHOW LICENSE PACKET SIZE BENCH TRACES EVENTS CONSOLE CORE
Please see the detailed commands description below.
CONNECT <src_type>:<src_stream>:<src_idx>:[opt] <dst_type>:<dst_stream>:<dst_idx>:[opt]
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.
The fields are:
src_type, dst_type:
RTP (RTP connection), TDM (TDM cross-connect), TDMOE (Pseudowire cross­connect)
src_stream, dst_stream:
For RTP: IP-address, for TDM: Span number
src_idx, dst_idx:
For RTP: Port number (local/remote), for TDM: Timeslot
opt:
Usually src_codec, dst_codec are voice codec used for the specified stream end, e.g.
alaw (or g711a), ulaw (or g711u), g729, g723, g726, etc.
Note:
If src_codec and dst_codec parameters are not specified, they take the default value.
Currently the default codec is alaw.
For the incoming RTP data src_codec can be overridden by the payload type of RTP
oc. No. 1412-1-SAA-1020-1 www.odints.com Rev. 1.9
D
JITTER BLOCKS
Copyright © Odin TeleSystems Inc., 2010
Loading...
+ 25 hidden pages