Vendor RFI and Responses (cao 20241205).pdf

RFI # Question Government Response

PWS Local Telecommunication Services (LTS) Conversion from LSTDM to SIP Trunking,

1.1 Objective provides:

“All connectivity requirements and features currently transported over the existing LSTDM must be migrated to an emulated SIP path without loss of capabilities. This PWS is for managed SIP circuit”.

Appendix 1, Site Specific Requirements provides for:

5.2 Direct-Inward-Dialing 1,500 numbers range (314) 527-7500 to 8999. These numbers appear to be MCI Metro formerly Worldcom numbers. MCI is part of Verizon.

5.4.3 Specifies PRI #1 with 1 D channel and 23 2-way B channels. Please confirm that this is a new PRI.

It is very unusual for one PRI to support 1,500 telephone numbers.

Managed SIP circuit is not listed as a site-specific requirement.

How do the site-specific requirements meet the objectives?

The requested emulated SIP solution will replace 1 PRI with 23 bidi voice channels, and 1 standard T1 with 24 bidi voice channels for a current total of 47 concurrent calls (excluding DSN). The 1500 DID's are the pool of numbers available to us currently. Our requirement is to retain this DID pool and maintain an equal or greater number of concurrent calls with local and long distance voice capability for any new PSTN connection proposal.

PWS 5.1 states “The Government telephone switching system is identified as an Avaya CM7 and associated software, and the switching system is located at 39 Kearney St., St. Louis, MO 63125.”

How many PRI can this system accommodate?

The number of PRI's our system can accomodate is limited by number of media gateways and number of T1 cards / card slots. Our PBX's current configuration can accomodate up to 6 PRI's, with 1 reserved for DSN, expandable to 8 if 2 additional T1 cards are procurred.

Instead of continuing with existing Avaya and proposed Cisco legacy on-prem telephone equipment, would Jefferson Barracks consider replacing its on-prem telephone system with an Unified Communications as a Service (UCaaS) solution?

No. A modification to our local PBX is not within the scope of this contract.

4 How many call paths are required? We are requesting 48 call paths.

5 How is the Government utilizing BRI service currently? 2 TDM circuits are currently utilized, 1 for local call routing, and one for long-distance call routing.

Managed service - Is the only required handoff, from the managed router, a single BRI? If more than just the BRI handoff is required, can the Government elaborate on the requirement?

2 TDM handoff's are required, supporting 46-48 concurrent 2-way calls depending on local t1 implementation.

To alleviate staffing issues during upcoming Thanksgiving holiday week, we are requesting a three week extension past the current due date.

Due date extended on Amendment 1.

Could you confirm if this opportunity is new work or a continuation of existing work? If it’s a continuation, is there an incumbent currently performing the work?

This is new work to replace 2 existing TDM voice circuits.

We kindly request a two-week extension to the submission deadline to ensure a thorough and high-quality response. Please let us know if this is possible.

Due date extended on Amendment 1.

1.1 Objective provides:

“All connectivity requirements and features currently transported over the existing LSTDM must be migrated to an emulated SIP path without loss of capabilities. This PWS is for managed SIP circuit”.

Please see attached twilio interopguide for avaya. The interopguide uses avaya cm 8.1.x as an example. twilio would connect to the avaya sbce which also connects to the avaya cm. please see Figure 1 Network Topology in attached interopguide. Is this what you expect for your managed sip circuit?

Our Avaya CM7 does not have Session Manager, and cannot natively support SIP. The request is for emulated SIP over ip from ISP with local TDM handoffs to the PBX.