Aastra DeTeWe OpenCom 100 OpenCom 107, OpenCom 130, OpenCom 131, OpenCom 150, OpenCom 510, OpenPhone 61, 63, 65, 71, 73, 75, 52, OpenPhone IPC, OpenCTI 50, OpenPhone 27, RFP 22, RFP 24, DECT User Guide

OpenCom 107

Mounting and Commissioning

User Guide

Welcome to Aastra DeTeWe

Thank you for choosing this Aastra DeTeWe product. Our product meets the strictest requirements with regard to quality and design.

The following operating instructions will assist you in using your OpenCom 107 and answer most of the questions that may arise.

If you require further technical support or information about other Aastra DeTeWe products, please refer to our website at www.Aastra-DeTeWe.de. It provides additional notes and tips on the product.

OpenCom 100 Product Family

This user guide applies to the OpenCom 100 product family comprising the

OpenCom 107, OpenCom 130, OpenCom 131, OpenCom 150 and OpenCom 510 systems.

If a reference is made in the text to the OpenCom 100, the description applies to all systems; if the individual characteristics are different, a special note is given.

For members of the product family, the following manuals exist:

■

Manual for OpenCom 107

■

Manual for OpenCom 130, OpenCom 131 and OpenCom 150

■

Manual for OpenCom 510

(19" housing)

We hope you enjoy using OpenCom 107.

Contents

1.

2.

2.1

2.2

2.3

3.

3.1

3.2

3.3

3.4

3.5

3.6

3.6.1

3.7

3.7.1

3.7.2

3.7.3

3.7.4

3.7.5

3.7.6

3.8

3.9

3.9.1

3.9.2

3.9.3

3.9.4

3.9.5

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Factory Settings on Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Telephony Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Authorisations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Internet Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Scope of Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Declarations of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Mounting Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Wall Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Available Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Positions of the Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Port Assignment, Termination, Cable Lengths . . . . . . . . . . . . . . . . . . . .21

S

0

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

U

pn

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

a/b Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

LAN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

DSL Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Basic Setting Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Connectible Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Internal/External S

0

U

pn

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

a/b Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

COM Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

LAN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

1

4.

4.1

4.2

4.3

4.4

4.5

5.

5.1

5.2

5.3

7.

7.1

7.2

6.

6.1

6.1.1

6.2

6.2.1

6.2.2

6.2.3

6.2.4

6.2.5

6.2.6

6.2.7

6.2.8

6.2.9

6.2.10

6.2.11

6.2.12

6.2.13

6.2.14

Accessories and Adapters (OpenPhone 61, 63, 65) . . . . . . . . . . . 29

U pn

Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

a/b Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Audio Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Approved Devices / Approved Accessories . . . . . . . . . . . . . . . . . . . . . . .31

Device Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Extensions and accessories for system telephones

(OpenPhone 71, 73, 75). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Power supply unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Keypad extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Brief Guide to Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

First Configuration via Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Configuring the OpenCom 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Preparing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Starting the Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Loading the Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Finishing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Preconfiguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Offline Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Remote Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Codes for IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Saving and Loading the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Receiving System Messages as E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Loading SW Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Resetting the System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Hardware Basic Settings Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Generating Your Own MoH Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

OpenCom 107 in Computer Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Introduction to TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

2

8.2

8.2.1

8.3

8.4

8.4.1

8.4.2

8.4.3

8.4.4

8.5

8.5.1

8.5.2

8.

8.1

8.1.1

8.1.2

8.1.3

8.1.4

8.1.5

8.1.6

7.3

7.3.1

7.3.2

7.3.3

7.4

7.4.1

7.4.2

7.4.3

7.5

7.6

7.6.1

7.6.2

7.6.3

7.6.4

OpenCom 107 in a Serverless LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

DNS Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

RAS Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

OpenCom 107 in a LAN with an IP-enabled Server . . . . . . . . . . . . . . . .59

DNS Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

RAS Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Branch Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Useful Information on Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Using the Web. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Voice over IP (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Propagation Delay and Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Latency and Packet Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Voice Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Call set-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Useful services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Media Gateway (MGW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Software MGW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

SIP Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

VoIP System Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Device Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

VoIP System Telephone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

LAN DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Start Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

OpenPhone IPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

3

10.

10.1

10.1.1

10.1.2

10.2

10.2.1

10.2.2

10.2.3

10.2.4

9.

9.1

9.1.1

9.1.2

9.1.3

9.2

9.2.1

9.2.2

9.2.3

9.2.4

9.3

9.3.1

9.3.2

9.3.3

9.4

11.

11.1

11.1.1

11.1.2

11.1.3

11.1.4

11.2

11.2.1

11.2.2

PBX Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Protocol: Q.SIG or DSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Master/Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

L1 Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Types of Point-to-Point Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Connection via an Active Transmission System . . . . . . . . . . . . . . . . . . .86

Connection via the Public Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Connection via Q.SIG.IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Trunk groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Technical Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Team Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Explanation of Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Team Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Examples of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Executive/Secretary Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Three-member Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Unified Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Toggle Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Call Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Activation of Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Call Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Examples of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Enquiry Station for an Operator with Two System Telephones . . . 105

Group of Three Enquiry Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

4

13.4

13.5

13.6

13.7

13.8

13.

13.1

13.2

13.3

12.

12.1

12.1.1

12.1.2

12.1.3

12.1.4

12.1.5

12.1.6

12.2

12.2.1

12.2.2

12.2.3

14.4

14.5

14.6

14.7

14.8

14.

14.1

14.2

14.3

Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Configuring the Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . . . 110

Activating the Multi-Company Variant. . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configuring and Managing Companies. . . . . . . . . . . . . . . . . . . . . . . . . 111

Assigning Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Assigning Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Allocating Routing Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Configuring the Company Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Working with the Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . 113

Company Telephone Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Making Calls Between Companies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Billing Charges per Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring the PC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

PC Offline Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Setting up TAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Setting up NET CAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Using the Systray Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Browser for OpenCTI and OpenHotel . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Setting up Video Telephony. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Synchronising the PC Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Address Queries using LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

PBX Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

WAN Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

RAS Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Branch Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

E-mail Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

E-mail Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

5

15.

15.1

15.2

15.3

15.4

15.5

16.

17.

Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

General/Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

DECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Notes on disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

6

Features

1.

Features

The OpenCom 107 communications system is designed to be connected to an

ISDN basic access using the DSS1 protocol. System access (point-to-point) and multi-terminal access (point-to-multipoint) are both supported. The two forms of access can be configured in parallel.

For this purpose, the OpenCom 107 has a total of four S

0

ports (one external, one internal and two that are switchable between internal/external).

The firmware of the OpenCom 107 is designed for configuring up to 150 users.

You can connect the following devices to the OpenCom 107:

■ analogue terminals

■

Euro-ISDN terminals

■

ISDN telephones (on the U pn

port) OpenPhone 52

■

DeTeWe system telephones

■

DeTeWe RFP 22 and RFP 24 base stations and DECT handsets (via an RFP 22/24 base station)

An S

0

port can be used by Euro-ISDN terminals working in accordance with DSS1.

A U pn

port is suitable for the OpenPhone range of DeTeWe system telephones and for the DeTeWe RFP 22/24 base stations. An analogue port is used by standard analogue devices.

If the CNIP (calling name identification presentation) feature is supported by your network provider, the latter will show you the name of callers in addition to their number for each incoming trunk call. The OpenCom 107 supports the display of the name on system telephones. However, if you have created an entry in the telephone book of the OpenCom 107 under the number of the caller, this will be displayed instead.

The OpenCom 107 can be integrated into an existing network (LAN) and be used by all workstations as an Internet access router and mail client.

7

Features

Configuration and programming of the OpenCom 107 is performed by means of a special Web browser (known as the “Web console”), which can be run on a connected PC.

The OpenCom107 can also be configured at the customer service centre and maintained by means of remote configuration.

A PC can be connected to the COM port for the purpose of configuring the system or transferring connection data.

To connect the OpenCom 107 with the existing company hardware, you can connect to any analogue port an door intercom (for example of the type “T-Com

DoorLine” or “Siedle DoorCom”). These can be used to operate a door opener and a doorbell via the system, for example.

The OpenCom 107 allows you to use CTI (Computer Telephony Integration) applications made by other manufacturers. This requires installation of a TAPI driver on

a Windows PC (see Setting up TAPI starting on page 117). The OpenCom 107 also

has an integrated dialling wizard: the OpenCTI 50. Via the OpenCTI 50 users can call up and use telephone functions on PCs without first having to install a special

TAPI driver.

The OpenCom 107 complies with the regulations for telecommunications equipment. The DSS1 protocol is implemented.

Packet data in the D channel

Some business applications, for instance POS terminals, cash registers or credit card terminals, require a permanent data connection over the X.25 packet data network. Packet data transfer through the ISDN D channel (according to X.31 via

SAPI 16) can also be established between several S

0

interfaces of the

OpenCom 107. Simultaneous connections are distinguished by means of a TEI

(Terminal Endpoint Identifier).

X.31 packet data can be forwarded between two S

0

interfaces (for instance an internal and external S

0

interface). Equally, data can be forwarded (“routed”) over permanent Q.SIG lines. Data can also be routed over an S

2M

interface. It is possible to operate multiple terminals with the same TEI on different internal S

0

interfaces.

A TEI mapping table allows these X.31 connections to be routed to the same external S

0

interface.

8

Features

The routing table for X.31 packet data is set in the Configurator under

PBX Configuration: X.31. Additional information can be found in the Configurator online help files.

Internet Access

It is possible to connect individual PCs to the OpenCom 107 via the internal S

0 ports, or to connect an entire LAN to the OpenCom 107 via the Ethernet port.

These PCs can access the Internet via the OpenCom 107. If Internet access is already available from an Internet service provider, this can be configured in the

OpenCom 107. If the client network is not IP-capable, the OpenCom 107 can administer the IP configuration necessary for Internet access. The OpenCom 107 has an integrated DHCP server and a DNS server, which in this case take over IP address administration and name resolution for the client PCs.

The OpenCom 107 enables Internet access for all connected PCs by means of a common IP address. Only this is externally visible. The local IP addresses of the client PCs are translated to the IP address of the OpenCom 107 by network address translation (NAT). In this way the client PCs in the LAN cannot be reached directly from the Internet. This protects them from direct external attack. The LAN is additionally protected by the OpenCom 107 filter lists, which can be customised individually (firewall function).

Note: We recommend you to read through the explana-

tions under Useful Information on Internet Access starting on page 63.

DECT Data Communication

The OpenPhone 27 DECT terminals enable PCs that are not connected to the

OpenCom 100 via the internal S

0

ports or the Ethernet interface to access the

Internet. These PCs can make full use of all the Internet and e-mail features of the

OpenCom 100.

Data is transmitted via the internal data interface of the OpenPhone 27. For this the OpenPhone 27 is connected with the serial port of the PC. The Internet can then be accessed directly via the remote data transfer (i.e. dial-up) network. The

OpenPhone 27 sets up a data connection with the OpenCom 100 via the DECT air interface. The remainder of the connection set-up is either direct - through an

ISDN B-channel - or indirect - through the internal RAS access of the

OpenCom 100. Indirect RAS access is preferable. This uses the routing function of the OpenCom 100 and thus also the security features of the shared Internet access.

9

Features

For detailed information on the installation of the required driver software and the various types of configuration, refer to the user guide for the OpenPhone 27.

For information on configuration of the OpenPhone 27 with a data interface, please refer to the online help documentation of the OpenCom 100.

E-mail

The OpenCom 107 has an integrated e-mail function that is able to use the POP3,

APOP or IMAP4 protocols to check the Internet service provider for incoming mail.

When configuring the OpenCom 107, e-mail account query can be configured for every member of staff. The OpenCom 107 then fetches the incoming e-mail headers (subjects) and senders from the mail server at set intervals, and forwards them to users’ system terminal.

E-mail accounts for the sending e-mail can also can be configured for users. Emails can then, for example, be sent directly from the OpenCTI 50 to other users.

In addition, users who have had a voicebox configured for themselves, can let themselves be notified of new voicebox messages via e-mail.

Important events and errors are kept by the OpenCom 107 in an internal log book: the error store. To inform or alert the system administrators, entries in the log book

(system messages) can be sent via e-mail.

Further Network Features

You can offer staff the possibility of dialling into the LAN by means of RAS access.

A LAN-to-LAN link can also be implemented by ISDN. In this way two

OpenCom 107s can connect their LANs by dial-in on demand.

A NET-CAPI program (driver software on the system CD-ROM) allows you to use

ISDN functions on those PCs that do not possess a built-in ISDN card.

Further Telephony Features

Installing an extra memory card allows you to operate a digital voice memory and voice information system. For more information, refer to the user guides called

“OpenVoice” and “OpenAttendant”.

You can optimise your telephone communication by using the team functions and the call-queuing function.

As your company’s requirements grow, the OpenCom 107 can be networked with other telecom systems. The OpenCom 107 can then operate as a sub-system or

DECT server. To operate the system as a DECT server the system’s U pn

ports must

10

Features be DECT-capable. It is also possible to create a telecom system with several networked telecom installations.

Voice over IP (VoIP)

The OpenCom 107 supports the connection of VoIP terminals and thereby allow telephony via the existing company network infrastructure. For this purpose, corded system terminals of the type “OpenPhone IP” are available. These devices have the same functionality and support the same features as the non-IP enabled system terminals “OpenPhone”. For users who wish to use PC supported telephony, the IP system terminals are also available as separate licensable software variations (OpenSoftphone). You will find further information in the

chapter Voice over IP (VoIP) starting on page 66).

Glossary

Refer to the explanations in the glossary (supplied as a PDF file on the system CD).

11

Factory Settings on Delivery Telephony Functions

2.

Factory Settings on Delivery

The following basic settings and features are active on delivery. We recommend that you configure the OpenCom 107 to your individual requirements before

putting it into operation (see Configuration starting on page 40).

2.1

Telephony Functions

■ The S

0

1 port is configured for multi-terminal access, the S

0 access.

2 port for system

■ The S

0

3 and S

0

4 ports are configured as internal S

0

buses with the call numbers

20 and 21.

■ The four U pn

ports are configured for OpenPhone 63 system telephones with the call numbers 30 to 33.

■ The four a/b ports are configured for analogue devices with the call numbers

10 to 13.

■ The OpenCom 107 is configured ready for operation in Germany.

■ Analogue devices: The dialling mode (pulse dialling or DTMF) is automatically detected.

■ All corded terminals connected ring when there are incoming external calls.

■ The system PIN, for example for remote-programmable call diversion, is set at

“0000”.

2.2

Authorisations

The use of functions by a terminal on the OpenCom 107 is regulated by means of authorisations. Authorisation is configured by means of user groups to which the users with their terminals are then assigned.

Three user groups are preset: “Administrators”, “Standard” and “Guests”. “Administrators” have access to all functions of the OpenCom 107 and unrestricted configuration rights. Users in the “Guests” group cannot configure the OpenCom 107, are

12

Factory Settings on Delivery Authorisations not able to make external calls, and have only restricted use of the terminal functions of the OpenCom 107. The “Standard” user group, because of its default settings, is well suited as a starting point for the creation of user groups for normal users of the system (e.g. the staff members of a company).

Note: When the OpenCom 107 is commissioned, all connected terminals are initially in the “Administrators” group until a user logs on to the Web console. Subsequently, all terminals are automatically in the “Guests” group (see also the

chapter entitled Configuring the OpenCom 107 starting on page 43). For more details on the configuration of user

groups, refer to the online help in the chapter entitled “User

Manager”.

The following terminal functions are factory preset to the “Administrators” group:

■

External line access: international numbers can be dialled from all configured telephones. External lines must be seized by entering a prefixed code.

■

Least cost routing is not active. As soon as LCR is configured, users can make calls via individually selected call-by-call providers.

■

“VIP call” is activated.

■

Announcements to system telephones are possible.

■

Baby calls can be configured.

■

If a call key is configured for a user on more than one terminal, he can program this key for more than one outgoing call, i.e. he can use his various terminals to make parallel calls from this telephone number.

■

“Pick-up” and “Pick-up selective” of calls from other telephones are activated.

Pick-up protection is deactivated.

■

“Call removal” is deactivated.

■

Callback (on busy) can be activated.

■

If more than one terminal is configured for a user under the same number, they can suppress the signalling of calls on the parallel terminals.

13

Factory Settings on Delivery Authorisations

■

Function “Reaction: Connection will be disconnected” is deactivated as callers trying to reach a terminal that cannot be reached or is busy will hear a busy signal.

■

The “call queue” function is deactivated.

■

Call forwarding to internal or external numbers can be activated. Call forwarding after delay is executed after 20 seconds. Door calls and MSN groups can be forwarded. Call forwarding for other users and call forwarding by other users are deactivated.

■

It is possible to transfer an external call to an external subscriber.

■

Three-party conferences can be set up.

■

Connections can be parked.

■

Call protection can be activated, call-waiting protection, announcement protection and pick-up protection can not be activated.

■

Transmission of one’s own phone number (MSN or system access number) can be suppressed on a per-call basis.

■

The telephone lock can be activated. The terminal PIN is “0000”.

■

Interception of “malicious” callers is possible if this feature has been ordered from the network operator.

■

The white list, black list and call filters are not preconfigured and thus not active. If these lists are configured, they can be activated for the user groups. A special list with emergency telephone numbers is preset and activated.

■

Call lists on terminals list internal calls, external calls, calls from the door and calls that the user received while they were telephoning.

■

Function keys can be programmed on system telephones, no keys are locked.

■

The evaluation of connection data by external cost-recording programs is deactivated.

■

The cost multiplier is set to 100%, i.e. the costs are not multiplied by any factor.

There are no preset basic amounts for the charging of calls.

14

Factory Settings on Delivery Internet Functions

■

Speed dialling is possible if this has been configured in the OpenCom 107 central telephone book.

■

Keypad dialling can be used.

■

The door opener can be activated from all terminals. Door calls can be forwarded.

■

Time control is not active as there are no time groups configured.

■

Call diversion for SMS calls in the fixed-line network is not activated.

■

Calls can be marked with a booking number for the purpose of project based accounting.

■

Users can use the OpenCTI 50 to send short messages to other users.

■

Every user can change the configuration of the OpenCom 107.

■

Every user can create a personal telephone book and edit entries in the central telephone book.

■

Every user can read out the charges.

■

Applications requiring a license (e.g. OpenCount) can be used after being activated.

■

Access via RAS is not allowed.

■

E-mail notification to system terminals is possible. There are no user accounts configured for the sending of e-mails, the authorisation for sending e-mails is not deactivated.

■

The multi-company variant is not activated.

2.3

Internet Functions

■ RAS access (with or without callback) can be set up for every OpenCom 107 user. RAS access requires activation of the RAS authorisation.

■ More than one mail account query can be set up for every user.

15

Factory Settings on Delivery Internet Functions

■

Every user with a system terminal can be informed automatically of the receipt of e-mails.

■

Users can disconnect existing Internet connections (via the OpenCom 107 Web console and from a system terminal if the function has been configured on that terminal).

The following IP addresses are preset for the network configuration:

■

Host name: host

■

IP address: 192.168.99.254

■

Network mask: 255.255.255.0

The following addresses are transmitted to the client PCs in the LAN via DHCP or

PPP:

■

Gateway address: 192.168.99.254

■

Domain name: domain

■

Domain name server: 192.168.99.254

■

PPP addresses: 192.168.100.0 to 192.168.100.10

■

DHCP addresses: 192.168.99.129 to 192.168.99.148

You can change the IP settings in the Configurator. Check with the network administrator responsible for the LAN if you wish to do this.

16

Installation

3.

Installation

Scope of Delivery

3.1

Scope of Delivery

The delivery consists of:

■

One OpenCom 107 communications system

■

Two connection cables for the ISDN S

0

port

■

One adapter cable for connection of RS-232 to RJ45 (for the COM port of the

OpenCom 107)

■

One set of mounting screws and wall plugs

■

One plug-in power supply (OpenCom 107 only)

■

One set of short user guides

■

One CD including the complete documentation and software

3.2

Safety Precautions

The CE symbol on the product confirms that it meets the technical guidelines on user safety and electromagnetic compatibility valid at the time of approval.

Please note:

Installation and maintenance should only be performed by specially trained personnel. Always remove the power plug from the mains socket before connecting devices to the

OpenCom 107 ports.

DANGER!

This device contains hazardous voltages. To make the system powerless, remove the power plug from the socket.

The OpenCom 107 may only be plugged into mains sockets with a protective earth conductor. Mount the OpenCom 107 only close to easily accessible sockets.

17

Installation Safety Precautions

Only open the housing cover. Unauthorised opening of the module cover and improper repair may damage the OpenCom 107 and could invalidate your warrantee.

CAUTION!

Static charges can damage the OpenCom 107. Make sure you discharge yourself and your tools before and while installing electrical and electronic components of the OpenCom 107.

Only devices that deliver safety extra-low voltage (SELV) may be connected to the

OpenCom 107. Proper use of authorised devices meets this requirement.

Only devices meeting the technical requirements may be connected to the ana-

logue ports. For details, refer to the section entitled a/b Ports starting on page 23.

Use a shielded Ethernet cable (STP cable, Shielded Twisted Pair cable) to connect the OpenCom 107 to a Local Area Network (LAN).

Do not allow any fluid to penetrate the OpenCom 107, because this may cause electric shocks or short circuits.

Do not install the OpenCom 107 during a storm. Do not connect or disconnect lines during a storm.

The OpenCom 107 is designed for indoor use only. Lay the cables so that they cannot be walked on or tripped over.

The connection of external devices to the sensor/actor should be performed by a qualified electrician.

18

Installation Declarations of Conformity

3.3

Declarations of Conformity

The OpenCom 107 ITC system conform to the requirements set down in the EU directive 99/5/EC.

The Declaration of Conformity can be viewed at the DeTeWe Web site at http://www.aastra-detewe.de.

3.4

Mounting Location

The ambient temperature for operating the OpenCom 107 must be between +5 and +40°C. The power supply must be 230 V/50 Hz AC. A separate fuse for the power supply is recommended.

To maintain the prescribed ambient temperature, mount the OpenCom 107 in a well-ventilated location, away from direct sources of heat.

Do not position the OpenCom 107

■ in front of or above heat sources such as radiators,

■ in direct sunlight,

■ behind curtains,

■ in small, unventilated, damp rooms,

■ on or near inflammable materials,

■ or near high-frequency devices such as transmitters, X-ray or similar apparatus.

Use a separate 230 V power circuit and install overvoltage protection.

3.5

Wall Mounting

The OpenCom 107 is mounted on the wall with three screws as shown in this diagram:

19

Installation Available Ports

A

332

B

184

C

134

D

Mounting plan

To fasten the screws at points B and C, remove the cover of the OpenCom 107 and insert the screws in the holes provided for this purpose. The OpenCom 107 is suspended from the screw at point A, so there must be a space of 3 mm between the screw and the wall.

3.6

Available Ports

The OpenCom 107 has the following ports (see also Positions of the Ports starting on page 21):

■

Four analogue a/b ports, designed as pressure terminals (a/b1 to a/b4)

■

One actor ports for connection to a door opener, designed as pressure terminals (Actor)

■

One S

0

port for connection to an external S

0

bus (usually the NTBA), designed as an RJ45 socket (S

0

1)

■

Two switchable S

0

ports (S

0

2 and S

0

3), which can be connected to either an internal or an external S

0

bus. The internal port is designed as a pressure terminal, the external port as an RJ45 socket

■

One S

0

port for an internal S

0

bus, designed as a pressure terminal (S

0

4). S

0

4 can also be wired externally (as a master) when networking two OpenCom 100

communications systems in a Q.SIG trunk (also refer to PBX Networking starting on page 83).

■

Four U pn

ports, designed as pressure terminals (U pn

1 to U pn

4)

■

One LAN port (10BaseT), designed as an RJ45 socket

20

Installation Port Assignment, Termination, Cable Lengths

■

One COM port for connection to a PC for configuration or transfer of call data, designed as an RJ45 socket

■

One port jack to connect the plug-in power supply. Only use the original

OpenCom 107 plug-in power supply.

CAUTIONT!

It is not allowed to operate the plug-in power supply inside the housing of the OpenCom 107.

3.6.1 Positions of the Ports

The following diagram shows the positions of the ports:

Default setting

LAN

COM S

0

1 ext

S

0

2 ext

S

0

3 ext

S

0

2 int

Position of ports on the OpenCom 107

S

0

3 int

S

0

4 int

U pn

1/2

U pn

3/4 a/b

1/2 a/b

3/4

Actuator

3.7

Port Assignment, Termination, Cable Lengths

3.7.1 S

0

Ports

Whether you use the switchable S

0 ports for internal or external communication depends on your communications requirements and the existing basic accesses.

Note that the S

0

bus requires a terminating resistor of 100 ohms at each end.

In the case of the OpenCom 107, the S

0

buses are terminated by software. You make this setting in the S

0 port configuration in the Configurator on the Web console.

You can connect up to eight terminals on every internal S

0

bus; up to three of the terminals can operate without an external power supply. The length of the four-

21

Installation Port Assignment, Termination, Cable Lengths wire cable of an internal S

0

bus must not exceed 150 m. The power consumption of each internal S

0

bus is approx. 2 W.

OpenCom

R

TR

IAE IAE

The S

0

bus is terminated at one end by the OpenCom 107.

IAE = ISDN socket (German: “ISDN Anschluß Einheit”) or an ISDN terminal.

TR = terminating resistor, the S

0

termination. The TR must be at the termination of the line. This can also be done by an appropriately wired IAE.

OpenCom

R

TR TR

IAE

IAE

The S

0

bus is terminated by the TR at the ends.

2a

2b

1a

1b

TR

TR

Termination on an ISDN socket

3.7.2 U pn

Ports

Each of the U pn

ports enable the connection of a RFP 22/24 DECT base station or an OpenPhone 61, 63 or 65 telephone using a twin-wire cable.

The maximum permissible length of the twin-wire cable on a U pn

port of an interface card is 1,000 m when 0.6 mm cable (with twisted pairs) is used. The power consumption of each U pn

port is approx. 3 W.

22

Installation Port Assignment, Termination, Cable Lengths

U pn

/RFP with 1 U pn

S

0 int

2a 2b 1a 1b

1 2 3 4 5 6 7 8

RFP with 2 U pn

1 2 3 4 5 6 7 8

1 2 3 4 5 6 7 8

Pin assignment of the S

0

and U pn ports

3.7.3 a/b Ports

The a/b ports are for operating analogue devices (e.g. a fax machine, modem or telephone). The maximum permissible length of the cable is 1,000 m when twinwire 0.6 mm cable (with twisted pairs) is used.

3.7.4 LAN Port

The LAN port enables integration of the OpenCom 107 into an existing in-house

LAN by means of a 10 Mbit hub.

A LAN line (twisted-pair line in accordance with 10BaseT) can be up to 100 m long.

Use a shielded Ethernet cable (STP cable, Shielded Twisted Pair cable).

3.7.5 DSL Port

External DSL modems can be connected via the LAN port. In the case of the

OpenCom 107, the output of the DSL modem (NTBBA) is led to the LAN port of the

OpenCom 107 via an external switch or hub. The router subsequently converts the

PPPoE protocolto the TCP/IP protocol of the LAN.

23

Installation Power Failure

OpenCom

TAE

DSL & Uk

0

DSL

Splitter

S

0

Net

TCP/IP &

PPPoE

Uk

0

NTBA S

0

DSL

PC

Crosslinked twisted pair cable

PPPoE

TCP/IP

DSL

Modem

Hub Net

Connecting the OpenCom 107 to the network via ISDN and DSL

Connection of the DSL modem is via a crossover twisted-pair line. You can also use a switchable port on the hub, which is usually indicated by an “X”.

3.7.6 Basic Setting Switch

Using the basic setting switch, it is possible to reset the OpenCom 107 system to

the factory configuration (see Factory Settings on Delivery starting on page 12).

The position of the switch can be seen in the diagram Positions of the Ports starting on page 21.

Please note:

The current configuration data is lost, the system is reset to the default configuration. For this reason you should back up your configuration regularly, the best time being after every

change. For details, refer to the chapter entitled Saving and

Loading the Configuration starting on page 49 and to the

Web console online help documentation.

3.8

Power Failure

In the event of a power failure, all the contents in the memory (program and user data) are saved without change. The internal clock continues to run for 24 hours. If the power failure lasts longer than 24 hours, the time and date are reset to the factory setting when power is switched on again. When the first external outgoing call is made, the time and date are set to the current value as given by the exchange.

24

Installation Connectible Devices

3.9

Connectible Devices

The OpenCom 107 ports offer a large number of possibilities for connecting devices.

3.9.1 Internal/External S

0

Ports

The S

0

2 and S

0

3 ports can either be connected externally (i.e. to ISDN network terminators) or internally; simultaneous use of both is not possible.

The internal S

0

4 port can also be wired externally (as a master) when networking

two OpenCom 107 communications systems in a Q.SIG trunk (also refer to PBX Net-

working starting on page 83).

Up to eight devices per bus (ISDN telephones, ISDN fax machines, ISDN base stations, ISDN cordless telephones, ISDN adapters for the PC among others) can be connected to the internal S

0

ports by twin-pair cables. The power for three of these devices can be supplied by the bus; if more devices are used, they then require their own power supplies. The internal S

0

buses enable point-to-multipoint calls as per the DSS1 protocol (Euro-ISDN).

25

Installation Connectible Devices

3.9.2 U pn

Ports

A system terminal can be connected to every U pn

port by a twin-wire cable.

The OpenPhone 61, OpenPhone 63 and OpenPhone 65 are cord-bound system terminals. The OpenPhones 63 and 65 can be cascaded on a U pn you can operate two OpenPhones on one U pn

adapter so that

port. For further details, refer to the

“OpenPhone 61, 63, 65” user guide.

You can also operate the OpenPhone 52 ISDN terminal on a U pn

port.

The RFP 22/24 base station is required for the use of cordless system telephones

(e.g. OpenPhone 26 or OpenPhone 27). The OpenPhone 27 features an USB port on which you can transfer data and surf on the Internet.

If this base station is connected to a U pn

port, four simultaneous calls are possible with the mobile parts. If the base station is connected to two U pn

ports, eight simultaneous calls are possible. However, note that only as many external connections are possible as there are externally connected B-channels available.

If you use a cordless handset such as the OpenPhone 26, this can also be contacted by other base stations using the GAP/CAP standard.

3.9.3 a/b Ports

The a/b ports a/b1 to a/b4 can be used for connecting analogue terminals. These can be for voice or data communication, and use DTMF or pulse dialling, e.g.

■ analogue telephones

■ class 3 fax machines

■ analogue modems (external or internal)

■ external devices for music on hold

■ external voice mail systems.

26

Installation Connectible Devices

Please note:

Adhere to the following notes and recommendations regarding the connection of analogue devices. Devices not meeting the technical requirements of the OpenCom 107 can cause damage to it.

Analogue Telephones

If analogue telephones are to be used, we recommend the use of devices featuring voice-frequency (VF) signalling, as the additional features of the OpenCom 107 cannot be used with pulse dialling.

Modems

The maximum transmission rate for analogue modems is 33.6 kbit/s (V.34+).

Music on Hold

A suitable external device for music on hold is the Genius 2000, manufactured by

Speech Design. If you do not operate an external MoH device, the OpenCom 107 offers an internal MoH, which you can load in the Web console Configurator in the SYS Configuration: Components menu. For details, refer to the online Help.

Please note:

Use only devices with an input impedance of 600 ohms, floating connection, for external music on hold. Incorrect input impedance can cause irreparable damage to the

OpenCom 107.

Voice Mail

If you are using an external voice mail system, it must be capable of handling the number of digits used for internal telephone numbers, e.g. five digits if you have configured five-digit internal numbers. We recommend the following Speech

Design products: Memo 200/300/400 or Memo 200-A/300-A/400-A.

The external voice mail system can be connected to internal a/b ports as well as to internal S

0

ports. For both port types the voice mail system can activate the notification for system terminals with the code procedures

*68

resp.

#68

.

Intercom System (for a/b)

The intercom systems “DoorLine T01/02” and “DoorLine T03/04” of the german

Telekom’s division T-Com can be connected via the “DoorLine M06” to any a/b port. The “DoorLine” module provides the actor for the door opener contact.

Observe the following when connecting:

27

Installation Connectible Devices

■

The intercom system and the “DoorLine” module should be set to their factory settings.

■

In the PBX Configuration: Ports: a/b: Change menu in the Configurator, select

Doorstation 2-wire under Type. Activate the Actuator option, if you want to use the actor port of the OpenCom 100 instead of the “DoorLine” relay. The

“DoorLine” actor can be operated only when the speech channel is open at the same time. The internal actor can be operated at any time.

■

The “DoorLine” intercom system has a number of bell keys to which you can assign different call numbers in the PBX Configuration: Ports: Doorbell menu in the Configurator.

■

You can call the “DoorLine” intercom system by entering the code procedure

*102

.

■

The “DoorLine” intercom system can be connected to any a/b port. However, you can use only one “DoorLine” with the OpenCom 100.

For details on installing and configuring the “DoorLine” intercom system, refer to the product user guide.

The intercom system should be installed by qualified personnel only as sensor/ actor contacts will need to be connected to the “DoorLine” module.

3.9.4 COM Port

Please note:

The connection line for the COM port can be up to three metres long.

A PC for configuring the OpenCom 107 or transmitting call data can be connected to the COM port. This call data can be evaluated in detail with the call charge registration program OpenCount.

3.9.5 LAN Port

Using the LAN port (Ethernet) you can integrate an OpenCom 107 into your corporate network (local area network), and thus use it, among other things, as an IP router for accessing the Internet.

28

Accessories and Adapters (OpenPhone 61, 63, 65) U pn

Adapter

4.

Accessories and Adapters

(OpenPhone 61, 63, 65)

The OpenPhone 63 and OpenPhone 65 system telephones have one or two slots on the rear for various adapters and other accessories. Further information on installing and operating these add-ons can be found in the “OpenPhone 61, 63,

65” user guide under “Add-ons (with & without an Adapter)”.

In the following you will find technical details on the add-ons and a list of compatible accessories.

4.1

U pn

Adapter

The U pn

adapter is an adapter with a U pn

port for connecting another

OpenPhone 61, 63, 65 system telephone and a socket for an extra plug-in power supply.

Weight: 70 g

Dimensions: 73 x 60 x 30 mm

Power consumption: max. 195 mW

Cable length: max. 30 m

Please note:

The U pn

adapter may be used only for connecting the system terminals listed above. The U pn

extension cable must not exceed 30 m in length and must not be used outdoors.

Note: An extra plug-in power supply is required to operate combinations of equipment with a power consumption that exceeds the power output of the U pn

ports.

4.2

a/b Adapter

You can use an a/b adapter to connect analogue terminals to the OpenPhone 63 and OpenPhone 65 system telephones.

Connecting an a/b adapter will result in exceeding the feed performance of the

U pn

port, regardless of the range. Therefore a plug-in power supply must be additionally connected to the a/b adapter.

29

Accessories and Adapters (OpenPhone 61, 63, 65) Audio Adapter

Note: Please use the plug-in power supply with the product code 4505759. The plug-in power supply for use in the UK has the product code 4510694.

Weight: 70g

Dimensions: 73 x 60 x 30 mm

Power consumption: max. 160 mW

Cable length: max. 3 m

4.3

Audio Adapter

The audio adapter is an adapter extension with four different ports for external audio and signalling devices.

Weight: 70g

Dimensions: 73 x 60 x 30 mm

Power consumption: max. 260 mW (with relay active).

Audio Adapter Pin Assignment

Port

1

2

3

4

Used for Socket

Ear cap, second handset, headset, active speaker or microphone

RJ-10

(4-pin

Western socket)

Recording device; relay contact generates signal for starting and stopping recording.

Stereo jack,

3.5 mm

Not used on

OpenCom 107

Door display

Round power socket

(4 mm)

RJ-11 or

RJ-12

(6-pin

Western socket)

Assignment

1: microphone -

2: speaker +

3: speaker -

4: microphone +

1 (GND): recording signal, relay contact 1

2 (peak): recording signal +

3 (ring): relay contact 1

-

4, 5: relay contact 2

1, 2, 3, 6: NC

30

Accessories and Adapters (OpenPhone 61, 63, 65)Approved Devices / Approved Accessories

Electrical Data of Ports

Port

Microphone, microphone of second handset, headset microphone

Ear cap, loudspeaker of second handset, headset, headset loudspeaker

Active speaker

Recording device audio input

Recording device start/stop

(relay contact 1)

Door display

(relay contact 2)

Connection Values

Electret microphone

Typical sensitivity: 10 mV/Pa

Power feed: I < 300 µA at 1.5 V

Typical impedance: 150 ± 30 ohms

Typical sensitivity: 94 dB/1 mW

(0 dB = 20 µPa)

Max. output voltage: 1 V rms at input impedance > 10 kOhms

Typical input sensitivity: 0.24 mV

(microphone level)

Max. switching voltage:

50 VDC/29 V AC

Max. switching current: 1 ADC/0.7 A AC

Max. switching voltage: 50 VDC/29 V

AC

Max. switching current: 1 ADC/0.7 A AC

4.4

Approved Devices / Approved Accessories

Please note:

Only the following, recommended accessories may be connected to the audio adapter. The cable to the door display must not be run outdoors.

The following devices are recommended:

Type

Headset:

Headset adapter cable:

Second handset

Handset

Manufacturer, Product Designation

GN-Netcom, Profile binaural

(1869-00-03)

GN-Netcom, Profile 3-in-1 (1866-00-04)

GN Netcom, QD cable (quick coupling), smooth, Mod 4 (8800-00-01)

Siemens, L30351-F600-A366

DeTeWe, OpenPhone 60

31

Accessories and Adapters (OpenPhone 61, 63, 65) Device Combinations

The following devices are recommended:

Type

Microphone:

Loudspeaker:

Recording device:

Manufacturer, Product Designation

Winfinity, 4511326 / H 282-18

Siemens, L30460-X1278-X

No recommendation

4.5

Device Combinations

You can use the following power values to calculate the power consumption of combined equipment:

■

U pn

adapter: 195 mW

■

Audio adapter: 260 mW

■ a/b adapter: 160 mW

(must be combined with a plug-in power supply!)

■

OpenPhone 61: 1,000 mW

■

OpenPhone 63: 1,025 mW

■

OpenPhone 65: 1,140 mW

■

Up to three add-on keypad modules: 330 mW

These symbols are used in the following tables:

●

This combination is possible.

❍

Reduced tone ringing, open listening and hands-free talking volume possible.

32

Accessories and Adapters (OpenPhone 61, 63, 65) Device Combinations

Configurations without Plug-in Power Supply

(Range up to 500 m)

The following table shows examples of equipment combinations for which the maximum power consumption of 2.4 W is not exceeded.

Basic Unit: OpenPhone 63

–

–

–

●

Add-ons

Audio adapter

–

Second Terminal Power

–

●

●

U pn adapter Up to 3 keypad modules

– –

–

–

–

●

–

–

–

OpenPhone 61

OpenPhone 63 without adapter

1025 mW

1285 mW

2220 mW

2245 mW

OpenPhone 65 without adapter or keypad module

2360 mW

Basic Unit: OpenPhone 65

–

–

–

●

Add-ons

Audio adapter

–

–

Second Terminal Power

–

●

●

–

–

U pn

adapter Up to 3 keypad modules

–

●

●

–

–

❍

–

–

–

–

OpenPhone 61

1140 mW

1470 mW

1730 mW

2335 mW

OpenPhone 63 without adapter

2360 mW

OpenPhone 65 without adapter or keypad module

2475 mW

33

Accessories and Adapters (OpenPhone 61, 63, 65) Device Combinations

Configurations without Plug-in Power Supply

(Range 500 to 1000 m)

The following table shows examples of equipment combinations for which the maximum power consumption of 2.2 W is not exceeded.

Basic Unit

OpenPhone 63

OpenPhone 65

Add-ons

–

●

Audio adapter

●

Power

–

–

U pn

adapter Up to 3 keypad modules

–

–

●

●

1285 mW

1470 mW

1730 mW

Configurations with Plug-in Power Supplies

The following table shows examples of equipment combinations operating with additional power from a plug-in power supply.

Basic Unit: OpenPhone 63

Add-ons:

Up to 3 keypad modules

Audio adapter

●

●

●

U pn adapter and plug-in power supply

Second terminal (OpenPhone, OP)

OP 61

●

OP 63 without adapter

●

OP 65 without adapter and with 1 keypad module

●

34

Accessories and Adapters (OpenPhone 61, 63, 65) Device Combinations

●

●

●

●

●

●

Basic Unit: OpenPhone 65

Add-ons:

Up to 3 keypad modules

Audio adapter

U pn adapter and plug-in power supply

Second terminal (OpenPhone, OP)

OP 61 OP 63 without adapter

OP 65 without adapter and with 1 keypad module

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

35

Extensions and accessories for system telephones (OpenPhone 71, 73, 75) Power supply

5.

Extensions and accessories for system telephones

(OpenPhone 71, 73, 75)

5.1

Power supply unit

The power supply unit 4516000 (in Britain operate only the AC adapter with the part no. 4516001)is required in the following cases:

■ when connecting a keypad extension to a OpenPhone 73/75 system telephone

(see also the chapter Keypad extensions starting on page 37)

■ when using the OpenPhone 73/75 IP system telephone (with or without keypad extension) where no Power over LAN is available in the network

Connecting the power supply unit to an IP telephone

The connector for the power supply unit is in the bottom of the telephone’s casing and is indicated by the symbol .

1. Plug the power supply unit’s RJ45 jack into the socket provided.

2. Pass the power supply unit’s cable through the recesses on the underside of the IP system telephone.

3. Connect the power supply unit to the mains power supply (see Connecting the

keypad extension starting on page 38).

36

Extensions and accessories for system telephones (OpenPhone 71, 73, 75) Keypad exten-

5.2

Keypad extensions

Up to three keypad extensions can be connected to each system telephone. The following equipment combinations are possible:

Overview: Combinations of system telephones and keypad extensions

System telephone connectable keypad extension …

Key Extension 73P

… features

– OpenPhone 73

– OpenPhone 73 IP

– OpenPhone 75

– OpenPhone 75 IP

Key Extension 75D

– 36 keys with LED display

– Labelled using paper inlays

– 20 keys with LED display

– 3 keys with LED display for allocating levels, providing you with up to programmable

60 memory locations and functions on each keypad extension

– Keys labelled via the display; a display line is assigned to each key

The number of keypad extensions connected to a system telephone (up to three) can be set in the Configurator of the OpenCom 107’s Web Console (in the menu

PBX Configuration: Devices: System telephone or VoIP telephone). Here the keys can also be programmed as call keys or assigned functions or destination call numbers. Users can change this programming as required.

The maximum distance between the connecting socket that the telephone/ keypad extension device combination is operating through and the

OpenCom 107 must be less than 1000 metres. You will need a plug-in power supply unitto provide power. The power supply unit is plugged into the last in the series of keypad extensions.

Configuration Needs Power Supply

U pn

system telephone

U pn

system telephone with 1-3 keypad extensions

No

Yes

IP system telephone Yes

37

Extensions and accessories for system telephones (OpenPhone 71, 73, 75) Keypad exten-

Configuration

IP system telephone with 1-3 keypad extensions

IP system telephone with PoE (Power over Ethernet)

IP system telephone with 1-3 keypad extensions and PoE

Needs Power Supply

Yes

No

No

Connecting the keypad extension

CAUTION! Guard against static charges!

Static charges can damage the OpenCom 107’s electronic components. Make sure you discharge yourself and your tools before and during any installation work on the OpenCom 107 and any connected terminals. Use discharging underlays or antistatic mats where possible.

Please note:

Never attach a keypad extension to a system telephone that is already connected to OpenCom 107. Pull the telephone plug out of the socket before screwing the keypad extension onto it.

2

1

2

1

This symbol on the system telephone indicates the connector for the keypad extension. It is on the underside of the telephone. This symbol on the keypad extension indicates the connector for a further keypad extension.

2 2

Underside of the device: keypad extension

(left) and system telephone (right)

This symbol on the keypad extension indicates the connector for the power supply unit and is on the underside of the device. This is the same connector which can be used instead of connecting an additional keypad extension.

38

Extensions and accessories for system telephones (OpenPhone 71, 73, 75) Headset

1. Plug the keypad extension’s RJ45 jack into the system telephone’s RJ45 socket

(1).

2. Screw the keypad extension onto the system telephone (2).

3. Plug the power supply unit’s RJ45 jack into the socket provided on the righthand side of the keypad extension.

4. Pass the power supply unit’s cable through the recesses provided on the underside of the keypad extension and the system telephone.

5. Connect the power supply unit to the mains power supply.

6. Connect the system telephone with the U pn

or ethernet port.

5.3

Headset

A headset can be connected to the OpenPhone 71/73/75 system telephones and to the OpenPhone 73/75 IP telephones.

The headset must comply with the DHSG standard (connection via RJ45 jack). The manufacturers Plantronics and GN Netcom make devices suitable for this purpose.

Alternatively, you can connect a “normal” headset (RJ11 jack) using an adapter.

The headset must comply with DIN Norm EN 60950-1 Point 6.2 (“Safety of information technology equipment including electrical business equipment”).

Connecting a headset to a system telephone

The connector for the headset is in the bottom of the system telephone’s casing and is indicated by this symbol .

1. Plug the RJ45 jack on the headset cable into the socket provided.

2. Pass the cable through the recesses provided on the underside of the system telephone.

3. Activate the headset on the system telephone in the menu “Telephone settings: Headset” (see also the system telephone’s user guide).

39

Configuration

6.

Configuration

Configuration and programming of the OpenCom 107 is performed by the Confi-

gurator, a special software application integrated into the system. The Configu-

rator is operated via the Web console, which can be run on any PC connected to the OpenCom 107.

The OpenCom 107 Web console

Using the Web console, you can:

■ perform the initial configuration of the OpenCom 107,

■ configure users of the OpenCom 107 and authorise them to use certain system services,

■ carry out further system maintenance,

■ use PC-supported telephony functions,

■ read out call charge information,

■ access the OpenCom 107 telephone book.

The Web console has an integrated online help function that offers comprehensive information on configuration and maintenance of the OpenCom 107 (see

Loading the Online Help starting on page 45).

40

Configuration Brief Guide to Initial Configuration

Note: In order to use all the new system software functions, we recommend that you download the latest software from our Web site at http://www.aastra-detewe.de.

For the initial configuration you can connect the PC to the OpenCom 107 via the

Ethernet port. A COM port can also be used. The TCP/IP network protocol is used to set up a connection via one of these ports. You can then open the Web console of the OpenCom 107 and call up the Configurator from there.

Note: To avoid problems with existing network installations, the OpenCom 107’s DHCP server is designed for static address assignment in its factory settings. The OpenCom 107’s

IP address is always168.99.254 in its factory settings.

6.1

Brief Guide to Initial Configuration

Setting up a first connection is quite simple with a standard Windows PC:

1. Connect the PC’s network card with one of the OpenCom 107.’s LAN ports Use a cross-wired Ethernet cable to do this.

2. Windows 2000/XP: log on as a user with “Administrator” rights.

3. You will find the IP settings in Windows 2000/XP under Start: Settings:

Network connections: Local Area Connection. Open the dialogue box Local

Area Connection Properties, and then the dialogue box Internet Protocol

TC/IP Properties (see figure: Setting the IP address in Windows XP on page 42).

4. Note down the existing settings so that you can restore them after completing the initial configuration.

5. Change the IP Address to 192.168.99.253. Change the subnet mask to

255.255.255.0, confirm with OK and Close.

6. Start a Web browser and in the address field enter “http://192.168.99.254/”.

The Web console’s log-on page will be displayed. Enter the user name “Administrator” without a password for the initial configuration. To support your next configuration steps, you should activate the Assistant mode on the entry page of the

Configurator. Please also pay attention to the online help.

41

Configuration Brief Guide to Initial Configuration

Setting the IP address in Windows XP

Tip:

To find out the IP address of the Web console, enter the code digit procedure

*182 on a connected system telephone. You can also view the net mask by entering the procedure

*183

. The PC’s IP address must be in this network range.

Note: Deactivate any connection via a proxy server which has been configured. Open the Internet Explorer, go to the menu Extras and open the Internet options dialogue box.

Select the Connections register and deactivate the Proxy

Server.

42

Configuration Configuring the OpenCom 107

6.1.1 First Configuration via Serial Port

The serial port can also be used as alternative access for the first configuration.

Additionally, you require a crossed serial line (“null modem”).

1. Install the “occonfig” program from the product CD. To do this, you must log on as an administrator under Windows NT or Windows 2000/XP.

2. Shut down the PC. Remove all connected network leads. Connect the serial port of the PC to the COM port of the OpenCom 107. Use the connecting cable that is supplied.

3. Restart the PC. Set up an Dial-up link with the icon configured on the desktop under step 1. Enter “Administrator” without a password as your user name.

4. Start the Web browser. Enter “http://192.168.99.254/” in the address box.

You will see the log-on page of the Web console. For initial configuration, enter the username “Administrator” and a blank password.

6.2

Configuring the OpenCom 107

6.2.1 Preparing the Configuration

Before starting with the configuration, make sure you have the following documents at hand:

■ An overview of the ports

■ A list of the terminals to be connected

■ A list of the IPEIs, if you wish to log on DECT terminals in the secure procedure

■ A list of the users to be set up (staff entitled to use the services of the

OpenCom 107) with their names, departments, and the internal call numbers you want to allocate to them

■ For Internet access: the Internet service provider access data.

43

Configuration Configuring the OpenCom 107

Data not available for initial configuration can be updated or corrected at a later date.

Note: Use the Configuration Guide starting on page 126. This

will assist you in making the settings in the correct sequence.

6.2.2 Starting the Web Console

1. Start your Web browser. Enter the OpenCom 107 IP address in the “Address” box: http://192.168.99.254/.

If the configuration PC gets its IP address automatically from the OpenCom 107 or if the OpenCom 107 is entered as the domain name server, you can also start the Web console by entering the DNS name. The DNS name in the factory setting is host.domain. You can change this in the Configurator (NET Confi-

guration: LAN menu).

2. The OpenCom 107 Web console is started. First set the country in which you are operating the OpenCom 107, and in which language the Web console is to be displayed.

OpenCom 107: log-on dialogue box

3. To commence configuration, you must first log on. For the initial configuration, enter your:

44

Configuration Configuring the OpenCom 107

- user name: “Administrator”

- password: for the initial configuration, leave this box blank.

4. Confirm this by clicking on OK. This puts all connected terminals into the

“Guest” user group with restricted user rights. In this way you prevent international external calls from the terminals, for example, while you are configuring the OpenCom 107 and the users.

OpenCom 107: dialogue box for initial access

5. The software opens a dialogue for initial access. Determine an administrator password and enter it in this dialogue. Also fill in the other input fields.

6. Confirm your input with Apply.

7. Click on the Configurator button on the home page.

You will find notes on using the Configurator and in the online help. Click on Help in the menu bar or click on TOC to activate an overview of help topics.

6.2.3 Loading the Online Help

The online help can now be loaded in the Configurator:

1. Go to the SYS Configuration: Components menu. Select the entry Online

Help and click on Browse.

45

Configuration Configuring the OpenCom 107

2. Look for one of the language-specific ZIP files in the OLH directory of the product CD. Confirm your choice by clicking on Open.

3. Then click on Load to transfer the online help to the system.

Please note:

After completion of the loading operation, the system will take a few minutes to analyse the transferred file.

Note: You can download the latest version of the online help from http://www.aastra-detewe.de/.

6.2.4 Finishing the Configuration

1. When you have completed all the settings in the Configurator, you must save

the configuration (see also Saving and Loading the Configuration on page 49).

2. Then select the Log-off command in the upper menu bar.

6.2.5 Preconfiguration

Configuration of the OpenCom 107 can be prepared at your DeTeWe Customer

Service Centre or by an authorised DeTeWe dealer. For this purpose, a

OpenCom 107 installed here is programmed with the customer data (e.g. user data, call distribution schemes, cord-bound terminals). This data is stored and then loaded into the OpenCom 107 at the customer’s site by a service technician.

This prepared configuration must be completed at the customer’s site (LAN configuration and DECT terminals).

For configuration of the OpenCom 107 Internet functions, first ask the responsible system administrator for details of the customer’s LAN prerequisites.

6.2.6 Offline Configurator

With the aid of the offline configurator a configuration for the system can be issued and created on a Windows PC. Thereby most of the configuration points are available. Each system type of the product family and firmware version release 7.0 or higher, has its own offline configurator; this is managed with the aid of a starter program. The starter program is included on the product CD. The operating systems Windows 2000 and XP are supported.

46

Configuration Configuring the OpenCom 107

You can find further information in the chapter PC Offline Configuration starting on page 115.

6.2.7 Remote Configuration

The OpenCom 107 configuration can also be altered or updated remotely by a customer service centre or authorised dealer. This requires activation of internal RAS access in the OpenCom 107 for the customer service centre/authorised dealer.

Note: If one or more MSNs are entered on the

PBX Configuration: System: Remote service menu page in the Configurator and the Status option is activated, remote configuration access is then activated when a data call from one of the entered MSNs is registered.

The customer service centre/authorised dealer can then log into the

OpenCom 107 as an administrator:

■ User name: “Administrator”

■ Password: [administrator password]

Note: If you do not wish to let the customer service centre/ authorised dealer know the administrator password, you can define a temporary password for remote configuration with at least five digits.

Use the following code digit procedure on a standard terminal or a system telephone to activate internal remote maintenance access for the service centre/ authorised dealer:

Remote configuration on (log-on with administrator password)

H * 1 9 * Z (system PIN) #

Remote configuration on (log-on with temporary password)

H * 1 9 * Z (system PIN) * Z (temporary password) #

Remote configuration off

H # 1 9 #

47

Configuration Configuring the OpenCom 107

Activation is automatically cancelled 30 minutes after the last configuration activity.

Note: During remote configuration, the OpenCom 107 is blocked for RAS access by any further users.

Please note:

The system PIN is preset to “0000” and it is absolutely imperative that the system administrator changes it to prevent undesirable remote maintenance.

Using remote configuration, all OpenCom 107 settings (with the exception of the system PIN) can be edited or updated. New software versions of the OpenCom 107 and the software for the connected system terminals and base stations can also be installed (see the SYS Configuration: Firmware menu in the Configurator).

For security reasons, settings in the Configurator, Net Configuration should only be edited on site to avoid malfunctions or failures in the customer’s LAN (e.g. due

to IP address conflicts). Refer to the chapter entitled Configuration Examples starting on page 54, where interaction between the OpenCom 107 and a LAN is

explained.

Forced logoff of another user by the administrator

The configuration of the system can always only be edited by one user. Working on the configuration in parallel is not possible. This ensures that no configuration conflicts arise.

If the user “Administrator” logs in and another user with administration rights is already logged in, then the administrator can forcibly log the other user off in order to configure. This functionality, for example can be used, when configuring remotely, when a user has forgotten to log out.

In order to forcibly log a user off:

1. The “Administrator” user logs on with the administration password.

2. They open the Configurator.

A message shows which user is currently configuring the system.

3. The administrator clicks on the Take over config rights button.

The other user can make no further modifications of the configuration.

48

Configuration Configuring the OpenCom 107

6.2.8 Codes for IP Configuration

The IP configuration of the OpenCom 107 is performed on the Web console in the

Configurator, in the NET Configuration: LAN menu.

In the event that the IP configuration of the OpenCom 107 has to be changed and access via the Web console is not possible, you can also use a code digit procedure to change these basic settings. Entry can be made from an analogue telephone, an

ISDN telephone and from system telephones.

Set IP address

H *182 Z (system PIN) *

Z (www) * Z (xxx) * Z (yyy) * Z (zzz) #

Set NET mask

H *183 Z (system PIN) *

Z (www) * Z (xxx) * Z (yyy) * Z (zzz) #

Example

Enter: H*1830000*192*168

*99*254#

If required, initiate a system restart with this procedure:

H * 1 8 5 Z (system PIN) #

Use the PIN you entered in the dialogue box for initial access. The factory setting is

“0000”.

6.2.9 Saving and Loading the Configuration

Configurations are saved in a file archive and can be loaded to the OpenCom 107 either locally from a connected configuration PC, or by remote configuration.

The following configuration and customer data can be saved and loaded again:

■

Telephony and network parameters

■

User data

■

Telephone book entries

49

Configuration Configuring the OpenCom 107

■

LCR tables

For further information, refer to the online help documentation under the topic

SYS Configuration: Data backup.

6.2.10 Receiving System Messages as E-Mail

Important events and errors are kept by the OpenCom 107 in an internal log book: the error store. To inform or alert the system administrators, entries in the log book

(system messages) can be sent via e-mail.

In order not to notified of every error, the administrator can define corresponding log filters (in the Configurator, the LOG Configuration: LOG Filter menu). These filters define which errors (category, severity, number per time interval) should be notified. The e-mails always include an internal event or error number, as well as an explanation of the message. Further, extra parameters (such as the port number when a trunk line drops out) are also provided.

The mail account for this service (Account for LOG filter) is configured in the Con-

figurator, NET Configuration: E-Mail Access.

6.2.11 Loading SW Updates

New versions of the system and terminal software can be loaded to the system.

New software versions of the OpenCom 107 are loaded from the configuration PC, which accesses the Configurator (see the SYS Configuration: Firmware menu).

For information on connecting a configuration PC, see Brief Guide to Initial Configu-

ration on page 41.

The terminal software is part of the OpenCom 107 software and is automatically loaded into the terminals via the OpenCom 107 if the software version in the terminal is different from the terminal software stored in the OpenCom 107.

For further information, refer to the online help documentation under the item

SYS Configuration: Firmware.

50

Configuration Configuring the OpenCom 107

6.2.12 Resetting the System Data

You can restore the factory settings of the OpenCom 107 in the Configurator.

Should this not be possible, refer to the next section entitled Hardware Basic

Settings Switch starting on page 51.

Please note:

If this is done, all individual settings and the user data are then lost. For this reason, you should back up your configuration regularly, the best time to do so being after every

change. For details, refer to the chapter entitled Saving and

Loading the Configuration starting on page 49 and to the

Web console online help.

Proceed as follows:

1. In the Configurator, call up the SYS Configuration: Restart menu.

2. Click on Restart with Defaults.

3. Confirm this by pressing “OK” when the query dialogue box opens.

6.2.13 Hardware Basic Settings Switch

The OpenCom 107 configuration can also be reset to the factory setting by means of the hardware basic settings switch.

Please note:

If this is done, all customer settings and user data will then be lost.

To reset the OpenCom 107 to its basic settings, proceed as follows:

1. Switch off the OpenCom 107 by removing the power plug.

2. Remove the cover.

3. Press the basic settings switch. The basic settings switch is a key switch. Hold the switch down.

You can see the position of the switch in the chapter Positions of the Ports starting on page 21.

51

Configuration Configuring the OpenCom 107

4. Replace the power plug in the mains socket. Wait about 30 seconds until the lamp on the front of the OpenCom 107 starts to flash steadily.

5. Remove the power plug from the mains socket again.

6. Release the key switch.

The system data is now reset.

7. Replace the power plug in the mains socket.

The OpenCom 107 now reboots in the default configuration. The procedure is completed when all connected system terminals show the time on their displays.

8. Log on to the Web console (see Starting the Web Console on page 44). Con-

figure the OpenCom 107 (possibly by loading a saved configuration; see Saving

and Loading the Configuration on page 49).

6.2.14 Generating Your Own MoH Files

The OpenCom 107 comes with an internal MoH file for Music on Hold. The

OpenCom 107 product CD contains a number of MoH files with different volume levels, which you can load at a later time as necessary.

The file format for non-resident Music on Hold is *.wav. You can also save your own

MoH in a *.wav file and load it into the OpenCom 107.

If you have a Windows operating system, you can use the “Sound Recorder” program to generate your own MoH file. This program is usually located in the

Windows directory called “Multimedia”.

The MoH file must be coded with 8000 Hz, 8 bit mono in accordance with CCITT, A-

Law. This coding is required for the OpenCom 107 and can be set in the “Sound

Recorder” when you save the file under Format (CCITT, A-Law) and Attributes

(8000 Hz, 8 bit mono). The maximum allowable size for a MoH file is 256 KB

(approx. 32 sec. play time). If a larger file is loaded then this will be “truncated” and thereby will also only be played for 32 seconds. The MoH capacity can be subdivided in a maximum of 5 files. These files can be used for different companies or for internal and external calls.

52

Configuration Configuring the OpenCom 107

Note: If you don't have the Sound Recorder program or the appropriate codec on your Windows operating system, you should install these components from your Windows CD.

Load your MoH file in the Web console's Configurator, in the SYS Configuration:

Components menu.

Note: When generating your own MoH file, you may incur a fee for the use of non-resident melodies (e.g. a GEMA fee in

Germany or MCPS fee in the UK). The MoH files that come with your OpenCom 107 can be used free of charge.

53

Configuration Examples OpenCom 107 in Computer Networks

7.

Configuration Examples

7.1

OpenCom 107 in Computer Networks

One of the outstanding features of the OpenCom 107 is the integration of telephony and computer networks. Connect the OpenCom 107 via a computer network (LAN) with suitably configured workstations, and you can use its network features from these workstations. Using a Web browser you can access:

■ the OpenCom 107 Configurator

■ call charge administration

■ the OpenCTI 50, with which telephone functions can be used on a PC

■ the OpenCom 107 central telephone book and your personal telephone book as well as to the company telephone book (if the multi-company variant is activated).

In addition, the OpenCom 107 can be used as an Internet access server. RAS access can also be implemented using the OpenCom 107, which enables the integration of external staff in the LAN.

In this chapter you will find several examples of configurations showing integration of the OpenCom 107 in a LAN. Which example applies to your situation depends on the size and properties of the existing or planned LAN infrastructure.

Note: Several menu entries mentioned in this chapter are available only, if you switch on the Level: Expert in the top level dialogue of the Configurator.

54

Configuration Examples Introduction to TCP/IP

The following LAN prerequisites are possible:

Server configuration in the LAN

No IP server present

IP server present

DHCP server present

IP server present

No DHCP server present

OpenCom 107 Functions

OpenCom 107 functions automatically as DHCP and DNS server

OpenCom 107 functions automatically as DHCP client

System Administrator must assign IP address and DNS name for

OpenCom 107

Special case when integrating the

OpenCom 107 in a LAN; settings in the

NET Configuration: LAN menu must be coordinated with the responsible system administrator

7.2

Introduction to TCP/IP

In a single LAN it is possible to use various protocols for the transmission of data.

The connection between a workstation computer and the OpenCom 107 runs via the IP protocol (also named TCP/IP) used on the Internet. IP can be used together with other protocols (e.g. NetBEUI, AppleTalk or IPX/SPX) on the same network.

Every device participating in data transmission using IP requires a unique IP address. An IP address consists of four groups of digits from 0 to 255, each separated by a full stop. The supplementary protocols DHCP and PPP automatically assign IP addresses to devices. Class C networks normally use IP addresses in which the first three numbers are the same and the last number is uniquely assigned to a specific device in the LAN. On the Internet, unique addresses assigned by a special organisation created for this purpose are used. Within a LAN, you can use addresses which are not unique world-wide:

IP Range

192.168.0.0-

192.168.255.255

Common Netmask

255.255.255.0

172.16.0.0-172.31.255.255

255.240.0.0

10.0.0.0-10.255.255.255

255.0.0.0

Comment

256 smaller networks

1 medium network

1 large network

55

Configuration Examples OpenCom 107 in a Serverless LAN

IP enables the establishment of connections via one or more intermediate stations. The decision whether to connect directly or indirectly to the partner device depends on the network mask. The network mask for a class C network is

255.255.255.0. If the IP address of the partner device does not fit the network mask, the connection is established via the default gateway. If a device knows several data routes to different intermediate stations, one speaks of a router.

The domain name system (DNS) resolves a plain text DNS name into an IP address.

The DNS is a hierarchically structured database, distributed worldwide. A DNS server can supply information on the names and IP addresses for which it is responsible. For all other information, a DNS server contacts other DNS servers. For the establishment of every connection from the workstation, it is possible to give either an IP address, or a name that a DNS server resolves into an IP address.

Note: For further explanations of technical terms, refer to the Glossary on the CD supplied.

7.3

OpenCom 107 in a Serverless LAN

In a peer-to-peer network, the workstations are connected to one another via network cables. In many networks, the cables run in the form of a star from a central hub or switch. Such networks do not require special servers. This configuration example is also valid for a LAN with a server using a protocol other than IP

(e.g. AppleTalk or IPX/SPX).

ISP

(DNS)

S

0

OpenCom

(DHCP, RAS, int. DNS, Internet)

S

0

Net

Ext.

PC

PC 1 PC 2

S

0

Net Hub Net

The OpenCom 107 in a serverless LAN

In a serverless LAN, the OpenCom 107 takes over the IP configuration of the connected workstations. All IP settings necessary for the workstations are assigned by

56

Configuration Examples OpenCom 107 in a Serverless LAN the OpenCom 107 via DHCP (dynamic host configuration protocol). In this operating mode, an IP address space reserved for such networks is used:

192.168.99.254

255.255.255.0

192.168.99.254

192.168.99.254

OpenCom 107 IP address

Network mask (class C network)

DNS server IP address

Default gateway IP address

Install the IP network protocol and a Web browser for every workstation which is to have access to the OpenCom 107 network features.

7.3.1 DNS Name Resolution

In a serverless LAN, the internal DNS name resolution is performed by the

OpenCom 107. If you type the string “host.domain” into your browser, a DNS request is sent to the OpenCom 107 IP address. The OpenCom 107 responds with the correct IP address, so that the Configurator home page can be called up.

In a peer-to-peer network (Windows network), the workstations each have a name which is displayed in the network environment. These NetBIOS names can differ from the DNS names assigned to the workstations by the OpenCom 107. The

OpenCom 107 is not visible in the network environment.

7.3.2 Internet Access

If access to an ISP has been configured on the OpenCom 107, the OpenCom 107 can be operated as an Internet access server without any additional configuration of the workstations. When you want to see a Web page, you simply type the URL

(uniform resource locator; Internet address; “http://...”) in your browser. In a serverless LAN, the OpenCom 107 is configured as a DNS server and default gateway. The workstation therefore sends its Internet connection request to the

OpenCom 107.

In almost all cases, the request will contain a DNS name which is unknown in the internal network. When you type a URL into your browser, the OpenCom 107 receives the request to find the corresponding IP address. If the name is unknown in the LAN, the request is forwarded to an ISP’s external DNS server.

57

Configuration Examples OpenCom 107 in a Serverless LAN

Note: Workstation PCs automatically add a domain name to

URLs without a dot. You specify this domain name in the

Configurator. For example, if you have configured

“firm.co.uk” as the domain name, an access request for

“www.firm.co.uk” will be interpreted as a local DNS request which does not lead to the establishment of an Internet connection. For this reason, you should choose a name which is not used in the Internet as the domain name (“firm-opencom.co.uk” for example).

7.3.3 RAS Access

You can establish a connection to the OpenCom 107 from an external PC via an

ISDN card.

The necessary IP settings are transmitted by the OpenCom 107 on establishment of the connection. The computer that has dialled in has access to all services in the

LAN that can be used via the IP protocol. The authorisation for RAS access is set up in the Configurator via the User Manager: User Groups menu.

The technical properties of the connection can be configured in the Configurator via the NET Configuration: RAS menu. Further information can be found in the online help of the web console.

In a serverless LAN, Windows uses the NetBIOS protocol for accessing files and printers via the network environment. NetBIOS can use NetBEUI, IPX/SPX or IP as the transport protocol. In the network environment, you can only access files and printers on workstations using IP for NetBIOS.

58

Configuration Examples OpenCom 107 in a LAN with an IP-enabled Server

7.4

OpenCom 107 in a LAN with an IP-enabled

Server

In a LAN with an IP-enabled server, you should coordinate integration of the

OpenCom 107 with the responsible network administrator. You must decide on the IP address space to be used and which network services (DHCP, DNS, RAS,

Internet access) the OpenCom 107 is to handle in the LAN.

ISP

(DNS)

S

0

OpenCom

S

0

Net S

0

int

Server

(DHCP, RAS, int. DNS,

Internet)

S

0

Net

PC 1 PC 2 Ext.

PC

S

0

Net Hub Net

The OpenCom 107 in a LAN with an IP-enabled server

In many cases, an IP-enabled server configures the IP settings via DHCP for all workstations. On starting, the OpenCom 107 requests IP settings via DHCP. If this request is responded to, the OpenCom 107 uses the IP settings received. You can then use a workstation to access the OpenCom 107 Configurator under the IP address assigned by the server.

In networks in which the IP settings are made manually, you have to enter the corresponding IP settings in the OpenCom 107 Configurator (NET Configuration:

LAN menu). Here the OpenCom 107 acts as the DHCP server. A workstation requesting the IP settings via DHCP then receives the settings you made in the

Configurator.

7.4.1 DNS Name Resolution

In a LAN with an IP-enabled server, the latter is also responsible for DNS name resolution. If you want to start the Configurator by entering a DNS name, you must link this name on the server with the IP address used by the OpenCom 107. For further information, refer to the server documentation.

59

Configuration Examples OpenCom 107 in a LAN with an IP-enabled Server

Note: To access the OpenCom 107 under the same IP address after a restart, you must specify this IP address permanently on a DHCP server. On a DHCP server it is possible to link the MAC address of a network card with a specific IP address. You will find details in the server documentation.

7.4.2 Internet Access

You can also use the OpenCom 107 as an Internet access server in a LAN with an

IP-enabled server. To do this, you must enter the OpenCom 107 IP address on the server as the default gateway. In addition, you must edit the internal DNS server configuration so that the resolution of external DNS names is forwarded to the

OpenCom 107.

In this example, the Internet connection is established from a workstation via the server, which in turn requests Internet access from the OpenCom 107.

There are two different ways of suitably configuring the internal DNS server. You can enter the OpenCom 107 IP address as a DNS forwarder. If you require access to extended DNS information, you can also configure the DNS server for a recursive

DNS request without the DNS forwarder. For further explanation, refer to the DNS server documentation.

ISP

(DNS)

S

0

OpenCom

(Internet)

S

0

Net S

0

int

Server

(DHCP, RAS, int. DNS)

S

0

Net

Ext.

PC

PC 1 PC 2

S

0

Net Hub Net

The OpenCom 107 as a DNS server in a LAN with an IP server

60

Configuration Examples OpenCom 107 in a LAN with an IP-enabled Server

7.4.3 RAS Access

In a LAN with an IP-enabled server you can also enable external computers to dial in via the OpenCom 107. To do this, you should coordinate with the network administrator the IP address space which can be assigned to an external computer dialling in, and enter it in the Configurator, NET Configuration: RAS: ISDN menu, under Address Range.

ISP

(DNS)

OpenCom

(RAS, Internet)

Server

(DHCP, int. DNS)

Net S

0

S

0

Net

Ext.

PC

PC 1 PC 2

S

0

Net Hub Net

RAS access by the OpenCom 107 in a LAN with an IP server

The user account administered by the OpenCom 107, with which dialling in is permitted, only allows the establishment of direct and anonymous TCP/IP connections such as HTTP, FTP or SMTP connections. If you additionally want to allow file or printer access in the network, you must set up a suitable user account on the addressed server for network log-in. If you use the same log-in name for the

OpenCom 107 user account and the same password for the network log-in, you have to enter this combination only once when dialling in.

Note: In a larger Windows network with several segments, the lists of computer names visible in the network environment can no longer be established by broadcasts. In this case you use a special WINS server whose address the

OpenCom 107 does not make known to the workstation when dialling in with ISDN. For this reason, you enter the address of a WINS server manually in the network settings of the workstation.

61

Configuration Examples Branch Link

7.5

Branch Link

You can use the OpenCom 107 to interlink two LANs via ISDN.

To do this, you configure two OpenCom 107 systems so that they can dial in to each other.

In order for this to work, the two LANs must be configured for different IP address ranges (subnetworks). For at least one of the OpenCom 107 systems, change the prescribed address range for the LAN.

OpenCom

(IP=192.168.99.254,

Net=192.168.99.0)

Net S

0

OpenCom

(IP=192.168.11.254,

Net=192.168.11.0)

S

0

Net

PC 1 PC 2 PC 1 PC 2

Net Hub Net Net Hub Net

The OpenCom 107 in a LAN-to-LAN link

In the Configurator, NET Configuration: Branch menu you can configure the dial-in settings. The OpenCom 107 will set up a connection whenever a IP data transfer to the other LAN is requested.

Note that such a connection is only set up when specific requests are made. These can be for FTP file transfers, e-mails or downloading Web pages. Name resolution via broadcasts is not possible. If you wish to use the LAN-to-LAN link to access files and printers in the Windows network, you need an IP-enabled server that administers the name resolution for the Windows network.

As the IP address range, you can select one of the 256 class C subnetworks designed for local LANs. Select a class C sub-network in the range from 192.168.0.0 to 192.168.255.0.

62

Configuration Examples Useful Information on Internet Access

7.6

Useful Information on Internet Access

7.6.1 Costs

The OpenCom 107 uses a router function to access the Internet, which means that it automatically establishes an Internet connection when required and terminates the connection after a certain period of time if no data are being transmitted.

Unfortunately, programs other than those typically intended to access the Internet

(such as your browser or your e-mail software) may send out data packets which cause an Internet connection to be established, even if these programs are not strictly Internet-associated applications.

Examples of such programs are the Microsoft

TM

XP

TM

operating system, various multimedia programs such as Realplayer

TM

and anti-virus applications that may establish an Internet connection for automatic updates (the so-called “phone home function”).

It is therefore highly advisable to limit ISP access by specifying the maximum monthly connection time under Connection time per month (maximal) in the

NET Configuration: WAN: [Provider] menu on the web console.

7.6.2 Using the Web

A Web browser not only enables you to use the OpenCom 107 Configurator from every workstation but also to obtain a wealth of information from the Internet.

Simply enter the desired URL in the address field of the browser. Access from a stand-alone PC via an online service differs from Internet access via the

OpenCom 107 in the following respects:

■ When you request a Web page, dialling in results automatically. There is no display of dialogues with manual confirmation of dialling in or hanging up.

■ Requesting Web pages is not a connection-orientated service. When the Web page has been loaded completely, the TCP/IP connection is cleared. If you do not request further Web pages, the OpenCom 107 automatically releases the connection to the Internet after a certain, specifiable duration.

■ It is possible to call up Web pages simultaneously from several workstations.

63

Configuration Examples Useful Information on Internet Access

■

The OpenCom 107 can block access to certain Web pages by means of filter lists.

7.6.3 E-mail

One of the most important services in the Internet is e-mail. E-mails are buffered in individual e-mail accounts on a mail server. Mail servers are operated by ISPs for example. With the OpenCom 107 you can set up one or more e-mail accounts for every user account configured on the OpenCom 107. These e-mail accounts are then checked at regular intervals.

If there are new e-mails in an e-mail account, and the OpenCom 107 has been configured for this function, the user specified in the OpenCom 107 user account is notified of the new e-mail on his system terminal. OpenPhone 6x

/OpenPhone 7x and OpenPhone 2x system terminals can also display information such as the sender or the subject of the e-mail.

7.6.4 NAT

Network address translation (NAT) is activated on accessing the Internet (ISP). You require this feature in order to translate internal IP addresses to valid external IP addresses. This has three important consequences for Internet access:

■

Several workstations can share a single Internet access. You do not require a

LAN access, only a single account with the Internet service provider.

■

The IP addresses used in the LAN are translated into IP addresses valid worldwide. So you require no such addresses for your LAN.

■

Only IP connections triggered from a workstation can be established. Consequently, while you can call up Web pages from a workstation, you cannot install a Web server visible in the Internet on a workstation.

Certain protocols cannot be used when NAT is being used. This affects protocols with the following properties:

■

IP addresses are transported in the useful load, e.g. NetBIOS over IP.

■

The protocol requires an active, inward-directed connection establishment, e.g. ICQ.

64

Configuration Examples Useful Information on Internet Access

■

The protocol will function without TCP/UDP port numbers, e.g. ICMP or IGMP.

The OpenCom 107 NAT has suitable processes for ensuring the functions of many important protocols affected by these rules. These are the protocols FTP (in

“active” mode), CuSeeMe (“videoconferencing”), IRC (“chat”), ICMP errors

(“traceroute”) and ICMP echo (“ping”).

Protocols which require inward-directed connection establishment can be configured in the Net Configuration: Port Access menu. For further information, refer to the online help of this menu.

65

Voice over IP (VoIP)

8.

Voice over IP (VoIP)

The term “Voice over IP” describes the usage of IP-based data networks for telephony. It is possible to distinguish between two different types of VoIP:

■

Telephony via Internet provides cheaper charge-models for telephone services.

For telephony directly via the Internet, only the cost of data transmission is incurred. Various Gateway providers can provide crossover into the PSTN

(“Public Switched Telephone Network”) for a fee. As well as standardised protocols such as SIP and H.323, proprietary protocols such as the Skype network, are used. optimised for data communication Voice and service quality via

Internet, is often indeterminable because you are dependent on the routes of various service providers. which have been optimised for data communication

■

Telephony via Intranet enables joint usage of existing infrastructure for telephony and for data communication. Integrating the two communication networks into a single communications network can provide considerable savings. The OpenCom 107 gives users all the features of system telephony through its use of an IP-based protocol. The control of the data connections used makes it possible to define exactly the voice and service quality.

Telephony over the Internet using the OpenCom 107 provides you with the fol-

lowing options (see also SIP Telephony starting on page 73):

■

You can use low-cost “SIP trunk lines” with your existing Internet connection

■

You can use the services of a SIP gateway service provider to access the public telephone network (PSTN)

■

Automatic fallback (bundle overflow) to ISDN connections in case of the breakdown or over-occupancy of the SIP connection

■

With a M100-AT4 interface card (4 analogue trunk lines) you can also use the external IP Gateway 1 for SIP telephony

VoIP system telephony with the OpenCom 107 offers the following possibilities:

■

Use of IP-based system telephones connected to Cat5 twisted-pair ethernet cables

■

Use of IP-based system telephones via VPN, RAS, Branch or WLAN connections

66

Voice over IP (VoIP) Fundamentals

■

Using voice-data compression with compressing codecs, it is also possible to make multiple IP-based telephone calls simultaneously on a 64 kilobit/s ISDN line

■

Use of PC-supported system telephones (so-called “Softphones”) without extra hardware costs

■

TC system networking using Q.SIG-IP via VPN connections (see also PBX Net-

working starting on page 83)

Integrating voice and data communication within the Intranet can provide savings possible and a range of new possibilities. However joint usage of existing network infrastructure may also cause conflicts, with IP address configuration via DHCP for

example (for details see Start Procedure starting on page 78). You should therefore

always plan the use of VoIP in the Intranet together with your network administrator. This chapter will help you avoid possible problems.

8.1

Fundamentals

VoIP makes the transmission of voice and telephony signalling via IP (“Internet

Protocol”) possible. After a connection is established, the terminal collects voice data (PCM data), which is then sent to the receiver using an IP packet. PCM data can also be compressed to save bandwidth.

8.1.1 Propagation Delay and Bandwidth

IP-based data networks are generally not able to guarantee a specific minimum bandwidth and defined propagation delay. A synchronised 64 kilobit/s ISDN line guarantees a fixed data rate as long as the connection exists. In an IP-based data network, the data rate and propagation delay can vary. Short-term bottlenecks or retransmission due to errors may be the cause. A data flow interruption of a few seconds is barely noticeable when fetching a Web page, but it can be seriously interfere with a telephone call.

A modern Intranet normally offers enough performance reserves and reliability to make good-quality VoIP telephony possible. Specific components can also be optimised; for example by using a modern switch which evaluates the TOS byte of

IP packets or by replacing unreliable connections.

67

Voice over IP (VoIP) Fundamentals

8.1.2 Latency and Packet Length

For technical reasons, there is always a delay (“latency”) between the recording of voice data via the microphone and playback via the receiver. Voice data is recorded for a short period so that it can be sent in an IP packet. The IP packet also has a signal-propagation delay before the receiver can begin playback. For these reasons, the extra time required for voice-data encoding and decoding may be neglected.

An IP packet consists of protocol data and user data. Sending shorter voice-data packets causes the ratio between the user data and the protocol data to become unfavourable and increases the bandwidth required. Sending longer voice-data packets increases latency.

The length of the voice-data packets must therefore be adjusted to the requirements of the transmission medium. Shorter voice-data packets can be sent if a direct ethernet connection exists. If an 64 kilobit/s ISDN line is to be used for transmission, then longer voice-data packets should be used.

Longer voice data packages are generally used for SIP telephony over the Internet.

The following table provides an overview of the required bandwidth for a telephone connection with various parameter settings. The values apply to halfduplex ethernet; for full-duplex the values can be halved.

Required bandwidth (kilobit/s) with respect to Packet Length and Codec

Packet

Length (ms)

20

30

40

50

60

70

80

G.711 (not compressed)

180.8

G.729A c. 6.3 kilobit/s

68.8

51.2

42.4

37.12

33.6

31.09

29.2

G.723.1

6.3 kilobit/s

48.0

30.4

G.723.1

5.3 kilobit/s

45.9

28.3

68

Voice over IP (VoIP) Fundamentals

Note: To ensure SIP compatiblility, the older system telephones OpenPhone 63 IP and OpenPhone 65 IP does not support the G.723 codec any more.

8.1.3 Voice Quality

The achievable voice quality depends on various factors. It is possible to optimise voice-data transmission on an existing network using the available configuration settings. Measuring the network quality may also help.

The following comparison provides a guide to voice quality with specific quality levels:

Quality Levels for Voice Transmission with VoIP

2

3

Level Voice Comprehensibility

1 Very Good

Good

Satisfactory

4

> 4

Limited

Unacceptable

Comparable to

ISDN

DECT

GSM

Defective GSM

No Connection

When a call is set up, the terminals involved negotiate the voice-data compression

(“codec”) that will be used. This is the first factor that determines the achievable quality level:

■

G.711 A-Law (Level 1, uncompressed): The audio data of a PCM channel

(64 kilobit/s) is adopted one-to-one. Every VoIP terminal must support this codec. This codec can not be used with an ISDN data connection.

■

G.729A (Level 2): Reduction to approximately 8 kilobit/s.

■

G.723.1 6.3 (Level 3): Reduction to 6.3 kilobit/s.

■

G.723.1 5.3 (Level 3): Reduction to 5.3 kilobit/s.

Unfavourable packet length selection may reduce voice quality. The duration of the recording and not the data packet’s byte count is relevant in making this selection:

69

Voice over IP (VoIP) Fundamentals

■

Duration <= 30 ms: optimal transmission

■

Duration 40 - 60 ms: one quality-level depreciation

■

Duration > 60 ms: two quality-levels depreciation

The achievable voice quality also depends on the packet propagation delay and the packet loss between the terminals involved. These parameters can be determined using the “ping” program.

Note: Measurements made with “ping” are round-trip propagation delays. Divide the maximum value displayed by two.

Packet Propagation Delay and Packet Loss

Value

Propagation delay

< 50 ms

Quality Level

Optimal

Propagation delay

50-100 ms

0.5 level depreciation

Propagation delay

100-150 ms

1 level depreciation

Propagation delay

150-200 ms

2 level depreciation

Propagation delay

200-300 ms

3 level depreciation

Propagation delay

> 300 ms

4 level depreciation

Value

Loss < 1 %

Loss 1-2 %

Loss 2-3 %

Loss 3-4 %

Loss 4-6 %

Loss > 6 %

Quality Level

Optimal

0.5 level depreciation

1 level depreciation

2 level depreciation

3 level depreciation

4 level depreciation

8.1.4 Optimisation

If you detect a large fluctuation in the propagation delay during measurement, this may also cause the voice quality to deteriorate. This may indicate a defective or overloaded line caused by bit-error or collision correction resulting from retransmission by the transmission procedure.

An existing star-topology ethernet-network may uses a Hub as the central distributor of ethernet packets. A Hub repeats all ethernet packets received on all

70

Voice over IP (VoIP) Fundamentals connected lines. This can cause substantial collisions and result in a high fluctuation in the propagation delay.

If this is the case, use a modern switch component. Selective forwarding of ethernet packets (“Layer 2 switching”) avoids collisions. Modern switch components also evaluate the TOS byte of IP packets, thereby providing the optimal prerequisites for VoIP telephony.

Note: The OpenCom 107 uses a TOS byte (“Type of Service”) value of 0xB8 for IP packets with VoIP data. This requests

“Minimise Delay” and “Maximise Throughput” for IP packets marked with this value.

8.1.5 Call set-up

Various IP-based protocols are used for system telephony via the Internet protocol

(“IP”) (see also Start Procedure starting on page 78). Multiple TCP connections are

made between an IP telephone and OpenCom 107 for the telephone’s start procedure, registration and signalling.

Call data is directly exchanged between IP telephones using the RTP (“Realtime

Transport Protocol”) protocol.

Channels on a Media Gateway (MGW) are allocated for making a telephone con-

nection with an ordinary terminal or for dial tones. The MGW converts IP voice data into PCM data streams used with conventional telephony and vice versa. For this, IP voice data are exchanged between the IP telephone and the gateway.

Tip:

Switching between voice data channels may cause a slight delay in some circumstances. For example: when accepting a call on an IP telephone, headset users should wait about one second before answering.

8.1.6 Useful services

The type of data compression used for VoIP prevents these types of connections from using certain services. Take these notes into account especially if you want to use connections made via Q.SIG-IP or SIP:

■

ISDN data services can not be used

71

Voice over IP (VoIP) Media Gateway (MGW)

■

Faxes can only be sent using the uncompressed G.711 codec

■

DTMF dial tones are only received by the other party if the uncompressed

G.711 codec is used

■

Analogue modems can not be used

Tip:

Configure the actual usage for the a/b ports, e.g. set them to

Fax or Data (analogue). Connections from and to these a/b ports will then be made using uncompressed or ISDN connections where possible.

8.2

Media Gateway (MGW)

The Media Gateway transforms VoIP voice data into PCM audio data. This function converts voice data between VoIP telephones and all other terminal types.

Without the Media Gateway, VoIP telephones can only exchange call data directly with other VoIP telephones. Media Gateway functionality is also required for producing dial tones and making external phone calls with a VoIP telephone. A Media gateway card makes 8 channels available. One Media gateway channel should be available for a maximum of 3 VoIP terminals.

The Media Gateway also takes over the routing function for external SIP connections, making 8 external SIP connections possible.

8.2.1 Software MGW

Using the system software of the OpenCom 107, one Media-Gateway function is available. Depending on system process utilisation and available system memory, up to four MGW channels can be available.

The Media-Gateway function implemented in system software has the following features:

■

Up to four channels can be used simultaneously.

■

The MGW channels are not compressed, that is, only the G.711 codec is available.

■

Echo suppression does not take place.

72

Voice over IP (VoIP) SIP Telephony

■

The voice quality can be inhibited during high system utilisation.

8.3

SIP Telephony

The SIP Internet (Session Initiation Protocol) protocol provides you with a low-cost, standardised option for telephoning via the Internet. OpenCom 107 enables you to use external SIP telephone connections (SIP trunk lines). The PBX Configu-

ration: Trunks: Route menu gives you the option of making an SIP connection on a normal ISDN line in case of bundle overflow, breakdown or over-occupancy. You can also set up your system to route certain types of calls, such as international calls, to an SIP connection.

Note: You will need a Media Gateway card for SIP telephony.

You will also need a fast Internet connection such as DSL for SIP telephony.

You will also usually need the services of a SIP provider. A SIP provider operates a special server (the SIP Registrar) to handle connections. The SIP provider also operates a gateway to the ordinary telephone network which users pay to use and which enables the SIP provider to provide calls to the telephone network.A SIP connection can also accept incoming calls from the telephone network.

The same voice transmission techniques as those explained in Fundamentals starting on page 67 are used for SIP telephony. SIP telephony has the following

distinctive features:

■ Subscribers are identified through an e-mail-like “SIP ID” such as

[email protected] or [email protected].

■ SIP transmits dialling numbers always in a single data package (block dialling).

Dialling can therefore be concluded with the hash key # on the system terminal, or the end of the number will be indicated by a time-out. The value for this time-out can be defined for each SIP provider separately.

■ You must log on (“Login”) to the SIP registrar before you can use SIP telephony.

Use the OpenCom 107 to manage important information for the registration

(user name and password) of one or more SIP accounts. It is possible to make several calls simultaneously using a single SIP account.

■ A SIP connection causes constant Internet data traffic, so do not use SIP with

Internet access which is paid for according to the time used.

73

Voice over IP (VoIP) SIP Telephony

■

RTP call data is also exchanged directly between terminals for SIP telephony, so different codecs can be used for sending and for receiving. It is also possible to change codecs dynamically during a call. You should use every codec available in the VoIP profile at least once, because this will enable you to establish connections with as many SIP subscribers as possible.

■

Fairly large packet lengths are quite normal on the Internet. They compensate for the longer packet propagation delay.

■

A bidirectional RTP data stream with a dynamically-assigned UDP port number is used to set up calls between subscribers. For this reason, incomng RTP calls often fail to get past the Firewall or NAT configuration of the Internet gateway product used. Do not use OpenCom 107 as an Internet gateway if the product used is to be compatible with SIP telephony. These products provide a “Full

Cone NAT” setting for this application.

■

To enable the use of multiple devices on a single Internet connection, the IP addresses used in a LAN (often 192.168.x.x) are translated to a valid IP address using address translation (NAT - Network Address Translation), but no status information is available for NAT on an incoming RTP connection.To avoid this problem, the IP address of a workplace computer or telephone visible on the

Internet is determined using a STUN server (STUN: Simple Traversal of UDP over

NAT). You can ask your SIP provider for the STUN server.’s IP address and port number If you don’t need a STUN server, leave the SIP Provider field empty.

■

For direct SIP telephony using OpenCom 107, only SIP IDs consisting of numbers for identifying subscribers registered with the SIP provider specified can be addressed

■

For each SIP account you can create just one bundle. You can specify this bundle in routes as a connection option. You can use a network provider rule to specify the routing of numbers within a specific range to use SIP telephony

as a preference (see also PBX Networking, under Configuration starting on page 88).

You can configure SIP connections in the Configurator on the pages

PBX Configuration: SIP: Accounts and PBX Configuration: SIP: Provider. Enter the technical attributes of a specific SIP provider, such as the IP addresses for the registrar and the STUN server under Provider. Under Accounts enter the information for an existing SIP account, such as the user name, password, assigned call number and the maximum number of simultaneous calls possible.

74

Voice over IP (VoIP) VoIP System Telephones

8.4

VoIP System Telephones

The following telephones and software packages are available for VoIP system telephony:

■ OpenPhone 73 IP: This is a VoIP-enabled edition of the OpenPhone 73 system telephone. This system telephone can be extended with up to three keypad extensions (KeyExtension 73P).

■ OpenPhone 75 IP: This is a VoIP-enabled edition of the OpenPhone 75 system telephone. This system telephone can be extended with up to three keypad extensions (KeyExtension 73P or KeyExtension 75D).

■ OpenPhone IPC: This VoIP software offers the functionality of a system tele-

phone using Windows 2000/XP executable software (see OpenPhone IPC starting on page 80). This software also provides local answering machine

functionality and can be integrated into CTI applications.

■ The older VoIP system telephones OpenPhone 63 IP and OpenPhone 65 IP can still be used.

8.4.1 Device Properties

The VoIP-enabled versions of the system telephones OpenPhone 73 IP and

OpenPhone 75 IP offer the same features as the corresponding system telephones. Using VoIP system telephones is therefore not much different from using standard system telephones. The following differences exist:

■

Two RJ45 connector ports are available for ethernet connection. The ports are connected to one another via the telephone’s internal switch. The switch supports 10 Mbit/s or 100 Mbit/s full-duplex with priority given to VoIP data transmission.

LAN Port: Allows the telephone to connected to the LAN. Use a non cross-over

RJ45 patch cable to connect to a Hub or Switch.

PC Port: Allows the telephone to be connected to a workplace computer. Use a non cross-over RJ45 patch cable to connect to the PC’s network port.

■

The VoIP system telephone’s power supply is provided by an extra plug-in power supply. It is also possible to provide a power feed via PoE (“Power over

75

Voice over IP (VoIP) VoIP System Telephones

Ethernet”). PoE requires special devices for power feeds, as well as a completely wired RJ45 connection line.

■

You can also connect a standard headset via RJ45 sockets (DHSG standard) to

VoIP system telephones.

■

VoIP system telephone’s audio signals are generated by the telephone itself.

DTMF dial tones and Music on Hold are produced by the Media Gateway function.

■

A VoIP system telephone can also be operated without a permanent connection to the communications system, for example via an on-demand RAS connection.

■

Signalling data for call control, call data during three-way conferences, connections to conventional terminals and external connections is exchanged between the VoIP system telephone and the communication system. During a call between two VoIP system telephones, call data is exchanged directly between the two VoIP system telephones.

■

During the device’s start procedure, the IP address is configured and the device software is requested via the DHCP and TFTP network protocols.

8.4.2 VoIP System Telephone Configuration

The VoIP system telephones OpenPhone 73 IP and OpenPhone 75 IP obtain the required IP address configuration and operating software via the DHCP, BOOTP and TFTP IP protocols. After the power supply is assured, the device’s internal boot loader is started which controls the further start procedure.

Standard operating procedure is to contact the OpenCom 107’s DHCP server so that the start procedure can be concluded without problems. To register a new

VoIP system telephone, proceed as follows:

1. Temporarily remove the VoIP system telephone’s ethernet connection. Switch on the VoIP system telephone’s power supply. Note the MAC address shown in the display, for instance “MAC: 00:30:42:00:00:00”. Switch off the power supply.

2. In the Configurator, open the PBX Configuration: Devices: VoIP Phones page. Click on the New button.

76

Voice over IP (VoIP) VoIP System Telephones

3. Select the VoIP system telephone’s Type and enter the previously noted MAC address. Assign a Name and Phone No. Confirm with Apply.

4. Connect the ethernet connection with the VoIP system telephone’s RJ45 connector. Switch on the power supply. Verify the correct start procedure on the display.

8.4.3 LAN DHCP Server

If the LAN already uses a DHCP server to configure workplace computers, there are various options for correctly responding to VoIP system telephones’ DHCP, BOOTP and TFTP requests. A comparatively simple approach is described here.

1. Configure the LAN’s DHCP server to ignore DHCP requests from the VoIP system telephones. With a Linux DHCP server program, you must, for example, include the following lines in the system file “/etc/dhcpd.conf”:

} group { deny booting;

} host 192.168.11.12 { hardware ethernet 00:30:42:00:11:22;

Every DHCP service program has similar options. You may need to reserve a free IP address for each VoIP system telephone. You will find more details in your DHCP service program’s online help or handbook. The MAC address of all

VoIP system telephones always begins with 00:30:42.

2. Configure a fixed IP address for the OpenCom 107. To do this, call up the Confi-

gurator and open the NET Configuration: LAN page. Click on the Change button.

3. Select from Get addresses from the DHCP server the option no. Enter the current IP address configuration in IP address and Network mask. Confirm with Apply.

4. Configure the OpenCom 107’s DHCP server to assign IP addresses. To do this, call up the Configurator and open the NET Configuration: LAN: DHCP

Server page. Click on the Change button.

77

Voice over IP (VoIP) VoIP System Telephones

5. From Status, select the address assignment option. Confirm with Apply. The

DHCP Server page is re-displayed.

6. Add the configured VoIP system telephones to the list of IP addresses. Click on the New button.

7. Enter the VoIP system telephone’s IP address and MAC address. Enter the IP address reserved by the DHCP service program. Confirm with Apply.

Restart the OpenCom 107 and all connected VoIP system telephones.

8.4.4 Start Procedure

It may sometimes be useful to understand a VoIP system telephone’s start procedure. Examples:

■ A complex DHCP address assignment prevents the operation of the

OpenCom 107’s DHCP server within the LAN.

■ A VoIP system should be operated with a non-broadcast-capable IP connection. This may be an RAS connection, a VPN connection or another type of routed connection.

An external DHCP server can also control a VoIP system telephone’s start procedure. In this case, system software matching the type of VoIP system telephone must be transferred via TFTP.

After the VoIP system telephone has been connected to the mains power supply, the start procedure is as follows:

1. The boot loader starts and shows the VoIP system telephone’s MAC address in the display. A DHCP request is sent simultaneously via broadcast on the

255.255.255.255 broadcast address.

2. An IP address, network mask and the default gateway for the start procedure are sent from the DHCP server. Via the “Next server” option, the DHCP server also provides the TFTP server’s IP address and the operations software’s file name. The DHCP server uses the MAC address to select the operations software file which matches the type of device.

78

Voice over IP (VoIP) VoIP System Telephones

3. The boot loader loads the operations software file from the specified TFTP server. The TFTP server’s IP address and the file’s name are shown in the display.

The loaded operations software is started.

4. The operations software sends a DHCP request on the broadcast address

255.255.255.255. The VoIP system telephone now receives an IP address, network mask and default gateway for operations from the DHCP server. Using

“Option 43”, which is reserved for this purpose, the DHCP server also provides the IP address of the communication system and port number 8100 for registration.

5. The VoIP system telephone creates a TCP connection to the supplied IPaddress/port-number combination and sends a registration query. The

OpenCom 107 checks the MAC address sent with the registration and confirms the registration request if the VoIP system telephone is listed in the menu

PBX Configuration: Devices: VoIP Phones. The keep-alive time, port number

(8101) for telephony signalling and the value to use for the TOS byte are also communicated in the registration answer.

6. The VoIP system telephone creates a second TCP connection using the signalling port number 8101 and sends a registration analogue to the U pn

system telephones.

7. Extra connections are created using the IP protocol RTP (“Realtime Transport

Protocol”) for call data when a call is created. For calls between two VoIP system telephones, port numbers above 8200 are used. For transmission to a Media

Gateway card, a port in the range 1024 – 1087 is used.

If you wish to operate a VoIP system telephone via a routed IP connection (for example VPN or RAS) it may be necessary to configure an external DHCP server accordingly. Please note the selection of the codec and keep-alive time for RAS connections. This can be done by selecting the default profile RAS in the

PBX Configuration: Devices: VoIP Phones for the VoIP system telephone. The operations software provided via TFTP must match the type of device and communication system. You may also need to configure BOOTP, DHCP and TFTP servers for the VoIP system telephone.

79

Voice over IP (VoIP) OpenPhone IPC

8.5

OpenPhone IPC

Besides the hardware VoIP system telephones, PC software for VoIP telephony can also be deployed. This software can be used with the operating systems

Windows 98 SE/ME and Windows 2000/XP.

Software VoIP system telephone OpenPhone 75 IPC with one keypad module

As well as VoIP system telephony from workplace computers, the OpenPhone IPC includes the following features:

■

Usage via Mouse/PC keyboard

■

“Drag & Drop” call number selection

■

Integrated answering machine / recording function

■

Terminal control for the sight-impaired

■

Selectable user interface (“Skins”)

■

Display language modification

The workplace computer requires a full-duplex-enabled sound card as well as a suitable headset for audio recording and playback.

80

Voice over IP (VoIP) OpenPhone IPC

You will not need a licence to install OpenPhone IPC but you will require a licence to operate it with the OpenCom 107. Unit licences, enabling the simultaneous operation of a certain number of OpenPhone IPCs, are available.

The licences are activated in the OpenCom 107’s Configurator in the Menu

SYS Configuration: Licences. The system software includes a licence for a demo version for temporary use (60 days). Please contact your local agent or DeTeWe representative if you wish to purchase a permanent licence. Licences can be combined. Each licence can be activated only once.

8.5.1 Installation

Installation is done using a setup program. The OpenPhone IPC can also be installed without a user interface. The program can then be used via a CTI application (Net-TAPI or OpenCTI).

Start the installation program from the OpenPhone IPC product CD and follow the installation assistant’s instructions.

8.5.2 Configuration

Analogue to the VoIP system telephones, the OpenPhone IPC creates multiple IP connections to the OpenCom 107. When you start the program for the first time, the Options dialogue is automatically opened. Here you must configure the following values:

1. Enter in the VoIP IP Address field the OpenCom 107’s IP address.

2. Enter six hexadecimal-digits into the Device ID field. This device ID is not a

MAC address, so overlapping with existent MAC addresses is possible. The device ID is configured in the Configurator, on the PBX Configuration:

Devices: VoIP Phones page.

3. Confirm with OK.

Notes

VoIP system telephony requires an active IP connection to a workplace computer.

If a Firewall is installed for your workplace computer, you may need to explicitly allow this connection.

81

Voice over IP (VoIP) OpenPhone IPC

If you log on to the workplace computer using a different user name, you must reconfigure these values.

You can use any arbitrary sequence of digits not already in use in the LAN for the device ID. Select a random device ID to secure telephone usage. The device ID can only be read on the Web console.

The displayed menu texts and parts of the operations software are elements of the

OpenPhone IPC installation, but they can be loaded from the OpenCom 107 via

TFTP. where necessary

82

PBX Networking

9.

PBX Networking

OpenCom 107 provides all the features necessary for PBX networking. You need

PBX networking in the following cases:

■

To operate the OpenCom 107 as a subsidiary system on another PBX. This will also allow you to use the OpenCom 107 as a DECT server, for example.

■

To network the OpenCom 107 with an OpenCom 1000. In this way you can use the OpenCom 107 as a PBX for a branch office, for instance.

■

To network several OpenCom 107s into a PBX system.

■

To use flexible configuration possibilities of trunk lines for a OpenCom 107.

All settings that affect the configuration of PBX networking can be found in the

Configurator menu PBX Configuration: Trunks and in the PBX Configuration:

System: Settings dialogue under System linking. Refer also refer to the corresponding help topics in the OpenCom 107 online help.

You can use ISDN point-to-point connections (Q.SIG or DSS1 protocol) or IP connections (Q.SIG-IP protocol) for TK system networking.

Note: If you do not need the features of PBX networking, the simplified configuration is sufficient in most cases. For this purpose, assign the preconfigured trunk groups (bundles) Multi-terminal access or System access to the ports.

The preconfigured route called External trunk now makes it possible to seize an external line immediately or by first dialling the prefix “0”. You can rename the preconfigured bundle and the preconfigured route if required, but you cannot delete them.

83

PBX Networking

9.1

Connections

Networking two or more TK systems means interconnecting them. The

OpenCom 107 allows you to use the following connections:

■ ISDN trunk lines

■ ISDN point-to-point connections (Q.SIG) on external S

0

ports

■ IP network connections (Q.SIG-IP)

Connections

PBX PBX PBX PBX

PBX

Trunk line

Point-to-point connection

Example of a PBX network

Various line types and transmission protocols can be used for point-to-point connections. The required network topology (distance, connection capacity) determines which type of point-to-point connection is most suitable.

9.1.1 Protocol: Q.SIG or DSS1

The Q.SIG protocol, designed for ISDN point-to-point connections, is the preferable choice as the transmission protocol; alternatively, the DSS1 protocol, designed for ISDN dial-up connections in the Euro-ISDN, can be used. Certain PBX networking features can only be used with the Q.SIG/Q.SIG-IP protocol, however.

In particular, the identifier indicating whether a call is internal or external cannot be transmitted using DSS1.

Both protocols implement communication on several protocol layers:

■ L1: Layer 1 defines the physical line properties and the electrical coding of signals.

■ L2: Layer 2 enables communication via individual error-protected channels that are independent of each other.

■ L3: Layer 3 defines the administration of the individual channels and implements the features designed for ISDN.

84

PBX Networking Connections

Note: All layers of the Q.SIG-IP protocol are symmetrical. The following are unnecessary: a Master/Slave setting, clock and

synchronisation settings (please refer to Connection via

Q.SIG.IP starting on page 87).

9.1.2 Master/Slave

For an ISDN connection, it is possible to determine which PBX is the protocol master and which the protocol slave. This relationship can be determined for all three protocol layers independently of one another.

For each protocol layer, the PBX at the other end always has to be suitably configured. If one PBX is the protocol master for a layer, the other PBX must be the protocol slave for this same layer. Normally all three protocol layers are configured identically. In the case of a trunk line, the network operator is the protocol master for all three layers.

9.1.3 L1 Clock

To enable PBXs in the ISDN network to communicate with each other, they must be “clock-aligned”. The L1 protocol master sets the clock for layer 1, and the L1 protocol slave adopts (synchronises to) this clock.

When planning a PBX networking scheme, you must make sure that the L1 clock propagates from a master via a number of PBXs.

Network operator

M S

PBX1

M

M S

PBX 3

S

S

PBX 2

M

Trunk line

Point-to-point connection

Example: propagation of the L1 clock

If more than one port with the setting L1 Type = “Slave” is configured on an

OpenCom 107 and the setting L1 sync possible has been activated, then one of the ports is automatically defined as the L1 clock source. The OpenCom 107 will automatically switch the clock source to another port configured as an L1 clock source (if a line fails, for example).

85

PBX Networking Types of Point-to-Point Connections

Please note:

Reciprocal or circular application of the L1 clock is not allowed.

Example: In the above case you could reverse the L1 slave/master setting for the connection between PBX 1 and PBX 3. However, if you then activate the setting

L1 sync possible for the port of PBX 1, this may cause parts of the PBX network to stop functioning temporarily.

When applying the L1 clock of trunk lines, you can assume that the public network is “clock-aligned”. So, in the above example, you can connect additional trunk lines to one of the PBXs.

9.2

Types of Point-to-Point Connections

There are different types of connection available for an point-to-point connection between two PBXs, depending on the distance between them.

9.2.1 Direct Connection

This type of ISDN point-to-point connection joins the two systems directly to each other using a crossover twisted-pair cable. An S

0

connection can be used for distances up to 1,000 metres. Normally one PBX is the protocol master for all three layers, and the other PBX is the protocol slave for all three layers.

PBX 1

L1 master

L2 master

L3 master

Direct connection

PBX 2

L1 slave

L2 slave

L3 slave

■ Use the RJ45 jacks on one of the external S

0

ports for an S

0

connection between two OpenCom 107s.

9.2.2 Connection via an Active Transmission System

For distances exceeding the range of a direct connection, an active transmission system can increase the range to up to 50 km. Normally the L1 master is the transmission system for the two connected PBXs. For the protocol layers L2 and L3, one

PBX is normally the protocol master and the other PBX is the protocol slave.

86

PBX Networking Types of Point-to-Point Connections

PBX 1

L1 slave

L2 master

L3 master

Transmission

System

L1 master

PBX 2

L1 slave

L2 slave

L3 slave

Connection by an active transmission system

Note: The active transmission system itself gets its L1 clock either from the network operator or from a clock generator connected by wire.

9.2.3 Connection via the Public Network

Point-to-point connections via the public network of a network operator can be used for bridging distances beyond 50 km. Due to the long distance involved, for technical reasons it is not possible to synchronise the L2 protocol. Consequently, the public network is normally the protocol master for protocol layers L1 and L2.

One PBX is therefore the L3 master and the other PBX the L3 slave.

PBX 1

L1 slave

L2 slave

L3 master

Public network

L1 master

L2 master

PBX 2

L1 slave

L2 slave

L3 slave

Point-to-point connection via a public network

9.2.4 Connection via Q.SIG.IP

If you are operating a fast and continuous internet connection at two or more locations, you can establish the TK system networking via internet connection as well. The OpenCom 107 uses the Q.SIG protocol, for use with ISDN point-to-point connections and transports the protocol and voice data via IP connections.

The number of simultaneous conversations possible will depend on the capacity of the internet connection and the compression method used. A multiple S

2M point-to-point connection is simulated for each Q.SIG-IP bundle. This means that 5 virtual D channels and up to 120 voice channels are available. Both Media Gateway

Card channels and the Media Gateway software function can be used for Q.SIG-IP.

Q.SIG-IP connection data are subject to codec compression (please refer to Voice

over IP (VoIP) chapter regarding Fundamentals starting on page 67). Q.SIG-IP also

transfers the voice data directly from terminal to terminal via the RTP protocol. In certain cases, for example, when an incoming external call is placed via multiple TK systems, one or more RTP proxies may be used to forward the connection.

87

PBX Networking Configuration

Currently, there are no standards for the necessary extensions to the Q.SIG protocol. This means that you can only use Q.SIG-IP between OpenCom 107 systems

(exception: OpenCom 1000).

Networking two OpenCom 107 systems using Q.SIG-IP requires 2 licenses – one license per system. The number of possible voice connections is not restricted by the license.

Go to the PBX Configuration: Trunks: Bundle page in the Configurator to set up a Q.SIG-IP connection. Create a new bundle and select the Access type “System

Access”. Select “Q.SIG-IP” under Protocol. Configure the IP address of the other system, the port numbers to be used, the number of possible voice connections and select a VoIP profile for the codec selection. Please refer to the relevant help topics in the Online Help for the OpenCom 107 as well.

Note: Q.SIG-IP cannot be operated using a connection with

NAT.

9.3

Configuration

The possible configurations described below can be set up in the Web console using the PBX Configuration: Trunks menu.

9.3.1 Trunk groups

This is a group of lines of the same type and direction. A line can only be assigned to one trunk group (bundle).

Network operator

PBX 1 PBX 3

A E

C

B D

PBX 2

Bundle

Trunk line

Point-to-point connection

Example of a PBX network with trunk groups

In the above example, the following trunk groups are configured for PBX 1:

■

Two S

0

lines in a multi-terminal configuration to the network operator which are assigned to the “A” trunk group.

88

PBX Networking Configuration

■

Two S

0

point-to-point connections to PBX 2 which are assigned to the “C” trunk group.

■

One S

0

point-to-point connection to PBX 3 which is assigned to the “E” trunk group.

Note: A line or a trunk group cannot be seized directly. It is always performed indirectly via a route.

9.3.2 Routes

A route is a group of trunk groups enabling a connection in one direction. If the first trunk group of a route is fully utilized, the next trunk group is seized (“trunk group overflow”). One trunk group can also be used for different routes.

In the above example, a route set up for PBX 1 allows a connection to PBX 2. Trunk groups “C,” “E” and “A” are assigned to this route. If a user connected to PBX 1 wants to reach a party in PBX 2, lines will be seized in the following order:

■ PBX 1 first searches for a free channel in the “C” trunk group.

■ If all the lines in trunk group “C” are busy, the system tries to set up a connection via trunk group “E”. PBX 3 switches the connection through, provided

it is appropriately configured (refer to Numbering starting on page 90).

■ If it was not possible to set up an indirect connection via PBX 3, the system tries again via trunk group “A”. The “prefix” necessary for this can be configured with the route.

■ The user does not get a busy signal until the attempt to set up an indirect connection via the network operator has also failed.

Note: If an internal connection is switched via a network operator, the call is signalled using the external number of the calling PBX.

For each route you can define a randomly selectable code digit for seizing the route. You can also configure whether a user is authorised to seize a particular route, whether LCR is to be used for one of the trunk groups and the criteria

(business or private call, booking numbers) for evaluating call data.

89

PBX Networking Configuration

9.3.3 Numbering

A user can seize a particular route by pre-dialling a specific code digit. With this

“open numbering”, a user must always dial this code digit and then the telephone number in order to reach a party in another PBX.

If none of the telephone numbers in your PBX network occur twice, you can also configure “closed numbering”, allowing the same telephone number to be used for reaching each user within the PBX network.

With closed numbering, the OpenCom 107 determines which route to seize from the telephone number dialled. The information needed for routing a call can be configured in a numbering table containing up to 100 entries. You use this table to assign telephone numbers and/or ranges of telephone numbers to a particular route.

A default entry in the numbering table makes it possible to seize a “default route” for all remaining unassigned numbers. In particular, this simplifies configuration of the OpenCom 107 as a subsidiary system: the only entry you assign to the default entry is the route to the host system

PBX

100-199 c d a b

PBX

400-499

4: b

D: c

D: a

PBX

200-299 e g h

3: e

5: h

D: d f

PBX

300-399 k

5: k

D: f

PBX

500-599 i

3: i

D: g

D:Default

Route

Example of closed numbering tables

The automatic switching of call requests (i.e. routing) by means of trunk group overflow or default numbering can lead to “circular switching”.

To avoid this, a “transit” counter is incremented whenever a connection is switched through on Q.SIG lines. When the configured maximum value is reached, further switching stops.

90

PBX Networking Technical Details

9.4

Technical Details

A different PBX number must be set for each OpenCom 107 in a PBX network. This setting can be found in the Web console, in the menu PBX Configuration:

System: Settings under the heading System linking. You can also set the maximum value for the transit counter there. This value depends on the topology of the PBX network and should allow the system to have the maximum number of further connections possible.

You can display the connection status of the lines at any time in the Configurator menu System info: PBX: Trunks. You should check this in particular after making changes to a configuration to see whether all the lines used for system networking are operable.

Some of the features possible in Q.SIG are not supported by OpenCom 107 with all their options, for example callback on busy within the Q.SIG network. The call categories defined in Q.SIG (e.g. Emergency Call, Operator, Normal) and the Q.SIG name transmission feature (“user names”) are fully supported.

The code digits to be used for seizing a route with open numbering are not transmitted to the destination PBX and thus cannot be evaluated by it. To reseize a route (for example for a callback), you must set the appropriate digit prefixes in the trunk group configuration for the routes to be reseized.

Tip:

If, for example, you are configuring a route which can be seized using routing code “5” and have selected one or more bundles for this route, change the Prefix for dest. call num-

ber at incoming internal setting to “5” for this bundle in order to enable the route to be reseized.

Owing to their hardware properties, not all S

0

ports of the OpenCom 107 can be used for PBX networking without restrictions. Depending on the type of system, some ports can only operate in the L1 master mode or L1 slave mode. The external

S

0

ports can be set according to the following table.

OpenCom 107

S

0

1

S

S

0

2

M/S

S

0

3

M/S

S

0

4

M

91

PBX Networking

Legend

S = Slave / M/S

= Master/Slave / M

= Master

Technical Details

92

Team Functions

10. Team Functions

Introduction

10.1

Introduction

With the team functions you can manage your telephone communication tasks by assigning lines with separate call numbers to the keys of different terminals. The terminal users, or team members, can thus pick up one another’s calls or telephone each other using the configured keys.

Team functions can only be configured on the corded system telephones of the

OpenPhone 6x and OpenPhone 7x product line because only these have the required features.

10.1.1 Explanation of Keys

The team functions are programmed on the call keys of the OpenPhone 6x/

OpenPhone 7x telephones. Depending on the terminal, different numbers of call keys are available:

Number of available call-keys

Telephone

OpenPhone 61

OpenPhone 63

OpenPhone 65

OpenPhone 71

OpenPhone 73

Number of keys

One key with a display, five keys without a display

Three keys with a display, five keys without a display

19 keys with a display: nine on the telephone itself and 10 on an add-on keypad module

One key with a display, five keys without a display

Three keys with a display, five keys without a display

93

Team Functions Introduction

Number of available call-keys

Telephone

OpenPhone 73 with an additional keypad extension KeyExtension 73P

OpenPhone 75

OpenPhone 75 with an additional keypad extension KeyExtension 75D

Number of keys

36 additional keys without a display

Up to three of these keypad extensions can be used with a OpenPhone 73.

Nine keys with a display

20 additional keys with a display

Up to three of these keypad extensions can be used with a OpenPhone 75.

Note: Only one function or call number can be programmed for each call key.

The following keys can be used:

■ Trunk key: Calls (for the programmed call number, e.g. 11) are signalled to this key, and you can make internal and external calls via this number. A trunk key can be programmed with a substitute function (with another team member acting as the substitute). Calls for you are then signalled to the terminal of another team member. A trunk key also provides functions for managing calls.

For example, you can configure call protection if you do not want to be disturbed, or call diversion to another telephone.

■ Team key: As with a trunk key, a team key can be used to receive or make calls.

However, this key cannot be used to change the settings for managing calls; it is not possible, for example, to configure call diversion to another telephone.

Calls made via a team key are signalled to all terminals with a trunk key that has been programmed with the same number. For example, the team key with the number 11 calls all trunk keys with the number 11.

■ Busy key: The purpose of a busy key is to make the busy status of other team members visible. An incoming call for a busy team member is signalled on the other team member's busy key. That team member can take this call by pressing the busy key, which seizes his own terminal's trunk key. Calls taken via the busy key are not entered in the call list of the team member who was originally called. In addition, it is possible to call the respective team member via his busy key when his terminal is idle. You set up a call to this team member by pressing your own trunk key.

94

Team Functions Introduction

■

Direct call key: Only outgoing calls can be made with a direct call key; they are signalled to all terminals with the same number programmed to a trunk key.

Calls via a direct call key are signalled to the destination terminal even if that terminal has been programmed with a substitution function or call protection.

If the destination terminal has been configured for call diversion, the direct call is not diverted.

Which key is suitable for which purpose?

■

Trunk keys can be assigned call numbers for managing central communication tasks, for example, customer support. If the call numbers of the support department are assigned to trunk keys on all of its terminals, then all members of the support department can receive and manage calls and use the substitute function.

■

Team keys, for example, can be used to create a project group within a department. Calls from customers of this group can then be answered by any team member who is not busy. The team members can call each other by the team keys.

■

A busy key can be used to configure an enquiry station showing the status of the individual users. The enquiry station sees the status of the users and can put calls through by simply pressing the key.

■

Direct call keys, for example, can be configured at a terminal in a conference room to call the secretary.

10.1.2 Team Configuration

You can create teams and program call keys in the Configurator of the

OpenCom 107 (PBX Configuration: Groups and Ports: Upn menu).

Call key 1 is preset as a trunk key on all system telephones. This setting can be changed by the system administrator.

95

Team Functions Examples of Use

10.2

Examples of Use

The following examples illustrate the various uses of teams and team functions.

For information on the display texts and how to use the individual functions, refer to the chapter “Managing Calls in a Team” in the “OpenPhone 61, 63, 65” or “Open-

Phone 71, 73, 75” user guide.

10.2.1 Executive/Secretary Team

In this example, the executive/secretary team comprises two members: the executive and the secretary. The secretary has one OpenPhone 73 system telephone, and the executive has two, one of which is used as a parallel telephone in a sofa suite.

Secretary

TrK 11: Secretary

TrK 10: Executive

DK 10: Executive

11

10

Executive

TrK 10: Executive

TrK 11: Secretary

TrK 12: Private

12

Executive´s Parallel

TrK 10: Executive

TrK 12: Private

Example: executive/secretary team

Line Seizure

The secretary can be reached on the call number 11 (trunk key TrK 11: secretary’s office).

The executive can be reached on the call number 10 (trunk key TrK 10: executive’s office). He can also answer calls from his parallel telephone. In addition, a private line is configured for both of the executive’s telephones (trunk key TrK 12: private).

96

Team Functions Examples of Use

Call numbers 11 and 10 are both configured as a trunk key on the executive’s and the secretary’s terminal respectively. Thus the executive and the secretary can use either call number (for answering as well as making calls). Each can act as a substitute for the other.

The secretary’s terminal also has the executive’s call number configured as a direct call number (DK 10: executive’s office). The secretary can therefore reach the executive and put through calls even if the executive has programmed a substitute.

Line Busy Indication

If a line is busy, e.g. TrK 11 secretary’s office, the other terminal will indicate this.

The executive’s private calls via TrK 12 are not indicated on the secretary’s terminal since no appropriate trunk key is configured on the latter’s telephone.

Call Signalling

In this configuration example, calls to one’s own call number are signalled acoustically on the following telephones:

■

Call number 11 on the secretary’s telephone

■

Call numbers 10 and 12 on the executive’s telephone.

Calls for the other team member’s call number are indicated by an optical signal on one’s own telephone (flashing trunk key LED).

The parallel telephone will indicate calls only by an optical signal.

Time-delayed acoustic signalling can be configured for TrK 10 on the secretary’s telephone. If the executive, for example, does not answer a call within 10 seconds, the secretary’s telephone will start to ring.

If the executive activates a substitute function with the secretary as the substitute, calls for call number 10 will be indicated on the executive’s telephone by an optical signal only, but signalled acoustically on the secretary’s telephone. The secretary can also activate a substitute function. Calls for call number 11 are then signalled acoustically on the executive’s telephone, and indicated by an optical signal on the parallel telephone and the secretary’s telephone.

97

Team Functions Examples of Use

10.2.2 Three-member Team

The three-member team described here is an example of a team configuration within a project group, e.g. export sales.

Each team member has one OpenPhone 73 system telephone with all call keys programmed as trunk and team keys.

10

Miller

TrK 10: Miller

TK 11: Johnson

TK 12: Smith

11

Johnson

Trk 11: Johnson

TK 10: Miller

TK 12: Smith

12

Smith

TrK 12: Smith

TK 10: Miller

TK 11: Johnson

Example: three-member team

Line Seizure

Each team member’s call number, e.g. call number 10 for Miller, is programmed as a trunk key on his telephone.

On the other telephones in the team, this call number is programmed as a team key (e.g. TK 10 on Johnson’s and Smith’s telephones). The team members can thus see which number a call is for and can answer it by pressing the appropriate team key.

The team members can call each other via the team keys. For example, Miller can call number 12 by pressing TK 12; the call is then signalled to Smith’s telephone on

TrK 12.

98

Team Functions Examples of Use

Line Busy Indication

If a line is busy, e.g. TrK 11 Johnson, the team keys 11 on Miller’s and Smith’s telephones will indicate this.

Call Signalling

In this example, calls via the trunk keys are signalled acoustically. Calls via the team keys are indicated by a visual signal (the team key LED flashes).

10.2.3 Unified Team

The unified team described here is an example of a team configuration within a department in which calls are to be managed quickly (e.g. support department).

Each team member has one OpenPhone 73 system telephone with all call keys programmed as trunk keys.

Miller

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

10

11

Johnson

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

12

Smith

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

Example: unified team

Line Seizure

Call numbers 10, 11 and 12 are programmed as trunk keys on each team member’s telephone (TrK 10 to TrK 12.

All team members can use these numbers for answering as well as making calls.

99

Team Functions Examples of Use

Tip:

In this team configuration it is useful to program one of the function keys on each telephone with the “Hold” function. A call, e.g. for TrK 11, can then be put on hold by pressing the function key. If another team member then presses trunk key

TrK 11 on his telephone, he can accept the call. For further information on function keys, refer to the “OpenPhone 61, 63,

65” or “OpenPhone 71, 73, 75” user guide.

Line Busy Indication

If a line is busy, e.g. TrK 11 Johnson, the trunk keys on the other team telephones will indicate this.

Call Signalling

In this example, calls via all trunk keys are signalled acoustically.

10.2.4 Toggle Team

The toggle team described here illustrates how a large number of call numbers can be managed efficiently with the help of team functions.

Each team member has one OpenPhone 75 system telephone with all call keys programmed as trunk and team keys.

100

Team Functions Examples of Use

13

14

15

16

10

11

12

Miller 14:22

Mi .

14.Feb

.

01

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

TrK 13: Support 4

TrK 14: Support 5

TrK 15: Hotline 1

TrK 16: Hotline 2

TK 20: Support 6

TK 25: Hotline 3

20

21

22

23

24

25

26

Johnson 14:22

Mi .

14.Feb

.

01

TrK 20: Support 6

TrK 21: Support 7

TrK 22: Support 8

TrK 23: Support 9

TrK 24: Support 10

TrK 25: Hotline 3

TrK 26: Hotline 4

TK 10: Support 1

TK 15: Hotline 1

Example: toggle team

Line Seizure

Each team member is assigned seven call numbers, each programmed as a trunk key (TrK 10 to TrK 16 and TrK 20 to TrK 26). For each member, these trunk keys are programmed either as support numbers or hotline numbers.

The first support number and the first hotline number of each team member is programmed as a team key on the other member’s telephone, e.g. TrK 10 and

TrK 15 on Miller’s telephone as TK 10 and TK 15 on Johnson’s telephone. The assumption here is that most calls will go to the respective first call numbers, and team members can thus help each other out by answering one another’s calls.

On each telephone it is possible to toggle between the calls on individual lines, e.g. TrK 10 and TrK 11, by pressing the appropriate key (toggling).

101

Team Functions Examples of Use

Every call on a trunk key can be transferred to any other party by means of the R key. For more information, refer to the chapter entitled “Consultation, Toggling,

Transfer and Conference” in the “OpenPhone 61, 63, 65” or “OpenPhone 71, 73, 75” user guide.

Line Busy Indication

If a line is busy, e.g. TrK 10 on Miller’s telephone, the appropriate team key will indicate this, e.g. TK 10 on Johnson’s telephone.

Call Signalling

In this example, calls via trunk keys are signalled acoustically. Calls via team keys are indicated by a visual signal (the team key LED flashes).

102

Call Queue

11. Call Queue

Introduction

11.1

Introduction

A queue can be activated for the telephone numbers of any type of telephone, i.e. for system, analogue, ISDN and DECT telephones.

If a call number with a queue is busy, calls to this number enter the queue. The caller first hears an announcement (if function “Announcer at busy” is configured) and then a dial tone.

Calls which remain in the queue for too long are cleared from the queue. The caller then gets a busy tone. If all the positions in the queue are taken then any further calls also hear the busy tone.

The time until an external call is cleared from a queue is defined by the network operator. In Germany this is usually two minutes and in other European countries usually three minutes.

If more than one telephone number (e.g. trunk or team keys) has been configured for a telephone, separate queues are used for each number.

On the OpenPhone 65/OpenPhone 75 system telephone, additional calls are signalled by a brief tone in the loudspeaker and in the display. If calls are in the queue, a number at the beginning of the second line of the display on the

OpenPhone 65/OpenPhone 75 indicates how full the queue is. If more than one telephone number with a queue is configured on the telephone, the total number of entries are displayed.

Calls in a queue are handled by the OpenCom 107 in the following order of priority: instant connection, door calls, automatic recalls, VIP calls, then other internal and external calls. Sensor calls thus have priority over other calls, for example. Calls of the same priority level are switched in the order of their arrival.

The system administrator sets the number of calls that can be placed in a queue individually for each user group. The value can lie between “0” and “99”. The “0” value deactivates the ”Call queue” function for a user group. When the maximum number of calls in the queue is reached, further callers hear a busy tone.

Only calls which have a “voice” service indicator are administered in a queue.

103

Call Queue Introduction

Note: As calling fax machines often operate with the “voice” service indicator (e.g. on analogue ports), you should assign ports for fax machines on the OpenCom 107 to a user group

without a queue.

Queues can be combined with the “forwarding,” “pickup” and “hunt group” functions, for example, in order to configure an enquiry station for an operator.

11.1.1 Activation of Queues

Queues can be activated on a per user group basis. On delivery the default set, for all preset groups, is off.

When using queues, it often makes sense to activate call waiting protection. For this purpose, “Call waiting protection” authorisation must be allocated to the user group, and call waiting protection must be activated on the terminal.

Furthermore it is sensible to combine queues with the “Announcer at busy” function. When a caller calls a subscriber who is busy then they will hear a “central welcoming text”, for example, “Here is company XYZ. You will be immediately connected”. The function “Announcer at busy” can be set in the PBX Configuration:

Call Distribution: Incoming menu. Central welcoming texts can be recorded using the program package OpenVoice.

You should configure a new user group (e.g. “Operators”) and activate the authorisations “Call queue”, “Call waiting protection” and, if necessary, “Call forwarding”.

If users belong to this group, a queue will be activated automatically for all telephone numbers assigned to them.

11.1.2 Call Forwarding

Forwarded calls of the forwarding type “Immediately” and “On busy” have priority over queues. The queue of the forwarding telephone is not used for forwarding calls in this manner.

During the configuration of this type of call forwarding, the contents of the queue are not transferred to the target terminal. If there are still calls in the queue when the call forwarding function is activated, these calls can only be accepted on the source terminal.

104

Call Queue Examples of Use

If a call is to be forwarded “After delay”, it enters the queue. If the call has not been answered before the delay period expires, it will be forwarded to the target terminal and can then be answered there.

11.1.3 Pickup

The functions “Pickup” (from a pickup group) and “Pickup selective” can be used together with queues. A user who accepts a call using “Pickup” or “Pickup selective” picks up the next call from the queue.

11.1.4 Hunt Groups

Hunt groups of the “parallel” type are usually used together with queues, with the queues of each telephone in the group being synchronised to each other. When a call to the number of the hunt group arrives, the call enters all parallel queues. If a call from one of the queues is answered, it is removed from all other parallel queues.

11.2

Examples of Use

11.2.1 Enquiry Station for an Operator with Two

System Telephones

The operator switches all incoming calls and can either work on the

OpenPhone 65/OpenPhone 75 or the mobile terminal, the OpenPhone 27.

Configuration

■ Configure the system access or access for multiple terminals under PBX Confi-

guration: Ports: S

0

.

■ Configure the OpenPhone 65/OpenPhone 75 and e.g. a RFP 22/24 under PBX

Configuration: Ports: U pn

.

■ Configure a trunk key for the OpenPhone 65/OpenPhone 75 under PBX Confi-

guration: System telephones.

105

Call Queue Examples of Use

■

Configure the OpenPhone 27 under PBX Configuration: Ports: DECT-PP and assign the OpenPhone 27 its own telephone number. Check in the

OpenPhone 27.

■

Under PBX Configuration: Call Distribution: Incoming or PBX Configu-

ration: Call Distribution: Incoming PTP route all incoming calls to the number of the OpenPhone 65/OpenPhone 75 trunk key.

■

In the Configurator, create a new group called “Operators” under User

Manager: User groups. Activate “Call queue”, “Call waiting protection” and

“Call forwarding” for this group and set the Dial out: External option appropriately.

■

Create a user called “Operator 1” under User Manager: User. Assign this user to the “Operators” user group. Assign the telephone numbers of the

OpenPhone 65/OpenPhone 75 trunk key and the number of the mobile

OpenPhone 27 to this user.

■

Activate

Call wait. prot.

(call waiting protection) on both terminals in the

Protection

menu.

■

Configure a function key on the OpenPhone 65/OpenPhone 75 which activates/deactivates a “call forwarding immediately” to the telephone number of the mobile OpenPhone 27 (in the menu

Call diversion: Divert phone: Immediately

).

Use

Incoming calls are routed to the OpenPhone 65/OpenPhone 75 manned by the operator, who then puts the calls through. A queue is used so that callers do not get a busy signal. The display on the OpenPhone 65/OpenPhone 75 indicates how many calls there are in the queue.

If the operator wants to leave the workstation and take along the enquiry station, call forwarding to the OpenPhone 27 is activated by pressing a function key. Calls which are in the OpenPhone 65/OpenPhone 75 queue must still be answered on this telephone. New calls are signalled on the mobile OpenPhone 27 or enter its queue, allowing the OpenPhone 27 to be used as a mobile enquiry station.

On returning to the workstation, the operator deactivates call forwarding by pressing a function key. Calls which are already in the queue are switched on the mobile OpenPhone 27. New calls are signalled on the OpenPhone 65/

OpenPhone 75 or enter its queue.

106

Call Queue Examples of Use

11.2.2 Group of Three Enquiry Stations

The enquiry stations switch all incoming calls. Incoming calls are administered in queues. Depending on the number of arriving calls, one to three enquiry stations in this group are manned. The enquiry stations are each equipped with an

OpenPhone 65/OpenPhone 75.

Configuration

■ Configure the multi-terminal access or the system access under PBX Configu-

ration: Ports: S

0

.

■ Configure the three OpenPhone 65/OpenPhone 75 telephones under PBX

Configuration: Ports: U pn

.

■ Configure a trunk key with its own telephone number for each of the

OpenPhone 65/OpenPhone 75 telephones under PBX Configuration:

Devices: System telephones.

■ Configure a hunt group of the “parallel” type under PBX Configuration:

Groups: Hunt Group, and include the three telephone numbers of the trunk keys in this hunt group.

■ Under PBX Configuration: Call Distribution: Incoming or PBX Configu-

ration: Call Distribution: Incoming PTP route all incoming calls to the number of the hunt group.

■ In the Configurator, create a new group called “Operators” under User

Manager: User groups. Activate “Call queue” and “Call waiting protection” for this group.

■ In the User Manager, configure a user for each of the three operators and assign these settings to the user group called “Operators”. Allocate each User the telephone number of the trunk key of their system telephone.

■ Activate

Call wait. prot.

(call waiting protection) on all three terminals in the

Protection

menu.

■ Program a function key with the function “Sign on/sign off from hunt group” on the three system telephones (in the menu

Calls: Hunt group

).

107

Call Queue Examples of Use

Use

Incoming calls are signalled in parallel to all signed-on enquiry stations. If the enquiry stations are busy, the incoming call joins the queue on each of the terminals in the hunt group. If one of the enquiry stations accepts a call from the queue, the call is removed from the queues of all the other enquiry stations. The display at each enquiry station (OpenPhone 65/OpenPhone 75) indicates how full the queue is.

If attendants leave the station, they sign off from the hunt group by means of a function key. In contrast to Example 1, further calls do not have to be processed after the sign-off, as the calls are also registered in the queues of the other signedon enquiry stations.

Note: When the last enquiry station remaining in the hunt group signs off, further callers will hear the busy tone.

108

Multi-Company Variant

12. Multi-Company Variant

Communications systems are frequently shared by several companies. These companies want to jointly use the existing infrastructure (e.g. the existing lines and features of the system), while at the same time they wish to organise and pay for their communication completely independently of one another.

This “multi-company variant” can be implemented using the OpenCom 107 within a shared office, for example.

In the multi-company variant, the companies are essentially completely independent of one another. This allows them to have their own trunk lines, which is useful for billing purposes. The OpenCom 107 hardware and software are used equally by all the companies, however. It is possible to configure the

OpenCom 107 for each company and define the extent to which the features of the system may be used.

In brief, the features of the multi-company variant are as follows:

■

Up to five companies can be configured at the same time.

■

Every user of the OpenCom 107 is assigned to a company.

■

Each available trunk group is uniquely assigned to a company so that incoming external calls can be transferred to the correct internal subscriber.

■

For each company, every route can have its own code. For example, it is possible to activate different routes with the code “0” for different companies. This enables separate charging for outgoing external calls, for example.

■

An individual exchange (“operator”) can be set up for each company.

■

Each company can maintain the communication data of its business partners in its own company telephone book.

■

The charges can be billed individually for each company.

109

Multi-Company Variant Configuring the Multi-Company Variant

12.1

Configuring the Multi-Company Variant

The multi-company variant can be commissioned and configured by the system administrator of the OpenCom 107 without any major effort. In the multicompany variant, the communications system behaves in exactly the same way as the single-company variant. This is particularly of interest to users who want to expand their own system and at the same time operate it in a group.

The process in brief:

1. The feature must be activated (see Activating the Multi-Company Variant starting on page 110).

2. The required companies must be set up (see Configuring and Managing Com-

panies starting on page 111).

3. The users of the OpenCom 107 are assigned to the individual companies (see

Assigning Users starting on page 111).

4. In order that the OpenCom 107 can transfer incoming calls to the corresponding company (or its staff ) correctly, the existing trunk groups must be

uniquely assigned to the companies (see Assigning Trunk Groups starting on page 112).

5. In the case of outgoing external calls, the lines via which the members of a

company can make a call must be defined (see Allocating Routing Codes starting on page 112).

6. An exchange must be set up for each company so that the OpenCom 107 can correctly process statuses in which a call should be routed to the exchange (see

Configuring the Company Exchange starting on page 113).

12.1.1 Activating the Multi-Company Variant

To be able to configure several companies in the OpenCom 107, the “Multicompany variant” (OpenCompany 45) program package must first be activated.

This is done in the Configurator on the Web console in the SYS Configuration:

Licences menu. The licence confirmation you received with the program package contains all the information you require about how to proceed.

110

Multi-Company Variant Configuring the Multi-Company Variant

Only when this package has been activated are the fields required to configure the multi-company variant available in the other menus of the Web console, for example in the User Manager: User groups menu or in the PBX Configuration:

Trunks menu.

12.1.2 Configuring and Managing Companies

Up to five companies can be configured in the OpenCom 107. By default, one company with the name “Company 1” is predefined. All configuration settings, e.g. in the user groups or in the trunk group configuration, apply to this predefined default company if not other company has been selected.

Companies are set up and managed in the PBX Configuration: Companies menu:

■ A new company is created in this menu using the command New. Each company can be given a name up to 20 characters long. This name is then displayed in all configuration dialogue boxes in which company-specific settings can be defined.

■ In this menu a company can be deleted again using the command Delete. If a company is deleted which is still used at other places (in the user groups, for example), the respective configuration is changed to the default company.

■ The name of the default company can be changed, but the default company itself cannot be deleted.

12.1.3 Assigning Users

For each user you must define the company to which they belong. This assignment determines, for example, which company telephone book the user has access to and which company-specific configuration data apply to them.

As the OpenCom 107 manages users in groups, the assignment “user > company” is also established this way. The company to which each user group belongs must be defined for each group. A user group can only belong to one company, i.e. not to several. However, a company can have several user groups. It is therefore possible, in the same way as in the entire system, to allocate a range of authorisation rights for the use and configuration of features for each company.

111

Multi-Company Variant Configuring the Multi-Company Variant

When setting up a new User group (in the User Manager menu), you will find that the default company is predefined; another company can be assigned as long as no other companies have been set up.

12.1.4 Assigning Trunk Groups

Connections of the same type and in the same direction are arranged in a trunk group (e.g. S

0 multi-terminal connections). To be able to correctly transfer incoming calls to the members of the configured companies (the users) via the lines of a certain trunk group of the OpenCom 107, each of the available trunk groups must be assigned to one of the companies. This is necessary to be able to transfer incoming external calls to the correct company exchange in cases where the called internal subscriber cannot be reached (“Connection to Operator”), for example.

The assignment of trunk groups to companies is done in the PBX Configuration:

Trunks: Bundle menu.

For outgoing external calls which users set up via the lines of their company’s trunk group, the assignment of the trunk group to the company is irrelevant: the charges are assigned according to the “source” principle.

Charges are billed to the company to which the user belongs who set up the connection. The OpenCom 107 recognises this on the basis of the assignment between user groups and companies and on the basis of the routing code with which a line of the trunk group was seized. For more information, please see the following section.

12.1.5 Allocating Routing Codes

Routes are used for automatic and selective seizure of trunk groups or connections for external calls. It is possible to seize a route by predialling a code.

In the PBX Configuration: Trunks: Route menu, you can define which company can seize each route. An individual code for the seizure is allocated per route for each company. The OpenCom 107 ensures that during configuration no seizure code is allocated twice (for two different routes) for each company. If during configuration of a route no code is allocated for one of the configured companies, the route concerned cannot be seized by the members (user groups) of this company.

112

Multi-Company Variant Working with the Multi-Company Variant

12.1.6 Configuring the Company Exchange

An internal telephone number must be set up for each company which represents the exchange, i.e. “the operator”. The calls to specific extensions arriving at the exchange are routed to this number, for example, as are all external calls where the called subscriber (a user who belongs to this company) cannot be reached, as in the case of a timeout.

A company exchange is set up in the PBX Configuration: Operator menu. In this menu, you can specify an internal telephone number for each company and time group which then represents the exchange for this company.

12.2

Working with the Multi-Company Variant

All the features of the OpenCom 107 which the users may already be familiar with from the single-company variant are available in the multi-company variant. These features can be used to the same extent and can be used in exactly the same way.

The following section describes the features additionally available to the users in the multi-company variant.

12.2.1 Company Telephone Book

An individual company telephone book can be created for each company. In addition to this, “personal” and “central” telephone books exist:

■ A personal telephone book is available for each user.

■ The central telephone book can be used across the companies by all users of the OpenCom 107.

The company telephone book is a central telephone book for the whole company.

It is only available to the users/user groups who are assigned to this company. You can also define whether the members of each user group may edit the company telephone book or not.

The company telephone book is treated exactly the same way on the system terminals as the other types of telephone books. This means that the entries listed in the personal, central and company telephone books are displayed on the system phones at the same time.

113

Multi-Company Variant Working with the Multi-Company Variant

Users can also use the telephone book of their company with the OpenCTI 50

Web applications and phone book, assuming they are authorised to use these applications.

In addition, it is also possible to assign a user group with the authorisation to edit foreign company telephone books. This authorisation is useful if members of this group - e.g. the “Administrators” - service the entire system. Foreign telephone books can only be edited in the Configurator in the Phone Book menu.

The number of entries in a company telephone book is unrestricted. The

OpenCom 107 can manage up to 2,000 entries in all telephone books (in the central, personal and company telephone books).

12.2.2 Making Calls Between Companies

All users of the OpenCom 107 can make internal calls to one another, irrespective of which company they belong to. Calls between users from the different companies are therefore not subject to any restrictions.

12.2.3 Billing Charges per Company

In the Costs Web application you can output the charges for each company.

Users who are authorised to use this application can view the charges for each company.

114

Configuring the PC Software PC Offline Configuration

13. Configuring the PC Software

Further possibilities of use can be implemented on a workstation PC with the

Windows operating system by installing drivers and programmes. You can find the installation programmes required for this on the product CD that comes with the

OpenCom 107.

Proceed as follows to install extra software:

1. Log on under Windows NT or Windows 2000/XP as the administrator.

2. Insert the product CD.

If your PC is suitably configured, the CD will start automatically. Otherwise select Run from the Start menu. Click on the Browse button to look for the program “cd_start.exe” on the CD. Confirm this with Open and OK.

3. Select the required option from the start interface. Follow the program instructions.

Further instructions for various options that are available are given below.

13.1

PC Offline Configuration

The offline configurator is a reduced system software that is executable under the operating systems Microsoft Windows 2000 or Microsoft Windows XP. With the offline configurator it is possible to create system configurations for various TCsystem types – without a connection to the live system. You configure a virtual system and later, aided by the data backup, transfer the configuration to the running system.

Installing the offline configurator

1. Display the product CD contents in Windows Explorer. Search the “\OFC\” installation directory for the offline configurator.

2. Start the StartCenter installation program by double-clicking on “Setup.exe”.

Following the installation assistant’s instructions. Select the appropriate installation directory or apply the default.

115

Configuring the PC Software PC Offline Configuration

3. On the product CD, in the offline configurator installation directory, you will find ZIP archives for various TC-system types. Copy the desired ZIP archives to the installation directory.

4. End the installation with a function test. With a double-click on the newly created desktop icon, start the StartCenter program. Select from the folddown selection the desired TC-system type. Available offline configurators are now displayed as symbols. Double-click on a configurator symbol and select from the dialogue Start with Factory settings. The offline configurator starts with an command window. Open a Web browser and in the address line enter:

“http://localhost/”. Confirm with enter.

5. Configure the virtual system as usual. Using the data backup, you can save the configuration.

6. Activate the command window. End the offline configurator with the window’s menu command Close.

To maintain multiple different installations, you can copy further offline configurators to new directories of your hard-drive. Change between the directories by selecting the command Extras: Setup in the StartCenter program. Select the corresponding Working Directory in the Setup dialogue. You will find further explanations in the StartCenter online help.

Notes

■

The ITC-system serial number to which the configuration is later to be transferred is queried when starting the offline configurator. You will recognise this by the caution symbol in the left symbol-bar. Click on this symbol. Enter the serial number into the input field that opens.

The serial number is required to activate program packages requiring licenses in the offline configurator (in menu SYS Configuration: Licenses). The serial number can be obtained for the ITC-system’s Configurator in the System Info:

Versions menu.

■

If there is a firewall installed on the workstation computer, then a warning will be displayed. This warning shows that the computer is now ready-to-receiver requests for the offline configurator’s web-server service. You must permit the web-server service, for example by activating the option For this program do

not display this notification again.

116

Configuring the PC Software Setting up TAPI

■

If there is an existing web-server service installed on the workstation computer, then you must enter a new port number in the Setup dialogue of the program

StartCenter, for example 8080. In the Web browser, the address line input is then: “http://localhost:8080/”. When using different port numbers you can also start multiple offline configurators simultaneously on one workstation computer.

■

If for the Web browser there is a proxy activated, then you might have to enter the computer name “localhost” into the exceptions list (No proxy for …).

■

During deinstallation of the program StartCenter, the entire installation directory with all its sub-directories is deleted. Backup the necessary offline configurators before uninstalling.

13.2

Setting up TAPI

With a TAPI (Telephony Application Programming Interface) you can operate a CTI application (computer telephony integration). Here, the CTI application uses the services of the OpenCom 107 with the help of the TAPI driver installed on a

Windows PC.

Many telephony functions, such as enquiry, toggling, three-party conference, pickup, call protection and call forwarding can be controlled using appropriate TAPIcompatible software.

Requirements

You require an active IP network connection between the PC and the communication system. CTI functions can be used only in conjunction with system telephones.

You must therefore have configured at least one user for a system telephone. In addition, you require a TAPI 2.1-compatible CTI application, for example the

Phone Dialer included in the Windows operating system.

Installing the TAPI Driver

1. Call up the start mask from the product CD (see Configuring the PC Software on page 115).

2. Select Software: TAPI Service Provider from the start mask and follow the program instructions.

117

Configuring the PC Software Setting up TAPI

Configuring the TAPI Connection

Note: Under Windows NT or Windows 2000/XP you should log on as the user for whom you want to configure the TAPI connection.

1. In the Start menu, select Settings: Control Panel. Double-click on the Tele-

phony icon (Phone and Modem Options icon under Windows 2000/XP).

2. Change to the Telephony Drivers tab (Advanced Options tab under

Windows 2000/XP).

3. From the list of installed driver software, select OpenCom 100 Service Pro-

vider and click on Configure.

4. In the following dialogue you will find a list with the configured connections for the user who is currently logged on. Click on New.

5. In the following dialogue you provide information for the new connection. In the Connection name box you can enter a descriptive name for the connection. In the CTI server box you must enter the DNS name or the IP address of the OpenCom 107. Using the […] button you can search for this in the LAN.

In the boxes Username and Password you enter the user data of one of the users configured on the OpenCom 107. This user must be allocated a system telephone. Confirm your entry with OK.

6. The new connection is now configured. Close the opened dialogues with OK and Close.

Testing the TAPI Function

1. In the Start menu, select Programs: Accessories: Communication and then start the program called Phone Dialer.

Under Windows XP the Phone Dialer is started indirect by using the dialling function of the Address book (can be found in the start menu under Pro-

grams: Accessories). A manual start of the program file “Dialer.exe” in the

“C:\Program files\Windows NT” folder is possible also.

2. In the Tools menu, select the item Connect using... to select the system telephone that is to use the CTI application. Under Windows 2000/XP you select

118

Configuring the PC Software Setting up NET CAPI the item Options from the Edit menu. In the Lines tab you then select the system telephone from the Phone calls list.

3. Enter a telephone number in the Number box and confirm with Dial. Under

Windows 2000/XP you first click on the Dial icon and in the subsequent dialogue activate Phone call.

4. The number you entered is displayed on the selected system telephone. Lift the receiver to start dialling.

Note: This note is not relevant to Windows 2000/XP. If the

“Phone Dialer” program is not installed, you will have to install it. To do this, you open the Control Panel and click on

Software. In the Windows Setup tab you activate the Con-

nections component.

13.3

Setting up NET CAPI

With a CAPI driver (common application programming interface) Windows programmes are able to access services and functions of an ISDN card. With a network-based CAPI, the OpenCom 107 allows the use of ISDN functions also by

PCs in which no ISDN card is integrated.

Requirements

You require an active IP network connection between the PC and the telephone system.

Please note:

Before installing the CAPI driver for the OpenCom 107, any existent ISDN card must be removed and any CAPI drivers on your PC must be de-installed.

Installing the NET CAPI driver

1. Call up the start mask from the product CD (see Configuring the PC Software on page 115).

2. Select Software: NET CAPI Driver from the start mask and follow the program instructions.

119

Configuring the PC Software Using the Systray Display

Configuring the NET CAPI Driver

The NET CAPI driver requires an extra internal number so that the “virtual ISDN card” on the OpenCom 107 can be addressed:

1. Go to the Configurator, PBX Configuration: Devices: CAPI-ISDN menu. Click on Change.

2. Activate the Status check box. Enter at least one unassigned, internal number in the boxes under Parameters. Confirm your entry with Assign.

3. Go to the Configurator, User Manager: User menu. Select one of the users shown. Enter the number just assigned in one of the boxes No. 1 to No. 10.

Confirm your entry with Apply.

4. If it is to be possible to call the “virtual ISDN card” externally, or if external calls are to be possible, the number must be included in call distribution

(Configurator, PBX Configuration: Call Distribution menu).

5. After installing the NET CAPI driver, you will find an extra icon on the right side of the Windows Start bar. Click on this icon with the right mouse key. Select the

Log-on command from the menu.

Note: In the subsequent dialogue you must log on NET CAPI first with the user (user name and password) for which you configured the CAPI telephone number in the User Manager

(see Step 3).

You will find further information on the working of the NET CAPI driver and CAPI application programmes on the product CD.

Note on sending faxes

The NET CAPI can not address an analogue Group-3 fax. Use a CAPI-compatible modem-simulation driver or connect an analogue modem or analogue modem card to one of the OpenCom 107’s internal a/b ports for sending faxes.

13.4

Using the Systray Display

You can configure a systray display for the OpenCom 107 to appear in the information area of the Start bar of a workstation. This systray display constantly shows you whether a WAN, a RAS or a Branch connection via ISDN is active. It is also possible to display the current occupancy of the trunk lines.

120

Configuring the PC Software Browser for OpenCTI and OpenHotel

Requirements

To use the systray display, you must first install TAPI; see Setting up TAPI starting on page 117.

Please note:

The systray display requires a current version of TAPI. If you are using TAPI from an earlier version of the OpenCom 107, you must first install the newer version from the product CD.

Installing the systray display

1. Call up the start mask of the product CD (see Configuring the PC Software on page 115).

2. From the start mask, select Software: Install Systray. Follow the program instructions.

3. Start the program with Start: Run and the configuration dialogue is displayed.

Select one of the entries displayed under Existing PBXs. Enter your user name and password in the boxes under Log-on.

4. If you activate the Autostart check box, you will see the systray display even after restarting your PC.

5. Confirm the entries in the configuration dialogue with OK and the systray display logs on for the OpenCom 107.

6. Right-click on the systray display in the Start bar. Select Configu-

ration to call up the configuration dialogue. Select Network Con-

nections or Trunk Lines to produce a status dialogue.

13.5

Browser for OpenCTI and OpenHotel

You can simplify the daily use of the OpenCTI and OpenHotel Web applications using the Web browser especially adapted for the OpenCom 107. Each time the workstation is restarted, this browser program can automatically start and log you in. This means that the applications are always operational and can be accessed using the icon in the information area of the task bar.

121

Configuring the PC Software Setting up Video Telephony

Installing the browser

1. Call up the start mask from the product CD (see Configuring the PC Software on page 115).

2. From the start mask, select Software: Install Browser for OpenCTI or

Software: Install Browser for OpenHotel. Follow the program instructions.

3. Follow the program instructions.

After installing the browser, there is a new menu entry in the Windows start menu under Programs: OpenCTI Browser respectively Programs: Hotel Starter.

Further information can be found in the online help of the browser program. To view this, click the top left corner in the OpenCTI-browser’s program window on the system menu symbol or on the symbol in the information area of the task bar.

Select the Readme command. You will find the OpenHotel’s readme in the installation directory of this browser program.

Note: Both browser programmes can be used simultaneously.

13.6

Setting up Video Telephony

You can use the OpenCTI to switch on the video function during an internal call.

To be able do this, the Microsoft NetMeeting 3.0 program must be installed and set up on all participating workplace computers.

Note: NetMeeting is already pre-installed on the Microsoft

Windows 2000 and XP operating systems.

Set up Microsoft NetMeeting 3.0

1. Connect a standard web cam to the workplace computer and install the driver.

2. In the Windows Start menu select Run and enter: “conf.exe”. Confirm your selection with OK.

3. Follow the instructions of the Install Wizard. Registration in an Internet directory is not necessary and is not recommended. Select the installed web cam and exit the Install Wizard.

122

Configuring the PC Software Synchronising the PC Clock

4. Run a functionality test. To do this, start the NetMeeting program. Click on the call button. Under Address enter the IP address or DNS host name of a external station. Confirm your selection with Call.

Note: If Firewall software is installed on the workplace computer, a warning will now appear. This shows that the computer is now ready to receive the NetMeeting. You must allow the NetMeeting, by activating the Do not show this

message for this program again option for example.

13.7

Synchronising the PC Clock

With the network service SNTP (simple network time protocol) it is possible to synchronise the internal clock of a PC with the time of the OpenCom 107.

Requirements

You must enter the time zone so that the OpenCom 107 can calculate the time of the internal clock back to the GMT (Greenwich Mean Time) required for SNTP:

1. Go to the Configurator, SYS Configuration: System menu. Click on Change.

2. Under Internet time (SNTP), enter the Time zone for which the time of the

OpenCom 107 applies and whether summer time is allowed for. Confirm this with Assign.

Configuring SNTP

For various operating systems, you can use one of the numerous SNTP programmes offered for downloading on the Internet. Configure the OpenCom 107 as an SNTP server for such programmes.

SNTP with Windows 2000

Here you configure the SNTP server as follows:

1. Log on as the administrator. Start the Command Prompt under Start: Pro-

grams: Accessories.

2. Enter the command line “net time /setsntp:192.168.99.254”. Confirm with the enter key. This command changes the setting for the SNTP server address in the system registry. Close the command line.

123

Configuring the PC Software Address Queries using LDAP

3. Open the Services dialogue under Start: Settings: Control Panel: Administ-

ration. Set the autostart type of the Windows Timer service to Automatic.

Start the service with Process: Start. Every time the service starts, the PC clock is synchronised with the time of the OpenCom 107.

Please note:

In a Windows domain network, the PDC server (primary domain controller) should automatically assume the function of the timer.

SNTP with Windows XP

Here you configure the SNTP server by double-clicking on the time in the Start bar.

Enter the OpenCom 107 as the Server in the Internet time tab.

13.8

Address Queries using LDAP

You can search the data of the central telephone book of the OpenCom 107 from a workstation in the LAN using LDAP (Lightweight Directory Access Protocol). When configuring an LDAP-enabled program, specify the IP address of the

OpenCom 107 as the address of the LDAP server.

LDAP with Outlook Express

You can configure and operate the LDAP directory service with Outlook Express

TM

, a Microsoft

TM

e-mail program, as follows:

1. Call up the Accounts command in the Tools menu.

The Internet Accounts dialogue box will then open.

2. Click on Add. Select the Directory Service command from the pop-up menu.

The Internet Connection Wizard dialogue box for Internet access will then open.

3. Under Internet directory (LDAP) server, enter the address of the

OpenCom 107. It is not necessary to log in to the LDAP server. Click twice on

Next. Then click on Finish.

4. Check the function. In the Edit menu, call up the Find: People command.

The Find: People dialogue box will then open.

124

Configuring the PC Software Address Queries using LDAP

5. In the Look in list, select the entry with the OpenCom 107 address. Enter a user in the Name input field, Administrator for example. Then click on Find now.

The list of entries found should now display the address from the central telephone book.

Note: Only users can be found for whom an internal telephone number has been configured.

125

Configuration Guide

14. Configuration Guide

The Configuration Guide contains a series of flowcharts that will help you to plan the configuration of the OpenCom 107 and guide you through the necessary settings step by step, focusing on the network settings. The individual charts are summarised below:

■

Overview: This chart gives you an overview of the initial configuration of the

OpenCom 107.

■

Configuring PBX Ports: This chart shows you the necessary steps for configuring ports and terminals.

■

Configuring Easy Access: This chart guides you through TCP/IP settings for the OpenCom 107.

■

Configuring ISP Settings: These instructions support you in configuring the

Internet access.

■

Configuring RAS Settings: This chart guides you through the configuration of the RAS settings.

■

Configuring LAN-to-LAN Settings: This chart guides you through the configuration of the LAN-to-LAN settings.

■

Configuring E-Mail: This diagram tells you how to create the requirements needed for configuring the OpenCom 107 e-mail access function.

■

Configuring E-Mail Access: This overview provides instructions on configuring the OpenCom 107 e-mail access server.

126

Configuration Guide

14.1

Overview

Yes

Connect the OpenCom and the configuration PC to the network

Ethernet network

(LAN) exists?

Yes

No

Cross-connected ethernet cable available?

Connect the configuration

PC to the OpenCom LAN port.

Enable DHCP.

No

Connect the configuration

PC to the OpenCom COM port.

Generate the Dialup Networking entry with “occonfig”.

Start the OpenCom configuration service via your Web browser.

Enter the OpenCom address, for example “http://192.168.99.254”.

User Manager

PBX Configuration

Yes

Create the user groups and users.

Set the system data. Select the access type. Connect the S

0

, U pn

and analogue devices and configure them.

Configure the call distribution scheme.

Configure the Least Cost Routing function: zones, network providers and holidays.

LCR Configuration

Configure OpenCom

Least Cost Routing function?

No

Configure OpenCom network functions?

Yes

LAN Configuration

RAS Configuration

No

Save data

Flowchart: Overview

Dial in (RAS)?

No

Connection (LAN)?

No

Internet?

No

E-mail?

No

Yes

Yes

Yes

Yes

Branch Configuration

WAN Configuration

E-Mail Configuration

Finished

Overview

127

Configuration Guide

14.2

PBX Ports

Do you have ISDN terminals that you wish to operate on an S

0

interface?

Define the access type

Set the access type (multiterminal access and/or system access).

Define the external

S

0

interfaces

Set the external S

0

interfaces and enter the telephone numbers assigned by your network provider.

S

0

terminals Yes

Define the internal S

0 interfaces

Set the internal S

0

interfaces and enter the internal telephone numbers.

No

Do you want to operate system telephones or

DECT terminals?

U pn

terminals Yes

Configure the

U pn

interfaces

Enter the U pn

interfaces and enter the internal telephone numbers.

PBX Ports

No No

DECT terminals

Do you want to operate

DECT terminals on the

OpenCom?

Yes

Configure the DECT terminals

Check in the DECT terminals and enter the internal telephone numbers.

Do you want to operate analogue terminals

(e.g. a fax machine)?

Analogue terminals Yes

Configure the a/b interfaces

Set the analogue interfaces and enter the internal telephone numbers.

No

Do you want to use a sensor contact on the

OpenCom (e.g. for a door opener)?

Sensor Yes Configure the sensor

Enter the internal telephone numbers for the time groups of the sensor.

No

Do you want to run the

OpenCount program?

COM Yes

No

Finished

Flowchart: Configuring the PBX Ports

Configure the COM interface

Select the “connection data” option.

128

Configuration Guide

14.3

LAN

Do you have a computer network?

LAN

Yes

Host name

No

Assign a name to the OpenCom.

Finished

Do you have a DHCP server in your network?

Activate the OpenCom

DHCP server.

Enter the Ethernet-IP configuration for the OpenCom.

Enter the address range of the client computers in your network.

Do you have a DNS server in your network?

Specify the IP address of the OpenCom under “Domain Name Server”. This is transferred as the DNS server to the client computers via DHCP.

Enter the address range for the RAS accesses.

PPP addresses

Finished

Flowchart: Configuring Easy Access

DHCP

No

OpenCom

DHCP server

Yes

The OpenCom takes the settings from your DHCP server

Ask your network administrator for the address range for the RAS accesses. For this purpose, your administrator must reserve an IP address range for the RAS accesses.

IP address

Network mask

Gateway address

DHCP adresses

Domain name

Client computers are informed of this gateway address via DHCP as a gateway.

Enter the domain name. This name is transferred to the client computers as the domain via DHCP.

DNS

No

OpenCom as

DNS server

Yes

Specify the IP address of your internal DNS server under “Domain Name

Server”. This is transferred as the DNS server to the client computers via DHCP.

Register internal DNS

LAN

129

Configuration Guide

14.4

WAN Settings

Do you want to configure a new Internet provider?

Enter your provider's dial-in data.

“SYS Configuration: System:

Country” = “German”?

No

Your own ISP

Yes

T-Online

Provider-New: Provider,

Telephone Number,

User Name and Password

No

Yes

T-Online: Telephone number,

Access identification, T-Online number, Co-user number and Password

Select a provider from the list

Select one of the default providers in

“NET Configuration:

WAN”.

Specify the IP address of the DNS in the Internet.

Specify a standard POP server and a standard SMTP server.

Specify the maximum time of inactivity after which the connection to the ISP is cleared down.

Domain Name Server

Mail input server and mail output server

Maximum idle time

Configure T-Online in “NET Configuration: WAN: Provider”. You will obtain the access data when you register.

Activate the status and select the provider

Configure the ISP in “NET Configu-ration:

WAN: Provider”.

DSL

(PPPoE)

No

Yes

Is your IP address allocated by your provider?

PPP

Yes

Dynamic

Yes

Enter the IP address and network mask you wish to obtain from your provider.

Your own telephone number

Max. connection time per month

Specify the maximum connection time for one month.

No

No

HDLC

Yes

No LAN

Yes

IP address

Network mask

Specify the gateway for the Internet connection.

Gateway

No

Maximum idle time

Filter list IN

Filter list OUT

Specify the maximum time of inactivity after which the connection to the ISP is cleared down.

Select the filter lists. Filter lists are created in “NET Configuration: Firewall”.

Finished

Flowchart: Configuring the ISP Settings

ISP cannot be configured.

WAN Settings

130

Configuration Guide

14.5

RAS Settings

Have you made the network settings for the OpenCom ?

LAN No

NET Configuration:

LAN

Configure the network settings for the OpenCom.

Configure the RAS access of the

OpenCom. “NET Configuration: RAS”

Yes

RAS Settings

Select from PAP,

CHAP and CLID.

Status

Telephone number

Activate the RAS access.

Specify the telephone number for which the RAS access should be configured.

Authorisation

Number of connections

Specify how many simultaneous connections are possible via this access.

Select the filter lists. Filter lists are created in “NET

Configuration: Firewall”

Filter list IN

Filter list OUT

Have you created users with RAS access rights?

Users

Yes

No

User Manager: Users and User Groups

Configure users that have RAS access rights.

Add internal telephone number to the incoming call distribution scheme.

Finished

Flowchart: Configuring the RAS Settings

131

Configuration Guide

14.6

Branch Settings

Have you made the network settings for the OpenCom?

LAN No

NET Configuration:

LAN

Configure the networksettings for the OpenCom.

Yes

Configure the LAN-LAN connection.

“NET Configuration: Branch”

Protocol

Telephone number local

IP address local

Network mask local

Select between PPP and HDLC transparent.

Enter the internal telephone number.

Enter the local IP address.

Enter the local network mask.

Yes CLID

No

User name local

Password local

Authorisation method of the local

LAN: CLID, PAP or CHAP?

Specify the user name with which the remote LAN can access a destination.

Specify the password with which the remote LAN can access a destination.

Telephone number remote

IP address remote

Network mask remote

Specify the telephone number of the remote LAN access.

Specify the IP address of the remote LAN.

Specify the network mask of the remote LAN.

Yes CLID

Authorisation method of the remote

LAN: CLID, PAP or CHAP?

No

User name remote

Password remote

Direction of connection

Maximum connection time per month

Maximum idle time

Add internal telephone number to the incoming call distribution scheme.

Specify the user name with which the remote LAN can be accessed.

Specify the password with which the remote LAN can be accessed.

Select the direction of the connection.

Specify the maximum number of minutes per month the connection to the remote LAN can be set up for.

Set the maximum idle time after which a connection to the remote LAN is cleared down.

Finished

Flowchart: Configuring the LAN-to-LAN Settings

Branch Settings

132

Configuration Guide

14.7

E-mail Function

Have you made the network settings for the OpenCom?

LAN No

Configure the network settings for the OpenCom.

NET Configuration:

LAN

Yes

E-mail Function

Do you want to use e-mail from the Internet?

Internet

No

Yes

Configure your Internet access.

NET Configuration:

WAN

Has an internal e-mail server been configured in your LAN?

LAN No

No e-mail use

Have you stored the users to be notified?

Yes

Do you want to be notified of e-mails on your system telephones?

Notification

Yes

Users

No

No

Create the users and activate e-mail notification. Also enter the users' e-mail addresses.

User Manager:

Users, User Groups and User Accounts

Yes

Finished

Set the polling time periods.

NET Configuration:

E-Mail Access

Finished

Flowchart: Configuring the E-mail Function

133

Configuration Guide

14.8

E-mail Access

Do you have access to a mail server in your network or in the Internet?

Mail server No

Configure your network/

Internet access.

NET Configuration: LAN or WAN

Yes

E-mail Access

Do you have created mail account polls in the “User Manager: User accounts”?

User accounts No

Set up user accounts in the User Manager.

User Manager: User Accounts

Yes

Configuration of e-mail access settings

Specify the time intervals in which the

OpenCom is to poll all mail accounts from the standard POP server.

Maximum number of e-mails per user account

Enquiry interval

Start and end times:

Monday to Friday 1st starting time

Monday to Friday 1st ending time

Monday to Friday 2nd starting time

Monday to Friday 2nd ending time

Saturday 1st starting time

Saturday 1st ending time

Saturday 2nd starting time

Saturday 2nd ending time

Sunday 1st starting time

Sunday 1st ending time

Sunday 2nd starting time

Sunday 2nd ending time

Specify the maximum no. of e-mails per user account that should be temporarily stored by the OpenCom.

Define the time windows in which the

OpenCom should check the mail accounts for new messages in the time intervals that have been set. You can define two time windows for each working day (Monday to Friday), and two each for Saturday and Sunday.

Finished

Flowchart: Configuring E-mail Access

134

Frequently Asked Questions General/Hardware

15. Frequently Asked Questions

This chapter provides tips and information on how to deal with any malfunctions or faults you may experience with the OpenCom 107.

Please note:

Repairs to the OpenCom 107 should only be carried out by qualified personnel.

The following LEDs indicate that the OpenCom 107 is ready for operation:

Power Good LED

Activity LED

LAN LEDs

Interface module

AC adapter

Position of LEDs on the OpenCom 107

15.1

General/Hardware

The OpenCom 107 is not functioning.

Make sure the mains plug is properly connected.

Plug another device into the mains socket to check whether there is any voltage.

The mains plug is connected, the mains socket is supplying output, but the

OpenCom 107 still does not function.

DANGER!

This device contains hazardous voltages. To make the system dead, remove the power plug from the socket.

Take the housing cover off. Is the “Power Fine” LED at the top left illuminated?

135

Frequently Asked Questions Telephony

If not, contact your service centre or an authorised dealer. The AC adapter plug of the OpenCom 107 may be defective.

After restarting the OpenCom 107, nothing is indicated on the displays of any connected terminals.

It takes a short while for the OpenCom 107 to start up.

After the restart, check whether the activity LED flashes at a rate of 10s / 1s. This flash cycle indicates that the OpenCom 107 has started up correctly and is ready for operation.

If the OpenCom 107 has not restarted properly, reset the OpenCom 107 to its

original factory setting (refer to the chapter entitled Resetting the System Data starting on page 51).

15.2

Telephony

It is not possible to make external calls.

Check the connection between the NTBA and the OpenCom 107.

In the Configurator, check whether the external S

0

ports are configured correctly

(PBX Configuration: S

0

menu):

– Configuration of System- / Multi-terminal access OK?

– Port is connected to the NTBA?

– Faultless Cabling?

– Terminating resistors properly configured?

The OpenCom 107 is connected to an NTBA with a multi-terminal configuration. Why is it not possible to establish external connections?

With the original factory setting, an additional external S

0

port is set for an NTBA in the system configuration; this additional port will be used first to seize a trunk line.

Deactivate the second S

0

port in the Configurator (PBX Configuration: S

0

menu).

136

Frequently Asked Questions Telephony

One of the telephones is not functioning at all.

Make sure the telephone has been properly connected.

Check also whether the appropriate port has been configured correctly in the

Configurator (PBX Configuration: Ports menu).

It is not possible to make external calls with one of the telephones.

Check whether a user is configured for the telephone. Otherwise the settings of the Guests user group are valid for the telephone. To standard, this user group has no external call authorisation.

Make sure the user configured for this telephone belongs to a user group with external line access (Configurator, User Manager: User groups menu).

Check also whether the internal call number of this telephone has been configured for incoming call distribution (Configurator, PBX Configuration: Call Dis-

tribution menu).

One of the features (e.g. call diversion) on one of the telephones cannot be used even though the feature has been configured in the Configurator of the

OpenCom 107.

Make sure the user configured for this telephone belongs to a user group that has access to this feature (Configurator, User Manager: User and User groups menus). Some features cannot be used until the system PIN is changed.

Nothing is indicated on the display of one of the connected ISDN telephones.

You have connected the ISDN telephone to an external S

0

port (RJ-45 socket).

These ports are intended for connection to the NTBA only. Connect the telephone to an internal S

0 port (pressure terminal).

Calls can be made but not received with one of the ISDN telephones.

The internal call number that has been configured for this ISDN telephone in the

Configurator (PBX Configuration: Ports: S0 menu) must also be configured as an MSN on the ISDN telephone itself. For further information, refer to the User

Guide of your ISDN telephone.

An ISDN telephone always rings, if another telephone on the S

0

bus is being called.

This case also requires configuring the MSN on the ISDN telephone (see above answer).

137

Frequently Asked Questions DECT

It is not possible to configure Call Distribution: Outgoing for multi-terminal access.

You have configured multi-terminal access and system access in parallel. All outgoing calls are therefore established via system access, and outgoing call distribution can be configured for system access only (Configurator, Call Distribution menu).

A specific MSN can be seized for individual calls by means of a code number procedure. For further information, refer to the “OpenCom 100, Operation on

Standard Terminals”user guide.

What are some of the causes for problems when sending and/or receiving faxes?

In frequent cases, the reason may be found in a problem with the ISDN-L1 reference clock distribution. The L1 clock is delivered from the network provider. An unclean L1 clock distribution and the introduced signalling jitter is overheard by the human ear. Nevertheless, data and fax transmissions may be disturbed by the jitter. Please check, which ISDN lines will deliver the L1 clock. Details can be found

under L1 Clock starting on page 85.

The fax data transfer possibly is routed via a compressing VoIP connection. Please verify, if the a/b port is configured with the “Fax” setting. For the VoIP connection, select a VoIP profile which includes the non-compressing G.711 codec.

15.3

DECT

The LED of the RFP 22/24 base station is flashing, but none of the DECT devices is functioning.

Make sure the terminal setting for the corresponding U pn

port is set to RFP 22/24

(Configurator, PBX Configuration: Ports: U

pn

menu).

If multiple RFP 22/24 base stations are installed, the blinking LED indicates that synchronisation is not finished.

The LED of the RFP 22/24 is continuously lit up, but one of the cordless DECT devices is indicating “No connection”.

You have not registered this DECT device. Configure a port in the Configurator and start the enrolment procedure (PBX Configuration: Devices: DECT Phones menu).

138

Frequently Asked Questions LAN

Is it possible to increase the time for the enrolment procedure?

You must manually enter the IPEI of the DECT device in the Configurator. The enrolment time is then increased to one hour (PBX Configuration: Devices: DECT

Phones menu).

Another manufacturer’s DECT device is not functioning.

Check whether the DECT device supports the DECT GAP standard. In the Configu-

rator, also make sure GAP is set for this DECT device (PBX Configuration:

Devices: DECT Phones menu).

The startup procedure of the RFP 22/24 take a long time? What is the reason?

This behaviour may indicate a problem with the reference clock. Refer also to What

are some of the causes for problems when sending and/or receiving faxes? starting on page 138.

15.4

LAN

Why is it not possible to establish a network connection with the

OpenCom 107?

Check whether the LEDs for the switch and the PC’s network card are indicating a connection.

Check the LEDs for the LAN functions of the OpenCom 107. The upper green LAN

LED indicates whether the network cable has been properly connected. The lower red LAN LED indicates whether there is any network traffic on the line.

To check whether there is a network connection with your OpenCom 107, enter the “ping IP address” command in “Run” in the Windows Start menu (e.g. ping

192.168.99.254).

How can I determine the IP address of the OpenCom 107?

To find out what the IP address is, enter the code number *182 on one of the connected system telephones.

The code-number procedure *183 also displays the network mask.

The network connection is functioning, but nothing is displayed in the browser.

Enter the complete IP address of the OpenCom 107 along with the protocol identifier, for example http://192.168.99.254/.

139

Frequently Asked Questions Internet

Check whether the browser has been configured for connection through a proxy server. If so, deactivate the “Connect through proxy server” setting.

You have just configured the OpenCom 107 via the network. Why is it not possible now to establish a remote data transfer network connection?

The network card and the communication (remote data transfer) adapter cannot be run with the same routing setting. Deactivate the network card before connecting via the dial-up network.

Our network has grown over time, with several segments connected by one central router. How can PCs from all segments connect to the OpenCom 107?

If several routers are configured for your network in different segments, you can enter extra static routes in the NET Configuration: LAN: Routes menu.

In our network the OpenCom 107 dynamically issues the IP addresses by

DHCP. Can I firmly assign the IP address for our internal server PCs (mail,

Web)?

You need a static address assignment for these PCs. Make the appropriate host assignment entries in the Configurator (NET Configuration: LAN: Hosts menu).

Create a static DHCP entry for each host assignment in the NET Configuration:

LAN: DHCP Server menu. Activate “Dynamic and static address” for the DHCP server.

15.5

Internet

I cannot access our company Web site.

Outside your system, your company Web site is accessed at “www.firm.com”, but in the Configurator you have entered “firm.com” as the domain. Your company’s site URL thus counts as an internal URL and can only be accessed by entering the direct IP address. If required, change the domain setting in the NET Configu-

ration: LAN menu.

Why do some Internet services not work even though they can be used when dialling in directly via a modem?

Some Internet services require an active connection coming from the Internet. But the configured filter rules prevent this. Plus, it is not possible to establish incoming

Internet connections with the PCs directly owing to the network address translation process.

140

Frequently Asked Questions Internet

It is possible to redirect incoming connections in the Configurator, menu NET

Configuration: Port Forwarding. You should secure the redirection target (PC or server) with a suitable firewall software.

It is not possible to access the Internet with the OpenPhone 27.

The requirement for this is that the set should be configured as Handset+data.

The telephone number used by the OpenPhone 27 to establish an Internet connection must also be specified in the respective user profile (Configurator, User

Manager: User menu).

With the OpenPhone 27, the Internet can be accessed either directly via the remote data transfer network or indirectly via RAS access on the OpenCom 107.

For direct access you can directly dial any provider. Indirect access uses the routing function of the OpenCom 107, accompanied by the configured security features, for example.

Directly via remote data transfer network

If the Internet is accessed directly via the remote data transfer network, make sure that

■ the remote data transfer network is properly installed on your PC and that the correct ISP access data is configured,

■ the internal number used by the OpenPhone 27 to establish the data connection is configured for outgoing call distribution (Configurator, PBX Confi-

guration: Call Distribution: Outgoing menu).

Indirectly via RAS access

If the Internet is accessed indirectly via RAS, the system administrator should make sure that:

■ permission has been given for Internet access via RAS (Configurator, Net Con-

figuration: Firewall menu),

■ an internal number is configured for RAS access (Configurator, Net Configu-

ration: Connections: RAS menu),

■ your user group has been granted RAS access rights (Configurator, User

Manager: User Groups menu).

For information on the installation of software and on configuring Internet access, refer to the “OpenPhone 26/27” user guide.

141

Frequently Asked Questions Internet

Is it possible to use Q.SIG-IP connections via an Internet access with dynamic

IP address?

Q.SIG-IP connections require a fixed IP assignment for technical and security reasons. Therefore you need an Internet access with a fixed IP address. It is possible to tunnel a Q.SIG-IP connection through a VPN connection. A VPN connection offers the possibility to determine the peer’s IP address with a DynDNS service during connection setup. VPN and DynDNS can be realized with external servers or routers.

142

Technical Specifications

16. Technical Specifications

Mains power supply

Rated power

Safety class

Euro ISDN external for basic access,

DSS1 protocol

Euro ISDN internal for ISDN terminals,

DSS1 protocol

– Supply voltage

– Supply power

– Range

Euro ISDN switchable for basic access,

DSS1 protocol or for ISDN terminals,

DSS1 protocol

– Supply voltage

– Supply power

– Range

U pn

for system terminals and DECT base stations

– Supply voltage

– Supply power

– Range a/b for analogue terminals with pulse or DTMF dialling, flash duration of

60 to 310 ms

– Supply voltage

– Supply power

– Range

230 V ~ 50 Hz

80 VA

2

1x

1x

40 V ± 10%

3 W

150 m

2x

40 V ± 10%

3 W for internal

150 m internal

4x

40 V ± 10%

3 W per U pn

bus

1000 m

4x

40 V ± 10%

25 mA

1,000 m

143

Technical Specifications

V.24 port (COM)

– Range

Permissible temperatures stationary, weatherproofed

Dimensions (W x H x D)

Weight (only system)

Contact load actor

– Voltage range for connection of a PC

5 m

+5°C to +40°C

396 x 390 x 100 mm about 2.8 kg

2 A / 125 V

U

≈

= 5 V … 30 V

Note: The online help provides an overview of the limits that should be observed when configuring the

OpenCom 107.

144

Notes on disposal

17. Notes on disposal

In order to avoid any possible effects resulting from the disposal of electrical and electronic equipment containing substances damaging to the environment and human health, the European Parliament and Council directives

■

2002/96/EC on waste electrical and electronic equipment (WEEE) and

■

2002/95/EC on the restriction of the use of certain hazardous substances in electrical and electronic equipment (RoHS) have been transferred into national law in all EU member states.

The primary aim of the legislation is the prevention of waste electrical and electronic equipment, and also the recycling, material recovery and any other form of recovery of such waste in order to reduce the quantities of waste to be disposed of and the amount of hazardous substances from electrical and electronic equipment in waste.

The product that you have purchased was developed in line with the current state of the art in an environmentally friendly manner and with a view to recycling. It therefore meets the specifications of the European directives.

The product is labelled with the symbol illustrated above. If you wish to dispose of this product, this symbol obliges you to do so separately from unsorted domestic waste. Suitable facilities have been set up for the return of waste electrical and electronic equipment. Waste equipment can be handed in at these return centres free of charge. To find out where these return centres are located, please consult the information provided by the department of your local authority responsible for waste disposal.

Please note:

Electrical equipment does not belong in household waste.

Deposit it free of charge at a return centre.

145

Index

Index

A

a/b adapter 29

Accessories 31

Actor

See Intercom system 28

Adapter

Audio 30

Cable (RJ-232 - RJ-45) 17

Upn 29

Add-on 32

Analogue a/b ports 23

Authorisations 12

B

Basic setting 51

Basic setting switch 24

Bundles 88

Busy key 94

C

Call keys 93

CAPI 119

Clock 123

Power failure 24

Synchronising the PC (via

SNTP) 123

Configuration 40

Initial configuration 40

Loading software updates 50

Preconfiguration 46

Remote configuration 47

Resetting the system data 51

Saving and loading the configuration 49

146

System prerequisites 41

via V.24 port 8

Configuration examples 54

Introduction to TCP/IP 55

OpenCom 100 in a LAN with an IPenabled server 59

OpenCom 100 in a serverless

LAN 56

RAS 58

Configuration guide

Branch settings 132

E-mail access 134

E-mail function 133

LAN 129

Overview 127

PBX ports 128

RAS settings 131

WAN settings 130

Configuring

Preparation 43

Starting the Web console 44

Connection scheme

Analogue (a/b) ports 26

S0 ports 25

Upn ports 26

D

DECT 9, 10, 138

DHCP 55

Direct call key 95

DNS 57, 59

DSL 23

DSL port 23

DSS1 84

DTMF 72

Index

E

E-mail 10

F

Factory settings 12

Authorisations 12

Basic settings switch 24

Internet functions 15

Telephony functions 12

FAQs 135

Fax 72

Features 7

Internet access 9

H

Hardware 135

Hardware basic setting switch 51

Headset 39

I

Installation 17

Basic setting switch 24

Mounting location 19

Ports 20

Scope of delivery 17

Wall mounting 19

Intercom system 27

Internet access 63

Costs 63

E-mail 64

NAT 64

Web 63

K

Keypad extensions 37

L

LAN port 23

LCR 89

LDAP 124

Log-in procedure 121

M

Multi-terminal access 7, 83

Music on Hold 27

External devices 27

Generating own files 52

N

NET CAPI 119

NTBA 136

NTBBA 23

Numbering 90

O

Online help 45

OpenCTI 121

OpenHotel 121

Outlook Express 124

P

PBX networking 83

PBX number 91

PC status display 120

Pin assignment

Audio adapter 30

147

Index

ISDN socket 22

Plug-in power supply 21

Point-to-point connections 86

Port assignment

Analogue a/b ports 23

DSL port 23

LAN 23

S0 port pin assignment 23

S0 ports 21

S0 terminating resistor 21

Upn ports 22

Ports

Actor 20

Analogue a/b 20

LAN 20, 28

V.24 21, 28

Ports (see Interfaces) 21

Power failure 24

Q

Q.SIG 84

R

Remote configuration 47

Resetting system data 51

Routes 89

S

S0 port 137

S0 port pin assignment 23

S0 ports 21

Safety

Power failure 24

Safety precautions 17

Saving and loading the configuration 49

148

Sensor

See Intercom system 28

SNTP 123

Software updates, loading 50

System access 7, 83

System data, resetting 51

Systray display 120

T

TAPI 117

Team Functions 93

Team functions

Explanation of keys 93

Introduction 93

Team key 94

Telephony 136

Terminating resistor 21

Three-member team 98

Time zone 123

Toggle team 100

Troubleshooting 135

Trunk key 94

U

Unified team 99

Upn port pin assignment 23

Upn ports 22

V

Voice mail 27

Configuration Example

OpenCom 107

OpenPhone 63

Upn

Analogue fax

a/b

S0

Upn

RFP 21

Upn

RFP 21

ISDN telephone

OpenPhone 26

Configuration example: OpenCom 107 with connected terminals

DeTeWe Systems GmbH

• Zeughofstraße 1 • D-10997 Berlin • www.Aastra-DeTeWe.de

As of October 2006

Subject to changes