B IG H AN D MO B IL ITY TE CH N ICAL R E Q U IR E ME N TS

Software version: 4.2 Last edited date: 26 October 2011

Contents

Contents
Contents
Introduction BigHand Mobility Topology

2
3 4

BigHand Email Gateway

BigHand Email Gateway (COM+) BigHand Email Exchange Service (Exchange Web Services)

5
6 7

BigHand Telephony BigHand Web Client

9 10

Introduction
The mobility options are as follows:
l l l

BigHand Email Gateway BigHand Web Client BigHand Telephony

Please refer to the BigHand for Smartphone Technical Requirements for device mobility options.

BigHand Mobility Topology

The architecture below summarises the server side and additional components required for BigHand Email Gateway, Telephony and Web Client.

BigHand Email Gateway

BigHand Email Gateway

The BigHand Email Gateway option enables users who record using a remote device to use a web based or home email account to send voice files into the system (e.g. Hotmail, Gmail or OWA). The BigHand Workflow Server automatically routes the work to the chosen recipient(s) with no manual file saving or email opening required. The subject line, priority and recipient of the email are interpreted by the BigHand Email Gateway and the voice file appears in a transcribers work in progress as normal. Authors can also send voice files in .amr file format using email-capable smartphones. The BigHand Email Gateway requires the following:
l l

BigHand Email Gateway BigHand Gateway

BigHand Email Gateway

BigHand Email Gateway (COM+)

Description: Component of: A BigHand COM+ component which resides on the Exchange server*, monitoring one or more mailboxes for messages with voice file attachments. Mobility Suite - BigHand Email Gateway

Connects to: BigHand Gateway Target of: Processor: Memory (RAM): BigHand for Windows Mobile and email submissions N/A* N/A*

Storage Negligible requirement: Operating System: Minimum: Windows Server 2003; Recommended: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET .NET Framework version 2.0 Framework: Connection info: N/A * This component is resident on Exchange Server. Exchange Server 2000, 2003 or 2007 (before SP1) required (64 bit versions supported).
Voice files are processed as they arrive at the Exchange Server and are deleted after

Other information:

processing.
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. Clustering: Install the BigHand Email Gateway on all physical nodes in an Exchange cluster. Do not install BigHand Email Gateway on virtual nodes.

BigHand Email Gateway

BigHand Email Exchange Service (Exchange Web Services)

Description: Component of: AWindows service that communicates with Microsoft Exchange to extract voice files sent to specific mailboxes and submit those attachments to the BigHand system. Mobility Suite - Email Gateway

Connects to: Microsoft Exchange and BigHand Gateway Target of: Processor: Memory (RAM): None* N/A (as for OS) N/A (as for OS)

Storage Negligible requirement: Operating System: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET .NET Framework version 3.5 Framework: Connection info: Web services calls using Exchange Web Services The service does not need to be hosted adjacent to Exchange Server. Microsoft Exchange 2010 and Microsoft Exchange 2007 SP1 are supported. Autodiscovery must be enabled on the Exchange Server. * The service independently polls the Exchange looking for newly arrived voice file attachments.
The service deletes the messages from the mailboxes on the Exchange Server after

Other information:

processing the attachments. Processing simply involves transferring the files to another BigHand component, the BigHand Gateway.
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the operating system before installing this component.

BigHand Email Gateway

BigHand Gateway Description: Component of: A Windows service that processes voice files sent in by email or smartphone and then submits them to the BigHand core. Mobility Suite - Email Gateway, BigHand for BlackBerry, BigHand for Windows Mobile, BigHand for iPhone and BigHand for Android

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): Email Gateway (COM+), Email Gateway (Exchange Web Services), Mobile Gateway As for BigHand Server service* As for BigHand Server service*

Storage As for BigHand Server service* requirement: Operating System: As for BigHand Server service*

.NET .NET Framework version 3.0 Framework: Connection info: Co-exist with other services: Web services, file system access

Yes * This component may be installed on the BigHand server. If the component is installed on a separate server, the specification of this gateway server should approximately match the BigHand server. Requires a service account can use the BigHand Server account.
Requires either to write to a directory, or upload via file service (recommended).

Other information:

Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

BigHand Telephony

BigHand Telephony
Description: Component of: A Windows service hosted on a telephony server. This module records voice files over the telephone and then submits them to the BigHand Server service. Mobility Suite Telephony

Connects to: BigHand Server Target of: Processor: Memory (RAM): Telephone voice calls Minimum: Pentium IV 1 GB

Storage 10 GB requirement: Operating System: Windows Server 2003*

.NET .NET 3.0 Framework: Connection info: Co-exist with other services: TCP/IP

No see Other information BigHand recommends a dedicated server for this component. The server must have a PCI TAPI telephony card with Global API support. Supported types include Intel Dialogic D4PCIUFEU, D41JCTLS and D120JCT. The target server requires enough physical space to house the PCI telephony card. The 4 port card is a half-length card and the 6 or 12 port cards are full length PCI cards. The server must have a full size PCI slot. Newer servers may only have PCI Express slots, in which case you will need to install and test the telephony card using an adapter. BigHand supports regular 5v or 3.3v PCI slots and PCI-X slots commonly found on server grade machines. PCI-Express slots (aka PCIe) are not suitable. * BigHand recommends that the latest relevant Service Packs and Windows Updates are installed on the Operating System before installing this component. Requires a service account if running in an Active Directory synchronised BigHand environment. Internet Explorer 6 or later (required for the XMLParser). Minimum specification may increase if other applications outside of BigHand are also running on the same machine.

Other information:

BigHand Web Client

BigHand Web Client

Description: Component of: An ASP.NET application that accepts voice files uploaded through a web browser interface. Mobility Suite

Connects to: BigHand Services Host Target of: Processor: Memory (RAM): User, via browser As required by OS and IIS* 256 MB

Storage Negligible requirement: Operating System: Windows Server 2003, Windows Server 2008 (64-bit versions supported), Windows Server 2008 R2

.NET .NET Framework: Versions 2.0 and 3.0 Framework: Connection info: HTTP/S and WCF web services * IIS version 6 or version 7 (Internet Information Services) required. A server authentication certificate is recommended to ensure file upload security. Other information:
BigHand recommends that the latest relevant Service Packs and Windows Updates

are installed on the Operating System before installing this component. Tested browsers: IE6, IE7, IE8, IE9.

10