Installation, administration
& user guide
Software version msXfax 7.6 build 357
Documentation version 7.6 rev 357
Installation, administration and user Guide
© Copyright 1996 to 2011 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.
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 27
1.3 Checklist for New Installations only 28
2
Introduction
30
2.1 Architecture 30
2.1.1 High Level diagram: the boxes 31
2.1.2 Software components 32
2.1.3 Message flow diagram 33
2.2 Quick Start Guide for the technical gurus 34
2.2.1 Can I test msXfax without a fax board? 34
2.2.2 Can my Outlook Web Access users send & receive faxes? 34 2.2.3 Do I have to put FaxEnabled into every user‘s AD record? 36 2.2.4 Can I use a Security Group to control access to a fax server? 36 2.2.5 Does msXfax Security Group access controls support nested
security groups? 36
2.2.6 I want all users to be able to send faxes, should I use the Fax
Enabled Security Group? 37
2.2.7 Do I need to authorize inbound fax using the Fax Enabled
options? 37
2.2.8 Is msXfax affected by anti-virus software products? 37
2.2.9 Does msXfax run on Windows Server 2003? 37
2.2.10 Does msXfax run on Windows Server 2008 64bit? 38
2.2.11 Does msXfax support Exchange 2003 Server? 38
2.2.12 How does msXfax handle failures in Exchange 2003 Server? 38 2.2.13 How does msXfax handle failures in Global Catalog
Servers? 38
2.2.21 Where do I install the fax software? 39
2.2.22 Can I install msXfax on a Domain Controller? 39
2.2.23 Can I install msXfax on a Virtual Machine? 39
2.2.24 Is FAX address space supported? 39
2.2.25 Can I install msXfax on a server which has SQL server? 39
2.2.26 Can msXfax work with Teleform software? 40
2.2.27 Where do I install the Dialogic Diva Server board? 40
2.2.28 What Exchange Service packs and registry considerations
are there? 40
2.2.29 What permissions do I need to install msXfax? 40
2.2.30 What permissions does the fax administrator need? 40
2.2.31 Does msXfax Messenger Service need to logon with account
permissions? 41
2.2.32 Does msXfax Print Service need to logon with account
permissions? 41
2.2.33 What end user security considerations are there? 41
2.2.34 What do I install on my users‘ PC? 41
2.2.35 What do I need to know about Active Directory ? 42
2.2.36 I have msXfax 5.0x, how do I migrate to msXfax? 42
2.2.37 Where do I get help? 42
2.3 Configuration options & capacity planning 43
2.3.1 Theoretical sizing of a fax server 43
2.3.2 Practical sizing of a fax server 43
2.3.3 Small to medium installations with direct inbound routing. 45
2.3.4 Larger installations with direct inbound routing. 48
2.3.5 Which Dialogic Diva Server board should I buy? 49
2.3.6 Can I set up a load test with Dialogic boards with loop back
cables? 50
2.3.7 Connecting Dialogic Diva Server to PBX‘s 50
2.3.8 PBX least cost routing over IP networks 50
2.3.9 Connecting Dialogic Diva Server to Cisco IGX WAN Switch 50
2.3.10 ISDN Line ordering specifications Basic Rate(s) 51
2.3.11 30 channel 2MB ISDN Line ordering specifications 51
2.3.12 North American Primary rate Line ordering specifications
Primary rate 52
2.3.13 North American channelized T1 connection Line ordering
specifications 53
2.4 Dialogic (Dialogic Networks) Inc Contacts 54
2.5 Government Security? 54
2.5.1 Security provisions – Eicon and msXfax 54
2.5.2 T.30 Fax and Modem communications 55
2.5.3 Diva Server adapters - general call handling 55
2.5.4 Diva Server adapters - Fax call handling 56
2.5.5 Installation and Configuration Security 56
3
Installation pre-requisites & considerations
58
3.1 Pre-requisites of your Exchange 2007 Server 58
3.2 Pre-requisites of your Exchange 2003 Server 58
3.2.1 Domain considerations 58
3.2.2 Schema 59
3.2.3 Exchange Server Service pack considerations 60
3.2.4 Exchange Server Registry Key addition 60
3.3 Pre-requisites of your fax server 61
3.3.1 Fax Server computer 61
3.3.2 Fax Server software 62
3.3.3 Direct InBound Fax Routing Utilizing PBX DTMF Tones
with selected Loop-Start Boards 62
3.3.4 Dialogic Diva Server Boards 63
3.4 Inter-operability with other applications 64
3.4.1 Finance One from Technology One 64
3.4.2 SAP Connectivity Exchange 2003 64
3.4.3 Connectivity to Alcatel OmniPCX 65
4
Configuring Exchange Server 2007/2010
65
4.1 Exchange limitations Outlook Business Fax Contacts 65
4.2 Exchange topology notes 66
4.3 Set up when msXfax will communicate with a Hub
Transport Server role 67
4.4 SMTP Communications to Exchange from msXfax 67
4.5 Create a send connector for msXfax 74
4.6 Verify Connection from msXfax to Exchange 82
4.7 msXfax Service Account 85
4.7.1 Change msXfax mailbox POP3 protocol settings 89
site/connector 103
5.4 Exchange POP3 Service 103
5.5 Service Account for msXfax Printing 104
6
Preparing your fax server
105
6.1 Installation on Windows Server 2003 32 bit 105
6.2 Permissions for a member fax server 108
6.3 Permissions required when installing msXfax on a Domain
Controller 109
6.4 Anti-virus software 111
6.5 Installation of Microsoft Office 112
6.5.1 Office 2007 installation section 113
6.5.2 Office 2003 installation section 114
6.6 Configure the Microsoft Office Document Image writer 117
6.7 Optional: Installation of Adobe Acrobat Software 118
6.7.1 Installing Adobe Acrobat Professional full product 118
6.8 Installing support for MAX Compress / Winzip 122
7
Installing Dialogic Diva Server boards
123
7.1 Installing Dialogic Diva Server board(s) 123
7.2 Obtaining Dialogic Diva Server software 123
7.3 Installing the Dialogic Diva Server software 124
7.3.1 Customers upgrading from Dialogic Diva Server version 6.x 124
7.3.2 New Installations of Dialogic Diva Server software 124
7.3.3 Diva Server Configuration Wizard 124
7.4 Configuring a Diva Server ISDN adapter 129
7.5 Configuring a Diva Server Pri adapter 133
7.6 Configuring a Diva Server Analogue adapter 135
7.6.1 Inbound routing using DTMF routing from PABX systems 138
7.7 Saving your configuration 138
7.8 Testing a Diva Server adapter 139
8
Dialogic Fax over IP solutions
141
9
Upgrading your msXfax software
142
9.1 Special notes for existing customers 142
9.2 Upgrading to release 7.0 and above 142
9.3 Upgrade procedure for non Exchange environments 142
9.3.1 Before you start the upgrade 143
9.3.2 Upgrade Dialogic Drivers 143
9.3.3 Upgrade msXfax installation files 143
9.3.4 Upgrade msXfax with the MSXSETUP.EXE 143
10
Initial Installation Files
146
10.1 Installing the installation files 146
11
Installing msXfax on your Exchange server
147
12
Installing msXfax
148
12.1.1 Login to the Domain & Permissions 148
12.1.2 Run the Setup program 148
12.1.3 msXfax Print Service 158
13
msXfax configuration overview
160
13.1 Permissions & Security 160
14.4.1 msXfax System Attendant 168
14.4.2 msXfax Routing Engine 169
14.4.3 msXfax Messenger 171
14.4.4 msXfax Dispatcher & Fax Queues 175
15
Send a test fax and some useful utilities
177
15.1 msXfax Utilities 177
15.1.1 Abort Broadcast 179
16
Active Directory Integration
181
16.1 Introduction 181
16.1.1 Quick setup all users can send a fax without automatic
cover sheets 181
16.1.2 Quick setup all users can send a common automatic cover
sheet 182
16.1.3 Global cover sheet based on sender‘s email address 185
16.1.4 Other global default options 186
16.2 Fax Server Access Controls 187
16.2.1 Adding an OU to the local domain where the fax server
accesses AD 188
16.3 Keywords & authorization to send a fax using Notes Field 194
16.3.1 Routing to Distribution Groups 198
16.4 Enterprise security & controls 200
16.5 Security recommendations 201
16.6 Active Directory Performance Settings 201
16.6.1 How to reduce the number of queries to GC‘s 202
16.6.2 Usage of Static GC option 204
16.6.3 More information on Special Inbound Processing 204
17
Global Fax Settings
210
17.1 Introduction 210
17.1.1 Global Fax Server Permissions and Cover Page Settings 211
17.1.2 Fax Server 212
17.1.3 User Feedback 213
17.1.4 Message Limits 214
17.1.7 Scenario 217
17.1.8 Compress or Rebuild Fax Database 226
17.1.9 Manage Fax Confirmation Templates 228
17.1.10 Reports 231
17.1.11 Automatic Reporting 232
17.1.12 Quick access to fax server statistics 234
18
msXfax Enhanced Security Edition
235
18.1 Permitted Security Classifications 236
18.2 Agency support details 236
18.1 msXfax generated messages 236
19
Dialing Rules and Least Cost Routing (LCR)
237
19.1 Introduction 237
19.2 Least Cost Routing (LCR) 238
19.3 msXfax Setup routines 238
19.4 Dialing Rules 238
19.4.1 Dialing Rules Level 1 - Exceptions 240
19.4.2 Dialing Rules Level 2 – International 241
19.4.3 Dialing Rules Level 3 – Local Calls 241
19.4.4 Dialing Rules Level 4 – Long Distance 242
19.4.5 Dialing Rules Level 5 – Absolute number (Freeform) 242
19.4.6 USA example showing 2 area codes (781 and 617) in Boston 242 19.4.7 USA example area code 781 Boston with a LCR to a fax
server in Hong Kong 244
19.5 Other facilities of dialing rules and LCR 248
19.5.1 Build a list of remote fax servers 248
19.5.2 Build a list of fax number masks 248
19.5.3 Build a list of test fax numbers 249
19.5.4 Request a remote dialing rules view from remote fax servers 249
19.5.5 Delete a Dialing Rule View 250
19.5.6 Test Dialing Rules 250
19.5.7 What to do if you decide to change an IP address on a fax
20.2.1 Static Cover Page 253
20.3 Cover Page Editor Overview 259
20.3.1 Cover Page tool features 259
20.3.2 The Keyword Tag definition is made up of two parts : 261
20.4 Using the Cover Page Tool 262
20.4.1 Configuration 262
20.4.2 Use of tables in RTF cover page files 262
20.4.3 Keywords 263
20.4.4 Open a sample Cover Page file msXcover.rtf 263
20.4.5 Test your Cover Page 265
20.5 How does msXfax handle text from Outlook 266
20.6 Fax Server cover page keywords 267
20.7 Management of cover sheets in large enterprises 271
21
Other configuration elements and options?
272
21.1 Changing confirmation messages 272
22
Configuring Exchange/AD for other tasks
273
22.1 How to route a fax to a user using DDI values 273
22.2 Creation of Active Directory Fax Contacts 273
22.3 How to route inbound faxes to a public folder 276
22.3.1 Create a Distribution Group which includes a public folder 278
22.4 Routing inbound faxes to external contacts 284
22.5 Inbound Printing Configuration 287
23
Fax Server Management
289
23.1 Windows Terminal Services and other products 289
23.2 System Center Operations Manager (SCOM) 2007 290
24
How do my users use the system?
291
24.2 Addressing & Sending faxes 293
24.2.1 Outlook Contacts 293
24.2.2 Outlook Contacts using msXfax Domain Addressing 295
24.2.3 Send a Word document example 296
24.2.4 Sending faxes when using Microsoft Word 298
24.2.5 Outlook public folder Contacts 299
24.2.6 msXfax Domain Addressing 299
24.2.7 msXfax free form addressing 300
24.3 Faxing from Windows Applications 302
24.3.1 How to set up Microsoft Office Image Writer 302
24.3.2 Print from your application 303
24.4 Broadcast faxing 305
24.4.1 Installing Microsoft Office Document Image Writer 306
24.4.2 Configure the Microsoft Office Document Image writer 308
24.4.3 Set up of your Excel CSV file 310
24.4.4 Set up a broadcast document 310
24.5 Receiving faxes 313
24.6 Special commands 314
24.6.1 Passcodes 314
24.7 Manual Selection of Cover Page 315
25
Removing msXfax
316
25.1 Exchange Server considerations 316
25.2 Removing msXfax from the fax server 317
25.3 How to remove msXfax if WISE fails to correctly remove
msXfax 317
25.3.1 First and preferred option 317
25.3.2 Removal via a re-install 317
26
Management, Troubleshooting & error messages
319
26.1 Database maintenance 319
26.2 msXfax data flow diagram 323
27
ENotify Application Interface
328
28
Independent Software Vendor and application programmer
integration guide
328
28.1 ENotify-AI approach 328
28.2 Email based approach to application integration 328
28.2.1 Application programs using domain addressing 329
28.2.2 Application Cover Sheets (Fax forms) 330
28.2.3 Application Cover Sheets (Fax forms) 330
28.2.4 Keywords supported in the memo of an email 331
28.2.5 Exchange Connector address space for ISV applications 332
29
Systems Integration Notes
333
29.1 Building a lab using BRI crossover cables with Dialogic 333
29.2 PRI crossover cables for Dialogic PRI cards 333
29.3 PRI crossover cables and PABXs 333
29.4 Objectives of a lab 334
29.5 Design considerations for high volume networks 336
29.6 Integration with Alcatel-Lucent OmniPCX office R510/23.4 336
30
Monitoring
339
30.1 msXfax System Tester 339
30.1.1 Installation 339
30.1.2 Edit INI file 341
30.1.3 Attachments to render 343
30.1.4 Changes made require a restart of the service 343
30.2 Log file data 343
30.1 Procedure to update to new versions 344
Table of tables
Table 1: Technology upgrades that take advantage of Microsoft‘s new
platform 30
Table 2: Dedicated Fax Server computer specifications 61
Table 3: Fax Server software specifications 62
Table 4: msXfax support attachment extension types 112
Table 5: msXfax keywords and their usage 196
Table 6: msXfax utilization of AD 225
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 31
Figure 2: Software architecture: high level implementation block diagram
showing key Microsoft technologies used by msXfax. 32
Figure 3: High level diagram Exchange Server & msXfax Fax Server 107 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. 262
Figure 5: Open the sample cover sheet 264
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 Suncorp Group‘s messaging and collaboration team – thanks.
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 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 - Dialogic Networks Malaysia.
To Barry Ho, Dialogic & 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
357 patches designed to be overlaid on top of build 356.
msXfax 7.6 b357 12th Jan 2011
Rework algorithm to remind Administrator that software is expiring. A new version of msXAttendant.exe will create registry entry in the msxfax root called AlertLicenseFrequency containing values 90,60,30,10,9,8,7,6,5,4,3,2,1.
To force the Attendant to perform a license check find the file called licdiag.ok in the msxfax XP\programs directory. This file should be renamed to licdiag to process an on demand alert message to the configured Administrator. msXfax has support for alerts to be sent to an alternate address and alternate
SMTP Server. Set these values viaregistry msxfax Xp root AltAlertEmail and AltSMTPServer.
Fix Bug in msXPrintSpool.exe where if a print of a tiff file in most cases a tiff file with only a header occursthe msxprintspool.exe task will not delete the offending file but continue to process and fail. Thisfix deletes the offending control and tiff file and continues.
msxfax 7.6 b357 27th Sept 2010
Strip * in DDI in msXdispatchRXIn.exe. Found * appearing in DDI coming from a PBX in bisk education.
msxfax 7.6 b357 22nd April2010
Updated msxfaxout.exe to handle situation where Acrobat rendering fails and pdf document is still locked by Acrobatprocess. Process need to be terminated so further rendering can continue.
msxfax 7.6 b357 4th March 2010
Updated msxfaxout.exe to check that all work files in the converter directory are purged before starting to process eml files. If files cannot be deleted an error is logged and the task terminates. It is hoped any locked files are released and subsequently deleted.
not be used and the mailbox will not be checked.
This is to enable customers who use only SMTP domain address to avoid using POP3.
Customers who use least cost routing or load balancing will require POP3 mailbox processing in their design using msXfax 7.6.
List of 357 patches
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=73 5&caller=%7e%2fFindAnswers.aspx%3ftxtCriteria%3dtechnical+bulletin%26sSessio nid%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
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
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.
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
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 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 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 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 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 Dialogic 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.
---
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 Dialogic 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 Dialogic 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 andprint 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 beingcontactable 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 8is 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 Dialogic Diva Server. - Drop support for TAPI Modems and Brooktrout boards. This release
supports Dialogic 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 Dialogic 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
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 Dialogic Analogue card
- The Channel No is mapped to a DID value so the DID logic inplace will work.
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 Dialogic Diva Server boards must download Dialogic Diva Server software version drivers as described in this manual. ALL customers should complete the
configuration of Dialogic 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
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 Dialogic Diva Server boards and Dialogic drivers Section 7
If using SoftIP (Fax over IP) then install Dialogic 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 Dialogic 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.
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
Exchange
Server
(or Exchange cluster)
10.1.1.1
C o m 3Local Area
Network
Windows 2003
Member server
msXfax XP
Fax Server
10.1.1.3
Telephone
network
msXfax can be installed on: Windows Server 2003 32 bit domain controllers or member servers.
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 System Attendant
msXfax Messenger
msXfax Fax Device Drivers
ADO, ADSI, LDAP Office
Adobe Acrobat full product (optional)
Active Directory Services Standard Exchange
SMTP Connector
msXfax Windows 2003 Fax Server
Member Server
Exchange Server(s)
(or a cluster)
Exchange POP3 Virtual Server Other Exchange components msXfax Routing Engine
SMTP
POP3
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).
2.1.3
Message flow diagram
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.
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).
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?
2.2.17
Can I install msXfax on an Exchange 2007/2010 server?
Not supported2.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 (Dialogic) 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.
msXfax has been tested on a system which has Teleform and SQL server.
2.2.27
Where do I install the Dialogic Diva Server board?
Installation of Dialogic board(s) is on the fax server where you intend to install msXfax software. Dialogic Networks is now called Dialogic.
All Dialogic 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
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?
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.
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 120 pages per hour This is theoretical only.
3 180 pages per hour This is theoretical only.
4 240 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.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.
Dialogic 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
Dialogic 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 Dialogic’s analogue card with msXfax and a PBX system.
SD COMPAQ WARNI NG SD SYSTEM RPS1x2x3x4x5x6x7x8x9x10x11x12x13x 14x15x16x17x18x19x20x21x22x23x24x 10BaseT MODE CISCO YSTEMSS ® UTLFDUP STAT Catalyst 1900 AxBx 100BaseTX LAN Switch Exchange Server
line solution
Network layer DDI inbound routing & outbound faxing
Eicon BRI 2M (single basic rate) equal to 2 fax lines
ISDN networks eg: Britiish Telecom Euro ISDN-2 services
Telstra On Ramp 2 etc 1 physical connection = 2 fax lines
SD COMPAQ WARNI NG SD SYSTEM RPS1x2x3x4x5x6x7x8x9x10x11x12x13x 14x15x16x17x18x19x20x21x22x23x24x 10BaseT MODE CISCO YSTEMSS ® UTLFDUP STAT Catalyst 1900 AxBx 100BaseTX LAN Switch Exchange Server
msXfax XP fax server using Eicon Networks ISDN basic rate 4 fax
line solution
Network layer DDI inbound routing & outbound faxing
Eicon BRI 2M (single basic rate) equal to 2 fax lines
ISDN networks eg: Britiish Telecom Euro ISDN-2 services
Telstra On Ramp 2 etc Eicon BRI 2M
(single basic rate) equal to 2 fax lines
SD COMPAQ WARNI NG SD SYSTEM RPS1x2x3x4x5x6x7x8x9x10x11x12x13x 14x15x16x17x18x19x20x21x22x23x24x 10BaseT MODE CISCO YSTEMSS ® UTLFDUP STAT Catalyst 1900 AxBx 100BaseTX LAN Switch Exchange Server
msXfax XP fax server using Eicon Networks ISDN basic rate 8 fax
line solution
Network layer DDI inbound routing & outbound faxing
Eicon 4BRI 8M (single board with 4
basic rate connections) equal to 4 fax lines
ISDN networks eg: Britiish Telecom Euro ISDN-2 services
Telstra On Ramp 2 etc 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.
Dialogic 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.
S D C O M P A Q W A R N I N G SD SYSTEM RPS 1x2x3x4x5x6x7x8x9x10x11x12x13x14x15x16x17x18x19x20x21x22x23x24x 10BaseT MODE CISCO YSTEMSS ® UTL FDUP STAT Catalyst 1900 Ax Bx 100BaseTX LAN Switch Exchange Server
msXfax XP fax server using Eicon Networks ISDN Primary Rate Up
to 30 channels (E1) or 24 channels (T1)
Full length Dialogic (Eicon) Diva
Server card ISDN network or compatible
