Convert from Telephone Directory based ADF to Phone Book Directory based ADF

If you are currently using Telephone Directory based ADF files it is recommended that you convert to Phone Book Directory based ADF files to take advantage of the additional information available within the MiVoice Business.

A convert from a Telephone Directory is performed when you click the Synchronize Now button in the Directory Administration Maintenance panel if there is an exported ESM Phone Book directory file in the ESM Directory Synchronization folder.

To convert from Telephone Directory based ADF to Phone Book Directory based ADF

  1. Ensure you have Administrative Access enabled to perform an ESM sync operation. If it is not already enabled, re-run the configuration wizard to select the option.

  2. Create a new ADF folder on a local or shared drive.

  3. Copy your existing ADF data and mapping files as well as your comments file from the existing folders to the new ADF folder.

  4. Export The MiVoice Business ESM Phone Book Directory.

    • Schedule a Once-only CSV FTP Phone Book Export on the MiVoice Business. See the topic Scheduler in the MiVoice Business System Administration Help.

    • Copy the exported file to your new ADF folder. Ensure the file name is pre-pended with ‘PB'.

  5. In the Directory Administration Configuration panel of your console, select the new ADF folder for your data, mapping, and comments files.

  6. In the Directory Administration Maintenance panel select the new folder for the ESM Directory Synchronization location and click the Synchronize Now button. A dialog box will be provided indicating that a conversion will be performed and informing you of how many matches were identified, as well as the total number of entries in each file. Press Continue to start the synchronization process.

    Note: It is recommended that the console be placed in absent mode prior to performing a Synchronize Now operation, since the console will not be able to manage calls for the duration of the process.
    Note: Upon completion of the synchronization, the ADF data and mapping files are converted to add new fields from the MiVoice Business and remove the entries that were excluded from the phonebook.

  7. Test your new ADF files. You will see the following changes to your phone book columns:

    • Name – The existing name field that represented the full telephone directory name prior to the conversion will hold the first name from the User and Services Configuration form if configured, otherwise it will hold the first name portion of the Telephone Directory form name. Note that if the telephone directory name is not in ‘last name, first name’ format, the full telephone directory name is populated in this field. See MiVoice Business Directory Configuration Guidelines for more information.

    • Last – This new field will hold the last name from the User and Services Configuration form if configured, otherwise it will hold the last name portion of the Telephone Directory form name.

    • Email – This new field will now contain the email field from the User and Services Configuration Form. If your ADF file already has an existing field with the name Email, it is retained and the column number from the ADF mapping file is added to the new email field name (eg. Email 13).

    • Prime Phone Service – This new field is determined by the prime phone service field for the user in the User and Services Configuration Form (if applicable).

    The existing additional fields are retained. These fields are hidden by default, but may be enabled for troubleshooting purposes:

    • Telephone Directory Name – This field contains the full name from the Telephone Directory form.
      Tip: You can customize the column header names in row 4 of the mapping file. Ensure the file is saved in CSV (Comma Delimited) format.
      Tip: Add and remove columns in the console display as needed. See Customize the Directories Area in the MiVoice Business Console Operator Help.
      Tip: If the operators have difficulty finding a name, enable the Telephone Directory Name field to determine if there are inconsistencies in the MiVoice Business configuration.
      Tip: Operators who are used to searching first and last names from the Full Name field in previous releases may find it helpful to use the Phone Book Search All feature.
    • GUID – This is the unique identifier that identifies the User in User and Configuration form.
  8. To complete the Phone Book conversion process:

    • Ensure all the consoles have been upgraded to Release 8.0.

    • Copy the new ADF data, mapping and comments files back to their original locations.
      Note: If you do not want all consoles to use the Phone Book Directory based files immediately you will need to maintain different folders for your Phone Book based ADF and comments files and your Telephone Directory based ADF and comments files. Note that the shared comments that are modified during this period will need to be updated by a console running Phone Book based ADF and by a console running Telephone Directory based ADF.
      Note: After a conversion has taken place, you cannot convert your Phone Book ADF files back to Telephone Directory based ADF files. If you wish to retain the original files as a backup, copy them to another location before moving the Phone Book based files back.
Parent topic: Phone Book Directory based ADF
↑