Actions

Tmedia, Tsig, and Tdev Web Portal 2.7 Tutorial Guide

Revision as of 19:53, 17 December 2021 by Allyntree (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


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


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.


[edit]

New Hardware

Add telecom hardware Add TMS hardware Add 1+1 group

TDM network

(Step 1)
Allocate Physical Interfaces
System Clock

IP network

(Step 1)
IP Interfaces
Create an IP port range
[edit]

ISDN NFAS

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configure ISDN-PRI Signaling
(Step 3)
Modify NAP profile
(Step 4)
Configure Network Access Points (NAPs)

OR

ISDN Advanced Features

ISDN Overlap Sending



CASR2

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring a CAS R2 stack
(Step 3)
Modify NAP profile
(Step 4)
Configure Network Access Points (NAPs)

SIP

(Step 1)
Configure IP port range
(Step 2)
Configure SIP Signaling
(Step 3)
Configure Codecs and Tone Detection
(Step 4)
Modify NAP profile
(Step 5)
Configure Network Access Points (NAPs)

SIP Advanced Features

SIP-I SIP-T
SIP Spiral


NAT Traversal

SS7 ISUP

MTP2-MTP3-ISUP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the MTP2 Layer
(Step 3)
Configuring the MTP3 Layer
(Step 4)
Configuring the ISUP Layer
(Step 5)
Modify NAP profile
(Step 6)
Configure Network Access Points (NAPs)




M2PA-MTP3-ISUP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the M2PA Layer
(Step 3)
Configuring the MTP3 Layer
(Step 4)
Configuring the ISUP Layer
(Step 5)
Modify NAP profile
(Step 6)
Configure Network Access Points (NAPs)


M3UA-ISUP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the M3UA Layer
(Step 3)
Configuring the ISUP Layer
(Step 4)
Modify NAP profile
(Step 5)
Configure Network Access Points (NAPs)

SCCP-TCAP

MTP2-MTP3-SCCP-TCAP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the MTP2 Layer
(Step 3)
Configuring the MTP3 Layer
(Step 4)
Configuring the SCCP Layer
(Step 5)
Configuring the TCAP Layer (optional)




M2PA-MTP3-SCCP-TCAP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the M2PA Layer
(Step 3)
Configuring the MTP3 Layer
(Step 4)
Configuring the SCCP Layer
(Step 5)
Configuring the TCAP Layer (optional)


M3UA-SCCP-TCAP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the M3UA Layer
(Step 3)
Configuring the SCCP Layer
(Step 4)
Configuring the TCAP Layer (optional)

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

(Step 1)
Create Line Interfaces
(Step 2)
Create MTP2 links
(Step 3)
Create M2UA configuration


M3UA

(Step 1)
Create Line Interfaces
(Step 2)
Create MTP2 links
(Step 3)
Create MTP3 configuration
(Step 4)
Create M3UA configuration

IUA

(Step 1)
Create Line Interfaces
(Step 2)
Create IUA Configuration

H.248

(Step 1)
Allocate Physical Interfaces
(Step 2)
Create IP Port Ranges
(Step 3)
Modify NAP profile
(Step 4)
Configure Network Access Points (NAPs)
(Step 5)
Configure Media Gateway for H.248 mode
(Step 6)
Add a New Media Gateway Controller
(Step 7)
Associate NAPs Resources to H.248 Configuration



[edit]

Static route

Add routes

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


Audio Prompts


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
Add label routing functionality
Update definition/digitmap files
[edit]

Call trace

Call trace
[edit]

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