SwyxWare Hosted Solution · PDF fileWhilst Swyx attempt to convey accurate and current...

SwyxWare Hosted Solution

Hosted IP-PBX Solution

As of: September 2008

n of SwyxWare and this documentation, the information provi-

thout any warranty of any kind, whether expressed or implied, a particular purpose or non-infringement.

istered trademarks of Swyx. All other trademarks and productntation is proprietary intellectual property of Swyx. Reproduc-t of Swyx is prohibited and will be prosecuted as a violation of

© 2000-2008 Swyx. All rights reserved.

Legal information

Whilst Swyx attempt to convey accurate and current information relative to the creatioded in this user guide may contain typographical or technical errors.

This documentation, including all information contained herein is provided „as is“, wiincluding, but not restricted to, any implied warranties of merchantability or fitness for

Trademark: Swyx, SwyxIt!, the integration smiley and „Click. Phone. Smile.“ are regnames are trademarks or registered trademarks of the respective owners. This documetion, adaptation, or translation of this documentation without the express written consenintellectual property rights.

Swyx Solutions AG

Joseph-von-Fraunhofer-Str. 13a

D-44227 Dortmund

www.swyx.com

http://www.swyx.com

2 The Basics

2.1 Hosted SwyxWare in Detail................................................... 11

ements

and Software Requirements ................................. 14k End Server (BES) Requirements ................................... 14

quirements for separated SwyxGate................................... 15quirements for Front End Server (FES) ............................... 15quirements of a virtual PBX.............................................. 16tabase System Requirements........................................... 16twork Card(s) ............................................................... 17

............................................................................... 17

Requirements and Bandwidth ................................. 18ating an Appropriate Network Environment for SwyxServer ..... 18

er for Voicemail ...................................................... 19

Exchange Server for Call Management ................. 19

mino Server for Call Management .......................... 19

............................................................................... 21

nts of Hosted SwyxWare ....................................... 21

............................................................................... 23

of a Number Plan .................................................... 24

er ............................................................................ 24

n of a separated database ..................................... 25

n of a licensing server (back end server) ............... 25

5.6 Installation of SwyxWare Administration ............................... 26

5.7 Configuration of a back end server (BES)............................. 26

n of a front end server (FES).................................. 27tallation of Virtuozzo....................................................... 27ation of the clone template for a virtual PBX ........................ 27

of a customer installation ........................................ 29

tion of a customer installation by the provider........ 31

2.1.1 Front End Server .............................................................. 122.1.2 Back End Server .............................................................. 122.1.3 Hosted SwyxWare database................................................ 132.1.4 Cold Standby Server ......................................................... 13

5.8 Installatio5.8.1 Ins

5.8.2 Cre

5.9 Creation

5.10 Configura

New Functions......................................................................................... 3

Introduction ............................................................................................. 6

1 What is meant by…?

1.1 Hosted SwyxWare................................................................... 8

1.2 Hosted SwyxWare Server (SwyxServer) ................................ 8

1.3 Front End Server (FES) .......................................................... 8

1.4 Database Server ..................................................................... 8

1.5 Back End Server (BES)........................................................... 8

1.6 Provider (Serviceprovider) ...................................................... 8

1.7 SoftSwitch ............................................................................... 9

1.8 Customer................................................................................. 9

1.9 User......................................................................................... 9

1.10 Virtual telephone system (V-PBX)........................................... 9

1.11 Virtuozzo ................................................................................. 9

1.12 Virtual Environment (VE)......................................................... 9

1.13 Licensing Server ..................................................................... 9

1.14 Location................................................................................... 9

1.15 Feature Profile......................................................................... 9

1.16 Reporting............................................................................... 10

1.17 Cold Standby Server ............................................................. 10

1.18 Administration profiles ........................................................... 10

1.19 Trunk and Trunk Groups ....................................................... 10

3 System Requir

3.1 Hardware3.1.1 Bac

3.1.2 Re

3.1.3 Re

3.1.4 Re

3.1.5 Da

3.1.6 Ne

3.2 Virtuozzo

3.3 Network 3.3.1 Cre

3.4 Mail Serv

3.5 Microsoft

3.6 Lotus Do

4 Scenario

4.1 Overview

4.2 Compone

5 Installation

5.1 Overview

5.2 Concept

5.3 Mail Serv

5.4 Installatio

5.5 Installatio

5.11 Configuration of a customer installation by the reseller ........ 32

5.12 Configuration of a customer installation by the customer ..... 33

5.13 Installation of the SwyxWare Web Administration................. 34

5.14 Installation of SwyxFax ......................................................... 345.14.1 Backup of a SwyxFax Server installation................................. 34

5.15 Update of the Virtuozzo environment .................................... 35

5.16 Update of an existing Hosted SwyxWare scenario ............... 35

6 Administration

6.1 Administration profiles ........................................................... 376.1.1 Administration profiles in the Standard Installation ..................... 386.1.2 Overview of the various administrator levels ............................ 39

6.2 Further Functions of Administration ...................................... 406.2.1 Bulk Administration ........................................................... 406.2.2 Reproduction of elements in Administration (Cloning)................. 40

6.3 Number of simultaneous connections ................................... 41

6.4 Feature Profiles..................................................................... 41

7 Licenses

7.1 Licenses ................................................................................ 43

7.2 Reporting............................................................................... 437.2.1 What is entered in Reporting? .............................................. 44

7.3 Logging of invoice-relevant activities on SwyxServer .......... 47

Index....................................................................................................... 48

> New Functions3

SwyxWare Administrator documentation.

zo 4.0 as virtualization platform for SwyxWare Essential

an be installed on a virtual platform (Virtuozzo). However, apermanent.

tandard Skin definable for all users

ion, the system-wide Standard Skin is specified as the skin forer, if the administrator has not provided otherwise.

an update to Version 6.20, it is checked whether the user usesaClassicXT, LoonaClassic or BlueLineClassic). In this case iter should use the system-wide Standard Skin. Thus after theadministrator changes the system-wide Standard Skin, the skinese users. All other configured skins will still be transferred

ler List entry for forwarded calls

xIt! and SwyxPhone is expanded so that for forwarded calls,be seen about the users involved.

ient, who forwarded the call to him/her, and the number of ther with whom he/she then spoke.

rder, the number of the original caller, and the person to whom this call.

g SwyxWare user, the final conversation partner.

n, please refer to the SwyxIt! documentation.

button for SwyxIt!

It is now possible in the user properties to select a line button, which is then alwaysused for outgoing calls if the user has not explicitly chosen a different line.

d line was chosen. This standard line is also used for calls thator Client SDK applications.

bsite

SwyxIt! to check whether a newer version is available forer can download and install the new client, provided he has the

Enhancement of the Swyx Trace Tool

Starting with this version, the trace files are compressed. Also, the SwyxWareconfiguration files and the network configuration are added to the trace files.

For further information, please refer to the SwyxWare Administrator documentation.

Previously, the last useare initiated via TAPI

Link to the we

It is now possible indownload. If so, the uscorresponding rights.

New FunctionsNew and Improved Functions in SwyxWare

Additional functions and increased flexibility and user-friendliness are typicalfeatures of every new version of SwyxWare, making SwyxWare one of the mostadvanced IP telephone systems on the market. The complete IP architecture andextensive range of functions have made SwyxWare the system of choice for morethan 4000 SMBs throughout Europe.

The main changes in Hosted SwyxWare will be listed below: You will find acomplete overview about the changes between the versions in the SwyxWareAdministrator Documentation.

• SwyxWare V6.20 - New Functions

Support of the new telephone family SwyxPhone L6xx

With this version, the phones SwyxPhone L620, SwyxPhone L640 , SwyxPhoneL660 and SwyxPhone L680 are offered along with the associated key modules. ThePhoneManager has been redesigned to support these. The 'PhoneController' service,which was formerly installed with SwyxServer, lapses from this version on. NewSwyxPhone firmware for the existing SwyxPhone L4xx/L5xx is unnecessary.

AD (Active Directory) support for the SwyxWareuser configuration

To import users that are already present in Windows administration into SwyxWare,there is the User Import Assistant. For further information, please refer to theSwyxWare Administrator documentation.

If new Windows users are created or existing ones removed, then from this versionthe creation / deletion of the associated SwyxWare user is also integrated via a furthertab in the user Windows properties. For further information, please refer to the

Use of Virtuoz

SwyxWare Essential cclone cannot be made

System-wide S

Starting with this verseach newly created us

For existing users or ina Standard Skin (Loonis assumed that the usupdate to v6.20, if the also changes for all thunchanged.

SwyxIt!

Additional Cal

The caller list in Swymore information can

In detail, it shows

• for the reciporiginal calle

• for the forwahe forwarded

• for the callin

For further informatio

Standard line

> New Functions4

SwyxIt! Mobile

n, please refer to the SwyxMobile documentation.

her operating systems

ersion, Windows Mobile 6.1 Professional is additionally

vior of SwyxIt! Mobile

It! Mobile has been improved in a few points:

e exceptions list can now be created simply by export of entriessting contacts.

n of SwyxIt! Mobile via a URL

bile can also be configured until now by import of a configura-rting with this version, it is possible to reference this file via a

bile (for dialing

avior for MEM usage 'On demand'

irect from the SwyxIt! Mobile interface, it is assumed that thego via the MobileExtensionManager. The parameter "MEM demand') only leads to a query if a number is dialed outsidebile.

es back end server

ls are set up between the front end servers and the back endble payments in Reporting, the channels of a back end serverpayment.

nism identifies a system with fewer than two configured users,s a back end system. In this case users, fax channels and voiceed.

Dual Mode support for SwyxIt! Mobile (Symbian)

Within a WLAN area it is possible to register directly on SwyxServer with a mobileterminal device as a SIP terminal device. It is thereby possible e.g. to log on with amobile phone both via SIP and via GSM (dual mode). The new version supports acall set-up via SIP, provided the user is in the WLAN area. If no WLAN or SIPregistration is present, the call is set up via GSM.

Skin preview

The skin can be changed in SwyxIt! and in the SwyxWare Administration. Startingwith this version, a preview of the selected skin is displayed when a skin is selectedin the drop-down list on the "Skin" tab.

Hosted SwyxWare

Use of Virtuozzo 4.0 as virtualization platform for Hosted SwyxWare

Virtuozzo 4.0 is the successor version to Virtuozzo 3.5.1. Hosted SwyxWare can beinstalled on Virtuozzo 4.0 and then cloned, as previously in Virtuozzo version 3.5.1.

An existing Hosted SwyxWare installation on Virtuozzo 3.5.1 can equally be updatedwith Virtuozzo 4.0.

Logging of invoice-relevant activities on SwyxServer

All changes of parameters that are entered in Reporting, and thus are relevant forbilling, are logged. The log contains the time of the change, the old and newparameter values, and the user making the change. The log file can be displayed inSwyxWare Administration or exported. For further information please refer tochapter 7.3, Logging of invoice-relevant activities on SwyxServer, page 47.

Feature profile "Deactivated" in Hosted SwyxWare

In some SwyxIt! scenarios there are users who only use their SwyxIt! access a fewdays in the year. These users can now be assigned the profile "Deactivated" duringtheir absence. Their entire configuration (announcements, scripts) is then preserved,but is no longer entered in Reporting.

If this profile is assigned to a user, then call routing rules are likewiseinactive for this user.

For further information please refer Feature profile 'Deactivated', page 46.


Support of furt

Starting with this vsupported.

Improved beha

The behavior of Swyx

• Entries in thfrom the exi

• Configuratio

SwyxIt! Motion file. Stalink (URL).

• SwyxIt! Mo

• Changed beh

For dialing dcall should usage (='OnSwyxIt! Mo

License chang

Voice and fax channeserver. To prevent douare excluded from the

If the Reporting mechathen it interprets this achannels are not count

> New Functions5

SwyxWare V6.12 - SwyxIt! Mobile Changes/EnhancementsThe functional range of the mobile phone client has been expanded: it is now

f settings with a password

e native calendar

uring of the SwyxIt! Mobile settings

onfiguration by configuration file

acement

aker / microphone

V6.12 - SwyxIt! Changesew functions in this version.

stems - 64-bit support

for SwyxPhone S315(SwyxIt! Dialer)

senger

b Extension

n, please refer to the SwyxIt! documentation.

V6.12 - Hardwareards are supported from this version on:

QuadBRI

SinglePRI

DualPRI

ISDN cards supplement the proven SX2 ISDN cards in the

available for a further operating system (RIM). Further information about thechanges and improvements you will find in the SwyxWare Administrator Manual.

• Direct calls without using the MobileExtensionManager

• Pickup of an active call with the office phone

• Sending of a DTMF string

• Right selection key configurable

• SwyxWare V6.12 - New FunctionsThe changes for this version are concentrated on telephony clients (SwyxIt! andSwyxIt! Mobile). Minor changes were made in the licensing model for HostedSwyxWare, and the Voicemail and Faxmail have been improved.

License changes back end server

Voice and fax channels are set up between the front end servers and the back endserver. To prevent double payments in Reporting, the channels of a back end serverare excluded from the payment.

If the Reporting mechanism identifies a system with fewer than two configured users,then it interprets this as a back end system. In this case users, fax channels and voicechannels are not counted.

For further information please refer Licensing and reporting of the back endserverThe back end server puts the fax and voice channels into the outside world andmanages the licenses. Typically, no users are created on such a back end server. Inorder that the voice and fax channels are not entered in duplicate in the reporting, aSwyxServer that has no more than one user is not recorded in reporting., page 46.

Changes for Voicemails

Voicemails sent as e-mail attachments now contain the number or name of the callerin the filename. The subject line of the e-mail also contains this information, alongwith the length of the recorded voicemail.

In the e-mail, you will find a link with which you can access the relevant voicemaildirectly by remote inquiry.

Changes for Faxmails

The name of the faxmail attachment (TIF or PDF) now contains the date/time, stationID, name and Caller ID.

• Protection o

• Access to th

• Better struct

• Automated c

• Number repl

• Activate spe

SwyxWareSwyxIt! offers a few n

• Operating sy

• Dialer Mode

• SwyxIt! Mes

• SwyxIt! We


SwyxWareThe following ISDN c

• SX2-express

• SX2-express

• SX2-express

The new SX2-expressSwyx portfolio.

> Introduction6

With a SwyxWare installation in your network, the fusion of computer and telephoneis quick and easy: for the first time, users are provided with really intelligent andintegrated telephone functions on their workstations. These cover everything from

m those of someone who needs to phone a lot. Users in a need a different kind of PC/telephone support thaned Sales staff. The future-proof Swyx telephone solutions takef requirements and needs into account. Thus - in addition to

rom the numerous user interfaces which are supplied - the userephone is presented, including how many and which buttons itormation is displayed, which ring tones or melodies are usednouncements should be played under which circumstances, to

view of the many functions supported when using SwyxIt! asr your SwyxServer in the SwyxIt! documentation.

Image ii-1 Example

fectiveness Through ‘Voice over IP’

one application is a pure software solution. It is thus easy toinstall, easy to administer and easy to extend. This saves money and it is very simple.Furthermore, the use of Voice over IP technology also means considerable costsavings: moving, deleting or adding subscribers has now become a matter of one or

is all done without specialist maintenance staff.

ails and advice on the efficient use of SwyxWare, interestingand tricks for the operation of more complexSwyxWarein this manual but also on theSwyx Internet pages at:

.

Caller ID and selection help at the click of the mouse, to sophisticated support forMicrosoft Office products and even Unified Messaging.

Flexibility Through Individual PC/Telephone Support

Telephony with SwyxWare can be arranged entirely according to the user's personaltaste and the desired workstation support - especially elegantly with the PC telephonyclient SwyxIt!. The requirements of a user who only uses the telephone occasionally

two mouse clicks, and

You'll find further detuse cases and tips installations, not only

http://www.swyx.com

IntroductionSwyx develops and markets powerful solutions for company telephony. The"SwyxWare" telephone system is practically a pure software solution, using theexisting standard PC platform: telephony thus becomes a network application likeyour e-mail system, your ERP system for company data management, or your CRMsystem for management of your customer and prospects database.

What is SwyxWare?The Swyx solution is software which, with the operating system Microsoft WindowsServer 2003, turns your PC into a high-performance and user-friendly telephonesystem. This telephone system can grow almost seamlessly from a few telephonesubscribers to company sizes of around 1000 subscribers.

SwyxWare here offers a previously unknown flexibility and capability for itstelephone users, who can choose freely between a wide variety of telephoneterminals: as in classic systems, a family of elegant system telephones("SwyxPhones") and various equipment features are available, but it is additionallypossible to connect other manufacturers' IP telephones which conform to thestandard, if the efficiency of the terminal devices is not the most important criterionfor the selection.

However, a completely new dimension opens up with the PC-based "SwyxIt!"telephony software, which converts any Windows PC into a telephone ofunprecedented capability, user-friendliness and flexibility. For each user a handset ora headset is selected, typically connected to the PC via the USB port, and the userthen has the most powerful telephone solution integrated directly into hisworkstation.

Perfect Integration into the ‘Microsoft world’

are very different froLogistics departmentcommunication-orientthese different kinds obeing able to choose fcan decide how his telshould have, what infand when, or which anwhich of his callers.

You will find an overterminal equipment fo

Unbeatable Ef

The SwyxWare teleph

http://www.swyx.com

> Introduction7

properties of Hosted SwyxWare which are needed for a hosted application.

Area of application of Hosted SwyxWare

Initial installation and configuration of Hosted SwyxWare

Administration of Hosted SwyxWare

Licensing and billing procedure

e Index provides you with an orientation resource which willd topics quickly.

formation time necessary for creating printed documentation, this

always current for the software. Therefore, you will find here:

nformation on the products, please see our Internet homepage:

wyx.com

estions concerning the current version are answered in the on the SwyxWare CD.

, in the Support database (Knowledgebase), you will findformation regarding special installation scenarios as well as for the optimal implementation of your SwyxWare.

wyx.com/support/support-kb.html

upport’ category of the homepage, you can download the moston of the documentation (PDF) and software updates:

wyx.com/support/index.html.

The Layout and Organization of this Documentation• Chapter 1 - Definition and explanation of special terms used in this

documentation.

• Chapter 2 - Requirements for operating Hosted SwyxWare

• Chapter 3 - Hardware, software, and network requirements, in addition tothe license conditions

Support from SwyxSwyx offers a comprehensive range of initial services provided by a team ofspecialists in the context of Hosted SwyxWare. This so called "Jump Start Package"enables providers to implement the services Hosted SwyxWare offers in a quick,efficient and professional way. The solutions contained in the "Jump Start Package"facilitate a smooth implementation of Hosted SwyxWare at the provider. Thisincludes the setup of call termination or the connection of clients, and furthermorethe adaptation of internal processes for the provider and the technical training ofstaff.

The "Jump Start package" enables Providers to minimize the risks associated with anew line of business, and to benefit from the experience of Swyx Solutions AG. Inaddition, corresponding service contracts for maintaining existing installations areavailable. For further information, please contact Swyx Sales or send an E-mail [email protected].

About this DocumentationThis documentation contains the information necessary for making the most effectiveuse of the Swyx solution and the advantages it provides.

Who is this documentation written for?

The documentation assumes that you, as system administrator, know the platformsused and their conventions.

Accordingly, a detailed description of Windows menu calls, for example, is notincluded with this documentation, and adequate basic knowledge of networkadministration is assumed.

A knowledge of the SwyxWare solution is also assumed, relating to installation aswell as configuration. For further information, please refer to the SwyxWareAdministrator documentation. This documentation deals only with the specific

• Chapter 4 -

• Chapter 5 -

• Chapter 6 -

• Chapter 7 -

• The extensivhelp you fin

Additional InGiven the processingdocumentation is notadditional information

• For current i

http://www.s

• Detailed qu‘readme’ file

• Furthermoreadditional intips & tricks

http://www.s

• Under the ‘Scurrent versi

http://www.s

http://www.swyx.com/de

http://www.swyx.com/de/support/support-kb.html

http://www.swyx.com/de/support/index.html

> What is meant by…?8

1.3 Front End Server (FES)Front end server refers to a computer on which several virtual instances are set up

rver a PC (or cluster of PCs) with Windows 2003 servers, on whichtabase is installed. We always recommend using a cluster, to failure safety. This shared database contains all data of thers. Each SwyxServer finds its users and their profiles here,t scripts. The reporting of the number of users set up, and theirrs directly from this database.

n please refer Hosted SwyxWare database, page 13.

rver (BES)rs to a computer which handles the connections to otherted SwyxWare. A back end server within a Hosted SwyxWare

he licensing and monitoring of the front end servers, and therver).

can be installed here on the PCs with Windows 2003 servers:

r the connection to the PSTN (ISDN or analog)

anager for SIP connections e.g. to other providers or to awhich then offer access to the public telephone network

ervice (on the licensing server) for the daily recording ofrs and feature profiles, and for sending the monthly reports

le to use several PCs here, according to requirements. Thers then use this functionality within the scope of the purchased

n please refer Back End Server, page 12.

1.6 Provider (Serviceprovider)A provider (hoster, service provider) offers accesses to the Internet. In this case the

ctor, who has an installation of Hosted SwyxWare and offerser companies) these telephony services.

with Windows 2003 servers (VEs). A SwyxServer (Hosted SwyxWare server) isinstalled on each of these virtual instances. For further information please refer FrontEnd Server, page 12.

provider is the contracustomers (usually oth

1 What is meant by…?Definition and explanation of special terms used in this documentation.

This chapter describes in detail the terminology commonly used throughout thisdocumentation. Knowledge of the SwyxWare documentation is assumed.

1.1 Hosted SwyxWareSoftware installation that covers the complete installation of SwyxWare. Thisincludes the installation at the service provider as well as the installation of thetelephony clients (SwyxIt! or SwyxPhone) at the customer.

The provider sets up the database, the front end servers and the back end servers. Theprovider is thus responsible for the interfaces to other networks, e.g. to the PSTN orto other providers.

Depending on the sales model of the provider the provider himself or theadministrator of the customer can create and configure the telephone users.

The supplied telephony services are invoiced with detailed reporting.

1.2 Hosted SwyxWare Server (SwyxServer)In a service provider's environment this is the equivalent of a SwyxServer. ThisSwyxServer is installed in a virtual environment (VE) with Windows 2003 server asoperating system, and offers the provider's customers the functionality of a telephonysystem.

For further information about hard and software please refer to the chapter 3.1,Hardware and Software Requirements, page 14.

1.4 Database SeThe database server isthe Microsoft SQL daensure the appropriateindividual SwyxServealong with the relevanfunctional range, occu


1.5 Back End SeBack end server refenetworks within a Hosinstallation takes on treporting (licensing se

The following services

• SwyxGate fo

• SwyxLinkMSoftSwitch,

• Reporting sinstalled use

It is naturally possibindividual SwyxServechannel licenses.



1.10 Virtual telephone system (V-PBX)V-PBX denotes a virtual telephone system. This is implemented with HostedSwyxWare as a SwyxServer, which is installed at the provider on a virtual instance

te SwyxServer installation. Virtuozzo is a product of Parallelsom).

onment (VE)denotes an isolated (Windows) server instance, implementedtance behaves like a stand-alone PC. A customer thus has anX, but without using separate PC hardware for each server.

rverck end servers within a Hosted SwyxWare installation, one of

cense administrator. The Hosted SwyxWare license is input, orhis licensing server. The reporting service is activated on thisdatabase is also only needed for this server. All other back endeference this licensing server for licensing.

ively a property of the telephone system. Call numbers ares property, e.g. a call into the local network is thereby

Server has the property:

England (code 44),

Luton (prefix 231)

now dials a number e.g.9345678 (’9’ as public line access),ognized as a local number and the number +44231345678 is

dialed. This configured location is naturally independent of where theprovider's PC actually physically is.

ile be made available to each user: the use of the Call Routingity of receiving voicemail or recording calls. These functionsofile. An individual user's functional range can be expanded

(VE) and is exclusively available to the customer.

1.11 VirtuozzoVirtuozzo is the software that supplies multiple isolated virtual environments (VE) ona single physical PC. This means that each of the provider's customers can be

1.15 Feature ProfVarious functions canManager, the possibilare combined in a pr

1.7 SoftSwitchThe SoftSwitch is a system that the provider uses to receive the calls via SIP(LinkManager) from the back end server and route them into the public telephonenetwork (PSTN).

1.8 CustomerCustomers of a provider can be companies as well as persons with a single line. Inthis case the customer uses the telephony services of the provider in the form of avirtual telephone system (V-PBX).

1.9 UserA user is a person, a group or a location (for example, a conference room), for whom/which an account has been set up on the SwyxServer. Each account on SwyxServer isassigned a user name and a PIN (Personal Identification Number). The PIN isrequired for user authentication when using the SwyxPhone and for remote inquiry.

When SwyxIt! is started your access authorization is automatically checked and youruser account on SwyxServer is recognized. If SwyxServer does not find aSwyxServer account for your user login, then SwyxIt! will be exited and an errormessage will appear. If several SwyxServer accounts exist for your user account, youwill be prompted by SwyxIt! to choose one of these accounts.

Each user’s individual settings are stored centrally (for example, entries in a personaltelephone book, forwarding definitions, or the assignment of extension numbers tolines). This means that you will always find the same telephone environment,whichever PC or SwyxPhone you logon to!

supplied with a separa(http://www.parallels.c

1.12 Virtual Envir'Virtual Environment' by Virtuozzo. This insexclusive server as PB

1.13 Licensing SeIf there are multiple bathese servers acts as limade permanent, on tserver, i.e. a reporting and front end servers r

1.14 LocationThe location is effectinterpreted using thirecognized.

Example:

The Swyx

If the userthis is rec

http://www.parallels.com/


1.19 Trunk and Trunk Groups"Trunk" denotes a connection into another network, e.g. the public telephone

o the Internet). If this is not available, a lower-priority path isrunk to the normal telephone network.

n, please refer to the SwyxWare Administrator documentation.

network. A connection to another network can be e.g. an "ISDN trunk", a connectionto the Internet an "SIP trunk". Connections (trunks) of the same type can becombined to form groups. The trunks of a trunk group then have the same properties- the trunk groups can therefore be seen primarily as capacity expansions.

Different trunk groups can be differently prioritized by the administrator. The resultis e.g. that calls are handled with preference given to a cost-efficient connection (e.g.

quickly and easily at any time, by assigning him a different profile. The assignedprofiles are used in reporting as the basis for the recording of the functions used.

If there is a functionality in the feature profile which should not be used by the userhimself will be deactivated by the user administrator.

For further information please refer to chapter 6.4, Feature Profiles, page 41.

1.16 ReportingReporting denotes the reporting procedure for the current user numbers and theirfunctional range. This reporting procedure serves for continuous licensing and therelated invoicing.

For further information please refer to chapter 7.2, Reporting, page 43.

1.17 Cold Standby ServerCold Standby Server denotes a server on which multiple virtual environments (VE)are already preinstalled. This server can be started if one of the current installed frontend servers fails. The SwyxServers of the virtual enviroments obtain the necessaryuser data for operation from the database.

For further information please refer Cold Standby Server, page 13.

1.18 Administration profilesAn administration profile is assigned to each user. These profiles define which areasa user can look at and change. You can choose from a variety of profiles:

For further information please refer to chapter 6.1, Administration profiles, page 37.

an SIP trunk directly tchosen, e.g. an ISDN t


> The Basics11

facilitate a smooth implementation of Hosted SwyxWare at the provider. Thisincludes the setup of call termination or the connection of clients, and furthermore

xWare in Detailsted SwyxWare contains several server installations. The heartare is the BackEnd server, which manages the license and

ons to the public network (ISDN, SIP). In a big installation one BackEnd-Server and also separated additional gateways.

e the license server on which the reporting service is installede may be several FrontEnd server, on which some virtuallled on using Virtuozzo. Each of these virtual instances is aomer. The data of the customer installation will be managed inted server.

below form the basis of a Hosted SwyxWare installation. Suchxpanded according to the requirements.

the adaptation of internal processes for the provider and the technical training ofstaff.

The "Jump Start package" enables Providers to minimize the risks associated with anew line of business, and to benefit from the experience of Swyx Solutions AG. Inaddition, corresponding service contracts for maintaining existing installations areavailable. For further information, please contact Swyx Sales or send an E-mail [email protected].

2 The BasicsRequirements for operating Hosted SwyxWare

Hosted SwyxWare is a client-capable software package of the well-known andproven telephony application SwyxWare.

Please refer to the relevant SwyxWare administrator documentation for details of theinstallation, configuration and operation of SwyxWare.

Knowledge of the installation and configuration of SwyxWare is assumedin the following. For further information, please refer to the SwyxWareAdministrator documentation.

Hosted SwyxWare is based on this Swyx technology, and now enables providers tooffer their customers optimally scaled telephony services. The telephony serverremains with the provider, who installs it and configures it according to thecustomer's wishes. The customer installs only the telephony clients, either as SwyxIt!on the employees' PCs or as stand-alone IP telephones, e.g. from the SwyxPhonefamily. If the customer wishes, his system administrator can also be allowed tomaintain his own telephony server. SwyxWare offers the option of administration atvarious levels.

The telephony services are invoiced using a reporting system, which takes intoaccount the functional range permitted for the individual users of SwyxWare. Eachuser's scope for use is defined by the provider or by the reseller, with the help of so-called features profiles (see chapter 6.4, Feature Profiles). For further informationplease refer to chapter 7.2, Reporting, page 43.

Swyx offers a comprehensive range of initial services provided by a team ofspecialists in the context of Hosted SwyxWare. This so called "Jump Start Package"enables providers to implement the services Hosted SwyxWare offers in a quick,efficient and professional way. The solutions contained in the "Jump Start Package"

2.1 Hosted SwyThe installation of Hoof the Hosted SwyxWprovides the connectithere can be more thanOnly one server can bon. Additionally therinstances can be instavirtual PBX for a custa database on a separa

The components listedan installation can be e

> The Basics12

verozzo, several SwyxServers are installed on this PC with the

dows 2003 Server x64-bit edition. Each of these SwyxServerssively for one customer, who can reach it via IP.

our virtual environments are to be operated on one system,Data Center Edition must be used.

connected via a further network card to the internal network,server is also available.

rvers has its own SwyxGate. To establish the connection to thef these SwyxServer is connected via a SwyxLink trunk to the manages the connections to the outside world. The number ofk trunk also defines the number of simultaneous outside callsake.

ilization of a PC, a further front end server with further can be added to the existing ones.

vere Hosted SwyxWare is installed directly on this PC with thedows 2003 Server. The main task of this server is to establisheen the virtual telecommunications systems (customerutside world. This server accordingly hosts

SwyxGates for the connection to the public telephone networks or analog trunks). SwyxGates can be installed on one or - for or failure safety reasons - on multiple physical PCs withg ISDN or analog cards.

ger, which establishes SIP connections e.g. to other providersor directly (SIP trunks). The connection to a SoftSwitch of the provider isalso managed here.

If only one back end server is present in an installation, it handles both the connectiond the licensing server function.

Image 2-1 Minimum Scenario for Hosted SwyxWareto the outside world an

2.1.1 Front End SerWith the help of Virtuoperating system Winis a virtual PBX exclu

If more than fthe Microsoft

The front end server isin which the database

None of these SwyxSeoutside world, each oback end server, whichchannels per SwyxLincustomer's staff can m

Depending on the utSwyxServer instances

2.1.2 Back End SerThe SwyxServer of thoperating system Winthe connection betwSwyxServer) and the o

• one or more(ISDN trunkperformancecorrespondin

• a LinkMana

> The Basics13

If a front end server fails, it is replaced by the administrator with the cold standbyserver. The names and the connection to the relevant database are configured for
these SwyxServer instances with a configuration program (IpPbxConfig). These newinstances can then connect to the database and are once again operational with allinformation relating to the respective customer, since this customer information iscentrally stored in the database.
Licensing ServerThe license server will be installed on a BackEnd server. It manages the HostedSwyxWare license, and licenses all other servers within the Hosted SwyxWareinstallation. The reporting service, which prepares a report about the configuredusers, the associated feature profiles and the server configuration at appropriate timeintervals, is active on the licensing server. For the report preparation, all installeddatabases of the Hosted SwyxWare are evaluated daily, and the results are stored in areporting database. The reporting service then extracts the information from thisreporting database. This service must be activated at all times within the HostedSwyxWare.

For further information please refer to chapter 7, Licenses, page 43.

2.1.3 Hosted SwyxWare databaseOn this central server, which cannot be seen from the customer side, a Microsoft SQLServer 2005 is installed. This server manages all databases of the installed front endservers and provides the database for the report information.

Swyx recommends the use of a cluster system on redundancy grounds, to ensure thenecessary failure safety for the SQL databases.

2.1.4 Cold Standby ServerThis server should act as a substitute for a failed front end server. A Windows Serveroperating system and Virtuozzo are already preinstalled on the cold standby server.The necessary SwyxServer instances are created (cloned) in the VirtuozzoManagement Console with the help of the prepared template on the cold standbyserver. These virtual instances have not yet been assigned names or databases.

The cold standby server does not use the SwyxWare standby functionalityas this always relates to exactly one SwyxServer and thus cannot be usedfor a front end server with multiple SwyxServer instances.

> System Requirements14

updates provided by Microsoft on a regular basis:

http://windowsupdate.microsoft.com

abase, and therefore do not add to the SwyxServer memory

for SwyxFaxFax within the installation, the provider or his SIP interface toetwork must support the T.38 protocol.

ver (BES) Requirementsstablishes the connection between the individual virtual PBXs The limiting factor is the management of the configured voice

re configured on this server. Please refer to Licensing andnd serverThe back end server puts the fax and voice channels

and manages the licenses. Typically, no users are created onr. In order that the voice and fax channels are not entered inrting, a SwyxServer that has no more than one user is not, page 46 for further information on special licensing of a back

Requirements

Dual Xeon Dual Core 3.2 GHz

4 GB for 400 voice channels via SIP or 76 channels via ISDN

rver 130 MBCorresponds to the installation of 'normal' SwyxWare

30 MB

acing If you want to save trace outputs to the hard disk during operation, further disk space has to be provided for this.

Memory space in the 60 MB

100 MBit

• Windows Server 2003 x64 bit• all available operating system updates• Microsoft .Net Framework 2.0• WSE 3.0 Runtime

Hard Drive Memory and File System for SwyxWareA complete SwyxWare installation needs around 130MB disk space (80MB in theprogram directory and 50MB in the "Documents and Settings" directory). The filesassigned to the users, such as their own call routing scripts, voicemailannouncements, bitmap files, ringing tones or skins, are stored with Hosted

database

Network Adapter

Software

3 System RequirementsHardware, software, and network requirements, in addition to the license conditions

Please note that the following hardware requirements apply only to aHosted SwyxWare installation. If you want to run other processes on thisPC, such as a file server application, the hardware requirements aredifferent.

3.1 Hardware and Software RequirementsIt is only possible to give examples of hardware requirements here. They are verymuch dependent on the number of SwyxServer instances on a front end server, thecalls to be handled simultaneously, and the extent of the script editing.

A hardware scenario is presented below which covers four SwyxServer instanceseach with 20 users. It is assumed there will be 1000 call set-ups per hour and perinstance.

Microsoft .NET Framework and WSE Runtime 3.0For the installation of SwyxWare, Microsoft .NET Framework v2.0 and WSERuntime 3.0 (Web Services Enhancements) are required. These components are alsorequired for installing SwyxWare Administration and the telephony client SwyxIt!,since the SwyxWaredatabase is now accessed via the web services. All softwarecomponents are available on the CD. If you start the installation from the CD, Setupchecks the availability and suggests installation of these components.

Please make certain that the most up-to-date Service Pack fromMicrosoft is installed when using the Windows system. Install the security

SwyxWare in the datrequirement.

Prerequisite In order to offer Swyxthe public telephone n

3.1.1 Back End SerThe back end server eand the outside world.channels.

Typically, no users areporting of the back einto the outside worldsuch a back end serveduplicate in the reporecorded in reporting.end server.

Back end server

CPU

Memory

Hard disk memory, se

Hard disk memory, administration

Hard disk memory, tr

http://windowsupdate.microsoft.com


s for Front End Server (FES)ou need space for

o installation and the related management tools (Chapter 3.2,

tallation that serves as a template for all virtual PBXs

wyxWare instances themselves, which can be configured by (Chapter 3.1.4, Requirements of a virtual PBX).

front end server are naturally dependent on the number ofvirtual PBXs) to be installed here. The memory requirement ofl PBX is only marginally dependent on the number of users,tself (e.g. for announcements, scripts etc.) is stored in the

from the laboratory can provide a clue here. For a front endo installation and e.g. 6 (30) SwyxWare instances each with 20ers have not installed any further scripts in addition to the, the following values apply:

lization of the operating system, please note the Microsoftions, e.g. at present the Standard Edition cannot bee Enterprise Edition only four times, but the DataCenterften. You will find further information on this atcrosoft.com/germany/serverlizenzierung/default.mspx.

Requirements

Dual Xeon Dual Core 3.2 GHz

4 GB (for 6 vPBX) to 32 GB (for more than 30 vPBX)

200 GB

dual Ethernet Board, 1Gbit/s

• Windows Server 2003 x64 Edition (for more than four virtual instances the Data Center Edition is needed)

• all available operating system updates• Microsoft .Net Framework 2.0• WSE 3.0 Runtime• Virtuozzo 3.5.1 SP1

For the virtualicense conditvirtualized, thEdition more ohttp://www.mi

3.1.2 Requirements for separated SwyxGateThe access to the public network can be via a separate SwyxGate. SwyxGate requiresNO special hardware equipment for operation. The software can be run on allstandard PCs on which Windows Server 2003 or Windows XP Professional can alsobe run. The hardware requirements correspond essentially to those recommended byMicrosoft for the use of these operating systems.

SwyxGate Requirements

CPU Pentium IV, 3 GHz HT (for SX2 SinglePRI)Dual Xeon (for SX2 DualPRI)

Memory 512 MB

Disk Space 25 MB

Network Adapter 1 GBit/s

PCI Plug-In Slot one free plug-in slot for each ISDN card

Software • Windows Server 2003 (32 bit or 64 bit) or Win-dows XP Professional

• all available operating system updates• Microsoft .Net Framework 2.0• WSE 3.0 Runtime

3.1.3 RequirementOn a front end server y

• the VirtuozzVirtuozzo),

• the clone ins

• the virtual Sthe customer

The requirements of aSwyxWare instances (each individual virtuasince the user data idatabase.

The installation valuesserver with a Virtuozzusers, where these usstandard call handling

Front end server

CPU

Memory

Disk Space

Network Adapter

Software


tem Requirementsan be installed on a cluster. It supplies the application data forBXs. The size of the system is thus dependent on the numberBXs. The data for the reporting is also recorded here.

Requirements

Pentium IV, 3 GHz HT

2 GB

• 60 MB for each virtual PBX• 5 MB for each installed user

Without memory space for recorded calls! Recordings should not be stored in the database: they should go in a separate directory at the provider.

1 GBit/s

• Windows Server 2003, Enterprise x64 Edition• Microsoft SQL Server 2005, Enterprise EditionIf the database is configured as a cluster, the opera-ting system must be at least Windows Server 2003Enterprise and the SQL Server Enterprise must beinstalled in the cluster configuration.

3.1.4 Requirements of a virtual PBXThe requirements of a single virtual environment are not dependent on the number ofusers set up, since this data is all stored in the database. Indications for a singlevirtual instance can be given here.

Please note that on a virtual instance only SwyxWare is installed, and nofurther applications from third-party manufacturers.

Virtual PBX Requirements

Disk Space SwyxServer 130 MB plus the space needed by the other software components (see below)

Hard disk memory, administration

30 MB

Hard disk memory, tracing If you want to save decentralized trace outputs to the hard disk during operation, further disk space has to be provided for this. We recommend at least 8 GB for each virtual environment.

Memory space in the database

60 MB (initial database), and additionally the data for users that are set up

Software • Windows Server 2003 x64 Editionis cloned by the Virtuozzo installation from the ope-rating system. Please note the Microsoft license con-ditions.• Microsoft .Net Framework 2.0• WSE 3.0 Runtime• Virtuozzo 3.5.1 SP1

3.1.5 Database SysThe database system cthe individual virtual Pof configured virtual P

CPU

Memory

Disk Space

Network Adapter

Software


er and Database Server

ly an access to the backnet.

e scenario was tested with Virtuozzo 3.5.1 SP1 and Virtuozzo

of Virtuozzo the Virtuozzo Management Console (VZMC) iss to be licensed separately. For Virtuozzo 4.0, the management

s Management Console". The program "Parallels Infrastructureles Virtuozzo to be administered online without restrictions.

enses, but are included in the Virtuozzo licenses assigned byng, the configuration via Management Console is therefore

from Virtuozzo for the Management Console (VZMC) arew.

dware used, the number of licenses for virtual instances pered to 100 in the software obtained by Swyx from Parallels.

n please refer directly to the manufacturer's website:

om/en/products/virtuozzo/tools/specs/

Requirements

25 MB (5 MB per 100 virtual environments is recom-mended)

60 MBadded to this is the necessary space for the individual virtual PBXs

Front end server

Two network cards or a dual network card should be installed in the front end servers.This provides on one side for the customer's access to his telephony server, and onthe other side the access to the back end server and the database.

3.1.6 Network Card(s) There are two networks present in the Hosted SwyxWare installation: the frontnetover which the customers reach their respective SwyxServer, and the backnet, whichcontains e.g. the back end server and the database server as well as the interfaces toother networks.

We recommend using two static IP addresses for the front end server. Internally (tothe back end server) it is possible also to distribute the IP address via DHCP.Externally, a static IP address for the customer is always needed.

Back End Serv

These servers need on

3.2 VirtuozzoThe Hosted SwyxWar4.0.

For the management recommended. That hatool is called "ParallelManager" (PIM) enabBoth tools require licSwyx. In the followidescribed.

The recommendationslisted in the table belo

Regardless of the harhardware node is limit


http://www.parallels.c

Front end server

Memory

Disk Space


per media stream - two media streams are needed for a call), a bandwidth of 17.9 Mb/s.

ppropriate Network Environment for SwyxServer xWare telephone system to operate smoothly, the existing is a deciding factor in addition to the basic software and

s described above. The following provides a description of ans optimal conditions for the functioning of SwyxServer.

of the SwyxServer PC

itions for SwyxServer, the following should be set up:

n which the SwyxWare is installed, will be configureds the telephony server. Other network services, such as e-mailP or DNS server, should not be provided on this PC.

is given a permanent IP address (Public IP address).

of the network

e of the Network

ses the Internet Protocol (IP) to transfer voice and control data.and SwyxServer PC requires a unique IP address in the net-

layer 2 switched network guarantees an optimal transmission and control data even in the case of a large number of Swyx-one calls or in a network with a great deal of data traffic (e.g. HTTP, FTP) but it is not absolutely necessary.

rver PC or the SwyxGate which has been installed on a sepa-t be connected to a switch. This will ensure that there is suffi-idth available for the data traffic between the telephony clientsSwyxPhone) and SwyxServer.

ervice

mprove the voice quality, the use of Quality of Service in thenetwork is advantageous. Especially with narrowband connections (e.g.home connections), the prioritization of the packets is important for voicetransmission.

lso supports QoS for RTP and SIP packets.

g Knowledgebase article describes in detail the procedure:

of QoS (Quality of Service) (kb2340)

SwyxWare a

The followin

Support

3.3 Network Requirements and BandwidthThe IP network, in its function as a transport medium, has a significant influence onthe voice quality of the telephone connections. Therefore, special attention must bepaid to the configuration of the network.

We recommend ensuring an adequate IP connection: at least a network with 100Mbit/s, according to requirements a network with 1 Gbit/s. The requirements depend verymuch on the number of systems in use and the number of active users.

For calls within a virtual PBX the media data stream is handled directly between thetwo terminal devices, i.e. only bandwidth in the end customer's LAN is needed forthese.

As well as the connection from the provider to the end customer, the connection fromthe provider to the SoftSwitch as ISDN interface into the public telephone networkmust also be considered here.

Practical experience suggests the following recommendations for the bandwidth inrelation to the number of users:

For the example of a front end server with 32 virtual PBXs and average user numbersof 20, this gives a requirement of 224 channels and, at 160 kb/s per channel (80 kb/s

Number of users

Chan-nels

Bandwidth

10 4 0.6 Mb/s

20 7 1.0 Mb/s

50 14 2.2 Mb/s

100 25 4.0 Mb/s

500 60 8.0 Mb/s

1000 90 14.4 Mb/s

3.3.1 Creating an AIn order for the Swynetwork infrastructurehardware requirementenvironment that offer

Suitable setup

To create optimal cond

• The PC, oexclusively aserver, DHC

• SwyxServer

Suitable setup

• Infrastructur

SwyxWare uEach client work.

A complete of the voiceWare telephfile transfer,

The SwyxSerate PC muscient bandw(SwyxIt! or

• Quality of S

In order to i

http://www.swyx.de/support/ssdb.html?kbid=kb2340


for Voicemailyou will need an SMTP mail server that can be contacted by

ion (user name and password) will be supported.

eck Voicemails, the mail server must support IMAP4 protocol., SwyxServer uses this protocol to access the user’s mailbox, inmails stored there upon demand.

change Server for Call Managementng Manager, SwyxWare further offers calendar-based callould like to take advantage of this, you must have a Microsofth is accessible via the MAPI interface. In order to ensure this,osoft Outlook Client on the SwyxServer.


o Server for Call Managementotes environment, you can also carry out an integration for

nagement.


• DHCP (Dynamic Host Configuration Protocol)

If the IP addresses for the telephony clients (SwyxIt! and SwyxPhone) areto be distributed automatically, a DHCP server which is in the customer'snetwork can be used.

This distribution offers the following advantages:

Unique assignment of IP addresses in the network

Automatic transmission of the SwyxServer IP address to the clients

To find out how to install a DHCP server and how to configure it for theuse of telephony clients, see the SwyxWare documentation.

• DNS (Domain Name Service)

An Active Directory requires a DNS Server located in the network. TheActive Directory uses DNS as a locator service, which helps to assign thenames of the client’s FQDN (Fully Qualified Domain Name), domains,locations and services in the Active Directory of an IP address.

If there are SwyxIt! instances in the network which are installed on the ope-rating system Windows Vista, please use DNS to assign the IP addresses.

If the above mentioned components are correctly configured, SwyxWare will beprovided with an optimal environment.

Link-up of the customer terminal devicesWe recommend linking the customer terminals via VPN (Virtual Private Network) tothe virtual PBXs. This is especially necessary if the customer uses a SwyxPhone orwants to implement a DECT link.

Such a VPN link further ensures greater security for both sides (provider andcustomer).

3.4 Mail Server To deliver voicemails SwyxServer.

The SMTP authenticat

In order to remotely chDuring remote inquiryorder to play the voice

3.5 Microsoft ExWith the Call Routimanagement. If you wExchange Server whicplease install the Micr


3.6 Lotus DominIf you have a Lotus Ncalendar based call ma


> Scenario > 420

osted SwyxWare. This is SwyxWare which gives providers theer companies.

4 ScenarioArea of application of Hosted SwyxWare

SwyxWare can be used in a very wide range of scenarios. Only one subset will be considered in this documentation: Hoption of offering SwyxWare as a solution which can be offered in freely scalable form by a provider as a service to oth

Image 4-1 An overview of SwyxWare's areas of application

> Scenario21

• B - Private User, Home Office with SwyxIt!

Individual telephony clients are linked via a SIP connection to the Hosted

of Hosted SwyxWarewyxWare components are installed at the provider in the back

verview of a complete Hosted SwyxWare installation

provider installs one or more front end servers (FES) in the so-On each front end server, several SwyxServers are installedzzo. Each of these SwyxServers is assigned to a customer. The

SwyxWare.

• C - Company with SwyxWare

A company that already uses SwyxWare as a telecommunication systemcan be linked via a SwyxLink to the provider's Hosted SwyxWare.

Image 4-3 O

Within his network, a called front network. with the help of Virtuo

4.1 OverviewFor a provider, the specific environment created by the supported services is ofinterest:

Image 4-2 Hosted SwyxWare

Various possibilities arise:

• A - Hosted Company

The telephony clients in a company are interfaced directly to Hosted Swyx-Ware, i.e. SwyxWare set up at a provider and hosted there.

4.2 ComponentsThe various Hosted Sand front networks.

> Scenario22

provider's customers connect their telephony clients to 'their' SwyxServer, which isinstalled on such a front end server.

In the back end network, which cannot be reached by the customer computers, areone or more back end servers and the database server. The database server in turn canbe installed on one or more PCs in the form of a cluster.

The front end servers are connected via a SwyxLink to the back end server. The backend server manages the reporting mechanism and the connections to the outsideworld. For example, several PCs each with a SwyxGate can be installed here, in orderto provide access via the built-in ISDN cards to the public telephone network. On theother hand, the back end server also supplies the access to the Internet or to other SIPproviders (Soft-Switch) via the LinkManager.

Connection to the Customer, Firewall

The connection to the customer is provided via an IP route, which in most cases (assoon as SwyxPhone is used) is implemented through a VPN. Suitable VPN systemsshould be used for this; they will usually already provide a firewall on both sides.

> Installation23

Explanation

Back end system• Operating system with current service packs and

updates• .NET 2.0• WSE 3.0• 1 network card

Front end system• Operating system with current service packs and

updates• Virtuozzo• .NET 2.0• WSE 3.0• 2 network cards

Make certain that the necessary hardware and software conditions have been fulfilled.For further information please refer to chapter 3.1, Hardware and Software Requirements, page 14.

Check your network in order to guarantee interference-free transmission. For further information please refer to chapter 3.3, Network Requirements and Bandwidth, page 18.

Install a Microsoft SQL 2005 server on a separated PC (cluster).Create the following databases:

• database for the reporting• a database for the back end system• for the front end template a database, from which all

further databases are then duplicated.Configure the access rights (DB user).For further information please refer to chapter 5.4, Installa-tion of a separated database, page 25.

5 InstallationInitial installation and configuration of Hosted SwyxWare

5.1 OverviewA complete Hosted SwyxWare scenario consists of at least one back end server(licensing server) and multiple front end servers.

Multiple virtual instances (VEs) are set up on the front end servers with the help ofVirtuozzo. A clone template is created, which already contains a SwyxServer, aSwyxWare Administration, possibly SwyxFax, a user 'Administrator' and featureprofiles defined by the provider.

Thereafter for each customer the clone template will be copied and namedaccordingly. This customer instance will be bound to a - copied- database andafterwards customer specific configured.

For further information please refer to chapter 2, The Basics, page 11.

The following specific actions must be executed. You will find references to thedetailed instructions for every step. Knowledge of the SwyxWare Administratordocumentation is assumed for the configuration of SwyxWare.

No. Step

1 Preparation ofthe systems (FES, BES)

2 Network

3 Install Micro-soft SQL Server 2005

> Installation24

8 FES: Customer installation

Use the clone template to create a SwyxServer for a custo-mer. Specify the database created for the customer. For further information please refer to chapter 5.9, Creation of

Number Planible, sustainable number concept is designed before Hosted.

ers can be supplied by the provider for the customer and

ent of these public numbers to the internal numbers within atallation.

5.3 Mail ServerFor the voicemail functionality and the reporting (licensing server), you will need an

hen installing SwyxServer you will need the name of the mailpany.com. For further information, please refer to the

tor documentation.

Create a SwyxLink from the customer's SwyxServer to the back end server. For further information, please refer to the SwyxWare Administrator documentation.

Create further databases and (using the template) SwyxSer-vers for further customers.

Install further FES as necessary.

For access to the public telephone network (ISDN) and to other SIP providers, install suitable gateways (SwyxLink-Manager or SwyxGate) on the back end server. For further information, please refer to the SwyxWare Administrator documentation.

Install further back end servers if necessary, e.g. for setting up separated gateways.

Explanation

a customer installation, page 29.

9 Adaptation of the customer installation

Adapt the cloned SwyxServer installation with the help of ’IPPBXConfig’.For further information please refer Configuration with IpPbxConfig, page 29.

SMTP mail server. Wserver, e.g. Mail.comSwyxWare Administra

4 Install back end system

Install a SwyxServer as back end server (licensing server) and the SwyxWare Administration.Configuration of the SwyxLink trunks of the BES:

• Use only canonical numbers for the forwarding to the FESs

• For each trunk configure "Signal the unassigned num-ber / URI"

• Configure NO public number limitationFor further information please refer to chapter 5.5, Installa-tion of a licensing server (back end server), page 25.

5 Virtuozzo installation

Install Virtuozzo on the front end system for the virtual environments.For further information please refer Installation of Virtuozzo, page 27.

6 FES: Create clone template

Create a complete SwyxWare installation on a virtual server. As database, use the database already created for the front end template.For further information please refer to chapter 5.8.2, Creation of the clone template for a virtual PBX, page 27.In particular, create the administrator profiles and the feature profiles which you want to use later on all customer servers. For further information, please refer to the SwyxWare Administrator documentation.

7 Database for customers

Before creating a customer server, duplicate the FES template database. For further information please refer to chapter 5.4, Installation of a separated database, page 25.

No. Step Explanation

5.2 Concept of aMake sure that a flexSwyxWare is installed

In doing so, consider

• which numb

• the assignmcustomer ins

10 Configure SwyxLink

11 Further custo-mer installati-ons

12 Additional FES

13 Create gate-ways

14 Further BES

No. Step

> Installation25

the Configuration Wizard awards the necessary rights (db_datawriter; db_datareader;IpPbxUser) to the user account under which SwyxServer will later access thedatabase.

of a licensing server (back end server)you install should be a back end server, the licensing server inges the Hosted SwyxWare license, so that there is no furtherer installations of the front end servers. If necessary you can end servers later, e.g. for linking to SoftSwitches. In thesence the previously existing licensing server for the license.

of the licensing server, create two databases:

atabasexWare data is stored in this database: user parameters, trunketers etc. server is used only for administration of the licenses and theunk groups, the database will remain small (see Licensing and the back end serverThe back end server puts the fax and voiceo the outside world and manages the licenses. Typically, noated on such a back end server. In order that the voice and fax not entered in duplicate in the reporting, a SwyxServer that

than one user is not recorded in reporting., page 46).tabasee is exclusively for the entry of the reporting data.

a licensing server (back end)

h a user account which has local administrator rights.

osted SwyxWare installation.

he installation from the CD using the link on the server page or from the command line. In the command line enter: /i setup.msi HOSTED=1

er to the SwyxServer documentation for the individual steps in the installation of the SwyxServer.

In particular enter during the server configuration

ated SwyxWare database Enter the user account and the rd with which the server should access this database.

abase created for the reporting, and enter the user account and rd with which the reporting service should access this

se.

r the license key.

Please note that for copied databases the access rights must then bemanually assigned. Alternatively, the Configuration Wizard can also berun again here.

• the crepasswo

• the datpasswodataba

4. Then ente

5.4 Installation of a separated databaseCreate a separated Microsoft SQL database for user administration for eachSwyxServer included in a Hosted SwyxWare installation (FrontEnd and BackEnd).The users configured for this SwyxServer are managed in this database along with allother server parameters.

It is recommended to use the template database which already containsprofiles, an administrator and other pre-configured parameters. Afterthe first configuration this database can be copied for every server youwant to create using the Backup&Restore mechanism.

When installing the SwyxServer you then give the instance name and the name ofthis database. The configuration wizard creates the necessary database schema forSwyxServer when configuring the SwyxServer.

Please note that the backup and restore function that can be used in theSwyxWare variant for businesses is not applicable for the HostedSwyxWare. This backup cannot be used since the database is not installedlocally on the same PC, but was implemented as a separated database.Please use the SQL server backup mechanism for the Hosted SwyxWare.

database for the reportingFor the daily data entry by the licensing server, a reporting database is needed. Datais collected here within the entry period (one month). The reporting uses the data ofthis database and this will be sent by e-mail both to the provider and to Swyx.

For further information please refer to chapter 7.2, Reporting, page 43.

Access rights for the databasesSwyxServer needs only restricted rights for database access. During the installation,

5.5 Installation The first SwyxServer fact. This server manalicense entry for furthalso create more backinstallations you refere

Preparation

Before the installation

• SwyxWare dAll the Swygroup paramIf the licensetrunks and trreporting ofchannels intusers are crechannels arehas no more

• Reporting daThis databas

How to install

1. Log on wit

2. Start the H

You start tinstallation

msiexec.exe

3. Please ref

> Installation26

The permanent license key for Hosted SwyxWare is requested after the installation ofthe licensing server. Start the licensing server for this, and under the server propertiesopen the "Licenses" tab. Click on "Create request" to start the process for requesting

valid so long as the reporting is active. For further information7, Licenses, page 43.

r a cold standby server

ld standby server, i.e. a substitute server which is an identicalserver and is activated if the original fails in the network, youkey for this server. This license key too is obtained from Swyx.

at the cold standby server's license must also be madehe limited license expires in any case 30 days aftereaning that the server cannot be operated afterwards.

of SwyxWare Administrationinistration can be installed on one or more PCs within theow to install the administration, please refer to the SwyxWaretation.

hanges to a SwyxServer, open the SwyxWare Administrationver you want to amend. You can change all present and activeay.

hat you must have the corresponding rights for the of a server. For further information please refer toinistration, page 37.

n of a back end server (BES)f a back end server, the following should be configured:

s and trunks

of SIP or ISDN trunk groups and trunks to establish the con-e outside world. For further information, please refer to the

SwyxWare Administrator documentation.

• Reporting (for a licensing server only)

porting under the server properties on the "Usage report" tab.nformation, please refer to the SwyxWare Administrator docu-

(for a licensing server only)

ense key permanent under the server properties on the "Licen- further information, please refer to the SwyxWare Administra-tation.

a permanent license. Hardware parameters of this PC are linked with the temporarylicense key, and the customer data is entered. For further information, please refer tothe SwyxWare Administrator documentation. The permanent license key is sent toyou by Swyx.

Please note that the temporary installation expires after 30 days.

Set up the reFor further imentation.

• License key

Make the licses" tab. Fortor documen

5. Configuration of back end server• SwyxLink: Use only canonical numbers for the forwarding to the FESs

• For each SwyxLink to the FES configure "Signal the unassigned number / URI"

• Configure NO termination of public numbers on this back end server.

How to install a further back end server

If a licensing server is already present within the installation and you want to create another back end server, the installation is similar to that of a SwyxServer. Specify the licensing server during the configuration of this server.. For further information, please refer to the SwyxWare Administrator documentation.

The installation of a standby server for the back end server does not takeplace here, since a standby SwyxServer as in the company environment isnot involved. If you want a standby system for a back end server onredundancy grounds (and we recommend this), you have to create anidentical copy of the existing back end server on new hardware (same IPaddress and computer name etc.). The simplest way to create the copy isto make use of a system which is identical in hardware to the existingback end server, and install an image of the existing system there. If theback end server now fails, the copy of the system can simply be activatedin the network.

License KeyFor Hosted SwyxWare, only one license key is needed. This is already input duringthe installation of the licensing server The front end servers obtain their legitimationfrom the licensing of the licensing server.

The licensing remainsplease refer to chapter

License key fo

If you want to use a cocopy of the licensing need a second license

Please note thpermanent. Tinstallation, m

5.6 Installation The SwyxWare Admnetwork. To find out hadministrator documen

If you want to make cand connect to the serSwyxServers in this w

Please note tadministrationchapter 6, Adm

5.7 ConfiguratioAfter the installation o

• Trunk group

Installation nection to th

> Installation27

How to install Virtuozzo on a front end server

1. Install a Virtuozzo server.

the Virtuozzo server with the help of the configuration wizard.

t updates are directly downloaded and installed. This may take .

a password is set, and the corresponding Virtuozzo templates 2003 Server R2" and "Windows 2003 Server SP2") are

icense for the Virtuozzo server.

will try to activate the license automatically. If the activation , try to activate the license manually. For further information r to the Virtuozzo documentation.

uration is then completed.

ork configuration of the host system (hardware nodes), create networks. Each network is assigned to a physical network a network adapter each for frontnet and backnet).

anagement console (PMC) is automatically installed at the

e clone template for a virtual PBXzzo it is possible to create a virtual instance, which serves as airtual instances. On this virtual instance, both the necessaryllations are carried out, and also the corresponding SwyxWaree the same for all virtual PBXs.

a clone template

irtuozzo management console (PZMC).

ew Private Server:hortcut menu, choose creation of a new Virtual Private Server.

mendation for the settings of the services for the Private Server:> CPU units: 1000 pcs (default)> Disk space: min. 3,000,000 1K blocks

ber of processes and TS sessions, VPS memory: unlimitedrd will guide you through the creation. You enter the basic ters such as a unique name for this instance, an ID, the

ing system template "Windows 2003 Server R2" and "Windows erver SP2", and a password.tual networks were already created during the creation of the stem (see How to install Virtuozzo on a front end

Read the license agreements and specify the required parameters, such as customer information, directories etc.. > Num

• A wizaparameoperat2003 STwo virhost sy

Please note that the temporary installation expires after 30 days.

5.8 Installation of a front end server (FES)Multiple virtual PBXs are set up for different customers on a front end server. Theinstallation is carried out in several steps:

• Installation of the operating system Windows 2003 Server includingService Pack 2

• Installation of .Net2.0 and WSE 3.0 Runtime

• Installation of Virtuozzo 4.0

• Installation of the operating system updates and the Virtuozzo updates, ifthis was not already done during the installation

• Creation of the clone template for a virtual PBX

• Creation of a customer installation

• Configuration of a customer installation by the provider

5.8.1 Installation of VirtuozzoThe installation of the operating system is followed by the installation of Virtuozzo.The necessary steps are only briefly explained in this documentation. For moreinformation, please read the documentation for the Virtuozzo software. You can alsoobtain further information on the website

http://www.parallels.com

For the installation of the Virtuozzo server, please have ready the file withthe Virtuozzo server license, and the Windows 2003 Server CD.

2. Configure

The currensome time

After this, ("Windowsinstalled.

3. Enter the l

Virtuozzo should failplease refe

4. The config

5. In the netwtwo virtualinterface (

The Virtuozzo msame time.

5.8.2 Creation of thWith the help of Virtuotemplate for further voperating system instainstallations, which ar

How to install

1. Open the V

2. Create a n• In the s

• Recom

http://www.parallels.com/

> Installation28

mand line tool:vzctl set [ContainerID] --netif [NetworkadapterID] --gateway ""

e.e restart, enter the domain user in the instance as local strator, to enable you to install further software.

ns for the SwyxWare

the operating system requirements for SwyxWare:.0

3.0 Runtime

Installationstall SwyxServer. For further information, please refer to the are Administrator documentation.is you install the corresponding SwyxWare Administration. For

information, please refer to the SwyxWare Administrator entation.yxFax Server can then be installed. For further information,

refer to the SwyxWare Administrator documentation.

xServer, create the parameters that are the same for all virtual following parameters are recommended:

istrator a user which has all SwyxWare administrator rights.

n the provider's location as a location in the SwyxServer. This is ary for limiting the number of calls between locations (interloca-ll limit).e Profiles different feature profiles, which can be assigned later to a cus- end users. These feature profiles represent the usable func-ptions) which are later summarized in the report which is sent.

ther information please refer to chapter 6.4, Feature s, page 41.

• Trunk groupCreate a trunk group with the type 'SwyxLink', which connects the

erver to the back end server (provider location). The trunks for ce channels and fax channels can be created within this trunk later.serverUN server is the same for all customers. Configure this STUN for SwyxIt! in the server properties on the "Client Settings" tab.eters of all FESlso want to specify further settings that are common to all other

If you delete the gateway in the Windows settings, it will be restored aftera restart. So please use the Virtuozzo program, which correspondinglymodifies the configuration file of the virtual environment.

7. If you want to manage the instances later as members of a domain, then• include the instance as a member in the domain, and restart the

SwyxSthe voigroup

• STUN The STserver

• ParamIf you a

server, page 27, step (5)). Both the virtual network cards must be con-figured in 'Bridged Mode'.Under ’Auto boot and Login’, activate the offline management, broad-cast and the QoS Packet Scheduler.After the displayed overview is confirmed, a corresponding virtual instance is created.

3. Start a Remote Desktop session for the created instance under the local administrator account.

4. Create further hard disks (drives) if you want.

5. Configure a further network card for the virtual environment:• To do this, open the properties of the virtual environment in the server,

and switch to the "Network" tab.• Enter a second IP address and the associated Subnet Mask, needed

for the backnet.• Add the DNS server for this backnet.• Activate the corresponding physical interface in the list of network

devices.

Then make sure from the virtual environment that both network accesses are accessible from the virtual environment.

6. In the server configure the two virtual network adapters in 'Bridged Mode'.• Activate QoS manually for the second network adapter.

Connect to the virtual instance, open the operating system configura-tion and activate the QoS Packet Scheduler in the properties of the adapter.

• Check the routing table of the virtual environment.If two standard gateways are listed there, delete the gateway that leads to the backnet.On the host system (hardware node) you can do this directly from the command line (not from a virtual instance). Use the Virtuozzo com-

instanc• After th

admini

8. Preparatio

• Install - .Net 2- WSE

9. SwyxWare• Then in

SwyxW• After th

furtherdocum

• The Swplease

10. In the SwyPBXs. The• Admin

Create

• LocatioCreatenecesstion ca

• FeaturCreatetomer'stions (oFor furProfile

> Installation29

IP address of the virtual environment.

9. Check the settings of the time zone. If one domain is used for all systems,

tual PBX at least one other license ID with the command/r", so that this will be entered in separate reporting.

all SwyxWare services so that they are automatically restarted

yxWare Administration and connect to the new system (local e).

xWare Administration, change the SIP Realm in the server on the "Client Settings" tab (see SIP realm of the ge 31). This realm must be unique.

cally managed SwyxLink, which connects the front end system end server. Check the registration and the record types in the Administration (see SwyxLink connection to the back end

ge 31).

e the further parameters for this customer (see chapter 5.10, ion of a customer installation by the provider).

n with IpPbxConfigram that is called from the command line. It is used for givingre the corresponding unique parameters, e.g. name of the database that was also copied for this clone is used here.

nfig in the SwyxWare program directory.

g options here:

Explanation

Displays an overview of the available parameters of IpPbxConfig.

Displays the current configuration of the SwyxWare database and the reporting database.

name>Name of the SQL Server instanceGives the name of the SQL Server on which the SwyxWa-redatabase for this PBX is installed.Example:

• /ii <SQL-Srv><Name of the PC on which an SQL Server instance isinstalled> (global instance)• /ii <SQL-Srv\Instance><Name of the PC on which SQL Server instances areinstalled \ Name of the instance> (named instance)

synchronization takes place over the domain. Otherwise the administrator must check all settings.

10. Configure the SwyxServer with the help of the program IpPbxConfig, and specify the new customer data (see Configuration with IpPbxConfig, page 29).

Alternatively, start the Configuration Wizard, which will prompt you for all the necessary parameters.

front end servers, configure these settings now.• Then pause the Virtual Private Server. The server can be reproduced

(cloned) only in the paused state. This prevents all services being started immediately when a cloned server is started.

11. Delete used IP addresses from the VE configuration.

5.9 Creation of a customer installationIf you want to create a new server instance (virtual PBX) for a customer, copy theexisting database of the template for this customer (see also chapter 5.4, Installationof a separated database, page 25) and generate a clone of the SwyxWare template.

How to generate a new virtual instance

1. Starting from the database of the clone template, and using the Backup&Restore mechanism, create a database for the customer.

2. Open the Virtuozzo management console (VZMC).

3. In the shortcut menu, choose "Tasks | Clone".

4. Give an IP address, or an IP address range for the clone template(s) in the case of multiple new instances.

5. Corresponding clones will be created, but all with the same host name.

6. Open the properties of a virtual private server and change the name to a unique name.

7. Start the virtual instance and then trigger a restart (reboot via cmd-line 'vzctl restart <ID>'). .NET Framework then adopts the new host name. The SwyxServer installed there accepts the new name of this instance too.

8. Create a new registration key under "HKLM\Software\Wow6432Node\Swyx\General\CurrentVersion\Options" with the name "LocalIpAddress" (REG_STRING), and enter the frontnet

Assign the vir"ipPbxConfig

11. Configure

12. Open a Swand remot

13. In the Swypropertiesclients, pa

14. Create a loto the backSwyxWareserver, pa

15. Then definConfigurat

ConfiguratioIPPbxConfig is a prognew cloned SwyxWadatabase and user. The

You will find IPPbxCo

You have the followin

Parameters

/?

/v

/ii <SQL Server

> Installation30

Sets the settings and permissions of the SwyxWare services for the new virtual PBX.

/start Starts all SwyxWare services

er 'CustomerA' to the database 'DB_CustomerA' on the SQLF'. In doing so, you also specify the name of the database userand his password 'Password_DB_CustomerA'. /ii DB_ServerA_F /di DB_CustomerA /ui omerA /pi Password_DB_CustomerA

re services without inquiry, enter: /stop /start /y

/stop Suspends all SwyxWare services

/ex Outputs expanded error messages

/y Silent installationIpPbxConfig will run without making further inquiries.

*. These values can only be set when the reporting is activated on this server.

/di <Database name> Name of SwyxWare databaseSets the name of the SwyxWare database for this PBX.

/ui <User> Name of the SwyxWare database userGives the name of the database user under whose user account the PBX accesses its database. This user must be a member of the database roles "db_datareader", "db_datawriter" and "IpPbxUser".

/pi <Password> Password of the SwyxWare database userSets the password belonging to the SwyxWare database user.

/ir <SQL Server name>

Name of the SQL Server instance*

Gives the name of the SQL Server on which the reporting database for this PBX is installed.

/dr <Database name> Name of the reporting database*Sets the name of the reporting database for this PBX.

/ur <User> Name of the reporting database user*Sets the name of the database user under whose user account the PBX stores the reporting data. This user must have writing and reading rights.

/pr <Password> Password of the reporting database user*Sets the password belonging to the reporting database user.

/r Generates a new license ID for the virtual PBXATTENTION: This PBX will afterwards be recorded under a different ID in reporting!

/l Local security settings

Parameters Explanation Example 1:

Connect e.g. the servServer 'DB_ServerA_'DBUser_CustomerA'

IpPbxConfigDBUser_Cust

Example 2:

To restart all SwyxWaIpPbxConfig

> Installation31

the clients

r this customer must be entered in the server properties on thengs" tab. This realm is then used by default for all users of this

r recordings

directory in which a user's recordings will be stored. You canders here, such as [user_name].

nformation, please refer to the SwyxWare Administrator docu-

• Numbers

numbers must be assigned to external numbers. Otherwise the cannot be reached by external subscribers.

We recommend the use of the canonical form for the numbers in routingrecords. It means that a unique correlation e.g. to the outgoing trunkgroup is recognizable for the administrator too.

The numbers or the SIP URIs are specified in the properties of the trunksbelonging to this trunk group.

The internalinternal lines

5.10 Configuration of a customer installation by the providerAfter the creation of a virtual PBX, you can still configure this further. It is essentialto create the following parameters:

• Customer administrator

A user must be created with the right to create and manage the users. Allother users can then be created and managed by the customer himself.

• SwyxLink connection to the back end server

A SwyxLink connection is set up to the back end server, and managedlocally on the customer side. The name must be unique. All connections tothe outside world are made via this trunk group.

The customer's numbers and corresponding SIP URIs are assigned to theSwyxLink connection to the back end server. Open the "Routing Records"tab in the properties of the SwyxLink trunk group for this.

• SIP realm of

The realm fo"Client Settiserver.

• Directory fo

Specify the use placehol

For further imentation.

> Installation32

Configure a SwyxFax userSwyxFax users are set up by the assignment of fax numbers to the user "SwyxFax" in

n of a customer installation by the reseller a reseller has the profile 'Reseller Administrator'. Thisis provided specifically for resellers. It allows completexServer. The only exception is the configuration of trunks andller is thus enabled to:

properties such as

ic on hold,

voicemail announcement

ver configuration

SIP logon parameters, realm

ction,

cording

ent of SwyxPhones and PhoneController

f Call Detail Records (CDRs)

one firmware update

re profiles

rmissions

r mappings

sing server

istration rights for customer administrators etc.

ns and new calls

firmware for the SwyxPhone

x numbers of all fax users to the user 'SwyxFax'

g of the incoming fax documents by e-mail to the relevantusers must be handled directly on the virtual instance with the help of theSwyxFax Administration.

plete detailed listing of a reseller administrator's options inw of the various administrator levels, page 39.

f SwyxIt! and SwyxPhone must be installed directly at the customer. The customer's do this on site.

the SwyxWare Administration. These numbers can then be used for sending faxdocuments. Forwarding of incoming fax documents to the users is configured inHosted SwyxWare by the provider's administrator. The assignment between thedialed fax number and the e-mail address to which these fax documents are to be sentmust be entered in the SwyxFax Administration for this.


You will find a comchapter 6.1.2, Overvie

Installation oThe terminal devicesadministrator can also

Specify concurrent calls for a locationYou can specify in the SwyxWare Administration how many calls (incoming andoutgoing) can be made simultaneously from one location to other locations.

The number of interlocation calls will be collected as well as the number of thespeech channels.

Please note that a further voice channel will be needed for setting upconferences between two locations. Thus if a location is connected withthree employees and these three employees want to hold an internalconference, you need a maximum number of four between locations.

5.11 ConfiguratioThe administrator ofadministrator profile configuration of a Swytrunk groups. The rese

• set up server

the mus

standard

mail ser

standard

skin sele

trunk re

assignm

saving o

SwyxPh

• specify featu

• set up call pe

• make numbe

• specify licen

• assign admin

• disable logo

• supply new

• assign the fa

The forwardin

> Installation33

Create userIf a logon as customer administrator occurs at the customer server, users can be

ting and editing)

strator can import, create and edit scripts for the users andCall Routing (Call Routing Manager or Graphical Script

at for script editing you can use only the SwyxWaren. The SwyxWare Web Administration does not offer this

bers

r to a subscriber, assign the relevant number to the SwyxFax Administration. You add the type of fax forwarding (e-mail,t) in the SwyxFax Administration.


created and administered by the customer himself. For information on how users arecreated, please refer to the documentation on SwyxWare Administration.

Users can also be imported directly with the UserImportAssistant. You will find thistool on the CD under Tools\UserImportAssistant. For further information, pleaserefer to the SwyxWare Administrator documentation.

5.12 Configuration of a customer installation by the customerThe customer administrator has the right to create and manage users. In detail, hecan:

• create users and groups

• set up server properties such as

the music on hold,

standard voicemail announcement

mail server configuration

skin selection,

assignment of SwyxPhones and PhoneController

saving of Call Detail Records (CDRs)

SwyxPhone firmware update

• set up call permissions

• make number mappings

• disable logons and new calls

• read firmware for the SwyxPhone

• assign administration rights for user administrators etc.

• assign the fax numbers of all fax users to the user 'SwyxFax'

The forwarding of the incoming fax documents by e-mail to the relevantusers must be handled directly on the virtual instance with the help of theSwyxFax Administration.

You will find a complete detailed listing of a customer administrator's options inchapter 6.1.2, Overview of the various administrator levels, page 39.

Scripts (impor

The customer adminigroups for Extended Editor).

Please note thAdministratiooption.

Assign fax num

To assign a fax numbeuser in the SwyxWaredirect, or printer outpu


> Installation34

4. In a web browser, open the site:

http://localhost/WebAdmin/

of SwyxFaxsible to clone SwyxFax on a virtual environment. So on everyxFax should run, a separate SwyxFax installation should be

u install the SwyxWare Web Administration

quirements must be met:

are is already installed on the VE. There is a trunk group to the nd server.

ser in the server with the type ’Fax’ (e.g. SwyxFax).

a new trunk 'Fax Trunk' within the trunk group which leads to nd server. For this trunk, configure the code 'Fax/T.38'. Select rameters as for the other trunks to the back end server.

e SwyxFax Server installation. A separate fax installation is r each customer server.

onfiguration wizard then starts:e a local user account for the fax server.

integration, choose the fax user (e.g. SwyxFax) in erver.

xFax Administration, specify the forwarding of the fax for each fax number (e-mail, printer or SwyxFax Client).

the SwyxFax Server from the SwyxFax Administration.

effect, it is possible to send or receive fax documents. All sent x documents can be detected in the SwyxFax Administration.

wyxFax Server installation SwyxFax installation, both the SwyxFax Server settings andn the SwyxFax Server must be backed up.

This is how you back up a SwyxFax installation

ing registration keys must be backed up for SwyxFax. For the e a script which uses 'reg.exe'.LOCAL_MACHINE\SOFTWARE\Wow6432Node\Swyx\FaxH323

LOCAL_MACHINE\SOFTWARE\Wow6432Node\Swyx\FaxPrintway

LOCAL_MACHINE\SOFTWARE\Wow6432Node\Swyx\FaxServ

5. If you want remote access to the SwyxWare Web Administration, make sure that the proxy configuration is correct.


1. The followbackup, us• HKEY_

• HKEY_erGate

• HKEY_er

5.13 Installation of the SwyxWare Web AdministrationThe SwyxWare Web Administration allows changes to the user and groupconfiguration. This makes it the appropriate instrument for the customeradministrator making changes within the SwyxWare from a web application.

The SwyxWare Web Administration can be installed either on the virtual machine oron your own PC.

This is how you install the SwyxWare Web Administration

The following requirements must be met:

• Internet Information System (IIS)• .Net 2.0• WSE 3.0 Runtime

• ASP.Net v2.0.50727 activated (Web Service Extension ‘allowed’)

1. Execute the Setup of the SwyxWare Web Administration.

Specify ’WebAdmin’ as the installation directory.

2. Check the configuration of the SwyxWare Web Administration in the IIS:

3. To do this, open the local PC or the VE in the IIS Manager ("Start | Programs | Administration | Internet Information Services Manager"):• Under "Websites | Standard WebSite", "WebAdmin" should be set.

• The standard site should be set up:Under "Websites | Standard WebSite | WebAdmin | Properties | Docu-ments", ’Default.aspx’ must be set as ’Standard content page’.

• Check whether the IIS standard website is started (on "Websites | Standard WebSite | WebAdmin": Stop is grayed out).

• Check whether ’Application pools’ is started under "Internet Information Services Manager | Application pools | DefaultAppPool": Start is grayed out.

5.14 Installation At present it is not posVE on which the Swycarried out.

This is how yo

The following re

• SwyxWback e

1. Create a u

2. Configure the back eall other pa

3. Perform thneeded fo

4. The Fax c• Choos

• For theSwyxS

5. In the Swydocuments

6. Then start

With immediateand received fa

5.14.1 Backup of a STo back up an existingall stored documents o

> Installation35

existing Hosted SwyxWare scenarioSwyxWare scenario already exists, this can be updated with.

f Hosted SwyxWare can be updated with the current version.n please refer to chapter 5.16, Update of an existing Hostedage 35.

version of Virtuozzo is Version 4.0. Existing Virtuozzoion 3.5.1, which were installed together with a first Hosted

l the new Version 4.0. For further information please refer tof the Virtuozzo environment, page 35.

u update a Hosted SwyxWare scenario

l existing databases (databases of the front end systems, of the ystem, and the reporting database).

t to update all installations with a new FES template, you can ogram 'IpPbxDBSchema.exe' on the licensing server. Please pport for this.

if only a few systems are present, you can also update eachem separately. But remember that for each new system ate is needed.

SwyxWare on the back end system.

ew Virtuozzo template.

ew database for this template.

new SwyxWare version on the template.

a Virtuozzo 4.0 installation with two virtual network cards in odee QoS for the second adapter manually, by activating the QoS

Packet Scheduler in the operating system configuration in the properties of this network card

the routing table, for whether two standard gateways are d there. In this case, delete the gateway that leads into the t to the back end server (vzctl set ID --netif venet0 --gateway

new SwyxWare Administration version on the clone system.

• Check specifiebackne"").

8. Install the

2. The received fax documents must be backed up. You will find these under C:\Documents and Settings\All Users\Application Data\Swyx\SwyxFax Server\Queue\ (Standard). Alternatively you can find the directory to be backed up in the registration under HKEY_LOCAL_MACHINE\SOFTWARE\Swyx\FaxServer\CurrentVersion\General\(REG_SZ) QueuePath.

3. As an alternative to (2), the incoming fax documents can also be stored in a directory in the network. Configure the path in this case e.g. \\<system-name>\<share-name>).

For automatic backups you can use the BackUp Scheduler.

5.15 Update of the Virtuozzo environmentBefore you update the Virtuozzo installation, please read the relevant Parallels guidewith care.

http://download.parallels.com/virtuozzo/virtuozzo4.0/docs/en/win/VzWindowsUpgrade.pdf

Make sure that a valid software update license for Virtuozzo is installed.

Download the appropriate Virtuozzo 4.0 container for your system (32Bit or 64Bit)and start the installation.

Further advice can be found in the Knowledgebase under

Update of an existing Hosted SwyxWare installation from Virtuozzo 3.5.1 toVirtuozzo 4.0

5.16 Update of anIf a complete Hosted new software versions

Existing installations oFor further informatioSwyxWare scenario, p

The current softwareinstallations with VersSwyxWare, can instalchapter 5.15, Update o

This is how yo

1. Back up alback end s

2. If you wanuse the prcontact Su

Alternatively, front end systcurrent templa

3. Update the

4. Create a n

5. Create a n

6. Install the

7. If you havebridged m• activat

http://download.parallels.com/virtuozzo/virtuozzo4.0/docs/en/win/VzWindowsUpgrade.pdf

http://www.swyx.de/support/ssdb.html?kbid=kb3774

> Installation36

new system name

14. Make sure that all Hosted SwyxWare systems have the same time (e.g. GMT). If you use one domain for all systems, this is synchronized through

m the customer system.

the operating system. Otherwise please check the time settings in each system yourself.

15. Use IPPbxConfig (see Configuration with IpPbxConfig, page 29) to assign the customer instances to your databases / to the corresponding database users:

IpPbxConfig.exe" /di "<DB-Name>" /ui "<User>" /pi "<Password>" /l /r /start /ex /y

9. Configure the clone system (see also chapter 5.10, Configuration of a customer installation by the provider, page 31):• Create a user 'Administrator'.• Specify the provider's location (for the calls between locations).

• Create a trunk group to the provider's location.• Configure a STUN server for SwyxIt!.• You can configure further parameters here, which should be the same

for all virtual servers (e.g. feature profiles).

10. Bring down the clone system.

11. Delete the used IP addresses in the VE configuration.

12. With the help of the clone system, create as many virtual environments as you need in order to update all customer installations.

13. Update the individual customer installations:

• Suspend the customer installation (vFES).• Rename the vFE (e.g. <Name>_old)• Start the program 'IPPbxDBSchema.exe' on the back end server to

update the customer databases. To do this, select the associated database from the list and click on "Update".

• Deactivate the Autostart of the old customer installation.• Remove the IP addresses.

• Configure a new system for the deactivated customer system as follows:- Enter the IP address(es) of the customer system- Create a registry entry "LocalIpAddress" under "HKLM\Soft-ware\Wow6432Node\Swyx\General\CurrentVersion\Option" and enter there the IP address of the VE in the frontnet.- Start the virtual environment and restart the system, e.g. by entering "vzctl restart <ID>" in the command line. .NET thus recognizes the

16. Log off fro

> Administration37

Backoffice Administrator These administrators have all the necessary rights for configuring SwyxServer. Above all, these administrators can create or alter feature

able 6-1 Administration profile (Standard)

tor* This profile allows partial configuration of the server properties. Especially the trunk configu-ration, feature profiles and change log can be displayed. You can configure Calling Rights and Locations and also change global files.

This administrator can undertake all configura-tions for users and groups. You can assign the numbers and administrator profiles and confi-gure group parameters. The exceptions here are the trunks and trunk groups, and the feature profiles.

This administrator is able to change user properties as well as create or delete users. These rights are typically needed by an administrator who is not meant to change the system configuration.

This administrator can see the current call status in the administration, e.g. whether calls are being made at present.

This right allows only editing of the global phonebook, e.g. by the addition or amendment of phone numbers that are important throughout the company.

This profile is the default profile for new users. Therewith the user can log on via SwyxWare Web Administration as user and change his own parameters (

*.This function is only for Hosted SwyxWare available.

ile Description

profiles.

Reseller Administrator* This profile allows complete configuration of the server properties. Especially new function profiles could be created. Only the trunk and trunk group configuration is excepted.

T

6 AdministrationAdministration of Hosted SwyxWare

Especial for Hosted SwyxWare the administration and feature profiles wereestablished. The administration profile defines if a user is allowed to connect to aSwyxServer via SwyxWare Administration and which changes he can make. Thefeature profile defines which advanced SwyxWare options are available for this user.

If the user is allowed to configure ( e.g. SwyxMobile) or start ( e.g. SwyxECR) thesesoptions by himself is defined by an administrator in the user profile.

6.1 Administration profiles

In addition to the administrator with all rights, there is the option of setting upadditional administrators whose rights are restricted to certain applications.

Only those parts of the administration for which the user has the appropriate rightsare displayed. For example, a user administrator will not see any trunk groups in theAdministration tree view and therefore cannot administrate them.

As default, the profile "Not administrator" is assigned to a user on creation. If youwant to change this, open the user properties and assign a different profile to the user.

Administration Profiles in the Standard InstallationYou are already supplied with a few simple administration profiles in the standardinstallation. It is not possible to create new profiles in the present version.

Administration profile Description

System Administrator These administrators have unrestricted access to SwyxWare.

Customer Administra

User Administrator

User Operator

Call Status Operator

Phonebook Operator

No Administrator

Administration prof

> Administration38

customers. They allow self-configuration of the customer's own front end server atvarious levels. Through these various levels, the provider or reseller can give the

dministrator*

trator has the maximum possible rights for a customer. He canl necessary configurations for his front end server. The onlyere are the trunks and trunk groups, and the feature profiles.

istrator

strator can change all properties of users and groups. Theseically needed by an administrator who is not meant to change

onfiguration.

or

om this role is assigned can read all user and group properties,ge them.

perator

strator can see the current call status in the administration, e.g.s are being made at present. This option is of interest to anr who e.g. wants to suspend the computer, and can thus findcalls are still in progress.

perator (editing of the global phonebook)

lows only editing of the global phonebook, e.g. by the additionnt of phone numbers that are important throughout the com-

customer the option of administrating his telephone system himself. Differingadministration levels can be assigned to different users at a customer. The followingspecific options arise:


6.1.1 Administration profiles in the Standard InstallationA general distinction is made between administrators of the Hosted SwyxWare(providers and resellers) and the customer himself.

Administrators of the Hosted SwyxWareThese administrators configure the complete Hosted SwyxWare. These are usuallythe administrators of the provider or the reseller. Only local administrators andWindows user accounts selected by the provider are granted this right. User accountsof a customer are not permitted here. The following specific administration levelsarise:

• System Administrator

These administrators have unrestricted access to Hosted SwyxWare. Thetarget group is the administrators of the provider or the reseller. Localadministrators of the Windows Server always have the rights of a HostedSwyxWare administrator. Further Windows user accounts can be added.These administrators also have the right to assign administration profiles toother users.

• Backoffice Administrator

These administrators have all the necessary rights for configuring HostedSwyxWare. Above all, these administrators can create or alter feature profi-les. The only exception is the configuration of users and groups.

• Reseller Administrator*

This administrator profile is provided specifically for resellers. It allowscomplete configuration of a SwyxServer. The only exception is the confi-guration of trunks and trunk groups.

CustomerThese administrator levels are created specifically for the administrators of

• Customer A

This adminisundertake alexceptions h

• User Admin

This adminirights are typthe system c

• User Operat

Users to whbut not chan

• Call Status O

This adminiwhether calladministratoout whether

• Phonebook O

This right alor amendmepany.

> Administration > 639

hts only - = Not visible for this level

torUserOperator

Call StatusOperator

PhonebookOperator

Non-Administrator

2 2 2 0R/W - - -

- - - R/W

- - - R/WR - - -R - - -R - R/W R- - - -

- - - -- - - -- - - -- - - -

- - - -- - - -- - - -- - - -- - - -- - - -- - - -R R R R

R/W - - R/WR/W - - -R/W R R -

- - - -

6.1.2 Overview of the various administrator levels

Legend: R/W = full access, i.e. reading and writing rights R = reading rig

Directory in the administration Provider and reseller CustomerSystemAdministrator

Back Office Administrator

ResellerAdministrator*


CustomerAdministrator

UserAdministra

Security level 6 5 4 3 2User (Properties, internal numbers)

R/W R R/W R/W R/W

User - Self (Properiese (partial), User lists

- - - - -

Users - pers. Phonebook R/W - - - -Groups R/W R R/W R/W R/WNumber mappings R/W R/W R/W R/W R/WGlobal Phonebook R/W R/W R/W R/WTrunk groups and TrunksForwarding

R/W R/W R -

Call Permission R/W R/W R/W -Feature Profiles R/W R/W R -Locations R/W R/W R/W -Changes R R R R -Server properties: Separated in the following items:Server properties in general R/W R/W R/W -Directory for recordings R/W R/W R -Server SIP Configuration R/W R/W R -License R/W R/W - -Disable logins R/W R/W R/W R/WDisable new calls R/W R/W R/W R/WFirmware R/W R/W R -Global files R/W R/W R/W RUser files R/W R/W R/W R/WUser specific default files R/W R/W R/W R/WActive Calls R/W R/W R/W R/WAssignment of rights for level 0-6 - 0-3 0-2

> Administration40

2. Open the shortcut menu and choose "Delete".

3. Confirm the inquiry.

of elements in Administration (Cloning)istration of many individual elements, it is possible to create, e.g. a user.

opied, an element with the same properties is created, and the with the extension '(copy 1)'. The elements thus created canpted to the requirements.

ced; also groups, locations, trunk groups and trunks, routingns, feature profiles and phonebook entries.

sonal parameters such as user account and password, SIPword, the H.323 alias, the PIN of the SwyxPhone and the e-re not copied, but left blank. A copied trunk group does notnks of the original group. A copied trunk does not containber / SIP URI of the original trunk.

All highlighted elements will be deleted.

6.2 Further Functions of AdministrationA few functions have been expanded in administration for the Hosted SwyxWaresolution. Bundled creation of new elements should thereby be made easier for theadministrator, as should changes to existing elements.

6.2.1 Bulk AdministrationTo facilitate administration of numerous individual elements, collectiveadministration has been introduced.

Multiple users of a SwyxWare installation can now be modified at the same time,e.g., possibly by having a new location assigned to them. This assignment is done bydrag & drop.

The step-by-step guide below is an example. You can deal analogously with otherelements (e.g. groups, rights profiles) in Administration.

How to assign a different location to many users

1. Highlight multiple users by clicking on them while holding down the shift key.

2. Drag these highlighted users with the mouse to the location which you will find on the left side in Administration

3. You can now release the mouse button.

All users now have a new location.

How to delete many elements at once

1. Highlight multiple users by clicking on them while holding down the shift key.

6.2.2 ReproductionTo simplify the admincopies from a template

When an element is cname is supplementedthen be edited and ada

Users can be reprodurecords, call permissio

For users, pername and passmail address acontain the truthe public num

> Administration41

Tip: Configure the maximum number for simultaneously incoming andoutgoing calls such that at least one channel remains available for the

iles

termines which SwyxWare functions a user can use. You willigured profiles in the SwyxWare Administration in therofiles".

entered in Reporting?, page 44When creating a user, thea feature profile for this user from the drop-down list. Thens the functional range available to the user. A differentrofile can subsequently be selected at any time by thenge takes place as soon as the administrator confirms the user's

a customer (customer administrator) can deactivate functionseature profile for a specific user. If a function is not included ine activated by the customer administrator.

re profile 'Standard' includes Call Routing Manager and while the feature profile 'Minimal' includes neither of theseThe customer administrator assigns a user the profile 'Stan-able him to use SwyxFax. Because of this, the customer admi-eactivates the Call Routing Manager checkbox in the fieldl Permissions and Features overview" on the "Rights" tab.ser can use SwyxFax, but not edit redirection rules himself

Routing Manager. Rules created by the administrator with theng Manager can be activated for this user, however. The fea-e 'Standard' is entered in Reporting and charged by the provi-

phical Script Editor':

ard' profile does not include the Graphical Script Editor, whilethe 'Advanced' profile include the Graphical Script Editor.

If the administrator chooses the 'Standard' profile fur User A, he cannot the Graphical Script Editor, since it is not included in the pro-assigns User B the 'Advanced' profile, the administrator canraphical Script Editor available for User B, by activating the

Script Editor in the administration. This allows User B to cre-

respective other direction. permit himfile. If he make the GGraphical

6.3 Number of simultaneous connectionsThe bandwidth between the provider and a customer installation limits the number ofcall connections that are simultaneously possible. For this, the number of channelscan be limited in the properties of the trunks on the "Channels" tab.

Image 6-1 Trunk Properties - "Channels" tab

The sum of all channels that are provided for simultaneous calls, over all trunks, mustmatch the available bandwidth.

6.4 Feature Prof

The feature profile defind several preconfsubdirectors "Feature P

(see 7.2.1 What is administrator selects feature profile contaipredefined feature padministrator. The chaproperties with "OK".

The administrator of that are included in a fthis profile, it cannot b

Example:

The featuSwyxFax,functions. dard', to ennistrator d"FunctionaNow the uwith Call Call Routiture profilder.

Example, 'Use the Gra

The 'Stand

> Administration42

such as the mobile number and password, or whether only the administ-rator can set these for him.

User limitThe system administrator can specify how many feature profiles can be assigned bythe customer administrator to a SwyxServer. This simultaneously limits the numberof users configurable on this SwyxServer.

ate or edit scripts with the Graphical Script Editor. If the Graphical ScriptEditor is not activated in the administration (e.g. if the user only has aSwyxPhone), then scripts created e.g. by the administrator for this usercan still run. This is not possible for User A.

It is possible here to grant the user rights to use advanced SwyxWare functionalities.To change the feature profile, select another profile from the selection list or create anew feature profile.

Feature Profiles in the Standard Installation The profile "Advanced" will be assigned to new users. If you want to assignautomatically a different profile to new users, e.g. the profile "Minimal", you have toconfigure this in the properties of the profile "Minimal".

Tje profile "No Features" is assigned to the preconfigured users "Conference" and"MobileExtensionManager", the profile "Advanced" to the user "Operator".

The usage of SwyxWare functions is defined in the user properties, and isnot immediately identical to the feature profile.

Example 1:

A user's profile must contain the function SwyxECR, in order that ascript (which was created e.g. by the administrator for this user with theGraphical Script Editor) can be used by this user. To prevent this userfrom changing the script himself, the Graphical Script Editor is deactiva-ted in the user properties.

Example 2:

SwyxMobile is activated in a user's profile, meaning that the user can usethe Mobile Extension. In the user properties it can now be specified whe-ther the user himself is allowed to configure the necessary parameters

> Licenses43

can no longer log on even with existing installations. The user data is preserved in thedatabase, so that the virtual PBX is again fully available when the license server

ut, so that the other components of the Hosted SwyxWare, e.g.e licensed and thus functional.

rvers are installed within one Hosted SwyxWare installation, activated on one of these servers only, the so-called licensing

g, this service makes sure that the data about the user numbersigned functions is reported at regular intervals both to the itself. These reports are sent monthly by e-mail. This e-mailh as text and as a signed XML file as an attachment for further

th on which this e-mail is sent can be specified in thelicensing server.

end an 'ad hoc' report for test purposes. This then contains allected since the last report, and is sent only to the provider. It isInformational Report - Not relevant for Accounting". The 'ad

stered in the reporting database. It is thereby ensured that theain covers the total timeframe of one month.

(reporting service) is reactivated and can access a valid license.

7.2 ReportingThe reporting service is a new additional component of Hosted SwyxWare, which isinstalled on the licensing server. This service ensures that the licensing of the

It is also possible to sdata that has been collmarked with the line "hoc' report is not reginext monthly report ag

7 LicensesLicensing and billing procedure

7.1 LicensesOnly one license key is required for the installation of Hosted SwyxWare. Thispermits installation of the full functional range of Hosted SwyxWare. This means thatthe installation of an unlimited number of end users and channels is allowed, alongwith the option of assigning the full functional range of SwyxWare to all front endservers. There is no need to enter further license keys.

Please enter the license key during installation or in the SwyxWare Administration onthe license server. The reporting service must also be activated on this server. Thelicense key for Hosted SwyxWare is made permanent after input, i.e. linked to data ofthis server's PC hardware. For further information, please refer to the SwyxWareAdministrator documentation.

The reporting service does not work without a valid license key. If thereporting service in the Hosted SwyxWare installation is inactive formore than a week, users can no longer log on to a front end server and nomore calls can be made.

This procedure allows the provider to set up SwyxServers as front end servers for hiscustomer without entering further license keys.

Failure of the license server

If the license server is inaccessible or if the reporting service is inactive, existinginstallations remain operational for 7 days (7x24 hours), i.e. users can log on andtelephone as usual, and administrators can edit users and create new ones. However,new customer installations cannot be started up. After this period has expired, users

installation is carried othe front end server, ar

If several back end sethe reporting service isserver.

As well as the licensininvolved and the assprovider and to Swyxcontains the report botelectronic processing.

The day of the monadministration for the

> Licenses44

To collate the reporting information, the reporting service contacts all databases ofthe various SwyxServers (front end servers and back end servers) in order to gain acurrent image of the database at a particular point in time. This information, retrieved

ed in Reporting? usage of the various functions daily. The monthly reportds up the used days per function.

allation with 10 users, all have the feature profile 'Standard'.ly report (data entry period 30 days) thus contains the cumula-

days (10*30=300). In the report this leads to the line

ofile 'Standard': 300

s in this report arise from an extrapolation. This is doneorts could not be entered.

eters

e-mail contains the following general entries:

parameters

is report is likewise included:

Explanation

> Contains the e-mail address from which this e-mail was sent.

Contains the date and time at which this e-mail was sent.

ess> Contains the recipient of the e-mail.

This report concerns a Hosted SwyxWare installation

- Not ng

Indicates whether the report was generated automati-cally (after a month has passed) or manually. You can start manual report generation in the SwyxWare Administration. This line only appears in a report generated manually.

Attachments: report.xml Attachment is an XML file, which contains the same data and is suitable for further automatic processing.

daily, is stored in a separate database. The monthly report is generated from thisdatabase. The report is sent to the provider in the form of an e-mail text and as adigitally signed XML attachment to this e-mail. This XML attachment forms thebasis for further electronic data processing as necessary.

General report

The data relating to th

You can obtain an overview of the sent reports in the properties of the license server,if you select the "Reports" button on the "Usage Reports" tab. You can also re-sendpreviously sent reports here.

Image 7-1 Overview of the reports sent

Reporting addressesThe reporting e-mail is sent to two different addresses:

• The provider's address

This address can be configured in the SwyxWare Administration on the"Usage report" tab. For further information, please refer to the SwyxWareAdministrator documentation.

• Swyx

This e-mail address is fixed and cannot be changed.

7.2.1 What is enterReporting records thegenerated from this ad

Example:

In an instThe monthtive usage

Feature pr

Decimal placewhen daily rep

General param

Specifically, the report

From: <mail_address

Sent: <date, time>

To: <destination_addr

Subject: Hosted SwyxWare Report

Informational Report relevant for Accounti

> Licenses45

Explanation

> Name of the SwyxServerThis name is also the name of the virtual instance (VE).

hots Number of daily reports (snapshots) for this server which should be recorded.

ots Number of daily reports (snapshots) for this server which could not be recorded.These missing reports are supplemented with the help of an extrapolation.

Unique identification number of the registered SwyxServers (FES)

Start of operation of the SwyxServer (first registration on the license server)

Number of days, the SwyxServer was registered at the license server

Usage days for all used feature profiles.If a feature profile was not used in the report period, it is not listed in it.

Number of usage days for this function: in detail, the following functions are available:

• SwyxBasicFunctionality (Basic Functionality)• SwyxCTI• SwyxFax• SwyxVoicemail• SwyxRecord• SwyxBCR• SwyxECR• SwyxAdHocConference• SwyxPhone• SwyxMonitor• SwyxMobile

If a feature was not used in the report period, it is not listed in it.

Report of a single SwyxWare installation (front end server)

The reporting data that is sent by e-mail to the provider is listed individually for eachinstalled server and the related database. The format for each front end server is asfollows:

Explanation

Report generated: <date, time>

Date and time at which this report was generated.

Report Period Begin: <date>

Start date/time of the report

Report Period End: <date> End time of the report

License Key Serial Number

Serial number of the license key

Provider:Name:Street:ZIP Code:City:

Name and address of the provider. This address infor-mation is taken from the request for a permanent license key.Thus, if the report is sent for a test installation, these fields remain blank.

Server: <server_name

Nominal Daily Snaps

Missed Daily Snapsh

Client ID

Client active since:

Client registrations inreport period

Feature Profiles

Users with Feature <function>

> Licenses46

ing of the back end serverThe back end server puts the faxto the outside world and manages the licenses. Typically, noch a back end server. In order that the voice and fax channels

Explanation

Number of SwyxServers configured in this HostedSwyxWare installation.

ots Number of daily reports (snapshots) which could not be recorded.These missing reports are supplemented with the help of an extrapolation.

Usage days for all used feature profiles.If a feature profile was not used in the reporting period, it is not listed in it.

Number of usage days for this function: in detail, the following functions are available:

• Fax Client• CTI• Phone (Use of SwyxPhone)• Call Routing Manager• Silent Call Intrusion (passive)• Voicemail and Remote Inquiry• Conference with more than three participants

(SwyxIt! and SwyxPhone))• Conversation Recording• Graphical Script Editor

Usage days of speech channels(number of channels*Usage days)

Number of configured users

sic functionality

Number of users with the feature profile "Deactivated"These users cannot log on, but their configuration data is not lost.

Usage days of the fax channels(number of channels*Usage days)

s Usage days of the conference rooms

Licensing and reportand voice channels inusers are created on su

NumFaxChannels

NumConferenceRoom

Feature profile 'Deactivated'

The feature profile "Deactivated" serves to preserve the configuration of a user whois absent for a lengthy period. A user with this profile cannot log on and telephone,nor are calls forwarded to him.

The number of users with this profile is shown separately in the report.

Cumulative values of the complete Hosted SwyxWare installation.

The values of the complete Hosted SwyxWare installation are accumulated, thatmeans all usage days, configured conference rooms and users were added. Thiscumulative data is included in the e-mail that is sent as a report to Swyx.

NumUsers Number of configured users.Deactivated users will be counted as well as preconfi-gured users "Conference", "MobileExtensionManager" using the profile "No Features" and the user "Operator" using the profile "Advanced".

NumUsers without basic functionality

Number of users with the feature profile "Deactivated"These users cannot log on, but their configuration data is not lost.

NumConferenceRooms Usage days of the configured conference rooms (number of the conference rooms (internal numbers assigned to the user "Conference")*Usage days)

NumVoiceChannels Usage days of speech channels(number of channels*Usage days)

NumFaxChannels Usage days of the fax channels (number of channels*Usage days)

Explanation

Servers

Missed Daily Snapsh

Feature Profiles

Users with Feature <function>

NumVoiceChannels

NumUsers

NumUsers without ba

> Licenses47

are not entered in duplicate in the reporting, a SwyxServer that has no more than oneuser is not recorded in reporting.

7.3 Logging of invoice-relevant activities on SwyxServerAll changes of parameters that are entered in Reporting, and thus are relevant forbilling, are logged. The log contains the time of the change, the old and newparameter values, and the user making the change. The log file can be displayed inSwyxWare Administration or exported.


> Index48

RRemote Inquiry

Access to the mail server 19Report

Details 44E-mail addresses 44

Reporting 10Reproduction 40SService provider 8Serviceprovider 8SoftSwitch 8, 9SQL Server 8Static IP address 17STUN server 28SwyxGate 8SwyxIt!

Windows Vista 19SwyxPhone 9SwyxServer

account 9SwyxWare

Hosted 8System Requirements

SMTP mail server for Windows 19Windows Server 14, 20, 23, 37, 43

TTrunk group

to BES 28UUser 9User account 9User Authentication 9User name 9VVirtual Environment (VE) 9virtual network adapter 28Virtual telephone system (V-PBX) 9Virtuozzo 9

Bridged Mode 28Virtuozzo 3.5.1 SP1 17

Inde

AAccess AuthorAccount 9

on SwyxSUser 9Windows

AdministrationLevels 37

BBack end serve

Cold standLicense

Bulk AdministraCClient

Windows Clone templateCloning 40Collective AdmCompany 9Configure fax uConfigure SwyCustomer 9Customer's neDDatabase ServDHCP 19DNS 19EEnd customer FFailure of the liFax

RequiremFeature ProfileFeature profileFeature Profile

Initial 28File System 14Front end serv

x

ization 9

erver 9

9

r 8by 26 Key 26tion 40

Vista 19 27

inistration 40

ser 32xFax user 32

twork 19

er 8

9

cense server 43

ents 14 9 'Deactivated' 46s

er 8

HHard Drive Memory 14Hardware Requirements

Windows Server 14Hosted SwyxWare

Definition 8Hoster 8IIMAP4 19Informational Report 44Interlocation call limit 28IP Address

second 28LLevel

Administration 37Levels

Administration 37Licensing Server 13Location

Provider 28MMail server (SMTP) 19

System Requirements on Windows 19NNetwork Adapter

for VE 28Network requirements 18NTFS 14PParallels Infrastructure Manager(PIM) 17Parallels Management Console 17Parameters

Common to all FES 28PIN 9Private Server 27

Settings of the services 27Profile

Feature 9Provider 8

> Index49

Virtuozzo 4.0 17Virtuozzo Management Console(VZMC) 17Voice quality 18WWindows

Hardware Requirements 14Windows User Account 9XXML

Report 44

Date post:	22-Mar-2018
Category:	Documents
Upload:	ledat
View:	218 times
Download:	0 times