Download Field Problems Reported at Workshop on C

S.No.
Problem Detail
Solution/Comments
10.
ROD should be ROUTE specific instead of TGP specific to enable
sending different calls through same TGP.
Suggestion is noted.
11.
CAMA should be ROUTE specific instead of TGP specific. This is
required in GDC to pre-collect CLI only for 0&95 levels.
Suggestion is noted.
Name of the Site/Circle : Narsingpur (M.P.)
S.No.
Problem Detail
Solution/Comments
1.
`VCC' calls on route `160233' not accessible by 256 RAX subscriber
directly parented to C-DOT MBM(XL)-TAX. He gets announcement "This facility is not currently available on your Telephone".
Site specific but related to improper data creation.
2.
Spurt in metering observed on subscribers of SBM/MBM connected
to Level 2 TAX (C-DOT-XL) on MOD-R2, while further
connectivity from C-DOT-TAX-XL to Level-1 TAX is on CCS7.
This happens, when terminating exchange extends some metering
pulse along with answer and specially when 'EWSD' TAX is in the
chain. Solution is to re-define data at terminating exchange to
extend 'ANS' only. i.e. putting a 'NON-MTRD' 'crg-rtn' with ANSEXP'.
3.
It is observed in LM Rack, when a call is already on & reset is
given to Active TIC of that `TU', the call remains in progress &
hence protected by the standby TIC. But if the active TIC to the
next TU of the same concentration chain is given reset, the
established calls in TU get cut. Why this is so ?
To be verified.
Name of the Site/Circle : Rajgarh, Alwar (Raj)
S.No.
Problem Detail
Solution/Comments
1.
Dynamic Lock is required for `95' barring. At present barring is
made effective by priority, but this diallows `IN' service also for
`LE' subscribers of SSP at Bhiwadi.
Priority should not be used for 95 barring. So there is no solution
at present for such a problem.
2.
In 2_2_1_3 (2.10) S/W, IOP synchronization problem is very
severe.
Solution will be provided in subsequent S/W release (2_2_1_4).
- 16 -