Aastra Corporate Headquarters

155 Snow Blvd., Concord, Ontario, Canada, L4K 4N9

Tel +1 905-760-4200

www.aastra.com

Ordering TWP Applications as of TWP R3.2 User’s guide Supported Platforms: Aastra 5000 / NeXspan Aastra 400 Aastra IntelliGate

®

Aastra MD Evolution Aastra 800 / OpenCom 100

Edition: 1.1 Date: February 2012 Doc no.: syd-0174_en Author: Cédric Loiseau

Aastra TWP R3.2

2

Contents

1 Introduction 3

1.1 Trademarks 3

1.2 Document description 3

2 TWP R3.2: Telephony Web Portal 4

2.1 Product overview 4

2.1.1 Services offered 4

2.1.2 Main new features in R3.2 5

2.1.3 Product structure 6

2.2 Ordering 7

2.2.1 Ordering a “customized” new system 7

2.2.2 Ordering and SME / Mobility bundle 13

2.2.3 Ordering a Try & Buy system 13

2.2.4 Ordering a demo pack for a distributor 14

2.2.5 Ordering summary 15

2.2.6 Ordering an extension 15

2.2.7 Ordering an upgrade to TWP 3.2 16

2.2.8 Ordering a migration to TWP 3.2 19

2.3 Prerequisites 26

2.3.1 General constraints 26

2.3.2 Particular constraints per feature 39

2.3.3 Capacities 49

2.4 Software subscription 52

3

1 Introduction

This document contains the TWP 3.2 ordering guide. To calculate the costs of TWP 3.2

configurations, we recommend using AastraPlan.

This document also gives information about specifications and capacities related to these

configurations. If you need a functional description of these applications, please refer to their

product guide.

TWP 3.2 can connect to different Aastra communication systems:

Aastra 5000 and NeXspan

Aastra IntelliGate®

Aastra 400

Aastra MD Evolution

Aastra 800 and OpenCom 100

This document is common to all platforms.

Paragraphs that are specific to the Aastra 5000 and NeXspan systems appear with double solid

orange border.

Paragraphs that are specific to the Aastra IntelliGate® and Aastra 400 systems appear with a

dashed blue border.

Paragraphs that are specific to the Aastra MD Evolution systems appear with a dotted green

border.

Paragraphs that are specific to the Aastra 800 and OpenCom 100 systems appear with a single

solid black border.

The reader should check for general availability status of the application for the communication

system in question.

Updates in this edition of the document are highlighted with a red line on the right side. This line

highlights new paragraphs as well as modified paragraphs. (Only content changes are highlighted;

not form changes.)

1.1 Trademarks

Aastra IntelliGate® is a registered trademark of Aastra Technologies Limited.

Microsoft Windows®, Microsoft Exchange® and Microsoft Outlook® are registered trademarks of

Microsoft Corporation.

Adobe® Flash®, Adobe® Flash Player®, Adobe AIR® are either registered trademarks or

trademarks of Adobe Systems Incorporated in the United States and/or other countries.

All other trademarks are trademarks of their respective proprietors.

The software and hardware designations referred to in this document are registered trademarks

and are subject to statutory provisions.

1.2 Document description

Document number: syd-0174

4

Document version: edition 1.1 (February 2012)

Valid for TWP 3.2.1111b patch A build 2 and patch B

Valid for Aastra IntelliGate® systems as of: I7.93 SP3

Valid for Aastra 400 systems as of: SW release 1.0

© 02.2012

Download document:

https://pbxweb.aastra.com/doc_finder/DocFinder/syd-0174_en.pdf?get&DNR=syd-0174

2 TWP R3.2: Telephony Web Portal

2.1 Product overview

2.1.1 Services offered

Telephony Web Portal R3.2 is a unified communications and collaboration suite based on web

services and open-standard technologies.

The TWP server offers the following applications; some are specific to a communication system.

See table below.

Aastra

5000

/ NeXspan

Aastra

IntelliGate®

Aastra

400

Aastra MD

Evolution

Aastra

800

TWP Browser

TWP Opencall

TWP Caller

TWP Alerter

TWP Audioshare

TWP Rules

TWP Recorder

TWP Videoshare

TWP Stats

TWP Toolkit

TWP Softphone

TWP OCS RCC Gateway

TWP Netviewer Web Conferencing

TWP Mail

on server

CPU2-

embedded

5

Aastra

5000

/ NeXspan

Aastra

IntelliGate®

Aastra

400

Aastra MD

Evolution

Aastra

800

TWP @Messaging

on server

CPU2-

embedded

= available = not available

Note: TWP Internet has been discontinued in TWP 3.2.

The TWP OCS CC Gateway feature is also part of TWP 3.2, but it is in the scope of a separate

ordering guide. Please consult the "Aastra – Microsoft Interoperability Solution" ordering guide for

more details.

For more information about the functions offered, please refer to the Product Guide.

2.1.2 Main new features in R3.2

The TWP Caller has been extended with some new features designed to a better usability:

Possibility to hide offline TWP contacts in contacts list

New tooltip in contacts list showing for TWP users their absence duration or the

current device profile name

Usage of TWP notes function between TWP users as a virtual “post-it” with visual

notification in the TWP Caller sidebar

Possibility to define a hotkey combination (ex: CTRL + F4) to dial a contact from the

contacts list

Possibility to dial any number highlighted in any application by a predefined hotkey

combination (ex: CTRL + F12)

TWP user preferences:

o Possibility to manually reset the terminal monitoring (in case of password change

on the terminal)

o Possibility to activate an email notification on missed calls

The TWP Toolkit is now offering a 1st-party TAPI Service Provider to ease 3rd party applications

integration (ex: dial from your Microsoft Outlook contacts). This Service Provider replaces the

Office plug-in that was provided with TWP 2.1. It is however for the moment compatible only with

32-bits operating systems.

TWP Netviewer Web Conferencing is a new module that offers, powered by Netviewer

technology (http://www.netviewer.com), the possibility to initiate and attend Web multimedia

conferences from your TWP Caller interface. Those conferences allow you to invite also external

(non-TWP) participants and share with them applications, voice, video, chat, whiteboard, etc…

This module can be offered only to customers already having an existing Netviewer contract.

TWP Internet is discontinued.

TWP Administration has also been slightly reworked for an easier and finer system setup:

6

Finer permissions management for chat, SMS, e-mail and calendar presence

Less advanced settings and more combo-boxes choices

New configuration “wizard” for first setup

All-in-one setup kit

Plus a few scalability changes: 2 types of TWP Media Server Video and Audio Channel licenses

are available with different scalability. “Proprietary” TWP Media Server Audio / Video channel

licenses can scale up to 24 channels in total on a server, whereas TWP Media Server Audio /

Video channel licenses “including HMP” can scale up to 100 channels in total on a server

(previously 64 channels in TWP 3.1).

2.1.3 Product structure

The solution comprises the following items:

The USB dongle: It is absolutely mandatory to plug this USB key into the TWP server. It

provides a strong license piracy protection. The XML software license keys are bound to a

specific USB dongle identifier and just stop working without it. Each dongle is identified by a

unique identifier like 03 FF FF xx xx xx xx. In case of virtualization, it is absolutely mandatory

to use a “USB over IP” device, as no virtual dongle solution is currently available.

The size of the USB Dongle is:

o Length: 41 mm including connector (29 mm excluding connector)

o Width: 17 mm

o Height (thickness): 8 mm

The TWP R3.2 DVD-ROM: It contains the following pieces of software:

o TWP Server: iPBX/communication system interfaces (CTI and directory), external

database and directory connectors, application modules (TWP Audioshare, TWP Stats,

TWP Recorder, etc…), Web Services API to third-party applications (TWP Toolkit, Web

administration (users, directories, licenses, etc.), directory browser, TWP database

(including mandatory additional components: Microsoft .NET Framework, Microsoft SQL

Server 2005 Express)

o Value-add 3rd party Tools (LDAP browser, Syslog, Dialogic HMP…)

o TWP 2.1 Configuration migration tool

o Documentation: User manuals, administration & configuration guide in available languages

Software licenses (XML file):

o User licenses: license for each application, it controls the number of named users declared

for the application.

Note: A named user can only have one main phone number to be controlled by TWP.

o The TWP Toolkit license gives access to specific application development APIs for a

certain number of developers. .

o The TWP Media Server (Audio or Video Channel) licenses control the number of IP

channels used by the TWP Audioshare/TWP Videoshare conference, TWP Mail / TWP

7

@Messaging, TWP Recorder and TWP Rules applications to record or play back greeting

messages but also to record and mix conversations.

Aastra 5000 / NeXspan: In case the TWP is bought for being connected to a NeXspan

communication system, the solution also contains the “NeXspan Call Server” CD-ROM:

intermediary between the iPBX network and the server, for implementing the directory browser

function. No similar CD-ROM is necessary for the Aastra 5000.

2.2 Ordering

2.2.1 Ordering a “customized” new system

2.2.1.1 The TWP pack

The TWP 3.2 pack must be ordered for any new sale. It contains:

The “TWP R3.2” software DVD-ROM

The USB dongle used to unlock the software (including TWP Browser)

NeXspan: The “NeXspan Call Server” CD-ROM, when bought for being connected to a

NeXspan iPBX,

The TWP “entry pack” containing 5 TWP Caller licenses

The TWP 3.2 pack can be used standalone to run the directory browser – TWP Browser, please

refer to 2.1.1 for availability information. For any other application, it must be used in combination

with the software licenses described in the paragraphs below.

Note: Aastra IntelliGate®: The Aastra IntelliGate® TWP connection license is not provided

anymore with the TWP pack. It must be ordered separately.

2.2.1.2 TWP Software licenses

2.2.1.2.1 TWP user licenses

All user licenses require the TWP Caller license, except TWP Opencall, TWP @Messaging and

TWP OCS CC Gateway.

Software user licenses are sold per step of 1 user. See the official price list for different pricing

options depending on the amount of licenses bought at a time and bound to the same USB

dongle.

The capacity corresponds to the total number of users declared or authorized on each TWP

server, regardless the fact that they effectively use these features or not.

User licenses are:

The TWP Opencall license can be acquired independently from any other license. It may be

extended by other TWP Opencall licenses.

The TWP Caller license is the basic license that gives to a named TWP user access to the

TWP Caller application. The relationship with other applications like TWP Alerter, TWP

Audioshare, TWP Stats, TWP Softphone, etc. is inter-dependency with the TWP Caller being

the basis. The TWP Caller license includes the right to use the TWP Opencall application, and

unlocks the corresponding features for the corresponding users, but does not provide an

additional TWP Opencall license/key.

The TWP Alerter and TWP Stats licenses require the TWP Caller license.

8

Aastra 5000 / NeXspan: The TWP Softphone is only available on Aastra 5000/NeXspan and

also requires the TWP Caller license.

The TWP Audioshare, TWP Recorder, TWP Rules, and TWP Videoshare licenses also

require the TWP Caller license. In addition, they require TWP Media Server Audio/Video

Channel licenses for managing audio/video channels in the media server. Two “proprietary”

TWP Media Server Audio channel licenses are included by default in the first order of TWP

Audioshare, TWP Rules, TWP Recorder and TWP Mail / TWP @Messaging (regardless of the

number of users, and without additional cost). Two “proprietary” TWP Media Server Video

channel licenses are included by default in the first order of TWP Videoshare (regardless of

the number of users, and without additional cost). Additional TWP Media Server Audio/Video

channel licenses can be purchased to meet the customer’s requirements.

o The TWP Audioshare, TWP Recorder, TWP Rules, and TWP Videoshare licenses give

access to the corresponding TWP application for one TWP user.

Note: For TWP Recorder, recording a conversation for a user and/or accessing recordings

history requires a TWP Recorder license.

The TWP Mail license provides an integrated voice mail as an extension of the TWP Caller. It

also requires the TWP Caller license.

The TWP @Messaging license providing an integrated voice mail and intelligent inbound calls

routing solution (combining TWP Mail and TWP Rules features). It includes by default two

“proprietary” TWP Media Server Audio channel licenses (allowing for example two

simultaneous voice message recordings), and must be acquired independently from the TWP

Caller license. Additional TWP Media Server Audio Channel licenses can be purchased to

meet the customer’s requirements

2.2.1.2.2 Other TWP licenses

Other licenses are:

The TWP Toolkit license enables you to develop specific 3rd party applications integrations or

applications for authenticated and supervised TWP Caller users. Each company making such

integrations (integrator), must first purchase the basic TWP Toolkit license allowing two

developers to work with the toolkit. Then, an extra TWP Toolkit developer license is needed

per extra developer. However, for each customer that buys an integration (made by the

integrator), the TWP Toolkit license is received for free. To get it, the end-customer must

provide the dongle identifier of the integrator company which made the integration by

purchasing the TWP Toolkit license.

Notes:

o TWP Toolkit now gives the right to use the TWP TAPI service provider for authenticated

and supervised TWP Caller users.

o In addition to the TWP Toolkit license, corresponding TWP licenses in order to use the

features via the toolkit (e.g. TWP Caller license).

The TWP Netviewer Web Conferencing license enables a certain predefined number of

authenticated and supervised TWP Caller users to create and attend Web conferences from

their TWP Caller application with other TWP users or external participants. The counter of the

license is only relevant for TWP Caller users, not for external participants.

9

Note: TWP Netviewer Web Conferencing also requires a contract with Netviewer AG. Since

the acquisition of Netviewer by Citrix Online, Netviewer contracts are not proposed anymore to

new customers. For customers already having an existing Netviewer contract, please contact

our sales personnel for more information about the Netviewer requirements.

The TWP Media Server Audio Channel license offers one IP audio channel for the TWP

Media Server. Audio channels can be used for the following features:

o TWP Recorder (to record and listen to conversations)

o TWP Rules (to record and broadcast announcements)

o TWP Mail (to record and play voice messages)

o TWP Audioshare (one channel per participant in an audio conference)

Notes:

o Each audio channel is configured statically by the administrator for only one application

o The administrator can manually configure one channel for another application if needed,

but there is no dynamic sharing of the channels between several applications.

o The two “proprietary” TWP Media Server Audio channel licenses which are received for

free when purchasing an application are preset only to work with the application they have

been received with: it is not possible to configure them for another application; neither

ignore them, except when purchasing TWP Media Server Audio channel licenses

“including HMP” – see section 2.2.1.2.3.

The TWP Media Server Video Channel license offers one IP video channel for the TWP

Media Server. Video channels can be used for the TWP Videoshare feature (conference with

voice, chat, video and desktop sharing). One channel is required per participant to a

Videoshare conference. To allow more flexibility, a video channel can also be configured to be

used as an audio channel: if needed, the administrator can change the configuration of a video

channel from the TWP Videoshare application to another TWP application requiring audio

channels like TWP Rules, TWP Audioshare, etc….

Notes:

o Each video channel is configured statically by the administrator for only one application

o The administrator can manually configure one channel for another application if needed,

but there is no dynamic sharing of the channels between several applications.

o The two “proprietary” TWP Media Server Video channel licenses which are received for

free when purchasing a TWP Videoshare license are preset only to work with TWP

Videoshare: it is not possible to configure them for another application; neither ignore

them, except when purchasing TWP Media Server Video channel licenses “including HMP”

– see section 2.2.1.2.3.

The TWP Media Server Audio Channel license can be transformed into a TWP Media Server

Video Channel license by acquiring the corresponding “TWP Media Server – Evolution from

Audio to Video Channel” license.

Tip!: the table below gives a guideline about an average number of media server channels needed

per module, depending on number of users

10

5 users 10 users 100 users 500 users 1000 users 5000 users

TWP Audioshare 4 8 16 32 48 64

TWP Rules 2 2 4 8 12 16

TWP Recorder

(manual)

2 2 6 12 18 24

TWP Recorder

(automatic)

2 4 16 32 64 128 (IP recording

only)

TWP Videoshare 3 6 12 24 36 48

TWP Mail 2 2 6 12 18 24

2.2.1.2.3 TWP Media Server Audio / Video channel licenses “including HMP”

For smaller TWP systems that need a total numbers of channels (audio + video) fewer than 24,

the media server component that manages the voice over IP coding is a proprietary TWP

component. In this case, “proprietary” TWP Media Server Audio / Video channel licenses have

to be bought. For larger systems that need a total numbers of channels (audio + video) up to 100

(maximum), this component is the Host Media Processing (HMP) software from Dialogic. In that

case, TWP Media Server Audio / Video channel licenses “including HMP” have to be bought.

The cost of the HMP licenses is included in the cost of the TWP Media Server Audio / Video

channel licenses “including HMP” (thus more expensive than “proprietary” TWP Media Server

Audio / Video channel licenses)

When HMP is included, an Ethernet card, which is independent of the built-in motherboard

network interface card, must be added to the TWP server. While ordering, you must indicate the

MAC address of this removable Ethernet card so that the voice HMP licenses associated with this

MAC address can be generated.

Note: It is not possible to extend “proprietary” TWP Media Server Audio / Video channel

licenses above 24 channels in total on a TWP system. Moreover, it is not possible to upgrade

“proprietary” TWP Media Server Audio / Video channels licenses into channel licenses

“including HMP”; the only possibility is to purchase new TWP Media Server Audio / Video

channel licenses “including HMP”. Both types of media server channel licenses do support

G.711A/µ and G.729 codecs.

2.2.1.3 Duplication licenses

Duplication is available only for the Aastra 5000 and NeXspan iPBX.

In case of redundant TWP solution (see section 2.3.1.1.4 for more details), it is necessary to

purchase the duplication pack and duplication licenses:

The duplication pack must be ordered first. Like the regular TWP pack, it contains 5

duplicated TWP Caller licenses, a spare dongle, but no software DVD.

Duplication licenses must then be bought for each user and feature that you want to

duplicate. These licenses will be bound to the spare dongle that is part of the duplication

pack.

11

Although it is recommended to buy the same features and quantities as on the main dongle, it is

possible to buy only a part of them. In this case, only the corresponding subset of features will be

functioning when the main dongle is not available. This case is not managed by Aastra Plan.

Note: For ordering a duplication TWP pack, the dongle identifier of the original system must be

provided.

The spare dongle may be used only as reserve dongle for the corresponding TWP Server

instance. It may not be used for running a second instance simultaneously with the instance that

uses the main dongle.

Cold standby redundancy is achieved through VMware and the original dongle is connected to a

“USB over IP” box. In case of ESX server failure, the backup TWP server is started and uses the

original dongle. In case of dongle failure, TWP does not automatically switch to the spare dongle.

It is necessary plug the spare dongle and set the system to use the duplication license key file,

which is bound to the spare dongle identifier.

SME bundles, Mobility bundles and “proprietary” Media server Audio / Video channels cannot be

duplicated.

2.2.1.4 IPBX/communication system licenses

Aastra 5000 / NeXspan:

User sets are managed by TWP thanks to VTI/XML or CSTA protocols. As most current phone

sets can be supervised in VTI/XML mode (for more details, refer to Section 2.3.1.3), in most

cases no CSTA license will be needed for monitoring user sets. CSTA licenses are not

included in TWP licenses, so if you need them anyway you must order them from the IPBX

price list.

Each IP line (used for each TWP Softphone, for each call queue, vor each virtual subscriber

used for intercom supervision, and for each TWP Media Server Audio or Video channel,

except for the IP flow replication mode of the TWP Recorder) requires a “proprietary” IP

license in the Aastra 5000 (a “generic” IP license will also do, but it’s more expensive) or an IP

license in the NeXspan. The type of IP license to be ordered depends also on the type of

A5000 Server used: standard or virtualized. The corresponding duplex IP licenses are also

required when connecting TWP to a duplex A5000 server. In the Aastra 5000 management

(AMP), a VTI/XML-IP set type will be used, and in the NeXspan administration, an Etherset IP

will be used. Standard A5000 architecture VoIP rules also apply to these IP lines, i.e. e.g. the

need for an EIP card for TDM-to-IP conversion, etc.

Aastra IntelliGate® :

The "TWP connection” license is needed. This license can be ordered as an Aastra

IntelliGate® part with the part number P0629-20952073 from the Aastra IntelliGate® part list.

This license is free of charge and allows using TWP with the corresponding Aastra

IntelliGate®. To order this license the Equipment ID (EID) of the customers’ communication

system is necessary.

Note: This license is NOT provided with TWP 3.2 pack for IntelliGate® or Aastra 400.

The "1 Aastra-SIP Terminal" (P0630-20952065) or "1 Standard SIP Terminal" (P0326-

20329240) license is required in the Communication System for each TWP Media Server

12

Audio channel or TWP Media Server Video channel. The appropriate configuration has to be

done.

Aastra 400 :

The "TWP connection” license is needed. This license can be ordered as an Aastra 400 part

with the part number A0000-20952177 from the Aastra 400 part list.

This license is free of charge and allows using TWP with the corresponding Aastra 400

communication system. To order this license the Equipment ID (EID) of the customers’

communication system is necessary.

Note: This license is NOT provided with TWP 3.2 pack for IntelliGate® or Aastra 400.

The "1 Aastra-SIP Terminal" (P0630-20952065, A0000-20952153 or A0000-20952154) or "1

Standard SIP Terminal" (P0326-20329240) license is required in the Communication System

for each TWP Media Server Audio channel or TWP Media Server Video channel. The

appropriate configuration has to be done except if you are using the CPU2 Application Card

(Aastra 470 only).

Aastra MD Evolution:

User sets are managed by TWP thanks to CSTA protocol. No license is needed on Aastra MD

Evolution side.

OpenCom 100 / Aastra 800:

User sets are managed by TWP thanks to CSTA protocol. The OpenCSTA 100 license (part

number 4516704) is needed for OpenCom communication system respectively Aastra CSTA

801/802 licence for Aastra 800.

Each IP line (for each TWP Media Server Audio or Video channel, except for the IP flow

replication mode of the TWP Recorder) requires an OpenAccess SIP 101 license (part number

4516703) or Aastra SIP User 801/802.

2.2.1.5 Server and factory integration

The TWP solution can be ordered:

as software only

On a server hardware

Embedded on CPU2 Application Card (Aastra 470 only)

If a server is ordered with TWP, the software and all the ordered parts can be integrated in the

Aastra factory provided that the corresponding service has also been ordered. Please note

however that the installed server operating system language is French, so this server offer is not

valid for all countries.

For information about the servers that Aastra proposes, please refer to the servers ordering guide.

If you use Aastra Plan to write your order, the factory integration service is automatically added if

you order the server.

Aastra does not sell or install VMware. As a consequence, only non-virtualized TWP servers can

be ordered.

13

2.2.2 Ordering and SME / Mobility bundle

To encourage the introduction of unified communications solutions into SME’s, Aastra offers an

attractive license bundle up to 100 users (bound to a single dongle identifier).

The SME bundle offers at a very competitive price a package containing:

o 1 TWP Caller license

o 1 TWP Alerter license

o 1 TWP Audioshare license

Note: Aastra MD Evolution: As the Audioshare feature is not available for Aastra MD Evolution,

a specific SME bundle has been defined for Aastra MD Evolution, containing only TWP Caller and

TWP Alerter licenses.

Aastra 5000 / NeXspan: The Mobility bundle offers at a very competitive price a package

containing:

o 1 TWP Caller license

o 1 TWP Alerter license

o 1 TWP Audioshare license

o 1 TWP Softphone license

Both bundles cannot be extended beyond 100 users. The rules for the TWP Media Server Audio

Channels are the same as for the individual Audioshare license.

Optionally, the TWP Bundles specially designed for SME’s or Mobility may be completed at

regular price with:

TWP applications licenses for any application available on the platform

Aastra 5000 / NeXspan: 100 users maximum also allowed for TWP OCS CC Gateway

licenses.

TWP Media server Audio/Video Channels licenses (“proprietary” or “including HMP”) (except

for Aastra MD Evolution)

TWP Toolkit licenses

3 years or 1 year of initial software subscription

Notes:

The TWP 3.2 pack for the corresponding platform must still be ordered as basis.

If at least one bundle has been purchased, the sum of TWP SME bundle + TWP Mobility

bundle + TWP Opencall + TWP Caller licenses cannot not exceed 100

2.2.3 Ordering a Try & Buy system

For our customers who would like to try the TWP 3.2 applications suite before a potential

purchase, Aastra offers a TWP 3.2 “Try & Buy” package per platform. This package is an

extended version of TWP 3.2 pack (see 2.2.1.1) – thus containing software DVD + USB Dongle +

5 TWP Caller licenses – but it also contains a special software license which is limited in time and

expires after three months.

14

Note: The three months validity period of the try & buy package starts when the order is registered

in the Aastra sales administration system.

This special trial license contains for 3 months:

Aastra MD Evolution: 20 users licenses for TWP Opencall

20 users licenses for the following applications: TWP Caller, TWP Alerter, TWP Audioshare,

TWP Rules, TWP Stats, TWP Recorder, TWP Videoshare – please refer to 2.1.1 for

availability information

Aastra 5000 / NeXspan: 20 users licenses for TWP Softphone and TWP OCS RCC Gateway

20 users licenses for TWP Mail (except on Aastra 5000 / NeXspan and Aastra MD Evolution)

20 “proprietary” TWP Media Server Audio channel licenses and 20 “proprietary” TWP Media

Server Video channel licenses

TWP Toolkit developers licenses

After 3 months, the trial license expires and the customer only keeps the basic TWP 3.2 pack with

the 5 TWP Caller licenses included. The trial license cannot be extended in time on the same

dongle identifier; however, the same dongle identifier can be extended with TWP software

licenses purchased at regular price.

2.2.4 Ordering a demo pack for a distributor

For our distributor partners which would like to have a TWP 3.2 system either for demonstration

purpose (showroom) or for their own internal use, we have created a TWP 3.2 demo package per

communication system. This package is a special version of TWP 3.2 pack (see 2.2.1.1) – thus

containing software DVD + USB Dongle – but it also contains 5 user licenses of each TWP

application available on the platform (unlimited in time).

This special demo pack contains the following licenses:

Aastra MD Evolution: 5 users licenses for TWP Opencall

5 users licenses for the following applications: TWP Caller, TWP Alerter, TWP Audioshare,

TWP Rules, TWP Stats, TWP Recorder, TWP Videoshare – please refer to 2.1.1 for

availability information

Aastra 5000 / NeXspan: 5 users licenses for TWP Softphone and TWP OCS RCC Gateway

Aastra IntelliGate® / Aastra 400: 5 users licenses for TWP Mail

5 “proprietary” TWP Media Server Audio channel licenses and 5 “proprietary” TWP Media

Server Video channel licenses

2 TWP Toolkit developers licenses

TWP demo pack for distributors may be completed at no charge with 3 years of software

subscription. Although this is free of charge, this software subscription consists in separate items

in the price list, which have to be ordered explicitly with the demo pack.

Note: The Aastra distributor is not allowed to transfer the property or lend the TWP 3.2 demo pack

directly or indirectly to an end-customer. The distributor name and installation location must be

provided during the order.

15

2.2.5 Ordering summary

The dependency relationships between the different TWP licenses are summarized in the table

below:

Notes:

* TWP @Messaging is a package that contains TWP Mail and TWP Rules and that does not

require the TWP Caller.

** TWP Browser is included in the TWP pack and needs no license

The procedure to follow for ordering a new TWP is summarized in the table below:

Order the server (or the CPU2 Application Card, for Aastra 470 only) if necessary.

Order the TWP pack

Order the licenses or SME / Mobility bundle (<=100 users).

If you need TWP Media Server Audio / Video channel licenses “including HMP”, indicate

the Ethernet card MAC address which serves as identifier.

If you need to use a toolkit integration that was developed by a third-party integrator,

indicate the dongle identifier of your integrator for receiving the TWP Toolkit license for

free.

Depending on the iPBX/communication system type and the features you need, order

the iPBX licenses (VoIP channels, SIP or IP licenses …).

Note: if you use AastraPlan for ordering TWP, those rules will be applied automatically

2.2.6 Ordering an extension

2.2.6.1 Extending a “customized” system

For each application, you can increase the number of users or channels by buying additional

licenses. Ordering an extension will consist in ordering the same articles as the ones for a new

sale, starting again from 1. The original system dongle identifier must be provided during the

extension order.

16

Example: on a site with 100 TWP Alerter users, you can extend up to 110 TWP Alerter users by

ordering 10 * "TWP Alerter - 1 user (from the 1st to the 10th user)" licenses.

Please check, while extending the number of users of applications that require the TWP Caller

license, that each user receiving a new application license does have a TWP Caller license.

In addition, it is also possible to convert some licenses into other applications:

A TWP Opencall user can be converted to a TWP Caller user through an evolution license

(“TWP Opencall 3.2 to Caller - 1 user”). The amount of users to be converted is not restricted.

Example: on a site with 1000 Opencall users, you can convert 100 users to TWP Caller users

by ordering 100 * “TWP Opencall 3.2 to Caller - 1 user” evolution licenses.

Aastra 5000 / NeXspan: A TWP OCS RCC Gateway user can be converted to a TWP Caller

user through an evolution license (“TWP RCC Gateway 3.2 to Caller - 1 user”). The amount of

users to be converted is not restricted.

Example: on a site with 50 TWP OCS RCC Gateway users, you can convert 40 users to TWP

Caller users by ordering 40 * “TWP RCC Gateway 3.2 to Caller - 1 user” licenses.

Some or all TWP Media Server audio channels may be converted to video channels through

an evolution license.

Example: on a site with 15 TWP media server audio channels, you can change to 10 TWP

media server audio channels and 5 video channels by ordering 5 * "Evolution from 1 audio to 1

video Media Server channel" licenses.

2.2.6.2 Extending an SME / Mobility bundle

The same logic applies as to extending a customized system, but please keep in mind that the

total number of users may not exceed 100 when at least one bundle has been purchased.

2.2.6.3 Extending a demo pack for a distributor

A TWP demo pack for distributor can be extended with users or TWP Media Server channel

licenses by buying additional licenses at special distributor discounted price (50%).

There is no limit in terms of number of users or channels for the extension, the only constraint is

that the Aastra distributor is not allowed to transfer the property or lend the licenses directly or

indirectly to an end-customer. The distributor name, installation location and dongle identifier must

be provided during the extension order.

2.2.7 Ordering an upgrade to TWP 3.2

2.2.7.1 Upgrading a system not covered by the software subscription

Depending on the TWP release you are using (2.x or 3.1), you will need to order the

corresponding upgrade license (the TWP upgrade from 2.x to 3.2, or the TWP upgrade from 3.1 to

3.2) for each owned TWP user or channel license.

All licenses being hosted on the same TWP server, be careful to the fact that you cannot run

simultaneously on the same system TWP 2.x or 3.1 and 3.2 licenses. Hence, you will have to

upgrade all the TWP licenses you have on your system, otherwise, you will not be able to use the

non-upgraded licenses anymore from the previous TWP version.

17

In any case, the order must be accompanied by the corresponding original dongle identifier. The

table below summarizes the correspondence between application modules / channels / packs in

TWP 2.x and TWP 3.2:

TWP 2.x TWP 3.2

TWP Browser <No license anymore needed for this feature>

TWP Opencall TWP Opencall

TWP Caller TWP Caller

TWP Alerter TWP Alerter

TWP Phone VoIP TWP Softphone

TWP Phone TWP Audioshare (incl. 2 “proprietary” TWP Media Server Audio channel

licenses)

TWP Visio TWP Videoshare (incl. 6 “proprietary” TWP Media Server Video channel

licenses)

TWP Stats TWP Stats

TWP Rules TWP Rules (incl. 2 “proprietary” TWP Media Server Audio channel

licenses)

TWP Recorder TWP Recorder (incl. 2 “proprietary” TWP Media Server Audio channel

licenses)

TWP Media Server “proprietary” TWP Media Server

Audio channel licenses - max 24

total channels per server

TWP Media Server Audio

channel licenses “including

HMP” - max 100 total channels

per server

“proprietary” TWP Media Server

Video channel licenses - max 24

total channels per server

TWP Media Server Video

channel licenses “including

HMP” - max 100 total channels

per server

TWP Toolkit TWP Toolkit

TWP Internet <Feature not available anymore>

TWP OCS RCC GW (2.1) TWP OCS RCC GW

TWP SME Pack, Orange Pack, Benelux

Pack

TWP SME Bundle

TWP Demo distributor pack TWP Demo distributor pack (includes Upgrade Pack)

Software

To upgrade the software of a customized system without software subscription, you need to order

the “Pack upgrade to TWP 3.2”. This pack contains the TWP 3.2 software DVD.

Licenses:

For all the other licenses, you have to order the corresponding upgrade path license with the

corresponding capacity.

18

Example: for a TWP R2.1 site with 100 TWP Caller users, including 50 TWP Alerter users, you

need to order:

1 * “Pack Upgrade TWP 3.2 all platforms - Incl. DVD TWP 3.2 software”

100 * "License Upgrade TWP Caller v2.X->3.2 - 1 user”

50 * " License Upgrade TWP Alerter v2.X->3.2 - 1 user”

Case of TWP SME pack/bundle

A TWP SME bundle from a previous version may be upgraded with the “Pack upgrade to TWP

3.2” and the corresponding upgrade license bundle. This license bundle contains the TWP Caller,

TWP Alerter and TWP Audioshare license upgrade.

Example: to upgrade an SME pack 2.1 for 10 users, you have to order:

1 * “Pack Upgrade TWP 3.2 all platforms - Incl. DVD TWP 3.2 software”

10 * “License Upgrade TWP License Pack SME, OBS, Benelux v2.X->3.2 - 1 user”

Case of TWP demo pack for distributor

Most demo packs for distributor of previous TWP releases are covered by software subscription

clause. If so, please refer to section 2.2.7.2 for more details. In case they are not, it is possible to

order the corresponding demo pack upgrade kit. This kit contains the software DVD and the

upgrade TWP licenses, thus the “Pack upgrade to TWP 3.2” is NOT needed.

Example: to upgrade a TWP Distributor pack 2.1 – NOT covered by software subscription, you

have to order:

1 * “Upgrade Distributor pack v2.X->3.2 A5000 Incl. DVD TWP3.2 + 5 Users all modules”

Note: Upgrade license are now not sold together with software subscription.

For other licenses, the procedure is the same as for a customized system

2.2.7.2 Upgrading a system covered by the software subscription

There is a kit used to upgrade a site (= same dongle identifier) and all the licenses covered by

software subscription.

For a TWP customized site, a TWP SME pack, or a TWP distributor demo pack, you just need to

order:

1 * “Pack upgrade via Software Subscription to TWP R3.2 (DVD + Licenses)”

This free item enables you to obtain new TWP 3.2 software DVD-ROM and corresponding

upgrades of the software keys covered.

Note: The media server channel licenses obtained through software subscription upgrade are

always “proprietary” TWP Media Server Audio / Video channel licenses, thus a maximum of 24

channels can be obtained, and otherwise TWP Media Server Audio / Video channel licenses

“including HMP” must be purchased (maximum 100 channels per TWP server).

For all licenses hosted on the same TWP server, be careful to the fact that you cannot run

simultaneously on the same system different TWP versions licenses (ex: 1.x, 2.x, 3.1, 3.2). Hence,

please make sure that all the TWP licenses you have on your system are covered by software

subscription, otherwise, you won’t be able to use the covered licenses not covered by software

subscription anymore.

19

The order of the upgrade must be accompanied by the corresponding original dongle identifier.

2.2.8 Ordering a migration to TWP 3.2

For Aastra customers who previously invested into some Aastra CTI solutions like TAPI Open

Suite or i2052 on NeXspan/Aastra 5000 or OfficeSuite on Aastra IntelliGate® / Aastra 400, it is

now possible to purchase an evolution license towards TWP 3.2 Caller at special discounted price.

2.2.8.1 Migration from TAPI Open Suite / i2052

Aastra 5000 / NeXspan:

Aastra 5000 / NeXspan customers which use the TAPI Open Suite or i2052 to achieve CTI

functions can now migrate to TWP 3.2 at a special price. A TAPI Open Suite or i2052 user license

can be converted to a TWP 3.2 Caller license.

Note: TWP 3.2 does now offer a TAPI-compatible interface to external application to access

telephony functions on NeXspan/Aastra 5000. The extra purchase of the TWP 3.2 Toolkit license

is needed.

Note: TWP 3.2 does not offer all i2052 features for Aastra 5000 / NeXspan. It offers instead an

alternative CTI solution based on TWP Caller application. Please refer to the table below for

detailed available features list

i2052 TWP 3.2 Caller

Telephony functions/ CTI for system terminals

Click to call, drag & drop dialing

Phone number reformatting / clean up

Call control (forward call, hang up, DTMF, etc…)

Call forward management

Mobility: change current device

Virtual speed dials and busy lamp field

External voicemail system management

Call journal

Inbound, outbound, missed calls (except missed calls)

Call journal sharing

Multiple directories connection

Personal / private directory

Search in multiple directories

Advanced search in multiple directories

Link to external web directories (yellow pages, etc…)

Unified communications

Chat

20

i2052 TWP 3.2 Caller

SMS

Add notes on a contact

Actions/events log on contact

Presence management

Telephony presence (speaking on the phone, alerting,

etc…)

Proprietary instant presence

Calendar presence (Microsoft Exchange / IBM Lotus

Domino)

Call forward upon presence status

Optional TWP Softphone add-on

Volume control, mute microphone

Answer, hang up from compatible wireless headset

DTMF dialpad

To be able to migrate from TAPI Open Suite or i2052 to TWP Caller, the order must be

accompanied by following items:

Proof of license ownership for TAPI Open Suite / i2052 from the end-customer (ex: identifier

number, license number.)

End-customer information : company, location, country

Aastra reseller name

Optionally, the i2052 / TAPI Open Suite migration may be completed at regular price with:

3 years or 1 year initial software subscription

2.2.8.2 Migration from Open Interfaces Platform/OfficeSuite

Aastra IntelliGate® / Aastra 400:

Aastra IntelliGate® / Aastra 400 customers who use the OfficeSuite application to achieve CTI

functions can now migrate to TWP 3.2 at a reduced price. An OfficeSuite user license can be

converted to a TWP 3.2 SME bundle license containing TWP Caller + TWP Alerter + TWP

Audioshare (also known as “Web CTI Pack Popup and Conference”).

Note: TWP 3.2 does not offer all OIP/OfficeSuite features for Aastra IntelliGate® / Aastra 400. It

offers instead an alternative CTI solution based on TWP Caller, TWP Alerter and TWP Audioshare

applications. Please refer to the table below for detailed available features list

21

OfficeSuite1

TWP 3.22 Notes

Telephony functions/CTI for system terminals:

Answer call

Outgoing dialing

End call

Announcement to user

Brokering

Call Charge Display

Call Deflection (Forwarding a call during the

ringing phase)

Call Forwardings: Unconditional (CFU), No

Reply (CFNR), Busy (CFB), Do Not Disturb

(DND)

Call Hold

Calling Line Identification Presentation (CLIP)

Call Transfer

Call Transfer without prior notice

Call Waiting

Callback (CCBS and CCNR; Completion of

Calls to Busy Subscribers and Completion of

Calls on No Reply)

Conference (3 or 6-party)

Conference (max 10-party) with control over

participants (mute, exclude)

Customizable pop-up window on

inbound/outbound call (contact picture / 3rd

party software integration with contact data /

link to Exchange contact)

Dual Tone Multi-Frequency (DTMF) dialing

Fetch call

Key telephone support

Message to busy user

Park

1 Office Suite + Phone book connector + Microsoft Exchange Connection + some OIP features

2 Pack TWP 3.2 for Aastra IntelliGate

® / Aastra 400 + TWP Caller + TWP Alerter + TWP Audioshare

22

OfficeSuite1

TWP 3.22 Notes

Reject call during the ringing phase

User-defined functions (macros/function

commands)

TWP 3.2 Caller: user-defined shortcut key

to dial contact

Presence Profiles:

Audio profiles

Call Forwarding Busy (CFB) destinations

Call Forwarding on No Reply (CFNR)

destinations

Call Forwarding Unconditional (CFU)

destinations

Control via OIP calendar or external calendar

(e.g. Microsoft Exchange)

TWP offers control by external calendar or

TWP presence

Create several presence profiles. TWP offers an alternative solution to

presence profiles called "simple Rules"

(without OneNumber constellation

support)

Display Profiles TWP offers an alternative solution to

presence profiles called "simple Rules"

Call Forwarding destinations (CFx) for

external calls

TWP only allows similar forward

destination for internal and external calls

Call Forwarding destinations (CFx) for internal

calls

TWP only allows similar forward

destination for internal and external calls

Function Profiles

Notification Profiles

Set presence status

Voice Mail Profiles TWP offers an alternative solution with

TWP "Messaging" presence status

Presence Indicator:

Presence Indicator via all OIP users

TWP only provides presence indicator to

TWP users

OIP Server:

Configuration of system terminals

Call lists (e-mail notification in the case of

unanswered calls)

PUM (Personal User Mobility)

Free seating (Aastra 400 only)

TWP can supervise the free-seating

23

OfficeSuite1

TWP 3.22 Notes

terminal

Notification of events:

Answered and unanswered calls

TWP 3.2 Caller: notification of

unanswered calls only

Voice Mail messages from the standard Voice

Mail system

TWP Caller supports from IntelliGate I7.9

MR1 visual notification only (no

management of Voice Mail messages

from the standard Voice Mail system in

the client application).

However, TWP offers an alternative

solution to standard Voice Mail system

with TWP Mail (TWP Mail license as well

as additional voice channels not included

in evolution from OfficeSuite)

E-mail message

Calendar events ? Needs special TWP Toolkit integration

(TWP Toolkit license not included in

evolution from OfficeSuite)

I/O Events

Notification to destinations:

Display on a terminal (ATAS)

TWP Mail does not offer the notification or

management of voicemail messages on

system terminals display; however,

notification by Message Waiting Indicator

led is available.

Text message

E-mail message

E-mail message with attached Voice Mail

message of the standard Voice Mail system

(wav or mp3)

TWP offers an alternative solution with

attachment of TWP Mail voicemails

(TWP Mail license not included in

evolution from OfficeSuite)

Voice Mail message in e-mail read/delete

synchronization

OIP: synchronization only available with

Microsoft Exchange

TWP: TWP Mail voicemails (TWP Mail

license not included in evolution from

OfficeSuite) synchronization available with

Microsoft Exchange and IBM Lotus Notes

24

OfficeSuite1

TWP 3.22 Notes

Triggering of an I/O event

needs special TWP toolkit integration

(TWP Toolkit license not included in

evolution from OfficeSuite)

Notification: Other features:

Allocation of filtering rules

Connection and access:

Connecting Aastra IntelliGate® / Aastra 400

directories

Connection of Microsoft Exchange

Connection to LDAP directories

Connection to ODBC directories

Access to the Twixtel external phone-book

directory (CH)

Access to the Das Telefonbuch external

phone-book directory (DE)

Access to the global address list of the Active

Directory

Access to web-based internet directories (e.g.

www.telsearch.ch) and display contact data

Access to web-based directories can be

achieved in TWP Alerter through

customized HTML Alerter pop-up card

(TWP Alerter license is included in

migration from OfficeSuite)

Import/export of other directories (CSV)

Access to web-based CRM applications and

display contact data

Access to web-based CRM applications

can be achieved in TWP Alerter through

customized HTML Alerter pop-up card

(TWP Alerter license is included in

migration from OfficeSuite)

Directory functions:

Search in directories with dialling by name

from client application

Note: for all directories except Twixtel and

Das TelefonBuch,

TWP keeps a local copy of the directory

content in its database,

optimized to provide quick search results

Search in directories with dialling by name

from system terminal

TWP provides this features thanks

TWP Browser, included in Pack TWP 3.2

for Aastra IntelliGate® / Aastra 400

Note: available for all directories except

25

OfficeSuite1

TWP 3.22 Notes

Twixtel and Das TelefonBuch

Search in directories with Quickdial dialing by

name

Name display to client application

Name display to system terminal

TWP provides this feature thanks to

TWP Browser, included in Pack TWP 3.2

for Aastra IntelliGate® / Aastra 400

Synchronization between PBX directories and

Microsoft Exchange directories

Synchronization of TWP directory with

Microsoft Exchange

Microsoft Exchange connection:

Data source for private contacts.

Integration of the public contact folders

Integration of the private calendar

OIP Call Centre:

Agent control - workgroups (log on and log off,

pause, wrap up)

TWP offers an alternative solution to OIP

Call Centre workgroups with

TWP Audioshare call queue feature but

without call routing, call tickets or statistics

(TWP Audioshare license is included in

evolution from OfficeSuite)

Call Center status (Waiting calls) in application

window

TWP offers an alternative solution to OIP

Call Centre workgroups with

TWP Audioshare call queue feature

(TWP Audioshare license is included in

evolution from OfficeSuite). Waiting calls

are displayed in the TWP Caller interface.

Miscellaneous:

Automatic terminal selection in One Number

and Twin Comfort configuration

Terminal selection is manual in TWP.

Client application automatic update

Client application installation needs no

admininistrator rights on workstation

26

OfficeSuite1

TWP 3.22 Notes

Display Webcam picture when ringing at the

door intercom system or unoccupied reception

? TWP offers an alternative solution to

display a webcam picture, when available

via a Web URL link: it is possible to

manually click on such a link that would

be configured in TWP Alerter pop-up card

(TWP Alerter license is included in

evolution from OfficeSuite).

Free configurable keyboard shortcuts ? TWP offers configurable keyboard

shortcuts to dial contacts or any

highlighted number only

KNX integration (programmable control keys)

PBX alarming key programming (Redkey)

PBX function keys

Twin Comfort DECT support

To be able to evolve from OfficeSuite to TWP, the order must be accompanied by following items:

Proof of license ownership for OfficeSuite from the end-customer (ex: license number./sheet)

End-customer information : company, location, country

Aastra reseller name

Optionally, the OfficeSuite evolution may be completed at regular price with:

TWP Media server Audio channel licenses (“proprietary” or “including HMP”)

3 years or 1 year initial software subscription

2.3 Prerequisites

2.3.1 General constraints

The constraints listed in this section are common to all TWP features. Please see also section

2.3.1.6 for the constraints that are specific to some features.

2.3.1.1 TWP server prerequisites

2.3.1.1.1 Operating systems

The TWP 3.2 server 3 is compatible with:

Microsoft Windows Server 2003 (32-bit)

Microsoft Windows Server 2003 R2 (32-bit)

Microsoft Windows Server 2008 Standard/Enterprise/Datacenter (32-bit & 64-bit)

3 Including Media Server Audio / Video channel licenses “including HMP”.

27

Microsoft Windows Server 2008 R2 Standard/Enterprise/Datacenter (64-bit)

In English (US), French and German releases only.

When TWP Media Server Audio / Video channel licenses “including HMP” are used, additional

restrictions apply:

With Windows Server 2008 (not R2), Service Pack 2 is required

With Windows Server 2008 and Windows Server 2008 R2, a system with BIOS support for the

HPET Timer is required. An HPETTool utility is provided on the TWP DVD to assist in

determining motherboard compatibility.

TWP server configurations with maximum 10 users and 50 total points (only with TWP

“proprietary” Media Server Audio / Video channel licenses) are also compatible with Microsoft

Windows 7 Business/Enterprise/Ultimate (32-bit & 64 bit) in English (US), French and German

release

Note: Virtualization creates several extra restrictions; please refer to section 2.3.1.1.4 for more

details.

2.3.1.1.2 Hardware requirements

The platform prerequisites depend on the capacity of the target system:

TWP

CTI

users

Max

total

points

Max

calls

per

hour

TWP

Opencall

clicks

per hour

TWP

Browser

only

calls per

hour

Microsoft

Windows OS

CPU RAM HDD

10 50 150 750 240 7 Business /

Enterprise /

Ultimate

1 Pentium 4 - 3.GHz 1 Go SATA

10 50 150 750 240 Server 2003 / 2008 1 Pentium 4 - 3.GHz 1 Go SATA

25 125 150 750 240 Server 2003 / 2008 1 Pentium 4 - 3.GHz 2 Go SATA

100 1000 600 3000 960 Server 2003 / 2008 Core 2 Duo E8500

LGA 775 (Dual Core)

2 Go SATA

500 5000 3000 15000 4800 Server 2003 / 2008 1 x Xeon® Dual core 3 Go SAS/SCSI

500 10000 3000 15000 9600 Server 2003 / 2008 1 x Xeon® Quad core

E5405

3 Go SAS/SCSI

1000 5000 6000 30000 4800 Server 2003 / 2008 1 x Xeon® Dual core 4 Go SAS/SCSI

1000 10000 6000 30000 9600 Server 2003 / 2008 1 x Xeon® Quad core

E5405

4 Go SAS/SCSI

4000 20000 12000 60000 32000 Server 2003 / 2008 2 x Xeon® Quad core

E5462

4 Go SAS/SCSI

4000 40000 12000 60000 32000 Server 2003

enterprise / Server

2008 64 bits

2 x Xeon® Quad core

E5462

6 Go SAS/SCSI

28

TWP

CTI

users

Max

total

points

Max

calls

per

hour

TWP

Opencall

clicks

per hour

TWP

Browser

only

calls per

hour

Microsoft

Windows OS

CPU RAM HDD

8000 40000 20000 60000 32000 Server 2003

enterprise / Server

2008 64 bits

2 x Xeon® Quad core

E5462

8 Go SAS/SCSI

8000 80000 20000 60000 32000 Server 2003

enterprise / Server

2008 64 bits

2 x Xeon® X5492

Quad Core

8 Go SAS/SCSI

The number of “TWP CTI users” is defined as the sum of TWP Caller users, TWP Opencall users

and TWP RCC Gateway users on a TWP system.

How to find the proper hardware configuration using this table?

Calculate your total number of “points” depending on how many “TWP CTI users” would be using

which application. Each application counts for a certain number of points;

TWP Caller: 3 points

TWP Alerter: 1 points

TWP Softphone: 0 point

TWP Audioshare: 3 points

TWP Rules: 2 points

TWP Stats: 1 points

TWP Videoshare: 3 points

TWP Mail: 1 points

TWP Recorder: 2 points

TWP @Messaging: 3 points

TWP OCS CC Gateway: 2 points

TWP Opencall on Aastra 5000 / NeXspan: 1 point (when mixed with others TWP Applications)

TWP Opencall on Aastra IntelliGate® / Aastra 400 : 2 points

TWP Opencall on Aastra 800: 0 point

TWP Opencall on Aastra MD Evolution: 0 point

TWP Browser: 2 points (when mixed with others TWP Applications)

Aastra 5000 / NeXspan: When the TWP server is dedicated for TWP Opencall on Aastra 5000 /

NeXspan platform, use the column « TWP Opencall clicks per hour ».

When the TWP server is dedicated for TWP Browser only, use the column « TWP Browser only –

calls per hour ».

If your total number of points OR number of “TWP CTI users” OR traffic exceeds those on a line,

jump to the first matching line in the table.

29

Example: for a TWP R3.2 site with 25 TWP Caller users, 25 TWP Alerter users, 15 TWP Recorder

users, 15 TWP Videoshare users and 150 calls per hour, you need the following configuration:

Total number of points= 25 * 3 + 25 * 1 + 15 * 2 + 15 * 3 = 175 points

Number of TWP CTI users = 25

Calls per hour = 150

The exceeded total number of points (above 125) obliges to select the following configuration in

the table:

TWP

CTI

users

Max

total

points

Max

calls

per

hour

TWP

Opencall

clicks

per hour

TWP

Browser

only calls

per hour

Microsoft

Windows OS

CPU RAM HDD

100 1000 600 3000 960 Server 2003 / 2008 Core 2 Duo E8500

LGA 775 (Dual Core)

2 Go SATA

Miscellaneous engineering rules:

Above 3,000 calls per hour: SAS/SCSI hard disk is recommended, a standard edition of

Microsoft SQL server is recommended (not provided by Aastra)

Above 300,000 directory contacts: a standard edition of Microsoft SQL server is recommended

(not provided by Aastra)

Above 10,000 calls per hour and without TWP Media Server Audio / Video channel licenses

“including HMP”: Microsoft Windows 2008 server is recommended

When using TWP Audioshare or TWP Videoshare application: a Dual Core CPU is

recommended

Hard disk drive : 40 GB minimum size, extra storage capacity is needed for TWP Recorder /

TWP Mail / TWP @Messaging voice messages or recorded conversations (1,5 KB/s or 6

MB/h)

The number of Media Server channels also depends on the processor: The TWP Recorder

application in IP flow replication mode uses IP recording channels that are only known by TWP

server. The TWP Recorder application in other modes and the TWP Rules, TWP Audioshare,

TWP Videoshare and TWP Mail / TWP @Messaging applications use IP channels corresponding

to IP (SIP on Aastra IntelliGate® / Aastra 400 / Aastra 800) extensions of the communication

server. In all cases they correspond to TWP Media Server Audio/Video licenses. The capacity for

each case (not concurrent) according to processor is given in the table below:

Processor Media server channels TWP recorder – IP recording

media server channels

1xPentium® 4 20 (G711) 30 – need HMP

Xeon® Dual core 32 (G711/G729) – need

HMP

64 – need HMP

2xXeon® Dualcore 64 (G711/G729) – need

HMP

128 – need HMP (scales up to

128 only for IP recording)

30

Whenever the HMP software from Dialogic is used for TWP Media server channels, a removable

Ethernet card is required on the server, to link the HMP licenses to the MAC address of this card.

In case the server would need to be replaced, this would enable the transfer of the HMP licenses

to the new server without having to purchase them anew, just by transferring the removable

Ethernet card to the new server.

Network topology constraint: If the connected LAN is made of separate layer 2 switches for

data and voice network without inter network (LAN) routing, it is possible to connect TWP server

with two network interface cards (one to the data network, one to the voice network).

Note: Aastra 5000 / NeXspan: In the case above, the TWP Softphone does not work (as it needs

to connect both to the TWP server and to the Aastra 5000 call server).

The use of a USB dongle requires a free USB 1.1 or 2.0 port.

Note: Parallel dongles are not available anymore from Aastra, only USB dongles are now shipped

2.3.1.1.3 Other software considerations

The server computer must be dedicated to TWP. In particular, the following applications must

NOT be installed on the server hosting TWP server:

Microsoft Exchange Server (Windows 2003 Small Business Servers for instance is not

supported)

Microsoft Active Directory domain controller

Any web server other than Microsoft IIS and using port 80

However, TWP can be installed on the same server OS as ACP (Aastra Communication Portal)

application. Please refer to the latest ACP ordering guide for information about TWP and ACP

cohabitation within the same server OS.

2.3.1.1.4 Impacts of virtualization / duplication

All server-side components of TWP 3.2 can now run in a virtual machine. Only VMware vSphere

4.x is supported for virtualization.

For real-time guarantee considerations, the Media Server component of TWP 3.2 can now run in a

virtual machine only when used with TWP Media Server Audio / Video channels “including

HMP”. The following restrictions apply:

Dialogic HMP 3.0 Service update 289 software or later is needed (available on the TWP DVD)

TWP Server Operating system must be Microsoft Windows Server 2003 (32-bit)

Note: When used with TWP “proprietary” Media server Audio / Video channels, then it is still

mandatory to install the TWP media server component on a separate, non-virtualized machine

(see TWP Administration & Configuration guide – section 17.6 “Remote Media Server

configuration” for instructions in setting up a separate TWP media server). The following

restrictions apply:

The separate (non virtual) machine running the TWP Media Server must be on the same LAN

as the ESX servers running the virtual machine that contains the other server-side

components of TWP.

The separate (non virtual) Media Server is a single point of failure: is not redundant.

31

If the version of VMware is 4.1 and the virtual machine is always hosted by the same hardware

server (no redundancy, no VMotion, etc.), then the USB dongle may be plugged directly in a USB

port of the hardware server.

The "High Availability" feature of VMware can be used for offering redundancy to TWP. In this

case, the following restrictions apply:

All ESX servers that are expected to host the virtual machine must be part of the same LAN,

for allowing the IP address(es) of the TWP server being constant.

A Storage Area Network (SAN) must be deployed for storing the virtual machine. Aastra does

not make any recommendation on the brand, type and version of the SAN solution. The

presence of the SAN probably imposes some additional (optical fiber or not) network interfaces

in each ESX server.

Network interface(s) on each ESX server have to be duplicated. Please ensure that duplicated

network interfaces are on separate cards for avoiding a card being a single point of failure.

A "USB over IP" solution must be deployed for allowing the virtual machine accessing the USB

dongle from whichever ESX server that hosts it. The Digi International AnywhereUSB 2-ports

device is available in the Aastra price list. But any other USB over IP solution can also be

used; in this case, please make sure that the selected solution is compatible with the operating

system of your TWP server and starts automatically without requiring a user starting a

Windows session on the server.

The dongle is a single point of failure: it is not redundant (except if you get a spare dongle

when purchasing duplication)

Parallel dongles are not supported.

Virtualized TWP servers have the same requirements as the classical non-virtualized TWP

servers. Hence, in case of a virtualized TWP server, you should ensure that the VMware server

provides to the virtualized TWP server the equivalent of the hardware server requirements

described in the section 2.3.1.1.2 above (dedicated resources).

2.3.1.2 Client PC Specifications

2.3.1.2.1 Operating systems

The TWP 3.2 client applications are compatible with the following operating systems - no

language restriction:

Microsoft Windows XP Professional (32-bit)

Microsoft Windows Vista (32-bit & 64-bit)

Microsoft Windows 7 (32-bit & 64-bit)

Linux OS

Mac OS

Note: TWP Softphone now officially supports 64-bit versions of Microsoft Windows Vista and

Microsoft Windows 7 (32-bit & 64-bit) operating systems

There are 3 possible modes to run TWP:

1. “Desktop integration” mode – TWP is launched like a regular desktop application and integrates

smoothly within the user desktop

32

Requirements: any Microsoft Windows, Linux or Mac OS X supporting Adobe AIR Client

version 2.6 (see Adobe pre-requisites for more detailed information)

Note: In “Desktop Integration” mode, Adobe Flash Player 9 or above is needed for the

following applications – see “pure web mode” below for requirements details:

TWP Administration: accessing the Admin pages in a web browser

TWP Stats: accessing the call statistics in a web browser

TWP Recorder: accessing recordings management interface in a web browser

Some restrictions however apply to some features:

Aastra 5000 / NeXspan: TWP Softphone is only available on Microsoft Windows

operating systems;

In TWP Videoshare, sharing one's desktop is only available on Microsoft Windows

operating systems. Linux and Mac users may only view (and control) the desktop of other

users, they may not share theirs.

2. “Pure web” mode, TWP is started inside a web browser, and is not integrated with the desktop

Requirements: any Microsoft Windows, Linux or Mac OS X supporting Adobe Flash Player

version 9 or above (see Adobe pre-requisites for more detailed information)

In “Pure web” mode, some restrictions apply:

Aastra 5000 / NeXspan: TWP Softphone not available

TWP Videoshare: no possibility to share your desktop but viewing other users' desktop is

still possible

Less integrated in the desktop:

o Fully included in the web browser window

o No TWP Alerter pop-up, no auto-hide, …

3. Thin client mode via Citrix XenApp or Microsoft Terminal Services, TWP is accessed inside a

web portal or client agent, and integrates smoothly within the desktop

Requirements: please refer to Citrix website for latest requirements

In “thin client” mode, some restrictions apply:

Aastra 5000 / NeXspan: TWP Softphone not available

The TAPI Service Provider is not available.

TWP Videoshare:

o No possibility to share your desktop but viewing other users' desktop is still

possible

o No possibility to send your video (no access to local webcam)

Citrix XenApp session mode only is supported (no support for application virtualization or

application streaming)

2.3.1.2.2 Web Browsers

The TWP 3.2 is compatible with all Web browsers supporting the Adobe Flash Player: Internet

Explorer, Firefox, Safari, etc.

33

Adobe Flash Player has to be minimum version 9 (or above).

2.3.1.2.3 Time zones

The TWP clients and server must be in the same time zone.

2.3.1.3 Compatible set types

TWP can be used for monitoring and controlling a high number of set types. This section lists the

compatible terminals for each call manager.

2.3.1.3.1 Aastra 5000 / NeXspan

Aastra 5000 / NeXspan:

User sets are managed by TWP thanks to VTI/XML or CSTA supervision.

The table below lists compatible terminal types:

CSTA

supervision

VTI/XML

supervision MakeCall

Ringback

tones after

MakeCall

AnswerCall

TWP

Browser call

by name

TWP

Browser

name

display

Analog

DECT

DECT

over IP

Digital

i7xx

Standard

SIP

Aastra

6700i

Series

telephones

up to

Aastra

5000

R5.1B

from

Aastra

5000

R5.1C

up to

Aastra 5000

R5.1

from

Aastra 5000

R5.2

Aastra

5300ip

Series

telephones

AMC

BluStar

Client

34

CSTA

supervision

VTI/XML

supervision MakeCall

Ringback

tones after

MakeCall

AnswerCall

TWP

Browser call

by name

TWP

Browser

name

display

TWP

Softphone

i2052 VoIP

Terminal +

i2052 CTI (depends on terminal type)

The meaning of the column titles is the following:

"CSTA supervision" means that the terminal type can be used for a TWP user but needs a

CSTA license for supervision (not provided with TWP);

“VTI/XML supervision” means that the terminal type can be used for a TWP user without need

for supervision license;

"MakeCall" means that TWP can make an outbound call without any manual intervention of the

user on the terminal. Terminal types having a in this column can also be used for making

outbound calls from TWP, but they will start ringing first, then the user will have to manually lift

up the receiver before the call is actually made;

"Ringback tones after MakeCall" means that the terminal generates ringback, busy and error

tones when TWP is used for making an outbound call. Terminal types having a in this column

do not generate such tones in this case, which can be a bit disconcerting for the user;

"AnswerCall" means that TWP can control the terminal for answering an incoming call.

Terminal types having a in this column can answer calls only by manually lifting up the

receiver of the terminal. As a consequence, the "answer call" buttons of TWP have no effect on

these terminal types.

“TWP Browser call by name” means that the terminal itself can be used for searching for

contacts in the directories to which TWP connects.

“TWP Browser name display” means that the terminal itself can show, for a given call, the

name of the remote party, extracted from the directories to which TWP connects.

The following constraints also need to be taken into account:

Supervision on attendant console is not possible (ACP Web Attendant is supported though).

A digital or DECT set in associated or tandem mode cannot be supervised.

A set in a general call group cannot be supervised.

Associated sets: VTI/XML IP sets cannot be part of an association, thus TWP Softphone or

i2052 VoIP cannot be associated with another set. Associated sets can be supervised and

controlled via VTI/XML protocol, not by CSTA.

Comments:

CCO-related functions are not available on all sets.

TWP can manage only one line (i.e. only one directory number) per user. But TWP can

manage multiple CCO (i.e. multiple lines on the same directory number).

35

iPBX limitations to be taken into account:

VTI/XML:

Maximum 8 VTI/XML servers per site

CSTA:

64 CSTA servers maximum per multi-site (R5.x)

16 CSTA servers maximum per site (R5.x), each server can monitor 255 objects (AX

Series) and 2048 (Aastra 5000 server)

8 CSTA servers maximum per site/multi-site (R4.2 or hybrid 4.2 & 5.x), each server can

monitor 255 objects.

2.3.1.3.2 Aastra 400 / Aastra IntelliGate®

Aastra 400 / Aastra IntelliGate®:

User terminals are managed by TWP thanks to CTI supervision.

Supported terminals for control & monitoring:

o Aastra 5300 Series telephones/digital telephones

o Aastra 5300ip Series telephones

o Aastra 2380ip

o Office 25,35,45

o Office 20,30,40 (IntelliGate only)

o Dialog 4220, 4222, 4223 (Aastra 400 only)

o Office DECT 135, 135pro

o Aastra 600d Series with SB4+/SB8 base stations

Supported terminals with limited call control (make call, answer call and end call):

o Aastra 6700i

Supported terminals for monitoring only (not supported for control):

o Analog terminal

o Standard SIP phones

TWP can manage only one line (i.e. only one directory number) per user.

Aastra IntelliGate® limits are 400 TWP clients for a single node and 600 TWP clients for an AIN

(Aastra IntelliGate® Net)

2.3.1.3.3 Aastra 800 / OpenCom 100

Aastra 800 / OpenCom 100:

User terminals are managed by TWP thanks to CSTA supervision (PBX CSTA license needed).

Supported terminals for control & monitoring:

Supported Disable en-bloc

dialing

Complex

calls

36

Supported Disable en-bloc

dialing

Complex

calls

Aastra 673xi Series telephones/digital telephones -

Aastra 675xi Series telephones/digital telephones -

Aastra 677x(ip) Series telephones/digital telephones

Aastra 277xi Series softphones

OpenPhone 6x/7x Series telephones/digital telephones

Aastra 142d -

Aastra OpenPone 26/27 -

Aastra 600d Series -

Analog terminal (manually hook on/off by user) -

SIP terminal -

Virtual terminal for CSTA -

The meaning of the column titles is the following:

“Supported”: this type of terminal can be used with TWP

“Disable en-bloc dialing”: for terminals having a in this column, en-bloc dialing must be

disabled in the phone settings for automatic offhook.

“Complex calls”: terminals having a in this column do not support over CSTA/TWP features

like answer a second call, consultation call, alternate call and PBX conference.

One Number: TWP can manage only one terminal per dialling number (Aastra 800 supports one

dialling number on up to ten terminals).

2.3.1.3.4 Aastra MD Evolution

Aastra MD Evolution:

User terminals are managed by TWP thanks to CSTA supervision.

Supported terminals for control & monitoring:

o Dialog 4200

o Dialog 4400ip

o Aastra 7400ip

o Aastra 6700i

o DT390, DT690, DT4xx (TDM-DECT)

o Aastra 600d, A142d (IP-DECT and TDM-DECT)

o Analog

2.3.1.4 IPBX/Communication system prerequisites

2.3.1.4.1 Aastra 5000 / NeXspan

Aastra 5000 / NeXspan:

37

TWP is compatible with the following models of iPBX:

Communication Server

M6550

NeXspan

Aastra 5000

AXS

AXL

AXD

IPBX releases that are supported are:

NeXspan R4.2

Aastra 5000 R5.1

Aastra 5000 R5.2

Aastra 5000 R5.3

Please refer to the distributors' extranet and technical bulletins for the minimum software stages of

these software releases.

If the Aastra 5000 / NeXspan network is using several CSTA servers, the total number of CSTA

subscribers of the multi-site configuration has to be unlocked on each site where a CSTA server is

activated.

It is also necessary to provision as many VoIP channels on the EIP card (UCV or USV daughter

card) or on the VoIP daughter board (PT2 or PVI daughter card) as the number of TWP Audio +

Video Media Server channels (except for the IP flow replication mode of the TWP Recorder).

Please note that the use of VTI/XML by TWP is not subject to license in the Aastra 5000 or

NeXspan iPBX.

2.3.1.4.2 Aastra 400 / Aastra IntelliGate®

Aastra 400 / Aastra IntelliGate®:

Aastra IntelliGate® supported software releases are:

I7.9 SP3

Aastra 400 supported software releases are:

R1.0, R1.1

TWP and Open Interfaces Platform can run in parallel (multiple 3rd party CTI), but 1st party CTI

has to be disabled.

For each non-IP/TDM device or terminal that will need to communicate with the TWP Media

Server channel, DSP’s must be provisioned (embedded in IntelliGate® or need to add AIP cards),

but also “VoIP channels for standard media switch” licenses must be provisioned.

Communication system limitations to be taken into account:

Maximum 1 CTI interface connection per application for a single node

2.3.1.4.3 Aastra 800 / OpenCom 100

38

Aastra 800 / OpenCom 100:

TWP is compatible with the following PBX models: Aastra 800, OpenCom 100 family, since

release 10.

2.3.1.4.4 Aastra MD Evolution

Aastra MD Evolution:

TWP R3.2 is supported on Aastra MD Evolution from version R11.0.

Running CTI Link is a pre-requisite for TWP to work with Aastra MD Evolution, as TWP uses the

CSTA protocol to talk to Aastra MD Evolution IP-PBX. CTI Link server can be installed on the

TWP server or on a separate server/PC.

TWP is also supported in a networking configuration. Such configuration implies running as many

instances of CTI Link as the number of Aastra MD Evolution sites.

INT FP configurations are also supported from Aastra MD Evolution R11.0 Service Pack.

2.3.1.5 IT environment prerequisites

The following authentication modes are possible for authenticating the TWP client users:

workgroup, Active Directory, IIS: NTLM and basic authentication for Single Sign-on.

Contacts can be synchronized with the following sources:

Microsoft Exchange Server 2003, 2007 and 2010 (private and public contacts)

Notes:

o Private contacts support requires the private contacts to be replicated on the

Microsoft Exchange Server.

o Form-based authentication is not supported.

o For Exchange 2007, public contacts support requires Service Pack 1.

Microsoft Exchange Online (private contacts only)

IBM Lotus Domino 7, 8 and 8.5 (private and public contacts)

Notes:

o Private contacts support requires the private contacts to be replicated on the Lotus

Domino server (roaming).

o For Domino 8, private contacts support requires 8.01.

OBDC, SQL and LDAP databases

Calendar presence information can be retrieved from the following supported servers:

Microsoft Exchange Server 2003, 2007 and 2010

Note: Form-based authentication is not supported.

Microsoft Exchange Online

IBM Lotus Domino 7, 8 and 8.5

SMS can be sent by TWP via an external provider:

TWP connects to an SMPP-compliant service provider

o A subscription to this provider is needed

39

o No GSM modem is needed in TWP

TCP/IP-based protocol (TCP port 2775)

o SMPP v3.4 is supported

o Ciphering (SSL) is not supported

2.3.1.6 Bandwidth

The required bandwidth per user between the TWP client and the TWP server is 5 kbits/s.

This bandwidth is measured under the following hypotheses:

Each user uses the TWP Caller and TWP Alerter features;

Each user manages 4 calls/hour, among which 2 outgoing calls with directory search and 2

incoming calls;

Each directory search provides an average of 16 results;

Each user has an average of 20 contacts with supervision;

The network link with the TWP server is shared between at least 10 users (in order to

"flatten" the traffic peaks that are mainly due to the directory searches);

A copy of the Caller executable has been made on a local server (which is a general

recommendation in case of low bandwidth).

See section 2.3.2 for additional bandwidth considerations specific to some features.

2.3.2 Particular constraints per feature

2.3.2.1 TWP Alerter

In TWP “pure web” mode, this feature is available with no pop-up card on top. The opening of an

application from the TWP Alerter can only be triggered by a URL link.

2.3.2.2 TWP Audioshare

The shared call queues managed by TWP Audioshare must correspond to the following types of

subscribers:

Aastra 5000 / NeXspan: In NeXspan, these can be either a digital subscriber with the right

to be disconnected, or a connected IP set. In Aastra 5000, same as NeXspan but a

VTI/XML IP set can also be used. Depending on the case, you have to make provisions for

a digital line interface or an IP license (an Aastra 5000 “proprietary” or generic” IP license,

unlocking an Aastra 5000 VTI/XML-IP subscriber; or a NeXspan IP license, unlocking a

NeXspan Etherset subscriber). They can only be monitored in VTI/XML. Empty hunt

groups are not supported.

Aastra 400 / Aastra IntelliGate®: Each shared call queue corresponds to one CDE

number in the ACD queue of the Aastra 400 / Aastra IntelliGate®.

Call queues are not considered anymore as subscribers managed by TWP and hence don't have

to be counted anymore in the total number of TWP Caller licenses needed. For the TWP

Audioshare audio conference capability, make sure to provision enough bandwidth towards the

40

TWP Media Server. The mixing of the audio streams takes place in the Media Server, it needs to

receive and send <number of participants> * call bandwidth.

The bandwidth consumed for each call depends on the chosen encoding law. For more

information on codec-based bandwidths, please refer to the Product Guide.

RTP stream QoS marking is supported by the TWP Media Server.

Please see also the constraints of the media server in section 2.3.2.5 for managing audio

conferences.

2.3.2.3 TWP Browser

Aastra 5000 / NeXspan:

With a NeXspan iPBX (up to R4.2), the TWP Browser feature requires a NeXspan Communication

Server (NCS) for accessing the TWP directories. If no NCS is present in the multi-site, then one

has to be added, even if it does not manage any subscriber. With Aastra 5000 (from R5.1), this

constraint is not valid anymore: any Aastra 5000 gateway or call manager can directly access the

TWP directories.

See section 2.3.1.3.1 for the list of terminals that benefit from the TWP Browser feature.

Aastra 400 / Aastra IntelliGate®:

Only one Name Server is configurable. TWP can be the Name Server for the Aastra 400 /

Aastra IntelliGate® communication systems if no OIP is running at the same time.

2.3.2.4 TWP Caller

A TWP Intercom group should not scale above 40 users.

Constraints specific to Aastra 5000 / NeXspan:

The Intercom service (virtual keys) is only proposed to sets supervised in VTI/XML mode.

By default, this feature takes into account the supervision keys that are defined on the user

set.

However, it is possible to use an intermediate "virtual" set for supervising other subscribers

via the Intercom service, for instance for increasing the number of supervised subscribers.

This virtual set may be either a digital subscriber with the right to be disconnected (but the

digital card must be present) or a connected IP set. It is rather recommended to use a

VTI/XML IP device on Aastra 5000 or an Etherset subscriber (VTI/XML IP type) on

NeXspan, which does not need any physical device connected. Depending on the case,

you have to make provisions for a digital line interface or an IP license (on Aastra 5000

“proprietary” – cheaper – or generic” IP license). Each virtual set allows the supervision of

64 subscribers.

The "my current device" function with change of current set is only proposed for digital or

IP sets supervised in VTI/XML mode (need for hands free function).

Simple rules can define different forwarding types for internal calls and external calls.

TWP Caller contact list makes no difference in delivered call supervision between internal

and external calls

Constraints specific to the Aastra 400 / Aastra IntelliGate® communication system:

Simple rules can not define different forwarding types for internal calls and external calls.

41

The TWP Caller call log is not synchronized with the terminal call list

Take function, callback are not possible to control from the TWP Caller interface

TWP Caller contact list makes no difference in delivered call supervision between internal

and external calls

OneNumber active terminal can be selected from TWP Caller preferences window

Line keys or “key telephone” are not controlled by TWP.

Constraints specific to the OpenCom 100 / Aastra 800 communication system:

The TWP Caller call log is not synchronized with the terminal call list

Line keys are not controlled by TWP

2.3.2.5 TWP Media Server

The following constraints are common to all applications that require the TWP Media Server:

TWP Audioshare, TWP Mail / TWP @Messaging, TWP Recorder, TWP Rules and TWP

Videoshare.

Supported codecs: G.711A-law & µ-law, G.729 - 10/20/30/40 ms frames are supported

(regardless the type of channels: proprietary or including HMP).

Voice and/or signalling encryption are not supported on TWP Media Server.

Maximum number of channels per server:

“Proprietary” TWP Media Server Audio / Video channel licenses (without HMP) : maximum

24 total channels (audio + video) supported per server

TWP Media Server Audio / Video channel licenses “including HMP”: maximum 100 total

channels (audio + video) supported per TWP server

There is no difference here between Aastra 5000/NeXspan and Aastra 400 / Aastra IntelliGate®

platforms.

2.3.2.6 TWP Mail / TWP @Messaging

Voice messages can be listened to from any terminal, phone number or on the client PC. To do

so, the client PC must be equipped with a full-duplex sound card to which you can add a USB or

regular audio accessory (headset or speakers).

TWP Mail & TWP @Messaging support the following e-mail servers:

Microsoft Exchange Server 2003 and 2007

IBM Lotus Domino 7 and 8

Any SMTP compliant e-mail server.

Notes:

For e-mail servers which are not “Microsoft Exchange-IMAP4” or “IBM Domino-IMAP4”

compliant, TWP Mail / TWP @Messaging is not able to truly unify the voice messages left

in the voice mailbox:

o Voice messages read/listened to from the e-mail system will not be considered as

listened to in the voice mailbox (and the phone set message waiting indicator will

not be turned off)

42

o Voice messages listened to from the voice mailbox will not be considered as

red/listened to in the e-mail system.

o Voice messages deleted from the e-mail system will not be deleted in the voice

mailbox.

o Voice messages deleted from the voice mailbox will not be deleted in the e-mail

system.

For e-mail and groupware servers other than Microsoft Exchange Server or IBM Lotus

Domino, the intelligent inbound calls routing module from TWP @Messaging won’t be able

to connect to their calendar feature, and hence won’t be able to take routing decisions

based on the corresponding calendar presence status. This feature is available with TWP

@Messaging, when connected with Microsoft Exchange Server 2003 or 2007 server, or an

IBM Lotus Domino 7 or 8 server.

Please see also the constraints of the Media Server in section 2.3.2.5.

2.3.2.7 TWP Opencall

TWP Opencall is an enhanced dialer that offers an access to the iPBX/communication system

internal and TWP users directories.

It is available as a client application similar to the TWP Caller in “desktop integration” mode.

However, it is available only on Microsoft Windows operating systems (the same ones as for TWP

Caller in “desktop integration” mode). TWP Opencall is not available in “pure web” mode, only a

simple “make call” web service is available then.

2.3.2.8 TWP Recorder

TWP Recorder offers several techniques of recording conversations:

IP flow replication (also known as ”full IP” recording in TWP);

Intrusion (Aastra 5000 / NeXspan only);

Three-party conference (also known as ”DAT” recording in TWP).

In all techniques, each recording and playback uses a TWP Media Server Audio Channel license.

The recording Media Server resource can record either G711 or G729 coding law streams. G723

is not supported anymore.

In the last two techniques, each recording uses a conference circuit on the iPBX/communication

system.

To be able to listen to recorded conversations, the client PC must be equipped with a full-duplex

sound card to which you can add a USB or regular audio accessory (headset or speakers).

Note: Access to recorded conversations requires a TWP Recorder user license.

Aastra 5000 / NeXspan:

For the Aastra 5000 and NeXspan iPBX, the number of conference circuits in the iPBX system will

then determine the maximum simultaneous recording capacity. Please consult the Aastra 5000

ordering guide for knowing the number of conference circuits of your iPBX.

Aastra 400 / Aastra IntelliGate®:

For Aastra 400 / Aastra IntelliGate® communication system, the system type will determine the

maximum simultaneous recording capacity (Three-party conference):

43

Aastra IntelliGate A150: 4 (three-party conference circuit); 4 (six-party conference circuit)

Aastra IntelliGate 2025/2045/A300: 4 (three-party conference circuit); 4 (six-party

conference circuit)

Aastra IntelliGate 2065: 14 (three-party conference circuit); 14 (six-party conference circuit)

Aastra 415/430 : 4 (three-party conference circuit); 4 (six-party conference circuit)

Aastra 470 : 10 (three-party conference circuit); 10 (six-party conference circuit)

It is possible to mix several techniques in a single system, each TWP user being configured for

being recorded in one (and only one) technique.

Please see also the constraints of the Media Server in section 2.3.2.5.

Aastra 800 / OpenCom 100:

For Aastra 800 / OpenCom 100 communication system, the system type will determine the

maximum simultaneous recording capacity:

Aastra 800: 20 conference circuits

OpenCom 100 family: 5 conference circuits

2.3.2.8.1 Recording through IP flow replication

This recording technique allows recording at the user’s initiative and also automatic recordings.

The recorded telephone sets must be IP sets/terminal and they must have a static/fixed IP

address.

Aastra 5000 / NeXspan:

Unless they are a TWP Softphone, in which case their IP address may be dynamic.

Aastra 400 / Aastra IntelliGate®:

In a One Number constellation with several IP terminals, only one IP address can be specified in

TWP, thus only one IP terminal can be recorded per named TWP user.

Aastra 800 / OpenCom 100:

The IP flow replication type of recording can be used for all IP terminals, and must be used for

Aastra SIP and SIP terminals

Internal conversations from one IP set to another IP set cannot be recorded.

The network infrastructure must:

Provide 2 network cards on the TWP server (one for signaling, the other for VoIP flows)

Allow the replication of the IP flow from the iPBX VoIP network interface(s) to the TWP

server (manageable switch, for example).

2.3.2.8.2 Recording through intrusion

This recording technique is available only for Aastra 5000 / NeXspan iPBX.

This recording technique allows recording at the user’s initiative and also automatic recordings.

All types of telephone sets may be used except SIP (generic) and Wi-Fi SIP. The telephone sets

must be set to single CCO.

All types of conversations can be recorded.

44

You have to make provisions for:

As many three-way conference circuits as the conversation recordings you wish to perform

simultaneously

As many VoIP channels on the EIP card (UCV or USV daughter card) or on the VoIP

daughter board (PT2 or PVI daughter card) as conversation recordings, recording playback

you want to perform simultaneously

As many IP licenses (proprietary IP for R5.1 and above) on the iPBX as the VoIP channels

used by TWP Recorder

During recording, the sets cannot perform any inquiry call-related operation (consultation call after

putting a call on hold, call transfer, recover, conference, etc.).

If voice over IP encryption is implemented on the telephony server, conversations can be recorded

if no encryption is set between iPBX and TWP Media server.

The intrusion recording technique is available only with proprietary Media Server channels. It is

not compatible with Media Server channels including HMP.

Note: If the recorded user hangs up first, his phone will ring back after he hangs up.

2.3.2.8.3 Recording through three-party conference

This recording technique is not available for Aastra SIP and SIP terminals on Aastra 800 /

OpenCom 100 PBX, then the SIP terminal should be the conference master.

This recording technique only allows recording at the user’s initiative (automatic recording is not

available):

The following constraints apply:

All types of telephone sets may be used.

All conversation types can be recorded.

During recording, the sets cannot perform any inquiry call-related operation (consultation

call after putting a call on hold, call transfer, recover, conference, etc.).

Aastra 400 / Aastra IntelliGate®: enquiry calls while recording may still be possible if 6

party conference circuits are still available.

Aastra 5000 / NeXspan: if voice over IP encryption is implemented on the telephony

server, conversations can be recorded if no encryption is set between iPBX and TWP

Media server.

For Aastra 5000 / NeXspan, you have to make provisions for:

As many three-way conference circuits as the conversation recordings you wish to perform

simultaneously

As many VoIP channels on the EIP card (UCV or USV daughter card) or on the VoIP

daughter board (PT2 or PVI daughter card) as the conversation recordings, recording

playback, voice announcement recordings and broadcast you want to perform

simultaneously

As many IP licenses (proprietary IP for R5.1 and above) on the iPBX as the VoIP channels

used by TWP Recorder

45

For Aastra 400 / Aastra IntelliGate®, you need for each simultaneous recording channel:

1 three-way conference call circuit

VoIP Channels :

o 1 VOIP channel if the caller and the called parties are TDM

o 2 VOIP channels if one of the caller or called parties is IP and the other TDM

o 3 VOIP channels if all parties are IP

1 SIP terminal resource (Aastra SIP or Standard SIP) – also needed for playback

For Aastra 800 / OpenCom 100, you have to make provisions for:

As many three-way conference call circuits as the conversation recordings you wish to

perform simultaneously

As many DSPs and “VoIP Channels for standard Media gateway” on the communication

system as the conversation recordings you wish to perform simultaneously.

As many SIP subscribers licenses as the conversation recordings, recording playback you

want to perform simultaneously

2.3.2.8.4 Summary table

The characteristics and limitations of these different recording techniques are summarized in the

table below.

IP flow replication Intrusion 3-party conference

iPBX compatibilities

Compatible with

Aastra 5000 / NeXspan

Compatible with

Aastra 400 / IntelliGate®

Compatible with Aastra

MD Evolution

Compatible with

Aastra 800 / OpenCom

100

Offered features

Manual recording Yes

Automatic recording Yes No

Discretion ++++ ++ +

Constraints

Recordable phone types IP or TWP Softphone only Any mono-CCO except

SIP, Wi-FI SIP Any

Recorded conversations All conversations, except All conversations

46

IP flow replication Intrusion 3-party conference

IP-to-IP

Ciphered conversations Cannot be recorded Can be recorded, but no ciphering between iPBX and

TWP Media Server

Limitations on call

management None

On all platforms: prevents from inquiry call, transfer,

conference, etc. during recording

Additional behaviors None

On Aastra 5000 and

NeXspan, callback if hung

up

None

iPBX conference

circuits Not used Used

Capacity (channels) Up to 128 (incl. HMP), Up

to 24 (proprietary)

Limited by iPBX

conference circuits

Up to 24 (proprietary)

Limited by iPBX

conference circuits

Up to 100 (incl. HMP) or

up to 24 (proprietary)

Additional operating

constraints

IP stream replication;

2 network cards;

static phone IP addr.

Aastra 5000 and NeXspan: IP lines declared in iPBX

Aastra 400 and Aastra IntelliGate®: SIP subscriber

licenses, DSP’s & VoIP licenses declared in iPBX

Coding law G.711 + G.729

2.3.2.9 TWP Rules

Advanced rules only work if a call is presented to user’s set, so:

No effect if phone is immediately forwarded (call forward unconditional)

One ring tone can be heard even if an immediate forward is executed

Aastra 5000 / NeXspan:

For Aastra 5000 and NeXspan, the following constraints apply:

Programming advanced rules on busy is only available for multi-CCO sets and is only

effective for calls presented on a CCO (does not allow the forwarding of a waiting call).

You have to make provisions for:

As many VoIP channels on the EIP card (UCV or USV daughter card) or on the VoIP

daughter board (PT2 or PVI daughter card) as greeting message recordings and broadcasts

you want to perform simultaneously

As many IP licenses (Proprietary IP for R5.1 and above – Generic IP license are valid too,

but they are more expensive) on the iPBX as the VoIP channels used by TWP Rules

Aastra 400 / Aastra IntelliGate®:

For Aastra 400 / Aastra IntelliGate®, the following constraints apply:

Programming advanced rules on busy is not available on Aastra 400 / Aastra IntelliGate®

systems

47

You have to make provisions for:

As many DSP’s and “VoIP Channels for standard Media switch” licenses on the

communication system as greeting message recordings and broadcasts you want to perform

simultaneously to / from a non-IP device.

As many SIP subscribers (or Aastra-SIP subscribers from I7.9 – cheaper) as greeting

message recordings and broadcasts you want to perform simultaneously

Aastra 800 / OpenCom 100:

For Aastra 800 / OpenCom 100 family, the following constraints apply:

Programming advanced rules on busy is not available on Aastra 800 / OpenCom 100 family

systems

You have to make provisions for:

As many DSP’s and “VoIP Channels for standard Media gateway” on the communication

system as greeting message recordings and broadcasts you want to perform simultaneously

to / from a non-IP device.

As many SIP subscribers (or Aastra-SIP subscribers – cheaper) as greeting message

recordings and broadcasts you want to perform simultaneously

Please see also the constraints of the Media Server in section 2.3.2.5.

2.3.2.10 TWP Softphone

Aastra 5000 / NeXspan:

As written above the TWP Softphone application is only available on Microsoft Windows operating

systems (see section 2.3.1.2.1 for more details)

The client PC must be equipped with a full-duplex sound card to which you can add a USB or

regular audio accessory (headset or handset or a microphone only). Of course, the sound quality

depends on the quality of these devices.

Any USB headset is supported for the standard speech and listen features. Some particular

devices have pick up / hang up control buttons/features: these features have been validated only

with the following devices:

Jabra wireless headsets GN9330 and GN9350 (DECT)

Jabra wireless headsets PRO 9460 and PRO 9470 (DECT)

Plantronics CS50-USB and CS60-USB headsets

Plantronics Voyager 510-USB Bluetooth headset

If other accessories are used, Aastra cannot guarantee the pick up/hang up buttons/features are

correctly supported.

Users must be declared as VTI/XML-IP type IP sets (named Etherset in the NeXspan) and the

corresponding number of IP licenses must be provided on the iPBX.

TWP Softphone manages only encoding laws G711 A and µ-law and G729, without encryption.

The bandwidth consumed for each call depends on the chosen encoding law. For more

information on codec-based bandwidths, please refer to the Product Guide.

RTP stream QoS marking is supported by the TWP Softphone.

48

If customer’s network is made of separate layer 2 switches for data and voice network without

inter network routing, the TWP Softphone does not work (as it needs to connect both to the TWP

server and to the Aastra 5000).

Running a TWP Softphone from a remote location requires a Virtual Private Network (VPN) to be

set up between the client computer and the server.

2.3.2.11 TWP Stats

The disk space occupied by one call stored in the statistics database is about 320 bytes.

The statistics data is stored by default for 520 days (configurable).

2.3.2.12 TWP Toolkit and TAPI Service Provider

The specifications for a client application integrating the TWP Toolkit are:

Web Services require HTTP or SOAP client on any type of operating system

Authentication is done thanks to the Microsoft Windows single sign-on or workgroup

authentication (see the TWP Toolkit Developer’s Manual 3.1 for more detailed explanations).

The TAPI Service Provider may be used only in a 32-bits Windows operating system.

2.3.2.13 TWP Videoshare

As written above, sharing one's desktop is only available on Microsoft Windows operating systems

(see section 2.3.1.2.1 for more details). Linux and Macintosh users may only view (and control)

the desktop of other users, they may not share theirs.

While using video, this application requires a webcam which is supported by the Adobe Flash

Player version 9 or above (most of the standard webcams are supported – see Adobe

specifications for more detailed pre-requisites).

The images resolution is the following:

320x240 pixels (QVGA) for the large image (the selected participant);

160x120 pixels (QQVGA) for the small images (all other participants).

The audio, video and application sharing streams are multiplexed by the TWP server to allow

multi-point conferencing. The table below summarizes the bandwidth usage:

Type of stream Bandwidth needed “Worst case”

bandwidth needed

Protocol QoS

marking

Audio Depends on codec:

G711: about 87 Kbits/s per participant

G729: about 31 Kbits/s per participant

Per system: with 6

conferences of 10 users +

1 conference of 4 users in

G711: 5,5 Mbits/s

UDP Yes,

managed

by TWP

Media

server

49

Type of stream Bandwidth needed “Worst case”

bandwidth needed

Protocol QoS

marking

Video Per image per participant, for a 320x240

pixels image with 20 fps (image quality is

a TWP setting per system):

15 Kbytes/s for low image quality

30-40 Kbytes/s for "correct" image

quality

60 Kbytes/s or more for superior

image quality

Per system: with 6

conferences of 10 users +

1 conference of 4 users,

all with published

webcam and superior

image quality: 295 Mbits/s

TCP No

Application

sharing

Per user, approximately between 150 and

300 Kbytes/s

Variable because depends on the

activity of the computer

Possible to configure 256 colors mode

to save bandwidth

Per system: with 64

participants (any number

of conferences) and 300

Kbytes/s = 154 Mbits/s

TCP No

Note: It is not possible to join an external party (non-TWP Videoshare user) directly from

Videoshare, unless establishing a PBX conference for audio only.

Please see also the constraints of the TWP Media Server in section 2.3.2.5.

2.3.3 Capacities

2.3.3.1 General capacities

The following table lists the capacities of TWP that are independent from the iPBX/communication

system range:

Capacity

Per IP network

Max number of TWP servers unlimited

Per TWP Server

Max number of companies 50

Max number of domains 50

Max number of users per domain 500

Max total number of participants to

simultaneous audio or video conferences

100 (TWP Media Server Audio / Video

channel licenses “including HMP”)

24 (TWP Media Server “proprietary” Audio

/ Video channel licenses)

Max number of users of TWP CTI users 8,000

Max traffic of TWP Browser 32,000 calls per hour

Max traffic of TWP Opencall users 60,000 TWP Opencall clicks per hour

50

Capacity

Per TWP Audioshare or TWP Videoshare conference

Max number of participants 10

2.3.3.2 Capacities for Aastra 5000 and NeXspan

Aastra 5000 / NeXspan:

The following table lists the specific capacities of TWP when connected to an Aastra 5000 or

NeXspan iPBX:

Capacities Monitored subscribers Traffic

Per multi-site

VTI/XML users 512 users per VTI/XML link on AX Series

15,000 users per VTI/XML link on Aastra 5000

server

-

CSTA users If iPBX version ≤ R4.2: 2,040 (=255*8)

If iPBX version ≥ R5.1: 15,000

-

Per TWP Server

Monitored TWP CTI

users

8,000 20,000 calls per hour

TWP Opencall users Unlimited (iPBX limitations only) 60,000 clicks per hour

TWP Browser users Not supervised: 10,000 if the server is dedicated to

this function. Up to 8,000 users if the NCS/ACS

manages up to 4,000 IP subscribers on the same

machine

Up to 600,000 directory records

(needs SQL Server Standard

Edition)

VTI/XML users 8,000 -

Number of VTI/XML

links

Unlimited (iPBX limitations only) unlimited per domain (Attention iPBX 8 VTI/XML servers per site!) -

Monitored CSTA

users per CSTA link

If IPBX version ≤ R4.2: 255

If IPBX version ≥ R5.1:

o 255 (AX series)

o 2048 (Aastra 5000 server)

-

Number of CSTA

links

1 per TWP domain4 -

Per VTI/XML link

NeXspan native IP 250 -

4 If the Aastra 5000 / NeXspan network is using several CSTA servers, you have to unlock the total number of CSTA

subscribers of the multi-site configuration on each site where a CSTA server is activated

51

Capacities Monitored subscribers Traffic

port

Non-dedicated IP

card

250 -

Dedicated IP card 500 -

Communication

Server

4000 -

Per site

M6540 100 600 calls per hour

NeXspan 500 (per

PVI card)

250 1,500 calls per hour

M6550 – USH cluster 100 600 calls per hour

NeXspan S,L,D,

Aastra XS, XL, XD

250 4,500 calls per hour

Aastra XS,X2S 500 6,000 calls per hour

Aastra , XL, XD 692 1,000 6,000 calls per hour

Communication

Server R4.x

4,000 24,000 calls per hour

Aastra 5000 Server

R5.1

15,000 45,000 calls per hour

2.3.3.3 Capacities for Aastra 400 / Aastra IntelliGate®

Aastra 400 / Aastra IntelliGate®:

The following table lists the specific capacities of TWP when connected to an Aastra 400 /

Aastra IntelliGate® communication system:

Capacities Monitored subscribers Traffic

Per AIN

Max number of TWP

CTI users

600 -

Per TWP Server

Monitored TWP CTI

users

8,000 20,000 calls per hour

TWP Opencall users Unlimited (PBX limitations only) 60,000 clicks per hour

TWP Browser users Not supervised: 10,000 if the server is dedicated to

this function

Up to 600,000 directory records

(needs SQL Server Standard

Edition)

CTI monitored users 8,000 20,000 calls per hour

Number of CTI links 1 per TWP domain -

52

Capacities Monitored subscribers Traffic

TWP Opencall users Unlimited (PBX limitations only) 60,000 clicks per hour

Per IntelliGate system

Aastra 470 maximum

subscribers

600 (without AIN: 400) -

Aastra 430 maximum

subscribers

100 (without AIN: 50) -

Aastra 415 maximum

subscribers

12 -

Aastra IntelliGate®

A150 maximum

subscribers

12 -

Aastra IntelliGate®

A300 maximum

subscribers

100 (without AIN: 50) -

Aastra IntelliGate®

2025 maximum

subscribers

20 -

Aastra IntelliGate®

2045 maximum

subscribers

60 -

Aastra IntelliGate®

2065 maximum

subscribers

400 -

2.3.3.4 Capacities for Aastra MD Evolution

Aastra MD Evolution:

A maximum of 100 TWP users (Open Call or Caller) are supported on a Aastra MD Evolution

equipment. In a networking configuration, please refer to General capacities chapter for capacities

on TWP Server side.

2.4 Software subscription

The software subscription offer is an optional service which must cover an entire TWP system.

This service gives the customer access, if he or she desires, to all upgrades (operational

upgrades) for a specific period. This service can be ordered at any time as long as the customer

TWP system version is the latest one available from the current Aastra price-list.

The end-customer can then benefit from the latest features for a very attractive cost and extend

the lifecycle of the initial investment.

This service is associated with a software subscription license, the principles of which are:

53

The software subscription license gives access to software function upgrades over a specific

period: mandatory initial period of 1 or 3 years, followed by possible 1 year extensions.

The software subscription license does not include the installation or implementation of the

upgrades.

The software subscription license is attached to a single piece of hardware (dongle).

The software subscription license applies to all the software functions acquired for this piece

of hardware (dongle).

The software subscription license is valid for a limited period. This period may be extended

before expiration.

In a given product release and for a given piece of hardware covered by the software

subscription license, if the customer buys new software licenses (capacity increase, new

modules), they will be automatically covered by the software subscription license and sold at

a price including software subscription until next maturity date.

When Aastra makes a new version available, the customers under software subscription may

ask for the new software as well as new licenses without license fees.

The new licenses correspond to the modules and capacities acquired in the previous version.

The new modules are not concerned.

Aastra undertakes to regularly provide new software releases.

The TWP software releases impose engineering and compatibility rules on the environment:

hardware pre-requisites, OS version, iPBX version, and database interface prerequisites. A TWP

upgrade may require upgrading certain components of the environments, which are not included

in the software subscription license price.

The price for the service is defined as a percentage of the catalogue price of the TWP software

licenses. For an extension of capacity, the price is calculated on the added licenses.

TWP-related orders must be accompanied by the server dongle number in case of extension of

maintenance period or while ordering the upgrade kit.

Please refer to Aastra software subscription case studies for more information.

Note: For Aastra 400, the software subscription model is different for the communication server,

OIP and TWP, even with the embedded CPU2 Application Card

54

© 2012 Aastra Technologies Limited. All rights reserved.

This document contains proprietary information, which is protected by copyright.

No part of this document may be reproduced or transmitted in any form or by any means,

electronic or mechanical, including photocopying, recording, or by any information storage and

retrieval system, or translated into another language, without the prior written consent of Aastra

Technologies Limited, Concord, Ontario, Canada.

NOTICE

The information in this document is subject to change without notice.

AASTRA MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY

AND FITNESS FOR A PARTICULAR PURPOSE. AASTRA shall not be liable for errors contained

herein, neither for incidental nor for consequential damages in connection with the furnishing,

performance, or use of these materials.

Aastra Technologies Limited

Concord, Ontario, Canada