IN - PCO
Present Scenario:
To allow only the 160244 rout from the PCO , we don’t have
a direct method in the CDOT switches working with 2_1_1_1 software.
Hence a round about method was developed and PCOs are working.
Proposed
Scenario:
Presently 2_2_1_4 and 2_2_1_6 software are available and
mostly all the C-DOT Exchanges are working with either 2_2_1_4 or
2_2_1_6. In this software a new facility ‘category based charging’
is available , mostly all the officers working with C-DOT might be
knowing. And also , now we are having different SCPs in our network
and each one should be accessed.
A customer buying
a ITC card from Lucknow, should be able to use at Tamilnadu. To
enable this facility 1602 routes pertain to all the SCPs are to be
made available from the PCO.
Procedure at
C-DOT Switches:
Category Based Charging is to be introduced in your Exchange.
2_2_1_4 or 2_2_1_6 software Release highlights may be referred or
details available at site:www.geocities.com/cdot_pandian.
For
example category ‘16’ is assigned to PCO Directory Number. In the
Sub-charge table make ‘cat 16’ to ‘cat 1’ and ‘cat 16’ to ‘cat 21’
if given for other PCOs as invalid , using the command ‘mod-sub-crg’.
In the 1602 routes , allow the category 16 and give no-mtr for this
category in the ‘cre-rout’ command. In this condition dial tone will
be available in the IN-PCO , and a user can dial any of the required
1602 rout as per his requirements. Other than 1602 , no rout should
be allowed for category 16 in your system. Other than 1602 , user
will not get ant other service from this Phone.