4.2 bighand mobility technical requirements

7/31/2019 4.2 BigHand Mobility Technical Requirements

1/10

B I G H A N D M O B I L I T Y T E C H N I C A L R E Q U I R E M E N T SSoftware version: 4.2

Last edited date: 26 October 2011


2/10

ontents

Contents

Contents 2

Introduction 3

BigHand Mobility Topology 4

BigHand Email Gateway 5

BigHand Email Gateway (COM+) 6

BigHand Email Exchange Service (Exchange Web Services) 7

BigHand Telephony 9

BigHand Web Client 10


3/10

3

Introduction

The mobility options are as follows:

l BigHand Email Gateway

l BigHand Web Client

l BigHand Telephony

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


4/10

4

BigHand Mobility Topology

The architecture below summarises the server side and additional components required for BigHand

Email Gateway, Telephony and Web Client.


5/10

gHandEmail 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 BigHand Email Gateway

l BigHand Gateway


6/10

BigHandEmail Gateway

6

BigHand Email Gateway (COM+)

Description:A BigHand COM+ component which resides on the Exchange server*, monitoring one

or more mailboxes for messages with voice file attachments.

Component

of:Mobility Suite - BigHand Email Gateway

Connects to: BigHand Gateway

Target of: BigHand for Windows Mobile and email submissions

Processor: N/A*

Memory

(RAM):N/A*

Storage

requirement:Negligible

Operating

System:

Minimum: Windows Server 2003; Recommended: Windows Server 2003, Windows

Server 2008, Windows Server 2008 R2 (64-bit versions supported)

.NET

Framework:.NET Framework version 2.0

Connection

info:N/A

Other

information:

* 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

processing.

BigHand recommends that the latest relevant Service Packs and Windows Updatesare 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.


7/10

gHandEmail Gateway

BigHand Email Exchange Service (Exchange Web Services)

Description:A Windows service that communicates with Microsoft Exchange to extract voice files

sent to specific mailboxes and submit those attachments to the BigHand system.

Component

of:Mobility Suite - Email Gateway

Connects to: Microsoft Exchange and BigHand Gateway

Target of: None*

Processor: N/A (as for OS)

Memory

(RAM):N/A (as for OS)

Storage


Operating

System:

Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64-bit

versions supported)

.NET


Connection

info:Web services calls using Exchange Web Services

Otherinformation:

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

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.


8/10

BigHandEmail Gateway

8

BigHand Gateway

Description:A Windows service that processes voice files sent in by email or smartphone and then

submits them to the BigHand core.

Component

of:

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: Email Gateway (COM+), Email Gateway (Exchange Web Services), Mobile Gateway

Processor: As for BigHand Server service*

Memory

(RAM):As for BigHand Server service*

Storage

requirement:As for BigHand Server service*

Operating

System:

As for BigHand Server service*

.NET


Connection

info:Web services, file system access

Co-exist

with other

services:

Yes

Other

information:

* 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 approximatelymatch 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).

Minimum specification may increase if other applications outside of BigHand are also

running on the same machine.


9/10

gHandT elephony

BigHand Telephony

Description: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.

Component

of: Mobility Suite Telephony

Connects to: BigHand Server

Target of: Telephone voice calls

Processor: Minimum: Pentium IV

Memory

(RAM):1 GB

Storage

requirement:10 GB

OperatingSystem:

Windows Server 2003*

.NET

Framework:.NET 3.0

Connection

info:TCP/IP

Co-exist

with other

services:

No see Other information

Other

information:

BigHand recommends a dedicated server for this component. The server must have aPCI 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 XML Parser).

Minimum specification may increase if other applications outside of BigHand are also

running on the same machine.


10/10

BigHandWeb Client

10

BigHand Web Client

Description:An ASP.NET application that accepts voice files uploaded through a web browser

interface.

Component

of: Mobility Suite

Connects to: BigHand Services Host

Target of: User, via browser

Processor: As required by OS and IIS*

Memory

(RAM):256 MB

Storage


OperatingSystem:

Windows Server 2003, Windows Server 2008 (64-bit versions supported), WindowsServer 2008 R2

.NET

Framework:.NET Framework: Versions 2.0 and 3.0

Connection

info:HTTP/S and WCF web services

Other

information:

* IIS version 6 or version 7 (Internet Information Services) required. A server

authentication certificate is recommended to ensure file upload security.

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.

4.2 bighand mobility technical requirements

Documents