Fine-tuning of OCB IN working

After launching of new ITC cards of OCB IN in south India, some of the problems
observed at different sites are explained with suggestions to improve OCB IN functioning.

OCB SSP to SRP call routing follows the network scenario as given below. At some
stations, Lev-2 OCB TAX is configured as SSP.

A B C D E F
Local OCB SSP Lev-2 TAX Lev-1 TAX Lev-1 TAX SRP

Sl. Network Problem/Observation Solution/Suggestion

No. arrangement
1 PTX=NTSR at B & If call is tried using ITC
E, and PTX= 41/42/1 card from telephone with
(i.e. not NTSR) at C pulse-dialing facility, call is
& D for the SRP getting dropped while
IND. Normal PTX dialing the called number.
(41/42/1) is kept at C Even for calls made from
& D to avoid splitting tone-dialing telephones, call
of INDs to give is getting dropped during
NTSR for SRP IND dialing called number, if
number alone (e.g. complete announcements
08025380123). are heard and then card
number, destination number,
(In many E10B Local etc, are dialed slowly (due to
exchanges, tone checking & dialing). If
dialing facility KLA complete procedure upto
is not given for most dialing full called number is
of the subscribers). not completed within 60
seconds from the time of
starting of first welcome
announcement, call is timed-
out by C or D TAXs.
2 Same as above Due to Answer message
not received, all calls to SRP
are treated as failed calls at
C & D. OFCLA shows
CE=70. This reduced the
ASR of inter-TAX route.
3 Same as above OFINA fault messages (with
SCP PS code) at SSP, for
calls timed-out or for SRP
calls failed due to
congestion.
4 For SRP IND, Lot of OFSUT fault
PTX=NTSR at SSP, messages at SSP, for the
and normal PTX at CICs handling SRP calls.
TAXs C/D/E.
Due to PTX=NTSR for SRP IND
at E-TAX, Answer message
received from SRP is not sent
backwards to C/D-TAX resulting
in 60 sec time-out. PTX can be 0
or 1 at E-TAX so that Answer
message shall be repeated
backwards. This avoids the
timing problem at C & D. Call
dropping is not taking place even
with slow dialing or pulse
dialing.
By having normal PTX (i.e. not
NTSR) at E, Answer message
is received and SRP calls are
treated as effective calls and
ASR improved drastically.
OFINA fault messages are
negligible with PTX=0 at SSP
and PTX not NTSR at C/D/E.
By having PTX=0 for SRP IND
at SSP also, OFSUT messages
are not generated.

Page 1 of 2
5 From D- TAX (e.g. Due to routing of more calls Instead of specifying 11 digit
Coimbatore), 08025 (including SRP calls) number as SRP IND, a 4 or 5
codes were routed to through BG Central TAX, digits spare code (e.g 1552) can
Bangalore WMS BHCA of Central TAX has be specified as SRP IND. This
TAX whereas SRP increased considerably code can be routed as it is upto
was connected to BG resulting in heavy call SRP connected TAX. Or, 1552
Central TAX. Since rejection. can be routed upto D-TAX where
11 digits number was it can be routed to SRP-TAX
given as SRP-IND, to with DIS=CN in the ACH to
avoid splitting of convert to actual SRP IND. This
codes upto 11 digits, arrangement will avoid splitting
all 08025 codes of codes at B/C/D. Otherwise, to
including SRP IND limit splitting of codes to 6/7
were routed to digits, information about upto
Bangalore Central which level analysis is required
TAX. (e.g. 0802538) can also be
intimated.
6 C/D is AXE TAX ; IN call is not successful With PTX not NTSR at E,
PTX=NTSR at E- Answer message is received by
TAX AXE TAX and IN call is
successful.
7 Call from SSP to For every call to SRP, there This is due to not sending calling
SRP, routed via are two sets of C7 messages line id & category from SSP.
EWSD TAX with Headers 03 & 04. These additional 4 messages per
(For calls through OCB call is increasing load on PUPEs.
TAXs, one set of 03 & 04
messages.)
8 PTX=NTSR at SSP All SRP calls are treated as With PTX=0 at SSP, SRP calls
successful (with CE=0 in are treated as effective only
OFCLA) when Answer message is
received from SRP.
9 OCB TAX is SSP; All 1602 calls from OCB At TAX SSP, 1602425 was
1602425 was routed Local failed suddenly. After analysed in TRAD 6. When
from OCB Local to routing through ACH with ARCMO was done to modify
TAX thro common FITX, calls were getting OK NTRA06 & TRCHBL, OCB SSP
trunk group with since charge message was TAX started sending Charge
PTX=0; calls OK. received from SSP TAX. message.

Conclusion:
a) For SRP-IND, PTX=0 at SSP and normal PTX (except NTSR) at all TAXs is
found better.
b) Spare code as SPR-IND and routing as it is upto Lev-1 TAX helps to route to
correct TAX without splitting of INDs at intermediate TAXs.

(A.K.KALAIARASU)
DE, RMC, Chennai

Page 2 of 2