Avaya Multi-Tech FaxFinder s Suplemento

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

1 of 34

FaxFinder_SM61

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

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

Solution & Interoperability Test Lab Application Notes

2 of 34

FaxFinder_SM61

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 using SIP signaling.

2. General Test Approach and Test Results

This section describes the compliance test approach used to verify interoperability of Multi-Tech

FaxFinder® IP Fax Server.

2.1. General Test Approach

The general test approach was to make intra-site and inter-site fax calls to and from FaxFinder. The

inter-site calls were made using SIP or ISDN-PRI trunks between the sites. Faxes were sent with

various page lengths, resolutions, and at various fax data speeds. For capacity, a large number of

multi-page faxes were continuously sent between the two FaxFinder servers simultaneously.

Serviceability testing included verifying proper operation/recovery from failed cables, unavailable

resources, and 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;

the integrated VoIP engine of the Avaya G450 Media Gateway and the Avaya MM760 Media

Module installed in the Avaya G450 Media Gateway.

2.2. Test Results

Multi-Tech FaxFinder® IP Fax Server successfully passed compliance testing.

2.3. General Observations

Fax calls consume DSP (Digital Signal Processing) resources for processing fax data on the

TN2302AP IP Media Processor (MedPro) circuit pack and the TN2602AP IP Media Processor

circuit pack in the Avaya G650 Media Gateway, and the integrated Voice over Internet Protocol

(VoIP) engine of the Avaya G450 Media Gateway. To increase the capacity to support simultaneous

fax calls, additional TN2302AP and/or TN2602AP MedPro circuit packs need to be installed in the

Avaya G650 Gateway, and additional Avaya MM760 Media Module or Modules need to be installed

in the Avaya G450 Media Gateway. The information contained in the table below indicates DSP

capacities/usage in the Avaya media processors. Customers should work with their Avaya sales

representatives to ensure that their fax solutions have adequate licenses and DSP resources to match

the intended Fax capacity/usage.

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

3 of 34

FaxFinder_SM61

Platform

Device

DSP Resources

per Platform Device

DSP Resources

per FoIP Call

TN2302, G450, MM760

TN2602

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 contacting Multi-Tech Systems at:

Phone: (800) 972-2439 or (763) 717-5863

Email: support@multitech.com

Web: https://support.multitech.com

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

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.

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

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.

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

6 of 34

FaxFinder_SM61

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

-2 MedPros –TN2302

-2 MedPros –TN2602

TN799DP - HW01 FW38 & HW13 FW 38

TN2302AP - HW20 FW120

TN2602AP - HW02 FW057

Avaya S8300D Server (at Site B)

Avaya Aura®Communication Manager 6.0 SP2

R016x.00.1.510.1 with patch 18734

Avaya G450 Media Gateway (at Site B)

30.14.0/1

Avaya 9620 IP Telephone (SIP)

Avaya 9630 IP Telephone (H.323)

Avaya one-X®Deskphone Edition SIP 2.5

H.323 3.11

Analog Fax Machines

Multi-Tech FaxFinder® IP Fax Server

1.0.14

Multi-Tech FaxFinder® Client software

2.2.2

The Multi-Tech FaxFinder® IP Fax Server is shipped as an all-in-one appliance. The physical

dimensions are 9.1” W x 6.1” L x 1.7” H, roughly the size of a modem.

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

7 of 34

FaxFinder_SM61

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 shown in this section refer to Site A. Unless specified otherwise, these same

steps also apply to Site B using values appropriate for that location.

The configuration of Communication Manager was performed using the System Access Terminal

(SAT). After the completion of the configuration, the save translation command was used to make

the changes permanent.

5.1. Steps to Configure Communication Manager

The configuration on Communication Manager include the following areas:

Verify Communication Manager License (Step 1)

Identify IP Interfaces (Step 2)

Administer IP Network Regions (Steps 3 –6)

Administer IP Node Name (Step 7)

Administer IP Network Map (Step 8)

Administer IP Codec Set (Steps 9 –10)

Administer SIP Signaling Group (Step 11)

Administer SIP Trunk Group (Steps 12 –13)

Administer Public Unknown Numbering (Step 14)

Administer Route Pattern (Step 15)

Administer AAR Analysis (Steps 16 –17)

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

8 of 34

FaxFinder_SM61

Step

Description

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 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 2 of 11

OPTIONAL FEATURES

IP PORT CAPACITIES USED

Maximum Administered H.323 Trunks: 12000 96

Maximum Concurrently Registered IP Stations: 18000 1

Maximum Administered Remote Office Trunks: 12000 0

Maximum Concurrently Registered Remote Office Stations: 18000 0

Maximum Concurrently Registered IP eCons: 414 0

Max Concur Registered Unauthenticated H.323 Stations: 100 0

Maximum Video Capable Stations: 18000 0

Maximum Video Capable IP Softphones: 18000 0

Maximum Administered SIP Trunks: 24000 298

Maximum Administered Ad-hoc Video Conferencing Ports: 24000 0

Maximum Number of DS1 Boards with Echo Cancellation: 522 0

Maximum TN2501 VAL Boards: 128 2

Maximum Media Gateway VAL Sources: 250 0

Maximum TN2602 Boards with 80 VoIP Channels: 128 0

Maximum TN2602 Boards with 320 VoIP Channels: 128 2

Maximum Number of Expanded Meet-me Conference Ports: 300 0

(NOTE: You must logoff & login to effect the permission changes.)

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

9 of 34

FaxFinder_SM61

Step

Description

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 ip-interface medpro

IP INTERFACES

Net

ON Slot Code/Sfx Node Name/ Mask Gateway Node Rgn VLAN Virtual Node

IP-Address

-- ----- -------- --------------- ---- --------------- --- ---- ---------------

n 01A02 TN2302 MEDPRO1A /24 Gateway001 1 n

10.64.22.15

n 02A02 TN2302 MEDPRO2A /24 Gateway001 2 n

10.64.22.18

y 01A04 TN2602 MEDPRO1A-2 /24 Gateway001 1 n

10.64.22.17

y 02A04 TN2602 MEDPRO2A-2 /24 Gateway001 2 n

10.64.22.20

list ip-interface clan

IP INTERFACES

Skts Net Eth

ON Slot Code/Sfx Node Name/ Mask Gateway Node Warn Rgn VLAN Link

IP-Address

-- ---- -------- --------------- ---- --------------- ---- --- ---- ----

y 01A03 TN799 D CLAN1A /24 Gateway001 400 1 n 1

10.64.22.16

y 02A03 TN799 D CLAN2A /24 Gateway001 400 2 n 2

10.64.22.19

RAB; Reviewed:

SPOC 7/12/2011

Solution & Interoperability Test Lab Application Notes

10 of 34

FaxFinder_SM61

Step

Description

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 sent

directly between IP endpoints without using media resources in the Avaya Media

Gateway. This was done for both intra-region and inter-region IP-IP Direct Audio.

This is the default setting. Media Shuffling can be further restricted at the trunk level

on the Signaling Group form.

The Codec Set field was set to the IP codec set to be used for calls within this IP

network region. In this case, IP codec set 1 was selected.

The default values were used for all other fields.

At Site B, all IP components were located in IP network region 1 and the IP network

region was configured in the same manner as shown below.

display ip-network-region 1 Page 1 of 20

IP NETWORK REGION

Region: 1

Location: Authoritative Domain: avaya.com

Name: PN1

MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes

Codec Set: 1 Inter-region IP-IP Direct Audio: yes

UDP Port Min: 2048 IP Audio Hairpinning? n

UDP Port Max: 3329

DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y

Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS

Audio PHB Value: 46 Use Default Server Parameters? y

Video PHB Value: 26

802.1P/Q PARAMETERS

Call Control 802.1p Priority: 6

Audio 802.1p Priority: 6

Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS

H.323 IP ENDPOINTS RSVP Enabled? n

H.323 Link Bounce Recovery? y

Idle Traffic Interval (sec): 20

Keep-Alive Interval (sec): 5

Keep-Alive Count: 5

Este manual sirve para los siguientes modelos

Tabla de contenidos

Otros manuales de Software de Avaya

Avaya

Avaya IP Office Phone Manager Manual de usuario

Avaya

Avaya Integrated Management Manual técnico

Avaya

Avaya Aura Communication Manager Manual técnico

Avaya

Avaya iContact Manual de usuario

Avaya

Avaya CCC Report Manager Manual de usuario

Avaya

Avaya 40DHB0002USAR Manual de usuario

Avaya

Avaya IP Office Phone Manager Manual de usuario

Avaya

Avaya Media Gateway G350 Manual de usuario

Avaya

Avaya Call Management System Manual de usuario

Avaya

Avaya IP Office Conferencing Center 3.0 Manual de instrucciones

Avaya

Avaya IP Office CTI Link Manual de usuario

Avaya

Avaya Compact Contact Center V5 Manual de servicio

Avaya

Avaya IP Office Voicemail Pro Manual del producto

Avaya

Avaya CPSEE_TSP500 Manual de usuario

Avaya

Avaya SAB Manual de usuario

Avaya

Avaya PARTNER ACS R5.0 Manual de usuario

Avaya

Avaya Communication Manager Manual de servicio

Avaya

Avaya Customer Interaction Express 1.0 Manual de usuario

Avaya

Avaya IP Office Phone Manager Manual de usuario

Avaya

Avaya Unified Messenger Manual de usuario

Avaya

Avaya IP Office Phone Manager Manual de usuario

Avaya

Avaya Definity Enterprise Communications Server Manual de usuario

Avaya

Avaya one-X Quick Edition Manual de usuario

Avaya

Avaya PROGNOSIS IP s Suplemento

Manuales populares de Software de otras marcas

COMPRO

COMPRO COMPROFM Manual de usuario

Muratec

Muratec OFFICEBRIDGE ONLINE Manual de usuario

Oracle

Oracle Contact Center Anywhere 8.1 Manual de usuario

Adobe

Adobe 65007312 - Photoshop Lightroom Manual

HP ProLiant BL420c Manual de usuario

PS Audio

PS Audio PowerPlay Manual del propietario

Brady

Brady LOCKOUT PRO 3.0 Manual de servicio

Texas Instruments

Texas Instruments TI-83 Plus Silver Edition Manual

Novell

Novell GROUPWISE 8 - INTERNET AGENT Manual de usuario

Oracle

Oracle Application 9i Manual de usuario

Acer

Acer RDM Manual de usuario

Canon

Canon Vixia HF21 Manual de usuario

Canon

Canon ZR950 Manual de usuario

Samsung

Samsung Auto Backup Manual de usuario

Polycom

Polycom Vortex EF2201 Instrucciones de instalación y funcionamiento

Brocade Communications Systems

Brocade Communications Systems Brocade 8/12c Manual de usuario

Novell

Novell SP2 - S Manual de instrucciones

Lexmark

Lexmark Apps Manual de servicio