RAB; Reviewed:
SPOC 7/12/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
4 of 34
FaxFinder_SM61
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 two sites were
connected via SIP and ISDN-PRI trunks. Faxes were alternately sent between the two sites using
these two facilities. Connections to Session Manager were via SIP trunk facilities, and the FaxFinder
servers communicated directly with Session Manager via SIP.
Two separate Session Manager Servers were used to connect to the FaxFinder Servers at each site.
Figure 1: Multi-Tech FaxFinder
®
IP Fax Server sample configuration
Site A had an Avaya S8800 Communication Manager Server with two Avaya G650 Media
Gateways. Each Media Gateway was configured in a separate port networks with separate IP
network regions. The FaxFinder server at this site communicated with Session Manager via SIP. In
turn, Communication Manager used a SIP Trunk which terminated on a CLAN circuit pack in port
network 2 to communicate with Session Manager. IP media resources were provided by Media
Processor (MedPro) circuit packs. Two versions of the MedPro circuit pack were tested in this
configuration: TN2302AP and TN2602AP. Endpoints at this site included an Avaya 9600 Series IP
Telephone (with H.323 firmware), and an analog fax machine.
