Client Matter Codes and Forced Authorization Codes

Client matter codes (CMC) and forced authorization codes (FAC) can be applied to route patterns.

CMCs are typically used in professional organizations where a great deal of business is transacted over the phone and clients are billed for such time. The CMC is added to call details records (CDR) to allow accounting and billing of calls based on their client matter. If a route pattern that has a CMC applied is matched, the user is prompted to enter a CMC for the call to be extended.

Valid CMCs are created in the system and associated with the company that will be paying for the services of the organization. For calls to be extended, users have to enter a valid CMC.

FACs are used to prevent calls from being placed by unauthorized users. Some organizations use unique FACs for every user in the system for legal or accounting reasons. We will investigate using FACs as another way of restricting calls similar to using CSSs. If a route pattern is matched to a pattern that has a FAC applied, the user is prompted to enter a FAC for the call to be extended. CSSs and FACs are not mutually exclusive; they can be used together.

Valid FACs are added to CUCM, and an authorization level is assigned to FACs. If a FAC is required for a route pattern, the minimum required authorization level has to be specified at the route pattern. Users have to enter a valid authorization code whose authorization level is equal to or greater than the level configured at the FAC-enabled router pattern.

Figure 13-18 illustrates a CMC application where UserA dials a number that matches a route pattern where the Require Client Matter Code parameter is checked. CUCM plays a tone to indicate to the user that a CMC has to be entered. The user has to enter a valid CMC for the call to be extended. In the example, CMCs 1234, 1244, and 3489 are configured. The user entered 1234. If the user does not terminate the code with the # sign, the user will have to wait until the interdigit timeout (T.302 timer) expires (15 seconds by default). The call is successful, and the entered CMC is included in the generated CDR.

Figure 13-18 Client Matter Code: Successful Operation r Route Pattern* Route Partition L 0 Require Client Matter Code

9.12125551XXX

LDPSTN_PT

r Route Pattern* Route Partition L 0 Require Client Matter Code

UserA

Voice GW

Figure 13-19 uses the same configuration as the preceding example, but this time UserA enters 5555 at the CMC prompt. This is not a valid CMC; therefore, the call is denied. A CDR is generated for the attempted call if the CDR Log Calls with a Zero Duration Flag CallManager service parameter has been enabled. Calls with zero duration flags are not logged in CDRs by default.

UserA

Voice GW

Figure 13-19 uses the same configuration as the preceding example, but this time UserA enters 5555 at the CMC prompt. This is not a valid CMC; therefore, the call is denied. A CDR is generated for the attempted call if the CDR Log Calls with a Zero Duration Flag CallManager service parameter has been enabled. Calls with zero duration flags are not logged in CDRs by default.

Figure 13-19 Client Matter Code: Call Failure

Route Pattern* Route Partition

0 Require Client Matter Code

9.12125551XXX LDPSTN_PT

CMC Codes:

1234 1244 3489

Route Pattern* Route Partition

0 Require Client Matter Code

UserA

Voice GW

Voice GW

In Figure 13-20, UserA dials a number that matches a route pattern where the Require Forced Authorization Code parameter is checked and the Authorization Level is set to 3. CUCM plays a tone to indicate to the user that a FAC has to be entered. The user has to enter a valid FAC with an authorization level of 3 or above for the call to be extended. At the prompt, the user enters 1888. Because the FAC level of the code was equal to or higher than the required authorization level, the call is successful, and the name of the entered FAC is included in the generated CDR.

Figure 13-21 has the same configuration as the preceding example, but this time UserA enters 1234 at the FAC prompt. The call is denied because the authorization level of the entered FAC is lower than the required level configured at the route pattern. A CDR is generated logging the attempted call.

Figure 13-20 Forced Authorization Code: Successful Operation

Route Pattern*

9.1[2-9]XX[2-9]XXXXXX

Route Partition

LDPSTN_PT

0 Require Forced Athorization Code

Authorization Level*

1234: Level 1 1244: Level 2 1888: Level 7

Voice

UserA

Voice

Figure 13-21 Forced Authorization Code: Call Failure

Route Pattern* Route Partition

9.1[2-9]XX[2-9]XXXXXX

LDPSTN_PT

0 Require Forced Authorization Code

Authorization Level*

1234: Level 1 1244: Level 2 1888: Level 7

Was this article helpful?

+1 -1

Responses

  • ANNE KOLKKA
    When did authorization for code J0221?
    1 month ago

Post a comment