Avaya Solution & Interoperability Test Lab Application Notes for Configuring Sagemcom XMediusFAX Service Provider Edition with Avaya Aura® Session Manager and Avaya Aura® Communication Manager - Issue 1.0 Abstract These Application Notes describe the procedures for configuring Sagemcom XMediusFAX Service Provider (SP) Edition with Avaya Aura® Session Manager and Avaya Aura® Communication Manager. XMediusFAX is a software based fax server that sends and receives fax calls over an IP network.
1. Introduction These Application Notes describe the procedures for configuring Sagemcom XMediusFAX Service Provider (SP) Edition with Avaya Aura® Session Manager and Avaya Aura® Communication Manager using SIP 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 the Session Manager and Communication Manager to send/receive faxes using SIP trunks and the T.
. Reference Configuration Figure 1 illustrates the reference configuration used during testing. In the reference configuration, the two sites are connected via a direct SIP trunk and an ISDN-PRI trunk. Faxes were sent between the two sites using either of these two trunks, as dictated by each individual test case.
A Dell™ PowerEdge™ R610 Server running Avaya Aura® System Manager. System Manager provides management functions for Session Manager. An HP ProLiant DL360 G7 Server running Avaya Aura® Session Manager. XMediusFAX running on a Windows 2008 R2 Enterprise Server (SP1). An analog fax machine Various Avaya IP endpoints (not all shown). Although the IP endpoints (H.
4. Equipment and Software Validated The following equipment and software were used for the reference configuration: Equipment Software Site 1 Avaya S8800 Server with a Avaya G650 Media Gateways: - 2 CLANs – TN799DP - 2 IP MedPros – TN2302AP - 2 IP MedPros – TN2602AP Avaya Aura® Communication Manager 6.0.1, R016x.00.1.510.1, Patch 19009 : - HW01, FW038 - HW20, FW120 - HW02, FW57 Avaya S8800 Server Avaya Aura® System Manager: 6.0.0 (Build No. – 6.0.0.0.688-3.0.7.2) (Avaya Aura® System Platform: 6.0.2.1.
5. Configure Communication Manager This section describes the Communication Manager configuration at Site 2 to support the network shown in Figure 1. Although not shown is this document, a similar Communication Manager configuration would be required at Site 1. The configuration of 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. Step 1.
Step 2. Description IP network region Use the display ip-network-region command to view the network region settings. The values shown below are the values used during compliance testing. Authoritative Domain: avaya.com This field was configured to match the domain name configured on Session Manager. The domain will appear in the “From” header of SIP messages originating from this IP region. Name: Any descriptive name may be used (if desired).
Step 3. Description Codecs 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. display ip-codec-set 1 Page 1 of 2 IP Codec Set Codec Set: 1 Audio Codec 1: G.711MU 2: Silence Suppression n Frames Per Pkt 2 Packet Size(ms) 20 On Page 2, set the FAX Mode field to t.38-standard.
Step 4. Description Node Names Use the change node-names ip command to create a node name for the IP address of Session Manager. Enter a descriptive name in the Name column and the IP address assigned to Session Manager in the IP address column. change node-names ip Page 1 of 2 IP NODE NAMES Name AES_21_46 CM_20_40 CM_22_12_CLAN1A CM_22_12_CLAN2A IPO_21_64 SM_20_31 SM_21_31 default msgserver procr procr6 MJH; Reviewed: SPOC 8/4/2011 IP Address 10.64.21.46 10.64.20.40 10.64.22.16 10.64.22.19 10.64.21.
Step 5. Description Signaling Group Signaling group 1 was used for the signaling group associated with the SIP trunk group between Communication Manager and Session Manager. The signaling groups and trunk groups between the two sites of the reference configuration is assumed to already be in place and not described in this document. Signaling group 1 was configured using the parameters highlighted below. Near-end Node Name: procr This node name maps to the IP address of the Avaya S8300D Server.
Step 6. Description Trunk Group Trunk group 1 was used for the SIP trunk group between Communication Manager and Session Manager. The signaling groups and trunk groups between the two sites of the reference configuration is assumed to already be in place and not described in this document. Trunk group 1 was configured using the parameters highlighted below. Group Type: sip This field sets the type of the trunk group.
Step Description Trunk Group – continued On Page 3: The Numbering Format field was set to unk-pvt. This field specifies the format of the calling party number sent to the far-end. The default values may be retained for the other fields.
Step 8. Description Automatic Alternate Routing Automatic Alternate Routing (AAR) was used to route calls either to Session Manager or to the Communication Manager at the other site. Use the change aar analysis command to create an entry in the AAR Digit Analysis Table. The example below shows numbers that begin with 75 and are 5 digits long use route pattern 1 (to Session Manager).
Step 9. Description Route Pattern Route pattern 1 was used for calls destined for the XMediusFAX fax server through Session Manager. Route patterns 7 and 8 (not shown) were used for calls destined for the other site in the reference configuration. Route pattern 1 was configured using the parameters highlighted below. Pattern Name: Any descriptive name. Grp No: 1 This field is set to the trunk group number defined in Step 5. FRL: 0 This field sets the Facility Restriction Level of the trunk.
6. Configure Session Manager This section provides the procedures for configuring Session Manager (version 6.1) as provisioned at Site 2 in the reference configuration. Although not shown is this document, a similar Session Manager configuration would be required at Site 1 (using the appropriate version 6.0 screens). All provisioning for Session Manager is performed via the System Manager web interface.
example, if a call arrives at Session Manager and matches a certain Dial Pattern, then Session Manager selects one of the Network Routing Policies specified in the Dial Pattern. The selected Network Routing Policy in turn specifies the SIP Entity to which the call is to be routed. 1. Login Access the System Manager administration web interface by entering https:///SMGR/ as the URL in an Internet browser, where is the IP address of the System Manager server.
2. Add SIP Domain The Routing menu contains all the configuration tasks listed at the beginning of this section. During compliance testing, one SIP Domain was configured. Navigate to RoutingDomains, and click the New button (not shown) to add the SIP domain with Name: avaya.com (as set in Section 5, Step 2) Notes: optional descriptive text Click Commit to save the configuration. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
3. Add Location Locations identify logical and/or physical locations where SIP entities reside. Only one Location was configured at each site for compliance testing. Navigate to RoutingLocations and click the New button (not shown) to add the Location. Under General: Name: a descriptive name Notes: optional descriptive text Under Location Pattern, click the Add button to add a new line: IP Address Pattern: 10.64.21.* Notes: optional descriptive text Click Commit to save the configuration.
4. Add Adaptation An Adaptation was created and applied to the “Fax Server” SIP entity to override the destination domain as shown below. The ingressOverrideDestinationDomain (iodstd) Module paramater replaces the domain in the Request-URI, To Header (if administered), and Notify/messagesummary body with the given value (e.g. avaya.com) for ingress only.
5. Add SIP Entities A SIP Entity must be added for Session Manager and for each SIP-based telephony system supported by it using SIP trunks. During compliance testing, a SIP Entity was added for the Session Manager itself, Communication Manager, and the XMediusFAX fax server. Navigate to RoutingSIP Entities, and click the New button (not shown) to add a SIP Entity.
Add SIP Entities (continued) – Session Manager The screens below show the SIP Entity configuration details for the Session Manager. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Add SIP Entities (continued) – Communication Manager The screen below shows the SIP Entity configuration details for the Communication Manager. Note the CM selection for Type. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Add SIP Entities (continued) – XMediusFax The screen below shows the SIP Entity configuration details for the XMediusFAX fax server. Note the Other selection for Type, and the Adaptation created Step 4 of this section is selected. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
6. Add Entity Links A SIP trunk between Session Manager and a telephony system is described by an Entity link. Two Entity Links were created: one between Session Manager and Communication Manger; the other between Session Manager and the XMediusFAX fax server. Navigate to RoutingEntity Links, and click the New button (not shown) to add a new Entity Link. The screen below shows the configuration details for the Entity Link connecting Session Manager to Communication Manager.
Add Entity Links (continued) The Entity Link for connecting Session Manager to the XMediusFAX fax server was similarly defined as shown in the screen below. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
7. Add Time Ranges Before adding routing policies (configured in next step), time ranges must be defined during which the policies will be active. One Time Range was defined that would allow routing to occur at anytime. Navigate to RoutingTime Ranges, and click the New button to add a new Time Range: Name: a descriptive name Mo through Su: check the box under each of these headings Start Time: enter 00:00 End Time: enter 23:59 Click Commit to save this time range.
8. Add Routing Policies Routing policies describe the conditions under which calls will be routed to the SIP Entities connected to the Session Manager. Two routing policies were added – one for routing calls to Communication Manager, and the other for routing calls to the XMediusFAX fax server. Navigate to RoutingRouting Policies, and click the New button (not shown) to add a new Routing Policy.
Add Routing Policies (continued) The screens below show the configuration details for the two Routing Policies used during compliance testing. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
9. Add Dial Patterns Dial Patterns define digit strings to be matched against dialed numbers for directing calls to the appropriate SIP Entities. 5-digit extensions beginning with “5” resided on Communication Manager at Site 2. 5-digit extensions matching “20000” or “65000” were routed to the local Communication Manager for onward routing to Site 1. 5-digit extensions beginning with “75” were routed to the XMediusFAX fax server. Therefore 4 Dial Patterns were created accordingly.
Add Dial Patterns (continued) The screens below shows the configuration details for the Dialed Patterns defined for routing calls to Communication Manager at the main enterprise site. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Add Dial Patterns (continued) The screen below shows the configuration details for the Dialed Pattern defined for routing calls to the XMediusFAX fax server. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
7. 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 the XMediusFAX Administrator Guide [5] and User Guide [7]. The examples shown in this section refer to Site 2.
Step 3. Description Configure Driver Properties On the main screen, navigate to XMediusFAX System Configuration Hosts WIN-8E644SJFMQO Driver in the left hand tree menu. Right-click on Driver and select Properties (not shown). MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Step 4. Description General Options On the Driver Properties screen, select the Options tab. Set the Maximum Number Of Channels and Preferred Number Of Channels fields under T.38 Channel Configuration to the number of simultaneous faxes to be processed. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Step 5. Description 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 desired. For the compliance test, this value was set to High (200x200).
Step 6. Description SIP Parameters On the Driver Properties screen, select the SIP tab. Configure the fields as follows: Local SIP UDP port – Set this field to match the first Port field in Section 6, Step 6. During compliance testing, UDP was used as the transport layer protocol by the XMediusFAX fax server. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Step 7. Description Peer List On the Driver Properties screen, select the Peer List tab. To add a new SIP peer, select the Add SIP Peer button and enter the values shown in Step 8. To view an existing peer, highlight the peer in the list and click Properties. The example below shows the peer list after the Session Manager interface, 10.64.21.31, has been added to the list. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Step 8. Description Peer Properties On the Peer Properties screen, configure as follows: Host Name – Set this field to the IP address of Session Manager. Transport: Set this field to UDP. During compliance testing, UDP was used as the transport layer protocol by the XMediusFAX fax server. Port - Set this field to 5060. Check the Send CNG using RTP field. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Step 9. Description Codec On the Peer Properties screen, select the Advanced tab. To add a codec for the SIP peer, select the Add button and select the values from the drop-down menu. To view an existing codec, highlight the codec in the list and click Properties. The example below shows the codec list supported by the newly added SIP peer. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Step 10. Description 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 in Step 11. To view an existing entry, highlight the entry in the list and click Properties to get the Number Pattern Properties screen. The example below shows the dial plan after the entry for * (any value) has been added to the list.
Step 11. Description Number Pattern Properties On the Number Pattern Properties screen, configure as follows: Number Pattern – Set this field to the pattern to match. In this example, the value of * indicates any dialed number is acceptable. Peer – Click the Add button. In the Peer Properties window that appears (not shown), enter the Peer IP Address and Preference value of 1 and click OK. In this example, only one peer is configured.
Step 12. Description Once all the driver properties have been configured, go to Start Control Panel Administrative Tools Services to stop and start the XMFaxDriver service to make the changes take effect. MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
Step 13. Description Configure Channels On the main screen, navigate to XMediusFAX System Configuration Hosts WIN-8E644SJFMQO 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. During compliance testing, 9 channels were set to Send and 14 channels were set to Receive. s MJH; Reviewed: SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes ©2011 Avaya Inc. All Rights Reserved.
8. Verification Steps The following steps may be used to verify the configuration: Using System Manager, navigate to Session ManagerSystem StatusSIP Entity Monitoring, and click on the appropriate SIP Entities to verify that the Entity Link to Communication Manager is up.
©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 trademark s are the property of their respective owners. The information provided in these Application Notes is subject to change without notice.