Downloads |
Table Of Contents
fax send coverpage e-mail-controllable
fax send coverpage show-detail
fax send transmitting-subscriber
mmoip aaa method fax accounting
mmoip aaa method fax authentication
mmoip aaa receive-accounting enable
mmoip aaa receive-authentication enable
mmoip aaa receive-id secondary
mmoip aaa send-accounting enable
mmoip aaa send-authentication enable
mta receive maximum-recipients
debug fax receive called-number
debug fax receive calling-number
Command Reference
This section documents new or modified commands for the Store and Forward Fax feature. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command references.
•
dsn
•
•
•
•
•
•
•
•
•
•
•
•
•
•
destination-pattern
To specify either the prefix or the full E.164 telephone number (depending on your dial plan) to be used for a POTS or MMoIP dial peer, use the destination-pattern dial-peer configuration command. Use the no form of this command to restore the default value.
destination-pattern [+]string
no destination-patternSyntax Description
Defaults
Enabled with a null string.
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the destination-pattern command to define the E.164 telephone number for this dial peer.
This pattern is used to match dialed digits to a dial peer. The dial peer is then used to complete the call. When a router receives voice data, it compares the called number (the full E.164 telephone number) in the packet header with the number configured as the destination pattern for the voice-telephony peer. The router then strips out the left-justified numbers corresponding to the destination pattern. If you have configured a prefix, the prefix will be appended to the front of the remaining numbers, creating a dial string, which the router will then dial. If all numbers in the destination pattern are stripped-out, the user will receive a dial tone.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Note
Examples
The following example configures the E.164 telephone number "555-1234" for a dial peer:
dial-peer voice 10 potsdestination-pattern +5551234dial-peer voice
To enter dial-peer configuration mode, define the type of dial peer, and define the tag number associated with this dial peer, use the dial-peer voice global configuration command. Use the no form of this command to disable this dial peer.
dial-peer voice number {pots | mmoip | voip}
no dial-peer voice numberSyntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the dial-peer voice global configuration command to switch to dial-peer configuration mode from global configuration mode and to define a particular dial peer. Use the exit command to exit dial-peer configuration mode and return to global configuration mode.
In Store and Forward Fax on the Cisco AS5300, the POTS dial peer defines the inbound faxing line characteristics from the sending fax device to the receiving Cisco AS5300 and the outbound line characteristics from the sending Cisco AS5300 to the receiving fax device. The MMoIP dial peer defines the inbound faxing line characteristics from the Cisco AS5300 to the receiving SMTP mail server.
After you have created a dial peer, that dial peer remains defined and active until you disable that particular dial peer. To disable a dial peer, use the no form of this command.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Note
Example
The following example accesses dial-peer configuration mode and configures a POTS peer identified as dial peer 10 and an MMoIP dial peer identified as dial peer 20:
configure terminaldial-peer voice 10 potsdial-peer voice 20 mmoipThe following example disables the MMoIP peer identified as dial peer 20:
configure terminalno dial-peer voice 20direct-inward-dial
To enable the Direct Inward Dial (DID) call treatment for the incoming called number, use the direct-inward-dial dial-peer configuration command. Use the no form of this command to disable DID.
direct-inward-dial
no direct-inward-dialSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
11.3(1)NA
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the direct-inward-dial command to enable the DID call treatment for the incoming called numbers. When this feature is enabled, the incoming call is treated as if the digits are received from the DID trunk. The called number is used to select the outgoing dial peer. No dial tone will be presented to the caller.
Use the no form of this command to disable DID. When disabled, the called number is used to select the outgoing dial peer. The caller will be prompted for a called number via dial tone.
This command is only applicable to POTS dial peers. This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example enables DID call treatment for incoming called numbers:
dial peer voice 10 potsdirect-inward-dialdsn
To specify that a delivery status notice be delivered to the sender, use the dsn MMoIP dial-peer configuration command. Use the no form of this command to cancel a specific delay status notice option.
dsn {delay | failure | success}
no dsn {delay | failure | success}Syntax Description
Note
Defaults
The default is success and failure.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Delivery status notifications (DSNs) are messages or responses that are automatically generated and sent to the sender or originator of an e-mail message by the SMTP server, notifying the sender of the status of the e-mail message. Specifications for DSN are described in RFC 1891, RFC 1892, RFC 1893, and RFC 1894.
The on-ramp DSN request is included as part of the fax-mail message sent by the on-ramp gateway when the matching MMoIP dial peer has been configured. The on-ramp DSN response is generated by the SMTP server when the fax-mail message is accepted. The DSN is sent back to the user defined in using the mta send mail-from command. The off-ramp DSN is requested by the e-mail client. The DSN response is generated by the SMTP server when it receives a request as part of the fax-mail message.
Note
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,DELAYThere are three different states that can be reported back to the sender:
•
•
•
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.
DSN messages notify the sender of the status of a particular e-mail message containing a fax TIFF image. Use the dsn command to specify which notification messages will be sent to the user.
The dsn command allows you to select more than one notification option by reissuing the command, specifying a different notification option each time. To discontinue a specific notification option, use the no form of the command for that specific keyword.
Note
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example specifies that a DSN message be returned to the sender when the e-mail message containing the fax has been successfully delivered to the recipient or if the message containing the fax has failed, for whatever reason, to be delivered:
dial-peer voice 10 mmoipdsn successdsn failureThe following example specifies that a DSN message be returned to the sender either when the e-mail message containing the fax has been successfully delivered to the recipient or when the message has been delayed:
dial-peer voice 10 mmoipdsn successdsn delayedRelated Commands
fax receive called-subscriber
To define the called subscriber identifier (CSI), use the fax receive called-subscriber global configuration command. Use the no form of this command to disable the configured number.
fax called-subscriber {$d$ | string}
no fax called-subscriber {$d$ | string}Syntax Description
Defaults
Enabled with a null string.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the fax called-subscriber command to define the number displayed in the LCD of the sending fax device when you are sending a fax to a recipient. Typically, with a standard Group 3 fax device, this is the telephone number associated with the receiving fax device. The command defines the CSI.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example configures the number "555-1234" as the called-subscriber number:
configure terminalfax received called-subscriber 5551234fax send center-header
To specify the data that will appear in the center position of the fax header information, use the fax send center-header global configuration command. Use the no form of this command to disable the selected options.
fax send center-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}
no fax send center-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}Syntax Descriptions
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Mail messages that contain only text or contain text attachments (MIME media type of text) can be converted by the off-ramp AS5300 into a format understood by fax machines using the Cisco AS5300's text-to-fax converter. When this conversion is performed, this fax send center-header command is used to indicate what header information should be added to the center top those pages.
Mail messages with TIFF attachments (MIME media type of image and subtype of TIFF) are expected to include their own per-page headers, and the Cisco AS5300's software does not modify TIFF attachments.
Note
This command lets you configure multiple options at once—meaning that you can combine one or more wild cards with text string information to personalize your fax header information.
Note
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example selects the transmission time of the fax as the center fax header information:
configure terminalfax send center-header $t$The following example configures the company name "Widget" and its address as the center fax header information:
configure terminalfax send center-header widget $s$Related Commands
fax send left-header
Specifies the data that will appear on the left in the fax header.
fax send right-header
Specifies the data that will appear on the right in the fax header.
fax send coverpage comment
To define personalized text for the title field of a fax cover sheet, use the fax send coverpage comment global configuration command. Use the no form of this command to disable the defined comment.
fax send coverpage comment string
no fax send coverpage comment stringSyntax Description
string
Text string that adds personalized text in the title field of the fax cover sheet. Valid characters are any ASCII characters.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The fax send coverpage comment command can be overridden by the fax send coverpage e-mail controllable command.
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example configures an individualized title comment of "Acme Fax Services" for generated fax cover sheets:
configure terminalfax send coverpage enablefax send coverpage comment Acme Fax ServicesRelated Commands
fax send coverpage e-mail-controllable
To defer to the cover page setting in the e-mail header to generate a standard fax cover sheet, use the fax send coverpage e-mail-controllable global configuration command. Use the no form of this command to disable standard fax sheet generation.
fax send coverpage e-mail-controllable
no fax send coverpage e-mail-controllableSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
You can also use the destination address of an e-mail message to control the cover page generation on a per-recipient basis. 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 this and generate and send a fax cover page.
shows examples of what the user would enter in the To: field of the e-mail message.
Table 3
Example Entries for the To: Field
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example enables standard generated fax cover sheets:
configure terminalfax send coverpage enablefax send coverpage e-mail-controllableRelated Commands
fax send coverpage enable
To enable the Cisco AS5300 to generate fax cover sheets for faxes that originate from e-mail messages, use the fax send coverpage enable global configuration command. Use the no form of this command to disable fax cover sheet generation functionality.
fax send coverpage enable
no fax send coverpage enableSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Note
This command applies to off-ramp Store and Forward Fax functions.
Example
The following example enables Cisco AS5300-generated fax cover sheets:
configure terminalfax send coverpage enableRelated Commands
fax send coverpage show-detail
To print all of the e-mail header information as part of the fax cover sheet, use the fax send coverpage show-detail global configuration command. Use the no form of this command to disable the e-mail header information being displayed.
fax send coverpage show-detail
no fax send coverpage show-detailSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to off-ramp Store and Forward Fax functions.
Note
Examples
The following example configures an individualized generated fax cover sheet that contains the e-mail header text:
configure terminalfax send coverpage enableno fax send coverpage e-mail-controllablefax send coverpage show-detailRelated Commands
fax send left-header
To specify the data that will appear on the left in the fax header, use the fax send left-header global configuration command. Use the no form of this command to disable the selected options.
fax send left-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}
no fax send left-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Mail messages that contain only text or contain text attachments (MIME media type of text) can be converted by the off-ramp AS5300 into a format understood by fax machines using the AS5300's text-to-fax converter. When this conversion is performed, this fax send left-header command is used to indicate what header information should be added to the left top of those pages.
Mail messages with TIFF attachments (MIME media type of image and subtype of TIFF) are expected to include their own per-page headers and the AS5300's software does not modify TIFF attachments.
This command lets you configure multiple options at once—meaning that you can combine one or more wild cards with text string information to personalize your fax header information.
Note
This command applies to off-ramp Store and Forward Fax functions.
Example
The following example selects the transmission time of the fax as the left fax header information:
configure terminalfax send left-header $t$The following example configures the company name "Widget" and its address as the left fax header information:
configure terminalfax send left-header widget $s$Related Commands
fax send max-speed
To specify the maximum speed at which an outbound fax will be transmitted, use the fax send max-speed global configuration command. Use the no form of this command to disable the selected speed.
fax send max-speed {12000 | 14400 | 2400 | 4800 | 7200 | 9600}
no fax send max-speed {12000 | 14400 | 2400 | 4800 | 7200 | 9600}Syntax Description
Defaults
14400
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example sets the outbound fax transmission rate at 2400 bps:
configure terminalfax send max-speed 2400fax send right-header
To specify the data that will appear on the right in the fax header information, use the fax send right-header global configuration command. Use the no form of this command to disable the selected options.
fax send right-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}
no fax send right-header {$a$ | $d$ | $p$ | $s$ | $t$ | string}Syntax Description
Defaults
No connection
Command Modes
Global configuration
Command History
Usage Guidelines
Mail messages that contain only text or contain text attachments (MIME media type of text) can be converted by the off-ramp AS5300 into a format understood by fax machines using the AS5300's text-to-fax converter. When this conversion is performed, this fax send right-header command is used to indicate what header information should be added to right top of those pages.
Mail messages with TIFF attachments (MIME media type of image and subtype of TIFF) are expected to include their own per-page headers and the AS5300's software does not modify TIFF attachments.
This command lets you configure multiple options at once—meaning that you can combine one or more wildcards with text string information to personalize your fax header information.
Note
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example selects the date of the fax as the right fax header information:
configure terminalfax send right-header $a$The following example configures the company name "Widget" and its address as the right fax header information:
configure terminalfax send right-header widget $s$Related Commands
fax send center-header
Specifies the data that will appear in the center in the fax header.
fax send left-header
Specifies the data that will appear on the left in the fax header.
fax send transmitting-subscriber
To define the transmitting subscriber identifier (TSI), use the fax send transmitting-subscriber global configuration command. Use the no form of this command to disable the configured value.
fax send transmitting-subscriber {$s$ | string}
no fax send transmitting-subscriber {$s$ | string}Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
The transmitting subscriber number is the number displayed in the LCD of the receiving fax device. Typically, with a standard Group 3 fax device, this is the telephone number associated with the transmitting or sending fax device. This command defines the TSI.
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example configures the company's name (as captured by the on-ramp from the sending fax machine as +18005551234) as the TSI:
configure terminalfax send transmitting-subscriber +14085551234image encoding
To select a specific encoding method for fax images associated with an MMoIP dial peer, use the image encoding dial-peer configuration command. Use the no form of this command to restore the default value.
image encoding{mh | mr | mmr | passthrough}
no image encoding{mh | mr | mmr | passthrough}Syntax Description
Defaults
Passthrough
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use the image encoding command to specify an encoding method for e-mail fax TIFF images for a specific MMoIP dial peer. This command applies primarily to the on-ramp MMoIP dial peer. Although you can optionally create an off-ramp dial peer and configure a particular image encoding value for that off-ramp call leg, Store and Forward Fax ignores the off-ramp MMoIP setting and transmits the file using Modified Huffman encoding.
There are four available encoding methods:
Modified Huffman (MH)—One-dimensional data compression scheme that compresses data in only one direction (horizontal). Modified Huffman compression does not allow the transmission of redundant data. This encoding method produces the largest image file size.
Modified Read (MR)—Two-dimensional data compression scheme (used by fax devices) that handles the data compression of the vertical line and that concentrates on the space between lines and within given characters.
Modified Modified Read (MMR)—Data compression scheme used by newer Group 3 fax devices. This encoding method produces the smallest possible image file size and is slightly more efficient than Modified Read.
Passthrough—No encoding method will be applied to the image—meaning that the image will be encoded by whatever encoding method is used by the fax device.
The IETF standard for transmitting fax TIFF images is Modified Huffman encoding with fine or standard resolution. RFC 2301 requires compliant receivers support TIFF images with MH encoding and fine or standard resolution. If a receiver supports features beyond this minimal requirement, you might want to configure the Cisco AS5300 to send enhanced-quality documents to that receiver.
The primary reason to use a different encoding scheme from MH is to save network bandwidth. MH ensures interoperability with all Internet fax devices but it is the least efficient of the encoding schemes for transmitting fax TIFF images. For most images, MR is more efficient than MH and MMR is more efficient than MR. If you know the recipient is capable of receiving more efficient encodings than just MH, Store and Forward Fax allows you to send the most efficient encoding the recipient can process. For end-to-end closed networks, you can choose any encoding scheme because the off-ramp gateway can process MH, MR, and MMR.
Another factor to take into account is the viewing software. Many viewing applications (for example, those that come with Windows `95 or Windows NT) are able to display MH, MR, and MMR. Therefore you should decide, based on the viewing application and the available bandwidth, which encoding scheme is right for your network.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following example selects Modified Modified Read as the encoding method for fax TIFF images sent by MMoIP dial peer 10:
dial-peer voice 10 mmoipimage encoding mmrRelated Commands
image-resolution
Specifies a particular fax image resolution for a specific MMoIP dial peer.
image resolution
To specify a particular fax image resolution for a specific MMoIP dial peer, use the image resolution dial-peer configuration command. Use the no form of this command to restore the default value.
image resolution {fine | standard | superfine | passthrough}
no connection {fine | standard | superfine | passthrough}Syntax Description
Defaults
Passthrough
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use the image resolution command to specify a specific resolution (in pixels per inch) for e-mail fax TIFF images sent by the specified MMoIP dial peer. This command applies primarily to the on-ramp MMoIP dial peer. Although you can optionally create an off-ramp dial peer and configure a particular image resolution value for that off-ramp call leg, Store and Forward Fax ignores the off-ramp MMoIP setting and transmits the file using fine resolution.
This command enables you to increase or decrease the resolution of a fax TIFF image, thereby changing not only the resolution but the size of the fax TIFF file. The IETF standard for transmitting fax TIFF images is Modified Huffman encoding with fine or standard resolution. The primary reason to configure a different resolution is to save network bandwidth.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following example selects the resolution fine (meaning 204-by-196 pixels per inch) for e-mail fax TIFF images associated with MMoIP dial peer 10:
dial-peer voice 10 mmoipimage encoding mhimage resolution fineRelated Commands
image encoding
Specifies a specific encoding method for e-mail TIFF images for a specific MMoIP dial peer.
incoming called-number
To specify an incoming called number of an MMoIP or POTS dial peer, use the incoming called-number dial-peer configuration command. Use the no form of this command to reset the default value for this command.
incoming called-number string
no incoming called-number stringSyntax Description
string
Specifies the incoming called telephone number. Valid entries are any series of digits that specify the E.164 telephone number.
Defaults
No incoming called number is defined.
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the incoming-called number command to define the destination telephone number for a particular dial peer. For the on-ramp POTS dial peer, this telephone number is the DNIS number of the incoming fax call. For the off-ramp MMoIP dial peer, this telephone number is the destination fax machine telephone number.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following example configures the number (310)555-9261 as the incoming called number for MMoIP dial peer 10:
dial-peer voice 10 mmoipincoming 3105559261information-type
To select a particular information type for either an MMoIP or a POTS dial peer, use the information-type dial-peer configuration command. Use the no form of this command to reset the default value for this command.
information type {fax | voice}
no information type {fax | voice}Syntax Description
fax
Indicates that the information type has been set to store and forward fax.
voice
Indicates that the information type has been set to voice.
Defaults
Voice
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following example sets the information type for MMoIP dial peer 10 to fax:
dial-peer voice 10 mmoipinformation-type faxmax-conn
To specify a maximum number of connections for a particular MMoIP or POTS dial peer, use the max-conn dial-peer configuration command. Use the no form of this command to set an unlimited number of connections for this dial peer.
max-conn number
no max-conn numberSyntax Description
number
Specifies the maximum number of connections for this dial peer. Valid values for this field are 1 to 2147483647.
Defaults
The no form of this command is the default, meaning unlimited number of connections.
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the max-conn command to define the maximum number of connections used simultaneously on the Cisco AS5300 to transmit fax-mail.
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example configures the maximum number of connections for MMoIP dial peer 10 as 5:
dial-peer voice 10 mmoipmax-conn 5Related Commands
mta receive maximum-recipients
Specifies the maximum number of recipients for all SMTP connections.
mdn
To request that a message disposition notice be generated when the message is processed ("opened"), use the mdn command. Use the no form of this command to restore the default value.
mdn
no mdnSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Message disposition notification is an e-mail message that is generated and sent to the sender when the message is opened by the receiver. Use the mdn command to request that an e-mail response message be sent to the sender when the e-mail containing the fax TIFF image has been opened.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example requests that a message disposition notice be generated by the recipient:
dial-peer voice 10 mmoipmdnRelated Commands
mmoip aaa global password
To define a password to be used with CiscoSecure for Windows NT when using Store and Forward Fax with a modem card, use the mmoip aaa global password global configuration command. Use the no form of this command to restore the default value.
mmoip aaa default password password
no mmoip aaa default password passwordSyntax Description
password
Character string used to define the CiscoSecure for Windows NT password to be used with Store and Forward Fax. Maximum length is 64 alphanumeric characters.
Defaults
No password defined.
Command Modes
Global configuration
Command History
Usage Guidelines
CiscoSecure for Windows NT might require a separate password in order to complete authentication, no matter what security protocol you use. This command defines the password to be used with CiscoSecure for Windows NT. All records on the Windows NT server use this defined password.
This command applies to on-ramp Store and Forward Fax functions when using a modem card. It is not used with voice feature cards.
Examples
The following example defines a password (abercrombie) when CiscoSecure for Windows NT is used with Store and Forward Fax:
configure terminalmmoip aaa global-password abercrombiemmoip aaa method fax accounting
To define the name of the method list to be used for AAA accounting with Store and Forward Fax on a modem card, use the mmoip aaa method fax accounting global configuration command. Use the no form of this command to restore the default value.
mmoip aaa method fax accounting method-list-name
no mmoip aaa method fax accounting method-list-nameSyntax Description
method-list-name
Character string used to name a list of accounting methods to be used with Store and Forward Fax.
Defaults
No AAA accounting method list defined.
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines the name of the AAA accounting method list to be used with Store and Forward Fax. The method list itself, which defines the type of accounting services provided for Store and Forward Fax, is defined using the aaa accounting global configuration command. Unlike standard AAA (where each defined method list can be applied to specific interfaces and lines), the AAA accounting method lists used in Store and Forward Fax are applied globally on the Cisco AS5300.
After the accounting method lists have been defined, they are enabled by using the mmoip aaa receive-accounting enable command.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions when using a modem card. It is not used with voice feature cards.
Examples
The following example defines a AAA accounting method list (called sherman) to be used with Store and Forward Fax:
configure terminalaaa new-modelmmoip aaa method fax accounting shermanRelated Commands
mmoip aaa method fax authentication
To define the name of the method list to be used for AAA authentication with Store and Forward Fax, use the mmoip aaa method fax authentication global configuration command. Use the no form of this command to restore the default value.
mmoip aaa method fax authentication method-list-name
no mmoip aaa method fax authentication method-list-nameSyntax Description
method-list-name
Character string used to name a list of authentication methods to be used with Store and Forward Fax.
Defaults
No AAA authentication method list defined.
Command Modes
Global configuration
Command History
Usage Guidelines
This command defines the name of the AAA authentication method list to be used with Store and Forward Fax. The method list itself, which defines the type of authentication services provided for Store and Forward Fax, is defined using the aaa authentication global configuration command. Unlike standard AAA (where each defined method list can be applied to specific interfaces and lines), AAA authentication method lists used with Store and Forward Fax are applied globally on the Cisco AS5300.
After the authentication method lists have been defined, they are enabled by using the mmoip aaa receive-authentication enable command.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following example defines a AAA authentication method list (called peabody) to be used with Store and Forward Fax:
configure terminalaaa new-modelmmoip aaa method fax authentication peabodyRelated Commands
mmoip aaa receive-authentication enable
Enables on-ramp AAA authentication services.
mmoip aaa receive-accounting enable
To enable on-ramp AAA accounting services, use the mmoip aaa receive-accounting enable global configuration command. Use the no form of this command to restore the default value.
mmoip aaa receive-accounting enable
no mmoip aaa receive-accounting enableSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables AAA accounting services if a AAA accounting method list has been defined using both the aaa accounting command and the mmoip aaa method fax accounting command.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example enables a AAA accounting method list (called sherman) to be used with inbound Store and Forward Fax. In this example, Store and Forward Fax is being configured to track start and stop connection accounting records.
configure terminalaaa new-modelmmoip aaa method fax accounting shermanaaa accounting connection sherman stop-only radiusmmoip aaa receive-accounting enableRelated Commands
mmoip aaa method fax accounting
Defines the name of the method list to be used for AAA accounting with Store and Forward Fax.
mmoip aaa receive-authentication enable
To enable on-ramp AAA authentication services, use the mmoip aaa receive-authentication enable global configuration command. Use the no form of this command to restore the default value.
mmoip aaa receive-authentication enable
no mmoip aaa receive-authentication enableSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables AAA authentication services if a AAA authentication method list has been defined using both the aaa authentication command and the mmoip aaa method fax authentication command.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example enables a AAA authentication method list (called peabody) to be used with inbound Store and Forward Fax. In this example, RADIUS (and if the RADIUS server fails, then local) authentication is being configured for Store and Forward Fax.
configure terminalaaa new-modelmmoip aaa method fax authentication peabodyaaa authentication login peabody radius localmmoip aaa receive-authentication enableRelated Commands
mmoip aaa method fax authentication
Defines the name of the method list to be used for AAA authentication with Store and Forward Fax.
mmoip aaa receive-id primary
To specify the primary location where AAA retrieves its account identification information for on-ramp faxing, use the mmoip aaa receive-id primary global configuration command. Use the no form of this command to restore the default value, which means that account identification source is undefined.
mmoip aaa receive-id primary {ani | dnis | gateway | redialer-id | redialer-dnis}
no mmoip aaa receive-id primary {ani | dnis | gateway | redialer-id | redialer-dnis}Syntax Description
Defaults
No account identification source is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Normally, when AAA is being used for simple user authentication, AAA uses the username information defined in the user profile for authentication. With Store and Forward Fax, you can specify that the ANI, DNIS, gateway ID, redialer ID, or redialer DNIS be used to identify the user for authentication. This command defines what AAA uses for the primary identifier for inbound or on-ramp user authentication with Store and Forward Fax.
Store and Forward Fax allows you to define either a primary or a secondary identifier. (You configure the secondary identifier using the mmoip aaa receive-id secondary command.)
AAA does not use these methods sequentially—meaning that if the primary identifier is defined and AAA cannot authenticate the primary identifier information, it will not use the secondary identifier for authentication. Authentication simply fails.
Defining only the secondary identifier enables you to service two different scenarios simultaneously—for example, if you are offering fax services to two different companies, one of which uses redialers and the other of which does not. In this case, configure the mmoip aaa receive-id primary command to use the redialer DNIS, and configure the mmoip aaa receive id secondary command to use ANI. With this configuration, when a user dials in and the redialer-DNIS is not null, then the redialer DNIS is used as the authentication identifier. If a user dials in and the redialer DNIS is null, then ANI is used as the authentication identifier.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example defines the DNIS captured by the redialer as the AAA authentication identifier for Store and Forward Fax:
configure terminalaaa new-modelmmoip aaa receive-id primary redialer-dnisRelated Commands
mmoip aaa receive-id secondary
Specifies the primary location where AAA retrieves its account identification information for on-ramp faxing.
mmoip aaa receive-id secondary
To specify the secondary location where AAA retrieves its account identification information for on-ramp faxing if the primary identifier has not been defined, use the mmoip aaa receive-id secondary global configuration command. Use the no form of this command to restore the default value, which means that account identification source is undefined.
mmoip aaa receive-id secondary {ani | dnis | gateway | redialer-id | redialer-dnis}
no mmoip aaa receive-id secondary {ani | dnis | gateway | redialer-id | redialer-dnis}Syntax Description
Defaults
No account identification source is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Normally, when AAA is being used for simple user authentication, AAA uses the username information defined in the user profile for authentication. With Store and Forward Fax, you can specify that the ANI, DNIS, gateway ID, redialer DNIS, or redialer ID be used to identify the user for authentication. This command defines what AAA uses for the secondary identifier for inbound or on-ramp user authentication with Store and Forward Fax if the primary identifier has not been defined.
Store and Forward Fax allows you to define either a primary or a secondary identifier. (You configure the primary identifier using the mmoip aaa receive-id primary command.)
AAA does not use these methods sequentially—meaning that if the primary identifier is defined and AAA cannot match the primary identifier information, it will not use the secondary identifier for authentication. Authentication simply fails.
Defining only the secondary identifier enables you to service two different scenarios simultaneously—for example, if you are offering fax services to two different companies, one of which uses redialers and the other of which does not. In this case, configure the mmoip aaa receive-id primary command to use the redialer DNIS, and configure the mmoip aaa receive id secondary command to use ANI. With this configuration, when a user dials in and the redialer-DNIS is not null, then the redialer DNIS is used as the authentication identifier. If a user dials in and the redialer DNIS is null, then ANI is used as the authentication identifier.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example defines the DNIS captured by the redialer as the secondary AAA authentication identifier for Store and Forward Fax:
configure terminalaaa new-modelmmoip aaa receive-id secondary redialer-dnisRelated Commands
mmoip aaa receive-id primary
Specifies the primary location where AAA retrieves its account identification information for on-ramp faxing.
mmoip aaa send-accounting enable
To enable off-ramp AAA accounting services when using Store and Forward Fax on a modem card, use the mmoip aaa send-accounting enable global configuration command. Use the no form of this command to restore the default value.
mmoip aaa send-accounting enable
no mmoip aaa send-accounting enableSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Mode
Global configuration
Command History
Usage Guidelines
This command enables AAA accounting services if a AAA accounting method list has been defined using both the aaa accounting command and the mmoip aaa method fax accounting command.
This command applies to off-ramp Store and Forward Fax functions when using a modem card. It is not used with voice feature cards.
Examples
The following example enables a AAA accounting method list (called sherman) to be used with outbound Store and Forward Fax. In this example, Store and Forward Fax is being configured to track start and stop connection accounting records.
configure terminalaaa new-modelmmoip aaa method fax accounting shermanaaa accounting connection sherman stop-only radiusmmoip aaa send-accounting enableRelated Commands
mmoip aaa method fax accounting
Defines the name of the method list to be used for AAA accounting with Store and Forward Fax.
mmoip aaa send-authentication enable
To enable off-ramp AAA authentication services, use the mmoip aaa send-authentication enable global configuration command. Use the no form of this command to restore the default value.
mmoip aaa send-authentication enable
no mmoip aaa send-authentication enableSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables AAA authentication services if a AAA authentication method list has been defined using both the aaa authentication command and the mmoip aaa method fax authentication command.
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example enables a AAA authentication method list (called peabody) to be used with outbound Store and Forward Fax. In this example, RADIUS (and if the RADIUS server fails, then local) authentication is being configured for Store and Forward Fax.
configure terminalaaa new-modelmmoip aaa method fax authentication peabodyaaa authentication login peabody radius localmmoip aaa send-authentication enableRelated Commands
mmoip aaa method fax authentication
Defines the name of the method list to be used for AAA authentication with Store and Forward Fax.
mmoip aaa send-id primary
To specify the primary location where AAA retrieves its account identification information for off-ramp faxing, use the mmoip aaa send-id primary global configuration command. Use the no form of this command to restore the default value, which means that account identification source is undefined.
mmoip aaa send-id primary {account-id | envelope-from | envelope-to | gateway}
no mmoip aaa send-id primary {account-id | envelope-from | envelope-to | gateway}Syntax Description
Defaults
No account identification source is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Normally, when AAA is being used for simple user authentication, AAA uses the username information defined in the user profile for authentication. With Store and Forward Fax, you can specify that the account ID, username, or recipient name from the e-mail header information be used to identify the user for authentication. This command defines what AAA uses for the primary identifier for outbound or off-ramp user authentication with Store and Forward Fax.
Store and Forward Fax allows you to define either a primary or a secondary identifier. (You configure the secondary identifier using the mmoip aaa send-id secondary command.) AAA extracts the authentication identifier information from the defined sources. If the field is blank (meaning undefined), AAA will use the secondary identifier source if configured. The secondary identifier is used only when the primary identifier is null. In this case, when AAA sees that the primary identifier is null, it will check to see if a secondary identifier has been defined and use that value for user authentication.
AAA does not use these methods sequentially—meaning that if the primary identifier is defined and AAA cannot authenticate the primary identifier information, it will not use the secondary identifier for authentication. Authentication simply fails.
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.
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example defines the recipient name as defined in the envelope-to field of the e-mail header to be used as the AAA authentication identifier for Store and Forward Fax:
configure terminalaaa new-modelmmoip aaa send-id primary envelope-toRelated Commands
mmoip aaa send-id secondary
Specifies the secondary location where AAA retrieves its account identification information for off-ramp faxing.
mmoip aaa send-id secondary
To specify the secondary location where AAA retrieves its account identification information for off-ramp faxing, use the mmoip aaa send-id secondary global configuration command. Use the no form of this command to restore the default value, which means that account identification source is undefined.
mmoip aaa send-id secondary {account-id | envelope-from | envelope-to | gateway}
no mmoip aaa send-id secondary {account-id | envelope-from | envelope-to | gateway}Syntax Description
Defaults
No account identification source is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Normally, when AAA is being used for simple user authentication, AAA uses the username information defined in the user profile for authentication. With Store and Forward Fax, you can specify that the account ID, username, or recipient name from the e-mail header information be used to identify the user for authentication. This command defines what AAA uses for the secondary identifier for outbound or off-ramp user authentication with Store and Forward Fax.
Store and Forward Fax allows you to define either a primary or a secondary identifier. (You configure the secondary identifier using the mmoip aaa send-id primary command.) AAA extracts the authentication identifier information from the defined sources. If the field is blank (meaning undefined), AAA will use the secondary identifier source if configured. The secondary identifier is used only when the primary identifier is null. In this case, when AAA sees that the primary identifier is null, it will check to see if a secondary identifier has been defined and use that value for user authentication.
AAA does not use these methods sequentially—meaning that if the primary identifier is defined and AAA cannot match the primary identifier information, it will not use the secondary identifier for authentication. Authentication simply fails.
When you enable authentication, the on-ramp gateway inserts whatever value you configure for the mmoip aaa receive-id secondary command in the X-account-ID field of the e-mail header (if Store and Forward uses the defined secondary identifier). 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 secondary 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 secondary 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.
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example defines the recipient name as defined in the envelope-to field of the e-mail header to be used as the AAA authentication identifier for Store and Forward Fax:
configure terminalaaa new-modelmmoip aaa send-id secondary envelope-toRelated Commands
mmoip aaa send-id primary
Specifies the primary location where AAA retrieves its account identification information for off-ramp faxing
mta receive aliases
To specify a host name accepted as an SMTP alias for off-ramp faxing, use the mta receive aliases global configuration command. Use the no form of this command to disable this alias.
mta receive aliases string
no mta receive aliases stringSyntax Description
Defaults
Enabled with an empty string
Command Modes
Global configuration
Command History
Usage Guidelines
This command creates an accept or reject alias list. The first alias is used by the mailer to identify itself in SMTP banners and when generating its own RFC 822 Received: header.
Note
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example specifies the host name seattle-fax-offramp.example.com as the alias for the SMTP server:
configure terminalmta receive aliases seattle-fax-offramp.example.comThe following example specifies the host name 172.16.0.0 as the alias for the SMTP server:
configure terminalmta receive aliases [172.16.0.0]Related Commands
mta receive generate-mdn
To specify that the off-ramp gateway process a response message delivery notification (MDN) from an SMTP server, use the mta receive generate-mdn global configuration command. Use the no form of this command to disable message delivery notice generation.
mta receive generate-mdn
no mta receive generate-mdnSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
When message delivery notification is enabled on a sending Cisco AS5300, the device inserts a flag in the off-ramp message e-mail header, requesting that the receiving Cisco AS5300 generate the message delivery notification and return that message to the sender when the e-mail message containing the fax image is opened. Use the mta receive generate-mdn command to enable the receiving device—the off-ramp gateway—to process the response message delivery notification.
Depending on the configuration, usage, and features of the mailers used at a site, it might be desirable to enable or disable MDN generation. (DSN generation cannot be disabled.)
Specifications for MDN are described in RFC 2298.
This command applies to off-ramp Store and Forward Fax functions.
Examples
The following enables the receiving device to generate message delivery notices:
configure terminalmta receive generate-mdnRelated Commands
mta receive maximum-recipients
To specify the maximum recipients for all SMTP connections, use the mta receive maximum-recipients global configuration command. Use the no form of this command to restore the default value.
mta receive maximum-recipients number
no mta receive maximum-recipientsSyntax Description
number
Specifies the maximum number of recipients for all SMTP connections. Valid entries are from 0 to 1024.
Defaults
The default is 0 recipients. This means that incoming mail messages will not be accepted, thus no faxes will be transmitted by the off-ramp gateway.
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to off-ramp Store and Forward Fax functions.
Note
Use the mta receive maximum-recipients command to configure the maximum number of modems you want to allocate for fax usage at any one time. You can use this command to limit the resource usage on the gateway. When the value for the number argument is set to 0, no new connections can be established. This is particularly useful when preparing to shut down the system.
Examples
The following example defines 10 as the maximum number of recipients for all SMTP connections:
configure terminalmta receive maximum-recipients 10Related Commands
mta send mail-from
To specify the mail-from address (also called the RFC 821 envelope-from or the Return-Path address), use the mta send mail-from global configuration command. Use the no form of this command to disable this return path information.
mta send mail-from {hostname string | {username string | username $s$}}
no mta send mail-from {hostname string | {username string | username $s$}}Syntax Description
Defaults
None.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the mta send mail-from command to designate the sender of the fax TIFF attachment. This value is equivalent to the return path information in an e-mail message.
The postmaster address, configured with the mta send postmaster command, is used if the mail-from address is blank.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example specifies that the mail-from username information will be derived from the sender's calling number:
configure terminalmta send mail-from username $s$Related Commands
mta send origin-prefix
To add additional information to the e-mail prefix header, use the mta send origin-prefix global configuration command. Use the no form of this command to disable the defined string.
mta send origin-prefix string
no mta send origin-prefix stringSyntax Description
string
Text string that adds comments to the e-mail prefix header. If this string contains more than one word, the string value should be contained within quotation marks ("x").
Defaults
Null string
Command Modes
Global configuration
Command History
Usage Guidelines
Normally, the Store and Forward Fax feature provides the slot and port number from which this e-mail came in the e-mail prefix header information. Use this command to append the defined text string to the front of the e-mail prefix header information. This test string is a prefix string that is appended with the modem port and slot number and passed in the originator_comment field of the esmtp_client_engine_open() call. Eventually, this ends up in the Received header field of the fax-mail message. For example:
Received (test onramp Santa Cruz slot1 port15) by router-5300.cisco.com for <test-test@cisco.com> (with Cisco NetWorks); Fri, 25 Dec 1998 001500 -0800In other words, using the command mta send origin-prefix dog will cause the Received header to contain the following information:
Received (dog, slot 3 modem 8) by as5300-sj.example.com .....This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example provides the user with additional information:
configure terminalmta send origin-prefix Cisco-Powered Fax SystemRelated Commands
mta send postmaster
To define where an e-mail should be delivered (the mail server postmaster account) if it cannot be delivered to the defined destination, use the mta send postmaster global configuration command. Use the no form of this command to disable this defined postmaster.
mta send postmaster e-mail-address
no mta send postmaster e-mail-addressSyntax Description
e-mail-address
Defines where this e-mail should be delivered (the mail server postmaster account) if it cannot be delivered to the defined destination.
Defaults
Undefined
Command Modes
Global configuration
Command History
Usage Guidelines
If you have configured the Cisco AS5300 to generate DSNs and MDNs but you have not configured the sender information (using the mta send mail-from command) or the SMTP server, DSNs and MDNs will be delivered to this e-mail address.
The address defined by this command is 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 example.com is replaced with your domain name, and fax-administrator is aliased to the person responsible for the operation of the AS5300's 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 and thus should be a different e-mail address.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example configures the e-mail address fax-admin@example.com as the sender for all incoming faxes. Thus, any returned DSNs will be delivered to fax-admin@example.com if the Mail From filed is otherwise blank.
configure terminalmta send postmaster fax-admin@example.comRelated Commands
mta send return-receipt-to
To specify the address where MDNs will be sent, use the mta send return-receipt-to global configuration command. Use the no form of this command to restore the default value.
mta send return-receipt-to {hostname string | {username string | $s$}}
no mta send return-receipt-to {hostname string | {username string | $s$}}Syntax Description
Defaults
None defined
Command Modes
Global configuration
Command History
Usage Guidelines
Use the mta send return-receipt-to command to define where you want MDNs to be sent after the fax-mail is opened.
Note
Note
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example configures scoobee as the SMTP mail server to which DSNs will be sent:
configure terminalmta send return-receipt-to hostname server.commta send return-receipt-to username scoobeeRelated Commands
mta send server
To specify a destination mail server or servers, use the mta send server global configuration command. Use the no form of this command to disable the specified destination mail server.
mta send server {host-name | IP-address}
no mta send server {host-name | IP-address}Syntax Description
host-name
Defines the host name of the destination mail server.
IP-address
Defines the IP address of the destination mail server.
Defaults
IP address defined as 0.0.0.0
Command Modes
Global configuration
Command History
Usage Guidelines
Use the mta send server command to provide a backup destination server in case the first configured mail server is unavailable. (This command is not intended to be used for load distribution.)
You can configure up to 10 different destination mail servers using the mta send server command. If you configure more than one destination mail server, the Cisco AS5300 attempts to contact the first mail server configured. If that mail server is unavailable, it will contacts the next configured destination mail server.
DNS MX records are not used to look up hostnames provided to this command.
Note
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example defines the mail servers scoobee.example.com and doogie.example.com as the destination mail servers:
configure terminalmta send server scoobee.example.commta send server doogie.example.comRelated Commands
mta send subject
To specify the subject header of the e-mail, use the mta send subject global configuration command. Use the no form of this command to disable this string.
mta send subject string
no mta send subject stringSyntax Description
Defaults
Null string
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to on-ramp Store and Forward Fax functions.
Note
Examples
The following example defines the subject header of an e-mail message as "fax attachment":
configure terminalmta send subject fax attachmentRelated Commands
prefix
To specify the prefix of the dialed digits for this dial peer, use the prefix dial-peer configuration command. Use the no form of this command to disable this feature.
prefix string
no prefixSyntax Description
Defaults
Null string
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the prefix command to specify a prefix for a specific dial peer. When an outgoing call is initiated to this dial peer, the prefix string value is sent to the telephony interface first, before the telephone number associated with the dial peer.
If you want to configure different prefixes for dialed numbers on the same interface, you need to configure different dial peers.
This command is applicable only to POTS dial peers. This command applies to off-ramp Store and Forward Fax functions.
Examples
The following example specifies a prefix of 9 and then a pause:
dial-peer voice 10 potsprefix 9,session protocol
To establish a session protocol for calls between the local and remote routers via the packet network, use the session protocol dial-peer configuration command. Use the no form of this command to reset the default value for this command.
session protocol {smtp}
no session protocolSyntax Description
Defaults
smtp
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
For this release, SMTP is the only available session protocol.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following example selects SMTP as the session protocol:
dial-peer voice 10 mmoipsession protocol smtpsession target
To specify a network-specific address for a specified dial peer, use the session target dial peer configuration command. Use the no form of this command to restore the default value.
session target {mailto:{name | $d$}@domain-name | ipv4:destination-address | dns:[$s$. | $d$. | $u$. | $e$.] host-name | loopback:rtp | loopback:compressed | loopback:uncompressed}
no session targetSyntax Description
Defaults
The default for this command is enabled with no IP address or domain name defined.
Command Modes
Dial peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the session target command to specify a network-specific address or domain name for a dial peer. Whether you select a network-specific address or a domain name depends on the session protocol you select. The syntax of this command complies with the simple syntax of mailto as described in RFC 1738.
Use the session target mailto to deliver fax-mail to multiple recipients by specifying an email alias as the name argument and have that alias expanded by the mailer.
The session target loopback command is used for testing the voice transmission path of a call. The loopback point will depend on the call origination and the loopback type selected.
The session target dns command can be used with or without the specified wildcards. Using the optional wildcards can reduce the number of VoIP dial peer session targets you need to configure if you have groups of numbers associated with a particular router.
This command applies to on-ramp Store and Forward Fax functions.
Examples
The following example configures a session target using dns for a host, "voice_router," in the domain "cisco.com":
dial-peer voice 10 voipsession target dns:voice_router.cisco.comThe following example configures a session target using DNS, with the optional $u$. wildcard. In this example, the destination pattern has been configured to allow for any four-digit extension, beginning with the numbers 1310222. The optional wildcard $u$. indicates that the router will use the unmatched portion of the dialed number—in this case, the four-digit extension, to identify the dial peer. As in the previous example, the domain is "cisco.com."
dial-peer voice 10 voipdestination-pattern 1310222....session target dns:$u$.cisco.comThe following example configures a session target using DNS, with the optional $d$. wildcard. In this example, the destination pattern has been configured for 13105551111. The optional wildcard $d$. indicates that the router will use the destination pattern to identify the dial peer in the "cisco.com" domain.
dial-peer voice 10 voipdestination-pattern 13105551111session target dns:$d$.cisco.comThe following example delivers fax-mail to multiple recipients:
dial-peer voice 10 mmoipsession target marketing-information@mailer.example.comAssuming that mailer.example.com is running sendmail, you can put the following information into its /etc/aliases file:
marketing-information:john@example.com,fax=+14085551212@sj-offramp.example.comshow call active
To show active call information for a fax transmission in progress, use the show call active fax privileged EXEC command.
show call active {voice | fax}
no show call active {voice | fax}Syntax Description
voice
Specifies that the active call table displays voice call information.
fax
Specifies that the active call table displays fax call information.
Command Modes
Privileged EXEC
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
Use the show call active privileged EXEC command to display the contents of the active call table. If you use the voice keyword, the active call table displays information about all of the voice calls currently connected through the router or access server. If you use the fax keyword, the active call table shows all of the fax calls currently connected through the router.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following is sample output from the show call active voice command:
router# show call active voiceGENERIC:SetupTime=179388054 msIndex=1PeerAddress=+5....PeerSubAddress=PeerId=5PeerIfIndex=32LogicalIfIndex=29ConnectTime=179389793 msCallState=4CallOrigin=2ChargedUnits=0InfoType=2TransmitPackets=532TransmitBytes=10640ReceivePackets=147ReceiveBytes=2940TELE:ConnectionId=[0xE3EA3FF8 0xFF6D0105 0x0 0x6AEC71E4]TxDuration=23230 msVoiceTxDuration=2940 msFaxTxDuration=0 msCoderTypeRate=g729r8NoiseLevel=-84ACOMLevel=20OutSignalLevel=-66InSignalLevel=-66InfoActivity=2ERLLevel=20SessionTarget=GENERIC:SetupTime=179388237 msIndex=1PeerAddress=+3622PeerSubAddress=PeerId=3PeerIfIndex=31LogicalIfIndex=0ConnectTime=179389793 msCallState=4CallOrigin=1ChargedUnits=0InfoType=2TransmitPackets=143TransmitBytes=2860ReceivePackets=580ReceiveBytes=11600VOIP:ConnectionId[0xE3EA3FF8 0xFF6D0105 0x0 0x6AEC71E4]RemoteIPAddress=172.24.96.200RemoteUDPPort=16422RoundTripDelay=37 msSelectedQoS=best-effortSessionProtocol=ciscoSessionTarget=ipv4:172.24.96.200OnTimeRvPlayout=9920GapFillWithSilence=0 msGapFillWithPrediction=0 msGapFillWithInterpolation=0 msGapFillWithRedundancy=0 msHiWaterPlayoutDelay=70 msLoWaterPlayoutDelay=30 msReceiveDelay=30 msVAD = enabledCoderTypeRate=g729r8The following is sample output from the show call active fax brief command:
router# show call active fax brief<ID>: <start>hs.<index> +<connect> pid:<peer_id> <dir> <addr> <state> \tx:<packets>/<bytes> rx:<packets>/<bytes> <state>IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>delay:<last>/<min>/<max>ms <codec>FR <protocol> [int dlci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)Tele <int>: tx:<tot>/<v>/<fax>ms <codec> noise:<l> acom:<l> i/o:<l>/<l> dBm1 : 22021hs.1 +2263 pid:0 Answer wook song activetx:0/0 rx:0/41190IP 0.0.0.0 AcceptedMime:2 DiscardedMime:11 : 23193hs.1 +1091 pid:3469 Originate 527.... activetx:10/13838 rx:0/0Tele : tx:31200/10910/20290ms noise:-1 acom:-1 i/0:0/0 dBmThe following is sample output from the show call active fax command:
router# show call active faxGENERIC:SetupTime=22021 msIndex=1PeerAddress=wook songPeerSubAddress=PeerId=0PeerIfIndex=0LogicalIfIndex=0ConnectTime=24284CallState=4CallOrigin=2ChargedUnits=0InfoType=10TransmitPackets=0TransmitBytes=0ReceivePackets=0ReceiveBytes=41190MMOIP:ConnectionId[0x37EC7F41 0xB0110001 0x0 0x35C34]RemoteIPAddress=0.0.0.0SessionProtocol=SMTPSessionTarget=MessageId=AccountId=ImgEncodingType=MHImgResolution=fineAcceptedMimeTypes=2DiscardedMimeTypes=1Notification=NoneGENERIC:SetupTime=23193 msIndex=1PeerAddress=527....PeerSubAddress=PeerId=3469PeerIfIndex=157LogicalIfIndex=30ConnectTime=24284CallState=4CallOrigin=1ChargedUnits=0InfoType=10TransmitPackets=5TransmitBytes=6513ReceivePackets=0ReceiveBytes=0TELE:ConnectionId=[0x37EC7F41 0xB0110001 0x0 0x35C34]TxDuration=24010 msFaxTxDuration=10910 msFaxRate=14400NoiseLevel=-1ACOMLevel=-1OutSignalLevel=0InSignalLevel=0InfoActivity=0ERLLevel=-1SessionTarget=ImgPages=0provides an alphabetical listing of the show call active fields and a description of each field.
Related Commands
show call history
To display the fax call history table for a fax transmission, use the show call history fax privileged EXEC command.
show call history {voice | fax} [last number | brief]
no show call history {voice | fax} [last number | brief]Syntax Description
Command Modes
Privileged EXEC
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
The fax call history table contains a listing of all fax calls connected through this router in descending time order since Store and Forward Fax was enabled. You can display subsets of the fax call history table by using specific keywords. To display the last calls connected through this router, use the keyword last, and define the number of calls to be displayed with the argument number. To display a truncated version of the call history table, use the brief keyword.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Examples
The following is sample output from the show call history voice command:
router# show call history voice brief<ID>: <start>hs.<index> +<connect> +<disc> pid:<peer_id> <direction> <addr>tx:<packets>/<bytes> rx:<packets>/<bytes> <disc-cause>(<text>)IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms delay:<last>/<min>/<max>ms <codec>Telephony <int>: tx:<tot>/<voice>/<fax>ms <codec> noise:<lvl>dBm acom:<lvl>dBm234 : 158305740hs.1280 +241 +9199 pid:0 Answer +3...tx:3804/76080 rx:1358/27160 10 (normal call clearing.)IP 172.24.96.200:16468 rtt:33ms pl:25990/0ms delay:30/30/70ms g729r8234 : 158305745hs.1281 +236 +9195 pid:6 Originate +68888tx:1358/27160 rx:3804/76080 10 (normal call clearing.)Telephony 0:D:22: tx:91850/76080/0ms g729r8 noise:-84dBm acom:20dBm235 : 158344850hs.1282 +230 +28773 pid:0 Answer +3...tx:11063/221260 rx:4604/92080 10 (normal call clearing.)IP 172.24.96.200:16474 rtt:41ms pl:88260/290ms delay:40/30/130ms g729r8235 : 158344856hs.1283 +224 +28769 pid:6 Originate +68888tx:4604/92080 rx:11063/221260 10 (normal call clearing.)Telephony 0:D:22: tx:287590/221280/0ms g729r8 noise:-75dBm acom:20dBmThe following is sample output from the show call history fax brief command:
router# show call history fax brief<ID>: <start>hs.<index> +<connect> +<disc> pid:<peer_id> <direction> <addr>tx:<packets>/<bytes> rx:<packets>/<bytes> <disc-cause>(<text>)IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>delay:<last>/<min>/<max>ms <codec>Telephony <int>: tx:<tot>/<voice>/<fax>ms <codec> noise:<lvl>dBm acom:<lvl>dBm2 : 5996450hs.25 +-1 +3802 pid:100 Answer 408tx:0/0 rx:0/0 1F (T30 T1 EOM timeout)Telephony : tx:38020/38020/0ms g729r8 noise:0dBm acom:0dBm2 : 5996752hs.26 +-1 +3500 pid:110 Originate uut1@linux2.allegro.comtx:0/0 rx:0/0 3F (The e-mail was not sent correctly. Remote SMTP server said: 354 )IP 14.0.0.1 AcceptedMime:0 DiscardedMime:03 : 6447851hs.27 +1111 +3616 pid:310 Originate 576341.tx:11/14419 rx:0/0 10 (Normal connection)Telephony : tx:36160/11110/25050ms g729r8 noise:115dBm acom:-14dBm3 : 6447780hs.28 +1182 +4516 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:04 : 6464816hs.29 +1050 +3555 pid:310 Originate 576341.tx:11/14413 rx:0/0 10 (Normal connection)Telephony : tx:35550/10500/25050ms g729r8 noise:115dBm acom:-14dBm4 : 6464748hs.30 +1118 +4517 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:05 : 6507900hs.31 +1158 +2392 pid:100 Answer 4085763413tx:0/0 rx:3/3224 10 (Normal connection)Telephony : tx:23920/11580/12340ms g729r8 noise:0dBm acom:0dBm5 : 6508152hs.32 +1727 +2140 pid:110 Originate uut1@linux2.allegro.comtx:0/2754 rx:0/0 3F (service or option not available, unspecified)IP 14.0.0.4 AcceptedMime:0 DiscardedMime:06 : 6517176hs.33 +1079 +3571 pid:310 Originate 576341.tx:11/14447 rx:0/0 10 (Normal connection)Telephony : tx:35710/10790/24920ms g729r8 noise:115dBm acom:-14dBm6 : 6517106hs.34 +1149 +4517 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:07 : 6567382hs.35 +1054 +3550 pid:310 Originate 576341.tx:11/14411 rx:0/0 10 (Normal connection)Telephony : tx:35500/10540/24960ms g729r8 noise:115dBm acom:-14dBm7 : 6567308hs.36 +1128 +4517 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:0The following is output from the show call history command.
router# show call history fax l 2GENERIC:SetupTime=23193 msIndex=1PeerAddress=527....PeerSubAddress=PeerId=3469PeerIfIndex=157LogicalIfIndex=30DisconnectCause=10DisconnectText=normal call clearing.: Normal connectionConnectTime=24284DisconectTime=31288CallOrigin=1ChargedUnits=0InfoType=faxTransmitPackets=62TransmitBytes=88047ReceivePackets=0ReceiveBytes=0TELE:ConnectionId=[0x37EC7F41 0xB0110001 0x0 0x35C34]TxDuration=80950 msFaxTxDuration=10910 msFaxRate=14400NoiseLevel=-1ACOMLevel=-1SessionTarget=ImgPages=3GENERIC:SetupTime=22021 msIndex=2PeerAddress=wook songPeerSubAddress=PeerId=0PeerIfIndex=0LogicalIfIndex=0DisconnectCause=10DisconnectText=normal call clearing.ConnectTime=24284DisconectTime=31545CallOrigin=2ChargedUnits=0InfoType=faxTransmitPackets=0TransmitBytes=0ReceivePackets=0ReceiveBytes=41190MMOIP:ConnectionId[0x37EC7F41 0xB0110001 0x0 0x35C34]RemoteIPAddress=0.0.0.0SessionProtocol=SMTPSessionTarget=MessageId=AccountId=ImgEncodingType=MHImgResolution=fineAcceptedMimeTypes=2DiscardedMimeTypes=1Notification=Noneprovides an alphabetical listing of the fields for the show call history command and a description of each field.
Related Commands
show call active fax
Shows active call information for a fax transmission in progress.
shutdown (dial peer)
To change the administrative state of the selected dial peer from up to down, use the shutdown dial-peer configuration command. Use the no form of this command to change the administrative state of this dial peer from down to up.
shutdown
no shutdownSyntax Description
This command has no arguments or keywords.
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced.
12.0(4)T
This command was modified for Store and Forward Fax.
Usage Guidelines
When a dial peer is shut down, you cannot initiate calls to that peer.
This command applies to both on-ramp and off-ramp Store and Forward Fax functions.
Example
The following example changes the administrative state of MMoIP dial peer 10 to down:
configure terminaldial-peer voice 10shutdownThe following example changes the administrative state of MMoIP dial peer 10 to up:
configure terminaldial-peer voice 10no shutdownRelated Commands
dial-peer voice
Enters the dial-peer configuration mode, define the type of dial peer, and define the dial-peer tag number.
Debug Commands
This section documents new debug commands. All other debug commands used with this feature are documented in the Cisco IOS Release 12.0 Debug Command Reference.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
debug fax receive all
Use the debug fax receive all EXEC command to display Class 2 fax tracing information on all on-ramp fax connections. Use the no form of this command to disable debugging output.
[no] debug fax receive all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following example displays output from the debug fax receive all command. This command, by definition, displays Class 2 information about all on-ramp fax calls as they occur; in this example, only one fax call is being traced.
router# debug fax receive allAll fax receptions debugging is onrouter#The following output shows that a fax call has come in to the on-ramp gateway, and the on-ramp gateway is verifying calling number (the transmitter), the called number (the receiver) and identifying the appropriate on-ramp dial peer.
*Jan 2 194033.945 csm_check_accept_fax_call calling=4085553414 called=5550847, peer found*Jan 2 194033.945 ftsp_onramp_new_call new call, calling=4085553414, called=5550847A fax record is created for TTY line 19.
*Jan 2 194033.949 create_fax_record tty19*Jan 2 194033.949 ftsp_ind_call tty19, peer_tag=400, callid=0x48Class 2 modem tracing begins, showing that the modem is being initialized.
*Jan 2 194033.949 000000.000 AA*Jan 2 194034.001 000000.052 TT*Jan 2 194034.057 000000.108 Q0E0S0=0OKClass 2 modem tracing continues.
*Jan 2 194034.057 000000.108 OK*Jan 2 194037.325 000003.376RING000003.376 AT-C0T105*Jan 2 194037.333 000003.384OK*Jan 2 194037.333 000003.384 ATT106*Jan 2 194037.337 000003.388OKlTE AT+FCLASS=2*Jan 2 194037.345 000003.396OK000003.396 +FDCC=..;+FBOR=*Jan 2 194037.357 000003.412OK000003.412 AT+FLID*Jan 2 194037.365 000003.416OKATX3DT;*Jan 2 194040.281 000006.332OKIn the following output, the on-ramp gateway is about to present a dial tone to the user.
about to play dial-toneIn the following output, the on-ramp gateway receives digits form the caller.
*Jan 2 194043.105 000009.156 0 Digit 0*Jan 2 194043.241 000009.292 1 Digit 1*Jan 2 194043.389 000009.440 2 Digit 2*Jan 2 194043.541 000009.592 3 Digit 3*Jan 2 194043.693 000009.744 4 Digit 4*Jan 2 194043.841 000009.892 5 Digit 5*Jan 2 194044.005 000010.056 6 Digit 6*Jan 2 194044.153 000010.204 7 Digit 7*Jan 2 194044.305 000010.356 8 Digit 8*Jan 2 194044.441 000010.492 9 Digit 9*Jan 2 194044.605 000010.656 0 Digit 0*Jan 2 194044.741 000010.792 1 Digit 1*Jan 2 194044.905 000010.956 2 Digit 2*Jan 2 194045.041 000011.092 3 Digit 3*Jan 2 194045.193 000011.244 4 Digit 4*Jan 2 194045.341 000011.392 5 Digit 5*Jan 2 194045.493 000011.544 6 Digit 6*Jan 2 194045.641 000011.692 7 Digit 7*Jan 2 194045.793 000011.844 8 Digit 8*Jan 2 194045.941 000011.992 9 Digit 9*Jan 2 194046.093 000012.144 # Digit #*Jan 2 194046.241 000012.292 1 Digit 1*Jan 2 194046.393 000012.444 4 Digit 4*Jan 2 194046.541 000012.592 0 Digit 0*Jan 2 194046.693 000012.744 8 Digit 8*Jan 2 194046.841 000012.892 5 Digit 5*Jan 2 194046.993 000013.044 7 Digit 7*Jan 2 194047.141 000013.192 1 Digit 1*Jan 2 194047.305 000013.356 0 Digit 0*Jan 2 194047.441 000013.492 8 Digit 8*Jan 2 194047.605 000013.656 4 Digit 4*Jan 2 194047.741 000013.792 7 Digit 7*Jan 2 194058.393 000024.444+FCONThe following output shows that the fax call is connected from the on-ramp router to the calling party. Class 2 modem tracing continues.
+FTSI +31 703712194"1d19h %FTSP-6-FAX_CONNECT Reception*Jan 2 194058.393 RxPhaseA CONNECT*Jan 2 194058.393 CollectDTMF tty=19, ftsp set time=15723604,con time=15726049,tx dur=24450 Redialer Serial Number 01234567890123456789*Jan 2 194058.393 ftsp_onramp_match_digits tty19, redialer in use*Jan 2 194058.393 ftsp_onramp_match_digits destPat(5710847), matched(7), tag(401)target (mailtotest@nt4server.allegro.com) RxPhaseB RxTSI*Jan 2 194058.665 000024.716+FDCS0,3,0,2,0,0,0,5RxPhaseB RxDCS*Jan 2 194100.641 000026.692OKRxPhaseB OK PhB000026.692 AT+FDR*Jan 2 194101.949 000028.000+FCFR+FDCS0,3,0,2,0,0,0,5RxPhaseB Rx CFRRxPhaseB RxDCS*Jan 2 194102.573 000028.624CONNECTRxPhaseB RxConRxPhaseC000028.624DC2*Jan 2 194130.761 000056.812+FPTS1,0+FET2OKRxPhaseD RxFPTSRxPhaseD MCFRxPhaseD MODEM_FET*Jan 2 194130.761 RxPhaseD tty=19,ensp set time=15726049,con time=15729286 RxPhaseD Rx EOPRxPhaseD MODEM_OK000056.812 AT+FDRThe following output shows that the fax transmission is complete.
*Jan 2 194133.469 000059.520+FHNG00RxPhaseE Received Hangup Call complete*Jan 2 194133.533 000059.584OKRxPhaseE Received OK Ending CallThe following output shows that the calling party disconnects following fax transmission.
1d19h %FTSP-6-FAX_DISCONNECT Reception*Jan 2 194133.533 fap_onramp_end_call disconnect-1d19h %LINK-3-UPDOWN Interface Serial10, changed state to down*Jan 2 194134.537 all booleans set*Jan 2 194134.537 ftsp_do_call_history disc cause=16, Normal connection delete_f_rec() calling free()Related Commands
debug fax receive called-number
Use the debug fax receive called-number EXEC command to display Class 2 fax tracing information about on-ramp connections filtered on a particular called number. Use the no form of this command to disable debugging output.
[no] debug fax receive called-number {string}
Syntax Description
string
Specifies the called telephone number. Valid entries are any series of digits that specify the E.164 telephone number.
Defaults
Disabled
Command History
Examples
Note
The following example displays output from the debug fax receive called-number command. In this example, Store and Forward Fax displays Class 2 information about all on-ramp fax calls for the called number 555-0847.
router# debug fax receive specificrouter# debug fax receive called-number 5550847All fax receptions debugging is onrouter#The following output shows that a fax call has come in to the on-ramp gateway, and the on-ramp gateway is verifying the calling number (the transmitter), the called number (the receiver), and identifying the appropriate on-ramp dial peer.
*Jan 2 194033.945 csm_check_accept_fax_call calling=4085553414 called=5550847, peer found*Jan 2 194033.945 ftsp_onramp_new_call new call, calling=4085553414, called=5550847A fax record is created for TTY line 19.
*Jan 2 194033.949 create_fax_record tty19*Jan 2 194033.949 ftsp_ind_call tty19, peer_tag=400, callid=0x48Class 2 modem tracing begins, showing that the modem is being initialized.
*Jan 2 194033.949 000000.000 AA*Jan 2 194034.001 000000.052 TT*Jan 2 194034.057 000000.108 Q0E0S0=0OKClass 2 modem tracing continues.
*Jan 2 194034.057 000000.108 OK*Jan 2 194037.325 000003.376RING000003.376 AT-C0T105*Jan 2 194037.333 000003.384OK*Jan 2 194037.333 000003.384 ATT106*Jan 2 194037.337 000003.388OKlTE AT+FCLASS=2*Jan 2 194037.345 000003.396OK000003.396 +FDCC=..;+FBOR=*Jan 2 194037.357 000003.412OK000003.412 AT+FLID*Jan 2 194037.365 000003.416OKATX3DT;*Jan 2 194040.281 000006.332OKIn the following output, the on-ramp gateway is about to present a dial tone to the user.
about to play dial-toneIn the following output, the on-ramp gateway receives digits form the caller.
*Jan 2 194043.105 000009.156 0 Digit 0*Jan 2 194043.241 000009.292 1 Digit 1*Jan 2 194043.389 000009.440 2 Digit 2*Jan 2 194043.541 000009.592 3 Digit 3*Jan 2 194043.693 000009.744 4 Digit 4*Jan 2 194043.841 000009.892 5 Digit 5*Jan 2 194044.005 000010.056 6 Digit 6*Jan 2 194044.153 000010.204 7 Digit 7*Jan 2 194044.305 000010.356 8 Digit 8*Jan 2 194044.441 000010.492 9 Digit 9*Jan 2 194044.605 000010.656 0 Digit 0*Jan 2 194044.741 000010.792 1 Digit 1*Jan 2 194044.905 000010.956 2 Digit 2*Jan 2 194045.041 000011.092 3 Digit 3*Jan 2 194045.193 000011.244 4 Digit 4*Jan 2 194045.341 000011.392 5 Digit 5*Jan 2 194045.493 000011.544 6 Digit 6*Jan 2 194045.641 000011.692 7 Digit 7*Jan 2 194045.793 000011.844 8 Digit 8*Jan 2 194045.941 000011.992 9 Digit 9*Jan 2 194046.093 000012.144 # Digit #*Jan 2 194046.241 000012.292 1 Digit 1*Jan 2 194046.393 000012.444 4 Digit 4*Jan 2 194046.541 000012.592 0 Digit 0*Jan 2 194046.693 000012.744 8 Digit 8*Jan 2 194046.841 000012.892 5 Digit 5*Jan 2 194046.993 000013.044 7 Digit 7*Jan 2 194047.141 000013.192 1 Digit 1*Jan 2 194047.305 000013.356 0 Digit 0*Jan 2 194047.441 000013.492 8 Digit 8*Jan 2 194047.605 000013.656 4 Digit 4*Jan 2 194047.741 000013.792 7 Digit 7*Jan 2 194058.393 000024.444+FCONThe following output shows that the fax call is connected from the on-ramp router to the calling party. Class 2 modem tracing continues.
+FTSI +31 703712194"1d19h %FTSP-6-FAX_CONNECT Reception*Jan 2 194058.393 RxPhaseA CONNECT*Jan 2 194058.393 CollectDTMF tty=19, ftsp set time=15723604,con time=15726049,tx dur=24450 Redialer Serial Number 01234567890123456789*Jan 2 194058.393 ftsp_onramp_match_digits tty19, redialer in use*Jan 2 194058.393 ftsp_onramp_match_digits destPat(5710847), matched(7), tag(401)target (mailtotest@nt4server.allegro.com) RxPhaseB RxTSI*Jan 2 194058.665 000024.716+FDCS0,3,0,2,0,0,0,5RxPhaseB RxDCS*Jan 2 194100.641 000026.692OKRxPhaseB OK PhB000026.692 AT+FDR*Jan 2 194101.949 000028.000+FCFR+FDCS0,3,0,2,0,0,0,5RxPhaseB Rx CFRRxPhaseB RxDCS*Jan 2 194102.573 000028.624CONNECTRxPhaseB RxConRxPhaseC000028.624DC2*Jan 2 194130.761 000056.812+FPTS1,0+FET2OKRxPhaseD RxFPTSRxPhaseD MCFRxPhaseD MODEM_FET*Jan 2 194130.761 RxPhaseD tty=19,ensp set time=15726049,con time=15729286 RxPhaseD Rx EOPRxPhaseD MODEM_OK000056.812 AT+FDRThe following output shows that the fax transmission is complete.
*Jan 2 194133.469 000059.520+FHNG00RxPhaseE Received Hangup Call complete*Jan 2 194133.533 000059.584OKRxPhaseE Received OK Ending CallThe following output shows that the calling party disconnects following fax transmission.
1d19h %FTSP-6-FAX_DISCONNECT Reception*Jan 2 194133.533 fap_onramp_end_call disconnect-1d19h %LINK-3-UPDOWN Interface Serial10, changed state to down*Jan 2 194134.537 all booleans set*Jan 2 194134.537 ftsp_do_call_history disc cause=16, Normal connection delete_f_rec() calling free()Related Commands
debug fax receive calling-number
Use the debug fax receive calling-number EXEC command to display Class 2 fax tracing information about on-ramp connections filtering on a particular calling number. Use the no form of this command to disable debugging output.
[no] debug fax receive calling-number {string}
Syntax Description
string
Specifies the calling telephone number. Valid entries are any series of digits that specify the E.164 telephone number.
Defaults
Disabled
Command History
Examples
Note
The following example displays output from the debug fax receive calling-number command. In this example, Store and Forward Fax displays Class 2 information about all on-ramp fax calls for the calling number 408 555-3414.
router# debug fax receive specificrouter# debug fax receive calling-number 4085553414All fax receptions debugging is onrouter#The following output shows that a fax call has come in to the on-ramp gateway, and the on-ramp gateway is verifying the calling number (the transmitter), the called number (the receiver) and identifying the appropriate on-ramp dial peer.
*Jan 2 194033.945 csm_check_accept_fax_call calling=4085553414 called=5550847, peer found*Jan 2 194033.945 ftsp_onramp_new_call new call, calling=4085553414, called=5550847A fax record is created for TTY line 19.
*Jan 2 194033.949 create_fax_record tty19*Jan 2 194033.949 ftsp_ind_call tty19, peer_tag=400, callid=0x48Class 2 modem tracing begins, showing that the modem is being initialized.
*Jan 2 194033.949 000000.000 AA*Jan 2 194034.001 000000.052 TT*Jan 2 194034.057 000000.108 Q0E0S0=0OKClass 2 modem tracing continues.
*Jan 2 194034.057 000000.108 OK*Jan 2 194037.325 000003.376RING000003.376 AT-C0T105*Jan 2 194037.333 000003.384OK*Jan 2 194037.333 000003.384 ATT106*Jan 2 194037.337 000003.388OKlTE AT+FCLASS=2*Jan 2 194037.345 000003.396OK000003.396 +FDCC=..;+FBOR=*Jan 2 194037.357 000003.412OK000003.412 AT+FLID*Jan 2 194037.365 000003.416OKATX3DT;*Jan 2 194040.281 000006.332OKIn the following output, the on-ramp gateway is about to present a dial tone to the user.
about to play dial-toneIn the following output, the on-ramp gateway receives digits form the caller.
*Jan 2 194043.105 000009.156 0 Digit 0*Jan 2 194043.241 000009.292 1 Digit 1*Jan 2 194043.389 000009.440 2 Digit 2*Jan 2 194043.541 000009.592 3 Digit 3*Jan 2 194043.693 000009.744 4 Digit 4*Jan 2 194043.841 000009.892 5 Digit 5*Jan 2 194044.005 000010.056 6 Digit 6*Jan 2 194044.153 000010.204 7 Digit 7*Jan 2 194044.305 000010.356 8 Digit 8*Jan 2 194044.441 000010.492 9 Digit 9*Jan 2 194044.605 000010.656 0 Digit 0*Jan 2 194044.741 000010.792 1 Digit 1*Jan 2 194044.905 000010.956 2 Digit 2*Jan 2 194045.041 000011.092 3 Digit 3*Jan 2 194045.193 000011.244 4 Digit 4*Jan 2 194045.341 000011.392 5 Digit 5*Jan 2 194045.493 000011.544 6 Digit 6*Jan 2 194045.641 000011.692 7 Digit 7*Jan 2 194045.793 000011.844 8 Digit 8*Jan 2 194045.941 000011.992 9 Digit 9*Jan 2 194046.093 000012.144 # Digit #*Jan 2 194046.241 000012.292 1 Digit 1*Jan 2 194046.393 000012.444 4 Digit 4*Jan 2 194046.541 000012.592 0 Digit 0*Jan 2 194046.693 000012.744 8 Digit 8*Jan 2 194046.841 000012.892 5 Digit 5*Jan 2 194046.993 000013.044 7 Digit 7*Jan 2 194047.141 000013.192 1 Digit 1*Jan 2 194047.305 000013.356 0 Digit 0*Jan 2 194047.441 000013.492 8 Digit 8*Jan 2 194047.605 000013.656 4 Digit 4*Jan 2 194047.741 000013.792 7 Digit 7*Jan 2 194058.393 000024.444+FCONThe following output shows that the fax call is connected from the on-ramp router to the calling party. Class 2 modem tracing continues.
+FTSI +31 703712194"1d19h %FTSP-6-FAX_CONNECT Reception*Jan 2 194058.393 RxPhaseA CONNECT*Jan 2 194058.393 CollectDTMF tty=19, ftsp set time=15723604,con time=15726049,tx dur=24450 Redialer Serial Number 01234567890123456789*Jan 2 194058.393 ftsp_onramp_match_digits tty19, redialer in use*Jan 2 194058.393 ftsp_onramp_match_digits destPat(5710847), matched(7), tag(401)target (mailtotest@nt4server.allegro.com) RxPhaseB RxTSI*Jan 2 194058.665 000024.716+FDCS0,3,0,2,0,0,0,5RxPhaseB RxDCS*Jan 2 194100.641 000026.692OKRxPhaseB OK PhB000026.692 AT+FDR*Jan 2 194101.949 000028.000+FCFR+FDCS0,3,0,2,0,0,0,5RxPhaseB Rx CFRRxPhaseB RxDCS*Jan 2 194102.573 000028.624CONNECTRxPhaseB RxConRxPhaseC000028.624DC2*Jan 2 194130.761 000056.812+FPTS1,0+FET2OKRxPhaseD RxFPTSRxPhaseD MCFRxPhaseD MODEM_FET*Jan 2 194130.761 RxPhaseD tty=19,ensp set time=15726049,con time=15729286 RxPhaseD Rx EOPRxPhaseD MODEM_OK000056.812 AT+FDRThe following output shows that the fax transmission is complete.
*Jan 2 194133.469 000059.520+FHNG00RxPhaseE Received Hangup Call complete*Jan 2 194133.533 000059.584OKRxPhaseE Received OK Ending CallThe following output shows that the calling party disconnects following fax transmission.
1d19h %FTSP-6-FAX_DISCONNECT Reception*Jan 2 194133.533 fap_onramp_end_call disconnect-1d19h %LINK-3-UPDOWN Interface Serial10, changed state to down*Jan 2 194134.537 all booleans set*Jan 2 194134.537 ftsp_do_call_history disc cause=16, Normal connection delete_f_rec() calling free()Related Commands
debug fax receive specific
Use the debug fax receive specific EXEC command to enable Class 2 fax protocol tracing information for on-ramp activities to be filtered using either a calling or called number. Use the no form of this command to disable filtering debugging output.
[no] debug fax receive specific
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
Note
The following example displays output from the debug fax receive calling-number command, which is enabled using the debug fax receive specific command. In this example, Store and Forward Fax displays Class 2 information about all on-ramp fax calls for the calling number 408 555-3414.
router# debug fax receive specificrouter# debug fax receive calling-number 4085553414All fax receptions debugging is onrouter#The following output shows that a fax call has come in to the on-ramp gateway, and the on-ramp gateway is verifying the calling number (the transmitter), the called number (the receiver) and identifying the appropriate on-ramp dial peer.
*Jan 2 194033.945 csm_check_accept_fax_call calling=4085553414 called=5550847, peer found*Jan 2 194033.945 ftsp_onramp_new_call new call, calling=4085553414, called=5550847A fax record is created for TTY line 19.
*Jan 2 194033.949 create_fax_record tty19*Jan 2 194033.949 ftsp_ind_call tty19, peer_tag=400, callid=0x48Class 2 modem tracing begins, showing that the modem is being initialized.
*Jan 2 194033.949 000000.000 AA*Jan 2 194034.001 000000.052 TT*Jan 2 194034.057 000000.108 Q0E0S0=0OKClass 2 modem tracing continues.
*Jan 2 194034.057 000000.108 OK*Jan 2 194037.325 000003.376RING000003.376 AT-C0T105*Jan 2 194037.333 000003.384OK*Jan 2 194037.333 000003.384 ATT106*Jan 2 194037.337 000003.388OKlTE AT+FCLASS=2*Jan 2 194037.345 000003.396OK000003.396 +FDCC=..;+FBOR=*Jan 2 194037.357 000003.412OK000003.412 AT+FLID*Jan 2 194037.365 000003.416OKATX3DT;*Jan 2 194040.281 000006.332OKIn the following output, the on-ramp gateway is about to present a dial tone to the user.
about to play dial-toneIn the following output, the on-ramp gateway receives digits form the caller.
*Jan 2 194043.105 000009.156 0 Digit 0*Jan 2 194043.241 000009.292 1 Digit 1*Jan 2 194043.389 000009.440 2 Digit 2*Jan 2 194043.541 000009.592 3 Digit 3*Jan 2 194043.693 000009.744 4 Digit 4*Jan 2 194043.841 000009.892 5 Digit 5*Jan 2 194044.005 000010.056 6 Digit 6*Jan 2 194044.153 000010.204 7 Digit 7*Jan 2 194044.305 000010.356 8 Digit 8*Jan 2 194044.441 000010.492 9 Digit 9*Jan 2 194044.605 000010.656 0 Digit 0*Jan 2 194044.741 000010.792 1 Digit 1*Jan 2 194044.905 000010.956 2 Digit 2*Jan 2 194045.041 000011.092 3 Digit 3*Jan 2 194045.193 000011.244 4 Digit 4*Jan 2 194045.341 000011.392 5 Digit 5*Jan 2 194045.493 000011.544 6 Digit 6*Jan 2 194045.641 000011.692 7 Digit 7*Jan 2 194045.793 000011.844 8 Digit 8*Jan 2 194045.941 000011.992 9 Digit 9*Jan 2 194046.093 000012.144 # Digit #*Jan 2 194046.241 000012.292 1 Digit 1*Jan 2 194046.393 000012.444 4 Digit 4*Jan 2 194046.541 000012.592 0 Digit 0*Jan 2 194046.693 000012.744 8 Digit 8*Jan 2 194046.841 000012.892 5 Digit 5*Jan 2 194046.993 000013.044 7 Digit 7*Jan 2 194047.141 000013.192 1 Digit 1*Jan 2 194047.305 000013.356 0 Digit 0*Jan 2 194047.441 000013.492 8 Digit 8*Jan 2 194047.605 000013.656 4 Digit 4*Jan 2 194047.741 000013.792 7 Digit 7*Jan 2 194058.393 000024.444+FCONThe following output shows that the fax call is connected from the on-ramp router to the calling party. Class 2 modem tracing continues.
+FTSI +31 703712194"1d19h %FTSP-6-FAX_CONNECT Reception*Jan 2 194058.393 RxPhaseA CONNECT*Jan 2 194058.393 CollectDTMF tty=19, ftsp set time=15723604,con time=15726049,tx dur=24450 Redialer Serial Number 01234567890123456789*Jan 2 194058.393 ftsp_onramp_match_digits tty19, redialer in use*Jan 2 194058.393 ftsp_onramp_match_digits destPat(5710847), matched(7), tag(401)target (mailtotest@nt4server.allegro.com) RxPhaseB RxTSI*Jan 2 194058.665 000024.716+FDCS0,3,0,2,0,0,0,5RxPhaseB RxDCS*Jan 2 194100.641 000026.692OKRxPhaseB OK PhB000026.692 AT+FDR*Jan 2 194101.949 000028.000+FCFR+FDCS0,3,0,2,0,0,0,5RxPhaseB Rx CFRRxPhaseB RxDCS*Jan 2 194102.573 000028.624CONNECTRxPhaseB RxConRxPhaseC000028.624DC2*Jan 2 194130.761 000056.812+FPTS1,0+FET2OKRxPhaseD RxFPTSRxPhaseD MCFRxPhaseD MODEM_FET*Jan 2 194130.761 RxPhaseD tty=19,ensp set time=15726049,con time=15729286 RxPhaseD Rx EOPRxPhaseD MODEM_OK000056.812 AT+FDRThe following output shows that the fax transmission is complete.
*Jan 2 194133.469 000059.520+FHNG00RxPhaseE Received Hangup Call complete*Jan 2 194133.533 000059.584OKRxPhaseE Received OK Ending CallThe following output shows that the calling party disconnects following fax transmission.
1d19h %FTSP-6-FAX_DISCONNECT Reception*Jan 2 194133.533 fap_onramp_end_call disconnect-1d19h %LINK-3-UPDOWN Interface Serial10, changed state to down*Jan 2 194134.537 all booleans set*Jan 2 194134.537 ftsp_do_call_history disc cause=16, Normal connection delete_f_rec() calling free()Related Commands
debug fax send all
Use the debug fax send all EXEC command to display Class 2 fax protocol tracing information for all off-ramp faxing activities. Use the no form of this command to disable debugging output.
[no] debug fax send all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following example displays output from the debug fax send all command. This command, by definition, displays Class 2 information about all off-ramp fax calls as they occur; in this example, only one fax call is being traced.
router# debug fax send allThe following output shows that the off-ramp gateway is placing a fax call.
*Jan 1 175435.703 ftsp_offramp_match_digits phone number to translate 5553413*Jan 1 175435.703 destPat(5553413), matched(6), prefix() peer_tag(310)*Jan 1 175435.703 ftsp_offramp_match_digits target 5763413*Jan 1 175435.743 fap_offcm tty(72), Got dial message000000.000 AT&F\Q0S7=255Class 2 modem tracing begins, including modem initialization.
000000.080 A000000.096 T000000.128 &F000000.144 \Q000000.160 0S7=255000000.160OKIn the following output, Class 2 modem tracing continues.
000000.160 E0V1000000.192 A000000.192 TE000000.208 0000000.208OK000000.208AT+FCLASS=2000000.288OK000000.288 +FDCC=..;+FBOR=000000.368OK000000.368 AT+FLID000000.432OKThe following output shows that the off-ramp gateway is dialing out.
000000.432 ATDTW5553413*Jan 1 175436.419 ftsp_setup_for_oc tty72, callid=0x1C*Jan 1 175436.419 ftsp_setup_for_oc ctl=2, cas grp=-1, snmp_ix=102*Jan 1 175436.419 ftsp_off_ramp_active_call_init tty72 callid=0x1C,The following output identifies the SMNP index of the off-ramp device.
snmp_ix=102000011.784+FCONPhase A StartThe following output shows that the called party has answered and that the fax transmission is beginning. Class 2 modem tracing continues.
175449 %FTSP-6-FAX_CONNECT Transmission*Jan 1 175447.527 TxPhaseA MODEM_FCON000012.524+FNSFB5 00 2E 57 46 58 3A 37 2E 30Phase B StartTxPhaseB MODEM_FNSF000013.276+FCSI" Allegro Fax machine"Phase B StartTxPhaseB MODEM_FCSI000013.756+FDIS1,5,0,2,3,0,1,0OKPhase B StartTxPhaseB MODEM_FDISTxPhaseB MODEM_OK*Jan 1 175449.499 TxPhaseB, tty(72), Tx Speed=14400bps*Jan 1 175449.499 000013.756 AT+FDIS000013.820OKPhase B StartTxPhaseB MODEM_OK000013.820 AT+FDT000020.704+FDCS0,5,0,2,0,0,0,0Phase B StartTxPhaseB MODEM_FDCS*Jan 1 175456.447 calc_min_line_bytes normal resolution000021.280CONNECTPhase B StartTxPhaseB MODEM_CONNECT000021.296Phase C StartTxPhaseC MODEM_XON*Jan 1 175457.139 asfax_txservice tty(72), MPS b000024.788OKTx Phase D StartTxPhaseD MODEM_OKTx Phase D MPS000027.128+FPTS1OKTx Phase D StartTxPhaseD MODEM_FPTSRxFPTS +FPTS1TxPhaseD MCFTxPhaseD MPSPhase C StartTxPhaseC MODEM_OK000027.768CONNECTPhase C StartTxPhaseC MODEM_CONNECT000027.784Phase C StartTxPhaseC MODEM_XON*Jan 1 175503.687 asfax_txservice tty(72), EOP000032.444OKTx Phase D StartTxPhaseD MODEM_OKTx Phase D EOP000034.716+FPTS1Tx Phase D StartTxPhaseD MODEM_FPTSRxFPTS +FPTS1TxPhaseD MCFEnabling smtp for receiving data, body_page_number 2, body_page_number_sent 1000036.272+FHNG0TxPhaseE MODEM_FHNG000036.832OKTxPhaseE MODEM_OKThe following output shows that the fax transmission is complete.
175514 %FTSP-6-FAX_DISCONNECT Transmission*Jan 1 175512.575 tty(72) fax transmit done175514 %LINK-3-UPDOWN Interface Serial222, changed state to downRelated Commands
debug fax send calling-number
Use the debug fax send calling-number EXEC command to display information for a particular outbound calling number. Use the no form of this command to disable debugging output.
[no] debug fax send calling-number {string}
Syntax Description
string
Specifies the telephone number to which the fax transmission was sent. Valid entries are any series of digits that specify the E.164 telephone number.
Defaults
Disabled
Command History
Examples
Note
The following example displays output from the debug fax send calling-number command. In this example, Store and Forward Fax displays Class 2 information about all off-ramp fax calls for the calling number 555-3414.
router# debug fax send specificrouter# debug fax send calling-number 5553413The following output shows that the off-ramp gateway is placing a fax call.
*Jan 1 175435.703 ftsp_offramp_match_digits phone number to translate 5553413*Jan 1 175435.703 destPat(5553413), matched(6), prefix() peer_tag(310)*Jan 1 175435.703 ftsp_offramp_match_digits target 5553413*Jan 1 175435.743 fap_offcm tty(72), Got dial message000000.000 AT&F\Q0S7=255Class 2 modem tracing begins, including modem initialization.
000000.080 A000000.096 T000000.128 &F000000.144 \Q000000.160 0S7=255000000.160OKIn the following output, Class 2 modem tracing continues.
000000.160 E0V1000000.192 A000000.192 TE000000.208 0000000.208OK000000.208AT+FCLASS=2000000.288OK000000.288 +FDCC=..;+FBOR=000000.368OK000000.368 AT+FLID000000.432OKThe following output shows that the off-ramp gateway is dialing out.
000000.432 ATDTW5553413*Jan 1 175436.419 ftsp_setup_for_oc tty72, callid=0x1C*Jan 1 175436.419 ftsp_setup_for_oc ctl=2, cas grp=-1, snmp_ix=102*Jan 1 175436.419 ftsp_off_ramp_active_call_init tty72 callid=0x1C,The following output identifies the SMNP index of the off-ramp device.
snmp_ix=102000011.784+FCONPhase A StartThe following output shows that the called party has answered and that the fax transmission is beginning. Class 2 modem tracing continues.
175449 %FTSP-6-FAX_CONNECT Transmission*Jan 1 175447.527 TxPhaseA MODEM_FCON000012.524+FNSFB5 00 2E 57 46 58 3A 37 2E 30Phase B StartTxPhaseB MODEM_FNSF000013.276+FCSI" Allegro Fax machine"Phase B StartTxPhaseB MODEM_FCSI000013.756+FDIS1,5,0,2,3,0,1,0OKPhase B StartTxPhaseB MODEM_FDISTxPhaseB MODEM_OK*Jan 1 175449.499 TxPhaseB, tty(72), Tx Speed=14400bps*Jan 1 175449.499 000013.756 AT+FDIS000013.820OKPhase B StartTxPhaseB MODEM_OK000013.820 AT+FDT000020.704+FDCS0,5,0,2,0,0,0,0Phase B StartTxPhaseB MODEM_FDCS*Jan 1 175456.447 calc_min_line_bytes normal resolution000021.280CONNECTPhase B StartTxPhaseB MODEM_CONNECT000021.296Phase C StartTxPhaseC MODEM_XON*Jan 1 175457.139 asfax_txservice tty(72), MPS b000024.788OKTx Phase D StartTxPhaseD MODEM_OKTx Phase D MPS000027.128+FPTS1OKTx Phase D StartTxPhaseD MODEM_FPTSRxFPTS +FPTS1TxPhaseD MCFTxPhaseD MPSPhase C StartTxPhaseC MODEM_OK000027.768CONNECTPhase C StartTxPhaseC MODEM_CONNECT000027.784Phase C StartTxPhaseC MODEM_XON*Jan 1 175503.687 asfax_txservice tty(72), EOP000032.444OKTx Phase D StartTxPhaseD MODEM_OKTx Phase D EOP000034.716+FPTS1Tx Phase D StartTxPhaseD MODEM_FPTSRxFPTS +FPTS1TxPhaseD MCFEnabling smtp for receiving data, body_page_number 2, body_page_number_sent 1000036.272+FHNG0TxPhaseE MODEM_FHNG000036.832OKTxPhaseE MODEM_OKThe following output shows that the fax transmission is complete.
175514 %FTSP-6-FAX_DISCONNECT Transmission*Jan 1 175512.575 tty(72) fax transmit done175514 %LINK-3-UPDOWN Interface Serial222, changed state to downRelated Commands
debug fax send specific
Use the debug fax send specific EXEC command to enable filtering information on an outbound calling number. Use the no form of this command to disable debugging output.
[no] debug fax send specific
Syntax Description
This command uses no arguments or keywords.
Defaults
Disabled
Command History
Examples
Note
The following example displays output from the debug fax send calling-number command, which has been enabled by using the debug fax send specific command. In this example, Store and Forward Fax displays Class 2 information about all off-ramp fax calls for the calling number 555-3414.
router# debug fax send specificrouter# debug fax send calling-number 5553414The following output shows that the off-ramp gateway is placing a fax call.
*Jan 1 175435.703 ftsp_offramp_match_digits phone number to translate 5553413*Jan 1 175435.703 destPat(5553413), matched(6), prefix() peer_tag(310)*Jan 1 175435.703 ftsp_offramp_match_digits target 5763413*Jan 1 175435.743 fap_offcm tty(72), Got dial message000000.000 AT&F\Q0S7=255Class 2 modem tracing begins, including modem initialization.
000000.080 A000000.096 T000000.128 &F000000.144 \Q000000.160 0S7=255000000.160OKIn the following output, Class 2 modem tracing continues.
000000.160 E0V1000000.192 A000000.192 TE000000.208 0000000.208OK000000.208AT+FCLASS=2000000.288OK000000.288 +FDCC=..;+FBOR=000000.368OK000000.368 AT+FLID000000.432OKThe following output shows that the off-ramp gateway is dialing out.
000000.432 ATDTW5553413*Jan 1 175436.419 ftsp_setup_for_oc tty72, callid=0x1C*Jan 1 175436.419 ftsp_setup_for_oc ctl=2, cas grp=-1, snmp_ix=102*Jan 1 175436.419 ftsp_off_ramp_active_call_init tty72 callid=0x1C,The following output identifies the SMNP index of the off-ramp device.
snmp_ix=102000011.784+FCONPhase A StartThe following output shows that the called party has answered and that the fax transmission is beginning. Class 2 modem tracing continues.
175449 %FTSP-6-FAX_CONNECT Transmission*Jan 1 175447.527 TxPhaseA MODEM_FCON000012.524+FNSFB5 00 2E 57 46 58 3A 37 2E 30Phase B StartTxPhaseB MODEM_FNSF000013.276+FCSI" Allegro Fax machine"Phase B StartTxPhaseB MODEM_FCSI000013.756+FDIS1,5,0,2,3,0,1,0OKPhase B StartTxPhaseB MODEM_FDISTxPhaseB MODEM_OK*Jan 1 175449.499 TxPhaseB, tty(72), Tx Speed=14400bps*Jan 1 175449.499 000013.756 AT+FDIS000013.820OKPhase B StartTxPhaseB MODEM_OK000013.820 AT+FDT000020.704+FDCS0,5,0,2,0,0,0,0Phase B StartTxPhaseB MODEM_FDCS*Jan 1 175456.447 calc_min_line_bytes normal resolution000021.280CONNECTPhase B StartTxPhaseB MODEM_CONNECT000021.296Phase C StartTxPhaseC MODEM_XON*Jan 1 175457.139 asfax_txservice tty(72), MPS b000024.788OKTx Phase D StartTxPhaseD MODEM_OKTx Phase D MPS000027.128+FPTS1OKTx Phase D StartTxPhaseD MODEM_FPTSRxFPTS +FPTS1TxPhaseD MCFTxPhaseD MPSPhase C StartTxPhaseC MODEM_OK000027.768CONNECTPhase C StartTxPhaseC MODEM_CONNECT000027.784Phase C StartTxPhaseC MODEM_XON*Jan 1 175503.687 asfax_txservice tty(72), EOP000032.444OKTx Phase D StartTxPhaseD MODEM_OKTx Phase D EOP000034.716+FPTS1Tx Phase D StartTxPhaseD MODEM_FPTSRxFPTS +FPTS1TxPhaseD MCFEnabling smtp for receiving data, body_page_number 2, body_page_number_sent 1000036.272+FHNG0TxPhaseE MODEM_FHNG000036.832OKTxPhaseE MODEM_OKThe following output shows that the fax transmission is complete.
175514 %FTSP-6-FAX_DISCONNECT Transmission*Jan 1 175512.575 tty(72) fax transmit done175514 %LINK-3-UPDOWN Interface Serial222, changed state to downRelated Commands
debug fmail client
Use the debug fmail client command to display e-mail parameters (such as Mail from and Envelope to and Envelope from) as well as the progress of the SMTP client. Use the no form of this command to disable debugging output.
[no] debug fmail client
Syntax Description
This command uses no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following example shows how the debug fmail client command traces the component that communicates with the SMTP client on the on-ramp Cisco AS5300.
router# debug fmail clientIn the following output, the fax-mail client is trying to establish a session with an e-mail server.
*Jan 1 18:04:39.419: fmccm: tty(1), establishing a connection*Jan 1 18:04:39.419: fmccm tty(1): Envelope to: uut1@linux2.allegro.com*Jan 1 18:04:39.419: fmccm tty(1), Mail from user name is fully specified*Jan 1 18:04:39.419: fmccm: tty(1), Envelope from: FAX=4085763413@allegrouut1.allegro.comIn the following output, the fax-mail client opens a session with e-mail server.
*Jan 1 18:04:39.423: fmccm: Opening connection with email host 14.0.0.4*Jan 1 18:04:39.423: ensp_ind_call: tty1 peer_tag=110 onRamp18:04:50: %FTSP-6-FAX_CONNECT: Reception18:05:01: %FTSP-6-FAX_DISCONNECT: Reception*Jan 1 18:04:59.043: fm_cpd:: tty(1),Received TIFF_PAGE_READY messagfm_cpd:: tty(1), Received TIFF_PAGE_READY message*Jan 1 18:04:59.043: fm_cpd:: tty(1),END_OF_FAX_PAGE received*Jan 1 18:04:59.043: fm_cpd:: tty(1),Received TIFF_PAGE_READY messagfm_cpd:: tty(1), Received TIFF_PAGE_READY message18:05:01: %LINK-3-UPDOWN: Interface Serial2:0, changed state to down*Jan 1 18:05:00.831: fmcbfc: tty(1): esmtp response status 0*Jan 1 18:05:00.831: fmcbfc:: tty(1), Faxmail message id = 002D2000180439695@allegrouut1.allegro.com*Jan 1 18:05:00.831: fmcbfc: tty(1): Calling fap_onramp_process_boolean() for cleanup*Jan 1 18:05:00.831: ensp_do_call_history: disc cause=63, service or option not available, unspecifiedRelated Commands
debug fmail server
Use the debug fmail server EXEC command to display communication with the SMTP server. Use the no form of this command to disable debugging output.
[no] debug fmail server
Syntax Description
This command uses no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following output shows how the debug fmail server command provides information about cover-page generation and progress of the data that the off-ramp Cisco AS5300 is processing from the SMTP server.
router# debug fmail serverIn the following output, the off-ramp gateway receives an e-mail message from a mail server.
from uut1@linux2.allegro.com, ph#in fax=5553413*Jan 1 175725.383 decode_minaddr (pstn fax=5553413)*Jan 1 175725.383 decode_minaddr Fax Number5553413*Jan 1 175725.383 decode_minaddr phone string returned [5763413]tel_number_dial 5763413*Jan 1 175725.383 create fax payload*Jan 1 175725.383 ensp_ind_call offRamp*Jan 1 175725.383 Entering faxmail_server_new_recipient()*Jan 1 175725.383 envelope_to 35, [fax=5763413@allegrouut1.allegro.com]*Jan 1 175725.383 allocate_modem mica_last_used 72*Jan 1 175725.383 allocate_modem microcom_last_used 0*Jan 1 175725.383 statbits 10420In the following output, the off-ramp gateway looks for a free modem.
*Jan 1 175725.383 statbits2 5*Jan 1 175725.383 statbits 10420*Jan 1 175725.383 statbits2 5*Jan 1 175725.383 statbits 10420*Jan 1 175725.383 statbits2 5*Jan 1 175725.383 statbits 10420*Jan 1 175725.383 statbits2 5*Jan 1 175725.383 statbits 10420*Jan 1 175725.387 statbits2 5*Jan 1 175725.387 statbits 10020*Jan 1 175725.387 statbits2 1In the following output, the off-ramp gateway finds and seizes an available MICA modem.
*Jan 1 175725.387 allocate_modem found a mica modem*Jan 1 175725.391 allocate_modem seizing modem 72*Jan 1 175725.391 create_fax_record tty72*Jan 1 175725.391 cover page is enabled for fax=5763413@allegrouut1.allegro.com*Jan 1 175725.391 fax_record->tel_number_dial 5763413*Jan 1 175725.391 Total rcpt so far 1rfc_payload->envelope_from 24, [uut1@linux2.allegro.com]In the following output, the off-ramp gateway matches the MMoIP dial peer information.
*Jan 1 175725.399 ensp_offramp_match_digits destPat(5763413), matched(6), tag(300)target ()*Jan 1 175725.399 decode_minaddr (pstn fax=5763413@allegrouut1.allegro.com)*Jan 1 175725.399 decode_minaddr Fax Number5763413*Jan 1 175725.399 decode_minaddr phone string returned [5763413]from_personal_name 4, [uut1]cover_page_from1 8, ["uut1", ]*Jan 1 175725.399 >>> from_raw 23, [uut1@linux2.allegro.com]*Jan 1 175725.399 Non-digit character encountered [u]cover_page_from2 [uut1@linux2.allegro.com]In the following output, the off-ramp gateway displays the data included in the Store and Forward Fax-generated cover page.
//Cover page--------------------------------------------------------------------------------Title: This is the offrampTo: 5553413From: "uut1", uut1@linux2.allegro.comDate: Thu, 21 Jan 1999 10:44:21 -0800Subject: test--------------------------------------------------------------------------------]*Jan 1 17:57:25.399: Calling text2fax_data_handler for cover page*Jan 1 17:57:25.411: Returned buffer length: 1548 (mime != text)*Jan 1 17:57:25.411: faxmail_server_put_buffer: buffer_info == BUFF_END_OF_PART*Jan 1 17:57:25.415: Returned buffer length: 1548 (mime != text)*Jan 1 17:57:25.415: faxmail_server_put_buffer: buffer_info == BUFF_END_OF_PART*Jan 1 17:57:25.415: Returned buffer length: 624 (mime == text)*Jan 1 17:57:25.415: faxmail_server_put_buffer: buffer_info == BUFF_END_OF_PART*Jan 1 17:57:25.415: [test]*Jan 1 17:57:25.415: Calling text2fax_data_handler - TEXT_BODY_PAGE*Jan 1 17:57:25.431: Authentication bypassed....not enabledIn the following output, the off-ramp gateway places the call to the receiving fax machine.
*Jan 1 17:57:25.431: Sending dial messages now*Jan 1 17:57:25.431: faxmail_server_send_dial_message to fap 5763413*Jan 1 17:57:25.431: send DIAL*Jan 1 17:57:25.535: Returned buffer length: 1548 (mime != text)*Jan 1 17:57:25.535: faxmail_server_put_buffer: buffer_info == BUFF_END_OF_PART*Jan 1 17:57:25.535: Returned buffer length: 624 (mime == text)*Jan 1 17:57:25.535: Got a page with only returns and newline's - setting buffer_length=0*Jan 1 17:57:25.535: faxmail_server_put_buffer: buffer_info == BUFF_END_OF_PART*Jan 1 17:57:25.535: []*Jan 1 17:57:25.535: Calling text2fax_data_handler - TEXT_BODY_PAGE*Jan 1 17:57:25.535: Returned buffer length: 1548 (mime != text)*Jan 1 17:57:25.539: Returned buffer length: 1548 (mime != text)*Jan 1 17:57:25.547: Returned buffer length: 1548 (mime != text)*Jan 1 17:57:25.551: Returned buffer length: 1548 (mime != text)*Jan 1 17:57:25.555: faxmail_server_put_buffer: buffer_info == BUFF_END_OF_PART*Jan 1 17:57:25.555: Returned buffer length: 624 (mime == text)*Jan 1 17:57:25.555: faxmail_server_put_buffer: buffer_info == BUFF_LAST*Jan 1 17:57:25.555: []*Jan 1 17:57:25.555: Calling text2fax_data_handler - TEXT_BODY_PAGE*Jan 1 17:57:25.555: Stopping smtp from receiving data, fax_payload->body_pages 2, body_page_number_sent 0*Jan 1 17:57:25.555: All reserved modems have been previous dialed.In the following output, the receiving fax machine answers the call from the off-ramp gateway.
17:57:38: %FTSP-6-FAX_CONNECT: TransmissionThe following output shows that the transmission is complete.
17:58:03: %FTSP-6-FAX_DISCONNECT: Transmission*Jan 1 17:58:01.619: Entering faxmail_server_fap_done(f_rec: 616EB70C, fmode: 5)faxmail_server_fap_done: status: 23, num_pages: 217:58:03: %LINK-3-UPDOWN: Interface Serial1:0, changed state to down*Jan 1 17:58:10.559: ensp_do_call_history: disc cause=16, normal call clearing.*Jan 1 17:58:10.559: Remove fax_record from Q..., frec 616EB70C*Jan 1 17:58:10.559: delete_f_rec(): calling free()*Jan 1 17:58:10.559: fax_record 616EB70C is deleted*Jan 1 17:58:10.559: Entering faxmail_server_dispose_context (todelete fax_payload: 0x612B4B40)*Jan 1 17:58:10.559: delete_f_rec(): calling free()*Jan 1 17:58:10.559: delete_fax_payload: fax_payload freed !!!Related Commands
debug fmail client
Displays e-mail parameters (such as Mail from and Envelope to and Envelope from) as well as the progress of the SMTP client.
debug mmoip aaa
Use the debug mmoip aaa EXEC command to display output relating to AAA services with Store and Forward Fax. Use the no form of this command to disable debugging output.
[no] debug mmoip aaa
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following output shows how the debug mmoip aaa command provides information about AAA on-ramp or off-ramp authentication:
router# debug mmoip aaa5d10h:fax_aaa_begin_authentication:User-Name = mmoip-b.cisco.com5d10h:fax_aaa_begin_authentication:fax_account_id_origin = GATEWAY_ID5d10h:fax_aaa_end_authentication_callback:Authentication successfulThe following output shows how the debug mmoip aaa command provides information about AAA off-ramp accounting:
router# debug mmoip aaa5d10h:fax_aaa_start_accounting:User-Name = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:Calling-Station-Id = gmercuri@mail-server.cisco.com5d10h:fax_aaa_start_accounting:Called-Station-Id = fax=571-0839@mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:fax_account_id_origin = GATEWAY_IDmmoip-b#ax_aaa_start_accounting:fax_msg_id = <37117AF3.3D98300E@mail-server.cisco.com>5d10h:fax_aaa_start_accounting:fax_pages = 25d10h:fax_aaa_start_accounting:fax_coverpage_flag = TRUE5d10h:fax_aaa_start_accounting:fax_modem_time = 26/325d10h:fax_aaa_start_accounting:fax_connect_speed = 14400bps5d10h:fax_aaa_start_accounting:fax_recipient_count = 15d10h:fax_aaa_start_accounting:fax_auth_status = USER SUCCESS5d10h:fax_aaa_start_accounting:gateway_id = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:call_type = Fax Send5d10h:fax_aaa_start_accounting:port_used = slot:0 modem port:05d10h:fax_aaa_do_offramp_accounting tty(6), Stopping accounting5d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveTransmitBytes = 180385d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveTransmitPackets = 14The following output shows how the debug mmoip aaa command provides information about AAA on-ramp accounting:
router# debug mmoip aaa5d10h:fax_aaa_start_accounting:User-Name = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:Calling-Station-Id = FAX=408@mail-from-hostname.com5d10h:fax_aaa_start_accounting:Called-Station-Id = FAX=5710839@mail-server.cisco.com5d10h:fax_aaa_start_accounting:fax_account_id_origin = GATEWAY_ID5d10h:fax_aaa_start_accounting:fax_msg_id = 00391997233216263@mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:fax_pages = 25d10h:fax_aaa_start_accounting:fax_modem_time = 22/325d10h:fax_aaa_start_accounting:fax_connect_speed = 14400bps5d10h:fax_aaa_start_accounting:fax_auth_status = USER SUCCESS5d10h:fax_aaa_start_accounting:email_server_address = 1.14.116.15d10h:fax_aaa_start_accounting:email_server_ack_flag = TRUE5d10h:fax_aaa_start_accounting:gateway_id = mmoip-b.cisco.com5d10h:fax_aaa_start_accounting:call_type = Fax Receive5d10h:fax_aaa_start_accounting:port_used = Cisco Powered Fax System slot:1 port:45d10h:fax_aaa_do_onramp_accounting tty(5), Stopping accounting5d10h:fax_aaa_stop_accounting:endb->cact->generic.callActiveTransmitBytes = 266875d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveReceiveBytes = 185585d10h:fax_aaa_stop_accounting:ftdb->cact->generic.callActiveReceivePackets = 14debug mmoip send email
Use the debug mmoip send email EXEC command to test connectivity between the on-ramp gateway and the e-mail server by sending a test e-mail to a specified e-mail address. Use the no form of this command to disable debugging output.
[no] debug mmoip send email {string}
Syntax Description
Defaults
Disabled
Command History
Examples
The debug mmoip send email command is used to test connectivity between the on-ramp gateway and the e-mail server. Basically, this debug command sends an e-mail message to the recipient specified in the e-mail address string. There is no specific output associated with the debug mmoip send email command; to see how the on-ramp gateway and e-mail server interact when processing the test e-mail message, enable the debug fmail client command.
The following example tests connectivity between the on-ramp gateway and the e-mail server by sending a test e-mail message to ilya@mail-server.com.
router# debug fmail clientrouter# debug mmoip send email ilya@mail-server.comrouter#01:22:59:faxmail_client_send_test:Sending the test message toilya@mail-server.com from testing@mmoip-a.cisco.com...01:22:59:faxmail_client_send_test:Opening client engine.01:22:59:faxmail_client_send_test:Sending 59 bytes ...01:22:59:faxmail_client_send_test:Done sending test email.debug mmoip send fax
Use the debug mmoip send fax EXEC command to send an off-ramp test fax. Use the no form of this command to disable debugging output.
[no] debug mmoip send fax{string}
Syntax Description
Defaults
Disabled
Command History
Examples
The debug mmoip send fax command is used to test connectivity between the off-ramp gateway and a recipient fax device. Basically, this debug command sends a test fax transmission to the recipient specified in the telephone number string. There is no specific output associated with the debug mmoip send fax command; to see how the off-ramp gateway and fax device interact when processing the test fax, enable the debug fax send all command.
The following example sends a test fax message to the telephone number 5550839:
router# debug fax send allrouter# debug mmoip send fax 5550839The following output shows that the off-ramp gateway is placing a fax call.
01:28:18:ftsp_offramp_match_digits:phone number to translate:555083901:28:18: destPat(5......), matched(1), prefix() peer_tag(1)01:28:18:ftsp_offramp_match_digits:target:71083901:28:18:fap_offcm:tty(4), Got dial message00:00:00.000:AT&F\Q0S7=255Class 2 modem tracing begins, including modem initialization.
00:00:00.008:AA00:00:00.068:TT00:00:00.128:&F\Q0S7=25500:00:00.128:OK00:00:00.128:E0V100:00:00.140:ATE0OK00:00:00.140:AT+FCLASS=200:00:00.148:OK00:00:00.148:+FDCC=..;+FBOR=00:00:00.168:AT+FLID00:00:00.180:OK00:00:00.180:ATDTW710839The following output shows that the fax transmission is complete; in this particular example, there was a transmission error, and the modem timed out.
01:28:25:ftsp_setup_for_oc:tty4, callid=0xA01:28:25:ftsp_setup_for_oc ctl=0, cas grp=-1, snmp_ix=3001:28:25:ftsp_off_ramp_active_call_init tty4 callid=0xA, snmp_ix=3001:29:18:fap_offpmt:tty(4), TxPhaseA:modem timeout01:29:18:%FTSP-6-FAX_DISCONNECT:Transmission errordebug mmoip transfer
Use the debug mmoip transfer EXEC command to send output of the TIFF writer to a TFTP server. Use the no form of this command to disable debugging output.
[no] debug mmoip transfer {prefix-filename tftp-server-name}
Syntax Description
Defaults
Disabled
Command History
Examples
The debug mmoip transfer sends the content of the fax data received to the TFTP server named by the tftp-server-name variable into the file identified by the prefix-filename variable. Each page of the fax transmission is a separate file, designated by the letter p, followed by the page number.
For example, the following command transfers the received fax content to a TFTP server named keyer. The first page of the transmission goes to the file /tftpboot/test/testp1.tiff, the second page goes to the file named /tftpboot/test/testp2.tiff and so on.
router# debug mmoip transfer /tftpboot/test/test keyerThe named files must exist on the TFTP server and be writable for the debug operation to be successful.
debug mta receive all
Use the debug mta receive all EXEC command to show output relating to the activity on the SMTP server. Use the no form of this command to disable debugging output.
[no] debug mta receive all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following example shows the messages exchanged (for example, the handshake) between the e-mail server and the off-ramp gateway.
router# debug mta receive all#R: 'Received: from win98pc2 (win98pc2.allegro.com [14.0.0.11]) by nt4server.allegro.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)'R: ' id C321SPKM; Thu, 7 Jan 1999 11:51:32 -0800'R: 'Message-ID: <00ff01be3a76$be0c9480$0b00000e@win98pc2.allegro.com>'R: 'From: "test" <test@nt4server.allegro.com>'R: 'To: <fax=5763413@allegrouut1.allegro.com>'R: 'Subject: test for debug.....'R: 'Date: Thu, 7 Jan 1999 11:48:47 -0800'R: 'MIME-Version: 1.0'R: 'Content-Type: multipart/alternative;'R: ' boundary="----=_NextPart_000_00FC_01BE3A33.AFB6F9E0"'R: 'X-Priority: 3'R: 'X-MSMail-Priority: Normal'R: 'X-Mailer: Microsoft Outlook Express 4.72.3110.1'R: 'X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3'R: ''R: 'This is a multi-part message in MIME format.'Unrecognized/handled MIME content type rejectedR: ''R: '------=_NextPart_000_00FC_01BE3A33.AFB6F9E0'R: 'Content-Type: text/plain;'R: ' charset="iso-8859-1"'The following output specifies the encoding type.
R: 'Content-Transfer-Encoding: quoted-printable'R: ''R: 'test for debug......'The following output shows the transmission of the encoded text data.
R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: 'HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH'R: ''R: '------=_NextPart_000_00FC_01BE3A33.AFB6F9E0'R: 'Content-Type: text/html;'R: ' charset="iso-8859-1"'R: 'Content-Transfer-Encoding: quoted-printable'The following output shows the transmission of the HTML encoded data.
R: ''R: '<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">'Unrecognized/handled MIME content type rejectedR: '<HTML>'R: '<HEAD>'R: ''R: '<META content=3Dtext/html;charset=3Diso-8859-1 ='R: 'http-equiv=3DContent-Type>'R: '<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>'R: '</HEAD>'R: '<BODY bgColor=3D#ffffff>'R: '<DIV><FONT color=3D#000000 size=3D2>test for debug......</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000 size=3D2>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000 size=3D2>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000 size=3D2>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000 size=3D2>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000 size=3D2>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000 size=3D2>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000 size=3D2>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV>'R: '<DIV><FONT color=3D#000000=20'R: 'size=3D2>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH='R: '</FONT></DIV></FONT></DIV></FONT></DIV></FONT></DIV></FONT></DIV></FONT><='R: '/DIV></FONT></DIV></FONT></DIV></BODY></HTML>'R: ''R: '------=_NextPart_000_00FC_01BE3A33.AFB6F9E0--'R: ''The following output shows that the transmission is complete.
R: '.'Found the terminating Dot!Related Commands
debug mta send all
Use the debug mta send all EXEC command to display output for all of the on-ramp client connections. Use the no form of this command to disable debugging output.
[no] debug mta send all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
This display shows the messages exchanged (for example, the handshake) between the e-mail server and the on-ramp gateway.
router# debug mta send allAll email send debugging is onrouter#The following output shows that the calling party is connected to the on-ramp router. R specifies the information received from the mail server. S specifies the messages sent from the on-ramp gateway to the mail server.
1d19h: %FTSP-6-FAX_CONNECT: Receptionsocket 0 attempting to connect to IP address 14.0.0.1socket 0 readable for first time - let's try to read itR: 220 nt4server.allegro.com ESMTP Server (Microsoft Exchange Internet Mail Service 5.5.1960.3) readyS: EHLO allegrouut1.allegro.comR: 250-nt4server.allegro.com supports the following extensions:R: 250-XEXCH50R: 250-HELPR: 250-ETRNR: 250-DSNR: 250-SIZE 0R: 250-AUTH=LOGINR: 250 TLSS: MAIL FROM:<FAX=4085763414@allegrouut1.allegro.com> RET=HDRSR: 250 OK - mail from <FAX=4085763414@allegrouut1.allegro.com>S: RCPT TO:<test@nt4server.allegro.com> NOTIFY=SUCCESS,FAILURE ORCPT=rfc822;FAX+3D4085763414@allegrouut1.allegro.comR: 250 OK - Recipient <test@nt4server.allegro.com>R: 354 Send data. End with CRLF.CRLFS: Received: (originator..... slot:1 port:16) by allegrouut1.allegro.com for <test@nt4server.allegro.com> (with Cisco NetWorks); Sun, 02 Jan 2000 19:30:56 +0000S: To: "14085710847" <test@nt4server.allegro.com>S: Message-ID: <00152000193056665@allegrouut1.allegro.com>S: Date: Sun, 02 Jan 2000 19:30:56 +0000S: Subject: onramp testS: X-Mailer: IOS (tm) 5300 Software (C5300-IS-M)S: MIME-Version: 1.0S: Content-Type: multipart/mixed;S: boundary="yradnuoB=_00142000193054321.allegrouut1allegro.com"1d19h: %FTSP-6-FAX_DISCONNECT: ReceptionS: From: "+31 703712194" <FAX=4085763414@allegrouut1.allegro.com>S: X-Account-Id: nullS: --yradnuoB=_00142000193054321.allegrouut1allegro.comS: Content-ID: <00162000193129665@allegrouut1.allegro.com>S: Content-Type: image/tiff; application=faxbwS: Content-Transfer-Encoding: base64writing lingering data for socket 0writing lingering data for socket 0writing lingering data for socket 0writing lingering data for socket 0writing lingering data for socket 0writing lingering data for socket 0writing lingering data for socket 0writing lingering data for socket 01d19h: %LINK-3-UPDOWN: Interface Serial1:0, changed state to downwriting lingering data for socket 0S: --yradnuoB=_00142000193054321.allegrouut1allegro.com--Sending terminating dot ...(socket=0)S: .R: 250 OKS: QUITThe following output shows that the fax transmission is complete.
R: 221 closing connectionFreeing SMTP ctx at 0x613C8620returned from work_routine, context freedRelated Commands
debug mta send rcpt-to
Use the debug mta send rcpt-to EXEC command to display output for a specific on-ramp SMTP client connection during an e-mail transmission. Use the no form of this command to disable debugging output.
[no] debug mta send rcpt-to{string}
Syntax Description
Defaults
Disabled
Command History
Examples
The following example shows debugging information displayed when the debug mmoip send email command has been enabled and the SMTP client is sending an e-mail message.
router# debug mta send allAll email send debugging is onrouter# debug mmoip send email ilyau@company.comrouter# socket 0 attempting to connect to IP address 172.69.95.82socket 0 readable for first time - let's try to read itR:220 quisp.cisco.com ESMTP Sendmail 8.8.4-Cisco.1/8.6.5 ready at Tue, 6Apr 1999 13:35:39 -0700 (PDT)S:EHLO mmoip-c.cisco.comR:250-quisp.cisco.com Hello [172.22.95.16], pleased to meet youR:250-EXPNR:250-VERBR:250-8BITMIMER:250-SIZER:250-DSNR:250-ETRNR:250-XUSRR:250 HELPS:MAIL FROM:<testing@> RET=HDRSR:250 <testing@>... Sender okS:RCPT TO:<ilyau@cisco.com> NOTIFY=SUCCESS ORCPT=rfc822;testing@R:250 <ilyau@cisco.com>... Recipient okR:354 Enter mail, end with "." on a line by itselfS:Received:(Cisco Powered Fax System) by mmoip-c.cisco.com for<ilyau@cisco.com> (with Cisco NetWorks); Fri, 17 Oct 1997 14:54:27 +0800S:To: <ilyau@cisco.com>S:Message-ID:<000F1997145427146@mmoip-c.cisco.com>S:Date:Fri, 17 Oct 1997 14:54:27 +0800S:Subject:mmoip-c subject hereS:X-Mailer:IOS (tm) 5300 Software (C5300-IS-M)S:MIME-Version:1.0S:Content-Type:multipart/mixed;S: boundary="yradnuoB=_000E1997145426826.mmoip-ccisco.com"S:From:"Test User" <testing@>S:--yradnuoB=_000E1997145426826.mmoip-ccisco.comS:Content-ID:<00101997145427150@mmoip-c.cisco.com>S:--yradnuoB=_000E1997145426826.mmoip-ccisco.com--Sending terminating dot ...(socket=0)S:.R:250 NAA09092 Message accepted for deliveryS:QUITR:221 quisp.cisco.com closing connectionFreeing SMTP ctx at 0x6121D454returned from work_routine, context freedRelated Commands
debug text-to-fax
Use the debug text-to-fax EXEC command to show information relating to the off-ramp text-to-fax conversion. Use the no form of this command to disable debugging output.
[no] debug text-to-fax
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following debug output shows the off-ramp text-to-fax conversion.
router# debug text-to-faxText to fax debugging is onrouter#6d03h: text2fax_data_handler: START_OF_CONNECTION6d03h: text2fax_data_handler: new_context6d03h: text2fax_data_handler: resolution: fine6d03h: text2fax_data_handler: buffer size: 506d03h: text2fax_put_buffer: START_OF_FAX_PAGE6d03h: text2fax_put_buffer: START_OF_FAX_PAGE6d03h: text2fax_put_buffer: END_OF_FAX_PAGE. Dial now ...if not in progress6d03h: text2fax_data_handler: START_OF_DATA6d03h: text2fax_data_handler: END_OF_DATA6d03h: text2fax_data_handler: Dispose context6d03h: text2fax_data_handler: START_OF_CONNECTION6d03h: text2fax_data_handler: END_OF_CONNECTION6d03h: %FTSP-6-FAX_CONNECT: Transmission6d03h: %FTSP-6-FAX_DISCONNECT: Transmission6d03h: %LINK-3-UPDOWN: Interface Serial1:22, changed state to downdebug tiff reader
Use the debug tiff reader EXEC command to display output about the off-ramp TIFF reader. Use the no form of this command to disable debugging output.
[no] debug tiff-reader
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following debug example displays information about the off-ramp TIFF reader.
router# debug tiff reader*Jan 1 18:59:13.683: tiff_reader_data_handler: new context*Jan 1 18:59:13.683: tiff_reader_data_handler: resolution: standard*Jan 1 18:59:13.683: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() ENGINE_START/DONE gggg(pl 616E9994)*Jan 1 18:59:13.691: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.699: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)*Jan 1 18:59:13.703: tiff_reader_put_buffer: START_OF_FAX_PAGEi>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.711: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.719: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.727: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.735: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.743: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.751: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.759: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.767: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.775: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.787: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.795: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.803: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.811: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.819: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.827: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.835: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.843: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.851: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.863: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.871: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.879: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.887: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.895: tiff_reader_data_handler: buffer size: 1524*Jan 1 18:59:13.903: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994)i>> tiff_reader_engine() case FAX_EBUFFER gggg*Jan 1 18:59:13.907: tiff_reader_data_handler: buffer size: 311i>> tiff_r_finish() END_OF_FAX_PAGE pppp*Jan 1 18:59:13.907: tiff_reader_put_buffer: END_OF_FAX_PAGE. Dial now ...if not in progress*Jan 1 18:59:13.907: tiff_reader_data_handler: END_OF_DATA*Jan 1 18:59:13.907: tiff_reader_data_handler: BUFF_END_OF_PART*Jan 1 18:59:13.907: tiff_reader_data_handler: Dispose contextRelated Commands
debug tiff writer
Use the debug tiff writer EXEC command to display output about the on-ramp TIFF writer. Use the no form of this command to disable debugging output.
[no] debug tiff-writer
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command History
Examples
The following debug example shows information about the off-ramp TIFF writer.
router# debug tiff writer*Jan 1 18:54:59.419: tiff_writer_data_process: START_OF_CONNECTION18:55:10: %FTSP-6-FAX_CONNECT: Reception*Jan 1 18:55:14.903: tiff_writer_data_process: START_OF_FAX_PAGE*Jan 1 18:55:14.903: tiff_writer_data_process: tiff file created = 2000:01:01 18:55:1418:55:21: %FTSP-6-FAX_DISCONNECT: Reception*Jan 1 18:55:19.039: tiff_writer_data_process: END_OF_CONNECTION or ABORT_CONNECTION*Jan 1 18:55:19.039: tiff_writer_put_buffer: END_OF_FAX_PAGE*Jan 1 18:55:19.039: send TIFF_PAGE_READY*Jan 1 18:55:19.039: send TIFF_PAGE_READY18:55:21: %LINK-3-UPDOWN: Interface Serial2:0, changed state to downRelated Commands
