Oracle® Communications Services Gatekeeper System Administrator's Guide Release 5.1 E37531-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how to configure shortcode mappings for incoming messages to Oracle Communications Services Gatekeeper.
The Shortcode Mapper is shared between the following plug-ins:
Parlay X 2.1 Short Messaging/SMPP
Parlay X 2.1 Multimedia Messaging/MM7
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.
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:
In the Administration Console, expand the plug-in that uses short code mapping:
Plugin_px21_multimedia_messaging_mm7 > ShortCodeMapper
Plugin_px21_short_messaging_smpp > ShortCodeMapper
Then click ShortCodeMapper to display the operations and attributes for the Shortcode Mapper.
In an MBean browser, such as JConsole, one instance of the MBean is displayed using the same ObjectName (at the same hierarchical level) as the plug-in it is used by.
Note:
You need to configure ShortCodeMapper attributes for all of the above mentioned plug-ins that are going to use this functionality. Only the attributes for the related plug-in are displayed in the console.Managed object: ShortCodeMapper
MBean: com.bea.wlcp.wlng.shortcode.management.ShortCodeMapperMBean
Following is a list of operations for configuration:
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 short codes (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:”. |
Scope: Cluster
Displays a list of shortcode mappings.
Signature:
listShortCodeMappings()
Scope: Cluster
Removes a previously added shortcode mapping. Both fields must match.
Signature:
removeShortCodeMapping(OriginalDestination: String, MappedDestination: String)