Table Of Contents
T.37/T.38 Fax Gateway for Cisco 2600 Series Routers and Cisco 3600 Series Routers
Using Interactive Voice Response for Call Processing
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring the Fax Gateway to Support IVR
Configuring the On-Ramp Gateway
Configuring the Called Subscriber Number
Configuring the POTS Dial Peer
Configuring the MMoIP Dial Peer
Verifying the On-Ramp Gateway Configuration
Configuring the Off-Ramp Gateway
Configuring the Transmitting Subscriber Number
Configuring the Fax Transmission Speed
Configuring the Receiving Mail Transfer Agent
Configuring the POTS Dial Peer
Configuring the MMoIP Dial Peer
Configuring the Faxed Header Information
Configuring the Fax Cover Page Information
Verifying the Off-Ramp Gateway Configuration
Configuring the Gateway Security
Configuring On-Ramp Gateway Security
Configuring Off-Ramp Gateway Security
Configuring the Gateway for TCL Application Files
Configuring the On-Ramp Gateway Elements for MDN
Configuring the Off-Ramp Gateway Element for MDN
T.37/T.38 Fax Gateway for Cisco 2600 Series Routers and Cisco 3600 Series Routers
Feature History
This document describes the T.37/T.38 Fax Gateway feature for the Cisco 2600 series and Cisco 3600 series routers in Cisco IOS Release 12.2(8)T. This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
This feature adds fax detection and Store-and-Forward Fax to the Cisco 2600 series and Cisco 3600 series routers. Store-and-Forward Fax, previously documented in the Cisco IOS Multiservice Applications Configuration Guide, enables Cisco 2600 series routers and Cisco 3600 series routers to send and receive faxes across packet-based networks. When equipped with Digital and Analog voice network modules, these routers support configuration of the T.37/T38 Fax Gateway. Supported network modules are NM-HDV with voice interface cards (VIC) for Digital T1 connections and Voice 2V with voice interface cards (VIC) FXS for Analog connections. VWIC and VIC FXS are the voice interface cards within the network modules.
Voice network modules installed in Cisco 2600 series or Cisco 3600 series routers convert telephone voice signals into data packets that can be transmitted over an IP network. VWICs/VICs work with existing telephone and fax equipment, and are compatible with H.323 standards for audio and video conferencing.
When the Cisco 2600 series or Cisco 3600 series is equipped with network modules, it supports carrier-class Voice over IP (VoIP) and fax over IP services. Since the Cisco 2600 series routers and Cisco 3600 series routers are H.323 compliant, they support a family of industry-standard voice codecs and provide echo cancellation and Voice Activity Detection (VAD)/silence suppression. There is an Interactive Voice Response (IVR) application that provides voice prompts and digit collection in order to authenticate the user and identify the call destination.
Figure 1 highlights the real-time (T.38 path) versus the Store-and-Forward processing (T.37 path) for fax transactions over IP networks.
Figure 1 Real-time versus Store-and-Forward Fax Processing
Previously, fax over IP used a proprietary protocol and an H.323 connection, represented by the T.37 path in the diagram. The T.37 path used the Extended Simple Mail Transfer Protocol (ESMTP) store-and-forward method. The on-ramp gateway router accepted fax data from the PSTN or a fax machine connected to the analog line.
The router converted the fax data into a TIFF attachment in a MIME e-mail message and transmitted the attachment to a store-and-forward SMTP server. These servers would deliver the faxmail message to the off-ramp gateway router. Once the off-ramp gateway router received the faxmail message, it processed the message and initiated a session with the destination fax machine.
The T.38 path will take precedence over the T.37 path whenever possible. This means that as a fax session is being set up, the sending gateway will first communicate using the T.38 path. If the communication fails, the sending gateway will rollover to the Cisco T.37 path if it is configured to rollover.
Note
To configure Store-and-Forward Fax, the VoIP software component must be installed and functional on the Cisco 2600 series routers and Cisco 3600 series routers.
Using Interactive Voice Response for Call Processing
Interactive Voice Response (IVR) applications control calls in the T.37/T.38 Fax Gateway. They can be assigned to specific ports or invoked based on DNIS and accommodate many gateway services by customizing the presentation of the interfaces to callers.
IVR uses Tool Control Language (TCL) scripts to gather information. For example, a TCL script plays when the caller receives a voice-prompt to enter a specific type of information, such as a PIN. After the caller inputs the PIN, TCL collects the digits and forwards the digits to the server for storage and retrieval.
Note
Benefits
Cost Savings and Port Density
The cost of maintaining two architectures, one for voice and one for fax, is eliminated. Service providers can use a single port for both voice, fax relay, and Store-and-Forward Fax. For smaller points of presence, the single-port configuration for both technologies is even more significant because mixed traffic can be handled more efficiently (only a single pool of ports versus splitting traffic across two pools).
Single Number for Voice and Fax Access
Service providers can offer the new service of a single number for subscriber voice and fax access. The applications that use a single number for voice and fax require only half as many Dialed Number Identification Service (DNIS) numbers and dial peers as would be required with separate voice and fax applications.
Switch from Fax Relay to Fax Store-and-Forward
Service providers can offer applications that require toggling from voice to fax.
Restrictions
The Cisco gateway must be equipped with 128 MB of Random Access Memory (RAM).
The Cisco 3660 gateway must be equipped with 256 MB of Random Access Memory (RAM) in the following situations:
•
•
Related Features and Technologies
Store-and-Forward Fax and Fax Relay make use of and are related to the following features and technologies:
•
•
•
•
•
•
•
Related Documents
For more information about voice configuration, see the following Cisco IOS Release 12.2 guides:
•
•
For related information on this feature, refer to the following documents:
•
•
•
•
The following online feature documentation and installation guides describe the configuration and installation of hardware components:
•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis3600/index.htmSupported Platforms
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Supported Standards, MIBs, and RFCs
Standards
•
•
•
•
MIBs
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Store-and-Forward Fax is also compliant with the SMTP requirements in RFC 1123, Requirements for Internet Hosts—Application and Support.
Prerequisites
Before configuring the T.37/T.38 Fax Gateway on a Cisco 2600 series or Cisco 3600 series router, the following task must be completed:
•
Configuration Tasks
The configuration tasks that must be performed are:
•
•
•
•
•
Configuring the Fax Gateway to Support IVR
Before configuring the Cisco gateway to support IVR, perform the following:
•
•
•
•
–
–
•
•
Enabling T.37 Functionality
To enable T.37 functionality, use the following command in global configuration mode:
Enables T.37 functionality for Cisco 2600 series and Cisco 3600 series.
Configuring IVR Functionality
To configure IVR functionality using either classic or TCL scripts, perform the following:
•
•
•
•
To configure IVR functionality, use the following commands, beginning in privileged EXEC mode:
Table 1 lists the required TCL scripts for fax applications on T.37 functionalitys.
Use the following commands to verify the IVR configuration:
•
•
•
•
Configuring the On-Ramp Gateway
When acting as the on-ramp gateway, the Cisco gateway receives faxes from end users, converts them into TIFF files, creates standard MIME e-mail messages, attaches the TIFF files to the e-mail messages, and forwards the fax-mail messages to the designated SMTP server for storage.
The gateway uses the sending MTA and dial peers to complete these tasks. The sending MTA, which is the Cisco gateway, defines delivery parameters associated with the e-mail message to which the fax TIFF file is attached. The delivery parameters include defining a return e-mail path or designating a destination mail server.
To configure the on-ramp gateway, perform the tasks described in the following sections:
•
•
•
•
Configuring the Called Subscriber Number
The called subscriber number is the number displayed in the LCD of the fax device when a fax is sent to a recipient. Typically, with a standard Group 3 fax device, this is the telephone number associated with the receiving fax device. To configure the called subscriber number, use the following commands beginning in privileged EXEC mode:
Note
Configuring the Sending MTA
MTAs define the elements of the e-mail message to which the fax TIFF file is attached, which includes:
•
•
•
•
•
•
•
Note
To configure the sending MTA, use the following commands in global configuration mode:
Configuring the POTS Dial Peer
To configure the POTS dial peer, use the following commands beginning in global configuration mode:
Configuring the MMoIP Dial Peer
To configure the MMoIP dial peer, use the following commands beginning in global configuration mode:
Verifying the On-Ramp Gateway Configuration
To verify the on-ramp gateway configuration, perform the following:
•
•
Note
•
•
•
•
•
•
•
Note
Configuring the Off-Ramp Gateway
Off-ramp faxing requires that the Cisco gateway act as an off-ramp gateway to dial the POTS and communicate with a remote fax machine (Group 3 fax device), using standard fax protocols. The off-ramp gateway provides the following functionality:
•
•
•
•
Note
The off-ramp POTS dial peer defines the telephone number of the destination fax device. Because a destination pattern is defined for an outbound POTS peer, number expansion can be used.
To configure the off-ramp gateway, perform the tasks in the following sections:
•
•
•
•
•
•
•
•
Configuring the Transmitting Subscriber Number
You can configure the off-ramp gateway to convert a fax TIFF file to a standard fax or send an e-mail message as a fax by configuring the transmitting subscriber number.
The transmitting subscriber number is 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.
To configure the transmitting subscriber number, use the following commands beginning in privileged EXEC mode:
Configuring the Fax Transmission Speed
You can control the maximum speed of the fax transmission if the off-ramp gateway is sending faxes into an area where the fax transmission speed is always negotiated down to a slower speed.
To configure the fax transmission speed, use the following command in global configuration mode:
Router(config)# fax send max-speed {2400 | 4800 | 9600 | 12000 | 14400}Specifies the maximum speed at which an off-ramp fax is sent.
Configuring the Receiving Mail Transfer Agent
To configure the receiving MTA, use the following commands in global configuration mode:
Configuring the POTS Dial Peer
To configure the POTS dial peer for the off-ramp gateway, use the following commands beginning in global configuration mode:
Configuring the MMoIP Dial Peer
To configure the off-ramp gateway MMoIP dial peer, use the following commands beginning in global configuration mode:
Note
Configuring the Faxed Header Information
Store-and-Forward Fax converts standard e-mail messages into fax transmissions. When a fax is sent using a standard Group 3 device, there is usually header information appended to the top of each faxed cover and text page indicating the telephone number of the sending fax device, the date, and the time of transmission. These faxes require that header information is appended to each faxed page.
Store-and-Forward Fax requires that you configure the header information. Also, the destination address of an e-mail message can control the cover page generation on a per-recipient basis.
Note
To configure faxed header information, use the following commands in global configuration mode:
Configuring the Fax Cover Page Information
The off-ramp gateway can create fax cover pages for faxes that originate from e-mail messages.
Note
To configure fax cover page information, use the following commands in global configuration mode:
The destination address of an e-mail message can 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.
For example, if the address has the cover parameter set to no, the parameter overrides the setting for the fax send coverpage enable command, and the off-ramp gateway does not generate a fax cover page. If the address has the cover parameter set to yes, the off-ramp gateway defers the setting configured in the e-mail address and generates a cover page. Table 2 contains examples of what you can enter in the e-mail To: field.
To configure the router to defer to the cover page setting in the e-mail header, use the following commands in global configuration mode:
Verifying the Off-Ramp Gateway Configuration
Perform the following to verify the off-ramp gateway configuration:
•
•
•
•
•
•
•
To check whether the fax cover page generates correctly, send an e-mail message to the off-ramp gateway. To check if the fax-mail is processed correctly, request a return receipt in the e-mail message and send a fax-mail using a mail client, such as Eudora to the off-ramp gateway. The destination e-mail address must have the appropriate fax=user@receive alias to be allowed.
Configuring the Gateway Security
To configure gateway security, perform the tasks in the following sections:
•
•
•
Configuring On-Ramp Gateway Security
On-ramp security controls who can send fax messages to the network and is facilitated by AAA security services using either RADIUS or TACACS+ as the local security protocol. On-ramp faxing is a client of the authentication server, whether RADIUS or TACACS+. User information is forwarded to the AAA interface, which is then forwarded as an authentication request to the security server.
Authentication must be completed before the first page of faxed material is accepted from the modem by the Fax Application Process (FAP). If a response is not received from the AAA server before the first page is received, the fax modem disconnects the call.
To configure on-ramp security, use the following commands in global configuration mode:
Configuring Off-Ramp Gateway Security
Off-ramp security controls who can send outgoing fax messages and is facilitated by AAA security services using either RADIUS or TACACS+. Authentication begins as soon as a fax e-mail message header is received from the e-mail server on the off-ramp gateway. The Cisco AS5300 Universal Access Server does not dial the destination fax device until authentication for each fax-mail is successfully completed.
The on-ramp gateway inserts the value that was configured 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 the configured gateway value in the X-account-ID field should be used, the mmoip aaa send-id primary command must be configured with the account-id keyword. This keyword enables Store-and-Forward Fax to generate end-to-end authentication and accounting tracking records. If authentication is not configured on the on-ramp gateway, the X-account-ID field is left blank.
Note
Note
To configure off-ramp security, use the following commands in global configuration mode:
Configuring the ACLs
Incoming ACLs can be used on Ethernet or FastEthernet interfaces to filter SMTP traffic for Store-and-Forward Fax. We recommend that ACLs be configured to restrict access to the SMTP port (port 25) to only trusted e-mail servers.
Creating ACLs is a relatively complicated task and beyond the scope of this document. The following example, though, provides a starting point.
The following example shows how to restrict access to the SMTP port 25 to a trusted e-mail server (IP address 10.0.0.1):
! Enter global configuration mode.configure terminal!! Configure ACLs to restrict access to the SMTP port (port 25) to only "trusted"! e-mail servers. Depending on the topology of your particular network, replace the! any keyword with the destination IP addresses of the Ethernet and FastEthernet! interfaces. Define all trusted e-mail servers using the tcp host ip-address! portion of this command.access-list 100 permit tcp host 10.0.0.1 any eq smtpaccess-list 100 deny tcp any any eq smtpaccess-list 100 permit ip any any!! Enter interface configuration mode for Ethernet interface 0.interface ethernet 0! Apply the access list to this interface.access-group 100 in!! Enter interface configuration mode for FastEthernet interface 0.interface fastethernet 0! Apply the access list to this interface.access-group 100 inFor complete information about configuring ACLs, refer to the relative chapters in the Cisco IOS Security Configuration Guide.
Configuring the Gateway for TCL Application Files
To configure gateway security for the TCL application files being used for fax calls on T.37 functionality, use the following commands in global configuration mode:
Configuring MDN
One basic e-mail operation that Store-and-Forward Fax supports is MDN (return receipt). Described in RFC 2298, MDN indicates that the e-mail message has been opened. A sender requests that an MDN be returned when the receiver opens an e-mail message.
The MDN is initiated by the sending e-mail client, and the return receipt is generated by the receiving e-mail client. Most PC-based e-mail software applications, such as Eudora, Netscape Messenger, and Microsoft Outlook,) generate MDNs.
The MDN is sent to an address chosen by the sender and the following header is included in the e-mail header of the message:
Disposition-Notification-To:This header is followed by the address of the sender.
RFC 2298 requires that the receiver can prevent the automatic generation of an MDN. Because of the requirement, it is difficult to determine whether or not the user has actually received the e-mail message. For example, the recipient can always choose not to respond to MDN requests, or the recipient software cannot understand or accept MDN requests.
To configure MDN for Store-and-Forward Fax, configure the MDN elements on both the on-ramp and off-ramp gateways.
The required tasks are:
•
•
Configuring the On-Ramp Gateway Elements for MDN
To configure the on-ramp gateway to support MDN, use the following commands beginning in global configuration mode:
Configuring the Off-Ramp Gateway Element for MDN
To configure the off-ramp gateway to support MDN, use the following command in global configuration mode:
Specifies that the Cisco 2600 series or Cisco 3600 series router acting as the off-ramp gateway will respond to a request for an MDN.
Verifying MDN Configuration
Perform the following to verify the MDN configuration:
•
•
•
•
Configuring DSN
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. 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 the mta send mail-from command.
The off-ramp DSN is requested by the e-mail client. The DSN response is generated by the off-ramp gateway when it receives a request as part of the fax-mail message. DSNs can only be generated if the mail client on the SMTP server is capable of responding to a DSN request. Because the SMTP server generates the DSNs, you need to configure both the mail from: and rcpt to: commands for the DSN feature to be operational, for example:
mail from: <user@mail-server.company.com>rcpt to: <fax=555-1212@company.com> NOTIFY=SUCCESS,FAILURE,DELAYThree different states can be reported back to the sender as follows:
•
•
•
Note
To configure DSN, use the following commands beginning in global configuration mode:
Verifying DSN Configuration
Perform the following tasks to verify the DSN configuration:
•
•
•
•
•
Configuration Examples
The example covers the T.37 onramp, offramp and T.38 fallback to T.37 features over PRI, CAS-FGD and Analog FXS signalling types.
!version 12.2no service single-slot-reload-enableservice timestamps debug datetime msecservice timestamps log uptimeno service password-encryption!hostname faxgate-3660-1!logging buffered 10000 debugginglogging rate-limit console 10 except errorsenable secret 5 $1$J.ez$AsdHObxxtAIsFsRalbh4w0enable password cisco!username all!!memory-size iomem 40clock timezone PST -8voice-card 1!voice-card 3!ip subnet-zero!!no ip domain-lookupip domain-name cisco.comip host yushiro 223.255.254.254!no ip dhcp-client network-discoveryno mgcp timer receive-rtcpisdn switch-type primary-4essisdn voice-call-failure 0call rsvp-synccall application voice off_ramp tftp://255.255.254.254/script/t37_offramp.nchen.tclcall application voice app_lib_rollover tftp://255.255.254.254/script/fax_rollover_on_busy.tclcall application voice on_ramp tftp://255.255.254.254/script/t37_onramp14.nchen.tclcall application voice on_ramp language 1 encall application voice on_ramp set-location en 0 tftp://255.255.254.254/audio/call application voice r39 tftp://255.255.254.254/script/fax_detect_2.1.2.0.tclcall application voice r39 prompt tftp://225.255.254.254/audio/en_listen_first.aucall application voice r39 mode connect-firstcall application voice r39 language 1 encall application voice r39 set-location en 0 tftp://255.255.254.254/audio/en_listen_first.au!voice service voipfax protocol t38 ls-redundancy 2 hs-redundancy 2h323 call start fast!!!!!fax receive called-subscriber $d$fax interface-type fax-mailmta send server 1.2.129.200mta send subject "Faxgate - Regression"mta send postmaster devtest@faxgate.commta send mail-from hostname faxgate.commta send mail-from username devtestmta send return-receipt-to hostname faxgate.commta send return-receipt-to username devtestmta receive aliases [1.2.129.1]mta receive aliases [1.2.129.200]mta receive maximum-recipients 100!!controller T1 1/0framing sflinecode ami!controller T1 1/1framing esflinecode b8zsds0-group 0 timeslots 1-24 type e&m-wink-start!controller T1 3/0framing esflinecode b8zspri-group timeslots 1-24!controller T1 3/1framing esflinecode b8zsds0-group 0 timeslots 1-24 type e&m-fgd!interface FastEthernet0/0ip address 1.2.129.1 255.255.0.0speed autohalf-duplex!interface FastEthernet0/1ip address 172.19.149.110 255.255.255.0duplex autospeed auto!interface Serial3/0:23no ip addressno logging event link-statusisdn switch-type primary-4essisdn incoming-voice voiceisdn T310 60000no cdp enable!ip default-gateway 1.2.0.1ip classlessip route 0.0.0.0 0.0.0.0 1.2.0.1ip route 171.0.0.0 255.0.0.0 FastEthernet0/1ip route 223.255.254.254 255.255.255.255 1.2.0.1no ip http server!!!snmp-server packetsize 4096snmp-server manager!!voice-port 1/1:0!voice-port 2/0/0!voice-port 2/0/1!voice-port 2/1/0!voice-port 2/1/1!voice-port 3/0:23!voice-port 3/1:0!dial-peer cor custom!!! Dial-peer mmoip for offrampdial-peer voice 68 mmoipapplication off_rampincoming called-number .information-type fax! Dial-peer pots for offramp (PRI)dial-peer voice 70 potsdestination-pattern 321....direct-inward-dialport 3/0:23forward-digits 0prefix 321!! Dial-peer pots for offramp (FGD)dial-peer voice 80 potsdestination-pattern 521....direct-inward-dialport 1/1:0forward-digits 0prefix 521!! Dial-peer pots for offramp (FXS)dial-peer voice 90 potsdestination-pattern 621....port 2/1/0forward-digits all!!! Dial-peer mmoip for onrampdial-peer voice 67 mmoipapplication fax_on_vfc_onramp_app out-bounddestination-pattern ........information-type faxsession target mailto:devtest@[1.2.129.200]!! Dial-peer pots for onramp (PRI)dial-peer voice 69 potsapplication on_rampmax-conn 100destination-pattern 321....direct-inward-dialport 3/0:23forward-digits 0prefix 321!! Dial-peer pots for onramp (FGD)dial-peer voice 79 potsapplication on_rampmax-conn 100destination-pattern 521....direct-inward-dialport 3/1:0forward-digits 0prefix 521!! Dial-peer pots for onramp (FXS)dial-peer voice 89 potsapplication on_rampmax-conn 100destination-pattern 621....port 2/0/0forward-digits all!! Dial-peer pots for T.38 Fallback to T.37 (PRI)dial-peer voice 75 potsapplication app_lib_rolloverport 3/0:23!! Dial-peer pots for T.38 Fallback to T.37 (FGD)dial-peer voice 85 potsapplication app_lib_rolloverport 3/1:0!! Dial-peer pots for T.38 Fallback to T.37 (FXS)dial-peer voice 65 potsapplication app_lib_rolloverport 2/0/1!! Dial-peer voip for T.38dial-peer voice 71 voippreference 1destination-pattern 9.......playout-delay maximum 300fax protocol t38 ls-redundancy 2 hs-redundancy 2!! Dial-peer voip for T.37dial-peer voice 66 mmoippreference 2application fax_on_vfc_onramp_app out-bounddestination-pattern 9.......information-type faxsession target mailto:devtest@[1.2.129.200]!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4password lablogin!!endThis example covers the T.37 onramp with AAA functionality using Radius server over PRI signalling.
!version 12.2no service single-slot-reload-enableservice timestamps debug datetime msecservice timestamps log uptimeno service password-encryption!hostname Faxgate-3660-2!logging buffered 4096 alertslogging rate-limit console 10 except errorsaaa new-modelaaa authentication login h323 group radius localaaa authorization exec fax_list group radiusaaa authorization exec fax group radiusaaa authorization exec h323 group radiusaaa accounting connection fax stop-only group radiusaaa accounting connection fax_list stop-only group radiusaaa accounting connection h323 stop-only group radius!!!memory-size iomem 30voice-card 3!voice-card 5!ip subnet-zero!!no ip domain-lookup!no ip dhcp-client network-discoveryno mgcp timer receive-rtcpisdn switch-type primary-4essisdn voice-call-failure 0call rsvp-synccall application voice off_ramp tftp://255.255.254.254/faxacct-test/t37_offramp.0.0.6.tclcall application voice app_lib_rollover tftp://255.255.254.254/faxacct-test/fax_rollover_on_busy.tclcall application voice on_ramp tftp://255.255.254.254/faxacct-test/t37_onramp14.tclcall application voice on_ramp accounting enablecall application voice on_ramp access-method prompt-usercall application voice on_ramp authen-list fax_listcall application voice on_ramp authen-method prompt-usercall application voice on_ramp authentication enablecall application voice on_ramp language 1 encall application voice on_ramp set-location en 0 tftp://255.255.254.254/audio/en/!voice service voipfax protocol t38 ls-redundancy 2 hs-redundancy 2h323 call start fast!!!!!fax receive called-subscriber $d$fax send max-speed 12000fax send right-header From:$s$fax send coverpage enablefax send coverpage show-detailfax send coverpage email-controllablefax send coverpage comment This is a Off-Ramp call cover pagefax interface-type fax-mailmta send server 1.2.129.200mta send subject "3660-Offramp"mta send postmaster devtest@faxgate.commta send mail-from hostname faxgate.commta send mail-from username devtestmta receive aliases [1.2.129.200]mta receive aliases [1.2.129.2]mta receive maximum-recipients 20!controller T1 5/0framing esfclock source internallinecode b8zspri-group timeslots 1-24!!interface FastEthernet0/0ip address 1.2.129.2 255.255.0.0speed autohalf-duplex!interface Serial5/0:23no ip addressno logging event link-statusisdn switch-type primary-4essisdn incoming-voice voiceisdn T310 60000no cdp enable!ip default-gateway 1.2.0.1ip classlessip route 0.0.0.0 0.0.0.0 1.2.0.1ip route 223.255.254.254 255.255.255.255 1.2.0.1no ip http server!!!snmp-server packetsize 4096snmp-server manager!radius-server host 1.4.174.1 auth-port 1645 acct-port 1646radius-server retransmit 3radius-server key ciscoradius-server vsa send accountingradius-server vsa send authentication!voice-port 5/0:23!dial-peer cor custom!!dial-peer voice 69 potsapplication on_rampincoming called-number .destination-pattern 9.......port 5/0:23!dial-peer voice 67 mmoipapplication fax_on_vfc_onramp_app out-bounddestination-pattern .information-type faxsession target mailto:thsu@[1.2.129.200]dsn delayeddsn successdsn failure!!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4!!endThe following examples show configuration for NM-HDV T.38 Rollover to T.37 on the Cisco 2600 series router and Cisco 3600 series router.
fax interface-type fax-mailvoice service voipfax protocol t38 ls-redundancy 0 hs-redundancy 0call application voice app_libretto_offramp5 tftp://dirt/libretto-test/app_libretto_offramp5.tclcall application voice app_onramp9 tftp://dirt/nchen/onramp13.nc.tclcall application voice app_onramp9 language 1 encall application voice app_onramp9 accounting-list faxcall application voice app_onramp9 set-location en 0 tftp://dirt/cchiu/WV/en_new/call application voice app_lib_rollover tftp://dirt/libretto-test/ fax_rollover_on_busy.tclfax receive called-subscriber $d$fax send transmitting-subscriber $s$fax send left-header $s$fax send center-header $t$fax send right-header Page: $p$fax send coverpage enablefax send coverpage email-controllablefax send coverpage comment Cisco cover page commentmta receive aliases [1.14.120.2]mta send server faxgate_smtp_servermta send subject "T.38 Rollover to T.37 testing on T1 CAS FGD"mta send origin-prefix Cisco Faxmta send postmaster postmaster nchen@cisco.commta send mail-from hostname faxgate_testmta send mail-from username fax-usermta send return-receipt-to hostname return.host.commta send return-receipt-to username $s$mta receive aliases bock.cisco.commta receive aliases cisco.commta receive maximum-recipients 200mta receive generate-mdncontroller T1 1/1framing esfclock source line primarylinecode b8zspri-group timeslots 1-24interface Ethernet0ip address 1.14.120.2 255.255.0.0no ip directed-broadcastinterface Serial3/0:23no ip addressip mroute-cacheno logging event link-statusisdn switch-type primary-5essisdn incoming-voice modemfair-queue 64 256 0no cdp enable! The following configuration command must be set for T.38 rollover to T.37voice hunt user-busy!! Inbound peer for T.38/T.37 onramp rollover operation! This peer includes the TCL application for rollover operationdial-peer voice 70 potsapplication app_lib_rolloverport 3/0:23! Outbound peer for T.38 ingress gateway! This peer requires lower preference number then next matching peerdial-peer voice 71 voippreference 1destination-pattern 3746096session target ipv4:1.14.120.109fax protocol t38 ls-redundancy 0 hs-redundancy 0! Outbound peer for T.37 onramp operationdial-peer voice 72 mmoippreference 2! The application name below must be exactly as shown!application fax_on_vfc_onramp_ap out-bounddestination-pattern 3746096session target mailto:$d$@mail-server.cisco.cominformation-type faxThe following examples show configuration for NM-HDV T.38 on the Cisco 2600 series router and Cisco 3600 series router.
fax interface-type fax-mailservice timestamps debug uptimeservice timestamps log uptimehostname fax-gatewayenable password lab!username betatest password 0 passwordip subnet-zeroip host dirt 223.255.254.254ip host faxgate_smtp_server 172.28.129.150ip domain-name cisco.comip name-server 1.14.116.1! used for fallback from T.38 fax relay to T.37 faxvoice hunt user-busy! global service for fax relayvoice service voipfax protocol t38 ls_redundancy 0 hs_redundancy 0call application voice app_libretto_offramp tftp://dirt/libretto-test/app_libretto_offramp5.tclcall application voice app_libretto_offramp authen-list faxcall application voice app_libretto_offramp authen-method gatewaycall application voice app_libretto_offramp accounting-list faxcall application voice app_onramp tftp://dirt/nchen/onramp13.nc.tclcall application voice app_onramp authen-list faxcall application voice app_onramp authen-method gatewaycall application voice app_onramp language 1 encall application voice app_onramp accounting-list faxcall application voice app_onramp set-location en 0 tftp://dirt/cchiu/WV/en_new/call application voice app_lib_rollover tftp://dirt/libretto-test/ fax_rollover_on_busy.tclfax receive called-subscriber $d$fax send transmitting-subscriber $s$fax send left-header $s$fax send center-header $t$fax send right-header Page: $p$fax send coverpage enablefax send coverpage email-controllablefax send coverpage comment Cisco cover page commentmta receive aliases [1.14.120.2]mta send server faxgate_smtp_servermta send subject "SN testing on T1 CAS FGD"mta send origin-prefix Cisco Faxmta send postmaster postmaster nchen@cisco.commta send mail-from hostname faxgate_testmta send mail-from username fax-usermta send return-receipt-to hostname return.host.commta send return-receipt-to username $s$mta receive aliases bock.cisco.commta receive aliases cisco.commta receive maximum-recipients 200mta receive generate-mdncontroller T1 1/1framing esfclock source line primarylinecode b8zsds0-group 0 timeslots 1-24 type e&m-fgdinterface Ethernet0ip address 1.14.120.2 255.255.0.0no ip directed-broadcastinterface FastEthernet0no ip addressno ip directed-broadcastshutdownduplex autospeed autoip default-gateway 1.14.0.1ip classlessip route 223.255.254.0 255.255.255.0 1.14.0.1no ip http servervoice-port 1/1:0! Inbound peer for T.37 onramp operationdial-peer voice 2 potsapplication app_onrampincoming called-number 5......direct-inward-dialport 1/1:0!! Outbound peer for T.37 onramp operationdial-peer voice 3 mmoip! The application name below must be exactly as shown!application fax_on_vfc_onramp_ap out-bounddestination-pattern 57108..session target mailto:$d$@mail-server.cisco.com! MDN and DSN configuration can be set in this peer! Inbound peer for T.37 offramp operationdial-peer voice 21 mmoipapplication app_libretto_offrampincoming called-number 5......information-type fax!! Outbound peer for T.37 offramp operationdial-peer voice 20 potsdestination-pattern 5......port 1/1:0prefix 5The following set of 3 peers are for onramp T.38 fax rollover to T.37 fax. Rollover occurs when the destination fax line is busy. The following configuration command must be set for T.38 rollover to T.37.
voice hunt user-busy! Inbound peer for T.38/T.37 onramp rollover operation! This peer includes the TCL application for rollover operationdial-peer voice 70 potsapplication app_lib_rolloverincoming called-number 5......port 1/1:0! Outbound peer for T.38 ingress gateway! This peer requires lower preference number then next matching peerdial-peer voice 71 voippreference 1destination-pattern 3746096session target ipv4:1.14.120.109fax protocol t38 ls_redundancy 0 hs_redundancy 0! Outbound peer for T.37 onramp operationdial-peer voice 72 mmoippreference 2! The application name below must be exactly as shown!application fax_on_vfc_onramp_ap out-bounddestination-pattern 3746096session target mailto:$d$@mail-server.cisco.cominformation-type fax!Command Reference
This section documents modified commands used with the T.37/T.38 Fax Gateway feature. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
Modified
fax interface-type
To enable the T.37 functionality (Store-and-Forward Fax), use the fax interface-type command in configuration mode. To disable T.37 functionality, use the no form of this command.
fax interface-type {fax-mail }
no fax interface-type {fax-mail }
Syntax Description
Defaults
The default is determined by the hardware available in the router and is fax-mail when used in a router having only voice modules.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the fax interface-type fax-mail command to set the voice module in the router as the interface through which to send and receive fax messages.
Examples
The following example shows the interface configured for fax mail:
Router# fax interface-type fax-mailRelated Commands
fax interface-type modem
Sets the type of interface for the fax to a modem in the Cisco AS5300 Universal Access Server using a modem.
Glossary
AAA—Authentication, Authorization, and Accounting. AAA is a suite of network security services which provides the primary framework through which access control can be set up on a Cisco router or universal access server.
ANI—Automatic Number identification.
CED—Called station identification. A 3-second, 2100 Hz tone generated by a fax machine answering a call, which is used in the hand-shaking used to set the call; the response from a called fax machine to a CNG tone.
CLI—Command Language Interpreter. Basic Cisco IOS configuration and management interface.
CNG—the 1100Hz tone that a fax machine uses to signal to a caller (human) that the calling party is a fax. The tone cycles on for .5 second, and then off for 3 seconds, for up to 30 seconds. This is part of the T.30 specification.
Dial peer—an addressable call endpoint. In Voice over IP (V0IP), there are two types of dial peers: POTS and VoIP.
DNIS—Dialed Number Identification Service.
DSN—Delivery Status Notification (RFC1891).
DSP—digital signal processor. This term is used to refer to the actual microprocessor on which the modulation/demodulation process is executed.
DTMF—Dual Tone Multiple Frequency.
E.164—eight-byte public network addressing recommendation defined by the International Telecommunication Union (ITU-T) for international telecommunication numbering.
ESMTP—Extended SMTP. A method for extending SMTP to include richer mail features such as delivery notification, capabilities negotiation and session delivery
Fallback—fax delivery mode where the receiver is busy. The fax is delivered to a disk server and delivered in s&f mode.
Fax mail—an SMTP or ESMTP e-mail message that is produced by a T.37 onramp gateway or an e-mail message sent to a T.37 offramp gateway.
Fax relay—a mechanism on Cisco VoIP gateways to locally terminate a fax call on the Digital Signal Processor (DSP), essentially emulating the remote fax machine; the fax is then transmitted over IP in a real-time manner.
FTSP —Fax Telephony Service Provider.
H.323—an International Telecommunication Union (ITU-T) standard that describes packet-based video, audio, and data conferencing. H.323 is an umbrella standard that describes the architecture of the conferencing system, and refers to a set of other standards (H.245, H.225.0, and Q.931) to describe its actual protocol.
IVR—Interactive Voice Response.
MIME—Multipurpose Internet Mail Extensions. A standard MIME e-mail message is created and attached with the TIFF file to form a fax mail to the messaging infrastructure of a designated SMTP server.
MMoIP—Multimedia Mail over Internet Protocol. Dial peer specific to Store-and-Forward Fax. The MMoIP dial peer is the vehicle you use to assign particular line characteristics (such as a destination telephone number) to the connection between the Cisco voice gateway and the SMTP mail server during on-ramp faxing.
MSP—Media Service Provider.
MTA—Mail Transfer Agent.
Offramp—the function of converting an Internet image format into a suitable Group 3 format and transmitting it over the PSTN.
Onramp —the function of receiving a Group 3 fax image and converting it into a format suitable for Internet transmission.
POTS—Plain Old Telephone Service. Basic telephone service supplying standard single-line telephones, telephone lines, and access to the public switched telephone network.
PSTN—Public Switched Telephone Network.
RDNIS—Redirected DNIS. Number that identifies the original dialed number of a call that is redirected to a voice, fax, or e-mail server, usually because the number is busy or does not answer. RDNIS is carried in the Cisco proprietary data fields in H.323-standard signalling protocols over the packet network to the server.
RTP—real-time transport protocol. Defined by RFC 1890, a session-layer protocol used in IP networks for real-time traffic such as voice and video.
RTSP—Real-time Streaming Protocol.
Redialer—An interface hardware device that interconnects between a fax device and a PSTN network that maps the numbers that a user dials to reach a specific destination to a different number, and forwards the dialed digits to that new number, transparent to the user.
S&F Fax—delivery mode where the fax is stored on a disk server and delivered some time after the sender disconnected.
SMTP—Simple Mail Transport Protocol.
SPI—service provider interface.
T.33—ITU Recommendation T.33 defines application rules for the routing of Group 3 facsimile messages using the Subaddress (SUB) signal as defined in Recommendation T.30. The aspects that are addressed include placement of telephone address components (phone extensions and secondary dialing numbers) within the SUB frame, encoding and decoding rules, and an outline of the facsimile routing procedure.
T.37—ITU Recommendation T.37 describes the features necessary for the Store-and-Forward 'Simple' mode of operation of facsimile document transmission via Internet Mail. The general guidelines for the modes of operation of facsimile over the Internet are contained in Recommendation F.185.
T.38—ITU Recommendation T.38 describes the features necessary to transfer facsimile documents in real-time between two standard Group 3 facsimile terminals over the Internet or other networks using IP protocols. The recommendation allows the use of either TCP or UDP depending on the service environment.
T.4—Standardization of Group 3 facsimile terminals for document transmission
TCL—Tool Command Language. Language in which IVR scripts are written.
TFTP—Trivial File Transfer Protocol. Method used to copy files to and from routers.
TIFF-f—Tagged Image File Format for Fax (profile f)
TSP—Telephony Service Provider
UM—Unified Message
UOne—Unified Open Network Exchange
VIC—Voice interface card
TSP—Telephony Service Provider
VIC—Voice interface card
VGW—Cisco Voice Gateway
VWIC—Voice/WAN interface card
Guest
