/mcpClient Matter Codes and Forced Authorization Codes Configuration Task Flow You can implement CMCs and FACs separately or together. For example, you may authorize users to place certain classes of calls, such as long distance calls, and also assign the class of calls to a specific client. CMC and FAC tones sound the same to the user; if you configure both codes, the feature prompts the user to enter the FAC after the first tone and enter the CMC after the second tone. Before you begin • Review Client Matter Codes and Forced Authorization Codes Prerequisites, on page 599 Procedure Purpose Command or Action After you finalize the list of CMCs that you plan to use, add those codes to the database and enable the CMC feature in route patterns. To Configure Client Matter Codes, on page 600, complete the following subtasks: Step 1 • Add Client Matter Codes, on page 601 • Enable Client Matter Codes, on page 601 After you finalize the list of FACs and authorization levels that you plan to use, add To Configure Forced Authorization Codes, on page 602, complete the following subtasks: Step 2 those codes to the database and enable the FAC feature in route patterns. • Add Forced Authorization Codes, on page 602 • Enable Forced Authorization Codes, on page 602 Configure Client Matter Codes Procedure Purpose Command or Action Determine unique client matter codes that you want to use and add them to your system. Add Client Matter Codes, on page 601 Step 1 Because the number of CMCs directly affects the time that is required for your system to start up, limit the number of CMCs to a maximum of 60,000. If you configure more CMCs than the maximum number, expect significant delays. Enable client matter codes through a route pattern. Enable Client Matter Codes, on page 601 Step 2 Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 600 Custom Features Client Matter Codes and Forced Authorization Codes Configuration Task Flow