WarmTransfer
emergency calling · published

Intrado enterprise 911 routing services

Verified 2026-09-24 · 50 sources · tier 1–2

Also known as Intrado Emergency Routing Service (ERS), Intrado V9-1-1 for Enterprise Service, National E911 Service Provider.

Intrado positions its Emergency Routing Service (ERS) as a hosted E911 solution that delivers calls to the jurisdictionally appropriate public safety answering point (PSAP) and sends caller location automatically to the call taker's screen 27. Intrado describes ERS as maintaining connections to more than 6000 PSAPs across North America 28.

Architecture and Core Services

Intrado states that its E911 solutions work with Avaya, Cisco, Genesys, Microsoft Teams, and Mitel unified communications (UC) and UCaaS platforms 43. Intrado claims that ERS runs continuous 24/7/365 emergency call routing over a geo-redundant network with no single point of failure 31. Intrado claims that ERS delivers caller location down to the floor, room, or workstation 3.

Intrado also offers the Emergency Gateway, an on-premises management appliance intended to simplify E911 across complex, multi-vendor UC deployments 25. In multi-vendor and multi-cluster Cisco Unified Communications Manager (UCM) environments, the Emergency Gateway discovers on-premises phone locations and alerts security teams, while ERS routes 911 calls with location data to the appropriate PSAP 1​2. The two components can be deployed together or separately 2. Emergency Response Locations (ERLs) sync natively with ERS through an Intrado proprietary API 26.

Intrado owns and operates a 24/7/365 Emergency Call Relay Center (ECRC) staffed with APCO-certified telecommunicators 22. For Teams, Intrado describes the ECRC as U.S.-based, providing initial support and connecting callers to the appropriate 911 center 24. Calls placed off-premises or lacking location data route to the ECRC for triage by trained personnel 23.

For internal alerting, Intrado's Crisis Alert notification provides time, location, callback number, and caller name 21.

Microsoft Teams Integration

Intrado announced its E911 solution for Microsoft Teams on 2019-11-12 and updated the announcement on 2023-03-13 45. Microsoft lists Intrado ERS as a certified and supported 911 service provider for Teams Direct Routing, alongside Bandwidth Dynamic Location Routing and Inteliquent 36. Microsoft states that it may reject support cases if an enterprise uses a non-certified emergency services provider with Direct Routing 38.

Intrado states that ERS works with Microsoft Teams Direct Routing and all Microsoft-certified Session Border Controllers (SBCs) for Teams 46. This integration is described as fully automated, requiring no additional hardware or software 48. In Teams deployments, the Emergency Gateway serves as an optional add-on for security desk notification, listening in on calls, and emergency bridging across multi-vendor UC systems 47. Intrado's Teams offering lists desk alert screen pop-ups, crisis email alerts, and multiparty emergency bridging 44.

For Teams E911 coverage, Intrado claims direct connectivity to over 6000 PSAPs across the U.S. and Canada 50. Teams clients do not prepend '+' to emergency numbers, requiring Direct Routing voice routes toward an emergency provider to match 911 rather than +911 37. Teams transmits location information in a PIDF-LO SIP body on emergency call INVITEs for Direct Routing 49.

Under Microsoft documentation, Direct Routing supports two methods for dynamic emergency routing: Emergency Routing Service Providers (which are US only) and SBC-based ELIN applications 35. In an SBC ELIN application, the SBC matches caller location to an ELIN record, replaces the calling number with the ELIN, and routes to the PSAP; ELIN records must be uploaded to the PSTN emergency database, and callbacks undergo reverse-substitution 33. Microsoft separates these capabilities in its certified SBC table, marking SBCs as "911 Service Provider Capable", "ELIN capable", or neither (for example, Cisco CUBE is marked 911 Service Provider Capable but not ELIN capable) 39.

When using an Emergency Routing Service Provider with Direct Routing, calls with dynamically acquired locations route automatically to the corresponding PSAP, while calls without location data are screened first to verify caller location 34. For Direct Routing in Canada, dynamic emergency location behaves as in the US, except that all emergency calls are screened nationally prior to transfer to the PSAP 32.

Cisco Emergency Responder Integration

In Cisco Emergency Responder (CER) Release 12.5(1)SU8b-SU9, CER supports Intrado V9-1-1 for Enterprise Service as an alternative to direct Local Exchange Carrier (LEC) connections for both on-premises and off-premises phones 11. While CER 12.5(1) dedicates a chapter titled "Intrado V9-1-1 Enterprise Services", CER 15 titles the corresponding enterprise services chapter "National E911 Service Provider" and does not name Intrado in its headings 14. CER Release 15 documentation names both RedSky and Intrado as approved third-party National E911 Service Providers 17.

In this architecture, Unified CM sends emergency calls to CER, which routes them to the provider over a configured SIP trunk using route patterns 10. CER 15 documentation notes that only one National E911 Service Provider route pattern is required because call redundancy is managed within Unified CM configuration 16. During call processing, the provider receives the calling party's 10-digit Emergency Location Identification Number (ELIN) and uses it to retrieve Automatic Location Identification (ALI) data 7.

CER communicates with Intrado over HTTPS using the Validation and Update Interface (VUI) to validate civic addresses against Intrado's Master Street Address Guide (MSAG) data and submit ALI records 12. The VUI connection requires a provider certificate, which must be re-uploaded following any CER upgrade 6. Beginning in CER Release 14SU2, the certificate must be in .bcfks format 5. Integration with RedSky and Intrado remains supported when CER operates in FIPS mode 13.

CER maintains two synchronization schedules with the provider:

  • ALI Update Schedule: Sends newly created telephone number (TN) records 4.
  • Secondary Status Update Schedule: Queries for records containing errors 4.

The documented setup sequence for Intrado V9-1-1 on CER involves obtaining account credentials and a certificate from Intrado, configuring VUI settings, setting up Intrado route and translation patterns, creating Intrado ERLs, and assigning those ERLs to switch ports, IP subnets, and unlocated phones 9.

For off-premises endpoints, CER supports only one off-premises location per DID (directory number plus external calling party mask); off-premises devices sharing a DID are restricted to a single location 8. In CER 15, on-premises devices provide location through automated ERL-ELIN delivery, whereas off-premises location must be entered by the user against their DID 15. An optional MyE911 setting integrates third-party location clients such as Webex and Jabber, though the sources do not establish whether it applies when the configured provider is Intrado 15. Intrado's Webex App Hub listing states that its E911 offering integrates with Cisco UCM, Webex, and Jabber, supporting on-premises and remote users across multi-cluster and multi-vendor networks 1.

Standards and Regulatory Framework

SIP location conveyance is governed by RFC 6442 using the Geolocation header field 41. A cid: URI conveys location by value pointing to an included PIDF-LO body, whereas sip:, sips:, pres:, http:, or https: URIs convey location by reference, requiring dereferencing at an external location server 41. Under RFC 6442, an omitted Geolocation-Routing header field defaults to a value of "no", prohibiting intermediaries from routing based on the included location 40.

In the United States, enterprise multi-line telephone systems (MLTS) are subject to federal rules under 47 CFR 9.16:

  • Direct Dialing: Station users must be able to dial 911 directly without prefixes, postfixes, or trunk access codes 18.
  • Notification: Systems must provide contemporaneous notification to a central facility location when 911 is dialed, without delaying the call 20.
  • Dispatchable Location: Automated dispatchable location was mandated for fixed on-premises MLTS devices by 2021-01-06, and for non-fixed on-premises and off-premises devices by 2022-01-06 (with alternative location information permitted when automated dispatchable location is technically unfeasible) 19.

Corporate Structure

Stonepeak completed its acquisition of Intrado Life & Safety on 2023-01-31 42.

See also

Applicability

Applies to: Intrado Emergency Routing Service, Intrado Emergency Gateway, Intrado Emergency Call Relay Center, Intrado Emergency Routing Service for Microsoft Teams, Intrado Crisis Alert, Intrado corporate, Cisco Emergency Responder, Microsoft Teams Phone Direct Routing, IETF SIP, and MLTS. Deployments: on-premises, multi-tenant, and hosted. Sources checked 2026-09-24. Intrado ERS operates as a hosted deployment model, while Emergency Gateway is deployed on-premises 25​27. Cisco Emergency Responder integration details cover CER 12.5(1)SU8b through SU9, CER 14SU2, and CER 15 5​11​17. Microsoft Teams Direct Routing Emergency Routing Service Provider functionality applies to the US, while nationwide screening applies in Canada 32​35.

What remains uncertain

Whether Intrado ERS accepts or dereferences location by reference (Geolocation URI / HELD) on enterprise SIP 911 trunks is not covered by the sources below.

Whether Intrado ERS is offered for multi-tenant Webex Calling or only Cisco UCM and Dedicated Instance is not covered by the sources below.

The operation and support of Intrado ERS with Teams Operator Connect or Teams Phone Mobile is not covered by the sources below.

Documentation and technical specifications for the Intrado proprietary ERL sync API are not covered by the sources below.

The actual Canadian call path for Intrado ERS, regarding national screening versus direct PSAP routing, is not covered by the sources below.

The ERS pricing model, including whether it uses per-TN, per-user, or monthly subscription fees, is not covered by the sources below.

The specific network location discovery methods used by the Emergency Gateway, such as switch port, LLDP, subnet, or wireless mapping, are not covered by the sources below.

Whether the CER 15 MyE911 location-update option applies when the configured National E911 Service Provider is Intrado is not covered by the sources below.

See also

Referenced by

Sources

  1. 1
    Intrado's Webex App Hub listing says its E911 offering integrates with Cisco UCM, including Jabber and Webex, and serves on-premises and remote users in multi-cluster UCM and multivendor environments.
    Intrado - Webex App Hub · Listing overview · Checked 2026-09-24
  2. 2
    In the Cisco listing, Emergency Gateway discovers on-premises phone locations and alerts security teams, ERS routes 911 calls to the appropriate PSAP with location, and the two can be deployed together or separately.
    Intrado - Webex App Hub · How it works section · Checked 2026-09-24
  3. 3
    Intrado claims ERS delivers caller location to the PSAP down to floor, room or workstation.
    Intrado - Webex App Hub · Location capabilities statement · Checked 2026-09-24
  4. 4
    CER uses two schedules with the provider: the ALI Update Schedule sends newly created TN records, and the Secondary Status Update Schedule queries for records that have errors.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider Enterprise Services · Add Scheduled National E911 Service Provider Updates · Checked 2026-09-24
  5. 5
    From CER Release 14SU2, the provider certificate must be in .bcfks format.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider · Connection method and security notes · Checked 2026-09-24
  6. 6
    CER needs a certificate from the provider for the VUI connection, and that certificate must be uploaded again after a CER upgrade.
    Cisco Emergency Responder Administration Guide, Release 12.5(1)SU8b-SU9 - Configure Emergency Responder and Intrado V9-1-1 Enterprise Services · Set Up Intrado VUI Settings · Checked 2026-09-24
  7. 7
    In the CER integration, the provider receives the calling party's 10-digit ELIN and uses that number to retrieve the caller's ALI data.
    Cisco Emergency Responder Administration Guide, Release 12.5(1)SU8b-SU9 - Configure Emergency Responder and Intrado V9-1-1 Enterprise Services · Emergency Call Flow section · Checked 2026-09-24
  8. 8
    In the CER provider integration, only one off-premises location can be configured per DID (DN plus external mask), so off-premises phones sharing a DID can have only one location.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider Enterprise Services · National E911 Service Provider for Enterprise Service; limitations · Checked 2026-09-24
  9. 9
    CER setup order for the Intrado service: get account details and certificate from Intrado, configure VUI settings, configure Intrado route/translation patterns, create Intrado ERLs, then assign ERLs to switch ports, IP subnets and unlocated phones.
    Cisco Emergency Responder Administration Guide, Release 12.5(1)SU8b-SU9 - Configure Emergency Responder and Intrado V9-1-1 Enterprise Services · Set Up Support for Intrado V9-1-1 for Enterprise Service (task list) · Checked 2026-09-24
  10. 10
    In the CER Intrado integration, Unified CM sends the emergency call to CER, which routes it to Intrado over a configured SIP trunk using Intrado route patterns.
    Cisco Emergency Responder Administration Guide, Release 12.5(1)SU8b-SU9 - Configure Emergency Responder and Intrado V9-1-1 Enterprise Services · Emergency Call Flow section; Set Up Intrado Patterns · Checked 2026-09-24
  11. 11
    In CER 12.5(1)SU8b-SU9, Cisco Emergency Responder supports Intrado V9-1-1 for Enterprise Service as an alternative to a direct connection with the Local Exchange Carrier, for both on-premises and off-premises phones.
    Cisco Emergency Responder Administration Guide, Release 12.5(1)SU8b-SU9 - Configure Emergency Responder and Intrado V9-1-1 Enterprise Services · Overview; Intrado V9-1-1 for Enterprise Service · Checked 2026-09-24
  12. 12
    CER talks to Intrado over HTTPS through the Validation and Update Interface (VUI), which validates civic addresses against Intrado's MSAG data and sends ALI records.
    Cisco Emergency Responder Administration Guide, Release 12.5(1)SU8b-SU9 - Configure Emergency Responder and Intrado V9-1-1 Enterprise Services · Set Up Intrado VUI Settings; Set Up Intrado ERLs (Pre-validate from Intrado) · Checked 2026-09-24
  13. 13
    CER 15 documentation states that RedSky/Intrado integration is supported when CER runs in FIPS mode.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider · Connection method and security notes · Checked 2026-09-24
  14. 14
    The CER 15 enterprise-services chapter calls the provider 'National E911 Service Provider' and does not name Intrado, whereas the 12.5(1) chapter is titled 'Intrado V9-1-1 Enterprise Services'.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider Enterprise Services · Chapter title and all 13 section headings · Checked 2026-09-24
  15. 15
    In CER 15, on-premises phones convey location through automated ERL-ELIN delivery, while off-premises location is entered by the user against the user's DID. An optional MyE911 setting integrates third-party location apps such as Webex and Jabber.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider · Location conveyance and location updates notes · Checked 2026-09-24
  16. 16
    CER 15 documentation says only one National E911 Service Provider route pattern is needed, because redundancy is handled in Unified CM configuration.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider · Call routing notes · Checked 2026-09-24
  17. 17
    CER Release 15 documentation names both RedSky and Intrado as approved third-party National E911 Service Providers.
    Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider · Chapter overview · Checked 2026-09-24
  18. 18
    47 CFR 9.16(b)(1) requires an MLTS to let a user dial 911 directly from any station with dialing facilities, without any additional digit, code, prefix or post-fix.
    47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication) · 47 CFR 9.16(b)(1) · Checked 2026-09-24
  19. 19
    47 CFR 9.16(b)(3) requires automated dispatchable location from fixed on-premises MLTS devices by 2021-01-06, and sets 2022-01-06 for non-fixed on-premises and off-premises devices, with alternative location information allowed where automation is not technically feasible.
    47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication) · 47 CFR 9.16(b)(3) · Checked 2026-09-24
  20. 20
    47 CFR 9.16(b)(2) requires MLTS notification to a central location at the facility; the notification must be contemporaneous with the 911 call and must not delay it.
    47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication) · 47 CFR 9.16(b)(2) · Checked 2026-09-24
  21. 21
    Intrado's Crisis Alert notification includes time, location, callback number and name.
    Enterprise E911 Solutions | Intrado · Crisis Alert product block · Checked 2026-09-24
  22. 22
    Intrado owns and operates a 24/7/365 Emergency Call Relay Center (ECRC) staffed with APCO-certified telecommunicators.
    Enterprise E911 Solutions | Intrado (Emergency Routing Service) · ECRC support statement · Checked 2026-09-24
  23. 23
    Intrado's Teams announcement says calls made off-premises or without location data go to the ECRC, where trained staff triage the call.
    Intrado Develops New E911 Solution for Microsoft Teams · Emergency Call Relay Center paragraph · Checked 2026-09-24
  24. 24
    For Teams, Intrado describes the ECRC as U.S.-based: it provides initial support and connects the caller to the appropriate 911 center.
    Intrado E911 for Microsoft Teams · Emergency Call Relay Center section · Checked 2026-09-24
  25. 25
    Intrado Emergency Gateway is an on-premises management appliance intended to simplify E911 in complex, multi-vendor UC deployments.
    Intrado E911 Solutions · Emergency Gateway description block · Checked 2026-09-24
  26. 26
    Intrado states that Emergency Response Locations sync natively with Emergency Routing Service through an Intrado proprietary API.
    Enterprise E911 Solutions | Intrado (Emergency Routing Service) · API integration feature statement · Checked 2026-09-24
  27. 27
    Intrado positions Emergency Routing Service as a hosted E911 solution that delivers calls to the jurisdictionally appropriate PSAP and sends caller location automatically to the 911 call taker's screen.
    Intrado E911 Solutions · Emergency Routing Service description block · Checked 2026-09-24
  28. 28
    Intrado describes Emergency Routing Service as having connections to more than 6000 public safety answering points across North America.
    Enterprise E911 Solutions | Intrado (Emergency Routing Service) · ERS product page, PSAP connectivity feature statement · Checked 2026-09-24
  29. 29
    For Teams Direct Routing, Intrado ERS most likely receives caller location by value (PIDF-LO in the SIP INVITE) forwarded by the SBC, not by reference, because Teams sends PIDF-LO by value and ERS is a Microsoft-certified ERSP. No Intrado document fetched states this.inferred
    Emergency calling for Microsoft Teams Direct Routing with Azure Communications Gateway · Overview of emergency calling (PIDF-LO SIP body) · Checked 2026-09-24
  30. 30
    Enterprise E911 products (ERS, Emergency Gateway) are probably part of the Stonepeak-owned Intrado Life & Safety business, because the current intrado.com enterprise E911 pages sit alongside the 911 infrastructure business. The acquisition release does not say so explicitly.inferred
    Stonepeak Completes Acquisition of Intrado Life & Safety · Press release body (the fetch found no mention of enterprise E911) · Checked 2026-09-24
  31. 31
    Intrado claims ERS runs continuous 24/7/365 E911 call routing over a geo-redundant network with no single point of failure.
    Intrado E911 for Microsoft Teams · Operational reliability statement · Checked 2026-09-24
  32. 32
    For Direct Routing in Canada, dynamic emergency location works as in the US except that all emergency calls are screened nationally before being transferred to the PSAP.
    Considerations for Direct Routing · Dynamic emergency calling for Direct Routing, final paragraph · Checked 2026-09-24
  33. 33
    With an SBC ELIN application, the SBC matches the caller's location to an ELIN record, replaces the caller's number with the ELIN, and routes to the PSAP. The ELIN records must be uploaded to the PSTN emergency database, and callbacks are reverse-substituted.
    Considerations for Direct Routing · Emergency Location Identification Number applications subsection · Checked 2026-09-24
  34. 34
    With an Emergency Routing Service Provider integrated into Direct Routing, calls with a dynamically acquired location route automatically to the PSAP for that location, and calls without one are first screened to confirm the caller's location.
    Considerations for Direct Routing · Emergency Routing Service Providers subsection · Checked 2026-09-24
  35. 35
    Microsoft names two ways to route Direct Routing emergency calls dynamically: Emergency Routing Service Providers, which are US only, and SBC-based ELIN applications.
    Considerations for Direct Routing · Emergency call routing for Direct Routing · Checked 2026-09-24
  36. 36
    Microsoft lists Intrado Emergency Routing Service (ERS) as a certified and supported 911 service provider for Teams Direct Routing, together with Bandwidth Dynamic Location Routing and Inteliquent.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · Certified SBC vendors table footnote '911 service providers' · Checked 2026-09-24
  37. 37
    Teams clients no longer prepend '+' to emergency numbers, so Direct Routing voice routes toward an emergency provider must match 911 rather than +911.
    Considerations for Direct Routing · Emergency call routing for Direct Routing, Note · Checked 2026-09-24
  38. 38
    Microsoft says it may reject support cases if a non-certified emergency services provider is used with Direct Routing.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · '911 service providers' footnote · Checked 2026-09-24
  39. 39
    Microsoft's certified SBC table marks each SBC as '911 Service Provider Capable' and/or 'ELIN capable' separately; for example, Cisco CUBE is marked 911 Service Provider Capable but not ELIN capable, and several certified SBCs are marked as neither.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · Certified SBC vendors table, columns '911 Service Provider Capable*' and 'ELIN capable' · Checked 2026-09-24
  40. 40
    Under RFC 6442, if a SIP request has no Geolocation-Routing value, that is treated the same as 'no', and intermediaries must not use the included location for routing.
    RFC 6442: Location Conveyance for the Session Initiation Protocol · Sections 4.2 and 4.2.1 · Checked 2026-09-24
  41. 41
    RFC 6442 conveys location in SIP through the Geolocation header field: a cid: URI points to a PIDF-LO body in the request (location by value), while a sip, sips, pres, http or https URI must be dereferenced at a location server (location by reference).
    RFC 6442: Location Conveyance for the Session Initiation Protocol · Sections 3.1, 3.2 and 4.1 · Checked 2026-09-24
  42. 42
    Stonepeak completed its acquisition of Intrado Life & Safety on 2023-01-31.
    Stonepeak Completes Acquisition of Intrado Life & Safety · Press release dateline and headline · Checked 2026-09-24
  43. 43
    Intrado states that its E911 solutions work with Avaya, Cisco, Genesys, Microsoft Teams and Mitel UC and UCaaS platforms.
    Intrado E911 Solutions · Platform compatibility statement · Checked 2026-09-24
  44. 44
    Intrado's Teams E911 offering lists crisis email alerts, desk alert screen pop-ups and multiparty emergency bridging.
    Intrado E911 for Microsoft Teams · Alert capabilities list · Checked 2026-09-24
  45. 45
    Intrado announced its E911 solution for Microsoft Teams on 2019-11-12 and last updated the announcement on 2023-03-13.
    Intrado Develops New E911 Solution for Microsoft Teams · Byline dates · Checked 2026-09-24
  46. 46
    Intrado's Teams announcement says ERS works with Microsoft Teams Direct Routing and with all Microsoft-certified SBCs for Teams.
    Intrado Develops New E911 Solution for Microsoft Teams · Teams integration paragraph · Checked 2026-09-24
  47. 47
    Intrado's Teams announcement presents Emergency Gateway as an optional add-on for security desk notification, listening in on the call and emergency bridging across multi-vendor UC.
    Intrado Develops New E911 Solution for Microsoft Teams · Optional security feature paragraph · Checked 2026-09-24
  48. 48
    Intrado's Teams announcement describes the ERS integration as fully automated and needing no additional software or hardware.
    Intrado Develops New E911 Solution for Microsoft Teams · Emergency Routing Service paragraph · Checked 2026-09-24
  49. 49
    Microsoft documentation states that Teams always sends location information in a PIDF-LO SIP body on emergency call INVITEs for Direct Routing.
    Emergency calling for Microsoft Teams Direct Routing with Azure Communications Gateway · Overview of emergency calling; Emergency numbers and location information · Checked 2026-09-24
  50. 50
    Intrado's Teams E911 page claims direct connectivity to over 6000 PSAPs across the U.S. and Canada.
    Intrado E911 for Microsoft Teams · Coverage statistics block · Checked 2026-09-24

Documents

tier 1 standards and regulators

47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication)

Legal Information Institute, Cornell Law School (republishing eCFR) · 2020-12-03 · accessed 2026-09-24

tier 1 standards and regulators

RFC 6442: Location Conveyance for the Session Initiation Protocol

IETF / RFC Editor · 2011-12-01 · accessed 2026-09-24

tier 2 current vendor documentation

Cisco Emergency Responder Administration Guide, Release 12.5(1)SU8b-SU9 - Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Cisco Systems · accessed 2026-09-24

tier 2 current vendor documentation

Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider

Cisco Systems · 2026-03-17 · accessed 2026-09-24

tier 2 current vendor documentation

Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider Enterprise Services

Cisco Systems · accessed 2026-09-24

tier 2 current vendor documentation

Considerations for Direct Routing

Microsoft · 2026-09-10 · accessed 2026-09-24

tier 2 current vendor documentation

Emergency calling for Microsoft Teams Direct Routing with Azure Communications Gateway

Microsoft · 2023-10-09 · accessed 2026-09-24

tier 2 current vendor documentation

Enterprise E911 Solutions | Intrado

Intrado · accessed 2026-09-24

tier 2 current vendor documentation

Enterprise E911 Solutions | Intrado (Emergency Routing Service)

Intrado · accessed 2026-09-24

tier 2 current vendor documentation

Intrado - Webex App Hub

Cisco Webex App Hub (listing authored by Intrado) · accessed 2026-09-24

tier 2 current vendor documentation

Intrado Develops New E911 Solution for Microsoft Teams

Intrado · 2023-03-13 · accessed 2026-09-24

tier 2 current vendor documentation

Intrado E911 for Microsoft Teams

Intrado · accessed 2026-09-24

tier 2 current vendor documentation

Intrado E911 Solutions

Intrado · accessed 2026-09-24

tier 2 current vendor documentation

Session Border Controllers certified for Direct Routing - Microsoft Teams

Microsoft · 2026-05-27 · accessed 2026-09-14

tier 2 current vendor documentation

Stonepeak Completes Acquisition of Intrado Life & Safety

Intrado · 2023-01-31 · accessed 2026-09-24

Cite this page

APA

WarmTransfer. (2026, September 24). Intrado enterprise 911 routing services. WarmTransfer. https://warmtransfer.net/knowledge/intrado-enterprise-911

BibTeX

@misc{warmtransfer-intrado-enterprise-911,
  title  = {Intrado enterprise 911 routing services},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/intrado-enterprise-911},
  note   = {Verified 2026-09-24}
}