|
|
|
| Chapter 4: CallFinder Software Screens | |
|
|
|
|
|
|
|
| Phone Book Screen Field Definitions (cont’d) |
| ||
|
|
|
|
|
|
| Field Name |
| Values | Description |
|
|
|
|
|
|
|
| First row |
| alphanumeric | Administrator row. |
|
|
|
|
| NOTE: This first row can be renamed as desired. |
|
|
|
|
| However, its function will always remain the |
|
|
|
|
| same: it is the party who serves as administrator |
|
|
|
|
| for the CallFinder system. Do not enter the |
|
|
|
|
| Name and DID number of an ordinary user in this |
|
|
|
|
| field. |
|
| Second row |
| alphanumeric | Ideally, a PBX extension is assigned to every |
|
| (with default label |
|
| available DID number. If, however, there are DID |
|
| “Unassigned Number”) |
|
| phone numbers to which no PBX extension has |
|
|
|
|
| been assigned, calls to these unassigned |
|
|
|
|
| numbers will go to the destination specified in |
|
|
|
|
| this field. (Calls involving corrupted DID numbers |
|
|
|
|
| also go to the party handling the Unassigned |
|
|
|
|
| Number function.) Such calls might reasonably |
|
|
|
|
| go either to the extension of a |
|
|
|
|
|
| |
|
|
|
| extension that plays a recorded message. |
|
|
|
|
| NOTE: This second row can be renamed as |
|
|
|
|
| desired. However, its function will always remain |
|
|
|
|
| the same: it is the destination for calls to DID |
|
|
|
|
| numbers to which no PBX extension has been |
|
|
|
|
| assigned. Do not enter the Name and DID |
|
|
|
|
| number of an ordinary user in this field. |
|
|
|
|
|
|
|
CF220 CallFinder User Guide | 43 |