Avaya Multi-Tech FaxFinder Application Notes
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Software
  5. Multi-Tech FaxFinder s
  6. Application notes
Avaya Multi-Tech FaxFinder Application Notes

Avaya Multi-Tech FaxFinder Application Notes

For configuring multi-tech faxfinder ip fax server via sip trunk interface
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Avaya Solution & Interoperability Test Lab
Application Notes for Configuring Multi-Tech FaxFinder
Fax Server with Avaya Aura
®
Avaya Aura
- Issue 1.0
These Application Notes describe the procedures for configuring the Multi-Tech FaxFinder
IP Fax Server with Avaya Aura
using a SIP trunk interface.
FaxFinder is an appliance-based fax server that sends and receives fax calls over an IP
network. In the tested configuration, FaxFinder interoperated with Avaya Aura
Manager to send/receive faxes using SIP trunk facilities.
Information in these Application Notes has been obtained through DevConnect compliance
testing and additional technical discussions. Testing was conducted via the DevConnect
Program at the Avaya Solution and Interoperability Test Lab.
RAB; Reviewed:
SPOC 7/12/2011
Session Manager via SIP Trunk Interface
®
Communication Manager and Avaya Aura
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
®
Communication Manager and
Abstract
®
IP
®
®
Session Manager
®
Session
1 of 34
FaxFinder_SM61

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Multi-Tech FaxFinder and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Avaya Multi-Tech FaxFinder

Summary of Contents for Avaya Multi-Tech FaxFinder

  • Page 1 SIP trunk interface. FaxFinder is an appliance-based fax server that sends and receives fax calls over an IP ® network. In the tested configuration, FaxFinder interoperated with Avaya Aura Session Manager to send/receive faxes using SIP trunk facilities.

  • Page 2: Test Results

    Session Manager and FaxFinder restarts. Fax calls were also tested with different Avaya Media Gateway media resources used to process the fax data between sites. This included the TN2302 MedPro circuit pack, the TN2602 MedPro circuit pack in the Avaya G650 Media Gateway;...
  • Page 3 Technical support for FaxFinder can be obtained by contacting Multi-Tech Systems at:  Phone: (800) 972-2439 or (763) 717-5863  Email: support@multitech.com  Web: https://support.multitech.com RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 3 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...

  • Page 4: Configuration Details

    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.
  • Page 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.

  • Page 6: Equipment And Software Validated

    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 & HW13 FW 38 2 MedPros – TN2302 TN2302AP - HW20 FW120 2 MedPros –...
  • Page 7 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: ...
  • Page 8 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 controls the maximum permitted. If there is insufficient capacity, contact an authorized Avaya sales representative to make the appropriate changes display system-parameters customer-options...
  • Page 9 10.64.22.15 n 02A02 TN2302 MEDPRO2A Gateway001 10.64.22.18 y 01A04 TN2602 MEDPRO1A-2 Gateway001 10.64.22.17 y 02A04 TN2602 MEDPRO2A-2 Gateway001 10.64.22.20 RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 10 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.
  • Page 11 Inter Network Region Connection Management dst codec direct WAN-BW-limits Video Intervening Units Total Norm Prio Shr Regions NoLimit n all NoLimit n all RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 11 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 12 1 of IP Codec Set Codec Set: 1 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 13 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 ITU-T T.38 specifications as redundancy standard. With this standard, each Fax over IP packet is sent with additional (redundant) 0 to 3 previous fax packets based on the redundancy setting.

  • Page 14: Signaling Group

    The Far-end Network Region was set to 2. This is the IP network region which contains Session Manager and FaxFinder.  The Far-end Domain was set to avaya.com. This domain is sent in the headers of SIP INVITE messages for calls originating from and terminating to Session Manager using this signaling group.
  • Page 15 Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: auto Signaling Group: 12 Number of Members: 50 RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 15 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...

  • Page 16: Trunk Features

    Note: If an entry applies to a SIP connection to Avaya Aura(tm) Session Manager, the resulting number must be a complete E.164 number. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 17 AAR DIGIT ANALYSIS TABLE Location: all Percent Full: 1 Dialed Total Route Call Node String Pattern Type Reqd 40000 45000 RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 17 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 18 These procedures are covered in [3]. This section summarizes the configuration steps that are necessary for interoperating with Multi- Tech FaxFinder® IP Fax Server. The test environment was previously configured to enable Avaya ® Aura Communication Manager and Session Manager at each site to communicate with each other.
  • Page 19 Navigate to Routing\SIP Entities and click New to create an Entity definition. In the screenshot below, the Entity RB_FaxServer was previously created using the following settings. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 19 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 20 Use the Add button to create a new link. In this case, Session Manager at the Main Site, demoSM, was configured to communicate with RB_FaxServer using UDP protocol over port 5060 as a Trusted Entity. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 20 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 21 Below are the settings used for this test. Use the Select or Add buttons to create or use existing definitions for each parameter. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 21 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 22 The ‘40’ and ‘45’ dial patterns were created for this test, all others were in place in the test environment. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 22 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 23 Dial Pattern 45. This was used to route calls from the Main Site Fax Server to the Remote Site Fax Server. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 23 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 24 The examples shown in this section refer to Site A. Unless specified otherwise, these same steps also apply to Site B using values appropriate from Figure 1. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 24 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 25 RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 25 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 26 Click Set and Save when entries are completed in each section. Below is an example of the settings used in the tested configuration: RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 26 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 27 To add a share, click the Add link and provide the path and credentials for the share. The share was previously configured, however the Edit dialog shown below looks similar to the Add dialog: RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 27 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 28 Session Manager in the SIP section. Note that at this time, UDP is the only option for communications with Session Manager. Default T.38 settings were used in the compliance tests. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 28 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 29 A default destination can be defined if no other routing policies apply: A Recipient Routing rule will automatically be created when users are configured (in the following Step 3). RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 29 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 30 Enable Outbound Approval setting, and selecting a User to approve outbound faxes: RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 30 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...
  • Page 31 In the tested configuration, these were used to simplify sending proceedures. See the Administration Guide [4] for complete instructions on managing contacts. RAB; Reviewed: Solution & Interoperability Test Lab Application Notes 31 of 34 SPOC 7/12/2011 ©2011 Avaya Inc. All Rights Reserved. FaxFinder_SM61...

  • Page 32: Verification Steps

    ®  From Avaya Aura System Manager, confirm that the Entity Link between Avaya Aura Session Manager and the FaxFinder server is in service.  From the FaxFinder web interface, navigate to Status & Logs > Fax Status to see the...

  • Page 33: Additional References

    245-205, Release 6.0, Issue 8.0, June, 2010. [2] Administering Avaya Aura™ Communication Manager, Doc # 03-300509, Release 6.0, Issue 6.0, June, 2010. [3] Administering Avaya Aura™ Session Manager, Doc # 03-603324, Release 6.0, Issue 3, August, 2010. ® [4] FaxFinder IP...
  • Page 34 2011 Avaya Inc. All Rights Reserved. © Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice.

This manual is also suitable for:

Aura communication managerAura session manager

Table of Contents