|
|
This section documents new or modified commands M though Z. All other commands beginning with the letter M through Z used with this feature are documented in the Cisco IOS Release 12.0 command references.
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
number | Specifies the maximum number of connections for this dial peer. Valid values for this field are 1 to 2147483647. |
The no form of this command is the default, meaning unlimited number of connections.
Dial-peer configuration
| Release | Modification |
|---|---|
11.3(1)T | This command was introduced. |
12.0(4)T | This command was modified for Store and Forward Fax. |
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.
The following example configures the maximum number of connections for MMoIP dial peer 10 as 5:
dial-peer voice 10 mmoip max-conn 5
| Command | Description |
mta receive maximum-recipients | Specifies the maximum number of recipients for all SMTP connections. |
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.
mdnThis command has no arguments or keywords.
Disabled
Dial-peer configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following example requests that a message disposition notice be generated by the recipient:
dial-peer voice 10 mmoip mdn
| Command | Description |
mta receive generate-mdn | Specifies that the Cisco AS5300 acting as the off-ramp gateway will respond to a request for an MDN. |
mta send-return receipt-to hostname | Specifies the hostname address where MDNs are sent. |
mta send-return receipt-to username | Specifies the username address where MDNs are sent. |
To define a password to be used with CiscoSecure for Windows NT when using Store and Forward Fax, 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
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. |
No password defined.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following example defines a password (abercrombie) when CiscoSecure for Windows NT is used with Store and Forward Fax:
configure terminal mmoip aaa global-password abercrombie
To define the name of the method list to be used for AAA accounting with Store and Forward Fax, 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
method-list-name | Character string used to name a list of accounting methods to be used with Store and Forward Fax. |
No AAA accounting method list defined.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following example defines a AAA accounting method list (called sherman) to be used with Store and Forward Fax:
configure terminal aaa new-model mmoip aaa method fax accounting sherman
| Command | Description |
mmoip aaa receive-accounting enable | Enables on-ramp AAA accounting services. |
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
method-list-name | Character string used to name a list of authentication methods to be used with Store and Forward Fax. |
No AAA authentication method list defined.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following example defines a AAA authentication method list (called peabody) to be used with Store and Forward Fax:
configure terminal aaa new-model mmoip aaa method fax authentication peabody
| Command | Description |
mmoip aaa receive-authentication enable | Enables on-ramp AAA authentication services. |
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 enableThis command has no arguments or keywords.
Disabled
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
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 terminal aaa new-model mmoip aaa method fax accounting sherman aaa accounting connection sherman stop-only radius mmoip aaa receive-accounting enable
| Command | Description |
mmoip aaa method fax accounting | Defines the name of the method list to be used for AAA accounting with Store and Forward Fax. |
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 enableThis command has no arguments or keywords.
Disabled
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
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 terminal aaa new-model mmoip aaa method fax authentication peabody aaa authentication login peabody radius local mmoip aaa receive-authentication enable
| Command | Description |
mmoip aaa method fax authentication | Defines the name of the method list to be used for AAA authentication with Store and Forward Fax. |
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}
ani | Indicates that AAA uses the calling party telephone number (automatic number identification or ANI) as the AAA account identifier. |
dnis | Indicates that AAA uses the called party telephone number (dialed number identification service or DNIS) as the AAA account identifier. |
gateway | Indicates that AAA uses the router-specific name derived from the host name and domain name as the AAA account identifier, displayed in the following format: router-name.domain-name. |
redialer-id | Indicates that AAA uses the account string returned by the external redialer device as the AAA account identifier. In this case, the redialer ID is either the redialer serial number or the redialer account number. |
redialer-dnis | Indicates that AAA uses the called party telephone number (dialed number identification service or DNIS) as the AAA account identifier captured by the redialer if a redialer device is present. |
No account identification source is defined.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following example defines the DNIS captured by the redialer as the AAA authentication identifier for Store and Forward Fax:
configure terminal aaa new-model mmoip aaa receive-id primary redialer-dnis
| Command | Description |
mmoip aaa receive-id secondary | Specifies the primary location where AAA retrieves its account identification information for on-ramp faxing. |
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}
ani | Indicates that AAA uses the calling party telephone number (automatic number identification or ANI) as the AAA account identifier. |
dnis | Indicates that AAA uses the called party telephone number (dialed number identification service or DNIS) as the AAA account identifier. |
gateway | Indicates that AAA uses the router-specific name derived from the host name and domain name as the AAA account identifier, displayed in the following format: router-name.domain-name. |
redialer-id | Indicates that AAA uses the account string returned by the external redialer device as the AAA account identifier. In this case, the redialer ID is either the redialer serial number or the redialer account number. |
redialer-dnis | Indicates that AAA uses the called party telephone number (dialed number identification service or DNIS) as the AAA account identifier captured by the redialer if a redialer device is present. |
No account identification source is defined.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following example defines the DNIS captured by the redialer as the secondary AAA authentication identifier for Store and Forward Fax:
configure terminal aaa new-model mmoip aaa receive-id secondary redialer-dnis
| Command | Description |
mmoip aaa receive-id primary | Specifies the primary location where AAA retrieves its account identification information for on-ramp faxing. |
To enable off-ramp AAA accounting services, 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 enableThis command has no arguments or keywords.
Disabled
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
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 terminal aaa new-model mmoip aaa method fax accounting sherman aaa accounting connection sherman stop-only radius mmoip aaa send-accounting enable
| Command | Description |
mmoip aaa method fax accounting | Defines the name of the method list to be used for AAA accounting with Store and Forward Fax. |
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 enableThis command has no arguments or keywords.
Disabled
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
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 terminal aaa new-model mmoip aaa method fax authentication peabody aaa authentication login peabody radius local mmoip aaa send-authentication enable
| Command | Description |
mmoip aaa method fax authentication | Defines the name of the method list to be used for AAA authentication with Store and Forward Fax. |
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}
account-id | Indicates that AAA uses the account username from the originating fax-mail system as the AAA account identifier. This means the off-ramp gateway uses the account identifier in the x-account ID field of the e-mail header. The benefit of using this attribute offers end-to-end authentication and accounting tracking. |
envelope-from | Indicates that AAA uses the account username from the fax-mail header as the AAA account identifier. |
envelope-to | Indicates that AAA uses the recipient derived from the fax-mail header as the AAA account identifier. |
gateway | Indicates that AAA uses the router-specific name derived from the host name and domain name as the AAA account identifier, displayed in the following format: router-name.domain-name. |
No account identification source is defined.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
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 terminal aaa new-model mmoip aaa send-id primary envelope-to
| Command | Description |
mmoip aaa send-id secondary | Specifies the secondary location where AAA retrieves its account identification information for off-ramp faxing. |
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}
account-id | Indicates that AAA uses the account username from the originating fax-mail system as the AAA account identifier. This means the off-ramp gateway uses the account identifier in the x-account ID field of the e-mail header. The benefit of using this attribute offers end-to-end authentication and accounting tracking. |
envelope-from | Indicates that AAA uses the account username from the fax-mail header as the AAA account identifier. |
envelope-to | Indicates that AAA uses the recipient derived from the fax-mail header as the AAA account identifier. |
gateway | Indicates that AAA uses the router-specific name derived from the host name and domain name as the AAA account identifier, displayed in the following format: router-name.domain-name. |
No account identification source is defined.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
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 terminal aaa new-model mmoip aaa send-id secondary envelope-to
| Command | Description |
mmoip aaa send-id primary | Specifies the primary location where AAA retrieves its account identification information for off-ramp faxing |
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
string | Specifies the host name or IP address to be used as an alias for the SMTP server. If you specify an IP address to be used as an alias, you must enclose the IP address in brackets as follows: {xxx.xxx.xxx.xxx]. |
Enabled with an empty string
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
This command applies to on-ramp Store and Forward Fax functions.
The following example specifies the host name seattle-fax-offramp.example.com as the alias for the SMTP server:
configure terminal mta receive aliases seattle-fax-offramp.example.com
The following example specifies the host name 172.16.0.0 as the alias for the SMTP server:
configure terminal mta receive aliases [172.16.0.0]
| Command | Description |
mta receive generate-mdn | Specifies that the off-ramp gateway process a response message delivery notification (MDN) from an SMTP server. |
mta receive maximum-recipients | Defines the number of simultaneous SMTP recipients handled by the off-ramp gateway. |
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-mdnThis command has no arguments or keywords.
Disabled
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following enables the receiving device to generate message delivery notices:
configure terminal mta receive generate-mdn
| Command | Description |
mdn | Requests that an MDN be sent to the destinations defined by the mta send return-receipt-to command. |
mta receive aliases | Defines a host name to be used as an alias for the off-ramp gateway. |
mta receive maximum-recipients | Defines the number of simultaneous SMTP recipients handled by the off-ramp gateway. |
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
number | Specifies the maximum number of recipients for all SMTP connections. Valid entries are from 0 to 1024. |
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.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
This command applies to off-ramp Store and Forward Fax functions.
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.
The following example defines 10 as the maximum number of recipients for all SMTP connections:
configure terminal mta receive maximum-recipients 10
| Command | Description |
mta receive aliases | Defines a host name to be used as an alias for the off-ramp gateway. |
mta receive generate-mdn | Specifies that the off-ramp gateway process a response message delivery notification (MDN) from an SMTP server. |
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$}}
hostname string | Text string that specifies the SMTP host name or IP address. If you specify an IP address, you must enclose the IP address in brackets as follows: {xxx.xxx.xxx.xxx]. |
username string | Text string that specifies the sender's username. |
username $s$ | Wildcard that specifies that the username will be derived from the calling number. |
None.
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
The following example specifies that the mail-from username information will be derived from the sender's calling number:
configure terminal mta send mail-from username $s$
| Command | Description |
mta send origin-prefix | Defines additional identifying information to be appended in front of the e-mail header. |
mta send postmaster | Defines the address used as the mta send mail-from address if the evaluated string is blank. |
mta send return-receipt-to | Specifies the address where MDNs are sent if you request MDNs. |
mta send server | Specifies the destination server for the on-ramp. |
mta send subject | Defines the text that appears in the subject field of the fax-mail message. |
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
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"). |
Null string
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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 -0800
In 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.
The following example provides the user with additional information:
configure terminal mta send origin-prefix Cisco-Powered Fax System
| Command | Description |
mta send mail-from | Specifies the mail-from address. |
mta send postmaster | Defines the address used as the mta send mail-from address if the evaluated string is blank. |
mta send return-receipt-to | Specifies the address where MDNs are sent if you request MDNs. |
mta send server | Specifies the destination server for the on-ramp. |
mta send subject | Defines the text that appears in the subject field of the fax-mail message. |
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
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. |
Undefined
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
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 terminal mta send postmaster fax-admin@example.com
| Command | Description |
mta send mail-from | Specifies the mail-from address. |
mta send origin-prefix | Adds additional information to the e-mail prefix header. |
mta send return-receipt-to | Specifies the address where MDNs are sent if you request MDNs. |
mta send server | Specifies the destination server for the on-ramp. |
mta send subject | Defines the text that appears in the subject field of the fax-mail message. |
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$}}
hostname string | Text string that specifies the SMTP host name where MDNs will be sent. |
username string | Text string that specifies the sender's username where MDNs will be sent. |
$s$ | Wild card that specifies that the calling number (ANI) is used to generate the disposition-notification-to e-mail address. |
None defined
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
Use the mta send return-receipt-to command to define where you want MDNs to be sent after the fax-mail is opened.
This command applies to on-ramp Store and Forward Fax functions.
The following example configures scoobee as the SMTP mail server to which DSNs will be sent:
configure terminal mta send return-receipt-to hostname server.com mta send return-receipt-to username scoobee
| Command | Description |
mta send mail-from | Specifies the mail-from address. |
mta send origin-prefix | Adds additional information to the e-mail prefix header. |
mta send postmaster | Defines the address used as the mta send mail-from address if the evaluated string is blank. |
mta send server | Specifies the destination server for the on-ramp. |
mta send subject | Defines the text that appears in the subject field of the fax-mail message. |
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}
host-name | Defines the host name of the destination mail server. |
IP-address | Defines the IP address of the destination mail server. |
IP address defined as 0.0.0.0
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
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.
This command applies to on-ramp Store and Forward Fax functions.
The following example defines the mail servers scoobee.example.com and doogie.example.com as the destination mail servers:
configure terminal mta send server scoobee.example.com mta send server doogie.example.com
| Command | Description |
mta send mail-from | Specifies the mail-from address. |
mta send origin-prefix | Adds additional information to the e-mail prefix header. |
mta send postmaster | Defines the address used as the mta send mail-from address if the evaluated string is blank. |
mta send return-receipt-to | Specifies the address where MDNs are sent if you request MDNs. |
mta send subject | Defines the text that appears in the subject field of the fax-mail message. |
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
string | Text string that specifies the subject header of an e-mail message. |
Null string
Global configuration
| Release | Modification |
|---|---|
12.0(4)T | This command was introduced. |
This command applies to on-ramp Store and Forward Fax functions.
The following example defines the subject header of an e-mail message as "fax attachment":
configure terminal mta send subject fax attachment
| Command | Description |
mta send mail-from | Specifies the mail-from address. |
mta send origin-prefix | Adds additional information to the e-mail prefix header. |
mta send postmaster | Defines the address used as the mta send mail-from address if the evaluated string is blank. |
mta send return-receipt-to | Specifies the address where MDNs are sent if you request MDNs. |
mta send server | Specifies the destination server for the on-ramp. |
string | Integers representing the prefix of the telephone number associated with the specified dial peer. Valid numbers are 0 through 9, and a comma (,). Use the comma to include a pause in the prefix. |
Null string
Dial-peer configuration
| Release | Modification |
|---|---|
11.3(1)T | This command was introduced. |
12.0(4)T | This command was modified for Store and Forward Fax. |
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.
The following example specifies a prefix of 9 and then a pause:
dial-peer voice 10 pots prefix 9,
smtp | Specifies Simple Mail Transfer Protocol (SMTP) session protocol. |
smtp
Dial-peer configuration
| Release | Modification |
|---|---|
11.3(1)T | This command was introduced. |
12.0(4)T | This command was modified for Store and Forward Fax. |
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.
The following example selects SMTP as the session protocol:
dial-peer voice 10 mmoip session protocol smtp
mailto:name | Specific recipient e-mail address, name, or mailing list alias. |
mailto:$d$ | Wildcard that inserts the destination pattern of the recipient. |
@domain-name | Specifies the appropriate domain name associated with the e-mail address. |
ipv4:destination-address | IP address of the dial peer. |
dns:host-name | Indicates that the domain name server will be used to resolve the name of the IP address. Valid entries for this parameter are characters representing the name of the host device. (Optional) You can use one of the following three wildcards with this keyword when defining the session target for VoIP peers: · $s$.---Indicates that the source destination pattern will be used as part of the domain name. · $d$.---Indicates that the destination number will be used as part of the domain name. · $u$.---Indicates that the unmatched portion of the destination pattern (such as a defined extension number) will be used as part of the domain name. · $e$.---Indicates that the destination pattern is used as part of the domain name in reverse dotted format for tpc.int DNS format. For example, if the destination number is 310 555-1234 and the session target is configured as $e$.cisco.com, the translated DNS name will be 4.3.2.1.5.5.5.0.1.3.cisco.com. |
loopback:rtp | Indicates that all voice data will be looped back to the originating source. This applies to VoIP peers. |
loopback:compressed | Indicates that all voice data will be looped back in compressed mode to the originating source. This applies to POTS peers. |
loopback:uncompressed | Indicates that all voice data will be looped back in uncompressed mode to the originating source. This applies to POTS peers. |
The default for this command is enabled with no IP address or domain name defined.
Dial peer configuration
| Release | Modification |
|---|---|
11.3(1)T | This command was introduced. |
12.0(4)T | This command was modified for Store and Forward Fax. |
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.
The following example configures a session target using dns for a host, "voice_router," in the domain "cisco.com":
dial-peer voice 10 voip session target dns:voice_router.cisco.com
The 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 voip destination-pattern 1310222.... session target dns:$u$.cisco.com
The 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 voip destination-pattern 13105551111 session target dns:$d$.cisco.com
The following example delivers fax-mail to multiple recipients:
dial-peer voice 10 mmoip session target marketing-information@mailer.example.com
Assuming 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.com
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}
voice | Specifies that the active call table displays voice call information. |
fax | Specifies that the active call table displays fax call information. |
Privileged EXEC
| Release | Modification |
|---|---|
11.3(1)T | This command was introduced. |
12.0(4)T | This command was modified for Store and Forward Fax. |
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.
The following is sample output from the show call active voice command:
router# show call active voice GENERIC: SetupTime=179388054 ms Index=1 PeerAddress=+5.... PeerSubAddress= PeerId=5 PeerIfIndex=32 LogicalIfIndex=29 ConnectTime=179389793 ms CallState=4 CallOrigin=2 ChargedUnits=0 InfoType=2 TransmitPackets=532 TransmitBytes=10640 ReceivePackets=147 ReceiveBytes=2940 TELE: ConnectionId=[0xE3EA3FF8 0xFF6D0105 0x0 0x6AEC71E4] TxDuration=23230 ms VoiceTxDuration=2940 ms FaxTxDuration=0 ms CoderTypeRate=g729r8 NoiseLevel=-84 ACOMLevel=20 OutSignalLevel=-66 InSignalLevel=-66 InfoActivity=2 ERLLevel=20 SessionTarget= GENERIC: SetupTime=179388237 ms Index=1 PeerAddress=+3622 PeerSubAddress= PeerId=3 PeerIfIndex=31 LogicalIfIndex=0 ConnectTime=179389793 ms CallState=4 CallOrigin=1 ChargedUnits=0 InfoType=2 TransmitPackets=143 TransmitBytes=2860 ReceivePackets=580 ReceiveBytes=11600 VOIP: ConnectionId[0xE3EA3FF8 0xFF6D0105 0x0 0x6AEC71E4] RemoteIPAddress=172.24.96.200 RemoteUDPPort=16422 RoundTripDelay=37 ms SelectedQoS=best-effort SessionProtocol=cisco SessionTarget=ipv4:172.24.96.200 OnTimeRvPlayout=9920 GapFillWithSilence=0 ms GapFillWithPrediction=0 ms GapFillWithInterpolation=0 ms GapFillWithRedundancy=0 ms HiWaterPlayoutDelay=70 ms LoWaterPlayoutDelay=30 ms ReceiveDelay=30 ms VAD = enabled CoderTypeRate=g729r8
The 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> dBm 1 : 22021hs.1 +2263 pid:0 Answer wook song active tx:0/0 rx:0/41190 IP 0.0.0.0 AcceptedMime:2 DiscardedMime:1 1 : 23193hs.1 +1091 pid:3469 Originate 527.... active tx:10/13838 rx:0/0 Tele : tx:31200/10910/20290ms noise:-1 acom:-1 i/0:0/0 dBm
The following is sample output from the show call active fax command:
router# show call active fax GENERIC: SetupTime=22021 ms Index=1 PeerAddress=wook song PeerSubAddress= PeerId=0 PeerIfIndex=0 LogicalIfIndex=0 ConnectTime=24284 CallState=4 CallOrigin=2 ChargedUnits=0 InfoType=10 TransmitPackets=0 TransmitBytes=0 ReceivePackets=0 ReceiveBytes=41190 MMOIP: ConnectionId[0x37EC7F41 0xB0110001 0x0 0x35C34] RemoteIPAddress=0.0.0.0 SessionProtocol=SMTP SessionTarget= MessageId= AccountId= ImgEncodingType=MH ImgResolution=fine AcceptedMimeTypes=2 DiscardedMimeTypes=1 Notification=None GENERIC: SetupTime=23193 ms Index=1 PeerAddress=527.... PeerSubAddress= PeerId=3469 PeerIfIndex=157 LogicalIfIndex=30 ConnectTime=24284 CallState=4 CallOrigin=1 ChargedUnits=0 InfoType=10 TransmitPackets=5 TransmitBytes=6513 ReceivePackets=0 ReceiveBytes=0 TELE: ConnectionId=[0x37EC7F41 0xB0110001 0x0 0x35C34] TxDuration=24010 ms FaxTxDuration=10910 ms FaxRate=14400 NoiseLevel=-1 ACOMLevel=-1 OutSignalLevel=0 InSignalLevel=0 InfoActivity=0 ERLLevel=-1 SessionTarget= ImgPages=0
Table 4 provides an alphabetical listing of the show call active fields and a description of each field.
| Field | Description |
|---|---|
ACOM Level | Current ACOM level for this call. This value is the sum of the Echo Return Loss, Echo Return Loss Enhancement, and nonlinear processing loss for this call. |
CallOrigin | Call origin: answer or originate. |
CallState | Current state of the call. |
CoderTypeRate | Negotiated coder transmit rate of voice/fax compression during this call. |
ConnectionId | Global call identifier for this gateway call. |
ConnectTime | Time at which the call was connected. |
Dial-Peer | Tag of the dial peer transmitting this call. |
ERLLevel | Current Echo Return Loss (ERL) level for this call. |
FaxTxDuration | Duration of fax transmission from this peer to voice gateway for this call. You can derive the Fax Utilization Rate by dividing the FaxTxDuration value by the TxDuration value. |
GapFillWithInterpolation | Duration of voice signal played out with signal synthesized from parameters or samples of data preceding and following in time because voice data was lost or not received in time from voice gateway for this call. |
GapFillWith Redundancy | Duration of voice signal played out with signal synthesized from redundancy parameters available because voice data was lost or not received in time from voice gateway for this call. |
GapFillWithPrediction | Duration of voice signal played out with signal synthesized from parameters or samples of data preceding in time because voice data was lost or not received in time from the voice gateway for this call. Examples of such pullout are frame-eraser or frame-concealment strategies in G.729 and G.723.1 compression algorithms. |
GapFillWith Silence | Duration of voice signal replaced with silence because voice data was lost or not received in time for this call. |
HiWaterPlayoutDelay | High water mark Voice Playout FIFO Delay during this call. |
Index | Dial-peer identification number. |
InfoActivity | Active information transfer activity state for this call. |
InfoType | Information type for this call. |
InSignalLevel | Active input signal level from the telephony interface used by this call. |
LogicalIfIndex | Index number of the logical interface for this call. |
LoWaterPlayoutDelay | Low water mark Voice Playout FIFO Delay during this call. |
NoiseLevel | Active noise level for this call. |
OnTimeRvPlayout | Duration of voice playout from data received in time for this call. You can derive the Total Voice Playout Duration for Active Voice by adding the OnTimeRvPlayout value to the GapFill values. |
OutSignalLevel | Active output signal level to telephony interface used by this call. |
PeerAddress | Destination pattern associated with this peer. |
PeerId | ID value of the peer table entry to which this call was made. |
PeerIfIndex | Voice-port index number for this peer. |
PeerSubaddress | Subaddress to which this call is connected. |
ReceiveBytes | Number of bytes received by the peer during this call. |
ReceiveDelay | Average Playout FIFO Delay plus the Decoder Delay during this call. |
ReceivePackets | Number of packets received by this peer during this call. |
RemoteIPAddress | Remote system IP address for the VoIP call. |
RemoteUDPPort | Remote system UDP listener port to which voice packets are transmitted. |
RoundTripDelay | Voice packet round trip delay between the local and remote system on the IP backbone during this call. |
SelectedQoS | Selected RSVP quality of service (QoS) for this call. |
SessionProtocol | Session protocol used for an Internet call between the local and remote router via the IP backbone. |
SessionTarget | Session target of the peer used for this call. |
SetupTime | Value of the system UpTime when the call associated with this entry was started. |
TransmitBytes | Number of bytes transmitted from this peer during this call. |
TransmitPackets | Number of packets transmitted from this peer during this call. |
TxDuration | Duration of transmit path open from this peer to the voice gateway for this call. |
VADEnable | Whether voice activation detection (VAD) was enabled for this call. |
VoiceTxDuration | Duration of voice transmission from this peer to voice gateway for this call. You can derive the Voice Utilization Rate by dividing the VoiceTxDuration value by the TxDuration value. |
| Command | Description |
show call history fax | Shows call history information for fax transmissions. |
voice | Specifies that the call history tables displays voice call information. |
fax | Specifies that the call history table displays fax call information. |
last number | (Optional) Displays the last calls connected, where the number of calls displayed is defined by the argument number. Valid values are from 1 to 2147483647. |
brief | (Optional) Displays a truncated version of the call history table. |
Privileged EXEC
| Release | Modification |
|---|---|
11.3(1)T | This command was introduced. |
12.0(4)T | This command was modified for Store and Forward Fax. |
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.
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>dBm
234 : 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 g729r8
234 : 158305745hs.1281 +236 +9195 pid:6 Originate +68888
tx:1358/27160 rx:3804/76080 10 (normal call clearing.)
Telephony 0:D:22: tx:91850/76080/0ms g729r8 noise:-84dBm acom:20dBm
235 : 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 g729r8
235 : 158344856hs.1283 +224 +28769 pid:6 Originate +68888
tx:4604/92080 rx:11063/221260 10 (normal call clearing.)
Telephony 0:D:22: tx:287590/221280/0ms g729r8 noise:-75dBm acom:20dBm
The 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>dBm 2 : 5996450hs.25 +-1 +3802 pid:100 Answer 408 tx:0/0 rx:0/0 1F (T30 T1 EOM timeout) Telephony : tx:38020/38020/0ms g729r8 noise:0dBm acom:0dBm 2 : 5996752hs.26 +-1 +3500 pid:110 Originate uut1@linux2.allegro.com tx: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:0 3 : 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:-14dBm 3 : 6447780hs.28 +1182 +4516 pid:0 Answer tx:0/0 rx:0/0 10 (normal call clearing.) IP 0.0.0.0 AcceptedMime:0 DiscardedMime:0 4 : 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:-14dBm 4 : 6464748hs.30 +1118 +4517 pid:0 Answer tx:0/0 rx:0/0 10 (normal call clearing.) IP 0.0.0.0 AcceptedMime:0 DiscardedMime:0 5 : 6507900hs.31 +1158 +2392 pid:100 Answer 4085763413 tx:0/0 rx:3/3224 10 (Normal connection) Telephony : tx:23920/11580/12340ms g729r8 noise:0dBm acom:0dBm 5 : 6508152hs.32 +1727 +2140 pid:110 Originate uut1@linux2.allegro.com tx:0/2754 rx:0/0 3F (service or option not available, unspecified) IP 14.0.0.4 AcceptedMime:0 DiscardedMime:0 6 : 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:-14dBm 6 : 6517106hs.34 +1149 +4517 pid:0 Answer tx:0/0 rx:0/0 10 (normal call clearing.) IP 0.0.0.0 AcceptedMime:0 DiscardedMime:0 7 : 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:-14dBm 7 : 6567308hs.36 +1128 +4517 pid:0 Answer tx:0/0 rx:0/0 10 (normal call clearing.) IP 0.0.0.0 AcceptedMime:0 DiscardedMime:0
The following is output from the show call history command.
router# show call history fax l 2 GENERIC: SetupTime=23193 ms Index=1 PeerAddress=527.... PeerSubAddress= PeerId=3469 PeerIfIndex=157 LogicalIfIndex=30 DisconnectCause=10 DisconnectText=normal call clearing.: Normal connection ConnectTime=24284 DisconectTime=31288 CallOrigin=1 ChargedUnits=0 InfoType=fax TransmitPackets=62 TransmitBytes=88047 ReceivePackets=0 ReceiveBytes=0 TELE: ConnectionId=[0x37EC7F41 0xB0110001 0x0 0x35C34] TxDuration=80950 ms FaxTxDuration=10910 ms FaxRate=14400 NoiseLevel=-1 ACOMLevel=-1 SessionTarget= ImgPages=3 GENERIC: SetupTime=22021 ms Index=2 PeerAddress=wook song PeerSubAddress= PeerId=0 PeerIfIndex=0 LogicalIfIndex=0 DisconnectCause=10 DisconnectText=normal call clearing. ConnectTime=24284 DisconectTime=31545 CallOrigin=2 ChargedUnits=0 InfoType=fax TransmitPackets=0 TransmitBytes=0 ReceivePackets=0 ReceiveBytes=41190 MMOIP: ConnectionId[0x37EC7F41 0xB0110001 0x0 0x35C34] RemoteIPAddress=0.0.0.0 SessionProtocol=SMTP SessionTarget= MessageId= AccountId= ImgEncodingType=MH ImgResolution=fine AcceptedMimeTypes=2 DiscardedMimeTypes=1 Notification=None
Table 5 provides an alphabetical listing of the fields for the show call history command and a description of each field.
| Field | Description |
|---|---|
ACOMLevel | Average ACOM level for this call. This value is the sum of the Echo Return Loss, Echo Return Loss Enhancement, and nonlinear processing loss for a particular call. |
CallOrigin | Call origin: answer or originate. |
CoderTypeRate | Negotiated coder rate. This value specifies the transmit rate of voice/fax compression to its associated call leg for this call. |
ConnectionID | Global call identifier for the gateway call. |
ConnectTime | Time this call was connected. |
DisconnectCause | Description explaining why this call was disconnected. |
DisconnectText | Descriptive text explaining the disconnect reason. |
DisconnectTime | Time this call was disconnected. |
FaxDuration | Duration of fax transmission from this peer to voice gateway for this call. You can derive the Fax Utilization Rate by dividing the FaxTxDuration value by the TxDuration value. |
GapFillWithInterpolation | Duration of voice signal played out with signal synthesized from parameters or samples of data preceding and following in time because voice data was lost or not received in time from the voice gateway for this call. |
GapFillWithRedundancy | Duration of voice signal played out with signal synthesized from redundancy parameters available because voice data was lost or not received in time from the voice gateway for this call. |
GapFillWithSilence | Duration of voice signal replaced with silence because the voice data was lost or not received in time for this call. |
GapFillWithPrediction | Duration of voice signal played out with signal synthesized from parameters or samples of data preceding in time because voice data was lost or not received in time from the voice gateway for this call. |
HiWaterPlayoutDelay | High water mark Voice Playout FIFO Delay during the voice call. |
Index | Dial peer identification number. |
InfoType | Information type for this call. |
LogicalIfIndex | Index number of the logical voice port for this call. |
LoWaterPlayoutDelay | Low water mark Voice Playout FIFO Delay during the voice call. |
NoiseLevel | Average noise level for this call. |
OnTimeRvPlayout | Duration of voice playout from data received on time for this call. You can derive the Total Voice Playout Duration for Active Voice by adding the OnTimeRvPlayout value to the GapFill values. |
PeerAddress | Destination pattern or number associated with this peer. |
PeerId | ID value of the peer entry table to which this call was made. |
PeerIfIndex | Index number of the logical interface through which this call was made. For ISDN media, this would be the index number of the B channel used for this call. |
PeerSubAddress | Subaddress to which this call is connected. |
ReceiveBytes | Number of bytes received by the peer during this call. |
ReceiveDelay | Average Playout FIFO Delay plus the Decoder Delay during this voice call. |
ReceivePackets | Number of packets received by this peer during this call. |
RemoteIPAddress | Remote system IP address for this call. |
RemoteUDPPort | Remote system UDP listener port to which voice packets are transmitted. |
RoundTripDelay | Voice packet round trip delay between the local and remote system on the IP backbone for this call. |
SelectedQoS | Selected RSVP QoS for this call. |
Session Protocol | Session protocol to be used for an Internet call between the local and remote router via the IP backbone. |
Session Target | Session target of the peer used for third call. |
SetUpTime | Value of the system UpTime when the call associated with this entry was started. |
TransmitBytes | Number of bytes transmitted by this peer during this call. |
TransmitPackets | Number of packets transmitted by this peer during this call. |
TxDuration | Duration of the transmit path open from this peer to the voice gateway for this call. |
VADEnable | Whether voice activation detection (VAD) was enabled for this call. |
VoiceTxDuration | Duration of voice transmitted from this peer to voice gateway for this call. You can derive the Voice Utilization Rate by dividing the VoiceTxDuration by the TxDuration value. |
| Command | Description |
show call active fax | Shows active call information for a fax transmission in progress. |
This command has no arguments or keywords.
Dial-peer configuration
| Release | Modification |
|---|---|
11.3(1)T | This command was introduced. |
12.0(4)T | This command was modified for Store and Forward Fax. |
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.
The following example changes the administrative state of MMoIP dial peer 10 to down:
configure terminal dial-peer voice 10 shutdown
The following example changes the administrative state of MMoIP dial peer 10 to up:
configure terminal dial-peer voice 10 no shutdown
| Command | Description |
dial-peer voice | Enters the dial-peer configuration mode, define the type of dial peer, and define the dial-peer tag number. |
Posted: Tue Jul 18 14:57:44 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.