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

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_configure-emergency-responder-and-redskynational.html

Published

2026-03-17

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• On-premises National E911 Service Provider ERLs are added under ERL > National E911 Service Provider ERL with ALI details, and the ALI Location field must be under 20 characters. in context
• Before configuring a National E911 Service Provider, the administrator needs the account information and a certificate from the provider. in context
• National E911 Service Provider route or translation patterns must be entered in Emergency Responder (System > Telephony Settings) before any National E911 Service Provider ERL can be added, and matching patterns are configured in Unified CM. in context
• ALI Update and Secondary Status Update schedules between Emergency Responder and the National E911 Service Provider are set under ERL > National E911 Service Provider ERL > National E911 Service Provider Schedule, with Enable Schedule checked. in context
• ALI data must be submitted to the National E911 Service Provider as a TN Update through the provider VUI before an emergency call can be routed successfully. in context
• Under System > National E911 Service Provider VUI Settings the administrator uploads the provider certificate with its password and the VUI URL, clicks Test and Validate, enters the account information, and uses Test Connectivity, where a 200 OK result means Emergency Responder reached the provider's location update service securely. in context
• From Release 14SU2 onward, the provider-issued certificate that Emergency Responder uses for the National E911 Service Provider connection must be in BCFKS format. in context
• Emergency Responder integrates with two approved National E911 Service Providers, RedSky and Intrado, to automate location conveyance and call completion. in context
• With a National E911 Service Provider, Emergency Responder sends ERL and ELIN information for on-premises phones; for off-premises users the calling party number is the user's own number, which the provider uses to identify the caller and location. in context
• For National E911 Service Provider calls, connection redundancy comes from Unified CM route lists and route groups, so extra provider route patterns are not required. in context
• With RedSky as the National E911 Service Provider, Emergency Responder supports neither queries from the provider nor level of service. in context
• From CER Release 14SU2, the provider certificate must be in .bcfks format. in context
• CER 15 documentation states that RedSky/Intrado integration is supported when CER runs in FIPS mode. in context
• 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. in context
• CER 15 documentation says only one National E911 Service Provider route pattern is needed, because redundancy is handled in Unified CM configuration. in context
• CER Release 15 documentation names both RedSky and Intrado as approved third-party National E911 Service Providers. in context
• RedSky and Intrado are the approved national E911 service providers for Cisco Emergency Responder, as an alternative to a direct connection with the local exchange carrier. in context
• With a national E911 provider, Emergency Responder off-premises users create a location on the Off-Premises User page (or through Jabber or Webex) and validate the address with the provider before it becomes active. in context
• With a national E911 provider, Emergency Responder tracks each phone as On-premises, Off-premises or unlocated. in context

Cite this source record

APA

WarmTransfer. (2026, March 17). Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cer-15-admin-national-e911

BibTeX

@misc{warmtransfer-cisco-cer-15-admin-national-e911,
  title  = {Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cer-15-admin-national-e911},
  note   = {Cisco Systems, accessed 2026-09-24}
}