s, firewalls, and border elements as these configurations need to be replicated when you implement production SIP trunk services in your network. When the test plan has been successfully completed and all serious issues resolved, you are ready to bring your pilot user community's live calls onto the SIP trunk. Start Using the SIP Trunk for the Pilot User Community During the planning step, you identified the user community that is to participate in the trial. While the SIP trunk installation and testing take place, prepare this user community for the date on which test calls will start and train them on the procedures you want them to follow to report problems or inconsistencies they might notice. Provide any training you might deem necessary to these users. Ensure that they have backup calling access and procedures if the SIP trunk should be down or unable to com- plete the calls they initiate. After you define a clear test plan and execute the test plan satisfactorily, the Pilot Trial user community can start using the SIP trunk actively for normal business calls. You can consider adding a prefix (such as an 8) to the dial plan SO that the user community can easily choose whether they use the SIP trunk trial or pro- duction TDM trunks. Another technique to stress test the SIP trunk is to arrange call bursts by the user com- munity where every caller has a script of test calls to execute during a given 5-10 minute time period. 256 SIP Trunking Production Service In the Pilot Trial step, you defined clear success criteria and the length of the Pilot Trial. When you complete these steps to your organization's satisfaction, and the driving fac- tors for migration to SIP trunk service still hold true (such as cost savings), you are now ready to move into production service. Before production service can start, you need to educate the larger user community who will now join SIP trunk service in the same way you did the pilot user community. Initially you might still want to maintain TDM backup access for these users 