This guide is written with both the systems implementer and systems administrator in mind. It shows you how to

(1)

Chapter

1 –

Introduction

Congratulations

on

your

purchase

of

the

NET

SatisFAXtion

IP

Port

Server

from

FaxBack,

Inc.

Many

years

of

effort

have

gone

into

developing

a

system

that

will

give

you

the

functionality

you

desire

today

and

a

platform

that

can

accommodate

your

growing

needs

in

the

years

to

come.

How

to

Use This

Manual

To

make

the

guide

clear

and

easy

to

read,

symbols

have

been

used

to

identify

information

that

is

critical

to

the

operation

of

your

FaxBack

system.

Please

pay

close

attention

to

anything

identified

as

Important

Information.

About this Guide

This

guide

is

written

with

both

the

systems

implementer

and

systems

administrator

in

mind.

It

shows

you

how

to

install

and

configure

the

NET

SatisFAXtion

IP

Port

Server.

It

also

shows

you

how

to

install

and

configure

client

software.

Customer

Service

FaxBack

is

dedicated

to

giving

our

customers

world

‐

class

support.

New

purchases

include

30

days

of

free

Port

Server

support

from

the

date

of

purchase.

Extended

support

plans,

including

telephone,

fax,

email

and

remote

dial

‐

in

support,

are

available

on

an

annual

basis.

To

find

out

more

about

FaxBack’s

portfolio

of

electronic

and

person

‐

to

‐

person

technical

support

options

designed

to

meet

your

needs,

please

visit

our

web

site

at:

http://www.faxback.com/support

There

are

several

ways

to

purchase

a

new

software

subscription

or

to

renew

an

existing

subscription:

Email

[email protected]

Web

http://www.faxback.com/support/overview

Phone

800

‐

FAXBACK

(800

‐

329

‐

2225)

or

(503)

597

‐

5350

Knowledge

Base and Technical Support

If

you

need

technical

support

on

your

FaxBack

products,

your

first

and

best

option

is

to

search

the

FaxBack

Knowledge

Base

which

can

be

found

at:

http://www.faxback.com/support.

This

technical

database

gives

you

access

to

valuable

information

on

installation,

configuration

and

maintenance

issues.

The

extensive

database

includes

powerful

search

capabilities,

allowing

you

to

access

information

quickly.

If

you

need

help

and

cannot

find

your

answers

in

this

manual

or

in

the

Knowledge

Base,

please

feel

free

to

contact

us.

Comments

and

suggestions

regarding

the

documentation

are

also

welcome.

The

Knowledge

Base

is

available

for

free

to

all

FaxBack

customers.

To

obtain

technical

support

by

telephone,

fax

or

email,

you

must

provide

the

six

‐

digit

Server

ID

that

was

provided

to

you.

With

this

code

and

a

current

support

agreement,

you

can

contact

Port

Server

support

in

one

of

the

following

methods:

(2)

Support E‐mail

[email protected]

Support Telephone

(503)

597

‐

5360

Please

be

prepared

to

fully

describe

your

hardware

and

network

setup,

the

conditions

under

which

the

problem

is

occurring

and

the

effects

of

the

problem.

(3)

Chapter

2 –

Server Overview

The

NET

SatisFAXtion

IP

Port

Server

enables

telecom

service

providers

to

offer

e

‐

fax

services

to

their

customers.

It

is

robust

and

highly

scalable

up

to

DS3

(672

ports)

densities.

Its

modular

nature

allows

it

to

be

adapted

to

fit

nearly

any

network

architecture.

What

role does

the Port Server play in the existing

VoIP

infrastructure?

Port

Server Overview

Figure 2‐1: Overview of the NET SatisFAXtion IP Port Server Architecture

There

are

three

major

components

of

the

NET

SatisFAXtion

IP

Port

Server.

They

are

the

Connection

Server,

the

Port

Server

and

the

HTTPS

Proxy.

The

components

communicate

between

themselves

using

HTTP

so

they

can

be

installed

either

all

on

the

same

server,

distributed

across

multiple

servers

on

the

same

LAN,

or

even

geographically

distributed

across

a

WAN.

(4)

Connection

Server

The

Connection

Server

is

the

component

that

clients

log

in

to

in

order

to

send

and

receive

faxes,

and

administrators

connect

to

in

order

to

manage

user

accounts,

inbound

DID

routing

assignments,

and

send

routing

rules.

It

provides

session

tracking,

authentication,

quota

and

usage

tracking

functions.

Port

Server

The

Port

Server

is

the

component

that

facilitates

SIP+T.38

“VoIP

Fax”

connections

with

media

gateways.

Client

software

interacts

with

the

port

server

using

HTTP

or

HTTPS

connections,

using

a

real

‐

time

protocol

that

is

better

able

to

handle

delays

compared

to

a

pure

T.38

connection.

The

more

timing

sensitive

T.38

protocol

is

only

implemented

between

the

port

server

and

the

media

gateway.

Although

clients

interact

directly

with

the

port

server,

the

port

server

does

not

maintain

a

list

of

accounts.

Send

and

receive

connections

are

always

initiated

first

between

the

connection

server

and

the

port

server,

resulting

in

a

unique

“session

id”.

The

port

server

will

only

interact

with

clients

that

can

produce

this

session

id.

Https

Proxy

The

HTTPS

Proxy

is

the

component

that

enables

client

access

to

the

Connection

and

Port

Servers

securely

across

the

open

Internet.

The

HTTPS

Proxy

is

an

ASP.NET

2.0

application

hosted

on

an

IIS

server.

Implementation Overview

Which

Components

Are

Needed?

The

fewest

components

required

are

just

the

Connection

Server

and

the

Port

Server.

This

will

allow

sending

and

receiving

of

faxes

over

unsecured

HTTP

through

the

port

server

to

a

T.38

media

gateway.

It

is

not

recommended

to

put

the

Port

Server

directly

on

the

Internet.

The

HTTPS

Proxy

is

used

to

provide

Internet

‐

accessible

secure

communication.

Implementation

Patterns

There

are

three

general

types

of

NET

SatisFAXtion

IP

Port

Server

installations.

Single Server

(Consolidated)

(5)

The

HTTPS

Proxy,

Connection

Server,

Port

Server,

and

SQL

Server

are

all

installed

on

a

single

server.

This

is

sufficient

for

small

installations

of

24–96

ports.

Multiple Servers

Figure 2‐3: Multiple Server Installation

The

HTTPS

Proxy

and

SQL

Server

are

installed

on

separate

servers.

The

Connection

Server

and

Port

Server

may

be

installed

on

separate

servers,

and

there

may

be

multiple

Port

Servers.

This

is

the

typical

installation

for

a

regional

provider.

Multiple Port

Servers

Figure 2‐4: Distributed Installation

There

is

a

single

HTTPS

Proxy

and

Connection

Server

that

the

clients

connect

to,

but

multiple,

geographically

distributed

Port

Servers.

The

SQL

Servers

are

also

distributed

and

replicate

databases.

(6)

Scalability

&

Reliability

By

default,

the

Connection

Server

will

load

‐

balance

amongst

the

configured

Port

Servers.

Port

Servers

can

also

be

brought

on

‐

line

and

dynamically

added

to

routing

groups

in

case

of

failure.

Both

Connection

Servers

and

Port

Servers

can

be

disabled

for

maintenance

without

disrupting

connected

clients

or

their

faxes.

While

disabled,

that

particular

server

will

refuse

any

new

faxes,

and

any

logged

in

clients

will

be

migrated

to

another

Connection

Server.

Any

faxes

in

progress

when

the

server

is

disabled

will

finish

without

interruption,

but

new

faxes

will

be

routed

to

alternate

servers,

if

available.

Infrastructure Requirements

IIS

/

SQL

Server

Any

version

of

IIS

that

supports

ASP.NET

2.0

is

sufficient

to

run

the

HTTPS

Proxy.

A

Microsoft

SQL

Server

version

2000

or

above

is

required

for

the

Port

Server

and

Billing

databases.

For

smaller

installations,

MSDE

or

SQL

Server

Express

versions

are

sufficient.

SIP+T.38

media

gateway

The

Port

Server

must

be

connected

to

media

gateways

that

support

SIP

and

T.38.

For

outbound

faxes,

the

media

gateway

must

re

‐

INVITE

for

T.38

if

a

fax

is

detected.

For

inbound

faxes,

the

Port

Server

will

immediately

re

‐

INVITE

for

T.38.

Each

Port

Server

can

be

configured

to

use

a

SIP

proxy

instead

using

a

per

‐

Port

Server

user

name

and

password.

Each

Port

Server

can

be

configured

to

send

REGISTER

requests

to

a

SIP

registrar.

Media

gateways

that

are

known

to

work

include

(but

are

not

limited

to):

•

AudioCodes

TrunkPack

and

Mediant

series

•

Most

Cisco

routers

T.38

traffic

is

expected

to

consume

approximately

60kbps

per

active

fax

port.

Upstream

SIP

Trunking

Provider

A

Port

Server

can

be

configured

to

use

an

upstream

SIP

trunking

provider

instead

of

a

media

gateway.

Insure

that

the

upstream

provider

supports

end

‐

to

‐

end

T.38

for

reliable

faxing.

It

is

also

important

to

have

a

low

‐

latency

link

(less

than

50ms

round

‐

trip)

to

the

provider.

LAN

/

WAN

topology

At

this

time,

only

IPv4

networks

are

supported.

(7)

Firewall

considerations

The

HTTPS

Proxy

needs

only

TCP

port

443

(https)

open

to

the

Internet.

From

the

proxy

to

the

Connection

Server

&

Port

Server

components,

each

one’s

corresponding

port

must

be

open.

These

ports

are

configurable

but

default

to

60

(CS)

and

61

(PS).

NAT

traversal

and

client

‐

server

communication

Hardware

and Software

Requirements

CPU

&

RAM

Operating

System

Connection

Server

&

Port

Server

require

one

of

these

operating

systems:

•

Microsoft

Windows

Server

2008,

any

version

(except

Server

Core)

•

Microsoft

Windows

Server

2003

Service

Pack

2,

any

version

•

Microsoft

Windows

Server

2003

R2

Service

Pack

2,

any

version

NET

SatisFAXtion

Port

Server

supports

32

‐

bit

(x86)

and

64

‐

bit

(x64)

versions

of

these

operating

systems.

Itanium

is

not

supported.

Other

Software

The

full

CD

Image

installer

will

install

all

prerequisite

software.

For

speed

of

installation,

it

is

also

possible

to

install

prerequisites

before

installing

the

NET

SatisFAXtion

Port

Server.

The

following

software

is

required

for

NET

SatisFAXtion

Port

Server:

•

Microsoft

.NET

Framework

o

2.0

SP1

o

3.0

SP1

o

3.5

SP1

(8)

Chapter

3 –

Client Overview

What

features does

the Port Server bring your users?

NET

SatisFAXtion

IP

Port

Server

leverages

your

existing

VoIP

network

to

allow

your

users

to

send

and

receive

faxes

from

their

desktops

transparently.

Your

users

can

also

continue

to

use

their

existing

fax

machines

without

the

need

for

a

dedicated

extra

phone

line.

Available

Clients

NET SatisFAXtion Client:

The

NET

SatisFAXtion

fax

server

can

connect

to

the

Port

Server

to

provide

all

the

features

of

a

LAN

fax

server

to

users,

including

server

‐

side

print

conversion

and

additional

desktop

clients

such

as

the

Client

Suite

and

Microsoft

Fax.

Microsoft Fax Client: This

fax

application

ships

with

Windows

XP

and

Vista

(except

the

“Home”

editions

of

Vista),

and

may

be

downloaded

from

the

Microsoft

web

site

for

Windows

2000.

A

Microsoft

Fax

server

is

also

a

part

of

Windows

Small

Business

Server,

Windows

Server

2003

and

Windows

Server

2008.

A

plug

‐

in

is

provided

to

allow

both

of

these

to

use

the

Port

Server

to

send

and

receive

faxes.

Because

this

is

built

in

to

the

operating

system

it

has

a

very

low

support

and

maintenance

overhead.

Fax Machine Client:

This

store

‐

and

‐

forward

server

enables

any

SIP+T.38

ATA

device

or

IAD

to

send

and

receive

faxes

via

the

Port

Server.

Typically

this

will

be

installed

on

a

Windows

server

on

the

same

network

as

the

ATA

device(s).

FaxOut Client:

This

client

provides

a

virtual

printer

for

desktop

conversion

of

documents

and

attaches

them

to

email.

The

printer

driver

works

with

all

email

applications,

simply

using

the

system

default

mail

client.

SDK Client:

This

client

provides

a

powerful

API

for

software

developers

to

create

custom

fax

solutions.

The

Effects of Connected/Disconnected

Clients

Most

of

the

clients

(excluding

the

Outlook

Add

‐

in)

maintain

an

HTTPS

connection

to

the

Port

Server.

If

that

link

is

not

established

(the

client

isn’t

logged

in)

then

the

Port

Server

will

return

a

“busy”

(486

Busy

Here)

for

any

faxes

to

that

client’s

associated

DIDs.

(9)

Chapter

4 –

License Ke

ports

each

note

which

Connection

Installation

into

C:\NS

perform

th

Important

By

running

Setup

wiza

Setup

wiza

Server

>

Fa

The

welcom

provided.

B

features

th

–

Port Serve

ey:

Each

Port

Se

Port

Server

ca

h

Port

Server

is

n &

Port Ser

n from CD:

Ru

n from Downlo

SPortServer C

he

installation,

:

Do

not

attem

g

the

setup.exe

ard

will

run.

At

ard

is

canceled

ax

Hardware

Se

me

screen

is

w

By

entering

the

hat

will

be

unlo

er Installat

erver

installati

an

be

configure

s

using

which

k

rver

n

setup.exe

in

oad:

The

down

CD Image\.

Th

if

necessary.

R

mpt

to

install

fr

e

program,

the

this

point,

the

,

it

can

be

run

etup).

where

you

will

e

serial

numbe

ocked

by

the

se

ion

on

will

be

issu

ed

for,

as

well

key.

n

the

root

of

th

nloaded

EXE

is

directory

is

i

Run

setup.exe

om

a

network

Port

Server

fil

e

Port

Server

so

again

from

the

enter

your

Lice

er,

the

remaind

erial

number.

ed

an

individu

as

enabling

lic

he

CD

to

begin

a

self

‐

extracti

identical

to

the

e

from

this

dire

share.

Microso

les

will

be

insta

oftware

is

insta

e

Start

menu

(S

ense

Key.

Paste

der

of

the

insta

al

product

key

ensed

features

n

the

installatio

ng

archive.

Ru

e

official

CD,

an

ectory

to

begin

oft

.NET

securi

alled.

After

this

alled,

just

not

c

Start

>

All

Prog

e

or

type

this

s

allation

will

be

Fig

y.

This

key

cont

s.

Keep

this

ke

on.

n

it

to

extract

t

nd

can

be

burn

n

the

installatio

ity

settings

wil

s

is

complete,

configured.

If

t

grams

>

NET

Sa

server’s

License

customized

fo

gure 4‐1: Entering

trols

the

numb

y

in

a

safe

plac

the

installation

ned

onto

a

CD

on.

l

likely

prevent

the

Fax

Hardw

the

Fax

Hardw

atisFAXtion

Por

e

Key

in

the

fie

or

you

based

on

g the Server’s Lice

ber

of

ce

and

n

files

to

t

this.

ware

are

rt

eld

n

the

nse Key

(10)

The

Next.

The

configure

a

You

can

br

be

able

to

local

LAN

s

button

will

rem

creen

will

allow

a

SIP

Proxy

as

w

rowse

the

loca

discover

Audio

segment,

simp

main

grayed

ou

w

you

to

config

well

as

a

SIP

Re

l

LAN

segment

oCodes

and

Cis

ly

enter

its

hos

t

until

a

valid

P

gure

which

SIP

egistrar

here.

t

for

VoIP

Gate

sco

devices

on

stname

or

IP

ad

Product

Key

is

P+T.38

media

g

way

devices

by

the

same

loca

ddress

in

the

G

entered.

Once

gateway

this

Po

y

clicking

Brow

al

network.

If

th

Gateway

entry

Figure 4‐2 Figure 4‐3: Brows

e

you

have

ente

ort

Server

will

wse.

The

Brows

he

VoIP

Gatew

.

: Configuring the

sing the Local Sub

ered

the

key,

c

use.

You

may

a

se

feature

will

way

is

not

on

th

SIP+T.38 Media G

net for a Media G

click

also

only

he

Gateway Gateway

(11)

Next,

a

list

Certain

po

Next,

you

w

Proxy

and

installation

If

using

ho

resolvable

t

of

configured

rts

can

also

be

will

be

able

to

the

SQL

Serve

n

of

the

HTTPS

st

names

for

th

from

all

HTTPS

ports

is

displa

e

reserved

for

i

choose

if

this

r

is

also

config

proxy

and

SQL

he

Connection

S

proxies,

Conn

yed.

This

allow

nbound

or

out

installation

wi

ured

from

this

L

Server.

If

not

Server

or

the

nection

Server

ws

the

per

‐

port

tbound

traffic.

ll

be

a

Connect

s

screen.

Before

t,

this

screen

ca

Port

Server,

in

rs

and

Port

Ser

t

configuration

tion

Server,

a

P

e

continuing,

y

an

be

revisited

nsure

the

name

vers.

n

of

default

CSI

Figure 4‐4: Setting

Port

Server,

or

you

may

want

d

once

those

st

es

assigned

are

ID

and

dial

pre

g Individual Port S

both.

The

HTT

to

complete

th

teps

are

compl

e

valid

and

efix.

Settings

TPS

he

ete.

(12)

HTTPS

Prox

Check

the

path

to

https://sec

Once

ente

the

HTTPS

Databases

A

default

i

a

Microsof

There

are

f

•

SQ

•

RA

•

SQ

•

Ac

•

Ex

Most

insta

infrastruct

xy

“Http

‐

proxy

on

o

the

nsps

app

cure.netsatisfa

red,

you

will

se

Proxy.

nstallation

of

t

ft

SQL

Compac

five

supported

QL

ADIUS

QL

Compact

ccess/MDB

(M

xternal

Provide

llations

will

ut

ure.

n

IIS”

checkbox

lication.

The

d

axtion.com/nsp

ee

the

“Client

a

the

NET

SatisFA

t

database.

Th

d

database

type

Microsoft

JET);

n

er

DLL

ilize

SQL,

but

R

x

and

enter

the

efault

will

be

s

ps/nsps.aspx

access

Urls”

fo

AXtion

IP

Port

is

sufficient

es:

not

available

o

RADIUS

is

supp

e

fully

qualified

something

sim

or

the

Connecti

Server

will

sto

for

initial

testi

on

64

‐

bit.

ported

for

optio

Figur

d

domain

nam

ilar

to:

ion

Server

and

re

its

account

ng,

but

is

not

i

onal

integratio

re 4‐5: Configuring

e

of

your

IIS

se

d

Port

Server

ch

list

and

accoun

ntended

for

pr

on

with

existing

g Port Server Para

erver,

followed

hange

to

point

nting

informat

roduction

use.

g

AAA

ameters

d

by

to

ion

in

(13)

SQL

NET

SatisFA

billing

(NSP

Each

table

database,

Modify

eac

rights,

you

Your

instal

AXtion

Port

Se

PortServerBillin

may

be

indep

or

even

each

o

ch

entry

to

poi

can

allow

the

llation

of

this

P

erver

uses

the

d

ng).

endently

confi

on

a

completel

int

to

the

corre

Fax

Hardware

Port

Server

is

n

database

for

u

igured

and

nam

y

separate

dat

ect

SQL

Server

e

Setup

program

now

complete.

ser

authentica

med,

and

may

tabase

server.

and

configure

m

to

create

the

You

may

now

ation

and

fax

ro

reside

in

a

diff

authenticatio

e

required

tab

begin

testing.

outing

(NSPort

ferent

databas

Figure 4‐ Figure 4‐7:

n

as

needed.

If

les

and/or

dat

tServerMain),

a

e,

in

the

same

‐6: Port Server Da

SQL Database Pro

f

you

have

suff

abases.

and

tabases

operties

ficient

(14)

RADIUS

One

or

more

RADIUS

servers

may

be

specified.

The

Port

Server

will

use

RADIUS

calls

to

authenticate

users,

identify

ownership

of

DIDs,

and

for

call

logging

(CDRs).

Please

see

the

Port

Server

RADIUS

Support

document

for

more

information

about

implementing

RADIUS.

The

following

tables

may

be

implemented

with

RADIUS:

•

AccountsDb

•

ReceiveDb

•

BillingDb

Note

that

using

RADIUS

does

not

completely

remove

the

need

for

SQL.

The

following

tables

will

still

be

stored

in

SQL:

•

SndRoutingDb

•

ServersDb

External Provider DLL

An

external

DLL

may

be

specified,

which

the

Port

Server

will

call

to

authenticate

users,

identify

ownership

of

DIDs,

and

for

call

logging

(CDRs).

Please

refer

to

the

appropriate

documentation

to

develop

your

own

external

provider

DLL.

HTTPS

Proxy

In

order

to

provide

security

for

Internet

faxing,

NET

SatisFAXtion

IP

Port

Server

provides

an

ASP

application

that

proxies

communication

between

the

clients

and

the

Port

Server.

The

HTTPS

proxy

may

be

installed

on

an

IIS

server

either

running

on

the

Port

Server

itself,

or

on

a

separate

server.

When

using

an

HTTPS

proxy

server,

your

clients

will

be

connecting

to

a

URL

similar

to:

https://secure.netsatisfaxtion.com/nsps/nsps.aspx?target=conserv

Prior

to

installation,

the

Web

Site

you

are

using

must

have

an

SSL

certificate,

and

be

accessible

via

https.

It

is

advisable

to

require

SSL

communications.

For

using

self

‐

signed

SSL

certificates

for

testing,

please

see

Chapter

12

–

Testing,

Validation

&

Troubleshooting,

page

42.

Prerequisites

•

Microsoft

Internet

Information

Services

(IIS)

with

:

o

World

Wide

Web

Service

o

ASP.NET

support

•

ASP.NET

2.0

must

be

an

allowed

Web

Service

Extension.

Creating

the

nsps

Application

Server

installed,

copy

the

proxy

application

directory

from

the

Port

Server

server.

It

can

be

found

(by

default)

in

C:\Program

(15)

Open

IIS

Manager

and

locate

the

Default

Web

Site.

Right

‐

click

on

it

and

create

a

new

Virtual

Directory.

Its

Alias

will

be

“nsps”:

Next,

choose

the

directory

the

HTTPS

proxy

is

installed

in.

The

default

is

C:\Program Files\NSPortServer\Http Proxy\.

Allow

the

following

permissions:

Read,

Run

scripts

(such

as

ASP).

Finish

the

Wizard.

Next,

right

‐

click

on

the

nsps

virtual

directory

and

open

its

properties.

Next,

go

to

the

ASP.NET

tab

and

verify

the

ASP.NET

version

used

is

2.0.50727.

(16)

Next,

go

to

the

Virtual

buffering.”

Insure

ASP.NET

v2.0.50727

is

allowed

in

IIS.

Navigate

to

Web

Service

Extensions.

Select

ASP.NET

v2.0.50727

and

click

the

Allow

button.

(17)

It

may

be

n

C:\WINDOW

Configuring

If

the

proxy

Hardware

If

not,

the

…\NSPortS

necessary

to

m

WS\Microsoft.

g

the

HTTPS

y

is

installed

o

Setup

to

config

XML

file

will

ne

Server\Http P

manually

registe

.NET\Framewo

S

Proxy

Rout

n

the

same

ser

gure

the

routin

eed

to

be

edite

Proxy\Bin\IP

er

ASP.NET

2.0

ork\v2.0.5072

ting

Table

rver

as

NET

Sat

ng

table:

ed

manually.

It

PFSProxy.xml.

0

with

IIS.

Run

27\aspnet_re

tisFAXtion

IP

P

t

can

be

found

.

egiis.exe /i.

Port

Server,

you

in

.

u

may

use

the

Figure 4‐8: HT

GUI

within

Fax

TTPS Proxy Config

x

(18)

http://conserver.netsatisfaxtion.com:60/HttpService.api </Route>

http://portserver.netsatisfaxtion.com:61/HttpService.api </Route>

</RoutingTable> </IPFSProxy>

Simply

update

these

URLs

to

reflect

the

internal

names/IP

addresses

and

ports

of

the

Connection

Server

and

Port

Server.

These

names

need

only

be

resolvable

from

the

HTTPS

Proxy

server.

Note:

The

host

names

used

in

the

proxy

routing

table

must

match

exactly

the

host

names

and

port

numbers

specified

in

the

Port

Server

Setup

wizard.

If

they

do

not

match,

then

Setup

will

be

unable

to

identify

the

correct

Client

Access

URLs,

and

will

display

“***

UNABLE

TO

LOCATE

PROXY

URL!

***”.

For

example

if

the

routing

table

uses

“localhost:60”

in

the

Connection

Server

URL,

set

the

Connection

Server’s

Http

host

name

to

“localhost”

and

Port

number

to

“60”

as

well.

SQL Server

NET

SatisFAXtion

Port

Server

uses

the

Microsoft

.NET

Framework

Data

Provider

for

SQL

Server,

and

so

it

can

only

connect

to

Microsoft

SQL

Server

versions

7.0

or

newer.

Specifically,

SQL

Server

2000,

SQL

Server

2005,

Microsoft

Desktop

Engine

(MSDE),

and

SQL

Server

2005

Express

are

supported.

The

SQL

Server

may

be

installed

on

the

same

server

or

remotely.

NET

SatisFAXtion

Port

Server

can

use

an

existing

database,

and

has

simple

built

‐

in

methods

for

creating

the

databases

and

tables

as

needed.

SQL

Server

Remote

Connections

All

“on

site”

Connection

and

Port

Servers

will

need

to

connect

to

the

SQL

Server

because

it

is

used

to

store

most

configuration

information.

Insure

each

system

can

connect

to

the

SQL

Server

when

implementing

a

multiple

server

Port

Server

configuration.

SQL

Server

Security

and

Required

Permissions

NET

SatisFAXtion

Port

Server

can

use

either

SQL

Server

authentication

(username

and

password)

or

Windows

Authentication

(if

on

a

domain).

SQL

Server Authentication

The

simplest

authentication

method

is

SQL

Server

authentication.

Simply

create

a

login

on

the

SQL

Server

and

then

specify

this

login

and

password

in

the

Connection

Server’s

Hardware

Setup.

Windows Authentication

Windows

Authentication

may

be

used

when

both

NET

SatisFAXtion

Port

Server

and

the

SQL

Server

are

on

the

same

domain

or

if

there

is

sufficient

trust

between

them.

(19)

When

running

the

NET

SatisFAXtion

Port

Server’s

Fax

Hardware

Setup

program,

it

will

use

the

credentials

of

the

current

user

using

Windows

Authentication.

In

order

to

make

use

of

its

automatic

database

and

table

creation

features,

the

current

user

must

have

sufficient

permissions

on

the

SQL

Server

(e.g.

a

member

of

the

Domain

Admins

group).

NET

SatisFAXtion

Port

Server

will

run

as

the

SYSTEM

account.

This

is

important

because

if

a

remote

SQL

Server

is

in

use,

it

will

refuse

the

Connection

Server

by

default.

Be

sure

to

create

a

login

for

the

DOMAIN\SERVERNAME$

account

on

the

SQL

Server

and

give

it

permissions

(listed

below

under

“running

permissions”)

to

the

NSPortServerMain

and

NSPortServerBilling

databases

or

equivalents.

Both

the

Connection

Server

module

and

the

Port

Server

module(s)

require

a

database

connection

so

each

server

used

must

have

SQL

permissions.

Setup Permissions

The

account

used

when

running

the

NET

SatisFAXtion

Port

Server’s

Fax

Hardware

Setup

program

must

have

the

following

permissions:

Create Databases:

Grant

server

‐

wide

“Create

any

database”

permissio