.. _set_up_cisco_emergency_responder: Configure Cisco Emergency Responder (CER) ------------------------------------------ This procedure configures Cisco Emergency Responder (CER) on VOSS Automate. .. note:: * For more information on CER installation and setup, refer to the Cisco Emergency Responder Administration Guide. * References to HCM-F and Shared Data Repository (SDR) are only relevant if installed. **To configure CER**: 1. Log in as the appropriate hierarchy administrator. 2. Set the hierarchy path to the correct level. Shared instances are created at the provider, reseller, or customer level. Dedicated instances are created at the customer level. 3. Choose **Apps Management > CER > Servers**. 4. Perform one of the following: * To add a new Cisco Emergency Responder (CER) in VOSS Automate, click **Add**. * To modify an existing CER, click its name in the list of Cisco Emergency Responders. 5. Enter a name for the Cisco Emergency Responder in the **CER_Virtual Server Name** field. .. note:: A Cisco Emergency Responder server that has been configured in HCM-F and synced into VOSS Automate may exist at the sys.hcs hierarchy. If the server name you enter matches this server, the **Migrate from HCM-F to VOSS Automate** check box is displayed. Click **Save** to migrate this server to the current hierarchy level. The fields will be populated with the values that were configured in HCM-F. If you do not want to migrate the server, enter a different server name. 6. Select the **Publisher** check box if you are configuring a publisher node. .. note:: The **Publisher** tab is populated only when the **Publisher** check box is selected. 7. Expand **Network Addresses**. a. Choose the SERVICE_PROVIDER_SPACE address space. b. Enter the IP address of the CER Server in the **IPV4 Address** field. .. note:: Either the hostname or the IP address is required. Ensure that the hostname or IP address does not contain a trailing blank space. VOSS Automate cannot validate an entry that contains a blank space at the end of the hostname or IP address. c. The **Hostname** field is automatically populated with the CER Name. Edit it if necessary. d. Fill in the domain of the CER application. e. Provide an optional description for the network address. 8. Expand **Credentials**. a. Add credentials for PLATFORM and ADMIN credential types. Click + to add more credentials. b. Fill in the user ID and password that you configured when you installed the CER. c. Choose RO (Read-only) or RW (Read or Write) for the Access Type. The default is RO. d. Provide an optional description for the credential. PLATFORM and ADMIN are required for license management. 9. Fill out the fields on the **Publisher** tab: .. tabularcolumns:: |p{3cm}|p{12cm}| +--------------+-----------------------------------------------------+ | Field | Description | +==============+=====================================================+ | | Select the version of the Cisco Emergency Responder | | Version | Servers in this cluster. The available versions | | | depend on the version of the HCM-F device that has | | | been configured. | +--------------+-----------------------------------------------------+ | | Read-only field. If creating at provider level, | | Multi-Tenant | this field is set to Shared. If creating at | | | customer level, this field is set to Dedicated. | +--------------+-----------------------------------------------------+ 10. Click **Save**. .. rubric:: Next Steps * Associate CER with Customers