1. IP Telephony (IPT) update
NCAB Presentation
18-Jun-2003
Jeff Custard
Teresa Shibao

2. Outline for today’s presentation
Current state of deployment
Overview of changes and enhancements
Schedule for remaining deployment
Input on dates and contacts
Future items
Potential services and enhancements

3. VoIP – a typical migration
Step 1   Pilot stage—the IP network is introduced, and a very limited number of users are given IP service. In this initial deployment, which often will include the telecom or IT group, users sometimes retain their conventional phones side-by-side with IP phones. Usually, however, they move immediately onto the new system. When the pilot trial is stable and satisfactory for a number of weeks, it can be expanded.
Step 2   User block migration—a block of users is moved (usually over a weekend) from the conventional voice network to the IP network. The block can be chosen as a geographical group, a group sharing a block of directory numbers (DNs), or a community of interest, such as the purchasing department.
Step 3   Further user block migration—the number of users moved in a block is determined by the maximum number of users the telecom staff can move over a weekend, and the number of weekends the telecom department is prepared to work. In general, migration should be completed as quickly as possible.
Taken from:

4. 99 boxes of phones in the warehouse…99 boxes of phones…

5. Plus switch upgrade gear….

6. Current state of deployment
3 Cisco Call Managers (CCMs)
1 Unity voic server
Misc. IPT servers (e.g., for services, billing, etc.)
~620 IP phones deployed
~500 users

8. New IPT application servers
Cisco Emergency Responder (CER) - provides location of IP phones and notifies security about 911 calls
Cisco Integrated Contact Distribution (ICD) - a “help desk” solution

9. Schedule for remaining IPT deployment
Draft schedule for converting the rest of the organization from the PBX based system to the IPT based system now available
Goal is to complete this by the end of the 2003 calendar year. You may view this schedule at:
Input on
Technical contact(s)
Administrative contact(s)
Please review this schedule. We are asking for your input on the following items:
Dates for the various groups: if you know of major conflicts, meetings, or key personnel may may be absent, etc., during the times we've allotted, please let us know so we can make adjustments now if necessary.
Technical and Administrative contact information: I think we have most of these already (even though you don't see them all on the schedule yet), but we would like your input to assure we don't miss somebody you would like kept in the loop on everything. We are planning on working closely with these individuals regarding the specific changes and then counting on them to notify their respective user groups.

10. End state of deployment
4 Cisco Call Managers (CCMs)
1 Cisco Unity voic server
Misc. IPT servers (e.g., for services, billing, etc.)
~1,800 IP phones deployed
~1,500 users on new IPT systems

11. IPT is a driver for increased redundancy and network resiliency
IPT is a driver for increased redundancy and network resiliency. These improvements do not have to cost a ton of money, but we do need to make significant changes in our overall network design to achieve them (such as going to a layer3 backbone).

12. IPT is a driver for increased redundancy and network resiliency
IPT is a driver for increased redundancy and network resiliency. These improvements do not have to cost a ton of money, but we do need to make significant changes in our overall network design to achieve them (such as going to a layer3 backbone).

13. Futures? “SoftPhone” support?
Additional “services” and directory functions from phones?
Intra-FRGP member IPT?
Intra-I2 member IPT?

14. Wrap-up NETS VoIP project page: Questions?
Questions?