Web Portal Tutorial Guide v2.7: Difference between revisions
Nicole Tan (talk | contribs) (Modify "Import customized routing script" to "Enable Flexible NOA") |
No edit summary |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Tmedia, Tsig, and Tdev Web Portal 2.7 Tutorial Guide}} | |||
__NOTOC__ | |||
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). | 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. | 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 [[Tmedia_Installation#Tdev|Tdev installation guides]].) | ('''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: | Furthermore, in the case of a Tdev device and the initial configuration of the [[Toolpack]] application server, the following will have been provided: | ||
| Line 16: | Line 20: | ||
This document also assumes familiarity with topics, such as [[ISDN]] signaling, [[SIP]] signaling, [[SS7]], [[CAS|CAS]] signaling, and [[SIGTRAN]] signaling. | This document also assumes familiarity with topics, such as [[ISDN]] signaling, [[SIP]] signaling, [[SS7]], [[CAS|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. | *'''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 22: | Line 26: | ||
'''''IMPORTANT!''''' The Topics covered in the following table are common to <u>all</u> TMedia installations. This section should be consulted before moving on to any other. | |||
'''''IMPORTANT!''''' The Topics covered in the following table are common to <u>all</u> TMedia installations. | |||
=System= | =System= | ||
'''Access and User Management''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 61: | Line 62: | ||
|} | |} | ||
'''Database Backup''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 75: | Line 76: | ||
|} | |} | ||
'''SNMP''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 93: | Line 94: | ||
|} | |} | ||
'''Configuration''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| 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 | ! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Activating a Configuration | ||
| Line 104: | Line 105: | ||
|} | |} | ||
'''Minor Package Upgrade''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 115: | Line 115: | ||
*[[Toolpack:Activating_a_Release_A|Activating a software release]] | *[[Toolpack:Activating_a_Release_A|Activating a software release]] | ||
|} | |} | ||
'''Upload license''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 127: | Line 126: | ||
*[[Toolpack:Uploading_a_License_A|Uploading a license]] | *[[Toolpack:Uploading_a_License_A|Uploading a license]] | ||
|} | |} | ||
'''Statistics''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 145: | Line 143: | ||
|} | |} | ||
'''Audit Logs''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 155: | Line 153: | ||
|} | |} | ||
'''VoIP Bonding''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 167: | Line 165: | ||
=Hardware= | =Hardware= | ||
'''New Hardware''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 187: | Line 185: | ||
|} | |} | ||
'''TDM Network''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 202: | Line 200: | ||
|} | |} | ||
'''IP Network''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 218: | Line 216: | ||
=Protocol Stacks= | =Protocol Stacks= | ||
'''ISDN NFAS''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
| Line 249: | Line 247: | ||
|} | |} | ||
'''ISDN Advanced Features''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
| Line 260: | Line 256: | ||
|} | |} | ||
'''CAS''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 290: | Line 284: | ||
|} | |} | ||
'''SIP''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 319: | Line 312: | ||
|} | |} | ||
'''SIP Advanced Features''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 328: | Line 320: | ||
*[[Enabling_SIP_I_SIP_T_B|Enabling SIP-I SIP-T]] | *[[Enabling_SIP_I_SIP_T_B|Enabling SIP-I SIP-T]] | ||
|} | |} | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 338: | Line 330: | ||
|} | |} | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 352: | Line 341: | ||
*[[Enabling_Local_NAT_Traversal_A|Enabling Local NAT Traversal]] | *[[Enabling_Local_NAT_Traversal_A|Enabling Local NAT Traversal]] | ||
|} | |} | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 364: | Line 352: | ||
</div> | </div> | ||
'''SS7 ISUP''' | |||
''MTP2-MTP3-ISUP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 413: | Line 399: | ||
|} | |} | ||
''M2PA-MTP3-ISUP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 460: | Line 444: | ||
|} | |} | ||
''M3UA-ISUP'' | |||
{| 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 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 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 1b) <br>Configuring the M3UA Layer - SGP | ! 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: continuous;" | (Step 1c) <br>Configuring the M3UA Layer - SGP | |||
! 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: 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: 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 482: | Line 466: | ||
**[[Toolpack:Creating an M3UA Peer Server A|Create an M3UA Peer Server]] | **[[Toolpack:Creating an M3UA Peer Server A|Create an M3UA Peer Server]] | ||
**[[Toolpack:Creating an M3UA Route A|Create an M3UA Route]] | **[[Toolpack:Creating an M3UA Route 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 ASP 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_(IPSP)_A|Create an M3UA User Part]] | |||
**[[Toolpack:Creating an M3UA Peer Application Server Process (ASP) A|Create an M3UA Peer Signalling Process]] | |||
**[[Toolpack:Creating an M3UA Peer Server (ASP) A|Create an M3UA Peer Server]] | |||
**[[Toolpack:Creating an M3UA Route (ASP) A|Create an M3UA Route]] | |||
| valign="top" | | | valign="top" | | ||
| Line 509: | Line 504: | ||
|} | |} | ||
''SS7 Advanced Features'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 524: | Line 517: | ||
|} | |} | ||
'''SCCP-TCAP''' | |||
''MTP2-MTP3-SCCP-TCAP'' | |||
| Line 578: | Line 568: | ||
|} | |} | ||
''M2PA-MTP3-SCCP-TCAP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 626: | Line 614: | ||
|} | |} | ||
''M3UA-SCCP-TCAP'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
|- | |- | ||
| Line 664: | Line 651: | ||
|} | |} | ||
=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 670: | Line 657: | ||
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 700: | Line 688: | ||
|} | |} | ||
''M3UA'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
| Line 738: | Line 726: | ||
|} | |} | ||
''IUA'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
| Line 761: | Line 749: | ||
|} | |} | ||
''H.248'' | |||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
| Line 803: | Line 791: | ||
|} | |} | ||
=CDR (Call Detail Record)= | =CDR (Call Detail Record)= | ||
| Line 823: | Line 809: | ||
|} | |} | ||
= | =Fax= | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
| Line 843: | Line 828: | ||
=Routes= | =Routes= | ||
'''Static Route''' | |||
{| 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;" |Add routes | ! 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 routes | ||
| Line 851: | Line 836: | ||
|} | |} | ||
''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 858: | Line 843: | ||
'''*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 863: | Line 856: | ||
! 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]] | ||
*[[Enable_Flexible_NOA_Routing_Script_A|Enable Flexible NOA 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_B|Enable routing script in Gateway]] | ||
*[[Activate_Configuration_B|Activate configuration]] | *[[Activate_Configuration_B|Activate configuration]] | ||
| Line 877: | Line 870: | ||
*[[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_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]] | |||
|} | |} | ||
{| cellpadding="5" border="1" class="wikitable" | {| cellpadding="5" border="1" class="wikitable" | ||
| Line 892: | Line 890: | ||
|} | |} | ||
=Label Routing= | |||
This section assumes: | This section assumes: | ||
| Line 928: | Line 924: | ||
|} | |} | ||
=RADIUS Authorization and Authentication= | |||
{| | {| | ||
|STYLE="vertical-align: top"| | |STYLE="vertical-align: top"| | ||
| Line 953: | Line 949: | ||
|} | |} | ||
=Lawful Interception= | =Lawful Interception= | ||
| Line 967: | Line 962: | ||
*[[Toolpack:Configuring_lawful_interception_A|Configure Lawful Agencies]] | *[[Toolpack:Configuring_lawful_interception_A|Configure Lawful Agencies]] | ||
|} | |} | ||
=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 980: | Line 975: | ||
|} | |} | ||
'''Test Call''' | |||
{| 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;" |Test Call | ! 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;" |Test Call | ||
| Line 988: | Line 983: | ||
|} | |} | ||
'''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;" | Activate Call Recording | ! width="300" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Activate Call Recording | ||
| Line 1,002: | Line 997: | ||
|} | |} | ||
'''VoIP Ethernet Capture''' | |||
{| cellpadding="5" border="1" class="wikitable" | {| 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 | ! width="250" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Capturing Ethernet Traffic | ||
| Line 1,013: | Line 1,008: | ||
= | =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 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). | ||
| Line 1,065: | Line 1,060: | ||
|} | |} | ||
<headertabs/> | |||
[[category:Toolpack]] | [[category:Toolpack]] | ||
Latest revision as of 16:29, 16 December 2021
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.
IMPORTANT! The Topics covered in the following table are common to all TMedia installations. This section should be consulted before moving on to any other.