Oracle Communications Network Charging and Control Product: … · 2010. 11. 25. · Continued . Network architecture (continued) The UCAI communicates with the SCF over SS7, using

Oracle Communications Network Charging and Control

Product: OCNCC 4.3 Component: Universal Call Agent for ISUP

Technical Guide S’ware version: Release 3.2.0 Guide version: 04.00

Release date: December 2010

Status: Approved

Commercial In Confidence

Copyright Universal Call Agent for ISUP Technical Guide, Release 3.2.0

04.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.

Page ii Universal Call Agent for ISUP Technical Guide


Contents

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

Chapter 1

System Overview

Overview .............................................................................................................................. 1 UCAI Introduction ................................................................................................................ 2 UCAI Operation - Loop Back Mode ..................................................................................... 5 Supported Messages Overview ........................................................................................... 8 Overlap Sending ................................................................................................................ 15

Chapter 2

Configuration

Overview ............................................................................................................................ 21 Configuration Overview ..................................................................................................... 22 Configuring the Environment ............................................................................................. 23 UCAI Configuration File ..................................................................................................... 24 M3UA Configuration .......................................................................................................... 28 M3UA configuration file syntax .......................................................................................... 31 Routing Options ................................................................................................................. 33 Configuring UCAI ............................................................................................................... 36 Configuring IN Call Model Triggers ................................................................................... 38

Chapter 3

Background Processes

Overview ............................................................................................................................ 43 vssp ................................................................................................................................... 44

Chapter 4

Troubleshooting

Overview ............................................................................................................................ 53 Common Troubleshooting Procedures .............................................................................. 54 Possible Problems ............................................................................................................. 56

Chapter 5

System Alarms

Overview ............................................................................................................................ 57 Alarm Topic Description .................................................................................................... 58 VSSP ISUP Interface alarms ............................................................................................. 60 M3UA interface alarms ...................................................................................................... 82

Chapter 6

Pre-installation

Overview ............................................................................................................................ 83 UCAI Requirements ........................................................................................................... 84 Installation Pre-requisites .................................................................................................. 86

Continued on next page

Universal Call Agent for ISUP Page iii Technical Guide


Page iv Universal Call Agent for ISUP Technical Guide

Chapter 7

Installation

Overview ............................................................................................................................ 89 Installation Procedure Overview ........................................................................................ 90 Loading the Distribution File .............................................................................................. 92 Installing VSSP .................................................................................................................. 93 Checking the Installation ................................................................................................... 95

Chapter 8

Removal Overview ............................................................................................................................ 97 Removing VSSP Package ................................................................................................. 98

Appendix Overview .......................................................................................................................... 101 Glossary of Terms ........................................................................................................... 103 Index ................................................................................................................................ 107


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

Scope

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

Audience

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

Pre-requisites

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. A good of switch configuration is required to correctly configure the UCAI. A detailed understanding of M3UA is essential for configuring the M3UA interface.

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 there are no pre-requisites for using this guide, familiarity with the target platform would be an advantage.

The following documents are related to this document: Related documents

• SLEE Technical Guide • USMS Technical Guide • USMS User Guide • ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes • ITU-T. Q.764, Signalling System No. 7 — ISDN User Part signalling

procedures

Here are the changes to the document since the last release. Changes in this document

Version no.

Revision Date Description

01.01 2006-07-21 Draft release. 02.00 2007-09-17 Overlap sending for IAM and SAM.

Universal Call Agent for ISUP Page v Technical Guide


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

Typographical conventions

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.

Icons

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.

Page vi Universal Call Agent for ISUP Technical Guide


Chapter 1

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.

Introduction

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

This chapter contains the following topics.

UCAI Introduction ............................................................................................ 2 UCAI Operation - Loop Back Mode ................................................................. 5 Supported Messages Overview ...................................................................... 8 Overlap Sending ............................................................................................ 15

In this chapter

Universal Call Agent for ISUP Page 1 Technical Guide

Chapter 1 Commercial In Confidence

UCAI Introduction The Universal Call Agent for ISUP (UCAI) is a signaling element which provides Intelligent Network functionality, without having to upgrade or replace non-SS7 capable switches.

Description

It does this by using fixed connections between incoming and outgoing calls.

UCAI controls call signaling, while internally looping the speech circuits of the call. Without the heavy load that speech traffic creates, UCAI is able to handle more calls than a service node solution.

Using only the Call Set-Up Protocol ISUP, it can offer: Features

• advanced number translation Services such as Free phone and Number portability, and

• call monitoring services such as Prepaid.

Features include:

• support for standard protocols (INAP, ISUP) • support for all ISUP messages, including maintenance messages (for

example: Blocking, unblocking, reset, and Circuit group messages). • provides basic (CS1) IN functionality • leg control can be used for more advanced solutions • can originate both legs of a Call (for example, a call can be originated from a

webpage) • each Transient switch can have its own UCAI for increased network

performance and resilience • failover and load balancing can be easily supported by configuring the network

routing to send messages between mated UCAIs, and • INAP between UCAI and SCP can be over TCP/IP, (reducing Signaling costs).

UCAI runs on low cost general purpose Hardware.

This diagram shows how UCAI is installed within a network. There may be one or more UCAI, each connected to one or more exchanges.

Network architecture


Page 2 Universal Call Agent for ISUP Technical Guide

Commercial In Confidence Chapter 1

UCAI Introduction, Continued

Network architecture (continued)

The UCAI communicates with the SCF over SS7, using either ETSI/ITU-T INAP or AIN0.x. An operator may manage its configuration and alarms by USMS, or via a Q.3 agent using Q.751.

Note: Although the UCAI is shown as a separate physical entity in this diagram, it may also co-exist on the UASs. If so, it will still communicate with the SCF over INAP (though this may not leave the SS7 stack).

UCAI achieves SSP functionality by: Call processing

• Effectively splitting a single physical switch into 2 logical switches. • Using the routing plan of the network, the UCAI appears as another Transient

switch to the original switch for signaling routing purposes. • Voice circuits are looped back to provide the speech path.

UCAI uses ISUP to control calls made to looped-back ISUP speech trunks.

• Each speech circuit going out of the switch has a permanently mapped circuit going into the switch.

• Consequently, the UCAI can make a call on the egress circuit that is effectively a continuation of the original call (even if mapped to a destination determined by an SCP via an INAP protocol).




UCAI Introduction, Continued

Call processing (continued)

UCAI controls processing of the whole call, or control of an individual leg.

• It can be used to implement most IN services. • The type of processing is specified on a per service basis.

This diagram shows the main components of the UCAI hosted on a UAS. Components



UCAI Operation - Loop Back Mode Here is an example of how UCAI works in its simplest configuration. A single incoming circuit and a single outgoing circuit.

Basic processing

As shown in the example, the only actual connection to UCAI is the signaling link. No speech paths are routed. All signalling, for both the incoming and outgoing circuits on the loop, are carried on the signalling link. The speech path is looped with very low visibility to the switch. This may be achieved by using a static configuration of the switch matrix, or by an external piece of hardware. In either case, the switch's call process is unaware of the loop.

Calls to UCAI must only be routed down an incoming leg. Calls routed down a UCAI incoming leg that are not intended for UCAI, are still sent to the SCF for processing. This almost always results in that call being rejected.

Calls routed to a UCAI outgoing leg are rejected.

A full understanding of this is essential to correct configuration of a UCAI into a Telco’s network.

The following steps describe what happens when a call arrives on the incoming leg to the UCAI.

Call processing

Note: This process description assumes the network is configured as described above.

Stage Description 1 The call is routed to UCAI.

Notes: • Before this can happen, the external network must have been

correctly configured to route the call into UCAI. • The last part of the host network on which the call appears is

the switch which is directly connected to UCAI. This is the switch which sends the ISUP IAM message to UCAI, indicating the call is being made.

• The specific circuit (that is, timeslot) which the call arrives on must be specified as “incoming”. If a call arrives on a leg designated as "outgoing", it will be rejected.

2 UCAI queries an SCF to determine how the call is to be processed. This example assumes a simple number translation (for example, translating a free or premium rate phone number into its final destination).

3 UCAI sends an outgoing ISUP IAM message on the outgoing leg that corresponds to the incoming leg on which the call arrived. The IAM contains the translated number. It may also have other parameters modified by the SCF. UCAI automatically selects a circuit on to route the outgoing call on. Because it contains no switch matrix, the only circuit the call's speech can be present is the one to which the incoming leg is looped.




UCAI Operation - Loop Back Mode, Continued

Call processing (continued)

Stage Description 4 Call processing continues as it would with any other SSP. The ISUP

messages are acted on by the SSP under SCF control, exactly as would happen with a conventional SSP. The SCF is unaware UCAI is different from any other sort of SSP.

In order to correctly plan, install and configure a working installation you must be aware of the following issues:

Important installation planning

• Signalling • Loop Back, and • UCAI configuration.

These issues are discussed further below.

Signalling configuration is very important to the correct functioning of UCAI. The example network configuration above only has a single signalling link. That link is the only connection between UCAI and the attached network.

Signalling

Signalling for both the incoming and outgoing legs is carried on the same link. This can cause some complex issues for the configuration of the attached switch, and these must be carefully addressed. The signalling link is set up in a completely standard manner, with point codes allocated to both ends and an agreement on the allocation of cics to specific timeslots. However, the two circuits involved are looped without the switch's knowledge. This has a major effect on the routing policy that must be configured on the attached switch. In the example, two circuits are used. However, the switch may only make calls to the UCAI down the incoming leg. This requires the switch to be configured so routing is allocated not only on a point code basis (which permits the switch to route calls down any circuit), but also on a per circuit basis (so that calls are only routed down those circuits designated as "incoming" to the UCAI). The details of this are highly switch-specific, but must be provided to ensure correct operation.

This example extends the previous example. Configuration example

Assumptions:

• UCAI has point code 1 • switch has point code 2 • single incoming circuit is assigned cic 1 • single outgoing circuit has cic 2 • calls should be processed with the prefix 0800.

Required Configuration: The switch must be configured so it will route calls with the 0800 prefix to point code 1, but only on cic 1. A switch-specific example is an mml command of the form: ROUTE:PREFIX=0800,DPC=1,CICS=1;




UCAI Operation - Loop Back Mode, Continued

Configuration example (continued)

This command indicates calls prefixed with 0800 should be sent to point code 1, and the only available cic is 1.

If the switch does not offer this degree of routing control, there are several options discussed in Routing Options (on page 33).

Ideally, the loop back is performed by the switch. However, it must be possible to do this without interfering with the switch's call processing. If this is impossible, some external form of loop back device must be employed. This may be possible with whatever device is used to extract the signalling information and pass it onto the UCAI.

Loop back

UCAI must also be configured. Given the point codes and cics detailed in Configuration (on page 21), the configuration file need only contain:

UCAI configuration

connect 1/2/1 to 1/2/2.

Note: The full stop at the end of every configuration statement is essential.

UCAI uses a sliding window of one second to measure load. If an IAM arrives less than one second after the one <CAPS limit> IAMs before it, it is rejected.

Throttling

Example: UCAI is set with a limit of 20 CAPS. This means in any single second window UCAI will allow 20 call attempts and the 21st will be rejected.

• If the IAMs arrive exactly at 1/20th of a second intervals, there will be 20 CAPS.

• If an IAM arrives even one microsecond 'early' it causes a peek of 21 CAPS and is rejected.

So, even if traffic is sent at 20 CAPS and a 20 CAPS limit is set, the occasional call will still be rejected.



Supported Messages Overview This table describes UCAI's main message groups: Introduction

Component Description Call Processing The basic call processing package is composed of a group

of simple messages to progress the call. For more information, see Call processing messages (on page 9) below.

Additional Call Set-up

Call setup may be made more complex by the use of extra, more complex messages to progress the call. For more information, see Additional call setup messages (on page 10) below.

Continuity Testing Some networks support use of ISUP’s continuity testing procedures. UCAI is able to handle all such situations correctly. For more information, see Continuity testing messages (on page 12) below.

Maintenance The UCAI supports single circuit maintenance messages, or group messages, to allow for blocking, unblocking, or resetting of circuits. For more information, see Maintenance messages (on page 13) below.




Supported Messages Overview, Continued

This table lists the basic call processing messages which are supported by the UCAI.

Call processing messages

Message Type Description Initial Address Message (IAM)

The Initial Address Message has five mandatory parameters and 42 optional parameters (for more information, see Table 32 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The mandatory parameters are: • nature of connection indicators • forward call indicators • calling party’s category • transmission medium requirement • called party number The UCAI handles all the mandatory and optional parameters. However, some filtering may take place, in order to ensure correct operation of the UCAI. In addition, certain pathological values for some parameters may cause rejection of the call in some cases. Note: If a hop counter occurs on the incoming leg and its value is zero, the call is rejected. If its value is greater than zero, the value is decremented and used on the outgoing leg. If no hop counter was provided, one is inserted with a default value. Use of the hop counter is very important. It avoids the possibility of a routing error in the network resulting in a ‘circular call’ that ‘bounces’ between the UCAI and its attached switches. Such an occurrence is a very dangerous network event, as it consumes very large amounts of processing power and signalling bandwidth.

Address Complete Message (ACM)

The Address Complete Message has one mandatory parameter and 19 optional parameters (for more information, see Table 21 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The mandatory parameter is backward call indicators. As with the Initial Address Message, some filtering of the message parameters may take place.

Answer (ANM) The Answer message has no mandatory parameters and 21 optional parameters (for more information, see Table 22 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). As with the Initial Address message, some filtering of the message parameters may take place.





Call processing messages (continued)

Message Type Description Release (REL) The Release message has one mandatory parameter, and

up to seven optional ones (for more information, see Table 33 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The mandatory parameter is cause indicators. As with the Initial Address message, some filtering of the message parameters may take place.

Release Complete (RLC)

The Release complete message has one optional parameter (for more information, see Table 34 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The optional parameter is cause indicators. As with the Initial Address message, some filtering of the message parameters may take place.

Call setup may be made more complex by the use of some of the more complex messages to progress the call. This table describes these message types supported by the UCAI.

Additional call setup messages

Message type Description Subsequent Address Message (SAM)

The Subsequent Address Message has one mandatory parameter (for more information, see Table 35 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The mandatory parameter is subsequent number. The UCAI will handle use of SAM messages (also known as ‘overlap’ sending). However, the service itself should be made aware that this form of signalling may be in use, as it can confuse some services, if they assume all the digits are to be presented at once. This can usually be avoided by careful use of network, UCAI and service configuration, but care should be taken to avoid it. In addition, use of SAM or overlap signalling results in increased network traffic and processing overhead. It should therefore be avoided, wherever possible.

Call Progress The Call Progress has one mandatory parameter and 25 optional ones (for more information, see Table 23 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The single mandatory parameter is event information.






Additional call setup messages (continued)

Message type Description Connect The Connect message has one mandatory parameter and

19 optional ones (for more information, see Table 27 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The mandatory parameter is backward call indicators. The UCAI treats the Connect message in a very similar manner to an Address Complete followed by an Answer.

Identification Request

The Identification Request message has no mandatory parameters and three optional ones (for more information, see Table 47 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes).

Identification Response

The Identification Response message has no mandatory parameters and seven optional ones (for more information, see Table 48 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes.).

Information Request The Information Request message has one mandatory parameter and three optional ones (for more information, see Table 31 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The single mandatory parameter is information request indicators.

Information The Information message has one mandatory parameter and six optional ones (for more information, see Table 30 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The single mandatory parameter is information indicators.

Suspend and Resume

The Suspend and Resume messages have one mandatory parameter and one optional (for more information, see Table 38 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes). The single mandatory parameter is suspend/resume indicators. The UCAI processes Suspend and Resume requests as required by §9.1.3 of ETR 164, Integrated Services Digital Network (ISDN); Intelligent Network (IN); Interaction between IN Application Protocol (INAP) and ISDN User Part (ISUP) version 2.




Some networks support use of ISUP’s continuity testing procedures. UCAI handles the following cases correctly:

Continuity testing messages

• Testing after an Initial Address message (this may occur after every IAM, or some form of statistical sampling may be employed).

• Testing an idle circuit. • A call can be placed that is waiting for the results of a continuity test on a

previous circuit.

Note: In theory, there should be no need for continuity checks in a modern network. The lower-level signalling should detect the failure of a speech or signalling link, and block use of those circuits. However, it can be useful for testing for correct configuration of the UCAI.

A major feature of the UCAI is speech circuits do not pass through it. Consequently, the UCAI (though able to detect failures in the signalling links) is unable to detect problems with the associated speech circuits. Instead it relies upon the attached switches to detect problems.

If the UCAI's speech circuits are mis-configured, the usual result is for the call to be made and appear to work (including billing) but no speech is heard.

Continuity testing can help guard against these problems. Periodic and/or statistical testing is recommended, unless the operator has taken great care in the configuration of the UCAI and its attached switches.

The UCAI handling of continuity testing is in accordance with §2.1.8 of ITU-T. Q.764, Signalling System No. 7 — ISDN User Part signalling procedures.

Continuity check request The Continuity Check Request message has no parameters (for more information, see Table 39 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes).

Use of CCR is only valid on idle incoming circuits, and the CCR message is passed onto the corresponding outgoing circuit.

Continuity The Continuity message has one mandatory parameter and no optional ones (for more information, see Table 28 of ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes).

The mandatory parameter is continuity indicators.





This table describes the single circuit and group circuit maintenance messages supported by UCAI.

Maintenance messages

Message Type Description Single circuit maintenance messages

Several single circuit maintenance messages are defined in ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes. Those supported by the UCAI are: • Blocking • Blocking Acknowledgement • Reset Circuit • Unblocking • Unblocking Acknowledgement. None of these have any parameters. The functionality the same as is described in ITU-T. Q.764, Signalling System No. 7 — ISDN User Part signalling procedures, but with one addition imposed by the UCAI. As the UCAI ties incoming and outgoing circuit together, any blocking or unblocking coming into the UCAI on an outgoing circuit causes a similar message to be reflected on the corresponding incoming circuit. Similarly, if any problem occurs with an outgoing leg, the UCAI blocks the corresponding incoming leg, to avoid being given calls it cannot process.






Maintenance messages (continued)

Message Type Description Circuit group maintenance messages

It is often more efficient to use one of the group messages defined in ITU-T. Q.763, Signalling System No. 7 — ISDN User Part formats and codes, than to use a number of the corresponding single circuit maintenance message. The UCAI currently supports the following group messages: • Circuit Group Blocking • Circuit Group Blocking Acknowledgement • Circuit Group Unblocking • Circuit Group Unblocking Acknowledgement • Circuit Group Reset • Circuit Group Reset Acknowledgement. The functionality is the same as is described in ITU-T. Q.764, Signalling System No. 7 — ISDN User Part signalling procedures, but with one addition imposed by the UCAI. As the UCAI ties incoming and outgoing circuit together, any blocking or unblocking coming into the UCAI on an outgoing circuit causes a similar message to be reflected on the corresponding incoming circuit. Handling of some circuit group messages can be problematical in some networks. In addition, due to the potentially arbitrary nature in which incoming and outgoing circuits can be tied together for the UCAI, a circuit group block on an outgoing leg is repeated through to the incoming side, as a series of single circuit blocks. A similar technique is used in handling circuit group resets and unblocking. Therefore, the UCAI only sends circuit group messages in response to circuit group messages received. If the network does not support circuit group messages, none will arrive at the UCAI and so the UCAI will not use them in response.


Overlap Sending Overlap Sending or Signalling can be used in a fixed line environment where a call set up can begin even before the caller has dialed all digits of the intended destination number. This is achieved when the caller has dialled enough digits for an originating exchange using the Overlap Sending method, to determine the target exchange. The originating exchange packs the digits collected from the calling party so far, into an Initial Address Message (IAM) and sends it to the next exchange.

Introduction

Subsequent digits dialled by the caller are contained within the Subsequent Address Message (SAM). Each new SAM contains additional digits dialled by the caller. UCAI invokes appropriate IN services within the call setup path based on pre-defined triggering rules.

Note: Overlap sending is not possible in a mobile environment since the calling party must dial all the digits of the intended destination before initiating a call setup attempt.

Here is an example of how UCAI supports the Overlap Sending method of setting up a call.

How Overlap Sending works

The originating exchange will attempt to set up a call once it has collected sufficient digits from the calling party to identify the next target exchange (tandem or ultimate destination exchange) in the call flow. It will generate an IAM (Initial Address Message) with all the digits the calling party has dialled until then, and route it along the network.




Overlap Sending, Continued

How Overlap Sending works (continued)

Subsequent digits dialled by the caller will be contained within the Subsequent Address Message (SAM). Depending on the caller's dialling speed, one or more SAMs may be generated. Each SAM will contain any new digits dialled since the last SAM (or the initial IAM) was sent.

IN services within the signalling path are activated based on the triggering rules used by UCAI. Currently, these triggering rules are defined in the tdp.conf file.

In the Overlap Sending method, the call setup begins even before the caller dials all the digits of the intended destination. However, in such a scenario, IN systems involved in the call signalling path cannot determine when to trigger the IN services. Currently, UCAI uses the triggering rules defined in the tdp.conf. This file is processed by the IN call model component of the UCAI.

Triggering Rules

UCAI triggers IN services when the incoming digits dialled so far trigger a matching rule in the tdp.conf. The decisive digits invoking the rule may be contained in:

• The IAM received from the originating exchange, or • The IAM + one or more SAM messages received from the originating

exchange.

tdp.conf Here is an example of the tdp.conf file.

KEEP SD ETC RULES=6 3 3 1 3 request all 3:01473222

Stop Digit Typically, when the caller dials a local/national number, the originating exchange will lookup the configured numbering plan information to determine if sufficient digits have been dialled to identify the target exchange. If it recognises the numbering pattern of the dialled digits, the originating exchange will insert a stop digit into the called number signalling sequence.

UCAI triggers the IN service when a stop digit is detected and an appropriate rule in tdp.conf is found. The stop digit may be contained in either of the following:

• The IAM received from the originating exchange, that is at the end of the IAM, or

• The IAM + one or more SAM messages received from the originating exchange, that is, at the end of the last SAM.





Triggering Rules (continued)

SAM Timer Sometimes, due to a lack of numbering plans available, a local or transit exchange within a country may not correctly decipher the numbering pattern of the dialled digits (typically an international number). Consequently, the originating exchange fails to insert the stop digit. This results in the UCAI waiting an indefinite period of time for the overlap sequence to end, not knowing when to trigger the IN service. To safeguard against this situation, the UCAI is equipped with a timer, known as SAM timer. The SAM timer is used for initiating IN services when Overlap Sending is invoked for a number with an unrecognisable numbering scheme.

The UCAI waits for a fixed period of time to receive the first or next SAM in an overlap sequence before activating the IN services. When this timer has expired the UCAI assumes that the caller has completed the dialling sequence for the intended destination number and ignores any additional dialled digits. This means no new digits will be accepted from the caller/network after the timer expires.

The UCAI starts the SAM timer for a call when it receives an IAM not containing the stop digit. The SAM timer is restarted each time a new SAM is received for the call.

Note: The SAM timer will not be started if the digits contained within the IAM or the SAM are sufficient for the UCAI to trigger an IN service.

Forced Trigger Scenario If the SAM timer expires and an IN Service has not been triggered, then the UCAI adds a stop digit to the dialled overlap sequence. This is known as a "forced trigger" scenario.

One of the following results may occur in a forced trigger scenario:

• A matching rule in the tdp.conf file is found which triggers an IN service, or • A matching rule is not found and the UCAI releases the call by sending a REL

message on the A-leg.

After an IN service is triggered, it returns any one of the following results: IN Service Processing

• Continue • Connect ("cut and paste" option not set) • Connect ("cut and paste" option set) • ETC (treated as 'Connect' by UCAI) • Release • Error

After the UCAI has sent an IAM on the B-leg of the call and BEFORE an ACM message is received from the B-leg, it is possible that additional SAM messages may be received on the A-leg.






IN Service Processing (continued)

Before an IAM is sent on the B-leg This table describes how the UCAI treats different message scenarios before an IAM is sent on the B-leg.

Scenario Result Additional digits are received in SAM messages while IN service is treating the request.

UCAI will store the digits.

In a forced trigger scenario, additional digits are received in SAM messages while IN service is treating the request.

UCAI will ignore the digits.

'Continue' message is received from IN service. All digits received by UCAI (including digits received/stored when the IN service was processing the call) will be used in the calledPartyAddress field of the IAM sent on the B-leg.

'Connect' message is received from IN service with the "cut and paste” field NOT set.

The number specified in the destinationRoutingAddress field of the 'Connect' message shall be used in the calledPartyAddress field of the IAM sent on the B-leg Any additional digits received in the period when the IN service was processing the call will be ignored.

'Connect' message is received from IN service with the "cut and paste” field set.

All digits received by UCAI (including digits received/stored when the IN service was processing the call) will be used. Based on the options set in the “cut and paste” field, the required number of digits will be cut from the beginning of the calledPartyAddress received in the IAM and all the SAM mesages. The cut number is then pasted to the number received in the destinationRoutingAddress. The resultant number from the cut and paste operation will be used in the calledPartyAddress field of the IAM which is sent on the B-leg. Note: In a forced trigger scenario any additional digits received during the IN service processing will be ignored and not be included in the resultant number when the "cut and paste" field is set.

An 'ETC' operation is received from IN service. The number specified in that operation will be used in the calledPartyAddress field of the IAM sent on the B-leg. Any additional digits received in the period when the IN service was processing the call will NOT be used in the calledPartyAddress and will be ignored.




IN Service Processing (continued)

After an IAM is sent on the B-leg After the UCAI has sent an IAM on the B-leg of the call and BEFORE an ACM message is received from the B-leg, it is possible that additional SAM messages may be received on the A-leg. Any SAM messages received on the A-leg of the call after the IAM has been sent on the B-leg of the call shall be transparently sent onto the B-leg of the call.

The following cases are some exceptions to this transparent sending:

• ACM is received on the B-leg. • IN services issues a 'Connect' message with the "cut and paste" option not

set. • IN services issues an 'ETC' message. • IN service was triggered in a forced trigger scenario.

In case 2 and 3, the UCAI will add a stop digit to the number if one is not already present. The UCAI then ignores all subsequent messages if:

• A stop digit is encountered on either the IAM or SAM message sent on the B-leg, or

• The IN service was triggered in a forced trigger scenario.

If the UCAI has been instructed by the IN service to route the call to a totally different number/address than as intended by the caller, the SAM being relayed onto the B-leg may have an undesirable affect on the destination (or transit exchange).

For example: The IN service routes the call to an IVR number where the caller was expecting to be connected to an international party.

During call setup, the UCAI allows certain messages to be transparently passed between the A and B legs, even after the call has been established.

Transparent Passing of ISUP Messages

Here, the following ISUP messages are notable as examples:

• The call progress message (CPG) can be passed transparently between the A and B leg of a call after it has been established, that is, after the ANM message is received from B-leg.

• Facility (FAC) messages received on either A or B leg can be transparently passed onto the other leg without triggering the IN service.





In this situation, the called party suspends a call by replacing the receiver back on the hook, in order to change the physical phone that is currently connected to the call. The called party then physically attends the call from another phone on the same line. The UCAI handles this functionality by providing an appropriate safeguard that allows the B-leg to stay connected, even if the call has been suspended for a specific period of time.

Handling Called Party Suspends

On receiving a SUS (suspend) message on the B-leg, the UCAI starts a 'suspend' timer for the call. Currently, the T6 timer is implemented as the suspend timer. The UCAI will stop the suspend timer on receiving a RES (resume) message on the suspended B leg.

When the suspend timer expires, the UCAI sends a REL message on the B-leg of the call and waits for a RLC message. On receiving the RLC message, the IN call model is notified that the B-leg has been disconnected. If the IN service has armed an event for B-leg disconnect, it will be informed by the IN call model that the called party has disconnected. It is possible to configure the length of time used by the suspend timer in seconds.



Chapter 2

Configuration Overview

This chapter explains how to configure the application. Introduction


Configuration Overview ................................................................................. 22 Configuring the Environment ......................................................................... 23 UCAI Configuration File ................................................................................. 24 M3UA Configuration ...................................................................................... 28 Routing Options ............................................................................................. 33 Configuring UCAI .......................................................................................... 36 Configuring IN Call Model Triggers ............................................................... 38

In this chapter



Configuration Overview UCAI is configured by the following components: Configuration

components

Component Locations Description Further Information vssp.config all UAS Required to configure the

UCAI process. UCAI Configuration Files (see "UCAI Configuration File" on page 24)

vssp.sh all UAS Sets UCAI process's command line startup parameters.

Configuring the Environment (on page 23)

m3ua.config all UAS Required to provide M3UA configuration. Not required if this version of UCAI does not support M3UA.

M3UA Configuration (on page 28)

keyfile all UAS Required if UCAI has a circuit limit.

Editing the vssp.sh file (on page 23)

tdp.conf all UAS Configures the IN Call Model library. Required for interaction with the SLEE.

Configuring IN Call Model Triggers (on page 38)

SLEE.cfg all UAS SLEE.cfg sets up SLEE interfaces and applications.

SLEE Technical Guide.

UCAI will reread its configuration when it is restarted. Rereading configuration

Note: To restart UCAI, you must restart the SLEE. For more information about restarting the SLEE, see SLEE Technical Guide.



Configuring the Environment The UCAI environmental variables are set in the vssp.sh file. Introduction

The file vssp.sh is used to set environment variables and command line parameters before the UCAI executable is started. There are potential stack-specific environment variables as well as UCAI-generic command line options.

There are three possible command line parameters in the format: Editing the vssp.sh file

vssp [-c] <dir/filename> [-k] <dir/filename> [-m] <dir/filename>

The only mandatory option is the name of the vssp configuration file. This can either be specified by the -c flag or it is the first non- flagged parameter. For more information about setting up this file, see UCAI Configuration Files (see "UCAI Configuration File" on page 24).

In UCAI builds which require a license key file, the name of the file may be specified on the command line. This may be specified either using the -k flag or it is the second non-flagged parameter. If it is not given, UCAI will default to using the file called keyfile in the same directory as the vssp.config file.

In UCAI builds which use the M3UA protocol, the M3UA configuration file name can be given. This can either be set using the -m flag or it is the third non-flagged parameter. If no file name is given, UCAI will default to using a file called m3ua.config in the same directory as the vssp.config file.

This text shows an example vssp.sh file. Example vssp.sh file

LD_LIBRARY_PATH=/usr/lib/secure export LD_LIBRARY_PATH exec /IN/service_packages/VSSP/bin/vssp -c /IN/service_packages/VSSP/etc/vssp.config -m /IN/service_packages/VSSP/etc/m3ua.config >> /IN/service_packages/VSSP/tmp/logfile 2>&1



UCAI Configuration File The main UCAI configuration file is vssp.config. It configures the UCAI process and is located in:

Introduction

/IN/service_packages/VSSP/etc

vssp.config has two sections:

1 Global vssp options (see "Parameters" on page 45) 2 Point Code routing (Circuit Loops)

Circuit loops are described using the connect statement. In their simplest form connects take the form of:

Configuring circuit loops

connect <circuit> to <circuit>.

Note: Each command in vssp.config must end with either:

• a full stop (.) or • a semi-colon (;).

The circuit in the above example is composed of three parts in the format: a/b/c

Where:

• a = the point code of the UCAI end • b = the point code of the remote end • c = the circuit identification code

A circuit loop has two circuits: Example 1

1 an incoming circuit to point code 1 from remote point code 2 on cic 1, and 2 an outgoing circuit from point code 1 to remote point code 2 on cic 2. This setup would be configured in vssp.config as: connect 1/2/1 to 1/2/2.

A single 2.048 Mbps ‘E1’ link has 32 timeslots (0-31), of which: Example 2

• timeslot 0 is used for link management • timeslots 1-15 are where incoming calls have their speech arrive • timeslot 16 for signalling, and • timeslots 17-31 are used by outgoing calls.

The point codes are the same as in Example 1, so vssp has point code 1 and the attached switch has point code 2.

The circuit loop section of the vssp.config for this scenario would appear as follows: connect 1/2/1 to 1/2/17. connect 1/2/2 to 1/2/18. connect 1/2/3 to 1/2/19. connect 1/2/4 to 1/2/20. connect 1/2/5 to 1/2/21. connect 1/2/6 to 1/2/22. connect 1/2/7 to 1/2/23. connect 1/2/8 to 1/2/24. connect 1/2/9 to 1/2/25. connect 1/2/10 to 1/2/26.




UCAI Configuration File, Continued

Example 2 (continued)

connect 1/2/11 to 1/2/27. connect 1/2/12 to 1/2/28. connect 1/2/13 to 1/2/29. connect 1/2/14 to 1/2/30. connect 1/2/15 to 1/2/31.

Signalling is in timeslot 16. This will need to be sent out to UCAI.

Speech sent out on timeslot 1 must return on timeslot 17, so that the called party can hear the calling party. Similarly, the speech sent out on timeslot 17 must return on timeslot 1, so the caller can hear the called party. This is repeated with timeslot 2 and 18 and so on, up to timeslot 15 and 31.

This can also be written as: Shorthand configuration

connect 1/2/1 to 1/2/17 for 15.

The “for 15” on the end instructs the UCAI that the connect is to be repeated for a total of 15 times, including the one specified in the line. Each time, UCAI adds 1 to the cics for both the incoming and the outgoing circuits.

The number after the “for” indicates the total number of circuits generated and not the number of additional circuits. It includes the circuit number specified in the line it is set in.

Care must be taken, as it is very easy to get the count of the circuits wrong. The final number of cics used is the first one, plus the number of repetitions minus one. For example, if you are starting at cic 1 and specify "for 2”, the final cic will be 2 and not 3.

Mistakes in this configuration will result in mismatches of conversations, for example:

• a one-way call (where one party can hear the other, but not the other way round)

• different calls connected together, or • (most commonly) total silence at both ends.





The diagram shows the logical structure of how a loop box should be set up to handle Example 2. The speech paths are looped but the signalling is extracted and passed onto UCAI. The exact method for doing this will be very site-specific (several methods may even be employed in the same site).

Diagram

Note: The connections for incoming timeslots 2 to 14 and 18 to 30 have been omitted, so the diagram is less cluttered.

This is an example of the vssp.config file (comments have been removed). Example configuration - vssp.config set option slee.

set option syslog. set option stats. set cdr file="cdr.log"; #set option debug. #set option mtp debug. set ica iam cpc 10; connect 1/2/1 to 1/2/17 for 15;

Optimal configuration for the network depends on many variables, including: Optimal configuration

• types of service to be implemented • detailed estimates of the calling pattern to each service • trunking a call between switches • cost of trunk and signalling interfaces • network topology, and • UCAI costs.






Optimal configuration (continued)

It is beyond the scope of this document to detail the modelling required to produce an optimal solution.

The basic requirements for installation of the UCAI are the same regardless of the configuration chosen for a network. The requirements may be broken into the connection to the originating exchange, and the connection to the terminating exchange.

These may be subtly different from a signalling perspective, since each call arriving at the UCAI from the originating exchange may result in multiple sequential calls being made to the terminating exchange. For example, a call may be routed to an announcement prior to be routing to the eventual destination.


M3UA Configuration This section introduces the configuration of the UCAI M3UA interface. Overview

We will give a very simplified example of a M3UA network and its configuration to illustrate the fundamental concepts of UCAI's M3UA configuration.

In our example network we consider the last switch in a chain of SS7 switches. Everything further away from the UCAI will be pure SS7. For this example it will have a switch point code of 1.

Note: This chapter is not a substitution for a detailed knowledge of M3UA. A thorough understanding of the principles and techniques of M3UA is a vital prerequisite to successful configuration of the UCAI M3UA interface.

As with standard configuration, UCAI needs loopbacks to be set up on the switch. Switch configuration

For this example, we will use two E1 links which are looped back to each other. (In other words, the transmit of the first link is connected to the receive of the second link and vice versa.) Signalling is not carried in the traditional timeslot 16, this timeslot is unused.

Elsewhere on the switch are signalling links that connect to the SS7-sigtran gateway (the signalling gateway (SG), commonly a Cisco ITP). It will have a point code of 2. These links have signaling on timeslot 16 but the other timeslots (1–15 and 17–31) are unused.

The switch has a link to the SG on local point code 1 and remote point code 2. It has 60 circuits. The first 30 are bi-directional, the second 30 are incoming only. These circuits are on the loopback that we built previously and not anything to do with the unused timeslots on the link to the SG. Although the linkset is between point codes 1 and 2, the point code of the remote end at the ISUP level is that of the UCAI (which we will define to be 3). This is the configuration normally used for ISUP if the traffic is being routed via some sort of SS7 router.

To summarise the configuration of the switch it has:

• two E1 ports being used for the loopback (only carries speech, no signalling). • a port being used signal to the SG (only carries signalling, no speech). • signalling is configured with a local point code of 1 and a remote point code of

2. • ISUP on the switch is configured to use the 60 speech circuits of the looped

links. • ISUP DPC is set to be 3. • point code of the UCAI and the switch is configured to route to DPC 3 via point

code 2 (the SG).




M3UA Configuration, Continued

The SG is assumed to be a Cisco ITP. To set it up, configure the baseline internet and the SS7 link. This provides the core SS7 and IP routing functions.

SG (ITP) Configuration

First set the port and IP address for the M3UA SCTP port, that is, the Signalling gateway Point (SGP) as follows:

Command UCAI Mode cs7 m3ua 5000 local-ip 192.168.1.1

Loop Back Mode: The M3UA is configured on the SG. In this example: • SCTP port 5000 is used for the sigtran

M3UA • ITP has an IP address of 192.168.1.1 • IP address of the UCAI machine is

192.168.1.2 cs7 m3ua 5000 local-ip 192.168.1.1 cs7 m3ua 5001 local-ip 192.168.1.2

Basic Inline Mode: In this mode, we define 2 local M3UA stacks.

The vssp.config for this example is: VSSP Configuration

connect 3/1/1 to 3/1/33 for 15; connect 3/1/17 to 3/1/49 for 15;

This configuration indicates that the circuit with local (to the UCAI) point code 3, remote (to the UCAI) point code 1 and cic 1 is looped to circuit local 3, remote 1 and cic 33. This is repeated for the other 29 circuits skipping the unused timeslot 16.

When using M3UA, a second configuration file is also needed. This details the M3UA-specific configuration. For this example, it could be: asp port 5000 addrs {192.168.1.2}; sgp itp1 port 5000 addrs {192.168.1.1}; gateway sg1 {

sgp itp1 key 1234; pc {2, 1};

} as pc 3 gateway {sg1};

This shows a local ASP on SCTP port 5000 with local address 192.168.1.2.

Note: There can only be a single port but it can be on multiple addresses. All the addresses given must belong to the local machine.

It also shows an ITP called itp1 with a port number of 5000 on the remote address of 192.168.1.1. Again, multiple addresses can be given and they must all belong to the remote SGP.

It also shows a signalling gateway called sg1. This contains the single SGP itp1 and identifies the routing key on the peer SGP. It also shows a list of point codes. The first is the point code of the SG itself (in this case 2) and any following point codes are those which can be reached via the SG. For this example, we specify that point code 1 may be reached via this SG.




M3UA Configuration, Continued


VSSP Configuration (continued)

It also shows our local AS. For this example, it has a point code of 3 and is peered with SG sg1.


M3UA configuration file syntax The M3UA configuration file supports two sorts of comments: Lexical

considerations • comment to end of line is indicated by a double forward slash (// with no space

in between them).

Example: Comment to end of line // This is the M3UA configuration file for the test network.

• comments that run over several lines are introduced by a /* and ended with a */.

Example: /* * Now we set up the various SGPs in our network. There are three of * them. * * sgp1 --- located in The Fort this deals with its local area. * sgp2 --- located in The Hoist this is a hot standby for sgp1. * sgp3 --- located in Heaven this handles all international traffic. */

Whitespace is only used to separate other lexical items. Otherwise it is ignored. Whitespace

Example: The following methods of defining an asp are identical. asp port 5000 addrs {192.168.1.2}; asp

port 5000 addrs { 192.168.1.2 }

;

This text shows an example M3UA configuration: Example M3UA configuration file

#start file asp port 6969 addrs {192.168.26.117}; sgp itp1 port 2905 addrs {192.168.26.215}; gateway sg1 {

sgp itp1 key 6969; pc {999, 4805, 4807};

} as pc 4701 gateway {sg1}; #end file

Using more whitespace, this file could also be displayed as follows: #start file asp

port 6969 addrs {192.168.26.117}

; sgp itp1

port 2905 addrs {192.168.26.215}

;




M3UA configuration file syntax, Continued


Example M3UA configuration file (continued)

gateway sg1 {

sgp itp1 key 6969; pc {999, 4805, 4807};

} as

pc 4701 gateway {sg1}

; #end file


Routing Options It is possible for attached switches to be configured so calls are only presented to the UCAI on circuits designated as “incoming” to the UCAI. There may be switches that do not allow routing on a per cic basis, and this section deals with several possible work-arounds for this problem.

Introduction

These options are necessarily, highly switch-specific, but one or more of them should be effective.

Some switches do not perform their routing based on point code. Instead they route based on sending calls down a specific link or linkset. In this case, the fix is fairly simple.

Per link fix

Routing should be configured so an entire link or linkset is designated as either all “incoming” to the UCAI or “outgoing” from the UCAI. Routing is then configured so calls are only routed down the links or link sets designated as “incoming” to the UCAI.

Example: A hypothetical mml command might be of the form: ROUTE:PREFIX=0800,LINKS=LNK1,LNK3;

where the links LNK1 and LNK3 are designated as “incoming” to the UCAI and the unreferenced links (LNK2 and LNK4) are for the “outgoing” from the UCAI circuits. This would lead us to a loop-back structure looking something like this diagram.

Quite how the signalling would work in this situation is somewhat unclear. However, it is possible to do it with just the one signalling link, provided care is taken to assign the cics correctly.

One possible method would be to have LNK1 using cics in the range 1 to 31 (based on the timeslots) and then to have the rest shifted up by 32, so LNK2 would be 33 to 63, LNK3 65 to 95 and LNK4 97 to 127.

This would lead to a vssp.config file which looks like: connect 1/2/1 to 1/2/33 for 31 except 15. connect 1/1/65 to 1/2/97 for 31.

This assumes:

• the UCAI has point code 1 and the attached switch point code 2, and • timeslot 16 of LNK1 carries the signalling.

Another possible option to work around routing problems in an attached switch, is to use multiple point codes on the attached switch. This means a switch may be able to support multiple links between itself and the UCAI.

Multiple point code fix




Routing Options, Continued

Multiple point code fix (continued)

These links may have different sets of point codes at the switch end. In this case, calls can be routed out from the switch to the UCAI from one point code, and be sent back into the switch from the UCAI on another point code.

Example: If the UCAI has point code 1 and the switch has point codes 2 and 3, our network diagram would look something like this diagram.

Note: The major difference between this and the ‘per link’ fix is there are now two signalling links involved. The signalling for the traffic from the switch to the UCAI uses one link, while the signalling for the traffic coming from the UCAI to the switch uses the other.

Routing should be configured so this is the case. All traffic to the UCAI should be routed out of the switch’s point code 2 link, to the UCAI’s point code 1. No traffic should be routed out of the switch’s point code 3.

A hypothetical mml command might be of the form: ROUTE:PREFIX=0800,OPC=2,DPC=1;

Both signalling links must also be configured so they can send signalling information. This is usually a lower-level operation than setting up routing information. The configuration for UCAI only requires connecting the inputs to the outputs: connect 1/2/0 to 1/3/0 for 32 except 0 and 16.

This assumes timeslot 16 carries the signalling on both the links.




Routing Options, Continued

This method solves the problem of dealing with routing issues, by placing the UCAI between two switches (called ‘A’ and ‘B’ in this example).

Two switch fix

In this case, UCAI is simply modifying the signalling on an otherwise ordinary link between two switches. The timeslots associated with link management and speech (usually, all except 16) are left intact. UCAI takes the signalling out to be processed.

To implement this method, configure all the nodes to have their signalling point codes allocated according to the signalling requirements.

In the example:

• switch ‘A’ talks with its point code of 2 to a remote point code of 1 • switch ‘B’ talks with its point code of 3 to a remote point code of 1, and • UCAI talks with its point code of 1 to both 2 and 3).

Switch ‘B’ is configured to route no calls to point code 1 and switch ‘A’ is configured to route calls to UCAI to point code 1.

This configuration can be performed on either a point code or a link basis (as illustrated in the previous examples). There is no requirement for excluding any timeslots from use (apart from the management and signalling ones, usually 0 and 16).

Configure UCAI with just 30 incoming and outgoing circuits, as follows: connect 1/2/0 to 1/3/0 for 32 except 0 and 16.



Configuring UCAI The following two case studies illustrate the configuration modes of the UCAI. Case studies

A GSM mobile operator has invested in a network that does not support CS-1 IN features. To allow it to provide a prepaid function, the operator deploys a service node solution that requires all prepaid calls to be trunked to the service node platform for service logic and then back to the eventual destination.

Loop back UCAI

This solution has obvious cost and scalability issues, but allows entry to the emerging prepaid mobile market. The operator is caught out by the unforeseen rapid growth of prepaid mobiles combined with the drastic reduction in charges due to strong competition. He now finds that the solution is prohibitively expensive and the limit of the solution’s scalability is reached.

Two UCAIs are installed (co-resident on hardware with prepaid service logic SCP), connected to the operator’s SS7 network via STPs. Loop-back trunks are deployed on each of the operator’s mobile service switching centres (MSC), and signalling for these trunks is routed to UCAIs. The GSM HLR (Home Location Register) is configured with a service flag, to route calls from pre-paid mobiles to UCAI trunks, allowing service logic to be invoked.

For mobile to mobile calls, the eventual destination of the call is not known, so routing between switches may be counter-productive, since the destination switch may need to route the call back or on to another switch. A possibility exists that, for calls to fixed phones or other mobile operators’ phones, the call could be triggered at the point of interconnect between the operators using an in-line UCAI. This would reduce the number of loop-backs required. However, the complexities of configuring switch routes that are based on calling party (being prepaid) and called party (whether fixed or other operator mobile), are considered too complex and costly in terms of man-power to be worth the saving in loop-back trunks.

This example shows a loop-back UCAI configuration. This configuration is optimal for triggering services:

Loop back UCAI example

• that often result in the call being terminated on the same switch from which it originated, or

• when the eventual destination for the call is unpredictable.




Configuring UCAI, Continued

An application service provider (ASP), offering advanced services to other operators via their own switch, wishes to offer services beyond the capabilities of the AIN build of software currently available on the switch. The vast majority of the ASP’s traffic originates from other networks, and traverses their switch to offer the service and route the call.

In line UCAI

In this case, in-line UCAIs are very helpful, as most of the traffic is via points of interconnection. A UCAI placed on the signalling line of the other operator’s switch and the ASP’s network can control all incoming calls, avoiding loop-backs on the ASP switch entirely. Some loop-backs may be required for traffic originating on the ASP’s network.

This example shows an in line or inter-switch UCAI configuration. This type of configuration is optimal for calls for which the vast majority of calls requiring UCAI processing originate from, or are eventually routed to, a network address that is not on the originating network switch, but which can be efficiently reached via the destination network switch.

In line UCAI example

Example: This diagram shows a network where:

• the originating switch is a local exchange (end office) • the destination switch is a trunk level or international switch (central office),

and • the service to be triggered via the UCAI is a national or international freephone

service.



Configuring IN Call Model Triggers This introduces the generic configuration requirements of the Oracle IN Call Model.

Overview

The Oracle IN Call Model is not a separate product, rather it is a set of libraries that is bound into a final useable interface (such as the VSSP).

This table describes the UNIX shell environment variables to be configured. Environment variables

Environment Variable Name

Description

Example Value

TDP_DEFINITIONS Defines the full path name of the Trigger Detection Point definition file.

/IN/service_packages/SLEE/etc/tdp.conf

The tdp.conf file has two sections: Trigger detection point (TDP) definition file 1 a number of configuration parameters, and

2 the trigger tables used to determine when to trigger a call to the SCF. Example: This text shows an example tdp.conf file: # A comment KEEP SD ETC RULES=6 3 3 1 3 request all 123 6 4 2 4 notify all 222 keep 3 1 3 request 2:122 3:222 5 keep

Note: All lines starting with # are treated as comments. If no TDP definition file is defined, a default action is taken where:

• ALL calls are triggered to the SCF with a service key of 1 (one) and a trigger point of 3 (analyzedInformation ), and

• none of the global configuration parameters are considered set.

The following configuration parameters may be set once on individual lines in the TDP definition file.

Global configuration parameters

Global Parameter Description KEEP SD If defined ALL all stop digits (defined by the BCD digit ’F’)

on the end of called party numbers are kept in the called party number. By default the stop digit is stripped from ALL triggered numbers.

CAMEL This parameter is intended for CAMEL testing purposes only and should not be defined under normal usage. If defined, the called party number is also copied into the intialDP’s calledPartyBCDNumber CAMEL parameter. The NOA of the called party number becomes the BCD number type.




Configuring IN Call Model Triggers, Continued


Global configuration parameters (continued)

Global Parameter Description ADDITIONALNUMS If defined, the IN Call Model will request all additional

numbers available from the underlying protocol and insert them into the InitialDP message sent to the SCP. All these additional numbers are placed into a G8 extension in the InitialDP except any additional calling party number that is placed in the additionalCallingPartyNumber field.

ETC RULES= c or ETC RULES= c s

If defined then additional EstablishTemporaryConnection (ETC) rules are used. If the integer c is defined, the correlationID in all ETC messages from the SCF are appended on to the end of the assistingSSPIPRoutingAddress that is used, the digits are padded to a width of c digits. If s is also defined, then the scfID of the ETC is also appended on afterwards in the same way. For example: With "ETC RULES=6 4" and an ETC message with: assistingSSPIPRoutingAddress =1111, correlationID =55, scfID =0x42 Then the actual assistingSSPIPRoutingAddress used will be "11110000550042"

USER LIB = library If defined the call model will use the user written shared object library specified by the full pathname library when dealing with ApplyCharging operations.

AC=a,b,c.... Sets the TCAP application context used by the call model to the comma separated list of OIDs supplied.

ORIG_PC= pc See note 1

If defined, all InitialDPs will be sent with an SCCP calling party (origination) address that includes a Point Code defined by the integer pc. Note: This value may be defined in hex using a prefix of 0x.

ORIG_SSN= ssn See note 1

If defined, all initialDP’s will be sent with an SCCP calling party (origination) address that includes a subsystem number defined by the integer ssn.

ORIG_GT=1, n, addr orORIG_GT=2, t, addr or ORIG_GT=3, t, p, addr or ORIG_GT=4, t, p, n, addr See note 1

If defined, all initialDP’s will be sent with an SCCP calling party (origination) address that includes a Global Title defined by the integers n, t, p and the number string addr.The initial value (1 to 4) identifies the Global Title type: • n is the NOA, • t is the Translation Type, • p is the Numbering Plan, and • addr is the address digits (0 to 9, A to F).




Global configuration parameters (continued)

Global Parameter Description DEST_PC= pc See note 2

If defined, all initialDP’s will be sent with an SCCP called party (destination) address that includes a Point Code defined by the integer pc. Note: This value may be defined in hex using a prefix of 0x.

DEST_SSN= ssn See note 2

If defined, all initialDP’s will be sent with an SCCP called party (destination) address that includes a subsystem number defined by the integer ssn.

DEST_GT=1, n, addr orDEST_GT=2, t, addr or DEST_GT=3, t, p, addr or DEST_GT=4, t, p, n, addr See note 2

If defined all initialDP’s will be sent with an SCCP called party (destination) address that includes a Global Title defined by the integers n, t, p and the number string addr.The initial value (1 to 4) identifies the Global Title type: • n is the NOA, • t is the Translation Type, • p is the Numbering Plan, and • addr is the address digits (0 to 9, A to F).

ACH WARN PERIOD=period

Sets the default ApplyCharging warning to occur period seconds before the end of the call.

ACH RESOURCE=ad Sets the default ApplyCharging warning announcement/tone to use the resource identified by the address digits ad. Note: This is only applicable if the underlying controlled call supports the ability to play announcements/tones.

ACH ANNOUNCE=messageId

Causes the default ApplyCharging warning to use announcement with message identifier messageId. Note: This is only applicable if the underlying controlled call supports the ability to play announcements/tones

ACS TONE=id,dur Causes the default ApplyCharging warning to use tone with identifier id for a duration of dur seconds. Note: This is only applicable if the underlying controlled call supports the ability to play announcements/tones

If none of these entries is defined all InitialDPs will be sent without an SCCP calling party address.

Note 1

After any global parameters have been set, the configuration file may take one or more trigger detection point (TDP) definitions.

Trigger detection point definitions

Each line defines a single trigger; its trigger parameter values that get sent and the conditions under which it gets sent.

Each line takes the following form: <tdp> <svcKey> <eventType> <msgType> <cgPn> <cdPn> [<wild>] [keep]






Trigger detection point definitions (continued)

The table below defines the meanings and forms of these parameters.

Global Parameter Value

Type

Description

<tdp> integer This integer value defines the point that the TDP is triggered at. Together with <cgPn>, <cdPn> and <wild> it defines the condition that the trigger will fire on. See the TDP Event Type table for a list of valid values and meanings.

<svcKey> integer This parameter defines the serviceKey value that will be inserted into the initialDP message when this trigger fires.

<eventType> integer This parameter defines the eventTypeBCSM value that will be inserted into the InitialDP message when this trigger fires. See the TDP Event Type table for a list of valid values and meanings. Generally this will be the same value as <tdp>.

<msgType> request or notify This parameter defines whether the TDP is sent as a TDP-R (request) or TDP-N(notify). Generally request is used here.

<cgPn> <num> or <nat>:<num> or all

This parameter defines the calling party numbers that will trigger the TDP. Together with <tdp>, <cdPn> and <wild> it defines the condition that the trigger will fire on. • <num> defines the prefix of the calling party digits,

numbers must begin with these digits for the trigger to fire.

• <nat> is optional and defines additionally a nature of address (NOA) of the calling party that must match for the trigger to fire. If not provided a nature of 2 (unknown) is assumed.

If all is defined then ALL calling party numbers will match.

<cdPn> <num> or <nat>:<num> or all

This parameter defines the called party numbers that will trigger the TDP. Together with <tdp>, <cgPn> and <wild> it defines the condition that the trigger will fire on. • <num> defines the prefix of the called party digits,

numbers must begin with these digits for the trigger to fire.

• <nat> is optional and defines additionally a nature of address (NOA) of the called party that must match for the trigger to fire. If not provided a nature of 2 (unknown) is assumed.

If all is defined then ALL called party numbers will match.




Trigger detection point definitions (continued)

Global Parameter Value

Type

Description

<wild> integer This optional parameter defines the number of digits that must be present in the called party numbers before the TDP will trigger. Together with <tdp>, <cgPn> and <cdPn> it defines the condition that the trigger will fire on. If set the trigger will not fire until the called party number has this number of digits.

Note: The <wild> parameter can be set to a special value of "stop". If it is set to this value, then the trigger will only fire when a stop digit is received.

keep - If this optional flag is defined then all numbers triggered by this TDP will keep their stop digits (if they have one).

The following table defines the list of TDPs as defined by the CS-1 standard. It also defines the point at which the trigger will be instantiated by the Oracle IN Call Model.

TDP event type values

TDP CS-1 Trigger Name Call Model TDP Creation Point 1 origAttemptAuthorized digitsReceived

2 collectedInfo digitsReceived

3 analyzedInformation digitsReceived

4 routeSelectFailure released (cause != 16, 17, 18, 19, 21 or 31)

5 oCalledPartyBusy released (Aparty, cause==17)

6 oNoAnswer released (Aparty, cause==18, 19 or 21)

7 oAnswer answered(Aparty)

8 oMidCall not supported

9 oDisconnect released (Aparty, cause==16 or 31)

10 oAbandon released (Aparty, cause==16 or 31)

12 termAttemptAuthorized digitsReceived

13 tCalledPartyBusy released (Bparty, cause==17)

14 tNoAnswer released (Bparty, cause==18, 19 or 21)

15 tAnswer answered(Bparty)

16 tMidCall not supported

17 tDisconnect released (Bparty, cause==16 or 31)

18 tAbandon released (Bparty, cause==16 or 31)

100 n/a ringing (Aparty) 101 n/a ringing (Bparty)



Chapter 3

Background Processes Overview

This chapter explains the processes which run automatically as part of the application. These processes are started automatically by one of the following:

Introduction

• inittab • crontab, or • SLEE.

Note: This chapter also includes some plugins to background processes which do not run independently.


vssp ............................................................................................................... 44

In this chapter



vssp vssp is the binary which runs the UCAI application. Purpose

No other binaries are installed with UCAI.

This task is started by the SLEE, by the following lines in SLEE.cfg: Startup

INTERFACE=VSSP vssp.sh /IN/service_packages/VSSP/bin EVENT

Notes:

• The actual startup script name may vary. • If you have configured UCAI to run without the SLEE, you can also start UCAI

from the command line.

vssp accepts the following parameters from vssp.config. Configuration

unset option slee. set option syslog. set option stats. set cdr file="<filename>"; set option debug. set option mtp debug. set option stats. set startup time <secs>. set network <network identifier>.

filter iam drop [{<number>,} <number> and] <number>. connect <circuit> to <circuit> [for <number of circuits>].

vssp supports these parameters from m3ua.config. M3UA configuration

asp port <port> addrs {<ip_address>}

; sgp itp1

port <port> addrs {<ip_address>}

; gateway sg1 {

sgp itp1 key <int>; pc {<int>, [<int>, ...]};

} as

pc <int> gateway {sg1}

;




vssp, Continued

Here are the parameters for vssp. Parameters

Command line parameters vssp supports the following command line parameters.

Note: These are usually specified in the startup script, vssp.sh.

-c <configuration file> Specifies the filepath and name of the vssp configuration file.

Default: none Notes: (Required.)

-k <keyfile> Specifies the filepath and name of the keyfile file which sets the maximum number of circuits UCAI can use.

Default: keyfile Notes: (Optional.)

-m <m3ua configuration file> Specifies the filepath and name of the M3UA configuration file.

Default: m3ua.config Note: (Optional.)




vssp, Continued


Parameters (continued)

Standard options These parameters are available for all types of UCAI installation.

cdr file If set to a valid filepath, vssp will log CDRs to the specified file.

Default: off Allowed: string Format: set cdr file = "<filename>"; Note: The equals sign (=) is optional.

connect Defines the circuit loops for vssp. For more information about configuring circuit loops, see Configuring circuit loops (on page 24).

Default: none Allowed: connect <circuit> to <circuit>[ for <number

of circuits>][ except <cic>[ and <cic>]]. Note: The full stop or semi-colon on the end is essential if you are

not specifying a number of circuits.

debug Turns vssp debug output on or off. If enabled, an operator can debug SSP functionality, as well as lower-level ISUP functionality. The SSP functionality details how calls are being progressed and the ISUP debugging prints out all the ISUP messages sent and received.

Default: off Format: set option debug Notes: This output is sent out on the debugging output of the VSSP

(stdout).

filter Drops specified parameters within an IAM. Drops the parameters with the name value of any of the given <number>s on an outgoing IAM message.

Default: empty set Format: filter iam drop [{<number>,} <number> and]

<number> Where: • square brackets enclose optional entries, and • curly brackets enclose zero or more entries.

Note: Mandatory parameters cannot be dropped.



vssp, Continued



limit Sets a CAPS limit on vssp. The first number is the CAPS limit and the second is the release cause to be used if the CAPS limit is exceeded.

Default: Cause defaults to 42. Format: set option limit to <number> caps cause

[<cause number>] Notes: The "to" can be replaced with an equals sign.

<cause number> is optional.

mtp debug Turns mtp traffic output from vssp on or off. If on, a hexadecimal representation of all the ISUP messages is written to the vssp’s debugging output (stdout).

Default: off Format: set option mtp debug

network Sets the network identifier in the MTP3 header to be the specified value.

Default: 2 Note: This only applies to the M3UA and Data Kinetics stacks.

2 is national network.

set ica iam cpc Sets the calling party category on the legs of ICA calls. The CPC can be set on just the A-leg or on both legs.

Default: none Format: set ica iam cpc <A-leg number> [<B-leg

number>] Where: • number = the override value for the calling party

category. Notes: By default, the CPC set for the A-leg number will be used for

the B-leg. There is an Oracle extension to INAP that allows the CPC to be set on the A-leg of an ICA-created call. Service logic may override a set B-leg value.

slee Enable or disable the interface between vssp and the SLEE. If the SLEE interface is disabled, vssp acts simply as a call router, in effect providing a null service.

Default: on Format: unset option slee Note: This option should only be used for debugging.



vssp, Continued



startup time Seconds vssp takes to reset all its circuits at start up.

Default: 15 Allowed: number Format: set startup time = <secs> Note: If there are a large number of circuits, the default may need

to be increased to avoid temporary congestion of the network. The equals sign (=) is optional.

stats If set, vssp will log a basic calculation of the number of calls being processed by vssp per second.

Default: off Format: set option stats

syslog Send error messages to the syslog as well as UNIX stderr. Any errors will now be logged to syslog. The syslog identifier is set to VSSP, the facility is set to LOG_USER and errors are logged at level LOG_ERR.

Default: off Format: set option syslog



vssp, Continued



M3UA parameters The M3UA configuration uses a cascading definition structure. The first parameter (file) is defined by four other parameters. Those four parameters are in turn defined by other parameters set later in the file.

For more information about how these parameters work together to configure vssp, see M3UA Configuration (on page 28).

vssp supports these parameters from the m3ua.config file.

Note: These parameters are only available if you have installed the M3UA version of UCAI.

as Application Server definition. Assigns ASPs to ASs.

Default: Syntax: as pc <number> gateway { <gateway_list>};

Where: • number = Point Code number of the AS • gateway_list = list of SGs the AS is peered with.

Note:

asp Defines the local ASP.

Default: Syntax: asp port <port> addrs {<ip>};

Where: • port = the port the AS process is running on • ip = the ip address the AS process is running on.

gateway Gateway definitions.

Default: Syntax: gateway <identifier>

{ sgp itp1 key <key> pc {<pcs>};

} Where: • identifier = a unique identifier • keyed_sgsp = a <keyed sgsp> parameter • pcs = a list of comma separated point codes.



vssp, Continued


sgp Signalling Gateway Process definitions.

Default: Syntax: sgp itp1 port <port> addrs {<ip>};

Where: • port = the port the SG process is running on • addrs = the ip address the SG process is running on.

This is an example of the vssp.config file (comments have been removed). Example configuration - vssp.config set option slee.

set option syslog. set option stats. set cdr file="cdr.log"; #set option debug. #set option mtp debug. set ica iam cpc 10; connect 1/2/1 to 1/2/17 for 15;

This text shows an example M3UA configuration: Example M3UA configuration file

#start file asp port 6969 addrs {192.168.26.117}; sgp itp1 port 2905 addrs {192.168.26.215}; gateway sg1 {

sgp itp1 key 6969; pc {999, 4805, 4807};

} as pc 4701 gateway {sg1}; #end file

Using more whitespace, this file could also be displayed as follows: #start file asp

port 6969 addrs {192.168.26.117}

; sgp itp1

port 2905 addrs {192.168.26.215}

; gateway sg1 {

sgp itp1 key 6969; pc {999, 4805, 4807};

} as




vssp, Continued

Example M3UA configuration file (continued)

pc 4701 gateway {sg1}

; #end file

vssp writes error messages to the system messages file, and also writes additional output to the following default:

Output

/IN/service_packages/VSSP/output/outputFile.log

Note: May vary as per configuration in the startup script.



Universal Call Agent for ISUP Page 53

Chapter 4

Troubleshooting Overview

This chapter explains common troubleshooting procedures and problem symptoms.

Introduction

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 ......................................................... 54 Possible Problems ......................................................................................... 56

In this chapter

Technical Guide


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

Introduction

The vssp process supports debug. To turn on debug for vssp, set the debug option in the vssp.config file and reload the configuration.

Turning on debug

For information about turning on debug, see debug (on page 46).

Important: Turning on debug increases the load on the vssp process. It should only be used on a production platform when absolutely necessary.

The vssp process supports debug for its M3UA. To turn on M3UA debug for vssp, set the mtp debug option in the vssp.config file and reload the configuration.

Turning on M3UA vssp debug

For information about turning on debug, see mtp debug (on page 47).

Important: Turning on debug increases the load on the vssp process. It should only be used on a production platform when absolutely necessary.

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).

Checking current processes

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.

To check the details of an installed package, use the pkginfo command. Checking installed packages 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 VERSION: 3.1.0 VENDOR: Oracle PSTAMP: smsNode20041020104925 INSTDATE: Oct 20 2004 13:15 EMAIL: [email protected] STATUS: completely installed FILES: 348 installed pathnames




Common Troubleshooting Procedures, Continued

Checking installed packages (continued)

39 directories 89 executables 152448 blocks used (approx)

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

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

Checking network connectivity

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.

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.

Checking configuration files

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.



Possible Problems This topic lists common problems and actions which can be taken to investigate or solve them. This list enables you to check for alarms based on the overall behaviour you are experiencing.

Introduction

If any of the following are true, it may indicate that the circuit loop configuration is mismatched:

Circuit mismatches

1 One party can hear the other, but not the other way round. 2 Different calls connected together. 3 Total silence at both ends. Check the vssp.config file for possible mismatches. For more information about configuring circuit loops, see Configuring circuit loops (on page 24).



Chapter 5

System Alarms Overview

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

Introduction


Alarm Topic Description ................................................................................ 58 VSSP ISUP Interface alarms ........................................................................ 60 M3UA interface alarms .................................................................................. 82

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.

Alarm generation

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

This table describes the alarms severity levels. 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: Alarm 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)

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.

Alarm text and variables



Alarm Topic Description, Continued

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.

Further information

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



VSSP ISUP Interface alarms This table defines the Critical messages for the VSSP ISUP interface. Critical Errors -

vssp

Alarm Text Reason Remedy ISUPIF(123) CRITICAL =123 INStateMachine.cc@123: Timer 123 not yet implemented

Internal SSF error. Contact level 1 support.

ISUPIF(123) CRITICAL =123 INStateMachine.cc@123: INControlledCall does not support correlation id


ISUPIF(123) CRITICAL =123 INStateMachine.cc@123: Failed to create a new call model instance


ISUPIF(123) CRITICAL =123 INStateMachine.cc@123: SSF received invalid BEGIN component 123

SCP sent a TC-BEGIN which was not an initiateCallAttempt.

Contact level 1 support.

ISUPIF(123) CRITICAL =123 INStateMachine.cc@123: SSF received no BEGIN component

TC-BEGIN message was received from SCF with no INAP component.


ISUPIF(123) CRITICAL =123 INStateMachine.cc@123: Invalid TDP configuration line 123 ofZZZ

tdp.conf has error on indicated line. Refer to application expert. Correct specified error in tdp.conf.

ISUPIF(123) CRITICAL =123 INStateMachine.cc@123: TDP 123 is not supported at line 123 ofZZZ

Specified line of specified tdp.conf is invalid.

Refer to application/signalling expert. Correct specified line in tdp.conf.




VSSP ISUP Interface alarms, Continued

This table defines the error messages for the VSSP ISUP interface. Errors

Alarm Text Reason Remedy 123/123/123:123:Attempt to send RLC with params!

Sending RLC with parameters. Refer to application/signalling expert. Configure not to send RLC with parameters.

123:Setting signal handler for ABC123 failed, status ABC123, errno 123!

Kernel error on current machine. Refer to UNIX/application expert first. If problem persists, contact level 1 support.

cmn::Exception received in main():ZZZ

Kernel error on current machine. Refer to UNIX/application expert first. If problem persists, contact level 1support.

ERROR from ABC123 COO received after changeover completeZZZ

COO received after changeover complete.


ERROR from ABC123 Erroneous FSN in COAZZZ

ISUP message unknown. Refer to application/signalling expert. Check the MTP2. Report status to level 1 support.

ERROR from ABC123 Failed to receive CBAZZZ

CBA not received. Contact level 1 support.

ERROR from ABC123 Failed to receive COAZZZ

COA not received. Contact level 1 support.

ERROR from ABC123 Failed to receive LIAZZZ

LIA not received. Contact level 1 support.

ERROR from ABC123 Failed to receive LUAZZZ

LUA not received. Contact level 1 support.

ERROR from ABC123 Failed to receive LUNZZZ

LUN not received. Contact level 1 support.

ERROR from ABC123 Failed to send LSSU/FISU to driverZZZ

LSSU or FISU not sent. Contact level 1 support.

ERROR from ABC123 Failed to send SU to lower layerZZZ

Failed to send SU to lower layer. Contact level 1 support.

ERROR from ABC123 Failure to retrieve BSNTZZZ

Failure to retrieve BSNT. Contact level 1 support.

ERROR from ABC123 Frames added to garbage queueZZZ

Frames added to garbage queue. Contact level 1 support.






Errors (continued)

Alarm Text Reason Remedy ERROR from ABC123 Intern`l software error (SLTM)ZZZ

Internal software error (SLTM). Contact level 1 support.

ERROR from ABC123 Internal software error (SNMM)ZZZ

Internal software error (SNMM). Contact level 1 support.

ERROR from ABC123 Invalid ID in message HDRZZZ

Invalid ID in message HDR. Contact level 1 support.

ERROR from ABC123 Invalid l2_llid in HDR structureZZZ

Invalid l2_llid in HDR structure. Contact level 1 support.

ERROR from ABC123 Length Error, SU not transmittedZZZ

Length error, SU not transmitted. Contact level 1 support.

ERROR from ABC123 Messages discarded due to overflow of Re-Routing bufferZZZ

Messages discarded. Contact level 1 support.

ERROR from ABC123 MSU too long for bufferZZZ

MSU too long for buffer. Contact level 1 support.

ERROR from ABC123 MTP2 Failed to initialiseZZZ

MTP2 failed to initialise. Contact level 1 support.

ERROR from ABC123 MTP2 failure to perform retrievalZZZ

MTP2 failed to perfrom retrieval. Contact level 1 support.

ERROR from ABC123 MTP2 memory allocation errorZZZ

MTP2 memory allocation error. Contact level 1 support.

ERROR from ABC123 MTP2 unable to accept primitiveZZZ

MTP2 unable to accept primitive. Contact level 1 support.

ERROR from ABC123 MTP3 attempt to re-use active timer resourcZZZ

MTP2 attempt to re-use active timer resource.


ERROR from ABC123 MTP3 Failed to allocate T_FRAMEZZZ

MTP3 failed to allocate T_FRAME. Contact level 1 support.

ERROR from ABC123 MTP3 failed to send MSU to lower layerZZZ

MTP3 failed to send MSU to lower layer (MTP2).


ERROR from ABC123 MTP3 unable to accept primitiveZZZ

MTP3 unable to accept primitive. Contact level 1 support.





Errors (continued)

Alarm Text Reason Remedy ERROR from ABC123 MTP3 unable to allocate MSGZZZ

MTP3 Unable to allocate message. Contact level 1 support.

ERROR from ABC123 No free buffers in MTP2 transmit poolZZZ

No free buffers in MTP2 pool. Contact level 1 support.

ERROR from ABC123 No free frames in MTP3 transmit poolZZZ

No free buffers in MTP3 pool. Contact level 1 support.

ERROR from ABC123 No room to add level 2 header, SU not transmittedZZZ

No room to add L2 header, SU not transmitted.


ERROR from ABC123 Retrieval failureZZZ

Retrieval failure. Contact level 1 support.

ERROR from ABC123 Signalling link test failureZZZ

Signalling link test failure. Refer to application/signalling expert. Check links.

Exception received in main():ZZZ

Internal error. Contact level 1 support.

Failed to close CDR file!

CDR file close failed. Contact level 1 support.

Failed to getrusage: 123!

getrusage failed. Contact level 1 support.

Failed to open CDR fileZZZ

Kernel communication/disk error. Check the following: 1) Does the directory where this file is being created exist? 2) Are the correct permissions set for the directory where this file is being created? 3) Is the directory where this file is being created corrupt? 4) Is the disk full? 5) Contact level 1 support.

Failed to release message, status ActiveA, errno 123!


Got MSU:ZZZ Internal error. Contact level 1 support. ISUP 123/123/123 msg 123:123:Malformed ISUP message:ZZZ

Malformed ISUP message. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

ISUP 123/123/123 msg 123:123:rx unknown message!

Unknown ISUP message. Contact level 1 support.





Errors (continued)

Alarm Text Reason Remedy ISUP 123/123/123 spare 123:123:Spare bits set in COT?

COT has non-zero spare bits. Contact level 1 support.

ISUP 123/123/123 timeout ABC123:123:Internal error!


ISUP 123/123/123 type 123 offset 123:123:Unknown circuit on group ABC123!

Circuit in group unknown. Refer to application/signalling expert. Confirm configuration.

ISUP 123/123/123 type 123:123:Unknown group ABC123 type!

Group type unknown. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

ISUP 123/123/123:123:Bad RAS on CGQ!

CGQ has invalid RAS. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

ISUP 123/123/123:123:BLA long (T123) timeout!

T13 expired. Refer to application/signalling expert. Check links.

ISUP 123/123/123:123:Internal error!


ISUP 123/123/123:123:No USI on IAM!

IAM doesn't have USI. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

ISUP 123/123/123:123:Remote circuit unequiped!

UCIC received. Refer to application/signalling expert. Confirm configuration.

ISUP 123/123/123:123:UBA long (T123) timeout!

T15 expired. Refer to application/signalling expert. Check links.

ISUP 123/123/123:1603:No TMR or wrong size on IAM!

IAM TMR invalid. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

ISUP ABC123 msg 123:123:Unknown ISUP message!ZZZ

ISUP message unknown. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy ISUP: Runt MSU!ZZZ MSU too small. Refer to application/signalling

expert. Check the ISUP. Report status to level 1 support.

ISUPIF(123) ERROR =123 INStateMachine.cc@123: E2:No such TDP config fileZZZ

Kernel communication/disk error. Check the following: 1) Does the directory where this file is being created exist? 2) Are the correct permissions set for the directory where this file is being created? 3) Is the directory where this file is being created corrupt? 4) Is the disk full? 5) Contact level 1 support.

ISUPIF(123) ERROR =123 INStateMachine.cc@123: Error loadinglibraryZZZ

User charging shared library not found.

Check the value specified for the shared library on the line "USER LIB" in TDP configuration file. 1) Check file exists and is not corrupt. 2) Check file permissions. 3) Contact level 1 support.

ISUPIF(123) ERROR =123 INStateMachine.cc@123: ETC Failed with cause 123

Attempt to Establish Temporary Connection has failed with specified network cause.

Refer to application/signalling expert. Lookup release casue in ISUP standard Q.763 to determine problem.

ISUPIF(123) ERROR =123 INStateMachine.cc@123: Event ABC123()in state ABC123 is undefined


ISUPIF(123) ERROR =123 INStateMachine.cc@123: SCF Dialogue (TC-END) while in stateZZZ

Dialogue to SCF was ended (by TC-END) without being in Idle state but in state specified.


ISUPIF(123) ERROR =123 INStateMachine.cc@123: SSF failed to connect to resource

SCP sent ConnectToResource which is not supported.

Refer to application/signalling expert. Ensure service logic uses EstablishTemporaryConnection instead.

ISUPIF(123) ERROR =123 INStateMachine.cc@123: SSF failed to disconnect from resource

SSF failed to disconnect from connected resource.






Errors (continued)

Alarm Text Reason Remedy ISUPIF(123) ERROR =123 INStateMachine.cc@123: SSF received INAP error id=123

Unrecognised INAP error was received from SCP.


ISUPIF(123) ERROR =123 INStateMachine.cc@123: SSF received unrecognised INAP operation id=123

SCP sent an unrecognised or unsupport INAP operation.


ISUPIF(123) ERROR =123 INStateMachine.cc@123: SSF received unrecognised INAP result id=123

Unrecognised INAP result was received from SCP.


ISUPIF(123) ERROR =123 INStateMachine.cc@123: SSF received unrecognised TCAP componentZZZ

Unrecognised TCAP component was received from SCP.


ISUPIF(123) ERROR =123 INStateMachine.cc@123: Unexpected UI response from IN call 123


ISUPIF(123) ERROR =123 sleeINCallModel.cc@123: Unknown service key 123

Specified service key is not provisioned in SLEE.

Refer to application expert. It is required to configure the service key into SLEE configuration file (SLEE.cfg).

LIU ABC123 status AIS Cleared

AIS cleared. No resolution.

LIU ABC123 status AIS Detected

AIS detected. Refer to application/signalling expert. Check the specified link. Report status to level 1 support.

LIU ABC123 status Frame Slip

Frame slip. Refer to application/signalling expert. Check the specified link. Report status to support.

LIU ABC123 status Frame Sync Loss

Frame sync lost. Refer to application/signalling expert. Check the specified link. Report status to level 1 support.

LIU ABC123 status Frame Sync OK

Frame sync restored. No resolution. If problem persists, contact level 1support.

LIU ABC123 status PCM Loss

PCM lost. Refer to application/signalling expert. Check the specified link. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy LIU ABC123 status PCM Restored

PCM restored. No resolution. If problem persists, contact level 1support.

LIU ABC123 status Remote Alarm

Remote alarm received. Refer to application/signalling expert. Check the specified link. Report status to level 1 support.

LIU ABC123 status Remote Alarm Cleared

Remote alarm cleared. No resolution. If problem persists, contact level 1support.

MTP PAUSE with invalid point code!

MTP-PAUSE of invalid point code. Refer to application/signalling expert. Check point code

MTP RESUME with invalid point code!

MTP-RESUME wth invalid point code.

Refer to application/signalling expert. Check the specified point code. Report status to level 1 support.

MTP STATUS remote user unavailableZZZ

MTP-STATUS (RUU) received. Refer to application/signalling expert. Check the specified point code. Report status to support.

MTP2 ABC123 event Abatement of congestionZZZ

Congestion now abated. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 event Abnormal FIBR/BSNRZZZ

Abnormal FIBR/BSNR. Refer to application/signalling expert. Check MTP 2.

MTP2 ABC123 event Congestion caused discardZZZ

Congestion caused message discard.

No resolution. If problem persists, contact level 1support.

MTP2 ABC123 event Excessive congestionZZZ

Excessive congestion. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 event Excessive delay of ackZZZ

ACK delayed too much. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 event Excessive error rateZZZ

Excessive error rate. Refer to application/signalling expert. Check the specified link. Report status to level 1 support.

MTP2 ABC123 event Onset of congestionZZZ

Congestion onset. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 event SIOS receivedZZZ

SIOS received. No resolution.

MTP2 ABC123 event Stop request receivedZZZ

Stop request received. No resolution.





Errors (continued)

Alarm Text Reason Remedy MTP2 ABC123 event Unexpected SIE receivedZZZ

Unexpected SIE. Refer to application/signalling expert. Check MTP 2.

MTP2 ABC123 event Unexpected SIN receivedZZZ

Unexpected SIN. Refer to application/signalling expert. Check MTP 2.

MTP2 ABC123 event Unexpected SIO receivedZZZ

Unexpected SIO. Refer to application/signalling expert. Check MTP 2.

MTP2 ABC123 state Aligned, Not Ready

MTP2 now aligned but not ready. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 state Aligned, Ready

MTP2 now aligned and ready. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 state In Service

MTP2 now in service. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 state Initial Alignment

MTP2 now performing initial alignment.


MTP2 ABC123 state Out of Service

MTP2 out of service. No resolution. If problem persists, contact level 1support.

MTP2 ABC123 state Processor Outage

MTP2 reports processor outage. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Adjacent SP accessibleZZZ

MTP3 reports remote PC available. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Adjacent SP inaccessible

MTP3 reports remote PC unavailable.


MTP3 at ABC123 Changeback

MTP3 reports change back. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Changeover

MTP3 reports change over. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Congestion cleared

MTP3 reports congestion. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Destination available

MTP3 reports destination available. No resolution. If problem persists, contact level 1support.





Errors (continued)

Alarm Text Reason Remedy MTP3 at ABC123 Destination unavailable

MTP3 reports destination unavailable.


MTP3 at ABC123 Link set failure

MTP3 link set failure. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Link set recoveredZZZ

MTP3 link set recovered. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 MSU discarded due to congestion

MSU discarded because of congestion.


MTP3 at ABC123 Remote processor outage

MTP3 reports PO. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Remote processor outage cleared

MTP3 reports PO cleared. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Restoration commenced

MTP3 link restoration started. No resolution. If problem persists, contact level 1support.

MTP3 at ABC123 Signalling link congestion

MTP3 signalling link congested. No resolution. If problem persists, contact level 1support.

MTP3 PC ABC123 is congested.

MTP3 PC congested. No resolution. If problem persists then contact support.

MTP4 ABC123/ABC123 length 123:123:Runt MSU!

Small MSU received. No resolution. If problem persists, contact level 1support.

MTP4 ABC123:123:Unknown circuit!

Unknown circuit. Refer to application expert. The unknown circuit needs to be correctly configured.

Process timeouts gavce time value of 123,123!


Select status was ABC123 with errno 123!


Select status was ActiveA with errno 123 for timeout 123/123!


Send failed, status ActiveA, errno 123!


SINAP errno 123:123:ca_get_msu failed!

SINAP error. Contact level 1 support.





Errors (continued)

Alarm Text Reason Remedy SINAP length 123:123:RUOK with data?


SINAP length 123:123:Truncated PAUSE/RESUME message!


SINAP length 123:123:Truncated STATUS message!


SINAP Message not understood!ZZZ


SINAP status ABC123 errno 123:123:ca_put_msu for raw failed!


SINAP status ABC123 errno 123:123:ca_register failed!


SINAP statusABC123 errno 123:123:ca_get_msg failed!


SINAP type ABC123:123:Invalid PAUSE/RESUME type!


SleeException received in main():ZZZ


std::exception received in main():ZZZ


std::logic_error received in main():ZZZ


std::runtime_error received in main():ZZZ


Unknown exception received in main() - exiting


VSSP :1317:makeCall unable to allocate call model!


VSSP 123/123/123,123/123/123 event 123:123:Unknown CPG event!

CPG event unknown. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123 filler ABC123:123:IAM with non-zero filler nibble!

non-zero filler nibble on IAM. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 leg 123 ok ABC123 state ActiveA:123:COT not on A-leg!

COT not on A-leg. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 leg 123 state ActiveA:123:CCR not on A-leg!

CCR not on A-leg. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 leg 123 state ActiveA:123:LPA not on B-leg!

LPA not on B-leg. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 leg 123 state ActiveA:123:RSC in unknown state!

Interal error. Contact level 1 support.

VSSP 123/123/123,123/123/123 leg 123:123:INR not from B-leg!

INR not on a B-leg. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 leg 123:123:Internal error!


VSSP 123/123/123,123/123/123 leg 123:123:Unexpected RLC!

RLC unexpected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 leg A and B:123:Reset circuit ignored!

RSC ignored (T17 expired). Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 leg A:123:Reset circuit ignored!






Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123 leg ABC123:123:RSC on unknown leg!

RSC on unknown leg. Refer to application/signalling expert. Confirm configuration.

VSSP 123/123/123,123/123/123 leg B:123:Reset circuit ignored!


VSSP 123/123/123,123/123/123 length 123:123:Invalid hop counter length!

Hop counter length invalid. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 ok ABC123 state ActiveA:123:COT in wrong state!

COT in unexpected state. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 ok ABC123:123:SCF too slow for continuity!

SCF failed to respond in time for COT.


VSSP 123/123/123,123/123/123 request ABC123:123:INR wants unknown information!

INR requested unknown information. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state Active:123:B-CPG when active?

Internal error. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA alarm ABC123:123:Internal error!


VSSP 123/123/123,123/123/123 state ActiveA leg 123:123:RLC unexpected!

RLC unexpected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA leg 123:123:SUS when not active!

SUS when not active. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123 state ActiveA leg 123:123:Unexpected RES!

RES unexpected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA to ActiveA:123:Internal error!


VSSP 123/123/123,123/123/123 state ActiveA, leg 123:123:Internal error!


VSSP 123/123/123,123/123/123 state ActiveA:123:A-leg ACM!

A-leg ACM. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:A-leg CPG!

CPG on A-leg. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:ANM on A-leg!

ANM on A leg. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:A-RLC unexpected!

A-RLC unexpected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:A-SAM unexpected!

A-SAM unexpected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:B-ACM without IAM!

B-ACM without IAM. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:B-ANM before IAM!

B-ANM before IAM sent. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123 state ActiveA:123:B-CON with no B-IAM!

B-CON with no B-IAM. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:B-CPG unexpected!

B-CPG unexpected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:B-leg SAM!

SAM on B-leg. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:CCR in wrong state!

CCR in wrong state. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:IAM on B!

IAM on B-leg. Refer to application/signalling expert. Confirm configuration, both local and remote.

VSSP 123/123/123,123/123/123 state ActiveA:123:INR when not expected!

INR when not expected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:Internal error!


VSSP 123/123/123,123/123/123 state ActiveA:123:LPA in wrong state!

LPA in wrong state. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:Second IAM when waiting for RLC!

Second IAM. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 state ActiveA:123:Unexpected IAM!

IAM unexpected. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123 state Route:123:Second IAM with outgoing call!

Internal error. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123 timeout ABC123:1123:Internal error!


VSSP 123/123/123,123/123/123 value 123:123:Bad call model result (IAM)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (SAM)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (B-ACM)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (ANM ringing)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (ANM answered)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (CON ringing)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (CON answered)!






Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (B-REL)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (A-REL)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (A-ACM)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (B-ANM)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (A-ANM)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (A-CON)!


VSSP 123/123/123,123/123/123 value ABC123:123:Bad call model result (A-REL, o/g)!


VSSP 123/123/123,123/123/123:123:A-ACM after A-ANM!

A-ACM after A-ANM. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:A-REL and B-REL long timeout!

A-REL and B-REL long timeout (T5). Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:A-REL long timeout!

A-REL long timeout (T5). Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123:123:A-RES when not suspended?

A-RES when not suspended. Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:A-RLC unexpected!

A-RLC unexpected Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-ACM after B-ANM!

B-ACM after B-ANM Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-ACM when Idle!

B-ACM when idle Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-ACM with Idle B, clearing A!

B-ACM with idle leg Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-ACM with Idle B, resettingA!

B-ANM with idle leg Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-ANM duplicated!

B-ANM duplicated Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-ANM on idle circuit!

B-ANM when idle Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-ANM when waiting for A-RLC!

B-ANM when waiting for A-RLC Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-CON after B-ANM!

B-CON after B-ANM Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-CON when Idle!

B-CON when idle Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123:123:B-CON when waiting for A-RLC!

B-CON when waiting for A-RLC Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-CPG when Idle!

B-CPG when idle Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-CPG when waiting for A-RLC!

B-CPG when waiting for A-RLC Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-REL long timeout with follow-on!

B-REL long timeout (T5) Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-REL long timeout!

B-REL long timeout (T5) Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-REL on blocked circuit.

B-REL on blocked circuit Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:B-RES when not suspended?

B-RES when not suspended Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:Call model failed to complete (A-REL)!

Internal error Contact level 1 support.

VSSP 123/123/123,123/123/123:123:CON on A-leg!

CON on A-leg Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:Duplicate A-ACM!

Duplicate A-ACM Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:Duplicate B-ACM!

Second B-ACM Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123:123:IAM with hop counter zero!

IAM with zero hop count Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:INR requests charging!

Charging requested in INR Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:INR requests holding!

Holding requested in INR Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:Internal error!


VSSP 123/123/123,123/123/123:123:LPA without CCR!

LPA without CCR Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:LPA without continuity check!

LPA without continuity check Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:No call model available!


VSSP 123/123/123,123/123/123:123:SAM after bad IAM!

SAM after bad IAM Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:SAM when Idle!

SAM when idle Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:SAM zero length!

SAM zero length Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:Unexpected A-RLC!

Unexpected A-RLC Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP 123/123/123,123/123/123:123:Unusual cause!ZZZ

Cause unusual Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.





Errors (continued)

Alarm Text Reason Remedy VSSP 123/123/123,123/123/123:123:Zero digit odd IAM!

IAM with called odd but zero length Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP attempt to configure too many circuits, limited to 123!

License limits number of circuits Refer to application expert. It is likely that you will need to purchase license upgrade.

VSSP corrupt keyfile, limited to 123 circuit pairs!

Keyfile corrupt Refer to application expert. You may need to purchase license upgrade.

VSSP key file corrupt! Limited to 123 circuit pairs!

Keyfile corrupt Refer to application expert. You may need to purchase license upgrade.

VSSP No key file, limited to 123 circuit pairs!

No key Refer to application expert. It is likely that you will need to purchase license upgrade.

VSSP no license key, limited to 123 circuit pairs!

No license key Refer to application expert. It is likely that you will need to purchase license upgrade.

VSSP state ActiveA:123:call model progress but no params!


VSSP to ABC123 FROM ABC123:123:No free circuits for outgoing call!

No free circuits Refer to application/signalling expert. Add circuits and confirm configuration.

VSSP: SINAP status -123 errno 123:123:ca_register failed!

Internal error Refer to application/signalling expert. Check the ISUP. Report status to level 1 support.

VSSP: Sinap terminate status was ABC123 with errno 123!





This table defines the warning messages for the VSSP ISUP interface. Warnings

Alarm Text Reason Remedy ISUPIF(123) WARNING =123 INStateMachine.cc@123: Request to arm event 123 without required legID - assuming Leg1

SCP attempted RequestReportBCSMEvent request without a mandatory legID

Contact support

ISUPIF(123) WARNING =123 INStateMachine.cc@123: Operation ABC123 sent in TC-END! Operation ignored

SCP sent a request in a TC-END which does not make sense - request operation is ignored

Contact support.

ISUPIF(123) WARNING =123 INStateMachine.cc@123: IN call model already complete

SSF Aborted TCAP dialogue to SCP No resolution.

This table defines the notice messages for the VSSP ISUP interface. Notices

Alarm Text Reason Remedy ISUPIF(123) NOTICE =123 INStateMachine.cc@123: TCAP dialogue aborted by SCF

SSF failed to disconnect from connected resource.


ISUPIF(123) NOTICE =123 INStateMachine.cc@123: TCAP dialogue aborted by call model

SCP Aborted TCAP dialogue to SSF. Information only. No action required.



M3UA interface alarms This table defines the alarm messages for the VSSP M3UA alarms Errors

Alarm Text Reason Remedy Failed to open M3UA configuration file `<name>'!

Configuration file cannot be opened Check file exists and is accessible.

Failed to parse M3UA configuration file!

Configuration file failed to parse M3UA configuration has invalid syntax. Ensure that it is defined according to this manual.

SGP <name> not found An SGP <name> has been referred to but it hasn't been defined.

Define SGP

No SGPs for SG <name> SG <name> has no SGPs defined for it.

Define at least one.

Cannot find SGP <name> An SGP <name> has been referred to but it hasn't been defined

Define SCG

Gateway <name> not found! A gateway <name> has been referred to but it hasn't been defined.

Define gateway.

No gateways found! No gateways have been defined. Define at least one. SCTP error <error> Refer to technical support HSS error <error> Refer to technical support Failed: <error> Refer to technical support M3UA: Transfer failed: <error> Refer to technical support



Chapter 6

Pre-installation Overview

This chapter explains the pre-installation configuration requirements of the application.

Introduction


UCAI Requirements ...................................................................................... 84 Installation Pre-requisites .............................................................................. 86

In this chapter



UCAI Requirements The UCAI can reside on either: Environment

• a UAS Solaris host machine using internal INAP communication between the VSSP and SCF software, or

• its own independent Solaris machine and communicate with the UAS(s) via SS7 TCAP or TCAP over IP.

Originating Exchange Signalling ISUP Signalling Link Set Dimensioning The signalling capacity requirements for the SS7 links to the originating network

switch are dependent on the following parameters:

• BHCA for service • Required normal network link load • Average number of octets send and received per call

The bit rate capacity can be estimated as:

r=(x.b)/450

Where:

• x = the BCHA number, and • b = number of octets per call (sent or received).

Example: Assuming 100 octets per call (both sent and received), a service with 300000 BHCA would require 66.7 Kbits per second.

If 64Kbit s-1 links are used, and a link load of 60% is required, a link would support 38.4 Kbit s-1.

Therefore, 2 links would be required to support the load. For redundancy, an additional link is normally installed unless the link load figure takes account of this.

Terminating Exchange Signalling ISUP Signalling Link Set Dimensioning Since the terminating trunk signalling may need to establish and clear more than

one call per call to the service, the terminating exchange signalling requirements are a multiple of the originating signalling requirements.

The average number of calls that must be established as a result of each incoming call determines the required multiple.

Example: If each service invocation requires a call to be established to an SRF and then routed to final destination, a multiplication factor of 2 would be applied to determine the terminating exchange signalling requirements.

The number of trunks that must be configured is totally dependent on the number of simultaneous calls UCAI must handle.

Trunk dimensioning

This is dependent on traffic forecasts and quality of service (QoS) data. If a service is expected to have x busy hour call attempts (BHCA), with each call lasting an average of y seconds, then the number of simultaneous calls C is:

c=(x.y)/3600

The number of VSSP trunks is the number of simultaneous calls divided by the number of speech channels in a trunk (E1=30, T1=24).




UCAI Requirements, Continued


Trunk dimensioning (continued)

When QoS is taken into consideration, the number of trunks will be increased, to allow for the non-uniform profile of real service usage.

Example: A service requires 10000 BHCA and has an average call hold time of 2 minutes. The number of simultaneous calls is therefore 3334, which is 14 T1 trunks. To achieve the desired QoS requires a 30% over provisioning of capacity, which results in 19 T1 trunks.


Installation Pre-requisites This topic provides a list of the pre-requisites for the installation of the UCAI application.

Introduction

For details on the installation of the required system software, refer to the installation and set-up documentation supplied with the software.

Important: It is highly recommended that you understand the replication process and have sketched a possible replication set-up before installing any software.

This table describes the third party or layered software which should have been installed on the UAS machines as part of installing SLEE. It is also required for VSSP.

VSSP machine

Note: While either version 9 or 10 of Solaris and Oracle can be used, a Solaris 9 installation must have version 9 of Oracle. Similarly, an installation with Solaris 10, can only have version 10 Oracle. Software Version Description Solaris 9 or later

10 or later SUN operating system

Oracle 9.2.0 or later 10 or later

Oracle DBMS

Patch 9.2.0.4 Solaris Enterprise Edition

This table describes the Oracle software which must be installed before VSSP is installed on a UAS.

For details about which version of the software is required, see the release notes for the VSSP packages you are installing.

Software Version Description Further information smsScp 3.0.0 or later Service Management

System SMS Technical Guide.

SLEE 3.2.0 or later Service Logic Execution Environment

SLEE Technical Guide.

Check that your Oracle version is correct. Checking Oracle version

As acs_oper (or whichever user is appropriate) logon to sqlplus as "/", e.g.:

bash-2.05$ sqlplus /

The resulting messages show the Oracle version in use:

SQL*Plus: Release 9.2.0.4.0 - Production on Fri Jul 22 06:55:45 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:

Oracle9i Release 9.2.0.4.0 - 64bit Production

JServer Release 9.2.0.4.0 - Production

Check that your Solaris version is correct. The version required is listed under the machine names in this topic.

Checking software on Solaris




Installation Pre-requisites, Continued

Checking software on Solaris (continued)

Example commands: You can check your Solaris version by using the commands:

• uname -r, and

• pkginfo

For more information about finding out your Solaris version, see your Solaris documentation.

Use the pkginfo utility to check the versions of Oracle application packages on each node.

Checking Oracle application versions - cmn

For more information about:

• which versions are required, see the list under the machine name in this topic. • using pkginfo, see Checking installed packages (on page 54).




Chapter 7

Installation Overview

This chapter explains how to install the application. Introduction


Installation Procedure Overview ................................................................... 90 Loading the Distribution File .......................................................................... 92 Installing VSSP .............................................................................................. 93 Checking the Installation ............................................................................... 95

In this chapter

Technical Guide


Installation Procedure Overview This diagram shows how UCAI is installed within a network. There may be one or more UCAI, each connected to one or more exchanges.

Network architecture

The UCAI communicates with the SCF over SS7, using either ETSI/ITU-T INAP or AIN0.x. An operator may manage its configuration and alarms by USMS, or via a Q.3 agent using Q.751.

Note: Although the UCAI is shown as a separate physical entity in this diagram, it may also co-exist on the UASs. If so, it will still communicate with the SCF over INAP (though this may not leave the SS7 stack).

UCAI is installed from the VSSP package. Package installation

It is installed using pkgadd.

The pkg utilities provide a convenient method to install a set of packages. These utilities are supplemented by post-installation scripts which must be manually executed after using the pkg utilities.




Installation Procedure Overview, Continued

This table describes the steps involved in installing UCAI packages for a UAS. VSSP install process overview

Stage Description 1 The VSSP distribution file must be loaded onto the UAS. For more

information, see Loading the Distribution File (on page 92).

2 The VSSP package must be installed on the UAS. This is a two part procedure: 1 adding the package using the pkgadd utility, and 2 completing the installation configuration script (this starts

automatically when the pkgadd utility finishes adding the VSSP package).

3 Insert a line in SLEE.cfg for the vssp.



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.

Introduction

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.

Installation directory

Follow these steps to load the distribution file. Procedure

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.



Installing VSSP Use this procedure to install the VSSP package on a single Sun platform. Introduction -

install vssp This process uses the pkgadd utility to install the package. When the install is complete, the utility automatically runs the post-install script.

During installation, the installation script will overwrite any previously installed files in /IN/service_packages and /IN/html. If you want to keep these files, move them before starting the installation.

Before you begin

The table below provides a sample of the text displayed during a VSSP package install. Some of the content has been removed to save space.

VSSP installation script

Script Action # pkgadd -d `pwd` VSSP

Type this command to start the installation

Processing package instance <VSSP> from </volA/packages> VSSP EAX Installation

Oracle

## Processing package information.

## Processing system information.

## Verifying disk space requirements.

## Checking for setuid/setgid programs.

This output displays: • the location of the

installation script • the version of the software

that is being installed, and • information about the steps

being performed by the script.

The following files are being installed with setuid and/or setgid permissions: /IN/service_packages/VSSP/bin/vssp <setuid root> Do you want to install these as setuid/setgid files [y,n,?,q] y

Type y to continue with the installation. If you type anything other than y, the script will abort.

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 <VSSP> [y,n,?] y

Type y to continue with the installation. If you type anything other than y, the script will abort.

Installing VSSP EAX Installation as <VSSP> ## Executing preinstall script. NOTE: Installing VSSP into /IN/service_packages/VSSP

This output indicates the directory VSSP will be installed into. No action is required.




Installing VSSP, Continued

VSSP installation script (continued)

Script Action ## Executing postinstall script. NOTE : VSSP Software Installation complete Installation of <VSSP> was successful.

This output indicates that the installation process has been completed. No action is required.

Configure UCAI to use the SLEE by adding an entry for the vssp process in SLEE.cfg.

Add vssp entry to SLEE.cfg

Unless the setup of this installation of UCAI is unusual, the line should be: INTERFACE=VSSP vssp.sh /IN/service_packages/VSSP/bin EVENT

For more information about adding entries to SLEE.cfg, see SLEE Technical Guide.



Checking the Installation Refer to these checklists to ensure that UCAI has installed correctly. Introduction

Follow the steps in this checklist to ensure UCAI has been installed on a UAS machine correctly.

Checklist

Step Action 1 Log in to UAS machine as root. 2 Check the following directory structure exists with subdirectories:

• /IN/service_packages/VSSP

3 Check the directory contains subdirectories and that all are owned by: acs_oper user (group Oracle)

4 Check the entries of following file: /IN/service_packages/SLEE/etc/SLEE.cfg

SLEE startup entries for VSSP on a UAS: 1 INTERFACE=VSSP vssp.sh

/IN/service_packages/VSSP/bin EVENT 5 Check that the processes listed in the process lists are running on the

relevant machine. For a list of the processes which should be running, see Process list (on page 95).

If the application is running correctly, the following processes should be running on each UAS:

Process list

• started during SLEE startup: vssp




Chapter 8

Removal Overview

This chapter explains how to remove the application. Introduction


Removing VSSP Package............................................................................. 98

In this chapter

Technical Guide


Removing VSSP Package The swremove and pkgrm utilities will delete the entire package directory. Please check the /IN/service_packages/VSSP directory for any files you wish to keep.

Before you begin

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

Follow these steps to remove the VSSP package from a Solaris machine. Removing VSSP

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

Result: This removes this package and the configuration entries.

The table below provides a sample of the text displayed during a VSSP package removal. Some of the content has been removed to save space.

VSSP removal script

Script Action pkgrm VSSP Type this command to start the

installation

The following package is currently installed: VSSP VSSP EAX Installation (sun4u) 3.1.2.2 Do you want to remove this package? [y,n,?,q] y

Type y to continue with the package removal. If you type anything other than y, the script will abort.

## Removing installed package instance <VSSP> 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 with the package removal. If you type anything other than y, the script will abort.

## Verifying package dependencies. ## Processing package information. ## Executing preremove script. ## Removing pathnames in class <none> /IN/service_packages/VSSP/tmp <non-empty directory not removed> /IN/service_packages/VSSP/etc/vssp.config /IN/service_packages/VSSP/etc/m3ua.config /IN/service_packages/VSSP/etc <non-empty directory not removed> /IN/service_packages/VSSP/bin/vssp.sh /IN/service_packages/VSSP/bin/vssp

This output indicates the directory VSSP components will be removed from. No action is required




Removing VSSP Package, Continued


VSSP removal script (continued)

Script Action ## Executing postremove script. NOTE: Removing directory IMPORTANT: Please ensure the SLEE.cfg file is updated to remove references to VSSP. ## Updating system information. Removal of <VSSP> was successful. #

This output indicates that the installation process has been completed. No action is required.



Appendix

Overview

This appendix contains the following topics. In this appendix

Glossary of Terms ....................................................................................... 103 Index ............................................................................................................ 107

Technical Guide


Glossary of Terms

Authentication, Authorisation, and Accounting. Specified in Diameter RFC 3588. AAA

Application Context. A parameter in a TCAP message which indicates what protocol is conveyed. May indicate MAP, CAMEL, INAP, etc. Also usually specifies the particular version of the conveyed protocol, e.g. which CAMEL Phase.

AC

Advanced Control Services configuration platform. ACS

Advanced Intelligent Network AIN

Application Server. The logical entity serving a SUA routing key. An AS is equivalent to an SS7 end point (e.g. HLR, MSC,…). An AS contains, at least, one ASP.

AS

ASP • Application Service Provider, or • Application Server Process. An IP based instance of an AS. An ASP

implements a SCTP connection between 2 platforms.

See SS7. C7

Customized Applications for Mobile network Enhanced Logic CAMEL

This is a 3GPP (Third Generation Partnership Project) initiative to extend traditional IN services found in fixed networks into mobile networks. The architecture is similar to that of traditional IN, in that the control functions and switching functions are remote. Unlike the fixed IN environment, in mobile networks the subscriber may roam into another PLMN (Public Land Mobile Network), consequently the controlling function must interact with a switching function in a foreign network. CAMEL specifies the agreed information flows that may be passed between these networks.

Credit-Control-Request, used in Diameter by the credit-control client to request credit authorization from the credit-control server.

CCR

Call Detail Record CDR

Note: The industry standard for CDR is EDR (Event Detail Record). Over time EDR will replace CDR in the Oracle documentation.

Connection

Transport level ink between two peers, providing for multiple sessions.

Unix utility for scheduling tasks. cron

File used by cron. crontab

ETSI INAP Capability Set 1. An ITU standard. CS1

A feature rich AAA protocol. Utilises SCTP and TCP transports. Diameter

Dual Tone Multi-Frequency - system used by touch tone telephones where one high and one low frequency, or tone, is assigned to each touch tone button on the phone.

DTMF



European Telecommunications Standards Institute ETSI

File Transfer Protocol - protocol for electronic transfer of files FTP

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

GPRS

Global System for Mobile communication. GSM

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. GT

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.

HLR

Home PLMN HPLMN

HyperText Markup Language, a small application of SGML used on the World Wide Web.

HTML

It defines a very simple class of report-style documents, with section headings, paragraphs, lists, tables, and illustrations, with a few informational and presentational items, and some hypertext and multimedia.

InitiateCallAttempt. A CAMEL/INAP operation sent by the UAS to an SSP request that a voice call is started.

ICA

Intelligent Network IN

Intelligent Network Application Part - a protocol offering real time communication between IN elements.

INAP

1) Internet Protocol IP

2) Intelligent Peripheral - a box that is able to play announcements

Internet Protocol Address - network address of a card on a computer IP address

Integrated Services Digital Network - set of protocols for connecting ISDN stations. ISDN



ISDN User Part - part of the SS7 protocol layer and used in the setting up, management, and release of trunks that carry voice and data between calling and called parties.

ISUP

International Telecommunication Union ITU

Interactive Voice Response - systems that provide information in the form of recorded messages over telephone lines in response to user input in the form of spoken words or, more commonly, DTMF signalling.

IVR

MTP3 User Adaptation. The equivalent of MTP in the SIGTRAN suite. M3UA

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.

MAP

Mobile Switching Centre. Also known as a switch. MSC

Message Signalling Unit MSU

Mobile Terminated MT

Message Transfer Part (part of the SS7 protocol stack). MTP

Message Transfer Part - Level 3. MTP3

Nature Of Address - a classification to determine in what realm (Local, National or International) a given phone number resides, for the purposes of routing and billing.

NOA

Oracle Corporation Oracle

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

Public Land Mobile Network PLMN

Signalling Connection Control Part (part of the SS7 protocol stack). SCCP

Service Control Function - this is the application of service logic to control functional entities in providing Intelligent Network services.

SCF

Service Control Point. Also known as UAS. SCP

Stream Control Transmission Protocol. A transport-layer protocol analogous to the TCP or User Datagram Protocol (UDP). SCTP provides some similar services as TCP (reliable, in-sequence transport of messages with congestion control) but adds high availability.

SCTP

Standard Generalized Markup Language. The international standard for defining descriptions of the structure of different types of electronic document.

SGML

Signalling Gateway Process. SGP

Serving GPRS Support Node SGSN



Page 106 Universal Call Agent for ISUP

Service Logic Execution Environment SLEE

Short Message Service. SMS

Structured Query Language - a database query language. SQL

A Common Channel Signalling system used in many modern telecoms networks that provides a suite of protocols which enables circuit and non circuit related information to be routed about and between networks. The main protocols include MTP, SCCP and ISUP.

SS7

Sub Service Field. SSF

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

Service Switching Point SSP

Signalling Connection Control Part User Adaptation Layer SUA

Anything that can send and receive C7 messages. Switching Point

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

TCAP

Transmission Control Protocol. This is a reliable octet streaming protocol used by the majority of applications on the Internet. It provides a connection-oriented, full-duplex, point to point service between hosts.

TCP

Trigger Detection Point. TDP

Telecommunications Provider. This is the company that provides the telephone service to customers.

Telco

See Telco. Telecommunications Provider

Universal Application Server - hardware on which applications run. UAS

Universal Call Agent ISUP (formerly VSSP) UCAI

Universal Service Management System hardware platform. USMS

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.

VLR

Virtual SSP - old name for UCAI VSSP

Technical Guide


Index

A

About this Document Audience • v Changes in this document • v Pre-requisites • v Related documents • v Scope • v

AC • 39 ACS • 40 Add vssp entry to SLEE.cfg

Installing VSSP • 94 Additional call setup messages • 8

Supported Messages Overview • 10 After an IAM is sent on the B-leg • 19 AIN • 37 Alarm format

Alarm Topic Description • 58 Alarm generation

Alarm Topic Description • 58 Alarm text and variables

Alarm Topic Description • 58 Alarm Topic Description

Alarm format • 58 Alarm generation • 58 Alarm text and variables • 58 Further information • 59 Severity levels • 58

as • 49 AS • 30 asp • 49 ASP • 29 Audience

About this Document • v

B

Basic processing UCAI Operation - Loop Back Mode • 5

Before an IAM is sent on the B-leg • 18 Before you begin

Installing VSSP • 93 Removing VSSP Package • 98

C

-c <configuration file> • 45

C7 • 106 Call processing

UCAI Introduction • 3 UCAI Operation - Loop Back Mode • 5

Call processing messages • 8 Supported Messages Overview • 9

CAMEL • 38 Case studies

Configuring UCAI • 36 CCR • 12 CDR • 63 cdr file • 46 Changes in this document

About this Document • v Checking configuration files

Common Troubleshooting Procedures • 55 Checking current processes

Common Troubleshooting Procedures • 54 Checking installed packages • 87

Common Troubleshooting Procedures • 54 Checking network connectivity

Common Troubleshooting Procedures • 55 Checking Oracle application versions - cmn

Installation Pre-requisites • 87 Checking Oracle version

Installation Pre-requisites • 86 Checking software on Solaris

Installation Pre-requisites • 86 Checking the Installation

Checklist • 95 Introduction • 95 Process list • 95

Checklist Checking the Installation • 95

Circuit mismatches Possible Problems • 56

Command line parameters • 45 Common Troubleshooting Procedures

Checking configuration files • 55 Checking current processes • 54 Checking installed packages • 54 Checking network connectivity • 55 Introduction • 54 Turning on debug • 54 Turning on M3UA vssp debug • 54

Components UCAI Introduction • 4

Configuration • 7 vssp • 44

Configuration components Configuration Overview • 22

Configuration example UCAI Operation - Loop Back Mode • 6

Configuration Overview Configuration components • 22 Rereading configuration • 22

Configuring circuit loops • 46, 56 UCAI Configuration File • 24

Configuring IN Call Model Triggers • 22 Environment variables • 38 Global configuration parameters • 38 Note 1 • 40 Overview • 38



TDP event type values • 42 Trigger detection point (TDP) definition file

• 38 Trigger detection point definitions • 40

Configuring the Environment • 22 Editing the vssp.sh file • 23 Example vssp.sh file • 23 Introduction • 23

Configuring UCAI Case studies • 36 In line UCAI • 37 In line UCAI example • 37 Loop back UCAI • 36 Loop back UCAI example • 36

connect • 46 Connection • 65 Continuity • 12 Continuity check request • 12 Continuity testing messages • 8

Supported Messages Overview • 12 Critical Errors - vssp

VSSP ISUP Interface alarms • 60 cron • 103 crontab • 43 CS1 • 2

D

debug • 46, 54 Description

UCAI Introduction • 2 Diagram

UCAI Configuration File • 26 Diameter • 103 Document Conventions

Icons • vi Typographical conventions • vi

DTMF • 105

E EAX • 93 Editing the vssp.sh file • 22

Configuring the Environment • 23 EDR • 103 Environment

UCAI Requirements • 84 Environment variables

Configuring IN Call Model Triggers • 38 Errors

M3UA interface alarms • 82 VSSP ISUP Interface alarms • 61

ETSI • 3 Example 1

UCAI Configuration File • 24 Example 2

UCAI Configuration File • 24 Example configuration - vssp.config

UCAI Configuration File • 26

vssp • 50 Example M3UA configuration file

M3UA configuration file syntax • 31 vssp • 50

Example vssp.sh file Configuring the Environment • 23

F Features

UCAI Introduction • 2 filter • 46 Forced Trigger Scenario • 17 FTP • 92 Further information

Alarm Topic Description • 59

G

gateway • 49 Global configuration parameters

Configuring IN Call Model Triggers • 38 GPRS • 104 GSM • 36 GT • 39

H

Handling Called Party Suspends Overlap Sending • 20

HLR • 36 How Overlap Sending works

Overlap Sending • 15 HPLMN • 104 HTML • vi

I ICA • 47 Icons

Document Conventions • vi Important installation planning

UCAI Operation - Loop Back Mode • 6 IN • v In line UCAI

Configuring UCAI • 37 In line UCAI example

Configuring UCAI • 37 IN Service Processing

Overlap Sending • 17 INAP • 2 Installation directory

Loading the Distribution File • 92 Installation Pre-requisites

Checking Oracle application versions - cmn • 87

Checking Oracle version • 86 Checking software on Solaris • 86 Introduction • 86 VSSP machine • 86

Installation Procedure Overview



Network architecture • 90 Package installation • 90 VSSP install process overview • 91

Installing VSSP Add vssp entry to SLEE.cfg • 94 Before you begin • 93 Introduction - install vssp • 93 VSSP installation script • 93

Introduction Checking the Installation • 95 Common Troubleshooting Procedures • 54 Configuring the Environment • 23 Installation Pre-requisites • 86 Loading the Distribution File • 92 Overlap Sending • 15 Possible Problems • 56 Routing Options • 33 Supported Messages Overview • 8 UCAI Configuration File • 24

Introduction - install vssp Installing VSSP • 93

IP • 2 IP address • 29 ISDN • v ISUP • ii ISUP Signalling Link Set Dimensioning

UCAI Requirements • 84 ITU • v IVR • 19

K

-k <keyfile> • 45

L Lexical considerations

M3UA configuration file syntax • 31 limit • 47 Loading the Distribution File • 91

Installation directory • 92 Introduction • 92 Procedure • 92

Loop back UCAI Operation - Loop Back Mode • 7

Loop back UCAI Configuring UCAI • 36

Loop back UCAI example Configuring UCAI • 36

M

-m <m3ua configuration file> • 45

M3UA • v M3UA configuration

vssp • 44 M3UA Configuration • 22, 49

Overview • 28

SG (ITP) Configuration • 29 Switch configuration • 28 VSSP Configuration • 29

M3UA configuration file syntax Example M3UA configuration file • 31 Lexical considerations • 31 Whitespace • 31

M3UA interface alarms Errors • 82

M3UA parameters • 49 Maintenance messages • 8

Supported Messages Overview • 13 MAP • 103 MSC • 36 MSU • 62 MT • 104 MTP • 67 mtp debug • 47, 54 MTP3 • 47 Multiple point code fix

Routing Options • 33

N

network • 47 Network architecture

Installation Procedure Overview • 90 UCAI Introduction • 2

NOA • 38 Note 1

Configuring IN Call Model Triggers • 40 Notices

VSSP ISUP Interface alarms • 81

O

Optimal configuration UCAI Configuration File • 26

Oracle • ii Output

vssp • 51 Overlap Sending

Handling Called Party Suspends • 20 How Overlap Sending works • 15 IN Service Processing • 17 Introduction • 15 Transparent Passing of ISUP Messages •

19 Triggering Rules • 16

Overview Configuring IN Call Model Triggers • 38 M3UA Configuration • 28

P Package installation

Installation Procedure Overview • 90 Parameters • 24

as • 49 asp • 49



-c <configuration file> • 45 cdr file • 46 connect • 46 debug • 46 filter • 46 gateway • 49 -k <keyfile> • 45 limit • 47 -m <m3ua configuration file> • 45 mtp debug • 47 network • 47 set ica iam cpc • 47 sgp • 50 slee • 47 startup time • 48 stats • 48 syslog • 48 vssp • 45

PC • 39 Per link fix

Routing Options • 33 PLMN • 103 Possible Problems

Circuit mismatches • 56 Introduction • 56

Pre-requisites About this Document • v

Procedure Loading the Distribution File • 92

Process list • 95 Checking the Installation • 95

Purpose vssp • 44

R

Related documents About this Document • v

Removing VSSP Removing VSSP Package • 98

Removing VSSP Package Before you begin • 98 Removing VSSP • 98 VSSP removal script • 98

Rereading configuration Configuration Overview • 22

Routing Options • 7 Introduction • 33 Multiple point code fix • 33 Per link fix • 33 Two switch fix • 35

S SAM Timer • 17 SCCP • 39 SCF • 3 Scope

About this Document • v

SCP • 2 SCTP • 29 Service Provider • 103 set ica iam cpc • 47 Severity levels

Alarm Topic Description • 58 SG (ITP) Configuration

M3UA Configuration • 29 SGML • 104 sgp • 50 SGP • 29 SGSN • 104 Shorthand configuration

UCAI Configuration File • 25 Signalling

UCAI Operation - Loop Back Mode • 6 Sinap • 80 slee • 47 SLEE • v SMS • vi SQL • 86 SS7 • 2 SSF • 60 SSN • 39 SSP • 3 Standard options • 46 Startup

vssp • 44 startup time • 48 stats • 48 Stop Digit • 16 SUA • 103 Supported Messages Overview

Additional call setup messages • 10 Call processing messages • 9 Continuity testing messages • 12 Introduction • 8 Maintenance messages • 13

Switch configuration M3UA Configuration • 28

Switching Point • 106 Symbolic names

<configuration file> • 45 <keyfile> • 45 <m3ua configuration file> • 45

syslog • 48

T TCAP • 39 TCP • 2 TDP • 38 TDP event type values

Configuring IN Call Model Triggers • 42 tdp.conf • 16 Telco • 5 Telecommunications Provider • 106 Throttling




UCAI Operation - Loop Back Mode • 7 Transparent Passing of ISUP Messages

Overlap Sending • 19 Trigger detection point (TDP) definition file

Configuring IN Call Model Triggers • 38 Trigger detection point definitions

Configuring IN Call Model Triggers • 40 Triggering Rules

Overlap Sending • 16 Trunk dimensioning

UCAI Requirements • 84 Turning on debug

Common Troubleshooting Procedures • 54 Turning on M3UA vssp debug

Common Troubleshooting Procedures • 54 Two switch fix

Routing Options • 35 Typographical conventions

Document Conventions • vi

U

UAS • 4 UCAI • v UCAI configuration

UCAI Operation - Loop Back Mode • 7 UCAI Configuration File • 22, 23

Configuring circuit loops • 24 Diagram • 26 Example 1 • 24 Example 2 • 24 Example configuration - vssp.config • 26 Introduction • 24 Optimal configuration • 26 Shorthand configuration • 25

UCAI Introduction Call processing • 3 Components • 4 Description • 2 Features • 2 Network architecture • 2

UCAI Operation - Loop Back Mode Basic processing • 5 Call processing • 5 Configuration example • 6 Important installation planning • 6 Loop back • 7 Signalling • 6 Throttling • 7 UCAI configuration • 7

UCAI Requirements Environment • 84 ISUP Signalling Link Set Dimensioning • 84 Trunk dimensioning • 84

USMS • v

V VLR • 104

vssp Configuration • 44 Example configuration - vssp.config • 50 Example M3UA configuration file • 50 M3UA configuration • 44 Output • 51 Parameters • 45 Purpose • 44 Startup • 44

VSSP • 23 VSSP Configuration

M3UA Configuration • 29 VSSP install process overview

Installation Procedure Overview • 91 VSSP installation script

Installing VSSP • 93 VSSP ISUP Interface alarms

Critical Errors - vssp • 60 Errors • 61 Notices • 81 Warnings • 81

VSSP machine Installation Pre-requisites • 86

VSSP removal script Removing VSSP Package • 98

W

Warnings VSSP ISUP Interface alarms • 81

Whitespace M3UA configuration file syntax • 31

Documents

Oracle Communications Network Charging and Control Product: … · 2010. 11. 25. · Continued . Network architecture (continued) The UCAI communicates with the SCF over SS7, using