Web Portal Tutorial Guide v2.7

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(Added M3UA steps for SDP)
(M3UA-ISUP)
 
(29 intermediate revisions by 6 users not shown)
Line 73: Line 73:
 
*[[Toolpack:Uploading a Database Backup B|Uploading a Database Backup]]
 
*[[Toolpack:Uploading a Database Backup B|Uploading a Database Backup]]
 
*[[Toolpack:Restoring a Database Backup B|Restoring a Database Backup]]
 
*[[Toolpack:Restoring a Database Backup B|Restoring a Database Backup]]
 +
|}
 +
 +
==SNMP==
 +
{| cellpadding="5" border="1" class="wikitable"
 +
|-
 +
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Enable SNMP
 +
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | SNMP Get/Get Next
 +
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | SNMP Traps
 +
|-
 +
| valign="top" |
 +
* [[Activating_tbSnmpAgent|Enabling SNMP]]
 +
| valign="top" |
 +
* [[Toolpack:Configuring_tbSnmpAgent_A|Configuring SNMP Agent]]
 +
* [[Toolpack:Creating_an_SNMPv1/SNMPv2_Community_A|Creating SNMP v1, SNMP v2 communities]]
 +
or
 +
* [[Toolpack:Creating_an_SNMPv3_User_A|Creating an SNMP v3 user]]
 +
| valign="top" |
 +
* [[Toolpack:Creating_an_SNMP_Trap_Destination_A|Configuring SNMP traps destination]]
 
|}
 
|}
  
Line 96: Line 114:
 
*[[Toolpack:Uploading_a_Release_A|Uploading a software release]]
 
*[[Toolpack:Uploading_a_Release_A|Uploading a software release]]
 
*[[Toolpack:Activating_a_Release_A|Activating a software release]]
 
*[[Toolpack:Activating_a_Release_A|Activating a software release]]
 +
|}
 +
</div>
 +
 +
<div id="Upload license">
 +
==Upload license==
 +
{| cellpadding="5" border="1" class="wikitable"
 +
|-
 +
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Installing a Package
 +
|-
 +
| valign="top" |
 +
*[[Toolpack:Retreiving_a_License_A|Retrieving a license]]
 +
*[[Toolpack:Uploading_a_License_A|Uploading a license]]
 
|}
 
|}
 
</div>
 
</div>
Line 434: Line 464:
 
{| cellpadding="5" border="1" class="wikitable"
 
{| 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;" | (Step 1) <br>Allocate Physical Interfaces
+
! 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;" | (Step 1a) <br>Configuring the M3UA Layer - IPSP
! 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;" | (Step 2a) <br>Configuring the M3UA Layer-IPSP
+
! 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;" | (Step 1b) <br>Configuring the M3UA Layer - ASP
! 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:  
+
! 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;" | (Step 1c) <br>Configuring the M3UA Layer - SGP
continuous;" | (Step 2b) <br>Configuring the M3UA Layer-SDP
+
! 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;" | (Step 2) <br>Configuring the ISUP Layer
! 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:  
+
! 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;" | (Step 3) <br>Modify NAP profile
continuous;" | (Step 3) <br>Configuring the ISUP Layer
+
! 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;" | (Step 4) <br>Configure Network Access Points (NAPs)
! 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;" | (Step 4) <br>Modify NAP profile
+
! 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;" | (Step 5) <br>Configure Network Access Points (NAPs)
+
  
 
|-
 
|-
 
| valign="top" |
 
*[[Toolpack:Creating_a_Line_Interface B|Create a new line interface]]
 
*[[Toolpack:Creating_a_Line_Service B|Create a new line service]]
 
  
 
| valign="top" |  
 
| valign="top" |  
Line 455: Line 479:
 
**[[Toolpack:Creating an M3UA SAP A|Create an M3UA SAP]]  
 
**[[Toolpack:Creating an M3UA SAP A|Create an M3UA SAP]]  
 
**[[Toolpack:Creating an M3UA Network A|Create an M3UA Network]]  
 
**[[Toolpack:Creating an M3UA Network A|Create an M3UA Network]]  
**[[Toolpack:Creating an M3UA User Part A|Create an M3UA User Part]]  
+
**[[Toolpack:Creating_an_M3UA_User_Part_(IPSP)_A|Create an M3UA User Part]]  
 
**[[Toolpack:Creating an M3UA Peer Signalling Process (IPSP) A|Create an M3UA Peer Signalling Process]]  
 
**[[Toolpack:Creating an M3UA Peer Signalling Process (IPSP) A|Create an M3UA Peer Signalling Process]]  
 
**[[Toolpack:Creating an M3UA Peer Server A|Create an M3UA Peer Server]]  
 
**[[Toolpack:Creating an M3UA Peer Server A|Create an M3UA Peer Server]]  
Line 463: Line 487:
 
*[[Toolpack:Creating the SCTP Configuration B|Edit the SCTP Configuration]]  
 
*[[Toolpack:Creating the SCTP Configuration B|Edit the SCTP Configuration]]  
 
*[[Toolpack:Creating SS7 Point Codes A|Create SS7 Point Codes]]  
 
*[[Toolpack:Creating SS7 Point Codes A|Create SS7 Point Codes]]  
*[[Toolpack:Creating an M3UA Configuration (IPSP) B|Create an M3UA Configuration]]  
+
*[[Toolpack:Creating an M3UA Configuration ASP B|Create an M3UA Configuration]]  
 
**[[Toolpack:Creating an M3UA SAP A|Create an M3UA SAP]]  
 
**[[Toolpack:Creating an M3UA SAP A|Create an M3UA SAP]]  
 
**[[Toolpack:Creating an M3UA Network A|Create an M3UA Network]]  
 
**[[Toolpack:Creating an M3UA Network A|Create an M3UA Network]]  
**[[Toolpack:Creating an M3UA User Part A|Create an M3UA User Part]]  
+
**[[Toolpack:Creating_an_M3UA_User_Part_(IPSP)_A|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process (IPSP) A|Create an M3UA Peer Signalling Process]]  
+
**[[Toolpack:Creating an M3UA Peer Application Server Process (ASP) A|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server A|Create an M3UA Peer Server]]  
+
**[[Toolpack:Creating an M3UA Peer Server (ASP) A|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route A|Create an M3UA Route]
+
**[[Toolpack:Creating an M3UA Route (ASP) A|Create an M3UA Route]]
 +
 
 +
| valign="top" |
 +
*[[Toolpack:Creating the SCTP Configuration B|Edit the SCTP Configuration]]
 +
*[[Toolpack:Creating SS7 Point Codes A|Create SS7 Point Codes]]
 +
*[[Toolpack:Creating an M3UA Configuration SGP B|Create an M3UA Configuration]]
 +
**[[Toolpack:Creating an M3UA SAP A|Create an M3UA SAP]]
 +
**[[Toolpack:Creating an M3UA Network A|Create an M3UA Network]]
 +
**[[Toolpack:Creating an M3UA User Part (SGP) A|Create an M3UA User Part]]  
 +
**[[Toolpack:Creating an M3UA Peer Signalling Process (SGP) A|Create an M3UA Peer Signalling Process]]  
 +
**[[Toolpack:Creating an M3UA Peer Server (SGP) A|Create an M3UA Peer Server]]  
 +
**[[Toolpack:Creating an M3UA Route (SGP) A|Create an M3UA Route]]
  
 
| valign="top" |  
 
| valign="top" |  
Line 607: Line 642:
 
{| cellpadding="5" border="1" class="wikitable"
 
{| 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;" | (Step 1) <br>Allocate Physical Interfaces
+
! 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;" | (Step 1) <br>Configuring the M3UA Layer  
! 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;" | (Step 2) <br>Configuring the M3UA Layer  
+
! 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;" | (Step 2) <br>Configuring the SCCP Layer
! 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;" | (Step 3) <br>Configuring the SCCP Layer
+
! 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;" | (Step 3) <br>Configuring the TCAP Layer (optional)
! 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;" | (Step 4) <br>Configuring the TCAP Layer (optional)
+
  
 
|-
 
|-
 
| valign="top" |
 
*[[Toolpack:Creating_a_Line_Interface B|Create a new line interface]]
 
*[[Toolpack:Creating_a_Line_Service B|Create a new line service]]
 
  
 
| valign="top" |  
 
| valign="top" |  
Line 747: Line 777:
 
{| cellpadding="5" border="1" class="wikitable"
 
{| 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;" | (Step 1) <br>Allocate Physical Interfaces
+
! 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;" | (Step 1) <br>Allocate TDM Physical Interfaces
 
! 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;" | (Step 2) <br>Create IP Port Ranges
 
! 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;" | (Step 2) <br>Create IP Port Ranges
 
! 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;" | (Step 3) <br>Modify NAP profile
 
! 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;" | (Step 3) <br>Modify NAP profile
Line 766: Line 796:
 
*[[Toolpack:Allocating_a_VoIP_Network_Access_Point_(NAP) B|Allocate a VoIP NAP]]
 
*[[Toolpack:Allocating_a_VoIP_Network_Access_Point_(NAP) B|Allocate a VoIP NAP]]
 
*[[Toolpack:Allocating_a_TDM_Network_Access_Point_(NAP) B|Allocate a TDM NAP]]
 
*[[Toolpack:Allocating_a_TDM_Network_Access_Point_(NAP) B|Allocate a TDM NAP]]
 +
*[[Web_Portal_Tutorial_Guide_v2.7#CAS|Allocate a CAS Stack and NAP]]
 
|-
 
|-
 
! 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;" | (Step 5) <br>Configure Media Gateway for H.248 mode
 
! 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;" | (Step 5) <br>Configure Media Gateway for H.248 mode
Line 839: Line 870:
 
'''*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.
 
'''*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'''.<br />
 +
'''group''' serves as two purpose:
 +
# priority: a lower value will have higher priority 
 +
# 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
 +
<br>
 +
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|Adding_Load_Sharing_to_Routing_Script]]
  
 
{| cellpadding="5" border="1" class="wikitable"
 
{| cellpadding="5" border="1" class="wikitable"
Line 844: Line 883:
 
! 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;" |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
 
! 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
 +
! 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;" |Priority and Load-sharing Routing
 
|-
 
|-
 
| valign="top" |
 
| valign="top" |
  
 
*[[Toolpack:Create_New_Routing_Script_B|Create new routing script]]
 
*[[Toolpack:Create_New_Routing_Script_B|Create new routing script]]
*[[Import_Customized_Routing_Script_A|Import customized routing script]]
+
*[[Enable_Flexible_NOA_Routing_Script_A|Enable Flexible NOA script]]
 
*[[Add_NOA_Columns_in_Routes_B|Add NOA columns in routes]]
 
*[[Add_NOA_Columns_in_Routes_B|Add NOA columns in routes]]
*[[Enable_Routing_Script_A|Enable routing script]]
+
*[[Enable_Routing_Script_B|Enable routing script in Gateway]]
 
*[[Activate_Configuration_B|Activate configuration]]
 
*[[Activate_Configuration_B|Activate configuration]]
  
Line 857: Line 897:
 
*[[Toolpack:Create_New_Routing_Script_B|Create new routing script]]
 
*[[Toolpack:Create_New_Routing_Script_B|Create new routing script]]
 
*[[Import_Customized_Routing_Script_A|Import customized routing script]]
 
*[[Import_Customized_Routing_Script_A|Import customized routing script]]
*[[Enable_Routing_Script_A|Enable routing script]]
+
*[[Enable_Routing_Script_B|Enable routing script in Gateway]]
 
*[[Activate_Configuration_B|Activate configuration]]
 
*[[Activate_Configuration_B|Activate configuration]]
  
 +
| valign="top" |
 +
 +
*[[Toolpack:Create_New_Routing_Script_B|Create new routing script]]
 +
*[[Enable_Priority_Loadsharing_Routing_Script_A|Enable Priority and Load-sharing Routing script]]
 +
*[[Add_group_weight_Columns_in_Routes_B|Add group and weight columns in routes]]
 +
*[[Enable_Routing_Script_B|Enable routing script in Gateway]]
 +
*[[Activate_Configuration_B|Activate configuration]]
 
|}
 
|}
  
Line 970: Line 1,017:
 
==Target Recording==
 
==Target Recording==
 
{| cellpadding="5" border="1" class="wikitable"
 
{| cellpadding="5" border="1" class="wikitable"
! width="300" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Activating a Configuration
+
! width="300" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Activate Call Recording
! width="300" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Web Portal Profile
+
! width="300" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Start the Stream Server
 +
! width="300" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Access the Recorded Files
 
|-
 
|-
 
| valign="top" |
 
| valign="top" |
 
*[[Enabling_Recordings_A|Enabling the Recording of Calls]]
 
*[[Enabling_Recordings_A|Enabling the Recording of Calls]]
 +
| valign="top" |
 +
*[[How_to_Start_Stream_Server|Start Stream Server]]
 
| valign="top" |
 
| valign="top" |
 
* [[Accessing_Recording|Accessing the Recording]]
 
* [[Accessing_Recording|Accessing the Recording]]
 
|}
 
|}
 +
 +
==VoIP Ethernet Capture==
 +
{| cellpadding="5" border="1" class="wikitable"
 +
! width="250" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Capturing Ethernet Traffic
 +
|-
 +
| valign="top" |
 +
*[[VoIP_Ethernet_Capture_TMG800_A|Capturing on a TMG800]]
 +
*[[VoIP_Ethernet_Capture_TMG3200_A|Capturing on a TMG3200]]
 +
*[[VoIP_Ethernet_Capture_TMG7800_A|Capturing on a TMG7800]]
 +
|}
 +
  
 
=''Status Menus''=
 
=''Status Menus''=

Latest revision as of 04:03, 18 January 2019

Contents

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

Web Portal Access User Management
Add User Modify User Permission Delete User


Database Backup

Create Database Backup Restore Database

SNMP

Enable SNMP SNMP Get/Get Next SNMP Traps

or

Configuration

Activating a Configuration Web Portal Profile

Upload license

Installing a Package

Statistics

Configuration Profile Graphs

Audit Logs

Audit Logs

VoIP Bonding

VoIP Bonding

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

Hardware

New Hardware

Add telecom hardware Add TMS hardware Add 1+1 group Add N+1 group

TDM Network

(Step 1)
Allocate Physical Interfaces
(Step 2)
System Clock

IP Network

(Step 1)
IP Interfaces
Create an IP port range

Protocol Stacks

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



CAS

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring a CAS 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
Remote NAT Traversal Local 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 1a)
Configuring the M3UA Layer - IPSP
(Step 1b)
Configuring the M3UA Layer - ASP
(Step 1c)
Configuring the M3UA Layer - SGP
(Step 2)
Configuring the ISUP Layer
(Step 3)
Modify NAP profile
(Step 4)
Configure Network Access Points (NAPs)

SS7 Advanced Features

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)
Configuring the M3UA Layer
(Step 2)
Configuring the SCCP Layer
(Step 3)
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 M2UA Configuration

H.248

(Step 1)
Allocate TDM 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


Fax

FAX passthrough FAX T.38


Routes

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.

*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
Flexible NOA Prefix NOA Priority and Load-sharing Routing


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

RADIUS Authorization and Authentication

RADIUS
RADIUS (with custom dictionary)

Troubleshooting

Call Trace

Call trace

Test Call

Test Call

Target Recording

Activate Call Recording Start the Stream Server Access the Recorded Files

VoIP Ethernet Capture

Capturing Ethernet Traffic


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
Personal tools