Summary of the content on the page No. 1
Avaya Solution & Interoperability Test Lab
®
Application Notes for Configuring Multi-Tech FaxFinder IP
®
Fax Server with Avaya Aura Communication Manager and
®
Avaya Aura Session Manager via SIP Trunk Interface
- Issue 1.0
Abstract
®
These Application Notes describe the procedures for configuring the Multi-Tech FaxFinder
® ®
IP Fax Server with Avaya Aura Communication Manager and Avaya Aura Session Manager
using a SIP trunk interface.
FaxFinder is an applian
Summary of the content on the page No. 2
1. Introduction ® These Application Notes describe the procedures for configuring Multi-Tech FaxFinder IP Fax ® ® Server with Avaya Aura Communication Manager and Avaya Aura Session Manager. FaxFinder is an appliance-based fax server solution that sends and receives faxes over an IP network. FaxFinder utilizes T.38 Fax over Internet Protocol (FoIP) for sending media. In the tested ® configuration, FaxFinder interoperated directly with Avaya Aura Session Manager to send/receive faxes u
Summary of the content on the page No. 3
Platform DSP Resources DSP Resources Device per Platform Device per FoIP Call TN2302, G450, MM760 64 4 TN2602 64 1 Note that the SIP trunk group on Communication Manager for connecting to Session Manager at each site, as well as the SIP or ISDN-PRI trunk group for connecting the 2 sites must be configured with adequate number of trunk group members to support the number of simultaneous fax calls intended. 2.4. Support Technical support for FaxFinder can be obtained by contactin
Summary of the content on the page No. 4
3. Configuration The test configuration was designed to emulate two separate sites with multiple Port Networks at one site, and modular Gateway resources at the other site. Each site was configured with Multi-Tech ® ® ® FaxFinder IP Fax Server, Avaya Aura Communication Manager and Avaya Aura Session Manager. Figure 1 illustrates the configuration used in the tested configuration. 3.1. Configuration Details In the tested configuration, Communication Manager Servers and Gateways at the t
Summary of the content on the page No. 5
Site B had an Avaya S8300 Communication Manager Server in an Avaya G450 Media Gateway. The FaxFinder server at this site communicated with Session Manager via SIP. On the Avaya G450 Media Gateway, the signaling and media resources supporting a SIP trunk connected to Session Manager were integrated directly on the media gateway processor. Endpoints at this site included Avaya 9600 Series IP Telephones (with H.323 and SIP firmware), and an analog fax machine. The IP telephones were not invo
Summary of the content on the page No. 6
4. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration provided: Equipment Software/Firmware ® Avaya S8800 Servers (at both sites) Avaya Aura Session Manager 6.0 (6.0.2.0.602004) 6.1 (6.1.2.0.612004) ® Avaya Aura System Manager 6.0, 6.1 ® Avaya S8800 Server (at Site A) Avaya Aura Communication Manager 6.0 SP1 R016x.00.0.345.0 with patch 18567 Avaya G650 Media Gateway (at Site A) - 2 CLANs TN799DP - HW01 FW38 & HW1
Summary of the content on the page No. 7
® 5. Configure Avaya Aura Communication Manager This section describes the Communication Manager configuration necessary to interoperate with Session Manager and Multi-Tech FaxFinder® IP Fax Server. Connectivity via SIP and PRI trunks between the two sites used existing configurations which follow standard practices. Therefore, it focuses on the configuration of the SIP trunks connecting Communication Manager to the Avaya SIP infrastructure with the following assumption: The examples
Summary of the content on the page No. 8
Step Description 1. Verify Communication Manager License Use the display system-parameters customer-options command to verify that the Communication Manager license has proper permissions for features illustrated in these Application Notes. Navigate to Page 2, and verify that there is sufficient remaining capacity for SIP trunks by comparing the Maximum Administered SIP Trunks field value with the corresponding value in the USED column. The license file installed on the system
Summary of the content on the page No. 9
Step Description 2. Identify IP Interfaces Use the list ip-interface clan and list ip-interface medpro commands to identify IP interfaces in each network region. Interfaces in cabinet 01 (port network 1) as indicated in the Slot field are in IP network region 1 as indicated in the Net Rgn field. Testing with the TN2302 and TN2602 circuit packs were done separately. When testing with the TN2302, the TN2602 was disabled (turned off) and vice versa as indicated in the ON field. list i
Summary of the content on the page No. 10
Step Description 3. Administer IP Network Region 1 The configuration of the IP network regions (Steps 3 – 6) was already in place and is included here for clarity. At Site A, the Avaya G650 Media Gateway comprising port network 1 and all IP endpoints were located in IP network region 1. Use the display ip-network-region command to view these settings. A descriptive name was entered for the Name field. IP-IP Direct Audio (Media Shuffling) was enabled to allow audio traffic to be
Summary of the content on the page No. 11
Step Description 4. Administer IP Network Region 1 – Continued On Page 4, codec sets are defined for inter-region calls. In the case of the compliance test at Site A, calls from IP network Source Region 1 to IP network region 2 (dst rgn 2) used codec set 1. The default values were used for all other fields. At Site B, only one IP network region was used, so no inter-region settings were required. display ip-network-region 1 Page 4 of 20 Source
Summary of the content on the page No. 12
Step Description 7. Administer IP Node Name Use the change node-names ip command to create a node name that maps to the Session Manager IP address. This node name is used in the configuration of the SIP trunk signaling group in Step 11. change node-names ip Page 1 of 2 IP NODE NAMES Name IP Address CLAN1A 10.64.22.16 CLAN2A 10.64.22.19 CM-Remote 10.
Summary of the content on the page No. 13
Step Description 10. Administer IP Codec set – Fax settings On Page 2, set the FAX Mode field to t.38-standard. This is necessary to support the FaxFinder server assigned to IP network region 2. The Modem Mode field should be set to off. Leave the FAX Redundancy setting at its default value of 0. A packet redundancy level can be assigned to improve packet delivery and robustness of FAX transport over the network (with increased bandwidth as trade-off). Avaya uses IETF RFC-2198 and
Summary of the content on the page No. 14
Step Description 11. Administer SIP Signaling Group For the compliance test, a signaling group with the associated SIP trunk group was used for routing fax calls to/from the FaxFinder server via Session Manager. For the compliance test at Site A, signaling group 12 was configured using the parameters highlighted below. All other fields were set as described in [3]. The Group Type was set to sip. The Transport Method was set to the recommended default value of tls (Transport Lay
Summary of the content on the page No. 15
Step Description 12. Administer SIP Trunk Group For the compliance test, trunk group 12 with the associated signaling group was used for routing fax calls to/from Session Manager. Trunk group 12 was configured using the parameters highlighted below. All other fields were set as described in [3]. On Page 1: The Group Type field was set to sip. A descriptive name was entered for the Group Name. An available trunk access code (TAC) that was consistent with the existing dial plan
Summary of the content on the page No. 16
Step Description 13. Administer SIP Trunk Group – continued On Page 3: Set the Numbering Format field to public. This field specifies the format of the calling party number sent to the far-end. Default values may be used for all other fields. change trunk-group 12 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Maintenance Tests? y
Summary of the content on the page No. 17
Step Description 15. Administer Route Pattern Use the change route-pattern command to create a route pattern that will route fax calls to the SIP trunk that connects to the FaxFinder server. The example below shows the route pattern used for the compliance test at the Main Site. A descriptive name was entered for the Pattern Name field. The Grp No field was set to the trunk group created in Steps 12–13. The Facility Restriction Level (FRL) field was set to a level that allows acces
Summary of the content on the page No. 18
® 6. Configure Avaya Aura Session Manager - Overview This section covers the configuration of Session Manager at Site A. Session Manager is configured via an Internet browser using the administration web interface. It is assumed that the setup screens of the administration web interface have been used for initial configurations. For additional information on these installation tasks, refer to [3]. Each SIP endpoint used in the compliance test that registered with Session Manager required
Summary of the content on the page No. 19
6.1. Configure Session Manager - Details This section summarizes the applicable user-defined parameters used during the SIP installation procedures. Step Description 1. Login Access the System Manager administration web interface by entering https:///SMGR as the URL in an Internet browser, where is the IP address (or FQDN) of the System Manager server. Log in with the appropriate credentials. 2. Create a SIP Entity for the FaxFinder Server Navigate
Summary of the content on the page No. 20
Step Description 3. Create a SIP Entity for the FaxFinder Server - Continued Enter a descriptive Name such as RB_FaxServer and enter the FQDN or IP Address for the FaxFinder server as shown below. Select Other for the Entity Type. All other settings were defaults. 4. Create an Entity Link for the FaxFinder Server An Entity Link establishes the details of how Entities will communicate with each other. Use the Add button to create a new link. In this case, Session Manager at th
