MJH; Reviewed:
SPOC 8/4/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
3 of 47
Sagemcom_SM61
Figure 1 illustrates the reference configuration used duri ng testing. In the reference
configuration, the two sites are connected via a direct SIP trunk a nd an ISDN-PRI trunk. Faxes
were sent between the two sites using either of these two trunk s, as dictated by each individual
test case.
Figure 1: XMediusFAX with Session Manager and Com munication Manager
At Site 1 consists of the following equipment:
An Avaya S8800 Server running Avaya Aura® Communicatio n Manager with two
Avaya G650 Media Gateways. Each media gateway i s configured as a separate port
network in separate IP network regions. The media r esources required are provided by
the IP Media Processor (MedPro) circuit packs. Two ver sions of the IP MedPro circuit
pack were tested in the configuration: the TN2302 AP and the TN2602AP.
An Avaya S8800 Server running Avaya Aura® System Manag er. System Manager
provides management functions for Session Manager.
An Avaya S8800 Server running Avaya Aura® Session Manager.
XMediusFAX running on a Windows 2008 R2 Enterpri se Server (SP1).
An analog fax machine.
Various Avaya IP endpoints (not all shown).
At Site 2 consists of the following equipment:
An Avaya S8300D Server running Avaya Aura® Communicatio n Manager in an Avaya
G450 Media Gateway. The signaling and media resources ne eded to support SIP trunks
are integrated directly on the media gateway processor.