.. _move-phones: Move Cisco Phones -------------------- .. _25.4|EKB-28120: .. _25.4|EKB-28167: :bdg-secondary:`provider-only` .. tip:: :ref:`use-action-search-to-navigate-automate` Overview .......... You can move phones between sites only if they are not assigned to users. When moving a Cisco phone, you can choose whether to move the phone's associated lines to the target site. * If **Move lines to new site** is selected, any associated lines are moved along with the phone where supported. * If **Move lines to new site** is not selected, the phone is moved without moving its lines. In this case, lines may be disassociated or left unchanged depending on the source and target site dial plan type. Moving a phone between sites handles the situation where a phone is either physically moved or logically assigned to a different site. If a phone is assigned in the Associated Devices list of a CUCM user, the phone is moved during a user move. See :ref:`move-user-without-services` Move Cisco Phone settings .......................... To move Cisco phones, go to **Move Cisco Phone**. .. image:: /src/images/move-cisco-phone.png Settings on this field are: * **Move From Hierarchy**: The name of the hierarchy node from which the user will be moved if the conditions are satisfied. * **Phone Name (Unassociated Phones Only)**: Only phones which are not associated to users can be moved * **Move To Hierarchy**: The name of the hierarchy node to which the user will be moved if the conditions are satisfied. * **Move lines to new site**: Enable this setting to move any lines associated with the user to the new site (Default: true) * **Use default CSS at new site**: Use the CSS defined as the site default. * **Calling Search Space at new site**: Specify a specific CSS to be used at the new site. * **Use default device pool at new site**: Use the CSS defined as the site default (Default: true) * **device pool at new site**: Choose a specific device pool to be used at the new site * **Move Phone**: Default: true Restrictions that apply when moving phones ............................................. Phones can be moved between sites within the same customer hierarchy. Moving phones between different customers is not supported. You can only move phones when the following conditions are met: * The phone you wish to move must not be assigned to a user * Phones can only be moved from one site to another site: * Phones can't be moved from a customer to a customer. * Source and target site must reference the same NDL * Source and target site must have the same type of dial plan * Source and target site must have the same country When moving a phone with an intercom line, the line is not moved or updated. .. rubric:: Related topics * :ref:`ini-reserve-for` Move a Cisco phone ..................... This procedure moves a Cisco phone to a different hierarchy. 1. Log in as a provider, reseller, or customer administrator. 2. Set the hierarchy path to the customer whose phones you are moving. 3. Go to **Move Cisco Phone**; then, configure settings: * From **Move from Hierarchy**, select the source site. * From **Phone Name (Unassociated Phones Only)**, select a phone. .. note:: Only standalone (unassigned) phones are displayed for selection. Phones that are currently assigned to users do not appear in the list and must be moved as part of a user move. * From **Move To Hierarchy**, select the target hierarchy. * At **Move lines to new site**: * Select **Move lines to new site** to move the phone together with its associated lines where supported. If set to true, enable or disable **Use default CSS at new site**. If set to false (disabled), select a **Calling Search Space at new site**. * Clear **Move lines to new site** to move the phone without moving its lines. .. note:: Line handling depends on the site dial plan type. * Enable or disable **Use default device pool at new site**. If disabled, choose the device pool at the new site. * Enable or disable **Move Phone** to move the move with the settings configured. 4. To verify that the phone was moved to the correct target site, go to **Cisco Phones**. .. _moving-phones-from-site-to-site: Moving phones from site to site .................................. :bdg-secondary:`provider-only` As an administrator, you can move phones from one site to another. When moving phones between sites, line handling depends on both the site dial plan type and the selection of the **Move lines to new site** option in the **Move Cisco Phone** form. Certain conditions must be met for a site-to-site move to succeed. When moving a phone between sites, VOSS checks the following: * The source and target sites must reference the same NDL * The source and target sites must have the same country configured * The source and target sites must have the same type of site dial plan deployed * Whether the phones are assigned to users * Whether the phones are under same customer * Whether the phones are moving between sites .. note:: Quick Add User with phone/line/EM/SNR/voicemail can be added to site and moved across the sites within the same country. .. rubric:: Models and Relations Moved (SLC) For moves between sites with SLC type dial plans: * ``device/cucm/Phone`` (includes ``device/cucm/Line``) .. note:: * Lines are disassociated from the phone * Warnings are logged for any lines associated with the phone .. rubric:: Models and Relations Moved (Non-SLC) For moves between sites with non-SLC type dial plans: * ``device/cucm/Phone`` * ``device/cucm/Line`` * ``device/cucm/InternalNumberInventory`` .. note:: Warnings are logged for any lines associated with: * an E164 Inventory * a Call Pickup Group * a Hunt Group * a Remote Destination .. rubric:: Moving Phones Between Non-SLC Sites with a DNR Configured For moves between non-SLC sites with directory number routing (DNR) configured at *either* site, a warning appears stating that any lines associated to the phone being moved may not work correctly unless you take one of the recommended actions provided. See the Advanced Configuration Guide to perform the first recommended action. .. note:: * To see warning messages see the phone move log messages. * Moving phones from Non-SLC to Non-dial plan site will not dissociate the lines, but movement from SLC to Non-dial plan site will dissociate the lines. To support the Overbuild Tool for Managed Services, certain fields in the Phone and Line devices are updated to the target site's default settings. Within ``device/cucm/Phone``, the following models and fields are updated: * Phone * Device Pool Name * Location Name Within ``device/cucm/Line``, the following models and fields are updated: * Line * Call Forward All * Calling Search Space * Route Partition Name * Share Line AppearanceCssName