Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager

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_b_cisco-emergency-responder-administration-guide-1401_chapter_011.html

Published

unknown

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

• The Emergency Responder application user in Unified CM (User Management > Application User) controls all CTI ports and the 911, 912 and ELIN route points, and belongs to the Standard CTI Enabled and Standard CTI Allow Calling Number Modification groups. in context
• The primary Unified CM in the Unified CM Group assigned to the Emergency Responder device pool must also be the primary CTI Manager configured in Emergency Responder. in context
• Emergency Responder CTI ports must use a device pool in a G.711 region, use PhoneCSS and the Phones partition in Cisco's example, and have consecutive extension numbers starting from the first port's DN. in context
• In the E911CSS calling search space the E911 partition must be listed before the Phones partition, so that a 911 call matches the Emergency Responder route point. in context
• For PSAP callbacks, a translation pattern matching the ELIN DIDs (for example 5555551XXX) is created in the E911 partition with E911CSS and prefix digits that send the call to the PSAP callback route point. in context
• Each ERL route pattern is a prefix, a dot and the emergency number (for example 10.911) in the E911 partition, discarding PreDot digits, with Use Calling Party's External Phone Number Mask selected and the gateway to the local PSAP chosen. in context
• The gateway that connects to the emergency network or PSTN over CAMA or PRI is assigned the E911CSS calling search space so PSAP callbacks can reach the ELIN translation patterns. in context
• Where several Emergency Responder groups exist, each gets an inter-group route pattern (for example 1000.911, PreDot discard, over the intercluster trunk) in Unified CM, and the same pattern must be defined in every other Emergency Responder group under System > Telephony Settings. in context
• Where 9 is the outside access code, Cisco's example creates translation patterns 911 and 9.911 in the Phones partition with E911CSS and Provide Outside Dial Tone checked, 9.911 discarding PreDot, and places the 911, 912 and 913 route points in the E911 partition. in context
• Cisco's example Unified CM setup creates a Phones partition and a PhoneCSS calling search space containing it, and assigns both to the phones. in context
• The primary emergency CTI route point in Cisco's example is RP911 with directory number 911 in the Phones partition, calling search space E911CSS, and Forward Busy to 912. in context
• The standby route point (912, E911 partition, E911CSS) forwards on busy to the route pattern for the default ERL or to onsite security, so calls still reach the default PSAP or security if the standby server cannot take them. in context
• The ELIN route point (example RPELIN913, directory number 913XXXXXXXXXX, E911 partition, E911CSS) is the destination of all incoming PSAP callbacks, and the 911, 912 and 913 route points must be unique. in context
• Cisco's Unified CM chapter says the Calling Party Selection option on the trunk (Device > Trunk Configuration) should be set to Originator. in context
• Where the external access code is 9, Cisco warns that a 911 or 9.911 CTI route point can interfere with secondary dial-tone timing, and recommends translation patterns that send 9 plus 911 to the single 911 pattern. in context
• Emergency Responder must be added as a Unified CM application user that controls its CTI ports, CTI route points and ELIN route points. in context
• Emergency Responder uses Unified CM CTI ports, configured with consecutive extensions, to call onsite alert (security) personnel when an emergency call is made. in context
• Emergency Responder needs Unified CM CTI route points for the local emergency number (for example 911), for a number the standby server listens on (for example 912), and for incoming PSAP callbacks (for example 913XXXXXXXXXX). in context
• The example Unified CM configuration uses an E911 partition for Emergency Responder objects and an E911CSS calling search space that contains the E911 and Phones partitions. in context
• In the traditional ELIN deployment, one Unified CM route pattern is created for every ERL, and the ELINs are DID numbers obtained from the service provider. in context
• With Cisco Emergency Responder, Unified CM needs a CTI route point for the emergency number (such as 911) in the E911 partition so Emergency Responder intercepts emergency calls. in context
• In Emergency Responder's Unified CM setup the E911 partition must be listed before the phones partition in E911CSS, and phones cannot reach the E911 partition directly. in context
• Emergency Responder uses a PSAP callback CTI route point such as 913XXXXXXXXXX in the E911 partition, with 913 stripped to reveal the ELIN, to route PSAP callbacks to the emergency caller. in context
• The Emergency Responder guide uses translation patterns in the phones' partition, with calling search space E911CSS, for 911 and for 9.911 (discarding PreDot digits) so both reach the 911 route point without secondary-dialtone delay. in context

Cite this source record

APA

WarmTransfer. (2026, September 24). Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cer-15-admin-configure-cucm

BibTeX

@misc{warmtransfer-cisco-cer-15-admin-configure-cucm,
  title  = {Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cer-15-admin-configure-cucm},
  note   = {Cisco Systems, accessed 2026-09-24}
}