Questions-RFP BPM058210.pdf

RFP BPM058210 – Questions/Responses # Questions UMD Response(s)

1 Under section 1.4, Requirements "Voice Services Requirements": Are those requirements for the SIP Trunking or for the Unified Communications Platform?

Alternately, are those requirements for a PBX system? I'm seeking a little more clarity on that section. For example, V-001 the SIP trunking will include a bucket of 300,000 minutes but is V-004 asking if the SIP trunk will support those features or is the university looking for a phone system to provide those features?

UMD is not looking for a PBX as part of this RFP. The SIP Service should include the features of V-004 as an optional override to default call routing to the intended SIP circuit(s). 300,000 monthly minutes should be shared across all SIP circuits.

2 SIP Trunk Requirements: S-002: Will the University be porting the 32,000 DIDs?

Yes, the University currently owns 32,000 DIDs, and we wish to port to the new SIP Service.

3 Service Locations:

a) University of Maryland 2740 Comcast, College Park, MD 20742: Please verify address. How many Toll Free numbers at this location?

b) UMD Atlantic Building 4254 Stadium

Dr, College Park, MD 20742: Is this the main location that requires the two SIP trunks with 200 Concurrent Call Paths?

c) UMD California, MD 44219 Airport Rd, California, MD 20619: How many POTS at this location? What is the Dynamic IP referenced? This location requires 1 SIP

Trunk with 20 Concurrent users.

d) UMD College Park 2113 Chesapeake

Bldg, College Park, MD 20742: Please confirm address Google is returning: 2113 Chesapeake Building, 4300 Terrapin Trail, College Park, MD

20742. How many POTS at this location?

e) UMD Patuxent Building 1 University of

Maryland, College Park, MD 20740:

Please confirm address. Google is returning 4161 Fieldhouse Dr, College

Please see updated Service Location table after question 78 for breakdown of site & call paths

Dynamic IP implies a vendor-managed, directly peered SIP Circuit. We do NOT want any SIP Trunk to ride over commodity internet.

a. No toll-free numbers specific to the Comcast building itself. Nothing is at that address at this time.

b. UMD Atlantic Building is one of two locations at the main UMD site, requiring 200 call paths

c. There are no POTS lines at the UMD California site. Please see comment above about Dynamic IP. POTS lines are not part of this RFP

d. Regarding 2113 Chesapeake: We do not have POTS lines or active carrier service at the Chesapeake building. That location likely appeared as a legacy billing address at some point. Please do not include this address.

Park, MD 20742. What is Dynamic IP referencing? How many Voice Users at this location? How many Toll-Free lines?

f) UMD IBBR Building 9600 Gudelsky Dr, Rockville, MD 20850: What is Dynamic

IP referencing? How many Voice Users at this location? How many Toll-Free lines?

e. 1 University of Maryland - dummy address for the Verizon POP, before Building 10 (Patuxent) had a “civic” address of 4161 Field House Dr. Do not include this address. See comment above about Dynamic IP. UMD Patuxent Building is one of two locations at the main UMD site, requiring 200 call paths each. The main UMD site includes approx 9,000 “knowledge workers”

4 The RFP document stops at page 60 of 67. This is a typo. The source doc had page 1 start 7 pages later than it should have.

5 Attachment C only has the instructions; no price sheet was included.

Attachment C will be resent via an amendment. It will be an actual Excel sheet to complete.

6 Part of the RFP states that questions are due 3 days before the pre-bid conference which would be 8/4, but then it also states the deadline for questions is 8/12.

The first cutoff date of August 4th for questions was for any question(s) that an attendee would want addressed at the Pre-Proposal conference. All questions and responses from August 4th and August 12th will be published in an amendment to the RFP for all.

7 Existing PBX Architecture & Session Border Controllers (S-005 Interoperability) Regarding requirement S-005 ('Provide interoperability with existing Private Branch eXchange infrastructure'), could the University specify the make, model, software versions, and primary Session Border Controllers (SBCs) currently deployed across the College Park, IBBR, and USMSM campuses? Additionally, is UMD expecting the vendor to hand off SIP trunks directly to on-premises SBCs via cross-connect, or via vendor-managed edge gateways?

The university currently uses Cisco ISR4431 running IOS-XE 17.12 at all locations for our SBCs. A single centralized Cisco Unified Communications Manager 15 cluster is the PBX behind all SBCs.

UMD prefers the vendor to hand off directly to these on-prem SBCs, providing a /30 IP block to each SIP Circuit as indicated in S-008. If the vendor solution requires their own managed edge gateways, this *MUST* be priced into their response

See Diagrams at end of Questions.

8 Analog POTS Lines vs. Modernized IP/Cellular Gateways (P-001) Regarding the 92+ analog lines required in P- 001 for life-safety elevators, fire/burglar alarms, and fax machines: Will UMD accept cloud-managed Analog Telephone Adapters (ATAs) or cellular survivable POTS replacement gateways (e.g., POTS-in-a-Box) provided by the vendor, or does the University require

POTS lines are not to be considered for this

RFP.

traditional copper central office lines delivered directly by an Incumbent Local Exchange Carrier (ILEC)?

9 LPTA Evaluation & Desirable Cloud UC Pricing

(UC-001 / D-002)

Under the Lowest Price Technically Acceptable (LPTA) evaluation methodology, how will optional/desirable requirements like UC-001 / D-002 ('Integration with cloud service providers such as Microsoft Teams Phone, Zoom Phone, Webex Calling or similar platforms') be weighted in the financial evaluation? Will optional UC subscription pricing on Exhibit C be included in the total price calculation used to rank offerors, or will financial ranking be evaluated strictly on the mandatory SIP Trunking, DID, Voice, and POTS line costs?

Strictly Mandatory.

Scope of R1 Higher Education Reference Requirements (Section 3.1.1.1) Section 3.1.1.1 requires offerors to provide references for at least 3 successful deployments at R1 research institutions with 25,000+ undergraduate students. To ensure full compliance, does the University require these reference accounts to demonstrate scope specifically in SIP Trunking / Enterprise Dial-Tone migration, or will references demonstrating large-scale Cloud UC/UCaaS deployments at R1 universities also satisfy this mandatory qualification?

The university requires references specific to SIP Trunking / Enterprise Dial-Tone migration. References to any other offering are irrelevant and will be ignored.

Is the university considering a replacement of the existing legacy on-premise PBX system and migrating to Cloud UCaaS? Or is the university only considering submissions that offer phone service trunking to connect to the existing PBX?

This is for SIP replacement only.

Can you please explain the fiber route diversity requirements for this RFP?

UMD wants last-mile diversity to our main site and to IBBR. We want separate geographic and vendor diversity for last-mile connectivity. UMD requires physically diverse local access paths from separate vendors, with separate building entrances/demarcations, at our College Park campus and at IBBR sites.

Geographic diversity: For the geographically distinct SIP circuits at UMCP and IBBR, please define the required level of diversity. Does UMD require physically diverse local access paths, separate carrier POPs/SBCs, separate building entrances/demarcations, or some combination thereof?

See Question 12.

DID inventory: Please provide the current DID inventory/NPA-NXX ranges and clarify whether the stated minimum 32,000 station numbers represents numbers currently assigned, total reserved numbering capacity, or the minimum DID block capacity the provider must support.

UMD will provide at a later time if required. For purposes of RFP response, assumption is stated minimum 32,000 station numbers at this time.

Is it possible to provide the current PBX/voice environment by site, including Cisco CUCM versions, SBC manufacturer/models/software, voicemail platform, fax servers, trunk signaling/security settings, codecs, and any required interoperability certifications.

See diagrams below; we will not provide data beyond that.

Fax servers are not part of our environment, but we do require T.38 FOIP support. Inbound and outbound calls must use the G. 711 codec

E911: Please describe UMD's current E911 architecture and location-management process, including the approximate number of locations/endpoints requiring location records and whether UMD expects the awarded provider to supply an E911 management portal/database

E911 is not required for this RFP, but the vendor should be able to deliver 911 calls to local PSAPs for each SIP circuit. (AOR)

Can you clarify whether wireless backup capabilities are desired for SIP resiliency?

This is not a requirement for this RFP

Is the 300,000 minutes per month a guaranteed bundled allowance, an estimated usage baseline, or a minimum capacity requirement? Can UMD provide at least 12 months of historical usage by local, domestic long distance, international, and toll-free traffic, including peak-hour/peak-day volumes.

Current minutes used last year:

Month In Out Combined

Jun 25 125,664 54,752 180,416

Jul 25 171,282 61,737 233,019

Aug 25 319,542 89,260 408,802

Sep 25 157,375 60,940 218,315

Oct 25 136,070 59,530 195,600

Nov 25 151,517 65,973 217,490

Dec 25 106,806 46,804 153,610

Jan 26 177,449 62,269 239,718

Feb 26 274,478 111,488 385,966

Mar 26 209,421 87,398 296,819

Apr 26 286,753 123,186 409,939

May 26 156,791 73,512 230,303

Can you speak to the MBE goal percentages for the

RFP?

There is no MBE goal for this particular requirement, however, UMD has a 29% participation overall goal for UMD Procurement activities.

SIP Refer support? IPv6? UMD can support IPV6/4. Clarify SIP

REFER.

Section 3.1.1.1.iii and 3.1.1.1.v require at least three reference accounts from higher-education institutions with 25,000+ undergraduate students, including at least one R1 institution. Will the

University accept references from large-scale, multi-site SIP trunking and voice deployments at comparable public-sector or K-12 institutions of similar technical complexity and call-path volume, in lieu of a reference from a four-year university, or is this requirement strictly limited to four-year institutions of the stated size?

This will need to be a vendor’s decision in submitting a proposal. UMD has stated it’s requirements for technical format and references to be considered for award.

Section 4.1.4.1 asks offerors to describe their

Business Inclusion and Supplier Diversity

Program. For offerors without a formally named program, is a narrative description of relevant practices and goals sufficient, or is a formal, named program required?

Relevant practices and goals are sufficient.

Section 4.1.5 asks offerors to identify sustainability measures and eco-labels used by the company.

Please confirm whether this section carries any pass/fail weight in the technical evaluation, or whether it is informational only.

This is not mandatory and will be treated as informationally only.

Requirement BA-002 (email response within 2 business days, updates within 7 business days) is listed as Desirable. Please confirm whether

Desirable items are scored in any way, or whether they are informational only and do not affect the

"Fully Meet" / "Don't Meet" technical acceptability determination under Section 3.2.2.3.

Desirable items are not scored. They are informational only.

Current Architecture

Can the University provide a high-level diagram of the current telecommunications architecture, See Diagrams at the bottom of the page including carrier connectivity, SIP trunk termination, SBC placement (if applicable), and major campus locations?

Existing Equipment

Please confirm whether existing customer-owned voice infrastructure (PBX, SBCs, gateways, etc.) will remain in service, and that the contractor's responsibility is limited to providing and supporting telecommunications services unless otherwise specified.

Answered in the diagram below and in question 7.

Incumbent Environment

Can the University identify the incumbent telecommunications service provider(s)?

No

Team/Subcontractor Experience Qualification

Section 4 requires the Offeror to demonstrate a minimum of 5 years of experience and at least 3 successful deployments at R1 institutions with 25,000+ undergraduate students, along with 3 reference accounts (at least one from an R1 institution). For a proposal submitted by a prime contractor partnering with subcontractors/teaming partners, may the collective team's experience and references be used to satisfy this requirement, or must the prime entity independently meet it in full?

The Prime Entity and it’s team must meet the full requirement.

UMD Affiliate Account Requirement

Section 4.2.1 states that staff involved in implementation and configuration activities must obtain a UMD Affiliate account, requiring SSN, full name, birth date, and citizenship/visa status. Does this requirement apply only to on-site field/implementation personnel, or does it extend to all team members, including remote program management, solution architecture, and governance roles?

This is for people who need to access any university systems as an administrator.

We do not expect a Contractor to administer UMD’s systems; this is standard boilerplate to get a university ID and login access.

Financial Viability Evaluation

Section 4.2.2 notes that the University may request an Annual Report or audited financial statements to evaluate financial viability. For a proposal submitted by a small business prime contractor

The financial viability will be evaluated at the prime level.

teaming with larger subcontracted partners who will deliver the underlying carrier services, will financial viability be evaluated at the prime level, the subcontractor level, or both?

Contract Term and Renewal Options

Could the University confirm the anticipated contract term and any renewal option periods for this engagement?

The contract terms will be a Three (3) year base period with Two(2) Twelve (12) month options.

Can UMD please confirm if the correct solicitation number is BPM038479 or BPM058210?

The correct Solicitation number is

BPM058210.

SIP capacity: Can UMD please confirm the required concurrent-call capacity by site?

See question 3 & updated Service Location table after question 78

CP has 400 (200/Per) call paths IBBR has 100 (50/per) USMSM has 20

See question 18 for full call volume.

SIP demarcation:

a. In lieu of 4254 Stadium Drive; will UMD accept

GigE handoff at 7954 Baltimore Ave, Building 224?

b. In lieu of 9600 Gudelsky Dr. will UMD accept

GigE handoff at 9640 Gudelsky Dr?

c. Can UMD provide space and power for network interface devices at each address?

a. No. See question 3 & updated service location table after question 78

b. No. See question 3 & updated service location table after question 78

c. Yes, UMD will provide space & power for vendor provided NID at all service locations in the table after question 78

4.

Number portability: Can UMD please provide the approximate number of DIDs and toll-free numbers that will need to be ported and identify the current carrier(s)/RespOrg where available?

32,000/ The Responsible org will be announced at contract award.

Dynamic IP – please elaborate on the requested Dynamic IP feature - what is your expectation of how it will be utilized in conjunction with UMD’s SIP trunking configuration?

Dynamic IP just implies a vendor-managed, direct-peered SIP Circuit. We do NOT want any SIP Trunk to ride over commodity internet.

V-002 / E911: Please clarify the University's expected division of responsibility for E911calls.

a. Is the SIP provider expected to only support

911/E911 call routing and associated ANI/location delivery to the appropriate PSAP, or is the provider

E911 is not required for this RFP, but the vendor should be able to deliver 911 calls to local PSAPs for each SIP circuit. (AOR) also expected to furnish and maintain the E911 location database and/or location-management platform?

b. Please also identify the required dispatchable-location granularity (campus, building, floor, room/endpoint) and any existing Emergency

Response application with which the proposed SIP service must integrate.

How many Toll-Free Numbers do you own? Approximately 25

Please confirm DID count is 32,000. Approximately 32,000

What is the average number of Toll-Free Inbound minutes?

Unknown at this time

Is E911 out of scope for the underlying PSTN service since Cisco Call Manager should be utilizing

CER and E911 provider?

E911 is not required for this RFP, but the vendor should be able to deliver 911 calls to local PSAPs for each SIP circuit. (AOR)

If E911 is in scope for current Cisco Call Manager, what is the expected functionality desired?

Not in Scope - E911 is not required for this RFP, but the vendor should be able to deliver 911 calls to local PSAPs for each SIP circuit. (AOR)

Is E911 requirement for future Zoom, Teams or

Webex Calling solution?

E911 is not required for this RFP, but the vendor should be able to deliver 911 calls to local PSAPs for each SIP circuit. (AOR)

Outside of Cisco Call Manager, are there any

Contact Center services currently being utilized?

Not in scope, but we do run UCCX in conjunction with Call Manager for our College Park campus solutions.

Are there any 3rd party integrations into Call

Manager, such as RightFax, etc.

Not in scope

Is SRST deployed with the existing Cisco Call

Manager?

Yes

On the pre-bid call there was mention that the SIP services would not be “over the top” or not delivered over the internet but via dedicated circuit. Please confirm whether the winner will provide those circuits as part of their solution.

Yes

If a reference meets or exceeds the 400 concurrent talk paths and/or the 300K minutes per month but is less than 25K students, would the University consider that a viable reference ?

At least one Offerors must provide three (3) reference accounts for implementing and configuring a campus Telecommunication system Services of similar size and scope at Higher education institutions with at least 25,000 undergraduate students. At least one of the references must be for a

R1 institution with at least 25,000 undergraduate students.

Attachment C contains instructions referencing an

Enterprise Telecommunication Services pricing sheet and a Price Proposal form; however, the attachment provided appears to contain instructions only and does not include any pricing tables or fields for completion. Please confirm whether a separate pricing worksheet was intended to be included and, if so, provide the correct pricing template.

See question 5 response.

Attachment B requires Offerors to provide narrative responses demonstrating compliance with each requirement. The RFP also requests separate solution and implementation narratives.

To avoid unnecessary duplication, may Offerors provide concise responses within Attachment B and cross-reference supporting information contained within the solution and implementation narratives, or does the University require fully self-contained responses within Attachment B?

Yes a cross-reference supporting response is acceptable.

Attachment C contains instructions referencing an

Enterprise Telecommunication Services pricing sheet and a Price Proposal form; however, the attachment provided appears to contain instructions only and does not include any pricing tables or fields for completion. Please confirm whether a separate pricing worksheet was intended to be included and, if so, provide the correct pricing template.

See question 5 response.

Please confirm that the physical delivery addresses for the SIP Services.

See questions 3 & 34 and updated service location table after question 78

Will you please remove all references to POTS? RFP has been updated to exclude references to POTS

Will you please provide the addresses and number of call paths where the SIP services and circuits are to be delivered.

See questions 3 & 34 and updated service location table after question 78

Offeror Experience / Subcontractor Experience No, the Offeror experience will be based on the Prime Contractor.

Regarding the required corporate experience, deployments, and institutional references, may an Offeror satisfy any portion of these requirements through the documented experience of a named key subcontractor, or must all mandatory experience qualifications be held independently by the Offeror?

Joint Venture Qualifications

If a proposal is submitted by a formal joint venture, may UMD evaluate the combined experience, deployments, personnel, and references of the individual JV members when determining compliance with the minimum qualification requirements?

Yes.

Higher-Education / R1 References

Please clarify the required reference standard.

Must all three required references/deployments involve R1 institutions with at least 25,000 undergraduate students, or is only one required to meet the R1/25,000-undergraduate threshold while the remaining references may be comparable higher-education institutions?

Offerors must provide three (3) reference accounts for implementing and configuring a campus Telecommunication system Services of similar size and scope at Higher education institutions with at least 25,000 undergraduate students. These should be in an on-campus and in-person setting and within the United States. At least one of the references must be for a R1 institution with at least 25,000 undergraduate students.

Timing of Subcontractor Approval

The contract provisions require prior written

University consent before services are subcontracted in whole or in part. At what stage is this consent required: proposal submission, identification of the proposed subcontractor, prior to award, prior to execution of the subcontract, or prior to the subcontractor beginning performance?

At proposal submission.

Required Teaming Disclosures UMD will need legal entity name, assigned scope, workshare, references, What information must be included in the proposal for each proposed key subcontractor or JV member—for example legal entity name, assigned scope, workshare, references, key personnel, insurance, security responsibilities, technical responsibilities, or lower-tier providers?

key personnel, insurance, security responsibilities and technical responsibilities. Additional information may be required.

Underlying Carriers and Lower-Tier Providers

Where a proposed telecommunications provider relies upon underlying CLECs, local-access carriers, fiber providers, network operators, or other lower-tier providers to deliver geographic or path diversity, must each underlying provider be separately disclosed to or approved by UMD?

Yes underlying providers and lower tier providers will need to be disclosed.

However, all sub-contractors will need to be managed by the prime contractor.

Partner Substitution

If an Offeror needs to replace or add a key technical subcontractor, carrier, or other critical teaming member after proposal submission or after award, what University approval process and qualification standards would apply?

The same qualification standards would apply and the partner substitution process will be discussed with the awardee.

Foreign or Offshore Participation

May an Offeror utilize a subcontractor with a foreign parent company and/or offshore technical or support personnel? If so, please identify any restrictions involving UMD data access, administrative access, customer support, data residency, cybersecurity, Section

889 compliance, or other applicable requirements.

No foreign or offshore participation will be accepted.

Written Confirmation of August 7 Scope

Clarifications

Please confirm in writing any August 7 pre-

POTS and FAX services are not part of this

RFP

proposal conference changes to the issued requirements, particularly with respect to:

· analog/POTS, elevator, fire-alarm and fax services;

· UMD retaining its existing CUCM/CUBE environment and endpoints;

· the contractor’s Cisco/CUCM responsibilities;

and onsite field-service responsibilities.

The address 2740 Comcast way seems to be only a shipping address. Is the physical address

8500 Paint Branch Drive?

See Question 16

If P-001, P-002, and P-003 have been removed or modified, please identify the controlling revised scope.

The RFP has been amended per Amendment 1.

Final SIP Circuit and Capacity Requirements

Please confirm the final required number of private SIP circuits, the location of each circuit, required concurrent-call-path allocation, bandwidth/handoff requirements, and static-IP requirements.

See Questions 3, 33, and 34 and the updated Service Locations table after question 78

Diversity Standard

Please define the required level of geographic and/or path diversity. Does compliance require separate physical fiber paths, building entrances, local-loop providers, carrier points of presence, central offices, or another specific diversity standard?

See Question 12

Technical Demarcation

Please identify the intended technical demarcation between UMD and the awarded contractor. Specifically, is the contractor expected to deliver the private SIP service to

UMD’s Cisco CUBE environment while UMD

Upon award, the contractor is expected to deliver the private SIP service to UMD’s Cisco CUBE environment while UMD retains responsibility for CUCM, CUBE configuration, internal dial plan, retains responsibility for CUCM, CUBE configuration, internal dial plan, firewalls, VLANs, QoS, campus networking, and endpoints?

firewalls, VLANs, QoS, campus networking, and endpoints.

Carrier-to-CUBE Architecture / Additional

Management Layer

Does UMD require the underlying telecommunications carrier’s private SIP service to terminate directly on UMD’s Cisco

CUBE, or may an additional communications or service-management platform operate within the signaling and/or media path provided that all private-connectivity, QoS, security, redundancy, interoperability, and SLA requirements are satisfied?

See Question 67

Telecommunications Expense Management and Reporting

May the administrative portal and reporting solution include enhanced Telecom Expense

Management functionality such as DID inventory management, invoice reconciliation, usage analytics, departmental or cost-center allocation, carrier-performance reporting, anomaly identification, and cost-optimization reporting?

Yes.

If these capabilities exceed the mandatory requirements, may they be identified as value-added functionality without inclusion in the evaluated base LPTA price?

Yes, UMD desires value added functionality without inclusion in the evaluated base LPTA price.

Transition Inventory and Baseline Data

Following award, will UMD provide the selected contractor with the current DID inventory, number blocks, carrier/account information, department/location mappings, Yes, this type of information will be shared at a Kickoff meeting and subsequent meetings during transition.

and available historical usage records necessary for migration and reconciliation, or should Offerors include development and validation of that baseline inventory within their implementation scope?

We would also appreciate confirmation regarding the apparent MBE documentation inconsistency: Section 4.1.4.3 directs Offerors to MBE participation documentation in Section

4.3, while Section 4.3 indicates that no MBE goal is required for this procurement. Please confirm which, if any, MBE forms must be submitted with the proposal for BPM058210.

MBE participation is optional. Please complete the MBE form(s) if applicable.

Item V-001 notes usage traffic of 300K minutes per month. Please provide a 3-4 months’ worth of usage, or a breakout of that usage across the following categories:

a. Local:

b. Outbound Long Distance (Domestic and

International if applicable):

c. Toll-Free:

d. FAX:

See question 18

We have no data for a, b, or c; faxes are not part of this RFP.

Pg 7, Items P-001, P-002 and P-0003 note that

POTS lines are a mandatory item in the RFP. At the pre-bid conference on Friday 8/7 it was stated that POTS are not a part of the scope.

Can we get clarification on that?

a. If POTS are in scope, can you advise how many POTS lines terminate into each respective building(s)/address(es)?

POTS are not included in this RFP.

Item S-001 notes 2 circuits supporting a minimum of 200 concurrent paths each at the

“main UMCP campus”. Is that the 2113

Chesapeake address, or can you please validate the UMCP campus address?

See question 34 and table below.

Along the same lines as question #77 please verify our interpretation of the sites and corresponding number of circuits and SIP Paths per site:

a. UMCP Campus: 2113 Chesapeake, College

Park, MD. 400 paths. 200 Paths per circuit. 2

Geo Diverse Circuits

b. IBBR Building: 9600 Gudelsky Dr, Rockville, MD. 20850 (IBBR Building) – 100 Paths. 50

Paths per circuit. 2 Geo Diverse Circuits.

c. USMSM: 44219 Airport Rd, California, MD.

20619 - 20 Paths, 1 Circuit

See question 34 and updated table

Item TF-002 notes porting of Toll-Free numbers. How many toll-free numbers will be ported, and can you provide those toll-frees to validate portability? Usage estimates have been requested as well, to accurately quote

TF-001.

We do not have that data.

In respect to correlating the S-001 section requests to the service locations provided, is it correct to assume the California, MD location and Rockville, MD location are both considered IBBR locations with each getting a single circuit to support the listed call paths? There doesn't appear to be a

IBBR tag in the nomenclature for California, MD but it is listed as a DYIP site.

California location is USMSM, and Rockville is IBBR; See questions 3, 33 & 34 and updated service location table after question 78

3. Service Locations (Updated)

Site Name Bldg # Address Concurrent SIP Calls

UMCP 10

4161 Fieldhouse Dr.

College Park, MD 20742

UMCP 224

4254 Stadium Dr.

College Park, MD 20742

IBBR 976

9600 Gudelsky Dr.

Rockville, MD 20850

IBBR 977

9600 Gudelsky Dr.

Rockville, MD 20850

USMSM SM3

44219 Airport Rd.

California, MD 20619

Diagram 1

Diagram 2