McDewey

C H A P T E R 48 Client Matter Codes and Forced Authorization Codes • Client Matter Codes and Forced Authorization Codes Overview, on page 599 • Client Matter Codes and Forced Authorization Codes Prerequisites, on page 599 • Client Matter Codes and Forced Authorization Codes Configuration Task Flow, on page 600 • Client Matter Codes and Forced Authorization Codes Interactions, on page 603 • Client Matter Codes and Forced Authorization Codes Restrictions, on page 604 Client Matter Codes and Forced Authorization Codes Overview With client matter codes (CMCs) and forced authorization codes (FACs), you can effectively manage call access and accounting. CMCs assist with call accounting and billing for clients, and FACs regulate the types of calls that certain users can place. CMCs force the user to enter a code; this action specifies 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. FACs force the user to enter a valid authorization code that is assigned at a certain access level before the call is completed. Client Matter Codes and Forced Authorization Codes Prerequisites • Cisco Unified IP Phones that are running SCCP and SIP support CMC and FAC. • The CMC and FAC tones play only on Cisco Unified IP Phones that are running SCCP or SIP; TAPI/JTAPI ports; and MGCP FXS ports. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 599