Laserfiche WebLink
Client:City of Decatur IL <br /> Opportunity#:1003525100530.2 <br /> Date:February 03,2026 IDR E S I D I a <br /> Title:Webex Calling Migration <br /> • Complete Presidio provided workbook, after the joint design session, with all the required network <br /> elements and mapping these elements to any required physical Emergency Response Locations <br /> (ERL/Dispatchable-Location) <br /> • Review USA FCC regulations regarding e911 for Multi Line Telephone Systems(MLTS)- <br /> https://www.fcc.gov/mlts-911-requirements. Or the regulations applicable to the deployment country <br /> • Client is responsible for determining and establishing emergency calling policies based on the <br /> geographical requirements of the Client(i.e. state, county, city, township, etc.). Presidio is not <br /> responsible for determining e911 requirements based on Client locality. <br /> • Client is responsible for the discovery, definition and quantity of Emergency Response Locations <br /> (ERL)to comply with any applicable regulations <br /> • Client is responsible for discovering, documenting, and maintaining the following network element <br /> information: Public IP address, Internal IP subnet(s), switch chassis LLDP IDs, switch port LLDP IDs, <br /> and wireless access point BSSIDs. Mapping these elements to physical locations required for the <br /> configuration of Emergency Response Locations (ERL) in accordance with Client's understanding of <br /> applicable laws. <br /> • To create a granular ERL based on physical Ethernet cabling, Client needs to understand, document, <br /> and map the Ethernet cabling at a wall jack to a particular switch port to map either a Switch Chassis <br /> LLDP identifier and/or a Switch Port LLDP identifier to an ERL <br /> • To create a granular ERL based on the approximate physical location of a Wireless Access point <br /> (AP), Client needs to understand, document, and map the all the Wi-Fi BSSIDs on a particular access <br /> point to a physical location in a building to map each access point an ERL <br /> • Client is responsible for testing emergency calling from all ERLs <br /> o including contacting the PSAP servicing the location and determining the desired testing <br /> procedures of that specific PSAP <br /> • Collect and provide data required for the successful configuration of the emergency services. <br /> • Make changes to the network if needed to support the emergency configuration. <br /> • After initial configuration and demonstration by Presidio, Client will be responsible for any subsequent <br /> network element and physical location database updates to keep emergency call routing accurate as <br /> time passes. <br /> o (i.e. as the network changes over time, Client must update the E911 system and the data <br /> elements to maintain accuracy for Emergency Response Locations (ERLs) <br /> 2.3.5. Migrate Cisco Phones to MPP Quantity: 1 <br /> Migrate Supported Cisco Phones to MPP Software <br /> During a cutover event, Presidio will perform a one-time bulk migration of supported Cisco phones to <br /> Multi-Platform Phone(MPP)software <br /> • Presidio can assist with up to 2 manual phone migrations to validate networking and access <br /> requirements, prior to the migration event, if requested. <br /> o Client will identify supported handsets to test with. <br /> • If pilot migration(s)are included in this engagement, Presidio will support the MPP migration effort for <br /> up to (2)pilot migration events including up to 20 phones per event prior to the main migration event. <br /> • Assist with preparation and review of requirements for MPP migration <br /> Assumptions <br /> Confidential and Proprietary Page 10 of 25 <br /> SOW-V1.25 <br />