Web Portal Tutorial Guide v2.6: Difference between revisions
No edit summary |
No edit summary |
||
Line 22: | Line 22: | ||
'''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. | *'''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. | *'''Hardware:''' Each TelcoBridges devices, whether it is a TMP6400, TMG3200, or TMS1600 is referred to as a hardware device or hardware adapter. | ||
Line 164: | Line 164: | ||
|} | |} | ||
''ISDN Advanced Features'' | |||
<div class="mw-collapsible mw-collapsed" data-collapsetext="ISDN NFAS Overlap" data-expandtext="ISDN NFAS Overlap" style="width: 400px;"> | <div class="mw-collapsible mw-collapsed" data-collapsetext="ISDN NFAS Overlap" data-expandtext="ISDN NFAS Overlap" style="width: 400px;"> | ||
Line 178: | Line 177: | ||
<br><br> | <br><br> | ||
'''CASR2''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 203: | Line 201: | ||
|} | |} | ||
'''SIP''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 232: | Line 229: | ||
|} | |} | ||
''SIP Advanced Features'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 251: | Line 247: | ||
|} | |} | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 261: | Line 256: | ||
*[[Enabling_NAT_Traversal_A|Enabling NAT Traversal]] | *[[Enabling_NAT_Traversal_A|Enabling NAT Traversal]] | ||
|} | |} | ||
'''SS7 ISUP''' | |||
''MTP2-MTP3-ISUP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 312: | Line 304: | ||
|} | |} | ||
''M2PA-MTP3-ISUP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 359: | Line 349: | ||
|} | |} | ||
''M3UA-ISUP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 401: | Line 390: | ||
|} | |} | ||
'''SCCP-TCAP''' | |||
''MTP2-MTP3-SCCP-TCAP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
Line 453: | Line 439: | ||
|} | |} | ||
''M2PA-MTP3-SCCP-TCAP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 501: | Line 485: | ||
|} | |} | ||
''M3UA-SCCP-TCAP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
Line 544: | Line 527: | ||
|} | |} | ||
'''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 forward signalling messages to the SSW, you will require to configure M2UA, M3UA or IUA before configuring H.248. | ||
Line 550: | Line 533: | ||
If the Tmedia is used to connect media only, then you can go straight to [[#H.248|H.248 Configuration]] | If the Tmedia is used to connect media only, then you can go straight to [[#H.248|H.248 Configuration]] | ||
''M2UA'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
Line 581: | Line 564: | ||
''M3UA'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
Line 619: | Line 602: | ||
|} | |} | ||
''IUA'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
Line 642: | Line 625: | ||
|} | |} | ||
''H.248'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
Line 686: | Line 669: | ||
=CDR (Call Detail Record)= | =CDR (Call Detail Record)= | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
Line 703: | Line 685: | ||
|} | |} | ||
=Fax= | =Fax= | ||
Line 731: | Line 712: | ||
|} | |} | ||
'''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. | 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 757: | Line 738: | ||
*[[Enable_Routing_Script_A|Enable routing script]] | *[[Enable_Routing_Script_A|Enable routing script]] | ||
*[[Activate_Configuration_A|Activate configuration]] | *[[Activate_Configuration_A|Activate configuration]] | ||
|} | |} | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
Line 770: | Line 748: | ||
|} | |} | ||
''' Label Routing''' | |||
This section assumes: | This section assumes: | ||
Line 808: | Line 784: | ||
=Troubleshooting= | =Troubleshooting= | ||
'''Call trace''' | |||
{| 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;" |Call trace | ! 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 867: | Line 843: | ||
|} | |} | ||
<headertabs/> | |||
[[category:Toolpack]] | [[category:Toolpack]] |
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.