Application Notes for Configuring Sagemcom XMediusFAX fax server with Avaya IP Office - Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Sagemcom XMediusFAX fax server with Avaya IP Office - Issue 1.0 Abstract These Application Notes describe the procedures for configuring Sagemcom XMediusFAX Service Provider (SP) Edition with Avaya IP Office. 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 IP Office 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. 1 of 42

2 1. Introduction These Application Notes describe the procedures for configuring Sagemcom XMediusFAX fax server with Avaya IP Office 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 Avaya IP Office to send/receive faxes using SIP trunks and the T.38 protocol between XMediusFAX and the Avaya SIP 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 Server with the Avaya SIP infrastructure (IP Office). This section also covers the test results 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 1 served as the main enterprise site and Site 2 served as a simulated PSTN or a remote enterprise site. Inter-site calls and simulated PSTN calls were made using an ISDN-PRI trunk between the sites. Faxes were sent with various page lengths, resolutions, and at various fax data speeds. For capacity testing, page faxes were continuously sent between the two XMediusFAX fax servers. Serviceability testing included verifying proper operation/recovery from network outages, unavailable resources, and IP Office and XMediusFAX fax server restarts. All tests were performed with ECM disabled Test Results XMediusFAX successfully passed compliance testing Support For technical support on XMediusFAX, contact Sagemcom at: Web: Phone: (888) xmediusfax.support.americas@sagemcom.com 3. Reference Configuration Figure 1 illustrates the reference configuration used during testing. In the reference configuration, the two sites are connected via a direct ISDN-PRI trunk. Faxes were sent between the two sites using this trunk, as dictated by each individual test case. 2 of 42

3 Figure 1: XMediusFAX with Avaya IP Office Sites 1 and 2 utilized of the following equipment: An Avaya IP Office system. XMediusFAX fax server running on a Windows 2008 R2 Enterprise Server (SP1). An analog fax machine. Ethernet Routing Switch (ERS 4550T-PWR Used for network connectivity) Various Avaya IP endpoints (not all shown). Although the IP endpoints 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. Outbound fax calls originating from the XMediusFAX fax server are sent using the SIP trunk to the Avaya IP Office system. Based on the dialed digits, Avaya IP Office will route calls to the local fax machine, or to the other site via the ISDN-PRI trunk. Inbound fax calls destined for the XMediusFAX fax servers are initiated from the local fax machine or remote site. Avaya IP Office also routes these calls to their intended destinations. 3 of 42

4 4. Equipment and Software Validated The following equipment and software were used for the reference configuration: Equipment Software Avaya IP Office 500 V2 8.0 XMediusFAX fax server (Windows 2008 R2 Enterprise Server, SP1) Analog Fax Machine - Various Avaya H.323 endpoints with patch XMFSP_ Note: T.38 is only supported on IP Office 500 hardware and the IP Office system must be equipped with VCM 32 or VCM 64 voice compression modules. One VCM channel is used for each fax call. 5. Configure Avaya IP Office This section describes the Avaya IP Office configuration to support Site1 in the network shown in Figure 1. Although not shown is this document, a similar Avaya IP Office configuration would be required at Site 2. The configuration of Avaya IP Office system was performed using the Avaya IP Office Manager application. Once completed the Avaya IP Office Manager Configuration must be saved and uploaded to the IP Office System. This process may sometimes force a system reboot. The Avaya IP Office configuration includes following sections: Connect to IP Office using Manager Verify IP Office Control Unit Verify IP Office Licenses Configure System Parameters Configure IP Office SIP Line Configure IP Office Extensions Configure IP Office Users Configure PRI Trunk for PSTN Access Configure Short Codes o Routing to the Simulated PSTN o Routing to the XMediusFAX fax server Configure Incoming Call Routes o Calls Received on the PRI o Calls Received on the SIP Line Saving IP Office Configuration 4 of 42

5 5.1. Connect to IP Office using Manager From a PC running the Avaya IP Office Manager application, select Start All Programs IP Office Manager to launch the Manager application. Select the desired IP Office system and login with the appropriate credentials Verify IP Office Control Unit From the configuration tree in the navigation pane, expand Control Unit and select IP 500 V2. Verify Unit Type and Version. This compliance test verified functionality using Avaya IP Office 500 V2 HW with version 8.0 SW. 5 of 42

6 5.3. Verify IP Office Licenses From the configuration tree in the navigation pane, expand License and highlight SIP Trunk Channels. Verify that the License Status field displays Valid there are sufficient Instances for the number of SIP Trunk channels that are required. Each SIP Trunk requires a SIP Trunk Channel license. 6 of 42

7 5.4. Configure System Parameters From the configuration tree in the navigation pane, expand System then highlight LAN1 in the right pane. From this page the LAN Settings, VoIP, and SIP Registrar tabs will need to be configured LAN Settings From the LAN Settings tab configure an IP Address and Subnet Mask for the IP Office system. DHCP Mode can also be configured from this page if required. 7 of 42

8 VoIP From the VoIP tab. Verify that the SIP Trunks Enable box is checked SIP Registrar From the SIP Registrar tab. Enter the IP Address or Domain Name for IP Office. All other field values are default. 8 of 42

9 5.5. Configure IP Office SIP Line From the configuration tree in the navigation pane, use the right mouse button to select Line, and select New SIP Line from the pop-up list (Not shown) to add the SIP trunk to the XMediusFAX fax server. Default parameters are sufficient for the SIP Line tab. 9 of 42

10 10 of 42

11 From the Transport tab enter the IP Address of the XMediusFAX fax server. Select UDP for the Layer 4 Protocol. 11 of 42

12 From the SIP URI tab click the Add button and configure the Edit Channel Section: In this compliance test the SIP trunk was configured to accept any incoming SIP call by using * in the Local URI, Contact, and Display Name fields. Note: Verify that the Incoming and Outgoing groups match the SIP Line number. 12 of 42

13 From the VoIP tab select T38 for FAX Transport Support. Verify that the Re-Invite Supported box is checked. 13 of 42

14 Default parameters for the T38 Fax settings were used during the compliance test. Note: The Avaya IP Office system supports UDPTL only for T.38 transport. 14 of 42

15 5.6. Configure IP Office Extension From the configuration tree in the navigation pane, use the right mouse button to select Extension, and select New H323 Extension from the pop-up list to add a new H323 extension. Enter the desired digits for the Base Extension field. Select the OK button. During the compliance test, extensions were used to verify voice calls with ongoing faxes. 15 of 42

16 5.7. Configure IP Office Users From the configuration tree in the navigation pane, use the right mouse button to select User, and select New from the pop-up list. Enter desired value for the Name and Password fields. For the Extension field, enter the H323 extension previously created. 16 of 42

17 5.8. Configure PRI Trunk for PSTN Access From the configuration tree in the navigation pane, expand Line and select the PRI. Verify that the parameters required for the PRI are configured appropriately. In this compliance test the Switch Type was configured as 5ESS, Line Sub Type as PRI, Framing as ESF and Zero Suppression as B8ZS. 17 of 42

18 Create PRI Channels From the PRI page select the Channels tab. On this page use the shift key to mark all channels. Once all of the Channels have been highlighted, select the Edit button to configure channel parameters. From the Edit page configure the Incoming and Outgoing Groups to match the Line position of the PRI. The PRI for this test was in position of 42

19 5.9. Configure ARS Route to the Simulated PSTN From the configuration tree in the navigation pane, using the right mouse button select ARS. When the menu appears select New. In right pane enter a Route Name. The image below displays the configuration used during the compliance testing. All other fields display their default values. 19 of 42

20 Select the Add button to configure a Code that will be used to reach the destination. In the compliance test it was observed that the Telephone Number in the ARS route for the 5 digit extensions starting with 7 (7xxxx) had to be configured as.sie. This configuration allowed the extension to be sent as the calling party ID on the PSTN trunk. Without this configuration calls using the PRI did not include the Calling Party Number and were dropped by the receiving IP Office System. Select the OK button. 20 of 42

21 5.10. Configure Short Code for routing to the Simulated PSTN From the configuration tree in the navigation pane, using the right mouse button select Short Code when menu appears select New. In right pane enter a Code that will be used to reach the destination. Additionally enter the Line Group ID. In this compliance test 5 digit extensions starting with 7 (7xxxx) were used for the code and Line Group ID 51 was the ARS route used to route calls to the simulated PSTN. Use default values for all other fields. Select the OK button. Note: When a 5 digit extension starting with 7 is dialed, the call will be routed via the PRI to the Simulated PSTN. 21 of 42

22 5.11. Configure Incoming Call Routes From PSTN From the configuration tree in the navigation pane, using the right mouse button select Incoming Call Route, when menu appears select New. In right pane select Standard tab. From Standard tab enter the following values: Bearer Capability = Any Line Group ID = Line Group ID of PRI (9) Use default values for all other fields. 22 of 42

23 From PSTN Destinations From current Incoming Call Route page select the Destinations tab. Enter a period in the Destination field. 23 of 42

24 From XMediusFAX fax server From the configuration tree in the navigation pane, using the right mouse button select Incoming Call Route, when menu appears select New. In right pane select Standard tab. From Standard tab enter the following values: Bearer Capability = Any Line Group ID = Line Group ID of the SIP Line (17) Use default values for all other fields. 24 of 42

25 From PSTN Destinations From current Incoming Call Route page select the Destinations tab. Enter a period in the Destination field Saving IP Office Configuration Once the configuration changes have been completed, select the floppy disk icon (not shown) to push the changes to the IP Office system. Note: Changes will not take effect until this step is completed. This may cause a reboot of Avaya IP Office causing service disruption. 25 of 42

26 6. Configure Sagemcom XMediusFAX fax server This section describes the configuration of XMediusFAX fax server. It assumes that the application and all required software components have been installed and properly licensed. The number of channels supported by the XMediusFAX fax server is controlled via an XMediusFAX fax server license file. For instructions on sending and receiving faxes, consult the XMediusFAX Administrator Guide [2] and User Guide [4]. The examples shown in this section refer to Site 1. Unless specified otherwise, the same steps also apply to Site 2 using values appropriate for Site 2 from Figure Initial Preparation Prepare the fax server for launching the XMediusFAX Server software. Consult Sagemcom for requirements and instructions Launch Application On the XMediusFAX fax server, launch the XMediusFAX application 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. 26 of 42

27 6.3. Configure Driver Properties On the main screen, navigate to XMediusFAX System Configuration Hosts WIN- EPS16UR492Q Driver in the left hand tree menu. Right-click on Driver and select Properties (not shown). 27 of 42

28 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. 28 of 42

29 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 High (200x200). 29 of 42

30 SIP Parameters On the Driver Properties screen, select the SIP tab. Configure the fields as follows: Local SIP UDP port Set this field to During compliance testing, UDP was used as the transport layer protocol by the XMediusFAX fax server. 30 of 42

31 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 IP Address of IP Office. To view an existing peer, highlight the peer in the list and click Properties. The example below shows the peer list after the IP Office IP address, , has been added to the list. 31 of 42

32 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 Check the Send CNG using RTP field. 32 of 42

33 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. 33 of 42

34 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 Number Pattern and select a Peer to reach this number. 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. 34 of 42

35 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. Lastly, click OK on the Driver Properties screen shown in Section 6.3.7, to accept the Driver Configuration. 35 of 42

36 Restart Service 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. 36 of 42

37 Configure Channels On the main screen, navigate to XMediusFAX System Configuration Hosts WIN- EPS16UR492Q 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. 37 of 42

38 7. Verification Steps The following steps may be used to verify the configuration: Using IP Office Manager, navigate to File Advanced System Status (Not shown). The following screen will be displayed. Enter the appropriate credentials and click Logon. 38 of 42

39 From the screen that follows, navigate to Trunks in the left pane. Select and verify the status of each trunk used in the configuration. PRI Trunk to PSTN: 39 of 42

40 SIP Trunk to XMediusFAX Server: 40 of 42

41 Active calls can also be verified using the IP Office System Status application. Verify that fax calls can be placed to/from the XMediusFAX fax server at each site. 8. Conclusion Sagemcom XMediusFAX passed compliance testing. These Application Notes describe the procedures required to configure Sagemcom XMediusFAX to interoperate with Avaya IP Office to support the network shown in Figure Additional References Product documentation for Avaya products may be found at [1] IP Office Manager, December 2011, Release 10.0, Document Number , Issue 27m. Product documentation for XMediusFAX may be may be obtained from Sagemcom. [2] Sagemcom XMediusFAX Administrator Guide, September 2010 [3] Sagemcom XMediusFAX Installation and Maintenance Guide, September 2010 [4] Sagemcom XMediusFAX User Guide, September of 42

42 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 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 42 of 42