The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Contents
This chapter provides information to validate phone records. When you choose Validate Phones, the system runs a validation routine to check that the CSV data file and Cisco Unified Communications Manager Bulk Administration (BAT) phone template have populated all required fields, such as device pool and locations. The validation also checks for discrepancies with the first node database.
You must have a BAT phone template for the devices that you are adding. You can use a master phone template with multiple lines to add phones that have a single line or several lines. You must also have a data file in comma separated variable (CSV) format that contains the unique details for the phones or other IP telephony devices.
You must have a BAT phone template for the devices that you are adding. You can use a master phone template with multiple lines to add phones that have a single line or several lines.
You must have a data file in comma separated variable (CSV) format that contains the unique details for the phones or other IP telephony devices.
| Step 1 | Choose . The Validate Phones Configuration window displays. |
| Step 2 | To validate phone records that use a customized file format, click Validate Phones Specific Details radio button and continue with Step 4 and Step 5. |
| Step 3 | To validate phone records from an exported phones file that was generated by using the All Details option, click Validate Phones All Details radio button. |
| Step 4 | In the File Name drop-down list box, choose the CSV data file that you created for this specific bulk transaction. |
| Step 5 | For the Specific Details option, in the Phone Template Name drop-down list box, choose the BAT phone template that you created for this type of bulk transaction. |
| Step 6 | To verify the chosen CSV data file with the first node database, click Submit. The job gets submitted and gets executed immediately. |
The validation of phones has the following limitations:
The validation process only checks for the number of lines that are configured on the template; it does not check the line numbers that are configured on the template. After running the Validate phones - specific details job, the administrator sees the following message in the log when the CSV date file contains more lines than are supported by the phone template: "WARNING: CSV contains more number of lines than are supported by the phone template." If blank Directory Numbers and/or blank Speed dials and/or blank Busy Lamp Field Speed Dials exist, this indicates that the warning message that is displayed in the summary log file may be inaccurate.
The validate process does not check whether mandatory fields are specified in the CSV file.
If IP phone service parameters are specified in the phone text file, the validate process only checks whether a parameter exists with a name that is specified in the CSV on Cisco Unified Communications Manager. It does not check whether the parameter that is specified is configured on the IP phone service.