The Vendor is required to provide to replace its existing Cisco Unified Communications Manager (CUCM) telephone system with a cloud-based VOIP (Voice over Internet Protocol) system.
- These servers operate as a primary and secondary failover.
- City has reviewed common VOIP system features and functions and developed the listing of system requirements shown below:
• Call forwarding
• Call transfer
• Caller ID
• Call routing
• Three-way call
• Auto Attendant
• IVR
• Call queues
• Custom MOH
• Voicemail
• Voicemail transcription
• Video conferencing
• Call recording
• Call analytics
• Anonymous call rejection
• Wireless phone sets
• Mobile App
• Number porting
• Call screening
• ATA (Analog device connectivity)
• Paging system interface
• Recorded hotline number
- Essential Requirements - New System
• Handsets. Configuration determined based on unit pricing and functionality, including desk handsets and conference rooms.
• Voice Mail “Announcement mailboxes” –Departments may use these for general mailboxes not tied to an individual or to provide information without allowing the caller to leave a message. Include system capabilities, and the ease of use
• The system has the capabilities to send voicemails to email.
• Calling auto attendant(s)
• Call routing
• Call transferring
• Do not disturb
• Three way calling
• City Directory – Vendors are asked to provide detail on how this is maintained on your system.
• Emergency Notification – Provide details on how your solution notifies key public
• Safety personnel when 911 is dialed from a City phone.
• Training for staff members
- This functionality may have benefit for the city with “ad hoc recording” available as needed by city staff.
• A mobile app to take calls on a mobile device.
• Software used to take calls on a desktop/laptop computer, such as a softphone.
• Video Conferencing
• Call reporting.
- Mandatory walk-through Date: February 18, 2026