oracle communications network charging and control product ... manager n… · oracle...

Oracle Communications Network Charging and Control

Product: OCNCC 4.3 Component: Messaging Manager Navigator

Technical Guide S’ware version: Release 3.1.2 Guide version: 03.00

Release date: December 2010

Status: Approved

Commercial In Confidence

Page ii Messaging Manager Navigator Technical Guide

Copyright Messaging Manager Navigator Technical Guide, Release 3.1.2

03.00

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.


Messaging Manager Navigator Page iii Technical Guide

Contents

Copyright ............................................................................................................................. ii About this Document ........................................................................................................... v Document Conventions ...................................................................................................... vi

Chapter 1 .................................................................................................................... 1

System Overview ............................................................................ 1

Overview .............................................................................................................................. 1 What is Messaging Manager Navigator? ............................................................................ 2

Chapter 2 .................................................................................................................... 3

Configuration .................................................................................. 3

Overview .............................................................................................................................. 3 RIMS Configuration File ...................................................................................................... 4 MAP ..................................................................................................................................... 6 IS41 ..................................................................................................................................... 8 Caching .............................................................................................................................. 12 Chassis Actions ................................................................................................................. 15

Chapter 3 .................................................................................................................. 19

RIMS Nodes ................................................................................... 19

Overview ............................................................................................................................ 19 RIMS Nodes Use Cases .................................................................................................... 20 Available Feature Nodes ................................................................................................... 21 IS41 RIMS Query .............................................................................................................. 22 MAP RIMS Query .............................................................................................................. 25

Chapter 4 .................................................................................................................. 29

Background Processes ................................................................ 29

Overview ............................................................................................................................ 29 Statistics ............................................................................................................................ 30

Chapter 5 .................................................................................................................. 33

Troubleshooting ........................................................................... 33

Overview ............................................................................................................................ 33 Common Troubleshooting Procedures .............................................................................. 34

Chapter 6 .................................................................................................................. 37

System Alarms .............................................................................. 37

Overview ............................................................................................................................ 37 Alarm Topic Description .................................................................................................... 38 RIMS Alarms ...................................................................................................................... 40

Chapter 7 .................................................................................................................. 51

Installation ..................................................................................... 51

Overview ............................................................................................................................ 51 Loading the Distribution File .............................................................................................. 52 Installing the rimsScp Package ......................................................................................... 53 Installing the rimsSms Package ........................................................................................ 56


Page iv Messaging Manager Navigator Technical Guide

Installing the rimsSms Package on a Cluster .................................................................... 59

Chapter 8 .................................................................................................................. 63

Removal ......................................................................................... 63

Overview ............................................................................................................................ 63 Un-installing the rimsSms Package ................................................................................... 64 Un-installing the rimsScp Package .................................................................................... 67

Appendix .................................................................................................................. 69 Overview ............................................................................................................................ 69 Glossary of Terms ............................................................................................................. 71 Index .................................................................................................................................. 75


Messaging Manager Navigator Page v Technical Guide

About this Document The scope of this document includes all the information required to install, configure and administer the Messaging Manager Navigator application.

This guide was written primarily for system administrators and persons installing, configuring and administering the Messaging Manager Navigator application. However, sections of the document may be useful to anyone requiring an introduction to the application.

A solid understanding of Unix and a familiarity with IN concepts are an essential pre-requisite for safely using the information contained in this technical guide. Attempting to install, remove, configure or otherwise alter the described system without the appropriate background skills, could cause damage to the system; including temporary or permanent incorrect operation, loss of service, and may render your system beyond recovery.

Although it is not a pre-requisite to using this guide, familiarity with the target platform would be an advantage.

This manual describes system tasks that should only be carried out by suitably trained operators.

The following documents are related to this document:

• MMX Technical Guide

• MMX User's Guide

Scope

Audience

Pre-requisites

Related documents


Page vi Messaging Manager Navigator Technical Guide

Document Conventions Before you start using this guide, it is important to understand the terms and typographical conventions used in the documentation.

Specialised terms and acronyms are defined in the Glossary at the end of this guide.

Formatting convention Type of information Special Bold Items you must select such as menu options,

or names of tabs. Emphasis within text. Names of database tables and fields.

Italics Name of a document, chapter, topic or other publication.

Button The name of a button to click or a key to press. Example: To close the window, either click Close or press Esc.

Key+Key Key combinations for which the user must press and hold down one key and then press another. Example: Ctrl+P, or Alt+F4.

Monospace Text that you must type and examples of code or standard output.

variable Used to indicate variables or text that should be replaced.

menu option > menu option > Used to indicate the cascading menu option to be selected, or the location path of a file. Example: Operator Functions > Report Functions Example: /IN/html/SMS/Helptext/

hypertext link Used to indicate a hypertext link on an HTML page.

The following icons are used as visual cues to draw attention to important information.

Note: Indicates useful and complementary information. Explanation, comment, or short expansion of the text object that is intended to catch your attention.

Tip: Indicates practical but non-essential information that makes the solution easier to use or operate (e.g. keyboard shortcut, alternative way to perform a step in a procedure, etc).

Warning: Indicates a caution. If this information is ignored, it could cause possible and irreversible damage to the equipment, data or software.

Typographical conventions

Icons


Messaging Manager Navigator Page 1 Technical Guide

System Overview Overview

This chapter provides a high-level overview of the application. It explains the basic functionality of the system and lists the main components.

It is not intended to advise on any network or service implications of the product.

This chapter contains the following topics.

What is Messaging Manager Navigator? ........................................................ 2

Chapter 1

Introduction

In this chapter

Chapter 1 Commercial In Confidence

Page 2 Messaging Manager Navigator Technical Guide

What is Messaging Manager Navigator? Messaging Manager Navigator is a SLEE interface which caches as much of the HLR lookup information as possible. This reduces the amount of network traffic, and makes the HLR information available to other applications.

Messaging Manager Navigator performs a protocol specific HLR dip. It supports both IS-41 CDMA and MAP (1,2,3) messages. It supports cache maintenance commands from other processes for functions such as clearing/invalidating cache entries and updating cache entries. The cached HLR information is required by Messaging Manager to perform FDA.

Note: Throughout this manual there are references to RIMS. This is the name of the Messaging Manager Navigator program.

Here is a diagram showing the Messaging Manager Navigator and HLR lookup processes on the UAS.

Introduction

SCP processes



Configuration Overview

This chapter explains the configuration of the RIMS section of the eserv.config file.


RIMS Configuration File .................................................................................. 4 MAP ................................................................................................................. 6 IS41 ................................................................................................................. 8 Caching ......................................................................................................... 12 Chassis Actions ............................................................................................. 15

Chapter 2

Introduction

In this chapter



RIMS Configuration File Here is an example of the Messaging Manager Navigator config section (known as RIMS) of the eserv.config. RIMS = {

tcapInterfaceServiceKey = 42 sleepTime = 100000 hlrTimeout = 3 hlrErrorMap = [

{ error = 1, permanent = true } { error = 32, permanent = false }

] MAP = {

defaultMapVersionHlr = 3 hlrErrorMap = [

{ error = 1, permanent = true } { error = 32, permanent = false } { error = 73, permanent = true }

] GT = "" PC = 17 SSN = 9 checkCacheForTcap = false

} IS41 = {

MdnMinTranslation = [ { fromNoa=306, prefix="3", min=4, max=32, remove=2, prepend="1111" } { fromNoa=0, prefix="00", min=4, max=32, remove=0, prepend="" } { fromNoa=0, prefix="0", min=1, max=32, remove=1, prepend="0032" } { fromNoa=0, prefix="", min=1, max=6, remove=0, prepend="" } { fromNoa=0, prefix="", min=1, max=32, remove=0, prepend="0032" } { fromNoa=1, prefix="", min=1, max=32, remove=0, prepend="00" } { fromNoa=2, prefix="", min=1, max=32, remove=0, prepend="0032" }

] GT = "" PC = 17 SSN = 8 checkCacheForTcap = false supportIS841 = false minHLRTransType = 3 mdnHLRTransType = 14

} # Cache tuning options

Continued on next page

Example config file

Commercial In Confidence Chapter 2

RIMS Configuration File, Continued


Example config file (continued)

cache = { size = 5000000 defaultSuccessValidityPeriod = “01:00:00” defaultTransientFailureValidityPeriod = “00:30:00” defaultPermanentFailureValidityPeriod = “04:00:00” successValidityPeriods = {

{ prefix = “027”, period = “01:30:00” } { prefix = “021”, period = “00:45:00” }

} transientFailureValidityPeriods = {

{ prefix = “027”, period = “00:15:00” } } permanentFailureValidityPeriods = {

{ prefix = “027”, period = “03:00:00” } }

} ChassisActions = {

RimsChassisAction = { rimsInterfaceName = "rimsIf" TON = "001" NPI = "001" allowGPRS = true timeout = 3 timeoutTick = 3

} }

}

Here are the parameters for the main section of the RIMS config.

tcapInterfaceServiceKey

Syntax: tcapInterfaceServiceKey = <num> Description: SLEE service key of Hughes stack. Example: tcapInterfaceServiceKey = 42

sleepTime

Syntax: sleepTime = <microseconds> Description: Sleep time when there is no work to do. Allowed: microseconds Example: sleepTime = 10000

hlrTimeout

Syntax: hlrTimeout = <secs> Description: Timeout period for queries to the HLR. Allowed: seconds Example: hlrTimeout = 3

RIMS parameters



MAP The RIMS config includes a sub-section for interacting with the MAP plugin.

Destination fields for data from RIMS for IMSI is in the callingImsi or calledImsi.

Destination fields for data from RIMS for VMSC is in in the locationNum or the calledLocationNum.

Destination fields for data from RIMS for SGSN is in in the callingSgsn or the calledSgsn.

Here is an example configuration of the MAP sub-section of the RIMS section. MAP = {

defaultMapVersionHlr = 3 hlrErrorMap = [

{ error = 1, permanent = true } { error = 32, permanent = false } { error = 73, permanent = true }

] GT = "" PC = 17 SSN = 9 checkCacheForTcap = false

}

defaultMapVersionHlr

Syntax: defaultMapVersionHlr = <num> Description: MAP version used to query the HLR. Example: defaultMapVersionHlr = 3

Here are the MAP configuration parameters.

Note: GT, PC and SSN form the source address used by Messaging Manager Navigator when consulting a MAP HLR.

hlrErrorMap

Syntax: hlrErrorMap = [ {

error = <int>, permanent = <bool> } ...

] Description: Mapping of HLR responses to severity. Type: Array Example: hlrErrorMap = [

{ error = 1, permanent = true } ...

]


Introduction

IMSI store location VMSC store location

SGSN store location

Example MAP config

MAP parameters


MAP, Continued


MAP parameters (continued)

GT

Syntax: GT = <num> Description: Originating Global Title used by the HLR to communicate

back to MMX or Messaging Manager Navigator (RIMS). Allowed Valid global title number Note: This parameter takes priority over PC or SSN match. Example: GT = "62912425346"

PC

Syntax: PC = <num> Description: Originating Point Code array of messages used by the HLR

to communicate back to MMX or Messaging Manager Navigator (RIMS).

Allowed Defined by Network Administrator Default: 0 Note: • This parameter takes priority over SSN match.

• To remove the point code from outgoing requests, set the PC value to 65535.

Example: PC = 17

SSN

Syntax: SSN = <num> Description: Originating Subsystem Number of the messages used by

HLR to communicate back to MMX or Messaging Manager Navigator (RIMS).

Allowed Valid sub system number. Note: Example: SSN = 9

checkCacheForTcap

Syntax: checkCacheForTcap = <bool> Description: Determines whether the RIMS cache will be checked for

MAP SRISM messages. Type: Boolean Allowed: true, false Default: false Example: checkCacheForTcap = false



IS41 When Messaging Manager performs a RIMS query using the IS41 Protocol, RIMS uses a set of number rules to normalise the MDN to a MIN. The MIN is then sent to the HLR and used to locate the VMSC.

Note: This is the default action; however you can turn this off and allow RIMS to send the MDN to the HLR, rather than perform the conversion. The RIMS config includes a sub-section for interacting with the IS-41 plugin.

Destination fields for data from RIMS for MIN is in the callingImsi or calledImsi.

Destination fields for data from RIMS for VMSC is in in the locationNum or the calledLocationNum.

ACCESS_DENIED_REASON_Denied and ACCESS_DENIED_REASON_Invalid will generate permanent failures.

The presence of any other value in the SMS Access Denied field will generate a transient failure.

Here is an example configuration of the IS41 sub-section of the RIMS section. IS41 = {

MdnMinTranslation = [ { fromNoa=306, prefix="3", min=4, max=32, remove=2, prepend="1111" } { fromNoa=0, prefix="00", min=4, max=32, remove=0, prepend="" } { fromNoa=0, prefix="0", min=1, max=32, remove=1, prepend="0032" } { fromNoa=0, prefix="", min=1, max=6, remove=0, prepend="" } { fromNoa=0, prefix="", min=1, max=32, remove=0, prepend="0032" } { fromNoa=1, prefix="", min=1, max=32, remove=0, prepend="00" } { fromNoa=2, prefix="", min=1, max=32, remove=0, prepend="0032" }

] GT = "" PC = 17 SSN = 8 checkCacheForTcap = false supportIS841 = false minHLRTransType = 3 mdnHLRTransType = 14

}

Here are the IS41 configuration parameters.

Note: GT, PC and SSN form the address used by Messaging Manager Navigator when consulting IS41 HLR.


Introduction

MIN store location VMSC store location

IS41 Errors

Example IS41 config

IS41 parameters


IS41, Continued


IS41 parameters (continued)

MdnMinTranslation

Syntax: MdnMinTranslation = [ {

<number normalisation rules parameters> } ...

]

Description: Translates an MDN to MIN. Type: Array Notes: This parameter uses Number Normalisation rules to perform

the translation. For information about the Number Normalisation parameters shown in the example below, see the MMX Technical Guide.

Example: MdnMinTranslation = [ {

fromNoa = 0, prefix = "3">, min = 4, max = 32, remove = 2, prepend = "0035"

} ...

]

GT

Syntax: GT = <num> Description: Originating Global Title used by the HLR to communicate

back to MMX or Messaging Manager Navigator (RIMS). Allowed Valid global title number Note: This parameter takes priority over PC or SSN match. Example: GT = "62912425346"

PC

Syntax: PC = <num> Description: Originating Point Code array of messages used by the HLR

to communicate back to MMX or Messaging Manager Navigator (RIMS).

Allowed Defined by Network Administrator Default: 0 Note: • This parameter takes priority over SSN match.

• To remove the point code from outgoing requests, set the PC value to 65535.

Example: PC = 17



IS41, Continued



SSN

Syntax: SSN = <num> Description: Originating Subsystem Number of the messages used by

HLR to communicate back to MMX or Messaging Manager Navigator (RIMS).

Allowed Valid sub system number. Note: Example: SSN = 9

checkCacheForTcap

Syntax: checkCacheForTcap = <bool> Description: Determines whether the RIMS cache will be checked for

IS41 SMSReq messages. Type: Boolean Allowed: true, false Default: false Example: checkCacheForTcap = false

supportIS841

Syntax: supportIS841 = <bool> Description: Determines whether to send the MDN to the HLR, if there is

an MDN available, rather than perform the conversion. Type: Boolean Allowed: true, false Default: false Notes: If set to true, HLR lookups will be used in preference to

MdnMinTranslation. Example: supportIS841 = false

minHLRTransType

Syntax: minHLRTransType = <num> Description: The Global Title translation type to be used for lookups to the

HLR when using an MIN. Allowed Default: 3 Note: Example: minHLRTransType = 3



IS41, Continued



mdnHLRTransType

Syntax: mdnHLRTransType = <num> Description: The Global Title translation type to be used for lookups to the

HLR when using an MDN. Allowed Default: 14 Note: Example: mdnHLRTransType = 14



Caching Messaging Manager Navigator is a SLEE component which provides HLR lookup and caching. This component communicates with other SLEE components using the predefined RIMS protocol or MAP/IS-41 HLR lookups over TCAP.

Messaging Manager Navigator caches the results of the HLR queries. This information should be retained for different periods of time depending on its type (a real result, or a failure of some kind) and which network it belongs to.

The primary input of information to the RIMS cache is from the Messaging Manager Navigator HLR query responses, however it is possible to update the RIMS cache from other processes. This is useful for such things as invalidating any cached entry when a MAP-ALERT-SERVICECENTRE message is received, reinvigorating the cached entry when a delivery using that information works, or updating the VMSC based on incoming calls.

The RIMS cache has indexes over the MSISDN/MDN and IMSI/MIN for the same data, although both point to the same information.

There are a number of things that is done to the cache data.

• Look up existing entries. • Add new entries. • If the cache is full, expire the oldest entries. • Update existing entries.

Note: When a new element is added to the cache, its validity period is set from the configuration. The configuration is only consulted when an item is added, not every time it is updated.

A validity period of 00:00:00 means that an entry should not be added to the cache. If an element is not added to the cache for this reason, the update function (used for both additions and updates) will return false as though it already contained more relevant data for that key.

Here is an example configuration of the cache section of RIMS. RIMS = {

cache = { size = 5000000 defaultSuccessValidityPeriod = “01:00:00” defaultTransientFailureValidityPeriod = “00:30:00” defaultPermanentFailureValidityPeriod = “04:00:00” successValidityPeriods = {

{ prefix = “027”, period = “01:30:00” } { prefix = “021”, period = “00:45:00” }

} transientFailureValidityPeriods = {

{ prefix = “027”, period = “00:15:00” } } permanentFailureValidityPeriods = {

{ prefix = “027”, period = “03:00:00” } }

} }

Here are the Cache configuration parameters


Introduction

Cache operations

Example caching config

Cache parameters


Caching, Continued


Cache parameters (continued)

size

Syntax: size = <int> Description: Maximum number of HLR responses to cache at any one

time. Allowed Note: Value specified in bytes. Example: size = 100

defaultSuccessValidityPeriod

Syntax: defaultSuccessValidityPeriod = <time> Description: Lifetime of successful results not covered by a specific

IMSI/MIN prefix. Allowed HH:MM:SS Note: Example: defaultSuccessValidityPeriod = "00:01:00"

defaultTransientFailureValidityPeriod

Syntax: defaultTransientFailureValidityPeriod = <time>

Description: Lifetime of transient failure results not covered by a specific IMSI/MIN prefix.

Allowed HH:MM:SS Note: Example: defaultTransientFailureValidityPeriod =

"00:00:10"

defaultPermanentFailureValidityPeriod

Syntax: defaultPermanentFailureValidityPeriod = <time>

Description: Lifetime of permanent failure results not covered by a specific IMSI/MIN prefix.

Allowed HH:MM:SS Note: Example: defaultPermanentFailureValidityPeriod =

"00:00:30"

successValidityPeriods

Syntax: successValidityPeriods = <time> Description: Success validity period set per IMSI/MIN prefix. Allowed HH:MM:SS Note: Example: successValidityPeriods = "00:00:30"



Caching, Continued


Cache parameters (continued)

transientFailureValidityPeriods

Syntax: transientFailureValidityPeriods = <time> Description: Transient failure validity period set per IMSI/MIN prefix. Allowed HH:MM:SS Note: Example: transientFailureValidityPeriods = "00:00:30"

permanentFailureValidityPeriods

Syntax: permanentFailureValidityPeriods = <time> Description: Permanent failure validity period set per IMSI/MIN prefix. Allowed HH:MM:SS Note: Example: permanentFailureValidityPeriods = "00:00:30"



Chassis Actions The RIMS config includes a ChassisActions sub-section.

Here is an example configuration of the ChassisActions sub-section of the RIMS section.

ChassisActions = { RimsChassisAction = {

rimsInterfaceName = "rimsIf" TON = "001" NPI = "001" allowGPRS = true timeout = 3 timeoutTick = 3

} }

Here are the parameters in the RimsChassisAction sub-section of the ChassisActions section of the eserv.config.

rimsInterfaceName

Syntax: rimsInterfaceName = <str> Description: Controls the interface that the chassis action creates a SLEE

dialog to. Allowed string - valid name of interface Default: "rimsIf" Note: Example: rimsInterfaceName = "rimsIf"

TON

Syntax: TON = <num> Description: Specifies the Type of Number value that will be filled into the

query key value, in the case that the query key to be used in one of the extension digits fields.

Allowed Values: • 000 = unknown • 001 = international • 002 = national • 003 = network_specific • 004 = subscriber_number • 005 = alphanumeric • 006 = abbreviated

Default: "001" Note: The TON should be set to the most likely TON for an MSISDN

or MDN, as it will be used as part of the query to Messaging Manager Navigator and the HLR.

Example: TON = "001"


Introduction

Example ChassisActions config

RimsChassisAction parameters


Chassis Actions, Continued


RimsChassisAction parameters (continued)

NPI

Syntax: NPI = <num> Description: Specifies the Number Plan Indicator value that will be filled

into the query key value, in the case that the query key to be used in one of the extension digits fields.

Allowed Values: • 000 = unknown • 001 = ISDN (E.163/E.164) • 003 = Data (X.121) • 004 = Telex (F.69) • 006 = Land mobile (E.212) • 008 = National • 009 = Private • 010 = ERMES • 013 = Point Code & subscriber number • 014 = Internet (IP) • 018 = WAP

Default: "001" Note: The NPI should be set to the most likely NPI for an MSISDN

or MDN, as it will be used as part of the query to Messaging Manager Navigator and the HLR.

Example: NPI = "001"

allowGPRS

Syntax: allowGPRS = <bool> Description: Determines whether the network supports GPRS. Type: Boolean Allowed: true, false Default: true Notes: MAP node specific parameter. Example: allowGPRS = true

timeout

Syntax: timeout = <sec> Description: Timeout if Messaging Manager Navigator does not reply. Allowed: seconds Example: timeout = 3



Chassis Actions, Continued


RimsChassisAction parameters (continued)

timeoutTick

Syntax: timeout = <sec> Description: The length of a timeout monitoring period. Minimum value is

1. Allowed: seconds Notes: Changing this value will change the timeout for all SLEE

based applications running on the same SLEE as Messaging Manager Navigator.

Example: timeout = 3



RIMS Nodes Overview

This chapter explains the RIMS macro nodes in depth.


RIMS Nodes Use Cases ............................................................................... 20 Available Feature Nodes ............................................................................... 21

Chapter 3

Introduction

In this chapter



RIMS Nodes Use Cases In order to retrieve the requested values from Messaging Manager Navigator and store them in the chassis and engine fields, each node has two states.

• The first state sets up an xmsRimsChassisAction and passes the data needed to generate the RIMS query message.

• The second state receives information determining which exit branch to take from the chassis action.

The only difference between the MAP and IS41 nodes are the data fields in the GUI that will be used to populate the query message, thus the following section will apply to both MAP and IS41 nodes unless specified.

The first state in each node will construct an xmsRimsChassisAction and send it the node data needed to construct the RIMS query message.

The node will then set the next state to be State 2, and will return ACS_ENGINE_MACRO_STAY_HERE, passing control to ACS until a response is received.

The second state of the node will be entered once the xmsRimsChassisAction has determined the validity of the response message from RIMS, and stored the values in the chassis and engine contexts if they are successful. The chassis action will return an enum denoting which exit branch the node should take based on this.

Therefore, all the second state will need to do is follow the specified exit branch.

Introduction

Query

Response



Available Feature Nodes This topic lists all the Feature Nodes (available in the Feature Set called RIMS) that are available to Messaging Manager Navigator within the Call Plan Editor. In some cases, additional nodes may have been created and installed to fit a specific customer need. These custom (and ACS) nodes do not appear in this list.

This table lists all the available RIMS feature nodes.

Node name Node icon Node description Reference IS41 RIMS Query

Supports IS-41 messages and queries the IMSI/MIN or IMSI/MIN & VMSC/SGSN address of any ACS number field.

IS41 RIMS Query (on page 22)

MAP RIMS Query

Supports MAP messages and queries the IMSI/MIN or IMSI/MIN & VMSC/SGSN address of any ACS number field.

MAP RIMS Query (on page 25)

Introduction

Node list



IS41 RIMS Query The IS41 RIMS Query node supports IS-41 messages and queries the IMSI/MIN or IMSI/MIN & VMSC address of any MDN stored in an ACS number field.

The results can then be placed into ACS chassis and engine parameters.

This node allows you to overide the SCCP Destination address digits used by the RIMS interface when sending IS41 SMSRequest messages to the HLR. The SCCP Calling Party address can also be overidden, allowing different addresses to be selected inside the control plan.

This node has one entry point and five exits that are set by the system. The number of exit points is fixed and may not be edited by the user.

Exit Cause Description 1 Success Query was successful.

2 Transient Failure A transient failure status was returned.

3 Permanent Failure

A permanent failure status was returned.

4 Node Failure General case for an unhandled state in this node. 5 RIMS Timeout Response time exceeded timeout.

The HLR SCCP Address area in this node specifies a full SCCP Destination address, not just the prefix. Therefore, this node is expected to be used in conjunction with, and after a Copy and/or a Modify node when a composite address is required by the control plan, for example, prefix + MDN.

This node may be used any number of times within a control plan.


Node description

Node icon

Node exits

Restrictions


IS41 RIMS Query, Continued


Here is an example Configure IS41 RIMS Query screen.

Follow these steps to edit the node.

Step Action 1 Select the value in MDN source to query to send as the MDN key in the

query message to RIMS.

2 In the Party for Results area, select the option to store the values in the response from RIMS in either calling or called engine and chassis fields.

3 In the Type of Query area, select the return option to control the contents of the requested results field in the query message.


Configuration screen

Configuring the node


IS41 RIMS Query, Continued


Configuring the node (continued)

Step Action 4 In the HLR SSCP Address area, tick the Override check box to optionally

edit the following fields: • Digits Location: the profile block where the global title SCCP

Destination address digits are stored. • Digits Field: the profile tag where the global title SCCP Destination

address digits are stored. • Translation Type: the translation type applicable to this global title.

Note: This area is used to specify the SCCP Destination address digits for the RIMS interface to use while sending IS41 SMSRequest messages to the HLR. This will be based on the data stored in the profile.

5 In the SCCP Calling Party area, select from the drop down list the Return Address of the SCCP originating address. This field is populated from the scf parameter in the sms.html file and the acs.conf file. For more information about this parameter, see ACS Technical Guide.

Note: It is recommended to select the Return Address value as Default. The default value is configured in the RIMS.IS41 section of the eserv.config file.

6 Click Save.



MAP RIMS Query The MAP RIMS Query node supports MAP messages and queries the IMSI/MIN or IMSI/MIN & VMSC/SGSN address of any MDN stored in an ACS number.

The results can then be placed into ACS chassis and engine paramters.

This node allows you to overide the SCCP Destination address digits used by the RIMS interface when sending MAP SendRoutingInfoForSM messages to the HLR. The SCCP Calling Party address can also be overidden, allowing different addresses to be selected inside the control plan.

This node has one entry point and six exits that are set by the system. The number of exit points is fixed and may not be edited by the user.

Exit Cause Description 1 Success - VMSC VMSC, or only the IMSI, are successfully returned.

2 Success - SGSN SGSN successfully returned.

3 Transient Failure A transient failure status was returned.

4 Permanent Failure

A permanent failure status was returned.

5 Node Failure General case for an unhandled state in this node. 6 RIMS Timeout Response time exceeded timeout.

The HLR SSCP Address area in this node specifies a full SCCP Destination address, not just the prefix. Therefore, this node is expected to be used in conjunction with, and after a Copy and/or a Modify node when a composite address is required by the control plan, for example, prefix + MSISDN.

This node may be used any number of times within a control plan.


Node description

Node icon

Node exits

Restrictions


MAP RIMS Query, Continued


Here is an example Configure Map RIMS Query screen.

Follow these steps to edit the node.

Step Action 1 Select the value in MSISDN source to query to send as the MSISDN key in

the query message to RIMS.

Note: If you select an IMSI, RIMS will treat this value as an MSISDN and may return a non-intuitive number.

2 In the Party for Results area, select the option to store the values in the response from RIMS in either calling or called engine and chassis fields.


Configuration screen

Configuring the node


MAP RIMS Query, Continued


Configuring the node (continued)

Step Action 3 In the Type of Query area, select the return option to control the contents

of the requested results field in the query message.

Note: If you select the Return IMSI and SGSN/MSC address option, but only the VMSC address is returned, the exit branch used will be "Success - VMSC".

4 Tick the Priority Request check box if you wish to set RIMS query message to priority, rather than normal.

5 In the HLR SSCP Address area, tick the Override check box to optionally edit the following fields: • Digits Location: the profile block where the global title SCCP DEST

address digits are stored. • Digits Field: the profile tag where the global title SCCP DEST

address digits are stored. • Translation Type: the translation type applicable to this global title.

Note: This area is used to specify the SCCP Destination address digits which the RIMS interface will use while sending MAP SendRoutingInfoForSM messages to the HLR. This will be based on the data stored in the profile.

6 From the SCCP Calling Party area, select from the drop down list the Return Address of the SCCP originating address. This field is populated from the scf parameter in the sms.html file and the acs.conf file. For more information about this parameter, see ACS Technical Guide.

Note: It is recommended to select the Return Address value as Default. The default value is configured in the RIMS.MAP section of the eserv.config file.

7 Click Save.



Background Processes Overview

This chapter explains the background processes that run for Messaging Manager Navigator.


Statistics ........................................................................................................ 30

Chapter 4

Introduction

In this chapter



Statistics Messaging Manager Navigator gathers statistics when it receives queries, for example from MMX, and when it sends requests to the HLR.

When Messaging Manager Navigator can't respond to a query from its internal cache, it will ask the HLR for information using:

• in the case of GSM MAP, a SendRoutingInfoForSM request; or • in the case of IS-41 and IS841, an SMSequest.

Messaging Manager Navigator statistics are generated by each SCP, and then transferred at periodic intervals to the Service Management Platform (SMP) for permanent storage and analysis.

An existing statistics system (smsStats) provides functions for the collection of basic statistical events. This is provided in the Oracle SMS application. Refer to the SMS Technical Guide for details.

The incidence of 12 separate events are counted, classified under the following names.

SMS_SET_ROUTING_INFO Incremented when Messaging Manager Navigator receives a RIMS update request.

SMS_GET_ROUTING_INFO Incremented when Messaging Manager Navigator receives a RIMS query request.

SMS_GET_ROUTING_INFO_SUCCESS Incremented when Messaging Manager Navigator returns a RIMS response with the status of 'successful'.

SMS_GET_ROUTING_INFO_FAIL Incremented when Messaging Manager Navigator returns a RIMS response with a status other than 'successful'.

SMS_MAP_SRI_SM_ATTEMPT Incremented whenever Messaging Manager Navigator attempts to send a MAP SendRoutingInfoForSM message to the HLR.

SMS_MAP_SRI_SM_TEMP_ERR Incremented when Messaging Manager Navigator receives a transient error response to a MAP SendRoutingInfoForSM message.

SMS_MAP_SRI_SM_PERM_ERR Incremented when Messaging Manager Navigator receives a permanent error response to a MAP SendRoutingInfoForSM message.

SMS_MAP_SRI_SM_TIMEOUT Incremented whenever Messaging Manager Navigator waits too long for a response to a MAP SendRoutingInfoForSM message.

SMS_IS41_SMSREQ_ATTEMPT Incremented whenever Messaging Manager Navigator attempts to send an IS-(8)41 SMSRequest message to the HLR.


Introduction

Statistics gathered


Statistics, Continued


Statistics gathered (continued)

SMS_IS41_SMSREQ_TEMP_ERR Incremented whenever Messaging Manager Navigator receives a transient error response to an IS-(8)41 SMSRequest message.

SMS_IS41_SMSREQ_PERM_ERR Incremented whenever Messaging Manager Navigator receives a permanent error response to an IS-(8)41 SMSRequest message.

SMS_IS41_SMSREQ_TIMEOUT Incremented whenever Messaging Manager Navigator has to wait too long for a response to an IS-(8)41 SMSRequest message.



Troubleshooting Overview

This chapter explains common troubleshooting procedures and problem symptoms.

If the problem is not solved after consulting this chapter, contact Level 1 support. You will be asked to describe the failure in detail, together with any error messages that may have been displayed at the time of failure.


Common Troubleshooting Procedures ......................................................... 34

Chapter 5

Introduction

In this chapter



Common Troubleshooting Procedures This topic provides instructions for completing common troubleshooting procedures.

You can check which processes are running using the standard UNIX command: ps. To find processes being run by Oracle software, you can grep for the string 'oper', which will display all processes being run by the application operator accounts (for example, acs_oper, ccs_oper and smf_oper).

Note: Some processes which are required for proper functioning may be run by other users, including root or the user which runs the webserver. Example command: ps -ef | grep oper

For more information about the ps command, see the system documentation for the ps command.

You can also check how much of the processor a process is using by running the standard UNIX tool: top. If you have some baseline measurements, you will be able to compare it with the current load.

Example command: top

Tip: Some processes should only have one instance. If there are two or more instances, this may indicate a problem. For example, there will usually only be one timerIF running on each UAS. For more information about which processes should be running on each node, check the Process List for each node in Installation.

You can check whether a process is restarting using the SMS Alarms subsystem.

Processes raise alarms when they are stopped or started. The alarms include:

• their name • the time the alarm was logged, and • some other information about why the event may have occurred.

Further information about the specific alarm can be found in either the:

• System Alarms chapter of the application's Technical Guide, or • application's Alarms Guide.

Alarms can be accessed from:

• the syslog on the local machine and the USMS(s), and • the Alarms tab in the SMS Alarms Management screen.

For more information about the syslog, see SMS Technical Guide.

For more information about the Alarms Management screen, see SMS User's Guide.

To check the details of an installed package, use the pkginfo command.

Example command: pkginfo -l smsSms

Example output: This is an example of the output of the example command above. PKGINST: smsSms NAME: Oracle smsSms CATEGORY: application ARCH: sun4u


Introduction

Checking current processes

Process failure

Checking installed packages


Common Troubleshooting Procedures, Continued


Checking installed packages (continued)

VERSION: 3.1.0 VENDOR: Oracle PSTAMP: smsNode20041020104925 INSTDATE: Oct 20 2004 13:15 EMAIL: [email protected] STATUS: completely installed FILES: 348 installed pathnames 39 directories 89 executables 152448 blocks used (approx)

For more information about the pkginfo utility, see the system documentation.

A number of services and functions rely on access to the Oracle database. To check that Oracle is available to a service, check the following:

1 Use sqlplus to check that you can log into Oracle with the username and password the service is using to connect (these can usually be found in the service's configuration file). Example command: sqlplus smf/smf

2 Where the tables required for a service are known, use SQL queries to check that: the tables exist, and they have appropriate content.

For more information about SQL queries, see the Oracle documentation.

Network connectivity will affect any process which requires communication between two different network addresses.

Network connectivity should support ssh sessions between the two machines experiencing the problem.

If you can open an ssh session between the two machines, check the following before contacting Level 1 support with details:

• If the address of either of the machines specified in the Node Management screens is a hostname, check that the hostnames used in the ssh sessions are the hostnames specified in the Node Management screen.

If you cannot ssh, check the following before contacting Level 1 support with details:

• Check that the hostname is resolving correctly in the DNS. • Check that the physical network connection is working correctly. • Check that the inetd and sshd are running. • Check that sshd is listening on the expected port. • Check that the smf_oper and acs_oper accounts are not locked, and that the

username and password combinations being used are correct.


Checking Oracle

Checking network connectivity


Common Troubleshooting Procedures, Continued


Replication may be failing for the following reasons:

• ssh keys have not been correctly set up between origin and destination machines.

• The destination node has been incorrectly set up in the Node Management screens of the SMS Java screens.

• Oracle is not running correctly. • A new replication.cfg file has not been created after a change. • replication.cfg may not be successfully copying to the destination machine (an

error should display when the Create Config File button on the Node Management screens is clicked).

• The partition on the destination machine where the data is being replicated to may be full.

• The updateLoader on the destination machine may be running incorrectly. • The destination database may be substantially out of sync with the SMF. Run

a resync.

One of the significant areas where faults can occur and be remedied is in the configuration of processes. Configuration files can be edited by any standard text editor. A backup of the existing configuration file should always be taken before editing a configuration file.

For more information about the configuration files used in this application, see Configuration.

For more information about the configuration file for a specific program or tool, see the section named after the binary in question.

Replication

Checking configuration files



System Alarms Overview

This chapter explains the alarms which may be generated by the application, probable causes and recommended responses.


Alarm Topic Description ................................................................................ 38 RIMS Alarms ................................................................................................. 40

Chapter 6

Introduction

In this chapter



Alarm Topic Description Alarms on each configured node are written to the syslog and are then captured by the smsAlarmDaemon for entry in the SMF database.

For management of these alarms, refer to the SMS Technical Guide.

This table describes the alarms severity levels.

Level Abbr Description Critical C These alarms are raised when the application has encountered

an error which indicates that the system is unable to function.

Error E These alarms indicate the application has encountered a serious problem completing a necessary task and could not complete the task.

Warning W Warnings are raised to indicate the application encountered a problem completing a non-mission critical task.

Notice N Notices are raised to indicate that the application has completed a task successfully.

Alarms usually follow this format: Mon DD 24:MM:SS <hostname> <process name>: [ID <alarmID> user.<severity>] <process>(PID) <SEVERITY>: <Alarm text with possible variables>

Where:

Variable Description Mon DD Month and date the alarm was logged.

24:MM:SS Time the alarm was logged in 24 hour format.

hostname Name of the machine on which the alarm was generated.

process name Name of the process which logged the alarm.

alarmID ID number of the alarm.

severity Alarm severity.

process Name of the process which logged the alarm.

PID Process ID of the process which logged the alarm.

SEVERITY Alarm severity. Alarm text Alarm text. This may include variables such as node number.

Note: In some cases the entire alarm text is generated from variables.

Note: Some alarms from some subsystems may have a different format. Example: This text shows an smsMaster alarm about pending update queues. Mar 30 13:34:54 prodsmp1 smsMaster: [ID 953149 user.warning] smsMaster(17833) WARNING: Pending queue now above 15 (Worst Node 317)


Alarm generation

Severity levels

Alarm format


Alarm Topic Description, Continued


The %d and %s symbols represent variables within the alarm text. These values are generated by the subsystem and added to the message when the alarm is raised.

Usually the %d is a number and the %s is text in the context of the message to complete the alarm message. Occasionally other % symbols are also used (e.g. %u) for different variables.

For more information about the SMS Alarms subsystem, see the SMS Technical Guide.

For more information about creating and maintaining the SMS Alarm Relay rule set, see the SMS User's Guide.

Alarm text and variables

Further information



RIMS Alarms This table defines the critical error messages for Messaging Manager Navigator.

Alarm Text Reason Remedy Config File error: '%s'

There is an error in the eserv.config file; the full text of the alarm should provide details.

Correct the config file and restart the SLEE.

Could not initialise RIMS interface.

An error occurred during RIMS initialisation.

Check the RIMS log for more detail.

Failed to open RIMS section in config file.

eserv.config file does not contain a RIMS section.

Add necessary section to the config file.

One of Global Title (GT) or Point Code/Subsystem Number (PC/SSN) must be specified.

Missing parameters in the config file. Add GT or PC to eserv.config.

Reloading configuration failed.

An error occurred during RIMS configuration.

The eserv.config file contains an error.

This table defines the error messages for Messaging Manager Navigator.

Alarm Text Reason Remedy Cache configuration invalid.

Misconfiguration detected. Correct eserv.config file.

CacheElement::isValid unable to call gettimeofday

problem accessing standard c functions

Contact Oracle support.

Cannot get SLEE event types (Management=%p,TCAP=%p,RIMS=%p).

Misconfiguration detected. Check that you have a valid SLEE interface name configured.

Cannot get SLEE Interface API handle.

SLEE resource shortage. Contact Oracle support.

Cannot install SIGHUP handler - %s [%d].

Failed to install signal handler. Contact Oracle support.

Cannot install SIGUSR1 handler - %s [%d].

Failed to install signal handler. Contact Oracle support.

Can't respond to RIMSQuery: SLEE dialog is NULL.

One of our SLEE dialogues was closed unexpectedly.


Can't send protocolFailure status to RIMS client: no SLEE dialog.

One of our SLEE dialogues was closed unexpectedly.


Can't send protocolFailure status to RIMS client: send failed.

Problem allocating SLEE resources. Contact Oracle support.


Critical

Error


RIMS Alarms, Continued


Error (continued)

Alarm Text Reason Remedy CdmaTransaction cannot handle unknown teleservice %d.

RIMS asked to perform an IS41 query without a teleservice ID.


CdmaTransaction couldn't extract TCAP component from HLR response for MDN '%s'.

HLR Response does not contain correct primitive.

Check configuration of the HLR, contact Oracle support.

CdmaTransaction couldn't extract TCAP component from HLR response for MIN '%s'.



CdmaTransaction couldn't retrieve SMSAddress from SMSREQ result for MDN '%s'.

HLR Response was correct except for a missing SMSC address.


CdmaTransaction couldn't retrieve SMSAddress from SMSREQ result for MIN '%s'.



CdmaTransaction received %s while expecting TCAP_RESPONSE(TC_RESULT_L) for MDN '%s'.

The HLR responded to a IS41 message with an unexpected TCAP primitive.

Investigate the TCAP messages between RIMS and the HLR; contact Oracle support.

CdmaTransaction received %s while expecting TCAP_RESPONSE(TC_RESULT_L) for MIN '%s'.

The HLR responded to a IS41 message with an unexpected TCAP primitive.


CdmaTransaction received invalid SLEE event.

Misconfiguration detected. Check SLEE.cfg file

CdmaTransaction received invalid TCAP primitive.



CdmaTransaction received TCAP_ABORT(%d) from HLR for MDN '%s' using teleservice %d. abortCause set to %d

The HLR responded to an IS41 message with a TCAP ABORT.


CdmaTransaction received TCAP_ABORT(%d) from HLR for MIN '%s' using teleservice %d.

The HLR responded to an IS41 message with a TCAP ABORT.






Error (continued)

Alarm Text Reason Remedy CdmaTransaction received TCAP_NOTICE from HLR for MDN '%s' using teleservice %d.

The HLR responded to an IS41 message with a TCAP NOTICE.

nvestigate the TCAP messages between RIMS and the HLR; contact Oracle support.

CdmaTransaction received TCAP_NOTICE from HLR for MIN '%s' using teleservice %d.

The HLR responded to an IS41 message with a TCAP NOTICE.


CdmaTransaction received unreadable response for MDN '%s'.



CdmaTransaction received unreadable response for MIN '%s'.



Couldn't send SLEE event on dialog %x.

SLEE communication attempt failed. Contact Oracle support.

dt_add: Require appID, statID, statInfo all non-NULL

An internal statistics function call has passed invalid parameters.


dt_add: Require appID, statID, statInfo all non-zero len



dt_find: Require appID, statID, statInfo all non-NULL



Exception reloading config file: %s

The configuration file contains an error.

Examine the log file for more detail of the error.

File not found when reloading config file %s

RIMS is unable to find the config file. Check the location of the file at $ESERV_CONFIG_FILE

MAP.defaultMapVersionToHlr must be 1, 2 or 3.

Misconfiguration detected. Correct eserv.config file.

MapTransaction cannot perform HLR query: no MSISDN available for IMSI '%s'.

RIMS has been asked to perform an HLR lookup without access to all necessary information.


MapTransaction failed: No components in TCAP primitive.



MapTransaction received MAP-OPEN with unrecognised Application-Context-Name.

RIMS received a MAP-OPEN where it was unable to decipher the mapVersion.






Error (continued)

Alarm Text Reason Remedy MapTransaction received TCAP_U_ERROR (%d).

HLR lookup failed. Check configuration of the HLR, contact Oracle support.

MapTransaction received unexpected MAP-OPEN.

RIMS received a MAP-OPEN that was not an alertServiceCentre.


MapTransaction: HLR MAPv1 SRI-SM response did not contain an MSC address.



MapTransaction: HLR MAPv2 SRI-SM response did not contain an MSC or SGSN address.



MapTransaction: HLR requested fallback using an unrecognised Application Context Name.

RIMS didn't recognise the MAP application context the HLR requested.


MapTransaction: MAPv1 HLR result component is not an SRI-SM result.









MapTransaction: Received bad TCAP component type %d.

HLR lookup failed. Check configuration of the HLR, contact Oracle support.

MapTransaction: Received SLEE TCAP event with no primitive.

SLEE communication attempt failed. Check test tool configuration, contact Oracle support.

MapTransaction: Received TCAP_ABORT(%s) from HLR.

The HLR responded to a MAP message with a TCAP ABORT.


MapTransaction: received TCAP_NOTICE from HLR.

The HLR responded to a MAP message with a TCAP NOTICE.






Error (continued)

Alarm Text Reason Remedy No appropriate key present in RIMS update message.

RIMS asked to perform lookup without an MSISDN or IMSI


No cache configuration found.

Missing parameters in the config file Add the RIMS.cache section to eserv.config

Reattached to shmKey %d. Lost stats on %d calls

The shared memory segment used by the smsStatsDaemon had become unavailable, and is now available again. A number of statistics values have been lost.

Check for a problem with the smsStatsDaemon.

RIMS cannot route incoming TCAP event to any existing transaction (primitive type %d).

RIMS transaction to handle the incoming event does not exist.


RIMS protocol error: Bad message type %d

RIMS event badly formatted. Contact Oracle support.

RIMS protocol error: Bad protocol type %d


RIMS protocol error: CDMA query requests SGSN.


RIMS protocol error: CDMA query requires MIN or MDN key.

RIMS asked to perform query without an MDN or MIN


RIMS protocol error: IS41 parameters requested by MAP query.


RIMS protocol error: MAP parameters requested by IS41 query.


RIMS protocol error: MAP query requests SGSN but does not allow GPRS.

RIMS received an update with a contradiction.


RIMS protocol error: MAP query requires MSISDN or IMSI key.

RIMS asked to perform query without an MSISDN or IMSI.


RIMS protocol error: MAP update sets SGSN but does not allow GPRS.

RIMS received an update with a contradiction.






Error (continued)

Alarm Text Reason Remedy RIMS SLEE interface requires 'tcapInterfaceServiceKey'.

Missing parameters in the config file. Add tcapInterfaceServiceKey to eserv.config.

shmAttach: Cannot attach to shmKey %d

A problem has occurred attempting to attach the shared memory segment used by the smsStatsDaemon.

Check that the smsStatsDaemon is running without errors. If necessary, restart the smsStatsDaemon. Check that the system settings for shared memory and semaphores have been set to recommended levels.

shmAttach: Cannot get semID from semKey %d



shmAttach: Cannot get shmKey from semID %d



shmAttach: Error %d getting INODE for %s



smsRetrieveStats: Cannot attach to SHM







Error (continued)

Alarm Text Reason Remedy smsRetrieveStats: Cannot reattach to SHM



smsSetStats: Could not retrieve '%s.%s'

A problem has occurred attempting to dettach the shared memory segment used by the smsStatsDaemon.


smsTryRecordStats: Cannot attach to SHM



smsTryRecordStats: Cannot reattach to SHM



smsTryRecordStats: Internal error updating '%s.%s'



smsTryRecordStats: Memory state not VALID - giving up

The indicated statistics value could not be written. This is a system error, not just a missing statistics entry problem.






Error (continued)

Alarm Text Reason Remedy smsTrySetStats: Internal error retrieving '%s.%s'



smsTrySetStats: Internal error updating '%s.%s'



Transaction couldn't create SLEE dialog to service key %d.

SLEE communication attempt failed. Check configured service keys in RIMS and SLEE config files.

Unable to allocate space for %d elements in Cache::config:

Not enough space for required cache size.

Lower the required cache size in eserv.config.

This table defines the warning messages for Messaging Manager Navigator.

Alarm Text Reason Remedy deltaCounter: Failed to delta statistic '%s.%s.%s'

Failed to increment a statistic counter.


Error detaching from smsStatsDaemon shm. %d (%s)

A problem has occurred attempting to dettach the shared memory segment used by the smsStatsDaemon.


getCounter: Failed to get value for statistic '%s.%s.%s'

Failed to look up a statistic counter. Contact Oracle support.

MapTransaction's HLR response arrived on dialog %x, expected %x.

RIMS has an internal dialog consistency error.


MDN (%s) too short, assuming that it is already a MIN

RIMS is receiving invalid MDN values in IS41 queries.



Warning




Warning (continued)

Alarm Text Reason Remedy out of memory No memory left on the SCP. Find the process using all the

memory and restart it. Received Unsupported EventType 0x%lu

Received a SLEE event that is not supported.


Request for fallback to bad MAP version %d, using version 3 instead.

Fallback request not completely understood, using MAP version 3.

No action required.

RIMS update operation invalid: no MDN specified.

RIMS asked to perform update without an IMSI.


RIMS update operation invalid: no MSISDN specified.

RIMS asked to perform update without an MSISDN.


setCounter: Failed to set statistic '%s.%s.%s'

Failed to set statistic. Contact Oracle support.

Terminated with INTERFACE_END

rims terminated after receiving an interface end management event.

No action required.

Terminated with INTERFACE_KILL

rims terminated after receiving an interface end management event.

No action required.

This table defines the notice messages for Messaging Manager Navigator.

Alarm Text Reason Remedy dt_add: Parent statistic '%s.%s' does not exist

The indicated statistics value could not be written. This typically indicates that the statistics value does not exist in the SMF_STATISTICS_DEFN table.

Check that SMF_STATISTICS_DEFN contains the indicated statistics value. Check for spelling errors. Restart the smsStatsDaemon if necessary.

Management Event REPORT_REQUEST

Event report request received. No action required.

Management Event REREAD_CONFIG

Event report request received. No action required.

out of memory No memory left on the SCP. Find the process using all the memory and restart it.

RIMS: cache.size = %lu New configuration loaded. No action required. RIMS: GT = '%s' New configuration loaded. No action required. RIMS: hlrTimeout= %d New configuration loaded. No action required. RIMS: MAP.defaultMapVersionToHlr = %d

New configuration loaded. No action required.


Notice




Notice (continued)

Alarm Text Reason Remedy RIMS: MAP.hlrErrorMap = %s


RIMS: PC = %u New configuration loaded. No action required. RIMS: sleepTime = %lu New configuration loaded. No action required. RIMS: SSN= %d New configuration loaded. No action required. RIMS: TcapInterfaceServiceKey = %d


smsRecordStats: Statistic not found '%s.%s'

The indicated statistics value could not be written. This typically indicates that the statistics value does not exist in the SMF_STATISTICS_DEFN table.

Check that SMF_STATISTICS_DEFN contains the indicated statistics value. Check for spelling errors. Restart the smsStatsDaemon if necessary.



Installation Overview

This chapter explains how to install the application.


Loading the Distribution File .......................................................................... 52 Installing the rimsScp Package ..................................................................... 53 Installing the rimsSms Package .................................................................... 56 Installing the rimsSms Package on a Cluster................................................ 59

Chapter 7

Introduction

In this chapter



Loading the Distribution File Before you can install the application packages, you must load them in an installation directory on the correct machines. This procedure copies and registers packages from the distribution file on to the system.

You must repeat this procedure on every machine. If your application packages have already been loaded, you do not have to complete this procedure.

This procedure copies the distribution file into the /tmp directory. The installation procedure assumes that the /tmp directory has been used.

Follow these steps to load the distribution file.

Step Action 1 Ensure you are logged onto the machine as root.

2 Copy the distribution file into the /tmp directory. The application's distribution file will be distributed on either CD or from an FTP location. If you do not either have a CD or know the correct FTP location, please contact your Oracle contact. The packages are often distributed in one large compressed file (for example, sms.tar.gz).

3 Check whether the distribution file is compressed (zipped). You can usually determine this by the file extension: .gz or .tgz will mean the file is compressed. Occasionally, the file extension will be incorrect, or the file will fail to uncompress or untar. If it is available, you can use the file command to attempt to determine the type of file by checking its contents. If the distribution file is: • not compressed, go to Step 4. • compressed, uncompress the file. Example commands: • gunzip <filename>, or • gzip –d <filename>

Where: <filename> is the distribution file

Result: This uncompresses the distribution file. 4 If the distribution file is:

• .pkg file, no further actions are required to load the distribution file. • a tar ball, untar the distribution. Example command: tar –xvf <filename> • Where:

<filename> is the uncompressed distribution file. Result: Untarring unzips the packages into the /tmp directory and will create an install sub-directory.

Introduction

Installation directory

Procedure



Installing the rimsScp Package Use this procedure to install the rimsScp package on to the Sun box.

This process automatically runs the post-install script on the SCP.

This procedure assumes that you have already installed the following packages and run any associated configuration scripts.

Package For more information, see... SLEE SLEE Technical Guide.

smsScp SMS Technical Guide.

smsSms SMS Technical Guide.

acsScp ACS Technical Guide.

acsSms ACS Technical Guide. acsCbScp ACS Convergent Billing Technical Guide.

Follow these steps to install the rimsScp package.

Step Action 1 Type pkgadd -d . rimsScp

Result: This step starts the package installation utility.

2 The package will request permission to install and execute scripts with super-user permissions, answer y (yes) to continue or n (no) to quit the installation process

3 When prompted, enter a password for the rim_oper user, and then reconfirm that password.

4 When prompted to install RIMS macro nodes, answer y. 5 The installation script will complete after a few minutes. No further

action is required.


Introduction

Before you begin

Procedure


Installing the rimsScp Package, Continued


The table below provides a sample of the text displayed during a rimsScp package install on an SCP.

Script Output Action pkgadd -d . rimsScp Type this command to start the

installation.

Processing package instance <rimsScp> from </volA/pkgs/RIMS> RimsScp Installation (sun4u) 1.0.0-pre-8 Oracle ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package.

Information only. No user action required.

Do you want to continue with the installation of <rimsScp> [y,n,?]

Type Y.

Installing RimsScp Installation as <rimsScp> ## Executing preinstall script. NOTE: Installing rimsScp into /IN/service_packages/RIMS NOTE: Creating account rim_oper ## Installing part 1 of 1. /IN/service_packages/RIMS/bin/rims /IN/service_packages/RIMS/lib/ckstr /IN/service_packages/RIMS/lib/ckyorn /IN/service_packages/RIMS/lib/cmnInstallLib.sh /IN/service_packages/RIMS/lib/librimsChassisActions.so /IN/service_packages/RIMS/lib/librimsMacroNodes.so /IN/service_packages/RIMS/rimsScp.conf.sh /IN/service_packages/RIMS/rimsScp.unconf.sh [ verifying class <none> ] ## Executing postinstall script. * Importing SMF environment variables. NOTE: Please enter a password for rim_oper in order to unlock the account for remote access.


New Password: Type the password.

Re-enter new Password: Type the password a second time.

passwd: password successfully changed for rim_oper

* Install the RIMS macro nodes? [y,n,?]

Type Y.


Sample script


Installing the rimsScp Package, Continued


Sample script (continued)

Script Output Action * NOTE: Adding RIMS to SLEE.cfg * rimsScp install complete Installation of <rimsScp> was successful.


On successful installation the rimsScp package will have installed the following binaries: IN/service_packages/RIMS/bin/RIMS

The following shared libraries will have been installed: /IN/service_packages/RIMS/lib/librimsChassisActions.so /IN/service_packages/RIMS/lib/librimsMacroNodes.so

Checking the installation



Installing the rimsSms Package Use this procedure to install the rimsSms package on to the Sun box, primary node in a cluster.

This process automatically runs the post-install script on the SMS.







Follow these steps to install the rimsSms package on an SMP, primary node in a cluster.

Step Action 1 Type pkgadd -d rimsSms

Result: This step starts the package installation utility.



4 When prompted to install ACS components, answer y.

5 Enter the SMF password as requested.

Note: If these are not known consult your System Administrator. 6 The installation script will complete after a few minutes. No further

action is required.


Introduction

Before you begin

Procedure


Installing the rimsSms Package, Continued


The table below provides a sample of the text displayed during a rimsSms package install on an SMP.

Script Output Action pkgadd -d . rimsSms Type this command to start the

installation.

Processing package instance <rimsSms> from </volA/pkgs/RIMS> RIMS (for SMS) Installation (sun4u) 1.0.0-pre-8 Oracle ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package.


Do you want to continue with the installation of <rimsSms> [y,n,?]

Type Y.

Installing RIMS (for SMS) Installation as <rimsSms> ## Executing preinstall script. NOTE: Installing rimsSms into /IN/service_packages/RIMS NOTE: Creating account rim_oper ## Installing part 1 of 1. /IN/html/Acs_Service/images/FNIS41RimsQuery.gif /IN/html/Acs_Service/images/FNMapRimsQuery.gif /IN/html/Acs_Service/images/PFNIS41RimsQuery.gif /IN/html/Acs_Service/images/PFNMapRimsQuery.gif /IN/html/rims.jar.sig


/IN/service_packages/RIMS/db/install/create/SMP/scripts/rims_drop_feature_node_set.sh .

.

.

/IN/service_packages/RIMS/lib/ckstr


Sample script


Installing the rimsSms Package, Continued



Script Output Action /IN/service_packages/RIMS/lib/ckyorn /IN/service_packages/RIMS/lib/cmnInstallLib.sh /IN/service_packages/RIMS/rimsSms.conf.sh /IN/service_packages/RIMS/rimsSms.unconf.sh [ verifying class <none> ] ## Executing postinstall script. * Importing SMF environment variables.

NOTE: Please enter a password for rim_oper in order to unlock the account for remote access.




Install the ACS components ? [y,n,?]

Type Y.

* Please enter the password for the SMF user on the SMF instance (default: SMF) [?]

If you are using: • the default password, press

Enter, • otherwise type the

password and press Enter

• * Please enter the password for the ACS_ADMIN user on the SMF instance

(default: ACS_ADMIN) [?]

If you are using: • the default password, press

Enter, • otherwise type the

password and press Enter * Creating /IN/service_packages/RIMS/.profile * RIMS statistics database updates were successfully installed. * RIMS node database updates were successfully installed. * rimsSms install is complete Installation of <rimsSms> was successful.


On successful installation the rimsSms package will have created the following directories: /IN/service_packages/RIMS /IN/service_packages/RIMS/lib /IN/service_packages/RIMS/tmp /IN/service_packages/RIMS/db




Installing the rimsSms Package on a Cluster Use this procedure to install the rimsSms package on to the Sun box, secondary & subsequent nodes in a cluster.

This process automatically runs the post-install script on the SMS.







Follow these steps to install the rimsSms package on an SMP cluster.

Step Action 1 Install the package on the primary node. See Installing the rimsSms

Package (on page 56).

2 Type pkgadd -d rimsSms Result: This step starts the package installation utility.



5 When prompted to install database, answer n.

6 When prompted to install ACS components, answer y.

7 Enter the SMF password as requested.

Note: If these are not known consult your System Administrator. 8 The installation script will complete after a few minutes. No further

action is required.


Introduction

Before you begin

Procedure


Installing the rimsSms Package on a Cluster, Continued


The table below provides a sample of the text displayed during a rimsSms package install on a SMP secondary node.

Script Output Action pkgadd -d . rimsSms Type this command to

start the installation.

Processing package instance <rimsSms> from </u01/share/pkg> RIMS (for SMS) Installation(sun4u) 3.1.1.1 Oracle ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package.


Do you want to continue with the installation of <rimsSms> [y,n,?]

Type Y.

Installing RIMS (for SMS) Installation as <rimsSms> ## Executing preinstall script. NOTE: Installing rimsSms into /IN/service_packages/RIMS NOTE: Creating account rim_oper ## Installing part 1 of 1. /IN/html/Acs_Service/images/FNIS41RimsQuery.gif /IN/html/Acs_Service/images/FNMapRimsQuery.gif /IN/html/Acs_Service/images/PFNIS41RimsQuery.gif /IN/html/Acs_Service/images/PFNMapRimsQuery.gif /IN/html/Rims_Service/helptext/English/124.gif /IN/html/Rims_Service <implied directory> /IN/html/Rims_Service/helptext <implied directory> /IN/html/Rims_Service/helptext/English <implied directory> /IN/html/Rims_Service/helptext/English/125.gif /IN/html/Rims_Service/helptext/English/1370.css

.

.

.

/IN/service_packages/RIMS/db/install/create/SMP/scripts/rims_uninstall_alarms.sh /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_install_statistics.sh /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_install_statistics.sql /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_remove_statistics.sh



Sample script





Script Output Action /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_remove_statistics.sql /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_statistics_defines.sql /IN/service_packages/RIMS/lib/ckstr /IN/service_packages/RIMS/lib/ckyorn /IN/service_packages/RIMS/lib/cmnInstallLib.sh /IN/service_packages/RIMS/rimsSms.conf.sh /IN/service_packages/RIMS/rimsSms.unconf.sh [ verifying class <none> ]

## Executing postinstall script. * Importing SMF environment variables. NOTE: Please enter a password for rim_oper in order to unlock the account for remote access.




* The database install only needs to be done if this is the primary node * of a cluster, or a non-clustered machine. * Install the database ?

[y,n,?] Type n.

* Install the ACS components ?

[y,n,?] Type y. * Creating /IN/service_packages/RIMS/.profile * Option to install database was not selected. RIMS statistics database updates have not been done. * Option to install database was not selected. RIMS nodes have not been configured. * rimsSms install is complete Installation of <rimsSms> was successful.

The rimsSms package has been successfully installed and configured. Note: Any other message will indicate a failed installation. Refer to the install log file for more information.





On successful installation the rimsSms package will have created the following directories: /IN/service_packages/RIMS /IN/service_packages/RIMS/lib /IN/service_packages/RIMS/tmp




Removal Overview

This chapter explains how to remove the application.


Un-installing the rimsSms Package .............................................................. 64 Un-installing the rimsScp Package ............................................................... 67

Chapter 8

Introduction

In this chapter



Un-installing the rimsSms Package The pkgrm utility will delete the entire package directory. Check the /IN/service_packages/RIMS directory for any files you wish to keep.

If you are storing any critical files there, move them before starting these procedures.

Follow these steps to remove the package rimsSms from the Sun machine.

Step Action 1 Log in as root. 2 Type pkgrm rimsSms

Result: This will remove this package and the configuration entries.

The table below provides a sample of the text displayed during a rimsSms package un-install on an SMP.

Script Output Action pkgrm rimsSms The following package is currently installed: rimsSms RIMS (for SMS) Installation (sun4u) 9.9.9

Type this command to start the un-installation.

Do you want to remove this package? [y,n,?,q] y ## Removing installed package instance <rimsSms> This package contains scripts which will be executed with super-user permission during the process of removing this package.

Type Y to continue.

Do you want to continue with the removal of this package [y,n,?,q] y ## Verifying package dependencies. ## Processing package information. ## Executing preremove script. * Importing SMF environment variables. * Please enter the password for the SMF user on the SMF instance

Type Y to continue.


Before you begin

Removing rimsSms

Sample script


Un-installing the rimsSms Package, Continued



Script Output Action (default: SMF) [?] smf * rimsSms statistics database updates were removed. * rimsSms node database updates were removed. * rimsSms uninstall is complete ## Removing pathnames in class <none> /IN/service_packages/RIMS/tmp /IN/service_packages/RIMS/rimsSms.unconf.sh /IN/service_packages/RIMS/rimsSms.conf.sh /IN/service_packages/RIMS/lib/cmnInstallLib.sh /IN/service_packages/RIMS/lib/ckyorn /IN/service_packages/RIMS/lib/ckstr /IN/service_packages/RIMS/lib <non-empty directory not removed>

Type the password

/IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_statistics_defines.sql /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_remove_statistics.sql /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_remove_statistics.sh /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_install_statistics.sql /IN/service_packages/RIMS/db/install/create/SMP/statistics/rims_install_statistics.sh /IN/service_packages/RIMS/db/install/create/SMP/statistics /IN/service_packages/RIMS/db/install/create/SMP/scripts/rims_install_feature_node_set.sh /IN/service_packages/RIMS/db/install/create/SMP/scripts/rims_feature_node_defines.sql /IN/service_packages/RIMS/db/install/create/SMP/scripts/rims_drop_feature_node_set.sh /IN/service_packages/RIMS/db/install/create/SMP/scripts /IN/service_packages/RIMS/db/install/create/SMP /IN/service_packages/RIMS/db/install/create

/IN/service_packages/RIMS/db/install <non-empty directory not removed> /IN/service_packages/RIMS/db <non-empty directory not removed> /IN/service_packages/RIMS <non-empty directory not removed> /IN/html/rims.jar.sig /IN/html/Rims_Service/helptext/English_Rims_Service.hs /IN/html/Rims_Service/helptext/English/toc.xml /IN/html/Rims_Service/helptext/English/tail.gif /IN/html/Rims_Service/helptext/English/tab_toc.htm /IN/html/Rims_Service/helptext/English/tab_index.htm /IN/html/Rims_Service/helptext/English/stylesheet.css /IN/html/Rims_Service/helptext/English/search.log /IN/html/Rims_Service/helptext/English/search.cfg /IN/html/Rims_Service/helptext/English/rimsnodemaprimsquery.jpg



Un-installing the rimsSms Package, Continued



Script Output Action /IN/html/Rims_Service/helptext/English/rimsnodeis41rimsquery.jpg /IN/html/Rims_Service/helptext/English/rimsconfiguremaprimsquery.jpg /IN/html/Rims_Service/helptext/English/rimsconfigureis41rimsquery.jpg /IN/html/Rims_Service/helptext/English/map.jhm /IN/html/Rims_Service/helptext/English/linespacer.jpg /IN/html/Rims_Service/helptext/English/index2.gif /IN/html/Rims_Service/helptext/English/index1.gif /IN/html/Rims_Service/helptext/English/index.xml /IN/html/Rims_Service/helptext/English/Oraclelogo.jpg /IN/html/Rims_Service/helptext/English/contents2.gif /IN/html/Rims_Service/helptext/English/contents1.gif /IN/html/Rims_Service/helptext/English/38.css /IN/html/Rims_Service/helptext/English/36.css /IN/html/Rims_Service/helptext/English/21166.htm /IN/html/Rims_Service/helptext/English/20638.htm

/IN/html/Rims_Service/helptext/English/20577.htm /IN/html/Rims_Service/helptext/English/20576.htm /IN/html/Rims_Service/helptext/English/20574.htm /IN/html/Rims_Service/helptext/English/1370.css /IN/html/Rims_Service/helptext/English/125.gif /IN/html/Rims_Service/helptext/English/124.gif /IN/html/Acs_Service/images/PFNMapRimsQuery.gif /IN/html/Acs_Service/images/PFNIS41RimsQuery.gif /IN/html/Acs_Service/images/FNMapRimsQuery.gif /IN/html/Acs_Service/images/FNIS41RimsQuery.gif ## Executing postremove script. NOTE: Removing user rim_oper NOTE: Removing /IN/html/Rims_Service ## Updating system information. Removal of <rimsSms> was successful.



Un-installing the rimsScp Package The pkgrm utility will delete the entire package directory. Check the /IN/service_packages/RIMS directory for any files you wish to keep.

If you are storing any critical files there, move them before starting these procedures.

Ensure that the SLEE is not running. For more information about stopping and starting the SLEE, see the SLEE Technical Guide.

Follow these steps to remove the package rimsScp from the Sun machine.

Step Action 1 Log in as root. 2 Type pkgrm rimsScp

Result: This will remove this package and the configuration entries.

The table below provides a sample of the text displayed during a rimsScp package un-install on an SCP.

Script Output Action pkgrm rimsScp The following package is currently installed: rimsScp RimsScp Installation (sun4u) 1.0.0-pre-9

Type this command to start the un-installation.

Do you want to remove this package? [y,n,?,q] y

Type Y to continue.

## Removing installed package instance <rimsScp> This package contains scripts which will be executed with super-user permission during the process of removing this package.

Do you want to continue with the removal of this package [y,n,?,q] y

Type Y to continue.

## Verifying package dependencies. ## Processing package information. ## Executing preremove script. * rimsScp uninstall is complete ## Removing pathnames in class <none> /IN/service_packages/RIMS/rimsScp.unconf.sh /IN/service_packages/RIMS/rimsScp.conf.sh /IN/service_packages/RIMS/lib/librimsMacroNodes.so /IN/service_packages/RIMS/lib/librimsChassisActions.so /IN/service_packages/RIMS/lib/cmnInstallLib.sh /IN/service_packages/RIMS/lib/ckyorn /IN/service_packages/RIMS/lib/ckstr /IN/service_packages/RIMS/lib


Before you begin

Removing rimsScp

Sample script


Un-installing the rimsScp Package, Continued



Script Output Action /IN/service_packages/RIMS/db/install <non-empty directory not removed> /IN/service_packages/RIMS/db <non-empty directory not removed> /IN/service_packages/RIMS/bin/rims /IN/service_packages/RIMS/bin <non-empty directory not removed> /IN/service_packages/RIMS <non-empty directory not removed> ## Executing postremove script. Note: Removing user rim_oper ## Updating system information. Removal of <rimsScp> was successful.



Appendix

Overview

This appendix contains the following topics.

Glossary of Terms ......................................................................................... 71 Index .............................................................................................................. 75

In this appendix



Glossary of Terms

Advanced Control Services configuration platform.

Code Division Multiple Access is a method for describing physical radio channels. Data intended for a specific channel is modulated with that channel's code. These are typically pseudo-random in nature, and possess favourable correlation properties to ensure physical channels are not confused with one another.

First Delivery Attempt

File Transfer Protocol - protocol for electronic transfer of files

General Packet Radio Service - employed to connect mobile cellular users to PDN (Public Data Network- for example the Internet).

Global System for Mobile communication.

It is a second generation cellular telecommunication system. Unlike first generation systems, GSM is digital and thus introduced greater enhancements such as security, capacity, quality and the ability to support integrated services.

Global Title.

The GT may be defined in any of the following formats: • Type 1: String in the form "1,<noa>,<BCD address digits>" • Type 2: String in the form "2,<trans type><BCD address digits>" • Type 3: String in the form "3,<trans type>,<num plan>,<BCD address digits>" • Type 4: String in the form "4,<trans type>,<num plan>,<noa>,<BCD address

digits>"

The contents of the Global Title are defined in the Q713 specification, please refer to section 3.4.2.3 for further details on defining Global Title.

The Home Location Register is a database within the HPLMN (Home Public Land Mobile Network). It provides routing information for MT calls and SMS. It is also responsible for the maintenance of user subscription information. This is distributed to the relevant VLR, or SGSN (Serving GPRS Support Node) through the attach process and mobility management procedures such as Location Area and Routing Area updates.

Home PLMN

International Mobile Subscriber Identifier. A unique identifier allocated to each mobile subscriber in a GSM and UMTS network. It consists of a MCC (Mobile Country Code), a MNC (Mobile Network Code) and a MSIN (Mobile Station Identification Number).

The IMSI is returned by the HLR query (SRI-SM) when doing FDA. This tells the MSC exactly who the subscriber is that the message is to be sent to.

Interim Standard 41 is a signaling protocol used in cellular telecommunications systems. It deals with the signalling between the MSC and other network elements for the purpose of handovers and roaming etc.

ACS

CDMA

FDA

FTP

GPRS

GSM

GT

HLR

HPLMN

IMSI

IS-41



Mobile Application Part - a protocol which enables real time communication between nodes in a mobile cellular network. A typical usage of the protocol would be for the transfer of location information from the VLR to the HLR.

Mobile Directory Number

Mobile Identification Number, also known as an MSID.

Messaging Manager.

Mobile Switching Centre. Also known as a switch.

Mobile Subscriber Identification, also known as an MIN.

Mobile Station ISDN number. Uniquely defines the mobile station as an ISDN terminal. It consists of three parts; the country code (CC), the national destination code (NDC) and the subscriber number (SN).

Mobile Terminated

Oracle Corporation

Point Code. The Point Code is the address of a switching point.

Public Land Mobile Network

Routing Information for Mobile Services. Used to cache HLR lookup information.

Note: Now known as "Messaging Manager Navigator".

Service Control Point. Also known as UAS.

Serving GPRS Support Node

Service Logic Execution Environment

Service Management Platform (also referred to as USMS).

Short Message Service.

Short Message Service Centre - stores and forwards a short message to the indicated destination subscriber number.

Service Number

Subsystem Number. An integer identifying applications on the SCCP layer.

Transaction Capabilities Application Part – layer in protocol stack, message protocol.

Universal Application Server - hardware on which applications run.

Visitor Location Register - contains all subscriber data required for call handling and mobility management for mobile subscribers currently located in the area controlled by the VLR.

MAP

MDN

MIN

MMX

MSC

MSID

MSISDN

MT

Oracle

PC

PLMN

RIMS

SCP

SGSN

SLEE

SMP

SMS

SMSC

SN

SSN

TCAP

UAS

VLR



Visited Mobile Switching Centre

Wireless Application Protocol. A standard designed to allow the content of the Internet to be viewed on the screen of a mobile device such as mobile phones, personal organisers and pagers. It also overcomes the processing limitation of such devices. The information and services available are stripped down to their basic text format.

VMSC

WAP



A About this Document

Audience • v Pre-requisites • v Related documents • v Scope • v

Alarm format Alarm Topic Description • 38

Alarm generation Alarm Topic Description • 38

Alarm text and variables Alarm Topic Description • 39

Alarm Topic Description Alarm format • 38 Alarm generation • 38 Alarm text and variables • 39 Further information • 39 Severity levels • 38

allowGPRS • 16 API • 40 Audience

About this Document • v Available Feature Nodes

Introduction • 21 Node list • 21

B Before you begin

Installing the rimsScp Package • 53 Installing the rimsSms Package • 56 Installing the rimsSms Package on a

Cluster • 59 Un-installing the rimsScp Package • 69 Un-installing the rimsSms Package • 66

C Cache operations

Caching • 12 Cache parameters

Caching • 12 Caching

Cache operations • 12 Cache parameters • 12 Example caching config • 12 Introduction • 12

CDMA • 2 Chassis Actions

Example ChassisActions config • 15 Introduction • 15 RimsChassisAction parameters • 15

checkCacheForTcap • 7, 10

C,(continued) Checking configuration files

Common Troubleshooting Procedures • 36 Checking current processes

Common Troubleshooting Procedures • 34 Checking installed packages

Common Troubleshooting Procedures • 34 Checking network connectivity

Common Troubleshooting Procedures • 35 Checking Oracle

Common Troubleshooting Procedures • 35 Checking the installation


Cluster • 63 Common Troubleshooting Procedures

Checking configuration files • 36 Checking current processes • 34 Checking installed packages • 34 Checking network connectivity • 35 Checking Oracle • 35 Introduction • 34 Process failure • 34 Replication • 36

Configuration screen IS41 RIMS Query • 23 MAP RIMS Query • 26

Configuring the node IS41 RIMS Query • 23 MAP RIMS Query • 26

Critical RIMS Alarms • 40

D defaultMapVersionHlr • 6 defaultPermanentFailureValidityPeriod • 13 defaultSuccessValidityPeriod • 13 defaultTransientFailureValidityPeriod • 13 Document Conventions

Icons • vi Typographical conventions • vi

E Error

RIMS Alarms • 40 Example caching config

Caching • 12 Example ChassisActions config

Chassis Actions • 15 Example config file

RIMS Configuration File • 4

Index



E,(continued) Example IS41 config

IS41 • 8 Example MAP config

MAP • 6

F FDA • 2 FTP • 52 Further information

Alarm Topic Description • 39

G GPRS • 16 GSM • 30 GT • 4, 7, 9

H HLR • 2 hlrErrorMap • 6 hlrTimeout • 5 HPLMN • 73

I Icons

Document Conventions • vi IMSI • 6 IMSI store location

MAP • 6 Installation directory

Loading the Distribution File • 52 Installing the rimsScp Package

Before you begin • 53 Checking the installation • 55 Introduction • 53 Procedure • 53 Sample script • 54

Installing the rimsSms Package • 59 Before you begin • 56 Checking the installation • 58 Introduction • 56 Procedure • 56 Sample script • 57

Installing the rimsSms Package on a Cluster Before you begin • 59 Checking the installation • 63 Introduction • 59 Procedure • 59 Sample script • 60

Introduction Available Feature Nodes • 21 Caching • 12 Chassis Actions • 15 Common Troubleshooting Procedures • 34 Installing the rimsScp Package • 53

I,(continued) Installing the rimsSms Package • 56 Installing the rimsSms Package on a

Cluster • 59 IS41 • 8 Loading the Distribution File • 52 MAP • 6 RIMS Nodes Use Cases • 20 Statistics • 30 What is Messaging Manager Navigator? • 2

IS41 Example IS41 config • 8 Introduction • 8 IS41 Errors • 8 IS41 parameters • 8 MIN store location • 8 VMSC store location • 8

IS-41 • 2 IS41 Errors

IS41 • 8 IS41 parameters

IS41 • 8 IS41 RIMS Query • 21

Configuration screen • 23 Configuring the node • 23 Node description • 22 Node exits • 22 Node icon • 22 Restrictions • 22

L Loading the Distribution File

Installation directory • 52 Introduction • 52 Procedure • 52

M MAP • 2

Example MAP config • 6 IMSI store location • 6 Introduction • 6 MAP parameters • 6 SGSN store location • 6 VMSC store location • 6

MAP parameters MAP • 6

MAP RIMS Query • 21 Configuration screen • 26 Configuring the node • 26 Node description • 25 Node exits • 25 Node icon • 25 Restrictions • 25

MDN • 8 mdnHLRTransType • 11



M,(continued) MdnMinTranslation • 9 MIN • 8 MIN store location

IS41 • 8 minHLRTransType • 10 MMX • v MSC • 27 MSID • 74 MSISDN • 12 MT • 73

N Node description

IS41 RIMS Query • 22 MAP RIMS Query • 25

Node exits IS41 RIMS Query • 22 MAP RIMS Query • 25

Node icon IS41 RIMS Query • 22 MAP RIMS Query • 25

Node list Available Feature Nodes • 21

Notice RIMS Alarms • 48

NPI • 5, 16

O Oracle • ii

P Parameters

allowGPRS • 16 checkCacheForTcap • 7, 10 defaultMapVersionHlr • 6 defaultPermanentFailureValidityPeriod • 13 defaultSuccessValidityPeriod • 13 defaultTransientFailureValidityPeriod • 13 GT • 7, 9 hlrErrorMap • 6 hlrTimeout • 5 mdnHLRTransType • 11 MdnMinTranslation • 9 minHLRTransType • 10 NPI • 16 PC • 7, 9 permanentFailureValidityPeriods • 14 rimsInterfaceName • 15 size • 13 sleepTime • 5 SMS_GET_ROUTING_INFO • 30 SMS_GET_ROUTING_INFO_FAIL • 30 SMS_GET_ROUTING_INFO_SUCCESS •

30 SMS_IS41_SMSREQ_ATTEMPT • 30

P,(continued) SMS_IS41_SMSREQ_PERM_ERR • 31 SMS_IS41_SMSREQ_TEMP_ERR • 31 SMS_IS41_SMSREQ_TIMEOUT • 31 SMS_MAP_SRI_SM_ATTEMPT • 30 SMS_MAP_SRI_SM_PERM_ERR • 30 SMS_MAP_SRI_SM_TEMP_ERR • 30 SMS_MAP_SRI_SM_TIMEOUT • 30 SMS_SET_ROUTING_INFO • 30 SSN • 7, 10 successValidityPeriods • 13 supportIS841 • 10 tcapInterfaceServiceKey • 5 timeout • 16 timeoutTick • 17 TON • 15 transientFailureValidityPeriods • 14

PC • 4, 7, 9 permanentFailureValidityPeriods • 14 PLMN • 73 Pre-requisites

About this Document • v Procedure


Cluster • 59 Loading the Distribution File • 52

Process failure Common Troubleshooting Procedures • 34

Q Query

RIMS Nodes Use Cases • 20

R Related documents

About this Document • v Removing rimsScp

Un-installing the rimsScp Package • 69 Removing rimsSms

Un-installing the rimsSms Package • 66 Replication

Common Troubleshooting Procedures • 36 Response

RIMS Nodes Use Cases • 20 Restrictions

IS41 RIMS Query • 22 MAP RIMS Query • 25

RIMS • 2 RIMS Alarms

Critical • 40 Error • 40 Notice • 48 Warning • 47



R,(continued) RIMS Configuration File

Example config file • 4 RIMS parameters • 5

RIMS Nodes Use Cases Introduction • 20 Query • 20 Response • 20

RIMS parameters RIMS Configuration File • 5

RimsChassisAction parameters Chassis Actions • 15

rimsInterfaceName • 15

S Sample script


Cluster • 60 Un-installing the rimsScp Package • 69 Un-installing the rimsSms Package • 66

Scope About this Document • v

SCP • 30 SCP processes

What is Messaging Manager Navigator? • 2 Severity levels

Alarm Topic Description • 38 SGSN • 6 SGSN store location

MAP • 6 size • 13 SLEE • 2 sleepTime • 5 SMP • 30 SMS • vi SMS_GET_ROUTING_INFO • 30 SMS_GET_ROUTING_INFO_FAIL • 30 SMS_GET_ROUTING_INFO_SUCCESS • 30 SMS_IS41_SMSREQ_ATTEMPT • 30 SMS_IS41_SMSREQ_PERM_ERR • 31 SMS_IS41_SMSREQ_TEMP_ERR • 31 SMS_IS41_SMSREQ_TIMEOUT • 31 SMS_MAP_SRI_SM_ATTEMPT • 30 SMS_MAP_SRI_SM_PERM_ERR • 30 SMS_MAP_SRI_SM_TEMP_ERR • 30 SMS_MAP_SRI_SM_TIMEOUT • 30 SMS_SET_ROUTING_INFO • 30 SMSC • 41 SN • 74 SSN • 4, 7, 10 Statistics

Introduction • 30 Statistics gathered • 30

S,(continued) Statistics gathered

Statistics • 30 successValidityPeriods • 13 supportIS841 • 10

T TCAP • 12 tcapInterfaceServiceKey • 5 timeout • 16 timeoutTick • 17 TON • 15 transientFailureValidityPeriods • 14 Typographical conventions

Document Conventions • vi

U UAS • 2 Un-installing the rimsScp Package

Before you begin • 69 Removing rimsScp • 69 Sample script • 69

Un-installing the rimsSms Package Before you begin • 66 Removing rimsSms • 66 Sample script • 66

V VLR • 73 VMSC • 6 VMSC store location

IS41 • 8 MAP • 6

W WAP • 16 Warning

RIMS Alarms • 47 What is Messaging Manager Navigator?

Introduction • 2 SCP processes • 2

oracle communications network charging and control product ... manager n… · oracle...

Documents