Software Release 2 - 2 - 1 - 9 (2.22) Retrofit Procedure For Max/Sbm-Rax/Tax

C-DOT DSS MAX
SOFTWARE RELEASE 2_2_1_9(2.22) RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX
System Practices
Section No. 400-643-0967 Draft 01, June 2010
C-DOT DSS MAX
2010, C-DOT Printed in India
C-DOT DSS MAX SOFTWARE RELEASE 2_2_1_9(2.22) RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX
DRAFT 01 JUNE 2010 ASADHA 2066 SERIES 600 : SOFTWARE CSP SECTION NO. 400-643-09467 THIS CDOT SYSTEM PRACTICE REFERS TO THE CDOT DIGITAL SWITCHING SYSTEM MAIN AUTOMATIC EXCHANGE (ABBREVIATED AS CDOT DSS MAX IN THE REST OF THIS PUBLICATION).
THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION PURPOSES AND IS SUBJECT TO CHANGE WITHOUT NOTICE.
A COMMENT FORM HAS BEEN INCLUDED AT THE END OF THIS PUBLICATION FOR READER'S COMMENTS. IF THE FORM HAS BEEN USED, COMMENTS MAY BE ADDRESSED TO THE DIRECTOR (C & S), CENTRE FOR DEVELOPMENT OF TELEMATICS, C-DOT CAMPUS, MEHRAULI, NEW DELHI - 110 030
2010 BY CDOT, NEW DELHI.
Table of Contents
Chapter 1. Introduction & Release Highlights ................................................................................................ 7 1.1. 1.2. 1.3. Chapter 2. SBM RAX/TAX and C-DOT DSS MAX ............................................................................. 7 Software Release 2_2_1_6 (2004) ...................................................................................... 8 New Software Release 2_2_1_9 (2007) ........................................................................... 22
Software and Hardware Status.................................................................................................... 29 2.1. 2.2. Software status ................................................................................................................ 29 Change of Eproms Required for S/W Release 2_2_2.22_9 over Existing Release ........... 2_2_7.7_6 .......................................................................................................................... 36
Chapter 3.
Software Retrofit Philosophy and Pre-Retrofit Checks ..............................................................37 3.1. 3.2. 3.3. General Considertions ..................................................................................................... 37 Pre-Retrofit Checks ..........................................................................................................38 Contact nos. of c-dot control room ................................................................................... 38
Chapter 4.
Retrofit Procedure From 2_1_7.7_6 to 2_2_1_9........................................................................... 39 4.1. 4.2. 4.3. 4.4. 4.5. 4.6. 4.7. 4.8. 4.9. 4.10. Pre Retrofit Activities ......................................................................................................39 Mock retrofit Procedure One day before the Retrofit date ......................................... 39 Final Retrofit Procedure .................................................................................................. 43 Post-Retrofit Checks ........................................................................................................ 48 Recovery Action ................................................................................................................ 49 Retrofit Completing Activities ........................................................................................ 49 Procedure to View Subscribers & TGPs Detail Bill Records Through RGEN Utility . 50 Time Zones and Tariff Classes for HOLIDAY & Normal Day ...................................... 50 Modify Definition of Day Type 1 and 2 as per Table I, using command MOD-TYP- ...... DAY .................................................................................................................................. 51 Implementation of Distinctive Ringing feature ............................................................. 52
Chapter 5.
Retrofit Procedure from S/W 2_2_1_9 (2.11) / 2_2_1_9 (2.13)/2_2_1_9 (2.16) to ....................... 2_2_1_9 (2.22) ................................................................................................................................ 53 5.1. 5.2. Change of S/W Deliverables in 2_2_2.22_9 over 2_2_2.11_9/ 2_2_2.13_9/2_2_2.16_9. 53 Retrofit Procedure for C-DOT Exchanges having S/W 2_2_2.11_9/ 2_2_2.13_9/ ............ 2_2_2.16_9 ........................................................................................................................ 53
Chapter 6.
Details of Centrex Feature Implementation ............................................................................... 56 6.1. 6.2. 6.3. 6.4. Main Highlights of Centrex feature offered in this release are : .................................. 56 Details of Centrex Feature Implementation. ................................................................. 56 Call Handling Strategy for different type of Centrex Calls ........................................ 57 Change In Usage Of Existing Facilities By Centrex Members ..................................... 58
6.5. 6.6. 6.7. 6.8. 6.9. 6.10. Chapter 7.
Charging and Billing ....................................................................................................... 58 Traffic Observation ..........................................................................................................59 Changes in Man-Machine Interface................................................................................ 59 Detailed Description Of New Commands ....................................................................... 64 Enhancements To Existing Commands.......................................................................... 76 Changes In SIF Procedures ............................................................................................. 90
Special Priority Implementation in S/W Release 2_2_1_9 ......................................................... 91 7.1. 7.2. 7.3. 7.4. 7.5. Feature Introduction........................................................................................................ 91 Feature Implementation.................................................................................................. 91 At Originating Exchange ................................................................................................. 91 At Transit Exchange ........................................................................................................ 94 Commands Updations...................................................................................................... 95
Chapter 8.
New Strategy for Detailed Billing Records (CDR) Generation & Transfer............................... 97 8.1. 8.2. Feature Introduction........................................................................................................ 97 Implementation ................................................................................................................97
Chapter 9.
Do's and Dont's .............................................................................................................................. 99 9.1. 9.2. 9.3. 9.4. IOP Related Problems and Solutions ............................................................................. 99 Do's and Dont's for Card Handling ............................................................................... 103 General - DO'S and DON'TS for O&M Activities ........................................................ 104 Operation and Maintenance Related Guidelines ......................................................... 105
Annexure - A Annexure - B Annexure - C
IOP Loading Procedure............................................................................................................... 110 Duplication Procedure for Cartridge/Floppy ............................................................................. 116 EPROMs for English Announcements ....................................................................................... 120
Annexure - C (Contd.)EPROMs for BI-Lingual Announcements ......................................................................121 Annexure - D Addition of Base Module ............................................................................................................. 122 Annexure - E Annexure - F Optimized Utilization of PHC Terminal in VU ......................................................................... 128 Use of Subscriber Based Category for WLL Subscriber ........................................................... 129
Annexure - G Abort Filter Card (AFB) ECN Details ....................................................................................... 131 Annexure - H New Implementation on NSC and Fault Isolation Strategy .................................................... 133 Annexure - I Annexure - J Changes Required to be made to Run CTS-B Tool in 2_2_1_9 Software ................................ 139 List of Charge Rate Numbers..................................................................................................... 141
H:\MAX-XL\WORD\SWR2219(2.22).DOC
December 26, 2011
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. Software Release 1_4_2.25_4 (1997) This release was being used by BSNL at sites, where main C-DOT exchange was having connectivity with private operator network. This release supported following features in addition to all the features of S/W 1_4_5.43_3 : Revenue counters and detail billing on trunks. CLI for long distance calls when C-DOT DSS is configured as ILT/TAX 'CAMA' application when exchange is being used as ILT/TAX. CLI for analog subscribers.
Software Release 1_4_8.1_3 (1997) This release was being used by BSNL at sites, where CCS7 signalling and Network Synchronisation was required. All the 'MAX-XL' exchanges were being commissioned with this software. These two features were in addition to all the features contained in S/W 1_4_5.43_3. Software Release 2_1_1_1 (1998) This software release 2_1_1_1 was introduced to offer new features such as ISDN, 800K BHCA etc. as well as merge all the features of the earlier three different software releases. Thus all the features could be offered to subscribers at any site after retrofitting S/W release 2_1_1_1. The last patch in this series was 2_1_7.9_1.
Chapter 1
Software Release 2_2_1_4 (2001) The software release 2_2_1_4 was introduced to support V5.2 protocol capability in addition to all the features supported by S/W 2_1_1_1. This provided connectivity with WLL (Access Network) of HFCL/Hundai, LG or Lucent technologies & ANRAX of C-DOT technology. This software supported subscriber category based charging. Moreover same S/W supported Intelligent Network services also. The last patch in this series is 2_2_4.4_4 for PSTN and 2_2_5.5_4 for IN working. 1.2. SOFTWARE RELEASE 2_2_1_6 (2004) New S/W release 2_2_1_6 has been introduced to provide dynamic control for Lev 9x (except 90,96) default Detail Bill on these routs, Line Monitoring Feature, Increase in 'AI' links to '14' in MBM & '11' in SBM. These facilities are in addition to all the features supported in S/W 2_2_1_4. Detail of all the features is given below: 1.2.1. 1.2.1.1. New Features Introduced in 2_2_1_6 S/W Release Number of Access Interface Links have been Increased to '14' per BM in Case of MBM & '11' in SBM Exchange It will be possible to connect '14' interfaces on V5.2 in one BM with single PCM Connectivity. This will find use for 'AN-RAX' connectivity. 1.2.1.2. Detail Billing Records Generation on all 9x Calls (Excluding 90 & 96) by Default and Dynamic Locking Control for these Levels Dynamic locking/unlocking is available for 9x (excluding 90 & 96) levels as 'OG-UPTO-REG' access. Dynamic Locking/unlocking of Levels 9x is achieved by Dialling 124 ABCD1 and 124 ABCD5 respectively. This procedure will lock/unlock 9x levels simultaneously. Individual locking of 9x levels is not supported. CDRs will be generated for 9x (excluding 90 & 96) calls by default, in addition to '0' & '00' levels. Meter increment for 9x level calls will be done in 'STD' counters instead of Local Counters. Detail bill for these calls can not be stopped by any means. 1.2.1.3. New Announcements for Feature Invocation (Activation/Deactivation) in Place of Tones. For various features invocations like Dynamic locking/unlocking, now 'announcements will be fed instead of tones. The announcements are following: 1. 2. This feature has been invoked successfully. Feature invocation has failed.
C-DOT DSS MAX
INTRODUCTION & RELEASE HIGHLIGHTS
Note : Two Nos. of additional Language EPROMs will be required in each 'ANNC' card, to achieve this feature. 1.2.1.4. Queue Announcement to Caller in Case of Call Waiting in Place of RBT. In case of Call-waiting, Calling party will get Queue Announcement instead of RBT Announcement in this case will be "kindly wait, you are in Queue". 1.2.1.5. Unequipping of 'BM' Possible through 'CRP' Command "UNEQ-BM" For this, there should be no data (subs/trunks) equipped in the BM. All the frames should be unequipped. Unequip all 'mfc' cards also. 1.2.1.6. Separate Area (STD) Code for RSU and Access Network for CLI Purpose It is possible to assign separate STD code for RSU/Access Networks belonging to different SDCA's. For this, 'Area Code' field is available in 'MOD-XCOD' command. If Area Code field is not defined in an 'XCOD', then system parameters ARCD* will be referred for prefixing Area Code to CLI for that 'XCOD. Area Code Defined in 'MOD-RBM-XCOD' will superseed, the code defined either in 'MOD-XCOD' or 'ARCD*' parameters. 1.2.1.7. Separate Access for Special Services in Case of RSU & Access Network By using 'MOD-RBMNRM-CONFIG' command special services like 131, 198 etc. can be mapped separately for RBMs. For this special service code 131/198 etc. should be opened on 'Alternate Nos' of the Main Exchange. If these routs are opened as normal rout, then mapping will not be possible. For Access Network, command 'CRE-ANNRM-CONFIG' can be used to map special service codes to DIR. NOS. belonging to respective 'AI' Nos. 1.2.1.8. Line Monitoring Feature to Enable Parallel Speech Monitoring of Any Subscriber No. For this the monitoring agency No. can be from the same exchange or any other exchange on Subscriber Trunk Dialling. Maximum 30 Nos. per BM (A maximum of 100 Nos. in whole Exchange) can be put on speech Monitoring Observation simultaneously. Special CDRs will be maintained for such calls. No charging will be done for calls routed to Monitoring Agency Nos.
Chapter 1
1.2.1.9.
Change of SIF Codes for 3W_Conf/6W_Conf/Absnt_Fixed_Num Features to Enable Functioning of New Special Services 125X New Codes have been covered in para 1.2.2.3.
1.2.1.10.
'DISPL-SUB-LIST' Command Enhancement This command has been enhanced to get list of subscribers having different 'SUB-CAT'.
1.2.1.11.
Transaction Records Transactions on IOP upto '10000' records will be preserved in Trans files, after which, records will be overwritten. The file size has been reduced to half as compared to previous release 2_2_1_4. Trans files now will be transferred during IOP synchronization.
1.2.1.12.
New Strategy for Charge Rate Number Definition In S/W 2_2_1_6, any 'CRG-RTN' must be defined for all the 'Tariff classes' defined in Day Type = 1 or 2. Otherwise call will fail for categories for which such 'CRG-RTN' are allotted. In addition some recovery messages will be generated which may cause frequent system initialization.
1.2.1.13.
Calling Line Identification (CLI) Sending and Presentation A. CCS7 Signalling : Area Code for prefixing to 'CLI' is defined in system parameters ARCD-DGT*. In case 1st digit (ARCD-DGT1) defined is zero (i.e. 10), then Area Code without '0' will be sent towards next exchange. During CCS7 signalling messages parameter 'NAI' will be set as National (significant) Number. At the destination exchange (having 2_2_1_6 S/W), 'CLI' with '0' will be presented to the called party. In case ARCD-DGT1 = Non-Zero, then 'NAI' will be set as 'LOCAL' and 'CLI' without zero will be sent. At the destination exchange, CLI without zero will be presented the called party. Caution : In this case, ISD calls, to some countries specially 'Gulf Area' may fail. B. MOR-R2 Signalling In case, 'ARCD-DGT1=10', then Area Code without zero will be sent towards next exchange. At the destination exchange, CLI with zero will be presented to the called party. In case, 'ARCD-DGT1=Non-Zero, then Area code, without zero i.e. as defined in 'ARCD-DGTS' will be sent towards destination.
10
C-DOT DSS MAX
At the destination exchange, CLI with zero will be presented to the called party. Conclusion: Always define, 1st digit of Area Code as '0' in system parameters i.e. ARCD-DGT1=10. Also define NUM-ANI=10 in order to ask for 10 digits CLI. 1.2.1.14. Implementation of IVRS, Application as per 'TEC' Guidelines As per New 'TEC' requirements, a route 1951/1952 is to be opened towards IVRS. Now, when a call for deleted subscriber is received, the exchange will route the call towards IVRS with digits '195x' prefixed to the Dialled digits. As a result, the deleted No. shall be sent to IVRS, which will directly announce the Changed Number to the Calling Party. To achieve this, following steps of Data creation are required :1. 'MOD-SYS-DIRNO' OPR-TYP TYPE DIRNO 2. 'CRE-ROUT' ROUT-CODE : 1951, DIGIT-LENGTH = OPEN : : : CRE IVRS 1951 or 1952
with O/G TGP opened towards IVRS. This 'TGP' should have "Rank of digit = 5". 3. Delete the DIRNOs DEL-SUB DIRNO TEN MODE 1.2.1.15. : : : No. to be Deleted <> IVRS
Call Diversion Possible on all 1x Levels (Except 10x) BSNL Subscribers availing Answering Machine Service (AMS) can divert their calls on Level 170511, 170512, 170513 etc. or any other 1x level as desired (except 10x).
11
Chapter 1
1.2.1.16.
Software Configuration Display Crp command 'DISPL-SW-CONFIG' has been modified to show complete Software Release Identification on its first page of the output.
1.2.1.17.
Continuity Check Feature and Compatibility Continuity check and compatibility features are provided now as per latest ITU-T recommendations for CCS7 signalling. Continuity check is achieved by connecting a Transceiver (check tone transmitter and receiver) to the go and return paths of the outgoing circuit at the first and succeeding exchange. The continuity check is considered successful when a tone (2000 20 Hz) is sent on the go path and is received on the return path within acceptable transmission and timing limits. Various timers like T8 (10-15 sec), T24(2sec), T25 (1-10 sec), T26 (1-3 min), T27 (4 min) are used for continuity check.
1.2.1.18.
CCS7 Message Analyser CCS7 Message Analyser is available in S/W 2_2_7.5_6 onward; similar to MF Signalling Analyser. This will monitor the messages between two exchanges when calls are made on #7 trunks. The analyser will display the sequence of forward and backward message transmitted between two exchanges as per call basis on the #7 trunks put on 'ISUP' observation using 'MOD-TRK-OBS' command. Reports can be seen by crp command 'DISPL-NSMA-RPT'.
1.2.1.19.
New Strategy for Charging on Local PCO's Local PCOs can be given access level as 'OG-UPTO-REG' now, thus allowing them to have access to '95' level routes. In this case, charging for local call will be done as per 'CRG-RTN' defined in 'SYS-PARAM' - 'PCO-MTR-LCL'. For route calls, charging will be done as per 'CRG-RTN' defined in route parameters.
1.2.1.20.
AI Traffic Report The format for AI traffic report output has been changed. Traffic reports have been further elaborated.
1.2.1.21.
A new feature of Crystal Swing Detection in NSC had been implemented in S/W 2_2_7.7_6. Feature details and fault isolation strategy has been explained in Annexure-H. This feature facilitate exchange administrator to isolate faulty NSC card in the system. Dialling by Equipment (DBE) Facility for Trunk Testing Dialling by Equipment (DBE) is 'ORG-FAC' to be given to exchange administrator number. To test any trunk port during any time of the day, that particular trunk (TEN) is to be put on. 'DBE' observation by A `mod-lnk-
1.2.1.22.
12
C-DOT DSS MAX
obs. Then using allotted service code '683' calls can be originated on this trunk port. 1.2.2. 1.2.2.1. Important Features of the Previous Links 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: 1.2.2.2. 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
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.
13
Chapter 1
1.2.2.3.
Subscriber Features & Supplementary Services The subscriber features have been implemented as per specifications of DOT/TEC document No. G/ASF-01/01 MAR 94. The control/invocation procedure has been standardised and charging for different services has been implemented so that these services can be released to subscribers with standard procedures for usage as well as billing by DOT as an operator. Invocation procedure as well as system limit for each service is listed subsequently in this section. DTMF subscribers as well ISDN subscribers will follow the procedure as specified in this section, unless it is specifically mentioned for ISDN subscribers. The decadic subscribers will follow the procedure by replacing * or # by '1' in the beginning only without dialling any other digit in place of # in the end. A DTMF subscriber can use both the options. New Invocation Procedures for Subscriber Services Number Identification Supplementary Services
Sl.No. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Facility Type CLIP CLIR CLIRO MCID MSN DDI SUB COLP COLR COLRO Activation NO NO NO See Note-1 NO NO NO NO NO NO Deactivation NO NO NO NO NO NO NO NO NO NO Remarks
Only for ISDN Only for ISDN Only for ISDN Only for ISDN Only for ISDN Only for ISDN
Call Offering Supplementary Service

Sl.No. 1. 2. 3. 4. 5. 6. 7. Facility Type LH CFU (fixed) CFU (SEL) CFB (GRP) CFB (SEL) CFNR (GRP) CFNR (SEL) Activation NO *224# *14 B# NO *220 B# *228# *222 B# Deactivation NO #225# #15# NO #221# *229# #223# See Note-2 See Note-3 $ See Note-2 See Note-3 $ See Note-2 See Note-3 $ Remarks
For Centrex Subscriber dial Escape Code before number 'B'
14
C-DOT DSS MAX
Call Completion Supplementary Services

Sl. No. 1. 2. 3. 4. 5. 6. Facility Type CW CH-WOR CH-WR TP Hot Line (Timed) Hot-Line (Un-timed) Activation *18# HOLD/RETRIEVE HOLD/RETRIEVE SUSPEND/RESUME *20 B# NO Deactivation #19# NO NO NO #21# NO See Note-4 Only for ISDN Only for ISDN Only for ISDN See Note-3 $
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. 1. Facility Type Dynamic Locking Activation Deactivation Remarks 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 See Note-6 See Note-6 Only for PSTN See Note-7 $ Only for Exchange Administrator for testing purpose. 15
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 * 16 hh mm # *226 hh mm # *686# #17 hh mm # #227 hh mm# #685#
2. 3. 4. 5.
Alarm (Once) Alarm (DLY) Queuing Directed (DBE) call
*681 TEN # for line *682 TEN B# for trunk *683 TEN # for Tone/Annc.
Chapter 1 Sl.No. 6. 7. 8. Facility Type AOC-E & AOC-D 16 Khz for Home Meters Distinctive Ringing Activation NO NO No Deactivation NO NO No Remarks Only for ISDN Only for PSTN See Note-8 Only for PSTN subscribers
Following Changes in SIF Service Codes are as per TEC requirements

SIF ABSENTEE_FIXED_NUM_ACT ABSENTEE_FIXED_NUM_DEACT 3W_CONF 6W_CONF ADD_CONF CONF_TOGGLE DROP_SEL_PARTY Old Code 28 29 250 251 252 253 254 New Code 498 499 490 491 492 493 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#. 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. 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. 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 - 2 :
Note - 3 :
Note-4 :
16
C-DOT DSS MAX
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. 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. 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. 25% of the total termination capacity can be used as 16 KHz ports subject to the equipage of compatible hardware.
Note-6 :
Note-7 :
Note-8 : 1.2.2.4.
Enhanced Traffic Reports Monitoring of traffic flow has become one of the most important functions of network administrator. The traffic reports are used to monitor the network performance in terms of Call Completion Ratio (CCR) as well as to take the corrective measures to improve the CCRs by re-routing/re-dimensioning of network resources. The traffic reports in C-DOT DSS have been re-organised to generate following parameters : Separate Reports to monitor performance of PSTN and ISDN subscribers CCR for Local and O/G calls. Trunk Groups/Route Reports CCS7 Link performance reports Separate counters for individual line/ trunk circuits for monitoring the performance of individual circuit. Details of call failures/ counters for failure analysis.
The organization of traffic reports help the administrator to monitor the exchange performance for different applications as local, ILT and TAX Configurations. 1.2.2.5. Revenue Metering and Detail Billing on Trunks The new telecom policy enables private operators to offer basic and cellular telephony services in different telecom circles. The different operator exchanges will be connected amongst themselves and to the DOT controlled TAXs by trunks. There is a need that the various telecom service providers keep track of the revenues which are shared by them, on the basis of resource
SOFTWARE RELEASE 2_2_1_9(2.22) RETROFIT PROCEDURE FOR MAX/SBM-RAX/TAX 17
Chapter 1
utilisation. With revenue metering on trunks implementation in C-DOT DSS, it can be configured as TAX with function as network's hand-over point. Online charging on per call basis is done on Trunk Groups (TGPs). At the end of every successful call, the charge meter of TGP is incremented by the applicable charge depending on the distance, type of day and call duration. Also information of number of successful calls on the TGP is maintained. A detailed billing record for every successful call can also be generated if required A trunk group can be put under detail billing observation in each configuration of C-DOT DSS as Local/Tandem/TAX or ILT. However calling party identity will be part of detail billing records i.e. CAMA functions, only when exchange is configured as TAX or ILT. In case of revenue metering on ISUP trunks, the meter counters are incremented and detail bill records are made by incrementing the counters for actual charge units in both the cases of CHU and CHB. All the trunk groups are associated with Local, STD and ISD meter counters. In case of Bothway trunk groups, two sets of counters (one each for I/C and O/G) are associated with each TGP. 1.2.2.6. Year 2000 (Y2K) Solution Different commands have been modified to support 4 digit year field to solve the problem of year 2000. 1.2.2.7. Killer Trunk Implementation As per definition/specification in the latest revised specifications of TEC, the concept of Killer Trunks has been implemented. The scope of definition has been improved by C-DOT to ensure unmanned operation of interconnecting resources and their maximum availability to carry the traffic. This feature will block the faulty junctions automatically and restore after monitoring the fault removal. This will be very useful feature at ILT and TAX, connecting the remote exchanges with limited resources. 1.2.2.8. Automatic Modification of Tariff Class to New Pulse Rate if Tariff Class gets Changed During the Call As per definition of charging, in addition to distance and day type, the time is also a important factor to decide the charging. Accordingly, a day i.e. 24 hours are divided in different time zones. If a call progresses to the next tariff zone, the corresponding tariff class becomes effective for subsequent period. 1.2.2.9. 20 Digit Routing Capability As per decision of ITU-T, the international numbering plan has been increased to 17 digits from 16 digits. To take care of future requirement, the routing capability has been increased to 20 digits.
18 C-DOT DSS MAX
1.2.2.10.
Automatic Detection and Reporting of Large Duration Calls on Subscriber and Trunks To meet the requirement of automatic reporting of large duration calls, it is possible to define the threshold for Call Duration as well as Charge Units. An exception report is generated for all the calls, crossing the threshold value. The exception report is generated on the OOD as well as printer. It is possible to retrieve the records at any time as these are also available in the disks as logs. The report include all the details, related to the call and required by the administrator, e.g. Calling Party Number, Called Party Number, Call Duration, Charge Units, Time of Originations etc.
1.2.2.11.
Trunk Interface in RSU Keeping in view the topology of telephony networks in the SSAs, the trunk interface (Analog or Digital) has been implemented in RSU. It is possible to parent the smaller exchanges at RSU itself. (Fig. 3.1) This results is advantages as listed below: i) ii) Avoid the requirement of separate media/connectivity for smaller exchanges upto main exchange. Efficient utilization of media, between RSU and Main Exchange by sharing the resources to carry the traffic to/from the network to smaller exchanges. 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.
iii)
1.2.2.12.
CAMA for Smaller Exchanges, Parented on R2 Signalling With implementation of CAMA along with suitable MMI commands to generate the detail bill from SSA HQ for smaller exchanges/parented on R2 signalling, it is felt that C-DOT DSS is ideally suited for Indian Telecom Network, specifically for SSA Networks.
1.2.2.13.
Enhanced Command DISPL-BILL-REC The existing command has been enhanced to support the following functions: Display of billing records of Subscriber and Trunks Display of billing records of subscriber, belonging to specific level e.g. in the numbering plan 548xxxx, it is possible display the records of 100 subscribers belonging to 54823xx. Display of TGP/Subscriber bill records with exceptionally higher charge units.
19
Chapter 1
Display of CAMA records in the format of detail bill to facilitate the Administrator to generate the detail bills for smaller exchanges from a centralised place.
1.2.2.14.
Command DISPL-XCHG-MTR to Monitor the Revenue Generation It is possible to get the total number of charge units to monitor the revenue generation in the exchange. The flexible implementation of the command facilitate the Administrator to monitor the revenue generation for different application as Local, ILT or TAX. In case of an ILT exchange, it is possible to get the revenue figures with break up for the subscribers of its own exchange as well as revenues for parented exchanges, for which it is functioning as TAX.
1.2.2.15.
Distinctive Ringing for Long Distance Calls It is used to notify the caller that the incoming call is from distant place. The subscriber gets one type of ringing for Local calls and a different type of ringing for STD/ISD calls. The implementation of this feature is dependent on the type of Power Supply used in the exchange. In case of already commissioned sites, this feature will be available to the subscribers only after implementing the necessary modifications as the Power Supply Card and compatible TIC PROMs. No special procedure is required for activation, deactivation or usage of the failure and it is available by default to all the subscribers in the exchange.
1.2.2.16.
Inbuilt MF Signalling Analyser Due to integration of multiple technologies in the network along with coexistence of different interworking scenarios, the inbuilt signalling tracer is required to collect the details of call failures and take the corrective measures. The Multi Frequency Signalling Analysis is possible in C-DOT DSS on one or more than one trunk, simultaneously but a max. of 32 trunks at a time. The details of forward and backward signal are logged in IOP which can be displayed any time.
1.2.2.17.
Threshold Alarms for PCMs between RSU and Main Exchange In case of partial failure i.e one or more PCMs have failed, audio and visual alarm is raised for the attention of O&M personnel to take corrective measures. The exchange administrator can programme the parameters to control the raising and retiring of alarms.
1.2.2.18.
16 Tariff Classes to Support New Tariff Plan of TRAI To meet the requirement of new tariff plan, the tariff classes have been increased to 16.
20
C-DOT DSS MAX
1.2.2.19.
CCS #7 Signalling System Signalling System #7 (SS7) is a common channel inter-exchange signalling mechanism that is intelligent, efficient, flexible and economical. The network comprising of switches with SS7 capability also provides the infrastructure for network features and services such as ISDN, Intelligent Network, Mobile Applications, Operation and Maintenance Applications, etc. The system has a 4-layer architecture. Layer1 provides the Physical Layer, usually a 64 Kbps channel in a digital environment using PCM technique for transmission. Layer2 provides the Datalink Layer functionality and is responsible for reliable transmission of messages over a link without loss, duplication or mis-sequencing, through flow control and error correction mechanisms. Layer3 provide the Message Handling (discrimination and routing) and Network Management (Traffic, Link and Route Management) functionality a part of the Network layer. All these comprise the Message Transfer Part (MTP). Level4 is for the User Parts. ISDN User Part (ISUP) is one that defines the logical sequence of events for a particular application using the services of the lower layers. ISUP defines the procedure for control of switched services in ISDN and covers both voice and non-voice (circuitswitched 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 SPcum-STP. The implementation is supported by incorporating necessary ManMachine. The Call Processing software provides ISUP as well as the interworking with DSS1, MF and Decadic signalling.
1.2.2.20.
Network Synchronisation The Network Synchronisation Controller (NSC) card in MAX-XL system is capable of synchronising its own clock to the network clock and supplying it to the exchange. This network clock is available through the DTKs coming from either a higher level or a peer level exchange and is extracted by the DTS card in a Digital Trunk BM before being given as input to the NSC cards in the CM complex. With this synchronisation capability, inter-exchange data transfer at very high rates can be achieved since the slips encountered will be very less. This implementation offers level2 network synchronisation capability in MAX-XL. However SBM-RAX and MAX-L exchanges do not have NSC card inbuilt, therefore Network Synchronisation feature in these exchanges can be implemented by using C-DOT Network Synchronisation Equipment (NSE) as a standalone synchronisation unit.
21
Chapter 1
1.2.2.21.
Calling Line Identity (CLI) and CAMA C-DOT DSS supports CLI and CAMA functions for different applications as Local, Integrated Local cum TAX (ILT) and TAX. When working as local exchange, it is possible to programme the parameters to decide that whether <Area Code> is to be part of Calling Line Identity information or not. If it is Yes, it is possible to programme the digit length as well as sequence of digits in the area code, prefixed to the subscriber directory number. In cases where all the digits are already forwarded in response to CLI request in the form of A4 signal, the additional one or more A4 signals are responded by 0. In other words, additional digits as 0 are suffixed to complete CLI information in the network. In case of incoming terminating call when used as local exchange or incoming transit call when used as TAX, the number of digits to be requested from the preceding exchange can be programmed. Accordingly the no. of A4 signals are sent towards preceding exchange. It is also true when CAMA is set for one or more TGPs as well as in case of R2 to CCS7 interworking. It is possible to programme the CLI information in the network for any specific requirement for different applications as Local, ILT / CLT or TAX.
1.3.
NEW SOFTWARE RELEASE 2_2_1_9 (2007) New S/W Release 2_2_1_9 has been introduced to provide three new features, in addition to all the existing features, supported in previous S/W release 2_2_1_6. New features are :i) ii) iii) CENTREX GROUP implementation Special subscriber priority implementation New strategy for `ncbr & `tgbr files dumping in IOP.
Solution to all the existing problems of 2_2_1_6 and various enhancements have also been included in the new release 2_2_1_9. 1.3.1. CENTREX Groups introduced in 2_2_1_9 will have following features
22
500 CENTREX groups can be created in MBM, while only 10 CENTRAX groups are possible in SBM. Total number of Centrex Subscribers in all the Centrex groups should not exceed 5000. For SBM only '10' Centrex subscribers can be created. Only PSTN & V5.2 subscribers can become members of Centrex Groups. ISDN subscribers can not be added to Centrex groups. Centrex Feature will not work in 'RBMSA' mode.
C-DOT DSS MAX
Centrex Group members should be from the same exchange and having same area code. RSU & AN-RAX subscribers of different 'SDCA' with different Area codes can not form part of the Centrex group of main exchange. Maximum '10' Centrex Groups can be put on traffic observation simultaneously. Complete flexibility is provided to charge or not to charge the intracentrex group calls. Centrex group members will have three additional PABX features (i) Call Transfer (ii) Auto call back (iii) Abbreviated Dialling. Dialing Patterns For New Features For Centrex Members Service Automatic Call Back - Activation Automatic Call Back - Deactivation Call Transfer Usage Code HSF 1294 HSF 1295 HSF 1296 ABBR
Following are the legends used in above table. ABBR HSF Abbreviated number of called Centrex member Hook Switch Flash
New commands added for Centrex Group Features are:1. CRE-CNTRX 2. DEL-CNTRX 3. MOD-CNTRX-CHAR 4. REM-MEM-FRM-CNTRX 5. ADD-MEM-TO-CNTRX 6. DISPL-CNTRX-CHAR 7. DISPL-CNTRX-MTR 8. MOD-CNTRX-OBS
Note: Refer Chapter 6 for details of Centrex Group Data Creation/Display & maintenance commands.
23
Chapter 1
1.3.2.
Special Priority Implementation Currently in the field, for India-One Plan (or any other similar plan) implementation, the requirement is that all outgoing traffic from INDIAONE subscribers should be carried over a new TGP towards the TAX. At TAX, for that New TGP, charging data is defined for INDIA-ONE plan (Say @ Rs.1/ min), the charging CHB/Charging pulses are sent towards the originating exchange. In future, there may be some other plan, which will have the similar requirement like India-one. So a general strategy has been designed to implement some Special Sub/TGP Priorities to seize desired OG TGP for outgoing calls routing. Special Priority range is from 15 to 19.These priorities will be used internally for TGP seizure only & will not be floated over the network.(Refer Chapter 6 for feature implementation details).
1.3.3.
Strategy for Detailed Billing Records (CDR) Generation and Transfer Bharat Sanchar Nigam Limited (BSNL) is having countrywide presence with over 40 million subscriber base. BSNL has proposed to implement next generation state-of- Art Detail Billing Records (CDR) based Customer Care and Convergent Billing System. This can be achieved with deployment of Centralized Integrated Billing Systems with supporting technological and communication infrastructure. To implement this, Detail Billing Records (CDRs) are to be obtained from different type of Network elements capable of generating billable information, using centralized Mediation System. In BSNL Network , 90% of the switches are of CDOT Technology. To meet the above requirement, there is a need to generate 100% Detail Billing Records for all the completed calls. Generation of 100% Detail Billing Records is supported in the existing & New software releases of C-DOT. These Detail Billing Records need to be automatically transferred to the Billing center preferably in real time mode.( refer Chapter 7 for implementation details ).
1.3.4.
Problem Fixes in 2_2_1_9 Over 2_2_1_6(7.7) 1. 2. IOP Synchronization and Duplex working has been stabilized. Special Service routes (say 198 etc.) mapping for RSUs & AN-RAX using MOD-RBMNRM-CONFIG & CRE-ANNRM-CONFIG is working properly in all scenarios. ISDN PABX problem of wrong CLI (Always CLI of PDN) and calls of more than 12 digits failure has been solved.
3.
24
C-DOT DSS MAX
4. 5. 6.
No Dial Tone & Voice over ISND BRI subscribers in new ISTU frames has been solved by changing ITC/ICC problems. 4 digit level routes working properly for RSU subscriber in new release. When Annc. card made OOS-OPR, then on Dynamic locking/unlocking, congestion tone is given instead of PIT/FIT. This problem has been fixed. BW TGP traffic reports will now get transferred during IOP synchronization. Reversal will be extended to AN-subscriber created with line-typ=CCBCRD. Proper announcement will be fed to subscriber of C-DOT after dialling a non-existing route via ISUP trunks (earlier busy tone was given).
7. 8. 9. 1.3.5.
Enhancements in S/W Release 2_2_1_9(2.11) 1. During Creation of Subscriber data, default value of the parameter "ACC-BAR" will be IC-NOT-BRD/OG-UPTO-REG/BS12 (Earlier it was IC-NOT-BRD/OG-UPTO-LCL/BS12). In 2_2_1_9, 'BC' group has been splitted into two separate groups, i.e. 'BC' (for ncbr only) and TG (for tgbr files only). This will ensure a separate back-up of ncbr and tgbr files, as files size has increased after default CDR generation for all level '9' calls.
2.
3. Total no of TGPs in MBM has been reduced from 512 to 300, while it is same in case of SBM. 1.3.6. Enhancements & Problem Fixes in S/W release 2_2_1_9 ( 2.13) 1. 2. 3. During Subscriber data creation by cre-sub command, parameter DET-BLG will accept LCL-BLG as default value. As level 950 has been allotted for Mobile Services, calls on this rout are now allowed ( Blocked in previous release) As levels 90 & 96 have been allotted for Mobile Services, these levels will be accessible to Subscribers having ACC-BAR as OG_UPTO_REG (Earlier these levels were accessible to SUBs having OG_UPTO_LCL). CDRs for these levels will be generated by Default . Meter increment will be done in STD counters. In general , levels 90 & 96 will be treated at par with levels 91,92,93,94,95,97,98,99. Access Network Interface Status change Report will be available through CRP command displ-ood-log by option:
25
4.
Chapter 1
REP-NAME : 5.
205 ( AN - STS CHG -REP)
Meter Reading spurt on Subscriber No. having Subs_Index = 0 was observed if calls were made on any other Subscriber (in that BM) with activated call diversion. This problem has been solved.
1.3.7. 1.3.7.1.
Enhancements and Problem Fixes in S/W release 2_2_1_9 (2.16) As a requirement for implementation of Mobile Number Portability (MNP) in the Telecom Network, Charge Band Number (CHB) information is to be made available in the CDRs for Subscribers as well as TGPs. This feature has been implemented in S/W 2219(2.16). Charge Band Information in CDRs for different type of calls is explained below: 1. Intra-exchange (Local) Calls: For Local calls, system will check 'CHB' Number mapped to the 'CRG-RTN' used for changing of the Local calls. Normally crg-rtn=21 (180 sec) is used for charging of local calls. CHB=11 is associated for crg-rtn=21. Then Charge-Band=11 will be shown in Bill Record of such calls. An extra field "Charge-Band" has been included in the Output format of the command "displ-billrec". For Outgoing Calls following cases may arise :a) b) If CRG-RTN in a particular route is 'prd-lcl', then CHB number associated with this crg-rtn will be dumped in the CDR. If CRG-RTN in the route is 'prd-tax', then CHB number received from TAX (TGP on CCS7-signalling) will be dumped in the CDR. If CRG-RTN in a the route is 'prd-tax" & TGP is on MOD-R2 signalling then only metering pulses will be received. In this case an invalid CHB=255 will be dumped in the CDR. If CRG-RTN in the route is prd-tax', & TGP is on CCS7 signalling with SIG-INFO=ISUP-CRG-CHU then CHB will not be received. So an Invalid CHB=255 will be dumped in the CDR. Hence, always use option "ISUP-CRG-CHB".
2.
c)
d)
Warning! In S/W 2_2_2.16_9, all the relevant Charge Band Nos. (CHB Nos) must be mapped to the correct CRG-RTNs using "mod-chb-crg", otherwise system may go for frequent booting.
26
C-DOT DSS MAX
1.3.7.2.
New Unix 11.7 has been released which will be required wherever 146 GB hard disk is to be replaced in IOP. (However for the existing low capacity 1.2GB/2.5GB/4.5GB/9.5GB Hard disks, Unix 11.6 can also be used.) PCMs going to 'OOS-TRANS' state because of media flicks & not recovering to normal state automatically even after removal of the flicks. This problem has been solved. With new implementation, such PCMs will become 'INSFREE' automatically after 5 minutes of removal of flicks in the media. Problem of delay in 'COPY-OUT' of ED/BD/BC due to large block size of various files has been solved by implementing following: 1. Now 'trnsf' gp files (iotmsg*/iotind*) will not be part of 'ed.grp'. Backup of trans files can be taken separately by 'COPY-OUT' command for [fgp] : trnsf; History files ioh* have been removed from 'ED' group. No backup is required for this group. Commercial Bill Record files 'iocbil*' have been removed from 'BC' & 'BD' groups. These files are already available in ED group.
1.3.7.3.
1.3.7.4.
2. 3. 1.3.8. 1.3.8.1.
Enhancements & Problem Fixes in S/W Release 2_2_1_9 (2.22) Problem Fixes 1). 2). During HGP creation, PDN defined with TEN-BW getting partial ringing, Problem has been solved. The invalid digits (like * or #) dialled either in the exchange-code OR in the digits dialled after exchange-code will fail the call with numberunobtainable error. Calls not successful in case MNP is taken by IDEA subscribers. ISTU tics going oos-sus, when call dialled from ISDN PABX to IDEA mobiles. This problem is solved in this release. After MNP implementation, AM recovery noticed if LSB towards TAX not created. Also on interruption of LS towards SSTP (TDM), all Voice Ckts going to S7-bsy state & not restoring even after restoration of LS status to activated & available. The problem has been solved in this release. Sometimes error printouts regarding data file apbmss start coming on Active IOP console Terminal. Part-init to AM was the only solution. This problem has been solved.
3)
4)
5)
27
Chapter 1
1.3.8.2.
Enhancements/Changes 1) The check in the MOD-LIN-STA command for the OOS-line status is removed, so that even if the subscriber is INS the command is allowed. So now one can make a subscriber BNP-ANNC from normal without forcing the terminal OOS. In order to support the CDR based billing feature for subscribers, there is requirement to generate the CDRs for all the local calls & Centrex calls irrespective of the value ORD-BLNG, CNTX-BLNG or LCL-BLG for subscribers. Now CDR will be generated for all types of call for all subscribers by default (No administrator Control). CLIR facility removal (None of the CLIR facilities will be available). A new Error string introduced as This facility is not allowed to Registered/Deregistered. Changes in speech monitoring to display CLIP differently at Monitoring Number. MOD-SMON-LIST is changed to include one additional parameter MON-CLIP that indicated the CLIP Info (either OBSERVED or CONNECTED) associated with the Monitoring Dir. No.
2)
3)
4)
28
C-DOT DSS MAX
Chapter 2.
Software and Hardware Status

2.1. 2.1.1. 2.1.1.1. SOFTWARE STATUS Media Details Status for SBM-RAX
S. NO 1. 2 3. 4. Unix 11.7 BAC/SC2_2_1_9
MEDIA
SIZE 11890 Blocks 134756 Blocks 40097 Blocks 18133 Blocks
CPC/SC2_2_2.22_9 BMDC/SC2_2_2.10_9
2.1.1.2.
Status for MAX-L/MAX-XL

S. NO 1. 2. 3. 4. Unix 11.7 BAC/MC2_2_1_9 CPC/MC2_2_2.22_9 BMDC/MC2_2_2.10_9 MEDIA SIZE 11890 Blocks 144786 Blocks 43298 Blocks 17532 Blocks (MAX-L) 17538 Blocks (MAX-XL)
2.1.1.3.
Retrofit Utility Cartridges

S. NO 1. Retrofit Utility Cartridges EDRETRO 2219 SIZE 1153 Blocks
2.1.2.
PROM Status There are different types of PROM used in different controllers. In addition to the size of memory which is clearly identified by the PROM Type/Number,
29
Chapter 2
the speed is also one of the critical parameters. The speed of different types of PROMs, is specified below: PROM Type 27C256 27C512 27C010 27C040 200 200 120 90/100 Speed nsec nsec nsec nsec
It is advised to use the PROMs with access time as recommended. 2.1.2.1.

S. No. 1
IOP
Card Type FOR IOP-VH APC-VHC358/O-S00 U22 LVHCMON7.0 2F37 27C040 Position PROM (ID) Checksum PROM TYPE
2.1.2.2.
S. No. 1.
ADP
Card Type APC-SMC122/T-S03 FOR SBM-RAX ONLY Position U7 PROM (ID) LADP101XSC2_2_2.2_9 Checksum 83DA PROM TYPE 27C256
2.
APC-SMC122/T-S03 FOR MAX-L /MAXXL
U7
LADP101XMC2_2_2.2_9
0FE7
27C256
2.1.2.3.
S. No. 1.
Central Module in MAX-XL

Card Type APC-BPC441/O-S02 FOR 300K BHCA Position U45 U43 APC-HPC393/O-S01 FOR 800K BHCA U55 U19 PROM (ID) LAPC2XXXMC2_2_2.2_9 HAPC2XXXMC2_2_2.2_9 LAPC3XXXMC2_2_2.2_9 LMSC3XXXMC2_2_1_9 Checksum 2C27 E103 0934 2FCE PROM TYPE 27C010 27C010 27C040 27C010
2.
APC-HMS394/O-S01
30
C-DOT DSS MAX
SOFTWARE AND HARDWARE STATUS S. No. 3. Card Type APC-BPC441/O-S02 FOR 300K BHCA Position U45 U43 APC-HPC393/O-S01 FOR 800K BHCA 4. APC-CHD370/F-S01 (Used on APCNSC369/H-A01) APC-CHD370/F-S01 (Used on APCNSC369/H-A01) U55 U43 PROM (ID) LSSC2XXXMC2_2_2.2_9 HSSC2XXXMC2_2_2.2_9 LSSC3XXXMC2_2_2.2_9 LNSC1XXXC2_2_1_9 Checksum 401B 7D99 53EE 51E8 PROM TYPE 27C010 27C010 27C040 27C256
U42
HNSC1XXXC2_2_1_9
1CB5
27C256
2.1.2.4.
S. No. 1.
Central Module in MAX-L

Card Type APC-CPU019/F-S04 OR APC-CPU019/F-S05 Position U79 U82 U64 U66 PROM (ID) LAPC1XXXMC2_2_2.2_9 HAPC1XXXMC2_2_2.2_9 LAPC1XXXMC2_2_2.2_9 HAPC1XXXMC2_2_2.2_9 LMSC1XXXXC2_2_1_9 HMSC1 XXXXC2_2_1_9 LSSC1 XXXMC2_2_2.2_9 HSSC1 XXXMC2_2_2.2_9 LSSC1 XXXMC2_2_2.2_9 HSSC1 XXXMC2_2_2.2_9 Checksum F181 98F7 F181 98F7 1B9F F931 88A7 FDB9 88A7 FDB9 PROM TYPE 27C512 27C512 27C010 27C010 27C256 27C256 27C512 27C512 27C010 27C010
2.
APC-MSC014/F-S07
U66 U67
3.
APC-CPU019/F-S04 OR APC-CPU019/F-S05
U79 U82 U64 U66
2.1.2.5.
PROM Status for BM-L / BM-XL Analog Terminal Unit (ATU)
S. No. 1.
Card Type APC-TIC002/T-S08 OR APC-TIC002/F-S10
Position U56 U62 U75 U3
PROM (ID) LTIC108XXC2_2_1_9 HTIC108XXC2_2_1_9 CTIC110XXC2_2_1_9 LTTC105XXC2_2_1_9 OR LTTC106XXC2_2_1_9
Checksum B758 0270 0A14 303E D32F
PROM TYPE 27C256 27C256 27C512 27C256
2.
APC-TTC051/T-S06
31
Chapter 2 S. No. 3. Card Type APC-ANN078/T-S03 OR APC-EAC371/H-S00 OR APC-ASVA27/HS001 Position U9 U9 U18 U7 U6 PROM (ID) LANC1XXXXC2_2_1_9 LEAC1XXXXC2_2_1_9 HEAC1XXXC2_2_1_9 LASV1XXXL2_2_1_9 HASV1XXXC2_2_1_9 Checksum 9E86 00EB BAD4 8E1D DCB4 PROM TYPE 27C256 (200 ns) 29F040-PLCC 29F040-PLCC 29F040-PLCC 29F040-PLCC
Note : Two additional EPROMs are to be provided in 'ANNC' Card at U72 & U75 positions For Hindi/Eng. Annc. For other Bi-lingual Announcements. Refer Annex-C. ISDN Terminal Unit (ISTU)
S. No. 1. Card Type APC-ICC536/H-S01 Position U35 U29 2. APC-ITC535/H-S01 U3 U4 3. APC-BRL537/H-S01 U60 U50 4. APC-PRL538/F-S01 U24 U23 PROM (ID) HICC1XXXXC2_2_2.2_9 LICC1XXXXC2_2_2.2_9 HITC1XXXXC2_2_2.2_9 LITC1XXXXC2_2_2.2_9 HLCC1XXXXC2_2_1_9 LLCC1XXXXC2_2_1_9 HLCC1XXXXC2_2_1_9 LLCC1XXXXC2_2_1_9 Checksum 451E 1DEB FBAC 04A9 E2A8 0C73 E2A8 0C73 PROM Type 27C040 27C040 27C040 27C040 27C040 27C040 27C040 27C040
Signalling Unit Module (SUM) for CCS7

S. No. 1. 2. Card Type APC-TUC046/T-S03 APC-BPC441/O-S02 for SBM RAX with 32 signalling links APC-HPC393/O-S01 for SBM RAX with 64 signalling links Position U85 U68 U45 U43 U55 PROM (ID) HTUC101XXC2_2_1_9 LTUC101XXC2_2_1_9 LNPC2XXXSC2_2_2.2_9 HNPC2XXXSC2_2_2.2_9 LNPC3XXXSC2_2_2.2_9 Checksum F62F E5CC DAFE 6E38 59B9 PROM Type 27C256 27C256 27C010 27C010 27C040
32
C-DOT DSS MAX
SOFTWARE AND HARDWARE STATUS S. No. 3. Card Type APC-BPC441/O-S02 MAX-L and MAX-XL with 32 Signalling Links APC-HPC393/O-S01 in MAX-L / MAX-XL 64 Signalling Links 4. APC-SHM473/H-S01 For 32 Signalling Links with BPC APC-SHM473/H-S01 For 64 Signalling Links with HPC Position U45 U43 U55 PROM (ID) LNPC2XXXMC2_2_2.2_9 HNPC2XXXMC2_2_2.2_9 LNPC3XXXMC2_2_2.2_9 Checksum D6C8 5A3E 357E PROM Type 27C010 27C010 27C040
U17,U20 U5,U10 U17,U20 U5,U10
LPHC102XXC2_2_1_9 HPHC102XXC2_2_1_9 LPHC202XXC2_2_1_9 HPHC202XXC2_2_1_9
0306 D2A1 F5B0 2B3F
27C040 27C040 27C040 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. 1. Card Type APC-TUC046/T-S03 Position U85 U68 2. 3. APC-DTC067/T-S04 APC-DTS066/T-S04 or APC-DTS495/F-S00 U3 U19 U15 PROM (ID) HTUC101XXC2_2_1_9 LTUC101XXC2_2_1_9 LDTC101XXC2_2_1_9 LDTS101XXC2_2_1_9 LDTS101XXC2_2_1_9 Checksum F62F E5CC F25A EBEC EBEC PROM Type 27C256 27C256 27C256 27C256 27C256
Time Switch Unit (TSU)

S. No. 1. Card Type APC-MFC043/F-S06 OR APC-MFC043/F-S08 APC-MFC043/T-S04 2. APC-MSC014/F-S07 OR APC-HMS394/0-S01 3. APC-TGA077/T-S02 Position U71 U67 U63 U66 U67 U19 U14 PROM (ID) LMFC106XXC2_2_1_9 TONE PROM for CCTRX LMFC104XXC2_2_1_9 LMSC1XXXXC2_2_1_9 HMSC1XXXXC2_2_1_9 LMSC3XXXMC2_2_1_9 LTGC1XXXXC2_2_1_9 Checksum 5310 FE7F 33BF 1B9F F931 2FCE E0B5 PROM Type 27C256 27C512 27C256 27C256 27C256 27C010 27C256
33
Chapter 2 S. No. Card Type Position U45 4. APC-TSC008/F-S06 SBM/MAX-L U24 U23 APC-TSC008/F-S04 SBM/MAX-L APC-TSC008/F-S06 Only for MAX-XL U24 U23 U24 U23 APC-TSC008/F-S04 Only for MAX-XL 5. APC-TIC002/T-S08 OR APC-TIC002/F-S10 6. APC-ETS477/H-S01 For sixteen PCMs APC-RTS457/H-S02 For four PCMs U24 U23 U56 U62 U75 U9 U3 PROM (ID) LTGC1XXXXC2_2_1_9 LTSC1061XC2_2_1_9 HTSC1061XC2_2_1_9 LTSC1041XL2_2_2_9 HTSC1041XL2_2_2_9 LTSC1062XC2_2_1_9 HTSC1062XC2_2_1_9 LTSC1042XL2_2_1_9 HTSC1042XL2_2_1_9 LTIC108XXC2_2_1_9 HTIC108XXC2_2_1_9 CTIC110XXC2_2_1_9 LETS1XXXMC2_2_1_9 LRTS1XXXMC2_2_1_9 Checksum 3EAC 996A A13D 8C71 A7BD 64D4 02B4 46EC D469 B758 0270 0A14 98AD 4710 PROM Type 27C256 27C256 Note 1 27C256 Note 1 27C256 27C256 27C256 Note 1 27C256 Note 1 27C256 27C256 27C256 27C256 27C512 68HC705C9P 68HC705C9
Note : 1. In case of PROMs for TSC, it depends on the BM application and not its type. The checksum for TSC will be same for BM-L as well as BM-XL if used as SBM-RAX or as BM/RSU of MAX-L Similarly the checksum for TSC PROM will be same for BM-L as well as BM-XL if used as colocated BM or RSU BM of MAX-XL. Base Processor Unit (BPU) in BM for MAX-L/MAX-XL
S. No. 1. Card Type APC-CPU019/F-S04 Position U79 U82 APC-CPU019/F-S05 U64 U66 APC-BPC441/O-S02 FOR 300K BHCA APC-HPC393/O-S01 FOR 800K BHCA U43 U45 U55 PROM (ID) LBPC1XXXMC2_2_2.2_9 HBPC1XXXMC2_2_2.2_9 LBPC1XXXMC2_2_2.2_9 HBPC1XXXMC2_2_2.2_9 HBPC2XXXMC2_2_2.2_9 LBPC2XXXMC2_2_2.2_9 LBPC3XXXMC2_2_2.2_9 Checksum 739A D0A9 739A D0A9 7731 B12E 7DF2 PROM TYPE 27C512 27C512 27C010 27C010 27C010 27C010 27C040
34
C-DOT DSS MAX
SOFTWARE AND HARDWARE STATUS
Base Processor Unit (BPU) for SBM-RAX

S. No. 1. Card Type APC-CPU019/F-S04 Position U79 U82 APC-CPU019/F-S05 U64 U66 APC-BPC441/O-S02 U45 U43 APC-HPC343/0-S01 U55 PROM (ID) LBPC1XXXSC2_2_2.2_9 HBPC1XXXSC2_2_2.2_9 LBPC1XXXSC2_2_2.2_9 HBPC1XXXSC2_2_2.2_9 LBPC2XXXSC2_2_2.2_9 HBPC2XXXSC2_2_2.2_9 LBPC3XXXSC2_2_2.2_9 Checksum 8DE8 B944 8DE8 B944 EE2C AEE6 FDB7 PROM Type 27C512 27C512 27C010 27C010 27C010 27C010 27C040
PROM Status of V5.X Unit (VU)

S. No. 1. 2. Card Type APC-TUC046/T-S03 APC-BPC441/O-S02 for SBM RAX with 32 signalling links APC-HPC393/ O-S01 for SBM RAX with 64 signalling links 3. APC-BPC441/O-S02 MAX-L and MAX-XL with 32 Signalling Links APC-HPC393/O-S01 in MAX-L / MAXXL 64 Signalling Links 4. APC-SHM473/H-S01 For 32 Signalling Links with BPC APC-SHM473/H-S01 For 64 Signalling Links with HPC Position U85 U68 U45 U43 U55 PROM (ID) HTUC1XXXXC2_2_1_9 LTUC1XXXXC2_2_1_9 LVPC2XXXSC2_2_2.2_9 HVPC2XXXSC2_2_2.2_9 LVPC3XXXSC2_2_2.2_9 Checksum F62F E5CC C382 BACA 176C PROM Type 27C256 27C256 27C010 27C010 27C040
U45 U43 U55
LVPC2XXXMC2_2_2.2_9 HVPC2XXXMC2_2_2.2_9 LVPC3XXXMC2_2_2.2_9
BDD3 9AF3 F7AF
27C010 27C010 27C040
U17,U20 U5, U10 U17,U20 U5,U10
LPHC102XXC2_2_1_9 HPHC102XXC2_2_1_9 LPHC202XXC2_2_1_9 HPHC202XXC2_2_1_9
0306 D2A1 F5B0 2B3F
27C040 27C040 27C040 27C040
35
Chapter 2
2.2.
CHANGE OF EPROMS REQUIRED FOR S/W RELEASE 2_2_2.22_9 OVER EXISTING RELEASE 2_2_7.7_6
Deliverable S/W 2_2_7.7.6 S/W 2_2_2.11_9 X S/W 2_2_2.13_9 X } } } } } } } } } } } } } } } S/W 2_2_2.16_9 X } } } } } } } } } } } } } } }
ADC BM-XL/BM-L TICS08/S10 TUC (HTUC-U85) DTS DTC TOGC (LTGC-U14) TTC ANNC MFC S04 (U63) / S06/S08 (U71 & U67) BPC (CPU-S04/S05) BPC-S02 HPC TSC MSC/HMS ASV 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) MSC CM-XL BPC-S02 (APC & SSC) or HPC-S01 ( " ) NSC HMS ISTU ICC ITC BRL/PRL Unix BAC CPC BMDC ED/BD RETRO RGEN
X X X X x x
} } } } } } } } } } } } } }
X X
X X X
X X X
X X X
36
C-DOT DSS MAX
Chapter 3.
Software Retrofit Philosophy and PreRetrofit 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. 2. The 2_2_1_9 retrofit procedure has to be carried out over previous software releases 2_2_7.7_6. Refer chapter 4 for detailed procedure. Exchange Data Retrofit Utility Cartridge For S/W Retrofit 2219, 'ED', 'BD' and 'BC' of old S/W 2216(7.7) will be used. In S/W 2219, structure of many Data files is changing. To incorporate these changes over the existing data files of 2216, Retrofit Utility cartridge will be required. Same way billing Data files (ncbr??, tgbr??, locctr?? & stdctr?? etc) will also be retrofitted to make these compatible with new S/W 2219. Thus existing exchange data & subscriber meter Reading will remain same. Note : * It is important to inform TRA section about change in the file structure, in case, bills are being generated using some Billing Generation Package. Package will have to be upgraded. 2_2_1_9 billing file structure can be obtained from C-DOT for the upgradation of billing package. 3. In S/W Rel. 2219, maximum no. of TGPs in MBM system has been reduced to 300 (earlier it was 500). Now all the TGPs having number >300 have to be deleted and re-created with any free TGP number <300. For SBM, maximum limit has not been changed. 4. After retrofit process has been completed with one IOP, do not rush to load other IOP with new S/W deliverables of 2_2_1_9. Watch the system stability for one day. Please make sure to arrange PROMs for spare cards also.
37
5.
Chapter 3.
6.
The other IOP is to be loaded with complete S/W 2_2_1_9 and two copies of S/W deliverables, cartridges of UNIX, BASE, PATCH and BMDC are to be prepared from the master set.
3.2.
PRE-RETROFIT CHECKS All the duplex units in the system are fine, i.e., the system is able to work with either copy as active and other standby and they respond correctly to all switch maintenance commands. This should be tested for IOPs also. All simplex units (TTC, ANNC & MFCs) are fine and respond to switch maintenance commands with either of the higher duplex units as active. System alarms are working fine. All input/output devices (cartridge and floppy drives) of C-DOT IOPs are fine. This can be verified by copying out data from one IOP and copying the same in other IOP. All deliverable corresponding to old release are available at site. Latest ED/BD backups are available. Take list of the BNP-DISC NOs from active IOP. Ensure that the new PROMs for all controllers cards and SPARES are available as per card versions being used in the system. Note down characteristics of all the operator terminals created in each IOP, as these will be required to be added again after the retrofit. BP cables for BM-L, BM-XL & SUM should be available at site.
3.3.
CONTACT NOS. OF C-DOT CONTROL ROOM At Delhi : At Bangalore 011-26802815, 26802816, 26598282 Fax: 011-26598562 080-25119999 Fax: 080-25119251
Go to C-DOT Help Desk through C-DOT Helpline Portal (www.cdothelpline.ernet.in)
38
C-DOT DSS MAX
Chapter 4.
Retrofit Procedure From 2_1_7.7_6 to 2_2_1_9

4.1. PRE RETROFIT ACTIVITIES Stop all the Traffic Reports & remove all entities (Subs, TGPs, Trks, Routs, AIs etc) from any type of observations. Make sure that New S/W 2219 deliverables (Unix, BAC, CPC, BMDC), Retrofit Utility, RGEN utility cartridges & all the required EPROMS as per Chapter 2, are available at site before starting the retrofit activity. Stop executing Data base modifications from Active IOP, once Retrofit activity has started in the other IOP. If there are any TGPs having No >300, then these TGPs have to be deleted & re-created with any free TGP No <= 300 by running TGP retrofit utility. For this, prepare a list of old TGP Nos(>300) & New free TGP Nos(<=300) & TGP Names to be allocated. Preserve ED of 2216(7.7) and last one year "BC" Back-ups for records. Do mock retrofit exercise one day before the actual retrofit date as per procedure given in para 4.2.
Success of mock retrofit will ensure that actual retrofit gets completed without any problems and as per schedule. 4.2. 4.2.1. MOCK RETROFIT PROCEDURE ONE DAY BEFORE THE RETROFIT DATE Running of check.sh utility in IOP having S/W 2_2_1_6 1. Bring SBY IOP (Say IOP-0) to warm-start level using init-iop: 2, 1; command. a) In IOP-0 make directory "retro2219" in /u/admn as follows : IOP5C> mkdir /u/admn/retro2219 IOP5C> cd /u/admn/retro2219 IOP5C> pwd (Should show /u/admn/retro2219 )
39
Chapter 4
b)
Copy the Retrofit Utility 2219 in IOP-0 having S/W 2_2_1_6 by following commands: Insert Retrofit Utility 2219 cartridge in IOP-0. IOP5C> cpio -icv <$TAPE IOP5C> chmod 755 *
2.
IOP5C> check.sh This utility will verify sanity of ED files on which retrofit 2219 has to be done.In case no errors are shown, message Utility for ED files Checking Successfully over will appear at the end. In this case, proceed to carry out Mock Retrofit activity as given below in step 4.2.2. However if errors of the type (1) (3) core dump Error in getting index-info (2) (4) can not open Error in key info
are observed , the Utility will fail with message Utility for ED files Checking failed and one log file err.log will be generated. In such a case ,corrective action has to be taken for the corrupted ED files before carrying out mock retrofit. Contact C -DOT ,Delhi or Bangalore for on-line correction if possible. Once files have been corrected & check.sh utility is successfully run , proceed to carry out mock retrofit exercise. In case on-line correction is not possible, then ED cartridge has to be brought to C-DOT Office for further action. 4.2.2. Mock Retrofit Procedure 1. Bring SBY IOP (Say IOP-0) to warm-start & then to cold-start level using init-iop:2,1; and init-iop:1,1; commands. Load complete software (Unix, BAC, CPC, BMDC) of release 2_2_1_9 in it. Shutdown / reboot & set-site-id. Load Rgen 2219 Cartridge in this IOP by standard procedure. 2. a) In IOP-0 make directory "retro2219" in /u/admn as follows : IOP5C> mkdir /u/admn/retro2219 IOP5C> cd /u/admn/retro2219 IOP5C> pwd (Should show /u/admn/retro2219 ) b) Copy the Retrofit Utility cartridge and give execute permission as follows: Insert Retrofit Utility 2219 cartridge in IOP-0. IOP5C> cpio -icv <$TAPE
40
C-DOT DSS MAX
RETROFIT PROCEDURE FROM 2_1_7.7_6 TO 2_2_1_9
Various files will be copied & Total Blocks should be shown. IOP5C> chmod 3. 4. 5. 755 *
On Active IOP-1 give command <del-fgp-file:,ioh; and then take ED backup by 'Copy-out' command. In IOP-0 (having 2219 S/W) , COPY-IN the ed backup taken in step 3,with RES-OPT = OVR-REL Running of TGP mapping Utility (For MBM Exchange only) to map TGP Nos >300 to the free TGP Nos <=300 as per list prepared during pre-retrofit activities :IOP5C> cd /u/admn/retro2219 IOP5C>pwd (should show /u/admn/retro2219) IOP5C>retro_tgp.sh This utility is interactive & prompts various inputs to be given by the user. Important Inputs being: Enter Old TGP Num: Enter New TGP Num (Less than 301] : Enter New TGP Name It will show the enterd values & ask Do you want to proceed with these values Y/N ? Give Y here if the values are correct.
After modification, Utility prompts for Exit /Continue(0/1) for the next TGP Number. Once all the listed TGP Numbers have been mapped as per list, exit(0) from the utility .Watch for the message !!! TGP UTILITY OVER !!! Verify displ-tgp & displ-tgp-rout commands for the modified TGPs only after completing step 6(b). 6. On IOP-0, follow the ED retrofit procedure as mentioned below: a) IOP5C> cd IOP5C> pwd b) /u/admn/retro2219 (should show /u/admn/retro2219)
Execute the "retro_ed" for retrofitting ED files as follows: IOP5C> retro_ed
41
Chapter 4
Retrofitting messages will appear for all files to be retrofitted. There should be no errors shown. Watch for the exact message "RETROFIT UTILITY(ED) SUCCESSFULLY OVER". c) Verification of ED Retrofit : Some commands are being given here for verifying the successful execution of retrofit utility. Output of these commands Prior to Running Retrofit and After Running the Retrofit should come out to be same except new fields related to Centrex Feature/Special Priority. 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) DISPL-SUB-LIST of all BMs (Verify Special Priority & Centrex Number Field) DISPL-SUB from various BMs (Sample check for SPLPRI, Centrex No & Abbreviated No.) DISPL-COM-BILL (Sample check & verify for Centrex Counters) DISPL-TGP (Sample check for New TGP nos & names) DISPL-ALL-ROUT DISPL-ALL-FAC DISPL-HGP DISPL-ROUT-CHAR (Sample Check) DISPL-SYS-PARAM (Important System parameters) DISPL-TGP-LIST (New TGP Nos & Names) DISPL-XCOD DISPL-SMON-LIST DISPL-ALL (for PDDN, PDDI, System DIR NOs)
RGEN Utilities can also be used for verification. d) A log file "retro_ed.log" will be formed in the current directory. If Utility gets terminated "UNSUCCESSFULLY", then do not proceed to carry out Final Retrofit Exercise. Contact C-DOT Control Room for further action. Warning : Don't run "UNSUCCESSFULLY" "retro_ed" utility again if it gets terminated
42
C-DOT DSS MAX
4.3. 4.3.1.
FINAL RETROFIT PROCEDURE On the day of Retrofit, do following during day time: 1. Bring SBY IOP (Say IOP-0 ) to warm-start and then to cold-start level using init-iop:2,1 & init-iop:1,1; commands. Load complete software (Unix, BAC, CPC ,BMDC) of release 2_2_1_9 in it . Shutdown / reboot & set-site-id. Load rgen 2219 cartridge in this IOP by standard procedure. 2. a) In IOP-0 make directory "retro2219" in /u/admn as follows : IOP5C> mkdir IOP5C> cd IOP5C> pwd b) /u/admn/retro2219
/u/admn/retro2219 (Should show /u/admn/retro2219 )
Copy the Retrofit Utility cartridge and give execute permission as follows: Insert Retrofit Utility 2219 cartridge in IOP-0. IOP5C> cpio -icv <$TAPE
Various files will be copied & Total Blocks = 1152 should be shown. IOP5C> chmod 3. 755 *
In IOP-0 , preserve files iotmsg*, iotind* in a new directory "misc" & copy bcr.grp & bdr.grp by giving following commands :IOP5C> cd IOP5C> pwd IOP5C>script1 IOP5C> cd $PRCDATAP/misc (It should list 6 files of iotmsg* & iotind* ) /u/admn/retro2219 (should show /u/admn/retro2219)
IOP5C>ls ls 4.
On Active IOP-1 give command <del-fgp-file:,ioh; and then take ED backup. Take BC backup of last Two months (or current Billing Cycle) using COPY-OUT command. After this do not give any Exchange data modification or updation Commands. In IOP-0 (having 2219 S/W) , COPY-IN step 4,with RES-OPT = OVR-REL the ed backup taken in
5. 6.
IN IOP-0 ,COPY-IN BC backup as taken in Step 4 with

43
Chapter 4
RES-OPT = OVR-REL FGP = bcr {Frm date-> to date} 7. On IOP-0 , Restore earlier saved iotmsg* & iotind* files as follows: IOP5C> cd IOP5C> pwd IOP5C> script2 8. Running of TGP mapping Utility (For MBM Exchange only) to map TGP Nos >300 to the free TGP Nos <=300 as per list prepared during pre-retrofit activities. /u/admn/retro2219 ( should show /u/admn/retro2219 )
Note: This step is not required if such TGP Nos. do not exist Warning: In case such TGPs exist and this step is skipped by mistake, although system will recover, all the Trunk BMs & AM will go for frequent booting. /u/admn/retro2219 ( should show /u/admn/retro2219 )
IOP5C> cd IOP5C>pwd
IOP5C>retro_tgp.sh This utility is interactive & prompts various inputs to be given by the user. Important Inputs being: Enter Old TGP Num :
Enter New TGP Num (Less than 301] : Enter New TGP Name :
It will show entered values and ask "Do you want to proceed with these values (Y/N). Give 'Y' here, if the values are correct. After modification, Utility prompts for Exit/Continue (0/1) for the next TGP Number. Once all the listed TGP Numbers have been mapped exit from the Utility. Watch for the message !!!TGP UTILITY OVER!!! Verify "displ-tgp" & "displ-tgp-rout" commands for the modified TGPs after completing step 9. 9. On IOP-0, follow the ED retrofit procedure as mentioned below: a)
44
IOP5C> cd /u/admn/retro2219
C-DOT DSS MAX
IOP5C> pwd b)
(should show /u/admn/retro2219)
Execute the "retro_ed" for retrofitting ED files as follows: IOP5C> retro_ed Retrofitting messages will appear for all files to be retrofitted. There should be no errors shown. Watch for the exact message "RETROFIT UTILITY(ED) SUCCESSFULLY OVER".
c)
Verification of ED Retrofit : Some commands are being given here for verifying the successful execution of retrofit utility. Output of these commands Prior to Running Retrofit and After Running the Retrofit should come out to be same except new fields related to Centrex Feature/Special Priority. 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) DISPL-SUB-LIST of all BMs (Verify Special Priority & Centrex No. field) DISPL-SUB from various BMs ( Sample check for SPLPRI, Centrex No. & Abbreviated No. fields) DISPL-COM-BILL (Sample check) DISPL-TGP (Sample check for New TGP Nos. & names if any)) DISPL-ALL-ROUT DISPL-ALL-FAC DISPL-HGP DISPL-ROUT-CHAR ( Sample Check) DISPL-SYS-DIRNO DISPL-SYS-PARAM ( Important System parameters) DISPL-TGP-LIST DISPL-XCOD DISPL-SMON-LIST (If any No. on SMON observation)
DISPL-ALL (for PDDN, PDDI & System Directory No.) RGEN Utilities can also be used for verification. A log file "retro_ed.log" will be formed in the current directory.
Chapter 4
Warning : Don't failure. 10.
run
"retro_ed" utility again in case of
In Growth mode, give command <del-fgp-file:, alm; Copy-out the Retrofitted ED Back-up & lable the same as ED2219. Running of BC Retrofit Utility On IOP-0 , run the Retrofit utility retro_bc for `BC Group files (ncbr*, tgbr*, frmt* etc.) of the last billing cycle copied in Step-6 as follows: IOP5C> cd IOP5C> pwd IOP5C> retro_bc Retrofitting messages will appear for all files to be retrofitted. There should be no errors shown. Watch for the exact message "Retrofit Utility( BC) Successfully Over" . Warning: failure. Don't run retro_bc" utility again in case of /u/admn/retro2219 ( Should show /u/admn/retro2219 )
11.
A log file "retro_bc.log" will be formed in the current directory. If this offline utility gets terminated "Unsuccessfully", then intimate to C-DOT control room alongwith log file "retro_bc.log" Verification: Verify some Sub & TGP detail bill records by "DISPLBILL-REC" command. Also verify in $DUMPP, whether ncbr & tgbr files have been splitted into hourly files. i.e. files of date 7-7-2007 can be verified by following commands: IOP5C>cd $DUMPP IOP5C> ls -ls nc*070707.dat IOP5C>ls -ls tg*070707.dat (Should show 24 hourly files) (Should show 24 hourly files)
'BC' & 'TG' Backups: Copy-out the 'BC' & 'TG' backups and label as BC (2219) & TG (2219). 4.3.2. On the day of Retrofit, do following during night Hrs (after 20:00Hrs): a) From Active IOP-1, note down counters dump time of BM1 by giving commands
C-DOT DSS MAX
46
IOP5C>ls -ls *ctr00*
(to display locctr00* & stdctr00* files)
10 minutes before the Dump time, block all the Traffic towards TAX Exchanges and 'POI' directions. In case of CCS7, all PCMs having Signalling Links (LSs) can be forced OOS, while in case of MOD-R2, both OG and I/C TGPs are to be blocked. This is required to ensure that no discrepancy is observed in CDR's of POIs. After 5 minutes of Dump time, take Current Day 'bd' backup using COPY-OUT command with FGP = bd (Do not mention any dates).
After 'bd' backup, bring IOP-1 to warm start by <init_iop : 2,1; b) In IOP-0 , copy-in 'BD' Back-up taken in step a) with RES-OPT= OVR-REL FGP = bdr c) Running of BD Retrofit Utility Warning : Since BD Retrofit takes care of current day ncbr & tgbr files only, it is utmost important to finish this activity on same day before 00 Hrs. Time taken is from 1 to 3 Hrs depending upon No. of BMs.
In IOP-0, run retro_bd on Current day Billing Data files as follows: IOP5c> cd /u/admn/retro2219
IOP5c> retro_bd Retrofitting messages will appear for all files to be retrofitted. There should be no errors shown. Watch for the exact message "RETROFIT UTILITY(BD) SUCCESSFULLY OVER". 'BD' Backup: Copy-out the retrofitted 'BD' backup and label as BD (2219). A log file "retro_bd.log" will be formed in the current directory Warning : Don't run retro_bd" utility again in case of failure & utility gets terminated "Unsuccessfully" consult C-DOT Control Room for further action.
47
Chapter 4
4.3.3.
Initialization/Booting up the System with 2219 It is recommended to follow the under mention steps of Initialization/ Booting up the system with 2219: 1. 2. 3. Before power-on of AM/CM after changing the PROMs, must ensure that all co-located BMs TSUs should be switched off. For all RBMs either remove the data cables from CM end or remove the U-Link from DDF. Once AM & CM recover and ADP shows critical alarms of all BMs/RBMs, change the EPROMs of BMs one-by-one and recover them after Code/Patch/Data loading. Also for RBMs, change the EPROMs and then before switch-on the RBM, connect the data cable or put the U-Link at DDF.
4.
If the above mentioned steps are not followed and if the AM/CM recovered in new S/W version and any BMs/RBMs are remain connected and powered-on with older version frequent File Id Error message come on console terminal. As a result none of the BMs will start code loading even after changing new S/W proms. 5. 6. 7. 4.4. Displ-sys-all for all the BMs & bring 'OOS' units if any to ins-act/sby status. Verify MFC channel status by `displ-srv-status in all the BMs & bring these ins-free if found oos-sys Note down OMR of the modified numbered TGPs in Step 4.2.1.
POST-RETROFIT CHECKS The retrofit is now complete and the system can be observed for normal functioning. Following checks may be performed : a) b) c) e) f) g) Dial tone on at least one port of all the TUs. Dial tone on at least one DTMF subscriber in each BM. Line to Line calls O/G calls Proper updation of meter readings and detail bill record. Also verify that detail bill of SUBs & TGPs show proper 'CHB' Nos. Proper announcements
48
C-DOT DSS MAX
h) i) j)
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. All simplex unit are fine and respond to maintenance commands with either higher units as active. Create one Centrex Group with few members. Verify various type of calls and all the features relevant to Centrex Group members.
Observe the system stability for about 6 hours and then proceed to next setup. 4.5. RECOVERY ACTION In case the retrofit 2_2_1_9 is not successful, do following : i) ii) iii) iv) v) vi) 4.6. Bring IOP-0 to warm start level by init-iop : 2,1; command. Switch off all PSUs in all frames i.e. AM, CM, BMs and LMs. Replace EPROMs in relevant cards with previous S/W version PROMs and jack in the cards. Replace PROMs in SUM & ISTU frame also. Power on all the frames of the system Give INIT-IOP:5,1 from IOP-1 (having previous version data) to bring it INSACT and thus giving code load to system. Replace EPROMs of previous version in the left out cards.
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. Generate two sets of S/W deliverables of 2_2_1_9 using the cartridge duplication procedure listed in ANNEXURE-B. Load complete S/W in IOP-1, using one of the two sets of deliverables, prepared at the site. Bring IOP-1 inservice from IOP-0 by executing CRP commands: <put-swu-oos : iom, iop-1; <put-swu-ins : iom, iop-1; 5. 6. 7. 8. Change the EPROMs in the spare cards and test these cards. Implement password management in the IOPs if already being used. Add terminals and operators in the IOP-1 also. Load latest 'RGEN/CMD' utility in SBY IOP-1.
2. 3. 4.
49
Chapter 4
9. 4.7.
Put all the desired entities (TGPs, Routes, Subs etc.) on Traffic Observation and start the traffic reports.
PROCEDURE TO VIEW SUBSCRIBERS & TGPS DETAIL BILL RECORDS THROUGH RGEN UTILITY Before running rgen utilities 'ncbr' & 'tgbr', hourly files of nchhddmmyy.dat & tghhddmmyy.dat have to be combined to form a single day file by following procedure:IOP5X>cd $DUMPP IOP5X>cmb_ncbr Enter the date as "DD-MM-YY" & give Enter This will form a single day file as 'ncbrddmmyy'. IOP5X>rgen ncbr (To view Subscriber Detail Bill record of that day)
Similarly to get TGP detail bill records, do following: IOP5X>cmb_tgbr Enter the date as "DD-MM-YY" & give Enter This will form a single day file as 'tgbrddmmyy'. IOP5X>rgen tgbr (To view TGP Detail Bill record of that day)
Note: Commands 'cmd_ncbr' & 'cmb_tgbr' work only for single day. 4.8. TIME ZONES AND TARIFF CLASSES FOR HOLIDAY & NORMAL DAY Definition of Day Types 1 & 2 has been shown in Table 4-1, while Charge Band Number (CHB) to Pulse Rate association has been shown in Table 4.2. Table-4.1 DAY-TYP=1 (Holiday)
START TIME 0000 0700 2300 END TIME 0700 2300 2400 TARRIF CLASS 3 2 3 ROUTING INFO NOT-BARRED NOT-BARRED NOT-BARRED
DAY-TYP=2 (Normal/Working day)

START TIME 0000 END TIME 0700 TARRIF CLASS 3 ROUTING INFO NOT-BARRED
50
C-DOT DSS MAX
RETROFIT PROCEDURE FROM 2_1_7.7_6 TO 2_2_1_9 START TIME 0700 0730 2230 2300 END TIME 0730 2230 2300 2400 TARRIF CLASS 2 1 2 3 ROUTING INFO NOT-BARRED NOT-BARRED NOT-BARRED NOT-BARRED
4.9.
MODIFY DEFINITION OF DAY TYPE 1 AND 2 AS PER TABLE I, USING COMMAND MOD-TYP-DAY There is change in the definition of Day Types 1 and 2. Use command MOD-TYP-DAY to modify Day Types 1 & 2 as following:a) Mod-typ-day Day-typ = Prd-trf = execute Mod-typ-day Day-typ = Prd-trf = 1 0000-3-2 & 0700-2-2 & 2300-3-2
b)
2 0000-3-2 & 0700-2-2 & 0730-1-2 & 2230-2-2 & 2300-3-2 Table-4.2
Charge Band Number (CHB) to Pulse Rate association

Charge Band Number 0 1 11 12 20 21 27 33 34 38 39 Purpose Non-metered Unit Fee (Fixed) Local (Intra-Circle) Internet Inmarset Calls Inmarset Calls Rest of the World Sri Lanka USA, UK, CANADA Pvt Operator Basic, WLL, Mobile Intra Circle European Continent, Singapore, Thailand, Malaysia, Indonesia, Hongkong Inter-circle Basic & WLL Mobile >50KM, Intercircle all cellular Intra circle BSNL Basic & WLL Pulse Rate (Sec) --180 450/900 150msec 260 msec 4 6 10 45 7.5
41 42
30 60
51
Chapter 4 Charge Band Number Purpose >50 KM, Intra circle BSNL Mobile, Inter-circle Basic 0-50 KM Local BSNL, WLL, Intra-circle & WLL 0-50 KM, Intercircle BSNL Basic 0-50KM Pulse Rate (Sec)
43
90
Note: Verify 'CHBs' list from Leading 'TAX' exchange. 4.10. IMPLEMENTATION OF DISTINCTIVE RINGING FEATURE 1. There may be two types of PSU-I (with ringer) being used in TERMINAL UNIT. i) For PSU036/T-S16 (old PSUs) ECN (cut and straps) will be required to be done in all the PSUs. Detail can be taken from C-DOT web-site. ii) For PSU 036/A09 (New PSUs) EPROM (PSU E2D6) has to be changed in the child card, at U11 position. 2. 3. 4. IC-TGP from TAX should be made. TTAX type. Modify system parameter SPL-RNG = 1 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 5. Retrofit Procedure from S/W 2_2_1_9 (2.11) / 2_2_1_9 (2.13)/2_2_1_9 (2.16) to 2_2_1_9 (2.22)
5.1. CHANGE OF S/W DELIVERABLES IN 2_2_2.22_9 OVER 2_2_2.11_9/ 2_2_2.13_9/2_2_2.16_9
Deliverables UNIX CPC Over S/W 2_2_2.11_9 / 2_2_2.13_9/2_2_2.16_9 X
5.2. 5.2.1.
RETROFIT PROCEDURE FOR S/W 2_2_2.11_9/2_2_2.13_9/2_2_2.16_9 List of Deliverables
C-DOT
EXCHANGES
HAVING
Refer chapter 2 (para 2.1.1.) for changed block size of the CPC 5.2.2. Pre Retrofit activities 1. 2. 3. 5.2.3. Take ED,BC,TG ,BD Backups. Note down Characteristics of the icc ports & operator's accounts as these have to be created again. IOPs should be in duplex working & interchange of IOPs should work.
Procedure 1. 2. Bring Stand by IOP ( Say IOP-0) to warm start level by <init-iop:2,1; command & then to cold start level by <init-iop:1.1; command. Give reset to IOP. Load complete S/W (Unix,BAC, CPC2.22 ,BMDC) of 2_2_2.22_9 release. Shutdown, reboot & set-site-id. Load latest RGEN cartridge using standard procedure. After loading RGEN, 'CDR Transfer Utility Files' will be automatically loaded in
53
Chapter 5
/u/instalces directory. Intall "IOP-FT UTIL" by standard commands (# ./INST-IOP-FT). Also create 'cdr' operator using standard procedure. 3. Copy-in the latest ED backup in this IOP-0 having 2_2_2.22_9 S/W :VOL-NAME : edDdMm RES-OPT : : FGP 4. 5. : ed :< >
Copy-in BC & TG backups of last two months( or Billing Cycle) in IOP-0. Once slack traffic hour starts (after 22:00 Hrs),take backup without any date. `Copy-in this BD in IOP-0. Shutdown & reboot the IOP to bring it to warm-start level. latest BD
6. 7.. 8.
Bring active IOP-1 to warm-start by <init-iop:2,1; command. In IOP-0, give command <del-fgp-file: , alm;> Give <init-iop:5,1; from IOP-0 having S/W 2_2_2.22_9 .Once this IOP becomes ins-act ,give Power-on to system by <init-sys:, power-on; command. AM,CM ,all BMs & SUM will go for Code/patch/data loading. Now Give reset to VP-0 & VP-1 cards in all the VU frames, so that VUs also recover after Code/Patch loading. Once complete system has recovered ,verify displ-ood-log for RepName: 182 & confirm that all the Modules have gone for Poweron/Patch-init. Verify VUs recovery level by option Rep-Name: 202; Post Upgradation Checks The retrofit is now complete and system can be observed for normal functioning as listed below:a) b) c) d) Verify Dial tone on atleast on one port of all TUs covering DTMF subscriber also. Local calls & meter updation. O/G calls on various routes, specially routes 950x. Verify that Routes 90x & 96x are available from SUBs having ACC-BAR as OG_UPTO_REG (& not by OG_UPTO_LCL).
9.
10.
54
C-DOT DSS MAX
RETROFIT PROCEDURE FROM S/W 2_2_1_9 (2.11) / 2_2_1_9 (2.13)/2_2_1_9 (2.16) TO 2_2_1_9 (2.22)
e) f) 11.
Updation of Detail bills of SUBs & TGPs, with proper 'CHB' number. Verify mod-line-sta command working without making DIRNO as OOS-OPR. Load complete S/W 2_2_2.22_9 in IOP-1 also. Synchronize IOP-1 by standard procedure Add terminals & operators in both the IOPs Implement password management in IOPs if any. Load latest RGEN cartridge in this IOP. Install IOP-FT-UTIL by standard commands (# ./INST-IOP-FT). Create 'cdr' operator using standard procedure.
Retrofit Completing Activities a) b) c) d) e)
Warning: Ensure that all the relevant (defined in routes & 'Sub-Crg') CRG-RTNs are mapped to the corresponding CHBs, otherwise system may go for frequent booting.
55
Chapter 6.
Details of Centrex Feature Implementation

6.1. MAIN HIGHLIGHTS OF CENTREX FEATURE OFFERED IN THIS RELEASE ARE : 500 CENTREX group can be created in MBM., while only 10 CENTREX group can be created in SBM Total number of Centrex subscribers in all Centrex groups in MBM not to exceed 5000 . In SBM total no of Centrex Subs can be 10. Only PSTN & V5.X subscriber will be allowed as members of Centrex. ISDN subscribers cannot be a member of a Centrex group. Centrex Feature will not function in RBMSA mode. Centrex groups members should be in the same exchange & having same area code. Subscribers of RSU which are in different SDCAs having different area codes than main exchange can not make part of the same Centrex groups. It is possible to generate traffic statistics separately for each centrex group. However maximum number of Centrex groups that can be put under observation is 10. Flexibility exists to charge or not to charge the intra Centrex calls. Centrex group members will have three additional features 1. 2. 3. 6.2. 6.2.1. Call transfer Auto call back Abbreviated Dialling
DETAILS OF CENTREX FEATURE IMPLEMENTATION. Feature Definition The CENTREX feature is used to provide a virtual PABX for a group of subscribers. The attributes of a Centrex are shared by all its members.
C-DOT DSS MAX
56
DETAILS OF CENTREX FEATURE IMPLEMENTATION
A Centrex can have landlines PSTN subscribers of one exchange as its members. 6.2.2. In addition to other facilities provided to normal subscribers, this release provides following facilities to Centrex members Abbreviated dialing Each member of a CENTREX shall be administratively assigned an abbreviated number. The abbreviated number of a Centrex member shall be unique to that CENTREX. Members of a CENTREX can call each other by dialing the abbreviated code of the destination number. Automatic Call Back (ACB) If a Centrex member calls another Centrex member which is already in conversation (busy), then the calling member may book automatic call towards that subscriber. Whenever the called member becomes free, call will be initiated towards both the members. Call Transfer A Centrex member can transfer a call landing on it to another centrex member using this facility. In order to complete the call transfer, the former should disconnect itself after intimating the new member. 6.2.3. Following are the system limits for X2219 release. Table 1: System limits for X2219 release Entity Number of CENTREX Groups in system Total number of Centrex members in system (MBM Config.) Maximum number of CENTREX under observation 6.3. 6.3.1. CALL HANDLING STRATEGY CALLS Intra - Centrex Call On going offhook, a centrex member shall be fed a new dial tone named as Centrex Dial Tone (CDT). The CDT is having frequency of 400 Hz and is continuous. In order to make intra centrex call, a centrex member shall dial the abbreviated number of the called party. In case the called party is Limit 500 5000 10 CENTREX
FOR DIFFERENT TYPE OF
57
Chapter 6
having CLIP facility, then abbreviated number of the calling party shall be displayed in the CLI device. 6.3.2. Calls To Public Network By Centrex Members In order to provide access to public network, each CENTREX shall be having an escape code. Each CENTREX can have a different escape code. The escape code of a CENTREX will be defined during its creation. On getting CDT, a Centrex member can make call towards public network by d i a l i n g the escape code of the CENTREX, provided the subscriber as well as the CENTREX is having access barring required for the outgoing call. The calling member shall be fed normal dial tone on dialing escape code. After getting normal dial tone, a Centrex member can make calls outside the CENTREX. In case the called party is having CLIP facility, then full directory number of Centrex member shall be displayed in CLI device. 6.3.3. Calls Landing On Centrex Members From Public Network In case Centrex member is having CLIP facility, then full directory number of calling party shall be displayed in CLI device. 6.4. 6.4.1. CHANGE IN USAGE OF EXISTING FACILITIES BY CENTREX MEMBERS SIF Invocation By Centrex Members A Centrex member can invoke different Subscriber Initiated Features by dialing different SIF codes after CDT itself. While activating or using those features in which directory numbers are to be specified, a Centrex member can specify either an abbreviated number or a directory number of the public network. In case a directory number of public network is being specified, the escape code of the Centrex is to be dialed before the directory number. The facilities in which a subscriber can dial an abbreviated number of a Centrex member or a directory number of a public network are, 3 way conference, 6 way conference, drop selected party, hot line, absentee to selected number, diversion on busy to selected number and diversion on no answer to selected number. For other features, the procedure of activation, deactivation and usage is same as for normal subscribers. 6.5. 6.5.1. CHARGING AND BILLING Charging of intra-Centrex calls There shall be a provision of charging / not charging intracentrex calls of a CENTREX Group. In order to specify the charging for intra Centrex calls, a charge rate number shall be associated with every CENTREX. In case the intra Centrex calls of a CENTREX are to be charged, then a charge rate
58 C-DOT DSS MAX
number with desired initial charge, periodic charge and charge period can be associated with that CENTREX during its creation and can be modified later on. 6.5.2. 6.5.2.1. Modes of Billing Bulk Billing Separate billing counters are being maintained for intra Centrex calls. The charging counters are being stored separately for each member of the CENTREX. There shall be a provision to display the charging counters of a CENTREX also. The bulk billing reports generated by the system shall contain the counters for intra Centrex calls also. 6.5.2.2. Detailed Billing There shall be a provision to generate detailed billing records for all the calls, including intra Centrex calls, made by the members of a Centrex. 6.5.2.3. Commercial Billing Commercial billing records shall be generated for a subscriber when that subscriber is added into a CENTREX and when the subscriber is removed from a CENTREX. Also, commercial billing records shall be generated for a CENTREX on Centrex creation, deletion, modification. 6.6. TRAFFIC OBSERVATION There shall be a provision to put a CENTREX under observation. Following shall be possible when a CENTREX is put under observation. Dumping of CDRs of each call originated by members of the CENTREX under observation Dumping of CDRs of each call terminating on the members of the CENTREX under observation Periodic dumping of counters corresponding to calls originating from and calls terminating on a CENTREX Traffic counters shall be maintained for calls originated by members of a CENTREX and for calls terminating on members of a CENTREX 6.7. 6.7.1. CHANGES IN MAN-MACHINE INTERFACE Introduction Of New Commands Two new command classes "Centrex Management Update Class" and "Centrex Management Display Class" has been introduced. Two new
59
Chapter 6
commands DISPL-CNTRX-MTR and MOD- CNTRX-OBS have been introduced into billing and traffic command classes respectively. Following are the commands being introduced in the centrex management command classes. 6.7.2. Centrex Management Update Class CRE-CNTRX ADD-MEM-TO-CNTRX MOD-CNTRX-CHAR REM-MEM-FRM-CNTRX DEL-CNTRX 6.7.3. Centrex Management Display Class DISPL-CNTRX-CHAR Following are the new commands introduced in existing command classes. 6.7.4. New Billing Commands Following new billing command is being introduced. DISPL-CNTRX-MTR 6.7.5. New Traffic Commands Following new traffic command is being introduced. MOD-CNTRX-OBS 6.7.6. Description Of Parameters Parameter ABBR-NO Description This parameter describes the abbreviated numbers for the intra-Centrex calls. This accepts numeric values in the range 0 to 9999. This parameter describes the length of the abbreviated numbers for the intra-Centrex calls This accepts numeric values in the range 1 to 4. This parameter describes the maximum access barring levels allowed for the members of the centrex being created. It has 3 subfields C-DOT DSS MAX
ABBR-LEN
ACC-BARR
60
First subfield can have values INCMNG_NOT_BAR & INCMNG_BRRD. Second subfield OG_UPTO_LCL, can have values OG_UPTO_10X,
OG_UPTO_REG, OG_UPTO_NAT, OG_UPTO_INT. Third subfield can have values ALL_BS, BS12 and BS3. Sets and ranges are not allowed. ADD-ABBR This parameter describes the identity of Centrex member which additionally has to be put under observation. This will accept two subfields Centrex id and abbreviated number. First subfield shall accept numeric values between 1 to 500. Second subfield shall accept numeric values between 0to 9999. This parameter accepts set of values. ADD-CTRX This parameter describes the Centrex number of the Centrex which additionally has to be put under observation. All the members of this CENTREX shall be put under observation. It shall accept numeric values between 1 to 500. This parameter accepts sets and ranges of values. ATND-NUM CENTREX. CALL-STA This parameter describes the attendant position for the This accepts numeric values in the range 0 to 9999. This parameter describes the call status of the CENTREX. This parameter accepts alphanumeric values. It shall accept values NRM-LIN, BNP-ANNC and BNPDISC. This parameter describes the type of CDR which are to be displayed via DISPL-CDR command. This parameter accepts alphanumeric values CLLNG, CLLD, DIV and SPLFTY. This parameter accepts set of values. This parameter describes the commercial billing record type. This parameter accepts alphanumeric values. The possible values of this parameter are SUB, TGP and CTRX
CDR-TYP
COM-TYP
61
Chapter 6
CTRX-NUM
This parameter describes the centrex number to be created in the exchange. This parameter accepts the numeric values in the range 1 to 500. Sets & ranges not allowed. This instance is used in CRE-CNTRX, DEL- CNTRX, DISPL-CNTRX-CHAR and MOD-CNTRX- CHAR. In first instance, this parameter describes the centrex name to be created in the exchange. This parameter accepts the alphanumeric values of length 10. In second instance, this parameter describes the centrex name. This parameter accepts the alphanumeric values. Default value is ALL. In case its value is NONE, the command shows the list of the subscribers which are not member of any centrex. This instance is used for DISPLSUB-LIST. This parameter describes the charge rate number for the intra-centrex calls for the created centrex. This parameter accepts numeric values in the range 0 to 127. This parameter shall accept alphanumeric values. It shall accept value OBS-ORG and OBS-TRM. This parameter describes the identity of centrex member. This will accept two subfields Centrex number and abbreviated number. First subfield shall accept numeric values between 1 to 500. Second subfield shall accept numeric values between 0 to 9999. This parameter accepts set of values.
CTRX-NAM
CTRX-NAM
CRG-RTN
CTRX-OBS CTX-ABBR
DEL-ABBR
This parameter describes the identity of centrex member which has to be removed from observation. This will accept two subfields centrex number and abbreviated number. First subfield shall accept numeric values between 1 to 500. Second subfield shall accept numeric values between 0 to 9999. This parameter accepts set of values.
62
C-DOT DSS MAX
DEL-CTRX
This parameter describes the centrex number of the CENTREX which has to be removed from observation. All the members of this CENTREX shall be removed from observation. This parameter shall accept numeric value in the range 1 to 500. This parameter accepts sets and ranges of values. This parameter describes whether all entities are to be removed from observation. This parameter accepts alphanumeric values. Possible values are YES,NO. This parameter describes the detailed billing-type. It can accept the values ORD-BLG, LCL-BLG, CTRX-BLG. This parameter describes the directory number & the corresponding abbreviated number. It consists of two subfields separated by a -. Possible values of DIRNO : 200 to 8999999 Possible values of ABBRNO : Numeric values in range 2 to 9999 This parameter accepts set of values.
DEL-ALL
BLG-TYP DIR-ABBR
ESC-CODE
This parameter describes the escape code for the CENTREX. This parameter accepts numeric values of length 1, in the range 0 to 9. This parameter is optional with default value 0. This parameter describes the Observation Period for which CENTREX has to be put under observation. This parameter describes the originating facilities attached with the CENTREX being created. It can accept a set of alphanumeric values. It shall accept the values NO-ORG and AUTO-CBAK. This parameter describes the revenue type. It accepts alphanumeric values. The possible values of this parameter are SUBS, TAX and ILT. This parameter describes the Stop Date for putting CENTREX under observation. It has three subfields separated by -. First subfield specifies the day of month and accepts numeric values between 1 to 31.
OBS-PRD ORG-CFAC
REV-TYPE
STP-DTE
63
Chapter 6
Second subfield specifies the month and accepts numeric values between 1 to 12. Third subfield specifies the year and accepts numeric values between 1970 to 2036. The default value of this parameter is NONE. STP-TME This parameter describes the Stop Time for putting CENTREX under observation. It has 2 subfields separated by :. First subfield specifies the hour and accepts numeric values between 0 to 23. Second subfield specifies the minute and accept numeric values between 0 to 59. The default value of this parameter is NONE. TRM-CFAC This parameter describes the terminating facilities attached with the CENTREX being created. It can accept a set of alphanumeric values. It will accept the values NOTRM and of CALL-TRNSFR.
6.8. 6.8.1.
DETAILED DESCRIPTION OF NEW COMMANDS CRE-CNTRX This command shall be used to create a new CENTREX having characteristics given in the input fields. Input form CRE-CNTRX CTRX-NUM CTRX-NAM [ESC-CODE] ABBR-LEN [BLG-TYP] [MTRG-CLS] [CRG-RTN] [ATND-NUM] CREATE A NEW CENTREX : : : : : : : : NONE ORD-BLG NRM-MTR 0
64
C-DOT DSS MAX
[ORG-CFAC] [TRM-CFAC] [ACC-BARR] DIR-ABBR
: : : :
NO-ORG NO-TRM INCMNG_NOT_BAR-OG_UPTO_10X-ALL_BS
Validation and Remarks 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. This command shall be allowed in ONLINE mode only, as is done in hunt group management class. The Centrex with the given CTRX-NUM should not be already created in the system. The Centrex with the given CTRX-NAM should not be already created in the system. The Centrex name CTRX-NAM should have alphanumeric characters that should not start or end with - . The ESC-CODE shall not be 1. Every directory number in the list of DIR-ABBR should be made OOSOPR before making it a member of the CENTREX. Each of the Directory number in the DIR-ABBR list shall be a subscriber of self-exchange. Any of the Directory number in the DIR-ABBR list shall not be a frozen number. Any of the Directory number in the DIR-ABBR list shall not be a system directory number. Each of the Directory number in the DIR-ABBR shall be an ordinary subscriber, a PDN number or a member directory number. Any of the Directory number in the DIR-ABBR shall not belong to any other CENTREX. Either directory number or the abbreviated number or both in the combination of every DIR-ABBR should not be repeated. None of the abbreviated numbers in DIR-ABBR should start with the ESC-CODE digit. Length of the abbreviated number in the DIR-ABBR should be of ABBR-LEN.
65
Chapter 6
15.
If the Directory number in the DIR-ABBR is a PDN, then all the member directory numbers of the PDN should be present in the set of entries for DIR-ABBR. If MTRG-CLS is NRM-MTR, then the CRG-RTN should be existing in the system. ATND-NUM shall be same as the abbreviated number given in one of the entry of DIR-ABBR. The system limits for originating and terminating facilities shall not exceed the limit. Number of Centrex in the system shall not exceed the maximum limit. Number of members in the new CENTREX being created should not exceed the total maximum limit for Centrex members. The billing counters of a Centrex shall get initialized to zero at the time of its creation. Commercial billing records will be added for the CENTREX as well as the members being added. In the output report, the DIR TYPE field shown along with directory number shall indicate NORMAL DIRNO or PDN.
16. 17. 18. 19. 20. 21. 22. 23.
Output Report CREATE CENTREX REPORT CENTREX NUMBER CENTREX NAME BILLING TYPE ESCAPE CODE ABBRIVIATED DIGIT LENGTH OF MEMBER CHARGE RATE NUMBER ACCESS BARRING FACILITY ORIGINATING FACILITY TERMINATING METERING CLASS ATTENDEN TNUMBER CTRX COUNTERS
66
= = = = = = = = = = = =
C-DOT DSS MAX
LOCAL COUNTERS STD COUNTERS STD CALLS ISD COUNTERS ISD CALLS DIRNO [ ABBREVIATED NO
= = = = = DIR-TYPE
] 6.8.2. ADD-MEM-TO-CNTRX This command is used to add members to an existing CENTREX. Input form ADD-MEM-TO-CNTRX [CTRX-NUM] [CTRX-NAM] DIR-ABBR Validation and Remarks : 1. 2. 3. 4. 5. 6. 7. 8. This command shall be allowed in ONLINE mode only. Both CTRX-NUM and CTRX-NAM should not be non-default Both CTRX-NUM and CTRX-NAM should not be default. If CTRX-NUM is non-default, then the Centrex with the given CTRX-NUM should be already created in the system. If CTRX-NAM is non-default, then the Centrex with the given CTRX-NAM should be already created in the system. Each of the Directory number in the DIR-ABBR list shall be a subscriber of self-exchange. Any of the Directory number in the DIR-ABBR list shall not be a system directory number. Any of the Directory number in the DIR-ABBR list shall not be a frozen number.
67
ADD MEMBER TO CENTREX : NONE : NONE :
Chapter 6
9. 10. 11. 12. 13. 14.
Each of the Directory number in the DIR-ABBR list shall be an ordinary subscriber, a PDN number or a member directory number. None of the Directory number in the DIR-ABBR list shall belong to any CENTREX. Either the directory number or the abbreviated number or both in the combination for every DIR-ABBR should not be repeated. None of the abbreviated numbers in DIR-ABBR should start with the ESC-CODE digit. Length of the abbreviated number in the DIR-ABBR should be of ABBR-LEN. If the Directory number in the DIR-ABBR is a PDN, then all the member directory number of the PDN should either be present in the set of entries for DIR-ABBR or should be already a member of this CENTREX. Number of members in the new Centrex being created should not exceed the total maximum limit for Centrex members. Every directory number in the list of DIR-ABBR should be made OOSOPR before making it a member of the new Centrex being created. Commercial billing records will be added for the centrex and for the members being added to the CENTREX.
15. 16. 17.
Output Report ADD MEMBER TO CENTREX REPORT CENTREX NUMBER CENTREX NAME DIRNO [ = = ABBREVIATED NO DIR-TYPE
] 6.8.3. REM-MEM-FRM-CNTRX This command shall be used to delete existing member(s) from a CENTREX. Input form REM-MEM-FRM-CNTRX REMOVE MEMBER FROM CENTREX
68
C-DOT DSS MAX
[CTRX-NUM] [CTRX-NAM] ABBRNO
:NONE :NONE :
Validation and Remarks :
1. 2. 3. 4. 5. 6. 7. 8.
This command shall be allowed in ONLINE mode only. Both CTRX-NUM and CTRX-NAM should not be non-default Both CTRX-NUM and CTRX-NAM should not be default. If CTRX-NUM is non default, the Centrex with the given CTRXNUM should be already created in the system. If CTRX-NAM is non default, the centrex with the given CTRX-NAM should be already created in the system. ABBRNO shall not be repeated in the input. Each ABBRNO shall be a member of the CENTREX. If the Directory number corresponding to the ABBRNO is a member directory number of a PDN, then either the PDN should be specified in ABBRNO or the PDN should not be a member of the CENTREX. The directory number corresponding to the ABBRNO should be made OOS-OPR before deleting it from CENTREX. ATND-NUM of the CENTREX can not be deleted by this command. All the members of a CENTREX can not be deleted by this command.
9. 10. 11.
Output Report REMOVE MEMBER FROM CENTREX REPORT CENTREX NUMBER CENTREX NAME DIRNO [ = = ABBREVIATED NO DIR-TYPE
69
Chapter 6
6.8.4.
MOD-CNTRX-CHAR This command shall be used to modify the characteristics of an existing CENTREX. Input form MOD-CNTRX-CHAR CTRX-NUM [ESC-CODE] [DET-BLG] [CALL-STA] [CRG-RTN] [ATND-NUM] [ORG-CFAC] [TRM-CFAC] MODIFY CHARACTERISTICS OF CENTREX : : : : : : : :
Validation and Remarks
1. 2. 3. 4. 5. 6. 7. 8.
ESC-CODE shall not be 1. The CENTREX given in CTRX-NUM should be existing in the system. The ESC-CODE should not be same as the first digit of any member of the CENTREX. If MTRG-CLS is NRM-MTR, then CRG-RTN shall be existing in the system. If the existing CALL-STA of the CENTREX is NRM-LIN, then it can not be modified to BNP-DISC. If the existing CALL-STA of the centrex is BNP-DISC, then it can not be modified to BNP-ANNC. ATND-NUM shall be a member of the CENTREX. The system limits for originating and terminating facilities shall not exceed the limit.
70
C-DOT DSS MAX
Output Report MODIFY CENTREX CHARACTERISTICS REPORT CENTREX NUMBER CENTREX NAME ESCAPE CODE BILLING TYPE MODIFY CENTREX METERING CLASS CHARGERATENUMBER ATTENDENTNUMBER FACILITY ORIGINATING FACILITY TERMINATING ACCESS BARRING A.2.1.5 DEL-CNTRX This command is used to delete an existing CENTREX. INPUT FORM DEL-CNTRX [CTRX-NAM] [CTRX-NUM] DELETE EXISTING CENTREX : : = = = = CHARACTERISTICS REPORT = = = = = =
Validation and Remarks 1. 2. 3. 4. 5. 6. This command shall be allowed in ONLINE mode only. Both CTRX-NUM and CTRX-NAM shall not be default. Both CTRX-NUM and CTRX-NAM shall not be non-default. If CTRX-NUM is non-default then CENTREX with the given CTRX-NUM should be already created in the system. If CTRX-NAM is given as non-default then the CENTREX with the given CTRX-NAM should be already created in the system. The CENTREX shall not be under observation.
71
Chapter 6
7.
All the members of the CENTREX shall be made OOS-OPR prior to this command.
Output Report DELETE CENTREX REPORT CENTREX NUMBER CENTREX NAME CTRX COUNTERS LOCAL COUNTERS STD COUNTERS STD CALLS ISD COUNTERS ISD CALLS 6.8.5. DISPL-CNTRX-CHAR Input form DISPL-CNTRX-CHAR DISPLAY CENTREX CHARACTERSTICS [CTRX-NUM] [CTRX-NAM] Validation and Remarks 1. If CTRX-NUM and CTRX-NAM is given as default i.e ALL, then the output report will be different i.e it will show only the CTRX-NUMs and the number of members in them in tabular form. If CTRX-NUM is non-default then CENTREX with the given CTRX-NUM should be already created in the system. If CTRX-NAM is given as non-default then the CENTREX with the given CTRX-NAM should be already created in the system. : : ALL ALL = = = = = = = =
2. 3.
Output Report 1. If input entries are default i.e. ALL DISPLAY CENTREX REPORT TOTAL NO OF CENTREX TOTAL NO OF CENTREX MEMBERS
72 C-DOT DSS MAX
CENTREX NUMBER NO. OF CENTREX MEMBERS 2. If input entries are non-default.
DISPLAY CENTREX CHARACTERISTICS REPORT CENTREX NUMBER CENTREX NAME NO OF MEMBERS = = = =
ABBREVIATED DIGIT LENGTH OF MEMBER ESCAPE CODE BILLING TYPE METERING CLASS CHARGE RATE NUMBER ATTENDENT NUMBER FACILITY ORIGINATING FACILITY TERMINATING ACCESS BARRING = = = = = = = DIR-TYPE
MEMBER-DIRNO ABBREVIATED NO [
] 6.8.6. MOD-CNTRX-OBS This command shall be used to put remove a Centrex from observation. Input form: MOD-CNTRX-OBS [ADD-CTRX] [DEL-CTRX] [DEL-ALL] : : : TO MODIFY CENTREX OBSERVATION a Centrex under observation or to
73
Chapter 6
CTRX-OBS [OBS-PRD] [STP-DTE] [STP-TME]
: : : :
Validation and Remarks 1. 2. 3. 4. If DEL-ALL is YES, then ADD-CTRX and DEL-CTRX shall be default. If DEL-ALL is YES, then at least one Centrex should be under observation. In the STP-DTE parameter, the number of days in the month shall not exceed the maximum number of days in that month. In the STP-DTE parameter, if the month subfield is 2 (i.e. FEB) and if the year subfield corresponds to a leap year, then the number of days subfield shall contain value 29. STP-DTE should not be less than Current Date. If STP-DTE is equal to Current-Date, then STP-TME should not be less than the Current- Time. Both OBS-PRD and STP-DTE parameters should not be non-default. Both OBS-PRD and STP-TME parameters should not be non-default. If DEL-ALL is YES, then none of STP-DTE, STP-TME or OBSPRD should be non-default. Minimum possible value of Observation Period is 15 minute. The centrex (given in ADD-CTRX) to be put under observation should have been created. The centrex (given in ADD-CTRX) to be put under observation should not be already under observation. The centrex (given in DEL-CTRX) to be removed from observation should have been created. The centrex (given in DEL-CTRX) to be removed from observation should be already under observation. Number of centrex to be added under observation in the system shall not exceed the maximum limit.
5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.
74
C-DOT DSS MAX
OUTPUT REPORT MODIFY CENTREX OBSERVATION REPORT CENTREX ADDED CENTREX DELETED OBSERVATION TYPE OBSERVATION PERIOD OLD STOP DATE OLD STOP TIME NEW STOP DATE NEW STOP TIME 6.8.7. DISPL-CNTRX-MTR Input form DISPL-CNTRX-MTR information. [CTRX-NUM] [CTRX-NAM] Display : : Centrex group latest meter = = = = = = = =
Validation and Remarks 1. 2. 3. 4. 5. Both CTRX-NUM and CTRX-NAM shall not be default Both CTRX-NUM and CTRX-NAM shall not be non-default. If CTRX-NUM is non-default, then the centrex specified by CTRXNUM shall have been created in the system. If CTRX-NAM is non-default, then the centrex specified by CTRXNAM shall have been created in the system. Cumulative billing counters for the specified centrex are displayed in the output report.
Output Report DISPLAY CENTREX's LATEST METER INFORMATION Centrex Number =
75
Chapter 6
Centrex Name Centrex counter Local Counter STD Counter STD calls ISD counter ISD calls Bulk Counter 6.9. 6.9.1.
= = = = = = = =
ENHANCEMENTS TO EXISTING COMMANDS DEL-SUB Delete an existing subscriber line [Dir no.] : [TEN ] : Mode :
Validation and Remarks 1. 6.9.2. If the subscriber specified by DIRNO or TEN parameter is a member of a centrex, then the subscriber can not be deleted by this command.
DISPL-SUB Display subscriber related data [Dir no.] : [TEN ] : A new field is to be shown in the output report. Output Report DISPLAY SUBSCRIBER DIRECTORY NUMBER TERMINAL EQUIPMENT NO SERVICE GROUP NO CENTREX NUMBER ABBREVIATED NUMBER REPORT
76
C-DOT DSS MAX
6.9.3.
DISPL-SUB-LIST Input Form DISPL-SUB-LIST DISPLAY SUBSCRIBER LIST BM-NO [LST-REQ] ... ... ALL ALL NO
[MISC-STA] [CTRX-NUM]
Validation and Remarks 1. If the value in the CTRX-NUM parameter is given as default i.e `ALL, then the output will show the directory numbers irrespective of their Centrex numbers, but if the same is given as 0, then the output report will display those subscribers whose attributes meet the other criteria specified in the input and which are not member of any Centrex. If CTRX-NUM is non-default and is non-zero, then it should have been created in the system.
2.
77
Chapter 6
OUTPUT REPORT DISPLAY SUBSCRIBER STATISTICS REPORT : : : TERMINAL EQUIPMENT NO TEN TYPE
BASE MODULE NUMBER BASIC SERVICES CENTREX NUMBER DIRECTORY NUMBER 6.9.4. DEL-HGP Delete a hunt group Pri dir Mode : :
Validation and Remarks 1. 6.9.5. If the PDN being deleted is a member of a Centrex, then it can not be deleted.
DISPL-HGP Display a hunt group information PRI dir :OUTPUT REPORT
DISPLAY
HUNT/DDI GROUP
REPORT
PRIMARY DIRECTORY NUMBER GROUP TYPE ... ...
B-CHANNEL SELECTION MECHANISM CENTREX NUMBER ABBREVIATED NUMBER 6.9.6. DISPL-NUM-NAME - Display number to name mapping [ENT-TYPE ] [ENT-NUM ] [ENT-NAME ]
78
C-DOT DSS MAX
The ENT-TYPE parameter of this command shall support an additional value CTRX. This value shall be used to display the number to name mapping of all the Centrex created in the system. OUTPUT FORM ENTITY TYPE ENTITY NUMBER CENTREX ENTITY NAME
-----------------------------------------------------------------------------------------------------------1 25 6.9.7. DISPL-SUB-MTR Input Form ONE TWENTYFIVE
DISPL-SUB-MTR INFO. [DIRNO] [TEN] [CTX-ABBR]
DISPLAY : : :
SUBSCRIBER'S
LATEST
METER
Validation and Remarks 1. 2. 3. Only one parameter DIRNO, TEN, CTX-ABBR shall be non-default, other two should be default. If CTX-ABBR is non-default, then the Cent r ex specified in this parameter shall have been created in the system. If CTX-ABBR is non-default, then the abbreviated number specified shall have been a member of the Centrex specified.
Output Report Output Report for Ordinary Subscriber Display Subscriber's Latest Meter Information Directory Number =
79
Chapter 6
Terminal Equipment No = Display Subscriber's Latest Meter Information Directory Number Type Centrex Number Centrex Name Abbreviated No Centrex counter Local Counter STD Counter STD calls SD counter SD calls Bulk counter Output report for PDN Display Subscribers Latest Meter Information Centrex Number = Centrex Name = DIRNO CTX-CTR LOC-CTR STDCTR STD-CALL ISD-CTR ISD-CALL If a DIR-NO or a PDN is part of any CTRX-NUM, then there shall be an additional counter called CTX-CNTR, and BULK-CNTR shall be a total of all the counters including the CTRX- CNTR. 6.9.8. DISPL-BILL-REC Input Form DISPL-BILL-REC DISPLAY BILLING TRUNK RECORD GROUP/ OF A SUBSCRIBER/ GROUP : : : : :
C-DOT DSS MAX
= = = = = = = = = = =
CNTRX
FDATE [TDATE] FRM-TIME [TO-TIME] DBLG-TYP

80
[CHG-THRS] [DIR-DGTS] [TGP-NUM] [CTX-ABBR]
:1 : : ALL : ALL
Validation and Remarks 1. 2. 3. 4. 5. One and only one of the input parameters DIR-DGTS, TGP-NUM, CTRX-NUM and ABBR- NUM shall be non-default. If DBLG-TYP is SUB, then TGP-NUM shall be default. If DBLG-TYP is SUB then both DIR-DGTS and CTRX-ABBR shall not be default If DBLG-TYP is SUB, then both DIR-DGTS and CTRX-ABBR shall not be non-default. If second subfield of CTX-ABBR is default, then output report will show billing records of all the members of the Centrex specified by first subfield. If both subfield of CTX-ABBR parameter are non-default, then output report will show the billing records of the particular Centrex member specified by CTX-ABBR parameter. If DBLG-TYP is TGP then DIR-DGTS, CTRX-NUM and ABBR-NUM should be default.
6.
7.
Output Report DISPLAY BILLING RECORD REPORT Directory Number = Centrex Number = =
Abbreviated Number
Normal Call Billing Record [----------------------------------------------------------------------------------------------DATE TIME CALLED PARTY hh:mm:ss ] -----------------------------------------------------------------------------------------------mm:ss CHG-DURN CHG-UNITS BS
81
Chapter 6
Diverted Calls Billing Record [---------------------------------------------------------------------------------------------DATE TIME CALLED PARTY hh:mm:ss ] ---------------------------------------------------------------------------------------------Special Services Billing Record [---------------------------------------------------------------------------------------------DATE TIME hh:mm:ss ] ----------------------------------------------------------------------------------------------6.9.9. DISPL-XCHG-MTR Display Exchange meter FRM-DATE : TO DATE : [REV-TYPE]: Output Report There is no change in output report in case of REV-TYPE as TAX. In case of SUBS and ILT, the output form shall display Centrex Counter, if it is NON-ZERO. Display Exchange Meter Output Report START DATE END DATE REVENUE TYPE CENTRX COUNTER LOCAL COUNTER : : : : : DIALLED DIGITS FAC-TYP CHG-UNITS mm:ss CHG-DURN CHG-UNITS BS
Display Exchange Meter Output Report

82 C-DOT DSS MAX
STD COUNTER ISD COUNTER
: :
TOTAL REVENUE : 6.9.10. FMT-BLG-CNTR FMT-TYPE : The FMT-TYPE parameter of this command shall support one more value CNTRX which shall be used to format the billing counters of the Centrex created in the system. 6.9.11. REPORT-BILL-CNTRS Generate Billing counter request This command generates the report file in text format from formatted binary file. Input Form REPORT-BILL-CNTRS REP-TYP [DIRNO] [TGP-NUM] [TGP-NAME] [CTRX-NUM] [CTRX-NAM] : : : : : :
OUTPUT REPORT The layout of the report for subscriber is as follows : DIR no. CTRXCNTR LOCCNTR STD-CNTR STD= CALL ISD-CNTR ISD-CALL
83
Chapter 6
The layout of report for Centrex is as follows : CTRXNUM CTRXNAM CTRXCNTR LOCCNTR STDCNTR STDCALL ISD-CNTR ISDCALL
Validation and Remarks 1) 2) 3) 6.9.12. If REP-TYP is SUB, one and only one of CTRX-NUM, CTRX-NAM or DIRNO is to be specified. If CTRX-NUM is non-default, then it shall have been created in the system. If CTRX-NAM is non-default, then it shall have been created in the system.
DISPL-COM-BILL Input Form: DISPL-COM-BILL FDATE [TDATE] COM-TYP [DIRNO] [TGP-NAME] [CTRX-NUM] [CTRX-NAME] : : : : : : : DISPLAY COMMERCIAL BILLING RECORD
Validation and Remarks 1. 2. All DIRNO, TGP-NUM, TGP-NAME, CTRX-NUM & CTRX-NAME All cannot be simultaneously DEFAULT or NON-DEFAULT. If COM-TYP is CTRX then DIRNO, TGP-NUM & TGP-NAME should be default and CTRX-NUM & CTRX-NAME both should not be default.
OUTPUT REPORT Display Centrex Commercial Billing Record DATE TIME USER NAME
84 C-DOT DSS MAX
OPERATION TYPE OPERATION MODE CNTRX NUM CNTRX NAME NO OF MEMBERS IN CENTREX FACILITY ORIGINATING FACILITY TERMINATING OLD BILLING TYPE NEW BILLING TYPE OLD LINE STATUS NEW LINE STATUS OLD ACCESS BAR NEW ACCESS BAR OLD CHARGE RATE NUMBER NEW CHARGE RATE NUMBER CENTREX COUNTER LOCAL CNTR STD COUNTER STD CALLS ISD COUNTER ISD CALLS BULK COUNTER 6.9.13. DISPL-TRF-RPT This command is used to display traffic report depending upon the type of report mentioned by operator. The RPT-ID parameter of this command shall accept a new value CTRXREP for displaying centrex traffic reports. Output Report: PERIODIC REPORT ON CENTREX TRAFFIC
Chapter 6
DATE OBS DUR MODULE
: : : TRAFFIC
CENTREX ORIGINATING-CENTREX TERMINATING INFORMATION Total Intra Centrex call attempts Successful call attempts(%) Completed call attempts(%) Success rate (%)
CENTREX ORIGINATING-OUTGOING TRAFFIC INFORMATION Total Centrex originated call attempts towards public network Successful call attempts (%) Completed call attempts (%) Success rate (%) INCOMING-CENTREX TERMINATING TRAFFIC INFORMATION Total call attempts from public network to Centrex Successful call attempts(%) Completed call attempts(%) Success rate (%) 6.9.14. DISPL-TRF-OBS This command is used to display active reports, periodicity & output options. Usually this command is used to check whether the desired traffic report is active or not. Input Form For Centrex traffic observation type , a new value given against the field OBS-TYP. Output Form i) For OBS-TYP=REPORT, following would be output report if Centrex has already been put under observation. "CTRX" has to be
86
C-DOT DSS MAX
DISPLAY TRAFFIC OBSERVATION REPORT OBSERVATION TYPE =REPORT REPORT TYPE CENTREX ii) For OBS-TYP=CTRX, following would be output report DISPLAY TRAFFIC OBSERVATION REPORT OBSERVATION TYPE = CENTREX OBSERVATION CENTREX NUMBER(s)= OBSERVATION TYPE= STOP DATE FOR TRAFFIC OBSERVATION= STOP TIME FOR TRAFFIC OBSERVATION= 6.9.15. DISPL-CDR This command shall be used to display Call Detail Records of specific type for a specific period for a particular Centrex subscriber. Input Form DISPL-CDR [DIRNO] [CTX-ABBR] CDR-TYP FRM-DATE TO-DATE FRM-TIME TO-TIME : : : : : : : TO DISPLAY CALL DETAIL RECORD UNIT PERIODICITY OUTPUT OPTION
Validation and Remarks 1. 2. 3. 4. 5. Both DIRNO and CTX-ABBR shall not be default. Both DIRNO and CTX-ABBR shall not be non-default. If DIRNO is non-default, then it should not be a Centrex member. The Centrex given in the CTX-ABBR should be already created in the system. Abbreviated number given in CTX-ABBR shall belong to Centrex given in CTX-ABBR.
87
Chapter 6
OUTPUT REPORT i) FOR CALLING TYPE CDR CALL DETAIL RECORD TYPE : CLLNG CALLING SUBSCRIBER DETAILS CENTREX NUMBER ABBREVIATED NUMBER .............. ............. CALLED SUBSCRIBER DETAILS CENTREX NUMBER ........... ............ ii) FOR CALLED TYPE CDR CALL DETAIL RECORD TYPE: CALLED CALLED SUBSCRIBER DETAILS CENTREX NUMBER ABBREVIATED NUMBER .................................. ................................. CALLING SUBSCRIBER DETAILS CENTREX NUMBER ................................ ................................ ................................ 6.9.16. START-TRF-RPT This command is used to start traffic reports For Centrex traffic, a new value "CTRX-REP" has to be given against the field RPT-TYP. Output Form START TRAFFIC REPORT
REPORT TYPE CENTREX

88
UNIT
PERIODICITY
C-DOT DSS MAX
6.9.17.
MOD-RPT-PERDTY This command is used to modify the periodicity of traffic report(s). For Centrex traffic report, a new value against the field RPT- TYP. "CTRX-REP" has to be given
6.9.18.
MOD-OUT-OPT This command is used to modify the output option of traffic report(s). For Centrex traffic report, a new value against the field RPT- TYP. "CTRX-REP" has to be given
6.9.19.
STOP-TRF-RPT This command is used to deactivate(stop) one or more active traffic reports. For Centrex traffic report, a new value against the field RPT- TYP. "CTRX-REP" has to be given
6.9.20.
MOD-SUB-OBS Modify subscriber observation ADD-DIR : DEL-DIR : DEL-ALL : SUB-OBS : OBS-PTD : STP-DTE : STP-TIM : This command is used to put individual subscriber under observation or remove a particular subscriber from observation for any type of calls (originating, terminating, malicious). OUTPUT FORM MODIFY SUBSCRIBER OBSERVATION REPORT OBSERVATION TYPE = SUBSCRIBERS <OBS-TYPE (e.g ORIG)>
SUBSCRIBERS ADDED TO THE LIST ADDED-DIRNO [
89
Chapter 6
Directory Number Centrex Number
Abbreviated Number
SUBSCRIBERS DELETED FROM THE LIST DELETED-DIRNO [ Directory Number Centrex Number Abbreviated Number
] OLD STOP DATE : OLD STOP TIME : NEW STOP DATE: NEW STOP TIME: 6.10. CHANGES IN SIF PROCEDURES 6.10.1. Dialling Patterns For New Features For Centrex Members Table 2: Dialing Patterns For New Features For Centrex Members
Service Automatic Call Back - Activation Automatic Call Back - Deactivation Call Transfer Following are the legends used in above table. ABBR HSF
Usage Code HSF 1294 HSF 1295 HSF 1296 ABBR
Abbreviated number of called Centrex member Hook Switch Flash
90
C-DOT DSS MAX
Chapter 7.
Special Priority Implementation in S/W Release 2_2_1_9

7.1. FEATURE INTRODUCTION Currently in the field, for India-One Plan (or any other similar plan) implementation, the requirement is that all outgoing traffic from INDIA-ONE subscribers should be carried over a New TGP towards the TAX. At TAX, for that New TGP, charging data is defined for INDIA-ONE plan (Say @Rs. 1/ min), the charging CHB/Charging pulses are sent towards the originating exchange. In future, there may be some other plan, which will have the similar requirement like India-one. So a general strategy has been designed to implement some Special Sub/TGP Priorities to seize desired OG TGP for outgoing calls routing. 7.2. FEATURE IMPLEMENTATION a) A new parameter SPECIAL PRIORITY(SPL-PRI) has been introduced for this purpose. This special priority can be assigned to a subscriber during its creation or during modification of subscriber characteristics and becomes a part of subscriber office data. Its values are from 15 to 19 & default value is NONE. New values of special priority (i.e. 15 to 19) can also be allocated to Trunk Groups in TGP Priority field, which are in addition to the existing values of 1 to 8. Special priorities (15 to 19) if allocated, will be used internally for TGP selection only. These will not be sent over the network to subsequent nodes. Existing Sub/TGP priorities 1 to 8 will have the same interpretation as before.
b)
c) d) 7.3. 7.3.1. 7.3.1.1.
AT ORIGINATING EXCHANGE Call handling in Various Call Scenarios Existing Implementation in MOD-R2 Signalling Total, No. of Subscriber priorities = 1 to 14
91
Chapter 7
Operator can define only 1 to 8 priorities, while 9 to 14 are defined by system automatically based on LIN-TYP parameter in Cre-Sub command :-LIN-TYP CCB CCB-STD CCB-CRD PABX / Hunt Group OPR TST-LIN SUB-PRI 9 10 11 12 13 14
These priorities are internal to C-DOT & used to select an O/G TGP to route a call .Only three type of categories are sent over the Network as Calling Line Category for various type of subscribers (Viz. Ordinary Sub, Priority Sub & Operators) as explained below: Calling Subscriber Priority 1 2 to 6 7 8 9 (CCB) /10 (CCB-STD)/ 11 (CCB-CRD) 12 ( PABX/Hunt Group ) 13 (Operator) cat1 (ordinary line) cat 5 (operator) Calling Line Category sent Outward cat 1 (Ordinary Subscriber) cat 2 (Priority Subscriber) cat 1 (Data call) cat 1 (Ordinary line) cat1 (ordinary line)
Effect of Special Priority (SPL-PRI) having values 15 to 19 i) If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1, 7, 8, 9, 10, 11 or 12 and Special Priority (SPL-PRI) as any value from 15 to 19, then O/G TGP will be selected based on value of special priority(15 to 19) . In the network, category of ordinary subscriber i.e.1 will be floated as calling subscriber category. Thus for network purpose, priorities 1,7,8,9,10,11 and 12 are mapped to 1. If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1, 7, 8, 9, 10, 11 or 12 and Special Priority (SPLPRI) as NONE then O/G TGP will be selected based on value of
C-DOT DSS MAX
ii)
92
SPECIAL PRIORITY IMPLEMENTATION IN S/W RELEASE 2_2_1_9
SUB-PRI and category of ordinary subscriber i.e.1 will be floated in the network as calling subscriber category. iii) If a call is originated from a priority subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and Special Priority (SPL-PRI) as any value from 15 to 19 then O/G TGP will be selected based on special priority (15 to 19) and category of priority subscriber i.e.2 will be floated in the network as calling subscriber category. Thus for network purpose, priorities 2 to 6 are mapped to 2. If a call is originated from a priority subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and special priority (SPL-PRI) as NONE then O/G TGP will be selected based on normal priority (SUB-PRI) and category of priority subscriber i.e.2 will be floated in the network as calling subscriber category.
iv)
7.3.1.2.
Existing Implementation for CCS7 Signalling Total, No. of Subscriber priorities = 1 to 14 Operator can define only 1 to 8 priorities, while 9 to 14 are defined by system automatically based on LIN-TYP parameter in Cre-Sub command :-LIN-TYP CCB CCB-STD CCB-CRD PABX / Hunt Group OPR TST-LIN SUB-PRI 9 10 11 12 13 14
These priorities are internal to C-DOT & used to select an O/G TGP to route a call. In message based CCS7 signalling, Calling line category in various type of Subs is sent over the network as stated below : Calling subscriber Priority 01 02 to 06 07 08 (ORD-SUB) (Priority Subscriber) (Data Call) Calling Sub Category sent Outward 0A 0B 0C 00
93
Chapter 7
09 12 13 14
(CCB)/10(CCB-STD)/ 11(CCB-CRD) (PBX) (TRK-OPR) (TST-LIN)
E1 E4 09 E6
Effect of Special Priority (SPL-PRI) having values 15 to 19 : If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1 and Special Priority (SPL-PRI) as any value from 15 to 19, then O/G TGP will be selected based on value of special priority (15 to 19). In the network, category of ordinary subscriber i.e. 0A will be floated as calling subscriber category. If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) as 1 and Special Priority (SPL-PRI) as NONE then O/G TGP will be selected based on value of SUB-PRI and category of ordinary subscriber i.e.0A will be floated in the network as calling subscriber category. If a call is originated from a subscriber having priority (SUB-PRI) as any value from 2 to 6 and Special Priority (SPL-PRI) as any value from 15 to 19 then O/G TGP will be selected based on special priority and category of priority subscriber i.e. 0B will be floated in the network as calling subscriber category. Thus for network purpose, priorities 2 to 6 are mapped to 0B. If a call is originated from a subscriber having normal priority (SUB-PRI) as any value from 2 to 6 and special priority (SPL-PRI) as NONE then O/G TGP will be selected based on normal priority (SUB-PRI) and category of priority subscriber i.e. 0B will be floated in the network as calling subscriber category. 7.4. 7.4.1. AT TRANSIT EXCHANGE Existing Implementation At Transit Exchange IC TGP-PRI parameter can take values from 1 to 8.In case call is coming from an Ordinary Sub( Sub-Pri=1) from previous node, then we can make use of TGP-PRI value to seize the desired OG TGP towards further network. But in case ,call is coming from a Priority Sub ( Sub-Pri= 2 to 6), we cannot make use of TGP-PRI value to seize the desired OG TGP, as all calls now will pass through OG TGP defined against priority 2 on any route. 7.4.2. 7.4.2.1. Effect of additional TGP-PRI values 15 to 19 If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) either 1, 7, 8, 9, 10, 11 or 12 and call is coming on an I/C trunk
C-DOT DSS MAX
94
SPECIAL PRIORITY IMPLEMENTATION IN S/W RELEASE 2_2_1_9
group of the transit exchange having trunk priority > 14(i.e. Special priority), then O/G TGP will be selected based on the trunk priority and category of ordinary subscriber i.e.1 will be floated in the network as calling subscriber category. 7.4.2.2. If a call is originated from an ordinary subscriber having normal priority (SUB-PRI) either 1, 7, 8, 9, 10, 11 or 12 and call is coming on an I/C trunk group of the transit exchange having trunk priority < 15(i.e. Normal priority), then O/G TGP will be selected based on the trunk priority and Calling Line Category 1 will be floated in the network . If a call is originated from a priority subscriber having normal priority (SUBPRI) as any value from 2 to 6 and call is coming on an I/C trunk group of the transit exchange having trunk priority > 14(i.e. Special priority), then O/G TGP will be selected based on the trunk priority and category of priority subscriber i.e 2 will be floated in the network as Calling Line category. If a call is originated from a priority subscriber having normal priority (SUBPRI) as any value from 2 to 6 and call is coming on an I/C trunk group of the transit exchange having trunk priority < 15 (i.e. Normal priority), then O/G TGP will be selected based on the calling subscriber priority which is received as category of calling subscriber i.e 2(i.e. priority subscriber) and 2 only will be floated in the network as calling subscriber category. This is the case when call is coming from a priority subscriber and not opted for any special plan (like India One or Lo kar lo baat)
7.4.2.3.
7.4.2.4.
7.5. 7.5.1.
COMMANDS UPDATIONS TRUNK MANAGEMENT COMMANDS UPDATE 1. CRE-TGP ( CREATE TRUNK GROUP ):TRK-PRI field will be modified to accept values from 1 to 8 & 15 to 19 2. MOD-TGP-CHAR (MODIFY TRUNK GROUP CHARACTERISTICS) : TRK-PRI will be modified to accept values from 1 to 8 & 15 to 19 3. CRE-ROUT (CREATE A ROUTE): TGP-CHOICE parameter now will accept values from 1 to 19. 4. MOD-ROUT-CHAR: Same changes as in CRE-ROUT command. 5. DISPL-TGP-LIST:
95
Chapter 7
TRK-PRI will be modified. presently its value is defined as range, from 1 to 8. Now its range will be from 1to 8 & 15 to 19. 7.5.2. SUBSCRIBER MANAGEMENT COMMANDS UPDATE 1. ADD-MSN-DN (ADDING A MSN SUBSCRIBER TO AN ACCESS) New input parameter SPL-PRI is introduced in crp data. Range is from 15 to 19. 2. CRE-SUB New input parameter SPL-PRI is introduced in crp data. Range is from 15 to 19. 3. MOD-SUB-CHAR New input parameter SPL-PRI is introduced in crp data. Range is from 15 to 19. 4. CRE-HGP (CREATE A HUNT/DDI GROUP) New input parameter SPL-PRI will be introduced in crp data. Range is from 15 to 19. 5. MOD-HGP New input parameter SPL-PRI is introduced in crp data. Range is from 15 to 19. 6. DISPL-SUB-LIST New input parameter SPL-PRI will be introduced in crp data. Range is from 15 to 19.
96
C-DOT DSS MAX
Chapter 8.
New Strategy for Detailed Billing Records (CDR) Generation & Transfer
8.1. FEATURE INTRODUCTION Bharat Sanchar Nigam Limited (BSNL) is having countrywide presence with over 40 million subscriber base. BSNL has proposed to implement next generation stateof- Art Detail Billing Records (CDR) based Customer Care and Convergent Billing System. This can be achieved with deployment of Centralized Integrated Billing Systems with supporting technological and communication infrastructure. To implement this, Detail Billing Records (CDRs) are to be obtained from different type of Network elements capable of generating billable information, using centralized Mediation System. In BSNL Network, 90% of the switches are of CDOT Technology. To meet the above requirement, there is a need to generate 100% Detail Billing Records for all the completed calls. Generation of 100% Detail Billing Records is supported in the existing & New software releases of C-DOT. These Detail Billing Records need to be automatically transferred to the Billing center preferably in real time mode. 8.2. IMPLEMENTATION The above requirement has been implemented by a) Software changes at IOP end 1. 2. 3. Changes in existing s/w release to S/W release 2_2_1_9 Generation of hourly detailed billing files instead of daywise for subscribers and trunk groups NCBR & TGBR files have been modified to new names :
Old File Name ncbrddmmyy.dat tgbrddmmyy.dat New File name nchhddmmyy.dat tghhddmmyy.dat
97
Chapter 9
Where hh =Hour, dd= Day, mm = Month, yy = Year b. Addition of Compact Embedded System (CES) : A new add on unit known as Compact embedded systems (CES) has been introduced for this purpose. CES has to be connected with both CDOT IOPs at every site. Detail Billing records for subscribers and trunk groups will be automatically transferred every hour from CDOT IOP to Compact Embedded System (CES), CES will be connected further on LAN. All the Detail Billing Records can be picked up from CES at a predefined frequency by the centralised billing center using FTP (File Transfer Protocol) application. Modes of Detail Billing Records files transfer -Two modes of Detail Billing records file transfer are possible with this feature Automatic Whenever CES comes up after booting, automatic file transfer is invoked,otherwise automatic file transfer is invoked periodically. Manual - Manual file transfer is invoked on operator request. Once the CES is connected to IOP, on invoking file transfer utility in the defined mode (Manual or Automatic) the file transfer will begin. Refer CES User Document for details of Hardware / software, Installation, Maintenance procedures, various commands and Applications. The connectivity of CES with IOPs and Billing Center is shown in Fig 1.
IOP-5C IP NETWORK BILLING CENTER
CES BOX
IOP-5D
FIGURE 1
98
C-DOT DSS MAX
Chapter 9.
Do's and Dont's

9.1. IOP RELATED PROBLEMS AND SOLUTIONS To ensure smooth operation of the IOPs and the Exchange, some of the routine maintenance problems along with their solutions are explained. It is expected from the maintenance personnel to refer the specific section for a problem and strictly follow the same sequence, listed as possible solutions of the problem. Some of the problems are listed below : 1 2. 3. 4. 9.1.1. "CRP" fails to run on the IOP. "CRP" is running but CRP command fails to execute on the IOP. OOD - Report related problems. Printer related problems. "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 : CASE 2 : Solution : IOP5X> ipcrm - Q805 When "CRP" fails to run with error "CRP not found" 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
99
Chapter 9
Remove the cartridge from IOP-1 and insert it in IOP-0. The CRP file has been copied on the cartridge from IOP-1. Now copy the same file from cartridge to IOP-0. On IOP-0 : IOP5C>cd $CURREL IOP5C>cpio -icv<$TAPE Now remove the cartridge from the cartridge drive and run "CRP" on IOP-0. 9.1.2. OOD Related Problems Case 1 : aood_main process is recreating again & again on the CONSOLE of one IOP with error message: "recreating /u/code/iopete/aood_main, 2,1,0,0" Solution : 'aood_main' file is to be copied in this (say IOP-1) as per the procedure given below: Case 2 : Solution : 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 Alarms do not appear immediately after the unit fails. 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
100
C-DOT DSS MAX
DO'S AND DONT'S
Process aood_main will be recreated in response to the above command. Go to CRP prompt. Current alarms will start coming immediately. Go to CRP and resume normal operations. 9.1.3. Printer Related Problems The Report stopped coming on the printer Solution : Step 1 Check status of the printer using following command iop5x> cat /etc/passwd >/dev/icc_0 (if printer is connected on ASIO-0 of IOP VL or ASIO-1 of IOP-VH. If the output of the file is printed on the printer, then printer cable, printer port of IOP and printer itself are ok. Go to Step 2. In case output is not printed on printer, then i) ii) iii) iv) printer itself may be faulty, check by self test. printer cable may be connected on the wrong port. printer port icc_0 may be faulty. 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 IOPend 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.
101
Chapter 9
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) ii) iii) Scheduler is running. All printers (Pr1, Pr2 accepting requests ..... Pr4) are enabled and
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 This will start printer
iop5x> lpsched 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:
C-DOT DSS MAX
102
DO'S AND DONT'S
login : lp Password : DSSlp iop5x > enable prn1 iop5x > exit # 4. If lot of request are pending in the queue, then in admn account itself do following: iop5x > cancel x (x = pr1-1 etc.)
where x is the printer request pending in the queue, as shown in response to the lpstat -t command. Step 3 To change printer port from icc_0 to icc_4 (say) i) ii) move the printer cable from ASIO-0 (icc_0) to ASIO-4 (icc_4) for IOP VL. log into lp account login : lp Password : DSSlp iop5x> cd /usr/lib
iop5x> lpshut iop5x> lpadmin -pprn1 -v/dev/icc_4 iopx> lpsched iop5x> enable prn1 This will enable the printer at new port icc_4. Log out of lp account. 9.2. 9.2.1. DO'S AND DONT'S FOR CARD HANDLING 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.
103
Chapter 9
9.2.2.
Controller Cards (TIC, ANNC, TTC, MSC, TSC, CPU etc) Before changing the cards with that of spares arranged from some other sites it should be ensured that the new card is having proper S/W EPROMs compatible to the present software release working in the exchange. (for S/W details, refer Chapter 2).
9.2.3. 9.2.3.1.
CPU-S04/S05 Cards At the time of changing the CPU cards, the proper check sum of the CPUcards should be ensured before using it in the system because of the following reasons. Checksum of the EPROMs of the CPU-card used in SBM-RAX/TAX is different than that the CPUs used in MAX-L. Checksums of the EPROMs, of the CPU - cards used in different Base Modules of MAX-L i.e. BPU of BM and APU and SCU of CM, are different.
9.2.3.2. 9.2.4.
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. Message Switch Device (MSD) Card The jumper settings of MSD card should be verified as per its placement in Base Module or Central Module. Same MSD card is used in both the modules with different jumper settings.
9.2.5.
16 MB Memory Card (TME) Card or BME Card At sites, where 16 Mb TME or BME card is used in BMs and in CM, DO NOT CHANGE THE CARD IN POWER ON CONDITIONS. Switch off the corresponding power supply unit before jack-out or jack-in of the card.
9.3. 9.3.1. 9.3.2. 9.3.3.
GENERAL - DO'S AND DON'TS FOR O&M ACTIVITIES Take 'ed' and 'bd' back-ups daily in low traffic hours. At MAX-L/XL standard procedure of 'bc' backups after every two months can be followed. Monitor the disk space in the both the IOPs every day and ensure that disk space in / data does not fall below less than 5000 blocks in SBM-RAX/TAX and 10000 blocks in MAX-L sites. To monitor disk space: IOP5x>df. In the above display, the content against /data indicates the current available disk space.
104
C-DOT DSS MAX
DO'S AND DONT'S
9.3.4. 9.3.5.
A no. of new traffic reports have been implemented in 2_2_1_9 software. If the traffic reports are enabled, delete the 'tf' file group regularly. The 'old' backups (i.e. ed, bd, bc ... etc) taken in S/W release 2_2_1_6, should not be restored in the Exchange after upgrading it to new software release 2_2_1_9. While taking the display/printouts of TRUNK/ROUTE related traffic reports, the input against parameter MOD-NO should always be AM. 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. 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. Do not remove the floppy and cartridges from the drives till the drive's LED is glowing. 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. It MBM-Sites, do not create DTMF-ckts in TRUNK BMs and MF-Senders/ Receivers in Line-BMs. Do not execute INIT-SYS command. In case of emergency, execute INITMOD for the specific modules. Also for Base-Modules, do not execute INITMOD with INIT-LVL as PI or higher level of initialisation, as this will cause all STD nos. to be locked.
9.3.6. 9.3.7.
9.3.8.
9.3.9. 9.3.10.
9.3.11. 9.3.12.
9.4. 9.4.1.
OPERATION AND MAINTENANCE RELATED GUIDELINES Restoration of BMDC The BMDC cartridge should never be restored in day to day operation. Restoration of BMDC is required only when complete software is being loaded in the exchange. The restoration of "ed" backup does not require restoration of "BMDC". In case of data corruption when restoration of old exchange data is required, only "ed" backup restoration using command
105
Chapter 9
COPY-IN is sufficient. As and when BMDC has been restored in working exchange, "ed" as well "bd" must be copied. 9.4.2. Programming Trunk Groups in C-DOT DSS Keeping in view the complexity of the network and multiple features being supported in the common software release for different configurations / applications of C-DOT DSS, the following requirements should be met at the time of creating a trunk group : All the incoming trunk groups from TAX or ILT should be programmed as TTAX. All the incoming trunk groups from the parented exchanges should be defined as ORD. If C-DOT DSS is configured as TAX/ILT, all the O/G trunks should be defined as ORD if going towards a terminating exchange and TTAX if going towards a TAX exchange.
9.4.3.
Calendar Programming in C-DOT DSS To maintain consistency of alarms and reports for lines, trunks and service circuits. AUDIT with AUDIT-SET=12 should be programmed in the calender with daily triggers for all the days in the current year. This programming is required to be done only once in a year or every time when a software is loaded in the exchange.
9.4.4.
Use of TSC PROMs in Different Exchange Configurations When BMs of MAX-L are being integrated with MAX-XL or BM-XL are being integrated with MAX-L, then following care should be taken for use of TSC PROM. The checksum for TSC PROM will be same for BM-L as well as for BM-XL if used as SBM-RAX or as colocated BM/RSU of MAX-L. The checksum for TSC PROM will be same for BM-L as well as for BM-XL if used as colocated BM or RSU of MAX-XL.
Otherwise, we can conclude that the PROMs on TSC will depend on the type of CM i.e. CM-L or CM-XL and it is independent of BM-type. 9.4.5. TIC Cards with Compatible Software EPROMs The C-DOT DSS supports distinctive ringing in all the new exchanges with retrofit option for existing sites. The software has been designed to take care of compatibility related problems. The exchange is defined to support Distinctive Ringing by setting the system parameter SPL-RNG to 1. At these sites, all the PSUs should be updated for ECNs. Also the TIC cards
106 C-DOT DSS MAX
DO'S AND DONT'S
should be updated for compatible software EPROM. The TIC unit will not become INS unless compatible software EPROM is not used. 9.4.6. Mandatory Execution of MOD-DAY-TYP It should be ensured that in 1st week of January & July of every year, the command is executed to define the day type.
P P
9.4.7.
Programming for Routing of Priority Subscriber's Call In all the routes, priority 2 should be allowed by defining the trunk group choice against priority 2.
9.4.8.
Proper Definition of 'CRG-RTNs' for all Tariff Classes Charge Rate Number (CRG-RTNs) must be defined for all the tariff classes mentioned in the definition of Day Type 1 and 2. Other wise, call may fail during such time zones for which tariff class has not been defined in 'CRGRTN' and this may cause system initialilzation also.
9.4.9.
Precautions to be Taken While Handling Various Hardware Cards i) With the introduction of "Distinctive Ringing" in C-DOT DSS, there are two different versions of PSU used in Analog Terminal Unit. One with blinking LED to indicate the ringing cadence which is used at the existing sites. The modified PSU is identified with continuous LED and used only at the sites where "Distinctive Ringing" feature is offered. The two PSUs can not be used interchangeably. Also in one exchange, only one version of Power Supply can be used. 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. 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. 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. 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.
ii)
iii)
iv)
v)
107
Chapter 9
vi) vii)
While changing any Processor Card in BM, CM & AM, the jumper settings and EPROM status should be ensured. At the time of changing any controller card from some other site, PROMs of correct software version should be ensured before jacking the card into the system.
9.4.10.
O&M Changes as a Result of Feature Enhancements (i) (ii) (iii) (iv) A subscriber OOS-OPR. data can be modified only after making it
It is not possible to delete the subscriber in growth mode. All the Hunt Group related CRP commands are possible only when IOP is ONLINE. Due to enhanced disk partitioning, to utilize the full capacity of the disk, the boot up time for IOP has been increased to 30 minutes or even more depending upon the IOP and disk types, used. It is not possible to go to growth mode, when IOPs are in DUPLEX. This has been done to avoid data inconsistencies. 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. 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.
(v) (vi)
(vii)
9.4.11.
Known Constraints and Possible Alternatives 1. While creating a trunk group, more than 40 trunks should not be given at a time. If more than 40 trunks are required in a trunk group, trunks can be added using ADD-TRK commands in the existing trunk group. 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. In case of more than 100 trunks, MOD-TGP-CHAR does not work. Command is rejected with suitable error message. To modify the
C-DOT DSS MAX
2.
3.
108
DO'S AND DONT'S
characteristics, the no. of trunks should be reduced to <100. After modification, the deleted trunks should be added.
U U
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.
109
Annexure - A
IOP Loading Procedure

The S/W for the SBM RAX comes in four cartridge tapes, which are labeled as Unix, BAC, CPC and BMDC. These names stand for Unix (Operating System), Base Cartridge, Combined Patch Cartridge and Bare Minimum Data Cartridge. Step 1: Power up the system and wait for the system to come to the monitor prompt. IOCp.q> where p.q is the monitor prompt (say 7.0)
Enter the following command at the monitor prompt to boot the system from the unix cartridge, after inserting the cartridge in the drive. IOCp.q > bo c Following options will be displayed :Unix 11.6 0 1 2 3 lm.x.y ve.x.y vh.x.y xle.x.y OR Unix 11.7 0 1 2 cx.pmthM txl.pmthM vh.pmthM
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
C-DOT DSS MAX
110
IOP LOADING PROCEDURE
for
IOP-ML
or
IOP-VE
or
IOP-XLE
or
IOP- TMC
or
IOP- VH
(m/v/e/t/h)?
Input your choice depending upon the type of IOP. (say h for IOP-VH & v for IOP-VL) It makes only ROOT file system for UNIX. It does not disturb the other file system. CURRENT DEVICE CONFIGURATION
DEVICE WINCH CART TYPE SCSI SCSI NCRNO 0 0 ID 1 2 DEV-FILE DFLT-DV-FILE NAME W0s1_x C0S2 m350_0t w0 C MONITOR-
Only one WINCH present in the system. Configuring the WINCH as rest device. Format of WINCH is not required unless you are sure that the media is bad. If the WINCH is formatted, complete software must be loaded onto WINCH again. The system would then display: Want to format winch(s) (y or n)? If disk capacity is 520/700/1200/2100 MB, then need not to format normally hence press "n". The system would then display either of the following depending upon the type of the disks used: Disk capacity in MB 1200/2100/4500/9000 If formatting is required then press 'y' when asked 'Want to format Winch (Y or N) ?' Disk will be automatically formatted, without asking for bad block information. Formatting available for Disk #x Want to format (y/n) ? If 'y' is given the system displays the following and starts formatting the winch: Formatting winch #x ......... (In the above display, #x, would be #0 as only single disk is being used) Wait till the following print appears :
Annexure - A
Formatting over ! The system then displays : Load the object (y/n) ? Type y to continue the loading process or n to discontinue the loading process. The system would then display the following : Dev: 0x800xxSCSI : WARNING : BOOT BLOCK BEING WRITTEN Making ROOT file system ........ There would be delay at this option as the system makes the root files system on the winch where the UNIX cartridge would be loaded. The system then displays the following : Loading the object ............. This is followed by the list of files that are copied from the unix cartridge to the winch. After the complete cartridge has been loaded the system would carry out an audit to check whether all the files have been copied to the winch correctly. Wait till the process gets over. The system would then display the following and carry out the check of the root file system : When the check is over the system would display the following : Root File system Loading Complete Hit Reset, and Reboot from Winchester Remove unix cartridge from the drive. Press the reset switch on the front panel of the IOP. After pressing the reset switch wait till the system comes to the monitor prompt. Boot from the winchester by giving the following command at the monitor prompt : IOC x.x> bo After the system boots up it displays the following : Specify the release for which system is to be configured. Release 1_35_1_7(l3) or 1_4_1_3/1_4_1_4(l4) or 1_5_1_2/2_1_1_1/2_2_1_1 (l5) (l3 or l4 or l5) ?
Checking ROOT File System
112
C-DOT DSS MAX
Here enter 'l5' for 2_2_1_6/2_2_1_9 release. The system would display : Create file systems other than root (y/n) ? Give 'y' to continue loading of software i.e., BAC, CPC & BMDC. various file systems will be generated. This will take about 15 minutes. Then date format will be shown. Fill in correct date/time. It will show System Not in warm start level Boot after Copying BC
Step 2: The login prompt will appear as 'Console login : ' Login into root by typing Console login Password : : root <> 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 <>
113
Annexure - A
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 /<> 0<>
# > shutdown
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
114 C-DOT DSS MAX
VHC 7.0> bo <> After console login appears login into admn account as follows Console login Password : : admn <> CDOTadmn <>
Now, the IOP will come to iop5c> or iop5d> prompt. Go to CRP and set-site-id.
115
Annexure - B
Duplication Procedure for Cartridge/Floppy

It is required to make copies of cartridges and floppies at the sites. This can be done at the site itself, using dd command of C-DOT IOP. At the time of making the copies of cartridges, it should be ensured that the IOP on which copies are being made, is loaded with fresh S/W to ensure availability of sufficient disk-space. However, this is not required to make the copies of a floppy. Procedure 'A' is meant for copying single cartridge of BAC or CPC or BMDC. Procedure 'B' is for generating BAC, CPC & BMDC from the combined cartridge. A. 1. 2. 3. PROCEDURE FOR MAKING COPIES OF CARTRIDGE : Shutdown one of the two IOPs, say IOP-0 using CRP-command INIT-IOP:2,1; and then INIT-IOP:1,1; Load this IOP with complete S/W (UNIX, BAC, CPC & BMDC). Shutdown and boot it again. Login to 'root' account. Insert the 'Master cartridge' in the cartridge drive of the IOP-0 and execute the following command from #> prompt; #>mkdir /data/copy #>cd /data/copy
#>ulimit 180000 4. #>dd if=$TAPE of=xxxx
This will copy the contents of the master cartridge, in to file 'xxxx'. After completion of copying process which may take 10 to 40 minutes, depending upon the block size of the cartridge, being duplicated, the total block size will be displayed which should match with that of master cartridge. 5. Now the user may generate as may copies as desired, by repeating the following process : Remove the master cartridge and insert the cartridge on which copy is to be made.
C-DOT DSS MAX
116
DUPLICATION PROCEDURE FOR CARTRIDGE/FLOPPY
Execute the following command #>dd if=xxxx of=$TAPE
After completion of the process (10 to 40 minutes), the block size will be displayed which should match with that of master cartridge. By repeating STEP-5, generate as many copies as desired. To generate the copies of the other masters, start afresh from STEP-4. Remove file xxxx after required no. of copies have been generated. #rm xxxx #cd /data #rmdir copy
B.
PROCEDURE FOR MAKING COPIES OF BAC, CPC and BMDC Cartridge from COMBINED CARTRIDGE SUPPLIED BY C-DOT :A single cartridge having complete software (i.e BASE, CPC, BMDC, RGEN, EDRETRO UTILITY etc. )except UNIX will be supplied to the site. From this Cartridge, individual S/W Cartridge for BASE/CPC/BMDC/RGEN/ED Retro can be generated at site itself using following procedure. Bring SBY /Spare account. IOP to Warm start Level. Login into root
At UNIX prompt #>, execute the following commands #> mate 1440
Make a new Directory: #> mkdir #> cd /data/copy
/data/copy (should show /data/copy)
#> pwd #> ulimit 300000
Now insert combined S/W cartridge in cartridge drive & copy the contents by following command. #> cpio icv<$TAPE #> ls ls This will list all the files copied from Cartridge in this Directory. Note down the name as appear in this list on the extreme right column as the same will be used as filename later for making the individual s/w cartridges.
117
Annexure - B
Generation of Individual S/W Cartridge Insert a blank Cartridge, and copy the required file to generate S/W cartridge using following command: Say file name for BMDC of MAX-XL is generated by following command: #> dd if=bmdc-xl of=$TAPE bmdc-xl, then this will be
At the end, Block size of the Cartridge will be shown. Once copying is complete,remove the cartridge & label it properly. The contents can be verified by following command: #> cpio icvt <$TAPE
Similarly other S/W Cartridges & any number of copies can be generated at the site. PROCEDURE FOR COPYING UNIX 11.X CARTRIDGE : Before making copies, ensure that IOP is having unix 11.X loaded in it and there is sufficient disk space. Login into root account and give following command on unix prompt. #cpcart $TAPE or # cpcart /dev/rmt/m350_0t Following message will be displayed. Enter the cartridge to be copied Press RETURN to continue ...... Insert the master unix 11.X cartridge in the drive and press RETURN. Unix cartridge will be rewound first and then actual copying of contents will take place on the disk. No. of msgs will be displayed. In the end, message will appear : Rewinding the Cartridge Insert the blank cartridge Press RETURN to continue .....
118
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. 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 :
C-DOT DSS MAX
Copy another cartridge (y/n) :
DUPLICATION PROCEDURE FOR CARTRIDGE/FLOPPY
Wait .... removing files It takes some time to remove all the files, so please wait. Do not interrupt file removing operation. The unix prompt will appear after some time. DISPLAYING CONTENTS OF UNIX 11.X
COMMAND FOR 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.
119
Annexure - C
EPROMs for English Announcements

Sl. No. 1. 2. 3. 4. 5. 6. 7 8 9 10. 11. 12. 13. 14. 15. 16. 17 18. 19. 20. 21. Position U14 U17 U24 U29 U37 U45 U48 U56 U63 U71 U74 U15 U18 U25 U30 U38 U46 U49 U57 U64 U72 English only E3F0 B843 4BD0 2904 6440 F7BC A3B0 41A1 8160 E5D0 4C7B 20BA A400 ---------
NOTE :
1. 2.
EPROMs at Sl. No. 1 to 9 are the old ones used in P8.9 version. 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...
C-DOT DSS MAX
120
EPROMS FOR BI-LINGUAL ANNOUNCEMENTS
Annexure - C (Contd.)
EPROMs for BI-Lingual Announcements

Sl. No. 1. 2. 3. 4. 5. 6. 7 8 9 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20 21. 22. 23. 24. Position U14 U17 U24 U29 U37 U45 U48 U56 U63 U71 U74 U15 U18 U25 U30 U38 U46 U49 U57 U64 U72 U75 U19 U26 Eng./ Hindi ABF5 BF99 A505 ECA7 4905 E63A D96F E12A F3D1 A211 0847 543D 5493 50A9 505B 2722 70AC 06E1 C9D7 8A82 1D9D 520D --Eng./ Oriya ABF5 BF99 A505 ECA7 4905 E63A D96F E12A F3D1 A211 0847 7E9E 2F1B AA93 E837 DF32 8E9A 63AC 797F 1A6D A974 8A82 BE74 A217 Eng./ Bangla 687A E664 633A 99D8 C076 E0D6 FA00 D2F5 991B EC5B 7FDA C003 A7F5 E77E 1317 A610 DF80 7CCD EF00 -EBD4 4F3F --Eng/ Assamese 687A E664 633A 99D8 C076 E0D6 FA00 D2F5 991B 90E2 7B71 FEF7 B4F3 0FB5 41C7 4F56 F5E6 BDCB 4040 AEF1 B07E -76AB B6C5-Eng./ Kannada 613E 499B 6AE3 CA5D E5D0 4C7B 20BA A400 603D F878 CAC3 134D 6837 OD6C 3DAD 4853 E351 DFA3 2791 7EF2 ----Eng./ Malayalam E393 BB44 C074 F5A4 8DEE 3791 3DD7 F1CB 8C51 3468 1A27 C29C 6682 8605 B3AD D094 2D33 14F2 OB7C 9772 35A3 -------Eng./ Telugu 75FB 8994 86FD 5AD1 8A7D 7A68 EE9A CE2B 26A7 C8BF 896A FC58 AE8F 8D86 6CDF 5E92 FCC7 ----Eng./ Tamil F7DC 4435 F11C 159B 70AE 9EAA 143F A031 618D 3039 FOE2 F11A 0320 4D7O 4639 2F98 528B 84EE B563 --Eng./ Marathi 3A2B 5573 1111 6DD5 93D6 C755 709C 1AC9 B544 974D DCCE OBB1 AB53 A1A5 6EC6 2A3D 9FF7 2BFF 2206 9A21 E151 E524 D1EF --
Language Ids
01
07
09
08
02
03
04
06
05
NOTE : 1. All the EPROMs are 27C512 (200 nsec).
121
Annexure - D
Addition of Base Module

D.1 INTRODUCTION It is assumed that before attempting the BM-addition activities, all the requirements of additional hardware, as listed in Chapter 4 has been met. It is recommended to place the new additional Trunk BM in Rack Position 1 or 2 or 3 (as the case may be) in the 2nd suite. In some exceptional cases, where it may not be possible to place the Trunk BM as recommended above, the same can be placed in any other convenient place available in the suite. After physically installing the BM, complete the following activities step by step : However in case of Line BM, the placement of Base Module should be such that two Line Modules (One on each side) can be connected with the BM to other 2000 Lines by adding one Line BM alongwith two LMs. D.1.1 Physical Installation Power/Earth cables from PDP of the suite to the BM Rack. BM-CM Data Cable and BM-CM clock cables from CM to the BM-Rack.
At the time of laying down the BM-CM Data Cables and clock cables, it must be ensured that they are properly terminated at the right termination point as listed in C-DOT DSS MAX INSTALLATION MANUAL. Otherwise the added TRUNK BM will not get initialised. Set the jumper settings at the Back. Plane (Mother Board) of the Base Processor Unit as the logical BM-NO being configured in the Main Exchange.
This completes the physical Installation and interconnection of Trunk BM with CM. Parallely the trunk cables can be extended from the Rack to MDF. Now switch on the trunk BM and follow the procedures listed below to equip the base module and to create the necessary data. D.2 EQUIPPING THE NEW BM The procedure to equip the new base module in MAX-L/MAX-XL exchange is off-line where the BM is equipped and data is created in growth mode at warmlevel IOP without updation in the exchange and after completing the data base
C-DOT DSS MAX 122
ADDITION OF BASE MODULE
creation at the IOP, it is updated to the exchange memory by low level (part-init) initialisation of the complete system, which results in total system downtime of approximately 10 minutes. It is recommended, only off-line procedure should be followed to avoid any data inconsistency. Also, it should be tried out in low traffic hours. ED and BD should be taken before starting the addition. D.2.1 Off-Line Addition of A Base Module 1. Start with both IOPs in duplex. Take ED & BD backups. 2. Bring SBY-IOP (say IOP-1) to warm start level by INIT-IOP: 2,1; command. Create data regarding new BM in for IOP-1 in 'GROWTH MODE'. 3. Equip the new BM (say BM No. 6) in Growth mode by following command: <EQUIP-MOD Config Mod-No Ver-No = = = MAX-L or MAX-XL 6 1 or 2 Normal or Remote <default> or (1&2&17&18)
[MOD-TYP] = [DTK-id] Execute. =
After the command gets executed, verify following i) ii) DISPL-SYS-ALL : 6; 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 MFReceivers in case of TRUNK BM and only DTMF circuits in case of LINE BM. 7. Equip Terminal Cards LCC/CCB/DTK etc. - as per requirement. For equippage of LCC/CCB type terminal cards 'equip' utility in /u/admn/ cmdfile can be used.
123
Annexure - D
8. Once all the terminal cards have been equipped and verified using 'DISPL-TEN' for 'EQUIP' option, SUB's Data or TRUNK data creation can be started. For subscriber creation, 'create' utility lying in /u/admn/cmdfile can be used, by which first command files can be generated and then these command files can be run in Growth Mode to create SUB's Data in bulk. 9. Physically install new SSM/PSM cards in BTU corresponding to the new BM and SSS/PSS cards in SSU if required. Do make corresponding SS plane OOS-OPR before replacing SSS/PSS cards. 10. Now give command <del-fgp-file:, ioh; Then take 'ED' backup using 'COPY-OUT' command from IOP-1, in which new BM data has been created. 11. During Night hours, take 'BD back up from Active IOP-0, with required dates for Detail Bill Record and restore the same in IOP-1. Shut down and reboot IOP-1, to warm start level. 12. Now bring Active IOP-0 to warm start using command <INIT-IOP:2, 1; Then execute command <INIT-IOP:5, 1; from IOP-1 in which new BM data has been created. 13. Once IOP-1 becomes INS-ACT and critical alarm of IOP changes to urgent, give following command INIT-SYS: , PART-INIT; MLF LED will glow on ADP and complete system will go for initialisation up to 'PART-INIT' level. All the LEDs/Alarms on ADP will be cleared one by one except that for newly added BM-6. New BM-6 will go for code-loading along with message on console terminal of IOP-1. "Code Loading Begins. . . . . ." Wait for the local pass report of the new BM and then make all the MFC cards, ANNC & TTC INS-ACT. Make intra / inter BM calls from new BM and verify charging. Also verify voice quality with both SS planes with respect to both BUS-0 & BUS-1.
124
C-DOT DSS MAX
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 Old 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 : New Exchange Code" New x-cod1 ... ..
125
Annexure - D
"Minimum disc space requirement" SBM : MBM : Current disk space : 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. 3000 block 12000 block xxx block
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;
126
C-DOT DSS MAX
Once system has recovered completely verify Local, O/G & I/C calls and their charging. In case of any error message noticed while carrying out X-code modification. Consult C-DOT before proceeding further. Keep other IOP-1 in warm start with old ed for minimum 24 hrs and then synchronize it.
Caution : Note : 1.
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. 2. 3. 4. 5. 22 --> 55 (Any unused level) 20 --> 220 21 --> 221 23 --> 223 55 --> 222
127
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.
C-DOT DSS MAX
128
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
1. 2. 3. Step 2:
CLNG-CAT: Y (category assigned to CCB subscribers) CLLD-CAT: 1 (one) 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. 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.
Network of Balasore SSA

Area Code : 06782 Exch. Code : 3xxxx
BTS
Area Code: 06784 60XXX SDCA BHADRAK Subs. Cat = 22
BTS
Area Code: 06781 61XXX SDCA BASTA Subs. Cat = 23
MAX-XL LE
V5.2 Interface
BSC
BTS
Area Code: 06786 63XXX SDCA CHANDBALI Subs. Cat = 24
BTS
66XXX SDCA BALASORE Subs. Cat = 21
BTS
Area Code: 06788 65XXX SDCA SORO Subs. Cat = 25
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.
130
C-DOT DSS MAX
Annexure - G
Abort Filter Card (AFB) ECN Details

Note 1: If a BM using HMS card in TSU is being used to provide V5.2 Interface, then Abort Filter Cards (AFB) used in TSU should have Engineering Change Note (ECN) 12311 implemented on them in the field. Some cards already have the ECN implemented which requires one strap on the soldering side and one resistance on the component side.
Details are as under: Strap U4 (Pin3) to U11 (Pin12) on the soldering side. Resistance (R31) 470 W 5% MFR mounted between Pin12 and Pin 16 of IC Position U11 on the component side. The details given in Fig1. shall help identify whether AFB cards are with or without ECN implemented. These cards are used in every BMs 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.
131
Annexure - G
Fig.1: View from Component Side
U3
U10
Card Ejectors
U4
16 1
U11
Rev. Euro Female Connectors Position of Resistance (R31)
U5
U12
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. To implement the IN feature in 2_2_1_6 S/W DTMF Circuits are required in all type of BMs. To take care of such requirements, slot numbers xx-1-6-5 (MFC1) and xx-1-6-22 (MFC3) are modified from old S/W equipage as follows by the utility. However if IN functionality is not desired then equipage of MFC cards in TRUNK BMs may be modified to include only MF-SNDR and MF-RCVR. But care has to be taken that the V5.2 BM should have DTMF circuits. Block-I DTMF DTMF Block-II DTMF DTMF Block-III MF-SNDR MF-SNDR Block-IV MF-RCVR MF-RCVR
Note 3
Slot number xx-1-6-5 xx-1-6-22
132
C-DOT DSS MAX
Annexure - H
New Implementation on NSC and Fault Isolation Strategy

H.1 INTRODUCTION Main problems observed due to disturbance in the NSC output are as follows: General or Random noise in the Voice Calls. Disconnection/Slow speed of Internet and Data Calls. Frequent ETE failure of CCS #7 Module. Digital Trunks becoming OOS-SO. SS planes of CM becoming INS-FRC and OOS-SUS. ETE failure of some BMs breaking (mainly RBMs)
To overcome these problems, various ECNs i.e. ECN 15109, 15105, 15114 were implemented in CM-XL with following details:ECN 15109: Noise problem in Inter-BM calls & CCS#7 instability in CM-XL when the BM equipage is more than 16 and most of the Even BMs (i.e. RBMs) are equipped while the Odd BMs remain unequipped. Major changes in case of ECN 15109 are: Putting of Loop Back Connectors for the vacant odd BM position. Change of Resistor Network in ACP Card. Change of EPLD in ESM Card. Introduction of BSR Child Card on PSM Card. Introduction of STM Child Card on ESM Card.
ECN 15114: Noise in the ring back tone and voice path in CM-XL, with EUAFS03130A-060 at U62,U63, and U65 on PSS card instead of 3120 device. This has been taken care by changing the device program at U64.The checksum of U64 should be 9BE9 instead of CCD4/C53F. In case device is 3120 or 3020, then no change is required at U64.
133
Annexure - H
ECN 15105:Resistor of 2.0K, 1/4W 5% MFR should be inserted at R58, R66 in ESM Card for the Noise in RSU. Despite above ECN implementation, some 'NSC' related problems are difficult to isolate and only means to find out the fault is to change the NSC card one after the other. As there is no inbuilt tool to measure the Clock output, its difficult to conclude whether NSC card is actually faulty. H.2. NEW IMPLEMENTATION ON NSC In 2_2_(7.7)_6 Software Release, a new feature has been introduced as a tool for the measurement of clock accuracy with respect to active copy. Some pending problems have also been resolved in this new s/w release. Features: Swing Detection feature has been implemented for the Crystal Swing problem in NSC card or Swing in the Reference Clock (explained in details later). Detection of Oscillator Power Supply failure of NSC card. ETE failure of Some BMs during the Interchange of SS Plane Reason: IFC tuned to Standby copy of NSC. It was observed that sometimes when we interchange Switch plane or NSC, IFC remains tuned with previously Active clock (which is now standby after interchange). As the system data path and clock path will be different, this causes problems like non synchronization etc. For proper synchronization in the system, IFCs should be tuned to active NSC card only. As data flows in ACT paths only and if clock is extracted from standby path then synchronization may not be maintained between receive and transmit mode. This results in noise in Voice calls or disconnection of Data Calls. On giving interchange to SS plane, CCS#7 links and links between BM and CM goes down. SS plane not coming INS-ACT state after power on of SSC. SSC card goes suspect during DGN of NSC card.
Problems Resolved:
H.3. CRYSTAL SWING DETECTION FEATURE AND FAULT ISOLATION The root cause of the problem is due to crystal oscillator which behaves abnormally sometimes. Since NSC PLL tries to lock onto the reference clock, the output of VCO is affected by the erratic behavior of the self clock of the crystal. However this may also occur due to reference clock also in case the reference itself is bad.
134 C-DOT DSS MAX
NEW IMPLEMENTATION ON NSC AND FAULT ISOLATION STRATEGY
H.3.1
Case I : No Reference Clock Equipped The Architecture of CM-XL Clock distribution (without Reference Clock)
COPY 0 (ACT)
Clk O/P
Dup Clk
COPY 1 (SBY)
Clk O/P
O/P Clk to System i.e. IFCs/SWCs
C C K
Slf Clk
N S C
Dup Clk
N S C
Slf Clk
C C K
Fig. H.1 If there is no Reference clock equipped (i.e. no network synchronization) then the implementation of clock swing detection is as follows: For the detection of Crystal Swing the mandatory requirement is the availability of two clocks. As per implementation, the NSC of Active copy of SS plane feeds clock to system through IFCs and SWCs. Also the active NSC feeds clock to standby copy of NSC as duplex clock so that the standby is in synchronization with active for the smooth switchover from one copy to another, however the duplex clock from standby NSC is not honored by Active NSC. Thus there are two clocks available for standby NSC (Self Clk & Dup Clk) and only one clock (Self Clk) is available to active NSC. This means the swing is always detected in standby copy of NSC. If there is a swing in standby crystal, the Self Clock is disturbed with respect to duplex Clock and the system reports crystal swing. Similarly if there is a swing in active crystal the Duplex Clock is disturbed with respect to Self Clock and the system reports crystal swing. If a crystal swing is detected for 10 minutes, following report is displayed on ood/printer:
Crystal Swing Detection Report Unit Id : Clk 0 or 1* Crystal Swing Detected Change NSC card
Annexure - H
The Unit id will always be the number corresponding to SBY copy of NSC.
In DISPL-OOD-LOG command, one new type of report option is available i.e. Rep-type: mnsrep(204) which helps to view the Crystal Swing Detection Report On detection of this swing following possibilities exists. POSSIBILITY 1 : One Card out of Active/Standby is Bad. POSSIBILITY 2 : Both Cards in Active and Standby are Bad. Procedure to isolate the Faulty Card : (Possibility 1) STEP-1 a) b) c) Replace the standby card with a new good card. Jack-in the same and warm-up for an hour. Put the card in-service using PUT/FRC command after DGN.
There may be following Observations :OBSERVATION 1 : No swing detected after replacement and it remains inssby CONCLUSION : Standby card was bad. OBSERVATION 2 : Swing detected again within 10 minutes after the replacement of NSC card. CONCLUSION : Active card may be bad. In case of Observation 2, follow procedure given in step-2 below. STEP-2 a) b) c) d) e) f) Force an SS interchange. Active card will now become Stand-By. Make standby copy OOS-OPR. Replace the standby card with a new good NSC card. Jack-in the same and warm-up for an hour. Put the card in-service using PUT/FRC command.
OBSERVATION : No swing detected CONCLUSION : 1) Previously active NSC card is bad.
136
C-DOT DSS MAX
NEW IMPLEMENTATION ON NSC AND FAULT ISOLATION STRATEGY
2) Card removed from the system as Standby in Step-1 may or may not be bad. Procedure to Isolate the the faulty card : (Possibility 2) STEP-3 Replace the Standby card with NSC card which was ins-sby in the system initially and was removed in the Step-1. Wait it for warm up time (approx. an hour) Put the card in service OBSERVATION 1: No swing detected CONCLUSION : Initial card in standby copy is OK. OBSERVATION 2 : Swing detected again. CONCLUSION : Initial card in Standby copy is also bad. Replace the same with a good card. Take observation at least for a day or two. Then put the Reference Clock in service. It has been observed that the system stability improves if only one reference clock is equipped and the same reference is given to both NSCs. So it is recommended to equip only one Reference clock (Rclk0) and ideally any reference clock that shows one fault/failure in a day should not be used. H.3.2. Case II: Reference clock equipped The Architecture of CM-XL Clock distribution (with Reference Clock)
Ref. Clk
(ACT) COPY 0 C C K
Clk O/P
Dup Clk
(SBY) COPY 1
N S C Sby.
Ref. Clk Clk O/P
N S C Act.
Dup Clk
C C K
Slf. Clk
Slf. Clk
Fig. H.2
Annexure - H
If there is a Reference clock equipped (i.e. Network synchronization has been done) then the implementation of clock swing detection is as follows: As already told that for the detection of Crystal Swing the mandatory requirement is the availability of two clocks. If the reference clock is equipped then the Active NSC gets one clock as reference clock (Rclk) and tries to lock with the reference clock, however the reference clock input to standby is not honored. Rest of the procedure is same as explained in the case of no reference clock equipped. There are two clocks available for standby NSC (Self Clk & Dup Clk) and also two clocks (Self Clk & Rclk) is available to active NSC. This mean the swing is detected now in both the copies of NSCs. If there is a swing in Reference Clock, the Self Clock disturbed with respect to Reference Clock and the system reports crystal swing and vice-versa may happen. Similarly if there is a swing in active crystal the Duplex Clock disturbed with respect to Self Clock of Standby and the system reports crystal swing and vice-versa may also happen. Whenever there will be disturbance in the external clock, a swing will be detected both by the active and standby NSC cards. Crystal swing Detection Report will be displayed on OOD twice one due to Active copy and the second due to standby.
U
Procedure to isolate the faulty card. Whenever external clock is equipped and Crystal Swing Detection Report comes on OOD, first remove the external clock and allow system to work on the NSC card clock. Wait for a fresh Swing Detection Report on OOD. If no swing is detected then the fault is in the Reference clock and if swing is detected then the fault is in one of the NSC cards. Isolation of faulty NSC card has already been explained.
138
C-DOT DSS MAX
Annexure - I
Changes Required to be made to Run CTS-B Tool in 2_2_1_9 Software

Come to IOP5x prompt and give the following commands Step 1 : Step 2: IOP5x> cd $ABPEXE 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 : Step 5 : Step 6 : Step 7 : IOP5x> cd $CTSBP Use command pwd as indicated in step 2 and ensure that you are in /u/tool/ctsb directory or else repeat step 4. chmod +w ctsbi Use vi editor for editing the file ctsbi IOP5x> vi ctsbi Step 8 : Search for pattern CTSBENT :/CTSBENT At line number 69 and 70 in this file the contents will be displayed as follows. 0) CTSBENT = XXXXXX 1) CTSBENT = YYYYYY
Annexure - I
Step 9 : Step 10 :
For SBM replace XXXXXX with the address noted at step 3 or for MBM replace YYYYYY with the address noted at step 3. Save the file and quit : wq!
140
C-DOT DSS MAX
Annexure - J
List of Charge Rate Numbers

Following Charge Rate Numbers are available in BMDC defined for BS=1,2,3: Charge Rate Number = 0
TRF CLS 1 2 3 4 5 6 7 8 9 10 11 12 INIT CHARGE 1 1 1 1 1 1 1 1 1 1 1 1 CHARGE PERIOD 0 0 0 0 0 0 0 0 0 0 0 0 PRD CHARGE 0 0 0 0 0 0 0 0 0 0 0 0 CHARGE MODE FXD FXD FXD FXD FXD FXD FXD FXD FXD FXD FXD FXD METERING INFO METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD ANSWER INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP
141
Annexure - J
Charge Rate Number = 1

TRF CLS 1 2 3 4 5 6 7 8 9 10 11 12 Init Charge 0 0 0 0 0 0 0 0 0 0 0 0 Charge Period 0 0 0 0 0 0 0 0 0 0 0 0 Prd Charge 0 0 0 0 0 0 0 0 0 0 0 0 CHARGE MODE PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX METERING INFO METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD ANSWER INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP

TRF CLS 1 2 3 4 5 6 7 8 9 10 11 12 Init Charge 1 1 1 1 1 1 1 1 1 1 1 1 Charge Period 0 0 0 0 0 0 0 0 0 0 0 0 Prd Charge 0 0 0 0 0 0 0 0 0 0 0 0 CHARGE MODE PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX PRD-TAX METERING INFO METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD ANSWER INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP
142
C-DOT DSS MAX
LIST OF CHARGE RATE NUMBERS

TRF CLS 1 2 3 4 5 6 7 8 9 10 11 12 Init Charge 0 0 0 0 0 0 0 0 0 0 0 0 Charge Period 0 0 0 0 0 0 0 0 0 0 0 0 Prd Charge 0 0 0 0 0 0 0 0 0 0 0 0 CHARGE MODE NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET METERING INFO NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD ANSWER INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP

TRF CLS 1 2 3 4 5 6 7 8 9 10 11 12 Init Charge 0 0 0 0 0 0 0 0 0 0 0 0 Charge Period 0 0 0 0 0 0 0 0 0 0 0 0 Prd Charge 0 0 0 0 0 0 0 0 0 0 0 0 CHARGE MODE NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET METERING INFO METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD ANSWER INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP
143
Annexure - J

TRF CLS 1 2 3 4 5 6 7 8 9 10 11 12 Init Charge 2 2 2 2 2 2 2 2 2 2 2 2 Charge Period 3 3 3 3 3 3 3 3 3 3 3 3 Prd Charge 2 2 2 2 2 2 2 2 2 2 2 2 CHARGE MODE PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL METERING INFO METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD ANSWER INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP

144
C-DOT DSS MAX


145
Annexure - J

TRF CLS 1 2 3 4 5 6 7 8 9 10 11 12 Init Charge 0 0 0 0 0 0 0 0 0 0 0 0 Charge Period 0 0 0 0 0 0 0 0 0 0 0 0 Prd Charge 0 0 0 0 0 0 0 0 0 0 0 0 CHARGE MODE NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET NO-MET METERING INFO NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD NON-MTRD ANSWER INFO NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP NANS-XP RING INFO NO-RING NO-RING NO-RING NO-RING NO-RING NO-RING NO-RING NO-RING NO-RING NO-RING NO-RING NO-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP

146
C-DOT DSS MAX

*Charge Rate Number = 13

147
Annexure - J


148
C-DOT DSS MAX


149
Annexure - J


150
C-DOT DSS MAX

Charge Rate Number to be associated for SAARC countries Charge Rate Number = 17
151
Annexure - J

This Charge Rate number is to be associated for countries in Africa, Gulf ,Asia & Oceania Charge Rate Number = 18
152
C-DOT DSS MAX

This Charge Rate Number is to be associated for all countries in America Charge Rate Number = 19
153
Annexure - J

This Charge Rate Number is to be associated for all the EUROPIAN Countries Charge Rate Number = 20
154
C-DOT DSS MAX


155
Annexure - J


156
C-DOT DSS MAX


157
Annexure - J


158
C-DOT DSS MAX


159
Annexure - J
*Charge Rate Number =53


160
C-DOT DSS MAX
*Charge Rate Number =47


TRF CLS 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. INIT CHRG 0 0 0 0 0 0 0 0 0 0 0 0 CHRG PRD 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 PRD CHRG 1 1 1 1 1 1 1 1 1 1 1 1 CHRG MODE PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL MET INFO METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD ANS INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP
161
Annexure - J

TRF CLS 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. INIT CHRG 1 1 1 1 1 1 1 1 1 1 1 1 CHRG PRD 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 1200 PRD CHRG 1 1 1 1 1 1 1 1 1 1 1 1 CHRG MODE PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL PRD-LCL
(BS1/BS2/BS3)
MET INFO METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD METERD ANS INFO ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP ANS-XP RING INFO NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING NRM-RING BEEP INFO NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP NO-BEEP
162
C-DOT DSS MAX

Software Release 2 - 2 - 1 - 9 (2.22) Retrofit Procedure For Max/Sbm-Rax/Tax

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Software Release 2 - 2 - 1 - 9 (2.22) Retrofit Procedure For Max/Sbm-Rax/Tax

Caricato da

Copyright:

Formati disponibili

C-DOT DSS MAX