Retro 2216

C-DOT DSS MAX

SOFTWARE RELEASE 2_2_1_6

RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX

System Practices

Section No. 400-643-0873

Draft 02, July 2003

C-DOT DSS MAX

SOFTWARE RELEASE 2_2_1_6 RETROFIT PROCEDURE FOR

MAX/SBM-RAX/TAX

© 2003, C-DOT Printed in India

C-DOT DSS MAX

SOFTWARE RELEASE 2_2_1_6 RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX

DRAFT 02

JULY 2003

KARTIKA 2060

SERIES 600 : SOFTWARE

CSP SECTION NO. 400-643-0873

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 (SYSTEMS), CENTRE FOR DEVELOPMENT OF TELEMATICS, 39, MAIN

PUSA ROAD, NEW DELHI - 110 005

© 2003 BY C–DOT, NEW DELHI.

Table of Contents

Chapter 1. Introduction & Release Highlights..........................................................................................5 1.1. SBM RAX/TAX and C-DOT DSS MAX .........................................................................5 1.2. software release 2_2_1_6 (2004)....................................................................................6 1.3. Important features of previous software links ...........................................................15

Chapter 2. Software and Hardware Status .............................................................................................18 2.1. Software status.............................................................................................................18

Chapter 3. Software Retrofit Philosophy and Pre-Retrofit Checks .......................................................26 3.1. General Considertions .................................................................................................26 3.2. Pre-Retrofit Checks......................................................................................................27

Chapter 4. Retrofit Procedure (from 2_1_1_1 to 2_2_1_6)......................................................................28 4.1. Software Retrofit Procedure ........................................................................................28 4.2. procedure to extract existng data from 2_1_1_1 s/w..................................................28 4.3. Back-up of Command Files Generated .......................................................................30 4.4. Loading of New Software Release 2_2_1_6 in IOP-0 .................................................31 4.5. Creation of Data in 2_2_1_6 Environment .................................................................31 4.6. Post Data Creation Checks and Updation..................................................................32 4.7. Initialisation/Booting up the System with S/W 2_2_1_6 ...........................................36 4.8. Post-Retrofit Checks ....................................................................................................37 4.9. Recovery Action ............................................................................................................38 4.10. Retrofit Completing Activities...................................................................................38

Chapter 5. Retrofit Procedure for S/W 2_2_1_6 at Sites Already having S/W 2_2_1_3/2_2_1_4 .........39 5.1. S/W RELEASE 2_2_1_6 DELIVERABLE STATUS ..................................................39 5.2. Retrofit Procedure for C-DOT Exchanges having S/W 2_2_2.10_3...........................40 5.3. Retrofit Procedure for C-DOT exchanges having s/w release 2_2_(4.4)_3/2_2_(4.3)_4/2_2_(4.4)_4.......................................................................................41 5.4. New Time Zones and Tariff Classes for Holiday & Normal Day .............................45 5.5. Verification of Charge Rate Number ..........................................................................49 5.6. Command file creation for ISD routes in order to implement ‘PRD-LCL’ charging for ISD calls.............................................................................................................................50 5.7. Now modify definition of Day Type 1 and 2 as per Table I, using command ‘MOD-TYP-DAY’ ................................................................................................................................50 5.8. Implementation of Distinctive Ringing feature .........................................................51

Chapter 6. Do's and Dont's .......................................................................................................................52

6.1. IOP Related Problems and Solutions..........................................................................52 6.2. Do's and Dont's for Card Handling .............................................................................56 6.3. GENERAL - DO'S AND DON'TS FOR o&m ACTIVITIES .......................................57 6.4. OPERATION AND MAINTENANCE RELATED GUIDELINES ............................58

Annexure - A IOP Loading Procedure ..........................................................................................................63

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

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

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

Annexure - D Addition of Base Module ........................................................................................................74 D.1 INTRODUCTION.........................................................................................................74 D.2 EQUIPPING THE NEW bm........................................................................................74 D.3 x-cod modification in 2_2_1_6......................................................................................77

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

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

Annexure - G Changes Required to be made to Run CTS-B Tool in 2_2_1_6 Software ............................83

Annexure - H List of ISD Routs ....................................................................................................................85

Annexure - I List of Charge Rate Numbers ................................................................................................88

H:\HOME\MAX-XL\WORD\SWR2216.DOC January 14, 2004

SOFTWARE RELEASE 2_2_1_6 RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX 5

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 DOT 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 DOT 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_2_7.9_1.

Chapter 1.

6 C-DOT DSS MAX

Software Release 2_1_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 is being introduced to provide dynamic control for 98/95/94, default Detail Bill on 98/95/94 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. 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

INTRODUCTION & RELEASE HIGHLIGHTS


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

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

Chapter 1.

8 C-DOT DSS MAX

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

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

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



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.

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

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

Chapter 1.

10 C-DOT DSS MAX

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

Chapter 1.

12 C-DOT DSS MAX

1.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.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.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.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.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.11. Separate Area (STD) Code for RSU and Access Network

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.

1.2.12. 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.13. 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.14. 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.

∗ 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.15. 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

Chapter 1.

14 C-DOT DSS MAX

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.16. 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.17. 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.18. 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.19. 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.20. Line Monitoring Feature to Enable Parallel Speach Monitoring of Any Subscriber No.

For this the monitoring agency No. can be from the same exchange or any other exchange on Trunk Dialling.



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

1.2.22. Detail Billing Records Generation on 94/95/98 Calls by Default and Dynamic Locking Control for these Levels

Dynamic locking/unlocking is available for 94/95/98 levels as 'OG-UPTO-REG' access. CDRs will be generated for 94/95/98 calls by default, in addition to '0' & '00' levels.

1.2.23. 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.24. New Announcements for Feature Invocation in Place of Tones & Queue Announcement to Caller in case of Call Waiting in place of RBT.

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.

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

1.2.26. 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.3. IMPORTANT FEATURES OF PREVIOUS SOFTWARE LINKS

A number of important features of previous software links, are also available. As these features have already been evaluated and validated by TEC in other software links, they are now merged in a common software link. Few of the important features are listed below:

Chapter 1.

16 C-DOT DSS MAX

1.3.1. 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.3.2. 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.

1.3.3. 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 otherwords, 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.

18 C-DOT DSS MAX

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.4 11890 Blocks

2 BAC/SL2_2_1_6 133275 Blocks

3. CPC/SL2_2_4.2_6 21176 Blocks

4. BMDC/SL2_2_4.1_6 16902 Blocks

2.1.1.2. Status for MAX-L/MAX-XL

S. NO MEDIA SIZE

1. Unix 11.4 11890 Blocks

2. BAC/ML2_2_1_6 143079 Blocks

3. CPC/ML2_2_4.2_6 23237 Blocks

4. BMDC/ML2_2_4.1_6 16348 Blocks (MAX-L)

16353 Blocks (MAX-XL)

SOFTWARE AND HARDWARE STATUS


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, 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_1_6 519E 27C256

2. APC-SMC122/T-S03

FOR MAX-L /MAX-XL

U7 LADP101XMC2_2_1_6 B6CC 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_4.1_6 186E 27C010

U43 HAPC2XXXMC2_2_4.1_6 065A 27C010

APC-HPC393/O-S01 U55 LAPC3XXXMC2_2_4.1_6 9631 27C040

Chapter 2.

20 C-DOT DSS MAX

S. No.

Card Type Position PROM (ID) Checksum PROM TYPE

FOR 800K BHCA

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

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

U45 LSSC2XXXMC2_2_4.1_6 3EA6 27C010

U43 HSSC2XXXMC2_2_4.1_6 A38F 27C010

APC-HPC393/O-S01 FOR 800K BHCA

U55 LSSC3XXXMC2_2_4.1_6 DD09 27C040

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

U43 LNSC1XXXC2_2_1_6 6B90 27C256

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

U42 HNSC1XXXC2_2_1_6 20B6 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_4.1_6 B80F 27C512

OR U82 HAPC1XXXMC2_2_4.1_6 9AC6 27C512

APC-CPU019/F-S05 U64 LAPC1XXXMC2_2_4.1_6 B80F 27C010

U66 HAPC1XXXMC2_2_4.1_6 9AC6 27C010

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

U67 HMSC1 XXXXC2_2_1_6 F931 27C256

3. APC-CPU019/F-S04 U79 LSSC1 XXXMC2_2_4.1_6 87B5 27C512

OR U82 HSSC1 XXXMC2_2_4.1_6 0002 27C512

APC-CPU019/F-S05 U64 LSSC1 XXXMC2_2_4.1_6 87B5 27C010

U66 HSSC1 XXXMC2_2_4.1_6 0002 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_6 B4F5 27C256

OR U62 HTIC108XXC2_2_1_6 1BB3 27C256

APC-TIC002/F-S10 U75 CTIC110XXC2_2_1_6 21F3 27C512

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

LTTC106XXC2_2_1_6

303E D32F

27C256

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

OR U9 LEAC1XXXXC2_2_1_6 00EB 29F040-PLCC

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

OR U7 LASV1XXXL2_2_4.2_6 8F28 29F040-PLCC

APC-ASVA27/H-S001

U6 HASV1XXXC2_2_4.2_6 DBBB 29F040-PLCC

Note :

Two additional EPROMs are to be provided in 'ANNC' Card at U72 & U75 positions (For Hindi/Eng. Annc.) for new 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_1_6 6BC1 27C040

U29 LICC1XXXXC2_2_1_6 D9A6 27C040

2. APC-ITC535/H-S01 U3 HITC1XXXXC2_2_4.0_6 FFB7 27C040

U4 LITC1XXXXC2_2_4.0_6 F0C3 27C040

3. APC-BRL537/H-S01 U60 HLCC1XXXXC2_2_4.0_6 16C8 27C040

U50 LLCC1XXXXC2_2_4.0_6 FA86 27C040 U24 HLCC1XXXXC2_2_4.0_6 16C8 27C040 4. APC-PRL538/F-S01

U23 LLCC1XXXXC2_2_4.0_6 FA86 27C040

Chapter 2.

22 C-DOT DSS MAX

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_6 F600 27C256 U68 LTUC101XXC2_2_1_6 E5CC 27C256 2. U45 LNPC2XXXSC2_2_4.1_6 0043 27C010

APC-BPC441/O-S02 for SBM RAX with 32 signalling links U43 HNPC2XXXSC2_2_4.1_6 69AC 27C010

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

U55 LNPC3XXXSC2_2_4.1_6 6356 27C040

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

U45 LNPC2XXXMC2_2_4.1_6 F147 27C010

MAX-XL with 32 Signalling Links

U43 HNPC2XXXMC2_2_4.1_6 55BD 27C010

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

U55 LNPC3XXXMC2_2_4.1_6 4C4E 27C040

4. APC-SHM473/H-S01 U17,U20 LPHC102XXC2_2_1_6 B423 27C040

For 32 Signalling Links with BPC

U5,U10 HPHC102XXC2_2_1_6 2E31 27C040

U17,U20 LPHC202XXC2_2_1_6 A622 27C040

APC-SHM473/H-S01 For 64 Signalling Links with HPC U5,U10 HPHC202XXC2_2_1_6 C62F 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_6 F600 27C256 U68 LTUC101XXC2_2_1_6 E5CC 27C256 2. APC-DTC067/T-S04 U3 LDTC101XXC2_2_1_6 F25A 27C256

3. APC-DTS066/T-S04 or

U19 LDTS101XXC2_2_1_6 EBEC 27C256

APC-DTS495/F-S00 U15 LDTS101XXC2_2_1_6 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 LMFC106XXC2_2_1_6 3E90 27C256

APC-MFC043/T-S04 U63 LMFC104XXC2_2_1_6 283E 27C256

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

OR U67 HMSC1XXXXC2_2_1_6 F931 27C256

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

3. APC-TGA077/T-S02 U14 LTGC1XXXXC2_2_1_6 DFFA 27C256

U45 LTGC1XXXXC2_2_1_6 3EAC 27C256

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

U24 LTSC1061XC2_2_4.0_6 996A 27C256 Note 1

U23 HTSC1061XC2_2_4.0_6 A13D 27C256 Note 1

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

U24 LTSC1062XC2_2_4.0_6 64D4 27C256 Note 1

U23 HTSC1062XC2_2_4.0_6 02B4 27C256 Note 1

5. APC-TIC002/T-S08 U56 LTIC108XXC2_2_1_6 B4F5 27C256

OR U62 HTIC108XXC2_2_1_6 1BB3 27C256

APC-TIC002/F-S10 U75 CTIC110XXC2_2_1_6 21F3 27C512

6. APC-ETS477/H-S01 For sixteen PCM

U9 LETS1XXXMC2_2_1_6 98AD 68HC705C9P

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.

Chapter 2.

24 C-DOT DSS MAX

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_4.1_6 7A22 27C512

U82 HBPC1XXXMC2_2_4.1_6 D2F3 27C512

APC-CPU019/F-S05 U64 LBPC1XXXMC2_2_4.1_6 7A22 27C010

U66 HBPC1XXXMC2_2_4.1_6 D2F3 27C010

APC-BPC441/O-S02 U43 HBPC2XXXMC2_2_4.1_6 9705 27C010

FOR 300K BHCA U45 LBPC2XXXMC2_2_4.1_6 D671 27C010

APC-HPC393/O-S01 FOR 800K BHCA

U55 LBPC3XXXMC2_2_4.1_6 14B3 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_4.1_6 7EB8 27C512

U82 HBPC1XXXSC2_2_4.1_6 B812 27C512

APC-CPU019/F-S05 U64 LBPC1XXXSC2_2_4.1_6 7EB8 27C010

U66 HBPC1XXXSC2_2_4.1_6 B812 27C010

APC-BPC441/O-S02 U45 LBPC2XXXSC2_2_4.1_6 04A7 27C010

U43 HBPC2XXXSC2_2_4.1_6 CB21 27C010

APC-HPC343/0-S01 U55 LBPC3XXXSC2_2_4.1_6 8A60 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_6 F600 27C256 U68 LTUC1XXXXC2_2_1_6 E5CC 27C256 2. U45 LVPC2XXXSC2_2_4.1_6 E33C 27C010

APC-BPC441/O-S02 for SBM RAX with 32 signalling links U43 HVPC2XXXSC2_2_4.1_6 BD48 27C010

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

U55 LVPC3XXXSC2_2_4.1_6 345C 27C040



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

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

U45 LVPC2XXXMC2_2_4.1_6 CCC7 27C010

MAX-XL with 32 Signalling Links

U43 HVPC2XXXMC2_2_4.1_6 9B82 27C010

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

U55 LVPC3XXXMC2_2_4.1_6 EC08 27C040

4. APC-SHM473/H-S01 U17,U20 LPHC102XXC2_2_1_6 B423 27C040

For 32 Signalling Links with BPC

U5,U10 HPHC102XXC2_2_1_6 2E31 27C040

U17,U20 LPHC202XXC2_2_1_6 A622 27C040

APC-SHM473/H-S01 For 64 Signalling Links with HPC U5,U10 HPHC202XXC2_2_1_6 C62F 27C040

26 C-DOT DSS MAX

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_6 retrofit procedure has to be carried out over. previous software releases 2_1_1_1.

2. Exchange Data Retrofit Utility Cartridge

This is used to generate the command files by reading the database of the present software release. These command files are later executed in new software environment 2_2_1_6 to generate the complete database i.e. subscribers, TGPs, Routes, Hunt Groups etc. with exactly same characteristics as it is presently working.

3. Billing Data Not to be Restored

As billing files structure has been changed in S/W 2_2_1_6, therefore it will not be possible to restore the old billing data. As a result, meter reading of all the subscribers will start from a fresh (i.e. zero). Also detail bills of past will not be available and fresh data will be considered from the date of retrofit.

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_6 billing file structure can be obtained from C-DOT for the upgradation of billing package.

4. Expected time for complete retrofit procedure is about 2 days for SBM and 4 days for MAX-L exchanges. It must be noted that the procedure is to be followed in completeness and in the same sequence as described subsequently. Also, carry out different checks at different stages and in case of errors, take corrective action as recommended.

SOFTWARE RETROFIT PHILOSOPHY AND PRE-RETROFIT CHECKS


5. 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_6. Before this, complete data base created in 2_2_1_6 has to be compared with that of 2nd IOP and any data missing has to be recreated. Watch the system stability for one day.

6. Please make sure to replace the PROMs for spare cards also.

7. The other IOP is to be loaded with UNIX only and two copies of S/W deliverables, cartridges of UNIX, BASE, PATCH and BMDC are to be prepared from the master set. After this do loading of this IOP with one set of the two copies prepared at the site to verify that the deliverables do not have any problem.

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 including IOPs, ADP 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. • Take a printout of all the system parameters. • If following originating and terminating facilities have been provided to some

subscribers, withdraw them by 'MOD-SUB-FAC' command:

ORG-FAC : Auto Call Back, Manual Alarm, Admn-og-barr Cal-wat-clg

TRM-FAC : Absnt-man-Ans, Absnt-fxd-annc. - Take print out of all the 'DID' routes and their characteristics using

command "DISPL-ROUT-CHAR". • BP cables for both BM-L, BM-XL & SUM should be available at site.

28 C-DOT DSS MAX

Chapter 4.

Retrofit Procedure (from 2_1_1_1 to 2_2_1_6)

4.1. SOFTWARE RETROFIT PROCEDURE

• Stop all the Traffic Reports if they are ON. • Make all the copy-0 controllers as INS-SBY. • Bring the IOP-0 (SBY-IOP) to warm start level by crp command INIT-IOP:

2,1; • Stop executing Data Base Modification related 'CRP' commands from INS-

ACT IOP e.g. MOD-SUB-FAC, MOD-TGP-CHAR, MOD-ROUT-CHAR etc. till the retrofit procedure is not complete.

• Prepare the exchange data command files for 2_2_1_6 release using the exchange data retrofit utility as explained in para 3.2.

4.2. PROCEDURE TO EXTRACT EXISTNG DATA FROM 2_1_1_1 S/W

• Please ensure that RGEN utility is loaded in IOP-0 (warm – start level) - Insert the ed retro utility cartridge to cartridge drive of IOP – 0 (warm –

start level) and give the following commands from IOP5X prompt. - IOP5X> cd /u/admn - IOP5X> mkdir retro2-2 - IOP5X> cd retro2-2 - IOP5X> pwd (press return and ensure that you are in /u/admn/retro2-2

directory) - IOP5X>cpio –icv <$TAPE

After copying is over, the following files should be available in /u/admn/retro2-2, which can be checked, by issuing the following command

RETROFIT PROCEDURE (FROM 2_1_1_1 TO 2_2_1_6)


IOP5X> ls -C admbsy2 creoos2_2 linch5 rxcd_pre.cmd trua_fin.awk

backup crerout2_2 linchr4 spc_pre.awk trua_fin.cmd

cgs_fin.awk crespc2_2 insts2 spc_pre.cmd trua_pre.awk

cgs_fin.cmd cresrs2_2 ls_fin.awk srs_fin.awk trua_pre.cmd

cgs_pre.awk cresub2_2 ls_fin.cmd srs_fin.cmd trus_fin.awk

cgs_pre.cmd cresubbar2_2 ls_pre.awk srs_pre.awk trus_fin.cmd

chb_pre.awk cretgp2_2 ls_pre.cmd srs_pre.cmd trus_pre.awk

conv_decad cretrm2_2 lsb_fin.awk srv_pre.awk tsys_par.awk

crecgs2_2 crexcod2_2 lsb_fin.cmd stdfac1 ttgp1_fin.awk

crechb2_2 crg_pre.awk lsb_pre.awk stdfac2 ttgp_fin.awk

crecrg2_2 crgrtn3 lsb_pre.cmd stdloc1 ttgp_fin.cmd

crehgp2_2 dtyp_pre.awk mfc_eqp.sh sub3 ttgp_pre.awk

crels2_2 frm_pre.awk mfc_pre.awk sub4 ttgp_pre.cmd

crelsb2_2 hgpfin.awk mod_pre.awk tdatsubl2_2 util

cremfc2_2 hgppre.awk procedure2_2 tday_pre.awk xcod_pre.awk

cremisc2_2 iot2 retro_split temp

cremod2_2 linch33 rxcd_pre_awk tgptrk2

iop5x>cd /u/admn/retro2-2 • To extract the Complete data command files.

i) Run the following command from crp <exec-cmd-file : ttgp_pre.cmd,n; ii) Run the following command from IOP5X prompt.

• IOP5x>nohup util & wait till IOP prompt appears

• Following file should be present (ls –ls *.cmd command at IOP5X prompt may be used for viewing the for list of these files).

[acgs.cmd achb.cmd acrg.cmdacrus.cmd acrut.cmd actgp.cmd aefrm.cmd als.cmd alsb.cmd amod.cmd asrs.cmd axcod.cmd arxcd.cmd acsub.cmd aetrm.cmd aemfc.cmd ahgp.cmd instyp.cmd oosopr.cmd, admbsy.cmd]

• File Details !!! • acgs.cmd # CGS Command File • aspc.cmd # SPC Command File • achb.cmd # Charge Band Command File

Chapter 4.

30 C-DOT DSS MAX

• acrg.cmd # Charge Rate Number Command File • acrus.cmd # Special Rout Command File • acrut.cmd # Rout Command File • actgp.cmd # Tgp Command File • actrk.cmd # ADD-TRK Command File • aefrm.cmd # Frame Equippage Command File • aemfc.cmd # MFC card equippage Command File • aesrv.cmd # SRV card equippage Command File • als.cmd # LS Command file • alsb.cmd # LSB Command file • amod.cmd # MODULE Equippage Command File • asrs.cmd # SRS Command File • axcod.cmd # EXCHANGE CODE Command File • arxcd.cmd # RBM EXCHANGE CODE Command File • acsub.cmd # CRE-SUB Command File • aetrm.cmd # EQUIP-TRML-CARD Command File • ahgp.cmd # CRE-HGP Command File • grntocr.cmd # GRNT-OCR-SUB Command File • admbsy.cmd #BNP-ANNC and BNP-DISC numbers command files • oosopr.cmd #OOS-OPR command file Note 1: edit amod.cmd file for correct equipage of DTK ids for RBMs only.

If there is no RSU in system, do not carry out this correction.

2. IF there are CCS7 TGPs going towards EWSD exchange then modify the parameter SIG-INF in the file actgp.cmd of the corresponding TGPs to include the parameter ACCS-CD-NPFX as per software 2_2_1_6 which is ISUP-ACS-CD-NP.

4.3. BACK-UP OF COMMAND FILES GENERATED

Insert a scratch cartridge marked as “DATA COMMAND FILES” in the Tape Drive of IOP-0 and give following commands:

Take the Command File backup on Cartridge, Using following command on IOP Prompt • IOP5X> >$TAPE • IOP5X>cat backup|cpio –ocv >$TAPE

After copying is over, verify the contents by using following command

IOP5C> cpio -icvt <$TAPE



The command will show all the files copied and at the end, total block size will be shown.

Remove the cartridge from the drive, mark it as data command file and preserve it, as it will be used for creating fresh data in 2_2_1_6 S/W environment.

4.4. LOADING OF NEW SOFTWARE RELEASE 2_2_1_6 IN IOP-0

a) Bring the IOP-0 to cold start level using the crp command <INIT-IOP: 1,1;

b) Load new software 2_2_1_6 (UNIX 11.4, BAC, CPC and BMDC) using standard S/W loading procedure. For details of complete S/W loading procedure, refer Annexure-A of this document.

c) After complete loading of software, shutdown the IOP and boot it again.

d) Enter 'CRP and execute 'SET-SITE-ID' command to set identity of the site.

4.5. CREATION OF DATA IN 2_2_1_6 ENVIRONMENT

4.5.1. Copying of 'Data Command Files' in IOP-0

IOP5X>mkdir /u/ admn/cretro

IOP5X>cd /u/admn/cretro

IOP5XY PWD (Press return, response of this command should be in / admn / cretro

Restore the Command file backup on 2_2_1_6 IOP, After inserting the backup cartridge in IOP Cartridge drive.

IOP5X>cpio -icv <$TAPE

After successful Installation, Following file should be present [acgs.cmd achb.cmd acrg.cmd acrus.cmd acrut.cmd actgp.cmd actgpnot.cmd aefrm.cmd als.cmd alsb.cmd amod.cmd asrs.cmd axcod.cmd acsub.cmd aetrm.cmd actrk.cmd tdasubl2_2 retro_spilt admbsy.cmd oosopr.cmd]

4.5.2. Generation of Exchange Data

Now give the following Command on IOP Prompt to generate the DATA on 2_2_1_6 S/W IOP.

IOP5X> tdatsubl2_2

and wait for the Submission over Message!!!

verify the errors from log files using following command

iop5x>grep error accrp0*.log

Chapter 4.

32 C-DOT DSS MAX

and so on for other accrp log files i.e. accrp1*.log, accrp2*.log, accrp3*.log ... accrp9*.log

Time taken for creation of exchange data depends upon the capacity of the exchange. This may be 4 to 6 hrs. for SBM-TAX; 10 hrs. for SBM-RAX and 1 to 2 days for MBM exchange. After the data creation is over, message “DATA CREATION OVER !!! will be displayed.

The time during which data is being created can be utilised for following jobs:

i) Make all copy-0 controllers 'OOS-OPR' from INS-ACT IOP-1 and then change the new PROMs on these cards. However, it should be ensured that after replacing the EPROMs and putting the cards into the right slot, these should not be jacked-in. Only diagnostics of TIC/TUC card with new EPROMs can be done after jacking them in.

4.6. POST DATA CREATION CHECKS AND UPDATION

• After completing the step 3.5, we are having complete exchange database in both the IOPs. The OOS-SYS IOP-0 is having S/W 2_2_1_6 on which complete data for the exchange has been created and IOP-1 is INS-ACT with S/W 2_1_1_1 and existing exchange data.

• Now, before proceeding further, compare the data base in both the IOPs for subscriber, TGPs and ROUTE creation. Execute the command. 'DISPL-DIRNO' with option ASSIGN on both the IOPs and compare the results whether all the subscribers working in the exchange have been created successfully. In case, few working subscribers are not created in IOP-0, create them one by one by executing CRE-SUB command in growth mode.

• Note the subscribers from active IOP whose line status is BNP-DISC. Modify the status of the corresponding subscribers in IOP-O accordingly.

• Repeat the above process for TGPs and ROUTES by executing the commands 'DISPL-TGP-ROUT' and “DISPL-All-ROUT”. Verify that, except 'DID' routes all other routs have been created. Create the DID routes and for CCS7 TGPs towards EWSD exchange, ensure that the SIG-INF parameter to include ISUP-ACS-CD-NP.

a) If in any BM, ANNC card is equipped in any other place apart frame 1 slot 3 then equip that ANNC card in the required frame and slot. The ANNC card has to be equipped as [UNIT-ID]=ANNC-0 and [EQP-TYP] = standard.

b) Modify System Parameters • Give Crp command 'DISPL-SYS-PARAM' in the IOP-1 having

previous S/W data and note down values of following system parameters



i) XCHG-TYPE

ii) NON-MTR-LCL iii) MIN-SUBS-DIALS iv) NUM-ANI v) BM-01-CAT to BM-32-CAT (32 parameters) vi) ARCD *parameters for area code prefixing. [ARCD-DGT1]

has to be given as `0' instead of `10'.

vii) CLI-INFO

viii) PCO-MTR-LCL ix) SPL-RNG xi) NO7-THR xii) INT-THR xiii) CALL-DUR-THR xiv) CALL-CHRG-THR xv) ROUTING xvi) PSWD-TAMP-THRS xvii) SUB-CHRG-CTG

• In IOP-0, having S/W 2_2_1_6 data, modify all the above system parameters in 'GROWTH MODE' using CRP command 'MOD-SYS-PARAM' with following parameters

Parameter Name :

Parameter Value :

c) Verification of HGPs and special routes which have PDN of HGPs as their alternate number • In case some'HGP' has not been created, then create the same

after comparing data from active IOP. Also create the missing special routes if any.

Chapter 4.

34 C-DOT DSS MAX

d) SUB-CRG

Verify 'SUB-CRG' for various categories using command 'DISPL-SUB-CRG'. In case any mismatch is noticed, correct the same using 'MOD-SUB-CRG' command.

e) In case of RBM, 'MOD-RBMNRM-CONFIG' for special routs if already existing in old data.

f) Add required terminals and operators in IOP-0 which were existing in it, in the previous S/W.

g) Create answering circuit number and remote alarm reporting number, if existing in the previous data.

h) Check DAY-TYPE and TYPE OF DAY i.e. whether a particular day is holiday or not and the various tariff class within each DAY-TYPE.

i) Subscriber having priority other than `1' to be checked and modify them accordingly.

j) Create the required operators with the desired `Admin' and `maint' classes.

k) Go to crp and give following command

<DEL-FGP-FILE:, ioh; • Take 'ED' and 'BD' BACKUP by 'COPY-OUT' command. • While taking 'BD' backup, following is to be given in parameter

'FGP':

FGP = bd • Shutdown and boot the IOP-0 to warm start level.

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.

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

Chapter 4.

36 C-DOT DSS MAX

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

4.7. INITIALISATION/BOOTING UP THE SYSTEM WITH S/W 2_2_1_6

1. During night hours, bring the ACTIVE IOP-1 to warm start level using <INIT-IOP:2,1; command.

2. Switch off the power supplies in all the frames of CM, BMs & LMs. (In case of 'SBM' only BM & LMs are relevant).

3. At MBM sites, change EPROMs in both the copies of APC, SSC and MSCs in all the four CMSs. Switch on the PSUs of all the frames of CM after jacking the controller cards in APU and SCU in the right slots. Execute the CRP command INIT-IOP:5,1; from IOP-0 and wait for the message “code loading begins ……” on the CONSOLE terminal. Now proceed to the next step. (In case of SBM, EPROMs have to be changed in BPU and TSU frame for all the relevant cards. Then switch on PSUs in BPU and TSU and give command INIT-IOP:5,1; from IOP-0 to initialise the system).

4. Change the PROMs in all the controllers of different units of Base Modules as listed below :

BPU CPU or BPC

TSU (MSC/HMS, TSC, SCIC, MFC, TOGC) ATU (TTC, ANNC*) (One copy of TIC/TUC cards has already DTU (DTC,DTS, TUC) been replaced with NEW PROMs) ADP (SMC) CSU BPC, SHM VU BPC, SHM ISTU ITC, ICC, BRL, PRL * Provide 2 additional EPROMs also at U72 & U75 positions as

per Annexure-C.

5. Jack in both the copies of controllers in TSU and BPU in 1st BM and one copy of TICs/TUCs on which new PROMs have been changed. Jack out other copy of TICs/TUCs with previous S/W PROMs. Switch on the PSUs of BPU, TSU & TUs/DTUs. Wait for code load to start with message “code load begins …..” on the console terminal. Once the 1st BM has recovered, then proceed to next two BMs at a time, till all the BMs are recovered.



6. Wait for the Load Pass Report on OOD/PRINTER for all the BMs and critical alarm to retire from ADP.

7. Make all the MFC units INS-ACT one by one in all the BMs using CRP command “PUT-SWU-INS:. After that bring TTC & ANNC INS-ACT in all the BMs.

8. Displ system status (DISPL-SYS-ALL) for various modules and bring the simplex switch units in INS-ACT status.

9. Check that SUM and VU have come up if equipped in the exchange. Ensure that the BM which has VU equipped in one of its frame has at least few of its MFC card circuits equipped as DTMF type.

10. Execute the command file oosopr.cmd for 'oos-opr' Directory Nos. if any. At crp give the following command

exec-cmd-file : oosopr.cmd,n;

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

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) Registering a new password (secret dynamic STD code) and then subsequent locking/unlocking function upto different access barring levels works fine as per new procedure.

k) Other released SIF features are working properly with new feature invocation codes.

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

Chapter 4.

38 C-DOT DSS MAX

4.9. RECOVERY ACTION

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

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

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

iii) Replace EPROMs in AP, SSC, MSC, TSC, SCIC, MFC, TTC, with previous S/W version PROMs and jack in the cards. Replace PROMs in SUM & ISTU frame also.

iv) Jackout copy-0 TIC cards having new PROMs in all TUs and jack in copy-1 cards with (old version PROMs)

v) Power on all the frames of the system

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

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

4.10. 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_6 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. As all the dirnos., which were OOS-OPR will become INS-FREE, so make

them OOS-OPR using 'frc-trm-oos' command. 9. Load latest 'RGEN/CMD' utility in both IOPs.


Chapter 5.

Retrofit Procedure for S/W 2_2_1_6 at Sites Already having S/W

2_2_1_3/2_2_1_4

5.1. S/W RELEASE 2_2_1_6 DELIVERABLE STATUS

5.1.1. Change of Eproms Required for s/w Release 2_2_4.2_6 over Various Rel. Existing

Deliverable 2_2_2.10_3 2_2_4.4_3 2_2_4.3_4 2_2_4.4_4

ADC √ √ X X

BM-XL/BM-L MFC-S04/S06 TTC

√ √

√ X

√ X

√ X

BPC-S02 BPC-S01 CPU-S04/S05 TSC-S04/S06

√ √ √ √

√ √ √ √

√ √ √ √

√ √ √ √

SUM

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

√ √ √ √

√ √ √ √

√ √ √ √

√ √ √ √

VU

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

√ √ √ √

√ √ √ √

√ √ √ √

√ √ √ √

CM-L

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

√ √

√ √

√ √

√ √

CM-XL

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

√ √ √

√ √ X

√ √ X

√ √ X

ISTU

ICC ITC BRL/PRL

√ √ √

√ √ √

√ √ √

√ √ √

Chapter 5.

40 C-DOT DSS MAX

Deliverable 2_2_2.10_3 2_2_4.4_3 2_2_4.3_4 2_2_4.4_4

BAC CPC BMDC Retro Utility 2_2_1_6

√ √ √ √

√ √ √ √

√ √ √ √

√ √ √ √

5.2. RETROFIT PROCEDURE FOR C-DOT EXCHANGES HAVING S/W 2_2_2.10_3

5.2.1. List of Deliverables

Refer para 5.1.1 for New EPROMs required for S/W 2_2_4.2_6 over various releases.

5.2.2. Pre Retrofit Checks

1. Take ed, bc, bd and tf backups

2. Note down characteristics of icc ports and operator’s accounts.

5.2.3. Procedure

Step 1 : Bring standby IOP-1 to warm start level.

Step 2 : Shut down this IOP-1 and load complete new software (2_2_1_6). After loading the new software, shut down and reboot this IOP.

Step 3 : Unequip all the announcement (ANNC) & TTC cards on all the BM's in ON LINE mode in the active IOP.

Step 4 : Take a Ed backup from active IOP-0 and load this in IOP in which new software has been loaded (i.e. IOP-1). While copy-in, in Restore option [RES-OPT] field give OVER-REL.

Step 5 : Login in admn account.

Step 6 : Insert the BMDC extra files cartridge in the cartridge drive and give the following commands on IOP5x> Prompt - IOP5x>cd $DUMPP - IOP5x>mkdir exf - IOP5x>cd exf - IOP5x>pwd (to confirm you are in /data/dump/exf

directory) - IOP5x>cpio -icv <$ TAPE

RETROFIT PROCEDURE FOR S/W 2_2_1_6 AT SITES ALREADY HAVING S/W 2_2_1_3/2_2_1_4


- IOP5x>retro4.4 (This is an interactive utility which will ask for the BM numbers existing in your system and automatically copy the required files in respective directory).

- Shut down and reboot this IOP (with SW 2_2_4.4_4)

Step 7 : Bring the active IOP-0 (SW 2.10) to warm start and switch-off the system and replace EPROMs as per 2_2_4.4_4 release note.

Step 8 : Copy in BD from IOP-0 with SW 2_2_2.10_3 to IOP with SW 2_2_4.4_4.

Step 9 : Switch on the system after all the required PROMs have been changed.

5.3. RETROFIT PROCEDURE FOR C-DOT EXCHANGES HAVING S/W RELEASE 2_2_(4.4)_3/2_2_(4.3)_4/2_2_(4.4)_4

5.3.1. List of Deliverables

Refer para 5.1.1 for New EPROMs required for S/W 2_2_4.2_6 over various releases.

5.3.2. Pre Retrofit Checks

1. Take ed, bc, bd and tf backups

2. Note down characteristics of icc ports and operator’s accounts.

3. IOPs should be in duplex working and interchange IOP should work.

5.3.3. Procedure

1 Bring standby IOP (Say IOP-0) to warm start level and then to cold start level.

2 Switch off power supply. Verify 'VHC'-U22 chcksum is '2f37'. If required change the EPROM. Then switch-on the power.

3 Load complete software (Unix, BAC, CPC, BMDC) of 2_2_4.2_6 release. Shut down, reboot and "set-site id".

4 Save files bpsifc * and ansprm * in some other directory :-

IOP5C> mkdir $GLBDATAP/misc

IOP5C> cd $GLBDATAP/misc

IOP5C> pwd (should show /data/exdata/glbdata/misc)

Chapter 5.

42 C-DOT DSS MAX

IOP5C> cp $GLBDATAP/bpsifc* !

IOP5C> cp $GLBDATAP/ansprm* !

IOP5C> ls -ls (should show 3 files each of bpsifc* & ansprm*)

5 'Copy-in' the 'ed' backup taken from 2_2_1_4 software (in para 5.3.2) in this IOP-0 having 2_2_1_6 s/w:-

Copy-in : VOL-NAME = ed DDMM

RES-OPT : OVR-REL

: :

FGP : ed

6 Copy relevant announcement files "ioanpgxx" from $PRCDATAP to $GLBDATAP/bpanpg*

e.g. for 'Hindi-English' announcements 'language id'=01

IOP5C> cd $PRCDATAP

IOP5C> cp ioanpg01.dat $GLBDATAP/bpanpg.dat

IOP5C> cp ioanpg01.idx $GLBDATAP/bpanpg.idx

IOP5C> cp ioanpg01.lok $GLBDATAP/bpanpg.lok

IOP5C> cd $GLBDATAP

IOP5C> ls -ls bpanpg*

verify that current time is shown for the three files.

7 Restore ansprm* and bpsifc* files :-

IOP5C> cd $GLBDATAP/misc

IOP5C> cp ansprm* $GLBDATAP

IOP5C> cp bpsifc* $GLBDATAP

IOP5C> cd $GLBDATAP

IOP5C> ls -ls bpsifc* ansprm*

verify that current time is shown for all the six files.



8. Run command file 'amlpr.cmd' to modify line testing parameters :-

IOP5C> cd /u/admn/cmdfile

Go to crp and execute :-

exec-cmd-file : amlpr.cmd;

9. Verify important system parameters and modify these as per old IOP-1 having 2_2_1_4 s/w using 'mod-sys-param' command :

XCHG-TYP, NON-MTR-LCL, MIN-SUB-DIALS, PCO-MTR-LCL, CLI-INFO, NUM-ANI, ARCD-IN-CLLNG, ARCD-LEN, ARCD-DGTX*, PSWD-TAMP-THRS, CALL-DUR-THR, CALL-CHRG-THR, SPL-RNG, BM-XX-CAT (where xx is BM-NO), NO7-THR, INT-THR- V5-THR, VU-INT-THR, DNA-TMR = 280, SUB-CHRG-CTG.

10. Running of Retrofit Utility 2_2_1_6 in IOP-0

i) Insert retrofit utlility 2_2_1_6 in cartridge drive :

IOP5C> mkdir /u/admn/retro2216

IOP5C> cd /u/admn/retro2216

IOP5C> pwd (to verify directory /u/admn/retro2216)

IOP5C> cpio -icv <$TAPE

Once retrofit Utility has been copied, remove cartridge from the drive.

IOP5C> chmod 755 *

ii) Take backups of bpsod*, abexcd* and aplvl1* :-

IOP5C> cd $GLBDATAP

IOP5C> ls bpsod* abexcd * aplvl1* | cpio -ocv> /u/admn/retro2216/backup

iii) IOP5C> cd /u/admn/retro2216

IOP5C> retrofit

Watch for the message ‘Operation complete. Do you want to copy the new files to required files (Y/N) ?’ Give ‘Y’ here.

Retrofitting messages will appear for all the BMs. There should be no errors shown.

In case any errors are shown, consult C-DOT control Room

Chapter 5.

44 C-DOT DSS MAX

iv) Verify 'sub-crg' mapping using 'DISPL-SUB-CRG' for various categories as already available in old data (2_2_1_4). Modify if required. Also verify certain commands, like 'Dipsl-All-rout', 'Displ-tgp-rout', Displ-chb-crg;, 'Displ-crg-rtn', 'Displ-ten', Displ-sub-list; as a - sample check of exchange data.

12. 'Copy-in' 'BC' backup for last 2 months (Billing Cycle) in IOP-0.

13. Once, slack hour starts at “00 Hrs”, take latest 'BD' backup with date option not covered in 'BC' back-up loaded in step 12. 'Copy-in' this 'BD' in IOP-0.

Shut down & Reboot. Now this IOP is ready for retrofit.

14. Bring Active IOP-1 to warm start level, by INIT-IOP : 2, 1; command. Switch off PSUs in 'TSU' frames of all the BMs (Local + Remote). Then switch off PSU's in AM & CM (6th & 5th frames of CM).

15. Change Proms in BPC cards of AM & CM. Switch on PSU's. Give 'INIT-IOP : 5,1; from IOP-0 having 2_2_1_6 s/w. Let AM & CM recover fully after code/patch/data loading.

16. Switch off PSUs in BPU of BM-1 (or any line BM), Change Proms in BPC/TSC/MFC. Provide additional proms in 'ANNC' card at the positions defined. Change Proms in BRL/PRL/ITC/ICC cards of ISTU if equipped in this BM. Switch on PSU's in BPU/TSU and let 'BM' go for code/patch/data loading. Once BM-1 recovers completely verify D/Tone and few local calls. If every thing is fine, move ahead for next BMs.

17. Switch off PSUs in BPUs of all the remaining BMs and start changing Proms in BPC/CPU/TSC/MFC/SUM/VU/ISTU cards covering BMs one by one. Switch on PSUs and let BM's recover after code/patch/data loading.

18. Once complete system has recovered, verify 'Displ-ood-log' for report type = 182 and confirm that all BM's have gone for 'power-on' (i.e. code load) initialization.

19. Post Retrofit Checks

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

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

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

c) Line to Line local calls and meter updation.

d) O/G calls on various routs & meter updation.



e) Proper updation of Detail Bill Records both for subscriber and Trunks. Verify Detail Bill coming ok for 95/94/98 calls, even if subscriber is on ord-blg.

f) All accuncements are working fine, specially, new announcements for feature invocation (Dynamic Locking/ Unlocking etc.).

g) Verify Dynamic Locking/unlocking function, specially for “O/G upto Regional” by which 95/94/98 access can be controlled.

20. Retrofit Completing Activities

a) Change EPROMs in spare cards.

b) Load 2_2_1_6 software in IOP-1.

c) Synchronise IOP-1 by standard procedure.

d) Implement password management in IOP's if any.

e) Add terminals and operators in the IOP-0 & IOP-1.

f) Load latest RGEN Utility in both the IOPs.

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

Definition of Day Types 1 & 2 has been shown in Table 5-1, while tarrif rates for various distances have been shown in tables 5-2(a), 5-2(b), 5-2(c), 5-2(d) & 5-2(e).

Table-5.1

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

0000 0630 12 NOT-BARRED

0630 2230 11 NOT-BARRED

2230 2400 12 NOT-BARRED

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

0000 0600 12 NOT-BARRED

0600 0630 10 NOT-BARRED

0630 0800 7 NOT-BARRED



Chapter 5.

46 C-DOT DSS MAX

START TIME END TIME TARRIF CLASS ROUTING INFO







2230 2300 10 NOT-BARRED


5.4.1. The tariff applicable for inter-circle and intra-circle and of BSNL & TRAI are separately summarized

5.4.1.1. Pulse Rates for Local Calls for TRAI and BSNL Packages

Table-5.2(a)

Type of call TRAI Tariff (Sec)

BSNL Tariff (Sec)

Basic To Basic 120 180

Basic to FXD WLL 120 180

Basic to WLL (Mobile) 120 90

Basic to Cell

Metro

Circle

90

60

60

30

5.4.1.2. Pulse Rates for National Long Distance Calls

5.4.1.2.1. Charging Plan for TRAI

PEAK HOUR (0900 - 2200 Hrs)/ off peak hour (2200 - 0900)

Table-5.2(b)

Distance TRAI Tariff

Basic to Basic & FXD WLL

(Sec)

Basic to WLL (Mobile)

(Sec)

Basic to Cell (Sec)

0-50 Km 120 120 90 (Metro), 60 (Circle)

>50-100 15 15 15



>100-200 15 15 15

>200-500 12 12 12

>500 9 9 9

Note: Charge Pulse are same for peak & off-peak hours and for Intra circle and Inter circle calls in TRAI Tariff Plan.

5.4.1.2.2. Charging Plan for BSNL Package

PEAK HOUR(0900 - 2200 Hrs)/ off peak hour (2200 - 0900)

Table-5.2(c)

BSNL Tariff (sec)

Intra Circle Inter Circle

Distance Basic to Basic &

WLL FXD (Sec)

Basic to WLL

(Mobile) (Sec)

Basic to cell

(Sec)

Basic to Basic &

WLL FXD

Peak/ off peak (Sec)

Basic to WLL

(Mobile)

Peak/ offpeak

(Sec)

Basic to cell

Peak/ offpeak

(Sec)

0-50 Km 180 90 30 90 60 30

>50-100 60 60 30 30 30 30

>100-200 30 30 30 30 30 30

>200-500 30 30 30 15 / 30 15 / 30 20 / 30

>500 30 30 30 15 15 20 / 30

Note :

• Charge Pulse are same for peak & off-peak hours if mentioned only once.

• ON Sundays and National Holiday the off peak pulses will be applicable for 24 hours.

Chapter 5.

48 C-DOT DSS MAX

5.4.1.2.3. Charging for Internet call

Table-5.2(d)

TRAI (sec)

BSNL (sec)

Peak 120 (0800 to 2000 Hrs)

180 (0630 to 2230)

Off Peak 180 (2000 to 0800 hr)

600 (2230 to 0630)

5.4.2. Table of New Charge Rate Number and the Charge Bands to be Associated

Table 5.2.(e) Sl. No. Charge Band

Number Charge Rate

Number Initial Charge

Pulse Rate Peak/off peak

(Sec)

1 11 21,11 1,0 180 / 180

2 44 51,50 1,0 120 / 120

3 43 43,33 1,0 90 / 90

4 42 42,32 1,0 60 / 60

5 41 41,31 1,0 30 / 30

6 15 25,15 1,0 15 / 15

7 29 26,16 1,0 12 / 12

8 13 23,13 1,0 9 / 9

9 37 47,37 1,0 120 /180

10 14 24,14 1,0 15 / 30

11 45 52,53 1,0 20 / 30

12 10 54,44 1,0 180 / 600



Table 5-2 (f) ISD Charge Rates/Bonds PEAK *OFF PEAK

Charge Band Nos. 0800-1900 Hrs. IST 0000-0800 Hrs.

1900-2400 Hrs. IST

SAARC & other Neighbouring countries

17 3.4 Secs. 4.0 Secs.

Countries in Africa, Gulf, Asia & Oceania

18 3.0 Secs. 3.4 Secs.

0600-1100 Hrs. 1800-2400 Hrs. IST

0000-0600 Hrs. 1100-1800 Hrs. IST

All countries in American Continent and other places in western Hemisphere

19 3.0 Secs. 3.4 Secs.

1100-2200 Hrs. IST

0000-1100 Hrs. 2200-2400 Hrs.

IST

All countries in Europe 35 3.0 Secs. 3.4 Secs.

5.5. VERIFICATION OF CHARGE RATE NUMBER

Take a printout of all the Charge Rate Numbers from Active IOP-1. Now verify that relevant Charge Rate Numbers covering all the New Pulse Rates (As per Table 5.3) are available in IOP-0. In case, any ‘CRG-RTN’ is not available, then some unused charge rate no. has to be modified for required Pulse Rate for at least 1st Tariff class in BS1, BS2 and BS3 categories (Refer Annex-F for definition of the CRG-RTNs).

Note : Any charge rate no. can be modified only after disassociation of ‘Charge Band’ from that CRG-RTN e.g. crg-rtn ‘18’ has to be modified and it is associated with charge band no. ‘18’ then do the following : <MOD-CHB-CRG>

OPER-TYP : DEL-CHB

CHB : 18

CRG-RTN : ALL

This will disassociate CHB NO. 18 from CRG-RTN ‘18’. Thereafter proceed with ‘MOD-CRG-RTN’. After modification, associate the ‘CHB’ again using the same command ‘MOD-CHB-CRG’, if required (Mandatory for exchange having CCS7 signaling)

Chapter 5.

50 C-DOT DSS MAX

5.6. COMMAND FILE CREATION FOR ISD ROUTES IN ORDER TO IMPLEMENT ‘PRD-LCL’ CHARGING FOR ISD CALLS.

Select charge rate nos. meant for ISD calls as per pulse rates to be used for SAARC, AFRICA, GULF, ASIA, OCEANIA, EUROPE and AMERICAN subcontinent (Annex–F). Using these charge rate nos., prepare a command file having “cre-rout” commands for all the ISD routes as per Annex.-E. Use same TGPs as being used for existing ISD rout/routes.

Note : If ‘PRD-LCL’ charging for ISD routes is not required, do not carry out this step and proceed to step 5.

5.7. NOW 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-12-2 & 0630-11-2 & 2230-12-2 execute

b) Mod-typ-day Day-typ = 2 Prd-trf = 0000-12-2 & 0600-10-2 & 0630-7-2 & 0800-5-2 & 0900-1-2 & 1100-2-2 & 1800-3-2 & 1900-4-2 & 2000-6-2 & 2130-8-2 & 2200-7-2 & 2230-10-2 & 2300-9-2 execute

Table-5.3

Charge Band Number (CHB) to Charge Rate Number (CRG-RTN) association

Charge Band Number Pulse Rate (Sec)

0 Non-metered 1 Unit Fee

10 180/360 11 180 12 18/28

14 15/30 15 8/16



16 8/16 17 3.4/4.0(SAARC & Neighbouring)

18 3.0/3.4 sec (AFRICA , GULF,ASIA & Ocenia) 19 3.0/3.4 (American Continent & Others in Western

Hemisphere)

20 300 msec 21 1300msec

24 600msec 35 3.0/3.4 (EUROPE)

36 30/60 sec. 44 120 sec. 45 30 sec.

5.8. 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 strapps) will be required to be done in all the PSUs. Detail can be taken from C-DOT.

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

52 C-DOT DSS MAX

Chapter 6.

Do's and Dont's

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

6.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↵

DO'S AND DONT'S


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.

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

Chapter 6.

54 C-DOT DSS MAX

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.

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

DO'S AND DONT'S


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:

Chapter 6.

56 C-DOT DSS MAX

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.

6.2. DO'S AND DONT'S FOR CARD HANDLING

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

DO'S AND DONT'S


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

6.2.3. CPU-S04/S05 Cards

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

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

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

6.2.5. New 16 MB Memory Card (TME) Card

At the new sites, where 16 Mb TME card is used in place of 4 Nos of 2 Mb memory card in BMs and 2 Nos of 2 MB memory card 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.

6.3. GENERAL - DO'S AND DON'TS FOR O&M ACTIVITIES

6.3.1. Take 'ed' and 'bd' back-ups daily in low traffic hours.

6.3.2. At SBM-RAX sites, take 'bc' back-ups after every 15 days against the standard procedure of 2 months and clean the 'bc' file groups regularly to have the sufficient disk space. However, at MAX-L sites and at those sites where disk space is more because of the retrofitting of new Hard Disk, standard procedure of 'bc' backups after every two months can be followed.

6.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:

Chapter 6.

58 C-DOT DSS MAX

IOP5x>df.

In the above display, the content against /data indicates the current available disk space.

6.3.4. A no. of new traffic reports have been implemented in 2_2_1_6 software. If the traffic reports are enabled, delete the 'tf' file group regularly.

6.3.5. The 'old' backups (i.e. ed, bd, bc ... etc) taken in S/W release 2_1_1_1, should not be restored in the Exchange after upgrading it to new software release 2_2_1_6.

6.3.6. While taking the display/printouts of TRUNK/ROUTE related traffic reports, the input against parameter MOD-NO should always be “AM”.

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

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

6.3.9. Do not remove the floppy and cartridges from the drives till the drive's LED is glowing.

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

6.3.11. It MBM-Sites, do not create DTMF-ckts in TRUNK BMs and MF-Senders/ Receivers in Line-BMs.

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

6.4. OPERATION AND MAINTENANCE RELATED GUIDELINES

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

DO'S AND DONT'S


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 “COPY-IN” is sufficient. As and when BMDC has been restored in working exchange, "ed" as well "bd" must be copied.

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

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

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

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

Chapter 6.

60 C-DOT DSS MAX

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 should be updated for compatible software EPROM. The TIC unit will not become INS unless compatible software EPROM is not used.

6.4.6. Mandatory Execution of MOD-DAY-TYP

It should be ensured that in 1st week of January & July of every year, the command is executed to define the day type.

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

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

vi) While changing any Processor Card in BM, CM & AM, the jumper settings and EPROM status should be ensured.

DO'S AND DONT'S


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.

6.4.9. 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 utilise 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.

6.4.10. 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 characteristics, the no. of trunks should be reduced to <100. After modification, the deleted trunks should be added.

Chapter 6.

62 C-DOT DSS MAX

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.


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 :-

0 lm.x.y (where x.y is the unix release, say 11.0) 1 ve.x.y 2 vh.x.y 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

Annexure - A

64 C-DOT DSS MAX

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 OMTI 0 0x11 w0o0_* - w0

FLOPPY OMTI 0 0x11 f0o2_* m320_2s* f

CART OMTI 0 0x11 c0o3 m350_0t c

Enter DEV-FILE for WINCH to be configured as root device:

The table displayed is a list of devices present in the system. From the devices marked WINCH, select the device on which the root file system is to be made.

At the prompt, enter the device filename as displayed (under DEV-FILE heading) without change. For example, in the table above, the device filename is w0O0_*

Note : In case of Single Disk, device file name is not required.

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 : 520/700/1200/2100 • If formatting is required for 520 MB/1.2 GB disk, 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:

IOP LOADING PROCEDURE


Formatting winch #x .........

(In the above display, #x, would be #0 as only single disk is being used)

Wait till the following print appears :

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 :

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 :

Annexure - A

66 C-DOT DSS MAX

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 release. • The system would display :

Creation of file systems (other than ROOT) available

Create file systems other than root (y/n) ? • Give 'y' to continue loading of software i.e., BAC, CPC & BMDC.

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

IOP LOADING PROCEDURE


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

Annexure - A

68 C-DOT DSS MAX

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.


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 UNIX-only to ensure availability of sufficient disk-space. However, this is not required to make the copies of a floppy.

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 only UNIX and then 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;

>ulimit 150000

#>mkdir /code/copy

#>cd /code/copy

4. #>dd if=/dev/rmt/m350_0t of=xxxx bs=60k count = zzz

where count zzz = blk size/120 (result rounded off to next integer)

e.g., if size 49108, then count = 49108/120 = 409.23 ≡ 410.

This will copy the contents of the master cartridge in to file 'xxxx'. After completion of copying process which may take 15 to 60 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.

Annexure - B

70 C-DOT DSS MAX

♦ Execute the following command #>dd if=xxxx of=/dev/rmt/m350_0t bs=60k count = zzz

After completion of the process (15 to 60 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 /code #rmdir copy

PROCEDURE FOR MAKING COPIES OF FLOPPY :

The copies of the floppy can be made by using the following procedure :

1. Login to “root” account and insert the master FLOPPY in the floppy drive.

2. Execute the command : # mkdir /data/dump/copy # cd /data/dump/copy

#>dd if=/dev/rdsk/m320_2s0 of=xxxx bs=60k

Wait for the display of block size.

3. Remove the master 'FLOPPY' and insert the floppy on which a copy is to be made. Execute the command.

#>dd if=xxxx of=/dev/rdsk/m320_2s0 bs=60k

wait for the display of block size which should match with that of master floppy.

Repeat STEP-3 to generate as many copies as desired. However, to generate copies of another master, repeats STEP-2 and STEP-3 again. Remove file xxxx after required no. of copies have been generated. rmdir /data/dump/copy

NOTE: If minload floppy has to be duplicated, then use m320_2s7.

DUPLICATION PROCEDURE FOR CARTRIDGE/FLOPPY


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

72 C-DOT DSS MAX

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 -- 2F98 2A3D

17. U46 70AC 8E9A DF80 F5E6 E351 2D33 -- 528B 9FF7

18. U49 06E1 63AC 7CCD BDCB DFA3 14F2 -- -- 2BFF

19. U57 C9D7 797F EF00 4040 -- OB7C -- -- 2206

20 U64 8A82 1A6D -- AEF1 -- -- -- -- 9A21

21. U72 1D9D A974 -- B07E -- -- -- -- E151

22. U75 520D 8A82 -- -- -- --

Language Ids 01 07 09 08 02 03 04 06 05

NOTE :

1. All the EPROMs are 27C512 (200 nsec).

74 C-DOT DSS MAX

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

There are two different procedures to equip the new base module in MAX-L/ MAX-XL exchange. The first procedure is the on line equipage of the additional BM without any system down time. The other procedure is off-line procedure where the

ADDITION OF BASE MODULE


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

Annexure - D

76 C-DOT DSS MAX

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.

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 requried 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

78 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

80 C-DOT DSS MAX

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

82 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

BTSBTS

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

Changes Required to be made to Run CTS-B Tool in 2_2_1_6 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 - G

84 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 - H

List of ISD Routs

Level No. ROUTE CODE REGION PULSE RATE BMDC CRG-RTN

1 1. 001 America North 3.0/3.4 19/29

2 2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15

16

17

18

19

20

21

22

0020

0021

0022

00230

00231

00232

00233

00234

00235

00236

00237

00238

00239

0024

0025

0026

0027

0028

00291

00297

00298

Africa

Africa

Africa

Africa

Africa

Africa

Africa

Africa

Africa

Africa

America

Africa

Africa

Ocenia

Africa

Africa

Africa

Africa

Africa

America

Europe

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

18/28

18/28

18/28

18/28

18/28

18/28

18/28

18/28

18/28

18/28

19/29

18/28

18/28

18/28

18/28

18/28

18/28

18/28

18/28

19/29

20/30

Annexure - H

86 C-DOT DSS MAX


23 00299 Europe 3.0/3.4 20/30

3. 24 003 Europe 3.0/3.4 20/30

4 25 004 Europe 3.0/3.4 20/30

5 26 005 America (C,N, & S)

3.0/3.4 19/29

6 27 006 Asia & Oceania 3.0/3.4 18/28

7 28. 007 Europe 3.0/3.4 20/30

8 29.

30.

31.

32.

33.

34.

35.

0081

0082

0084

0085

0086

00880

00886

Asia

Asia

Asia

Asia

Asia

SARRC

Asia

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.4/4.0

3.0/3.4

18/28

18/28

18/28

18/28

18/28

17/27

18/28

9 36.

37.

38.

39.

40.

41.

42.

43.

44.

45.

46.

47.

48.

49.

0090

0092

0094

0095

00960

00961

00962

00963

00964

00965

00966

00967

00968

00971

Europe

SAARC

SARRC

SAARC

SAARC

Asia

Asia

Asia

Asia

Gulf

Gulf

Gulf

Gulf

Gulf

3.0/3.4

3.4/4.0

3.4/4.0

3.4/4.0

3.4/4.0

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

3.0/3.4

20/30

17/27

17/27

17/27

17/27

18/28

18/28

18/28

18/28

18/28

18/28

18/28

18/28

18/28

LIST OF ISD ROUTS



50.

51.

52.

53.

54.

55.

56.

57.

00972

00973

00974

00975

00976

00977

0098

0099

Asia

Gulf

Gulf

SAARC

Asia

SARRC

Asia

Europe

3.0/3.4

3.0/3.4

3.0/3.4

3.4/4.0

3.0/3.4

3.4/4.0

3.0/3.4

3.0/3.4

18/28

18/28

18/28

17/27

18/28

17/27

18/28

20/30

88 C-DOT DSS MAX

Annexure - I

List of Charge Rate Numbers

All the charge Rate numbers must be 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

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

Annexure - I

90 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 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




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



Annexure - I

92 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

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



Annexure - I

94 C-DOT DSS MAX


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






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 - I

96 C-DOT DSS MAX


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



*Charge Rate Number = 15

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




Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - I

98 C-DOT DSS MAX


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






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



Annexure - I

100 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 countries in America


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 the EUROPIAN Countries


Init Charge

Charge Period

Prd Charge

CHARGE MODE

METERING INFO

ANSWER INFO

RING INFO BEEP INFO



Annexure - I

102 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 - I

104 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 - I

106 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





*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



Annexure - I

108 C-DOT DSS MAX

*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














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













Date post:	18-Jan-2016
Category:	Documents
Upload:	mbhagavanprasad
View:	42 times
Download:	0 times

Retro 2216

Documents