SAM FA282324Q3028 Q-n-A as of 3Mar25.pdf
PDF 77 KB Posted
- Attached to
- Full Phone Service Eglin AFB
- Solicitation number
- FA282324Q3028
About this file
This is a Questions and Answers document for solicitation FA282324Q3028 regarding full telephone service at Eglin AFB. The document addresses technical requirements and specifications for SIP trunking and related telecommunications services.
Key details include: The solution must use SIP trunking delivered to Eglin's central office and handed off to their Call Manager via T-1/PRI, with no direct IP trunking connection allowed to maintain separation between Air Force and Commercial networks. The requirement involves porting 30,000 phone numbers (850-882-XXXX/ 850-883-XXXX/ 850-885-XXXX), with 345 SIP trunk channels needed. Call volume statistics show approximately 190,616 local calls and 211,120 CONUS calls over a 120-day period, with minimal OCONUS traffic (98 calls). The two SIP trunks will terminate in Building 252 at Eglin AFB in an active/active configuration. Additional requirements include 4-wire shout lines for FAA partners and dry copper OSP circuits for facilities without government-owned infrastructure. 911 services are not required as they route directly from the Avaya CM to an on-base PSAP. The government will provide Avaya technical support during implementation.
View the file
Other files
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
SAM:FA282324Q3028 QUESTIONS & ANSWERS
1. Would a solution whereby your calls are handed-off to our switch via an IP routing from your Avaya Call manager be an acceptable solution? In this way there would be minimal changes to your existing arrangement. Simply put, your calls would route to our platform for outbound termination.
At no time will there be a direct connection of an external IP trunking into the Avaya Call Manager. There is a requirement for separation of the Air Force Network and Commercial network IP’s. The service must be delivered to Eglin’s central office via SIP trunking and handed off to our Call Manager via T-1/PRI.
2. If the above is not suitable, please state what additional solutions will be plausible.
The service must be delivered to Eglin’s central office via SIP trunking and handed off to our Call Manager via T-1/PRI in order to keep the separation of Commercial and Air Force Networks. This is the only acceptable solution.
3. The PWS list 30,000. How many are active? This will be useful in pricing.
Eglin owns all 30,000 numbers per the local LEC and will need them all ported to the new SIP trunks.
4. PWS 5.4.3 list TWO SIP trunks to Bldg 252, yet 5.3.1 shows FOUR possible demarcation points. Please confirm if the TWO SIP trunks are located at 402 West “D” Avenue, Building 252, Eglin AFB, FL 32542, or otherwise.
The 2 SIP Trunks will terminate in Building 252, 402 West D Ave. Eglin AFB, FL 32542. The numbers listed in 5.3.1 will need to terminate in the addresses indicated in the PWS.
5. Can we get an estimate outbound call traffic (CONUS)?
LOCAL
Nov 1 - Feb 28 (30,31,31,28) = (120 days) 190,616 Total Calls 9929:56:22 hr:min:sec
1588.46 calls/day
6.25 avg/call
FTS CONUS
Nov 1 - Feb 28 (30,31,31,28) = (120 days) 211,120 Total Calls 11,068:00:25
1759.33 calls/day
6.30 avg/call
6. Is there OCUNUS traffic? If so, are you asking for a flat rate or can this be a pay per minute per destination?
Which ever rate is most cost effective to the government.
7. Are the analog lines, PWS 5.3.1 connected to the Avaya Call Manager, as well?
NO
8. We are not certain how PWS 5.6 is related to the outbound call component of this RFP. Can you elaborate?
These are 4 wire shout lines utilized by our FAA partners and the connection runs through local vendor transport equipment. Must be included in the solution.
9. We are not certain how PWS 5.7 is related to the outbound call component of this
RFP. Can you elaborate?
These are dry copper OSP circuits leased from the local vendor servicing facilities on the local base not containing government own OSP.
10. PWS 5.12 states E911 = NA. Are you NOT asking for 911 service?
NO, 911 services are routed from the AVAYA CM directly to a PSAP on base.
11. The install will require your Avaya Call Manager to handoff the call to our router at the demarc. Will you be providing your Avaya tech to assist?
YES
12. What is the total number of local minutes used on average over a four-month period?
Please see the answer for Question 5 listed above.
13. What is the total number of long-distance minutes used on average over a four-month period?
Please see the answer for Question 5 listed above.
14. What is the total number of international minutes used on average over a four-month period?
FTS OCONUS
Nov 1 - Feb 28 (30,31,31,28) = (120 days) 98 Total Calls 8:34:59 .81 /calls/day
10.49 avg/call
15. Please confirm the required number of SIP trunk ports/channels is 500.
To match current T1/PRI service, 345 is required and will be sufficient.
16. Please confirm the total number of DIDs is 30,000.
YES, 30,000 850-882-XXXX/ 850-883-XXXX/ 850-885-XXXX
17. What is the estimated number of DIDs that will require 911 provisioning on average?
Only the 4 lines listed in the PWS section 5.3.1 will need 911 routing since they do not terminate in the base call manager.
18. Is this requirement solely for SIP trunking?
NO, all items listed in the PWS must be included.
19. Can CSL be ported over SIP trunk? If no, will you accept and alternate solution?
NO, Commercial Subscriber Lines are in place for emergency services do to a catastrophic outage.
20. For the two SIP circuits; will they be active, active? Or active, standby? Are you looking for POP diversity? Is there a second entrance?
Active/Active do to expected call volume. Infrastructure does not support a POP diversity or second entrance.
21. For PWS 5.6; can you share the equipment type, application use?
No, equipment is owned by another vendor.
22. For PWS 5.7; Is Loc A the same? Equipment and application use?
No equipment is attached by the vendor, these are dry copper connections extending base services to facilities that do not have Air Force owned OSP.
File details come from the government source that posted it. Updated .