Test Section 4.1.1.1 : Preliminary Network Interconnection This tests for basic interconnection between service providers (can we place a call between our networks). This is rather basic, but we need to know whether or not we can complete a call before we port. Test Section 4.3.3 Repair Process These tests will verify that the Ameritech repair processes will be handled correctly by the regional groups responsible for Michigan. Test Section 4.4 Porting Process These tests will verify that the Ameritech provisioning and porting processes will be handled correctly by the regional groups responsible for Michigan. Test Section 4.5.6 911 Testing All 911 tests should be completed in each area where LNP is initially deployed, with each PSAP involved. Test Section 4.8 Operator Services You will notice that I did not attach specific tests. The reason being that it is difficult to separate the absolutely necessary tests from the original test plan. Operator Services testing needs to be done for Michigan as there are separate platforms (same switch types, different locations) . I think we need to discuss this area at our next meeting. This issue may pertain to other Service Providers also. Test Section 4.11 NPA Split This is an issue that rears its head immediately in Michigan, and I feel this is necessary for all Service Providers. 4.1.1 - Preliminary Network Interconnection 4.1.1.1 Ability of switch to make Non-ported to non-ported calls between switches Test Description: This test will consist of a basic call through from each testing switch to every other testing switch using the testing switches and currently used interconnection. Test Procedure: A technical representative of each Service Provider company will select a working line that is being furnished dial tone from the represented switch. The representative will furnish the other Service Providers the telephone number to be used. The Service Provider representative will then proceed to call all other Service Provider numbers. Representatives of the other Service Provider companies will respond by answering the call, identifying themselves and company affiliation. The testers from the other companies will then return the call to originating company. Report results of tests to Other providers using forms in Appendix D Expected Results: Each Service Provider must be able to initiate a call from their switch. call all other Service Providers from their switch. respond to calls from all other Service Provider switches. 4.3.3 - Repair Process Similar to process being used on 800/888 database trouble reporting. Subscriber with ported number encounters trouble on line Subscriber makes decision to report problem to service provider Reports to assigned LSP Reports to other LSP Reports to OSP Assigned LSP responds directly to report Responds to subscriber, takes report Identifies that subscriber is valid customer If not refers to proper LSP Tests subscriber service Explains any repair costs to subscriber Arranges repair schedule Other LSP, receives call from subscriber Responds to subscriber, takes report Identifies which LSP has assigned subscriber Uses access to LNP SMS Refers to proper LSP for repair Assigned LSP repairs customer service and responds to customer as shown above for "Assigned LSP" Operator Service Provide, receives call from subscriber Responds to subscriber, takes report Identifies which LSP has assigned subscriber Uses access to LNP SMS Refers to proper LSP for repair Assigned LSP repairs customer service and responds to customer as shown above for "Assigned LSP" LSP test subscribers services Determines cause of problems Refers problem to appropriate organization for repair Follows up with customer, giving status and arranging access if needed LNP SMS Repairs all data base problems referred by authorized LSP Subscriber returned to service LSP informs customer of repairs 4.3.3.1.1 Trouble Report initiated by a Ported number, reporting to LSP providing service Test Description: >From a Ported subscriber line (see Appendix A, Figures 28 through 31) Subscriber notifies Service provider of problem encountered with service Service provider Tests subscribers service Service provider determines if database or other problem is the cause If problem resides in database Service provider refers trouble to LNP SMS provider If problem is within network, normal network trouble reporting procedures are implemented Subscriber notified when problem repaired Test Procedure: >From 312-NXX-507X (terminating on a default switch) (see Appendix A, Figures 28 through 31) Subscriber notifies service provider of problem encountered on line, "Getting wrong numbers" Service provider tests line Service provider identifies problem residing in LNP SMS and refers problem out SMS checks translations in SCP and identifies problem SMS corrects information in SCP and reports back to service provider Service provider retests line to ensure correct operation Service provider then closes trouble report with subscriber Document Test Results, including time required for all transitional steps Report results of tests to Appropriate reporting organization using forms in Appendix D Expected Results: Subscribers report is taken and properly tested Trouble report is not lost moving to and from SMS 312-NXX-507X is fully functional and test ported number after repairs are completed Dips were made on all tests to 312-NXX-507X after porting was completed Verify that response time of process is not excessive No trouble reports generated in switch Proper billing records generated 4.3.3.1.2 Trouble Report initiated by a Ported number, reporting to an LSP not providing service Test Description: >From a Ported subscriber line (see Appendix A, Figures 28 through 31) Subscriber notifies another LSP of problem encountered with service (call is initiated from another line, or subscriber is just not aware of who is providing service) Other LSP takes reports from subscriber Other LSP identifies carrier through SMS Other LSP refers trouble to service provider Service provider Tests subscribers service Service provider determines if database or other problem is the cause If problem resides in database Service provider refers trouble to LNP SMS provider If problem is within network, normal network trouble reporting procedures are implemented Subscriber notified when problem repaired Test Procedure: >From 312-NXX-507X (terminating on a default switch) (see Appendix A, Figures 28 through 31) Subscriber notifies another LSP of problem encountered with service (call is initiated from another line, or subscriber is just not aware of who is providing service) Subscriber notifies service provider of problem encountered on line, "Getting wrong numbers" Other LSP takes reports from subscriber Other LSP identifies carrier through SMS Other LSP refers trouble to service provider Service provider tests line Service provider identifies problem residing in LNP SMS and refers problem out SMS checks translations in SCP and identifies problem SMS corrects information in SCP and reports back to service provider Service provider retests line to ensure correct operation Service provider then closes trouble report with subscriber Document Test Results, including time required for all transitional steps Report results of tests to Appropriate reporting organization using forms in Appendix D Expected Results: Subscribers report is taken by other LSP Trouble report is passed to proper service provider Service provider properly tests service Trouble report is not lost moving to and from SMS 312-NXX-507X is fully functional and test ported number after repairs are completed Dips were made on all tests to 312-NXX-507X after porting was completed Verify that response time of process is not excessive No trouble reports generated in switch Proper billing records generated 4.3.3.1.3 Trouble Report initiated by a Ported number, reporting to an Operator Service Provider Test Description: >From a Ported subscriber line (see Appendix A, Figures 28 through 31) Subscriber notifies OSP of problem encountered with service (call is initiated from another line, or subscriber is just not aware of who is providing service) OSP identifies carrier through SMS OSP refers subscriber to appropriate service provider Service provider tests subscribers service Service provider determines if database or other problem is the cause If problem resides in database Service provider refers trouble to LNP SMS provider If problem is within network, normal network trouble reporting procedures are implemented Subscriber notified when problem repaired Test Procedure: >From 312-NXX-507X (terminating on a default switch) (see Appendix A, Figure 28 through 31) Subscriber notifies OSP of problem encountered with service (call is initiated from another line, or subscriber is just not aware of who is providing service) Subscriber notifies service provider of problem encountered on line, "Getting wrong numbers" OSP identifies carrier through SMS OSP refers subscriber to service provider Service provider tests line Service provider identifies problem residing in LNP SMS and refers problem out SMS checks translations in SCP and identifies problem SMS corrects information in SCP and reports back to service provider Service provider retests line to ensure correct operation Service provider then closes trouble report with subscriber Document Test Results, including time required for all transitional steps Report results of tests to Appropriate reporting organization using forms in Appendix D Expected Results: Subscribers report is taken by other OSP Trouble report is passed to proper service provider Service provider properly tests service Trouble report is not lost moving to and from SMS 312-NXX-507X is fully functional and test ported number after repairs are completed Dips were made on all tests to 312-NXX-507X after porting was completed Verify that response time of process is not excessive No trouble reports generated in switch Proper billing records generated 4.4 - Porting Process Porting Process testing is designed to determine the ability of the various networks to manage the subscriber's service during inter-network activities that are required between LSPs. The primary thrust of these tests is to develop and evaluate the processes that are necessary between the networks involving these transitions. Many of these tests will assume that the services are unbundled and are available to be contracted partially by other carriers. The interconnection configurations are shown in Figures 27 through 31 in Appendix A. The transition of subscribers for this aggregation of tests will involve the initial test of subscriber services, which will be limited in an actual working environment. The primary direction of this portion of certification activity is the movement of the line ensuring the least amount of disruption to the customer. The process flow has been developed by the Illinois Local Number Portability Operation Committee (ICC Flowcharts contained in Appendix A). 800 / 888 database trouble reporting was is used as the pattern for the Trouble Reporting test sequence. The interaction between networks is the primary concern of the test scripts, with limited description of what should transpire within each individual network. Communication between participants should be used as the testing progresses streamline the process within the individual Service Provider's organization. Other tests can be done or repeated to ensure that the services are functional in the ported environment. Basic Interconnection Tests (from the FCC Field Test Plan Section 4.1 and 4.2) are identified for applications before and after the progression from one carrier to another. Tests contained in other sections of the FCC Field Test Plan can also be selectively used to further ensure the functionality of the ported subscriber's number. The tests are grouped into categories established by the action that is impacting the subscriber line. The individual tests scripts are then separated by where the transition of the line occurs. The unbundling of the loop and possible configurations (Appendix A -- Figures 27 through 31) will be the primary considerations for the transitions. These tests will encompasses the spectrum from an LSP providing the entire service including the local loop, to where the transition occurs with collocated switches. Participants are expected to have departments within their organizations to perform the functions identified in the test scripts, therefore the tests will require the operations environment identified by the Operations Committee. New Service Provider (NSP) and Incumbent Service Provider (ISP) designations are provided in the test scripts to identify the role assigned to each participant for a series of tests. The information obtained from the process should be shared between participants as testing progresses. 4.4.1 - Basic Porting Sequence Subscriber has assigned number Subscriber makes decision to change local service provider wants to keep currently assigned number authorizes New Service Provider (NSP) to make move NSP receives call from subscriber wanting service ported checks availability of LNP on subscribers NXX, the NXX must be portable explains service to subscriber explains costs to subscriber arranges tentative cutover schedule NSP issues order for move date for change and schedule established ISP is notified using appropriate ASR forms IC notified dates confirmed with subscriber NPAC notified NSP initiates notification to NPAC ISP initiates notification to NPAC NPAC compares and validates information NPAC requests any missing or incorrect information NSP prepares subscriber's equipment for move validate existing configurations applicable call to subscriber to validate schedule for change test services in place LNP LSMS database update notified of scheduled change by NSP notified of effective date NSP change of assigned number location entered in database number assigned proper LRN for routing NSP Translation and physical changes enters translations into class 5 switch runs necessary jumpers in CO performs pretest to ensure proper CO connections programs services and features ordered pretest all features and services being installed instructs customer on services being installed ISP prepares subscribers number for transfer places 10 digit trigger where available places translations required for porting does physical removal removes 10 digit trigger if applied NSP installation LNP LSMS activates new database information and disables old Tests facilities to NSP CO Disconnect subscriber from ISP facilities ISP disconnects service to subscriber Call NSP CO to activate service NSP activates service to subscriber Cuts customer to NSP facilities Calls LNP LSMS to redirect database information Test made to complete transition Validate all services being provided Validate subscribers understanding of how services operate Subscriber transfer complete to NSP 4.4.1.1.1 Convert Non-ported number to Ported, changing loop and CO (see Appendix A, Figure 29) Test Description: >From a Non-Ported subscriber line (see Appendix A, Figure 27) Subscriber notifies NSP of desire to change carrier Subscriber requests to keep same directory number NSP processes request to convert number, using the process in Section 4.4.1 ISP disconnects termination NSP terminates and tests subscriber to new switch using the process in Section 4.4.1 of the FCC Field Test Plan Transition made using bundled configuration, cutting the loop from the ISP CO to the NSP CO (see Appendix A, Figure 29) Test Procedure: >From 312-NXX-107X (terminating on a incumbent switch) (see Appendix A, Figure 27) Subscriber notifies NSP (recipient switch provider) of desire to change carrier NSP notifies NPAC and ISP (donor switch provider) of impending change Test 312-NXX-107X, using selection of tests identified as pre-move in Appendix F NPAC, ISP and NSP transition station and facilities to NSP termination. All original translations, facilities and equipment are left in tact and placed in made busy state allowing the new service to function properly. The original configuration is keep to restore service should a problem be encountered re-terminating the service. NSP coordinates transition NPAC activates database modifications to port 312-NXX-107X from incumbent LSP, maintaining old database information for cut back should it be required NSP releases translations to switch that add 312-NXX-107X as a ported number, and places old equipment and translation in a busy state ISP activates translations in switch that identify 312-NXX-107X as a ported number to another switch, and places old translations in a busy state NSP and ISP physically cut CO and loop facilities to accept 312-NXX-107X, old facilities are disconnected, not removed Test 312-NXX-107X, using selection of tests identified for post-move in Appendix F Test all features and services associated with 312-NXX-107X When testing has determined that 312-NXX-107X is fully functional remove all translations that were made busy to the original termination Document Test Results, including time required for all transitional steps Report results of tests to the Implementation Project Manager using forms in Appendix D Expected Results: 312-NXX-107X is fully functional and test ported number Dips were made on all tests to 312-NXX-107X after porting was completed Verify that response time of process is not excessive Subscriber is not without service, except during transition being coordinated by NSP No trouble reports generated in switch Proper billing records generated 4.4.1.1.2 Convert Non-ported number to Ported, same loop and separate COs (see Appendix A, Figure 29) Test Description: >From a Non-Ported subscriber line (see Appendix A, Figure 27) Subscriber notifies NSP of desire to change carrier Subscriber requests to keep same directory number NSP processes request to convert number, using the process in Section 4.4.1 ISP disconnects termination NSP terminates and tests subscriber to new switch using the process in Section 4.4.1 of the FCC Field Test Plan Transition made using unbundled configuration, the loop remaining terminated at the ISP CO mdf and multiplexed with other subscribers to the NSP CO (see Appendix A, Figure 29) Test Procedure: >From 312-NXX-107X (terminating on a incumbent switch) (see Appendix A, Figure 27) Subscriber notifies NSP (recipient switch provider) of desire to change carrier NSP notifies NPAC and ISP (donor switch provider) of impending change Test 312-NXX-107X, using selection of tests identified as pre-move in Appendix F NPAC, ISP and NSP transition station and facilities to NSP termination. All original translations and equipment are left in tact and placed in made busy state allowing the new service to function properly. The original configuration is keep to restore service should a problem be encountered reterminating the service. NSP coordinates transition NPAC activates database modifications to port 312-NXX-107X from incumbent LSP, maintaining old database information for cut back should it be required NSP releases translations to switch that add 312-NXX-107X as a ported number, and places old equipment and translation in a busy state ISP activates translations in switch that identify 312-NXX-107X as a ported number to another switch, and places old translations in a busy state NSP and ISP physically cut loop facilities to terminate 312-NXX-107X on multiplex routed to NSP Test 312-NXX-107X, using selection of tests identified for post-move in Appendix F Test all features and services associated with 312-NXX-107X When testing has determined that 312-NXX-107X is fully functional remove all translations that were made busy to the original termination Document Test Results, including time required for all transitional steps Report results of tests to the Implementation Project Manager using forms in Appendix D Expected Results: 312-NXX-107X is fully functional and test ported number Dips were made on all tests to 312-NXX-107X after porting was completed Verify that response time of process is not excessive Subscriber is not without service, except during transition being coordinated by NSP No trouble reports generated in switch Proper billing records generated 4.4.2 - Cancellation of Service Order Subscriber has had requested number Subscriber reverses decision and not to change local service provider wants to keep current ISP as service provider calls NSP or ISP to cancel change NSP or ISP receives call from subscriber requesting service not be ported explains any costs that may be incurred to subscriber identifies date for change and schedule established NSP or ISP issues order to cancel change Other carrier notified (NSP or ISP ) notified NPAC notified IC notified LNP LSMS notified of cancellation by NSP or ISP notified of scheduled date for number transfer change of assigned number location removed from database NSP cancels and remove all prearranged activity Removes translations in switch Removes necessary jumpers in CO ISP prepares subscribers number for normal operation replaces translations required for porting, with original translation Test made to complete transition validate all services being provided validate subscribers understanding of how services operate 4.4.2.1.1 Cancel Order in Progress Converting Non-ported number to Ported Test Description: >From a Non-Ported subscriber line (see Appendix A, Figure 27) Subscriber notifies NSP of desire to change carrier Subscriber requests to keep same directory number NSP processes request to convert number, using the process in Section 4.4.1 Subscriber changes mind and cancels change order NSP terminates change sequence for using the process in Section 4.4.2 of the FCC Field Test Plan Transition made using bundled configuration, cutting the loop from the ISP CO to the NSP CO (see Appendix A, Figure 28) Test Procedure: >From 312-NXX-207X (terminating on a incumbent switch) (see Appendix A, Figure 27) Subscriber notifies NSP (recipient switch provider) of desire to change carrier NSP notifies NPAC and ISP (donor switch provider) of impending change Test 312-NXX-207X, using selection of tests identified as pre-move in Appendix F Subscriber notifies NSP to cancel transfer request NSP notifies NPAC of cancellation NSP notifies ISP (donor switch provider) of cancellation NSP confirms that NPAC and ISP have canceled required preparations NPAC, ISP and NSP return all translations and equipment to status prior to transaction request Test 312-NXX-207X, using selection of tests identified for pre-move in Appendix F Test all features and services associated with 312-NXX-207X Test to determine that 312-NXX-207X is fully functional as when test originated Document Test Results, including time required for all transitional steps Report results of tests to the Implementation Project Manager using forms in Appendix D Expected Results: 312-NXX-207X is fully functional and tested non-ported number No dips were made on all tests to 312-NXX-207X after stopping transition was completed Verify that response time of process is not excessive Subscriber is not without service, except during transition being coordinated by NSP No trouble reports generated in switch Proper billing records generated 4.4.3 - Disconnect for Ported Number Ported subscriber makes decision to disconnect service calls service provider to disconnect Service Provider issues disconnect order Date for disconnect and schedule established NPAC notified IC notified dates confirmed with subscriber LNP LSMS removes assigned number database Test made to complete removal Validate all number referrals and announcement being properly provided Validate default routing 4.4.3.1.1 Disconnect Ported Subscribers Service Test Description: >From a Non-Ported subscriber line (see Appendix A, Figure 27 - 31) Subscriber notifies service provider of desire to disconnect service Service Provider processes request to disconnect number, using the process in Section 4.4.3 Service provider disconnects service LNP LSMS changes database to terminate number at incumbent switch or provide a referral termination LSP with incumbent switch changes translations for disconnected number Service disconnected Test Procedure: >From 312-NXX-307X subscriber notifies service provider) of desire to disconnect service Service provider notifies NPAC Service provider notifies incumbent switch provider of impending disconnect NPAC, NSP and ISP make preliminary modifications NPAC enters database modifications to disconnect 312-NXX-307X from incumbent (donor) LSP, modifications are held in busy state until the time of the disconnect Service provider adds translations to switch for adding 312-NXX-307X as a disconnected number, and places equipment and translations in a busy state Incumbent switch provider prepares translations in switch to identify 312-NXX-307X as a disconnected number, and places all translations in a busy state Service provider physically prepares CO and loop facilities to disconnect 312-NXX-307X Service provider confirms that NPAC and incumbent switch have made required preparations NPAC, incumbent switch and service provider disconnect station and facilities to service provider. All original translations, facilities and equipment are left in tact and placed in made busy state allowing the new service to function properly. The original configuration is keep to restore service should a problem be encountered terminating the service. Service provider coordinates disconnect NPAC disconnects subscriber number in database Service provider removes translations to switch for 312-NXX-307X as a ported number Incumbent switch provider activates translations in switch that identify 312-NXX-307X as a disconnected number Service provider physically disconnects CO and loop facilities to 312-NXX-307X Test 312-NXX-307X, using selection of tests identified for pre-move and testing vacant numbers in Appendix F When completed testing has determined that 312-NXX-307X is fully disconnected all translations, removal is finalized Document Test Results, including time required for all transitional steps Report results of tests to the Implementation Project Manager using forms in Appendix D Expected Results: 312-NXX-307X is a disconnect number Dips were made on all tests to 312-NXX-307X after disconnect was completed are properly routed Verify that response time of process is not excessive Subscriber is not without service, except during transition being coordinated by NSP No trouble reports generated in switch Proper billing records generated 4.4.4 - Basic Un-Porting Sequence Subscriber has assigned ported number Subscriber makes decision to change from ported service provider, returning to incumbent provider wants to keep currently assigned number authorizes New Service Provider (NSP) to make move NSP (incumbent service provider for NXX) receives call from subscriber wanting service explains service to subscriber explains costs to subscriber arranges tentative cutover schedule NSP (incumbent service provider for NXX) issues order for change date for change and schedule established Local Exchange Carrier notified Original or Ported Provider (ISP) notified, (Firm Order Confirmation (FOC)) NPAC notified IC notified dates confirmed with subscriber NSP (incumbent service provider for NXX) prepares for move validate existing configurations applicable call to subscriber test services in place LNP LSMS notified of scheduled change by NSP notified of effective date by NSP change of assigned number location entered in database CPC number removed for proper routing ISP (ported service provider) is officially notified by NSP (incumbent service provider for NXX) of move, with subscribers authority NSP (incumbent service provider for NXX) enters translations into class 5 switch prior to date runs necessary jumpers in CO performs pretest to ensure proper CO connections programs services and features ordered pretest all features and services being installed instructs customer on services being installed ISP (ported service provider) prepares subscribers number for transfer places translations required for removing subscribers number from porting, holds in made busy state NSP (incumbent service provider for NXX) installer visits premise Tests facilities to NSP CO (incumbent service provider for NXX) Calls ISP (ported service provider) and notifies them move is in process, disconnect subscriber ISP disconnects service to subscriber Call NSP to activate service NSP activates service to subscriber Cuts customer to NSP facilities Calls LNP LSMS to redirect database information LNP LSMS activates new database information and disables old Test made to complete transition validate all services being provided validate subscribers understanding of how services operate Subscriber transfer is complete to NSP (incumbent service provider for NXX) 4.4.4.1.1 Convert Ported number to Non-ported, changing loop and CO (see Appendix A, Figure 29) Test Description: >From a Ported subscriber line (see Appendix A, Figure 29) Subscriber notifies Service Provider or Incumbent switch service provider of desire to change to incumbent Subscriber requests to keep same directory number, but revert to the service provider with the incumbent switch Incumbent switch service provider processes request to convert number, using the process described in Section 4.5.1, but moving from the ported to the incumbent switch Original ported service provider disconnects termination Incumbent switch service provider terminates and tests subscriber to new switch using the process described in Section 4.5.1, but moving from the ported to the incumbent switch of the FCC Field Test Plan Transition made using bundled configuration, cutting the loop from the Original ported service provider CO to the Default switch service provider CO (see Appendix A, Figure 27) Test Procedure: >From 312-NXX-407X (terminating on a Original ported service provider) (see Appendix A, Figure 27) Subscriber notifies Default switch service provider (default or donor switch provider) of desire to change to default Default switch service provider notifies NPAC and Original ported service provider (original recipient switch provider) of impending change Test 312-NXX-407X, using selection of tests identified as pre-move in Appendix F NPAC, Original ported service provider and Default switch provider make preliminary modifications NPAC enters database modifications to un-port 312-NXX-407X to default (donor) LSP, modifications are held in busy state until the time of the transition Default switch service provider adds translations to switch for adding 312-NXX-407X as a non-ported number, and places equipment and translations in a busy state Original ported service provider prepares translations in switch to identify 312-NXX-407X as a non-ported number terminating on another switch, and places all translations in a busy state Default switch service provider physically prepares CO and loop facilities to accept 312-NXX-407X Default switch service provider confirms that NPAC and Original ported service provider have made required preparations NPAC, Original ported service provider and Default switch service provider transition station and facilities to Default switch service provider termination. All original translations, facilities and equipment are left in tact and placed in made busy state allowing the new service to function properly. The original configuration is keep to restore service should a problem be encountered re-terminating the service. Default switch service provider coordinates transition NPAC activates database modifications to un-port 312-NXX-407X to default LSP, maintaining old database information for cut back should it be required Default switch service provider releases translations to switch that add 312-NXX-407X as a non-ported number, and places old equipment and translation in a busy state Original ported service provider activates translations in switch that identify 312-NXX-407X as a non-ported number to another switch, and places old translations in a busy state Default switch service provider physically cuts CO and loop facilities to accept 312-NXX-407X, old facilities are disconnected, not removed Test 312-NXX-407X, using selection of tests identified for post-move in Appendix F Test all features and services associated with 312-NXX-407X When testing has determined that 312-NXX-407X is fully functional remove all translations that were made busy to the original termination Document Test Results, including time required for all transitional steps Report results of tests to the Implementation Project Manager using forms in Appendix D Expected Results: 312-NXX-407X is fully functional and tested non-ported number Dips were properly routed on all test calls to 312-NXX-407X after un-porting was completed Verify that response time of process is not excessive Subscriber is not without service, except during transition being coordinated by Default switch service provider No trouble reports generated in switch Proper billing records generated 4.4.5 - Administrative Situations All individual organizations offering ported services will have completed all inter-company agreements required to provide ported services. All interchange of information and any operating system interaction should be tested to ensure the most effective control of subscribers. The initial assumption to testing is that organizations have internal processes capable of providing all administrative elements required to provide ported service to subscribers. These processes have been applied within the organizations providing service and have an accept track record in compliance with recognized industry standards. 4.4.5.1 - Industry Impact 4.4.5.1.1 LERG interactions, the impacts on issuing the LERG. 4.4.5.1.2 LARG interactions, the additional point codes that are to be included in LARG distributions. 4.4.5.2 - Customer Impacts 4.4.5.2.1 Trouble report Routing Customers that call in report from neighbor's location (other carrier). This aspect involves the transferring the report from one LSP to another, which will probably involve reciprocity and various business agreements. Routing of trouble reports not received a proper location. Customers will report troubles to any source they feel is adequate, to ensure customer satisfaction for all carriers local reporting of troubles must include employee and customer education. 4.4.5.3 - Other System Impacts Interaction of ported numbers with other carriers automated test systems such as MLT. 4.5.6 - Enhanced Services 4.5.6.1 - 911/E911 Call with Direct Trunks to PSAP 4.5.6.1.1 911/E911 Call From a Non Ported number in an closed NPA-NXX Test Description This will test that a non-ported number in an closed NPA-NXX can place a 911/E911 call Test Procedure >From a non-ported number in an NPA-NXX not opened to portability Dial 911/E911 Test Results Originating LSP routes call to 911/E911 PSAP PSAP receives ANI of originating calling party PSAP receives address of calling party PSAP can return the call to the originating station 4.5.6.1.2 911/E911 Call From a Non Ported number in an open NPA-NXX Test Description: This will test that a non-ported number in an open NPA-NXX can place a 911/E911 call Test Procedure: >From a non-ported number in an NPA-NXX opened to portability Dial 911/E911 Test Results: Originating LSP routes call to 911/E911 PSAP PSAP receives ANI of originating calling party PSAP receives address of calling party PSAP can return the call to the originating station 4.5.6.1.3 911/E911 Call From a Ported number in an open NPA-NXX Test Description: This will test that a ported number in an open NPA-NXX can place a 911/E911 call Test Procedure: >From a ported number in an NPA-NXX opened to portability Dial 911/E911 Test Results: Originating LSP routes call to 911/E911 PSAP PSAP receives ANI of originating calling party PSAP receives address of calling party PSAP can return the call to the originating station 4.5.6.2 - 911/E911 Calls Using Access Tandem to PSAP 4.5.6.2.1 911/E911 Call From a Non Ported number in an closed NPA-NXX Test Description This will test that a non-ported number in an closed NPA-NXX can place a 911/E911 call Test Procedure >From a non-ported number in an NPA-NXX not opened to portability Dial 911/E911 Test Results Originating LSP routes call to 911/E911 PSAP PSAP receives ANI of originating calling party PSAP receives address of calling party PSAP can return the call to the originating station 4.5.6.2.2 911/E911 Call From a Non Ported number in an open NPA-NXX Test Description This will test that a non-ported number in an open NPA-NXX can place a 911/E911 call Test Procedure >From a non-ported number in an NPA-NXX opened to portability Dial 911/E911 Test Results Originating LSP routes call to 911/E911 PSAP PSAP receives ANI of originating calling party PSAP receives address of calling party PSAP can return the call to the originating station 4.5.6.2.3 911/E911 Call From a Ported number in an open NPA-NXX Test Description This will test that a ported number in an open NPA-NXX can place a 911/E911 call Test Procedure >From a ported number in an NPA-NXX opened to portability Dial 911/E911 Test Results Originating LSP routes call to 911/E911 PSAP PSAP receives ANI of originating calling party PSAP receives address of calling party PSAP can return the call to the originating station 4.8 - Operator Service Routed Calls 4.8 - Operator Service Routed Calls 4.8.1 - CALL COMPLETION FOR 0-/00- CALLS (STATION PAID BILLING) 4.8.1.1 - Intra LATA Calls 4.8.1.2 - Inter LATA Calls 4.8.2 - BILL TO THIRD 4.8.2.1 - Intra LATA Calls 4.8.3.1 - Inter LATA Calls 4.8.3 - Automated Operator Handled Calls 4.8.4 - COLLECT 4.8.4.1 - Intra LATA Calls 4.8.4.2 - Inter LATA Calls 4.8.4.3 - Automated Operator Handled Calls 4.8.5 - CALLING CARD 4.8.5.1 - Intra LATA Calls 4.8.5.2 - Inter LATA Calls 4.8.5.3 - Automated Operator Handled Calls 4.8.6 - BUSY LINE VERIFY/EMERGENCY INTERRUPT 4.8.6.1 - Intra LATA Calls 4.8.6.2 - Inter LATA Calls 4.8.7 - BRANDING 4.11 - NPA Splits The shortage of available numbers with NPAs has led to the splitting of NPA within densely populated areas around the country. This trend will probably continue as populations grow. LRN LNP must be able to respond to the split NPA configuration with these areas. LRN LNP services that have been successfully tested will not be directly affected by split NPAs. 2 LRNs required, for each switch, NPAC mass down load and Lab tested. ---------- From: Mark D. Foster[SMTP:mdfassoc@mindspring.com] Sent: Tuesday, May 20, 1997 10:37 PM To: 'Richard Carter' Subject: RE: May 6,1997 Michigan Impementation Meeting Minutes Rich, You might forward this to Bryan for posting on npac.com. R, Mark --------------------------------------------------------------- Mark D. Foster | mdfassoc@mindspring.com MDF Associates | Tel: +1(703) 404-2258 Telecoms Consulting | Fax: +1(703) 404-2591 -----Original Message----- From: Richard Carter [SMTP:rich.carter@internetmci.com] Sent: Tuesday, May 20, 1997 2:26 PM To: 'Mark D. Foster' Subject: FW: May 6,1997 Michigan Impementation Meeting Minutes << File: michtst.doc >> ---------- From: Barry Bishop[SMTP:barry.bishop@ported.com] Sent: Tuesday, May 20, 1997 12:18 PM To: lvasquez2@bsi.att.com; terry.appenzeller@ameritech.com; rich.carter@internetmci.com; nancy.deroo@ameritech.com; 258443@mci.com; jjoerger@mcimail.com; lewis.scot@mfst.com; sam.mehta@telops.gte.com; jfshea@worldnet.att.net Cc: conway@lga.uucp; eelkin@bsi.att.com; judithevans@bsi.att.com; pete.hoffman@airtouch.com; e_kistner@mcimail.com; dnoorani@bsi.att.com; tamplin@bsi.att.com Subject: Re: May 6,1997 Michigan Impementation Meeting Minutes Larry (all), attached you will find a file containing the tests that I feel are necessary to test the differences required by Ameritech when we move to Michigan. Please note that they are not inclusive of all tests that may need to be done for all service providers, but only what needs to be done to reflect what is handled by different organizations within Ameritech. There should be no differences in the various process flows and the outcome of the tests should be the same as the tests completed for MSA1. If you have any questions, please let me know. Barry ---------- > From: lvasquez2@bsi.att.com > To: terry.appenzeller@ameritech.com; barry.bishop@ported.com; rich.carter@internetmci.com; nancy.deroo@ameritech.com; 258443@mci.com; jjoerger@mcimail.com; lewis.scot@mfst.com; sam.mehta@telops.gte.com; jfshea@worldnet.att.net; lvasquez2@bsi.att.com > Cc: conway@lga.uucp; eelkin@bsi.att.com; judithevans@bsi.att.com; pete.hoffman@airtouch.com; e_kistner@mcimail.com; dnoorani@bsi.att.com; tamplin@bsi.att.com > Subject: May 6,1997 Michigan Impementation Meeting Minutes > Date: Thursday, May 15, 1997 8:25 AM > > Michigan Number Portability Implementation Meeting Minutes > Detroit, Michigan > May 6, 1997 > > Meeting Minutes taken by Larry Vasquez, AT&T. > > Attendees: Present > > Pete Hoffman Airtouch > Barry Bishop Ameritech > Dee Branch Ameritech > Nancy DeRoo Ameritech > Bob Reynolds Ameritech > Larry Vasquez AT&T > Tom VanDusen GTE > John Shea Lockheed Martin > Dick Dowd MCI/LLC > Jim Joerger MCI Metro > Bob Currier NENA Michigan, St Clair County 911 > Scot Lewis WorldCom/MFS > > Attendees: NOT Present > > Denise Hardaway Ameritech > Larry Neeper Brooks Fiber > Mark Wyman Comcast > Rich Carter Lockheed Martin > Rick Arzadon Teleport > > Agenda: > Update on 9/29/97 readiness All > What's The Status Of GTE GTE > What are the tests that will be State specific All > Michigan Testing Dick Dowd > Revised Pick From List Status Larry Vasquez > 911 issues Nancy DeRoo > 4/25/07 Lansing Meeting > PSAP Update > New Entrant Handbook Barry Bishop > Open Issues All > Next Meetings > > > Larry Vasquez opened up the meeting with an overview of the agenda. > > The poll for 9/29/97 readiness are as follows: > Ameritech Yes ( Barry Bishop) > AT&T Yes (Larry Vasquez) > Brooks Fiber No, will not be on Detroit MSA > GTE No, per Sam Mehta, February 1998 > MCI Yes (Jim Joerger) > Teleport Yes (Rick Arzadon) > Worldcom/MFS Yes (Scot Lewis) > > Jim Joerger raised the issue of why we need to get an update on the > readiness of all new entrants at the beginning of every meeting. We > seemed to all agree, and for subsequent meetings we will assume all > new entrants to be ready on 9/29/97 unless we are told otherwise. > > Regarding GTE not being ready until February 1998. > Larry Vasquez is to check with Terry Appenzeller (Ameritech - Steering > Committee Chair) and determine the appropriate protocol for notifying > the MPSC of the anticipated delay of GTE. > Larry Vasquez will also notify Sam Mehta that a letter may need to > written to Terry or directly to the MPSC regarding their delay. > > Michigan Testing > Dick Dowd did an overview of the testing activities that he will > coordinate in Michigan. Some of the tests will be state specific. > Barry Bishop is to review the test plan and list what tests and we > will have to perform in Michigan versus Illinois. He will also > outline why the tests will be required in Michigan. He hopes to get > the list of tests out to all new entrants within the next week. > > Dick recommended that each company assign a Single Point of Contact > SPOC) for him to work with directly during the Michigan tests. The > dedicated resources are as foloes: > Ameritech Bob Bartenstein > AT&T Larry Vasquez to supply name by 5/14/97 > Pam Overly MCI > Mitch Mitchell Worldcom/MFS > Teleport Unknown (LV to check) > > The SPOC's will work with Dick Dowd and have planning conference calls > and provide the following for the tests: > Telephone Numbers for testing > SSN's (Sub System Numbers) > Trunk Translations > Point Codes > Etc. > > Dick recommended that a tentative date to begin testing in Michigan is > August 18 through September 29, 1997 > > Revised Pick From List > Regarding the revised pick from list. Larry Vasquez is to contact > Terry Appenzeller and determine how to obtain a data aggregator. Bill > Celio (MPSC) has rejected our request to aggregate the data. > As of 5/13/97 Terry A. made arrangements to have Brent Struthers > (Illinois Commerce Commission) handle the neutral third party > aggregation. Lists will be due to Brent on June 6, 1997 during our > next meeting in Chicago. > > A conference call has been established, for all CLEC's to discuss the > format and timeline for new pick from list submittals to Brent. The > conference call is scheduled for Friday, May 16, from 9:00 - 10:00 > Central Time. The bridge number is > 334-264-8326, the participant code is 412-739 > > 911 Testing > Regarding the 911 Update. Nancy DeRoo will contact Walt Subora > (Ameritech) for an updated list of 911 tests. She will advise Dick > and test team SPOC's as required. > > Nancy again raised the issue regarding all new entrants having a > contract for network routing with Ameritech, Making sure all new > entrants can bill operational surcharges, provide trap and trace > capabilities, correct ANI failures, etc. This should be handled and > answered by each companies SPOC. > > Other tests will be to perform company-to-company testing for LSR's. > In addition, the 911 testing procedures with what telephone numbers > we test, when we test for 911 calls and when we schedule the testing > will be managed by each companies SPOC and Dick Dowd and address some > of the following open issues > * When/how/what numbers do we test > * How do we test for ANI failures > * How do we handle default routing testing > * Will each vendor be able to determine surcharges > * We will need to test before and after the ALI database update > * We will have to test calls to the NXX holder > * How will call transfers between PSAP's be managed > * Trunking for vendors to 911 routing by rate center > * Etc./Etc. As you can tell lots of 911 issues to be resolved > > New Entrant Handbook > Barry Bishop updated the team on a new entrant handbook that was > recently developed by the Sub-Committee Chairpersons in the Chicago > Trial. The chairs met in Dallas, Texas (hosted by Jim Joerger, MCI) > to develop a handbook that all new entrants could use as a LNP > guideline. Barry passed out copies and will be used as a tool for > future entrant procedures. John Shea stated that new entrants in > Michigan will be handled by Lockheed on a case by case basis. > > *********************************************************** > > Next Two Meetings In Chicago, Illinois!!!!!!!!! > > June 9, 1997 Chicago, Illinois > Ameritech Training Center > 350 Orleans (Holiday Inn Mart Plaza) > 4th Floor > 12:00 - 5:00 > If you cannot attend in person, call Barry Bishop for the > conference bridge number > > Tentative Agenda > Submit Sealed Pick from lists All > Testing Procedures/Updates Dick Dowd > 911 Testing Issues Nancy DeRoo > Line by line review of the Timeline All/Dick Dowd > Dates for the timeline by all IXC's All > Open Issues > Next meeting > > July 11, 1997 Chicago, Illinois > Ameritech Training Center > 350 Orleans (Holiday Inn Mart Plaza) > 4th Floor > 8:30 - 12:00 > If you cannot attend in person, call Barry Bishop for the > conference bridge number > ********************************************************************* > > If you have any questions or corrections to this memo, please feel > free to call me on (312) 230-6253 or via E-Mail on lvasquez2@ att.com > > LV > 5/14/97 > ----------