Subscriber and Trunk Priority/Category Handling in C-DOT DSS

A. Some Related Parameters

1. SUB-PRI: Subscriber Priority [CRE-SUB / MOD-SUB-CHAR / MOD-LIN-

CHAR]

This is a class-of-service parameter and is used for assigning preferences to subscriber

lines. The preference level is used for allowing/disallowing calls from lines in times of
congestion. Priority 1 to 8 are assigned via MML commands, while 9 to 14 are
automatically assigned by the system as follows:

SUB-PRI at LE Meaning
1,7,8 ORDINARY Subscriber
2,3,5,4,6 Priority subscriber
9 ORD-CCB
10 CCB-STD
12 PBX
13 Operator
11,14 Spare

The priority of the calls originated from a Trunk Offer operator is assigned as 13 for the
purpose of call routing. However, in MF-R2, the subscriber category is sent as 5.

2. SUB-CTG : Subscriber Category [CRE-SUB / MOD-SUB-CHAR]

This parameter can have values from 1 to 64 and is used to differentiate charging of
calls originating from different subscriber lines. All lines in a BM have the same
category.

3. TRK-PRI: Trunk Priority [CRE-TGP / MOD-TGP-CHAR]

All circuits (trunks) in an Incoming Trunk Group (TGP) are assigned the same priority for
the purpose of outgoing trunk assigned on a route selection. Calls received from TGPs
can be restricted to only some outgoing TGPs based on the trunk priority. The following
points may be noted:

a) In case of decadic trunk signaling. TGP-PRI overrides the SUB-PRI received

from the originating exchanges.
b) Calls with priority 1 are routed on TGP for priority 1. This is generally reserved
for originating calls and is not assigned for Incoming calls for the purpose of
differentiating Initial Charge.
c) In case of R2, calls from priority 2,3,4,5 and 6 are routed on trunk group with
priority 2.
d) Incoming calls with category 5, i.e. as a result of trunk offer, are sent out only on
outgoing trunks meant for priority 13 calls.
B. Assignment of Subscriber Category at LE and its Treatment at Transit
Center

a) In decadic signaling, the local data of the TGP is relevant. No significance of the
sub priority at the LE.
b) In MF-R2,, the subscriber priority at the LE is mapped as follows:

SUB-PRI at LE SUB-CAT in MF-R2 Treatment at Transit Centre

1,7,8 1 Local Incoming TGP-PRI data
takes precedence at Transit
2,3,4,5,6 2 Calls will pass through OG
TGP defined for Priority=2
13 5 Calls will pass through OG
TGP defined for Priority=13
9,10,12 1 Local Incoming TGP-PRI data
takes precedence at Transit
11,14 Spare or Not implemented Spare or Not Implemented.
Treated as 1.

Note: If SUB-PRI = 11,14 or undefined category will be passed treating is a ordinary

Subscriber at transit center.

c) In case of CCS7 signaling, subscriber priority information is carried in the IAM

message as part of the Calling-subscriber-Category field.

SUB-PRI at Calling-Sub-Cat in Treatment at Transit Centre

LE IAM
1 Ordinary Calling At the originating Exchange treated as Priority =
Subscriber (0000 1 for the purpose of outgoing trunk selection.
1010) (0A) The Calling-Sub-Cat field in IAM is transparently
passed ahead. At the transit point it selects
Outgoing TGP depending on the Incoming TGP
Priority.
2,3,4,5,6 Calling Subscriber At the originating Exchange treated at Priority =
with Priority (0000 2,3,4,5,6 respectively for the purpose of outgoing
1011) (0B) trunk selection. The calling-Sub-Cat field in IAM
is transparently passed ahead. At the transit
point it selects TGP for TGP-PRI=1 irrespective
of Incoming TGP Priority.
9 Coin Collection Box At the originating Exchange treated as Priority =
(1110 0001) (E1) 9 for the purpose of outgoing trunk selection.
The Calling-Sub-Cat field in IAM is transparently
passed ahead. At the transit point it selects TGP
for TGP-PRI=1 irrespective of Incoming TGP
Priority
10 Payphone (STD- At the originating Exchange treated as Priority =
PCO) (1110 0001) 10 for the purpose of outgoing trunk selection.
(E1) The Calling-Sub-Cat field in IAM is transparently
passed ahead. At the transit point it selects TGP
 for TGP-PRI=1 irrespective of Incoming TGP
Priority
12 PABX (1110 0100) At the originating Exchange treated as Priority =
(E4) 12 for the purpose of outgoing trunk selection.
The Calling-Sub-Cat field in IAM is transparently
passed ahead. At the transit point it selects TGP
for TGP-PRI=1 irrespective of Incoming TGP
Priority.
13. National Operator At the originating Exchange treated as Priority =
with TO (0000 1001) 13 for the purpose of outgoing trunk selection.
(09) The Calling-sub-Cat field in IAM is transparently
passed ahead. At the transit point it selects TGP
for TGP-PRI=13 for Incoming calls.
7 (0000 1100) (0C) It is treated as Priority = 7 for the purpose of
outgoing trunk selection at the originating
Exchange. At the transit Exchange it selects
TGP for TGP-PRI=1 for outgoing calls.
8 (0000 0000) (00) It is treated as Priority = 8 for the purpose of
outgoing trunk selection at the originating
Exchange. At the transit Exchange it selects
TGP for TGP-PRI=1 for outgoing calls.

Note: The priority of the calls originated from a Trunk offer operator is assigned Calling-
Sub-Cat a Operator with Trunk Offer (0000 1001)

C. Problems Encountered due to the Present Implementation

In case of CCS7 following problems are observed:

i. Originating subscriber with priority 7 and 8 are coded as 0C{0000 1100(data

call)} and 00 {0000 0000 (unknown national use)} respectively which is not as per
any specs.
ii. Except Operator with TO and Ordinary calling subscriber, all other priority
subscribers in the transit network selection are treated as Priority =1 for the
purpose of outgoing trunk selection irrespective of incoming TGP Priority.
However calling Sub-Cat field in the IAM is passed transparently. In the case
of ordinary subscriber however the TGP priority takes precedence for Out going
TGP selection which is correct implementation.
iii. Unlike implementation in R2 signaling, subscribers with Priority 2,3,4,5 and 6
selects TGP in the originating Exchange based on respective priority and not on
TGP-PRI=2.

D. Solution for the Problem Encountered

i. As in the case of R2 subscriber with priority 7 and 8, should be treated as

Ordinary calling subscriber both at originating and Transit Exchange and should
be coded as 0000 1010 (0A).
ii. Subscribers other than priority and Operator with TO should take incoming TGP
priority as priority for outgoing TGP selection at the transit network, as is the case
in R2 signaling.
iii. Subscriber with Priority 2,3,4,5 and 6 should select TGP at the Originating
Exchange for TGP-PRI=2 as in the case of R2.
iv. Any other undefined category subscriber at the transit network should be treated,
as Ordinary subscriber as in the case of R2 and the call should be passed
through.
 HARDWARE DETAILS THAT ARE TO BE CHECKED IN SHM CARDS (SU7 UNIT)

There have been a lot of changes in the SHM hardware. This note describes the
details of the changes that have been done so far. It has t be ensured that the changes
mentioned here are done before checking for stability of the system. Please note that all
these changes are applicable irrespective of the software release. Especially, the EPLD
firmware is also independent of the software release. Only distinction is for BPC version
and HPC version cards. Please refer to the LATEST SHM documents for further details.

Power Monitor (U2):

The power monitor IC U2 with part code EUD-C001232-000 should be of Dallas
make only (vendor part code: DS1232). Earlier, MAXIMs MX1232 was also approved
by C_DOT as an additional source. Due to stability reasons, the component was
removed from the COI in 1999. Hence some old SHM cards might have MX1232 in U2
position. This might cause instability.

SRAM Elements (U4, U11, U19, U33, U34, U44):

Previously, 128 KB SRAM chips (C-DOT part code: EUM-c0628128-0B6) were
used in SHM, Subsequently it has been upgraded to 512 KB chips (C-DOT part code
EUM-C0628512-0B6) for HPC version SHM, through ECN no. 15079, dated 08-12-1998.
It is desirable that all the cards have the higher capacity memories (especially with HPC
as the SUM controller).
Resistor Changes:
1. A resistor R48 (10K) has been added through the ECN 15079, to take care of copy
selection problem during the SU7 copy changeover. Refer to the AD document for
assembly procedure of the resistor.
2. The value of the pre-charge resistors (R45-R47) has been changed to 2.2E (C-DOT
part code: ERF-E002, 200-112).
EPLD Firmware Details:
The firmware in EPLDs of SHM has undergone a lot of changes, the latest of
which is reflected in the ECN no.: 12416 dated 09.06.2003. Refer to the latest FRM
document for SHM for further details. The changes done in the FRM are to take care of
hardware issues, and irrespective of the software release version, it is always better to
have the latest firmware in the cards.

LATEST CHECKSUMS OF SHM CARD EPLDs (as on 21-Aug-03):

IMP EPLD U6, SCC EPLD TUC EPLD PAL U22, U31
U9 U47 U51
BPC VER EC13 1AA6 F192 70AA
HPC VER 2EF2 18F1 F18A 65B7
 Procedure for Barring Local Calls and allowing IN Services Calls
(e.g. ITC/VCC, ACC, PRM, FPS) under BSNL SULABH Scheme

Option 1:
[Valid for MBM/SBM/RSU/AN with version 2_2_1_4]

Steps:

1. Modify the system parameter using command MOD-SYS-PARAM:

SUB-CHRG-CTG=2
[To implement subscriber category based charging]
2. Find out any free category (which is not used in I/C TGP or Subscriber category)
e.g.25
3. The subscriber line should be assigned access barring [ACC-BAR] as OG-UPTO-
LCL & modify SUB-CAT=25 using command MOD-SUB-CHAR for existing lines or
CRE-SUB for new subscriber lines to be opened for SULABH scheme.
4. Modify subscriber charging using MOD-SUB-CRG:

Calling :25 Calling : 25 Calling : 1 Calling : x

Called :25 Called : 1 Called : 25 Called : 25
Crg-rtn : Invalid Crg-rtn : Invalid Crg-rtn : 21 Crg-rtn : on-metered
charge rate No.
(e.g. 4)

Where x = All existing Incoming TGP categories.

Allow category 25 in IN services routs [e.g. 16xx] using MOD-ROUT-CHAR with non-
metered charge-rate number being used for CAT-1 already.

Note: -
Category 25 should not be allowed in any other route.
Option 2:
[Valid for SBM/MBM with version 2_1_1_1 and 2_2_1_4]

Steps:

1. Equip and ATU frame in any Trunk BM (say BM-5) as per normal procedure with
proper TIC ID and equip the LCC as per normal procedure.
2. Create a subscriber with access barring [ACC-BAR] as OG-UPTO-LCL
3. Change the category of BM-5, using MOD-SYS-PARAM:
Parameter Name : BM-05-CAT
Parameter Value : 25 [Any spare category]
4. Modify the subscriber charging using command MOD-SUB-CRG:

Calling :25 Calling : 25 Calling : 1 Calling : x

Called :25 Called : 1 Called : 25 Called : 25
Crg-rtn : Invalid Crg-rtn : Invalid Crg-rtn : 21 Crg-rtn : non-metered
charge rate No.
(e.g. 4)

Where x = All existing Incoming TGP categories

5. For IN-PCOs where I/C is barred, modify the [ACC-BARR] of IN-PCO number using
MOD-SUB-CHAR:

[ACC-BARR] = 2-2-1 [I/C barred O/G upto LCL all BS]

Note:
i. Option-1 is better in case of S/W version 2_2_1_$.
ii. In Option-2, RSU not compatible for SULABH scheme.
iii. SULABH facility not compatible for INTEGRATED IN MBM Exchange.
 Annexure-I

Procedure for Transferring Files from IOP to PC and Vice-Versa

INTRODUCTION: There are two utilities namely rz and sz present in directory

$TOOLP which are used to transfer the files from IOP to PC/LAPTOP and vice-versa.

i. rz is the utility to transfer the file from PC/Laptop to IOP

ii. sz is the utility to transfer the file form IOP to PC/Laptop.

PROCEDURE: For using the rz and sz utilities follow the procedure given below:

Copy the rz and sz utilities in $TOOLP directory in IOP.

Connect the com port (say com2) of PC/Laptop to ASIO port of IOP using RS-
232 cable having female connector on both side.
Go to Hyperterminal option on the PC/Laptop available in Accessories.
In th etop menu of Hyperterminal, click on file and select the properties to
change the setting of Hyperterminal. Select Port as COM2 and click on
configure. In the port setting of COM2 give the following values for the given
parameters
a) Bits per second = 9600
b) Data bits = 8
c) Parity = None
d) Flow control = None
Click OK after setting all these parameter. New click Setting and select
Emulation as VT100 and click OK.
After connecting the cable and changing the setting the above setting login
prompt will be obtained on the Hyperterminal.
Login as admn and password as CDOTadmn
The file from IOP to PC/Laptop can be transferred by using the sz utility. For
this run the following command at IOP prompt:

IOP 5x>sz filename

This will transfer the file from IOP to Hyperterminal (PC/Laptop)

The file form PC/Laptop to IOP can be transferred using the ulitlity rz. For this
run the following command at IOP prompt:

IOP 5x>rz

In the top menu of Hyperterminal, click on transfer and select the send file. A
browser window will get opened. Select the Protocol as Z modem and the file name to
be transferred to IOP.

Cable Preparation
1. RS-232 cable having female connectors on both sides should be used.
2. Pin connection for cable should be 2-3, 3-2, 5-5.
3. Pin no 1-4-6 should be shorted both sides.
 Annexure III

RECOVERY TYPES AND SOLUTIONS

S.No Site Name Recovery Type Details Solution

& S/w
1. Roper Process 180c378h Recovery coming on i)Put Break Point
2_1_4.19_1 (Code 207) I/C TGP (MF) from to find out dialled
39h parented exchange digits.
Vidisha 0h or I/C TGP from ii) In O/ TGP of
P4.26 1h TAX exchange parent station on
defined as TTAX which call is failing,
Udhampur EQN : 7 04 4200h and calls transiting change TGP-
P4.26 to parent stations on Type=TTAX OR
STD code with TGP Change ROD=5 or
TYP=ORD and 6 (STD code
ROD=1 length+1)
2. Sonepat Process 180cc06b0h Recovery coming in Block OOS-Trans
2_1_4.19_1 (Code 107) Trk. BM7, where PCMs till
gen_rec_routine PCMs are going disturbance
7ah, OOS-Trans and bilized.
ffff fffff h, PCM, channels (Solved in P4.26
0h going OOS-KLR onwards)
very frequently
3. Kalanwali Process 18020C01h A0 Send failure to Ti01-0 made OOS
2_1_4.19_1 (Code 208) or (Code peripheral and ti01-1 made
210) gen_rec_routine Controllers. 4H ACTIVE
A0h TIC updation not
4h taking place.
18 a0 0041h 18a00041h -> Ti01-
0
4. Unnao Process 180035 25h Line BM-1 booting Solved in S/W 6.x
2_1_4.19_1 (code=218) frequently onwards
otp_rec_routine 192h-Time out
192h,4h,143h problem
Eqn: 3600h
5. Process 18003d06h A0 Send failure If recovery is very
(Code 214) frequent, part-init
Gen_rec_routine to system will
A0h solve the problem
4h
18482359h
6. Samarala Process 185605 e0h AM repeatedly Process 05e0 =
2_1_4.19_1 (Code 94), Booting to SBL-CLR temp
gen_rec_routine with reason SRF- Reason: System
a4h Counter O/F parameter file is
ffff ffff corrupt
 0h Load fresh file
ansprm in
$GLBDATAP from
BMDC. Modify
relevant system
parameter as per
old data. Then
give part-init to
AM
7. Moreha Process 18060830h tca process (830) Unequip/epuip
Ahmedgarh (Code 131), gen_rec getting hit service cards
P4.26 C8h (annc/mfc) may
0h solve the problem
70000h Delete Trunking
Data in BM may
solve the problem
tca process can
be halted for some
time through BP
terminal mdeb>hlt
%830
old Ed can be
used to solve the
problem
8. Unnao Process 18080b4ch 192h = Time Out Put Break Point to
(Code 203) Problem find out dialled
Cmf_rec_routine digits
192h ch = Call Clearing
ch Phase
0h
eqn : Changing
9. Muzaffarpur Process 18161aa1h 192h = Time out Put Break Point to
(Code 208) problem fine out dialled
Ogmf_rec_routine digits
192h 4h = Updation of Blocking of
4h TIC
 Detail of ECN 50030 (for OOS-SO problem in BRI subscriber)

OLD Checksum/IC Type Revised Checksum/IC

Type
U67 (EPLD) 80FE 6075
U66 (Dual Multi Vibrator) 74HC123 74HCT123
U77 Octal/Buffer/Line Drive 74HC241 74ABT241
U78 Octal/Buffer/Line Drive 74HC241 74ABT241
8.12 Modem setting for Dialup CRP Terminal at RSU

Set Terminal speed at 9600 and do following setting in both the modems

at
ok
at&f (factory setting)
ok
atel (Enable echo)
ok
at$ba0
ok
at$sb9600
ok
at$mb9600
ok
at&d0 (Ignore DTR signal)
sok
ats0=1 (Ans at 1st ring)
ok
at&w0&w1 (To save profile)
ok
at15 or at17 (To display setting)

Now switch OFF & ON the modem. Verify setting

for RSU end modem: Only difference is to Enable ECHO by ate0

Use normal modem cable at both ends having one to one connection.

i.e. 2-2
3-3
4-4 etc.

8.13 9Pin-25 Pin Connection and PC to modem Cable for COMAC for Dialup
Mode

9Pin 25 Pin Connection PC to modem Cable for COMAC for Dialup Mode
9 Pin 25 Pin 25Pin 25 Pin
1 - 8 2 - 2
2 - 3 3 - 3
3 - 2 4 - 4
4 - 20 5 - 5
5 - 7 6 - 6
6 - 6 7 - 7
7 - 4 20 - 20
8 - 5 22 - 22