Attachment 6 Questions and Answers- FA487726QA500.pdf

Q&A – FA487726QA500

1. Can the Government confirm the current incumbent carrier/provider supporting the existing SIP trunking and Local Telecommunication Services for the 520-228 and 520-202 DID ranges?

Lumen, and we need to include that they also support 520-334-68xx and 520-334-69xx and any other 610 CACS numbers that were cut over finally.

2. Is there an existing baseline for concurrent call path/session capacity currently provisioned, or should offerors determine appropriate SIP session capacity based on the 11,000 DID inventory and operational assumptions around 10-12% of DIDs as concurrent call requirement

For DISA, we baselined at about 165 concurrent calls but that is for DSN.

3. Can the Government confirm ownership and responsibility for Session Border Controllers (SBCs), if currently deployed, and whether contractor-provided SBC functionality is expected as part of the proposed solution? If so is there a preferred OEM vendor /Model

We own and operate our SBCs that then interconnect with the current providers equipment through a boundary network switch which we own and operate as well.

4. Are there any specific failover, redundancy, or logical resiliency expectations beyond the stated 99.9% uptime requirement, particularly regarding emergency services and E911 continuity?

No and e911 is handled within our Base Area Network.

5. For E911 routing, can the Government confirm whether all emergency call routing must terminate directly to the Davis-Monthan AFB Fire Department, and whether any existing PSAP integrations or special routing configurations must be preserved?

E911 is handled on prem by our Base Area Network. 911 calls do not get passed to the service provider if they originate on our telephone network.

6. Are there any incumbent interconnection agreements, Local Number Portability considerations, or carrier-specific constraints that the Government is aware of that may affect transition planning for the 11,000 DID numbers?

The government is unaware of any incumbent interconnection agreements which would warrant consideration for transitioning the DID numbers.

7. Can the Government confirm whether all contractor-provided CPE through the demarcation point must be located within the contractor rack space identified in Building 5150, and whether any additional site access or coordination constraints should be considered?

CPE must be located in building 5010 and site (base) access will require individuals to pass background checks and have a Real ID.

8. Are there any known transition blackout periods, mission windows, or operational restrictions that would affect number porting, testing, or final cutover scheduling?

Hard to say since we have all these mission partners. Ultimately, the cutover should be accomplished within a single day to reduce mission impact.

9. Can the Government please confirm the expected or required DID porting timelines? For example, will porting be completed in phases? Must all 11K DIDs be fully ported to the winning provider within a certain amount of time?

The actual porting should occur all at once by the winning provider, this is how we accomplished this in the past.

10. Please advise what IP PBX make, model and software version number will be deployed by the Government for use with the requested SIP trunks.

Cisco C8300s are our SBCs running version 17.12.5 as of today. Cisco CUCM version 15 is our Call handler for base telephone service.

11. Please clarify the scope of services being requested. This appears to be a request for SIP trunks for local voice access to the PSTN, however all categories of service in Sections 5.3 – 5.8 are marked “N/A” and Section 1.2 states “the Government requires SIP trunking services delivered over IP-based infrastructure to support voice, video, and real-time communications.” For the requested services, please state the required quantities such as peak number of simultaneous calls, monthly minutes of long distance use or unlimited long distance, etc. (other than the noted 11K DIDs).

We are looking at roughly 43k calls a month with around 4.3 million total minutes. Peak calls simultaneously could be 200 but needs the ability to fluctuate. Bidders should identify whether they can support unlimited long distance and how much they would charge, and how much packages of long distance monthly minutes would would charge.

12. Please clarify this requirement from Section 5.12 “All 911 calls that generate on-base to the base switch (internally) must also be routed to the Davis-Monthan AFB Fire Department.” Should bidders understand this to mean that the DMAFB IP

PBX (“the base switch”?) will originate 911 calls onto the winning bidder’s SIP trunks and those SIP trunks must route those calls to the DMAFB Fire Department?

E911 is handled internally by the Base Area Network, we do not pass e911 data to the local carrier. We do send 988 (National Suicide Hotline) to the carrier however, just not sure if that is considered e911 based traffic.

13. Please clarify the relationship between Section 5.12 requirements “access to 911/E911 services..through thelocal city or county emergency services organization.” versus “All 911 calls that generate on-base to the base switch (internally) must also be routed to the Davis-Monthan AFB Fire Department.” Is DMAFB Fire Department considered a “local city or county emergency services organization”?

E911 is handled internally by the Base Area Network, we do not pass 911 data to the local carrier. We do send 988 (National Suicide Hotline) to the carrier however, just not sure if that is considered e911 based traffic.

IF THERE ARE ADDITIONAL QUESTIONS THAT A REPRESENTATIVE OF YOUR COMPANY

HAS SUBMITTED DURING THE SUBMISSION PERIOD THAT HAVE NOT BEEN

ANSWERED, PLEASE FORWARD THEM TO THE LISTED ALTERNATE POC MR. JERRY

SAUDER.