/mcpEmergency Call Handling Configuration Task Flow The administrator can use the following task to have a dynamic location for 9-1-1 emergency calling and transfer the call to emergency responders. Procedure Purpose Command or Action Create a SIP Trunk for routing the call to the RedSky server. Configure RedSky Server Step 1 Add the Service Profile details of an end-user for emergency calls. Configure Service Profile Step 2 Assign the created service profile to the Webex client end-user. Assign the Service Profile Step 3 Create SIP Route Pattern with the domain name and associate the same with the previously created SIP trunk. Setting Up the SIP Route Pattern for Routing Calls Step 4 Configure RedSky Server Use this procedure to create a SIP Trunk for routing the call to the RedSky server. Steps 7, 8 and 9 are only needed during on-premises integration. Note Procedure Step 1 From Cisco Unified CM Administration, choose Device > Trunk. Step 2 Click Add New. Step 3 From the Trunk Type drop-down list, choose SIP Trunk. Step 4 From the Protocol Type drop-down list, choose the type of SIP trunk that matches your deployment and click Next. Step 5 In the SIP Information area, enter an IPv4 address of the RedSky server, fully qualified domain name, or DNS SRV record for the server or endpoint that you want to connect to the SIP trunk in the Destination Address text box. Step 6 From the SIP Trunk Security Profile drop-down, assign a security profile. If you don't select this option, a SIP Trunk Security Profile nonsecure profile will be assigned. Step 7 (Optional) From the SIP Profile drop-down list, assign a Ping option enabled RedSky SIP profile. Step 8 (Optional) In the Normalization Script area, from the Normalization Script drop-down, choose redsky-alternate-id-interop. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 652 Custom Features Emergency Call Handling Configuration Task Flow