Web Portal Tutorial Guide v2.5
(→SIGTRAN Application Scenarios) |
(→Web Portal Basics: Add minor package upgrade section) |
||
(30 intermediate revisions by 5 users not shown) | |||
Line 23: | Line 23: | ||
− | == | + | == Web Portal Disposition == |
+ | The Web Portal is divided up into eight major sections reflected in the navigation bar located on the left-hand side of the portal. These are: | ||
+ | |||
+ | #'''[[Web Portal Sections:Status|Status]]''' -- series of screens providing overall system status as well as the status of various active applications, services, interfaces, and protocols | ||
+ | #'''[[Web Portal Sections:Users|Users]]''' -- list of all individuals with access to the system | ||
+ | #'''[[Web Portal Sections:Logs|Logs]]''' -- view or download records of system activity | ||
+ | #'''[[Web Portal Sections:Backups|Backups]]''' -- create, download or restore copies of the overall system configuration data | ||
+ | #'''[[Web Portal Sections:Packages|Packages]]''' -- list of installed releases of the system software | ||
+ | #'''[[Web Portal Sections:Systems|Systems]]''' -- list of hardware devices and configuration settings | ||
+ | #'''[[Web Portal Sections:Configurations|Configurations]]''' -- list of settings that have been created for a device | ||
+ | #'''[[Web Portal Sections:Gateway|Gateway]]''' -- options for configuring network access points, call detail records, calling routes, etc. | ||
+ | |||
+ | |||
+ | == Web Portal Basics== | ||
'''''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. | '''''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. | ||
Line 75: | Line 88: | ||
|- | |- | ||
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | (Topic E) <br>Configure IP Interfaces | ! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | (Topic E) <br>Configure IP Interfaces | ||
+ | ! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | (Topic F) <br>Minor Package Upgrade | ||
|- | |- | ||
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack_v2.5:Configuring_IP_Interfaces|Configure IP Interfaces]] |
+ | | 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]] | ||
|} | |} | ||
Line 337: | Line 355: | ||
| valign="top" | | | valign="top" | | ||
*[[Toolpack:Adding an Adapter A|Adding an Adapter]] | *[[Toolpack:Adding an Adapter A|Adding an Adapter]] | ||
− | *[[Toolpack | + | *[[Toolpack:Creating a Line Interface A|Create Line Interfaces]] |
− | *[[Toolpack | + | *[[Toolpack:Creating an MTP2 Configuration A|Create an MTP2 Configuration]] |
− | *[[Toolpack | + | *[[Toolpack:Creating MTP2 Links A|Create MTP2 Links]] |
− | *[[Toolpack | + | *[[Toolpack:Creating the SCTP Configuration A|Edit the SCTP Configuration]] |
− | *[[Toolpack | + | *[[Toolpack:Creating SS7 Point Codes A|Create SS7 Point Codes]] |
− | *[[Toolpack | + | *[[Toolpack:Creating an MTP3 Configuration A|Create an MTP3 Configuration]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an MTP3 Network A|Create an MTP3 Network]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an MTP3 Linkset A|Create an MTP3 Linkset]] |
− | **[[Toolpack | + | **[[Toolpack:Creating MTP3 Links (M3UA) A|Create MTP3 Links]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an MTP3 Route A|Create an MTP3 Route]] |
− | *[[Toolpack | + | *[[Toolpack:Creating an M3UA Configuration (SGP) A|Create an M3UA Configuration]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA SAP A|Create an M3UA SAP]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Network A|Create an M3UA Network]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA User Part A|Create an M3UA User Part]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Peer Signalling Process (SGP) A|Create an M3UA Peer Signalling Process]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Peer Server A|Create an M3UA Peer Server]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Route (SGP) A|Create an M3UA Route]]<br> |
| valign="top" | | | valign="top" | | ||
*[[Toolpack:Adding an Adapter A|Adding an Adapter]] | *[[Toolpack:Adding an Adapter A|Adding an Adapter]] | ||
− | *[[Toolpack | + | *[[Toolpack:Creating the SCTP Configuration A|Edit the SCTP Configuration]] |
− | *[[Toolpack | + | *[[Toolpack:Creating SS7 Point Codes A|Create SS7 Point Codes]] |
− | *[[Toolpack | + | *[[Toolpack:Creating an M3UA Configuration (ASP) A|Create an M3UA Configuration]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA SAP A|Create an M3UA SAP]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Network A|Create an M3UA Network]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA User Part A|Create an M3UA User Part]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Peer Signalling Process (ASP) A|Create an M3UA Peer Signalling Process]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Peer Server A|Create an M3UA Peer Server]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA Route A|Create an M3UA Route]] |
− | *[[Toolpack | + | *[[Toolpack:Creating an ISUP Stack A|Create an ISUP Stack]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an M3UA ISUP Network A|Create an M3UA ISUP Network]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an ISUP User Part A|Create an ISUP User Part]] |
− | **[[Toolpack | + | **[[Toolpack:Creating an ISUP Interface A|Create an ISUP Interface]] |
− | ***[[Toolpack | + | ***[[Toolpack:Creating ISUP CIC Groups A|Create ISUP CIC Groups]] |
− | **[[Toolpack | + | **[[Toolpack:Creating a NAP (SIGTRAN) A|Create a NAP]] |
|} | |} | ||
Line 385: | Line 403: | ||
|- | |- | ||
| valign="top" | | | valign="top" | | ||
− | *[[Toolpack | + | *[[Toolpack:Adding an Adapter A|Adding an Adapter]] |
− | *[[ | + | *[[Toolpack:Creating_a_Line_Interface A|Create Line Interfaces]] |
− | *[[ | + | *[[Toolpack:Creating_a_Line_Service A|Create Line services]] |
− | *[[Toolpack | + | *[[Toolpack:Copy variant script A|Copy variant script]] |
− | *[[Toolpack | + | *[[Toolpack:Create CAS R2 stack A|Create CAS R2 stack]] |
− | *[[Toolpack | + | *[[Toolpack:Setting CAS R2 BACK DIGITS variable A|Set backward digits string]] |
− | *[[ | + | *[[Toolpack:Creating_a_CAS_R2_NAP A|Create a NAP]] |
|} | |} | ||
Line 409: | Line 427: | ||
|- | |- | ||
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Adding_an_Adapter A|Adding an Adapter]] |
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Creating_a_Line_Interface A|Create line interfaces]] |
− | *[[ | + | *[[Toolpack:Creating_a_Line_Service A|Create line services]] |
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Creating_an_IP_Port_Range A|Create IP port ranges]] |
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Allocating_a_VoIP_Network_Access_Point_(NAP) A|Allocate a VoIP network access point (NAP)]] |
− | *[[ | + | *[[Toolpack:Allocating_a_TDM_Network_Access_Point_(NAP) A|Allocate a TDM network access point (NAP)]] |
Line 434: | Line 452: | ||
|- | |- | ||
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Configure the Media_Gateway_for_H248_Mode A|Configure the Media Gateway for H.248 mode]] |
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Creating_an_H.248_Configuration A|Create a new H.248 configuration]] |
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Adding_a_Media_Gateway_Controller_(MGC) A|Add a new media gateway controller (MGC)]] |
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Associating_NAPs_with_an_H.248_Configuration A|Associate the NAPs with the H.248 configuration]] |
|- | |- | ||
Line 450: | Line 468: | ||
|- | |- | ||
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Selecting_Timeslots_for_TDM_Interfaces A|Select timeslots for the TDM interfaces]] |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
|} | |} | ||
Line 490: | Line 489: | ||
=Configuring RADIUS= | =Configuring RADIUS= | ||
− | Toolpack v2.5 can send accounting requests containing CDR data to a remote RADIUS server. In order to do so, refer to the [[ | + | Toolpack v2.5 can send accounting requests containing CDR data to a remote RADIUS server. In order to do so, refer to the [[Toolpack:Configuring_RADIUS A|Configuring RADIUS]] page. |
=Configuring Fax= | =Configuring Fax= | ||
Line 505: | Line 504: | ||
*[[Configure_Fax_Relay_A|Configure Fax Relay]] | *[[Configure_Fax_Relay_A|Configure Fax Relay]] | ||
*[[Configure_Fax_T38_A|Configure Fax T38]] | *[[Configure_Fax_T38_A|Configure Fax T38]] | ||
+ | |} | ||
+ | |||
+ | =Configuring 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. | ||
+ | |||
+ | {| 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;" |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 | ||
+ | |- | ||
+ | | valign="top" | | ||
+ | |||
+ | *[[Create_New_Routing_Script_A|Create new routing script]] | ||
+ | *[[Import_Customized_Routing_Script_A|Import customized routing script]] | ||
+ | *[[Add_NOA_Columns_in_Routes_A|Add NOA columns in routes]] | ||
+ | *[[Enable_Routing_Script_A|Enable routing script]] | ||
+ | *[[Activate_Configuration_A|Activate configuration]] | ||
+ | |||
+ | | valign="top" | | ||
+ | |||
+ | *[[Create_New_Routing_Script_A|Create new routing script]] | ||
+ | *[[Import_Customized_Routing_Script_A|Import customized routing script]] | ||
+ | *[[Enable_Routing_Script_A|Enable routing script]] | ||
+ | *[[Activate_Configuration_A|Activate configuration]] | ||
+ | |||
|} | |} | ||
Line 521: | Line 550: | ||
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Tmedia_Status_Menus A|Tmedia Status Menus]] |
− | **[[ | + | **[[Toolpack:Status_Menus:Navigation A|Navigation]] |
− | **[[ | + | **[[Toolpack:Status_Menus:Screen_Conventions A|Status Screen Conventions]] |
| valign="top" | | | valign="top" | | ||
− | *[[ | + | *[[Toolpack:Status_Menus:System A|System]] |
− | *[[ | + | *[[Toolpack:Status_Menus:Adapters_and_IP_Interfaces A|Adapters and IP Interfaces]] |
− | *[[ | + | *[[Toolpack:Status_Menus:Hosts A|Hosts]] |
− | *[[ | + | *[[Toolpack:Status_Menus:Applications A|Applications]] |
− | *[[ | + | *[[Toolpack:Status_Menus:TDM_Lines A|TDM Lines]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SCTP A|SCTP]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_MTP2 A|SS7 MTP2]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_M2UA A|SS7 M2UA]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_IUA A|SS7 IUA]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_M2PA A|SS7 M2PA]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_M3UA A|SS7 M3UA]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_MTP3 A|SS7 MTP3]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_ISUP A|SS7 ISUP]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_SCCP A|SS7 SCCP]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SS7_TCAP A|SS7 TCAP]] |
− | *[[ | + | *[[Toolpack:Status_Menus:ISDN A|ISDN]] |
− | **[[ | + | **[[Toolpack:Status_Menus:NFAS A|NFAS]] |
− | *[[ | + | *[[Toolpack:Status_Menus:CAS R2 A|CAS R2]] |
− | *[[ | + | *[[Toolpack:Status_Menus:SIP A|SIP]] |
− | *[[ | + | *[[Toolpack:Status_Menus:Clock A|Clock]] |
− | *[[ | + | *[[Toolpack:Status_Menus:TMS A|TMS]] |
− | *[[ | + | *[[Toolpack:Status_Menus:NAP A|NAP]] |
− | *[[ | + | *[[Toolpack:Status_Menus:H.248 A|H.248]] |
− | + | ||
|} | |} |
Latest revision as of 14:44, 27 June 2013
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 TMP6400 Installation Guide.)
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 TMP6400 Installation Guide.
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.
Web Portal Disposition
The Web Portal is divided up into eight major sections reflected in the navigation bar located on the left-hand side of the portal. These are:
- Status -- series of screens providing overall system status as well as the status of various active applications, services, interfaces, and protocols
- Users -- list of all individuals with access to the system
- Logs -- view or download records of system activity
- Backups -- create, download or restore copies of the overall system configuration data
- Packages -- list of installed releases of the system software
- Systems -- list of hardware devices and configuration settings
- Configurations -- list of settings that have been created for a device
- Gateway -- options for configuring network access points, call detail records, calling routes, etc.
Web Portal Basics
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:
- The basic knowledge needed to properly navigate through the Web Portal (A).
- The fundamentals of user account management and permission masks (B).
- The initial steps required for first starting the Web Portal, and verifying that it is functioning properly (C).
- The process involved in backing up your database for the first time (D).
- The process involved in first configuring your IP interfaces (E).
(Topic A) Web Portal Basics |
(Topic B) Log-on and User Access Levels |
(Topic C) Application Start-up and Verification |
(Topic D) Database Backup |
---|---|---|---|
|
|||
(Topic E) Configure IP Interfaces |
(Topic F) Minor Package Upgrade | ||
ISDN-SIP Gateway Configuration
The following tables contain a typical configuration scenario for an ISDN to SIP gateway. This type of installation allows for the transfer of information from traditional ISDN signaling to SIP protocol for VoIP applications. Please follow each step one after another as these are listed in logical order.
The steps are as follows:
- 1) Log On and Create a New Configuration
- 2) Allocate Physical Interfaces
- 3) Configure ISDN-PRI Signaling
- 4) Configure Clocking Source
- 5) Configure SIP Signaling
- 6) Configure Codecs and Tone Detection
- 7) Configure Network Access Points (NAPs)
- 8) Create Call Routing Rules
IMPORTANT! After completing the setup process, remember to activate the configuration, as outlined in the General Web Portal Applications section.
(Step 1) Log On and Create a New Configuration |
(Step 2) Allocate Physical Interfaces |
(Step 3) Configure ISDN-PRI Signaling |
(Step 4) Configure Clocking Source |
---|---|---|---|
OR |
|||
(Step 5) Configure SIP Signaling |
(Step 6) Configure Codecs and Tone Detection |
(Step 7) Configure Network Access Points (NAPs) |
(Step 8) Create Call Routing Rules |
Configuring SS7
The following table contains information on configuring the SS7 signaling protocol. The various control layers of the SS7 protocol are listed individually in each column. These layers are:
Follow the topics listed in each column from left to right in order to configure an SS7 protocol stack.
(Step 1) Configuring the MTP2 Layer |
(Step 2) Configuring the MTP3 Layer |
(Step 3) Configuring the ISUP Layer |
(Step 4) Configuring the SCCP Layer |
(Step 5) Configuring the TCAP Layer |
---|---|---|---|---|
|
|
|
|
|
SIGTRAN Application Scenarios
Toolpack version 2.5 enables you to configure SIGTRAN and thereby extend SS7 signalling functionality to the IP network. Toolpack enables you to configure a number of SIGTRAN applications based upon your requirements. These applications are listed below as follows:
- M2PA system. See column (A) below. In this configuration the SS7 MTP2 layer is replaced by the SIGTRAN M2PA layer which extends MTP2 signalling functionality into the IP network. This application is typically used between a Signalling Gateway and an IP Signalling Point, or between two IP Signalling Points.
- M2UA system. See columns (B) and (C) below. An M2UA system on a Signalling Gateway Controller interfaces with an M2UA system on a Media Gateway Controller. In this configuration, M2UA bridges the SS7 MTP2 layer of a Signalling Gateway, across an IP network, with the SS7 MTP3 layer of a Media Gateway Controller.
- IUA system. See column (D) below. An IUA system on a Signalling Gateway Controller interfaces with an IUA system on a Media Gateway Controller. In this configuration, IUA bridges the SS7 MTP2 layer of a Signalling Gateway, across an IP network, with the SS7 MTP3 layer of a Media Gateway Controller.
- M3UA system on two IP signalling points. See column (E) below. In this configuration the SS7 MTP2 and MTP3 layers are replaced entirely by the SIGTRAN M3UA layer. This application is typically used between two IP Signalling Points.
- M3UA system. See columns (F) and (G) below. An M3UA system on a Signalling Gateway Process interfaces with an M3UA system on an Application Server Process. In this configuration, the MTP3 links are extended across the IP network.
A SIGTRAN scenario walkthrough is provided in the table columns below, to illustrate the order that must be followed when configuring SIGTRAN.
(Scenario A) Configuring an M2PA System |
(Scenario B) Configuring an M2UA System on a Signalling Gateway |
(Scenario C) Configuring an M2UA System on a Media Gateway Controller |
(Scenario D) Configuring an IUA System on a Signalling Gateway |
(Scenario E) Configuring an M3UA System on IP Signalling Points |
(Scenario F) Configuring an M3UA System on a Signalling Gateway |
(Scenario G) Configuring an M3UA System on an Application Server |
---|---|---|---|---|---|---|
|
|
Configuring CAS R2
Toolpack v2.5 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.
Configuring a CAS R2 stack |
---|
Configuring H.248
The following table contains steps for configuring an H.248 media gateway control protocol
(Step 1) Add a Hardware Adapter |
(Step 2) Allocate Physical Interfaces |
(Step 3) Create IP Port Ranges |
(Step 4) Configure Network Access Points (NAPs) |
---|---|---|---|
|
| ||
(Step 5) Configure the Media Gateway for H.248 mode |
(Step 6) Create an H.248 Configuration |
(Step 7) Add a New Media Gateway Controller |
(Step 8) Associate NAPs with the H.248 Configuration
|
(Step 9) Select Timeslots for TDM Terminations | |||
Configuring SNMP
To use the Simple Network Management Protocol (SNMP)on your machine, you must first configure the tbSnmpAgent.
The tbSnmpAgent is a software application that interfaces between the TMedia system hardware and the NetSnmp implementation of the SNMP that is supported by TelcoBridges.
By default, tbSnmpAgent is disabled. In order to use the SNMP protocol to monitor and manage your hardware, complete the following tasks:
- Activate the tbSnmpAgent
- Configure the tbSnmpAgent as required
These tasks can be completed using the Web Portal:
Once these tasks are completed, your TMedia platform is ready to expose system variables for polling with the Simple Network management Protocol (SNMP).
Configuring RADIUS
Toolpack v2.5 can send accounting requests containing CDR data to a remote RADIUS server. In order to do so, refer to the Configuring RADIUS page.
Configuring Fax
FAX passthrough | FAX T.38 |
---|---|
Configuring 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 |
---|---|
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 |
---|---|