msxfax for microsoft exchange 2003, 2007 & 2010 server 1 · 2.3.8 pbx least cost routing over...

msXfax for Microsoft® Exchange 2003, 2007 & 2010 Server 1

Document Version 7.6 for software version 7.6 build 356

Installation, administration & user guide

with commitment comes success

Software version msXfax 7.6 build 356

Documentation version 7.6 rev 356 7 January 2010



Installation, administration and user Guide

© Copyright 1996 to 2010 Better Network Services Group Pty Ltd, all rights reserved.

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

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. Exchange Server 2010 is a Trademark of Microsoft Corporation Inc. Exchange Server 2007 is a Trademark of Microsoft Corporation Inc. Exchange Server 2003 is a Trademark of Microsoft Corporation Inc. Windows®, Windows 2008®, Windows 2003®, Windows 2000® and Windows

XP® are registered trademark of Microsoft Corporation Inc. Acrobat® is a registered trademark of Adobe Systems Inc. Eicon and Diva Server and trademarks of Eicon Networks Inc/Dialogic.



Table of Contents

1 Installation checklists and latest revisions 17

1.1 Latest Revision history 17

1.2 Checklist for customers UPGRADING msXfax from a previous release of msXfax 25

1.3 Checklist for New Installations only 26

2 Introduction 28

2.1 Architecture 28 2.1.1 High Level diagram: the boxes 29 2.1.2 Software components 30 2.1.3 Message flow diagram 31

2.2 Quick Start Guide for the technical gurus 32 2.2.1 Can I test msXfax without a fax board? 32 2.2.2 Can my Outlook Web Access users send & receive faxes? 32 2.2.3 Do I have to put FaxEnabled into every user’s AD record? 34 2.2.4 Can I use a Security Group to control access to a fax server? 34 2.2.5 Does msXfax Security Group access controls support nested

security groups? 34 2.2.6 I want all users to be able to send faxes, should I use the Fax

Enabled Security Group? 35 2.2.7 Do I need to authorize inbound fax using the Fax Enabled

options? 35 2.2.8 Is msXfax affected by anti-virus software products? 35 2.2.9 Does msXfax run on Windows Server 2003? 35 2.2.10 Does msXfax run on Windows Server 2008 64bit? 36 2.2.11 Does msXfax support Exchange 2003 Server? 36 2.2.12 How does msXfax handle failures in Exchange 2003 Server? 36 2.2.13 How does msXfax handle failures in Global Catalog

Servers? 36 2.2.14 Can I install msXfax in a pure Exchange 5.5 environment? 36 2.2.15 Can I install msXfax on an Exchange 2000 server? 36 2.2.16 Can I install msXfax on an Exchange 2003 server? 36 2.2.17 Can I install msXfax on an Exchange 2007/2010 server? 37 2.2.18 Can I use msXfax in an Exchange 2003 server network? 37 2.2.19 Can I use msXfax in an Exchange 2007/2010 server

network? 37



2.2.20 Can I install msXfax on SBS 2003 server? 37 2.2.21 Where do I install the fax software? 37 2.2.22 Can I install msXfax on a Domain Controller? 37 2.2.23 Can I install msXfax on a Virtual Machine? 37 2.2.24 Is FAX address space supported? 37 2.2.25 Can I install msXfax on a server which has SQL server? 37 2.2.26 Can msXfax work with Teleform software? 38 2.2.27 Where do I install the Eicon Diva Server board? 38 2.2.28 What Exchange Service packs and registry considerations

are there? 38 2.2.29 What permissions do I need to install msXfax? 38 2.2.30 What permissions does the fax administrator need? 38 2.2.31 Does msXfax Messenger Service need to logon with account

permissions? 39 2.2.32 Does msXfax Print Service need to logon with account

permissions? 39 2.2.33 What end user security considerations are there? 39 2.2.34 What do I install on my users’ PC? 39 2.2.35 What do I need to know about Active Directory ? 40 2.2.36 I have msXfax 5.0x, how do I migrate to msXfax? 40 2.2.37 Where do I get help? 40

2.3 Configuration options & capacity planning 41 2.3.1 Theoretical sizing of a fax server 41 2.3.2 Practical sizing of a fax server 41 2.3.3 Small to medium installations with direct inbound routing. 43 2.3.4 Larger installations with direct inbound routing. 46 2.3.5 Which Eicon Diva Server board should I buy? 47 2.3.6 Can I set up a load test with Eicon boards with loop back

cables? 48 2.3.7 Connecting Eicon Diva Server to PBX’s 48 2.3.8 PBX least cost routing over IP networks 48 2.3.9 Connecting Eicon Diva Server to Cisco IGX WAN Switch 48 2.3.10 ISDN Line ordering specifications Basic Rate(s) 49 2.3.11 30 channel 2MB ISDN Line ordering specifications 49 2.3.12 North American Primary rate Line ordering specifications

Primary rate 50 2.3.13 North American channelized T1 connection Line ordering

specifications 51

2.4 Dialogic (Eicon Networks) Inc Contacts 52

3 Installation pre-requisites & considerations 53

3.1 Pre-requisites of your Exchange 2007 Server 53

3.2 Pre-requisites of your Exchange 2003 Server 53 3.2.1 Domain considerations 53 3.2.2 Schema 54



3.2.3 Exchange Server Service pack considerations 55 3.2.4 Exchange Server Registry Key addition 55

3.3 Pre-requisites of your fax server 56 3.3.1 Fax Server computer 56 3.3.2 Fax Server software 57 3.3.3 Direct InBound Fax Routing Utilizing PBX DTMF Tones

with selected Loop-Start Boards 57 3.3.4 Dialogic Diva Server Boards 58

3.4 Inter-operability with other applications 59 3.4.1 Finance One from Technology One 59 3.4.2 SAP Connectivity Exchange 2003 59 3.4.3 Connectivity to Alcatel OmniPCX 60

4 Configuring Exchange Server 2007/2010 60

4.1 Exchange limitations Outlook Business Fax Contacts 60

4.2 Exchange topology notes 61

4.3 Set up when msXfax will communicate with a Hub Transport Server role 62

4.4 SMTP Communications to Exchange from msXfax 62

4.5 Create a send connector for msXfax 69

4.6 Verify Connection from msXfax to Exchange 77

4.7 msXfax Service Account 80 4.7.1 Change msXfax mailbox POP3 protocol settings 84 4.7.2 POP3 protocol settings 85

5 Configuring Exchange Server 2003 87

5.1 Configure POP3 virtual server for line wrap 87

5.2 Configure Exchange SMTP Connector 88

5.3 Adding an account in Active Directory for msXfax 92 5.3.1 Customers configuring more than 1 fax server in a

site/connector 98

5.4 Exchange POP3 Service 98

5.5 Service Account for msXfax Printing 99



6 Preparing your fax server 100

6.1 Installation on Windows Server 2003 32 bit 100

6.2 Permissions for a member fax server 103

6.3 Permissions required when installing msXfax on a Domain Controller 104

6.4 Anti-virus software 106

6.5 Installation of Microsoft Office 107 6.5.1 Office 2007 installation section 108 6.5.2 Office 2003 installation section 109

6.6 Configure the Microsoft Office Document Image writer 112

6.7 Optional: Installation of Adobe Acrobat Software 113 6.7.1 Installing Adobe Acrobat Professional full product 113

6.8 Installing support for MAX Compress / Winzip 117

7 Installing Eicon Diva Server boards 118

7.1 Installing Eicon Diva Server board(s) 118

7.2 Obtaining Eicon Diva Server software 118

7.3 Installing the Eicon Diva Server software 120 7.3.1 Customers upgrading from Eicon Diva Server version 6.x 120 7.3.2 New Installations of Eicon Diva Server software 120 7.3.3 Diva Server Configuration Wizard 120

7.4 Configuring a Diva Server ISDN adapter 124

7.5 Configuring a Diva Server Pri adapter 128

7.6 Configuring a Diva Server Analogue adapter 130 7.6.1 Inbound routing using DTMF routing from PABX systems 133

7.7 Saving your configuration 133

7.8 Testing a Diva Server adapter 134 7.8.1 Test if your line is working 134



8 Dialogic Fax over IP solutions 136

9 Upgrading your msXfax software 137

9.1 Special notes for existing customers 137

9.2 Upgrading to release 7.0 and above 137

9.3 Upgrade procedure for non Exchange environments 137 9.3.1 Before you start the upgrade 138 9.3.2 Upgrade Eicon Drivers 138 9.3.3 Upgrade msXfax installation files 138 9.3.4 Upgrade msXfax with the MSXSETUP.EXE 138

10 Initial Installation Files 141

10.1 Installing the installation files 141

11 Installing msXfax on your Exchange server 142

12 Installing msXfax 143

12.1.1 Login to the Domain & Permissions 143 12.1.2 Run the Setup program 143 12.1.3 msXfax Print Service 153

13 msXfax configuration overview 155

13.1 Permissions & Security 155

14 msXfax Configuration 156

14.1 msXfax Console 156

14.2 Configuring Dialogic (Eicon) boards 156 14.2.1 Configuration option for analogue Eicon Diva Server 158

14.3 msXfax General Configuration 160 14.3.1 Licensing 160



14.4 msXfax Configuration in more detail 163 14.4.1 msXfax System Attendant 163 14.4.2 msXfax Routing Engine 164 14.4.3 msXfax Messenger 166 14.4.4 msXfax Dispatcher & Fax Queues 170

15 Send a test fax and some useful utilities 172

15.1 msXfax Utilities 172 15.1.1 Abort Broadcast 174

16 Active Directory Integration 176

16.1 Introduction 176 16.1.1 Quick setup all users can send a fax without automatic

cover sheets 176 16.1.2 Quick setup all users can send a common automatic cover

sheet 177 16.1.3 Global cover sheet based on sender’s email address 180 16.1.4 Other global default options 181

16.2 Fax Server Access Controls 182 16.2.1 Adding an OU to the local domain where the fax server

accesses AD 183

16.3 Keywords & authorization to send a fax using Notes Field 189 16.3.1 Routing to Distribution Groups 193

16.4 Enterprise security & controls 195

16.5 Security recommendations 196

16.6 Active Directory Performance Settings 196 16.6.1 How to reduce the number of queries to GC’s 197 16.6.2 Usage of Static GC option 199 16.6.3 More information on Special Inbound Processing 199

17 Global Fax Settings 205

17.1 Introduction 205 17.1.1 Global Fax Server Permissions and Cover Page Settings 206 17.1.2 Fax Server 207 17.1.3 User Feedback 208 17.1.4 Message Limits 209 17.1.5 Audit images of sent and received faxes 210 17.1.6 Default handling of inbound faxes 212



17.1.7 Scenario 212 17.1.8 Compress or Rebuild Fax Database 221 17.1.9 Manage Fax Confirmation Templates 223 17.1.10 Reports 226 17.1.11 Automatic Reporting 227 17.1.12 Quick access to fax server statistics 229

18 msXfax Enhanced Security Edition 230

18.1 Permitted Security Classifications 231

18.2 Agency support details 231

18.1 msXfax generated messages 231

19 Dialing Rules and Least Cost Routing (LCR) 232

19.1 Introduction 232

19.2 Least Cost Routing (LCR) 233

19.3 msXfax Setup routines 233

19.4 Dialing Rules 233 19.4.1 Dialing Rules Level 1 - Exceptions 235 19.4.2 Dialing Rules Level 2 – International 236 19.4.3 Dialing Rules Level 3 – Local Calls 236 19.4.4 Dialing Rules Level 4 – Long Distance 237 19.4.5 Dialing Rules Level 5 – Absolute number (Freeform) 237 19.4.6 USA example showing 2 area codes (781 and 617) in Boston 237 19.4.7 USA example area code 781 Boston with a LCR to a fax

server in Hong Kong 239

19.5 Other facilities of dialing rules and LCR 243 19.5.1 Build a list of remote fax servers 243 19.5.2 Build a list of fax number masks 243 19.5.3 Build a list of test fax numbers 244 19.5.4 Request a remote dialing rules view from remote fax servers 244 19.5.5 Delete a Dialing Rule View 245 19.5.6 Test Dialing Rules 245 19.5.7 What to do if you decide to change an IP address on a fax

server 246

20 Configuring Cover Sheets 247

20.1 Domain level cover sheet controls 247



20.2 Cover Page types 248 20.2.1 Static Cover Page 248

20.3 Cover Page Editor Overview 254 20.3.1 Cover Page tool features 254 20.3.2 The Keyword Tag definition is made up of two parts : 256

20.4 Using the Cover Page Tool 257 20.4.1 Configuration 257 20.4.2 Use of tables in RTF cover page files 257 20.4.3 Keywords 258 20.4.4 Open a sample Cover Page file msXcover.rtf 258 20.4.5 Test your Cover Page 260

20.5 How does msXfax handle text from Outlook 261

20.6 Fax Server cover page keywords 262

20.7 Management of cover sheets in large enterprises 266

21 Other configuration elements and options? 267

21.1 Changing confirmation messages 267

22 Configuring Exchange/AD for other tasks 268

22.1 How to route a fax to a user using DDI values 268

22.2 Creation of Active Directory Fax Contacts 268

22.3 How to route inbound faxes to a public folder 271 22.3.1 Create a Distribution Group which includes a public folder 273

22.4 Routing inbound faxes to external contacts 279

22.5 Inbound Printing Configuration 282

23 Fax Server Management 284

23.1 Windows Terminal Services and other products 284

23.2 System Center Operations Manager (SCOM) 2007 285

24 How do my users use the system? 286

24.1 Outlook Web Access 286



24.2 Addressing & Sending faxes 288 24.2.1 Outlook Contacts 288 24.2.2 Outlook Contacts using msXfax Domain Addressing 290 24.2.3 Send a Word document example 291 24.2.4 Sending faxes when using Microsoft Word 293 24.2.5 Outlook public folder Contacts 294 24.2.6 msXfax Domain Addressing 294 24.2.7 msXfax free form addressing 295

24.3 Faxing from Windows Applications 297 24.3.1 How to set up Microsoft Office Image Writer 297 24.3.2 Print from your application 298

24.4 Broadcast faxing 300 24.4.1 Installing Microsoft Office Document Image Writer 301 24.4.2 Configure the Microsoft Office Document Image writer 303 24.4.3 Set up of your Excel CSV file 305 24.4.4 Set up a broadcast document 305

24.5 Receiving faxes 308

24.6 Special commands 309 24.6.1 Passcodes 309

24.7 Manual Selection of Cover Page 310

25 Removing msXfax 311

25.1 Exchange Server considerations 311

25.2 Removing msXfax from the fax server 312

25.3 How to remove msXfax if WISE fails to correctly remove msXfax 312

25.3.1 First and preferred option 312 25.3.2 Removal via a re-install 312

26 Management, Troubleshooting & error messages 314

26.1 Database maintenance 314

26.2 msXfax data flow diagram 318

26.3 Exchange 2007 back pressure 318

26.4 Winmail.dat error messages 319

26.5 User receives Email with Subject = Incomplete Fax Received 319

26.6 Which folders can be monitored by network management software 319

26.7 Possible ISDN Errors from Diva Diagnostics 320



27 ENotify Application Interface 323

28 Independent Software Vendor and application programmer

integration guide 323

28.1 ENotify-AI approach 323

28.2 Email based approach to application integration 323 28.2.1 Application programs using domain addressing 324 28.2.2 Application Cover Sheets (Fax forms) 325 28.2.3 Application Cover Sheets (Fax forms) 325 28.2.4 Keywords supported in the memo of an email 326 28.2.5 Exchange Connector address space for ISV applications 327

29 Systems Integration Notes 328

29.1 Building a lab using BRI crossover cables with Eicon 328

29.2 PRI crossover cables for Eicon PRI cards 328

29.3 PRI crossover cables and PABXs 328

29.4 Objectives of a lab 329

29.5 Design considerations for high volume networks 331

29.6 Integration with Alcatel-Lucent OmniPCX office R510/23.4 331

30 Monitoring 334

30.1 msXfax System Tester 334 30.1.1 Installation 334 30.1.2 Edit INI file 336 30.1.3 Attachments to render 338 30.1.4 Changes made require a restart of the service 338

30.2 Log file data 338

30.1 Procedure to update to new versions 339

30.2 Procedure to remove msXfax System Tester 339



Table of tables

Table 1: Technology upgrades that take advantage of Microsoft’s new platform 28

Table 2: Dedicated Fax Server computer specifications 56

Table 3: Fax Server software specifications 57

Table 4: msXfax support attachment extension types 107

Table 5: msXfax keywords and their usage 191

Table 6: msXfax utilization of AD 220

Table 7: Example of Keyword Tag definition 256



Table of figures

Figure 1: High level diagram showing that msXfax is implemented on a Windows 2003 computer in the same Active Directory domain as your Exchange 2003/2007 server 29

Figure 2: Software architecture: high level implementation block diagram showing key Microsoft technologies used by msXfax. 30

Figure 3: High level diagram Exchange Server & msXfax Fax Server 102

Figure 4: The Cover Page Tool is an “always on top” tool, to be used in conjunction with Microsoft Word. Fields are easily dragged onto cover pages created using Microsoft Word. 257

Figure 5: Open the sample cover sheet 259

Figure 6: Cover page testing using the in-built test facility. 260



Foreword

BNS Group would like to thank the following people and organizations for making msXfax a world class product:

To all our staff and their families for working tirelessly to deliver undoubtedly the best value for money product available for Microsoft Exchange Server.

To Amos Wong & Kenneth Chan and the Mandarin Oriental Hotel Group for their input with respect to enterprise networks.

To all our customers for their feedback, wish lists and support of msXfax. To Jane Huxley, Melissa Withers, Allan Cruz, Helen Barnsley, Ross Dembecki,

Mark Host, Bruce Smith, John Paloni, Raj Natarajan, Ed Beck, the Exchange beta team and everyone at Microsoft who continue to encourage us to create world class technology that adds value to Microsoft Exchange and Active Directory.

To our colleagues at Microsoft for developing a great messaging system and the best directory service of all time.

To Hussein Tanana Microsoft support—thanks for following through hotfix rollups into E2K SP2.

To Darwin Abustan, Senior Development Support Specialist, Microsoft South Pacific Regional Support Center – thanks for researching

To Australian Settlements Limited, Australian Association of Permanent Building Societies for ISDN testing.

To Australian Government Solicitors for DTMF testing with their PABX, feedback on documentation improvements.

To Deborah Frankham at OCTAVO for assistance with documentation layout. To Wayne Small MCSE+I MCSE 2000 Technical Director of Correct Solutions Pty

Limited for assistance with SMTP socket pooling references to Microsoft Web site allowing Exchange to listen on specific IP addresses port 25.

To Chew Weng Hock - Eicon Networks Malaysia. To Barry Ho, Eicon & networking specialist consultant Sydney Australia To Eric Henna, Yves Humbert and Alain Kientz of Panalpina Worldwide Freight

for testing SAP and other features of msXfax. To Sunny Mallapur and Savo Regulic – Australian Taxation Office. To Robert Goodworth – IBM/GSA & Department of Finance. To Thinh Ngo Product Infrastructure Manager, Telstra Technology, Innovation

and Product Group. Colin Ewars and Max McLean of the ISDN product group. To Steve Dozspot, Branch Manager Canon Canberra. To janusNET Pty Limited – Greg Cola and Neville Jones regarding Email

Protective Marking Standards implementation and providing janusSEAL evaluation software for verification and inter-operability testing.

Thanks to our customers and partners for being patient with us. We admit to being slow with our releases because we focus on rigorous quality assurance testing which takes time. Thank you all so much.



1 Installation checklists and latest revisions

1.1 Latest Revision history

Release 7.6.0 (Build 356) 7 January 2010

--------------------------------------------------------

Build 356 is a general release. Build 355 was not released generally so you should review all changes inclusive of build 355 below.

Additions to 355 to make build 356 Updated FaxFail.htm and FaxEpmFail.txt templates Updated Documentation Included support for TIFF file attachments. Updated msXfax UI with new Email Protective marking reference to ISM not

ACSI33.

Controlled Release 7.6.0 (Build 355) 12 Dec 2009

-----------------------------------------------------------------

Build 355 is a controlled release to selected customers. It addresses a major problem described in BNS Technical Bulletin 19 Nov 2009 (Copy the link text below into your browser, if you click on the link in Acrobat it may not work - Adobe bug)

http://mycusthelp.com/BNSGROUP/_cs/AnswerDetail.aspx?sSessionID=&inc=735&caller=%7e%2fFindAnswers.aspx%3ftxtCriteria%3dtechnical+bulletin%26sSessionid%3d

Re-architected components of msXfax to circumvent a Microsoft problem described in Technical Bulletin 19 Nov 2009.

New msxfax System Test Service • Provides an automated system test tool to check system integrity on a periodic

basis. Updated msXfaxroutingengine.exe • New msxfaxroutingEngine.exe with new smart hosts to handle Microsoft

change of dropping Custom X Headers in all mime attachments via domain addressing.

• Domain addressed messages are now accepted via the new smart host and passed directly via disk to a modified msxverify.exe that authenticates the sender.

• msxverify.exe still pulls down messages from the msxfax mailbox as well. Updated msXverify.exe • Modified msxverify.exe handles domain addressed files from the routing

spooler directory as well as from the msxfax mailbox. Updated msXfaxout.exe • msxfaxout.exe changed to drop any *.eml files found in the attachment list.

Occassionaly an original.eml is created in the attacthemnt list even though its



not a specified attachment by the sender. Possibly caused by a POP3 error or POP3 sdk.

• msxfaxout.exe changed to drop png & gif files found in auto-signatures but still allow the message to be processed.

Updated All routines using Easymail SDK • upgraded to Easymail 6.5 SDK with patches • Fixed SMTP related problem where long files names in attachments were not

sent correctly back to Exchange. Updated msXfaxout.exe • Support Acrobat 9. Needed to monitor and terminate Acrobat.exe after a

render because task would not terminate. Note Acrobat 7 and 8 still supported. • Fixed a bug where mime files from Exchange 2007 with X-Headers x-tm-as-

user-approved-sender: No AND x-tm-as-user-blocked-sender: No would cause the parser in msXfaxout.exe to identify the wrong sender. This was caused by Exchange Anti Virus X-headers being interpreted as being msXfax related.

• Fixed a rare problem during rendering of Excel Documents on Office 2003/Office 2007 systems where the Microsoft registry setting to suppress launching of the mspview.exe application after printing to the MODI printer is not honoured. The mspview app locks the rendered tif attachment causing the msxfax render process to fail. All subsequent renders also fail while the mspview.exe app stays active in background.

• Patch msXfaxout.exe and msXconv.exe (Multi converter systems) to kill mspview.exe process if running prior to taking and processing rendered tif file.

• Fixed problem where sending a freeeform fax from a user whose email address contains an _ resulted in a failed AD Lookup for the Sender because the _ was stripped prior to the AD Lookup.

Updated AD Routines • Fixed bug where if AD could not be contacted an indefinite wait would occur

consuming CPU.

Release 7.6.0 (Build 350) July 2008

------------------------------------------------------ • Fixed a bug in msXfaxout.exe and msxconv.exe (multi-converter version) to

stop duplicating a tif file attachment when there are multiple recipients. The second recipient onwards would get a doubling up of the attachment. This would only happen if there was a single tiff file attachment.

• Improve performance delivery of inbound faxes by handing off large multipage faxes to the msXorphan.exe process to split up according to inbound message limit sizes and send to users. Previously when incorporated with msxfaxinRX.exe this would slowdown inbound flow and be an issue on busy inbound systems. Patch to msXfaxINRX.exe and msXorphan.exe.

• Include Support for Traditional Fax Receipt which includes Sender Company,Fax Details and scaled first page of sent fax all on a single tif page. Changed : msxfaxXP.exe, msXfaxInTX.exe, msXimage.dll,msxsetup.exe

• Extended the Canon Image Real Capture (IRC) support to look at sub-directories on the IRC output directory. The subdirectory names should be numeric and are used as the ddi value for the new inbound fax. For reference setting IRC support is as follows :



• Support Canon Image Real Capture (IRC). IRC will accept a multi-page tif files with special bar code separator pages in them and split them up accordingly into an output directory. msXfax Image Real Capture service if configured will read this output directory and artificially create inbound fax transactions. These Fax transactions will follow normal processing. In order to activate this functionality create a C:\irc.txt in the root of C:, run the msxsetup.exe and a new service msXfax Image Real Capture will be created. Once installed run msxfax console, select Global Fax Settings, select Special Handling of inbound Faxes, create a record in the database to route inbound faxes with a specific DDI assigned for IRC to a local directory. Make this directory the Input directory for IRC (see IRC Configuration).

• Run Regedit and select HKEY_Local_Machine\Software\Better Network Services Group\msXfax XP\Image Real Capture Pickup. Set the Pickup Directory to the Output directory of Image Real Capture, set the CSID to what ever you prefer, and set the DDI to a new value that must not be the same as the DDI assigned to IRC. (A loop will occur if this is done). Start all services up.

• Place a catch-all test for CSID to drop any characters not in the a-z, A-Z, 0-9 + range. This was done for ATO. Patch to msxfaxInRX.exe

• Handle issue created in Exchange 2007 where multiple recipients via domain addressing are dropped. This was due to duplicate X-Headers not being supported in Exchange 2007 but was in Exchange 2003.

Release 7.6.0 (Build 339) November 2007

------------------------------------------------------ • Support for Exchange 2007 Hub Transport Server connectivity • Automated reports • Support for JPEG & JPG file attachments. • Fixed memory leak in msXDispatchRX, replace use of imagelib with leadtools. • Adjusted the date time assigned to the audit RX and TX tif file name to be the

same as the actual transmit and received time in the statistics table. • Fixed bug in msXfaxout for ENotify to resize rendered tif file to correct

dimensions for Dialogic Fax Card. • Also catered for situation where if render of ENotify attachments fail they are

failed back to the sender. • Fixed bug in msXfaxout for Broadcast to recreate a fresh tif file for every new

batch in a Broadcast transmission, previously tif files were concatenated for each batch in the transmission.

• Fixed problem that occurs when borlandmm.dll crashes during inserting records into Fax database, The result is that a records set comprising Store, Recipient and Attach records are not created. This will result in a stall situation occuring and records not being processed. This patch will delete Orphan Store, Recipient Attach and the associated tif file and requesting the send to resumbit fax.

• Fixed bug in Broadcast module where an apostrophe in a recipient's name caused an insertintostore error.

• Fixed bug where rendering a pdf file temp files are places in the ..\modi spooler directory. On a Failure on the render these temp are not cleared out and could be used in a subsequent render. This fax been fixed.

• Fixed a bug in msXfaxout.exe to stop hitting the Local Database every second to examine queue depths this has been extended to every minute.



• Fixed Bug in Export Local Database where Cache data was also exported when requested. When the CSV was imported cache data was re-created as non-cached data that could not be cleared by the clear cache function.

• Enhanced CSV2ADR to save adr files to the Desktop and changed the button on the adr browse to indicated a save rather than an open task is going to occur.

• Fixed bug in msxfaxInRX.exe to detect the occurance of a blank CSID after invalid CSID characters are removed during inbound fax filename creation is occuring. If detected the flag CSIDNotSet is set


• Support keyword HKey-Local-Machine\Better Network Services Group\msxfax XP\messenger\SplitInboundByPage that when set to 1 will split all inbound faxes into single pages and route them via the normal logic as individual emails.

• Support intelligent splitting up of inbound faxes into smaller multipage tif files based on the maximum tif file size.

• Support Canon Image Real Capture (IRC). IRC will accept a multi-page tif files with special bar code separator pages in them and split them up accordingly into an output directory. msXfax Image Real Capture service if configured will read this output directory and artifically create inbound fax transactions. These Fax transactions will follow normal processing.

• In order to activate this functionality create a C:\irc.txt in the root of C:, run the msxsetup.exe and a new service msXfax Image Real Capture will be created. Once installed run msxfax console, select Global Fax Settings, select Special Handling of inbound Faxes, create a record in the database to route inbound faxes with a specific DDI assigned for IRC to a local directory. Make this directory the Input directory for IRC (see IRC Configuration).

• Run Regedit and select HKEY_Local_Machine\Software\Better Network Services Group\msXfax XP\Image Real Capture Pickup. Set the Pickup Directory to the Output directory of Image Real Capture, set the CSID to what ever you prefer, and set the DDI to a new value that must not be the same as the DDI assigned to IRC. (A loop will occur if this is done). Start all services up.

6th June 2007

Update History : Release 7.6.0 (Build 334)

-------------------------------------------- • Fixed problem that occurs when borlandmm.dll crashes during inserting

records into Fax database, The result is that a records set comprising Store, Recipient and Attach records are not created. This will result in a stall situation occuring and records not being processed. This patch will delete Orphan Store, Recipient Attach and the associated tif file and requesting the send to resumbit fax.

• Fixed bug in Broadcast module where an apostrophe in a recipient's name caused an insertintostore error.

• Fixed bug where rendering a pdf file temp files are places inthe ..\modi spooler directory. On a Failure on the render these temp are not cleared out and could be used in a subsequent render. This fax been fixed.




• Fixed Bug in Export Local Database where Cache data was also exported when requested. When the CSV was imported cache data was created non-cache record that could not be cleared by the clear cache function.

• Enhanced CSV2ADR to save adr files to the Desktop and changed the button on the adr browse to indicated a save rather than an open task is going to occur.

• Fixed bug in msxfaxInRX.exe to detect the occurance of a blank CSID after invalid CSID characters are removedduring inbound fax filename creation is occuring. If detected the flag CSIDNotSet is set


• Fixed bug in msXfaxInRX to not lookup DNS when installed in a standalone workgroup setup.

• Changed Coverpaged rendering in msXfaxout to use MODI driver • Fixed bug in msxfaxout to not strip _ in email addresses • Fixed bug in console to show/control Eicon Service when Transmit service

disabled. • Fixed bug in msxfaxInRX when the Audit Filename will contain trailing

spaces in the filename for faxes that have been partially received. • Fixed bug where when a CS#usercover.rtf is specified for a one-off coverpage

a trailing space in the coverpage filename would cause the coverpage not to be found.

• Included support for Tiff Class 6 when saving inbound fax files. • Included the administrator email address in an alert message that goes back to

the user when an inbound fax is greater in size to a configured maximum. • Stopped any attachments other than single adr and single tif files being

attached to a Broadcast. • A rare occassion where a reporting error in a Broadcast could cause a deadlock

has been fixed.

1 June 2007

Release 7.6 build 334

------------------------------------------- • Fixed bug in msXfaxInRX to not lookup DNS when installed in a standalone

workgroup setup. • Changed Coverpaged rendering in msXfaxout to use MODI driver • Support Sending tif attachment of failed fax back to the user with

confirmation if configured. • Fixed bug in msxfaxout to not strip _ in email addresses • Fixed bug in console to show/control Eicon Service when Transmit service

disabled. • Fixed bug in msxfaxInRX when the Audit Filename will contain trailing spaces

in the filename for faxes that have been partially received. • Fixed bug where when a CS#usercover.rtf is specified for a one-off coverpage

a trailing space in the coverpage filename would cause the coverpage not to be found.

7 May 2007

Release 7.6 build 330

-------------------------------------------



• Added a permissions check in the system attendant and print service to check that the respective service accounts have permissions to write to the registry. Local Administrator permissions are required for the services to operate correctly.

• Support for Eicon diva server drivers version 8.3 • Support for Windows 2003 SP2 or SP1. • Include support for .eml files that have html bodies, change made to

msxfaxout.exe • Include in msxsetup option to disable the print spooler or if required specify a

separate service account details for msxfax print spooler. See UI Change in setup. A potential conflict is possible with both the messenger and print spooler running under the same logon credentials as both attempt to set different default printers at the same time.

• The Attendant does now not attempt to startup diabled services • Support the setting of a single Static GC for all AD lookups - See UI change in

Messenger Properties un Active Directory • Support the holding of suspect mime files in a suspended sub-directory in the

Router Spooler directory. If an error other than SMTP Server not being contactable occurs from the Routing Engine those mime files will be held in a Suspended directory and an NT Event Message will be raised.

• Improved Windows Event Logging being progressively introduced to all msXfax modules to provide richer content for network management products such as Microsoft Operations Manager.

• Fixed bug where Dispatcher would consume CPU when idle. • Support for Adobe Acrobat full product version 8 • Support for Office 2007

12th Sept 2006

Update History : Release 7.6.0

--------------------------------------------

- Support Email Protective Marking standards compliance for Australian Government.

- Do not block 50+ recipients from being sent to in a single fax. Now there is no limit because of MODI driver.

- Drop MAAD/R20 tool from setup.

- Supplied a new CSV to ADR utility for use with Broadcasts.

- msXfax Console OutQ count now includes Faxes transmitting and waiting for a free line.

- msXfax Console ProcessQ count now includes Faxes being rendered by Enotify and msxfaxout and waiting to be processed by converter.

- Certified with SoftIP v2.0 and Alcatel OMNIPCX Office Rel 5. (Fax over IP – FOIP T.38 standards compliance)

- Support a special record in the Local Database when AD is disabled and a user record is created with an email address of 'allusers@domain' e.g [email protected], outbound fax requests from any user in test.com will be allowed to send a fax.

- Fix bug where if an invalid fax number is specified in a list using domain addressing then no results is returned.



- Support Exchange 2007

- Support Office 2007

- Fix bug where on a rare occasion a tif file associated with an outbound fax gets lost. The fax now rejected back to the user rather than holding up a device as in use.

- Free Disk Space monitoring builtin to msXfax Attendant. See Attendant Configuration.

23rd June 2006

Update History : Release 7.5.1 (Build 319)

--------------------------------------------

- Drop support for apf fax printer driver and support Microsoft Office Document Image Printer available in Office 2003.

- Clearer higher resolution tiff files created for faxing.

- Support for Office 2003 SP2

Update History : Release 7.5 (Build 314)

--------------------------------------------

11th April 2006

- Fixed bug in outbound fax call where calling Party number was set to a space and causing an issue on Alcatel PBXs.

- Fixed a bug where an inbound fax had the potential of being lost on fast processors.

- Fixed a bug where on a busy server a mime file containing a fax request was incorrectly deemed to be corrupt.

- if the file could not be renamed from an .eml to .emt for processing. The logic has been changed to retry the rename.

Update History : Release 7.5 (Build 312)

--------------------------------------------

11th March 2006

- Support for Load Balancing across multiple msXfax servers via the msXfax routing engine.

- Support for multiple routed destinations (served in a round robin fashion) from a dialing rule.

- Extensive Least cost routing, load balancing and load testing performed across many msXfax servers in this release.

- Fixed Cover Page support.

- Performance improvements.

- R2O support dropped and replaced with Microsoft Office Document Imaging Printer support. Creates tiff files from any application.

- Support for prioritised Broadcasts via rules engine.

- Cached Active Directory calls.



- Support for real-time Fax Header processing via Eicon Diva Server.

- Drop support for TAPI Modems and Brooktrout boards. This release supports Eicon Diva Server only.

- Support for Canon Multi-function Devices. Support a fast submit.

- Support for automatic loopback mode when TX/RX circuits in Diva Server Configuration set to 0.

- Support for intelligent dialing where the same fax number will not be dialed outbound on multiple channels.

- Support for Australian On-Ramp 10, On-Ramp 20, On-Ramp 30 licensing variants.

- Tested with Eicon SoftIP v1.2 in a Lab facility with 2 Fax Servers back to back with 30 lines.

- Office 2003 SP1 Support on the Fax Server.

- Support for user specified keywords words in email body

- /S-userkeyword=value

- /R-userkeyword=value

- These keywords like [S-USerKeyword] and [R-UserKeyword] should be placed in the coverpage

- and will be replaced with the specified value during rendering.

- Support for Default Inbound Route to an email address and/or folder.

- Support for tiff and bmp files natively.

- Support for Acrobat 7. Note. Acrobat 5 or 6 cannot be installed inplace of Acrobat 7 because

- of changes Adobe have made.

- Brooktrout Support has been dropped from the setup.

- Fixed bug where on shutdown an error referring an unknown device was displayed.

- Support for Eicon SDK 3.5 and drivers v8.0.

- msxdispatchRX.exe had bug where outbound faxes with an apostrophe in the subject would not get updated

- in the stats table.

- Fixed bug in msXfaxInRX where inbound faxes were getting saved with multiple .tif extensions to folders

- specified in the special inbound db. This occurred when auditing was turned on.

- support Channel based routing on an Eicon Analogue card

- The Channel No is mapped to a DID value so the DID logic inplace will work.

- Support for Eicon Diva Server ver 8.0 Drivers.



1.2 Checklist for customers UPGRADING msXfax from a previous release of msXfax

This checklist provides you with a list of tasks which must be completed by existing customers intending to upgrade an existing msXfax Fax Server. If you are upgrading for other reasons eg: infrastructure upgrades to Exchange 2007 then you should consider all factors and perhaps treat the project as a new installation.

Tasks to install and configuring msXfax Install notes

Install Windows Server 2003 SP2.

msXfax version 7.0+ now performs an upgrade in place of releases from 6.2.1. If you have a release prior to release 6.2.1 you should note all parameter settings of your current system, save your existing cover sheets, remove your old msXfax version then install the new version.

Save your cover sheets, export any statistics or produce reports as required because this information will be deleted.

Customers using Eicon Diva Server boards must download Eicon Diva Server software version drivers as described in this manual. ALL customers should complete the configuration of Eicon Diva Server software.

Install initial installation files (INSTALLMSX.EXE). This will update the installation files on your fax server.

Remove previous versions of Microsoft Office. If you are not changing the version of Office then there is no requirement to remove Office.

Re-Configure Microsoft Office Document Image writer Printer Driver

Run msXsetup.exe

Configure and Test your fax device(s)

Configure msXfax

Send a test fax. Send a fax to msXfax – check admin alert mailbox for its arrival

Configure Global Options as required

Modify default cover sheet and/or create new cover sheet(s). Copy back any saved cover sheets.

Implement other options as required. Review possibility of using security groups for access controls if you current use [Fax Enabled] keyword. If you allow all users to send a fax then you should NOT implement security group checking due to the overhead involved

Only customers upgrading from 6.5.4 to 7.0+ will require a new security license keys. Customers on previous releases eg: 6.2 will not require new license keys unless they intend to make license changes or hardware changes.

Customer testimonials can be sent to [email protected] or via your reseller.



1.3 Checklist for New Installations only

This checklist provides you with a list of tasks which must be completed by most customers installing msXfax for the first time. This manual provides a logical sequence to follow when installing msXfax. The order of each chapter and the order of this checklist closely match one another. Please use the checklist to ensure that key tasks are completed. Verify that all other documented chapters have been completed/reviewed. Follow the sequence of the user guide

Tasks prior to installing and configuring msXfax Install notes

Please check the backup strategy of the fax server. USB hard disks will affect the license key of msXfax if a USB hard disk is connected.

Identify Exchange bridgehead server(s) in your Exchange 2003/2007 network which will be used to configure a standard Microsoft SMTP Connector to provide a connection between Exchange and msXfax smart host services.

Exchange 2007 Sites perform section 4

Exchange 2007 installations Section 4

Exchange 2003 Sites perform section 5

Exchange 2003 installations Section 5

POP3 virtual server line wrap. Microsoft have outstanding issues with this. This is just a note for your information.

No action required.

Configure SMTP Connector and apply address space to the connector Section 5.5

Configure msXfax domain addressing if required. Section 5.5.1

Create an Active Directory mail enabled user account for each fax server Section 5.6

Check that the Exchange POP3 service is running Section 5.7

Tasks to install and configuring msXfax

On a suitable computer (refer sizing recommendations in this guide) install Windows Server 2003 32 bit version SP2

Section 6.1

Set the Windows event log to overwrite. Set regional and other settings for your environment Section 6.1

Set permissions for a member fax server Section 6.2

If installing on a domain controller – set permissions Section 6.3

Check Anti Virus settings so that msXfax and related directories and process are not affected Section 6.4

Install Office 2003 OR install Office 2007 (see detailed section for version support) Section 6.5

Configure Microsoft Office Document Image writer Printer Driver . Section 6.6

Install Adobe Acrobat FULL PRODUCT (see detailed section for version support) Section 6.7

Optional – installation support for MAX Compress / WINZIP Section 6.8

Install Eicon Diva Server boards and Eicon drivers Section 7

Diva Server adapter Line testing Section 7.7



If using SoftIP (Fax over IP) then install Eicon SoftIP Section 8

Observe special notes if upgrading from a previous release of msXfax Section 9

Install initial installation files (INSTALLMSX.EXE) Section 10

Special notes if you do intend to install msXfax on your Exchange Server Section 11

Running the msXfax setup program Section 12

Read the configuration overview Section 13

Configure your Eicon fax board Section 14

License your fax server (Not required if you are evaluating msXfax) Section 14.3.1

Review and Configure other msXfax information Section 13

Send a test fax. Send a fax to msXfax – check admin alert mailbox for its arrival Section 15

Active Directory and other considerations and settings Section 16

Configure Global Options as required. Determine if you will allow all users to send or restrict users sending based upon Group membership or via keyword in Notes field. Group membership is recommended.

Section 17

If you have licenced the Enhanced Security Edition you should configure settings Section 18

Dialing Rules and Least Cost routing – this section is optional. Australian customers are advised to turn on Dialing rules if they intend to support Business Fax contacts in Outlook. Reason: to provide support for users with area codes with and without a zero.

Section 19

Modify default cover sheet and/or create new cover sheet(s) Section 20

Optional – modify confirmation messages sent to users. Perhaps links to your help desk/internal web site for documentation etc.

Section 21

Implement and test inbound fax routing.

Routing to a public folder in Exchange

Section 22.1

Section 22.3

Implement other options as required. Section 22 onwards

Fax Server Management Section 23

How do my users use the system? Section 24

Request a license key from your reseller or BNS’s web site per instructions in this documentation.

Section 14.3.1

Conduct your pilot tests and roll out to users as required.

Customer testimonials can be sent to [email protected]

Customer support is available directly from www.bnsgroup.com.au Customers with support arrangement from their resellers should contact their reseller.



2 Introduction

This guide is designed to provide administrators and technical staff with a comprehensive set of instructions to install, deploy and manage msXfax within an enterprise network or even on a single LAN installation.

msXfax has been built upon 17 years of development at BNS Group, building upon BNS Group’s previous versions of its Email based fax solutions (from the early days of: msMail 3.x) through Exchange version 4 through to Exchange version 5.5 & Exchange 2003 and now Exchange 2007.

Exchange 2000 server was a significant change for Microsoft embracing more industry standards and fully integrating with their new Active Directory (AD) service. Exchange 2007 is another quantum leap forward for Microsoft.

Many other vendors continued to port or modify their existing Exchange Fax Connectors (Exchange MAPI based gateways) in an attempt to fit in with Exchange 2000. BNS Group decided it was time re-develop its software to fully integrate with AD whilst offering a more industry standards based method of integrating with Exchange 2000/2003 server. All references to Exchange include Exchange Server 2003 and Exchange 2007 unless explicitly noted.

Technology : BNS Group has made significant investments in upgrading its technology to take advantage of Microsoft’s new platform.

Table 1: Technology upgrades that take advantage of Microsoft’s new platform

Integration Technology used Comments

Active Directory ADSI, LDAP & ADO msXfaxxp does not extend the schema which makes it attractive to enterprises both large and small.

Exchange 2003/2007 SMTP & POP3 msXfaxxp uses a standard Microsoft SMTP Connector which is configured by you. It is so easy. Administrators appreciate this approach because no 3rd party Exchange components run on your Exchange server. Your Exchange Server Environment remains a 100% pure Microsoft Exchange Environment

2.1 Architecture

An understanding of the architecture of any product will help you understand the fundamental benefits to be gained from such a product.



2.1.1 High Level diagram: the boxes

As can be seen in Figure 1, msXfax fax server hardware and software can be installed on a separate Windows 2003 (32bit) member server.

Figure 1: High level diagram showing that msXfax is implemented on a Windows 2003 computer in the same Active Directory domain as your Exchange 2003/2007 server

Com3

msXfax can be installed on: Windows Server 2003 32 bit domain controllers or member servers.



2.1.2 Software components

msXfax uses the latest Microsoft recommended technologies to integrate and interact with key Microsoft services: Active Directory Services and Microsoft Exchange server using Industry standard protocols for message transmission with Exchange Server..

Figure 2: Software architecture: high level implementation block diagram showing key Microsoft technologies used by msXfax.

msXfax fax server can be installed on Windows Server 2003 (32 bit only) SP2. ADSI interacts with Active Directory Domain Controllers, SMTP & POP3 interacts with the Exchange server. In many instances, the Exchange server is also a Domain Controller/Global Catalogue Server (for more information on Domain Controllers and Global Catalog servers, refer to Microsoft’s Exchange server and Windows 2003 Active Directory resource and planning guides).

Exchange 2007 is slightly different but the same principles apply.



2.1.3 Message flow diagram

Figure 3: msXfax message flow



2.2 Quick Start Guide for the technical gurus

2.2.1 Can I test msXfax without a fax board?

Yes. Set the number of transmit and receive channels to 0 (zero) and that will automatically enable a software loopback. By default this is the setting for a new installation allowing prospective customers to test msXfax functionality without a fax board.

2.2.2 Can my Outlook Web Access users send & receive faxes?

Yes.

Receiving faxes is no different from the Outook rich client. Internet Explorer has a TIF viewer for reading faxes.

Sending faxes from OWA can be done using all methods described in this guide. However, OWA does not create a “FAX” address book entry like the rich client does when a Business Fax field is defined by a user.

Therefore, if OWA users want to create Fax Contacts they should create a Contact with an email address which follows the msXfax domain addressing format.

OWA users can define a contact’s fax address just like a regular email address. The addressing format is known as msXfax domain addressing. A second email address is built into OWA contacts which can be used for a fax address.



The above example shows how OWA Contacts can be defined with a regular email address and a fax address.



Your users can select either Bob Brown’s email address of his fax address.

2.2.3 Do I have to put FaxEnabled into every user’s AD record?

NO. By default, ALL users can send a fax when msXfax is installed. msXfax will check AD to see if they actually exist. To restrict who can send you need to set an option in Fax Global Settings to use either the NOTES field in AD or use Security Groups as the means of controlling who can send a fax. If you must have granular controls for sending faxes, use Active Directory security groups.

2.2.4 Can I use a Security Group to control access to a fax server?

YES. msXfax allows a network administrator to define a security group in an OU in a Domain to control access to send a fax. By default ALL users can send unless you nominate to use either control by Group or via the Notes field. The administrator can define control via a keyword in the Notes field or via a Global/Universal Security Group or Distribution Group.

2.2.5 Does msXfax Security Group access controls support nested

security groups?

YES, however, Nested Groups from other Domains are NOT Supported. To allow users from other domains in the same forest to send faxes directly to your fax server in your domain; you have to specifically add the user to the Fax Enabled Universal Security Group in your domain.



2.2.6 I want all users to be able to send faxes, should I use the Fax Enabled

Security Group?

NO. Just take the defaults which allow all users to send a fax. Messages are still authenticated via an email address lookup to AD. We assume your firewall prevents spoofing. msXfax always checks the sender’s email address against AD to ensure that the sender’s email address is an AD user object.

2.2.7 Do I need to authorize inbound fax using the Fax Enabled options?

No. A fax received by the fax server does not require any specific authorization controls other than the DID/DDI routing value being placed in an Active Directory (AD) record. In other words, a user can receive faxes without requiring any other form of authorization. You have authorized receipt by them by virtue of adding a routing value in their AD record.

2.2.8 Is msXfax affected by anti-virus software products?

msXfax is fully tested with Symantec Anti-Virus Corporate edition during BNS Group quality assurance tests.

For all anti-virus software products the following directories must be excluded from being scanned:

Program files\BNS Applications and all sub directories

msXtemp

ETrust from Computer Associates is known to be intrusive on files created by msXfax causing msXfax to fail. Customers using ETrust should take appropriate action to prevent msXfax files and processes from being impacted by ETrust.

This is what to do if you have ETRUST • Excluding the directory :\program files\BNS Applications

• Exclude msXtemp directory off the root.

• If that does not work then you may have to disable real time scanning (version 6.x of Etrust for example).

• Perform periodic scans of your hard drives

2.2.9 Does msXfax run on Windows Server 2003?

YES. msXfax has been tested on 32 bit version of Windows Server 2003 SP2. 64bit is not supported because MODI printer drivers are not available from Microsoft.



2.2.10 Does msXfax run on Windows Server 2008 64bit?

NO. msXfax has been tested on 32 bit version of Windows Server 2003 SP2. 64bit is not supported because MODI printer drivers are not available from Microsoft.

http://support.microsoft.com/kb/927383/en-us

2.2.11 Does msXfax support Exchange 2003 Server?

YES: msXfax has been tested with Exchange 2003 SP1 and SP2.

2.2.12 How does msXfax handle failures in Exchange 2003 Server?

Good question. Most other fax products crash when the Exchange Server services fail or are stopped. This is because most other fax products use Extended MAPI based gateways (Connectors). msXfax is not affected by Exchange being stopped or any individual services being stopped. Of course, no faxes will flow in or out of Exchange in all situations. msXfax will continue to receive faxes from external parties and will hold onto those faxes until Exchange SMTP services are restored.

2.2.13 How does msXfax handle failures in Global Catalog Servers?

Many fax products which are Active Directory aware typically require an LDAP/global catalog server to be hard coded in the configuration.

msXfax dynamically binds to the next available Global Catalog Server in the AD Site or another GC which responds to ADSI queries.

msXfax is therefore not affected by a GC failure if other GC’s are available in the site or enterprise.

msXfax uses Microsoft Active Directory Services Interface (ADSI) to establish which GC it should query against. A failure in a GC therefore should not impact on msXfax if the customer has designed their AD correctly. At least 2 GC’s should be available in a site. Architects should also provision at least 1 GC per domain per site.

2.2.14 Can I install msXfax in a pure Exchange 5.5 environment?

NO. BNS no longer supports Exchange 5.5 installations.

2.2.15 Can I install msXfax on an Exchange 2000 server?

Not supported.

2.2.16 Can I install msXfax on an Exchange 2003 server?

Not supported.



2.2.17 Can I install msXfax on an Exchange 2007/2010 server?

Not supported

2.2.18 Can I use msXfax in an Exchange 2003 server network?

YES.

2.2.19 Can I use msXfax in an Exchange 2007/2010 server network?

YES.

2.2.20 Can I install msXfax on SBS 2003 server?

Not supported

2.2.21 Where do I install the fax software?

• You fax server can be installed on Windows Server 2003 32 bit family. • We recommend a member server which is not an Exchange Server.

2.2.22 Can I install msXfax on a Domain Controller?

Yes.

2.2.23 Can I install msXfax on a Virtual Machine?

For testing purposes in loopback yes. msXfax relies on Dialogic (Eicon) Diva Server cards for robust communications. Therefore, for production implementation a physical server is required.

2.2.24 Is FAX address space supported?

No longer supported because Microsoft did not provide compatibility for the ISV community with the introduction of Exchange 2007. Use Domain addressing.

2.2.25 Can I install msXfax on a server which has SQL server?

msXfax has been tested on a system which also runs SQL 2005.



2.2.26 Can msXfax work with Teleform software?

msXfax has been tested on a system which has Teleform and SQL server.

2.2.27 Where do I install the Eicon Diva Server board?

Installation of Eicon board(s) is on the fax server where you intend to install msXfax software. Eicon Networks is now called Dialogic.

All Eicon Diva Server boards are supported except the voice only boards. This provides:

• ISDN Basic Rate • ISDN Primary rate E1 • North American T1 • Analogue boards

2.2.28 What Exchange Service packs and registry considerations are

there?

• Exchange 2003 Server SP2 is supported. • A registry additional parameter is required. The procedure is documented

further on in this guide. • Exchange 2007 with SP1.

2.2.29 What permissions do I need to install msXfax?

To install software on the Windows server you will need Administrator rights to the local server.

You or your Exchange Administrator will need to login to your Exchange server with sufficient permissions to:

• Configure various Exchange options • Add an SMTP connector

• Create an Active Directory user (Service account) for use by msXfax

2.2.30 What permissions does the fax administrator need?

This is fully documented in this guide. If your administrator is in fact a member of the Domain Admins or Administrators local group (of the Windows member server), they have sufficient permissions to administer msXfax. If you have thought through the benefits of delegated administration through Active Directory and set up ‘pseudo administrators’ (delegated rights in AD, Server Operator and Backup Operator for example) they will not have sufficient rights.

For pseudo administrators you could add one of their Global Security Groups or their individual account to be a member of the local Administrators Group on the Windows computer. Full control permissions are essentially required on the registry keys Local Machine\…\.. BNS Applications for your pseudo administrator to



successfully use msXfax’s console. Alternatively, you could apply specific permissions to the registry key via REGEDT32. Different customers have their own ways of implementing security. Whichever way you decide to implement your security, the above should help you control access to msXfax management console functions.

2.2.31 Does msXfax Messenger Service need to logon with account

permissions?

Yes. It must be a member of the local administrators group.

2.2.32 Does msXfax Print Service need to logon with account permissions?

If you decide to implement printing then the answer is Yes. It must be a member of the local administrators group. If you do not implement printing the service can be disabled.

2.2.33 What end user security considerations are there?

For any user to send a fax they must be listed as a user object in Active Directory or be included in the msXfax local database for non Active Directory networks. Additional security checks can be made including Security Group memberships.

2.2.34 What do I install on my users’ PC?

Office 2003 or Office 2007 or better is required.



2.2.35 What do I need to know about Active Directory ?

Good news! The news that Exchange Administrators want to hear. msXfax does not extend or modify the schema in any way.

You will be pleased to know that msXfax does not extend or modify the schema. Therefore, you can install msXfax without Schema Admin rights. Domain Administrator rights or local Administrator rights for Windows 2003 member servers will be sufficient to install msXfax together with your Exchange Administrator (Full) account capable of creating an SMTP Connector and configuring other options in Exchange System Manager.

2.2.36 I have msXfax 5.0x, how do I migrate to msXfax?

There is a checklist in section 1 of this manual. Follow the checklist for some key considerations. Please feel free to contact BNS Support by placing a call via our web based support system. We will track your support request and respond with answers to assist you in your migration planning.

2.2.37 Where do I get help?

BNS Group has implemented a customer self help service and technical support tracking system. To use the system for pre sales questions or post sales support (to track and manage your support requests) use the link http://mycusthelp.com/bnsgroup/ or simply select Support from the BNS Group web site http://www.bnsgroup.com.au

ALL customers must use the above support system. BNS monitors its web based support systems approximately 18 hours per day.



2.3 Configuration options & capacity planning

2.3.1 Theoretical sizing of a fax server

Fax traffic tends to be oriented around peak periods. Even though a typical fax page typically takes 1 minute to send or receive per page there are so many variations it is difficult to sensibly calculate even a theoretical maximum.

We have therefore made the per page rate = 1 minutes for the purposes of this exercise.

Number of fax lines (Typical fax content)

maximum number of pages per 60 minute period

Comments

1 60 pages per hour This is theoretical only.




2.3.2 Practical sizing of a fax server

BNS Group’s view is that practical sizing of a Fax server should represent 50% or lower of the maximum theoretical. This accommodates many variables and peak demands for fax lines.

If your design involves attachments being sent to the fax server, there is a limited throughput that the fax server will achieve because each attachment must be processed to a rendered image. OLE Automation is used to automate the application concerned eg: Microsoft Word. Version 7.5 of msXfax offers load balancing to utilise multiple fax servers for cover sheet preparation and document rendering.

Number of fax lines

(Typical fax content)

maximum number of pages per 60 minute period

Practical number of pages per minute (50%)

Comments

1 60 pages per hour 30 pages per hour Much higher chance of contention in peak periods

2 120 pages per hour 60 pages per hour

3 180 pages per hour 90 pages per hour

4 240 pages per hour 120 pages per hour This is a popular configuration for msXfax.

8 480 pages per hour 240 pages per hour Much lower chance of contention in peak periods



16 960 pages per hour 480 pages per hour Much lower chance of contention in peak periods



2.3.3 Small to medium installations with direct inbound routing.

Sites receiving faxes directly into Microsoft Exchange Server mailboxes controlled via Active Directory can choose a number of technologies.

Unless otherwise stated, all these options allow outbound transmissions in addition to inbound routing capability.

Inbound routing technology

Option Comments

ISDN direct in-dial (DDI also referred to as DID). This a where many numbers can be assigned to an ISDN service for use with inbound routing.

Eicon Networks Diva server boards

Single Basic: Rate BRI 2M (1 basic rate = 2 fax lines)

4 Basic Rates: 4 BRI 8M (4 basic rate = 8 fax lines)

(Note: a number of these boards can be inserted into the one fax server. Eg: 2 x BRI 2M = 4 fax lines).

Primary rate boards offering up to 30 lines are also supported.

Refer to the complete range of boards and part numbers listed later in this section.

DTMF routing using analogue

Eicon Networks Analogue Diva Server 4 or 8 port card supports DTMF routing. Similar to voice mail systems that listen to PBX connections for DTMF digits being call forwarded from the PBX to the DTMF capable device. BNS has tested Eicon’s analogue card with msXfax and a PBX system.



S D

C O M P A Q

W A R N IN G

SD

SYSTEMRPS

1x 2x 3x 4x 5x 6x 7x 8x 9x 10x 11x 12x 13x 14x 15x 16x 17x 18x 19x 20x 21x 22x 23x 24x

10BaseT

MODE

CISCO YSTEMSS

®

UTL FDUPSTAT

Catalyst 1900

Ax Bx

100BaseTX

LAN Switch

Exchange Server

msXfax XP fax server using Eicon Networks ISDN basic rate 2 faxline solution

Network layer DDI inbound routing &outbound faxing

Eicon BRI 2M(single basic rate)equal to 2 fax lines

ISDN networks eg: BritiishTelecom Euro ISDN-2 services

Telstra On Ramp 2 etc

1 physical connection = 2 fax lines

S D

C O M P A Q

W A R N IN G

SD

SYSTEMRPS


10BaseT

MODE

CISCO YSTEMSS

®

UTL FDUPSTAT

Catalyst 1900

Ax Bx

100BaseTX

LAN Switch

Exchange Server







2 physical connections = 4 fax lines



S D

C O M P A Q

W A R N IN G

SD

SYSTEMRPS


10BaseT

MODE

CISCO YSTEMSS

®

UTL FDUPSTAT

Catalyst 1900

Ax Bx

100BaseTX

LAN Switch

Exchange Server



Eicon 4BRI 8M(single board with 4

basic rateconnections)

equal to 4 fax lines



4 physical connections = 8 fax lines



2.3.4 Larger installations with direct inbound routing.

Sites wishing to receive faxes directly into Microsoft Exchange Server mailboxes controlled via Active Directory can choose from a number of technologies.

Note: From a design perspective, BNS Group recommends that system architects consider multiple fax servers in large sites. Multiple fax servers offer redundancy. As such, many of the medium scale routing technologies still apply to large sites.

Inbound routing technology

Option Comments

ISDN direct in-dial (DDI also referred to as DID). This a where many numbers can be assigned to an ISDN service for use with inbound routing.

Eicon Networks Diva server boards

1 Primary Rate: PRI 30M (1 primary rate = 30 fax lines)

1 T1 Primary Rate (USA 1 T1 PRI = 24 fax lines)

Refer to the complete range of boards and part numbers listed later in this section.

SD

COMPAQ

WARNING

SD

SYSTEMRPS


10BaseT

MODE

CISCO YSTEMSS

®

UTL FDUPSTAT

Catalyst 1900

Ax Bx

100BaseTX



2.3.5 Which Eicon Diva Server board should I buy?

Universal - Multifunction Communications Platforms Diva Server is a family of robust all-in-one communication adapters offering connectivity via Analog, ISDN Base Rate (BRI) and Primary Rate (PRI) as well as E1/T1 type of interfaces. They are scalable, flexible, and can handle any combination of ISDN, GSM, V.90 analog, fax, and voice calls - making them a perfect choice for building Remote Access, Fax, Unified Messaging, Voice and CTI solutions. On board Digital Signal Processors (DSPs) perform key real-time tasks that would normally cause an excessive burden on the host server. With one dedicated DSP per channel, the Diva Server adapters offer maximum performance. Ranging from 2 to 240 channels per system, Diva Server adapters offer the right choice for all types of organizations

Diva Server BRI Eicon Networks' Diva Server BRI is a high-performance, active PC-based server card that provides digital, analogue and GSM connections over an ISDN line. It is the perfect choice for

corporate servers that need to support high-speed Internet access, remot

Diva Server 4BRI Eicon Networks’ Diva Server 4BRI is a high-performance, active four-port ISDN server card for mid-sized organizations that provides digital, analogue and GSM connections over an ISDN line.

Diva Server PRI/E1-30 Eicon Network’s Diva Server PRI/E1-30 are exceptionally powerful, active server adapters which provide both digital and analog connectivity for up to 30 channels via ISDN Primary Rate

Interface (PRI) or E1 interfaces.

Diva Server PRI/T1-24 Eicon Networks' Diva Server T1/PRI-24 are remarkably powerful, active server adapters which provide both digital and analog connectivity for up to 24 channels via T1 or ISDN Primary Rate

Interface (PRI) standards.

Diva Server Analog-4P/-8P Eicon Networks' Diva Server Analog-4P/-8P are universal communications adapters offering either four or eight concurrent connections over analog trunk interfaces, enabling powerful

enterprise fax, voice and remote access applications.

Diva Server PRI/E1/T1-8 Eicon Networks’ Diva Server PRI/E1/T1-8 telephony adapters offer digital network interfaces selectable for full and fractional E1, T1 or ISDN Primary Rate (PRI) standards with 8-channel Fax

support.

Diva Server PRI/E1/T1-CTI Eicon Networks’ Diva Server PRI/E1/T1-CTI telephony adapters offer E1, T1 or ISDN Primary Rate (PRI) digital network interfaces and provide proven and reliable connectivity with all kinds

of PBX and switch systems.



2.3.6 Can I set up a load test with Eicon boards with loop back cables?

Configuration of a single 4 BRI with 2 cables is described in BNS Group knowledge base article number W000282-070105.

Cable specifications are from Eicon Networks.

2.3.7 Connecting Eicon Diva Server to PBX’s

For the latest information, refer to Eicon Networks documentation at http://www.eicon.com

Q-SIG line specifications are generally used for connection to PBX’s.

2.3.8 PBX least cost routing over IP networks

BNS suggests that extreme care be taken if you consider doing this. You may find that “Remote Fax Abort” messages are reported. Fax protocols are subject to time sensitivity.

2.3.9 Connecting Eicon Diva Server to Cisco IGX WAN Switch

Q-SIG line specifications are generally used for connection to Cisco IGX Switches. However, it is important to force on CRC4 mode.



2.3.10 ISDN Line ordering specifications Basic Rate(s)

If you are configuring 1 or more ISDN Basic Rate services with a range of numbers to allocate to users for their incoming fax numbers you should order the following from your telecommunications provider:

• Point to Point NT1 Interface (this is the standard in countries such as Australia).

• If more than 1 NT1 Interface is required (eg: 4 would be required for use with Eicon’s 4BRI model) then you should make sure that hunt grouping has been specified on your order to your Telco.

2.3.11 30 channel 2MB ISDN Line ordering specifications

• Point to Point NT Interface is the default for connection to public ISDN networks. Australia and other Euro ISDN compatible countries provide these services.

• If you intend to connect to your PBX refer to the previous section regarding Q-SIG. If you’re not sure, contact Eicon technical support.



2.3.12 North American Primary rate Line ordering specifications Primary

rate


• The following is an extract from Eicon Network’s Diva Server manual.



2.3.13 North American channelized T1 connection Line ordering

specifications

• The following is an extract from Eicon Network’s Diva Server manual.




2.4 Dialogic (Eicon Networks) Inc Contacts

Helpful contacts for you. Refer to www.dialogic.com for other regions.



3 Installation pre-requisites & considerations

This guide is designed to provide administrators and technical staff with a comprehensive set of instructions to install, deploy and manage msXfax within an enterprise.

3.1 Pre-requisites of your Exchange 2007 Server

At the time of writing this documentation, BNS tested against Exchange 2007 RTM. Exchange 2007 SP1 was not released at the time this documentation was prepared. Some aspects of this documentation will therefore be different.

3.2 Pre-requisites of your Exchange 2003 Server

Your Exchange 2003 mode of operation can be either Mixed mode or Native mode.

3.2.1 Domain considerations

msXfax can be in any domain or child domain.

It is recommended that your Windows 2003 32 bit fax server computer be a member computer in the same domain as your Exchange server.

By default any user in AD can send faxes.

If you wish to implement granular security controls for sending faxes, use Active Directory security groups.

Using Security Groups to control access to fax servers should be done at domain level. Consideration of nesting security groups across domains to form part of a universal security group is also possible. msXfax will ONLY authenticate security groups (if you decide to implement this level of control) against the domain to which it is a member of. To allow users from another domain access controls to this fax server, those users need to be a member of the “FaxEnabled” security



group in the domain to which msXfax is a member of. Nesting Groups to a Universal Group is also supported which could help provide controls across an enterprise with many domains.

3.2.2 Schema

MsXfax does not extend the schema. Installer permissions do not require Schema Administration rights. Domain

Admin rights is sufficient for most installations. Installation on Windows member servers only requires local administrators group permissions to install msXfax.



3.2.3 Exchange Server Service pack considerations

msXfax will operate in conjunction with an Exchange server(s) which has the following:

Exchange release Service Pack Comments

2003 SP2

2007 SP1

3.2.4 Exchange Server Registry Key addition

Note: Business Fax Contact ‘FAX address space’ is not supported in Exchange 2007. Microsoft does not support it in Exchange 2007. BNS therefore no longer supports FAX Address space.



3.3 Pre-requisites of your fax server

All software and hardware can operate independently of your Exchange Server.

Integration with AD is achieved using Microsoft’s recommended developer programming API’s such as ADSI and ADO. Interaction with Exchange itself is achieved using industry standards SMTP and POP3 protocols.

3.3.1 Fax Server computer

Note: Do not use USB hard disks otherwise the System ID will change and your fax server will not work.

Table 2: Dedicated Fax Server computer specifications

Item Minimum Comments

Motherboard Brand supplier such as DELL Major brand suppliers to ensure compatibility with PCI specifications. Capable of running Windows server.

CPU requirements for up to 16 fax lines

Single CPU Intel® Xeon™ Processor 2.4 Ghz or better. 2GB RAM min

Higher spec processor(s) will perform better for large volumes

CPU requirements over 16 lines to 30 lines

Dual Intel® Xeon™ Processor 3Ghz or better. 2GB RAM min

Higher spec processor(s) will perform better for large volumes

Your fax server computer must be compatible with Windows Server software and:

1. Have sufficient compatible PCI-X slots to accommodate your fax boards

2. PCI-e (PCI Express) boards from Dialogic are now available in some countries, check with Dialogic.

3. Full length slots are required for Primary rate fax cards.



3.3.2 Fax Server software

Table 3: Fax Server software specifications

Software Version/service packs

Mandatory or optional Vendor/Manufacturer

Windows Server 2003

SP2

R2 is supported.

Mandatory Microsoft Corporation

Office 2003

OR

Office 2007

SP1 or SP2

Mandatory msXfax uses Microsoft Office for a number of tasks including: Cover sheet generation and rendering of various attachments to be sent as a Group III fax image.

msXfax msXfax Mandatory BNS Group

Adobe Acrobat (Full product)

7.x 8.x 9.x Optional Adobe Systems Inc. (required to support faxing of PDF attachments)

3.3.3 Direct InBound Fax Routing Utilizing PBX DTMF Tones with selected

Loop-Start Boards

msXfax supports analogue DTMF routing with PABX’s. Version 7.x of msXfax supports Eicon Diva Server analogue fax boards (4 and 8 port versions).

After your board receives DTMF routing information and passes it to msXfax, msXfax performs the same routine of concatenating (msXfax site code with routing digits), performs an ADSI search, selects the recipient’s SMTP email address and submits directly to the Exchange server using SMTP protocols.

The following is the high level sequence that occurs using this technique. The sending fax machine dials the number for the board. PABX rings the board, and plays ringing tone to the sending fax machine. Board answers the call (goes off-hook). PABX senses this, and sends down the last few digits of the dialed number as

DTMF tones (usually the last 3 or 4 digits of the phone number). PABX connects the sending fax machine to the Board. The fax is then received. msXfax collects the DTMF digits, stores them with the received fax in the

received fax queue. msXfax Messenger concatenates its <SiteCode> with the DTMF routing value,

performs ADSI search on Active Directory. msXfax obtains the SMTP address(es) which match the fax routing code.



msXfax constructs an SMTP message to the recipient(s).

3.3.3.1 PABX System Requirements for analogue connections

PABX should provide a standard loop-start line for the Board. (Loop-start is often referred to as "POTS", for Plain Old Telephone Service.)

Be capable of assigning a sub-group of numbers to a single port. When any number within the subgroup is dialed, the call is automatically routed to the same port. Hunt grouping would be required for multiple fax server lines.

Be able to send down the dialed number, or part of the dialed number to the port as DTMF digits after the call has been answered. This is commonly called after-dialing, and is a feature provided for the PABX to communicate with other peripherals, such as voice mail.

Send the first DTMF digit no earlier than 200ms after the call has been answered by the Board. Ideally this parameter would be programmable, or significantly longer than the 200ms required by the Board to allow for delays within the application.

Many systems are capable of sending down a pre-defined number of digits, and stripping off any leading digits. For example, a typical system can be programmed to send down the last 4 digits.

3.3.4 Dialogic Diva Server Boards

MsXfax supports Dialogic Diva server boards. The voice only boards are not supported.



3.4 Inter-operability with other applications

Basically, any application which can send email will work with msXfax.

3.4.1 Finance One from Technology One

Finance One can send SMTP email with msXfax freeform addressing (FAX=) in the memo body. Finance One can produce PDF files (V4) and attach them to the SMTP email.

Finance One runs from a user’s workstation sending the fax over the MAPI session of the user to Microsoft Exchange.

Installation of Adobe Acrobat full product on the fax server is required.

Technology One can be reached via www.technnologyonecorp.com

3.4.2 SAP Connectivity Exchange 2003

At the time of writing this documentation, SAP did not have an Exchange 2003 compliant Connector.

However, SAP version 6.1 and higher, SMTP support is integrated therefore there is no requirement for an Exchange Connector.



3.4.3 Connectivity to Alcatel OmniPCX

Refer to BNS Group web site for further information.

4 Configuring Exchange Server 2007/2010

4.1 Exchange limitations Outlook Business Fax Contacts

Due to omissions in Microsoft Exchange 2007, users can’t send faxes to Business Fax addresses.

BNS reported this to Microsoft November 2007. SRS071029600009 - Winmail.dat sent to external users on 3rd party Fax



Customers upgrading from Exchange 2003 may find that their ‘FAX’ address space on an Exchange SMTP Connector may work when Exchange 2007 is joined to the site. New installations of Exchange 2007 appear not to support this feature which was first included by Microsoft in Exchange 2000 SP2.

Customers should consider using msXfax domain addressing and move away from using Outlook Business Fax Contacts.

4.2 Exchange topology notes

Exchange 2007/2010 sites must have at least 1 server with the Hub Transport Server role configured. A typical installation of Exchange includes the hub transport service role as part of the Exchange installation.

msXfax should be configured to communicate SMTP with the Hub Transport Server and have access to Active Directory global catalogues and DNS. It should also be allowed access to a mailbox using POP3 protocol which is located on the Exchange server.

Customers who wish to place msXfax in a DMZ should contact BNS.



4.3 Set up when msXfax will communicate with a Hub Transport Server role

After you have installed Exchange your standard settings for receive connectors should look like the example below.

4.4 SMTP Communications to Exchange from msXfax

To enable msXfax to communicate with Exchange at the SMTP layer, requires a specific receive connector to be set up.

This can be done via the GUI. In the receive connectors pane select ‘create a new receive connector’



Type the name with custom settings then press next

Choose the default setting as shown above then click next



Enter the IP address START and END address of the msXfax server press OK.

Press next

Press New. Click finish when completed.

Your basic Receive Connector for msXfax to send SMTP messages to Exchange is created. However, additional settings are required.

Select Properties for the connector



Default Authentication should not require any changes as shown above

Select Permissions Groups property tab



for

Set permissions groups to anonymous.

Messages can now be sent using SMTP from msXfax at the IP address defined on

the Receive Connector.

Note: Only SMTP messages originating from the fax server will be received via this connector.



4.5 Create a send connector for msXfax

Open the Exchange Management Console (EMC). Navigate to hub Transport in Organization Configuration Select New Send Connector from the Actions pane

When the Send connector is created you can then edit or add other address spaces to the connector via the Exchange Management Console GUI. You can also edit the smart host IP address as required. Go to the Send Connectors section as shown below and select the Refresh option.



Provide the connector with a name which is appropriate to your organisation. Adding the location and target IP address as part of the name is useful.

Press Next



Click on the Add button

Establish a domain address for faxing. Use your company name eg: bns.fax. The domain must end with .FAX



Select Next.



s

Select Route mail through the following smart hosts



Add the IP address of the fax server. Additional msXfax servers can be added for fault tolerance.

Select Next



Select Next



Add any additional Hub Transport servers if required in your network. Again fault tolerance is important if you have more than one hub transport server in your site.



The SMTP domain address should be added as shown below. Click OK.

Click OK.

4.6 Verify Connection from msXfax to Exchange

From the msXfax console run the SMTP Utility

Select the SETUP



The SMTP Server is your Exchange HUB Transport Server role

The Email address of the sender is ‘Donotreply@yourdomainname’

Name can be anything eg: msXfax Server

Select OK

Proceed to send a test SMTP Email to an Outlook mailbox then verify it arrives.



Put the Outlook recipient’s email address in the TO: field Type a subject and place some text in the message area. Press the ‘Envelope button” to send the message. A message sent dialogue should be displayed.



4.7 msXfax Service Account

A mailbox account for the Messenger service is required to logon to its mailbox using POP3 protocol. The account must have the ‘logon as a service permission’. This permission is automatically granted when the password is specified for the service account.

One msXfax Service Account is required per fax server.



4.7.1 Change msXfax mailbox POP3 protocol settings

Select POP3 for the mailbox

Uncheck protocol defaults and select Text. Press ok Follow other prompts to create the mailbox.



4.7.2 POP3 protocol settings

Enabling POP3 protocol access is performed on the Exchange server which has the Client Access Server role.

From the Exchange Client Access Server open the Exchange Management Shell

The example above shows how to access the Exchange Management Shell



Issue the command

Set-PopSettings –Logintype Plaintextlogin

Go to Services and set the Exchange POP3 service to start automatically. Start the service. If the service is already running it will be necessary to restart the service.

Check the msXfax console to ensure that successful login of the messenger service

to the msXfax mailbox.



5 Configuring Exchange Server 2003

5.1 Configure POP3 virtual server for line wrap

Customers may observe that text inserted into Microsoft Outlook will word wrap at column 67 inside a fax cover sheet.

BNS Group tested Microsoft’s registry change with Microsoft Exchange 2003 service pack 2 and could not get it to work.

Microsoft KB Article 219031 acknowledges the problem is a Microsoft problem.

http://support.microsoft.com/kb/219031/en-us

Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003 To change the message text word-wrap in an Exchange 2000 or Exchange 2003 environment, you must create a new registry key. Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To resolve this problem, follow these steps: 1. Start Registry Editor. 2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\POP3Svc\Parameters 3. On the Edit menu, point to New, and then click DWORD Value. 4. Type Line Length, and then press Enter. 5. Double-click the Line Length subkey, and then click Decimal. 6. In the Value data box, type a value that is greater than 72, and then click OK.

Note The registry key is case-sensitive. Also note that the value must be greater than 72 (decimal). Setting the value too high (range 100,000) may cause the information store to stop because of stack overflow.

7. Quit Registry Editor. 8. For this change to take effect, you must stop and restart the Microsoft Exchange Information Store.

Back to the top

STATUS Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.



5.2 Configure Exchange SMTP Connector

Fax Connector: A standard Microsoft SMTP Connector is required

Open Exchange System Manager to begin.

This SMTP connector communicates with the msXfax Smart Host.

The IP Address of your msXfax Windows fax server is required for the configuration of the Exchange SMTP Connector. (The IP Address was set up when you installed and configured Windows server to be used as your msXfax Fax Server. In our examples it is 10.1.1.3)

Right Click the Connectors folder and choose New Connector, SMTP Connector



On the General properties page, Configure the connector to forward all mail to the Smart Host which is the IP address of your msXfax Windows Server computer. Shown above as [10.1.1.3].



Add a local Bridgehead Server by clicking the Add button on the Bridgehead

Server section, use the local Exchange Server

The General Properties should look as follows:



Click on the Address Space property tab.

Select Add. Select SMTP Provide a domain address for msXfax which ends in .FAX

Typically, customers will use their Location.FAX or CompanyName.FAX or BusinessUnit.FAX



Boston.fax is only valid within your Exchange network thereby providing added security for your enterprise fax network. By limiting the msXfax SMTP Connector scope to a routing group, effectively segments your design. This allows the local msXfax fax server to process ALL messages within the routing group.

It is recommended that you limit the scope to the Routing Group if this fits with your overall messaging design.

Click OK.

5.3 Adding an account in Active Directory for msXfax

From your Exchange Server 2003 server, open Active Directory Users and Computers snap in. Exchange 2007/2010 customers can use the Exchange Management Console to create a user account for msXfax (Refer Exchange 2007/2010 section).

Select View, choose Advanced View. This will allow you to select the options required in this section.



Create a user for msXfax and create an Exchange Mailbox for this account on this Exchange Server.



Customers with more than one location should configure the account name with the site name/location included. The example above shows how Boston can be included in the name and User logon name to allow multiple msXfax servers to co-exist within the enterprise.

Select Next.

Ensure the password does not have to be change, and never expires



Select the check box to Create an Exchange mailbox. Next…

Select Finish



Complete other details as required.

Permissions for this user account are the same as a normal Exchange user. Eg: membership of built-in security group “Domain users”

Set POP3 protocol for the msXfax account should be set as follows:



Select “Provide message body as plain text” Click OK to save the settings.



5.3.1 Customers configuring more than 1 fax server in a site/connector

The following configuration notes will assist customers configuring 2 or more msXfax servers in an Exchange Server location.

A second msXfax user object is required similar to the first one but with a different login account name and other details. The following example will show an example of a second msXfax Exchange user account servicing the second fax server.

msXfax. Boston services the first fax server. msXfax. Boston1 services the second fax server. This second failover fax server

could be used for mainly incoming faxes with a minimal amount of outbound capability to handle failovers from fax server 1.

Both fax servers accept fax submissions from Exchange SMTP Connector configurations.

5.4 Exchange POP3 Service

msXfax uses POP3 protocol to access its mailbox. New installations of Exchange 2003 Server, sets the service to disabled. Upgrades of Exchange 2000 to Exchange 2003 server preserves the POP3 service settings. Please check to see if your service is running.

Set the POP3 service to be automatic by: Select Start, select run, type SERVICES.MSC Scroll down until you see Microsoft Exchange POP3. Right click, Select Properties Select Startup type = Automatic. Run Exchange System Manager



Expand Servers, expand the Exchange Server where the msXfax mailbox is located, expand protocols, expand POP3, Start the Default POP3 virtual server.

5.5 Service Account for msXfax Printing

If you intend to use msXfax printing features it will be necessary to set up 1 msXfax print service.

From Active Directory Users and Computers Add a new account called msXfax- Printing. This account does not require a mailbox.

The msXfax print service account requires permissions to print to printers in the network. Usually, domain users is sufficient.

It will require logon locally to the member server in order for the administrator to add local printer definitions. Once these have been set up the logon locally permission can be removed if necessary.

Note: section 5 describes an additional permission which is performed on the member server to apply permissions of the msXfax print service and the msXfax service accounts to be members of the local administrators group.



6 Preparing your fax server

Now that you have fully prepared your Exchange environment, it is now time to build your fax server.

If you are evaluating msXfax you have 30 days to conduct your evaluation. If you require more time please contact your regional distributor or email [email protected] to obtain an extension.

MsXfax is licensed on an annual subscription basis. Multi-year subscriptions can also be purchased. After you have evaluated msXfax the next step is to purchase your first annual license from your Distributor/Reseller or web site.

This documentation assumes that you have purchased your first annual license agreement to use the software.

6.1 Installation on Windows Server 2003 32 bit

msXfax must be installed on Windows Server 2003 32 bit version.

Optimum performance can be achieved by ensuring that your AD design incorporates a Global Catalog server in the Windows Active Directory Site where your fax server is located. MsXfax uses ADO and ADSI to access your AD service to obtain information about your users.

Perform a typical installation of Windows Server 2003 to be a member server in a domain.

Windows Server 2003 SP2 (R2 with SP2) should be installed on your fax server. Set the event viewer ‘Application log file settings” to overwrite events as needed.



Figure 3: High level diagram Exchange Server & msXfax Fax Server

Com3

Set the IP address of the your fax server to a reserved IP address for use by this server. Do not allow DHCP to assign an address. The IP address in the above example and throughout this guide is 10.1.1.3

Set DNS server IP address to the IP address of your DNS server. In the above example, the Exchange server is also a DNS server and is also a global catalog server. Therefore, the IP address of the DNS server entered into the TCP/IP properties of the fax server is 10.1.1.1.



6.2 Permissions for a member fax server

BNS recommends installation of msXfax on a Windows Server 2003 (32 bit only) member server in the same domain as Microsoft Exchange Server. If you intend to install msXfax on a member server, please set the permissions to allow the msXfax Service and the msXfax Print Service to access the registry and file system. The msXfax Service account is applied to 2 services namely: msXfax Attendant and the msXfax Messenger Service.

Logon to Windows as an Administrator. Select Start, Administrative Tools Select Computer Management

Expand Local Users and Groups Open the Groups folder Double click on Administrators Group Add the msXfax Service account



The above action allows the msXfax service account which is just a standard user in the domain (Domain Users) to have full permissions to the fax server registry and file system.

Also, add the msXfax Print Service account to the Administrators local group. Click OK.

6.3 Permissions required when installing msXfax on a Domain Controller

BNS recommends installation of msXfax on a Windows 2003 (32 bit only) member server in the same domain as Microsoft Exchange Server. However, if you have to install msXfax on a domain controller eg: Small Business Server, you should provide sufficient permissions to allow the msXfax service account full access to the registry and file system. The recommended way is to add the account to the Administrators Group in Active Directory.



6.4 Anti-virus software

msXfax is fully tested with Symantec Anti-Virus. For all anti-virus software products the following directories must be excluded from being scanned:

Exclude these directories from Real time scanning and scheduled scans

Program files\BNS Applications and all sub directories

msXtemp

ETrust from Computer Associates is known to be intrusive on files created by msXfax causing msXfax to fail. Customers using ETrust should take appropriate action to prevent msXfax files and processes from being impacted by ETrust.

This is what to do if you have ETRUST

• Excluding the directory :\program files\BNS Applications

• Exclude msXtemp off the root if it exists

• Disable Real Time scanning

• Perform periodic scans of your hard drives



6.5 Installation of Microsoft Office

If you choose to install Office 2007 please refer to the section below relating to Office 2007. If you choose to install Office 2003 you should use Service Pack 2.

Table 4: msXfax support attachment extension types

Attachment

Extension

Native Office required on fax server Adobe full version

DOC Yes

RTF Yes

BMP Yes

DCX Yes

HTM Yes

HTML Yes

XLW Yes

PCX Yes

PPT Yes

TIF Yes

TXT Yes

WK1 Yes

WK3 Yes

WK4 Yes

WPD Yes

PDF Yes

XLS Yes

JPG or JPEG Yes



Upgrading Office:If you are upgrading your fax server please stop all msXfax services and remove the previous version of Office.

6.5.1 Office 2007 installation section

Perform a Custom installation as follows:

Choose Customize



Select Microsoft Office Document Imaging to “Run from My Computer”

Select the options above for Microsoft Office Document Imaging Select “Install Now” Proceed to the next major section “Configure the Microsoft Office Document

Image Writer”.

6.5.2 Office 2003 installation section




Click on the option Choose advanced customization of applications.



Note: Customers installing msXfax on an Exchange Server should NOT install Outlook on the Exchange Server

Make sure that Office Assistant is removed from the installation. Do not check any of the options on the Setup Completion wizard.



6.6 Configure the Microsoft Office Document Image writer

Logoff the system. Logon as the msXfax Service account

Note: it is important to logon as the msXfax service account to set up the Microsoft Office Document Image writer settings

Select Start Select Printers Right click on the Microsoft Office Document Image Writer printer icon Select properties Select advanced

Select Printing Defaults option (lower left). Select advanced



Select Fine (200 DPI) Do not change the Default folder. Allow the system to determine the setting. Click ok

6.7 Optional: Installation of Adobe Acrobat Software

A standard installation of Adobe Acrobat Full product is required (FULL PRODUCT not the reader only).

Note: If your users intend to fax PDF attachments using Outlook or applications intend to submit PDF files for processing by msXfax, a full version of Adobe Acrobat is required on the fax server.

Installing Adobe Acrobat on the fax server is only required if users wish to send PDF files by fax.

6.7.1 Installing Adobe Acrobat Professional full product

Perform a customized installation selecting the location to install the software. If you require support of Asian languages, these must be selected in a number of places and are part of Adobe’s installation.

After installing Adobe Full product you must run the product, activate and register it.



Logout and log back in as the msXfax Service account user. This is necessary to ensure that the Adobe preferences are set for the user context of the service account

Run Adobe Acrobat Select Help from the menu bar Choose the option “Improvement Program Options”. Select “No”

Settings for Version 8 of Adobe Select the preferences option (EDIT, preferences)

To avoid any popup conflicts it is advisable to set the web update option in Adobe as follows:



Version 9 Adobe automatic update settings

Select Help from the menu bar Select check for updates Apply any updates When updates have been completed and installed, set the preferences to not

update automatically. This is important to prevent interruption to msXfax services.

Select Preferences

Uncheck the option to Automatically check for updates Version 9 Adobe automatic launching of update checker



Disable the launching of this checker because it will create additional overhead each time a PDF file is converted.

Open Adobe Acrobat version 9 Select Edit Select Preferences Uncheck the option called “Check for updates” Logoff as the msXfax service account.



6.8 Installing support for MAX Compress / Winzip

msXfax supports attachments which have been zipped either by the user or by using products such as Max Compress. msXfax will automatically unzip files, render them to fax format at the fax server.

To implement this support: Purchase Winzip version 8 or better.

Make sure that you install the Winzip command-line add-on

Install Winzip fully licensed version on your fax server. Copy the file WZUNZIP.EXE needs to be copied to C:\WINNT\SYSTEM32

directory of the fax server.



7 Installing Eicon Diva Server boards

7.1 Installing Eicon Diva Server board(s)

Install BRI board(s) or a single PRI board in accordance with EICON’s documentation.

Start your computer Windows Server will detect your board(s). Cancel the “Found New Hardware Wizard”. Connect Eicon board(s) to your ISDN line(s).

7.2 Obtaining Eicon Diva Server software

Go to www.eicon.com to download the Eicon Diva Server Software. Download the latest version of Eicon Diva Server software. We suggest that you download the option which includes drivers for all

analogue, Basic Rate and Primary rate boards. Refer to the screen example below.



Download DsAllM.exe (12MB+). Save the file to your fax server hard drive. Run the self extracting file DsAllM.exe



7.3 Installing the Eicon Diva Server software

7.3.1 Customers upgrading from Eicon Diva Server version 6.x

Customers with version 6.x of Eicon Diva Server software should follow these instructions:

Run the program SETUP.EXE from the directory where you ran the self extracting EXE.

Select Upgrade and follow the screen prompts. A reboot is required. Login with Domain Admin rights once again. Select Start, Programs, Diva Server for Windows Software Run the Diva Server Configuration Wizard Proceed to the section below “Diva Server Configuration Wizard

7.3.2 New Installations of Eicon Diva Server software

Run the program SETUP.EXE from the directory where you ran the self extracting EXE. This will launch the Diva Server Configuration Wizard in addition to installing the software. Proceed to next section below.

7.3.3 Diva Server Configuration Wizard



Note: Australian customers should select Europe/other countries as shown above.

Analogue cards: If you are installing an Eicon Diva Server analogue card the analogue switch type is presented as shown above. If your country is not listed, choose the default = Europe.



To improve security, select the options as shown above.

Only Diva Server API/CAPI should be selected. This improves security. If you wish to protect the server from being reconfigured select the password

option and assign a password. Note: this should be placed in a secure location.



Select Next

If this server is to be used only for outgoing fax services you may change the option to not accept incoming calls.

Select Next



Select Next Wizard should now complete to the finish. You should now restart your server.

7.4 Configuring a Diva Server ISDN adapter

Select Start, Programs, Diva Server Configuration Manager. You should see a screen similar to the one below with just the CAPI Services

linked to your adapter(s).

TIP! Select View, Advanced to see additional fields in the configuration program.



The example screen above is for a customer who has 4 basic rate services connected to their fax server. It is recommended that CAPI configurations be allowed to answer calls a number of channels which is the same number of receive circuits configured in msXfax. msXfax sees the CAPI service as one logical pool. msXfax allows you to set how many circuits will be used for transmission and how many for reception.



For lines 1 and 2 this example shows how to prevent incoming calls from being answered on those interfaces. Call answering = No calls.

Line specification example for a system connected to point to multipoint system (No Direct Dial Inwards service).



Line specification example for a system connected to point to point Direct Dial Inwards service

Tip

If you need to connect Services to the Adapter or Lines to the Adapter perform the following:

1. Right click on say Services and click copy.

2. Right click on your adapter (eg: 4BRI card) then Right click Connect.

When you have finished configuring the Eicon Adapters, lines and services: Select File, Save As. Save your configuration file with an appropriate name eg: EICONISDN.CFG. Select File, Activate. A message will be displayed stating that the configuration update is in progress. You should now see a message “The configuration was updated successfully”. A restart the server will now be necessary.



7.5 Configuring a Diva Server Pri adapter

PRI configuration is easy. Verify that your installation looks similar to the example above.

Australia can use Europe/other countries, Euro ISDN for both Telstra and Optus services.



Select the line which joins CAPI and the PRI adapter. Set call answering to suit your needs.



7.6 Configuring a Diva Server Analogue adapter

Select Start, Programs, Diva Server Configuration Manager. You should see a screen similar to the one below with just the CAPI Services

linked to your adapter(s).

TIP! Select View, Advanced to see additional fields in the configuration program.

The example screen above is for a customer who has an analogue telephone lines connected to their fax server. It is recommended that CAPI configurations be allowed to answer calls a number of channels which is the same number of receive circuits configured in msXfax. msXfax sees the CAPI service as one logical pool. msXfax allows you to set how many circuits will be used for transmission and how many for reception.



If you require any of the telephone lines to accept incoming calls you must select Call Answering = All Calls.

Note: Connect your incoming fax lines to the high order ports eg: on a 4 line analogue fax board, connect the incoming fax lines to port say 3 & 4.

msXfax will transmit from low order port numbers. Therefore, to have 2 fax lines for transmission and 2 for reception, connect transmitting fax lines to port 1 & 2 and incoming fax lines to port 3 & 4.



For standard analogue services, the default above should be satisfactory in most instances.



7.6.1 Inbound routing using DTMF routing from PABX systems

If you have a PABX capable of sending DTMF tones representing a series of digits please refer to the next section.

To activate DTMF collection, turn DTMF collection ‘On’. Note: this is only required when inbound routing technology is limited to DTMF digits from PABX systems.

7.7 Saving your configuration

Select File, Save As. Save your configuration file with an appropriate name eg: EICONISDN.CFG. Select File, Activate. A message will be displayed stating that the configuration update is in progress. You should now see a message “The configuration was updated successfully”. A restart the server will now be necessary.



7.8 Testing a Diva Server adapter

If you do not have the Diva Server API/CAPI service installed, the Line Check utility will run instead of the Line Test Tool. The Diva Server Line Test tool offers signicantly greater functionality than the previous Line Check utility, to assist in troubleshooting a variety of issues.

7.8.1 Test if your line is working

Click on the Line Check tab Select the adapter that you want to test from the drop-down Device list, Click 'Start' to run a Line check.

If the Line Check utility reports an error, verify that:

• Your cabling is connected correctly. • Your ISDN switch type, network type, ISDN numbers, and SPIDs (if required)

are correct.



• Your Diva Server adapter is not conflicting with any other hardware • Your telco company is not experiencing any problems.

If you see “Line check passed”. If the line check fails, check with your telecommunications company to

determine the correct settings.

TIP! If you have multiple Basic rate Eicon Boards in your server we recommend that you use a permanent marking pen and write the serial number (available from the configurator and the line test utility) on the metal facia of the board. It is also recommended that you label port 1 being the port nearest the top of the board.



8 Dialogic Fax over IP solutions

For more information contact BNS Group technical support via the contact support option at www.bnsgroup.com.au .



9 Upgrading your msXfax software

9.1 Special notes for existing customers

Releases of msXfax prior to release 6.2.2 allowed the installation files to be installed on any drive letter but the actual msXfax installation did not allow installation on any other drive letter other than C.

Customers who installed on C drive but who now wish to install on D drive should:

Note all parameter settings and copy any files such as cover sheets to a safe location.

Remove msXfax software Remove msXfax Installation files Proceed to install a fresh copy on any local disk drive in the next chapter.

9.2 Upgrading to release 7.0 and above

Version 7.0 supports an upgrade-in-place for msXfax versions 6.2.1+ or greater.

9.3 Upgrade procedure for non Exchange environments

Non Exchange environments means:

a) Exchange is not communicating with msXfax using SMTP Connectors and;

b) No Active Directory (AD) lookups are performed or;

c) The customer does not have Exchange/AD to reference.

Examples of this include:

1. msXfax installation in a DMZ.

2. msXfax installation in an environment such as a Lotus Notes, Unix etc.



9.3.1 Before you start the upgrade

Make a list of which msXfax XP services are currently disabled. Stop msXfax services. Backup your fax server

9.3.2 Upgrade Eicon Drivers

To check which version you have: • Start, Programs, Diva Server for Windows, Diva Server Configuration

Manager. • Select Help, About. • The version number is displayed in the About box.

If necessary, upgrade to latest Eicon Diva Server drivers (8.3 as at Nov 2007). Refer to msXfax installation guide. It is the same procedure as installing the original drivers.

A reboot may be required.

9.3.3 Upgrade msXfax installation files

Determine which drive letter the original installation files were installed. Navigate in Windows explorer to Program files\BNS Applications\Fax Server

Installation Files. Note the driver letter and location. Download the INSTALLMSX.EXE file and copy it to any location on your fax

server. Run the INSTALLMSX.EXE to refresh your installation files. Be sure to replace

the existing files by specifying the current drive letter eg: E:\Program files\BNS Applications\Fax Server Installation Files

9.3.4 Upgrade msXfax with the MSXSETUP.EXE

Close all program windows including the msXfax console program. Run MSXSETUP.EXE located in \Program files\BNS Applications\Fax Server

Installation Files\Fax Software



Press Continue Click next a few times, accept or reject the end user licence agreement Click next on the evaluation notice (make sure the check box is unchecked).

Check that the installation Destination Folder is correct. Then select Next. Make sure that the Determine which drive letter the original installation files

were installed. Site Identifier: verify details have been migrated correctly and press NEXT.



Exchange Integration: NOTE: Non Exchange Environments, DMZ environments and all other situations where the local database is used must UNCHECK both check boxes which are checked by default during an upgrade.

All subsequent screens should correctly pickup all previous configuration information. Do not re-type passwords or any other information. Just select Next and allow msXfax to upgrade the system.

Click FINISH Click CANCEL not to reboot the system Run Services.msc to review all services. Scroll down to the msXfax XP services. Set the selected services which were previously DISABLED back to DISABLED. Reboot your system Check all functions of your system.



10 Initial Installation Files

10.1 Installing the installation files

Downloading msXfax software allows you to trial the software and turn it into a fully licensed product after purchasing a subscription license.

By downloading the software a file called “INSTALLMSX.EXE” is downloaded from BNS Group’s Internet web site.

Copy the file INSTALLMSX.EXE to your Fax Server’s local hard drive. Run INSTALLMSX.EXE Follow the wizard and select a local hard drive to install. Note: if you are

upgrading your system, please select the existing location where your installation files were originally installed.

Program INSTALLMSX.EXE installs 2 major components on your fax servers local hard drive:

• “Fax Documentation”—This installation documentation and any other technical notes.

• “Fax Software”—Cover Page Setup and Fax Server Setup programs.



11 Installing msXfax on your Exchange server

BNS Group does NOT support installation of msXfax on your Exchange Server.



12 Installing msXfax

12.1.1 Login to the Domain & Permissions

If your fax server is a Windows member server you may login as a user of the local administrators group or as a domain admin.

If your fax server is a Windows domain controller you should login as a Domain Administrator.

It is recommended that your fax server computer account be in the same domain as your Exchange server computer account.

With the exception of the msXfax Print Service, Messenger Service and msXfax System Attendant all other msXfax services run in the local system context. msXfax uses POP3 protocol to access its Exchange mailbox using credentials supplied in the setup/configuration of msXfax. Therefore, msXfax requires no special permissions to access your Exchange server over and above the POP3 credentials to access the msXfax Messenger mailbox.

Active Directory services interfaces built into Windows Server provide the transport for msXfax to access directory resources.

Therefore, you should create 2 service accounts – for example:

msXfax (Service account used by the Messenger and Attendant services) msXfax-Printing (Service account used by msXfax Print Service)

In a large network it may be necessary to establish accounts for each site – for example:

msXfax-Boston (Service account used by the Messenger and Attendant services) msXfax-Boston-Printing (Service account used by msXfax Print Service)

12.1.2 Run the Setup program

The initial installation setup program installs: documentation and msXfax Setup software.

If you’re upgrading you should have already installed the msXfax installation files (see previous chapter). The procedure is the same to upgrade as it is to install a fresh copy. In most instances, msXfax setup software will examine existing software settings and preserve them during the upgrade.

In previous sections you installed and tested hardware components, configured Exchange server in preparation for installation of msXfax on your Windows fax server.

Now it is time to install msXfax on your fax server.



Navigate to Program Files\BNS Applications\Fax Server Installation Files\Fax Software

Run the msXfax Install Program, msxsetup.exe



If you are performing an upgrade the following screen will be displayed

If you are performing an upgrade the following screen will be displayed

Accept or Reject the license agreement, click Next



Click Next

Customers can evaluate msXfax without an Eicon Diva Server fax card by clicking the checkbox on the above setup screen.



Check that the destination folder is the same as the current installation if you are performing an upgrade

The Exchange Site code is used by msXfax to qualify DID/DDI routing information in Active Directory. For example: it is possible that DID fax extension 5555 in your Boston PBX could also exist in your London office. Therefore, to distinguish the intended recipient in Active Directory, msXfax fax server(s) in a particular site are configured to concatenate the Site code with the numeric DID value to ensure that



inbound faxes are routed to the Active Directory object which matches both the Site code and the DID value. In a global enterprise this is essential.

Recommendation for sites in Countries such as Australia. If your organization does not extend beyond your country your ISDN number range will be unique. Therefore, using “AUS” or “DDI” or “DID” or “FAX” as the Exchange Site code is recommended. Reason: it is more meaningful in that context when inserting routing information into Active Directory.

The msXfax Site Code is used to uniquely identify inbound routing information within a global enterprise directory. The msXfax Site code is pre-pended to the actual DID/DDI value received by the fax server to form a unique string of characters to search Active Directory.

Recommendation for customers who have designed their Active Directory and Exchange networks based on Geographic location: • Insert a meaningful msXfax Site Code being the general location eg: AUS or

Boston or USA etc. • Supply the IP address of one your Exchange Servers (or SMTP Servers)

servicing the Site. DNS entries can also be used.

Special Note: Customers who have Exchange Server deployed should leave both of these options checked and click next.



The POP3 Host IP address: is the IP address of the Exchange server where you created the msXfax mailbox. POP3 Host Port Number is usually port 110.

POP3 Mailbox ID is the Account login name for the msXfax mailbox. POP3 password is the password you set in Active Directory for the msXfax

mailbox. Messenger Email Address is the SMTP email address of the msXfax mailbox..

This is the SMTP address of the msXfax mailbox you created. Refer to the Email



addresses property sheet and the general property sheet of the the msXfax mailbox. Refer to the following example.



Select the Country code settings



Specify the domain\account and password for use by the msXfax Messenger service. Permissions for this account were previously described in this documentation. Permissions required for the messenger service are the same as a normal user account. However, any group policy your organization might apply could impact on the exact permissions that you should implement.

If your installation must print incoming faxes select the check box provided.

Permissions required for the print service are the same as a normal user account. Choose the Program Manager group to place shortcuts into, click Next to

continue



Click Next to continue installation, msXfax Setup will now proceed to install files When a message box appears saying you have successfully installed msXfax.

Click Finish to complete the installation. A message stating that your system needs to be rebooted to complete installation,

click OK. Your system will reboot and msXfax will be successfully installed. When the system restarts, go to SERVICES.MSC, scroll down to the msXfax

services which have the msXfax service account specified. Enter the password again and this will cause the permission ‘Log on as a Service’ to be granted.

12.1.3 msXfax Print Service

msXfax offers inbound printing features.

If your installation does not intend to use printing please ignore all instructions relating to the msXfax print service.

If your installation requires printing please follow these instructions: Run a program Services.msc Scroll down until you see the msXfax Print Server Right click properties Select Log on property tab Select This account



Click Browse to select the Service Account you created earlier Eg: msXprint

It may be necessary to re-enter the password for the account Verify the password for the account Click OK. Logon as a service right may appear if the account you have used has not yet

been granted the right. Click OK. STOP the msXfax Print Service. DO NOT START the service. Press the refresh button (green arrowed button)

on the Service MMC. msXfax’s System Attendant should automatically restart the service having detected that it was not running.

Logoff the fax server and logon as the msXfax Printing service account. Add printers that the print service is required to print to.

It is important to do this when logged on as the print service account because it creates the correct permissions and printer references.

That completes the installation of the Print Service.



13 msXfax configuration overview

Note: All administration is performed via msXfax’s Console

13.1 Permissions & Security

msXfax uses the underlying services provided by ADSI/LDAP. Enterprise customers running global networks generally delegate control of AD to selected site administrators many of whom are NOT members of the Domain Administrators Group.

msXfax has been designed to consider enterprise global security permissions allowing selected operations to be conducted at a local computer level (ie: Login as user who had been granted local Administrator rights to the member server as opposed to a Domain Administrator login).



14 msXfax Configuration

14.1 msXfax Console

To load the msXfax Console, select Start, Programs, BNS Applications, msXfax, msXfax Console.

The first time msXfax is started you are allowed 30 days to evaluate the software. At any time you can activate the software from evaluation mode to production. Once it is activated, the expiration date of your license is displayed on the main msXfax console. During the evaluation period, each fax transmitted by msXfax has an evaluation statement included at the top of each fax page (called the fax header). When the product is activated in a production environment, the fax header comprises details such as recipient name.

14.2 Configuring Dialogic (Eicon) boards

msXfax and Eicon Networks Diva Server boards offer a flexible, scalable and easy to configure solution.

Open Eicon Fax server Double click Fax Devices

Expand Fax Lines



Double click on CAPI Devices The CSID (Communication Subscriber ID) for All Channels is the value which

msXfax will exchange with the remote fax machine in the fax call setup. CSID usually contains your main fax line number for identification purposes by the receiver.

Total CAPI channels available represents the number of B channels (for ISDN) or analogue lines which are configured between the CAPI Pool Service and your Eicon adapter(s).

You need to set how many of the fax lines will be used for transmitting and the number for receiving faxes.

Receive circuits represents the number of fax lines which can be received.

Receive Circuits must match the total number of Eicon Interfaces configured to Answer incoming calls. It is important that your Eicon adapters are configured to answer calls and that the total number of lines set to answer should be equal to the number specified in msXfax.

Archive period refers to the msXfax events recorded in the Statistics table of the msXfax database.

Archiving of statistics is performed via the Fax Server statistics option by clicking the checkbox “Purge & Archive Statistics” then pressing “Export to CSV”.



msXfax has now been configured to communicate with your Eicon Diva Server board.

14.2.1 Configuration option for analogue Eicon Diva Server

Customers using Eicon analogue boards can map their analogue line to a DDI number. This is recommended so that Direct Dial Inwards routing can be used.



Restart Eicon Service: It is important that you now restart the Eicon Fax Service.



14.3 msXfax General Configuration

14.3.1 Licensing

To fully license your product, you are required to supply a value called “System ID” to your reseller who in turn obtains a license key for the subscription period eg: 12 months.

The System ID is nothing more than a value generated which is tied to the configuration of your hardware. It does not identify anything about your organization or credentials or any other elements which would breach security. It is only a means of generating a key pair (based on the hardware platform) to avoid piracy of BNS Group software.

Note: It is also possible to stop and start all the msXfax services via the console.

Left click on the + symbol to open respective folders. Double click on the options which are expanded. Each option is called a Node.

There is a note on the main console screen to remind you to double click to open the function.



Commonly used functions are now included Right Click on the msXfax Folder in the Console Root, and select Update License

A screen similar to the following is displayed.

The Notes field can be used for your records to record additional information such as: who you purchased the software from, your purchase order number and other relevant details. This will be very useful in the future.

If you purchased your software via the Internet, enter your purchase details for future reference.

If you purchased msXfax via the Internet you can electronically request an Activation code. If your fax server is connected to the Internet, press the hyperlink “Request License Key” http://www.bnsgroup.com/bns/license.asp?a=products&next=chooseprod

Alternatively, visit www.bnsgroup.com.au to request a license key (Select Product Info, “Registration and Licensing”) . License keys typically take 24 hours to clear our verification system. Please do not leave it until the last day or so before you activate the product.

If you purchased msXfax from a reseller, you should advise your reseller of your System ID and allow your reseller to request an activation code on your behalf.



Activation codes are not issued until payment has been received in full by BNS Group.

Please note: Activation keys are sent to the registered customer via email only after payment has been received in full.

Upon receipt of the license key, enter it into the field called License key and click on the Activate Licence button.



14.4 msXfax Configuration in more detail

msXfax’s setup program requests as much information as possible to pre-configure the required elements of your fax server and its interaction with Exchange/Active Directory.

14.4.1 msXfax System Attendant

The msXfax XP system attendant is responsible for overseeing and managing various services. If the system attendant detects a service not running, it will automatically start the service.

msXfax’s console allows you to manage different aspects of each service or function.

Double click Properties



The properties of the System Attendant shows basic configuration elements. The default maximum alerts should be set to 10. Queue depths represent the number of items in the queue at any one time. If

these thresholds are reached a warning message is delivered to the email address(es). Do not change the settings unless you have good reason to do so.

Adjust the Free Disk space parameters as required.

14.4.2 msXfax Routing Engine

msXfax Routing Engine is a powerful SMTP smart host included with the msXfax package, which acts specifically as a router for FAX and other eligible address space items from Exchange. Configure the Routing Engine properties as follows:

These values were configured automatically based on the values you supplied during msXfax’s setup program.

Make sure that “Allow Detail Logging” is turned on.

Logging items to the Windows Event log and detailed logging should be used for troubleshooting or when event log information is used to feed into network management products.



14.4.2.1 msXfax Routing Engine Logs

To show some activity in the Routing Engine perform the following from the Fax Server:

Run Outlook rich client. (You may need to create an Outlook profile to access your mailbox.). Alternatively, use an existing desktop Outlook client to send a message

Refer to the following examples to create an Outlook Contact. Enter a fax number for this test user which is a fax number of your fax machine in your office. This will allow verify that the fax transmission worked successfully.



Your test fax should look similar to the one above. Press send and then observe the Routing Engine being contacted by Exchange

Server. In this example the server w2ks1 in domain Americas.test.com routed the message to msXfax.

To view the dialogue between Exchange and msXfax you can view the logs by double clicking on the Logs option above.

The above log file shows contact made from Exchange SMTP Connector to msXfax routing engine.

14.4.3 msXfax Messenger

The msXfax messenger handles core processing and management of fax messages.\



Note: The Filter property tab effective release 7.6 has been replaced by the Australian Government Email Protective marking standards. Customers who must comply with the standard must purchase and msXfax enhanced security edition.

From the main msXfax Console, open the msXfax Messenger folder Various property sheets are displayed.

Most of these settings should not be altered once they are set up. We recommend that you leave these settings as they are until you examine the security recommendations later in this documentation.

Global Pass Code is optional for additional security when used with freeform addressing. If you set the Global Pass Code to “Microsoft”, users will need to include PASSCODE#Microsoft in the memo of their Outlook fax message.

Some users nowadays use FAX# in their autosignatures which could cause forwarded emails to fax to be copied to recipients not intended to be copied. msXfax allows the freeform string to be defined by your organization. Examples could include: FAX@, FAX=, msxfax# or fax% or any other keyword you feel is appropriate. BNS recommend that you use FAX= as the freeform address

Enable Enotify-AI support – this turns on options in the Global Settings. Enable Dialling rules and Least Cost Routing this turns on options in the Global

Settings. Customers with specific requirements for dialling rules should only use this option. For example: customers in the USA can use dialling rules to define a number of local area codes and specific rules required. Australia’s default dialling rules will be activated once the option is set.



The Host IP address should be the IP address or DNS name of your Exchange Server

The mailbox ID for Messenger is the Active Directory Account login name Password is the Active Directory password for that account. Email address is the SMTP address of the Active Directory account used by the

msXfax Messenger. POP3 Host Port is the TCP/IP port number configured on your Exchange

Server’s Default POP3 Virtual Server.

This is the IP address or DNS name of your Exchange Server.



This is the disclaimer which msXfax will automatically include on automatic cover sheets. The default option is OFF. BNS recommends that you leave this option turned off and modify your cover sheets (example one is msXcover.rtf), insert your standard organization disclaimer using Microsoft Word to edit your cover sheet(s). The concept of an enterprise wide disclaimer fax cover sheet is very popular. A user’s auto signature in Outlook defines who they are and their contact details. Just like regular email messages, the auto signature is included in the message body of the cover sheet taken from their Outlook message.

Diagnostic logging is useful if you want to fully understand all the activity that msXfax is performing.

Note: If you want to log events to the Windows Event log, make sure that you have set the “overwrite events as needed” in the Event Viewer.



14.4.4 msXfax Dispatcher & Fax Queues

The msXfax Dispatcher is responsible for Fax Queue management, dispatching eligible faxes to lower layer device drivers for transmission. The Dispatcher plays a role in the management of inbound faxes.

Access to fax queues via the msXfax console is achieved from the dispatcher folder.

Open Dispatcher folder Double click on the Fax Queues. Double click on the queue you are interested in eg: “Awaiting a Free Line”. If you want to view a fax—double click on the entry in the queue. It is possible to expand this window to full size. Sorting on columns is achieved by clicking on the column heading. The only

exception is POP3 which is a linear view of the mailbox.



Hints: If you are trouble shooting your fax server the following hints may help:

Stop system attendant—this will prevent this process from re-starting other tasks Stop Routing engine—this will prevent additional messages being received from

Exchange SMTP Connector while you are resolving any issues. Stop Messenger—this will prevent additional messages being received from

Exchange POP3 mailbox while you are resolving any issues. Use the “Move all faxes to the suspense queue” check box to highlight and move

all the items to the suspense queue until you resolve the issues. This can be useful to avoid too many NDR’s in the case of a telephony failure or other temporary problem.



15 Send a test fax and some useful utilities

msXfax has a large button to allow you to quickly send a test fax. Select Send Test Fax Enter the fax number you want to send to It is possible to generate many faxes by increasing the number from 1 using the

up arrow. A sample fax is sent. By increasing the Transmission simply adds additional

pages to the fax to increase the transmission time.

15.1 msXfax Utilities

msXfax comes packed with lots of useful tools including an SMTP send utility and a POP3 client utility.

Both of these tools can be used from your fax server if there is a problem trying to send from your fax server to Exchange users or when attempting to read messages using POP3 protocol from the Exchange Mailbox reserved for msXfax’s Messenger service.



Click on the setup option as shown above and set the values that correspond to your Exchange Server.

Click OK.



Click on the envelope to send your message Go into your Outlook Email and verify that you got the message.

A similar utility exists should there be a need to verify that POP3 protocol is working to your Exchange server.

15.1.1 Abort Broadcast

Use this option only on a broadcast server only when you wish to abort a broadcast currently in progress.



16 Active Directory Integration

16.1 Introduction

msXfax uses existing fields in Active Directory (AD) to store specific information required for outbound and inbound fax controls and routing.

16.1.1 Quick setup all users can send a fax without automatic cover sheets

Allowing all users to send a fax from Word would be satisfactory for some organizations; whereas, other organizations may want each user to be explicitly allowed to send faxes via Active Directory.

To allow all users to send faxes without expressly setting their options in AD: Expand Global Fax Settings Double click Global Fax Server Permissions and cover page settings

By setting “Allow all Users to Fax” will allow users in Active Directory or in msXfax’s local database to send a fax.

msXfax also allows specific users to be nominated to send a fax using security group membership.

FAXENABLED is legacy support only.



16.1.2 Quick setup all users can send a common automatic cover sheet

Some organizations want all their users to be able to send a fax without any restrictions using a single automatic cover page.

An understanding of the cover page section is necessary to fully appreciate the following points. Please read the cover page section to obtain a basic understanding of how it works.

If you are a small company you may have only a few variables in your cover page and you may simply place your company name and logo in the cover page. This is actually quite efficient because it reduces the number of Active Directory queries.

General Page explained:

These values are used when assembling an automatic cover page if the values are not available from Active Directory.



Address Page explained:

These values are used when assembling an automatic cover page if the values are not available from Active Directory.

Most medium to large sized enterprise customers will always use Active Directory therefore the above fields are not used.



This is where an enterprise wide cover page can be defined. Nowadays, this is used as an enterprise wide disclaimer for all outgoing fax correspondence.



16.1.3 Global cover sheet based on sender’s email address

Organizations which acquire different companies from time to time still retain their identity and their e-mail addresses.

msXfax allows automatic generation of disclaimer/cover sheets based on the sender’s email domain name.

The domain name is determined as the first string after the @ symbol in the email address of the sender.

Examples

Company name Email address Cover sheet which will be used

ABC Corporation @ABC.NET.AU ABC.RTF or ABC.TIFF

ZYX Insurance Group @XYZ.COM XYZ.RTF or AYZ.TIFF

Sales Division @Sales.DEF.GOV SALES.RTF or SALES.TIFF

A user or application which supplies CS# keyword in the message body (memo) will override any global settings.



16.1.4 Other global default options

Global inbound and outbound settings can be implemented for example: • Ability to print all sent/received faxes • Ability to save all sent/received faxes to a directory

Customers can use Active Directory to determine what action is to be taken for a specific user.



16.2 Fax Server Access Controls

Note: The default installation is Allow all Users to Fax. If you accept this default there is no need to do anything further to Active Directory.

Prior to release 7.0 of msXfax an administrator could only nominate selected users to send as a fax using the Notes field keyword called [FaxEnabled]. This is fully described in the next section.

Version 7.0 of msXfax introduced a new method of allowing administrators to nominate who is authorized to send a fax. This method uses group membership from Active Directory as follows:

Customers who elect to use Group Membership to control access to send faxes and have multiple domains, must take care to understand entire solution and how it fits into a global enterprise.



16.2.1 Adding an OU to the local domain where the fax server accesses AD

Dffsd

The example above shows a child domain Americas.test.com which is where the fax server is located.

To create the OU to control for msXfax perform the following Run Active Users and Computers Right click on the Domain icon Select New, Organizational Unit.



BNS decided to promote this OU naming convention to allow other 3rd party vendors and in-house programming staff to use a common OU for this type of information. msXmms (BNS Group’s SMS and MMS server for Microsoft Exchange) is managed in another OU underneath Application Controls with security groups for SMS Enabled and MMS Enabled.

Now create an OU underneath Application Controls called msXfax

Now create a Group to control access for msXfax fax servers in this domain



Fd

Create the group name Fax Enabled. Make sure there is a space between Fax and Enabled.

A universal group will provide more flexibility for inclusion of users or nested groups from other domains.



Dfd

Do not mail enable the security group unless you have a good reason to do so. Now you can add users to this Group who are authorised to send a fax. From msXfax Console’s Global Settings, scroll along from the Fax Server Access

tab to the right until you see the Active Directory Tab.



Change the DC=child, DC=parentdomain,DC=com to reflect what domain this fax server is located in.

As can be seen from the above example, we have a domain called Americas.test.com.

In the example shown above Americas.test.com you would change the value to:



Click save these values. Double click again on Global Fax Server Permissions, navigate back to the Active

Directory tab. Click the Check Group button to verify that msXfax can connect to Active

Directory and read the Group information.

Note: If your Active Directory Domain name is only a parent root domain eg: TEST.COM then you would change the value to the example shown below

That completes setting up msXfax Fax Server Access using Security Groups. If you completed this section because you prefer to use Security Groups to control access to who can send faxes; you can proceed to review the next section.

Note: the next section describes a [FaxEnabled] keyword to control access. This keyword is not required if you have elected to use Security Groups. It is useful to read the next section so you are aware of the other keywords which can be used in the notes field.



16.3 Keywords & authorization to send a fax using Notes Field

Using the Notes field in AD is not recommended for determining whether or not users can send faxes.

This section outlines the individual level keyword settings in AD to expand your understanding of how msXfax harnesses the power of AD.



The Notes field is used to instruct msXfax to: authorize, account for, route, save, print and log faxes.

msXfax uses the Notes field to:

1. To avoid extending your AD schema and;

2. To allow additional keywords to be added in the future without compromising your directory service.

The fax number field can be used for inbound DID/DDI routing – we’ll look at that in just a moment.



All msXfax keywords are enclosed in square brackets within the Notes field.

The following table summarizes the keywords above and their usage:

Table 5: msXfax keywords and their usage

Keyword Function Comments

Note: if you are using Eicon analogue cards, use the channel to DDI mapping capability. This allows a channel to be presented as a DDI value. DDI routing can then occur on faxes coming in on a certain channel for analogue systems

Channel based routing.

[InPrinter:1|Printer name] Received faxes on fax line 1 will be printed on the printer Eg: [InPrinter:1|\\fileserver1\HPLaserJ]

[InDMI:1|Directory location]

Received faxes on fax line 1 will be stored in the directory specified. DMI is short for Document Management Interface. Faxes can be automatically profiled into any document management system which can import from an external directory.

Eg: [InDMI:1|\\Fileserver1\DMI]

[OutDMI:Directory location]

Outbound faxes will be stored in the directory specified. DMI is short for Document Management Interface. Faxes sent from your organization can be automatically profiled into any document management system which can import from an external directory.

Eg: [OutDMI:C:\FAXESOUT]

[CS:Coversheetfilename] If this keyword is present, an automatic cover sheet will be sent each time this user sends a fax.

Eg: [CS:SALES.RTF]

The coversheets must be stored in the local path Program Files\BNS Applications\msXfax\Cover Sheets

[CC:<costcenter] Each fax sent by this user will be recorded in a database for reporting and input to an accounting system for internal billing purposes.

Eg: [CC:Sales] = sales cost center.

Another common example follows:



The above example shows that this user has a DID (read also DDI/DTMF) Fax number 7789 (embedded in the Fax Field) qualified with the Boston site code.

The user’s full fax number is not used by msXfax, only the routing portion to the right hand side of the : (colon) is used.

In addition to searching the Notes field for [DDI:Boston7789] or [DID:Boston7789] msXfax will also perform a filtered ADSI query on the fax number field in AD.

Filtered ADSI queries perform efficient searches against AD.

This user will have cover sheet business_unit1_cover.rtf attached automatically each time they send a fax. If an employee moves to another department on a temporary basis, it is a simple matter of updating AD with their temporary cover sheet. Users can override cover sheet settings by attaching a cover sheet in the message.

Charge codes: Legal firms can enter charge codes in each fax message sent. This is covered in the user documentation. Charge codes are not to be confused with cost centers. A cost center is an internal



billing code whereas a charge code is used by some orgnanizations to bill clients.

16.3.1 Routing to Distribution Groups

The above example shows how an AD Distribution Group containing multiple members can be set up to use msXfax to route incoming faxes based on all the same criteria as previously discussed earlier in this chapter.

Inbound DID values can be assigned to the Notes field together with Document Management Interfaces etc.

Organizations have the capability with msXfax to collectively route incoming faxes to:

Users Distribution Groups Contacts Other email addresses Printers Document Management or other applications

Example: Distribution group based routing (Inbound fax) with output to a network share.

• In this example “Faxserver1” is the ‘Site code’. A site code is generally applicable to a Country to ensure global uniqueness.

• 12345678 is the DDI value presented from the telephone network.



When using the notes field for routing controls, it is important to include the option “search notes field for DDI” in the Active Directory tab of the fax server defaults.

Note: if the connection to network share fails, msxfax will route the fax to the associated email address for the ddi (if any) and if that fails then it will route it to the configured default route/administrator.



16.4 Enterprise security & controls

In well designed, secure Active Directory enterprises, designers and security control officers require local IT staff to conduct day to day management of services including:

• Management of users • Management of printers • Management of groups • Management of exchange mailboxes

msXfax when installed on a Windows member server it can only be administered by members of the local Administrators Group.

If the person managing msXfax is not a member of the Administrators group or Domain admins group, add them to the Administrators group as follows:

Administrative Tools Computer Management Local Users and Groups Select Administrators Group



Select the user or domain global security group to be included in the local Administrators group.

Using the above approach will provide access to msXfax’s functions. However, some network security controllers do not allow local IT staff to have the capability to change settings such as TCP/IP properties.

The solution in that case would be to provide specific rights to the msXfax registry keys on the fax server as follows:

Log on as an administrator Run regedit Navigate to local machine, software, Better Network Services Group Set the security permissions on this registry key to include full control to the

person or global security group who will be responsible for the day to day management of msXfax.

16.5 Security recommendations

msXfax support Domain addressing in various format including: [email protected] and name|[email protected] (Recipient name is separated from the fax number using a vertical bar keyboard character).

For example: an Outlook user can send to Larry|[email protected]

Domain Boston.fax is only known to Exchange by virtue of that address SMTP space being added to the msXfax SMTP Connector. It is not possible to address email to Boston.fax on the Internet thereby providing added security for addressing purposes within the organization.

As a general rule it advisable to: • Set policies on your firewalls to prevent spoofing from the outside. • Use Fax address space in the msXfax Connector to allow authenticated

Outlook users to send to Outlook Contacts and; • Use msXfax Domain addressing

Note: msXfax always checks the sender’s email address against Active Directory. The sender’s email address must be present in AD and must be authorized.

16.6 Active Directory Performance Settings

Customers with a large Active Directory (AD) or customers with high volume inbound faxing to a series of common work flow fax numbers can significantly improve throughput by reducing queries to Global Catalog (GC) servers.

There are two independent performance tuning options namely:

1. Exclusion options for querying global catalogs



2. Local database search before querying a GC

msXfax provides many methods of routing inbound faxes to AD users, public folders and other objects in the directory. The options include:

a) DDI (Direct Dial Inwards, also referred to as DID) based routing using the Notes field

b) DDI/DID routing using the Fax Number field

c) CSID based routing (notes field)

Customers will typically assign fax numbers to users in AD and to work flow processes. Work flow processes typically process inbound faxes from a disk directory. Some customers configure msXfax to simply not route inbound faxes for certain numbers leaving the only copy in the audit directory for processing and interfacing to their internal document management and work flow processes. This technique uses a NULL route which will be discussed later in this chapter.

16.6.1 How to reduce the number of queries to GC’s

It is recommended that all customers have the “Activate Special Inbound processing via local database turned” turned on.



For small networks with low volume inbound faxing, we recommend that the above example defaults be used to allow every possible type of inbound routing method to be used.

Removing unwanted inbound routing options will improve performance.

High Volume: Recommendations for high volume customers with ISDN primary rate

Customers with high volume inbound fax traffic should use the Fax Number field in Active Directory to store the DDI value and set the values to search the msXfax cache.

How does the cache work? msXfax keeps a cache of DDI values from previous searches of a GC. If the same DDI value is found in the cache then no search is performed on the GC. Once a fax number is assigned to a person it rarely changes so this is highly recommended for large volume customers.

If you know that number re-assignment has taken place in your organization, you can manually clear the cache as required.



16.6.2 Usage of Static GC option

In some rare circumstances it may be necessary for a customer to nominate which Global Catalog server is to be used. Dynamic binding to AD is always recommended. However, where there is a genuine need to nominate the GC manually the format will look like the example below.

16.6.3 More information on Special Inbound Processing

Customers with very large Active Directories and high inbound fax volumes to a common set of numbers assigned to work flow processes for example should consider allocating selected fax number routing details in msXfax’s local routing table to avoid any lookups on a GC and thereby improving throughput on high volume inbound fax servers.



How does Inbound Special Processing work?

SpecialInbound

=1

Performsearch on

GC

No

yes

Performsearch onlocal DB

msXfax XPRoutingTable

Fax numberfound?

yes

No

Is inbound toemail address

set?

SMTP Sendto Exchange

Server

Email address setto NULL

yes

yes

No

If folder valueis set write

copy to diskdirectory

Inbound routingFolder set to

NULL

yes

AuditImage copied

to auditdirectory

End inboundprocessing

The above flow chart shows that if the Special Inbound Processing option is set msXfax will search the local database.

If msXfax locates a record in the local database it will not search a GC.

msXfax offers a feature called NULL Route. A value of NULL in the email address and the folder routing field will cause msXfax to do nothing. This should be used



only where customers set the audit directories and decide to process inbound faxes from the audit directory for their work flow applications.

Double click on Special Handling of Inbound Faxes

Position the mouse pointer anywhere in the table and right click

Select Add User



In this example we are adding a route to a user who is not listed in Active Directory. This is just to show you other uses of this local routing table. It is also the first step to the creation of a CSV file to allow easy editing and importing into the routing table.

Inbound Fax Folder must be a local disk directory, do not use a network share. Click save. Your first entry is now added. NOTE: CSV files are now used to import and

export from the table.

If you do not select a specific directory using the “Select Directory to Import/Export from” msXfax will default to C:\ (root directory).

Leave the option checked to launch Excel.



Click Export to CSV to create your first CSV file.

Click OK.

Most customers will elect to set the audit directory options in msXfax to save all inbound and outbound fax images. If your work flow application/document management system intends to process all incoming faxes from the audit directories, then you should create a NULL route entry in the routing table to:

a) Avoid AD lookups and;

b) Avoid any specific action by msXfax for routing purposes.

The net result of a NULL route will leave only a copy in the audit directory for your application to process with no overheads in GC queries.



Text column DID Excel defaults all columns to number format. If you have leading zeroes in the DID field you must set the properties of the DID column to text. (Right click column C set the category to text format).

Warning: You should create an XLS format file as your master spreadsheet. Do not attempt to work from a CSV file directly, otherwise, leading zeroes will be dropped and other special formatting may be lost.

XLS format Create a master spreadsheet in XLS format. When your changes have been made, save your XLS spreadsheet.

CSV format for importing:

From your XLS file, select File, Save as. Save your XLS master to a CSV file. DO NOT OPEN THE CSV WITH EXCEL AFTER IT HAS BEEN CREATED. IMPORT IT DIRECTLY INTO MSXFAX’S IMPORT FACILITY.

After saving the XLS to a CSV and importing it into the local database, this is how it should appear.

msXfax will now route any faxes inbound using the instructions above. No AD lookups will occur for the above numbers.



17 Global Fax Settings

17.1 Introduction

Global Fax Settings provides global settings for each fax server:

1. Global settings which apply for customers with Exchange environments.

2. Global settings which apply when msXfax is deployed in non Exchange/Active Directory sites.

3. After a while you will become familiar with msXfax keywords which are used in the notes field of an AD object to identify the object for such things as: permissions to send a fax or an inbound DID fax number.



17.1.1 Global Fax Server Permissions and Cover Page Settings

The General fields are used for cover sheets values when not sourced from AD. It is not essential that these fields be completed if you are using AD.

Same applies to the Address tab.



17.1.2 Fax Server

Fax Server Maintenance Password should be set the same across the entire enterprise. This password is required to allow a central administrator to distribute cover sheets to many fax servers in the organization via email.



17.1.3 User Feedback

To improve the feedback to end users of the system, msXfax provides administrators the ability to send messages back to Outlook users when:

1. their fax has been accepted for processing

2. their fax has been inserted into the fax queue for transmission

3. their fax has commenced dialing.

You can optionally send confirmations when a fax has successfully been sent or if it failed message.

Note: for normal installations, you should always send confirmations “Send Fax Sent Confirmations” and “Send Fax Fail Confirmations”. An example when this would not be the case is when a fax server is dedicated for use by application and only failures are to be sent back to an inbox for operator review. An example might be a customer relationship management product which transmits faxes automatically. The system administrator may only want to know which faxes were unsuccessful, allowing corrective action to take place on an exception basis..

There are additional parameters which allow users to receive Fax Sent confirmations with the first or all pages of the fax as it was transmitted.



17.1.4 Message Limits

Administrators can restrict message sizes and recipient limits.

Version 7.6 build 329 introduced an additional option to set the maximum file size of a TIF image being sent to Exchange/SMTP servers from the fax server. This was necessary to prevent messages from being rejected and/or lost in some configurations.

msXfax will now split up a single incoming fax transmission into multiple SMTP messages to the intended recipient. Ie: an inbound fax that is too big to be sent is broken up into chunks (lower than the Maximum tif file size specified above) and sent to the intended recipient

If a single fax page should ever be larger than the maximum tif file size specified above (which it should not) then the intended recipient is provided information regarding the file name of their fax which is located on the fax server.



The location is \BNS Applications\msXfax XP\Undelivered Faxes

17.1.5 Audit images of sent and received faxes

Administrators can specify directories to store images of faxes successfully sent or successfully received.

Outbound Audit File Name Convention : TX_ccyymmdd_hhmmsshh_FaxServerSiteCode_FaxServerID_EventID_SenderDisplayName_Pages_Channel_DialedNo_RemoteCSID.tif



Inbound Audit File Name Convention : RX_ccyymmdd_hhmmsshh_FaxServerSiteCode_FaxServerID_EventID_Pages_Channel_DDI_RemoteCSID.tif

The above example saves all sent faxes to a folder on the fax server and sends a copy to a public folder for inclusion in document management and work flow systems.

The above example also shows that all received faxes are placed into an audit directory in addition to routing to users and other Exchange/AD objects.



17.1.6 Default handling of inbound faxes

Administrators can specify how inbound faxes are to be routed when no route can be determined after searching the local database or Active Directory.

The example below would send a fax which could not be routed to an email address and to a nominated folder.

If one of the options above is selected then the default route will be only that option.

If both options are not specified then the default route will be the administrator defined in the System Attendant.

17.1.7 Scenario

Many customers will install msXfax in the simplest way possible whereas other customers need granular controls for complex routing and management of faxes.

The best way to understand this subject is to look at various examples.

Example 1: a small business with a single incoming fax line with 20 users.

Their users have come from a manual system of faxing and used Microsoft Word Fax templates to create their manual faxes. The customer does not want to change the staff work practices. They have elected to continue to use their Word Fax



templates. All faxes that come in on line 1 will go to the default fax administrator who is currently responsible for distributing paper faxes.

Answer= this customer would not make any changes to any of the Global Fax Property sheets. All users by default in Exchange can send a fax when msXfax is installed (refer to Fax Server Access). However, for added security, the user object must be in AD. This customer would nominate the default administrator during installation. The default administrator is located in the msXfax System Attendant properties. The field is called Primary Alert Address. It is the email address of the user or distribution group or any other email address.

The customer decides to disable freeform fax addressing preventing forged relay of faxes from outside the organization.



Note: entering a cryptic freeform fax string similar to the one above will help prevent forged emails being bounced off the customer’s Exchange Server onto other Connectors.

Example 2: similar to example 1 but the default fax admin is different from alert admin.

Answer= this customer would nominate the Helpdesk to handle all fax server alerts (Errors). See below.

The customer would then set the Default Inbound Route handling to a nominated email address under the Global Fax Settings – Global Fax Server Permissions and Cover Page Settings. The customer would set the email address under the Default Inbound Route property page.



Example 3: any sized business with a number of fax lines and users who want to use automated standardized organization wide cover sheet for transmissions. The customer has a few more specific requirements for inbound fax lines. The IT Director (Sharon) has the following requirements:

• She has many users who will send Outlook messages to fax recipients and the Outlook memo text has to be inserted into a standard automated fax cover sheet with automatic disclaimers. She wants to do this because she wants only one place to change the business fax cover sheet, its representation and disclaimers which the legal department keep changing.

• She wants to restrict who can sent faxes using AD. • Her users typically drag and drop standard PDF files to create fax responses

based on the type of customer enquiry. • She has 1 fax line (fax line 1) which will receive faxes. She wants these faxes to

be sent to a nominated email address and a specific printer. • She has another fax line (fax line 2) which will receive customer complaints

and other special correspondence which must be document managed. Answer:

• Prepares an automatic cover sheet using msXfax cover sheet program. • The cover sheet can use the company and address details supplied in the

property sheet or they can be simply inserted into the word document as normal. She decides to not use Company and address details in the global fax settings but simply to layout her fax cover sheet in her own way.



• Therefore, all she has to do is to nominate the cover sheet she has created then nominate the keywords for fax line 1 and fax line 2.

Selecting Channel Routing (channel = fax line) allows selection of various options including Printing, Saving to disk and emailing to an email address.

The result should look like this.

She now wants to restrict which users can send faxes. This is done in Active Directory.

Firstly, she must change the Fax Server access property sheet as shown below. This forces msXfax to check Group Membership.



The Administrator could elect to use the notes field looking for the keyword [FaxEnabled].

She has elected to set up a Security Group “Fax Enabled” in the OU=Application Controls/msXfax. She now adds her users to that group.

Done. Example 4: a large multi-national with many requirements.

The IT Director (James) has the following requirements: Nothing is to be installed on the desktop because he has 30,000 users. They have approximately 50 regional locations where a fax server is to be located. They have SAP mainframe applications which must be able to send emails, faxes

and other forms of communications in the future. They use Maxcompress within their Exchange network to minimize network

traffic. He wants to restrict who can send faxes using AD. He would also like to set up least cost routing so that a fax server in say

Singapore can send a fax via the USA. He must provide accounting information for cost centers to be correctly billed via

the general ledger Inbound routing is required within the enterprise across 63 countries.

Answer:

Follow the procedures to use Microsoft Office Document Imaging printer to render from applications/documents.

They should install 50 regional fax servers ideally each one in its own routing group. If this is not possible then each fax server should be given a logical site name and possible use of msXfax Domain addressing to make each fax server specifically addressable via msXfax Domain addressing. FAX Address space is still a consideration where there is no direct correlation between Fax servers supporting FAX Address space and a Routing Group.

Install support for Winzip as documented in this guide.



This customer will use AD for almost everything they do with msXfax. Including establishing a security group for each domain/OU structure plus using keywords for: Cost centers.

He should carefully consider how least cost routing can be used within msXfax and utilizing the Exchange design that they have.

Example 5: a customer installs an analogue Eicon Diva Server card to a PABX with 4 incoming fax lines. Customer wants to route those 4 lines to 4 different email addresses. Answer:

From msXfax console, select Eicon Fax Server, Fax Devices, expand Fax Lines, double click on CAPI. Select Eicon Analogue only.

Set a DDI value for each channel. This example shows a DDI value 010 for line 1.

Go to Active Directory and place the value of the DDI into the respective user’s fax number field



Enter a colon followed by your site code and the DDI value assigned to the analogue channel of the Eicon card.



msXfax utilizes AD for the following:

Table 6: msXfax utilization of AD

Feature Field Used in Active Directory Value/Parameter

Option 1: Direct Dial Inwards fax number

Fax Number Field (Telephone Tab) A colon followed by the <SiteCode>DDI value eg:

:Boston62813355

Option 2: Direct Dial Inwards fax number

Notes field [DDI:<SiteCode>DDI value]

eg: [DDI:Boston62813355]

eg: [DID: Boston62813355]

Cover sheet Notes Field [CS:sales_cover.rtf]

Cost Center Notes Field [CC:Sales]

Printer to use for inbound faxes

Notes Field (This feature will be rolled into service pack1)

[InPrinter:<Printer name>]

Printer to use for outbound faxes

Notes Field(This feature will be rolled into service pack1)

[OutPrinter:<Printer name>.]

Channel based routing Notes Field [CH:<Sitecode+channel number>]

eg: [CH:Boston2]

Place received faxes in a directory

Notes Field InDMI:channel number|network path

Eg: InDMI:1|C:\faxes_received

Note: Channel 0 means any fax channel

Place transmitted faxes in a directory

Notes Field OutDMI:channel number|network path

Eg: OutDMI:0|C:\faxes_received

Note: Channel 0 means any fax channel



17.1.8 Compress or Rebuild Fax Database

From time to time it is recommended that a compress of the database be performed. At least annually in most cases and perhaps every 6 months for busy systems.

Click Apply.

Warning: Creating an empty database is reserved for rare situations where the MSGSTORE.MDB is corrupted and the customer has no backup.



Select Yes

Click OK when the database compress has been completed and all services restarted.

If the database can’t be compressed (open by another process), simply exit the msXfax Console, run the msXfax Console and retry the operation.

FAQ: can this operation can be run remotely via terminal Services? Answer=yes



17.1.9 Manage Fax Confirmation Templates

This option is available under Global Fax Settings. A range of reports are available and are self explanatory.

Double click on Manage Fax Confirmation Templates. Select the template eg: FaxSent.htm, Microsoft Word is launched allowing you to

modify the template.



Do not change any of the keywords in the template. You can change insert other HTML Double click on Manage Fax Confirmation Templates.

Select the template eg: FaxSent.htm, Microsoft Word is launched allowing you to modify the template.



The above example shows how you can provide information and links to your users for every fax confirmation they receive in their inbox.



17.1.10 Reports

This option is available under Global Fax Settings. A range of reports are available and are self explanatory.



17.1.11 Automatic Reporting

Automatic reporting allows a selection of reports to be sent via email to selected users.

The following example shows how to nominate an hourly utilization report for sent faxes on a weekly basis.

Click ‘Add’

Enter details of the person to receive the report. • The Display Name should be the same as in Active Directory. • Email address is the user’s primary email address in Active Directory

Press OK.



Select the date to commence reporting from. (note: msXfax automatically roles over to subsequent weeks when the previous week’s report has been produced).

Select the report(s) required. Select ‘Weekly’ for a weekly based report. Select ‘All users’ for a consolidated report. ‘This user only’ relates to the intended recipient of the report. It is important that

the display name of the recipient is spelled correctly and is the same as in Active Directory when this option is selected.

Click on Save

Reports are sent to users based on the frequency selected.

Example Outlook inbox of a manager who requires a range of reports from msXfax.



17.1.12 Quick access to fax server statistics

This option is available under Global Fax Settings

Features:

Ability to sort columns View sent/received faxes or all faxes Export to CSV and launch Excel

Note: Statistics are retained in the MSGSTORE.MDB file. They are removed based on the number of days set in the Statistics Tab found under Fax Devices.



18 msXfax Enhanced Security Edition

Email Protective Marking Standard for the Australian Government COMPLIANCE WITH THE PSM AND ACSI 33 The Australian Government Information and Communications Technology Security Manual (ACSI 33) states that ‘the standard for the application of protective markings to emails will be promulgated separately once it has been finalised.’

The Implementation Guide for Email Protective Markings for Australian Government Agencies Version 1 (October 2005) and the Email Protective Marking Standard for the Australian Government Version 1 (October 2005) were developed to assist agencies in implementing protective markings. These documents can be accessed at www.agimo.gov.au.

msXfax version 7.6 confirms with the standard but requires a license key to activate the msXfax Enhanced Security Edition features.



18.1 Permitted Security Classifications

Some defaults are presented which can be modified or added to. Security administrators should be contacted to determine which classification can traverse your fax server.

18.2 Agency support details

This information is used to compile response messages to users.

A response similar to the one below is sent to the user if msXfax rejects the message in accordance with the standard.

18.1 msXfax generated messages

Subject to ACSI33 allowing system generated messages to contain a classification msXfax administrators can turn on this feature. System generated messages include: Confirmation messages to users, error messages. The default setting is OFF.



19 Dialing Rules and Least Cost Routing (LCR)

19.1 Introduction

Tip! Dialing rules and Least Cost Routing (LCR) is activated in the Messenger Properties.

Dialing rules and LCR allow administrators to define rules on msXfax fax servers version 7.0 or better to:

• Route international faxes to another msXfax fax server in another country to take advantage of lower rates.

• Specify specific rules to dial prefixes and strip digits from fax numbers. • Manage long distance calls • Specify a rule which defines a number of area codes which are considered to

be local area codes. Dialing rules allow you precise control of outbound faxing including deferring faxes to certain times of the day or their priority.

msXfax stamps a message which has been routed to another server to prevent message loops.



19.2 Least Cost Routing (LCR)

LCR is available at all levels. Any message which is actioned by a rule containing a LCR routing instruction will be stamped so that the receiving msXfax fax server will not attempt perform further LCR operations.

A fax which is least cost routed will be notified to the sender’s email address.

The LCR engine uses SMTP protocols to send the message on behalf of the sender. Therefore, the msXfax fax server responsible for this message will then send fax sent or fax failed confirmations directly to the sender’s email address.

19.3 msXfax Setup routines

msXfax Setup places telephony values in the registry which are subsequently used by Dialing rules and Least Cost Routing (LCR). These values include: Country code, Area code(s), International dial prefix, Long distance code prefix.

19.4 Dialing Rules

Dialing rules provides a simple but powerful rules engine to allow the administrator to define the prefixes and rules to be applied to certain fax number destinations.

msXfax employs a hierarchical rules engine to easily understand the concepts and abilities of the technology.



Faxes prepared in Outlook and other applications ultimately create an entry in the msXfax queue (database table).

msXfax’s dispatcher processes faxes off the queue and if activated will follow the dialing rules and LCR instructions.

Historically, most telephony systems were implemented in similar ways to handle international, long distance and local calls. Nowadays, with increased competition, an ever increasing de-regulated telecommunications industry, increased populations and consolidation or expansion of local area codes; msXfax provides the tools to manage most of the common requirements for public and private PBX prefix and suffix handling and number presentation.

Least cost routing instructions can be applied at any level.



19.4.1 Dialing Rules Level 1 - Exceptions

Rules are applied from level 1 to level 5. Level 1 rules are rules you create to specify any specific matches on Country, Area codes/numbers which are not covered by lower layer rule sets.

Rule 1 above shows an example of an exception. Outlook users may have defined their local area code as (02). The correct setting should be 2 without the zero.

This rule will handle the condition by stripping the country code and allowing the fax server to dial the presented number.

This rule requires only the country code to be stripped because the user has supplied the number inclusive of long distance code.



19.4.2 Dialing Rules Level 2 – International

Level 2 deals with International numbers because these are easy to indentify because the Country code in the number is different to that contained in the local fax server settings.

Rule 2 above shows the reserved name “International” automatically created by msXfax when dialing rules is turned on.

This rule is the next logical hierarchical rule to be applied to the number.

The International rule does not strip the country code and prefixes the number with the international dial prefix.

19.4.3 Dialing Rules Level 3 – Local Calls

Level 3 deals with local calls. Local calls are determined by local area codes in the number string which match the rule pattern. msXfax setup stores the local area code(s) in the registry allowing a level 3 rule to be defined when you turn on Dialing Rules and LCR. Telephone companies are combining many local area codes and advising customers that they are now considered to be eligible and charged as a local call. As such there is no long distance code required for these numbers.

msXfax allows customers to define an alternate substring.

Example: Area codes in the USA of 781, 782 and 783 are considered to be a local call and no long distance code is required.

String pattern for the rule would be ^1(781|782|783). The full stop is part of the string pattern.



Rule 3 above is automatically created by msXfax when dialing rules are turned on. The rule is created to handle the local area code(s) defined during the setup of msXfax.

19.4.4 Dialing Rules Level 4 – Long Distance

Since rules are applied from level 1 to level 5, the previous levels have dealt with Exceptions, International and local areas. Therefore, by elimination there can only be long distance or a freeform number encoded into the Number portion with no country or area code.

Typically all long distance codes require a single digit such as 1 or 0 to signal that the number is a long distance number.

Rule 4 above is automatically created by msXfax when dialing rules are turned on. The rule is created to handle calls to other area codes in the country.

19.4.5 Dialing Rules Level 5 – Absolute number (Freeform)

Level 5 rule will generally be applied to freeform addresses which encode the absolute dial string (from a user perspective) into the number portion of the fax destination (ie: Country code and area code fields in the database are blank).

Applying rules at this level may be appropriate if customers have connections to a PABX where a digit must be dialed to obtain a line.

The rule may be as simple as:

Pattern = . Prepend a 0

19.4.6 USA example showing 2 area codes (781 and 617) in Boston

The 1st rule deals with the exceptions. This customer has a large msXfax server in London. Any fax from Boston to the UK will be routed via the fax server in London over the WAN.

Rule 2: International numbers will be handled in accordance with standard dialing rules.

Rule 3: manages the local area codes (no long distance digit required).



Rule 4: Long distance calls will be controlled by this rule.

Rule 5: any other number will be dialed as is.



19.4.7 USA example area code 781 Boston with a LCR to a fax server in Hong

Kong

This is the default dialing rule after installation of msXfax for a fax server in Boston area code 781.

If other area codes are considered local they can be added to rule 12.

This exercise demonstrates how to add a rule to route faxes to say Hong Kong from the USA over your internal network to save on international call rates.

Steps: Select the Boston Fax Server in the left hand pane.

In the right hand pane edit Spare Rule 1



Enter the ^ character followed by the Country code for Hong Kong (852).

Next click on Number adjustment. Ensure that no adjustments are made as shown below. The entire number must be passed to the destination server.



Select the Destination Tab. Enter the Exchange Email address of the destination Fax Server in Hong Kong.

Customers with multiple outgoing fax servers in a region can specify multiple email addresses of destination fax servers. This creates a load balance of fax messages similar to Exchange 2003 connectors. A customer scenario is described later this section how this is used in conjunction with Exchange Connectors.

The local Exchange Server’s IP address (or DNS resolution) is taken from the Messenger Property page. This IP address should not be changed unless there is a topology / design constraint or preference in your network.



This is how it should appear in the rules set.



19.5 Other facilities of dialing rules and LCR

19.5.1 Build a list of remote fax servers

This is simply a list of msXfax fax servers in your enterprise which is used for administrative purposes. An IP address or DNS host names can be defined.

19.5.2 Build a list of fax number masks

This is simply a list of msXfax fax servers in your enterprise which is used for administrative purposes.



This is a reference list which you can build to suit your organization. The Fax Number Mask is used when defining rules. The Fax Number Mask can be selected as the Fax Phone Number Pattern when defining dialing rules.

The above examples are:

^ = at the start of the fax number

61= Australia

With either a 2 or 3 or 7 or 8 in the area code

Followed a full stop = any other series of digits that follow.

^ = at the start of the fax number

1= USA

With either a 781 or 782 or 783 in the area code

Followed a full stop = any other series of digits that follow.

These examples can be used to define dialing rules to determine if long distance prefixes need to be dialed.

19.5.3 Build a list of test fax numbers

This is simply a list of fax numbers which can be selected when performing tests via this interface.

It is important that the + symbol be used followed by the Country code followed by area code.

When there is no area code such as Hong Kong, place a pair of parenthesis as shown above with a space character in the area code.

19.5.4 Request a remote dialing rules view from remote fax servers

The list of Fax Server IP addresses (or DNS host names) defined in the “Build a List of Remote Fax Servers” option is presented in this function.



Select any remote fax server to review its dialing rules. Press Send Request. msXfax uses SMTP protocols to exchange information with

remote fax servers.

19.5.5 Delete a Dialing Rule View

Remote fax server views can be removed by right clicking on the Dialing Rules under the Remote Fax Server Views and selecting ‘Delete a Dialing Rule View’.

This simply removes the view from which has been established.

19.5.6 Test Dialing Rules

This test facility should be used on the LOCAL FAX server.



Select Run Test. The above example shows that a fax server in Boston would process +44(701)12345678 as an International fax to be sent via the local fax server in Boston with Normal priority. The number to dial would include the international dial prefix from the USA.

19.5.7 What to do if you decide to change an IP address on a fax server

The LCR definition file is tied to an IP address. The example below shows an IP address of 192.168.0.108.

If you decide to change the IP address of your fax server you must do 3 things:

1. Stop all service

2. Rename the INI file to the new IP address.

3. Edit the INI file and change the IP address inside.



20 Configuring Cover Sheets

20.1 Domain level cover sheet controls

Business units with unique sender domain email addresses can use Company based cover sheets eg:

@Company1.xxx.xx

@Company2.xxx.xx

msXfax looks for a cover sheet file name = Company1.RTF or Company1.RTF

msXfax will always look for the leftmost string (After the @ symbol) in an email address of the sender to locate the correct cover sheet file.



20.2 Cover Page types

msXfax allows 2 different types of cover pages:

• a static cover page • a variable cover page

Variable cover pages are described in the next major section called “Cover Page Editor Overview”.

20.2.1 Static Cover Page

A static cover page, has a file extension .TIF. Static cover pages have no variable fields, no memo text or any other values inserted in the cover page.

However, the sender and recipient name, date and time is always included in the header stamp at transmission time.

Microsoft Word is used to design cover pages then printed to the Microsoft Office Document Imaging printer driver to generate a TIF static cover page file.

An example word document is provided with msXfax located in the cover page folder. The document is called "Disclaimer_Static_Cover_Page.RTF"

A static cover page is typically used where the customer does not require variable text to be inserted on the cover page.

Examples include: • Fax transmissions from workflow applications which require a standard

disclaimer cover page. • Fax transmissions from multifunction devices which require a standard

disclaimer cover page.

Note: Any text that is in an Outlook message body is not used with fixed cover pages. Static cover pages are typically used in broadcasting, application driven faxing eg: sending formatted remittance advices, purchase orders etc.

20.2.1.1 Step one – setting the Microsoft Office Document Image Printer

To follow instructions, as soon that you will be creating your cover pages on the fax server itself. If you wish to do this on your desktop computer, simply copy the word document to your computer and perform the same routines.

Select start. Open printers and faxes Right click Microsoft Office Document Image Writer Select properties.



Select advanced



select printing defaults select Advanced

f

Select TIFF as shown above.



20.2.1.2 Step two – open the example disclaimer cover page

All example files are stored on the fax server in the folder "Program Files\BNS Applications\msXfax\Cover Sheet".

Navigate to that folder, open the word document Disclaimer_Static_Cover_Page.RTF

To follow instructions assume that you’ll be creating your cover pages on the fax server itself. If you wish to do this on your desktop computer, simply copy the word document to your computer and perform the same routines.

Insert your logo in the top left corner. Insert your telephone number, and any other relevant text. Change your address and phone numbers as required. Select file save as, provide your cover page with a file name, make sure you save

it as a .rtf



20.2.1.3 Step three – create a TIF cover page file by printing the RTF file

Print the document to the Microsoft Office Document Image Writer as shown below.



Your resultant TIF cover page file is displayed. This cover page file can be referenced in msXfax, as a default or by users and/or applications inserting a cover sheet keyword in the message body.



20.3 Cover Page Editor Overview

A Cover Page editor setup program is supplied with the general install files. This setup can be deployed to users responsible for the creation of cover pages for their respective business units

Cover pages created using the Cover Page editor can be tested by forwarding it to the Fax Server to process and return a rendered image as it would appear as a fax. The forwarding process is actually part of the Cover Page editor. A TIF image is returned showing you exactly how the cover page would appear if sent as a fax.

To control the implementation of user defined cover pages, users must send their final designs to the msXfax administrator for inclusion in the Program Files\BNS Applications\msXfax\Cover Sheet location on the fax server.

20.3.1 Cover Page tool features

Cover Page Tool supports Microsoft Word as the editor and allows Active Directory keyword tags to be dragged from the sender and receiver panes in the tool to word.

The keyword tags are defined in a text file called ‘msXKeywords.txt ‘ located on the fax server by default in C:\program files\BNS Applications\msXfax\Cover Sheets’.

msXfax keyword tags support ANY Active Directory attribute for Person or Contact Objects. msXfax also supports user defined keyword tags for by end users or application processes. This unique feature in msXfax is extremely powerful for use by: Application developers, Outlook forms designers or users who want to insert values in the message body and have those values appear on the fax cover sheet.

Supporting user defined keyword tags allows systems integrators to provide value added integration services for their clients to integrate msXfax to any application such as: Document Management Systems, Outlook front end forms, mainframe applications, SAP applications, E-commerce applications etc.

From an application perspective, an msXfax cover sheet could be considered like a fax business form which can be supplied values from an application. For example: an SAP application could perform a simple MAPI send or an SMTP send for an AD user called [email protected]. This AD user has a cover sheet called Purchaseorder.DOC and the application supplies the variables the message text.

This is a simple implementation of BNS Group’s Enotify-AI application programmers interface which is now bundled with msXfax version 6.7.4+

When msXfax receives a message with embedded user defined keywords it will perform a search and replace on the cover page associated with the user when the fax is rendered.

Technical note: The keyword/value combination should be specified in the message body of the email and prefixed with a ‘S-‘ for Sender details or ‘R-‘ for Receiver



details and , e.g. R-SAPAccount=Q12654UQ, then in the Cover Page the keyword tag should placed in any suitable place but be enclosed in brackets e.g. [R-SAPAccount].

There is no limit to the number of keyword/value combinations in a message or Cover Page. While traditionally a cover page is a single page there is no limitation in msXfax and a cover page can be any number of pages.



20.3.2 The Keyword Tag definition is made up of two parts :

This is technical information for customers who need to know a little more about the inner workings of cover sheet processing:

Table 7: Example of Keyword Tag definition

Part Description Comments

S-GivenName The ‘S-’ prefix indicates that the tag refers to Sender Details, The value following refers to the Active Directory Attribute name for the Given name of the Sender

Value=GivenName The label assigned to Value is displayed in the Cover Page tool to describe meaningfully what the AD Attribute refers to.

Extensible: Keyword Tags/Value combinations can be added to a file called ‘msXkeywords.txt using a text editor such as notepad at any time.

It should be noted however, that the Cover Page Tool setup (which may be deployed to users desktops) also requires the ‘msXkeywords.txt’ file. If any changes are made to this file in regards to adding new keyword Tag/value combinations, this file must be copied to the Fax Server(s) for the new keywords to be used.



Figure 4: The Cover Page Tool is an “always on top” tool, to be used in conjunction with Microsoft Word. Fields are easily dragged onto cover pages created using Microsoft Word.

20.4 Using the Cover Page Tool

20.4.1 Configuration

The configuration menu shows the location to store cover page files. Click the Folder icon to the right of the location to select another location. This is where your cover sheets will be created if you create them from the tool. Fields can be dragged onto any word document that is open.

20.4.2 Use of tables in RTF cover page files

For maximum reliability and performance, do not use tables in cover sheets. MsXfax, by default uses high-performance conversion routines, rather than full rendering print streams.

If tables are inserted into cover sheets, you'll find that your cover sheet does not render correctly.



20.4.3 Keywords

Opens the extensible msXfax keywords file in notepad. This file an be altered by advanced Administrators with a good knowledge of Active Directory and msXfax. Keywords are representative of Active Directory Object Properties.

Instructions exist in comments at the top of the file. Once you correctly modify this file, the keywords you add will appear in the keyword list next time you start the Cover Page Tool.

20.4.4 Open a sample Cover Page file msXcover.rtf

Click on the Folder icon to open an existing cover sheet (RTF format file).

Select the sample supplied with msXfax called “MSXCOVER.RTF”.



Figure 5: Open the sample cover sheet

This sample cover sheet includes many of the common values for your Active Directory users.

It is a simple matter of drag and dropping the keywords from the tool to the word document.

Note: Please minimize the number of keywords you use, otherwise it will add more processing requirements on your fax server. Where possible use static values in your cover sheets. For example: Rather than pulling the Company name from Active Directory it would be more efficient to simply have your company name and



logo in the word document. If your enterprise is split into many business units and AD is the source of all information, ensure that your fax server has sufficient CPU and memory.

20.4.5 Test your Cover Page

From the Cover Page tool you can test your cover page using the “test cover page” button. This will send the cover page to the fax server, perform an OLE automation of Word then return the result as a TIF image.

Click the Test Cover Page button, the following dialogue appears:

Figure 6: Cover page testing using the in-built test facility.

You can browse for an existing cover sheet that you want to test. Specify your Exchange server DNS name or just the IP address of your Exchange

Server. Complete the fields similar to the above example replacing company.com with

your DNS domain name. The example above shows that we used the fax server’s POP3 Mailbox email

address used by msXfax’s Messenger process. [email protected] Click Send to send the test. A mail message containing the cover sheet will be

sent to the specified address.



msXfax will process the message and send you a TIF image of the rendered cover page. If you see some large text on secondary pages, please ignore this and move on to perform a real test using your fax server and a fax machine).

When you’re happy with the presentation, you should send yourself a test fax to a fax machine. However, before you send a test fax you must:

Ensure that the cover page file eg: msxcover.rtf is located on the fax server in Program Files\BNS applications\msXfax\Cover sheets\.

Go to your Active Directory user object and add the keyword [CS:msxcover.rtf] in the Notes field.

20.5 How does msXfax handle text from Outlook

There are many combinations to consider. This is how msXfax handles the different combinations:



Fax Server configuration

User operation in Outlook

No cover sheet

Static (Fixed) cover sheet

Variable cover sheet

Supplies only memo text

Allowed – sends as plain text

Not allowed –fax is rejected

Text is inserted into cover sheet.

Supplies memo text and attachment(s)

Allowed –

sends as plain text as initial page(s) and then the attachment

Allowed –

Ignores plain text. Sends just the static cover page and the attachment

Text is inserted into cover sheet.

Specify only attachment(s)

Allowed Allowed Allowed

20.6 Fax Server cover page keywords

This information is provided for administrator’s to be aware of the comprehensive features sets of msXfax with respect to cover pages.

As mentioned in the introduction section of this chapter, you can add your own keywords to the keywords file. Keywords can be used in conjunction with your applications and Outlook forms (VB Script) to insert keyword commands into the body of messages.

The following file can be edited via the “Keywords” menu option in the Cover Page Tool. It is physically located in the:

“Program files\BNS Applications\msXfax \cover sheets” directory on your fax server.

************************************************** * msXfax Cover Page Keywords File * * * This file is used by msXfax to propagate the* * Cover Page program and the Messenger as to * * what Active Directory attributes are supported * * * * Modify this with Care * * Version 6.0 * ************************************************** * The TAG is the actual AD Attribute in brackets and the value is the name displayed * in the Cover Page Program. * * Tags Prefixed with a 'S-' refer to single value Sender attributes. * Tags Prefixed with a 'S*' refer to multivalue Sender attributes. * Tags Prefixed with a 'R-' refer to single value Receiver attributes. * Tags Prefixed with a 'R*' refer to multivalue Receiver attributes.



* Note that Receive details will only be extracted if the Receiver is in Active Directory ************************************************************************* * Special Tags not part of AD but used by msXfax * Do not delete or change ************************************************************************* [S-Subject] Value = EMail Subject [S*MailBody] Value = EMail Body ************************************************************************* ************************************************************************* * Sender Tags * ************************************************************************* [S-GivenName] Value = Given Name [S-Sn] Value = Last Name [S-DisplayName] Value = Display Name [S-Initials] Value = Initials [S-Title] Value = Title [S-Manager] Value = Manager [S-Company] Value = Company [S-DirectReports] Value = Direct Reports [S-ManagedObjects] Value = Managed Objects [S-Department] Value = Department [S-Info] Value = Notes [S-Description] Value = Description [S*StreetAddress] Value = Business Street [S-L] Value = Business City [S-St] Value = Business State [S-Co] Value = Business Country [S-PostalCode] Value = Postal Code [S-PostOfficeBox] Value = Business Post Office [S-PostalAddresss] Value = Business Postal Address [S-physicalDeliveryOfficeName] Value = Office



[S-HomePhone]' Value = Home Phone [S-TelephoneNumber] Value = Business Telephone [S-Pager] Value = Pager [S-Mobile] Value = Mobile [S-FacsimileTelephoneNumber] Value = Fax [S-OtherMobile] Value = Alternate Mobile [S-OtherPager] Value = Alternate Pager [S-OtherTelephone] Value = Alternate Business Telephone [S-OtherFacsimileTelephoneNumber] Value = Alternate Fax [S-IPPhone] VAlue = IP Phone [S-OtherPPhone] Value = Alternate IP Phone [S-wwwhomepage] Value =www Home Page [S-url] Value = url [S-mail] Value = Email Address ************************************************************************* * Receiver Tags * ************************************************************************* [R-GivenName] Value = Given Name [R-Sn] Value = Last Name [R-DisplayName] Value = Display Name [R-Initials] Value = Initials [R-Title] Value = Title [R-Manager] Value = Manager [R-Company] Value = Company [R-DirectReports] Value = Direct Reports [R-ManagedObjects] Value = Managed Objects [R-Department] Value = Department



[R-Info] Value = Notes [R-Description] Value = Description [R*StreetAddress] Value = Business Street [R-L] Value = Business City [R-St] Value = Business State [R-Co] Value = Business Country [R-PostalCode] Value = Postal Code [R-PostOfficeBox] Value = Business Post Office [R-PostalAddresss] Value = Business Postal Address [R-physicalDeliveryOfficeName] Value = Office [R-HomePhone]' Value = Home Phone [R-TelephoneNumber] Value = Business Telephone [R-Pager] Value = Pager [R-Mobile] Value = Mobile [R-FacsimileTelephoneNumber] Value = Fax [R-OtherMobile] Value = Alternate Mobile [R-OtherPager] Value = Alternate Pager [R-OtherTelephone] Value = Alternate Business Telephone [R-OtherFacsimileTelephoneNumber] Value = Alternate Fax [R-IPPhone] VAlue = IP Phone [R-OtherPPhone] Value = Alternate IP Phone [R-wwwhomepage] Value =www Home Page [R-url] Value = url [R-mail] Value = Email Address



20.7 Management of cover sheets in large enterprises

Administrator’s may have the need to update common cover sheets across a number of fax servers. This is can be performed via email as follows:

Set up an Exchange Distribution Group which comprises all mailboxes used by all msXfax fax servers in the enterprise.

Run Outlook Create a new message and address a new message to the Exchange Distribution

Group Enter the following in the subject “Cover Page Update” (without the quotes). In the memo enter the special keyword. MP#

Maintenance Password (MP#)

Setting a maintenance password on all fax servers to the same value eg: 12345 would require you to enter in the memo of the Outlook message MP#12345

Attach the revised cover sheet with the MP# password. The password must be

set the same on all fax servers.



21 Other configuration elements and options?

21.1 Changing confirmation messages

Fax Sent, Fax Failed, fax received message templates can all be changed to suit your organization’s standards.

msXfax uses HTML format files allowing maximum flexibility for administrators to change the way users are presented with messages from msXfax.

The following files are located in the msXfax\templates directory on the fax server.

File name Purpose

ALERT.HTM msXfax Alert message

FAXSENT.HTM msXfax sent confirmation

FAXFAIL.HTM msXfax failed fax notification

FAXIN.TXT This is a text file used for received faxes

Note: Before making any modifications to these files, make sure that you make a copy of the originals for safe keeping.

Some customers like to modify the HTML files to include their company logo and links to their own internal intranets for user instructions and policy in relation to msXfax.

Remember to apply any file changes to all your fax servers.



22 Configuring Exchange/AD for other tasks

22.1 How to route a fax to a user using DDI values

Edit the user’s Telephone property tab in Active Directory. Insert a colon to the right of any existing value in the that field. Followed by the sitecode and the DDI value

Note: msXfax can be configured to apply a DDI value to a fax which came in on a specific analogue line when using Eicon Diva Server analogue boards. Refer to the Eicon Board configuration in this guide. An example shows how a fax coming in on line 1 can have a DDI value 010 applied for routing purposes. msXfax will then search Active Directory for “:sitecode010” and route the fax to the AD object, in this example it is a user’s inbox but it could be any AD object.

22.2 Creation of Active Directory Fax Contacts

From Exchange Management Console, select New Mail Contact.



Provide the fax number in international or local format eg: [email protected]

Complete the wizard. Edit the properties of the Fax Mail Contact as shown below



Note: if Fax Mail Contacts are used in Distribution Groups (DG), the DG must be expanded in Outlook before sending the fax.

22.3 How to route inbound faxes to a public folder

Routing inbound faxes to users is achieved by using an email address. The following describes how to accomplish the task of routing to a public folder.

Firstly let’s look at an example public folder structure in Exchange.



In this scenario we want to route faxes that come in on fax line 1 to the “PF Sales Received Faxes” public folder. We also want to notify ALL people in the sales team that a fax has arrived and has been placed in the public folder. Our assumption in your Exchange design is that you have mail enabled you Global Security Group eg: Sales Team Boston

Firstly create your public folder in Exchange System Manager and assign permissions to the folder.

Right click the public folder Select All Tasks Select Mail Enable as shown below

Right click the PF Sales Faxes Received public folder Select properties



Note: Exchange/AD may take a little time depending on your AD Design to actually generate the proxy email address(es).

Your public folder should now have an email address automatically generated by Exchange. You can now send an email to [email protected] and you should be able to see the message in the public folder from Outlook.

Note: if you only wish to route inbound faxes to a public folder, you could use the local database option to route incoming numbers to the email address of the public folder. The section below describes how you can use a distribution group to route to a public folder which is a member of the group.

22.3.1 Create a Distribution Group which includes a public folder

Scenario: The Sales Manager decided he wanted ALL of his sales team to receive a copy of faxes for Sales. His staff cover for one another while they are on vacation so he wants all of his staff to receive a copy plus he wants a copy stored in a Public Folder for his team to refer back to if they lose a copy from their mailbox.

How to Implement this scenario: Create a global distribution group which will have 2 members:



• The public folder “PF Sales Faxes Received” • The Global Security Group called “Sales Team Boston”

By making the Global Security Group mail enabled ensures that if a new staff member is added to the sales team they will automatically start receiving sales faxes without the Exchange Administrator having to change anything else.

Run Active Directory users and computers Select the OU where you want to create the Distribution Group (we will use a

global distribution group in our example. Depending on your design you may want to use Universal Distribution Groups).

For the purposes of this documentation we have used a prefix DG to make it clear which objects are which. You should carefully plan your naming conventions.

Next



Create an Exchange e-mail address Next then Finish The following example shows: 3 users, a global security group (mail enabled)

and global distribution group (Mail enabled).

Right Click on DG Sales Faxes Boston



Select Add Exchange Public Folders

Select your public folder Click on Ok Right click properties on DG Sales Faxes Boston. View the Members property tab



Now you can add other objects to the list. We will add the Sales Team Boston as shown below

Your example should now look like the one below: a Distribution Group containing a mail enabled security group and a public folder.



Click on the General Property Tab

[CH:Boston1] is the channel routing keyword for msXfax for the site Boston line 1 to route to this Distribution Group. We have given you some ideas how you can use the notes field to make your own notes about the function of the Distribution Group. Using Distribution Groups provides ultimate flexibility.



22.4 Routing inbound faxes to external contacts

Fax Service providers and customers can configure Contacts in AD with a Fax number assigned in their AD properties to enable inbound routing to external contacts.

When a fax is received on a particular DID fax number, msXfax will lookup AD and send the fax to the Contact.

The AD Contact can be on any external network including: Groupwise, Notes, SMTP Internet, X.400 etc.

The following example shows how to create a contact in AD that an inbound fax will be routed to.

From Users and Computers snap-in select an OU then Right click, create New Contact



The example above shows how the fax field in AD is used together with the site code and a colon to create the search criteria for msXfax to determine which external contact will receive this fax.



An alternative approach would be to use the [DDI] keyword in the notes field. This is required if printing is required in addition to routing to user’s inbox or to a distribution group.

22.5 Inbound Printing Configuration

Logoff the fax server and logon as the msXfax Print service account. This is the

service account which was established during the installation process. Add printers via Control Panel that the msXfax print service should print to.

It is important to do this when logged on as the print service account because it creates the correct permissions and printer references.

Inbound printing is associated with a DDI value usually associated with an AD

User Object or Distribution Group. This DDI keyword is inserted into the Notes field part of the User Object as per attachment. The keyword must be of the format [DDI:sitecode+ddivalue] e.g [DDI:Sydney1234567]

Also a Printing keyword needs to be inserted into the Notes field. The format is [InPrinter:0|\\local fax server\printer name]

e.g [InPrinter:0|\\faxserver\EPSON Stylus C65 Series]



Example of inbound printing using Active Directory notes field.

Faxes are routed to the user’s inbox and to the printer.

Routing to Distribution Groups and printing is supported.



23 Fax Server Management

23.1 Windows Terminal Services and other products

Warning: Microsoft and other 3rd party products such as Damewear may cause RPC errors and other errors with msXfax if you are logged on using a network account login.

Member Server If you use such products to remotely manage msXfax servers, login using an account which has appropriate permissions and make sure you login to the member server (……..This Computer) not a Domain.

/ Console Using the /console command with Microsoft’s RDP on Windows 2003 SP0 will cause problems. Please upgrade to SP2 of Windows 2003 Server.



23.2 System Center Operations Manager (SCOM) 2007

System Center Operations Manager provides end-to-end service management that is easy to customize and extend to help improve service levels across your IT environment.

A Management Pack for SCOM 2007will be released in a future release of msXfax.



24 How do my users use the system?

msXfax uses features already built-in to Microsoft Outlook that allow users to send a fax.

24.1 Outlook Web Access

Receiving faxes is no different from the Outook rich client. Internet Explorer version 6.x has a good TIF viewer for reading faxes.

Sending faxes from OWA can be done using all methods described in this guide. However, OWA does not create a “FAX” address book entry like the rich client does when a Business Fax field is defined by a user.

Therefore, if OWA users want to create Fax Contacts they should create a Contact with an email address which follows the msXfax domain addressing format.

OWA users can define a contact’s fax address just like a regular email address. The addressing format is known as msXfax domain addressing. A second email address is built into OWA contacts which can be used for a fax address.



The above example shows how OWA Contacts can be defined with a regular email address and a fax address.



Your users can select either Bob Brown’s email address of his fax address.

24.2 Addressing & Sending faxes

There are many other ways to send faxes which include: Exchange Custom Addressing msXfax Free form addressing msXfax Domain addressing Printing to Microsoft Office document imaging then emailing the TIF image to a

fax recipient. Scan to Outlook

We will discuss these additional ways to send a fax later in this chapter. Let’s look firstly at sending a fax to an Outlook Contact using Outlook and we will attach a Microsoft Word document to be sent as a fax.

24.2.1 Outlook Contacts

Users can simply add the recipient’s fax number in the business fax number field of an existing contact. For one-off faxing, we suggest you use Exchange Custom addressing.

The following is a basic Outlook Contact entry. This could be a Contact in the user’s Mailbox or a public folder Contact.

Important: Please advise your users to always format their fax numbers with full International formats. This is particularly important for



roaming users who connect to other subnets in your enterprise. The international format is +Country code (area) number EG: +1 (781) 12345678 +1 = USA, 781 = area code in Boston, 12345678 is the fax telephone number

The example above:

+61 = Australia Country code

(2) = area code for greater part of NSW and ACT

followed by the number

Note: in some countries (such as Australia and the UK) people think of an area code for say Sydney NSW as area code (02) or an area code in the UK (0173).

This is correct in the context of the National telephone system which people use everyday. In actual fact, the 0 is in effect the long distance code. 2 or 173 in the case of is the area code.



24.2.2 Outlook Contacts using msXfax Domain Addressing

Some organizations who are unable to change settings in their Exchange network to allow FAX address space to be used, can still use Outlook Contacts by creating an additional Contact Record for Fax Addressing purposes.

Alternatively, the secondary email address built into Outlook will achieve the same result.

The example below shows a second Outlook contact record with a SMTP email address formatted to work with msXfax.

The example below includes the person’s name as part of the email address followed by a vertical bar. The name will then be placed on an automatic cover sheet if one has been specified.



24.2.3 Send a Word document example

Selecting recipients from your local Contacts requires care. 2 entries are shown on the left hand side of the Outlook Select Names window. This is because you have specified a fax number and an email address for a single contact.

This is as designed by Microsoft, please take care when selecting the recipient and check that “(Business Fax)” is displayed by Outlook in the Message Recipients list box.



24.2.4 Sending faxes when using Microsoft Word

Many customers prefer to implement simple fax templates using Microsoft Word for creating and sending a fax message rather than using msXfax automatic cover pages.

After a fax message has been created inside Word: Select File Select Send to Select “Mail Recipient (As attachment)” (This option does not appear in all Word

versions. If you are using an older version of Microsoft Word and this option does not appear, you should select “Mail Recipient” which in fact sends the word document as an attachment.

When Word launches an Outlook send window, you can address your fax using the many options supported by msXfax.



24.2.5 Outlook public folder Contacts

The same level of functionality is provided as in Outlook Contacts. The only consideration is to ensure that your users’ profile has been configured correctly to include a public contacts folder in their address list.

24.2.6 msXfax Domain Addressing

Users can use Outlook MAPI client or OWA can simply address their faxes just like an email.

For example

Example for a USA fax number +1-781-12345678

Country with no area code +852- -12345678 No spaces between the dash symbols in the case of +852



Above: Another example of msXfax domain addressing.

This is the recommended way to prepare faxes using domain addressing if automatic cover sheets are used. msXfax uses the name eg: BillBrown to include on the fax cover sheet.

24.2.7 msXfax free form addressing

msXfax has a very useful form of addressing called “msXfax free form”.

Free form addressing is mainly used for sending to a list of fax recipients which you store in a text file.

With msXfax free form addressing you can either: • Paste the free form values into your memo or; • Attach a text file (.ADR extension) with the free form values contained in the

file. Let’s look at an example to see how easy it is.

NOTE: The default freeform fax command is FAX@

The default value can be changed in msXfax. BNS recommends “FAX=”



The example above shows that full International numbers can be specified by using the + symbol. msXfax fax server will automatically dial the International dial number eg: 011 (If dialing from USA), 0011 (Australia).

You can specify an absolute number as shown in the example above to Bill Brown who is in area code 671. However, where possible please use full international formatted numbers.

011 (International dial from USA) 852 is Country code for Hong Kong There is no area code The remaining digits is the local number in Hong Kong.



24.3 Faxing from Windows Applications

Faxing from Windows applications is achieved by printing to the Microsoft Office document image writer printer.

24.3.1 How to set up Microsoft Office Image Writer

To set up the Microsoft Office document image writer perform the following is a one-off operation:

select start printers right click Microsoft Office document image writer printer properties advanced printing defaults advanced

Select TIFF Fine 200 DPI. Choose a default folder where these images are to be kept. OK



24.3.2 Print from your application

Run any application such as MYOB

Select the Print option Select Microsoft Office document image writer printer

Select Print



Make sure that the View Document Image is checked.

Note: Microsoft for some reason removed the “View Document Image” option from version 11.03.0001.00 which is the version found in Office 2007. If you are using Office 2007 you can’t use the view feature to streamline your viewing and sending functions. You will need to locate the TIF file and double click on it or simply attach the TIF file in a new Outlook message window and view it from there before sending.

Save the image to a location

Select File Select Send to Select Email Recipient (As attachment)



Send the image to a fax recipient(s), distribution groups, email recipients.

Press send

24.4 Broadcast faxing

Note: Broadcast functions are not supported on msXfax licences less than 8 lines.



Broadcast faxing is identical to sending from an application except that an Address list is attached with the message and a few simple commands. Broadcast faxing is for high volume faxing.

24.4.1 Installing Microsoft Office Document Image Writer

If you have installed Microsoft Office 2003 on your desktop the Microsoft Office Document image writer printer driver is automatically installed; proceed to the sections below to configure the printer driver.

If you have installed Microsoft Office 2007 it will be necessary to install the Microsoft Office Document image writer printer driver as follows.

OFFICE 2007 installation requirements on the client computer which will prepare the broadcast


Choose Customize



Select Microsoft Office Document Imaging to “Run from My Computer”



Select the options above for Microsoft Office Document Imaging Proceed to Configure the Microsoft Office Document Image Writer below

24.4.2 Configure the Microsoft Office Document Image writer

Select Start Select Printers Right click on the Microsoft Office Document Image Writer printer icon Select properties Select advanced



Select Printing Defaults option (lower left). Select advanced

Select Fine (200 DPI)



Do not change the Default folder. Allow the system to determine the setting. Click ok

24.4.3 Set up of your Excel CSV file

Your CSV file should contain a minimum of 2 fields: Recipient Name and Fax number.

Your column heading names can be anything you like.

The fax numbers in the CSV file should be formatted to include the country and area codes eg: +1(781)12345678

When faxing within your own Country only, it is possible to include the absolute number to be dialed inclusive of area code.

Two sample files called example.adr and example.csv are located in directory \Fax Server Installation Files\Fax Software A utility program called CSV2ADR.EXE is also included in the same folder. This utility converts CSV files to ADR files for broadcasting. Customers who previously used Render to Outlook for broadcasting should now use this utility.

24.4.4 Set up a broadcast document

Customers typically want to broadcast a word document to a given list of recipients. The following is an example of how to broadcast from Microsoft Word 2007.

Create your TIF image file. Example below shows how to create a TIF image using Word 2007.



Press Control+P to print the word document.

Select Microsoft Office Document Image Writer. Click ok.



Save you document as a TIF image file Open your Outlook Ask your administrator of the name of the broadcast server mailbox. Enter the name of the mailbox in the to field Enter a subject field broadcast attach your broadcast address list file (.ADR) Enter the keyword [ broadcast] in a memo Enter the keyword FaxSender# followed by the name to appear on top of each

fax broadcast page.



msXfax will provide broadcast updates and final completion information directly to the sender’s Outlook mailbox.

24.5 Receiving faxes

When a fax is sent to the msXfax fax server usually there is direct in-dial (DID or DDI or DTMF) values detected by msXfax. Put simply, if msXfax receives a fax on the number assigned to you by your administrator, the fax will be sent to your mailbox.

msXfax supports receiving to other locations IN ADDITION to your mailbox, these include:

Printer Disk directory

The following shows how a received fax appears in your mailbox.



24.6 Special commands

Organizations such as Legal firms usually track fax usage for client disbursement charges.

Legal firms’ client accounting systems usually have Client/Matter number as the billing control.

msXfax allows special commands to be included in the memo portion of a fax which is extracted and written to the fax transaction log for reporting and import into back office client accounting systems. The Client/Matter number are removed from the memo before transmission by fax.

Outlook forms, document management systems or work flow applications can construct fax messages with special commands.

Inserting BC#<matter number> in the body of a message would allow legal firms the opportunity to record and report faxes by matter number.

24.6.1 Passcodes

As an additional security check it is possible to configure msXfax to check for the presence of a keyword in the message memo body called PASSCODE#

Passcodes can be implemented at a Fax Server level or at a user level.

Administrator’s notes: • At the fax server level the Passcode is entered in msXfax console - Messenger

General Property tab • At a user level in Active Directory as a keyword for example: [Passcode#test]

The format would look like the example below:



24.7 Manual Selection of Cover Page

In the Outlook memo type the following keyword in the first part of your memo.

CS#yourcoverpage.rtf



The RTF cover page must exist in the fax server’s directory where cover pages are stored.

25 Removing msXfax

25.1 Exchange Server considerations

Delete any Exchange mailboxes which you used for msXfax. Delete Exchange SMTP connectors which you configured for msXfax.

Deleting the additional registry entries can be performed if required but it is not essential.



25.2 Removing msXfax from the fax server

Login with Domain Admin rights or with local Administrators group permissions.

Control Panel, Add/Remove programs Select the first msXfax entry which has approximately 20MB associated with it. Select Remove

Removal issue? BNS noted that sometimes WISE uninstall does not work correctly. Symptom is that removal of the entry from Add/Remove happens immediately without actually removing msXfax. If this happens to you, refer to the special section below.

If you want to remove msXfax’s installation files also, remove the other msXfax entry which has no associated file size associated with it.

If you are removing msXfax to simply re-install it on the same machine, there is no requirement to remove the installation files. Installation files can be copied to another machine and a new installation performed. However, a change in hardware platform will require a new release code and activation process. Please contact your reseller or BNS Group if you intend to relocate your msXfax license to another machine.

25.3 How to remove msXfax if WISE fails to correctly remove msXfax

25.3.1 First and preferred option

There is a known problem with WISE uninstall, whereby WISE does not remove the software correctly and continues to remove its own UNWISE.EXE program. A copy of this program exists in the Program Files\BNS Applications\Fax Server Installation Files directory. If you can’t find a copy of this program contact BNS Group support via www.bnsgroup.com.au

Copy the UNWISE.EXE program to the Program Files\BNS Applications\msXfax directory.

Run the remove option again in Control panel’s Add/Remove programs.

25.3.2 Removal via a re-install

There is a known problem with WISE uninstall, whereby WISE does not remove the software correctly and continues to remove its own UNWISE.EXE program. By reinstalling the software creates another copy of the UNWISE.EXE program.



Remain logged in with Domain Admin rights or with local Administrators group permissions.

Run REGEDIT Navigate to HKEY_LOCAL_MACHINE\Software\Better Network Services

Group\msXfax\Messenger Rename the registry key “POP Host IP” to “POP Host IPX”. Close REGEDIT. Run Windows Explorer and navigate to your msXfax Setup files

eg: Program files\BNS Applications\Fax Server Installation files\Fax Software Stop all msXfax services Run the program msXsetup.exe to re-install msXfax. After installation is completed DO NOT reboot the machine. Now you can go back to the section above to remove the software again.



26 Management, Troubleshooting & error messages

This section is provided for installations which do not go to plan or where additional technical information may be required outside of the normal installation and operational procedures.

26.1 Database maintenance

On busy systems this procedure should be followed on a monthly basis or less frequent on less busy systems. As a minimum every 6 months on low usage systems.

Stop all services. Then set options as shown below. Default is 365 days.

Select OK. Select Statistics



Select purge & archive statistics Export to CSV



Select Yes

Now close the msXfax console Reopen the msXfax console and select Compress or Rebuild.

Note the original size. Select COMPRESS DATABASE



Apply Should this error message appear, simply close the msXfax console then open the

msXfax console and try again.

The services should restart after compress has taken place. The above should be done periodically for maximum performance and stability.



26.2 msXfax data flow diagram

26.3 Exchange 2007 back pressure

If you experience SMTP errors with Exchange 2007 it could be because of Exchange Back Pressure feature hitting certain thresholds. When Exchange 2007 thresholds reach their limit, Exchange refuses to accept any SMTP connections so MSXFAX isn’t able to send Inbound faxes to the designated Email address.

The following Microsoft article may help you fix the problem.



http://msexchangeteam.com/archive/2008/05/14/448890.aspx

26.4 Winmail.dat error messages

Remove support for FAX Address space from your fax connectors.

26.5 User receives Email with Subject = Incomplete Fax Received

This can happen when an inbound fax is partially received and the transmission did not complete successfully. The partial fax (tif file) may be corrupt so it cannot be forwarded on to the recipient, instead msxfax will generate this default incomplete image to indicate to the user that this situation has occurred. In a situation where the tif file is readable it will be sent to the user with an indication that it is a partial transmission.

Some fax machines resend a fax after a transmission failure from where it left off. msXfax will receive the subsequent part of the transmission and deliver 2 emails to the destination address for the inbound fax.

26.6 Which folders can be monitored by network management software

The following folder names can be monitored by management products to determine if the fax server may have encountered a problem dealing with either outbound or inbound faxes.

Program files\bns applications\msXfax xp\programs\message spooler\conv1 A file count of *.EML will indicate the conversion load on the server. If this count remains high for an extended period of time then investigate.

Program files\bns applications\msXfax xp\files When a file is converted and inserted into the database a tif file is placed temporarily in the Program files\bns applications\msXfax xp\files directory until it is sent and then it is deleted. Inbound faxes are also kept in this directory. So if there



is a buildup in this directory and it does not go down over time then there is a problem.

26.7 Possible ISDN Errors from Diva Diagnostics

Diva Server Diagnostics software can provide detailed diagnostics. For more information on using the Diva Server diagnostic module refer to Dialogic manuals and help within the Diagnostic software utility.

Cause Code (Dec)

Value in trace (Dec)

Cause Code (Hex)

Value intrace(Hex)

Meaning

Category 0 - normal event

00 128 00 80 Normal Disconnect

01 129 01 81 Unassigned (Unallocated number)

02 130 02 82 No route to specified transit network

03 131 03 83 No route to destination

04 132 04 84 Send special information tone*

05 133 05 85 Misdialled trunk prefix*

06 134 06 86 Channel unacceptable

07 135 07 87 Call awarded and being delivered in an established channel

08 136 08 88 Preemption*

09 137 09 89 Preemption, circuit reserved for re-use*

Category 1 - normal event

16 144 10 90 Normal call clearing

17 145 11 91 User busy

18 146 12 92 No user responding

19 147 13 93 User alerting, no answer

20 148 14 94 Subscriber absent*

21 149 15 95 Call rejected

22 150 16 96 Number changed

23 151 17 97 Redirection to new destination*

24 153 19 99 Exchange routing error*

26 154 1A 9A Non-selected user clearing

27 155 1B 9B Destination out of order

28 156 1C 9C Invalid number format

29 157 1D 9D Facility rejected

30 158 1E 9E Response to STATUS ENQUIRY

31 159 1F 9F Normal unspecified



Category 2 - resource unavailable

34 162 22 A2 No circuit/channel available

38 166 26 A6 Network out of order

39 167 27 A7 Permanent frame mode connection out of service*

40 168 28 A8 Permanent frame mode connection operational*

41 169 29 A9 Temporary failure

42 170 2A AA Switching equipment congestion

43 171 2B AB Access information discarded

44 172 2C AC Requested circuit/channel not available

46 174 2E AE Precedence call blocked*

47 175 2F AF Resource unavailable, unspecified

Category 3 - service or option not available

49 177 31 B1 Quality of service unavailable

50 178 32 B2 Requested facility not subscribed

53 181 35 B5 Outgoing calls barred within CUG*

55 183 37 B7 Incoming calls barred within CUG*

57 185 39 B9 Bearer capability not authorized

58 186 3A BA Bearer capability not presently available

63 191 3F BF Service or option not available, unspecified

Category 4 - service or option not implemented

65 193 41 C1 Bearer capability not implemented

66 194 42 C2 Channel type not implemented

69 197 45 C5 Requested facility not implemented

70 198 46 C6 Only restricted information bearer capability available

79 207 4F CF Service or option not available, unspecified

Category 5 - invalid message (e.g. parameter out of range)

81 209 51 D1 Invalid call reference value

82 210 52 D2 Identified channel does not exist

83 211 53 D3 A suspended call exists, but this identity does not

84 212 54 D4 Call identity in use

85 213 55 D5 No call suspended

86 214 56 D6 Call having the requested call identity has been cleared

87 215 57 D7 User not a member of CUG*

88 216 58 D8 Incompatible destination

90 218 5A DA Non-existent CUG*

91 219 5B DB Invalid transit network selection

95 223 5F DF Invalid message, unspecified

Category 6 - protocol error (e.g. unknown message)

96 224 60 E0 Mandatory Information Element is missing

97 225 61 E1 Message type non-existent or not implemented



98 226 62 E2 Message not compatible with call state, or not implemented

99 227 63 E3 Information Element non-existent or not implemented

100 228 64 E4 Invalid Information Element contents

101 229 65 E5 Message not compatible with call state

102 230 66 E6 Recovery on time expiry

103 231 67 E7 Parameter not implemented*

111 232 6F EF Protocol Error, unspecified

Category 7 - interworking

127 255 7F FF Interworking, unspecified



27 ENotify Application Interface

This section of documentation was extracted into a separate manual dated November 2007. If you require a copy please refer to BNS Group knowledge base article A000599-110107

28 Independent Software Vendor and application

programmer integration guide

msXfax can be integrated with applications developed by Independent Software Vendors (ISV’s).

28.1 ENotify-AI approach

This method is described in the previous section. It is applicable where the application can’t send an email or where Microsoft Exchange does not exist.

Using the email based approach below is the preferred approach for software developers.

28.2 Email based approach to application integration

This is the preferred approach because the application can be anywhere on the network.



28.2.1 Application programs using domain addressing

Application programmers are encouraged to use SMTP email to send fax requests to msXfax. Specifically, domain addressing offers many advantages, the most important being the ability to route to specific fax servers via SMTP Connectors. Application programmers should provide the fax recipient name in the body of the message and use a simple domain addressing. The following Outlook message is an example of what is required to place the name of the Recipient on a default cover sheet. The reason this is required is because spaces are not allowed in email addresses and this process.

Applications can also provide the CS#<coversheet name> command to specify the exact cover sheet they wish to use.



28.2.2 Application Cover Sheets (Fax forms)

ISV’s can create any number of Fax cover sheets or use this technique to send forms as a fax.

The fax cover sheet/form is designed using Microsoft Word and saved as a RTF file.

An example word document is shown below.

The above word document (RTF format) is stored on the fax server in the coversheets folder. The values

28.2.3 Application Cover Sheets (Fax forms)

ISV’s can create any number of Fax cover sheets or use this technique to send forms as a fax. The keyword values beginning with R/- value and S/- value are reserved for applications. ISV’s can use as many values as they like to propagate the cover page/form.

The subject value can be supplied as a value in its own right or can be supplied as the in-built S-Subject keyword.

The benefit of using the S-Subject keyword for the subject is that fax confirmations which go back to the Outlook user’s mailbox will have “Fax Sent – orginal subject name” as the subject of those confirmations.

The following example using Outlook (which is an application) demonstrates to ISV’s how to compose a message from their application. This example does not have any attachments. If it did have attachments, the attachments would be constructed as additional pages of the fax transmission.



28.2.4 Keywords supported in the memo of an email

Keyword Function

FAXSENDER#name Overrides the Sender Display Name normally extracted from Active Directory and used on a Coversheet, e.g. FAXSENDER#James Smith.

CS#coversheenamet.rtf Overrides the default coversheet set and uses the specified rtf coversheet. Coversheet must be in msXfax coversheet directory, e.g. CS#sales.rtf.

[BYPASSCOVER] Stops cover page creation which includes ignoring any body text, only attachments are processed.

BC#billingcode Saves the specified billing code and applies it against this fax in the statistics database. E.g.BC#I12345

/S-keyword=value

User defined Sender keyword/value combination for use in cover pages, e.g. /S-SalesRepName=James Smith

/R-keyword=value

User defined Recipient keyword/value combination for use in cover pages e.g. /R-InvoiceNo=D12345678

[BROADCAST]

Used to signify this message is a broadcast request and contains a tif and file combination.

BROADCAST#refno Used to request a Broadcast report from the Fax Server on a specific batch where refno is the reference number of the batch in question.



28.2.5 Exchange Connector address space for ISV applications

The Exchange Connector can be configured with an address space of say “Application.fax” where “Application” can be your application’s name.



29 Systems Integration Notes

29.1 Building a lab using BRI crossover cables with Eicon

Systems Integrators are encouraged to build a lab using a 4BRI card from Eicon with 2 loopback cables. Loopback cables specifications are available from Eicon Networks.

To assist you with the set up, BNS has created a configuration file for the Eicon Diva Server card. This can be downloaded from the BNS Group web site www.bnsgroup.com.au navigate to the support section, knowledge base and search for article number W000282-070105.

URL to the article is http://mycusthelp.com/bnsgroup/supportkbitem.asp?sSessionID=&Inc=282&sFilA=Products&sFilB=Product%20Components&sFilC=&KEY=loopback

29.2 PRI crossover cables for Eicon PRI cards

Refer to http://www.eicon.com/support/helpweb/divasvr/PRIloop.htm

Build a cross over cable 1 to 4 and 2 to 5 at each end.

29.3 PRI crossover cables and PABXs

When installing the Diva Server Card behind a PBX it is sometimes necessary to use a

crossover cable. A T1 or E1 line uses pins 1,2,4, and 5. These are the 4 pins that have

to be crossed over.

Dialogic Adapter cross over for PRI can be referenced at http://www.dialogic.com/pubs/20319513.pdf



29.4 Objectives of a lab

Systems Integrators should focus on the following areas: • Become familiar with Eicon layers and concepts of a CAPI pool. • Become familiar with and configure msXfax to utilise the CAPI pool. • Send test faxes out from msXfax console and back into Exchange. • Send test faxes out from Outlook and back into Exchange/folders etc • Check audit files for both send and receive. • Load testing • Checking global catalogue access via ADSI • Checking the dynamic nature of msXfax when a GC becomes unavailable. IE:

Configure 2 GC’s in the active directory site and msXfax should continue to bind to the next available GC.

• If you are configuring a large network, perhaps configure 2 fax servers one in site A and one in Site B. Configure least cost routing if that is a requirement.

• Test any interfaces to your document / record management systems.



msXfax XPMMC Configuration

Defines 4 transmit and 4 receive

EICON DIVA SERVER PCI CARD4BRI

Line1 Line2 Line3 Line4

specialloopback

cable

specialloopback

cable

Termination typeNT=Network TerminationTE=Terminal Equipment

NT NTTE TE

Point to PointDirect Dial Inward

(DDI)=YES

Logical representation to configure msXfax XP with Eicon 4BRI card to perform lab tests with 8 concurrent fax circuits (4 transmit and 4 receive).

This is particularly useful for Systems Integrators to load test msXfax XP in their environment before migrating from existing fax services

Instructions for manufacturing cables for Eicon Basic Rate boards can be found in the Eicon Diva Server manual.

Eicon CAPI Driver presents a pool

Eicon Configuration

For answer on the interface NO YES NO YES

The Eicon Configuration file can be found at www.bnsgroup.com.au navigate to the support system and search the knowledge base.



29.5 Design considerations for high volume networks

Systems Integrators are encouraged to consider the load involved in preparing cover sheets and rendering attachments using msXfax OLE automation. Rendering of documents and string replacement on msXfax cover sheets does take time.

If you are a large customer/systems integrator with high capacity fax server design considerations, please contact BNS Group for advice and design guidelines.

29.6 Integration with Alcatel-Lucent OmniPCX office R510/23.4

Systems Integrators are provided the following information courtesy of VExpress. Extract from test report produced by Mr. Alex Boyd.

Purpose Of Report Testing was performed to check the interoperability between the BNS msXfax server using Dialogic hardware and the Alcatel OmniPCX office

Device Under Test BNS msXFax server on windows 2003 server (with SP2) connected to an OmniPCX office

Manufacturer BNS Group/Dialogic City Woden Supplier BNS Group State ACT Address1 PO Box 671 Postcode 2606

Address2 PH: 02 62312704 02 99720113

Compliance Approval

Software Version msXfax server V7.6.0 Build 323, Dialogic driver 8.3 Alcatel-Lucent OmniPCX office R510/23.4

Test Summary The testing was performed using a primary rate QSIG interface, a Basic Rate QSIG interface and an analog interface inside the fax server and the OXO. Using QSIG gives DDI capabilities and tested correctly, the analog interface gave limited incoming call options but tested correctly.

Details The BNS msXFax server was installed in a Windows 2003 server environment with SP2, also installed was Office 2007 ans Acrobat 8 The Alcatel-Lucent OmniPCX office (OXO) was fitted with the necessary boards to interface with the fax server.

First test was using the T2 (Primary rate 30B+D interface board)

The fax server was configured for QSIG PBX, TE emulation and 30 channels The number of channels is dependant on a license and needs to match the number of channels licensed in the OXO)



The OXO was configured with a DLT2 (QSIG) board configured in Network mode with 30 channels activated. To achieve this a license is required for QSIG private networking and the required number of Private T2 B-channels (this can be from 1 to 30)

The OXO was configured to use 7xx as an ARS prefix to allow calls via the ARS towards the Fax server. The Numbering Plans were set as required to allow incoming and internal calls to reach the fax server. The private numbering plan was configured to allow the fax server to make calls out of the system (0 for an outside line and the subscriber range within the system (although this is not really necessary except for test purposes or if a fax is to be routed to a physical fax machine within the OXO.)

Once connected calls to and from the fax server were successful

Secondly the configuration was tested using a T0 (Basic Rate or 2B+D interface board)

The fax server was configured for QSIG PBX, TE emulation and Layer 2 connection mode was set to permanent.

The OXO was configured with a BRA4 (MIX cards do not support QSIG in Network mode) The third circuit was changed to provide QSIG protocol and Network mode, this then causes the fourth BRA circuit to be configured the same way (QSIG/Network).

To achieve this a license is required for QSIG private networking and the required number of Private T0 B-channels (1 or 2 per circuit, 2 highly recommended per circuit to allow higher efficiency)

A cross over cable was necessary to get layer1/2 connection with the fax server (The cross over is pins 4/5 TX Fax end to pins 3/6 OXO end and pins 3/6 R/X Fax end to pins 4/5 OXO end)

The numbering configuration was the same as for the T2 test and worked successfully

Thirdly the configuration was tested using an analog interface in the Fax server connected to an SLI circuit in the OXO

No special configuration was required in the Fax server The OXO used standard SLI ports with no special configuration (It is recommended to remove the mailboxes to stop

message wait from being sent to the fax server, if possible it would be better to set up the required circuits as copies of the

FAX subscriber , 1st analog by default) In analog mode it is possible to configure the fax server to distibute calls on the separate analog circuits.

Each circuit can therefore be setup in the OXO to call distribute to different SLI ports to allow pseudo fax machine

emulation (eg Sales, Support, Marketing, etc)

The testsing proved successful.

To further test the BNS msXFax/OXO interoperability the following VoIP tests were attempted.

Two systems were configured with VoIP using H323 site to site.

The Fax server was connected to site A, and analog fax was connected to site B

These tests were performed using both the QSIG interfaces and the analog interfaces

The codec for the VoIP was set to G711 (no compression and T38 was activated)

Faxes sent from the analog fax machine to the fax server switched via the VoIP network connected and were successful at



14400bps.

Due to the type of fax machine used (read cheap here!) the faxes sent from the fax server to the machine connected and

were successful at 9600bps

The codec was then reduces to G729.a (8k compressed, recommended for WAN connectivity)

Again the same results were found.

All tests to and from the BNS msXFax server were successful.

For further information regarding this report contact 1300 888 647



30 Monitoring

30.1 msXfax System Tester

This is an add-on service provided to customers to automate the generation of a test fax message to ensure that all components that make up your solution is working.

30.1.1 Installation

Locate “msxsystestsetup.exe” in the software installation folder.



Run it on the fax server you want to generate tests to. It can be installed anywhere but with multiple fax servers it makes it easier to manage if it is installed on the server you want to test with.

Proceed through to the Finish wizard.



Select no to restart Go to Services

Start the Service to create an INI file. Stop the Service.

30.1.2 Edit INI file

Edit the ini file.



SmtpHostIp – set this to your SMTP IP or DNS FrequencyInMinutes – Set this to 240 to produce a test message every 4 hours. SenderEmailName – this can be left as is. SenderEmail – set this to a legitimate email address as the sender from your

system. ToRecipientEmail – Set this to a msXfax supported address eg:

[email protected] CCRecipientEmail – Set this to your own address if you require a copy of the

automated submission as it was sent to your SMTP Server. Example INI file

Start the Service and set the service to start automatically.



30.1.3 Attachments to render

Simply use the samples images for rendering or replace them with your own Word files, JPG, PDF etc.

30.1.4 Changes made require a restart of the service

If you change any settings, just restart the service to read the new values.

30.2 Log file data

Detailed SMTP logs show SMTP dialog for each submission.



30.1 Procedure to update to new versions

Stop the service msXfax System Tester. Run the new setup Start the service

30.2 Procedure to remove msXfax System Tester

Stop the service msXfax System Tester. Remove the existing version via control panel (ADD/REMOVE) Remove the folders if required.