In this section:

GWST Process Overview

Note

The terms CPU and VM may be used interchangeably. 

For detailed information about the appropriate description of the various supported CPUs and VMs, refer to Terminology.

GWST is based on the configurable data found in the GWST configuration file and the GWST screening, redirection, and accounting tables. The GWST feature is deployed with the Message Transfer Part 3 (MTP3) over multiple peers for maximum performance.

As shown in the following figure, each MTP3 DRE process links with the GWST library. The GWST library is responsible for the gateway screening queries, accounting, measurements, and statistics collection. A separate Gateway Screening process is started on each Routing and Management CPU to manage the data provisioning and screening measurements through the UI proxy bridge (PXBR) connections.

For gateway accounting, the GWST sends its accounting category statistics to the Statistics Collector Agent (SCA). All the reporting and file management of the accounting data is handled by the SCA process and associated scripts on the Routing and Management CPU.

Note

MTP3 DRE and SNM connectivity is not shown in the following figure for simplicity.

For SP2000

The MSU Tracing process for the SP2000 is executed with only one management CPU and typically one Routing CPU.

GWST Process Overview

Filtering

If required to manage a large number of records, use GWST Web UI filter capabilities for all screening, redirection, and accounting tables. The Web UI filters large number of these database records based on the criteria you define in the Web UI, takes a snapshot of these records, and displays the filtered information in the Web UI for your use.

There are two ways to access a filter table – as a SS7ADMIN user with read/write access or as a monitor user with read-only access.

Note

A maximum of 16 concurrent users can access a filtered table, but only one of the 16 can have the read/write access. Non-monitor users have the ability to enter the table in read-only access if the read/write access is already in use.

A total of 96 sessions are allowed to access the filtered tables in GWST.

Beyond the 96 user maximum on the GWST, there is always a minimum of one read/write or read-only session guaranteed per table.

Multiple tabs do not equal multiple sessions; however, opening different browsers does create multiple sessions.

Monitor users and users selecting read-only access can only filter up to a maximum of 2,000 records. If the output of the criteria exceeds this maximum, an error will be returned requesting a fine-tune of the criteria for a more restricted output.

If you access a filtered table as a read/write user, the Web UI locks the given table until you complete your task. Clearing this lock may take place in the following three ways:

  • after you back out of the filtered table, the Web UI automatically unlocks this table
  • if more than an hour has passed since any activity has occurred
  • another read/write user unlocks the filtered table in the Web UI

If another read/write user wants to unlock the table, the Web UI displays a caution message that the respective filtered table is locked by <username of current read/write user> and unlocking this table forces the release of the table. If the new user only wants to view the GWST, there is an option to continue with Read Only access as a monitor user. Otherwise, the user can force an unlock in order to edit the table. See the following figure.

Example of a locked warning message

Filtered information is usually associated with other records or lists from different tables. The Soft Link feature helps link related filtered records and lists across multiple database tables for the GWST application. The Soft Link (displayed as an arrow on the Web UI, see the following figure) is created between a record or list according to the creation and provisioning hierarchy of the GWST application. As a result, Soft Links have a one-way relationship between database records and lists.

For GWST, links to records or lists are retrieved using the Next Table and the Next EPR attribute. The Soft Link goes to the record or list based on the Next Step attribute. In the following figure, for example, the Allowed SIO Soft Link goes to the Allowed TCAP OP Codes table.

GWST Soft Link Example

Note

Soft Links do not appear in the Web UI if there is no record or table to link to the attribute.

If the table owning the linked record or list of records is locked, a warning message appears requesting the user decide to continue with read only access or to unlock the table, forcing the release of the table from the current user who is viewing or editing a record in the table.

Note

After clicking a filtered Soft Link selection, the back button cannot be used to return to the originating record. To get back to the originating record, a new filter must be applied on the given table. This filter application can trigger the lock warning prompt if that table is in use by another user.

  • No labels