Introduction and Highlights of New Software 2_2_1_9

1.3. NEW SOFTWARE RELEASE 2_2_1_9 (2007)

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

New features are :-

i) CENTREX GROUP implementation

ii) Special subscriber priority implementation

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

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

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

·        500 CENTREX groups can be created in MBM,

·        10 CENTRAX groups are possible in SBM.

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

·        Only PSTN & V5.2 subscribers can become members of Centrex Groups.

·        ISDN subscribers can not be added to Centrex groups.

·        Centrex Feature will not work in 'RBMSA' mode.

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

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

·        Complete flexibility is provided to charge or not to charge the 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 Usage Code

Automatic Call Back - Activation HSF 1294

Automatic Call Back - Deactivation HSF 1295

Call Transfer HSF 1296 ABBR

Following are the legends used in above table.

ABBR Abbreviated number of called Centrex member

HSF Hook Switch Flash

 New commands added for Centrex Group Features are:-

1. CRE-CNTRX

2. DEL-CNTRX

3. MOD-CNTRX-CHAR

4. REM-MEM-FRM-CNTRX

5. ADD-MEM-TO-CNTRX

6. DISPL-CNTRX-CHAR

7. DISPL-CNTRX-MTR

8. MOD-CNTRX-OBS

Note:

Refer Chapter 5 for details of Centrex Group Data Creation/Display

& maintenance commands.

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. IOP Synchronization and Duplex working has been stabilized.

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

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

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

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

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

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

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

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

1.3.5. Enhancements in S/W Release 2_2_1_9

1. During Creaion of Subscriber data, default value of the parameter

"ACC-BAR" will be IC-NOT-BRD/OG-UPTO-REG/BS12 (Earlier it was IC-NOT-BRD/OG-UPTO-LCL/BS12).

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

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