Frequently Asked Questions about the Managed IP Phone Assistant

Question: If an IP phone has already been created from a migration item, can the migration assistant be re-run for that same item at a later date and be expected to re-convert?

Answer: No. It is recommend to use Interaction Administrator to make any modifications on the phone at this point.

Question: If a migrated Polycom phone configuration file has a registration for a shared appearance or a station that does not exist in Interaction Administrator, will that shared appearance or station be added to the new managed IP phone?

Answer: No. The assistant uses the information in the Polycom configuration file to match existing information in Interaction Administrator. If the identification address in the configuration file does not exist in Interaction Administrator, either for an un-managed station or a shared appearance, then registration will not be added to the new IP phone.

Question: When the migration code converts a migration item to an IP phone, and all of the stations that are added to the phone are marked as "inactive", is the resulting IP phone "inactive"?

Answer: Yes.

Question: What time zone is used for a new managed IP phone?

Answer: No time zone is used, because there is no time zone setting directly on a managed IP phone. The managed IP phone uses the time zone based on the location setting assigned. The migration process used the location found on the first private station added to the IP phone.

Question: Does the assistant support the 000000000000.cfg file for migrating Polycom phone configurations?

Answer: No. The assistant uses the configuration file's name to determine the MAC address that is assigned to the migration item.

More: When a Polycom phone tries to request it's main configuration file, the phone will first try to get it by requesting the phone's .cfg file based on it's MAC address. If that doesn't exist, it will ask for "000000000000.cfg" for its configuration information. This makes sense from  the phone's perspective, because the phone knows its MAC address. Looking at it from the assistant's perspective, the migration would have to be given a list of phone MAC addresses that exist at a site, which is not supported.

Question: Does the migration support substitution of a phone's MAC address for the [MACADDRESS] syntax in a phone's CONFIG_FILES entry?

Answer: Not at this time. In general, this is used for sites that want phones to pick up main configuration from the 000000000000.cfg file. As an example, the list of configuration files to load might look like this in 000000000000.cfg:

CONFIG_FILES="phone-[MACADDRESS].cfg, phone1.cfg, sip.cfg"

If the phone whose MAC address was 0004f20352b2 went to find the files it should load, it would replace the [MACADDRESS] with 0004f20352b2 so we could think of the list looking like:

CONFIG_FILES="phone-0004f20352b2.cfg, phone1.cfg, sip.cfg"

Again, since the migration doesn't know the MAC addresses of phones that would possibly be requesting configuration at a site, it does not have support for the [MACADDRESS] substitution.

Question: What manufacturers and models are supported for managed IP phones in Interaction Administrator?

Answer: If migrating, the supported models are listed in the pull-down list in the Select Default Model page of the assistant. If importing, the supported models are listed in New Managed IP Phone.