Document for AXE-10

Configuration Procedures in AXE-10

INDEX

1.0 Introduction

0.0 Objective

CONFIGURATION MANAGEMENT

1.0 Procedure for RP Creation

2.0 Procedure for EM Creation

3.0 Procedure for SNT creation

4.0 Procedure for DIP Creation

5.0 Procedure for Route Creation

6.0 Procedure for Routing Case Creation and Modification

7.0 Procedure for Charging Analysis Creation

8.0 Procedure for B-Number Analysis

ADMINISTRATION MANAGEMENT

11.0 Procedure for Back-Up Management

12.0Procedure for Subscriber Management

13.0Terminal and password Management

PERFORMANCE MANAGEMENT

14.0 Procedure for Performance Management-Traffic Measurement

15.0Procedure for Performance Management-Service Quality Measurement

PREVENTIVE MAINTENANCE MANAGEMENT

16.0Preventive Maintenance Routines and other activities in switch.

FAULT MANAGEMENT

17.0Procedure for Alarm Management

18.0Process for System Restart & Reload

PRODUCT MANAGEMENT

19.0Carrier Access Code

20.0 Centrex

21.0 POTs

22.0 Internet dialup

INTRODUCTION

Reliance Communications Limited is deploying 17 Ericsson AXE-10 switches in year one which will be installed in seventeen different locations for providing Wireline, NLD and ILD services. These switches will be managed from two centralized locations with the help of element management system XMATE (EMS) supplied by Ericsson. This Element Management System (EMS will installed in NOC .All 17 switches will be controlled by the NOC.

A NOC provides centralized functions in the Reliance Network.

The major functional groups in NOC are as follows:

Switch Control Management

Switch configuration & modification Management

Transport Control Management

Radio Network Management

Data Network & Adjunct systems Management

System Administration and Cross functional management

Resources Management

OSP & ISP facilities management.

OBJECTIVE

This document has been primarily intended to guide the NOC Engineer in day-to-day Operation & Maintenance activity. The goal of this manual is to describe all the activities carried out in NOC.

The procedure for all the activities are explained and the command descriptions, which is considered to be of special interest for NOC activity has been added. This document is an extract for only technical activities.

CONFIGURATION MANAGEMENT

Sub-Process Name :

A. Procedure for RP Creation

B. Procedure for EM Creation

C. Procedure for SNT Creation

D. Procedure for DIP Creation

E. Procedure for New Route Creation

F. Procedure for Routing Case and Modification

G. Procedure for Charging Analysis Creation

H. Procedure for B-Number Analysis

A. STANDARD OPERATING PROCEDURE FOR RP CREATION

A.1. SCOPE

This document explains the procedure to create Regional Processor (RP).

A.2. DESCRIPTION

A.2.1. Check if the HW is available in the switch and necessary cabling is done.

A.2.2. Check if provision exists in Database table specification.

Refer A.4.1.

A.2.3. Check the work order for the number of RPs to be defined

and its application.

A.2.4. Check the status of RPs.

Refer A.4.2.

A.2.5. Define the RP type

Refer A.4.3.

A.2.6. RP software definition.

Refer A.4.4.

A.2.7. De-block the RP and check the status.

Refer A.4.5.

A.3. REQUIREMENTS

A.3.1. Approved Work Order

A.3.2. Reference Manual

A.4. PROCEDURES

A.4.1. CHECK IF PROVISION EXISTS IN DATABASE TABLE SPECIFICATION.

DBTSP:TAB=table name;

Database, Table Specification, PrintThis command prints a table or a specified part of a table. Normally during commisioning of the switch, all the table will be created.

Parameter Description


TAB

Table Name (e.g. RPSRPBSPOS for RPs)

Note: DBTSI is used for defining the table. Refer ALEX for more details. To check the RP database, the RP Table RPSRPBSPOS is used in the command.

A.4.2. CHECK THE STATUS OF RPs.

EXRPP: RP = ALL;

RP status Print

Orders a printout of data and states for an RP and its twin.

A.4.3. DEFINE THE RP TYPE

EXRPI: RP=rp number [,RPT=rp twin number],TYPE=rp type;

EXRPI

Exchange data function, rp initiateInitiates Regional Processor (RP) equipment for the specified RP-address (or addresses) and for the specified type of RP.


RP Number

Regional processor address

RP Twin number

RP twin address

RP Type

Different types of RPs are available for various

applications.

e.g. RPM6A, RPG2A etc.,

Refer ALEX for more information.

A.4.4. RP SOFTWARE DEFINITION

EXRUI: RP=rp number, [RPT=rp twin number], SUID=software unit identity;

EXRUI

Exchange Data, RP Software Unit, InitiateParameter Description

RP Number

Regional processor address

RP Twin number

RP twin address

Software Unit IdentitySoftware Unit (SU) identity If the identifier contains any character, other than letters or digits then the string must be given within quotation marks.

EXRUP: RP=rp number;

RP Software Unit Data Print

Orders a printout of data for programs, Extension Modules (EMs), and Control Modules (CMs), associated with a specified loadable RP.

A.4.5. DEBLOCK RP AND CHECK THE STATUS

Note: In case of RPG2A, refer to the definition of EM SOP/NOC-B/R1. EM must be deblocked first.

BLRPE: RP=rp number;

De-blocking of RPs

This command is used when de-blocking a Regional Processor (RP). The maximum number of RPs that can be specified in the command is eight.

EXRPP: RP=rp number;

RP status PrintNote : For Fault codes and Size alteration Events refer ALEX

A.5. CONCLUSION

After completion of above process, proceed to the next step in the work order. If there are no more steps, close the work order and forward it to the concerned department.

B. STANDARD OPERATING PROCEDURE FOR EM CREATION

B.1. SCOPE

This document explains the procedure to create EXTENSION MODULE (EM) to the existing Regional Processor.

B.2. DESCRIPTION

B.2.1. Check if the hardware is available in the switch and necessary cabling is done.

B.2.2. Check the RP status.

Refer B.4.1.

B.2.3. Check the status of EMs.

Refer B.4.2.

B.2.4. Define the new EM.

Refer B.4.3.

B.2.5. De-block the EM.

Refer B.4.4.

B.2.6. Check the Status of the EM.

Refer B.4.5.B.3. REQUIREMENTSB.3.1. Approved Work Order

B.3.2. Reference Manual

B.4. PROCEDURES

B.4.1. CHECK THE RP STATUS

EXRPP:RP=ALL;

RP status print

EXRUP:RP=ALL;

RP Software Unit Data print

Note: The RPs should be loaded with the relevant software unit data

B.4.2. CHECK THE STATUS OF EMs.

EXEMP: EM = all, RP=rp;EM status print

Orders the printout of state as well as associated devices and program pages for one or several EMs.


RP

RP address

EM

EM address

B.4.3. DEFINE THE EM

EXEMI: EQM=eqm,EM= em,RP=rp [,RPT=rpt][,SUID=suid];

EXEMI

Exchange Data Function, EM Initiate This command is used for defining an EM and for linking equipment to a software unit. The command may be given to both blocked and deblocked non-loadable RPs with program pages.

In the case of an EM which is controlled by an RP pair, both RP addresses must be specified. The RP which is specified in the parameter RP is set as the home address for the EM 'PRIM'. The RP twin is set as the standby address for the EM "SEC".

If the RP does not have the property "Load sharing allowed" then the EMs must always be controlled from the same RP.

Note: . RP address will vary. All the related details will be given with the work order.

For Fault Codes and Command parameter details refer ALEX document. The parameters put in brackets may be optional.Parameter DescriptionEQMEquipment for EM tied to specified unit. EQM consists of a string specifying the block that owns the equipment and a suite for which equipment is to be connected to the specified RP(s) and EM.

EM

EM address

RP

RP address

RPT

RP twin address

SUID Software unit product identityIf other than letter or digit, the string must be given within quotation marks.

B.4.4. DE-BLOCK THE EM.

Note : The EMS should be first de-blocked in case of RPG2A.

BLEME:RP=rp[,RPT=rpt], EM=em;

BLEME

De-blocking of EM


RP

Regional Processor Address

RPT

Regional Processor Twin Address

EM

Extension Module Address

B.4.5. CHECK THE STATUS OF THE EM

EXEMP:EM=all, RP=rp;EM status print

Orders the printout of state as well as associated devices and program pages for one or several EMs.

The EM status should be in working state. If not check the RP status and refer ALEX for the fault codes.

B.5. CONCLUSION

After completion of above process, close the work order and forward it to concerned department.

C. STANDARD OPERATING PROCEDURE FOR SNT CREATION

C.1. SCOPE

This document explains the procedure to create the SWITCHING NETWORK TERMINAL (SNT).

C.2. DESCRIPTION

C.2.1 Check if the HW is available in the switch and necessary cabling is done.

C.2.2 Check the status of RP and EM

Refer C.4.1.

C.2.3 Check the status of SNTs.

Refer C.4.2.C.2.4. Define the SNT.

Refer C.4.3.

C.2.5. Test the SNT.

Refer C.4.4.

C.2.6. De-block the SNT.

Refer C.4.5.

C.2.7. Connection of devices to the SNT.

Refer C.4.6.

C.2.8. Check the status of the SNT.

Refer C.4.7.

C.3. REQUIREMENTS

3.1. Approved Work Order

3.2. Reference Manual

C.4. PROCEDURES

C.4.1. CHECK THE STATUS OF RP AND EMEXRPP:RP=all;

RP status print

EXEMP:EM=all,RP=all;EM status print

C.4.2. CHECK THE STATUS OF SNTs.

NTCOP:SNT= ALL;

Switching Network Terminal connection data print

This command prints the connection data of the SNTs i.e. details on SNTP (Signalling network terminal point), DIP (Digital Point), TSM position etc.

C.4.3. DEFINE THE SNT

NTCOI:SNT=snt,SNTV=sntv,SNTP=sntp;

NTCOI

Switching Network Terminal connection data, Initiate

This command connects an SNT to the Group Switch (GS) or the Subscriber Switch (SS). For SNTs with SUBSNTs one SNT can be connected in one command issue. For SNT any other type the maximum of 32 SNTs can be connected. For a SNT with several hardware connections to the group switch, the connection is Make in consecutive order according to the designations of these connections.


SNT

Switching network terminal

Expressed as snt-n where:

snt Switching network terminal type Identifier. 1~13 characters

n Switching network terminal number. Numeral 0 ~ 65535

SNTV

Switching network terminal variant

SNTP

Switching network terminal connection point

Note : SNT address ,variant and connection Points will vary. All the related details will be given with the work order. For Fault Codes, Size Alteration Events and Command parameter details refer ALEX document.

C.4.4. TEST THE SNT

NTTEI: SNT=snt;

Switching network terminal, Test Initiate

This command initiates testing of a manually blocked SNT or a subordinate SNT. When an SNT with subordinate SNTs is specified in the command, only the specified subordinate SNTs are tested. Otherwise, the complete SNT is tested.

C.4.5. DEBLOCK THE SNT

NTBLE: SNT=snt;

Switching network terminal, DeblockThis command deblocks an SNT or a subordinate SNT. When an SNT with subordinate SNTs is specified in the command, only the specified subordinate SNTs are deblocked. Otherwise, the complete SNT is deblocked.

A maximum of 128 SNT or 7 subordinate SNT individuals can be specified in one command issue.

C.4.6. CONNECT THE DEVICES TO THE SNT

EXDUI:DEV=device, DEVP=device position; Connection of Devices to a SNT, InitiateThis command connects devices to a switching network terminal unit.

The parameter DEVP is only used for devices that do not have an SNT associated with them. Therefore, the device positions within the SNT are not pre-determined, and must be specified in the command.

C.4.7. CHECK THE STATUS

NTSTP:SNT=snt;

Switching network terminal, status print.

Note : The Signalling Network Terminal should be in working state. If not, Check the status of the RP, EM and the physical cabling in the Group switch. Action to be taken as per the fault code. For details on fault code and Size Alteration Event refer ALEX. C.5. CONCLUSION


D. STANDARD OPERATING PROCEDURE FOR DIP CREATION

D.1. SCOPE

This document explains the procedure to create the Digital Path (Digital Path).

D.2. DESCRIPTION:

D.2.1. Check if necessary cabling is done between the ETC card DDF Transport DDF.

D.2.2. Check the through connection between the exchanges.

D.2.3. Check the work order for the number of DIPs to be

defined, DIP name and number

D.2.4. Check the status of RPs, EMs and SNT

Refer D.4.1.

D.2.5. Check the status of DIP

Refer D.4.2.

D.2.6. Define the DIP.

Refer D.4.3.

D.2.7. Define the initial data for digital path

Refer D.4.4.

D.2.8. De-block the DIP

Refer D.4.5.

D.2.9. Check the DIP status.

Refer D.4.6.

D.3. REQUIREMENTS

D.3.1. Approved Work Order

D.3.2. Reference Manual

D.4. PROCEDURES

D.4.1. CHECK THE STATUS OF RPS, EMs AND SNTEXRPP: RP = ALL;

RP status Print

EXEMP:EM = ALL, RP=ALL;EM status Print

NTCOP: SNT= ALL;

SNT status Print

D.4.2. CHECK THE STATUS OF DIP

DTSTP : DIP = dip name;

DTSTP

Digital Path Transmission Functions, State, Print

This command initiates a printout of the state for the specified DIP. Up to 16 DIPs can be specified in each command. If STATE is specified in the command, only the DIPs with the indicated state are printed.


DIP

Digital Path name

D.4.3. DEFINE THE DIP

DTDII:DIP=dip name, SNT=snt;

DTDII

Digital Path Transmission Functions, Digital Path, Initiate

This command specifies the name of the DIP and connects the DIP to an SNT, a port on a network node, a sequence of RSM devices, or a TRI device.

Up to 32 devices can be specified in the command.

When the SNT can have more than one DIP connected, the DIP connection point must be specified.


DIP

Digital Path name. Identifier 1- 7 characters.

SNT

Switching Network Terminal

Expressed as snt-n where:

snt - SNT type and n- SNT number.

Note: The DIP can be defined with various parameters. For more information refer ALEX.

D.4.4. DEFINE THE INITIAL DATA FOR DIGITAL PATH

DTIDC:DIP=dip name,INACT=inact,CRC=crc,MODE=mode,MULTIFS=multfs;

This command specifies the initial data for digital paths.


DIP

Digital Path name. Identifier 1- 7 characters.

INACT

Inhibited actions

at excessive error rate or consecutive severely errored seconds. Numeral 0 ~ 1

0 No inhibition (AIS/ALL1 will be sent towards GS)

1 Inhibition of AIS/ALL1 towards GS (The incoming bitstream will be sent towards GS)

CRC

Cyclic Redundancy Check (CRC)

(Only used with 32 channel ETC or ETB without Echo Canceller (EC).) CRC is only available for certain ETC and ETB hardware.(See each value of the CRC parameter.). Numeral 0 ~ 3

MODE

Specifies in which mode the ETC is working. Numeral 0-1.

0 - For 32 ch.: Timeslot 16 connected towards GS.

For 24 ch.: Timeslot 9 connected towards GS.

1- For 32 ch.: Timeslot 16 as a single 64 kbit/s channel that can be extracted from ETC. (For example towards a Signalling Terminal Circuit (STC).)

For 24 ch.: Timeslot 9 as a single 64 kbit/s channel that can

be extracted from ETC. (For example towards a STC.)

Note : To be used only used for CCS, when timeslot 16 for 32 channel PCM or timeslot 9 for 24 channel PCM is used as a 64 kbit/s connection.

MULTIFS

Multiframe structure

00 No multiframe structure

01 Multiframe structure (The ETC will work as it does for CAS.)

11 Multiframe structure and circuit supervision (satellite connections)

Note : Refer ALEX for more details of the parameters.

D.4.5. DEBLOCK THE DIP

DTBLE : DIP = dip name;De-blocking of the DIP

This command deblocks the specified DIPs.

D.4.6. CHECK THE DIP STATUS.

DTSTP:DIP=dip name;Digital Path Transmission Functions, State, Print

Note : The DIP should be in working state. If not check the status of RP, EM , SNT and the physical connection between the exchanges, in DDF and in Transport DDF. For Fault codes and Size alteration Events refer ALEX.

D.5. CONCLUSION


E. STANDARD OPERATING PROCEDURE FOR ROUTE CREATION

E.1. SCOPE

This document explains the procedure to create a new route. The route is defined in the Routing case analysis.

E.2. DESCRIPTION

E.2.1. Check the work order for the route details.

E.2.2. Define RP

Refer A.

E.2.3. Define EM

Refer B.E.2.4. Define SNT

Refer C.

E.2.5. Check the status of RP, EM, SNT and DIP.

Refer E.4.1.

C7 Signaling and Traffic route definition.

E.2.6. Define the Signalling Terminal.

Refer E.4.2.

E.2.7. Define the Signalling Point (SP).

Refer E.4.3.

E.2.8. Define the Link Set.

Refer E.4.4.

E.2.9. Initiate the Link Set.

Refer E.4.5.

E.2.10. Initiate the routing specifications.

Refer E.4.6.

E.2.11. Define the Signalling Routes.

Refer E.4.7.

E.2.12. Define the Traffic Routes.

Refer E.4.8.

E.2.13. Connect the devices to the Signaling route.

Refer E.4.9.

E.2.14. Connect the devices to the Traffic route.

Refer E.4.10.

E.2.15. Put the devices in to service.

Refer E.4.11.

E.2.16. Define the Semi-Permanent connection.

Refer E.4.12.

E.2.17. De-block the Traffic devices

Refer E.4.13.

E.2.18. De-block the Signalling and Traffic routes.

Refer E.4.14.

E.2.19. Activate the Signalling Link and routes..

Refer E.4.15.

R2MFC route definition.

E.2.20. Create the R2MFC outgoing route.

Refer E.4.16.

E.2.21. Connect the devices to the Traffic route.

Refer E.4.17.

E.2.22. Put the devices in to service.

Refer E.4.18.

E.2.23. De-block the outgoing route and devices.

Refer E.4.19.

E.2.24. Create R2MFC incoming route.

Refer E.4.20.

E.2.25. Connect the devices to the route.

Refer E.4.21.

E.2.26. Put the devices in to the service.

Refer E.4.22.

E.2.27. De-block the devices.

Refer E.4.23.

Analysis table creation

E.2.28. Create the Routing case. Refer.

Refer SOP/NOC-F/R1

E.2.29. Create the Charging case. Refer

Refer SOP/NOC-G/R1

E.2.30. Create the B-Number analysis.

Refer SOP/NOC-H/R1

E.2.31. Test the routes.

Refer E.4.24

E.3. REQUIREMENTS

E.3.1. Approved Work Order

E.3.2. Information of the far-end exchange

E.3.3. Interconnectivity

E.3.4. ALEX and standard operating procedure

E.4. PROCEDURES

Note : For the fault codes, size alteration events and more information on commands and parameters, refer ALEX.

The parameters (Route name, DIP name and devices name) will vary. All the related details will be given with the work order.

E.4.1. CHECK THE STATUS OF RP,EM, SNT & DIP.

EXRPP : RP = ALL:

RP status print

EXEMP:EM=ALL, RP=rp number;

EM status print

NTCOP:SNT=ALL;

SNT status print

DTSTP:DIP=ALL:

DIP status print

STDEP:DEV=UPDN3-1&&-31;

Device status print

Note : The status of the RP, EM. SNT and DIP should be in WO state

The device should be in MBL and NC state.

E.4.2. DEFINE THE SIGNALLING TERMINAL

C7STI:ST=st, ITYPE=itype;

CCITT7 Signalling Terminal, InitiateThis command defines a signalling terminal and its interface type to the signalling data link.

Parameter DescriptionST

Signalling Terminal (ST)

Expressed as string-num where:

string Block designation

num Individual in the block

ITYPE

Interface type

This parameter specifies the interface type between the signalling terminal and the signalling data link.

Note : Refer the block C7ST2 in ALEX for more details. Normally ITYPE=14 is given in the command. This ITYPE corresponds to a particular bit rate on the SDL, and indicates whether bit inversion is required and if the bit rate is to be high or low.

E.4.3. DEFINE THE SIGNALLING POINT

C7SPI : SP=sp code [,OWNSP=ownsp];

C7PNC:SP=sp code, SPID=spid;

This Command is used to define one or more Signalling Points in their corresponding networks.

The OWNSP parameter is used when one or more own signalling points have been defined for the same network. In this case the new signalling point or points are

connected to the OWNSP specified.

The specified own signalling point will be used as originating point code (OPC) when labelling messages to be sent to signalling points connected to it.

E.4.4. DEFINE THE LINK SET

C7LDI:LS=ls;

C7 link set data initiate

The command defines one or more Link Sets in an CCITT7 signalling network.

E.4.5. INITIATE THE LINK SET

C7SLI:LS=ls,SLC=slc,ST=st,SDL=sdl;C7 signalling link initiate

The command defines a Signalling Link in a CCITT7 signalling network


ST

Signalling Terminal (ST)

Expressed as string-num where:

string Block designation

num Individual in the block

SDL Identification string of the Signalling Data Link with a maximum length of 31 characters

LSLink Set.

Expressed as ls=ni-spc

ni Network Indicator.

spc Signalling Point Code.

SLC

Signalling Link Code within a link set.

E.4.6. INITIATE THE ROUTING SPECIFICATION

C7RSI:LS=ls,DEST=dest,PRIO=prio;C7 routing specification, Initiate

The command C7RSI is used to introduce a signalling route into the routing data. For each route a link set is assigned to a destination and given a priority, priorities 1 and 14 being the highest and lowest respectively.

Priorities 9 down to 14 are used for restricted routes. Any destination may possess up to eight alternative signalling routes. Signalling traffic is sent via the highest priority route that is available.


LSLink Set.

Expressed as ls=ni-spc

ni Network Indicator.


DEST

Destination point.

Expressed as ni-spc

ni Network Indicator

spc Signalling Point Code

PRIO

Priority of Signalling Route.

E.4.7. DEFINE THE SIGNALLING ROUTES

EXROI:R=route name,FNC=fnc,DETY=dety; Route data, Initiate

Command EXROI is used to initiate and define data for a Signalling route or routes.


DETY

Symbolic device type designation

R

Route designation

both incoming & outgoing

FNC

Function code

E.4.8. DEFINE THE TRAFFIC ROUTES FOR SS7

EXROI:R=route name,FNC=fnc,DETY=dety,SI=si,SP=sp;

EXROI

Route data, Initiate

Command EXROI is used to initiate and define data for a Traffic route or routes.


DETY


R

Route designation


FNC

Function code

SI

Service Indicator

SP

Signalling pointEXRBC:R=route name;[BO=bo,CO=co](If the calls from this route have to be analysed differently)

EXRBC

Specification of Route change

This command changes or specifies route data. The data can be changed regardless of the route state. Only the parameters for which a new value is required need to be specified.


R

Route designation

BO

Origin of B-number analysis

CO

Origin of analysis of charging

E.4.9. CONNECT THE DEVICES FOR SIGNALLING ROUTE

EXDRI:DEV=dev,R=sig route name;Connection of devices to Route, Initiate

This command connects devices to a Signalling route.

Note : This command has lot of parameters. For further details refer ALEX.

E.4.10. CONNECT THE DEVICES TO TRAFFIC ROUTE

EXDRI:DEV= device range,MISC1=misc,R=route name;

This command connects devices to a Traffic route.

MISC1

Miscellaneous information

MISC1 is equal to CIC number

DEV

Device

Expressed as dety-n

Dety - Device type

N Device number

R

Traffic Route designation


E.4.11. PUT THE DEVICES IN TO THE SERVICE

EXDAI:DEV=device;

Prepost service device, activation, Initiate

Command EXDAI brings a device into service from a PRE-POST SERVICE state.

E.4.12. DEFINE THE SEMIPERMANENT CONNECTION

EXSPI:NAME=name;

Semi-permanent connection procedure, Initiate

The command EXSPI initiates the command procedure for reservation of a semipermanent connection. The command is not accepted if the command procedure is already in progress

EXSSI:DEV1=Trunk dev;Semi-permanent connection specification, Initiate

EXSSI:DEV2=C7ST dev;

This command defines all data concerning one side of the semi-permanent connection. It can only be given if a command procedure for reservation of a semi-permanent connection is in progress.

EXSPE [:del];

Semi-permanent connection procedure, End

This command ends the reservation of a semi-permanent connection procedure. The command can only be given if a command procedure for reservation of a semi-permanent connection is in progress.

EXSCI:NAME=name,DEV=trunk dev; Semi-permanent connection, Initiate

This command activates a semipermanent connection that has previously been reserved.


NAME

Semipermanent connection name

DEV1

Device 1 (incoming side) for the semipermanent connection

DEV2Device 2 (outgoing side) for the semipermanent connection

DEL

Delete all data defined with the command procedure.

E.4.13. DEBLOCK THE TRAFFIC DEVICES.

BLODE:DEV=device;

Deblocking of devices.

E.4.14. DEBLOCK THE SIGNALLING AND TRAFFIC ROUTES

BLORE:R=route name;

Deblocking of Traffic or Signalling route.

E. 4.15. ACTIVATE THE SIGNALLING LINK AND ROUTES

C7LAI:LS=ls,SLC=slc;

C7 signalling link activation, initiate

The command orders the activation of a signalling link in a specified link set.

C7RAI:DEST=dest;

C7 signalling routing activation, initiate

The command is used to activate the routing of signalling traffic to a destination. If the LS parameter is included the corresponding route is activated. If the LS parameter is omitted all inactivated routes to the destination will be activated.

LS

Link Set.

Expressed as ls=ni-spc where:



SLC

Signalling Link Code within a link set.

DEST

Destination point

Expressed as dest=ni-spc where:


spc Signalling Point Code

E.4.16. CREATE THE R2MFC OUTGOING ROUTE

EXROI:R=route name, FNC=fnc, DETY=dety;

EXRBC:R=R2MFC route name, R1=co-operative route;

EXROI

Route data, Initiate

Command EXROI is used to initiate and define data for a Traffic route or routes.

EXRBC

Specification of Route change

This command changes or specifies route data. The data can be changed regardless of the route state. Only the parameters for which a new value is required need to be specified.


DETY


R

Route designation

FNC

Function code

R1

co-operative route (CSR route)E.4.17. CONNECT DEVICES TO THE TRAFFIC ROUTE

EXDRI:DEV=device or device range,R=R2MFC route name;

Note : Refer E.4.10 for command and Parameter Description.

E.4.18. PUT DEVICES IN TO SERVICE

EXDAI:DEV= device or device range;


E.4.19. DEBLOCK THE OUTGOING DEVICES AND ROUTE

BLODE:DEV= device or device range;

BLORE:R=R2MFC route name;

Note : Refer E.4.13 and E.4.14 for command and Parameter Description.

E.4.20. CREATE THE R2MFC INCOMING ROUTE

EXROI:R= route name,DETY=device type, FNC=fnc;

EXRBC:R= route name, R1=co-operative route;

EXRBC:R= route name, LSV=lsv;

EXRBC:R= route name, BO=b-origin;


E.4.21. CONNECT THE DEVICES TO ROUTE

EXDRI:DEV= device or device range,R=R2MFC route name;


E.4.22. PUT THE DEVICES IN TO SERVICE

EXDAI:DEV= device or device range;


E.4.23. DEBLOCK THE ROUTE AND DEVICES.

BLORE:R=R2MFC route name;

BLODE: DEV= device or device range;

Note : Refer E.4.13 and E.4.14 for command and Parameter Description.

E.4.24. TESTING :

Check the status of the devices

All the devices should be in IDLE state.

Create the routing case and insert it in to the B-number Table.

Make a call to the destination where the new route is defined and check the following

Status of the device (BUSY state)

Speech quality and Charging

E.5. CONCLUSION


F. STANDARD OPERATING PROCEDURE FOR ROUTING CASE CREATION AND MODIFICATION.

F.1. SCOPE

This document explains the procedure to create and modify the routing case. This analysis is used in B-Number analysis table.

F.2. DESCRIPTION:

Create the new Routing Case

F.2.1. Check the work order for Routing case details.

F.2.2. Check the status of the Route and the devices

Refer F.4.1

F.2.3. Check the status of all the Routing case

defined in the system.

Refer F.4.2

F.2.4. Define the Routing case in the Non-Operated Area

with different routing programs.

Refer F.4.3

F.2.5. Swap the Routing case data from Non-Operated area

to Operated area. Refer 4.4

Refer F.4.4.

F.2.6 Testing

Refer F.4.9

Modification of the existing routing Case

F.2.7. Check the Routing case data.

Refer F.4.5

F.2.8. Clear (Zeroing) the Non-Operating data.

Refer F.4.6

F.2.9. Define the Routing case in the Non-Operated

Area with the modifications.

Refer F.4.7

F.2.10. Swap the data between non-operating area to

operating area.

Refer F.4.8

F.2.11. Testing

F.3. REQUIREMENTS

F.3.1. Approved Work Order

F.3.2. Information of the Route and the Routing case number.

F.3.3. ALEX and standard operating procedure

F.4. PROCEDURES


F.4.1. CHECK THE STATUS OF ROUTE AND DEVICES.

STRSP:R= route name;

Route status printThe command orders a survey printout for telephony devices in routes. The following information is provided for each route: the number of devices, the number of occupied devices, the number of idle devices, the number of blocked devices, and the route status.

STDEP:DEV=device name;

Device status print The command prints the states for telephony devices. The printout details the current state of each device, or all devices in a device type that are specified in the command.

Information is provided for a device on fault-marked, and fault-suspected subscriber lines, line circuits, and telephony devices. These telephony devices can be fault-marked, or fault-suspected, by the disturbance supervision, quality supervision, or subscriber line test functions.

F.4.2. CHECK THE STATUS OF ALL THE ROUTING CASE DEFINED

IN THE SYSTEM

ANRSP:RC=routing case;Routing Case specification printThis command prints routing case data in the operating of the specified routing cases.

Note :From this command find if the new routing case to be defined is free.F.4.3. DEFINE THE ROUTING CASE IN THE NON-OPERATED AREA WITH

DIFFERENT ROUTING PROGRAMS.

ANRPI:RC=routing case,CCH=cch;

ANRSI:R=route,P01=p01, ,SP=sending program;

ANRSI:R=route,P01=p01, SP=sending program;

ANRPE;

ANRPIThis command initiates a procedure to specify a routing case if specification requires the use of several ANRSI commands.

ANRSIThis command indicates an entire routing case. When specifying an entire routing case, parameter RC is always included in the command

This command initiates specification of a part of a routing case within a specification procedure. This means that the command must have been preceded by an ANRPI and ended with an ANRPE command.

ANRPE This command ends the specification of a routing case, initiated by command ANRPI.

Parameter DescriptionRC

Routing Case

R

SS7 Route

CCH

Compatibility Check

SP

Sending Program

SP = X Y Z means

X An outgoing device in the route is seized after reception of the Xth digit.

Y Seizure Signal is sent after the reception of the Yth digit. Z The first digit to be transmitted is the Zth digit.

P01Alternative number dealing with the first routing programThe character "P" in the parameter name indicates that this alternative belongs to routing program using automatic alternative routing. The number "01" in the parameter indicates the first routing program. The alternatives in routing program must be consecutive. All next possible alternatives in this routing program must use this hunting method.

Note: Routing case can be defined with different configurations. Refer ALEX for other configurations. Care should be taken when creating or modifying the data in Non-operating area. The copying, editing and activating the data between NOP and OP should be done carefully. A copy of the previous RC data should be Make before modifying the table.

F.4.4. SWAP(ACTIVATE) THE ROUTING CASE DATA FROM NON-OPERATED

AREA TO OPERATED AREA.

ANRAI:RC=1; Routing case Activation, Initiate

This command activates the specified routing case by swapping the operating and non-operating areas.

A 24-hour protection period prevents changes to the former operating area (now stored in the non-operating area).

The first time a routing case is activated, no protection period is started because no former operating area data exists.

Modification of the existing routing Case

F.4.5. CHECK THE ROUTING CASE.

ANRSP:RC=ALL;

Routing case Specification data, Print

F.4.6. CLEAR (ZEROING) THE NON-OPERATING DATA. ANRZI:RC=rc;

Zeroing the Non-Operated area.

This command zeroes data in the non-operating area for the specified routing cases.

This command is not allowed when the non-operating area is being printed

Note: The RC number is the number of the routing case that needs to be modified.F. 4.7. DEFINE THE ROUTING CASE IN THE NON-OPERATED AREA

WITH THE MODIFICATIONS.

ANRSI:RC=rc,R=route,CCH=cch,SP=sp;

Note : Refer F.4.3 for the command explanationF. 4.8. SWAP(ACTIVATE) THE MODIFIED ROUTING CASE BETWEEN

NON- OPERATING AREA TO OPERATING area.ANRAI:RC=rc;

Routing case Activation, Initiate

Note : Refer F.4.4 for the command explanationF.4.9. TESTING :

Insert the RC in B-number analysis Table Make calls to the destination and verify the definition. If the old routing case is needs to be reverted back then the command ANRAR is used.

ANRAR:RC=rc;

Routing case Activation, Reset

This command resets activated routing case before the protection period expires by swapping the operating and non-operating areas.

F.5. CONCLUSION


G. STANDARD OPERATING PROCEDURE FOR CHARGING ANALYSIS CREATION

G.1. SCOPE

This document explains the procedures for charging analysis.This charging analysis is Make by means of several tables such as Charging Case ,Charging Program,Tariff Class,Switching Class & Tariff Data.Charging Case(CC) is referred in the B-no. analysis table.

G.2. DESCRIPTION

G.2.1. Check the work order for Charging case details .

G.2.2. Print the Tariff data.

Refer G.4.1

G.2.3. Print the Switching class data

Refer G.4.2.

G.2.4. Print the Traffic class data

Refer G.4.3.

G.2.5. Print the Charging program.

Refer G.4.4.

G.2.6. Print the Charging Case

Refer G.4.5.

G.2.7. Define new tariff data

Refer G.4.6.

G.2.8. Define the Switching class data

Refer G.4.7.

G.2.9. Define the Traffic class data

Refer G.4.8.

G.2.10.Define the Charging program.

Refer G.4.9.

G.2.11.Define the Charging Case

Refer G.4.10.

G.2.12.Testing

Refer G.4.11.

G.3. REQUIREMENTS

3.1. Approved Work Order

3.2. Information about all charging data.

3.3. Alex processes & standard operating procedures

G.4. PROCEDURES


G.4.1. PRINT THE TARIFF DATA.CHTSP:T=ALL:

Charging Administration of Tariff Specification, PrintThis command generates a printout of tariff data in the in the operating area.


T

Tariff Data

G.4.2. PRINT THE SWITCHING CLASS DATA

CHSSP: SWC=ALL

Switching Class specification, print

This command prints the switching class data in the operating area.


SWC

Facilitate the time differentiated tariff implementation

G.4.3. PRINT THE TRAFFIC CLASS

CHCSP: TC = ALL;

Tariff Class Specification, PrintThis command prints tariff class data in the operating area .


TC

Indicates identity of tariff class

G.4.4. PRINT THE CHARGING PROGRAM.

CIPSP:CHP=ALL;

Charging Program Data Print

This command initiates a printout of charging program data for the operating area.Parameter Description

CHPA charging program defines the charging actions to be performed, how they are to be performed, and where in the network they are to be performed.

G.4.5. PRINT THE CHARGING CASE

CIBSP:CC=ALL;

Charging Case Data Print

This command initiates a printout of charging case data of the operating area.

The command is not allowed while a charging case is being defined.


CCIdentity of Charging Case. CC leads to Charging program. CC is referred in the B-number analysis

G.4.6. DEFINE NEW TARIFF DATA

CHTSI: T=tariff data, NSP=no.of start pulses, TDS=time duration in second, NPP=no. of periodic pulses;

CHTSI

Charging Administration of Tariff Specification, InitiateThis command specifies or changes the data in the non-operating area for a tariff.

This format is used when Ericsson charge unit based tariffs for one period must be specified.


T

Tariff data identity

NSP

Indicates no. charge pulses when the charging is initiated ,

e.g. on the receipt of the B-answer.

TDSIndicates the time in seconds, or parts of the second between the pulses.

NPP

Indicates Periodic burst of charge units

CHTSP:T=ALL,NOP:Charging Administration of Tariff Specification, PrintThis command generates a printout of tariff data in the in the non-operating area.

CHRAI: T=Tarrif Data;Charging Administration of Tariff Activation, InitiateThis command activates a change of a tariff or puts a tariff that was previously not in operation into operation.

G.4.7. DEFINE THE SWITCHING CLASS DATA

CHSSP: SWC= Switching Class; Switching Class Specification, PrintThis command prints the switching class data in the operating area.

Parameter DescriptionSWC Facilates time differenciated tariff implementation. It is linked toTariff Class.

CHSPI: SWC=swc;Charging Administration of Switching Class Procedure, InitiateThis command initiates a specification procedure of a switching class.

CHSSI: DCAT=day categories,Time= time; Switching Class Specification, InitiateThis command specifies switching times for one, several or all day categories.

DCAT

Days of the week have been classifed into three different

Categories.

DCAT0-Ordinary working day

DCAT1-Day before holiday(e.g. Saturday)

DCAT2-Holiday

TimeIndicates the time during the day when tariff change is to be Make

CHSPE;

Switching Class Procedure, EndCHSAI:SWC=swc; Activates the Switching Class stored in the Non-Operating Area

This command ends specification procedure of a switching class.

G.4.8. DEFINE THE TARIFF CLASS DATA

CHCSP: TC=ALL;

Tariff Class Specification, PrintThis command prints tariff class data in the operating area .


Tariff Class

-Identity of Tariff class.Refers to Tariff data.leads toTariff data

and Switching Class (If time differenciated charging is defined)

CHCPI: TC=tc, SWC=swc;

Tariff Class Procedure, InitiateThis command initiates specification of a tariff class. The command is used only in conjunction with time-differentiated charging.

CHCSI: DCAT=dcat, T=t; Tariff Class Specification, InitiateThis command specifies tariff class data for one, several, or all day categories. Charging for a particular day category must always be defined. This format is used with time-differentiated charging.

Parameter DescriptionT Tariff Data Identity

CHCPE;

Charging Administration of Tariff Class Procedure, EndThis command ends a specification procedure of a tariff class. It is used only with time-differentiated charging.CHCAI: TC=tc;

Charging Administration of Tariff Class Activation, InitiateThis command activates a change of a tariff class or puts a tariff class that was previously not in operation into operation.

G.4.9. DEFINE THE CHARGING PROGRAM.

CIPSP: CHP=ALL;

Charging program specification, Print

This command initiates a printout of charging program data for operating area.CIPSI: CHP=chp, CD=3,TC=tc, TTD, AP; Charging Program Specification, InitiateThis command specifies charging program data. A charging program defines the charging actions to be performed, how they are to be performed, and where in the network they are to be performed.


CHP

Charging program

CD

Charging determining Code. Determines whether

the switch is the charging or Charge determining or charging and charge determining point

TC

Identity of Tariff Class

TTD

Toll Ticketing Pulse Distribution

AP Calling Party

CIPAI: CHP=chp;

Charging program activateThis command activates a change of a charging program or puts into operation a charging program which was not previously in operation. When a change has been executed, the old data of this charging program are protected for a specific period of time, during which only a return to the original data can be Make.G.4.10. DEFINE THE CHARGING CASE

CIBSP: CC=ALL;

Charging case branching specification, print

This command initiates a printout of charging analysis data of the operating area. The command is not allowed while a charging case is being defined.Parameter Description

CC

Identity of Charing Case

CIBSI: CC=cc, CHP=chp;Charging Case Specification, InitiateThis command indicates which branching parameter is to be used in a charging case.

Parameter description

CC

Chaging Case

CHP

Charging Program

CIBAI: CC=cc;CHARGING CASE BRANCHING ACTIVATION, INITIATE This command activates a change of a charging case or puts a charging case which was not previously in operation into operation. When a change has been executed, the old data for this charging case is protected for a specific period of time during which only a return to this original data can be Make.

G.4.11.TESTING

Introduce the charging case in B-number analysis table and make some calls and verify the charging. Changing Tariff data and switching class can change the charging rate and switching timings. It is desirable to keep the testing no. in meter observation & calls had been Make in different time slabs.

G.5. CONCLUSION


H. STANDARD OPERATING PROCEDURE FOR B-NUMBER ANALYSIS

H.1. SCOPE

This document explains the procedure for the B-number analysis. This is the final analysis table that supplies the information to other analysis tables.

H.2. DESCRIPTION

H.2.1. Check the work order for details on Route, Routing case

and Charging case.

H.2.2.Check the status of the route, routing case and charging case. Refer H.4.1.

H.2.3. Print the B-Number analysis Table for B-Origin in work order.Refer H.4.2.

H.2.4. Define the B-number analysis

Refer H.4.3.

H.2.5. Verify the definition

Refer H.4.4.

H.2.6. Testing

Refer H.4.5.

H.3. REQUIREMENTS

H.3.1. Approved Work Order

H.3.2. Information of the Route, Routing Case, Charging Case and Destination Table

H.3.3. ALEX and Standard Operating Procedure.

H.4. PROCEDURESH.4.1. CHECK THE STATUS OF ROUTE, ROUTING CASE AND CHARGING CASE

EXROP:R=route name;

STRSP:R= route name;

ANRSP:RC=routing case;

CHCSP:CC=charging case;

H.4.2. PRINT THE B-NO. ANALYSIS TABLE FOR B-ORIGIN IN WORK ORDER.

ANBSP:B= b-number origin;

A copy of the B-number table should be stored before doing any modifications.

H.4.3. DEFINE THE B-NUMBER ANALYSIS

ANBLI; Analysis of B-Number, Logged, InitiateThis command initiates clearing the protection time on the previous (old) tables in the non-operating area. The order is automatically performed when the protection time has elapsed.

ANBZI;

Analysis of B-Number, Zeroing, Initiate.

This command initiates a zeroing of the entire non-operating area for the B-number analysis.

This command should not be given before the elapse of the protection period (24hrs)

ANBCI;

Analysis of B-Number, Copying, Initiate

This command initiates copying of the operating table for B-number analysis to the non-operating area. After this command the NOP and OP will have the similar data.

ANBSI: B=b-number origin, D=destination table, M=modification,CC= charging case,RC=routing case, L=length;

Note: Before giving this command all the parameters to be checked from ALEX.

ANBSI

Analysis of B-Number, Specification, InitiateThis command initiates specification of the result of a B-number analysis for a number series with a routing case, and is used for changing B-number analysis tables.


B

Contains the origin for analysis and the digits to be analysed.

L

Indicates the length of the B-number. If the length is unknown the

minimum and maximum lengths are specified.

MThe number of digits to be deleted and digits to be entered in the digit magazine, counted from the first position of the number, are specified here.

RCReferences of Routing Cases and terminating traffic. For definition of RC refer document SOP/NOC-F/R1

CC References of Charging Cases. For definition of CC refer document SOP/NOC-G/R1

DIdentifies a trunk discrimination case and is used for blocking certain number series for certain subscribers.

Expressed as d1-d2 where:

d1 Superior traffic destinationd2 Subordinate division of d1

Note: If more than one digit to be analysed, the numbers should be given in steps as shown below.

ANBSI:B=10-0;

ANBSI:B=10-01;

ANBSI:B=10-019;

ANBSI:B=10-0192;

ANBSI:B=10-01921,D=12-0,RC=90,L=5;

ANBSP:B=b-number origin, NOP;

Analysis of B-Number Print in NOP.

Check the new B-number definition in Non-Operating area before activating it to Operating area.

ANBAI;

Analysis of B-Number, Activation, InitiateThe command activates the whole NOP area and makes it operating. The old data, previously in the operating area, is now in the NOP and it is write protected for 24hrs.

H.4.4. VERIFY THE DEFINITION.

ANBSP:B=ALL,COMP;

Analysis of B-Number Print and Compare.

The number series that are different on the operating area (OP) and in the non-operating area (NOP) must be printed out.

H.4.5. TESTING

Make the call to the destination and check if the call is through.

H.5. CONCLUSIONAfter completion of above process, close the work order and forward it to concerned department.

ADMINISTRATIVE MANAGEMENT

Sub-Process Name:

I. Procedure for Back-Up Management

J. Procedure for Subscriber Management

K. Terminal and password Management

I. STANDARD OPERATING PROCEDURE FOR BACK UP MANAGEMENT

I.1. SCOPE

This document explains the procedures for backup of CP i.e. the system dump, backup of AMA records, and backup of alarm.

I.2. DESCRIPTION

I.2.1. Automatic dump of the system.

I.2.2. Manual system dump Backup on OD.

I.2.3. AMA backup.

I.2.4. Transaction Log backup.

I.3. REQUIREMENTSI.3.1. OD disk I.3.2. Alex processes & standard operating procedures

I.4.PROCEDURES

I.4.1. AUTOMATIC DUMP OF THE SYSTEM.

SYBUI: DISC;System functions, backup information output, initiateThis command is used to activate the automatic output function for the small and the large data dumps respectively.

Parameter descriptionDISC The parameters DISC are used to indicate the medium towards which the output function will be activated. The parameter DISC entails output towards one single predefined file (RELFSW0) on disc store.

I.4.2. MANUAL SYSTEM DUMP AND BACKUP ON OD

SYBUP:FILE; System functions, backup information output, punchThis command initiates the output of a system backup copy. The parameter "File" indicates the medium to which the output has to be carried out. The output will normally get copied to the RELSW2 file in Hard disk. This command copies the contents of DS & PS to the Hard Disk.

The file is a generation number that must be created on the hard disk before back-up command is issued. The backup will take around 60 minutes to give the result printout.


File

Name of the File in the Hard disk.

INMCT:SPG=0;IO subsystem functions file management functions change, transfer This is the entry command to the file management system. The command is intended to be used by operators with the highest authority which allows change, initiate and printout commands.

INVOL: Node = A, IO=OD-1; IO Subsystem Functions, Volume Administration, LoadThis command is used to load (open) a volume belonging to a removable medium.This command is received in a Support Processor (SP).

Note: Insert the OD before giving this command.

END;

END of Procedure

SYMTP: SPG=0, DIR=OUT, NODE=node, IO2=OD-1, FILE2=RELFSW2;

SYMTP

System Functions, Media Transfer, PunchThe command converts a backup copy between a hard disc and a portable medium in both directions, in the same Support Processor Group.Parameter Description

SPGSupport Processor Group. Specifies in SPG0 conversion is to be Make.DIRThe command converts a system backup copy from hard disc to portable medium.

NODENode in the Support Processor Group. We can give the value of A or B.

IO2

IO file device, Expressed as dt-n where

dt - Device type (Optical Disk)

n - IO device number

FILE2 Basic component in the file name on the portable medium

INMCT:SPG=0;IO subsystem functions file management functions change, transfer This command is the entry command to the File Management System. The command is intended to be used by operators with the highest authority which allows change, initiate and printout commands.

INVOE:NODE= node name,IO=OD-1;IO subsystem functions volume administration, END The command must have been preceded by the path-building command INMCT. Command INVOE is used to dismount a volume on a removable medium, which is mounted on the specified IO-unit.

END;

END of Procedure

Note : The OD from the OD drive should be removed only after the volume is ended by command INVOE. If it is removed before ending the volume, then the OD drive needs to be formatted.

SYTUC;System Functions, Total Update of Backup Files, ChangeThis command orders updating all the Back-up files by means of name rotation which exists in the Hard Disk. By renaming the files successfully, Relfsw2 is renamed as Relfsw0, Relfsw0 as Relfsw1 and Relfsw1 as Relfsw2. The latest copy should be in Relfsw0 and the oldest copy should be in Relfsw2.

RELFSW0 RELFSW1

RELFSW1 RELFSW2

RELFSW2 RELFSW0I.4.3. AMA BACKUP ON OD.

The AMA records in AXE are dumped in HDD periodically. The block

CHOFTT is handling this function. This block keeps about 20 records in its

buffer and then dumps to the hard disk of the IOG. The buffer size of this

block can be checked by following command:

SAAEP:SAE=500, BLOCK=CHOFTT;Size Alteration, Alteration Event, PrintThis command is used to print information about one or several size alteration events (SAE) in the exchange.


SAE

- Size Alteration Event

BLOCK

- Block designation

The AMA file in AXE is known as TTFILExx where xx is denotation number

between 00-99 e.g. TTFILE00. The file is created and then defined in File

Process Utility (FPU).

BACKUP OF TTFILES

Insert the OD in the OD drive.

INMCT :SPG=0;

Entry command to FMS.

INVOL: VOL=volume name,IO=OD-1,NODE=A(B); Open the volume

END;

INMCTThis is the path building command to File Management Subsystem. Subcommands are given following this command, which are executed in SPG.

INVOLThis command loads or opens the volume in the Optical Disk.

INMCT :SPG=0;


INFIP:FILE=OD0A1; List the Subfiles copied in the Optical Disk

END;

INFIPThis command lists the subfiles copied in Optical Disk.

INFSP:FILE=TTFILE00,DEST=destination; List the subfiles defined in the destination.

INFSP

This command prints the list of subfiles with their file size, in the defined destination. This also gives the transfer status (transfer of subfile to the defined destination via data link) and dump status ( dumping of the subfile in to the OD) INMCT: SPG=0;


INFET:FILE1=TTFILE00-XXXX,FILE2=XXXX,VOL2=volume name;

END;

INFET

Copy the TTfiles in OD.

This command copies the TTfiles from the hard disk to Optical Disk.

where xxxx is the subfile which was closed.

INMCT :SPG=0;


INVOE:VOL=TTFILE;

Unload the volume

END;

INVOEThis command unloads or closes the volume in the Optical Disk.

I.4.4. TRANSACTION LOG BACKUP

This activity is done in order to keep track of the transactions carried out in the switch. A composite file has been defined by name TRLOGFILE in the FMS Subsystem to log the transactions. The conditions to log the Commands and Printouts executed in the IO terminals are defined through the command " MCTLC". The file has transactions of the last 240hrs at any point of time. By logging the printouts from the AT connected to the printer & commands from other ATs, the alarms and the action taken information can be extracted.

i) Initiate the search in Transaction log for Printouts

All alarms in AXE are displayed on the alarm terminal and i.e. default AT-0.

The backup of this terminal can be taken separately in transaction log file.

Open a log file yymmdd.prn in WINFIOL to log the Printouts from terminal connected to the printer, where yy indicates the year, dd denotes the date & mm denotes the month.

IMLIT:SPG=0;

MCSAP:FILE=TRLOGFILE,SDATE=YYYYMMDD,STIME=0000,IO1=AT-0,(printer terminal) PRINTOUTS,EDATE=YYYYMMDD,ETIME=2359;

END;

where yyyy indicates the year, mmstands for the month & dd denotes the date.

The command MCSAP initiate the search in the transaction log. The search can be based on type of transaction, date & time, IO & specific commands.

Example

! open a log file 20020901.prn !

mcsap:file=trlogfile,sdate=20020901,stime=0000,io1=at-0, printouts, edate=20020901, etime=2359;

The log file is then copied to a external media (eg. Floppy).

ii) Initiate the search in Transaction log for Commands

Open a log file yymmdd.cmd in to log the Commands from the defined ATs , where yy indicates the year, dd denotes the date & mm denotes the month.

IMLIT:SPG=0;

MCSAP:FILE=TRLOGFILE,SDATE=YYYYMMDD,STIME=0000,EDATE=YYYYMMDD, ETIME=2359,IO1=ALL,COMMAND=ALL;

END;

where yyyy indicates the year, mm denotes the month & dd indicates the date.

Example! open a log file 20020901.cmd !

mcsap:file=trlogfile,sdate=20020901,stime=0000,io1=all, command=all, edate=20020901,etime=2359;

END;

MCSAPMan Machine Communication Subsystem Functions, Authorized Search in Transaction Log, PrintThe command is received in a Support Processor (SP).It is used to order a search in the transaction log and obtain a printout of the search result. The output of the command MCSAP has to be copied in the log file.

The log file is then copied to a external media (eg. Floppy).

I.5. CONCLUSION

The backups should be taken as per the schedule. After every back up activity, name the external media and store it in a safe place.

J. STANDARD OPERATING PROCEDURE FOR SUBSCRIBER MANAGEMENT

J.1. SCOPE

This document explains the procedures for subscriber services.

J.2. DESCRIPTION

J.2.1. Priority calls

J.2.2. Call barring operator controlled.

J.2.3. Call barring subscriber controlled.

J.2.4. Absentee subscriber service, pstn

J.2.5. Call forwarding

J.2.6. Anonymous call rejection

J.2.7. 16khz home metering

J.2.8. Call completion to busy subscribers intra exchange

J.2.9. Call Return

J.2.10. Selective call Acceptance

J.3. REQUIREMENTSJ.3.1. Reference Document

J.3.2. Work order with subscriber classJ.4. PROCEDUREJ.4.1. PRIORITY CALLS

Purpose

To give priority only to certain numbers to make out going calls.

Description

This test enables the subscribers with priority to make outgoing calls when the system state is set to high priority, or some software correction is getting loaded where the outgoing calls has to be restricted or during very high traffic.

Test Setup

Three Telephones connected to a access network over a V5.2 interface with a LE.

Pre-requisites

Nil

Actual Procedure

1. Creat the priority for the A -Subscriber with the parameter PRI-2 in LE.

SUSCC:SNB=4431999016,SCL=PRI-2;

2. Set the system to alarm state where normal subscribers cannot make outgoing calls.

PLSDC:SAL=2;

3. Make a call from B-Subscriber to C-Subscriber and the call should not success.

4. Make a call from A -Subscriber to C-Subscriber and the call should success.

5. Remove the system from the alarm state.

PLSDC:SAL=0;

6. Make a call from B-Subscriber to C-Subscriber and the call should success.

7. Remove the facility in LE.

SUSCC:SNB=4431999016,SCL=PRI-0;

J.4.2. CALL BARRING OPERATOR CONTROLLED.

Purpose

To test the feature Outgoing Call Barring Fixed Supplementary service AXE10Description

The Outgoing Call Barring Fixed supplementary (OCBF) service makes it possible for the subscriber to prevent all outgoing calls or calls dependant on the destination. With Fixed service the operator has the control on barring. The service is arranged by the service provider using operator commands when the service is assigned to the subscriber. Different Barring Programs based on the destination is activated by the operator and the subscriber cannot control the supplementary service by means of subscriber procedure. Destination is dependent on B-number analysis. When the OCBF is active the ability of the subscriber to receive calls is not affected.

Available barring programs:

1Barring NSD and ISD

2Barring NSD, ISD, calls to Manual booking, Special services & Level95.

3Barring ISD calls only

4Barring all outgoing calls except emergency calls.

5 Barring NSD only

Test Setup

2 Telephones connected to a access network over a V5.2 interface with a LE.

Pre-requisites

Nil

Actual Procedure

1. Create the facility for subscriber services in LE with the parameter CCB-2 & KWC-0 for Subs.A

SUSCC:SNB=4431999001,SCL=CCB-2&KWC-1;

2. Define the Barring program 1 2 3 4 5 .

SUCBC:snb=4431999001,BP=1&&5;3. Activate the barring program by command

SUCBI:snb=4431999001,BP=4;4. Establish the call from Subs.A to B and the call should not establish.

5. Change the barring program from 1 to 5 and test all the cases.

6. Remove the facility with the parameter CCB-0 for Subs.A.

SUSCC:SNB=4431999001,SCL=CCB-0;

Note: Further details on Call barring is given in the Application Information block BBLHJ.4.3. CALL BARRING SUBSCRIBER CONTROLLED.

Purpose

To test the feature Outgoing Call Barring , User Controlled, in the system AXE10.

Description

The outgoing Call Barring subscriber controlled enables an end-user to prevent his or her number from being used to make all or certain types of calls. A user controlled service implies the subscriber can control barring through a specific basic service or through all basic services by means of subscriber procedure. There are two types of user controlled service, prearranged barring program, or selective barring programs.

In user controlled prearranged barring program the subscriber has only one barring program to control by means of subscriber procedure. The end -user can only activate, deactivate the barring service and cannot change the Barring program.

In selective barring programs, the user can select the predefined barring program as per his need.

Available barring programs:

0 No barring

1 Barring NSD and ISD

2 Barring NSD, ISD, calls to Manual booking, Special services & Level95.

3 Barring ISD calls only

4 Barring all outgoing calls except emergency calls.

5 Barring NSD only

Required Equipment

Two Telephones, Winfiol.

Required Documentation

Level 2 documents

Test Setup


Actual Procedure

1. Create the facility for A-subscriber with the parameter CCB-2 & KWC-1 in LE.


2. Define the 4 digit keyword for Subs. A.

SUKWI:SNB=4431999001,KWORD=1111,TYPE=1;3. Define the Barring program 1 2 3 4 5 .

SUCBC:snb=4431999001,BP=1&&5;4. Change the password using the code 123 old new pwd .

5. Activate the barring program 4 in the handset using 124 new pwd barring program

6. Establish the call from A-Subscriber to B-Subscriber and call should not get matured.

7. Repeat the same for all the Barring Program.

8. Remove the barring using the code 124 new pwd barring program, where the barring program is 0.


Note : Further details on Call barring is given in the Application Information block BBLHJ.4.4. ABSENTEE SUBSCRIBER SERVICE, PSTN

Purpose

To divert the incoming calls in absence of the subscriber.

Description

The subscriber can divert his incoming calls to an announcement machine or to a tone in his

absence. Two variants of services exists,

a. Prearranged service ------The facility activated by the Operator.

b. Selective service ------The facility activated by the Subscriber.

Required Equipment

Three Telephones, Winfiol.


Level 2 documents

Test Setup


Pre-requisites

Nil

Actual Procedure

1. Create the absentee subscriber service with parameter CCA-1 in LE for the A-Subscriber..

SUSCC:SNB=4431999001,SCL=CCA-1;2. Initiate the subscriber diversion type =1.

SUDTI:SNB=4431999001,ADTYPE=1;3. Activate the service from the handset with the code *24#. Long beep confirmation tone should be heard.

4. Interrogate the service with the code *#24#.

5. Initiate the test system to trace the End-of-Selection.

6. Make a call from B-Subscriber to A-subscriber.

7. The call should not establish. Announcement or a Tone will be provided by the switch

8. Deactivate the service with the code #24# .

9. Repeat the test with different ADTYPEs. (1-31)

SUDTI:SNB=4431999001,ADTYPE=1&&31;

Note : The details on ADTYPE (1-31) and the End-Of-Selection cases for every ADTYPE is given in the Application Information block SUSASU J.4.5. CALL FORWARDING

i. UNCONDITIONAL

Purpose

To divert all the calls to another number.

Description

Call Forwarding Unconditional permits the served user to have the network send all the incoming calls to another number. If this service is active, calls are forwarded regardless of the state of the forwarded-to-number. The service can apply to all incoming calls.

Two variants of the service exist,

a Fixed service Service determined by the operator

b Variable service Service activated by the subscriber

Required Equipment



Level 2 documents

Test Setup


Actual Procedure

1. Create the call forwarding facility (fixed) in LE with the parameter CFUF-1

for A-Subscriber.

SUSCC:SNB=4431999001,SCL=CFUF-1;

2. Define the forwarded-to-number B-Subscriber with command

SUDNC:SNB=4431999001,SERVICE=CFUF,DIN=31999016;3. Activate the call forwarding service with the command

SFSAI:SNB=4431999001,SERVICE=CFUF;

4. Establish the call from C-Subscriber to A and the call should get routed to

B without any condition.

5. Remove the call forwarding unconditional facility and define the variable service

with the parameter CFUV-1 for A- Subs.A

SUSCC:SNB=4431999001,SCL=CFUF-0; SUSCC:SNB=4431999001,SCL=CFUV-1;

6. Activate the forwarded-to-B-number from the Telephone with the code

114 B.number

7. Establish the call from Subs.C to A and the call should get routed to B

without any condition.

8. Deactivate the service from the Telephone with the code 115.

9. Remove the facility by command in LE.

SUSCC:SNB=4431999001,SCL=CFUV-0;ii. BUSY

Purpose

To divert the calls to another number under the busy condition..

Description

Call Forwarding Busy permits the served user to have the network send all incoming calls to another number if the user is busy.




Required Equipment



Level 2 documents

Test Setup


Actual Procedure1. Create the call forwarding facility (fixed) in LE with the parameter CFBF-1 for A-Subscriber SUSCC:SNB=4431999001,SCL=CFBF-1;2. Define the forwarded to number B-Subscriber with command

SUDNC:SNB=4431999001,SERVICE=CFBF,DIN=31999016;3. Activate the call forwarding service with the command

SFSAI:SNB=4431999001,SERVICE=CFBF;4. Keep the A-Subscriber in busy state.

5. Establish the call from C-Subscriber to A-Subscriber and the call should get

routed to B-Subscriber.

6. Remove the facility CFBF-1and define the variable service with the parameter

CFBV-1 for A-Subscriber

SUSCC:SNB=4431999001,SCL=CFBF-0&CFBV-1;7. Activate the forwarded to number in the Telephone with the code

1220 B. number#

8. Establish the call from C-Subscriber to A-Subscriber and the call should get routed

to B-Subscriber .

9. Deactivate the facility in the Telephone with the code 1221.

SUSCC:SNB=4431999001,SCL=CFBV-0;iii. NO REPLY

Purpose

To divert the calls to another number under no reply condition.

Description

Call Forwarding No reply permits the served user to have the network send incoming calls to another number if there is no reply.




Required Equipment



Level 2 documents

Test Setup


Actual Procedure

1. Create the call forwarding facility with the parameter CFNRF-1 for Subs.A.

SUSCC:SNB=4431999001,SCL=CFNRF-1;2. Define the forwarded to number Subs.B with command

SUDNC:SNB=4431999001,SERVICE=CFNRF,DIN=31999016;3. Activate the call forwarding service with the command

SFSAI:SNB=4431999001,SERVICE=CFNRF;4. .Establish the call from Subs.C to A and the call should not be answered.

5. After the ringing time, the call should get forwarded to B. Subscriber.

6. Remove the facility CFNRF-1and define the variable service with the

parameter CFNRV-1 for A-Subscriber

SUSCC:SNB=4431999001,SCL=CFNRF-0&CFNRV-1;7. Activate the forwarded to number with the code 1222. B. number*RTime#

8. Establish the call from C-Subscriber to A-Subscriber and the should not be answered.

9. After the ringing time, the call should get forwarded to B-Subscriber

10. Deactivate the service with the code 1223.

11. Remove the facility in LE with the command.

SUSCC:SNB=4431999001,SCL=CFNRV-0;Note : Further details are given in the Application Blocks SUSCFA, SUSCFDB, SUSCFIH, SUSCFPH and SUBCATJ.4.6. ANONYMOUS CALL REJECTION

Purpose

To reject the incoming calls with-out Calling Line Identification.

Description

The calls not having any CLI ( Calling Line Identification) facility and having CLIR (Calling Line Identification Restriction) activated are rejected.

Required Equipment



Level 2 documents

Test Setup


Actual Procedure

1. Create the facility in LE with the parameter ACRJ-1 for Subs.A

SUSCC:SNB=4431999002,SCL=ACRJ-1;

2. Create the facility with the parameter CLIR-1 for Subs.B

SUSCC:SNB=4431999016,SCL=CLIR-1;

3. Activate the service with the command

SFSAI:SNB=4431999002,SERVICE=ACRJ;4. Make a call from Subscriber B and the call should get rejected. Either an announcement or a tone will be fed by the switch.

5. Make a call from Subscriber C and the call should establish.

6. Deactivate the facilities with the commands

SUSCC:SNB=4431999016,SCL=CLIR-0;

SUSCC:SNB=4431999002,SCL=ACRJ-0;

Note : The Application Block SUSACRJ gives further information on Anonymous Call Rejection.

J.4.7. 16KHz HOME METERING

Purpose

To check the 16KHz pulse metering in AXE 10.

Description

This test enables the centralized private metering for connecting PCO monitors for which the 16KHz pulse will be sent from thecharging function located in the local exchange.

Required Equipment

PCO Monitor, One Telephone, Winfiol.


Level 2 documents

Test Setup


Actual Procedure

1. Connect the home meter as an A subscriber to the Access Network

2. Activated the 16KHz home metering function in LE with SUCPI command.

SUCPI:DEV=LIV5G-16;

3. Make a call from the phone connected to the Home meter (A-subscriber) to

B-Subscriber.

4. As soon as the call was established, the no. of pulses will be shown on the display of the Home Meter.

5. Receive the printout of the charges after the completion of the call.

J.4.8. CALL COMPLETION TO BUSY SUBSCRIBERS INTRA EXCHANGE

Purpose

To get the call back from the busy subscriber to the calling party.

Description

This service makes it possible for the served user, encountering a busy destination to have the call completed when the destination becomes idle. This service is activated by the served user when he/she encounters busy tone at the destination. When the destination or the B-subscriber becomes idle the network blocks the B-subscriber for incoming calls and waits a short period of time to allow B to make outgoing calls. If user B is still idle after this period of time the network informs Subscriber-A by giving a special ringing tone. When the calling party lifts the handset another ringing signal is sent to the destination which was busy and the call is established.

Required Equipment

Three Telephone, Winfiol.


Level 2 documents

Test Setup

Three Telephones connected to a access network over a V5.2 interface with a LE.

Actual Procedure

1. Create the Call back facility for the subscriber B with the parameter

CBB-1&FLA-2. SUSCC:SNB=4431999001,SCL=CBB-1&FLA-2;

2. Make a call from Subscriber C to Subscriber A and keep the subscriber A busy.

3. Make a call from Subscriber B to Subscriber A 4. Flash the phone once and dial the code #5 and keep the receiver on-hook

5. After the completion of the call between subscriber C and A, a special ringing tone is fed to Subscriber A and after A lifts the handset, the ringing tone is fed to B-subs.

6. The call will get established successfully between subscriber A and B.

7. Remove the facility by the command.

SUSCC:SNB=4431999001,SCL=CBB-0&FLA-0;

Note : Further details on this service is given in the Application Information block SUSCCTA J.5.9. CALL RETURN

Purpose

The Call Return service registers the information of the last incoming call.

Description

The call Return service is an incoming call service which registers information of the last unanswered call and enables a user to make a return call to the registered number by using a subscriber procedure. Only one registration is possible, which remains until a new incoming call overwrites the latest registration or an erasure procedure is invoked.

There are two versions of the services availablea. BasicThe served user does not get any information about the last incoming call which was registered, when the service is invoked.

b. EnhancedThe served user gets information about the last incoming call which was registered (called partys number, date and time) when the service is invoked.Required Equipment



Level 2 documents

Test Setup


Actual Procedure

1. Create the Call Return facility with the parameter CR-1 in LE for A-Subscriber

SUSCC:SNB=4431999001,SCL=CR-1;

2. Make a test call-1 from C-Subscriber to A-Subscriber

3. Make a test call-2 made from B-Subscriber to A-Subscriber

4. Both the calls should not be answered by A-Subscriber

5. Pick up the phone and dial the code *92# and the call will establish between

A-Subscriber and B-Subscriber.

6. Remove the Call Return facility with the parameter CR-0.

SUSCC:SNB=4431999001,SCL=CR-0;J.5.10. SELECTIVE CALL ACCEPTANCE

Purpose

Selective incoming calls are accepted and other calls are rejected.

Description

Selective Call Acceptance permits the subscriber to receive incoming call from selected numbers and other calls are routed to an announcement or to a Special Tone.

Required Equipment



Level 2 documents

Test Setup


Actual Procedure

1. Create the facility with the parameter SCA-1 for A-Subscriber in LE.

SUSCC:SNB=4431999001,SCL=SCA-1;

2. Activate the supplementary service by the command and the number of origination where the incoming calls to be accepted is defined as 10.

SFSOC:SNB=4431999001,SERVICE=SCA,OPT=LSIZE-10;

3. Define 10 numbers (B-Subscribers) from where the call is to be accepted.

SFSLC:SNB=4431999001,SERVICE=SCA,POS=1,ANB=4431999016;4. Activate the service from the Telephone with the code *932#. A long beep confirmation tone should be heard.

5. Establish the call from B-Subscriber to A-Subscriber and the call should be

successful.

6. Establish the call from C-Subscriber to A-Subscriber and the call should not be successful .

7. De-activate the feature from the Telephone with the code #932#. 8. The same feature can be activated with the command in the LE instead of the code in handset to test the fixed service.

SFSAI:SNB=4431999001,SERVICE=SCA;

9. Remove the feature for the A-Subscriber after the test.

SUSCC:SNB=4431999002,SCL=SCA-0;

J.5. CONCLUSION

The Subscriber services should be tested after creating the procedure and verify if the service is working ok.

K. STANDARD OPERATING PROCEDURE FOR TERMINAL AND PASSWORD MANAGEMENT

K.1. SCOPE

This document describes how to assign authority to terminals or users. Purpose of this document is to insert the password user-wise or terminal wise. This document also describes creating command class and attaching password to the command class.K.2. DESCRIPTION

K.2.1. Attaching password to terminal.

Refer K.4.1.

K.2.2. Creation of command category

Refer K.4.3.

K.2.3 Insert authorisation to terminal group.

Refer K.4.4.

K.2.4. Insert authorisation for user group.

Refer K.4.5.

K.2.5. Shifting command from one command class to other. Refer K.4.6.

K.2.6. Creation of password level.

Refer K.4.7.

K.2.7. Modification of password.

Refer K.4.8.

K.2.8. Addition of password to O & M operator

Refer K.4.9.

K.2.9. Deletion of password to O & M operator

Refer K.4.10.

K.3. REQUIREMENTS

K.3.1. Approved Work Order

K.3.2. Reference Manual

K.4. PROCEDURES

K.4.1. ATTACHING PASSWORD TO TERMINAL.

IOTAC:IO=io,ATGR=atgr,AUTH=yes or no;

Terminal Authority ChangeThis command is used to change a terminal's terminal group and authority condition.

The authority condition is either "Yes", authority is required by the user of the terminal, or "No", authority is not required.

It is not permitted to perform changes upon a terminal that is in use and has an authority condition set. If the specified terminal is otherwise in use, the terminal's group and the terminal's authority condition will remain unchanged until the end of the terminal's present command session. It is not permitted to perform changes upon the ordering terminal.


ATGR

Alphanumeric terminal group

Numeral 0 - 15

AUTH

Authority condition

YES Authority requirement is set for the user

of the terminal.

NO Authority requirement is not set.

IO

Alphanumeric terminal name

K.4.2. PRINT THE THERMINAL AUTHORITY

IOTAP; IO Subsystem functions, Terminal Authority, Print. This command is used to print out the list of terminals, their terminal group and whether use of the terminal requires authority by the user.

K.4.3. CREATION OF COMMAND CATEGORY

IOCTI:COMMAND=command,COCA=coca;

IOCTI

Command category group table, Insert.

This command is used to put a command into another Command Category Group. The command and its new command category is stored in the Command Category Group Table.


COCA

Command Category Group

Numeral 0 255

COMMAND

Command name

Characters 1 - 7 charactersK.4.4. INSERT AUTHORISATION TO TERMINAL GROUP

IOTGC:ATGR=atgr + [,CATI=cati..] [,CATR=catr...];

IOTGC

Terminal group, Change.

The command IOTGC is used to change the authorization given to a terminal group. Several terminal groups can be authorized for the same category. One terminal group, and a maximum of 256 categories, can be specified in one IOTGC command.

Note : It is not permitted to change the authority of the terminal group of the ordering terminal.


ATGR

Terminal group.

A terminal group consists of one or several terminals.

Numeral 0 - 15

CATI

Category insertion.

Numeral 0 - 255

CATR

Category removal.

Numeral 0 - 255

K.4.5. INSERT AUTHORISATION TO USER GROUP

IOUGC:USERGR=usergr+ [,CATI=cati..] [,CATR=catr...];

IOUGC

IO Subsystem Functions, User Group, Change

The command IOUGC is used to change the authorization given to a user group. Several user groups can be authorized for the same category. One user group, and a maximum of 256 categories, can be specified in one IOUGC command.

Note: It is not permitted to change the authority for the user group of the ordering user.

K.4.6. SHIFTING OF COMMAND FROM ONE COMMAND CLASS TO OTHER

IOCTE:COMMAND=command;

Command Category Group Table, Erase.

This command is used for deleting or erasing the changed command category group, for a given command name, in the Command Category Group Table.

The given command will resume its ordinary command category group.

IOCTI:COMMAND=command,COCA=coca;

IOCTI

Command Category Group Table, Initiate.

This command is used to put a command into another Command Category Group. The command and its new command category is stored in the Command Category Group Table.

K.4.7. CREATION OF PASSWORD LEVEL

IOUAL:USER=user,PSW=psw,USERGR=usergr;User Authority, Load

The command IOUAL is used to insert a new user identity into the system.

Note : Only the command code IOUAL, colon and semicolon are logged on the transaction log. No parameter between colon and semicolon in the command string is logged. The command is logged on the command log, with the password encrypted.


USER

Usercode.

This is the identity code given to one system user, and is represented by a string of length 1 to 15 printable

alphanumeric ASCII characters.

Note : USER=ALL is not allowed.

PSW

Password.

The password is a secret code, which is known only by the user, and is stored encrypted.

The password is connected with the usercode, and is only used to validate the given usercode.

Passwords are represented by a string of length 6 to 15 printable alphanumeric ASCII characters, and contains at least one digit in any position.

USERGR

Usergroup.

A usergroup consists of one or several users.

Numeral 0-15.

K.4.8. MODIFICATION OF PASSWORD

IOUAC:USER=user,OLDPSW=oldpsw,NEWPSW=newpsw;IOUAC

IO Subsystem Functions, User Authority, Change.

This command makes it possible for an operator to change his password, so it better suits his situation. It is not possible for the operator to change the password for someone else.

The command is only accepted from a terminal that requires usercode and password at logon, where the specified USER in the command IOUAC must be the same as the entered usercode.


USER

Usercode.

This is the identity code given to one system user, and is represented by a string of length 1 to 15 printable alphanumeric ASCII characters.

OLDPSW

Old password.

The password is a secret code, which is known only by the user, and is stored encrypted.

NEWPSW

New password.

K.4.9. ADDITION OF PASSWORD

IOUAI:USER=user;

IO Subsystem Functions, User Authority, Initiate

This command initiates authority for users who are defined to the system. It also ends the alarm that was generated when command IOUAE :USER=ALL; was initiated.

K.4.10. DELETION OF PASSWORD

IOUAE:USER=user;

IO Subsystem Functions, User Authority, End

This command ends the authority of users who are defined to the system. The command will not end the authority of a user who is logged onto the system until that user logs off. The command will not end the authority of the ordering user.

K.5. CONCLUSION

After completion of above process, close the work order and forward it to the concerned department.

PERFORMANCE MANAGEMENT

Sub Process Name:

L. Procedure for Performance Management Traffic Measurement

M. Procedure for Performance Management Service Quality Measurement

L. STANDARD OPERATING PROCEDURES FOR TRAFFIC MEASUREMENTS

L.1. SCOPE

The purpose of this procedure is to test traffic measurement administration

Loss system on Route/Queuing system on Routes/Traffic destinations /Traffic type.

L.2. DESCRIPTION

L.2.1 Print Subscriber Line Groups

Refer L.4.1.

L.2.2 Free Traffic Recording identities print.

Refer L.4.2.

L.2.3 Traffic Measu

Document for AXE-10

Documents

Transcript of Document for AXE-10