Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
hp OpenCall SS7 platform Application Developer's Guide: For Release 3.1 on Linux > Chapter 1 Introduction to HP OpenCall SS7 APIs

Virtual Point Codes (VPCs) and Virtual Users (VUs)

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

NOTE: The VPC and VU features are available only if the signaling network is SS7. These features are not available if the signaling network is IP (using SIGTRAN).

These features provide the following functionalities:

  • On a single node, an SS7 stack can have multiple non-physical point codes (called VPCs).

  • A user application, called a Virtual User (VU), can receive and send traffic through VPCs, and manage the VPC behavior.

  • A user application can bridge a non-SS7 network with an SS7 network.

Two objects are associated with these features:

  • a VPC object that must be configured as a new point code.

  • a VU object that must be configured as a new local user application.

Virtual Point Codes (VPC)

A VPC is a non-physical point code. The configuration of a VPC consists in the dynamic configuration of a point code. A maximum of 16 VPCs is allowed on each HP OpenCall SS7 stack.

Like an Alias Point Code, a VPC is associated with the LPC.

In the case of an incoming MSU containing an Alias Point Code, the alias is replaced by the LPC (in the MTP routing label) before being given to the user. In the case of an incoming MSU containing a VPC, the DPC of the MTP Routing Label remains set to the VPC.

An outgoing MSU with the OPC set to a VPC is sent to the network without any substitution of the OPC.

Management and monitoring are not available on VPCs.

Virtual Users

A VU is a user that can be connected to a VPC. The configuration of a VU consists of the dynamic configuration of a SubSystem Number (SSN) associated with a VPC. Thus a VU is identified by two values: VPC and SSN.

A maximum of 16 VUs is allowed on each HP OpenCall SS7 stack. Because a VU application behaves like a local user application, all the SCCP functionalities, including monitoring, are available for a VU.

OAM API

The OAM API allows configuration of Virtual Point Codes (VPCs) through the command MTPL3_oamcmd() using the virtual_pc MtpOamObject object.

The OAM API allows configuration and monitoring of VUs using the following commands SCCP_oamcmd(), SCCP_oamrecv() and SCCP_oamstat() through the SO_VIRTUAL_USER SccpOamObject object.

SCCP API

The SCCP API allows connection to a Virtual User (VU) using the ss7_xifcreate() function and the cnx_info variable which has a specific add_info field.

Tutorials

The OAM and SCCP specific VPC tutorials show how to use the data structures and the functions of the OAM and SCCP APIs.

To use the OAM tutorials, execute the cc_oam makefile. This creates an executable file OAM. Execute this file without arguments to see how to use the program.

To use the SCCP VPC tutorials, execute the cc_sccp_vpc makefile. This creates two executables: SccpClientVpc and SccpServerVpc. Execute these programs without any arguments to see the available options. Do not forget to set the mode option (primary or secondary) to connect the tutorial to a Virtual User.

The files cc_sccp_vpc, SccpClientVpc.c and SccpServerVpc.c are located in the /opt/OC/tutorials directory.

CAUTION: If you want to change a makefile or a tutorial supplied with HP OpenCall SS7, you must first copy it to your own working directory. You must not change the sources supplied with the HP OpenCall SS7 product in the directories in which they are delivered.
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.