Skip Headers
Oracle® Communications Services Gatekeeper System Administrator's Guide
Release 5.0

Part Number E16623-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

24 Managing and Configuring Shortcode Mappings

This chapter describes how to configure shortcode mappings for incoming messages to Oracle Communications Services Gatekeeper.

Introduction

The Shortcode Mapper is shared between the following plug-ins:

The Shortcode Mapper maps network-triggered messages (mobile originated) with a given destination address, the original destination address, to another destination address, the translated destination address.

The original destination address can be expressed as a pattern (a regular expression), which means that a range, or set, of original destination addresses can be translated to one single translated destination address.

This is useful when applications are triggered by a range of phone numbers; for example, 2345600 through 2345699. Using the functionality available in the Parlay X 2.1 Short Messaging interface, the application would have to call startSmsNotification 100 times. Shortcode mapping allows the application to express the original destination address as a pattern, such as 23456?? generating only a single call to startSmsNotification using this address.

Configuration and Management

All configuration and management is performed in the managed object, ShortCodeMapper.

The ShortCodeMapper OAM functionality is shared among the plug-ins: they reuse the same MBean. Rendering, however, is per plug-in (one instance is displayed per plug-in). The ShortCodeMapper appears slightly differently depending on how to the MBean is accessed:

Reference: Attributes and Operations for ShortCodeMapper

Managed object: ShortCodeMapper

MBean: com.bea.wlcp.wlng.shortcode.management.ShortCodeMapperMBean

Following is a list of operations for configuration:

Operation: addShortCodeMapping

Scope: Cluster

Translates the original destination address of a network-triggered message to a translated destination address. The translated destination address is used when the message is matched with notification registrations. This makes it possible for an application to register for a notification from a single shortcode and receive messages sent to a range of shortcodes (original destination addresses).

Note:

Shortcode translation takes place before mapping a mobile originated message to registered application notifications. If two or more short code translations match an original destination number the best match, the most specific, is chosen.

An identifier for the shortcode translation is returned.

Signature:

addShortCodeMapping(orig_dest_pattern: String, trans_dest_addr: String)

Table 24-1 addShortCodeMapping

Parameter Description

orig_dest_pattern

Pattern that is matched against the original destination address of a message received from the network.

The pattern should be specified as a regular expression: ^6

trans_dest_addr

The resulting translated address.

Addresses must be specified with the prefix “tel:”.


Operation: listShortCodeMappings

Scope: Cluster

Displays a list of shortcode mappings.

Signature:

listShortCodeMappings()

Operation: removeShortCodeMapping

Scope: Cluster

Removes a previously added shortcode mapping. Both fields must match.

Signature:

removeShortCodeMapping(OriginalDestination: String, MappedDestination: String)

Table 24-2 removeShortCodeMapping

Parameter Description

OriginalDestination

Registered original destination pattern.

MappedDestination

Registered translated destination address.