XM Fax (formerly XMedius) Setup Guide for Power-T.38 SIP Trunks

Connect XM Fax to our Power-T.38 fax-optimized SIP trunks and see how we use science, not superstition, to achieve enterprise-quality fax performance without traditional PSTN circuits.

XMedius Fax (XM Fax) is a legacy product with a proud history of innovation in the T.38 FoIP industry. XMedius was acquired by OpenText in 2020, and has since been re-branded as OpenText Core Fax. The screen shots used to generate this guide were collected from XMedius Fax and may be obsolete. Please report any inaccuracies to our support team.

XMedius fax is capable of both IP address and username/password authentication, but we recommend IP address authentication for best results.

Prerequisites

• You have signed up for a free trial of our Power-T.38 SIP trunking service
• You have access to our customer self-care portal with an assigned role that allows you to add and delete SIP trunks
• You have used the T38Fax self-care portal to create a SIP trunk and you now wish to use its credentials to connect to your Xmedius server 

Incoming Faxes

Similar to a Dialogic Virtual Faxcard SR140, XMedius will accept all incoming connections out of the box. To get inbound working, route some calls to the XMedius server.

XMedius can whitelist incoming connections. Some instances of XMedius may have this enabled, so it is important to check this setting before assuming that inbound will automatically work.

System Configuration ➤ Hosts ➤ [Host Name] ➤ Driver ➤ (right-click) Properties ➤ Peer List

• Use Peer List For Inbound Security [checkbox]
  • The box is unchecked by default

• Unchecked:

[No configuration changes needed in XMedius]

Unchecked means the server will answer incoming calls from any IP.

From a T38Fax perspective, this makes it easy to get inbound faxing working through an IP Auth trunk.

Simply set the IP of the T38Fax SIP trunk to the public IP address of the XMedius server.

If the XMedius server resides behind a firewall, point the traffic to the environment’s firewall and ensure the correct firewall rules and port-forwarding are in place to route T38Fax inbound traffic to the XMedius server.

• Checked:

If this box is checked, XMedius will only allow incoming connections from gateways or proxies listed here in the Peer List.

• Add a new entry into the Peer List to accept incoming calls from T38Fax.

System Configuration ➤ Hosts ➤ [Host Name] ➤ Driver ➤ (right-click) Properties ➤ Peer List ➤ Add

• Host Name:
  • sip.t38fax.com / 8.34.182.111 / 8.34.182.112 / 8.20.91.194
• Port:
  • 5080

• Redundancy settings:
  • Set High Speed Redundancy to 2
  • Set Low Speed Redundancy to 5

Important Note:

Inbound Whitelisting in XMedius is UNTESTED at this time, so you may need to create
multiple peers for all the possible incoming connections via T38Fax trunking:

sip.t38fax.com - 8.34.182.111 - 8.34.182.112 - 8.20.91.194

Outgoing Faxes

There are two main items that need to be configured in XMedius to enable outbound functionality, a new Peer and a new Dial Plan.

1. The Peer is the IP or hostname to which XMedius will send its initial invite.

2. The Dial Plan determines which calls go to which Peer.

• New Peer:

Follow the steps above to create a Peer for T38fax.

When it comes to outbound, sip.t38fax.com is all that is needed for the Host Name, use port 5080 and set High Speed redundancy to 2 and Low Speed redundancy to 5.

• New Dial Plan:

System Configuration ➤ Hosts ➤ [Host Name] ➤ Driver ➤ Properties (right-click) ➤ Dial Plan

Adding a Dial Plan is simple, just enter the Number Pattern and choose the T38Fax Peer.

Here you have options for defining which outbound traffic you want to send to T38Fax.

• The asterisk (*) represents any number of digits or no digits at all
• The question mark (?) represents any single digit

For example:

If there are two matching rules, you can use a Preference value to determine the tiebreaker.

(This is the Properties button in the Dial Plan window)

Preference is specified in descending order by the numbers 1 to 5.

Note: Preference is set when the same numeric pattern is specified for two or more peer gateways.

The gateway with the highest preference is used. If that gateway is not available, the gateway with the next highest preference is used, and so on.

This means you can create outbound failover by making matching dialing rules and setting your Primary Peer (T38Fax) with a higher Preference than your Secondary Peer (someone else), or vice versa. 

Note: If using the SIP From value as the Caller ID, you will have to make sure that each user is configured for “Users cannot override the information (allow the sending with default settings.)" in the Override Policy - Organization Information section. 

That’s it!

From an XMedius configuration perspective, this completes the steps to enable inbound and outbound to work with IP Auth.