Avaya Solution & Interoperability Test Lab Application Notes for Configuring Sagemcom XMediusFAX Service Provider Edition with Avaya Aura Communication Manager via H.323 Trunks - Issue 1.0 Abstract These Application Notes describe the procedures for configuring Sagemcom XMediusFAX Service Provider (SP) Edition with Avaya Aura Communication Manager using H.323 trunks. XMediusFAX is a software based fax server that sends and receives fax calls over an IP network. In the configuration tested, XMediusFAX interoperates with Avaya Aura Communication Manager to send/receive faxes using H.323 trunks and the T.38 fax protocol. 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. 1 of 27
1. Introduction These Application Notes describe the procedures for configuring Sagemcom XMediusFAX Service Provider (SP) Edition with Avaya Aura Communication Manager using H.323 trunks. XMediusFAX is a software based fax server that sends and receives fax calls over an IP network. In the configuration tested, XMediusFAX interoperates with Communication Manager to send/receive faxes using H.323 trunks and the T.38 protocol between XMediusFAX and the Avaya infrastructure. The compliance testing focused on fax calls to and from the XMediusFAX fax server using various page lengths, resolutions, and fax data speeds. 2. General Test Approach and Test Results This section describes the general test approach used to verify the interoperability of Sagemcom XMediusFAX SP Edition with the Avaya Communication Manager via H.323 trunks DevConnect Compliance Testing is conducted jointly by Avaya and DevConnect members. The jointly-defined test plan focuses on exercising APIs and/or standards-based interfaces pertinent to the interoperability of the tested products and their functionalities. DevConnect Compliance Testing is not intended to substitute full product performance or feature testing performed by DevConnect members, nor is it to be construed as an endorsement by Avaya of the suitability or completeness of a DevConnect member s solution. 2.1. Interoperability Compliance Testing The general test approach was to make intra-site and inter-site fax calls to and from the XMediusFAX fax server. The compliance tested configuration contained two sites. Site 2 served as the main enterprise site and Site 1 served as a simulated PSTN or a remote enterprise site. Inter-site calls and simulated PSTN calls were made using H.323 trunks and ISDN-PRI trunks between the sites. By using a Communication Manager at each site and two port networks at Site 1, fax calls across multiple TDM/IP hops were able to be tested. Faxes were sent with various page lengths, resolutions, and at various fax data speeds. For capacity testing, 100 2- page faxes were continuously sent between the two XMediusFAX fax servers. Serviceability testing included verifying proper operation/recovery from network outages, unavailable resources, Communication Manager and XMediusFAX restarts. Fax calls were also tested with different Avaya Media Gateway media resources to process the fax data. This included 2 TN2302 MedPro circuit packs, 2 TN2602 MedPro circuit packs in the Avaya G650 Media Gateway; and the integrated VoIP engine of the Avaya G450 Media Gateway with 4 MP80s VoIP Modules. Specifically, the following fax operations were tested during compliance testing: - Faxes from/to a fax server to/from an analog fax machine at a local site - Faxes from/to a fax server to/from an analog fax machine at a remote site - Faxes from/to a fax server to/from a fax server at a remote site 2 of 27
2.2. Test Results All test cases were executed and passed with the following exceptions/observations noted: To ensure successful faxing, set the configuration in the XMediusFAX Server with Fast Start ON and Tunnelling OFF. While performing capacity testing, 100 2-page faxes continuously sent between the two XMediusFAX fax servers, using the TN2302 MedPro circuit pack some failures were observed. The TN2302 MedPro circuit packs were reset and speed/duplex was hardcoded to 100Mbps/full-duplex, then the failures ceased. The speed/duplex was reverted back to auto-negotiated and the failures did not return. Media shuffling was enabled on the H.323 trunks to the fax servers and tested successfully. If media shuffling was enabled on the H.323 trunk between sites, some failures were observed. With shuffling disabled on the H323 trunk between sites, faxes were tested successfully. 2.3. General Observation Fax calls consume DSP (Digital Signal Processing) resources for processing fax data on the TN2302 IP Media Processor (MedPro) circuit pack and the TN2602 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 TN2302 and/or TN2602 MedPro circuit packs may need to be installed in the Avaya G650 Gateway, and additional Avaya MP80 VoIP Module or Modules need to be installed in the Avaya G450 Media Gateway. 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. 2.4. Support For technical support on XMediusFAX, contact Sagemcom at: Web: http://xmediusfax.sagemcom.com/support/ Phone: (888) 766-1668 Email: xmediusfax.support.americas@sagemcom.com 3 of 27
3. Reference Configuration Figure 1 illustrates the configuration used in these Application Notes. In the sample configuration, two sites were connected via an H.323 trunk, as well as by an ISDN-PRI trunk. Faxes were sent between the two sites using either of these two trunks, based on test case requirements. Site 1 consisted of an Avaya S8800 Server running Avaya Aura Communication Manager with an Avaya G650 Media Gateway. The media gateway is configured as a separate port network in separate IP network region. The media resources required are provided by the IP Media Processor (MedPro) circuit packs. Two versions of the IP MedPro circuit pack were tested in the configuration: the TN2302 and the TN2602. XMediusFAX at this site was running on a Windows 2008 Server and communicated with Communication Manager via an H.323 trunk whose signaling used a CLAN circuit pack in port network 2. Various IP endpoints at this site included Avaya one-x Deskphone 96xx and 96x1 (not all shown) series phones and an analog fax machine. Site 2 consisted of an Avaya S8300D Server running Avaya Aura Communication Manager in an Avaya G450 Media Gateway. The signaling and media resources needed to support H.323 trunks are integrated directly on the media gateway processor with DSP childboards. The G450 for this test had 4 MP80 VoIP Modules installed. XMediusFAX at this site was running on a Microsoft Windows 2008 Server Enterprise Edition R2 x64-bit and communicated with Communication Manager via an H.323 trunk. Various IP endpoints at this site included Avaya one-x Deskphone 96xx and 96x1 (not all shown) series phones and an analog fax machine. Although the IP endpoints (H.323 and SIP telephones) are not involved in the faxing operations, they are present at both sites to verify that VoIP telephone calls are not affected by the FoIP faxing operations and vice versa. 4 of 27
EST SAS SAS SAS FORWARD HEADSET SPEAKER MESSAGE OK CONTACTS MENU CALL LOG.,@ ABC DEF 1 2 3 GHI JKL MNO 4 5 6 PQRS TUV WXYZ 7 8 9 * Avaya one-x [ 0 # PHONE VOLUME MUTE FORWARD HEADSET SPEAKER MESSAGE OK CONTACTS MENU CALL LOG.,@ ABC DEF 1 2 3 GHI JKL MNO 4 5 6 PQRS TUV WXYZ 7 8 9 * Avaya one-x [ 0 # PHONE VOLUME MUTE ISDN-PRI T1 Trunk H.323 Trunk Analog Analog Avaya Aura Communication Manager on S8300 Server Fax Machine Avaya G650 Avaya 9630 IP Avaya 9630 IP with G450 Media Gateway Fax Machine Media Gateway Telephone Telephone (20000) (45000) 10.64.60.43 H.323 Trunk 10.64.22.12 Avaya Aura Communication Manager on Avaya S8800 Server (10.64.22.12) Layer 2 Switch Router Layer 2 Switch 10.64.101.46 10.64.101.56 H.323 Trunk Sagemcom XMediusFAX (60000) Sagemcom XMediusFAX (50000) Site 1 Site 2 Figure 1: Sagemcom XMediusFAX Test Configuration 5 of 27
4. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Avaya S8800 Server with a Avaya G650 Media Gateway Site 1 Software Avaya Aura Communication Manager R6.2 (R016x.02.0.823.0, Patch 20001) XMediusFAX fax server (Windows 2008 R2 Enterprise Server, SP1) XMediusFAX_7.0.0.298 with patch XMFSP_7.0.0.310 Analog Fax Machine - Avaya one-x Deskphone SIP endpoints 96xx 96x1 Avaya one-x Deskphone H.323 endpoints 96xx 96x1 Avaya S8300D Server with a Avaya G450 Media Gateway XMediusFAX fax server (Windows 2008 R2 Enterprise Server, SP1) Site 2 2.6.8 6.2.0 3.1.5 6.2.2 Avaya Aura Communication Manager R6.2 (R016x.02.0.823.0, Patch 20001) XMediusFAX_7.0.0.298 with patch XMFSP_7.0.0.310 Fax Machine - Various Avaya SIP and H.323 endpoints - 6 of 27
5. Configure Avaya Aura Communication Manager This section describes the Avaya Aura Communication Manager configuration necessary to interoperate with XMediusFAX. It focuses on the configuration of the H.323 trunk between Avaya Aura Communication Manager and XMediusFAX. All other components are assumed to be in place and previously configured, including the H.323 and ISDN-PRI trunks that connect both sites. The examples shown in this section refer to Site 1. Unless specified otherwise, these same steps also apply to Site 2 using values appropriate for Site 2 from Figure 1. The configuration of Avaya Aura Communication Manager was performed using the System Access Terminal (SAT). After the completion of the configuration, perform a save translation command to make the changes permanent. This section provides the procedures for configuring Communication Manager. The procedures include the following areas: Verify Communication Manager License IP Codec Set IP Network Region IP Node Names IP Network Map H.323 Signaling Group H.323 Trunk Group Update Signaling Group Route Pattern AAR Analysis 7 of 27
5.1. Verify Avaya Aura Communication Manager License Use the display system-parameters customer-options command and on Page 2, verify that the Maximum Administered H.323 Trunks has sufficient remaining capacity. The example shows that 12000 licenses are available and 228 are in use. The license file installed on the system controls the maximum values for these attributes. If a required feature is not enabled or there is insufficient capacity, contact an authorized Avaya sales representative to add additional capacity. display system-parameters customer-options Page 2 of 11 OPTIONAL FEATURES IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: 12000 228 Maximum Concurrently Registered IP Stations: 18000 0 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: 41000 0 Maximum Video Capable IP Softphones: 18000 0 Maximum Administered SIP Trunks: 24000 536 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.) 5.2. IP Codec Set Use the change ip-codec-set command to administer an IP codec set. IP codec set 1 was used during compliance testing. Multiple codecs can be listed in priority order to allow the codec used by a specific call to be negotiated during call establishment. The example below shows the values used during compliance testing. IP codec sets are used in Section 5.3 for configuring IP network regions to specify which codec sets may be used within and between network regions. change ip-codec-set 1 Page 1 of 2 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 2: 8 of 27
On Page 2, set the FAX Mode field to t.38-standard. 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 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. A setting of 0 (no redundancy) is suited for networks where packet loss is not a problem. change ip-codec-set 1 Page 2 of 2 IP Codec Set Allow Direct-IP Multimedia? n Maximum Mode Redundancy FAX t.38-standard 0 Modem off 0 TDD/TTY US 3 Clear-channel n 0 5.3. IP-Network-Region IP network region 1 At Site 1, the Avaya S8800 Server, the Avaya G650 Media Gateway comprising port network 1 and all IP endpoints were located in IP network region 1, using the parameters described below. At Site 2, the Avaya G450 Media Gateway and all IP components were located in IP network region 1 and the IP network region was configured in the same manner as shown below. Use the change ip-network-region command to administer the network region settings. The values shown below are the values used during compliance testing. Authoritative Domain: avaya.com Name: Any descriptive name may be used (if desired). Intra-region IP-IP Direct Audio: yes Inter-region IP-IP Direct Audio: yes By default, IP-IP direct audio (media shuffling) is enabled to allow audio traffic to be sent directly between IP endpoints without using media resources in the Avaya Media Gateway. Shuffling can be further restricted at the trunk level on the Signaling Group form. Codec Set: 1 The codec set contains the list of codecs available for calls within this IP network region. 9 of 27
change 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 Call Control PHB Value: 46 Audio PHB Value: 46 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 IP network region 2 At Site 1, IP network region 2 was created in a similar manner as IP network region 1 shown in the previous step but with a different name. change ip-network-region 2 Page 1 of 20 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: 3329 DIFFSERV/TOS PARAMETERS Call Control PHB Value: 46 Audio PHB Value: 46 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 10 of 27
5.4. IP Node Names Use the change node-names ip command to create node names that map to IP addresses for the Site 1 XMediusFAX server (Xmed_FaxServer) and Communication Manager at Site 2 (CM2_D4F26). These node names are used in the configuration of the H.323 trunk signaling groups. Node-names were already configured for CLAN and Medpro resources. Repeat the same procedure on Site 2 Communication Manager, adding the XMediusFAX server for Site 2 and Communication Manager for Site 1. change node-names ip Page 1 of 2 IP NODE NAMES Name IP Address CLAN1A 10.64.22.16 CLAN2A 10.64.22.19 CM2_D4F26 10.64.60.43 CM_10_67 10.64.10.67 CM_21_111 10.64.21.111 CM_21_41 10.64.21.41 FaxCore1 192.45.108.71 Gateway001 10.64.22.1 MEDPRO1A 10.64.22.15 MEDPRO2A 10.64.22.18 Xmed_FaxServer 10.64.101.46 default 0.0.0.0 procr 10.64.21.41 procr6 :: 5.5. IP Network Map If the XMediusFAX server is to be located in an IP network region other than the default region of 1, then the region is assigned using the change ip-network-map command. In the case of the compliance test, the XMediusFAX server IP address at Site 1 is assigned to IP network region 2 as shown in the example below. At Site 2, the XMediusFAX server is located in the default IP network region 1, so it does not require an IP address map entry. change ip-network-map Page 1 of 63 IP ADDRESS MAPPING Subnet Network Emergency IP Address Bits Region VLAN Location Ext --------------------------------------------- ------ ------ ---- ------------- FROM: 10.64.101.46 / 2 n TO: 10.64.101.46 11 of 27
5.6. H.323 Signaling Group Use the add signaling group command to create a signaling group for use by the H.323 trunk to the XMediusFAX server. For the compliance test at Site 1, signaling group 21 was configured using the parameters highlighted below. Default values may be used for all other fields. The following values for the specified fields and the default values may be used for the remaining fields. Set the Group Type to h.323. The Trunk Group for Channel Selection is left blank until the trunk group is created. It will be updated later. Set the Near-end Node Name to the node name that maps to the IP address of the CLAN circuit pack used to connect to the XMediusFAX server. Node names are defined using the change node-names ip command. For Site 2, this node name would map to the IP address of the Avaya Media Server (procr). Set the Far-end Node Name to the node name that maps to the IP address of the XMediusFAX server. Set the Near-end Listen Port and Far-end Listen Port to 1720. Set the Far-end Network Region to the IP network region which contains XMediusFAX. Set the Direct IP-IP Audio Connections field to y. field must be set to y to enable media shuffling on the H.323 trunk. The default values were used for all other fields. add signaling-group 21 Page 1 of 5 SIGNALING GROUP Group Number: 21 Group Type: h.323 SBS? n Remote Office? n Max number of NCA TSC: 0 Q-SIP? n Max number of CA TSC: 0 IP Video? n Trunk Group for NCA TSC: Trunk Group for Channel Selection: TSC Supplementary Service Protocol: a X-Mobility/Wireless Type: NONE Network Call Transfer? n T303 Timer(sec): 10 H.245 DTMF Signal Tone Duration(msec): Near-end Node Name: CLAN2A Far-end Node Name: Xmed_FaxServer Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Media Encryption? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n Enable Layer 3 Test? n Interworking Message: PROGress H.323 Station Outgoing Direct Media? n DCP/Analog Bearer Capability: 3.1kHz 12 of 27
5.7. H.323 Trunk Group Use the add trunk group command to create a trunk group for the H.323 trunk to the XMediusFAX server. For the compliance test at Site 1, trunk group 21 was configured using the parameters highlighted below. Default values may be used for all other fields. On Page 1: Set the Group Type field to isdn. Enter a descriptive name for the Group Name. Enter an available trunk access code (TAC) that is consistent with the existing dial plan in the TAC field. Set the Carrier Medium to H.323. Set the Service Type field to tie. Set the Member Assignment Method to auto. Set the Signaling Group to the signaling group shown in the previous step. In Number of Members field, enter the number of members in the trunk group. This determines how many simultaneous calls can be supported by the configuration. Default values may be used for all other fields. add trunk-group 21 Page 1 of 21 TRUNK GROUP Group Number: 21 Group Type: isdn CDR Reports: y Group Name: Xmed_FaxServer COR: 1 TN: 1 TAC: *021 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? n Queue Length: 0 Service Type: tie Busy Threshold: 255 Night Service: Auth Code? n Member Assignment Method: auto Signaling Group: 21 Number of Members: 40 13 of 27
H.323 Trunk Group continued On Page 3: Set the Send Name field and Send Calling Number field to y. The enables sending calling party name and number to the far end. Set the Numbering Format field to natl-pub. This field specifies the format of the calling party number sent to the far-end. Default values may be used for all other fields. add trunk-group 21 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: natl-pub UUI IE Treatment: service-provider Network Call Redirection: none Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n Hold/Unhold Notifications? n Modify Tandem Calling Number: no Show ANSWERED BY on Display? y 14 of 27
5.8. Update Signaling Group Use the change signaling-group command to update the Trunk Group for Channel Selection field with the trunk group created in Section 5.7. change signaling-group 21 Page 1 of 5 SIGNALING GROUP Group Number: 21 Group Type: h.323 SBS? n Remote Office? n Max number of NCA TSC: 0 Q-SIP? n Max number of CA TSC: 0 IP Video? n Trunk Group for NCA TSC: Trunk Group for Channel Selection:21 TSC Supplementary Service Protocol: a X-Mobility/Wireless Type: NONE Network Call Transfer? n T303 Timer(sec): 10 H.245 DTMF Signal Tone Duration(msec): Near-end Node Name: CLAN2A Far-end Node Name: Xmed_FaxServer Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Media Encryption? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n Enable Layer 3 Test? n Interworking Message: PROGress H.323 Station Outgoing Direct Media? n DCP/Analog Bearer Capability: 3.1kHz 5.9. Route Pattern Use the change route-pattern command to create a route pattern that will route calls to the H.323 trunk that connects to XMediusFAX. The example below shows the route pattern used for the compliance test at Site 1. A descriptive name was entered for the Pattern Name field. The Grp No field was set to the trunk group created in Section 5.7. 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 21 Page 1 of 3 Pattern Number: 21 Pattern Name: Xmed_FaxServer SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 21 0 n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR 0 1 2 M 4 W Request Dgts Format Subaddress 1: y y y y y n n rest none 2: y y y y y n n rest none 3: y y y y y n n rest none 15 of 27
5.10. AAR Analysis Automatic Alternate Routing (AAR) was used to route calls to XMediusFAX and to Communication Manager at the other site. Use the change aar analysis command to create an entry in the AAR Digit Analysis Table for this purpose. The example below shows entries that were created for Site 1 using the display aar analysis command. The entry 60000, that is 5 digits long uses route pattern 21 to route calls to the local XMediusFAX. Calls to Site 2 for 45000 (not shown) and 50000 were routed using route pattern 4 which used either the PSTN (Trunk Group 4), or H.323 (Trunk Group 50) in various tests to route calls using the inter-site trunks. At Site 2, similar entries were created for a 5 digit dialed strings 20000, 50000, and 60000 and defined the route pattern to the XMediusFAX server at Site 2, and Inter-Site trunks to reach Site 1. display aar analysis 5 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Location: all Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 5 4 4 11 aar n 5 5 5 11 aar n 50000 5 5 4 aar n 600 4 4 5 aar n 60000 5 5 21 aar n 601 4 4 20 aar n 16 of 27
6. Configure Sagemcom XMediusFAX This section describes the configuration of XMediusFAX. It assumes that the application and all required software components have been installed and properly licensed. The number of channels supported by the XMediusFAX server is controlled via an XMediusFAX server license file. For instructions on sending and receiving faxes, consult references (3) and (4) in Section 9. The examples shown in this section refer to Site 1. However, unless specified otherwise, these same steps also apply to Site 2 using values appropriate for Site 2 from Figure 1. 6.1. Launch the Application On the XMediusFAX server, launch the XMediusFAX management console snap-in tool from the Windows Start Menu. Navigate to Start All Programs XMediusFAX XMediusFAX. A login screen appears. Log in with proper credentials. Click the OK button. 17 of 27
6.1.1. Configure Driver Properties On the main screen, navigate to XMediusFAX System Configuration Hosts WIN2008R2SP1 Driver in the left hand tree menu. Right-click on Driver and select Properties (not shown). General Options On the Driver Properties screen, select the Options tab. Set the Maximum Number of Channels and Preferred Number Of Channels fields to the number of simultaneous faxes to be processed. 18 of 27
6.1.2. T.38 Parameters On the Driver Properties screen, select the T.38 tab. Configure the fields as follows: Received Document Encoding Set this field to the highest encoding allowed. For the compliance test, this value was set to Group 3 (1d). Terminal Resolution Capacity Set this field to the highest resolution allowed. For the compliance test, this value was set to Ultra (400x400). 19 of 27
6.1.3. Peer List On the Driver Properties screen, select the Peer List tab. To add a new H.323 peer, select the Add H.323 Peer button and enter the values shown below. To view an existing peer, highlight the peer in the list and click Properties. The example below demonstrates addingcommunication Manager CLAN interface (10.64.22.19) to the list. On the Peer Properties screen, configure as follows: Host Name Set this field to the procr or CLAN IP address associated with the node name configured in Section 5.4. Port - Set this field to match the Near-end Listen Port field in Section 5.6 Select the Send CNG using T.38 option. Select the Fast Start and deselect H245 Tunneling options (Refer to Section 2.2, this is a change from previous version test configuration). On the Advanced tab, select the Wait for RequestModeAck option. 20 of 27
6.1.4. Dial Plan On the Driver Properties screen, select the Dial Plan tab. To add a new entry to the dial plan, select the Add button and enter the values shown. To view an existing entry, highlight the entry in the list and click Properties. The example below shows the dial plan after the entry for * (any value) has been added to the list. 21 of 27
6.1.5. Configure Channels On the main screen, navigate to XMediusFAX System Configuration Hosts WIN2008R2SP1 Driver Channels in the left hand tree menu. Right-click on each channel in the right pane to set the Mode to Send, Receive or Both. In the compliance test, 40% of the channels were set to Send and 60% of the channels were set to Receive. 22 of 27
6.1.6. Fax Options On the main screen, navigate to XMediusFAX Sites Avaya DevConnect Configuration Profiles in the left hand tree menu. Right-click on the profile Basic (the profile that the user uses in the compliance test) in the right pane and select Properties. On the Fax Options tab, set the Maximum to Ultra Fine under the Resolution section. 23 of 27
7. Verification Steps The following steps may be used to verify the configuration: From Communication Manager SAT, use the status signaling-group command to verify that the H.323 signaling group to the XMediusFAX Server is in-service. status signaling-group 21 STATUS SIGNALING GROUP Group ID: 21 Active NCA-TSC Count: 0 Group Type: h.323 Active CA-TSC Count: 0 Group State: in-service From Communication Manager SAT, use the status trunk-group y command to verify that the H.323 trunk group is in-service (where y is the trunk group number for the trunk between Communication Manager and XMediusFAX server). status trunk 21 Page 1 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0021/001 T00739 in-service/idle no 0021/002 T00740 in-service/idle no 0021/003 T00741 in-service/idle no 0021/004 T00742 in-service/idle no 0021/005 T00743 in-service/idle no 0021/006 T00744 in-service/idle no 0021/007 T00745 in-service/idle no 0021/008 T00746 in-service/idle no 0021/009 T00747 in-service/idle no 0021/010 T00748 in-service/idle no From Communication Manager SAT, use the list trace tac command to verify that fax calls are routed over the expected trunks. list trace tac *021 Page 1 LIST TRACE time data 09:49:23 TRACE STARTED 11/08/2012 CM Release String cold-02.0.823.0-20001 09:49:29 dial 50000 route:aar 09:49:29 term trunk-group 4 cid 0x1eaa 09:49:29 dial 50000 route:aar 09:49:29 route-pattern 4 preference 1 location 1/ALL cid 0x1eaa 09:49:29 seize trunk-group 4 member 17 cid 0x1eaa 09:49:29 Setup digits 50000 24 of 27
Verify that fax calls can be placed to/from XMediusFAX and analog machines. Confirm the status in the Outbound History view under System Monitor on the XMediusFAX server management console snap-in tool. 25 of 27
8. Conclusion These Application Notes describe the procedures required to configure Sagemcom XMediusFAX to interoperate with Avaya Aura Communication Manager to support the network shown in Figure 1. All test cases were completed and passed with the exceptions/observations noted in Section 2.2. 9. Additional References The following Avaya product documentation can be found at http://support.avaya.com (1) Avaya Aura Communication Manager Feature Description and Implementation Release 6.2, Issue 9.0, July 2012, Document Number 555-245-205. (2) Administering Avaya Aura Communication Manager Release 6.2, Issue 7.0, July 2012, Document Number 03-300509. Product documentation for XMediusFAX may be obtained from Sagemcom (3) Sagemcom XMediusFAX Administrator Guide, Version Number 7.0.0.298, August 2012. (4) Sagemcom XMediusFAX Installation and Maintenance Guide, Version Number 7.0.0.298, August 2012. 26 of 27
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. 27 of 27