Example 12-1 configures a set of PMDF-FAX channels at EXAMPLE.COM on node NAPLES, and Example 12-2 shows a corresponding checklist file. This is the same sample site pictured in Figure 4-1 and configured in Example 4-1.

Whenever appropriate, each prompt also supplies a default answer which is enclosed within square brackets. Simply pressing return, [RETURN], selects the default answer.

Remember that the values in this sample are for purposes of example only. Be sure to use the values appropriate for your system when you perform the actual configuration.

Example 12-1 Example PMDF-FAX Configuration

$ SET DEFAULT PMDF_TABLE: $ PMDF CONFIGURE FAX PMDF-FAX Configuration Utility, Version 6.2 This utility creates a set of rewrite rules and channel definitions which, when properly inserted into a PMDF configuration file, will provide electronic mail access to a FAX modem via the PMDF-FAX software. Important note: No changes are made to existing PMDF-FAX configuration information until all questions have been answered. This utility can be aborted at any prompt by entering a CTRL/Z. The files output by this utility can optionally be redirected to a different location so they will have no impact on existing PMDF-FAX files. This utility does NOT edit the PMDF configuration file itself; the necessary steps to do this are described in the checklist created by this utility. Do you wish to continue [Y]? YES Do you wish to have a detailed explanation printed before each question [N]? YES Part One: Configuring PMDF-FAX for sending facsimiles Most sites base the domain names for their systems on a common root. For example, all systems at the Claremont Colleges have domain names ending in ".EXAMPLE.COM". Enter the root of your domain names. Enter the root of your domain: example.com To send text e-mail to the FAX modem, users will use addresses of the general form: /FN=fax-number/@text-fax.domain-name A domain name appropriate for your configuration must be chosen for "text-fax.domain-name". This should be a name that does not conflict with any existing names you already use, as well as being one that users can remember. Also be sure that the name you choose is within a domain or subdomain that you have administrative authority over. Domain name for sending plain text e-mail to FAX [text-fax.example.com]: text-fax.example.com To send PostScript to the FAX modem, users will use addresses of the general form: /FN=fax-number/@ps-fax.domain-name A domain name appropriate for your configuration must be chosen for "ps-fax.domain-name". This should be a name that does not conflict with any existing names you already use, as well as being one that users can remember. Also be sure that the name you choose is within a domain or subdomain that you have administrative authority over. Domain name for sending PostScript to FAX [ps-fax.example.com]: ps-fax.example.com Supported FAX modems are: (1) DCE FaxBox/30 (2) Fujitsu dexNET 200 (3) Service Class 2 FAX modem (e.g., ZyXEL, MultiTech) Please specify which FAX modem you will be using at your site. The curently supported modems are (1) the DCE FaxBox/30, (2) the Fujitsu dexNET 200, (3) selected Service Class 2 modems. Respond to this question by entering 1 if you will be using the FaxBox/30, 2 if you will be using the dexNET 200, etc. Which FAX modem will you be using [2]? 3 Enter the name of the terminal line device that the FAX modem is attached to. Physical device names, logical names, LAT port names, and even multiple equivalence logical names (for FAX modem pools) are all acceptable. If a physical device name is used, be sure to include the colon (e.g., TTA2:). Device name of the FAX modem's terminal port [PMDF_FAX_MODEM]: LTA333: By default the FAX modem places phone calls using touch tone dialing. If the phone line to which you intend to connect your FAX modem does not support touch tone dialing or if you would prefer to use pulse dialing by default, then enter NO; otherwise enter YES. Can your FAX modem's phone line use touch-tone dialing [Y]? YES It is recommended that a queue other than MAIL$BATCH be used to to process FAX delivery jobs and that this service queue have a job limit which does not exceed the number of FAX modems accessible to the queue. Furthermore, this queue should only run on the machines from which the FAX modems are accessible. Service queue to use for FAX delivery jobs [FAX_BATCH]: FAX_BATCH The process that feeds data to the modem should run at elevated priority to insure that data reaches the modem in a timely fashion. Facsimile transmissions are synchronous, and if the modem runs out of data the connection will be broken. Note that the process feeding the modem is completely I/O bound; it does not use significant CPU resources. A priority of 6 is recommended. What priority should FAX delivery jobs run at [6]: 6 The FAX delivery channel will periodically try to transmit a FAX message until either a permanent error occurs (e.g., a human voice answers the phone) or the message is successfully delivered. An upper limit is placed on the number of transmission attempts which will be made. This upper limit can be any integer in the range 1 through 253, inclusive. If a message is not successfully delivered after making the specified number of attempts, it will be deleted and a descriptive e-mail message returned to the message's originator. Maximum number of delivery attempts per FAX (1-253) [15]? 15 By default, acknowledgement e-mail messages are sent to the originator of a FAX message only when the message is aborted (e.g., bad FAX telephone number) or sent successfully but with possible transmission errors. Ordinarily, no acknowledgement message is sent if the FAX is delivered successfully and without any transmission errors. If you answer YES to this prompt, then an e-mail message giving the final disposition of the FAX message (i.e., succesfully sent, successfully sent but with transmission errors, or aborted) of the FAX message will always be sent back to the originator of the message. Send acknowledgement messages when FAXes are delivered [Y]? YES As part of the CCITT T.30 handshake, the FAX modem will transmit a FAX Station Identification (FSI) string. This string should be the phone number for your FAX modem. The string should contain only the digits 0 - 9 and not exceed a length of 20 digits. This string will only appear on FAXes if the receiving FAX machine prints the FSI string on received FAX pages. Most FAX machines only print this information on activity logs or display it in a status display as the FAX is being received. What will the FAX modem phone number be (digits & spaces only): 508 555 1212 Across the top of each transmitted FAX page, the FAX modem will print a string which identifies the organization or group sending the FAX. This string should be brief and identify your organization (e.g., "Process"). At this point you can specify the default contents of this 40 character string. Organizational name to be printed atop each FAX page: Example, Inc. When addressing e-mail messages, user's can optionally specify with the /TTI= attribute-value pair an organizational name to print across the top of each transmitted FAX page. By answering YES to this prompt, you allow these user-supplied organizational names to override the name supplied in response to the previous question. May users override this organizational name with a name of their own [N]? NO Part Two: Configuring PMDF-FAX for receiving facsimiles If you want to also configure PMDF-FAX to receive FAXes, then answer YES to this prompt. You can use the same FAX modem for both sending and receiving operations; however, you will incur the, albeit small, cost of having a detached process present on your system. This detached process hibernates until an inbound FAX is detected at which point it awakens and receives the FAX and then hibernates until another inbound FAX is detected. Do you wish to configure PMDF-FAX to receive facsimiles [N]? YES Send received FAXes to: (1) a designated e-mail mail box, (2) a designated printer queue, or (3) a designated file directory. FAXes are received as bitmaps with no information indicating who they are for. The only way to determine who the intended recipient of a FAX is is for someone to examine the FAX. PMDF-FAX does not attempt to examine the FAX for you; PMDF-FAX will merely send the FAX to a designated location such as an e-mail mail box, a printer queue, or a file directory. Which of the above options do you want to select [1]? 1 Enter a valid user@host style e-mail address for the mail box to to send received FAXes. Specify a user@host style address to send received FAXes to: bob@example.com In which image format do you want to store received FAXes? (1) DDIF (CDA) (2) GIF 87a (3) GIF 89a (4) LN03 sixel format (5) PCL 3 (e.g., LaserJet, LaserJet Plus, LaserJet II) (6) PCL 4 (e.g., LaserJet II series except for the LaserJet II) (7) PCL 5 (e.g., LaserJet III, and 4 series) (8) PostScript (9) TIFF Received FAXes can be stored in one of the following image formats: DDIF (also known as CDA), GIF, LN03 sixel format, PCL (used by HP LaserJet printers, for instance), PostScript, or TIFF. Select a format compatible with the output destination you have chosen (e.g., DDIF for FAXes sent as e-mail to a DECwindows MAIL or A1MAIL user, PostScript, PCL, or LN03 for FAXes sent to a laser printer, etc.). Which image format do you want to use [1]? 1 Part Three: Process and write files Enter the name of the file to contain the PMDF configuration rewrite rules created by this procedure. This file should subsequently be included in your PMDF configuration file. Rewrite rules text file [PMDF_TABLE:FAX.RULES]: [RETURN] Enter the name of the file to write the channel block definitions for the PMDF-FAX channels to. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. FAX channel definitions text file [PMDF_TABLE:FAX.CHANS]: [RETURN] This procedure generates an options file that contains options for the PS_TO_G3 channel. This file is read by the PS_TO_G3 master program during initialization and sets up the characteristics of the channel prior to generating a FAX message. PS_TO_G3 channel options file [PMDF_TABLE:PS_TO_G3_OPTION.]: [RETURN] This procedure generates an options file that contains options for the G3_TO_FAX channel. This file is read by the G3_TO_FAX master program during initialization and sets up the characteristics of the FAX modem when sending FAXes. G3_TO_FAX channel options file [PMDF_TABLE:G3_TO_FAX_OPTION.]: [RETURN] This procedure generates an options file that contains options for the FAX_TO_DATA channel. This file is read by the FAX_TO_DATA slave program during initialization and sets up the characteristics of the FAX modem when receiving FAXes. FAX_TO_DATA channel options file [PMDF_TABLE:FAX_TO_DATA_OPTION.]: [RETURN] This procedure generates an options file that contains options for the DATA_TO_BITMAP channel. This file is read by the DATA_TO_BITMAP channel program and specifies how received FAXes are to be processed. DATA_TO_BITMAP channel options file [PMDF_TABLE:DATA_TO_BITMAP_OPTION.]: [RETURN] This procedure generates a checklist file that contains the list of actions you must perform in order to make the PMDF-FAX gateway operational. This procedure does *NOT* perform these operations itself; you must do them manually. PMDF-FAX checklist file name [PMDF_TABLE:FAX.CHECKLIST]: [RETURN] All configuration questions have been answered. Do you wish to generate the configuration files [Y]? YES Generating FAX.RULES file... FAX.RULES file is complete. Generating FAX.CHANS file... FAX.CHANS file is complete. Generating the PS_TO_G3 option file... PS_TO_G3 option file is complete. Generating the G3_TO_FAX option file... G3_TO_FAX option file is complete. Generating the FAX_TO_DATA options file... FAX_TO_DATA option file is complete. Generating the DATA_TO_BITMAP options file... DATA_TO_BITMAP option file is complete. Generating the setup checklist... Checklist file is complete. *********************************************************************** * * To complete your PMDF-FAX configuration, carry out the steps * detailed in the checklist file PMDF_TABLE:FAX.CHECKLIST * *********************************************************************** Enter Yes if you want to see the checklist now. You can still type the file out later if you say No. Do you want to see the checklist now [Y]? n $

Example 12-2 Example Checklist File for PMDF-FAX Configuration

$ TYPE PMDF_TABLE:fax.checklist Checklist for setting up your PMDF-FAX gateway. Written by SYSTEM, 1-NOV-2002 13:58 This file was created by the PMDF-FAX configuration generator V6.2. (1) Add the contents of the FAX.RULES file to the existing set of rewrite rules in your PMDF configuration file by adding the line <PMDF_TABLE:FAX.RULES to the rewrite rules section of your PMDF.CNF file; it should be be added before any general TCP/IP rewrite rules (e.g., .COM, .EDU, etc.). Note: You can find the lines ! ! Rewrite rules for PMDF-FAX ! !<PMDF_TABLE:FAX.RULES around the middle of your PMDF.CNF file. In this case, merely uncomment the line "!<PMDF_TABLE:FAX.RULES" and, if necessary, change the file name so that it reads ! ! Rewrite rules for PMDF-FAX ! <PMDF_TABLE:FAX.RULES (2) Add the contents of the FAX.CHANS file to the existing set of channels in your PMDF configuration file by adding the line <PMDF_TABLE:FAX.CHANS to the very end of your PMDF.CNF file; it should be preceded by a single blank line. Note: You can find the lines ! ! PMDF-FAX channels ! !<PMDF_TABLE:FAX.CHANS towards the end of your PMDF.CNF file. In this case, merely uncomment the "!<PMDF_TABLE:FAX.CHANS" line and, if necessary, change the file name so that it reads ! ! PMDF-FAX channels ! <PMDF_TABLE:FAX.CHANS (3) If you are running with a compiled PMDF configuration, be sure to recompile your configuration. (4) If you are running a domain name system (DNS) nameserver, you will need to insert MX or A records for the domain names text-fax.example.com and ps-fax.example.com into the database. If you are using host tables, make sure to add host aliases for these domain names. (5) Check to make sure that the system SYSGEN parameter MAXBUF is set to at least 2560 bytes on all systems which will run PMDF-FAX. (On node NAPLES, MAXBUF is set to 10240 bytes.) PMDF-FAX uses $QIO buffers of length 2048 bytes when sending or receiving FAXes. Consequently, MAXBUF must be set to a number which exceeds 2048 bytes. (6) Initialize and start the queue FAX_BATCH with the commands: $ INITIALIZE/QUEUE/BATCH/START/JOB_LIMIT=n FAX_BATCH with n the number of FAX modems accessible to the queue. For most installations, n = 1. Use the /ON qualifier to control which nodes the queue will run on. Be sure to also add this command to your system startup procedure. (7) If you will be receiving FAXes with PMDF-FAX, then execute the command $ @PMDF_COM:START_FAX_RECEIVE.COM once for each detached FAX receive process you want to start. (Each process will allocate a FAX modem.) Also add this command to your system startup procedure. This command should be executed after SYS$STARTUP:PMDF_STARTUP.COM is executed but before you start your PMDF service queues (e.g., MAIL$BATCH and FAX_BATCH). The terminal line, LTA333:, must be set /PERMANENT/NOTYPE_AHEAD/ALTYPEAHD/EIGHTBIT This should be done regardless of whether a regular terminal line or a terminal server port is used. (9) If you would like to have status reports sent to users, adjust the setting of the ACKNOWLEDGEMENTS option in the options file G3_TO_FAX_OPTION.; -- see the G3_TO_FAX channel documentation in the PMDF-FAX chapter of the PMDF System Manager's Guide. The setting ACKNOWLEDGEMENTS=0 only generates an acknowledgement report when the FAX message is successfully transmitted and does not generate intermediate reports should temporary problems (e.g., remote FAX device busy, FAX modem needs to be reset, etc.) be encountered while trying to send the FAX. (10) You might want to define the following system wide logical: $ DEFINE/SYSTEM PMDF_TEXT_FAX_DOMAIN "text-fax.example.com" This logical is used by the pop-up FAX addressing form as the default address to send FAX e-mail to. Consult the PMDF-FAX chapter of the PMDF System Manager's Guide for further details. Do not define this logical in SYS$STARTUP:PMDF_STARTUP.COM as its definition will then be lost whenever you upgrade PMDF. That's all!