Avaya SM61 User's Manual
Contents
1. Avaya S8800 Server at Site A Avaya Aura Communication Manager 6 0 SP1 R0O16x 00 0 345 0 with patch 18567 Avaya G650 Media Gateway at Site A 2CLANs 2 MedPros TN2302 2 MedPros TN2602 TN799DP HWO1 FW38 amp HW13 FW 38 TN2302AP HW20 FW120 TN2602AP HW02 FW057 Avaya S8300D Server at Site B Avaya Aura Communication Manager 6 0 SP2 R0O16x 00 1 510 1 with patch 18734 Avaya G450 Media Gateway at Site B 30 14 0 1 Avaya 9620 IP Telephone SIP Avaya one X Deskphone Edition SIP 2 5 Avaya 9630 IP Telephone H 323 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 amp Interoperability Test Lab Application Notes 6 of 34 2011 Avaya Inc All Rights Reserved 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 Man2. RAB Reviewed Solution amp Interoperability Test Lab Application Notes 10 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 4 Administer IP Network Region 1 Continued On Page 4 codec sets are defined for inter region calls In the case of the compliance test at Site A calls from IP network Source Region 1 to IP network region 2 dst rgn 2 used codec set 1 The default values were used for all other fields At Site B only one IP network region was used so no inter region settings were required display ip network region 1 Page Source Region 1 Inter Network Region Connection Management dst codec direct WAN BW limits Video Intervening Dyn ron set WAN Units Total Norm Prio Shr Regions CAC F it 2 al y NoLimit 3 5 Administer IP Network Region 2 At Site A IP network region 2 was created for Port Network 2 in a similar manner as IP network region 1 shown in Step 3 but with a different name This was the network region used for SIP Trunk connections to Session Manager display ip network region 2 IP NETWORK REGION Region 2 Location Authoritative Domain avaya com Name PN2 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 2329 DIFFSERV TOS PARAMETERS Call Control PHB Value 46 Audio PHB Value 46 Video PHB Value 26 802 1P Q PARAMETERS Cali
3. Access the tool by pointing your web browser to http lt ip_address gt The home page is displayed below Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout FaxFinder FF240 IP 8 Web Management Version 1 0 14 mia Dene 2205 Woodale Drive Mounds View MN 55112 U S A www multitech com Tel 763 785 3500 or 800 328 9717 Fax 763 785 9874 Technical Support 763 717 5863 or 800 972 2439 Online Support Portal support multitech com FTP site ftp multitech com Knowledge Base amp Resolutions System Configuration Configure Network Settings FaxFinder ships with a default network address so initial configuration needs to be performed from a browser on a host manually configured with an address on the same network segment Once connected navigate to System Configuration gt Network to assign an appropriate Hostname IP Address and other relevant network settings as shown below Click Save to commit the changes which will reboot the device To complete the remaining settings access the web configuration tool from a host that has access to the network segment of the newly configured address Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout System foie Network Configuration Configuration Hostname faxfinder avaya com Network Description SMTP Time IP Address 10 64 22 171 Printer Subne
4. or FQDN of the System Manager server Log in with the appropriate credentials AVAYA Avaya Aura System Manager 6 0 Log On Username admin Password Jocesees 2 Create a SIP Entity for the FaxFinder Server 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 AVAYA Avaya Aura System Manager 6 0 one eee ee ey Help About Change Password Log off Home Routing SIP Entities plElements SIP Entities gt Events THE EEE Edit New Duplicate Delete More Actions Commit Licenses Routing 10 Items Refresh Filter Enable Domains Name EPity FQDN or IP Address Locations CM_Juniper gt 10 64 21 111 cM Adaptations democm 10 64 20 40 cm SIP Entities demoSM a 10 64 20 31 Session Manager Entity Links mainLabG650 gt 10 64 22 19 cM Time Ranges mainLabS8300D d 10 64 21 41 CM Routing Policies MH FaxSitel 10 64 21 100 Dial Patterns MH FaxSite2 d 192 45 108 100 RB FaxServer gt 10 64 22 170 Regulamespresions Sonus GSX9000 10 64 20 83 WPIEVGLU SS Sonus NBS5200 10 64 20 81 gt Security gt System Manager Data selec iL None gt Users RAB Reviewed Solution amp Interoperability Test Lab Application Notes 19 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFin
5. 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61
6. Control 02 7p Priority ACERO BO 5 lj Iie eae 7s Video 802 1p Priority AUDIO RESOURCE RESERVATION PARAMETERS H 323 1P ENDPOINTS RSVP Enabled n H 323 Link Bounce Recovery Idle Traffic Interval sec Keep Alive Interval sec Keep Alive Count 6 Administer IP Network Region 2 Continued The inter region codec setting was created similarly to Step 4 display ip network region 2 Page Source Region 2 Inter Network Region Connection Management dst codec direct WAN BW limits Video Intervening Dyn ron set WAN Units Total Norm Prio Shr Regions CAC 1 1 y NoLimit 2 3 3 y NoLimit RAB Reviewed Solution amp Interoperability Test Lab Application Notes 11 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 7 Administer IP Node Name Use the change node names ip command to create a node name that maps to the Session Manager IP address This node name is used in the configuration of the SIP trunk signaling group in Step 11 change node names ip IP NODE NAMES Name IP Address CLANIA 0 64 22 16 CLAN2A 0 64 o S CM Remote Oe4 2210 Ma DemoSM 10 64 20 31 Gateway001 OGL eZ Al MEDPROI1A OG Olas S MEDPRO1A 2 O64 22 07 MEDPRO2A 0 64 22 18 MEDPRO2A 2 Dot 22220 TR18300 0 64 10 67 8 Administer IP Network Map Session Manager and the FaxFinder server were configured to be located in an IP network region different than the default region 1 The region was
7. The following steps may be used to verify the configuration From Avaya Aura Communication Manager SAT use the status signaling group command to verify that the signaling groups are in service From Communication Manager SAT use the status trunk group command to verify that the trunk groups are in service Verify that fax calls can be placed to from Multi Tech FaxFinder IP Fax Server servers at each site From Communication Manager SAT use the list trace tac command to verify that fax calls are routed to the expected trunks 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 amp Logs gt Fax Status to see the current status of each port and any inbound or outbound fax activity currently in progress Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout Status amp Logs help Pauni mon se sna ats mie enna resem ip Metaton fiat At Fax Status Tale ari Idle Reset Idle Idle Waiting For Ring R Waiting For Ring Waiting For Ring Mail Queue Mail Log Inbound Fax Log Outbound Fax Log Call Log oN OO ON Waiting For Ring Inbound Fax Status There is no Inbound Fax activity at this time Outbound Fax Status There is no Outbound Fax activity at this time Additional System Status information such as the status of
8. analysis command to create an entry in the AAR Digit Analysis Table for this purpose The example below shows entries previously created for the Main Site using the display aar analysis 0 command The 3 highlighted entry specifies that 5 digit dial string 40000 was to use route pattern 12 to route calls to the FaxFinder server at Site A via Session Manager The dial string 45000 the FaxFinder server at Site B used Route Pattern 15 to route calls between Communication Managers change aar analysis 0 Page il ONE 2 AAR DIGIT ANALYSIS TABLE Location all Percent Full 1 Dialed Total Route Call Node ANI SEEN Min Max Pattern Type Num Reqd 10 4 4 4 aar n 5 5 12 aar n 40000 5 5 12 aar n 45000 5 5 15 aar n RAB Reviewed Solution amp Interoperability Test Lab Application Notes 17 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 6 Configure Avaya Aura Session Manager Overview This section covers the configuration of Session Manager at Site A Session Manager is configured via an Internet browser using the administration web interface It is assumed that the setup screens of the administration web interface have been used for initial configurations For additional information on these installation tasks refer to 3 Each SIP endpoint used in the compliance test that registered with Session Manager required that a user and endpoint profile be created and associated with Session Manager This c
9. assigned using the change ip network map command In the case of the compliance test the IP addresses for these resources at the Main Site were assigned to IP network region 2 as shown in the example below At the Remote Site Session Manager and the FaxFinder server were located in the default IP network region 1 so it did not require an IP address map entry change ip network map Page IP ADDRESS MAPPING Subnet Network Emergency IP Address Region VLAN Location Ext 10 64 20 31 10 64 20 31 10 64 22 170 10 64 22 170 9 Administer IP Codec set Use the change ip codec set 1 command to verify that G 711MU or G 711A is contained in the codec list The example below shows the value used in the compliance test display ip codec set 1 WP Cocke 5er Caceres Seek Il Audio Silence Frames Packet Codec Suppression Per Pkt Size ms 1 G 711MU n 2 20 RAB Reviewed Solution amp Interoperability Test Lab Application Notes 12 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 10 Administer IP Codec set Fax settings On Page 2 set the FAX Mode field to 438 standard This is necessary to support the FaxFinder server assigned to IP network region 2 The Modem Mode field should be set to off 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 i
10. clicking the Add link from the dialog that appears when the Edit link is clicked in Global Routing this rule applies to all Faxes received in addition to any other routing rules Global Destinations a E Share 10 64 10 51 Fax2 Edit Delete 7 Done Add Destination Global Share if 0 64 10 51 Fax Browse Save A default destination can be defined if no other routing policies apply Add Destination Default Emailto User admin Save A Recipient Routing rule will automatically be created when users are configured in the following Step 3 RAB Reviewed Solution amp Interoperability Test Lab Application Notes 29 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_SM61 Step Description Fax Configuration Configure Outbound Rules Configuration is needed only if an archive of outbound faxes is to be used In the tested configuration outbound archiving was configured to save in PDF format to the network share that was used in the previous step for inbound fax delivery This was intermittently enabled and disabled by clicking on the Enable Outbound Archive selection on the Fax Configuration gt Outbound page Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout Confi uration All imul faxi h g A aimi taneous faxing to the same Tl
11. connectivity to Session Manager and network shares can be found on the Status amp Logs gt System Status page eer Printer Status a nE ane There are no Printers Outbound Fax Log ous a Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout Status amp Logs help System Status Current Time 05 18 2011 04 26 43 PM Fax Status Up Time 34 minutes Time Server Status Synchronized at 05 18 2011 03 57 45 PM offset 25 903463 sec SIP Register Sfatus Disabled Mail Queue Mail Log Network Share Status 10 64 10 51 Fax2 disconnected Additional status screens showing mail queues and logs inbound and outbound fax logs etc are also available not pictured from the Status and Logs web pages RAB Reviewed Solution amp Interoperability Test Lab Application Notes 32 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 9 Conclusion These Application Notes describe the procedures required to configure Multi Tech FaxFinder IP Fax Server interoperate with Avaya Aura Communication Manager and Avaya Aura Session Manager Multi Tech FaxFinder IP Fax Server successfully passed compliance testing 10 Additional References 1 Avaya Aura Communication Manager Feature Description and Implementation Doc 555 245 205 Release 6 0 Issue 8 0 June 2010 2 Administering Avaya Aura Communication Manager Doc 03 300509 Release 6 0
12. dialed numbers beginning with 2 the local analog fax machine at Site A dialed numbers beginning with 40 to route incoming Fax calls to the FaxFinder server at Site B dialed numbers beginning with 45 to route to Communication Manager at Site A in order to route via the public network interface between the sites In addition an existing 4 digit patterns beginning with 60 was used to route Fax calls to Communication Manager at the Main Site for routing via the public network interfaces to the analog machine at the Remote Site The 40 and 45 dial patterns were created for this test all others were in place in the test environment Welcome AM Avaya Aura System Manager 6 0 gt Elements Dial Patterns gt Events New Delete More Actions Commit gt Groups amp Roles Licenses Y Routing 9 Items Refresh Filter Enable Domains Pattern i Emergency Call SIP Domain Notes Locations avaya com avaya com to mainLabG650 Adaptations W ma e IS avaya com to democm SIP Entities avaya com Entity Links avaya com avaya com to Sonus GSx9000 Time Ranges Routing Policies avaya com Fax Server at Site 2 Dial Patterns F avaya com To Rob CM Analog Fax PEP EB Regular Expressions avaya com Fax Server at Site 1 Defaults gt Security gt System Manager Data Sele
13. 1 Alaw MG7 11 plaw Dial Prefix o Redundancy Level 3 Jitter Buffer Delay 300 msecs Max Buffer 4000 Max Datagram s Extension Source SIPTo Header Extension Digits Use All w Extension Length 0 Channel Reservation 4 Inbound Only 4 Outbound only Save RAB Reviewed Solution amp Interoperability Test Lab Application Notes 28 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder SM61 Step Description Fax Configuration Configure Inbound Routing Navigate to Fax Configuration gt Inbound Routing to define Global Default and specific Recipient routing rules For each rule a network share email address or printer can be defined for fax delivery Click on Edit in each section to define or modify the respective rules Below is a view of the rules used in the tested configuration Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout General Setup Email Size Limit 5000 K bytes Fax ytput Format PDF Email Fax Details Oo Global Routing s here in addition to regular routing Fax Destinations Action Share 10 64 10 51 Fax2 Edit Default Routing extension isn t found Fax Destinations ction Email to User admin Edit Add Import Export Delete All n Extension Name Fax Destinations oo Action o 40000 Default Share 10 64 10 51 Fax2 Edit Delete Global Routing was configured by
14. 11 Avaya Inc All Rights Reserved FaxFinder SM61 Step Description RAB Create a Routing Policy Navigate to Routing Routing Policies and click New to create a routing policy for incoming calls to the FaxFinder server The illustration below was captured after the Policy RB_Fax_Server_2 had been created and the following steps will describe how this policy was created Help About Change Password Lag off AVAYA Avaya Aura System Manager 6 0 Nia AE apaan aE nperis PR pana SeA jome Routing Routing Policies gt Elements Routing Policies gt Events Edit New Duplicate Delete More Actions 7 J Commit gt Groups amp Roles Licenses Routing 9 Items Refresh Filter Enable Domains Name Disabled Destination Notes Tonalin RB Fax Server 2 Adaptations to CMJuniper SIP Entities to demoCM Entity Links to Fax Server Site 1 Time Ranges RB_FaxServer CM_Juniper democm MH_FaxSitet MH_FaxSite2 mainLabG650 to Fax Server Site 2 to mainLabG650 to mainLabS8300D Dial Patterns to Sonus GSx9000 Regular Expressions to Sonus NBS5200 Defaults Routing Policies mainLabS8300D Sonus GSX9000 ooooooo080 Sonus NBS5200 Select All None gt Security gt System Manager Data gt Users A Routing Policy consists of a definition of the SIP Entity as Destination the Time of Day the policy applies and th
15. 72 2439 or 763 717 5863 Email support multitech com Web https support multitech com RAB Reviewed Solution amp Interoperability Test Lab Application Notes 3 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved 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 Analog Fax Machine 20000 Avaya 9630 Avaya 9630 SIP Telephone SIP Telephone 23xxx i 601x Analog Avaya 9630 Fax Machine IP Telephone 6006 600x SIP Entity Link Ga i gt 8 l Avaya G650 Media Gateway Port Network 1 Avaya Aura Layer 2 Switch Layef 2 Switch Communication Manager on Avaya Aura Avaya S8800 Server Comm
16. AVAYA Avaya Solution amp 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 Solution amp Interoperability Test Lab Application Notes 1 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved 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
17. Issue 6 0 June 2010 3 Administering Avaya Aura Session Manager Doc 03 603324 Release 6 0 Issue 3 August 2010 4 FaxFinder IP Administrator User Guide S000493A Version A Model FF240 IP Documentation for Avaya products may be found at http support avaya com Multi Tech products may be found at https support multitech com RAB Reviewed Solution amp Interoperability Test Lab Application Notes 33 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 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 The configurations technical data and recommendations provided in these Application Notes are believed to be accurate and dependable but are presented without express or implied warranty Users are responsible for their application of any products specified in these Application Notes Please e mail any questions or comments pertaining to these Application Notes along with the full title name and filename located in the lower right corner directly to the Avaya DevConnect Program at devconnect avaya com RAB Reviewed Solution amp Interoperability Test Lab Application Notes 34 of 34 SPOC 7 12
18. N FORMAT Total ESENE TEK CPN CPN Len Code Grp s Prefix Len Total Administered 6 Se ell 5 Maximum Entries 9999 5 2 5 5 4 5 Note If an entry applies to Sie 5 5 a SIP connection to Avaya 4 6 4 Aura tm Session Manager S a 5 the resulting number must be a complete E 164 number RAB Reviewed Solution amp Interoperability Test Lab Application Notes 16 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 15 Administer Route Pattern Use the change route pattern command to create a route pattern that will route fax calls to the SIP trunk that connects to the FaxFinder server The example below shows the route pattern used for the compliance test at the Main Site A descriptive name was entered for the Pattern Name field The Grp No field was set to the trunk group created in Steps 12 13 The Facility Restriction Level FRL field was set to a level that allows access to this trunk for all users that require it The value of 0 is the least restrictive level The default values were used for all other fields change route pattern 12 Page il Gz 3 Pattern Number 12 Pattern Name To SM SCCAN EN Secure S12 im Grp FRL NPA Pix Hop Toll No Inserted DESEXE No Miele Abie Ise DSL WsleaLies QSIG Dgts Intw ihe alr 0 n user 16 Administer AAR Analysis Automatic Alternate Routing AAR was used to route calls to FaxFinder via Session Manager Use the change aar
19. Save Enable Outbound Archive o Archive Format PDF Archive Directory 1 10 64 10 51 Fax2 Browse Save An Outbound approval rule was used to hold outbound faxes for a portion of the testing This was not a requirement but was a useful method for traffic test scenarios The approval setup simply requires a check on the Enable Outbound Approval setting and selecting a User to approve outbound faxes Fax Outbound Approval Setup cannguratan Enable Outbound Approval Approvers ers who apyove outbound faxes admin Approved Fax Numbers numbers that do not require approval matches any digit e g 1 SS5S 7O5 Hea Approved Users Users that do not require approval admin Remove Reminders Email reminder sent to approver s at the specified time s 30 minutes Remove 60 minutes Remove qaaa eee eee Outbound Approval Report M Enabled Report Format CSV v B Month ES Every Minute 113 a a JE very Day of Week A 14 a E Sunda z 1 115 z 2 Monday 2 E 3 Tuesday 4 Wednesday RAB Reviewed Solution amp Interoperability Test Lab Application Notes 30 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description Configure Users and Contacts Two users were configured an administrator admin and a standard user test Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout Users heip I FaxFinde
20. a 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 Solution amp Interoperability Test Lab Application Notes 2 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Platform DSP Resources DSP Resources Device per Platform Device per FoIP Call TN2302 G450 MM760 64 4 TN2602 64 l 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 9
21. ager to the Avaya SIP infrastructure with the following assumption e 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 e Verify Communication Manager License Step 1 e Identify IP Interfaces Step 2 e Administer IP Network Regions Steps 3 6 e Administer IP Node Name Step 7 e Administer IP Network Map Step 8 e Administer IP Codec Set Steps 9 10 e Administer SIP Signaling Group Step 11 e Administer SIP Trunk Group Steps 12 13 e Administer Public Unknown Numbering Step 14 e Administer Route Pattern Step 15 e Administer AAR Analysis Steps 16 17 RAB Reviewed Solution amp Interoperability Test Lab Application Notes 7 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 1 Verify Communication Manager License display system parameters customer options OPTIONAL FEATURES IIE TEXOURE CUNEINC JLIDIL ES Maximum Administered H 323 Trunks Maximum Concurrently Registered IP Stations Maximum Administ
22. ct All None gt Users RAB Reviewed Solution amp Interoperability Test Lab Application Notes 22 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 7 Create or Modify Dial Patterns Continued The entries required to create the new Dial Pattern for routing calls to the FaxFinder server at the Main Site are illustrated below The Pattern Min and Max number of digits and SIP Domain entries were used for this Dial Pattern definition Click Add to associate the dial pattern with an existing Routing Policy in this case the RB_Fax_Server_2 policy created in Step 5 above The Originating Location Name All was used in this case to apply this pattern regardless of originating locations In the same way a new Dial Pattern was created not shown and associated with the existing policy to route calls to Communication Manager at the Main Site for onward routing to remote site using the Dial Pattern 45 This was used to route calls from the Main Site Fax Server to the Remote Site Fax Server Dial Pattern Details General Pattern Min Max Emergency Call SIP Domain avaya com Notes Originating Locations and Routing Policies 1 Item Refresh Filter Enable Originating Routing Paea Routing Policy Routing Location Notes Policy Name Disabled Destination Policy Notes Originating Location Name 1 RB Fax Server 2 ALL Any L
23. der_ SM61 Step Description Create a SIP Entity for the FaxFinder Server Continued Enter a descriptive Name such as RB_ FaxServer and enter the FQDN or IP Address for the FaxFinder server as shown below Select Other for the Entity Type All other settings were defaults SIP Entity Details General Name RB_FaxServer FQDN or IP Address 10 64 22 170 Other Type R Notes Adaptation Location vi Time Zone America Denver Override Port amp Transport with DNS SRY SIP Timer B F in seconds Credential name Call Detail Recording SIP Link Monitoring SIP Link Monitoring Link Monitoring Enabled Proactive Monitoring Interval in seconds 900 Reactive Monitoring Interval in seconds 120 Number of Retries 1 4 Create an Entity Link for the FaxFinder Server An Entity Link establishes the details of how Entities will communicate with each other 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 Entity Links 1 Item Refresh Filter Enable g SIP Entity 1 Protocol Port SIP Entity 2 Port Trusted demosM UDP 5060 RB_FaxServer 5060 a ect All None Input Required RAB Reviewed Solution amp Interoperability Test Lab Application Notes 20 of 34 SPOC 7 12 2011 20
24. e Dial Patterns that will trigger this particular policy Below are the settings used for this test Use the Select or Add buttons to create or use existing definitions for each parameter Routing Policy Details Commit General Name RB Fax Server 2 Disabled Notes SIP Entity as Destination RB_FaxServer 10 64 22 170 Other Time of Day ada Remove view Gaps Overlaps 1 Item Refresh Filter Enable Ranking 1 Start Time End Time Notes 0 00 00 23 59 Time Range 24 7 ect All None Dial Patterns 1 Item Refresh Filter Enable Pattern a i Emergency Call SIP Domain Originating Location Notes 40 avaya com ALL ect All None Reviewed Solution amp Interoperability Test Lab Application Notes 21 of 34 SPOG 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_SM6 Step Description Create or Modify Dial Patterns Associating a dial pattern with a SIP Routing Policy instructs Session Manager how to route calls matching the administered Dial Pattern s In the test existing Routing Policies were modified for routing to endpoints or Entities at the Remote Site and new Dial Patterns were created to route to the Main Site and Remote Site Fax Servers using the existing and new routing policies In the snapshot below the Dial Patterns were previously created The applicable patterns were all 5 Digit extension patterns
25. ered Remote Office Trunks Maximum Concurrently Registered Remote Office Stations Maximum Concurrently Registered IP eCons Max Concur Registered Unauthenticated H 323 Stations Maximum Video Capable Stations Maximum Video Capable IP Softphones Maximum Administered SIP Trunks Maximum Administered Ad hoc Video Conferencing Ports Maximum Number of DS1 Boards with Echo Cancellation Maximum TN2501 VAL Boards Maximum Media Gateway VAL Sources Maximum TN2602 Boards with 80 VoIP Channels Maximum TN2602 Boards with 320 VoIP Channels Maximum Number of Expanded Meet me Conference Ports 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 DDE SOND DF EN SD ED RAB Reviewed SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved Solution amp Interoperability Test Lab Application Notes 8 of 34 FaxFinder_ SM61 Step Description 2 Identify IP Interfaces Use the list ip inte
26. es ip command see Step 7 above The Far end Node Name was set to demoSM This node name maps to the IP address of the Session Manager server as defined using the change node names ip command 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 Direct IP IP Audio Connections was set to y This field must be set to y to enable Media Shuffling on the trunk level see Step 3 on IP IP Direct Audio The DTMF over IP field was set to the default value of in band The default values were used for all other fields change signaling group 12 Page IOE is SIGNALING GROUP Group Number 12 Group Type sip IMS Enabled n Transport Method tls OSSD ia SIP Enabled LSP n IP Video n MeO SIS WikUL imeyie SRUNE2 yy Peer Detection Enabled y Peer Server SM Near end Node Name CLAN2A Far end Node Name demoSM Near end Listen Port 5061 Far end Listen Port 5061 Far end Network Region 2 Far end Domain avaya com Bypass If IP Threshold Exceeded n Incoming Dialog Loopbacks eliminate RFC 3389 Comfort Noise n DTMF over IP in band Direct IP IP Audio Connections y Session Establishment Timer min 3 IP Audio Hairpinning n Enable Layer 3 T
27. est y Initial IP IP Direct Media n H 323 Station Outgoing Direct Media n Alternate Route Timer sec 6 RAB Reviewed Solution amp Interoperability Test Lab Application Notes 14 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 12 Administer SIP Trunk Group For the compliance test trunk group 12 with the associated signaling group was used for routing fax calls to from Session Manager Trunk group 12 was configured using the parameters highlighted below All other fields were set as described in 3 On Page 1 The Group Type field was set to sip A descriptive name was entered for the Group Name An available trunk access code TAC that was consistent with the existing dial plan was entered in the TAC field The Service Type field was set to tie The Signaling Group was set to the signaling group shown in the previous step The Number of Members field contained the number of trunks in the SIP trunk group It determines how many simultaneous SIP calls can be supported by the configuration Each SIP call between two SIP endpoints whether internal or external requires two SIP trunks for the duration of the call The default values were used for all other fields change trunk group 12 Page i e Zul TRUNK GROUP Group Number 12 Group Type sip CDR Reports y Group Name PN2 to demoSM CORE TNA TAC 012 Direction two way Outgoing Display n Dial Access n Ni
28. g 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 Solution amp Interoperability Test Lab Application Notes 5 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved 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
29. ght Service Queue Length 0 Service Type tie Auth Code n Member Assignment Method auto Signaling Group 12 Number of Members 50 RAB Reviewed Solution amp Interoperability Test Lab Application Notes 15 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 13 Administer SIP Trunk Group continued On Page 3 Set the Numbering Format field to public This field specifies the format of the calling party number sent to the far end Default values may be used for all other fields change trunk group 12 Page 3 oe Zil TRUNK FEATURES ACA Assignment n Measured none Maintenance Tests y Numbering Format public UUI Treatment service provider Replace Restricted Numbers n Replace Unavailable Numbers n Modify Tandem Calling Number no Show ANSWERED BY on Display y 14 Administer Public Unknown Numbering Public unknown numbering defines the calling party number to be sent to the far end Use the change public unknown numbering command to create an entry that will be used by the trunk groups defined in Steps 12 13 In the example shown below all calls originating from a 5 digit extension beginning with 2 or 4 and routed across any trunk group Trk Grp column is blank were sent as a 5 digit calling party number change public unknown numbering 0 Page iL ORE 2 NUMBERING PUBLIC UNKNOW
30. n the tested configuration Mutti to Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout cen Configuration Time Server pool ntp org pantak Custom Time Server SMTP p F z time Synchronize every 0 Days 12 _ Hours Printer Time Zone America Denver x Shares Date Format MM DD YYYY Certificates Time Format 1 2HOUR Save e T Set Current Time R Software Update A Set Time 15 21 35 24hr hh mm ss Reboot Debug Set Date 05 18 2011 MM DD YYYY Set Bele RAB Reviewed Solution amp Interoperability Test Lab Application Notes 26 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description System Configuration Configure Printers and Network Shares FaxFinder can be configured to deliver inbound faxes to an email address to a printer or to a network share In the tested configuration all inbound faxes were saved to a network share 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 Mutti tci Home aA System Configuration Fax Configuration Users Contacts Send Fax Logout System __ Shared Resources Configuration Domain Workgroup WORKGROUP Network Shares a 10 64 10 51 Fax2 administrator Disconnect Edit Delete Prin
31. ncreased 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 A setting of 0 no redundancy is suited for networks where packet loss is not a problem change ip codec set 1 IP Codec Set Allow Direct IP Multimedia n Mode Redundancy FAX t 38 standard 0 Modem off 0 TD D A Ye US 3 Clear channel n 0 RAB Reviewed Solution amp Interoperability Test Lab Application Notes 13 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description 11 Administer SIP Signaling Group For the compliance test a signaling group with the associated SIP trunk group was used for routing fax calls to from the FaxFinder server via Session Manager For the compliance test at Site A signaling group 12 was configured using the parameters highlighted below All other fields were set as described in 3 The Group Type was set to sip The Transport Method was set to the recommended default value of tis Transport Layer Security As a result the Near end Listen Port and Far end Listen Port are automatically set to 5061 The Near end Node Name was set to CLAN2A the node name that maps to the IP address of the CLAN circuit pack used to connect to Session Manager Node names are defined using the change node nam
32. ocations RB_FaxServer ect All None Denied Originating Locations 0 Items Refresh Filter Enable Originating Location Input Required RAB Reviewed Solution amp Interoperability Test Lab Application Notes 23 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 7 Configure Multi Tech FaxFinder IP Fax Server This section describes the configuration of Multi Tech FaxFinder IP Fax Server For further instructions on configuring FaxFinder consult the Administrator User Guide 4 7 1 Configure FaxFinder Details The configuration procedures covered in this section include tasks in the following sub categories 1 System Configuration e Launch FaxFinder web configuration tool e Configure Network Settings e Configure SMTP Settings e Configure Time Settings e Configure Printers and Network Shares 2 Fax Configuration e Configure SIP T 38 e Configure Inbound Routing e Configure Outbound rules 3 Configure Users and Contacts 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 amp Interoperability Test Lab Application Notes 24 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description System Configuration Launch FaxFinder web configuration tool The FaxFinder configuration is performed using a web browser
33. onfiguration is not directly related to the interoperability of the products being tested so it is not included here 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 Details of this configuration are not described in this document and additional information can be obtained in 3 The documented configurations were repeated for the Session Manager at Site B using values appropriate for that site from Figure 1 This includes but is not limited to the IP addresses SIP domain and user extensions The steps used were e Create a SIP Entity for the FaxFinder Server e Create a SIP Entity Link for the FaxFinder Server e Create a Routing Policy e Create or modify Dial Patterns RAB Reviewed Solution amp Interoperability Test Lab Application Notes 18 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_SM61 6 1 Configure Session Manager Details This section summarizes the applicable user defined parameters used during the SIP installation procedures Step Description l Login Access the System Manager administration web interface by entering https lt ip addr gt SMGR as the URL in an Internet browser where lt ip addr gt is the IP address
34. r Users e FaxFinder Users Users for logging into the FaxFinder and sending 5 R ie Name username email Phone Fax Organization action administrator admin bowersr avaya com Edit Test test bowersr avaya com Edit Delete To create a user navigate to the Users tab then click the Add link and enter a Username Full Name Password and Email address for each user In addition if a user has a unique inbound fax extension a routing rule can be created by providing information in the lower section of the form Add FaxFinder User Username test Full Name admin Password eceee Confirm Password eccee Email testuser avaya com Phone Number Fax Number Organization Create Inbound Routing Recipient Optionally email inbound faxes to this user for the specified extension Add Route M Fax Extension 40000 Update Global and Personal contacts and Groups can be configured by clicking on the Contacts tab In the tested configuration these were used to simplify sending proceedures See the Administration Guide 4 for complete instructions on managing contacts LocalAnlgFax e Personal Groups RemoteAnigFax 6006 6006 Edit Delete lelensnicrsuns 7 RemoteFaxServer 45000 45000 Edit Delete RAB Reviewed Solution amp Interoperability Test Lab Application Notes 31 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 8 Verification Steps
35. rect 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 Pore 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 CuI Comiciaol S025 ihe werevoreiheys a Audio S02 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
36. rface 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 clan IP INTERFACES Net Eth Code Sfx Node Name Mask Gateway Node Rgn VLAN Link IP Address TN799 D CLANIA 24 Gateway001 10 64 22 TN799 D CLAN2A 24 Gateway001 10 64 22 list ip interface medpro IP INTERFACES Code Sfx Node Name Mask Gateway Node VLAN Virtual Node P Address TN2302 MEDPROI1A Gateway001 0 64 22 15 TN2302 MEDPRO2A Gateway001 0 64 22 18 TN2602 MEDPROIA 2 Gateway001 0 64 22 17 TN2602 MEDPRO2A 2 Gateway001 0 64 22 20 RAB Reviewed Solution amp Interoperability Test Lab Application Notes 9 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved 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 Di
37. t Mask 255 255 255 0 Shares Default Gateway 10 64 22 1 Ceruficates Primary DNS 205 171 3 65 s Rest m A Secondary DNS 205 171 2 65 EA Software Update Reboot R Debug RAB Reviewed Solution amp Interoperability Test Lab Application Notes 25 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description System Configuration Configure SMTP Settings FaxFinder can be configured to generate email alerts for a number of events Navigate to System Configuration gt SMTP to configure the outgoing mail gateway click Save to commit the changes Below is an example Home Status amp Logs System Configuration Fax Configuration Users Contacts Send Fax Logout System SMTP Configuration Configuration SMTP Server Address smtp comcast net Network _ SMTP SMTP Port 587 sid Ue SMTP Username lavayauser Printer f 1 i SMTP Password 20000000 Shares E Certificates Confirm SMTP Password R eoccccce Save Restore FaxFinder Email Address avayausef comcastn Save SEO WUE Send a Test Email Reboot T Send Test Email To Address Send Test Email Debug System Configuration Configure Time Settings Set the current date and time it is also recommended that an NTP server be configured to keep the system time in synch with other servers Click Set and Save when entries are completed in each section Below is an example of the settings used i
38. ter EPET Edit Network Share pa PPRPP WNC Location 10 64 10 51 Fex2 3 2 pi wg Save Restore Username administrator Software Update Password CAED Reboot Confirm Password eccccecece save Debug RAB Reviewed Solution amp Interoperability Test Lab Application Notes 27 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved FaxFinder_ SM61 Step Description Fax Configuration Configure SIP T 38 Navigate to Fax Configuration gt SIP T 38 and provide the appropriate information for the 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 muti c Home Status amp Logs System Configuration Fax help Configuration SIP T 38 Inbound Routing Outbound Outbound Approval Cover Pages Store amp Forward Fax T 37 Fax Log SIP Transport Protocol SIP Proxy Gateway SIP Domain Authorization Required Username Password SIP T 38 Configuration UDP 10 64 20 31 avaya com o Local Port SIP Proxy Port Use Registrar Registrar Registrar Port Fax Configuration Users Contacts Send Fax Logout Confirm Password Expires 3600 secs Fax ID FF240 P Max Rate 1a y Fax Method T 38 Re invite Error Correction on Ooff Fax Codec M67 1
39. 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 Medi
40. unication Manager On 8300 Server with G450 Media Gateway Avaya G650 A Aura I7 Media Gateway veya ANa FAX Server1 FAX Server 2 Avaya Aura Port Network 2 Session Manager 45000 40000 Session Manager SIP Entity Link _ __ SIP Entity Link SIP Trunk Site A Site B 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 Solution amp Interoperability Test Lab Application Notes 4 of 34 SPOC 7 12 2011 2011 Avaya Inc All Rights Reserved 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 supportin
Download Pdf Manuals
Related Search