ND 56981 327eee 02

ND-56981-327 (E)
Issue 2, December 1999

NEAX61S
DIGITAL
SWITCHING SYSTEM
OFFICE DATA
MODIFICATION MANUAL
PRACTICE
NEC Corporation
Copyright
1999 by NEC Corporation

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or
transmitted, in any form or by any means, including electronic, mechanical, photographic, or magnetic,
without prior written permission of the publisher.
CENTREX is a registered trademark of AT&T.
Printed in Japan
NEC PRACTICE
ND-56981-327 (E) Precautions
PL 1 of 10
Precautions
To prevent you from facing death or suffering injury, this manual and alert labels, attached to the
system, give you various safety instructions. You must read the safety instructions in this manual and
take notice of alert labels on the system before performing operation and maintenance work.
This manual is intended for the operation and maintenance personnel of the NEAX61S system.
Safety Instructions
The Safety Instructions gives you safety instructions for the NEAX61S system and its maintenance
terminals. For other equipment, refer to the relevant manual of the equipment.
DEFINITIONS OF ALERT CATEGORIES
The safety instructions are divided into three categories.
DANGER
This symbol is given to an item that is explicitly dangerous to your life.
Disobedience to this instruction can put you in imminent danger of death
or serious injury.
WARNING
This symbol is given to an item that is potentially dangerous to your life.
Disobedience to this instruction can lead to death or serious injury.
CAUTION
This symbol is given to an item that is potentially dangerous to your body
and property. Disobedience to this instruction can cause injury to you, or
damage to the property such as equipment and components, and the
communication network.
NEC PRACTICE
Precautions ND-56981-327 (E)
PL 2 of 10
LIST OF ALERT LABELS
The following lists alert labels attached to the system. When you see the label, be sure to
follow the instruction on the label.
(Location)
Frame (LTF, RBF, ELF, etc.)
(Explanation)
While working with a drawer-type module pulled out of a frame,
take care not to hit your head or back against the module. Such
an accident can cause injury to you.
(Location)
Frame (BF, CPF, LTF, etc.)
(Explanation)
When you replace a fan, do not touch the fan before the fan
completely stopped. If you touch a rotating fun, you can be
injured.
(Location)
Frame (BF, CPF, etc.)
(Explanation)
The Class 1 laser product (harmless to human body) is used.
(Location)
All types of frames
(Explanation)
Wear a rubber or vinyl gloves to touch a metal-shielded tube.
Touching a metal-shielded tube can cause dermatitis.
NEC PRACTICE
PL 3 of 10
LIST OF SAFETY INSTRUCTIONS
When you find a safety instruction in this manual, be sure to read the instruction before
performing work.
The safety instructions, especially regarding death or injury, contained in this manual are
listed below, being categorized with alert categories.
Alert category: Caution
CAUTION
Safety instructions on whole work:
Before starting operation and maintenance work, ensure that the
working environment is safe.
Before starting operation and maintenance work, secure a refuge in
case of an accident or emergency situation.
Never wear slippers during work. You can fall down and get injured.
Take care not to trip over the cables, components, or tools during the
work. Such an accident can cause injury to you.
Take care so that the sleeves and trouser leg hems of your working
uniform are not caught in equipment and machines during work. A
caught sleeve or hem can lead to an injury or accident.
Do not put liquid like water in the system components or touch the
system with wet hands. Moisture in the system can cause an
electrical shock or a trouble. Should liquid enter the system,
immediately turn off the power of the affected components, and ask
for repairs.
Do not rework or disassemble the system components. An electrical
shock, a fire or trouble can result.
NEC PRACTICE
PL 4 of 10
Alert category: Caution (continued)
Precautions for Normal System Operation
The Precautions for Normal System Operation provides precautions against possible troubles that can
occur on the system. In order to maintain the normal operation of the system, you have to pay
particular attention to each item of the precautions when performing operation and maintenance work
SITE CONSIDERATION
To maintain normal system operation, your site must always meet the requirements listed
below.
(1) Temperature and humidity
CAUTION
Safety instructions on handling cards:
Wear thin cotton gloves when handling cards. Working with bare
hands can lead to an injury or accident.
While working with a drawer-type module pulled out form a frame,
take care not to hit your head or back against the module. Such an
accident can cause injury to you and/or damage to the system.
Handle the card being tested, the test instrument, cables, and all
other components properly in accordance with the instructions given
in the relevant manuals.
Safety instructions on high voltage and high current:
Persons other than the maintenance personnel must not touch the
direct current power distribution board (DC-PDB). The DC-PDB
involves a high voltage and high current. Touching it can lead to an
electrical shock or accident.
Make sure that the switching system contains components with high
voltage or current. An inadvertent contact with any of these
components can cause injury, death, and/or damage to the system.
Be sure to provide grounding where required. A failure to do so can
lead to a system failure or electrical shock at the time of lightening.
When measuring voltage or current, take adequate insulating
measures, such as covering or winding the superfluous parts of the
measuring terminal and tools with insulating tape. Allowing the
measuring terminal to touch another terminal or a short-circuit caused
by a tool can lead to an electrical shock or accident.
Operate the test equipment and the call simulation equipment (CSE)
on the specified voltage (100 or 200 V system). Operating them on an
inadequate voltage can cause a fire.
NEC PRACTICE
PL 5 of 10
(2) Dust
To prevent a short circuit due to dust buildup, make sure that the site is not a dusty place.
(3) Vibration
Since the system components are precision-engineered equipment and devices, make
sure that the site is not subject to vibration.
(4) Heat dissipation
Proper air circulation is necessary to prevent temperature rise inside the system. Make
sure that the vents of the system components are not blocked.
(5) Static electricity
Be sure to connect a wrist strap to ground such as ESD terminal, etc.
Make sure that the temperature and humidity levels are within the acceptable
range: the temperature is 5 to 40C and the humidity 20 to 80% (no condensation).
Make sure that the site is not exposed to liquid such as water and oil.
Make sure that the site is not exposed to direct sunlight or near a fire or heating
appliance like a stove.
NEC PRACTICE
PL 6 of 10
LIST OF PRECAUTIONS
The items of precautions are listed by the following working situations:
When Operating the System
When Handling Cards
When Handling the Power Supply
When Handling Parts and Components
When Operating the System
Keep the doors of the machine room closed during the work. In humid air, vapor can
condense on cards and modules in the switching system, which can lead to a short-
circuit or fire. Dust can cause a short-circuit or fire, too.
While using air-conditioning, take care to prevent water from dropping on cards and
modules in the switching system from the ceiling or refrigerant pipe. If any component
in the system becomes wet, a short-circuit or fire can result.
Keep the humidity in the machine room within the range of 20 to 80%.
Do not leave foreign objects such as screws, wires, or pieces of metal, inside the frames,
modules, main distribution frame (MDF) or terminal devices of the switching system.
Such foreign object can damage the equipment or cause a short-circuit, subsequently
resulting in a malfunction of the switching system.
Wear antistatic shoes during operation and maintenance work.
NEC PRACTICE
PL 7 of 10
When Handling Cards
When you mount or dismount a card of the system components, always wear thin cotton
gloves and a wrist strap to prevent static electricity. Electrostatic charge can damage the
internal parts.
Make sure that the switches and short plugs on the spare card are in the same condition
as those on the card to be replaced.
Wear a pair of gloves.
Wear a wrist strap.
GND
wrist strap
0 1 2 3
ON
OFF
DIP switches
Rotary switch
Short plugs
NEC PRACTICE
PL 8 of 10
Make sure the top and bottom sides of the spare card are correct. Do not force the card
into the slot. Forcibly inserting a card in a wrong direction can damage it.
Do not bend or twist the card. Bending or twisting the card can damage it and lead to a
malfunction.
Be sure to turn the power switch of a card off before removing a card with ! label.
Right Wrong
NEC PRACTICE
PL 9 of 10
When Handling the Power Supply
The system components are kept in operation with the power supply turned on at all
times. Make sure that no personnel except the system administrator is allowed to
operate the power switch. If the power supply is interrupted, communications will be
disrupted, and the unsaved data will be lost.
Never turn the power switch of a card on and off, or insert or remove a fuse except when
necessary. Be careful not to abruptly turn the power supply on and off.
When Handling Parts and Components
Never swing a cable. Never wind a cable forcibly. Swinging a cable or winding a cable
forcibly can break the cable or damage its connector.
Never remove the cap from an optical connector, except when attaching the connector.
If an optical connector is damaged or contaminated with dust, a communication error
can occur.
Never step on a battery. Stepping on a battery can cause a leakage.
Use tools and components such as batteries and cables correctly in accordance with the
instructions given in the relevant manuals.
NEC PRACTICE
PL 10 of 10
(This page is intentionally left blank.)
NEC PRACTICE
ND-56981-327 (E) Preface
PR 1 of 4
Preface
PURPOSE OF THE MANUAL
This manual provides an outline and procedure examples for modifying office data to help maintenance
personnel to carry out office data modification. It also describes how to use Graphical User Interface
(GUI) icons which make complicated operations much easier.
APPLICATION OF THE MANUAL
This manual covers information on all processor systems, functions and hardware equipment for
NEAX61 systems applied to various types of switching offices. Your concentration shall be focused on
the descriptions applicable to your system configurations provided under the contract.
MANUAL ORGANIZATION
A. Section
This manual comprises of the following sections:
SECTION 1 : OFFICE DATA OVERVIEW
Provides basic information that maintenance personnel need to know before carrying out office
data modification processing.
SECTION 2 : OFFICE DATA CHANGE TASKS
Describes typical job procedures of office data modification required when office condition
changes.
B. Module
Each section comprises of independent information units called modules. For easy identification, each
module has an identifier followed by module number. The module identifiers are defined below:
INT : Introduction
Describes general information on office data change, function of office data categories, and
relationship among office data and the switching system.
In this manual, INT modules are contained in Section 1.
PRC : Procedure
Describes a series of operating procedures.
In this manual, PRC modules are contained in Section 2.
Fig.1 shows the module title, module identifier, and module number in each module, and how they
correspond to the Table of Contents.
NEC PRACTICE
Preface ND-56981-327 (E)
PR 2 of 4
Fig. 1 Module Reference
Section 2
Section 1
Table of Contents
Preface
TITLE
SECTION 1
OFFICE DATA OVERVIEW
INDEX NUMBER ISSUE DATE
INT-040-1100 Define Office Data 5 9/97
PRC-040-2000
Task/Sub-Task Listing for Office Data Change
3 3/97
Module title
Define Office Data
INT-040-1100 1/4
PRC
INT
Module title
PRC-040-2000 1/2
Module number
Module identifier
SECTION 2. OFFICE DATA CHANGE TASKS
Module title
Precautions
Copyright
Cover Sheet
NEC PRACTICE
ND-56981-327 (E) Preface
PR 3 of 4
RELATED MANUALS
This manual is positioned as shown in Fig. 2. The related manuals should be referred to as required for
smooth maintenance and operation of the system.
Fig. 2 Relations Among Manuals
GUIDE
Introduction of
documents
Document Guide
GUIDE
Introduction of the
system
System Description
Maintenance (preventive and
fault recovery) information
MNT HARD
Equipment Description
OPER
Hardware
Information
System and maintenance
operation information
Card Replacement Procedures
System Recovery Manual
Routine Maintenance Manual
Output Manual
Traffic Data Measurement Manual
IMAT Operation Manual
Input Manual
Office Data Modification Manual
Traffic Control Manual
Charge Data Recording Manual
Service Order Processing Manual
Other operation manuals
On-line manual (built in the system)
Output Manual
Input Manual
Other manuals
NEC PRACTICE
Preface ND-56981-327 (E)
PR 4 of 4
NOTICE
The screen images shown in this manual might differ from the actual screen images in your system. In
that case, please proceed according to the actual screen images.
NEC PRACTICE
ND-56981-327 (E) Contents
CL 1 of 2
Contents
(*:REVISION)
TITLE INDEX NUMBER ISSUE DATE
SECTION 1
Define Office Data............................................................ INT-040-1100-10(E) 6 4/98
Office Data Change and Management ............................ INT-040-1300-10(E) 4 6/98
Icons Used for Office Data Modification........................... INT-040-1400-10(E) 1* 9/99
SECTION 2
OFFICE DATA CHANGE TASKS
Tasks/Sub-Task Listing for Office Data Change............... PRC-040-2000-10(E) 4 4/98
Destination Opens with Direct Routes ............................. PRC-040-2100-26(E) 1 8/99
Destination Closes with Direct Routes............................. PRC-040-2110-24(E) 1 8/99
Destination Opens without Direct Routes ........................ PRC-040-2120-23(E) 1 8/99
Destination Closes without Direct Routes........................ PRC-040-2130-23(E) 1 8/99
Add Direct Routes to Existing Destination....................... PRC-040-2140-26(E) 1 8/99
Delete Direct Routes to Existing Destination................... PRC-040-2150-25(E) 1 8/99
Change Route Selection.................................................. PRC-040-2160-23(E) 1 8/99
Create/Modify/Delete OOC Routing Feature................... PRC-040-2320-16(E) 3* 9/99
Adjacent Node Opens...................................................... PRC-040-2500-15(E) 6* 9/99
Adjacent Node Closes ..................................................... PRC-040-2510-15(E) 6 8/99
Non-Adjacent Node Opens.............................................. PRC-040-2600-15(E) 4 8/99
Non-Adjacent Node Closes ............................................. PRC-040-2610-15(E) 5* 9/99
Add Trunks....................................................................... PRC-040-3200-27(E) 1 8/99
Delete Trunks................................................................... PRC-040-3210-23(E) 1 8/99
NEC PRACTICE
Contents ND-56981-327 (E)
CL 2 of 2
NEC PRACTICE
SECTION 1
NEC PRACTICE
NEC PRACTICE
INT-040-1100-10 (E) Define Office Data
Issue 6, April 1998
INT-040-1100 1 of 6
Define Office Data
1. SUMMARY
Office data is office-provided data, which deals with what is called infrastructure of the office.
Examples of office data are; No.7 data set up for No.7 signaling network to other offices, translation
data for call processing, routing and trunk data for assigning inter-office speech path, charge data for
tariff table and charging rate, etc. Each office, according to its role in the network, requires specific
data.
2. OFFICE DATA CATEGORY
Office data that are used in this switching system can be divided into categories, defined as group icon,
according to function. Table 1 shows the office data category and functions.
Table 1 Office Data Categories and Functions (1/3)
CATEGORY FUNCTION
CCS7 Assigns CCS7 Link data
Assigns CCS7 Link Group data
Assigns CCS7 Routing data
Assigns Own Signaling Point data
Charge Data Control Assigns Charging (Charging Table
Activate, Charging Table Test, Tariff
Number, Charge, Rate Schedule) data
Assigns Charge Accounting data
Assigns FC Charge Accounting data
Equipment Control Assigns Register data
Assigns Dch Protocol Data Link
Parameter data
Assigns Emergency Supervisory
Equipment data
Assigns ISDN Protocol Information data
Assigns Reference Clock data
Assigns Spare Line Circuit data
Navigation Assigns Navigation data
NEC PRACTICE
Define Office Data INT-040-1100-10 (E)
Issue 6, April 1998
INT-040-1100 2 of 6
Number Translation Assigns Special Number data
Assigns Receiving Digits data
Assigns Sending Digits data
Assigns Translation data
Assigns BBG Translator data
Assigns Remote Translator data
Routing Control Assigns Route Sharing data
Assigns Routing data
Assigns Holiday data
Subscriber Data Control Assigns Access Network Data
Assigns Basic Business Group Data
Assigns Office Code data
Subscriber Line Control Assigns Line Module data
System Data Control Assigns Bulk Data Control data
System Expansion Assigns Announcement data
Assigns Tone data
Assigns Audio Connect Control data
Traffic Control Assigns Restriction Class data
Trunk and Line Test Assigns Monitor Telephone data
Assigns Remote Maintenance Terminal
Data
Assigns Howler Trunk Data
Assigns Line Test Equipment Data
Assigns Speech Path Test Trunk Data
Assigns Test Line Data
Assigns External Measurement
Equipment Data
CATEGORY FUNCTION
NEC PRACTICE
Issue 6, April 1998
INT-040-1100 3 of 6
3. OFFICE DATA IN THE SYSTEM AND NETWORK
Fig. 1 shows an example of interrelation between the office data and switching system. Fig. 2 shows an
example of relationship between office data and network.
Trunk Data Control Assigns Route Data
Assigns Route Profile data
Assigns Trunk data
Utility Assigns X25 Line data
CATEGORY FUNCTION
NEC PRACTICE
Issue 6, April 1998
INT-040-1100 4 of 6
Fig. 1 Interrelation between the Office Data and Switching System
LC
LTE
MONTEL LC LOC
TDNW
ICT
OGT
BWT
ANT
REC
SND
TNG
HOWT
SPT
MONT
CCSC DTIC
HUB
CSP OMP
COC SCC
MAT
DAT MT DK
Announcement
Register
Tone
Howler Trunk Data
Speech Path Test
Trunk Data
Monitor Telephone
Data (Circuit)
Line Test Equipment Data
Monitor Telephone Data (Line)
DTI
DTI
DTI
CCS7 Link
CCS7 Link
CCS7 Link
Route Data
DTIC
CCS7
Link Group
LC
TSTADP
LOC
DSLC LOC
ISDN Protocol Information
DLTC DTI
ELM Access
Network
Access Network
Data
NEC PRACTICE
Issue 6, April 1998
INT-040-1100 5 of 6
Fig. 2 Relations among Office Data and Network
Subscriber a
ICT
OGT
ICT
STP
STP
STP
Another Office C
Destination
Office B
Signaling Transfer Point
Office A
Subscriber b
Translator Data
Charge Data
No.7 Signaling
Data
Routing Data (Primary)
Routing Data (Alternative)
C
B
OGT
NEC PRACTICE
Issue 6, April 1998
INT-040-1100 6 of 6
NEC PRACTICE
INT-040-1300-10 (E) Office Data Change and Management
Issue 4, June 1998
INT-040-1300 1 of 4
Office Data Change and Management
1. SUMMARY
When an exchange opens, all office data are prepared as parts of software files to fulfill initial office
conditions such as numbering plan, tariff table, the number of line/trunk/equipment and location or
attribute.
However, as the office conditions change, along with events such as system expansion, trunk/line
addition or numbering change, associated office data must also be changed to fulfill new conditions.
Therefore maintenance personnel is required to set office data every time when office conditions
change. This office data setting is called office data change.
2. TRIGGERS OF OFFICE DATA CHANGE
Triggers for office data change are classified according to the kind of the changes of office conditions.
Typical triggers for office data change as follows:
(1) The associated office newly opens or closes
Registration and deletion of the name of the associated office
Registration and deletion of signaling group
New establishment and deletion of signaling link
Registration and deletion of signaling route
Registration and deletion of route name
New establishment and deletion of speech trunk
Setup and change of route selection order
(2) Trunks are added to or removed from the office
New establishment and deletion of speech trunks
(3) Signaling links are added to or deleted from the existing No.7 signaling line network
Registration of signaling link group
Registration of signaling route
New establishment and deletion of signaling link
NEC PRACTICE
Office Data Change and Management INT-040-1300-10 (E)
Issue 4, June 1998
INT-040-1300 2 of 4
(4) Routing is changed
Setup and change of route selection order
Routing method change (e.g., to route sharing)
(5) Hardware units are added or removed
Addition and removal of various types of hardware units
3. SYSTEM OPEARTION ALONG OFFICE DATA CHANGE
The function of office data change involves addition, deletion, and change of office data without
interruption of the switching service. The following process describes how the office data change
should be performed.
3.1 Operation Stages for Office Data Change
By using icons, office data change is carried out between operation terminal and switching system. The
process consists of the following stages:
(1) The current office data files are stored in Main Memory (MM) of Call Processor (CLP),
Operation and Maintenance Processor (OMP) or DISK (DK).
(2) Maintenance personnel enters new office data using office data icon.
(3) New data, except translator data and charge data, are directly overwritten to current data.
(4) When translator data and charge data change, new data (changed data) are stored in test area
of MM so that the new data is tested. If the result is successful, the maintenance personnel
changes over the current data to the new data.
If system restart of PH1 (or higher level) occurs, the newly changed office data files in MM will be lost,
and the system resumes its operation with backup files in the DK. Fig. 1 shows the structure of the
office data change.
NEC PRACTICE
INT-040-1300-10 (E) Office Data Change and Management
Issue 4, June 1998
INT-040-1300 3 of 4
Fig. 1 Structure of Office Data Change
Subscriber A
Subscriber B
Office
Data
MM
HUB
CLP
MM
DK
Backup
Test area
Flow of office data
Call processing
OMP
NEC PRACTICE
Office Data Change and Management INT-040-1300-10 (E)
Issue 4, June 1998
INT-040-1300 4 of 4
4. OFFICE DATA MANAGEMENT FUNCTION
This switching system provides GUI operation with maintenance personnel. Table 1 shows office data
management function and icon operations.
5. NOTICE FOR OFFICE DATA CHANGE
The data exchanging process may be seriously affected if an entry error occurs during the work. To
prevent this, it is necessary to understand the basic flow of operations and remember the following
remarks:
Prepare Magnetic Tape (MT) to save backup data during the work.
The latest current data should be saved in MT before changing office data.
After the office data is changed, create a backup data apart from the backup data prepared
during the work.
Office data change should be performed during the lowest traffic time.
Table 1 Office Data Management Function
FUNCTION DESCRIPTION
Office Data
Change
Adds, changes, or deletes office data.
The change functions are: Create, Delete, Modify, Block, Unblock, In Service,
Out of Service, etc.
Error Message Displays an error message when an illegal operation has been done. From the
message, maintenance personnel decide how to deal with the error.
Office Data Test Verifies that running office data or changed office data is correct.
Display Displays current office data and new data using View operation in the window.
NEC PRACTICE
INT-040-1400-10 (E) Icons Used for Office Data Modification
Issue 1, September 1999
INT-040-1400 1 of 4
Icons Used for Office Data Modification
1. SUMMARY
For easy operation and maintenance of the switching system, icons can be used in Graphical User
Interface (GUI) instead of commands in Command User Interface (CUI). This module describes the
function and structure of icons used in this manual.
2. ICON AND ICON GROUP
The icon is a graphical representation for various functions in the switching system. Operating icon is
the same function as entering command. Each icon is corresponded to a certain command. Icons are
classified by their function to be formed icon groups.
3. ICON WINDOW
To operate or maintain the switching system using icons, select an appropriate icon and open its
window according to the following procedure:
To activate an appropriate icon:
STEP ACTION / REMARKS
1 Click [Start] located at the lower-left corner of the screen, and position the pointer at
[Program], [VitaOne], and an appropriate icon group in order. Then, click an
appropriate icon.
The selected icon is activated, and its window is opened.
Fig. 1 shows [Routing] icon window, and the followings describe the meaning of each element.
NEC PRACTICE
Icons Used for Office Data Modification INT-040-1400-10 (E)
INT-040-1400 2 of 4
Fig. 1 Example of Icon Window
Title bar
The name of the icon is displayed. When more than one window is opened, the title bar for
the active window is a different color or intensity than others.
Menu bar
The available menus are listed. Most of icons have a [File] menu and a [Help] menu.
Tool bar
The office name and the available buttons are displayed.
Tab
Some icons include various functions. These functions are assigned to each tab which has the
different window.
Operation field
Check boxes of mutually exclusive operations are displayed in this field. Only one check box
can be selected at a time. The selected check box contains a black dot. Unavailable
operations are dimmed.
Data input field
Fields used for entering data. Point and type data to be entered directly, or specify an
appropriate item from display field.
Pull-down button
Some fields have a pull-down button at the side of Data input field. When the button is
clicked, data that can be selected are listed.
[...] button
Some fields have a [...] button at the side of data input field to display a dialog box.
Data display field
Menu bar
Title bar
Tab
Operation field
Pull-down button
Command button
[...] button
Data input field
Tool bar
NEC PRACTICE
INT-040-1400-10 (E) Icons Used for Office Data Modification
INT-040-1400 3 of 4
Data display field
The registered or a specified data is displayed in this field.
Command button
Execute button is used to execute operation on specified data in the window. Clear button is
used to clear specified data in the window. Close button is used to close the window.
4. HOW TO OPERATE ICON WINDOW
Basic operation of each icon window is described below.
To use an icon help:
1 Click [Help] on the menu bar.
The [Help] window is opened and its contents is displayed.
2 Specify a desired item in the contents.
Information of the specified item is displayed.
To input a data in data input field (without pull-down button):
1 Click a desired field.
The cursor flashes in the specified field.
2 Type a data to be entered.
The typed data is entered in the box.
To input a data in data input field (with pull-down button):
1 Click the pull-down button of a desired field.
The list box appears.
2 Click an item to be entered from the list box.
The specified item is entered in the field.
To change an active tab to another tab:
1 Click a desired tab.
The displayed window changes to the selected tab window.
NEC PRACTICE
Icons Used for Office Data Modification INT-040-1400-10 (E)
INT-040-1400 4 of 4
To carry out command:
1 Click [Execute] button.
The specified data is registered and displayed in data display field.
To clear all data in data input fields:
1 Click [Clear] button.
The data is cleared from data input fields.
To exit an active window:
1 Click [Close] button.
The active icon window is closed.
NEC PRACTICE
SECTION 2
OFFICE DATA CHANGE TASKS
NEC PRACTICE
NEC PRACTICE
PRC-040-2000-10 (E) Task/Sub-Task Listing for Office Data Change
Issue 4, April 1998
PRC-040-2000 1 of 2
1. SUMMARY
Changes in network configuration and service provision raise the need for changing office data at each
switching office existing in the network. Even changes in own office may require the changing office
data. The procedures to change office data differ and involve different types of office data, depending
on the purpose of the change.
The terms, task and sub-task, used in this manual, represent the procedures to achieve a specific
purpose. The task refers to the procedures fundamental to the switching office, addition of an
outgoing route, for instance. The tasks, at some steps of their procedures, provide choices of optional
procedures. The sub-task refers to those optional procedures. Practical implementation of office data
change is often a combination of tasks and sub-tasks.
This module gives a list of tasks/sub-tasks to perform at the switching office. In this module, tasks/sub-
tasks are listed by category, with reference to the Procedure (PRC) module where step-by-step
procedures are explained.
2. TASK/SUB-TASK LISTING BY CATEGORY
Tasks/sub-tasks for office data change are grouped under the following categories:
Route/Routing
Common Channel Signaling No.7 (CCS7)
Trunk/Line Installation
2.1 Route/Routing
In the Routing category, tasks and sub-tasks mostly deal with addition/deletion of an outgoing route:
Routing is controlled at the originating side. Table 1 is the list of the tasks/sub-tasks.
Table 1 Tasks/Sub-Tasks for Route/Routing (1/2)
Item Task/Sub-Task Refer to
Destination Opens with Direct Routes Task PRC-040-2100
Destination Closes with Direct Routes Task PRC-040-2110
Destination Opens without Direct Routes Task PRC-040-2120
Destination Closes without Direct Routes Task PRC-040-2130
Add Direct Routes to Existing Destination Task PRC-040-2140
Delete Direct Routes to Existing Destination Task PRC-040-2150
NEC PRACTICE
Task/Sub-Task Listing for Office Data Change PRC-040-2000-10 (E)
Issue 4, April 1998
PRC-040-2000 2 of 2
2.2 CCS7
Tasks in the CCS7 category deal with No.7 signaling network. Table 2 is the lists of the tasks. This
category has no sub-tasks.
2.3 Trunk/Line Installation
These tasks deal with addition/deletion of trunk/line which belongs to the trunk category. Table 3 is the
list of the tasks. This category has no sub-tasks.
Change Route Selection Task PRC-040-2160
Create/Modify/Delete OOC Routing Feature Sub-task PRC-040-2320
Table 2 Tasks for CCS7
Adjacent Node Opens Task PRC-040-2500
Adjacent Node Closes Task PRC-040-2510
Non-Adjacent Node Opens Task PRC-040-2600
Non-Adjacent Node Closes Task PRC-040-2610
Table 3 Tasks for Trunk/Line Installation
Add Trunks Task PRC-040-3200
Delete Trunks Task PRC-040-3210
Table 1 Tasks/Sub-Tasks for Route/Routing (2/2)
NEC PRACTICE
PRC-040-2100-26 (E) Destination Opens with Direct Routes
Issue 1, August 1999
PRC-040-2100 1 of 18
Destination Opens with Direct Routes
1. SUMMARY
When a switching office newly opens in network, the local office may need direct routes to connect
with the new office. Setting up direct routes to a destination comprises of Outgoing (OG) and Incoming
(IC) routes addition. Fig. 1 and Fig. 2 show examples.
This task provides step-by-step procedures for setting up direct routes to a new destination.
Fig. 1 OG Route Addition Example
Fig. 2 IC Route Addition Example
New route index
dstb
New OG trunk
ogtb0001
Existing
destination A
New
destination B
DN=0123
Office
A
Dials 0123-XXX-XXXX
New route
Existing route ogta
O
G
T
B OG
OGT
: Outgoing
: Outgoing Trunk
New IC trunk
ictb0001
Existing
destination A
New
destination B
Office
A
New route ictb
IC
T
B
IC
ICT
: Incoming
: Incoming Trunk
NEC PRACTICE
Destination Opens with Direct Routes PRC-040-2100-26 (E)
PRC-040-2100 2 of 18
2. HOW TO SET OFFICE DATA
2.1 Icons to Use
This task involves creation or modification of office data by using the following icons:
[Route Profile] icon
[Route Data] icon
[Trunk] icon
[Routing] icon
[Translation] icon
2.2 Fundamental Data Fields
Some data fields of office data are fundamental to this task. These data fields show directions in which
other data fields have to be defined, and are used as indexes of the office data. Table 1 shows the
fundamental data fields.
Table 1 Fundamental Data Fields
Data Field Icon to Use Description Data Example
Profile Name [Route Profile]
icon
Defines trunk class for trunk types
of Incoming Trunk (ICT)/Outgoing
Trunk (OGT).
ogttup, icttup
Route Name [Route Data] icon Route Name in this icon defines
trunk class for IC/OG routes.
ogtb, ictb
Circuit Name [Trunk] icon Designates trunks for IC/OG routes. ogtb0001, ictb0002
Route Index [Routing] icon Defines OG route selections
specific to destination.
dstb
Directory
Number
[Translation] icon Translates digits of directory
number.
Routing decision and charge index
are derived from the translation
result.
0123
Access Code Decides connection type. lcl (Local Call)
Minimum Digit/
Maximum Digit
Assigns minimum/maximum
number of digits to be received
after the directory number is
received.
Min. Digit=7
Max. Digit=7
NEC PRACTICE
PRC-040-2100 3 of 18
3. PROCEDURE OVERVIEW AND OPERATION FLOW
3.1 Procedure Overview
The procedure of setting up direct routes to a new destination consists of the following stages of
operation:
Stage 1: Create trunk data.
Stage 2: Create routing data.
Stage 3: Create translator.
Stage 4: Make trunk test.
Stage 5: Place trunk in service and activate translator.
Note: Addition of IC routes requires Stages 1, 4 and 5.
3.2 Operation Flow
Fig. 3 shows the operation flow. In the figure, the following conventions are used:
[CCC..] Icons explained in this module.
[CCC..]
Non-office data icons used in this module. Refer to related manuals for details.
Icons used in sub-task. Refer to the module indicated below.
[CCC..]
NEC PRACTICE
PRC-040-2100 4 of 18
Area, CPC, RTF,
etc.
Start
Stage 1
Stage 2
Stage 3
[Route Profile]
[Route Data]
[Trunk]
[Routing]
Apply routing
feature?
No Routing
feature
[Routing
[Holiday]
[Routing]
TOD OOC
Yes
No
[Route Sharing]
[Translation]
Create Profile
Name
Create Route Name
Create trunks by
entering Circuit Name
Create Route Index
Create translator by registering
Directory Number/Access Code/
Minimum Digit/Maximum Digit
Continue to Stage 4
PRC-040-2320
IC route or
OG route?
Proceed to Stage 4
IC route
OG route
Yes
Create
Profile Name?
No
Yes
Fig. 3 Operation Flow Example (1/2)
Apply route
sharing?
Note: For details about these icons, refer to Traffic Control Manual.
See Note
See Note
See Note
Schedule]
NEC PRACTICE
PRC-040-2100 5 of 18
4. PROCEDURE DETAILS
Procedures for setting up direct routes to a new destination are explained below.
Note: For further explanation of parameter specification, refer to I ntelligent Maintenance
and Administration Terminal (I MAT) Operation Manual. For details of test
procedure, refer to Routine Maintenance Manual.
[Trunk Test] Test new trunks
[Trunk]
Place new trunks
in service
[Translation]
Activate new
translator
OK
Test result
is OK?
Check office data
and retry
End
Stage 4
Stage 5
NG
CPC
OOC
RTF
TOD
: Calling Party Category
: Out of Chain
: Route Transfer
: Time of Day
IC route or
OG route?
IC route
OG route
NEC PRACTICE
PRC-040-2100 6 of 18
Stage 1: Create Trunk Data
Notes:
1 To create a new profile name, start with STEP 1 Create Profile Name.
2 To apply an existing profile name, start operation with STEP 2 Create Route Name.
1 Create profile name.
1-A Click [Route Profile] icon from [Trunk Data Control] icon group.
[Route Profile] (View) window is displayed.
1-B Select Create from Operation field.
The screen changes to [Route Profile] (Create) window.
Fig. 4 Route Profile Window (Create)
NEC PRACTICE
PRC-040-2100 7 of 18
1-C Specify Profile Name, Protocol Type, Trunk Type, Type of Select Trunkhunt, Line
information, Pretranslation, Glare Control Indication and Satellite Indicator
fields.
1-D Specify other data input fields.
Note: The fields vary depending on what is selected in Protocol Type field.
1-E Click [Execute] button.
1-F Click [Close] button to close the icon.
2 Create route name.
2-A Click [Route Data] icon from [Trunk Data Control] icon group.
[Route Data] (View) window is displayed.
The screen changes to [Route Data] (Create) window.
When General is selected in
Protocol Type field
When Individual is selected in
Protocol Type field
Protocol Name field Line Signal field
Version Number field Register Signal field
Connecting Test field Line Signal of Detail field
Sending and Receive field
NEC PRACTICE
PRC-040-2100 8 of 18
Fig. 5 Route Data Window (Create)
2-C Enter route name in Route Name field.
-or-
Click [...] button to open Route Name dialog, and specify route name.
NEC PRACTICE
PRC-040-2100 9 of 18
Fig. 6 Route Name Dialog
If the fields to be specified are not found in [Parameter 1] tag, click [Parameter 2] tag
or [Parameter 3] tag.
To specify all route names Select All Route in Type Of Selection field, and
click [OK] button.
To omit specifying Select No Route in Type Of Selection field, and
click [OK] button.
To specify a route name Select Specific Route from the list in Type Of
Selection field. Enter the appropriate route name,
or select it from the list. Click [OK] button.
To refresh the route name
list
Click [Refresh] button.
Note: The list shows previously-acquired information and may not
show current host status. Clicking this button updates the
information.
To narrow down the route
name list by the first letter
of the name
Select the letter in Index field. A list of the
narrowed down route names is shown in
Available Route(s) list. Select an appropriate
route name, and click [OK] button.
Note: To show all route names, select (All) in Index field.
To cancel the setting Click [Cancel] button.
NEC PRACTICE
PRC-040-2100 10 of 18
3 Create trunks.
3-A Click [Trunk] icon from [Trunk Data Control] icon group.
[Trunk] (View) window is displayed.
The screen changes to [Trunk] (Create) window.
Fig. 7 Trunk Window (Create)
3-C Specify object type in Object Type field.
3-D Specify data in Equipment Trunk field.
3-E Specify another data input field(s.)
Note: The field to be specified varies depending on what is selected in Object Type
field.
When Route Name is selected, specify Route Name field.
When Circuit Name is selected, specify Circuit Number field.
When Circuit Name & Circuit Identification Code is selected, specify Circuit
Number and Circuit Identification Code fields.
3-F Click [Execute] button.
3-G Click [Close] button to close the icon.
Notes:
1 To add OG route, proceed to Stage 2 Create Routing Data.
2 To add IC route, proceed to Stage 4 Make Trunk Test.
NEC PRACTICE
PRC-040-2100 11 of 18
Stage 2: Create Routing Data
1 Create Route Index.
1-A Click [Routing] icon from [Routing Control] icon group.
[Routing] (View) window is displayed.
The screen changes to [Routing] (Create) window.
Fig. 8 Routing Window (Create)
1-C Select Route Index from Data Type field.
1-D Specify appropriate data in Route Index field.
1-E Enter appropriate data in Processing Identifier field.
-or-
Click [...] button to open Processing Identifier dialog, and specify the data.
NEC PRACTICE
PRC-040-2100 12 of 18
Fig. 9 Processing Identifier Dialog
To specify all data Select All in Select Type Of Data field, and click
[OK] button.
To omit specifying Select None in Select Type Of Data field, and
click [OK] button.
To specify special strings Select Special in Select Type Of Data field. A
different label, such as Skip, Cancel, or nothing
appears depending on command. Click [OK]
button.
To specify specific
selectable values
Click Specific Data in Select Type Of Data field.
Select an appropriate value in the list. Repeat this
step until all the desired values are selected. Click
[OK] button.
To remove entered data
Select data to be removed from the list. Repeat
this step until all the desired values are selected.
Click [OK] button.
NEC PRACTICE
PRC-040-2100 13 of 18
1-F Click [Edit...] button to open Routing Data dialog, and specify routing data.
Fig. 10 Routing Data Dialog
1-G Click [Execute] button.
The screen changes to [Routing] (View) window.
Note: To create Out of Chain (OOC) routing, refer to PRC-040-2320, Create/Modify/
Delete OOC Routing Feature.
1-H Click [Close] button to close the icon.
To add routing data Click [Add...] button. Another dialog
opens. Specify appropriate data in the
dialog, and click [OK] button.
To modify routing data Select the data to be modified from the
list, and click [Edit...] button. Another
dialog opens. Specify appropriate data to
be modified in the dialog, and click [OK]
button.
To change the order of the routing data Select appropriate data from the list, and
click up or down arrow. Click [OK]
button.
To remove routing data Select the data to be removed from the
list. Click [OK] button.
NEC PRACTICE
PRC-040-2100 14 of 18
Stage 3: Create Translator
1 Create translator.
1-A Click [Translation] icon from [Number Translation] icon group.
[Translation] (View) window is displayed.
1-B Click [Display] menu in the menu bar, then select Translation Type from the
pulldown menu.
1-C Select Create from Operation field.
The screen changes to [Translation] (Create) window.
Fig. 11 Translation Window (Create)
1-D Specify appropriate data in Translator Identification and Data Type fields.
The parameters in Data Type field are as follows:
NEC PRACTICE
PRC-040-2100 15 of 18
1-E Specify the rest of the fields.
Note: The fields to be specified vary depending on what is selected in Data Type field.
Stage 4: Make Trunk Test
1 Test new trunks.
1-A Click [Trunk Test] icon from [Trunk and Line Test] icon group.
n: Directory number rst_sub: Subscriber origination
restriction demand
control
prfx: Prefix number d: Minimum digit/
Maximum digit
id_fact: Incomplete call factor
identification
nrd: Route decision
necessary number of
digits
ac: Access code tmg_d Inter-digit timing
(Timing digit)
dst: Destination chrg_rate: Charge rate
idx_rut: Route index id: Iteration identifier
(Identification)
rc_dst: Destination restriction
class
chrg_band: Charge band
type_chrg: Charging class/Message
billing index
tmg_rng: Special number ringing
timing (Ringing timing)
fc: Function code for
services and special
numbers
cli: Calling line
identification
NEC PRACTICE
PRC-040-2100 16 of 18
[Trunk Test] main window is displayed.
Fig. 12 Trunk Test Main Window
1-B Click [TRK] button.
[Trunk Test] window is displayed.
Fig. 13 Trunk Test Window
1-C Specify the trunk to be tested and execute test.
1-D Click [Close] button to close [Trunk Test] icon.
Notes:
1 If the test result is OK, proceed to Stage 5 Place Trunk in Service and Activate
Translator.
2 If the test result is NG, check office data and retry.
NEC PRACTICE
PRC-040-2100 17 of 18
Stage 5: Place Trunk in Service and Activate Translator
1 Place new trunks in service.
1-B Select In Service from Operation field.
The screen changes to [Trunk] (In Service) window.
Fig. 14 Trunk Window (In Service)
1-C Select an object type from Object Type field.
1-D Specify another data input field.
Note: This field varies depending on what is selected in Object Type field.
When Equipment Trunk is selected in Object Type field, specify Equipment
Trunk field.
When Circuit Number is selected in Object Type field, specify Circuit Number
field.
Notes:
1 To add OG route, proceed to STEP 2 Activate new translator.
2 To add IC route, end the operation.
NEC PRACTICE
PRC-040-2100 18 of 18
2 Activate new translator.
2-B Select Activate from Operation field.
The screen changes to [Translation] (Activate) window.
Fig. 15 Translation Window (Activate)
2-C Specify Office Data Area field and Office Code Update field.
2-D Click [Execute] button.
2-E Click [Close] button to close the icon.
NEC PRACTICE
PRC-040-2110-24 (E) Destination Closes with Direct Routes
PRC-040-2110 1 of 12
Destination Closes with Direct Routes
1. SUMMARY
If an office and a closed destination are interconnected via direct routes, the office needs to remove
those routes. Removal of direct routes to a closed destination comprises of deletion of Outgoing (OG)
and Incoming (IC) routes. Fig. 1 and Fig. 2 show the examples.
This task provides step-by-step procedures for removing direct routes to a closed destination.
Fig. 1 OG Route Deletion Example
Fig. 2 IC Route Deletion Example
2.1 Icons to Use
This task involves deletion or modification of office data by using the following icons:
[Translation] icon
Destination A
Closed
destination B
DN=0123
Office
A
Delete route ogtb
Route ogta
Delete route
index dstb
O
G
T
B
Delete OG trunk
ogtb0001
OG
OGT
: Outgoing
: Outgoing Trunk
Delete route ictb
Destination A
Closed
destination B
Office
A
IC
T
B
Delete IC trunk
ictb0002
IC
ICT
: Incoming
: Incoming Trunk
NEC PRACTICE
Destination Closes with Direct Routes PRC-040-2110-24 (E)
PRC-040-2110 2 of 12
[Routing] icon
[Trunk] icon
[Route Data] icon
Some data fields of office data are fundamental to this task. These data fields show the directions in
which other data fields have to be defined, and are used as indexes of the office data. Table 1 shows
The procedure for removing direct routes to a closed destination consists of the following stages of
operation:
Stage 1: Place trunks out of service
Stage 2: Delete translator
Stage 3: Delete routing data
Stage 4: Delete trunk data
Stage 5: Activate new translator
Note: Deletion of IC routes requires Stages 1 and 4.
3.2 Operation Flow
Fig. 3 shows an example of the operation flow.
Directory
Number
[Translation] icon Translates digits of Directory Number.
Routing decision and charge index are
derived from the translation result.
0123
Route Index [Routing] icon Defines OG route selections specific to
destination.
dstb
Circuit Name [Trunk] icon Designates trunks for IC/OG routes. ogtb0001,
ictb0002
Route Name [Route Data] icon Route names in this icon define trunk
class for IC/OG routes.
ogtb, ictb
NEC PRACTICE
PRC-040-2110 3 of 12
Fig. 3 Operation Flow Example
Start
Stage 1
Stage 2
[Trunk]
[Translation]
[Route Data]
Place trunks out of service
Delete translator by selecting
Directory Number
IC route or
OG route?
IC route
OG route
[Routing]
Stage 3
[Trunk]
[Routing]
Yes
No
PRC-040-2320
Delete OOC
End
Delete trunks by entering
circuit number
Delete route name
IC route or
OG route?
IC route
OG route
Stage 5
[Translation]
Activate new
translator
Stage 4
OOC : Out of Chain
Delete OOC?
Delete route index
[CCC..]
[CCC..]
Icons explained in this module.
Icons used in sub-task. Refer to the module indicated above.
NEC PRACTICE
PRC-040-2110 4 of 12
Procedures for removing direct routes to a closed destination are explained below.
Note: For further explanation of parameters specification, refer to I ntelligent Maintenance
and Administration Terminal (I MAT) Operation Manual.
Stage 1: Place Trunks Out of Service
1 Place trunks out of service.
1-B Select Out of Service from Operation field.
Fig. 4 Trunk Window (Out of Service)
1-C Specify appropriate data in Object Type field.
1-D Specify another data input field as it is displayed.
field.
Trunk field.
field.
When Route Name is selected in Object Type field, specify Route Name field.
NEC PRACTICE
PRC-040-2110 5 of 12
Notes:
1 To delete OG route, proceed to Stage 2 Delete Translator.
2 To delete IC route, proceed to Stage 4 Delete Trunk Data.
Stage 2: Delete Translator
1 Delete translator.
pulldown menu.
1-C Select Delete from Operation field.
Fig. 5 Translation Window (Delete)
1-D Specify Translator Identification field.
Notes:
1 The field(s) to be specified varies depending on what is selected in Translator
Identification field.
2 The data to be deleted can also be selected from the display area. The selected data
NEC PRACTICE
PRC-040-2110 6 of 12
are displayed in appropriate data input fields respectively. The values in the fields
can be changed after that. (This method is available only when the display area
contains data.)
Stage 3: Delete Routing Data
1 Delete route index.
Note: If the routing data to be deleted applies Out of Chain (OOC) routing feature, delete
OOC data before deleting route index. For details, refer to PRC-040-2320 Create/
Modify/Delete OOC Routing Feature.
Fig. 6 Routing Window (View)
1-B Select Routing Data from Data Type field.
1-C Specify Route Index field.
1-D Enter appropriate data in Processing Identifier field.
-or-
NEC PRACTICE
PRC-040-2110 7 of 12
1-F Select Delete from Operation field.
[OK] button.
click [OK] button.
button.
To specify specific
selectable values
[OK] button.
Click [OK] button.
NEC PRACTICE
PRC-040-2110 8 of 12
Note: If no routing feature exists with the route index, omit the rest of the steps.
Fig. 8 Routing Window (Delete)
1-G Select Routing Data from Data Type field.
1-H Specify Object Type field.
1-I Specify the rest of the data input fields.
Note: The field(s) to be specified varies depending on what is selected in Object Type
field.
1-J Click [Execute] button.
1-K Click [Close] button to close the icon.
Stage 4: Delete Trunk Data
1 Delete trunks.
NEC PRACTICE
PRC-040-2110 9 of 12
Fig. 9 Trunk Window (View)
1-B Specify Circuit Trunk in Data Type field.
1-C Specify Object Type field.
field.
When Equipment Trunk is selected, specify Equipment Trunk field.
When Circuit Number is selected, specify Circuit Number field.
When None is selected, only those in the installed state are displayed.
1-E Specify View Element field.
When All is selected, all objects whether installed or not installed are
displayed.
Note: View Element field becomes selectable only when all items except None are
selected in Object Type field.
1-F Select Delete from the Operation field.
2 Delete route name.
[Route Data] window is displayed.
NEC PRACTICE
PRC-040-2110 10 of 12
2-B Select Delete from Operation field.
Fig. 10 Route Data Window (Delete)
-or-
NEC PRACTICE
PRC-040-2110 11 of 12
Note: To delete route name from IC route, repeat STEPs 2-B to 2-C.
To specify all Select All Route in Type Of Selection field, and
click [OK] button.
click [OK] button.
To specify route
name
Select Specific Route from the list in Type Of
Selection field, and click [Add...] button. Another
dialog opens. Specify route name in the dialog.
Repeat this step until all the desired data are added.
Click [OK] button.
To edit entered data Select Specific Route from the list in Type Of
Selection field. Select data to be edited from the list,
and click [Edit...] button. Another dialog opens.
Specify route name in the dialog. Repeat this step
until all the desired data are edited. Click [OK]
button.
To remove entered
data
Selection field. Select data to be removed from the
list, and click [Remove] button. Repeat this step
until all the desired data are removed. Click [OK]
button.
NEC PRACTICE
PRC-040-2110 12 of 12
Note: To delete OG route, proceed to Stage 5 Activate New Translator.
Stage 5: Activate New Translator
1-B Select Activate from the Operation field.
1-C Specify Office Data Area and Office Code Update fields.
Note: The data to be activated can also be selected from the display area. The selected
data will be displayed in appropriate data input fields respectively. The values
in the fields can be changed after that. (This method is available only when the
display area contains data.)
NEC PRACTICE
PRC-040-2120-23 (E) Destination Opens without Direct Routes
PRC-040-2120 1 of 10
Destination Opens without Direct Routes
1. SUMMARY
When a switching office is newly opened in the network, an office needs to set up transit routes if no
direct route exists between the office and the switching office. Transit routes are set up at the
originating side, over existing routes in the network. Fig. 1 shows the example.
This task provides step-by-step procedures for setting up transit routes to a new destination.
Fig. 1 Transit Route Setup Example
2.1 Icon to Use
[Routing] icon
[Translation] icon
which other data fields have to be defined, and are used as indexes of the office data. Table 1 shows the
New route
index dstb
New
destination B
DN=0123
Office
Dials 0123-XXX-XXXX
Existing destination A
Existing destination C
Existing route ogta
Existing route ogtc
A
C
B
Existing route index dsta
NEC PRACTICE
Destination Opens without Direct Routes PRC-040-2120-23 (E)
PRC-040-2120 2 of 10
The procedure for setting up transit routes to a new destination consists of the following stages of
operation:
Stage 1: Create routing data
Stage 2: Create translator
Stage 3: Execute trunk test
Stage 4: Activate translator
3.2 Operation Flow
Fig. 2 shows an example of the operation flow. In the figure, the following conventions are used:
dsta, dstb
Directory
Number
number.
result.
0123
Access Code Decides connection type. lcl (Local Call)
Minimum Digit/
Maximum Digit
Assigns minimum/maximum
number of digits to be received
after the directory number is
received.
Min. Digit=7
Max. Digit=7
[CCC..]
[CCC..]
[CCC..]
Non-office data icons used in this module. Refer to related manuals for
NEC PRACTICE
PRC-040-2120 3 of 10
See Note
Area, CPC, RTF,
etc.
Start
Stage 1
Stage 2
[Routing]
Apply routing
data?
No
Routing
data
[Routing
Schedule]
[Holiday]
[Routing]
TOD OOC
Apply route
sharing?
Yes
No
[Route Sharing]
[Translation]
Create Route Index
Create translator registering
Directory Number/Access Code/
Minimum Digit/Maximum Digit
PRC-040-2320
Yes
Create Route
Index?
No
Yes
Proceed to Stage 3
See Note
See Note
Note: For details about these icons, refer to Traffic Control Manual.
NEC PRACTICE
PRC-040-2120 4 of 10
Procedures for setting up transit routes (OG route only) to a new destination are explained below.
A route index can be created for a new destination. The route index existing with intermediate transit
office can also be applied.
To create a route index, start with STEP 1 Create route index. To apply an existing route index, start
with STEP 2 Create translator.
[Translation]
Activate new
translator
End
Stage 4
CPC
OOC
RTF
TOD
: Calling Party Category
: Out of Chain
: Route Transfer
: Time of Day
[Trunk Test]
Test new trunks
Test result
is OK?
Check office
data and retry
Stage 3
NG
OK
NEC PRACTICE
PRC-040-2120 5 of 10
Stage 1: Create Routing Data
1 Create route index.
Note: If it is unnecessary to create routing index, skip this step and proceed to Stage 2
Create Translator.
1-C Select Routing Data from Data Type field.
1-D Specify a new route index in Route Index field.
1-E Specify appropriate routing feature in Processing Identifier field.
1-F Click [Edit...] button, and specify routing data.
Routing Data dialog is displayed.
NEC PRACTICE
PRC-040-2120 6 of 10
Notes:
1 To create Out of Chain (OOC) routing, refer to PRC-040-2320, Create/Modify/
2 To create Time of Day (TOD) routing, refer to Traffic Control Manual.
To add routing data Click [Add...] button. Route dialog is displayed.
Specify appropriate data to be added in the dialog,
and click [OK] button.
To modify routing data Select the data to be modified from the list. Click
[Edit...] button. Route dialog is displayed. Specify
appropriate data to be modified in the dialog, and
click [OK] button.
To change the order of
routing data
Select appropriate data to be changed from the list.
Click up or down arrow so that the order changes.
Click [OK] button.
To remove routing data Select appropriate data to be removed from the list,
and click [Remove] button. Then click [OK]
button.
NEC PRACTICE
PRC-040-2120 7 of 10
Stage 2: Create Translator
1 Create translator.
pulldown menu.
1-C Select Create from Operation field.
Fig. 5 Translation Window (Create)
1-D Specify appropriate data in Data Type field.
Notes:
1 The fields to be specified vary depending on what is selected in the fields above.
2 To copy data format from other data, check Command Pattern Reflection under
[Option] menu first. From the display area, select the data line whose format (kinds
of parameters) is required.
By doing this, the same kinds of parameters used in the selected data appear in the
data input fields. (This option is available only when the display area contains
some data.)
NEC PRACTICE
PRC-040-2120 8 of 10
Stage 3: Execute Trunk Test
1 Test new trunks.
NEC PRACTICE
PRC-040-2120 9 of 10
1-C Specify the trunk to be tested and execute the test.
1-D Click [Close] button to close [Trunk Test] icon.
Notes:
Translator.
2 If the test result is NG, check the office data and retry the operation.
Stage 4: Activate Translator
NEC PRACTICE
PRC-040-2120 10 of 10
Note: A set of the data can be selected from the display area. The selected set of data
will be displayed in appropriate data input fields respectively.
The values in the fields can be changed after that. (This method is available only
when the display area contains data.)
NEC PRACTICE
PRC-040-2130-23 (E) Destination Closes without Direct Routes
PRC-040-2130 1 of 8
Destination Closes without Direct Routes
1. SUMMARY
If an office and a closed destination are interconnected via transit routes, the office has to delete the
transit routing information. Fig. 1 shows an example.
This task provides step-by-step procedures for deletion of transit routing information for a closed
destination.
Fig. 1 Transit Route Deletion Example
2.1 Icon to Use
[Translation] icon
[Routing] icon
Closed
destination B
DN=0123
Office
Destination A
Destination C
Route ogta
Route ogtc
A
C
Delete route
index dstb
Route index dsta
B
NEC PRACTICE
Destination Closes without Direct Routes PRC-040-2130-23 (E)
PRC-040-2130 2 of 8
The procedure for deletion of transit routing information for a closed destination consists of the
following stages of operation:
Stage 1: Delete translator
Stage 2: Delete routing data
Stage 3: Activate translator
3.2 Operation Flow
Directory Number [Translation] icon Translates digits of directory
number.
Routing decision and charge
index are derived from the
translation result.
0123
dsta, dstb
[CCC..]
[CCC..]
NEC PRACTICE
PRC-040-2130 3 of 8
Procedures for deletion of transit routing information for a closed destination are explained below.
Stage 1: Delete Translator
1 Delete translator.
pulldown menu.
1-C Select Delete from Operation field.
Start
Stage 1
[Translation]
Delete translator by selecting
Directory Number
[Routing]
Stage 2
Yes
No
PRC-040-2320
Delete OOC
End
Stage 3
[Translation] Activate new translator
OOC : Out of Chain
Delete OOC?
Delete route index
Yes
No
[Routing]
route index?
Delete
NEC PRACTICE
PRC-040-2130 4 of 8
Fig. 3 Translation Window (Delete)
1-D Specify Translator Identification field.
Notes:
1 The fields to be specified vary depending on what is selected in Translator
Identification field.
2 A set of the data can be selected from the display area. The selected set of data is
displayed in appropriate data input fields respectively.
NEC PRACTICE
PRC-040-2130 5 of 8
OOC data before deleting route index.
For details, refer to PRC-040-2320 Create/Modify/Delete OOC Routing Feature.
1-C Specify Route Index and Processing Identifier fields, and click [Execute] button.
1-D Select Delete from Operation field.
[Routing] (Delete) window is displayed.
NEC PRACTICE
PRC-040-2130 6 of 8
1-E Select Routing Data from Data Type field.
1-F Specify Object Type field.
1-G Specify the rest of the data input fields.
field.
1-H Click [Execute] button.
1-I Click [Close] button to close the icon.
NEC PRACTICE
PRC-040-2130 7 of 8
Note: A set of the data can be selected from the display area. The selected set of data
will be displayed in appropriate data input fields respectively.
NEC PRACTICE
PRC-040-2130 8 of 8
NEC PRACTICE
PRC-040-2140-26 (E) Add Direct Routes to Existing Destination
PRC-040-2140 1 of 18
Add Direct Routes to Existing Destination
1. SUMMARY
When an network plan changes, an office may need reform of routing:
Add direct routes to a destination
Only transit routes can exist between an office and a destination. As a result of the reform,
traffic to the destination is routed via direct routes.
This reform comprises of addition of Outgoing (OG) and Incoming (IC) routes.
Delete direct routes to a destination
Direct routes can exist between an office and a destination. As a result of the reform, traffic
to the destination is routed via transit routes.
This reform comprises of deletion of OG and IC routes.
Change route selection
This reform comprises of addition/deletion of alternative routes, change of route selection
order, or diversion of traffic to other route indexes.
This module provides step-by-step procedures for adding direct routes to an existing destination. Fig. 1
and Fig. 2 show the examples.
Procedures for other reforms are provided in PRC-040-2150 Delete Direct Routes to Existing
Destination, and PRC-040-2160 Change Route Selection.
Fig. 1 OG Route Addition Example
New route
index dstb
Destination B
DN=0123
Office
Dials 0123-XXX-XXXX
Destination A
Destination C
Existing
routeogta
Existing
routeogtc
A
C
B
New route ogtb
OGT
New OG trunk
ogtb0001
OG
OGT
Existing route
index dsta
: Outgoing
: Outgoing Trunk
NEC PRACTICE
Add Direct Routes to Existing Destination PRC-040-2140-26 (E)
PRC-040-2140 2 of 18
Fig. 2 IC Route Addition Example
2.1 Icon to Use
[Route Profile] icon
[Route Data] icon
[Trunk] icon
[Routing] icon
[Translation] icon
Table 1 Fundamental Data Fields (1/2)
icon
Trunk (OGT).
ogttup, icttup
Destination B
Office
Destination A
Destination C
A
C
B
New route ictb
ICT
New IC trunk ictb0002
IC
ICT
: Incoming
: Incoming Trunk
NEC PRACTICE
PRC-040-2140 3 of 18
The procedure of addition of direct routes to an existing destination consists of the following stages of
operation:
Stage 2: Create/Modify Routing Data
Stage 3: Modify Translator
Note: Addition of IC routes requires Stages 1, 4 and 5.
3.2 Operation Flow
ogtb, ictb
Circuit Name [Trunk] icon Designates trunks for IC/OG routes. ogtb0001, ictb0002
dsta, dstb
Directory
Number
number.
result.
0123
[CCC..]
[CCC..]
Non-office data icons used in this module. Refer to related manuals for
details.
NEC PRACTICE
PRC-040-2140 4 of 18
Start
Stage 1
Stage 2
Stage 3
[Route Profile]
[Route Data]
[Trunk]
[Routing]
Create Profile
Name
Create Route Name
Create trunks by
entering Circuit Name
Create Route Index/
add direct route
IC route or
OG route?
IC route
OG route
Create
Profile Name?
Yes
No
[Translation]
[Trunk Test]
Test new trunks
OK
Test result
is OK?
Check office data
and retry
NG
Modify translator
Stage 4
Proceed to Stage 5
No
Yes
New Route
Index?
NEC PRACTICE
PRC-040-2140 5 of 18
Procedures for addition of direct routes to an existing destination are explained below:
Notes:
1 To create a new profile name, start with STEP 1 Create Profile Name.
2 To apply an existing profile name, start with STEP 2 Create Route Name.
[Trunk]
Place new trunks in service
IC route or
OG route?
IC route
OG route
[Translation]
End
Stage 5
No
Yes
Translator
modified?
Activate new
translator
NEC PRACTICE
PRC-040-2140 6 of 18
1-C Specify Profile Name, Protocol Type, Trunk Type, Line Information and Satellite
Indicator fields.
1-D Specify the rest of data input fields.
Note: The fields to be specified vary depending on what is selected in any of the fields
above.
NEC PRACTICE
PRC-040-2140 7 of 18
[Route Data] (Create) window is displayed.
-or-
NEC PRACTICE
PRC-040-2140 8 of 18
2-D Specify other appropriate data input fields.
If the fields to be specified are not found in [Parameter 1] tag, click [Parameter 2] or
[Parameter 3] tag.
click [OK] button.
click [OK] button.
To specify a route name Select Specific Route from the list in Type Of
Selection field. Enter a route name by typing or by
selecting from the list. Click [OK] button.
To refresh the route
name list
Click [Refresh] button. The list shows the
previously acquired information and may not show
the current host status. Clicking this button updates
the information.
To narrow down the
route name list by the
first letter of the name
Select the first letter in Index field. The narrowed
down route names are shown in Available Route(s)
field.
NEC PRACTICE
PRC-040-2140 9 of 18
3 Create trunks.
3-C Specify object type in Object Type field.
3-D Specify Equipment Trunk field.
3-E Specify other data input field(s.)
field.
field.
When Circuit Number & Circuit Identification Code is selected in Object Type
field, specify Circuit Number and Circuit Identification Code fields.
Notes:
1 To add OG route, proceed to Stage 2-A Create Routing Data.
2 To add IC route, proceed to Stage 4 Execute Trunk Test.
NEC PRACTICE
PRC-040-2140 10 of 18
Stage 2-A: Create Routing Data
1 Create Route Index.
[Routing] (Create) window is displayed.
1-C Select Routing Data from Data Type field.
1-D Specify a new route index in Route Index field.
1-E Enter appropriate data in Processing Identifier field.
-or-
NEC PRACTICE
PRC-040-2140 11 of 18
1-F Click [Edit...] button, and specify routing data.
[OK] button.
click [OK] button.
button.
To specify specific
selectable values
[OK] button.
Click [OK] button.
NEC PRACTICE
PRC-040-2140 12 of 18
Notes:
1 To create Out of Chain (OOC) routing, refer to PRC-040-2320, Create/Modify/
2 To create Time of Day (TOD) routing, refer to Traffic Control Manual.
To add routing data Click [Add...] button. Another dialog is
displayed. Specify appropriate data in the dialog,
and click [OK] button.
To modify routing data Select the data to modify from the list. Click
[Edit...] button. Another dialog is displayed.
Specify appropriate data in the dialog, and click
[OK] button.
routing data
Select appropriate data from the list. Click up or
down arrow so that the order changes. Click [OK]
button.
To remove routing data Select appropriate data from the list, and click
[Remove] button. Then click [OK] button.
NEC PRACTICE
PRC-040-2140 13 of 18
Stage 2-B: Modify Routing Data
Note: If the destination has already been assigned to a specific route index, add the direct route
to current route selections.
1 Add direct route.
1-C Specify Route Index and Processing Identifier fields.
Note: For Processing Identifier field, refer to Fig. 9 and follow its procedure.
The screen changes to [Routing] (Modify) window.
NEC PRACTICE
PRC-040-2140 14 of 18
Fig. 12 Routing Window (Modify)
1-E Make sure that the current routing data for the route index are displayed in Data
Type, Route Index and Processing Identifier fields.
1-F Click [Edit...] button to open Routing Data dialog, and specify route data to be
added. (See Fig. 10 and follow its procedure.)
Note: If it is unnecessary to modify translator, proceed to Stage 4 Execute Trunk
Test.
1 Modify translator.
pulldown menu.
1-C Select Modify in Operation field.
The screen changes to [Translation] (Modify) window.
Note: This operation cannot be executed when the no data is shown in the list view. In
this case, acquire data by performing View operation first, then Modify
operation.
NEC PRACTICE
PRC-040-2140 15 of 18
Fig. 13 Translation Window (Modify)
1-D Select the data to be modified from the List View.
1-E Specify the rest of data input fields.
Notes:
1 Modify can not be executed when the List View shows no data. Get data by
performing View operation first. Then, perform Modify operation.
2 A set of the data can be selected from the display area. The selected set of data will
be displayed in appropriate data input fields respectively.
To copy data format from other data, check Command Pattern Reflection under
some data.)
NEC PRACTICE
PRC-040-2140 16 of 18
1 Test new trunks.
NEC PRACTICE
PRC-040-2140 17 of 18
1-C Specify the trunk to be tested and execute test.
1-D Close [Trunk Test] icon.
Notes:
Translator.
2 If the test result is NG, check office data and retry the operation.
1-B Select In Service from Operation field.
1-C Select an appropriate object type from Object Type field.
field.
Trunk field.
field.
NEC PRACTICE
PRC-040-2140 18 of 18
Note: For IC route, select View from Operation field and specify the IC route name.
Then repeat STEPs 1-B to 1-D.
Notes:
1 To add OG route, proceed to STEP 2, Activate new translator.
2 To add IC route, end the operation.
2-B Select Activate from Operation field.
NEC PRACTICE
PRC-040-2150-25 (E) Delete Direct Routes to Existing Destination
PRC-040-2150 1 of 14
Delete Direct Routes to Existing Destination
1. SUMMARY
When a network plan is changed, the routing data may also need to be changed as follows:
Outgoing (OG) and Incoming (IC) routes should be added so that calls to the destination can
be routed via direct routes.
The OG and IC routes should be deleted so that the calls to the destination can be routed via
transit routes.
Alternate routes should be added/deleted, route selection order should be changed, or calls
should be diverted to other routes.
This module provides step-by-step procedures for deletion of direct routes to an existing destination.
Fig. 1 and Fig. 2 show examples.
Procedures for other reforms are provided in PRC-040-2140 Add Direct Routes to Existing
Destination and PRC-040-2160 Change Route Selection.
Fig. 1 OG Route Deletion Example
Delete/keep route
index dstb
Destination B
DN=0123
Office
Dials 0123-XXX-XXXX
Destination A
Destination C
Route ogta
Route ogtc
A
C
B
Delete route ogtb
OGT
Delete OG trunk
ogtb0001
OG
OGT
Divert to route
index dsta
: Outgoing
: Outgoing Trunk
NEC PRACTICE
Delete Direct Routes to Existing Destination PRC-040-2150-25 (E)
PRC-040-2150 2 of 14
Fig. 2 IC Route Deletion Example
2.1 Icon to Use
[Translation] icon
[Routing] icon
[Trunk] icon
[Route Data] icon
which other data fields have to be defined, and are used as indexes of the office data.
Table 1 shows fundamental data fields. For other data fields, refer to DDS module of the icon.
Destination B
Office
Destination A
Destination C
A
C
B
Delete route ictb
ICT
Delete IC trunk
ictb0002
IC
ICT
: Incoming
: Incoming Trunk
NEC PRACTICE
PRC-040-2150 3 of 14
The procedure for deletion of direct routes to an existing destination consists of the following stages of
operation:
Stage 1: Place Trunk Out of Service
Note: Deletion of IC routes requires Stages 1 and 4.
3.1 Operation Flow
Fig. 3 shows an example of the operation flow. In the figure, the following convention is used:
Directory
Number
number.
result.
0123
Route Index [Routing] icon Defines specific OG route
selections to destination.
dstb, dsta
Circuit Name [Trunk] icon Designates trunks for IC/OG routes ogtb0001, ictb0002
ogtb, ictb
[CCC..]
NEC PRACTICE
PRC-040-2150 4 of 14
Procedures for deletion of direct routes to an existing destination are explained below.
Start
Stage 1
Stage 2
[Trunk]
[Translation]
[Route Data]
Place trunks out of service
Modify translator
IC route or
OG route?
IC route
OG route
[Routing]
Stage 3
[Trunk]
End
Delete trunks by entering
circuit name
Delete route name
IC route or
OG route?
IC route
OG route
Stage 5
[Translation]
Activate new
translator
Stage 4
Delete route index/delete
direct route
Delete
route index?
No
Yes
NEC PRACTICE
PRC-040-2150 5 of 14
1-B Select Out of Service from Operation field.
[Trunk] (Out of Service) window is displayed.
1-C Specify appropriate data in Object Type field.
field.
Trunk field.
field.
NEC PRACTICE
PRC-040-2150 6 of 14
Notes:
1 To delete the current route index and divert calls to others, proceed to Stage 2
Modify Translator.
2 To keep the current index and delete the direct route, proceed to Stage 3 Delete
Routing Data.
3 To delete IC route, proceed to Stage 4 Delete Trunk Data.
pulldown menu.
1-C Select Modify in Operation field.
operation.
1-D Select the data to be modified from the List View.
NEC PRACTICE
PRC-040-2150 7 of 14
1-E Specify another data input field.
Notes:
some data.)
OOC data before deleting route index.
Refer to PRC-040-2320 Create/Modify/Delete OOC Routing Feature.
NEC PRACTICE
PRC-040-2150 8 of 14
-or-
NEC PRACTICE
PRC-040-2150 9 of 14
[OK] button.
click [OK] button.
button.
To specify specific
selectable values
[OK] button.
Click [OK] button.
NEC PRACTICE
PRC-040-2150 10 of 14
field.
1 Delete trunks.
NEC PRACTICE
PRC-040-2150 11 of 14
Fig. 9 Trunk Window (View)
1-B Specify Circuit Trunk in Data Type field.
1-C Specify Object Type field.
field.
Trunk field.
field.
When None is selected in Object Type field, only those in the installed state
are displayed.
1-E Specify View Element field.
When All is selected, all objects whether installed or not installed are
displayed.
Note: This field becomes selectable only when items except None are selected in
Object Type field.
1-F Select Delete from Operation field, and click [Execute] button.
NEC PRACTICE
PRC-040-2150 12 of 14
-or-
NEC PRACTICE
PRC-040-2150 13 of 14
Note: To delete OG route, proceed to Stage 5 Activate New Translator.
To specify all Select All Route, and click [OK] button.
To omit specifying Select No Route, and click [OK] button.
To specify a route name Select Specific Route from the list. Enter a route
name by typing or by selecting from the list. Click
[OK] button.
To edit entered data Select Specific Route from the list, and select data
to be edited from the list. Click [Edit] button. Edit
data in dialog window field. To edit multiple route
name, repeat above operations. Click [OK] button.
To remove entered data Select Specific Route from the list, and select data
to be removed from the list. Click [Remove] button.
Edit data in dialog window field. To remove multiple
route name, repeat above operations. Click [OK]
button.
NEC PRACTICE
PRC-040-2150 14 of 14
Note: Clicking COMMON tab selects the COMMON sheet for the data setting.
NEC PRACTICE
PRC-040-2160-23 (E) Change Route Selection
PRC-040-2160 1 of 12
Change Route Selection
1. SUMMARY
According to the change of network plan, an office may also need to change routing data as follows:
Outgoing (OG) and Incoming (IC) routes are to be added so that calls to the destination can
be routed via direct routes.
The OG and IC routes are to be deleted so that calls to the destination can be routed via
transit routes.
Alternate routes are to be added/deleted, route selection order is to be changed, or calls are to
be diverted to other routes.
This module provides step-by-step procedures for some practical cases of changing route selection.
Figs. 1 to 4 show examples.
Procedures for other changes relating routing are provided in PRC-040-2140 Add Direct Routes to
Existing Destination, and PRC-040-2150 Delete Direct Routes to Existing Destination.
Fig. 1 Alternate Route Addition Example
Route index
dstb
Office
Destination B
DN=0123
Destination C
B
C
A
Route ogtb
Destination A
Route ogta
Route ogtc
Before addition:
route 00 (primary route)=ogtb
route 01 (first alternate route)=ogta
Addition:
route 02 (second alternate route)=ogtc
Dials 0123-XXX-XXXX
NEC PRACTICE
Change Route Selection PRC-040-2160-23 (E)
PRC-040-2160 2 of 12
Fig. 2 Alternate Route Deletion Example
Fig. 3 Example of Changing Route Selection Order
Office
Destination C
B
C
A
Route ogtb
Destination A
Route ogta
Route ogtc
Before deletion:
route 00 (primary route)=ogtb
route 01 (first alternate route)=ogta
Deletion:
Dials 0123-XXX-XXXX
Destination B
DN=0123
Route index
dstb
01
Dials 0123-XXX-XXXX
Route index dstb
Office
Destination C
B
C
A
Route ogtb
Destination A
Route ogta
Route ogtc
Changed from:
route 00: (primary route)=ogtb
route 01: (first alternate route)=ogta
route 02: (second alternate route)=ogtc
Change to:
route 00: (primary route)=ogtb
route 01: (first alternate route)=ogtc
route 02: (second alternate route)=ogta
00
02
Destination B
DN=0123
XX indicates
selection order
after change
NEC PRACTICE
PRC-040-2160 3 of 12
Fig. 4 Example of diverting to Other Route Indexes
2.1 Icon to Use
This task involves modification of office data by using the following icons:
[Routing] icon
[Translation] icon
Route Index [Routing] icon Defines OG route selections specific
to destination.
dsta, dstb, dstc
Directory
Number
[Translation] icon Translates digits of directory number.
Routing decision and charge index are
derived from the translation result.
0123
Divert to Route
Index dstc
Current Route
Index dsta
Office
Destination A
A
C
Route ogta
Route ogtc
Destination C
Dials 0123-XXX-XXXX
Destination B
DN=0123
B
NEC PRACTICE
PRC-040-2160 4 of 12
The procedure for change of route selection provides the following cases of operation:
Case 1: Add Alternate Route
Case 2: Delete Alternate Route
Case 3: Change Route Selection Order
Case 4: Divert to Other Route Indexes
3.2 Operation Flow
Fig. 5 shows an example of the operation flow. In the figure, the following convention is used:
Procedures for change of route selection are explained below.
[CCC..]
Start
[Translation]
[Routing]
End
Case1:
Add alternate route
Case2:
Delete alternate route
Case3:
Change route selection order
Case4:
Divert to other route
indexes
Operation
Case 4
Cases 1 to 3
NEC PRACTICE
PRC-040-2160 5 of 12
Case 1: Add Alternate Route
1 Add alternate route.
-or-
NEC PRACTICE
PRC-040-2160 6 of 12
[OK] button.
click [OK] button.
button.
To specify specific
selectable values
[OK] button.
Click [OK] button.
NEC PRACTICE
PRC-040-2160 7 of 12
1-F Select Create from Operation field.
The screen changes to [Routing] (Create) window.
1-H Specify Route Index field.
1-I Specify Processing Identifier field (refer to Fig. 7 and follow its procedure.)
1-J Click [Edit...] button, and specify routing data.
NEC PRACTICE
PRC-040-2160 8 of 12
1-K Click [Execute] button.
1-L Click [Close] button to close the icon.
Case 2: Delete Alternate Route
1 Delete alternate route.
[Routing] (View) window is displayed (see Fig. 6.)
1-D Specify Processing Identifier field (see Fig. 7 and follow its procedure.)
Routing data is displayed.
Note: If the alternate route to be deleted applies Out of Chain (OOC) routing feature,
delete OOC routes before deleting the alternate route. Refer to PRC-040-2320
Create/Modify/Delete OOC Routing Feature.
Specify appropriate data in the dialog, and click [OK]
button.
To modify routing data Select the data to modify from the list. Click [Edit...]
button. Route dialog is displayed. Specify appropriate
data in the dialog, and click [OK] button.
routing data
Select appropriate data from the list, and click up or
down arrow to change the order. Then click [OK]
button.
NEC PRACTICE
PRC-040-2160 9 of 12
field.
Notes:
1 Delete operation can delete route index number only.
2 The data to be deleted can also be selected from the display area. The data selected
will be set to respective controls in the data input fields.
The values in the fields can be changed. (This method is available only when the
display area contains data.
Case 3: Change Route Selection Order
1 Change route selection order.
NEC PRACTICE
PRC-040-2160 10 of 12
Routing data is displayed.
1-F Select Modify from Operation field.
[Routing] (Modify) window is displayed.
1-I Specify Processing Identifier field (refer to Fig. 7 and follow its procedure.)
1-J Click [Edit...] button, and specify routing data (refer to Fig. 9 and follow its
procedure.)
Case 4: Divert to other route indexes
NEC PRACTICE
PRC-040-2160 11 of 12
Fig. 12 Translation Window (View)
1-B Specify Translator Identification field.
1-C Click [Execute] button.
1-D Select Modify in Operation field.
operation.
NEC PRACTICE
PRC-040-2160 12 of 12
1-E Select the data to be modified from the List View.
1-F Specify another data input field.
Notes:
some data.)
NEC PRACTICE
PRC-040-2320-16 (E) Create/Modify/Delete OOC Routing Feature
PRC-040-2320 1 of 8
Create/Modify/Delete OOC Routing Feature
1. SUMMARY
Applying Out of Chain (OOC) routing feature in routing data allows each alternate route to own up to
four substitution routes. These substitution routes are called OOC routes. Fig. 1 shows an example of
OOC route.
This task provides step-by-step procedures for creation, modification, and deletion of OOC routing
feature.
Fig. 1 OOC Routing Example
2.1 Icon to Use
This task involves creation, modification, and deletion of office data by using the following icon:
[Routing] icon
Alternate route
ogta
OOC
routes
ogtc
Destination A
Office
B
A
Primary route
ogtb
C D E
Destination B
DN=0123
Dials 0123-XXX-XXXX
Route index dstb
ogte ogtd
OOC: Out of Chain
Route index dstb
NEC PRACTICE
Create/Modify/Delete OOC Routing Feature PRC-040-2320-16 (E)
PRC-040-2320 2 of 8
The procedure provides the following cases of operation:
Case 1: Create OOC routing feature
Case 2: Modify OOC routing feature
Case 3: Delete OOC routing feature
3.2 Operation Flow
(1) Create OOC routing feature after adding the alternate route with [Routing] icon.
(2) Modify OOC routing feature while the alternate route is existing with [Routing] icon.
(3) Delete OOC routing feature before deleting the alternate route with [Routing] icon.
Procedures for creation, modification and deletion of OOC routing feature are explained below:
Case 1: Create OOC Routing Feature
1 Create OOC routes.
1-A Activate [Routing] icon from [Routing Control] icon group.
Route Index [Routing] icon Defines OG route selections specific
to destination.
dstb
Route
(except Route of
Number 00)
Creates an alternate route.
OOC routing feature allows the
alternate route to own up to four
substitution routes.
ogta
NEC PRACTICE
PRC-040-2320 3 of 8
-or-
NEC PRACTICE
PRC-040-2320 4 of 8
[OK] button.
click [OK] button.
button.
To specify specific
selectable values
[OK] button.
Click [OK] button.
NEC PRACTICE
PRC-040-2320 5 of 8
The routing data is displayed.
1-F Select Create from Operation field.
1-G Select Out of Chain Route from Data Type field.
1-I Specify Processing Identifier field (see Fig. 3 and follow its procedure.)
1-J Click [Edit...] button, and specify the OOC data.
NEC PRACTICE
PRC-040-2320 6 of 8
[OK] button.
To modify routing data Select the data to be modified from the list.
Click [Edit...] button. Route dialog is displayed.
[OK] button.
routing data
Select appropriate data from the list, and click
up or down arrow so that the order changes.
Then click [OK] button.
NEC PRACTICE
PRC-040-2320 7 of 8
Case 2: Modify OOC Routing Feature
1 Modify OOC routes.
[Routing] (View) window is displayed. (See Fig. 2.)
1-F Select Modify from Operation field.
[Routing] (Modify) window is displayed.
1-J Click [Edit...] button to specify OOC data (see Fig. 5 and follow its procedure.)
NEC PRACTICE
PRC-040-2320 8 of 8
Case 3: Delete OOC Routing Feature
1 Delete OOC routing feature.
NEC PRACTICE
PRC-040-2500-15 (E) Adjacent Node Opens
PRC-040-2500 1 of 14
Adjacent Node Opens
1. SUMMARY
When a signaling node opens in the network of Common Channel Signaling No.7 (CCS7), direct
connections and transmit messages should be set directly to the signaling node. For an adjacent node,
the messages must be transmitted via signaling transfer points.
Note: The signaling nodes that have direct connections are called adjacent nodes, and those
without direct connections are called non-adjacent nodes.
Connections with adjacent nodes are set with the following data:
(1) Own node data:
New node name, network indicator and point code.
(2) Signaling link data:
Signaling links and link groups are within the scope. Connections among signalling nodes
are physically the numbers of signaling links. Those signaling links that have the same link
attributes are regarded as a signaling group.
(3) Signaling route data:
Signaling routes are transmission paths which is set over signaling links for sending
messages to their destinations. When the destination is an adjacent node, direct signaling
routes are to be set.
This task provides step-by-step procedures for setting up connections with an adjacent node. If the
destination is a non-adjacent node, refer to PRC-040-2600, Non-Adjacent Node Opens.
Fig. 1 Connection to Adjacent Node Setup Example
Add adjacent node
Own Node
NI=1
PC=00001
NI=2, PC=00002
LGN
NI
PC
SLK
uninstalled tstopc0
tstopc1
adj0
NI=2, PC=10001
Add SLK:1
Add SLK:2
Add LGN:1(Main/adjacent route)
: Added Node
: Added Link Group, Route
: Added Link
: Signaling Link Group
: Network Indicator
: Point Code
: Signaling Link
NEC PRACTICE
Adjacent Node Opens PRC-040-2500-15 (E)
PRC-040-2500 2 of 14
2.1 Icon to Use
[Own Signaling Point] icon
[CCS7 Link Group] icon
[CCS7 Link] icon
[CCS7 Routing] icon
which other data fields have to be defined, and are used as indexes of the office data. Table 1 shows the
Node Name [Own Signaling
Point] icon
Defines own nodes name.
A signaling node contains up to four
node names, each of which is assigned
to a different Network Indicator and
Point Code.
tstopc1
Network
Indicator/Point
Code
Defines Network Indicator and Point
Code of own node.
2/00002
Link Group
Number
[CCS7 Link
Group] icon
Defines Link Group Number to which
the signaling link belongs.
001
Signaling Link
Number
[CCS7 Link] icon Assigns Signaling Link Number to
add.
0001, 0002
Node Name [CCS7 Routing]
icon
Node Name set in this icon is the
destination.
adj0
Network
Indicator/Point
Code
Code of the destination.
2/10001
Adjacent/Main/
Sub Link Group
Number
Defines signaling routes. To an
adjacent destination, direct routes are
set over the link groups that connect
the nodes.
Adjacent/Main:
001
Sub: None
NEC PRACTICE
PRC-040-2500 3 of 14
The procedure of setting up connections with an adjacent node consists of the following stages of
operation:
Stage 1: Create Own Node Name
Stage 2: Create Signaling Link Groups and Links
Stage 3: Create Destination Nodes and Signaling Routes
Stage 4: Start Signaling Links
Stage 5: Unblock Signaling Routes
Note: If it is unnecessary for the node to create a new node name, omit Stage 1.
3.2 Operation Flow
[CCC..]
[CCC..]
NEC PRACTICE
PRC-040-2500 4 of 14
Procedures for setting up connections with an adjacent node are explained below.
Start
Stage 1
Stage 3
[Own Signaling Point]
[CCS7 Link Group]
Create own
node name
Need a
new node name?
No
[CCS7 Link]
Create signaling link groups
Yes
Yes
Stage 2
[CCS7 Routing]
Stage 4
Create signaling links
Create destination nodes
and signaling routes
End
[CCS7 Link]
Start signaling links
Need a
speech path?
Yes
No
PRC-040-2100,Destination Opens
with Direct Routes or
PRC-040-2120,Destination Opens
without Direct Routes
Stage 5 [CCS7 Routing]
Unblock signaling routes
to the destination
NEC PRACTICE
PRC-040-2500 5 of 14
Stage 1: Create Own Node Name
Note: If the node does not need a new node name, omit this step.
1 Create own node name.
1-A Activate [Own Signaling Point] icon from [CCS7] icon group.
[Own Signaling Point] (View) window is displayed.
1-B Select Create in Operation field.
Fig. 3 Own Signaling Point Window (Create)
1-C Specify Node Name field.
-or-
Click [...] button to open Node Name dialog, and specify node name.
NEC PRACTICE
PRC-040-2500 6 of 14
Fig. 4 Node Name Dialog
1-D Specify Network Indicator, Point Code, Own Signaling Point Kind and Protocol
Type fields.
Notes:
1 The point code must conform to its protocol type.
2 The data to be specified can also be selected from the display area. The data
selected will be displayed to the respective data input fields. The values in the fields
can be changed. (This method is available only when the display area contains
To specify all nodes Select All Node, and click [OK] button.
To omit the setting Select No Node, and click [OK] button.
To specify a node Select Specific Node from the list, and select the
node from the list or enter it directly in the box.
Then click [OK] button.
To refresh the list of nodes Click [Refresh] button. Push this button in case
the latest data is not displayed in Available
Node(s) list box.
To narrow down a list of
node names by their initial
alphabet
Select the initial alphabet from Index list box.
The narrowed down nodes starting with the
alphabet are displayed in the Available Node(s)
list box.
Note: To display all nodes, select All in Index list
box.
NEC PRACTICE
PRC-040-2500 7 of 14
data.)
The created own node name is displayed in list box.
Stage 2: Create Signaling Link Groups and Links
1 Create signaling link groups.
1-A Activate [CCS7 Link Group] icon from [CCS7] icon group.
[CCS7 Link Group] (View) window is displayed.
The screen changes to [CCS7 Link Group] (Create) window.
Fig. 5 CCS7 Link Group Window (Create)
1-C Specify Link Group Number, Kind Adjacent, Signal Link Attribute, Main Network
NEC PRACTICE
PRC-040-2500 8 of 14
Indicator, In Network Indicator and Out Network Indicator fields.
Note: Enter data in both In Network Indicator and Out Network Indicator fields,
otherwise select (None) for both of them.
The created link groups are displayed in list box.
2 Create signaling links.
2-A Activate [CCS7 Link] icon from [CCS7] icon group.
[CCS7 Link] (View) window is displayed.
Fig. 6 CCS7 Link Window (Create)
2-C Specify Signal Link Number, Link Group Number, Signal Link Code, Common
Signaling Channel and Channel fields.
Note: The data to be created can also be selected from the display area. The data
selected will be displayed in the respective data input fields. (This method is
available only when the display area contains data.)
NEC PRACTICE
PRC-040-2500 9 of 14
The created signaling link is displayed in list box.
Note: Leave this window opened; procedure in this window continues to Stage 4
Start Signaling Links.
1 Create destination nodes.
1-A Activate [CCS7 Routing] icon from [CCS7] icon group.
[CCS7 Routing] (View) window is displayed.
Fig. 7 CCS7 Routing Window (Create)
1-C Specify Route Data or Partial Translation Routing Data in Data Type field.
2 Create signaling routes.
2-A Specify Node Name, Network Indicator, Point Code, Main Link Group Number,
Adjacent Link Group Number, Sub 1/2/3 Link Group Number and Shift Bit
Pattern fields.
NEC PRACTICE
PRC-040-2500 10 of 14
Notes:
1 When Partial Translation Routing Data is specified in Data Type field, Adjacent
Link Group Number field cannot be specified.
2 Point Code field must be set with Network Indicator field.
2-B Click [Execute] button.
The created destination node names are displayed in list box.
2-C Select the destination node name in list box, then select View in Operation field.
The screen changes to [CCS7 Routing] (View) window, and the destination node
status is displayed.
2-D Make sure that the node status became inaccessible and is blocked.
Stage 4: Start Signaling Links
1 Start signaling links.
1-A Select Start in Operation field.
Fig. 8 CCS7 Link Window (Start)
1-B Specify Data Type field.
NEC PRACTICE
PRC-040-2500 11 of 14
1-C Specify Signal Link Number field.
Note: The data to be specified can also be selected from the display area. The selected
data is set to respective data input fields. (This method is only available when
the display area contains data.)
1-E Select View in Operation field.
The screen changes to [CCS7 Link] (View) window.
Fig. 9 CCS7 Link Window (View)
1-F Select Status Information from Data Type field.
1-G Enter appropriate value in Signal Link Number field.
-or-
Click [...] button to open Signal Link Number dialog, and specify the number.
Note: Selecting (None) displays status of all signalling links.
NEC PRACTICE
PRC-040-2500 12 of 14
Fig. 10 Signal Link Number Dialog
1-H Make sure that the link status of the added links is displayed in the list box.
Note: If the status is not available, select Stop in Operation field and execute the stop
procedure of the signalling link. Then start the signalling link procedure again.
1-I Click [Close] button to close the icon.
Note: The data to be created can also be selected from the display area. The data
selected will be displayed in the respective data input fields. (This method is
available only when the display area contains data.)
To specify all data Select All, and click [OK] button.
To omit the setting Select None, and click [OK] button.
To specify special strings Select Special. A different label, such as Skip,
Cancel, or nothing appears depending on
command. Then click [OK] button.
To specify a specific digit Select Specific Numeric Data. Enter the digit in
the field, and click [OK] button.
To specify the data by
range
Select Ranged Numeric Data. Enter a couple of
the digits in From and To fields. Click [OK]
button.
NEC PRACTICE
PRC-040-2500 13 of 14
1 Unblock signaling routes to the destination.
1-B Select Unblock in Operation field.
Fig. 11 CCS7 Routing Window (Unblock)
1-C Select Node Name or Point Code in Object Type field.
field.
When Node Name is selected in Object Type field, specify Node Name and
Link Group Number fields.
When Point Code is selected in Object Type field, specify Network Indicator,
Point Code and Link Group Number fields.
Note: If the selected parameters are to be changed after selecting the data, the
parameters can be changed by specifying new parameters in appropriate fields.
NEC PRACTICE
PRC-040-2500 14 of 14
The specified signaling link group is unblocked.
Note: When adding a speech path to the destination node, follow the procedures of
PRC-040-2100, Destination Opens with Direct Routes or PRC-040-2120,
Destination Opens without Direct Routes.
NEC PRACTICE
PRC-040-2510-15 (E) Adjacent Node Closes
PRC-040-2510 1 of 12
Adjacent Node Closes
1. SUMMARY
When an adjacent node closes, the following data must be deleted:
(1) Signaling route data:
Destination node and related signaling routes
(2) Signaling link data:
Signaling link groups and links that connect own (home) node and an adjacent node
(3) Own node data:
Own node name and point code that connect with the adjacent node
This task provides step-by-step procedures for deleting connections with an adjacent node. If the
destination is a non-adjacent node, refer to PRC-040-2610 Non-Adjacent Node Closes.
Fig. 1 Connection to Adjacent Node Deletion Example
Delete adjacent node
Own node
NI=1
PC=00001
NI=2, PC=00002
uninstalled
tstopc0
tstopc1
adj0
NI=2, PC=10001
Delete SLK:1
Delete SLK:2
Delete LGN:1(Main/adjacent route)
LGN
NI
PC
SLK
: Signaling Link Group
: Network Indicator
: Point Code
: Signaling Link
: Deleted Node
: Deleted Link Group
: Deleted Link
NEC PRACTICE
Adjacent Node Closes PRC-040-2510-15 (E)
PRC-040-2510 2 of 12
2.1 Icon to Use
[CCS7 Routing] icon
[CCS7 Link] icon
[CCS7 Link Group] icon
[Own Signaling Point] icon
which other data fields must be defined, and are used as indexes of the office data. Table 1 shows
icon
Node Name set in this icon is the
destination.
adj0
Network
Indicator/Point
Code
Defines Network Indicator and
Point Code of the destination.
2/10001
Adjacent/Main/
Sub Link Group
Number
Defines signaling routes. To an
adjacent destination, direct routes
are set over the link groups
connecting the node.
Adjacent/Main:
001 Sub: None
Signaling Link
Number
[CCS7 Link] icon Assigns Signaling Link Number to
delete.
0001, 0002
Link Group
Number
[CCS7 Link
Group] icon
Defines Link Group Number to
which the signaling link belongs.
001
Node Name [Own Signaling
Point] icon
Defines own node name.
A signaling node can have up to
four node names, each assigned a
different Network Indicator and
Point Code.
tstopc1
Network
Indicator/Point
Code
Point Code of own node.
2/00002
NEC PRACTICE
PRC-040-2510 3 of 12
The procedure of deleting connections with an adjacent node consists of the following stages of
operation:
Stage 1: Block Signaling Routes
Stage 2: Stop Signaling Links
Stage 3: Delete Destination Nodes and Signaling Routes
Stage 4: Delete Signaling Links and Link Group
Stage 5: Delete Own Node Name
Note: If it is unnecessary for the node to delete own node name, omit Stage 5.
3.2 Operation Flow
[CCC..]
[CCC..]
NEC PRACTICE
PRC-040-2510 4 of 12
Start
Stage 2
Stage 4
[CCS7 Link]
[CCS7 Routing]
Stop signaling links
[CCS7 Link Group]
Delete destination nodes
Stage 3
[Own Signaling Point]
Stage 5
Delete own node
name
End
Delete own
Yes
No
node name?
[CCS7 Routing]
Block signaling routes to
the destination
Stage 1
[CCS7 Link]
Delete signaling links
Delete signaling link groups
path exits?
Yes
No
Delete the speech path, then start this
procedure with Stage 3 again.
Refer to PRC-040-2110
Destination Closes with Direct Routes
or PRC-040-2130 Destination Closes
without Direct Routes.
A speech
NEC PRACTICE
PRC-040-2510 5 of 12
Procedures for deletion of connections with an adjacent node are explained below.
Stage 1: Block Signaling Routes
1 Block signaling routes to the destination.
1-A Click [CCS7 Routing] icon from [CCS7] icon group.
1-B Select Block in Operation field.
Fig. 3 CCS7 Routing Window (Block)
1-C Specify Data Type field.
1-D Specify Node Name field.
1-E Specify Link Group Number field.
NEC PRACTICE
PRC-040-2510 6 of 12
The specified signaling link group is blocked.
Stage 2: Stop Signalling Links
1 Stop signaling links.
1-A Click [CCS7 Link] icon from [CCS7] icon group.
1-B Select Stop in Operation field.
Fig. 4 CCS7 Link Window (Stop)
1-D Specify Signal Link Number field.
Stage 3: Delete Destination Nodes and Signaling Routes
NEC PRACTICE
PRC-040-2510 7 of 12
Note: If a speech path which is directed to a signaling node exists, delete the existing signaling
node before deleting the destination node and signaling routes. For details, refer to PRC-
040-2110 Destination Closes with Direct Routes or PRC-040-2130 Destination
Closes without Direct Routes.
1 Delete destination nodes and signaling routes.
1-B Select Delete in Operation field.
Fig. 5 CCS7 Routing Window (Delete)
When Routing Data by Node Name is selected in Data Type field, specify Node
Name field.
When Routing Data by Point Code is selected in Data Type field, specify
Network Indicator and Point Code fields.
Note: The data to be deleted can also be selected from the display area. The selected
NEC PRACTICE
PRC-040-2510 8 of 12
The destination and signaling routes are deleted.
Stage 4: Delete Signaling Links and Link Groups
1 Delete signaling links.
1-A Click [CCS7 Link] icon from [CCS7] icon group.
Fig. 6 CCS7 Link Window (Delete)
1-D Specify Signal Link Number field.
NEC PRACTICE
PRC-040-2510 9 of 12
2 Delete signaling link groups.
Notes:
1 Make sure that the signaling link group has no signaling links. If it does, stop the
operation and delete the existing signaling link beforehand.
2 If the signaling link group to be deleted is used as main/sub route in CCS7 routing data,
delete the signaling link group in the CCS7 routing data beforehand by using [CCS7
Routing] (Delete) window.
2-A Click [CCS7 Link Group] icon from [CCS7] icon group.
[CCS7 Link Group] (View) window is displayed.
Fig. 7 CCS7 Link Group Window (Delete)
2-D Specify Link Group Number field.
Note: If own node name is not to be deleted, omit Stage 5.
NEC PRACTICE
PRC-040-2510 10 of 12
Stage 5: Delete Own Node Name
1 Delete own node name.
Notes:
1 Make sure that own node has no signaling link groups by using [CCS7 Link Group]
(View) window. If it does, stop and delete the existing signaling link group beforehand.
2 Make sure that own node has no destination nodes by using [CCS7 Link Group] (View)
window. If it does, delete the existing destination node beforehand.
1-A Click [Own Signaling Point] icon from [CCS7] icon group.
[Own Signaling Point] (View) window is displayed.
Fig. 8 Own Signaling Point Window (Delete)
-or-
NEC PRACTICE
PRC-040-2510 11 of 12
Click [...] button to open Node Name dialog, and specify node name.
Fig. 9 Node Name Dialog
The own node name is deleted.
To specify all nodes Select All Node, and click [OK] button.
To omit the setting Select No Node, and click [OK] button.
To specify a node Select Specific Node from the list, and select
the node from the list or enter it directly in the
box. Then click [OK] button.
To refresh the list of nodes Click [Refresh] button. Push this button in case
the latest data is not displayed in Available
Node(s) list box.
To narrow down a list of
node names by their initial
alphabet
Select the initial alphabet from Index list box.
The narrowed down nodes starting with the
alphabet are displayed in Available Node(s) list
box.
Note: To display all nodes, select (All) in Index list box.
NEC PRACTICE
PRC-040-2510 12 of 12
NEC PRACTICE
PRC-040-2600-15 (E) Non-Adjacent Node Opens
PRC-040-2600 1 of 6
Non-Adjacent Node Opens
1. SUMMARY
When a signaling node opens in the network of Common Channel Signaling No.7 (CCS7), direct
connections and transmit messages are to be set directly to the signaling node. For an adjacent node, the
messages must be transmitted via signaling transfer points.
Note: The signaling nodes that have direct connections are called adjacent nodes, and those
without direct connection are called non-adjacent nodes.
When a non-adjacent node opens, set the following data:
Signaling route data:
Signaling routes are transmission paths which is set over signaling links for sending
messages to their destinations. When the destination is a non-adjacent node, transfer routes
via signaling transfer points is to be set.
This task provides step-by-step procedures for setting up connections with a non-adjacent node. If the
destination is an adjacent node, refer to PRC-040-2500 Adjacent Node Opens.
Fig. 1 Example of Connection to Non-Adjacent Node Setup
Node
NI=1
PC=00001
NI=2
PC=00002
LGN: Signaling Link Group
NI : Network Indicator
PC : Point Code
SLK: Signaling Link
STP: Signaling Transfer Point
SP : Signaling Point
uninstalled
tstopc0
tstopc1
Adjacent node(STP)
Adjacent node (STP)
adj0
NI=2,PC=10001
adj1
NI=2,PC=10002
dst1
NI=2,PC=10003
Non-adjacent
destination (SP)
Main route
(LGN:1,SLK:1,2)
Sub route
(LGN:2,SLK:3)
: Added Node
: Added Route
NEC PRACTICE
Non-Adjacent Node Opens PRC-040-2600-15 (E)
PRC-040-2600 2 of 6
2.1 Icon to Use
This task involves creation or modification of office data by using the following icon:
[CCS7 Routing] icon
which other data fields are to be defined, and are used as indexes of the office data. Table 1 shows
The procedure of setting up connections with a non-adjacent node consists of the following stages of
operation:
icon
Node Name is set for the destination. dst1
Network
Indicator/Point
Code
Code of the destination.
2/10003
Adjacent/Main/
Sub Link Group
Number
Defines signaling routes. To a non-
adjacent destination, routes are set
via signaling transfer points.
Adjacent: None
Main: 001
Sub: 002
NEC PRACTICE
PRC-040-2600 3 of 6
3.2 Operation Flow
Procedures for setting up connections with a non-adjacent node are explained below.
[CCC..]
[CCC..]
[CCC..]
Start
Stage 1
End
[CCS7 Routing]
Create destination nodes
Need a
speech path?
Yes
No
PRC-040-2100 Destination
Opens with Direct Routes or
PRC-040-2120 Destination
Opens without Direct Routes
Stage 2
[CCS7 Routing]
Unblock signaling routes
to the destination
NEC PRACTICE
PRC-040-2600 4 of 6
1 Create destination nodes.
Fig. 3 CCS7 Routing Window (Create)
Note: The destination node to be added must obtain the same network indicator as
own node.
2 Create signaling routes.
2-A Specify Main Link Group Number, Sub1/2/3 Link Group Number and Shift Bit
Pattern fields.
Notes:
1 When Partial Translation Routing Data is specified in Data Type field, Adjacent
Link Group Number field cannot be specified.
2 Point Code field must be set with Network Indicator field.
NEC PRACTICE
PRC-040-2600 5 of 6
2-B Click [Execute] button.
The created destination node name is displayed in list box.
2-C Click [Close] button to close the icon.
1 Unblock signaling routes to the destination.
1-B Select Unblock in Operation field.
Fig. 4 CCS7 Routing Window (Unblock)
1-E Specify Link Group Number field.
Note: If addition of a speech route to the destination node is required, follow the
NEC PRACTICE
PRC-040-2600 6 of 6
procedures of PRC-040-2100 Destination Opens with Direct Routes or PRC-
040-2120 Destination Opens without Direct Routes.
NEC PRACTICE
PRC-040-2610-15 (E) Non-Adjacent Node Closes
PRC-040-2610 1 of 6
Non-Adjacent Node Closes
1. SUMMARY
When a non-adjacent node is closed, the following data must be deleted:
Signalling route data: Destination node and related transfer routes
This task provides step-by-step procedures for deleting connections with a non-adjacent node. If the
destination is an adjacent node, refer to PRC-040-2510 Adjacent Node Closes.
Fig. 1 Connection to Non-Adjacent Node Deletion Example
Node
NI=1
PC=00001
NI=2
PC=00002
LGN: Signaling Link Group
NI : Network Indicator
PC : Point Code
SLK: Signalling Link
STP: Signalling Transfer Point
SP : Signalling Point
uninstalled
tstopc0
tstopc1
Adjacent node(STP)
Adjacent node (STP)
adj0
NI=2,PC=10001
adj1
NI=2,PC=10002
dst1
NI=2,PC=10003
Non-adjacent
destination (SP)
Main route
(LGN:1,SLK:1,2)
Sub route
(LGN:2,SLK:3)
: Deleted Route
: Deleted Node
: Deleted Link Group
NEC PRACTICE
Non-Adjacent Node Closes PRC-040-2610-15 (E)
PRC-040-2610 2 of 6
2.1 Icon to Use
This task involves deletion or modification of office data by using the following icon:
[CCS7 Routing] icon
The procedure of deleting connections with a non-adjacent node consists of the following stages of
operation:
Stage 1: Block Signalling Routes
Stage 2: Delete Destination Nodes and Signalling Routes
icon
Node Name set in this icon as
destination.
dst1
Network
Indicator/Point
Code
Point Code of the destination.
2/10003
Block/Unblock
All Check
Blocks or unblocks all signalling
routes to the destination.
Adjacent/Main/
Sub Link Group
Number
Defines signalling routes. To a non-
adjacent destination, routes are set
via signalling transfer points.
Adjacent: None
Main: 001
Sub: 002
NEC PRACTICE
PRC-040-2610 3 of 6
3.2 Operation Flow
Fig. 2 shows an example of the operation flow. The following conventions are used in the figure:
Procedures for deleting connections with a non-adjacent node are explained below.
If a speech path to the signalling node exists, delete the existing signalling node before deleting the
destination node and signalling routes. Refer to PRC-040-2110 Destination Closes with Direct
Routes or PRC-040-2130 Destination Closes without Direct Routes.
[CCC..]
[CCC..]
[CCC..]
Start
Stage 2
End
[CCS7 Routing]
Delete destination nodes
and signalling routes
path exits?
Yes
No
Delete the speech path, then start
this procedure again.
Refer to PRC-040-2110 Destination
Closes with Direct Routes or
PRC-040-2130 Destination Closes
without Direct Routes
A speech
[CCS7 Routing]
Block signalling routes to
the destination
Stage 1
NEC PRACTICE
PRC-040-2610 4 of 6
Stage 1: Block Signalling Routes
1 Block signaling routes to the destination.
1-B Select Block in Operation field.
Fig. 3 CCS7 Routing Window (Block)
field.
NEC PRACTICE
PRC-040-2610 5 of 6
Notes:
1 If the selected parameters should be changed after selecting data from the list box,
the parameters can be changed by specifying new parameters in appropriate fields.
2 When a signalling route to be blocked is specified with an undefined point code and
the route has been registered as a partial route, the signalling route can be blocked
by the specification of the undefined point code if the undefined point code is
subordinate to the partial route.
If the route to be blocked has been registered a default route, it can be blocked by
the specification of the undefined point code as well.
3 The data to be blocked can also be selected from the display area. The selected data
is set to respective data input fields. (This method is only available when the
display area contains data.)
Stage 2: Delete Destination Nodes and Signalling Routes
1 Delete destination nodes and signalling routes.
1-A Select Delete in Operation field.
NEC PRACTICE
PRC-040-2610 6 of 6
Fig. 4 CCS7 Routing Window (Delete)
1-B Specify Data Type field.
1-C Select other appropriate data input fields.
field.
The destination and signalling routes are deleted.
NEC PRACTICE
PRC-040-3200-27 (E) Add Trunks
PRC-040-3200 1 of 10
Add Trunks
1. SUMMARY
If a trunk is added to an office due to increase in traffic, the trunk needs to be registered in logical and
physical locations.
This task provides step-by-step procedures for addition of trunks.
Fig. 1 Example of Trunk Addition
2.1 Icon to Use
This task involves creation or modification of office data by using the following icon:
[Trunk] icon
which other data fields must be defined, and are used as indexes of the office data.
Table 1 shows fundamental data fields.
icon
Trunk (OGT).
ogttup
Office
TRK
TRK
TRK
: Added trunk
New trunk
ogtb0001
: Trunk
NEC PRACTICE
Add Trunks PRC-040-3200-27 (E)
PRC-040-3200 2 of 10
The procedure for addition of trunks consists of the following stages of operation:
Stage 3: Place Trunk In Service
3.2 Operation Flow
ogtb
Circuit Name [Trunk] icon Designates trunks for IC/OG routes. ogtb0001
[CCC..]
[CCC..]
[CCC..]
NEC PRACTICE
PRC-040-3200 3 of 10
Procedures for adding trunks are explained below.
Notes:
1 To create a new profile name, start with STEP 1 Create profile name.
2 To apply an existing profile name, start with STEP 2 Create route name.
[Trunk Test]
Check office data and retry
Stage 1
Stage 2
Stage 3
[Trunk]
Test new trunks
Place new trunks in
service
OK
is OK?
NG
Start
[Trunk]
Create trunks
Trunk result
[Route Profile]
[Route Data]
Create Profile
Name
Create Route Name
Create
Profile Name?
No
Yes
End
NEC PRACTICE
PRC-040-3200 4 of 10
1-C Specify Profile Name, Protocol Type, Trunk Type, Line Information and Satellite
Indicator fields.
Note: The fields to be specified vary depending on what is selected in any of the fields
above.
NEC PRACTICE
PRC-040-3200 5 of 10
-or-
NEC PRACTICE
PRC-040-3200 6 of 10
If the fields to be specified are not found in [Parameter 1] tag, click [Parameter 2] or
click [OK] button.
click [OK] button.
To specify a route
name
name list
the information.
To narrow down the
route name list by
the first letter of the
name
field.
NEC PRACTICE
PRC-040-3200 7 of 10
[Parameter 3] tag.
3 Create trunks.
3-C Specify Object Type and Equipment Trunk fields.
3-D Specify another data input field(s.)
field.
field.
When Circuit Number & Circuit Identification Code is selected in Object Type
field, specify Circuit Number and Circuit Identification Code fields.
NEC PRACTICE
PRC-040-3200 8 of 10
1 Test new trunks.
NEC PRACTICE
PRC-040-3200 9 of 10
1-C Specify the trunk to be tested and execute the test.
1-D Click [Close] button to close the [Trunk Test] icon.
Notes:
Translator.
2 If the test result is NG, check the office data and retry the operation.
Stage 3: Place Trunk in Service
1-B Select In Service in Operation field.
1-C Select an appropriate object type in Object Type field.
field.
Trunk field.
field.
NEC PRACTICE
PRC-040-3200 10 of 10
NEC PRACTICE
PRC-040-3210-23 (E) Delete Trunks
PRC-040-3210 1 of 6
Delete Trunks
1. SUMMARY
When traffic is redistributed over the network, existing trunks need to be deleted. Also, trunks in logical
and physical locations are to be deleted.
This task provides step-by-step procedures for deletion of trunks.
Fig. 1 Trunk Deletion Example
2.1 Icon to Use
This task involves deletion of office data by using the following icons:
[Trunk] icon
[Route Data] icon
Circuit Name [Trunk] icon Designates trunks for IC/OG routes. ogtb0001
ogtb
TRK
TRK
TRK
: Deleted trunk
Trunk to be deleted
ogtb0001 : Trunk
Office
NEC PRACTICE
Delete Trunks PRC-040-3210-23 (E)
PRC-040-3210 2 of 6
The procedure of deleting trunks consists of the following stages of operation:
Stage 1: Place Trunk Out of Service.
Stage 2: Delete Trunk Data.
3.2 Operation Flow
[CCC..]
[CCC..]
Stage 1
[Trunk]
Place trunks out
of service
Start
End
[Trunk]
Delete trunks
No
Yes
Delete Route
Name
Delete
Route Name?
Stage 2
[Route Data]
NEC PRACTICE
PRC-040-3210 3 of 6
Procedures for deletion of trunks are explained below.
1-B Select Out of Service in Operation field.
The screen changes to [Trunk] (Out of Service) window.
1-C Select an appropriate object type in Object Type field.
field.
Trunk field.
When Circuit Name is selected in Object Type field, specify Circuit Name field.
NEC PRACTICE
PRC-040-3210 4 of 6
1 Delete trunks.
The screen changes to [Trunk] (Delete) window.
Fig. 4 Trunk Window (Delete)
1-C Select an object type in Object Type field.
field.
Trunk field.
When Circuit Name is selected in Object Type field, specify Circuit Name field.
NEC PRACTICE
PRC-040-3210 5 of 6
Note: If it is unnecessary to delete the route name, omit this step.
-or-
NEC PRACTICE
PRC-040-3210 6 of 6
click [OK] button.
click [OK] button.
To specify a route
name
name list
the information.
To narrow down the
route name list by
the first letter of the
name
field.
CC-1
CUSTOMER COMMENT FORM
Your comments on our manual are welcome. They will aid us in our effort to improve the quality and
usefulness of our documentation. Use this form to report errors or to make suggestions on improving
the contents of our manual. Make your comments below and mail or fax this form to the NEC office
serving your switch, or to the address in Japan shown below.
Comments: ..............................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
Date: ......................................................................
Submitted by:
Name: ....................................................................Job/Title: .................................................................
Office: .....................................................................Company: ...............................................................
Address: .................................................................
State/County: .........................................................Country: ..................................................................
Telephone number: .................................................
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cut here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Doc. Title: Office Data Modification Manual
Doc. Number: ND-56981-327 (E) Issue: 2
In general, this documents is:
Usable and
Not usable
Usable but inadequate
Easy to understand
Difficult to understand
Reasons explained below
Use the address sheet shown on the left
when you mail directly to NEC.
As NEC is unable to supply the postage,
please make sure that your envelope has the
correct postage.
Attention: Manager (26-35400)
Technical Assistance and Service Center
NEC Corporation
1131 Hinode, Abiko, CHIBA 270-1198
JAPAN
FAX No. : 81-471-82-2125
2
1
(Continue overleaf)
NEC Control Number
CC-2
Comments (Cont.):..................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
Customer TASC Documentation
- - - - - - - - - - - - - - - - - - - - - - - - -Please do not write below this line.- - - - - - - - - - - - - - - - - - - -

ND 56981 327eee 02

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ND 56981 327eee 02

Încărcat de

Drepturi de autor:

Formate disponibile

ND-56981-327 (E)

Issue 2, December 1999

1999 by NEC Corporation

S-ar putea să vă placă și