Winscribe Installation Guide · 2013-10-31 · 7 About this Guide This guide describes how to...

Copyright ©2013, Winscribe Inc. All rights reserved.

Publication Date: October 2013

Winscribe Installation Guide

4.2

2

Copyright© 2013 Winscribe Inc. All Rights Reserved.

Portions of the software described in this document Copyright© Microsoft Corporation. All Rights Reserved. Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those agreements. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical or photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Winscribe Inc.

Winscribe® is a registered trademark of Winscribe Inc. in New Zealand and other countries. Microsoft is a registered trademark, Windows NT and Windows is a trademark of Microsoft Corporation. Dragon NaturallySpeaking® is a trademark of Nuance, Inc. and is used here under license. Other brands and their products are the trademarks or registered trademarks of their respective holder and should be noted as such.

Winscribe Inc. P.O. Box 33-178 Takapuna Auckland New Zealand Email: [email protected] Visit our web page: http://www.winscribe.com

3

Contents

Contents

About this Guide ................................................................................................................................ 7

Overview of Manual Contents ...................................................................................................................................... 7 Other Documentation ............................................................................................................................................. 7 Who should read this manual? ............................................................................................................................... 8

Chapter 1. Installing Winscribe Server Components ............................................................................ 9

Section 1: Introduction and Installation Summary ....................................................................................................... 9 Winscribe Server Requirements ............................................................................................................................ 10 LAN / WAN & Internet Bandwidth Requirements ................................................................................................. 12 Dictation Storage Requirements ........................................................................................................................... 16 Dialogic Telephony Hardware Requirements ........................................................................................................ 17 Choosing a Dialogic Card ....................................................................................................................................... 17 ISDN Telephony ..................................................................................................................................................... 19

Section 2: SQL Server Database Software ................................................................................................................... 20 Microsoft SQL Server Express or SQL Server ......................................................................................................... 20 SQL Configuration Settings .................................................................................................................................... 21 Running SQL Server 2005 or SQL Express on Windows Server 2008 or Windows Vista Operating Systems ........ 21 Changing SQL Credentials ..................................................................................................................................... 21 Transferring an Existing MSDE Winscribe Database to a New SQL Server ............................................................ 22 Running Winscribe with a SQL Named Instance ................................................................................................... 22

Section 3: Installing Winscribe Server ......................................................................................................................... 23 Prerequisites for the Winscribe Server Installation .............................................................................................. 23 Step 1 Install Dialogic Telephony Boards .............................................................................................................. 24 Step 2 Install the Dialogic Drivers .......................................................................................................................... 24 Step 3 Configure the Dialogic Boards .................................................................................................................... 28 Step 4 Install Microsoft .NET 4 .............................................................................................................................. 30 Step 5 Install the Winscribe License Server ........................................................................................................... 30 Step 6 Install the Winscribe Dictation Server Software ........................................................................................ 33 Configuring Share Properties ................................................................................................................................ 43 Step 7 Install the Winscribe Web Components ..................................................................................................... 45 Web Components and Primary Server on Different Boxes ................................................................................... 49 Using Distributed Audio ........................................................................................................................................ 49 Using Self-signed SSL Certificates with Winscribe ................................................................................................. 51

Section 4: Installing Winscribe on Windows 2003 Server ........................................................................................... 51 Prerequisites for Windows 2003 Server ................................................................................................................ 51 Installation Summary for Windows 2003 Server ................................................................................................... 52 Steps 1-7 ................................................................................................................................................................ 52 Step 8 Configure IIS Server for Web Components on Windows 2003 Server ....................................................... 52 Step 9 Prepare to Install the Client applications on Windows 2003 Server .......................................................... 55 Step 10 Install the Client Applications ................................................................................................................... 56 Troubleshooting Winscribe Installation on Windows 2003 Server ....................................................................... 56

Section 5: Installing Winscribe on a Microsoft Windows 2008 Server ....................................................................... 57 Installation Summary for Windows 2008 Server ................................................................................................... 57 Step 1: Turn on Network Discovery....................................................................................................................... 57 Step 2: Install Required IIS Features ...................................................................................................................... 58 Step 3: Install Winscribe ........................................................................................................................................ 61 Step 4: Install Desktop Experience ........................................................................................................................ 62

Section 6: Installing Winscribe on a Microsoft Windows 2012 Server ....................................................................... 62 Installation Summary for Windows 2012 Server ................................................................................................... 62 Step 1: Configure Advanced Sharing Options ....................................................................................................... 62 Step 2: Install Required IIS Features ...................................................................................................................... 63

4


Step 3: Install Winscribe ........................................................................................................................................ 65 Step 4: Install Desktop Experience ........................................................................................................................ 65

Section 7: Installing Winscribe on 64-bit Operating Systems ..................................................................................... 66 Enabling 32bit Microsoft.NET on Server 2003 64bit ............................................................................................. 67 Registry Locations ................................................................................................................................................. 67

Section 8: Installing Winscribe ATS ............................................................................................................................. 68 Introduction .......................................................................................................................................................... 68 Step 1 Install ATS Prerequisites ............................................................................................................................. 69 Step 2 Install ATS ................................................................................................................................................... 69 Step 3 Configure ATS ............................................................................................................................................. 71 Step 4 Configure Advanced Review ...................................................................................................................... 77 Step 5 Beyond Advanced Review .......................................................................................................................... 77

Section 9: Installing Winscribe Voice over IP (VoIP) ................................................................................................... 82 HMP Software ....................................................................................................................................................... 82 HMP Licensing ....................................................................................................................................................... 83 Installation Overview ............................................................................................................................................ 83 Installation Option One: New Install ..................................................................................................................... 83 Installation Option Two: Existing Winscribe Dictation Server without Telephony ............................................... 86 Configuring the IPPhone Service ........................................................................................................................... 86

Section 10: Post Installation Steps & Licensing ........................................................................................................... 88 Licensing your Winscribe Software ....................................................................................................................... 89

IIS File-size Limit .......................................................................................................................................................... 91

Chapter 2. Installing Winscribe Server Manager Applications ............................................................ 92

Section 1: Winscribe Telephony Manager .................................................................................................................. 92 Configuring Telephony Manager ........................................................................................................................... 94

Section 2: Winscribe Web Manager ........................................................................................................................... 96 Installation Summary ............................................................................................................................................ 96 Installation Configuration ...................................................................................................................................... 96 Minimum Hardware and Software Requirements ................................................................................................ 96 Install Prerequisites ............................................................................................................................................... 97 Installing Winscribe Web Manager ....................................................................................................................... 98 Next Steps ........................................................................................................................................................... 105 Configuration of the Job Upload functionality .................................................................................................... 105 Setting up Database Mail for use with Alarm Email Notification and Workflow Email Notification................... 107

Section 3: Winscribe Exporter................................................................................................................................... 110 Installation Summary .......................................................................................................................................... 110 Installation Configuration .................................................................................................................................... 111 Minimum Hardware and Software Requirements .............................................................................................. 111 Install Prerequisites ............................................................................................................................................. 111 Installing Winscribe Exporter Service & Manager ............................................................................................... 114 Next Steps ........................................................................................................................................................... 117

Section 4: Winscribe Active Directory Synchronization ............................................................................................ 117 Single Sign-on Configuration ............................................................................................................................... 118 Active Directory Settings ..................................................................................................................................... 118 Installing the Winscribe Active Directory Synchronization Tool ......................................................................... 118 Configuring the Winscribe Active Directory Synchronization Tool ..................................................................... 119 Server 2003 — Authentication Methods ............................................................................................................ 120 Server 2003 R2 SP2 — Authentication Methods................................................................................................. 126 Server 2008 — Authentication Methods ............................................................................................................ 129 User Accounts Mapping ...................................................................................................................................... 134

Section 5: Installing Winscribe Internet Importer as a Windows Service ................................................................. 135 Configuring the Temp Folder when Importer is run as a Windows Service ........................................................ 138

Chapter 3. Installing Client Applications ......................................................................................... 139

5

Contents

Section 1: Features and Prerequisites ...................................................................................................................... 139 Minimum Requirements: Winscribe Author, Winscribe Client, Internet Author and Importer ......................... 140

Section 2: Client Deployment Guidance ................................................................................................................... 141 Overview ............................................................................................................................................................. 141 Command Line .................................................................................................................................................... 141 Configuring Client Installer Properties ................................................................................................................ 142 Installer Properties .............................................................................................................................................. 143 Logging ................................................................................................................................................................ 145

Section 3: Installing Winscribe .................................................................................................................................. 146 Setting Installation Parameters ........................................................................................................................... 146 Automatic Deployment of Scripts ....................................................................................................................... 148 Author/Client Grid Layout ................................................................................................................................... 151

Section 4: Installing Internet Importer (Standard Windows Application) ................................................................ 153 Configuring the Temp Folder when Importer is run as a Windows Application ................................................. 155

Section 5: Configuring Web Installation ................................................................................................................... 155 Section 6: Installing Winscribe Author, Winscribe Client, Internet Author, or Importer via the Web ..................... 156 Section 7: Customizing the Login Window................................................................................................................ 158 Section 8: Troubleshooting Client Applications ........................................................................................................ 159

Install stops responding ...................................................................................................................................... 159 Can't register components during installation .................................................................................................... 159 Winscribe Server has been shutdown for system maintenance ......................................................................... 159 SQL Server not found .......................................................................................................................................... 159 An error has occurred attempting to open the Winscribe database .................................................................. 160 Your demonstration license has expired! ........................................................................................................... 160 No Sound Card Detected! ................................................................................................................................... 160 Invalid User Id or security code ........................................................................................................................... 160 Error 502 Check your Winscribe URL .................................................................................................................. 160 Internet request failed. Web page was not found. ............................................................................................. 160 Firewall preventing data traffic ........................................................................................................................... 161 An author-reviewer can't find/access an existing job ......................................................................................... 161 Sound Card in use by another Application! ......................................................................................................... 161 No sound when playing a job or prompt............................................................................................................. 161 Nothing was recorded ......................................................................................................................................... 161 Sound volume is too low ..................................................................................................................................... 162 Typist's foot pedal doesn't work ......................................................................................................................... 162 Playback starts at the wrong location ................................................................................................................. 162 Job's Voice File not found! .................................................................................................................................. 162 Error attempting to create a new dictation! ....................................................................................................... 163 Error No Voice Server Present ............................................................................................................................. 163 Archive/save VOX files ........................................................................................................................................ 163

Chapter 4. Managing Servers ......................................................................................................... 164

Winscribe Windows Services .................................................................................................................................... 164 How to Stop/Start Winscribe Services ................................................................................................................ 164 Configuring a Windows Service to Start Automatically ....................................................................................... 164

Configuring Winscribe Telephony Parameters ......................................................................................................... 165 Timeouts.............................................................................................................................................................. 165 Hangup Tones...................................................................................................................................................... 167 Author Keys ......................................................................................................................................................... 168 Author Line Keys ................................................................................................................................................. 170 Typist Keys ........................................................................................................................................................... 172 Typist Line Keys ................................................................................................................................................... 174

Winscribe Shared Directory ...................................................................................................................................... 175 Sub-directories in the Shared Directory .............................................................................................................. 175

6


Winscribe Server ....................................................................................................................................................... 177 Shutting Down a Winscribe Server ...................................................................................................................... 178 Configuring Winscribe Web Server Settings ....................................................................................................... 179 Windows Event Log ............................................................................................................................................. 180

Troubleshooting Servers ........................................................................................................................................... 181 Winscribe Services do not appear in the Services window ................................................................................. 181 Dialogic Driver installation failed ........................................................................................................................ 181 Winscribe does not answer calls ......................................................................................................................... 182 Winscribe Server Shutdown for maintenance .................................................................................................... 182 Telephone port not disconnecting ...................................................................................................................... 182

Chapter 5. Upgrading to Winscribe Version 4.2 ............................................................................... 183

Prerequisites ............................................................................................................................................................. 183 License Files .............................................................................................................................................................. 183 Upgrade Summary for Winscribe Version 4.2 .......................................................................................................... 183 Step 1 Upgrade the License Server ........................................................................................................................... 184 Step 2 Remove LAN Manager ................................................................................................................................... 185 Step 3 Upgrade the Dictation Server ........................................................................................................................ 186 Step 4 Install Telephony Manager ............................................................................................................................ 186 Step 5 Upgrade the Web Components ..................................................................................................................... 187 Step 6 Upgrade the Client Applications .................................................................................................................... 187

Disabling the Upgrade Prompt ............................................................................................................................ 188 Step 7 Remove Discontinued Client Applications ..................................................................................................... 188 Upgrading a system with Server-side Speech Recognition ....................................................................................... 188 Upgrading a system with Exporter licenses .............................................................................................................. 188 Upgrading a system with Mobile Recorder licenses ................................................................................................. 189 Upgrading the Web Manager Author Job Upload feature ....................................................................................... 189 Upgrading a Server to Support Telephone Dictation ................................................................................................ 189 Upgrading a Server from 2.5 to 3.0........................................................................................................................... 191

Upgrade Steps ..................................................................................................................................................... 191 Troubleshooting ........................................................................................................................................................ 192

Updating the URL ................................................................................................................................................ 192

Chapter 6. Uninstalling Winscribe .................................................................................................. 194

Winscribe Server Uninstall Procedure ...................................................................................................................... 194

Appendix 1. Programming Requirements for PBX's ......................................................................... 195

Programming Requirements for PBX's With DID (Direct Inwards Dialing) ............................................................... 195 Programming Requirements For PBX's Without DID ................................................................................................ 195

Determine Disconnect Frequency ....................................................................................................................... 195

Appendix 2. ATS Keypad Functions ................................................................................................. 197

Appendix 3. Installing the Web Components (Full) .......................................................................... 201

Index ............................................................................................................................................. 212

7

About this Guide

This guide describes how to install Winscribe version 4.2.

Overview of Manual Contents This installation guide is divided into sections, as follows:

Section Description

Installing Winscribe Chapter 1. Installing Winscribe Server Software (see page 9)

This section describes the installation of Winscribe Server software for the following:

Winscribe Dictation Server (Telephony, Advanced Telephony, and Non-telephony)

Windows 2003 Servers

Windows 2008 Servers

Windows 2012 servers

Servers running Microsoft Windows Vista

64-bit Operating Systems

Winscribe ATS

Winscribe Voice over IP

Chapter 2. Installing Winscribe Server Applications Software (see page 92)

This section describes the installation of Winscribe applications that are used to work with Winscribe Servers. These include management applications such as Winscribe Web Manager and Winscribe Telephony Manager.

Chapter 3. Installing Client Applications (see page 139)

This section describes the installation of Winscribe client applications such as the Author, Client and Importer applications. These applications typically run on the end users computer.

Managing Winscribe Chapter 4. Managing Servers (see page 164)

This chapter describes how to manage servers, including stopping and starting Winscribe Services, configuring servers, and troubleshooting.

Upgrading Winscribe Chapter 5. Upgrading to Winscribe Version 4.2 (see page 183)

This section describes the process for upgrading an existing Winscribe system to version 4.2.

Uninstalling Winscribe Chapter 6. Uninstalling Winscribe (see page 194)

This chapter describes how to uninstall the Winscribe Server and Client applications.

Other Documentation For further information about specific Winscribe applications, consult the following documentation:

Winscribe Web Manager Guide

Winscribe Author, Winscribe Client, Internet Author and Internet Importer User Guides

Winscribe Speech Recognition Guide

Winscribe Exporter Guide

Winscribe Telephony Manager Guide

About this Guide

8


Before using Winscribe, it is also recommended that you check the release notes for the latest information.

Who should read this manual?

This manual is written with the assumption that you are already familiar with Microsoft Windows Systems Administration and is written for those who will install Winscribe.

9

Chapter 1. Installing Winscribe Server Components

The following chapter will guide you through the steps required to install the Winscribe Server Software. It is important that these steps are followed exactly, and that you do them in the sequence described here. Not doing so may result in the installation failing.

Note: Do not install over an existing installation unless you have first backed up all existing Winscribe files and the Winscribe database. While unlikely, this installation may overwrite custom prompts and/or the database files of an existing installation.

Section 1: Introduction and Installation Summary

Step Description Required?

1 Install Dialogic Telephony Boards (see page 24)

Only required if installing Winscribe with the telephony interface.

Note: Refer to the sections on Dialogic Telephony Hardware Requirements (see page 17), Choosing a Dialogic Card (see page 17), ISDN Telephony (see page 19), and VoIP (see page 82) for all Dialogic requirements, including Service Packs, before commencing installation.

You must install the Dialogic hardware drivers before you proceed with this installation.

2 Install Microsoft .NET 4 (see page 30)

Required if not already installed.

3 Install the Winscribe License Server (see page 30)

Always required.

4 Install the Winscribe Dictation Server (see page 33)

Always required if installing the Winscribe Server software

Unless you are:

Upgrading the server to support telephone dictation.

Upgrading from Version 2.5 to 3.0

Upgrading to Version 4.2

Note: Windows Server 2003, 2008, and 2012 require certain prerequisites be completed. Refer to Section 4 and 5 of this chapter.

5 Configure Share properties (see page 43)

Only required if changing the default Winscribe Server directory properties or installing a secondary server.

6 Install the Winscribe Web Components (see page 45)

Always required. May be installed on a server other than the Winscribe Server

7 Web Components and Primary Server on Different Boxes

Only required if you have installed the web components on a server other than the Winscribe Primary Server.

8 Install Server Applications (see page 92)

Generally required for configuration of the system.

9 Install Client applications (see page 139)

Optionally installs the Winscribe client applications.

10 Post Installation Steps and Always required.


10


Step Description Required?

licensing (see page 88)

Winscribe Server Requirements Winscribe server software has a number of components that can be installed on a single server and/ or several servers. Typically several servers are used at a large site or when redundancy is required.

Note: Winscribe will operate on VMWare and Microsoft Virtual PC/Server. However many hardware manufacturers' device drivers are not supported in these environments. Sound must be enabled on the virtual image, as follows:

If the Winscribe Server is installed on a virtual image and the Winscribe Clients are installed on a fat client, no sound card is needed on the server.

If both the Winscribe Server and the Winscribe Clients are installed on the same virtual image then a sound card must be installed.

The table below explains the various components and their operating system requirements:

Component Software Notes

Winscribe Dictation Service*

Windows Server 2003 (SP2 or higher)

Windows Server 2008

Windows Server 2008 R2

Windows XP Professional (SP2 or higher)

Windows Vista (SP1 or higher) - all versions except Home Basic and Home Premium

Always install the latest Windows service pack

Windows 2003 Small Business Server is not certified for use with Winscribe Server

Must not be installed on a Domain Controller1

Winscribe Telephony Service*


Windows Server 2008




Usually installed on the Dictation Server but can be installed on separate servers

Windows 2003 Small Business Server is not certified for use with Winscribe Server

Must not be installed on a Domain Controller1

Winscribe Telephony is not supported in virtual server environments

Winscribe Web Components*


Windows Server 2008




Winscribe Web Components are usually installed on the Dictation Server but can be installed on a separate server.

IIS is included with XP Pro but needs to be manually installed.

IIS 5 in XP only allows 10 concurrent internet-based connections. If using Winscribe Internet clients and you have more than 10 users upgrading to IIS6.0 is recommended.

11


Component Software Notes

Database Engine SQL Server Express 2005

SQL Server Express 2008

SQL Server 2005

SQL Server 2008

SQL Server 2008 R2

SQL Server 2012

SQL must be installed and available before starting the Winscribe installation.

The database engine is typically installed on the same server as the Winscribe Dictation Service, but it can be installed on another networked database server.

SQL Server 2000 is no longer supported.

Microsoft Client Access Licenses (CALs) are required for the full SQL Server editions.

See the section on SQL Server version for further details.

Security Note: To ensure that the system is protected against all known malicious attacks, it is recommended that you visit the Microsoft security website (http://www.microsoft.com/security/) and install the latest patches.

1 The networking and processor load generated by authentication and other domain controller processes can degrade IIS performance, which, in turn, will degrade Winscribe performance.

When installing Winscribe, you must be logged in to the server with local administrative rights — and this account is used to create certain registry entries, etc., necessary for the proper operation of Winscribe. Adding users to a group that can log on locally to the domain controller can increase the attack surface that is exposed by a Web application. If security is compromised on the domain controller, security is compromised on the entire domain.

* As per the Microsoft EULA, Windows XP, Windows Vista, and Windows 7, 8, 8.1 are not to be installed as production servers. As such, Winscribe server software should not be installed on these operating systems other than for purely demonstration purposes. Winscribe support is limited in these instances.

Winscribe Server Hardware & Network Minimum Requirements

The table below provides a list of the minimum hardware required for the various Winscribe Server components. Keep in mind that more memory and a faster hard drive will improve performance.

Component Hardware Notes

Winscribe Dictation Service

(Primary Server)

Pentium IV or higher

256MB ram

800MB disk space for software (not including dictation storage space)

Should be a dedicated server and must not be installed on a domain controller.

Redundant disks recommended, e.g. Raid5.

Refer to Dictation Storage Requirements (see page 16) for details on dictation storage requirements.

Security Warning: For security purposes, Microsoft recommends that all drives be formatted as NTFS. Also the working directories that are created during the Winscribe installation should be on a separate partition to the

http://www.microsoft.com/security/

12


Component Hardware Notes

operating system.

Winscribe Telephony Service

(Primary or Secondary Server)


256MB ram

PCI or ISA slot free for each telephone card

Usually installed on the same server as the Winscribe Dictation Service, however ensure 512 MB RAM is available (256 x 2). You can install this component on up to 4 additional servers (secondary servers), with a maximum 96 telephone ports per server, providing up to 480 ports in total.

Winscribe Web Components


256MB ram

Can be installed on the same server as the Winscribe Dictation Service or on the customers existing web server.

Security Warning: For security purposes, Microsoft recommends that all drives used with IIS be formatted as NTFS, also the working directories that are created during the Winscribe Web Components installation should be on a separate partition to the operating system.

Database Pentium IV or higher

256MB ram minimum

By default installed on the same server as the Winscribe Dictation Service but can be installed on a separate SQL server if desired (large sites).

Network Static IP address for each server.

100Mbit or faster network card for each server.

Public IP address if Internet clients require off-site access.

Note: Modem and remote access software is recommended for off-site support.

LAN / WAN & Internet Bandwidth Requirements

Many large organizations have sites that are spread out in various geographical locations. These sites need a way to connect and remain connected to the main or central site where the Winscribe server is located. One of these methods may also be used to connect to an ISP (Internet Service Provider) for Winscribe Internet clients who work offsite. Different wide-area-Internet connection media are used in different parts of the world. The table below describes the various wide-area technologies and their uses.

Wide-Area Technology

Definition

T1 Transmits at a speed of 1.544 Mbps, and consists of 23 B channels, which are used for data, and a 1 D channel which is used for clocking. T1 can also be fractionalized into separate 64 kilobytes per second (Kbps) segments.

E1 Used primarily in Europe. Transmits at a speed of 2.048 Mbps.

T3 Transmits DS3 data at 44.736 Mbps.

Frame Relay Packet-switched technology that is considered the replacement for X.25. Commonly runs at speeds up to T1.

Digital Subscriber Line (DSL)

DSL consists of an asymmetric digital subscriber line (ADSL), a high-data-rate digital subscriber line (HDSL), a single-line digital subscriber line (SDSL), and a very-high-data-rate digital subscriber line (VDSL).

Site connectivity can also rely on the use of dial-up mediums such as Integrated Services Digital Network (ISDN), or analog phone lines (POTS) for low traffic links.

13


Examples of Network Impact

The tables below show network impact on a T1 connection.

Note: Calculations are based on average and uniform loading of dictation throughout the day. Instantaneous loading may be higher at peak times, e.g. before lunch, before 5:00 pm.

VOX

Total System Dictations

Total Dictations Per day = 100

Average length of dictations in minutes 4

Network Impact Calculations

Total dictated minutes 400

Total dictated seconds 24,000

Total bits @32Kbps (VOX) 768,000,000

Time on T1 in Seconds

10 Mb (average speed of 1.5 Mbs) 512

Total seconds in 8 hour day 28,800

Traffic (as a percentage) impact on Net 10Mb 1.78%

GSM, Low 8khz


Total dictations per day 100

Average length of dictation in minutes 4




Total bits @ 13Kbps (GSM Low) 312,000,000

Time on T1 in seconds

10Mb (average speed of 1.5 Mbs) 208



GSM, Medium 11 kHz – (This is the default Winscribe setting).







14


Total bits @ 17.912 Kbps (GSM Med) 429,888,000


10Mb (average speed of 1.5 Mbs) 286.6



GSM, High 22 kHz







Total bits @ 35.824Kbps (GSM High) 859,776,000


10Mb (average speed of 1.5 Mbs) 573.2



Speex, Low







Total bits @20.600Kbps (Speex Low) 494,400,000


10 Mb (average speed of 1.5 Mbs) 329.6



Speex, Medium






15



Total bits @27.800Kbps (Speex Medium) 667,200,000





Speex, High







Total bits @42.200Kbps (Speex Low) 1,012,800,000





16


Dictation Storage Requirements The storage requirement for dictation will vary based on how long you wish to store completed dictation, how long the average dictation is, how quickly jobs are typed, the archive and deletion settings in the 'Job Type' profile, and the length of time archived jobs are retained. We suggest that you undertake an analysis to determine your specific requirements.

Storage Calculation Formula

The above formula will determine an average storage requirement for your organization.

Example

Parameters:

The compressed Dialogic ADPCM format requires 240kb per minute of disk storage space

Parameters (specific to this example):

A typical author produces an average of 25 minutes of dictation per day

The storage period is two weeks (10 working days)

There are 16 authors

Calculation:

((240 x 25) x 10) x 16 = 960000

Result:

The example's parameters will require an average 0.96 GB of storage space.

Disk Storage Requirement Table

Format One Hour One Minute

Compressed Dialogic ADPCM 14 MB 240 KB

Vox (8 kHz) 13.73 MB 228 KB

GSM Low (8 kHz) 5.5 MB 95 KB

GSM Medium (11 kHz) 7.69 MB 131 KB

GSM High (22 kHz) 15.37 MB 262 KB

Speex Low (16 kHz Quality = 6) 8.84 MB 147 KB

17


Speex Medium (16 kHz Quality = 8) 11.93 MB 199 KB

Speex High (16 kHz Quality = 10 18.11 MB 301 KB

Dialogic Telephony Hardware Requirements Following are the requirements for each Dialogic Telephony port you have installed on Winscribe:

Each Winscribe telephone port (Dialogic port) requires an analog extension port either on your PBX or directly on the PSTN (telephone exchange).

The analog extensions for the Winscribe ports should be terminated with RJ-11 sockets. Refer to the documentation supplied with the Dialogic cards for wiring details.

Fly-leads are required from the RJ-11 sockets to the Winscribe ports. These should be terminated using male RJ-11 plugs.

Choosing a Dialogic Card Winscribe supports analog Dialogic cards. Winscribe is shipped with Dialogic DNA 6.0 Drivers that support the following cards:

DIALOG/4: Half-size, 4-port ISA voice board

ProLine/2V: 2/3 size, 2-port ISA voice board

D/21D: 2- port ISA voice board

D/41D: 4- port ISA voice board

D/21E: 2- port ISA voice board

D/41ESC: 4-port ISA voice board

D/21H: Half-size, 2-port ISA voice board

D/41H: Half-size, 4-port ISA voice board

D/160SC-LS: 16-port ISA voice board

D/4 PCIU: Half-size, 4 port PCI voice board (Note: See also Service Packs (see page 18).)

D/4 PCIUF: 4 port voice and fax board

D/41EPCI: 4-port PCI voice board

D/120JCT-LS: 12-port PCI voice board (requires PCI bus cable with multiple boards)

We recommend using PCI cards for ease of installation. The card(s) you choose will depend on the number of ports required, and the approval status of the cards in your country (Telecommunications Regulatory Body approval). Consult the Dialogic web site (http://www.dialogic.com) for up-to-date approval information.

PCISIG Specification for Universal PCI

From 2003 onwards, Motherboard specifications for PC's and Servers utilize a new specification for Bus Compatibility. PCI Slots now contain at least one PCI-X slot for Universal PCI cards. PCI-X conforms to PCISIG Bus Specification Revs 2.1 and 2.2.

What Does This Mean For Dialogic Cards? Older Dialogic Cards should still work on newer machines with the PCI-X slot specification. If companies are thinking of buying new hardware and transferring over existing peripherals and cards (particularly Dialogic Cards), they will need to be aware of compatibility issues, but generally, if the card fits the slot, it should work.

http://www.dialogic.com/

18


Dialogic Cards that are Universal PCI compliant

Intel has a handful of Universal PCI Dialogic Cards that will run in the PCI-X slot (note that Dialogic Cards are NOT compatible with PCI – E slots). Refer to: www.dialogic.com, Technical Specifications (Form Factor). The following PCIU cards are supported:

Suitable Cards

D/4 PCIU (Note: Also see "Service Packs" below.)

D/41 JCT -LS (PCISIG Bus Specification Rev 2.1)

D/120 JCT -LS (PCISIG Bus Specification Rev 2.2)

Higher Spec Cards

D/240 JCT -T1 (PCISIG Bus Specification Rev 2.2)

D/300 JCT -E1 (PCISIG Bus Specification Rev 2.2)

D/480 JCT -2T1 (PCISIG Bus Specification Rev 2.2)

D/600 JCT -2E1 (PCISIG Bus Specification Rev 2.2)

Note:

The JCT Series cards should work on any PC/Server regardless of voltage output (3.3v or 5v).

Winscribe supports ISDN Telephony for E1 and T1 type Dialogic Cards.

You will need specific drivers for ISDN cards, rather than the standard analog drivers that are used for older cards.

Dialogic Springware & DM3 boards are supported with 64-bit versions of Windows Vista; Windows 7, 8, 8.1;Server 2008 Standard & Enterprise operating systems, including Server 2008 R2; and Server 2012. Dialogic System Release 6.0 PCI Service Update 271 or higher is required. Please refer to the Dialogic System Release – Release Update documentation for further information.

PCI-Express compatibility

All of the cards listed above are PCI-E compatible. Note: when ordering the desired part, you must select a Product ID that contains at least one ‘E’. For example, to obtain a D/4 PCI-E card select (D4PCIUFEQ). European customers would select (D4PCIUFEQEU).

Dialogic PCI-Express (PCI-E) cards require the use of Intel/Dialogic software (FP 6.0 Build SU115) or later. Contact your local Dialogic reseller to obtain the latest Dialogic software.

Note: Winscribe only supports PCI-E versions of the cards listed above (e.g. D/4 PCIU).

Service Packs

When installing the D/4 PCIU you need to install Dialogic 6.0. This is included on the Winscribe Distribution DVD in the Utilities directory.

19


ISDN Telephony

Considerations for upgrading if using Dialogic Cards

Winscribe systems that are using Analog Dialogic cards, and are upgrading from a version prior to Winscribe 3.3.2, will need to stop the Winscribe Dictation and Telephony Services (do not stop SQL) prior to uninstalling the Dialogic Drivers and then reinstall the Dialogic Drivers with the globalcall option selected (specified when running a Custom install). You can either reinstall the original Dialogic Drivers if using Release 6.0 or higher, or install the Dialogic Drivers required for your type of card. Note that you should refer to the Dialogic website or the documentation that came with your Dialogic card to determine which version of the Dialogic Driver to use with your card. The driver must be at least Release 6.0 or higher to work with Winscribe 4.2.

Considerations for installing ISDN Dialogic Cards

There are a number of issues to consider when installing ISDN Dialogic Cards:

ISDN Cards are only supported on Winscribe 3.3 systems or higher.

Winscribe systems that are using ISDN Dialogic cards with Winscribe will need to stop the Winscribe Dictation and Telephony Services (do not stop SQL) prior to uninstalling the dialogic drivers and then will need to reinstall the dialogic drivers with the globalcall option selected (specified when running a custom install) and with the ISDN option and ISDN driver(s) selected. You can either reinstall the original Dialogic Drivers if using Release 6.0 or higher, or install the Dialogic Drivers required for your type of card. Note that you should refer to the Dialogic website or the documentation that came with your Dialogic card to determine which version of the Dialogic Driver to use with your card. The driver must be at least Release 6.0 or higher to work with Winscribe 4.2.

The physical process for installing an ISDN card is no different than installing an older style Analog Card.

The ISDN Card interfaces between a computer and a Telephony System/Switch. The ISDN uses a parameter file (file extension=.PRM) which contains certain settings appropriate to the Telephony System/Switch in question.

As there are many Telephony Systems on the market (Lucent, Fuijtsu etc), the parameter file is not a generic file that can be used in any ISDN install situation. The Winscribe Manager/Technician should contact their Telephony System Provider for information relating to parameter settings.

Always ensure you have the latest Service Packs.

An example of the types of parameter settings used may include:

CRC Enable Switch

Protocol Type

Enable/Disable the D-Channel

Remote Loopback Mode

Inverted D Channel

ISDN Feature List

Should you require more information, contact the Winscribe Helpdesk.

Programming Requirements for PBXs

Refer to Appendix 1 (see page 195) for information regarding programming requirements for PBXs.

20


Section 2: SQL Server Database Software Winscribe supports the following versions of SQL:

Microsoft SQL Express 2005

Microsoft SQL Server 2005

Microsoft SQL Express 2008


Microsoft SQL Server 2008 R2

Microsoft SQL Server 2008 Web Edition


Note: For further information, please see: SQL Server Express or SQL Server in Winscribe Hardware Specifications.

Microsoft SQL Server Express or SQL Server When installing Winscribe you can use Microsoft SQL Server Express or SQL Server. Which option you choose will depend largely on if you already have SQL Server installed but there are other factors to consider.

SQL Server Express Edition is a scaled down, free edition of SQL Server 2005, SQL Server 2008, or SQL Server 2012 (depending on the version chosen).

SQL Server Express supports single-CPU systems and has a maximum storage capacity of 1Gb of RAM.

Function SQL Express SQL Server

File size limitation 4 Gb1 Unlimited (dependent on HDD space)

Enterprise Tools Available as a separate download or included with SQL Server Express with Advanced Services

Yes

Automated Backup No Yes

Users Unlimited Unlimited

Licenses Required No Yes

Supported by Microsoft Yes Yes

1 Each facility in Winscribe is a new database, and in theory would not reach 4 Gb

Note: Winscribe recommends that large multi-facility installations be run on SQL Server.

Server-based processing. With server-based database systems such as SQL Server technology, requests for information are processed on the server and only the resultant data is sent back to the client application. This scenario greatly reduces network traffic; it also allows users to access data and experience outstanding application performance without the requirement for a high-end client workstation.

Server-based data engines perform all processing on the server and return only query results to the client therefore Winscribe can perform well over low-bandwidth links.

21


SQL Configuration Settings When installing SQL Server 2005, SQL Server 2008, SQL Server 2012, or SQL Express, the following configuration settings are required:

Once SQL is installed, open the SQL Configuration Manager and enable the TCP/IP and Named Pipe Network protocols along with the SQL Browser service, then restart the SQL Server service.

When installing SQL, select Use Built In System Account > Local System. (See note below)

The system administrator (sa) account must have a password. If you have upgraded to SQL 2005 or SQL Express from a previous version, and you have an administrative account with a blank password, you will need to select Programs > Winscribe > Tools > Web server (and Winscribe Server) settings tabs and update the sa password there as well.

Note: The NT AUTHORITY\SYSTEM account does NOT have the sysadmin server role in SQL Server 2012. If Dictation Server / Web Components are installed using Windows Authentication for the connection to SQL, the sysadmin server role needs to be enabled on SQL Server 2012

Running SQL Server 2005 or SQL Express on Windows Server 2008 or Windows Vista Operating Systems If Microsoft SQL Server 2005 or Microsoft SQL Server 2005 Express is installed with Advanced Services on a computer that is running either Windows Server 2008 or Windows Vista, the following warning message may be displayed on the System Configuration Check page in the SQL Server 2005 Setup program:

Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation.

Refer to the Microsoft KnowledgeBase article 920201 (http://support.microsoft.com/kb/920201/en-us) for more details.

Changing SQL Credentials If, for security reasons, you change the SQL password you will also need to change the password in the following Winscribe applications to match:

Winscribe Server Settings or Web Server Settings. Click Start | Programs | Winscribe | Tools.

Note: It is only necessary to change the SQL password in either the Winscribe Server or Web Server settings as the change is automatically mirrored in the other.

Web Manager

Telephony Manager

Winscribe Exporter

ATS

Mobile Web Service

SR Submitter

WSR Submitter

Voice Forms Manager

Note: Special characters (e.g. !@#$%^&*<>?”|}{,./) are not allowed within the password of the SQL sa login.

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

22


Transferring an Existing MSDE Winscribe Database to a New SQL Server Winscribe can be configured to use SQL Server as the data store in circumstances where the organization has an existing MSDE Database. To upgrade to SQL, your Database Administrator (DBA) or SQL expert should execute the following steps:

1. Log off all Winscribe users and shutdown all Winscribe related services.

2. On the destination SQL server run the Data Transformation Services (DTS) Import and Export Wizard, which will guide you through the process of importing the source Winscribe database into the destination SQL server. When prompted choose the source as SQL and provide the server name where the current database resides. When prompted choose to import data AND structure. The end result should be a perfect replication of the source Winscribe database, including data and table structures.

3. Using the SQL Server Service Manager, stop the existing MSDE service on the Winscribe server. This will avoid any users from continuing work on the old server.

Point the Winscribe services to the new SQL server by running the Winscribe Server Settings application on the Winscribe server. The database settings are found on the Database tab. Start the Winscribe services and confirm correct operation.

4. Change the following applications to point to the new SQL server.

Winscribe Exporter, if this is being used – Refer to the Exporter installation guide for details.

Winscribe Telephony Manager. Refer to Configuring Telephony Manager (see page 94).

Winscribe Web Manager. Run the Web Manager Configuration application which is located in your Programs | Winscribe | Tools folder. Configuration instructions are given in Installing Winscribe Web Manager (see page 96).

Note: If you are going to use SQL server rather than MSDE, a full Winscribe server install should be performed prior to performing the above steps. In effect this imports an empty Winscribe database.

Running Winscribe with a SQL Named Instance SQL Server and SQL Express have default installation settings that install SQL as a named instance. If you install SQL as a named instance, you will need to specify the instance name when installing the Winscribe applications.

Note: This is only true for SQL Server 2005, not 2008 or 2012.

23


For example, the default install of SQL 2005 Express will create an instance called <servername>\SQLExpress. You will need to enter this instance name when prompted for the database location during Winscribe installations.

If the named instance of SQL is not specified in Web Manager, an error will be generated when you attempt to log in.

Section 3: Installing Winscribe Server The following sections will guide you through the steps required to install the Winscribe Server Software. It is important that these steps are followed exactly, and that you do them in the order presented here. Not doing so may result in the installation failing and thereby require reinstallation of the software.

Note: If installing Winscribe on a Windows 2003 Server, please complete the prerequisites (see page 51) before proceeding.

Important:

1. Check that the computer name that Winscribe is being installed on is 14 characters or less. You will be unable to install Winscribe Server until the computer name meets this requirement.

2. We recommend that you disable any anti-virus software currently running until you have completed the Winscribe installation.

3. If your Winscribe Database Server will use SQL, ensure that SQL configuration has been set up as detailed in SQL Configuration Settings (see page 21).

Note: Local Administrator rights are required to install Winscribe Server.

Step

1. Install the Dialogic Telephony Boards (see page 24) (only if installing Winscribe with the Telephone Interface).

2. Install the Dialogic Drivers (only if installing Winscribe with the Telephone Interface).

3. Configure the Dialogic Boards (see page 28) (only if installing Winscribe with the Telephone Interface).

4. Install Microsoft .NET Runtime (see page 30)

5. Install the Winscribe License Server (see page 30)

6. Install the Winscribe Dictation Server Software (see page 33)

7. Install the Winscribe Web Components (see page 45)

Prerequisites for the Winscribe Server Installation

Prior to installing the Winscribe Server Software, you must have SQL installed either on the Winscribe server or a separate server. During installation you will be prompted to enter the path to the SQL server. The Winscribe Database will be created on the SQL server.

Before installing Winscribe server software ensure that the server has a reliable network connection. Failure to do so will affect the operation of the Winscribe Dictation Windows service.

For more details on the SQL engine, refer to the SQL Engine section (see page 20).

24


Step 1 Install Dialogic Telephony Boards Follow this step only if installing Winscribe with Telephony. Otherwise, go to Step 4 (see page 30).

When installing Winscribe with the telephone interface you must first install the Dialogic board(s) into the server. To install the Dialogic boards follow the Dialogic installation instruction sheet included with the hardware.

Warning: Before handling a Dialogic board, be sure to read the information about electrostatic discharge included on the board's quick install card. Electrostatic discharge WILL damage your hardware!

To Install the Dialogic Card:

1. Shut down the Winscribe Server.

2. Install the Dialogic card(s) according to the Dialogic Installation Instructions card.

3. Restart the Server.

Step 2 Install the Dialogic Drivers Follow this step only if installing Winscribe with Telephony. Otherwise, go to Step 4 (see page 30).

1. Insert the Winscribe Distribution DVD. Browse to the DVD and double click the setup.exe for the Dialogic Drivers.

Click Next to continue.

25


2. Enter your Customer Information:


3. Choose an installation location for executables, libraries, etc.:


26


4. Choose an installation location for the user-modifiable files:


5. Select the features to install:

When installing the Drivers, select "Core Run-Time Package", or select ISDN Protocols and/or SNMP Component Manager, if your type of Dialogic card requires those protocols/options.


27


6. If you receive a Security Alert for required third-party software, click Yes.

7. Select where to install, or accept the default:


8. Click Next to begin the installation:

28


9. The installation setup will commence:

10. If requested by windows security, click to Install:

11. Installation will now take place.

Click Finish to complete.

Step 3 Configure the Dialogic Boards

Follow this step only if installing Winscribe with Telephony. Otherwise, go to Step 4 (see page 30).

During the Dialogic Drivers install, the Dialogic Configuration Manager will run automatically. Click Connect to display the Dialogic Configuration Manager and perform the following necessary tasks:

29


Configure Dialogic Boards

Set the Driver start-up mode to automatic

To Configure the Dialogic Boards:

1. The Dialogic Configuration Manager (DCM) should automatically detect the cards you installed into the server, and configure them for you. Check that the DCM displays the cards you installed. If not, you will have to add the boards manually. Choose the Action and click Add Device and add the appropriate boards. Depending on the board type you may need to enter values for IRQ and memory address (ISA boards only) that you determined when installing the cards. Use the DCM Help menu option for assistance in adding boards.

Note: If you receive "Failed to Detect Board(s) – Error configuring the TDM Bus", reboot the Server and repeat this step.

2. You must also set the appropriate Country parameters for each card. To do this, double click on

each card shown in the DCM, select the Country tab and choose your country from the drop down list.

30


3. You now need to set the Driver start-up mode to Automatic. Click Service, and then click Startup Mode and select Automatic. This will allow the Dialogic drivers to start automatically when the computer is restarted.

Important: Always reply No if prompted to restart your system. Complete the install first and then restart your PC.

4. Exit the DCM (if it was started for you); you will briefly see a Command window as Winscribe registers components before the Setup Complete dialog is displayed.

5. Click Finish to complete this step of the Setup process.

Step 4 Install Microsoft .NET 4

Use the following procedure to install Microsoft .NET 4. Other versions of Microsoft .NET Runtime may be installed on the server alongside, but will not be used by Winscribe.

1. On the installation server, insert the Winscribe Distribution DVD.

2. Run the Microsoft .Net setup program Utilities\Dot Net Runtime\Microsoft .NET v4.0\dotNetFx40_Full_x86_x64.exe.

3. Follow the on-screen instructions to complete the installation.

Note:

On Windows 8 / 8.1 and on Server 2012 you cannot install .NET 4.0 from an installer. It is already included in the OS. You need to enable the feature.

In Server 2012: Add .NET Framework 4.5 in the Application Server role.

In Win 8 & 8.1: Enable ASP.NET 4.5 inside .NET Framework 4.5 Advanced Services. This can be found inside Windows Features. The link to Windows Features is found in Programs and Features.

Step 5 Install the Winscribe License Server The Winscribe License Server is a required component for all Winscribe systems from v3.8 upwards. The License Server uses license files that are obtained via email from Winscribe Technical Support. If Telephony is installed, the Winscribe system will not function without Telephony Licenses in place. Refer to Licensing your Winscribe Software (see page 89) for further details.

Prerequisites

The License Server requires the following environment:

Windows 2003 Server with Service Pack 2(or higher), Windows XP Service Pack 2 (or higher), Windows 2008 Server, Windows Server 2008 R2, Windows Server 2012, or Windows Vista with Service Pack 1 or higher. (Note that Vista Home Basic and Home Premium are not supported).

Microsoft IIS

To Install the Winscribe License Server:

Note: Run this procedure on the server designated as the License Server.

31


1. Run the supplied Winscribe License Server.msi. This launches the Winscribe License Server Setup Wizard:

Click Accept and Install to install.

Note: Click Options you wish to install to a location other than the recommended default.

2. Click Next to continue:

32


3. Enter the username and password to be used by the administrator to manage licenses and configure License Server parameters.


4. You are now ready to complete the License Server configuration. Click Save:

5. The Configuration Wizard will save your settings, displaying the progress as it goes:

33


6. Click Finish to begin the installation.

The installation will take place.

7. Click Finish to complete the Winscribe License Server configuration:

Step 6 Install the Winscribe Dictation Server Software

Note: Prior to installing the Winscribe Server Software, you must have SQL installed either on the Winscribe server or on a separate server. During installation you will be prompted to enter the path to the SQL server. The Winscribe Database is created on the SQL server. For more details, refer to the SQL Engine section (see page 20).

To install the Dictation Server:

1. Run the supplied Winscribe Dictation Server.msi to launch the Dictation Server Setup Wizard.

Click Accept and Install to begin the installation.

34


2. The Customer Information window is displayed:

Note: The company name must be a minimum of 5 characters. It can contain spaces and hyphenation.

Enter your user name and company name and click Next.

3. Enter the database configuration details:

Click Test Connection to test/confirm the database details are correct. A "tick" will appear in place of the "!" to confirm the connection is valid:

Once confirmed, click Next to continue.

35


4. The Setup Type window will be displayed:

Choose the setup type from the list provided and click Next:

Primary Server if this is the main Winscribe Server that will contain the SQL Database and dictation recordings, but no Dialogic cards (telephone authoring and telephone typing will not be available).

Primary Server with Telephony if this is the main Winscribe Server which will contain the SQL Database and the dictation recordings and you are configuring a Winscribe server for use with telephony (including VoIP).

Secondary Server with Telephony if this is the second or subsequent server to be installed at a site for the purpose of expanding the number of Telephony Ports (Dialogic cards must be installed in the Server for this option to be valid).

If you chose:

Primary Server go to Option 1: Installing a Primary Server

Primary Server with Telephony go to Option 2: Installing a Primary Server with Telephony

Secondary Server with Telephony go Option 3: Installing a Secondary Server

Option 1: Installing a Primary Server

1. Enter the URL of the Winscribe License Server:

36



2. Enter the path to the Winscribe Shared directory. You can accept the default directory shown, or click Change to browse to a directory.

Important: This directory is the location that dictation recordings will be stored so you must ensure that there is sufficient space on this drive for your requirements. The Server's computer name must be a valid NETBIOS name and must be 14 characters or less.

If the directory does not exist it will be created.


3. The setup program now has all the information it requires for the installation. Click Install to complete the installation process. Note that this process may take several minutes to complete and that you may see command prompt windows appear briefly during the process.

37


4. Once installed, click Finish to complete.

Option 2: Installing a Primary Server with Telephony

1. Enter the URL of the Winscribe License Server.


38


2. Choose the Telephony Driver.

Note: Software from the selected manufacturer must be installed before continuing. For example, if Dialogic hardware is chosen, the Dialogic drivers must be installed prior to starting the Winscribe Server installation.


3. Select the telephone feature set (type of telephony server).


39


4. If you have Dialogic software installed on the server, you will be prompted to choose the language set (voice prompts) to be installed.

Select a language and click Next to continue.

5. Enter the path to the Winscribe Shared directory. You can accept the default directory shown, or click Change to browse to a directory.

Important: This directory is the location that dictation recordings will be stored, so you must ensure that there is sufficient space on this drive for your requirements.

Note: The Server's computer name must be a valid NETBIOS name and must be 14 characters or less.

If the directory does not exist it will be created.

40


6. The setup program now has all the information it requires for the installation. Click Install to complete the installation process. Note that this process may take several minutes to complete and that you may see command prompt windows appear briefly during the process.

7. Click Finish to complete the installation.

41


Option 3: Installing a Secondary Server

1. Enter the URL of the Winscribe License Server.


2. Choose the Telephony Driver then click Next.

Note: Software from the selected manufacturer must be installed before continuing. For example, if Dialogic hardware is chosen, the Dialogic drivers must be installed first.

42


3. Select the telephone feature set (type of telephony server).


4. Enter the name of the primary Winscribe Server.


5. Enter the name of the Winscribe Primary Server shared directory.

43


This directory must be the shared directory that is set up on the Primary server and must be entered as a UNC path. For example: \\MachineName\WinscribeShare

The directory you enter must be visible to this server. If the directory will not be located on this server ensure both servers are on the LAN and you are able to browse to the alternate directory location from the Winscribe server or the installation will fail.

6. The setup program now has all the information it requires for the installation.

Click Install to complete the installation process. Note that this process may take several minutes to complete and that you may see command prompt windows appear briefly during the process.


Configuring Share Properties

This step is required if you are:

Changing the default Winscribe Shared Directory properties for security reasons

Installing a secondary server

Otherwise you can skip this section and go directly to Installing the Winscribe Web Components (see page 45).

44


Changing the Default Winscribe Shared Directory Properties

During the server installation the Winscribe shared directory is created. If you accepted the default options, this directory will have been created under C:\Winscribe\Server on the primary server.

Winscribe setup automatically shares this directory with access for Everyone (all users), the Windows default. Winscribe setup gives it the network resource name WinscribeShare.

To restrict access to individual users or groups you should change the properties for the Winscribe Shared directory. This is not compulsory, however it is recommended for security purposes.

Configuring Share Properties if Installing a Secondary Server

A secondary server requires network privileges to be able to read and write to the Winscribe Shared directory on the primary server. The easiest way to achieve this is to grant the secondary server permission to the Winscribe Shared directory. The steps below outline this procedure.

Note: To perform this operation you must login with domain administrative rights.

1. Browse to and select the Winscribe Shared directory on the primary server, usually c:\winscribe\server.

Right click the folder icon and choose Sharing & Security from the available menu items. The Properties dialog will be displayed.

2. Choose the Security tab and click Add.

3. The Select Users, Computers, or Groups dialog is displayed.

Actual screens and security process may differ slightly between operating systems.

45


4. In the Location select the domain that the Winscribe Primary/Secondary server is attached to.

If you are changing the default share properties, select and add your individual users or groups.

If you are configuring the Winscribe Secondary server, select and add the secondary server.

You should see your selections in the lower pane. Click OK and the Permissions dialog will be displayed.

5. Click the Full Control tick box to automatically select all permissions. Click OK to save your changes and close the Properties dialog box.

Step 7 Install the Winscribe Web Components To use the Winscribe Client applications, you will need to install the Web Components on a server running Internet Information Server (IIS) 5.0 or above.

Note: Mobile Web Service is included in Web Components.

Security Note: To ensure that the system is protected against all known malicious attacks, it is recommended that you visit the Microsoft security website (http://www.microsoft.com/security/) and install the latest patches. You should also have the latest Microsoft service packs installed.

Prerequisites

The Web Components (Data Provider) requires one of the following MSXML versions in order to communicate with the License Server:

MSXML 3.0

MSXML 4.0

MSXML 5.0

MSXML 6.0

For security reasons we recommend downloading and installing the latest version, currently MSXML 6.0 (http://www.microsoft.com/downloads/details.aspx?familyid=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en)

Considerations for Installing Winscribe Web Components

Winscribe client technology uses the HTTP(S) internet protocol to communicate with the Winscribe Server. The client applications require the Winscribe Web Components to operate on a designated web server.

The considerations for these client applications are:

the ability to communicate with the server using the HTTP or HTTPS protocol over TCP/IP.

they work in a LAN/WAN environment and over the Internet.

they require IIS on the Server and Internet Explorer 6.0 or higher on the Client PC to operate.

they can use password authentication, encryption, and Certificates to secure access to dictation.

they allow users to work off-line (i.e. without a connection to the Winscribe Server)

the Internet Clients require less bandwidth to operate, and provide a higher level of security.

When installing the Internet Clients, the Web Components need to be installed on a computer running IIS (Microsoft Internet Information Server) version 5.0 or above.


http://www.microsoft.com/downloads/details.aspx?familyid=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en

http://www.microsoft.com/downloads/details.aspx?familyid=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en

46


IIS can be installed on the Winscribe Primary Server, but if the Server has a connection to the Internet, it is preferable to have IIS on a separate machine, or at least have the Winscribe Web Components working directory on a different partition to the operating system.

If you already have an IIS Server, then the Winscribe Web Components can reside on that machine.

Installing the Web Components

Note:

The instructions below detail the installation of the Winscribe Data Provider. The installer used (Winscribe Web Components) additionally enables installation of the Web Manager and the Mobile Web Service. If you would like to install all three web components at the same time, follow the instructions in Appendix 3. Installing the Web Components (Full).

Prerequisite Requirement: The Data Provider requires .NET 4 to be installed.

To install the Winscribe Web Components:

1. From the Winscribe Dictation 4.2 Installer DVD web page, select:

Server / Winscribe Web Components

Or run the supplied WinscribeWebComponents.msi:

Note: By default, web components are installed under:

C:\Program Files(x86)\Winscribe\Web Components\

47


2. Click Accept and Install to continue:

3. Select to install Data Provider, and then click Next:

4. Enter the Database connection credentials:

Enter your database Username and Password, and select the Connection type.

Click Next.

48


5. Click Install to install the Data Provider:

6. The installation is now complete. Click Finish to complete and exit the setup wizard:

IIS6 comes with a limit on the size of files that are allowed to be transferred via ASP scripts. This limit blocks large Winscribe jobs from being downloaded. You can increase this limit by following the instructions in Increasing IIS File-size Limit.

Note: You must ensure that the Winscribe Web Components will have full access to the Winscribe Shared Directory. The Web Components 'impersonate' a user when they try to gain access to the Shared Directory, so the user account that the components impersonate must have full access to the shared directory. The impersonated user is determined by the Identity of the Application Pool associated with Winscribe site in IIS (DictationAppPool by default). If you use other security methods, you will need to ensure all appropriate users have access to the shared directory.

Winscribe Server URL

During the installation of the Web Components, Winscribe Setup creates a virtual directory (alias) named Winscribe. To install the Winscribe Internet client applications, you will need to know the URL to this virtual directory.

When working across the Internet, the URL will consist of the DNS entry for the Web Server (i.e. www.winscribe.com) followed by the path to the virtual directory. If you created the virtual directory in the root of the web site the path will be the Web Server's URL followed by the alias for the virtual directory (e.g. www.winscribe.com/winscribe).

49


When using the Internet Clients in a LAN/WAN environment, the URL can simply be the machine name of the Web Server, followed by the alias of the Winscribe virtual directory (e.g. http://servername/winscribe).

Web Security Considerations

The installation procedure outlined above installs the Web Components with anonymous access to the Winscribe Services. No encryption or passwords are used to control access to the service (however, each user is authenticated as a valid Winscribe User). Configuring additional security is outside the scope of this manual. Please consult your IIS documentation for details on how this is achieved. Basic authentication can be configured by selecting the Winscribe virtual directory, and all sub-directories, and editing the Directory Security tab of the directories properties. Using encryption is more complex and requires setting up a secure site, with an appropriate server certificate, and client certificates if required.

Web Components and Primary Server on Different Boxes Installation of Winscribe Web Components is complete. You may begin installing Winscribe Internet Clients. Refer to the section on Installing Client Applications (see page 139) for details on hardware requirements and installation steps.

Using Distributed Audio

What is Distributed Audio and how do you use it?

Distributed Audio is used to lower the bandwidth demand when Winscribe is rolled out across a large WAN. Instead of all audio being retrieved from a central store (across the entire WAN), localized storage is employed to store smaller pockets of audio. There's a greater chance the audio is only required locally (e.g. transcribed locally), therefore reducing the entire network throughput of traffic.

50


This concept is shown in the following diagram.

Distributed Audio allows Web Components to be installed in remote locations and to store the audio (Vox files) on a machine in the remote location while still using the central database. Web Components from any location can retrieve these files only if they have permission to the share in the remote location. The same permissions are also required for the Standard Telephony Server and for the Advanced Telephony Server.

Distributed Audio is also called DVS (Distributed Voice System)

Enabling Distributed Audio

Use the following procedure to enable distributed audio:

1. Domain Account

Choose a domain account to be used for accessing all the distributed locations.

2. Web Components

Note: Steps 2a to 2d must be completed on the PC identified as the Distributed Audio PC.

a. Load the Web Components.

b. Create a local folder called 'WinscribeShare', and share it to 'Everyone'.

c. Create a new string registry key in HKEY_LOCAL_MACHINE/SOFTWARE/WINSCRIBE/WEB called LocalSharedDirectory

d. Set the value of the new key to the path where files should be stored (that is, the folder created in Step 2a, above). For example, \\PCName\ShareName (You MUST use a UNC path).

Note: Steps 2e to 2g must be completed on all servers where the Web Components are installed.

51


e. Change the identity of the Application Pool containing “Winscribe” (DictationAppPool by default) to the domain account chosen in Step 1

f. On the Web Components folder “Uploads” (Default path = C:\Program Files (x86)\Winscribe\Web Components\Data Provider\App_Data\Uploads), add the domain account chosen in Step 1 and grant it Modify permission

g. Reset IIS.

1. Dictation Service (Standard or Advanced)

Set the log on of the Winscribe Dictation service to the domain account chosen in Step 1.

Notes:

Files uploaded to the server by a script will always go to the main server (and will be downloaded from there also).

Exporter does not support distributed audio.

Speech Recognition Submitters (Dragon and Philips) do not support Distributed Audio.

Using Self-signed SSL Certificates with Winscribe To use a Self-Signed SSL certificate on your Winscribe Web Site, it is necessary to add a DWORD value to the General or Importer Key. If you do not do this, users of the Author, Client, and Importer applications will receive warnings each time they connect to the Web Server.

For Authors and Typists, add the following DWORD value to the General Key:

1. Start Regedit.

2. Expand to HKEY_CURRENT_USER ... Software ... Winscribe ... General.

3. Right click on "General" and choose "New ... DWORD value".

4. Overtype "New Value #1" with "IgnoreSSLCertificateWarnings" and then double-click on it.

5. Change the "value Data" from "0" to "1".

For Importer, add the following DWORD value to the Importer Key:

1. Start Regedit

2. Expand to HKEY_LOCAL_MACHINE ... Software ... Winscribe ... Importer.

3. Right click on "Importer" and choose "New ... DWORD value".

4. Overtype "New Value #1" with "IgnoreSSLCertificateWarnings" and then double-click on it.

5. Change the "value Data" from "0" to "1".

Section 4: Installing Winscribe on Windows 2003 Server

Prerequisites for Windows 2003 Server

If you are installing Winscribe with Telephony Support on a Windows 2003 server you must ensure your Dialogic Drivers are upgraded to version 6.0. Earlier versions of the Dialogic Drivers do not provide support for Windows 2003 and may not install successfully, particularly on 64-bit systems. For your convenience the required Dialogic Drivers are included on the Winscribe Distribution DVD.

Prior to installing the Winscribe Server Software, you must have a database engine installed either on the Winscribe server or a separate server. During installation you will be prompted to enter the path to the database engine. The Winscribe Database will be created on the database engine server. For further details on database engines, refer to the SQL Engine section (see page 20).

52


Note:

Intel Dialogic drivers prior to Release 6 Build 95, as well as Dialogic D4/PCI cards, are NOT supported by Windows 2003 Server. Dialogic D4/PCI-U cards are required.

Installation Summary for Windows 2003 Server The following table gives a summary of the steps you need to take to install Winscribe onto Windows 2003 Server.

Step

1 Install the Dialogic Telephony Boards (see page 24) (only if installing Winscribe with the Telephone Interface).

2 Install the Dialogic Drivers (only if installing Winscribe with the Telephone Interface).

3 Configure the Dialogic Boards (see page 28) (only if installing Winscribe with the Telephone Interface).

4 Install Microsoft .NET Runtime (see page 30)

5 Install the Winscribe License Server (see page 30)

6 Install the Winscribe Dictation Server Software (see page 33)

7 Install the Winscribe Web Components (see page 45)

8 Configure the IIS Server for the Web Components (see page 52).

9 Prepare to install the client applications (see page 55).

10 Install the client applications (see page 139)

Steps 1-7 Complete steps 1 – 7 of the Installation procedure detailed in Installing Winscribe Server (see page 23).

Step 8 Configure IIS Server for Web Components on Windows 2003 Server Important:

Even if you have IIS already installed, you must still perform the following tasks.

Do not 'uncheck' any boxes that are pre-checked. Doing this will result in those components being uninstalled.

You will need your Windows 2003 Installation CD to perform these actions.

Installing/Modifying IIS

Use the following procedure to install or modify IIS.

1. Click Start | Control Panel | Add/Remove Programs.

2. Click Add/Remove Windows Components.

53


3. Select Application Servers and click on Details.

The Application Server window is displayed.

4. Select ASP.NET

Ensure Enable network COM+ access is checked (it should be ticked automatically when you select ASP.NET)

Ensure Internet Information Service (IIS) is checked (it should be ticked automatically when you select ASP.NET)

5. Select Internet Information Services (IIS) and click Details.

The Internet Information Services (IIS) window opens

Select Common Files

Select Internet Information Services Manager

54


Select World Wide Web Service

6. With World Wide Web Service selected, click Details.

The World Wide Web Service window opens.

Select Active Server Pages

Select Server Side Includes

Select World Wide Web Service

7. Click OK until you return to the Windows Components Wizard dialog, then click Next.

You may be prompted to load the Windows 2003 Server Installation CD. If so, load it so the necessary files can be copied. This will take several minutes.

8. Click Finish to complete the IIS install.

9. Browse to http://localhost/ to verify the IIS installation. You should see a 'Under Construction' page.

10. To make sure the ASPNET account was created, type: lusrmgr.msc in the Start > Run dialog box. This opens the Local Users and Group manager window.

Check under the Users folder for the ASPNET entry.

11. Start Internet Information Services (IIS) Manager by selecting Start | Control Panel | Administrative

Tools then clicking on Internet Information Services (IIS)

55


Click on Web Server Extensions and ensure Active Server Pages, ASP.NET V2, and Server Side Includes are all set to allowed.

Step 9 Prepare to Install the Client applications on Windows 2003 Server If client applications are required on the server, install the Winscribe Client Applications (see page 139).

When you browse to the Setup page (http://webservername/Winscribe/Setup) you may be presented with the warning shown.

Click Add and the Trusted Sites window will be displayed, as shown.

56


Click Add again. This will add your Web Server to your 'Trusted sites' and you can then load your Author or Client application from the Setup page.

To run Winscribe Author, Winscribe Client, Internet Author, and/or Importer on the Server:

You must have a Sound Card installed.

Enable Sounds by selecting Sounds and Audio Devices from the Control Panel, then selecting Enable Windows Audio.

Start the Windows Audio Service.

Step 10 Install the Client Applications

Install the client applications as detailed in Installing Client Applications (see page 139).

Troubleshooting Winscribe Installation on Windows 2003 Server

HTTP 403 / HTTP 404

If ASP .NET is not registered and you try to browse to the web manager site http://localhost/winscribenet you may receive HTTP 404 (not found) or HTTP 403 (forbidden) error messages. Refer to Knowledge Base 1205.

57


Raw .aspx code

If ASP .NET is not registered and you try to browse to the web manager site http://localhost/winscribenet you may see raw .aspx code in the browser. Refer to Knowledge Base 1205.

Download .aspx file

If ASP .NET is not registered and you try to browse to the web manager site http://localhost/winscribenet you may be prompted to download an .aspx file. Refer to Knowledge Base 1205.

Section 5: Installing Winscribe on a Microsoft Windows 2008 Server This section describes the installation of Winscribe on a Microsoft Windows 2008 Server.

Installation Summary for Windows 2008 Server The following is a summary of the steps needed to install Winscribe onto a Windows 2008 Server.

Step 1 Turn on Network Discovery (see page 57)

Step 2 Install Required IIS Features

Step 3 Install Winscribe (see page 61)

Step 4 Install Desktop Experience (see page 62) Required if installing the Mobile Web Service or Winscribe Exporter

Step 1: Turn on Network Discovery 1. Click Start | Control Panel, then double-click on Network and Sharing Center. This opens the

Network and Sharing Center window.

2. Set the Network Discovery option to On.

3. Set the Public Folder Sharing option to On, by choosing Turn on sharing so anyone with network access can open, change, and create files.

58


Step 2: Install Required IIS Features

Note: IIS7 has directory browsing set to enabled by default. If running IIS7, you should ensure that directory browsing for the Winscribe website is disabled.

1. Click Start | Control Panel then double-click on Programs & Features. Select the Turn Windows Features On or Off option from the left hand Tasks menu. This opens the Server Manager window.

2. In the Server Manager window, scroll down to the Roles Summary section of the right pane.

3. Click on the Web Server (IIS) link.

This opens the Web Server (IIS) window.

4. In the Web Server (IIS) Window, scroll down to the Role Services section.

5. Click on the Add Role Services link on the right side of the right hand pane.

This opens the Select Role Services window.

6. Expand the Common HTTP Features tree.

Tick the following checkboxes:

The Static Content checkbox

The Default Document checkbox

The Directory Browsing checkbox

59


The HTTP Errors checkbox

Note: If using Windows server 2008 R2 64-bit, ensure "Web Dav Publishing" (not shown) is also checked (see Section 7 for further information).

7. Expand the Application Development tree.

Within this tree, tick the following checkboxes:

The ASP.NET checkbox

The .NET Extensibility checkbox

The ISAPI Extensions checkbox

The ISAPI Filters checkbox

8. Expand the Health and Diagnosis tree.

60


Within this tree tick the HTTP Logging checkbox.

9. Expand the Security tree. Within this tree, tick the following checkboxes:

The Windows Authentication checkbox

The Request Filtering checkbox

10. Expand the Performance tree.

61


Within this tree tick the Static Content Compression checkbox.

11. Expand the Management Tools tree.

Within this tree tick the following checkbox:

The IIS Management Console checkbox.

Step 3: Install Winscribe

Install the following:

1. If you wish to install Dialogic Cards, refer to the Dialogic sections of the Installing Winscribe Server (see page 23)


3. Install the Winscribe Dictation Server (see page 33)


5. Install Winscribe Client software (see page 139) as required (Winscribe Author, Winscribe Client, Internet Author)

Note: When installing the License server, verify that the 'IUSR' or the group IIS_IUSRS has 'Modify' permissions on the virtual directory (usually C:\Inetpub\wwwroot\LicenseServer).

62


Step 4: Install Desktop Experience

Note: This step is only required if you are installing the Mobile Web Service or using Winscribe Exporter.

1. From the Windows Start menu, open the Server Manager.

2. In the right-hand pane, scroll down to the Features Summary section.

3. Click on the Add Features hyperlink. The Add Features Wizard opens.

4. Select the Desktop Experience checkbox.

5. Click Next to continue.

Section 6: Installing Winscribe on a Microsoft Windows 2012 Server This section describes the installation of Winscribe on a Microsoft Windows 2012 Server.

Installation Summary for Windows 2012 Server

The following is a summary of the steps needed to install Winscribe onto a Windows 2012 Server.

Step 1 Configure Advanced Sharing Options

Step 2 Install Required IIS Features

Step 3 Install Winscribe

Step 4 Install Desktop Experience Required if installing the Mobile Web Service or Winscribe Exporter

Step 1: Configure Advanced Sharing Options 1. From the Control Panel, open the Network and Sharing Center.

63


2. Open Advanced sharing settings:

a. Set the Network Discovery option to On

b. Set the File and Printer Sharing option to On

3. Click Save changes.

Step 2: Install Required IIS Features

Note: IIS7 has directory browsing set to enabled by default. If running IIS7, you should ensure that directory browsing for the Winscribe website is disabled.

1. From the Control Panel, open Programs and Features.

2. In the top, left-hand corner of the Programs and Features window, click Turn Windows features on or off to open the Server Manager.

3. In the top, right-hand menu of the Server Manager, click Manage, and then Add Roles and Features:

64


4. This opens the Add Roles and Features Wizard. Click Server Roles in the left menu:

5. In the options tree, expand Web Server (IIS) | Web Server

6. Expand Common HTTP Features. Tick the following checkboxes:

Static Content

Default Document

Directory Browsing

HTTP Errors

7. Expand Application Development. Tick the following checkboxes:

.NET Extensibility 4.5

ASP.NET 4.5

ISAPI Extensions

ISAPI Filters

8. Expand Health and Diagnosis. Tick the following checkbox:

HTTP Logging

9. Expand Security. Tick the following checkboxes:

65


Request Filtering

Windows Authentication

10. Expand Performance. Tick the following checkbox:

Static Content Compression

11. Expand Management Tools. Tick the following checkbox:

IIS Management Console

Within Management Tools, expand IIS 6 Management Compatibility, and tick the following checkboxes:

IIS 6 Metabase Compatibility

IIS 6 Scripting Tools

IIS 6 WMI Compatibility

12. Click Next, then click to Install.

Step 3: Install Winscribe Install the following:

1. If you wish to install Dialogic Cards, refer to the Dialogic sections of the Installing Winscribe Server (see page 23)


3. Install the Winscribe Dictation Server (see page 33)


5. Install Winscribe Client software (see page 139) as required (Winscribe Author, Winscribe Client, Internet Author)

Note: When installing the License server, verify that the 'IUSR' or the group IIS_IUSRS has 'Modify' permissions on the virtual directory (usually C:\Inetpub\wwwroot\LicenseServer).

Step 4: Install Desktop Experience

Note: This step is only required if you are installing the Mobile Web Service or using Winscribe Exporter.

1. From the Control Panel, open Programs and Features.

66


2. In the top, left-hand corner of the Programs and Features window, click Turn Windows features on or off to open the Server Manager.

3. In the top, right-hand menu of the Server Manager, click Manage, and then Add Roles and Features, to open the Web Server (IIS).

4. This opens the Add Roles and Features Wizard. Click Features in the left menu:

5. In the menu tree, expand User Interfaces and Infrastructure:

6. Tick Desktop Experience

7. Click Next, then click to Install.

Section 7: Installing Winscribe on 64-bit Operating Systems

Winscribe can be installed on 64-bit operating systems. In this case, Windows executes the application in 32-bit emulation mode.

For more information refer to: http://msdn.microsoft.com/en-us/library/aa384249(v=vs.85).aspx http://msdn.microsoft.com/en-us/library/aa384249(v=vs.85).aspx

The following 64-bit operating systems are supported by Winscribe:

Windows Server 2003

Windows Server 2008


Windows Vista *

Windows 7, 8, 8.1 *

http://msdn.microsoft.com/en-us/library/aa384249(v=vs.85).aspx

67


* As per the Microsoft EULA, Windows Vista and Windows 7, 8, 8.1 are not to be installed as production servers. As such, Winscribe server software should not be installed on these operating systems.

The following Winscribe server applications are supported on 64-bit operating systems:

Winscribe Server

Advanced Telephony Service (ATS)

Web Components

Telephony Manager

Web Manager

Exporter

Importer

License Server

SR Controller

SR Submitter

SR Training Application

Active Directory Sync Tool

Voice Forms Manager

User Importer

Winscribe Mobile Services

Winscribe Speech Recognition Service

Winscribe Speech Recognition Submitter

The following Winscribe client applications are supported on 64-bit:

Winscribe Author

Winscribe Internet Author

Winscribe Client

Nuance Dragon Naturally Speaking (DNS)

DNS is supported on 64-bit operating systems in 32-bit emulation mode, as are the adapter and analyzer.

Client-side speech recognition is supported on 64-bit using Dragon 11.0, 11.5, 12, and 12.5.

The following topics outline the steps required to enable Winscribe on 64-bit operating systems.

Enabling 32bit Microsoft.NET on Server 2003 64bit

On 64-bit systems you must enable Microsoft .NET 2.0 to run as a 32-bit application.

Note: This step is not necessary if running Server 2008.

Use the following procedure to run the 32-bit version of Microsoft .NET 2.0:

1. From the Windows Start menu, click on Run. Type cmd into the Run window, and click OK.

2. Type the following command to enable the 32-bit mode:

Cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

3. Type the following command to install the version of .NET 2.0 (32-bit) and to install the script maps at the IIS root and under:

%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i

4. Ensure that the status of Microsoft .NET version 2.0.50727 (32-bit) is set to Allowed in the Web Service Extension List in the Internet Information Services Manager.

Registry Locations Please note that registry locations change under 64-bit operating systems.

68


The 32-bit path is SOFTWARE\Winscribe

The 64-bit path is SOFTWARE\Wow6432Node\Winscribe

Section 8: Installing Winscribe ATS

Introduction

Winscribe Advanced Telephony Server (ATS) is a feature pack available for use with Winscribe version 3.5.3 and above. It provides an alternative to the standard telephony functionality, offering additional features and functions.

In its basic configuration, ATS operates in the same way as Winscribe's standard telephony functionality. Users familiar with this interface will require no additional training. By taking advantage of ATS's extra features, the interface can be enhanced and changed to better meet user requirements.

Feature Summary

In addition to the standard Winscribe Telephony features, ATS includes the following features:

Feature Description

Scripting ATS's telephone interface can be controlled by custom scripts. Scripts gain complete control over phone calls allowing detailed customization to user requirements. Customized scripts can be used to validate entered data or update external data sources.

Line Configuration Each line can be configured separately to specify Language, Facility, Keypad, Script, and line usage.

DNIS DNIS numbers can be defined to over-ride line configuration, allowing complete call customization based on the number dialed.

Keypads ATS's keypad definitions allow multi-level commands. Keypads can be associated with lines, DNIS numbers and users for maximum flexibility.

Text to Speech Scripts can take advantage of SAPI compatible Text to Speech if installed. If a prompt has not been recorded, scripts can pass text to ATS and it will be converted to audio. This feature is great for speaking information like patient/client name and address information for data validation.

Outbound Dialing Scripts that perform outbound calls are supported. Outbound scripts can be scheduled to run at defined frequencies or run on demand. Telephone re-record from other systems including demographic collection is possible using this feature.

Advanced Review In addition to the standard Winscribe review modes, ATS supports Advanced Review. It allows reviewers to select jobs by entering key field, job type, job number or author id as well as combinations of these. Still not enough flexibility? Using scripting, job selection can be expanded to allow access based on exactly the information you want.

Key Logging Key logging allows logging of user responses to telephony prompts. Selectable per user, logging allows confirmation of user actions.

ATS Installation Summary

The following table provides a summary of the steps you need to take to install ATS at an existing Winscribe installation.

Step

1. Install ATS Prerequisites (see page 69)

69


2. Install ATS (see page 69) by running the ATS Setup Wizard from the Winscribe Distribution DVD.

3. Configure ATS (see page 71)

4. Configure Advanced Review (see page 77) (optional)

5. Beyond Advanced Review (see page 77) (optional) – Develop scripts to customize functionality. Refer to the ATS Technical Reference Manual for further details.

Uninstalling Winscribe ATS

The procedure for uninstalling Winscribe ATS is detailed in Chapter 6: Uninstalling Winscribe ATS.

Step 1 Install ATS Prerequisites

Required Components

ATS requires the following prerequisites to be installed before running the ATS Setup Wizard:

Winscribe Server with Telephony Support. For installation instructions refer to Installing Winscribe Server (see page 23).

Microsoft .NET 4. To install Microsoft .NET 4, insert the Winscribe Distribution DVD and browse to the following directory: Utilities\Dot Net Runtime\Microsoft .NET v4.0. Double click on the dotNetFx40_Full_x86_x64.exe file to run it, and follow the on-screen instructions to complete the installation.

Notes:

You must have .NET 4 installed for Winscribe ATS to run. Other versions of Microsoft .NET Runtime may also be installed alongside, but will not be used by Winscribe.

To successfully complete these installations, you must have local administrative privileges.

Optional Components

The following optional components may also be installed:

For Text to speech functionality, a SAPI compliant text to speech engine must be installed (you can download Microsoft's text to speech from their web site).

For DNIS functionality, a digital dialogic card is required.

Step 2 Install ATS In order to install ATS, you must be logged in with local Administrative rights. Run the ATS Setup Wizard, as follows:

1. Ensure that Microsoft .NET 4 has been installed, as detailed above.

2. Confirm that the 'Dialogic', 'Winscribe Dialogic', and 'Winscribe Dictation' services are all running and operating normally.

3. On the target computer, insert the Winscribe Distribution DVD and browse to Software\Server\Services\ATS. This runs the ATS Setup Wizard.

4. Read the notes on the Welcome screen then click Next to continue.

5. Change the default Installation folder if required.

6. Click Next to begin copying files.

7. Click Close to finish the installation process.

70


Next Steps

To confirm successful installation, open the Event Viewer and click on Application Events. You should see three information events from Winscribe ATS. Any problems detected during operation will be logged to the application event log.

ATS is now setup and running. You can make a call to the system to confirm proper operation. If ATS does not answer your call, check the event log for details of the problem encountered.

Troubleshooting Winscribe ATS

If SQL becomes unavailable while the system is in use, the user will receive a message advising them that the Winscribe database is offline. Please note that if the user is from a facility other than the default Winscribe facility, they will hear the message from the default facility rather than their own facility. This means that if the facilities have different languages, the user will hear the message in a language that is different to their own.

Configuration

There are several options that enable you to configure the behavior of ATS. These options are covered in the following sections.

ATS Configuration (see page 71)

A configuration program installed with ATS which allows you to configure ATS specific settings. This option is documented in this section.

Advanced Review (see page 77)

To utilize ATS's Advanced Review feature, changes must be made to the default script. These changes are documented in this section.

Scheduling Outbound Scripts (see page 78)

Outbound scripts can be scheduled using Windows Task Scheduler. This section documents the process of scheduling an outbound script.

Tone Detection (see page 79)

For analog lines, tones need to be configured to detect disconnect (for inbound and outbound calls) and call progress (for outbound calls). This section documents the process of setting up these tones.

Key Logging (see page 80) ATS's configuration file can be changed to specify which users should have DTMF key logging enabled. This section documents the process of changing ATS's configuration file.

Note: In addition to the above configuration options, the standard Winscribe Server Settings has several options which affect the operation of the telephony interface. These settings still apply to ATS.

71


Step 3 Configure ATS During installation, the ATS Configuration program is installed. To start it, select Start | All Programs | Winscribe | Tools | ATS Configuration.

ATS Configuration enables you to change the following information:

Global Settings Database connection settings

Line Defaults Default values associated with each telephony line

Line Overrides Values that override the Line Defaults for specific lines

DNIS Values that override the Line Defaults and Line Overrides when a call is received to a specified DNIS number

Keypads The keypad definitions to be used by ATS

Keypad Assignment Assignment of defined keypads to users.

72


Global Settings

The SQL Server options enable you to specify the SQL Server that hosts the Winscribe database along with the login details to use.

These values will have been set during installation and should not be modified unless they have changed.

SQL Server name This is the name of the SQL Server that hosts the Winscribe database. If this is the same machine as ATS is installed on, this field may contain '(Local)' instead of the machine name.

User name SQL Server user name that ATS should use when logging on to the database.

Password SQL Server password that ATS should use when logging on to the database.

Windows NT security If your SQL Server uses Windows authentication, then this box should be checked. User name and password do not apply in this situation, since the Windows login the ATS Service uses will be used to login to the database. If you select this tick box, you must also set the NT User for the ATS Service.

To set the NT User for the ATS Service, open the Services applet (in Administrative Tools) and double click on the "Winscribe Advanced Telephony" service. Select the "Log On" tab. Click on the "This account" option and enter the NT User details.

73


Line Defaults

Line defaults are values associated with all telephone lines handled by ATS. These values can be overridden by Line Overrides or DNIS settings.

Note: Once a user has logged on, the values for Language, Keypad and Facility are determined by the user settings.

Language Language sets the default language for all lines. Choose a value from the list. Only installed languages will be displayed in the drop-down.

Script

Script to run for inbound calls. Scripts you add will appear in this drop-down as well as the 'Default' script copied during installation (which mimics the original Winscribe telephony interface).

Keypad

Keypad definition to use if a user has no keypad specified. During installation, the standard Winscribe keypad is created (named Default).

Facility

The facility. If you specify 'All Facilities', users from any facility can logon. If you specify a particular facility, only users from that facility can logon.

Line type

The type associated with each line. Valid types are:

Inbound Only used for inbound calls

Outbound Only used for outbound calls. Inbound are ignored.

Inbound/Outbound Used for both inbound and outbound calls

Unused Not used by ATS (no inbound or outbound calls)

74


Line Overrides

Line Overrides enable you to override the Line Defaults for specific lines.

To specify line overrides, create a new row and enter the start and end line number (which can be the same for a single line). Now select the override values.

DNIS

DNIS entries enable you to specify the settings associated with a call to a specific telephone number (DNIS Id).

Create a new row and specify the DNIS Id exactly as the telecoms carrier will transmit it. When a call is received, if the DNIS number matches one of these entries, the associated language, script, keypad and facility will apply to that call (Line Defaults and Line Overrides will be ignored).

Note: Line type does not apply to DNIS settings.

75


Keypads

Keypads define the key sequences and associated functions that are valid when a user is working with a Winscribe dictation job.

You can define an unlimited number of keypads. Each keypad should have a definition for each of the three keypad types, which are:

Edit Used by Authors creating or editing new dictation (new or open jobs)

Review Used by Authors reviewing existing jobs

Transcription Used by transcriptionists transcribing jobs.

Each type has a different set of key functions available (e.g. a transcription keypad does not support the record key functions).

For each key definition you need to specify:

Keypad

The keypad name this definition belongs to.

Note: During installation a keypad named 'Default' was created which implements the standard Winscribe keypad.

Key Sequence

The sequence of DTMF keys the user presses to activate the key function.

Note: Specialist dictation stations will often generate multiple DTMF digits when a function button is pressed. To support these stations, enter all of the digits generated by these function buttons.

Key Function The function to be performed when the Key Sequence is pressed by the user. For a complete list of available key functions, refer to Appendix 2.

Type The type (Edit, Review or Transcription) that this particular entry belongs to.

Key Conflicts

Take care to avoid creating key conflicts. Two identical key sequences with the same keypad name and type will not both work (the first one entered will override the second).

Defining key sequences (for the same key pad and type) with the same starting digits is valid. But be aware that a short delay will result if two key sequences such as "1" and "11" are defined while ATS waits to see if the user will press the second 1.

76


Keypad and Type Filters

To reduce the number of records displayed on the Keypad tab, you can filter the records by keypad and/or keypad type.

Choose the keypad and/or type from the drop-down list to apply a filter, or select 'All keypads' or 'All types' to remove the filter.

Keypad Assignment

The Keypad Assignment tab is used to provide a means of associating ATS keypads with Authors and Typists.

To assign a keypad to a user, select the facility from the drop-down, then the user table and click Retrieve Records. Find the appropriate user and select the keypad.

Note: A new keypad created on the keypad tab will not appear in the drop-down until you save and exit ATS Configuration. Restart ATS Configuration to associate the new keypad.

General Usage

Adding New Grid Rows:

To add a new row to the Line Overrides, DNIS or Keypad grids, scroll to the last row in the grid (the one with the '*' on the left). Enter the new details in the new row.

Note: When adding new rows to the Keypad grid, if the new record does not match the applied filter, the record will 'disappear' right after entry. To see your new record, remove or change the filter.

Deleting Grid Rows:

To delete a grid row, click on the grey area to the left of the row and press the 'Delete' key. The row will be deleted.

Sorting Grid Rows:

You can sort records displayed in the Line Overrides, DNIS, Keypad or Keypad Assignment grids. Click on the grey area above the column you wish to sort on. The records will be sorted in ascending order. Click again to sort in descending order.

77


Saving and Exiting:

Save your changes by pressing the 'Save' button. ATS Configuration will confirm successful saving of the configuration information.

Note: The SQL Server options will not take effect until the next time you restart the ATS Service. All other changes will take effect within approximately 15 seconds.

To exit ATS Configuration, click the Exit button or the close window button on the title bar (the X). If you have made changes that have not yet been saved, you will be prompted to save or discard them.

Step 4 Configure Advanced Review Winscribe's standard telephone review feature enables an author to select jobs by entering a job number or review key. ATS supports this same functionality, and this is the mode used in the default script. By modifying the default script, you can utilize the advanced review functionality which allows authors to select jobs by:

Key field

Job type

Job type and key field

Job number

Author Id

To switch between standard review mode and advanced review mode, follow these steps:

1. Using Notepad, open the file called Default.cs in the ATS installation directory:

32bit: C:\Program Files\Winscribe\Dictation Server\Winscribe Advanced Telephony

64bit: C:\Program Files (x86)\Winscribe\Dictation Server\Winscribe Advanced Telephony

2. Find the following line in the script:

if (Author.JobList.PromptForReviewCriteria())

and change it to:

if (Author.JobList.PromptForReviewCriteriaAdvanced())

3. Save your changes

Note: Scripts are not reloaded automatically. For your change to take effect, either restart the Winscribe Advanced Telephony service, or, using ATS Configuration, make any change to the configuration data and save your changes. ATS will reload scripts when changes have been made to its configuration.

Special Note: In this release of ATS, two prompts required to support Advanced Review are required to be manually copied copied to the prompts directory. The prompts (prompt 8000 and 8001) can be found in the 'New Prompts' subdirectory of the ATS install directory. Select the two prompts from the appropriate subdirectory (USA Male or USA Female), and copy them to the following directory: C:\Winscribe\Server\Prprompt\Normal\English

Step 5 Beyond Advanced Review

If the advanced review feature still does not meet your customer requirements, you can develop a custom script which prompts the caller for exactly the information required and retrieve the matching jobs for review.

78


Scheduling Outbound Scripts

Prior to scheduling an outbound script, you must develop the script and copy it to the installation directory. Consult the ATS technical reference manual for assistance with developing outbound scripts. Outbound scripts are scheduled using Windows Task Scheduler.

To schedule an outbound script:

1. Click Start | Programs | Accessories | System Tools | Scheduled Tasks.

A list of scheduled tasks is displayed.

2. Double click "Add scheduled task".

The Scheduled Task Wizard appears.

Click Next to move to the Program Selection Window

3. Click Browse to select the program.

Browse to the ATS installation directory:

32bit: C:\Program Files\Winscribe\Dictation Server\Winscribe Advanced Telephony

64bit: C:\Program Files (x86)\Winscribe\Dictation Server\Winscribe Advanced Telephony

Select the program wsTaskStart.exe.

Click Open

4. Continue working through the Wizard to define the frequency and the time the outbound script should be run.

5. After clicking Finish, your new task will appear in the list of scheduled tasks.

Double click your new task to show its properties.

79


6. Click on the 'run' text box and move to the end of the text it contains (right after the last quote mark).

Type in the name of the script you wish to have run, making sure you leave a space between the quote mark and the script name.

7. Click OK to complete the task schedule

Note: Using the Schedules Task properties dialog, you can also make adjustments to the schedule you entered or enable and disable the scheduled task.

Tip: Right-click on your scheduled task and choose Run to run your Outbound Script immediately.

Tone Detection

Note: For systems using Dialogic Digital (T1 or E1), VoIP or Brooktrout connections, Disconnect Tone or Call Progress Tone detection is not required. For Dialogic Digital (T1 or E1) connections, you can still define Special Tones.

Tones used on analog lines to indicate disconnect, busy and ringing vary depending on the PBX or Telecoms provider. ATS needs to know the characteristics of these tones in order to operate correctly.

When using ATS only for inbound calls, just the Disconnect tone is relevant. If you intend to use ATS for outbound calls also, then all Call Progress tones will need to be defined.

In addition to call progress tones, you can also specify special tones to be detected when re-recording from other systems that provide tone confirmation when playback of a dictation has completed.

Defining Disconnect Tone

There are two methods of defining Disconnect tone. You can follow the procedure in the Defining Call Progress Tones section (below) which will create the Disconnect definition for you (along with the other call progress tones). Alternatively, you can just define the Disconnect tone by following the instructions under Configuring the Winscribe Telephony Service.

Defining Call Progress Tones

To define all call progress tones, Dialogic's PBXpert software will be used to capture the tone characteristics and create a Tone Set File.

Note: To follow the procedure below, you will need to have two Dialogic lines connected to the PBX or Carrier, and know the phone numbers for each of these lines.

1. Ensure that the "Winscribe Advanced Telephony Server" and "Winscribe Telephony Server" services are both stopped. Use the Services applet in Administrative Tools to confirm this.

2. Ensure that the Dialogic drivers are started. Click on the "Start | Programs | Dialogic | DCM" shortcut to confirm this.

3. Click on the "Start | Programs | Dialogic | PBXpert" shortcut. The Tone Wizard will start. Follow the on screen instructions to create and save a tone definition file.

Note: On occasion, PBXpert dials too quickly for the PBX, resulting in tone detection failures. If this occurs, cancel the Tone Wizard, choose settings from the toolbar, and enter a comma in the Dial Prefix field. Restart the tone wizard and try again.

80


4. Click on the "Start | Programs | Dialogic | DCM" shortcut to start the Dialogic configuration manager. Make the following configuration changes to EACH analog Dialogic card:

a. Stop the Dialogic Service (click on the red toolbar button)

b. Double click on the card to open its configuration

c. Choose the 'Misc' tab

d. Set TSFFileSupport=Yes and DisconnectTone=Yes

e. Choose the 'Files' tab

f. Set the TSFFileName to the full path and name of the tone set file you created in the above steps

g. Start the Dialogic Service (click on the green toolbar button)

5. Restart the "Winscribe Telephony Server" and "Winscribe Advanced Telephony Server" services.

Defining Special Tones

Special Tones may be required when re-recording from some dictation systems which provide a tone confirmation when playback of a dictation job is complete. These tone definitions will cause ATS to stop re-recording a job when detected.

Up to five special tones can be defined.

In order to complete this procedure you will need to know the frequencies of the tone to detect.

1. Using Notepad, open the file 'WSDialog.ini' in your Windows directory

2. Find the section beginning with '[Tones]'

3. For single frequency tones, add the following line under the '[Tones]' section header, replacing the XXX with the frequency of your tone:

TONE_V= freq1=XXX:40

For dual frequency tones, add the following line under the '[Tones]' section, header, replacing the XXX and YYY with the two frequencies of your tone:

TONE_V= freq1=XXX:40,freq2=YYY:40

4. To add additional tones, repeat step 3, replacing TONE_V with TONE_W, TONE_X, TONE_Y or TONE_Z.

5. Save your changes to 'WSDialog.ini'

6. Restart the "Winscribe Telephony Server" and "Winscribe Advanced Telephony Server" services.

Note: In the tone definitions shown above, the figure 40 is a frequency deviation (an allowable deviation to still be considered valid for your tone). If you experience problems with special tones being detected, you can increase this number. Increasing the value beyond 100 is not recommended.

Key Logging

To configure ATS to log DTMF keys for a user, you need to edit ATS's configuration file. This file can be found in the installation directory and is called "wsATS.exe.config".

1. Open the configuration file using notepad.

2. Find the section which looks like:

<appSettings>

<add key="LogTonesUser0000" value="c:\User0000.log" />

</appSettings>

3. Change LogTonesUser0000 to match the user id you wish to log (e.g. for user id 555 change it to LogTonesUser555).

81


For example: <add key="LogTonesUser555" value="c:\User555.log">

The files will be saved under C:\ and can be found by searching for "User555.log".

4. To change the file where the information is logged, change the file name after "value=" on the same line

5. To log for additional users, copy the line and paste the copy immediately beneath the existing line, then repeat steps 3 & 4 for the new line. You can log to the same file, or change the filename to log to a different file.

6. Save the configuration file

Log File Contents

Log files will contain entries like: 12/31/2004 11:59:59 PM,UserId[1000],3

The date and time the log occurred appears first, followed by the Id of the user the log relates to. At the end of the line are the digits entered by the user. The digits entered may be blank if the user did not respond to a request for tone input.

Note: In order to begin logging, you must change the configuration file as described above, then STOP AND RESTART the Winscribe Advanced Telephony service using the services applet in Administrative tools.

82


Section 9: Installing Winscribe Voice over IP (VoIP) Winscribe's VoIP solution enables customers to build full-featured, scalable, and cost-effective dictation systems based on voice packets sent over the internet. It offers flexibility in configuring media processing features and cost of ownership savings because it avoids the tolls charged by ordinary telephone service. VoIP involves sending voice information in digital form in discrete packets over an IP network rather than using the traditional circuit-committed protocols of the public switched telephone network (PSTN). Winscribe VoIP software provides all of the functionality normally available with standard Winscribe Telephony, without the need for additional hardware.

HMP Software

The Winscribe VoIP solution requires HMP software to be installed.

For more information on Dialogic's VoIP HMP software, refer to the Dialogic website (http://www.dialogic.com)

The HMP software can also be downloaded from Dialogic (http://www.dialogic.com/products/ip_enabled/download/hmp_download.htm)

Important: If required, you can obtain a 4 port evaluation license from the same website. (Refer to the HMP Licensing section below for more details).

http://www.dialogic.com/

http://www.dialogic.com/products/ip_enabled/download/hmp_download.htm

83


HMP Licensing For one author to use VOIP dictation, you will need both an HMP license and a standard Winscribe

Telephony port license. There is a one-to-one relationship between the number of HMP licenses purchased and available phone lines in Winscribe. If, for example, the Winscribe server has eight lines available for telephone dictation, you would need to purchase eight HMP licenses.

HMP licenses can only be purchased in blocks of four, therefore you must have at least four Winscribe telephony licenses. Ensure you have the same number of Winscribe telephony licenses as HMP licenses. If you have more HMP licenses than Winscribe telephony licenses installed, no prompts will be played when an unlicensed Winscribe telephony port is called. For example, if you have two Winscribe telephony licenses and four HMP licenses, calls one and two will be processed normally, calls three and four will result in no prompts being played.

IMPORTANT: There is currently at least a 24 hour turnaround for production HMP license keys. Please contact your Winscribe Channel Account Manager before scheduling the installation to ensure the HMP License Key will be available.

There are two types of HMP licenses available:

1. Local (the bulk of VoIP traffic will reside on a LAN), or

2. Remote (the bulk of VoIP traffic resides on a WAN).

Local offers higher quality but consumes more bandwidth, while Remote is the opposite.

Dialogic offers a free 30-day evaluation HMP license that can be downloaded from the link below and used for testing purposes. This license does NOT include a Winscribe Telephony Port license. The Winscribe server requires at least one Telephony Port license in addition to the Dialogic HMP license for proper operation of VoIP.

Dialogic HMP 3.0 software and manuals can be downloaded from the link below.

Note: if Server 2008 is being used then HMP 3.0 Update 307 or later is required. Be sure to browse to the appropriate section at the bottom of the web page. Note: If Server 2012 is being used, then HMP 3.0 Update 343 or later is required.

http://www.dialogic.com/products/media-server-software/hmp-software/hmp-windows.aspx

Installation Overview There are two different procedures for installing Winscribe VoIP. Choose the option that most closely matches your current installation.

Option One: New Install (see page 83) Use this procedure on a server that has not previously had Winscribe software installed.

Option Two: Existing Winscribe Dictation Server without Telephony Use this procedure if you are installing VoIP onto a server which is already running the Winscribe Dictation Server software but not Winscribe telephony.

Note: Winscribe does not support the implementation or configuration of vendor's VoIP solutions. These procedures assume that your VoIP system is operational and presenting calls to the Winscribe server.

Installation Option One: New Install

Use this procedure on a server that has not previously had Winscribe software installed.

1. Download and install HMP software version (with all applicable HMP software updates applied).

84


When prompted by the HMP installation wizard to select which components to install, ensure that the Core Run-Time Package is selected. Other features may be installed as desired however they would not be used by Winscribe.

For assistance in activating the HMP license refer to the Licensing Transition Guide located in the Documentation section of the Dialogic web page http://www.dialogic.com/products/media-server-software/hmp-software/hmp-windows.aspx.

From the HMP License Manager:

a. Browse to the HMP License File.

b. Click the Activate License button.

2. Ensure the HMP Software is running, as follows:

a. Click Start | Programs | Configuration Manager - DCM.

http://www.dialogic.com/products/media-server-software/hmp-software/hmp-windows.aspx

85


b. Choose Configuration Manger DCM. This opens the Configuration Manager.

c. Check the HMP Software #0 item is displayed with a green arrow, as shown in the screenshot below.

If the HMP Software is not running, check that the HMP Services are started. Please refer to the documentation accompanying the HMP software for more information and troubleshooting.

3. Install the Winscribe Dictation Server (see page 33). Note the following:

In Step 8 of the procedure, select to install as Primary Server with Telephony Support.

In Step 9 of the procedure, select the Intel HMP radio button.

4. Open the Services window (from the Control Panel, select Administrative Tools, and then Services). The Winscribe Dictation and Winscribe IPPhone Services should now be displayed, as shown below.

Check that the IPPhone Service is set to start automatically by ensuring Automatic is displayed in the Startup Type column. If it is set to manual, change it to Automatic as follows:

a. Right-click on the Winscribe IPPhone Service and select Properties from the right-click menu. The Properties window will be displayed.

86


b. Change the Startup Type option in the General Tab on the Properties window.

Installation Option Two: Existing Winscribe Dictation Server without Telephony 1. Uninstall Winscribe Dictation Server.

2. Re-Install Winscribe Dictation Server following the outlined procedure:

a. Install the Winscribe Dictation Server. Note the following:

In Step 5 of the procedure, select to install as Primary Server with Telephony Support.

In Step 3 of Option 2: Install a Primary Server with Telephony, select the Intel HMP radio button.

Configuring the IPPhone Service The Winscribe IPPhone Service utilizes a configuration file called "WsIPMedia.cfg" which is located in the same directory as WsPhoneCards.exe. In most cases. Winscribe VoIP will run correctly once installed following the procedures above and there will be no need to modify this file.

For details on how to create or modify the configuration file, please refer to the Intel HMP documentation. The WsIPMedia.cfg file will allow multiple codecs to be specified, so if you have multiple types of IP-Phones using, for example, either G711Alaw and G711Mulaw CODECS, add both to the CFG file. In the example below, you would uncomment those 6 lines (i.e. remove the “#”). A sample of the configuration file follows:

87


#################################################################################### # IP Protocol : # The IP Protocol used for opening the IP Line devices, values: H323, SIP, both # # DTMFmode # possible options: # OutOfBand, inband, rfc2833 # # Capability possibilities: # g711Alaw # g711Mulaw # gsm # gsmEFR # g723_5_3k # g723_6_3k # g729a # g729ab # t38UDPFax # # Note: if you want to run the demo with coder g729 use: # g729a for running with VAD disable # and 729ab for running with VAD enable # # Caution: # If capability is g711Alaw /Mulaw ==> FramesPerPkt = 10,20,30. # G711 frame per packet defines the packet size in milliseconds # If capability is g723_5_3k / 6_3k ==> FramesPerPkt = 1, 2, 3 . # FrameSize isn't needed, default= 30ms. # If capability is gsm ==> FramesPerPkt = 1, 2, 3 . # FrameSize isn't needed, default= 20ms. # If capability is gsmEFR ==> FramesPerPkt = 1, 2, 3 . # FrameSize isn't needed, default= 20ms. # If capability is g729a ==> FramesPerPkt = 3, 4 . # FrameSize isn't needed, default= 10ms. # VAD disable, the VAD parameter is ignored # If capability is g729ab ==>FramesPerPkt = 3, 4 . # FrameSize isn't needed, default= 10ms. # VAD enable, the VAD parameter is ignored # #################################################################################### ipProtocolName = H323 DTMFmode = inBand Channel = 1-120 { Capability { # TxType = g711Alaw # TxFramesPerPkt = 30 # TxVAD = 0 # RxType = g711Alaw # RxFramesPerPkt = 30 # RxVAD = 0 TxType = g711Mulaw TxFramesPerPkt = 20 TxVAD = 0 RxType = g711Mulaw RxFramesPerPkt = 20 RxVAD = 0 # TxType = t38UDPFax } MediaAlarmLostPackets { Threshold = 20 # Threshold value DebounceOn = 10000 # Threshold debounce ON DebounceOff = 10000 # Threshold debounce OFF Interval = 1000 # Threshold Time Interval (ms)

88


PercentSuccess = 60 # Threshold Success Percent PercentFail = 40 # Threshold Fail Percent } MediaAlarmJitter { Threshold = 60 # Threshold value DebounceOn = 20000 # Threshold debounce ON DebounceOff = 60000 # Threshold debounce OFF Interval = 5000 # Threshold Time Interval (ms) PercentSuccess = 60 # Threshold Success Percent PercentFail = 40 # Threshold Fail Percent } # MediaAlarmResetAlarmState = 0 }

Section 10: Post Installation Steps & Licensing This section details the steps required following the installation of the Winscribe Server in order to ensure correct operation of the software and explains how to register a Winscribe server.

To Check Correct Operation of Winscribe Server Software:

Following installation and after the Winscribe Server has restarted, you can check the correct operation of the Winscribe Server by following the steps below.

1. Click Start | Settings | Control Panel | Administrative Tools | Services. Ensure that the services listed below are showing a status of 'Started'.

You should see a service called Winscribe Dictation. This is required for telephone and PC based systems.

For systems using Dialogic Telephony cards, you should see a service called Winscribe Dialogic

For systems using HMP Telephony, you should see a service called Winscribe IPPhone

89


2. Click Start | Settings | Control Panel | Administrative Tools | Event Viewer to check the Event Log. You should see an entry in the application log displaying 'Winscribe'. Double click the entry to display the Event Detail window.

3. If errors have occurred during start up, there may be entries in the Application Event log that

explain the problem. Check these before calling technical support.

4. You should also check the System Event log for messages from the Service Control Manager. These may highlight any problems encountered during start up.

5. If you have the Dialogic telephony option on your Winscribe Server, ensure the cables are connected correctly to your telephone extensions, and call the Winscribe system to confirm correct operation.

Licensing your Winscribe Software To license your Winscribe Software, install the Winscribe License Server and contact Winscribe Technical Support via e-mail to obtain the required software licenses. Refer to the Winscribe License Server Installation and User Guide for more details.

How Many Licenses Do You Need?

A Winscribe license is required for:

Each Winscribe Typist working online at any one time.

Each Winscribe for Smartphones or Winscribe for BlackBerry Smartphones user that wishes to upload jobs to the Winscribe server.

Each telephone port you wish to activate. (For example, although a 4-port card is installed you can choose to license only 2 ports. Winscribe Telephony will then answer on only 2 of the 4 available ports.)

Each Winscribe Author that wishes to use client or server speech recognition.

Winscribe Exporter. The license for this application is based on the number of hours of jobs you export each month.

Contacting Winscribe Technical Support

To obtain Winscribe Licenses, email Winscribe Technical Support (mailto:[email protected]).

For an immediate response, use the following telephone contacts:

USA Callers

mailto:[email protected]

90


Chicago Helpdesk: 1866 4 WINSCR (1866 4 946727)

Pacific Helpdesk: 1866 WINSCRI (1866 9467274)

Asia Pacific

Tel: +64 (9) 486 9010

Austria, France, Germany, Switzerland, BeNeLux

Tel: +41 44 934 50 35

UK and the rest of Europe

Tel: +44 (0) 118 984 2133

You must provide the following information before licenses can be issued:

The Installation ID from the Winscribe License Server.

The version number you are installing.

The site name of the installation.

If you do not have Winscribe Software Assurance, a valid purchase order number for the required number of licenses must be provided.

Refer to the Winscribe License Server Installation and User Guide for more details.

91


IIS File-size Limit IIS6 comes with a limit on the size of files that are allowed to be transferred via ASP scripts. This limit blocks large Winscribe jobs from being downloaded. You can increase this limit by following the instructions for the appropriate version of IIS below:

In some cases, the 'Request Filtering' option is not available. In this case, update maxAllowedContentLength in the web.config file at: C:\Program Files (x86)\Winscribe\Web Components\Data Provider

<security> <requestFiltering> <requestLimits maxAllowedContentLength='200000000'/>  </requestFiltering> </security>

This setting may need to be adjusted when uploading large files from the authoring apps, or the Importer. Be sure to restart IIS afterwards for your change to take effect.

NOTE: Although your DSS file may be less than 30mb, the file conversion to VOX increases its size by over 100%, so it's the size of the VOX file that is relevant here (e.g. a standard SP DSS file from a DS4000 that is approx 5 hours long is 31.6mb in size, but the resultant VOX file will actually be 72mb in size).

92


This chapter will guide you through the steps required to install the Winscribe Server Manager Applications software.

Winscribe Server Applications Software includes software tools that are run against one or more Winscribe Servers. These tools include:

Telephony and Web Managers

Exporter

Active Directory Synchronization Tool

Note: The purpose of this document is to provide installation guidance. For a description on how to use the Winscribe Server Applications, please refer to the appropriate user guide.

Section 1: Winscribe Telephony Manager Winscribe Telephony Manager is used to manage and configure the telephony portion of your Winscribe digital dictation system.

1. Run the supplied Winscribe Telephony Manager.msi. This launches the Telephony Manager Installation Wizard.

Click Accept and Install.

Or click Options to change any of the default settings:

Chapter 2. Installing Winscribe Server Manager Applications

93


a. Select the folder where Telephony manager will be installed:


b. Click Install to install Telephony Manager:


94


3. Depending on your setup, you may be required to enter your database connection credentials:

Click Yes to continue.

4. Enter the advanced features password:

Click OK to continue.

5. Enter the Winscribe Database connection credentials and click OK.

If you are using an instanced database, specify the full instance name in the Database Server path, for example: (local)\SQLExpress.

6. Winscribe Telephony Manager will now launch, if you ticked for it to (at step 2).

Configuring Telephony Manager

After installing Telephony Manager, you can open the Winscribe Telephony Manager Setup window to configure it:

1. Click Start | Programs | Winscribe | Winscribe Telephony Manager.

2. Enter your user id and password, then click the Advanced button to access the Winscribe Client Setup window.

95


The Server Tab

The Shared Directory & Telephony Servers section points to the shared directory you set up on the Primary Winscribe Server and to the names of the Winscribe Secondary Servers 1-5.

Shared Directory Enter the path to the shared directory. This can be a mapped drive on the client computer, however for security reasons it is recommended that you use a UNC name (eg \\MachineName\ShareName). If you change the name of the Winscribe Server or Shared directory name, you will need to modify this parameter on each client.

Telephony Server 1-5 For sites that have installed the Winscribe Author & Typist Telephone interface, this parameter must point to the name of the Primary Winscribe Server for the first entry and to any subsequent Winscribe Servers that have Dialogic telephony boards installed for the remaining entries. This parameter must be present for System Managers who will have access to viewing telephone port activity & disconnecting telephone users. If the entry is incorrect or missing the System Manager will receive an error message when attempting to view telephone port activity. Refer to the Telephony Manager User Guide for more information on this feature.

The Database Tab

In the Server Name field enter the name of the server where the Winscribe database is installed. If you are using an instanced database, specify the full instance name in the Database Server path, for example: (local)\SQLExpress.

The other fields on this tab can be used to modify any other properties as required.

96


When you have finished configuring Winscribe Telephony Manager, click the OK button to return to the Winscribe Manager Logon dialog box.

Section 2: Winscribe Web Manager Winscribe Web Manager adds browser based administration capabilities to Winscribe Digital Dictation systems. Using a standard web browser, Winscribe System Managers can create and update facilities, users, job types and departments as well as monitor and produce reports from their Winscribe Digital Dictation system.

Winscribe Web Manager is a Microsoft .NET application, which runs on one or more IIS servers installed on the same LAN as the Winscribe Digital Dictation system it manages.

Installation Summary The following table gives a summary of the steps you need to take to install Winscribe Web Manager on an existing Winscribe installation.

Step

1 Decide on the installation configuration (see page 96).

2 Install prerequisites (see page 97).

3 Run the Winscribe Web Manager Setup wizard.

4 Configure job upload functionality (see page 105) (if required).

5 Set up Database Mail for use with Alarm Email Notification and Workflow Email Notification (see page 107) (if required).

Installation Configuration

Winscribe Web Manager can be installed on the main Winscribe Server, or on a separate server. In sites where there is likely to be more than fifteen concurrent Winscribe Web Manager Users, we recommend a separate server.

Minimum Hardware and Software Requirements The server you intend using must have the following minimum requirements:

Windows 2003 Server with Service Pack 2 (or higher), Windows 2008 Server, Windows 2008 Server R2, Windows 2012 Server, Windows XP with Service Pack 2 (or higher) or Windows Vista with Service Pack 1 or higher (all versions except Home Basic and Home Premium).

Internet Information Server (IIS) version 5.0 or newer


1000 MHz or higher Pentium-compatible CPU

512 megabytes (MB) of RAM recommended minimum; more memory generally improves responsiveness

2GB hard disk with a minimum of 800MB of free space for installing Winscribe Web Manager


97


Security Note: for security purposes, Microsoft recommends that all drives used with IIS be formatted with NTFS, also the web site that is created during the Winscribe Web Manager Installation should be on a separate partition to the operating system.

VGA Monitor, Keyboard & Mouse

10/100Mbit network card, TCP/IP protocol

If connecting Winscribe Web Manager directly to the Internet, an IP address from your Internet Service provider will be required.

Install Prerequisites

Winscribe Web Manager requires the following software to be installed before running the Winscribe Web Manager Setup Wizard:

Internet Information Services (IIS)

Microsoft .NET 4

Crystal Reports Runtime Version 13.0

Notes:

You must install Microsoft .NET 4 before installing Crystal Reports Runtime Version 13.0.

You must have .NET 4 installed for Winscribe Web Manager to run. Other versions of Microsoft .NET Runtime may also be installed alongside, but will not be used by Winscribe.


Installing Microsoft .NET 4




Security Warning: If you are installing on Windows 2003 Server, you will need to configure IIS to Allow ASP.NET extensions. If you do not, you will receive 404 File not found errors when browsing to the Managers interface.

Installing Crystal Reports Runtime 13

To install Crystal Reports Runtime 13



Utilities / Crystal Reports Runtime 13

Or

Run the installer by double clicking on the following file:

Software / Utilities / Crystal Reports Runtime 13 / CRRuntime_32bit_13_0_5.msi


98


Installing Winscribe Web Manager

Note:

The instructions below detail the installation of the Winscribe Web Manager. The installer used (Winscribe Web Components) additionally enables installation of the Data Provider and the Mobile Web Service. If you would like to install all three web components at the same time, follow the instructions in Appendix 3. Installing the Web Components (Full).

Prerequisite Requirement: The Web Manager requires .NET 4 and Crystal Reports Runtime 13 to be installed.

To install the Winscribe Web Manager:




Note: In order to install Winscribe Web Manager, you must be logged in with local Administrative rights. If you intend using NT authentication to access the Winscribe Database Server, then you must have admin rights to SQL Server as well.



99



3. Select to install Web Manager, and then click Next:

4. Prerequisite check:

The installer will check that Crystal Reports Runtime 13 has been pre-installed.

If you need to install the runtime, the instructions are here:

Once the prerequisite check is OK, click Next to continue.

100



Enter your database Username and Password.

Click Next.

Note: This screen will not appear if installing on a PC with the Dictation Server already installed.

6. Click Install to begin the installation process:

The Winscribe Web Manager Setup wizard will copy the required files to your local hard disk. This may take several minutes to complete.

7. Once the installation process has completed, the Web Manager Configuration wizard appears.

Click Next to commence configuration.

101


8. Enter the language and time format defaults for Winscribe Web Manager.

The time format default controls the format time will be displayed in, for example 10pm is displayed as 10:00pm in the 12 hour format, or 22:00 in the 24 hour format.

9. Enter the Root Login password.

The Root Login is used to log in to the Winscribe Web Manager and change the database login details.


10. Enter the Admin Login password.

The Admin Login is used to log in to the Winscribe Web Manager and change server-wide parameters, which affect all facilities on a Winscribe Server.

102


If Web Manager has been installed before (for example, if you are upgrading to a new version), you can retain your previous Admin login and password by ticking the 'Keep current username and password' checkbox.


11. Enter the Owner Login password.

The Owner Login is used to log in to the Winscribe Web Manager and add and change facilities.

If Web Manager has been installed before (for example, if you are upgrading to a new version), you can retain your previous Owner login and password by ticking the 'Keep current username and password' checkbox.


12. Enter the name of an SMTP server that the Winscribe Web Manager can use to send emails.

If you do not enter the SMTP server name, the password retrieval email feature will not operate.


103


13. If Winscribe is being installed at a site that utilizes Active Directory and you wish to take advantage of Active Directory's 'Single sign on' feature for applications, select the Use Active Directory Integration radio button.

Enter the name of the Domain you wish to query for a list of authorized Winscribe users.

Enter the user name and password of a Domain administrator account that has sufficient permissions to query the Active Directory database for a list of those users.

If the site is not using Active Directory please leave the default setting Not Using Active Directory Integration.


14. Enter the path to the Winscribe server:


104


15. You are now ready to complete the Winscribe Web Manager configuration.

Click Save to save the settings you have entered, or press Back to make changes.

16. The Configuration Wizard saves your settings, displaying progress as it goes.

Click Finish to complete the Winscribe Web Manager configuration.

17. The Winscribe Web Manager Installation Complete window is displayed. Click Close to complete the installation and exit.

105


Next Steps The Winscribe Web Manager is now installed. Browse to http://<Winscribe Server Name>/winscribenet and logon using the default Winscribe Manager Id and password: User ID: 1111/ Password: 0000. Additional Manager IDs can now be added to your Winscribe system as desired.

Note: The first time you browse to the site it will take a few moments to display. From then on the page should appear immediately.

Configuration of the Job Upload functionality

Web Manager is not limited to use by Systems Administrators. Authors may also log into Web Manager using their Winscribe Author ID and password, to check the status of their jobs and to upload new jobs. The Job Upload functionality allows an author to browse to a directory or USB recording device attached to a local PC and upload audio files to the Winscribe server. The Winscribe Server must also have the Winscribe Importer installed for the Job Upload function to operate correctly.

Overview of Script Functionality

The Job Upload page contains several fields that aren't recognized by the Importer. These fields are 'Pretype Review', 'Posttype Review' and 'TypistID'. In order for these fields to be imported, the following process occurs:

1. The Job Upload website (used by the author), writes these fields into the .wst file upon upload.

2. An Importer script (see page 105) extracts this information from the .wst file and stores them in the job's notes field.

3. When the job information arrives at the database (e.g. a new row in the Job table), a SQL trigger (see page 106) is activated, extracting fields out of the Notes and placing them correctly into the database.

The end result is the ability for the Importer to route directly to a typist and mark the job for Pretype and/or Posttype Review.

Procedure for Configuring Job Upload

The following table gives a summary of the steps you need to take to enable the Importer to route directly to a typist and mark the job for Pretype and/or Posttype Review.

Step

1 Create a Script (see page 105).

2 Create the SQL Trigger (see page 106).

3 Specify the source (see page 106)

4 Specify the destination (see page 106)

5 Create a new rule (see page 106).

6 Start the Importer Monitor (see page 107).

Step 1: Create a Script

1. Install Winscribe Importer or Importer Service on the Server hosting the Web Manager application according to the instructions in the Winscribe Importer Guide.

2. From the Importer User Interface select File | New | Script.

106


3. Copy the text from the Job Upload file on the Winscribe Distribution DVD. This file is located in the following directory:

Software\Addins\Author Job Upload\Job Upload.vbs

4. Paste the text into the Script window.

Step 2: Create the SQL Trigger

There are two methods of creating the SQL Trigger. One method is for those who use SQL Server Management Studio, and the other method is for those who do not. Both methods are detailed below.

Use the following procedure to create the sql trigger if you have SQL Server Management Studio:

1. In SQL Server Management Studio, drill down into the Job Table of the Winscribe Facility to where you wish to apply the trigger, and expand the Triggers folder. Right click on the Triggers folder and click on "New Trigger...".

2. Copy the text from the Upload Trigger file on the Winscribe Distribution DVD 1. This file is located in the following directory: \SOFTWARE\Addins\Author Job Upload\Uploadtrigger.sql

3. Paste the text into the NewTriggers window. Execute the new trigger and it should now appear under the Triggers folder.

4. If the system uses multiple facilities, you will need to repeat the trigger creation for each facility name.

Use the following procedure to create the sql trigger if you do not have SQL Server Management Studio:

1. Load the Winscribe Distribution DVD 1, and locate the Upload Trigger file. This file can be found in the following directory: \SOFTWARE\Addins\Author Job Upload\Uploadtrigger.sql

2. Save the file into the c:\ directory and execute the following command from a command prompt on the database server:

osql -U sa -d Winscribe -i c:\UploadTrigger.sql

You will be prompted to enter the sa password if it is blank. Just press Enter.

3. If the system uses multiple facilities, you will need to repeat the above command for each additional facility, substituting "Winscribe" with each facility name.

Step 3: Specify the Source

In Internet Importer, configure a Source definition that will scan the directory that has been automatically created. Refer to the Internet Importer User Guide for more details on creating source definitions.

Step 4: Specify the Destination

In Internet Importer, specify the destination. Typically this is the Winscribe Dictation server. E.g. http://<servername>/winscribe.

Refer to the Internet Importer User Guide for instructions on creating destination definitions.

Step 5: Create a new Rule

In Internet Importer, create a new Rule that defines the source and destinations you set up previously and selects the script to run as defined in step 1.

107


Refer to the Internet Importer User Guide for instructions on creating rule definitions.

Step 6: Start the Importer Monitor.

Start the Importer Monitor either by starting the service if it's installed as a service, or by opening the application and starting monitoring if it's installed as an application.

Setting up Database Mail for use with Alarm Email Notification and Workflow Email Notification If you wish to use the email notification features of Web Manager and/or Winscribe Client, you must first configure Database Mail using the SQL Server Management Studio. Email notification enables the system to notify users when alarms are triggered or jobs are redirected. For example, the system can notify typists by email when they get a priority job, or notify managers, authors or typists by email when jobs have waited too long for typing.

Minimum Requirements: SQL Server 2005 Standard Edition or higher. To send Database Mail users must also be added to the DatabaseMailUsersRole in the msdb database.

Use the following steps to configure email sending for use with Alarm notification and Workflow:

1. Open Microsoft SQL Server Management Studio and expand Management in the tree view.

2. Right click on Database Mail and choose "Configure Database Mail". If Database Mail has never been configured on the server, you will be prompted to enable it.

108


3. The Database Mail Configuration wizard appears and steps you through setting up database mail.

4. In the Select Configuration Task window, select Set up Database Mail by performing the following

tasks. Click Next to continue.

109


5. In the New Profile window, specify the profile name and description. Click the Add button to add an STMP account to the profile.

6. Specify the details of the SMTP account, as follows:

Field Name Description

Account Name / Description Enter the account name and a description of the SMTP account.

Email Address Enter the email address to which notifications will be sent when alarms are triggered.

Display Name Enter a meaningful name for the reply email address. For example 'Notification System'.

Reply email Enter the email address that the emails will be generated from (the system email address).

Server Name Enter the name of your Server.

SMTP Authentication Select whether to connect using Windows authentication, Basic Authentication or Anonymous authentication.

110


7. After setting up database mail, ensure that the profile you set up is a public profile, and it is set as the default profile. You can check this by right clicking Database Mail and choosing Configure Database Mail. Click Next on the Welcome screen and select Manage Profile Security, then click Next again. The public column should be ticked and Default Profile set to Yes, as shown below.

8. Ensure that you can send email using this default profile by right clicking on Database Mail in

Microsoft SQL Server Management Studio and choosing "Send Test E-Mail..." from the menu.

Section 3: Winscribe Exporter Winscribe Exporter adds export capabilities to Winscribe Digital Dictation systems. Exporting is the process of taking Winscribe-encrypted dictation stored on the Winscribe Server, extracting the audio and data associated with the job and sending the information to another location in another audio format. VB & Java Scripting allow you to change or access a job's data while the job is being exported. For example a script can be set up to:

Abort exporting of the job.

Read job data such as a user field.

Change job data such as the job file name and priority.

Winscribe Exporter consists of two components:

1. Exporter Service: The Export Service which performs the actual export of Winscribe Jobs and runs as a Windows Service.

2. Exporter Manager: The web-based interface for the Winscribe Exporter that allows you to configure the parameters for jobs to be exported. This component is a Microsoft ASP.NET application, which runs on one or more IIS servers installed on the same LAN as the Winscribe Digital Dictation system it manages.

Installation Summary

The following table gives a summary of the steps you need to take to install Winscribe Exporter on an existing Winscribe installation.

Step

111


1 Decide on the installation configuration (see page 111)

2 Install prerequisites (see page 111)

3 Run the Winscribe Exporter Service Setup wizard

4 Run the Winscribe Exporter Management Setup wizard

5 Enable scripts to perform additional functions (optional), refer to the Exporter Administrator Guide for details.

Installation Configuration

Both of the Winscribe Exporter components can be installed on the main Winscribe Server, or on a separate server. In sites where there is likely to be large volumes of jobs exported (over 200 per day), or if converting to WMA or MP3 format, we recommend a separate server.

Minimum Hardware and Software Requirements The server you intend using must have the following minimum requirements:

Windows 2003 Server with Service Pack 2 (or higher), Windows 2008 Server, Windows 2008 Server R2, Windows 2012 Server, Windows XP with Service Pack 2 (or higher) or Windows Vista with Service Pack 1 or higher (all versions except Home Basic and Home Premium).

Internet Information Server (IIS) version 5.0 or later.


2GHz or higher Pentium-compatible CPU.

256 megabytes (MB) of RAM recommended minimum; more memory generally improves responsiveness.

2GB hard disk with a minimum of 800MB of free space for installing Winscribe Web Manager.

A standalone server when exporting to WMA or MP3 voice formats.

Security Note: for security purposes, Microsoft recommends that all drives used with IIS be formatted with NTFS. In addition, the web site that is created during the Winscribe Exporter Manager Installation should be on a separate partition to the operating system.

VGA Monitor, Keyboard & Mouse.

10/100Mbit network card, TCP/IP protocol and a static IP address.

If connecting Winscribe Exporter Manager directly to the Internet, an IP address from your Internet Service provider will be required.

Install Prerequisites Winscribe Exporter

Winscribe Exporter requires the following software to be installed before running the Winscribe Exporter Setup wizard:

Microsoft .NET 4.

Install DirectX End-User Runtime 8.1 and Windows Media Player 9 or higher if you wish to use Exporter to convert files to WMA (Windows Media Player) format.


112


If installing Winscribe Exporter on Windows Server 2008, 2008 R2, or 2012, 'Desktop Experience' must be already installed. Refer to Installing Winscribe on a Microsoft Windows 2008 Server (see page 57) for more details.

Winscribe Exporter Manager

Winscribe Exporter Manager requires Crystal Reports Runtime 13.0 to be installed before running the Winscribe Exporter Manager Setup wizard.

Notes:

You should install Microsoft .NET 4 before installing Crystal Reports Runtime 13.0.

You must have .NET 4 installed for Winscribe Exporter to run. Other versions of Microsoft .NET Runtime may also be installed alongside, but will not be used by Winscribe.







Installing Crystal Reports Runtime 13





Or




Installing Support for WMA (optional)

With Winscribe Exporter you can export Winscribe VOX files to WMA (Windows Media Player) format if required, along with an associated tag file.

To convert files to this format, you must have DirectX End-User Runtime (Version 8.1 or higher) installed. You can obtain DirectX End-User Runtime 8.1 and Windows Media Player 9 or higher from Microsoft (http://www.microsoft.com/directx). Follow the on screen instructions to complete the installation.

Supported Export Formats

The table below details the voice file formats supported by Winscribe Exporter.

http://www.microsoft.com/directx

113


WMA MP3 WAV G???

5kbps, 8kHz mono

6kbps, 8kHz mono

8kbps, 8kHz mono

8kbps, 11kHz mono

10kbps, 11kHz mono

10kbps, 16kHz mono

12kbps, 8kHz

12kbps, 16kHz mono

16kbps, 16kHz mono

16kbps, 16kHz

16kbps, 22kHz mono

20kbps, 16kHz

20kbps, 22kHz mono

20kbps, 22kHz

20kbps, 32kHz mono

20kbps, 44kHz mono

22kbps, 22kHz

32kbps, 22kHz

32kbps, 32kHz

32kbps, 44kHz mono

32kbps, 44kHz

40kbps, 32kHz

48kbps, 32kHz

48kbps, 44kHz mono

48kbps, 44kHz

64kbps, 44kHz

64kbps, 48kHz

80kbps, 44kHz

96kbps, 44kHz

96kbps, 48kHz

128kbps, 44kHz

128kbps, 48kHz

160kbps, 44kHz

160kbps, 48kHz

192kbps, 44kHz

192kbps, 48kHz

256kbps, 44kHz

320kbps, 44kHz

44kHz, Lossless

44kHz VBR 10

44kHz, VBR 25

44kHz, VBR 50

44kHz, VBR 75

44kHz, VBR 90

44kHz, VBR 98

8 KHz, 8 Kbps

8 KHz, 16 Kbps

8 KHz, 32 Kbps

11 KHz, 8 Kbps

11 Khz, 16 Kbps

11 KHz, 32 Kbps

8kHz 8 bit

8kHz 16 bit

11kHz 8 bit

11kHz 16 bit

22kHz 8 bit

22kHz 16 bit

MS ADPCM 8Khz

MS ADPCM 11Khz

GSM 6.10 8KKhz

GSM 6.10 11Khz

GSM 6.10 22Khz

G721:

8Khz

11Khz

G73:

8Khz, 3 bit

8Khz, 5 bit

11Khz, 3 bit 11Khz, 5 bit

G726:

8Khz, 4 bit

8Khz, 5 bit

11Khz, 4 bit

11Khz, 5 bit

114


WMA MP3 WAV G???

48kHz, VBR 90

48kHz, VBR 98

In addition Export supports the following Winscribe formats:

VOX: 8Khz, 4 bit.

Winscribe Encrypted: 8Khz, 4 bit.

Warning: We recommend that Winscribe Exporter is installed on a separate server to Winscribe Server when exporting to MP3 or WMA formats. Conversion to these formats could degrade performance of the Winscribe Server (depending on volumes).

Installing Winscribe Exporter Service & Manager 1. Run the supplied Winscribe Exporter.msi. This launches the Winscribe Exporter Setup Wizard:

Click Accept and Install to install the Service and the Manager to the default destination folder.

Or, click Options to specify the destination folder and/or which feature of Exporter to install:

a. Select the required destination folder:


115


b. Select the feature to install:

Click Install to begin the installation.

2. You are now ready to configure the installation:


3. Select the language for the installation and click Next.

116


4. Enter the SQL Server details and click Next.

5. Enter the SMTP server details (if required) and click Next.

6. Click Save to update the settings:

117


7. The configuration will be saved.

Click Finish to begin the installation.

8. The Export will be installed:

Click Finish to complete the installation.

Next Steps The Winscribe Exporter Manager is now configured. You can now browse to the virtual directory you created during setup and logon using an existing Winscribe Manager Id and password.

Note: The first time you browse to the site, Exporter Manager may take a few moments to display. From then on the page should appear immediately.

Section 4: Winscribe Active Directory Synchronization Winscribe provides single sign on functionality via Microsoft Active Directory.

With Active Directory mapping, users are not required to enter their credentials into the Winscribe Login screens to activate client applications such as Typist, Author and Manager. Furthermore, Active Directory user information is also transferred from the Active Directory to the Winscribe Database for users with a mapped account.

A synchronization tool can be scheduled to be run on a regular basis via Windows Scheduler that updates the Winscribe Database with any changes made to the AD User account.

118


Single Sign-on Configuration Enabling the single sign-on feature requires the following steps:

Configure the Active Directory Settings.

Define the User Accounts Mapping.

Modify the Winscribe Server Authentication Methods.

Modify the Web Manager Authentication Methods.

The table below specifies which configurations steps are necessary depending on the application(s) requiring single sign-on.

Application Requiring Single Sign-on

Necessary Configuration

Active Directory Settings

User Accounts Mapping

Winscribe Server Authentication Methods

Web Manager Authentication Methods

Winscribe Author

Winscribe Client

Internet Author

Web Manager

The following sections describe the necessary configuration steps.

Active Directory Settings

Enabling single sign-on requires the definition of an Active Directory Domain Name and credentials with sufficient permissions to query the Active Directory database. These settings are defined using the Winscribe Web Server Settings application.

Note: Windows authentication through Active Directory requires that the Winscribe Server that is referenced by the client application has been setup using the machine name and not the machine IP address.

Check the client registry key as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\WINSCRIBE\GENERAL\WinscribeURL | http://servername/winscribe

-and-

HKEY_CURRENT_USER\SOFTWARE\WINSCRIBE\GENERAL\WinscribeURL | http://servername/winscribe

Installing the Winscribe Active Directory Synchronization Tool

The Winscribe Active Directory Synchronization tool copies user details from Active Directory into the Winscribe database. This allows system administrators to maintain user details in a central data store, i.e. the Active Directory.

Install Prerequisites

The Winscribe Active Directory Synchronization tool requires Microsoft .NET Runtime 4.0 to be installed before running the Setup wizard:

119


Notes:

You must have .NET 4 installed for Winscribe Active Directory Synchronization to run. Other versions of Microsoft .NET Runtime may also be installed, but will not be used by Winscribe.

To successfully complete this installation, you must have local administrative privileges.






Winscribe Active Directory Synchronization Installation Procedure

1. Insert the Winscribe Distribution DVD into the DVD drive on the Winscribe Server. If the PC is configured to autorun, the Options Menu will be displayed. If not, browse to the DVD and double-click the start.html file in the root directory.

2. Click Active Directory Sync Tool to launch the Active Directory Sync Tool Installation Wizard.

3. Follow the on-screen directions to complete the installation.

Configuring the Winscribe Active Directory Synchronization Tool 1. Click Start | Programs | Winscribe | Tools | WEB Server Settings.

2. Select the Active Directory tab.

Enter the following details:

Domain Name of the users requiring single sign-on.

User Name and Password of account to be used when querying Active Directory

Click OK.

3. Setup a scheduled task to execute the Winscribe Active Directory Synchronization utility.

120


On 32-bit operating systems, the Winscribe.Dictation.WinscribeActiveDirectorySync.exe utility is located in the Windows applications folder: C:\Program Files\Winscribe\Active Directory Sync Tool

On 64-bit operating systems, the utility can be found here: C:\Program Files (x86)\Winscribe\Active Directory Sync Tool

This utility updates Winscribe user accounts with the details found in Active Directory accounts. The following details are updated:

First name

Surname

Title

Work phone number

Mobile phone number

Pager number

Fax number

Email address

Server 2003 — Authentication Methods Enabling or disabling Single Sign On is performed in the Web Components installer and can be done either at the time of installation or later.

When doing a fresh install:

If doing a fresh install, install Web Components and enable the Single Sign On feature.

121


When Web Components are already installed:

1. If Web Components are already installed, go to Programs and Features, right-click on Winscribe Web Components, and select Change:

2. Click Next:

122


3. Click Change:

4. When you come to the Product Features selection, select to Enable Single Sign On:

Client Apps

Following are the sequence of steps for configuring single sign-on for client apps in IIS for Microsoft Server 2003.

Enabling single sign-on for the Winscribe Author, Winscribe Client, Internet Author and/or Internet Importer applications on servers running Microsoft Server 2003 requires the following modifications to the Winscribe Server:

Winscribe Authentication

Anonymous Authentication: Disabled

Windows Authentication: Enabled

123


1. From your Windows Start menu, select Administrative Tools. Double-click on the Internet Information Services (IIS) Manager. This opens the Internet Information Services Manager window.

2. In the left pane:

Expand the machine name

Expand the Web Sites tree

Expand Default Web Site

Right-click Winscribe

3. Select Properties:

124


4. In the Winscribe Properties window, select the Directory Security tab and click Edit in the Authentication and access control panel:

5. In the Authentication Methods window, enable Windows Authentication and ensure Anonymous

access is disabled:

Click OK.

6. You may now close the Winscribe Properties window and the IIS Manager.

Web Manager

Following are the sequence of steps for configuring single sign-on for Web Manager in IIS for Microsoft Server 2003.

Enabling single sign-on for the Web Manager on servers running Microsoft Server 2003 requires the following modifications to the Winscribe Server:

WinscribeNet Authentication

125





2. In the left pane:


Expand the Web Sites tree

Expand Default Web Site

Right-click WinscribeNet

3. Select Properties:

126


4. In the WinscribeNet Properties window, select the Directory Security tab and click Edit in the Authentication and access control panel:

5. In the Authentication Methods window, enable Windows Authentication and ensure Anonymous

access is disabled:

Click OK.

6. You may now close the WinscribeNet Properties window and the IIS Manager.

Server 2003 R2 SP2 — Authentication Methods Enabling or disabling Single Sign On is performed in the Web Components installer and can be done either at the time of installation or later.

127






128


2. Click Next:

3. Click Change:


129


Server 2008 — Authentication Methods Enabling or disabling Single Sign On is performed in the Web Components installer and can be done either at the time of installation or later.





130


2. Click Next:

3. Click Change:


131


Client Apps

Following are the sequence of steps for configuring single sign-on for client apps in IIS for Microsoft Server 2008.

Enabling single sign-on for the Winscribe Author, Winscribe Client, Internet Author and/or Internet Importer applications on servers running Microsoft Server 2008 requires the following modifications to the Winscribe Server:

Winscribe Authentication

Anonymous Authentication: Enabled

Basic Authentication: Disabled


Authorization

All anonymous users Deny


2. In the left pane (Connections):


Expand the Sites tree

Expand the Default Web Site tree

Double-click Winscribe

132


3. Click to open the Authentication applet:

4. Enable Windows Authentication, keep Anonymous Authentication enabled, and ensure Basic

Authentication is disabled:

5. Click to open the .NET Authorization Rules applet:

6. Click Add Deny Rules in the Actions panel:

7. Choose All anonymous users and click OK:

8. You may now close the IIS Manager.

133


Web Manager

Following are the sequence of steps for configuring single sign-on for Web Manager in IIS for Microsoft Server 2008, 2008 R2, 2012.

Enabling single sign-on for the Web Manager on servers running Microsoft Server 2008 requires the following modifications to the Winscribe Server:

WinscribeNet Authentication




2. In the left pane (Connections):


Expand the Sites tree

Expand the Default Web Site tree

Double-click WinscribeNet

3. Click to open the Authentication applet:

134


4. Enable Windows Authentication and disable Anonymous Authentication:

5. You may now close the ISS Manager.

User Accounts Mapping Enabling single sign-on for users of Winscribe applications requires associations between the Winscribe user accounts and the corresponding Active Directory account.

A given Active Directory account can be associated with up to three Winscribe user accounts:

Associate Active Directory accounts with Winscribe Author user accounts to provide single sign-on capability to the Winscribe Author and Internet Author applications.

Associate Active Directory accounts with Winscribe Typist user accounts to provide single sign-on capability to the Winscribe Client application.

Associate Active Directory accounts with Winscribe Manager user accounts to provide single sign-on capability to the Web Manager application.

If single sign-on for the Web Manager application is enabled, it is strongly recommended that the Active Directory user account(s) of user(s) accessing the Web Manager as Root, Admin, or Owner are not associated with Winscribe Manager user account(s). These associations would automatically login the users as Managers, preventing them from logging on as Root, Admin, or Owners.

The user account associations can be configured using Web Manager.

Note: If the Domain Account drop-down list remains empty after completing the configuration detailed in the previous section it may be necessary to restart the IIS Services.

Web Manager

1. Start the Web Manager application and go to one of the following pages:

Add Author

Update Author

Add Typist

Update Typist

Add Manager

Update Manager

135


2. Use the Domain Account selection to define the Active Directory account to be associated with a Winscribe user account.

3. Click to open the Domain User Search window.

You can perform partial searches for the user based on first name, last name, username or display name.

4. Select the user from the resulting list and click OK.

To clear the selected domain account, click .

Section 5: Installing Winscribe Internet Importer as a Windows Service

The following section will guide you through the steps required to install Winscribe Internet Importer. This configuration is used when you wish to run Importer as a Windows Service on the target machine. It is particularly useful when the ability to continuously monitor for job uploads from USB devices or for regular job uploads from a source directory is required. If Internet Importer is running as a Windows Service the monitoring process starts automatically as part of the PC’s boot process.

Note: It is recommended UAC is disabled before installing Internet Importer as a service on Windows Vista, Windows 7, 8, 8.1 and Server 2008, 2008 R2, 2012 operating systems. If UAC remains enabled, Importer must be launched "as an administrator" for configuration to work. Additionally, the Importer Service would need to run as an account with administrative privileges for logging to function.

136


Minimum System Requirements

Winscribe Importer will operate satisfactorily on any PC that meets the minimum requirements for the operating system in use: Windows 2003 Server with Service Pack 2 (or higher), Windows 2008 Server, Windows 2008 Server R2, Windows 2012 Server, Windows XP Service Pack 2 (or higher), Windows Vista with Service Pack 1 (or higher), or Windows 7, 8, 8.1.

If Dragon speech recognition is required, the PC must also meet the minimum requirements for that software.

Configuring Internet Importer

Configuration of the service is identical to the Importer running in application mode. Following installation, launch the Winscribe Importer from the Start menu and set source and destination targets. Monitoring starts automatically, and the service will continue monitoring in the background according to the parameters you have defined. For more information on the configuration of Importer, refer to the Winscribe Internet Importer User Guide.

To Install Internet Importer as a Service:

1. From within Windows close all open programs.


3. Click Internet Importer to launch the Winscribe Importer Installation Wizard.

Click Options to continue.

4. You will be prompted to select the type of application you wish Winscribe Importer to run as:

Windows Service, or

137


Windows Application.

Select to install as Windows service.


5. Accept the default Destination Folder, or click Change... to browse to an alternative folder. Click Next.

6. Click Install to begin the installation process. The Installation Wizard will start copying files to the

destination folder you selected. This may take several minutes to complete.

138


7. When the installation has completed, click Finish to close the Installation Wizard.

Configuring the Temp Folder when Importer is run as a Windows Service

By default, the Importer temporary directory is C:\Windows\Temp. However, Administrators may specify a desired temp folder using the following registry key:

HKEY_LOCAL_MACHINE / Software / Winscribe / Importer / TempDir

If this key is created, and its value set to a desired temp folder, the Importer will use that path instead of the default.

139

Chapter 3. Installing Client Applications

This chapter will guide you through installing the Winscribe Client applications. The setup process is the same whether installing under any of the supported operating systems:

Windows XP with Service Pack 2 (or higher)

Windows 2003 Server with Service Pack 2 (or higher)

Windows Vista with Service Pack 1 or higher (all versions except Home Basic).

Windows 2008 Server

Windows 2008 Server R2

Windows 2012 Server

Windows 7

Windows 8

Note: Winscribe operates on VMWare and Microsoft Virtual PC/Server. However please note that many hardware manufacturers' device drivers are not supported in these environments. Sound must be enabled on the virtual image, as follows:

If the Winscribe Server is installed on a virtual image and the Winscribe Clients are installed on fat client, no sound card is needed on the server.

If both the Winscribe Server and the Winscribe Clients are installed on the same virtual image then a sound card must be installed.

There can be instances where the installation package is required to install-on-demand, repair, or update the client application. If the installer is unable to locate the available source, the user is asked to provide the media or to go to a network location containing the needed sources. We recommend you ensure that the setup files are stored in a location that is accessible to all users. If pushing the client application out via group policy, map it to a shared network drive so it is accessible to all users on the network.

Section 1: Features and Prerequisites Winscribe Author, Winscribe Client, Internet Author, and Internet Importer:

Winscribe Internet Clients require that .NET 4 be installed on the client PC

Ability to communicate with the Winscribe server using the HTTP or HTTPS protocol over TCP/IP.

Require that Winscribe Web components be installed on the site’s Web server .

Are supported in a LAN/WAN environment and over the Internet.

Require IIS 5.0 (or higher) be installed at the site, either on the Winscribe server or another web-enabled server.

Can be configured to use password authentication, encryption, and certificates to secure access to dictation.

Allow users to work off-line (i.e. without a connection to the Winscribe Server)

Internet clients support multiple profiles on the same PC, i.e. configuration settings for each user are stored in a folder based on their User Id.

Can be installed over the Internet or from the Winscribe Distribution DVD.


140


If you choose to use the Internet Clients, the Web Components need to be installed on a computer running IIS (Microsoft Internet Information Server) version 5.0 or above. IIS can be installed on the Winscribe Primary Server, but if the Server has a connection to the Internet, for security reasons it is preferable to have the IIS Server on a separate machine or at least on a different drive partition to the operating system. If you already have an IIS Server, then the Winscribe Web Components can reside on that machine. For instructions on installing the Web components see Installing the Web Components (see page 45). Winscribe authoring clients use the WININET API, which is installed with Windows Internet Explorer, version 6.0 or greater.

Minimum Requirements: Winscribe Author, Winscribe Client, Internet Author and Importer

Windows 2003 Server with Service Pack 2 (or higher), Windows XP with Service Pack 2 (or higher), Windows Vista with Service Pack 1 or higher (all versions except Home Basic), Windows 2008 Server, Windows Server 2008 R2, Winsdows Server 2012, Windows 7 (Ultimate, Enterprise, Professional, and Home Premium only), or Windows 8, 8.1.

1 GHz or higher Pentium-compatible CPU.

If running Windows XP, 512 MB RAM (1 GB is recommended)

If running Windows Vista, 1 GB RAM (1.5 GB recommended)

1GB hard disk with a minimum of 100 MB of free space.

VGA Monitor.

Keyboard & Mouse.

Network Card (10/100Mbit recommended).

Microsoft Internet Explorer Version 6.0 or higher (Internet clients only).

Note: If using the browser provided by AOL (America Online) or any other browser supplied by an ISP, you must install Microsoft Internet Explorer as well.

High speed Internet connection for remote or mobile users (Internet clients only).

Sound Blaster or compatible sound card and headset.

USB foot control (optional). Dictation playback can be controlled with keyboard function keys or keyboard shortcuts.

Games Port on the sound card, or USB port depending on the type of foot control.

Winscribe Client

The typist can control dictation playback using a mouse, USB foot control, or a standard foot control. Any suitable headset may be used.

Winscribe Client is compatible with Microsoft Word 2003, Word 2007, Word 2010, and Word 2013.

Winscribe Author and Internet Author

Authors control their dictation using a mouse and microphone/speakers connected to a Sound Blaster or compatible sound card. Alternatively, various models of hand-held dictation microphones may be used and / or USB foot controls for hands-free dictation.

141


Section 2: Client Deployment Guidance

Overview

Client Installers

There are three client installers:

Winscribe Author.msi

Winscribe Internet Author.msi

Winscribe Client.msi

Installer Privileges

The client installers require administrative privileges.

Automatic Updates

Once the user logs in, the client will automatically check to see if a new version is available on the server.

If the current user does not have administrative privileges, then the update check will be canceled, avoiding the scenario of launching the installer when the user cannot run it.

The client will compare the product version of the client executable to the product version number on the server.

If an update is found, the client application will prompt the user, asking if they want to install the available update.

Command Line

You can set installer parameters from the command line.

Installers are run by the Windows Installer executable, called msiexec.exe.

Full details on the command line arguments for Windows Installer are available here: Command-Line Options @ msdn.microsoft.com

Examples

Installing an MSI msiexec /i "Winscribe Client.msi"

Uninstalling a product msiexec /x "Winscribe Client.msi"

Silent installation

You can do a silent installation that does not present any user interface or interaction by using the /quiet option. Note that the quiet option will also not show any error messages, and it is not readily clear if and when the installation has run and finished.

msiexec /quiet /i "Winscribe Client.msi"

An automated installation that does not involve any user interaction but provides a progress interface is called unattended mode, using the /passive option:

142


msiexec /passive /i "Winscribe Client.msi"

If you wish to have more control over how the Windows Installer interface behaves, you can read about the /q option in the Windows Installer documentation.

Passing Installer Properties

You can customize installation defaults and behavior by passing in values for known properties.

You pass in a property value by specifying the name (in all uppercase) and its value:

msiexec /i "Winscribe Client.msi" PROPERTYNAME=Value

As with command-line arguments, if an argument contains whitespace, you must enclose the value in quotation marks:

msiexec /i "Winscribe Client.msi" PROPERTYNAME="Value with whitespace"

Configuring Client Installer Properties

Configuring Features

You can configure what features to install or exclude by combining the ADDLOCAL and REMOVE properties.

NOTE: If you are selecting features, always use ADDLOCAL=ALL , and then selectively specify any unwanted features by adding them to the REMOVE property.

NOTE: The Author and Internet Author products only have one feature, therefore their features cannot be configured.

Example

The following example will install all features except for the Olympus hardware support:

msiexec /i "Winscribe Client.msi" ADDLOCAL=ALL REMOVE=Olympus

Removing Multiple Features

If you wish to exclude multiple features, you can separate them by a comma. No spaces are allowed in the REMOVE property, and you should not enclose the value in quotation marks.

Example

The following example will install all features except for the VEC Hardware support, and the Open Office Document Manager:

msiexec /i "Winscribe Client.msi" ADDLOCAL=ALL REMOVE=VEC,OpenOfficeDocumentManager

Client Option Features

By default, the Client will install all available features.

The following table lists the optional features you can configure, and the folder they are installed to (relative to the Client installation directory).

Feature Name Description Folder

MobileWebServiceImporter Importer Add-In AddIns\MobileWebServiceImporter

MicrosoftWordBasic Document Manager for Microsoft Word

AddIns\MicrosoftWordBasic

143


OpenOfficeDocumentManager Document Manager for Open Office

AddIns\OpenOfficeDocumentManager

FolderTemplateManager Template Manager AddIns\FolderTemplateManager

VirtualChannelFeature Virtual Channel support (Citrix/Terminal Services)

AddIns\VirtualChannel

GrundigFeature Grundig hardware support AddIns\Grundig

Olympus Olympus hardware support AddIns\Olympus

Philips Philips hardware support AddIns\Philips

VEC VEC hardware support AddIns\VEC

Installer Properties The following properties can be over-ridden in several ways.

When doing automatic deployment of client applications, it is recommended you pass Install Properties, using the highest-priority one available, to ensure your desired configuration is deployed correctly to all workstations.

Server URL

This defines the URL of the Winscribe Dictation Server.

Default value: http://servername/winscribe

NOTE: Because the default value is not valid, the installer will prompt for a proper value if no value was supplied by any way listed in the table below.

Ways to set this value, in order of precedence (highest to lowest):

Name/Location Set From Priority

SERVERURL Installer Property Highest

WSURL Installer Property

EDITA1 Installer Property

HKLM\Winscribe\General@WinScribeURL Registry

HKCU\Winscribe\General@WinScribeURL Registry Lowest

As an example from the table above, the SERVERURL property, if set from the command line, will set the URL regardless of what's in the registry.

Example msiexec SERVERURL=http://server1/winscribe WSURL=http://server2/winscribe /i "Winscribe Client.msi"

The server URL will be set to http://server1/winscribe, as SERVERURL takes precedence over WSURL.

Install Location

This configures where the application is installed to.

Default value: %Program Files%\Winscribe\<Product Name>

144


Overrides, in order of precedence (highest to lowest):


WSINSTALLDIR Installer Property Highest

INSTALLLOCATION Installer Property

HKLM\Software\Winscribe\<Product Name>@InstallLocation Registry

HKCU\Software\Winscribe\<Product Name>@InstallLocation Registry

APPLICATIONFOLDER Installer Property Lowest

Install Location troubleshooting

You cannot install two or more client applications to the same folder. If you try to do so, you will receive an error notification in the installer.

The error message will be similar to "<Product Name> is already installed at <Install Location>".

User Working Directory

This sets the location of the user working directory.

Default value: %ProgramData%\Winscribe\Users

Where %ProgramData% refers to the path of the All Users profile.


WSUSERDIR Installer Property Highest

HKLM\Software\WinScribe\General@UserWorkingDirectory Registry

HKCU\Software\WinScribe\General@UserWorkingDirectory Registry

USERWORKINGDIRECTORY Installer Property Lowest

Silent Install

This property enables a "silent install".

This property is generally passed when launching the installer from the Web Component installer pages.

Default value: Not set

Name/Location Set From

WSWEB Installer Property

Old behavior

Previously, the property reduced the number of dialogs in the installer.

New behavior

If specified in the client installers, this will simply disable the Options button in the installer that allows a user to configure the install properties.

If the Server URL has not been passed to the installer and cannot be found in the registry, then the installer will fail with the error:

145


"Silent install is not supported if the server url cannot be found".

If you wish to achieve a complete silent or non-interactive install, please consult the Silent Installation section.

Recording Audio Quality

You can set the audio quality for recording by setting this property.

Default value: medium

Available values: low, medium, high


WSAUDIOQUAL Installer Property Highest

HKLM\Software\WinScribe\General@VirtualChannelAudioQuality Registry

HKCU\Software\WinScribe\General@VirtualChannelAudioQuality Registry Lowest

Logging You can generate a log of the installation process by passing the /l argument and a path and filename to the log file you wish to produce.

The /l*v argument is recommended. The wildcard specifies all logging options except for verbose and extra debugging messages. Adding the v to the wildcard also includes the verbose logging.

Example

Create a log of the Winscribe Client installation, called "C:\Client.log":

msiexec /l*v C:\Client.log /i "Winscribe Client.msi"

Automatic Installer Logs

For cases where you are not manually running Windows Installer from the command line, you can set a registry setting to ensure Windows Installer creates a log whenever it runs.

Each time Windows Installer runs, it will create a log in the %TEMP% directory with a name in the format MSI<random>.log, where <random> is a random combination of letters and numbers.

1. Create a HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer registry key if it doesn't exist.

2. Create a Logging String value if it doesn't exist.

3. Set the Logging value to the logging levels you wish e.g. voicewarmup for all verbose logging values, except for extra debugging information.

More information is available at: How to enable Windows Installer logging at support.microsoft.com

Inspecting Verbose Windows Installer Logs

Windows Installer logs require a good understanding of Windows Installer to be interpreted fully, but helpful information can still be found for someone troubleshooting an installation.

Windows Installer logs are in plain text and can be read in any text editor.

146


Windows Installer Verbose Log Analyzer

This utility is available in the Windows SDK, called WiLogUtl.exe.

Documentation is available at http://msdn.microsoft.com/en-us/library/aa372811(v=vs.85).aspx

You can browse to select a Windows Installer log:

Clicking Analyze gives you additional information, and allows you to easily browse any errors found in the log file, with possible solutions.

The analyzer can also generate a colorized HTML version of the log that can be more easily read and browsed than the plain text log.

Section 3: Installing Winscribe

Setting Installation Parameters If required, you can set the installation parameters for Winscribe client applications using a command line argument. This prevents the user performing the installation from having to manually enter the parameters.

Note: Parameters are case sensitive.

Example

At the command prompt or in the Run box, type in the following command, replacing the file paths with those appropriate to your system:

msiexec /quiet /i "C:\Winscribe\Winscribe Client.msi" SERVERURL="http://webserver/Winscribe" INSTALLLOCATION="c:\Program Files\Winscribe" USERWORKINGDIRECTORY="c:\Winscribe\Users"

The breakdown of this command is as follows:

msiexec The Windows installer executable that executes msi files.

/quiet This performs a silent install without any user prompting

/i <msi name and path> Installs the msi file specified after the /i

SERVERURL Winscribe URL – replace with the path to your Winscribe URL

INSTALLLOCATION Install Directory – replace with the path to your installation directory

USERWORKINGDIRECTORY User Directory – replace with the path to your Winscribe user directory

Note: Winscribe Client has additional options that allow you to define which features and device support are installed.

Troubleshooting the Installer:

You can create a verbose log by passing the /l*v argument to msiexec:

msiexec /i "Winscribe Client.msi" /l*v C:\WinscribeClient.Install.log

147


Client

Admin & Web Components Properties

These properties can be set from the msiexec command-line, or passed to the msi using the Web Components installer.

Property Name Description Example

SERVERURL The WinScribe server URL http://servername/winscribe

INSTALLLOCATION The place where WinScribe will be installed

C:\WinScribe

USERWORKINGDIRECTORY Place for the user working directories C:\WinScribe\Users

Example

Example of setting these properties from the command line:

msiexec /i "WinScribe Client.msi" SERVERURL=http://devserver40/winscribe INSTALLLOCATION=C:\WinScribe USERWORKINGDIRECTORY=C:\WinScribe\Users

Specifying features to install on the command-line for unattended installs

To do a silent install, you can use the /quiet msiexec option, which will install silently. You can alternatively use /passive, which will also be an unattended install but will show a progress UI when installing.

You can specify which features of the product to install on the commandline:

msiexec /i "WinScribe Client.msi" ADDLOCAL=[Feature1,Feature2,Feature3] <additional options>

You can specify one or more features to install, separated by commas.

Currently available features:

Id Title Description Notes

ProductFeature WinScribe Client The WinScribe Client Base product (required)

VirtualChannelFeature Terminal Services and Citrix Server Support

Supports hardware devices and audio file import when installing onto a Windows Terminal Services or Citrix server.

DevicesFeature Hardware Devices Installs support for foot pedals from various manufacturers

Installs all device support. You can also specifically install certain devices by specifying the nested features below.

GrundigFeature Grundig Foot Pedals Supports Grundig foot pedals

Olympus Olympus Foot Pedals Supports Olympus foot pedals

Philips Philips SpeechMikes and Foot Pedals

Supports Philips foot pedals & SpeechMike devices

VEC Infinity / VEC / WinScribe Foot Pedal

Supports the WinScribe foot pedal made by Infinity/VEC

148


Developers: The list of features are in the Product.wxs file in the WinScribe.Client.Setup project, defined by <Feature> elements. They can be nested.

Examples

Silently install the base product, and virtual channel support, for the server in a Citrix or Terminal Services environment:

msiexec /i "WinScribe Client.msi" ADDLOCAL=ProductFeature,VirtualChannelFeature /quiet

Unattended install of the product, showing install progress UI, with support just for Philips devices:

msiexec /i "WinScribe Client.msi" ADDLOCAL=ProductFeature,PhilipsFeature /passive

Silently install the base product, with support for all hardware devices:

msiexec /i "WinScribe Client.msi" ADDLOCAL=ProductFeature,DevicesFeature /quiet

Silently install the base product, with no hardware support:

msiexec /i "WinScribe Client.msi" ADDLOCAL=ProductFeature /quiet

Author/Internet Author

WSINSTALLDIR:

The directory the application is installed to, for example, C:\Program Files\Winscribe

WSUSERDIR:

The location of the user working folder. This is set in HKLM. For example, C:\Winscribe\Users

WSURL:

The URL location of the web components server. This is set in HKLM (Note that if there a current value in HKCU that will remain unchanged and will take priority over the one in HKLM). For example, http://mywebserver/winscribe

WSAUDIOQUAL:

This sets the audio quality for recording. Valid options are: medium, low, high

Automatic Deployment of Scripts If scripts are placed in the Upgrades folder of the Winscribe Server, the scripts are automatically downloaded to the PCs of authors and typists when they log on. This feature allows any new authors or typists to inherit Options permissions in the same way they inherit hardware settings.

When a new author or typist logs on, their Options permissions will be created based on the last logged on author or typist. This is the same way that the hardware settings are set for new users. If they are the first user to log on to the PC, then the Winscribe default options will apply.

When an existing author or typist logs on, a "Logged On" event script can run that writes to the Options settings in the registry of the user. These Options registry settings are then loaded immediately and are applied to that user's session. The scripts override any current user's Options settings. No other registry setting changes will be applied.

Downloaded scripts will be applied immediately during the current user session and the "Logged On" event will be run again for each script that is downloaded. This could result in the "Logged On" event running several times for a user.

149


New Authors

For new Authors only, the scripts placed in the Upgrades folder can be named the following:

Script Name Description

AuthorScriptsFacility.xml Will apply to all new Authors in this Facility

AuthorScriptsDeptXX.xml XX is the Dept ID that this script will apply to, e.g. AuthorScriptsDept1.xml will apply to all new Department 1 Authors only and will override the AuthorScriptsFacility.xml script.

AuthorScriptsAuthorXX.xml XX is the Author Id that this script will apply to, e.g. AuthorScriptsAuthor1000.xml will apply only to Author 1000 and will override the AuthorScriptsDeptXX.xml script.

Current Authors

For current Authors only (which will overwrite any scripts currently using), the scripts placed in the Upgrades folder can be named the following:


AuthorScriptsOverwriteFacility.xml Will apply to all Authors in this Facility.

Note: Each facility has its own Upgrades folder. The script file must be added to the Upgrades folder for each facility you want it to apply to.

AuthorScriptsOverwriteDeptXX.xml XX is the Dept ID that this script will apply to, e.g. AuthorScriptsOverwriteDept1.xml will apply to all Department 1 Authors only and will override the AuthorScriptsOverwriteFacility.xml script.

AuthorScriptsOverwriteAuthorXX.xml XX is the Author Id that this script will apply to, e.g. AuthorScriptsOverwriteAuthor1000.xml will apply only to Author 1000 and will override the AuthorScriptsOverwriteDeptXX.xml script.

Typist Scripts

These same script names can be used for the Typist (change the Author part to Typist) as well.

Note: These scripts are applied such that the Author (or Typist) script overrides the department script and the department script overrides the facility script.

Example Scripts for the "Logged On" Event

The following example "Logged On" event scripts are used to set the Options permissions for authors or typists.

150


Example Author Script: const HKEY_LOCAL_MACHINE = &H80000002 const HKEY_CURRENT_USER = &H80000001 Sub main() strComputer = "." Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv") strKeyPath = "Software\Winscribe\Users\" & Right("000000" & objAuthor.UserId, 6) strValueName = "AskForDepartment" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "AskForJobtype" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "AutostartNewJob" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "ConfirmEndJobCommands" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "JobRecordsAutoRefresh" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "JobRecordsDownloadDays" strValue = "7" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "JobRecordsRefreshInterval" strValue = "15" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "ReuseKeyfield" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "WindowsAlwaysOnTop" strValue = "True" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue end sub

Example Typist Script: const HKEY_LOCAL_MACHINE = &H80000002 const HKEY_CURRENT_USER = &H80000001 Sub main() strComputer = "." Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv") strKeyPath = "Software\Winscribe\Users\" & Right("000000" & objTypist.UserId, 6) strValueName = "ConfirmEndJobCommands" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "SyncSRText" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "AutoRefresh" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue

151


oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "NewWorkNotification" strValue = "False" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue strValueName = "RefreshInterval" strValue = "60" oReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue oReg.SetStringValue HKEY_CURRENT_USER,strKeyPath,strValueName,strValue end sub

Author/Client Grid Layout

Administrators may push out grid-layout definition files that order the columns displayed in Winscribe Author and in Winscribe Client.

To make changes, the administrator:

1. Custom-creates a desired layout in Author or Client1, on his or her machine.

2. Looks in their profile folder, in the user working directory, for the file: GridLayout.xml

3. Copies this file to the Upgrades folder on the server, changing the filename to one in the following tables, depending on the application and the desired action.

4. When authors/typists next log on to the server, the xml file (if it is applicable to them) will be downloaded to their machine and their application grid layout updated.

Making changes to Client grid layouts:

New Typists

For new Typists only, the GridLayout.xml placed in the Upgrades folder can be named the following:


TypistGridLayoutFacility.xml Will be copied to the user's working directory as TypistGridLayout.xml and will apply to all Typists in this Facility.

TypistGridLayoutDeptXX.xml Will be copied to the user's working directory as TypistGridLayoutDeptXX.xml, where XX is the Dept ID that this grid layout will apply to, e.g. TypistGridLayoutDept1.xml will apply to all Department 1 Typists only and will override the TypistGridLayoutFacility.xml grid layout.

TypistGridLayoutTypistXX.xml Will be copied to the user's working directory as TypistGridLayoutTypistXX.xml where the XX is the Typist Id that this grid layout will apply to, e.g. TypistGridLayoutTypist1000.xml will apply only to Typist 1000 and will override the TypistGridLayoutDeptXX.xml grid layout.

Current Typists

For current Typists only (which will overwrite any grid layouts they are currently using), the grid layouts placed in the Upgrades folder can be named the following:


TypistGridLayoutOverwriteFacility.xml Will be copied to the user's working directory as TypistGridLayoutOverwrite.xml and will apply to all Typists in this Facility.

Note: Each facility has its own Upgrades folder. The grid layout file must be added to the Upgrades folder for each facility you want it to apply to.

152



TypistGridLayoutOverwriteDeptXX.xml Will be copied to the user's working directory as TypistGridLayoutOverwriteDeptXX.xml, where XX is the Dept ID that this grid layout will apply to, e.g. TypistGridLayoutOverwriteDept1.xml will apply to all Department 1 Typists only and will override the TypistGridLayoutOverwriteFacility.xml grid layout.

TypistGridLayoutOverwriteTypistXX.xml

Will be copied to the user's working directory as TypistGridLayoutOverwriteTypistXX.xml, where the XX is the Typist Id that this grid layout will apply to, e.g. TypistGridLayoutOverwriteTypist3000.xml will apply only to Typist 3000 and will override the TypistGridLayoutOverwriteDeptXX.xml grid layout.

Making changes to Author grid layouts:

New Authors

For new Authors only, the grid layouts placed in the Upgrades folder can be named the following:


AuthorGridLayoutFacility.xml Will apply to all new Authors in this Facility

AuthorGridLayoutDeptXX.xml XX is the Dept ID that this grid layout will apply to, e.g. AuthorGridLayoutDept1.xml will apply to all new Department 1 Authors only and will override the AuthorGridLayoutFacility.xml grid layout.

AuthorGridLayoutAuthorXX.xml XX is the Author Id that this grid layout will apply to, e.g. AuthorGridLayoutAuthor1000.xml will apply only to Author 1000 and will override the AuthorGridLayoutDeptXX.xml grid layout.

Current Authors

For current Authors only (which will overwrite any grid layouts they are currently using), the grid layouts placed in the Upgrades folder can be named the following:


AuthorGridLayoutOverwriteFacility.xml Will apply to all Authors in this Facility.

Note: Each facility has its own Upgrades folder. The grid layout file must be added to the Upgrades folder for each facility you want it to apply to.

AuthorGridLayoutOverwriteDeptXX.xml

XX is the Dept ID that this grid layout will apply to, e.g. AuthorGridLayoutOverwriteDept1.xml will apply to all Department 1 Authors only and will override the AuthorGridLayoutOverwriteFacility.xml grid layout.

AuthorGridLayoutOverwriteAuthorXX.xml

XX is the Author Id that this grid layout will apply to, e.g. AuthorGridLayoutOverwriteAuthor1000.xml will apply only to Author 1000 and will override the AuthorGridLayoutOverwriteDeptXX.xml grid layout.

153


Section 4: Installing Internet Importer (Standard Windows Application) The following section will guide you through the steps required to install the Internet Importer. It is important that these steps are followed exactly, and that you do them in the order presented here. Failure to do so may result in the installation failing, therefore requiring reinstallation of the software.

Minimum System Requirements

Winscribe Importer will operate satisfactorily on any PC that meets the minimum requirements for the operating system in use: Windows 2003 Server with Service Pack 2 (or higher), Windows XP with Service Pack 2 (or higher), Windows Vista with Service Pack 1 or higher (all versions except Home Basic), Windows 2008 Server, Windows Server 2008 R2, Windows Server 2012, and Windows 7, 8, 8.1.

If Dragon speech recognition is required, the PC must also meet the minimum requirements for that software.

1. Run the supplied Winscribe Importer.msi. This launches the Winscribe Importer Wizard.

Click Accept and Install to continue and install the default settings,

or click Options to custom configure the installation, as follows:

2. Select to install as Winscribe Importer Windows Application.


154


3. Accept the default Destination Folder, or click Change... to browse to an alternative folder.


5. When it has finished, the Installation Complete dialog will be displayed:

6. Click Finish to complete the setup process.

155


Configuring the Temp Folder when Importer is run as a Windows Application By default, the Importer temporary directory is C:\Windows\Temp. However, Administrators may specify a desired temp folder using the following registry key:

HKEY_CURRENT_USER / Software / WinScribe / Importer / TempDir

If this key is created, and its value set to a desired temp folder, the Importer will use that path instead of the default.

Section 5: Configuring Web Installation Winscribe Internet clients can be installed using Microsoft Internet Explorer, as detailed below. System Administrators can modify the client applications web installation in order to specify:

whether the installation process will prompt users to enter configuration settings.

a different URL for your Web Components.

whether Winscribe Internet Importer will install either as a service or as a Windows application.

To configure web installation:

1. Browse to the Web Components Includes folder: C:\Program Files\Winscribe\Web Components\Data Provider\Setup\includes

2. Open the WebSetup.config.js file with a text editor such as Notepad.

3. Edit the following options as required:

xxSilent: For each application you can choose whether users will have the option to enter configuration settings (such as the destination folder for the installation) when they install the client applications. Set the xxSilent argument to '0' to allow users to enter settings, or to '1' to have the installation process run without displaying any prompts to allow the users to enter settings.

xxURL: For the Winscribe Client, Winscribe Author, and Internet Author applications you can specify a different address for the Web Components Server if required. Leave the xxURL setting at 'Default' for the client application installation to point to the default Web Components Server, or enter the URL of the new server.

IAppType: You can specify whether the Internet Importer will install as a Windows application or a Windows Service by default. Set the IAppType setting to 'WinApp' to make the default setting to install as a Windows application, or 'WinService' to make the default setting to install as a Windows service.

156


If you have set the xxSilent variable to '0', users will have the choice of how to install Importer and the IAppType setting will merely select the default. If you have set the xxSilent variable to '1', users will not have the option to override this default setting.

Section 6: Installing Winscribe Author, Winscribe Client, Internet Author, or Importer via the Web Winscribe client applications can be installed using Microsoft Internet Explorer whether the user is connected to the LAN (locally) or connected remotely via the Internet. The following sections will guide you through the steps required to install Winscribe client applications from Internet Explorer. Make sure the PC you are installing Winscribe client applications on meets the minimum requirements (see page 140).

Note: System administrators can customize the web installation as detailed in Configuring Web Installation (see page 155).

1. Close all open programs.

2. Start Microsoft Internet Explorer.

3. Enter the URL that points to the location where Winscribe Web Components are installed followed by the word "Setup". For example:

If you are installing whilst connected to the LAN, enter the URL in the form:

http://servername/winscribe/setup/

If you are installing remotely via the Internet, (no LAN connection is present), enter the URL in the form:

157


http://www.websitename.com/winscribe/setup/

The installation options web page is displayed. Click the client application you would like to install: either Internet Author, Winscribe Author, Winscribe Client, or Internet Importer.

4. The Winscribe Author Setup dialog is displayed based on your previous choice.

5. Click Install to continue. The installation files are automatically downloaded to your computer. This

process may take several minutes to complete.

158


6. The InstallShield Wizard for the application you selected is displayed.

7. Click Next to continue.

8. Click Install to start the installation process. This process may take several minutes to complete.

The InstallShield Wizard Completed window is displayed when the installation is complete.

9. Click Finish to close this window.

The Winscribe application is now ready for use. Your system manager will provide a login Id and security code.

Note: If you disabled anti-virus software while doing the installation please re-enable it now.

Section 7: Customizing the Login Window The login window for the Winscribe Client, Winscribe Author, Internet Author, and Internet Importer applications can be customized as required. This is done by simply replacing the Winscribe standard image with one of your own design, as outlined below.

The image file must be called LoginGraphic.jpg and should be 341 x 121 pixels.

159


Customizing the Winscribe Client, Winscribe Author, or Internet Author Login Window

If you place a copy of your LoginGraphic.jpg in the Winscribe Server WinscribeShare\Upgrades directory after installing the Server, this file is uploaded automatically to the client applications when they log on online, and used the next time they connect.

Alternatively, you can place the image in the user working directory on the client PC after installation:

e.g. C:\Documents and Settings\All Users\Application Data\Winscribe\Users

Customizing the Internet Importer Login Window

For the Internet Importer, you will need to manually overwrite the Winscribe LoginGraphic.jpg (in C:\Program Files\Winscribe\Importer) with your graphic file after the Internet Importer is installed.

Section 8: Troubleshooting Client Applications This section is intended to assist technical staff with troubleshooting and resolving problems that may occur during installation and day-to-day operation of Winscribe Internet Client programs.

Install stops responding The install program stops responding while registering components.

Resolution Certain files (DLLs and OCXs) are in use by another program, preventing the Winscribe install program access to update them. Restart windows. After restarting, close any open programs including background utilities and then restart the installation.

Can't register components during installation

Resolution Certain files (DLLs and OCXs) need to be registered with Windows. On slow machines this can take some time. Let the install program finish (this should not exceed 30 minutes).

Winscribe Server has been shutdown for system maintenance When logging on the following error message is displayed: The Winscribe Server has been shutdown for system maintenance. You cannot logon at this time.

Resolution A System Manager has shutdown the Winscribe Server and the Winscribe Dictation Service has been stopped. You will need to wait until the System Manager restarts Winscribe before logging on. If you are the user that shutdown the System, you will still be able to logon

SQL Server not found When running a report the following message is received: "SQL Server not found".

Resolution Winscribe Managers wishing to run reports must be logged into the same Domain or Workgroup as the Winscribe SQL Server, or be logged into a Domain that has a Trust relationship with the Domain. Please contact your network administrator to correct this problem.

160


An error has occurred attempting to open the Winscribe database When logging on the following error message is displayed: An error has occurred attempting to open the Winscribe database.

Resolution The ServerName in the Winscribe Advanced Setup program on the Database properties sheet may be invalid. Check the ServerName entry and correct it if it is invalid. This error may also occur on some PC's that do not belong to the same Domain as the Winscribe Server. This problem can be corrected by changing the entry in Winscribe Client Setup Advanced Features SQL Server Options properties page file as follows:

Connection= TCP/IP

This instructs Winscribe to connect to the SQL Server using TCP/IP instead of the default, which is Named Pipes.

Your demonstration license has expired! When logging on the following error message is displayed: Your demonstration license has expired!

Resolution You have a Winscribe demonstration license which has expired. You will need to register the software in order to continue using it. Contact your supplier for assistance.

No Sound Card Detected! When logging on the following error message is displayed: No Sound Card Detected!

Resolution The soundcard is not installed correctly. The software that came with the soundcard needs to be installed and configured before it can be used. Obtain the install disks that came with the soundcard and follow the installation routine. If the soundcard still doesn't work, you may have a hardware conflict and you should consult the troubleshooting section of the soundcard manual.

Invalid User Id or security code Users receive the following error when logging in "Invalid User Id or security code":

Resolution The user's ID or security code is not recognized by the system. They may have made a typo in the login box or the login credentials they are entering are incorrect. Check the credentials and try again.

Error 502 Check your Winscribe URL

Internet user receives the following error message when logging in: "Internet request failed! Web server returned status: 502 Check your Winscribe URL is correct and that the Server is running."

Resolution This indicates that the Winscribe web server wasn't found on the web. The server name is immediately after the "http://" part of the URL and can sometimes be an IP address. Check the URL for spelling mistakes. This error may also be caused by the Winscribe web server being offline, so this should also be investigated (e.g. try logging in from another remote PC or use the PC's browser to browse to your Winscribe server's setup page).

Internet request failed. Web page was not found. Internet user receives the following error message when logging in: Internet request failed! Web page was not found. Check your Winscribe URL is correct.

161


Resolution This indicates that the Winscribe web server was found, but the Winscribe page wasn't found on the server. The Winscribe page is immediately after the "http://{servername}/" part of the URL. Check the URL being entered is correct and that it hasn't been misspelt.

Firewall preventing data traffic Data traffic submitted externally to and from Winscribe applications is blocked by the server's firewall.

Resolution: Investigate the server's firewall settings. Consider configuring the port to allow HTTP commands "PUT", "GET", and "POST".

Use caution. Be aware of any potential security issues changed HTTP settings may give rise to.

An author-reviewer can't find/access an existing job An author-reviewer can't find/access an existing job for editing or reviewing.

Resolution The job may be currently being reviewed, typed or authored by another author or the job may have been completed. The author-reviewer may also be searching for the wrong job or key number, or does not have the correct access level for the job.

If the job is currently being reviewed, typed or authored, the author-reviewer must wait until the user has finished working on the job. Check the author's access level. Check the author is allowed to review other authors work if the job is not their own.

Sound Card in use by another Application! When attempting to play or record a job, an error similar to the following occurs: Sound Card in use by another Application!

Resolution The soundcard is being used or hasn't been released by another application. The program using the soundcard needs to be found and closed. If there appears to be no other program using the soundcard, it is likely that the program crashed while being used and hasn't released the soundcard. You will need to restart Windows.

No sound when playing a job or prompt

No sound when playing a job or prompt.

Resolution The headphones/speakers are not connected correctly, the mixer needs configuring, or there is a more serious hardware problem. Check the following items:

1. Check that the headphones/speakers are plugged in to the correct soundcard socket. Note: Different soundcards have different socket locations.

2. Run the mixer program that is part of the soundcard software (look in the soundcard software group). The mixer controls the sound levels of devices plugged into the soundcard. Ensure the wave device is not muted. Increase the master volume and wave volume.

3. Plug in a pair of headphones/speakers that work on another PC.

4. Exchange the soundcard for one that works.

Nothing was recorded

After recording with the microphone nothing was recorded.

162


Resolution The microphone isn't connected correctly, the mixer needs configuring or there is a more serious hardware problem. Check the following items:

1. Play a job or prompt that you know has voice content and make sure it can be heard comfortably. (If not, use the steps described in the previous problem/solution).

2. Check that the microphone is plugged in to the correct soundcard socket.

Note: Different soundcards have different socket locations.

3. Run the mixer program that is part of the soundcard software (look in the soundcard software group). The mixer controls the sound levels of devices plugged into the soundcard. Ensure the microphone device is not muted. Increase the microphone volume, master volume or wave volume.

4. Plug in a microphone that works onto another PC.

5. Exchange the soundcard for one that works.

Sound volume is too low Sound volume is too low even when the Winscribe volume slide is at its maximum.

Resolution The master and/or wave volumes are too low on the mixer program. Start playing a job or prompt and run the mixer program. Adjust the master volume or wave volume to a comfortable level.

Typist's foot pedal doesn't work

Typist's foot pedal doesn't work or pedal operation is erratic.

Resolution The foot pedal is not plugged in correctly, has not been configured in the Winscribe application, another games port is present, the soundcard is not configured correctly, or the pedal is faulty. Start playing a job and follow these steps:

1. Make sure the pins of the pedal plug are straight and unbroken. Ensure that the games port connector is correctly inserted.

2. If a pedal has previously worked on this PC, go to step 4. Look for a second games port socket. If a second games port is present try using that socket. If neither socket works then disable the port that does not reside on the soundcard. This is usually achieved by changing a jumper setting on the I/O card, (consult the PC manual if in doubt).

3. If a pedal used to work on this PC, go to step 4. Make sure the game port works and doesn't conflict with other hardware. Games ports usually have their own I/O address and can double as a MIDI port. From the Control Panel or a DOS utility, look for an enabled address for the Games/MIDI port. Make sure MIDI functionally is enabled and works.

4. Swap the foot pedal for one that works on another PC.

5. Exchange the soundcard.

Playback starts at the wrong location

After a typist stops and restarts playback. The play starts at the wrong location.

Resolution The pause rewind setting for that typist is set too high.

Note: A value of zero will cause play to continue from exactly where it was stopped.

Job's Voice File not found! When trying to open/play a job, an error similar to the following occurs:

163


Job's Voice File not found!

Resolution A record of the job exists but the actual voice portion is missing. The voice portion is stored as a file, which may have been moved or deleted. If the job is old, the voice file may have been removed as part of the system archive/deletion schedule. Alternatively, the network location of the voice files may no longer be accessible by the PC. Follow these steps:

1. Ensure the network location is accessible by using the File Manager to view the Shared Directory set in Advanced Features option. From here check that a subdirectory called RECRDING exists.

2. If the job has been archived and deleted by the system then follow this procedure: From the management program go to Jobs|Restore and browse the archive directory (<shared directory>\ARCHIVE) for a file called <jobnumber>.VOX. Highlight the file and click OK. If the job can't be found in the archive directory, it has not been archived.

3. If the job has been deleted by the system but not archived, the only solution is to restore the job from a tape backup. The system manager should re-assess the deletion and archiving schedule to avoid this situation in the future.

Error attempting to create a new dictation! When attempting to record a new job the following error occurs: Error attempting to create a new dictation!

Resolution The network location of the voice files may no longer be accessible by the PC or the storage drive may be full. Follow these steps:

1. Make sure the network location is accessible by using the File Manager to view the Shared Directory on the Winscribe server. From here check that a subdirectory called RECRDING exists.

2. Check the available space on the storage drive.

Error No Voice Server Present In the Telephony Manager program, when using the Maintenance | Phones option, the following error occurs: ERROR NO VOICE SERVER PRESENT

Resolution The Telephony ServerName entry specified in the Winscribe Setup Advanced features program has not been found or there are too many managers viewing this option at the moment.

Archive/save VOX files

Does the Winscribe system backup voice recordings in the event of system failure?

Resolution Winscribe has an automatic backup process, to save completed and open jobs to an Archive folder (stored in a sub-directory of the Users folder) so that no loss of voice recordings occurs in the event of hardware or software failure. These backup files are deleted after a specified number of days (default = 3 days). There are two Registry settings that control this feature. They are: "ArchiveVoxFiles=True", and "ArchiveDays = 3". Either of these settings can be manually edited, but they should not be deleted as they are automatically recreated with the default settings when the user next logs on.

164


This chapter provides information on the various settings that effect the operation of Winscribe. Many of the settings involve making entries in, or modifications to, the Winscribe Server Settings program located in your Winscribe applications folder (Start | Program Files | Winscribe).

Winscribe Windows Services To operate successfully, the Winscribe system requires the following Windows Services to be running:

Winscribe Dictation

Winscribe Telephony Server (if Telephony support is installed)

Dialogic (if Telephony support is installed)

MSSQL Server

Internet Information Services (for all Winscribe Web-based applications)

These Services are set to start automatically when the system is powered up or rebooted. However, if you are not restarting the server you will need to start them manually.

Warning: Before stopping any services you should first have the System Manager run the Shutdown option, which will automatically log-off all users. This process may take a few minutes.

How to Stop/Start Winscribe Services

To stop or start the Winscribe Services, use the following steps:

1. Log on to the Winscribe server in the normal manner.

2. Click Start | Control Panel | Administrative Tools | Services.

3. Select the Winscribe Dialogic service, click Action and then click Stop/ Start. Microsoft Windows displays a timer while attempting to start or stop the Service. When one Service depends on other Services the Stopping dialog box is displayed to warn you that other services will also be stopped.

4. Click OK to accept.

5. Highlight the Dialogic service and click Stop. You will be prompted to confirm your decision.

6. Click Yes to confirm.

Configuring a Windows Service to Start Automatically If Windows were to lose its Service parameters you may need to change the Winscribe Services back to automatic startup. To change a Service to start automatically use the following steps:

1. Log on to the Winscribe server in the normal manner.

2. Click Start | Control Panel | Administrative Tools | Services.

3. Highlight the desired Service and click Properties.

4. Choose Automatic in the Startup Type panel and click OK. The Service is changed to start automatically when the server is restarted.

5. In the Services window click Start if you would like to start the Service immediately.

Chapter 4. Managing Servers

165


Configuring Winscribe Telephony Parameters The Winscribe Server Settings application enables you to set various telephony related parameters for the Winscribe telephone interface. This section describes the parameters that can be configured using the Winscribe Server Settings application.

Note: Prior to configuring any settings using the Winscribe Server Settings application, you should stop the Winscribe Dictation Service.

Timeouts

The Timeouts tab enables you to configure global timeout settings, as follows:

Inactivity timeout (secs): The amount of time that Winscribe will continue to prompt a caller for a response over the telephone interface before assuming the caller is no longer there and disconnecting them. The default setting is 300 seconds or 5 minutes.

Tone input timeout (secs): The amount of time Winscribe will wait for touch-tone input before timing-out. This value is used when requesting multi-digit tone fields such as user defined fields. The default value is 20 seconds.

Inter-digit timeout (secs): The amount of time Winscribe will wait between touch-tone digits on multi-digit tone fields before timing-out. The default value is 3 seconds.

Menu input timeout (secs): The amount of time Winscribe will wait for a menu option before timing-out. The default value is 20 seconds.

Recording timeout (secs): The maximum time in seconds that a dictation can be before the caller is requested to press the record function key to continue recording. The default value is 900 seconds (15 minutes).

Maximum silence recorded (secs): The maximum time in seconds of silence that will be recorded before the caller is requested to press the record function key to continue recording. The default value is 45 seconds.

Record Delay (milliseconds): On some installations with the Dictaphone Connexions Dictate Station (Cphone), the beep generated by the Cphone at the beginning of a recording is recorded into the dictation. This parameter allows a delay in milliseconds to be introduced before recording begins. If you experience this problem, set the record delay parameter to 60 (you may have to experiment with this figure to eliminate the beep entirely). The default for this parameter is zero.

166


Maximum archive life (days): The number of days that archived voice files and job data files will be stored. See the section on the Archive Directory. The default value is zero days. This setting means that these files must be deleted manually. You may enter the number of days you wish to keep these files and Winscribe will automatically delete files older than the specified number of days.

Review jobs order: The order that jobs are played back to Authors requesting a list of jobs to review. Valid values for this parameter are FIFO (newest first) or FIFO (oldest first). The default value is FIFO.

Ask for Review Key First: This parameter determines whether the Author will be asked for the job number or the key field first when attempting to review dictation. Valid values for this parameter are Yes (selected, ask for key field first) or No (deselected, ask for job number first). The default value is No.

Play Pause Tones: This parameter determines whether a brief pause tone will be played whilst telephone callers are in pause mode. Valid values for this parameter are Yes (selected) or No (not deselected). The default value is No.

Play Playback Paused Prompt: This parameter determines whether the "playback paused" prompt is played to Authors when they go into pause mode. Valid values for this parameter are Yes (selected) or No (deselected). The default value is No.

Authors Auto-start a New Job After Login: This parameter determines whether the author is asked to select the new job option (Press one, to dictate a new job) from the main menu or go straight into starting a new job. If this option is being used (selected) and the user wants to access any other main menu options then they must press the star key to cancel starting a new job. This is a global parameter and will affect all authors.

Authors Job Left Open on Hang-up: This parameter determines whether jobs are forwarded for typing automatically or are left open for future completion by the author. This will occur if the author hangs-up without completing job in the normal manner. This parameter is global and affects all telephone authors.

Note: Many of the parameters described above may be used in conjunction with specialist dictation devices such as the Philips LFH4060 and the Dictaphone Cphone. For example, the 'Play pause tones' setting is a useful audible aid to remind the author that he or she is in paused mode. Modify the default settings to suit site-specific requirements.

167


Hangup Tones The Hangup Tones tab is used to describe the cadence and frequency of the disconnect tone provided by the PBX or PSTN when a caller hangs up. This information allows Winscribe to recognize the disconnect and act appropriately. The entries in the Tones tab consist of one or more Disconnect entries which provide the details of the disconnect tone. Normally there would only be one Disconnect entry however in some cases it may be necessary to listen for more than one disconnect tone, so you can add additional entries if required.

Each Disconnect entry consists of the following information:

Freq1=<Frequency>:<Deviation> Where <frequency> is the frequency in Hz of the disconnect tone, and <Deviation> is the allowable deviation in Hz from this frequency.

Freq2=<Frequency>:<Deviation> This entry is the same as the freq1 entry, but is used when the disconnect tone is a dual frequency tone. If the disconnect tone is a single frequency, then this entry is not required.

On time=<Duration>:<Deviation> Where <Duration> is the time in milli-seconds that the disconnect tone is on for, and Deviation is the allowable deviation from this time (in milliseconds)

Off time=<Duration>:<Deviation> Where <Duration> is the time in milli-seconds that the disconnect tone is off for, and Deviation is the allowable deviation from this time (in milliseconds)

Count=<count> Where <count> represents the number of on/off cycles Winscribe must hear to determine that it is disconnect tone.

Minimum Loop Current off to be treated as a disconnect=<Duration> Where the minimum loop current duration is the time in 10 milli-second increments that the current is off. This setting is used in conjunction with Ring Generators that drop loop current to indicate hang-up has occurred.

Disconnect Tone Examples

Simple on/off tone (default): Freq1=400:100, on time=25:10, off time=25:10,count=2

Dual frequency on/off tone: Freq1=400:50, freq2=900:50, on time=25:10, off time=25:10,count=2

Continuous tone: Freq1=425:100, on time=250

168


Default Disconnect Tones

[Tones] Freq1=400:100, on time=25:10, off time=25:10,count=2

[Board] minlcoff=10

Note: It is possible that some older telephone systems do not provide disconnect signal. To overcome this Winscribe uses the * (Cancel) key, this is available when the caller is at the Main Menu options for both the author & typist telephone interfaces.

Author Keys The Author Telephone Key Mapping tab enables the functions performed by the Author telephone interface to be associated with specific keys on the telephone. In this way Winscribe is able to integrate with various analog dictation devices.

This tab defines the default behavior of each key when using the Telephone Author interface. Individual lines can however over-ride this default behavior with entries in the Author Line Keys tab (refer to the section on Author Line Keys, below).

Entries in the Author Telephone Key Mapping tab consist of a series of key=function pairs which describe which function will be associated with which tone (i.e. Help=0). The keys that are available for mapping are 0123456789*#ABCD. The default values for the Keys are as follows:

0=Help 6=Segment A=Pause

1=Record 7=Rewind B=Pause

2=Play 8=Pause C=Pause

3=Settings 9=Forward D=Pause

4=BookMark #=End

5=MarkSegment *=Cancel

The functions available to be mapped are described below.

Function Purpose

Help Callers may access context sensitive help at any time by pressing this function key.

169


Function Purpose

Record Places the system in record mode. The caller has the option to record, overwrite or record insert with this function.

Play Plays the recording

Settings Accesses the Edit Menu settings options. Refer to the Telephone Author User Guide for more information.

Book Mark Accesses the bookmark options. Refer to the Telephone Author User Guide for more information.

Mark Segment Insert the start and end points in a recording so that a portion of the recording may be deleted or pasted to another point in the recording.

Segment Pastes or deletes a previously marked segment into another position in the recording.

Rewind Rewinds the recording. For more information on the Rewind function refer to the Telephone Author User Guide.

Pause Places the system in pause mode awaiting a response from the user.

Forward Goes forward in the recording. For more information on the forward function refer to the Telephone Author User Guide.

End Accesses the End Job options. Refer to the Telephone Author User Guide for more information.

Cancel When this function key is pressed Winscribe cancels the current function and returns to the previous function.

Record Overwrite This function may be used as an alternative to or in conjunction with the Record function for devices that have keys to perform only this function. The caller will not be offered the record insert option that is available with the default Record function.

Record Insert This function may be used as an alternative to or in conjunction with the Record function for devices that have keys to perform only this function. The caller will not be offered the record overwrite option that is available with the default Record function.

Send For Typing

This function may be used as an alternative to or in conjunction with the End function for devices that have keys specific to this function. The default End function offers the caller additional options such as leave the job open, whereas the Send For Typing function places the job in 'Waiting for Typing Status' and no additional key presses are required.

Insert Bookmark

This function may be used as an alternative to or in conjunction with the BookMark function for devices that have keys specific to this function. If a device provides a specific function key for this purpose the key may be re-mapped to automatically insert a bookmark. Refer to the Telephone Author User Guide for more information on using bookmarks.

Rewind Play This function may be used as an alternative to or in conjunction with the Rewind function for devices that have keys specific to this function. If assigned to a key the user must press once to start rewind and a second time to start playing.

Forward Play As above

170


Author Line Keys When installing other manufacturers' analog dictation devices, you must specify which Dialogic ports are going to be used by these devices. This is because some devices provide additional function keys. The Author Line Keys tab is used to specify either a specific dictation device for Authors calling the port, or to override the default keypad mapping specified in the Author Keys tab for the port. If a Dialogic port does not have settings specified on the Author Line Keys tab, then the default key mapping as specified on the Author Keys tab will apply.

Overriding the Default Keypad Mapping

In order to over-ride the default keypad mapping defined in the Author Keys tab for a specific port, you need to change the settings on the Author Line Keys tab for the port. To override keypad mapping for port 1 (Line 1), you would change the Key Function for each key.

The entries in the Author Line Keys tab follow the same format as detailed in the Author Keys section, and consist of Key=Function pairs. You need only specify the keys that will differ from the standard keys. For example, if you wished to assign the 1 key (Line 1) to the play function and key 2 to the record function for line 1, the Author Line Keys settings would look like this:

[Line1]

1 Key Function=Play

2 Key Function=Record

Assigning a Pre-Programmed Device to a Line

Winscribe has been pre-programmed with three different manufacturers' dictation devices to simplify the task of re-mapping keys. These are the Dictaphone C-Phone, the Lanier Voicewrite and the Philips LFH40XX stations. To specify the type of device that will be used on a port:

1. Stop the Winscribe Dictation service.

2. Open the Winscribe Server Settings (click Start | Programs | Winscribe | Tools | Winscribe Server Settings). You will need to log in using a valid user id and password.

3. Select the Author Line Keys tab.

4. In the Type column click the Line number and select the device from the drop down list of supported devices.

5. Exit Winscribe Server Settings and restart the Winscribe Dictation service for your new settings to take effect.

171


Note: When you use a pre-programmed dictation device entry for a line, you cannot re-map keys for that port as well. If you do enter key mappings in the same 'Author Keys for Each Line' section as a Type= entry, the mappings will be ignored.

Important: When setting up systems where telephones and specialized dictation devices are being used together, you may need to create separate terminal hunt groups (a group of extensions with a pilot number) for each type of device. This is only necessary in cases where you are unable to provide the same functionality on the telephone as you would get from the specialized device.

Other Settings in the Author Line Keys Section

In addition to keypad mapping entries and type entries on the Author Line Keys tab, you can also specify some additional parameters that effect the operation of the line for an Author. These are:

Record Beep This entry determines if Winscribe will beep prior to beginning recording. Valid values for Record Beep are Yes (selected) or No (deselected). The default value is Record Beep=Yes

New Job Mode The New Job Mode setting determines what an author hears when they begin a new dictation job. Select the desired parameter for each line from the New Job Mode drop down list. Valid values for New Job Mode are:

Record: Winscribe goes directly into record mode at the start of a new job.

Pause: Winscribe goes into pause mode at the start of a new job.

Job Number Record: Winscribe plays the job number before going into record mode at the start of a new job.

Job Number Pause: Winscribe plays the job number before going into pause mode at the start of a new job. The default setting is New Job Mode=Record

Use Display The Use Display entry only applies when the LFH4060 Philips Dictation Device is specified. This entry determines if Winscribe should display prompts on the LFH4060's LCD display when requesting input. Valid values for Use Display are Yes, (selected) or No, deselected. The default value is Use Display=No.

172


Typist Keys The Typist Telephone Key Mapping tab enables the functions performed by the Typist telephone interface to be associated with specific keys on the telephone to integrate with various analog dictation devices. This tab defines the default behavior of each key when using the Telephone Typist. You can , however, override this default behavior for individual lines using the Typist Line Keys tab.

The Typist Keys tab consists of a series of key=function pairs which describe which function will be associated with which tone (i.e. 0=Help). The keys that are available for mapping are 0123456789*#ABCD. The default values for the Typist Keys are as follows:

0=Help 6= VolumeDown A=Pause

1= EndComplete 7=Rewind B=Pause

2=Play 8=Pause C=Pause

3=Settings 9=Forward D=Pause

4=BookMark #=End

5= VolumeUp *=Cancel

The functions available to be mapped are described below.

Function Purpose

Help Callers may access context sensitive help at any time by pressing this function key

Play Plays the recording

Bookmark Accesses the bookmark options

Rewind Rewinds the recording

Pause Places the system in pause mode awaiting a response from the user

Forward Goes forward in the recording

End Accesses the End Job options

Cancel When this function key is pressed Winscribe cancels the current function and returns to the previous function

Rewind Play This function may be used as an alternative to or in conjunction with the Rewind function for devices that have keys specific to this function

Forward Play As above with rewind & play

173


Function Purpose

Next Bookmark This may be used as an alternative to or in conjunction with the Bookmark function for devices that have keys specific to this function

Previous Bookmark As above

End Incomplete This may be used as an alternative to or in conjunction with the End function for devices that have keys specific to this function, or to provide a quick key for marking a job as incomplete.

End On Hold This may be used as an alternative to or in conjunction with the End function for devices that have keys specific to this function or to provide a quick key for marking a job as on hold.

End Complete This may be used as an alternative to or in conjunction with the End function for devices that have keys specific to this function or to provide a quick key for marking a job as complete

End Reject This may be used as an alternative to or in conjunction with the End function for devices that have keys specific to this function or to provide a quick key for rejecting a job, rejected jobs are placed back in the typist general queue.

Volume Up The default playback mode keypad has a key mapped to this function, you may re-map the key for use by another function

Volume Down As above

Speed Up This can be used to provide a fast key for increasing playback speed with a single key press when in play-back mode

Speed Down As above

Play Header This can be used to provide a fast key for accessing the job header information whilst in playback mode

Play Job Details This can be used to provide a fast key for accessing the job details information whilst in playback mode

Forward Fast This may be used as an alternative to or in conjunction with the Forward function for devices that have keys specific to this function

Rewind Fast As above

Forward To End As above

Rewind To Start As above

174


Typist Line Keys When installing other manufacturers' analog dictation devices you must specify which Dialogic ports are going to be used by these devices. This is because some devices provide additional function keys. The Typist Line Keys tab is used to specify either a specific dictation device for Typists calling the port, or to over-ride the default keypad mapping specified in the Typist Keys tab for the port. If a Dialogic port does not have settings specified in the Typist Line Keys tab then the default key mapping as specified in the Typist Keys tab will apply to the port.

Overriding the Default Keypad Mapping

In order to override the default keypad mapping defined in the Typist Keys tab for a specific port, you can edit the Typist Line Keys tab for the port (Line) you wish to change. For example, to override keypad mapping for Port 1, you would the edit the Typist Line Keys in Line 1.

The entries in the Typist Line Keys follow the same format as the Typist Keys, and consist of Key=Function pairs. You need only specify the keys that will differ from the standard keys. For example, if you wished to assign key 7 to the Forward function and key 9 to the Rewind function for Line 1, the 'Typist Keys for Each Line' section would look like this:

[Line1]

7 Key Function=Forward

9 Key Function=Rewind

Assigning a Pre-Programmed Device To a Line

Winscribe has been pre-programmed with three different manufacturers' dictation devices to simplify the task of re-mapping keys. These are the Dictaphone C-Phone, the Lanier Voicewrite and the Philips LFH40XX stations. To specify the type of device that will be used on a port:

1. Stop the Winscribe Dictation service.

2. Start the Winscribe Server Settings program by selecting Winscribe Server Settings from Winscribe Tools in your Start Menu. You will need to log in using a valid user id and password.

3. Select the Typist Line Keys tab.

4. In the Type column click the Line number and select the device from the drop down list of supported devices.

5. Exit Winscribe Server Settings and restart the Winscribe Dictation service for your new settings to take effect.

175


Note: When you use a pre-programmed dictation device entry for a line, you cannot re-map keys for that port as well. If you do enter key mappings in the same 'Author Keys for Each Line' section as a Type=entry, the mappings will be ignored.

Important: When setting up systems where telephones and specialized dictation devices are being used together, you may need to create separate terminal hunt groups (a group of extensions with a pilot number) for each type of device. This is only necessary in cases where you are unable to provide the same functionality on the telephone, as you would get from the specialized device.

Other Settings in the Typist Line Keys Section

In addition to specifying keypad mapping entries and type entries in the Typist Line Keys tab, you can also specify the 'Do Job Key' parameter that will affect the operation of the line for a typist.

Do Job Key From the main menu in the typist telephone interface the typist can start the highest priority job from either their personal or general queue by pressing one. Winscribe allows for an alternative key to be used for this function. The alternative key must be specified in the Typist Line Keys tab for each Dialogic port, and will only be required when configuring a device that uses this function. The Do Job Key must not be set to 2,3,4,*, or 0, since these keys are already assigned. For example, to assign the Do Job Key to the 9 key for line 2, the Typist Line Keys section would look like this:

[Line2]

Alternate Do Job Key=9

Winscribe Shared Directory The Shared Directory path is defined on the Paths tab in the Winscribe Server Settings application. This path must be in UNC format (\\server name\WinscribeShare)

Sub-directories in the Shared Directory The Winscribe shared directory includes a number of sub-directories that are created when Winscribe Server is installed.

176


Archive

The Archive directory is where the jobs voice file and data are copied to once the job has been completed and is ready for archiving. Jobs are not necessarily archived immediately after completion, but instead are archived after the number of Archive Job After Days parameter as specified for the job type. Consult the Web Manager Guide for more information on this parameter. When a job is archived, the jobs voice file is copied to the archive directory and a file is created in the archive directory, this contains a copy of the database information stored for that job. For example, if job 3500 is archived, the recording (00003500.VOX) is copied to the archive directory, and the file 00003500.DAT is also created in the archive directory.

Note: Once these two files have been backed up, they can be deleted from the archive directory. The original voice file and data are not necessarily deleted at the same time the job is archived. The original voice file will be deleted after the Delete Voice After days parameter and the data will be deleted after the Delete Job After days parameter as specified in the jobs job type. Refer to the Web Manager Guide for more information on archive & deletion parameters.

Facilities

Winscribe creates a folder structure under the facilities sub-directory each time you add a new facility. This folder structure mirrors what you see in the Server directory, for example, it will contain a Users folder. In this way each facility has its own separate location for storing prompts, dictation recording etc... When adding a new facility you are offered the option to create new prompt directories. If you chose this option you need to manually copy the prompt set you wish to use into the facilities prompts directory.

Important: Because a facility is created under the Server folder, which is shared as 'WinscribeShare', your facility will inherit the WinscribeShare permissions.

Import

No longer used.

Prprompt

The Prprompt directory is created when you install Winscribe with the Telephone interface. This folder contains the system prompts used to inform & instruct callers, for example, 'Enter user Id'. These are important to the operation of Winscribe and should not be changed or edited without first contacting Winscribe support. A directory structure is required for each language used with Winscribe.

Recrding

The Recrding directory contains the actual dictation recordings. The file name for each recording in this directory is the same as the job number and appears with a Dialogic ADPCM (vox) extension.

Important: Never manually delete files from the Recrdng directory under any circumstances. Doing so will have a serious negative effect on the operation of the Winscribe system. These files are automatically deleted as necessary by the Winscribe Archiving process.

177


Report

The Report directory contains the Crystal Reports, report definition files for all reports accessible by the System Manager.

Speak

The Speak prompt directory is created when you install Winscribe with the Telephone interface. This folder contains the prompts that are used to inform callers of dates & times or numbers. For example, informing the caller of the job number. A directory structure is required for each language used with Winscribe.

Training

The Training directory is the temporary location for speech recognition training files created during the initial training session for a telephone author. Once the files are created they are imported into the Speech Recognition server for acoustic adaptation.

Upgrades

The Upgrades directory is used by the Telephony Manager to automatically upgrade to later versions. When upgrading a Winscribe server, the setup will place any new files in this directory. The next time a user logs in to Telephony Manager, the new files are installed on their PC.

UserProm

The UserProm directory is the location into which any User Prompts created by the Winscribe Telephony Manager are stored. User prompts are used to describe job type & department names and are also used in Job Type User Defined fields to request the entry of job related information, for example a patient or customer number.

Users

The Users directory contains a file for each user currently logged onto Winscribe. Whilst this file exists the same user will be prevented from logging on with the same Id.

Warning: Under no circumstances should the files in this Shared directory be deleted. Contact technical support if you require assistance.

Winscribe Server

Primary Server:

The primary Winscribe server is responsible for the following:

1. Processing and storing dictation received via the telephone, internet, or LAN/WAN.

2. Enabling transcription of dictation via the telephone.

3. Summarizing information stored by the system, in the form of reports.

4. Purging old reporting information stored by the system.

5. Archiving jobs when they are due to be archived.

6. Deleting jobs when they are due to be deleted.

178


7. Detecting user defined alarm conditions and triggering alarms when these are encountered.

8. Monitoring activity on secondary servers, and triggering alarms when there is a failure on a secondary server.

9. Monitoring the status of Secondary Servers and reporting on any faults.

Secondary Server:

Winscribe supports up to 96 telephone ports in one server. To provide telephone port redundancy you may want to consider installing telephone ports in a second server (Winscribe will support up to 5 servers each with a maximum of 96 ports). The database and dictation files are stored on the primary server so any secondary server can be a lower specification. Contact Winscribe technical support to answer any questions.

Winscribe secondary server(s) are responsible for the following:

1. Processing dictations received via the telephone and relaying the data to the primary Winscribe server for storage.

2. Enabling transcription of dictation via the telephone.

3. Contacting the primary server and providing a 'heartbeat' to the primary server to indicate that operation is normal. If the secondary server goes down an alarm will be triggered on the primary server.

Shutting Down a Winscribe Server Winscribe servers may be shutdown using either of the methods described below:

1. Stop the Winscribe Dictation & Telephony Services as described in How to Stop/Start Winscribe Services.

2. Shut down Windows.

The Impact of Shutting Down Winscribe

When Winscribe is shutdown by either of the methods above, the following occurs:

1. If the server that is shutdown is a secondary server, then a low priority alarm is generated to indicate that the secondary server is now off line.

2. If the server that is shutdown is the primary server, then any secondary server(s) go into idle mode (i.e. they will no longer accept calls). In addition, all Winscribe clients that are currently using the system will be asked to log out, and any new clients attempting to log on will be informed that system maintenance is in progress and logins are not permitted.

Restarting Winscribe Services after a Shutdown

To restart a Winscribe server after a shutdown, select the Shutdown | Restart option from the toolbar if Windows is still running. Otherwise, if Windows is shutdown, then click the restart button on the screen, or press the reset button on the Winscribe server.

Checking if a Restart was Successful

Approximately 5 minutes after restarting the Winscribe server(s), the following event messages will be logged to the Application Event log of the primary server. If these messages are not seen, then the restart has not been successful. An alternative message should appear in the event log, to describe the problem.

Message 1: "WINSCRIBE1: Winscribe Primary Server Version x Started"

Message 2: "WINSCRIBE1: Secondary Server (WINSCRIBE2) Connected" (where applicable).

179


Configuring Winscribe Web Server Settings

When you install Winscribe Web Components the Winscribe Web Server Settings interface is installed in the Winscribe program group.

Shared Directory

The Web Components need to point to the location of the Winscribe Shared Directory, which is created during the Winscribe Server installation. If for some reason you change the Shared Directory name on the Winscribe Server you will need to modify this parameter.

Upload Directory

During installation of the Web Components a sub-directory called FileUpload is created under the directory that you installed the Web Components into. If for some reason you change where this directory is located you will need to modify this parameter also.

SQL Server Settings

The Winscribe Web Components need to know the name of the machine that contains the SQL database that is installed with Winscribe Server. If for some reason you change the name of the machine you will need to modify this parameter also.

To configure Winscribe Web Server Settings:

1. On the machine that you installed the Winscribe Web Components click Start | Programs | Winscribe | Tools | Web Server Settings. A login window is displayed.

2. Enter the default Winscribe System Manager login id and password and click OK. The Winscribe

Web Server Settings window is displayed.

3. To change the Shared Directory or Upload directory parameters, click the Browse button to open

the Browse for Folder Dialog.

180


4. To change the SQL Server options click the Database tab, and adjust the parameters as required then click OK. If you are using an instanced database, specify the full instance name in the Database Server path, for example: (local)\SQLExpress.

Windows Event Log

When Winscribe encounters a serious error or considers that the System Manager should be informed of a problem, it does two things:

1. Sets an alarm (refer to the Winscribe Web Manager User Guide for details on alarms).

2. Logs an event into the event log of the current machine. Some problems that occur may not allow an alarm to be triggered, and it is for this reason that all errors are also logged into the Windows Event Log. If there are problems with the Winscribe server(s), then the Event Log is the best source of information to the cause of the problem.

Note: Each server has an event log that needs to be checked. You will need to go to each server and check the log for clues to a problem. Alternatively, you can use the select computer option from the events program to access the event logs from any Windows machine that has access to the Winscribe server(s).

To check the event log click Start | Control Panel | Administrative Tools | Event Viewer. Choose the Application menu item. All of the events in the log will be displayed. Look for events that show the source as Winscribe, and double click that item to view the event details.

181


Troubleshooting Servers This section provides tips and tricks on identifying and correcting problems with your Winscribe Server software.

If you encounter problems during or after installation of the Winscribe Server, consult the following notes before contacting technical support.

Winscribe Services do not appear in the Services window During checking for correct operation, you notice the Winscribe Services do not appear in the Services window.

Resolution

1. For Systems with Dialogic Cards:

a. Check and see if the Dialogic Service shows in the Services window. If it does, then the problem is likely to be that the User Name or password you provided during installation was invalid. You can manually register the Winscribe services once you have the correct user details and have checked that the user has 'logon as a service' rights. To manually register the services, open a command window (MSDOS Window) and type:

Wsserver_/Register_1_\<UserName>_<Password>

Notes

Please replace underscores with a space.

The user name and password you use must have local or Domain administrator rights.

If the user is a domain account, remember to put the Domain name in front of the user name (i.e. wsdialog /Register 1 \Domain\UserName Password).

b. If the Dialogic Service does not exist in the Services window, then the Dialogic drivers did not install correctly, which caused the Winscribe services registration to fail. Install the Dialogic services manually by browsing to the Server\Dialogic subdirectory on the DVD and clicking on setup. Once the Dialogic drivers have successfully installed, run the DCM to configure the Dialogic cards as explained in the section on Upgrading a Server to Support Telephone Dictation (page ). Next, register the Winscribe Services by following the instructions above.

2. For Systems without Dialogic Cards:

The problem is likely to be that the User Name or password you provided the Setup program was invalid. You can manually register the Winscribe service once you have the correct user details and have checked that the user has 'logon as a service' rights. To manually register the services, open a command window (MSDOS Window) and type:

Wsserver_/Register_0_\<UserName>_<Password>

Notes:

Please replace underscores with a space.

The user name and password you use must have local or Domain administrator rights.

If the user is a domain account, remember to put the Domain name in front of the user name (i.e. wsdialog /Register 0 \Domain\UserName Password).

Dialogic Driver installation failed During installation the Dialogic driver installation failed.

182


Resolution

You will need to manually install the Dialogic Drivers. Follow the Resolution instructions for the problem Winscribe Services do not appear in the Services Window (see page 181).

Winscribe does not answer calls

Winscribe does not answer calls.

Resolution

1. Ensure that the Winscribe server is operational.

2. Shutdown and restart both the primary Winscribe server and any secondary Winscribe server(s).

3. Check the Event Log for details of the problem that has occurred and report any errors with as much information as possible to technical support.

Winscribe Server Shutdown for maintenance Typists and managers receive a message saying, "The Winscribe server has been shutdown for system maintenance. You cannot logon at this time" or authors calling the system hear a message saying that the system has been shutdown for maintenance.

Resolution

Check with the System Manager to see if work is currently being done on the primary Winscribe server. Check that the primary server is running, restart if it is not, then check that any secondary server(s) are running and restart if is not running. Check the Event Log for details of the problem that has occurred and report any errors to technical support.

Telephone port not disconnecting When the caller hangs up the telephone port does not disconnect immediately (within 3 seconds).

Resolution

This means that the default entry present in the Winscribe Server Settings Hang-up tones section is incorrect. Refer to the Winscribe Web Manager Guide for further information.

183

Chapter 5. Upgrading to Winscribe Version 4.2

You can upgrade to Winscribe version 4.2 by following the instructions provided below.

Note: If upgrading from version 2.5, you must first upgrade from 2.5 to 3.0 (see page 191) before performing these steps.

Prerequisites To upgrade to Version 4.2, you must have Winscribe Software Assurance or your reseller will need to place an order with Winscribe for the required number of licenses.

License Files Prior to upgrading a Winscribe system to v4.2 you need to request and obtain license files by contacting Winscribe Technical Support. An upgraded system will not function until the license files are in place. The information you need to provide depends on your current version:

Requesting upgrade licenses for an existing v3.8 or above system:

1. Load the License Server User Interface and retrieve the Installation ID.

2. Email Winscribe Technical Support with your Installation ID and your site name and request v4.2 upgrade licenses.

Requesting upgrade licenses for an existing v3.7 system or earlier:

1. Load the Web Manager or LAN Manager and retrieve the System Code.

2. Install the v4.2 License Server.

3. Load the License Server User Interface and retrieve the Installation ID.

4. Email Winscribe Technical Support with your System Code, Installation ID and site name and request v4.2 upgrade licenses.

Once you have received the upgrade licenses you can proceed with the system upgrade as described in the following sections.

Upgrade Summary for Winscribe Version 4.2 The following table gives a summary of the steps required to upgrade to Winscribe 4.2.

Step

1 Upgrade the License Server (see page 184)

2 Remove LAN Manager (see page 185)

3 Upgrade the Dictation Server (see page 186)

4 Install Telephony Manager (see page 186)

5 Upgrade the Web Components (see page 187)

6 Upgrade the Client Applications (see page 187)

7 Remove the discontinued client applications (see page 188)


184


Step 1 Upgrade the License Server Install the 4.2 License Server:

1. Run the supplied Winscribe License Server.msi. This launches the Winscribe License Server Setup Wizard:

Click Accept and Install to continue.

Or, click Options if you wish to configure the destination folder for the installation.

2. Click Next to begin the License Server configuration:

3. Enter the administrator login details and click Next to continue.

185


4. Click Save to update the configuration.

5. The configuration will now be saved, click Finish when completed.


Step 2 Remove LAN Manager LAN Manager has been discontinued in Winscribe 4.0 and should be removed when upgrading. Web Manager is now the main application for configuring the Winscribe product, and the new Telephony Manager is used for configuring the Telephony part of the Winscribe environment.

1. Click Start | Control Panel | Add or Remove Programs.

186


2. Locate and select Winscribe LAN Manager in the list of currently installed programs and click Remove.

Step 3 Upgrade the Dictation Server To upgrading to Winscribe v4.2, you must run the Winscribe v4.2 Dictation Server installer. The installer detects that a previous version of Winscribe is already installed and upgrades the executable files, supporting libraries, and the Winscribe Database.

To upgrade the Winscribe Dictation Server:


2. Select Dictation Server to launch the Winscribe Dictation Server Setup Wizard.

3. When prompted, enter the URL of the Winscribe License server: e.g. http://localhost/licenseserver.

4. Click Install to complete the upgrade process.

Step 4 Install Telephony Manager 1. Insert the Winscribe Distribution DVD into the DVD drive on the Winscribe Server. If the PC is

configured to autorun, the Options Menu will be displayed. If not, browse to the DVD and double-click the start.html file in the root directory.

2. Click Telephony Manager to launch the Telephony Manager Installation Wizard.

Click View to read the Terms and Conditions.

Click Accept and Install to continue the installation (click Cancel to terminate the installation).

3. The installation will continue and the Telephony Manager will be installed.

187


4. The "Completed" window will display when the setup is concluded:

Click Finish to complete the installation process.

Step 5 Upgrade the Web Components To upgrade to Winscribe v4.2, you must run the Winscribe v4.2 Web Components installer. The installer detects that a previous version of Winscribe is already installed and upgrades the executable files.

To upgrade the Web Components:


2. Select Web Components to launch the Winscribe Web Components Wizard.

3. Follow the on-screen directions to complete the upgrade.

Step 6 Upgrade the Client Applications When upgrading the Winscribe server components, new versions of the client applications are copied onto the server. Each time a user logs on, Winscribe checks the version on their PC against the version installed on the Winscribe server. If a later version is found, he or she is offered the option to upgrade. This enables a site to easily stay up-to-date, and is a task that can be performed remotely if necessary.

Note: If you have more than one internet client application (i.e. Author and Typist) installed on a single computer you must upgrade all of them to Version 4.2 at the same time.

To upgrade the client applications:

1. Start the client application (Winscribe Author, Internet Author, Internet Typist or Winscribe Client)

2. When prompted to upgrade, select Yes.

Note: Winscribe Client is a new application introduced in version 4.0 that replaces the Internet Typist. Starting Internet Typist and choosing to upgrade, installs the Winscribe Client and automatically removes Internet Typist.

188


Disabling the Upgrade Prompt In certain circumstances, an administrator may choose to disable the auto-prompting for newer versions. This can be achieved by deleting the relevant MSI file from its folder.

Winscribe Author

C:\Program Files (x86)\Winscribe\Web Components\Data Provider\Setup\Author2\

Winscribe Internet Author

C:\Program Files (x86)\Winscribe\Web Components\Data Provider\Setup\Author\

Winscribe Client

C:\Program Files (x86)\Winscribe\Web Components\Data Provider\Setup\Typist\

Note: To keep auto-prompting disabled, this action will need to occur after every upgrade.

Step 7 Remove Discontinued Client Applications Winscribe Client now includes the functionality previously provided by the Typist Job Manager and Notification Service (wsNotify) applications. These two applications are no longer supported and should be removed.

1. Click Start | Control Panel | Add or Remove Programs.

2. Locate and select Winscribe Typist Job Manager in the list of currently installed programs and click Remove.

3. Locate and select Winscribe Notification Service in the list of currently installed programs and click Remove.

Upgrading a system with Server-side Speech Recognition 1. Stop the SR Submitter service.

2. Wait until there are no outstanding SR tasks. This can be verified via the SR Controller Web-based user interface by checking the status of the tasks on the controller diagnostics page.

3. Upgrade the License Server (see page 184).

4. Run the 4.2 Speech Recognition installer and select desired features.

5. Upgrade the Winscribe Server (see page 186).

6. Upgrade the Web Components (see page 187).

7. Upgrade the client applications (see page 187).

Upgrading a system with Exporter licenses 1. Upgrade the License Server (see page 184).

2. Upgrade the Winscribe Server (see page 186).

3. Run the 4.2 Exporter Installer.

189


Upgrading a system with Mobile Recorder licenses 1. Upgrade the License Server (see page 184).

2. Upgrade the Winscribe Mobile Services:

Uninstall the Winscribe Mobile Services using Add / Remove Programs from the Control Panel.

Run the Winscribe Mobile Services installers.

3. Upgrade Winscribe on the device.

Upgrading the Web Manager Author Job Upload feature Sites that are using the Web Manager Author Job Upload feature must update the SQL trigger as well as the Importer script.

1. Upgrade the Winscribe Server:

Run the Winscribe Server installer either directly or via the Distribution DVD product selection user interface.

Drop the JOBUPDATE_FROM_NOTES trigger from the JOB table.

Run the UploadTrigger.sql script found on the Distribution DVD found under Winscribe Applications\Author Job Upload.

2. Upgrade the Internet Importer:

Uninstall the Importer using Add / Remove Programs from the Control Panel.

Run the Importer installer either directly or via the Distribution DVD product selection user interface.

Replace the Importer Job Upload script with the one found on the Distribution DVD found under Winscribe Applications\Author Job Upload.

Upgrading a Server to Support Telephone Dictation This section is designed to guide you through upgrading an existing Winscribe system to enable telephone dictation. It assumes you have read the previous chapters and have a good working knowledge of Winscribe Server operations. If you previously installed Winscribe and would now like to add telephone dictation to the server you can do so by following the steps outlined below.

1. Purchase the required number of telephone port licenses and Dialogic hardware from Winscribe Inc.

2. Set the Winscribe Dictation service to Manual start, and shutdown the Winscribe Server.

3. Install the Dialogic board (s) using the instruction card that accompanies the board.

4. Restart the server and install the Dialogic drivers. For your convenience Dialogic 6.0 drivers are included on the Winscribe Distribution DVD.

190


5. Run the Configuration Manager – DCM.

The Dialogic Configuration Manager should automatically detect the boards you installed into the server, and configure them for you. Check that the DCM displays the boards you installed. If not, you will have to add the boards manually. On the Action menu click the Add Device menu item and add the appropriate boards. Depending on the board type you may need to enter values for IRQ and memory address (ISA boards) that you determined when installing the cards. Use the DCM Help menu option for assistance in adding boards.

6. Set the appropriate Country parameters for each card by double-clicking on each card shown in the DCM, selecting the Country tab and choosing your country from the drop down list.

7. Set the Driver start-up mode to Automatic as follows:

On the Settings menu, select System/Device Autostart, then select Start System.

This will allow the Dialogic drivers to start automatically when the computer is restarted.

8. Manually start the system as follows: On the System menu, select Start System.

9. Exit the Dialogic Configuration Manager and restart the PC if Setup requires you to.

10. Open the Services window and check the Intel® Dialogic product System Service is started.

11. Uninstall Winscribe Dictation Server.

12. Re-install Winscribe Dictation Server, choosing Primary Server or Secondary Server with Telephony.

13. Choose Standard Telephony or Advanced Telephony, as desired.

14. Start Telephony Manager, enter your User ID and Password, and choose the Advanced button. Verify that the Telephony Server field contains the name of the Winscribe telephony server and enter it if needed.

191


Upgrading a Server from 2.5 to 3.0 This section covers upgrading an existing Winscribe installation from version 2.5 (any build) to version 3.0. You cannot upgrade directly from version 2.5 to version 4.2. You must first run the upgrade to version 3.0, and then run the 4.1 upgrade procedure.

Note: If you are running an earlier version of the Winscribe software, such as version 2.0, you must first upgrade from version 2.0 to version 2.5. Once that upgrade is complete, you can then upgrade from version 2.5 to version 3.0 following the instructions in this section, then upgrade to version 4.2.

Warning:

1. Before upgrading the Server to version 3.0, you must change the working directory, Speak and Prompt paths to UNC pathnames. For the Winscribe facility, you must manually edit the wsserver.ini file. For all other facilities, use the Winscribe Server settings or Web Manager programs.

2. We recommend that you disable any anti-virus software currently running while completing the installation.

Important Notes:

If using Analog Dialogic cards:

Winscribe systems that are using Analog Dialogic cards, and are upgrading from a version prior to Winscribe 3.3.2, will need to first uninstall the existing dialogic drivers and reinstall the dialogic drivers with the globalcall option selected (Specify a "Custom" Install). You can either re-install the original Dialogic Drivers if using Release 6.0 or higher, or install the Dialogic Drivers required for your type of card. Note that you should refer to the Dialogic website or the documentation that came with your Dialogic card to determine which version of the Dialogic Driver to use with your card. The driver must be at least Release 6.0 or higher to work with Winscribe.

If using Digital Dialogic cards:

Winscribe systems that are using ISDN Dialogic cards and are upgrading from a version prior to Winscribe 3.3.2, will need to reinstall the dialogic drivers with the globalcall option selected (Specify a "Custom" Install) and with the ISDN option and ISDN driver(s) selected. You can either re-install the original Dialogic Drivers if using Release 6.0 or higher, or install the Dialogic Drivers required for your type of card. Note that you should refer to the Dialogic website or the documentation that came with your Dialogic card to determine which version of the Dialogic Driver to use with your card. The driver must be at least Release 6.0 or higher to work with Winscribe.

Upgrade Steps To upgrade a Winscribe Server from Version 2.5 to Version 3.0, complete the following steps:

1. Check that the PC you are installing on meets the minimum requirements.

2. Logon to Winscribe as a System Manager and choose the Shutdown option from the Maintenance Control Center. Ensure that all users have logged off before continuing.

3. Stop the Winscribe Services.

4. Backup your Winscribe Server and Database Server (if it is a different server). Ensure you backup WSServer.exe and WSDialog.exe in the c:\WinNT\System32 directory and Winscribe.mdf and Winscribe.ldf in the MSSQL7\Data directory. These files will be required in order to go back to the previous version if you have problems during the upgrade.

192


5. Browse to the 'Upgrades\Upgrade25to30' subdirectory on the Winscribe Distribution DVD and double-click on Setup.exe to install version 3.0. The Welcome dialog will be displayed.

6. To start the upgrade process, click on the Next button.

7. Once the upgrade has completed, the Upgrade Complete Dialog will be displayed.

8. In order to complete the upgrade, the Winscribe Server must be restarted. To have Setup restart the

Server for you, make sure the "Yes, I want to restart my computer now" option is selected and click the Finish button. If you wish to restart the Server later, choose the "No, I will restart my computer later" option and click the Finish button. After restarting the Server following the upgrade, refer to the instructions in the section on Post Installation Steps & Licensing (page ) to Register the Winscribe Server and to confirm proper operation of the system.

9. The upgrade is now complete. You can now complete your upgrade to the latest version of Winscribe by running the Upgrading to Winscribe Version 4.2 procedure.

Note: The upgrade process will not overwrite any prompts on your system, so all custom prompt changes you have made will still exist.

Troubleshooting

Updating the URL If the source of the original Winscribe Web Components has been changed to a new server, or the server name has changed from which the upgrade is now being performed and you are upgrading the Author or Typist applications from the web based setup, an error will be displayed on login (Can Not Locate Server).

This only occurs if the URL of the Winscribe server, prior to upgrade, differs from the location of the web based upgrade.

Note: This problem does not affect users upgrading using the upgrade prompt they get when they login to their client application after a server upgrade has been performed. It only affects users who manually browse to a Web Components web page to perform an upgrade.

193


Installing a Client Application onto a Clean System

If you are installing a client application (Winscribe Author, Winscribe Client, Internet Author) from the web onto a clean system, then the URL is written to HKLM\Software\General.

The first time the client application is launched, the URL is copied from HKLM\Software\Winscribe\General to HKCU\Software\Winscribe\General.

For each subsequent user that logs into the Windows OS on this machine and runs one of these Winscribe clients the procedure is repeated.

Upgrading a Client Application

If you are upgrading a client application, the installer will retain whatever URL values are already stored in the registry.

If you are upgrading from a previous version and you manually browse to a new Web Components location in order to upgrade to Version 4.2, the previous URL that was already present will be retained. The new server will not be located and the user will receive an error message on login when the application attempts to connect.

To fix this problem, login to the Winscribe application offline and manually change the URL (on the Server tab in the Options window). This fix will only apply to that particular user login. If multiple Winscribe users login in on the same machine, they would all need to make this change.

Alternatively, manually write the new URL to the HKCU\Software\Winscribe\General, and this would affect all Winscribe users who are sharing the same windows account (provided they haven't manually changed the URL in the application at any stage).

If there are multiple users, sharing multiple windows accounts and Winscribe accounts, then you will need to change the URL in the application on an individual basis.

Manually Changing the URL

If you manually change the URL within the application (on the Server tab in the Options window), then the new URL is written to HKCU\Software\Winscribe\Users\XXXX and also, if permissions allow, to HKLM\Software\Winscribe\Users\XXXX (XXXX is the user login id). If a URL exists in the Users directory, that URL will be used to locate the server instead of the URL in the General directory.

Summary of URL Updates

On first time install The URL is written to HKLM\Software\Winscribe\General (this never changes)

On first time launching a client application

The URL values are copied from HKLM\Software\Winscribe\General to HKCU\Software\Winscribe\General (these values now don't change)

On changing the URL in a client application

The URL is written to HKCU\Software\Winscribe\Users\XXXX and also to HKLM\Software\Winscribe\Users\XXXX (where XXXX is the users login id)

On creating a new Winscribe user

The URL is read from HKCU\Software\Winscribe\General (unless the user manually changes the URL in the application)

Upgrading Client app. from either Web or MSI

Values in registry are retained. Nothing is changed.

194


The following section will guide you through the steps required to remove Winscribe Server from a PC. You should only follow this procedure if you have encountered problems while installing a new Winscribe system and you would like to reinstall it, or if you will no longer be using Winscribe and wish to remove it from your system.

Warning: The procedure below is only intended for use when problems are encountered during a new install of Winscribe Server. If you are upgrading an existing Winscribe server refer to the earlier chapters in this guide for details.

Winscribe Server Uninstall Procedure To uninstall Winscribe Server follow the steps as described. You must be logged on to the server with Administrative rights.

1. Close all open applications.

2. Shutdown Winscribe using the Telephony Manager Maintenance Shutdown option (this step is only required if you have users connected to the server).

3. Stop the Winscribe Dictation Service, and the Winscribe Telephony &. Dialogic Services if you installed the telephone interface. To do this click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools and double-click Services. Select the Service(s) you wish to stop, right click and choose Stop.

4. Unload the Winscribe Web Components from IIS: Click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools and double-click Internet Services Manager. Expand Internet Services Manager to view the Default Web Site item. Expand the Default Web Site item and right click on the Winscribe item. Select properties and then choose Unload.

5. From Control Panel... Add/Remove Programs, uninstall Winscribe in the sequence below. To uninstall the Dialogic drivers go to the Dialogic program folder and choose the Uninstall option.

Internet Author, Winscribe Author, Winscribe Client

Winscribe Tools such as Upgrade Utilities and Speech Recognition Submitter

Winscribe Web Components Com+

Winscribe Web Components

Winscribe Server

Dialogic Programs (if these are not being used elsewhere)

Notes:

When uninstalling Winscribe applications, you will be prompted when a shared component is detected to either delete it or leave it on the system. Although it is usually safe to reply "Yes" or "Yes to All", this can sometimes result in unpredictable errors. As a rule of thumb, reply "Yes" to anything that starts with the characters "WS" and "No" to all others. You may just wish to reply "No to All" to avoid being presented with numerous "delete requests".

You may also be presented with a "Read Only File Detected" message. To be safe, reply "No".

If a component was deleted during an uninstall of an application, you may be notified of a "Self Registration Error" when uninstalling another application that also used that component. Reply "OK'

6. Reboot the Winscribe Server.

Chapter 6. Uninstalling Winscribe

195

Appendix 1. Programming Requirements for PBX's

Programming Requirements for PBX's With DID (Direct Inwards Dialing) Analog extensions are required to connect to the Dialogic ports on the Winscribe server. An additional analog extension is required for the remote support modem. To prepare the extensions when your PBX uses DID numbers:

Create a terminal hunt group with one analog extension port per Dialogic port, terminated with RJ11's. The modem port should NOT be in the hunt group.

Route an easy to remember DID number to ring directly to the hunt group. Authors and Typists will use this number for access to the Winscribe server from outside your office.

Program the remote support modem extension with data protection. Route a DID number to ring directly to this extension.

DTMF sending should be enabled from system and analog extensions to all members of the hunt group.

Determine the PBX disconnect signal. This is required so that Winscribe can disconnect the telephone port when a caller hangs up. The standard signal used by most PBX's is: frequency 400 hertz, cadence 250 ms ON 250 ms OFF, however you do get variations and in some cases there is no signal at all. When no signal is present it has not been enabled on the PBX.

Programming Requirements For PBX's Without DID Analog extensions are required to connect to the Dialogic ports on the Winscribe server. One additional analog extension is required for the remote support modem. To prepare the extensions complete the following steps:

Create a terminal hunt group with the analog extension ports that are terminated with RJ11's. The modem port should NOT be in the hunt group.

In conjunction with the customer's telephone equipment suppliers, determine the most appropriate method for providing external access to the Winscribe telephone interface. DISA (Direct Inward System Access) or automated attendants are appropriate methods.

Warning: Allowing DISA on a system with CO (Central Office) line access can be dangerous, since anybody can call into your system and then dial out again.

Program the remote support modem extension with data protection and organize to be able to ring directly to this extension. DISA or an automated attendant are appropriate methods.

DTMF sending should be enabled from system and analog extensions to all members of the hunt group.

Determine Disconnect Frequency Determine the PBX disconnect signal. This is required so that Winscribe can disconnect the telephone port when a caller hangs up. The standard parameters used by most PBX's are:

frequency - 400 hertz

cadence - 250 ms ON 250 ms OFF

Appendix 1. Programming Requirements for PBX's

196


however you do get variations and in some cases there is no signal at all. When no signal is present it has not been enabled for the extension you're ringing from.

If you are unable to obtain the disconnect frequency for the PBX a good method to overcome this problem is to use a program that can analyze it. A product that we have found easy to use is AUDITION, previously packaged as COOLEDIT. This program can be purchased from Syntrillium (http://www.syntrillium.com). Install this on a PC with a sound card and microphone. Connect an analog telephone to one of the Winscribe ports and ring the operator, and then ask the operator to hang-up. Use AUDITION to record and analyze the signal. Refer to Managing Servers (see page 164) for a list of commonly used disconnect frequencies.

Note: You must use an analog telephone to record a disconnect tone. Digital telephones will not work.

http://www.syntrillium.com/

197

Appendix 2. ATS Keypad Functions

The following table details each of the key functions that can be associated with Key sequences in a keypad definition.

Table Key

Value The integer value of the Function (required for CustomKey methods in scripts)

Valid Types The keypad types for which the function is valid:

E = Edit

R = Review

T = Transcription

Function

Value

Valid Types

Notes

Record 1 E,R Recording at the current position in the last mode set (defaults to insert)

RecordInsert 2 E,R Records in insert mode

RecordOverWrite 3 E,R Records in overwrite mode

RecordModeToggle 4 E,R Toggles between insert and overwrite mode

RecordInsertMode 5 E,R Sets record mode to insert

RecordOverwriteMode 6 E,R Sets record mode to overwrite

Play 7 E,R,T Plays from the current position

PlayFast 8 E,R,T Plays from the current position at 2x speed

Rewind 9 E,R,T Rewinds until the next command or beginning of file reached

RewindFast 10 E,R,T Fast rewinds until the next command or beginning of file reached

RewindToBeginning 11 E,R,T Rewinds immediately to the beginning

Rewind5 12 E,R,T Rewinds 5 secs




Rewind5Play 16 E,R,T Rewinds 5 secs then begins playing



Rewind15PlayRepeat 19 E,R,T Rewinds 15 secs plays 5 secs then repeats until the next command or beginning of file reached

Rewind30PlayRepeat 20 E,R,T Rewinds 30 secs plays 5 secs then repeats until the next command or beginning of file reached

Forward 21 E,R,T Forward until the next command or beginning of file reached

ForwardFast 22 E,R,T Fast forward until the next command or end of file reached


198


ForwardToEnd 23 E,R,T Forward immediately to the end

Forward5 24 E,R,T Forward 5 secs




Forward5Play 28 E,R,T Forward 5 secs then begins playing



Forward5PlayRepeat 31 E,R,T Forward 5 secs plays 5 secs then repeats until the next command or beginning of file reached



BookmarkSet 34 E,R Sets a bookmark at the current position

BookmarkNext 35 E,R,T Moves to the next bookmark

BookmarkPrevious 36 E,R,T Moves to the previous bookmark

BookmarkDeleteCurrent 37 E,R Deletes the bookmark at the current position

BookmarkDeleteAll 38 E,R Deletes all bookmarks

BookmarkPlayNext 39 E,R,T Moves to the next bookmark and begins playing

BookmarkPlayPrevious 40 E,R,T Moves to the previous bookmark and begins playing

BlockMark 41 E,R Sets a block mark at the current position

BlockMarkStart 42 E,R Set a block start mark at the current position

BlockMarkEnd 43 E,R Set a block end mark at the current position

BlockMarkClear 44 E,R Clears any block marks

BlockCut 45 E,R Cuts the block of audio between two block marks

BlockPaste 46 E,R Paste a cut block of audio at the current position

VolumeUp 47 E,R,T Increases the volume

VolumeDown 48 E,R,T Decreases the volume

VolumeNormal 49 E,R,T Sets the volume to normal

SpeedUp 50 E,R,T Increases the speed

SpeedDown 51 E,R,T Decreases the speed

SpeedNormal 52 E,R,T Sets the speed to normal

PreTypeReviewToggle 53 E,R Toggles the state of pre-type review

PreTypeReviewOn 54 E,R Sets pre-type review on

PreTypeReviewOff 55 E,R Sets pre-type review off

PostTypeReviewToggle 56 E,R Toggles the state of post-type review

PostTypeReviewOn 57 E,R Sets post-type review on

199


PostTypeReviewOff 58 E,R Sets post-type review off

JobNumberSpeak 59 E,R,T Speaks the job number

KeyFieldSpeak 60 E,R,T Speaks the value of the key field

UserFieldsSpeak 61 E,R,T Speaks the value of each of the user fields

UserFieldsReEnter 62 E,R Prompts the user to re-enter the user fields

PriorityToggle 63 E,R Toggles the priority of the job

PriorityHigh 64 E,R Sets priority to high

PriorityLow 65 E,R Sets Priority to normal

Pause 66 E,R,T Pauses

Cancel 67 E,R,T Pauses

RedoInput 68 E,R,T Pauses (currently unused)

BookMarkMenu 69 E,R,T Offers the Winscribe bookmark menu (see author telephone guide)

BlockMarkMenu 70 E,R Offers the Winscribe block mark menu (see author telephone guide)

SettingsMenu 71 E,R,T Offers the Winscribe settings menu (see author telephone guide)

ReviewPrePostMenu 72 E,R Offers the Winscribe pre-post review menu (see author telephone guide)

UserFieldsMenu 73 E,R Offers the Winscribe user fields menu (see author telephone guide)

Help 74 E,R,T Offers the help menu

EndJobComplete 500 E Completes the job

EndJobDiscard 501 E Discards the job

EndJobLeaveOpen 502 E Leaves the job open

EndJobDelete 503 E Deletes the job

EndJobCompleteHangup 504 E Completes the job then hangs up

EndJobDiscardHangup 505 E Discards the job then hangs up

EndJobLeaveOpenHangup 506 E Leaves the job open then hangs up

EndJobDeleteHangup 507 E Deletes the job then hangs up

EndJobMenu 508 E Offers the Winscribe end job menu (see author telephone guide)

EndReviewComplete 600 R Ends and completes review

EndReviewCompleteNext 601 R Ends and completes review and begins reviewing the next in the job list

EndReviewCompletePrevious 602 R Ends and completes review and begins reviewing the previous in the job list

EndReviewCompleteHangup 603 R Ends and completes review and hangs up

EndReviewInComplete 604 R Ends an incomplete review.

EndReviewInCompleteNext 605 R Ends an incomplete review and begins reviewing the next in the job list

200


EndReviewInCompletePrevious 606 R Ends an incomplete review and begins reviewing the previous in the job list

EndReviewInCompleteHangup 607 R Ends an incompletes review and hangs up

EndReviewDiscard 608 R Ends review, discarding any changes

EndReviewDiscardNext 609 R Ends review, discarding any changes and begins reviewing the next in the job list

EndReviewDiscardPrevious 610 R Ends review, discarding any changes and begins reviewing the previous in the job list

EndReviewDiscardHangup 611 R Ends review, discarding any changes and hangs up

EndReviewMenu 612 R Offers the Winscribe end review menu (see author telephone guide)

EndTranscriptionMenu 700 T Offers the Winscribe end transcription menu (see typist telephone guide)

EndTranscriptionComplete 701 T Completes transcription

EndTranscriptionCompleteNext 702 T Completes transcription, starts transcribing the next job

EndTranscriptionCompleteHangup

703 T Completes transcription and hangs up

EndTranscriptionInComplete 704 T Leaves job incomplete

EndTranscriptionInCompleteNext 705 T Leaves job incomplete, starts transcribing the next job

EndTranscriptionInCompleteHangup

706 T Leaves job incomplete and hangs up

EndTranscriptionOnHold 707 T Leaves job incomplete, placing it on hold

EndTranscriptionOnHoldNext 708 T Leaves job incomplete, placing it on hold, starts transcribing the next job

EndTranscriptionOnHoldHangup 709 T Leaves job incomplete, placing it on hold and hangs up

EndTranscriptionReject 710 T Leaves job incomplete, placing it back in the general queue

EndTranscriptionRejectNext 711 T Leaves job incomplete, placing it back in the general queue, starts transcribing the next job

EndTranscriptionRejectHangup 712 T Leaves job incomplete, placing it back in the general queue and hangs up

201

Appendix 3. Installing the Web Components (Full)

Prerequisite Requirement: The Web Components require .NET 4 to be installed.

To install the Winscribe Web Components:




Note: In order to install Winscribe Web Manager, you must be logged in with local Administrative rights. If you intend using NT authentication to access the Winscribe Database Server, then you must have admin rights to SQL Server as well.





202


3. Select to install Data Provider, Web Manager, and Mobile Web Service, and then click Next:

4. Prerequisite check:

The installer will check that Crystal Reports Runtime 13 has been pre-installed.

If you need to install the runtime, the instructions are here:


1) On the installation server, insert the Winscribe Distribution DVD.

From the Winscribe Dictation 4.2 Installer DVD web page, select:


Or



2) Follow the on-screen instructions to complete the installation.

Once the prerequisite check is OK, click Next to continue.

203



Enter your database Username and Password.

Click Next.


The Winscribe Web Manager Setup wizard will copy the required files to your local hard disk. This may take several minutes to complete.

7. Once the installation process has completed, the Web Manager Configuration wizard appears.

Click Next to commence configuration.

204


8. Enter the language and time format defaults for Winscribe Web Manager.

The time format default controls the format time will be displayed in, for example 10pm is displayed as 10:00pm in the 12 hour format, or 22:00 in the 24 hour format.

9. Enter the Root Login password.

The Root Login is used to log in to the Winscribe Web Manager and change the database login details.


10. Enter the Admin Login password.

The Admin Login is used to log in to the Winscribe Web Manager and change server-wide parameters, which affect all facilities on a Winscribe Server.

205


If Web Manager has been installed before (for example, if you are upgrading to a new version), you can retain your previous Admin login and password by ticking the 'Keep current username and password' checkbox.


11. Enter the Owner Login password.

The Owner Login is used to log in to the Winscribe Web Manager and add and change facilities.

If Web Manager has been installed before (for example, if you are upgrading to a new version), you can retain your previous Owner login and password by ticking the 'Keep current username and password' checkbox.


12. Enter the name of an SMTP server that the Winscribe Web Manager can use to send emails.

If you do not enter the SMTP server name, the password retrieval email feature will not operate.


206


13. If Winscribe is being installed at a site that utilizes Active Directory and you wish to take advantage of Active Directory's 'Single sign on' feature for applications, select the Use Active Directory Integration radio button.

Enter the name of the Domain you wish to query for a list of authorized Winscribe users.

Enter the user name and password of a Domain administrator account that has sufficient permissions to query the Active Directory database for a list of those users.

If the site is not using Active Directory please leave the default setting Not Using Active Directory Integration.


14. You are now ready to complete the Winscribe Web Manager configuration.

Click Save to save the settings you have entered, or press Back to make changes.

207


15. The Configuration Wizard saves your settings, displaying progress as it goes.

Click Finish to complete the Winscribe Web Manager configuration.

16. The Winscribe Web Manager Installation Complete window is displayed.

Click Close to complete the installation and exit.

Note: IIS comes with a limit on the size of files that are allowed to be transferred via ASP scripts. This limit blocks large Winscribe jobs from being downloaded. You can increase this limit by following the instructions in Increasing IIS File-size Limit.

You must ensure that the Winscribe Web Components will have full access to the Winscribe Shared Directory. The Web Components 'impersonate' a user when they try to gain access to the Shared Directory, so the user account that the components impersonate must have full access to the shared directory. The impersonated user is determined by the Identity of the Application Pool associated with Winscribe site in IIS (DictationAppPool by default). If you use other security methods, you will need to ensure all appropriate users have access to the shared directory.

17. The next step is to configure the Mobile Web Service, which is done by running the Mobile Web Service Configuration application in the Start menu:

Start / Winscribe / Tools / Mobile Web Service Configuration

208


18. With the Mobile Web Service Configuration application open, click Next:

19. Enter the SQL Server connection settings:

Enter the name of the Server, your Winscribe Database, Connection and Authentication methods. If using SQL Server authentication, enter your Login ID and Password.

Click Next.

209


20. Enter the SMTP Server settings, or leave blank if not required:

Click Next.

21. Edit Settings as required:

The path to the upload directory is:

C:\Program Files\Winscribe\Web Components\Data Provider\App_Data\Uploads\

Note: The Security and Server Settings only apply to job authentication methods when using Winscribe on mobile devices.

Click Next when completed.

210


22. Complete the Mobile Device Application Settings. Unless installing the Mobile Web Service for use with mobile devices (Blackberry Smartphone), you can accept the defaults and click Next.

Full details on these settings can be found in the Winscribe for Mobile Devices Installation Guide.

23. The Configuration wizard now has sufficient information to update your system. Click Save to run the configuration process.

211


24. The configuration file has now been updated. Click Finish to complete and exit the setup wizard:

212


A

About this Guide • 7 Active Directory Settings • 118 An author-reviewer can't find/access an existing job

• 161 An error has occurred attempting to open the

Winscribe database • 160 Appendix 1. Programming Requirements for PBX's •

195 Appendix 2. ATS Keypad Functions • 197 Appendix 3. Installing the Web Components (Full) •

201 Archive • 176 Archive/save VOX files • 163 Assigning a Pre-Programmed Device to a Line • 170 Assigning a Pre-Programmed Device To a Line • 174 ATS Installation Summary • 68 Author Keys • 168 Author Line Keys • 170 Author/Client Grid Layout • 151 Author/Internet Author • 148 Automatic Deployment of Scripts • 148 Automatic Installer Logs • 145 Automatic Updates • 141

C

Can't register components during installation • 159 Changing SQL Credentials • 21 Changing the Default Winscribe Shared Directory

Properties • 44 Chapter 1. Installing Winscribe Server Components •

9 Chapter 2. Installing Winscribe Server Manager

Applications • 92 Chapter 3. Installing Client Applications • 139 Chapter 4. Managing Servers • 164 Chapter 5. Upgrading to Winscribe Version 4.2 • 183 Chapter 6. Uninstalling Winscribe • 194 Choosing a Dialogic Card • 17 Client • 147 Client Apps • 122, 131 Client Installers • 141 Client Option Features • 142 Command Line • 141 Configuration • 70 Configuration of the Job Upload functionality • 105 Configuring a Windows Service to Start

Automatically • 164 Configuring Client Installer Properties • 142 Configuring Features • 142 Configuring Share Properties • 43 Configuring Share Properties if Installing a Secondary

Server • 44

Configuring Telephony Manager • 94 Configuring the IPPhone Service • 86 Configuring the Temp Folder when Importer is run as

a Windows Application • 155 Configuring the Temp Folder when Importer is run as

a Windows Service • 138 Configuring the Winscribe Active Directory

Synchronization Tool • 119 Configuring Winscribe Telephony Parameters • 165 Configuring Winscribe Web Server Settings • 179 Considerations for Installing Winscribe Web

Components • 45 Contacting Winscribe Technical Support • 89

D

Default Disconnect Tones • 168 Defining Call Progress Tones • 79 Defining Disconnect Tone • 79 Defining Special Tones • 80 Determine Disconnect Frequency • 195 Dialogic Cards that are Universal PCI compliant • 18 Dialogic Driver installation failed • 181 Dialogic Telephony Hardware Requirements • 17 Dictation Storage Requirements • 16 Disabling the Upgrade Prompt • 188 Disconnect Tone Examples • 167 DNIS • 74 Download .aspx file • 57

E

Enabling 32bit Microsoft.NET on Server 2003 64bit • 67

Enabling Distributed Audio • 50 Error 502 Check your Winscribe URL • 160 Error attempting to create a new dictation! • 163 Error No Voice Server Present • 163 Example Scripts for the • 149 Examples • 141 Examples of Network Impact • 13

F

Facilities • 176 Feature Summary • 68 Firewall preventing data traffic • 161

G

General Usage • 76 Global Settings • 72

H

Hangup Tones • 167 HMP Licensing • 83 HMP Software • 82

Index

213

Index

How Many Licenses Do You Need? • 89 How to Stop/Start Winscribe Services • 164 HTTP 403 / HTTP 404 • 56

I

IIS File-size Limit • 91 Import • 176 Inspecting Verbose Windows Installer Logs • 145 Install Location • 143 Install Prerequisites • 97, 111, 118 Install stops responding • 159 Installation Configuration • 96, 111 Installation Option One

New Install • 83 Installation Option Two

Existing Winscribe Dictation Server without Telephony • 86

Installation Overview • 83 Installation Summary • 96, 110 Installation Summary for Windows 2003 Server • 52 Installation Summary for Windows 2008 Server • 57 Installation Summary for Windows 2012 Server • 62 Installer Privileges • 141 Installer Properties • 143 Installing a Client Application onto a Clean System •

193 Installing Crystal Reports Runtime 13 • 97, 112 Installing Microsoft .NET 4 • 97, 112, 119 Installing Support for WMA (optional) • 112 Installing the Web Components • 46 Installing the Winscribe Active Directory

Synchronization Tool • 118 Installing Winscribe Exporter Service & Manager •

114 Installing Winscribe Web Manager • 98 Installing/Modifying IIS • 52 Internet request failed. Web page was not found. •

160 Introduction • 68 Invalid User Id or security code • 160 ISDN Telephony • 19

J

Job's Voice File not found! • 162

K

Key Logging • 80 Keypad Assignment • 76 Keypads • 75

L

LAN / WAN & Internet Bandwidth Requirements • 12 License Files • 183 Licensing your Winscribe Software • 89 Line Defaults • 73 Line Overrides • 74 Logging • 145

M

Manually Changing the URL • 193 Microsoft SQL Server Express or SQL Server • 20 Minimum Hardware and Software Requirements •

96, 111 Minimum Requirements

Winscribe Author, Winscribe Client, Internet Author and Importer • 140

N

Next Steps • 70, 105, 117 No Sound Card Detected! • 160 No sound when playing a job or prompt • 161 Nothing was recorded • 161

O

Option 1 Installing a Primary Server • 35

Option 2 Installing a Primary Server with Telephony • 37

Option 3 Installing a Secondary Server • 41

Other Documentation • 7 Other Settings in the Author Line Keys Section • 171 Other Settings in the Typist Line Keys Section • 175 Overriding the Default Keypad Mapping • 170, 174 Overview • 141 Overview of Manual Contents • 7

P

Passing Installer Properties • 142 PCI-Express compatibility • 18 PCISIG Specification for Universal PCI • 17 Playback starts at the wrong location • 162 Prerequisites • 45, 183 Prerequisites for the Winscribe Server Installation •

23 Prerequisites for Windows 2003 Server • 51 Programming Requirements for PBXs • 19 Programming Requirements for PBX's With DID

(Direct Inwards Dialing) • 195 Programming Requirements For PBX's Without DID •

195 Prprompt • 176

R

Raw .aspx code • 57 Recording Audio Quality • 145 Recrding • 176 Registry Locations • 67 Removing Multiple Features • 142 Report • 177 Running SQL Server 2005 or SQL Express on

Windows Server 2008 or Windows Vista Operating Systems • 21

Running Winscribe with a SQL Named Instance • 22

214


S

Scheduling Outbound Scripts • 78 Section 1

Features and Prerequisites • 139 Introduction and Installation Summary • 9 Winscribe Telephony Manager • 92

Section 10 Post Installation Steps & Licensing • 88

Section 2 Client Deployment Guidance • 141 SQL Server Database Software • 20 Winscribe Web Manager • 96

Section 3 Installing Winscribe • 146 Installing Winscribe Server • 23 Winscribe Exporter • 110

Section 4 Installing Internet Importer (Standard Windows

Application) • 153 Installing Winscribe on Windows 2003 Server •

51 Winscribe Active Directory Synchronization • 117

Section 5 Configuring Web Installation • 155 Installing Winscribe Internet Importer as a

Windows Service • 135 Installing Winscribe on a Microsoft Windows

2008 Server • 57 Section 6

Installing Winscribe Author, Winscribe Client, Internet Author, or Importer via the Web • 156

Installing Winscribe on a Microsoft Windows 2012 Server • 62

Section 7 Customizing the Login Window • 158 Installing Winscribe on 64-bit Operating Systems

• 66 Section 8

Installing Winscribe ATS • 68 Troubleshooting Client Applications • 159

Section 9 Installing Winscribe Voice over IP (VoIP) • 82

Server 2003 — Authentication Methods • 120 Server 2003 R2 SP2 — Authentication Methods •

126 Server 2008 — Authentication Methods • 129 Server URL • 143 Service Packs • 18 Setting Installation Parameters • 146 Setting up Database Mail for use with Alarm Email

Notification and Workflow Email Notification • 107

Shutting Down a Winscribe Server • 178 Silent Install • 144 Single Sign-on Configuration • 118 Sound Card in use by another Application! • 161

Sound volume is too low • 162 Speak • 177 SQL Configuration Settings • 21 SQL Server not found • 159 Step 1

Configure Advanced Sharing Options • 62 Create a Script • 105 Turn on Network Discovery • 57

Step 1 Install ATS Prerequisites • 69 Step 1 Install Dialogic Telephony Boards • 24 Step 1 Upgrade the License Server • 184 Step 10 Install the Client Applications • 56 Step 2

Create the SQL Trigger • 106 Install Required IIS Features • 58, 63

Step 2 Install ATS • 69 Step 2 Install the Dialogic Drivers • 24 Step 2 Remove LAN Manager • 185 Step 3

Install Winscribe • 61, 65 Specify the Source • 106

Step 3 Configure ATS • 71 Step 3 Configure the Dialogic Boards • 28 Step 3 Upgrade the Dictation Server • 186 Step 4

Install Desktop Experience • 62, 65 Specify the Destination • 106

Step 4 Configure Advanced Review • 77 Step 4 Install Microsoft .NET 4 • 30 Step 4 Install Telephony Manager • 186 Step 5

Create a new Rule • 106 Step 5 Beyond Advanced Review • 77 Step 5 Install the Winscribe License Server • 30 Step 5 Upgrade the Web Components • 187 Step 6

Start the Importer Monitor. • 107 Step 6 Install the Winscribe Dictation Server

Software • 33 Step 6 Upgrade the Client Applications • 187 Step 7 Install the Winscribe Web Components • 45 Step 7 Remove Discontinued Client Applications •

188 Step 8 Configure IIS Server for Web Components on

Windows 2003 Server • 52 Step 9 Prepare to Install the Client applications on

Windows 2003 Server • 55 Steps 1-7 • 52 Sub-directories in the Shared Directory • 175 Summary of URL Updates • 193 Supported Export Formats • 112

T

Telephone port not disconnecting • 182 The Database Tab • 95 The Server Tab • 95 Timeouts • 165

215

Index

Tone Detection • 79 Training • 177 Transferring an Existing MSDE Winscribe Database to

a New SQL Server • 22 Troubleshooting • 192 Troubleshooting Servers • 181 Troubleshooting Winscribe ATS • 70 Troubleshooting Winscribe Installation on Windows

2003 Server • 56 Typist Keys • 172 Typist Line Keys • 174 Typist's foot pedal doesn't work • 162

U

Uninstalling Winscribe ATS • 69 Updating the URL • 192 Upgrade Steps • 191 Upgrade Summary for Winscribe Version 4.2 • 183 Upgrades • 177 Upgrading a Client Application • 193 Upgrading a Server from 2.5 to 3.0 • 191 Upgrading a Server to Support Telephone Dictation •

189 Upgrading a system with Exporter licenses • 188 Upgrading a system with Mobile Recorder licenses •

189 Upgrading a system with Server-side Speech

Recognition • 188 Upgrading the Web Manager Author Job Upload

feature • 189 User Accounts Mapping • 134 User Working Directory • 144 UserProm • 177 Users • 177 Using Distributed Audio • 49 Using Self-signed SSL Certificates with Winscribe •

51

W

Web Components and Primary Server on Different Boxes • 49

Web Manager • 124, 133, 134 Web Security Considerations • 49 Who should read this manual? • 8 Windows Event Log • 180 Winscribe Active Directory Synchronization

Installation Procedure • 119 Winscribe Author and Internet Author • 140 Winscribe Client • 140 Winscribe does not answer calls • 182 Winscribe Server • 177 Winscribe Server Hardware & Network Minimum

Requirements • 11 Winscribe Server has been shutdown for system

maintenance • 159 Winscribe Server Requirements • 10 Winscribe Server Shutdown for maintenance • 182

Winscribe Server Uninstall Procedure • 194 Winscribe Server URL • 48 Winscribe Services do not appear in the Services

window • 181 Winscribe Shared Directory • 175 Winscribe Windows Services • 164

Y

Your demonstration license has expired! • 160

Winscribe Installation Guide · 2013-10-31 · 7 About this Guide This guide describes how to...

Documents

Transcript of Winscribe Installation Guide · 2013-10-31 · 7 About this Guide This guide describes how to...