My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt15 Packet Fusion
RedwoodCity
>
City Clerk
>
Agreements
>
2010-2019
>
2015
>
Agmt15 Packet Fusion
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/7/2015 4:35:42 PM
Creation date
10/7/2015 4:33:32 PM
Metadata
Fields
Template:
Agreement
Contractor Name
Packet Fusion
PROJECT NAME
New Telephone System
RMP File Number
304
Date
10/7/2015
MO Ref
15-160
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
69
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
EXHIBIT "A" SCOPE OF WORK <br /> Feature to be implemented Description <br /> Warm Standby or Secondary call processor with a current copy of the <br /> Active/Passive - Redundancy database. Upon failure of the main call processor <br /> phones will register and start to accept call control <br /> from the second processor. This may involve the <br /> disruption of calls that were already in progress. <br /> Switchover should take less than 5 minutes and be <br /> automatic without human intervention. <br /> Hot Standby/Mirrored — Hot standby call processor with a synched database <br /> Redundant copy that will take over from the main call processor <br /> if there is a failure. Failover should be automatic <br /> and maintain the same user functionalit _ <br /> Complete Branch Survivability All locations will continue to process calls correctly <br /> for all applications with local dial-tone, ability to send calls to voicemail, <br /> simple ACD routing, etc. if the WAN connection to <br /> the central call processor fails. <br /> Disaster Recovery - Cold Cold servers are placed into a remote DR facility <br /> Standby and a back-up is restored (or active <br /> synchronization) in the case of a catastrophic failure <br /> of HQ. Requires manual intervention. (Geographic <br /> redundanc also meets this re uirement. <br /> Business Continuity - Backup redundant senrers for the phone system, <br /> Geographic redundancy voicemail, and other core telephony applications are <br /> lacated at a remote location and remain <br /> synchronized with active servers. Phones should <br /> re-home automatically and feature functionality <br /> should be virtuall identical to normal o eration <br /> High Availability PSTN SIPs, PRI, analog ports and Fixed Wireless <br /> Gateway resources should be distributed among the <br /> atewa s to allow for resilienc . <br /> Restorable Network Back-up Phone system, ACD, voice mail, and other critical <br /> telephony servers will automatically back up all <br /> system programming to a network drive on a regular <br /> schedule, with included software, without service <br /> interru tion. <br /> Voicemail back-up without Voicemail will automatically back up all <br /> messages programming and greetings on back-ups, but not <br /> back up messages in order to reduce back-up <br /> duration and size, and avoid le al retention issues. <br /> Networking and VoIP: <br /> Single System Functionality System will allow all users to feel like they are part <br /> of one big system with full feature functionality <br /> between locations. <br /> Single Telephone System and System operates as one phone system with a single <br /> Database administration database, not a collection of <br /> REV:08-28-15 MLG <br /> Page 30 of 69 <br /> ATTY/AGR.2015.207/Packet Fusion New Telephone System <br />
The URL can be used to link to this page
Your browser does not support the video tag.