RAB; Reviewed:
SPOC 7/12/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
5 of 34
FaxFinder_SM61
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 involved in the faxing operations, they were present in the configuration
to verify that VoIP telephone calls did not interfere with FoIP faxing operations.
Outbound fax calls originating from FaxFinder were sent to Session Manager first, then to
Communication Manager, via the configured SIP trunks. Based on the dialed digits, Communication
Manager directed the calls to the local fax machine, or the inter-site trunks (ISDN-PRI or SIP) to
reach the remote site. Inbound fax calls to FaxFinder were first received by Communication
Manager from the local fax machine or from across either ISDN-PRI or SIP trunks connected to the
remote Site. Communication Manager then directed the calls to FaxFinder via the configured
Session Manager SIP trunks.
