Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Emergency Call Handling with RedSky

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_emergency-call-handling-with-redsky.html

Published

2026-09-16

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

• In Unified CM's native RedSky mode, endpoints get a location URI from RedSky through HELD, and Unified CM routes the emergency call to RedSky with that URI in the Geolocation header of the outgoing INVITE. in context
• Unified CM's native Emergency Call Handling with RedSky is available from Releases 12.5(1)SU6 and 14SU2 onward. in context
• Unified CM's Emergency Call Handling with RedSky can be used without Cisco Emergency Responder emergency call routing; Emergency Responder can optionally complement it by tracking devices and passing ALI/ELIN information to RedSky. in context
• The Emergency Service Numbers field in the Unified CM service profile defaults to 911 and 933, separated by a comma. in context
• In the Unified CM integration the RedSky server substitutes the appropriate ELIN and sends the call to the PSAP. in context
• When 911 is dialed, Unified CM places the previously saved location URI in the Geolocation header of the outgoing INVITE to RedSky. in context
• In the Unified CM integration the endpoint stores the location URI that the RedSky server returns in response to a HELD request. in context
• The SIP profile normalization script used for the RedSky trunk in Unified CM is named redsky-alternate-id-interop. in context
• Cisco's Unified CM guide states that E911 Anywhere sends SMS, email and security desk screen alerts at the same time as the emergency call. in context
• A Unified CM service profile applies to a device only when the device's owner user ID is set. in context
• Unified CM Emergency Call Handling with RedSky is available from Release 12.5(1)SU6 and 14SU2 onwards. in context
• The Unified CM service profile Emergency Calling section holds Enable Emergency Calling, the RedSky Organization ID and Secret, a Location URL, and Emergency Service Numbers. in context
• Cisco recommends connecting Unified CM to the RedSky server over a SIP trunk, and a predefined Lua script must be applied to that trunk for customer identification. in context
• The Unified CM RedSky configuration task flow is: Configure RedSky Server (SIP trunk), Configure Service Profile, Assign the Service Profile, then set up the SIP route pattern that routes calls to the RedSky trunk. in context
• The Unified CM RedSky call flow described by Cisco applies when 911 is dialed from Webex; the guide does not name Cisco IP phones or Jabber as covered endpoints. in context
• Cisco states that Emergency Call Handling with RedSky can be used without Cisco Emergency Responder emergency call routing. in context

Cite this source record

APA

WarmTransfer. (2026, September 16). Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Emergency Call Handling with RedSky. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-fcg-15-redsky

BibTeX

@misc{warmtransfer-cisco-cucm-fcg-15-redsky,
  title  = {Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Emergency Call Handling with RedSky},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cucm-fcg-15-redsky},
  note   = {Cisco Systems, accessed 2026-09-24}
}