# Customizing FCOS

There are two ways to create customized FCOS selections if you need to apply special features to mailboxes. You can:

- copy an existing default FCOS, rename it, re-number it, and add or delete feature bits as required

OR

- create a new FCOS from scratch

Note: We recommend that you do NOT modify the default FCOS selections for two reasons:

1. When you modify an FCOS already assigned to a mailbox, all mailboxes with that FCOS behave according to the new definition, and

2. You may need to restore a default FCOS to help in troubleshooting a problem.

Use an FCOS Worksheet and the guidelines in this section to design a customized FCOS. To customize an FCOS, you can either copy a default FCOS or create a new FCOS. If you copy an FCOS, you start with a copy of an existing FCOS, then add or delete the required feature bits. Give this copy a new name and new FCOS number; for example, “10-NoLogin,” if the new FCOS is a copy of FCOS 10 (VIP) without feature bit 001. Although creating a new FCOS gives the experienced system administrator the maximum flexibility to customize call processing, this is the more complex option. Be aware that not all feature bits are compatible. For more information, see Suggested Additional FCOS, Feature Bits by Category and Feature Bit Descriptions in this chapter.

## COS Interactions

When you assign an FCOS, a Limits Class of Service (LCOS), and a Group Class of Service (GCOS) to a mailbox, certain options interact within and between each class of service. Some options require the presence of other options, and some combinations are not compatible. For more information see Other Classes of Service. Carefully analyze the intended function of each mailbox before you begin assigning classes of service.

Keep the following interactions in mind:

- The LCOS that you assign can affect the function of an FCOS feature. For example: If you give a mailbox the ability to receive user messages (feature bit 040), but you assign an LCOS with a User Message Length limit of 0 seconds, the mailbox will be unable to store an unplayed (or played) user message.

- Interaction between mailboxes is limited by the GCOS that you assign to each mailbox when it is created and by the FCOS assigned to other mailboxes within this GCOS. For example: If an FCOS allows a user to make private messages (feature bit 023), other users within the same GCOS must be able to receive messages from other users (feature bit 040) and to play confidential messages (feature bit 051); otherwise, the make private message feature is ineffective.

Note: When you create a COS using the Web console, you must provide a name for it. When you are using the Text console, however, you can create a COS with no name. Since the Web console does not allow you to view or edit an unnamed COS, you must use the Text console to modify (or name) any unnamed COS.

### FCOS

Some features require a primary feature bit in an FCOS, and some feature bits override others within the same FCOS. See Feature Bit by Category and Feature Bit Descriptions.

### LCOS

The LCOS that you assign to each mailbox can affect how a feature functions. For example, if you assign an FCOS that allows a mailbox to make messages (feature bit 020), but you assign an LCOS with a User Message Length limit of 0 seconds, the mailbox user cannot record a message.

### GCOS

The GCOS that you assign to each mailbox limits interaction between mailboxes. A user in one GCOS may not be able to receive any messages from a user in another GCOS, regardless of the FCOS. Also, the FCOS for the other mailboxes within one GCOS can affect mailbox interaction. For example, if an FCOS allows a user to make confidential messages (feature bit 023), the other users within the same GCOS must be able to receive messages (feature bit 040) and play messages (feature bit 050).

### FCOS Worksheet

When you are familiar with the features you can add to an FCOS, use the FCOS and Feature Bit Descriptions in this section as a basis for completing your FCOS Worksheet. Fill in an FCOS number (“FCOS to modify”) and name, and indicate if it is based on an existing FCOS (“FCOS to copy”). Circle all feature bits you wish to include. If you are including all the feature bits in a category, just circle the category name. Assign any number from 18-20 or 25-640 to your FCOS, and any name that helps you easily identify it. Complete one worksheet for each FCOS you design. Keep your completed sheets for future reference.

Note: FCOS information is stored in blocks of 64 FCOS per OAA record. To save disk space, use all FCOS from 1 to 64 before using higher numbers. Then use 65 to 128, and so forth. You probably will not use all categories listed. For any categories you do use, be sure to include the primaryfeature bits, those feature bits that enable other feature bits within the same category.

- Managing FCOS