From TBwiki

(Difference between revisions)

Revision as of 13:02, 20 July 2012

Introduction

This guide is designed to provide users with a scenario-based approach to installing Tmedia and Tdev systems, using the Web Portal configuration tool. This means that users must first go through the steps that are general to all installations, and subsequently follow the instructions that are specific to their particular application scenario (this corresponds to the type of service, and hardware system being set up).

Prerequisites

This document assumes that the Tmedia or Tdev devices are installed as described in their Quick Reference Guides, and in the case of the Tmedia system communication has been established with the control network.

(Note: Tmedia devices are shipped with the Tmedia Web Portal pre-installed, while Tdev devices require that Toolpack be installed as described in the TMP6400 Installation Guide.)

Furthermore, in the case of a Tdev device and the initial configuration of the Toolpack application server, the following will have been provided:

The Tdev device to which the Web Portal will first connect.
The Tdev device will have been pre-configured with its physical TDM interface.
The serial number of the Tdev device will have been entered into the configuration file.
The application software for the Tdev device will have been pre-installed on the Toolpack application server, as described in the TMP6400 Installation Guide.

This document also assumes familiarity with topics, such as ISDN signaling, SIP signaling, SS7, CAS R2 signaling, and SIGTRAN signaling.

Key Concepts

System: A system is defined as the complete solution that is designed for a network. If a system solution is comprised of 4 TMP6400’s and a TMS1600, then the combination of these TelcoBridges devices is termed a system.
Hardware: Each TelcoBridges devices, whether it is a TMP6400, TMG3200, or TMS1600 is referred to as a hardware device or hardware adapter.
Line Interface: The physical TDM module installed on the TelcoBridges device is referred to as a line interface.

General Web Portal Applications

IMPORTANT! The Topics covered in the following table are common to all TMedia installations. Therefore, this section should be consulted before moving on to any other.

Topics covered here:

The basic knowledge needed to properly navigate through the Web Portal (A).
The fundamentals of user account management and permission masks (B).
The initial steps required for first starting the Web Portal, and verifying that it is functioning properly (C).
The process involved in backing up your database for the first time (D).
The process involved in first configuring your IP interfaces (E).

(Topic A) Web Portal Basics	(Topic B) Log-on and User Access Levels	(Topic C) Application Start-up and Verification	(Topic D) Database Backup
Navigating the Web Portal

ISDN-SIP Gateway Configuration

The following tables contain a typical configuration scenario for an ISDN to SIP gateway. This type of installation allows for the transfer of information from traditional ISDN signaling to SIP protocol for VoIP applications. Please follow each step one after another as these are listed in logical order.

The steps are as follows:

1) Log On and Create a New Configuration
2) Allocate Physical Interfaces
3) Configure ISDN-PRI Signaling
4) Configure Clocking Source
5) Configure SIP Signaling
6) Configure Codecs and Tone Detection
7) Configure Network Access Points (NAPs)
8) Create Call Routing Rules

IMPORTANT! After completing the setup process, remember to activate the configuration, as outlined in the General Web Portal Applications section.

(Step 1) Log On and Create a New Configuration	(Step 2) Allocate Physical Interfaces	(Step 3) Configure ISDN-PRI Signaling	(Step 4) Configure Clocking Source

(Step 5) Configure SIP Signaling	(Step 6) Configure Codecs and Tone Detection	(Step 7) Configure Network Access Points (NAPs)	(Step 8) Create Call Routing Rules

Configuring SS7

The following table contains information on configuring the SS7 signaling protocol. The various control layers of the SS7 protocol are listed individually in each column. These layers are:

MTP2 layer (Step 1)
MTP3 layer (Step 2)
ISUP layer (Step 3)
SCCP layer (Step 4)
TCAP layer (Step 5)

Follow the topics listed in each column from left to right in order to configure an SS7 protocol stack.

(Step 1) Configuring the MTP2 Layer	(Step 2) Configuring the MTP3 Layer	(Step 3) Configuring the ISUP Layer	(Step 4) Configuring the SCCP Layer	(Step 5) Configuring the TCAP Layer

SIGTRAN Application Scenarios

Toolpack version 2.6 enables you to configure SIGTRAN and thereby extend SS7 signalling functionality to the IP network. Toolpack enables you to configure a number of SIGTRAN applications based upon your requirements. These applications are listed below as follows:

M2PA system. See column (A) below. In this configuration the SS7 MTP2 layer is replaced by the SIGTRAN M2PA layer which extends MTP2 signalling functionality into the IP network. This application is typically used between a Signalling Gateway and an IP Signalling Point, or between two IP Signalling Points.

M2UA system. See columns (B) and (C) below. An M2UA system on a Signalling Gateway Controller interfaces with an M2UA system on a Media Gateway Controller. In this configuration, M2UA bridges the SS7 MTP2 layer of a Signalling Gateway, across an IP network, with the SS7 MTP3 layer of a Media Gateway Controller.

IUA system. See column (D) below. An IUA system on a Signalling Gateway Controller interfaces with an IUA system on a Media Gateway Controller. In this configuration, IUA bridges the SS7 MTP2 layer of a Signalling Gateway, across an IP network, with the SS7 MTP3 layer of a Media Gateway Controller.

M3UA system on two IP signalling points. See column (E) below. In this configuration the SS7 MTP2 and MTP3 layers are replaced entirely by the SIGTRAN M3UA layer. This application is typically used between two IP Signalling Points.

M3UA system. See columns (F) and (G) below. An M3UA system on a Signalling Gateway Process interfaces with an M3UA system on an Application Server Process. In this configuration, the MTP3 links are extended across the IP network.

A SIGTRAN scenario walkthrough is provided in the table columns below, to illustrate the order that must be followed when configuring SIGTRAN.

(Scenario A) Configuring an M2PA System	(Scenario B) Configuring an M2UA System on a Signalling Gateway	(Scenario C) Configuring an M2UA System on a Media Gateway Controller	(Scenario D) Configuring an IUA System on a Signalling Gateway	(Scenario E) Configuring an M3UA System on IP Signalling Points	(Scenario F) Configuring an M3UA System on a Signalling Gateway	(Scenario G) Configuring an M3UA System on an Application Server

Configuring CAS R2

Toolpack v2.6 allows you to configure CAS R2 signaling stacks. The following table lists the basic steps that must be followed in order to configure CAS R2.

Configuring a CAS R2 stack

Configuring H.248

The following table contains steps for configuring an H.248 media gateway control protocol

(Step 1) Add a Hardware Adapter	(Step 2) Allocate Physical Interfaces	(Step 3) Create IP Port Ranges	(Step 4) Configure Network Access Points (NAPs)

(Step 5) Configure the Media Gateway for H.248 mode	(Step 6) Create an H.248 Configuration	(Step 7) Add a New Media Gateway Controller	(Step 8) Associate NAPs with the H.248 Configuration

(Step 9) Select Timeslots for TDM Terminations

Configuring an H.323 to SIP Converter

The following table contains steps for configuring NAPs that wil allow an interface between the web portal and a YATE H.323 to SIP signal converter:

Configuring an H.323 to SIP Signal Converter

Configuring SNMP

To use the Simple Network Management Protocol (SNMP)on your machine, you must first configure the tbSnmpAgent.
The tbSnmpAgent is a software application that interfaces between the TMedia system hardware and the NetSnmp implementation of the SNMP that is supported by TelcoBridges. By default, tbSnmpAgent is disabled. In order to use the SNMP protocol to monitor and manage your hardware, complete the following tasks:

Activate the tbSnmpAgent
Configure the tbSnmpAgent as required

These tasks can be completed using the Web Portal:

Once these tasks are completed, your TMedia platform is ready to expose system variables for polling with the Simple Network management Protocol (SNMP).

Configuring RADIUS

Toolpack v2.6 can send accounting requests containing CDR data to a remote RADIUS server. In order to do so, refer to the Configuring RADIUS page.

Configuring Fax

FAX passthrough	FAX T.38

Configuring Routing script

TelcoBridges provides a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps. Please select one of the following examples according to your needs. You may modify it when necessary.

*Flexible NOA: Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.

*Prefix NOA: Remapp Calling/Called NOA according to the prefix of the calling/called number, manipulate calling/called number. For calling number, if it is a privacy call, use the number in P-Asserted-Identity line or Remote-Party-ID line as the calling number to remap the NOA and do the manipulation.

Flexible NOA	Prefix NOA
Create new routing script Import customized routing script Add NOA columns in routes Enable routing script Activate configuration	Create new routing script Import customized routing script Enable routing script Activate configuration

Status Menus

The Web Portal configuration tool will guide you through a number of status menus, each of which indicate the current state of a certain hardware service (assuming said service has been configured). The following table contains the general conventions of the Web Portal's display (A), as well as a variety of specific status menus (B).

(A) Menus Overview	(B) Individual Menu Descriptions

@@ Line 294: / Line 294: @@
 | valign="top" |
 | valign="top" |
+|}
+=Configuring Routing script=
+TelcoBridges provides a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps. Please select one of the following examples according to your needs. You may modify it when necessary.
+'''*Flexible NOA:''' Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.
+'''*Prefix NOA:''' Remapp Calling/Called NOA according to the prefix of the calling/called number, manipulate calling/called number. For calling number, if it is a privacy call, use the number in P-Asserted-Identity line or Remote-Party-ID line as the calling number to remap the NOA and do the manipulation.
+{| cellpadding="5" border="1" class="wikitable"
+|-
+! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Flexible NOA
+! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Prefix NOA
+|-
+| valign="top" |
+*[[Create_New_Routing_Script_A|Create new routing script]]
+*[[Import_Customized_Routing_Script_A|Import customized routing script]]
+*[[Add_NOA_Columns_in_Routes_A|Add NOA columns in routes]]
+*[[Enable_Routing_Script_A|Enable routing script]]
+*[[Activate_Configuration_A|Activate configuration]]
+| valign="top" |
+*[[Create_New_Routing_Script_A|Create new routing script]]
+*[[Import_Customized_Routing_Script_A|Import customized routing script]]
+*[[Enable_Routing_Script_A|Enable routing script]]
+*[[Activate_Configuration_A|Activate configuration]]
 |}

Web Portal Tutorial Guide v2.6