.ps 59,78 .nhy .nfl accept .rm 78 .lm +5;.rm -3 .literal M E M O R A N D U M Date: March 20, 1986 To: VAXNET Users. From: Robin Miller. Subject: Phone Logging / Authorization. .end literal .p This memo describes the phone logging and authorization features added to the VAXNET program. These features only affect systems using autodial modems although similar authorization could be added for direct lines as well. .hl 1 Phone Authorization. To enable the phone authorization feature, define the logical name VAXNET$PHONE_AUTH to the authorization file to use. The program looks for this logical name in the GROUP and SYSTEM logical name tables. This allows access to be controlled by either group, system wide, or both. The format of the phone authorization file is as follows: .literal username [ LOCAL ] [! Comments. ] .end literal The first field contains the user's login name which can optionally be followed by the keyword "LOCAL" and comments. The fields can be separated by tabs and/or spaces. The second field if defined to "LOCAL" prevents the user from making long distance phone calls. If "LOCAL" isn't specified, the user is allowed both local and long distance phone calls. The third field is for comments which are ignored by the program. .s Long distance phone calls are detected by the number of digits in the phone number exceeding the local digits count (by default 8). I choose the default digits count by presuming that most people must dial 9 to get an outside line through their PBX system followed by the 7 digit phone number (i.e., 9-nnx-line = 8 digits). This count can be overridden by defining the logical name VAXNET$LOCAL_DIGITS to the value required. This logical must be defined in either the GROUP or SYSTEM logical name tables. The system logical name, if defined, takes precedence over the group logical name. By defining this logical to a small value (i.e., 0), you can prevent both local and long distance access if desired. .s If access is denied, one of the following messages is displayed and the program exits. .literal *** Sorry, you are not authorized to make long distance calls. *** *** Sorry, you are not authorized to use the autodial modems. *** .end literal When creating the phone authorization file, ensure you allow either group and/or world read access for the GROUP and SYSTEM logical name table entrys respectively. If errors are encountered either when openning or reading from the file, appropriate error messages are displayed and the program exits. .hl 1 Phone Logging. To enable the phone logging feature, define the logical name VAXNET$PHONE_LOG to the phone log file to use. The program looks for this logical name in the PROCESS, GROUP, and SYSTEM logical name tables and makes entrys in each file found. Please note that the phone log files pointed to by the GROUP and SYSTEM logical name must have write access for group or world respectively. If the initial log file doesn't exist, VAXNET creates the file with the default protection of the current user. Thereafter, the entrys are appended to the end of the phone log file. If an error occurs either when opening or writing to the phone log file, further access to that file is disabled. The format of each phone log entry is listed below: .rm +3 .literal Phone log record format: Field Width Description Of Field ----------- -------------------- (20) date/time The date and time of the log entry. (12) username The user name making the phone call. ( 8) account_name The account name from the authorization file. (10) modem_type The type of autodial modem. This is useful for systems with different autodial modem types. ( 8) modem_port The modem port used for the phone call. The format is: _ddcn: dd = device name (i.e., TX) c = controller (i.e., A) n = unit number (i.e., 0) I've allowed 3 characters for the unit number. ( 4) modem_speed The speed of the modem port. ( 9) entry_type The type of entry logged (see below). ( 7) modem_state This field contains the state of the modem at the time of the log entry. The state is based upon the status of the modem carrier signal. ONLINE = The modem is online. (Carrier) OFFLINE = The modem is offline. (No Carrier) (25) phone_number The phone number which was dialed. This number appears exactly as the user typed it in. (60) phone_comment The phone number comment. This field contains the characters which follow the comment character (!) following the phone number. For example, to specify a comment in the DCL symbol phone number use: $ PHONE_NUMBER :== "9-nnx-line ! Comment." ( 1) end_of_record This field contains the character (|) which is used show the end of the record. This field was used to force padding of the phone comment field. .end literal .rm -3 Each of the above fields is separated by a single space for readability except for the end of record field. The total length of the log record is 174 characters for those who may want to generate reports from this file (possibly using Datatrieve). .hl 2 Phone Log Entry Types. This section describes the type of entrys which way get written to the phone log file. .hl 3 CALLBACK The user was called back. This entry type is logged after the phone number is dialed and the call-back feature is enabled. .hl 3 DIALOUT The user dialed out. This entry type is logged after a phone number is dialed by a user on the system. .hl 3 HANGUP The modem was hungup. This entry type is logged each time the modem is hungup. .hl 3 NOAUTH The user is not authorized. This entry type is logged when an unauthorized user attempted to use the autodial modems. This entry can only be logged if phone authorization is enabled. .hl 3 NOCARRIER The carrier signal was lost. This entry type is logged during the virtual terminal mode when the modem check feature is enable to detect the lost of modem carrier. Later, this type of entry will also be logged when modem carrier is lost during file transmissions (not done yet). .hl 3 NOHANGUP The user requested no modem hangup. This entry type is logged when the program exits and the user requested the modem not be hungup. This entry type is useful to find out "Who forgot to hangup the modem?". .hl 3 NOLONG - No long distance authorization. This entry is logged when a user not authorized to make long distance calls. This entry type can only be logged when phone authorization is enabled. .hl 3 NOPORTS - No modem ports are available. This entry type is logged when trying to assign a remote port at startup time. This information can be used as justification of needing more autodial modems when this type of entry is being logged frequently.