bility of TDM- Assess on pilot learning patterns equivalent features organizational Educate/prepare Assess network Geographic responsibility user community design implications coverage Determine length of Port DIDs Emergency call Investigate trial policy DID porting Installation and Define production Call load balancing configuration user community and failover routing Define a clear test phases Emergency call plan including all Define user handling required production community to pilot Determine physical call flows Evaluate future new delivery Test failover and services Determine network redundancy Assess security demarcation Address problems precautions Agree on monitoring that come up and troubleshooting Test monitoring procedures procedures Figure 11-1 Deployment Steps Planning The planning step has two major goals: Complete an analysis to determine the benefits of installing a SIP trunk, Determine the various impacts to your network SO that each issue can be objectively evaluated and a plan put in place to address any areas of concern. Chapter 11: Deployment Steps and Best Practices 245 Even though a decision might already have been made or directed to implement a SIP trunk in your network, it is still recommended you keep an open mind until completing Step 3, which is to execute a Pilot Trial. After you execute the trial, you will have all the necessary information to make an informed decision on whether to continue with a pro- duction implementation in your network. To ensure a smooth and predictable implemen- tation that meets initial expectations, the planning step is of the utmost importance. As already pointed out in earlier chapters, the SIP trunking industry is not yet at the same maturity level as installing a Primary Rate Interface (PRI) from a SP. Hopefully the indus- try will reach this level of predictability soon, but until then, success might largely depend on the thoroughness of your planning and preparation. During the planning step, work through the following activities and address each to