/mcpCause: In this case the ELINs have been set as DID which is used to identify a caller's location. This should not be used on any phone or for any other purpose. Solution: Check the ELIN configuration information, and unset the ELINs that have been set as DID. Outgoing Calls Scenarios Outgoing Emergency Call Does Not Contain Calling Party as Emergency Location Number Problem: An outgoing emergency call does not contain the calling party as an Emergency Location (ELIN) number. Cause: The translation pattern or route pattern for this ELIN was not configured correctly. Solution: Check that the translation pattern or route pattern settings are correctly configured for this ELIN, and make sure that the Is an Emergency Services number check box is checked on the relevant translation pattern or route pattern configuration page. Outgoing Emergency Call Contains Modified Emergency Location Number Problem: An outgoing emergency call contains a modified Emergency Location (ELIN) number. Cause: The outgoing trunk or route list contains extra transformations that are not required for ELINs. Solution: Check the transformations that were applied for the call, and make sure that only the required transformations for ELINs are present on the outgoing trunk or route list. Incoming Calls Scenarios Incoming PSAP Callback Call Fails Problem: An incoming PSAP Callback call fails. Cause: The device that made the original emergency call was not registered correctly. Solution: Check whether the device that made the original emergency call is still registered and whether any Extension Mobility is involved. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 648 Custom Features Outgoing Calls Scenarios