Summary of the content on the page No. 1
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 fa
Summary of the content on the page No. 2
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.38 protocol between X
Summary of the content on the page No. 3
3. 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. Figure 1: XMediusFAX with Session Manager and Communication Manager At Site 1 consists of the following equipment: An Avaya S8800 Server running Avaya Aura® Communi
Summary of the content on the page No. 4
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.323 and SIP telephones) are not involved in the faxing operations, they are present at both sites to verify that VoIP t
Summary of the content on the page No. 5
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 Avaya Aura® Communication Manager 6.0.1, Media Gateways: R016x.00.1.510.1, Patch 19009 : - 2 CLANs – TN799DP - HW01, FW038 - 2 IP MedPros – TN2302AP - HW20, FW120 - 2 IP MedPros – TN2602AP - HW02, FW57 Avaya Aura® System Manager: 6.0.0 (Build No. – Avaya S8800 Server 6.0.0.0.688-3.0.7.2) (Avaya Aura®
Summary of the content on the page No. 6
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 Description
Summary of the content on the page No. 7
Step Description 2. 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). Intra-region IP-IP Direct Audi
Summary of the content on the page No. 8
Step Description 3. 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 Silence Frames Packet Codec
Summary of the content on the page No. 9
Step Description 4. 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 IP Address AES_21_46 10.64.21.46 CM_20_40 10.64.20.40 CM_22_12_CLAN1
Summary of the content on the page No. 10
Step Description 5. 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 S
Summary of the content on the page No. 11
Step Description 6. 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. TAC: 101 Enter an valid value consistent with the Communicatio
Summary of the content on the page No. 12
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. display trunk-group 1 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Maintenance Tests? y
Summary of the content on the page No. 13
Step Description 8. 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). Numbers that begin with 20000 or 65 and are 5 digits long use route pattern 7, which routes calls to Co
Summary of the content on the page No. 14
Step Description 9. 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 Leve
Summary of the content on the page No. 15
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. The following sections assume that Session Manager and System Manager have been in
Summary of the content on the page No. 16
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. Log
Summary of the content on the page No. 17
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 Routing Domains, 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: Solution & Interoperability Test Lab Application Notes 17 of 47 SPOC 8/
Summary of the content on the page No. 18
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 Routing Locations 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 t
Summary of the content on the page No. 19
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/message- summary body with the given value (e.g. avaya.com) for ingress only. The override DestinationDomain (odstd) Module paramater replaces the domain in the Request-URI, To Header (if administered), Ref
Summary of the content on the page No. 20
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 Routing SIP Entities, and click the New button (not shown) to add a SIP Entity. The configuration details for the SIP Entity defined for Session Manager are as follows: Under General: Name: a
