Configuring Store and Forward Fax

This chapter includes the following sections:

• Send and receive faxes to and from Group 3 fax devices

• Receive faxes that will be delivered as an e-mail attachment

• Create and send a standard e-mail message that will be delivered as a fax to a standard Group 3 fax device

Store and Forward Fax functionality is facilitated through Simple Mail Transfer Protocol (SMTP). Additional functionality is provided in this product to provide confirmed delivery using existing SMTP mechanisms, such as Extended Simple Mail Transfer Protocol (ESMTP).

With Store and Forward Fax, the Cisco AS5300, acting as the on-ramp gateway, receives faxes from end users and converts them into TIFF files. It then creates a standard Multipurpose Internet Mail Extensions (MIME) e-mail message and attaches the TIFF file to it. The on-ramp gateway then forwards this "fax-mail" to the messaging infrastructure of a designated SMTP server, where the fax-mail message is stored. The messaging infrastructure performs message routing, message storage, and transport, and can be either a standard Internet Message Transfer Agent (MTA)---for example, UNIX sendmail---or custom store-and forward fax software. The responsibility of delivering the fax-mail message falls to SMTP and the mail server.

Fax-mail stored on the SMTP server can be delivered either as an e-mail message with attachment when the recipient downloads messages or as a standard fax to a Group 3 fax device. In the latter case, the SMTP server mail delivery infrastructure delivers the fax-mail to the Cisco AS5300 acting as an off-ramp gateway. The off-ramp router converts the attached TIFF file back into standard fax format and then sends the information to a standard Group 3 fax device. The off-ramp gateway is also responsible for generating delivery status notifications (DSNs) and message disposition notifications (MDNs).

Note We strongly recommend that you configure your Cisco AS5300 acting as an off-ramp gateway to only accept incoming SMTP connections from trusted mailers. Configure packet filters to allow only certain "trusted" IP addresses to send faxes to the Store and Forward Fax off-ramp gateway.

Store and Forward Fax is used in conjunction with the software feature VoIP for the Cisco AS5300; to use Store and Forward Fax, you must have the software component of VoIP for the Cisco AS5300 installed on your access server. In addition, you need to have a modem card installed; Store and Forward Fax functionality depends on the type of modem card installed.

Note Because the AS5300 uses modems to send data in Store and Forward Fax, you need not have a voice network module (VNM) for VoIP installed in your Cisco AS5300. You must have the software component of VoIP for the Cisco AS5300 installed to use Store and Forward Fax.

• text/plain

• text/enriched

• image/tiff ("Profile S" described in RFC 2301)

• 7 bit

• 8 bit

• Base 64

• Quotable-printable

These content transfer encodings can be wrapped in any multipart/* content type. When Store and Forward Fax receives messages with multiple sections, it processes the first part of the multipart message and records a count of what is and is not successfully sent. Store and Forward Fax then discards the rest of the message. For example, if a multipart/alternative message has a text/plain part and a text/html part (and the text/plain part is first), Store and Forward Fax processes only the text/plain part.

Note The TIFF file format must conform to RFC 2301 (File Format for Internet Fax by L. McIntyre, S. Zilles, R. Buckley, D.Venable, G. Parsons, and J. Rafferty; March 1998). Store and Forward Fax does not support uuencoded text, JPEG or JBIG files, or multiraster content.

Caution The Cisco AS5300 only recognizes the listed file attachment types for Store and Forward Fax activities. If the Cisco AS5300 receives a file format different from one of the defined acceptable formats, it discards the data.

Store and Forward Fax on-ramp has been designed to work in one of two ways: either using a feature called direct inward dial (DID) or using a redialer, which is an interface hardware device that interconnects between a fax device and a Public Switched Telephone Network (PSTN) network. If you choose not to enable DID, you must configure and enable a redialer on the originating fax machine for Store and Forward Fax to be operational.

• Edit the SMTP server alias file to include an alias for fax transmissions---meaning an e-mail address that has "fax=" prefix included in it. For example, suppose you create the following alias: fax=5551212; user@hostname.com. In this example, if a fax is sent to the telephone number 5551212, the on-ramp gateway will automatically forward it to the mailbox for user@hostname.com.

If you create aliases to forward faxes to particular e-mail addresses, you need to configure the on-ramp multimedia over IP (MMoIP) dial peer session-target command as follows:

session target mailto: $d$@hostname.com. 

The $d$ keyword specifies that the destination fax machine telephone number is inserted in the envelope to: field of the fax-mail that gets sent to the SMTP server.

• Modify parameters involving SMTP delivery requirements.

Fax transmission has delivery requirements that are different from e-mail; for example, in certain countries, it is illegal to try to send a fax more than three times in a row if transmission fails. In addition, the time between retransmission attempts can be extremely short. SMTP mail delivery requirements are not governed by such strict regulations; in general, if an e-mail message cannot be delivered, the SMTP server will continue trying to deliver the message every 30 minutes for up to 5 days. To avoid any complications arising from the difference between the SMTP e-mail and fax delivery requirements, modify the following parameters:

• Delivery to one recipient

• Message priority

• Connection Cache Size

• Minimum Queue Age

Caution  It is extremely important to modify SMTP delivery requirement parameters. Failure to do so can result in a monopoly of bandwidth and fax resources.

Use a redialer in the following circumstances:

• Provisioning a DID service is not possible

• You need user information, such as a PIN from the redialer

• T1-CAS signaling is in use

For Store and Forward Fax to work with a redialer, you must perform the following tasks:

• Program the redialer to dial the Cisco AS5300 acting as the on-ramp gateway and capture the dialed digits.

A redialer is an interface hardware device that interconnects between a fax device and a PSTN network that maps the numbers that a user dials to reach a specific destination to a different number, and forwards the dialed digits to that new number, transparent to the user. The user enters the complete telephone number into the fax device, and the attached redialer captures and stores those dialed digits. The redialer then dials the on-ramp Cisco AS5300, which provides a secondary dial tone.

When the no direct-inward-dial command is configured for the on-ramp POTS dial peer, the on-ramp gateway will answer the call and provide secondary dial tone. The redialer should be programmed to wait 2 seconds, then send the PIN and destination digits to the on-ramp gateway.

• Configure an MMoIP dial peer to match the forwarded dialed digits from the redialer.

When the redialer forwards the original dialed digits to the on-ramp Cisco AS5300, the on-ramp gateway will collect the digits, separate the PIN from the destination, and attempt to match an on-ramp MMoIP dial peer with the destination. If the debug fax receive command is enabled, you can see the digits as they are received by the on-ramp gateway. If a dial peer is matched, the fax proceeds. If a dial peer is not matched, the fax fails.

Store and Forward Fax allows 19 digits (maximum) for the PIN and 32 digits (maximum) for the destination number. The PIN and destination number must be separated by a #, for example:

0000000012345678#01127116650945

The fax protocol starts after 52 digits are detected or the interdigit timeout exceeds 5 seconds.

The following redialers are supported:

• Mitel

• Telecom Research

You use dial peers to apply specific attributes to call legs, such as identifying call origin and destination. In Store and Forward Fax, you also use dial peers to configure MDNs, DSNs, fax image resolution, and encoding type.

Two different kinds of dial peers are used in Store and Forward Fax as follows:

• POTS dial peers---POTS dial peers define the line characteristics generally associated with a typical or traditional telephony network connection. In Store and Forward Fax, there are two different implementations of POTS dial peers: one that defines the line characteristics of the connection between the sending fax machine and the Cisco AS5300 acting as the on-ramp gateway, and another defining the line characteristics between the receiving fax machine and the Cisco AS5300 acting as the off-ramp gateway. For more information about on-ramp POTS dial peers---for example, how to configure them and how the on-ramp router uses them---see the "Configuring On-Ramp POTS Dial Peers" section later in this chapter. For more information about off-ramp POTS dial peers, see the "Configuring Off-Ramp POTS Dial Peers" section later in this chapter.

• MMoIP dial peers---MMoIP dial peers describe the line characteristics generally associated with a packet network connection; for example, in the case of Store and Forward Fax, this is the IP network connection between the on-ramp (and optionally, the off-ramp) gateway and the SMTP server.

For more information about on-ramp MMoIP dial peers---for example, how to configure them and how the on-ramp router uses them---see the "Configure On-Ramp MMoIP Dial Peers" section later in this chapter. For more information about how and when to configure optional off-ramp MMoIP dial peers, refer to the "Configure Off-Ramp MMoIP Dial Peers" section later in this chapter. For more general background or supplementary information about voice-related dial peers, refer to the "Voice over IP" chapter.

For example, suppose there is a fax device whose E.164 called number is 1(408)555-1234 and that this fax device can be reached within the company by dialing its extension number, 51234. If you configure a destination pattern of "1408555...." (the periods represent wild cards) for the associated off-ramp POTS dial peer, the off-ramp gateway will strip out the digits "1408555" when it receives a call for 1(408)555-1234. For the off-ramp gateway to forward the call to the appropriate destination, the digit "5" needs to be prepended to the remaining digits. In this case, you would configure a prefix of 5.

Suppose there is a fax device whose E.164 called number is 1(408)555-1234 and to reach this device you need to dial "9." In this case, you might configure "1408......." as the destination pattern, and "9" as the prefix. In this example, the off-ramp router will strip the digits "1408" from the called number and append the digit "9" to the front of the remaining numbers, so that the actual number dialed is "9,5551234." The comma in this example means that the router will pause for one second between dialing the "9" and the "5551234" to allow for a secondary dial tone.

For more information about the destination-pattern and prefix commands, refer to the Cisco IOS Multiservice Applications Command Reference publication.

You implement number expansion by using the num-exp command. The extension-number argument defines the number pattern to be expanded. The extension-string argument defines the number to be prepended to the defined extension number. You can verify the number expansion information by using the show num-exp command to show that you have mapped the telephone numbers correctly. After you have configured dial peers and assigned destination patterns to them, you can verify number expansion information by using the show dialplan number command to see how a telephone number maps to a dial peer.

Using a simple telephony-based example, suppose John works in a company where you dial the last four digits of the full E.164 telephone number to reach his extension. The E.164 telephone number is 555-2123; his extension number is 2123. Suppose every employee on his floor has a telephone number that begins with the same first four digits: 555-2. You could define each dial peer's destination pattern using each peer's extension number, and then use number expansion to prepend the first four digits on to the extension. In John's case, the Cisco AS5300 could be configured as follows:

configure terminal
num-exp 2... 5552...
dial peer voice 1 pots
  destination pattern 2123

Number expansion can also be used to replace a dialed number with another number, as in the case of call forwarding. Suppose John, for some reason, needs to have all of his telephone calls forwarded to another number, 555-6611. In this case, you would configure the Cisco AS5300 as follows:

configure terminal
num-exp 2123 5556611
dial peer voice 1 pots
  destination pattern 2123

In this example, every time the device receives a call for extension 2123, the dialed digits will be replaced with 555-6611 and forwarded to that telephone.

The way that you use number expansion with Store and Forward Fax depends on how you have implemented your dial plan. In general, you can use number expansion if you have used the destination-pattern command to define a destination telephone number for a dial peer. For example, off-ramp POTS dial peers define the telephone number of the destination fax device using the destination-pattern command. In this case, if you need to, you could use number expansion.

To configure the on-ramp gateway, perform the tasks described in the following sections:

	Command	Purpose
Step 1	Router#configure terminal	Enters global configuration mode.
Step2	Router(config)#fax receive called-subscriber {$d$|string}	Defines the number that is displayed in the LCD of the sending fax machine. This parameter defines the called subscriber identification (CSI).

• Subject

• Destination

• Return path

• Postmaster

• Any additional identifying e-mail header information

• Address to which any disposition notices are sent

Of these configuration steps, you must define the originator of the e-mail fax, the destination mail server, the subject of the message, and the postmaster, which is the default mail station for undeliverable e-mail messages. The remaining configuration steps are optional.

NoteYou use the mta send mail-from username and mta send mail-from hostname commands to configure the From: user name in the e-mail message. The To: address of the fax-mail is derived from the session target command configured for the MMoIP dial peer for the on-ramp gateway.

To configure the sending MTA, use the following commands in global configuration mode:

	Command	Purpose
Step1	Router(config)#mta send mail-from hostname string	Specifies the originator (host name portion) of the e-mail fax message. This information appears in the RFC 822 From: field and the RFC 821 MAIL FROM field of the e-mail fax message. This information is also used for generating DSNs. NoteWhen you configure the mta send mail-from hostname command, the host name configured is used with the mta send mail-from username command to form a complete e-mail address, like faxuser@onramp-gateway.com.
Step2	Router(config)#mta send mail-from {username string | username $s$}	Specifies the originator (username portion) of the e-mail fax message. This information appears in the RFC 822 From: field and the RFC 821 MAIL FROM field of the e-mail fax message. This information is also used for generating DSNs. When you configure the mta send mail-from username command, the username configured is used with the mta send mail-from hostname command to form a complete e-mail address, like faxuser@onramp-gateway.com.
Step3	Router(config)#mta send server {host-name | IP-address}	Specifies the destination server. NoteDNS MX records are not used to determine the IP address of the host specified with the mta send server command.
Step4	Router(config)#mta send subject string	Defines the text that appears in the Subject field of the e-mail fax message.
Step5	Router(config)#mta send postmaster e-mail-address	Defines address to be used as the mta send mail-from address if the evaluated string is blank. An address such as fax-administrator@example.com is recommended (where company.com is replaced with your domain name, and fax-administrator is aliased to the person responsible for the operation of the Cisco AS5300 fax functions). At some sites this may be the same person as the e-mail postmaster, but at most sites this is likely to be a different person.
Step6	Router(config)#mta send origin-prefix string	(Optional) Defines additional identifying information to be prepended to the e-mail header.
Step7	Router(config)#mta send return-receipt-to {hostname string username string}	(Optional) Specifies the address where MDNs are sent, if you request MDN.

On-Ramp Gateway POTS Dial Peer/Call Discrimination Process

An understanding of how the on-ramp gateway uses POTS dial peers in the course of call discrimination is helpful before you configure on-ramp POTS dial peers. First, though, some functional definitions should be created. As mentioned, Store and Forward Fax uses either DID or a redialer to process a fax call. In both of these cases, a different telephone number is used. For the purposes of the following discussion, the term destinationDN refers to the telephone number of the fax machine where the user wants a fax to be sent and accessDN refers to the telephone number dialed by a redialer to access an on-ramp gateway.

The process of call discrimination begins when the on-ramp router receives a call. It immediately identifies whether the call is being delivered via a PRI interface or a T1-CAS interface. If the on-ramp gateway determines that the call is coming in over a T1-CAS interface, it checks the service type field of the CAS group configuration. If the service type of the CAS group is fax, it flags the call as a Store and Forward Fax call and forwards it to the MMoIP dial peer to be processed as a fax call. If it determines that the call is coming in over a PRI interface, then the on-ramp gateway begins to look at several POTS dial peer data fields to determine what kind of call it has received.

The on-ramp gateway looks at the incoming called number field of each POTS dial peer listed in the dial peer lookup table. It compares the number configured as the incoming called number to the number received and selects the first POTS dial peer where the data matches. If the on-ramp router does not find a match, it assumes that this is a data call and processes the call accordingly.

If the on-ramp router does find a match, it will then look at the service type field of the POTS dial peer to determine whether this is a voice or fax call. If this call has been flagged as a voice call, the on-ramp gateway will process it appropriately as a voice call. If the call has been flagged as a fax call, the on-ramp gateway checks to see whether DID has been enabled. If DID has been enabled, it concludes that the telephone number it has received is the destinationDN and forwards the call to be matched with the appropriate on-ramp MMoIP dial peer.

If DID has not been enabled, the on-ramp gateway assumes that the telephone number it received is the accessDN. In this case, the on-ramp router provides a secondary dial tone and collects another telephone number from the redialer at the other end of the connection that it will use as the destinationDN. After it has received this number from the redialer, the on-ramp gateway forwards the call to be matched to the appropriate on-ramp MMoIP dial peer.

Redialers Versus DID for POTS Peers

By default, DID is disabled, which means that the on-ramp gateway assumes that the fax call it receives is being placed using a redialer. In this situation, when a call arrives on the on-ramp gateway, it presents a dial tone and collects digits until it can identify the destination, as described. After the destination has been identified, it forwards the call through to the next call leg (in this case, the MMoIP dial peer) to the destination.

If DID is enabled, the on-ramp gateway uses the called number (DNIS) to find a dial peer for the outgoing call leg. DID enables the gateway to match the incoming called number with a dial peer and then directly place the outbound call. With DID, the server does not present a dial tone to the fax machine and does not collect digits; it forwards the call directly to the configured destination.

To configure on-ramp gateway POTS dial peers, use the following commands beginning in global configuration mode:

	Command	Purpose
Step1	Router(config)#dial-peer voice number pots	Defines the POTS dial peer tag number and enters dial-peer configuration mode.
Step2	Router(config-dial-)#information-type fax	Identifies calls associated with this dial peer as being fax transmissions, as opposed to being voice calls.
Step3	Router(config-dial-)#direct-inward-dial	(Optional) Specifies DID. If you are not using a redialer, you must enable DID to use Store and Forward Fax.
Step4	Router(config-dial-)#incoming called-number string	Defines the telephone number associated with the POTS dial peer---in Store and Forward Fax, if DID is enabled, the incoming called number (DNIS number) is used to match the destination pattern of outgoing MMoIP dial peers.
Step5	Router(config-dial-)#max-conn number	(Optional) Defines the maximum number of on-ramp connections used simultaneously on this Cisco AS5300 to send fax-mail.

On-ramp MMoIP dial peers are used to define the destination fax telephone number, to specify a destination e-mail address (which in this case identifies the SMTP server), to define the image encoding and resolution specifics for the associated fax-mail TIFF files, and to request either DSNs, MDNs, or both. If you enabled DID and specified an incoming called number for the on-ramp POTS dial peer, the destination pattern of the on-ramp MMoIP dial peer should be the same as the configured incoming called number. If you did not enable DID, then you need to configure and enable a redialer to use Store and Forward Fax. If you use a redialer, you need to configure the destination pattern to match the forwarded dialed digits from the redialer.

On-Ramp Gateway MMoIP Dial Peer/Call Discrimination Process

An understanding of how the on-ramp gateway uses MMoIP dial peers is helpful before configuring on-ramp MMoIP dial peers. As with on-ramp POTS dial peers, for the purposes of the following discussion, the term destinationDN refers to the telephone number of the fax machine where the user wants a fax to be sent, and accessDN refers to the telephone number dialed by a redialer to access an on-ramp gateway.

The function of the on-ramp call discrimination process using MMoIP dial peers is to determine the destination of the fax-mail, which in this case means the off-ramp gateway over which the fax-mail is sent to the destination fax machine.

The on-ramp gateway looks at the destination pattern field of each MMoIP dial peer listed in the dial peer lookup table. It compares the number configured as the destination pattern to the number received and selects the first MMoIP dial peer where the data matches. The on-ramp gateway then looks at the session target field for the selected MMoIP dial peer to identify the destination of the fax-mail message---this could be a specific off-ramp gateway for a Store and Forward fax or, if the fax is being delivered as an e-mail message, an e-mail address for a specific mail server.

Image Encoding and Image Resolution

Depending on the capacity of the fax machines in your network, you might want to use a different image encoding (compression) scheme for the fax TIFF image Store and Forward Fax creates. As a default, image encoding in Store and Forward Fax is set to passthrough, which means that the image is forwarded exactly as it is received. If you want to specify a specific encoding (compression) scheme for the fax TIFF image, use the image encoding dial-peer configuration command.

DSN

• Delay---Indicates that, for some reason, the message was delayed in being delivered to the recipient.

• Success---Indicates that the message was successfully delivered to the recipient mailbox.

• Failure---Indicates that, for some reason, the SMTP server was unable to deliver the message to the recipient.

Because these delivery states are not mutually exclusive, you can configure Store and Forward Fax to generate these messages for all or any combination of these events.

You enable DSN requests as part of the on-ramp MMoIP dial peer configuration. For complete instructions on how to configure DSNs using Store and Forward Fax, refer to the "Configuring Delivery Status Notification" section later in this chapter.

MDN

To configure on-ramp gateway MMoIP dial peers, use the following commands beginning in global configuration mode:

	Command	Purpose
Step1	Router(config)#dial-peer voice number mmoip	Defines the MMoIP dial peer tag number and enters dial-peer configuration mode.
Step2	Router(config-dial-)#information-type fax	Identifies calls associated with this dial peer as being fax transmissions, as opposed to strictly being voice calls.
Step3	Router(config-dial-)#destination-pattern [+]string	Identifies the destination fax telephone number. If DNIS has been enabled, this number should be the same as the configured incoming called number. If DNIS is not enabled, this should be the number from the redialer DNIS.
Step4	Router(config-dial-)#session target {mailto:{name | $d$}@domain-name | ipv4:destination-address | dns:[$s$. | $d$. | $u$. | $e$.] host-name| loopback:rtp |loopback:compressed | loopback:uncompressed}	Defines the destination e-mail address for the fax-mail, meaning the e-mail address identifying the SMTP server.
Step5	Router(config-dial-)#session protocol smtp	Identifies the session protocol being used between the on-ramp gateway and the remote mail server as SMTP.
Step6	Router(config-dial-)#image encoding {mh | mr | mmr | passthrough}	Selects a specific encoding method for the fax-mail messages forwarded via this dial peer.
Step7	Router(config-dial-)#image resolution {fine | standard | super-fine | passthrough}	Selects a specific resolution for the TIFF images attached to the fax-mail message forwarded vis this dial peer.
Step8	Router(config-dial-)#max-conn number	(Optional) Defines the maximum number of connections used simultaneously on this CiscoAS5300 to send fax-mail.
Step9	Router(config-dial-)#dsn {delay | failure | success}	(Optional) Requests that a delivery status notification be generated by the last hop mailer if the delivery was successful. This DSN is sent to the address specified by the mta send mail-from command. Three types of DSNs can be requested: delay, failure, and success. NoteDSN must be supported by the remote mail server.
Step10	Router(config-dial-)#mdn	(Optional) Requests that a message disposition notification be generated by the mail user agent when the message is processed (typically opened or read). The MDN is generated by the receiving mail user agent and sent to the address defined by the mta send return-receipt-to command. NoteReturn receipt must be supported/initiated by the receiving e-mail client.

• Fax and data

• Data only

As a default, Store and Forward Fax receives faxes on modems that are in the on-ramp gateway default modem pool---meaning that these modems are available for both fax and data calls. The on-ramp gateway determines the call type by using the DNIS. The on-ramp gateway compares the DNIS to the configured value for the incoming called-number POTS dial-peer configuration command; if the DNIS matches the incoming called number, then it treats the call as a fax transmission. If it does not find a match in its dial peer lookup table, it treats the call as a data call.

You can specify which incoming fax calls will not be presented to the default modem pool by defining a named modem pool. This is particularly useful if you have both MICA and Microcom faxes; it allows you to divert fax traffic from MICA modems, which at this time do not support fax transmission.

To configure on-ramp modem pooling, use the following commands beginning in privileged EXEC mode:

	Command	Purpose
Step1	Router#configure terminal	Enters global configuration mode.
Step2	Router(config)#modem-pool name	Creates a modem pool.
Step3	Router(config)#pool-range number-number	Assigns a range of modems to the specified modem pool.

You need to enable Cisco routers and access servers to support the Nagle congestion control algorithm. To optimize Store and Forward Fax performance and to avoid packet congestion, enable the Nagle congestion control algorithm by using the service nagle global configuration command.

To enable the Nagle Congestion Algorithm, use the following command in global configuration mode:

Command	Purpose
Router(config)#service nagle	(Optional) Enables the Nagle congestion control algorithm to optimize Store and Forward Fax performance.

NoteThere may be unexpected side effects with other services that run over TCP sockets on this same Cisco AS5300 if you enable the Nagle congestion algorithm when using Store and Forward Fax. However, we are unaware of any side effects at this time.

The off-ramp gateway performs the following activities:

• Converts a fax-mail TIFF file (or plain text file) back into a standard format and delivers it to the recipient, which in this case is a Group 3 fax device. Store and Forward Fax does not alter the TIFF or plain text file in any way from its original format when converting it back into a standard fax format. The off-ramp gateway uses the receiving MTA and dial peers to perform this conversion.

• Delivers an e-mail message as a standard fax transmission, which is received and processed by a Group 3 fax device. The source of this transmission is an e-mail message. The Cisco AS5300 generates information to be appended to the top of each "faxed" page (meaning, text-to-fax pages) and creates a fax cover sheet. The off-ramp gateway uses the receiving MTA, dial peers, and commands specific to formatting the appended information and generating a fax cover sheet to deliver e-mail messages as fax transmissions.

NoteOff-ramp faxing activities are not mutually exclusive. You can create an e-mail to be sent as a fax and attach a TIFF file to it; when the Cisco AS5300 converts the e-mail to fax format, it also converts the attached TIFF file to standard Group 3 fax format.

The off-ramp gateway usually uses only POTS dial peers to define the line characteristics between the off-ramp gateway forwarding the converted e-mail message and the fax device; as an option, you can configure MMoIP dial peers, but MMoIP dial peers have limited functionality in off-ramp faxing activities. In general, off-ramp MMoIP dial peers merely define fax compression schemes and resolution and are useful only if you want to alter those parameters for the fax-mails being received.

The off-ramp gateway uses receiving MTAs to define the parameters associated with the AS5300 SMTP server, such as its SMTP host alias(es), which can be different than its normal DNS host name(s) or internal Cisco IOS host name. Off-ramp POTS dial peers basically define the telephone number of the destination fax device. Because a destination pattern is defined for an outbound POTS peer, you can use number expansion.

To configure the off-ramp gateway, perform the tasks in the following sections:

To configure the transmitting subscriber number, use the following commands beginning in privileged EXEC mode:

	Command	Purpose
Step1	Router#configure terminal	Enters global configuration mode.
Step2	Router(config)#fax send transmitting-subscriber {$d$ | string}	Defines the number that appears in the LCD of the receiving fax device. This parameter defines the transmitting subscriber identification (TSI).

To configure the fax transmission speed, use the following command in global configuration mode:

Command	Purpose
Router (config)#fax send max-speed {12000 | 14400 | 2400 | 4800 | 7200 | 7600}	Specifies the maximum speed at which an off-ramp fax is sent.

	Command	Purpose
Step1	Router(config)#mta receive aliases string	Defines a host name to be used as an alias for the off-ramp Cisco AS5300 device. You can define up to ten different aliases. NoteThe Cisco AS5300 SMTP server will only accept incoming mail if the destination host name of the incoming mail matches one of the aliases as configured by the mta receive aliases command. NoteThis command does not automatically include reception for a domain IP address---it must be explicitly added. If you add an IP address, you must enclose the address in brackets as follows: [xxx.xxx.xxx.xxx].
Step2	Router(config)#mta receive generate-mdn	(Optional) Configures the Cisco AS5300 to actually generate an MDN message when requested to do so. Some sites may want to enable or disable this feature depending on the types of mailers in use.
Step3	Router(config)#mta receive maximum-recipients number	Defines the number of simultaneous SMTP recipients handled by this device. This is intended to limit the number of resources (modems) allocated for fax transmissions.

Only two resolutions are available for this release: standard and fine. If you select any other image resolution command options (such as passthrough or super-fine), the fax will be sent using the fine resolution. Encoding type defines the type of compression scheme the off-ramp gateway uses for the TIFF image. There are four available compression options: Modified Huffman, Modified Read, Modified Modified Read, and passthrough.

Off-Ramp Gateway MMoIP Dial Peer/Call Discrimination Process

Once again, understanding how the off-ramp gateway uses MMoIP dial peers in the course of call discrimination is helpful before you configure off-ramp MMoIP dial peers. For the purposes of the following discussion, the term destinationDN refers to the telephone number of the fax machine where the user wants a fax to be sent, and accessDN refers to the telephone number dialed by a redialer to access an on-ramp gateway. For the on-ramp gateway to forward the fax-mail to the appropriate SMTP server, it converts the destinationDN into an e-mail address. The left side of this address is the destinationDN; the right side of this e-mail address defines the domain.

When the off-ramp router receives the fax-mail message, it looks at the destinationDN portion of the e-mail address and tries to match that value with the incoming called number field for each of the defined off-ramp MMoIP dial peers in its lookup table. If the off-ramp gateway finds an appropriate match, it uses the specified resolution and encoding values for the fax-mail message. If it cannot find a match, or if no resolution or encoding information has been defined for a matched off-ramp MMoIP dial peer, it applies fine resolution and non (passthrough) encoding for those parameters.

To configure off-ramp gateway MMoIP dial peers, use the following commands beginning in global configuration mode:

	Command	Purpose
Step1	Router(config)#dial-peer voice number mmoip	Defines the MMoIP dial peer tag number and enters dial-peer configuration mode
Step2	Router(config-dial-)#information-type fax	Identifies calls associated with this dial peer as being fax transmissions, as opposed to strictly being voice calls.
Step3	Router(config-dial-)#incoming called-number string	Identifies the destination fax telephone number.
Step4	Router(config-dial-)#image resolution {fine | standard | super-fine | passthrough}	Specifies the fax image resolution for TIFF files associated with this particular MMoIP dial peer. NoteOnly standard and fine fax resolutions are supported for Cisco IOS Release 12.1.
Step5	Router(config-dial-)#image encoding {mh | mr | mmr | passthrough}	Specifies the type of encoding to be used for TIFF files associated with this MMoIP dial peer.

Off-Ramp Gateway POTS Dial Peer/Call Discrimination Process

Once again, understanding how the off-ramp gateway uses POTS dial peers in the course of call discrimination is helpful before you configure off-ramp POTS dial peers. For the purposes of the following discussion, the term destinationDN refers to the telephone number of the fax machine where the user wants a fax to be sent, and accessDN refers to the telephone number dialed by a redialer to access an on-ramp gateway. For the on-ramp gateway to forward the fax-mail to the appropriate SMTP server, it converts the destinationDN into an e-mail address. The left side of this address is the destinationDN; the right side of this e-mail address defines the domain.

The off-ramp gateway looks at the destination-pattern field of each POTS dial peer listed in the dial peer lookup table. It compares the number configured as the destination pattern to the destination DN portion of the fax-mail address and selects the first POTS dial peer where the data matches.

After the off-ramp gateway identifies the appropriate POTS dial peer, it then matches call type information. If the call type is identified as fax, it forwards the fax-mail message to off-ramp services. If the off-ramp router does not find a match, the recipient identified by this address will not be accepted by the off-ramp router.

NoteTo generate E.164 e-mail addresses compliant with RFC 2304, use the following address format: fax=+$d$@your.hostname.com. If the off-ramp gateway receives this type of e-mail address, it strips the + and matches an off-ramp POTS dial peer on the remaining digits.The number contained in "$d$" must be a fully qualified E.164 telephone number (that is, it must include the country code) and it must not include an access code (such as "9" to get an outside line).

To configure off-ramp gateway POTS dial peers, use the following commands beginning in global configuration mode:

	Command	Purpose
Step1	Router(config)#dial-peer voice number pots	Defines the POTS dial peer tag number and enter dial-peer configuration mode.
Step2	Router(config-dial-)#information-type fax	Identifies calls associated with this dial peer as being fax transmissions, as opposed to strictly being voice calls.
Step3	Router(config-dial-)#destination-pattern [+]stringT	Identifies the destination fax telephone number.
Step4	Router(config-dial-)#prefix number	(Optional) Specifies the prefix of the dialed digits associated with this dial peer. If you configure a prefix, when an outgoing call is initiated, the prefix string value is sent to the modem first, before the telephone number configured for this dial peer.

NoteBecause the off-ramp gateway does not alter fax TIFF attachments, you cannot configure faxed header information for faxes being converted from TIFF files to standard fax transmissions.

To configure faxed header information, use the following commands in global configuration mode:

	Command	Purpose
Step1	Router(config)#fax send center-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}	Specifies the header information to be displayed in the center position. The wildcards used in this command are used to insert the following information: $a$---date $d$---destination address $s$---sender address $p$---page count $t$---transmission time You use the string argument in this command to insert personalized text string.
Step2	Router(config)#fax send right-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}	Specifies the header information to be displayed on the right. The wildcards used in this command are used to insert the following information: $a$---date $d$---destination address $s$---sender address $p$---page count $t$---transmission time You use the string argument in this command to insert personalized text string.
Step3	Router(config)#fax send left-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}	Specifies the header information to be displayed on the left. The wildcards used in this command are used to insert the following information: $a$---date $d$---destination address $s$---sender address $p$---page count $t$---transmission time You use the string variable in this command to insert personalized text string.

NoteBecause the off-ramp gateway does not alter fax TIFF attachments, you cannot configure cover pages for faxes being converted from TIFF files to standard fax transmissions.

To configure fax cover page information, use the following commands in global configuration mode:

	Command	Purpose
Step1	Router(config)#fax send coverpage enable	Enables the off-ramp gateway to send a cover sheet with faxes that originate from e-mail messages.
Step2	Router(config)#fax send coverpage comment string	(Optional) Adds personalized text in the title field of the fax cover sheet.
Step3	Router(config)#fax send coverpage show-detail	(Optional) Prints all of the e-mail header information as part of the fax cover sheet text.

You can also use the destination address of an e-mail message to control the cover page generation on a per-recipient basis. You use the fax send coverpage e-mail-controllable command to configure the router to defer to the cover page setting in the e-mail header.

In essence, the off-ramp router defers to the setting configured in the e-mail address itself. For example, if the address has a parameter set to cover=no, this parameter will override the setting for the fax send coverpage enable command and the off-ramp gateway will not generate and send a fax cover page. If the address has a parameter set to cover=yes, the off-ramp gateway will defer to the setting configured in the e-mail address and generate and send a fax cover page.

To configure the router to defer to the cover page setting in the e-mail header, use the following commands in global configuration mode:

	Command	Purpose
Step1	Router(config)#fax send coverpage enable	Enables the off-ramp gateway to send a cover page with faxes that originate from e-mail messages.
Step2	Router(config)#fax send coverpage e-mail controllable	Configures the router to defer to the cover page setting in the e-mail header. For example, if the address has a parameter set to cover=no or cover=yes, it will override the setting for the fax send coverpage enable command.

To configure on-ramp security, use the following commands in global configuration mode:

	Command	Purpose
Step1	Router(config)#aaa new model	Enables AAA security services.
Step2	Router(config)#mmoip aaa method fax authentication method-list-name	Defines the name of the method list to be used for Store and Forward Fax AAA authentication.
Step3	Router(config)#mmoip aaa method fax accounting method-list-name	Defines the name of the method list to be used for Store and Forward Fax AAA accounting.
Step4	Router(config)#aaa authentication login {default | list-name} method1 [method2...]	Creates a local authentication method list and enables authentication.
Step5	Router(config)#aaa accounting {system | network | exec | connection | commands level} {default | list-name} {stop-only} [method1 [method2...]]	Creates an accounting method list and enables accounting. We recommend the following configuration: aaa accounting connection list-name stop-only.
Step6	Router(config)#mmoip aaa receive-id primary {ani | dnis | gateway | redialer-id | redialer-dnis}	Specifies the primary location where AAA retrieves its identifying information for on-ramp faxing.
Step7	Router(config)#mmoip aaa receive-id secondary {ani | dnis | gateway | redialer-id | redialer-dnis}	(Optional) Specifies the secondary location where AAA retrieves its identifying information for on-ramp faxing.
Step8	Router(config)#mmoip aaa receive-authentication enable	Enables on-ramp AAA authentication services.
Step9	Router(config)#mmoip aaa receive-accounting enable	Enables on-ramp AAA accounting services.
Step10	Router(config)#radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number]	Specifies the IP address or host name of the remote RADIUS server host and assigns authentication and accounting destination port numbers. (Typical authentication and accounting destination ports are 1645 and 1646.)
Step11	Router(config)#radius-server key string	Specifies the shared secret text string used between the router and the RADIUS server.
Step12	Router(config)#radius-server vsa send accounting	Enables the network access server to recognize and use accounting vendor-specific attributes (VSAs) as defined by RADIUS IETF attribute 26.
Step13	Router(config)#radius-server vsa send authentication	Enables the network access server to recognize and use authentication VSAs as defined by RADIUS IETF attribute 26.

When you enable authentication, the on-ramp gateway inserts whatever value you configure for the mmoip aaa receive-id primary command in the X-account-ID field of the e-mail header. This X-account ID field contains the value that is used for authentication and accounting by the on-ramp gateway. For example, if the mmoip aaa receive-id primary command is set to gateway, the on-ramp gateway name (for example, hostname.domain-name) is inserted in the X-account-ID field of the e-mail header of the fax-mail message.

If you want to use this configured gateway value in the X-account-ID field, you must configure the mmoip aaa send-id primary command with the account-id keyword. This particular keyword enables Store and Forward Fax to generate end-to-end authentication and accounting tracking records. If you do not enable authentication on the on-ramp gateway, the X-account-ID field is left blank.

NoteWe recommend that you configure access control lists (ACLs) to restrict which IP addresses can connect to the SMTP port (port 25). For information about configuring ACLs, refer to the Cisco IOS Security Configuration Guide.

NoteWe strongly recommend that you configure your Cisco AS5300 acting as an off-ramp gateway to only accept incoming SMTP connections from trusted mailers. Configure packet filters to allow only certain trusted IP addresses to send faxes to the Store and Forward Fax off-ramp gateway.

To configure off-ramp security, use the following commands in global configuration mode:

	Command	Purpose
Step1	Router(config)#aaa new model	Enables AAA security services.
Step2	Router(config)#mmoip aaa method fax authentication method-list-name	Defines the name of the method list to be used for Store and Forward Fax AAA authentication.
Step3	Router(config)#mmoip aaa method fax accounting method-list-name	Defines the name of the method list to be used for Store and Forward Fax AAA accounting.
Step4	Router(config)#aaa authentication login {default | list-name} method1 [method2...]	Creates a local authentication method list and enables authentication.
Step5	Router(config)#aaa accounting {system | network | exec | connection | commands level} {default | list-name} {stop-only} [method1 [method2...]]	Creates an accounting method list and enables accounting. We recommend the following configuration: aaa accounting connection list-name stop-only.
Step6	Router(config)#mmoip aaa send-id primary {account-id | envelope-from | envelope-to | gateway}	Specifies the primary location where AAA retrieves its identifying information for off-ramp faxing.
Step7	Router(config)#mmoip aaa send-id secondary {account-id | envelope-from | envelope-to | gateway}	(Optional) Specifies the secondary location where AAA retrieves its identifying information for off-ramp faxing.
Step8	Router(config)#mmoip aaa send-authentication enable	Enables off-ramp AAA authentication services.
Step9	Router(config)#mmoip aaa send-accounting enable	Enables off-ramp AAA accounting services.
Step10	Router(config)#radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number]	Specifies the IP address or host name of the remote RADIUS server host and assigns authentication and accounting destination port numbers. (Typical authentication and accounting destination ports are 1645 and 1646.)
Step11	Router(config)#radius-server key string	Specifies the shared secret text string used between the router and the RADIUS server.
Step12	Router(config)#radius-server vsa send accounting	Enables the network access server to recognize and use accounting VSAs as defined by RADIUS IETF attribute 26.
Step13	Router(config)#radius-server vsa send authentication	Enables the network access server to recognize and use authentication VSAs as defined by RADIUS IETF attribute 26.

Creating ACLs is a relatively complicated task and beyond the scope of this document. The following example, though, provides a starting point.

The following configuration example shows how to restrict access to the SMTP port 25 to a trusted e-mail server (IP address 10.0.0.1):

! Enter global configuration mode.
configure terminal
!
! Configure ACLs to restrict access to the SMTP port (port 25) to only "trusted" e-mail
! servers. Depending on the topology of your particular network, replace the any
! keyword with the destination IP addresses of the Ethernet and FastEthernet
! interfaces. Define all trusted e-mail servers using the tcp host ip-address 
! portion of this command.
access-list 100 permit tcp host 10.0.0.1 any eq smtp
access-list 100 deny tcp any any eq smtp
access-list 100 permit ip any any
!
! Enter interface configuration mode for Ethernet interface 0.
interface ethernet 0
! Apply the access list to this interface.
access-group 100 in
!
! Enter interface configuration mode for FastEthernet interface 0.
interface fastethernet 0
! Apply the access list to this interface.
access-group 100 in
 

For complete information about configuring ACLs, refer to the relative chapters in the Cisco IOS Security Configuration Guide.

For more information about using vendor-specific RADIUS attributes, refer to "RADIUS Attributes" appendix in the Cisco IOS Security Configuration Guide. This appendix file contains a complete list of supported vendor-specific, vendor-proprietary, and IETF-compliant RADIUS attributes, the Cisco IOS releases in which they were implemented, and their definitions.

• Using RADIUS accounting

• Collecting the accounting information using SMTP

The ESMTP Accounting in Store and Forward Fax feature enables you to collect accounting information about fax services as part of the SMTP session. This functionality is activated through the use of an intelligent fax client or MTA. In ESMTP accounting, the off-ramp gateway (acting in its capacity as an ESMTP server) advertises capabilities to the MTA, which is acting as an e-mail client. One of the capabilities the off-ramp gateway advertises is xaccounting, which means that it supports ESMTP accounting. If the MTA recognizes the xaccounting service extension, the MTA (acting as the client) can accept the ESMTP accounting information sent from the off-ramp gateway. If the MTA does not recognize the xaccounting service extension, it will not send the xact command to the off-ramp gateway. In that case, the off-ramp gateway will not respond with ESMTP accounting data.

To use SMTP to collect accounting data, then, you must configure the MTA to explicitly request accounting information as part of the e-mail session---meaning that you must program the MTA to do the following:

• Recognize the xaccounting service extension during the extended hello (ehlo) transaction

• Send the xact command to the off-ramp gateway to activate the ESMTP accounting feature

You need not configure any commands on the Cisco AS5300 to enable ESMTP accounting.

In the following example, ESMTP accounting is manually activated via a Telnet session. The output from the MTA is in bold; the output from the off-ramp Cisco AS5300 is in italics.

NoteIn this particular example, the fax call was placed using a Microcom modem.

telnet 172.14.120.2 25
Trying 172.14.120.2...
Connected to 1.14.120.2.
Escape character is '^]'.
220 mmoip-b.cisco.com Cisco NetWorks ESMTP server
ehlo anyserver.com
250-mmoip-b.cisco.com, hello anyserver.com [223.255.254.10] (really)
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-PIPELINING
250-HELP
250-DSN
250-XSESSION
250 XACCOUNTING
mail from:<>
250 2.5.0 Sender <> ok
rcpt to:<FAX=+1408555-7442@cisco.com>
250 2.1.5 Recipient <FAX=+1408555-7442@cisco.com> ok, maps to '5557442' (cp=yes)
xact
250 2.5.0 XACCOUNTING enabled
data
354 Enter mail, end with a single "."
 
Testing 1 2 3
Testing 1 2 3
Testing 1 2 3
Testing 1 2 3
Testing 1 2 3
Testing 1 2 3
Testing 1 2 3
.
 

The following example shows the accounting information sent to the SMTP server from the off-ramp gateway when the fax transmission is successful:

250-2.5.0 Message delivered to remote fax machine
250-2.5.0 fax_modem_time = 32/41
250-2.5.0 fax_pages = 2
250-2.5.0 gateway_id = mmoip-b.cisco.com
250-2.5.0 fax_connect_speed = 14400bps
250-2.5.0 transmit_bytes = 16870
250-2.5.0 port_used = slot:1 port:2
250-2.5.0 call_type = Fax Send
250-2.5.0 abort_cause = 0
250-2.5.0 T30_error_code = 0
250-2.5.0 ISDN_disconnect_code = 16
250 2.5.0 CSID =555-7442
 

The following example shows the accounting information sent to the SMTP server from the off-ramp gateway when the fax transmission is unsuccessful. In this particular example, the fax transmission was unsuccessful because the line was busy.

450-4.3.2 Modem busy
450-4.3.2 fax_modem_time = 0/59
450-4.3.2 fax_pages = 0
450-4.3.2 gateway_id = mmoip-b.cisco.com
450-4.3.2 fax_connect_speed = 2400bps
450-4.3.2 transmit_bytes = 0
450-4.3.2 port_used = slot:1 port:3
450-4.3.2 call_type = Fax Send
450-4.3.2 abort_cause = 1
450-4.3.2 T30_error_code = 11
450-4.3.2 ISDN_disconnect_code = 17
450 4.3.2 CSID = 

The MDN is sent to an address chosen by the sender. When the sender requests an MDN, the following header is included in the e-mail header of the message:

Disposition-Notification-To:

This header is followed by the address the recipient should use when sending the MDN itself.

RFC2298 requires that the receiver be able to prevent the automatic generation of an MDN. Because of RFC requirement, it is difficult (if not impossible) to determine whether or not the user has actually received the e-mail message based solely on receiving an MDN, for example:

• The recipient can always choose not to respond to MDN requests.

• The recipient software may not understand or accept MDN requests.

To configure MDN for Store and Forward Fax, you need to configure elements on both the on-ramp and off-ramp gateways.

NoteDSNs can only be generated if the mail client on the SMTP server is capable of responding to a DSN request.

Because the SMTP server generates the DSNs, you need to configure both the mail from: and rcpt to: commands for the DSN feature to be operational, for example:

mail from: <user@mail-server.company.com>
rcpt to: <fax=555-1212@company.com> NOTIFY=SUCCESS,FAILURE,DELAY

Three different states can be reported back to the sender as follows:

• Delay---Indicates that, for some reason, the message was delayed in being delivered to the recipient.

• Success---Indicates that the message was successfully delivered to the recipient mailbox.

• Failure---Indicates that, for some reason, the SMTP server was unable to deliver the message to the recipient.

Because these delivery states are not mutually exclusive, you can configure Store and Forward Fax to generate these messages for all or any combination of these events.

To configure DSN, use the following commands beginning in global configuration mode:

	Command	Purpose
Step1	Router(config)#mta send mail-from {hostname string}	Specifies the originator (host name portion) of the e-mail fax message. This information appears in the RFC822 From: field and the RFC821 MAIL FROM field of the e-mail fax message. This information is also used for generating DSNs. When you configure the mta send mail-from hostname command, the host name configured is used with the mta send mail-from username command to form a complete e-mail address, like faxuser@onramp-gateway.com.
Step2	Router(config)#mta send mail-from {username string | username $s$}	Specifies the originator (username portion) of the e-mail fax message. This information appears in the RFC822 From: field and the RFC821 MAIL FROM field of the e-mail fax message. If the wild card $s$ is used, a transmission report is sent to the originating fax machine. This information is also used for generating DSNs. When you configure the mta send mail-from username command, the username configured is used with the mta send mail-from hostname command to form a complete e-mail address, like faxuser@onramp-gateway.com.
Step3	Router(config)#dial-peer voice number mmoip	Defines the MMoIP dial peer tag number and enter dial-peer configuration mode.
Step4	Router(config-dial-)#dsn {delay | success | failure}	Requests that a DSN be sent to the destination(s) defined by the mta send mail-from command.

! Enter global configuration mode.
configure terminal
!
! Define the called subscriber number---in this case, the number configured as the
! destination pattern will be used as the called subscriber identifier.
fax receive called-subscriber $d$
!
! Specify the originator of the e-mail address---in this case, the originator information
! is derived from the calling number.
mta send mail-from username $s$
!
! (Optional) Provide additional information about the sending device. In this example,
! the sending device's hostname is alabama
mta send origin-prefix alabama
!
! Define where this fax-mail should be delivered (which is the mail server postmaster
! account) if it cannot be delivered to the defined destination.
mta send postmaster postmaster@company.com
!
! (Optional) If you decide to configure MDNs, specify the address where they should be
! sent.
mta send return-receipt-to username postmaster@company.com
!
! Specify the destination e-mail server that accepts on-ramp fax-mail.
mta send server california.fax.com
!
! Define the text string that will be displayed as the subject of the fax-mail.
mta send subject Fax-Mail Message
!
!
! Enter dial-peer configuration mode and define an on-ramp POTS peer.
dial-peer voice 1000 pots
!
! Designate fax as the type of information handled by this dial peer.
information-type fax
!
! Specify direct inward dial for this dial peer.
direct-inward-dial
!
!Define the incoming called number associated with this dial peer
incoming called number 5105551212
!
! (Optional) Define the maximum number of connections that will be used simultaneously
! to transmit fax-mail.
max-conns 10
!
!
! Define an on-ramp MMoIP dial peer.
dial-peer voice 1001 mmoip
!
! Define the telephone number associated with this dial peer.
destination-pattern 14085554321
!
! Define a destination e-mail address for this dial peer
session-target mailto:$d$@yourcompany.com
!
! (Optional) Request that DSNs be sent.
dsn
!
! Specify a particular image encoding method to be used for fax images. In this
! example, Modified Huffman (IETF standard) is being specified.
image encoding mh
!
! Specify a particular fax image resolution. In this example, the image resolution was
! set to 204 by 196 pixels per inch (fine).
image resolution fine
!
! Designate fax as the type of information handled by this dial peer.
info-type fax
!
! (Optional) Define the maximum number of connections that will be used simultaneously
! to transmit fax-mail.
max-conn 10
!
! (Optional) Request that MDNs be sent.
mdn
!
! Specify SMTP as the protocol to be used for Store and Forward Fax.
session protocol smtp
 

! Enter global configuration mode.
configure terminal
!
! Define the transmitting subscriber number (TSI); this is the number that is 
! displayed in the LCD of the receiving fax machine. In this example, the sender's
! name, captured by the on-ramp from the sending fax machine) will be used.
fax send transmitting-subscriber $s$
!
! Configure the speed of the fax transmission. In this case, fax transmissions will be
!sent at 14400 bits per second.
fax send max-speed 14400
!
! Define a hostname to be used as an alias for the off-ramp AS5300 device.
mta receive aliases yourcompany.com
!
! (Optional) Specify that the Cisco AS5300 will respond to an MDN request.
mta receive generate-mdn
!
! Define the number of simultaneous SMTP recipients (in this case, 10) handled by this
! Cisco AS5300.
mta receive maximum-recipients 10
!
!
! Specify that the company name will appear in the center position of the fax.
! header information.
fax send center-header Acme Company
!
! Specify that the page count will appear in the right position of the fax header
! information.
fax send right-header $p$
!
! Specify that the date will appear in the left position of the fax header
! information.
fax send left-header $a$
!
! Enable the Cisco AS5300 to send a cover sheet with faxes that originate from e-mail
! messages.
fax send coverpage enable
!
! Add a personalized comment to the title field of the fax cover sheet. In this case,
! the phrase FAX TRANSMISSION was added.
fax send coverpage comment FAX TRANSMISSION
!
! Enter dial-peer configuration mode and define an off-ramp POTS peer.
dial-peer voice 1002 pots
!
! Designate fax as the type of information handled by this dial peer.
information-type fax
!
! Define a telephone number to be associated with this dial peer.
destination-pattern 1408555....
!
! Add prefix.
prefix 9,555
!
! Define an off-ramp MMoIP peer.
dial-peer voice 1003 mmoip
!
! Designate fax as the type of information handled by this dial peer.
information-type fax
!
! Define an incoming called number to be associated with this dial peer.
incoming called-number 14085556789
!
! Specify a particular fax image resolution. In this example, the image resolution was
! set to 204 by 196 pixels per inch (fine).
image resolution fine

! Enter global configuration mode.
configure terminal
! Enable AAA security services.
aaa new-model
! Define the method list to be used with Store and Forward Fax authentication.
mmoip aaa method fax authentication onramp-auth
! Define the method list to be used with Store and Forward Fax accounting services.
mmoip aaa method fax accounting onramp-acct
! Define and enable the AAA authentication method list for Store and Forward Fax.
aaa authentication login onramp-auth radius local
! Define and enable the AAA accounting method list for Store and Forward Fax.
aaa accounting connection onramp-acct stop-only radius
! Enable on-ramp authentication.
mmoip aaa receive-authentication enable
! Enable on-ramp accounting services.
mmoip aaa receive-accounting enable
! Enable off-ramp authorization.
mmoip aaa send-authentication enable.
! Enable off-ramp accounting services.
mmoip aaa receive-accounting enable
! Define the gateway ID as the means by which AAA identifies the user for
! off-ramp authentication.
mmoip aaa send-id primary gateway
! Define the gateway ID as the means by which AAA identifies the user for on-ramp
! authentication.
mmoip aaa receive-id primary gateway
! Configure the Cisco AS5300 to support RADIUS.
radius-server host 173.13.11.13 auth-port 1645 acct-port 1646
radius-server key password
! Configure the RADIUS server to recognize and use vendor-specific attributes.
radius-server vsa send accounting
radius-server vsa send authentication

configure terminal
modem-pool mica-inbound
pool-range 25-84

router# show running configuration
 
Building configuration...
 
Current configuration:
!
! Last configuration change at 19:20:39 PST Mon Jul 14 1997
! NVRAM config last updated at 19:11:04 PST Mon Jul 14 1997
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service internal
service udp-small-servers
service tcp-small-servers
!
hostname mmoip-b
!
boot system tftp /auto/annex2/njoffe/c5300-is-mz 255.255.255.255
boot system flash c5300-is-mz
aaa new-model
aaa authentication login fax radius local
aaa accounting connection fax stop-only radius
!
username njoffe password 0 password
username jfitzhug password 0 password
username wooksong password 0 password
username gmercuri password 0 password
username faryaman password 0 password
username ilyau password 0 password
clock timezone PST -8
clock calendar-valid
!
modem-pool mica-inbound
modem poll time 2
ip subnet-zero
ip host mail-server 10.14.116.1
ip host keyer 223.255.254.254
ip host mail-server.cisco.com 10.14.116.1
ip domain-name cisco.com
ip name-server 10.14.116.1
!
isdn switch-type primary-5ess
fax receive called-subscriber $d$
fax send transmitting-subscriber $s$
fax send left-header $s$
fax send center-header $t$
fax send right-header Page:$p$
fax send coverpage enable
fax send coverpage email-controllable
fax send coverpage comment Cisco cover page comment
mta send server mail-server.cisco.com
mta send subject mmoip-b subject line here
mta send origin-prefix Cisco Powered Fax System
mta send postmaster gmercuri@mail-server.com
mta send mail-from hostname mail-from-hostname.com
mta send mail-from username $s$
mta send return-receipt-to hostname mmoip-b.cisco.com
mta send return-receipt-to username $s$
mta receive aliases mmoip-b.cisco.com
mta receive aliases [1.2.3.4]
mta receive aliases cisco.com
mta receive maximum-recipients 24
mta receive generate-mdn
mmoip aaa send-id primary gateway
mmoip aaa receive-id primary gateway
mmoip aaa method fax authentication fax
mmoip aaa method fax accounting fax
mmoip aaa send-accounting enable
mmoip aaa send-authentication enable
mmoip aaa receive-accounting enable
mmoip aaa receive-authentication enable
!
!
controller T1 0
framing esf
clock source line primary
linecode b8zs
cablelength short 133
pri-group timeslots 1-24
!
controller T1 1
shutdown
framing esf
clock source line secondary 1
linecode b8zs
cablelength short 133
cas-group 0 timeslots 1-24 type e&m-fgb service fax
!
controller T1 2
shutdown
framing esf
linecode b8zs
cablelength short 133
cas-group 0 timeslots 1-24 type e&m-fgb
!
controller T1 3
shutdown
framing esf
linecode b8zs
cablelength short 133
pri-group timeslots 1-24
!
!
voice-port 0:D
timeouts call-disconnect 0
!
voice-port 1:0
timeouts call-disconnect 0
!
voice-port 2:0
timeouts call-disconnect 0
!
voice-port 3:D
timeouts call-disconnect 0
!
dial-peer voice 5 mmoip
destination-pattern 55508..
information-type fax
mdn
dsn success
dsn failure
session target mailto:$d$@mail-server.cisco.com
!
dial-peer voice 1001 pots
incoming called-number 571....
port 0:D
!
dial-peer voice 2 pots
incoming called-number 5550839
information-type fax
direct-inward-dial
!
dial-peer voice 1 pots
destination-pattern 5......
information-type fax
prefix 5
!
num-exp 01133...... 33.......
!
interface Loopback0
no ip address
no ip directed-broadcast
!
interface Tunnel1
no ip address
no ip directed-broadcast
!
interface Ethernet0
ip address 10.14.120.2 255.255.0.0
no ip directed-broadcast
!
interface Serial0:23
no ip address
no ip directed-broadcast
encapsulation ppp
no ip route-cache
dialer rotary-group 1
dialer-group 1
isdn switch-type primary-5ess
isdn tei-negotiation first-call
isdn incoming-voice modem
no fair-queue
!
interface Serial3:23
no ip address
no ip directed-broadcast
shutdown
isdn switch-type primary-5ess
isdn tei-negotiation first-call
no cdp enable
!
interface FastEthernet0
no ip address
no ip directed-broadcast
shutdown
!
interface Group-Async1
ip unnumbered Ethernet0
no ip directed-broadcast
encapsulation ppp
ip tcp header-compression
dialer in-band
dialer-group 1
async mode interactive
peer default ip address pool default
no fair-queue
ppp multilink
group-range 1 12
hold-queue 10 in
!
interface Dialer1
ip unnumbered Loopback0
no ip directed-broadcast
encapsulation ppp
dialer in-band
dialer-group 1
peer default ip address pool def
no fair-queue
ppp multilink
!
ip default-gateway 10.14.0.1
no ip http server
ip classless
ip route 223.255.254.0 255.255.255.0 10.14.0.1
!
dialer-list 1 protocol ip permit
snmp-server engineID local 00000009020000E01EA48784
snmp-server community public RW
radius-server host 10.14.116.1 auth-port 1645 acct-port 1646
radius-server key password
radius-server vsa send accounting
radius-server vsa send authentication
!
line con 0
exec-timeout 0 0
logging synchronous
transport input none
line 1 12
autobaud
autoselect ppp
modem InOut
modem autoconfigure type microcom_hdms
rotary 1
transport input all
line aux 0
line vty 0 4
exec-timeout 0 0
password password
!
exception core-file /auto/annex2/gmercuri/coredump
exception dump 223.255.254.254
ntp source Ethernet0
ntp update-calendar
ntp peer 223.255.254.254
scheduler heapcheck process
scheduler interval 1000
end