Orig. Date: Control No.: ITSTD VoIP INFORMATION TECHNOLOGY STANDARD Title: VoIP to the Desktop Rev. Date: Rev. No.

Transcription

1 Technical Team: CFM Group Approval: Page 1 of 11 TABLE OF CONTENTS I. Purpose... 2 II. Standards Section 1: Overview Section 2: Pre implementation Guidelines Section 3: Voice over Internet Protocol Implementation Section 4: Functional Requirements and System Parameters Section 5: Components and Hardware Section 6: Functional Integration and Interoperability Section 7: Support/Warranty... 9 III. Related Standards... 9 IV. Exceptions or Waiver Requirements V. Requests for Clarification VI. References VII. Key Terms & Glossary VIII. Document History... 11

2 Technical Team: CFM Group Approval: Page 2 of 11 I. PURPOSE The District provides education programs to the community that meet the changing needs of students for academic and occupational preparation. Providing robust, sustainable technology systems at each of the nine colleges will enhance these educational programs. This standard is meant to provide minimum performances and guidelines for Voice over Internet Protocol (VoIP) to the desktop at the Los Angeles Community College District (LACCD) including, but not limited to, East Los Angeles College (ELAC), Los Angeles City College (LACC), Los Angeles Harbor College (LAHC), Los Angeles Mission College (LAMC), Los Angeles Pierce College (LAPC), Los Angeles Southwest College (LASC), Los Angeles Trade Tech College (LATTC), Los Angeles Valley College (LAVC), West Los Angeles College (WLAC), and the Los Angeles City College District Office, collectively LACCD, satellite campuses and select facilities. VoIP is a system for converting analog signals to digital signals so that telephone calls could be made over the internet. This standard will help ensure: Common Districtwide implementation practices Districtwide interoperability Implementation preparedness Standard integration and supportability Reliability and performance Energy efficiency & use of Green technology Consideration of life cycle maintenance Total cost of ownership The following standard applies to all LACCD full time, part time, temporary, consulting, engineering, integrators, and contract staff.

3 Technical Team: CFM Group Approval: Page 3 of 11 II. STANDARDS 1. Section 1: Overview This overview describes the general capabilities of the new IP based PBX telephone system. The new VoIP System will be a state of the art digital voice system, providing voice switching for LACCD. 1.1 The system will provide expedient and accurate call distribution for both digital and analog services for the LACCD students, faculty and staff. It shall be capable of routing internal and external calls within the LACCD s campuses including connections to local and long distance services. 1.2 The new IP based PBX telephone system will be a scalable and modular system that shall accommodate for future capacity as well as the addition of new features. The system will be based on an open industry standard architecture. 1.3 The new IP based PBX system shall provide full interoperability with the existing LACCD PBX systems. 2. Section 2: Pre implementation Guidelines A detailed plan should be developed to determine readiness, functionality, and overall system interoperability. The following guidelines will assist in determining environmental preparation for the successful implementation of VoIP technologies: 2.1 Evaluate current workload: Establish potential VoIP use cases 2.2 Network evaluation: Perform reliability and maintainability analysis of the Network to establish performance and capacity thresholds 2.3 Hardware and software: Consider VoIP hosting hardware and software based on LACCD standard practices. 2.4 Software: Carefully evaluate the software s capabilities to ensure that it supports the use cases 2.5 Data Center Suitability: Evaluation of mechanical, electrical and plumbing (MEP) support systems including HVAC, UPS, power, emergency generators, and fire suppression;

4 Technical Team: CFM Group Approval: Page 4 of 11 evaluation of rack/cabinet space and passive hardware including cabling, cable management, and termination panels see data center standard 2.6 Physical Infrastructure: Ensure proper distribution of copper and fiber media to all campus locations being served (see LACCD Infrastructure Standards) 2.7 Define VoIP system architecture: Consider use cases, network performance, Districtwide interoperability and standards 2.8 Administration: Determine whether the VoIP product management tools are sufficient or if more specific system management tools will be required to monitor the environment. 2.9 Develop a contingency plan to mitigate data loss or decreased system performance due to unexpected downtime. 3. Section 3: Voice over Internet Protocol Implementation Upon completion and approval of a detailed plan, a campus specification shall be developed to include overall requirements. The following standard implementation items should be included, as deemed necessary by the LACCD/Campus IT leadership, to address the scope of work included in the implementation. The following section is a synopsis of potential implementation tasks and requirements. 3.1 The selection of Voice over Internet Protocol will require design, procurement, installation, and commission of a telephone system to support the following areas: Classrooms/ Labs Administration Buildings Libraries Auditoriums Cafeterias Student/Staff Lounge Areas Open Areas as defined 3.2 The VoIP system will include: The end point devices (e.g. telephone sets) Private and Branch Exchange (PBX) call processing Unified messaging Interconnection of the IP based telephone system to the existing telephone

5 Technical Team: CFM Group Approval: Page 5 of 11 system (if applicable) Interconnection of the IP based telephone system with the new and existing paging systems (if applicable) Document preparation of an Owner approved operations and configuration document for each telephone device desired 3.3 The new system will include a new IP PBX system located in the LACCD designated area that will have the capability to perform as an independent PBX for the areas described in section above. If required, an approach for integrating with the existing PBX system will be developed The new IP capable PBX system must be scalable The scalability of the PBX system must accommodate extending features to those areas that are currently serviced from the existing PBX system Both analog and VoIP telephones shall provide full functionality call processing PBX System shall be capable of supporting analog devices, digital devices, soft phones and voice mail integration. 4. Section 4: Functional Requirements and System Parameters This section describes the IP based Telephone System functional requirements and system parameters. 4.1 If applicable, the new IP based PBX system shall be required to integrate with the existing voice mail system that will provide LACCD with voice messaging capabilities. Adequate voice mail port density including growth shall be incorporated into the design. 4.2 The new IP based PBX system shall provide IP telephones for the areas described in Section 2 A. Analog telephone connections shall be available for legacy devices, emergency phones and fax machines 4.3 Administration of the system will be provided from within an area meeting the environmental requirements defined in Section 2. The Administration system will provide monitoring and management of the new IP based PBX Telecommunication System and shall be accessible via the network and via web access. 4.4 The system will include security features that will provide the ability to prevent and track security violations.

6 Technical Team: CFM Group Approval: Page 6 of Due to the criticality of voice communications, it is imperative that the new IP based Telecommunications System be a "fault tolerant" system providing redundancy for all major components including battery and external generator backup. 4.6 The IP based system shall support Power over Ethernet (PoE) components 4.7 The system must constantly run internal diagnostics and have the ability to provide uninterrupted service even in the event of component failures. 4.8 The IP based telephone system must include the following Trunk Interface capabilities: Analog Trunk lines ISDN BRI/PRI lines OSIG IP trunks lines (H323/SIP) 4.9 The IP based telephone system must support the following Unified Communication features: Multiparty conference with clock to conference Multiparty data conferencing 4.10 The IP based telephone system must include the following Digital / IP Sets: IP sets to have large display (64 x 128 pixels) IP sets in medium and higher range to have built in QWERTY key pad to have dial by name IP sets to support up to 40 soft keys which can be managed with contextual keys with the help on a navigator Must have multiple line appearance buttons 4.11 The IP based telephone system must support the following Conference capabilities: Support multiple 3 party conference Support meet me conference (Minimum 6 users) 4.12 The IP based telephone system must support the following Music on Hold capabilities: To have option to program music of minimum 2 min To have external music on hold integration

7 Technical Team: CFM Group Approval: Page 7 of The IP based telephone system must support the following networking features: Support networking with other systems via Q sig over ISDN Line Support networking with other systems via IP trunks 4.14 The IP based telephone system must be Session Initiation Protocol (SIP) compliant 4.15 Codes The following section identifies standards and industry best practices specific to the IP based Telephone System United States Government Federal Communications Commission (FCC) CFR 15 Radio Frequency Devices Occupational Safety and Health Administration (OSHA) CFR 1910 Occupational Health and Safety Standards CFR 1926 Safety and Health Regulations for Construction CFR 15 Protection of Sensitive Security Information CFR 1520 Protection of Sensitive Security Information 5. Section 5: Components and Hardware This section defines the components and hardware of the IP based Telephone System. 5.1 At minimum, the new system must include an IP PBX that is capable of supporting the following features: Up to 100 TDM/IP users; expandable to 500 plus users WIFI for on site Voice & Data mobility Off site mobility with cellular client feature A built in CTI server to provide call management on every users workstation Pop up of incoming calls with caller ID on ISDN line List of incoming/outgoing and answered/unanswered calls Click to dial

8 Technical Team: CFM Group Approval: Page 8 of Integration with MS outlook to dial from user contact lists 5.2 The new PBX system must be capable of supporting the following future features: Unified messaging with Voic as.wav file in client Supervision feature with status (Free/Busy/forwarded etc) of all users The new PBX telephone system shall be capable of supporting an external battery with an inbuilt charger for additional power back up. 5.3 Grounding Provide an IP based telephone system grounded in accordance with the requirements specified in ANSI/TIA J STD Grounding Conductors Provide bare or insulated copper AWG wire grounding conductors complying with the requirements specified in ASTM B 3, ASTM B 8, and ASTM B For communications systems, provide stranded, insulated copper conductor having a minimum size of 6 AWG, since this will accommodate different code requirements and allow for future changes Where single conductor insulated grounding conductors are required, furnish green color (or tape marking) insulation rated for 600 volts. 6. Section 6: Functional Integration and Interoperability This section is a guideline for defining the potential systems requiring integration and interoperability with the IP based Telephone System. 6.1 Based on use cases and new IP based system capabilities, identify systems requiring integration and interoperability. 6.2 Some systems will require integration and/or interoperability with the Telephone System based on their required functionality.

9 Technical Team: CFM Group Approval: Page 9 of The following sample table denotes those systems that could potentially require integration and/or interoperability with the Telephone System. As part of the planning process, an integration and/or interoperability approach driven by the required functionality should be developed. SAMPLE SYSTEMS Access Control or Physical Security Systems Messaging/Emergency Communications Systems Paging System AV Control & Automation Digital Signage Systems Local Area Network Wireless Local Area Network Building Management Systems Master Clock Premise Distribution System Potential Integration/ Interoperability 7. Section 7: Support/Warranty 7.1 Cover all defects in workmanship and materials for five (5) years following purchase 7.2 All components included in warranty hour advance replacement of product 7.4 Local service for repair/replacement is preferred 7.5 Unlimited technical telephone support III. RELATED STANDARDS LACCD IT Standards, IT Infrastructure Design Standards Std LACCD IT Standards, IT Structure Cabling Systems Design Standards STD LACCD IT Standards, Districtwide Data Center Design STD LACCD IT Standards, Identity Management Standard LACCD IT Standards, Applications Standard LACCD IT Standards, Physical Security Standard LACCD IT Standards, Virtual PC s Standard*

10 Technical Team: CFM Group Approval: Page 10 of 11 LACCD IT Standards, AV Control & Automation System Standard LACCD IT Standards, AV Sound Amplification Standard LACCD IT Standards, AV Interactive Whiteboard Standard* LACCD IT Standards, AV Document Camera Standard L. LACCD Baseline Design Goals and Standards Classrooms, Chapter 1, Room and Space Specific Goals and Standards, Category A, Classrooms LACCD IT Standards, Videoconferencing Standard *These standards will be made available at a date and time to be determined by the District. Instructions on how to access these standards will be supplied at that time. IV. EXCEPTIONS OR WAIVER REQUIREMENTS Compliance Failure to comply with the exception or waiver requirements and process will lead to [insert] V. REQUESTS FOR CLARIFICATION A request for clarification on any of the standards listed above may be ed to [insert address]. In order to be considered, the request must include the following information: The specific standard number and title What aspect of the standard needs clarification One or two solutions VI. REFERENCES VII. American National Standards Institute (ANSI) Telecommunications Industry Association/Electronic Industries Association (TIA/EIA) Institute of Electrical and Electronics Engineers (IEEE) International Committee for Information Technology Standards (INCITS) Burton Group BICSI Cisco KEY TERMS & GLOSSARY Key Terms

11 Technical Team: CFM Group Approval: Page 11 of 11 Must means that the item or course of action is absolutely required. Shall means that the District intends that the supplier or consultant adhere to the instruction or command. Will means that the existing District systems or conditions require the item or course of action. Optional means that the consultant may choose to include or omit a particular item according to its preference. However, the item chosen must still interoperate or function with the District s existing systems. Minimum of means that the stated item or course of action meets the standard but may be superseded. Glossary The following terms are defined as follows: Need means that the item or course of action is essential and it will be absolutely required at the time indicated in the standard. (e.g., a high level risk assessment needs to be performed ) Call for means that the item or course of action is absolutely required. Are to be provided means that the item or course of action must be supplied in order to meet the standard. May be required if means that if the condition stated in the standard is met, the capability, performance expectation, or any other description in the standard is absolutely required. Recommended means that the course of action is in accordance with (Insert Applicable Area such as Security) Best Practices and should be adopted. Not Recommended means that a course of action is not consistent with (Insert Applicable Area) Best Practices and/or other laws, codes, or requirements and should not be adopted. May/Might/Can mean optional. The items specified using this language may be included or omitted depending upon the consultant/vendor s preferences. However, even if one particular item is optional, the item chosen must still interoperate or function with the District s existing systems. Preferred/encouraged mean that one item or course of action is favored over other optional courses of action because of proven favorable outcomes. Acceptable means that the item or course of action is only a minimum, and the consultant may supersede the quality or performance of that item or course of action. VIII. DOCUMENT HISTORY REV # DATE PAGE, PARA # CHANGE DESCRIPTION OF CHANGE APPROVAL SIGNATURE & DATE