RFP_8100_JNH3000_ADD_5_v1.pdf
PDF 114 KB Posted
- Attached to
- Aviation Telephone System & Services
- Solicitation number
- RFP 8100 JNH3000
- Issued by
- Texas
About this file
This is Solicitation Addendum No. 5 for RFP 8100 JNH3000 issued by the City of Austin Financial Services - Central Procurement, dated August 19, 2026, addressing enterprise telephony and unified communications system replacement and support services at Austin-Bergstrom International Airport. The addendum incorporates clarifications to the original solicitation through ten question-and-answer pairs addressing technical specifications and system requirements. Key details clarified include the current phone inventory (Cisco 8811s and 8851s, NEC DT400 series), existing server specifications (2 vCPU Intel Xeon Gold 6326 @ 2.90GHz with 10,240 MB RAM and 110 GB disk), current Cisco Unified Communications Manager version 15.0.1.12900-234 running on VMware ESXi 8.03, and the requirement to accommodate approximately 30-35 hunt groups across both legacy systems. The solicitation addresses system integration preferences, including flexibility regarding existing Ribbon Session Border Controller repurposing and support for SIP trunks or PRIs to maintain full operational continuity of legacy NEC/Cisco systems during deployment. Additional clarifications confirm that call recording utilizes NICE systems rather than SIPREC or Call Manager profiles and that no paging systems are included in the project scope.
The addendum specifies that all other terms and conditions from the original RFP remain unchanged. Offerors are required to acknowledge receipt and understanding of the addendum by returning a signed copy with their proposal submission prior to the solicitation closing date of August 27, 2026 at 2:00 PM CT, with failure to do so potentially constituting grounds for offer rejection. The City maintains flexibility regarding vendor selection for replacement infrastructure components, allowing offerors to propose solutions based on technical merit and capability to support the consolidation of existing Cisco and NEC systems into a single premises-based VoIP platform while maintaining system availability throughout the 270-day implementation period.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP_8100_JNH3000_ATT_12_v1.pdf | ||
| RFP_8100_JNH3000_ATT_4_v1.pdf | ||
| RFP_8100_JNH3000_ATT_13_v1.xlsx | XLSX spreadsheet | |
| RFP_8100_JNH3000_ATT_8_v1.pdf | ||
| RFP_8100_JNH3000_ATT_10_v1.xlsx | XLSX spreadsheet | |
| IFB_2200_CSH1061_ATT_10_v1.docx | DOCX document | |
| RFP_8100_JNH3000_ATT_9_v1.xlsx | XLSX spreadsheet | |
| RFP_8100_JNH3000_ADD_2_v1.pdf | ||
| RFP_8100_JNH3000_ATT_15_v1.pdf | ||
| RFP_8100_JNH3000_ADD_1_v1.pdf | ||
| RFP_8100_JNH3000_ATT_2_v2.pdf | ||
| RFP_8100_JNH3000_ATT_1_v7.pdf | ||
| RFP_8100_JNH3000_ATT_4_v2.pdf | ||
| RFP_8100_JNH3000_ATT_3_v1.pdf | ||
| RFP_8100_JNH3000_ATT_1_v1.pdf | ||
| RFP_8100_JNH3000_ATT_6_v1.pdf | ||
| RFP_8100_JNH3000_ATT_14_v1.pdf | ||
| RFP_8100_JNH3000_ADD_4_v1.pdf | ||
| RFP_8100_JNH3000_ADD_6_v1.pdf | ||
| RFP_8100_JNH3000_ADD_3_v1.pdf | ||
| RFP_8100_JNH3000_ATT_5_v1.pdf | ||
| RFP_8100_JNH3000_ATT_7_v1.pdf | ||
| RFP_8100_JNH3000_ATT_2_v1.pdf | ||
| RFP_8100_JNH3000_ATT_11_v1.xlsx | XLSX spreadsheet |
Show all 24
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SOLICITATION ADDENDUM
AUSTIN FINANCIAL SERVICES – CENTRAL PROCUREMENT
Revised 10/01/2024
Solicitation: RFP 8100 JNH3000 Addendum No: 5 Date: 08/19/2026
This addendum is to incorporate the following changes to the above referenced solicitation:
1.0 Questions:
1. Q: Would the City prefer to repurpose any of the existing phone models with the new solution? If yes, can you please list out the model numbers and quantities for each type of phone that are currently in use?
A: There is no preference. Cisco phones are mostly 8811s, some 8851s. NEC phones are mostly DT400 series.
2. Q: What is the current server model being used for the existing Cisco collaboration applications? If the City would like to repurpose these servers for the proposed solution, please also list the total RAM, Physical CPU Cores (with clock speeds), and disk space available for each model.
A: The current Cisco deployment is virtual only.
The system version: 15.0.1.12900-234.
The VMware Installation: 2 vCPU Intel(R) Xeon (R) Gold 6326 CPU @ 2.90GHz, disk 1: 110 Gbytes, 10240Mbytes RAM, Partitions aligned.
3. Q: Would the City prefer to keep the existing Ribbon SBCs or should replacement models be included in Offerors’ responses? If new SBCs are preferred, are they required to be Ribbon devices or is the City open to other vendors/models?
A: There is no preference. It is up to the offeror.
4. Q: How many hunt groups are required for the solution the City is seeking?
A: Cisco environment has ~15 hunt groups and NEC PBXes have another 15-20. Proposals from offerors need to be able accommodate at least that many.
5. Q: Since the legacy NEC/Cisco environment needs to remain fully operational throughout the deployment, would the City prefer to integrate the proposed solution via SIP Trunks or PRIs to enable sending calls between the three systems throughout the implementation? If yes, will the existing NEC PBX support a SIP trunk or is a PRI required?
A: NEC PBX can accommodate SIP trunks or PRIs, there is no preference.
6. Q: What are they using for call recording capture: SIPREC on the SBC or using the Call recording profile on the Call manager.
A: All call recording is currently done via NICE.
7. Q: What is the base clock rate on the target server, Need the server model, Clock, number of cores, RAM?
A: The Cisco UC server specs are as follows:
2 vCPU Intel(R) Xeon(R) Gold 6326 CPU @ 2.90GHz, disk 1: 110Gbytes, 10240Mbytes RAM, Partitions aligned.
SOLICITATION ADDENDUM
AUSTIN FINANCIAL SERVICES – CENTRAL PROCUREMENT
Revised 10/01/2024
8. Q: What are we connecting to for paging FXS, FXO, SIP?
A: There are no paging systems in the scope of this project.
9. Q: What is the current version of Call Manger you are running on?
A: 15.0.1.12900-234
10. Q: What ESXI version are you running today?
A: 8.03
2.0 ALL OTHER TERMS AND CONDITIONS REMAIN THE SAME.
ACKNOWLEDGED BY:
Offeror Name Offeror Authorized Signature Date
RETURN ONE COPY OF THIS ADDENDUM WITH YOUR RESPONSE PRIOR TO THE SOLICITATION CLOSING
DATE. FAILURE TO DO SO MAY CONSTITUTE GROUNDS FOR REJECTION OF YOUR OFFER.
Solicitation: RFP 8100 JNH3000 Addendum No: 5 Date: 08/19/2026
File details come from the government source that posted it. Updated .