Emergency Notification implications to networking

1. Emergency Notificationimplications to networking Bruce Campbell Information Systems and Technology

2. Emergency Notification Components • Text messaging to student cell phones • Voicemail to all • On screen pop up messages • VoIP public address system • Uses VoIP phones for public address, “zone paging” system • Plan is to put approximately 100 such phones into departmental offices, etc, so these areas can be “paged” from emergency operations centre.

3. Zone Paging • Approximately 100 VoIP phones to be deployed in departmental offices, and some other areas. • Emergency operations centre can then broadcast spoken message into these areas. • The VoIP phones deployed would also replace the existing phone on the persons desk. • Almost all areas of the campus network will be involved. • System needs to provide dependable service during emergencies, and non emergencies.

4. Voice over IP • Uses data network for voice communications. • Deployed in recent buildings, and all new buildings (RAC, HH addition, Health Sciences campus) • Approximately 100 VoIP for dons in residence • Other smaller deployments, e.g. IST Network Services

5. Campus Network • Managed by IST and faculty/departmental IT groups. • Coordination of activities through committees, CNAG and CTAG. • Mostly standardized equipment and processes across campus. • Dependable and supportable voice over IP services have some new implications. • CNAG subcommittee created to discuss issues and make recommendations. (in progress)

6. Some Issues to consider • Uninterruptable power, runtime etc • Service windows, when to upgrade firmware on switches • Documentation • Power over ethernet, e.g. injectors versus POE switches • Consistent practices • Quality of Service (QoS) • Cost implications • Changes in existing practices

7. Goal • document ideal standards • recommend achievable standards, with associated costs and other impacts.