BNS SR140 msXfax Enterprise Cloud Connector, M800B AudioCodes SIP Gateway, DMG2060V34 Dialogic DMG2060V34 Installers Guide

The SR140 is a fax server designed for medium to large businesses and government organizations seeking secure and compliant fax communication. It allows direct connection to SIP Trunk service providers' fax networks, ensuring real-time fax over secure IP networks. The SR140 can also be installed in a virtual machine running Windows 2012 R2 in environments such as Amazon Web Services (AWS) and Azure, providing ultimate scalability.

PDF Download

Document

Installers Guide

SR140 edition

ms X fax Enterprise Cloud Connector 2

Installation guide

Better Network Services Group Pty Ltd (BNS Group) ABN 54 003 868 120

Development team

Clive Pereira

Laurence Buchanan

Anthony Miller

Andrew McPhee

Administration team

Flavia Pereira

Gail Buchanan

The software described in this Guide is supplied under a license agreement and may only be used in accordance with that agreement. msXfax

 is a registered trademark of Better Network Services Group Pty Limited

(BNS Group). Other brands or product names are trademarks or registered trademarks of their respective holders.

Trademark acknowledgements:

 Microsoft® is a registered Trademark of Microsoft Corporation Inc.

 Office 365 is a Trademark of Microsoft Corporation Inc.

 Windows®, Windows Server 2012® are registered trademark of Microsoft

Corporation Inc.

 Acrobat® is a registered trademark of Adobe Systems Inc.

 Dialogic® is registered trademark of Dialogic Networks Inc.

 Brooktrout® is a registered trademark / company of Dialogic Corporation

 AudioCodes® is a registered trademark of AudioCodes Inc.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 3

1

1.3

1.4

1.5

1.6

1.7

1.1

1.2

Software notice / latest revisions

Component changes since previous release

Version 8.1 Build 22 - March 2016

Build 21 - November 2015

Build 20 14 May 2015

Build 19 29 April 2015

Build 18 16 April 2015

Build 17 13 October 2014

Build 16 21 September 2014

Software release July 2014

2 Introduction 16

2.1

AWS and Azure 17

2.2

Configuration options

2.2.1

Office 365

2.2.2

Hybrid 18

2.2.3

On-Premise 18

2.3

2.4

Office 365 and on-premises Exchange

Architecture diagrams

2.5

Security to Cloud based Email services

2.5.1

Office 365 hybrid network configurations

2.6

2.7

Member Server design with web console

Fax Servers in a workgroup with web console design

12

3

3.1

3.2

Work sheets

Project tasks template

Pre-installation tasks usually performed by the customer

Work sheet for On-Premises Exchange

23

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

3.1

Work sheet for Office 365 only installations

Installers checklist

4 Telephony configuration guides for msXfax

4.1

39

Introduction 39

5 How to configure on-premises MS Exchange 40

5.1

5.2

5.3

5.4

Introduction 40

Create an AD Account with a mailbox for each fax server

Check IMAP is configured on client access servers

Configuring outgoing fax from MS Exchange

MS Exchange receive connector

5.5

5.6

SMTP Relay from SMTP Based applications

5.6.1

Exchange 2010 internal relay on accepted domains

5.6.2

Exchange 2013 internal relay on accepted domains

6

7

8

6.1

6.2

6.3

7.1

7.2

7.3

Office 365 Fax Server mailbox

How to set up the Fax mailbox in Office 365

Password expiration of the fax server mailbox

Limitations with Office 365 messaging

VM Installation on Windows Server

General requirements

Windows Firewall

Windows 2012 R2 – set up of .Net framework

Installing the Package on Windows server

8.1

8.2

Obtaining the software

Installing the installation package

Software version 8.1 1 March 2016

68

61

76

ms X fax Enterprise Cloud Connector 5

8.3

8.4

8.5

8.6

8.7

8.8

8.9

8.10

SQL or SQL Express preparation

Overview SQL

SQL Server Express installation when no central SQL Server is available

8.5.1

Install pre-requisites on the fax server for SQL Express

Creation of SQL Databases

Creation of msXfax databases

8.7.1

Example of database creation

Mixed mode authentication for SQL Server / SQL Express 98

How to propagate the Direct Indial table 98

9 Installation Setup Files 103

9.1

9.2

AWS or Azure licensing

FIXED MAC addresses on Virtual machines

Upgrading an existing software installation 9.3

9.4

New installation On Premises

9.4.1

Reboot before running the setup

9.4.2

Copy the license file received via email onto the C Drive of the VM

9.4.3

Exchange 2013 specific notes from Microsoft.

9.5

New installation Office 365

9.5.1

Copy the license file received via email onto the C Drive of the VM

115

123

134

139

103

109

10 Brooktrout SR140 Software 159

10.1

Adding SR140 evaluation licences 159

10.1.1

Automatically (this computer is connected to the Internet) 161

11 Installing purchased SR140 licences

11.1

Identifying your SR140 licences

11.2

Uninstall evaluation licenses first

11.2.1

About Using the interactive web method

11.2.2

About using the create a request for email or fax

163

166

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 6

11.3

11.4

Activating a License Automatically 166

Overriding the Default MAC Address Used for Node

Locking 171

11.5

Activating a License Using the Web

11.5.1

Installing Licenses delivered via the web method

172

177

11.6

Troubleshooting SR140 licensing problems

11.6.1

Using the License Manager

179

11.6.2

Displaying and Copying Node IDs 180

11.6.3

Overriding the default MAC Address used for node locking 180

11.6.4

Adding licences and Brooktrout Configuration manager 181

12 Brooktrout Configuration tool

12.1.1

Release 6.7.4 specific

12.2

12.3

12.4

182

188

Technical 188

Backup Brooktrout license files

Outgoing failover fax routing

188

189

13 Start msXfax Services

13.1

Check msXfax BT RX and TX Services are registered

13.1.1

For SQL installations

190

192

14

15 msXfax Licensing - obtaining a license file 195

Configuration 198

15.1

15.2

15.3

15.4

Support tool Teamviewer

Configuring msXfax

Email to your host configuration

Protective marking and other msXfaxboot.ini edits

15.5

Turn on Dyanmic Routing if required

15.5.1

Maximum allowed SMTP within your Email network

15.6

How to stop and start the services

198

200

202

203

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 7

16 Dynamic Routing to Exchange Distribution Groups

16.1

16.2

204

How does msXfax build the email address to send to the group? 204

Create the Distribution Group 207

17 Inbound fax routing using Office 365

17.1

17.2

Office 365 Exchange Admin Center

Activate Dynamic Routing msXfaxboot.ini

214

217

18 Gmail for business Fax Server mailbox

18.1

18.2

Set up the Fax mailbox in Gmail for Business

Restrict use of the fax server to your internal users

218

19

19.2

19.3

19.4

19.5

19.1

19.2

19.3

19.1

Testing the fax server

Check that services start correctly

Check log files

Check the Audicodes message log

Send a test fax from Outlook using Office 365

Send a test fax from Outlook for On-Premises Exchange

Sending a test fax from the dashboard

SMTPFAST utility

Receiving faxes

219

224

225

226

228

219

220

223

20 Cover sheets

20.1

20.2

20.3

Default cover sheet

Boot.ini settings and overview

User Specified Coversheet keyword/value pairs

229

230

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 8

21 Troubleshooting 232

21.1

21.2

Rehosting your SR140 license

SR140 Node type

232

22 Optional: msXfax Web console 234

22.1

General 234

22.1.1

SQL Database Administrator (DBA) 236

22.1.2

Active Directory Security Groups 237

22.2

Installation of IIS for the WebConsole

22.2.1

Install Internet Information Server

22.2.2

Installing IIS on Windows Server 2012 R2

22.3

Install the Web console

238

240

249

22.4

Configure IIS 8 on Windows 2012R2

22.4.1

Create folder for msXfax console web site

22.4.2

Configure IIS

22.5

Configure settings and test webconsole connection

22.5.1

Test the connection to SQL

22.6

Configure sender domains

22.6.1

Destination domains

22.6.2

Inbound Direct Dial Inwards controls

266

267

252

253

261

264

23 Reporting Software

23.1

23.2

23.3

23.4

23.5

User permissions SQL Server

Configure ODBC on one FAX server to msXfax-

Provisioning database

Configure ODBC on the same Fax server to msXfax-

Transactions Database

Install msXfax reporting software

Offline activation & Renewal of licences

269

273

277

286

24 Powershell utility for Distribution Groups

24.1

Powershell generator for Exchange Distribution groups

290

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

24.1.1

Run the utility

24.2

Run the Powershell script for Exchange

25 Uninstalling msXfax

25.1

Uninstalling Brooktrout SR140 licenses

26 International dialling codes

297

298

299

293

295

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Table of figures

Figure 1 msXfax installed on a VM in Customer VPN network with SIP

Gateway in the customer’s on-premises datacenter

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Foreword

BNS Group’s commitment to providing well architected software continues with msXfax Enterprise version 8.

BNS would like to acknowledge and thank:

 AudioCodes staff in Australia for their co-operation.

 Dialogic Technical support Japan and the management team in Australia.

 Sonus staff in Australia for their co-operation

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Software notice / latest revisions

1.1

Component changes since previous release

8.1 22 NO

8.0 21 NO

8.0 20 NO

8.0

YES

8.0 17

Drivers

XCAPI

Drivers

New

(3.6.2)

NO (6.7.3)

Reporting DDLs Other

NO NO

NO (6.7.2)

YES (6.7.2)

6.7.1

NO NO

YES

YES This is the First SQL release and web console release

Base build version 8 no

SQL

1.1

Version 8.1 Build 22 - March 2016

 Introduced support for XCAPI drivers and software from TE-Systems.

 Upgraded Brooktrout support to 6.7.4

1.1

Build 21 - November 2015

 Fix bug to convert legacy msXfax XP User Database.csv routing table to new routing table format.

 Auto Purging of Outbound Faxes from Audit directory now included in Dispatcher

Service.

 Handle mime messages that do not have any message body, inject a blank line so current logic works.



Support special key Special-ClarendonClickHomeNoCover-int=1 to handle

Clarendon ClickHome Application where mime message has no body text and cover page needs to be supressed.



Inform Admin via alerts for all instances where inbound faxes are unable to be written to UNC Path.

 Provide the abiliy to requeue inbound faxes by date and time.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 13

 Update Console control services so Dialogic SIP layer can be started/stopped.

 Faxstop/Faxstart utilities now also stop/start sip layer.

 Updated inbound fax template informing user to check for completeness when there is a possibility that the fax may not have been received completely. Testing has shown that some fax machines like the Samsung Xpress M2885FW do not complete the end of fax handshake correctly and can cause an incomplete fax status to be raised even though the fax has been received correctly. The responsibility is passed to the user to verify.

1.2

Build 20 14 May 2015

 Fully tested with Sonus Session Border Controllers (SBC)

 Supports SIP Trunking with Optus / Sonus SBC's

 Support for broadcast fax similar to msXfax 7.6

 Includes the latest SR140 Brooktrout SDK 6.7.3

 Performance improvements

 Co-exists with Microsoft Skype for Business

 Support Broadcast Fax.

 Support coverpage keyword cs#name

 Support keyword [bypasscover]

 Support keyword faxsender#

 Stop invalid sql transactions being created on a retry in the Dispatcher.

 Improve FAXStart & FAXStop utilities

1.3

Build 19 29 April 2015

 Support Inbound DR DDI number in sql table and web console. This allows a primary and DR DDI number to be supported.

 Create an Inbound Folder if it does not exist under the share. Raise an alert if the folder can’t be created.



Delay system alerts on a system boot for services that have not yet started.

1.4

Build 18 16 April 2015

Build 18 supports:

 SQL service and SQL databases

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 14

 Web console for managing SQL provisioning database and viewing transaction logs.

 Provisioning database allowing service providers and developers to populate fax numbers and customer account information for multi-tenant services.

 Reporting software including graphs.

 Latest SR140 SDK 6.7.2 released by Dialogic February 2015

1.5

Build 17 13 October 2014

Build 17 supports:

 NDR’s for receive only servers. IMAP is always configured for NDR processing in all configurations.

 Other changes.

1.6

Build 16 21 September 2014

Build 16 supports:

 Email Protective Marking compliance checks including DLMs to 2012.3 standards.

 120 fax channels per VM

1.7

Software release July 2014

This release is the first release of msXfax Enterprise version 8 without SQL

Databases.

BNS is releasing updates progressively providing customers with the benefits of virtualization commencing with:

 July release supporting domain based cover sheets.

 Followed by progressive releases with SQL interface layers, reporting etc.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 15

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Introduction

msXfax Enterprise Cloud Connector (msXfax ECC) is focused on medium to large business and Government who understand the importance of fax from a legal perspective along with security and compliance.

As more customers migrate their problems to service providers (generically called

Cloud) so too will their needs for fax communications need to connect to services providers for email, telephony and other services.

Smaller customers with no regard for security or privacy will simply move their fax numbers to pure fax service providers such as EFax.

Medium to large customers with good security and privacy policies understand that if they outsource their fax completely, they may lose control of the fax images and files which contain sensitive information such as: client data, signatures and other private information.

Loss of control could lead to breach conditions of the Australian Privacy laws should the data be exposed.

Equally, many fax service providers simply deliver an inbound fax via SMTP which offers no guaranteed delivery. A fax is legally deemed to be delivered to a destination when the fax machines final pages are transmitted successfully and transmission summary pages printed. Failure to deliver a fax from a service provider to the customer could mean potential legal issues in cases of disputes or instructions from clients. msXfax ECC allows direct connection to a SIP Trunk service provider’s fax network providing real time fax over secure IP networks. Examples include: Optus Evolve

SIP Trunk service providing a range of the customer’s Fax numbers held inside the

Optus network allowing secure 2 way fax communications real time using T.38 fax protocol or G.711 QOS Service.

Optus is hosting the fax numbers for their customers provide reliable connections to the public switched telephone network allowing direct source and destination fax communications with no intermediate store and forward entities. msXfax ECC is designed to run a customer’s VM infrastructure providing secure

IMAP/SSL and SMTP/TLS (secure direct protocols) direct connections to Office365,

Gmail for business and other service providers using secure direct protocols. msXfax ECC can also be run on a customer’s Amazon or Azure VM infrastructure providing ultimate scalability msXfax ECC can be installed in a virtual machine running Windows 2012 R2 in environments such as:



Amazon Web Services (AWS)



Azure



Customer provisioned VM platforms such as VMWare/Hyper-V

Note: a fixed MAC address is required for Brooktrout SR140 licenses.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 17

Azure: Microsoft does not guarantee that a MAC address will not be changed.

AWS: check with that provider.

Contact BNS if you wish to install on a VM in any cloud environment such as AWS or

Azure.

2.1

AWS and Azure

AWS and Azure are termed “Customer VPN Networks” in this documentation.

Any component which must reside in the customer’s own datacenter is termed “Onpremises network”.

For example:



SIP Gateways and ISDN lines must reside in the customer’s on-premises network.

 msXfax on a VM can reside anywhere, provided the VM has a fixed MAC address and quality of service provides no packet loss between the VM and

SIP Gateway.

Note: Customers who plan to install msXfax in AWS or Azure MUST contact BNS for correct licensing procedures.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

2.2

Configuration options

2.2.1

Office 365



Uses IMAP to connect to a Office 365 Mailbox to read freeform fax requests.



Uses SMTP with TLS to connect to smtp.office365.com to send confirmations/inbound faxes to Office 365 Users

2.2.2

Hybrid



Uses IMAP to connect to a Office 365 Mailbox to read freeform fax requests.



Uses a Smart Host to accept connections from an on-premise exchange

Server via a send connector using domain addressing



Uses SMTP to connect to an on-premise exchange server to send confirmations/inbound faxes to on-premise Exchange/Office 365 Users.

2.2.3

On-Premise



Uses IMAP to connect to a on-premise Exchange Mailbox to read freeform fax requests.



Uses a Smart Host to accept connections from an on-premise exchange

Server via a send connector using domain addressing



Uses SMTP to connect to an on-premise exchange server to send confirmations/inbound faxes to on-premise Exchange.

2.3

Office 365 and on-premises Exchange

msXfax can be configured to:



Send and Receive faxes directly to Office 365.



Send and Receive faxes directly to Gmail for business.



Send and Receive faxes directly to Email hosting service providers offering

IMAP4 with SSL and SMTP with TLS encryption.



Send and Receive faxes directly to customer on-premises SMTP systems such as Microsoft Exchange Server 2007 through 2013+.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

2.4

Architecture diagrams

Figure 1 msXfax installed on a VM in Customer VPN network with SIP Gateway in the customer’s on-premises datacenter

msXfax will connect to any single email service whether on-premises or in the cloud.

Routing of inbound faxes dynamically to Email distribution groups is the easiest way to manage inbound fax routing.

Distribution Groups in Exchange on-premises or Office 365 are great examples of managing fax routing from within your email environment.

In a hybrid Office 365 / On-premises Exchange environment msXfax can be configured to:

1. Accept Domain based fax addressing eg: ( [email protected]

) which is routed from an Outgoing SMTP Connector on Office 365 to your internal SMTP servers then routed to msXfax and;

2. Process msXfax Freeform addressing using a mailbox on Office 365 accessed over IMAP/SSL and;

3. SMTP responses from msXfax will go back to users via an internal Exchange

Server or directly to Office 365 using SMTP/TLS.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

2.5

Security to Cloud based Email services

20 msXfax natively supports Office 365, Gmail for Business and other email services using encrypted protocols for maximum security.

Specifically, msXfax supports:

1. IMAP4 protocol with SSL encryption to process a mailbox using msXfax freeform addressing and;

2. SMTP protocol with TLS encryption to deliver incoming faxes & confirmation messages to email addresses in your cloud email platform.

3. A mailbox per Fax Server is also required to process NDR’s via the IMAP protocol.

2.5.1

Office 365 hybrid network configurations

Customers with a hybrid network model allows Office 365 to make SMTP / TLS connections back into the on-premises network for routing SMTP traffic from Office

365 to On-premises SMTP Servers. msXfax in this model offers flexible routing of outgoing Office 365 based fax requests using domain addressing such as ( [email protected]

). Office 365

Connectors can be configured to send fax requests to your on-premises msXfax fax server. For more information refer to Office 365 network configuration documentation or contact Microsoft. msXfax in this model can be configured to send incoming faxes & confirmations to the on-premises SMTP Server or the Office 365 SMTP Service using TLS encryption.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

2.6

Member Server design with web console

The standard method of deployment for enterprise fax servers will include deployment of a web console on at least one fax server. msXfax reporting software can be located on any of the member servers.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

2.7

Fax Servers in a workgroup with web console design

Customers requiring network separation or for other reasons, can place msXfax cloud connector software in a workgroup with some limitations. msXfax reporting software can be located on the member server.

Limitations which apply include:

1. UNC Copies and other domain permission dependencies may or may not work depending on the customer’s design.

2. Such a design implies firewall rules which could impact on functionality.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Work sheets

3.1

Project tasks template

Assumptions:

1. Windows Server 2012 R2 VM used for msXfax Connector software will be a member server in a domain. If not please advise architect.

2. Euro ISDN E1/BRI or T1 service either to PBX or direct to network is being used.

If not please advise architect.

Task

Initial Tasks

Order telephone service or connection PBX.

Who

(Customer, Integrator or Both)

Customer

Comments

If PBX then connection is the same as a direct service to the network. Ie:

Configure the same as Telstra or

Optus or other Euro ISDN provider.

USA = T1

If a SIP Trunk is to be used this is more complex requiring specific expertise.

International Dialing Customer Confirm which Telco is being used and the Fax international dialing code for quality of service on the telco network. Eg: Optus 0019 and

Telstra 0015

IP Address required with subnet mask DNS and Default gateway

Pre-configure AudioCodes SIP

Gateway (eg: M800B) if one is being used. Just configure the IP address unless all other information is known such as IP addresses of msXfax VMs.

Record the serial number of the

M800B in the work sheet provided in the installation guide. Also the

Integrator

Customer

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 24 rack/location reference.

Install M800B into rack and connect to telephone service (ISDN

E1/T1/BRI)

Customer A screw driver is required for the mounting brackets.

Connect 1 or 2 ethernet cables to the leftmost yellow ports on the M800B

(1 is active and the other is standby for installations that have dual switch configurations)

Customer Build a Windows Server 2012R2

VM 4GB ram with sufficient disk space to store any audit files (Fax copies) 50kb per page on average.

MAC Address on the VNIC has to be FIXED.

Customer Vmware Instructions in the manual.

If unable to fix the MAC address notify the architect.

Customer Provide integrator with

ServerName (Computername) and

IP Address of each VM onto the work sheet with subnet mask, DNS and Default Gateway.

Check that IMAP service on

Exchange is configured and running

Customer Instructions in the manual.

Create an AD Account with a mailbox (Normal user permissions).

Customer

Setup 2 x Domain Security Groups in AD

Customer

Instructions in the manual. Provide password to integrator during installation.

Note: the installers’s windows account must be a member of msXfax-Admin-Group security group.

Add other users as required who will administer the fax system.

Customer If SQL Express is to be used download SQL Express 2014 or better.

Main installation work

Both If a shared SQL Server is to be used:

Provide DDLs to SQL DBA along with instructions for required accounts (SQL Account and

Domain user accounts including msXfax-ServerName AD Account

Note: the Windows domain accounts of the fax administrators must be added with full permissions to the databases along with a SQL Account msxfax-connection which has full permissions to the databases.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Installer will need local administrator privileges to install all software.

Customer and Installer work together to configure and install the solution following each step in the manual.

Outbound Email Protective

Marking/DLM classifications allowed

Customer

Both

Place a call to the Telstra

FaxStream test number 1300

368999

Both

Testing outbound and inbound fax Both

Check that results.

A simple test plan should be developed.

When all testing is completed, arrange any cutover of existing services to the new installation

Both Advise any follow up requirements Sign off on installation

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 26

3.1

Pre-installation tasks usually performed by the customer

One sheet per fax server

Pre-installation task

Build a Windows 2012 R2 VM for each fax server required.

Requirements

4GB ram Min.

OS disk based on your SOE.

Application disk (D/E) for use by msXfax 50GB+ subject to audit retention requirements

4 x VCPU

1 x VNIC with 1 IP Address

MAC Address of VNIC has to be fixed.

If a Windows firewall or other server based firewall is on, port 25 must be allowed in for a Transmit fax server.

Create in AD an Installer account called msXfax-Installer

This account must be a member of the local administrators group.

Setup an account in AD with an

Exchange Email Address called msXfax-<ServerName>@yourdomain

<ServerName> is the fax server computer name.

IMAP must be enabled and operational for this account.

IMAP/SSL on port 993

If a shared SQL Server is to be used: have your DBA setup the 2 databases required for all fax servers. All fax servers will use a common database.

Documentation can be provided along with the DDLs.

If a shared SQL Server is to be used: have your DBA create a SQL user called msxfax-connection with full permissions to both databases.

Passwords should not expire as this is being used by a web based console.

Completed Comments

For pure Office 365 installations, create an email address on

O365 with IMAP permissions and a separate account AD

Account called msXfax-

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

If a shared SQL Server is to be used: have your DBA assign full permissions to both databases for both AD Accounts called: msXfax-Installer and msXfax-<ServerName>

Advise the installer the email addresses to be used for:

 Alerting of error messages:

Advise install of the SMTP server

IP address or DNS name to be used by this fax server using port

25 to route emails into your email network.

Advise Installer of which Telecom provider handles international outbound calls

Allocate an IP Address for use by any SIP media gateway or SBC or IP-PBX etc to be used by this fax server

Advise installer what SIP media gateway or SBC or IP-PBX is intended to be used.

If O365 is to be used, an email address with

27 password is required for sending

SMTP/TLS messages to your

O365.

If SQL Express is to be used, download the software onto the

Windows Server VM in a folder called c:\Build

If SQL Express is to be used, create a service account called msXfax-SQLExpress-Service or something similar aligned to your standards. http://www.microsoft.com/enau/download/details.aspx?id=42299

Password does not expire and make this account a member of the local administrators group on each fax server VM.

Software version 8.1 1 March 2016 known well before any planned procurement to ensure that some interop testing has been conducted.

ms X fax Enterprise Cloud Connector 28

Advise installer if http/https access to the internet is available or not from each fax server during the course of the installation.

Advise installer what default format inbound faxes should be presented in

Advise the installer what

Communication Subscriber ID

(CSID) is to be used for fax communications

PDF or TIF

Agree on the number of logical channels to be used for outbound and inbound.

Service providers, SBC, Media gateways, IP-PBX’s and msXfax must all use the same values.

This is typically the public general fax number of the organization. If there are many general numbers or is a multi tenant environment then make this value generic eg:

Microsoft or Fax Server

Confirm that the network between the fax server VM and the SIP Gateway/SBC/Ip-PBX is on a network with no packet loss

Provide Company name and address, contact name, phone number and email address for licensing purposes

This is required for registration of licenses

Eg: Reception@xxxxxxxx Default email address for ANY inbound fax which does not have a specific route defined.

If dynamic inbound routing is not to be used:

1. Provide a list of inbound numbers with email addresses to the installer.

2. Provide any UNC paths faxes are to be sent to for the same number.

If Dynamic routing is to be used:

1. Provide a list of the DDI number ranges which the service provider/equipment will

Eg: 0262121000 to 0262121099

Default email address to be assigned to each Distribution

Group.

Powershell generator creates a basic powershell script to create a distribution group for

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector present for inbound fax calls.

2. Confirm if the full number is to be presented inclusive of area codes or not.

3. Discuss with the installer the use of a powershell script generator for the entire range.

If a separate range is in DR advise the installer what is the mapping of

DR to prod inbound numbers.

29 each inbound number with a default member of the group to receive faxes.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 30

Download location for SQL Express 2014 http://www.microsoft.com/en-au/download/details.aspx?id=42299

Advise installer if a copy of each fax sent or received is to be sent to an email address.

Eg: this could be your document management system.

O365 is defined by

Microsoft. 25MB

Advise what the maximum SMTP

Message size (MB) allowed to be sent from the fax server to your onpremises SMTP servers.

Setup an Exchange SMTP

Connector with address space = yourdomain.fax to send to another email server (Smart Host) at IP

Address of this fax server. If multiple servers then include all IP addresses of all OUTGOING Fax servers.

Supply the Client Access Server IP address or (CAS DNS Pool name) for IMAP protocol access to the msXfax-<ServerName> mailbox.

Note: authentication is none for smart host authentication.

If you wish to lock down what

SMTP Servers msXfax will accept messages from, this can be done on the fax server using a positive white list of specific IP Addresses.

O365 in a hybrid network an SMTP

Connector for address space yourdomain.fax will have to also point back to your onpremises smtp servers. Refer to

Microsoft how to do this.

O365 is defined by

Microsoft.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Email Protective Markings

If you intend to implement protective marking checks on this msXfax server advise the installer the EPM classifications and DLM’s which the gateway will allow to go to the public network.

Defaults are:

Classification UNCLASSIFIED and UNOFFICIAL

DLM’s

FOR-OFFICIAL-USE-ONLY

SENSITIVE

SENSITIVE:LEGAL

SENSITIVE:PERSONAL

Supply to the installer the following values. Users who attempt to send a fax with a classification or a DLM which does not match those allowed via this gateway will produce an error message to the sender including the following:

General-EPM-Agency-str=Agency Name

General-EPM-Agency-Fax-PolicyUrl-str=http://www.xxxxxxxxx.gov.au/faxpolicy.htm

[email protected]

General-EPM-Support-Name-str=Agency Support

General-EPM-Support-Phone-str=+61 x xxxxxxxxx

General-EPM-User-Classification-URL-str=http://www.agency.gov.au/agency_userclassification.htm

General-EPM-User-Marking-Url-str=http://www.agency.com.au/agency_usermarking.htm

Assumption is that EPM within the agency is compliant with 2012.3 or better.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

3.2

Work sheet for On-Premises Exchange

Configuration item

Computer Name of the Windows

Server VM used for this msXfax instance

IP Address of your Windows Server

VM used for this msXfax instance

DNS IP Addresses used for this msXfax instance

Location of the VM

Other VM related information

Value

SIP Gateway

SIP Gateway model number & serial number

Model:

Serial number:

IP Address of the SIP Gateway

Version of firmware in SIP Gateway

Telephony identification

International Dialing

Serial number of the SIP Gateway

Installation date of the SIP Gateway

Location of the saved config ini file

SR140 License key(s) used on this fax server

MS Exchange

IP Address/DNS msXfax will use to send SMTP to your Hub Transport or Edge or other SMTP Server

Comments

Eg: own DC, AWS, Azure etc

Anything you feel is important

Eg: AudioCodes M800B 2xE1

Or Dialogic DMG2060V34

Eg: 6.80A.227.005

If ISDN this may be the Telstra /

Optus service reference number.

Service support etc.

Eg: Optus 0019 and Telstra 0015

Each time you change the config save a copy to your central config repository & send a copy to [email protected]

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 33

Exchange SMTP Connector(s) which route address spaces to this msXfax instance

Mailbox email address used for this msXfax instance

Mailbox Password used for this msXfax instance

Eg:

@Outlook.fax

@MyDomain.fax

@Fax.MyDomain.com

Each msXfax server uses a unique mailbox email address for NDR processing and also for freeform addressing support. A value such as:

Fax-<ServerName>@mydomain.com

Do not record it here Just a reminder you will need it and it should be in your password database.

IMAP must be enabled on this mailbox

IMAP Service must be running on

Client Access Servers (CAS)

DNS to access IMAP CAS servers or assign an IP address for msXfax to access one of them.

License renewal notifications email address

Note: msXfax uses IMAP/SSL.

System Alerts email address

This is the email address of the person or DL to be notified about warnings to renew software licenses.

This is the email address of the person or DL to receive system alerts from this fax server.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

3.1

Work sheet for Office 365 only installations

Configuration item

Computer Name of the Windows

Server VM used for this msXfax instance

IP Address of your Windows Server

VM used for this msXfax instance

DNS IP Addresses used for this msXfax instance

Location of the VM

Other VM related information

Value

SIP Gateway

SIP Gateway model number & serial number

Model:

Serial number:

IP Address of the SIP Gateway

Version of firmware in SIP Gateway

Telephony identification

International Dialing

Serial number of the SIP Gateway

Installation date of the SIP Gateway

Location of the saved config ini file

Comments

Eg: AudioCodes M800B 2xE1

Or Dialogic DMG2060V34

Eg: 6.80A.227.005

If ISDN this may be the Telstra /

Optus service reference number.

Service support etc.

Eg: Optus 0019 and Telstra 0015

Each time you change the config save a copy to your central config repository & send a copy to [email protected]

SR140 License key(s) used on this fax server

Eg: own DC, AWS, Azure etc

Anything you feel is important

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Office 365

Mailbox email address used for this msXfax instance

Mailbox Password used for this msXfax instance

IMAP must be enabled on this mailbox

License renewal notifications email address

System Alerts email address

Do not record it here

Each msXfax server uses a unique mailbox email address for NDR processing and also for freeform addressing support. A value such as:

Fax-<ServerName>@mydomain.com

Just a reminder you will need it and it should be in your password database.

This is the email address of the person or DL to be notified about warnings to renew software licenses.

This is the email address of the person or DL to receive system alerts from this fax server.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

3.1

Installers checklist

Configuration item/task

Obtain from your project manager or customer:

SR140 license key(s)

Serial number for msXfax reporting software

Confirm customer has done all the pre-installation checklist items and obtain all the information from the customer’s pre-installation task list

Configure initial IP of the SIP Gateway and disable

DHCP/BootP and rack it.

Configure the SIP Gateway to completion

If not using a SIP Gateway then confirm that any SIP

Trunk SBC/IP-PBX services is ready. vm installation on windows server

Set firewall

Install .net

Install software (Footprint) to non OS drive.

Install SQL Express if required

If SQL Express is used then you will have to create the databases using the DDLs supplied.

Import DDI numbers from excel to SQL is optional

(This can be done later)

Install msXfax Cloud Connector

If upgrading there is a section on this

Otherwise perform a new installation

License SR140 software

Configure SIP SR140

Set SQL Interface service logon credentials

Start all services

Wait for green ticks on the dashboard. Deal with any issues.

Send a test fax from dashboard back to yourself. If there are any issues with connectivity to IP-PBX or similar service which you have no control over, then point to your own IP to complete the installation checking all other functionality.

Checked  Comments / follow up work

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Check that outbound and inbound work to the default email address for inbound. This checks SMTP etc all work fine.

Chapter 15 email protective marking

Install web console

Setup any default cover sheet required. Usually this is a disclaimer style cover sheet on a per domain basis.

Install reporting software and license it

If dynamic routing is to be used then work with customer to set up Dist groups with on-premises exchange. Of O365 then they may have to do that manually.

Configure Cover sheets if outbound faxing is required and needed

Test an inbound fax from the outside world into the customer’s DDI range. Make sure it all works.

Test outbound fax to the outside world

Test any audit copies which are sent to an email address that they arrive ok. From there it is the customer’s responsibility.

Train customer to use the web console viewing log files etc

Train customer to use reporting software. Show them the standard reports which were imported. Prepare a few ad hoc reports for them so they get the idea and can play with that.

Send a copy of the SIP Gateway config to [email protected]

Customer sign off (below)

Installer Name _________________________________

Signature _____________________________________

Date ______________

Customer Name ________________________________

Signature ______________________________________

Date _______________

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Agreed follow up action points noted.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Telephony configuration guides for msXfax

4.1

Introduction

msXfax runs on a customer VM and communicates with the SIP Gateway or Session

Border Controller or compatible SIP based communications device. msXfax used Dialogic Brooktrout Sr140 the world leading Fax over IP protocol stack and API sets.

Extensive interop testing is conducted by Dialogic and BNS conducts its own testing and develops easy to use configuration guides for its partners.

Contact BNS for the latest configuration guides for: AudioCodes, Sonus and other vendors.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

How to configure on-premises MS Exchange

5.1

Introduction

A mailbox per fax server is required for processing Freeform addressed faxes and Non-

Delivery Reports.

Domain addressing ( [email protected]

) is the easiest method of addressing faxes in conjunction with Send SMTP Connectors.

5.2

Create an AD Account with a mailbox for each fax server

 A Service Account with a mailbox per fax server is required.

Recommended naming msXfax-<ServerName>

 The permissions for this account on the network will be just like a normal user, however, it will be granted logon a service right during the installation.

 This account should also be made a member of the local administrators group on the VM.

This account will also require full permissions to both SQL Databases. Instructions provided in the relevant section.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 41

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Once the mailbox has been created, select properties, mailbox features.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 43

5.3

Check IMAP is configured on client access servers

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 44

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 45

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 46

5.4

Configuring outgoing fax from MS Exchange

This example is Microsoft Exchange Management Console for Exchange 2010

 Right click Hub Transport

 New Send Connector. Call the connector msXfax.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 47

Different address space can be used such as YourCompanyName.FAX

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 48

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 49

 Enter the IP address of the msXfax VM that Exchange will route outgoing fax requests to.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 50

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 51

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 52

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 53

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 54

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 55

 The connector can be renamed to make it more descriptive and the message size can be restricted. 10MB is the default set by MS Exchange. Please review this setting to avoid limiting capabilities for your users. Perhaps set to 50MB as it is only being delivered to the fax server.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

5.5

MS Exchange receive connector

A receive connector may or may not need to be created subject to your existing configuration of Microsoft Exchange.

If inbound messages from msXfax are not accepted by Microsoft Exchange then create a specific receive connector. Example for Exchange 2010.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 57

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 58

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 59

 After you have created the receive connector, select the properties and allow anonymous connections.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

5.6

SMTP Relay from SMTP Based applications

If you have an application server which needs to send a fax using SMTP, your

Exchange server can be securely configured using a number of methods including:

Receive connectors, Accepted domains etc.

Your security team should consider all options open to them before considering any type of relay in Exchange.

5.6.1

Exchange 2010 internal relay on accepted domains

Internal Relay Domain to xxxx.FAX is relatively safe because

1. The domain space is invalid on the Internet and would be rejected at your edge servers.

2. msXfax is a known email server outside of your Exchange organization but relay is only internal not external.

5.6.2

Exchange 2013 internal relay on accepted domains

Internal relay is documented at https://technet.microsoft.com/en‐ us/library/jj657737(v=exchg.150).aspx

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Office 365 Fax Server mailbox

msXfax supports direct processing from an Office 365 mailbox.

This provides a simple to use outbound/Inbound fax processing service using your own on-premises fax server.

An Office 365 user Exchange account is required for the fax server with special restrictions on the mailbox so that only your users can send fax requests to the fax server.

SSL & TLS encryption is used to protect all fax messages which are sent to and from

Office 365.

6.1

How to set up the Fax mailbox in Office 365

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 62

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 64

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 65

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 66

6.2

Password expiration of the fax server mailbox

Office 365 offers some options to control password expiration. http://office.microsoft.com/en-au/office365-suite-help/set-up-user-passwords-tonever-expire-HA102816049.aspx

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

6.3

Limitations with Office 365 messaging

Office 365 has a 25MB limit on message sizes. msXfax allows for this limitation and will split incoming and response messages to users within the 25MB default.

Below is the table of Office 365 message limits.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

VM Installation on Windows Server

7.1

General requirements

msXfax can be installed on a VM which has a guest operating system:



Windows 2012 R2.

Other pre-requisites:



Net Framework 3.5 is required

. This guide contains instructions on which features are to be configured.



.Net 3.5 and .Net 4.5 can both be installed on Windows 2012R2. This guide contains instructions on which features are to be configured.



Inbound servers minimum memory = 3.75GB (AWS M1-Medium)



Outbound servers minimum memory = 6GB



FIXED MAC ADDRESS (Contact BNS if you intend to install on Azure or AWS)



Minimum 4 VCPU in all cases



Disk space depends on how many audit copies of faxes are to be stored on the

VM.



1 IP V4 address on 1 VNIC



Microsoft SQL 2008 or greater is supported.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

7.2

Windows Firewall

If your policy requires Windows Firewall ON you must allow SMTP inbound for delivery of messages from On-Premises Exchange.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 70

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 71

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 72

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

7.3

Windows 2012 R2 – set up of .Net framework

 From Server Manager

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 74

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Accept defaults after this until the frameworks are installed.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Installing the Package on Windows server

8.1

Obtaining the software

Software is downloaded from www.bnsgroup.com.au

follow the quick links to msXfax cloud connector.

8.2

Installing the installation package

The file downloaded is called “msXfax Enterprise Install Package.MSI”.

 Login into the Windows Server VM with local administrator privileges.

 Select Start then type CMD.

 Right click the CMD icon and select Run as an administrator.

 Navigate to the MSI package as shown below

 Run the MSI and follow the wizard.

8.3

SQL or SQL Express preparation

If your business requirements do not require: SQL transaction logging, web console based provisioning or reporting then proceed to the next section to install the msXfax

Cloud Connector.

8.4

Overview SQL

Customers requiring a simple implementation may not require the management features provided by the web console or SQL logging for audit and compliance. msXfax provides an SQL Service which can write transaction records to a SQL

Transactions database for inquiry and reporting purposes.

A web console is provided for use with SQL for:

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

1. Managing Inbound DDI routing

2. Outbound fax controls

3. View transaction logs msXfax also has an optional reporting module capable of producing ad hoc reports, scheduled reports, graphs and dashboards.

8.5

SQL Server Express installation when no central SQL

Server is available

Customers without SQL Server in their network can deploy SQL Server Express on one or more of their fax servers. Customers with a central SQL Server do not need to install SQL Express on any fax server and can skip this section (proceed to section 21.3)

Download location for SQL Express 2014 http://www.microsoft.com/en-au/download/details.aspx?id=42299

SQL Express can be installed on a fax server. A second fax server can access the

SQL Express Database if required.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

8.5.1

Install pre-requisites on the fax server for SQL Express

 Run Server manager

 Add roles and features

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 79

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Run the EXECUTABLE SQL Express 2014 with tools 64 bit to extract the installation setup files.

 Select non-os drive just over type the C drive with D or E

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

BNS recommends that a service account be setup in AD or via local users in a workgroup design.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector



If installing in a domain, allocate an AD Service account. See following pages.



This example shows the creation of a local user.

A service account in AD or a local user is better than the virtual service account.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Make the service account a member of the administrators group.

 Record the password for the customer. Use the same password on all servers.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 86

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

8.6

Creation of SQL Databases

This section applies in all cases whether SQL Express or a central SQL Server

 If you installed SQL Express then you are the DBA and you have to perform the creation of databases.

 Navigate to the folder under program files\ BNS Group\msXfax Installation

Software and Tools\msXfax SQL DDL scripts msXfax requires your SQL Database Administrator (DBA) to:



Create 2 databases. Your DBA can name the databases according to your naming conventions.



Set up permissions for the msXfax-<Servername> AD\email Account to have full read/write permissions to both databases.



Set up permissions for your installer account to have full read/write permissions to both databases.

The Windows login used by the installer of the software must have FULL permissions to the databases created by your DBA.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Please request that your installer Windows login account be allocated full permissions when the databases are created in this section.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

8.7

Creation of msXfax databases

Your SQL DBA can perform this task on the production SQL server and if a DR SQL server is used in your environment then a mirror should be set up in the DR Site or a replica if SAN technology of similar is being used.

Sizing the database:

Database name msXfax-Provisioning

Functional use

Used for management of

DDIs, outgoing controls and other features.

Sizing

10Mb initial size. msXfax-Transactions Contains 2 tables:

Outgoing transactions and incoming transactions.

1 million records in the received fax transaction table results in approximately 9GB of data/index space.

200,000 records in the outgoing fax transaction table results in 175MB of space for data/indexes.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

When you ran the msXfax Enterprise Installation Package, 2 .SQL files were created for use by your SQL Database Administrator. These are located in:

SQL DDL command file Description msXfax-Transactions.sql controls and other features.

Contains 2 tables:

Outgoing transactions and incoming transactions.

 Provide a copy of the .SQL files to your SQL DBA.

 SQL DBA will execute the SQL statements using SQL Management Studio or other tools against the respective Databases to create the tables.

8.7.1

Example of database creation

 Open SQL Management Studio

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 91

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 92

 Size the database based on the estimates earlier in this manual.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 93

8.8

Login Permissions msXfax-<ServerName> Account

Your SQL DBA must provide full permissions to both databases to the msXfax-

<ServerName> account.

Tip: where many fax servers exist accessing one SQL Server, create an AD Group to assign permissions to SQL Databases which contains all the msXfax-

<Servername> accounts, installer account and any other accounts which need full access to the databases.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 94

Other permissions required for msXfax to operate correctly are also included:

Service Account functions

Permissions required Comments

SQL DBA to determine best way.

Access msXfaxprovisioning & msXfax-Transactions

NTFS file system

Full permissions

Full control to folders and sub folders

BNS Group\msXfax\.......

Access DNS Servers Read

Access Global Catalog

Servers Active

Directory installations only

SMTP Send SMTP messages to

Exchange Hub Transport servers.

Receive SMTP messages from

Exchange Hub Transport servers

Registry None

Interactive Logon Not required

AD\Exchange Mailbox Required: one for each fax server.

SSL and TLS for Office

365

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 95

Example setting to allow all msXfax-<ServerName> accounts to access databases on a central Microsoft SQL Server.

Note: for a SQL Express design which is co-located on the fax server within a

Workgroup, it is recommended that SQL Authenticated user account is created rather than a Windows Authenticated account. Reason: in a multi fax server environment in a workgroup there are limitations with Windows authentication.

Therefore, use a SQL Server user account in such a situation.

In a central SQL environment or a SQL Express instance within a domain a security group can be created or you can assign permissions on a per account basis.

 Search the Ad Domain

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 96

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 97

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

8.9

Mixed mode authentication for SQL Server / SQL

Express

 Server Authentication must be SQL Server and Windows.

8.10

How to propagate the Direct Indial table

This section may not be required check the design.

Customers with blocks of indial ranges can use an Excel spreadsheet to build a list of numbers with routing information to initially propagate the SQL table. From there, administrators can use the web console to make changes.

 You can configure Excel to not turn the text into hyperlinks automatically. To do that:

 In Excel go to the Office button, and click on Excel Options . See the screenshot below. In Excel 2010, go to the

File menu, and click on

Options

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 99

 In Excel Options, click on Proofing in the left column. Then, click on the

AutoCorrect Options button.

 In the AutoCorrect Options box, click on the AutoFormat As You Type tab. Then, uncheck the box next to

Internet and network paths with hyperlinks

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Click OK twice to return to Excel.

 Navigate to Program Files\BNS Group\msXfax installation Software and Tools

100

 Open the XLSX example file.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Complete the DDI number column. Make sure you retain this as a text column.

Telstra default is no area code (02). Optus default is to supply the area code.

Check with your telco / IP PBX vendor.

 Supply email addresses and/or UNC paths.

 Column ‘K’ is P for PDF or T for TIFF or B for both.

101

 Save as CSV format.

 Click OK

 Select YES

 Exit Excel

 Select Don’t Save

 Using notepad, open the CSV file.

 You should see the leading 02 preserved.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 102

 Close the CSV file.

 Copy the CSV to the location where you are running SQL management Studio .

Eg: C:\Import\ImportDDI.CSV

 In the Program files\BNS Group\msXfax Installation Software and Tools \ msXfax migration tools folder you will see an example script ImportDDI.DDL

 Open the DDI file using notepad.

 Open the SQL Management console

 Open a new query window

 Copy and paste the bulk import commands. Adjust as needed.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Installation Setup Files

9.1

AWS or Azure licensing

Note: Customers who plan to install msXfax in AWS or Azure MUST contact BNS first.

9.2

FIXED MAC addresses on Virtual machines

Dialogic SR140 requires a static MAC address for licensing purposes. If you can’t assign a static MAC to your VM, contact BNS Group support via the support page of www.bnsgroup.com.au.

9.3

Upgrading an existing software installation

Refer to the build release information in chapter 1 to determine which components have to be upgraded.

 B

EFORE YOU COMMENCE THE UPGRADE YOU WILL NEED TO OBTAIN THE PASSWORD OF

THE SERVICE ACCOUNT USED BY MS

FAX

INT SQL I

NTERFACE

 Take a snap shot of your VM first.

 Close any windows which has Services.msc running

 Open a CMD window (Run as Administrator).

 From the CMD Window run FAXSTOP to stop all fax services

103

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 If the Brooktrout SR140 “Dialogic Brooktrout Runtime Software” has changed take a copy of the files shown below btcall.cfg and callctrl.cfg and place them inc:\savedconfigs

104

 If the Brooktrout SR140 “Dialogic Brooktrout Runtime Software” has changed uninstall it first.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 105

 From the command prompt

 CD to the new msXfaxEnterpriseInstallPackage.MSI

 Install the MSI. This will refresh the software and folders previously installed.

Make sure you install on the same drive letter.

 If the web console needs to be updated run that MSI then copy the web console files and replace the ones in the msXfaxconsole web site folder.

 If the reporting software has been changed run that setup to update the reporting software.

 If the Dialogic Brooktrout Runtime Software has not changed, do not remove it.

 CD to “:\Program Files\BNS Group\msXfax Installation Software and

Tools\msXfax Software”

 Run msXfaxEnterprise_Setup.msi

 Select “Continue with Install”

 If you see this screen click ok.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 If you get this screen press OK

 Run the msXfax dashboard

Software version 8.1 1 March 2016

106

ms X fax Enterprise Cloud Connector 107

 Go to Services

Check msXfax BT RX and TX Services are registered

If this server is a transmit server:

 Go to services and make sure the msXfax BT TX Service is listed.

If this server is a receive server:

 Go to services and make sure the msXfax BT RX Service is listed.

If either or both of the services are not listed follow this workaround:

 Open a CMD Window (Run as Administrator)

 Navigate to the programs folder as shown below

 run the program msXfaxbttx with the –service command.

 Also do the same for the msXfaxbtRX service if required.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 108

Continue to finalise the upgrade.

 Select Properties of the msXfax INT SQL Interface service.

 Assign the service account login account and re-key the password for this service account –ok

 Select Properties of the msXfax DMZ Incoming service

 Assign the service account login account and re-key the password for this service account –ok

 If the Brooktrout software had to be removed because of a newer version:

1. Copy the saved brooktrout config files back into the new C:\Program Files

(x86)\Brooktrout\config folder

2. Run the Brooktrout configuration program

3. Follow the wizard and make sure the correct IP address is selected along with other information.

4. Check all settings are correct.

5. Apply the settings

 Start the Services

 Observe and test

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

9.4

New installation On Premises

The following section describes installing msXfax for use with On-premises and assumes the initial software was placed on the C Drive.

9.4.1

Reboot before running the setup

 Reboot the VM before running the setup.

 Login as your installer account

 Open a CMD window (Run as Administrator).

 CD to “C:\Program Files\BNS Group\msXfax Installation Software and

Tools\msXfax Software”

 Run msXfaxEnterprise_Setup.msi

109

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Software version 8.1 1 March 2016

110

ms X fax Enterprise Cloud Connector 111

Make sure that your Virtual NIC has a fixed MAC address. If you can’t assign a static MAC contact BNS Group support. Select Support from www.bnsgroup.com.au

and submit a question.

If the next screen has detected more than 1 Network Card in your Virtual Machine then you may need to cancel the installation and remove any additional Virtual NICs.

Dialogic SR140 will node lock onto a MAC address .

To determine which adapter has which MAC address:

 Open a Command Prompt

 Enter the command getmac /v

This may help you determine which is the VNIC to bind to.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 112

 Select the VNIC which has the fixed MAC Address.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 113

 Write down the System ID Value or copy to the clipboard.

 Create an email with the subject “License Request”.



For your convenience, we have put the text which can be copied into your email on our web site www.bnsgroup.com.au

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 114

 Copy from the web site page the following text and complete as required:

SYSTEM ID =

Customer Name =

Customer Address =

Customer Primary contact name =

Customer Primary contact phone number =

Customer Primary contact email address =

Channel Partner company name =

Channel Partner address =

Channel Partner account manager name =

Channel Partner account manager phone number =

Channel Partner Installer name =

Channel Partner Installer Email address =

Channel Partner Installer On-site mobile phone =

Purchase order or other reference details for this installation =

 Send your email to [email protected]

A license file will be sent to the installer and the customer via email once verified by

BNS Group licensing.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

9.4.2

Copy the license file received via email onto the C Drive of the VM

 Copy the msXfax.lic file to any location on the C drive

115

 Follow the wizard. Do not check the box if this is a new installation.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 116

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Click Next

117 msXfax can be set up as a transmit only, receive only or transmit/receive fax server.

Depending on which option you choose will determine which services are installed.

If in doubt select Fax Transmit & Receive components because you can configure zero channels to a particular function achieving the desired result.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 118

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Double check that you have a fixed MAC address if installing on a VM.

119

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 120

 Set the values for license renewals and System alerts within your system. Note: only a single email address can be defined here. Create a distribution group email address if multiple people are to be notified.

Supported Fax Domains are the address spaces assigned to SMTP Connectors which route messages to this fax server. The domains DO NOT have to end in

.FAX but it is recommended they do.

Users and applications can address faxes from their email environment using [email protected]

or [email protected]

etc

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 121

 Specify the IP address or DNS name for your on-premises hub transport/smtp server.

 Also specify the default email address for faxes to be sent to in the event that msXfax can’t determine who to send faxes to.

Generally, no credentials are needed to send to on-premise SMTP servers.

There may be a need to add the fax server IP address to a list of servers in

Exchange receive connectors.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 122

 Select the global default option: format of received faxes

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 123

 If you are evaluating the software ensure the transmit and receive circuits are both set to 1.

 Go to your Exchange Server and create a mailbox for this fax server. Read the notes below

9.4.3

Exchange 2013 specific notes from Microsoft.

http://technet.microsoft.com/en-us/library/bb124489(v=exchg.150).aspx

When you install Microsoft Exchange Server 2013, IMAP4 client connectivity isn't enabled. To enable IMAP4 client connectivity, you need to start two IMAP services, the Microsoft Exchange IMAP4 service and the Microsoft Exchange IMAP4 Backend service. When you enable IMAP4, Exchange 2013 accepts unsecured IMAP4 client communications on port 143 and over port 993 using Secure Sockets Layer (SSL).

The Microsoft Exchange IMAP4 service runs on Exchange 2013 computers that are running the Client Access server role. The Microsoft Exchange IMAP4 Backend service runs on the Exchange 2013 computer that’s running the Mailbox server role.

In environments where the Client Access and Mailbox roles are running on the same computer, you manage both services on the same computer.

Note: each fax server requires its own mailbox and AD Account.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 124

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 125

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 126

Important Note

: if your Exchange system does not support UPN based credentials then set the mailbox email address field above to just the account name eg: F3TESTFAX5

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 127

Note:

msXfax setup now installs the pre-requisite software including Dialogic SR140 software.

At any time during the installation if you are offered to do a restart of the VM please ignore it.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 128

Note: Brooktrout software has to be installed on C

Drive. Do not change volume or path name.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 129

Note: At any time during the installation if you are offered to do a restart of the VM please ignore it.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 130

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 131

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 132

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Run the msXfax console AS ADMINISTRATOR on the desktop

133

When you see this screen , proceed to license and configure Brooktrout SR140 software using the Brooktrout License Manager and Brooktrout configuration Tool in chapter 10.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

9.5

New installation Office 365

134

The following section describes installing msXfax for use with Office 365. Installing msXfax for use with On-premises Exchange or other SMTP Servers differs only in the set up screens.

 Close any windows with services.msc running

 Open a CMD window (Run as Administrator).

 CD to “C:\Program Files\BNS Group\msXfax Installation Software and

Tools\msXfax Software”

 Run msXfaxEnterprise_Setup.msi

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 135

Make sure that your Virtual NIC has a fixed MAC address. If you can’t assign a static MAC contact BNS Group support. Select Support from www.bnsgroup.com.au

and submit a question.

If the next screen has detected more than 1 Network Card in your Virtual Machine then you may need to cancel the installation and remove any additional Virtual NICs.

Dialogic SR140 and msXfax node lock onto a MAC address.

To determine which adapter has which MAC address:

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Open a Command Prompt

 Enter the command getmac /v

This may help you determine which is the VNIC to bind to.

136

 Select the VNIC which has a fixed MAC Address.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 137

 Write down the System ID Value or copy to the clipboard.

 Create an email with the subject “License Request”.

 For your convenience, we have put the text which can be copied into your email on our web site www.bnsgroup.com.au

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 138

 Copy from the web site page the following text and complete as required:

SYSTEM ID =

Customer Name =

Customer Address =

Customer Primary contact name =

Customer Primary contact phone number =

Customer Primary contact email address =

Channel Partner company name =

Channel Partner address =

Channel Partner account manager name =

Channel Partner account manager phone number =

Channel Partner Installer name =

Channel Partner Installer Email address =

Channel Partner Installer On-site mobile phone =

Purchase order or other reference details for this installation =

 Send your email to [email protected]

A license file will be sent to the installer and the customer via email once verified by

BNS Group licensing.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

9.5.1

Copy the license file received via email onto the C Drive of the VM

 Copy the msXfax.lic file to a location on the C drive

139

 Follow the wizard

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 140

 Simply press NEXT and do not check the upgrade box.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 141

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 142

 For a customer with only Office 365 or Gmail for Business or other similar cloud based service, select the Cloud Mail Service option. Otherwise, select On-

Premise Mail System.

If you have a complex hybrid mix of on-premises and Hosted cloud email read the section specific to that scenario.

This part of the documentation will assume you have Office 365 only

 Click Next

Before you proceed any further you will need to create an Office 365 mailbox for the fax server.

 Go to your Office 365 Admin Center

 Create a user mailbox

Create a mailbox for each fax server.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 143

If you have multiple fax servers use the Server Name as the Mailbox address eg:msXfax-<ServerName>@yourdomain.com

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 144

 Check that IMAP is Enabled. It should be by default.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 145

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 146

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 147 msXfax can be set up as a transmit only, receive only or transmit/receive fax server.

Depending on which option you choose will determine which services are installed.

If in doubt select Fax Transmit & Receive components

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Double check that you have a fixed MAC address if installing on a VM.

148

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 149

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 150

The User Logon ID for Office 365 is the email address of the mailbox you created earlier.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 151

 Select the global default option: format of received faxes

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 If you are evaluating the software ensure the transmit and receive circuits are both set to 1.

152

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 153 msXfax setup now installs the pre-requisite software including Dialogic SR140 software.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 154

Note: This has to be installed on C Drive. Do not change volume or path name.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 155

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 156

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 157

 Run the msXfax console on the desktop

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 158

When you see this screen, proceed to license and configure Brooktrout SR140 software using the Brooktrout License Manager and Brooktrout configuration Tool in chapter 10.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Brooktrout SR140 Software

159

Select each of these in sequence to license and configure Brooktrout SR140 software. At the end of each step make sure you close the application.

10.1

Adding SR140 evaluation licences

 Select the option “Configure Licensing”.

If you are evaluating msXfax software you can install a 30 day SR140 evaluation licence which activates 2 fax channels.

 Start up the License Activation Wizard by selecting Activate License from the

License menu.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 160

 Select License -> Activate license. msXfax ships with a Demonstration License Key file (.dlk) file to allow you to run a

30 day evaluation of the Brooktrout SR140 software.

 To evaluate msXfax using a 30 day evaluation license, select

Use license key provided with my application

to activate the demonstration license.

 Click Next. The Activation Method dialog box appears:

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 161

 Use the Automatically (connected to the Internet)

10.1.1

Automatically (this computer is connected to the Internet)

Activates licenses automatically to the machine performing the activation. This is the easiest method if your computer is connected to the Internet. If successful, this step completes the product activation process immediately. Your new license files are displayed in the License Manager main window.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 162

 Select Finish

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Installing purchased SR140 licences

11.1

Identifying your SR140 licences

SR140 License keys are supplied in a word document obtained when a purchase was made.

The license key is a 12 digit number.

163

11.2

Uninstall evaluation licenses first

 Run Brooktrout License Manager

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Click ok

 Select License -> Activate license.

Software version 8.1 1 March 2016

164

ms X fax Enterprise Cloud Connector 165

 Select Enter externally provided license key. Click Next.

 Make sure your Windows Server is connected to the Internet

 Choose automatically

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 166

11.2.1

About Using the interactive web method

Activates licenses using the Dialogic License Activation website. After successfully processing activation information, you can choose to download the file immediately or have the license emailed to you. Within a couple of minutes Dialogic sends an email containing a license file, if you select to have the license emailed to you. To complete the activation process, use the License Manager interface to install the license file(s) on the machine specified.

11.2.2

About using the create a request for email or fax

See Activating a License Using Email or Fax on page 46 of the Dialogic Windows

End User Guide supplied with msXfax.

11.3

Activating a License Automatically

This section continues to describe the automatic installation of your SR140 license.

 Select the Add button to enter a purchased License Key for this system.

You can enter more than one License Key. You must enter at least one License Key to proceed, otherwise an Error dialog box appears.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

This License Key is shipped with your order for msXfax.

 The Please enter License Key dialog box appears:

167

 Enter the License Key and Click OK.

 The click next if no further license keys are to be entered.

 The Product Registration window appears:

 Click Next

For your convenience, Product Registration follows activation in the same session using the License Activation Wizard.

 Follow the screen prompts if the Product Registration window appears.

All but one of the registration fields are required (indicated by an asterisk [*]). When required information is not entered, an Error dialog box is displayed. Be sure to enter the information for the person responsible for the day-to-day running of the installation.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 168

 Verify that your computer is connected to the Internet.

 Click Next to begin processing your license request.

The License Manager sends the license request to the Dialogic License Activation

Center, where your license request is processed.

The request process can take a few minutes.

 The Request Status window appears when the automatic activation process is complete. The License Manager provides a Tip when license activation fails. The

Tip usually provides a possible solution or where to get more information that leads to a solution:

License Obtained

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 169

The requested license is automatically installed in your system. The product activation process is complete.

 Click Next

Congratulations, you have successfully installed an SR140 license.

Close the Brooktrout License Manager.

The remainder of this section describes alternative methods to activate your license.

Proceed to the next logical step/section.

Request Failed. Invalid license key.

The following is the tip associated with this failure:

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 170

Tip: The license key you are trying to activate is not valid. Please confirm the license key was entered accurately into the License Activation Wizard.

When a License Key is invalid because of a data-entry error, re-enter the correct license key by running the License Activation Wizard again. If the license key has been entered correctly but the request status is invalid, contact your reseller/distributor. Contact BNS Group only if the SR140 license was procured via

BNS Group’s authorised channel partners.

Request Failed. License already activated.

The following is the tip associated with this failure:

Tip: The license key you are trying to activate has already been activated. You cannot activate the same License Key on different systems. Please refer to your user documentation for details about moving licenses from one system to another or restoring lost licenses.

When you attempt to activate a license key for the second time from the same or another computer, it is considered re-hosting. Refer to BNS Support Article http://www.bnsgroup.com.au/bns-group/helpdesk/knowledgebase.php?article=134

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 171

Request Failed. Cannot communicate with the License Activation Center.

The following is the tip associated with this failure:

Tip: The License Activation Center cannot be reached. Please check your Internet connection, network and firewall settings. Please try again. You can also restart the

License Activation Wizard. Select either the option to use the interactive web method or the option to request a license via email or fax.

The License Activation Center cannot be reached because the License Activation

Center computer is temporarily unavailable or you are experiencing temporary

Internet problems.

Attempt to correct the problem and retry the request. When using the access numbers, if failures persist, contact reseller/distributor or BNS Group.

Request Failed. Internal error code["err #"].

The following is the tip associated with this failure:

Tip: Please try again. You can also restart the License Activation Wizard; select either the option to use the interactive web method or the option to request a license via email or fax.

If failures persist, contact reseller/distributor or BNS Group.

 Click Next.

The final License Activation Wizard window appears indicating which license keys have been activated and which license keys have failed activation.

 Click Finish to complete your activation process.

Because you activated automatically, you do not need to install licenses. Your activation process is finished.

If you successfully activated the SR140 license, proceed to the next Chapter.

11.4

Overriding the Default MAC Address Used for Node

Locking

Note: The follow procedure applies only to automated license activation.

In some cases, when you have multiple MAC addresses in your system, you may want to use a different MAC address other than the default MAC address used for node locking.

Create a file named brktlicmgr.cfg and place it in the same directory as the License Manager (for example,

Brooktrout\Boston\bin

This file should be a text file with a single line

‘NodeID=<enter node id here>’, with no spaces.

To obtain the node ID for the MAC address you intend to use follow the steps below.

 1.Launch the License Manager.

 2.From the Utilities menu, Select Display All Node Ids option.

 3.Select the adapter.

 4.Copy and paste into the

brktlicmgr.cfg

configuration file.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

11.5

Activating a License Using the Web

172

You can also activate your SR140 license on the web using a computer that has web access. This can be a different computer than the server on which you are installing msXfax.

It is critical that you enter the Node Lock information for the intended machine (Node

ID) on the website without errors. The software generates an unusable license when you enter incorrect Node Lock information. The second attempt to obtain the license using the corrected Node Lock information is considered re-hosting. Refer to BNS

Support Article http://www.bnsgroup.com.au/bnsgroup/helpdesk/knowledgebase.php?article=134

Follow the steps below to activate a license using the interactive web method:

 Start up the Brooktrout license manager on the fax server..

 Select Using the interactive web method as your method of activation.

 The following License Activation Wizard window appears:

 Click Save the instructions into a file button.

 The instructions shown in the License Activation Wizard window are saved to a file that you can print or refer to at a later date. The instructions provide the Node

Lock Type and the Node Lock that you enter when activating from the web.

 You can also display the Node ID information by selecting Display Node Lock under the Utilities menu in the License Manager window.

 On a computer that has Internet Access, enter the web address

www.dialogic.com/activation

, which directs you to a secure server. The following screen appears.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 173

 Enter your original SR140 License Key (this can be found on your License information supplied with msXfax) and click Submit. The following screen appears.

 Click Generate Licenses. The following screen appears.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 174

 Select the Product you are activating.

 Select Node ID Type VID.

 Enter the Node ID.

 Click Generate License.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 175

 Verify that the information on this screen is correct and click Confirm. The following screen appears:

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 176

 Click Save to File to save the license file to your computer or click Email to have the License file emailed to you. The following screen appears.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 177

 Follow the instructions

Installing Licenses below.

11.5.1

Installing Licenses delivered via the web method

When you receive a license file from the Dialogic License Activation

Center (via email or saved from the site) use the License Manager application to install the attached license.

If you receive the license file via email, the licensing information is sent to you in the body of the e-mail. You must create a file with a .LIC extension and copy the licensing information from the e-mail into that file. If you save the license file from the

Dialogic web site, you save the file to a temporary location as indicated below.

Note: If you use the automatic activation method, you do not need to install licenses.

Your activation process is finished.

Follow the steps below to install a license:

 Save the license file to a temporary location (for example,

C:\Brooktrout\Boston\bin) on your hard drive.

 Start the License Manager by selecting the following:

 Start > Program Files > Brooktrout > Brooktrout License Manager

The License Manager window appears.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 178

 Select Install previously activated license… from the License menu. The following screen appears:

 Browse to the location of the license file.

 Highlight the filename, then click Open to activate your product.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

11.6

Troubleshooting SR140 licensing problems

179

Page 50 of the Dialogic Windows End User Guide for SR140 provides technical information how to run the License Manager with the /D option. This produces a log file called BrktLicMgr.log.

To obtain a copy of the Dialogic Windows End User Guide version 6.7 go to

C:\Program Files\BNS Group\msXfax Installation Software and Tools\msXfax

Support Tools\SR140 Tools.

Automatic activation must be performed using the License Manager on the system which is to be licensed.

Note: Because the license verifies if the system clock has been set back, you should ensure that the system date is set correctly.

11.6.1

Using the License Manager

The License Manager application is usually installed with your fax application.

To start the License Manager, use one of the following methods:

 Start the License Manager from the Configuration Tool

 Select Start >

Program Files >Brooktrout > Brooktrout License Manager

The License Manager window appears.

This window shows information for any installed licenses. The application tries to determine license integrity and authenticity.

Typical problems when validating licenses:

1. The license can have a broken signature.

2. The license can expire.

3. The license can have the wrong Node ID.

4. System clock can be tampered.

If the license has more than one problem, only the first detected problem is indicated. For example, if the license has expired and has a broken signature, only the broken signature is indicated on the main screen.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 180

11.6.2

Displaying and Copying Node IDs

msXfax requires only 1 Fixed MAC Address on a VM.

If for some reason, you have more than one MAC address on the system you can choose the MAC address (Node ID) to use for licensing locking.

The License Manager allows you to view the Node ID representation of the first 20

Ethernet Adapter MAC addresses available on the system.

You need to use this function in order to node lock to a MAC address in the system other than the default MAC address used for node locking.

Follow the steps below:

 From the Utilities menu, select Display all node IDs. A screen like the following appears.

 Double-click to select the Node ID. Right click and select Copy to copy the Node

ID.

11.6.3

Overriding the default MAC Address used for node locking

Note: The follow procedure applies only to automated license activation.

In some cases, when you have multiple MAC addresses in your system, you may want to use a different MAC address other than the default MAC address used for node locking.



Create a file named brktlicmgr.cfg and place it in the same directory as the

License Manager (for example,

Brooktrout\Boston\bin

This file should be a text file with a single line

‘NodeID=<enter node id here>’, with no spaces.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 181

To obtain the node ID for the MAC address you intend to use follow the steps below.

 Launch the License Manager.

 From the Utilities menu, Select Display All Node Ids option.

 Select the adapter.

 Copy and paste into the

brktlicmgr.cfg

configuration file.

11.6.4

Adding licences and Brooktrout Configuration manager

Note: after adding SR140 licences to an existing system it is important to run the

Brooktrout configuation manager and proceed through the wizard and apply changes/finish. This then updates the system with the correct number of SR140

licenced channels.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Brooktrout Configuration tool

182

 Select Option 2 ‘Configure SIP”.

This runs the Brooktrout Configuration Tool automatically from the setup. If you need to run the Brooktrout Configuration Tool after the setup has completed, it is availabIe as shown below.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 183

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 184

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Software version 8.1 1 March 2016

185

ms X fax Enterprise Cloud Connector 186

Note: If you are evaluating the software only and do not have a SIP Gateway at this stage, set the primary gateway to the IP address of this server (ie: Point to yourself).

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 187

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

12.1.1

Release 6.7.4 specific

Re-run the Brooktrout configuration program in advanced mode.

Set a dummy secondary gateway.

188

12.2

Technical

Contact BNS Group support re advanced settings in the Brooktrout configuration.

Some key points:

 Pcmu is now the default issued by Brooktrout 6.7.3

 For all countries except north America this should be pcma

 If in doubt set this to pcma pcmu so both codecs are supported.

 Running higher than 14.4k bps will require G711 only to be used.

 Subject to the QOS and other factors will depend on what is the suitable configuration and protocols to be used.

12.3

Backup Brooktrout license files

 If you wish to backup and store the license files they can be located in folder

C:\Program Files(x86)\Common Files\Brooktrout.

 Place the copy in your central license management/document store.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

12.4

Outgoing failover fax routing

Customers with multiple outgoing servers may want to implement a failover to a second SBC\SIP Gateway.

In Advanced mode, it is possible to direct all outbound calls via a primary proxy server with failover to a secondary, third and even fourth SBC\Gateway.

There is no difference between a gateway and a proxy in this context.

189

SR140 software will failover to the next sip_proxy_server under one of the 2 conditions:

1) When the SR140 doesn't receive a response from the gateway and a local timeout occurs. The first entry will be used for all calls made by SR140, up to the moment that this first IP address is not responding anymore. msXfax will retry the call and SR140 will use the second entry. On the next call, SR140 will continue using the second entry, until it stops responding. SR140 will not monitor the device at the first entry; SR140 will stay on the sip_proxy_server from which it got last a response.

The SR140 receiving a 5xx (server error) or 6xx (global failure) message from the gateway will not cause a failover because the gateway is still running.

2) When SIP Session Refresh is enabled and the SR140 doesn't receive a 422 message.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Start msXfax Services

DO NOT START ALL SERVICES YET!

Note: If your installation DOES NOT have SQL or SQL Express - disable the msXfax

INT SQL Interface service.

13.1

Check msXfax BT RX and TX Services are registered

If you selected this server as a transmit server:

 Go to services and make sure the msXfax BT TX Service is listed.

If you selected this server as a receive server:

 Go to services and make sure the msXfax BT RX Service is listed.

If either or both of the services are not listed follow this workaround:

 Open a CMD Window (Run as Administrator)

 Navigate to the programs folder as shown below

 run the program msXfaxbttx with the –service command.

Software version 8.1 1 March 2016

190

ms X fax Enterprise Cloud Connector 191

 Also do the same for the msXfaxbtRX service if required.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

13.1.1

For SQL installations

 Set the Log On account for msXfax INT SQL Interface as shown below.

 Use the same AD\mailbox account set up earlier.

192

Note: Type the password

The account will be given Logon as a Service permission automatically.

 Set the service to startup type ‘Automatic (Delayed Start)

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 193

 Now select option 3 to Start all Services.

 The dashboard should now show all green ticks for installed components except if SQL is being used.

Note: it may take a minute or so for the green tick to appear in the FAX Services panel.

If the IMAP Connection does not come up green it is probably because of the login credential format being incorrect. Some Exchange servers require the email address format and others require just the account name.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 194

 Click on the tool icon in the SQL Connection panel.

 Supply the connection name to your SQL Server \ Instance.

 Apply changes



From Service Control Manager, restart the msXfax INT SQL Interface service

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 195

msXfax Licensing - obtaining a license file

Customers who ran an evaluation for a period of time can activate msXfax using a license file.

 To obtain the System-ID run the program ‘CheckLicense.exe’ which is located in

Program files\BNS Group\msXfax Enterprise\Programs

 Write down the System ID Value or select and copy to the clipboard.

 Create an email with the subject “License Request”.

 For your convenience, we have put the text which can be copied into your email on our web site www.bnsgroup.com.au

 Copy from the web site page the following text and complete as required:

SYSTEM ID =

Customer Name =

Customer Address =

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 196

Customer Primary contact name =

Customer Primary contact phone number =

Customer Primary contact email address =

Channel Partner company name =

Channel Partner address =

Channel Partner account manager name =

Channel Partner account manager phone number =

Channel Partner Installer name =

Channel Partner Installer Email address =

Channel Partner Installer On-site mobile phone =

Purchase order or other reference details for this installation =

 Send your email to [email protected]

A license file will be sent to the installer and the customer via email once verified by

BNS Group licensing.

 When a new license file is sent to you, simply replace the existing license file as shown below.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

197

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Configuration

15.1

Support tool Teamviewer

The version of Teamviewer which BNS supports can be downloaded from the link below, enter “Teamviewer” into the field ‘Ask a Question’.

This is the Quick Support Teamviewer software which does not need to be installed you simply download it, unzip and run the EXE. http://www.bnsgroup.com.au/bns-group/Support.aspx?a=30&s=50&c=58

198

15.2

Configuring msXfax

Most configuration information can be set via the dashboard. Advanced settings can be performed directly in the msXfaxboot.ini file.

The dashboard is very simple to use. Hover the mouse over the icons to see more information.

Using the dashboard you can access:



Logs



Set thresholds



Configure basic settings



Monitor fax lines and send a test fax.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 199

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

15.3

Email to your host configuration

200

For a pure Office 365 environment your settings will look very similar to the above.

Fields inside the yellow box are reserved for On-Premises SMTP/Exchange servers.

For Office 365 you only need to specify the values outside the yellow box.

15.4

Protective marking and other msXfaxboot.ini edits

 Open msxfaxboot.ini (Notepad)

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 201

Provide the URL strings for Agency fax policies, Internal support and helpdesk plus

URL’s for user classification usage and guidelines. Error messages sent back to users will include these links to help them determine why the fax gateway rejected their message.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 202

15.5

Turn on Dyanmic Routing if required

Note: If you intend to use Dynamic routing to distribution groups or Email aliases based on the direct dial inwards number edit the msXfaxboot.ini section as follows

DMZ-Inbound-UseDynamicRouting-Int=1 msXfax will check the local routing table first and will only perform a dynamic route if it does not find anything in the local Route Table.

If Dynamic routing is turned off (=0) and local Route table is on (=1) and no local entry is found then the fax will be routed to the default inbound route.

15.5.1

Maximum allowed SMTP within your Email network

 Default for on-premises Exchange is 9MB. Change this to be 3MB under your internal Transport / SMTP Connector limits.

 Specify the SMTP size limit which your system allows through firewalls and message transports and mailbox policies on your email system. If it is 30MB for example then specify a number slightly lower eg: 28.

Note: Office 365 limit is 25MB. msXfax sets a limit to 20MB so it is well under the limit. Incoming faxes are split into multiple parts to accommodate these limits.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

15.6

How to stop and start the services

 To start services run FAXSTART or FAXSTOP.

Note: subject to your UAC settings, you may need to elevate the command prompt so you have specific permissions to stop and start services.

203

Software version 8.1 1 March 2016

204 ms X fax Enterprise Cloud Connector

Dynamic Routing to Exchange Distribution Groups

msXfax offers inbound fax routing based on Direct Dial Inwards (DDI) values presented from the telephony network.

Dynamic Routing features of msXfax are easy to implement in: On-Premises

Exchange, Office365 or any other email system which supports Distribution

Groups/Lists.

You may want to do this later once you test the basic functionality of inbound routing which will route all inbound messages to the default email address you specified during installation.

Dynamic routing is designed to work with Distribution Lists/Groups of any email system.

The following examples shows how to create a distribution group in MS Exchange for routing an incoming fax to one or more users/applications.

16.1

How does msXfax build the email address to send to the group?

Before you create a distribution group in Microsoft Exchange you first need to know the DDI value and the prefix to be used for email address construction to send to the group.

Edit msXfaxboot.ini in the :\Program Files\BNS Group\msXfax\Programs folder.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 205

 Edit these values as indicated

Customers who require some local table routing and dynamic routing can do so.

The order of priority is the local table is checked first for any valid route.

If no route is found in the local table, a dynamic route will be taken.

Note: Customers using dynamic routing must make sure that the entire DDI range has a corresponding list of distribution groups/email aliases set up in their Email network.

 Save the changes to msXfaxboot.ini

 Open a CMD window.

 Run FAXSTOP

 Run FAXSTART

With dyanamic routing turned on, msXfax on receipt of a DDI value such as

62033724 will:

1. Check the ‘InboundRouteTable.txt” located in :\Program Files\BNS

Group\msXfax\Programs folder and if a DDI value of 62033724 has been defined then msXfax will route to the specific email address(es) in that file.

2. If no entry exists in the InboundRouteTable.txt and Dynamic Routing is enabled, msXfax will construct a message containing the fax to:

[email protected]

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 206

The file attachment will be a TIF or PDF. If both was selected as the default then the user(s) will receive 2 emails one containing the TIF and the other a

PDF.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

16.2

Create the Distribution Group

If you have many DDI values in your inbound fax number ranges, msXfax has a utility program which will generate Powershell scripts for those Exchange Admins who are familiar with Powershell. Contact BNS Group technical support for more information.

To create a Distribution Group manually follow these instructions.

 Run Exchange Management Console in your Exchange network

Example for Exchange 2010.

207

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 208

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 209

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 210

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 211

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 212

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 213

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Inbound fax routing using Office 365

17.1

Office 365 Exchange Admin Center

214

 Select Groups in the Recipients section

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 215

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector



Press Save to save the Group

216

 Your Group should now now appear in the list

 Click on the Pencil icon to the right to add members of the group.

 Select properties of the group to review your security requirements for example:

Congratulations you can now manage all inbound fax routing from within Office 365 environment by creating groups for all inbound numbers.

Remember to check other security options available in Office 365.

Remember that SMTP Email contacts of external recipients in the distribution group can be created and add to receive faxes via your fax server.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

For experienced Exchange Administrators

Remote Powershell will be useful when dealing with many hundreds of inbound number ranges. Refer to Microsoft documentation such as http://technet.microsoft.com/en-us/library/jj200677(v=exchg.150).aspx

Do not contact BNS Group, contact Microsoft for more information on remote powershell and how it works.

217

17.2

Activate Dynamic Routing msXfaxboot.ini

 Edit msXfaxboot.ini via the dashboard or directly from programs folder.

 Set the values replacing the domain name with your Office 365 domain name

DMZ-Inbound-UseDynamicRouting-int=1

DMZ-Inbound-UseDynamicRoutingPrefix-str=FAX

DMZ-Inbound-UseDynamicRoutingDomain-str=xxxxxx.onmicrosoft.com

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 218

Gmail for business Fax Server mailbox

msXfax support for direct processing from a Gmail Business account.

This provides a simple to use outbound/Inbound fax processing service using your own on-premises fax server.

A Gmail user account is required for the fax server with special restrictions on the mailbox so that only your users can send fax requests to the fax server.

SSL & TLS encryption is used to protect all fax messages which are sent to and from

Gmail.

18.1

Set up the Fax mailbox in Gmail for Business

Simply create a Gmail account under your Gmail Admin Console.

Give the account a name such as Fax Sydney, Fax Los Angeles etc.

18.2

Restrict use of the fax server to your internal users

https://support.google.com/a/answer/2640542?hl=en

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Testing the fax server

19.1

Check that services start correctly

219

 If any of the services do not start the next section “check log files” may help determine why the service could not start.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

19.2

Check log files

220

19.3

Check the Audicodes message log

 Open a web browser to the IP address of the AudioCodes gateway

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Login



Software version 8.1 1 March 2016

221

ms X fax Enterprise Cloud Connector 222

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

19.1

Send a test fax from Outlook using Office 365

223

Sending a fax using Office 365 web interface (as shown above) or Outlook desktops or other email clients such as Apple IPAD/MacBooks, the procedure is the same. msXfax freeform addressing is simple:



Send to the Fax Mailbox eg: Fax Sydney



Attach supported: MS Office, PDF or TIF files



In the first line of the memo put the recipient name followed by FAX=<faxNo>



Then press send.



Note: you can enter multiple recipients one per line.

Test from Outlook and other clients using the same freeform addressing method.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

19.2

Send a test fax from Outlook for On-Premises

Exchange

224

To send a fax using msXfax is as easy as sending an email with a few simple rules.



Your memo will appear as page 1 of the fax.

 msXax Lite supports only PDF attachments.



Include the recipient’s name in the top part of the memo so it appears on page

1 of your fax to them.

 Send the message

 A confirmation will be sent back to your inbox from msXfax when it receives the message for processing.

 A fax sent or fax failed message will also be sent back to your inbox.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

19.3

Sending a test fax from the dashboard

225

Note: if you want to send 3 faxes to this fax number enter 3 in the Iteration field. Be careful.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

19.4

SMTPFAST utility

226

This is a test tool only. It is used for diagnostic purposes. It is not supported and has known limitations.

 From the All Programs group locate the utility SMTP Client

You can send SMTP messages to Office 365, Exchange On-premises, Gmail or other SMTP Servers. This is a useful tool to perform end to end testing.



Creates a fax request just as though the user had performed this from their

Outlook or other email client.



Allows you to add attachments.



Allows you to include a memo to insert into the cover page and specify the

Freeform Fax address.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

SMTP Host: Office 365: SMTP.OFFICE365.COM

Exchange On-premises: DNS or IP Address

PORT: 587 (TLS)

User Name: This is the email address of the user making the request.

Password: The user’s password to log into Office 365

Use TLS: Office 365 must be checked

Exchange On-Premises usually not and used with port 25

Message Details

From:

To:

Must be the same email address of the user making the request.

The email address of the fax server

Subject: Your subject value

Attachments: Attach or clear any attachments

Message:

Iterations:

This is the memo field which must have Freeform fax addressing.

Recipient Name FAX=destination fax number

You can have multiple lines of fax addresses.

How many of these fax requests are to be sent? Take Care!

227

 Press Send.



You should see a log message as shown above.

This can be used for submissions via Office 365, back down to the fax server, watch the fax progress through the various stages of Cloud connection, Conversion, Fax

Transmission and Confirmation processing.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

19.5

Receiving faxes

228

Users in any email client can receive faxes in either TIF or PDF or both PDF and TIF formats.

Example below Outlook Web App on Office 365.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Cover sheets

20.1

Default cover sheet

A sample template word document Default.docx is installed by default.

229

 Provide a copy of this document to the administrator of the system. They can insert their logos and change the basic text disclaimer information etc.

 The default.docx can then be replaced and tested.

Additional Information is documented in the administration guide.

Domain based cover sheets are called xxxxxxxx.docx where the leftmost string of the sender’s email address is used for example:

Sender domain of @GIO.COM.AU would use a word cover sheet of GIO.DOCX. msXfax looks in the above folder for the cover sheet DOCX.

20.2

Boot.ini settings and overview

1. By Default at install a default cover page is set and activated by use of keywords, the default coverpage name can be changed but must reside in the coverpage subdirectory.

2. In situations where the body text is to be suppressed and only attachments are to be processed ie when a user creates their own coversheet is word and wants that and some attachments to be faxed in sequence then set this keyword to 1.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 230

3. In situations where Sender Domain Coversheet support is required, that is the sender of a fax whose email is [email protected]

, a coversheet called sales.docx will be searched for in the msXfax cover page directory. The keyword must be set to 1 for this functionality to be activated.

4. In situations where Destination Domain Coversheet support is required, that is domain addressing is used and say a fax is sent to [email protected]

then a coversheet called accounts.docx will be searched for in the msXfax cover page directory. The keyword must be set to 1 for this functionality to be activated.

5. In situations where a user supplied coversheet is required then the user must specify a coversheet keyword in the body of the email followed by the coversheet name such as CS#admin. The

‘admin.docx’ coversheet must exist in the msXfax cover page directory. The keyword must be set to 1 for this functionality to be activated.

The order in which Cover Sheet processing is actioned is as follows :

1. User specified Cover Sheet via keyword

2. Sender Domain Coversheet

20.3

User Specified Coversheet keyword/value pairs

It is possible for users to supply their own keyword/value pairs in the email body that are then used during cover sheet processing. The keywords correspond to merge fields that are specified in a coversheet. There merge fields are replaced with the corresponding values. The result is a customised coversheet. All keyword/value pairs are stripped from the email body and only the remaining text is inserted into the coversheet. The coversheet is created using MS Word.

The keywords are divided into sender ‘/S-name’ and recipient ‘R-name’ information e.g.. /S-MobileNo=041212345678 and /R-AccountNo=0024312 are placed in the message body of the requesting email. Use the insert merge field facility in MS-Word to insert the merge fields ‘S-MobileNo’ and ‘R-AccountNo’ into the coversheet. Place the coversheet in the the msXfax cover page directory.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 231

Software version 8.1 1 March 2016

232 ms X fax Enterprise Cloud Connector

Troubleshooting

21.1

Rehosting your SR140 license

Dialogic® Brooktrout® SR140 Fax Software (SR140) licenses are tied to the system node ID (also called 'node lock') which is based on the host machine's MAC address.

If this address changes for any reason, the license will become invalid and you will see a 'wrong host' error in the License Manager. http://www.dialogic.com/support/helpweb/helpweb.aspx/2852/how_to_ re_host_an_sr140_license/sr140

21.2

SR140 Node type

msXfax uses Dialogic Brooktrout SR140 SDK. Therefore the Node ID is VID which requires only the MAC address to be fixed. You can change the computer name without affecting your SR140 license. http://www.bnsgroup.com.au/bnsgroup/helpdesk/admin/manage_knowledgebase.php?a=edit_article&id=135

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 233

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Optional: msXfax Web console

22.1

General

Pre-requisite is SQL Server or SQL Express (any version from 2008 to 2014+) msXfax Webconsole should be installed on one or more of the fax servers.

 Windows 2012R2 Server which has IIS 8 with .Net4 framework installed.

234

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 235

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

22.1.1

SQL Database Administrator (DBA)

 Your SQL DBA will need to create a SQL User account for the Webconsole to connect to the database.

 msxfax-connection is the SQL user name used throughout this documentation.

 Run the SQL management studio.

 Navigate to SECURITY. Expand the folder.

 Right click on Logins

 Create a new login as shown below

236

 Select User Mapping

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 237

22.1.2

Active Directory Security Groups

In this section you will create an AD Security Groups.

 Create an Active Directory Security Group for the infrastructure administrators eg:

‘msxfax-admin-group’.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 238

NOTE : Add your AD domain user account to that group and also the domain account you are currently using to perform the installation of this software.

 Create an Active Directory Security Group for the operations team eg: ‘msxfaxoperations-group’. This is for future use only but it must exist.

22.2

Installation of IIS for the WebConsole

If you are deploying many FAX Servers in your network you only need to install IIS and the web console on say 2 FAX Servers (1 in production and 1 in DR).

22.2.1

Install Internet Information Server

Microsoft’s Internet Information Server is required to support msXfax Web Console.

This documentation describes the steps required to install IIS.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 239

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

22.2.2

Installing IIS on Windows Server 2012 R2

 Installing IIS8 on Windows 2012 R2

240

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 241

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 242

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 243

Note: do not uncheck .Net 3.5 if it has already been selected.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 244

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 245

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 246

 Select NEXT when you have checked all of the above options

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 247

 Select Install

To check that IIS installed correctly open a web browser from your fax server and proceed to the following address:

 http://localhost

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

You should see the default IIS webpage for example:

248

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

22.3

Install the Web console

249

The web console can be installed on one or more fax servers.

Navigate to program files\BNS Group\msXfax Installation Software and Tools.

 Open a CMD (Run as Administrator)

 CD to \Program Files\BNS Group\msXfax Installation Software and Tools\msXfax

WebConsole IIS Components

 Run msXfaxWebConsole_Setup.MSI

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 250

 Install and Finish

The folder msXfax WebConsole IIS Components contains the files for the web site.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 251

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

22.4

Configure IIS 8 on Windows 2012R2

22.4.1

Create folder for msXfax console web site

252

 Copy all of the web site files and sub folders from msXfaxWebConsole IIS

Components folder into the msfaxconsole folder.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 253

22.4.2

Configure IIS

 From the Start screen select Administrative tools

 Run Internet Information Services (IIS) Manager.

 From IIS remove the default web site

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 254

 From IIS create a web site

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 255

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 256

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 257

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 258

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 259

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 260

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 From IIS, restart the web site

261

22.5

Configure settings and test webconsole connection

 Run Internet Explorer from the fax server and enter http://localhost

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 262

 Select the option to configure the console.

The System Setup page will be displayed allowing you to supply your SQL

Server\instance name along with other key configuration options.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 263

 Save the configuration.

 Note – confirm the configuration has been saved.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

22.5.1

Test the connection to SQL

264

 Select test connection

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 265

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

22.6

Configure sender domains

266



The CSID can be the published fax number of the customer or other values depending on the way this system is being used. Eg: For a service provider, it may simply say “Fax Server”. For a small business it may be their general fax number eg: “+61212345678”

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

22.6.1

Destination domains

HIS IS MANDATORY

–

FOR EVERY DOMAIN SPACE YOU INTEND TO SET UP FOR USERS TO

SEND TO THEY MUST BE LISTED HERE

When users send to [email protected]

or [email protected]

etc those domain spaces must be specified below.

267

22.6.2

Inbound Direct Dial Inwards controls

Most enterprise customers will use dynamic routing in most instances not requiring specific entries in this table.

Customers who require folder based routing will generally use this table.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 268

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Reporting Software

23.1

User permissions SQL Server

Read access to both databases is required for Windows accounts that runs the

Reporting software.

269

Note:

23.2

Configure ODBC on one FAX server to msXfax-

Provisioning database

msXfax reporting is recommended to be installed on one msXfax server only in test and one in production.

To install and configure the reporting software you MUST be logged on to the FAX Server as the installer account which was provided full permissions to the SQL databases.

Note: use the 32 bit ODBC admin tool found in Windows 2012 R2 Control panel.

 Open ODBC 32bit admin tool from control panel.

 Select System DSN

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Select Add

 Scroll to the bottom, highlight SQL Server

 Select Finish

270

 The name of the Data Source as shown above MUST BE msXfax-Provisioning.

 Enter a meaningful description for your environment

 Select the SQL Server or instance from the drop down list

 Select Next.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 271

 Select Next



Select the name of the msXfax-Provisioning Database which your DBA created. It may be called something different to the default naming convention shown above.

 Select Next

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Select Finish

 Select Test Data Source

 If you can’t connect please contact your SQL DBA.

Software version 8.1 1 March 2016

272

ms X fax Enterprise Cloud Connector

 Select OK.

23.3

Configure ODBC on the same Fax server to msXfax-

Transactions Database

 Repeat the same procedure for msXfax-Transactions

273



Select Add

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 274

 Scroll to the bottom, highlight SQL Server



Select Finish

 The name of the Data Source as shown above MUST BE msXfax-Transactions.

 Select the SQL Server or instance from the drop down list



Select Next.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 275

 Select Next

 Select the name of the msXfax-Transactions database which your DBA created.

It may be called something different to the default naming convention shown above.

 Select Next

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Select Finish

 Select Test Data Source

 If you can’t connect please contact your SQL DBA.

Software version 8.1 1 March 2016

276

ms X fax Enterprise Cloud Connector 277

 Select OK.

23.4

Install msXfax reporting software

 This software should ONLY be installed on 1 of the Fax Servers in your test and 1 in your production network.

 Locate the msXfax Reporting folder.

 Open the folder

 Right click SETUP.EXE ‘Run As Administrator’

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 278

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 279

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 280

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 281

 After installation is completed, complete the next set of details.

 Change the drive letter if required but retain the folder structure name

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 282

 Choose an appropriate email address as the sender. This could be your messaging team mailbox for example.



Select TEST and make sure you got the test email before proceeding.

OTE

IF YOUR FIREWALLS DO NOT ALLOW HTTP FROM SERVERS DO NOT ATTEMPT TO

ACTIVATE THE SOFTWARE ON THE NEXT SCREEN

JUST HIT

OK.

CTIVATION CAN

OCCUR OFFLINE BY CONTACTING

BNS G

ROUP TECHNICAL SUPPORT VIA THE WEB

TICKETING SYSTEM

 Contact your reseller for the serial number for msXfax reports.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 283

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

 Close the License manager window

 Login with admin default password is admin

284

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 285

 A number of example reports, charts and dashboards are included in a ZIP file supplied in the msXfax reporting folder

Location of the ZIP file is :\Program Files\BNS Group\msXfax Installation Software and Tools\msXfax Reporting

 Unzip the reports ZIP file

 Import them into the report generator.

Note you can select all at once as shown below.

The reporting sub system allows you to generate scheduled and Ad hoc reports.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 286

23.5

Offline activation & Renewal of licences

Customers without Internet connections will have to contact BNS and provide serial numbers and registration details.

 From the report generator select Help from the menu bar

 Select ‘About msXfax Reports’

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 287

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 288

 BNS will provide an activation code within 48 hours.

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 289

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Powershell utility for Distribution Groups

24.1

Powershell generator for Exchange Distribution groups

This utility is installed on the server under msXfax Support Tools.

290

This utility allows you to generate a powershell script for use when dynamic routing to Exchange distribution groups is required.

Benefits of using Exchange distribution groups are that all fax routing can be done within the Exchange management console.

Administrators can still use the web console to create a specific route for a specific

DDI which will override a dynamic route.

 Run the MSI

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 291

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 292

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

24.1.1

Run the utility

293

This example shows a customer with 100 numbers assigned to their ISDN connection

Number range from 99720100 to 99720199

Telstra generally do not provide the area code. Check with your provider to see what they provide.

Note: Any leading zeroes or area codes are to be placed in the Prefix for Distribution

Group email address field eg: FAX02

Fields explained

Email Domain Name of your Exchange Server

This is the primary SMTP domain name eg: F2Company.com

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 294

Initial member of all groups (eg: Domain\Useraccount)

To ensure that faxes are routed to someone after the distribution group has been created, this person will be the initial member. Once your groups are created, you can use the Exchange Management Console / Exchange Admin Center to add the correct user or other Exchange objects to the group.

Managed by Admin(eg: Domain\Useraccount)

This shows in the Distribution Group property in Exchange so that other administrators know who is managing this group.

msXfax from Email address #1 thru #4

msXfax sends SMTP messages using a specific email address such as msXfax-

[email protected]

if you have multiple fax servers, specify all of the email addresses used by those servers.

Start of inbound number range (eg: 99721000)

This starting number can’t have leading zeroes. Any leading zeroes are to be placed in the Prefix for Distribution Group email address field eg: FAX02

End of inbound number range (eg: 99721999)

This starting number can’t have leading zeroes. Any leading zeroes are to be placed in the Prefix for Distribution Group email address field eg: FAX02

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 295

24.2

Run the Powershell script for Exchange

 From your Microsoft Exchange Server login with permissions to run a powershell script which will add distribution groups

 Run Exchange Management Shell



 Run the script

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector 296

If there is a need to add more email addresses to the distribution groups this is how it can be done. set-distributiongroup -Identity FAX99720100 -emailaddresses

@{add='[email protected]'} set-distributiongroup -Identity FAX99720101 -emailaddresses

@{add='[email protected]'}

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Uninstalling msXfax

 Uninstalling msXfax is performed via Control panel.

 When uninstalling, select the option ‘Do not close applications”.

297

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

25.1

Uninstalling Brooktrout SR140 licenses

 Before you uninstall the SR140 Dialogic Brooktrout Runtime software, take a copy of the folder C:\Program Files(x86)\Common Files\Brooktrout.

 Place the copy in your central license management/document store.

298

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Country Name

Afghanistan

Albania

Algeria

American Samoa

Andorra

Angola

Anguilla

Antarctica

Antigua

Argentina

Armenia

Aruba

Ascension

Australia

Australian External Territories

Austria

Azerbaijan

Bahamas

Bahrain

Bangladesh

Barbados

Barbuda

Belarus

Belgium

Belize

Benin

Bermuda

Bhutan

Bolivia

Bosnia & Herzegovina

Botswana

Brazil

International dialling codes

IDD International Prefix

00**

011

0011 (Voice calls)

0015 (Fax calls - Telstra)

0018 (Telstra special rates)

0019 (Fax calls - Singtel Optus)

011

8**10

( written as 8~10)

011

0010

(ENTEL)

0011

(AES COMMUNICATIONS BOLIVIA)

0012

(TELEDATA)

0013

(BOLIVIATEL)

0014 (Brasil Telecom)

0015 (Telefonica)

0021 (Embratel)

Software version 8.1 1 March 2016

299

ms X fax Enterprise Cloud Connector

British Virgin Islands

Brunei Darussalam

Bulgaria

Burkina Faso

Burundi

Cambodia

Cameroon

Canada

Cape Verde Islands

Cayman Islands

Central African Republic

Chad

Chatham Island (New Zealand)

Chile

China (PRC)

Christmas Island

Cocos-Keeling Islands

Colombia

Comoros

Congo

Congo, Dem. Rep. of (former Zaire)

Cook Islands

Costa Rica

Côte d'Ivoire (Ivory Coast)

Croatia

Cuba

Cuba (Guantanamo Bay)

Cura

ç

Cyprus

Czech Republic

Denmark

Diego Garcia

Djibouti

Dominica

Dominican Republic

East Timor

Easter Island

Ecuador

Egypt

El Salvador

0023 (Intelig)

0031 (Telemar)

011

001

011

0011 (Telstra)

0011

119

95200 (Discount carrier)

011

144+00 Telefonica

Software version 8.1 1 March 2016

300

ms X fax Enterprise Cloud Connector

Ellipso (Mobile Satellite service)

EMSAT (Mobile Satellite service)

Equatorial Guinea

Eritrea

Estonia

Ethiopia

Falkland Islands (Malvinas)

Faroe Islands

Fiji Islands

Finland

France

French Antilles

French Guiana

French Polynesia

Gabonese Republic

Gambia

Georgia

Germany

Ghana

Gibraltar

Global Mobile Satellite System (GMSS)

Globalstar (Mobile Satellite Service)

Greece

Greenland

Grenada

Guadeloupe

Guam

Guantanamo Bay

Guatemala

Guinea-Bissau

Guinea

Guyana

Haiti

Honduras

Hong Kong

Hungary

ICO Global (Mobile Satellite Service)

011

130+00 Telefonica

147-00 Telgua

001

001-- PCCW

0080 -- Hutchison

009 -- New World

00, 990, 994, 999

00 (France Telecom)

40 (TELE 2),

50 (OMNICOM)

70 (LE 7 CEGETEL),

90 (9 TELECOM)

8**10

(written as 8~10)

Software version 8.1 1 March 2016

301

ms X fax Enterprise Cloud Connector

Iceland

India

Indonesia

Inmarsat (Atlantic Ocean - East)

Inmarsat (Atlantic Ocean - West)

Inmarsat (Indian Ocean)

Inmarsat (Pacific Ocean)

Inmarsat SNAC

Note: Inmarsat plans to shift all other codes to this

Single Network Access Code by 2009.

International Freephone Service

International Shared Cost Service (ISCS)

Iran

Iraq

Ireland

001,007

017 Voice Over Internet (VOIP)

N/A

048 to Northern Ireland

(this special arrangement is much cheaper than dialing through the UK using country code 44)

Iridium (Mobile Satellite service) 00

Israel

Italy

Jamaica

Japan

Jordan

Kazakhstan

Kenya

Kiribati

Korea (North)

00 (default selected carrier, not available from public phones);

012 (Golden Lines); 013 (Barak LTD); or 014

(Bezeq LTD)

011

001 (KDD)

010 (MYLINE/MYLINE PLUS)

0061 (Cable & Wireless IDC)

0041 (Japan Telecom)

8**10

( written as 8~10)

000

006 to Uganda

007 to Tanzania

Korea (South)

001, 002

00700

(Speed/ SKTelecom mobiles)

00 Kuwait

Kyrgyz Republic

Laos

Latvia

Lebanon

(

To dial Syria From Lebanon, you may use "02-xx-number", where xx is the area code in Syria.)

00 Lesotho

Liberia

Libya

302

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Liechtenstein

Lithuania

Luxembourg

Macao

Macedonia (Former Yugoslav Rep of.)

Madagascar

Malawi

Malaysia

Maldives

Mali Republic

Malta

Marshall Islands

Martinique

Mauritania

Mauritius

Mayotte Island

Mexico

Micronesia, (Federal States of)

Midway Island

Moldova

Monaco

Mongolia

Montenegro

Montserrat

Morocco

Mozambique

Myanmar

Namibia

Nauru

Nepal

Netherlands

Netherlands Antilles

Nevis

New Caledonia

New Zealand

Nicaragua

Niger

Nigeria

Niue

Norfolk Island

Northern Marianas Islands

(Saipan, Rota, & Tinian)

Norway

Software version 8.1 1 March 2016

011

00**

011

009

020

011

001

011

303

ms X fax Enterprise Cloud Connector

Oman

Pakistan

Palau

Palestinian Settlements

Panama

Papua New Guinea

Paraguay

Peru

Philippines

Poland

Portugal

Puerto Rico

Qatar

Réunion Island

Romania

Russia

Rwandese Republic

St. Helena

St. Kitts/Nevis

St. Lucia

St. Pierre & Miquelon

St. Vincent & Grenadines

Samoa

San Marino

São Tomé and Principe

Saudi Arabia

Senegal

Serbia

Seychelles Republic

Sierra Leone

Singapore

Slovak Republic

Slovenia

Solomon Islands

011

00 Cable & Wireless

088+00 Telecarrier

055+00 Clarocom

002

0**0

882 Rubicon/BT "GeoVerse"

011

022 to Moldova

(this special arrangement is much cheaper than dialing through Moldova using country code 373)

8**10

( may be changing to 00)

011

001 - Singtel IDD

002 - MobileOne IDD

008 - Starhub IDD

012 - Singtel FaxPlus (Fax over IP)

013 - Singtel BudgetCall

(Voice recommended only/Fax possible)

018 - Starhub I-Call

(Voice over IP)

019 - Singtel V019

(Voice over IP)

Software version 8.1 1 March 2016

304

ms X fax Enterprise Cloud Connector

Somali Democratic Republic

South Africa

Spain

Sri Lanka

Sudan

Suriname

Swaziland

Sweden

Taiwan

Tajikistan

Tanzania

Switzerland

Syria

Thailand

Thuraya (Mobile Satellite service)

Timor Leste

Togolese Republic

Tokelau

Tonga Islands

Trinidad & Tobago

Tunisia

Turkey

Turkmenistan

Turks and Caicos Islands

Tuvalu

Uganda

Ukraine

United Arab Emirates

United Kingdom

United States of America

US Virgin Islands

Universal Personal Telecommunications (UPT)

Uruguay

Uzbekistan

Vanuatu

Vatican City

Venezuela

(

To dial Lebanon from Syria, you may also use ""06-xx-number"", where xx is the area code in Lebanon.)

002

8**10

(written as 8~10)

000

000, 005 to Kenya

006 to Uganda

001

(to call Malaysia, Cambodia, Laos and Myanmar from

Thailand, dial 007-60 +Area Code)

008, 009 Voice Over Internet (VOIP)

011

8**10

( written as 8~10)

011

000

000, 005 to Kenya

007 to Tanzania

8**10

( written as 8~10)

00 (including ISDN)

011

8**10

(written as 8~10)

305

Software version 8.1 1 March 2016

ms X fax Enterprise Cloud Connector

Vietnam

Wake Island

Wallis and Futuna Islands

Yemen

Zambia

Zanzibar

Zimbabwe

19**

000

306

Software version 8.1 1 March 2016

Hello! I am an AI chatbot specifically trained to assist you with the BNS DMG2060V34 Dialogic DMG2060V34 Installers Guide. I have thoroughly reviewed the document and can help you locate the exact information you need or explain the content in clear and simple terms. Whether you’re looking for guidance on specific features, troubleshooting steps, or general usage, feel free to ask your questions. The more details you provide about your concerns or needs, the more accurately and effectively I can assist you!

Show related prompts

Assistant typing

Assistant terminated

Key features

Secure and compliant fax communication
Direct connection to SIP Trunk service providers' fax networks
Real-time fax over secure IP networks
Scalable virtual machine deployment
Supports Office 365, Gmail for business, and other email services
Dynamic inbound routing to email distribution groups
Supports email protective marking compliance checks
Comes with a web console for management and reporting

Frequently asked questions

The SR140 can be installed in a virtual machine running Windows 2012 R2 in environments such as Amazon Web Services (AWS) and Azure, or on a customer's own VM platform.

The SR140 supports Office 365, Gmail for business, and other email services using encrypted protocols.

The SR140 supports dynamic inbound routing to email distribution groups, making it easy to manage inbound fax routing.

Installers Guide

SR140 edition

Installation guide

Table of Contents

1

Software notice / latest revisions

2

Introduction 16

12

3

Work sheets

23

4

Telephony configuration guides for msXfax

39

5

How to configure on-premises MS Exchange 40

6

7

8

Office 365 Fax Server mailbox

VM Installation on Windows Server

Installing the Package on Windows server

68

61

76

9

Installation Setup Files 103

10

Brooktrout SR140 Software 159

11

Installing purchased SR140 licences

163

12

Brooktrout Configuration tool

182

13

Start msXfax Services

190

14

15

msXfax Licensing - obtaining a license file 195

Configuration 198

16

Dynamic Routing to Exchange Distribution Groups

204

17

Inbound fax routing using Office 365

214

18

Gmail for business Fax Server mailbox

218

19

Testing the fax server

219

20

Cover sheets

229

21

Troubleshooting 232

22

Optional: msXfax Web console 234

23

Reporting Software

269

24

Powershell utility for Distribution Groups

290

25

Uninstalling msXfax

26

International dialling codes

297

299

Table of figures

Foreword

Software notice / latest revisions

Component changes since previous release

Version 8.1 Build 22 - March 2016

Build 21 - November 2015