2_2_1_6 Problems and solutions Page of M.Pandian

This software has been introduced mainly for the introduction of V 5.2 Protocol, for the implementation of AN-RAX and other Access Networks for WLL services. Category based charging and priority based switching is made possible for the implementation of TRAI plan and CCB PT provisions.

The following are the field problems faced with this 2_2_1_4 s/w.

1. BP message Buffer over load’ message in the OOD and at the same time blocking of C7 free circuits towards TAX exchange. After some time blocking becomes normal.

NOTE: A private patch ‘salum’ has been released and installed and found ok.

2. Answering circuit (161) is not accessible in C7 routes. Hence testing becomes difficult for the Trunk circuits from Tax exchange.

NOTE: This is being taken care in 2_2_1_6 software.

3. IOP sync problem: If more than 2 months BC is available, sync does not complete.

NOTE: Due to the volume of ‘bc’ and ‘tgcbr’ files are large, failure occurs ; Keep minimum one month data and delete others after taking back up before sync.. Any how, it is being taken care in 2_2_1_6 software.

4. The newly introduced ‘tcntr??$$.dat’ files are not deleted , while ‘bc’ deletion is done. The file ‘tcntr’ is not put in the ‘bc.grp’ list in the ‘$GRP’ directory.

NOTE: The ‘tcntr??$$.dat’ line should be introduced in the ‘bc.grp’ file in the $GRP directory and then ‘del-fgp-file’ command may be executed.

5. After the introduction of IUC the ‘tgcbr’ records become large and it is requested that a separate ‘tgcbr’ back up group may be created and ‘tgcbr’ should be taken on separate Cartridge.

NOTE: In the $GRP directory , ‘tgcbr.grp’ file may be created and separate back up can be taken accordingly.

6. ‘Directory Number not OOS’ report during data modification at BM/RBM numbers. A stable clear to the BM / RBM is to be given or sometime stable clear to the AM is needed.

NOTE: This problem is not solved and still testing is going on at the lab and the result is awaited; till such time the above method is to be followed.

7. Some numbers go without ‘Dial Tone’ (No Dial Tone) ; ‘displ-trm-status’of the number is ‘ins-free’, but ‘displ-call-info’ report says that number is ‘CP Busy’ or ‘os-call-bsy’. Only a stable clear to the BM solves the problem.

NOTE: This problem has been solved in the next s/w release 2_2_1_6.

8. AN – RAX stability.

NOTE: After the Rel 13 version EPROM (U2 = E89E & U20 = FCF5)for ARC card the stability has been improved. Any how still R&D is going on to improve the stability and would be solved in 2_2_1_6 with 5.2 patch release.

9. Maximum number of TGPs put in one CGS- Limitation: At present only 10 TGPs can be put in one CGS. NLDO and IUC implementation necessitate the scenario for additional TGPS in a given CGS.

NOTE: This is being implemented in the next s/w release.

10. Calls made to ‘NO-MTR’ subscriber is not metered in case of a local call (Intra Exch Call) and call does not disconnect after 60 seconds. But calls made to the same subscriber via a TGP (Inter Exch Call) gets metered.

NOTE: This is the implementation done in the system.

11. BNP modification is not effective for a ‘password tampered’ subscriber.

NOTE: This has been solved in 2_2_1_6 s/w. Any how those who are having 2_2_1_4 s/w , care should be taken while doing the disconnection.

12. Special service access code ‘1251’ is allotted for IVRS connectivity. But ‘125’ is used for activation code for ‘call diversion’ and this is to be rearranged.

NOTE: Change of special service code is done in the 2_2_1_6 s/w and Lev 125 is released for other services. Those who are working on 2_2_1_4, the option is to go for 2_2_1_6 or to have a private patch installed for solving this problem.

13. Insulation Resistance on AB lines is reported to be ‘zero’ during a ‘tst-trm’ command with ‘102’ test for external plant.

NOTE: The EPROM used in the 2_1_1_1 s/w , at U3 position , the value being D32F may be used in this s/w also.

14. ‘10 Digit’ CLI is the National Policy; But presenting the CLI with ‘0’ will be very convenient for redialing feature in a ‘CLI’ phone and in ‘Mobile Stations’(Cell Phone)

NOTE: This is being implemented in the s/w 2_2_1_6.

15. Error Message in the IOP console: %% SIF: error in delete mcp_file-one Reason: Error in isread

NOTE: The process ‘sif’ is to be recreated. Otherwise the subscribers who are not able to do any of the ‘sub initiated features’ should be reset for the particular feature. This can be done on receipt of complaint only.

16. Error Message in the IOP console: Msg [msgsend] : Either destination Q full or message free pool null.

NOTE: Any updation problem in the IOP will be indicated by this message. Immediately the IOP should be brought to warm state and taken to cold state and reset, boot and then sync with the active IOP.

17. Random occurrence of single unit charges on Lev 9 / 0 calls :
On verification it is noticed that , if closed numbering scheme is done for
Lev 9 route, this problem happens and after making open numbering, the above problem does not occur. It is recommended that only open numbering is to be done for Lev 9 and Lev 0 routes.(In the ‘cre-rout’ command , the value of parameter ‘dgt-len’ should be default ,ie 20).

18. Incoming calls made to ISDN subscriber are not incremented in ‘ Incoming TGP counter’. Hence a loss in the IUC bill.

NOTE: This has been solved in the next s/w release 2_2_1_6 and found alright.

19. Lev 1 rout could not be deleted and ‘displ-rout-char’ command shows an error report; ‘can`t read from file’

NOTE: The rout-code file ‘apdatb’ would have been corrupted. Using ‘datpat’ utility the value ‘da_dgt_flag’ in the ‘apdtab’ file should be modified as ‘0’ . Remedy: Special service route on Lev 1 is to be created with open numbering (dgt-len=20) and then modify for the required value 3 or 4 as the case may be , using ‘mod-rout-char’ command.

20.160244’ calls are not getting through from CDOT 256 RAX and SBM exchanges via MBM exchange working with 2_2_1_4 s/w. (mod-r2…c7 link)

FIELD PROBLEMS FACED AT 2_2_1_6 S/W IN C-DOT SYSTEMS

The important field requirements of Lev 9 sub-og-barring, Lev 9 detailed bill records and enhanced number of links towards AN-RAX per BM (14 links per BM) have brought the s/w release 2_2_1_6. This has been taken as field trail at Salem area and Four exchanges were retrofitted with the new release and feedback given to C-DOT.

Immediately after the retrofit is over, it has been noticed that some of the incoming call records in the i/c TGP of POI, the calling line id is missing. And ‘ BP message buffer over load also takes place in one or two sites and the same has been reported to C-DOT Bangalore.
A private patch ‘pune4’ has been released by C-DOT Delhi, and the same has been installed and the ‘CLI’ problem have been solved.

The other problems faced are listed below.

1. ‘add-cal’ command is not working in Duplex IOP mode. An error report : misc error (93,2) updation failure in mate ‘iop’.

NOTE: Lab testing is going on and solution is expected.

2. ‘mod-xcod’ command is also not working in IOP Duplex mode.

NOTE: Nullify the ‘abexcd.lok’ file in both IOPs and create the XCOD.

3. ‘Dialing by equipment’ feature is not working for trunk circuits; ‘1682 <TEN><directory number>’. It was told that a trunk circuit to be added in the ‘dbe’ list using the command ‘mod-trk-obs’ and this is also not working.

NOTE : Presently we are using only 4.5 patch release; In the 5.2 patch release this will be solved.

4. SSC Problem: Diagnostics of ‘SS’ could not be done; If done, the standby SSC goes to suspect and the diagnostics get aborted.

NOTE : This is to be verified in the next patch release only.

5. Subscribers could not be put under origination / termination observation, using the command ‘mod-sub-obs’ in some BMs. Probably the ‘iotslm’ file could have been corrupted. Using the ‘datpat’ utility this ‘iotslm’ file could not be accessed in 2_2_1_6 s/w version.

NOTE: Very rarely this problem occurs; If any body feels this problem , they can get the on line help of CDOT Bangalore.

6. “bpmcp” file gets corrupted at some sites. Observation: When a stable clear or soft start is given to a BM, the BM does not restore. The ‘bpmcp’ file is to be generated and copied and then only the BM restores.

7. Error message in the active IOP console regarding bpmcp??.dat.

NOTE: Item 6 and 7 are being taken care in the next patch release.

8. The ‘DTK’ equipped in the card slot ‘21’ at ‘ti13’ TU is giving problem for AN-RAX working. If ‘X-1-4-21’ is equipped for AN-RAX, only 8 simultaneous calls is possible with a LTG connected to the AN-RAX. If the DTK is used for any other ‘CAS’ or ‘CCS’ trunk the 32nd port goes with one way speech.

NOTE: This problem is made over to CDOT Delhi; It is advised not to use this DTK for AN-RAX purpose.

9. In general, AN-RAX stability is to be improved.

NOTE: The C-DOT 256 RAX is working fine with other switches like EWSD and OCB. It is unfortunate that it is not stable with C-DOT Local Exchange. A private patch has been developed and field trail is going on and shortly solution is expected.

10. BMON utility for 2_2_1_6 is requested.

11. In the ‘ti01, 02, 03 and 04 group, some of the calls towards other BM is of one way speech or noisy. It is noticed that time slot number 402, 422, 442, 462 are having the problem of one way speech or noisy.

NOTE: A hot patch ‘mbmrsu’ has been released and installed and the one way speech problem has been solved.

12. A combined patch including the ‘CLI Problem and One way speech’ has been installed and tested , and both the problems have been solved. But the answering circuit problem is raised once again and the same has been brought to the notice of CDOT Delhi..

13. While executing create space under ‘utility’ , the ‘TEMP’ directory is not getting removed; only after removing the ‘result.out’ files manually , the create space for removing ‘TEMP’ directory is possible.

NOTE: This is the limitation of file system.

14. Sometime , after doing this create space utility, typing of characters are not printed on the screen;

NOTE: After executing ‘stty echo’ command, the screen is restored or logout and login again.

15. A ‘rgen’ utility may be prepared for finding out the ‘rout code’ and associated ‘tgp’ choices and ‘charge rate numbers’ with category.

NOTE: C-DOT will prepare a utility for this requirement.

16. Error Message in the IOP console: Msg [msgsend] : Either destination Q full or message free pool null.

NOTE: Any updation problem in the IOP will be indicated by this message. Immediately the IOP should be brought to warm state and taken to cold state and reset, boot and then sync with the active IOP.

17. The ‘os-call-busy’ status of the subscriber still continues in this s/w also.

NOTE: Better solution is expected in the 5.2 patch release. Till such time give a stable clear to the particular BM and solve the problem.

18. Whenever a deletion and creation of any directory number is made, ‘ displ-xchg-mtr’ shows excess reading than the actual. While tallying the BM wise meter reading using ‘ rgen submtr2_2’ this was noticed.

NOTE: Problem is made over to R&D wing of Delhi C-DOT .

19. The NCBR and TGCBR files are not getting deleted while ‘del-fgp-file’ command is executed.

NOTE: It will be cleared in the 5.3 patch release.

Home Profile Helpline FAQ Photo News Thoughts	FIELD PROBLEMS FACED WITH 2_2_1_4 SOFTWARE IN C-DOT SYSTEMS This software has been introduced mainly for the introduction of V 5.2 Protocol, for the implementation of AN-RAX and other Access Networks for WLL services. Category based charging and priority based switching is made possible for the implementation of TRAI plan and CCB PT provisions. The following are the field problems faced with this 2_2_1_4 s/w. 1. BP message Buffer over load’ message in the OOD and at the same time blocking of C7 free circuits towards TAX exchange. After some time blocking becomes normal. NOTE: A private patch ‘salum’ has been released and installed and found ok. 2. Answering circuit (161) is not accessible in C7 routes. Hence testing becomes difficult for the Trunk circuits from Tax exchange. NOTE: This is being taken care in 2_2_1_6 software. 3. IOP sync problem: If more than 2 months BC is available, sync does not complete. NOTE: Due to the volume of ‘bc’ and ‘tgcbr’ files are large, failure occurs ; Keep minimum one month data and delete others after taking back up before sync.. Any how, it is being taken care in 2_2_1_6 software. 4. The newly introduced ‘tcntr??$$.dat’ files are not deleted , while ‘bc’ deletion is done. The file ‘tcntr’ is not put in the ‘bc.grp’ list in the ‘$GRP’ directory. NOTE: The ‘tcntr??$$.dat’ line should be introduced in the ‘bc.grp’ file in the $GRP directory and then ‘del-fgp-file’ command may be executed. 5. After the introduction of IUC the ‘tgcbr’ records become large and it is requested that a separate ‘tgcbr’ back up group may be created and ‘tgcbr’ should be taken on separate Cartridge. NOTE: In the $GRP directory , ‘tgcbr.grp’ file may be created and separate back up can be taken accordingly. 6. ‘Directory Number not OOS’ report during data modification at BM/RBM numbers. A stable clear to the BM / RBM is to be given or sometime stable clear to the AM is needed. NOTE: This problem is not solved and still testing is going on at the lab and the result is awaited; till such time the above method is to be followed. 7. Some numbers go without ‘Dial Tone’ (No Dial Tone) ; ‘displ-trm-status’of the number is ‘ins-free’, but ‘displ-call-info’ report says that number is ‘CP Busy’ or ‘os-call-bsy’. Only a stable clear to the BM solves the problem. NOTE: This problem has been solved in the next s/w release 2_2_1_6. 8. AN – RAX stability. NOTE: After the Rel 13 version EPROM (U2 = E89E & U20 = FCF5)for ARC card the stability has been improved. Any how still R&D is going on to improve the stability and would be solved in 2_2_1_6 with 5.2 patch release. 9. Maximum number of TGPs put in one CGS- Limitation: At present only 10 TGPs can be put in one CGS. NLDO and IUC implementation necessitate the scenario for additional TGPS in a given CGS. NOTE: This is being implemented in the next s/w release. 10. Calls made to ‘NO-MTR’ subscriber is not metered in case of a local call (Intra Exch Call) and call does not disconnect after 60 seconds. But calls made to the same subscriber via a TGP (Inter Exch Call) gets metered. NOTE: This is the implementation done in the system. 11. BNP modification is not effective for a ‘password tampered’ subscriber. NOTE: This has been solved in 2_2_1_6 s/w. Any how those who are having 2_2_1_4 s/w , care should be taken while doing the disconnection. 12. Special service access code ‘1251’ is allotted for IVRS connectivity. But ‘125’ is used for activation code for ‘call diversion’ and this is to be rearranged. NOTE: Change of special service code is done in the 2_2_1_6 s/w and Lev 125 is released for other services. Those who are working on 2_2_1_4, the option is to go for 2_2_1_6 or to have a private patch installed for solving this problem. 13. Insulation Resistance on AB lines is reported to be ‘zero’ during a ‘tst-trm’ command with ‘102’ test for external plant. NOTE: The EPROM used in the 2_1_1_1 s/w , at U3 position , the value being D32F may be used in this s/w also. 14. ‘10 Digit’ CLI is the National Policy; But presenting the CLI with ‘0’ will be very convenient for redialing feature in a ‘CLI’ phone and in ‘Mobile Stations’(Cell Phone) NOTE: This is being implemented in the s/w 2_2_1_6. 15. Error Message in the IOP console: %% SIF: error in delete mcp_file-one Reason: Error in isread NOTE: The process ‘sif’ is to be recreated. Otherwise the subscribers who are not able to do any of the ‘sub initiated features’ should be reset for the particular feature. This can be done on receipt of complaint only. 16. Error Message in the IOP console: Msg [msgsend] : Either destination Q full or message free pool null. NOTE: Any updation problem in the IOP will be indicated by this message. Immediately the IOP should be brought to warm state and taken to cold state and reset, boot and then sync with the active IOP. 17. Random occurrence of single unit charges on Lev 9 / 0 calls : On verification it is noticed that , if closed numbering scheme is done for Lev 9 route, this problem happens and after making open numbering, the above problem does not occur. It is recommended that only open numbering is to be done for Lev 9 and Lev 0 routes.(In the ‘cre-rout’ command , the value of parameter ‘dgt-len’ should be default ,ie 20). 18. Incoming calls made to ISDN subscriber are not incremented in ‘ Incoming TGP counter’. Hence a loss in the IUC bill. NOTE: This has been solved in the next s/w release 2_2_1_6 and found alright. 19. Lev 1 rout could not be deleted and ‘displ-rout-char’ command shows an error report; ‘can`t read from file’ NOTE: The rout-code file ‘apdatb’ would have been corrupted. Using ‘datpat’ utility the value ‘da_dgt_flag’ in the ‘apdtab’ file should be modified as ‘0’ . Remedy: Special service route on Lev 1 is to be created with open numbering (dgt-len=20) and then modify for the required value 3 or 4 as the case may be , using ‘mod-rout-char’ command. 20.160244’ calls are not getting through from CDOT 256 RAX and SBM exchanges via MBM exchange working with 2_2_1_4 s/w. (mod-r2…c7 link) FIELD PROBLEMS FACED AT 2_2_1_6 S/W IN C-DOT SYSTEMS The important field requirements of Lev 9 sub-og-barring, Lev 9 detailed bill records and enhanced number of links towards AN-RAX per BM (14 links per BM) have brought the s/w release 2_2_1_6. This has been taken as field trail at Salem area and Four exchanges were retrofitted with the new release and feedback given to C-DOT. Immediately after the retrofit is over, it has been noticed that some of the incoming call records in the i/c TGP of POI, the calling line id is missing. And ‘ BP message buffer over load also takes place in one or two sites and the same has been reported to C-DOT Bangalore. A private patch ‘pune4’ has been released by C-DOT Delhi, and the same has been installed and the ‘CLI’ problem have been solved. The other problems faced are listed below. 1. ‘add-cal’ command is not working in Duplex IOP mode. An error report : misc error (93,2) updation failure in mate ‘iop’. NOTE: Lab testing is going on and solution is expected. 2. ‘mod-xcod’ command is also not working in IOP Duplex mode. NOTE: Nullify the ‘abexcd.lok’ file in both IOPs and create the XCOD. 3. ‘Dialing by equipment’ feature is not working for trunk circuits; ‘1682 <TEN><directory number>’. It was told that a trunk circuit to be added in the ‘dbe’ list using the command ‘mod-trk-obs’ and this is also not working. NOTE : Presently we are using only 4.5 patch release; In the 5.2 patch release this will be solved. 4. SSC Problem: Diagnostics of ‘SS’ could not be done; If done, the standby SSC goes to suspect and the diagnostics get aborted. NOTE : This is to be verified in the next patch release only. 5. Subscribers could not be put under origination / termination observation, using the command ‘mod-sub-obs’ in some BMs. Probably the ‘iotslm’ file could have been corrupted. Using the ‘datpat’ utility this ‘iotslm’ file could not be accessed in 2_2_1_6 s/w version. NOTE: Very rarely this problem occurs; If any body feels this problem , they can get the on line help of CDOT Bangalore. 6. “bpmcp” file gets corrupted at some sites. Observation: When a stable clear or soft start is given to a BM, the BM does not restore. The ‘bpmcp’ file is to be generated and copied and then only the BM restores. 7. Error message in the active IOP console regarding bpmcp??.dat. NOTE: Item 6 and 7 are being taken care in the next patch release. 8. The ‘DTK’ equipped in the card slot ‘21’ at ‘ti13’ TU is giving problem for AN-RAX working. If ‘X-1-4-21’ is equipped for AN-RAX, only 8 simultaneous calls is possible with a LTG connected to the AN-RAX. If the DTK is used for any other ‘CAS’ or ‘CCS’ trunk the 32nd port goes with one way speech. NOTE: This problem is made over to CDOT Delhi; It is advised not to use this DTK for AN-RAX purpose. 9. In general, AN-RAX stability is to be improved. NOTE: The C-DOT 256 RAX is working fine with other switches like EWSD and OCB. It is unfortunate that it is not stable with C-DOT Local Exchange. A private patch has been developed and field trail is going on and shortly solution is expected. 10. BMON utility for 2_2_1_6 is requested. 11. In the ‘ti01, 02, 03 and 04 group, some of the calls towards other BM is of one way speech or noisy. It is noticed that time slot number 402, 422, 442, 462 are having the problem of one way speech or noisy. NOTE: A hot patch ‘mbmrsu’ has been released and installed and the one way speech problem has been solved. 12. A combined patch including the ‘CLI Problem and One way speech’ has been installed and tested , and both the problems have been solved. But the answering circuit problem is raised once again and the same has been brought to the notice of CDOT Delhi.. 13. While executing create space under ‘utility’ , the ‘TEMP’ directory is not getting removed; only after removing the ‘result.out’ files manually , the create space for removing ‘TEMP’ directory is possible. NOTE: This is the limitation of file system. 14. Sometime , after doing this create space utility, typing of characters are not printed on the screen; NOTE: After executing ‘stty echo’ command, the screen is restored or logout and login again. 15. A ‘rgen’ utility may be prepared for finding out the ‘rout code’ and associated ‘tgp’ choices and ‘charge rate numbers’ with category. NOTE: C-DOT will prepare a utility for this requirement. 16. Error Message in the IOP console: Msg [msgsend] : Either destination Q full or message free pool null. NOTE: Any updation problem in the IOP will be indicated by this message. Immediately the IOP should be brought to warm state and taken to cold state and reset, boot and then sync with the active IOP. 17. The ‘os-call-busy’ status of the subscriber still continues in this s/w also. NOTE: Better solution is expected in the 5.2 patch release. Till such time give a stable clear to the particular BM and solve the problem. 18. Whenever a deletion and creation of any directory number is made, ‘ displ-xchg-mtr’ shows excess reading than the actual. While tallying the BM wise meter reading using ‘ rgen submtr2_2’ this was noticed. NOTE: Problem is made over to R&D wing of Delhi C-DOT . 19. The NCBR and TGCBR files are not getting deleted while ‘del-fgp-file’ command is executed. NOTE: It will be cleared in the 5.3 patch release.	2_2_1_6 s/w with 5.3 Patch is available at C-DOT Bangalore.