FY 08 NETWORK PLANNING TASK FORCE.ppt

PennNet Phone Issues We have had some long-term problems with the PRIs from Verizon and the Cisco gateways that have caused known problems with transferring some calls, some caller ID, etc. Next steps We believe we have the PRI problems resolved. We tested the new gateway code yesterday. The new code release comes out in late October. If all goes well, we could have improved call transfers in production in November. * Instant Messaging Goals Users at Penn report that they are using Instant Messaging (AIM, Yahoo Messenger, Skype and Google Talk) today for business purposes. Our goal was to provide them with an alternative that Provides improved privacy and security Is able to make use of Penn identity information Can be integrated with other Penn communications elements * Instant Messaging Status The same open standard, open source technology used by Google Talk, jabber (based on the XMPP protocol family) is being deployed and used in a pilot mode at Penn today It provides controlled data path (need not leave campus when two on campus users chat) It provides identity assurance (uses Penns authentication system, and Penns naming scheme) It has so far proven to be low cost to operate and highly reliable. Next steps Pilot to a larger audience over the next 3-4 months Full rollout at no cost to current PennNet phone and email customers by end of FY’08. * Voice mail Goals Roll out version 1.0 of new voicemail in early 2008 (possible late January). Key reasons for change Today’s Octel Voicemail system is old and expensive to support (vendor EOL/EOS) It does not have good disaster recovery capabilities In a failure, we could be out for at least 12 hours Message recovery would be incomplete. The new system can recover rapidly with very complete data The new system is designed for the new PennNet Phone service to be used throughout Penn in the next few years A migration by all users to the new voice mail system now brings us back to one voice mail community * Voic