.. _configure_intelligent_proximity: Configure Intelligent Proximity for Mobile Voice in VOSS Automate ------------------------------------------------------------------- **Prerequisites**: Ensure that you have the latest COP files for your Cisco IP phone, or device package downloaded and installed in Cisco Unified Communications Manager (Unified CM): * In your browser, open https://software.cisco.com/download/navigator.html?mdfid. * In the Product Search window, enter Unified Communications Manager Version 10.5. * Choose Software Type Unified Communications Manager/CallManager Device Packages. * Download and install the file cmterm-devicepack 10.5.2 12020-1cop.sgn in Unified CM. Each phone that you register to Unified CM contains phone-specific settings. These settings appear in Unified CM at the bottom of the Phone Configuration window under the Product Specific Configuration Layout heading. The settings vary by phone model, and are tailored to each phone model. The phone has default settings, but in the Unified CM Phone Configuration window, you can override the settings and configure new values. Use this high-level procedure to perform these tasks: * Ensure that all the required settings are enabled on Cisco Unified CM. * Import the settings into VOSS Automate so they appear on the Phone Management page for each registered phone. * Ensure that the settings are correct in VOSS Automate. * Pair the mobile phone or tablet with the Cisco IP endpoint. **Perform these steps**: 1. In Cisco Unified CM, choose these settings on the **Device** page: * Proximity Mode - Choose 'On' * Call Control - Choose 'Enabled' * Proximity Content Share From Clients - Choose 'Enabled' * Proximity Content Share To Clients - Choose 'Enabled' 2. Import phone features (or refresh existing phone features) using the Import/Refresh feature in VOSS Automate. This step imports each phone type's features as listed on the Product Specific Configuration Layout page in **Devices > Phones** in Unified CM into VOSS Automate. VOSS Automate imports the settings and only shows settings that were available and imported the last time the command was run. Perform this step any time there is a change on the Unified CM, such as adding new phone types or templates. However, we recommend that you perform this step every time. To import or refresh phone features, perform these steps: a. Log in to VOSS Automate as provider or reseller administrator. #. Choose **Device Management > Advanced > Perform Publisher Actions**. #. From the **Action** drop-down, choose **Import**. #. From the **App Type** drop-down, choose **CUCM Device**. #. In the Clusters box, click the cluster to be configured for the Intelligent Proximity feature in the **Available** window. Click Select to move the cluster to the **Selected** window. #. Click **Save**. 3. Verify that the Bluetooth settings are enabled. a. Log in to VOSS Automate as customer administrator and choose a valid site from the hierarchy node. #. Choose **Subscriber Management > Phones**. #. Choose the endpoint to pair with the mobile phone or tablet. #. On the **Advanced Information** tab, make sure that these fields are set correctly if they appear for the selected endpoint type: * **Bluetooth** drop-down - **Enabled**. * **Allow Bluetooth Contacts Import** drop-down - **Enabled**. * **Allow Bluetooth Mobile Handsfree Mode** drop-down - **Enabled**. 4. Pair the mobile phone or tablet with the Cisco endpoint (device such as a desk phone). For more information, see 'Intelligent Proximity for Mobile Devices' in http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8811_8841_8851_8861/10_5/ english/userguide/P881_BK_C9A41445_00_cisco-ip-phone-8811-8841.pdf. a. At the Cisco IP endpoint, make sure that Bluetooth and Handsfree 2-way audio are enabled. #. Add the mobile device. Once the mobile device is discovered, you can pair the two and also store mobile contacts on the Cisco IP endpoint. #. A security code may appear on both the endpoint and mobile device. Accept the security code on both the Cisco IP endpoint and mobile device before the pairing can be completed.