Web Portal Tutorial Guide v2.6: Difference between revisions

Latest revision as of 15:53, 17 December 2021

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]

Access and User Management

Web Portal Access	User Access Levels
Connect to the Web Portal	User Access Viewing the User List Creating a New User Deleting a User Logging Off User privilege level

Database Backup

Create Database Backup	Restore Database
Carrying out a First Database Backup Downloading a Database Backup	Uploading a Database Backup Restoring a Database Backup

Configuration

Activating a Configuration
Activating the Configuration

Minor Package Upgrade

Installing a package
Retrieving a software release Uploading a software release Activating a software release

[edit]

New Hardware

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

TDM network

(Step 1) Allocate Physical Interfaces	System Clock
Create Line Interfaces Create Line services	System Clock

IP network

(Step 1) IP Interfaces	Create an IP port range
Configuring VoIP 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)
Create a new line interface Create a new line service	Configure an ISDN stack OR Configure NFAS	Modify profile	Allocate an ISDN NAP

ISDN Advanced Features

ISDN Overlap Sending
ISDN NFAS Overlap Parameters

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)
Create Line Interfaces Create Line services	Copy variant script Create CAS R2 stack Set backward digits string	Modify profile	Create a CASR2 NAP

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)
Create an IP port range	Create a SIP stack Create a SIP transport server Create a service access point (SAP)	Access profiles and validate settings	Modify profile	Allocate a SIP NAP

SIP Advanced Features

SIP-I SIP-T
Enabling SIP-I SIP-T

SIP Spiral
Enabling SIP Spiral

NAT Traversal
Enabling 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)
Create a new line interface Create a new line service	Create an MTP2 Configuration Create an MTP2 Link	Create an MTP3 Configuration Create an MTP3 Network Create an MTP3 Point Code Create an MTP3 Linkset Create MTP3 Links Create an MTP3 Route	Create an ISUP Stack Create an ISUP Network Create an ISUP User Part Create an ISUP Interface Create ISUP CIC Groups	Modify profile	Create an ISUP NAP

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)
Create a new line interface Create a new line service	Edit the SCTP Configuration Create an M2PA Configuration Create an M2PA SAP Add M2PA Links	Create an MTP3 Configuration Create an MTP3 Network Create an MTP3 Point Code Create an MTP3 Linkset Create MTP3 Links Create an MTP3 Route	Create an ISUP Stack Create an ISUP Network Create an ISUP User Part Create an ISUP Interface Create ISUP CIC Groups	Modify profile	Create an ISUP NAP

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)
Create a new line interface Create a new line service	Edit the SCTP Configuration Create SS7 Point Codes Create an M3UA Configuration Create an M3UA SAP Create an M3UA Network Create an M3UA User Part Create an M3UA Peer Signalling Process Create an M3UA Peer Server Create an M3UA Route	Create an ISUP Stack Create an ISUP Network Create an ISUP User Part Create an ISUP Interface Create ISUP CIC Groups	Modify profile	Create an ISUP NAP

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)
Create a new line interface Create a new line service	Create an MTP2 Configuration Create an MTP2 Link	Create an MTP3 Configuration Create an MTP3 Network Create an MTP3 Point Code Create an MTP3 Linkset Create MTP3 Links Create an MTP3 Route	Create an SCCP Stack Create an SCCP Network Create an SCCP Userpart Create an SCCP LSAP Create an SCCP Route Create an SCCP SSN Create an SCCP GTT Association Create an SCCP GTT Address Map	Create a TCAP Stack Create a TCAP Userpart Activating the Configuration

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)
Create a new line interface Create a new line service	Edit the SCTP Configuration Create an M2PA Configuration Create an M2PA SAP Add M2PA Links	Create an MTP3 Configuration Create an MTP3 Network Create an MTP3 Point Code Create an MTP3 Linkset Create MTP3 Links Create an MTP3 Route	Create an SCCP Stack Create an SCCP Network Create an SCCP Userpart Create an SCCP LSAP Create an SCCP Route Create an SCCP SSN Create an SCCP GTT Association Create an SCCP GTT Address Map	Create a TCAP Stack Create a TCAP Userpart Activating the Configuration

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)
Create a new line interface Create a new line service	Edit the SCTP Configuration Create SS7 Point Codes Create an M3UA Configuration Create an M3UA SAP Create an M3UA Network Create an M3UA User Part Create an M3UA Peer Signalling Process Create an M3UA Peer Server Create an M3UA Route	Create an SCCP Stack Create an SCCP Network Create an SCCP Userpart Create an SCCP LSAP Create an SCCP Route Create an SCCP SSN Create an SCCP GTT Association Create an SCCP GTT Address Map	Create a TCAP Stack Create a TCAP Userpart Activating the Configuration

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
Create line interfaces Create line services	Create an MTP2 Configuration Create MTP2 Links	Edit the SCTP Configuration Create an M2UA Configuration Create an M2UA SAP Create an M2UA Cluster Create M2UA Links Create M2UA Peers

M3UA

(Step 1) Create Line Interfaces	(Step 2) Create MTP2 links	(Step 3) Create MTP3 configuration	(Step 4) Create M3UA configuration
Create line interfaces Create line services	Create an MTP2 Configuration Create MTP2 Links	Create SS7 Point Codes Create an MTP3 Configuration Create an MTP3 Network Create an MTP3 Linkset Create MTP3 Links Create an MTP3 Route	Edit the SCTP Configuration Create an M3UA Configuration Create an M3UA SAP Create an M3UA Network Create an M3UA User Part Create an M3UA Peer Signalling Process Create an M3UA Peer Server Create an M3UA Route

IUA

(Step 1) Create Line Interfaces	(Step 2) Create IUA Configuration
Create Line Interfaces Create Line services	Edit the SCTP Configuration Create an IUA Configuration Create an IUA SAP Create an IUA Cluster Create IUA Links Create IUA Peers

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)
Create line interfaces Create line services	Create IP port ranges	Modify profile	Allocate a VoIP NAP Allocate a TDM NAP
(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
Configure the Media Gateway for H.248 mode Create a new H.248 configuration	Add a new media gateway controller (MGC)	Associate the NAPs with the H.248 configuration Select timeslots for the TDM interfaces

[edit]

Text CDR	RADIUS
Enabling CDR	Enabling RADIUS Configuring RADIUS client Adding RADIUS server(s)

[edit]

FAX passthrough	FAX T.38
Configure Fax Relay Configure Fax Passthrough	Configure Fax Relay Configure Fax T38

[edit]

Static route

Add routes
Create a first call 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.

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

Audio Prompts
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
Add Label Routing to script Create Database Files Assign Routing/Script Files to the Gateway Application Add the Digit Map Files to the System Add the Routset Definition Files to the System Assign Defintion/Digitmap Files on a per NAP Basis Generate Dynamic Routes Activate configuration

Update definition/digitmap files
Update the Digitmap Files Update the Routeset Definition Files Generate Dynamic Routes Activate configuration

[edit]

Call trace

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
Tmedia Status Menus Navigation Status Screen Conventions	System Adapters and IP Interfaces 1+1 Hosts Applications TDM Lines Line Interfaces SCTP SS7 MTP2 SS7 M2UA SS7 IUA SS7 M2PA SS7 M3UA SS7 MTP3 SS7 ISUP SS7 SCCP SS7 TCAP ISDN NFAS CAS R2 SIP Clock Clock Status List TMS NAP NAP Status List H.248 RADIUS

@@ Line 1: / Line 1: @@
-=Introduction=
+{{DISPLAYTITLE:Tmedia, Tsig, and Tdev Web Portal 2.7 Tutorial Guide}}
+__NOTOC__
+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==
+'''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 [http://download.distribution.telcobridges.com/documentation/TMP6400_Installation_Guide.pdf TMP6400 Installation Guide].)
+('''Note''': Tmedia devices are shipped with the Tmedia Web Portal pre-installed, while Tdev devices require that Toolpack be installed as described in the [[Tmedia_Installation#Tdev|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:
@@ Line 12: / Line 17: @@
 *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 [http://download.distribution.telcobridges.com/documentation/TMP6400_Installation_Guide.pdf TMP6400 Installation Guide].
+*The application software for the Tdev device will have been pre-installed on the Toolpack application server, as described in the [[Tmedia_Installation#Tdev|Tdev installation guides]].
 This document also assumes familiarity with topics, such as [[ISDN]] signaling, [[SIP]] signaling, [[SS7]], [[CAS|CAS R2]] signaling, and [[SIGTRAN]] signaling.
-==Key Concepts==
+'''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 <u>all</u> TMedia installations. Therefore, this section should be consulted before moving on to any other.
-'''Topics covered here:'''
+=System=
+'''Access and User Management'''
 {| cellpadding="5" border="1" class="wikitable"
 |-
-! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Log-on and User Access Levels
+! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Web Portal Access
-! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Database Backup
+! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | User Access Levels
 |-
 | valign="top" |
-*[[Toolpack:Connecting to the Web Server and logging on to the web portal A|Connect to the web server and log on to the Web Portal]]
+*[[Toolpack:Connecting to the Web Server and logging on to the web portal A|Connect to the Web Portal]]
+| valign="top" |
 *[[Toolpack:User access A|User Access]]
 **[[Toolpack:Viewing the User List A|Viewing the User List]]
@@ Line 43: / Line 48: @@
 **[[Toolpack:Logging Off A|Logging Off]]
 *[https://forums.telcobridges.com/viewtopic.php?f=12&t=248&p=1101&hilit=privilege#p1101 User privilege level]
+|}
+'''Database Backup'''
+{| cellpadding="5" border="1" class="wikitable"
+|-
+! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Create Database Backup
+! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Restore Database
+|-
 | valign="top" |
 *[[Toolpack:Database Backup A|Carrying out a First Database Backup]]
 *[[Toolpack:Downloading a Database Backup A|Downloading a Database Backup]]
+| valign="top" |
 *[[Toolpack:Uploading a Database Backup A|Uploading a Database Backup]]
 *[[Toolpack:Restoring a Database Backup A|Restoring a Database Backup]]
+|}
+'''Configuration'''
+{| cellpadding="5" border="1" class="wikitable"
+! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Activating a Configuration
+|-
+| valign="top" |
+*[[Toolpack:Activating_the_Configuration A|Activating the Configuration]]
 |}
+'''Minor Package Upgrade'''
+{| 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:Downloading_a_Release_A|Retrieving a software release]]
+*[[Toolpack:Uploading_a_Release_A|Uploading a software release]]
+*[[Toolpack:Activating_a_Release_A|Activating a software release]]
+|}
 =Hardware=
-== New Hardware ==
+'''New Hardware'''
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 73: / Line 102: @@
 |}
-==TDM network==
+'''TDM network'''
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 88: / Line 117: @@
 |}
-==IP network==
+'''IP network'''
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 96: / Line 125: @@
 |-
 | valign="top" |
-*[[Configuring IP Interfaces|IP Interfaces]]
+*[[Toolpack:Configuring_VoIP_Interfaces A|Configuring VoIP Interfaces]]
 | valign="top" |
 *[[Toolpack:Creating_an_IP_Port_Range A|Create an IP port range]]
 |}
 =Protocol Stacks=
-==ISDN/NFAS==
+'''ISDN NFAS'''
 {| cellpadding="5" border="1" class="wikitable"
@@ Line 128: / Line 152: @@
 | valign="top" |
-*[[Toolpack:Configuring_an_ISDN_Stack A|Configure an ISDN stack]]
+*[[Toolpack:Configuring_an_ISDN_Stack B|Configure an ISDN stack]]
 OR<br/>
 *[[Configure NFAS]]
@@ Line 136: / Line 160: @@
 | valign="top" |
-*[[Toolpack:Allocating_an_ISDN_Network_Access_Point_(NAP) A|Allocate an ISDN NAP]]
+*[[Toolpack:Allocating_an_ISDN_Network_Access_Point_(NAP) B|Allocate an ISDN NAP]]
 |}
+''ISDN Advanced Features''
-<div class="mw-collapsible mw-collapsed" data-collapsetext="Advanced Overlap Parameters" data-expandtext="Advanced Overlap Parameters" style="width: 400px;">
+<div class="mw-collapsible mw-collapsed" data-collapsetext="ISDN NFAS Overlap" data-expandtext="ISDN NFAS Overlap" style="width: 400px;">
 {| 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;" |Audio Prompts
+! 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;" |ISDN Overlap Sending
 |-
 | valign="top" |
-*[[Toolpack:Configuring_Overlap A|ISDN/NFAS Overlap Parameters]]
+*[[Toolpack:Configuring_Overlap A|ISDN NFAS Overlap Parameters]]
 |}
@@ Line 153: / Line 177: @@
 <br><br>
-==CASR2==
+'''CASR2'''
-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.
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 179: / Line 201: @@
 |}
-==SIP==
+'''SIP'''
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 208: / Line 229: @@
 |}
-<div class="mw-collapsible mw-collapsed" data-collapsetext="SIP Advance Features" data-expandtext="SIP Advance Features" style="width: 400px;">
+''SIP Advanced Features''
+{| 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;" | SIP-I SIP-T
+|-
+| valign="top" |
+*[[Enabling_SIP_I_SIP_T_A|Enabling SIP-I SIP-T]]
+|}
+</div>
+<div class="mw-collapsible mw-collapsed" data-collapsetext="SIP Spiral" data-expandtext="SIP Spiral" style="width: 400px;">
 {| 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;" | SIP-I/SIP-T
 ! 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;" | SIP Spiral
-! 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;" | NAT Traversal
 |-
-| valign="top" |
-*[[Enabling_SIP_I_SIP_T_A|Enabling SIP-I/SIP-T]]
 | valign="top" |
 *[[Enabling_SIP_Spiral_A|Enabling SIP Spiral]]
-| valign="top" |
-*[[Enabling_NAT_Traversal_A|Enabling NAT Traversal]]
 |}
-</div>
-<br>
-==SS7/ISUP==
-To configure the ISUP stack.
+{| cellpadding="5" border="1" class="wikitable"
+|-
-=== MTP2-MTP3-ISUP ===
+! 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;" | NAT Traversal
+|-
+| valign="top" |
+*[[Enabling_NAT_Traversal_A|Enabling NAT Traversal]]
+|}
+'''SS7 ISUP'''
+''MTP2-MTP3-ISUP''
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 254: / Line 280: @@
 | valign="top" |
-*[[Toolpack:Creating_an_MTP3_Configuration A|Create an MTP3 Configuration]]
+*[[Toolpack:Creating_an_MTP3_Configuration B|Create an MTP3 Configuration]]
 *[[Toolpack:Creating_an_MTP3_Network A|Create an MTP3 Network]]
 **[[Toolpack:Creating_SS7_Point_Codes A|Create an MTP3 Point Code]]
@@ Line 278: / Line 304: @@
 |}
+''M2PA-MTP3-ISUP''
-===M2PA-MTP3-ISUP===
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 303: / Line 326: @@
 | valign="top" |
-*[[Toolpack:Creating_an_MTP3_Configuration A|Create an MTP3 Configuration]]
+*[[Toolpack:Creating_an_MTP3_Configuration B|Create an MTP3 Configuration]]
 *[[Toolpack:Creating_an_MTP3_Network A|Create an MTP3 Network]]
 **[[Toolpack:Creating_SS7_Point_Codes A|Create an MTP3 Point Code]]
@@ Line 326: / Line 349: @@
 |}
+''M3UA-ISUP''
-===M3UA-ISUP===
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 369: / Line 390: @@
 |}
-==SCCP/TCAP==
+'''SCCP-TCAP'''
-===MTP2-MTP3-SCCP/TCAP===
+''MTP2-MTP3-SCCP-TCAP''
 {| cellpadding="5" border="1" class="wikitable"
@@ Line 395: / Line 413: @@
 | valign="top" |
-*[[Toolpack:Creating_an_MTP3_Configuration A|Create an MTP3 Configuration]]
+*[[Toolpack:Creating_an_MTP3_Configuration B|Create an MTP3 Configuration]]
 *[[Toolpack:Creating_an_MTP3_Network A|Create an MTP3 Network]]
 **[[Toolpack:Creating_SS7_Point_Codes A|Create an MTP3 Point Code]]
@@ Line 421: / Line 439: @@
 |}
-===M2PA-MTP3-SCCP/TCAP===
+''M2PA-MTP3-SCCP-TCAP''
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 444: / Line 460: @@
 | valign="top" |
-*[[Toolpack:Creating_an_MTP3_Configuration A|Create an MTP3 Configuration]]
+*[[Toolpack:Creating_an_MTP3_Configuration B|Create an MTP3 Configuration]]
 *[[Toolpack:Creating_an_MTP3_Network A|Create an MTP3 Network]]
 **[[Toolpack:Creating_SS7_Point_Codes A|Create an MTP3 Point Code]]
@@ Line 469: / Line 485: @@
 |}
+''M3UA-SCCP-TCAP''
-===M3UA-SCCP/TCAP===
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 513: / Line 527: @@
 |}
-==H.248/MEGACO==
+'''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.
@@ Line 519: / Line 533: @@
 If the Tmedia is used to connect media only, then you can go straight to [[#H.248|H.248 Configuration]]
-===M2UA===
+''M2UA''
 {| cellpadding="5" border="1" class="wikitable"
@@ Line 550: / Line 564: @@
-===M3UA===
+''M3UA''
 {| cellpadding="5" border="1" class="wikitable"
@@ Line 570: / Line 584: @@
 | valign="top" |
 *[[Toolpack:Creating SS7 Point Codes A|Create SS7 Point Codes]]
-*[[Toolpack:Creating an MTP3 Configuration A|Create an MTP3 Configuration]]
+*[[Toolpack:Creating an MTP3 Configuration B|Create an MTP3 Configuration]]
 **[[Toolpack:Creating an MTP3 Network A|Create an MTP3 Network]]
 **[[Toolpack:Creating an MTP3 Linkset A|Create an MTP3 Linkset]]
@@ Line 588: / Line 602: @@
 |}
-===IUA===
+''IUA''
 {| 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>Create Line 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 M2UA Configuration
+! 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 IUA Configuration
 |-
@@ Line 611: / Line 625: @@
 |}
-===H.248===
+''H.248''
 {| cellpadding="5" border="1" class="wikitable"
@@ Line 655: / Line 669: @@
-=CDR=
+=CDR (Call Detail Record)=
 {| cellpadding="5" border="1" class="wikitable"
 |-
@@ Line 664: / Line 677: @@
 | valign="top" |
-*[[Text_cdr|Text CDR]]
+*[[Toolpack:Enabling RADIUS A|Enabling CDR]]
 | valign="top" |
-*[[Toolpack:Configuring_RADIUS B|Configuring RADIUS]]
+*[[Toolpack:Enabling RADIUS A|Enabling RADIUS]]
+*[[Toolpack:Configuring_RADIUS_client A|Configuring RADIUS client]]
+*[[Toolpack:Adding_RADIUS_server A|Adding RADIUS server(s)]]
 |}
@@ Line 697: / Line 712: @@
 |}
-== Routing script ==
+'''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.
@@ Line 723: / Line 738: @@
 *[[Enable_Routing_Script_A|Enable routing script]]
 *[[Activate_Configuration_A|Activate configuration]]
 |}
-<div class="mw-collapsible mw-collapsed" data-collapsetext="Configuring Audio Prompts" data-expandtext="Audio Prompts" style="width: 400px;">
 {| cellpadding="5" border="1" class="wikitable"
@@ Line 736: / Line 748: @@
 |}
-</div>
-<br><br>
-== Label routing ==
+''' 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'''
+{|
+|STYLE="vertical-align: top"|
 {| 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;" |Label routing
+! 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;" |Add label routing functionality
 |-
 | valign="top" |
-*[[Toolpack:Configuring_Label_Routing A|Label routing]]
+*[[Adding_Label_Routing_to_any_Routing_Script|Add Label Routing to script]]
+*[[Create_Databse_Files A|Create Database Files]]
+*[[Assign_Routing_Script_DB_Files_to_Gateway_Application A|Assign Routing/Script Files to the Gateway Application]]
+*[[Add_Digitmap_Files A|Add the Digit Map Files to the System]]
+*[[Add_Routeset_Definition_Files A|Add the Routset Definition Files to the System]]
+*[[Assign_Definition_Digitmap_Files_per_NAP A|Assign Defintion/Digitmap Files on a per NAP Basis]]
+*[[Generate_Dynamic_Routes A|Generate Dynamic Routes]]
+*[[Activate_Configuration_A|Activate configuration]]
+|}
+|STYLE="vertical-align: top"|
+{| 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;" |Update definition/digitmap files
+|-
+| valign="top" |
+*[[Update_Digitmap_Files A|Update the Digitmap Files]]
+*[[Update_Routeset_Definition_Files A|Update the Routeset Definition Files]]
+*[[Generate_Dynamic_Routes A|Generate Dynamic Routes]]
+*[[Activate_Configuration_A|Activate configuration]]
+|}
 |}
 =Troubleshooting=
-== Call trace ==
+'''Call trace'''
 {| 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;" |Call trace
@@ Line 777: / Line 812: @@
 | valign="top" |
-*[[Toolpack:Status_Menus:System A|System]]
+*[[Toolpack:Status_Menus:System B|System]]
-*[[Toolpack:Status_Menus:Adapters_and_IP_Interfaces A|Adapters and IP Interfaces]]
+*[[Toolpack:Status_Menus:Adapters_and_IP_Interfaces B|Adapters and IP Interfaces]]
+*[[Toolpack:Status_Menus:1+1|1+1]]
 *[[Toolpack:Status_Menus:Hosts A|Hosts]]
 *[[Toolpack:Status_Menus:Applications A|Applications]]
 *[[Toolpack:Status_Menus:TDM_Lines A|TDM Lines]]
+**[[Toolpack:Status_Menus:Line Interfaces A|Line Interfaces]]
 *[[Toolpack:Status_Menus:SCTP A|SCTP]]
 *[[Toolpack:Status_Menus:SS7_MTP2 A|SS7 MTP2]]
@@ Line 796: / Line 833: @@
 *[[Toolpack:Status_Menus:CAS R2 A|CAS R2]]
 *[[Toolpack:Status_Menus:SIP A|SIP]]
-*[[Toolpack:Status_Menus:Clock A|Clock]]
+*[[Toolpack:Status_Menus:Clock B|Clock]]
+**[[Toolpack:Status_Menus:Clock Status List A|Clock Status List]]
 *[[Toolpack:Status_Menus:TMS A|TMS]]
 *[[Toolpack:Status_Menus:NAP A|NAP]]
+**[[Toolpack:Status_Menus:NAP Status List A|NAP Status List]]
 *[[Toolpack:Status_Menus:H.248 A|H.248]]
+*[[Toolpack:Status_Menus:RADIUS A|RADIUS]]
 |}
+<headertabs/>
 [[category:Toolpack]]