SWR2219(2.22)

C-DOT DSS MAX

SOFTWARE RELEASE 2_2_1_9(2.22)

RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX

System Practices

Section No. 400-643-0967

Draft 01, June 2010

C-DOT DSS MAX

SOFTWARE RELEASE 2_2_1_9(2.22) RETROFIT

PROCEDURE FOR MAX/SBM-RAX/TAX

© 2010, C-DOT Printed in India

C-DOT DSS MAX

SOFTWARE RELEASE 2_2_1_9(2.22) RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX

DRAFT 01

JUNE 2010

ASADHA 2066

SERIES 600 : SOFTWARE

CSP SECTION NO. 400-643-09467

THIS C–DOT SYSTEM PRACTICE REFERS TO THE C–DOT DIGITAL SWITCHING SYSTEM

MAIN AUTOMATIC EXCHANGE (ABBREVIATED AS C–DOT DSS MAX IN THE REST OF THIS

PUBLICATION).

THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION PURPOSES AND IS

SUBJECT TO CHANGE WITHOUT NOTICE.

A COMMENT FORM HAS BEEN INCLUDED AT THE END OF THIS PUBLICATION FOR

READER'S COMMENTS. IF THE FORM HAS BEEN USED, COMMENTS MAY BE ADDRESSED

TO THE DIRECTOR (C & S), CENTRE FOR DEVELOPMENT OF TELEMATICS, C-DOT

CAMPUS, MEHRAULI, NEW DELHI - 110 030

© 2010 BY C–DOT, NEW DELHI.

Table of Contents

Chapter 1. Introduction & Release Highlights ................................................................................................ 7 1.1. SBM RAX/TAX and C-DOT DSS MAX ............................................................................. 7 1.2. Software Release 2_2_1_6 (2004) ...................................................................................... 8 1.3. New Software Release 2_2_1_9 (2007) ........................................................................... 22

Chapter 2. Software and Hardware Status .................................................................................................... 29 2.1. Software status ................................................................................................................ 29 2.2. Change of Eproms Required for S/W Release 2_2_2.22_9 over Existing Release ........... 2_2_7.7_6 .......................................................................................................................... 36

Chapter 3. Software Retrofit Philosophy and Pre-Retrofit Checks .............................................................. 37 3.1. General Considertions ..................................................................................................... 37 3.2. Pre-Retrofit Checks .......................................................................................................... 38 3.3. Contact nos. of c-dot control room ................................................................................... 38

Chapter 4. Retrofit Procedure From 2_1_7.7_6 to 2_2_1_9 ........................................................................... 39 4.1. Pre Retrofit Activities ...................................................................................................... 39 4.2. Mock retrofit Procedure – One day before the Retrofit date ......................................... 39 4.3. Final Retrofit Procedure .................................................................................................. 43 4.4. Post-Retrofit Checks ........................................................................................................ 48 4.5. Recovery Action ................................................................................................................ 49 4.6. Retrofit Completing Activities ........................................................................................ 49 4.7. Procedure to View Subscribers & TGPs Detail Bill Records Through RGEN Utility . 50 4.8. Time Zones and Tariff Classes for HOLIDAY & Normal Day ...................................... 50 4.9. Modify Definition of Day Type 1 and 2 as per Table I, using command ‘MOD-TYP- ...... DAY’ .................................................................................................................................. 51 4.10. Implementation of Distinctive Ringing feature ............................................................. 52

Chapter 5. Retrofit Procedure from S/W 2_2_1_9 (2.11) / 2_2_1_9 (2.13)/2_2_1_9 (2.16) to ....................... 2_2_1_9 (2.22) ................................................................................................................................ 53 5.1. Change of S/W Deliverables in 2_2_2.22_9 over 2_2_2.11_9/ 2_2_2.13_9/2_2_2.16_9. 53 5.2. Retrofit Procedure for C-DOT Exchanges having S/W 2_2_2.11_9/ 2_2_2.13_9/ ............ 2_2_2.16_9 ........................................................................................................................ 53

Chapter 6. Details of Centrex Feature Implementation ............................................................................... 56 6.1. Main Highlights of Centrex feature offered in this release are : .................................. 56 6.2. Details of Centrex Feature Implementation. ................................................................. 56 6.3. Call Handling Strategy for different type of Centrex Calls ........................................ 57 6.4. Change In Usage Of Existing Facilities By Centrex Members ..................................... 58

6.5. Charging and Billing ....................................................................................................... 58 6.6. Traffic Observation .......................................................................................................... 59 6.7. Changes in Man-Machine Interface................................................................................ 59 6.8. Detailed Description Of New Commands ....................................................................... 64 6.9. Enhancements To Existing Commands .......................................................................... 76 6.10. Changes In SIF Procedures ............................................................................................. 90

Chapter 7. Special Priority Implementation in S/W Release 2_2_1_9 ......................................................... 91 7.1. Feature Introduction ........................................................................................................ 91 7.2. Feature Implementation .................................................................................................. 91 7.3. At Originating Exchange ................................................................................................. 91 7.4. At Transit Exchange ........................................................................................................ 94 7.5. Commands Updations ...................................................................................................... 95

Chapter 8. New Strategy for Detailed Billing Records (CDR) Generation & Transfer ............................... 97 8.1. Feature Introduction ........................................................................................................ 97 8.2. Implementation ................................................................................................................ 97

Chapter 9. Do's and Dont's .............................................................................................................................. 99 9.1. IOP Related Problems and Solutions ............................................................................. 99 9.2. Do's and Dont's for Card Handling ............................................................................... 103 9.3. General - DO'S and DON'TS for O&M Activities ........................................................ 104 9.4. Operation and Maintenance Related Guidelines ......................................................... 105

Annexure - A IOP Loading Procedure ............................................................................................................... 110

Annexure - B Duplication Procedure for Cartridge/Floppy ............................................................................. 116

Annexure - C EPROMs for English Announcements ....................................................................................... 120

Annexure - C (Contd.)EPROMs for BI-Lingual Announcements ...................................................................... 121

Annexure - D Addition of Base Module ............................................................................................................. 122

Annexure - E Optimized Utilization of PHC Terminal in VU ......................................................................... 128

Annexure - F Use of Subscriber Based Category for WLL Subscriber ........................................................... 129

Annexure - G Abort Filter Card (AFB) ECN Details ....................................................................................... 131

Annexure - H New Implementation on NSC and Fault Isolation Strategy .................................................... 133

Annexure - I Changes Required to be made to Run CTS-B Tool in 2_2_1_9 Software ................................ 139

Annexure - J List of Charge Rate Numbers ..................................................................................................... 141

H:\MAX-XL\WORD\SWR2219(2.22).DOC December 26, 2011

SOFTWARE RELEASE 2_2_1_9(2.22) RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX 7

Chapter 1.

Introduction & Release Highlights

1.1. SBM RAX/TAX AND C-DOT DSS MAX

Presently all the C-DOT exchanges have been upgraded to one of the following software versions available for different applications.

Software Release 1_4_5.43_3 (1997)

This is PSTN release to support normal subscriber features in different configuration of exchanges as SBM-RAX, MAX-L, ILT, RSU and TAX.


This release was being used by BSNL at sites, where main C-DOT exchange was having connectivity with private operator network. This release supported following features in addition to all the features of S/W 1_4_5.43_3 : • Revenue counters and detail billing on trunks. • CLI for long distance calls when C-DOT DSS is configured as ILT/TAX • 'CAMA' application when exchange is being used as ILT/TAX. • CLI for analog subscribers.


This release was being used by BSNL at sites, where CCS7 signalling and Network Synchronisation was required. All the 'MAX-XL' exchanges were being commissioned with this software. These two features were in addition to all the features contained in S/W 1_4_5.43_3.

Software Release 2_1_1_1 (1998)

This software release 2_1_1_1 was introduced to offer new features such as ISDN, 800K BHCA etc. as well as merge all the features of the earlier three different software releases. Thus all the features could be offered to subscribers at any site after retrofitting S/W release 2_1_1_1. The last patch in this series was 2_1_7.9_1.

Chapter 1

8 C-DOT DSS MAX

Software Release 2_2_1_4 (2001)

The software release 2_2_1_4 was introduced to support V5.2 protocol capability in addition to all the features supported by S/W 2_1_1_1. This provided connectivity with WLL (Access Network) of HFCL/Hundai, LG or Lucent technologies & AN-RAX of C-DOT technology. This software supported subscriber category based charging. Moreover same S/W supported Intelligent Network services also. The last patch in this series is 2_2_4.4_4 for PSTN and 2_2_5.5_4 for IN working.

1.2. SOFTWARE RELEASE 2_2_1_6 (2004)

New S/W release 2_2_1_6 has been introduced to provide dynamic control for Lev 9x (except 90,96) default Detail Bill on these routs, Line Monitoring Feature, Increase in 'AI' links to '14' in MBM & '11' in SBM. These facilities are in addition to all the features supported in S/W 2_2_1_4. Detail of all the features is given below:

1.2.1. New Features Introduced in 2_2_1_6 S/W Release

1.2.1.1. Number of Access Interface Links have been Increased to '14' per BM in Case of MBM & '11' in SBM Exchange

It will be possible to connect '14' interfaces on V5.2 in one BM with single PCM Connectivity. This will find use for 'AN-RAX' connectivity.

1.2.1.2. Detail Billing Records Generation on all 9x Calls (Excluding 90 & 96) by Default and Dynamic Locking Control for these Levels

Dynamic locking/unlocking is available for 9x (excluding 90 & 96) levels as 'OG-UPTO-REG' access. Dynamic Locking/unlocking of Levels 9x is achieved by Dialling 124 ABCD1 and 124 ABCD5 respectively. This procedure will lock/unlock 9x levels simultaneously. Individual locking of 9x levels is not supported. CDRs will be generated for 9x (excluding 90 & 96) calls by default, in addition to '0' & '00' levels. Meter increment for 9x level calls will be done in 'STD' counters instead of Local Counters. Detail bill for these calls can not be stopped by any means.

1.2.1.3. New Announcements for Feature Invocation (Activation/Deactivation) in Place of Tones.

For various features invocations like Dynamic locking/unlocking, now 'announcements will be fed instead of tones. The announcements are following:

1. This feature has been invoked successfully.

2. Feature invocation has failed.

INTRODUCTION & RELEASE HIGHLIGHTS


Note :

Two Nos. of additional Language EPROMs will be required in each 'ANNC' card, to achieve this feature.

1.2.1.4. Queue Announcement to Caller in Case of Call Waiting in Place of RBT.

In case of Call-waiting, Calling party will get Queue Announcement instead of RBT

Announcement in this case will be "kindly wait, you are in Queue".

1.2.1.5. Unequipping of 'BM' Possible through 'CRP' Command "UNEQ-BM"

For this, there should be no data (subs/trunks) equipped in the BM. All the frames should be unequipped. Unequip all 'mfc' cards also.

1.2.1.6. Separate Area (STD) Code for RSU and Access Network for CLI Purpose

It is possible to assign separate STD code for RSU/Access Networks belonging to different SDCA's. For this, 'Area Code' field is available in 'MOD-XCOD' command. If Area Code field is not defined in an 'XCOD', then system parameters ARCD* will be referred for prefixing Area Code to CLI for that 'XCOD. Area Code Defined in 'MOD-RBM-XCOD' will superseed, the code defined either in 'MOD-XCOD' or 'ARCD*' parameters.

1.2.1.7. Separate Access for Special Services in Case of RSU & Access Network

By using 'MOD-RBMNRM-CONFIG' command special services like 131, 198 etc. can be mapped separately for RBMs. For this special service code 131/198 etc. should be opened on 'Alternate Nos' of the Main Exchange. If these routs are opened as normal rout, then mapping will not be possible. For Access Network, command 'CRE-ANNRM-CONFIG' can be used to map special service codes to DIR. NOS. belonging to respective 'AI' Nos.

1.2.1.8. Line Monitoring Feature to Enable Parallel Speech Monitoring of Any Subscriber No. ∗ For this the monitoring agency No. can be from the same exchange or any

other exchange on Subscriber Trunk Dialling. ∗ Maximum 30 Nos. per BM (A maximum of 100 Nos. in whole Exchange)

can be put on speech Monitoring Observation simultaneously. ∗ Special CDRs will be maintained for such calls. ∗ No charging will be done for calls routed to Monitoring Agency Nos.

Chapter 1

10 C-DOT DSS MAX

1.2.1.9. Change of SIF Codes for 3W_Conf/6W_Conf/Absnt_Fixed_Num Features to Enable Functioning of New Special Services 125X

New Codes have been covered in para 1.2.2.3.

1.2.1.10. 'DISPL-SUB-LIST' Command Enhancement

This command has been enhanced to get list of subscribers having different 'SUB-CAT'.

1.2.1.11. Transaction Records

Transactions on IOP upto '10000' records will be preserved in Trans files, after which, records will be overwritten. The file size has been reduced to half as compared to previous release 2_2_1_4. Trans files now will be transferred during IOP synchronization.

1.2.1.12. New Strategy for Charge Rate Number Definition

In S/W 2_2_1_6, any 'CRG-RTN' must be defined for all the 'Tariff classes' defined in Day Type = 1 or 2. Otherwise call will fail for categories for which such 'CRG-RTN' are allotted. In addition some recovery messages will be generated which may cause frequent system initialization.

1.2.1.13. Calling Line Identification (CLI) Sending and Presentation

A. CCS7 Signalling : Area Code for prefixing to 'CLI' is defined in system parameters ARCD-DGT*. - In case 1st digit (ARCD-DGT1) defined is zero (i.e. 10), then

Area Code without '0' will be sent towards next exchange. During CCS7 signalling messages parameter 'NAI' will be set as National (significant) Number. At the destination exchange (having 2_2_1_6 S/W), 'CLI' with '0' will be presented to the called party.

- In case ARCD-DGT1 = Non-Zero, then 'NAI' will be set as 'LOCAL' and 'CLI' without zero will be sent. At the destination exchange, CLI without zero will be presented the called party. Caution : In this case, ISD calls, to some countries specially 'Gulf Area' may fail.

B. MOR-R2 Signalling - In case, 'ARCD-DGT1=10', then Area Code without zero will be

sent towards next exchange. At the destination exchange, CLI with zero will be presented to the called party.

- In case, 'ARCD-DGT1=Non-Zero, then Area code, without zero i.e. as defined in 'ARCD-DGTS' will be sent towards destination.



At the destination exchange, CLI with zero will be presented to the called party.

Conclusion: Always define, 1st digit of Area Code as '0' in system parameters i.e. ARCD-DGT1=10. Also define NUM-ANI=10 in order to ask for 10 digits CLI.

1.2.1.14. Implementation of IVRS, Application as per 'TEC' Guidelines

As per New 'TEC' requirements, a route 1951/1952 is to be opened towards IVRS. Now, when a call for deleted subscriber is received, the exchange will route the call towards IVRS with digits '195x' prefixed to the Dialled digits. As a result, the deleted No. shall be sent to IVRS, which will directly announce the Changed Number to the Calling Party.

To achieve this, following steps of Data creation are required :-

1. 'MOD-SYS-DIRNO'

OPR-TYP : CRE

TYPE : IVRS

DIRNO : 1951 or 1952

2. 'CRE-ROUT'

ROUT-CODE : 1951, DIGIT-LENGTH = OPEN

with O/G TGP opened towards IVRS. This 'TGP' should have "Rank of digit = 5".

3. Delete the DIRNOs

DEL-SUB

DIRNO : No. to be Deleted

TEN : < >

MODE : IVRS

1.2.1.15. Call Diversion Possible on all 1x Levels (Except 10x)

BSNL Subscribers availing Answering Machine Service (AMS) can divert their calls on Level 170511, 170512, 170513 etc. or any other 1x level as desired (except 10x).

Chapter 1

12 C-DOT DSS MAX

1.2.1.16. Software Configuration Display

Crp command 'DISPL-SW-CONFIG' has been modified to show complete Software Release Identification on its first page of the output.

1.2.1.17. Continuity Check Feature and Compatibility

Continuity check and compatibility features are provided now as per latest ITU-T recommendations for CCS7 signalling. Continuity check is achieved by connecting a Transceiver (check tone transmitter and receiver) to the go and return paths of the outgoing circuit at the first and succeeding exchange. The continuity check is considered successful when a tone (2000 ± 20 Hz) is sent on the go path and is received on the return path within acceptable transmission and timing limits. Various timers like T8 (10-15 sec), T24(2sec), T25 (1-10 sec), T26 (1-3 min), T27 (4 min) are used for continuity check.

1.2.1.18. CCS7 Message Analyser

CCS7 Message Analyser is available in S/W 2_2_7.5_6 onward; similar to MF Signalling Analyser. This will monitor the messages between two exchanges when calls are made on #7 trunks. The analyser will display the sequence of forward and backward message transmitted between two exchanges as per call basis on the #7 trunks put on 'ISUP' observation using 'MOD-TRK-OBS' command. Reports can be seen by crp command 'DISPL-NSMA-RPT'.

1.2.1.19. New Strategy for Charging on Local PCO's

Local PCOs can be given access level as 'OG-UPTO-REG' now, thus allowing them to have access to '95' level routes. In this case, charging for local call will be done as per 'CRG-RTN' defined in 'SYS-PARAM' - 'PCO-MTR-LCL'. For route calls, charging will be done as per 'CRG-RTN' defined in route parameters.

1.2.1.20. AI Traffic Report

The format for AI traffic report output has been changed. Traffic reports have been further elaborated.

1.2.1.21. A new feature of Crystal Swing Detection in NSC had been implemented in S/W 2_2_7.7_6. Feature details and fault isolation strategy has been explained in Annexure-H. This feature facilitate exchange administrator to isolate faulty NSC card in the system.

1.2.1.22. Dialling by Equipment (DBE) Facility for Trunk Testing

Dialling by Equipment (DBE) is 'ORG-FAC' to be given to exchange administrator number. To test any trunk port during any time of the day, that particular trunk (TEN) is to be put on. 'DBE' observation by A `mod-lnk-



obs’. Then using allotted service code '683' calls can be originated on this trunk port.

1.2.2. Important Features of the Previous Links

1.2.2.1. ISDN

The ISDN switching functionality is offered for both types of customer interfaces viz Basic Rate Access (BRA) and Primary Rate Access (PRA). A new type of terminal unit, ISDN Terminal Unit (ISTU) has been introduced. The new cards supported in this frame are ICC (ISDN Concentrator Card), ITC (ISDN Terminal Controller), BRL (Basic Rate Line Card) and PRL (Primary Rate Line Card).

In the basic call processing, the following interworking scenarios are supported: ∗ ISDN-PSTN ∗ PSTN-ISDN ∗ ISDN-MF-ISDN ∗ ISDN-DECADIC-ISDN ∗ ISDN-ISUP-ISDN ∗ ISDN-ISUP-PSTN ∗ ISDN-MF-PSTN ∗ ISDN-DECADIC-PSTN ∗ PSTN-ISUP-ISDN ∗ PSTN-MF-ISDN ∗ PSTN-DECADIC-ISDN

1.2.2.2. Support for 800K BHCA

The CDOT DSS Operating System (CDOS) currently being used in the main processor complexes of the switch, is suitably modified to support the new hardware involving 68040 and 68302. With the induction of HPC in place of BPC in APU (AM), SCU (CM), BPU (BM), SUM (#7SU) and HMS in place of MSC & MSD in all the BMs of MAX-XL, the combined processing power is fully exploited to enhance the load handling capability of CDOT-DSS beyond 800 K BHCA.

With the induction of HPC as CPU in SUM (#7SU), the message handling capacity is increased upto 2000 messages/sec as against 625 messages/sec with BPC as CPU. Also, it supports up to 64 channels as against 32 with BPC as #7SU CPU, thereby doubling the availability of CCS7 links for connectivity.

Chapter 1

14 C-DOT DSS MAX

1.2.2.3. Subscriber Features & Supplementary Services The subscriber features have been implemented as per specifications of DOT/TEC document No. G/ASF-01/01 MAR 94. The control/invocation procedure has been standardised and charging for different services has been implemented so that these services can be released to subscribers with standard procedures for usage as well as billing by DOT as an operator. Invocation procedure as well as system limit for each service is listed subsequently in this section. DTMF subscribers as well ISDN subscribers will follow the procedure as specified in this section, unless it is specifically mentioned for ISDN subscribers. The decadic subscribers will follow the procedure by replacing * or # by '1' in the beginning only without dialling any other digit in place of # in the end. A DTMF subscriber can use both the options.

New Invocation Procedures for Subscriber Services

Number Identification Supplementary Services

Sl.No. Facility Type Activation Deactivation Remarks 1. CLIP NO NO 2. CLIR NO NO 3. CLIRO NO NO 4. MCID See Note-1 NO 5. MSN NO NO Only for ISDN 6. DDI NO NO Only for ISDN 7. SUB NO NO Only for ISDN 8. COLP NO NO Only for ISDN 9. COLR NO NO Only for ISDN 10. COLRO NO NO Only for ISDN

Call Offering Supplementary Service Sl.No. Facility Type Activation Deactivation Remarks

1. LH NO NO 2. CFU (fixed) *224# #225# See Note-2 3. CFU (SEL) *14 B# #15# See Note-3 $ 4. CFB (GRP) NO NO See Note-2 5. CFB (SEL) *220 B# #221# See Note-3 $ 6. CFNR (GRP) *228# *229# See Note-2 7. CFNR (SEL) *222 B# #223# See Note-3 $ $ For Centrex Subscriber dial Escape Code before number 'B'



Call Completion Supplementary Services

Sl. No. Facility Type Activation Deactivation

1. CW *18# #19# See Note-4

2. CH-WOR HOLD/RETRIEVE NO Only for ISDN

3. CH-WR HOLD/RETRIEVE NO Only for ISDN

4. TP SUSPEND/RESUME NO Only for ISDN

5. Hot Line (Timed) *20 B# #21# See Note-3 $

6. Hot-Line (Un-timed) NO NO $ For Centrex Subscriber dial Escape Code before number 'B'

Multiparty Supplementary Services

1. CNF-3PTY HSF *490 B # to add B $ HSF *493 # to toggle HSF *494 B # to drop B $ HSF *494 # to drop last HSF *492 # to activate

Only for PSTN

2. CNF-6PTY As above with difference that dial 491 in place of 490 to add a party B. Before adding any new party, *492 # should be used.

Only for PSTN

See Note - 5

$ For Centrex Subscriber dial Escape Code before number 'B'

Miscellaneous Supplementary Services

Sl.No. Facility Type Activation Deactivation Remarks

1. Dynamic Locking To Select the password *23 ABCD ABCD # To change the password *23 ABCD PQRS # To select current access *24 ABCD N # where N is the current access Level

N=0 for all allowed N=1 for O/G upto Local N=3 for O/G upto STD N=4 for O/G upto 10X N=5 for O/G upto 98/94/95 level

2. Alarm (Once) * 16 hh mm # #17 hh mm # See Note-6

3. Alarm (DLY) *226 hh mm # #227 hh mm# See Note-6

4. Queuing *686# #685# Only for PSTN See Note-7

5. Directed (DBE) call *681 TEN # for line *682 TEN B# for trunk $ *683 TEN # for Tone/Annc.

Only for Exchange Administrator for testing purpose.

Chapter 1

16 C-DOT DSS MAX

Sl.No. Facility Type Activation Deactivation Remarks

6. AOC-E & AOC-D NO NO Only for ISDN

7. 16 Khz for Home Meters

NO NO Only for PSTN See Note-8

8. Distinctive Ringing No No Only for PSTN subscribers $ For Centrex Subscriber dial Escape Code before number 'B'

Following Changes in SIF Service Codes are as per TEC requirements

SIF Old Code New Code

ABSENTEE_FIXED_NUM_ACT 28 498

ABSENTEE_FIXED_NUM_DEACT 29 499

3W_CONF 250 490

6W_CONF 251 491

ADD_CONF 252 492

CONF_TOGGLE 253 493

DROP_SEL_PARTY 254 494

Note - 1 : The PSTN subscriber can invoke the service just by HSF and ISDN subscriber can invoke the service by functional keys <Memory> <function> and then *680#.

Note - 2 : These features are not part of TEC/DOT specification/ requirement but very useful for the users. The feature permits the subscriber to divert the call to a group of pre defined numbers with flexibility to activate/deactivate the feature by the subscriber.

Note - 3 : The diversion no. B can be local, regional, STD or ISD and diversion will be activated based on the current dynamic access level of the subscriber. However, when the call is being diverted, the subscribed access barring is checked.

Note-4 : Invocation procedure for ISDN and PSTN subscribers are different. A ISDN subscriber uses functional keys to put the existing call on hold to receive another call in waiting. The PSTN subscriber has to invoke the feature by HSF and can toggle between two subscribers by using HSF repeatedly. Alternatively the call in waiting can be accepted by ISDN as well as PSTN subscribers by releasing/clearing the current conversation.



Note-5 : Invocation of six party conference is subject to the condition that CNF card is equipped in the BM in which subscriber is connected.

Note-6 : All the alarm requests can be cancelled by using the procedure #17#. Also, it is possible to request the operator to book the alarm call for the subscriber subject to the limitation that a maximum number of six alarms can be booked on a subscriber interface.

Note-7 : The facility is valid for ISDN interface when configured as Hunt Group. However an individual ISDN subscriber can subscribe to CW facility so that more than one calls can wait on an ISDN interface as specified/allowed by the administrator for that interface.

Note-8 : 25% of the total termination capacity can be used as 16 KHz ports subject to the equipage of compatible hardware.

1.2.2.4. Enhanced Traffic Reports

Monitoring of traffic flow has become one of the most important functions of network administrator. The traffic reports are used to monitor the network performance in terms of Call Completion Ratio (CCR) as well as to take the corrective measures to improve the CCRs by re-routing/re-dimensioning of network resources. The traffic reports in C-DOT DSS have been re-organised to generate following parameters : ∗ Separate Reports to monitor performance of PSTN and ISDN subscribers ∗ CCR for Local and O/G calls. ∗ Trunk Groups/Route Reports ∗ CCS7 Link performance reports ∗ Separate counters for individual line/ trunk circuits for monitoring the

performance of individual circuit. ∗ Details of call failures/ counters for failure analysis.

The organization of traffic reports help the administrator to monitor the exchange performance for different applications as local, ILT and TAX Configurations.

1.2.2.5. Revenue Metering and Detail Billing on Trunks

The new telecom policy enables private operators to offer basic and cellular telephony services in different telecom circles. The different operator exchanges will be connected amongst themselves and to the DOT controlled TAXs by trunks. There is a need that the various telecom service providers keep track of the revenues which are shared by them, on the basis of resource

Chapter 1

18 C-DOT DSS MAX

utilisation. With revenue metering on trunks implementation in C-DOT DSS, it can be configured as TAX with function as network's hand-over point. Online charging on per call basis is done on Trunk Groups (TGPs). At the end of every successful call, the charge meter of TGP is incremented by the applicable charge depending on the distance, type of day and call duration. Also information of number of successful calls on the TGP is maintained. A detailed billing record for every successful call can also be generated if required

A trunk group can be put under detail billing observation in each configuration of C-DOT DSS as Local/Tandem/TAX or ILT. However calling party identity will be part of detail billing records i.e. CAMA functions, only when exchange is configured as TAX or ILT. In case of revenue metering on ISUP trunks, the meter counters are incremented and detail bill records are made by incrementing the counters for actual charge units in both the cases of CHU and CHB.

All the trunk groups are associated with Local, STD and ISD meter counters. In case of Bothway trunk groups, two sets of counters (one each for I/C and O/G) are associated with each TGP.

1.2.2.6. Year 2000 (Y2K) Solution

Different commands have been modified to support 4 digit year field to solve the problem of year 2000.

1.2.2.7. Killer Trunk Implementation

As per definition/specification in the latest revised specifications of TEC, the concept of Killer Trunks has been implemented. The scope of definition has been improved by C-DOT to ensure unmanned operation of interconnecting resources and their maximum availability to carry the traffic. This feature will block the faulty junctions automatically and restore after monitoring the fault removal. This will be very useful feature at ILT and TAX, connecting the remote exchanges with limited resources.

1.2.2.8. Automatic Modification of Tariff Class to New Pulse Rate if Tariff Class gets Changed During the Call

As per definition of charging, in addition to distance and day type, the time is also a important factor to decide the charging. Accordingly, a day i.e. 24 hours are divided in different time zones. If a call progresses to the next tariff zone, the corresponding tariff class becomes effective for subsequent period.

1.2.2.9. 20 Digit Routing Capability

As per decision of ITU-T, the international numbering plan has been increased to 17 digits from 16 digits. To take care of future requirement, the routing capability has been increased to 20 digits.



1.2.2.10. Automatic Detection and Reporting of Large Duration Calls on Subscriber and Trunks

To meet the requirement of automatic reporting of large duration calls, it is possible to define the threshold for “Call Duration” as well as “Charge Units”. An exception report is generated for all the calls, crossing the threshold value. The exception report is generated on the OOD as well as printer. It is possible to retrieve the records at any time as these are also available in the disks as logs. The report include all the details, related to the call and required by the administrator, e.g. Calling Party Number, Called Party Number, Call Duration, Charge Units, Time of Originations etc.

1.2.2.11. Trunk Interface in RSU

Keeping in view the topology of telephony networks in the SSAs, the trunk interface (Analog or Digital) has been implemented in RSU. It is possible to parent the smaller exchanges at RSU itself. (Fig. 3.1) This results is advantages as listed below:

i) Avoid the requirement of separate media/connectivity for smaller exchanges upto main exchange.

ii) Efficient utilization of media, between RSU and Main Exchange by sharing the resources to carry the traffic to/from the network to smaller exchanges.

iii) In case of media failure between RSU and Main Exchange, Connectivity to Smaller Exchanges is maintained with RSU which may be installed at Block/Taluka level.

1.2.2.12. CAMA for Smaller Exchanges, Parented on R2 Signalling

With implementation of CAMA along with suitable MMI commands to generate the detail bill from SSA HQ for smaller exchanges/parented on R2 signalling, it is felt that C-DOT DSS is ideally suited for Indian Telecom Network, specifically for SSA Networks.

1.2.2.13. Enhanced Command DISPL-BILL-REC

The existing command has been enhanced to support the following functions: ∗ Display of billing records of Subscriber and Trunks ∗ Display of billing records of subscriber, belonging to specific level e.g. in

the numbering plan 548xxxx, it is possible display the records of 100 subscribers belonging to 54823xx.

∗ Display of TGP/Subscriber bill records with exceptionally higher charge units.

Chapter 1

20 C-DOT DSS MAX

∗ Display of CAMA records in the format of detail bill to facilitate the Administrator to generate the detail bills for smaller exchanges from a centralised place.

1.2.2.14. Command DISPL-XCHG-MTR to Monitor the Revenue Generation

It is possible to get the total number of charge units to monitor the revenue generation in the exchange. The flexible implementation of the command facilitate the Administrator to monitor the revenue generation for different application as Local, ILT or TAX. In case of an ILT exchange, it is possible to get the revenue figures with break up for the subscribers of its own exchange as well as revenues for parented exchanges, for which it is functioning as TAX.

1.2.2.15. Distinctive Ringing for Long Distance Calls

It is used to notify the caller that the incoming call is from distant place. The subscriber gets one type of ringing for Local calls and a different type of ringing for STD/ISD calls. The implementation of this feature is dependent on the type of Power Supply used in the exchange. In case of already commissioned sites, this feature will be available to the subscribers only after implementing the necessary modifications as the Power Supply Card and compatible TIC PROMs. No special procedure is required for activation, deactivation or usage of the failure and it is available by default to all the subscribers in the exchange.

1.2.2.16. Inbuilt MF Signalling Analyser

Due to integration of multiple technologies in the network along with co-existence of different interworking scenarios, the inbuilt signalling tracer is required to collect the details of call failures and take the corrective measures. The Multi Frequency Signalling Analysis is possible in C-DOT DSS on one or more than one trunk, simultaneously but a max. of 32 trunks at a time. The details of forward and backward signal are logged in IOP which can be displayed any time.

1.2.2.17. Threshold Alarms for PCMs between RSU and Main Exchange

In case of partial failure i.e one or more PCMs have failed, audio and visual alarm is raised for the attention of O&M personnel to take corrective measures. The exchange administrator can programme the parameters to control the raising and retiring of alarms.

1.2.2.18. 16 Tariff Classes to Support New Tariff Plan of TRAI

To meet the requirement of new tariff plan, the tariff classes have been increased to 16.



1.2.2.19. CCS #7 Signalling System

Signalling System #7 (SS7) is a common channel inter-exchange signalling mechanism that is intelligent, efficient, flexible and economical. The network comprising of switches with SS7 capability also provides the infrastructure for network features and services such as ISDN, Intelligent Network, Mobile Applications, Operation and Maintenance Applications, etc.

The system has a 4-layer architecture. Layer1 provides the Physical Layer, usually a 64 Kbps channel in a digital environment using PCM technique for transmission. Layer2 provides the Datalink Layer functionality and is responsible for reliable transmission of messages over a link without loss, duplication or mis-sequencing, through flow control and error correction mechanisms. Layer3 provide the Message Handling (discrimination and routing) and Network Management (Traffic, Link and Route Management) functionality ⎯ a part of the Network layer. All these comprise the Message Transfer Part (MTP). Level4 is for the User Parts. ISDN User Part (ISUP) is one that defines the logical sequence of events for a particular application using the services of the lower layers. ISUP defines the procedure for control of switched services in ISDN and covers both voice and non-voice (circuit-switched data) applications.

This implementation provides MTP along with ISUP functionality as in transit exchanges. Implementation of these layers is in conformance with ITU-T White Books. This implementation of SS7 is available on SBM as well as MBM configurations of MAX-L and MAX-XL. The parent switch can be configured as a Signalling Point (SP), Signal Transfer Point (STP), or as SP-cum-STP. The implementation is supported by incorporating necessary Man-Machine. The Call Processing software provides ISUP as well as the inter-working with DSS1, MF and Decadic signalling.

1.2.2.20. Network Synchronisation

The Network Synchronisation Controller (NSC) card in MAX-XL system is capable of synchronising its own clock to the network clock and supplying it to the exchange. This network clock is available through the DTKs coming from either a higher level or a peer level exchange and is extracted by the DTS card in a Digital Trunk BM before being given as input to the NSC cards in the CM complex. With this synchronisation capability, inter-exchange data transfer at very high rates can be achieved since the slips encountered will be very less. This implementation offers level2 network synchronisation capability in MAX-XL.

However SBM-RAX and MAX-L exchanges do not have NSC card inbuilt, therefore Network Synchronisation feature in these exchanges can be implemented by using C-DOT Network Synchronisation Equipment (NSE) as a standalone synchronisation unit.

Chapter 1

22 C-DOT DSS MAX

1.2.2.21. Calling Line Identity (CLI) and CAMA

C-DOT DSS supports CLI and CAMA functions for different applications as Local, Integrated Local cum TAX (ILT) and TAX.

When working as local exchange, it is possible to programme the parameters to decide that whether <Area Code> is to be part of Calling Line Identity information or not. If it is Yes, it is possible to programme the digit length as well as sequence of digits in the area code, prefixed to the subscriber directory number. In cases where all the digits are already forwarded in response to CLI request in the form of A4 signal, the additional one or more A4 signals are responded by 0. In other words, additional digits as 0 are suffixed to complete CLI information in the network.

In case of incoming terminating call when used as local exchange or incoming transit call when used as TAX, the number of digits to be requested from the preceding exchange can be programmed. Accordingly the no. of A4 signals are sent towards preceding exchange. It is also true when CAMA is set for one or more TGPs as well as in case of R2 to CCS7 interworking.

It is possible to programme the CLI information in the network for any specific requirement for different applications as Local, ILT / CLT or TAX.

1.3. NEW SOFTWARE RELEASE 2_2_1_9 (2007)

New S/W Release 2_2_1_9 has been introduced to provide three new features, in addition to all the existing features, supported in previous S/W release 2_2_1_6.

New features are :-

i) CENTREX GROUP implementation

ii) Special subscriber priority implementation

iii) New strategy for `ncbr’ & `tgbr’ files dumping in IOP.

Solution to all the existing problems of 2_2_1_6 and various enhancements have also been included in the new release 2_2_1_9.

1.3.1. CENTREX Groups introduced in 2_2_1_9 will have following features

∗ 500 CENTREX groups can be created in MBM, while only 10 CENTRAX groups are possible in SBM.

∗ Total number of Centrex Subscribers in all the Centrex groups should not exceed 5000. For SBM only '10' Centrex subscribers can be created.

∗ Only PSTN & V5.2 subscribers can become members of Centrex Groups. ISDN subscribers can not be added to Centrex groups.

∗ Centrex Feature will not work in 'RBMSA' mode.



∗ Centrex Group members should be from the same exchange and having same area code. RSU & AN-RAX subscribers of different 'SDCA' with different Area codes can not form part of the Centrex group of main exchange.

∗ Maximum '10' Centrex Groups can be put on traffic observation simultaneously.

∗ Complete flexibility is provided to charge or not to charge the intra-centrex group calls.

∗ Centrex group members will have three additional PABX features (i) Call Transfer (ii) Auto call back (iii) Abbreviated Dialling.

Dialing Patterns For New Features For Centrex Members

Service Usage Code

Automatic Call Back - Activation HSF 1294

Automatic Call Back - Deactivation HSF 1295

Call Transfer HSF 1296 ABBR

Following are the legends used in above table.

ABBR Abbreviated number of called Centrex member

HSF Hook Switch Flash ∗ New commands added for Centrex Group Features are:-

1. CRE-CNTRX

2. DEL-CNTRX

3. MOD-CNTRX-CHAR

4. REM-MEM-FRM-CNTRX

5. ADD-MEM-TO-CNTRX

6. DISPL-CNTRX-CHAR

7. DISPL-CNTRX-MTR

8. MOD-CNTRX-OBS

Note:

Refer Chapter 6 for details of Centrex Group Data Creation/Display & maintenance commands.

Chapter 1

24 C-DOT DSS MAX

1.3.2. Special Priority Implementation

Currently in the field, for India-One Plan (or any other similar plan) implementation, the requirement is that all outgoing traffic from INDIA-ONE subscribers should be carried over a new TGP towards the TAX. At TAX, for that New TGP, charging data is defined for INDIA-ONE plan (Say @ Rs.1/ min), the charging CHB/Charging pulses are sent towards the originating exchange. In future, there may be some other plan, which will have the similar requirement like India-one. So a general strategy has been designed to implement some Special Sub/TGP Priorities to seize desired OG TGP for outgoing calls routing. Special Priority range is from 15 to 19.These priorities will be used internally for TGP seizure only & will not be floated over the network.(Refer Chapter 6 for feature implementation details).

1.3.3. Strategy for Detailed Billing Records (CDR) Generation and Transfer

Bharat Sanchar Nigam Limited (BSNL) is having countrywide presence with over 40 million subscriber base. BSNL has proposed to implement next generation state-of- Art Detail Billing Records (CDR) based Customer Care and Convergent Billing System. This can be achieved with deployment of Centralized Integrated Billing Systems with supporting technological and communication infrastructure.

To implement this, Detail Billing Records (CDRs) are to be obtained from different type of Network elements capable of generating billable information, using centralized Mediation System.

In BSNL Network , 90% of the switches are of CDOT Technology. To meet the above requirement, there is a need to generate 100% Detail Billing Records for all the completed calls. Generation of 100% Detail Billing Records is supported in the existing & New software releases of C-DOT. These Detail Billing Records need to be automatically transferred to the Billing center preferably in real time mode.( refer Chapter 7 for implementation details ).

1.3.4. Problem Fixes in 2_2_1_9 Over 2_2_1_6(7.7)

1. IOP Synchronization and Duplex working has been stabilized.

2. Special Service routes (say 198 etc.) mapping for RSUs & AN-RAX using MOD-RBMNRM-CONFIG & CRE-ANNRM-CONFIG is working properly in all scenarios.

3. ISDN PABX problem of wrong CLI (Always CLI of PDN) and calls of more than 12 digits failure has been solved.



4. No Dial Tone & Voice over ISND BRI subscribers in new ISTU frames has been solved by changing ITC/ICC problems.

5. 4 digit level routes working properly for RSU subscriber in new release.

6. When Annc. card made OOS-OPR, then on Dynamic locking/unlocking, congestion tone is given instead of PIT/FIT. This problem has been fixed.

7. BW TGP traffic reports will now get transferred during IOP synchronization.

8. Reversal will be extended to AN-subscriber created with line-typ=CCB-CRD.

9. Proper announcement will be fed to subscriber of C-DOT after dialling a non-existing route via ISUP trunks (earlier busy tone was given).

1.3.5. Enhancements in S/W Release 2_2_1_9(2.11)

1. During Creation of Subscriber data, default value of the parameter "ACC-BAR" will be IC-NOT-BRD/OG-UPTO-REG/BS12 (Earlier it was IC-NOT-BRD/OG-UPTO-LCL/BS12).

2. In 2_2_1_9, 'BC' group has been splitted into two separate groups, i.e. 'BC' (for ncbr only) and TG (for tgbr files only). This will ensure a separate back-up of ncbr and tgbr files, as files size has increased after default CDR generation for all level '9' calls.

3. Total no of TGPs in MBM has been reduced from 512 to 300, while it is same in case of SBM.

1.3.6. Enhancements & Problem Fixes in S/W release 2_2_1_9 ( 2.13)

1. During Subscriber data creation by ‘cre-sub’ command, parameter ‘DET-BLG’ will accept ‘LCL-BLG’ as default value.

2. As level ‘950’ has been allotted for Mobile Services, calls on this rout are now allowed ( Blocked in previous release)

3. As levels 90 & 96 have been allotted for Mobile Services, these levels will be accessible to Subscribers having ACC-BAR as ‘OG_UPTO_REG’ (Earlier these levels were accessible to SUBs having OG_UPTO_LCL). CDRs for these levels will be generated by Default . Meter increment will be done in STD counters. In general , levels 90 & 96 will be treated at par with levels 91,92,93,94,95,97,98,99.

4. Access Network Interface Status change Report will be available through CRP command ‘ displ-ood-log’ by option:

Chapter 1

26 C-DOT DSS MAX

REP-NAME : 205 ( AN - STS – CHG -REP)

5. Meter Reading spurt on Subscriber No. having Subs_Index = 0 was observed if calls were made on any other Subscriber (in that BM) with activated call diversion. This problem has been solved.

1.3.7. Enhancements and Problem Fixes in S/W release 2_2_1_9 (2.16)

1.3.7.1. As a requirement for implementation of Mobile Number Portability (MNP) in the Telecom Network, Charge Band Number (CHB) information is to be made available in the CDRs for Subscribers as well as TGPs. This feature has been implemented in S/W 2219(2.16). Charge Band Information in CDRs for different type of calls is explained below:

1. Intra-exchange (Local) Calls: For Local calls, system will check 'CHB' Number mapped to the 'CRG-RTN' used for changing of the Local calls. Normally crg-rtn=21 (180 sec) is used for charging of local calls. CHB=11 is associated for crg-rtn=21. Then Charge-Band=11 will be shown in Bill Record of such calls. An extra field "Charge-Band" has been included in the Output format of the command "displ-bill-rec".

2. For Outgoing Calls following cases may arise :-

a) If CRG-RTN in a particular route is 'prd-lcl', then CHB number associated with this crg-rtn will be dumped in the CDR.

b) If CRG-RTN in the route is 'prd-tax', then CHB number received from TAX (TGP on CCS7-signalling) will be dumped in the CDR.

c) If CRG-RTN in a the route is 'prd-tax" & TGP is on MOD-R2 signalling then only metering pulses will be received. In this case an invalid CHB=255 will be dumped in the CDR.

d) If CRG-RTN in the route is prd-tax', & TGP is on CCS7 signalling with SIG-INFO=ISUP-CRG-CHU then CHB will not be received. So an Invalid CHB=255 will be dumped in the CDR. Hence, always use option "ISUP-CRG-CHB".

Warning!

In S/W 2_2_2.16_9, all the relevant Charge Band Nos. (CHB Nos) must be mapped to the correct CRG-RTNs using "mod-chb-crg", otherwise system may go for frequent booting.



1.3.7.2. New Unix 11.7 has been released which will be required wherever 146 GB hard disk is to be replaced in IOP. (However for the existing low capacity 1.2GB/2.5GB/4.5GB/9.5GB Hard disks, Unix 11.6 can also be used.)

1.3.7.3. PCMs going to 'OOS-TRANS' state because of media flicks & not recovering to normal state automatically even after removal of the flicks. This problem has been solved. With new implementation, such PCMs will become 'INS-FREE' automatically after 5 minutes of removal of flicks in the media.

1.3.7.4. Problem of delay in 'COPY-OUT' of ED/BD/BC due to large block size of various files has been solved by implementing following:

1. Now 'trnsf' gp files (iotmsg*/iotind*) will not be part of 'ed.grp'. Backup of trans files can be taken separately by 'COPY-OUT' command for [fgp] : trnsf;

2. History files ioh* have been removed from 'ED' group. No backup is required for this group.

3. Commercial Bill Record files 'iocbil*' have been removed from 'BC' & 'BD' groups. These files are already available in ED group.

1.3.8. Enhancements & Problem Fixes in S/W Release 2_2_1_9 (2.22)

1.3.8.1. Problem Fixes

1). During HGP creation, PDN defined with TEN-BW getting partial ringing, Problem has been solved.

2). The invalid digits (like * or #) dialled either in the exchange-code OR in the digits dialled after exchange-code will fail the call with number-unobtainable error.

3) Calls not successful in case MNP is taken by IDEA subscriber’s. ISTU tics going oos-sus, when call dialled from ISDN PABX to IDEA mobiles. This problem is solved in this release.

4) After MNP implementation, AM recovery noticed if LSB towards TAX not created. Also on interruption of LS towards SSTP (TDM), all Voice Ckts going to S7-bsy state & not restoring even after restoration of LS status to activated & available. The problem has been solved in this release.

5) Sometimes error printouts regarding data file “apbmss” start coming on Active IOP console Terminal. Part-init to AM was the only solution. This problem has been solved.

Chapter 1

28 C-DOT DSS MAX

1.3.8.2. Enhancements/Changes

1) The check in the MOD-LIN-STA command for the OOS-line status is removed, so that even if the subscriber is INS the command is allowed. So now one can make a subscriber BNP-ANNC from normal without forcing the terminal OOS.

2) In order to support the CDR based billing feature for subscribers, there is requirement to generate the CDRs for all the local calls & Centrex calls irrespective of the value ORD-BLNG, CNTX-BLNG or LCL-BLG for subscribers. Now CDR will be generated for all types of call for all subscribers by default (No administrator Control).

3) CLIR facility removal (None of the CLIR facilities will be available). A new Error string introduced as “This facility is not allowed to Registered/Deregistered.”

4) Changes in speech monitoring to display CLIP differently at Monitoring Number. MOD-SMON-LIST is changed to include one additional parameter “MON-CLIP” that indicated the CLIP Info (either OBSERVED or CONNECTED) associated with the Monitoring Dir. No.


Chapter 2.

Software and Hardware Status

2.1. SOFTWARE STATUS

2.1.1. Media Details

2.1.1.1. Status for SBM-RAX

S. NO MEDIA SIZE

1. Unix 11.7 11890 Blocks

2 BAC/SC2_2_1_9 134756 Blocks

3. CPC/SC2_2_2.22_9 40097 Blocks

4. BMDC/SC2_2_2.10_9 18133 Blocks

2.1.1.2. Status for MAX-L/MAX-XL

S. NO MEDIA SIZE

1. Unix 11.7 11890 Blocks

2. BAC/MC2_2_1_9 144786 Blocks

3. CPC/MC2_2_2.22_9 43298 Blocks

4. BMDC/MC2_2_2.10_9 17532 Blocks (MAX-L) 17538 Blocks (MAX-XL)

2.1.1.3. Retrofit Utility Cartridges

S. NO Retrofit Utility Cartridges SIZE

1. EDRETRO 2219 1153 Blocks

2.1.2. PROM Status

There are different types of PROM used in different controllers. In addition to the size of memory which is clearly identified by the PROM Type/Number,

Chapter 2

30 C-DOT DSS MAX

the speed is also one of the critical parameters. The speed of different types of PROMs, is specified below:

PROM Type Speed 27C256 ≤ 200 nsec 27C512 ≤ 200 nsec 27C010 ≤ 120 nsec 27C040 ≤ 90/100 nsec

It is advised to use the PROMs with access time as recommended.

2.1.2.1. IOP S. No. Card Type Position PROM (ID) Checksum PROM TYPE

1 FOR IOP-VH

APC-VHC358/O-S00

U22

LVHCMON7.0

2F37

27C040

2.1.2.2. ADP S. No. Card Type Position PROM (ID) Checksum PROM TYPE

1. APC-SMC122/T-S03

FOR SBM-RAX ONLY

U7 LADP101XSC2_2_2.2_9 83DA 27C256

2. APC-SMC122/T-S03

FOR MAX-L /MAX-XL

U7 LADP101XMC2_2_2.2_9 0FE7 27C256

2.1.2.3. Central Module in MAX-XL S.

No. Card Type Position PROM (ID) Checksum PROM TYPE

1. APC-BPC441/O-S02 FOR 300K BHCA

U45 LAPC2XXXMC2_2_2.2_9 2C27 27C010

U43 HAPC2XXXMC2_2_2.2_9 E103 27C010

APC-HPC393/O-S01 FOR 800K BHCA

U55 LAPC3XXXMC2_2_2.2_9 0934 27C040

2. APC-HMS394/O-S01 U19 LMSC3XXXMC2_2_1_9 2FCE 27C010

SOFTWARE AND HARDWARE STATUS


S. No.

Card Type Position PROM (ID) Checksum PROM TYPE

3. APC-BPC441/O-S02 FOR 300K BHCA

U45 LSSC2XXXMC2_2_2.2_9 401B 27C010

U43 HSSC2XXXMC2_2_2.2_9 7D99 27C010


U55 LSSC3XXXMC2_2_2.2_9 53EE 27C040

4. APC-CHD370/F-S01 (Used on APC-NSC369/H-A01)

U43 LNSC1XXXC2_2_1_9 51E8 27C256

APC-CHD370/F-S01 (Used on APC-NSC369/H-A01)

U42 HNSC1XXXC2_2_1_9 1CB5 27C256

2.1.2.4. Central Module in MAX-L S. No. Card Type Position PROM (ID) Checksum PROM TYPE

1. APC-CPU019/F-S04 U79 LAPC1XXXMC2_2_2.2_9 F181 27C512

OR U82 HAPC1XXXMC2_2_2.2_9 98F7 27C512

APC-CPU019/F-S05 U64 LAPC1XXXMC2_2_2.2_9 F181 27C010

U66 HAPC1XXXMC2_2_2.2_9 98F7 27C010

2. APC-MSC014/F-S07 U66 LMSC1XXXXC2_2_1_9 1B9F 27C256

U67 HMSC1 XXXXC2_2_1_9 F931 27C256

3. APC-CPU019/F-S04 U79 LSSC1 XXXMC2_2_2.2_9 88A7 27C512

OR U82 HSSC1 XXXMC2_2_2.2_9 FDB9 27C512

APC-CPU019/F-S05 U64 LSSC1 XXXMC2_2_2.2_9 88A7 27C010

U66 HSSC1 XXXMC2_2_2.2_9 FDB9 27C010

2.1.2.5. PROM Status for BM-L / BM-XL

Analog Terminal Unit (ATU)

S. No. Card Type Position PROM (ID) Checksum PROM TYPE

1. APC-TIC002/T-S08 U56 LTIC108XXC2_2_1_9 B758 27C256

OR U62 HTIC108XXC2_2_1_9 0270 27C256

APC-TIC002/F-S10 U75 CTIC110XXC2_2_1_9 0A14 27C512

2. APC-TTC051/T-S06 U3 LTTC105XXC2_2_1_9 OR

LTTC106XXC2_2_1_9

303E D32F

27C256

Chapter 2

32 C-DOT DSS MAX

S. No. Card Type Position PROM (ID) Checksum PROM TYPE

3. APC-ANN078/T-S03 U9 LANC1XXXXC2_2_1_9 9E86 27C256 (200 ns)

OR U9 LEAC1XXXXC2_2_1_9 00EB 29F040-PLCC

APC-EAC371/H-S00 U18 HEAC1XXXC2_2_1_9 BAD4 29F040-PLCC

OR U7 LASV1XXXL2_2_1_9 8E1D 29F040-PLCC

APC-ASVA27/H-S001

U6 HASV1XXXC2_2_1_9 DCB4 29F040-PLCC

Note :

Two additional EPROMs are to be provided in 'ANNC' Card at U72 & U75 positions For Hindi/Eng. Annc. For other Bi-lingual Announcements. Refer Annex-C.

ISDN Terminal Unit (ISTU) S. No. Card Type Position PROM (ID) Checksum PROM Type

1. APC-ICC536/H-S01 U35 HICC1XXXXC2_2_2.2_9 451E 27C040

U29 LICC1XXXXC2_2_2.2_9 1DEB 27C040

2. APC-ITC535/H-S01 U3 HITC1XXXXC2_2_2.2_9 FBAC 27C040

U4 LITC1XXXXC2_2_2.2_9 04A9 27C040

3. APC-BRL537/H-S01 U60 HLCC1XXXXC2_2_1_9 E2A8 27C040

U50 LLCC1XXXXC2_2_1_9 0C73 27C040

4. APC-PRL538/F-S01 U24 HLCC1XXXXC2_2_1_9 E2A8 27C040

U23 LLCC1XXXXC2_2_1_9 0C73 27C040

Signalling Unit Module (SUM) for CCS7 S. No. Card Type Position PROM (ID) Checksum PROM Type

1. APC-TUC046/T-S03 U85 HTUC101XXC2_2_1_9 F62F 27C256 U68 LTUC101XXC2_2_1_9 E5CC 27C256 2. APC-BPC441/O-S02

for SBM RAX with 32 signalling links

U45 LNPC2XXXSC2_2_2.2_9 DAFE 27C010

U43 HNPC2XXXSC2_2_2.2_9 6E38 27C010

APC-HPC393/O-S01 for SBM RAX with 64 signalling links

U55 LNPC3XXXSC2_2_2.2_9 59B9 27C040



S. No. Card Type Position PROM (ID) Checksum PROM Type

3. APC-BPC441/O-S02 MAX-L and

U45 LNPC2XXXMC2_2_2.2_9 D6C8 27C010

MAX-XL with 32 Signalling Links

U43 HNPC2XXXMC2_2_2.2_9 5A3E 27C010

APC-HPC393/O-S01 in MAX-L / MAX-XL 64 Signalling Links

U55 LNPC3XXXMC2_2_2.2_9 357E 27C040

4. APC-SHM473/H-S01 U17,U20 LPHC102XXC2_2_1_9 0306 27C040

For 32 Signalling Links with BPC

U5,U10 HPHC102XXC2_2_1_9 D2A1 27C040

APC-SHM473/H-S01 For 64 Signalling Links with HPC

U17,U20 LPHC202XXC2_2_1_9 F5B0 27C040

U5,U10 HPHC202XXC2_2_1_9 2B3F 27C040

Note : The SHM card cannot be used interchangeably with BPC and HPC. The ECN in the form of Firmware changes in EPLD contents are mandatory to make the cards compatible. Also BME cards should be made compatible by correcting the jumper settings.

Digital Terminal Unit (DTU) S. No. Card Type Position PROM (ID) Checksum PROM Type

1. APC-TUC046/T-S03 U85 HTUC101XXC2_2_1_9 F62F 27C256 U68 LTUC101XXC2_2_1_9 E5CC 27C256 2. APC-DTC067/T-S04 U3 LDTC101XXC2_2_1_9 F25A 27C256

3. APC-DTS066/T-S04 or

U19 LDTS101XXC2_2_1_9 EBEC 27C256

APC-DTS495/F-S00 U15 LDTS101XXC2_2_1_9 EBEC 27C256

Time Switch Unit (TSU) S. No. Card Type Position PROM (ID) Checksum PROM Type

1. APC-MFC043/F-S06 OR APC-MFC043/F-S08

U71 U67

LMFC106XXC2_2_1_9 TONE PROM for CCTRX

5310 FE7F

27C256 27C512

APC-MFC043/T-S04 U63 LMFC104XXC2_2_1_9 33BF 27C256

2. APC-MSC014/F-S07 U66 LMSC1XXXXC2_2_1_9 1B9F 27C256

OR U67 HMSC1XXXXC2_2_1_9 F931 27C256

APC-HMS394/0-S01 U19 LMSC3XXXMC2_2_1_9 2FCE 27C010

3. APC-TGA077/T-S02 U14 LTGC1XXXXC2_2_1_9 E0B5 27C256

Chapter 2

34 C-DOT DSS MAX

S. No. Card Type Position PROM (ID) Checksum PROM Type

U45 LTGC1XXXXC2_2_1_9 3EAC 27C256

4. APC-TSC008/F-S06 SBM/MAX-L

U24 LTSC1061XC2_2_1_9 996A 27C256 Note 1

U23 HTSC1061XC2_2_1_9 A13D 27C256 Note 1

APC-TSC008/F-S04 U24 LTSC1041XL2_2_2_9 8C71 27C256

SBM/MAX-L U23 HTSC1041XL2_2_2_9 A7BD 27C256

APC-TSC008/F-S06 Only for MAX-XL

U24 LTSC1062XC2_2_1_9 64D4 27C256 Note 1

U23 HTSC1062XC2_2_1_9 02B4 27C256 Note 1

APC-TSC008/F-S04 U24 LTSC1042XL2_2_1_9 46EC 27C256

Only for MAX-XL U23 HTSC1042XL2_2_1_9 D469 27C256

5. APC-TIC002/T-S08 U56 LTIC108XXC2_2_1_9 B758 27C256

OR U62 HTIC108XXC2_2_1_9 0270 27C256

APC-TIC002/F-S10 U75 CTIC110XXC2_2_1_9 0A14 27C512

6. APC-ETS477/H-S01 For sixteen PCMs APC-RTS457/H-S02 For four PCMs

U9 U3

LETS1XXXMC2_2_1_9 LRTS1XXXMC2_2_1_9

98AD 4710

68HC705C9P 68HC705C9

Note : 1.

In case of PROMs for TSC, it depends on the BM application and not it’s type. The checksum for TSC will be same for BM-L as well as BM-XL if used as SBM-RAX or as BM/RSU of MAX-L Similarly the checksum for TSC PROM will be same for BM-L as well as BM-XL if used as colocated BM or RSU BM of MAX-XL.

Base Processor Unit (BPU) in BM for MAX-L/MAX-XL S. No. Card Type Position PROM (ID) Checksum PROM TYPE

1. APC-CPU019/F-S04 U79 LBPC1XXXMC2_2_2.2_9 739A 27C512

U82 HBPC1XXXMC2_2_2.2_9 D0A9 27C512

APC-CPU019/F-S05 U64 LBPC1XXXMC2_2_2.2_9 739A 27C010

U66 HBPC1XXXMC2_2_2.2_9 D0A9 27C010

APC-BPC441/O-S02 U43 HBPC2XXXMC2_2_2.2_9 7731 27C010

FOR 300K BHCA U45 LBPC2XXXMC2_2_2.2_9 B12E 27C010


U55 LBPC3XXXMC2_2_2.2_9 7DF2 27C040



Base Processor Unit (BPU) for SBM-RAX S. No. Card Type Position PROM (ID) Checksum PROM Type

1. APC-CPU019/F-S04 U79 LBPC1XXXSC2_2_2.2_9 8DE8 27C512

U82 HBPC1XXXSC2_2_2.2_9 B944 27C512

APC-CPU019/F-S05 U64 LBPC1XXXSC2_2_2.2_9 8DE8 27C010

U66 HBPC1XXXSC2_2_2.2_9 B944 27C010

APC-BPC441/O-S02 U45 LBPC2XXXSC2_2_2.2_9 EE2C 27C010

U43 HBPC2XXXSC2_2_2.2_9 AEE6 27C010

APC-HPC343/0-S01 U55 LBPC3XXXSC2_2_2.2_9 FDB7 27C040

PROM Status of V5.X Unit (VU) S. No. Card Type Position PROM (ID) Checksum PROM Type

1. APC-TUC046/T-S03 U85 HTUC1XXXXC2_2_1_9 F62F 27C256 U68 LTUC1XXXXC2_2_1_9 E5CC 27C256 2. APC-BPC441/O-S02

for SBM RAX with 32 signalling links

U45 LVPC2XXXSC2_2_2.2_9 C382 27C010

U43 HVPC2XXXSC2_2_2.2_9 BACA 27C010

APC-HPC393/ O-S01 for SBM RAX with 64 signalling links

U55 LVPC3XXXSC2_2_2.2_9 176C 27C040

3. APC-BPC441/O-S02 MAX-L and

U45 LVPC2XXXMC2_2_2.2_9 BDD3 27C010

MAX-XL with 32 Signalling Links

U43 HVPC2XXXMC2_2_2.2_9 9AF3 27C010

APC-HPC393/O-S01 in MAX-L / MAX-XL 64 Signalling Links

U55 LVPC3XXXMC2_2_2.2_9 F7AF 27C040

4. APC-SHM473/H-S01 U17,U20 LPHC102XXC2_2_1_9 0306 27C040

For 32 Signalling Links with BPC

U5, U10 HPHC102XXC2_2_1_9 D2A1 27C040

APC-SHM473/H-S01 For 64 Signalling Links with HPC

U17,U20 LPHC202XXC2_2_1_9 F5B0 27C040

U5,U10 HPHC202XXC2_2_1_9 2B3F 27C040

Chapter 2

36 C-DOT DSS MAX

2.2. CHANGE OF EPROMS REQUIRED FOR S/W RELEASE 2_2_2.22_9 OVER EXISTING RELEASE 2_2_7.7_6

Deliverable S/W 2_2_7.7.6 S/W 2_2_2.11_9 S/W 2_2_2.13_9 S/W 2_2_2.16_9

ADC √ X X X

BM-XL/BM-L

TICS08/S10 TUC (HTUC-U85) DTS DTC TOGC (LTGC-U14) TTC ANNC MFC S04 (U63) / S06/S08 (U71 & U67) BPC (CPU-S04/S05) BPC-S02 HPC TSC MSC/HMS ASV

√ √ X X √ X X √ √ √ √ x x √

} } } }

} X } } } } } } } } }

} } } } }

} X } } } } } } } } }

} } } } }

} X } } } } } } } } }

SUM

BPC-S02 HPC-S01 SHM (With BPC) SHM (With HPC)

√ √ √ √

X

X

X

VU

BPC-S02 HPC-S01 SHM (With BPC) SHM (With HPC)

√ √ √ √

X

X

X

CM-L

CPU-S05 (APC) CPU-S05 (SSC) MSC

√ √ x

X

X

X

CM-XL

BPC-S02 (APC & SSC) or HPC-S01 ( " ) NSC HMS

√ √ X X

X

X

X

ISTU

ICC ITC BRL/PRL

X

X

X

X

Unix BAC CPC BMDC ED/BD RETRO RGEN

√ √ √ √ √ √

√ X √ X X √

√ X √ X X √

√ X √ X X √


Chapter 3.

Software Retrofit Philosophy and Pre-Retrofit Checks

3.1. GENERAL CONSIDERTIONS

It is expected that the person, who is going to attempt this retrofit, should go through this document before starting the retrofit procedure.

1. The 2_2_1_9 retrofit procedure has to be carried out over previous software releases 2_2_7.7_6. Refer chapter 4 for detailed procedure.

2. Exchange Data Retrofit Utility Cartridge

For S/W Retrofit 2219, 'ED', 'BD' and 'BC' of old S/W 2216(7.7) will be used. In S/W 2219, structure of many Data files is changing. To incorporate these changes over the existing data files of 2216, Retrofit Utility cartridge will be required. Same way billing Data files (ncbr??, tgbr??, locctr?? & stdctr?? etc) will also be retrofitted to make these compatible with new S/W 2219. Thus existing exchange data & subscriber meter Reading will remain same.

Note :

* It is important to inform TRA section about change in the file structure, in case, bills are being generated using some Billing Generation Package. Package will have to be upgraded. 2_2_1_9 billing file structure can be obtained from C-DOT for the upgradation of billing package.

3. In S/W Rel. 2219, maximum no. of TGPs in MBM system has been reduced to 300 (earlier it was 500). Now all the TGPs having number >300 have to be deleted and re-created with any free TGP number <300.

For SBM, maximum limit has not been changed.

4. After retrofit process has been completed with one IOP, do not rush to load other IOP with new S/W deliverables of 2_2_1_9. Watch the system stability for one day.

5. Please make sure to arrange PROMs for spare cards also.

Chapter 3.

38 C-DOT DSS MAX

6. The other IOP is to be loaded with complete S/W 2_2_1_9 and two copies of S/W deliverables, cartridges of UNIX, BASE, PATCH and BMDC are to be prepared from the master set.

3.2. PRE-RETROFIT CHECKS

• All the duplex units in the system are fine, i.e., the system is able to work with either copy as active and other standby and they respond correctly to all switch maintenance commands. This should be tested for IOPs also.

• All simplex units (TTC, ANNC & MFCs) are fine and respond to switch maintenance commands with either of the higher duplex units as active.

• System alarms are working fine. • All input/output devices (cartridge and floppy drives) of C-DOT IOPs are fine.

This can be verified by copying out data from one IOP and copying the same in other IOP.

• All deliverable corresponding to old release are available at site. • Latest ED/BD backups are available. • Take list of the BNP-DISC NOs from active IOP. • Ensure that the new PROMs for all controllers cards and SPARES are

available as per card versions being used in the system. • Note down characteristics of all the operator terminals created in each IOP,

as these will be required to be added again after the retrofit. • BP cables for BM-L, BM-XL & SUM should be available at site.

3.3. CONTACT NOS. OF C-DOT CONTROL ROOM

At Delhi : 011-26802815, 26802816, 26598282 Fax: 011-26598562

At Bangalore 080-25119999 Fax: 080-25119251

Go to C-DOT Help Desk through C-DOT Helpline Portal (www.cdothelpline.ernet.in)


Chapter 4.

Retrofit Procedure From 2_1_7.7_6 to 2_2_1_9

4.1. PRE RETROFIT ACTIVITIES

• Stop all the Traffic Reports & remove all entities (Subs, TGPs, Trks, Routs, AIs etc) from any type of observations.

• Make sure that New S/W 2219 deliverables (Unix, BAC, CPC, BMDC), Retrofit Utility, RGEN utility cartridges & all the required EPROMS as per Chapter 2, are available at site before starting the retrofit activity.

• Stop executing Data base modifications from Active IOP, once Retrofit activity has started in the other IOP.

• If there are any TGPs having No >300, then these TGPs have to be deleted & re-created with any free TGP No <= 300 by running TGP retrofit utility. For this, prepare a list of old TGP Nos(>300) & New free TGP Nos(<=300) & TGP Names to be allocated.

• Preserve ED of 2216(7.7) and last one year "BC" Back-ups for records. • Do mock retrofit exercise one day before the actual retrofit date as

per procedure given in para 4.2.

Success of mock retrofit will ensure that actual retrofit gets completed without any problems and as per schedule.

4.2. MOCK RETROFIT PROCEDURE – ONE DAY BEFORE THE RETROFIT DATE

4.2.1. Running of “check.sh” utility in IOP having S/W 2_2_1_6

1. Bring SBY IOP (Say IOP-0) to warm-start level using “init-iop: 2, 1; command.

a) In IOP-0 make directory "retro2219" in /u/admn as follows : IOP5C> mkdir /u/admn/retro2219 IOP5C> cd /u/admn/retro2219 IOP5C> pwd (Should show /u/admn/retro2219 )

Chapter 4

40 C-DOT DSS MAX

b) Copy the Retrofit Utility 2219 in IOP-0 having S/W 2_2_1_6 by following commands: Insert “Retrofit Utility 2219” cartridge in IOP-0. IOP5C> cpio -icv <$TAPE

IOP5C> chmod 755 *

2. IOP5C> check.sh This utility will verify sanity of ED files on which retrofit 2219 has to be done.In case no errors are shown, message “Utility for ED files Checking Successfully over” will appear at the end. In this case, proceed to carry out Mock Retrofit activity as given below in step 4.2.2.

However if errors of the type

(1) core dump (2) can not open

(3) Error in getting index-info (4) Error in key info

are observed , the Utility will fail with message “Utility for ED files Checking failed” and one log file “err.log” will be generated. In such a case ,corrective action has to be taken for the corrupted ED files before carrying out mock retrofit. Contact C -DOT ,Delhi or Bangalore for on-line correction if possible. Once files have been corrected & check.sh utility is successfully run , proceed to carry out mock retrofit exercise. In case on-line correction is not possible, then ED cartridge has to be brought to C-DOT Office for further action.

4.2.2. Mock Retrofit Procedure

1. Bring SBY IOP (Say IOP-0) to warm-start & then to cold-start level using “init-iop:2,1; and ‘init-iop:1,1;’ commands. Load complete software (Unix, BAC, CPC, BMDC) of release 2_2_1_9 in it.

Shutdown / reboot & set-site-id. Load Rgen 2219 Cartridge in this IOP by standard procedure.

2. a) In IOP-0 make directory "retro2219" in /u/admn as follows :

IOP5C> mkdir /u/admn/retro2219 IOP5C> cd /u/admn/retro2219 IOP5C> pwd (Should show /u/admn/retro2219 )

b) Copy the Retrofit Utility cartridge and give execute permission as follows:

Insert “Retrofit Utility 2219” cartridge in IOP-0.

IOP5C> cpio -icv <$TAPE

RETROFIT PROCEDURE FROM 2_1_7.7_6 TO 2_2_1_9


Various files will be copied & Total Blocks should be shown.

IOP5C> chmod 755 *

3. On Active IOP-1 give command <del-fgp-file:,ioh; and then take ED backup by 'Copy-out' command.

4. In IOP-0 (having 2219 S/W) , COPY-IN the ‘ed’ backup taken in step 3,with RES-OPT = OVR-REL

5. Running of TGP mapping Utility (For MBM Exchange only) to map TGP Nos >300 to the free TGP Nos <=300 as per list prepared during pre-retrofit activities :-

IOP5C> cd /u/admn/retro2219 IOP5C>pwd (should show /u/admn/retro2219) IOP5C>retro_tgp.sh

This utility is interactive & prompts various inputs to be given by the user.

Important Inputs being: Enter Old TGP Num: Enter New TGP Num (Less than 301] : Enter New TGP Name

It will show the enterd values & ask “Do you want to proceed with these values

Y/N ? Give Y here if the values are correct.

After modification, Utility prompts for Exit /Continue(0/1) for the next

TGP Number. Once all the listed TGP Numbers have been mapped as per list, exit(0) from the utility .Watch for the message !!! TGP UTILITY OVER !!!

Verify “displ-tgp” & “displ-tgp-rout” commands for the modified TGPs only after completing step 6(b).

6. On IOP-0, follow the ED retrofit procedure as mentioned below:

a) IOP5C> cd /u/admn/retro2219

IOP5C> pwd (should show /u/admn/retro2219)

b) Execute the "retro_ed" for retrofitting ED files as follows:

IOP5C> retro_ed

Chapter 4

42 C-DOT DSS MAX

Retrofitting messages will appear for all files to be retrofitted. There should be no errors shown. Watch for the exact message "RETROFIT UTILITY(ED) SUCCESSFULLY OVER".

c) Verification of ED Retrofit :

Some commands are being given here for verifying the successful execution of retrofit utility. Output of these commands Prior to Running Retrofit and After Running the Retrofit should come out to be same except new fields related to Centrex Feature/Special Priority.

1) DISPL-SUB-LIST of all BMs (Verify Special Priority & Centrex Number Field)

2) DISPL-SUB from various BMs (Sample check for SPL-PRI, Centrex No & Abbreviated No.)

3) DISPL-COM-BILL (Sample check & verify for Centrex Counters)

4) DISPL-TGP (Sample check for New TGP nos & names)

5) DISPL-ALL-ROUT

6) DISPL-ALL-FAC

7) DISPL-HGP

8) DISPL-ROUT-CHAR (Sample Check)

9) DISPL-SYS-PARAM (Important System parameters)

10) DISPL-TGP-LIST (New TGP Nos & Names)

11) DISPL-XCOD

12) DISPL-SMON-LIST

13) DISPL-ALL (for PDDN, PDDI, System DIR NOs)

RGEN Utilities can also be used for verification.

d) A log file "retro_ed.log" will be formed in the current directory.

If Utility gets terminated "UNSUCCESSFULLY", then do not proceed to carry out Final Retrofit Exercise. Contact C-DOT Control Room for further action.

Warning : Don't run "retro_ed" utility again if it gets terminated "UNSUCCESSFULLY"



4.3. FINAL RETROFIT PROCEDURE

4.3.1. On the day of Retrofit, do following during day time:

1. Bring SBY IOP (Say IOP-0 ) to warm-start and then to cold-start level using ‘init-iop:2,1’ & ‘init-iop:1,1;’ commands. Load complete software (Unix, BAC, CPC ,BMDC) of release 2_2_1_9 in it .

Shutdown / reboot & set-site-id. Load rgen 2219 cartridge in this IOP by standard procedure.

2. a) In IOP-0 make directory "retro2219" in /u/admn as follows :

IOP5C> mkdir /u/admn/retro2219

IOP5C> cd /u/admn/retro2219

IOP5C> pwd (Should show /u/admn/retro2219 )

b) Copy the Retrofit Utility cartridge and give execute permission as follows:

Insert “Retrofit Utility 2219” cartridge in IOP-0.

IOP5C> cpio -icv <$TAPE

Various files will be copied & Total Blocks = 1152 should be shown.

IOP5C> chmod 755 *

3. In IOP-0 , preserve files iotmsg*, iotind* in a new directory "misc" & copy bcr.grp & bdr.grp by giving following commands :-



IOP5C>script1

IOP5C> cd $PRCDATAP/misc

IOP5C>ls –ls (It should list 6 files of iotmsg* & iotind* )

4. On Active IOP-1 give command <del-fgp-file:,ioh; and then take ED backup. Take BC backup of last Two months (or current Billing Cycle) using COPY-OUT command. After this do not give any Exchange data modification or updation Commands.

5. In IOP-0 (having 2219 S/W) , COPY-IN the ‘ed’ backup taken in step 4,with RES-OPT = OVR-REL

6. IN IOP-0 ,COPY-IN “BC” backup as taken in Step 4 with

Chapter 4

44 C-DOT DSS MAX

RES-OPT = OVR-REL

FGP = bcr {Frm date-> to date}

7. On IOP-0 , Restore earlier saved iotmsg* & iotind* files as follows:


IOP5C> pwd ( should show /u/admn/retro2219 )

IOP5C> script2

8. Running of TGP mapping Utility (For MBM Exchange only) to map TGP Nos >300 to the free TGP Nos <=300 as per list prepared during pre-retrofit activities.

Note: This step is not required if such TGP Nos. do not exist

Warning: In case such TGP’s exist and this step is skipped by mistake, although system will recover, all the Trunk BMs & AM will go for frequent booting.


IOP5C>pwd ( should show /u/admn/retro2219 )

IOP5C>retro_tgp.sh

This utility is interactive & prompts various inputs to be given by the user.

Important Inputs being:

Enter Old TGP Num :

Enter New TGP Num (Less than 301] :

Enter New TGP Name :

It will show entered values and ask "Do you want to proceed with these values (Y/N). Give 'Y' here, if the values are correct.

After modification, Utility prompts for Exit/Continue (0/1) for the next TGP Number.

Once all the listed TGP Numbers have been mapped exit from the Utility. Watch for the message !!!TGP UTILITY OVER!!!

Verify "displ-tgp" & "displ-tgp-rout" commands for the modified TGPs after completing step 9.

9. On IOP-0, follow the ED retrofit procedure as mentioned below:

a) IOP5C> cd /u/admn/retro2219




b) Execute the "retro_ed" for retrofitting ED files as follows:

IOP5C> retro_ed

Retrofitting messages will appear for all files to be retrofitted.

There should be no errors shown. Watch for the exact message

"RETROFIT UTILITY(ED) SUCCESSFULLY OVER".

c) Verification of ED Retrofit :

Some commands are being given here for verifying the successful execution of retrofit utility. Output of these commands Prior to Running Retrofit and After Running the Retrofit should come out to be same except new fields related to Centrex Feature/Special Priority.

1) DISPL-SUB-LIST of all BMs (Verify Special Priority & Centrex No. field)

2) DISPL-SUB from various BMs ( Sample check for SPL-PRI, Centrex No. & Abbreviated No. fields)

3) DISPL-COM-BILL (Sample check)

4) DISPL-TGP (Sample check for New TGP Nos. & names if any))

5) DISPL-ALL-ROUT

6) DISPL-ALL-FAC

7) DISPL-HGP

8) DISPL-ROUT-CHAR ( Sample Check)

9) DISPL-SYS-DIRNO

10) DISPL-SYS-PARAM ( Important System parameters)

11) DISPL-TGP-LIST

12) DISPL-XCOD

13) DISPL-SMON-LIST (If any No. on SMON observation)

DISPL-ALL (for PDDN, PDDI & System Directory No.)

RGEN Utilities can also be used for verification.

A log file "retro_ed.log" will be formed in the current directory.

Chapter 4

46 C-DOT DSS MAX

Warning : Don't run "retro_ed" utility again in case of failure.

10. In Growth mode, give command <del-fgp-file:, alm; Copy-out the Retrofitted ED Back-up & lable the same as ED2219.

11. Running of BC Retrofit Utility

On IOP-0 , run the Retrofit utility retro_bc for `BC’ Group files (ncbr*, tgbr*, frmt* etc.) of the last billing cycle copied in Step-6 as follows:


IOP5C> pwd ( Should show /u/admn/retro2219 )

IOP5C> retro_bc



"Retrofit Utility( BC) Successfully Over" .

Warning: Don't run “retro_bc" utility again in case of failure.

A log file "retro_bc.log" will be formed in the current directory.

If this offline utility gets terminated "Unsuccessfully", then intimate to C-DOT control room alongwith log file "retro_bc.log"

Verification: Verify some Sub & TGP detail bill records by "DISPL-BILL-REC" command. Also verify in $DUMPP, whether ncbr & tgbr files have been splitted into hourly files.

i.e. files of date 7-7-2007 can be verified by following commands:

IOP5C>cd $DUMPP IOP5C> ls -ls nc*070707.dat (Should show 24 hourly files) IOP5C>ls -ls tg*070707.dat (Should show 24 hourly files)

'BC' & 'TG' Backups: Copy-out the 'BC' & 'TG' backups and label as BC (2219) & TG (2219).

4.3.2. On the day of Retrofit, do following during night Hrs (after 20:00Hrs):

a) From Active IOP-1, note down counters dump time of BM1 by giving commands



IOP5C>ls -ls *ctr00* (to display locctr00* & stdctr00* files)

10 minutes before the Dump time, block all the Traffic towards TAX Exchanges and 'POI' directions. In case of CCS7, all PCMs having Signalling Links (LSs) can be forced OOS, while in case of MOD-R2, both OG and I/C TGPs are to be blocked. This is required to ensure that no discrepancy is observed in CDR's of POIs.

After 5 minutes of Dump time, take Current Day 'bd' backup using COPY-OUT command with

FGP = bd (Do not mention any dates).

After 'bd' backup, bring IOP-1 to warm start by <init_iop : 2,1;

b) In IOP-0 , copy-in 'BD' Back-up taken in step a) with

RES-OPT= OVR-REL FGP = bdr

c) Running of BD Retrofit Utility

- Warning : Since BD Retrofit takes care of current day ncbr & tgbr files only, it is utmost important to finish this activity on same day before 00 Hrs.

- Time taken is from 1 to 3 Hrs depending upon No. of BMs.

In IOP-0, run retro_bd on Current day Billing Data files as follows:

IOP5c> cd /u/admn/retro2219

IOP5c> retro_bd



"RETROFIT UTILITY(BD) SUCCESSFULLY OVER".

'BD' Backup: Copy-out the retrofitted 'BD' backup and label as BD (2219).

A log file "retro_bd.log" will be formed in the current directory

Warning : Don't run “ retro_bd" utility again in case of failure & utility gets terminated "Unsuccessfully" consult C-DOT Control Room for further action.

Chapter 4

48 C-DOT DSS MAX

4.3.3. Initialization/Booting up the System with 2219

It is recommended to follow the under mention steps of Initialization/ Booting up the system with 2219:

1. Before power-on of AM/CM after changing the PROMs, must ensure that all co-located BMs’ TSUs should be switched off.

2. For all RBMs either remove the data cables from CM end or remove the U-Link from DDF.

3. Once AM & CM recover and ADP shows critical alarms of all BMs/RBMs, change the EPROMs of BMs one-by-one and recover them after Code/Patch/Data loading.

4. Also for RBMs, change the EPROMs and then before switch-on the RBM, connect the data cable or put the U-Link at DDF.

If the above mentioned steps are not followed and if the AM/CM recovered in new S/W version and any BMs/RBMs are remain connected and powered-on with older version frequent “File Id Error” message come on console terminal. As a result none of the BMs will start code loading even after changing new S/W proms.

5. Displ-sys-all for all the BMs & bring 'OOS' units if any to ins-act/sby status.

6. Verify MFC channel status by `displ-srv-status’ in all the BMs & bring these ins-free if found oos-sys

7. Note down OMR of the modified numbered TGPs in Step 4.2.1.

4.4. POST-RETROFIT CHECKS

The retrofit is now complete and the system can be observed for normal functioning. Following checks may be performed :

a) Dial tone on at least one port of all the TUs.

b) Dial tone on at least one DTMF subscriber in each BM.

c) Line to Line calls

e) O/G calls

f) Proper updation of meter readings and detail bill record. Also verify that detail bill of SUBs & TGPs show proper 'CHB' Nos.

g) Proper announcements



h) All the duplex unit except TICs/TUCs in the system are fine i.e. system is able to work with either copy as active or standby.

i) All simplex unit are fine and respond to maintenance commands with either higher units as active.

j) Create one Centrex Group with few members. Verify various type of calls and all the features relevant to Centrex Group members.

Observe the system stability for about 6 hours and then proceed to next setup.

4.5. RECOVERY ACTION

In case the retrofit 2_2_1_9 is not successful, do following :

i) Bring IOP-0 to warm start level by init-iop : 2,1; command.

ii) Switch off all PSUs in all frames i.e. AM, CM, BMs and LMs.

iii) Replace EPROMs in relevant cards with previous S/W version PROMs and jack in the cards. Replace PROMs in SUM & ISTU frame also.

iv) Power on all the frames of the system

v) Give INIT-IOP:5,1 from IOP-1 (having previous version data) to bring it INS-ACT and thus giving code load to system.

vi) Replace EPROMs of previous version in the left out cards.

4.6. RETROFIT COMPLETING ACTIVITIES

1. Change EPROMs on other copies of TICs/TUCs which are in jacked out condition and having previous version PROMs. Jack in these cards and make them INS-SBY one by one.

2. Generate two sets of S/W deliverables of 2_2_1_9 using the cartridge duplication procedure listed in ANNEXURE-B.

3. Load complete S/W in IOP-1, using one of the two sets of deliverables, prepared at the site.

4. Bring IOP-1 inservice from IOP-0 by executing CRP commands: <put-swu-oos : iom, iop-1; <put-swu-ins : iom, iop-1;

5. Change the EPROMs in the spare cards and test these cards. 6. Implement password management in the IOPs if already being used. 7. Add terminals and operators in the IOP-1 also. 8. Load latest 'RGEN/CMD' utility in SBY IOP-1.

Chapter 4

50 C-DOT DSS MAX

9. Put all the desired entities (TGPs, Routes, Subs etc.) on Traffic Observation and start the traffic reports.

4.7. PROCEDURE TO VIEW SUBSCRIBERS & TGPS DETAIL BILL RECORDS THROUGH RGEN UTILITY

Before running rgen utilities 'ncbr' & 'tgbr', hourly files of nchhddmmyy.dat & tghhddmmyy.dat have to be combined to form a single day file by following procedure:-

IOP5X>cd $DUMPP

IOP5X>cmb_ncbr

Enter the date as "DD-MM-YY" & give Enter

This will form a single day file as 'ncbrddmmyy'.

IOP5X>rgen ncbr (To view Subscriber Detail Bill record of that day)

Similarly to get TGP detail bill records, do following:

IOP5X>cmb_tgbr

Enter the date as "DD-MM-YY" & give Enter

This will form a single day file as 'tgbrddmmyy'.

IOP5X>rgen tgbr (To view TGP Detail Bill record of that day)

Note: Commands 'cmd_ncbr' & 'cmb_tgbr' work only for single day.

4.8. TIME ZONES AND TARIFF CLASSES FOR HOLIDAY & NORMAL DAY

Definition of Day Types 1 & 2 has been shown in Table 4-1, while Charge Band Number (CHB) to Pulse Rate association has been shown in Table 4.2.

Table-4.1

DAY-TYP=1 (Holiday) START TIME END TIME TARRIF CLASS ROUTING INFO

0000 0700 3 NOT-BARRED



DAY-TYP=2 (Normal/Working day) START TIME END TIME TARRIF CLASS ROUTING INFO




START TIME END TIME TARRIF CLASS ROUTING INFO





4.9. MODIFY DEFINITION OF DAY TYPE 1 AND 2 AS PER TABLE I, USING COMMAND ‘MOD-TYP-DAY’

There is change in the definition of Day Types 1 and 2.

Use command MOD-TYP-DAY to modify Day Types 1 & 2 as following:-

a) Mod-typ-day Day-typ = 1 Prd-trf = 0000-3-2 & 0700-2-2 & 2300-3-2 execute

b) Mod-typ-day Day-typ = 2 Prd-trf = 0000-3-2 & 0700-2-2 & 0730-1-2 & 2230-2-2 & 2300-3-2

Table-4.2

Charge Band Number (CHB) to Pulse Rate association Charge Band Number Purpose Pulse Rate (Sec)

0 Non-metered -- 1 Unit Fee (Fixed) -- 11 Local (Intra-Circle) 180 12 Internet 450/900 20 Inmarset Calls 150msec 21 Inmarset Calls 260 msec 27 Rest of the World 4 33 Sri Lanka 6 34 USA, UK, CANADA 10 38 Pvt Operator Basic, WLL, Mobile

Intra Circle 45

39 European Continent, Singapore, Thailand, Malaysia, Indonesia, Hongkong

7.5

41 Inter-circle Basic & WLL Mobile >50KM, Intercircle all cellular

30

42 Intra circle BSNL Basic & WLL 60

Chapter 4

52 C-DOT DSS MAX

Charge Band Number Purpose Pulse Rate (Sec) >50 KM, Intra circle BSNL Mobile, Inter-circle Basic 0-50 KM

43 Local BSNL, WLL, Intra-circle & WLL 0-50 KM, Intercircle BSNL Basic 0-50KM

90

Note: Verify 'CHBs' list from Leading 'TAX' exchange.

4.10. IMPLEMENTATION OF DISTINCTIVE RINGING FEATURE

1. There may be two types of PSU-I (with ringer) being used in TERMINAL UNIT.

i) For PSU036/T-S16 (old PSUs)

ECN (cut and straps) will be required to be done in all the PSUs. Detail can be taken from C-DOT web-site.

ii) For PSU 036/A09 (New PSUs)

EPROM (PSU E2D6) has to be changed in the child card, at U11 position.

2. IC-TGP from TAX should be made. ‘TTAX’ type.

3. Modify system parameter SPL-RNG = 1

4. Initialize the system to softstart level using <INIT-SYS:, SOFT-START; command.

Verify distinctive ringing for I/C TAX calls


Chapter 5.

Retrofit Procedure from S/W 2_2_1_9 (2.11) / 2_2_1_9 (2.13)/2_2_1_9 (2.16) to 2_2_1_9 (2.22)

5.1. CHANGE OF S/W DELIVERABLES IN 2_2_2.22_9 OVER 2_2_2.11_9/ 2_2_2.13_9/2_2_2.16_9

Deliverables Over S/W 2_2_2.11_9 / 2_2_2.13_9/2_2_2.16_9

UNIX X

CPC √

5.2. RETROFIT PROCEDURE FOR C-DOT EXCHANGES HAVING S/W 2_2_2.11_9/2_2_2.13_9/2_2_2.16_9

5.2.1. List of Deliverables

Refer chapter 2 (para 2.1.1.) for changed block size of the CPC

5.2.2. Pre Retrofit activities

1. Take ED,BC,TG ,BD Backups.

2. Note down Characteristics of the icc ports & operator's accounts as these have to be created again.

3. IOPs should be in duplex working & interchange of IOPs should work.

5.2.3. Procedure

1. Bring Stand by IOP ( Say IOP-0) to warm start level by <init-iop:2,1; command & then to cold start level by <init-iop:1.1; command.

2. Give reset to IOP. Load complete S/W (Unix,BAC, CPC2.22 ,BMDC) of 2_2_2.22_9 release. Shutdown, reboot & “set-site-id’.

Load latest RGEN cartridge using standard procedure. After loading RGEN, 'CDR Transfer Utility Files' will be automatically loaded in

Chapter 5

54 C-DOT DSS MAX

/u/instalces directory. Intall "IOP-FT UTIL" by standard commands (# ./INST-IOP-FT). Also create 'cdr' operator using standard procedure.

3. ‘Copy-in’ the latest ED backup in this IOP-0 having 2_2_2.22_9 S/W :-

VOL-NAME : edDdMm

RES-OPT : < >

:

:

FGP : ed

4. ‘Copy-in’ ‘BC’ & ‘TG’ backups of last two months( or Billing Cycle) in IOP-0.

5. Once slack traffic hour starts (after 22:00 Hrs),take latest ‘BD’ backup without any date. `Copy-in’ this ‘BD’ in IOP-0.

Shutdown & reboot the IOP to bring it to warm-start level.

6. Bring active IOP-1 to warm-start by <init-iop:2,1; command.

7.. In IOP-0, give command <del-fgp-file: , alm;>

8. Give <init-iop:5,1; from IOP-0 having S/W 2_2_2.22_9 .Once this IOP becomes ins-act ,give Power-on to system by <init-sys:, power-on; command. AM,CM ,all BMs & SUM will go for Code/patch/data loading. Now Give reset to VP-0 & VP-1 cards in all the VU frames, so that VUs also recover after Code/Patch loading.

9. Once complete system has recovered ,verify “displ-ood-log’ for Rep-Name: 182 & confirm that all the Modules have gone for Power-on/Patch-init. Verify VUs recovery level by option Rep-Name: 202;

10. Post Upgradation Checks

The retrofit is now complete and system can be observed for normal functioning as listed below:-

a) Verify Dial tone on atleast on one port of all TUs covering DTMF subscriber also.

b) Local calls & meter updation.

c) O/G calls on various routes, specially routes 950x.

d) Verify that Routes 90x & 96x are available from SUBs having ACC-BAR as OG_UPTO_REG (& not by OG_UPTO_LCL).

RETROFIT PROCEDURE FROM S/W 2_2_1_9 (2.11) / 2_2_1_9 (2.13)/2_2_1_9 (2.16) TO 2_2_1_9 (2.22)


e) Updation of Detail bills of SUBs & TGPs, with proper 'CHB' number.

f) Verify ‘mod-line-sta’ command working without making DIRNO as OOS-OPR.

11. Retrofit Completing Activities a) Load complete S/W 2_2_2.22_9 in IOP-1 also. b) Synchronize IOP-1 by standard procedure c) Add terminals & operators in both the IOPs d) Implement password management in IOPs if any. e) Load latest RGEN cartridge in this IOP. Install ‘IOP-FT-UTIL’

by standard commands (# ./INST-IOP-FT). Create 'cdr' operator using standard procedure.

Warning: Ensure that all the relevant (defined in routes & 'Sub-Crg') CRG-RTNs are mapped to the corresponding CHBs, otherwise system may go for frequent booting.

C-DOT DSS MAX 56

Chapter 6.

Details of Centrex Feature Implementation

6.1. MAIN HIGHLIGHTS OF CENTREX FEATURE OFFERED IN THIS RELEASE ARE :

• 500 CENTREX group can be created in MBM., while only 10 CENTREX group can be created in SBM

• Total number of Centrex subscribers in all Centrex groups in MBM not to exceed 5000 . In SBM total no of Centrex Subs can be 10.

• Only PSTN & V5.X subscriber will be allowed as members of Centrex. ISDN subscribers cannot be a member of a Centrex group.

• Centrex Feature will not function in RBMSA mode. • Centrex groups members should be in the same exchange & having same

area code. Subscribers of RSU which are in different SDCAs having different area codes than main exchange can not make part of the same Centrex groups.

• It is possible to generate traffic statistics separately for each centrex group. However maximum number of Centrex groups that can be put under observation is 10.

• Flexibility exists to charge or not to charge the intra Centrex calls. • Centrex group members will have three additional features

1. Call transfer

2. Auto call back

3. Abbreviated Dialling

6.2. DETAILS OF CENTREX FEATURE IMPLEMENTATION.

6.2.1. Feature Definition

The CENTREX feature is used to provide a virtual PABX for a group of subscribers. The attributes of a Centrex are shared by all its members.

DETAILS OF CENTREX FEATURE IMPLEMENTATION


A Centrex can have landlines PSTN subscribers of one exchange as its members.

6.2.2. In addition to other facilities provided to normal subscribers, this release provides following facilities to Centrex members –

Abbreviated dialing

Each member of a CENTREX shall be administratively assigned an abbreviated number. The abbreviated number of a Centrex member shall be unique to that CENTREX. Members of a CENTREX can call each other by dialing the abbreviated code of the destination number.

Automatic Call Back (ACB)

If a Centrex member calls another Centrex member which is already in conversation (busy), then the calling member may book automatic call towards that subscriber. Whenever the called member becomes free, call will be initiated towards both the members.

Call Transfer

A Centrex member can transfer a call landing on it to another centrex member using this facility.

In order to complete the call transfer, the former should disconnect itself after intimating the new member.

6.2.3. Following are the system limits for X2219 release.

Table 1: System limits for X2219 release

Entity Limit

Number of CENTREX Groups in system 500

Total number of Centrex members in system (MBM Config.) 5000

Maximum number of CENTREX under observation 10

6.3. CALL HANDLING STRATEGY FOR DIFFERENT TYPE OF CENTREX CALLS

6.3.1. Intra - Centrex Call

On going offhook, a centrex member shall be fed a new dial tone named as Centrex Dial Tone (CDT). The CDT is having frequency of 400 Hz and is continuous. In order to make intra centrex call, a centrex member shall dial the abbreviated number of the called party. In case the called party is

Chapter 6

58 C-DOT DSS MAX

having CLIP facility, then abbreviated number of the calling party shall be displayed in the CLI device.

6.3.2. Calls To Public Network By Centrex Members

In order to provide access to public network, each CENTREX shall be having an escape code. Each CENTREX can have a different escape code. The escape code of a CENTREX will be defined during its creation. On getting CDT, a Centrex member can make call towards public network by dial ing the escape code of the CENTREX, provided the subscriber as well as the CENTREX is having access barring required for the outgoing call. The calling member shall be fed normal dial tone on dialing escape code. After getting normal dial tone, a Centrex member can make calls outside the CENTREX. In case the called party is having CLIP facility, then full directory number of Centrex member shall be displayed in CLI device.

6.3.3. Calls Landing On Centrex Members From Public Network

In case Centrex member is having CLIP facility, then full directory number of calling party shall be displayed in CLI device.

6.4. CHANGE IN USAGE OF EXISTING FACILITIES BY CENTREX MEMBERS

6.4.1. SIF Invocation By Centrex Members

A Centrex member can invoke different Subscriber Initiated Features by dialing different SIF codes after CDT itself. While activating or using those features in which directory numbers are to be specified, a Centrex member can specify either an abbreviated number or a directory number of the public network. In case a directory number of public network is being specified, the escape code of the Centrex is to be dialed before the directory number. The facilities in which a subscriber can dial an abbreviated number of a Centrex member or a directory number of a public network are, 3 way conference, 6 way conference, drop selected party, hot line, absentee to selected number, diversion on busy to selected number and diversion on no answer to selected number. For other features, the procedure of activation, deactivation and usage is same as for normal subscribers.

6.5. CHARGING AND BILLING

6.5.1. Charging of intra-Centrex calls

There shall be a provision of charging / not charging intra- centrex calls of a CENTREX Group. In order to specify the charging for intra Centrex calls, a charge rate number shall be associated with every CENTREX. In case the intra Centrex calls of a CENTREX are to be charged, then a charge rate



number with desired initial charge, periodic charge and charge period can be associated with that CENTREX during its creation and can be modified later on.

6.5.2. Modes of Billing

6.5.2.1. Bulk Billing

Separate billing counters are being maintained for intra Centrex calls. The charging counters are being stored separately for each member of the CENTREX. There shall be a provision to display the charging counters of a CENTREX also. The bulk billing reports generated by the system shall contain the counters for intra Centrex calls also.

6.5.2.2. Detailed Billing

There shall be a provision to generate detailed billing records for all the calls, including intra Centrex calls, made by the members of a Centrex.

6.5.2.3. Commercial Billing

Commercial billing records shall be generated for a subscriber when that subscriber is added into a CENTREX and when the subscriber is removed from a CENTREX. Also, commercial billing records shall be generated for a CENTREX on Centrex creation, deletion, modification.

6.6. TRAFFIC OBSERVATION

There shall be a provision to put a CENTREX under observation. Following shall be possible when a CENTREX is put under observation.

Dumping of CDRs of each call originated by members of the CENTREX under observation

Dumping of CDRs of each call terminating on the members of the CENTREX under observation

Periodic dumping of counters corresponding to calls originating from and calls terminating on a CENTREX

Traffic counters shall be maintained for calls originated by members of a CENTREX and for calls terminating on members of a CENTREX

6.7. CHANGES IN MAN-MACHINE INTERFACE

6.7.1. Introduction Of New Commands

Two new command classes "Centrex Management Update Class" and "Centrex Management Display Class" has been introduced. Two new

Chapter 6

60 C-DOT DSS MAX

commands DISPL-CNTRX-MTR and MOD- CNTRX-OBS have been introduced into billing and traffic command classes respectively.

Following are the commands being introduced in the centrex management command classes.

6.7.2. Centrex Management Update Class

CRE-CNTRX

ADD-MEM-TO-CNTRX

MOD-CNTRX-CHAR

REM-MEM-FRM-CNTRX

DEL-CNTRX

6.7.3. Centrex Management Display Class

DISPL-CNTRX-CHAR

Following are the new commands introduced in existing command classes.

6.7.4. New Billing Commands

Following new billing command is being introduced.

DISPL-CNTRX-MTR

6.7.5. New Traffic Commands

Following new traffic command is being introduced.

MOD-CNTRX-OBS

6.7.6. Description Of Parameters

Parameter Description

ABBR-NO This parameter describes the abbreviated numbers for the intra-Centrex calls. This accepts numeric values in the range 0 to 9999.

ABBR-LEN This parameter describes the length of the abbreviated numbers for the intra-Centrex calls This accepts numeric values in the range 1 to 4.

ACC-BARR This parameter describes the maximum access barring levels allowed for the members of the centrex being created. It has 3 subfields -



First subfield can have values INCMNG_NOT_BAR & INCMNG_BRRD.

Second subfield can have values OG_UPTO_10X, OG_UPTO_LCL,

OG_UPTO_REG, OG_UPTO_NAT, OG_UPTO_INT.

Third subfield can have values ALL_BS, BS12 and BS3. Sets and ranges are not allowed.

ADD-ABBR This parameter describes the identity of Centrex member which additionally has to be put under observation. This will accept two subfields Centrex id and abbreviated number.

First subfield shall accept numeric values between 1 to 500.

Second subfield shall accept numeric values between 0to 9999.

This parameter accepts set of values.

ADD-CTRX This parameter describes the Centrex number of the Centrex which additionally has to be put under observation. All the members of this CENTREX shall be put under observation. It shall accept numeric values between 1 to 500.

This parameter accepts sets and ranges of values.

ATND-NUM This parameter describes the attendant position for the

CENTREX. This accepts numeric values in the range 0 to 9999.

CALL-STA This parameter describes the call status of the CEN- TREX. This parameter accepts alphanumeric values. It shall accept values NRM-LIN, BNP-ANNC and BNP- DISC.

CDR-TYP This parameter describes the type of CDR which are to be displayed via DISPL-CDR command. This parameter accepts alphanumeric values CLLNG, CLLD, DIV and SPLFTY. This parameter accepts set of values.

COM-TYP This parameter describes the commercial billing record type. This parameter accepts alphanumeric values. The possible values of this parameter are SUB, TGP and CTRX

Chapter 6

62 C-DOT DSS MAX

CTRX-NUM This parameter describes the centrex number to be created in the exchange. This parameter accepts the numeric values in the range 1 to 500. Sets & ranges not allowed. This instance is used in CRE-CNTRX, DEL- CNTRX, DISPL-CNTRX-CHAR and MOD-CNTRX- CHAR.

CTRX-NAM In first instance, this parameter describes the centrex name to be created in the exchange. This parameter accepts the alphanumeric values of length 10.

CTRX-NAM In second instance, this parameter describes the centrex name. This parameter accepts the alphanumeric values. Default value is ALL. In case its value is NONE, the command shows the list of the subscribers which are not member of any centrex. This instance is used for DISPL- SUB-LIST.

CRG-RTN This parameter describes the charge rate number for the intra-centrex calls for the created centrex. This parameter accepts numeric values in the range 0 to 127.

CTRX-OBS This parameter shall accept alphanumeric values. It shall accept value OBS-ORG and OBS-TRM.

CTX-ABBR This parameter describes the identity of centrex member. This will accept two subfields Centrex number and abbreviated number.


Second subfield shall accept numeric values between 0 to 9999.


DEL-ABBR This parameter describes the identity of centrex member which has to be removed from observation. This will accept two subfields centrex number and abbreviated number.


Second subfield shall accept numeric values between 0 to 9999.




DEL-CTRX This parameter describes the centrex number of the CENTREX which has to be removed from observation. All the members of this CENTREX shall be removed from observation. This parameter shall accept numeric value in the range 1 to 500. This parameter accepts sets and ranges of values.

DEL-ALL This parameter describes whether all entities are to be removed from observation. This parameter accepts alphanumeric values. Possible values are YES,NO.

BLG-TYP This parameter describes the detailed billing-type. It can accept the values ORD-BLG, LCL-BLG, CTRX-BLG.

DIR-ABBR This parameter describes the directory number & the corresponding abbreviated number. It consists of two subfields separated by a ’-’.

Possible values of DIRNO : 200 to 8999999

Possible values of ABBRNO : Numeric values in range 2 to 9999


ESC-CODE This parameter describes the escape code for the CEN- TREX. This parameter accepts numeric values of length 1, in the range 0 to 9. This parameter is optional with default value 0.

OBS-PRD This parameter describes the Observation Period for which CENTREX has to be put under observation.

ORG-CFAC This parameter describes the originating facilities attached with the CENTREX being created. It can accept a set of alphanumeric values. It shall accept the values NO-ORG and AUTO-CBAK.

REV-TYPE This parameter describes the revenue type. It accepts alphanumeric values. The possible values of this parameter are SUBS, TAX and ILT.

STP-DTE This parameter describes the Stop Date for putting CEN- TREX under observation. It has three subfields separated by ’-’.

First subfield specifies the day of month and accepts numeric values between 1 to 31.

Chapter 6

64 C-DOT DSS MAX

Second subfield specifies the month and accepts numeric values between 1 to 12.

Third subfield specifies the year and accepts numeric values between 1970 to 2036.

The default value of this parameter is NONE.

STP-TME This parameter describes the Stop Time for putting CENTREX under observation. It has 2 subfields separated by ’:’.

First subfield specifies the hour and accepts numeric values between 0 to 23.

Second subfield specifies the minute and accept numeric values between 0 to 59.

The default value of this parameter is NONE.

TRM-CFAC This parameter describes the terminating facilities attached with the CENTREX being created. It can accept a set of alphanumeric values. It will accept the values NO-TRM and of CALL-TRNSFR.

6.8. DETAILED DESCRIPTION OF NEW COMMANDS

6.8.1. CRE-CNTRX

This command shall be used to create a new CENTREX having characteristics given in the input fields.

Input form

CRE-CNTRX CREATE A NEW CENTREX

CTRX-NUM :

CTRX-NAM :

[ESC-CODE] : 0

ABBR-LEN :

[BLG-TYP] : ORD-BLG

[MTRG-CLS] : NRM-MTR

[CRG-RTN] :

[ATND-NUM] : NONE



[ORG-CFAC] : NO-ORG

[TRM-CFAC] : NO-TRM

[ACC-BARR] : INCMNG_NOT_BAR-OG_UPTO_10X-ALL_BS

DIR-ABBR :

Validation and Remarks

1. This command shall be allowed in ONLINE mode only, as is done in hunt group management class.

2. The Centrex with the given CTRX-NUM should not be already created in the system.

3. The Centrex with the given CTRX-NAM should not be already created in the system.

4. The Centrex name CTRX-NAM should have alphanumeric characters that should not start or end with ’-’ .

5. The ESC-CODE shall not be 1.

6. Every directory number in the list of DIR-ABBR should be made OOS-OPR before making it a member of the CENTREX.

7. Each of the Directory number in the DIR-ABBR list shall be a subscriber of self-exchange.

8. Any of the Directory number in the DIR-ABBR list shall not be a frozen number.

9. Any of the Directory number in the DIR-ABBR list shall not be a system directory number.

10. Each of the Directory number in the DIR-ABBR shall be an ordinary subscriber, a PDN number or a member directory number.

11. Any of the Directory number in the DIR-ABBR shall not belong to any other CENTREX.

12. Either directory number or the abbreviated number or both in the combination of every DIR-ABBR should not be repeated.

13. None of the abbreviated numbers in DIR-ABBR should start with the ESC-CODE digit.

14. Length of the abbreviated number in the DIR-ABBR should be of ABBR-LEN.

Chapter 6

66 C-DOT DSS MAX

15. If the Directory number in the DIR-ABBR is a PDN, then all the member directory numbers of the PDN should be present in the set of entries for DIR-ABBR.

16. If MTRG-CLS is NRM-MTR, then the CRG-RTN should be existing in the system.

17. ATND-NUM shall be same as the abbreviated number given in one of the entry of DIR-ABBR.

18. The system limits for originating and terminating facilities shall not exceed the limit.

19. Number of Centrex in the system shall not exceed the maximum limit.

20. Number of members in the new CENTREX being created should not exceed the total maximum limit for Centrex members.

21. The billing counters of a Centrex shall get initialized to zero at the time of its creation.

22. Commercial billing records will be added for the CENTREX as well as the members being added.

23. In the output report, the DIR TYPE field shown along with directory number shall indicate NORMAL DIRNO or PDN.

Output Report

CREATE CENTREX REPORT

CENTREX NUMBER =

CENTREX NAME =

BILLING TYPE =

ESCAPE CODE =

ABBRIVIATED DIGIT LENGTH OF MEMBER =

CHARGE RATE NUMBER =

ACCESS BARRING =

FACILITY ORIGINATING =

FACILITY TERMINATING =

METERING CLASS =

ATTENDEN TNUMBER =

CTRX COUNTERS =



LOCAL COUNTERS =

STD COUNTERS =

STD CALLS =

ISD COUNTERS =

ISD CALLS =

DIRNO ABBREVIATED NO DIR-TYPE

[

]

6.8.2. ADD-MEM-TO-CNTRX

This command is used to add members to an existing CENTREX.

Input form

ADD-MEM-TO-CNTRX ADD MEMBER TO CENTREX

[CTRX-NUM] : NONE

[CTRX-NAM] : NONE

DIR-ABBR :

Validation and Remarks :

1. This command shall be allowed in ONLINE mode only.

2. Both CTRX-NUM and CTRX-NAM should not be non-default

3. Both CTRX-NUM and CTRX-NAM should not be default.

4. If CTRX-NUM is non-default, then the Centrex with the given CTRX-NUM should be already created in the system.

5. If CTRX-NAM is non-default, then the Centrex with the given CTRX-NAM should be already created in the system.

6. Each of the Directory number in the DIR-ABBR list shall be a subscriber of self-exchange.

7. Any of the Directory number in the DIR-ABBR list shall not be a system directory number.

8. Any of the Directory number in the DIR-ABBR list shall not be a frozen number.

Chapter 6

68 C-DOT DSS MAX

9. Each of the Directory number in the DIR-ABBR list shall be an ordinary subscriber, a PDN number or a member directory number.

10. None of the Directory number in the DIR-ABBR list shall belong to any CENTREX.

11. Either the directory number or the abbreviated number or both in the combination for every DIR-ABBR should not be repeated.

12. None of the abbreviated numbers in DIR-ABBR should start with the ESC-CODE digit.

13. Length of the abbreviated number in the DIR-ABBR should be of ABBR-LEN.

14. If the Directory number in the DIR-ABBR is a PDN, then all the member directory number of the PDN should either be present in the set of entries for DIR-ABBR or should be already a member of this CENTREX.

15. Number of members in the new Centrex being created should not exceed the total maximum limit for Centrex members.

16. Every directory number in the list of DIR-ABBR should be made OOS-OPR before making it a member of the new Centrex being created.

17. Commercial billing records will be added for the centrex and for the members being added to the CENTREX.

Output Report

ADD MEMBER TO CENTREX REPORT

CENTREX NUMBER =

CENTREX NAME =


[

]

6.8.3. REM-MEM-FRM-CNTRX

This command shall be used to delete existing member(s) from a CENTREX.

Input form

REM-MEM-FRM-CNTRX REMOVE MEMBER FROM CENTREX



[CTRX-NUM] :NONE

[CTRX-NAM] :NONE

ABBRNO :

Validation and Remarks :


2. Both CTRX-NUM and CTRX-NAM should not be non-default

3. Both CTRX-NUM and CTRX-NAM should not be default.

4. If CTRX-NUM is non default, the Centrex with the given CTRX-NUM should be already created in the system.

5. If CTRX-NAM is non default, the centrex with the given CTRX-NAM should be already created in the system.

6. ABBRNO shall not be repeated in the input.

7. Each ABBRNO shall be a member of the CENTREX.

8. If the Directory number corresponding to the ABBRNO is a member directory number of a PDN, then either the PDN should be specified in ABBRNO or the PDN should not be a member of the CENTREX.

9. The directory number corresponding to the ABBRNO should be made OOS-OPR before deleting it from CENTREX.

10. ATND-NUM of the CENTREX can not be deleted by this command.

11. All the members of a CENTREX can not be deleted by this command.

Output Report

REMOVE MEMBER FROM CENTREX REPORT

CENTREX NUMBER =

CENTREX NAME =


[

]

Chapter 6

70 C-DOT DSS MAX

6.8.4. MOD-CNTRX-CHAR

This command shall be used to modify the characteristics of an existing CENTREX.

Input form

MOD-CNTRX-CHAR MODIFY CHARACTERISTICS OF CENTREX

CTRX-NUM :

[ESC-CODE] :

[DET-BLG] :

[CALL-STA] :

[CRG-RTN] :

[ATND-NUM] :

[ORG-CFAC] :

[TRM-CFAC] :


1. ESC-CODE shall not be 1.

2. The CENTREX given in CTRX-NUM should be existing in the system.

3. The ESC-CODE should not be same as the first digit of any member of the CENTREX.

4. If MTRG-CLS is NRM-MTR, then CRG-RTN shall be existing in the system.

5. If the existing CALL-STA of the CENTREX is NRM-LIN, then it can not be modified to BNP-DISC.

6. If the existing CALL-STA of the centrex is BNP-DISC, then it can not be modified to BNP-ANNC.

7. ATND-NUM shall be a member of the CENTREX.

8. The system limits for originating and terminating facilities shall not exceed the limit.



Output Report

MODIFY CENTREX CHARACTERISTICS REPORT

CENTREX NUMBER =

CENTREX NAME =

ESCAPE CODE =

BILLING TYPE =

MODIFY CENTREX CHARACTERISTICS REPORT

METERING CLASS =

CHARGERATENUMBER =

ATTENDENTNUMBER =



ACCESS BARRING =

A.2.1.5 DEL-CNTRX

This command is used to delete an existing CENTREX.

INPUT FORM

DEL-CNTRX DELETE EXISTING CENTREX

[CTRX-NAM] :

[CTRX-NUM] :



2. Both CTRX-NUM and CTRX-NAM shall not be default.

3. Both CTRX-NUM and CTRX-NAM shall not be non-default.

4. If CTRX-NUM is non-default then CENTREX with the given CTRX-NUM should be already created in the system.

5. If CTRX-NAM is given as non-default then the CENTREX with the given CTRX-NAM should be already created in the system.

6. The CENTREX shall not be under observation.

Chapter 6

72 C-DOT DSS MAX

7. All the members of the CENTREX shall be made OOS-OPR prior to this command.

Output Report

DELETE CENTREX REPORT

CENTREX NUMBER =

CENTREX NAME =

CTRX COUNTERS =

LOCAL COUNTERS =

STD COUNTERS =

STD CALLS =

ISD COUNTERS =

ISD CALLS =

6.8.5. DISPL-CNTRX-CHAR

Input form

DISPL-CNTRX-CHAR DISPLAY CENTREX CHARACTERSTICS

[CTRX-NUM] : ALL

[CTRX-NAM] : ALL


1. If CTRX-NUM and CTRX-NAM is given as default i.e ’ALL’, then the output report will be different i.e it will show only the CTRX-NUMs and the number of members in them in tabular form.

2. If CTRX-NUM is non-default then CENTREX with the given CTRX-NUM should be already created in the system.

3. If CTRX-NAM is given as non-default then the CENTREX with the given CTRX-NAM should be already created in the system.

Output Report

1. If input entries are default i.e. ’ALL’

DISPLAY CENTREX REPORT

TOTAL NO OF CENTREX

TOTAL NO OF CENTREX MEMBERS



CENTREX NUMBER

NO. OF CENTREX MEMBERS

2. If input entries are non-default.

DISPLAY CENTREX CHARACTERISTICS REPORT

CENTREX NUMBER =

CENTREX NAME =

NO OF MEMBERS =

ABBREVIATED DIGIT LENGTH OF MEMBER ESCAPE CODE =

BILLING TYPE =

METERING CLASS =

CHARGE RATE NUMBER =

ATTENDENT NUMBER =



ACCESS BARRING =

MEMBER-DIRNO ABBREVIATED NO DIR-TYPE

[

]

6.8.6. MOD-CNTRX-OBS

This command shall be used to put a Centrex under observation or to remove a Centrex from observation.

Input form:

MOD-CNTRX-OBS TO MODIFY CENTREX OBSERVATION

[ADD-CTRX] :

[DEL-CTRX] :

[DEL-ALL] :

Chapter 6

74 C-DOT DSS MAX

CTRX-OBS :

[OBS-PRD] :

[STP-DTE] :

[STP-TME] :


1. If DEL-ALL is YES, then ADD-CTRX and DEL-CTRX shall be default.

2. If DEL-ALL is YES, then at least one Centrex should be under observation.

3. In the STP-DTE parameter, the number of days in the month shall not exceed the maximum number of days in that month.

4. In the STP-DTE parameter, if the month subfield is 2 (i.e. FEB) and if the year subfield corresponds to a leap year, then the number of days subfield shall contain value 29.

5. STP-DTE should not be less than Current Date.

6. If STP-DTE is equal to Current-Date, then STP-TME should not be less than the Current- Time.

7. Both OBS-PRD and STP-DTE parameters should not be non-default.

8. Both OBS-PRD and STP-TME parameters should not be non-default.

9. If DEL-ALL is YES, then none of STP-DTE, STP-TME or OBS-PRD should be non-default.

10. Minimum possible value of Observation Period is 15 minute.

11. The centrex (given in ADD-CTRX) to be put under observation should have been created.

12. The centrex (given in ADD-CTRX) to be put under observation should not be already under observation.

13. The centrex (given in DEL-CTRX) to be removed from observation should have been created.

14. The centrex (given in DEL-CTRX) to be removed from observation should be already under observation.

15. Number of centrex to be added under observation in the system shall not exceed the maximum limit.



OUTPUT REPORT

MODIFY CENTREX OBSERVATION REPORT

CENTREX ADDED =

CENTREX DELETED =

OBSERVATION TYPE =

OBSERVATION PERIOD =

OLD STOP DATE =

OLD STOP TIME =

NEW STOP DATE =

NEW STOP TIME =

6.8.7. DISPL-CNTRX-MTR

Input form

DISPL-CNTRX-MTR Display Centrex group latest meter information.

[CTRX-NUM] :

[CTRX-NAM] :


1. Both CTRX-NUM and CTRX-NAM shall not be default

2. Both CTRX-NUM and CTRX-NAM shall not be non-default.

3. If CTRX-NUM is non-default, then the centrex specified by CTRX-NUM shall have been created in the system.

4. If CTRX-NAM is non-default, then the centrex specified by CTRX-NAM shall have been created in the system.

5. Cumulative billing counters for the specified centrex are displayed in the output report.

Output Report

DISPLAY CENTREX's LATEST METER INFORMATION

Centrex Number =

Chapter 6

76 C-DOT DSS MAX

Centrex Name =

Centrex counter =

Local Counter =

STD Counter =

STD calls =

ISD counter =

ISD calls =

Bulk Counter =

6.9. ENHANCEMENTS TO EXISTING COMMANDS

6.9.1. DEL-SUB

Delete an existing subscriber line

[Dir no.] :

[TEN ] :

Mode :


1. If the subscriber specified by DIRNO or TEN parameter is a member of a centrex, then the subscriber can not be deleted by this command.

6.9.2. DISPL-SUB

Display subscriber related data

[Dir no.] :

[TEN ] :

A new field is to be shown in the output report.

Output Report

DISPLAY SUBSCRIBER REPORT

DIRECTORY NUMBER

TERMINAL EQUIPMENT NO

SERVICE GROUP NO

CENTREX NUMBER ABBREVIATED NUMBER



6.9.3. DISPL-SUB-LIST

Input Form

DISPL-SUB-LIST DISPLAY SUBSCRIBER LIST

BM-NO

[LST-REQ] NO

... ...

[MISC-STA] ALL

[CTRX-NUM] ALL


1. If the value in the CTRX-NUM parameter is given as default i.e `ALL’, then the output will show the directory numbers irrespective of their Centrex numbers, but if the same is given as 0, then the output report will display those subscribers whose attributes meet the other criteria specified in the input and which are not member of any Centrex.

2. If CTRX-NUM is non-default and is non-zero, then it should have been created in the system.

Chapter 6

78 C-DOT DSS MAX

OUTPUT REPORT

DISPLAY SUBSCRIBER STATISTICS REPORT

BASE MODULE NUMBER :

BASIC SERVICES :

CENTREX NUMBER :

DIRECTORY NUMBER TERMINAL EQUIPMENT NO TEN TYPE

6.9.4. DEL-HGP

Delete a hunt group

Pri dir :

Mode :


1. If the PDN being deleted is a member of a Centrex, then it can not be deleted.

6.9.5. DISPL-HGP

Display a hunt group information

PRI dir :-

OUTPUT REPORT

DISPLAY HUNT/DDI GROUP REPORT

PRIMARY DIRECTORY NUMBER GROUP TYPE

... ...

B-CHANNEL SELECTION MECHANISM CENTREX NUMBER

ABBREVIATED NUMBER

6.9.6. DISPL-NUM-NAME - Display number to name mapping

[ENT-TYPE ]

[ENT-NUM ]

[ENT-NAME ]



The ENT-TYPE parameter of this command shall support an additional value CTRX.

This value shall be used to display the number to name mapping of all the Centrex created in the system.

OUTPUT FORM

ENTITY TYPE CENTREX

ENTITY NUMBER ENTITY NAME

------------------------------------------------------------------------------------------------------------

1 ONE

25 TWENTYFIVE

6.9.7. DISPL-SUB-MTR

Input Form

DISPL-SUB-MTR DISPLAY SUBSCRIBER'S LATEST METER INFO.

[DIRNO] :

[TEN] :

[CTX-ABBR] :


1. Only one parameter DIRNO, TEN, CTX-ABBR shall be non-default, other two should be default.

2. If CTX-ABBR is non-default, then the Centrex specified in this parameter shall have been created in the system.

3. If CTX-ABBR is non-default, then the abbreviated number specified shall have been a member of the Centrex specified.

Output Report

Output Report for Ordinary Subscriber

Display Subscriber's Latest Meter Information

Directory Number =

Chapter 6

80 C-DOT DSS MAX

Terminal Equipment No =

Display Subscriber's Latest Meter Information

Directory Number Type =

Centrex Number =

Centrex Name =

Abbreviated No =

Centrex counter =

Local Counter =

STD Counter =

STD calls =

SD counter =

SD calls =

Bulk counter =

Output report for PDN

Display Subscriber’s Latest Meter Information

Centrex Number = Centrex Name = DIRNO CTX-CTR LOC-CTR STD-CTR STD-CALL ISD-CTR ISD-CALL

If a DIR-NO or a PDN is part of any CTRX-NUM, then there shall be an additional counter called CTX-CNTR, and BULK-CNTR shall be a total of all the counters including the CTRX- CNTR.

6.9.8. DISPL-BILL-REC

Input Form

DISPL-BILL-REC DISPLAY BILLING RECORD OF A SUBSCRIBER/ TRUNK GROUP/ CNTRX GROUP

FDATE :

[TDATE] :

FRM-TIME :

[TO-TIME] :

DBLG-TYP :



[CHG-THRS] : 1

[DIR-DGTS] :

[TGP-NUM] : ALL

[CTX-ABBR] : ALL


1. One and only one of the input parameters DIR-DGTS, TGP-NUM, CTRX-NUM and ABBR- NUM shall be non-default.

2. If DBLG-TYP is SUB, then TGP-NUM shall be default.

3. If DBLG-TYP is SUB then both DIR-DGTS and CTRX-ABBR shall not be default

4. If DBLG-TYP is SUB, then both DIR-DGTS and CTRX-ABBR shall not be non-default.

5. If second subfield of CTX-ABBR is default, then output report will show billing records of all the members of the Centrex specified by first subfield.

6. If both subfield of CTX-ABBR parameter are non-default, then output report will show the billing records of the particular Centrex member specified by CTX-ABBR parameter.

7. If DBLG-TYP is TGP then DIR-DGTS, CTRX-NUM and ABBR-NUM should be default.

Output Report

DISPLAY BILLING RECORD REPORT

Directory Number =

Centrex Number =

Abbreviated Number =

Normal Call Billing Record

[-----------------------------------------------------------------------------------------------

DATE TIME CALLED PARTY CHG-DURN CHG-UNITS BS

hh:mm:ss mm:ss

]

------------------------------------------------------------------------------------------------

Chapter 6

82 C-DOT DSS MAX

Diverted Calls Billing Record

[----------------------------------------------------------------------------------------------

DATE TIME CALLED PARTY CHG-DURN CHG-UNITS BS

hh:mm:ss mm:ss

]

----------------------------------------------------------------------------------------------

Special Services Billing Record

[----------------------------------------------------------------------------------------------

DATE TIME DIALLED DIGITS FAC-TYP CHG-UNITS

hh:mm:ss

]

-----------------------------------------------------------------------------------------------

6.9.9. DISPL-XCHG-MTR

Display Exchange meter

FRM-DATE :

TO DATE :

[REV-TYPE]:

Output Report

There is no change in output report in case of REV-TYPE as TAX. In case of SUBS and ILT, the output form shall display Centrex Counter, if it is NON-ZERO.

Display Exchange Meter Output Report

START DATE :

END DATE :

REVENUE TYPE :

CENTRX COUNTER :

LOCAL COUNTER :

Display Exchange Meter Output Report



STD COUNTER :

ISD COUNTER :

TOTAL REVENUE :

6.9.10. FMT-BLG-CNTR

FMT-TYPE :

The FMT-TYPE parameter of this command shall support one more value CNTRX which shall be used to format the billing counters of the Centrex created in the system.

6.9.11. REPORT-BILL-CNTRS

Generate Billing counter request

This command generates the report file in text format from formatted binary file.

Input Form

REPORT-BILL-CNTRS

REP-TYP :

[DIRNO] :

[TGP-NUM] :

[TGP-NAME] :

[CTRX-NUM] :

[CTRX-NAM] :

OUTPUT REPORT

The layout of the report for subscriber is as follows :

DIR no. CTRX-CNTR

LOC-CNTR

STD-CNTR STD= CALL

ISD-CNTR ISD-CALL

Chapter 6

84 C-DOT DSS MAX

The layout of report for Centrex is as follows :

CTRX-NUM

CTRX-NAM

CTRX-CNTR

LOC-CNTR

STD-CNTR

STD-CALL

ISD-CNTR ISD-CALL


1) If REP-TYP is SUB, one and only one of CTRX-NUM, CTRX-NAM or DIRNO is to be specified.

2) If CTRX-NUM is non-default, then it shall have been created in the system.

3) If CTRX-NAM is non-default, then it shall have been created in the system.

6.9.12. DISPL-COM-BILL

Input Form:

DISPL-COM-BILL DISPLAY COMMERCIAL BILLING RECORD

FDATE :

[TDATE] :

COM-TYP :

[DIRNO] :

[TGP-NAME] :

[CTRX-NUM] :

[CTRX-NAME] :


1. All DIRNO, TGP-NUM, TGP-NAME, CTRX-NUM & CTRX-NAME All cannot be simultaneously DEFAULT or NON-DEFAULT.

2. If COM-TYP is CTRX then DIRNO, TGP-NUM & TGP-NAME should be default and CTRX-NUM & CTRX-NAME both should not be default.

OUTPUT REPORT

Display Centrex Commercial Billing Record

DATE TIME

USER NAME



OPERATION TYPE

OPERATION MODE

CNTRX NUM

CNTRX NAME

NO OF MEMBERS IN CENTREX

FACILITY ORIGINATING

FACILITY TERMINATING

OLD BILLING TYPE

NEW BILLING TYPE

OLD LINE STATUS

NEW LINE STATUS

OLD ACCESS BAR

NEW ACCESS BAR

OLD CHARGE RATE NUMBER

NEW CHARGE RATE NUMBER

CENTREX COUNTER

LOCAL CNTR

STD COUNTER

STD CALLS

ISD COUNTER

ISD CALLS

BULK COUNTER

6.9.13. DISPL-TRF-RPT

This command is used to display traffic report depending upon the type of report mentioned by operator.

The RPT-ID parameter of this command shall accept a new value CTRX-REP for displaying centrex traffic reports.

Output Report:

PERIODIC REPORT ON CENTREX TRAFFIC

Chapter 6

86 C-DOT DSS MAX

DATE :

OBS DUR :

MODULE :

CENTREX ORIGINATING-CENTREX TERMINATING TRAFFIC INFORMATION Total Intra Centrex call attempts

Successful call attempts(%)

Completed call attempts(%)

Success rate (%)

CENTREX ORIGINATING-OUTGOING TRAFFIC INFORMATION

Total Centrex originated call attempts towards public network

Successful call attempts (%)

Completed call attempts (%)

Success rate (%)

INCOMING-CENTREX TERMINATING TRAFFIC INFORMATION Total call attempts from public network to Centrex

Successful call attempts(%)

Completed call attempts(%)

Success rate (%)

6.9.14. DISPL-TRF-OBS

This command is used to display active reports, periodicity & output options. Usually this command is used to check whether the desired traffic report is active or not.

Input Form

For Centrex traffic observation type , a new value "CTRX" has to be given against the field OBS-TYP.

Output Form

i) For OBS-TYP=REPORT, following would be output report if Centrex has already been put under observation.



DISPLAY TRAFFIC OBSERVATION REPORT

OBSERVATION TYPE =REPORT

REPORT TYPE UNIT PERIODICITY OUTPUT OPTION

CENTREX

ii) For OBS-TYP=CTRX, following would be output report DISPLAY TRAFFIC OBSERVATION REPORT OBSERVATION TYPE = CENTREX OBSERVATION

CENTREX NUMBER(s)= OBSERVATION TYPE=

STOP DATE FOR TRAFFIC OBSERVATION= STOP TIME FOR TRAFFIC OBSERVATION=

6.9.15. DISPL-CDR

This command shall be used to display Call Detail Records of specific type for a specific period for a particular Centrex subscriber.

Input Form

DISPL-CDR TO DISPLAY CALL DETAIL RECORD

[DIRNO] :

[CTX-ABBR] :

CDR-TYP :

FRM-DATE :

TO-DATE :

FRM-TIME :

TO-TIME :


1. Both DIRNO and CTX-ABBR shall not be default.

2. Both DIRNO and CTX-ABBR shall not be non-default.

3. If DIRNO is non-default, then it should not be a Centrex member.

4. The Centrex given in the CTX-ABBR should be already created in the system.

5. Abbreviated number given in CTX-ABBR shall belong to Centrex given in CTX-ABBR.

Chapter 6

88 C-DOT DSS MAX

OUTPUT REPORT

i) FOR CALLING TYPE CDR

CALL DETAIL RECORD TYPE : CLLNG CALLING SUBSCRIBER DETAILS CENTREX NUMBER

ABBREVIATED NUMBER

..............

.............

CALLED SUBSCRIBER DETAILS CENTREX NUMBER

...........

............

ii) FOR CALLED TYPE CDR

CALL DETAIL RECORD TYPE: CALLED CALLED SUBSCRIBER DETAILS CENTREX NUMBER

ABBREVIATED NUMBER

..................................

.................................

CALLING SUBSCRIBER DETAILS CENTREX NUMBER

................................

................................

................................

6.9.16. START-TRF-RPT

This command is used to start traffic reports

For Centrex traffic, a new value "CTRX-REP" has to be given against the field RPT-TYP.

Output Form

START TRAFFIC REPORT

REPORT TYPE UNIT PERIODICITY

CENTREX



6.9.17. MOD-RPT-PERDTY

This command is used to modify the periodicity of traffic report(s).

For Centrex traffic report, a new value "CTRX-REP" has to be given against the field RPT- TYP.

6.9.18. MOD-OUT-OPT

This command is used to modify the output option of traffic report(s).


6.9.19. STOP-TRF-RPT

This command is used to deactivate(stop) one or more active traffic reports.


6.9.20. MOD-SUB-OBS

Modify subscriber observation

ADD-DIR :

DEL-DIR :

DEL-ALL :

SUB-OBS :

OBS-PTD :

STP-DTE :

STP-TIM :

This command is used to put individual subscriber under observation or remove a particular subscriber from observation for any type of calls (originating, terminating, malicious).

OUTPUT FORM

MODIFY SUBSCRIBER OBSERVATION REPORT

OBSERVATION TYPE = SUBSCRIBERS <OBS-TYPE (e.g ORIG)>

SUBSCRIBERS ADDED TO THE LIST ADDED-DIRNO

[

Chapter 6

90 C-DOT DSS MAX

Directory Number Centrex Number Abbreviated Number

]

SUBSCRIBERS DELETED FROM THE LIST DELETED-DIRNO

[

Directory Number Centrex Number Abbreviated Number

]

OLD STOP DATE : OLD STOP TIME : NEW STOP DATE: NEW STOP TIME:

6.10. CHANGES IN SIF PROCEDURES

6.10.1. Dialling Patterns For New Features For Centrex Members

Table 2: Dialing Patterns For New Features For Centrex Members

Service Usage Code

Automatic Call Back - Activation HSF 1294

Automatic Call Back - Deactivation HSF 1295

Call Transfer HSF 1296 ABBR

Following are the legends used in above table.

ABBR Abbreviated number of called Centrex member

HSF Hook Switch Flash


Chapter 7.

Special Priority Implementation in S/W Release 2_2_1_9

7.1. FEATURE INTRODUCTION

Currently in the field, for India-One Plan (or any other similar plan) implementation, the requirement is that all outgoing traffic from INDIA-ONE subscribers should be carried over a New TGP towards the TAX. At TAX, for that New TGP, charging data is defined for INDIA-ONE plan (Say @Rs. 1/ min), the charging CHB/Charging pulses are sent towards the originating exchange. In future, there may be some other plan, which will have the similar requirement like India-one. So a general strategy has been designed to implement some Special Sub/TGP Priorities to seize desired OG TGP for outgoing calls routing.

7.2. FEATURE IMPLEMENTATION

a) A new parameter “SPECIAL PRIORITY”(SPL-PRI) has been introduced for this purpose. This special priority can be assigned to a subscriber during its creation or during modification of subscriber characteristics and becomes a part of subscriber office data. Its values are from 15 to 19 & default value is “NONE”.

b) New values of special priority (i.e. 15 to 19) can also be allocated to Trunk Groups in TGP Priority field, which are in addition to the existing values of 1 to 8.

c) Special priorities (15 to 19) if allocated, will be used internally for TGP selection only. These will not be sent over the network to subsequent nodes.

d) Existing Sub/TGP priorities 1 to 8 will have the same interpretation as before.

7.3. AT ORIGINATING EXCHANGE

7.3.1. Call handling in Various Call Scenarios

7.3.1.1. Existing Implementation in MOD-R2 Signalling

Total, No. of Subscriber priorities = 1 to 14

Chapter 7

92 C-DOT DSS MAX

Operator can define only 1 to 8 priorities, while 9 to 14 are defined by system automatically based on LIN-TYP parameter in Cre-Sub command :--

LIN-TYP SUB-PRI

CCB 9

CCB-STD 10

CCB-CRD 11

PABX / Hunt Group 12

OPR 13

TST-LIN 14

These priorities are internal to C-DOT & used to select an O/G TGP to route a call .Only three type of categories are sent over the Network as “Calling Line Category” for various type of subscribers (Viz. Ordinary Sub, Priority Sub & Operators) as explained below:

Calling Subscriber Priority Calling Line Category sent Outward

1 cat 1 (Ordinary Subscriber)

2 to 6 cat 2 (Priority Subscriber)

7 cat 1 (Data call)

8 cat 1 (Ordinary line)

9 (CCB) /10 (CCB-STD)/ cat1 (ordinary line)

11 (CCB-CRD)

12 ( PABX/Hunt Group ) cat1 (ordinary line)

13 (Operator) cat 5 (operator)

Effect of Special Priority (SPL-PRI) having values 15 to 19

i) If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1, 7, 8, 9, 10, 11 or 12 and Special Priority (SPL-PRI) as any value from 15 to 19, then O/G TGP will be selected based on value of special priority(15 to 19) . In the network, category of ordinary subscriber i.e.1 will be floated as calling subscriber category. Thus for network purpose, priorities 1,7,8,9,10,11 and 12 are mapped to 1.

ii) If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1, 7, 8, 9, 10, 11 or 12 and Special Priority (SPL-PRI) as “NONE” then O/G TGP will be selected based on value of

SPECIAL PRIORITY IMPLEMENTATION IN S/W RELEASE 2_2_1_9


“SUB-PRI” and category of ordinary subscriber i.e.1 will be floated in the network as calling subscriber category.

iii) If a call is originated from a priority subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and Special Priority (SPL-PRI) as any value from 15 to 19 then O/G TGP will be selected based on special priority (15 to 19) and category of priority subscriber i.e.2 will be floated in the network as calling subscriber category. Thus for network purpose, priorities 2 to 6 are mapped to 2.

iv) If a call is originated from a priority subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and special priority (SPL-PRI) as “NONE” then O/G TGP will be selected based on normal priority (SUB-PRI) and category of priority subscriber i.e.2 will be floated in the network as calling subscriber category.

7.3.1.2. Existing Implementation for CCS7 Signalling

Total, No. of Subscriber priorities = 1 to 14

Operator can define only 1 to 8 priorities, while 9 to 14 are defined by system automatically based on LIN-TYP parameter in Cre-Sub command :--

LIN-TYP SUB-PRI

CCB 9

CCB-STD 10

CCB-CRD 11

PABX / Hunt Group 12

OPR 13

TST-LIN 14

These priorities are internal to C-DOT & used to select an O/G TGP to route a call.

In message based CCS7 signalling, Calling line category in various type of Subs is sent over the network as stated below :

Calling subscriber Priority Calling Sub Category sent Outward

01 (ORD-SUB) 0A

02 to 06 (Priority Subscriber) 0B

07 (Data Call) 0C

08 00

Chapter 7

94 C-DOT DSS MAX

09 (CCB)/10(CCB-STD)/ 11(CCB-CRD) E1

12 (PBX) E4

13 (TRK-OPR) 09

14 (TST-LIN) E6

Effect of Special Priority (SPL-PRI) having values 15 to 19 :

If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1 and Special Priority (SPL-PRI) as any value from 15 to 19, then O/G TGP will be selected based on value of special priority (15 to 19). In the network, category of ordinary subscriber i.e. 0A will be floated as calling subscriber category.

If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1 and Special Priority (SPL-PRI) as “NONE” then O/G TGP will be selected based on value of “SUB-PRI” and category of ordinary subscriber i.e.0A will be floated in the network as calling subscriber category.

If a call is originated from a subscriber having priority (SUB-PRI) as any value from 2 to 6 and Special Priority (SPL-PRI) as any value from 15 to 19 then O/G TGP will be selected based on special priority and category of priority subscriber i.e. 0B will be floated in the network as calling subscriber category. Thus for network purpose, priorities 2 to 6 are mapped to 0B.

If a call is originated from a subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and special priority (SPL-PRI) as “NONE” then O/G TGP will be selected based on normal priority (SUB-PRI) and category of priority subscriber i.e. 0B will be floated in the network as calling subscriber category.

7.4. AT TRANSIT EXCHANGE

7.4.1. Existing Implementation

At Transit Exchange IC TGP-PRI parameter can take values from 1 to 8.In case call is coming from an Ordinary Sub( Sub-Pri=1) from previous node, then we can make use of TGP-PRI value to seize the desired OG TGP towards further network. But in case ,call is coming from a Priority Sub ( Sub-Pri= 2 to 6), we cannot make use of TGP-PRI value to seize the desired OG TGP, as all calls now will pass through OG TGP defined against priority 2 on any route.

7.4.2. Effect of additional TGP-PRI values 15 to 19

7.4.2.1. If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) either 1, 7, 8, 9, 10, 11 or 12 and call is coming on an I/C trunk

SPECIAL PRIORITY IMPLEMENTATION IN S/W RELEASE 2_2_1_9


group of the transit exchange having trunk priority > 14(i.e. Special priority), then O/G TGP will be selected based on the trunk priority and category of ordinary subscriber i.e.1 will be floated in the network as calling subscriber category.

7.4.2.2. If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) either 1, 7, 8, 9, 10, 11 or 12 and call is coming on an I/C trunk group of the transit exchange having trunk priority < 15(i.e. Normal priority), then O/G TGP will be selected based on the trunk priority and Calling Line Category 1 will be floated in the network .

7.4.2.3. If a call is originated from a priority subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and call is coming on an I/C trunk group of the transit exchange having trunk priority > 14(i.e. Special priority), then O/G TGP will be selected based on the trunk priority and category of priority subscriber i.e 2 will be floated in the network as Calling Line category.

7.4.2.4. If a call is originated from a priority subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and call is coming on an I/C trunk group of the transit exchange having trunk priority < 15 (i.e. Normal priority), then O/G TGP will be selected based on the calling subscriber priority which is received as category of calling subscriber i.e 2(i.e. priority subscriber) and 2 only will be floated in the network as calling subscriber category. This is the case when call is coming from a priority subscriber and not opted for any special plan (like India One or Lo kar lo baat)

7.5. COMMANDS UPDATIONS

7.5.1. TRUNK MANAGEMENT COMMANDS UPDATE

1. CRE-TGP ( CREATE TRUNK GROUP ):-

TRK-PRI field will be modified to accept values from 1 to 8 & 15 to 19

2. MOD-TGP-CHAR (MODIFY TRUNK GROUP CHARACTERISTICS) :

TRK-PRI will be modified to accept values from 1 to 8 & 15 to 19

3. CRE-ROUT (CREATE A ROUTE):

TGP-CHOICE parameter now will accept values from 1 to 19.

4. MOD-ROUT-CHAR:

Same changes as in CRE-ROUT command.

5. DISPL-TGP-LIST:

Chapter 7

96 C-DOT DSS MAX

TRK-PRI will be modified. presently its value is defined as range, from 1 to 8. Now its range will be from 1to 8 & 15 to 19.

7.5.2. SUBSCRIBER MANAGEMENT COMMANDS UPDATE

1. ADD-MSN-DN (ADDING A MSN SUBSCRIBER TO AN ACCESS)

New input parameter SPL-PRI is introduced in crp data. Range is from 15 to 19.

2. CRE-SUB


3. MOD-SUB-CHAR


4. CRE-HGP (CREATE A HUNT/DDI GROUP)

New input parameter SPL-PRI will be introduced in crp data. Range is from 15 to 19.

5. MOD-HGP


6. DISPL-SUB-LIST

New input parameter SPL-PRI will be introduced in crp data. Range is from 15 to 19.


Chapter 8.

New Strategy for Detailed Billing Records (CDR) Generation & Transfer

8.1. FEATURE INTRODUCTION

Bharat Sanchar Nigam Limited (BSNL) is having countrywide presence with over 40 million subscriber base. BSNL has proposed to implement next generation state-of- Art Detail Billing Records (CDR) based Customer Care and Convergent Billing System. This can be achieved with deployment of Centralized Integrated Billing Systems with supporting technological and communication infrastructure.

To implement this, Detail Billing Records (CDRs) are to be obtained from different type of Network elements capable of generating billable information, using centralized Mediation System.

In BSNL Network, 90% of the switches are of CDOT Technology. To meet the above requirement, there is a need to generate 100% Detail Billing Records for all the completed calls. Generation of 100% Detail Billing Records is supported in the existing & New software releases of C-DOT. These Detail Billing Records need to be automatically transferred to the Billing center preferably in real time mode.

8.2. IMPLEMENTATION

The above requirement has been implemented by

a) Software changes at IOP end

1. Changes in existing s/w release to S/W release 2_2_1_9

2. Generation of hourly detailed billing files instead of daywise for subscribers and trunk groups

3. NCBR & TGBR files have been modified to new names :

Old File Name New File name

ncbrddmmyy.dat nchhddmmyy.dat

tgbrddmmyy.dat tghhddmmyy.dat

Chapter 9

98 C-DOT DSS MAX

Where hh =Hour, dd= Day, mm = Month, yy = Year

b. Addition of Compact Embedded System (CES) :

A new add on unit known as “Compact embedded systems” (CES) has been introduced for this purpose. CES has to be connected with both CDOT IOP’s at every site. Detail Billing records for subscribers and trunk groups will be automatically transferred every hour from CDOT IOP to “Compact Embedded System” (CES), CES will be connected further on LAN. All the Detail Billing Records can be picked up from CES at a predefined frequency by the centralised billing center using FTP (File Transfer Protocol) application.

Modes of Detail Billing Records files transfer -Two modes of Detail Billing records file transfer are possible with this feature ♦ Automatic

Whenever CES comes up after booting, automatic file transfer is invoked,otherwise automatic file transfer is invoked periodically.

♦ Manual - Manual file transfer is invoked on operator request.

Once the CES is connected to IOP, on invoking file transfer utility in the defined mode (Manual or Automatic) the file transfer will begin. Refer “CES User Document” for details of Hardware / software, Installation, Maintenance procedures, various commands and Applications. The connectivity of CES with IOPs and Billing Center is shown in Fig 1.

FIGURE 1

IOP-5C

IOP-5D

CES BOX

IP NETWORK

BILLING CENTER


Chapter 9.

Do's and Dont's

9.1. IOP RELATED PROBLEMS AND SOLUTIONS

To ensure smooth operation of the IOPs and the Exchange, some of the routine maintenance problems along with their solutions are explained. It is expected from the maintenance personnel to refer the specific section for a problem and strictly follow the same sequence, listed as possible solutions of the problem. Some of the problems are listed below : 1 "CRP" fails to run on the IOP. 2. "CRP" is running but CRP command fails to execute on the IOP. 3. OOD - Report related problems. 4. Printer related problems.

9.1.1. "CRP" Fails to Run on the IOP.

In this case, the error message is to be noted and then select one of the possible solutions which will depend on the error message.

CASE 1 : When "CRP" fails to run with error

"ERROR CASE RMID - - - - - - - - - "

Solution : IOP5X> ipcrm - Q805

CASE 2 : When "CRP" fails to run with error "CRP not found"

Solution : If "CRP" fails to run on IOP-0 with above error message but runs successfully on IOP-1 then CRP file is to be copied from IOP-1 to IOP-0. → Insert cartridge in IOP-1 → IOP5D>>$TAPE → IOP5D>cd $CURREL ↵ → IOP5D>ls crp | cpio – ocv > $TAPE↵

Chapter 9

100 C-DOT DSS MAX

Remove the cartridge from IOP-1 and insert it in IOP-0. The CRP file has been copied on the cartridge from IOP-1. Now copy the same file from cartridge to IOP-0.

On IOP-0 :

IOP5C>cd $CURREL↵

IOP5C>cpio -icv<$TAPE ↵

Now remove the cartridge from the cartridge drive and run "CRP" on IOP-0.

9.1.2. OOD Related Problems

Case 1 : aood_main process is recreating again & again on the CONSOLE of one IOP with error message:

"recreating /u/code/iopete/aood_main, 2,1,0,0"

Solution : 'aood_main' file is to be copied in this (say IOP-1) as per the procedure given below:- ♦ Insert a cartridge in drive of IOP5C ♦ IOP5C>>$TAPE ♦ IOP5C> ls aood_main $ | cpio -ocv>$TAPE ♦ Remove the cartridge from IOP5C drive and insert

in IOP5D drive Now do the following in IOP5D : ♦ iop5d> cd $ CURREL ♦ iop5d> cpio -icv<$TAPE

Remove cartridge from the IOP-1 drive Case 2 : Alarms do not appear immediately after the unit fails.

Solution : In this case aood-main process has to be recreated as per the following procedure : ♦ On active iop, enter iop5x> prompt ♦ iop5x> ps -ef | grep aood

following message will be displayed:

root xx . .......................................... [aood_mai]

Note down this number 'xx' next to root ♦ iop5x > kill -9 xx

DO'S AND DONT'S


Process aood_main will be recreated in response to the above command. Go to CRP prompt. Current alarms will start coming immediately.

Go to CRP and resume normal operations.

9.1.3. Printer Related Problems

The Report stopped coming on the printer

Solution :

Step 1 Check status of the printer using following command

iop5x> cat /etc/passwd >/dev/icc_0 (if printer is connected on ASIO-0 of IOP VL or ASIO-1 of IOP-VH.

If the output of the file is printed on the printer, then printer cable, printer port of IOP and printer itself are ok. Go to Step 2.

In case output is not printed on printer, then

i) printer itself may be faulty, check by self test.

ii) printer cable may be connected on the wrong port.

iii) printer port icc_0 may be faulty.

iv) In the case of Installation Site, printer cable may be faulty.

To isolate the problem, shutdown the IOP and bring it to monitor prompt IOCx.x>

Now test the printer using command :

IOC x.x > print 1 10 ↵

Different characters will be printed in the response of the above command. If it is not so, remove the printer cable from IOP-end and put “ACIA - LOOPBACK CONNECTOR” on the corresponding port. Now test the port by executing the command :

IOCx.x > acio1 0 10 1 ↵

It should pass. This ensures that there is no fault at IOP-end and the only possibility is that “Printer Cable” or Printer itself may be faulty. This can be isolated by replacing the cable first and then Printer, one by one.

Chapter 9

102 C-DOT DSS MAX

However, if the ACIA loopback test fails, the printer can be connected to any other icc-x port.

Step 2 Check status of printer scheduler by giving following command:

IOP5x> lpstat -t

The response should be:

i) Scheduler is running.

ii) All printers (Pr1, Pr2 ..... Pr4) are enabled and accepting requests

iii) No printer request is pending in the queue for Pr1..

If every thing is OK, then go to step 3, proceed as listed below :

# 1 If scheduler is not running, then login into the 'lp' account:

login : lp

Password : DSSlp

iop5x> cd /usr/lib

iop5x> lpsched This will start printer scheduler.

log out of lp account by giving

iop5x > exit

Now go to admn account.

# 2. If printer is not accepting request then

log into 'lp' account

login : lp

Password : DSSlp

iop5x> cd /usr/lib

iop5x> accept pr1

Now log out of lp account

# 3. If scheduler is running & printer is accepting request but printer is disabled, then do following:

DO'S AND DONT'S


login : lp

Password : DSSlp

iop5x > enable prn1

iop5x > exit

# 4. If lot of request are pending in the queue, then in admn account itself do following:

iop5x > cancel x (x = pr1-1 etc.)

where x is the printer request pending in the queue, as shown in response to the lpstat -t command.

Step 3 To change printer port from icc_0 to icc_4 (say)

i) move the printer cable from ASIO-0 (icc_0) to ASIO-4 (icc_4) for IOP VL.

ii) log into lp account

login : lp

Password : DSSlp

iop5x> cd /usr/lib

iop5x> lpshut

iop5x> lpadmin -pprn1 -v/dev/icc_4

iopx> lpsched

iop5x> enable prn1

This will enable the printer at new port icc_4.

Log out of lp account.

9.2. DO'S AND DONT'S FOR CARD HANDLING

9.2.1. Terminal Unit Interface (TUI) Cards

At the time of changing the card, it should be ensured that the card is having proper jumper settings as per the requirement of its placement. Don't switch off power to TU during change of any card.

Chapter 9

104 C-DOT DSS MAX

9.2.2. Controller Cards (TIC, ANNC, TTC, MSC, TSC, CPU etc)

Before changing the cards with that of spares arranged from some other sites it should be ensured that the new card is having proper S/W EPROMs compatible to the present software release working in the exchange. (for S/W details, refer Chapter 2).

9.2.3. CPU-S04/S05 Cards

9.2.3.1. At the time of changing the CPU cards, the proper check sum of the CPU-cards should be ensured before using it in the system because of the following reasons. ∗ Checksum of the EPROMs of the CPU-card used in SBM-RAX/TAX is

different than that the CPUs used in MAX-L. ∗ Checksums of the EPROMs, of the CPU - cards used in different Base

Modules of MAX-L i.e. BPU of BM and APU and SCU of CM, are different.

9.2.3.2. At the time of changing the CPU card, also verify that same version of CPU card i.e. either CPU-S04 or CPU-S05 are used in both the copies of the unit.

9.2.4. Message Switch Device (MSD) Card

The jumper settings of MSD card should be verified as per its placement in Base Module or Central Module. Same MSD card is used in both the modules with different jumper settings.

9.2.5. 16 MB Memory Card (TME) Card or BME Card

At sites, where 16 Mb TME or BME card is used in BMs and in CM, DO NOT CHANGE THE CARD IN POWER ON CONDITIONS. Switch off the corresponding power supply unit before jack-out or jack-in of the card.

9.3. GENERAL - DO'S AND DON'TS FOR O&M ACTIVITIES

9.3.1. Take 'ed' and 'bd' back-ups daily in low traffic hours.

9.3.2. At MAX-L/XL standard procedure of 'bc' backups after every two months can be followed.

9.3.3. Monitor the disk space in the both the IOPs every day and ensure that disk space in / data does not fall below less than 5000 blocks in SBM-RAX/TAX and 10000 blocks in MAX-L sites. To monitor disk space:

IOP5x>df.

In the above display, the content against /data indicates the current available disk space.

DO'S AND DONT'S


9.3.4. A no. of new traffic reports have been implemented in 2_2_1_9 software. If the traffic reports are enabled, delete the 'tf' file group regularly.

9.3.5. The 'old' backups (i.e. ed, bd, bc ... etc) taken in S/W release 2_2_1_6, should not be restored in the Exchange after upgrading it to new software release 2_2_1_9.

9.3.6. While taking the display/printouts of TRUNK/ROUTE related traffic reports, the input against parameter MOD-NO should always be “AM”.

9.3.7. It is advised, not to put more than 40 TENs in a TGP. If it is required to have more than 40 trunks in a direction, create two or more TGPs and associate them as alternate choice in TGP-CHC parameter of a Route-Code.

9.3.8. Don't crash the IOP by resetting or switching - off the power supply. Always use CRP-Command INIT-IOP:2, 1; and then INIT-IOP:1,1; to shutdown the IOP.

9.3.9. Do not remove the floppy and cartridges from the drives till the drive's LED is glowing.

9.3.10. Do not remove the protection devices on the MDF and ensure that all the lines are having the protection (IPMs or GD-Tubes). If a protection device is removed for repair of the line, it should be replaced after repair. Also it should be ensured that IPMs/GD-Tubes make proper contact with the earthing strip of the MDF.

9.3.11. It MBM-Sites, do not create DTMF-ckts in TRUNK BMs and MF-Senders/ Receivers in Line-BMs.

9.3.12. Do not execute INIT-SYS command. In case of emergency, execute INIT-MOD for the specific modules. Also for Base-Modules, do not execute INIT-MOD with INIT-LVL as PI or higher level of initialisation, as this will cause all STD nos. to be locked.

9.4. OPERATION AND MAINTENANCE RELATED GUIDELINES

9.4.1. Restoration of BMDC

The BMDC cartridge should never be restored in day to day operation. Restoration of BMDC is required only when complete software is being loaded in the exchange. The restoration of "ed" backup does not require restoration of "BMDC". In case of data corruption when restoration of old exchange data is required, only "ed" backup restoration using command

Chapter 9

106 C-DOT DSS MAX

“COPY-IN” is sufficient. As and when BMDC has been restored in working exchange, "ed" as well "bd" must be copied.

9.4.2. Programming Trunk Groups in C-DOT DSS

Keeping in view the complexity of the network and multiple features being supported in the common software release for different configurations / applications of C-DOT DSS, the following requirements should be met at the time of creating a trunk group : ∗ All the incoming trunk groups from TAX or ILT should be programmed as

TTAX. ∗ All the incoming trunk groups from the parented exchanges should be

defined as ORD. ∗ If C-DOT DSS is configured as TAX/ILT, all the O/G trunks should be

defined as ORD if going towards a terminating exchange and TTAX if going towards a TAX exchange.

9.4.3. Calendar Programming in C-DOT DSS

To maintain consistency of alarms and reports for lines, trunks and service circuits. AUDIT with AUDIT-SET=12 should be programmed in the calender with daily triggers for all the days in the current year. This programming is required to be done only once in a year or every time when a software is loaded in the exchange.

9.4.4. Use of TSC PROMs in Different Exchange Configurations

When BMs of MAX-L are being integrated with MAX-XL or BM-XL are being integrated with MAX-L, then following care should be taken for use of TSC PROM. ∗ The checksum for TSC PROM will be same for BM-L as well as for BM-XL

if used as SBM-RAX or as colocated BM/RSU of MAX-L. ∗ The checksum for TSC PROM will be same for BM-L as well as for BM-XL

if used as colocated BM or RSU of MAX-XL.

Otherwise, we can conclude that the PROMs on TSC will depend on the type of CM i.e. CM-L or CM-XL and it is independent of BM-type.

9.4.5. TIC Cards with Compatible Software EPROMs

The C-DOT DSS supports distinctive ringing in all the new exchanges with retrofit option for existing sites. The software has been designed to take care of compatibility related problems. The exchange is defined to support “Distinctive Ringing” by setting the system parameter “SPL-RNG“ to 1. At these sites, all the PSUs should be updated for ECNs. Also the TIC cards

DO'S AND DONT'S


should be updated for compatible software EPROM. The TIC unit will not become INS unless compatible software EPROM is not used.

9.4.6. Mandatory Execution of MOD-DAY-TYP

It should be ensured that in 1P

stP week of January & July of every year, the

command is executed to define the day type.

9.4.7. Programming for Routing of Priority Subscriber's Call

In all the routes, priority 2 should be allowed by defining the trunk group choice against priority 2.

9.4.8. Proper Definition of 'CRG-RTNs' for all Tariff Classes

Charge Rate Number (CRG-RTNs) must be defined for all the tariff classes mentioned in the definition of Day Type 1 and 2. Other wise, call may fail during such time zones for which tariff class has not been defined in 'CRG-RTN' and this may cause system initialilzation also.

9.4.9. Precautions to be Taken While Handling Various Hardware Cards

i) With the introduction of "Distinctive Ringing" in C-DOT DSS, there are two different versions of PSU used in Analog Terminal Unit. One with blinking LED to indicate the ringing cadence which is used at the existing sites. The modified PSU is identified with continuous LED and used only at the sites where "Distinctive Ringing" feature is offered. The two PSUs can not be used interchangeably. Also in one exchange, only one version of Power Supply can be used.

ii) The SHM cards cannot be used interchangeably with BPC and HPC in SUM. To use SHM cards at the sites where HPC has been used as processor in SUM, ECN in the form of firmware changes are mandatory on SHM cards.

iii) For 32 signalling links, BPC is used as processor in CCS7 Signalling Unit. For more than 32 signalling links but upto 64 signalling links, only HPC is to be used as processor.

iv) In case of 800K BHCA configurations, HMS is used in all the BMs. HMS and MSC/MSD are not pin to pin compatible and can not be used interchangeably.

v) While changing any TUI card, proper jumper settings as mentioned in “Installation Document” should be ensured. The same is valid for BME cards used in CCS7 signalling unit (SUM) with HPC. Otherwise, it is same for BM, AM, CM and SUM with BPC.

Chapter 9

108 C-DOT DSS MAX

vi) While changing any Processor Card in BM, CM & AM, the jumper settings and EPROM status should be ensured.

vii) At the time of changing any controller card from some other site, PROMs of correct software version should be ensured before jacking the card into the system.

9.4.10. O&M Changes as a Result of Feature Enhancements

(i) A subscriber data can be modified only after making it OOS-OPR.

(ii) It is not possible to delete the subscriber in growth mode.

(iii) All the “Hunt Group” related CRP commands are possible only when IOP is ONLINE.

(iv) Due to enhanced disk partitioning, to utilize the full capacity of the disk, the boot up time for IOP has been increased to 30 minutes or even more depending upon the IOP and disk types, used.

(v) It is not possible to go to growth mode, when IOPs are in DUPLEX. This has been done to avoid data inconsistencies.

(vi) In case of TAX or ILT, the system has to be defined for TAX functioning by setting the parameters XCHG-TYPE = 4 and CLI-INFO = 1. If it is not so, the exchange will not support CLI for TAX functions in case of R2-R2 and R2-ISUP transit calls. In addition to exchange configurations, the incoming R2 trunk groups from parented stations should have CAMA=YES with TGP-TYP=ORD.

(vii) For ISDN subscribers, even if the subscriber has subscribed for CW facility, "Call-Hold" should also be subscribed as the facility works through "HOLD" and "RETRIEVE" messages.

9.4.11. Known Constraints and Possible Alternatives

1. While creating a trunk group, more than 40 trunks should not be given at a time. If more than 40 trunks are required in a trunk group, trunks can be added using ADD-TRK commands in the existing trunk group.

2. The status of more than 40 trunks cannot be displayed at a time in the same command. The range of terminals given in DISPL-TRM-STATUS should not be more than 40. Alternatively, the command DISPL-TRCNT-OOS can be used to know the breakup of more than 40 trunks. After that, DISPL-TRM-ALL can be used to find out the listing of trunks with a specific status.

3. In case of more than 100 trunks, MOD-TGP-CHAR does not work. Command is rejected with suitable error message. To modify the

DO'S AND DONT'S


characteristics, the no. of trunks should be reduced to U<U100. After modification, the deleted trunks should be added.

4. In few cases, modification commands for subscriber or Trunk Group Characteristics may fail with suitable error message, prompting the user for corrective measures. In such cases, the subscriber or trunks should be attempted once again to make them out of service.

C-DOT DSS MAX 110

Annexure - A

IOP Loading Procedure

The S/W for the SBM RAX comes in four cartridge tapes, which are labeled as Unix, BAC, CPC and BMDC. These names stand for Unix (Operating System), Base Cartridge, Combined Patch Cartridge and Bare Minimum Data Cartridge.

Step 1:

Power up the system and wait for the system to come to the monitor prompt.

IOCp.q> where p.q is the monitor prompt (say 7.0)

Enter the following command at the monitor prompt to boot the system from the unix cartridge, after inserting the cartridge in the drive.

IOCp.q > bo c

Following options will be displayed :-

Unix 11.6 OR Unix 11.7

0 lm.x.y 0 cx.pmthM 1 ve.x.y 1 txl.pmthM 2 vh.x.y 2 vh.pmthM 3 xle.x.y Enter Kernal no: Give the option depending on the type of IOP and unix release (say '2' for IOP-VH & '1' for IOP-VL) Msg will appear on the screen: MMU initialized ……… : : updating device files

Load IOP System Unix

IOP LOADING PROCEDURE


for IOP-ML or IOP-VE or IOP-XLE or IOP- TMC or IOP- VH (m/v/e/t/h)?

Input your choice depending upon the type of IOP. (say h for IOP-VH & v for IOP-VL)

It makes only ROOT file system for UNIX.

It does not disturb the other file system.

CURRENT DEVICE CONFIGURATION DEVICE TYPE NCRNO ID DEV-FILE DFLT-DV-FILE MONITOR- NAME

WINCH SCSI 0 1 W0s1_x - w0

CART SCSI 0 2 C0S2 m350_0t C

Only one WINCH present in the system.

Configuring the WINCH as rest device.

Format of WINCH is not required unless you are sure that the media is bad. If the WINCH is formatted, complete software must be loaded onto WINCH again.

The system would then display:

Want to format winch(s) (y or n)?

If disk capacity is 520/700/1200/2100 MB, then need not to format normally hence press "n".

The system would then display either of the following depending upon the type of the disks used:

Disk capacity in MB 1200/2100/4500/9000 • If formatting is required then press 'y' when asked 'Want to format Winch (Y

or N) ?' Disk will be automatically formatted, without asking for bad block information.

Formatting available for Disk #x

Want to format (y/n) ? • If 'y' is given the system displays the following and starts formatting the

winch:

Formatting winch #x .........

(In the above display, #x, would be #0 as only single disk is being used)

Wait till the following print appears :

Annexure - A

112 C-DOT DSS MAX

Formatting over ! • The system then displays :

Load the object (y/n) ? • Type y to continue the loading process or n to discontinue the loading process. • The system would then display the following :

Dev: 0x800xxSCSI : WARNING : BOOT BLOCK BEING WRITTEN

Making ROOT file system ........ • There would be delay at this option as the system makes the root files system

on the winch where the UNIX cartridge would be loaded. • The system then displays the following :

Loading the object ............. • This is followed by the list of files that are copied from the unix cartridge to

the winch. • After the complete cartridge has been loaded the system would carry out an

audit to check whether all the files have been copied to the winch correctly. • Wait till the process gets over. • The system would then display the following and carry out the check of the

root file system :

Checking ROOT File System • When the check is over the system would display the following :

Root File system Loading Complete Hit Reset, and Reboot from Winchester

Remove unix cartridge from the drive. • Press the reset switch on the front panel of the IOP. • After pressing the reset switch wait till the system comes to the monitor

prompt. • Boot from the winchester by giving the following command at the monitor

prompt :

IOC x.x> bo • After the system boots up it displays the following :

Specify the release for which system is to be configured.

Release 1_35_1_7(l3) or 1_4_1_3/1_4_1_4(l4) or 1_5_1_2/2_1_1_1/2_2_1_1 (l5) (l3 or l4 or l5) ?



Here enter 'l5' for 2_2_1_6/2_2_1_9 release. • The system would display :

Create file systems other than root (y/n) ? • Give 'y' to continue loading of software i.e., BAC, CPC & BMDC.

various file systems will be generated. This will take about 15 minutes. Then date format will be shown. Fill in correct date/time. It will show

• System Not in warm start level • Boot after Copying BC

Step 2:

The login prompt will appear as 'Console login : '

Login into root by typing

Console login : root <>

Password : DSSroot <>

Password will not be visible on the screen.

Wait for the unix prompt to appear as # >. Type

# > cd /usr/cdot<>

# > RESBC<>

A message will appear as

Have you inserted the cartridge (y/n) ?

Insert the Base cartridge into the tape drive and press 'y' then return. The loading of base cartridge will take half hour for IOP-VL and 20 minutes for IOP-VH. after which a message will appear as

Give the IOP id ( 0 / 1) :

Now type '0' for IOP-0 and '1' for IOP-1.

Press return also. The unix prompt will appear again after audit.

The login prompt will appear as 'console login:'

Login into root by typing: Console login : root < > Password : DSSroot <>

Annexure - A

114 C-DOT DSS MAX

Step 3 :

Remove the base cartridge and insert the combined Patch Cartridge (CPC). Type

# > cd /code/audit<>

# > RESPC<>

Press "Y" against the message "Have you inserted the cartridge"

The loading of patch cartridge will take approx 15 minutes in IOP-VL and 10 minutes for IOP-VH and after loading, the audit utility will check the loaded files and give the list of files missing from the system, changed in the system and extra in the system, if it finds any. Just press return a few times till you get the unix prompt back.

Step 4 :

Remove the patch cartridge and insert the data cartridge (BMDC).

Type

# > RESDC<>

Press "Y" against the message "Have you inserted the cartridge"

The loading will take only 5 min. and audit utility will show files missing, changed and extra in the system as none. At the end system will prompt for type of announcement required :

Language id :

Fill the required language identity against the message "language file to be copied? (00-09)" : Type 01 for English and Hind Announcements

Step 5 :

Remove the data cartridge from the drive and type

# > cd /<>

# > shutdown 0<>

Answer the question "want to continue?" by pressing 'y'.

Wait for the display to show "INIT : SINGLE USER MODE" and unix prompt followed by it. Press reset switch in the front panel of the IOP and the prompt will appear as

VHC 7.0>

Give the following command



VHC 7.0> bo <>

After console login appears login into admn account as follows

Console login : admn <>

Password : CDOTadmn <>

Now, the IOP will come to iop5c> or iop5d> prompt.

Go to CRP and set-site-id.

C-DOT DSS MAX 116

Annexure - B

Duplication Procedure for Cartridge/Floppy

It is required to make copies of cartridges and floppies at the sites. This can be done at the site itself, using “dd” command of C-DOT IOP. At the time of making the copies of cartridges, it should be ensured that the IOP on which copies are being made, is loaded with fresh S/W to ensure availability of sufficient disk-space. However, this is not required to make the copies of a floppy. Procedure 'A' is meant for copying single cartridge of BAC or CPC or BMDC. Procedure 'B' is for generating BAC, CPC & BMDC from the combined cartridge.

A. PROCEDURE FOR MAKING COPIES OF CARTRIDGE :

1. Shutdown one of the two IOPs, say IOP-0 using CRP-command INIT-IOP:2,1; and then INIT-IOP:1,1;

2. Load this IOP with complete S/W (UNIX, BAC, CPC & BMDC). Shutdown and boot it again. Login to 'root' account.

3. Insert the 'Master cartridge' in the cartridge drive of the IOP-0 and execute the following command from #> prompt;

#>mkdir /data/copy

#>cd /data/copy

#>ulimit 180000

4. #>dd if=$TAPE of=xxxx

This will copy the contents of the master cartridge, in to file 'xxxx'. After completion of copying process which may take 10 to 40 minutes, depending upon the block size of the cartridge, being duplicated, the total block size will be displayed which should match with that of master cartridge.

5. Now the user may generate as may copies as desired, by repeating the following process : ♦ Remove the master cartridge and insert the cartridge on which copy is

to be made.

DUPLICATION PROCEDURE FOR CARTRIDGE/FLOPPY


♦ Execute the following command #>dd if=xxxx of=$TAPE

After completion of the process (10 to 40 minutes), the block size will be displayed which should match with that of master cartridge.

By repeating STEP-5, generate as many copies as desired. To generate the copies of the other masters, start afresh from STEP-4. ♦ Remove file xxxx after required no. of copies have been generated.

#rm xxxx #cd /data #rmdir copy

B. PROCEDURE FOR MAKING COPIES OF BAC, CPC and BMDC Cartridge from COMBINED CARTRIDGE SUPPLIED BY C-DOT :-

A single cartridge having complete software (i.e BASE, CPC, BMDC, RGEN, EDRETRO UTILITY etc. )except UNIX will be supplied to the site. From this Cartridge, individual S/W Cartridge for BASE/CPC/BMDC/RGEN/ED Retro can be generated at site itself using following procedure.

Bring SBY /Spare IOP to Warm start Level. Login into ‘root’ account.

At UNIX prompt #>, execute the following commands

#> mate 1440 ↵

Make a new Directory:

#> mkdir /data/copy ↵

#> cd /data/copy ↵

#> pwd ↵ (should show /data/copy)

#> ulimit 300000 ↵

Now insert combined S/W cartridge in cartridge drive & copy the contents by following command.

#> cpio –icv<$TAPE ↵

#> ls –ls ↵

This will list all the files copied from Cartridge in this Directory. Note down the name as appear in this list on the extreme right column as the same will be used as filename later for making the individual s/w cartridges.

Annexure - B

118 C-DOT DSS MAX

Generation of Individual S/W Cartridge

Insert a blank Cartridge, and copy the required file to generate S/W cartridge using following command:

Say file name for BMDC of MAX-XL is ‘bmdc-xl’, then this will be generated by following command:

#> dd if=bmdc-xl of=$TAPE ↵

At the end, Block size of the Cartridge will be shown.

Once copying is complete,remove the cartridge & label it properly.

The contents can be verified by following command:

#> cpio –icvt <$TAPE ↵

Similarly other S/W Cartridges & any number of copies can be generated at the site.

PROCEDURE FOR COPYING UNIX 11.X CARTRIDGE : ♦ Before making copies, ensure that IOP is having unix 11.X loaded in it

and there is sufficient disk space. ♦ Login into root account and give following command on unix prompt. ♦ #cpcart $TAPE or # cpcart /dev/rmt/m350_0t

Following message will be displayed. Enter the cartridge to be copied Press RETURN to continue ......

♦ Insert the master unix 11.X cartridge in the drive and press RETURN. ♦ Unix cartridge will be rewound first and then actual copying of

contents will take place on the disk. No. of msgs will be displayed. In the end, message will appear :

Rewinding the Cartridge Insert the blank cartridge Press RETURN to continue .....

♦ Now remove the master cartridge and insert blank cartridge in the drive on which copy is to be made.

♦ The cartridge will be rewound and then files be copied on it. ♦ After copying is over following msg will appear. Copy another cartridge (y/n) : ♦ If another copy is to be made, remove the previous one and insert next

blank cartridge. Then press Y. ♦ After copying is over , press 'n'. Following message will appear :

DUPLICATION PROCEDURE FOR CARTRIDGE/FLOPPY


Wait .... removing files ♦ It takes some time to remove all the files, so please wait. Do not

interrupt file removing operation. The unix prompt will appear after some time.

COMMAND FOR DISPLAYING CONTENTS OF UNIX 11.X CARTRIDGE ♦ Login into root. Insert unix 11.X cartridge in the drive ♦ #cpcart -t $TAPE or # cpcart -t /dev/rmt/m350_0t ♦ When asked “display files in root file system (y or n)”

Press 'Y' ♦ This will display all the files in the cartridge and at the end total no. of

blocks will be shown.

C-DOT DSS MAX 120

Annexure - C

EPROMs for English Announcements Sl. No. Position English only

1. U14 E3F0 2. U17 B843 3. U24 4BD0 4. U29 2904 5. U37 6440 6. U45 F7BC 7 U48 A3B0 8 U56 41A1 9 U63 8160

10. U71 E5D0 11. U74 4C7B 12. U15 20BA 13. U18 A400 14. U25 -- 15. U30 -- 16. U38 -- 17 U46 -- 18. U49 -- 19. U57 -- 20. U64 -- 21. U72 --

NOTE : 1. EPROMs at Sl. No. 1 to 9 are the old ones used in P8.9 version. 2. EPROMs at Sl. No. 10 to 13 are new ones, which are to be

provided for additional announcements.

Language ID : 00 for English only Announcements

Contd...

EPROMS FOR BI-LINGUAL ANNOUNCEMENTS


Annexure - C (Contd.)

EPROMs for BI-Lingual Announcements

Sl. No.

Position Eng./ Hindi

Eng./ Oriya

Eng./ Bangla

Eng/ Assamese

Eng./ Kannada

Eng./ Malayalam

Eng./ Telugu

Eng./ Tamil

Eng./ Marathi

1. U14 ABF5 ABF5 687A 687A 613E E393 75FB F7DC 3A2B

2. U17 BF99 BF99 E664 E664 499B BB44 8994 4435 5573

3. U24 A505 A505 633A 633A 6AE3 C074 86FD F11C 1111

4. U29 ECA7 ECA7 99D8 99D8 CA5D F5A4 5AD1 159B 6DD5

5. U37 4905 4905 C076 C076 E5D0 8DEE 8A7D 70AE 93D6

6. U45 E63A E63A E0D6 E0D6 4C7B 3791 7A68 9EAA C755

7 U48 D96F D96F FA00 FA00 20BA 3DD7 EE9A 143F 709C

8 U56 E12A E12A D2F5 D2F5 A400 F1CB CE2B A031 1AC9

9 U63 F3D1 F3D1 991B 991B 603D 8C51 26A7 618D B544

10. U71 A211 A211 EC5B 90E2 F878 3468 C8BF 3039 974D

11. U74 0847 0847 7FDA 7B71 CAC3 1A27 896A FOE2 DCCE

12. U15 543D 7E9E C003 FEF7 134D C29C FC58 F11A OBB1

13. U18 5493 2F1B A7F5 B4F3 6837 6682 AE8F 0320 AB53

14. U25 50A9 AA93 E77E 0FB5 OD6C 8605 8D86 4D7O A1A5

15. U30 505B E837 1317 41C7 3DAD B3AD 6CDF 4639 6EC6

16. U38 2722 DF32 A610 4F56 4853 D094 5E92 2F98 2A3D

17. U46 70AC 8E9A DF80 F5E6 E351 2D33 FCC7 528B 9FF7

18. U49 06E1 63AC 7CCD BDCB DFA3 14F2 -- 84EE 2BFF

19. U57 C9D7 797F EF00 4040 2791 OB7C -- B563 2206

20 U64 8A82 1A6D -- AEF1 7EF2 9772 -- -- 9A21

21. U72 1D9D A974 EBD4 B07E -- 35A3 -- -- E151

22. U75 520D 8A82 4F3F -- -- -- E524

23. U19 -- BE74 -- 76AB -- -- -- -- D1EF

24. U26 -- A217 -- B6C5-- -- -- -- -- --

Language Ids 01 07 09 08 02 03 04 06 05

NOTE :

1. All the EPROMs are 27C512 (200 nsec).

C-DOT DSS MAX 122

Annexure - D

Addition of Base Module

D.1 INTRODUCTION

It is assumed that before attempting the BM-addition activities, all the requirements of additional hardware, as listed in Chapter 4 has been met. It is recommended to place the new additional Trunk BM in Rack Position 1 or 2 or 3 (as the case may be) in the 2nd suite. In some exceptional cases, where it may not be possible to place the Trunk BM as recommended above, the same can be placed in any other convenient place available in the suite. After physically installing the BM, complete the following activities step by step : However in case of Line BM, the placement of Base Module should be such that two Line Modules (One on each side) can be connected with the BM to other 2000 Lines by adding one Line BM alongwith two LMs.

D.1.1 Physical Installation

♦ Power/Earth cables from PDP of the suite to the BM Rack. ♦ BM-CM Data Cable and BM-CM clock cables from CM to the BM-Rack.

At the time of laying down the BM-CM Data Cables and clock cables, it must be ensured that they are properly terminated at the right termination point as listed in C-DOT DSS MAX INSTALLATION MANUAL. Otherwise the added TRUNK BM will not get initialised. ♦ Set the jumper settings at the Back. Plane (Mother Board) of the Base

Processor Unit as the logical BM-NO being configured in the Main Exchange.

This completes the physical Installation and interconnection of Trunk BM with CM. Parallely the trunk cables can be extended from the Rack to MDF.

Now switch on the trunk BM and follow the procedures listed below to equip the base module and to create the necessary data.

D.2 EQUIPPING THE NEW BM

The procedure to equip the new base module in MAX-L/MAX-XL exchange is off-line where the BM is equipped and data is created in growth mode at warm-level IOP without updation in the exchange and after completing the data base

ADDITION OF BASE MODULE


creation at the IOP, it is updated to the exchange memory by low level (part-init) initialisation of the complete system, which results in total system downtime of approximately 10 minutes. It is recommended, only off-line procedure should be followed to avoid any data inconsistency. Also, it should be tried out in low traffic hours. ED and BD should be taken before starting the addition.

D.2.1 Off-Line Addition of A Base Module

1. Start with both IOPs in duplex. Take ED & BD backups.

2. Bring SBY-IOP (say IOP-1) to warm start level by INIT-IOP: 2,1; command. Create data regarding new BM in for IOP-1 in 'GROWTH MODE'.

3. Equip the new BM (say BM No. 6) in Growth mode by following command:

<EQUIP-MOD

Config = MAX-L or MAX-XL

Mod-No = 6

Ver-No = 1 or 2

[MOD-TYP] = Normal or Remote

[DTK-id] = <default> or (1&2&17&18)

Execute.

After the command gets executed, verify following

i) DISPL-SYS-ALL : 6;

ii) DISPL-MOD-INFO : 6;

If the information is correct, go to next step.

4. Equip frames as per requirement, using command 'EQUIP-FRAME' and giving correct TIC-IDs to various frames of BM/LM1/LM2.

5. Equip TTC/ANNC using 'EQUIP-SRV-CARD' in the correct slots. In case of DIGITAL BM, only 'ANNC' should be equipped.

6. Equp MFC1, 2, 3, 4 cards with required No. of MF-sender and MF-Receivers in case of TRUNK BM and only DTMF circuits in case of LINE BM.

7. Equip Terminal Cards LCC/CCB/DTK etc. - as per requirement. For equippage of LCC/CCB type terminal cards 'equip' utility in /u/admn/ cmdfile can be used.

Annexure - D

124 C-DOT DSS MAX

8. Once all the terminal cards have been equipped and verified using 'DISPL-TEN' for 'EQUIP' option, SUB's Data or TRUNK data creation can be started.

For subscriber creation, 'create' utility lying in /u/admn/cmdfile can be used, by which first command files can be generated and then these command files can be run in Growth Mode to create SUB's Data in bulk.

9. Physically install new SSM/PSM cards in BTU corresponding to the new BM and SSS/PSS cards in SSU if required. Do make corresponding SS plane OOS-OPR before replacing SSS/PSS cards.

10. Now give command <del-fgp-file:, ioh;

Then take 'ED' backup using 'COPY-OUT' command from IOP-1, in which new BM data has been created.

11. During Night hours, take 'BD back up from Active IOP-0, with required dates for Detail Bill Record and restore the same in IOP-1.

Shut down and reboot IOP-1, to warm start level.

12. Now bring Active IOP-0 to warm start using command <INIT-IOP:2, 1;

Then execute command <INIT-IOP:5, 1; from IOP-1 in which new BM data has been created.

13. Once IOP-1 becomes INS-ACT and critical alarm of IOP changes to urgent, give following command -

INIT-SYS: , PART-INIT; ∗ MLF LED will glow on ADP and complete system will go for

initialisation up to 'PART-INIT' level. ∗ All the LEDs/Alarms on ADP will be cleared one by one except that for

newly added BM-6. ∗ New BM-6 will go for code-loading along with message on console

terminal of IOP-1. "Code Loading Begins. . . . . ."

∗ Wait for the local pass report of the new BM and then make all the MFC cards, ANNC & TTC INS-ACT.

∗ Make intra / inter BM calls from new BM and verify charging. Also verify voice quality with both SS planes with respect to both BUS-0 & BUS-1.



D.3 X-COD MODIFICATION IN 2_2_1_6

A new off-line utility has been provided to modify an existing exchange code to a new exchange code. Procedure for modifying x-cod is as follows before starting the actual procedure do the following :

1. Copy-out the 'ed' & 'bd' backup.

2. Check the disc space in iop in /code directory

Minimum 3000 block require in case of SBM. Minimum 12000 block require in case of MBM.

3. Shut down the SBY-IOP (say iop-1) & start x-code modification procedure in warm level of IOP-1.

4. Withdraw Sub facilities 'Hot-Line' (Timed/untimed) and 'Absentee-Selected No' (Call Diversion of any type) if given to any Nos.

5. Delete `DID' routs available if any.

6. Delete routs starting with level which is same as that of New X-code.

Procedure

iop5D>cd /code/tool ↵ iop5D>agmxcd.sh <old x-code1> <new x-code1>

Example: If old x-code is 21 we require to change it to 22.

i.e. iop5D>agmxcd.sh 21 22

On screen it will display

"EXCHANGE CODE MODIFICATION UTILITY"

"Number of Exchange code to be Modified : X"

(where X is the No. of exchange codes, which we want to modify).

"Old Exchange Code New Exchange Code"

Old x-cod1 New x-cod1 .. ... .. ..

Confirm (y/n) :

give y if you are confirm to change the x-code otherwise give n & it will come to iop5D>. Now on screen following message will come :

Annexure - D

126 C-DOT DSS MAX

"Minimum disc space requirement"

SBM : 3000 block MBM : 12000 block Current disk space : xxx block Is disk space enough ? (y/n) :

(Give y if disk space is enough)

Now list of files will display with the following end message :

"UPDATES SUCCESSFULLY OVER FOR ALL FILES"

"Do you want to copy new files to required files (y/n) : y

"The files are going to be moved now !"

"Are you sure, you want continue (y/n)" :

Give y, then it will display the list of files which are updated with new files.

abexcd. apdatb. .. .. .. ..

At last message will display

"Run copy out (FGP = x-cod) to copy files :" • Verify following things in growth mode.

∗ Displ-Xcod and 'Displ-rbm-Xcod' shows modified Exchange Code ∗ Displ-Sub. for few Subs in all the BMs or take `Sub-list' of all BM's. ∗ 'fmt-blg-cntr' and 'rgen submtr2' to verify meter reading against modified

Sub Nos (sample check only). ∗ Verify Special Routs with Alt. Nos. & ILT routs for I/C calls to exchange.

• Now bring the active iop (IOP-0) to warm start level using INIT-IOP command <INIT-IOP : 2,1;

• Take `BD' back up from IOP-0 for required period. • Copy in this `BD' in IOP-1 having modified data. • Bring iop-1 to INS-ACT level using <INIT-IOP: 5,1; • Give a part-init to the system from iop-1 by command <INIT-SYS:IOP-1, 3;



• Once system has recovered completely verify Local, O/G & I/C calls and their charging.

Caution : In case of any error message noticed while carrying out X-code modification. Consult C-DOT before proceeding further.

Note : 1. Keep other IOP-1 in warm start with old ed for minimum 24 hrs and then synchronize it.

If the exchange code length is increased using the existing codes & digit to be prefixed is same as that of xcod, e.g. the existing code 22 & to be modified to 222 then the above utility is do be run twice. First modify the exchange code 22 to some unused level x (say it is 55) and then 55 to 222. There should be no route corresponding to Lev. 5.

Note : 2. In case there are 4 exchange codes say 20, 21, 22, 23 and these are to be modified to 220, 221, 222 & 223 respectively. In such a case following sequence should be adopted.

1. 22 --> 55 (Any unused level)

2. 20 --> 220

3. 21 --> 221

4. 23 --> 223

5. 55 --> 222

C-DOT DSS MAX 128

Annexure - E

Optimized Utilization of PHC Terminal in VU

The only growth element in VU is the SHM card. SHM card contains Protocol Handler Controller (PHC) terminal, which can be configured as signalling terminals or internal message protocol (C.85) terminals. Out of the 8 PHC terminals available per SHM card, two (2) C.85 terminals are used for internal message communication of the VU with the processor of the BM in which it is equipped. The remaining terminals are available for utilization of C-Channels for each AI interface to be created. Two terminals per AI will be utilized, if both primary and secondary links are created.

The utilization of C.85 terminals for C-Channels is governed by system parameter "V5-THR". The default value of this parameter in BMDC is 50 (percent). Hence, out of the eight (8) C.85 terminals available per SHM card, four (4) terminals can be used for C-Channel and out of the remaining four (4) terminals, two (2) are utilized for internal message communication of the VU with the processor of the BM in which it is equipped. Hence two C.85 terminals are left spare. So, with one (1) SHM card equipped, we can create only two AI with both primary and secondary links of each AI inservice. If status of any of the four (4) PHC terminals goes OOS-SE, due to same hardware problems then we are left with only four (4) PHC terminals, two (2) for internal communication and two (2) for C-Channels. So, either the primary of both the AI will be inservice and secondary of both the AI will be down or only one interface can be up. To utilize the available C.85 terminals in a proper manner, we can set the system parameter 'V5-THR' to 75 (percent), which will give six (6) C.85 terminals for C-Channels. Set the value of system parameters VU-INT-THR to 25. The sum of parameters V5-THR + VU-INT-THR. But it is advised that at least two (2) SHM cards should always be equipped so that if status of some of the PHC terminal goes OOS-SE, the interface do not go down. By using two (2) SHM cards, we get 16 C.85 terminals out of which 12 terminals can be utilized for C-Channels and four (4) terminals or internal communication (with the value of system parameter V5-THR = 75). Hence, if three (3) interfaces are created with both primary and secondary link inservice, six (6) C.85 terminals are utilized. Still we have six (6) C.85 terminals spare for C-Channels and two (2) C.85 terminals spare for internal communication.


Annexure - F

Use of Subscriber Based Category for WLL Subscriber

The WLL subscribers of each SDCA are a part of different AN interfaces. Each of these AIs is given a unique interface category for Charging and Network access purpose.

Now, it is possible to provide a different category to all subscribers including WLL subscribers, while creating subscribers. So, all WLL subscribers of one BSC can use only one interface between LE and BSC.

Referring the case of Balasore SSA indicated in figure, to implement subs category based charging, following data modification will be required:

Step 1 : MOD-SYS-PARAM PARAM-NAME : SUB-CHRG-CTG PARAMETER VALUE : 2

Execute to enable subscriber category based charging. This will render BM-CAT and AI category ineffective.

Please note, if an RSU is working with different BM Cat = X (other than 1), provide category X to all subscribers of RSU by Command MOD-SUB-CHAR.

Once the value of system parameter SUB-CHRG-CTG is made equal to 2, the system parameter PCO-MTR-LCL will no longer be effective. This parameter governs the charging for intra exchange calls originating from CCB (ordinary) lines. The value given against this parameter indicates the charge rate number which may be given as per site requirement to govern the charging of intra exchange calls. Let us say the value of system parameter PRO-MTR-LCL is N. Now if it is desired that the charging of all the subscriber whose LIN-TYP is CCB (ordinary) should be governed by charge rate number N then we will have to first modify the category of all these subscribers to a unique category say Y, i.e. Y should not be assigned to any TGP or any other subscriber. After the category of all the subscribers with LIN-TYP as CCB (ordinary) is modified to Y using the command MOD-SUB-CHAR, then the command MOD-SUB-CRG has to be used for all the subscribers and TGP categories to which calls from CCB (ordinary) lines are allowed. The parameter required for command MOD-SUB-CRG are as follows:

Annexure - F

130 C-DOT DSS MAX

1. CLNG-CAT: Y (category assigned to CCB subscribers) 2. CLLD-CAT: 1 (one) 3. CRG-RTN: N (The value of system parameter PCO-MTR-LCL) The command has to be repeated for all the CLLD-CAT as explained earlier.

Step 2: All WLL subscribers should be deleted first, to delete interface.

Step 3: Delete all AIs (interfaces) i.e., AI NUM = 1,2,3,4,5.

Step 4: Create one AI with required parameters and AI-CTG as Default (i.e. 1).

Step 5:

Create WLL subscribers by CRE-SUB command and give unique category against parameter SUB-CTG = (say 21 for Balasore, 22 for Bhadrak, 23 for Basta, 24 for and bali and 25 for Soro).

To use this feature, some modifications may be required at BSC end also. Consult the WLL technology administrator for the same.

MAX-XLLE BSC

BTS

BTS

BTS

BTS

BTS

Area Code: 0678460XXXSDCA BHADRAKSubs. Cat = 22

Area Code: 0678161XXXSDCA BASTASubs. Cat = 23

Area Code: 0678663XXXSDCA CHANDBALISubs. Cat = 24

Area Code: 0678865XXXSDCA SOROSubs. Cat = 25

66XXXSDCA BALASORESubs. Cat = 21

Area Code : 06782Exch. Code : 3xxxx

V5.2 Interface

Network ofBalasore SSA

Fig.1

Note: For a new installation step 2 and step 3 are not required. New installation means that data related to Access Network (AI & WLL subscribers) is not existing in LE.


Annexure - G

Abort Filter Card (AFB) ECN Details

Note 1: If a BM using HMS card in TSU is being used to provide V5.2 Interface, then Abort Filter Cards (AFB) used in TSU should have Engineering Change Note (ECN) 12311 implemented on them in the field. Some cards already have the ECN implemented which requires one strap on the soldering side and one resistance on the component side.

Details are as under:

Strap U4 (Pin3) to U11 (Pin12) on the soldering side. Resistance (R31) 470 Ω ¼ W 5% MFR mounted between Pin12 and Pin 16 of IC Position U11 on the component side.

The details given in Fig1. shall help identify whether AFB cards are with or without ECN implemented. These cards are used in every BM’s TSU. The recent supplies of BM-XLs may already have the ECNs implemented on their AFB cards. LE sites are advised to look for the AFB cards with the ECN. The ECN, in effect, inserts a pull up resistance R31 between pin 3 of U4 and Vcc (which can be pin 16 of U11 or 14 of U4). The actual implementation can differ visually from site to site. It should be ensured that the TSU of the BM with the VU is equipped with the right AFB cards i.e. ones with ECNs. It would be a good idea to mark the good VU AFBs with a tag to lessen possibility of use of a non-ECN AFB from other BMs.

Annexure - G

132 C-DOT DSS MAX

Fig.1: View from Component Side

U3

U4

U5

U10

U11

U12

CardEjectors

Rev. Euro FemaleConnectors

Position ofResistance (R31)

1

89

16

ICs mounted on positions U3, U4, U5, U10

and U12. Position U11 is blank

If such AFBs are not available, ECN will need to be implemented on them.

Note:2 In case of VU in BM equipped with MSC+MSD in TSU, AFB cards without ECNs can also be used. In such cases, only three MFC cards should be equipped in the TSU instead of four. If four MFCs are currently being used, unequip one and reallocate the resources of the remaining three.

Note 3 To implement the IN feature in 2_2_1_6 S/W DTMF Circuits are required in all type of BMs. To take care of such requirements, slot numbers xx-1-6-5 (MFC1) and xx-1-6-22 (MFC3) are modified from old S/W equipage as follows by the utility. However if IN functionality is not desired then equipage of MFC cards in TRUNK BMs may be modified to include only MF-SNDR and MF-RCVR. But care has to be taken that the V5.2 BM should have DTMF circuits.

Slot number Block-I Block-II Block-III Block-IV

xx-1-6-5 DTMF DTMF MF-SNDR MF-RCVR xx-1-6-22 DTMF DTMF MF-SNDR MF-RCVR


Annexure - H

New Implementation on NSC and Fault Isolation Strategy

H.1 INTRODUCTION

Main problems observed due to disturbance in the NSC output are as follows: • General or Random noise in the Voice Calls. • Disconnection/Slow speed of Internet and Data Calls. • Frequent ETE failure of CCS #7 Module. • Digital Trunks becoming OOS-SO. • SS planes of CM becoming INS-FRC and OOS-SUS. • ETE failure of some BMs breaking (mainly RBMs)

To overcome these problems, various ECNs i.e. ECN 15109, 15105, 15114 were implemented in CM-XL with following details:-

ECN 15109: Noise problem in Inter-BM calls & CCS#7 instability in CM-XL when the BM equipage is more than 16 and most of the Even BMs (i.e. RBMs) are equipped while the Odd BMs remain unequipped.

Major changes in case of ECN 15109 are: • Putting of Loop Back Connectors for the vacant odd BM position. • Change of Resistor Network in ACP Card. • Change of EPLD in ESM Card. • Introduction of BSR Child Card on PSM Card. • Introduction of STM Child Card on ESM Card.

ECN 15114: Noise in the ring back tone and voice path in CM-XL, with EUA-FS03130A-060 at U62,U63, and U65 on PSS card instead of 3120 device.

This has been taken care by changing the device program at U64.The checksum of U64 should be 9BE9 instead of CCD4/C53F. In case device is 3120 or 3020, then no change is required at U64.

Annexure - H

134 C-DOT DSS MAX

ECN 15105:Resistor of 2.0KΩ, 1/4W 5% MFR should be inserted at R58, R66 in ESM Card for the Noise in RSU.

Despite above ECN implementation, some 'NSC' related problems are difficult to isolate and only means to find out the fault is to change the NSC card one after the other. As there is no inbuilt tool to measure the Clock output, it’s difficult to conclude whether NSC card is actually faulty.

H.2. NEW IMPLEMENTATION ON NSC

In 2_2_(7.7)_6 Software Release, a new feature has been introduced as a tool for the measurement of clock accuracy with respect to active copy. Some pending problems have also been resolved in this new s/w release.

Features: • Swing Detection feature has been implemented for the Crystal Swing

problem in NSC card or Swing in the Reference Clock (explained in details later).

• Detection of Oscillator Power Supply failure of NSC card.

Problems Resolved: • ETE failure of Some BMs during the Interchange of SS Plane

Reason: IFC tuned to Standby copy of NSC. It was observed that sometimes when we interchange Switch plane or NSC, IFC remains tuned with previously Active clock (which is now standby after interchange). As the system data path and clock path will be different, this causes problems like non synchronization etc.

For proper synchronization in the system, IFCs should be tuned to active NSC card only. As data flows in ACT paths only and if clock is extracted from standby path then synchronization may not be maintained between receive and transmit mode. This results in noise in Voice calls or disconnection of Data Calls.

• On giving interchange to SS plane, CCS#7 links and links between BM and CM goes down.

• SS plane not coming INS-ACT state after power on of SSC. • SSC card goes suspect during DGN of NSC card.

H.3. CRYSTAL SWING DETECTION FEATURE AND FAULT ISOLATION

The root cause of the problem is due to crystal oscillator which behaves abnormally sometimes. Since NSC PLL tries to lock onto the reference clock, the output of VCO is affected by the erratic behavior of the self clock of the crystal. However this may also occur due to reference clock also in case the reference itself is bad.

NEW IMPLEMENTATION ON NSC AND FAULT ISOLATION STRATEGY


H.3.1 Case I : No Reference Clock Equipped

The Architecture of CM-XL Clock distribution (without Reference Clock)

COPY 0 (ACT) COPY 1 (SBY)

Fig. H.1

If there is no Reference clock equipped (i.e. no network synchronization) then the implementation of clock swing detection is as follows: -

For the detection of Crystal Swing the mandatory requirement is the availability of two clocks. As per implementation, the NSC of Active copy of SS plane feeds clock to system through IFCs and SWCs. Also the active NSC feeds clock to standby copy of NSC as duplex clock so that the standby is in synchronization with active for the smooth switchover from one copy to another, however the duplex clock from standby NSC is not honored by Active NSC.

Thus there are two clocks available for standby NSC (Self Clk & Dup Clk) and only one clock (Self Clk) is available to active NSC. This means the swing is always detected in standby copy of NSC.

If there is a swing in standby crystal, the Self Clock is disturbed with respect to duplex Clock and the system reports crystal swing. Similarly if there is a swing in active crystal the Duplex Clock is disturbed with respect to Self Clock and the system reports crystal swing.

If a crystal swing is detected for 10 minutes, following report is displayed on ood/printer:

Crystal Swing Detection Report

Unit Id : Clk 0 or 1*

Crystal Swing Detected

Change NSC card

Dup Clk

Dup Clk

CCK

N S C

N S C

CCK O/P Clk to

System i.e. IFCs/SWCs

O/P Clk to System i.e. IFCs/SWCs

Clk O/P Clk O/P

Slf Clk Slf Clk

Annexure - H

136 C-DOT DSS MAX

* The Unit id will always be the number corresponding to SBY copy of NSC.

In DISPL-OOD-LOG command, one new type of report option is available i.e. Rep-type: mnsrep(204) which helps to view the Crystal Swing Detection Report

On detection of this swing following possibilities exists.

POSSIBILITY 1 : One Card out of Active/Standby is Bad.

POSSIBILITY 2 : Both Cards in Active and Standby are Bad.

Procedure to isolate the Faulty Card : (Possibility 1)

STEP-1

a) Replace the standby card with a new good card.

b) Jack-in the same and warm-up for an hour.

c) Put the card in-service using PUT/FRC command after DGN.

There may be following Observations :-

OBSERVATION 1 : No swing detected after replacement and it remains ins-sby

CONCLUSION : Standby card was bad.

OBSERVATION 2 : Swing detected again within 10 minutes after the replacement of NSC card.

CONCLUSION : Active card may be bad.

In case of Observation 2, follow procedure given in step-2 below.

STEP-2

a) Force an SS interchange.

b) Active card will now become Stand-By.

c) Make standby copy OOS-OPR.

d) Replace the standby card with a new good NSC card.

e) Jack-in the same and warm-up for an hour.

f) Put the card in-service using PUT/FRC command.

OBSERVATION : No swing detected

CONCLUSION : 1) Previously active NSC card is bad.

NEW IMPLEMENTATION ON NSC AND FAULT ISOLATION STRATEGY


(ACT) (SBY)

2) Card removed from the system as Standby in Step-1 may or may not be bad.

Procedure to Isolate the the faulty card : (Possibility 2)

STEP-3

Replace the Standby card with NSC card which was ins-sby in the system initially and was removed in the Step-1.

Wait it for warm up time (approx. an hour)

Put the card in service

OBSERVATION 1: No swing detected

CONCLUSION : Initial card in standby copy is OK.

OBSERVATION 2 : Swing detected again.

CONCLUSION : Initial card in Standby copy is also bad. Replace the same with a good card.

Take observation at least for a day or two.

Then put the Reference Clock in service. It has been observed that the system stability improves if only one reference clock is equipped and the same reference is given to both NSCs.

So it is recommended to equip only one Reference clock (Rclk0) and ideally any reference clock that shows one fault/failure in a day should not be used.

H.3.2. Case II: Reference clock equipped

The Architecture of CM-XL Clock distribution (with Reference Clock)

COPY 0 COPY 1

Fig. H.2

Clk O/P CCK

N S C

Act.

N S C

Sby.

CCK O/P Clk to

System i.e. IFCs/SWCs

O/P Clk to System i.e. IFCs/SWCs

Clk O/P Dup Clk

Dup Clk

Ref. Clk Ref. Clk

Slf. Clk Slf. Clk

Annexure - H

138 C-DOT DSS MAX

If there is a Reference clock equipped (i.e. Network synchronization has been done) then the implementation of clock swing detection is as follows: -

As already told that for the detection of Crystal Swing the mandatory requirement is the availability of two clocks. If the reference clock is equipped then the Active NSC gets one clock as reference clock (Rclk) and tries to lock with the reference clock, however the reference clock input to standby is not honored. Rest of the procedure is same as explained in the case of no reference clock equipped.

There are two clocks available for standby NSC (Self Clk & Dup Clk) and also two clocks (Self Clk & Rclk) is available to active NSC. This mean the swing is detected now in both the copies of NSCs.

If there is a swing in Reference Clock, the Self Clock disturbed with respect to Reference Clock and the system reports crystal swing and vice-versa may happen. Similarly if there is a swing in active crystal the Duplex Clock disturbed with respect to Self Clock of Standby and the system reports crystal swing and vice-versa may also happen.

Whenever there will be disturbance in the external clock, a swing will be detected both by the active and standby NSC cards. UCrystal swing Detection Report will be displayed on OOD twice one due to Active copy and the second due to standby.

Procedure to isolate the faulty card.

Whenever external clock is equipped and Crystal Swing Detection Report comes on OOD, first remove the external clock and allow system to work on the NSC card clock. Wait for a fresh Swing Detection Report on OOD. If no swing is detected then the fault is in the Reference clock and if swing is detected then the fault is in one of the NSC cards. Isolation of faulty NSC card has already been explained.


Annexure - I

Changes Required to be made to Run CTS-B Tool in 2_2_1_9 Software

Come to IOP5x prompt and give the following commands

Step 1 : IOP5x> cd $ABPEXE

Step 2: IOP5x>pwd

the response should be

/code/abpexe

else repeat step 1

Step 3 : IOP5x7> grep CTSBENT *.map

The following response will come

zzzxxxcts.map:CTSBENT 0XABCDEF

Note down the address 0XABCDEF

Step 4 : IOP5x> cd $CTSBP

Step 5 : Use command pwd as indicated in step 2 and ensure that you are in /u/tool/ctsb directory or else repeat step 4.

Step 6 : chmod +w ctsbi

Step 7 : Use vi editor for editing the file ctsbi

IOP5x> vi ctsbi

Step 8 : Search for pattern CTSBENT

:/CTSBENT

At line number 69 and 70 in this file the contents will be displayed as follows.

0) CTSBENT = XXXXXX

1) CTSBENT = YYYYYY

Annexure - I

140 C-DOT DSS MAX

Step 9 : For SBM replace XXXXXX with the address noted at step 3 or for MBM replace YYYYYY with the address noted at step 3.

Step 10 : Save the file and quit

: wq!


Annexure - J

List of Charge Rate Numbers

Following Charge Rate Numbers are available in BMDC defined for BS=1,2,3:

Charge Rate Number = 0 TRF CLS

INIT CHARGE

CHARGE PERIOD

PRD CHARGE

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO

1 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 2 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 3 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 4 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 5 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 6 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 7 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 8 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 9 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP

10 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP 11 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP

12 1 0 0 FXD METERD ANS-XP NRM-RING NO-BEEP

Annexure - J

142 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO

1 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 2 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 3 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 4 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 5 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 6 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 7 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 8 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 9 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP

10 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 11 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 12 0 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO

1 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 2 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 3 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 4 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 5 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 6 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 7 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 8 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 9 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP

10 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 11 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP 12 1 0 0 PRD-TAX METERD ANS-XP NRM-RING NO-BEEP

LIST OF CHARGE RATE NUMBERS



Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO

1 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 2 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 3 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 4 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 5 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 6 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 7 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 8 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 9 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP

10 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 11 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP 12 0 0 0 NO-MET NON-MTRD ANS-XP NRM-RING NO-BEEP


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO

1 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 2 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 3 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 4 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 5 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 6 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 7 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 8 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 9 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP

10 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 11 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP 12 0 0 0 NO-MET METERD ANS-XP NRM-RING NO-BEEP

Annexure - J

144 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO

1 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 2 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 3 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 4 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 5 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 6 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 7 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 8 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 9 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP

10 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 11 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP 12 2 3 2 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

146 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO

1 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 2 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 3 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 4 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 5 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 6 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 7 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 8 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 9 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP

10 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 11 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP 12 0 0 0 NO-MET NON-MTRD NANS-XP NO-RING NO-BEEP


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



*Charge Rate Number = 13 TRF CLS

Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

148 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

150 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Charge Rate Number to be associated for SAARC countries


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

152 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



This Charge Rate number is to be associated for countries in Africa, Gulf ,Asia & Oceania


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



This Charge Rate Number is to be associated for all countries in America


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

154 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



This Charge Rate Number is to be associated for all the EUROPIAN Countries


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

156 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

158 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO






Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - J

160 C-DOT DSS MAX

*Charge Rate Number =53 TRF CLS

Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO





*Charge Rate Number =47 TRF CLS

Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO




INIT CHRG

CHRG PRD

PRD CHRG

CHRG MODE

MET INFO ANS INFO

RING INFO BEEP INFO

1. 0 1200 1 PRD-LCL METERD ANS-XP NRM-RING NO-BEEP












Annexure - J

162 C-DOT DSS MAX

Charge Rate Number = 51 (BS1/BS2/BS3) TRF CLS

INIT CHRG

CHRG PRD

PRD CHRG

CHRG MODE

MET INFO ANS INFO

RING INFO BEEP INFO













SWR2219(2.22)

Documents

charge rate

abort filter

software release

29 hssc1 xxxmc222

software release

dot control

software release

charge rate