Download
Share
Print this page
Avaya Sagemcom XMediusFAX Application Notes
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Software
  5. Sagemcom XMediusFAX s
  6. Application notes
Avaya Sagemcom XMediusFAX Application Notes

Avaya Sagemcom XMediusFAX Application Notes

Configuring with sagemcom xmediusfax service provider edition
Hide thumbs

Advertisement

Quick Links

Download this manual
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
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. In the configuration tested, XMediusFAX interoperates with Avaya Aura® Session
Manager and Avaya Aura® Communication Manager to send/receive faxes using SIP trunks
and the T.38 fax protocol between XMediusFAX and the Avaya SIP infrastructure.
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.
MJH; Reviewed:
SPOC 8/4/2011
Abstract
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
1 of 47
Sagemcom_SM61

Advertisement

loading
Need help?

Need help?

Do you have a question about the Sagemcom XMediusFAX and is the answer not in the manual?

Questions and answers

Related Manuals for Avaya Sagemcom XMediusFAX

Summary of Contents for Avaya Sagemcom XMediusFAX

  • Page 1 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.

  • Page 2: Test Results

    Communication Manager and XMediusFAX restarts. Fax calls were also tested with different Avaya Media Gateway media resources to process the fax data. This included the TN2302 MedPro circuit pack, the TN2602 MedPro circuit pack in the Avaya G650 Media Gateway; and the integrated VoIP engine of the Avaya G450 Media Gateway.

  • Page 3: Reference Configuration

     An Avaya S8800 Server running Avaya Aura® Communication Manager with two Avaya G650 Media Gateways. Each media gateway is configured as a separate port network in separate IP network regions. 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 TN2302AP and the TN2602AP.
  • Page 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).

  • Page 5: Equipment And Software Validated

    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® System Platform: 6.0.2.1.5) Avaya S8800 Server Avaya Aura® Session Manager 6.0.2.0.602004 XMediusFAX fax server (Windows 2008 6.5.5 with patch XMFSP_6.5.5.213...
  • Page 6 Trunks field value with the corresponding value in the USED column. The license file installed on the system controls the maximum permitted. If there is insufficient capacity, contact an authorized Avaya sales representative to make the appropriate changes. display system-parameters customer-options...
  • Page 7 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.
  • Page 8 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.
  • Page 9 CM_20_40 10.64.20.40 CM_22_12_CLAN1A 10.64.22.16 CM_22_12_CLAN2A 10.64.22.19 IPO_21_64 10.64.21.64 SM_20_31 10.64.20.31 SM_21_31 10.64.21.31 default 0.0.0.0 msgserver 10.64.21.41 procr 10.64.21.41 procr6 MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 10 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. Node names are defined using the change node-names ip command.
  • Page 11 Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: auto Signaling Group: 1 Number of Members: 50 MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 11 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 12 1 of NUMBERING - PRIVATE FORMAT Ext Ext Private Total Len Code Grp(s) Prefix Total Administered: 1 Maximum Entries: 540 MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 13 AAR DIGIT ANALYSIS TABLE Location: all Percent Full: 1 Dialed Total Route Call Node String Pattern Type Reqd 20000 unku unku 59997 MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 14 5: y y y y y n rest none 6: y y y y y n rest none MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 14 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 15 Policies for routing calls that match the criteria. The criteria include the called party number and SIP domain in the Request-URI, and the Location from which the call originated. For MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 15 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 16 IP address of the System Manager server. Log in with the appropriate credentials. The main page for the administrative interface is shown below. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 17 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.
  • Page 18 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. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 18 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 19 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), Refer-To header, and Notify/message- summary body with the given value (e.g.
  • Page 20 Default settings can be used for the remaining fields. Click Commit to save the SIP Entity definition. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 20 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 21 Add SIP Entities (continued) – Session Manager The screens below show the SIP Entity configuration details for the Session Manager. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 21 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 22 The screen below shows the SIP Entity configuration details for the Communication Manager. Note the CM selection for Type. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 22 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 23 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: Solution & Interoperability Test Lab Application Notes 23 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 24  Protocol: select TLS as the transport protocol.  Notes: optional descriptive text Click Commit to save the configuration. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 24 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 25 The Entity Link for connecting Session Manager to the XMediusFAX fax server was similarly defined as shown in the screen below. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 25 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 26 End Time: enter 23:59 Click Commit to save this time range. The screen below shows the configured Time Range. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 26 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 27 Click Add to select the Time Range configured in the previous step (not shown). Default settings can be used for the remaining fields. Click Commit to save the configuration. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 27 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 28 Add Routing Policies (continued) The screens below show the configuration details for the two Routing Policies used during compliance testing. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 28 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 29 Click Add to select the time range configured in Step 7. Default settings can be used for the remaining fields. Click Commit to save the configuration. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 29 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 30 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: Solution & Interoperability Test Lab Application Notes 30 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 31 MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 31 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 32 MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 32 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 33 The screen below shows the configuration details for the Dialed Pattern defined for routing calls to the XMediusFAX fax server. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 33 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 34 Start Menu. Navigate to Start  All Programs  XMediusFAX  XMediusFAX. A login screen appears. Log in with proper credentials. Click the OK button. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 34 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 35 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: Solution & Interoperability Test Lab Application Notes 35 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 36 Of Channels and Preferred Number Of Channels fields under T.38 Channel Configuration to the number of simultaneous faxes to be processed. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 36 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 37 Terminal Resolution Capacity – Set this field to the highest resolution allowed desired. For the compliance test, this value was set to High (200x200). MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 37 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 38 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: Solution & Interoperability Test Lab Application Notes 38 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 39 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: Solution & Interoperability Test Lab Application Notes 39 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 40 XMediusFAX fax server.  Port - Set this field to 5060.  Check the Send CNG using RTP field. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 40 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 41 Properties. The example below shows the codec list supported by the newly added SIP peer. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 41 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 42 Pattern Properties screen. The example below shows the dial plan after the entry for * (any value) has been added to the list. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 42 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 43 Lastly, click OK on the Driver Properties screen shown in Step 10, to accept the Driver Configuration. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 43 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 44 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: Solution & Interoperability Test Lab Application Notes 44 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...
  • Page 45 Mode to Send, Receive or Both. During compliance testing, 9 channels were set to Send and 14 channels were set to Receive. MJH; Reviewed: Solution & Interoperability Test Lab Application Notes 45 of 47 SPOC 8/4/2011 ©2011 Avaya Inc. All Rights Reserved. Sagemcom_SM61...

  • Page 46: Verification Steps

    Verify that fax calls can be placed to/from the XMediusFAX fax server at each site.  From the Avaya Communication Manager SAT, use the list trace tac command to verify that fax calls are routed over the expected trunks. 9. Conclusion Sagemcom XMediusFAX passed compliance testing.
  • Page 47 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.

This manual is also suitable for:

Aura session managerAura communication manager