Aastra OpenCom 510 User Manual

PDF

Dokument

Annonce

OpenCom 510

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 510 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 130, OpenCom 131, OpenCom 150, OpenCom 510 and OpenCom X320 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.

We hope you enjoy using OpenCom 510.

Contents

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Factory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Telephony Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Authorisations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Internet Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Preliminary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Construction of the OpenCom 510 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Scope of Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Declarations of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

General Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Notes on the Mains Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Notes on EMC and Earthing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Notes on Installing the OpenCom 510 . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Notes on Installing Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Installation, Ambient Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Installation in a 19" Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Installing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Notes on Disconnecting the Mains Supply. . . . . . . . . . . . . . . . . . . . . . . .28

Installing the Central Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Installing Interface Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Installing a Power Supply Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Uninterruptible Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Interfaces and Connectible Terminals . . . . . . . . . . . . . . . . . . . . . . 40

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

External ISDN Ports (S

External) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Internal S

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

U pn

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Terminals Connected to U

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Technical Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

DECT Base Station Connection Variants. . . . . . . . . . . . . . . . . . . . . . . . . . .46

a/b Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Terminals Connected to a/b Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Technical Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

LAN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

DSL Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Service PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

COM Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

OpenPhone 71/73/75: Extensions and accessories for system telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Power supply unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Keypad extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Module Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Overview of Available Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

MPS+1-AC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

MC+1-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

MT+S2M1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

MX+S01-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

MS+UPN1-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

MS+UPN2-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

MS+A1-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

MS+A1-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Brief Guide to Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Configuring the OpenCom 510. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Preparing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Starting the Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Loading the Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Finishing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Preconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Offline Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Remote Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Codes for IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Saving and Loading the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .91

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

Loading SW Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Resetting the System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Generating Your Own MoH Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

OpenCom 510 in Computer Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Introduction to TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

OpenCom 510 in a Serverless LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

DNS Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

RAS Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

OpenCom 510 in a LAN with an IP-enabled Server . . . . . . . . . . . . . . . .98

DNS Name Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

RAS Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Branch Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Useful Information on Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Using the Web. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

10.

11.

Voice over IP (VoIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Quick start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

IP System Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

External SIP Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Internal SIP telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Propagation Delay and Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Latency and Packet Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Voice Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Optimisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Call set-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Useful services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Media Gateway (MGW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

MG+ETH1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

SIP Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

External SIP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Internal SIP subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

VoIP System Telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Device Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

VoIP System Telephone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 124

LAN DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Start Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Local Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

OpenPhone IPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

DECToverIP

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

DECT base stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Dual operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Setting up the WLAN function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Configuring for a remote location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

14.

15.

13.

12.

PBX Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Variants of PBX Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Functionality of PBX Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Putting a Cascaded PBX into Operation. . . . . . . . . . . . . . . . . . . . . . . . . 145

Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Licensing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

PBX Networking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Protocol: Q.SIG or DSS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Master/Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

L1 Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Types of Point-to-Point Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Connection via an Active Transmission System . . . . . . . . . . . . . . . . . 153

Connection via the Public Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Connection via Q.SIG.IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Trunk groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Numbering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Technical Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Team Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Explanation of Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Team Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Examples of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Executive/Secretary Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Three-member Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Unified Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Toggle Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Call Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Activation of Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Call Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

17.

18.

16.

Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Examples of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

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

Group of Three Enquiry Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Configuring the Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . . . 176

Activating the Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Configuring and Managing Companies. . . . . . . . . . . . . . . . . . . . . . . . . 177

Assigning Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Assigning Trunk Groups/SIP Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Allocating Routing Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Configuring the Company Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

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

Company Telephone Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Making Calls Between Companies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Billing Charges per Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Configuring the PC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

PC Offline Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Setting up TAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Setting up NET CAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Using the Systray Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Browser for OpenCTI and OpenHotel . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Setting up Video Telephony. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Synchronising the PC Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Address Queries using LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

PBX Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

LAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

WAN Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

19.

20.

21.

RAS Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Branch Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

E-mail Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

E-mail Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

General/Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

DECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Notes on disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Features

1. Features

The OpenCom 510 is a communications system for integrated voice and data communication. The most significant feature of this communications system is its modular structure. The OpenCom 510 is designed for installation in a 19" frame.

The frame itself can be installed in a 19" wall-mounted enclosure or in a 19" floorstanding cabinet.

The system provides a number of slots for the installation of modules. In a fully configured system, the following modules will have been installed (and all slots will be occupied): 2 power supply units,

1 control module, 12 interface cards. By combining different interface cards, it is possible to create configurations suited to the user’s specific communications requirements. If, for example, a user requests DECT-capable U pn

interfaces or additional S

or a/b interfaces, one or more interface cards can be integrated without having to exchange the entire system.

Moreover, OpenCom 510 systems can be cascaded, which allows you to integrate a higher number of modules, or networked in order to meet growing communications requirements.

The OpenCom 510 can be integrated into system environments with structured cabling. All connections to a structured cabling patch panel can be made with standard patch cables.

The OpenCom 510 supports the following communications applications:

■ Telephony with system telephones, ISDN telephones and analogue terminals,

Internet/intranet data communication, CTI applications, sub-system operation and system configuration using a standard web browser

■ Additional software packages for expanded telephony functions can be operated and for making telephone functions more comfortable, e.g. the digital voicebox and voice portal systems OpenVoice and OpenAttendant.

■ The “DoorLine” intercom system can be operated.

Telephony

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

ISDN basic access interface using the DSS1 protocol. Both multi-terminal access

(point-to-multipoint) and system access (point-to-point) configurations are sup-

Features ported. The system can be configured to run both types of access in parallel. S

0 and S

interface cards are available for connecting the system to the telecommunications network. An S

interface card provides eight S

ports (switchable to either internal or external connections). The S

interface card provides one ISDN

interface for connecting the OpenCom 510 either to a primary multiplex interface or to a second PBX (ISDN point-to-point connection). For an overview of

interface cards, refer to Modules starting on page 59.

The OpenCom 510 firmware is designed for a maximum of 600 users. For information on system limitations, refer to

Technical Data starting on page 209.

The following can be connected to the OpenCom 510:

■ Euro ISDN terminals

■ System telephones OpenPhone 71, OpenPhone 73, OpenPhone 75

■ System telephones OpenPhone 61, OpenPhone 63, OpenPhone 65

■ RFP 22 base stations

■ DECT handsets (with RFP 22 connected to DECT-capable U pn

port of

MS+UPN2-8 interface card)

■ analogue terminals

interfaces must be operated with Euro ISDN terminals in accordance with the

DSS1 protocol.

U pn

ports are suitable for connecting the OpenPhone range of system telephones.

Furthermore, the DECT-capable U pn

ports of the MS+UPN2-8 interface card can be used to connect RFP 22 base stations.

Analogue ports are suitable for connecting standard analogue terminals.

If your network provider supports the CNIP (Calling Name Identification Presentation) feature, the names of callers will be displayed in addition to the numbers whenever external calls are received. The OpenCom 510 supports the display of the name on system telephones. However, if you have created an entry in the telephone book under the number of the caller, this entry will be displayed instead.

Features

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

The OpenCom 510 can be configured and programmed by means of a web browser (web console). This browser needs to be installed on a PC which is connected to the system.

The OpenCom 510 can be pre-configured at the service centre and remote-configured for service purposes.

A COM port can be used to connect a PC for the purpose of transferring connection data.

You can use the “DoorLine” intercom system to connect the OpenCom 510 to a building’s wiring system, which enables you to use door opener and doorbell functions through the OpenCom 510.

The OpenCom 510 enables you to use third-party CTI (Computer Telephony Integration) applications. This requires the installation of a TAPI driver (provided on the system CD) on a Windows PC. The OpenCom 510 also features the integrated browser-based CTI application OpenCTI 50. Via the OpenCTI 50 users can call up and use telephone functions through their PCs without having to install a special

TAPI driver.

Further Telephony Features

The OpenCom 510 can be used to run digital voicebox and voice portal systems.

The configuration data and the recorded speech files (messages for, or left by, a caller) are stored on the OpenCom 510 CompactFlash card, which is installed on the MC+1-3 central control module.

For further information, refer to the “OpenVoice” and “OpenAttendant” user guides.

You can optimise telephone communication with the help of team functions and the call-queuing function.

The “OpenCount” application, which requires a separate licence, can be used to record and save connection data; these data can be analysed using a number of individually configurable filter criteria. For further information, refer to the web console online help.

Features

You can connect two OpenCom 510 systems (PBX cascading). Cascading is a simple way of increasing the number of terminals that can be connected.

As your communication requirements grow, the OpenCom 510 can be networked with other telecommunications systems. The OpenCom 510 can then operate as a sub-system or as a DECT server. It is also possible to create a telecommunications system with several networked PBXs.

Internet Access

For the purpose of providing Internet access, PCs can be connected to the

OpenCom 510 by means of the internal S

ports, and an entire LAN can be connected by means of the Ethernet port. If Internet access is already available from an Internet service provider, the OpenCom 510 can be configured accordingly. The

OpenCom 510 can also be used for IP configuration if there is no IP-capable client network. An integrated DHCP server and a DNS server will take over IP address administration and name resolution for the client PCs.

The OpenCom 510 enables all connected PCs to access the Internet using a common IP address; only the common address will be visible outside the LAN.

Network address translation (NAT) is used to change the IP addresses of the local

(client) PCs into the IP address of the OpenCom 510. This prevents direct access to the LAN’s client PCs and thus offers protection against attacks from the Internet.

The OpenCom 510 offers further protection of the LAN in the form of customisable filter lists (firewall function).

Note: Also observe the notes in

Useful Information on Internet Access starting on page 102.

DECT Data Communication

PCs that are not connected to the OpenCom 510 via the internal S

ports or the

Ethernet interface can access the Internet if used in combination with the

OpenPhone 27 DECT terminals. PCs in these configurations can also make full use of the Internet and e-mail features of the OpenCom 510.

Data will then be transmitted via the internal data interface of the OpenPhone 27.

The OpenPhone 27 must be connected to the serial port of the PC. The Internet can be accessed directly via the remote data transfer (i.e. dial-up) network. The

OpenPhone 27 will establish a data connection with the OpenCom 510 via the

DECT air interface. The Internet connection itself will be established either directly through an ISDN B-channel or indirectly through the internal RAS interface of the

OpenCom 510. Indirect RAS access is preferable as it uses the routing function of

Features the OpenCom 510 and thus benefits from the security features of shared Internet access.

For detailed information on installing the required driver software and on the various configuration options, refer to the “OpenPhone 27” user guide. For information on configuring the OpenPhone 27 data interface, please refer to the

OpenCom 510 online help.

E-Mail

The OpenCom 510 offers an integrated e-mail function that supports the POP3,

APOP or IMAP4 protocols used to query an Internet service provider for incoming mail. The OpenCom 510 can be configured to enable every member of staff to query mail accounts. The OpenCom 510 fetches the incoming e-mail headers (subjects) and senders from the mail server at set intervals and forwards them to the user’s 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 510 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.

Voice over IP (VoIP)

The OpenCom 510 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 105).

DECToverIP

DECT networking via VoIP is another possible option for offices already extensively using VoIP telephony. The Radio Fixed Parts (RFPs) are connected via network data connections, so they do not occupy any U pn ports and can use existing network connections. With DECToverIP, VoIP protocol data is changed into DECT-compatible voice data direct on the RFPs. DECT-RFPs and DECToverIP-RFP can be used

Features together in combination in many cases; it is however not possible to switch between RFPs using different technologies during a call.

Further Network Features

You can enable staff to dial into the LAN by means of RAS access.

In addition, you can configure a LAN-to-LAN link via ISDN. Two OpenCom 510 systems can thus connect their LANs for on-demand dial-in (from both sides).

A NET CAPI (driver software provided on the system CD-ROM) enables PCs without

ISDN cards to use ISDN functions.

Factory Settings Telephony Functions

2. Factory Settings

The OpenCom 510 is delivered with the following basic settings and activated features. We recommend that you configure the OpenCom 510 to meet your specific

requirements before putting it into operation (see Configuration starting on page 82).

Tip: Notes on the functions listed below can be found in the glossary (provided as a PDF file on the system CD).

2.1

Telephony Functions

■ The OpenCom 510 is pre-configured for use in Germany.

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

■ Incoming external calls are signalled at all corded terminals connected to the system.

■ The system PIN, which is used for remote-programmable call forwarding, for example, is “0000”.

2.2

Authorisations

Authorisations determine which functions can be used at the terminals connected to the OpenCom 510. Authorisations are configured for so-called user groups; users and their terminals are allocated to these groups.

Three user groups are preset: “Administrators”, “Standard” and “Guests”. “Administrators” have access to all functions of the OpenCom 510 and unrestricted configuration rights. Users in the “Guests” group cannot configure the OpenCom 510, are not able to make external calls, and have only restricted use of the terminal functions of the OpenCom 510. 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 510 is first put into operation, all connected terminals are in the “Administrators” group until a

Factory Settings Authorisations user logs on to the web console. All terminals are then automatically allocated to the “Guests” group. For further information on configuring user groups and users, refer to the online help chapter “User Manager”.

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

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

■ Least cost routing (LCR) is not active. As soon as LCR is configured, users can make calls using selected call-by-call providers.

■ VIP call is activated.

■ Announcements to system terminals 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.

■ “Pickup” and “Pickup selective” of calls from other telephones are activated.

Pickup protection is deactivated.

■ “Call removal” is deactivated.

■ “Callback on busy” can be activated.

■ If a user has configured more than one terminal under the same number, they can suppress the signalling of calls at the parallel terminals.

■ 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.

■ Function “Call queue” 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

Factory Settings Authorisations can be forwarded. Call forwarding for other users and call forwarding by other users are deactivated.

■ External calls can be transferred to an external subscriber.

■ Three-party conferences can be set up.

■ 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 blacklist, the whitelist and a call filter are not pre-configured 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 door opener can be operated from all terminals. Door calls can be forwarded.

■ Connection data analysis 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.

■ Speed dialling is possible, provided it has been configured in the

OpenCom 510 central telephone book.

■ Keypad dialling is possible.

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

Factory Settings Internet Functions

■ Call forwarding for SMS calls in the fixed-lines network is not activated.

■ Call charges can be recorded, associated with booking numbers and analysed.

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

■ Every user can change the configuration of the OpenCom 510.

■ 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 licence (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 configured for every

OpenCom 510 user, provided that RAS access is authorised.

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

■ Every user with a system terminal can be automatically notified of the receipt of e-mail.

■ Users can terminate Internet connections (through the OpenCom 510 web console or from a system terminal that has been configured accordingly).

The following IP addresses are preset for network configuration:

■ Host name: host

Factory Settings Internet Functions

■ IP address: 192.168.99.254

■ Network mask: 255.255.255.0

The following addresses are transmitted to the LAN’s client PCs using 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 . Consult the LAN’s network administrator if you wish to do so.

Preliminary Information Construction of the OpenCom 510

3. Preliminary Information

3.1

Construction of the OpenCom 510

The OpenCom 510 is designed to be used in 19" rack systems. It comprises the following:

■ A 19" mounting frame for the modules. In a fully configured system, the following modules will have been installed (and all slots will be occupied):

2 power supply units, 1 control module, 12 interface cards. The interface cards provide the system ports. The 19" frame of the OpenCom 510 is also referred to as the 1-12 frame (signifying the number of slots for interface cards).

■ A backplane. The backplane provides the sockets for the control module and the interface cards; it supplies the modules/cards with the required power and system signals.

The OpenCom 510 comes fully assembled. By contrast with other systems, you will not need to assemble the frame and backplane yourself.

A power supply unit and the central control module are built into the frame before delivery. Interface cards ordered by the customer must be installed separately.

Please note: Interface cards may be installed by qualified personnel only!

For further information on installing modules/cards, please refer to

Installation in a

19" Rack starting on page 26 and

Installing Modules starting on page 27.

3.2

Scope of Delivery

The OpenCom 510 communications system’s scope of delivery comprises the following:

■ 1 19" frame (1-12 frame) with slots for 1 control module and up to 2 power supply units and 12 interface cards

The basic configuration of a 19" frame includes the following components:

– 1 BPV+1-12 backplane

Preliminary Information Declarations of Conformity

– 1 MPS+1-AC power supply unit

– 1 mains cable for connection to the mains supply

– 1 MC+1-3 control module

– 1 CompactFlash Card; the firmware is stored on this card. This card is included in the scope of delivery only if the 1-12 frame is the first frame ordered and not being used to expand the OpenCom 510.

All other components (e.g. second power supply unit, interface cards and accompanying cables) are included as per the customer’s order.

■ 1 RS-232 to RJ45 adapter cable (for the V.24 interfaces of the MC+1-3 control module)

■ 1 set of mounting brackets and screws for installing the frame in a 19" rack

■ 1 set of dummy covers for covering unused slots

■ 1 set of short user guides

■ 1 CD

3.3

Declarations of Conformity

The communications systems of the OpenCom 100 product family comply with the requirements of EU directive 99/5/EC.

The declarations of conformity can be found on the Internet at http://www.aastra-detewe.de.

Installation

4. Installation

Safety Precautions

4.1

Safety Precautions

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

4.1.1 General Instructions

Please note: This product may be installed and serviced by qualified personnel only. Opening the housing and carrying out unauthorised repairs may damage the product and will invalidate the warranty.

DANGER!

Hazardous voltages inside the device!

The MPS+1-AC power supply unit may not be opened as this may lead to exposure to hazardous voltage!

Defective power supply units must be sent to the manufacturer for repairs.

Always use the original packaging when packing OpenCom 510 components for transport or storage.

CAUTION!

Static charge can damage the OpenCom 510. Before and during work on the electrical components of the OpenCom 510, discharge any static electricity from your body and the tools you are using.

Installation Safety Precautions

4.1.2 Notes on the Mains Supply

The OpenCom 510 may be connected only to mains sockets with a protective earth conductor.

Install the OpenCom 510 only near easily accessible, wall-mounted mains sockets.

Always use a dedicated circuit with 10 A protection to supply the 19" frame (1-

12 frame).

If the OpenCom 510 is being powered by two MPS+1-AC power supply units, each of the two units must be plugged into its own mains socket. It is not permissible to use multiway mains strips to connect more than one OpenCom 510 power supply unit or a OpenCom 510 and other devices to the same mains supply together.

The mains cables of the MPS+1-AC power supply units must have ferrite rings fitted. The mains cables are factory-fitted with ferrite rings.

Mains cable with ferrite ring

Install an overvoltage protection device.

4.1.3 Notes on EMC and Earthing

Please note: MOS modules:

Observe the regulations regarding modules and packaging carrying the MOS trademark!

Use earthing wrist straps connected to the appropriate points on the frame (see C in the illustration

OpenCom 510: 1-12 frame mounting points on page 26).

The mains socket’s protective earth conductor and the telephone earth line must be connected to one reference point for potential equalisation. This is normally the OpenCom 510 housing.

Installation Safety Precautions

Earthing and Potential

For the purpose of potential equalisation, all conductive parts of the

OpenCom 510 must be connected to the protective earth conductor (earth busbar of the building’s wiring system) by means of a solid or stranded wire of at least

2,5 mm

(yellow/green).

ø 2,5 mm 2

OpenCom 510: Earthing arrangement

The metal screens of the subscriber and trunk cables must be connected to the circuit common in the distributor or the patch field. The protective earth conductor of the 230 V mains cables is connected to the circuit common and the telephone earth line.

All metal parts of the communications system are mechanically and thus electrically coupled in order to provide protection through the protective earth conductor and the telephone earth line.

4.1.4 Notes on Installing the OpenCom 510

Do not allow any fluid to enter the OpenCom 510 as this may cause electric shocks or short circuits.

Do not install the OpenCom 510 during a thunderstorm. Do not connect or disconnect any cables during a thunderstorm.

The OpenCom 510 is designed for indoor use only. Route the cables in such a way that they cannot be stepped on or tripped over.

Installation Installation, Ambient Conditions

The OpenCom 510 must be securely screwed into the frame when installation work on the system is interrupted or terminated. Unused slots must be covered with dummy covers (included in the scope of delivery).

4.1.5 Notes on Installing Terminals

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

OpenCom 510. Proper use of standard terminals will satisfy this requirement.

The analogue interfaces may only be used to connect terminals that meet the appropriate technical requirements. For details, refer to

a/b Ports starting on page 48.

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

4.2

Installation, Ambient Conditions

The ambient temperature for operating the OpenCom 510 must be between +5 °C and +40 °C.

To maintain a safe ambient temperature, install the OpenCom 510 in a properly ventilated location, away from sources of direct heat.

Mount the OpenCom 510:

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

■ not in direct sunlight,

■ not behind curtains,

■ not in small, unventilated, damp rooms,

■ not near flammable materials,

■ nor near high-frequency devices such as transmitter and radiotherapy or similar apparatus.

Installation Installation in a 19" Rack

If the OpenCom 510 is to be installed together with other electronic equipment in a 19” cabinet, ensure that the air intake temperature for the OpenCom 510 does not exceed +40 °C.

The OpenCom 510 may also be connected to an IT system.

4.3

Installation in a 19" Rack

OpenCom 510: 1-12 frame mounting points

The OpenCom 510 is designed to be installed in 19" racks only.

The following mounting points for installation in a 19" rack can be found on the 1-

12 frame:

Left mounting bracket

Right mounting bracket

Installation Installing Modules

Mounting bracket screw bolts for front mounting (approx. 132 mm) to the uprights of the 19" rack

Mounting bracket screw bolts for mid-mounting (approx. 400 mm) to the uprights of the 19" rack

Left and right screw points for earthing wrist strap or circuit common connection between

1-12 frame and 19" rack

Note: If the OpenCom 510 is to be used as a wall-mounted instead of a floor-standing system, it must be installed in a standard-type wall-mounted enclosure using 19" mounting technology.

4.4

Installing Modules

A 0 B

C (1-6)

D (7-12)

OpenCom 510: 1-12 frame slots

4.4.1 Slots

The OpenCom 510 1-12 frame can house up to:

■ 2 power supply units

■ 1 control module

Installation Installing Modules

■ 12 interface cards (trunk or subscriber modules) split into 2 separate groups.

The following slots are provided for installing these modules:

Legend

Slot for group 1 power supply unit

Slot for group 2 power supply unit

Slot for central control module

Slots for group 1 interface cards (slots 1 - 6)

Slots for group 2 interface cards (slots 7 - 12)

Each of the two groups (1 or 2, or C and D, respectively, in the illustration) requires its own power supply unit. Power for the control module is always supplied by the group 1 power supply unit. The group 1 power supply unit must therefore always be installed.

Modules can be installed either when the entire system is configured or as an upgrade at a later time.

4.4.2 Notes on Disconnecting the Mains Supply

DANGER!

Hazardous voltages inside the device!

The OpenCom 510 must be disconnected from the mains supply for the following installation work:

■ Installation of the central control module

■ Installation of a power supply unit

If a 1-12 frame is being powered by two power supply units, it is de-energised by unplugging both mains cables.

Installation Installing Modules

DANGER!

Always unplug the mains cables of both power supply units when installing the central control module or a power supply unit.

If you unplug the mains cable of the group 2 (B) power supply unit, the

OpenCom 510 will still be operational! However, only the modules supplied by the group 1 (A) power supply unit, i.e. the central control module and the interface cards in slots 1 - 6, will be functional.

If you unplug the mains cable of the group 1 (A) power supply unit, the

OpenCom 510 ceases to be operational. However, slots 7 - 12 (D) will still be supplied with operating voltage. (Refer to the illustration

OpenCom 510: 1-12 frame slots on page 27 to determine the location of the modules specified in parentheses

above.)

The LEDs of each module indicate whether the respective module is operational.

For further information on LED indicators, refer to

Modules starting on page 59.

4.4.3 Installing the Central Control Module

The OpenCom 510 comes with the central control module installed. Should you need to exchange the central control module, proceed as follows:

Shut down the OpenCom 510. To do so, first restart the system by

– entering the code procedure H*185 (system PIN) # on a connected telephone, or

– clicking on Restart in the SYS Configuration: Restart menu in the Configurator .

Wait until the LEDs of the installed modules start flashing red.

DANGER!

Hazardous voltages inside the device!

Unplug all of the mains cables of the OpenCom 510 to disconnect the system from the mains supply.

Installation Installing Modules

The central control module must not be installed if the OpenCom 510 is switched on! Refer to

Notes on Disconnecting the Mains Supply starting on page 28.

Remove the screws with which the central control module is secured in the 1-

12 frame and pull the module out.

Unpack the central control module.

CAUTION!

Static charge can damage electronic devices. Observe the regulations regarding electrostatically sensitive components.

Carefully push the central control module into slot 0 (see also the illustration

OpenCom 510: 1-12 frame slots on page 27). The printing on the front of the

module should be at the top.

Ensure that the backplane plug of the central control module is securely plugged into the socket on the backplane.

Refit the screws to secure the module in the 1-12 frame.

Plug the desired cables into the corresponding RJ45 sockets on the central control module. Refer to

Modules starting on page 59 for information on pin

assignment.

Switch the OpenCom 510 on again. To do so, reconnect the group 1 power

supply unit (see A in the illustration OpenCom 510: 1-12 frame slots on page 27)

with the mains supply (if you are powering the OpenCom 510 with two power supply units, reconnect the second unit as well).

The system will now start up and all modules (interface cards) will be re-initialised.

Installation Installing Modules

10.

Observe the module LEDs during start-up of the OpenCom 510. Information on indicators can be found in

Modules starting on page 59.

Note: The MAC address for the OpenCom 510 is assigned by the central control module and cannot be changed. If the central control module has to be exchanged, you may need to change the IP settings. For further information on MAC addresses, refer to the online help.

Explanatory Note on Shutting Down the System

If the OpenCom 510 is disconnected from the mains supply, its main memory is deleted. The main memory stores the current configuration data, which are regularly copied to the CompactFlash memory card. Restarting the system causes it to copy the current configuration data from the main memory to the CompactFlash card, which ensures that the most recent configuration is restored when the system is started up.

4.4.4 Installing Interface Cards

Interface cards can be installed or exchanged with the system powered up (“hotplugging”). Proceed as follows:

If you want to exchange an interface card, the slot for this card needs to be deactivated first.

Open the PBX Configuration: Ports: Slots page in the Configurator . In the table row listing the card to be exchanged, click on Stop . The system then deactivates the slot. Any connections (telephone calls, data transfers) established through this card will be terminated.

Remove the screws with which the interface card is secured in the 1-12 frame and pull the card out.

Unpack the interface card and check whether it is the desired type. The type designation is printed on the front of the card.

Installation

MX+S01-8

Installing Modules

Detail: Printing on the front of an “MX+S01-8” type interface card

CAUTION!

Static charge can damage electronic devices. Observe the regulations regarding electrostatically sensitive components.

Carefully push the interface card into the corresponding slot. The printing on the front of the module should be at the top (see illustration in previous instruction).

Ensure that the backplane plug of the interface card is securely plugged into the socket on the backplane.

Refit the screws to secure the interface card in the 1-12 frame.

Plug the desired cables into the corresponding RJ45 sockets on the interface card. Refer to

Modules starting on page 59 for information on the pin

assignment for each interface card.

Cover any unused slots with dummy covers (included in the scope of delivery).

The dummy covers must be securely screwed to the frame!

If you have exchanged the interface card, you will need to reactivate the slot for this card.

Installation Installing Modules

Open the PBX Configuration: Ports: Slots page in the Configurator again. In the table row listing the card that has been exchanged, click on Start .

Observe the LEDs on the card. Information on indicators can be found in the

chapter Modules starting on page 59.

Checking the Status of the Interface Cards via the Web Console

You can also check the status of the interface cards via the Web console of the

OpenCom 510.

Open the PBX Configuration: Ports: Slots page in the Configurator .

In the Status table row, check whether a green tick is displayed for the newly installed interface card. The tick indicates that the interface card is operational.

4.4.5 Installing a Power Supply Unit

Depending on the number of installed modules (interface cards), either one or two power supplies are required (see A and B in the illustration

OpenCom 510: 1-12 frame slots on page 27):

■ The power supply unit for group 1 (A) must always be installed. It supplies the central control module and the interface cards in slots 1 - 6.

■ The power supply unit for group 2 (B) is required if interface cards are to be installed in slots 7 - 12.

If you want to deinstall the second power supply unit or exchange a defective one, proceed as follows:

Shut down the OpenCom 510. To do so, first restart the system by

– entering the code procedure H*185 (system PIN) # on a connected telephone, or

– clicking on Restart in the SYS Configuration: Restart menu in the Configurator .

Wait until the LEDs of the installed modules start flashing red.

Installation Installing Modules

DANGER!

Hazardous voltages inside the device!

Unplug all of the mains cables of the OpenCom 510 to disconnect the system from the mains supply.

Power supply units must not be installed if the OpenCom 510 is switched on!

Refer to

Notes on Disconnecting the Mains Supply starting on page 28.

Unpack the power supply unit.

CAUTION!

Static charge can damage electronic devices. Observe the regulations regarding electrostatically sensitive components.

Carefully push the power supply unit into the corresponding slot (see also the illustration

OpenCom 510: 1-12 frame slots on page 27). Seen from the front, the

mains inlet socket should be on the bottom right.

Ensure that the backplane plug of the power supply unit is securely plugged into the socket on the backplane.

Refit the screws to secure the power supply in the 1-12 frame.

Install further interface cards if required (see also Installing Interface Cards starting on page 31).

Switch the OpenCom 510 on. To do so, reconnect the power supply unit with the mains supply (if you are powering the OpenCom 510 with two power supply units, connect the second unit as well).

The system will now start up and all modules (interface cards) will be re-initialised.

Installation Backplane

Observe the module LEDs during start-up of the OpenCom 510. Information on indicators can be found in the chapter

Modules starting on page 59.

4.5

Backplane

The BPV+1-12 backplane of the OpenCom 510 supplies the modules installed in the 1-12 frame with the required power and system signals. The backplane is also used to provide access to the PCM highway (for transmitting utility data), the LAN

(for exchanging signalling data) and to the system clock circuits.

The backplane has vertically arranged sockets for the backplane plugs of the modules:

■ The MPS+1-AC power supply units and the MC+1-3 central control module are each connected by means of a 96-pin spring contact strip.

■ The interface modules are each connected by means of a 48-pin spring contact strip.

The backplane also carries the system serial number (etched into the backplane chip).

Should you need to exchange the backplane, proceed as follows:

DANGER!

Hazardous voltages inside the device!

Unplug all of the mains cables of the OpenCom 510 to disconnect the system from the mains supply.

Refer to

Notes on Disconnecting the Mains Supply starting on page 28.

Uninstall all modules and power supply units from the 1-12 frame (see

Installing Modules starting on page 27).

Remove the screws on the backplane (see arrows in the illustration

OpenCom 510: Backplane screws ). Carefully remove the backplane from the 1-

12 frame, pulling it out of the frame towards the front.

Installation Backplane

OpenCom 510: Backplane screws

From the front, insert the new backplane into the 1-12 frame. Insert and tighten the screws to secure the backplane in the 1-12 frame.

Reinstall the modules in the designated slots.

Cover any unused slots with dummy covers (included in the scope of delivery).

The dummy covers must be securely screwed to the frame!

Switch the OpenCom 510 on again. To do so, reconnect the power supply unit with the mains supply (if you are powering the OpenCom 510 with two power supply units, connect the second unit as well).

Observe the module LEDs during start-up of the OpenCom 510. Information on indicators can be found

Modules starting on page 59.

If you were using software packages subject to licensing (e.g. the internal voice mail program OpenVoice ) prior to exchanging the backplane, this software needs to be reactivated using new activation keys. Contact your dealer or

Aastra DeTeWe distributor.

The new keys will be generated using the backplane serial number. You will be required to state this serial number. You can determine the serial number in the

System Info: Versions menu in the Configurator .

10.

Enter the new activation key in the SYS Configuration: Licences menu in the

Configurator . This will reactivate the software packages.

Installation Uninterruptible Power Supply

The backplane serial number is also used to encode the PARK of a DECT system.

If you are using a DECT system with the OpenCom 510, you will need to reenter the PARK.

11.

You can determine the new PARK in the System Info: Versions menu in the

Configurator .

4.6

Uninterruptible Power Supply

If you are using uninterruptible power supplies (UPS) they must be earthed separately.

The total leakage current must not exceed 3.5 mA per mains socket. Use the leakage current specified by the UPS manufacturer as a reference.

An MPS+1-AC power supply unit has a leakage current of < 0.5 mA.

A 900-watt UPS is entirely sufficient to power the OpenCom 510.

4.7

Power Failure

In the event of a power failure, the system memory will retain all data (program and user data) without any changes.

The internal clock will continue to run for 24 hours. If the power failure lasts longer than 24 hours, the time and date will be reset to the factory setting when power is switched on again, and updated (by means of a signal from the exchange) after the first external outgoing call.

With multi-terminal access configurations, the OpenCom 510 provides an emergency service feature: In the event of a power failure, the S

1 interface will be switched to the S

8 interface, enabling you to make calls through a connected terminal.

The following is required to enable emergency service:

■ An MX+S01-8 interface card must be installed.

Installation Power Failure

■ The power failure circuit of this interface card must be activated. To do so, set

DIP switches S17 to S20 to “ON”. The interface card is delivered with the power failure circuit deactivated (default: off ).

■ Port S

1 must be connected to an NTBA (multi-terminal access) and configured as an external connection.

■ Port S

8 must be configured as an internal connection. An ISDN telephone with emergency service capability must be connected to this port.

Note: Emergency service is not possible with system access configurations.

Testing the Power Failure Circuit

You can test the configuration as follows:

Disconnect the OpenCom 510 from the mains supply (see instructions in

Installing the Central Control Module starting on page 29, steps 1 to 3).

Disconnect the NTBA from the mains supply.

It should now be possible to make external calls through the ISDN telephone connected to port S

Installation

S17/18 S19/20

2 1 2 1

ON ON

MX+S01-8: Location of the DIP switches for the power failure circuit

Power Failure

Interfaces and Connectible Terminals

5. Interfaces and Connectible

Terminals

Overview

5.1

Overview

The OpenCom 510 interfaces have been implemented as RJ45 sockets on the front

of the interface cards and the central control module. No special proprietary

cables are required. Patch panels can be connected by means of standard patch cables.

For technical information on the interfaces, refer to

Modules starting on page 59.

Interface

2M pn pn a/b

LAN

Card Properties

MX+S01-8 8 S

interfaces for either external or internal connections

Page

MT+S2M1-1 1 S

interface for connecting to digital networks (primary multiplex connections) or for cascading two PBXs

MS+UPN1-8 8 U pn

interfaces, U

DECT-capable pn

interfaces are not

MS+UPN2-8 8 U pn

interfaces, U

DECT-capable pn

interfaces are

MS+A1-8

MC+1-3

8 a/b interfaces

1 Ethernet port (10/100 Mbits/s)

(on central control module)

COM / V.24

MC+1-3 2 V.24 ports

(on central control module)

The following terminals and systems can be connected to the OpenCom 510’s interfaces:

Interfaces and Connectible Terminals

Overview: Interfaces and Connectible Terminals

Interface

U pn

Terminals/Systems

(internal) ISDN terminals (DSS1 protocol): telephones, fax machines, base stations and handsets,

ISDN cards for PCs

Digital terminals (ISDN terminals, system telephones) and DECT base stations

Page

a/b

LAN

Analogue terminals: telephones, G3 fax machines, (external or internal) modems, external music-on-hold devices, external voice mail systems, external intercom systems

Connection to a LAN (local area network) or a DSL modems

Connection of VoIP terminals

105

COM / V.24

Connection of a PC (for transmitting connection data) 52

Ports

5.2

Ports

All of the eight S

interfaces on the MX+S01-8 interface card are switchable, i.e. they can be used either for external connections (ISDN basic access or a second

PBX) or for internal connections (ISDN terminals). It is not possible to use these interfaces simultaneously for both types of connections.

The S

ports have been implemented as RJ45 sockets.

Pin Assignment

+ + – –

1 2 3 4 5 6 7 8

interface pin assignment

Interfaces and Connectible Terminals

The following table explains the S

interface pin assignment.

Pin Number

Assignment

Not used

Send +

Receive +

Receive -

Send -

Not used

Ports

5.2.1 Termination

Each interface card has 16 DIP switches (S1 to S16, two per S

interface). The DIP switches activate the required terminating resistors for the S

buses (100 ohms per

bus). In the default setting, all terminating resistors are activated (Default: on).

MX+S01-8: Location of DIP switches S1 to S16

Note: The following configuration information applies to external as well as internal S

interfaces.

Interfaces and Connectible Terminals S

Ports

Bus Configuration: OpenCom 510 at the End of an S

Bus

If a OpenCom 510 is connected at the end of an S

bus, the terminating resistors of the relevant S

interface cards must be activated.

In a typical configuration, the OpenCom 510 will be connected to the network termination for basic access (NTBA) with an externally switched S

port; therefore, all terminating resistors of the interface card are activated in the default setting.

OpenCom 510

IAE IAE

MX+S01-8: Terminating resistors activated

One end of the S

bus is terminated by the OpenCom 510; the terminating resistors must be activated (DIP switches set to “on”).

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

TR = Terminating Resistor, the S

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

Termination on an ISDN socket

The illustration

Termination on an ISDN socket

shows an IAE with integrated terminating resistors.

Bus Configuration: OpenCom 510 in the Middle of an S

Bus

If a OpenCom 510 is connected in the middle of an S

bus, the terminating resistors of the relevant S

interface cards must be deactivated.

Remove the interface card by following the instructions in Installing Interface

Cards starting on page 31.

Interfaces and Connectible Terminals S

Ports

The DIP switches are protected by a plastic foil. Use a pointed tool such as a screwdriver to slide the DIP switches down (see arrow in the illustration

MX+S01-8: Terminating resistors deactivated ).

OpenCom 510

TR TR

IAE IAE

MX+S01-8: Terminating resistors deactivated

Both ends of the S

bus are terminated by terminating resistors; the terminating resistors must be deactivated (DIP switches set to “1 2”).

5.2.2 External ISDN Ports (S

External)

You can connect the OpenCom 510 to the NTBA or to a second OpenCom 510 for

PBX cascading.

To connect the OpenCom 510 to the NTBA, wire pins 3, 4, 5, 6 of the NTBA and of the OpenCom 510 1:1.

To directly connect two OpenCom 510 systems via the external S

ports, connect the RJ45 sockets of the systems by means of a crossed twisted-pair cable. The distance between the two PBXs must not exceed 1000 metres (see also

PBX Networking starting on page 149).

PBX 1, S

ext

1 2 3 4 5 6 7 8

8 7 6 5 4 3 2 1

PBX 2, S

ext

(RJ-45 socket)

Wiring for direct connection

Interfaces and Connectible Terminals U pn

Ports

5.2.3 Internal S

Ports

Up to eight ISDN terminals per bus can be connected to the internal S

ports by means of four-wire cables. Three of these terminals can be supplied with power from the bus; any additional terminals will require their own power supply. The internal S

buses can be used for point-to-multipoint connections in accordance with the DSS1 protocol (Euro ISDN).

ISDN terminals can be connected to internal S

ports by means of a crossed ISDN cable. For the pin assignment of crossed ISDN cables, refer to the illustration

Wiring for direct connection on page 44. If the terminal did not come with a suitable ISDN

cable, contact your dealer or Aastra DeTeWe distributor.

The length of an internal S

bus cable must not exceed 150 m. Each internal S

bus has a power feed of approx. 3 W. The feed voltage is – 42 V.

5.3

U pn

Ports

5.3.1 Terminals Connected to U pn

Ports

U pn

ports can be used to connect one of the following system terminal types:

■ RFP 22 DECT base station

■ OpenPhone 71, OpenPhone 73 or OpenPhone 75 system telephone

■ OpenPhone 61, OpenPhone 63 or OpenPhone 65 system telephone

The (corded) OpenPhone 63 and OpenPhone 65 system telephones can be cascaded by means of a U pn

Phones to one U pn

adapter, which enables you to connect two Open-

port. For further information, refer to the “OpenPhone 61, 63,

65” user guide.

The RFP 22 DECT base station can be used to connect the OpenPhone 26 and

OpenPhone 27 DECT handsets. The OpenPhone 27 has an USB interface for data transmissions and Internet access. Note that handsets such as the OpenPhone 26 can also be used in conjunction with base stations operating with the GAP/CAP standard.

Interfaces and Connectible Terminals U pn

Ports

Note on the MS+UPN2-8 Interface Card

U pn

interfaces can only be used to connect DECT base stations if the MS+UPN2-8 has been installed in the master system; if this card is in the slave system, it is not possible to connect any DECT base stations to the card’s U pn

interfaces.

Note on the MS+UPN1-8 Interface Card

The U pn

interfaces of the

MS+UPN1-8 interface card cannot be used to connect DECT base stations.

5.3.2 Technical Information

The U pn

ports have been implemented as RJ45 sockets.

Each of the devices listed above can be connected to the U pn

interface by means of a two-wire 1:1 cable. System terminals come with a suitable cable for connection to the RJ45 socket of the interface.

A two-wire cable connected to a U pn a 0.6 mm twisted-pair cable.

port can be up to 1000 m long, provided it is

Each U pn

port has a power feed of approx. 2.1 W. The short-circuit-proof feed voltage is – 42 V.

5.3.3 DECT Base Station Connection Variants

A DECT base station can be connected to either one or two U pn

interfaces:

■ If the DECT base station is connected to one U pn

interface, four simultaneous calls or connections can be made through the handsets.

■ If the DECT base station is connected to two U pn

interfaces, eight simultaneous calls or connections can be made through the handsets.

Please note that it is not possible to establish more simultaneous external connections than there are external B channels.

To connect a DECT base station to two U pn ports on the MS+UPN2-8 interface card: U

interfaces, you can combine two U pn

ports 1+2, 3+4, 5+6 or 7+8 (U pn pn

port 2 is connected to U pn

port 1, U pn

port 4 to U pn

port 3 etc.). Ports are combined by setting the DIP switches on the card accordingly. In this configuration, the DECT

Interfaces and Connectible Terminals U pn

Ports base station must be connected to the first U pn cable (system telephone cable).

port of the pair by means of a 1:1

Pin Assignment

1 2 3 4 5 6 7 8

U pn interface pin assignment

The following table explains the U pn

interface pin assignment.

Pin Number

Assignment

Not used

U pn

a *)

U pn

b *)

Not used

*) If the DIP switches are set accordingly, the conductors of the adjacent U pn

port will be connected here; use only the first U pn

port in this configuration.

Setting DIP Switches

Remove the interface card by following the instructions in Installing Interface

Cards starting on page 31.

The DIP switches are protected by a plastic foil. Use a pointed tool such as a screwdriver to slide the DIP switches to the right (see arrow in the illustration

Location of the DIP switches on the MS+UPN2-8 interface card on page 48).

Interfaces and Connectible Terminals

1 2 a/b Ports

Location of the DIP switches on the MS+UPN2-8 interface card

5.4

a/b Ports

5.4.1 Terminals Connected to a/b Ports a/b ports can be used to connect analogue terminals, e.g. apparatus for speech and data communications using pulse or DTMF dialling, e.g.:

■ analogue telephones,

■ G3 fax machines,

■ (external or internal) analogue modems,

■ external music-on-hold devices,

■ external voice mail systems,

■ external intercom systems.

Please note: Observe the following notes on connecting analogue terminals. Terminals that do not satisfy the technical requirements for connection with the OpenCom 510 may cause damage to the communications system!

Interfaces and Connectible Terminals a/b Ports

Analogue Telephones

If analogue telephones are to be connected, we recommend devices that support dual-tone multi-frequency (DTMF) dialling as it is not possible to use the additional features of the OpenCom 510 with pulse dialling telephones.

Modems

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

Music on Hold

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

Speech Design. If you are not using an external MoH device, the OpenCom 510 offers an internal MoH feature: You can change the MoH melody in the SYS Configuration: Components menu of the Configurator . For further information, refer to the online help.

Please note: For external music on hold, use only devices with an input impedance of 600 ohms, floating connection. An incorrect input impedance can cause irreparable damage to the

OpenCom 510!

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

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:

■ 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 . Deactivate the Actuator option, if you want

Interfaces and Connectible Terminals a/b Ports to use the actor port of the OpenCom 510 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 510.

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.

5.4.2 Technical Information

The a/b ports have been implemented as RJ45 sockets. Each of the devices listed above can be connected to the a/b interface by means of a two-wire 1:1 cable.

A two-wire cable connected to an a/b port can be up to 6500 m long, provided it is a 0.6 mm twisted-pair cable, or up to 3000 m if a 0.4 mm twisted-pair cable is used.

The 50 Hz/40 V AC ringing voltage of the eight interfaces is supplied by the interface card.

Pin Assignment

1 2 3 4 5 6 7 8 a/b interface pin assignment

Interfaces and Connectible Terminals

The following Table explains the a/b interface pin assignment.

Pin Number

Assignment

Not used

Channel a

Channel b

Not used

LAN Port

5.5

LAN Port

The LAN port (Ethernet interface) on the MC+1-3 central control module allows the integration of the OpenCom 510 into a company LAN (Local Area Network) with the use of a 10-Mbit hub or switch. In such a configuration, the OpenCom 510 can, for example, act as an IP router for establishing Internet connections.

The Ethernet interface supports transmission rates of 10 Mbits/s and 100 Mbits/s in half duplex or full duplex mode. The transmission rate and mode are selected automatically (Auto Sensing function).

A LAN cable (twisted-pair in accordance with 10BaseT or 100BaseTX) must not be longer than 100 m. Safe operation with 100 Mbits/s requires the use of category 5 cables and sockets. Use a shielded Ethernet cable (STP cable, Shielded Twisted Pair cable).

5.5.1 DSL Port

External DSL modems can be connected via the LAN port. This requires the use of an external switch or hub which connects the output of the DSL modem (NTBBA) to the LAN port of the OpenCom 510. The router will then convert the PPPoE protocol to the TCP/IP protocol of the LAN.

Interfaces and Connectible Terminals COM Port

The DSL modem is connected by means of a crossed twisted-pair cable. Alternatively, you can use a switchable port on the hub, which is usually marked with an

“X”.

OpenCom

TAE

DSL & Uk

DSL

Splitter

Net

TCP/IP &

PPPoE

NTBA S

0 DSL

Crosslinked twisted pair cable

PPPoE

TCP/IP

DSL

Modem

Hub Net

Network connection of the OpenCom 510 via ISDN and DSL

5.5.2 Service PC

The Ethernet interface can also be used to connect a service PC using a crossed

Ethernet cable.

5.6

COM Port

The COM port (V.24-1 interface) on the MC+1-3 central control module can be used to connect a PC for the purpose of transmitting connection data. Connection data can be analysed in detail with the connection data recording program Open-

Count.

Please note: The COM port cable must not be longer than 3 metres.

The V.24 interface uses a transmission rate of 19.2 kbits/s.

Note: A special 10-pin cable is required for connecting apparatus to the V.24-1 interface. Contact your Aastra DeTeWe distributor or local retailer if you want to purchase one of these cables.

Interfaces and Connectible Terminals

Pin Assignment

1 2 3 4 5 6 7 8 9 10

V.24 interface pin assignment

The following Table explains the V.24 interface pin assignment.

Pin Number

CTS

TXD

RTS

RXD

Assignment

GND (EED)

Not used

DTR

DSR

DCD

Not used

COM Port

OpenPhone 71/73/75: Extensions and accessories for system telephones Power supply unit

6. OpenPhone 71/73/75:

Extensions and accessories for system telephones

6.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

■ 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 .

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

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

Connect the power supply unit to the mains power supply (see

Connecting the keypad extension starting on page 56).

OpenPhone 71/73/75: Extensions and accessories for system telephonesKeypad extensions

6.2

Keypad extensions

Up to three keypad extensions can be connected to system telephones: either three keypad extensions of the model KeyExtension 73P or three keypad extensions of the model KeyExtension 75D. A combination of these keypad extensions is, however, not possible.

The following equipment combinations are possible:

Keypad extension …

KeyExtension 73P

KeyExtension 75D

… with the features

– 36 keys with LED indicator

– Labelling on label strips connectable to a system telephone

– OpenPhone 73

– OpenPhone 73 IP

– OpenPhone 75

– OpenPhone 75 IP

– 20 keys with LED indicator

– 3 keys with LED indicator to shift levels; enables programming of 60 storage locations on each keypad extension

– Labelling of the keys over the display; each key is assigned to a display line

– OpenPhone 75

– OpenPhone 75 IP

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

PBX Configuration: Devices: System Phones or VoIP Phones ). 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 510 must be less than 1000 metres. You will need a plug-in power supply unit no. 4516000 (in Britain operate only the AC adapter with the part no.

OpenPhone 71/73/75: Extensions and accessories for system telephonesKeypad extensions

4516001) to 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

Yes

IP system telephone

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

Connecting the keypad extension

CAUTION!

Guard against static charges!

Please note:

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

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

OpenPhone 71/73/75: Extensions and accessories for system telephones Headset

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.

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

(1).

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

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

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

Connect the power supply unit to the mains power supply.

Connect the system telephone with the U pn

or ethernet port.

6.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.

OpenPhone 71/73/75: Extensions and accessories for system telephones Headset

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 .

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

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

Activate the headset on the system telephone in the menu Phone settings:

Headset (see also the system telephone’s user guide).

Modules

7. Modules

This chapter provides detailed technical information on the modules which can be installed in the OpenCom 510. You will find information on their respective fields of application, along with technical and operational information and notes on indicators.

The modules fulfil the following tasks:

■ Power supply units (max. 2) provide the OpenCom 510 with power.

■ A central control module controls the entire system. This module also houses the memory card (CompactFlash) for storing data.

■ Interface cards are used to connect the OpenCom 510 to the telecommunications network (or to another communications system) and to connect terminals.

A number of interface cards are available for these tasks. Depending on the interface card’s functions, it may also be referred to as a trunk module or as a subscriber module.

For detailed information on installing modules, refer to the chapter Installing

Modules starting on page 27.

Please note: When installing modules, always observe the

tions starting on page 22!

Safety Precau-

Modules Module Naming Conventions

7.1

Module Naming Conventions

Modules are named according to a schema which enables the deduction of the module’s type and function:

Mx+y1-z

+ y

Abbr.

M x

Meaning

Module

Indicates the module type as follows:

C Control

Subscriber

Trunk

Subscriber/Trunk

Power Supply

Character used to divide the product name

Indicates the interface type as follows:

A Analogue interface

UPN

U pn

interface

S2M S

interface

Module generation

Character used to divide the product name

Number of interfaces

Modules Overview of Available Modules

7.2

Overview of Available Modules

The following table provides an overview of modules available for the

OpenCom 510:

Name

MPS+1-AC

MC+1-3

MT+S2M1-1

MX+S01-8

Description

Power supply with AC/DC transformer

Central control module with three interfaces

Trunk module with one S

interface for connecting to digital networks or for cascading two PBXs

Trunk or subscriber module with eight S

interfaces for either external (trunk) or internal (subscriber) connections

MS+UPN1-8 Subscriber module with eight U pn

interfaces for connecting digital terminals (ISDN terminals, system telephones); does not support DECT base stations

MS+UPN2-8 Subscriber module with eight U pn

interfaces for connecting digital terminals (ISDN terminals, system telephones) and DECT base stations

MS+A1-8 Subscriber module with eight a/b interfaces for connecting analogue terminals

MT+A1-4

MG+ETH1-1

Trunk module with four a/b interfaces for connecting to analogue trunk lines

Media Gateway module for VoIP

115

Page

The name of the module and the interface type are printed on the front of the modules. The following illustration shows the printing on the MX+S01-8 interface card.

Modules

MX+S01-8

MPS+1-AC

Detail: Printing on the front of an MX+S01-8 interface card

7.3

MPS+1-AC

Field of Application

The MPS+1-AC power supply unit supplies power to the first six slots (1 to 6) of the

OpenCom 510. It converts the (220 V/110 V) AC input voltage into DC voltage

+3.3 V and – 42 V.

If the remaining slots (7 to 12) are to be used, a second MPS+1-AC power supply unit will need to be installed.

Modules

MPS+1-AC

MPS+1-AC

MPS+1-AC: Front view

Technical Data

The following data refer to the supply of power to the first six slots.

Input Voltage

Rated voltage

Voltage range

Rated current

Efficiency at rated load

230 V via standard IEC connector

95 V to 275 V

2.0 A at 115 V

1.0 A at 230 V

0.9 A at 275 V

> 80 %

Modules MPS+1-AC

+3.3 V Output Voltage

Rated voltage

Voltage range

Rated current

Current limitation

Short-circuit

+3.3 V

+3.2 V … +3.4 V

10.0 A

12 A to 15 A

Continuous short-circuit protection

– 42 V Output Voltage

Rated voltage

Voltage range

Rated current

Current limitation

Short-circuit

–42 V

–40 V … –44 V

4.0 A

4.4 A to 5.5 A

Continuous short-circuit protection

Indicators

There are two LEDs on the front of the MPS+1-AC power supply unit. The LEDs indicate the following:

■ Left: If the left LED is constantly lit up green, the output voltage is +3.3 V.

■ Right: If the right LED is constantly lit up green, the output voltage is –42 V.

The LEDs only indicate that the voltage is present. They do not say anything about the voltage quality.

Operational Information

The MPS+1-AC power supply unit will be ready for operation as soon as it has been plugged into the designated slot (see

Slots starting on page 27).

The mains voltage of 230 V is drawn through the standard IEC connector. The output voltages are fed to the BPV+1-12 backplane through the 96-pin spring

contact strip (see Backplane starting on page 35).

Modules MC+1-3

In the event of a power failure, the power supply unit will generate a power failure signal.

7.4

MC+1-3

MC+1-3: Front view

Field of Application

The MC+1-3 module is the central control module of the OpenCom 510. It can be installed in slot 0 only (at the left end in the 1-12 frame; see

Slots starting on page 27).

In addition to the control function, the MC+1-3 central control module provides a number of interfaces. These are standard external Ethernet (1x) and V.24 (2x) interfaces as well as internal PCMV, PCMH and CompactFlash slot interfaces.

Modules MC+1-3

Technical Information

■ The MC+1-3 central control module is powered by the group 1 power supply unit.

■ The MC+1-3 central control module has a plug-in card (MSUB-MRAM) with

128 Mbytes of main (random access) memory.

Please note: This plug-in card must not be exchanged by service personnel. In the event of a malfunction, the entire MC+1-3 central control module must be sent in for repair.

■ The MC+1-3 central control module has a CompactFlash slot (MSUB-MFL,

PCMCIA interface) for CompactFlash cards. The following data are stored on the CompactFlash card: the OpenCom 510 firmware, the system terminal software, the configuration data and all customer data such as audio files for the internal voice mail system.

Note: Only licenced cards may be used. These are currently

(May 2004) special 256-Mbyte cards by SanDisk. Contact your

Aastra DeTeWe distributor or local retailer if you want to purchase one of these cards.

■ The Ethernet port (10/100 Mbits/s) can be used to connect the OpenCom 510 to the LAN.

■ The V.24-1 interface can be used to connect additional apparatus, e.g. a computer for analysing call charges.

For information on the V.24 interface pin assignment, refer to COM Port starting on page 52.

Indicators

There are four LEDs on the front of the MC+1-3 central control module.

Modules

MC+1-3

MC+1-3

MC+1-3: LEDs

The LEDs indicate the following:

LED 1: Flashing yellow

LED 2: Constantly green

New software is being loaded onto an interface card (the corresponding interface card’s indicator will be constantly red).

The central control module is operational (flickering is normal).

Flashing green/yellow The system software (firmware) is starting up.

Flashing yellow The booter is reloading.

Constantly yellow

Constantly red

The system is booting.

System fault

LED 3: –

LED 4: Constantly green

Not used

An Ethernet connection has been established.

Operational Information

If you need to exchange the central control module, shut down the system first!

The OpenCom 510 must be disconnected from the mains supply (see

Installing the

Central Control Module starting on page 29).

Do not pull the CompactFlash card during operation as this may cause data to be lost!

A MC+1-3 central control module installed in a master system provides the following central resources:

■ 3 three-party conferences

Modules

■ 6 DTMF transmitters

■ 10 DTMF receivers

■ 1 Music On Hold

■ 32 HDLC controllers for RAS, ISP and DECT data.

7.5

MT+S2M1-1

MT+S2M1-1

MT+S2M1-1: Front view

Field of Application

The MT+S2M1-1 interface card provides one ISDN S

interface for connecting the

OpenCom 510 either to a primary rate access or to a second PBX (ISDN point-topoint connection).

Modules MT+S2M1-1

The MT+S2M1-1 interface card can be installed in any of the slots (1 to 12) of the

OpenCom 510 (see Slots starting on page 27).

Technical Information

■ The MT+S2M1-1 interface card can also be installed in a slave system.

■ A maximum of four MT+S2M1-1 interface cards can be configured in the entire system.

■ No settings need to be made on the MT+S2M1-1 interface card.

■ The MT+S2M1-1 interface card runs on software acquired from the system.

After the card has been installed it will automatically load the required software.

■ The maximum range is 300 m.

■ The short-circuit-proof feed voltage is – 42 V/7 W.

Pin Assignment

The following table shows the pin assignment for the RJ45 connector of the

interface (labelled “S2M”; see the illustration MT+S2M1-1: Front view on page 68):

Pin Number

Assignment

IN a

IN b

Not used

OUT a

OUT b

Not used

Modules MT+S2M1-1

The following table shows the pin assignment for the RJ45 connector of the power feed cable (labelled

“–42 V”; see the illustration

MT+S2M1-1: Front view on page 68):

Pin Number

Assignment

Not used

–42 V

0 V

–42 V

Not used

Indicators

There are four LEDs on the front of the MT+S2M1-1 interface card.

MT+S2M1-1

MT+S2M1-1: LEDs

The LEDs indicate the following:

Modules MX+S01-8

LED 1: Constantly yellow

LED 2: Constantly green

Flashing yellow

Constantly red

LED 3: Constantly green

At least one connection established through the interface card is active.

The interface card is operational; the slot has been activated (flickering is normal).

The interface card is ready, but the slot has not been activated or the interface card has not been configured yet.

New software is being loaded onto the interface card. If the LED lights up red for an extended period of time, there may be a fault.

The interface card is providing the system clock signal (indicated only in the master system and only on an interface card).

Not used LED 4: –

Operational Information

The MT+S2M1-1 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deactivated in the

Configurator in the web console (see

Installing Interface Cards starting on page 31).

7.6

MX+S01-8

Field of Application

The MX+S01-8 interface card provides eight 8 S

interfaces which can be used for either external connections, i.e. to connect the OpenCom 510 to a digital network

(PSTN, Public Switch Telephony Network), or internal connections, i.e. to connect digital terminals (ISDN telephones, ISDN fax machines etc.) to the OpenCom 510.

The MX+S01-8 interface card can be installed in any of the slots (1 to 12) of the

OpenCom 510 (see Slots starting on page 27).

Technical Information

■ The MX+S01-8 interface card can also be installed in a slave system.

Modules MX+S01-8

■ DIP switches S1 to S16 can be used to activate a 100-ohm terminal resistor

(default: on).

For further information, refer to

Termination starting on page 42.

■ The power failure circuit can be activated by means of DIP switches S17 to S20

(default: off ). If activated, the system will connect the first S

interface with the eighth S

interface in the event of a power failure; provided the system has been configured accordingly, external calls can be made using an emergency telephone.

For further information, refer to

Power Failure starting on page 37.

■ All eight S

interfaces can be configured either as subscriber (internal) interfaces or as trunk (external) interfaces.

For further information, refer to

S0 Ports starting on page 41.

■ The MX+S01-8 interface card can provide the system clock signalling.

■ The MX+S01-8 interface card runs on software acquired from the system. After the card has been installed it will automatically load the required software.

Pin Assignment

For information on the S

page 41.

interface pin assignment, refer to

S0 Ports starting on

Indicators

There are four LEDs on the front of the MX+S01-8 interface card.

MX+S01-8

MX+S01-8: LEDs

Modules MS+UPN1-8

The LEDs indicate the following:

LED 1: Constantly yellow

LED 2: Constantly green

Flashing yellow

Constantly red

LED 3: Constantly green

LED 4: Constantly yellow

At least one connection established through the interface card is active.

The interface card is operational; the slot has been activated (flickering is normal).

The interface card is ready, but the slot has not been activated or the interface card has not been configured yet.

New software is being loaded onto the interface card. If the LED lights up red for an extended period of time, there may be a fault.

The interface card is providing the system clock signal (indicated only in the master system and only on an interface card).

The interface card is running a combination of subscriber and trunk connections, i.e. both internal and external S

interfaces have been configured.

Operational Information

The MX+S01-8 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deactivated in the

Configurator in the web console (see

Installing Interface Cards starting on page 31).

All three protocol layers can be individually configured as master or slave for each

interface.

The S

interfaces can be configured as DSS1-PP, DSS1-PMP or Q.SIG lines.

7.7

MS+UPN1-8

Field of Application

The MS+UPN1-8 interface card provides eight U pn

interfaces for connecting system terminals; however, it is not possible to connect DECT base stations.

Modules MS+UPN1-8

The MS+UPN1-8 interface card can be installed in any of the slots (1 to 12) of the

OpenCom 510 (see

Slots starting on page 27).

Technical Information

■ The MS+UPN1-8 interface card can also be installed in a slave system.

■ No settings need to be made on the MS+UPN1-8 interface card.

■ The MS+UPN1-8 interface card runs on software acquired from the system.

After the card has been installed it will automatically load the required software.

Pin Assignment

RJ45 Connector Pin Assignment for the MS+UPN1-8 Interface

Pin Number Assignment

1 Not used

Not used

U pn pn

Not used

Indicators

There are four LEDs on the front of the MS+UPN1-8 interface card.

Modules

MS+UPN1-8

MS+UPN1-8

MS+UPN1-8

The LEDs indicate the following:

LED 1: Constantly yellow

LED 2: Constantly green

Flashing yellow

Constantly red

LED 3: –

LED 4: –

At least one connection established through the interface card is active.

The interface card is operational; the slot has been activated (flickering is normal).

The interface card is ready, but the slot has not been activated or the interface card has not been configured yet.

New software is being loaded onto the interface card. If the LED lights up red for an extended period of time, there may be a fault.

Not used

Operational Information

The MS+UPN1-8 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deactivated in the

Configurator in the web console (see

Installing Interface Cards starting on page 31).

The short-circuit-proof feed voltage is – 42 V.

Modules MS+UPN2-8

7.8

MS+UPN2-8

Field of Application

The MS+UPN2-8 interface card provides eight U pn system terminals and DECT base stations.

interfaces for connecting

The MS+UPN2-8 interface card can be installed in any of the slots (1 to 12) of the

OpenCom 510 (see

Slots starting on page 27).

Technical Information

■ The MS+UPN2-8 interface card can also be installed in a slave system.

■ A maximum of 48 RFPs (Radio Fixed Parts, DECT base stations) can be connected to the entire system.

■ In order to connect RFPs, U pn

ports 1+2, 3+4, 5+6 or 7+8 can be combined by setting the DIP switches on the card accordingly.

For further information, refer to

Upn Ports starting on page 45.

■ The MS+UPN2-8 interface card runs on software acquired from the system.

After the card has been installed it will automatically load the required software.

Pin Assignment

For information on the U pn

page 45.

interface pin assignment, refer to

Upn Ports starting on

Indicators

There are four LEDs on the front of the MS+UPN2-8 interface card.

Modules

MS+UPN2-8

MS+UPN2-8

MS+UPN2-8: LEDs

The LEDs indicate the following:

LED 1: Constantly yellow

LED 2: Constantly green

Flashing yellow

Constantly red

At least one connection established through the interface card is active.

The interface card is operational; the slot has been activated (flickering is normal).

The interface card is ready, but the slot has not been activated or the interface card has not been configured yet.

New software is being loaded onto the interface card. If the LED lights up red for an extended period of time, there may be a fault.

Not used

LED 3: –

LED 4: –

Operational Information

The MS+UPN2-8 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deactivated in the

Configurator in the web console (see

Installing Interface Cards starting on page 31).

Modules MS+A1-8

7.9

MS+A1-8

Field of Application

The MS+A1-8 interface card provides eight analogue interfaces for connecting analogue terminals.

The MS+A1-8 interface card can be installed in any of the slots (1 to 12) of the

OpenCom 510 (see

Slots starting on page 27).

Technical Information

■ The MS+A1-8 interface card can also be installed in a slave system.

■ The MS+A1-8 interface card supports pulse dialling as well as dual-tone multifrequency (DTMF) dialling. The central receivers of the MC+1-3 interface card are used for DTMF recognition.

■ Calling line identification presentation (CLIP) is supported.

■ The consultation feature can be selected by means of a flash key and/or earthing key.

■ The MS+A1-8 interface card runs on software acquired from the system. After the card has been installed it will automatically load the required software.

■ No settings need to be made on the MS+A1-8 interface card.

Pin Assignment

For information on the a/b interface pin assignment, refer to

a/b Ports starting on page 48.

Indicators

There are four LEDs on the front of the MS+A1-8 interface card.

Modules

MS+A1-8

MS+A1-8

MS+A1-8: LEDs

The LEDs indicate the following:

LED 1: Constantly yellow

LED 2: Constantly green

Flashing yellow

Constantly red

LED 3: –

LED 4: –

At least one connection established through the interface card is active.

The interface card is operational; the slot has been activated (flickering is normal).

The interface card is ready, but the slot has not been activated or the interface card has not been configured yet.

New software is being loaded onto the interface card. If the LED lights up red for an extended period of time, there may be a fault.

Not used

Operational Information

The MS+A1-8 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deactivated in the Configurator in the web console (see

Installing Interface Cards starting on page 31).

Modules MS+A1-4

7.10

MS+A1-4

Field of Application

The MT+A1-4 provides interface card four analogue interfaces for connecting analogue trunk lines.

The MT+A1-4 interface card can be installed in any of the slots (1 to 12) of the

OpenCom 510 (see

Slots starting on page 27).

Technical Information

■ The MT+A1-4 interface card can also be installed in a slave system.

■ The MT+A1-4 interface card supports pulse dialling as well as dual-tone multifrequency (DTMF) dialling.

■ Ringing tone detection works at 16

, 25 or 50 Hz. The analogue network terminations are electrically isolated. The country-specific adaption is made by the operating software.

■ Calling line identification presentation (CLIP), the consultation feature by means of a flash key and/or earthing key and the transmission of call data charges are not supported.

■ The MT+A1-4 interface card runs on software acquired from the system. After the card has been installed it will automatically load the required software.

■ No settings need to be made on the MT+A1-4 interface card.

Pin Assignment

For information on the a/b interface pin assignment, refer to

a/b Ports starting on page 48.

Indicators

There are four LEDs on the front of the MT+A1-4 interface card.

Modules

MT+A1-4

MS+A1-4

MT+A1-4: LEDs

The LEDs indicate the following:

LED 1: Constantly yellow

LED 2: Constantly green

Flashing yellow

Constantly red

LED 3: –

LED 4: –

At least one connection established through the interface card is active.

The interface card is operational; the slot has been activated (flickering is normal).

The interface card is ready, but the slot has not been activated or the interface card has not been configured yet.

New software is being loaded onto the interface card. If the LED lights up red for an extended period of time, there may be a fault.

Not used

Operational Information

The MT+A1-4 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deactivated in the Configurator in the web console (see

Installing Interface Cards starting on page 31).

Configuration

8. Configuration

Configuration and programming of the OpenCom 510 is performed by the Configurator , a special software application integrated into the system. The Configurator is operated via the Web console, which can be run on any PC connected to the OpenCom 510.

The OpenCom 510 Web console

Using the Web console, you can:

■ perform the initial configuration of the OpenCom 510,

■ configure users of the OpenCom 510 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 510 telephone book.

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

Loading the Online Help starting on page 87).

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 510 via the

Ethernet port. 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 510 and call up the Configurator from there.

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

IP address is always168.99.254 in its factory settings.

8.1

Brief Guide to Initial Configuration

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

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

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

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 84).

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

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

255.255.255.0, confirm with OK and Close .

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.

Configuration Brief Guide to Initial Configuration

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

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 .

Configuration Configuring the OpenCom 510

8.2

Configuring the OpenCom 510

8.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 510) with their names, departments, and the internal call numbers you want to allocate to them

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

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

Note: Use the

Configuration Guide starting on page 192. This

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

8.2.2 Starting the Web Console

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

If the configuration PC gets its IP address automatically from the OpenCom 510 or if the OpenCom 510 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 Configuration: LAN menu).

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

Configuration Configuring the OpenCom 510

OpenCom 510: log-on dialogue box

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

- user name: “Administrator”

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

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 510 and the users.

OpenCom 510: dialogue box for initial access

Configuration Configuring the OpenCom 510

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.

Confirm your input with Apply .

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.

8.2.3 Loading the Online Help

The online help can now be loaded in the Configurator:

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

Help and click on Browse .

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

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/.

8.2.4 Finishing the Configuration

When you have completed all the settings in the Configurator , you must save the configuration (see also

Saving and Loading the Configuration on page 91 ).

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

8.2.5 Preconfiguration

Configuration of the OpenCom 510 can be prepared at your Aastra DeTeWe Customer Service Centre or by an authorised DeTeWe dealer. For this purpose, a

OpenCom 510 installed here is programmed with the customer data (e.g. user

Configuration Configuring the OpenCom 510 data, call distribution schemes, cord-bound terminals). This data is stored and then loaded into the OpenCom 510 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 510 Internet functions, first ask the responsible system administrator for details of the customer’s LAN prerequisites.

8.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.

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

8.2.7 Remote Configuration

The OpenCom 510 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 510 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 510 as an administrator:

■ User name: “Administrator”

■ Password: [administrator password]

Configuration Configuring the OpenCom 510

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 #

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

Note: During remote configuration, the OpenCom 510 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 510 settings (with the exception of the system PIN) can be edited or updated. New software versions of the OpenCom 510 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 94, where interaction between the OpenCom 510 and a LAN is

explained.

Configuration Configuring the OpenCom 510

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:

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

They open the Configurator .

A message shows which user is currently configuring the system.

The administrator clicks on the Take over config rights button.

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

8.2.8 Codes for IP Configuration

The IP configuration of the OpenCom 510 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 510 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) #

Configuration Configuring the OpenCom 510

Example

Enter: H*1830000*192*168

*99*254#

If required, initiate a system restart with this procedure:

Trigger Restart

H * 1 8 5 Z (system PIN) #

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

“0000”.

8.2.9 Saving and Loading the Configuration

Configurations are saved in a file archive and can be loaded to the OpenCom 510 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

■ LCR tables

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

SYS Configuration: Data backup .

8.2.10 Receiving System Messages as E-Mail

Important events and errors are kept by the OpenCom 510 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

Configuration Configuring the OpenCom 510 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 Configurator , NET Configuration: E-Mail Access .

8.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 510 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 Configuration on page 83.

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

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

SYS Configuration: Firmware .

8.2.12 Resetting the System Data

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

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 91 and to the

Web console online help.

Proceed as follows:

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

Click on Restart with Defaults .

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

Configuration Configuring the OpenCom 510

8.2.13 Generating Your Own MoH Files

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

OpenCom 510 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 510.

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 510 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.

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 510 can be used free of charge.

Configuration Examples OpenCom 510 in Computer Networks

9. Configuration Examples

9.1

OpenCom 510 in Computer Networks

One of the outstanding features of the OpenCom 510 is the integration of telephony and computer networks. Connect the OpenCom 510 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 510 Configurator

■ call charge administration

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

■ the OpenCom 510 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 510 can be used as an Internet access server. RAS access can also be implemented using the OpenCom 510, 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 510 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 .

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 510 Functions

OpenCom 510 functions as DHCP and

DNS server

System Administrator must assign IP address and DNS name for

OpenCom 510

Special case when integrating the

OpenCom 510 in a LAN; settings in the

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

9.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 510 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

Configuration Examples OpenCom 510 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.

9.3

OpenCom 510 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)

OpenCom

(DHCP, RAS, int. DNS, Internet)

Net

Ext.

PC 1 PC 2

Net Hub Net

The OpenCom 510 in a serverless LAN

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

Configuration Examples OpenCom 510 in a Serverless LAN the OpenCom 510 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

OpenCom 510 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 510 network features.

9.3.1 DNS Name Resolution

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

OpenCom 510. If you type the string “host.domain” into your browser, a DNS request is sent to the OpenCom 510 IP address. The OpenCom 510 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 510. The

OpenCom 510 is not visible in the network environment.

9.3.2 Internet Access

If access to an ISP has been configured on the OpenCom 510, the OpenCom 510 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 510 is configured as a DNS server and default gateway. The workstation therefore sends its Internet connection request to the

OpenCom 510.

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 510 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.

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

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

9.3.3 RAS Access

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

ISDN card.

The necessary IP settings are transmitted by the OpenCom 510 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.

9.4

OpenCom 510 in a LAN with an IP-enabled

Server

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

OpenCom 510 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 510 is to handle in the LAN.

Configuration Examples

ISP

(DNS)

OpenCom

Net S

int

Server

(DHCP, RAS, int. DNS,

Internet)

Net

OpenCom 510 in a LAN with an IP-enabled Server

PC 1 PC 2 Ext.

Net Hub Net

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

In many cases, an IP-enabled server configures the IP settings via DHCP for all workstations. In networks in which the IP settings are made manually, you have to enter the corresponding IP settings in the OpenCom 510 Configurator ( NET Configuration: LAN menu). Additionally you should change the DHCP server to static address assignment (in the NET Configuration : LAN : DHCP Server menu) to enable the OpenCom 510, for example to configure connected VoIP system telephones. In certain cases you have to restrict the DHCP function of the IP-enabled server to ignore the MAC addresses for such terminals.

9.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 510. For further information, refer to the server documentation.

Note: To access the OpenCom 510 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.

9.4.2 Internet Access

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

IP-enabled server. To do this, you must enter the OpenCom 510 IP address on the server as the default gateway. In addition, you must edit the internal DNS server

Configuration Examples OpenCom 510 in a LAN with an IP-enabled Server configuration so that the resolution of external DNS names is forwarded to the

OpenCom 510.

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

There are two different ways of suitably configuring the internal DNS server. You can enter the OpenCom 510 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)

OpenCom

(Internet)

Net S

int

Server

(DHCP, RAS, int. DNS)

Net

PC 1 PC 2 Ext.

Net Hub Net

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

9.4.3 RAS Access

In a LAN with an IP-enabled server you can also enable external computers to dial in via the OpenCom 510. 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 .

100

Configuration Examples

ISP

(DNS)

OpenCom

(RAS, Internet)

Net

Server

(DHCP, int. DNS)

Net

Branch Link

PC 1 PC 2 Ext.

Net Hub Net

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

The user account administered by the OpenCom 510, 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 510 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 510 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.

9.5

Branch Link

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

To do this, you configure two OpenCom 510 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 510 systems, change the prescribed address range for the LAN.

101

Configuration Examples

OpenCom

(IP=192.168.99.254,

Net=192.168.99.0)

Net S

Useful Information on Internet Access

OpenCom

(IP=192.168.11.254,

Net=192.168.11.0)

Net

PC 1 PC 2 PC 1 PC 2

Net Hub Net Net Hub Net

The OpenCom 510 in a LAN-to-LAN link

In the Configurator , NET Configuration: Branch menu you can configure the dial-in settings. The OpenCom 510 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.

9.6

Useful Information on Internet Access

9.6.1 Costs

The OpenCom 510 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.

102

Configuration Examples Useful Information on Internet Access

Examples of such programs are the Microsoft

operating system, various multimedia programs such as Realplayer

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 in the NET Configuration : WAN : [Provider] menu on the web console.

9.6.2 Using the Web

A Web browser not only enables you to use the OpenCom 510 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 510 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 510 automatically releases the connection to the Internet after a certain, specifiable duration.

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

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

9.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 510 you can set up one or more e-mail accounts for every user account configured on the OpenCom 510. These e-mail accounts are then checked at regular intervals.

If there are new e-mails in an e-mail account, and the OpenCom 510 has been configured for this function, the user specified in the OpenCom 510 user account is

103

Configuration Examples Useful Information on Internet Access 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.

9.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 or SIP.

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

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

The OpenCom 510 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”).

Depending on the internet telephony protocol (VoIP, SIP) the required NAT extension (“Full Cone NAT”) or RTP-Proxy is activated on the Media Gateway Card.

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.

104

Voice over IP (VoIP)

10. 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. Voice and service quality via Internet is often indeterminable, because you are dependent on the communication lines 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 510 gives users all the features of system telephony through its use of an IP-based protocol. Furthermore, the standardised SIP protocol can also be used on the intranet. The control of the data connections used makes it possible to define exactly the voice and service quality.

VoIP telephony over the Internet using the OpenCom 510 provides you with the following options (see also

SIP Telephony starting on page 117):

■ 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

VoIP Telephony via intranet with the OpenCom 510 offers the following possibilities:

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

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

105

Voice over IP (VoIP) Quick start

■ 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

■

Operation of SIP-capable telephony software (see also SIP Telephony starting on page 117)

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

PBX Networking starting on page 149)

■ Setting up a DECToverIP network lets you use existing Ethernet cabling to set up a DECT network. The special DECT base stations designed for this purpose,

can be handled using OpenCom 510’s Web interface (see DECToverIP® starting on page 133).

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 125). You should

therefore always plan the use of VoIP in the Intranet together with your network administrator. In order to avoid possible conflicts please also note the information under

Fundamentals starting on page 110.

10.1

Quick start

10.1.1 IP System Telephony

VoIP system telephony can be quickly and easily set up using OpenCom 510.

Install a Media Gateway card MG+ETH1-1Call up the Configurator and go to the page PBX Configuration : Ports : Slots . Click on the corresponding slot. Under

Configured, select MGC VoIP.

Optional: enter an IP address from the

OpenCom 510 IP network which is not being used, such as 192.168.99.253 under IP Address Configured . Click on Apply .

Go to the page PBX Configuration : Devices : VoIP Telephone and click on

New . Enter the MAC Address printed on the underside of the IP system tele-

106

Voice over IP (VoIP) Quick start phone. Select the Type and enter an internal Number . Option: enter an IP address from the OpenCom 510 IP network which is not being used. Click on

Apply .

Connect the IP system telephone’s LAN connection to the LAN and connect the phone to the mains power using the power supply unit provided.

Once your IP system telephone has been successfully started, you can set it up and use as you would any other U pn

-based system telephone.

Note: Use a shielded CAT-5 Ethernet cable (STP cable,

Shielded Twisted Pair cable) to connect an IP telephone to a

Local Area Network (LAN).

10.1.2 External SIP Line

If your OpenCom 510 has access to the Internet, you can an easily and quickly set up an SIP line.

Install a Media Gateway card (see

MG+ETH1-1 starting on page 115).

Call up the Configurator and go to the page PBX Configuration : Ports : Slots .

Click on the corresponding slot. Under Configured, select MGC VoIP.

Optional: enter an IP address from the OpenCom 510 IP network which is not being used, such as 192.168.99.253 under IP Address Configured . Click on Apply .

Request at least one SIP account from an SIP provider.

Call up the Configurator and go to the page PBX Configuration : SIP Trunks :

SIP Provider . If your SIP provider is not listed, click on New . Otherwise select the preconfigured SIP provider. Enter the Name , Domain (DNS name of the SIP

ID) and the Phone Number . Enter the SIP server’s IP address under Proxy/Registrar and an IP address under STUN Server and STUN Port where necessary.

You can obtain more information on this from your SIP provider. Click on

Apply .

Go to the page PBX Configuration : SIP Trunks : SIP Accounts and click on

New . Activate the Status and enter a name for the account under Name . Select the SIP Provider . Enter the relevant account information under User name and Password . Click on Apply .

107

Voice over IP (VoIP) Quick start

Call up the PBX Configuration : Trunks : Route : New page once again. Enter

“SIP”, for example, under Name , under Code the number “8” and select the SIP account that was just configured for Bundle/SIP trunks 1 . The SIP account is now available with the dialling prefix “8”. To use the SIP account by default, call up the page PBX Configuration: Trunks: Route and select the route External trunk. Under Bundle/SIP trunks 1, select the SIP account you have just set up.

Click on Apply .

Note: The PBX Configuration : Trunks menu page is only displayed if you activate the Level : Expert option on the opening page of the Configurator .

Check that the SIP connection is active on the Systeminfo : PBX : Trunks page.

Also check the SIP licence count on the SYS Configuration: Licences page.

Check the functionality by making an external call. You should assign the relevant external number of the SIP account to the internal numbers on the page PBX Configuration: Call distribution: Incoming.

10.1.3 Internal SIP telephony

SIP telephones connected via LAN or SIP telephony software on LAN workstation computers can also be operated with the OpenCom 510.

Install a Media Gateway card (see

MG+ETH1-1 starting on page 115).

Call up the Configurator and go to the page PBX Configuration : Ports : Slots .

Click on the corresponding slot. Under Configured, select MGC VoIP.

Optional: enter an IP address from the OpenCom 510 IP network which is not being used, such as 192.168.99.253 under IP Address Configured . Click on Apply .

Call up the PBX Configuration : Devices : VoIP Phones page in the Configurator.

Tip: Click on New . Select the “SIP” option under internal Phone No.

Click on Apply .

Type and enter an

Call up the User Manager : User page. Assign the new internal call number to a user. Internal SIP telephones can also be operated by users without code words. If you do not assign the call number of the SIP telephone to a user, you can only configure a “Guest” user account on the SIP telephone.

108

Voice over IP (VoIP) Quick start

An internal SIP telephone can be operated with a dynamically assigned IP address. If the SIP telephone has its own Web interface, for example, a static IP address can be practical. Click on New on the NET Configuration : LAN : DHCP

Server page. Enter the MAC address of the SIP telephone and an available IP address and click on Apply .

Configure the SIP telephone or the SIP telephony software. Please also refer to the configuration help on the PBX Configuration: Devices: VoIP Phones page. For the desired call number, click on (Help) and select a suitable help page under Type .

A configuration dialogue of SIP telephony software

You can only conduct a certain number of telephone calls simultaneously with internal SIP telephones. The number licenced can be viewed on the SYS Configuration : Licences page. The number of SIP telephones currently licenced can be determined on the System Info : PBX : SIP phones page. If you click on

Reset licences , the available licences will be reassigned with the next incoming or outgoing calls.

109

Voice over IP (VoIP) Fundamentals

10.2

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.

10.2.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.

10.2.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.

110

Voice over IP (VoIP) Fundamentals

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)

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

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

10.2.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

Level Voice Comprehensibility

1 Very Good

2 Good

Comparable to

ISDN

DECT

111

Voice over IP (VoIP) Fundamentals

Quality Levels for Voice Transmission with VoIP

Level Voice Comprehensibility

> 4

Satisfactory

Limited

Unacceptable

Comparable to

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:

■ 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.

112

Voice over IP (VoIP) Fundamentals

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

10.2.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 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 510 uses a TOS byte (“Type of Service”) value of 0xB8 for IP packets with VoIP data. This requests

113

Voice over IP (VoIP) Fundamentals

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

10.2.5 Call set-up

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

made between an IP telephone and OpenCom 510 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.

10.2.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

■ 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

114

Voice over IP (VoIP) Media Gateway (MGW) ports will then be made using uncompressed or ISDN connections where possible.

10.3

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.

Using the OpenCom 510, the Media Gateway is provided using at least one

MG+ETH1-1 interface card.

10.3.1 MG+ETH1-1

Field of Application

The MG+ETH1-1 interface card provides 16 Media Gateway channels for VoIP.

The MG+ETH1-1 interface card can be installed in any of the OpenCom 510’s slots

interface cards can be operated.

Technical Data

■ OpenCom 510 can be connected to the LAN via the ethernet port (10/

100 Mbit/s).

■ The interface card supports: all codecs used by VoIP telephones, silence detection, echo suppression and DTMF tone detection.

■ The interface card can not be used in a slave system.

■ The interface card acquires its software from the system. After the card has been installed it will automatically load the required software.

115

Voice over IP (VoIP) Media Gateway (MGW)

■ No settings need to be made on the interface card.

Pin Assignment

The ethernet port’s pin assignment is designed for a direct connection, via a RJ45 patch cable, to an ethernet Switch. You will need a cross-link cable (“Cross-over

Cable”) for connection to a PC.

Indicators

There are four LEDs on the front of the MG+ETH1-1 interface card.

MG+ETH1-1

MG+ETH1-1: LEDs

The LEDs have the following meaning:

LED 1: Constantly yellow

LED 2: Constantly green

Flashing yellow

Constantly red

LED 3: –

LED 4: Constantly green

At least one call is being conducted via the interface card.

The interface card is operational; the slot has been activated (flickering is normal).

The interface card is ready, but the slot has not been activated or the interface card has not yet been configured.

New software is being loaded onto the interface card. If the LED lights up red for an extended period of time, there may be a fault.

Not used.

An ethernet connection is available.

Operational Information

The MG+ETH1-1 interface card can be exchanged during operation; the system does not need to be shut down or powered down. The slot must first be disabled

116

Voice over IP (VoIP) SIP Telephony in the Configurator

in the Web console (see also Installing Interface Cards starting on page 31).

Each MG+ETH1-1 interface card requires its own IP address. This can either be assigned statically or obtained via DHCP.

In the Configurator , open the PBX Configuration: Ports: Slots page.

Click on the slot number in the table row containing the desired interface card.

Enter the desired IP address in the IP address configured field. Enter “0.0.0.0” to obtain an IP address via DHCP.

Confirm with Apply .

The configuration page displays the MG+ETH1-1 interface card’s MAC address. You will need this for the static assignment of an IP address via a DHCP server.

10.4

SIP Telephony

The SIP Internet (Session Initiation Protocol) protocol provides you with a low-cost, standardised option for telephoning via IP-based networks. OpenCom 510 enables you to use external SIP telephone connections (“SIP trunk lines”).Furthermore, internal SIP subscribers, SIP telephones or SIP telephony software are also supported.

10.4.1 External SIP connections

The PBX Configuration : 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

117

Voice over IP (VoIP) SIP Telephony 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 110 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 510 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.

■ 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, incoming RTP calls often fail to get past the Firewall or NAT configuration of the Internet gateway product used. Do not use OpenCom 510 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

118

Voice over IP (VoIP) SIP Telephony information is available for NAT on an incoming RTP connection.To avoid this problem, the IP address of a workstation 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 510, 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 154).

You can configure SIP connections in the Configurator on the pages

PBX Configuration : SIP trunks : accounts and PBX Configuration : SIP trunks : 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.

10.4.2 Internal SIP subscribers

The OpenCom 510 becomes available as the SIP server for internal SIP subscriber telephony switching services. SIP telephones connected via LAN or SIP programmes installed on workstation computers can thus establish connections to all other devices or trunks connected to the OpenCom 510. For operation as a SIP server a

MG+ETH1-1

is required. licence assignment

The number of possible SIP subscribers is determined by the number of licences purchased. In order to provide you with the greatest possible flexibility regarding usage of available licences, licence assignment is dynamic via the “Floating licence”. Using a user/code word combination (“SIP log on”) you can have several

SIP subscribers under the same call number. Only every new SIP log-on occupies a new licence. The technical log-on process of a SIP subscriber with a valid user name and correct code word is always successful. Only when a connection is established is there an attempt made to occupy a licence under the SIP log-on. If

119

Voice over IP (VoIP) SIP Telephony all licences are occupied currently, the SIP subscriber can only make emergency calls.

Note: If the technical log-on is not successful due to an incorrect user name or incorrect code word, the SIP subscriber cannot establish any connections – no emergency calls either.

When a SIP subscriber logs off, when terminating the programme, for example, the associated licence will become available immediately. A licence is also made available when a SIP subscriber’s regular status query is not conducted. The internal clock for automatic log-out is determined by the Profile assigned under

PBX Configuration : Devices : VoIP Phones . The ( Keepalive ) internal clock setting is located on the PBX Configuration : System : VoIP profile page.

Detailed information on the current licence assignment and on logged-on SIP subscribers is located on the System Info : PBX : SIP phones page. This page is where you can reset licence assignment at any time by clicking on Reset licences .

Technical Notes

The names of settings for the various SIP telephones or SIP programmes are not uniform unfortunately. Please refer to the (Help) on the PBX Configuration :

Devices : VoIP Phones page and the following notes when configuring SIP subscribers:

■ The “REGISTER” SIP message must be sent to the IP address of the

OpenCom 510 using the 5060 destination port. For SIP subscribers, this setting is frequently located under “SIP Server” or “SIP Settings” with the terms

“Domain”, “Server IP” and “Server Port”.

■ The “REGISTER” SIP message must contain a valid user name and the appropriate code word (the User name and Password fields in the Configurator under User Manager : User ). For SIP subscribers, this setting is frequently located under “SIP User Settings” or “SIP Account” with the terms “Authorization User” and “Password”.

■ The “REGISTER” SIP message also contains a SIP-URI in the spelling for e-mail addresses, for example

"Displayname" <sip:[email protected]>

The text portion of the SIP-URI (“Display Name”) is not evaluated at log-on from the OpenCom 510. The series of characters before “@” is the “User Name” or

“SIP Username”. The internal call number of the user must always be used here

(the Ph.No. field in the Configurator under User Manager : User ). The series of

120

Voice over IP (VoIP) SIP Telephony characters after “@” is the “Domain Name” or the “SIP Domain”. The IP address of the OpenCom 510 must always be used here.

■ A STUN server (Simple Traversal of UDP over NAT) or a SIP proxy is not required because internal SIP subscribers on the LAN are directly connected to the

OpenCom 510. Switch these functions off if possible.

■ The “G.711 µ-law” codec (North America, Japan) is not supported. If the SIP telephone offers such a setting, you should switch on the “G.711 A-law” (Europe) instead.

Features

SIP subscribers can establish connections to all other terminals and trunks. The SIP protocol generally works with block dialling. This is why the selected call number is only activated after an internal clock has expired or activated immediately via the hash key (“#”) when dialling. This is why code number procedures without the hash key and code number procedures with a concluding hash key can be used.

An overview of code number procedures that can be used is located in the Configurator on the System Info : Codes page .

Activate “SIP phones”. Please also note the corresponding information in the “OpenCom 100, Operation on Standard Terminals”user guide.

Alongside code number procedures, SIP subscribers can also use a series of functional features realized via the SIP protocol. The OpenCom 510 is the ending for all

SIP connections as opposed to what is usually the case on the Internet. This enables SIP subscribers to use OpenCom 510 features. Direct data exchange is thus not possible between two SIP subscribers. The following table shows the possible features.

Features Notes

Incoming and outgoing calls with call number display (CLIP)

A SIP telephone requires a call number display for

CLIP.

Parallel connection of multiple SIP subscribers

Enquiry, toggling, call waiting, three-way conference, reject

SIP subscribers must be logged on under the same user identification.

Operation or feature must be available on the SIP telephone or in the SIP software.

121

Voice over IP (VoIP) VoIP System Telephones

Features

Call transfer

Blind Transfer

Keypad as “INFO” message

Notes before and during a call; operation must be available.

SIP only: forwarding an incoming call without accepting the call; feature must be supported by SIP telephone or by the SIP software.

DTMF tones cannot be securely transferred “in band” via compression codecs. Digital “out band” transferral as “INFO” SIP message is supported. This feature must be available and activated on a SIP telephone or in the SIP software.

10.5

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 telephone using Windows 2000/XP executable software (see

OpenPhone IPC starting on page 130). 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.

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

122

Voice over IP (VoIP) VoIP System Telephones

■ 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 workstation 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

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.

123

Voice over IP (VoIP) VoIP System Telephones

10.5.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 510’s DHCP server so that the start procedure can be concluded without problems. To register a new

VoIP system telephone, proceed as follows:

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.

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

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

Confirm with Apply .

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.

10.5.3 LAN DHCP Server

If the LAN already uses a DHCP server to configure workstation computers, there are various options for correctly responding to VoIP system telephones’ DHCP,

BOOTP and TFTP requests. A comparatively simple approach is described here.

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;

124

Voice over IP (VoIP) VoIP System Telephones

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.

Configure a fixed IP address for the OpenCom 510. To do this, call up the Configurator and open the NET Configuration: LAN page. Click on the Change button.

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 .

Configure the OpenCom 510’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.

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

DHCP Server page is re-displayed.

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

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 510 and all connected VoIP system telephones.

10.5.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 510’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.

125

Voice over IP (VoIP) VoIP System Telephones

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.

The file name determined by the telephone type.

Telephone type

OpenPhone 63 IP

OpenPhone 65 IP

OpenPhone 73 IP

File name

/ram/ip_tel/opi63.cnt

/ram/ip_tel/opi65.cnt

/ram/ip_tel/opi7x.cnt

OpenPhone 75 IP /ram/ip_tel/opi7x.cnt

RFP 31/32/33/34/41/42 /ram/ip_tel/ip_rfp.cnt

After the VoIP system telephone has been connected to the mains power supply, the start procedure is as follows:

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.

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.

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.

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.

The VoIP system telephone creates a TCP connection to the supplied IPaddress/port-number combination and sends a registration query. The

126

Voice over IP (VoIP) VoIP System Telephones

OpenCom 510 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.

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.

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.

10.5.5 Local Configuration

In addition to automatic configuration via BOOTP/DHCP, it is possible to manually configure an OpenPhone 73 IP or an OpenPhone 75 IP. This can make sense, for example, when you wish to connect a VoIP system telephone at a distant location via router. This local configuration is saved permanently in the non-volatile memory of the VoIP system telephone. To change the local configuration, use an additional programme, the Java-based “IP Phone Configurator”.

Note: Java programmes can be run on all common operating systems. To execute Java-based programmes, you must install a suitable Java runtime environment on your operating system (JRE). This can be downloaded under the following web address: http://www.java.com/.

127

Voice over IP (VoIP) VoIP System Telephones

The “IP Phone Configurator” can be started directly from the Product CD. Start

Windows Explorer. Navigate to the Product CD. Double-click the “Aastra-

DeTeWe\IpPhoneConfigurator.jar” file.

The “IP Phone Configurator” dialogue opens. Select the desired language setting (“English” or “German”)from the drop-down menu.

Enter the network address of the VoIP system telephone. You have two connection types to choose from under Connection to IP Phone :

- Deactivate the IP Phone address option to establish a broadcast connection via “UDP-Broadcast”. You have to select this type of connection if the VoIP system telephone has not yet been assigned an IP address. IP broadcasts cannot be transmitted via router. The VoIP system telephone thus has to be directly connected to your PC via a hub or via a switch.

- Activate the IP Phone address option to establish a point-to-point connection via “UDP-Unicast”. Enter the IP address of the VoIP system telephone

128

Voice over IP (VoIP) VoIP System Telephones into the entry field. You can select this type of connection if the VoIP system telephone has already been assigned an IP address.

Enter the MAC address of the VoIP system telephone. You will find the MAC address on the underside of the device. Click on List configuration . The status bar at the bottom edge of the programme window displays “list OK”.

Change the desired settings under Configuration of the IP Phone . Click on

Reset configuration to activate the standard settings for all entry fields.

Click on the Send configuration command to transfer the currently shown configuration to the VoIP system telephone. The status bar at the bottom edge of the programme window displays “send OK”.

Note: The VoIP system telephone receives the configuration and sends a response. The new configuration is only saved and activated once this has happened. This can result in the

“IP Phone Configurator” not receiving the response of the

VoIP system telephone.

Please note: If you are operating multiple network cards with active IP configuration in your PC, this may mean that the loading of configuration data fails. First you deactivate additional network cards or use a point-to-point connection. Sending configuration data with a broadcast connection functions even without a response from the VoIP system telephone.

You can implement the following settings:

IP parameter locally configured : Select the yes option to activate manual IP address configuration. Select the no option to activate automatic IP address configuration via BOOTP/DHCP.

IP address and Netmask : Enter an available IP address and the network mask to be used by the VoIP system telephone.

TFTP server IP address and TFTP server filename : Enter the IP address and the complete file name for the operating software of the VoIP system telephone (see

table on page 126).

Registration IP address and Registration port : This is where you usually enter the IP address of the OpenCom 510 and the port number 8100.

129

Voice over IP (VoIP) OpenPhone IPC

Default gateway : Click on the Add parameter command to have this optional entry field displayed. Then enter the IP address of the router (“Default Gateway”).

Click on the Delete button to remove the optional parameter.

SYSLOGD : For monitoring purposes, VoIP system telephone messages can be sent to a Syslog server. Activate the yes option and configure the SYSLOGD IP address and SYSLOGD port settings to activate this function.

VLAN : To improve transmission security or to enforce security guidelines, PC data transmission and VoIP data transmission can be separated using this method.

Activate the yes option and enter the desired IP Phone VLAN ID for the VoIP data transmission. Enter a value ranging from 1-4094. Data will always be transmitted without a VLAN tag at the VoIP system telephone’s PC access. If you activate the yes option for PC traffic tagged on LAN interface , PC data will be labelled with the PC VLAN ID at the LAN access. Please note that to change the VLAN settings, the VoIP system telephone has to be restarted.

10.6

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 workstation computers, the

OpenPhone IPC includes the following features:

130

Voice over IP (VoIP) OpenPhone IPC

■ 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 workstation computer requires a full-duplex-enabled sound card as well as a suitable headset for audio recording and playback.

You will not need a licence to install OpenPhone IPC but you will require a licence to operate it with the OpenCom 510. Unit licences, enabling the simultaneous operation of a certain number of OpenPhone IPCs, are available.

The licences are activated in the OpenCom 510’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 Aastra

DeTeWe representative if you wish to purchase a permanent licence. Licences can be combined. Each licence can be activated only once.

10.6.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.

10.6.2 Configuration

Analogue to the VoIP system telephones, the OpenPhone IPC creates multiple IP connections to the OpenCom 510. When you start the program for the first time, the Options dialogue is automatically opened. Here you must configure the following values:

131

Voice over IP (VoIP) OpenPhone IPC

Enter in the VoIP IP Address field the OpenCom 510’s IP address.

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.

Confirm with OK .

Notes

VoIP system telephony requires an active IP connection to a workstation computer. If a Firewall is installed for your workstation computer, you may need to explicitly allow this connection.

If you log on to the workstation 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 510 via

TFTP. where necessary

132

DECToverIP

Properties

11. DECToverIP

®

In order to achieve optimal network coverage, a DECT network with several DECT base stations can be operated. A DECT network is comprised of DECT terminals connected with the next respective base station (network cell). For users of a DECT terminal, the handover from DECT base station to base station is completely transparent. Even during a conversation, users are switched from one network cell to the next without any interruption. Administration of DECT terminals is done centrally via the OpenCom 510 Configurator in the PBX Configuration : Devices :

DECT Phones menu.

Note: DECToverIP® is a registered trademark of

Aastra DeTeWe GmbH.

11.1

Properties

11.1.1 DECT base stations

DECT base stations can be connected to the OpenCom 510 via U pn

accesses or via network (TCP/IP). These DECT base stations are available for the type of access selected:

■ RFP 22: Access via U pn

with lines up to 1000 metres in length; integrated antennas; 4 voice channels (8 when using 2 U pn

accesses)

■ RFP 24: like the RFP 22; mounted outside enclosed areas (IP55); external antennas

Note: The newer DECT base stations RFP 22 and RFP 24 can be simultaneously operated with the older DECT base stations, RFP 21 and RFP 23. Fax transmissions (group 3 with

ECM) and SARI (roaming with Secondary Access Rights Identification Broadcasts) can be done using the newer DECT base stations. Data transmission via DECT is not available with the newer DECT base stations.

Note: The DECT base stations RFP 32, RFP 34 and RFP 42 support the DECT encryption function. This feature is however, only available if all the DECT base stations support it.

133

DECToverIP

Properties

■ RFP 32: Access via shielded CAT5 Ethernet cable (STP cable, Shielded Twisted

Pair cable) with up to 100 metres of cable from the last Ethernet switch, integrated antennas; 8 voice channels

■ RFP 34: like the RFP 32; mounted outside enclosed areas (IP55); external antennas

■ RFP 42: Access via shielded CAT5 Ethernet cable (STP cable, Shielded Twisted

Pair cable); offers simultaneous function of a WLAN Access Point conforming with the IEEE 802.11b/g protocol; external antennas; 8 voice channels

Note: When started, the operating software for the DEC-

ToverIP base stations is transmitted via TFTP protocol from the OpenCom 510. The configuration for the start sequence is transmitted by the DHCP server of the OpenCom 510 to a

DECToverIP base station for the start sequence.

If VoIP telephony is already being used, Ethernet cable access makes good sense.

Transmission of telephony signalling and voice data via TCP/IP also offers usage of existing network infrastructure and an increase in range using suitable methods.

VPN connections, for example, can be used for data links to provide service to remote or hard-to-reach locations.

11.1.2 Features

All DECToverIP base stations can be connected to a CAT5 Ethernet cable with a 10/

100 Base T. Power is supplied either via Power-over-LAN (IEEE 802.3af ) or via an additional power supply unit.

Please note: The WLAN function of the RFP 42 is activated when connected to the 100 Base T.

DECT terminals offer all system telephony features. DECT telephones supporting the GAP standard can also be operated. Transparent GAP device handovers are supported. DECT encryption of calls can be deactivated for the RFP 32, RFP 34 and

RFP 42 if desired.

VoIP audio communication between the DECToverIP base station and the

OpenCom 510 is made via the RTP/RTCP protocol. RTP voice data are directly converted into DECT voice data by the base station. The base stations support the

VoIP codecs G.711, (uncompressed) as well as G.729 and G.723 (compressed).

134

DECToverIP

Configuration

11.2

Configuration

One of the DECToverIP base stations that is installed assumes coordination and configuration of the DECToverIP functions (DECToverIP-Manager). Select a base station that has a dependable data link to the OpenCom 510. Go to the PBX Configuration : Devices : DECToverIP page in the Configurator . Click on New , to add a DECToverIP base station. Enter the MAC address of the base station that you have selected to be the DECToverIP-Manager. The MAC address of the base station is located on its type label. Enter an IP address for this base station. Confirm with

Apply . Now click Change , to determine the DECToverIP-Manager. In standard cases, leave the Mode in the “IP address from the system DHCP server” setting.

Select the desired DECToverIP base station with the MAC address (IP address) setting. Confirm with Apply .

If the OpenCom 510’s DHCP server is not configured for static address assignment, you first need to configure the IP address of the DECToverIP-Manager with the help of an additional programme (see

Local IP address configuration starting on page 141). Also change the

Mode setting on the PBX Configuration : Devices :

DECToverIP page to “IP address configured local” and enter there the configured

IP address for the DECToverIP-Manager. All other base stations can be operated using either a fixed IP address or an IP address assigned dynamically via DHCP.

Please refer to the information given in the chapter entitled

LAN DHCP Server starting on page 124.

Note: A base station cannot be operated as a DECToverIP

Manager and a WLAN-Access Point simultaneously.You should therefore use a DECToverIP base station which does not have WLAN function as your DECToverIP Manager.

Create a separate entry for each DECToverIP base station and for the DECToverIP

Manager on the PBX Configuration : Devices : DECToverIP page. You use these entries to determine the VoIP data compression (Profile).

135

DECToverIP

Configuration

Configurator: PBX Configuration: Devices: DECToverIP

User administration and set-up of DECT terminals is done in the Configurator of the OpenCom 510 as well.

The DECToverIP Manager offers a separate web user interface to manage the settings of devices with WLAN functions. Therefore at least one WLAN-RFP has to be configured. If everything is configured correctly, you will see the WLAN Config link. Login as the user “Administrator” with the currently set administrator’s password of the OpenCom 510.

11.2.1 Dual operation

Simultaneous operation of base stations via U pn

access and base stations via Ethernet access is possible with the OpenCom 510. Transparent handovers, for example, are only possible when between DECT base stations using the same access technology. When switching over to a DECT base station using different access technology, a DECT terminal automatically re-establishes a connection

(roaming).

Be sure to keep the PARK ID of your OpenCom 510 in mind. The PARK ID is displayed under System Info : Versions in the Configurator . If the PARK ID starts with

31, there may be an attempt at a handover between DECT base stations using different access technology. In this case, make sure that the signal areas of the DECT base stations using different access technology do not overlap. If the PARK ID starts with a different value (e. g. 30), prevention of unintentional handovers is effective.

136

DECToverIP

Configuration

11.2.2 Synchronisation

Transmissions of all DECT base stations at a single location must be synchronised in order that DECT terminals are able to receive multiple DECT base stations simultaneously. Synchronisation can be conducted via U pn

access. It cannot be conducted via an Ethernet/IP connection. DECToverIP base stations are thus synchronised via wireless connection.

When planning a larger sized DECT network, it is advisable to take the following points into consideration:

■ All DECToverIP base stations at a single location must be able to receive at least one, or even better, two neighbouring base stations. Synchronisation requires less signal strength than a voice connection does.

■ Synchronisation range is increased using multiple base stations. To decrease the probability of a connection breakdown, base stations should not be arranged in chain formation. The signal should be distributed with a network that is as extensive as possible and where each base station is supported by multiple synchronisation partners.

■ To re-synchronise, first wait for all current connections to be terminated.

You can operate a DECT network consisting of several remote locations

(“clusters”). A cluster is a number of DECT base stations that operate synchronously with each other. No handover is possible between DECT base stations from different clusters. You should configure a second cluster for DECT base stations of a second location.

11.2.3 Setting up the WLAN function

The RFP 42 DECToverIP base station provide the additional function of a Wireless

LAN Access Point (WLAN-AP). WLAN refers to data transfer by means of radio waves in accordance with the IEEE 802.11b/g standard. This standard enables a wireless connection to be made to an Ethernet network (LAN) using suitably equipped user terminals. Data transfer via radio waves is very fast. Depending on the conditions of the operating environment, it can reach speeds of up to 54Mbit/ s (gross).

WLAN settings are configured centrally for all Access Points using a separate Web configurator, which can be found at the IP address of the DECToverIP Manager

137

DECToverIP

Configuration

(OMM, OpenMobility Manager). You can reach this address by entering the IP address of the DECToverIP Manager directly into the address bar of your Web

Browser. Alternatively, you can also go to the Configurator , to the page PBX Configuration : Devices : DECToverIP and click on the WLAN Config. button. Log in under the User Name “Administrator” and enter the same password as for the

OpenCom 510.

DECToverIP/OpenMobility Managers Login Page

The WLAN function and the function of the DECToverIP/OpenMobility Manager cannot be used simultaneously on the same DECToverIP base station, so you will always need at least two DECToverIP base stations. The WLAN settings are then made as follows:

Set up the existing DECToverIP base stations in theOpenCom 510’s Configurator . Go to the DECToverIP Manager’s Web Configurator.

On the WLAN Profiles page, configure at least one set of settings (see below under:

Setting up a WLAN profile

). Note down the password you have used

(“Pre-Shared Key”), so that you will be able to use it again later when setting up wireless user terminals or notebooks.

Assign the desired WLAN profile on the Radio Fixed Parts page. Click on spanner symbol ( ) on the left next to the relevant DECToverIP base station.

Under WLAN Settings select the number of the configured WLAN Profile .

Confirm your settings with OK . You can use one profile for multiple DECToverIP base stations.

You can now use the WLAN function of your WLAN-enabled DECToverIP base stations and set up the user terminals as required.

138

DECToverIP

Configuration

Setting up a WLAN profile

The WLAN function of the RFP 42 DECT base station also includes such rarelyrequired features as networks for large company premises or airports. In this guide we will, for the sake of brevity and clarity, describe only those features required for secure standard operation.

DECToverIP/OpenMobility Manager: WLAN Profiles

Use the following settings for standard operations.

General Settings

■ Select the desired WLAN Profile and activate the Profile Active option.

■ Enter a SSID (Service Set Identifier, wireless network identification) to identify a network. This network identification is transmitted at regular intervals, making it easier to find the networks you’re looking for, using the “View available wireless networks” function in Windows XP, for example.

■ For standard operation you should leave the following settings at their default values: VLAN Tag at 0 (Off ), Beacon Period at 100 ms, DTIM Period at 5, RTS

Threshold at 2347 (Off ), Fragmentation Threshold at 2346 (Off ), Maximum

Bitrate at 54 MBit/s, 802.11b/g Mode at “Mixed” and Interference Avoidance on “Off”.

139

DECToverIP

Configuration

Tip: If you are using only modern WLAN cards with 802.11g, you can further speed up data transfer by configuring the setting

802.11b/g Mode to “802.11g only”.

■ You can prevent the transmission of wireless network identification (SSID) with the Hidden SSID Mode setting. This will however make network identification difficult and does not generally increase data security, so it is preferable to leave this on the default setting of “Off”.

Security Settings

On no account should you use Open System or Wired Equivalent Privacy (WEP) settings , whether out of convenience or in order to avoid configuration problems, unless of course you want to start up an Internet Cafe!

■ Activate the Wifi Protected Access (WPA) option.

■ Under Type select the “WPA v.1”setting. If you are running the Microsoft

Windows XP operating system from ServicePack2 or higher on your computer, you can use the “WPA v.2” setting.

■ For standard operation select the Pre-Shared Key option. Enter a password in the Value input field and leave it set to Text . Use a password with the following characteristics:

– No words or names that can be found in a dictionary

– At least 8 characters long

You could also use the Generate button to generate a password. Some WLAN configuration software does not convert text into hexadecimal values as a standard procedure. If this is the case, go to the Hex Value setting and select the Generate button.

■ Leave the Cipher Length setting at 256 Bit and the Distribution Interval setting at 120 seconds. You will not usually need the settings for WME or for configuring Multiple SSIDs for standard operation.

Tip:

– It should also include numbers, a mixture of upper and lower case and special characters

If you are running an Internet-Cafe without using powerful encryption, you should, for the sake of your customers’ secu-

140

DECToverIP

Configuration rity, prevent them from being able to access each others’ computers. Activate the BSS Isolation option. You can also stop unpleasant guests from using the system with a MAC

Address Filter – but this will not hold up users who know about this function for long.

11.2.4 Configuring for a remote location

If you are using a DECToverIP base station in the same LAN as the OpenCom 510, the IP address configuration and software loading procedure which are run when a DECToverIP base station is started are handled by the OpenCom 510 using the

DHCP and TFTP protocols.

For the DHCP function to be available, the DECToverIP base station must be able to reach the OpenCom 510 via a “Broadcast”. In the case of a remote location this kind of access - via a VPN connection for example - will not be possible. As in the case of an IP system telephone, you will have to acquire the necessary system software for the DECToverIP base station with the help of a TFTP server.

Local IP address configuration

The IP address configuration can be set up as a “local configuration” with the help of an additional program.

Open the product CD and call up the “OpenMobility Configurator” Java program. Open Windows Explorer, go to the “Aastra-DeTeWe” directory and double-click on the OM_Configurator.jar” file.

Note: You need a Java runtime library to be able to run Java programs. If you don’t have one installed, you can install one by starting the “j2re-windows-i586-p.exe” installation program.

141

DECToverIP

Configuration

OpenMobility Configurator

Enter the MAC Address of the DECToverIP base station. The MAC address will be printed on the label on the DECToverIP base station’s casing. Click on List

Configuration .

The DECToverIP base station’s current configuration will be displayed.

Change the DECToverIP base station’s IP address configuration. Activate the

Use local configuration option and enter the required details into the IP

Address , Subnet , OMM IP Address and PBX IP Address input fields.

– IP Address : Static IP address of the DECToverIP base station

– Subnet : Network mask of the DECToverIP base station

– OMM IP address : IP address of the DECToverIP Manager. For the actual DEC-

ToverIP Manager simply repeat the entry from the IP address entry field.

– OMM Port; Leave the default setting on “16321”.

– PBX IP address : IP address of the OpenCom 510

– PBX Port : Leave the default setting on “8099”.

142

DECToverIP

Configuration

Under TFTP Server Address enter the IP address the operating software is to be downloaded from. This will usually be the OpenCom 510’s IP address. Leave the TFTP File Name setting on the default setting (“/ram/ip_tel/ip_rfp.cnt”).

For a remote location, the OpenCom 510’s LAN will usually be accessed via a

(VPN) router. Click on Add Parameter , select the option Router Addresses from the list, enter the router’s IP address under Router Addresses, and confirm by clicking on Add .

Click on Send Configuration to activate the desired IP address configuration.

143

PBX Cascading Variants of PBX Cascading

12. PBX Cascading

As requirements grow, the OpenCom 510 can be operated together with other

PBX installations. If you merely need a larger number of connections, it is easy to link a second PBX (PBX Cascading). If you want to operate the OpenCom 510 at several locations with different PBXs, this is possible by PBX Networking (see

page 149).

12.1

Variants of PBX Cascading

You can combine two PBXs in order to increase the number of terminals that can be connected. A master PBX and a slave PBX are connected to one another by means of a cable. The two PBXs essentially function like a single PBX with a higher number of ports. The master PBX controls the slave PBX. The following PBXs from the product family can be used for cascading:

Master system

OpenCom 510

Slave system

OpenCom 510

For the PBX Cascading you will need a licence. The licence agreement provides you with the necessary steps to activate this function.

12.2

Functionality of PBX Cascading

Cascaded PBXs must be connected by means of a twisted-pair lead with RJ45 plugs. All eight pins of the lead must be wired 1 to 1. Both voice and administration data are transferred via this lead. Connect the lead to the PCM ports of the two MC+1-3 central control modules of the PBXs. The shielded CAT-5 lead must not be longer than 50 centimetres.

Note: Owing to the very short permissible lead length, the two PBXs have to be stacked. It is not possible to place them side by side.

144

PBX Cascading

PBX 1 (Master) data lead (8 pins assigned, joined 1 to 1)

Putting a Cascaded PBX into Operation

BPX 2 (Slave)

Cascaded PBX system

12.3

Putting a Cascaded PBX into Operation

Proceed as follows to put a cascaded PBX system into operation:

If you want to cascade two OpenCom 510 PBXs, you will need to set the frame number using the DIP switches on the central control module.

To access the DIP switches, remove both central control modules (master and slave systems); proceed as described in

Installing the Central Control Module starting on page 29.

Set the DIP switches of both modules as follows:

DIP Switch Settings

Frame as Master

S1: open (switch set to “1”)

S2: open (switch set to “2”)

Frame as Slave

S1: closed (switch set to “ON”)

S2: open (switch set to “2”)

For the location of the DIP switches (S1and S2), refer to the illustration

MC+1-3:

Top view

Re-install the central control modules in the frames.

145

PBX Cascading Putting a Cascaded PBX into Operation

1 2

MC+1-3: Top view

Mount the slave system frame above or below the master system. Connect a system telephone to the slave system for a later performance check. Use the

U pn

1 terminal of an existing MS+UPN1-8 or MS+UPN2-8 interface card.

Back up the master system data. For further information, refer to the online help topic SYS Configuration: Data Backup . The backup procedure also stores the current configuration data to the CompactFlash memory card.

Switch off the master system if it is operating. Disconnect the module from the power supply by pulling out the mains plug.

Connect the two modules by means of a suitable cable as described above.

Power on the two PBXs. The order in which you do this does not matter.

In the PBX Configuration: Ports: Slots dialogue of the master system’s Configurator, click on Slave . Select the slave Type in the Slave: Change dialogue.

146

PBX Cascading Putting a Cascaded PBX into Operation

Please note: If you change the type of slave system later on, the port settings that have been made will be deleted.

The master system then initialises the slave system. This may involve transfer of firmware (operating software) from the master system to the slave system. This can take a few minutes.

Configure the system telephone connected to the slave system for testing purposes in the Configurator . In the PBX Configuration: Ports: Upn dialogue, click on one of the additionally displayed entries of the type Upn 1/m/n

(1: slave system, m: slot number, n: U pn

port number).

Note: Changes to the configuration while initialising the slave system may trigger error reports referring to the ongoing initialisation.

You can see that the initialisation has been completed from the display on the system telephone connected to the slave system.

12.3.1 Notes

Observe the following when operating a cascaded PBX system:

■ All U pn

, S

and a/b ports of the slave system interface cards can be used with appropriate telephones. All features of system telephones on U pn

ports are available without restriction.

■ The S

ports of the slave system can also be used for trunk lines or for PBX networking (see

PBX Networking starting on page 149).

■ It is not possible to operate a DECT base station on one of the U pn slave system.

ports of the

■ The ISDN-L1 reference clock signal is always transferred from the master to the slave system and must be acquired from an S

port –or preferably an S

port– on the master system. The master system therefore needs to be connected to at least one ISDN trunk line.

■ It is possible to operate an S

interface card of the type MS+S2M1-1 in the slave system. As the ISDN-L1reference clock signal supplied by an S

interface

147

PBX Cascading Putting a Cascaded PBX into Operation card is not precise enough, you will also need to operate an S

interface card in the master system.

■ The slave system cannot be addressed directly through a LAN. For configuration, always use the Web console of the master system.

■ To operate the slave system again normally, you must reset it to its factory set-

tings (refer to Resetting the System Data starting on page 92 and

DIP Switch Settings on page 145).

12.3.2 Licensing Information

A licence is required for certain additional OpenCom 510 program packages, for example for the internal voice-mail system called OpenVoice .

The following information is for customers who have already obtained licences for an OpenCom 510 and would like to cascade or network their existing system with another OpenCom 510.

PBX Networking

If you network two OpenCom 510 systems with each other, you needn't generate any new activation keys but can continue to use the corresponding functions on the existing OpenCom 510. The “disadvantage” of this alternative is that you have to administer a separate configuration on each OpenCom 510.

PBX Cascading

In the case of PBX cascading, the master system administers the overall configuration.

If you have already installed activation keys on an existing OpenCom, they have to be ported to the master system.

In this case, new activation keys for the use of additional program packages must be generated on the Aastra DeTeWe licence server

(http://lizenz.aastra-detewe.de). The licensing confirmation for the cascading contains all the information you need to carry out this procedure.

Note: You will need the serial numbers of both infocom systems for porting the activation keys. The serial numbers can be found in the Web console's Configurator , in the System

Info: Versions menu.

148

PBX Networking Connections

13. PBX Networking

OpenCom 510 provides all the features necessary for PBX networking. You need

PBX networking in the following cases:

■ To operate the OpenCom 510 as a subsidiary system on another PBX. This will also allow you to use the OpenCom 510 as a DECT server, for example.

■ To network the OpenCom 510 with an OpenCom 1000. In this way you can use the OpenCom 510 as a PBX for a branch office, for instance.

■ To network several OpenCom 510s into a PBX system.

■ To use flexible configuration possibilities of trunk lines for a OpenCom 510.

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 510 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.

13.1

Connections

Networking two or more TK systems means interconnecting them. The

OpenCom 510 allows you to use the following connections:

■ ISDN trunk lines

149

PBX Networking Connections

■ ISDN point-to-point connections (Q.SIG) on external S

ports or on the S

port

■ IP network connections (Q.SIG-IP)

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.

13.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.

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 154).

150

PBX Networking Connections

13.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.

Note: In the case of an S

line, it is also possible to determine for each useful channel which end can administer a channel (master = internally seized or slave = externally seized). On S

lines this setting is determined by “L3 master” for both B-channels.

13.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 S

PBX 3

PBX 2

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 510 and the setting L1 sync possible has been activated, then one of the ports is automatically defined as the L1 clock source. The OpenCom 510 will automatically switch the clock source to another port configured as an L1 clock source (if a line fails, for example).

151

PBX Networking Types of Point-to-Point Connections

LED 3 (top right) of an interface card will light up if one of the interfaces on the card has been selected as a clock source. If an S

interface of the type MT+S2M1-

1 is installed, it will be selected as the preferred clock source.

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.

13.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.

13.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

connection can be used for distances up to 1,000 metres, while an S

connection can span up to 250 meters.

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

ports for an S

connection between two OpenCom 510s.

152

PBX Networking

PBX 1, S

ext

1 2 3 4 5 6 7 8

Types of Point-to-Point Connections

8 7 6 5 4 3 2 1

PBX 2, S

ext

(RJ-45 socket)

Wiring of a direct connection

13.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.

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.

13.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

153

PBX Networking Configuration

13.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 510 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 110). 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.

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 systems.

Networking two OpenCom 510 systems using Q.SIG-IP requires 2 licences – one licence per system. The number of possible voice connections is not restricted by the licence.

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 510 as well.

Note: Q.SIG-IP cannot be operated using a connection with

NAT. For a Q.SIG-IP connection, a branch connection or another VPN connection is required.

13.3

Configuration

The possible configurations described below can be set up in the Web console using the PBX Configuration: Trunks menu.

154

PBX Networking Configuration

13.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

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

lines in a multi-terminal configuration to the network operator which are assigned to the “A” trunk group.

■ Two S

point-to-point connections to PBX 2 which are assigned to the “C” trunk group.

■ One S

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.

13.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.

155

PBX Networking Configuration

■ 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 156).

■ 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.

13.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 510 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 510 as a subsidiary system: the only entry you assign to the default entry is the route to the host system

156

PBX Networking Technical Details

PBX

100-199 c d a b 4: b

D: c

PBX

200-299 e g h

3: e

5: h

D: d f

PBX

300-399 k 5: k

D: f

PBX

400-499

D: a

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.

13.4

Technical Details

A different PBX number must be set for each OpenCom 510 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 510 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.

157

PBX Networking

Tip:

Technical Details

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 number at incoming internal setting to “5” for this bundle in order to enable the route to be reseized.

158

Team Functions

14. Team Functions

Introduction

14.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.

14.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

159

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.

160

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.

14.1.2 Team Configuration

You can create teams and program call keys in the Configurator of the

OpenCom 510 ( 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.

161

Team Functions Examples of Use

14.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.

14.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

Executive

TrK 10: Executive

TrK 11: Secretary

TrK 12: Private

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

162

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.

163

Team Functions Examples of Use

14.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.

Miller

TrK 10: Miller

TK 11: Johnson

TK 12: Smith

Johnson

Trk 11: Johnson

TK 10: Miller

TK 12: Smith

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.

164

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

14.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

Johnson

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

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.

165

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.

14.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.

166

Team Functions Examples of Use

Miller 14:22

Mi .

14.Feb

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

Johnson 14:22

Mi .

14.Feb

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

167

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

168

Call Queue

15. Call Queue

Introduction

15.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 510 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.

169

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 510 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.

15.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.

15.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.

170

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.

15.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.

15.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.

15.2

Examples of Use

15.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 Configuration: Ports: S

■ 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 Configuration: System telephones .

171

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

172

Call Queue Examples of Use

15.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 Configuration: Ports: S

■ 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 Configuration: 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 u ser 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

173

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.

174

Multi-Company Variant

16. 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 510 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 510 hardware and software are used equally by all the companies, however. It is possible to configure the

OpenCom 510 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 510 is assigned to a company.

■ Each available trunk group or SIP account 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.

175

Multi-Company Variant Configuring the Multi-Company Variant

16.1

Configuring the Multi-Company Variant

The multi-company variant can be commissioned and configured by the system administrator of the OpenCom 510 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:

The feature must be activated (see

Activating the Multi-Company Variant starting on page 176).

The required companies must be set up (see

Configuring and Managing Companies starting on page 177).

The users of the OpenCom 510 are assigned to the individual companies (see

Assigning Users starting on page 177).

In order that the OpenCom 510 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/SIP Accounts starting on page 178).

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 178).

An exchange must be set up for each company so that the OpenCom 510 can correctly process statuses in which a call should be routed to the exchange (see

Configuring the Company Exchange starting on page 179).

16.1.1 Activating the Multi-Company Variant

To be able to configure several companies in the OpenCom 510, 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.

176

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 .

16.1.2 Configuring and Managing Companies

Up to five companies can be configured in the OpenCom 510. 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.

16.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 510 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.

177

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.

16.1.4 Assigning Trunk Groups/SIP Accounts

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 510, 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. SIP accounts can also be assigned to a company.

The assignment of trunk groups to companies is done in the PBX Configuration:

Trunks: Bundle menu. The assignment of trunk groups to companies is done in the PBX Configuration: SIP: SIP accounts .

For outgoing external calls which users set up via the lines of their company’s trunk group/SIP account, 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 510 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/SIP account was seized. For more information, please see the following section.

16.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 510 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.

178

Multi-Company Variant Working with the Multi-Company Variant

16.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.

16.2

Working with the Multi-Company Variant

All the features of the OpenCom 510 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.

16.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 510.

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.

179

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 510 can manage up to 2,000 entries in all telephone books (in the central, personal and company telephone books).

16.2.2 Making Calls Between Companies

All users of the OpenCom 510 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.

16.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.

180

Configuring the PC Software PC Offline Configuration

17. Configuring the PC Software

Further possibilities of use can be implemented on a workstation computer 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 510.

Proceed as follows to install extra software:

Log on under Windows NT or Windows 2000/XP as the administrator.

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 .

Select the required option from the start interface. Follow the program instructions.

Further instructions for various options that are available are given below.

17.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

Display the product CD contents in Windows Explorer. Search the “\OFC\” installation directory for the offline configurator.

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.

181

Configuring the PC Software PC Offline Configuration

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.

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.

Configure the virtual system as usual. Using the data backup, you can save the configuration.

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 licences in the offline configurator (in menu SYS Configuration: licences ). 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 .

182

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.

17.2

Setting up TAPI

With a TAPI ( T elephony A pplication P rogramming I nterface) you can operate a CTI application ( c omputer t elephony i ntegration). Here, the CTI application uses the services of the OpenCom 510 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

Call up the start mask from the product CD (see Configuring the PC Software on page 181).

Select Software : TAPI Service Provider from the start mask and follow the program instructions.

183

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.

In the Start menu, select Settings : Control Panel . Double-click on the

Telephony icon ( Phone and Modem Options icon under Windows 2000/XP).

Change to the Telephony Drivers tab ( Advanced Options tab under

Windows 2000/XP).

From the list of installed driver software, select OpenCom 100 Service Provider and click on Configure .

In the following dialogue you will find a list with the configured connections for the user who is currently logged on. Click on New .

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 510. 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 510. This user must be allocated a system telephone. Confirm your entry with OK .

The new connection is now configured. Close the opened dialogues with OK and Close .

Testing the TAPI Function

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 Programs : Accessories ). A manual start of the program file “Dialer.exe” in the

“C:\Program files\Windows NT” folder is possible also.

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

184

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.

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 .

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 Connections component.

17.3

Setting up NET CAPI

With a CAPI driver ( c ommon a pplication p rogramming i nterface) Windows programmes are able to access services and functions of an ISDN card. With a network-based CAPI, the OpenCom 510 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 510, any existent ISDN card must be removed and any CAPI drivers on your PC must be de-installed.

Installing the NET CAPI driver

Call up the start mask from the product CD (see Configuring the PC Software on page 181).

Select Software : NET CAPI Driver from the start mask and follow the program instructions.

185

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 510 can be addressed:

Go to the C onfigurator, PBX Configuration : Devices : CAPI-ISDN menu. Click on Change .

Activate the Status check box. Enter at least one unassigned, internal number in the boxes under Parameters . Confirm your entry with Assign .

Go to the C onfigurator, 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 .

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

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 510’s internal a/b ports for sending faxes.

17.4

Using the Systray Display

You can configure a systray display for the OpenCom 510 to appear in the information area of the Start bar of a workstation computer. 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.

186

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 183.

Please note: The systray display requires a current version of TAPI. If you are using TAPI from an earlier version of the OpenCom 510, you must first install the newer version from the product CD.

Installing the systray display

Call up the start mask of the product CD (see Configuring the PC Software on page 181).

From the start mask, select Software : Install Systray . Follow the program instructions.

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 .

If you activate the Autostart check box, you will see the systray display even after restarting your PC.

Confirm the entries in the configuration dialogue with OK and the systray display logs on for the OpenCom 510.

Right-click on the systray display in the Start bar. Select Configuration to call up the configuration dialogue. Select Network Connections or Trunk Lines to produce a status dialogue.

17.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 510. Each time the workstation computer 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.

187

Configuring the PC Software Setting up Video Telephony

Installing the browser

Call up the start mask from the product CD (see

Configuring the PC Software on page 181).

From the start mask, select Software : Install Browser for OpenCTI or

Software : Install Browser for OpenHotel . Follow the program instructions.

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.

17.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

Connect a standard web cam to the workplace computer and install the driver.

In the Windows Start menu select Run and enter: “conf.exe”. Confirm your selection with OK .

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.

188

Configuring the PC Software Synchronising the PC Clock

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.

17.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 510.

Requirements

You must enter the time zone so that the OpenCom 510 can calculate the time of the internal clock back to the GMT (Greenwich Mean Time) required for SNTP:

Go to the Configurator, SYS Configuration: System menu. Click on Change .

Under Internet time (SNTP) , enter the Time zone for which the time of the

OpenCom 510 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 510 as an SNTP server for such programmes.

SNTP with Windows 2000

Here you configure the SNTP server as follows:

Log on as the administrator. Start the Command Prompt under Start : Programs : Accessories .

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.

189

Configuring the PC Software Address Queries using LDAP

Open the Services dialogue under Start : Settings : Control Panel : Administration . 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 510.

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 510 as the Server in the Internet time tab.

17.8

Address Queries using LDAP

You can search the data of the central telephone book of the OpenCom 510 from a workstation computer in the LAN using LDAP (Lightweight Directory Access Protocol). When configuring an LDAP-enabled program, specify the IP address of the

OpenCom 510 as the address of the LDAP server.

LDAP with Outlook Express

You can configure and operate the LDAP directory service with Outlook Express

, a Microsoft

e-mail program, as follows:

Call up the Accounts command in the Tools menu.

The Internet Accounts dialogue box will then open .

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.

Under Internet directory (LDAP) server, enter the address of the

OpenCom 510. It is not necessary to log in to the LDAP server . Click twice on

Next . Then click on Finish .

Check the function. In the Edit menu, call up the Find : People command.

The Find : People dialogue box will then open.

190

Configuring the PC Software Address Queries using LDAP

In the Look in list, select the entry with the OpenCom 510 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.

191

Configuration Guide

18. Configuration Guide

The Configuration Guide contains a series of flowcharts that will help you to plan the configuration of the OpenCom 510 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 510.

■ Configuring PBX Ports : This chart shows you the necessary steps for configuring ports and terminals.

■ Configuring LAN Settings : This chart guides you through TCP/IP settings for the OpenCom 510.

■ Configuring WAN Settings : These instructions support you in configuring the

Internet access (ISP).

■ Configuring RAS Settings : This chart guides you through the configuration of the RAS settings.

■ Configuring Branch Connections : This chart guides you through the configuration of the branch connections (VPN).

■ Configuring E-Mail : This diagram tells you how to create the requirements needed for configuring the OpenCom 510 e-mail access function.

■ Configuring E-Mail Access : This overview provides instructions on configuring the OpenCom 510 e-mail access server.

192

Configuration Guide

18.1

Overview

Yes

Connect the OpenCom and the configuration PC to the network

Ethernet network

(LAN) exists?

Yes

Cross-connected ethernet cable available?

Connect the configuration

PC to the OpenCom LAN port.

Enable DHCP.

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

, 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?

Configure OpenCom network functions?

Yes

LAN Configuration

RAS Configuration

Save data

Flowchart: Overview

Dial in (RAS)?

Connection (LAN)?

Internet?

E-mail?

Yes

Branch Configuration

WAN Configuration

E-Mail Configuration

Finished

Overview

193

Configuration Guide

18.2

PBX Ports

Do you have ISDN terminals that you wish to operate on an S

interface?

Define the access type

Set the access type (multiterminal access and/or system access).

Define the external

interfaces

Set the external S

interfaces and enter the telephone numbers assigned by your network provider.

terminals Yes

Define the internal S

0 interfaces

Set the internal S

interfaces and enter the internal telephone numbers.

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.

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.

Do you want to run the

OpenCount program?

COM Yes

Finished

Flowchart: Configuring the PBX Ports

Configure the COM interface

Select the “connection data” option.

194

Configuration Guide

18.3

LAN Settings

Do you have a computer network?

LAN

Yes

Host name

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?

DHCP

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

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.

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 LAN Settings

LAN Settings

195

Configuration Guide

18.4

WAN Settings

Do you want to configure a new Internet provider?

Enter your provider's dial-in data.

“SYS Configuration: System:

Country” = “German”?

Your own ISP

Yes

T-Online

Provider-New: Provider,

Telephone Number,

User Name and Password

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)

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.

HDLC

Yes

No LAN

Yes

IP address

Network mask

Specify the gateway for the Internet connection.

Gateway

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 WAN Settings

ISP cannot be configured.

WAN Settings

196

Configuration Guide

18.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

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

197

Configuration Guide

18.6

Branch Connections

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

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?

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 Branch Connections

Branch Connections

198

Configuration Guide

18.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

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

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

199

Configuration Guide

18.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

200

Frequently Asked Questions General/Hardware

19. Frequently Asked Questions

This chapter provides tips and information on how to deal with any malfunctions or faults you may experience with the OpenCom 510.

Please note: Repairs to the OpenCom 510 should only be carried out by qualified personnel.

The following LEDs indicate that the OpenCom 510 is ready for operation:

Activity LED

LAN LED

+3,3 V

LED

-42 V

LED

MPS+1-AC MC+1-3

Position of LEDs on the OpenCom 510

19.1

General/Hardware

The OpenCom 510 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 510 still does not function.

DANGER!

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

Is the +3,3V/-42V LED illuminated?

If not, contact your service centre or an authorised dealer. The AC adapter plug of the OpenCom 510 may be defective.

201

Frequently Asked Questions Telephony

After restarting the OpenCom 510, nothing is indicated on the displays of any connected terminals.

It takes a short while for the OpenCom 510 to start up.

After the restart, check whether the activity LED flickers in a regularly interval. This indicates that the OpenCom 510 has started up correctly and is ready for operation. Further information can be found in the chapter

Modules starting on page 59.

If the OpenCom 510 has not restarted properly, reset the OpenCom 510 to its

original factory setting (refer to the chapter entitled Resetting the System Data starting on page 92).

19.2

Telephony

It is not possible to make external calls.

Check the connection between the NTBA and the OpenCom 510.

In the Configurator , check whether the external S

ports are configured correctly

( PBX Configuration: S

menu):

– Configuration of System- / Multi-terminal access OK?

– Port is connected to the NTBA?

– Faultless Cabling?

– Terminating resistors properly configured?

The OpenCom 510 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

port is set for an NTBA in the system configuration; this additional port will be used first to seize a trunk line.

Deactivate the corresponding S

port in the Configurator ( PBX Configuration: S

0 menu).

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

202

Frequently Asked Questions Telephony

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 Distribution 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 510.

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

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

bus is being called.

This case also requires configuring the MSN on the ISDN telephone (see above answer).

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

203

Frequently Asked Questions DECT

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. One of the installed

ISDN interface boards (MX+S01-8 or MT+S2M1-1) should show a steady green

light with LED 3. Details can be found under L1 Clock starting on page 151.

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.

19.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).

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

204

Frequently Asked Questions LAN

Another manufacturer’s DECT device is not functioning.

Check whether the DECT device supports the DECT GAP standard. In the Configurator , 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 204.

19.4

LAN

Why is it not possible to establish a network connection with the

OpenCom 510?

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 510.

To check whether there is a network connection with your OpenCom 510, 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 510?

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 510 along with the protocol identifier, for example http://192.168.99.254/.

Check whether the browser has been configured for connection through a proxy server. If so, deactivate the “Connect through proxy server” setting.

205

Frequently Asked Questions Internet

You have just configured the OpenCom 510 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 510?

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 510 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.

19.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 Configuration : 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.

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.

206

Frequently Asked Questions Internet

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

(only with RFP 21/23). 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 510.

For direct access you can directly dial any provider. Indirect access uses the routing function of the OpenCom 510, 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 Configuration: 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 Configuration: Firewall menu),

■ an internal number is configured for RAS access ( Configurator , Net Configuration: 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.

A SIP connection only passes unidirectional voice. What is the reason?

You did not use the OpenCom 510 as internet router or the STUN server of the SIP provider is unavailable. You need to activate the SIP support at your internet

207

Frequently Asked Questions Internet router, such as “SIP-ALG” or “Full Cone NAT” functions. You can also use the

OpenCom 510 for internet access. Correct the STUN setting in the PBX Configuration : SIP Provider menu.

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.

208

Technical Data

20. Technical Data

Please observe the technical information regarding modules under

Modules starting on page 59.

Component

1-12 frame of the OpenCom 510

Page

– BPV+1-12 backplane system: Supply voltages and system signals for up to 2 power supply units, 1 central control module and 12 interface cards

– Dimensions:

– 4.5 height units (1 U = 44.45 mm)

19" frame in accordance with DIN

41494 Part 5 for installation in a 19" cabinet

– Number of slots:

Modules

– MPS+1-AC power supply unit (with AC/DC converter)

– MC+1-3 central control module

–

MT+S2M1-1 trunk module

MX+S01-8 subscriber or trunk module

– MT+A1-4 trunk module

– MS+UPN1-8 subscriber module

–

MS+UPN2-8 subscriber module

MS+A1-8 subscriber module

– MG+ETH1-1 media gateway module for VoIP

115

209

Technical Data

The following table provides an overview of the configuration limits for the

OpenCom 510. These limits result from the combination of different interface cards.

OpenCom 510: system configuration limits (single 19" frame)

Interface card

(module) maximal insertable

Maximum number of interfaces

Note

MC+1-3 1

MT+S2M1-1

MX+S01-8

MS+UPN1-8

MS+UPN2-8

4 x S

96 x S

88 x U pn

(10/100 Mbits/s), 1 x V.24

–

(for internal or external use)

– with a single 19" frame (a total of 12 slots) one slot is required for the outside line

– with a cascaded system

(two 19" frames) 12 interface cards of this type can be inserted in the 19" frame of the slave system

88 x U pn

– U pn

interfaces are

DECT-capable

– with a single 19" frame (a total of 12 slots) one slot is required for the outside line

– with a cascaded system

(two 19" frames) these interface cards can only be inserted in the 19" frame of the master system

210

Technical Data

OpenCom 510: system configuration limits (single 19" frame)

Interface card

(module)

MS+A1-8 maximal insertable

Maximum number of interfaces

88 x a/b

Note

MT+A1-4

MG+ETH1-1

– with a single 19" frame (a total of 12 slots) one slot is required for the outside line

– with a cascaded system

(two 19" frames) 12 interface cards of this type can be inserted in the 19" frame of the slave system for analogue trunk lines

(10/100 Mbits/s)

– with a cascaded system

(two 19" frames) 12 interface cards of this type can be inserted in the 19" frame of the master system

System configuration limits in general

CompactFlash carte

1 – –

Note: The online help provides an overview of the limits that should be observed when configuring the

OpenCom 510.

211

Notes on disposal

21. 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. 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.

212

Index

Numerics

1-12 frame 20, 26

19" frame 20, 26

a/b ports 48

Actor

See Intercom system 50

Adapter