Client Matter Codes and Forced Authorization Codes
This chapter provides information about using BAT to configure Forced Authorization Codes (FAC) and Client Matter Codes (CMC). You can create, update, delete, or add more CMC or FAC settings using either a CSV data file or a custom text-based CSV file.
Forced Authorization Codes (FAC) and Client Matter Codes (CMC) allow you to manage call access and accounting. CMC assists with call accounting and billing for billable clients, while Forced Authorization Codes regulate the types of calls that certain users can place.
Client Matter Codes force the user to enter a code to specify that the call relates to a specific client matter. You can assign client matter codes to customers, students, or other populations for call accounting and billing purposes. The Forced Authorization Codes feature forces the user to enter a valid authorization code before the call completes.
The CMC and FAC features require that you make changes to route patterns and update your dial plan documents to reflect that you enabled or disabled FAC and/or CMC for each route pattern.
Before you use BAT to configure CMC or FAC, review the following information:
Create separate CSV files for CMC and FAC. Do not mix the two features in a single CSV file.
When you add CMC or FAC settings for the first time, you can create a CSV file through BAT.xlt or create a custom text-based CSV file.
To update, delete, or add more CMC or FAC settings (not first time), you can edit an existing CSV file or create a custom text-based CSV file.
In the file/spreadsheet, do not enter two or more codes (and corresponding settings) on a single line. Designate a single line for each code (and corresponding setting). For example, use the following format when you enter codes for Forced Authorization Codes: (Authorization Code, Authorization Code Name, Authorization Level) 1234,John Smith,20 1235,Lisa Mendez,10 5551,Debbie Dunn,30
Deleting information from a file and leaving the information blank does not remove the information from the Cisco Unified Communications Manager database; in other words, a blank value does not overwrite an existing value in the database. Updating the values overwrites the existing value in the database.
Make sure that you upload the appropriate CSV files to the first node of the Cisco Unified Communications Manager server.
Any time that you create or change a CSV file, you must insert the CSV file in BAT to update the Cisco Unified Communications Manager database.
You can create the CSV file for CMC or FAC using the BAT spreadsheet BAT.xlt. You must create two separate CSV files, one for CMC and one for FAC.
The BAT.xlt file exists on the first node of the Cisco Unified Communications Manager server; however, you normally do not have Microsoft Excel installed on the server. In that case, copy the file from the first node and move it to a local machine that has Microsoft Excel installed.
CSV data file creation for Client Matter Codes and Forced Authorization Codes using text editor
You can use a text editor to create the text-based CSV data file for client matter codes and forced authorization codes. The comma separated values (CSV) file provides textual information in tabular form and contains lines of ASCII text with values separated by commas.
You update existing codes by manually updating an existing CSV file or creating a new CSV file using a text editor.
If you are updating a CMC CSV file, for example, you may enter 5555,Acme Toys, where 5555 equals the mandatory client matter code, and Acme Toys equals the description.
If you are updating a FAC CSV file, for example, you may enter 1234,John Smith,20, where 1234 equals the forced authorization code, John Smith equals the authorization code name, and 20 equals the authorization level.
You can change any part of an existing record, but you must include the code; for example, the forced authorization code or client matter code. Deleting information and leaving it blank does not remove the information from the database; a blank value does not overwrite an existing value in the database, but, updating the value, for example, to Acme Toys, Inc. or John L. Smith from the preceding examples, overwrites the existing value in the database.
To edit existing CSV data files, download the CSV files from the first node of the Cisco Unified Communications Manager server to your local workstation.
Open and edit the existing CSV file using a text editor.
Delete existing settings, add new codes, or update existing settings. See Table 1 for descriptions of the CMC and FAC configuration settings.
If you add new codes at the same time that you update them, make sure that you enter all required information.
A blank value does not overwrite an existing value in the database, but updating the value overwrites the existing value in the database.
What to Do Next
Upload the CSV files to the first node of the Cisco Unified Communications Manager server.
You must add the CSV file to BAT and insert the file to update the Cisco Unified Communications Manager database.
The following table provides descriptions of the configuration settings in the CMC and FAC CSV data files.
Table 1 Configuration settings for CMC and FAC
For CMC CSV file
Client Matter Code
Enter a unique code of no more than 16 digits that the user will enter when placing a call. The client matter code displays in the CDRs for calls that use this code.
This optional field helps you associate a client code with a client. The description can include up to 50 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets (<>).
For FAC CSV File
Enter a unique authorization code that is no more than 16 digits. The user enters this code when the user places a call through a FAC-enabled route pattern.
Authorization Code Name
Enter a unique name that is no more than 50 characters. The authorization code name ties the authorization code to a specific user or group of users; this name displays in the CDRs for calls that use this code.
If you plan to assign an authorization code to every user in the system, make sure that the code name includes an identifier for the user, such as the user name or another unique, non-sensitive identifier; for example, an email alias or employee/student number. Do not use identifiers such as a social security number because the authorization code name writes to CDRs, which are not secure.
Enter a three-digit authorization level that exists within the range of 0 to 255; the default equals 0. The level that you assign to the authorization code determines whether the user can route calls through FAC-enabled route patterns. To successfully route a call, the user authorization level must equal or be greater than the authorization level that is specified for the route pattern for the call.
Update CMC or FAC in CUCM database using BAT
To update the Cisco Unified Communications Manager database, you must insert the CMC or FAC CSV data file using BAT.
Before You Begin
Before you can update Cisco Unified Communications Manager, you must create or edit a CMC or FAC CSV file.
In Cisco Unified Communications Manager Administration, choose one of the following options:
BAT settings to update CMC and FAC in the database
The following table provides descriptions of the BAT update configuration settings for CMC and FAC.
Table 2 Settings in BAT for inserting CSV files
Setting in BAT
From the drop-down list box, choose the CMC or FAC file that you want to insert.
Override the existing configuration
This check box applies if you are updating code for existing settings.
Checking this check box overwrites the existing authorization code name (FAC), authorization level (FAC), or description (CMC) with the information that is contained in the file that you want to insert (existing authorization and client matter codes do not change). If you do not check the check box, an error, which writes to the log file, indicates that the authorization or client matter code already exists; therefore, no updates occur.