Table: Field Definitions; Remote Subscriber Screen
Field |
Valid Input |
Procedure/Description |
Subscriber Name: |
A string of 1 through 29 alphabetic characters |
Enter the name of the remote user to be added or changed. This is a mandatory input field; there is no default value. The name must be unique. We suggest that you enter the last name first, and then a comma, and then the first name. For example: Doe,Jane. However, any combination of letters may be used. (Notice that there are no blank (embedded) spaces in the example. That is, it was not entered as Doe,�Jane. We recommend that you enter names this way.) Furthermore, in places where telephones have letters accompanying the numbers, each name must be unique as entered on the keypad of a touchtone telephone. For example, use Doe,JaneA and Doe,JaneZ to distinguish between two subscribers named Jane Doe. |
Extension: |
A 3-digit to 10-digit telephone extension |
Enter the user's telephone extension. The extension must:
- Be within the range of numbers assigned to the remote machine.
- Not be assigned to another user on the same remote machine. The address (prefix plus extension) must be a unique address among all networked machines.
- Be of the length administered on the remote machine
|
Machine Name: |
Display only |
The name of the machine on which the remote user is administered, if the user is an administered user. |
Address: |
Display only |
The unique identifier created by combining the prefix assigned to the machine and the user's extension. |
Community ID: |
Blank or an integer from 1 through 15 |
Enter the community ID to be assigned to this user. A community is a group of users that is restricted from sending messages to other designated groups. For more information on community sending restrictions, see Setting Up Community Sending Restrictions. If this field is left blank, the system default community ID from the Machine screen for the local machine is used. If sending restrictions are in place on your network, the Community ID for this user must be the same on this machine as on the user's local machine. |
Administered? |
Display only |
When you manually add a remote user, the system automatically places a y in the field. Also, if a nonadministered remote user becomes administered through a remote update, the value in this field changes from n to y. If a remote system calls the local system and sends a message from a nonadministered remote user, the local system creates a verified remote user record in the database and places an n in the field. |
Voiced Name? |
Display only |
This field contains an n until you record the user's name or the user's voiced name comes across from the user's local machine during an update. This field automatically changes to y when you record the user's name or the user's voiced name comes across from the user's local machine during an update. |
Non-Administered Type: |
Display only |
This field displays the type of nonadministered user, such as verified. |
Last Usage Date: |
Display only |
This field displays the most recent date the remote user received a message in the Last Usage Date: field. The field helps you to determine the call traffic for the user. |