Field Notice: FN74155 - Cisco Emergency Responder Emergency Location Identification Number Lookup (ELIN) Fails When Making an Emergency Call - Software Upgrade Recommended

Available Languages

Updated:May 31, 2024
Document ID:FN74155

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected


Affected Software Product Affected Release Affected Release Number Comments
Cisco Emergency Responder  15SU1 15SU1 (15.0.1.11900-15) See the How to Identify Affected Products section of this field notice.

Defect Information


Defect IDHeadline
CSCwk02122911 Call from IPv6Only device is routing through default erl when using IP Subnet Tracking
CSCwj89638911 calls matches default ERL after introduction of IPV6 subnet tracking feature
CSCwk09485Telephony Setting Use IP Address from Call Signaling is not taking affect in CER for Specific cases

Problem Description


Where IP Subnet tracking (IPv4 and IPv6) is used to track devices and clients, Cisco Emergency Responder Release 15SU1 may route emergency calls using the default Emergency Response Location (ERL) instead of the actual ERL associated for the location of the caller.


Background


Cisco has determined that the search for an IP/Subnet match may end prematurely, resulting in a failure to find a match and in the default ERL being used to route emergency calls (for example, 911) instead of the associated Emergency Location Identification Number (ELIN).

Both IPv4 and IPv6 Subnet tracking are affected.

The three associated defects are as follows:

  • CSCwj89638: 911 calls match default ERL after introduction of IPV6 subnet tracking
  • CSCwk02122: 911 call from an IPv6-only device is routing through default ERL when using IP Subnet Tracking
  • CSCwk09485: The telephony setting Use IP Address from Call Signaling is not taking affect in Cisco Emergency Responder for some cases

Problem Symptom


An emergency call (for example, 911) may match to the default ERL. This can result in a non-specific location assignment (ALI) and the wrong callback/Emergency Location Identification Number (ELIN) assignment.

This can result in emergency dispatchers responding to the wrong address, building, or location. In addition, depending on configuration and deployment, the call could be routed to an Emergency Call Relay Center to determine the actual location, which may incur a charge.


Workaround/Solution


Solution

To fix the issue that is described in this field notice, upgrade to a fixed software release or apply a COP file as a patch, as shown in the following table. To determine which release a device is running, see the How to Identify Affected Products section of this field notice. 

Affected Software Product Affected Release First Fixed Release
Cisco Emergency Responder 15 SU1 (15.0.1.11900-15) 15 SU1a (15.0.1.11901-3)

Or apply this COP file:
ciscocm.cer-V15SU1_ip-subnet-tracking_C0218-1.cop.sha512
 

Download the latest release of Cisco Emergency Responder from the Cisco Software Center. 

If a previous COP has been applied to patch two of the issues, Cisco still recommends installing the COP to ensure that all issues are patched.

Workaround

There is no recommended workaround.


How to Identify Affected Products


To determine if a device is running an affected release, log in to the Emergency Responder Administrator interface and choose About > Observe the System Version.

If the release is 15.0.1.11900-15 (this is known as 15SU1), see the Workaround/Solution section of this field notice.

CER Screenshot 2024-05-23 at 18-26-11-1.jpeg


For More Information


If an earlier or later release of Cisco Emergency Responder is installed, then the product is not affected.


Revision History


VersionDescriptionSectionDate
1.0Initial Release—2024-MAY-31

For More Information

For further assistance or for more information about this field notice, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:

Receive Email Notification About New Field Notices

To receive email updates about Field Notices (reliability and safety issues), Security Advisories (network security issues), and end-of-life announcements for specific Cisco products, set up a profile in My Notifications.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products