Ismsc 2 4

ISMSC Manual
P/N 10-133-0006
Issue 1
Release 2.4
Oct 1999
Comverse ISMSC Manual

Release 2.4, Oct 1999
NOTICE
This document contains proprietary and confidential material of Comverse Network
Systems. Any unauthorized reproduction, use, or disclosure of this material, or any part
thereof, is strictly prohibited. This document is solely for the use of Comverse employees
and authorized Comverse customers.
The material furnished in this document is believed to be accurate and reliable. However, no
responsibility is assumed by Comverse Network Systems for the use of this material.
Comverse Network Systems reserves the right to make changes to the material at any time
and without notice.
TRILOGUE and INfinity are trademarks of Comverse Network Systems. OMNI
SignalWare is a registered trademark of Comverse Network Systems.
Copyright 1999 Comverse Network Systems.
Corporate Headquarters
100 Quannapowitt Parkway
Wakefield, MA 01880 USA
Tel: (781) 246-9000
Fax: (781) 224-8143
www.comversens.com
Comverse Network Systems

CAUTIONS AND WARNINGS

The following are general safety precautions that are not related to any specific procedures
and therefore do not appear elsewhere in this publication. It is recommended that personnel
understand and apply these precautions during the various phases of system maintenance.
WARNING
Electrical Shock Hazard
There is an Electrical Shock Hazard when servicing this system. Operating personnel must,
at all times, observe all safety regulations. System cabinets should be opened only by
authorized personnel trained by Comverse Network Systems. Insertion, removal, and
adjustment of boards, components, or other electrical subassemblies should always be done
when the system power is turned off.
CAUTION
Electrostatic Discharge
System modules contain Electrostatic Discharge Sensitive (ESDS) components. Improper
handling may damage these components. When working with modules, always wear one of
the ESD wrist straps provided with the system. The ESD wrist strap must be attached to
chassis ground.
Do not remove a module from its protective wrapper or from the module drawer unless you
have taken ESD precautions. When installing or removing modules, place them componentside up, on a grounded, static-free surface. Put the module on a special ESD foam pad, if
available. Do not slide modules over a surface of any kind.
Page i

WARRANTY
Comverse Network Systems maintains a technical support department for the sole purpose
of providing efficient and reliable service. All Comverse products are warranted against
defects in material and workmanship. The period of coverage and other warranty details are
specified in the Comverse terms and conditions warranty. In no event shall Comverse
Network Systems be liable for incidental or consequential damages in connection with, or
arising from use of any Comverse product.
Page ii

FCC Regulations
This equipment complies with FCC Regulations Part 68. The label on the rear panel of this
equipment provides, among other information, the FCC registration number and the Ringer
Equivalence Number (REN). In certain circumstances, it could be necessary for the telephone
company to request information concerning the equipment connected to the telephone line. Upon
request of the telephone company, provide the FCC registration number and the REN. The total of
all the RENs on the telephone lines should be less than five to assure proper service from the
telephone company.
If the telephone company notes a problem in the terminal equipment, it will notify you of the
problem and you will be given the opportunity to correct the problem and you will be informed of
your right to file a complaint with the FCC.
When programming emergency numbers and/or making test calls to emergency numbers:
1.
Remain on the line and briefly explain to the dispatcher the reason for the call.
2.
Perform these tasks in off-peak hours, such as early morning or late evenings.
Allowing this equipment to be operated without providing for proper answer supervision is a
violation of part 68 of the FCC regulations.
Proper answer supervision is when:
This equipment returns answer supervision to the PSTN when DID calls are:
1.
Answered by the called station.
2.
Answered by the attendant.
3.
Routed to a recorded announcement that can be administered by the CPE user.
4.
Routed to a dial prompt.
This equipment returns answer supervision on all DID calls forwarded to the PSTN. Permissible
exceptions are:
1.
A call is unanswered.
2.
A busy tone is received.
3.
A reorder tone is received.
Equal Access
This Equipment is capable of providing users access to interstate providers of operator services
through the use of access codes. Modification of this equipment by call aggregators to block access
dialing codes is a violation of the Telephone Operator Consumers Act of 1990.
Page iii

North American Numbering Plan (NANP)

The software contained in TRILOGUE INfinity to allow access to the network must be upgraded to
recognize newly established network area codes and exchange codes as they are placed into service.
Failure to upgrade the premises systems or peripheral equipment to recognize the new codes as they
are established will restrict the customer and customer's employees from gaining access to the
network and to these codes.
Bell Communications Research (Bellcore) publishes the North American Numbering Plan (NANP)
information paper, microfiche, and tape. An abbreviated summary of the newly established area
codes and exchange codes is also available. Bellcore may be contacted on (201) 829 3071 to obtain
appropriate information to keep customer equipment upgraded.
Service Requirements
In the event of equipment malfunction, all repairs must be performed by our Company or an
authorized agent. It is the responsibility of users requiring service to report the need for service to
our Company or to one of our authorized agents.
Service can be obtained at:
Corporate Headquarters
100 Quannapowitt Parkway
Wakefield, MA 01880 USA
Tel: (781) 246-9000
Fax: (781) 224-8143
www.comversens.com
Page iv

Systems Port Identification, Facility Interface & Service Order

Codes (1)
FCC Registration No.: 10 AISR-22850-VM-E TRILOGUE INfinity v3.0
Registration
Status
MFRS Port
Identifier
(4)
MTS/WTS FIC
(3)
REN
(5,6)
Network Jacks
(4)
* ATM + TLE
02LS2
AC-0.9B D
RJ21X
* ATM + TLGE
022GS-2
C-2.5
RJ21X
DID FIC (3) OR

DIGITAL FIC
A.S CODE (PAGE

D-11)
02RV2-T
AS.2
ANALOG PL FIC
(8)
SERVICE ORDER
CODE (9)
* ATM + DID
RJ21X
* ATM + TEM
TL11M or E
9.0 Y
RJ21X
* ATM + TEM
TL12M or E
9.0 Y
RJ21X
* ATM + TEM
TL31M or E
9.0 Y
RJ21X
DTM
04DU9-DN
6.0 N
RJ45
The ATM is delivered in the following configurations: 2, 4, 6, 8 lines.
Page v

UL Requirements
This equipment is to be installed only in Restricted Access Areas (Dedicated
Equipment Rooms, Equipment Closets, etc.) in accordance with Articles 110-16,
110-18 of the National Electrical Code, ANSI/NFPA 70.
The DTM/T1 Card is not approved for direct communication with the telephone
network, and shall not be connected to off-premises wiring.
Electromagnetic Compatibility
The TRILOGUE INfinity complies with Emission and Immunity requirements in
accordance with EN 55022 class B and EN 50082-1.
Page vi

MAIN TABLE OF CONTENTS

Chapter 1: Overview
Chapter 2: Concepts of Operation
Chapter 3: Design and Software Structure
Chapter 4: User Interface
Chapter 5: Provisioning
Chapter 6: Maintenance
Chapter 7: IPOS Provisioning
Chapter 8: Email Provisioning
Chapter 9: Web Access Provisioning
Chapter 10: Installation
Chapter 11: Man Machine Language
Chapter 12: Provisioning Data Storage and Recovery
Glossary
Index
Page vii

LIST OF EFFECTIVE PAGES

Chapter
Page Numbers
Revision
Date
Front matter
Title Page, i thru vii, viii blank, ix, x blank
Original
1-i, 1-ii blank, 1-1 thru 1-5, 1-6 blank
Original
2-i thru 2-iii, 2-iv blank, 2-1 thru 2-33, 2-34 blank
Original
3-i, 3-ii blank, 3-1 thru 3-6
Original
4-i thru 4-ii, 4-1 thru 4-19, 4-20 blank
Original
Original
6-i thru 6-iii, 6-iv blank, 6-1 thru 6-57, 6-58 blank
Original
7-i thru 7-ii, 7-1 thru 7-11, 7-12 blank
Original
Original
9-i, 9-ii blank, 9-1 thru 9-2
Original
10
10-i thru 10-vi, 10-1 thru 10-121, 10-122 blank
Original
11
11-i, 11-ii blank, 11-1 thru 11-6
Original
12
12-i, 12-ii blank, 12-1 thru 12-4
Original
Glossary
1 thru 3, 4 blank
Original
Index
1 thru 6
Original
No.
Page ix
Chapter 1
Overview

Chapter 1
Overview
Table of Contents
1. Introduction to the Short Message Service..........................................................................1-1
2. ISMSC Features.......................................................................................................................1-1
3. Scope of Manual and Audience.............................................................................................1-5
List of Tables
1-1
ISMSC Releases and their Features ..................................................................................1-2
Page 1-i

1.
Chapter 1
Overview
Introduction to the Short Message Service

The Comverse Intelligent Short Message Service Center (ISMSC) provides a
means of relaying short text messages and icons between mobile stations and the
SMSC (Short Message Service Center) of a digital cellular network such as GSM
(Groupe Speciale Mobile/Global Standard for Mobile Communications), TDMA
(Time Division Multiple Access), CDMA (Code Division Multiple Access), PCS
(Personal Communications System) or PCN (Personal Communications Network)
mobile network. The service is specified by the European Telecommunications
Standards Institute (ETSI) GSM standard, and by the Telecommunications
Industry Association (TIA) IS-41 Standard.
The SMS provides a means of passing Short Messages (SMs) of up to 160
octets/characters from a Short Message Entity (SME) to a mobile subscriber via a
SMSC (GSM). This service is known as the Mobile Terminated (MT) Short
Message Service. MT SMs may originate, for example, from an Email server, a
Web server, and the ISMSC for VMN. The SMS also provides a means of
originating SMs at a mobile station, known as the Mobile Originated (MO) Short
Message Service in GSM systems.
A mobile subscriber may be attached to the Home PLMN (HPLMN) or a Visited
PLMN (VPLMN). A PLMN (Public Land Mobile Network) is a network operated
by common carriers for the provision of mobile lines. In the event that the mobile
subscriber is unavailable (e.g., turned off), a flag is set in the Visitor Location
Register (VLR) and the address of the SMSC is stored in the Home Location
Register (HLR). When the mobile subscriber becomes available, (e.g., turned on
and registered) the flag in the address stored in the HLR enables the SMSC to
deliver the message to the mobile subscriber. Such a feature requires the use of the
Alert facility in the PLMN network, or the Notification in the TDMA/CDMA
network. A similar Alert/Notification mechanism is defined to handle the situation
in which a mobile subscriber cannot accept an SM because SM storage capacity is
exceeded.
The Comverse ISMSC is a standalone product, and operates in concert with any
voice mail system. When the ISMSC is used in conjunction with TRILOGUE
INfinity or other Comverse messaging platforms, network operators get the
additional benefits of functional, system, and management integration, and unique
services that are made possible by the coordination of Comverse messaging
platforms and the ISMSC.
The ISMSC complies with short message standards and specifications for the
leading digital cellular networks, including ETSI GSM standards (for GSM Phase
1, Phase 2, and Phase 2+), and also D-AMPS (TDMA) and CDMA networks,
based on EIA/TIA IS-41C standards.
2.
ISMSC Features
Table 1-1 presents a list of the ISMSC releases and their major features.
Page 1-1
Chapter 1
Overview

Table 1-1: ISMSC Releases and their Features

Release
Feature Name
1.10
Description
Redundancy, both in the application and signaling
levels
Support of canned and numbered messages
Voice Mail notifications
A new operator UI
1.20
2.0
Improved Alarms
New alarms were introduced for the redundant ISMSC

configuration.
Smart Retries
The Smart Retries feature enables SMs to be retried

using different schedules according to the reason for
failure. Messages are retried when they are likely to be
deliverable, thus conserving system resources.
IS41 Support for

TDMS/CDMA
Networks
Connection to multiple
TRMs
2.1
2.2
Page 1-2
Replace in Handset
This feature provides the ability to send a short

message to a mobile, that replaces a previously sent
message. Voice mail notifications do not accumulate in
the handset, but rather replace each other. (GSM Phase
II handset)
Statistics Files
The statistics produced by the ISMSC are now stored

in dedicated files in the trace directory, instead of the
log file. Several files may be generated daily, and can
be collected by a management center via FTP.
Future Delivery
This feature provides the ability to send short message

to the ISMSC that will be delivered to the subscriber at
some future time.
Mobile originated
Messages in GSM
An MO message is carried from a mobile station

through an MSC to the ISMSC. The ISMSC stores the
MO in its database, and acknowledges the message to
the MSC.
CPHS and DCS Icons

for GSM
Icons are used for voice/fax mail notification. The

TRM sends an ICON-ON indication to the ISMSC
instead of, or together with, a voice mail notification
text message (configurable).

Release
Feature Name
Chapter 1
Overview
Description
Infrastructure for
Supporting Multiple
Short Message Sources
and Destinations
Local language
support (Chinese)
IPOS Release 1.0
SMPP Interface
Short Email (Mobile
Terminated)
WWW access for
submitting SMs
TAP Interface
2.3
Address Translation
Corrects the length of prefixes, if necessary, for MO

calls to standardize destination addresses. Defines
either permitted or prohibited originating addresses for
MO calls.
Provisioning
Subsystem
Administration and verification, in both interactive and

batch modes, the provisioning rules of MT SM for
subscribers, dependent on the originating EI.
Enhanced Smart
Retries
Retries are defined for a greater range of errors,

including MAP errors, MAP causes, and general
network errors, or any combination thereof.
Enhanced Statistics
Statistics are counted per each source EI and per target

EI. The number and type of statistics collected is
greatly increased. In addition, statistics may be
collected according to the network errors used in
Enhanced Smart Retries.
MSC Time Zone
MSCs may be defined as having different time zones.

The message time stamp is then adjusted to meet the
local time zone of the MSC. In addition it is
configurable whether the time zone value is added to
the time stamp before sending the ForwardSM
message.
Page 1-3
Chapter 1
Overview

Release
Feature Name
Description
2.3.5
Broadcast SMS from

File
Batch and Broadcast Short Messaging are used for

billing reminders and other administrative messages.
An address list is used to Broadcast a single, identical
message to groups of users. Alternatively, the ISMSC
supports Batch processing of Short Messages from a
file. A different Short Message text can be specified
for each destination in the file. Existing subscriber lists
may be uploaded via FTP, forming the basis for the
Batch or Broadcast messaging. Retry optimization and
notification mechanisms are in full effect for Broadcast
Short Messages.
UDH Icon Notification

for GSM
With the addition of UDH support, the ISMSC

supports all three icon encoding protocols used in
GSM networks - DCS, UDH, and CPHS. The ISMSC
also supports icon on/off messages generated by the
VMN teleservice type in CDMA networks.
Email Notification
When new email arrives in a subscribers regular email

account, the ISMSC sends notification to the mobile
handset with important details such as the subject, the
sender, and whether the email has attachments.
IPOS with Distribution

Lists (IPOS Rel. 2.0)
Support for distribution lists and personalized address

books has been integrated into the ISMSC Paging
Operator Station (IPOS) application.
Black Lists/White
Lists
Administrators can restrict use of Short Messaging

services by applying Black List or White List
screening. The ISMSC can check both source and
destination addresses of every incoming message
against the screening list.
Enhanced Smart
Retries for IS-41C
The enhanced Smart Retries mechanism now uses a full

complement of IS-41C return codes in determining
retry behavior.
Enhanced Statistics
More detailed data collection, report options, and an

online query utility have been incorporated.
EI Configuration
Options
Flow control, statistical reporting, retry behavior, and

alarm indications may be configured separately for
each EI type.
User Defined
Teleservice (IS-41C)
ISMSC supports a user-defined teleservice with its own

Bearer Data format. When the ISMSC receives a
message with a non-standard teleservice ID value, it
transmits the message text using a user-defined Bearer
Data format.
2.4
Page 1-4

Release
3.
Chapter 1
Overview
Feature Name
Description
Cellular Paging
Teleservice Support
CPT is supported with its own Bearer Data format, as

specified in the TIA/EIA/IS-637 standard. Currently,
only Deliver Message functionality is supported.
Scope of Manual and Audience

This manual provides platform personnel with a detailed description of the
Comverse ISMSC platform, its operation, installation and maintenance. This
manual covers version releases up to 2.4.
Page 1-5
Chapter 2
Concepts of Operation

Chapter 2
Table of Contents
1. Overview ..................................................................................................................................2-1
2. Input Handled by the ISMSC ..................................................................................................2-1
2.1. Text Messages...................................................................................................................2-1
2.1.1. Predefined Messages .................................................................................................2-2
2.1.2. Predefined Messages using TRILOGUE INfinity Voice Mail Systems........................2-2
2.1.3. Numeric Messages .....................................................................................................2-2
2.1.4. Numeric Messages using TRILOGUE INfinity Voice Mail Systems............................2-2
2.2. Notification by Icon (GSM) .................................................................................................2-2
2.3. Notification by Icon (CDMA)...............................................................................................2-3
3. Applications.............................................................................................................................2-3
3.1. Short Email ........................................................................................................................2-3
3.2. ISMSC Paging Operator Stations ......................................................................................2-4
3.3. Web Access.......................................................................................................................2-5
3.4. Operator Generated Short Messages................................................................................2-5
4. ISMSC Functionality ...............................................................................................................2-5
4.1. Short Message Delivery .....................................................................................................2-5
4.2. Future Delivery...................................................................................................................2-6
4.3. ISMSC Message Types .....................................................................................................2-6
4.4. TRILOGUE INfinity VMS as an EI......................................................................................2-6
4.5. Processing of Inputs from EI..............................................................................................2-7
4.6. ISMSC Retry Mechanism...................................................................................................2-8
4.6.1. Smart Retries ..............................................................................................................2-8
4.6.2. Internal Retry ..............................................................................................................2-9
4.7. ISMSC Delivery Mechanism ..............................................................................................2-9
4.8. Delivery Receipt Messages................................................................................................2-9
4.9. ISMSC Treatment of Service Center Alert/Notification ......................................................2-9
5. ISMSC Interface with the PLMN...........................................................................................2-10
5.1. MAP Protocol Message Flow in GSM Systems ...............................................................2-10
5.1.1. Successful DeliveryGSM.......................................................................................2-10
5.1.2. Delivery Failure at MSC Due to Temporary ErrorGSM .........................................2-11
5.1.3. Delivery Failure at HLR Due to Temporary ErrorGSM ..........................................2-12
Page 2-i
Chapter 2

5.1.4. Delivery Failure at MSC Due to Permanent ErrorGSM ........................................ 2-13

5.1.5. Delivery Failure at HLR Due to Permanent ErrorGSM ......................................... 2-14
5.1.6. Alert Followed by Successful DeliveryGSM.......................................................... 2-15
5.2. MAP Protocol Message Flow in IS-41C Systems ........................................................... 2-16
5.2.1. Successful DeliveryIS-41C ................................................................................... 2-16
5.2.2. Delivery Failure at MSC Due to Temporary ErrorIS-41C...................................... 2-17
5.2.3. Delivery Failure at HLR Due to Temporary ErrorIS-41C ...................................... 2-19
5.2.4. Delivery Failure at HLR Due to Permanent ErrorIS-41C ...................................... 2-20
5.2.5. Delivery Failure at MSC Due to Permanent ErrorIS-41C ..................................... 2-21
5.2.6. NotificationIS-41C................................................................................................. 2-23
5.3. Mobile Originated Messages in GSM Systems ............................................................... 2-24
6. ISMSC Management Features............................................................................................. 2-26
6.1. Management Interface .................................................................................................... 2-27
6.2. Configuration Parameters ............................................................................................... 2-27
6.3. Billing Information............................................................................................................ 2-27
6.4. User Interface.................................................................................................................. 2-28
6.5. Alarms ............................................................................................................................. 2-28
6.6. Prevention of Abuse ........................................................................................................ 2-28
7. Architecture .......................................................................................................................... 2-28
7.1. ISMSC ............................................................................................................................. 2-29
7.2. Internet Messaging Unit .................................................................................................. 2-29
7.3. Disk Drawer..................................................................................................................... 2-30
7.4. Firewall ............................................................................................................................ 2-30
7.5. Hub.................................................................................................................................. 2-30
7.6. Remote Access Units...................................................................................................... 2-30
7.7. Routers............................................................................................................................ 2-30
7.8. Terminal Server Unit ....................................................................................................... 2-30
8. Connectivity with IPOS ........................................................................................................ 2-31
9. Redundancy .......................................................................................................................... 2-33
List of Figures
2-1
GSM. Successful Delivery................................................................................................ 2-11
Page 2-ii

Chapter 2
2-2
GSM. Temporary Error at MSC ........................................................................................2-12
2-3
GSM. Temporary Error at HLR .........................................................................................2-13
2-4
GSM. Permanent Error at MSC ........................................................................................2-14
2-5
GSM. Permanent Error at HLR.........................................................................................2-15
2-6
GSM. Alert Followed by Successful Delivery ....................................................................2-16
2-7
IS41. Successful Delivery .................................................................................................2-17
2-8
IS41. Temporary Error at MSC .........................................................................................2-19
2-9
IS41. Temporary Error at HLR..........................................................................................2-20
2-10 IS41. Permanent Error at HLR..........................................................................................2-21

2-11 IS41. Permanent Error at MSC.........................................................................................2-23
2-12 IS41. Notification...............................................................................................................2-24
2-13 Mobile Originated Message Delivery (GSM).....................................................................2-26
2-14 ISMSC System Architecture .............................................................................................2-29
2-15 IPOS Connected to a Local Network ................................................................................2-31
2-16 IPOS Connected by Remote Dial-Up................................................................................2-31
2-17 IPOS Connected to a Remote Intranet .............................................................................2-32
2-18 IPOS Connected to a Remote Public Network .................................................................2-32
Page 2-iii

1.
Chapter 2
Overview
The Comverse Intelligent Short Message Service Center (ISMSC) receives input
messages from External Interfaces (EIs) and delivers the messages to the PLMN
via a MAP interface or another media, which is part of the SS7 protocol. An EI
may be one of the following:
2.
Email
Paging Stations, including the Comverse ISMSC Paging Operator Station

(IPOS)
SMPP
TAP
TRILOGUE INfinity
Web
External mobile equipment for Mobile Originated SMs
Input Handled by the ISMSC

The ISMSC handles the following input:
2.1.
Text SMs (Paragraph 2.1.)
Icons (Paragraph 2.2., Paragraph 2.3.)
Numeric SMs (Paragraph 2.1.3.)
Binary SMs (used for data for SIM toolkits and Over the Air (OTA)
transmission)
Text Messages
The ISMSC receives Text Messages from a number of sources, for example,
email, paging operator, Mobile Originated (MO), and predefined messages. The
ISMSC forwards the SM to the subscribers destination (for example a mobile
handset, or email) or to another media, such as MO SM to email. Typical textual
messages are:
x
Call the office
Congratulations
Text messages can be used to provide Voice Mail Notification (VMN). When the
ISMSC is integrated with TRILOGUE INfinity Voice Mail System, the ISMSC
sends a message similar to:
You have {nnn} new messages, {uuu} of them urgent, and {fff} new
fax messages, Last message was a {voice/fax} messages from
{tel.#}. Please call {mbx} for retrieval.
Page 2-1
Chapter 2
2.1.1.

Predefined Messages
The ISMSC can interface with any standalone IVR application that sends callerselected predefined messages. The SM is sent to its destination via the ISMSC.
2.1.2.
Predefined Messages using TRILOGUE INfinity Voice Mail

Systems
A guest caller hears predefined messages, chooses a message by its number, and
sends it to the subscriber. The subscriber receives the text message on his handset.
The TRILOGUE INfinity VMS can store up to 90 predefined messages and their
associated numbers (codes). When a caller selects a code, TRILOGUE INfinity
translates the code to a short message, and sends it to the ISMSC, which sends it
to the subscriber.
NOTE:
2.1.3.
This feature is available if TRILOGUE Infinity is an EI.
Numeric Messages
Numeric messages are actually a type of textual messages, which use only
numerals. The ISMSC can interface with any standalone IVR application that
sends caller selected numeric messages. The SM (number) is sent to the subscriber
via the ISMSC.
2.1.4.
Numeric Messages using TRILOGUE INfinity Voice Mail Systems

When integrated with TRILOGUE INfinity, numeric messages are usually the
telephone numbers that a guest caller leaves (DTMF), in order for the subscriber
to return the call. The caller is prompted to either enter the phone number he
wishes the user to call using the DTMF keys or to use his CLI. The number,
without a voice element, is sent directly to the handset display using the ISMSC.
MO SMs are an example of Numeric messages.
NOTE:
2.2.
This feature is available if TRILOGUE Infinity is an EI.
Notification by Icon (GSM)

A MWI icon can be sent to GSM mobile stations. The icon indicates that there are
new messages in the subscribers mailbox (voice, fax or email).
There are three methods of managing the icon. One method is based on
manipulation of the Data-Coding-Scheme (DCS) field. Another method is based
on the User-Data-Header (UDH) field. CPHS defines an additional method for
lighting an icon on a CPHS enabled GSM mobile station.
Page 2-2
CPHS defines two types of icons, known as indicator 0 and indicator 1.
DCS defines four types of icons, 0 for voice, 1 for fax, 2 for email, 3 for
other.

Chapter 2
UDH defines four types of icons and the number of SMs for each.
The icon is used for voice/fax mail notification. The VMS sends the ISMSC an
ICON-ON indication, and the ISMSC turns on the icons. In the case of
TRILOGUE INfinity, the TRM sends an ICON-ON indication to the ISMSC
instead of, or together with, a voice mail notification text message. It is possible
to define on the ISMSC the following, on a per subscriber basis:
2.3.
Whether to send only text, only the icon, or both.
Whether to use the CPHS method or the DCS method, or both. The default
specifies both since the CPHS enabled mobiles understand the CPHS value
and ignore the DCS value, while GSM Phase II+ mobiles ignore the CPHS
value and use the DCS value.
Notification by Icon (CDMA)

A MWI icon can be sent to CDMA mobile stations. The icon indicates how many
new messages are in the subscribers mailbox (voice, fax or email).
3.
Applications
The ISMSC handles the following applications:
3.1.
Email is a standard application sending textual messages (Paragraph 3.1.).
IPOS is an application sending textual messages (Paragraph 3.2.).
MO is a standard application sending textual messages (Paragraph 5.3.).
Web is an application sending textual messages (Paragraph 3.3.).
Short Message Peer to Peer (SMPP) is a protocol that enables a third party
to transmit icons and textual SMs to the ISMSC.
Telocator Alphanumeric Protocol (TAP) is a protocol that enables a third

party to transmit textual SMs to the ISMSC.
TRILOGUE INfinity is a non-standard application that uses textual and

numeric messages and icons.
Short Email
The Short Email application enables users to send Email to a subscribers mobile
handset. Email arriving at the Email server is forwarded to the ISMSC. The
ISMSC converts the Email into SMs, which are forwarded to the subscribers
handsets.
Each subscriber is provided with a unique Email address. For example, a
subscriber of the provider named telco with the mobile number 1234567 has an
Email address resembling the following: 1234567@sms.telco.com. Email sent to
this address will be delivered as an SM to the handset with the number 1234567.
The SM includes the senders ID, the subject and a limited amount of text.
Page 2-3
Chapter 2

The service is based on an Email server on the IMU (Paragraph 7.2.). The ISMSC
receives Email messages via SMTP and converts them to SMs for delivery to the
subscriber.
A subscriber may also forward his Email to his handset via the ISMSC. The
address in this case resembles tel. number@domain name, where domain name is
the ISMSC address.
3.2.
ISMSC Paging Operator Stations

The ISMSC supports the Comverse ISMSC Paging Operator Station (IPOS), and
can also interface to other operator stations using TCP/IP, WAN, and TAP
protocols.
The IPOS is an ISMSC supported application that allows the network operator, or
customers of the network operator to set up a Short Message Desk. This handles
guest callers requests to send an SM to a mobile subscriber. The attendant at the
SM Desk types in the message manually or selects a pre-defined message and
sends it via a TCP/IP connection to the ISMSC, which transmits it to the
subscribers handset.
IPOS consists of a PC platform that interfaces to the ISMSC, and a PC-based
Paging Operator Station software package that runs on a Windows 95-based GUI.
The station can be located at the network operators site, or provided by the
network operator as a service to corporations or other organizational customers. In
the latter case, the IPOS user station is connected to the ISMSC via WAN or
modem.
The guest caller may reach the Short Message Desk in two ways:
x
The operator sets up a global access number for a Short Message Delivery
Service, which terminates at the Short Message Desk.
Calls can be diverted from a Voice Mail guest session to an IPOS operator,
if the guest decides to leave a short message in addition to, or instead of, a
voice message.
The IPOS package supports multiple languages, including oriental languages. An

unlimited number of commonly used messages can be maintained separately on
each workstation as a list, for the convenience of the operator in generating
messages. Messages in one language can be mixed with messages of another
language in this list.
Messages can be up to:
Page 2-4
160 characters long in English and phonetically based languages
70 characters long in ideographic based languages such as Chinese,

Japanese and Korean

3.3.
Chapter 2
Web Access
The Web Access application serves as a Web to the SMS interface providing
HTTP Gateway functionality. Users on the Internet/Intranet can send SMs to
subscribers using a standard Web browser, with the mobile number as the
subscribers identifier address.
Using standard commercially available internet browsers (Netscape Navigator
version 3 and up, Microsoft Explorer version 3 and up), the sender accesses the
service providers HTML page (e.g. sms.cellprov.com), enters the telephone
number of the subscriber, the senders name, and the short-message text, and
clicks Send Message. The Web server forwards the message to the ISMSC,
which forwards it as an SM to the subscriber.
The application also includes multi-language support enabling the user to specify
the language used for the message text. However, the ability to enter text in
foreign languages is not part of the application, but is rather dependant upon the
capabilities of the Web browser and the underlying operating system.
Service providers can extensively customize the screen to include any
information, advertisements, and links to other sites.
3.4.
Operator Generated Short Messages

An operator has the ability to type a short message on a terminal and send it to the
ISMSC. The textual information is then delivered to the MS. Refer to Chapter 4,
Paragraph 4.3.4.
4.
ISMSC Functionality
This section contains the following subsections:
4.1.
Short message delivery (Paragraph 4.1.)
Future delivery (Paragraph 4.2.)
ISMSC message types (Paragraph 4.3.)
TRILOGUE INfinity VMS as an EI (Paragraph 4.4.)
Processing of inputs from EI (Paragraph 4.5.)
ISMSC retry mechanism (Paragraph 4.6.)
ISMSC delivery mechanism (Paragraph 4.7.)
Delivery receipt messages (Paragraph 4.8.)
ISMSC treatment of service center Alert/Notification (Paragraph 4.9.)
Short Message Delivery

The life of a short message in the system can be described as follows:
1.
An SM is received by the ISMSC from an EI.
Page 2-5
Chapter 2
2.
4.2.

The ISMSC tries to deliver the short message through the MAP layer
running on top of the SS7 stack. When the ISMSC has finished processing a
message, it can send a delivery confirmation or a non-deliverable indication
(after several attempts have been made) to the EI, if requested. In a system
integrated with TRILOGUE INfinity, the confirmation/non-deliverable
indication is sent to the TRM. For a full description of call flows, refer to
Paragraph 5.
Future Delivery
The ISMSC supports Future Delivery.
NOTE:
4.3.
This feature is available upon prior consultation with your Comverse

representative.
ISMSC Message Types

The ISMSC supports the following messages:
4.4.
Send SM: Contains the fields: to (subscriber number), from, message text.
Optional fields include: callback number (a variation on the From field),
number of messages, replace (refer to Paragraph 4.5. step 1), and the icon
fields: type, information.
Send SM Acknowledgement
Cancel SM
Cancel SM Acknowledgement
Notification
TRILOGUE INfinity VMS as an EI

When the EI is TRILOGUE INfinity, the standard messages are used as follows:
Page 2-6
Send SM is used for VMN ON (TRILOGUE to ISMSC)
Send SM Ack is used for VMN ON-ACK (ISMSC to TRILOGUE)
Cancel SM is used for VMN OFF (TRILOGUE to ISMSC)
Cancel Ack SM is used for VMN OFF- ACK (ISMSC to TRILOGUE)
Notification is used for Message-Delivery-Confirmation (ISMSC to

TRILOGUE) on VMN ON messages
Notification is used for Message-Nondeliverable-Notification (ISMSC to

TRILOGUE) on VMN ON messages
Send SM is used for Predefined or Numbered messages (TRILOGUE to

ISMSC)

Chapter 2
Send SM Ack is used for Predefined or Numbered ACK (ISMSC to

TRILOGUE)
In cases of VMN ON, the replace feature is utilized. Predefined and Numbered
messages do not use the replace feature. (Refer to Paragraph 4.5. step 1.)
The text in the message used for VMN ON contains some or all of the following
information:
4.5.
The date and the time
The number of new voice messages
The number of urgent voice messages
The number of fax messages
The number of fax pages
The number of played messages
The last calling line identity
The mailbox number
The type and date of the last message received
Processing of Inputs from EI

The Email, Web, SMPP, and TAP EIs use only the Send SM. There is no
replacement, icon, From field, or Notification.
Upon receipt of a Send SM message the following process is activated:
1.
The ISMSC records the SM. If Replace is activated, the previous message of
the same type from the same EI is deleted. The new SM is placed at the end
of the queue. If replace is not activated, the new SM is placed at the end of
the queue.
2.
The ISMSC sends a Send Ack to the EI.
3.
If the subscriber has no pending messages, delivery is attempted. If the

subscriber has pending messages, delivery of the first message in the queue
is retried.
4.
If delivery in step 3 is successful, the message is deleted. In the case of

Send SM messages, a delivery confirmation (Notification) is sent to the EI
(if requested).
5.
If step 3 fails due to a temporary reason, as defined below, the message is

scheduled for retry and the ISMSC records a request to the network to
inform the ISMSC when the subscriber becomes available.
A partial list of situations which may cause temporary delivery failure:
x
The MS is not operational.
The MS memory is full.
Page 2-7
Chapter 2
6.

If step 3 fails due to permanent failure and the MS is incapable of receiving

short messages, the message is deleted. In the case of Send SM messages, a
non-deliverable-notification is optionally sent to the EI (Notification).
Receipt of a Cancel SM message activates the following processing:
4.6.
1.
Any pending SMs of the same EI for the current MS is deleted.
2.
A Cancel SM Ack message is sent back to the EI.
3.
No indication is sent to the MS.
ISMSC Retry Mechanism

There are two retry mechanisms. Smart retries (Paragraph 4.6.1.) allow for
varying retry schedules, depending on the reason for failure. In addition, internal
retries (Paragraph 4.6.2.) are used when delivery was not possible due to internal
ISMSC problems.
4.6.1.
Smart Retries
The Smart Retries feature configures individual retry schedules according to the
various reasons for unsuccessful delivery. The feature provides maximum
flexibility in scheduling next delivery attempts. Each Target EI, in case of delivery
failure, passes to the SFE an array of the diagnostic elements. The contents of the
diagnostic array depends on the type of the cellular network (GSM or IS-41C).
For GSM networks the diagnostic array is composed of the following:
x
Error reason as defined by MAP standards (GSM 09.02)
Error cause as defined by MAP standards (GSM 09.02)
Error codes as defined by MAP standards (GSM 03.40)
For IS-41C networks the diagnostic array is composed of the following:

x
Network entity (HLR, MSC) originating the error code
Error category (for example Return Error, SMDPP Error etc.)
Error cause/reason (TIA/EIA/IS-41-C)
Notification (alert) availability code
Each of these errors is mapped to a General (proprietary) Error derived from

MAP. For each General Error there is a Retry Decision Rule. The Retry Decision
Rule specifies which Retry Profile Definition is used for that specific error. Retry
Profile Definitions are the retry schedules defined in the system.
In order to further refine the retry capabilities, additional retry profile definitions
may be defined for the actual diagnostic array of errors. These additions are also
defined as Retry Decision Rules. Refer Chapter 10, Paragraph 7.2. for a full
discussion of Smart Retries.
Page 2-8

Chapter 2
When the ISMSC has received an error and needs to select a retry decision rule, it
first searches for a retry rule defined for the specific diagnostic array of errors. If
none exists, it proceeds to the general retry decision file, which defines the retry
rules for the general errors. If a retry decision rule for the error is not defined, the
retries are performed according to the default retry profile.
The Absent Subscriber error is used together with a timer in order to distinguish
between subscribers that are actually detached (handset is turned off) and
subscribers that are out of coverage. If the handset is turned off, the message
delivery is retried after an Alert/Notification is received. If the subscriber is out of
coverage, message delivery is retried on a short term schedule.
4.6.2.
Internal Retry
Internal Retry is used for retrying messages that were not successfully delivered
due to internal ISMSC problems, typically overload. These messages can usually
be delivered successfully in a short time, and therefore should be retried after a
short delay.
4.7.
ISMSC Delivery Mechanism

ISMSC delivers messages to the PLMN through MAP services. Refer to
Paragraph 5.
4.8.
Delivery Receipt Messages

In addition to the SMS-Status-Report receipt messages defined by GSM 03.40
(used for phase II handsets), the ISMSC can reformat the receipt message as a
standard MT SM using the SMS-Deliver message for phase I handsets. Receipts
may be configured in up to 254 languages using English, traditional Chinese, and
simple Chinese character sets.
4.9.
ISMSC Treatment of Service Center Alert/Notification

ISMSC receives Service Center (SC) Alerts from the PLMN through MAP
services. Receipt of an SC Alert for a particular MS causes a delivery retry, after a
pre-defined time-out has elapsed, due to a delay between the time the network
sends the alert and the time the MS is able to receive a short message. When
ISMSC delivers the message successfully, it sends a confirmation to the originator
of the message.
Page 2-9
Chapter 2
5.

ISMSC Interface with the PLMN

The ISMSC to PLMN protocol is implemented via a MAP interface over SS7. The
MAP layer of the ISMSC implements the functionality of the SMS-GMSC and
SMS-IWMSC. Paragraphs 5.1. and Paragraph 5.2. present call flow scenarios
which show the services used by the SMSC application, to communicate with the
GSM and the IS-41C networks (HLR and MSC) via the MAP layer. These are
examples of typical call flows. Not all possible parameters are presented.
5.1.
MAP Protocol Message Flow in GSM Systems

The ISMSC serves as both GMSC and IWMSC in the GSM PLMN. Supported
services (as defined in GSM Phase I and Phase II GSM standards 09.02 and 03.40)
are:
5.1.1.
Mobile terminated short message service transfer. This procedure allows for
delivery of short messages to MSs.
Short message waiting data set procedure. This procedure allows for the
ISMSC, in the event that it has failed to deliver a message to a MS, to ask to
be notified with an alert when the MS becomes reachable or has enough
memory to receive a new message. Note that even in the case of successful
delivery, this procedure may be used to notify the HLR of this success, so
that the HLR can remove the Alert flag, and alert other SMSCs in the
network (Phase II). This is an ISMSC configurable parameter.
Short message alert procedure. This procedure allows for a notification to

be sent from the ISMSC when an MS becomes reachable, or has enough
memory to receive new messages.
Mobile Originated SMS transfer.
Successful DeliveryGSM
This scenario (Figure 2-1) presents a successful delivery of an SMS message:
a
ISMSC sends a SendRoutingInfoForSMRequest to the HLR. The HLR is

addressed by the MSISDN. The request message contains the following field:
MSISDN: Mobile Subscriber International ISDN Number
HLR responds with a SendRoutinginfoForSMConfirmation the ISMSC. The

confirmation message contains the following fields:
MSC ADDRESS: Mobile Switching Center Address
IMSI: International Mobile Subscriber Identification
Page 2-10

Chapter 2
ISMSC sends a ForwardSMRequest to the MSC. The MSC is addressed using

the Global Title returned in the SendRoutingInfoForSM from the HLR. The
ForwardSMRequest message contains the following fields:
USER DATA: Message text as defined by GSM 03.40
The MSC responds with a ForwardSMConfirmation indicating successful

delivery.
Figure 2-1: GSM. Successful Delivery
5.1.2.
Delivery Failure at MSC Due to Temporary ErrorGSM

This scenario (Figure 2-2) presents a delivery failure at the MSC due to a
temporary error:
a
ISMSC sends a SendRoutinginfoForSMRequest to the HLR. The HLR is

HLR responds with a SendRoutinginfoForSMConfirmation to the ISMSC. The

Page 2-11
Chapter 2


the Global Title returned in the SendRoutinginfoForSM from the HLR. The
MSC responds with a temporary error in the forward SM confirmation (e.g.,

absent subscriber).
ISMSC sends a ReportSMDeliveryStatusRequest to the HLR that contains the

following field:
The HLR responds to the ISMSC with a ReportSMDeliveryStatusRequest

Acknowledgment.
Figure 2-2: GSM. Temporary Error at MSC
5.1.3.
Delivery Failure at HLR Due to Temporary ErrorGSM

This scenario (Figure 2-3) presents a delivery failure at the HLR due to a
temporary error:
a

Page 2-12

Chapter 2
HLR responds with temporary error in the

SendRoutinginfoForSMConfirmation.
Depending on the configuration and availability, the HLR can send the ISMSC
an InformSC message notifying the ISMSC that the ISMSC has been registered
for future Alert when the MS becomes available.
Figure 2-3: GSM. Temporary Error at HLR
5.1.4.
Delivery Failure at MSC Due to Permanent ErrorGSM

permanent error:
a

HLR responds with a SendRoutinginfoForSMConfirmation to the ISMSC. The

MSC: Mobile Switching Center

the Global Title returned in the SendRoutingForSM from the HLR. The
MSC: Mobile Switching Center
Page 2-13
Chapter 2

The MSC responds with a permanent error in the ForwardSMConfirmation

message. The result of this is that the SC does not attempt delivery of this SM
again and the ISMSC will erase this message from its database.
Figure 2-4: GSM. Permanent Error at MSC
5.1.5.
Delivery Failure at HLR Due to Permanent ErrorGSM

permanent error:
a

addressed by the MSISDN. The request message contains the following
field:
Page 2-14
The HLR responds with a permanent error in the

SendRoutinginfoForSMConfirmation. The result of this is that the SC
does not attempt delivery of this SM again and the ISMSC will erase this
message from its database.

Chapter 2
Figure 2-5: GSM. Permanent Error at HLR
5.1.6.
Alert Followed by Successful DeliveryGSM

In this scenario (Figure 2-6) a subscriber with pending messages becomes
available. The Message Waiting Dataset in the HLR and SC Alert messages are
the means to notify the SC that the subscriber is available, and any pending SMs
should be delivered.
MWD: Message Waiting Dataset. Stores information about absent subscribers that
have pending messages. For each subscriber, a list of service centers that have
messages pending for this subscriber is kept. An SC will automatically be added
to the MWD in case of failure to deliver a message due to a subscriber being
absent.
SC Alert: The HLR notifies all Service Centers listed in the MWD when a
subscriber becomes active, by sending them an SC Alert. The SCs can then retry
delivery of pending messages to the subscriber. SC Alerts are transferred to the
SC via the SMS-IWMSC module of the MAP layer.
a
The HLR sends an AlertServiceCenter message to the ISMSC. This message

contains the following field:
b
thru
d.
On receipt of the AlertServiceCenter message the ISMSC can resend an SMS

message to the MSC now that it knows that the MS is available. Refer to
Paragraph 5.1.1 for complete details of messages.
Page 2-15
Chapter 2

Figure 2-6: GSM. Alert Followed by Successful Delivery
5.2.
MAP Protocol Message Flow in IS-41C Systems

In IS-41C networks, the ISMSC serves as the MC. Supported services (as defined
in Telecommunications Industry Association (TIA) IS-41 Standard) are:
5.2.1.
Short Message Delivery Point to Point service. This procedure allows for
delivery of short messages to MSs (also uses the Short Message Request
service).
Short Message Notification procedure. This procedure allows for a

notification to be sent to the ISMSC when an MS becomes reachable, or has
enough memory to receive new messages.
Successful DeliveryIS-41C
This scenario (Figure 2-7) presents a successful delivery of an SMS message:
a
ISMSC sends an SMSRequest message to the HLR. The HLR is addressed by

global title or Point Code translation of the MIN. The request message contains
the following fields:
MIN: the subscribers mobile identification number
SMS_NotificationIndicator: set to notify when available
HLR responds with the current SMS routing address. The ACK message
includes the following fields:
ESN: the subscribers electronic serial number
SMS_Address: the subscribers current SMS routing address
Page 2-16

Chapter 2
ISMSC sends an SMSDeliveryPointToPoint message to the MSC. The MSC is

addressed using the SMSAddress returned in the SMSRequestACK. The request
message contains the following fields:
MIN: The subscribers mobile identification number
ESN: The subscribers electronic serial number (as received in the SMSRequest
ACK)
SMS_TeleserviceIdentifier: Set to the appropriate CDMA/TDMA Teleservice.
SMS_OriginatingAddress: For voice mail notifications, optionally set to the
VMS access number
SMS_ChargeIndicator: Value taken from configuration, or from the incoming
message.
SMS_BearerData: Contains the teleservice specific data, as defined in IS-637
for CDMA and IS-136 for TDMA.
MSC responds with an SMSDeliveryPointToPointACK indicating successful

delivery. The ACK message may include SMSBearerData that is ignored by the
ISMSC.
MSC
HLR
ISMSC
SMSRequest [MIN]
SMSRequestACK
[SMSAddress, ESN]
SMSDeliveryPointToPoint
[MIN, ESN]
SMSDeliveryPointToPointACK
a
b
c
d
IDG00584
Figure 2-7: IS41. Successful Delivery
5.2.2.
Delivery Failure at MSC Due to Temporary ErrorIS-41C

temporary error:
Page 2-17
Chapter 2


HLR responds with the current SMS routing address. The ACK message includes

ACK)
VMS access number
message.
SMS_BearerData: Contains the teleservice specific data, as defined in IS-637 for
CDMA and IS-136 for TDMA.
MSC responds with an SMSDeliveryPointToPointNAK message. The NAK

message contains:
SMS_CauseCode: IS41 Error Code
If the IS41 error code is SMS Delivery Postponed, a notification is sent when the
error condition is removed. Otherwise, a notification will not be sent to the
ISMSC.
Page 2-18

Chapter 2
Figure 2-8: IS41. Temporary Error at MSC
5.2.3.
Delivery Failure at HLR Due to Temporary ErrorIS-41C

temporary error:
a

HLR responds with an access denied reason. The NAK message includes the
following fields:
SMS_AccessDeniedReason: Postponed
A notification will be sent to the ISMSC when the error condition is removed
(subscriber becomes available).
Page 2-19
Chapter 2
MSC

HLR
ISMSC
SMSRequest [MIN]
SMSRequestNAK
[SMSACCDEN=postponed]
IDG00582
Figure 2-9: IS41. Temporary Error at HLR
5.2.4.
Delivery Failure at HLR Due to Permanent ErrorIS-41C

permanent error:
a

HLR responds with an access denied reason. The NAK message includes the
following field:
SMS_AccessDeniedReason: Denied
The result of this is that the SC does not attempt delivery of this SM again and
the ISMSC will erase this message from its database.
Page 2-20

MSC
Chapter 2
HLR
ISMSC
SMSRequest [MIN]
SMSRequestNAK
[SMSACCDEN=denied]
a
b
IDG00581
Figure 2-10: IS41. Permanent Error at HLR
5.2.5.
Delivery Failure at MSC Due to Permanent ErrorIS-41C

permanent error.
a

HLR responds with the current SMS routing address. The ACK message
includes the following fields:
Page 2-21
Chapter 2


MIN: The subscribers mobile identification number
ACK)
VMS access number
message.
MSC responds with an SMSDeliveryPointToPointNAK message. The NAK

message contains the field:
SMS_CauseCode: Set to, for example originating/terminating denied,
encoding problem
The result of this is that the SC does not attempt delivery of this SM again and
the ISMSC erases this message from its database.
Page 2-22

Chapter 2
Figure 2-11: IS41. Permanent Error at MSC
5.2.6.
NotificationIS-41C
In this scenario (Figure 2-12) a subscriber with pending messages becomes
available. The HLR/MSC knows that there are pending messages, since the
ISMSC always sets SMSNotificationIndicator when sending SMSRequest and
SMSDeliveryPointToPoint. Therefore the following sequence is triggered:
a
The HLR (or MSC) sends an SMSNotification message to the ISMSC. The
notification message contains the following fields:
SMS_Address: the current routing address of the subscriber
Note that the Notification comes from the HLR if the previous error was in the
HLR, and the Notification comes from the MSC if the previous error was in the
MSC.
ISMSC with an ACK. There are no parameters to the ACK.
Page 2-23
Chapter 2


addressed using the SMSAddress supplied in the SMSNotification message.
The delivery message contains the following fields:
MIN: The subscribers mobile identification number (as received in the
SMSNotification message)
ESN: The subscribers electronic serial number (as received in the
SMSNotification message)
VMS access number
message.
MSC responds with an SMSDeliveryPointToPointACK indicating successful

delivery. The ACK message may include SMSBearerData that is ignored by the
ISMSC.
MSC
HLR
ISMSC
SMSNotification
[MIN,ESN,SMSAddress]
SMSNotificationACK
SMSDeliveryPoint
[MIN, ESN]
SMSDeliveryPointToPointACK
a
b
c
d
IDG00579
Figure 2-12: IS41. Notification
5.3.
Mobile Originated Messages in GSM Systems

The ISMSC supports the exchange of messages between mobile subscribers in
GSM systems.
Page 2-24

Chapter 2
An MO message is carried from a mobile station through an MSC to the ISMSC

via the MAP FORWARD SM message. Upon receipt of this message the ISMSC
stores the MO in its database, and acknowledges the message to the MSC.
In the case of an illegal sender or an invalid parameter, the message is rejected
and an error is returned to the MS using a MAP_FORWARD_SM Response.
If the sender is legal, the ISMSC formats a short message from the MO message,
and sends it as a normal Mobile Terminated (MT) message to the destination
mobile subscriber. The ISMSC has the capability to modify the destination
address if necessary. Once the short message reaches a final state (delivered,
undeliverable, or expired), the ISMSC optionally (subscriber defined) formats a
receipt, and sends it to the mobile subscriber that originated the SM. The receipt
is sent as an SMS-Status-Report.
All short message traffic, both MO and MT, is carried by the MAP FORWARD
SM message. This MAP message contains the actual short message in a field
called SM_RP_UI. This field consists of a Short Message Transfer Protocol Data
Unit (SM-TP-DU). SM-TP defines several types of messages:
SMS_DELIVER
Used for normal MT short messages.
SMS_SUBMIT
Used for normal MO short messages.
SMS_STATUS_REPORT
Used for sending a receipt as an MT message.
SMS_COMMAND
Used for transferring short message commands from a

mobile subscriber to an SMSC.
The ISMSC support of MO together with MT messages consists of using

SMS_DELIVER, SMS_SUBMIT and SMS_STATUS_REPORT TPDUs.
The typical scenario is (Figure 2-13):
a
Mobile-A sends a short message to Mobile B by sending an SMS_SUBMIT to

the ISMSC via MSC-A.
The MSC-A forwards the SMS_SUBMIT within a MAP FORWARD_SM to the

ISMSC.
The ISMSC receives the MO messages, carried by FORWARD_SM messages.
The ISMSC performs the IWMSC operations for Mobile Originated messages.
It also decodes the SMS_SUBMIT messages.
ISMSC formats a short message from the SMS_SUBMIT and stores it in its
database. It then acknowledges the message with a MAP_FORWARD_SM
response, to MSC-A.
MSC-A forwards the ISMSCs response to Mobile-A.
The mobile terminated procedure is performed by the ISMSC, as for any MT

procedure.
Page 2-25
Chapter 2

When the short message reaches a final state, the ISMSC formats an
SMS_STATUS_REPORT message and sends it in a standard Mobile
Terminated procedure to Mobile-A (if provisioned to do so).
When the message reaches a final state, the ISMSC generates a state
notification message. The ISMSC formats the notification in a form of a short
message, stores it in its database, and then tries to deliver this message. When
the ISMSC receives a notification message, it formats an
SMS_STATUS_REPORT TPDU from the notification, and sends it to the
mobile that originated the message, as an MT message.
Figure 2-13: Mobile Originated Message Delivery (GSM)
6.
ISMSC Management Features

x
Management interface (Paragraph 6.1.)
Configuration parameters (Paragraph 6.2.)
Billing information (Paragraph 6.3.)
User interface (Paragraph 6.4.)
Alarms (Paragraph 6.5.)
Prevention of Abuse (Paragraph 6.6.)
Page 2-26

6.1.
Chapter 2
Management Interface
The user interface for ISMSC administration is activated on a UNIX ASCII
terminal, using a command line or screen interface or a GUI. In the case of a
system integrated with TRILOGUE INfinity, this enables remote operations from
the TRM via Telnet.
The following operator commands are available on all interfaces:
x
Start ISMSC
Stop ISMSC
Show ISMSC status: current number of input sources and their type, status
of the MAP external interfaces, status of SFE (Store and Forward Engine),
number of waiting messages in SFE, etc.
Show ISMSC statistics: total number of messages in ISMSC, number of

incoming messages per hour, number of completed delivery of message (by
final status) per hour, number of messages in active queue per hour, etc.
NOTE:
6.2.
The GUI is documented in the ISMSCOMAP and Customer Care

Graphic User Interface Applications Technical Bulletin, P/N 10-1800085.
Configuration Parameters
The following is a partial list of ISMSC configuration parameters:
6.3.
Maximum life of a short messages (expiry, in minutes)
Time-out between receipt of SC Alert and actual message delivery retry (in
seconds)
Smart Retries parameters
Billing Information
ISMSC billing information is accumulated in billing files on the ISMSC platform.
The data is retrieved by a billing computer through an FTP mechanism (preferably
at non-busy hours). The billing record includes the following information:
x
Entry date and time of message to ISMSC
Final state date and time
Mobile originator (subscriber telephone numberonly for MO SMs)
Mobile destination subscriber number (telephone number)
Final state (delivered, non-deliverable, expired, cancelled)
Number of retries until message reached final state
Input source of message (EI Id)
Page 2-27
Chapter 2
6.4.

Message typemessage or notification
User Interface
The command line interface and screen interface enable generation and
transmission of short messages to the ISMSC. Refer to Chapter 4.
6.5.
Alarms
There is an optional alarm processor, the Integrated Alarm Package (IAP), that
provides the capability for reporting system and functionality alarms. When the
ISMSC is part of a TRILOGUE INfinity system the IAP is integrated in the
system.
6.6.
Prevention of Abuse
The ISMSC allows network operators to define which mobile numbers are
allowed to initiate Mobile Originated messages, for example to allow or bar MO
messages of non-network subscribers. When an MO message is received by the
SFE, the originating address is compared with either a white (permitted) or black
(prohibited) list. If the address is prohibited, it is rejected by the SFE and an error
is returned to the mobile, by a MAP_FORWARD_SM message with the user error
GSM_MAPERR_SM_DELIV_FAILURE (32).
The white and black lists specify ranges of acceptable mobile number prefixes.
Typically, the prefix ranges correspond to different operators, allowing the system
to distinguish between native subscribers and those of other operators.
Configuration of black and white lists is detailed in Chapter 10, Paragraph 7.6.3.
7.
Architecture
The ISMSC system is designed to interface with any voice mail system (as well as
TRILOGUE INfinity and AccessNP) and can be configured for different sizes and
levels of redundancy. An overview of the system architecture for the ISMSC
(including both internal connections and external interfaces) is presented in
Figure 2-14. For a complete discussion of the software packages, refer to
Chapter 3.
The ISMSC is composed of the following modules:
x
ISMSC comprised of SFE and MAP
IMU (when configured with Web/Email services)
Disk Drawer (optional)
Firewall (required when configured with Web/Email services)
Remote Access Unit (when configured with IPOS/TAP modem connection)
Router
Page 2-28

Chapter 2
Terminal Server Unit
Figure 2-14: ISMSC System Architecture
7.1.
ISMSC
The ISMSC runs on the Pentium II, 233 MHz, platform. ISMSC configurations are
classified as small, medium or large, and each of these can be non-redundant or
redundant.
In the small configuration, the MAP and SFE and OMNI are installed on the same
platform as the software packages for call control. The small configuration is only
available in an installation with TRILOGUE INfinity. In this case, it shares
software packages with the OMNI CCS. In the medium configuration, the MAP,
SFE and OMNI are installed on the same platform.
7.2.
Internet Messaging Unit

The Internet Messaging Unit (IMU) platform enables Email and Web access
services. The IMU is connected to the system via a separate section of the system
hub. The IMU runs on the Pentium platform.
Page 2-29
Chapter 2
7.3.

Disk Drawer
The optional Disk Drawer (DDR) option serves the two SFEs as a data storage
unit and to reduce disk read/write access time and LAN load. To reduce access
time, a Raid application is installed on the SFE. The DDR option provides the
ISMSC with data redundancy capability (for a single disk failure). The DDR is
connected to the two SFEs via a SCSI connection.
7.4.
Firewall
A firewall must be added to the system when web and email connectivity is
required. The firewall is based on the Pentium platform.
7.5.
Hub
The ISMSC system has optional redundant hubs to support LAN data
communications within the system when a redundant hub is required. Each of the
hubs is connected to one SFE (two in the case of redundancy), one MAP (two in
the case of redundancy), one Router (two in the case of redundancy), one RAU
(two in the case of redundancy), one Web connection (for Firewall and Internet
Services) and one connection to the customers administrative LAN.
7.6.
Remote Access Units

The Remote Access Units (RAU) enables a connection of the ISMSC system LAN
to remote stations via telephone lines. The RAU is required when the IPOS
application is installed on a remote PC or for the TAP interface. The system can
support two RAUs in a load sharing configuration.
7.7.
Routers
Routers are used to connect the ISMSC system to the host voice mail system. The
router facilitates the connection of the ISMSC LAN to the host LAN while
maintaining two separate nets. Routers are also used for Internet and
administrative LAN connectivity. The ISMSC system has redundant Routers for
redundant systems.
7.8.
Terminal Server Unit

The system has one Terminal Server Unit (TSU) which provides access to all
ISMSC computer platforms via serial ports. This feature is needed for
maintenance when the platform is not accessible through the LAN connection.
The TSU has one LAN connection to one of the system Hubs and one serial
connection for each of the ISMSC system platforms. If the system does not
include an RAU, a modem connection to the TSU is provided to enable remote
access to the system.
Page 2-30

8.
Chapter 2
Connectivity with IPOS

There are four methods of connecting IPOS with the ISMSC:
x
Local network (Figure 2-15)
Remote dial-up (Figure 2-16)
Remote customer intranet (Figure 2-17)
Remote public network (Figure 2-18)

TRM
IPOS
Station
ISMSC
HUB
INfinity
HSBN
Cisco
Router(s)
IPOS
Station
ISMSC
Units
IDG00964
Figure 2-15: IPOS Connected to a Local Network
TRM
MODEM
INfinity
HSBN
ISMSC
HUB
Cisco
Router(s)
RAU
MODEM
ISMSC
IPOS
Station
IPOS
Station
Units
IDG00965
Figure 2-16: IPOS Connected by Remote Dial-Up
Page 2-31
Chapter 2

IPOS
Station
TRM
IPOS
Station
Router
INfinity
HSBN
ISMSC
HUB
Cisco
Router(s)
ISMSC
Units
IDG00966
Figure 2-17: IPOS Connected to a Remote Intranet

Public
Network
Router
TRM
Firewall
INfinity
HSBN
Firewall
(optional)
Firewall
(optional)
IPOS
Station
IPOS
Station
ISMSC
HUB
Cisco
Router(s)
ISMSC
Units
IDG00967
Figure 2-18: IPOS Connected to a Remote Public Network
Page 2-32

9.
Chapter 2
Redundancy
The ISMSC is available in an active standby configuration. In this configuration,
the ISMSC hardware and software are duplicated to provide redundancy/fault
resilience. The active system provides service to the EIs. In case of failure of the
active system, the standby system takes over. It is then the responsibility of EI to
establish connection with the standby ISMSC. (The EIs determine when the
ISMSC has performed a switchover through the use of Keep Alive messages.) The
database of short message pending delivery is mirrored in the standby system.
When the standby takes over and becomes active it continues from where the
active stopped. In order to make efficient mirroring, loss of a few messages is
possible during switchover. Switchover will not occur if the active ISMSC fails
and restarts during a 10 second period. Since this configuration involves database
mirroring, a running standby does not immediately imply redundancy. When the
standby system comes up, it first has to synchronize its database with the active
system (so that the mirroring is complete).
Page 2-33
Chapter 3
Design and Software
Structure

Chapter 3
Design and Software Structure
Table of Contents
1. Introduction .............................................................................................................................3-1
2. ISMSC Software General Description ...................................................................................3-1
2.1. Modules .............................................................................................................................3-1
2.2. ISMSC Software Modules..................................................................................................3-2
2.2.1. The Dispatcher (DSPTCH) .........................................................................................3-2
2.2.2. The Store and Forward Engine (SFE) ........................................................................3-2
2.2.3. The External Interface ................................................................................................3-3
2.2.4. The SFE/EI API...........................................................................................................3-4
2.2.5. The Man Machine Interface (MMI)..............................................................................3-4
2.3. Processes ..........................................................................................................................3-4
2.4. Interfaces ...........................................................................................................................3-4
2.4.1. The SFE/EI Interface ..................................................................................................3-4
2.4.2. The Control Interface ..................................................................................................3-5
3. System Configuration.............................................................................................................3-5
4. System Capacity Limitations .................................................................................................3-6
List of Figures
3-1
ISMSC Software Components............................................................................................3-1
3-2
ISMSC Configuration Options.............................................................................................3-6
Page 3-i

1.
Chapter 3
Introduction
This chapter presents the ISMSC top-level design and the ISMSC software
architecture. It contains a description of the ISMSC components/modules, their
division into processes, the interfaces between them, and how major procedures
are performed by the ISMSC software.
2.
ISMSC Software General Description
2.1.
Modules
The ISMSC software consists of a main engine called the Store and Forward
Engine (SFE). The SFE interacts with various external interfaces (EIs), which
represent the various input/output sources, known as Short Message Entities
(SMEs). Figure 3-1 shows the ISMSC software components.
Figure 3-1: ISMSC Software Components

The SFE is independent of the EIs. The main elements of the SFE are the database, the retry mechanism based on a timer, and the active messages queue.
The EIs hide the details of the SME and the interaction with it from the SFE,
reducing the interaction with the SFE to generic primitives. An EI may be a source
of short messages, a destination of short messages, or both.
EIs may be grouped according to types. Each group is capable of interacting with
a group of SMEs (e.g., two EIs interfacing to the digital cellular network, each
capable of reaching all the network subscribers). This feature is designed for loadsharing and redundancy purposes.
Page 3-1
Chapter 3

An EI may be local to the SFE (i.e., run in the same machine) or remote (i.e., run
in another machine, or even in another platform). This feature is transparent to the
SFE.
Since different EIs may have different characteristics which are unrelated to the
SFE (e.g., an EI that interacts with the GSM network, an EI that interacts with
TRILOGUE INfinitys TRM, or an EI that interacts with a data-processing
application), the SFE and the EIs interact through a proprietary Application
Program Interface (API).
The API offers SFE services to be used by the EIs (hereafter called SFE services),
and EI services, to be used by the SFE (hereafter called EI services).
The interaction between EIs and SMEs is subject to agreement between the SME
provider and the ISMSC provider. Currently, a proprietary messaging protocol
(based on TCP/IP connections) can be used for interaction between any SME that
can implement the protocol and a standard (built-in) EI of the ISMSC. If the
protocol is not suitable for the SME, a new EI must be implemented.
2.2.
ISMSC Software Modules

The ISMSC consists of the following modules, some of which are divided into
submodules.
2.2.1.
The Dispatcher (DSPTCH)

The ISMSC software is event driven, hence the main-loop consists of a
dispatcher waiting for events to occur, and dispatching the related handler (in SFE
or EIs) when the event occurs. Examples of events are: a new short message has
arrived, a time-out has occurred, etc. When a number of events occur
simultaneously, the dispatching is done according to a priority mechanism.
The Dispatcher is responsible for:
2.2.2.
Registering events and their handlers
Dispatch handlers when events occur
The Store and Forward Engine (SFE)

The SFE is the core of the ISMSC software. It performs the short message store
and forward procedures.
The Store and Forward Engine is responsible for:
Page 3-2
Short message store and forward
Retry mechanism
Supervising the EIs
Routing messages to EIs
Handling control requests

Chapter 3
Since the SFE has many tasks, it is functionally divided into the following
submodules:
2.2.3.
The Database (DB): The database contains information about all pending
short messages and the intended subscribers. As soon as a message is
delivered, the information is automatically deleted from the database.
The Timer (TMR): The Timer is responsible for:
Issuing time signals for the retry algorithm
Issuing time-outs in case of short message expiration
Issuing time-outs in case of unanswered dialogue with EIs
The DIALOGUE-Q (DGQ): The Dialogue-Q is responsible for maintaining

the state of each open dialogue with the EIs.
The Router (RUT): The Router is responsible for routing SFE requests to
the appropriate EI(s).
The Control (CTL): The Control is responsible for handling control

requests, and routing them to the appropriate SFE component.
The External Interface

The External Interface (EI) is responsible for:
x
Interaction with the SME
Mediation between the SME and the SFE
Since there is a specific EI for each SME, the functionality of the EIs may vary.
Typical EIs are:
x
Email EI: The Email EI supports the SMTP protocol for sending short
Emails to cellular phones.
IS41 EI: The IS41 EI receives the messages from the SFE and forwards the
messages to the handset.
MAP EI: The MAP EI receives the messages from the SFE, performs the
GMSC operations and forwards the messages to the MS.
MAP-MO EI: The MAP-MO EI receives the MO messages, performs the

GMSC operations and forwards the messages to the SFE.
OPER EI: The OPER EI interfaces with the IPOS (ISMSC Paging Operator
Station) client on a PC for sending short messages.
SMPP EI: The SMPP EI provides support to version 3.3 of the SMPP
protocol.
TAP EI: The TAP EI enables remote application to contact the SMSC using
a modem and sending short message to subscribers using the TAP protocol.
TRM EI: The TRM EI interacts with TRILOGUE INfinitys TRM.
Page 3-3
Chapter 3
2.2.4.

Web EI: The Web EI enables sending short messages to subscribers using a
Web browser.
The SFE/EI API

The EI API is designed to provide a simple API for interaction between the EIs
and the SFE. If a new EI is coded, it can rely on API services provided by the
SFE, and it has to implement its EI services according to the API services as used
by the SFE. This way, addition of new EIs is made very simple.
Note, that the API also conceals from the EI and SFE the distance between
them. This means that the SFE and EI see the same API when they run in the same
machine or in different machines.
2.2.5.
The Man Machine Interface (MMI)

Currently the MMI consists of a set of utilities used for operation of the system.
The utilities interact with the CTL component of the SFE.
The MMI capabilities include:
2.3.
Issue of short messages by the operator
Start/stop the system
Start/stop EIs
Initiate traces of the system components
Initiate status printouts of the system components
Processes
The ISMSC functionality is divided into several processes, some of which may
run on a remote UNIX machine.
2.4.
Interfaces
In this paragraph, a general view of the interfaces between the ISMSC modules is
given.
2.4.1.
The SFE/EI Interface

This interface is called the ISMSC services library. It consists of two libraries:
The SFE services library which enables EIs to contact the SFE, and the EI
services library which enables the SFE to contact the EIs. In both libraries the
interface is based on a two-phase dialog between the parties: a request followed
by a response. This is done to achieve independence of the SFE and EIs in two
aspects:
x
Page 3-4
Several requests can be processed simultaneously.

Chapter 3
Requests are queued and handled when possible. The module servicing the
request can set the priority of its input queues (SFE has several EI input
queues).
There are two possible scenarios which are addressed by the design of this
interface, depending on the physical placement of the EI module. An EI may be:
x
Local: A different process in the same host
Remote: A processes in another host, accessing the SFE via the network
In order to support this interface, a protocol has been defined to enable API based
on any communication channel. The API and protocol are based on an attributevalue scheme (attr1 = value1; attr2 = value2...). The same API is used in all cases.
The EI programmer simply uses the API calls, which are initialized according to
the relevant scenario.
2.4.2.
The Control Interface

An API is defined for issuing control requests:
x
Shutdown
Start EI
Print object(s) (status, messages, subscribers, etc.)
Trace object(s)
Control EI requests: The control interface may be used as an EI to allow the

operator to send SMs
The API is implemented over a TCP/IP communication link with a configurable

control port number.
3.
System Configuration
The ISMSC runs on the Pentium II platform. The ISMSC configurations are
classified as small, medium or large, and each of these can be non-redundant or
redundant. The configuration options are presented in Figure 3-2.
In the small configuration, the MAP and SFE and OMNI are installed on the same
platform as the software packages for call control. The small configuration is only
available when the ISMSC is integrated with TRILOGUE INfinity. In the medium
configuration, the MAP, SFE and OMNI are installed on the same platform. In the
large configuration the MAP and SFE are installed on separate units.
The IMU runs on a Pentium II platform. The IMU is also available in redundant
and non-redundant configurations. In all configurations the UNIX and BASE
packages are installed, with the addition of the application packages required, for
example IPOS, Web Server, and Email server.
Page 3-5
Chapter 3

Figure 3-2: ISMSC Configuration Options
4.
System Capacity Limitations

The ISMSC is delivered in three configurations:
x
Small Capacity System: 60 K BHSM (GSM)
Medium Capacity System: 110 K BHSM (GSM) and 130 K BHSM (IS-41C)
Large Capacity System: 235 K BHSM (GSM) and 250 K BHSM (IS-41C)
NOTE:
Page 3-6
Small and large configurations are available upon prior consultation

with your Comverse representative.
Chapter 4
User Interface

Chapter 4
User Interface
Table of Contents
1. Overview ..................................................................................................................................4-1
2. ISMSC Operation: OMAP Capabilities ..................................................................................4-1
3. System Access ........................................................................................................................4-2
4. User Interfaces ........................................................................................................................4-2
4.1. Screen Interface.................................................................................................................4-2
4.2. Command Line Interface ...................................................................................................4-2
4.3. ISMSC Operation Commands ...........................................................................................4-3
4.3.1. Start Command...........................................................................................................4-3
4.3.2. Stop Command...........................................................................................................4-4
4.3.3. Check..........................................................................................................................4-5
4.3.4. Send Message Command ..........................................................................................4-6
4.4. Maintenance Commands...................................................................................................4-7
4.4.1. Debug Command........................................................................................................4-7
4.4.2. Message Trace Command .........................................................................................4-7
4.5. Administration Commands.................................................................................................4-7
4.5.1. View Status Command ...............................................................................................4-8
4.5.2. Message Retry Command ..........................................................................................4-8
4.5.3. Browse Log Files ........................................................................................................4-9
4.5.4. Distribute Configuration Files......................................................................................4-9
4.6. Host Status ......................................................................................................................4-10
5. Billing Files ............................................................................................................................4-11
5.1. Record Fields Format ......................................................................................................4-11
5.2. Billing Record Examples ..................................................................................................4-15
5.2.1. Handset to Handset (SMS-MO to MT)......................................................................4-16
5.2.2. Notification (Receipt) to Originating Handset............................................................4-16
5.2.3. Application to Handset (SMS-MT from EI)................................................................4-17
5.2.4. Handset to Application (SMS-MO to EI) ...................................................................4-18
Page 4-i
Chapter 4
User Interface

List of Figures
4-1
ISMSC Control Command Menu Screen ........................................................................... 4-4
4-2
ISMSC Check Screen ........................................................................................................ 4-5
4-3
ISMSC Send Message Screen .......................................................................................... 4-6
4-4
ISMSC View Status Screen................................................................................................ 4-8
4-5
ISMSC Message Retry Screen .......................................................................................... 4-9
4-6
ISMSC Distribute Configuration File Screen .................................................................... 4-10
List of Tables
4-1
Fields in the Billing Record Files ...................................................................................... 4-12
4-2
ISMSC Source External Interfaces .................................................................................. 4-14
4-3
Handset to Handset Billing Records ................................................................................ 4-16
4-4
Notification (Receipt) to Originating Handset Billing Records .......................................... 4-16
4-5
Application to Handset Billing Records ............................................................................ 4-17
4-6
Handset to Application Billing Records ............................................................................ 4-18
Page 4-ii

1.
Chapter 4
User Interface
Overview
This chapter provides a general discussion of the ISMSC OMAP commands,
provisioning, information on alarms, and the commands, (screen and command
line interface) for diagnostics and troubleshooting, and procedures for replacing
modules.
2.
ISMSC Operation: OMAP Capabilities

The ISMSC OMAP operations are performed using the standard UNIX command
line interface, the screen interface and a GUI. The GUI is documented in
ISMSCOMAP and Customer Care Graphic User Interface Applications
Technical Bulletin, P/N 10-180-0085.
ISMSC supports the following OMAP capabilities:
x
Starting the SMSC Processes: This command is part of the startup of the
initialization procedures.
Stopping the SMSC Processes: Stopping the ISMSC process causes an

orderly shutdown of all ISMSC activities.
Checking the availability of ISMSC processes (SFE/MAP)
Viewing the Current Status of the SMSC Processes: This command

displays a snap-shot of the current status of the ISMSC processes and the
ISMSC activities. The status report includes also statistics on SMS traffic.
Sending a Short Message to the ISMSC: This feature is used for initial
testing of the system, for administrative purposes, and for troubleshooting.
Toggling SMSC Debug Printouts On/Off: This command is reserved for

technical staff, to help in fault isolation.
Tracing the Life-Cycle of a Short Message: This feature initiates printouts

regarding specified short messages, showing each stage and event in the
processing of the short message (e.g., short message is being re-tried, or
short message has been delivered).
Immediate Retry of Delivery of a Short Message: This feature initiates an

immediate delivery retry of the specified short message.
Distribution of Configuration Changes to all the Units: This feature

distributes configuration changes to all computers, systems or hosts.
Verifying the Role of a SFE Unit: The feature indicates if the unit is active
or standby.
Page 4-1
Chapter 4
User Interface
3.

System Access
To access the ISMSC system, log in to the computer running the SFE software.
This can be done directly through the terminal attached to the computer. When the
ISMSC is part of a TRILOGUE INfinity system the ISMSC can be accessed via a
Telnet session on the TRM.
In order to log in via one of the two methods mentioned above, use the ISMSC
user ID (usually SMSC), and the ISMSC user password (set during the ISMSC
installation). After logging in, proceed with the desired ISMSC commands
described in Paragraph 4.3. through Paragraph 4.6.
4.
User Interfaces
Two interfaces are available on the ISMSC: screen and command line. Both
interfaces are accessed on system terminal. Most commands can be issued on
either interface. In this section each command is listed with the available
procedures to issue the command.
4.1.
Screen Interface
To enter the menu screen interface:
x
Type smsc menu on the command line. The SMSC Control Menu appears.
Use the following commands to operate the menu interface:
4.2.
The title of the active menu is highlighted. Use the arrow keys to move
between the options on a menu.
Select an option by pressing <Enter>. The selected option is indicated by an

arrow pointing to it.
To move to another screen, press <Ctrl>+<J> and release the keys, then
press <X>, where X is the number of the screen.
To activate the <F> keys at the bottom of the screen, press <Ctrl>+<F> and
release the keys, then press <X>, where X is the number of the key,
counting from the left.
Enter data by typing in the fields.
A process is activated after data is specified/collected in a form. To activate

a process, select the SAVE <F3> key at the bottom of the screen.
For HELP, select the <F1> key at the bottom of the screen.
Command Line Interface

The structure of a command is: smsc <command> <arguments>
where:
<command> is the command name
Page 4-2

Chapter 4
User Interface
<arguments> is a list of the command arguments.

In the command line interface, the following notation is used:
4.3.
<value> stands for a value that is described later in the document.
[ value ] stands for an optional value.
( val1 | val2 | val3 ... ) stand for alternative values.
( val1 | val2 | val3 ... ) is the same as above, but if no value is specified the
underlined option (in this case val2) is used as a default.
value* stands for zero or more specifications of value.
value stands for one or more specifications of value.
ISMSC Operation Commands

Most of the SMSC administration commands are issued by a control request using
the following syntax: smsc control <command> <arguments> where <command>
is described in Paragraph 4.3.1. through Paragraph 4.3.4.
4.3.1.
Start Command
The start command can be used to activate the SFE of both the active and standby
systems, or only the current system where the command is specified. The default
operation is on both the active and standby systems. The display the current host
status option informs the user if the current host status is active or standby.
Screen Interface
To start the SMSC:
1.
Select Operation in the SMSC Control Menu. Press <Enter>. The SMSC
Operation Menu appears.
2.
Select Start SMSC. The SMSC Control Command Menu appears

(Figure 4-1).
3.
Select an option and press <Enter>. The SMSC Confirmation Form appears.
4.
Select the Save (F3) key at the bottom of the screen.
Page 4-3
Chapter 4
User Interface

Figure 4-1: ISMSC Control Command Menu Screen

To start the SMSC on the active system only:
x
Enter smsc control start [-this] .
To issue the command for both the active and standby systems and an additional
EI(s):
4.3.2.
1.
Enter smsc control start.
2.
Enter smsc control start <EI>.
Stop Command
The command may be specified either for the active and standby systems, or only
the current system where the command is specified.(See Paragraph 4.3.1.).
Screen Interface
To stop the SMSC and other EIs:
1.
Operation Menu appears (Figure 4-1).
2.
Select Stop SMSC. The SMSC Control Command Menu appears.
3.
Select ISMSC and press <Enter>. The SMSC Confirmation Form appears.
4.
Select the Save (F3) key at the bottom of the screen.
5.
Repeat step 1 through step 4 for the EI(s)

To stop the SMSC on the active system only:
x
Page 4-4
Enter smsc control stop [-this] .


Chapter 4
User Interface
To issue the command for both the active and standby systems and additional EIs:
4.3.3.
1.
Enter smsc control stop.
2.
Enter smsc control stop <EI>.
Check
This option determines whether the SFE processes are running. The command
may be specified either for the active and standby systems, or only the current
system where the command is specified.(See Paragraph 4.3.1.). The output is a
listing of the SFE processes.
Screen Interface
To check if the SFE processes are running:
1.
2.
Select Check SMSC. The SMSC Control Command Menu appears.
3.
Select an option and press <Enter>. The SMSC Output Messages appears,
indicating if the processes are running (Figure 4-2).
Figure 4-2: ISMSC Check Screen

To check the SMSC on the active system only:
x
Enter smsc control check [-this] .
To issue the command for both the active and standby systems:
x
Enter smsc control check.
Page 4-5
Chapter 4
User Interface
4.3.4.

Send Message Command

Short messages can be sent via the ISMSC to the SMEs. They can be traced
according to the following levels:
x
level = 0
level t 20 Reception of SM, and final state
level t 50 Every state change
level t 70 Retries information
level t 100 Updates to DB and sending of notifications
No trace
Each trace levels monitors the data of the levels below it, also.
Screen Interface
To send short messages via the ISMSC to SMEs:
1.
2.
Select Send Message. The SMSC Send Message Form appears

(Figure 4-3).
3.
In the Subscriber field, type the Subscriber Number.
4.
In the Replace field, type on or off. This specifies whether this message
replaces a previous message sent by the operator to this subscriber.
5.
In the trace field, type the level of trace, as defined above.
6.
Press <SAVE> to send the message.
Figure 4-3: ISMSC Send Message Screen

Page 4-6

Chapter 4
User Interface
To send short messages via the ISMSC to SMEs, enter the following:
smsc send_sm
target <Subscriber>
text <text>
[ trace level]
[ replace (on | off) ]
where:
4.4.
target <Subscriber>
is the Subscriber Number.
text <text>
is the short message text.
trace level
determines the level of details of the trace as defined above.
replace
specifies whether this message replaces a previous message sent to

this subscriber.
Maintenance Commands
Maintenance commands for the ISMSC consist of debugging and tracing.
4.4.1.
Debug Command
Screen Interface
The debug command starts/stops the ISMSC general debug printouts. Refer to
Chapter 6, Paragraph 4.2.2. for further explanation of debugging.
The debug command starts/stops the ISMSC general debug printouts. Refer to
Chapter 6, Paragraph 4.2.2. for further explanation of debugging.
4.4.2.
Message Trace Command

The message trace command starts/stops ISMSC message trace for a specific
subscribers messages. Refer to Chapter 6, Paragraph 4.5.2. for further
explanation of message trace.
4.5.
Administration Commands
The administration commands are presented in Paragraph 4.5.1. through
Paragraph 4.6.
Page 4-7
Chapter 4
User Interface
4.5.1.

View Status Command

Screen Interface
To view the current status of the SMSC:
1.
Select Administration in the SMSC Control Menu. Press <Enter>. The

SMSC Administration Menu appears.
2.
Select View Status. The SMSC View Status Form appears (Figure 4-4).
3.
Select a component, sfe, map or all, and select the Save (F3) key at the
bottom of the screen.
Figure 4-4: ISMSC View Status Screen

To view the current status of the SMSC:
x
Enter smsc control status ( all | sfe | map-ei ).
Refer to Chapter 6, Paragraph 4.4. for further explanation of the view status
command.
4.5.2.
Message Retry Command

This command activates an immediate retry of delivery of messages to the
specified subscriber. This attempted retry in effect replaces the next retry the
system would have attempted. If it is not successful, the system defined retries
will continue to be performed.
Screen Interface
To retry a message delivery:
1.
Page 4-8


Chapter 4
User Interface
2.
Select Retry Message. The SMSC Retry Message Form appears

(Figure 4-5).
3.
Enter the Subscriber Number in the Subscriber field, and select the Save
(F3) key at the bottom of the screen.
Figure 4-5: ISMSC Message Retry Screen

To retry a message delivery:
x
4.5.3.
Enter smsc control retry -target <Subscriber number>.
Browse Log Files

Refer to Chapter 6, Paragraph 4.5.4.
4.5.4.
Distribute Configuration Files

This command updates the configuration files in all additional CEs in the system.
It is used after changes have been made in the configuration files.
Screen Interface
To distribute configuration files:
1.

2.
Select Distribute Config Files. Press <Enter>. The SMSC Confirmation

Form appears (Figure 4-6).
3.
Select <F3> to confirm, or <F6> to cancel.
Page 4-9
Chapter 4
User Interface

Figure 4-6: ISMSC Distribute Configuration File Screen

To copy the configuration file:
x
Enter smsc distrib_config.
To specify a file to be copied:

x
4.6.
Enter smsc_distrib_config <file name>.
Host Status
This function displays the status of the current SFE host, either active or standby.
Screen Interface
To view the host status:
x
Page 4-10
Select Host Status in the SMSC Control Menu. Press <Enter>. The host
status is displayed.

5.
Chapter 4
User Interface
Billing Files
The billing files are accumulated in the ISMSC directory named: /site/trace. The
file names are of the form bills.YYYYMMDD, where: YYYYMMDD denotes the
date in which the file was created. A billing file is created once a day, at a
predefined (configurable) hour. At this time, the previous file is closed, and is
ready for FTP.
Due to their inherent sensitivity, the billing files are not deleted directly by the
ISMSC. It is assumed that an external process is responsible for that task,
according to the operators policy. One such policy could be to FTP the last
cumulative file of each days events, on a daily basis, keep the last 3 days history
on the ISMSC as backup, and delete any older files. Typically, file deletion is
done by the billing center as part of the daily FTP procedure. Alternatively, an
external process can be implemented on the ISMSC platform to periodically delete
older files regardless of the FTP procedure.
The ISMSC has enough free disk space to accommodate at least 7 days of billing
history (i.e. 7 file generations) even under the worst case scenario of operation at
maximum capacity and generating additional trace records and statistical data. For
less loaded systems or in cases where tracing and statistical data are not relevant,
this time period can be longer.
In the case of an ISMSC redundant system, it is assumed that the FTP procedure is
capable of FTPing billing files from both ISMSC active and stand-by platforms,
even on the same day. The latter situation can occur in case of a switch-over from
the active to the stand-by (redundant) platform due to a failure. Since each
platform accumulates its relevant billing records for the time of its operation, this
may result in two separate billing files, one on each platform on the same day.
One file would contain records until the switch-over moment and the other would
contain records from that moment onwards.
5.1.
Record Fields Format

The fields in a billing record are of the format:
<message type>\t<destination number>\t<originator number>\t<entry
date>\t<final state>\t<final state date>\t <number of retries>\t<input source>\t\n
where the format of the fields is presented in Table 4-1. The field separator is the
TAB character (hex09). It is denoted in the examples below by the \t sign. An
end of line is denoted by a carriage-return (hex 0d) and line-feed (hex 0a). It is
shown in the examples below by the \n sign.
A typical billing record is:
M\t12345\t67890\t19990415141312\tD\t19990415152732\t3\tTRM.1:1\n
Detailed examples describing different message scenarios are provided in
Paragraph 5.2.
Page 4-11
Chapter 4
User Interface

Table 4-1: Fields in the Billing Record Files

Field
Values
Message type
MMessage
NNotification (receipt)
TTransaction
Destination
Up to 15 numeric characters
Mobile Originator
(subscriber number,
otherwise N/A)
Entry date
YYYYMMDDHHMMSS
Final state
DDelivered
N/A if not available
UUndeliverable
EExpired
CCancelled
Final state date
YYYYMMDDHHMMSS
Number of retries
Input source
Up to 15 Alphanumeric characters
The information provided in the various fields is presented as follows:

Message Type
This field provides a simple indication of the different message types, as follows:
M (Message)
Regular messages assigned to a terminal handset (SMS-MT). This

includes messages originated by any external application, such as
Voicemail Notification, Email, Web, Information Services, etc. as
well as from another handset (SMS-MO to MT).
N (Notification)
Message notification (receipt) sent back to the originating user when

his/her previously sent message reaches its final state. This type of
message is generated internally by the ISMSC only in response to MO
message to another user (handset to handset message) and in cases
when the original user requested such notification.
T (Transaction)
Message transaction from a handset to an external application, such as

SMS to Email, SMS to Fax etc. This type of message is applicable
only for MO messages to an external interface (SMS-MO to EI), not
to another handset.
Page 4-12

Chapter 4
User Interface
Destination
This field specifies the MSISDN number of the message destination, as follows:
x
For messages designated to a user handset (SMS-MT)the full

international MSISDN number in standard international representation,
always starts directly with the country code, followed by the area code and
local number. It should be noted that this format always stays the same
whether the originating user omitted the country code or added leading
zeros and/or the + sign for the destination number.
For messages designated to an external interface (SMS-MO to EI)the

MSISDN service number for this application as defined and published for
users by the operator. Typically, this is a short code number, such as *123,
which is easy to remember and use.
The destination number can be up to 15 numeric characters. Currently, this field

always contains a number (i.e. it is never left blank or indicated by N/A), but this
situation may change in future releases.
Originator
This field specifies the MSISDN number of the message originator, as follows:
x
For messages originating from a cellular handset (SMS-MO)the full

international MSISDN number of the message originator, appears in the
same standard international representation as in the case of the destination
number above. The number always starts directly with the country code,
followed by the area code and local number.
For messages originating in an external application or interface (SMS from

EI)depends on whether the originating EI specified the Originator
Address field with the deposited message or not. If the field is specified,
then the specified number is indicated (in the same international
representation as mentioned above). If the field is not specified, then N/A
appears in the field.
It should be noted that ISMSC interfacing protocols, SMPP and NIP, contain an
optional Originating Address field. Currently, most of ISMSC provided
applications, such as ShortEmail, IPOS or Web Access, do not specify an
originating address, resulting in an N/A indication on the CDR.
Entry Date
Specifies the date and time when the message was received by ISMSC in the
format YYYYMMDDHHMMSS.
Final State
This field specifies the message final state, as follows:
D (Delivered)
The message was successfully delivered to its destination user or

application.
Page 4-13
Chapter 4
User Interface

U (Undeliverable)
The ISMSC detected a permanent error which prevented the

message from being delivered to its destination, such as unknown
destination number, non provisioned SMS teleservice, an illegal
number, etc. Such permanent errors are typically detected during
the first delivery attempt of a message, thus resulting in its
immediate termination in the ISMSC database.
E (Expired)
The message reached its expiration time in the ISMSC database

before it could be successfully delivered to its destination. ISMSC
expiration time is a configurable parameter with a default value of
5 days.
C (Cancelled)
The message was canceled by its originator while in the ISMSC

database, before it was delivered to its destination.
Final State Date

Specifies the date and time when the message reached its final state in the ISMSC
database in the format YYYYMMDDHHMMSS.
NOTE:
It is possible to calculate the time difference between the Entry Date

and Final State Date to indicate how long the message was stored in
the ISMSC database before being delivered to its destination.
Number of Retries
Specifies the number of message delivery attempts until the message reached its
final state: successfully delivered, undeliverable, expired or cancelled by the
originator. This information can be very useful for statistical analysis and
troubleshooting purposes.
Input Source
This field specifies the input source of the message, according to its External
Interface name. Every connection type to the ISMSC, such as Web, Email,
TRILOGUE INfinity TRM, the cellular network etc., is via its own External
Interface. This field indicates the External Interface from which the message was
received by the ISMSC, thus identifying the message source or service
application.
Table 4-2 specifies the available ISMSC Source External Interfaces along with
their respective application services. Target (destination) External Interfaces are
not relevant to the billing records.
Table 4-2: ISMSC Source External Interfaces
EI Name
Related Application (Service)
TRM
From TRM: VMN, Canned messages, UM-based messages
MAPMO
MO messages from cellular handsets
Page 4-14

Chapter 4
User Interface
EI Name
Related Application (Service)
OPER: TEXTAPI
ISMSC Paging Operator Station (IPOS)
EMAIL
ISMSC ShortEmail service
WEB:TEXTAPI
ISMSC Web Access service
SMPP
External services connected through SMPP interface
TAP
External services connected through TAP interface
IVR
In case an external IVR (not TRILOGUE IVR) is connected
BROADCAST
ISMSC SMS-From-File service
USER-EI
From ISMSC Console, sent by the System Administrator
EMAIL and WEB:TEXTAPI refer to the ISMSC embedded Email and Web Access
services, not to the Unified Messaging based Email and Web services. The UM
originated messages which appear in ISMSC billing records are sent from the
TRM.
External applications connected by the operator, which are not part of ISMSC
embedded services, such as Information Services, Over the Air platforms, and
Vehicle Dispatch services, appear as SMPP or TAP depending on their interfacing
protocol. It is possible to modify these default names to other logical names, like
Information, OTA, etc. This can be done only by Comverse trained personnel,
however, not by the operator himself.
IVR refers to an external IVR connection, not to the TRILOGUE INfinity built-in
IVR application, which is denoted in ISMSC billing records as TRM.
USER-EI refers to test messages sent by the ISMSC System Administrator from
the Console or OMAP application. No other messages denote this external
interface.
CAUTION: The full syntax of the External Interface name, as appears in the
billing records, also includes its Group and Instance connection, in
the following format: EIName.Group:Instanc, for example: TRM.1:1
or EMAIL.2:4. Any billing system application that processes the
billing records should refer to the EI name only and neglect the rest of
this field.
5.2.
Billing Record Examples

This section provides examples of various billing records in different possible
scenarioshandset to handset, message notification, application to handset, and
handset to application. For each scenario it also indicates its identifying fields,
meaning how to recognize that type of message scenario from the others.
Page 4-15
Chapter 4
User Interface

The TAB character (hex09) is denoted in the examples below by the \t sign.
The end of line identifier, comprising of carriage-return (hex 0d) and line-feed
(hex 0a) characters, is denoted by the \n sign.
5.2.1.
Handset to Handset (SMS-MO to MT)

Table 4-3 references regular messages from user to user on the cellular network:
Table 4-3: Handset to Handset Billing Records
Field
Value
Message type
M (Message)
Destination
MSISDN number of destination handset (up to 15 characters)
Originator
MSISDN number of originating handset (up to 15 characters)
Entry date
Date & time of message entry to ISMSC: YYYYMMDDHHMMSS
Final state
Message final state, could be any of: D, U, E, C
Final state date
Date & time of message final state: YYYYMMDDHHMMSS
Number of retries
Number of delivery attempts to destination (up to 5 digits)
Input source
MAPMO
Identifying fields:
Message Type: M
Input Source: MAPMO
Example:
M\t5161234567\t5167954528\t19990420101312\tD\t19990420121315\t2\tMAPMO.1:1\n
5.2.2.
Notification (Receipt) to Originating Handset

Table 4-4 references notification to the handset. This type of message is sent back
to a cellular handset by the ISMSC as a notification status of its previously sent
MO message.
Table 4-4: Notification (Receipt) to Originating Handset Billing Records
Field
Value
Message type
N (Notification)
Destination
MSISDN of the notification destination handset, i.e. the originator

number of the MO message triggering this notification
Page 4-16

Chapter 4
User Interface
Field
Value
Originator
MSISDN of the notification originator handset, i.e. the destination

number of the MO message triggering this notification
Entry date
Date & time of notification creation in ISMSC, i.e. date & time when
the MO message triggering this notification reached final state
Final state
Notification final state (not the original MO), could be any of: D, E
(U or C also possible in theory but not in practice)
Final state date
Date & time of notification final state (not the original MO)
Number of retries
Number of the notification delivery attempts (not the original MO)
Input source
MAPMO
NOTE:
The Final State, Final State Date and Number of Retries values refer
to the information relayed by the notification message, not to the
original MO message that triggered the notification.
Identifying field:
Message Type: N
Example:
A notification message for the MO message in the example above will look like
this:
N\t5167954528\t5161234567\ t19990420121316\tD\ t19990420121319\t0\tMAPMO.1:1\n
5.2.3.
Application to Handset (SMS-MT from EI)

Table 4-5 refers to service oriented messages from ISMSC service applications
Voicemail, ShortEmail, Web Access, IPOS, etc.to the cellular users.
Table 4-5: Application to Handset Billing Records
Field
Value
Message type
M (Message)
Destination
MSISDN number of destination handset (up to 15 characters)
Originator
MSISDN number of the Originator Address field, if specified by the

originating EI with the deposited message
N/Aif no Originator Address field was specified
Entry date
Page 4-17
Chapter 4
User Interface

Field
Value
Final state
Final state date
Number of retries
Number of delivery attempts to destination, up to 5 digits
Input source
External Interface name, e.g. TRM, EMAIL, SMPP. Could be any of

the list in Table 4-2.
Identifying fields:
Message Type: M
Input Source: Identifies the specific application (service) that initiated the
message.
Example:
Successful message:
M\t5161234567\tN/A\t19990420101312\tD\t19990420121315\t2\tSMPP.1:1\n
Failed message:
M\t5161234567\tN/A\t19990420101312\tE\t19990425101312\t72\tSMPP.1:1\n
5.2.4.
Handset to Application (SMS-MO to EI)

Table 4-6 refers to messages from a cellular user to an external application, such
as SMS to Email, SMS to Fax, MO based request for information, etc.
Table 4-6: Handset to Application Billing Records
Field
Value
Message type
T (Transaction)
Destination
MSISDN service number denoting the designated application, as

defined and published to users by the operator (up to 15 characters)
Originator
MSISDN number of originating handset (up to 15 characters)
Entry date
Final state
Final state date
Number of retries
Number of delivery attempts to destination, up to 5 digits
Input source
MAPMO
Page 4-18

Chapter 4
User Interface
Identifying fields:
Message Type: T
Destination: Identifies the specific application (service) that is connected with the
message.
Example:
T\t123\t5167954528\t19990420101312\tD\t19990420101313\t0\tMAPMO.1:1\n
Page 4-19
Chapter 5
Provisioning

Chapter 5
Provisioning
Table of Contents
1. Overview to the Provisioning Subsystem ............................................................................5-1
2. Resource Parameters .............................................................................................................5-1
3. Batch and Interactive Modes .................................................................................................5-3
3.1. Batch Command ................................................................................................................5-4
3.2. Interactive Commands.......................................................................................................5-4
3.3. Return Messages...............................................................................................................5-7
Page 5-i

1.
Chapter 5
Provisioning
Overview to the Provisioning Subsystem

The Provisioning Subsystem (PS) enables the definition and limitation of
subscriber profiles with respect to the various EIs in a system. Typical profiles are
defined by a Class of Service (COS), which defines the permitted and prohibited
EIs. Individual subscribers are also provisioned by specifying the permitted and
prohibited EIs for that specific subscriber. Subscribers may also be defined
outside the PS.
An individual subscribers COS profile may be overwritten by the addition or
prohibition of EIs.
All provisioning is defined by provisioning rules. The administration and
verification of provisioning rules is performed by the PS. The parameters defining
the PS are listed in Paragraph 2. Commands are executed either in batch or
interactive mode (Paragraph 3.).
A COS may be modified while subscribers are assigned to it, and the
modifications are effective immediately. A COS may not be deleted while
subscribers are assigned to it.
2.
Resource Parameters
The
following
parameters,
located
in
the
directory
/home/smsc/sfe.2.3/config/provision.config, define the PS. A value change is
effective from the next run of the SFE.
The PS parameters are:
ei.<einame>.provisioned
Description:
Determines which target/source cellular EIs are valid. This parameter is only
relevant for MAP, MAP-MO, IS41, IS41-MO
Units:
N/A
Legal values:
No, Yes
Default value:
No
Example:
N/A
See Also:
N/A
psactivate
Description:
Determines if the SFE uses the PS to determine which SMs are permitted for
delivery. When set to True, only permitted SMs as defined by the PS are allowed.
When set to false, the PS rules are bypassed and all SMs are allowed.
Units:
N/A
Page 5-1
Chapter 5
Provisioning

Legal values:
True, False
Default value:
False
Example:
N/A
See Also:
N/A
psdefault_cos_name
Description:
This parameter defines the name of a COS to be consulted in case the subscriber
is not defined in the PS. In case this COS does not exist,
psallow_if_user_does_not_exist is used.
Units:
N/A
Legal values:
printable set of characters
Default value:
psdefault_cos
Example:
N/A
See Also:
N/A
psallow_if_user_does_not_exist
Description:
This parameter determines whether short messages are allowed for all users not
yet defined in the PS. This resource is effective only if a default COS does not
exist.
Units:
N/A
Legal values:
0 (false), 1 (true)
Default value:
Example:
N/A
See Also:
N/A
psallow_if_sei_not_defined
Page 5-2
Description:
Determines if a subscriber is allowed to receive messages via an EI that is

not defined explicitly for the subscriber.
Units:
N/A
Legal values:
0 (false), 1 (true)
Default value:
Example:
N/A

See Also:
Chapter 5
Provisioning
N/A
psallow_if_tei_not_defined
Description:
Determines if a subscriber is allowed to send messages via an EI that is

not defined explicitly for the subscriber.
Units:
N/A
Legal values:
0 (false), 1 (true)
Default value:
Example:
N/A
See Also:
N/A
psbatch_chunk
Description:
This parameter defines the number of batch commands

(Paragraph 3.) to process during a single cycle of the SFE.
The smaller the value, the longer batch processing takes. The
larger the value, the slower the SFE performs its other
activities during the batch processing.
Units:
N/A
Legal values:
numeric values from 1 to 2**32-1
Default value:
100
Example:
N/A
See Also:
N/A
To modify the resource parameters:

x
Modify the file /home/smsc/site/config/sfe.config by adding the relevant

line at the end of the file in the format:
<resource parameter> = <resource value>
For example:
psactivate = 1
3.
Batch and Interactive Modes

Once connection is established, the user can make either batch or interactive
commands.
Page 5-3
Chapter 5
Provisioning
3.1.

Batch Mode: This mode is invoked by issuing the batch command, namely,
specifying a text file name containing a list of provision commands, each
one in a separate line. A return message confirms that the file is found and
that the batch processing is about to begin. The processing of these
commands is performed in chunks (controlled by the resource
psbatch_chunk), and the output is written into a message file bearing the
original file name and the suffix .msg. The last line in the output file
informs the user that the batch processing is over. No two batch processes
are allowed to run concurrently. The second batch request is rejected by the
PS.
Interactive Mode: This mode is invoked by issuing all other commands. The
command is executed immediately, and its output is sent back to the user.
Several interactive commands can be made concurrently. In case a batch
process is running at the same time, there is no guarantee which of the
conflicting commands be issued first.
Batch Command
Batch commands are executed using the following format:
x
Process batch file

Command format: P o <file_name>
NOTE:
The symbol o indicates pressing once on the <Tab> key.
Use: This command initiates processing of the file <file_name>.dat in the

directory: ~smsc/site/data/provision/batch/. The output file is named
<file_name>.msg and is placed in the same directory.
Example: P batch001
3.2.
Interactive Commands
To activate the interactive mode, enter the command:
smsc connect <sfe_hostname> <ps_port_number>
The separator between the commands tokens is a single <Tab>, represented by an

o in the text. Each command is terminated by a NEWLINE. Any unexpected
character results in a syntax error.
The following commands are used in interactive mode:
x
To insert a new class of service

Command format: CIo<name>o[<EI-type>=<y/n>]
Use: The name is a unique identifier of the class of service.
Examples:
CIoSuperoTRM=yoWEB=y
Page 5-4

Chapter 5
Provisioning
CIoStandardoTRM=y
x
To delete an existing class of service

Command format: CDo<name>
Use: A class of service may be deleted only if no existing subscriber is
using it.
Example: CDoSuper
To modify an existing class of service

Command format: CMo<name>o[<EI-type>=<y/n>]
Use: A class of service and all its subscribers are modified on the fly.
Subsequent queries on the relevant subscribers use the new provision rule.
Example: CMoStandardoWEB=noIVR=y
To find an existing class of service

Command format: CFo<name>
Use: Only the class of service name is needed for retrieving the COS record.
The output of this command is in a format similar to the preceding
commands.
Example: CFoStandard
Output:
COS Find: Standard TRM=y WEB=n IVR=y
To insert a new subscriber

Command format:
Io<name>o[cos=<cos name>]o[blocked=<y/n>]o[<EI-type>=<y/n>]
Use: The name uniquely identifies the subscriber. All the parameters except
for it are optional. The parameter cos specifies the subscribers class of
service. Class of service is useful for assigning a specific provision rule for
a group of subscribers. The class of service to be used must exist at the time
of the subscriber insertion. The parameter blocked indicates whether the
subscriber is currently blocked. If true (i.e. y) the provision rule assigned
for the subscriber is not consulted and the short message is not sent. The
default value for this parameter is n (i.e., not blocked). If used, the class of
service and the blocked indication should precede any other parameter. The
provision rule itself may consist of several blocks of EI-Types and values.
EI-Types currently available are: TRM, MAP, USER-EI, MAPMO, IS41,
EMAIL, TAP, WEB, IVR.
Examples:
IoSmithocos=RegularoTRM=yoEMAIL=noIS41=y
Page 5-5
Chapter 5
Provisioning

This command defines the subscriber Smith with the Regular COS. In
addition the TRM and IS41 EIs may send him messages, and the Email EI
may not send messages.
IoGreenocos=SuperoTAP=y
This command defines the subscriber Green with the Super COS. In
addition the TAP EI may send him messages.
x
To delete an existing subscriber

Command format: Do<name>
Use: Only the subscriber name is needed for deleting its provisioning
record.
Example: DoSmith
To modify an existing subscriber

Command format:
Mo<name>o[blocked=<y/n>]o[<EI-type>=<y/n>]
Use: Subscribers blocked indication and provisioning rules are modified on
the fly. The new data is in effect once the command is processed
successfully. Attributes not mentioned remain intact. The subscribers COS
may not be modified.
Example: MoSmithoTRM=noTAP=y
To find an existing subscriber

Command format: Fo<name>
Use: Only the subscriber name is needed for retrieving the provision record.
The output of this command is in a format similar to the preceding insert
and modify commands. A TAB is used as the token separator.
Example: FoSmith
Output:
Find: Smith cos=Regular TRM=n TAP=y EMAIL=n IS41=y
To reset an existing subscriber

Command format: Ro<name>
Use: The subscribers profile definition is reset to the COS he was assigned
upon initial definition. Only a subscriber who is assigned a COS may be
reset.
Example: RoSmith
Page 5-6

3.3.
Chapter 5
Provisioning
Return Messages
All messages are prefixed by invoking the command name. The responses to a
valid find command are presented in Paragraph 3.2. under the command names F
and CF. Syntax errors and internal errors are accompanied by a detailed message
in the error log of the SFE.
The following messages are returned in response to the interactive commands:
x
OK
Name does not exist
Name already exists
Provision database is full
COS not defined for given subscriber
COS is used by active subscribers and can't be deleted
COS cannot be redefined for given subscriber
File not found
Another batch request is in process. Request ignored
Syntax error
Internal problems
Page 5-7
Chapter 6
Maintenance

Chapter 6
Maintenance
Table of Contents
1. Overview ..................................................................................................................................6-1
2. Backup and Restore Procedures ..........................................................................................6-1
2.1. Full Backup ........................................................................................................................6-1
2.2. Full Restore........................................................................................................................6-2
3. System Monitoring and Alarms .............................................................................................6-3
4. Diagnostics, Troubleshooting, and Debugging...................................................................6-8
4.1. General ..............................................................................................................................6-9
4.2. Monitoring Commands.......................................................................................................6-9
4.2.1. Check Current Host Status .........................................................................................6-9
4.2.2. Debugging.................................................................................................................6-10
4.2.3. Distribute Config Files...............................................................................................6-12
4.3. Monitoring Files................................................................................................................6-12
4.4. View Status ......................................................................................................................6-13
4.5. Tracing Short Messages ..................................................................................................6-14
4.5.1. Message Trace Example ..........................................................................................6-15
4.5.2. Trace Message .........................................................................................................6-16
4.5.3. Trace All Messages ..................................................................................................6-17
4.5.4. Browsing the Trace Files ..........................................................................................6-18
4.6. Log Files ..........................................................................................................................6-19
4.7. Statistics Files ..................................................................................................................6-19
4.7.1. Defining Statistics Files.............................................................................................6-20
4.7.2. Counters ...................................................................................................................6-20
4.7.3. Reading Statistics Files.............................................................................................6-23
5. Control Status Output ..........................................................................................................6-27
5.1. General Information (GNSTAT Block) .............................................................................6-28
5.2. Connections to External Interfaces (SEIname and TEIname Blocks) .............................6-28
5.3. Performance Data............................................................................................................6-28
5.4. Source EIs .......................................................................................................................6-29
5.5. Target EIs ........................................................................................................................6-29
5.6. Sample of Control Status Output .....................................................................................6-31
5.7. Online Query Tool ............................................................................................................6-41
Page 6-i
Chapter 6
Maintenance

5.7.1. Short Form Report ................................................................................................... 6-41

5.7.2. Long Form Report .................................................................................................... 6-42
5.7.3. Debug Report ........................................................................................................... 6-43
5.7.4. Query Format ........................................................................................................... 6-43
5.7.5. Examples of Database Queries ............................................................................... 6-44
6. Assembly and Disassembly of ISMSC Modules................................................................ 6-50
6.1. General Instructions for the ISMSC Boards .................................................................... 6-51
6.2. Specific Instructions for the ISMSC CPU Board ............................................................. 6-52
6.3. ISMSC Hard Disk Drive................................................................................................... 6-53
6.4. ISMSC Floppy Disk Drive................................................................................................ 6-53
6.5. ISMSC DAT Drive ........................................................................................................... 6-54
6.6. ISMSC Power Supply ...................................................................................................... 6-55
6.7. ISMSC Fan Module ......................................................................................................... 6-56
7. Maintenance of the ISMSC Platform................................................................................... 6-56
List of Figures
6-1
IAP Alarm 9200, No Network Communication with ISMSC ............................................... 6-5
6-2
IAP Alarm 9700, ISMSC Link to MAP is OOS.................................................................... 6-6
6-3
IAP Alarm 9920, ISMSC Successful Transactions Below.................................................. 6-7
6-4
ISMSC Host Status Screen.............................................................................................. 6-10
6-5
ISMSC Start/Stop Debug Screen..................................................................................... 6-11
6-6
ISMSC Distribute Configuration File Screen .................................................................... 6-12
6-7
ISMSC View Status Screen.............................................................................................. 6-13
6-8
ISMSC Message Trace Log Screen................................................................................. 6-14
6-9
ISMSC Trace Message Screen........................................................................................ 6-17
6-10 ISMSC Trace All Messages Screen................................................................................. 6-18

6-11 ISMSC Browse Trace File Form ...................................................................................... 6-19
6-12 ISMSCExploded View................................................................................................... 6-50
Page 6-ii

Chapter 6
Maintenance
6-13 ISMSCCPU Board Jumpers..........................................................................................6-52
List of Tables
6-1
Statistics Counters............................................................................................................6-21
6-2
Contents of Raw Statistics Report ....................................................................................6-24
6-3
DAT Drive Switch Configuration .......................................................................................6-54
6-4
DAT Drive Jumper Configuration......................................................................................6-55
Page 6-iii

1.
Chapter 6
Maintenance
Overview
This chapter covers the following maintenance procedures: backup and restore
procedures, monitoring and alarm resolution, troubleshooting procedures,
assembly and disassembly, and monitoring of LEDs.
2.
Backup and Restore Procedures

Full backup (Paragraph 2.1.)
Full restore (Paragraph 2.2.)
2.1.
Full Backup
Full backup of a 4.5 GB disk takes approximately 45 minutes.
To backup the ISMSC:
1.
Verify that the source machine is turned off.
2.
Turn on the computer.
3.
When the SCO logo appears, press <spacebar> to enter the debug mode.
4.
Enter the command INITSTATE=s.
5.
At the boot prompt enter the command go.
6.
When prompted, enter the root password.
7.
Insert the DAT cassette (size must be 120m) labeled Emergency_rec tape.
8.
Enter the command /sbin/emergency_rec ctape1.
9.
Insert the diskette labeled Emergency Recovery Diskette #1/2 into the
floppy drive of the target machine.
10.
Enter the command /sbin/emergency_disk diskette1.
11.
Wait until the system prompts for the second diskette.
12.
Insert the second diskette labeled Emergency Recovery Diskette #2/2.
13.
Press <Enter>.
14.
Remove the diskette.
15.
To reboot machine enter init 6.
Page 6-1
Chapter 6
Maintenance
2.2.

Full Restore
Full restore of a 4.5 GB disk takes approximately one hour.
NOTE:
Perform this procedure only to repair the system.
To perform restore on the ismsc , do format to the new destination hard

disk , by turn on the power choose :control A then ,choose scsi utils and
format disk , when the format is finished you ready to begin the restore.
To perform restore on the ISMSC:
1.
Format the destination hard disk:

a.
Select control A.
b.
Select scsi utils.
c.
Format the disk.
2.
Turn off the power.
3.
Insert diskette labeled Emergency Recovery Diskette #1/2 into the floppy
drive of the target machine.
4.
Press <Enter>.
5.
Power on the system and wait until you will get the following message:
Insert the second emergency recovery floppy.
6.
Insert the second diskette labeled Emergency Recovery Diskette #2/2 into
the floppy drive.
7.
Press <Enter>.
8.
Either of the following two messages can appear:

The hard disk is sane.
Press ENTER to continue.
or
The hard disk is NOT sane.
Press ENTER to continue.
9.
In either case, a menu is displayed. Press <R> to select Restore Disk(s).
10.
Press <Enter>.
11.
A prompt to insert the tape labeled Emergency_rec tape appears.
12.
Insert the installation tape and press <Enter>.
13.
After approximately 30-40 minutes, the following dialog box should appear:
Disk(s) is(are) successfully restored.
14.
Page 6-2
Press <Enter> to continue.

Chapter 6
Maintenance
15.
The emergency recovery menu will appear. Press <B> or use the directional
arrows to select Reboot.
16.
Press <Enter>. The following message appears:

MAKE SURE THE BOOT DRIVE (DISKETTE OR CD-ROM) IS EMPTY.
3.
17.
Verify that the diskette has been removed.
18.
Press <Enter>. The system shuts down and reboots.
System Monitoring and Alarms

The system and functionality alarms are listed below. Alarm resolution for Alarms
9200, 9700 and 9920 are presented in Figure 6-1 through Figure 6-3.
ISMSC System Alarms:
9000: ISMSC Out of service
9100: ISMSC Unit manually out-of-service
9200: No network communication with ISMSC
Redundant ISMSC System Alarms:

9300: No Redundant ISMSC
9400: Two Active ISMSC Units
Functionality Alarms:
9600: ISMSC link to TRM is OOS (Out of Service)
9700: ISMSC link to MAP is OOS (Out of Service)
9800: ISMSC database utilization has reached:
9810-9817: ISMSC file system 1-8 utilization has

reached:
9820-9827: Standby ISMSC File System 1-8

utilization has reached:
t 70% (reset 60%)
minor
t 80% (reset 71%)
major
t 95% (reset 81%)
critical
t 70% (reset 60%)
minor
t 80% (reset 71%)
major
t 95% (reset 81%)
critical
t 70% (reset 60%)
minor
t 80% (reset 71%)
major
t 95% (reset 81%)
critical
Page 6-3
Chapter 6
Maintenance
9850: ISMSC File System Out Of Service
9870: Standby ISMSC File System Out Of Service
9900: ISMSC message rate has reached:
9920: ISMSC successful transactions below:
Page 6-4

t 1 file systems
minor
t 2 file systems
major
t 3 file systems
critical
t 1 file systems
minor
t 2 file systems
major
t 3 file systems
critical
t 95% (reset 85%)
minor
t 100% (reset 96%)
major
t 105% (reset101%)
critical
d50%
minor
d20%
major
d10%
critical

Chapter 6
Maintenance
Figure 6-1: IAP Alarm 9200, No Network Communication with ISMSC
Page 6-5
Chapter 6
Maintenance

AP MESSAGE 9700:
ISMSC LINK TO MAP
OUT OF SERVICE
IS CE OF MAP
RUNNING ?
NO
CONTACT
TIER 3
YES
IS CE OF OMNI
RUNNING ?
NO
TYPE mml
RESPONDS
error ?
YES
NO
YES
PING SFE TO MAP

USING THE COMMAND
PING SMSC1
CONTACT
TIER 3
NO
COMMUNICATION
ON MEDIUM
NON-REDUNDANT
SYSTEM ISSUE
THE COMMANDS
stop sfe
reboot
ON LARGE
NON-REDUNDANT
REBOOT
PING TRM to sfe1

and MAP
MAP
RESPONDS ?
NO
CONTACT
TIER 3
CONTACT
TIER 3
REPORT
TIER 3
CONTACT
TIER 3
YES
CHECK
TRANSCEIVER
LEDS
LEDS NOT FUNCTIONING
REPLACE
TRANSCEIVER
STILL FAULTY
CHECK CABLES
REPLACE IF
NECESSARY
STILL FAULTY
CONTACT
TIER 3
IDG00607
Figure 6-2: IAP Alarm 9700, ISMSC Link to MAP is OOS
Page 6-6

Chapter 6
Maintenance
AP MESSAGE 9920:
ISMSC SUCCESSFUL
TRANSACTIONS
BELOW
ON MAP CE ENTER
USER OMNI
TYPE : mml
dspl - slk ;
VERIFY THAT
LINKS ARE IN NORMAL
STATE : UNINHIBITED
AND ACTIVE
NO
CONTACT
TIER 3
NO
CONTACT
TIER 3
YES
TYPE: displ-rem ssn;
VERIFY THAT
ALL POINT CODES
ARE ACCESSIBLE
YES
VERIFY WITH
SWITCH ENGINEER
THAT ALIGNMENT
IS NORMAL
YES
CONTACT
TIER 3
IDG00605
Figure 6-3: IAP Alarm 9920, ISMSC Successful Transactions Below

Two examples are provided of links: LINK/REMSSN is OK, LINK/REMSSN is
Fail/Prohibited
Example 1: LINK/REMSSN is OK
Send [DISPL-SLK;]? [Y/N]y
Sent MML command #1 to smsc1.PM, cmd[DISPL-SLK;]
starting 5 min. timer...
1
[28 Sep 1997 05:59:49]
DISPL-SLK;
Page 6-7
Chapter 6
Maintenance

--- SIGNALLING LINKS -Name Nbr LSet LSet SLC Port Speed ADPC
State
Status
LNK1
LSET0
56000 214-171-000
ACTIVE
inblraP
LNK2
LSET0
56000 214-171-000
ACTIVE
IFblraP
--- SIGNALLING LINK STATUS LEGEND --i - installed
I - not installed
n - link normal
F - link failed
b - not locally blocked
B - link locally blocked
l - local not inhibited
L - local inhibited
r - remote not inhibited
R - remote inhibited
a - SLT Alignment enabled
A - SLT Alignment disabled
p - SLT Periodic enabled
P - SLT Periodic disabled
Usage: Filename:
- to execute from a file
MML command: - series of mml command(s)
Example 2: LINK/REMSSN is Fail/Prohibited

OMNI [28 Sep 1997 05:59:49] #2:displ-remssn;
Send [DISPL-REMSSN;]? [Y/N]y
Sent MML command #2
to smsc1.PM, cmd[DISPL-REMSSN;]
starting 5 min. timer...

2
[28 Sep 1997 05:59:59]
DISPL-REMSSN;
M
COMPLETED
command accepted
Display Remote Subsystem Number:
4.
Point Code:
214-170-2
Remote SSNs[1]:
8 [0x8] A
Point Code:
214-170-4
Remote SSNs[1]:
8 [0x8] P
Diagnostics, Troubleshooting, and Debugging

Page 6-8
General (Paragraph 4.1.)
Monitoring commands (Paragraph 4.2.)
Monitoring files (Paragraph 4.3.)

4.1.
View status (Paragraph 4.4.)
Tracing Short messages (Paragraph 4.5.)
Log files (Paragraph 4.6.)
Statistics files (Paragraph 4.7.)
Chapter 6
Maintenance
General
The enabling of special loggers provides ISMSC diagnostics, troubleshooting, and
debugging:
x
Trigger logging of ISMSC activity to a log filei.e. details about short

message being handled with relevant short message data, and type of
handling (for example, incoming, being-delivered, scheduled for retry, being
redelivered, expired).
Trigger logging for a specific subscriber.
Trigger printout of ISMSC central data-structures and current state.
An internal error-logging mechanism also provides ISMSC diagnostics,

troubleshooting, and debugging.
4.2.
Monitoring Commands
4.2.1.
Check Current Host Status (Paragraph 4.2.1.)
Debugging (Paragraph 4.2.2.)
Distribute config files (Paragraph 4.2.3.)
Check Current Host Status

The status of the Current Host Status is one of the following:
x
active
standby
standby (no active SFE accessible)
Screen Interface
To check the current host status:
1.
2.
Select Check SMSC, and press <Enter>. The SMSC Control Command
Menu appears.
3.
Select Display the current host status. The current host status appears on
the bottom of the screen.
Page 6-9
Chapter 6
Maintenance

or
x
Select Host Status in the SMSC Control Menu. Press <Enter>. The current
host status appears on the bottom of the screen (Figure 6-4).
Figure 6-4: ISMSC Host Status Screen

To check the current host status:
x
Enter the command: smsc host status <host_name>

where <host_name> is the host name of the active or standby SFE.
To check the current host, specify the name as <host_name>.
4.2.2.
Debugging
The debugging option provides information on message flow. The information is
recorded in the files debug.MAP and debug.sfe, in the directory
home/smsc/site/trace.
NOTE:
Debugging is mainly used for development purposes. The information

given here enables tier-3 personnel to access information for use by
R & D personnel.
NOTE:
Disable the debugging option before online operation. When

debugging is enabled, the system slows down.
Page 6-10

Chapter 6
Maintenance
Screen Interface
To activate the debugging option:
1.
Select Maintenance in the SMSC Control Menu, and press <Enter>. The
SMSC Maintenance Menu appears.
2.
Select Debug and press <Enter>. The SMSC Debug Menu appears.
3.
Select Start/Stop Debug and press <Enter>. The SMSC Start/Stop Debug
4.
Select a SMSC Component: SFE for the main process of the SFE, map for
MAP External Interface, all for both.
5.
On the Debug option type On to start, or Off to stop the SMSC general
debug. Select the Save (F3) key at the bottom of the screen.
Figure 6-5: ISMSC Start/Stop Debug Screen

To toggle the SFE debug command:
x
Enter smsc control debug (on|off).
To toggle the MAP External Interface debug:

x
Enter smsc control debug (on-ei|off-ei) .
To toggle all debug options:

x
Enter smsc control debug (on-all|off-all) .
Page 6-11
Chapter 6
Maintenance
4.2.3.

Distribute Config Files

Screen Interface
This option updates the configuration files in all additional CEs in the system. It
is used after changes have been made in the configuration files.
To distribute configuration files:
1.

2.
Select Distribute Config Files and press <Enter>. The SMSC Confirmation
3.
Select <F3> to confirm, or <F6> to cancel, and select the Save (F3) key at
Figure 6-6: ISMSC Distribute Configuration File Screen

This command copies the configuration file to all additional CEs in the system.
To copy the configuration file:
x
Enter smsc distrib_config.
To specify a file to be copied:

x
4.3.
Enter smsc_distrib_config <file name>.
Monitoring Files
Files that are relevant for monitoring and fault isolation are:
x
Page 6-12
Trace Files are created when the Trace is enabled. Refer to Paragraph 4.5.

4.4.
Chapter 6
Maintenance
Log files such as log.SFE and log.MAP, located in the trace directory,
contain information about system errors and important events. The SFE
prints a status report once each hour.
Statistics files, located in the trace directory, contain statistics on the system
status, EIs, incoming messages, and delivery of messages. Refer to
Paragraph 4.7.1.
View Status
The view status command permits viewing the current status and statistics of the
ISMSC processes. This command displays a snapshot of the current status of the
ISMSC processes and the ISMSC activities. A sample control status printout
appears in Paragraph 5.6.
Screen Interface
To view the ISMSC status:
1.
Select Administration in the SMSC Control Menu and press <Enter>. The
SMSC Administration Menu appears (Figure 6-7).
2.
Select View Status and press <Enter>. The SMSC View Status Form
appears.
3.
Select an option ( all, sfe, map), and press <Enter>.
Figure 6-7: ISMSC View Status Screen

To view the ISMSC status, enter: smsc control status [sfe | all]
Page 6-13
Chapter 6
Maintenance
4.5.

Tracing Short Messages

This paragraph describes various options that are available for tracing short
messages. A Trace is effective from the time of activation. There is no backward
tracing. Trace files are recorded in the file msg_trace.log. located in the directory
home/smsc/site/trace.
Messages are traced as specified by the following levels. Each increase in level
provides more detailed information.
value = 0
No trace
value t 20 Reception of SM, and final state

value t 50 Every state change
value t 70 Retries information
value t 100 Updates to DB and sending of notifications
Message Trace Files appear as presented in Figure 6-8.
Figure 6-8: ISMSC Message Trace Log Screen

The message trace file contains the following format:
<date> Short Message <isn> for <subs> <action>
where:
<date>
is the date of the event in the format YYYYMMDDhhmmss
<isn>
is an internal serial number of the message in the ISMSC

database. This is a unique identifier of the message.
Page 6-14

<subs>
is the subscriber number to which this message belongs.
<action>
is the operation on this message.
Chapter 6
Maintenance
The following actions are available:
4.5.1.
Received from <ei>. A new message has been received from an <ei>, where
<ei> is: the USER-EI, indicating the message was sent manually (using
smsc send_sm); TRM, indicating that the message comes from the TRM;
or another of the defined EIs.
Alert is received from MAP.... An alert indicating a subscriber is available

was received from the network and a delivery attempt for this subscriber
will be made promptly.
Trying to deliver. The ISMSC is making a delivery attempt of this message.
State= <state>, Minor state = <minor_state>. The message is in a new state.

The possible states are:
STATE_BEING_DELIVERED. The message is currently on route to

the subscriber.
STATE_PENDING_RETRY. The message is currently waiting for

delivery at a later time.
STATE_DELIVERED. The message was delivered successfully.
STATE_UNDELIVERABLE. The message cannot be delivered due to

a permanent error (UNKNOWN SUBSCRIBER or TELESERVICE
NOT PROVISIONED).
STATE_EXPIRED. The ISMSC was not able to deliver the message

for the time defined as expiration in the configuration.
STATE_DELETED. The message was canceled (or replaced).
Scheduled a retry on <date>. Message delivery failed and a re-delivery

attempt was scheduled to <date>.
Sent notification to EI <ei>. Notification of a message final state

(DELIVERED, UNDELIVERABLE, EXPIRED) is sent to the originator of
the message, where <ei> is again either the USER-EI or TRM.
Inserted to DB. The message was stored in the ISMSC database.
Updated to DB. The message state is updated in the database.
Deleted from DB. The message is removed from the ISMSC database.
Message Trace Example

This example shows a successful message delivery on the first attempt.
19960329012227 Short Message 7 for 8536880000
Received from 'USER-EI SMS1 (TRM)'
Page 6-15
Chapter 6
Maintenance


Inserted to DB
Trying to deliver
State=STATE_BEING_DELIVERED (5), Minor state=none
Updated to DB
State=STATE_DELIVERED (1), Minor state=none
Deleted from DB
4.5.2.
Trace Message
This command starts/stops the ISMSC message trace for a specific subscribers
messages. Information about specified short messages, showing each stage in the
processing of the short message (e.g. short message is being retried, or short
message has been delivered) is recorded in the file msg_trace.log.
NOTE:
This command is effective only if the subscriber has pending

messages in the ISMSC database.
Screen Interface
This option starts and stops the ISMSC message trace for a specific subscribers
messages.
To activate the trace message option:
1.
Select Maintenance in the SMSC Control Menu and press <Enter>. The
2.
Select Trace All Messages and press <Enter>. The SMSC Trace All
Messages Form appears (Figure 6-9).
3.
Enter the appropriate value in the Level field and press <Enter>.
4.
Enter the Subscriber Number in the Subscriber field and select the Save
(F3) key at the bottom of the screen.
Page 6-16

Chapter 6
Maintenance
Figure 6-9: ISMSC Trace Message Screen

To trace a short message, enter
smsc control trace_msg -level <level> [-target <subscriber>]
4.5.3.
Trace All Messages

This option starts and stops the ISMSC message trace for all messages. Tracing of
all messages is specified by the levels defined in Paragraph 4.5. Trace files are
recorded in the file msg_trace.log located in the directory home/smsc/site/trace.
Screen Interface
To activate the trace message option:
1.
2.
Select Trace Message and press <Enter>. The SMSC Trace Message Form
appears (Figure 6-10). The level of details of the trace is according to the
level value.
3.
Enter the appropriate value in the Level field and select the Save (F3) key at
Page 6-17
Chapter 6
Maintenance

Figure 6-10: ISMSC Trace All Messages Screen

To activate tracing for all short messages entering the system:
x
Enter smsc control trace_msg -level <level>.

This initiates the recording of information into the file msg_trace.log,
showing each stage in the processing of the short message (e.g. short
message is being retried, or short message has been delivered).
4.5.4.
Browsing the Trace Files

This command opens a window in the screen that presents the trace file, which
can be viewed by scrolling. Files can also be browsed by a standard UNIX
browser, for example more.
Screen Interface
To activate the ISMSC browse trace option:
1.
2.
Select Browse Trace File and press <Enter>. The SMSC Browse Trace File
Form appears.
3.
Enter the host name in the Host name field. The host name is the name of
the active SFE host. Use View Status to determine the active SFE host.
Page 6-18

4.
Chapter 6
Maintenance
Enter the range of lines (start + 100 lines, end - 100 lines) to be viewed in
the Browse from field (Figure 6-11), and select the Save (F3) key at the
bottom of the screen. The number of lines in the range can be modified, to
view a larger/smaller portion of the file. A window opens presenting the
trace file (Figure 6-8). Refer to Paragraph 4.5. for information on the
contents of the trace file.
Figure 6-11: ISMSC Browse Trace File Form
4.6.
Log Files
The log.SFE, log.MAP, and log.MAPMO log files, located in the trace directory,
contain information on startup, shutdown, redundancy status, connection and
disconnection, and other events and errors.
4.7.
Statistics Files
Statistics generated by the ISMSC include general information, EI status, and
performance data. The data is reported separately for Source EIs and target EIs.
Statistics reports are configurable. They are generated by counters, and by the
retry definition rules, which may be flagged for inclusion in the statistics report.
Refer to Paragraph 4.7.2. and Chapter 10, Paragraph 7.2.3.2.
When printing a status report, the SFE scans all the EI counters and calculates the
total ISMSC statistics for each counter. Both the individual EI counters and the
overall ISMSC counters are in the statistics report. All non-zero statistic counters
are printed, and all zero statistic counters are not printed. All counters may be
included or excluded from the statistics report, as specified by the user.
Page 6-19
Chapter 6
Maintenance

Statistics produced by the ISMSC are stored in dedicated files in the trace
directory. Files are generated at configurable times. A statistics file is closed when
the subsequent one is opened. Statistics reports are generated hourly into the
currently open file.
The information contained in the statistics file is the same as the output of the
control status command, in a different format. The statistics file presents either a
string of values or tabulated statistics, determined by the parameter
status_file_format (Paragraph 4.7.1.).
A statistics file can be collected by a management center via FTP. A user name
dedicated for file transfer is defined in the ISMSC systems as smsc_ftp and
password smsc_ftp.
A cleanup job runs daily in the ISMSC and deletes statistics files that are older
than a configurable number of days.
The names of statistics files are in the format STAT.YYYYMMDDhhmmss where
YYYYMMDDhhmmss is the date and time of the files creation.
4.7.1.
Defining Statistics Files

The following parameters, located in the file sfe.config in the directory site/config
are used when defining the generation and storage of log files:
x
status_log_open_hours contains a comma-separated-list of the hours of the

day when a new statistics file is to be opened.
status_log_keep_days controls the deletion of files. Files older than the

value of this parameter (in days) are deleted daily.
The creation of the first status report is done at a round hour plus the value
of the parameter status_log_start_at which is specified in minutes.
status_file_format controls the format of the statistics file. The value is

either raw (Paragraph 4.7.3.) or detailed (Paragraph 5.).
ei_type.1.sei_stats_report_structure specifies which source EI counters are

included in the statistics report. Refer Paragraph 4.7.2.
ei_type.2.tei_stats_report_structure specifies which target EI counters are

included in the statistics report. Refer to Paragraph 4.7.2.
The following file, located in the file sfe.config in the directory site/config is
created automatically:
x
4.7.2.
stats_index.sfe is an index of error names. Refer to Paragraph 4.7.3.
Counters
Counters are collected from source and target EIs. The source EI statistics are
compiled for each EI individually. A source EI is one of the following:
x
Page 6-20
Email EI

Chapter 6
Maintenance
IS41 EI
MAP EI
MAP-MO EI
OPER EI
SMPP EI
TAP EI
TRM EI
Web EI
The target EI is either MAP or IS41. Statistics are compiled for the active and
standby target EIs in one counter.
The configuration parameters specify which of the Source and Target EI statistics
are included in the report. The format of the parameters is:
sei_stats_report_structure = <counter name>:{Y,N}
tei_stats_report_structure = <counter name>:{Y,N}
A value of Y includes the counter in the report, a value of N excludes the counter.
Table 6-1 presents the counter names, a description of the information they
present, and the block name they are given in the raw statistics reports. For more
information on report blocks, refer to Table 6-2.
Table 6-1: Statistics Counters
Counter Name
Description
Raw Statistics
Report Block Name
SEI Counters
sei_report:
SEIname
incoming_sm
Incoming SMs
RTICMM
cancel_cmd
Issued Cancel commands
RTICNRQ
cancelled_sm
Canceled SMs
RTCNCL
replace_req
Replace requests
RTRPRQ
replaced_sm
Replaced SMs
RTRPLC
expired_sm
Expired SMs
RTEXPR
rejected_sm
Rejected SMs
RTRJCT
sei_notify
Issued notifications
RTSINM
Page 6-21
Chapter 6
Maintenance

Counter Name
Description
Raw Statistics
Report Block Name
TEI Counters
tei_report
TEIname
delivery_attempt
Delivery attempts
RTDLVA
delivered_sm
Delivered SMs
RTDLVD
delivery_fail
Delivery fails
RTDLFL
delivery_retry
Delivery retries
RTRTRY
alert_req
Alert requests
RTALRT
success_alert
Successful alerts
RTGALR
retry_distrib
Retry distribution
DLVMS#, DLVMS9
error_diag
Occurrences of detailed error
RTDxxx
retry_profile
Occurrences of selection of retry profiles
RTPxxx
retry_exec_prof
Occurrences of execution of retry profiles
RTExxx
retry_rule
Occurrences of selection of retry decision

rules
RTRxxx
stats_rule
Occurrences of selection of statistics rules
RTUxxx
tei_notify
Issued notifications
RTTINM
internal_retry
Occurrences of internal retries
RTINRT
general_error
Occurrences of general errors
RTGxxx
The following counters are defined by the retry rules (Chapter 10, Paragraph 7.2.):
x
error_diag
retry_profile
retry_exec_prof
retry_rule
The counter stats_rule contains additional rules for statistics collection that are in
the same format as the retry rules, but are defined only for statistical purposes.
Counters are specified in a set for each type of EI.
The default file name is: stats_rules.ei.<EI type>
Page 6-22

Chapter 6
Maintenance
where EI type is either MAP or IS41. An example of the file is located in the
config/examples/std directory.
The file is made up of statistics rules in the following format:
condition-1.condition-2.condition-3.condition-4 = [nostat/stat]
where:
condition-I
is the name of a specific condition, or asterisk if no error from that

condition is selected. The number and type of the conditions must
correspond to the errors listed in Chapter 10, Paragraph 7.2.
[nostat/stat]
specifies whether or not the statistics are presented in the report.
Examples:
*.*.ABSENT_SUBSCRIBER_IMSI_DETACHED = stat
*.*.ABSENT_SUBSCRIBER_PAGE_FAILED = nostat
4.7.3.
Reading Statistics Files

Detailed statistics files have the following format:
Count of incoming short messages:
Current minute : 0
Last round minute : 0
Peek per minute : 733
Current hour : 0
Last round hour : 0
Peek per hour : 11740
Total count : 14894
Detailed statistics files appear also as the output to the Status Control command.
For a complete description of the detailed format and an explanation of the fields
in statistics reports and the output to the Status Control command, refer to
Paragraph 5.
Raw statistics have the following form: <block name><values>
The equivalent statistics in raw format presented in the following format:
RTICMM 0 0 733 0 0 11740 14894
Block names and the values they contain are presented in Table 6-1.
The block names that end in XXX represent multiple blocks of statistics. Each
block is identified by the numeric code in the block name.
The file stats_index_file lists the error name and the corresponding numeric code
in the format:
full_counter_name : raw_counter_name
Page 6-23
Chapter 6
Maintenance

where full_counter_name is the name of the counter, and raw_counter_name is the

numeric code.
The blocks that are included in the SEIINF and TEINNF blocks are presented in
SEINNF and TEINNF as individual EIs, and are included in an overall counter for
all EIs.
Table 6-2: Contents of Raw Statistics Report
Block
Name
Meaning
Values
Comment
GNSTAT
General
statistic
Current time
Start time
Number of short messages in DB
Short messages cache hit rate
Number of successful hits
Total number of hits
Number of subscribers in DB
Subscribers cache hit rate
Number of successful hits
Total number of hits
Number of messages ready for retry
yyyymmddhhmmss
yyyymmddhhmmss
SYSTAT
System Status
Host name of the active SFE

State of the secondary SFE
SEIname
Source EI
SEIINF
Source EI
specific
information
RTICMM
Incoming
messages
Page 6-24
R(eady)
C(onnected)
NC(Not Connected)
Version
Connection status
Connection information (if
connected)
Notification queue length
C(onnected)
NC(Not Connected)
IP:port
(192.9.200.5:2401)
Includes blocks:
RTICMM
RTCNRQ
RTCNCL
RTRPRQ
RTRPLC
RTEXPR
RTRJCT
RTSINM
Number in the last round minute

Peak number per minute (in this run)
Number in the current hour
Number in the last round hour
Peak number per hour (in this run)
Total number (in this run)

Chapter 6
Maintenance
Block
Name
Meaning
Values
RTICNRQ
Issued Cancel
commands
as above
RTCNCL
Canceled
messages
as above
RTRPRQ
Replace
requests
as above
RTRPLC
Replaced
messages
as above
RTEXPR
Expired
messages
as above
RTRJCT
Rejected
messages
as above
RTSINM
Source EI
notifications
as above
TEIname
Target EI
Version
Connection status
Connection information (if
connected)
TEIDLG
Number of
open dialogs
TEIINF
Target EI
specific
information
Comment
C(onnected)
NC(Not Connected)
IP:port
(192.9.200.203:....)
Number of open dialogs
Includes blocks:
RTDLVA
RTRTRY
RTDLVD
RTDLFL
RTINRT
RTALRT
RTGALR
RTTINM
RTDxxx
RTPxxx
RTRxxx
RTGxxx
DLVMS#
DLVMS9
Page 6-25
Chapter 6
Maintenance

Block
Name
Meaning
Values
RTDLVA
Delivery
attempts
Number in the last round minute

Peak number per minute (in this run)
Number in the current hour
Number in the last round hour
Peak number per hour (in this run)
Total number (in this run)
RTRTRY
Retry Attempts
as above
RTDLVD
Delivered short
messages
as above
RTDLFL
Delivery
failures
as above
RTINRT
Internal
failures
as above
RTALRT
Incoming alerts
as above
RTGALR
Alerts that
generated a
retry
as above
RTTINM
Target EI
notifications
as above
RTDxxx
Detailed error
diagnostics (a
block as above
per each error);
xxx - error
code
as above
RTExxx
Retry profiles
executed (a
block as above
per each
profile); xxx profile ID
as above
RTPxxx
Retry profiles
selected (a
block as above
per each
profile); xxx profile ID
as above
Page 6-26
Comment

Chapter 6
Maintenance
Block
Name
Meaning
Values
RTRxxx
Retry rules
selected (a
block as above
per each retry
rule); xxx rule ID
as above
RTUxxx
Statistics rules
selected (a
block as above
per each
statistics rule);
xxx - rule ID
as above
RTGxxx
General errors
(a block as
above per each
error); xxx error code
as above
Comment
This block
includes all the
General Errors
used in the
Retry Decision
Rules. Refer to
Chapter 10,
Paragraph 7.2.
3.2.
5.
DLVMS#
9 blocks Number of
delivered
messages after
# retries # =
0...8
as above
DLVMS9
Number of
delivered
messages after
9 retries or
more
as above
Control Status Output

The output to the Control Status command also appears as the detailed statistics
file.
Page 6-27
Chapter 6
Maintenance

The output to the Control Status command consists of three parts: general
information, connections to external interfaces (EI), and performance data.
The ISMSC can be configured to print this report into its log file every fixed time
period (one hour by default).
5.1.
General Information (GNSTAT Block)

The format for the SMSC Statistics and Run start time is YYYYMMDDMMSS.
The information under the headings Short messages DB and Subscribers DB
represent the number of records and the cache hit rate which are specified for the
subscribers and short message databases. The number of records in the short
message database is greater or equal to the number in the subscribers database.
The line Messages ready for retry: 0 is the number of messages whose retry
timeout has expired but are not delivered yet. Usually it is 0 but it can be more in
heavily loaded systems.
5.2.
Connections to External Interfaces (SEIname and

TEIname Blocks)
The line Status of EI: reports on the connections between the SFE and the
different EIs. For each EI the state of its connection to the SFE is described.
According to the EI type additional data may be displayed. The order and types of
the EIs are configuration dependent. The TRM EI represents the connection to the
voice mail system. When the TRM EI is not connected, the SFE queues
notification intended for it. The number of queued notifications is displayed.
The line Status of EI MAP (Target): represent the connection to the GSM
network. The number of open dialogs specifies how many messages are currently
in the middle of the delivery process.
The line Status of EI USER-EI SMS1 (Source): presents status of the User EI,
which is the connection for commands entered using the command line or from
the ISMSC menus.
5.3.
Performance Data
The information under the heading Runtime statistics: presents information
gathered by different counters (RTUCMM, RTICNRQ, RTCNCL...). For each
counter the following information is displayed:
x
The count for the current part of minute. If the report time is 14:41:30 then
only messages for the last 30 seconds are counted.
The count during the last complete minute. In our example messages
between 14:41:00 and 14:41:22 are counted.
The maximal count gathered during a complete minute.
Page 6-28

5.4.
Chapter 6
Maintenance
The count for the current part of an hour. In our case it is for the last 41
minutes and 30 seconds.
The count during the last complete hour. In our case since the system is up
for less than an hour, it is 0.
The maximal count gathered during a complete hour.
Total count since system run start time.
Source EIs
The information under the heading Count of incoming short messages: presents
the number of messages received by the SFE.
The information under the heading Count of cancel short message requests:
presents the number of received requests to cancel short messages. A sender can
cancel a previously sent, yet undelivered, message. The source EI, for example a
voice mail system, cancels a message if a user enters his mailbox before receiving
the voice mail notification message.
The information under the heading Count of canceled/replaced short messages:
presents the number of canceled messages. The source EI, for example a
voicemail system, cancels a message if a user enters his mailbox before receiving
the voice mail notification message.
The information under the heading Count of replaced short messages: presents the
number of replaced messages. The source EI, for example a voicemail system,
replaces a message when a user receives a new voice mail. In this case a message
such as You have 2 voicemail messages is replaced by You have 3 voicemail
messages.
The information under the heading Count of expired short messages: presents the
number of expired messages. A message expires if it has not been delivered before
the expiry time as defined in the ISMSC parameter Expiration.
The information under the heading Count of rejected short messages: presents the
number of rejected messages. Messages are rejected for a number of reasons for
example an illegal subscriber, network problem, illegal equipment.
The information under the heading Count of issued notification messages:
presents the number of notification messages that have been issued. Notifications
are issued as a response to SMs, such as Acknowledgements.
5.5.
Target EIs
The information under the heading Count of delivery attempts: presents the
number of messages sent to an EI for delivery.
The information under the heading Count of delivered short messages: presents
the number of successful delivery indications received by the SFE. It should be
noted that such an indication may result from a message sent in a previous minute.
Page 6-29
Chapter 6
Maintenance

The information under the heading Count of short messages delivery fails:
presents the number of failed delivery indications received by the SFE. It should
be noted that such an indication may result from a message sent in a previous
minute.
The information under the heading Count of retries attempts: presents number of
delivery attempts due to retries. Messages are delivered either when received or
when retried. Count of delivery attempts presents the total number of delivery
attempts and this counter presents the portion of that total which are retries. The
counters in the current section are smaller or equal to those in the previous one.
The information under the heading Count of alerts: presents the Alerts which are
received from the network for informing the ISMSC when a subscriber switches
on his phone. The ISMSC, as a response, sends messages queued for that
subscriber without waiting for a retry timeout to expire.
The information under the heading Count of alerts which caused a retry: presents
the Count of alerts received by the ISMSC that caused a retry. Most, but not all,
alerts cause a retry. Retry will not occur if the message has been canceled by the
time the alert is received or when it is being delivered at that moment. Effective
alerts are also counted as alerts (as described in the previous paragraph).
The information under the heading Count of delivery fails because of internal
reason: presents the number of messages failed because of internal reason.
Internal reason can be caused when system is overloaded and queues are full or
when there is some sort of configuration error. Messages failed because of internal
reason are also counted as failed messages (as described in the previous section).
The information under the heading Count of issued notification messages presents
the number of times that notifications have been issued. Notifications are issued
as a response to SMs, such as delivery.
The information under the heading Count of messages delivered with no retry
presents the number of times that SM were delivered on the first attempt.
The information under the heading Count of messages delivered after X retries:
presents the count of messages that were successfully delivered after the specified
number of retries. These counters give an operator information that may help him
to perform a better tuning of the system retries algorithm. The sum of all these
counters matches the total number of delivered message in Count of delivered
short messages.
The information under the heading Count of <Error Name>: presents the number
of occurrences of the indicated error.
The information under the heading Count of selected profile <type or name>
presents the number of times that the indicated retry profile has been selected.
The information under the heading Count of executed profile <type or name>
presents the number of times that the indicated retry profile has been executed.
The information under the heading Count of retry rule <name> presents the
number of times that the indicated retry decision rule has been selected.
Example:
Page 6-30

Chapter 6
Maintenance
An error is reported as Error X, Error Y, which is mapped to General Error Z, and

there is no defined rule for errors X and Y. In this situation the following counters
are incremented: Error X, Error Y, Error Z, and the profile indicated by Error Z.
5.6.
Sample of Control Status Output

Following is a sample result of the command smsc control status sfe:
---------------------------------SMSC statistics for 19960714063837
---------------------------------SMSC statistics for 19981109200715
---------------------------------Run start time
: 19981107101152
Short messages DB:

Number of records
: 0
Cache hit rate
: 97% (222500 out of 227396)
Subscribers DB:
Number of records
: 0
Cache hit rate
: 92% (64886 out of 69782)
Messages ready for retry: 0

---------------------------------The active system is running on : smsc1
The standby system is ready.
---------------------------------Status of EI 'TRM.1:1
(Source)':
State
: not connected
Number of queued notifications : 0

Status of EI 'MAP:2 1.0 (Target)':
State
: connected (Peer='190.190.17.13:4868' (FD=36))
Number of open dialogs
: 0
Status of EI 'USER-EI|1 SMS1 (Source)':

State
Status of EI 'MAPMO:2 1.0 (Source)':

State
Status of EI 'SMPP.1:1
State
(Source)':
: not connected
Number of queued notifications : 0
Page 6-31
Chapter 6
Maintenance

-------------------------------------------Runtime statistics:
~~~~~~~~~~~~~~~~~~~
*******************
Source EIs
*******************
Count of incoming short messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 21028
Count of cancel short message requests:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of canceled short messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of replace short message requests:

Current minute
: 0
Page 6-32
Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0

Total count
Chapter 6
Maintenance
: 21028
Count of replaced short messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 14
Count of expired short messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of rejected short messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of issued notification messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
*******************
Target EIs
*******************
Count of delivery attempts:
Page 6-33
Chapter 6
Maintenance

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 45398
Count of delivered short messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 16129
Count of short messages delivery fails:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 29269
Count of retries attempts:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 24370
Count of alerts:
Current minute
: 0

Peak per minute
Page 6-34
: 0

Chapter 6
Maintenance
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of alerts which caused a retry:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of delivery fails because of internal reason:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of issued notification messages:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 0
Count of messages delivered with no retry:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Page 6-35
Chapter 6
Maintenance

Total count
: 14940
Count of messages delivered after 1 retry:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 1029
Count of messages delivered after 2 retries:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 70

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 10

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 15
Count of messages delivered after 9 or more retries:

Current minute
Page 6-36
: 0

Chapter 6
Maintenance

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 65
Count of GSM_MAPERR_ABSENT_SUBSC:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 11041
Count of GSM_SM_FAIL_CAUSE_CAPA_EXCEED:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 236
Count of ABSENT_SUBSCRIBER_IMSI_DETACHED:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 11041
Count of SYSTEM_FAILURE:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Page 6-37
Chapter 6
Maintenance

Last round hour
: 0
Peak per hour
: 0
Total count
: 18228
Count of GNRL_SM_DLVR_SYSTEM_FAILURE:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 18228
Count of GNRL_SM_DLVR_ABSENT_SUBSCRIBER:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 11041
Count of Selected profile short:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 6553
Count of Selected profile medium:

Current minute
: 0
Page 6-38
Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 6192

Chapter 6
Maintenance
Count of Selected profile long:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 16997
Count of Selected profile

alert_expected.GNRL_SM_DLVR_ABSENT_SUBSCRIBER:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 4277
Count of Selected profile *.GNRL_SM_DLVR_SYSTEM_FAILURE:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 6009
Count of Executed profile short:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 4489
Count of Executed profile medium:

Current minute
: 0
Page 6-39
Chapter 6
Maintenance


Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 4128
Count of Executed profile long:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 12100
Count of Executed profile *.GNRL_SM_DLVR_SYSTEM_FAILURE:

Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 3653
Count of Retry rule

alert_expected.GNRL_SM_DLVR_ABSENT_SUBSCRIBER:
Current minute
: 0

Peak per minute
: 0
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 4277
Count of Retry rule *.GNRL_SM_DLVR_SYSTEM_FAILURE:

Current minute
: 0

Peak per minute
Page 6-40
: 0

Chapter 6
Maintenance
Current hour
: 0
Last round hour
: 0
Peak per hour
: 0
Total count
: 3655
------------------------------------------------
5.7.
Online Query Tool

The online query tool provides a command line query to extract information about
messages stored in the SFE database. Typically, information is retrieved from an
EI about messages sent earlier by that EI.
The Control EI run by the SMSC administrator or customer care representatives
(as described in the OMAP Technical Bulletin), is defined not just as a source of
messages, but also as a control interface. The Control EI can query messages from
any originating EI. It is possible to run the Control EI in emulation of another EI
to generate an online report about messages from a specific EI.
Online query criteria can return information on the subscriber only, on a single
message, or on multiple messages.
The online query tool generates reports at three levels of detail:
5.7.1.
A short form report that summarizes subscriber and message information
A long form report that provides more message details
A debug report that duplicates a database dump for the messages reported
Short Form Report

The Short form of the online query report consists of two parts: subscriber
information common to all messages pending delivery for the subscriber, and
message information detailing all messages that match the query criteria.
Subscriber information reported includes:
x
Subscriber ID
Retry count
Current retry profile: number of the retry profile currently in use (as
recorded in the stats_index.sfe file).
Current retry count (number of retries using the current retry profile)
Alert expected: whether the SFE expects an SC Alert/Notification for the

subscriber
Next retry time
Number of short messages pending immediate delivery
Number of future delivery short messages
Page 6-41
Chapter 6
Maintenance

Last delivery error code
State: being delivered or pending retry
Minor state: sub-flags related to the delivery state
State date: time and date the subscriber entered this state
Next retry time: When the next pending retry should take place
Message information listed for each message in the report includes:
5.7.2.
Short message number (isn)
Arrival date
Retry count
Message type
Source address
Source EI id
Long Form Report

The Long form of the online query report consists of two parts: subscriber
information common to all messages pending delivery for the subscriber, and
message information detailing all messages that match the query criteria. The
subscriber information is the same as for the Short form of the report. Information
for the messages that match the query criteria is more detailed than the Short
form.
The subscriber information reported is identical to the short form subscriber
information.
Message information listed for each message in the report includes:
x
Subscriber ID
Short message number (isn)
Creation date
Arrival date
Retry count
Message type
Source address
Source EI id
Language
Page 6-42

5.7.3.
Chapter 6
Maintenance
Debug Report
This form is available via the control EI only, and is used for maintenance and
troubleshooting purposes. The Debug form of the online report includes all the
information about a subscriber or message in the same format that is generated by
internal database dump tools.
5.7.4.
Query Format
The command format for initiating an online query of the Control EI, or any other
EI, is:
smsc db_query {-flag1}{-flag2}...{-flagn}
The following optional flags are available:
Flag
Description
target
The target subscriber number for the query. This field is

mandatory if no ISN number provided in the request
source
The source number that submitted short messages to the queried

subscriber. Restricts report to messages from the specified
source.
id
The simulated source EI name (e.g., TRM) that is issuing the

db_query request. This flag is optional.
Default value: USER-EI
emulated_ei
When query is submitted through a Control EI, this flag

specifies the emulated source EI.
Default value: USER-EI
isn
The internal ID of the queried short message. This field is

mandatory if no target message number is provided in the query.
type
The type of the short message included in the query. More than
one short message type can be specified, separated by commas:
-type 2,4,5
Default value: all message types
info_lvl
The query information level:

sm: the short messages information only
subs the subscriber information only
subs+sm: the subscriber and its short messages information
Default value: subs+sm
Page 6-43
Chapter 6
Maintenance

Flag
Description
detail_lvl
The query output level:

essence: short form
full: long for
debug: debug form
Default value: essence
restrict
Restricts the USER-EI feature, which allows emulation query

via the Control EI.
Allowed values: on (yes) or off (no)
5.7.5.
Examples of Database Queries

This section presents a few sample db query results.
Example:
The command:
smsc db_query -target 112233 -info_lvl subs+sm -detail_lvl essence
results in:
Db Query answer received 112233
EI: Received DB Target SME info:
---------------------------------Target SME State information
---------------------------------Target
: 2 : 112233 1 1
Retry count
: 768
Current retry count
: 768
Current retry profile
: 0
Alert expected
: 0
Next retry time
: 19981210220458
Number of short msgs
: 6
Number of deffered msgs
: 0
Previous delivery diagnostics
1st SM state
: 6
1st SM minor state
: 2
1st SM state date
: 19981210214958
Short messages essence info
Page 6-44

Chapter 6
Maintenance
---------------------------------SM No.
: 5
Source EI
: USER-EI.1|1
Source ID
: 0 :
Type
: 0
Arrival date
: 19981207200346
Retry count
: 2
---------------------------------SM No.
: 6
Source EI
: USER-EI.1|1
Source ID
: 2 : 332211 1 1
Type
: 0
Arrival date
: 19981207201034
Retry count
: 6
----------------------------------
---------------------------------SM No.
: 12
Source EI
: USER-EI.1|1
Source ID
: 0 :
Type
: 1
Arrival date
: 19981207202521
Retry count
: 16
---------------------------------SM No.
: 13
Source EI
: USER-EI.1|1
Source ID
: 0 :
Type
: 2
Arrival date
: 19981207202530
Retry count
: 18
----------------------------------
Page 6-45
Chapter 6
Maintenance

SM No.
: 16
Source EI
: USER-EI.1|1
Source ID
: 0 :
Type
: 3
Arrival date
: 19981207202842
Retry count
: 24
Example:
The command:
smsc db_query -isn 16 -detail_lvl debug
results in:
Db Query answer received
EI: Received Data Base Query Debug ack
---------------------DB Query Debug ACK :

----------------------
------------------------------------------------------Target SME:
------------------------------------------------------Version=6
ID=112233
EI=[ 2 , 1 ]
Retry count=770
Current Retry count=770
Current Retry Profile=0
Alert Expected =0
Next retry time=19981210221158
Next event time=19981210221158
Trace level =(empty)
General Error =0
Target info =
General Retry Decider=0
Immediate Queue:
length=6
Page 6-46

Chapter 6
Maintenance
message IDs= 5 6 10 12 13 16
Deferred Queue:
length=0
message IDs=
----------------- END of TargetSME --------------------
EI: Received Data Base Query Debug ack
---------------------DB Query Debug ACK :

----------------------
--------------------------------------------------------------Short Message: 16
--------------------------------------------------------------Version=7
Language=Unknown language (7)
Date Format=
Time Format=
Priority=0
Trace Level=0
Notify states=[]
Target ID=[2,1] 2 : 112233 1 1
Original Target ID=1 : 112233 1 1
Source ID=0 :
Source EI='USER-EI.1|1 SMS1 (Source,Control)'
Type=3
Class=0
Initial Retry Count=24
Arrival Date=19981207202842
Creation Date=19981207202842
Arrival Time Diff=0
Delivery Time=19700101020000
Gsm Priority=-1
Gsm Replace=-1
Page 6-47
Chapter 6
Maintenance

Gsm Protocol_id=-1
State=STATE_INITIAL (0)
Minor State=0
State Date=19981207202842
Notification Ind=1
Text length=2
Text=t3
-------------------------- END of SM --------------------------
Example:
The command:
smsc db_query -target 112233 -type 3 -detail_lvl full
results in:
EI: Received DB SM State info:
-----------------------SM State information :
-----------------------Prev Delivery
: (empty)
SM Source
: 0 :
SM Target
: 2 : 112233 1 1
SM No.
: 16
SM Type
: 3
SM Language
: Unknown language (7)
SM Creation Date
: 19981207202842
SM Arrival Date
: 19981207202842
SM State
: 0
SM Minor State
SM Recipient RC
: 0
SM State Date
: 19981207202842
SM Retries #
: 746
SM Trace Level
: 0
Source Ei
: USER-EI.1|1
Next retry time
: 19981210221158
Number of msgs
: 6
Number of def msgs
: 0
Page 6-48

Chapter 6
Maintenance
Current retry profile : 0

Alert expected
: 0
Example:
The command:
smsc db_query -target 112233 -source 332211 -detail_lvl essence
results in the full form, since only one SM was found:

EI: Received DB SM State info:
-----------------------SM State information :
-----------------------Prev Delivery
: (empty)
SM Source
: 3 : 332211
SM Target
: 2 : 112233 1 1
SM No.
: 6
SM Type
: 0
SM Language
: Unknown language (7)
SM Creation Date
: 19981207201034
SM Arrival Date
: 19981207201034
SM State
: 0
SM Minor State
SM Recipient RC
: 0
SM State Date
: 19981207201034
SM Retries #
: 764
SM Trace Level
: 0
Source Ei
: USER-EI.1|1
Next retry time
: 19981210221158
Number of msgs
: 6
Number of def msgs
: 0
Current retry profile : 0

Alert expected
: 0
Page 6-49
Chapter 6
Maintenance
6.

Assembly and Disassembly of ISMSC Modules

This section provides instructions for replacing modules in the ISMSC. When
replacing modules in the ISMSC, refer to Figure 6-12.
Figure 6-12: ISMSCExploded View

The ISMSC is based on the Pentium II and contains the following components:
x
CPU Board: The CPU is the 300 MHz Pentium II.
ALM Board: The ALM board monitors the internal temperature and fan
activity.
Floppy Disk Drive
DAT Drive
Hard Disk Drive: The hard drive has a capacity of 4.5 GB.
Power Supply: The standard power supply used in other INfinity modules is
used. Within the drawer, LEDs on the power supply indicate +5V, -5V,
+12V, and -12V operation.
HDAM: PCI
Page 6-50

Chapter 6
Maintenance
LIM: Lan Interface module
Fans: Two fans are included in the ISMSC drawer.
Serial RS 232 Board (optional)
Backplane: A passive backplane supports both PCI and ISA boards. The
backplane provides four PCI slots, six ISA slots, and one CPU slot that
accesses both PCI and ISA tracks of the backplane. Three PCI slots are
universal. One slot is VGA only.
The operating system of the ISMSC (Pentium) is UNIXware. A keyboard and

three button mouse attach to ports on the CPU board. A standard monitor uses the
SVGA driver resident on the CPU card.
WARNING: There is an Electrical Shock Hazard when servicing this system.
Switch off the power before opening system cabinets or attempting to
remove or adjust boards, components, or other electrical
subassemblies.
CAUTION: These modules contain Electrostatic Discharge Sensitive (ESDS)
components. Improper handling may damage components. When
working with modules, always attach an ESD wrist strap.
Do not remove a module from its protective wrapper or from the
module drawer unless you have taken ESD precautions. When
installing or removing modules, place them component-side up, on a
grounded, static-free surface. Put the module on a special ESD foam
pad if available. Do not slide the modules over a surface of any kind.
NOTES:
During disassembly procedures, be sure to retain all hardware for use

during assembly procedures.
Before installing a disk or board or other electrical component, always
verify that required jumpers and DIP switches have been properly set.
Refer to the following sections for relevant information.
6.1.
General Instructions for the ISMSC Boards

The instructions in this section describe the general board replacement procedures
for the ISMSC. Additional instructions specific to each board are provided in
Paragraph 6.2.
To replace a faulty board in the ISMSC:
1.
Perform an orderly shutdown of the operating system.
2.
Turn off the appropriate switch on the distribution panel.
3.
Unscrew the four screws securing the ISMSC to the rack frame.
Page 6-51
Chapter 6
Maintenance
6.2.

4.
Slide the ISMSC forward in the rack frame.
5.
Unscrew the six screws on the top cover, and remove the top cover.
6.
Tag and disconnect any cables leading to the faulty board.
7.
Unscrew the screw securing the board to the chassis.
8.
Lift the board out of the ISMSC.
9.
Insert the replacement board.
10.
Replace the screw securing the board to the chassis.
11.
Reconnect any cables leading to the board.
12.
Replace the top cover and tighten the six screws securing it.
13.
Slide the ISMSC into the rack frame.
14.
Replace the four screws securing the ISMSC to the rack frame.
15.
Turn on the appropriate switch on the distribution panel.
Specific Instructions for the ISMSC CPU Board

In addition to the instructions in Paragraph 6.1., when replacing the CPU, verify
that the board is configured as presented in Figure 6-13.
23
JP2
SW4
SW3
SW2
JP4
JP6
JP15
JP12 JP13
ON
OFF
JP19
JP26
JP25
JP24
JP14
JP17 JP18
SW1
JP5
INSTALLED
NOT INSTALLED
IDG00953
Figure 6-13: ISMSCCPU Board Jumpers
Page 6-52

6.3.
Chapter 6
Maintenance
ISMSC Hard Disk Drive

To replace the hard disk drive on the ISMSC:
6.4.
1.
2.
3.
4.
5.
Unscrew the six screws on the top cover, and remove the top cover.
6.
Remove the connector and flat cable from the hard disk drive.
7.
Loosen the three captive screws securing the hard disk drive housing to the
chassis.
8.
Lift the hard disk drive out of the ISMSC.
9.
Remove the four screws securing the hard disk drive to the housing.
10.
Verify that the replacement drive is configured identically to the faulty

drive.
11.
Insert the replacement drive to the housing.
12.
Replace the four screws securing the hard disk drive to the housing.
13.
Insert the replacement hard disk drive.
14.
Tighten the three captive screws securing the hard disk drive housing to the
chassis.
15.
Reconnect the connector and flat cable leading to the hard disk drive.
16.
Replace the top cover and tighten the six screws securing it.
17.
18.
19.
ISMSC Floppy Disk Drive

To replace the disk drive on the ISMSC:
1.
2.
3.
4.
5.
Unscrew the six screws securing the front panel to the module, and remove
the front panel.
6.
Tag and disconnect the cable leading to the floppy disk drive.
Page 6-53
Chapter 6
Maintenance
6.5.

7.
Loosen the captive screw securing the floppy disk drive to the chassis.
8.
Slide out the floppy disk drive housing.
9.
Remove the four screws securing the floppy disk drive to the housing.
10.
Insert the replacement floppy disk drive into the housing.
11.
Replace the four screws securing the floppy disk drive to the housing.
12.
Slide in the replacement floppy disk drive.
13.
Tighten the captive screw securing the floppy disk drive to the chassis.
14.
Reconnect the cable leading to the floppy disk drive.
15.
Replace the front cover, and screw in the six screws.
16.
17.
ISMSC DAT Drive

To replace the DAT drive on the ISMSC:
1.
2.
3.
4.
the front panel.
5.
Loosen the captive screw securing the DAT drive to the chassis.
6.
Slide out the DAT drive.
7.
To set the SCSI ID on the internal DAT drive, verify that all eight dip
switches, SW1 through SW8, on the bottom of the unit are set to ON
(Table 6-3). Set jumpers on the back of the drive as in Table 6-4.
Table 6-3: DAT Drive Switch Configuration

Switch Number
Position
SW1
On
SW2
On
SW3
On
SW4
On
SW5
On
SW6
On
Page 6-54

Chapter 6
Maintenance
Switch Number
Position
SW7
On
SW8
On
Table 6-4: DAT Drive Jumper Configuration
6.6.
Jumper Label
Setup
SCSI 0
Installed
SCSI 1
Installed
SCSI 2
Not Installed
TERM PWR
Installed
8.
Slide in the replacement DAT drive.
9.
Tighten the captive screw securing the DAT drive to the chassis.
10.
Replace the front cover, and screw in the six screws.
11.
12.
ISMSC Power Supply

To replace the power supply on the ISMSC:
1.
2.
3.
4.
5.
the front panel.
6.
Remove the connectors from the power supply.
7.
Slide the power supply forward out of the chassis
8.
Slide in the replacement power supply
9.
Reattach the connectors to the power supply
10.
Replace the front cover, and screw in the six screws securing it in place.
11.
12.
13.
Page 6-55
Chapter 6
Maintenance
6.7.

ISMSC Fan Module

To replace the fan module on the ISMSC:
7.
1.
2.
3.
4.
5.
the front panel.
6.
Tag and disconnect the cable from the fan.
7.
Loosen the three captive screws securing the fan to the chassis.
8.
Remove the fan from the ISMSC.
9.
Insert the replacement fan.
10.
Tighten the three captive screws securing the fan to the chassis.
11.
Reconnect the cables to the power supply.
12.
Replace the front cover, and screw in the six screws securing it in place.
13.
14.
15.
Maintenance of the ISMSC Platform

ISMSC Platform LEDs:
On the units front panel there are four diagnostic LEDs:
x
Run: Lights green when power is being supplied to the IMU
Power: Lights green when power is being supplied to the IMU
Reset: Illuminated when a reset is in progress
Floppy Disk LED: Illuminated when disk access is in process.
On the units rear panel there is one diagnostic LED:

x
LAN card: Lights amber when 100Mb/s mode is selected. This LED
indicates when a receive packet that passed the address filtering is being
received, or a transmission is in progress.
Lights green to indicate a connection to an active network.
There are two internal LEDs, visible when the top cover is removed:
x
Page 6-56
Backplane LEDs: Lights green when +5V, -5V, +12V, -12V voltage is being
supplied to the Backplane.

Chapter 6
Maintenance
ALM LED: Lights red when the internal temperature of the drawer exceeds
50 degrees C.\
Page 6-57
Chapter 7
IPOS Provisioning

Chapter 7
IPOS Provisioning
Table of Contents
1. Program Installation ...............................................................................................................7-1
1.1. Information Required .........................................................................................................7-1
1.2. Installation IPOS ................................................................................................................7-1
2. Starting the ISMSC Paging Operator Station Application...................................................7-1
3. The IPOS Send Message Screen ...........................................................................................7-2
4. IPOS Send Message Main Menu............................................................................................7-4
4.1. Window Control..................................................................................................................7-5
4.2. File Menu Commands........................................................................................................7-5
4.3. Language Menu .................................................................................................................7-5
4.4. View Menu .........................................................................................................................7-5
4.5. Setup Menu........................................................................................................................7-6
4.6. Help Menu..........................................................................................................................7-6
5. Working with IPOS..................................................................................................................7-6
5.1. Creating a New Short Message .........................................................................................7-6
5.2. Deleting an Existing Message............................................................................................7-6
5.3. Clearing the Current Message ...........................................................................................7-7
5.4. Saving Messages...............................................................................................................7-7
5.5. Sending a Message ...........................................................................................................7-7
5.6. Changing the Environment Language ...............................................................................7-8
5.7. Setting Up the ISMSC Paging Operator Station Application Parameters ..........................7-8
5.7.1. Paging System Setup .................................................................................................7-8
5.7.2. Message Setup ...........................................................................................................7-9
5.8. Interface Utilities ..............................................................................................................7-10
5.8.1. Displaying Help .........................................................................................................7-10
5.8.2. Printing the Contents of the Active Screen ...............................................................7-10
5.8.3. Previewing the Contents of the Active Screen..........................................................7-10
5.8.4. Setting Up the Printer................................................................................................7-11
Page 7-i
Chapter 7
IPOS Provisioning

List of Figures
7-1
IPOSTypical Send Message Screen for English Messages........................................... 7-2
7-2
IPOSTypical Send Message Screen for Simplified Chinese and English Messages..... 7-3
7-3
IPOSServer Options Dialog Box..................................................................................... 7-8
7-4
IPOSMessage Setup Dialog Box.................................................................................... 7-9
List of Tables
7-1
IPOSSend Message Screen Elements........................................................................... 7-3
7-2
IPOSSend Message Toolbar Buttons............................................................................. 7-4
7-3
IPOSSend Message Screen Control Buttons................................................................. 7-4
7-4
IPOSServer Options Dialog Box Controls ...................................................................... 7-9
7-5
IPOSMessage Setup Dialog Box Controls ................................................................... 7-10
Page 7-ii

1.
Chapter 7
IPOS Provisioning
Program Installation
This section describes the installation procedure for the IPOS application. Check
the Readme file found in the program folder for any late-breaking changes.
1.1.
Information Required
Prepare the following information for use in the installation process:
1.2.
First server name. For an explanation, refer to Paragraph 5.7.1.
Second server name. For an explanation, refer Paragraph 5.7.1.
Users Name. The default is taken from the Windows installation.
Users Company. The default is taken from the Windows installation.
Destination Directory. The main installation directory of the application.

The default is Comverse.
Language or languages to be supported (if custom installation is chosen).
Program Folders. The name of the folder that holds the application icons.
The default is ISMSC Paging Operator Station.
Installation IPOS
IPOS is installed from two diskettes.
To install the IPOS application:
2.
1.
Insert the installation diskette number 1 in the diskette drive.
2.
Activate the setup program:

a.
Click Run in the Start menu.
b.
Type A:\setup and press <Enter>. The Wizard Setup progress window
appears.
3.
Fill in information as requested during the installation process.
4.
Insert installation diskette number 2 when requested.
5.
Confirm that on completion, the ISMSC Paging Operator Station icon has
been created and is functional.
Starting the ISMSC Paging Operator Station

Application
To start the ISMSC Paging Operator Station application:
1.
Select Programs from the Taskbar Start menu.
2.
Select the Comverse folder (or the alternative designated at installation).
Page 7-1
Chapter 7
IPOS Provisioning
3.
3.

Click the IPOS application icon. The Send Message screen appears
(Figure 7-1 and Figure 7-2).
The IPOS Send Message Screen

Most of the activity of the application is performed in the Send Message screen.
Figure 7-1 and Figure 7-2 present examples of the IPOS Send Message screen for
single and dual language environments respectively.
Figure 7-1: IPOSTypical Send Message Screen for English Messages
Page 7-2

Chapter 7
IPOS Provisioning
Figure 7-2: IPOSTypical Send Message Screen for Simplified Chinese and
English Messages
The IPOS Send Message screen is composed of the elements listed in Table 7-1
(refer to Figure 7-1 and Figure 7-2):
Table 7-1: IPOSSend Message Screen Elements
Element
Description
Title Bar
This bar contains the title of application.
Main Menu
This bar contains the highest level options of the application.

Clicking on an option causes a menu associated with that option to
pop up.
Standard Toolbar
The icons on the standard toolbar provide quick access to

commonly used menu-driven commands.
Text Entry Boxes
These boxes allow the user to enter area prefix (refer to Table 7-5),
subscriber number and message data.
List Box
The commonly used messages list is displayed here.
Control Buttons
Control buttons let the user perform the specific actions of adding
or deleting messages.
Status Bar
The current state of the program or an explanation of the currently

selected menu option is displayed here.
Page 7-3
Chapter 7
IPOS Provisioning

The interface is user friendly, intuitive and completely mouse driven. All menus,
control buttons and toolbars are activated by means of a simple mouse click or key
combination press.
4.
IPOS Send Message Main Menu

The following paragraphs detail the menu options found in the IPOS Send
Message menu. When working in the Main Menu, refer to Table 7-2 and Table 7-3
for information on the buttons in the window.
Table 7-2: IPOSSend Message Toolbar Buttons
Button
Name
Description
Window Control
Accesses the standard window control features.
Connect
Connect to the ISMSCs server before sending

messages to cellular subscribers.
Disconnect
Disconnect from the ISMSCs server after completing

the sending of messages to cellular subscribers.
Save
Save the current message list for future use.
Print
Print the current message list.
Message Sending
Send the current short message to a cellular subscriber.
Message Clearing
Clear the contents of the message text entry box.
Help
Activate the IPOS help application.
Table 7-3: IPOSSend Message Screen Control Buttons

Control
Button
Page 7-4
Name
Description
Add Message
Adds a message to the message list.
Delete Message
Deletes a message from the message list.

4.1.
Chapter 7
IPOS Provisioning
Window Control
Click on the Window Control icon at the left of the Send Message menu bar to
access the standard window control features:
4.2.
Restore
Move
Size
Minimize
Maximize
Close
Next
File Menu Commands

The File menu contains the following options.
4.3.
Connect: Connects the workstation to the ISMSC server.
Disconnect: Disconnects the workstation from the ISMSC server.
Send: Sends the message to the server for relay to the subscriber.
Clear: Clears the contents of the Message Text box.
Save: Saves the currently displayed message list to disk.
Print: Prints the list of messages. The Print dialog box provides several
options to assist in the print process.
Print Preview: Displays the message list in printed page format for preview
before printing.
Print Setup: Describes the printing setup options related to your computer.
Exit: Quits the program after prompting to save message list.
Language Menu
Select this option to reveal the languages available. Where there is more than one
language in which messages can be written, this menu displays the available
languages. Click the language to be activated.
4.4.
View Menu
Select this option to reveal switches for the following screen elements:
x
Toolbar
Status Bar
Page 7-5
Chapter 7
IPOS Provisioning

The display or hiding of these elements is controlled by toggle clicking the

appropriate bar name.
4.5.
Setup Menu
Two setup options are available from this menu:
x
Server setup: Parameters for connecting to the server are set here.
Message setup: Parameters for transmission of messages, such as area codes

to prefix subscriber numbers, are set here.
Refer to Paragraph 5.7. for setup details.
4.6.
Help Menu
Selecting the Help Topics option of the IPOS Help menu activates the
applications online help reference tool.
Details of the IPOS version can be viewed by pressing the About option of the
Help menu.
5.
Working with IPOS

The application is based on the following graphical elements:
x
Send Message window
Server Option dialog box
Message Setup dialog box
A single button connection function links the application to the ISMSC server.
The IPOS application is protected against unauthorized use by a locally
(workstation) maintained password. No password is used on the ISMSC side.
5.1.
Creating a New Short Message

To create a new message and add it to the Messages List:
5.2.
1.
In the Send Message window, fill in the Subscriber Number and Message
Text fields.
2.
Click Add Message.
Deleting an Existing Message

To delete an existing message from the Messages List:
Page 7-6
1.
In the Send Message window, highlight the message to be deleted.
2.
Click Delete Message.

5.3.
Chapter 7
IPOS Provisioning
Clearing the Current Message

To clear the current message:
x
In the Send Message window, select Clear from the File menu.
In the Send Message window, click on the Message Clearing toolbar icon.
The contents of the Subscriber Number and Message Text fields are erased.
5.4.
Saving Messages
To save all the messages in the subscribers Message List for future re-use:
1.
In the Send Message window, fill in the Subscriber Number field.
2.
Click Save from the File menu of the Main menu

or
Click on the Save toolbar icon.
NOTE:
5.5.
Messages are saved automatically when the application is exited

normally.
Sending a Message
To send a short message to a subscriber:
1.
Connect to a server.
2.
In the Send Message window, select a previously saved message from the
Messages List or create a new message by entering text into the Message
Text field.
3.
Enter the subscribers phone number in the Subscriber Number field.
4.
Select Send from the File menu of the Main menu

or
Press the <Ctrl>+<S> key combination
or
Click on the Message Sending toolbar icon.
The Message Sending toolbar button remains disabled until the operation is
completed.
NOTE:
If errors occur during transfer, they are indicated in popup

message windows.
On completion, a detailed status message is displayed on the status bar.
Page 7-7
Chapter 7
IPOS Provisioning
5.6.

Changing the Environment Language

The IPOS application includes a National Language Support option, which allows
switching between the supported languages.
To change the environment language:
5.7.
1.
Click Disconnect to disconnect from the ISMSCs server.
2.
Select the required language from the Language menu of the Main menu.
The system responds by displaying all windows and their contents in the
selected language.
3.
Click Connect to reconnect to the ISMSCs server.
Setting Up the ISMSC Paging Operator Station

Application Parameters
Two categories of parameters must be set correctly in the IPOS application before
connecting to the server. The two parameter categories are described in
Paragraph 5.7.1. and Paragraph 5.7.2.
5.7.1.
Paging System Setup

The paging system server options are configured in the Server Options dialog box
(Figure 7-3).
To configure the paging system setup data:
1.
Click Server Options from Setup in the Main menu.
2.
Configure the various options as described in Table 7-4.
3.
Click OK to accept the new data or Cancel to ignore the newly entered data.
Figure 7-3: IPOSServer Options Dialog Box
Page 7-8

Chapter 7
IPOS Provisioning
Table 7-4: IPOSServer Options Dialog Box Controls
5.7.2.
Control
Description
First Server
Name
Accept or modify the name or IP address of the providers first server.
Second Server
Name
Accept or modify the name or IP address of the providers second

server.
Server Port
Accept or modify the providers port number on the connected server.
OK
Select this button to set the default settings of the dialog box to their
new values.
Cancel
Select this button to reset the settings of the dialog box to their values
on entry.
Message Setup
The paging system setup data is configured in the Message Setup dialog box
(Figure 7-4).
To configure the paging system setup data:
1.
Click Message Setup from Setup in the Main menu.
2.
Configure the various options as described in Table 7-5.
3.
Click OK to accept the new data or Cancel to ignore the newly entered data.
Figure 7-4: IPOSMessage Setup Dialog Box
Page 7-9
Chapter 7
IPOS Provisioning

Table 7-5: IPOSMessage Setup Dialog Box Controls
5.8.
Control
Description
Prefix Number
A digit string that can be prefixed to the subscribers phone number. It

is used to hold a country or area code.
Enabled
A radio button that, when checked, causes the Prefix Number to be

prefixed to the subscribers phone number.
Phone Number
Length
Minimum and maximum values allowed for character string lengths of

phone numbers (not including prefix).
Message Length
The maximum byte length of any valid short message.
OK
Select this button to set the default settings of the dialog box to their
new values.
Cancel
Select this button to reset the settings of the dialog box to their values
on entry.
Interface Utilities
The utilities in Paragraph 5.8.1. through Paragraph 5.8.4. are available from each
active screen.
5.8.1.
Displaying Help
To activate online help, either:
5.8.2.
Select one of the items from the Interface Contents screen which appears
when the Help Topics option of the Help menu is chosen or
Press the Help toolbar button
Printing the Contents of the Active Screen

To print the contents of the active screen to the printer:
5.8.3.
Click Print from the File menu, or
Press the Print toolbar button
Previewing the Contents of the Active Screen

To preview the contents of the active screen before printing to the printer:
x
Page 7-10
Click Print Preview from the File menu.

5.8.4.
Chapter 7
IPOS Provisioning
Setting Up the Printer

To confirm or modify the printer settings:
x
Click Print Setup from the File menu.
Page 7-11
Chapter 8
Email Provisioning

Chapter 8
Email Provisioning
Table of Contents
1. Overview ..................................................................................................................................8-1
2. Configuration ..........................................................................................................................8-1
2.1. User Perspective................................................................................................................8-1
2.1.1. Short Message Format ...............................................................................................8-1
2.1.2. Subscriber Filtering .....................................................................................................8-2
2.2. System Perspective ...........................................................................................................8-2
2.2.1. SMTP Server ..............................................................................................................8-2
2.2.2. email2sms Program....................................................................................................8-2
2.2.3. Email EI.......................................................................................................................8-3
Page 8-i

1.
Chapter 8
Email Provisioning
Overview
This chapter provides a description of the steps necessary to configure the ISMSC
ShortEmail application. Installation is presented in Chapter 10.
The application is based on two components:
2.
The Email Server. Currently the standard UNIX Sendmail server is used.
The ShortEmail EI.
Configuration
Configuration of the Short-Email application is done in the following file on the
ISMSC machine: site/config/EMAIL.config.
Configuration of the Email Server used by the ShortEmail application is done in
the following files on the IMU machine:
/etc/sendmail.cf
site/config/sendmail.allowed
site/config/sendmail.prefixes
site/config/SENDMAIL.config
2.1.
User Perspective
2.1.1.
Short Message Format (Paragraph 2.1.1.)
Subscriber Filtering (Paragraph 2.1.2.)
Short Message Format

The operator can specify how Email messages are formatted into short messages.
The format can be specified using the SM_PATTERNconfiguration variable, in the
file SENDMAIL.config. The format includes any characters. The following
placeholders are used as indicated:
%e
The senders address
%n
The senders real name
%s
The Email subject
%t
The Email body
%a
Attachments description
Page 8-1
Chapter 8
Email Provisioning

For each of the above place holders it is possible to specify a length limitation. If
a value exceeds this limitation, it is truncated. A length limitation is specified by a
colon and a positive integer number.
The default format string is %n(%s:20)%a%t. This means: the sender name, the
subject (up to 20 characters) within brackets, attachments description, and the
message body.
2.1.2.
Subscriber Filtering
The operator has the option to enable/disable the service for specified users. This
is specified in the sendmail.allowed file in the site/config directory. The first line
specifies the filtering mode: allowed or denied. In allowed mode the service is
enabled only for subscribers specified in the file. In denied mode the service is
enabled for everybody except for subscribers specified in the file. Subscribers are
specified in the file by their MSISDN/MIN number, one per line in the beginning
of the line.
2.2.
System Perspective
Short Emails to the system are accepted by an SMTP server. The server forwards
them to an email2sms program that parses the Email, formats it and forwards it to
an Email EI. The Email EI program forwards it to the SFE.
For robustness it is possible to have two copies of the Email EI running on
different machines. The email2sms program contacts one of the Email EIs.
2.2.1.
SMTP Server
The SMTP server is a variation of the UNIX sendmail program. It listens on the
well-known Email port (TCP 25) and receives Email using the SMTP (and
ESMTP) protocols.
The configuration file of the SMTP server is sendmail.cf and it is located in the
/etc directory. During installation the following items should be configured:
x
Domain name
Outgoing Internet connected SMTP server
The operator can also specify valid addresses to be used. This is done by
specifying the allowed prefixes of the MSISDN/MIN numbers in the
sendmail.prefixes file in the site/config directory. If an Email is sent to an
MSISDN/MIN that does not begin with one of the allowed prefixes then the Email
is returned to the sender together with an explanation message. The format of the
sendmail.prefixes file is that each prefix is specified at the beginning of a line.
2.2.2.
email2sms Program
The email2sms program handles Email received by the SMTP server. If the Email
address and content are OK, then a short message is formatted and sent to the
Email EI for delivery.
Page 8-2

Chapter 8
Email Provisioning
Relevant configuration variables are:
2.2.3.
SFE_HOST
Host on which the Email EI runs
SFE_ALTERNATE_HOST
Additional host on which the Email EI can run
EMAIL_EI_PORT_NUMBER
TCP/IP port used by the Email EI for receiving requests
SM_PATTERN
Described in Paragraph 2.1.1.
SUBS_PREFIX
A prefix to add to MSISDN/MIN before sending to the

Email EI.
RECEIVE_ATTACHMENTS
Whether the ShortEmail system accepts attachments

within the Email
DOMAIN_NAME
The SMTP servers domain name
MAX_SM_LENGTH
Maximal short message length
EMAIL2SMS_PORT_NUMBER
TCP/IP port used by the email2sms for receiving

requests
Email EI
The Email EI is responsible for sending the short Emails to the SFE part of the
ISMSC. For redundancy there may be two Email EIs running on two different
hosts.
The relevant configuration variables are:
email.port
TCP/IP port to listen on for incoming requests
Page 8-3
Chapter 9
Web Access Provisioning

Chapter 9
Table of Contents
1. Overview ..................................................................................................................................9-1
2. Configuration ..........................................................................................................................9-1
2.1. User Perspective................................................................................................................9-1
2.2. System Perspective ...........................................................................................................9-2
2.2.1. Web Server.................................................................................................................9-2
2.2.2. Web EI ........................................................................................................................9-2
Page 9-i

1.
Chapter 9
Overview
The Web Access application may be customized for the specific needs of the
service provider by editing the HTML page. The only requirements are that the
input fields and buttons remain on the page. The service provider may add links to
other sites, or embed text and graphics, and create links from other sites to the
current one.
It is also possible to link the customer-provided web site with the Web Access
application (using a hyperlink). In this case, connectivity between the customers
server and the ISMSC should be maintained.
This chapter provides a description of the configuration the ISMSC Web Access
application. Installation is described in Chapter 10.
The application is based on two components:
2.
The Web Server. Currently the Apache Web server is used.
The Web access EI.
Configuration
Configuration of the Web application is performed in the following file:
site/config/WEB.config
Configuration of the Web Server used by the application is performed in the
following files:
site/httpd/htdocs/cgi-bin/send_sm.cgi
site/httpd/htdocs/send_sm.html
site/config/APACHE.config
site/config/APACHE.config.local
2.1.
User Perspective
HTML Page Format
Two configuration variables are available for specifying HTML pages to be
displayed to a user as a response to a successful or failed message submission:
SUCC_HTML_FILE
HTML page to be displayed after a successful submission
FAIL_HTML_FILE
HTML page to be displayed after a failed submission
The HTML pages should be located in the site/httpd/htdocs directory.

If none of the values are set, then a default screen will be displayed (generated by
the CGI).
Page 9-1
Chapter 9
2.2.

System Perspective
Short messages generated through the web access application are submitted from a
web browser, displaying an HTML page, and accepted by an HTTP (web) server.
The server runs a CGI script, which forwards them to the Web EI. The Web EI
program forwards it to the SFE which is the main part of the ISMSC.
For redundancy it is possible to have two copies of the Web EI running on
different machines.
2.2.1.
Web Server
The web server accepts HTTP requests issued from a web browser and activates a
CGI script, which interprets them. The following configuration variables control
these issues:
2.2.2.
WEB_EI_MAIN_HOST
Host on which the web EI runs
WEB_EI_ALTERNATE_HOST
Additional host on which the Web EI can run
WEB_EI_PORT
TCP/IP port used by the Web EI to receive requests
WEB_SERVER_PORT
The TCP/IP port number on which the Web server

listens for new connections
PHONE_LENGTH
Maximal length of a subscriber number
MAX_SM_LENGTH
The maximal length of a short message text
LANGUAGE_SUPPORT
Whether support for languages other then English is

required
Web EI
When submitting a request using the Web interface a connection is made from the
CGI script to a Web EI. The Web EI is a program which is used as a gateway
between the Web interface and the SMSC. In order for the Web interface to work
the Web EI program should be up and running. For robustness it is possible to
have two copies of the Web EI running on different machines. The following
configuration variable controls these issues:
TEXTAPI.port_number
Page 9-2
TCP/IP port used by the Web EI to receive requests
Chapter 10
Installation

Chapter 10
Installation
Table of Contents
1. Overview ................................................................................................................................10-1
2. Installation .............................................................................................................................10-1
2.1. Pre-installation Checklist..................................................................................................10-1
2.2. CPU Board Configuration ................................................................................................10-1
2.2.1. Installing the CPU Board...........................................................................................10-2
2.2.2. SCSI Adaptec Adapter Setup ...................................................................................10-8
2.3. SS7 Link Board Configuration..........................................................................................10-8
2.3.1. SS7 Link Board Hardware Configuration ..................................................................10-8
2.3.2. SS7 Link Board Software Configuration .................................................................10-10
2.4. Device Terminations Setup............................................................................................10-10
2.5. UnixWare Base 2.1 Installation......................................................................................10-10
2.6. Installing Unix 2.1.1, 2.1.2 Updates ...............................................................................10-13
2.7. Installation UnixWare Patches.......................................................................................10-14
2.8. LAN Driver Configuration ...............................................................................................10-15
2.9. Interconnection Diagrams ..............................................................................................10-16
3. OMNI Installation.................................................................................................................10-18
3.1. OMNI Prerequisites........................................................................................................10-18
3.2. OMNI Installation Flow ...................................................................................................10-18
3.3. Verifying the OMNI Installation.......................................................................................10-26
4. Adding or Removing SS7 Communication Boards From the Installation Kit...............10-27
4.1. ConfigurePlatform ..........................................................................................................10-27
4.2. 999 Command ...............................................................................................................10-29
4.3. ConfigureNodes .............................................................................................................10-29
5. OMNI Configuration ............................................................................................................10-30
5.1. Starting and Stopping the OMNI Platform......................................................................10-30
5.1.1. Starting OMNI .........................................................................................................10-30
5.1.2. Stopping OMNI .......................................................................................................10-30
5.2. OMNI Configuration References....................................................................................10-30
6. ISMSC Installation...............................................................................................................10-30
6.1. Pre-installation Procedures............................................................................................10-31
Page 10-i
Chapter 10
Installation

6.2. Installation of the ISMSC Packages .............................................................................. 10-31

6.3. Configuration of the File /etc/hosts................................................................................ 10-38
6.4. Define a License on the SFE Machine .......................................................................... 10-38
6.5. Fixing the Password of the SMSC User ........................................................................ 10-39
6.6. Removing an Installed Package.................................................................................... 10-39
7. ISMSC Configuration ......................................................................................................... 10-39
7.1. NYSMSSFE Parameters ............................................................................................... 10-40
7.1.1. ALERT.................................................................................................................... 10-40
7.1.2. BILLING.................................................................................................................. 10-40
7.1.3. EXPIRATION ......................................................................................................... 10-41
7.1.4. INTERNAL_RETRY ............................................................................................... 10-41
7.1.5. RETRY ................................................................................................................... 10-41
7.1.6. RETRY_INTERVALS ............................................................................................. 10-41
7.1.7. SMART RETRIES .................................................................................................. 10-42
7.1.8. START_ON_BOOT................................................................................................ 10-42
7.2. Smart Retries ................................................................................................................ 10-42
7.2.1. Error Groups .......................................................................................................... 10-43
7.2.2. Default Translation of Errors .................................................................................. 10-48
7.2.3. Format and Examples of Rules.............................................................................. 10-51
7.2.4. Retry Profile Definitions.......................................................................................... 10-52
7.2.5. File Locations ......................................................................................................... 10-54
7.3. Configuring the NYSMSMAP Package ......................................................................... 10-54
7.3.1. Configuration of the MTP (OMNI) .......................................................................... 10-54
7.3.2. Configuration of the SCCP (OMNI) ........................................................................ 10-55
7.3.3. MML Configuration Procedure ............................................................................... 10-56
7.3.4. Configuration of the SCCP, TCAP and MAP Parameters in the SMSC Configuration
File(s) for GSM .................................................................................................... 10-60
7.4. Configuring the NYSMSIS41 Package.......................................................................... 10-64
7.4.1. Configuration of the MTP (OMNI) .......................................................................... 10-65
7.4.2. Configuration of the SCCP (OMNI) ........................................................................ 10-66
7.4.3. MML Configuration Procedure ............................................................................... 10-66
7.4.4. Configuration of the SCCP, TCAP and MAP Parameters in the ISMSC Configuration
File(s) for IS41-C ................................................................................................. 10-70
7.5. Disabling and Enabling the Mobile Originated Feature ................................................. 10-72
7.6. Configuring Status Report Request Receipt Messages................................................ 10-72
Page 10-ii

Chapter 10
Installation
7.6.1. Defining Receipt Languages...................................................................................10-73

7.6.2. Defining Receipt Messages ....................................................................................10-73
7.6.3. Authorization of Message Originators (Black and White Lists)...............................10-74
7.7. Enabling the FTP of Statistics Files ...............................................................................10-74
7.8. Post Installation Procedures ..........................................................................................10-75
8. ShortEmail Installation .......................................................................................................10-75
8.1. Installing the Email Server .............................................................................................10-75
8.2. Installing the Email EI ....................................................................................................10-77
8.3. Verifying the Email Server Installation ...........................................................................10-78
8.4. Fallback Instructions ......................................................................................................10-79
9. IPOS Installation..................................................................................................................10-79
9.1. Preparation for IPOS Installation ...................................................................................10-79
9.2. Installing the IPOS .........................................................................................................10-80
9.2.1. Installing the IPOS Server.......................................................................................10-80
9.2.2. Installing the IPOS Client ........................................................................................10-80
9.3. Configuring the IPOS .....................................................................................................10-80
9.3.1. Defining Server Parameters ...................................................................................10-81
9.3.2. Defining Message Parameters ...............................................................................10-81
9.3.3. Changing the Environment Language ....................................................................10-82
9.4. Verifying the IPOS Installation .......................................................................................10-83
10. Web Access Installation ...................................................................................................10-83
10.1. Installing the Web Server.............................................................................................10-83
10.1.1. Web Server Installation.........................................................................................10-84
10.1.2. Configuring Web ISMSC Routing .........................................................................10-85
10.2. Installing the Web EI ....................................................................................................10-86
10.3. Web Installation Verification Instructions .....................................................................10-87
10.4. Web Installation Fallback Instructions .........................................................................10-87
10.5. Configuring the Web Server Applications ....................................................................10-87
10.6. Multiple Language Support ..........................................................................................10-90
11. SMPP Installation..............................................................................................................10-90
11.1. Installing the SMPP......................................................................................................10-90
11.2. Verifying the SMPP Server Installation ........................................................................10-91
Page 10-iii
Chapter 10
Installation

12. Additional Configuration of EIs ...................................................................................... 10-92

12.1. Notification Transaction Logs...................................................................................... 10-92
12.2. Flow Control ................................................................................................................ 10-93
12.3. Target EI Routing ........................................................................................................ 10-93
12.4. Configuring MO Routing.............................................................................................. 10-94
12.4.1. Defining a Prefix-Routing Combination ................................................................ 10-94
12.4.2. Listing the Prefix-Routing Combinations .............................................................. 10-95
12.4.3. Deleting a Prefix-Routing Combination ................................................................ 10-95
12.4.4. Editing a Prefix-Routing Combination .................................................................. 10-96
12.4.5. Updating a Prefix-Routing Combination............................................................... 10-96
12.5. Configuring the MO Address Translation Feature....................................................... 10-96
12.6. Configuring Bi-directionality of EIs .............................................................................. 10-97
13. Configuration of TRILOGUE INfinity .............................................................................. 10-99
13.1. TRM Configuration ...................................................................................................... 10-99
13.1.1. Defining Connections to Additional TRMs............................................................ 10-99
13.1.2. Configuring TRM System Parameters ................................................................. 10-99
13.1.3. Message Notification Screen ............................................................................. 10-103
13.1.4. Notification List Expansion Box.......................................................................... 10-105
13.1.5. Notification Device Table ................................................................................... 10-107
13.1.6. Notification Class Table Definition ..................................................................... 10-108
13.1.7. SMS Text Template Definition Screen ............................................................... 10-109
13.2. Configuring MSU Parametersfrom TRILOGUE INfinity Release 6.01x................. 10-111
13.2.1. Service Level and Access Right Parameters ..................................................... 10-111
13.2.2. System Parameters............................................................................................ 10-113
13.3. Configuring MSU ParametersPrevious to TRILOGUE INfinity Release 6.01x ...... 10-114
13.3.1. Online Parameters ............................................................................................. 10-114
13.3.2. Offline Parameters ............................................................................................. 10-117
13.4. Configuring the Integrated Alarm Package (IAP) for the ISMSC .............................. 10-119
13.4.1. IAP Versions from 5.0 ........................................................................................ 10-119
13.4.2. IAP Versions Previous to 5.0.............................................................................. 10-119
13.4.3. ISMSC Configuration for the IAP ....................................................................... 10-120
13.5. Starting the Process from the TRM........................................................................... 10-120
Page 10-iv

Chapter 10
Installation
14. Verifying the ISMSC Installation....................................................................................10-121
List of Figures
10-1 CPU Board........................................................................................................................10-2
10-2 SS7 Board ConfigurationP/Ns 56-306-0302 and 56-306-0303 (Board 1, DTE
Configuration) .................................................................................................................10-9
10-3 Interconnection DiagramNon-redundant .....................................................................10-16
10-4 Interconnection DiagramRedundant ...........................................................................10-17
10-5 Server Options Dialog Box..............................................................................................10-81
10-6 Message Setup Dialog box .............................................................................................10-82
10-7 SMSC Address Manipulation Tool Screen .....................................................................10-94
10-8 SMSC Routing Table Manipulation Tool Screen ............................................................10-95
10-9 Routing Manipulation Commands...................................................................................10-95
10-10 Sample Routing Table Screen........................................................................................10-95
10-11 SMSC Address Manipulation Tool Screen .....................................................................10-97
10-12 SMSC Translation Table Manipulation Tool Screen.......................................................10-97
10-13 Message Notification Expansion Box ...........................................................................10-104
10-14 Notification List Expansion Box ....................................................................................10-105
10-15 Notification Device Table ..............................................................................................10-108
10-16 Notification Class Table ................................................................................................10-109
10-17 SMS Text Messages Screen ........................................................................................10-110
List of Tables
10-1 Jumper Settings................................................................................................................10-3
10-2 Switch Settings .................................................................................................................10-4
Page 10-v
Chapter 10
Installation

10-3 BIOS Settings................................................................................................................... 10-4

10-4 SS7 Board Configuration ................................................................................................. 10-9
10-5 Device Terminations ...................................................................................................... 10-10
10-6 Disk File System for 4G Disk ......................................................................................... 10-12
10-7 Smart RetriesGSM Default Error Translation Rules................................................... 10-48
10-8 Smart Retries - IS-41C Default Error Translation Rules ................................................ 10-49
10-9 Server Options Dialog Box Controls .............................................................................. 10-81
10-10 Message Setup Dialog Box Controls ............................................................................. 10-82
10-11 Web AccessGeneral Parameters............................................................................... 10-87
10-12 Web AccessAbuse Prevention Parameters for Mass Market Application.................. 10-89
10-13 Notification Transaction Log Parameters....................................................................... 10-93
10-14 Flow Control Parameters ............................................................................................... 10-93
10-15 Target EI Routing Parameters ....................................................................................... 10-94
10-16 SMS Message Text Symbols ....................................................................................... 10-111
Page 10-vi

1.
Chapter 10
Installation
Overview
This chapter provides a description of the steps necessary to install the OMNI soft
platform and the ISMSC software on the ISMSC platform, the IMU installation,
configuration and customization of the system, the SS7 installation, and
installation of all EIs. Also included is the configuration of the TRM, MSU, and
IAP, applicable when TRILOGUE is one of the EIs.
Installation of the ISMSC software should be performed by a tier-3 technician
with broad-based UNIX knowledge, familiarity with SS7 and telecommunications,
and a solid understanding of the OMNI architecture and its components.
2.
Installation
2.1.
Pre-installation Checklist
Verify that the following are prepared before beginning the installation:
2.2.
Floppy drive
DAT tape
CD ROM drive connected to SCSI connector on CSI ID other than 0
SCO UnixWare Application server CD ROM 1 of 2 for Release 2.1
SCO UnixWare Installation diskette for Release 2.1.2
SCO UnixWare Host Bus Adapter (HBA) drivers for Release 2.1.2
License for Application Server
DAT tape that includes INTEL 100 PRO driver and UNIX patches
OMNI installation kit
SMSC application installation kit
CPU Board Configuration

When configuring the CPU board, refer to Figure 10-1.
WARNING: There is an Electrical Shock Hazard when servicing this system.
Before opening system cabinets or attempting to remove or adjust
boards, components, or other electrical subassemblies, always verify
that power is turned off.
CAUTIONS: These modules contain Electrostatic Discharge Sensitive (ESDS)
components. Improper handling may damage components. When
working with modules, always attach an ESD wrist strap.
Page 10-1
Chapter 10
Installation

Do not remove a module from its protective wrapper or from the

module drawer unless you have taken ESD precautions. When
installing or removing modules, place them component-side up, on a
grounded, static-free surface. Put the module on a special ESD foam
pad if available. Do not slide the modules over a surface of any kind.
NOTES:
During disassembly procedures, be sure to retain all hardware for use

during assembly procedures.
Before installing a disk or board or other electrical component, always
verify that required jumpers and DIP switches have been properly set.
23
JP2
SW4
SW3
SW2
JP4
JP6
JP15
JP12 JP13
ON
OFF
JP19
JP26
JP25
JP24
JP14
JP17 JP18
SW1
JP5
INSTALLED
NOT INSTALLED
IDG00953
Figure 10-1: CPU Board
2.2.1.
Installing the CPU Board

To install the CPU board:
1.
Verify that the jumper settings are configured as listed in Table 10-1.
2.
Verify that the switch settings are configured as listed in Table 10-2.
3.
Install the CPU board onto the passive backplane in the chassis.
4.
Attach all the necessary peripheral devices to the appropriate headers on the
surface of the SBCKeyboard Header, Mouse Header, COM2 Header.
5.
Attach all the necessary peripheral devices to the appropriate connectors on

the I/O bracket of the SBCCOM1 if needed.
6.
Power on the system.
Page 10-2

7.
Chapter 10
Installation
During bootup verify that the BIOS version is 4.06.1.2f. If it is another

version (4.06.1.2c):
a.
Shut down the unit being tested.
b.
Change the position of switch3 to ON.
c.
Insert the TMI BIOS for P-II 4.06.1.2f diskette to the floppy drive.
d.
Power on again the unit being tested.
e.
Verify that during boot the sentence CPU switch3 is on

Default Configuration loaded appears.
f.
Type a:\phlash and press <Enter> at the DOS OS prompt.
g.
Change back the position of switch3 to OFF. When the message

Press any key to restart the computer
appears, press any
key to reboot. (If the computer does not restart, switch off the power
and turn it back on.)
8.
When the message Press <F2> to enter Setup appears, press <F2>.
9.
Change the settings to the values presented in Table 10-3. There are six
menu selections across the top of the screen. Follow the directions on the
bottom of the screen to select menus and make changes Only the values that
need modification are presented. Use the <+> and <-> keys to scroll
between options.
10.
Press <Esc> to exit the setup routine. The CPU should boot Unixware from
the hard drive.
Table 10-1: Jumper Settings

Jumper
Setting
Description
JP2
2-3
RS232 Serial 2 Configuration
JP4
1-2
Reserved. Do not alter
JP5
2-3
JP6
2-3
JP12
None
Bus Core Ratio 2/9

CPU Speed 300 MHz
JP13
1-2
Bus Core Ratio 2/9

CPU Speed 300 MHz
JP14
1-2
JP15
None
Page 10-3
Chapter 10
Installation

Jumper
Setting
Description
JP17
None
Bus Core Ratio 2/9

CPU Speed 300 MHz
JP18
1-2
Bus Core Ratio 2/9

CPU Speed 300 MHz
JP19
None
JP24
None
Host Bus Speed 66.6 MHz
JP25
None
JP26
1-2
Host Bus Speed 66.6 MHz
Table 10-2: Switch Settings

Switch
Setting
Description
SW1- 1 Default Monitor Type
On
Color
SW1- 2 On Board ROM Access
Off
Flash memory mode enabled
SW1- 3 CMOS RAM
Off
Normal operation
SW1- 4 Configuration Ports
Off
Map ports to I/O address 270/271
Table 10-3: BIOS Settings

BIOS Setup Item
Setting
MAIN
Adjust the time correctly
Diskette A / B
1. 44 / Disabled
IDE Adapter
NONE (to all). Select NONE

manually; do not accept the default
of None.
Type
None
Cache Memory
Memory Cache
Page 10-4
Enabled

Chapter 10
Installation
BIOS Setup Item
Setting
Cache System
Write Protect
Video BIOS Area
Write Protect
Cache Base 0512K

512K640K
Write Back
Write Back
Cache Extended Memory Area
Write Back
Cache A000-EFFF
Disabled (all regions)
Boot Options
Enabled
Summary Screen
Enabled
Floppy Check
Disabled
Quiet Boot
Disabled
POST Errors
Enabled
Keyboard Options
Numlock
Auto
Key Click
Disabled
Keyboard AutoRepeat Rate
30/ sec
Repeat Delay
1/ 2 sec
ADVANCED
Integrated Peripherals
Serial Port A
Enable
I/O Address
3F8
Interrupt
IRQ4
Serial Port B
Enable
I/O Address
2F8
Interrupt
IRQ3
Parallel Port
Disabled
Page 10-5
Chapter 10
Installation

BIOS Setup Item
Setting
Floppy Disk Controller
Enabled
Base I/ O Address
Primary
Local Bus IDE Adapter
Disabled
Adaptec Ultra SCSI Adapter
Enabled
SCSI Adapter Frequency
40 MHz
Advanced chipset control

DRAM Speed
60 Ns
ECC/ Parity Config
ECC Gen & Correct
Enabled Memory Gap
Hole at 15Mb-16Mb
Release E000
Disabled
DMA Aliasing
Enabled
8- / 16- Bit I/ O Recovery
4.5 / 4.5
ISA Bus Speed PCI
Clock / 4
Watchdog Timer Status
Disabled
Watchdog Timer Delay
1.2
PCI CONFIGURATION
PCI IRQ Line 1
2
3
4
9
Disable
11
14
ISA Graphics Device Installed
No/yes ( depends if installed)
PCI/ PNP ISA UMB / IRQ Exclusion
Available (All regions and IRQs)
PS/ 2 Mouse
Disabled
Onboard Speaker
Enabled
Use Multiprocessor Specifications
1.1
CPU BIOS Update
Enabled
Page 10-6

Chapter 10
Installation
BIOS Setup Item
Setting
Plug & Play O/ S
No
Secured Setup Configurations
Yes
Large Disk Access Mode
Other
(for Unixware) (for DOS)
SECURITY
Supervisor / User Password
Clear
Password on Boot
Disable
Fixed Disk Boot Sector
Normal
Diskette Access
Supervisor
Virus Check / System Backup Reminder
Disabled
POWER
Power Savings
Disabled
Standby / Auto Suspend Timeout
Off
Hard Disk / Video Timeout
Disabled
Resume on Modem Ring / Time
Off
Advanced Options
IRQ 1
Enable
IRQ 315, SMI, NMI
Disabled (all IRQs, SMI, NMI)
BOOT
1. diskette drive
2. hard disk drive
3. ATAPI CDROM drive
SERVER
Console Redirect Port
Disabled
Console Redirect Baud Rate
9600
Page 10-7
Chapter 10
Installation

BIOS Setup Item
Setting
EXIT
Exit saving changes
2.2.2.
SCSI Adaptec Adapter Setup

To configure the SCSI setup:
1.
After exiting the BIOS setup, the system reboots. When the message Press
Ctrl and A to enter SCSI utility appears, press <Ctrl>+<A>.
2.3.
2.
Press <F6> to use the default settings.
3.
Select Configure/View Host Adapter Settings and press <Enter>.
4.
Select Advanced Configuration Options and press <Enter>.
5.
Verify that the Extended Bios translation for Dos drives > 1GB to set to
DISABLED.
6.
Press <Esc> to return to the SCSI Utility Main Menu.
7.
Select SCSI Disk Utility and press <Enter>.
8.
Verify that the Adapter recognizes the following:

x
Hard Disk Drive (ID 0)
DAT/ Drive (ID 3)
Host Bus Adapter (ID 7 )
9.
Press <Esc>.
10.
Save and reboot.
SS7 Link Board Configuration

This section describes the configuration of the SS7 Link Boards, P/N 56-306-0302
and P/N 56-306-0303.
2.3.1.
SS7 Link Board Hardware Configuration

Each SS7 board is configured individually.
To configure the SS7 board:
1.
Jumpers J7 and J8 are configured as presented in Figure 10-2 on all SS7

boards.
2.
Jumpers J9 and J10 are configured opposite to the switch. If the switch is
DCE, the DTE jumpers are jumpered as illustrated in Figure 10-2. If the
switch is DTE, the DCE jumpers are jumpered.
Page 10-8

3.
Chapter 10
Installation
The address switch (S1) is configured as presented in Table 10-4. The

configuration is unique for each board. Start with Board 1 for the first
board, and continue with Board 2, Board 3, Board 4.
Table 10-4: SS7 Board Configuration

Board
IRQ # (J7/J8)
I/O Switch (S1)
In order of
installation
The listed jumper is

jumpered
off
off
on
on
on
off
15
off
off
on
on
off
on
off
off
on
off
on
on
10
off
off
on
off
on
off
DGM&S
DCE
DTE
J10
C30 - V35B
1
J4
PORT1
DSP
C.S
J5
PORT
IRQ
IRQ
15 12 11 10
9 3 4 5 6 7
U29
R3
0N
S1
1
J7
J8
ADDR
J9
DTE
DCE
IDG00971
INSTALLED
NOT INSTALLED
Figure 10-2: SS7 Board ConfigurationP/Ns 56-306-0302 and 56-306-0303

(Board 1, DTE Configuration)
Page 10-9
Chapter 10
Installation
2.3.2.

SS7 Link Board Software Configuration

The procedure described in this section is usually performed automatically during
installation. It is included here in case it must be performed in other
circumstances.
To configure the software of the SS7 board:
2.4.
1.
Login as root.
2.
Type the command dcu and press <Enter>.
3.
Navigate to SW Device and Miscellaneous.
4.
Move to the line containing mpad and add * to the () using the space bar,
then press <Enter>.
5.
To add new entries move the cursor to the mpad line and press <F5>-new.
6.
Enter the card configuration and press <F10> to apply.
7.
Repeat step 5 and step 6 for each card.
8.
Press <F10> to apply and return.
9.
Press <Enter> and then select Return to DCU Main Menu.
10.
Select HW Device Configuration. Verify that the cards appear at the end of
the list.
11.
Press <F10> to return.
12.
Select Apply changes and Exit DCU.
13.
Type /etc/conf/bin/idbuild-B to rebuild the kernel.
14.
Reboot the system by typing shutdown y i6 g0. After rebooting OMNI

comes up and port_daemon should successfully load the boards.
Device Terminations Setup

Verify that the various devices are terminated as defined in Table 10-5.
Table 10-5: Device Terminations
2.5.
Device
Termination
Internal disk
No
External Device
Yes
Internal DAT
Yes
UnixWare Base 2.1 Installation

To install the UnixWare base 2.1:
1.
Page 10-10
Insert the Application Server CD-ROM 1 of 2 into the CD drive.


Chapter 10
Installation
2.
Insert the diskette Installation Diskette 2.1.2 into the floppy drive.
3.
Boot the computer.
4.
Press <Enter> at the welcome screen.
5.
Select the Keyboard type: US-ASCII (default).
6.
Enter the License No of application server in the field of Serial No.
7.
Enter the License Code of application server in the field of Activation Key,
and press <F10> to apply.
8.
Press <Enter> (continue installation) to approve installation.
9.
When prompted to install Host Bus Adapter, insert the 2.1.2 HBA diskette
and press <Enter>.
10.
When prompted to install another HBA Diskette, take out the 2.1.2 HBA
diskette and select Continue Installation.
11.
When prompted to enter DCU, select Continue Installation. The system

hardware drivers are now loaded.
12.
Select Install from CDROM , then select YES to confirm.
13.
If prompted
Installation.
14.
Select Use entire disk for UnixWare (Erase all partitions).
15.
Type ismsc1/ismsc2 for System Node Name. This name can be changed
later.
16.
Verify the Date details and select the time zone. (Press <F2> to view the
options.) Select Daylight Savings and press <F10> to apply the changes.
17.
18.
Select View/change package selection.
19.
Select All by pressing <F5> and then disable the following options (by
placing the cursor on the item and pressing the <spacebar>):
Destructive/Nondestructive,
select
Perform
Destructive
Basic: Additional Platform Utilities, OS Multiprocessor Support

Networking: Netware Networking, Netware
Integration Kit, Network Information Services
Unix
Client,
Netware
20.
Add (Enable) on UnixWare documentation: Desktop & Owner handbooks.
21.
Press <Page Down> for more and delete the following option:
Advanced: Access Control Lists, Auditing.
22.
Press <Enter> to return
23.
Select View or change disk configurations.
24.
Select File Systems. Modify the following slices as presented in

Table 10-6.
Page 10-11
Chapter 10
Installation
25.

Verify that the value of the Currently Used Size is equal or less than the
value of the Available Size (4360). If not, reduce the /root slice until they
are equal.
Table 10-6: Disk File System for 4G Disk

Slice Name
Slice Type
Size
/Root file system
vxfs
1374
/dev/swap
slice
512
/stand
bfs
25
/usr
off
/home
vxfs
/dev/dump
off
/var
vxfs
/home2
off
/tmp
vxfs
128
/dev/volprivate
slice
/var/tmp
off
ALTS TABLE
slice
2000
120
40
26.
Press <F10> to apply, and then select Return to previous menu.
27.
Select Accept all settings and install now . CDROM installation takes
about 30 min. In the case of Dual CPU the following message appears:
Choose Platform Support Module: Intel MP Specification.
This should be detected automatically by the system, If
not, contact your system administrator.
28.
When prompted to insert the HBA diskette again, insert the HBA diskette
and press <Enter>.
29.
Remove the CD and the HBA diskette when the installation is finished.
30.
Press <Enter> to reboot.
NOTE:
Press <Esc> to end rebuilding the kernel after it had been built twice.
31.
After the reboot, verify the UnixWare version: UnixWare 2.1 for the
Intel386 family.
32.
Select Cancel this utility without making changes, On networking.
Page 10-12

33.
Chapter 10
Installation
For TCP/IP parameters select the IP address:

ISMSC1
192.9.200.203
ISMSC2
192.9.200.205
34.
For languages select: Country: default, Additional support: install support

for relevant countries only.
35.
Press <Enter> twice to Apply.
36.
Select 4, No mouse in the system.
37.
Type the Owners name omni.
38.
Type the Login id omni.
39.
Type the Owners number 201, then press <Enter> to confirm.
40.
41.
Type the password omni. Press <Enter> to confirm.
42.
Leave the root password undefined. Press <Enter> to confirm.
43.
Type the system password omni. Press <Enter> to confirm. The login
desktop screen opens.
44.
Switch to the console mode by pressing <Ctrl> and <Alt> and then
<SysRq> and <P> at the same time, keeping <Ctrl> and <Alt> pressed.
45.
Login as root.
46.
Delete omni from being a desktop user by typing /usr/X/adm/dtdeluser

omni and press <Enter>.
2.6.
47.
Disable the UnixWare desktop graphical login by typing disable_glogin

and press <Enter>.
48.
Delete root from having a password by typing passwd d root and press
<Enter>.
49.
Reboot the system by typing cd/ ;shutdown -y -g0 -i6.
Installing Unix 2.1.1, 2.1.2 Updates

NOTE:
The installation takes about 20 minutes.
To install the Unix 2.1.1 and 2.1.2 updates:

1.
Insert the Application Server CD No. 1 of 2 into the CD drive.
2.
Switch to the console by pressing <Ctrl> then <Alt> and then <SysRq> and
<P> at the same time, keeping <Ctrl> and <Alt> pressed.
3.
Login as root.
Page 10-13
Chapter 10
Installation
2.7.

4.
Type the command /usr/bin/installcd, then press <Enter> to confirm.
5.
Press <Enter> for No Optional Products. The update is automatically

installed.
6.
Enter the license code and activity key for Internet server. (This is done
automatically, just press <Enter> three times. Warning messages for ipc
bind may appear on the console. Ignore them.) Select Apply.
7.
Packages for Internet Faststart Set, select No on all options. Select Apply.
8.
When asked for strong Encryption, press <Enter> to skip.
9.
Reboot the system by typing cd / ;Shutdown -y -g0 -i6.
10.
After the reboot you should see UnixWare 2.1.2 for the Intel386 family.
Installation UnixWare Patches

NOTE:
This installation is performed on the console only.
To install the Unixware patches:

1.
Insert the patches tape labeled Patches for UNIXWARE 2.1.2 into the DAT
tape drive.
2.
Login as root
3.
Go down to run-level 1 by typing:

# cd /
# shutdown -y -g0 -i1
4.
Login as root.
5.
Type # pkgadd -d /dev/rmt/ctape1
6.
Press <Enter> to select go, and continue installation.
7.
When prompted Select package(s) you wish to process (or

'all' to process all packages). (default: all) [?,??,quit]:
specify the packages in the following order:
Page 10-14
ptf3019
ptf3052
ptf3131
ptf3209b
ptf3280
ptf4001b
ptf4024

Chapter 10
Installation
8.
Press <Enter> or Approve Installation whenever required during the

installation flow.
9.
When prompted Select package(s) you wish to process (or

'all' to process all packages). (default: all) [?,??,quit]:
specify the packages in the following order:
x
erg500831
erg710649
uw_mxt
10.
Press <Enter> or Approve Installation whenever required during the

installation flow.
11.
When prompted What is the IP Address of TRM [192.9.200.5]?

enter the IP address of the TRM 192.9.200.6.
12.
When prompted Insert a cartridge into Tape Driver1, Type

[go] when ready, or [q] to quit:, press <Q> to end the installation.
13.
To rebuild the kernel, enter the comands

/etc/conf/bin/idbuild B
shutdown y g0 i6
14.
After reboot of system log in as root and change the INIT state to single
user mode by entering following commands:
cd /
shutdown -y -g0 -i1
15.
Remove the DAT tape and reboot the system by entering:

cd / ;Shutdown -y -g0 -i6.
2.8.
LAN Driver Configuration

To install the LAN driver configuration:
1.
Login as root.
2.
Invoke the NIC Support Utility by typing /usr/sbin/niccfg.
3.
Select Accept All Entries and Approve (yes). The Utility will dynamically
load the eeE driver into the UnixWare kernel.
4.
Configure the TCP/IP by typing /etc/confnet.d/configure -i.
5.
Enter the number of the device (1).
6.
Enter the local IP Host name (ismsc1/ismsc2).
7.
Enter the local IP Address.
8.
Enter Yes for Ethernet options.
9.
Reboot the system.
Page 10-15
Chapter 10
Installation
2.9.

10.
Connect a LAN cable from the INTEL LIM board to a HUB (configured to
192.9.200.151).
11.
Type ping 192.9.200.151 and press <Enter> to verify the network

configuration.
Interconnection Diagrams
This section presents interconnection diagrams for the following configurations:
x
Non-redundant (Figure 10-3)
Redundant (Figure 10-4)

SS7 LINK PANEL
1
SLM1
TO HSBN
TO SWITCH
BOX
SLM2
SLM3
SLM4
LAN 1
COM1
MONITOR
COM2
KBD
ISMSC
PS/2 MOUSE
POWER CABLE
SCSI
RS 232
OPTIONAL
RS232 PANEL
IDG00961
Figure 10-3: Interconnection DiagramNon-redundant
Page 10-16

Chapter 10
Installation
MTC PANEL
POWER CABLE
OPTIONAL
MONITOR
TO SWITCH
BOX
RS232
ISMSC
KBD
COM2
PS/2 MOUSE
LAN 1
TO HSBN
SLM1
COM1
SCSI
SLM2
SLM3
SLM4
8
SS7 LINK PANEL
SS7 LINK PANEL
8
SLM2
SLM3
KBD
SLM4
SCSI
LAN 1
COM1
MONITOR
TO SWITCH
BOX
SLM1
TO HSBN
ISMSC
PS/2 MOUSE
COM2
RS232
POWER CABLE
IDG00963
Figure 10-4: Interconnection DiagramRedundant
Page 10-17
Chapter 10
Installation

3.
OMNI Installation
3.1.
OMNI Prerequisites
The installation of both UNIX and any required patches are system prerequisites
for OMNI, and consequently must be performed prior to MAP EI and SFE
installation (on both computers in large configuration ISMSC). In HLR
Interrogation the software is supplied with the OMNI DAT.
NOTE:
3.2.
Before installing the OMNI package, verify that the SS7 link boards
are configured as described in Paragraph 2.3. and are inserted into the
ISA slots.
OMNI Installation Flow

This example is for 1 drawer with 1 SS7 board. If 2 SS7 boards are needed, follow
the installation procedure for one board and configure the second board using
configurePlatform and configureNodes utilities. (Refer to Paragraph 4.1. and
Paragraph 4.3.) This package is installed on the MAP/EI drawer of the ISMSC, in
large ISMSC configurations.
To avoid bypass file system space problems during installation, the packages
should be transferred from the installation tape to a temporary directory prior to
their installation. The packages must then be installed and the temporary directory
removed.
To install OMNI:
1.
Insert a cassette containing the OMNI packages into the tape unit.
2.
Log in as root.
3.
Type the following commands, pressing <Enter> after each one:

mkdir -p /home/omnipkgs/
pkgtrans /dev/rmt/ctape1 /home/omnipkgs all
pkgadd -d /home/omnipkgs
(If OMNI was previously installed, the following prompt appears:

Insert a cartridge tape into Cartridge Tape Drive.)
Type [go] when ready, or [q] to quit:
4.
Press <Enter> for the default (go). A message similar to the following
appears:
NOTE:
Messages vary with each release. The following is an example.
NOTE:
The package listed below, OMNI-C7, refers to GSM systems.
Installation in progress. Do not remove the cartridge.
Page 10-18

Chapter 10
Installation
The following packages are available:

1 BASE-CCS
CCS OMNI Base Configurations
(i386) GSM-5.02-1
2 OMNI
OMNI SS#7 Platform System

(OMNI-M7-UPC-5.02) M7-UPC-5.02
3 OMNI-C7
OMNI SS#7 Platform C7 Drivers
4 OMNI-GSM
OMNI SS#7 Platform GSM Mobile Appl
5 OU-1
OMNI SS#7 Platform System Update

(OMNI-M7-UPC-5.02) M7-UPC-5.02.1
6 OUC7-1

(OMNI-M7-UPC-5.02) M7-UPC-5.02.1
7 OUGSM-1
(OMNI-M7-UPC-5.02) M7-UPC-5.02.1
10 SPRTM1
Package for update portmon

(i386) Update portmon
... 6 more menu choices to follow;

Press <RETURN> for more choices, <CTRL-D> to stop display:
5.
Press <Enter> to continue. The following appears:

11 SS7-AITO
Auto Init & Terminate OMNI
(m88k) GSM-5.02-1
12 SS7-BIN
CCS OMNI Applications
(m88k) GSM-5.02-1
13 SS7-CSL
CCS Compresed System Logs
(m88k) GSM-5.02-1
14 SS7-DATA
CCS OMNI Data Files
(m88k) GSM-5.02-1
15 SS7-MISC
CCS OMNI Utilities
(m88k) GSM-5.02-1
16 SS7-OMNI
CCS OMNI Base Installation
(m88k) GSM-5.02-1
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,quit]
6.
Press <Enter> to select all packages. The following appears:
Page 10-19
Chapter 10
Installation

PROCESSING:
Package: CCS OMNI Base Configurations (BASE-CCS) from
</dev/rmt/ctape1>.
CCS OMNI Base Configurations
(m88k) GSM-5.02-1
Using </> as the package base directory.
----------------------------------------------------Copyright 1996 Comverse Technology, Inc
All Rights Reserved
----------------------------------------------------[ Notice ] User [ omni ] Exists In /etc/passwd
[ Notice ] User [ efrat ] Does Not Exists In /etc/passwd,
Appended...
........ --------------------------------------........
Default Configuration
........ --------------------------------------........ Number Of CEs

........ AP Address
........ TRM Address
: 2
: 192.9.200.5
: 192.9.200.5
........ SS7 Board Type
: c30c7
........ Number Of Ethernet Cards

........ CE 1 Name
........ CE 1 Address
: 1
: alpha
: 192.9.200.15
........ Nof Boards On CE 1
: 1
........ Ethernet alias Of CE 1

........ CE 2 Name
........ CE 2 Address
: alpha
: beta
: 192.9.200.16
........ Nof Boards On CE 2

........ Ethernet alias Of CE 2
: 1
: beta
Do you want to use default configuration (yes/no)?
7.
Type No and press <Enter>.

The following appears:
How many Computing Elements (max=2) [ 2 ] ? (1 for Single,
2 for Redundant)
Type 1 for single.

8.
Page 10-20

Chapter 10
Installation
How many Ethernet Alias per CE? (max=2) [ 1 ] ?
Type 2.
9.

What is the name of CE1 [ smsc1 ] ?
Type smsc1.
10.

What is the IP Address of AP [ 192.9.200.6 ] ?
Type 192.9.200.6 (if not specified otherwise).

11.

What is the IP Address of TRM [ 192.9.200.6 ] ?
Type 192.9.200.6 (if not specified otherwise)

12.

What is the IP Address of CE1 [ 192.9.200.203 ] ?
Type 192.9.200.203 (If not specified otherwise)

13.

How many boards on CE1 smsc1 [ 1 ] ?
Type 2.
14.

What is the Board Configuration for boards [ b30c7 ] ?
Press <Enter> (or c30c7 for CCITT, c30a7 for ANSI, c30ch7 for Chinese,
c30j7 for Japanese). The following appears:
........
Default Configuration
........ Number Of CEs
: 1
........ AP Address
: 192.9.200.6
........ TRM Address
: 192.9.200.6
........ SS7 Board Type
: b30c7
........ CE Name
: smsc1
........ CE Address
: 192.9.200.203
........ Nof Boards
: 2
Is this the configuration you want (yes/no) [yes] ?
15.
Press <Enter>. The following appears:

........ Select number between 1-1
........
CCS Host Names For 1 CEs
....... [ 1 ] - First Host [ smsc1 ]

Enter your choice for this CE :
Page 10-21
Chapter 10
Installation
16.

Type 1 and press <Enter>. The following appears:

CENAME=smsc1
CEADDR=192.9.200.203
[ Trace ] Changing Unit Name [ uname -S smsc1 ]
[ Trace ] Changing Unit Ip Address [ ifconfig INTEL
192.9.200.203 ]
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
Installing CCS OMNI Base Configurations as <BASE-CCS>
## Executing preinstall script.
[ verifying class <BaseCCS> ]
[ verifying class <OmniCCS> ]
## Installation of part 1 of 1 is complete.
## Executing postinstall script.
Installation of CCS OMNI Base Configurations (BASE-CCS) was
successful.
PROCESSING:
Package: OMNI SS#7 Platform System (OMNI) from
</dev/rmt/ctape1>.
OMNI SS#7 Platform System
Using </> as the package base directory.
Copyright 1992-1996 DGM&S Dale, Gesek, McWilliams, &
Sheridan, Inc
All Rights Reserved
Installation of this package will require a kernel rebuild.
Installing OMNI SS#7 Platform System as <OMNI>
## Installing part 1 of 3.
/home/omni/bin/almsvr
/home/omni/bin/nm
/home/omni/bin/oos
Page 10-22

Chapter 10
Installation
/home/omni/bin/pm
/home/omni/bin/tap
/home/omni/locale/english/omni.cat.m
/home/omni/man/generic/manual.man/cat8/omni_events.8
/home/omni/man/generic/manual.txt/txt8/omni_events.8q
/home/omni/man/online/adr/adg.ps.Z
/home/omni/man/online/ao/ao.ps.Z
/home/omni/man/online/api/docOMNIa.ps.Z
/home/omni/man/online/inst/inst.ps.Z
/home/omni/man/online/opr/docOMNIo.ps.Z
/home/omni/man/online/opr/opr.ps.Z
## Installing part 2 of 3.
/home/omni/bin/CheckProcess
/home/omni/bin/DFcat
/home/omni/bin/DFconvert
/home/omni/bin/DFcopy
/home/omni/bin/DFdaemon
/home/omni/bin/DFdir
/home/omni/bin/DFls
/home/omni/bin/DFtouch
/home/omni/bin/DFunlink
/home/omni/bin/GetState
/home/omni/bin/MonControl
/home/omni/bin/OmniRunTimeEnv
/home/omni/bin/Qerror
/home/omni/bin/Qfirst
/home/omni/bin/Qlimit
/home/omni/bin/Qremove
/home/omni/bin/Qstat
/home/omni/bin/Qstruct
/home/omni/bin/Restart
/home/omni/bin/RestartBrd
/home/omni/bin/ScrubCpt
/home/omni/bin/Start
/home/omni/bin/Terminate
Page 10-23
Chapter 10
Installation

/home/omni/bin/TxtControl
/home/omni/bin/almPRI
/home/omni/bin/almSS7
/home/omni/bin/almcon
/home/omni/bin/almconHP
/home/omni/bin/almdis
/home/omni/bin/almdiskmon
/home/omni/bin/almser
/home/omni/bin/c30boot.bin
/home/omni/bin/cetdisplay
/home/omni/bin/convsev
/home/omni/bin/diskmon
/home/omni/bin/dly
/home/omni/bin/dmp
/home/omni/bin/dr
/home/omni/bin/dumbMML
/home/omni/bin/dumpomni
/home/omni/bin/evt
/home/omni/bin/getGroup
/home/omni/bin/getUser
/home/omni/bin/gofer
/home/omni/bin/guiserver
/home/omni/bin/ln_daemon
/home/omni/bin/log
/home/omni/bin/log2ascii
/home/omni/bin/lomstat
/home/omni/bin/man_linkages
/home/omni/bin/meas
/home/omni/bin/mon
/home/omni/bin/monitor
/home/omni/bin/mpad_maint
/home/omni/bin/mr
/home/omni/bin/mrs
/home/omni/bin/ms
/home/omni/bin/ms_stats
Page 10-24

Chapter 10
Installation
/home/omni/bin/muxdump
/home/omni/bin/pcdbg
/home/omni/bin/pop
/home/omni/bin/port_daemon
/home/omni/bin/portmon
/home/omni/bin/prn
/home/omni/bin/pup
/home/omni/bin/rsm
/home/omni/bin/sig
/home/omni/bin/slan
/home/omni/bin/slandisp
/home/omni/bin/t30boot.bin
/home/omni/bin/tap_print
/home/omni/bin/termhandler
/home/omni/bin/txt
/home/omni/bin/v35conf
/home/omni/bin/watch
/home/omni/bin/xman
/home/omni/locale/english/omni.cat
/home/omni/severityLevel/sev.18
/home/omni/conf/Devices.awk
/home/omni/conf/configuration.sh
/home/omni/conf/configure.sh
/home/omni/conf/configureNodes
/home/omni/conf/configurePlatform
/home/omni/conf/go.omni.GENERIC
/home/omni/conf/mkceconf.1CE.sh
/home/omni/conf/mkceconf.nCE.sh
export LD_LIBRARY_PATH
[ Notice ] OMNI User Already In [ /etc/passwd ]
[ Notice ] Comverse User Already In [ /etc/passwd ]
[ Notice ] Shared memory is allready set to 10478000
[Notice ] Changing Limitation parameters to 0x7FFFFFFF
Page 10-25
Chapter 10
Installation

[ Notice ] Go script [/home/ss7/utils/go] Already installed

!!!
UX:idbuild: INFO:
The unix kernel will be rebuilt now.
This will take some time. Please wait.
UX:idbuild: INFO: The unix kernel has been rebuilt.
System SHOULD be rebooted when you finished Install all
instances
17.
Remove the DAT cassette from the tape drive before rebooting.
18.
Press <Enter> to reboot. After the system has rebooted the following
appears:
Welcome to UnixWare 2.1.2
The systems name is smsc1.
Console login:
19.
Type omni and press <Enter>. The following appears:

Password:
20.
Type omni and press <Enter>. The following appears:

UnixWare 2.1.2
smsc1
Copyright 1996 The Santa Cruz Operation, Inc. All Rights
Reserved.
Copyright 1984-1995 Novell, Inc. All Rights Reserved.
Copyright 1987, 1988 Microsoft Corp. All Rights Reserved.
U.S. Pat. No. 5,349,642
Last login: Tue Sep 8 09:57:44 1998 on pts002
[smsc1] [/home/omni] 1 >
3.3.
Verifying the OMNI Installation

To verify the OMNI installation:
1.
At the login prompt type omni.
2.
At the password prompt type omni. The following message appears:

[smsc1][/home/omni] 1 >
3.
Change the directory to /home/ss7/bin by entering:

cd /home/ss7/bin
The following message appears: [smsc1][/home/ss7/bin] 2 >
Page 10-26

4.
Chapter 10
Installation
If the upgrade procedure document contains the checksum of the file, run
checksum to verify the software integrity by entering: usr/bin/sum mapi
A message of the following type appears:
58328
9659
mapi
These numbers represent the checksum of the current OMNI version. The
message appearing should correspond with those supplied in the sitespecific installation DAT.
4.
Adding or Removing SS7 Communication Boards

From the Installation Kit
To add SS7 boards to the ISMSC:
4.1.
1.
Copy the files go.omni, cestart.201, and the db files to a temporary location.
2.
Turn off the power.
3.
Configure the board(s) as described in Paragraph 2.3.1. If there are two

boards already installed, use Board 3 for the next board to be installed.
4.
Insert the board in the next available ISA slot.
5.
Turn on the power.
6.
Perform configurePlatform (Paragraph 4.1.) or the command 999 procedure

(Paragraph 4.2.).
7.
Perform configureNodes (Paragraph 4.3.).
ConfigurePlatform
configurePlatform is used for a configuration of one or two boards. To add a third
or fourth board, refer to Paragraph 4.
After adding or removing SS7 boards:
1.
At the login prompt type omni.
2.
At the password prompt type omni.
3.
Enter su.
4.
Enter cd /home/omni/conf.
5.
Enter ./configurePlatform.
The following message appears:
CONFIGURE OMNI PLATFORM
*********** CONFIGURATION VARIABLES ****************
----- OMNI_HOME = /home/omni
----- HOME = /home/omni
Page 10-27
Chapter 10
Installation

Continue with CONFIGURE PLATFORM procedure, (Enter yes,

no)?
6.
Enter yes. The following message appears:

+------+ OMNI SS#7 Configure Script Info.
| INFO | Script=./configurePlatform Action=Script
Continues.
+------+ Message=Configure system.
#########################################################
#
obtain the number of CE's
#########################################################
How many CEs? [max=4]
7.
Enter [number of computers], (1 for non-redundant, 2 for redundant). The

following appears:
###################################################################
obtain the Name of all CE's
##########################################################
What is the name of CE1?
8.
Enter smsc1. The following message appears:

*********************************************************************
The current GENERIC port files are saved in the

/home/omni/conf directory.
Each old file is save as <filename>.configure.save
*********************************************************
**** saving slan.cf ****
********** saving portConf.GENERIC ***********
********** saving ce.conf.GENERIC ************
********** saving df.conf.GENERIC ************
********** saving cestart.GENERIC ************
********** saving start.nCE.GENERIC **********
+------+ OMNI SS#7 Configure Script Info.
| INFO|Script=/home/omni/conf/mkportconf.sh Action=Script
Continues.
+---+ Message=Constructing portConf.GENERIC for Dual CE
system.
How many boards on CE1 smsc1?
9.
Enter 2. The following prompt appears:

What is the Board ID of board 1 [0-3]?
Page 10-28

10.
Chapter 10
Installation
Enter 0. The following prompt appears:

What is the Board Configuration for board 1 ?
11.
Type c30c7 for GSM systems, c30a7 for ANSI systems, c30ch7 for Chinese
and c30j7 for Japanese. Press <Enter>.
The following prompt appears:
What is the Board ID of board 2 [0-3]?
4.2.
12.
Repeat steps 10 and 11 for every board, increasing the board ID by one for
each board.
13.
When a prompt appears enter exit.
999 Command
To add a third or fourth SS7 board:
4.3.
1.
Log in as omni.
2.
Open the file /home/ss7/ConfigCCS/CcsParamFile.
3.
Set the value of the parameter NumberofCE1Boards to the new number of

SS7 link boards.
4.
Enter the command 999.
5.
Select the option configure.
6.
Confirm the configuration.
ConfigureNodes
configureNodes builds the configuration files that are needed for the system
startup. This utility must be run after running configurePlatform.
To run configureNodes:
1.
Login as user OMNI.
2.
To clear any previous setup, enter configureNodes -clean.
3.
To enter this path, enter cd /home/omni/conf.
4.
To run configureNodes in a GSM system, enter

./configureNodes C7 C7.
To run configureNodes in an IS41 system, enter

./configureNodes A7 A7.
To run configureNodes in a Chinese system, enter

./configureNodes CH7 CH7.
Page 10-29
Chapter 10
Installation

5.
OMNI Configuration
5.1.
Starting and Stopping the OMNI Platform
5.1.1.
Starting OMNI
There are two methods of starting OMNI:
x
Manual Start
Manual start is defined as the direct execution of the go command from a
UNIX prompt by typing the command:
go -nored
Non-Manual Start
Non-manual is defined as any other means of starting OMNI which invokes
a script called go.omni in some automatic way with pre-assigned values
for the go.omni parameters, such as power on.
5.1.2.
Stopping OMNI
If the Platform was started manually, simply press <Ctrl>+<C> (or its equivalent
on the terminal in use) in the UNIX window where OMNI was started.
If the Platform was started by some non-manual method, or if the original window
no longer exists, then an orderly stop is made as follows:
x
Enter the UNIX command Terminate 0.
To power off from the root user:

x
5.2.
Enter shutdown -y -g0 -i0.
OMNI Configuration References

Configure and start the OMNI up in order for the MAP EI to function.
NOTE:
6.
If OMNI is not running, enter under the OMNI login and password to
run the MML utility, for system configuration, and later the SFE part
of the ISMSC.
ISMSC Installation
The following procedures are required to install the ISMSC:
x
Pre-installation procedures
Page 10-30
Checking the installation prerequisites
Installation of the ISMSC software

6.1.
Chapter 10
Installation
Installation and configuration of the NYSMSBASE
Installation of the NYSMSSFE package
Installation of the MAP-EI(s): NYSMSMAP (GSM), or NYSMSIS41MAP, or NYSMSMAPA (for GSM over ANSI systems)
Configuration of the communication parameters of the TRM to the ISMSC

connection.
Pre-installation Procedures
The ISMSC software relies on the MAP protocol to interconnect with the mobile
network. The MAP interface is provided by the OMNI software. OMNI should be
installed on the machine on which the NYSMSMAP-EI(s) will be installed. After
installing OMNI, it should be configured using the MML utility (refer to
Chapter 11), as to the appropriate SCCP, TCAP and MAP definitions.
6.2.
Installation of the ISMSC Packages

The ISMSC software consists of three separate packages:
x
NYSMSBASE
NYSMSSFE
NYSMSMAP, or MYSMSMAPA, or NYSMSIS41-MAP
The package installations should be carried out under user root. If the ISMSC
package(s) is already installed on the machine, the old installation should be first
removed. For instructions on how to remove a package, refer to Paragraph 6.6.
All packages are on the same tape. Every drawer must have the NYSMSBASE
package installed, in addition to which the additional packages, either
NYSMSSFE or NYSMSMAP or both, are installed. The installations after
NYSMSBASE take the values defined during the installation of the NYSMSBASE
package.
Host names in ISMSC installations are:
Large (Active Standby)
sfe1, sfe2 for SFE

smsc1, smsc2 for OMNI/MAP
Large (single platform)
sfe1 for SFE

smsc1 for OMNI/MAP
Medium, Small
NOTE:
smsc1, (also smsc2 for fault resilient systems)
The default values that appear in the installation procedure below are
not necessarily those that will actually appear during installation. The
installer selects to accept or alter the values.
Page 10-31
Chapter 10
Installation

The NYSMSBASE package must be installed on each platform on which it will

run.
To install the NYSMSBASE package and additional packages:
1.
Insert a cassette containing ISMSC packages into the tape unit.
2.
Login as root.
3.
Enter the command

mkdir -p /home/ismscpkgs/
4.
To install all the packages, enter the command

pkgtrans /dev/rmt/ctape1 /home/ismscpkgs all
OR
To install NYSMSBASE and another package, enter the command
pkgtrans /dev/rmt/ctape1 /home/ismscpkgs all
5.
Enter the command:

pkgadd -d /home/ismscpkgs
NOTE:
Depending on the type of tape drive and system configuration you are
using, you may need to use another tape drive name in place of ctape.
For example, if you are using an external SCSI tape drive, use ctape1
or ctape2.
6.
Enter the command go to start the installation. A list of packages is

displayed on the screen.
7.
Select ALL to install all the packages, or select the number of the package to
be installed. The following default package configuration and prompt
appears:
SMSC Base 2.2 Installation parameters
SFE Configuration : Active-Standby
SFE host name : sfe1
SFE IP address : 192.9.200.204 (new host)
Alternate SFE host name : sfe2
Alternate SFE IP address : 192.9.200.206 (new host)
GSM MAP EI #1 host name : smsc1
GSM MAP EI #2 IP address : 192.9.200.205 (new host)
Alarm Processor #1 host name : ap1
Alarm Processor #1 IP address : 192.9.200.5 (new host)
Alarm Processor #2 host name : localhost
Keep alive messages will be sent to the hub
Page 10-32

Chapter 10
Installation
Hub host name : HUB

Hub IP address : 192.9.200.151 (new host)
Administrator user name : smsc
Do you wish to change any of these values ? (default: n)
[y,n,?,q] y
The SFE can be configured as standalone, active or standby. The default is

standalone. When installing a redundant system, one host must be defined
as active and the other as standby. Type y to change the configuration. (Type
n to continue the installation without changing the parameters, or type q to
exit.) Press <Enter>.
8.

Change SMSC Base Installation parameters
1 Standalone
2 Active-Standby
Enter configuration of SFE (default: Active-Standby)
[?,??,q]:
Select an option and press <Enter>.

9.

Enter configuration of SFE (default: Active-Standby)
[?,??,q]:
Press <Enter> to accept the default, or type in another value and press
<Enter>.
10.

Enter a host name for SFE (default: sfe1) [?,q]
<Enter>.
11.

Enter an IP address for host sfe1 (default: 192.9.200.204)
[?,q]
<Enter>.
12.

Enter a host name for Alternate SFE (default: sfe2) [?,q]
<Enter>.
13.

Enter an IP address for host sfe2 (default: 192.9.200.206)
[?,q]
Page 10-33
Chapter 10
Installation

<Enter>.
14.

1
GSM
IS41C
Enter the type of MAP EIs (default: GSM) [?, ??, q]:
Select the type of MAP EIs for the network. From this point on, whenever
the word EI appears on the screen, either GSM or IS41C will also appear. In
this example, GSM is the selected option.
15.

1
Single
Dual
Enter configuration of GSM EIs (default: Dual) [?,?,q]
For standalone configuration, select Single. For active or standby

configuration select Dual. In a redundant system, the NYSMSMAP or
NYSMSIS41-MAP is installed twice. The two hosts running on the GSM or
IS41C MAP EIs are supplied in the installation of the NYSMSBASE
package.
16.
To configure the two hosts running on the GSM or IS41C MAP EIs, the
following prompt appears:
Enter a host name for GSM EI(#1) (default:smsc1) [?,q]
Press <Enter> to accept the default, or enter the host name and press
<Enter>.
17.
If the configuration is dual, the following prompt appears:

Enter a host name for GSM EI (#2) (default: smsc2) [?, q]
<Enter>.
18.
If the host name is not yet defined in /etc/hosts, the following prompt
appears:
Enter an IP address for host smsc2 (default: 192.9.200.10)
[?, q]
Press <Enter> to accept the default, or enter the IP address and press
<Enter>.
19.
To select one or two Alarm processors, the following prompt appears:

1
Single
Dual
Enter configuration of Alarm Processors (default: Dual) [?,

??, q]:
Page 10-34

Chapter 10
Installation
Press <Enter> to accept the default or type in single for one Alarmprocessors and press <Enter>.
20.
For configuration of the Alarm-processor connection, the following prompt

appears:
Enter a host name for Alarm Processor (#1) (default: ap1)
[?, q]
<Enter>.
21.
appears:
Enter IP address for host ap1 (default: 192.9.200.5) [?, q]
<Enter>.
22.
If the configuration is dual, the following prompt appears:

Enter a host name for Alarm Processor (#2) (default: ap2)
[?, q]
<Enter>.
23.
appears:
Enter an IP address for host ap2 (default: 192.9.200.10)
[?, q]
<Enter>.
24.
For configuration of the I-am-alive connection with the hub, the following
prompt appears:
Should keep alive messages be sent to the hub ? (default:
yes) [y, n, ?, q]
Press <Enter> to accept the default and enable the feature, or type n for no
and press <Enter>.
25.
If the default was accepted, the following prompt appears:

Enter a host name for Hub(default: HUB) [?, q]
<Enter>.
26.

Enter an IP address for host HUB (default: 192.9.200.151)
[?, q]
<Enter>.
Page 10-35
Chapter 10
Installation
27.

To create the UNIX user and group of the ISMSC administrator, the
Enter user name for SMSC (default: smsc) [?, q]
Press <Enter> to accept the default, or enter the user name and press
<Enter>.
28.
To create the UNIX user number of the ISMSC administrator, the following
prompt appears:
Enter a user id for user smsc (default: 20001/automatic)
[1-60000, ?, q]
Press <Enter> to accept the default, or enter the user ID and press <Enter>.
In the event that the user ID 20001 is already used, the default is set
automatically, and if it is accepted, the user ID will be allocated.
29.
To define a group name, the following prompt appears:

Enter group name for the SMSC user (default: sys) [?,q]
Press <Enter> to accept the default, or enter the group name and press
<Enter>.
30.
If you selected a non-existing group, or to define a user ID for SMSC, the

Enter a group id for user smsc (default: automatic) [160000, ?, q]
Press <Enter> to accept the default, or enter the group ID and press
<Enter>. In the event that the default is automatic, and it is accepted, the
group ID will be allocated automatically.
31.
To define the path in which the SMSC will be installed, the following
prompt appears:
Enter the path to the home directory of the SMSC user
(default: /home/smsc) [?, q]
Press <Enter> to accept the default, or enter the path-name and press
<Enter>.
NOTE:
32.
This is the location where the software will be installed.
After all the parameters have been set, the package configuration is
displayed again, for example:
SMSC Base 2.2 Installation parameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SFE Configuration : Active-Standby
SFE host name : sfe1
SFE IP address : 192.9.200.204 (new host)
Alternate SFE host name : sfe2
Page 10-36

Chapter 10
Installation
Alternate SFE IP address : 192.9.200.206 (new host)

GSM MAP EI #2 IP address : 192.9.200.205 (new host)
Alarm Processor host name : ap1
Alarm Processor IP address : 192.9.200.5 (new host)
Keep alive messages will be sent to the hub
Hub host name : HUB
Hub IP address : 192.9.200.151 (new host)
Administrator user name : smsc
Do you wish to change any of these values? (default: n)
[y,n,?,q]
Type y to change the configuration, or n to save it. Press <Enter>.

33.

Proceed with installation?
If all the parameters are correct, type y, then press <Enter> to start the
installation.
34.
The following text appears as the installation is performed.

Installing NETology SMSC as <NYSMSBASE>
## Installing part 1 of 1.n
[ verifying class <install> ]
[ verifying class <smsc> ]
[ verifying class <config> ]
[ verifying class <data> ]
Modifying /etc/rc2.d/S999smsc
[ verifying class <build> ]
[ verifying class <system> ]
Updating the hosts file ...
Finished updating the hosts file
Page 10-37
Chapter 10
Installation

Building configuration files ...

Finished building configuration files ...
*** Building the database, this will take a while. *** ***
Finished building the database ***
Installation of NETology SMSC completed successfully.
35.
6.3.
When the installation is complete, type q to exit the installation utility.
Configuration of the File /etc/hosts

To configure the file /etc/hosts:
1.
Login as user smsc.
2.
Type cd /hosts and press <Enter>.
3.
Use the editor vi to edit the file hosts so it would fit the specific platform of
the installed drawer. The following example is a hosts file for ISMSC
medium redundant platform:
# Internet host table
127.0.0.1
localhost
# 192.9.200.203
SMSC1 smsc1 smsc
# start of CCS part

192.9.200.203 smsc1
192.9.200.205 smsc2
192.9.200.6
ap
192.9.200.6
trm
192.9.200.6
echohost
# End of CCS part

### Following lines added by installation of NeTology
(NYSMSBASE)
192.9.200.6
ap1
192.9.200.151 HUB
### End of NETology addition (NYSMSBASE)
6.4.
Define a License on the SFE Machine

The CIR should contain a license for the SMSC, as the Busy Hour Short Messages
(BHSM) number. To set this license, login as SMSC on the SFE machine, and
type: smsc make_license. The utility prompts for the maximal BHSM, and sets
the value in the configuration file.
Page 10-38

6.5.
Chapter 10
Installation
Fixing the Password of the SMSC User

After installing the ISMSC packages, it is necessary to set the password of the
user to the node name.
To set the password of the user to the node name:
6.6.
1.
Login as root.
2.
Enter the command passwd smsc.
3.
For a new password, type the password smsc1 for smsc1 and smsc2 for
smsc2 and press <Enter>.
4.
Enter the password again.
5.
Enter passwd -x -1 smsc.
6.
Enter exit and enter as user smsc with the new password to verify the
change.
Removing an Installed Package

NOTE:
The MAP and SFE packages should be removed first, and then the
NYSMSBASE package.
To remove the ISMSC package(s):

1.
Enter the command # pkgrm. A list of packages will be displayed on the

screen. Press <Enter> to see more choices or <Ctrl>+<D> to stop displaying
the list of packages.
2.
Select the number corresponding to the NYSMSSFE or NYSMSMAP

package.
3.
When prompted, enter y to confirm deletion of the package.
The system is now ready to for reinstallation of the ISMSC package(s).
7.
ISMSC Configuration
The ISMSC software customization is performed for the two separate packages:
x
NYSMSSFE
NYSMSMAP/NYSMSMAPA/NYSMSIS41
Page 10-39
Chapter 10
Installation
7.1.

NOTE:
When the ISMSC is installed on multiple computers, there are

multiple configuration files, one on each drawer. The screen or line
command distribute configuration can be used to copy the
configuration file to all computers. Refer to Chapter 4,
Paragraph 4.5.4. for the screen interface. Perform this command by
typing: smsc_distrib_config. The configuration file is located in the
/home/smsc/site/config directory. The configuration of the SFE is in
the file sfe.config. The configuration of the MAP EIs is in the file
map.config. The ISMSC is configured using vi, or any other UNIX
editor. Perform both NYSMSMAP and NYSMSIS41-MAPconfiguration using one copy of the config file on one SFE host, and
distribute the file to the other hosts as described above.
NOTE:
Configuration of the NYSMSMAP and of the NYSMSIS41 are not the

same. See Paragraph 7.3.for configuration of the NYSMSMAP
package. See Paragraph 7.4. for configuration of the NYSMSIS41MAP package.
NYSMSSFE Parameters
Customization of the main parameters occurs during installation. After
installation, the following parameters should be verified for correct configuration.
Parameters and field values can be modified in the config file, located in the
subdirectory /home/smsc/smsc.<version>/config, <version> is the ISMSC version
(for example, version 1.12).
The parameters listed in Paragraph 7.1.1. through Paragraph 7.1.8. are those that
are relevant for the installation of the system.
7.1.1.
ALERT
The alert parameter enables/disables the SMSC handling of SC-Alerts. If alert
handling is enabled, a message delivery attempt will be made upon receipt of an
SC-Alert for the corresponding subscriber. If alert handling is disabled, SC-Alerts
are ignored and short-message redelivery attempts are based only on the retry
mechanism.
Default: yes
7.1.2.
BILLING
The billing parameter enables/disables the generation of a billing record for each
short-message arriving to a final state (i.e., delivered, permanently rejected or
expired). If billing is enabled, a billing record will be created. If billing is
disabled, no record will be created.
Default: no
Page 10-40

7.1.3.
Chapter 10
Installation
EXPIRATION
The expiration parameter sets the duration, in minutes, a short-message will exist
in the SMSC database from the moment in was initially accepted. During this
time, the message will optionally be scheduled for redelivery attempts based on
SC-Alerts and/or a retry mechanism.
When the expiration period is reached, the short message will be discarded from
the SMSC database. This value is valid for all messages.
Default: 7200 (120 hours, 5 days)
7.1.4.
INTERNAL_RETRY
The Internal Retry parameter enables retries of messages that failed due to
internal ISMSC problems, usually lack of response from MAP or a timeout
situation. A value of 0 indicates that the value defined in the parameter
RETRY_INTERVAL will be used.
Default: 15
7.1.5.
RETRY
The retry parameter enables/disables the SMSC retry mechanism. If the retry
mechanism is enabled, the delivery retries of a short-message will occur according
to the values of the retry_interval parameter (refer to Paragraph 7.1.6.). If the
retry mechanism is disabled, no delivery retries will occur. The short-message will
be redelivered only upon receipt of an SC-Alert for the corresponding subscriber,
or it will expire after the expiration period.
Default: yes
7.1.6.
RETRY_INTERVALS
The retry_interval parameter controls the intervals in which a short-message is
scheduled for a redelivery attempt. The parameter contains a number of triplets,
each triplet represents a range of retry attempts and the delay period between
them. The triplets are of the form:
<from>-<to>:<delay>
where:
<from> and <to> are the retry sequence attempts.
<delay> is the delay period (in minutes) to wait between retry attempts.
Any number of triplets may be specified. Unspecified retry delays will use the last
previously specified delay.
For example, the following commands:
1-5:5
6-10:10
Page 10-41
Chapter 10
Installation

specify that the first five retry attempts occur at intervals of five minutes. The
sixth to tenth retry attempts occur at ten minute intervals.
Default:
7.1.7.
1-1:15
2-2:30
3-5:60
6-9:180
10-5000:300
SMART RETRIES
This parameter enables Smart Retries.
NOTE:
This parameter must be set to yes.
Value: yes
7.1.8.
START_ON_BOOT
The start_on_boot parameter enables/disables starting of the SMSC processes
during system boot (startup).
Default: yes
7.2.
Smart Retries
Each Target EI, in case of delivery failure, passes to the SFE an array of the
diagnostic elements, in order to enable maximum flexibility in scheduling next
delivery attempts. The content of the diagnostic array depends on the type of the
cellular network (GSM or IS41), and on an internal ISMSC configuration
parameter, called diagnostic scheme.
The diagnostic array for GSM networks in the current release is composed of the
following:
x
Error reason as defined by MAP standards (GSM 09.02)
Error cause as defined by MAP standards (GSM 09.02)
Error codes as defined by MAP standards (GSM 03.40)
The diagnostic array for IS-41 networks in the current release is composed of the
following:
x
Network entity (HLR, MSC) originating the error code
Error category - valid values are listed in Paragraph 7.2.1.2.
Error cause/reason (TIA/EIA/IS-41-C)
Notification (alert) availability code
In addition, General Error conditions are defined. Error conditions from the
diagnostic arrays are mapped, or translated, to General Errors.
Page 10-42

Chapter 10
Installation
For each General Error there is a Retry Decision Rule. The Retry Decision Rule
specifies which Retry Profile Definition is used for that specific error. Retry
Profile Definitions are the retry schedules defined in the system.
In order to further refine the retry capabilities, additional retry profile definitions
may be defined for the actual diagnostic array errors. These additions are also
defined as Retry Decision Rules.
When the ISMSC has received an error, and needs to select a retry decision rule, it
first searches for a retry rule defined for the specific diagnostic array error. If
none exists, it proceeds to the general retry decision files, which define the retries
for the general errors. If a retry decision rule for the error is not defined, the
retries are performed according to the default retry profile.
This mechanism allows specification of complex retry behaviors. For example, the
Absent Subscriber error can be used with a timer to distinguish between
subscribers that are actually detached (handset is closed) and subscribers that are
out of coverage. The ISMSC calculates the time interval between issuing a
ForwardSM message and getting an answer for the message from the network. If
the handset is closed, the answer from the network is received very quickly. The
error is interpreted as ABSENT_SUBSCRIBER_IMSI_DETACHED. The message
delivery is retried after an Alert/Notification is received. A long term retry
schedule is also defined as a backup. If the answer from the network is received
after a time interval greater than that specified by the configuration parameter
imsi_detach_time,
the
ISMSC
considers
this
error
as
ABSENT_SUBSCRIBER_PAGE_FAILED and is retried on a short term schedule.
7.2.1.
Error Groups
The errors are defined in the following groups, which are referred to by their
condition numbers.
7.2.1.1. GSM Error Groups

The following error conditions are defined for ISMSC interaction with GSM
networks:
GSM/MAP reason code condition 1 (GSM 09.02)
x
GSM MAPERR UNKNOWN SUBSC (1)
GSM MAPERR ILLEGAL SUBSC (9)
GSM MAPERR TELE SVC NOT PROV (11)
GSM MAPERR ILLEGAL EQUIP (12)
GSM MAPERR CALL BARRED (13)
GSM MAPERR FAC NOT SUPPORTED (21)
GSM MAPERR ABSENT SUBSC (27)
GSM MAPERR SM DELIV FAILURE (32)
Page 10-43
Chapter 10
Installation

GSM MAPERR SYSTEM FAILURE (34)
GSM MAPERR DATA MISSING (35)
GSM MAPERR UNEXP DATA VALUE (36)
GSM/MAP cause code condition 2 (GSM 09.02)

x
GSM SM FAIL CAUSE CAPA EXCEED (0)
GSM SM FAIL CAUSE PROT ERR (1)
GSM SM FAIL CAUSE NOT SM (2)
GSM SM FAIL CAUSE UNKNOWN SVC (3)
GSM SM FAIL CAUSE SS CONGEST (4)
GSM SM FAIL CAUSE INVALID ADDR (5)
GSM SM FAIL CAUSE NOT SC SUB (6)
error code condition 3 (GSM 03.40)

x
UNKNOWN SUBSCRIBER (1)
ILLEGAL SUBSC (9)
TELESERVICE NOT PROVISIONED (11)
CALL BARRED (13)
LOWER LAYER CAPABILITIES NOT PROV (19)
ERROR IN MS (20) FACILITY NOT SUPPORTED (21)
MEMORY CAPACITY EXCEEDED (22)
ABSENT SUBSCRIBER IMSI DETACHED (29)
SYSTEM FAILURE (36)
ILLEGAL EQUIP (40)
ABSENT SUBSCRIBER PAGE FAILED (70)
alert expectation condition 4

x
ALERT NOT EXPECTED (0)
ALERT EXPECTED (1)
general errors
x
GNRL SM DLVR OK (0)
GNRL SM DLVR NETWORK PROBLEM (1)
GNRL SM DLVR RADIO PROBLEM (2)
GNRL SM DLVR ENCODING PROBLEM (3)
GNRL SM DLVR SYSTEM FAILURE (4)
Page 10-44

GNRL SM DLVR ILLEGAL EQUIPMENT (5)
GNRL SM DLVR TLSVC NOT PRVSND (6)
GNRL SM DLVR LOWER LAYER PROBLEM (7)
GNRL SM DLVR SMS ORIGIN DENIED (8)
GNRL SM DLVR SMS DEST DENIED (9)
GNRL SM DLVR SUPPL SERV NOT SUPP (10)
GNRL SM DLVR SMS NOT SUPP (11)
GNRL SM DLVR UNKNOWN SUBSCRIBER (12)
GNRL SM DLVR ILLEGAL SUBSCRIBER (13)
GNRL SM DLVR TERMINAL PROBLEM (14)
GNRL SM DLVR CALL BARRED (15)
GNRL SM DLVR MEMORY SHORTAGE (16)
GNRL SM DLVR ABSENT SUBSCRIBER (17)
GNRL SM DLVR NO PAGE RESPONSE (18)
GNRL SM DLVR DEST OUT OF SERV (19)
GNRL SM DLVR DEST BUSY (20)
GNRL SM DLVR SMS DLVR POSTPONED (21)
GNRL SM DLVR SC CONGESTION (22)
GNRL SM DLVR SFE INTERNAL PROBLEM (50)
Chapter 10
Installation
7.2.1.2. IS-41C Error Groups

The following error conditions are defined for ISMSC interaction with IS-41
networks:
Network entity - condition 1
x
IS41_ENTITY_HLR (0),
IS41_ENTITY_MSC (1)
Error category - condition 2

x
MAP_RC_INTERNAL_ERROR (1)
MAP_RC_ERROR (2)
MAP_RC_TIMEOUT (3)
MAP_RC_PROVIDER_ERROR (4)
MAP_RC_REJECT_ERROR (5)
MAP_RC_RETURN_ERROR (6)
Page 10-45
Chapter 10
Installation

MAP_RC_SMDPP_ERROR (7)
MAP_RC_SMSREQ_ERROR (8)
MAP_RC_SMSNOT_ERROR (9)
MAP_RC_ABORTED (10)
IS41 error cause/reason code - condition 3 (TIA/EIA/IS41-C)

x
IS41_EC_UNRECMIN (129)
IS41_EC_UNRECESN (130)
IS41_EC_MINHLRMIS (131)
IS41_EC_OPSEQPROB (132)
IS41_EC_RESSHORT (133)
IS41_EC_OPNOTSUP (134)
IS41_EC_TRUNKUN (135)
IS41_EC_PARAERROR (136)
IS41_EC_SYSFAIL (137)
IS41_EC_UNRECPAR (138)
IS41_EC_FEATINACT (139)
IS41_EC_MISSPAR (140)
IS41_SMSREQ_DENIED (257)
IS41_SMSREQ_POSTPONED (258)
IS41_SMSREQ_UNAVAILABLE (259)
IS41_SMDPP_NETWORK_ADDR_VACANT (0)
IS41_SMDPP_NETWORK_ADDR_TRANS (1)
IS41_SMDPP_NETWORK_RES_SHORT (2)
IS41_SMDPP_NETWORK_FAILURE (3)
IS41_SMDPP_NETWORK_INV_TELESERV (4)
IS41_SMDPP_NETWORK_PROB (5)
IS41_SMDPP_TERMINAL_NO_RESP (32)
IS41_SMDPP_TERMINAL_BUSY (33)
IS41_SMDPP_TERMINAL_NO_ACK (34)
IS41_SMDPP_TERMINAL_RES_SHORT (35)
IS41_SMDPP_TERMINAL_DELIVERY_POST (36)
IS41_SMDPP_TERMINAL_OUT_SERV (37)
Page 10-46

IS41_SMDPP_TERMINAL_NO_ADDR (38)
IS41_SMDPP_TERMINAL_PROB (39)
IS41_SMDPP_RADIO_RES_SHORT (64)
IS41_SMDPP_RADIO_INCOMP (65)
IS41_SMDPP_RADIO_PROB (66)
IS41_SMDPP_GENERAL_ENCOD_PROB (96)
IS41_SMDPP_GENERAL_ORIGIN_DEN (97)
IS41_SMDPP_GENERAL_TERMIN_DEN (98)
IS41_SMDPP_GENERAL_SUPPL_SERV (99)
IS41_SMDPP_GENERAL_NOT_SUPP (100)
IS41_SMDPP_GENERAL_MISS_PARE (102)
IS41_SMDPP_GENERAL_MISS_PARM (103)
IS41_SMDPP_GENERAL_UNREC_PAR (104)
IS41_SMDPP_GENERAL_UNEXP_PAR (105)
IS41_SMDPP_GENERAL_USER_DATA (106)
IS41_SMDPP_GENERAL_PROB (107)
Chapter 10
Installation
notification (alert) availability code - condition 4

x
ALERT_NOT_EXPECTED (0)
ALERT_EXPECTED (1)
General errors
x
GNRL_SM_DLVR_OK (0)
GNRL_SM_DLVR_NETWORK_PROBLEM (1)
GNRL_SM_DLVR_RADIO_PROBLEM (2)
GNRL_SM_DLVR_ENCODING_PROBLEM (3)
GNRL_SM_DLVR_SYSTEM_FAILURE (4)
GNRL_SM_DLVR_ILLEGAL_EQUIPMENT (5)
GNRL_SM_DLVR_TLSVC_NOT_PRVSND (6)
GNRL_SM_DLVR_LOWER_LAYER_PROBLEM (7)
GNRL_SM_DLVR_SMS_ORIGIN_DENIED (8)
GNRL_SM_DLVR_SMS_DEST_DENIED (9)
GNRL_SM_DLVR_SUPPL_SERV_NOT_SUPP (10)
GNRL_SM_DLVR_SMS_NOT_SUPP (11)
Page 10-47
Chapter 10
Installation
7.2.2.

GNRL_SM_DLVR_UNKNOWN_SUBSCRIBER (12)
GNRL_SM_DLVR_ILLEGAL_SUBSCRIBER (13)
GNRL_SM_DLVR_TERMINAL_PROBLEM (14)
GNRL_SM_DLVR_CALL_BARRED (15)
GNRL_SM_DLVR_MEMORY_SHORTAGE (16)
GNRL_SM_DLVR_ABSENT_SUBSCRIBER (17)
GNRL_SM_DLVR_NO_PAGE_RESPONSE (18)
GNRL_SM_DLVR_DEST_OUT_OF_SERV (19)
GNRL_SM_DLVR_DEST_BUSY (20)
GNRL_SM_DLVR_SMS_DLVR_POSTPONED (21)
GNRL_SM_DLVR_SC_CONGESTION (22)
GNRL_SM_DLVR_SFE_INTERNAL_PROBLEM (50)
Default Translation of Errors

The default error translation rules defined for GSM networks in ISMSC 2.4 are
presented in Table 10-7. The default error translation rules defined for IS-41C
networks in ISMSC 2.4 are presented in Table 10-8.
NOTE:
These rules must not be changed.
Table 10-7: Smart RetriesGSM Default Error Translation Rules

GSM Error
General Error
default
GNRL_SM_DLVR_UNRECOGNIZED_ERROR
GSM_MAPERR_ILLEGAL_EQUIP
GNRL_SM_DLVR_ILLEGAL_ EQUIPMENT
GSM_MAPERR_ILLEGAL_SUBSC
GNRL_SM_DLVR_ILLEGAL_ SUBSCRIBER
*.*.ABSENT_SUBSCRIBER_IMSI_DET
ACHED
GNRL_SM_DLVR_ABSENT_ SUBSCRIBER
*.*.ABSENT_SUBSCRIBER_PAGE_FAI
LED
GNRL_SM_DLVR_NO_PAGE_RESPONSE
GSM_MAPERR_SM_DELIV_FAILURE.
GSM_SM_FAIL_CAUSE_CAPA_EXCEE
D
GNRL_SM_DLVR_MEMORY_SHORTAGE
GSM_MAPERR_SM_DELIV_FAILURE.
GSM_ SM_FAIL_CAUSE_PROT_ERR
GNRL_SM_DLVR_ENCODING_PROBLEM
GSM_MAPERR_SM_DELIV_FAILURE.*
.LOWER_LAYER_CAPABILITIES_NOT
_PROV
GNRL_SM_DLVR_LOWER_LAYER_PROBLE
M
Page 10-48

Chapter 10
Installation
GSM Error
General Error
default
GNRL_SM_DLVR_UNRECOGNIZED_ERROR
GSM_MAPERR_ILLEGAL_EQUIP
GNRL_SM_DLVR_ILLEGAL_ EQUIPMENT
GSM_MAPERR_CALL_BARRED
GNRL_SM_DLVR_CALL_BARRED
GSM_MAPERR_TELE_SVC_NOT_PRO
V
GNRL_SM_DLVR_TLSVC_NOT_PRVSND
GSM_MAPERR_FAC_NOT_SUPPORTE
D
GNRL_SM_DLVR_SMS_NOT_SUPP
GSM_MAPERR_SYSTEM_FAILURE
GNRL_SM_DLVR_SYSTEM_FAILURE
*.*.SYSTEM_FAILURE
GSM_MAPERR_UNKNOWN_SUBSC
GNRL_SM_DLVR_UNKNOWN_SUBSCRIBE
R
Table 10-8: Smart Retries - IS-41C Default Error Translation Rules

IS-41 Error
General Error
default
GNRL_SM_DLVR_UNDEFINED_CODE
*.MAP_RC_TIMEOUT
*.MAP_RC_RETURN_ERROR
*.MAP_RC_SMSREQ_ERROR.IS41_SM
SREQ_DENIED
GNRL_SM_DLVR_SMS_DEST_DENIED
SREQ_POSTPONED
GNRL_SM_DLVR_ABSENT_SUBSCRIBER
SREQ_UNAVAILABLE
*.MAP_RC_SMDPP_ERROR.IS41_SMD
PP_NETWORK_ADDR_VACANT
GNRL_SM_DLVR_NETWORK_PROBLEM
PP_NETWORK_ADDR_TRANS
PP_NETWORK_RES_SHORT
PP_NETWORK_FAILURE
PP_NETWORK_PROB
PP_NETWORK_INV_TELESERV
GNRL_SM_DLVR_TLSVC_NOT_PRVSND
PP_TERMINAL_NO_RESP
GNRL_SM_DLVR_NO_PAGE_RESPONSE
Page 10-49
Chapter 10
Installation

IS-41 Error
General Error
PP_TERMINAL_BUSY
GNRL_SM_DLVR_DEST_BUSY
PP_TERMINAL_NO_ACK
GNRL_SM_DLVR_TERMINAL_PROBLEM
PP_TERMINAL_RES_SHORT
GNRL_SM_DLVR_MEMORY_SHORTAGE
PP_TERMINAL_DELIVERY_POST
PP_TERMINAL_OUT_SERV
GNRL_SM_DLVR_DEST_OUT_OF_SERV
PP_TERMINAL_NO_ADDR
PP_TERMINAL_PROB
PP_RADIO_RES_SHORT
GNRL_SM_DLVR_RADIO_PROBLEM
PP_RADIO_INCOMP
PP_RADIO_PROB
PP_GENERAL_ENCOD_PROB
PP_GENERAL_MISS_PARE
PP_GENERAL_MISS_PARM
PP_GENERAL_UNREC_PAR
PP_GENERAL_UNEXP_PAR
PP_GENERAL_USER_DATA
PP_GENERAL_ORIGIN_DEN
GNRL_SM_DLVR_SMS_ORIGIN_DENIED
PP_GENERAL_TERMIN_DEN
GNRL_SM_DLVR_SMS_DEST_DENIED
PP_GENERAL_SUPPL_SERV
GNRL_SM_DLVR_SUPPL_SERV_NOT_SUPP
PP_GENERAL_NOT_SUPP
GNRL_SM_DLVR_SMS_NOT_SUPP
Page 10-50

7.2.3.
Chapter 10
Installation
IS-41 Error
General Error
PP_GENERAL_PROB
Format and Examples of Rules

The following rules are defined:
x
Error Translation Rules: Translate GSM errors to general errors
Error Translation Rules to TRM Errors: translate general errors to errors

that are viewed on the TRM CEL logger.
NOTE:
The Error Translation Rules must not be altered.
Retry Decision Rules: Assign retry profiles for specific errors (not general)
General Decision Rules: Assign retry profiles for general errors
7.2.3.1. Error Translation Rules

Error translation rules are formatted as follows:
condition-1[.condition-2[. condition-3[.condition-4]]] = result-error
where:
condition-n is the name of a specific error condition (Paragraph 7.2.1.), or
an asterisk for a wild card
result-error is the name of the result translated error
Examples:
absent_subscriber_imsi_detached = gnrl_sm_dlvr_absent_subscriber
*.*.absent_subscriber_page_failed = gnrl_sm_dlvr_no_page_response
An * is necessary to indicate a wild card only if a lower number condition is
specified (on the left side of the rule). If a higher number condition is specified,
no * is necessary, for example:
condition-1 = result-error
GSM_MAPERR_ILLEGAL_EQUIP=GNRL_SM_DLVR_ILLEGAL_EQUIPMENT
7.2.3.2. Retry Decision Rules

Retry Decision Rules are formatted as follows:
condition-1[.condition-2[. condition-3 [.condition-4]]]=retry profile [stats/nostats]
where:
condition-n is the name of a specific error condition (Paragraph 7.2.1.), or
an asterisk for a wild card
Page 10-51
Chapter 10
Installation

retry_profile is the scheduler for further delivery attempts (Paragraph 7.2.4.)

stats/nostats is the flag that determines whether statistics are printed for this
rule
Examples:
The following rule specifies that when the error absent_subscriber_imsi_detached
is received, the long profile is selected:
*.*.absent subscriber imsi detached.alert expected=enter long
The following rule specifies that when the error gsm_maperr_sm_deliv_failure
and the cause gsm_sm_fail_cause_capa_exceed are received, the short profile is
selected:
gsm_maperr_sm_deliv_failure.gsm_sm_fail_cause_capa_exceed=enter short
7.2.3.3. General Decision Rules

Retry Decision Rules based on General Errors (for each rule the alert expected
specification may be added as a prefix, indicating that an alert is expected). The
format for these rules is:
alert.general error = retry profile [/nostats]
where:
alert is the condition that determines availability of the notification from the
network (may be replaced with asterisk)
general_error is the General SMSC Error (Paragraph 7.2.1.)
retry_profile is the scheduler for further delivery attempts (Paragraph 7.2.4.)
stats/nostats is the flag that determines (that in this case) no statistics are
printed for this rule.
Example: Absent Subscriber error
alert_expected.gnrl_sm_dlvr_absent_subscriber = enter long
7.2.4.
Retry Profile Definitions

The retry profiles and retry selection configuration resides in dedicated files in the
ISMSC config directory. A general retry profile file is named retry_profile. A per
EI retry profile selection file is named retry_decision.ei.<NAME>.
A retry profile file contains definitions in the following syntax:
<profile> = <triplet> , <triplet> , ... , <triplet> [ <terminator> ]
where a <triplet> defines an interval between retries in one of the following
formats:
1-x:z
retry attempts 1 through x are performed at an interval of z minutes
x:z
x retries are performed at an interval of z minutes
Page 10-52

Chapter 10
Installation
the next retry is performed after z minutes
The interval z can be accompanied by one of the following time specifiers:

s
seconds
minutes (default))
hours
The <terminator> is one of the following:

fail
Fail delivery for this subscriber. Stop making delivery attempts,

and make all pending messages undeliverable.
end
For Absent Subscribers: stop making delivery retries, and wait for
an Alert from the network or expiration of the pending messages.
In all other cases the fail logic is used.
enter <other-profile>
Retries are performed according to the profile specified in <otherprofile>
If no terminator is specified, the last specified retry interval is used for all
successive retries until reaching the time limit specified in the parameter
EXPIRATION (Paragraph 7.1.3.).
Example of a Short Term Schedule
This short term schedule operates on the assumption that the error condition will
be removed within the following hour.
short term = 10, 20, 30, enter long
Three delivery attempts are scheduled for this hour. After that a long term
schedule retry profile is enabled.
Example of a Long Term Schedule
long term = 60, 180, 300
When the long term schedule is used there is an attempt after 1 hour (=60
minutes), then 3 hours (=180 minutes), and then repeated attempts at five hour
(=300 minutes) intervals.
Example of a Composite Profile
profl = 1-2:20s, 10, 5:3h, fail
In this example the first and second retries are at 20 second intervals. The third
retry is 10 minutes after the seconds one fails. The fourth through eighth retries
are at 3 hours intervals. After that, all pending messages are marked as
undeliverable and no additional attempts are made.
Page 10-53
Chapter 10
Installation
7.2.5.

File Locations
The Retry Decision Rules reside in dedicated files in the ISMSC directory named
/home/smsc/site/config.
A general retry decision file is named: retry_decision_general.
A per EI retry decision file is named: retry_decision.ei.<NAME>
where <NAME> is the EI name: MAP for GSM/MAP, IS41 for IS41.
A general retry profile definition file is named: retry_profile.
7.3.
Configuring the NYSMSMAP Package

Before starting the customization, determine the HLRs and MSCs (including
GMSCs, in case inter-network roaming is implemented) to which the SMSC will
be connected. This is the same process as performed during OMNI installation.
NOTE:
Configuration of the NYSMSMAP package is applicable to GSM

networks only. For these procedures, a basic knowledge of GSM and
SS7 concepts is assumed.
For each one of the above entities, determine the following:

x
point-code (PC)
global-title (GT), with international prefix
GSM version supported (GSM ph-I or GSM-phII)
routing method from the SMSC to the entity:
route-on-dpc (routing is done using the physical point-code address of

the entity)
or
7.3.1.
route-on-gt (routing is done using the logical global-title attribute of

the entity)
Configuration of the MTP (OMNI)

In order to configure the MSCs, HLRs, and SSNs, determine how the SMSC is
connected to all HLRs and MSCs (including GATEWAY MSCs (GMSCs) for
international roaming). Define the ospc, link sets, links, route sets, and Global
Title of all HLRs and MSCs and the SMSC accordingly from the systems CIR.
Route sets should be defined for all the DPCs of all HLRs and MSCs in the
network. For details on MTP provisioning, data storage and recovery, refer
toChapter 12.
The MTP element maintains the SS7 logical nodes own point code (PC). The
Platform provides commands for creating, deleting, and displaying the nodes own
point code.
Page 10-54

NOTE:
Chapter 10
Installation
References in the notes below (MAN PGS) refer to UNIX manual

pages.
MAN PGS: CRTE-OSPC(8q);

OSPC(8q)
CRTE-OSPC_s(8q);
DLT-OSPC(8q);
DISPL-
The MTP maintains a Link Set Table, containing the name and adjacent point
code of every link set for the logical node. The Platform provides MML
commands for creating, deleting, and displaying link sets in the Link Set Table.
(For further details on the MML Interface, refer to Chapter 11.
MAN PGS: CRTE-LSET(8q); DLT-LSET(8q); DISPL-LSET(8q)
The MTP maintains a Link Table, containing the name, logical port number, link
set, and signaling link code of every signaling link in the logical node. The
Platform provides commands for creating (including specification of all
parameters), deleting, and displaying signaling links in the Link Table.
A routeset is a collection of the routes (link sets) over which a destination is
reachable. The MTP maintains a Route Set Table for every Destination Point Code
(DPC), containing the routeset name, destination point code, and all routes (link
sets) over which the destination is reachable from the logical node.
The Platform provides commands for maintenance of routesets as follows:
x
Creating (including specification of one or more link sets)
Adding one or more link sets to an existing routeset
Removing one or more link sets from an existing routeset
Deleting a routeset
Displaying a routeset
MAN PGS: CRTE-SLK(8q); DLT-SLK(8q); DISPL-SLK(8q); CRTE-RSET(8q);

CHG-RSET(8q); CHG-RSET(8q); DLT-RSET(8q); DLT-RSET-s(8q);
DISPL-RSET(8q)
7.3.2.
Configuration of the SCCP (OMNI)

The Signaling Connection Control Part (SCCP) provides connectionless and
connection-oriented network services. The SCCP is an MTP user that enhances
the MTP by providing connection-oriented and connectionless services.
Connectionless services transfer unit data, but provide no acknowledgments or
recovery procedures.
The SCCP augments the functionality of the MTP by permitting expanded
addressing capabilities. However, the SCCP requires greater overhead. Thus, the
services of the SCCP are used only when needed. For applications requiring
connectionless message transfer with limited addressing capability, the MTP is
sufficient.
Page 10-55
Chapter 10
Installation

The routing capability of the MTP is limited to delivering messages to the correct
signaling point based on the DPC, and once there, forwarding the message to the
correct MTP user within the signaling point based on the value of the service
indicator contained within the signal information octet. The SCCP provides an
additional global title address, such as dialed digits for voice, data, ISDN or
mobile networks, which cannot be routed directly. The SCCP translates this
number into a DPC and a subsystem number (SSN). The SSN identifies the SCCP
user at a signaling point.
MAN PGS: CHG-REMSSN.8.Z; CRTE-REMSSN.8.Z; DISPL-REMSSN.8.Z;
DLT-REMSSN.8.Z; DISPL-CPC.8q; DLT-CPC.8q; CRTE-CPC.8q;
CRTE-GT.8.Z; DISPL-GT.8.Z; DLT-GT.8.Z
7.3.3.
MML Configuration Procedure

Configuration details are provided in the system CIR. The required information
for OMNI configuration is the SS7 network structure:
x
Point codes to which the ISMSC connects directly
Number of links in each link set, and the SLC (signaling link code) of each
link
Point code of the ISMSC
Global title of the ISMSC
Point codes of all HLRs and MSCs in the network
Global titles of all HLRs and MSCs in the network
Global titles of all HLRs/MSCs in other networks with which the ISMSC
communicates
This information is required for MTP and SCCP and MAP configuration. MTP
and SCCP configuration is detailed below. MAP configurations are detailed in the
NYSMSMAP package configuration.
7.3.3.1. MML OMNI Configuration Of Links, Linksets And Routesets

This procedure configures the SS7 MTP layer. To determine the MML OMNI
configuration of links, linksets, and routesets, first determine the originating point
code (OPC), the destination PCs, and how the linksets are interconnected to the
ports and connected to the SS7 link boards.
In the following example of an MML configuration, assume that there are two
MSCs with PCs 111 and 222 and one HLR with PC 333. The SMSC PC is 444.
There is one SS7 link board, two link sets0 and 1, and two DPCs111 and 222.
Each set includes one link, with signaling link code 0.
NOTE:
Page 10-56
Every MML command ends with a ; (semicolon). After every entry of

an MML command, a confirmation prompt is displayed. Respond by
typing Y or N.

NOTE:
Chapter 10
Installation
In order to execute a list of commands in MML, a full path name of a

file containing MML may be specified. For example,
/home/ss7/conf/ss7.conf. MML reads all commands in the file and
executes them. It will present a confirmation prompt only for the
entire command file, and not for each command. It will report on the
completion status of each command in the file. MML commands can
also be entered from the smsc login (after the SMSC is installed), and
not only from the omni login.
To configure the SS7 MTP layer:

1.
At the login prompt enter omni.
2.
At the password prompt enter omni.
3.
To enter the MML utility, enter mml.
4.
To define the remote originating SMSC point code, enter

crte-ospc:pc=444,ni=nat0;
5.
To define the first link set with the concerned PC, enter
crte-lset:lset=lset0,pc=111;
6.
To define the link to the SS7 board, enter

crte-slk:slk=lnk0,lset=lset0,slc=0,speed=64k,port=0;
7.
To define the second link set with the concerned PC, enter
crte-lset:lset=lset1,pc=222;
8.
To define the link to the SS7 board, enter

9.
To define the first route set with the concerned PC, enter
crte-rset:rset=rset0,pc=111,rtes=lset0;
10.
To define the second route set with the concerned PC, enter
crte-rset:rset=rset1,pc=222,rtes=lset1;
11.
To activate the link to the SS7 board, enter alw-rset:rset=rset0;
12.
To activate the link to the SS7 board, enter alw-rset:rset=rset1;
13.
To save the configuration, enter backup-node;
14.
Define routes to the HLR through the two link sets:

crte-rset:rset=rset2, pc=333, rtes=lset0&lset1;
15.
To exit MML utilities, enter quit;
7.3.3.2. MML ISMSC Configuration of SCCP

This procedure configures the SS7 SCCP layer. For details on SCCP provisioning,
data storage and recovery, refer to Chapter 12.
Page 10-57
Chapter 10
Installation

In the following example of SCCP configuration, assume there are two MSCs with
PCs 111 and 222 and one HLR with PC 333, and global titles 123, 456, 789
respectively. Also assume the SMSC PC is 444 and its global title is 999.
7.3.3.3. Define Remote SSNs

After link sets and route sets are defined for each PC with which the SMSC needs
to communicate, define the remote SSN for this PC, and relevant SSNs (SSN=6
for HLR and SSN=8 for MSC). Use the following MML commands:
x
to define remote SSNs: crte-remssn:pc=<pc>,ssn=<ssn>;
to delete remote SSNs: dlt-remssn:pc=<pc>;
to display remote SSNs: displ-remssn;
To define remote SSNs:

1.
2.
3.
To enter the MML utility enter mml.
4.
To define the remote SSNs, enter

crte-remssn:pc=111,ssn=8;
5.
To verify the definitions, enter displ-remssn;

The following is displayed:
Point Code:
111 [0x6f]
Remote SSNs[1]:
8 [0x8]
Point Code:
222 [0xde]
Remote SSNs[1]:
8 [0x8]
Point Code:
333 [0x14d]
Remote SSNs[1]:
6 [0x6]
6.
If, at some point, MSC 111 is no longer used, delete its definition by typing
the command:
dlt-remssn:pc=111;
Page 10-58

Chapter 10
Installation
7.3.3.4. Define Concerned PCs

After a remote SSN is defined for each Point Code with which the SMSC needs to
communicate, define the concerned PC (CPC) for the PC with SSN=8 (the SSN of
the SMSC). Use the following MML commands:
x
To define concerned-PCs: crte-cpc:pc=<pc>,ssn=8;
To delete concerned-PCs: dlt-cpc:ssn=8;
To display concerned-PCs: displ-cpc;
To define CPCs:
1.
For two MSCs and one HLR as above, enter the following in the MML
utility:
crte-cpc:pc=111,ssn=8;
2.
To view the CPCs enter the command:

displ-cpc;

Display Concerned Point Code:
Local SSN:
8 [0x8] A
Replicated Point Code:
NONE
Concerned Point Codes[1]:
111 [0x6f] 222 [0xde] 333 [0x14d]
The delete command removes all CPCs of a given local SSN. The command
dlt-cpc:ssn=8; will delete all CPCs of SSN 8. In order to delete just one
CPC for a given SSN use chg-cpc. Refer to the TRILOGUE INfinity OMNI
CCS Manual.
7.3.3.5. Define Titles

Define global titles for all MSCs and HLRs, and for the SMSC. (A global title is a
string that identifies an SSN within a PC).
The MML commands to define/delete/display remote GTs are:
crte-gt:tt=0,dig=<dig>,pc=<pc>,ssn=<ssn>;
dlt-gt:tt=0,dig=<dig>;
displ-gt;
NOTE:
From Release 2.3 the default value of the National Address field is
National, and the International value of that field must be stated
explicitly. Therefore, NA=INT must be included in the following
commands.
Page 10-59
Chapter 10
Installation

To define global titles:

1.
To define global titles for the SMSC, enter the following:

crte-gt:tt=0,NA=INT,dig="999",pc=444,ssn=8;
2.
To define global titles, for two MSCs and one HLR, as in the example
above, enter in the MML utility:
NOTE:
3.
For GSM over ANSI systems, tt=10.
To view the global titles, enter the command:

displ-gt;

--- GLOBAL TITLE TRANSLATION --TRANSLATION TYPE
NUMBERING PLAN
NATURE OF ADDRESS
ISDN
NSN
DIGIT(S)
SSN
PC
123
111
456
222
789
333
999
444
BKUP_PC
4.
Visually verify the definition.
5.
If, at some point, MSC 111 is no longer used, delete its definition by typing
the command:
dlt-gt:tt=0,dig=123;
7.3.4.
6.
To save the configuration enter backup-node;
7.
To exit MML utilities, enter quit.
Configuration of the SCCP, TCAP and MAP Parameters in the

SMSC Configuration File(s) for GSM
The parameters listed in this paragraph must be defined as follows:
x
Page 10-60
MAP_SC_ADDRESS

Chapter 10
Installation
The map_sc_address parameter defines the SMSC global title in the

following format:
map sc address = 1 1 1 global title
The numerals 1 1 1 indicate an international number. This is fixed.
NOTE:
x
If this parameter is not defined correctly, the availability feature will

not work.
MAP_SC_POINT_CODE
The map_sc_point_code sets the value of the SMSC point code, in the
following format:
map_sc_point_code = 444
MAP_MSISDN2HLR_TABLE
If this keyword is not specified, the MSISDNs are used as global titles when
accessing the HLRs.
The value of the parameter is a table for translation of MSISDNs to HLR
addresses, formatted as a comma separated list of triplets, in the format
from-to:hlr. Each triplet matches a range of subscriber numbers (MSISDNs)
with the HLR that handles their information. The triplet 100200:9723690000 indicates that all MSISDNs starting with a number
between 100 and 200 (including 100 and 200) are handled by the HLR with
address 9723690000. If each HLR handles subscribers with a given prefix,
the triplet can be reduced to a pair: prefix:gt. The HLR addresses are treated
as international ISDN numbers (i.e. with type of number = 1 and numbering
plan = 1), and must therefore be specified with the international prefix.
Given an MSISDN the HLR that will be used is the one specified for the
FIRST entry in the table which matches this MSISDN. Therefore, the
longest prefixes should be specified first. If an MSISDN does not match any
of the ranges/prefixes specified in this table, the HLR addresses is taken to
be the MSISDN itself.
Example :
map_msisdn2hlr_table =
9723111 : 97230000 ,
97231-97233 : 97230001 ,
97234-97238 : 97230002 ,
97239 : 97230003
Notice that if 9723111 were not specified first it would have never been
used, because every MSISDN matching it would also match 7231-97233 and
so HLR 97230001 would have been used instead of 9723000.
MAP_TIME_ZONE
Page 10-61
Chapter 10
Installation

The map_time_zone parameter defines whether the time zone value is added
to the time stamp before sending the Forward SM message.
x
MAP_PROC
The map_proc parameter defines the map user procedures. These procedures
determine the routing method of the SMSC when interacting with the
various GSM peers/entities (HLRs, MSCs). Specifically, the routing method
to be used (route-on-dpc physical routing, or route-on-gt logical
routing) to send requests to the entity (hereafter called invoke a MAP
dialogue), and the GSM ph (I or II), that this entity supports are set here.
A set of profiles is defined. Each profile contains resources, and is used to
determine the behavior of a specific MAP dialogue between the SMSC and
another GSM entity, as described below.
Profile Selection
The decision which profile to use depends on the address of the peer used
for the operation (denoting an HLR or an MSC). The HLR is a common
prefix of the MSISDN, which it handles. The MSC is a derivative of the
HLR.
A profile is pointed to by a list of address prefixes. When invoking a MAP
dialog with address (MSISDN) X, the profile which is pointed to by the
longest matching prefix of X will be used. The selection of a profile is done
through the profiles addresses resource.
For example, suppose an operation is performed with number 123456, and
assuming the following definitions:
map_proc.prof1.addresses=11,12,13,14,15
map_proc.prof2.addresses=16,17,18,19
Then, the profile prof1 will be used, since 123456 matches prefix 12.
Note, that for dialogs vs the HLR (send_routing_info_for_sm,
report_sm_delivery_status) the MSISDN always contains the HLRs number
as prefix.
For dialogues vs the MSC (forward_sm) , the global title returned from the
HLR (via send_routing_info_for_sm) is used.
Resource Description
A profile contains resources. Each resource has a name and a value. The
values determine how the MAP dialog driven by the profile will behave.
The following resources are available:
Page 10-62
Version: GSM Version 1 or 2 (default=1)
dest_in_plmn

Chapter 10
Installation
The routing is according to dpc(1) or gt(0) (default=0). This affects the

routing indicator in the dest addr. For dest_in_plmn=0, routing is on Global
Title. For dest_in_plmn=1, routing-indicator field in SCCP address is DPC
(RI=DPC).
restart_allowed: Is restart from V2 to V1 allowed: 0 or 1 (default for

v1 is 0, and for v2 is 1).
timer: Invoke timer in seconds: integer > 0. The invoke timer defaults
to the maximum timer according to the specific service, as defined in
TS GSM 09.02.
time_zone: This parameter allows for the definition of varying time

zones for the MSCs that do not have the same local time. If this
parameter is defined, it is selected according to the MSC address
when the ISMSC is issuing the ForwardSM message. That means that
the message time stamp is adjusted to meet the local time zone of the
MSC.
Each resource may actually be specified at three levels:
Global for the entire profile: <profile>.<rsc>=...
For
a
specific
AC
(MAP
Application
Contexts):
<profile>.<ac>.<rsc>=... where <ac> is either sm_gateway (vs HLR),
or sm_relay (vs MSC).
For a specific procedure:<profile>.<proc>.<rsc>=...where <proc> is

srism (send-routing-info-for-sm), fsm (forward-sm), or rsds (reportsm-delivery-status).
A resource which is specified in the procedure level overrides the same

resource in the ac level which in turn overrides the global resources.
NOTE:
proc=srism or proc=rsds overrides ac=sm_gateway
NOTE:
proc=fsm overrides ac=sm_relay.
NOTE:
The timer resource should only be specified in proc context

using the command: map_proc.<profile>.<proc>.timer=x
NOTE:
The command map_proc.<resource>=x changes the default of

all resources that havent been otherwise defined.
The following commands cannot be used to specify the timer resource:

map_proc.<profile>.timer=x
map_proc.<profile>.<ac>.timer=x
For example: suppose an operation is to be performed using profile
v2_in_plmn (selected using the mechanism described above in Profile
Selection), and the resources for this profile are:
Page 10-63
Chapter 10
Installation

map_proc.v2_in_plmn.version=2
map_proc.v2_in_plmn.dest_in_plmn=1
map_proc.v2_in_plmn.sm_gateway.restart_allowed=0
map_proc.v2_in_plmn.fsm.timer=200
Then, when trying to interrogate an HLR using profile v2_in_plmn by a
send_routing_info_for_sm procedure, the version will be 2, with no restart
allowed (srism has sm_gateway as ac), routing-indicator field in SCCP
address is DPC (RI=DPC) since it is dest_in_plmn, timer=30 (as default in
09.02).
For a forward short message however, the version will be 2. Restart is
allowed (there is no override of the default, since sm_gateway is NOT the
AC of fsm). Routing-indicator field in SCCP address is DPC (RI=DPC)
since it is the dest_in_plmn. The invoke timer is set to 200 seconds instead
of the 10 minutes maximum in 09.02.
New Profile Definition
A new profile must first be added to the list of user-defined profiles, in the
parameter map_proc_user_configs, which contains a list of profile names,
separated by commas.
Note that there are two pre-configured default profiles in the system:
v1 - which has a version resource of 1
v2 - which has a version resource of 2
(All other resources of those profiles have default values, as explained

above in Resource Description.)
7.4.
Configuring the NYSMSIS41 Package

Before starting the customization, determine the HLRs and MSCs (including
GMSCs, in case inter-network roaming is implemented) to which the SMSC will
be connected.
NOTE:
Configuration of the NYSMSIS41 package is applicable to IS41

(GSM over ANSI) networks only. For the following procedures, a
basic knowledge of IS41C and SS7 concepts is assumed.
For each one of the above entities, determine the following:

x
Point-code (PC)
If the switch supports global title translation of MIN to HLR, then for each HLR:
x
Global-title (GT), with international prefix
SubSystemNumber (SSN) of HLR, MSC, SMSC. The values must be either:

HLR=5, MSC=5, SMSC=5 or
Page 10-64

Chapter 10
Installation
HLR=6, MSC=8, SMSC=11 or 5
7.4.1.
Configuration of the MTP (OMNI)

To configure the MSCs, HLRs, and SSNs, determine how the SMSC is connected
to all HLRs and MSCs (including GATEWAY MSCs (GMSCs) for international
roaming). Define the ospc, link sets, links, route sets, and Global Title of all HLRs
and MSCs and the SMSC accordingly from the systems CIR. Route sets should
be defined for all the DPCs of all HLRs and MSCs in the network.
The MTP element maintains the SS7 logical nodes own point code (PC). The
Platform provides commands for creating, deleting, and displaying the nodes own
point code.
NOTE:
References in the notes below (MAN PGS) refer to UNIX manual

pages.
MAN PGS: CRTE-OSPC(8q);

OSPC(8q)
CRTE-OSPC_s(8q);
DLT-OSPC(8q);
DISPL-
The MTP maintains a Link Set Table, containing the name and adjacent point
code of every link set for the logical node. The Platform provides MML
commands for creating, deleting, and displaying link sets in the Link Set Table.
MAN PGS: CRTE-LSET(8q);
DLT-LSET(8q);
DISPL-LSET(8q);
CLST(8q); DLT-CLST(8q); DISPL-CLSET(8q)
CRTE-
The MTP maintains a Link Table containing the name, logical port number, link
set, combined link sets, and signaling link code of every signaling link in the
logical node. The Platform provides commands for creating (including
specification of all parameters), deleting, and displaying signaling links in the
Link Table.
A routeset is a collection of the routes (link sets) over which a destination is
reachable. The MTP maintains a Route Set Table for every Destination Point Code
(DPC), containing the routeset name, destination point code, and all routes (link
sets) over which the destination is reachable from the logical node. The Platform
provides commands for maintenance of routesets as follows:
x
Creating (including specification of one or more link sets)
Adding one or more link sets to an existing routeset
Removing one or more link sets from an existing routeset
Deleting a routeset
Displaying a routeset
MAN PGS: CRTE-SLK(8q); DLT-SLK(8q); DISPL-SLK(8q); CRTE-RSET(8q);

CHG-RSET(8q); CHG-RSET(8q); DLT-RSET(8q); DLT-RSET-s(8q);
DISPL-RSET(8q)
Page 10-65
Chapter 10
Installation
7.4.2.

Configuration of the SCCP (OMNI)

The Signaling Connection Control Part (SCCP) provides connectionless and
connection-oriented network services. The SCCP is an MTP user that enhances
the MTP by providing connection-oriented and connectionless services.
Connectionless services transfer unit data, but provide no acknowledgments or
recovery procedures.
The SCCP augments the functionality of the MTP by permitting expanded
addressing capabilities. However the SCCP requires greater overhead. Thus, the
services of the SCCP are used only when needed. For applications requiring
connectionless message transfer with limited addressing capability, the MTP is
sufficient.
The routing capability of the MTP is limited to delivering messages to the correct
signaling point based on the DPC, and once there, forwarding the message to the
correct MTP user within the signaling point based on the value of the service
indicator contained within the signal information octet. The SCCP provides an
additional global title address, such as dialed digits for voice, data, ISDN or
mobile networks, which cannot be routed directly. The SCCP translates this
number into a DPC and a subsystem number (SSN). The SSN identifies the SCCP
user at a signaling point.
MAN PGS: CHG-REMSSN.8.Z; CRTE-REMSSN.8.Z; DISPL-REMSSN.8.Z;
DLT-REMSSN.8.Z; DISPL-CPC.8q; DLT-CPC.8q; CRTE-CPC.8q;
CRTE-GT.8.Z; DISPL-GT.8.Z; DLT-GT.8.Z
7.4.3.
MML Configuration Procedure

Configuration details are provided in the system CIR. The required information
for OMNI configuration is the SS7 network structure:
x
Point codes to which the ISMSC connects directly.
Number of links in each link set, and the SLC (signaling link code) of each
link.
Point code of the ISMSC.
Point codes of all HLRs and MSCs in the network.
Global titles of all HLRs (if global titles are required).
SubSystemNumber (SSN) of HLR, MSC, SMSC (should be either all SSNs

are 5, or HLR=6, MSC=8, SMSC=11).
This information is required for MTP and SCCP and MAP configuration.
Page 10-66

Chapter 10
Installation
7.4.3.1. MML Configuration Of Links, Linksets and Routesets

This procedure configures the SS7 MTP layer. To determine the MML OMNI
configuration of links, linksets, and routesets, first determine the originating point
code (OPC), the destination PCs, and how the linksets are interconnected to the
ports and connected to the SS7 link boards.
In the following example of an MML configuration, assume that there are two
MSCs with PCs 1-1-1 and 2-2-2 and one HLR with PC 3-3-3. The SMSC PC is
4-4-4. There is one SS7 link board, two link sets, 0 and 1, two DPCs, 1-1-1 and
2-2-2. Each set includes one link, with signaling link code 0.
NOTE:
Every MML command ends with a ; (semicolon). After every entry of

an MML command, a confirmation prompt is displayed. Respond by
typing Y or N.
NOTE:
In order to execute a list of commands in MML, the full path name of

a file containing MML may be specified. For example,
/home/ss7/conf/ss7.conf. MML reads all the commands in the file and
executes them. It presents a confirmation prompt only for the entire
command file, and not for each command. It will report on the
completion status of each command in the file. MML commands can
be entered from the smsc login (after the SMSC is installed), as well
as the omni login.
To configure the SS7 MTP layer:

1.
2.
3.
To enter the MML utility enter mml.
4.
Define the remote originating SMSC point code by entering:

crte-ospc:pc=4-4-4,ni=nat0;
5.
Define the first link set with the adjacent PC by entering:

crte-lset:lset=lset0,pc=1-1-1,type=A;
6.
Define the second link set with the adjacent PC by entering:

crte-lset:lset=lset1,pc=2-2-2,type=A;
7.
Create a combined link set to both adjacent PCs:

crte-clset:clset=clset01,lset=lset0&lset1;
8.
Define the link to the SS7 board by entering:

9.
Define the link to the SS7 board by entering:

10.
Define the first route set with the adjacent PC by entering:
Page 10-67
Chapter 10
Installation

crte-rset:rset=rset0,pc=1-1-1,rtes=clset01;
11.
Define the second route set with the adjacent PC by typing:

crte-rset:rset=rset1,pc=2-2-2,rtes=clset01;
12.
Activate the links by typing:

actv-lset:lset=lset0;
actv-lset:lset=lset1;
13.
Allow the routes by typing

alw-rset:rset=rset0;
14.
Save the configuration by entering:

backup-node;
15.
Define routes to the HLR through the two link sets:

crte-rset:rset=rset2, pc=3-3-3, rtes=clset01;
16.
Exit MML utilities by entering:

quit;
7.4.3.2. MML Configuration of SCCP

This procedure configures the SS7 SCCP layer.
In the following example of SCCP configuration, assume there are two MSCs with
PCs 1-1-1 and 2-2-2 and one HLR with PC 3-3-3. The HLR has global title
333333.
7.4.3.3. Define Remote SSNs

After link sets and route sets are defined for each PC with which the SMSC needs
to communicate, define the remote SSN for this PC, and relevant SSNs (either
SSN=5 for all, or SSN=6 for HLR and SSN=8 for MSC, SSN=11 for SMSC).
Use the following MML commands:
x
To define remote SSNs: crte-remssn:pc=<pc>,ssn=<ssn>;
To delete remote SSNs: dlt-remssn:pc=<pc>;
To display remote SSNs: displ-remssn;
To define remote SSNs:

1.
2.
At the password prompt enter: omni.
3.
Enter the MML utility by entering: mml.
4.
Define the remote SSNs by entering:
Page 10-68

Chapter 10
Installation
crte-remssn:pc=1-1-1,ssn=8; (or ssn=5)

5.
Verify the definitions by entering:

displ-remssn;

Point Code:
1-1-1
Remote SSNs[1]:
Point Code:
Point Code:
8 [0x8] A
3-3-3
Remote SSNs[1]:
6.
8 [0x8] A
2-2-2
Remote SSNs[1]:
6 [0x6] A
If, at some point, MSC 1-1-1 is no longer used, delete its definition by
entering the command: dlt-remssn:pc=1-1-1;
7.4.3.4. Define Concerned PCs

After a remote SSN is defined for each Point Code with which the SMSC needs to
communicate, define the concerned PC (CPC) for the PC with SSN=11 (or
SSN=5),the SSN of the SMSC. Use the following MML commands:
x
To define concerned-PCs: crte-cpc:pc=<pc>,ssn=11;
To delete concerned-PCs: dlt-cpc:ssn=11;
To display concerned-PCs: displ-cpc;
To define CPCs:
1.
For two MSCs and one HLR as above, enter the following in the MML
utility:
crte-cpc:pc=1-1-1,ssn=11;
2.
To view the CPCs enter the command:

displ-cpc;

Display Concerned Point Code:
Local SSN:
11 [0xB] A
Replicated Point Code:
NONE
Concerned Point Codes[1]: 1-1-1 2-2-2
3-3-3
Page 10-69
Chapter 10
Installation

The delete command removes all CPCs of a given local SSN. The command dltcpc:ssn=11; will delete all CPCs of SSN 11. (In order to delete just one CPC for
a given SSN use chg-cpc. Refer to the TRILOGUE INfinity OMNI CCS Manual.)
7.4.3.5. Define Global Titles

This stage is required if HLRs are accessed by global title translation of the MIN.
If not, the HLRs are accessed by point code, and the IS41_MIN2HLR_TABLE
resource of the ISMSC IS41-C package should be used (see Paragraph 7.4.4.).
Define global titles for all HLRs. (A global title is a string which identifies an
SSN within a PC).
To define a remote GT:
x
Enter crte-gt:tt=3,np=isdn-tel,dig=<dig>,pc=<pc>,ssn=<ssn>;.
To delete a remote GT:

x
Enter dlt-gt:tt=3,np-isdn-tel,dig=<dig>;.
To display a remote GT:

x
Enter displ-gt;.
To define global titles:

1.
Define global titles, for two MSCs and one HLR, as in the example above
by typing in the MML utility:
crte-gt:tt=3,np=isdn-tel,dig="333333",pc=3-3-3,ssn=6; (or 5)
2.
View the global titles by entering the command:

displ-gt;
3.
Verify the definition visually.
4.
Save the configuration by entering:

backup-node;
5.
Exit MML utilities by entering:

quit
7.4.4.
Configuration of the SCCP, TCAP and MAP Parameters in the

ISMSC Configuration File(s) for IS41-C
The configuration files are named is41_general_cfg and is41_proc_cfg and are
located in the configuration directory (site/config). The location of every
parameter below is specified in parenthesis.
The parameters listed in this paragraph must be defined as follows:
x
IS41_MC_TIME_ZONE
(in the general directory)
Time zone of the ISMSC in minutes from GMT.

x
Page 10-70
IS41_MIN2HLR_TABLE (in the general directory)


Chapter 10
Installation
If this keyword is not specified, the MINs are used as global titles when
accessing the HLRs.
The value of the parameter is a table for translation of MINs to HLR
addresses, formatted as a comma separated list of triplets, in the format
from-to:hlr. Each triplet matches a range of subscriber numbers (MINs) with
the HLR that handles their information. The triplet 100-200:5023690000
indicates that all MINs starting with a number between 100 and 200
(including 100 and 200) are handled by the HLR with address 5023690000.
If each HLR handles subscribers with a given prefix, the triplet can be
reduced to a pair: prefix:gt. The HLR addresses are treated either as
international ISDN numbers (i.e. with type of number = 1 and numbering
plan = 1), and in this case must be specified with the international prefix.
Or, as point codes in the following syntax: nnn-ccc-mmm. Given a MIN the
HLR that will be used is the one specified for the FIRST entry in the table
which matches this MIN. Therefore, the longest prefixes should be specified
first. If an MIN does not match any of the ranges/prefixes specified in this
table, the HLR addresses is taken to be the MIN itself.
Example:
map_msisdn2hlr_table =
5023111 : 4-4-4
In this example, all subscriber are routed to the single HLR using its point
code.
x
IS41_PROC.USE_GT
(in the proc directory)
When using point codes in the MIN2HLR table, this should be set to NO.
Otherwise, it should be set to YES.
x
IS41_PROC_USER_CONFIGS = GROUP1, GROUP2, GROUP3 ...(in the

proc directory)
IS41_PROC.GROUP1.PCS(in the proc directory)
IS41_PROC.GROUP1.TIME_ZONE

By defining groups of MSCs having the same time zone, it is possible to set the
time stamp of the message according to the time zone where the subscriber is
located. The PCS keyword is a list of point codes, and the time zone is the
difference in minutes from the SFE system time.
Example:
# MSCs 9-9-9 and 9-8-7 are one hour different from the ISMSC
IS41_PROC.GROUP1.PCS = 9-9-9. 9-8-7
Page 10-71
Chapter 10
Installation

IS41_PROC.GROUP1.TIME_ZONE = 60
7.5.
Disabling and Enabling the Mobile Originated Feature

The MO feature is installed as part of the MAP package. By default the MO
feature is enabled.
To disable the MO feature:
1.
Log in to one of the SFE machines as smsc.
2.
Enter the command

smsc remove_ei MAPMO 1
3.
Enter the command

smsc remove_ei MAPMO 2
4.
Enter the command

smsc distrib_config installed_eis
5.
Restart both SFEs and OMNIs.
To enable the Mobile Originated feature:

1.
2.
Enter the command

smsc install_ei MAPMO 1 <map-host-1>
where <map-host-1> is the name of the first MAP machine, usually smsc1.
3.
Enter the command

smsc install_ei MAPMO 2 <map-host-2>
Where <map-host-2> is the name of the first MAP machine, usually smsc2.
4.
Enter the command

5.
7.6.
Restart both SFEs and OMNIs.
Configuring Status Report Request Receipt Messages

Status Report Request (SRR) messages are used to send receipt messages to phase
I handsets. There are two steps in defining the receipt messages:
x
Defining the languages and their indicators used for the receipt
(Paragraph 7.6.1.)
Defining the format of the messages (Paragraph 7.6.2.)
Page 10-72

7.6.1.
Chapter 10
Installation
Defining Receipt Languages

Up to 254 languages can be defined. Languages are defined in the configuration
parameter mo_srr_list in the map.config file. Also defined is the symbol used to
invoke each language in the GSM/MAP MO EI. The symbols, when found at the
beginning of an MO message text, are interpreted as an SRR for a specific
language. The parameter has the following format:
SRR-sign-1 [ : lang-ID-1 ] [, SRR-sign-2 : lang-ID-2 ...]
where:
SRR-sign-x
is the specific symbol for that language
lang-ID-1
is the name given to the language
For example, the parameter:

mo_srr_list = ! : english, ## : chinese_trad, @ : italian
indicates that a subscriber must start a message with ! to request a receipt in
English, ## to request a receipt in traditional Chinese, and @ to request a receipt
in Italian.
The supported languages/character sets are those defined in the file
/home/smsc/infra.1.1/config/config. The languages currently supported are
English, simple Chinese, and traditional Chinese. English can be used for most
European languages. The default language is English. Thus, the following
parameter:
mo_srr_list = ! , ## : chinese_simp
specifies that ! uses English.
7.6.2.
Defining Receipt Messages

The configuration file /home/smsc/site/config/predef_msgs/notifications creates
templates for MO receipts.
A predefined messages file has the following format:
lang1
# template11
# template12
lang2
# template 21
# template 22
where langn is one of the languages specified in the mo_srr_list, or the default if
only one is listed.
The following variables can be set in the message:
Page 10-73
Chapter 10
Installation

$datetime and date of the short messages final state

$rcpthe recipients number (destination of the original SM)
For example:
English
11 Message to $rcp delivered successfully
12 Message to $rcp could not be delivered
chinese_trad
21 [the same in Chinese]
22 [the same in Chinese]
The system comes with the following default file:
default
1 $date delivery to $rcp succeeded
2 $date delivery to $rcp failed
7.6.3.
Authorization of Message Originators (Black and White Lists)

MO messages are filtered according to the prefix of the originating address. If a
message does not match the allowed prefixes, it is rejected by the SFE and an
error is returned to the mobile, by a MAP_FORWARD_SM message with user
error set to GSM_MAPERR_SM_DELIV_FAILURE (32). This is controlled by
the following configuration parameters located in the file site/config/sfe.config:
adrtrn_authorize_prefix
A list of prefixes indicating which subscribers are allowed

to send messages.
adrtrn_prefix_list_type
The type of the authorization list, which could be a black

list (where a prefix that is specified is considered illegal)
or a white list (where a prefix that is not specified is
considered illegal).
adrtrn_prefix_list_elm_len
The length of each prefix in the authorization list.
NOTE:
7.7.
All prefixes must be of the same length.
Enabling the FTP of Statistics Files

To enable the FTP of statistics files:
1.
Log in as root.
2.
Enter the command:

passwd -x -1 smsc
3.
Page 10-74
Enter the command:

Chapter 10
Installation
passwd smsc_ftp
4.
Enter the password, twice:

smsc_ftp
smsc_ftp
5.
Enter the command:

passwd -x -1 smsc_ftp
7.8.
Post Installation Procedures

At the completion of the package installation:
1.
Start keep alive messages to the hub by logging in as smsc and enter the
command smsc pinger &.
2.
To start the SMSC, login as smsc and enter smsc control start -this. This
command is executed on each drawer.
3.
If OMNI is down, start OMNI by entering go. To start the MAP EI, login as
smsc, then enter
smsc control start map-1
The OMNI startup starts the MAP EI.

NOTE:
8.
Automatic startup of the SFE is controlled by a configuration variable

START_ON_BOOT (refer to Paragraph 7.).
ShortEmail Installation
ShortEmail is distributed as a separate package called NYSMSMAIL. The
NYSMSMAIL package is installed after the ISMSC is installed.
The NYSMSMAIL package contains an Email Server (Sendmail based) and an
Email EI. The Email server is installed on an IMU platform. The Email EI is
installed on the ISMSC platform. Both platforms are based upon a Pentium PC
running Unixware 2.1.2. In the case of a redundant ISMSC, the Email EI is
installed on both ISMSC platforms.
After a successful installation of the NYSMSMAIL package, a patch that resides
on the same magnetic media should also be installed. The patch exists in a
package called NYSMSEP1, and should be installed on every platform that the
NYSMSMAIL package was installed on.
8.1.
Installing the Email Server

The Email Server is installed on a Pentium PC running Unixware 2.1.2.
To install the Email server:
1.
Log in as root on the IMU machine.
Page 10-75
Chapter 10
Installation

2.
Insert the installation tape into the drive.
3.
Check if the NYSMSBASE package is installed by entering:

pkginfo | grep NY
4.
If the NYSMSBASE package is not installed, then install by entering:

pkgadd -d /dev/rmt/ctape1
5.
Install the NYSMSMAIL package by entering:

6.
7.
During the installation, the following parameters need to be configured:

a.
The official domain name for this site. Specify a name that identifies
the Email server. The domain name is the domain part of the
subscribers email addresses.
b.
Whether there is an Internet connected SMTP server, which is an

email (SMTP) server through which email (error messages) are sent to
the outside world (Internet).
c.
The host name of the Internet connected SMTP server, if one exists.
Install the NYSMSEP1 package by entering:

8.
Log in as smsc on the IMU machine.
9.
Configure the email server by entering:

smsc custom SENDMAIL
The following parameters can be modified:
Page 10-76
SM composition pattern
The format of the short message. Default is:

%n(%s:20)%a%t.
Maximal SM length
The maximum length of a short message. Messages

longer than this value will be truncated. The default is
160 characters.
Subscribers prefix
A prefix to be added to the address (phone number)

before sending to the ISMSC. No default is available.
Email EIs port number
Port number used by the Email EI. Default is 3535.
Email2Sms scripts port

number
Port number used by the Email parsing module.

Default is 2525.
Domain Name
A name that identifies the Email server. This is the

domain part of the Email addresses of the subscribers.
Allow Attachments
Whether attachments are valid or non-valid.

Whenever they are not valid, such an email will be
automatically rejected.

Maximal Email Size
10.
Chapter 10
Installation
The maximal allowed email size. Emails that exceed

this size should be rejected.
Edit the file sendmail.cf by entering:

vi ~/site/sendmail/sendmail.cf
11.
Find the Timeout.indent parameter by pressing:

/#O Timeout.ident<CR>
12.
Enable the parameter and set it by pressing:

x16lx
Now the line should read

O Timeout.ident=0s
13.
Save the file by pressing:

:wq<CR>
14.
Repeat step 10 for ~/site/sendmail/sendmail.cf.empty.
15.
Restart the IMU machine.
16.
Perform the email server verification instructions (refer to Paragraph 8.3.).

It may be possible that another SMTP server is running.
17.
If another SMTP server is running, check where the other server is located:
a.
Enter the following commands:

ps -ef | grep sendmail
ps -ef | grep smtpd
b.
Log in as root.
c.
Enter the command:

mv otherserver otherserver.sv
d.
8.2.
Reboot the IMU machine.
Installing the Email EI

To overcome file system space problems during installation, transfer the package
from the installation tape to a temporary directory prior to the installation. Then
install the package and remove the temporary directory:
To install the Email EI:
1.
Log in as root on the SFE machine.
2.
Make sure that the NYSMSBASE package is installed using the command:
pkginfo | grep NY
3.
Make sure that both active and standby computers are up.
4.
Enter the command mkdir -p /home/pkgs.
Page 10-77
Chapter 10
Installation

5.
6.
Enter the command pkgtrans /dev/rmt/ctape1 /home/pkgs.
7.
Install the NYSMSMAIL package by entering

pkgadd -d /home/pkgs.
During the installation procedure, select only the Email EI option.

8.
Install the NYSMSEP1 package by entering:

pkgadd -d /home/pkgs.
9.
If the ShortEmail system should support languages other than English, the
SFE should be configured to identify the dominant language. This
configuration handles the translation of an Email with an unknown language
(not English). Such Email might be received when the user composes the
Email using an English Email client.
The configuration is performed by writing the following line in the
ei.EMAIL.config file within the SFE configuration directory:
ei.EMAIL.language=<language_id>
where <language_id> is the language ID of the requested language (e.g. 259

for Traditional Chinese).
10.
In case of an ISMSC medium configuration (SFE and MAP installed on the

same machine), log in as omni on the current machine and stop the OMNI
processes by entering:
Terminate 0
11.
8.3.
Reboot the ISMSC machines.
Verifying the Email Server Installation

To verify that Email Server installation:
1.
Start the ISMSC on all computers. After a few minutes run the command
smsc control check all
2.
Verify that all parts of the ISMSC (including the EMAIL) are defined
correctly and are up and running. By default, EMAIL.1:1 and EMAIL:1.2
should be up and running.
3.
Enter the command:

smsc control status sfe
4.
In the result report, verify that EMAIL:1 and EMAIL:2 are connected.
5.
Log in as smsc on the IMU.
6.
Enter the command:

ps ef | grep sendmail
and verify that SENDMAIL is running.
Page 10-78

7.
Chapter 10
Installation
Enter the command:

ps ef | grep email2sms.pl
and verify that email2sms.pl process is running.

8.
Enter the command:

telnet localhost 25
Verify that there is a connection to the Email server.
8.4.
9.
Verify that the Email server name is as configured.
10.
Enter quit to disconnect.
Fallback Instructions
To fall back to the original version on the Email server and Email EI computers:
1.
Log in as root.
2.
Remove the installed packages using the commands:

pkgrm NYSMSEP1
pkgrm NYSMSMAIL
9.
IPOS Installation
9.1.
Preparation for IPOS installation (Paragraph 9.1.)
Installing the IPOS (Paragraph 9.2.)
Configuring the IPOS (Paragraph 9.3.)
Verifying the IPOS Installation (Paragraph 9.4.)
Preparation for IPOS Installation

Prepare the following information for use during the installation process:
x
First server nameThe ISMSC first servers IP address or name.
Second server nameThe ISMSC second servers IP address or name.
Users NameThe default is taken from the Windows installation.
Users CompanyThe default is taken from the Windows installation.
Destination DirectoryThe main installation directory of the application.

The default is Comverse.
Language or languages to be supported if custom installation is chosen.
Program FoldersThe name of the folder which holds the application

icons. The default is ISMSC Paging Operator Station.
Page 10-79
Chapter 10
Installation
9.2.

Installing the IPOS

Two steps are required for installation of the IPOS:
9.2.1.
Installing the server side of the IPOS application once on the ISMSC.
Installing the client IPOS application on a Windows 95 based PC.
Installing the IPOS Server

The server side is installed on the SFE machine. In a redundant ISMSC, it is
installed on both SFE machines.
To install the IPOS Server side:
1.
On the ISMSC, log in as root.
2.
Verify (or create) a temporary directory by entering the command:

mkdir -p /home/pkgs
9.2.2.
3.
4.
Enter the command pkgtrans /dev/rmt/ctape1 /home/pkgs
5.
Install the NYSMSOPER package by entering pkgadd -d /home/pkgs
Installing the IPOS Client

To install the IPOS client application on a PC:
1.
Check the Readme file in the program folder for any late-breaking changes.
2.
Insert the installation diskette #1 in the diskette drive.
3.
Activate the setup program:

a.
Select Run from the Start menu.
b.
Type A:\setup and press <Enter>. The Wizard Setup progress window
appears.
4.
Fill in information as requested during the installation process.
5.
Insert installation diskette #2 when requested.
6.
On completion of the installation process, confirm that the IPOS icon has
been created and is functional.
For details of network installation, refer to the Readme file found in the program
folder.
9.3.
Configuring the IPOS

This section describes how to choose the environment language and specify server
and message parameters.
Page 10-80

9.3.1.
Chapter 10
Installation
Defining Server Parameters

To set the required server parameters:
1.
From the Setup menu, click Server. The Server Options dialog box appears
(refer to Figure 10-5).
Figure 10-5: Server Options Dialog Box

2.
Set the required parameters as described in Table 10-9.
Table 10-9: Server Options Dialog Box Controls

Control
Description
Primary Server
Name
The User defined Server name or the IP address of the providers first
ISMSC server.
Second Server
Name
The User defined Server name or the IP address of the providers

second ISMSC server.
Server Port
The providers port number on the connected server.
3.
9.3.2.
Click OK to accept the settings and close the dialog box, or click Cancel to
close the dialog box without accepting the changes.
Defining Message Parameters

To define Message Setup parameters:
1.
From the Setup menu, select Message. The Message Setup dialog box
appears (refer to Figure 10-6).
Page 10-81
Chapter 10
Installation

Figure 10-6: Message Setup Dialog box

2.
Set the required parameters as described in Table 10-10.
Table 10-10: Message Setup Dialog Box Controls

Control
Description
Phone Number
Length
Defines minimum and maximum allowable values for character string

lengths of phone numbers (not including prefix).
Full Message
Length
Defines the maximum allowable number of characters in a message.
Visible Prefix
Number
Defines the area code, a company code (e.g. of a mobile phone

company), or another defined code. When Enabled is checked, the
Visible Prefix is displayed in the Main window. The Visible Prefix
value has no effect on the recipients phone number.
Non Visible
Prefix Number
The Non Visible prefix is an internal ISMSC code, defined by the

ISMSC system. This value, e.g. an area code, is added to the
recipients phone number. When Enabled is checked, this value is
embedded in the target phone number upon message delivery.
For example, if the target phone number is (212)313454, the nonvisible prefix is 212, the phone number portion is 313454 and the
message is sent to 212313454.
3.
9.3.3.
Click OK to accept the settings and close the dialog box; or click Cancel to
close the dialog box without accepting the changes.
Changing the Environment Language

The IPOS application includes a National Language Support option, which
permits the user to choose between the supported languages, as defined at setup.
Currently supported languages are:
x
English
Arabic
Page 10-82

Simplified Chinese
Traditional Chinese
Chapter 10
Installation
To change the current language:

1.
From the Language menu, select the required language. The system
responds by permitting the user to compose and send messages in the
required language to the ISMSC. While updating the language, the system is
disconnected from the ISMSC server.
2.
To reconnect to the ISMSCs server, perform one of the following:

x
Click Connect.
From the File menu select Connect.
Press the <Ctrl>+<T> key combination.
NOTE:
9.4.
Ensure that the Server and Port parameters are configured correctly
before connecting (refer to Paragraph 9.3.1.)
Verifying the IPOS Installation

A Windows 95 folder named Comverse (or any other name specified during the
installation process) now exists that contains two items:
x
A readme file
The IPOS application
To verify the IPOS installation:
10.
1.
Activate the IPOS application, and press the connect toolbar button. The
application is connected to the ISMSC if the disconnect and send toolbar
buttons are enabled while the connect toolbar button is disabled.
2.
When the IPOS is connected to the ISMSC, type the MS number existing in
the network in the appropriate field. Send a message with free text to the
mobile subscriber.
Web Access Installation

Web Access is distributed as a separate package called NYSMSWEB. Install the
ISMSC prior to installing the NYSMSWEB package. The NYSMSWEB package
contains a Web server (Apache based) and a Web EI. The Web server is installed
on an IMU platform and the Web EI is installed on an ISMSC platform. Both
platforms are based on a Pentium PC running Unixware 2.1.2.
10.1.
Installing the Web Server

x
Web server installation (Paragraph 10.1.1.)
Page 10-83
Chapter 10
Installation

Configuring Web ISMSC routing (Paragraph 10.1.2.)
10.1.1. Web Server Installation

The Web Server is to be installed on a Pentium PC running Unixware 2.1.2.
To install the Web server:
1.
Log in as root on the IMU machine.
2.
3.
Check if the NYSMSBASE package is installed by entering:

pkginfo | grep NY
4.
If the NYSMSBASE package is not installed then install it by entering:

5.
Install the NYSMSWEB package by entering:

6.
Log in as smsc and configure the Web server by entering:

smsc custom APACHE
The following parameters can be modified:

Web Server's port number
The TCP/IP port number on which the Web server listens for new
connections. Must be greater than the value1024, default is 8080.
Web EI's port number
The TCP/IP port number on which the Web EI listens for connections
from the Web server. Must be greater than 1024, default is 3401.
Company name
The name of the service provider is displayed on the Web Page. Default
is Netology.
Non-Visible prefix
A prefix that is not displayed on the screen and is added to the

subscriber number entered by the user before sending to the ISMSC.
There is no default.
Visible prefix
A prefix for the subscriber number that is displayed on the screen. This
prefix is not passed to the ISMSC as part of the subscriber number.
There is no default.
Mobile Number Length
Maximal length of a subscriber number (in characters). It does not

include any prefix. Default is 6.
Maximal SM's length
The maximal length of a short message text. Default is 160.
Success HTML File
A name of an HTML file to be displayed when a message is accepted by

the ISMSC for delivery. If none is specified then an application default
is used.
Page 10-84

Chapter 10
Installation
Failure HTML File
A name of an HTML file to be displayed when it is not possible to send

a message. If none is specified then an application default is used.
Language Support
If support for languages other then English is required. Default is NO. If

YES is entered then there is a need to specify the languages and their
codes.
7.
Restart the IMU machine only.
8.
Further customization of the Web page of sending SM is possible.

This may be done by manually editing the HTML files send_sm.html.empty
and language.html.empty in the site/httpd/htdocs directory and running
again:
smsc custom APACHE
NOTE:
Irresponsible changes of this file can damage Web to SMS

functionality. Changes are to be performed by HTML knowledgeable
personnel only.
10.1.2. Configuring Web ISMSC Routing

The Web ISMSC Routing feature provides a means of routing incoming messages
from the Web Server to an unlimited number of ISMSC computers. The Web
server evaluates incoming messages according to the routing table. Messages are
routed according to the MSISDN and are directed to the corresponding computer
name and its port.
In the case of a non-redundant EI, the message is routed to one EI only. In the case
of a redundant EI the message is routed to the Main EI. If it encounters a failure it
is routed to the alternate EI.
The routing table is implemented as one configuration parameter named
msisdn2web_ei, in the file site/config/APACHE.config.
The routing table is composed of lines in the following formats:
<MSISDNs>
<Port number>; <Main Web EI>; <Alternate Web EI>
<MSISDNs>
<Port number>; <Main Web EI>
where:
<MSISDNs>: has two possible formats:
x
<prefix>: All MSISDNs starting with this prefix
<prefix1>-<prefix2>: All MSISDNs starting with the range of prefixes

including prefix1 and prefix2
<Port Number>: The corresponding Web EIs port number

<Main Web EI>: The corresponding main Web EIs host name
<Alternate Web EI>: The corresponding alternate Web EIs host name (if it exists)
Page 10-85
Chapter 10
Installation

The first match in the table from the top down is the match that is used. Therefore,
the longest prefixes should be specified first.
Example:
All messages that are sent to MSISDNs starting with a number between 521 and
525 (inclusive) are routed to the Web EI on smsc1, which listens to port 3400. If
its not available (e.g. host down, Web EI is down etc.), the messages are routed to
the Web EI on smsc2, on the same port (3400).
All messages that are sent to MSISDNs starting with 53 are routed to the Web EI
on smsc3, which listens to port 3401. This Web EI works on a standalone
system, i.e. there is no alternate Web EI.
521-525 :
53 :
10.2.
3400; smsc1; smsc2
3401; smsc3
Installing the Web EI

To overcome file system space problems during installation, transfer the package
from the installation tape to a temporary directory prior to the installation. Then
install the package and remove the temporary directory.
To install the Web EI:
1.
Log in as root on the SFE machine.
2.
Make sure that the NYSMSBASE package is installed using the command:
pkginfo | grep NY
3.
Make sure that both active and standby computers are up.
4.
Enter the command:

mkdir -p /home/pkgs
5.
6.
Enter the command:

pkgtrans /dev/rmt/ctape1 /home/pkgs
7.
Install the NYSMSWEB package by entering:

pkgadd -d /home/pkgs
(Select the option of Web EI only)

8.
In case of an ISMSC medium configuration (SFE and MAP installed on the

same machine), log in as omni on the current machine and stop the OMNI
processes by entering:
Terminate 0
9.
Page 10-86
Reboot the ISMSC machines.

10.3.
Chapter 10
Installation
Web Installation Verification Instructions

To verify the Web installation:
1.
Start the ISMSC on all computers. After a few minutes run the command:
smsc control status sfe
Verify in the result report that Web:1 and Web:2 are connected.
10.4.
2.
Log in as smsc on the IMU platform.
3.
Enter telnet localhost 8080 (or other port number if configured) and verify
the connection to the Web server.
4.
Enter quit to disconnect.
Web Installation Fallback Instructions

To fall back to the original version on the Web server and Web EI computers:
1.
Log in as root.
2.
Remove the package using:

pkgrm NYSMSWEB
10.5.
Configuring the Web Server Applications

Both Corporate and Mass Market versions of the Web Access application share
the basic configuration parameters listed in Table 10-11.
Table 10-11: Web AccessGeneral Parameters
Parameter
Description
HostName
IP addresses of the ISMSC system
AltHost
Port
Port used to access the ISMSC
HttpServer
IP address of computer hosting the Web Access application
MsisdnToWebEIFile
Location and filename of the Routing Table file
ValidTime
Maximum idle time for an open session, in minutes
OdbcDSN
Parameters controlling access to the local database

application on the Web Access unit: pointer to database,
user ID, and password
OdbcUID
OdbcPWD
Page 10-87
Chapter 10
Installation

Parameter
Description
VirtualDir
Path to Web server application on the local Web Access

unit
ApplPath
MaxMsgs
Maximum number of personal message texts each user can

store.
MaxRcpts
Maximum number of entries in each users personal

address book
MaxGroups
Maximum number of mailing groups that can be defined in

each users personal address book
MaxPublicMessages
Maximum number of stored message texts available to all

users
MaxPublicRecipients
Maximum size of public address book
MaxPublicGroups
Maximum number of mailing groups that can be defined in

the public address book
MaxPersonalGroupMembers
Maximum number of addressees in each personal mailing

group
MaxPublicGroupMembers
Maximum number of addressees in each public mailing

group
MaxRcptsOneMsg
Maximum number of recipients for each message. Mailing

groups do not count as a single recipient; each addressee of
a group counts as an individual recipient.
MaxSentMessages
Rollover maximums for systems internal counters. These

parameters do not limit performance.
MaxSessionID
MaxEmailLen
Maximum length of the Email Address field, in characters
MaxFirstNameLen
Maximum length of the First Name field, in characters
MaxLastNameLen
Maximum length of the Last Name field, in characters
MaxNickNameLen
Maximum user nick name/alias
MaxPwdLen
Maximum and minimum password length
MinPwdLen
PhoneLen
Page 10-88
Length of valid phone numbers

Chapter 10
Installation
Parameter
Description
AreaCodes
Area Codes recognized as cellular networks
ComverseLogoLink
Web addresses of on-screen links to Comverse and

Netology
NetologyLogoLink
DefaultLanguage
Default Language of system operation
SmscErr0
Parameters used to map ISMSC error codes to appropriate

text displays in the String Table
SmscErr1
...
SmscErr10
SmscErrDefault
LogFilesSavePeriod
Time period, in days, that log files are retained for

download
SepChar1
Parameters used to specify unique delimiter characters.

These characters are used when parsing and formatting
message texts.
...
SepChar7
Because the Mass Market Web Access application is open to all Internet users, it
incorporates special security features. Table 10-12 describes the parameters that
control these features.
Table 10-12: Web AccessAbuse Prevention Parameters for Mass Market
Application
Parameter
Description
PreventionofAbuse
Activates abuse prevention features such as passworded login.

Valid values are 1 (abuse prevention activated) and 0 (no abuse
prevention).
ValidSessionTime
Maximum idle time for an open session, in minutes
MsgLimit
SendPeriod
Together, these parameters define maximum messaging activity for

an account. Users cannot send more that MsgLimit number of
messages within SendPeriod hours.
AccountDuration
Maximum length of time inactive accounts are retained, in days
Page 10-89
Chapter 10
Installation

Both Corporate and Mass Market Web Access applications refer to a Routing
Table file. This file lists ISMSC ports and server addresses associated with
telephony prefixes. Typical contents of a Routing Table file are show below.
misisdn2web=
052 : 3401; 130.1.60.101; 130.1.60.101
054 : 3401; 130.1.60.101; 130.1.60.101
In this example, the telephony prefixes are 052 and 054, and the target port of the
ISMSC is 3401.
10.6.
Multiple Language Support

For each language supported by the system, the Web Access application creates a
separate directory of language-related configuration files. There are two primary
language handling files:
11.
A file of language-specific parameters such as language direction (left to

right or right to left). This file is named <Language>Params.cfg for each
language.
A String Table of text strings displayed by the Web Access application.

These include prompts for information, error messages, and field names.
The default string table file contains English strings. For each language
supported, the file must be copied and edited, replacing the English strings
with their equivalents in the supported language.
SMPP Installation
The NYSMSSMPP package is installed on the ISMSC platform, after installing
the ISMSC. On a redundant ISMSC, the NYSMSSMPP package is installed on
both ISMSC platforms. Prior to the installation the package should be transferred
from the installation tape to a temporary directory. The package is then installed,
after which the temporary directory can be removed. This prevents file system
space problems during installation.
11.1.
Installing the SMPP

To install release SMPP 1.1:
1.
On the ISMSC, log in as root.
2.
Verify that the NYSMSBASE package is installed using the command:

pkginfo | grep NY
3.
Verify that both the active and standby computers are up.
4.
Enter the command mkdir -p /home/pkgs.
5.
Insert the installation DAT tape into the tape drive.
Page 10-90

Chapter 10
Installation
6.
Enter the command pkgtrans /dev/rmt/ctape1 /home/pkgs.
7.
Install the NYSMSSMPP package and type pkgadd -d /home/pkgs.
8.
Log in as smsc and configure the SMPP by typing smsc custom SMPP.
The following parameters may be modified:
SMPP Keep-Alive delay time: The time period (in seconds) between which
the SMPP EI sends the enquire_link command to the ESME. A value of 0
means never send.
Valid values: 0 or any positive integer
Default: 0
SMPP Keep-Alive timeout: The period of time (in seconds) the SMPP EI
waits for an enquire_link_resp before it closes the connection to the ESME.
Valid values: Any positive integer
Default: 15
EI's port number: The TCP/IP port number on which the EI listens for a
connection from an ESME.
Default: 3700
SMPP Password: A password that should be passed by the ESME to the
SMPP EI in the bind commands.
Default: smsc
SMPP System ID: A system identifier that should be passed by the ESME
to the SMPP EI in the bind commands.
Default: netology
9.
Modify the line in the file /home/smsc/.nyappl/smsc.SMPP (which is a

symbolic link to smsc.smpp.2.1) from:
smpp.2.1:usrlocal.1.0:infra.1.1:smsbase.2.3
to:
smpp.2.1:usrlocal.1.0:infra.1.2:smsbase.2.4
10.
11.2.
Reboot the ISMSC platforms.
Verifying the SMPP Server Installation

To verify the SMPP installation:
1.
Start the ISMSC on both computers.
2.
After a few minutes, enter the command smsc control check all.
Verify that all parts of the ISMSC (including the SMPP) are defined
correctly and are up and running. By default, SMPP.1:1 and SMPP:1.2
should be up and running.
Page 10-91
Chapter 10
Installation
3.

Enter the command smsc control status sfe.

Verify in the report that SMPP:1 and SMPP:2 are connected.
12.
Additional Configuration of EIs

This section contains the following topics:
12.1.
Notification transaction logs (Paragraph 12.1.)
Flow control (Paragraph 12.2.)
Target EI routing (Paragraph 12.3.)
Configuring MO routing (Paragraph 12.4.)
Configuring the MO address translation feature (Paragraph 12.5.)
Configuring Bi-Directionality of EIs (Paragraph 12.6.)
Notification Transaction Logs

When a connection to a source EI is down, the SFE writes the notifications
addressed to the source EI to non-volatile disk memory for later delivery.
The SFE stores these undelivered notifications in a Transaction Log separate from
the general database. The messages are stored per EI group, and not per
subscriber. Because all EI instances of a specific EI handle the same data, the
connection is declared down only when all instances of the EI are down. One
Transaction Log stores notifications for the entire EI group.
When a connection to a source EI is established, the SFE delivers the queued
messages for this EI. New incoming notifications are appended to the queue in
order to maintain a first-in-first-out behavior towards the EI.
The SFE periodically scans the Transaction Logs, removing expired notifications.
A validity period can be configured for Transaction Logs. Undelivered
notifications that have been stored longer than the validity period are removed
from the Transaction Log. By default, the SFE scans the Transaction Logs every
five seconds. This scanning frequency is configurable.
Transaction Logs are mirrored on the standby SFE, so that they are not lost in
system restart or switchover.
Table 10-13 details the configuration parameters for Transaction Log storage and
notification retries from Transaction Logs. These parameters are set in the EI
configuration files. EI configuration filenames have the format ei.<eitype>.config
and are stored in the SFEs config directory.
Page 10-92

Chapter 10
Installation
Table 10-13: Notification Transaction Log Parameters

Parameter
Description
max_segments
Maximum number of Transaction Log segments that can be

open simultaneously.
Default value: 1024
segment_len.
Maximum segment length for each Transaction Log. Default

value: 40960
notification_expiration
Validity period for notifications stored in the Transaction Log.

Default value: 1440 minutes
sei_retry_interval
Specifies retry profile for delivery of stored notifications to the

source EI.
Default value: 2,5,fail (2 minutes, 5 minutes, then the
notification is deleted from the Transaction Log)
12.2.
Flow Control
A flow control mechanism can be used to limit the load on the SFE from source
EIs. The maximum incoming messages per second that each EI can send is
configurable. If a source EI generates more incoming messages than the defined
rate, the messages are not handled by the SFE. The source application receives a
standard TCP/IP indication that the SFE is blocking its input.
Table 10-14 details parameters controlling traffic flow for the EI group. These
parameters are set in the EI configuration files. EI configuration filenames have
the format ei.<eitype>.config and are stored in the SFEs config directory.
Table 10-14: Flow Control Parameters
12.3.
Parameter
Description
receive_delay
specifies a minimum period of time (in miliseconds) between two consecutive

blocks of incoming messages.
receive_limit
specifies a maximum number of messages in a block of incoming messages.
Target EI Routing
The SMSC supports a number of target EIs running simultaneously. Provisioning
parameters can restrict delivery to target EIs explicitly provisioned for a specific
subscriber (refer to Chapter 5, Paragraph 2.).
Page 10-93
Chapter 10
Installation

Target EIs can be configured to support this per-subscriber verification, or to omit

it. Typically, provisioning verification is performed for Target/Source EIs that
interface with cellular networks, but not for target EIs that serve application
servers.
Table 10-15 details the EI configuration parameters that activate target EI
restriction. These parameters are set in the EI configuration files. EI configuration
filenames have the format ei.<eitype>.config and are stored in the SFEs config
directory.
Table 10-15: Target EI Routing Parameters
12.4.
Parameter
Description
provisioned
Determines if EI screens traffic, only accepting messages from

subscribers explicitly provisioned to access this EI type.
MO_provisioned
Determines if EI screens Mobile Originated messages, only

accepting messages from subscribers explicitly provisioned to
access this EI type.
Configuring MO Routing
MO messages that have non-cellular destinations are routed according to the EI
that supports the required application or interface. The subscriber dials a predefined string, which results in routing to the specific EI. The actual destination
of the message is included in the text of the message. The routing is configured
using the SMSC Address Manipulation Tool.
The routing parameters are in home/smsc/site/config/sfe.addr_manip.config.
The prefix-to-destination is a one-to-one relationship.
12.4.1. Defining a Prefix-Routing Combination

To configure a prefix-routing combination:
1.
Enter the command smsc addr_manip in the UNIX command line

interface. The SMSC Address Manipulation Tool screen appears
(Figure 10-7).
SMSC Address Manipulation Tool

~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ROUTING
2 TRANSLATION
Figure 10-7: SMSC Address Manipulation Tool Screen

2.
Press <1>. The SMSC Routing Table Manipulation Tool screen appears
(Figure 10-8).
Page 10-94

Chapter 10
Installation
SMSC Routing Table Manipulation Tool

~~~~~~~~~~~~~~~~~~~~~~~~~~
1 List
2 Add
3 Delete
4 Edit
5 Update
Figure 10-8: SMSC Routing Table Manipulation Tool Screen

3.
Press <2>, Add, then press <Enter>. The response Enter Prefix [?,q]
appears. Figure 10-9 presents an example of defining the prefix 555 with the
Emailout EI. Prefixes are numeric strings that are never used as the initial
digits when outdialing.
4.
Enter the new prefix. A list of the Gateway EIs defined in the system
appears, and the prompt Enter destination EI [?,??,q].
5.
Enter the destination EI using the systems pre-defined number. The

message Adding route <prefix>--><EI name> done appears. Then
the Routing Table Manipulation Tool screen appears.
Enter Prefix [?,q] 555

1 MAP.1
2 EMAILOUT.1
Enter destination EI [?,??,q] 2
Adding route 555--> EMAILOUT.1 done
Figure 10-9: Routing Manipulation Commands

6.
Update the configuration as described in Paragraph 12.4.5.
12.4.2. Listing the Prefix-Routing Combinations

To list the defined prefix-routing combinations:
x
Press <1> in the SMSC Routing Table Manipulation Tool screen. A list of
the defined combinations appears (Figure 10-10).
Routing Table:
Prefix
Destination
1 555 --> EMAILOUT.1
Figure 10-10: Sample Routing Table Screen
12.4.3. Deleting a Prefix-Routing Combination

To delete a defined prefix-routing combinations:
1.
Press <3> in the SMSC Routing Table Manipulation Tool screen. The
prompt Enter entry number to delete [1-n,?,q] appears, where n is
the last route defined.
Page 10-95
Chapter 10
Installation

2.
Enter the number of the combination. Use the List option to identify the
route. The prompt Delete route: "<prefix> --> <destination>" ?
appears.
3.
Type y and press <Enter>. The message Deleting route: "<prefix> -> <destination>" done appears.
4.
12.4.4. Editing a Prefix-Routing Combination

To edit the defined prefix-routing combinations:
1.
Press <3> in the SMSC Routing Table Manipulation Tool screen. The file
opens in vi editor mode.
2.
Modify the file as required.
3.
12.4.5. Updating a Prefix-Routing Combination

Updating saves the new configuration and exports it to all the computers in the
system (SMSC1, SMSC2, MAP etc). Updating is required after any modifications.
To update the Prefix-Routing configuration:
x
Press <5>, Update, and press <Enter>. A message flow similar to the
following appears:
Are you sure you wish to update the routing table ? y
Copying files to SMSC1 ...
... Ended
Copying files to SMSC2 ...
... Ended
Copying files to MAP ...
... Ended
** The routing table has been updated. Please restart the
SFEs **
If there are any errors, they are reported at this time.
12.5.
Configuring the MO Address Translation Feature

The Address Translation feature provides the capability of manipulating the
destination address of a short message so that the final address is a standard
international number.
The
address
translation
parameters
home/smsc/site/config/sfe.addr_manip.config.
Page 10-96
are
in
the
file

Chapter 10
Installation
The actual translation procedure is documented in this section. The functionality

of the menu options 2 through 5 are the same as the Routing Table Manipulation
Tool. Refer to Paragraph 12.4.2. through Paragraph 12.4.5.
To configure a prefix translation:
1.
Enter the command smsc addr manip in the UNIX command line interface.
The SMSC Address Manipulation Tool screen appears (Figure 10-7).
SMSC Address Manipulation Tool

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ROUTING
2 TRANSLATION
Figure 10-11: SMSC Address Manipulation Tool Screen

2.
Press <2>, then press <Enter>. The SMSC Address Manipulation Tool
screen appears (Figure 10-12).
SMSC Translation Table Manipulation Tool

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 List
2 Add
3 Delete
4 Edit
5 Update
Figure 10-12: SMSC Translation Table Manipulation Tool Screen
12.6.
3.
Press <2>, Add, then press <Enter>. The prompt Enter the from prefix
appears.
4.
Enter the original prefix. The prompt Enter the to prefix appears.
5.
Enter the translated prefix. The SMSC Translation Manipulation Tool

screen appears.
6.
Verify the translation by pressing <1>, List, then press <Enter>.
7.
If necessary, modify the translation by repeating step 3 through step 6.
8.
Configuring Bi-directionality of EIs

The default type of EI is Source only. The Emailout EI can be configured as a
Gateway EI. The SMPP EI can be configured as Source, Gateway or both.
To modify the EI configuration to Gateway or Both:
1.
Verify that the file ei.<einame>.config

home/smsc/site/config.
If
not
copy
home/smsc/sfe.2.4/config/ei.<einame>.config.
2.
In the file ei.<einame>.config verify the parameter ei.<name>.type=n,

where the values for n are:
is
in
the
the directory
file
from
Page 10-97
Chapter 10
Installation

1Source
8Gateway
9Both
Email Eis amy be defined as 1 or 8. SMPP EIs may be defined as 1, 8 and 9.

All other EIs may be defined as 1 only.
3.
4.
In the file config.dir, verify that the following file names are listed:
ei.<name>.config 20
sfe.addr_manip.config 20
This step is relevant for defining a type 8 or 9. In the same file, the
following lines appear for the default type, Source:
ei.<name>.diagnostic_scheme
ei.<name>.sei_error
For any EI defined as Gateway or Both, add the following modified lines:
ei.<name>.sei.diagnostic_scheme
ei.<name>.sei.sei_error
5.
This step is relevant when defining the SMPP EI as type 8 or 9 only. In the
file /home/smsc/smsbase.2.4/config/sa_defs/config add the following (take
the existing EMAILOUT lines and modify them):
ei.SMPP.sa.SfeGeiSendShortMsgRequest
Message,
sa_msg_reference
gsm_mo_status_report M Message,
gsm_reply_path M Message,
gsm_data_coding_scheme M Message,
gsm_protocol_id M Message
6.
This step is relevant when defining SMPP as a Gateway only. Enter the
following command to create a symbolic between the indicated files:
o error_translation.ei.SMPP.sei
ln -s error_translation.ei.SMPPo
7.
To verify the configuration:
Define the EI using the MO routing. The tool only lists Gateway EIs
(Paragraph 12.4.1.).
or
Page 10-98
Enter the command smsc control status sfe. Under each individual
Status of EI, verify that the type is listed accurately.

13.
Configuration of TRILOGUE INfinity
13.1.
TRM Configuration
Chapter 10
Installation
The TRMs role in the initialization and routing of the short message is necessary
to maintain control of the routing process of messages. It is essential to configure
and verify the TRM parameter values prior to running the ISMSC.
13.1.1. Defining Connections to Additional TRMs

Multiple TRM connections may be defined.
To define a TRM connection:
1.
2.
Enter the command

smsc install_ei TRM #
where # is the additional TRM number starting from 2 (TRM 1 is always

installed).
The
ID
of
the
TRM
(system
parameter
ISM_TRM_IDENTIFICATION) should be defined as TRM. <#>
3.
Enter the command

4.
Restart the SFEs.
13.1.2. Configuring TRM System Parameters

To enable communication between the ISMSC and the TRM it is necessary to set
the appropriate TRM System Parameters.
To access the TRM System Parameters screen:
1.
Select 3, Configuration Management in the Operation and Maintenance

Menu.
2.
Select 2, System Parameters.
The following parameters support the ISMSC:

FEATURE_ENABLED_ISM
Enables the ISMSC in the TRM.
Set to Y.
FEATURE_ENABLED_ISM_ICON
Enables the MWI icon on/off on the subscribers handset using the CPHS
protocol, the DCS protocol, or both.
Set to N.
FEATURE_ENABLED_ISMSC_CDMA
Page 10-99
Chapter 10
Installation

Enables the ISMSC to turn a handset icon on/off using CDMA.

Set to Y to enable the feature.
FEATURE_ENABLED_MPA
In a redundant ISMSC configuration, or if there are additional notification
devices, such as a pager, hooked up to the TRM the MPA feature must be enabled.
FEATURE_ENABLED_SMS_FWD_REACH
Perform reachability calls when delivery is successful, not only when delivery
fails, or due to an Alert. This means an outgoing notification call is made in
addition to the short message and the call is issued just after the subscriber
receives the short message. Set to Y to enable the feature, N to disable it.
FEATURE_ENABLED_SMS_ZERO_FAXES
When enabled, the number of faxes parameter is excluded from the text message,
if it is 0. Messages 7 and 8 would be used for VMN, instead of 1,3,4,6. Refer to
Paragraph 13.1.7.1.
Set to N.
FEATURE_ENABLED_SMS_ZERO_VOICE
When enabled, the number of voice messages parameter is excluded from the text
message, if it is 0. Refer to Paragraph 13.1.7.1.
Set to N.
ISM_CONNECT_RETRY_DELAY
This is the amount of time to wait between retries to the ISMSC system when an
ACK message is not received by the TRM after sending a message.
Set to 300.
ISM_LINK_1
Controls the ISMSC key name of the TRM status to the AP.
Set to ISM1.
ISM_MAX_ACK_DELAY
Maximum time the TRM waits for the ISMSC to send back an acknowledgment
message before re-transmission. After the delay has been exhausted, the original
MWI message is resent.
Set to 30.
ISM_MAX_RETRANSMIT_RETRIES
Maximum number of times a message is sent with no acknowledgment from
ISMSC.
Set to 5.
ISM_TCP_DEV_NAME
Page 10-100

Chapter 10
Installation
This is the internal TRM device name for TCP/IP communication with the ISMSC
application. The value is the network device used by the process when TCP/IP is
initialized.
Set to BG:.
ISM_TCP_LOCAL_PORT_ADDRESS
This is the local TCP/IP address port address used by the TRM application.
Set to 2401.
ISM_TCP_NET_LOCAL_ADDRESS
This is the site-dependent TCP/IP network address of the TRM.
ISM_TCP_NET_REMOTE_ADDRESS
This is the network TCP/IP address for a remote ISMSC server (SFE machine).
ISM_TCP_REMOTE_PORT_ADDRESS
This is the address of the port used for remote communication with the ISMSC.
The port address is the actual binding socket numbers in TCP/IP.
Set to 2400.
ISM_TRM_IDENTIFICATION
Unique TRM identifier for the ISMSC which allows the ISMSC to communicate
with more than one TRM. A different value is specified for each TRM.
Set to TRM for the first TR; subsequent TRMs are named TRM.1, TRM.2.
OPTION_MPA
This enables a screen that aids in the configuration of the Multi SMSC and TNPP
Rally screens.
Set to Y.
OPTION_MWI
The Message Waiting Indication option installed (value Y) or not (value N). This
parameter must be set to Y to enable the TRM to generate SMs. If not installed,
the MWI field is disabled.
Set to Y.
OPTION_NOTIFICATION_LIST
This enables the Notification List feature. Enable (Y) for multiple notification to
ISMSC, Pager, CCS. Disable (N) if only one type of MWI is used.
OPTION_REACHABILITY
Reachability option installed.
Set to Y.
SMS_ALERT_WHEN_AVAILABLE
Perform Reachability calls when MS becomes available (due to an SC Alert).
Page 10-101
Chapter 10
Installation

Set to Y.
SMS_AMERICAN_DATE_FORMAT
Defines the date format as American if set to Y (MM/DD/YY), or non-American
if set to N (DD/MM/YY). This parameter is relevant only for the SMS CMG
protocol.
Set to Yes.
SMS_INFORM_CEL_OF_DELIVERY
Enables (value Y) or disables (value N) the printing of error messages in the CEL,
informing of a reachability request from the SMSC. This feature is enabled only
for testing
Set to No.
SMS_INTERNATIONAL_PREFIX
A constant prefix added to the Mobile Subscribers phone number. This should be
set per site according to the international prefix of the mobile subscribers.
SMS_LANGUAGE_OFFSET
Defines an offset to the next language group of standard short messages. Value 0
means that numbers from 1 to 99 will be used for one language.
Set to 0.
SMS_MAX_MBX_MSGS
Maximum number of messages of maximum size in local mailbox queue. Used to
configure the ISM MailBox similar to the SMS.
Set to 44.
SMS_MAX_MBX_MSG_SIZE
Maximum size of mailbox messages. Used to configure the ISM MailBox similar
to the SMS.
Set to 1452.
SMS_PRIORITY_VALUE
The GSM defined SMS-Priority message flag, will be set in messages from the
TRM to the ISMSC according to this value. This parameter is a GSM-only
parameter. Its setting does not affect an IS-41C system.
Set to 0. Set to 1 only if required in the specific GSM network.
SMS_ORIGINATOR_CONSTANT
If given a value, this value overrides the originator field value with its contents.
When this parameter is set to any string, it blocks the ability of the caller to
request the CLI as the number message, by replacing the CLI with whatever
constant is set here.
Set to a constant string.
Page 10-102

Chapter 10
Installation
SMS_PRIORITY_VALUE
Enables (value 1) or disables (value 0) the priority setting of all SMS messages to
the SMSC.
Set to 0.
SMS_PROTOCOL_ID
This parameter enables the Replace in Handset feature. When enabled, VMN
messages are replaced in the handset, rather than accumulating. Set to 65 to
replace messages.
Set to 0 (do not replace).
NOTE:
This feature is supported by handsets that are compatible with Phase 2

only.
SMS_SUBID_IN_ORIG
Determines whether the subscriber ID replaces (value Y) CLI as originator
address or not (value N).
In Nokia systems, this parameter determines what data is transferred to the SMSC
within the ORIGINATOR field of an MWI messageeither the Subscriber ID or a
value of the system parameter SMS_ORIGINATOR_CONSTANT. In Aldiscon
systems, this parameter defines a condition to place the Subscriber ID into the
source_addr field.
Set to N.
SMT_TCP_DEV_NAME
TCP/IP device name used by the SMT application when TCP/IP is initialized.
Set to BG.
TRM_ISM
This is the application ID of the ISMSC application in the TRM.
Set to 152 for non-redundant systems.
Set to 516 or 517 for redundant systems, in the parameters named TRM$ISM_1,
TRM$ISM_2.
NOTE:
Online changes do not affect this parameter. The system must be shut
down and restarted for any change to this parameter to take effect.
13.1.3. Message Notification Screen

The MWI features are controlled by the parameters in the Message Notification
expansion box (Figure 10-13). Open the Message Notification expansion box in
the Subscriber Record Management screen.
Page 10-103
Chapter 10
Installation

Figure 10-13: Message Notification Expansion Box

The following parameters appear in the Message Notification Screen.
MSG WAITING IND
Description:
Activates (Y) or deactivates (N) the Message Waiting Indication.
Units:
N/A
Legal values:
Y or N
Default value:
Set to Y
IMPLEMENTATION MODE
Description:
The TRM mode indicates that MWI messages will be sent to an

SMSC computer.
NOTE: If Notification List is selected, Implementation Mode is not
in use.
Units:
N/A
Legal values:
N/A
Default value:
Set to TRM.
FORWARDING TYPE
Description:
Selects which type of messages will trigger forwarding.
Units:
N/A
Legal values:
N/A
Page 10-104

Default value:
Chapter 10
Installation
Set to NONE.
REACHABILITY
Description:
Reachability calls will be forwarded to this phone.
Units:
N/A
Legal values:
N/A
Default value:
Set to MAIN.
13.1.4. Notification List Expansion Box

The Notification List (Figure 10-14) is used to configure the system to send up to
four Message Waiting Indications in parallel via different media. A maximum of
four entries can be made in the Notification List expansion box. New entries can
only be added to the bottom of the list.
Figure 10-14: Notification List Expansion Box

The Notification List expansion box contains the following fields:
Entry
Description:
The number of the Notification List entry.
Units:
N/A
Legal values:
A single integer
Default value:
N/A
Media Type
Page 10-105
Chapter 10
Installation

Description:
The Media Type available to select depends on the specific

configuration of the system. The system can send an MWI to a pager,
or another application or host, that is accessible to the subscriber.
There are four possible options.
Units:
N/A
Legal values:
DLX: The Data Link to Exchange allows the system to communicate

with a public exchange system at the site by transmitting the
MWI data through the appropriate protocol. The protocol is set
during installation of the system.
TRM: The TRM option enables the MWI to be transmitted through
the TRM to a host computer. The device through which the
TRM transmits the MWI may be specified by using the ON
DIALTYPE and OFF DIALTYPE parameters.
CCS: In environments with SS7 telephony protocols, MWI signals are
transmitted through the CCS (Call Control Server).
DIAL: With Dial mode, the system implements MWI by dialing to a
pager, light indicator, or other mechanism available to the
subscriber. The On Dial Type and Off Dial Type parameters
should be set accordingly. Entries may be selected from LOV.
Default value:
N/A
Destination
Description:
The destination of the MWI. This is a mandatory field.
Units:
ID: Subscriber ID
Main: Main Phone number
Fax: Fax ID
Bill Num: Billing Number
AT Dest: Auto Transfer Destination. Entries may be selected from the
LOV.
Legal values:
Alt: Alternate Phone Number
Default value:
N/A
On Dial Type
Description:
Page 10-106
Only set this parameter if the Media Type is set to TRM or DIAL.
This parameter determines the dialing sequence necessary to activate
and deactivate the subscribers MWI.

Chapter 10
Installation
Units:
N/A
Legal values:
An integer from 1 to 60
Default value:
N/A
Off Dial Type

Description:
Only set this parameter if the Media Type is set to TRM or DIAL.
This parameter determines the dialing sequence necessary to activate
and deactivate the subscribers MWI.
Units:
N/A
Legal values:
An integer from 1 to 60
Default value:
N/A
13.1.5. Notification Device Table

In a redundant ISMSC configuration, or if there are two auxiliary devices hookedup to the TRM, such as a pager and SMSC, the devices have to be defined in the
Notification Device Table. For an example of a configuration for a pager and a
SMSC, see Figure 10-15.
To access the Notification Device table:
1.
Select 3, Configuration Management Menu in the TRM Operation and

Maintenance Menu.
2.
Select 4, Notification Configuration Menu.
3.
Select 1, Notification Device Table.
In a redundant ISMSC configuration, there should be two entries for the ISMSC:
ISM1 ISM BG: 192.9.200.204 192.9.200.5
2400 2401
ISM2 ISM BG: 192.9.200.206 192.9.200.5
2400 2401
ISM1 and ISM2 are links to the two SFE hosts.

NOTE:
Remote and Additional Local Addresses are set according to the

TCP/IP address of the SMSC and TRM, respectively. Consequently,
the same holds true for the Remote and Local Port Addresses.
To insert a large amount of text into a small box, if necessary:

x
Press <PF3>.
To save changes and exit the screen:

x
Press <F8>.
Page 10-107
Chapter 10
Installation

Figure 10-15: Notification Device Table
13.1.6. Notification Class Table Definition

In order for the TRM to distinguish between classes in a redundant ISMSC
configuration, or if two auxiliary devices are connected to the TRM, such as a
pager and SMSC, the devices have to be defined in the Notification Class Table.
An example of a configuration for a pager and a SMSC is presented in
Figure 10-16.
To access the Notification Class Table:
1.
Selecting 3, Configuration Management Menu in the TRM Operation and

Maintenance Menu.
2.
3.
Select 2, Notification Class Table.
In a redundant ISMSC configuration, the ISM line should read:

OTHER
ISM1 ELSE ISM2
On a single TRM configuration the ISM line should read:

OTHER
Page 10-108
ISM1

Chapter 10
Installation
Figure 10-16: Notification Class Table
13.1.7. SMS Text Template Definition Screen

The conversion of messages from the MSU parameter based messages to the final
text messages displayed on the MS is a mandatory part of the ISMSC interface
support. The ISMSC has no conversion capabilities and the text must be formatted
in the packet messages sent to the ISMSC. Text of the short messages are defined
in the SMS Text Definition Template (Figure 10-17). The Short Message Text
Definition Template screen contains two fields, Text ID and Message Text. The
fields are described in the following paragraphs.
To access the TRM Operation and Maintenance Menu:
1.
Select 3, Configuration Management Menu in the Operation and

Maintenance Menu.
2.
3.
Select 3, Short Message Text.
Page 10-109
Chapter 10
Installation

Figure 10-17: SMS Text Messages Screen
13.1.7.1. Text ID
This field is used for entering a two-digit record number between 01 and 99.
Entries 1 to 8 are used for internal system messages. Entries 10 to 99 are used for
canned messages.
Messages 1 to 8 are numbered and defined according to the following:
1.
MWI_ON is sent with CLI and MWI_MODE of FIRST
2.
Numerical message sent with CLI
3.
MWI_ON is sent with CLI and MWI_MODE of ALL
4.
MWI_ON is sent without CLI and MWI_MODE of FIRST
5.
Numerical message sent without CLI
6.
MWI_ON is sent without CLI and MWI_MODE of ALL
7.
MWI_ON is sent (NO FAX) with CLI
8.
MWI_ON is sent (NO FAX) without CLI
13.1.7.2. Message Text

This 100 character field is used for entering the internal system and canned
message texts. The optional parameters of the text messages are represented by $
symbols and a letter indicating parameter type, as summarized in Table 10-16.
Typical text messages appearing on the display of the mobile telephone may be as
follows (but may be changed by the operator on the ISMSC):
Page 10-110

Chapter 10
Installation
You have {nnn} new messages, {uuu} of them urgent, and {fff} new
fax messages Last message was a {voice/fax} messages from
{line}. Please call {mbx} for retrieval.
NOTE:
In order to make the changes in the text definition effective, restart

the TRM$ISM process.
Table 10-16: SMS Message Text Symbols
13.2.
Symbol
Definition
$A
Callback DTMF data
$C
CLI/Sending Mailbox
$F
Number of fax messages in Mailbox
$D
Date in DD/MM/YY format (where DD = day, MM = month and YY = year)
$G
Number of urgent messages in the subscribers Mailbox
$L
Message Trigger: Voice/Fax/Number
$S
ID number
$T
Time in HH:MM format (where HH = hour and MM = minute)
$V
Total number of messages in the subscribers mailbox
Configuring MSU Parametersfrom TRILOGUE INfinity

Release 6.01x
Certain MSU parameters must be activated in order that the ISMSC operate
properly. Parameters relevant to the ISMSC configuration are found in the
following three parameter sets: Service Level, Access Right, and MSU system
parameters.
NOTE:
In TRILOGUE releases previous to 6.01x, these parameters are

accessed via the Direct Access menu on the TRM. Refer to
Paragraph 13.3.
13.2.1. Service Level and Access Right Parameters

The parameters are listed in the sets and subgroups indicated below.
To access the Service Level and Access Right parameters:
1.
Login to the TRM as a System administrator.
2.
Select 4, Subscriber Administration Parameters Menu.
Page 10-111
Chapter 10
Installation

3.
Select 3, Subscriber Unit Parameters Menu.
4.
Select 1, Service Level Parameters Menu, or 2, Access Right Parameters

Menu.
NOTE:
For a full discussion of modifying and distributing Service Level and

Access Right parameters, refer to the TRILOGUE INfinity
Administration and Provisioning Manual.
Service Level Set:

x
Notification Subgroup:
Deactivate MWI for TRM
Specifies whether the system has to send a deactivation message (from TRM
to SMSC).
Set to Y.
Forward Numeric Messages Via TRM
Determines whether numeric messages are forwarded via the TRM.
Set to YES.
MWI Deactivation at
Determines when to deactivate the MWI.
Set to LOGIN.
MWI Trigger
Determines whether the MWI should be sent after every new message or
after the first new message.
Set to EVERY MESSAGE.
Reachability Delay in Minutes [0-120]
Sets the delay from reachability to dialout.
Set to 0.
User Interface Subgroup:

Save Number Messages
Determines whether Number Messages are saved in the subscribers
mailbox or are sent to the external host without any notification in the
mailbox. This parameter also determines whether forwarding calls (to phone
or dial type) are transmitted upon arrival of a number message. If these
messages are not kept in the mailbox, no forwarding calls are made, and no
MWI notification is performed.
Set to NO.
User Access Subgroup:

Guest CLI Handling
Page 10-112

Chapter 10
Installation
If set to Y the CLI is set as the short message originator.

Set to YES.
Access Right Parameter Set:
x
Non Subs Group:

Guest Message Types
Defines the types of message a non-subscriber may leave for the subscriber.
Valid values are Voice(Fax)/Number/Both.
Set to BOTH for voice and numeric messages.
13.2.2. System Parameters

The parameters are listed in the Groups indicated below.
To verify or modify the values of the MSU System Parameters:
1.
Login to the TRM as O&M.
2.
From the Operation and Maintenance menu select 3, Configuration

Management menu.
3.
Select 3, System Configuration menu.
4.
Select 2, MSU Configuration menu.
NOTE:
For a full discussion of modifying and distributing system parameters,

refer to the TRILOGUE INfinity Service and Maintenance Manual.
MSU System Parameters:

x
Feature Setup:
Message Waiting Indication
This feature enables the system to turn Message Waiting Indication devices
on and off.
Set to YES.
Reachability
The Reachability parameter is used to define whether forwarding calls upon
demand from the SMSC are enabled in the system.
Set to YES.
Notification:
Number Pager
This parameter determines whether the system supports the use of display
pagers.
Set to YES.
Send MWI Upon Demand
Page 10-113
Chapter 10
Installation

Enable (Y) or disables (N) MSU support of Reachability calls.

Set to YES.
Simultaneous Notification
Enables the Notification List feature.
Set to YES.
Voice Pager
This parameter specifies whether the Play Voice Pager dialing symbol (V)
on the online Dialing Types screen is active or not. If set to YES, it is
possible to use the V dialing symbol to define a Dialing Type for a voice
pager.
Set to YES.
13.3.
Configuring MSU ParametersPrevious to TRILOGUE

INfinity Release 6.01x
This section is relevant only for TRILOGUE Infinity releases previous to 6.01x.
13.3.1. Online Parameters

Parameters are located in the screens listed below. Access each screen as
instructed, and verify that the parameters are set as described.
To access the online parameters:
1.
Login to the TRM as an Operation and Maintenance administrator.
2.
From the Operation and Maintenance Menu, select Operation Utilities

Menu.
3.
From the Operation Utilities Menu, select Direct Access Menu.
4.
From the Direct Access Menu, select Access to MSU.
5.
A box appears prompting for the MSU ID. Enter the ID number of the MSU
that is connected to the TRM in this session. A LOV may be displayed to
select the relevant MSU. After selecting an MSU, an MSU screen appears.
Press <F6> (UNIX), or <PF1> (OpenVMS).
6.
If a screen other than the Unit Status Screen appears, press <Insert>
(UNIX), or <PF1>+<6> (OpenVMS) until the Administration Main Menu
appears.
7.
If the Unit Status Screen appears, press <F1> to display the System
Administration Access Screen.
8.
Enter the ID and password in the appropriate fields. The Administration

Main Menu appears.
Page 10-114

Chapter 10
Installation
To terminate a direct access session for online parameters:

1.
Press <Insert> (UNIX), or <PF1>+<6>

Administration Main Menu appears.
(OpenVMS)
until
the
2.
Press <Ctrl>+<X> (UNIX), or <Ctrl>+<Z> (OpenVMS) to return to the

TRM.
13.3.1.1. Service Level Screen

The Service Level Screen is accessed from the Administration Main Menu by
pressing <F2>, System Administration then pressing <F1>, Service Levels.
Delay Reachability
Description:
This parameter determines the delay in placing reachability calls. If

the subscriber logs in within the specified delay, the outcall is
canceled. In not, the outcall is performed. When set to 0, there is no
delay.
Units:
Minutes
Legal values:
Integer
Default value:
N/A
FORWARD_NUMERIC_MESSAGES_VIA_TRM
Description:
Determines whether numeric messages are forwarded via the TRM.
Units:
N/A
Legal values:
N/A
Default value:
Set to YES.
Guest CLI Handling

Description:
This parameter affects the he CLI (Originator) value on the SMS

message as well as on the Voice message header.
Units:
N/A
Legal values:
N/A
Default value:
Setting is determined on-site.
NOTE:
This parameter exists in TRILOGUE INfinity Releases from 5.41x.

Previous to this release, this parameter was called Save CLI as Sender
in the offline General Parameters screen
MWI DEACTIVATION REQUIRED FOR TRM
Page 10-115
Chapter 10
Installation

Description:
Specifies whether the system has to send a deactivation message

(from TRM to SMSC).
Units:
N/A
Legal values:
N/A
Default value:
Set to Y.
MWI DEACTIVATION
Description:
Determines when to deactivate the MWI.
Units:
N/A
Legal values:
N/A
Default value:
Set to LOGIN.
MWI TRIGGER
Description:
Determines whether the MWI should be sent after every new message
or after the first new message.
Units:
N/A
Legal values:
N/A
Default value:
Set to EVERY MESSAGE.
SAVE_NUMBER_MESSAGES
Description:
Determines whether Number Messages are saved in the subscribers

mailbox or are sent to the external host without any notification in the
mailbox. This parameter also determines whether forwarding calls (to
phone or dial type) are transmitted upon arrival of a number message,
because if these messages are not kept in the mailbox, no forwarding
calls are made, and no MWI notification is performed.
Units:
N/A
Legal values:
N/A
Default value:
Set to NO.
13.3.1.2. Access Rights Screen

The following parameter is defined in the Access Rights screen.
GUEST_MESSAGE_TYPES
Page 10-116

Chapter 10
Installation
Description:
Defines the types of message a non-subscriber may leave for the

subscriber. Valid values are Voice(Fax)/Number/Both.
Units:
N/A
Legal values:
N/A
Default value:
Set to BOTH.
13.3.2. Offline Parameters

To access the MSU offline parameters:
1.
Perform an orderly shutdown.
2.
Wait for the Restart System Menu to appear.
3.
Access the Administration Main Menu.
4.
Press <F2> to access the System Parameters Main Menu.
13.3.2.1. General Parameters Screen

To access the General Parameters screen:
x
Press <F1>, General Parameters in the System Parameters Main Menu.
NOTIFICATION LIST
Description:
Enables the Notification List feature.
Units:
N/A
Legal values:
N/A
Default value:
Set to YES.
SEND MWI UPON DEMAND

Description:
Enable (Y) or disables (N) MSU support of Reachability calls.
Units:
N/A
Legal values:
N/A
Default value:
Set to YES.
SAVE CLI AS SENDER

Description:
If set to Y the CLI is set as the short message originator.
Units:
N/A
Page 10-117
Chapter 10
Installation

Legal values:
N/A
Default value:
Set to YES.
NOTE:
This parameter exists in TRILOGUE INfinity releases previous to

5.41x. In later releases this parameter is named Guest CLI Handling,
and appears in the Service Level screen, Online Parameters.
13.3.2.2. Feature Setup Screen

To access the Feature Setup screen:
x
Press <F3>, Optional Features in the System Parameters Main Menu, then
press <F1>, Feature Setup.
MWI
Description:
This feature enables the system to turn Message Waiting Indication

devices on and off.
Units:
N/A
Legal values:
N/A
Default value:
Set to YES.
REACHABILITY
Description:
The Reachability parameter is used to define whether forwarding calls

upon demand from the SMSC are enabled in the system.
Units:
N/A
Legal values:
N/A
Default value:
Set to YES.
13.3.2.3. Installer Parameters Screen

The following parameters are set in the Installer Parameters screen, accessed from
the Installer Options menu in the System Parameters offline utility.
NUMBER_PAGER
Description:
This parameter determines whether the system supports the use of

display pagers.
Units:
N/A
Legal values:
N/A
Page 10-118

Default value:
Chapter 10
Installation
Set to YES.
VOICE PAGER
13.4.
Description:
This parameter specifies whether the Play Voice Pager dialing symbol
(V) on the online Dialing Types screen is active or not. If set to YES,
it is possible to use the V dialing symbol to define a Dialing Type for
a voice pager.
Units:
N/A
Legal values:
N/A
Default value:
Set to YES.
Configuring the Integrated Alarm Package (IAP) for the

ISMSC
x
IAP Versions from 5.0 (Paragraph 13.4.1.)
IAP Versions Previous to 5.0 (Paragraph 13.4.2.)
ISMSC Configuration for the IAP (Paragraph 13.4.3.)
13.4.1. IAP Versions from 5.0

To define the unit:
1.
In the Definition Screen, press <F7>.
2.
Select ISMSC and press <F7>.
3.
Type the Name, ID, Pair, and Switch-over Timeout.
4.
Press <Do>.
13.4.2. IAP Versions Previous to 5.0

There are three steps to configuring the IAP for the ISMSC: system configuration,
unit configuration and unit monitoring.
13.4.2.1. System Configuration

To configure the system:
x
In the Configure Setup Screen, enable Monitoring the ISMSC, by selecting

SMS or R-SMS (redundant).
Page 10-119
Chapter 10
Installation

13.4.2.2. Unit Configuration

To configure the unit:
1.
Select System Configuration from the IAP Main Menu.
2.
Select 7, Define SMS Monitoring Parameters.
3.
In the ISMSC Configuration Screen set the following parameters:

For redundant systems:
Enter 1 in the field SMS A Unit No:
Enter 2 in the field SMS B Unit No:
For non-redundant systems:
Enter 1 in the field SMS A Unit No:
13.4.2.3. Unit Monitoring

To enable unit monitoring:
1.
Select Monitoring Options from the Main Menu.
2.
Select Status of Monitored SMS.
3.
Select Modify, and enable the monitoring.
13.4.3. ISMSC Configuration for the IAP

ISMSC Configuration for the IAP is already performed during the installation
procedure. In the case of a redundant TRM, the common IP address should be
used. In the hosts file, set the AP1 IP address to the TRM platform. If the system
includes a redundant TRM platform, verify the TRM platform common address.
13.5.
Starting the Process from the TRM

If necessary to start the ISMSC from the TRM:
In the TRM Process Control Screen:
x
For a non-redundant system, enter TRM_ISM
For a redundant system, enter

TRM_MPA
TRM_ISM_1
TRM_ISM_2
Page 10-120

14.
Chapter 10
Installation
Verifying the ISMSC Installation

After completing the installation, perform the following verification. This test
requires a mobile phone unit.
To verify the ISMSC Installation:
1.
Start the system.
2.
Turn on the mobile phone.
3.
Leave a message in the subscribers mailbox.
4.
Check that a Voice Mail Notification message is displayed on the mobile

phone handset display.
5.
Clear the subscriber mailbox.
6.
Turn off the mobile phone unit.
7.
Wait 20 minutes (for the mobile to be registered as inactive in the HLR).
8.
Leave another message in the mailbox.
9.
Wait a few seconds and activate the mobile phone unit.
10.
Wait a few more seconds, and check that a Voice Mail Notification is
displayed on the mobile phone handset display.
Page 10-121
Chapter 11
Man Machine Language

Chapter 11
Table of Contents
1. Overview ................................................................................................................................11-1
2. Process Management MML Commands .............................................................................11-1
3. MML Commands Man Pages ...............................................................................................11-1
3.1. Own Signaling Point Code (OSPC)..................................................................................11-1
3.2. Linkset..............................................................................................................................11-2
3.3. Link ..................................................................................................................................11-2
3.4. Routeset...........................................................................................................................11-3
3.5. Concerned Point Code (CPC)..........................................................................................11-3
3.6. Remote Subsystem Replicated........................................................................................11-4
3.7. Timers ..............................................................................................................................11-4
3.8. Global Title Translation ....................................................................................................11-4
3.9. Node Related Commands ...............................................................................................11-5
3.10. Measurements ...............................................................................................................11-5
Page 11-i

1.
Chapter 11
Overview
Man Machine Language (MML) Interface provides an interactive terminal
interface for operator input of commands. The terminal interface program
interacts with the user and accepts and forwards MML commands to the
appropriate process. When a response is returned, the result is displayed to the
operator.
2.
Process Management MML Commands

This section provides a description of MML commands used for configuration.
These commands are handled by the active copy of tap to establish or change the
active, standby, and/or idle copies of one or more processes:
3.
SWITCH-ACTIVE(8q)Switch Active and Standby copies of a process.
SWITCH-STANDBY(8q)Exchange the standby copy and an idle copy of

a process.
SWITCH-CE(8q)Move all active process copies from a CE.
ALW-MONITOR(8q)Allow the indicated Process, STREAMS Module, or

the Logical Link on the given CE to be placed into monitoring state.
MML Commands Man Pages

In order to obtain detailed information about any of the following MML
commands:
x
Enter man <command name>.
For a list of all available commands:

x
Enter mml MML_Intro.
NOTE:
3.1.
The MML has no accompanying help. Detailed information can be

retrieved from the man pages.
Own Signaling Point Code (OSPC)

The OSPC commands are:
x
CRTE-OSPC(8q) and CRTE-OSPC_s(8q)Establish a Point Code (called

Own Signaling Point Code) for this logical node. This must be entered
before any additional configuration of either the MTP or the SCCP can be
established.
DISPL-OSPC(8q)Display the Own Signaling Point Code associated with

the logical node.
Page 11-1
Chapter 11
3.2.

DLT-OSPC(8q)Delete the assigned Own Signaling Point Code from the

logical node. All Signaling Links, Link Sets and Route Sets for the logical
node must be deleted before this command can be executed.
Linkset
Linkset displays the available, congested or unavailable status of the nodes
linkset and provides the following functions:
3.3.
CRTE-LSET(8q)Create a Link Set. Every Signaling Link must belong to a

Link Set and that Link Set must be created before the Signaling Link can be
created. The Adjacent Point Code associated with the Link Set is specified
in this command.
DISPL-LSET(8q)Display configuration and status data for a single Link

Set or for all Link Sets.
CHG-SLK(8q)Change the Signaling Link Test (SLT) options for a

Signaling Link after the link is created.
DLT-SLK(8q)Delete a single physical Signaling Link from the

configuration.
ACTV-LSET(8q)Activate all Signaling Links in a Link Set.
DEACT-LSET(8q)Deactivate all the Signaling Links in a Link Set,

preventing MTP routing from actively using this LSET.
DLT-LSET(8q)Delete a Link Set. Before doing this, all Signaling Links

in the Link Set must first be deleted, and the Link Set must be removed
from all Route Sets of which it is a member.
Link
The commands used for signaling links are:
x
CRTE-SLK(8q)Create a physical Signaling Link as a member of a Link

Set. The speed and physical port number of the Signaling Link are specified,
as is the Signaling Link's unique Signaling Link Code within the Link Set.
DISPL-SLK(8q)Display configuration and status data for a single

Signaling Link or for all Signaling Links.
ACTV-SLK(8q)Activate a single Signaling Link.
DEACT-SLK(8q)Deactivate a single Signaling Link, causing it to go out

of alignment and to stop carrying traffic.
INH-SLK(8q)Inhibit Signaling Link makes a given Signaling Link

unavailable to User-Part-generated signaling traffic. The link is inhibited for
the purpose of maintenance or testing.
UNINH-SLK(8q)Restore to service a Signaling Link previously inhibited

by the INHIBIT-SLK command.
Page 11-2

3.4.
Chapter 11
Routeset
Routesets show the accessible, congested, or inaccessible status of the nodes
routesets and provide the following functions:
x
CRTE-RSET(8q)Establish a Route Set associated with a single Point

Code, and define one or more Link Sets as routes within that Route Set.
Once so defined, the Signaling Links within these Link Sets are candidates
for reaching the given Point Code. In addition, this command specifies the
load sharing indicators for the Route Set.
DISPL-RSET(8q)Display configuration and status data for a single Route

Set or for all Route Sets.
CHG-RSET(8q)Command to the MTP to add or delete a Link Set to/from

a given Route Set. When adding, the priority of Link Set within the Route
Set is specified. Load sharing may also be enabled or disabled with this
command.
DLT-RSET(8q) and DLT-RSET_s(8q)Delete Route Set. The Point Code

associated with the Route Set must have been removed from the SCCP
Configuration, as either a Concerned Point Code or as a Remote Point Code,
before this command can be executed.
ALW-RSET(8q)Allow (unblock) a single Route Set.
INH-RSET(8q)Disables outgoing signaling before deleting the routeset.

Before using this command, the system should be configured in such a way
that no incoming or outgoing traffic is handled via trunks handling this
routeset. It could cause loss of calls.
NOTE:
3.5.
Priority of routes is implied by the order listed. Priority may be

changed using CHG command. Routeset must be inhibited before
entering CHG command.
Concerned Point Code (CPC)

The commands used for Concerned Point Codes are:
x
CHC-CPS(8q)Change Concerned Point Codes.
CRTE-CPC(8q)Associate one or more Concerned Point Codes with a

single Signaling Subsystem Number.
DISPL-CPC(8q)Display Concerned Point Codes associated with a single

Signaling Subsystem Number or with all Signaling Subsystem Numbers.
CHG-CPC(8q)Add or delete up to 10 Concerned Point Codes for a given

Signaling Subsystem Number.
DLT-CPC(8q)Delete all the Concerned Point Codes associated with a

given Signaling Subsystem Number.
Page 11-3
Chapter 11
3.6.

Remote Subsystem Replicated

The commands used for Remote Subsystems are:
x
CRTE-REMSSN(8q)Associate one or more Remote Signaling Subsystem

Numbers with a single Remote Point Code.
DISPL-REMSSN(8q)Display all Remote Subsystem Numbers associated

with a single Remote Point Code or with all Remote Point Codes.
If this command is entered a typical display is:
Point Code:
12576 [0x3120] A
Remote SSNs[1]: 8
[0x8]
The output is a list of pairs - pc+ssns. Each pair contains a point code
number (in decimal and hexadecimal), and a list of subsystem numbers (in
decimal and hexadecimal).
The letter "A" of the point code indicates if it is available or not. "A"
meaning available and "P" meaning prohibited. The value for the Remote
SSN is always "A" even when the remote SSN is not equipped.
x
CHG-REMSSN(8q)Command to the SCCP to add or delete up to 10

Remote Subsystem Numbers for a given Remote Point Code.
DLT-REMSSN(8q)Delete all the Remote Subsystem Numbers associated

with a given Remote Point Code.
NOTE:
3.7.
The remote point code must have a routeset associated with it using
CRTE-RSET command.
Timers
The commands used for Timers are:
3.8.
DISPL-TIMER(8q) and DISPL-TIMERm(8q)Display the value of a single

timer within the MTP or SCCP, or of all timers within both the MTP and
SCCP.
CHG-TIMER(8q) and CHG-TIMER_s(8q)Allow the setting the value for

timers within the MTP and SCCP, such as the MTP delay time for
controlled changeover or the SCCP connection establishment timer.
Global Title Translation

Global Title Translation displays the list of global titles and provides the
following functions:
x
Page 11-4
CRTE-GT(8q)Create global title for a particular translation type.

3.9.
Chapter 11
DISPL-GT(8q)Display Numbers, Point Codes and Subsystem Numbers

associated with a particular Translation Type. It also displays Number, Point
Code, Subsystem Number and Backup point code associated with a
particular Translation Type and Number for Global Title.
DLT-GT(8q)Delete Point Code and Subsystem Number associated with a

specified number and Translation Type for Global Title format.
Node Related Commands

The Node related commands are:
3.10.
BKUP-NODE(8q)Save the current configuration of the SCCP, the MTP

and the logical node manager to disk files.
RST-NODE(8q)Establish which one of three configuration databases

(associated with the last three manual or automatic database backups) will
be used at the next restart of the logical node. In the case of the most recent
backup, the command also gives the option of applying or ignoring recent
changes (entered since the last database backup), when next restarting the
logical node. The default is to use data from the most recent database
backup, and to apply recent changes.
SCH-BKUP(8q)Change the number

configuration database backups.
SCH-PURGE(8q)Change the number of days after which measurement

and log files are purged from the system.
DISPL-BKUP(8q)Display the number of days between automatic backups

of configuration data, and display the time of the next automatic backup.
Backups may also be done manually by the BKUP-NODE comma
DISPL-PURGE(8q)Display the current setting for the number of days

after which log and measurement files will be purged from the system.
START-NODE(8q)Start a logical node on all computing elements (CEs)

in the OMNI Platform.
STOP-NODE(8q)Perform an orderly shutdown of all programs associated

with the logical node.
DISPL-SSN(8q)Display the current state (allowed or unequipped) of one

or every Signaling Subsystem Number.
of
days
between
automatic
Measurements
The commands used for measurements are:
x
ALW-MEAS (8q)Allows measurements.
INH-MEASInhibits Measurements.
Page 11-5
Chapter 11
Page 11-6

RTRV-MEAS(8q)Generate a report of either the MTP, SCCP, TCAP or

system event measurement data collected for a specified 30 minute or five
minute time interval. MTP measurements are available at five and 30 minute
intervals. SCCP, TCAP and system event measurements are available at 30
minute intervals only.
Chapter 12
Provisioning Data Storage
and Recovery

Chapter 12
Provisioning Data Storage and Recovery
Table of Contents
1. Overview ................................................................................................................................12-1
2. Provisioning Limits...............................................................................................................12-1
3. Provisioning Order ...............................................................................................................12-2
4. Provisioning Example ..........................................................................................................12-3
List of Figures
12-1 Order of SS7 Node Configuration.....................................................................................12-2
12-2 Removing SS7 Node Configurations ................................................................................12-3
Page 12-i

1.
Chapter 12
Overview
Both operator-invoked and automatically scheduled backups are available to
maintain both the MTP and SCCP configurations in the current database. The
backup files consist of MML commands. On recovery after a power off,
shutdown, or other failure, the platform retrieves its MTP and SCCP configuration
from the most recent database files plus the recent change log. Three generations
of backup files are maintained. These are designated primary, secondary, and
tertiary.
All configuration commands invoked since the last backup are stored in the
Recent Change File. The Recent Change file is zeroed after each backup.
Normal restart after power-off or shutdown uses the configuration stored in MTP
and SCCP database files, supplemented by commands in the Recent Change File.
An operator command may be used to restore the current logical nodes database
to the configuration in the primary, secondary, or tertiary database files. An
optional parameter, this command specifies use or non-use of the Recent Change
file with the primary database. The Recent Change file is never used with the
secondary or tertiary file.
The recovery options of database selection and use of Recent Change file are
stored in a file, and used each time the system is restarted. To restart the platform
with a null database, remove the Recent Change and Recovery Options files after
shutdown and before entering the go.omni command. These files are:
Recovery
[path]/db.<node name>.mtp (and sccp).$SHM.pri (and

sec, tri)
Recent Change
[path]/rc.<node name>.$SHM
Options
[path]/RecoveryOptions.<node name>.$SHM
where [path] = $OMNI_HOME/<ce name>/dffile
2.
Provisioning Limits
The Platform provisioning limits for an SS7 node are:
MTP
x
127 Linksets
255 Links
256 Destination Point Codes (DPC)
8 Possible Routesets per DPC
8 Combined Linksets (A7 only)
16 Links per Linkset
Page 12-1
Chapter 12

SCCP
x
256 Destination Point Codes (DPC)
254 Subsystem Numbers
TCAP
x
32,000 Simultaneous Dialogues per process instance
32,000 Invoke Timers per process instance
Note that in C7 OMNI the point code must be in the range of 0 to 16383. In A7
OMNI, the point code is constructed as a set of three three-digit numbers
indicating network-cluster-member. The CH7 point code uses the A7 format.
3.
Provisioning Order
Provisioning of a CCITT, ANSI SS7, or GF001-9001 (CH7) node establishes the
configurations of the MTP, SCCP, and TCAP associated with the logical node.
The SS7 logical node must be provisioned, or un-provisioned in specific
sequences. Flowcharts showing overviews of these sequences are found in
Figures 12-1and 12-2.
Figure 12-1: Order of SS7 Node Configuration
Page 12-2

Chapter 12
Figure 12-2: Removing SS7 Node Configurations
4.
Provisioning Example
To provision a node in the SS7 network, a succession of Man Machine Language
(MML) commands must be issued by the operator, through the ASCII terminal
handler. The commands are issued in a prescribed order that provides validation
and sanity checking.
A typical set of provisioning commands in an OMNI configuration is:
Create own point code
CREATE-OSPC:PC=101010;
Create linkset
CREATE-LSET:LSET=LSDALOUS, PC=20300,
Create linkset
CREATE-LSET:LSET=LSDALCHI, PC=20310,
Create link
CREATE-SLK:SLK=LNKP0C0, LSET=LSDALOUS, SLC=0,

SPEED=64K, PORT=0;
Create link
CREATE-SLK:SLK=LNKP1C1, LSET=LSDALOUS, SLC=1,

SPEED=64K, PORT=1;
Page 12-3
Chapter 12

Create link
CREATE-SLK:SLK=LNKP2C0, LSET=LSDALCHI, SLC=0,

SPEED=64K, PORT=2;
Create link
CREATE-SLK:SLK=LNKP3C1, LSET=LSDALCHI, SLC=1,

SPEED=64K, PORT=3;
Create combined linkset
CREATE-CLSET:CLSET=CLSDALLS, LSET=LSDALOUS
& LSDALCHI;
Create routeset
CREATE-RSET:RSET=STLOUIS, PC=20300,
RTES=CLSDALLS;
Create routeset
CREATE-RSET:RSET=CHICAGO, PC=20310,
RTES=CLSDALLS;
Create routeset
CREATE-RSET:RSET=PHILA, PC=202020,
RTES=CLSDALLS;
Create concerned point

code
CREATE-CPC:SSN=254, PC=20300 & 20310 & 202020;
Create remote SSN
CREATE-REMSSN:PC=202020, SSN=254;
Activate routeset
ALW-RSET:RSET=STLOUIS;
Activate routeset
ALW-RSET:RSET=CHICAGO;
Activate routeset
ALW-RSET:RSET=PHILA;
Activate linkset
ACTV-LSET:LSET=LSDALOUS;
Activate linkset
ACTV-LSET:LSET=LSDALCHI;
Page 12-4
Glossary

Glossary
Ack
Acknowledgment
API
Application Program Interface
BHSM
Busy Hour Short Messages
CC
Call Completion
CCS
Call Control Server
CDMA
Code Division Multiple Access
CLI
Calling Line Identification
COS
Class of Service
CPC
Concerned Point Code
CPHS
Common PCN Handset Specification
DCS
Data Coding Scheme
DPC
Destination Point Code
EI
External Interface
ESME
External Short Message Entity
ETSI
European Telecommunications Standards Institute
ETSI
European Telecommunications Standards Institute
ExSMSC
External SMSC
GMSC
Gateway Mobile Switching Center
GSM
Groupe Speciale Mobile/Global Standard for Mobile Communications
GT
Global Title
HLR
Home Location Registry
HPLMN
Home PLMN
IMU
Integrated Media Unit
IPOS
ISMSC Paging Operator Station
IS-41C
Interim Standard-41C
Page 1

Glossary
Page 2
ISDN
Integrated Services Digital Network
ISMSC
Intelligent Short Message Service Center
IWMSC
Interworking Mobile Switching Center
MAP
Mobile Application Part
MISDN
Mobile ISDN
MMI
Man Machine Interface
MML
MO
Mobile Originated
MS
Mobile Station
MSC
Mobile Switching Center
MSC
Mobile Service Center
MSISDN
Mobile Station ISDN Number
MSU
Messaging Storage Unit
MT
Mobile Terminated
MWI
Message Waiting Indication
NAK
Negative Acknowledgement
OMAP
Operation, Maintenance, Administration, and Provisioning
OOS
Out of Service
PC
Point Code
PCN
Personal Communications Network
PCS
Personal Communications System
PLMN
Public Land Mobile Network
PS
Provisioning Subsystem
RPC
Remote Procedure Call
SC
Service Center
SC-Alert
Service Center Alert

Glossary
SCCP
Signaling Connection Control Part (SS7 signaling protocol)
SFE
Store and Forward Engine
SM
Short Message
SME
Short Message Entity (TRILOGUE or MS)
SMPP
Short Message Peer to Peer
SMRSE
Short Message Relay Service Element
SMS
Short Message Service
SMSC
Short Message Service Center
SS7
Signaling System No 7.
TAP
Telocator Alphanumeric Paging Protocol
TCAP
Transactional Capabilities Application Part (ISDN application protocol)
TCP/IP
Transmission Control Protocol/Internet Program
TDMA
Time Division Multiple Access
TRM
TRILOGUE Manager
VLR
Visitor Location Register
VMN
Voice Mail Notification
VMS
Voice Mail System
VPLMN
Visited PLMN
Page 3
Index

Index
PC, 10-59, 10-69
A
Abuse prevention, 2-28
Address translation
configuration, 10-96
SSN, 10-58, 10-68

MSU parameters, 10-111, 10-114
NYSMSMAP
MTP (OMNI), 10-54, 10-65
alarms, 2-28, 6-3
new profile definition, 10-64
resolution of 9200, 6-5
parameters, 10-60
profile selection, 10-62
resource description, 10-62
and, 4-7
Architecture, 2-28
IPOS, 2-31
Authorizing message originators, 10-74
B
Backup, 6-1
Billing files, 4-11
SCCP, 10-55, 10-66

NYSMSMAP-IS41, parameters, 10-70
parameters, 2-27
SMPP server, 10-91
TRM, 10-99
Web server, 9-1, 10-84
configureNodes, 10-29
examples, 4-15
configurePlatform, 10-27
record format, 4-11
Control commands, 4-3
Billing information, 2-27
Control interface, 3-5
Black list, 10-74
Control Status output, sample, 6-31
Browse Trace File command, 6-18
CPC (Concerned Point Code ), 11-3
C
Call flows
CPU board, configuration, 10-1

CPU board, installation, 10-2
GSM, 2-10
IS-41C, 2-16
Data
Check command, 4-5
recovery, 12-1
Check Current Host Status command, 6-9
storage provisioning, 12-1
Class of Service, 5-1
db query, 6-41
Command line interface, See User interface
examples, 6-44
Configuration, 3-5
format, 6-43
EI, 10-92
Debug command, 6-10
Email server, 10-76
Delivery mechanism, 2-9
ISMSC, 10-39
Delivery receipt messages, 2-9
MML, 10-56, 10-67
Device terminations setup, 10-10
global titles, 10-59, 10-70
Distribute Config Files command, 4-9, 6-12
Page 1

Index
DPC (Destination Point Code), 10-55, 10-65
DSPTCH (Dispatcher), 3-2
handling messages, 7-6
installation, 7-1, 10-79
EI (External Interface), 3-1, 3-3
installation verification, 10-83
EI bi-directionality
interface utilities, 7-10
parameters, 7-8
preparation for installation, 7-1
Email
configuration files, 8-1
Send Message functions, 7-4
email2sms program, 8-2
Send Message screen, 7-2
SMTP server, 8-2
server installation, 10-80

server parameters, 10-81
Email EI
E-mail EI, 8-3
installation, 10-77
Email server
installation, 10-75
IPOS client
installation, 10-80
ISMSC
configuration
NYSMSMAP
Short Message Format, 8-1
MTP (OMNI), 10-54, 10-65
Subscriber Filtering, 8-2
new profile definition, 10-64
F
Flow control
G
Global title translation, 11-4
H
Host Status command, 4-10
I
IAP
monitoring ISMSC, 10-120
Input processing, 2-7
Integrated Alarm Package, See IAP
Interconnection diagrams, 10-16
IPOS
changing languages, 7-8, 10-82
Page 2
parameters, 10-60
profile selection, 10-62
resource description, 10-62
SCCP, 10-55, 10-66
NYSMSMAP-IS41, parameters, 10-70
installation, 10-30
ISMSC packages, 10-31
NYSMSBASE, 10-32
NYSMSSFE, post installation
procedures, 10-75
removing an installed package, 10-39
verification, 10-121
ISMSC message types, 2-6
use in TRILOGUE INfinity, 2-6
L
LAN driver

Index
LED indicators, 6-56
help on commands, 11-1
Links, 11-2
PC, configuration, 10-59, 10-69
adding or removing, 10-27

Linkset, 11-2
SSN, configuration, 10-58, 10-68

MO
Log files, 6-19
enabling and disabling, 10-72
Loggers, 6-9
messages, 2-24
M
Management features, 2-26
MO routing
Measurements, 11-5
Mobile Originated, See MO
Message notification, 10-103
Monitoring, 6-3, 6-12
Message Retry command, 4-8
MSU
Message trace file, example, 6-15

Message Trace Status command, 4-7
online parameters, 10-114

MTP (OMNI), configuration, 10-54, 10-65
Message types
icon, 2-2, 2-3
Node related commands, 11-5
numeric, 2-2
Notification, 2-5, 2-9
operator generated, 2-5
Notification class table definition, 10-108
predefined, 2-2
Notification device table, 10-107, 10-108
text, 2-1
Notification list, 10-105
MMI (Man Machine Interface), 3-4

MML (Man Machine Language)
ASCII terminal handler, 11-1
Notification transaction logs

NYSMSSFE parameters, configuration, 10-40
commands
CPC, 11-3
OMAP capabilities, 4-1
Global Title Translation, 11-4
OMNI
Link, 11-2
configuration
Linkset, 11-2
example, 12-3
Measurements, 11-5
MML, 10-56, 10-67
Node related commands, 11-5
global titles, 10-59, 10-70
OSPC, 11-1
links,linksets,routsets, 10-56, 10-67
Remote Subsystem Replicated, 11-4
PC, 10-59, 10-69
Routeset, 11-3
SSN, 10-58, 10-68
Timers, 11-4
configureNodes, 10-29
configuration, 10-56, 10-66
configurePlatform, 10-27
global titles, configuration, 10-59, 10-70
installation, 10-18
Page 3

Index
SS7 links, adding or removing, 10-27

OMNI platform
R
Receipt languages configuration, 10-73
starting, 10-30
Receipt messages configuration, 10-73
stopping, 10-30
Recent change file, 12-1
OSPC (Own Signaling Point Code), 11-1
P
Paging operator stations, 2-4
Parameters
Redundancy, 2-33
Remote Subsystem Replicated, 11-4
Replacing modules, 6-50
boards, 6-51
Email server, 10-76
CPU, 6-52
IPOS, 7-8
DAT drive, 6-54
ISMSC, 10-40
fan, 6-56
MSU, 10-111, 10-114
floppy disk drive, 6-53
PS resource, 5-1
hard disk drive, 6-53
SMPP, 10-91
power supply, 6-55
TRM, 10-99
Restore, 6-2
Web server, 10-84, 10-87
Retry mechanism
Password, SMSC user, 10-39
internal retry, 2-9
PLMN, interface, 2-10
Smart Retries, 2-8
Process management, MML commands, 11-1
Retry profile definitions, 10-52
Provisioning
Routeset, 11-3
batch mode, 5-3
example, 12-3
SC Alerts, 2-5, 2-9
interactive mode, 5-4
SCCP, configuration, 10-55, 10-66
limits, 12-1
Send Message command, 4-6
order of node configuration, 12-2
SFE (Store and Forward Engine), 3-1, 3-2
Provisioning Subsystem, See PS
SFE/EI API, 3-4
PS
SFE/EI interface, 3-4

class of service, 5-1
Short Email, 2-3
resource parameters, 5-1
SLT (Signaling Link Test), 11-2
return messages, 5-7
SM delivery, 2-5
Q
Query tool, 6-41
Smart Retries, 2-8, 10-42

error translation, 10-48
examples, 6-44
error translation rules, 10-51
format, 6-43
errors
GSM, 10-43
Page 4

IS-41C, 10-45
Index
Trace Message command, 6-16
file locations, 10-54
Tracing short messages, 6-14
general decision rules, 10-52
TRM
retry decision rules, 10-51

rules, 10-51
message notification, 10-103
SME (Short Message Entity), 3-1
notification class table, 10-108
SMPP
notification device table, 10-107
installation, 10-90
notification list, 10-105
SMS text template definition screen,

10-109
SMS text template definition screen, 10-109

Software description, 3-1
Software modules, 3-1
defining connections to, 10-99

Troubleshooting
alarm 9200, 6-5
SS7
node provisioning limits, 12-1
order of node configuration flowchart, 12-2
removing node configuration flowchart, 12-3
SS7 link board
hardware configuration, 10-8
Start command, 4-3
alarm 9700, 6-6

alarm 9920, 6-7
Control Status file, 6-27
Control Status output, sample, 6-31
Debug command, 6-10
tracing short messages, 6-14
View Status, 6-13
Statistics
raw, 6-24
Statistics files, 6-19
UnixWare
counters, 6-20
installation, 10-10
defining, 6-20
patches, 10-14
enabling FTP, 10-74
updates, 10-13
reading, 6-23
Status Report Request configuration, 10-72
User interface, 2-28, 4-2

command line interface, 4-2
Stop command, 4-4

System access, 4-2
View Status command, 4-8, 6-13
System capacity limitations, 3-6
T
Target EI routing
Timers, 11-4
Trace All Messages command, 6-17
W
Web Access, 2-5
multiple languages, 10-90
Web EI
installation, 10-86
Web installation verification, 10-87
Page 5
Index

Web ISMSC routing, 10-85

Web server
configuration files, 9-1
installation, 10-84
White list, 10-74
Page 6

Ismsc 2 4

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ismsc 2 4

Caricato da

Copyright:

Formati disponibili

ISMSC Manual

Comverse ISMSC Manual

Comverse Network Systems

Comverse ISMSC Manual

CAUTIONS AND WARNINGS

Comverse Network Systems

Comverse ISMSC Manual

Comverse Network Systems

Comverse ISMSC Manual

Answered by the called station.

Answered by the attendant.

Routed to a recorded announcement that can be administered by the CPE user.

Routed to a dial prompt.

A busy tone is received.

A reorder tone is received.

Comverse Network Systems

Comverse ISMSC Manual

North American Numbering Plan (NANP)

Comverse Network Systems

Comverse ISMSC Manual

Systems Port Identification, Facility Interface & Service Order

DID FIC (3) OR

A.S CODE (PAGE

The ATM is delivered in the following configurations: 2, 4, 6, 8 lines.

Comverse Network Systems

Comverse ISMSC Manual

Comverse Network Systems

Comverse ISMSC Manual

MAIN TABLE OF CONTENTS

Comverse Network Systems

Comverse ISMSC Manual

LIST OF EFFECTIVE PAGES

Title Page, i thru vii, viii blank, ix, x blank

1-i, 1-ii blank, 1-1 thru 1-5, 1-6 blank

3-i, 3-ii blank, 3-1 thru 3-6

4-i thru 4-ii, 4-1 thru 4-19, 4-20 blank

5-i, 5-ii blank, 5-1 thru 5-7, 5-8 blank

7-i thru 7-ii, 7-1 thru 7-11, 7-12 blank

8-i, 8-ii blank, 8-1 thru 8-3, 8-4 blank

9-i, 9-ii blank, 9-1 thru 9-2

10-i thru 10-vi, 10-1 thru 10-121, 10-122 blank

11-i, 11-ii blank, 11-1 thru 11-6

12-i, 12-ii blank, 12-1 thru 12-4

Comverse Network Systems

Comverse ISMSC Manual

Comverse Network Systems

Comverse ISMSC Manual

ISMSC Releases and their Features ..................................................................................1-2

Comverse Network Systems

Comverse ISMSC Manual

Introduction to the Short Message Service

Comverse Network Systems

Comverse ISMSC Manual

Table 1-1: ISMSC Releases and their Features

New alarms were introduced for the redundant ISMSC

The Smart Retries feature enables SMs to be retried

IS41 Support for

This feature provides the ability to send a short

The statistics produced by the ISMSC are now stored

This feature provides the ability to send short message

An MO message is carried from a mobile station

CPHS and DCS Icons

Icons are used for voice/fax mail notification. The