Revision as of 02:17, 18 January 2019

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 Tdev installation guides.)

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 Tdev installation guides.

This document also assumes familiarity with topics, such as ISDN signaling, SIP signaling, SS7, CAS 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:

System

Access and User Management

Database Backup

SNMP

Configuration

Statistics

Audit Logs

VoIP Bonding

Note: Web portal configuration for VoIP bonding is not yet available.

Hardware

New Hardware

TDM Network

IP Network

Protocol Stacks

ISDN NFAS

ISDN Advanced Features

CAS

SIP

SIP Advanced Features

SS7 ISUP

MTP2-MTP3-ISUP

M2PA-MTP3-ISUP

M3UA-ISUP

SS7 Advanced Features

SCCP-TCAP

MTP2-MTP3-SCCP-TCAP

M2PA-MTP3-SCCP-TCAP

M3UA-SCCP-TCAP

H.248 MEGACO

If the Tmedia is used to forward signalling messages to the SSW, you will require to configure M2UA, M3UA or IUA before configuring H.248.

If the Tmedia is used to connect media only, then you can go straight to H.248 Configuration

M2UA

M3UA

IUA

H.248

Fax

Routes

Static Route

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.

*Priority and Load-sharing Routing:This shows how to add Priority and Load sharing to any Routing scripts. This is a powerful script that allows to regroup Routes of the same kind, distribute load among them and prioritize one group versus another. Alternatively, you can do the same on NAPs. You will use two additional parameters in the routes: group and weight.
group serves as two purpose:

1. priority: a lower value will have higher priority
2. matching routes of the same group will load share according to the weight parameter

weight will load share calls among matching routes of the same group

For the procedure to add Priority and Load-sharing Routing to existing routing script, please refer to the below link:
*Adding_Load_Sharing_to_Routing_Script

Label Routing

This section assumes:

• The routing script is already implemented (you just need to add the label routing functionality)
• The routeset definition and digimap files are already created

RADIUS Authorization and Authentication

Troubleshooting

Call Trace

Test Call

Target Recording

VoIP Ethernet Capture

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).