. QUE edi d ddl e lees ees sb | Go System atste ii Suge Practices C-DOT MAX-NG ACCEPTANCE TESTING (Line Access Gateway Unit) (LAGU) ©2014, C-DOT Printed in India| a System = 2 Sure Practices C-DOT MAX-NG ACCEPTANCE TESTING (Line Access Gateway Unit) (LAGU) © 2014, C-DOT Printed in India bbe ed ddd ddd b luce esse LULL |Table of Contents Chapter 1. Line Access Gateway (LAGU)... 11. INTRODUCTION Chapter 2. Conformity Check. 2.1, DOCUMENT 2.2, HARDWABB ween. 23, SOFTWARE vocceceonce Chapter 3. Cabling and Power Distribution Checks... 31. CABLING Chapter 4. Line Access Gateway Unit Tests. 41. Prerequisite. 4.2. Power -ON Test. 43. Call Testing 44. FEATURE TESTIN( 4.5. Administrative features. 4.6. Maintenance‘Related Test. 4.7, Performance Report evn 48 Automatic changeover of linkiLink redundancy (Test Case 42)... 49 System reboot test (Test Case 48).. 4.10 System Backup (Test Case 44) i 4.11 View port status and activation and deactivation ports (Pest Case 45) 412 Dial Tone/Ringing Tone/Ring back Tone checking. (Test Case 46). 4.13. Voltage in subseriber line test (Test Case 47) 4.14 Check for QOS (Test Caso 48 7 4.15 Check for Ethernet test (Test Case 49)... i 25 4.16: ‘Transaction log tost_ Tost Case 60). 417 PCO call Test, (Test Case S1)..roec---n 4.18. Voltage drop test (Test: Case 52) 4.19. Partial Dial Test (Test Case 53). ae 4.20. Test for connectivity from LAG to PR , DR Soft Switch and LIS server (Test Case 54)27 421 IPvé Test caso (Test Case 55)... 422 Load Test (Test Case 56) i ‘H:\HOME \NG-MAX\User\C-DOT_MAXNG_AT-LAG.doe December 29, 2014 b & tly to eo i i? i ie i ee elddilldd a, Yrandes pth hbe egy ce GM (RA) rized Leeder OF Ase Om NCnGn Che uO C-DeTChapter 1. Line Access Gateway (LAGU) 1.1. INTRODUCTION ‘The Line, Access Gateway is the Main component for the MAX-NG (Next Generation) Network upgradation, which provides the IP domain access to the existing C-DOT MAX subscriber lines. Tt acts as Gateway for interfacing to IP network. It caters analog Voice to IP packet conversions. It is mainly responsible for the conversion of the time division multiplexed (TDM) voice circuits to voice packets. 12 ARCHITECTURE OVERVIEW ‘The bulk part of existing DSS-MAX hardware is Terminal Unit (ATU) in which subscribers lines are connected. In MAX-NG architecture this ATU hardware is retained. LAG is implemented by connecting the Terminal Units (ATU) to NGTI Card which acts as a Gateway for interfacing with IP network. NGTJ card is capable of converting time division multiplexed (TDM) voice circuits to IP packets and vice versa. These IP packets are delivered over Ethernet links to IP network.Thus Line Access Gateway (LAG) basically consists of Line TUs, TSI and Access Gateway Module (NGTJ). Both the NGTJ cards are installed in a newly designed two slot cabinet. ‘The view of LAGU will be as follows in EMS terminal ‘This document contains total 56 numbers of tests for AT of LAGU oe eee re eee eee Choy a) Ws Ppt Sh sro Wyse Aeey, "TANCE TESTING (ACC!— Bee = hl nie 7 OR = im) Le | : a Cddb ddd lub eeeddddd| VPOaoaL”Y dull ddddudddiuu ell lldd Chapter 2. Conformity Check BE 2.2, 23 DOCUMENT ‘Test Case 1: Ensure that the dispatched hardware is as per dispatch list, Test Case 2: Ensure that the softeopy of documents is as per the list HARDWARE Test Case 3: i Check the LAGU hardware physically whether any damage is there. All the cards should be in good condition. The LAGU consists of * Two slot cabin + Two NGTJ cards (NGTJ-A00) © LAN cable set to interface with IP network * Power cable set. ‘Test case 4: ii, Ensure that the proper cable markers have been put on various cables as per installation document Test Case 5: Hi Cheek that LAGU is connected as per the approved connectivity diagram Note! Interface cable between new NGTJ card and TIC will be same as that used presently between TIC and TSU frame. SOFTWARE Test Case 6:Verify the software release version of LAG. Test Case 7:Verify the IP address marking on LAG Hardware as per the IP address list for that site. Test Case 8:Verify the MAC Addresses marking on LAG Hardware a nO efi ehde ; come domeuieieChapter 3. bb Cabling and Power Distribution Checks 3.1. CABLING Test Case 9° Check for the following type of cables. + Subscriber cables from LAGU unit to DDF frame already existing and no change will be there. + Ethernet cables from 2 slot cabin to the CACU system as per installation document. + 48V power cables from BUS bar of the racks to different LAGU system cold dddddddbbuuecl dd ddide :Chapter 4. Line Access Gateway Unit Tests 4.1, PREREQUISITE 411. Network Elements 1. Line Access Gateway (LAG) is installed and dial tone is available on the LAG Subscribers. LAG is discovered in EMS LAGU System 1. Hardware is installed and powered up with backup power. 2. Application SW is installed on LAG 2, Client Terminal is connected to LAG 412. Client Terminal 1. Linux Machine 2, Firefox Browser installed 42. POWER-ON TEST: 4.2.1. Power Supply and distribution (Test Case 10) Objective ‘To check the Power supply and distribution Test Procedures ‘* The LAG chassis is powered up using two “48 v input. All the LEDs of hoth the LAG card will be ON. Switch off one input -48 V source. | Expected Results « All the LEDs of both the LAG card “willl be ON. Both LAG card should get the input power. [Results 1Passed Pailed i f a a Se ra BD _R mont’ Was “fb s ‘CDOT DSS MAX-NG CUE L EEL esc ee ee ess Lh hbk |ebb b ddd b dbo bebe sess shhh bbl Chapter 4 - 4.2.2. Power Redundancy (Test Case 11) Objective To check the uninterrupted functionality of LAG using redundant power supply Test Procedures i, The LAG chassis is powered up using two -48 v input. All the LEDs of both the LAG card will be ON, | ii Make a sample call from one subscriber to another subscriber. iii. Switch off one input -48 V souree. iv, The call shall continue after power supply switch off. | v. Now switch ON the -48 V source. Repeat the above by | switching off the other power supply source Expected Results |The call shall continue after power supply switch off. Reaulta Passed Pailed 428 Login in to LAG System (Test Case 12) Objective To check the login into the system via. LAGEMS and SSH | (Secure login) Test Procedures | A) — Oo 3. Access EMS from thin client ii Check or Assign IP address as per site requirement. Procedure given in Installation document. iii, Open firefox browser and type the IP Addzoas of ems server with port no btn» x x:9090 username sxxxx pasewd ~ yyyy double click on LAG NODE Main menu will display. A topological view will be displayed showing various nodes in the | networks One * oa Mall Chey 10 \ ~~" c-DoT DSs MAX-NG|ATEWAY UNIT TESTS: B) From the client give ssh root@IP. LAG prompt should come id password is OK Expected Results | Login in to LAG is possible through LAGEMS and SSH Results | Passed | Failed 424 Details of LAG Configuration Verification (Test Case 13) Objective ‘To verify the details configured in LAG ] Test Procedures | In LAG GUI , go to configuration Menu >SYSTEMS> click “displ lag info” command Expected Results | Self IP address , mate LAG IP , DSP IP and Soft Switch IP should be shown in the table Results 1 Passed Failed 425 Verification of Date and“Time in LAG (Test Case 14) Objective ‘To verify the date and time in LAG Test Procedures | In LAG GUI , go to configuration Menu Miscellaneous > click “displ lag time” command Expected Results | Date and time shall match with core. Results Passed Failed 426 Software Version (Test Case 15) Objective To check Software version in LAG Test Procedures _ | Open the LAG GUI Go to configuration Menu > Miscellaneous displ lag release Expected Resulte | SW version shall be as per document or higher Release) Results Passed | Failed 427 Alarm Indication (Test Case 16) Objective ‘To verify alarm on the LAG Test Procedures Login into LAG ‘vid LAGEMS, ie fl. Qe Orns Nara \ i 1 a ACCEPTANCE TESTING (ACCESS)) 4 Chapter 4, Expected Resulis i. ii, iii, iv. iii, iv. Make one TIC card out of service using command “force unit oos” Again this TIC card make inserves using command “force Make one LAG card (standby one) out of service using command “force unit 00s” Again this LAG ecard mako inservice using command “force | unit ins” The colour of the TIC will become red and in alarm | window minor alarm is raised. Switch off one power supply in any ATU frame. Alarm will be cleared and for this TIC The colour of the LAG card will become red and in alarm =window minor alarm is raised. Alarm will be cleared and for this LAG card Results | Passed Failed 4.3. CALL TESTING 4.3.1. Intra-Lag Call (Test Case 17) Objective To verify Intra-LAG eal, Test Procedure Make sample call from one LAG subscriber to another subscriber of same LAG Expected Results ‘The call should be successful. Results O Passed OFailed 432. Inter-LAG Call (Test Case 18) Objective ‘To verify InterLAG call. Test Procedure Make a sample call from one LAG subscriber to another t= Piet WorGbe Ch. * CDOT DSS MAX-NG a |wl LINE ACCESS GATEWAY UNIT TESTS subscriber of another LAG Expected Results | The call should be successful. Results CO Passed O Failed 43.3. Originating Call to Mobile ( This test will be successful when all other nodes of MAX-NG will be functional like C4, TMG , SG) (Test Case 19) Objective To verify originating call to Mobile. Test Procedure Make a sample call from one subscriber to a mobile subscriber. Expected Results The call should be successful. Voice should be clear and there shall be no echo Results O Passed O Failed | 4.3.4, Originating Call to PSTN of Other Network (Test Case 20) | Objective To verify originating call to a PSTN of some other network. | Test Procedure Make a sample call from one subscriber toa PSTN subscriber Expected Results | Tho“eal] sould be successful. Voice should be clear and there shall be no echo Results 1 Passed O Failed 43.5. Terminating Call on LAG Subseriber (Test Case 21) Objective To verify terminating call on a LAG subscriber ‘Test Procedure Expected Results Results Make a sample call from a mobile phone/PSTN to LAG subscriber | The eall should be successful. |B Passed O Failed | 436. Announcements Test: + Subs. A,B, C: LAG Subscriber 43.6.1 Busy (Test Case 22) Objective To verify bu y eall announcements, Procedure Establish a sample eall betweon subseriber-A and subscriber B From subscriber C dial A Ahy pmentChapter 4, Expected Results | The subscriber-C should hear the busy announcement Results O Passed O Failed 43.6.2. __NoAnswer (Test Case 23) Objective To verify No answer announcements. Procedure From subscriber B dial A Do not pick up the call Expected Results After ring time out subscriber B should hear no answer announcement. Results O Passed O Failed 45.6.8. Out of Service (Test Case 24) Objective [ To verify out of service announcements Procedure | Change the subscriber status of subseriber-A to out of service using LAG EMS GUI. Go to configuration menu subscriber select subscriber | Dmodify line status select fre_line_oos > click modify status | | option Make a sample call from subscriber-B to subscriber-A. V Expected Results | The subscriber-B should hear the appropriate announcement. | Rosnits Oi Passed C1 Failed Emergency Call (Test Case 25) To verify emergency call. Procedure Call an emergency number from subseriber-A. | 100 Police | 101 Fire control service | 102 Ambulance | Expected Results | The eall should be successful. Results O Passed O Failed | 1 Ler’ * oe ee Cf heLINE ACCESS GATEWAY UNIT TESTS 43.8. Enquiry (Test Case 26) Objective | To verify enquixy calls. Procedure Call an enquiry number from su | 139 Railway Enquiry [198 _Bschange control room, | ful. Fnpected Results | The call should be nee Re: | as 44, FEATURE TESTING 441. CLIP (Test Case 27) Objective | To verily CLIP feature. | Procedure [Brom a subseribor Take a sample call to subscriber B.) Subscriber B should have CLIP display phone. | Expected Resulis [Tho call should be successful and A's jumber should display | B. Results [Passed O Failed | 442. Dynamic STD Barring (Test Case 28) Objective [To verily dynamic locking feature “| Procedure [From a subsoriber A dial °2 (where XXXK is the access 1 rrotword of A & & is the code for ancoss MPH sm Cal. | Mnnouncement “Your access is upto National call” is played. | sane a subscriber A, make a sample call to oo gbacbers | From a subseriber A dial *248KX81 (qhore XXXX is the acvess | password of A & 1 is the code for access upto Local call) | . Announcement “Your access is now $* to Local call” is played | Brom a subsenber “A. make a sample call to STD subseriber B | Fxpocted Results | The call should be successful. | | The call should fail & Announcement “Your access level does not | allow to use this facility” is played | a [DPassed fe Wert owe Wyse by ACCEPTANCE TESTING (ACCESS) ~C FailedChapter 4. 4.5, ADMINISTRATIVE FEATURES 45.1. Display subscriber Details (Test Case 29) Objective ‘To verify the command to find out subscriber details Procedure Go to configuration menu >subscriber >sclect subscriber from list >click detail option Expected Results | The result should display the details of the selected subscriber. Results O Passed O Failed 45.2. Display subscriber List (Test Case 30) Objective ‘To verify the total number subscribers created in the system with TEN(port number) Procedure Go to configuration menu > click subscriber option Expected Results | The result should display list of all subseribers with TEN. Results O Passed O Failed 45.3. Display System Parameter (Test Case 31) Objective To verify the system parameter configured in the system Procedure Go to configuration menu system >displ general params Expected Results | The result should display all the parameters configured in the system like country code , area code ete. [Results 1 Passed O Failed 4.5.4, Display Subscriber Status (LLO, Inservice ete) (Test Case 32) Objective To verify the various status of subscriber Procedure Go to configuration >Query line status query eclect LLO/INSIOPR ete submit query Expected Results | Result should display a List of LLO/INS/OPR subscriber, | Results O Passed O Failed Le peo Mpa — hy 16 CDOT DSS MAX-NGCbbddddddddddbuveceddddlidds LINE ACCESS GATEWAY UNIT“TESTS 4.6. MAINTENANCE RELATED TEST 4.6.1. Automatic Line Test (107 Test—Dial pad, loop current and loop resistance test) (Test Case 33) [ Objective To verify dial pad test of the telephone instrument and to verify Joop cuzreat and loop resistance test. Pre-requisite ‘TTC card should be in-service Procedure © Establish a conversation between A and B * Execute the test 107 from EMS Go to configuration menu Ssubseriber >select subscriber test linedselect test no 107 click Next + Dial all the digits of the phone To sce the teat report'- © Go to configuration menu Report select test option = test list->double click on required test Expected Results The test report should display all the reports of the tests | executed as mentioned (dial pad test jloop current and loop resistance). Results Passed O Failed 4.6.2. Automatic Line test (103 Test) (Test Case 34) Objective To verify line card side test (exchange side) Prerequisite | PTC card should be in-service and in working condition Procedure + Excoute the test 103 from EMS for any subseribor + Go to configuration menu subscriber >scleet subscriber Dtest line>select tost no 103 Selick Next To see the test report! Go to configuration menu Report select test option | test list Pdouble click on required test Expected Results | The result should display all the test measurements. Results Ol Passed Failed ACCEPTANCE TESTING (ACC#SS) LeaD ptr sue Wpdau hey ;Chapter 4 46.3. Objective Prerequisite T = To verily line side test (subscriber line side). | = TTC card should be in-service and in working condition “Automatic Line Test (102 Test—External Line Condition Test) (Test Case 35) > Execute the test 102 from EMS for any subseriber (s Procedure | physically eonnected to the line eard in detail option = Goto configuration menu >subscriber Dselect subseriber Stest Hine Dselect test no 102 (brief (Detail) >eliek Next ‘To cee the test report + Go to configuration menu Report select test option test list >double click on required test Expected Rewults | The result should display all the test measurements Results | oPassea 1 Failed 464. Ringer Test (Test Case 36) Objective To verify whether the ringer of the instrument is proper or not _| Prerequisite PTC card chould be in-service and in working condition Procedure Expected Results From a subsoriber dial 161. Ring back tone is heard. Now on hook the handset. Tmmediately system initiates a call to this phone and one can verify the ringing in the instrument, Results OPassed 1 Failed 465. Switchover Test (for TIC card)/Card redundancy (Test Case 37) Objective ‘To verify the redundancy of TIC card | Procedure «Make a sample call. | «Switchover the TIC card of the corresponding TU Go to chassis menu Right click on tic Smodify status >select switchover click next «The active one becomes standby and earlier standby one become active. Expected Results |The result should pass and the call shall continue after TIC Nps Sate (tie so DOT DSS MAX-NG| | Results 46.6. Switchovel Objective Procedure LINE ACCESS GATEWAY UNIT TESTS | switchover. ] |B Passed OPailed _! Test (for LAG card)/ Card redundancy (Test Case 38) | To verify the redundancy of LAG card + Make a sample call | * Give switchover to LAG card, | Go to chassis menu Right click on LAG —modify status select switchover click next * The active one becomes standby and earlier standby one become active Caution: LAG eard shall not be jacked out in running condition as it is LINUX based | + Jack out card tost: Properly shutdown the standby LAG. After that jack it out. Now jack the card again. The eard should come as standby. Expected Results The result should pass and the call shall continue after LAG switchover. Results Passed O Failed 46.7. Diagnostic Test (for TIC card) (Test Case 39) Objective Procedure | To verity the diagnostic test for TIC * Make one TIC card out of service. Go to chassis menu Right click on tic >modify status select frc_unit_oos>click next * Right click on TIC card in EMS and execute DGN command. * Go to chassis menu Right click on tic Selick run diagnostic option Expected Results Results ‘The result should display the diagnostic test report of the card O Passed O Failed ACCEPTANCE TESTING (ACCESS) Berrian Whsbies fyChapter 4. 4.6.8. Diagnostic Test (for LAG card) (Test Case 40) Objective To verify whether diagnostic test is working Ok for LAG card Procedure + Make one LAG card out of service | Go to chassis menu Right dick on LAG modify status->select frc_unit_cos click next + Right click on LAG card in EMS and exceute DGN command. * Go to chassis menu Right click on LAGS click Run diagnostic option Expected Results | The result should display the diagnostic tost report of she card Results O Passed Failed | 47. PERFORMANCE REPORT 471. Performance Report (Pest Ca8e 41) Objective ‘To verify the performance of the LAG system. Procedure Expected Results Open LAG GUI Click the Performance Menu in the EMS GUI. (Procedure — click on performance menu of GUI click traffic four option will be appeared) + Start Traffic report + Stop Traffic report + Display Active - View Report Click the Start Option with input Parameters Start Date & Time Stop Date &Time Polling Interval(15 sec) (Check for the report after 30 min after start of traffic report) Traific report will be displacd. Click on performance menu ~click on traffic click on view BER Jntaader wo Was dae “ chor pss Max-Na hyLINE ACCESS GATEWAY UNIT TE: | 7eport double click on latest report Capper to lower) Command should get executed and tral in new window, Report should display Number of e: reason and successful ffie report will be opened all attempts, Call failure q 49 SYSTEM REBOOT TEST (TEST CASE 43) Resulis 1 Passed O Failed “8 AUTOMATIC CHANGEOVER OF LINK/LINK REDUNDANCY (TEST CASE 42) Objective To check of automatic changeover of Ethernet link ] Procedure Make a sample call & then remove one lthernet interface from the chassis, | Call shall continue. | Verily the corresponding alarm [Expected Results | Callshallcontinue Results O Passed D Failea Objective [ Check of restoration of LAG hy system hoot Procedure SSH to LAG. Go to ete directory and give lag shutdown command. Once system goes down give lag restart command. | Expected Results | The system should eome up without any problem.. Make a new sample call and it should be OK. (Take the screen shot of reboot messages from thin client ifone wants) Resulis |B Passed O Failed | ACCEPTANCE TESTING (ACCESS) ent Roy oe Mee ie (f., U1eo Chapter 4. 4.10 SYSTEM BACKUP (TEST CASE 44) f Objective ‘To test the data backup of LAG. Procedure In EMS select the node and right click . Click backup. Message will come that backup is successful. Expected Results | Backup should be OK. Results O Passed O Failed 4.11 VIEW PORT STATUS AND ACTIVATION AND DEACTIVATION OF PORTS. (TEST CASE 45) Objective |_ Chee the port status Procedure In EMS select the card for which port status to be verified. Right click and select line card and click status. The output shall display status of all line ports in that card. ‘To deactivate any line card we have to make the status out of service . Select the port and select modify option. Once the command is executed the port will go to OOS-OPR state and port will be deactivated and there will be no dial tone corresponding to this port. | ‘To make this subscriber In-service (active state) status again select modify option. Once the command is executed, dial tone will be there in that port, When subscriber is OOS-OPR state, there will be no dial tone ‘Once it is in in-service state , dial tone should be there Expected Results | Results [ D Passed D Failed Webbe bd ebb bbe esd dddbdsl fenyentms ou Nese Voor pss Max. 4 1webs tell bbb bb bbb d bd lb ebeds eWAY UNIT TESTS 4.12 DIAL TONE/RINGING TONE/RING BACK TONE CHECKING. (TEST CASE 46) Objective Dial Tone/Ringing Tone/Ring back Tone checking Procedure Off hook one subscriber and immediately dial tone should play. Dial a subscriber and hear ringing and ring back tone. Expected Results Ringing tone and RBT should be OK Results O Passed O Failed 4.13. VOLTAGE IN SUBSCRIBER LINE TEST (TEST CASE 47) Objective | Chéck the voltage of line. Procedure Expected Results Using a multi meter check the DC voltage present in the line in | on-hook condition. It should be between 40 to 48 volt DC. Results O Passed O Failed 4.14 CHECK FOR QOS (TEST CASE 48) ‘The result shall give packet loss % , round trip delay. Objective Check the packet loss , round trip delay in the network from LAG. | Procedure Login to LAG system. Run ping command ( to soft switch IP). Expected Results Results Packet loss should be less than 0.5 % between next hop and shold be less than 1% a syatem located in core site. Latency <50-100 msec Jitter < 20-30 msec. 1 Passed O Failed ACCEPTANCE TESTING (ACCESS) Pea recs.n \Wy.sle CheChapter 4, 4.15 CHECK FOR ETHERNET TEST (TEST CASE 49) Objective Cheek the Ethernet port of LAG Procedure Login into LAG card. In the command prompt give command + Hngtj_tester Select. Ethernet test, This test will diagnose the Ethernet port hardware inside the card Give the following command | © # ifconfig. Cit will show the packots tranamitted , received , exrors ifany ote) | Expected Results | The output of ngtj_toster command should give * CPU_eth0==UP and CPU_ethi==UP ‘The output of ifconfig command will give details of Ethernet connectivity, sample will be as follows ehO Link encapihernee [Wade D969 'A66555, Inet addr192.1682.189) Beast192 168,2.258 Mask:255,255 2550 } UP BROADCAST RUNNING MULTICAST MTU1600 Motes! RX packessis80949 errors droppedi309 overruns framed ‘TK packots'1679 erro%'? deopocd overruns0 carrier cullsions9 txquevelen1000 RX bytae5:206258 (50.7 MB) TX bytos 218196 (218.0 KiB) ‘Base aaarss:0x2000 eth Link encap:timernes HWadds ova" AF5 58 inet aldeH10002 Reast10.255 255.955 Maxk'255.0.00 UP BROADCAST RUNNING MULTICAST MTU1900 Metre: RX packosB82 184 ornare dropped 09 ovornanaD fase ‘TX packets errors dropped overrans earner callisions tequsveton1000 RS byte39760490 (91.2 MID) TX bytss'40774 (8938 KAD) Base addresscdx3000 Results Passed O Failed BeQrwss ar We Lae by4.16: TRANSACTION LOG TEST (TEST CASE 50) | Objective To find out command dumps in the system executed by operator. Procedure cute some commands in EMS for LAG(iKe force tie 00s modify TEN etc) and open the transaction log for that LAG. The result shall display the client IP , user name , command details. Expected Results Results ‘The result shall display the client IP , user name , command details. O Passed O Failed 4.17 PCO CALL TEST. (TEST CASE 51) [ Objective PCO call and 16Khz metering test Procedure From a PCO subseriber make an outgoing call. Once the called party answer , LAG should send 16khz metering pulse to PCO subscriber . Expected Results | PCO call should be OK and hear a beep tone on answer and after every time interval when metering pulses are sent. To be tested only once at only one location Passed O Failed Results 4.18. VOLTAGE DROP TEST (TEST CASE 52) Objective Check the voltage in the card and output from battery Procedure Using a multi meter check the DC voltage present the LAG card and also check the voltage from battery end Expected Results | Voltage drop should be less than 1 voltage drop Results Passed O Failed a f ACCEPTANCE 1 == Wale FED rate SSTING (ACCESS) 25Chapter 4, 4.19. PARTIAL DIAL TEST (TEST CASE 53) Objective Partial Dial from LAG subscriber Procedure From a subscriber dial only 3 or 4 digits and wait. Expected Results _ | Call will fail after sometime Results Gi Passed O Failed 4.20. TEST FOR CONNECTIVITY FROM LAG TO PR , DR SOFT SWITCH AND LIS SERVER (TEST CASE 54) Objective Testrof connectivity to PR and DR SS from LAG Procedure | Login to LAG from PC. Give ping command from LAG terminal to PRIP, DRIP and LIS server IP address. Expected Results | Ping should be OK. Resulis | D Passed O Pailed 4.21 IPV6 TEST CASE (TEST CASE 55) | Objective Ipv6 Test Procedure Presently Ipv6 is not supported. However undertaking will be given that it will be supported in future. Expected Results | Undertaling to be submitted. Results O Passed OFailed J 26 ¢-DOT DSS MAN-NG™ ebb ddsbbddddbbbbbobibbbddbés4.22 LOAD TEST (TEST CASE 56) Objective Check the system stability at load (to be seen in LAB) Procedure Using CTSB (script for load test) run load at around 3000BHICA. Expected Results | System should be stable without any problem. | Results C Failed (}} Aye Key pee ake oe gerd) - Depts ie eaesonne_—_senbeadec (ET ACCEPTANCE TESTING ACCESS Ne wany > >¢ ( eae yet