Download Field Problems Reported at Workshop on C

Name of the Site/Circle : RMC, Chennai
S.No.
Problem Detail
1.
R2
A
C-DOT
Local
Solution/Comments
As per standard, only leading TAX should handle the call link by
link, while all other TAXs/LE nodes should do signalling end to
end.
B
C
D
C-DOT
TAX
OCB
TAX
GDS
Call analysis at the site only can decide the exact cause.
In open numbering working, call was successful only with
following conditions :
a)
`A' exchange was made `leading' by making TGP type at `B' as
TTAX and
b)
`B' was defined as parented local exchange at `C' (i.e. C was
sending charging to B).
Both a & b above are non-standard arrangements. How to solve
the problem.
2.
R2
A
B
OCB
TAX
C-DOT
MBM
R2
This is a case of wrong data creation. For I/C call from TAX and
'going to parent station 'C', crg-rtn as 'PRD-TAX' causes confusion
in the software as neither pulses are required to be sent or to be
received. So only 'No-Mtr' crg-rtn should be used.
C
RAX
In the above case, if CRG RTN was defined as 1 (i.e. PRD-TAX) for
the I/C TGP at B for the ROUTE to C, about 40% calls were
getting disconnected (busy tone) when called party answered.
When CRG RTN 4 (NO-METR) was given, there was no problem.
What is the reason ?
- 14 -