Installing SMSC-SMPP

This section describes hardware and software requirements for SMSC-SMPP. It also describes how to load SMSC-SMPP files on the NuPoint Messaging server.

Before You Begin

Loading SMSC-SMPP Files

Currently, SMSC-SMPP integration products include:

The MWI feature is considered base SMSC-SMPP software. Customers who want the CBN feature can install CBN in addition to MWI. To install optional feature software, follow the instructions in Installing an Optional Feature.

Configuration Overview

After loading SMSC-SMPP optional feature software, you can configure the NuPoint Unified Messaging server SMSC integration. There are three steps involved:

Configuring SMSC Processes and Links

SMSC processes and links are mechanisms that implement SMSC integration. An SMSC process represents software configured and running at the remote SMSC. (Each instance of SMSC process represents a separate SMPP pathway.) SMSC links are internal connections established by SMSC-SMPP at the NuPoint Unified Messaging server.

The first integration step is to identify (define) SMSC processes and links and to make associations between them. This step involves considerable input of parameters. For that reason, worksheets to plan SMSC process and link configuration are provided in Appendix A, “Configuration Worksheets.”

Configuring (Editing) Message Formats

The second integration step is to configure the formats for messages contained in MWIs and CBNs. The MWIs and CBNs are sent from the NuPoint Unified Messaging server to the SMSC.

As indicated in Installing SMSC-SMPP, you configure message formats by assembling mailbox variables and constants in a series. The variables and constants are called message elements. A field separator is placed between each element.

Configuring Mailboxes for SMSC Support

The third step for SMSC integration is to set the appropriate subscriber mailbox parameters to support MWI and CBN mechanisms.

The first two integration steps are done offline at the NuPoint Messaging console using the Resource Configuration Manager. The third step can be done through a network using the NP Mailbox Admin interface, or it can be done offline at the console using the Resource Configuration Manager.