[Index]

Model: view/HcsMovePhonesVIEW

Move Phones

Full HTML Help

PROVIDER ONLY

Tip

Use the Action search to navigate Automate

Overview

You can move phones between sites only if they are not assigned to users.

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 Move users, without services

Restrictions that apply when moving phones

You can only move phones when the following conditions are met:

When moving a phone with an intercom line, the line is not moved or updated.

Related topics

Move a phone

This procedure moves one or more phones.

  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 Phones.

  4. At Action, choose an option:

  5. To verify that the phone or phones were moved to the correct target site, go to Phones.

Moving phones from site to site

PROVIDER ONLY

Tip

Use the Action search to navigate Automate

As an administrator, you can move phones from one site to another.

Certain conditions must be met for a site-to-site move to succeed. When moving a phone between sites, Automate checks the following:

Note

Quick Add User with phone/line/EM/SNR/voicemail can be added to site and moved across the sites within the same country.

Models and Relations Moved (SLC)

For moves between sites with SLC type dial plans:

Note

Models and Relations Moved (Non-SLC)

For moves between sites with non-SLC type dial plans:

Note

Warnings are logged for any lines associated with:

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 support the Overbuild Tool for Managed Services, the certain fields are updated in the Phone and Line devices to the target site's default settings.

Within device/cucm/Phone, the following models and fields are updated:

Within device/cucm/Line, the following models and fields are updated:

Model Details: view/HcsMovePhonesVIEW

Title Description Details
Action The type of Move action to perform.
  • Field Name: move_action
  • Type: String
  • MaxLength: 1024
  • Choices: ["Move phones by names", "Move phone by name"]
Phone Name of individual phone that will be moved.
  • Field Name: one_name
  • Type: String
  • MaxLength: 1024
  • Choices: [" "]
Note Information regarding the specified action.
  • Field Name: note
  • Type: String
  • MaxLength: 1024
Move From Hierarchy The name of the hierarchy node from which the phone will be moved if the conditions are satisfied.
  • Field Name: move_from_hn
  • Type: String
  • MaxLength: 1024
Move From Hierarchy Count The number of the hierarchy nodes that match the from phone name. Default: TBD
  • Field Name: move_from_hn_count
  • Type: String
  • Default: TBD
  • MaxLength: 1024
Move To Hierarchy The name of the hierarchy node to which the phone will be moved if the conditions are satisfied.
  • Field Name: move_to_hn
  • Type: String
  • MaxLength: 1024
  • Choices: [" "]
Move All Phones Move all the phones at the move from hierarchy. Default: false
  • Field Name: move_all_phones
  • Type: Boolean
  • Default: false
Phones Names of phones that will be moved.
  • Field Name: names.[n]
  • Type: Array