Configuring the Network

You must set the platform Local Point Code (LPC) and aliases in the SS7 Monitor before doing anything else.

	NOTE: You cannot directly modify an LPC on an existing configuration. If you want to change the LPC, you must create a new network configuration as described in the section “Creating Different Network Configurations”.

For an explanation of LPC aliases, see the HP Opencall SS7 Application Developer's Guide.

Virtual Point Codes (VPCs) are non-physical point codes than enable each SS7 stack to have up to 16 point codes. Virtual Users (VUs) are user applications that send and receive traffic through the VPCs.

VPCs can be configured using the configure entities | LPC window, and VUs can be configured using the configure entities | SCCP window. Alternatively, both VPCs and VUs can be configured using the ss7oamtool command.

Links/Linksets

The Signaling Link Code (SLC) value for ANSI, ITU-T, and the Chinese standard must be between 0 and 15. For TTC, the SLC value must be between 0 and 7.

With a TTC system, you need to define whether the linkset is configured as A or B. A linkset defined as A accepts all even SLSs. A linkset defined as B accepts all odd SLSs.

Destinations/ Routes

Before you can configure destinations and routes, at least one route must be configured for each destination.

Only one destination may be configured as a gateway (STP used to interconnect national and international networks).

For information on cluster and full point code routing in the ANSI standard, see “Configuring ANSI Routing”.

Example for Configuring Destinations and Routes

The following example demonstrates how to configure destinations and routes.

The example configures a primary and secondary route from LPC 1 to DPC 3. In the case of the primary route, DPC 3 is both the APC and the DPC.

Peer Point Code

Only an LPC can have a peer point code.

Setting the concerned parameter

Use the following table to decide if you need to set the concerned parameter to y or n.

SCCP Standard used at DPC

Use this parameter to tell the LPC what SCCP standard mode is in use at the DPC. The syntax of how to do this is in the procedures and examples that follow.

Configuring Global Title Translations

In the Configure Global Title Translations window, the following abbreviations are used:

Under Address a backslash \ can be used as a void character. The numbers following the backslash are then ignored. For example, 800\ can be used to represent all 800 numbers.

Priority Field

You can prioritize your global title translations. This means that if one destination is no longer preferred (for example, it becomes inaccessible) then the destination with the next highest priority is contacted.

You can prioritize up to ten destinations for one global title translation. 0 has the highest priority and 100 has the lowest priority.

To change the default value, edit the file sys.<className>.sccp.

	NOTE: If you want the global title translation to be done by a remote node, configure the remote node (Remote SP) without a remoteUser (SSN). To modify or remove an SSN, create a new network configuration as described in the section “Creating Different Network Configurations”.

The overall procedure for configuring a GDI stack using the SS7 Monitor is the same as for any other SS7 stack.

	NOTE: Connections may be closed by the SS7 Stack in the case of an IP protocol error. If this happens the connection is not reactivated automatically. The HP Opencall GDI Server accepts client connections only if a TCAP application is connected to SSN 256. Otherwise, the connection is refused.

Configuring GDI as a Client

By default, a GDI host is configured as a server. If you want your GDI host to act as a client, you must edit the file sys.classname.gdi by hand - refer to the file’s comments to help you. You must add the line:

platformMode:     CLIENT;

after the line:

portNumber:     ha_ss7gdi_1;

This section provides offline and online procedures for configuring ISUP/TUP applications. It also provides a procedure for changing the circuit(s) assigned to a running ISUP application (ISUP CIC-based distribution).