OpenCom 510 - United Statespbxweb.aastra.com/extra/opencom/oc100/software/Montage... · Features 5...

OpenCom 510Mounting and

Commissioning

User Guide

Welcome to DeTeWe

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

The following instructions will guide you in the operation of your OpenCom 510 software and answer most of the questions that may arise.

If you require further technical sup-port or information about other De-TeWe products, please refer to our website at

www.detewe.de.

It provides additional notes and tips on the product.

We hope you enjoy using OpenCom 510.

OpenCom 100 Product Family

This user guide applies to the OpenCom 100 product family comprising the OpenCom 107, OpenCom 130, OpenCom 131, OpenCom 150 and OpenCom 510 systems. If a reference is made in the text to the OpenCom 100, the description applies to all systems; if the individ-ual characteristics are different, a special note is given.

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

■ Manual for OpenCom 107

■ Manual for OpenCom 130, OpenCom 131 and OpenCom 150

■ Manual for OpenCom 510(19" housing)

We hope you enjoy using the OpenCom 510.

Contents

Features 5

Factory Settings 10Telephony Functions 10

Authorisations 10

Internet Functions 13

Preliminary Information 15Construction of the OpenCom 510 15

Scope of Delivery 16

Declarations of Conformity 16

Installation 17Safety Precautions 17General Instructions . . . . . . . . . . . . 17Notes on the Mains Supply . . . . . . 17Notes on EMC and Earthing . . . . . 18Notes on Installing the

OpenCom 510. . . . . . . . . . . . . . 19Notes on Installing Terminals . . . . 20

Installation, Ambient Conditions 20

Installation in a 19" Rack 21

Installing Modules 22Slots . . . . . . . . . . . . . . . . . . . . . . . . . . 22Notes on Disconnecting the Mains

Supply . . . . . . . . . . . . . . . . . . . . 23Installing the Central Control

Module. . . . . . . . . . . . . . . . . . . . 23Installing Interface Cards. . . . . . . . 25Installing a Power Supply Unit . . . 27

Backplane 28

Uninterruptible Power Supply 30

Power Failure 31

Interfaces and Connectible Terminals

33Overview 33

S0 Ports 34Termination . . . . . . . . . . . . . . . . . . . 35External ISDN Ports (S0 External) . 37Internal S0 Ports. . . . . . . . . . . . . . . . 37

Upn Ports 38Terminals Connected to Upn Ports 38Technical Information. . . . . . . . . . . 38DECT Base Station Connection

Variants . . . . . . . . . . . . . . . . . . . 39

a/b Ports 40Terminals Connected to a/b Ports 40Technical Information. . . . . . . . . . . 42

LAN Port 43DSL Port. . . . . . . . . . . . . . . . . . . . . . . 43Service PC . . . . . . . . . . . . . . . . . . . . . 44

COM Port 44

Accessories and Adapters 45Upn Adapter . . . . . . . . . . . . . . . . . . . 45a/b Adapter . . . . . . . . . . . . . . . . . . . 45Audio Adapter . . . . . . . . . . . . . . . . . 46Approved Devices / Approved

Accessories . . . . . . . . . . . . . . . . 48Device Combinations . . . . . . . . . . . 48

1

2

Modules 52Module Naming Conventions 53

Overview of Available Modules 54

MPS+1-AC 55

MC+1-3 57

MT+S2M1-1 59

MX+S01-8 62

MS+UPN1-8 64

MS+UPN2-8 65

MS+A1-8 67

MS+A1-4 and MT+A1-8 69

Configuration 71Brief Guide to Initial Configuration 72First Configuration via Serial Port . 72

System Requirements 73

Configuration under Windows 74Connection on Serial Port (V.24) . . 74Notes on Configuring the Serial

Port . . . . . . . . . . . . . . . . . . . . . . . 76Connection by Network Card

(LAN) . . . . . . . . . . . . . . . . . . . . . . 76Testing the Setup . . . . . . . . . . . . . . . 77Starting the Browser . . . . . . . . . . . . 78

Configuration for Linux and MacOS 79Linux . . . . . . . . . . . . . . . . . . . . . . . . . . 79MacOS. . . . . . . . . . . . . . . . . . . . . . . . . 79

Configuring the OpenCom 510 80Preparing the Configuration . . . . . 80Starting the Web Console . . . . . . . . 80Loading the Online Help . . . . . . . . . 82Finishing the Configuration . . . . . . 83

Preconfiguration. . . . . . . . . . . . . . . . 83Offline Configurator . . . . . . . . . . . . .83Remote Configuration . . . . . . . . . . .83Codes for IP Configuration . . . . . . . 85Saving and Loading the

Configuration. . . . . . . . . . . . . . .86Receiving System Messages as

E-Mail . . . . . . . . . . . . . . . . . . . . .86Loading SW Updates . . . . . . . . . . . . 86Resetting the System Data . . . . . . .87Generating Your Own MoH Files . .87

Configuration Examples89

OpenCom 510 in Computer Networks 89

Introduction to TCP/IP 90

OpenCom 510 in a Serverless LAN 91DNS Name Resolution . . . . . . . . . . .92Internet Access . . . . . . . . . . . . . . . . .92RAS Access . . . . . . . . . . . . . . . . . . . . .93

OpenCom 510 in a LAN with an IP-enabled Server 93DNS Name Resolution . . . . . . . . . . .94Internet Access . . . . . . . . . . . . . . . . .94RAS Access . . . . . . . . . . . . . . . . . . . . .95

LAN-to-LAN Link 96

Useful Information on Internet Access 97Costs . . . . . . . . . . . . . . . . . . . . . . . . . .97Using the Web. . . . . . . . . . . . . . . . . . 97E-mail . . . . . . . . . . . . . . . . . . . . . . . . .98NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Voice over IP (VoIP)100

Fundamentals 101Propagation Delay and

Bandwidth . . . . . . . . . . . . . . . 101Latency and Packet Length . . . . . 101Voice Quality . . . . . . . . . . . . . . . . . 102Optimisation . . . . . . . . . . . . . . . . . 104

Media Gateway (MGW) 105MG+ETH1-1 . . . . . . . . . . . . . . . . . . 105

VoIP System Telephones 107Device Properties . . . . . . . . . . . . . 107VoIP System Telephone

Configuration . . . . . . . . . . . . . 108LAN DHCP Server. . . . . . . . . . . . . . 109Start Procedure . . . . . . . . . . . . . . . 110

OpenPhone IPC 113 Installation. . . . . . . . . . . . . . . . . . . 114Configuration . . . . . . . . . . . . . . . . . 114

PBX Networking 116Connections 116Protocol: Q.SIG or DSS1 . . . . . . . . 117Master/Slave . . . . . . . . . . . . . . . . . 117L1 Clock . . . . . . . . . . . . . . . . . . . . . . 117

Types of Point-to-Point Connection 118Direct Connection . . . . . . . . . . . . . 118Connection via an Active

Transmission System. . . . . . . 119Connection via the Public

Network . . . . . . . . . . . . . . . . . . 119

Configuration 120Trunk groups . . . . . . . . . . . . . . . . . 120Routes . . . . . . . . . . . . . . . . . . . . . . . 120Numbering . . . . . . . . . . . . . . . . . . . 121

Technical Details 122

Team Functions 123Introduction 123Explanation of Keys. . . . . . . . . . . . 123Team Configuration . . . . . . . . . . . 125

Examples of Use 125Executive/Secretary Team . . . . . . 125Three-member Team . . . . . . . . . . 126Unified Team . . . . . . . . . . . . . . . . . 127Toggle Team . . . . . . . . . . . . . . . . . . 128

Call Queue 130Introduction 130Activation of Queues . . . . . . . . . . 131Call Forwarding . . . . . . . . . . . . . . . 131Pickup . . . . . . . . . . . . . . . . . . . . . . . 131Hunt Groups . . . . . . . . . . . . . . . . . . 132

Examples of Use 132Attendant Terminal for an Operator

with Two System Telephones132Group of Three Attendant

Terminals . . . . . . . . . . . . . . . . . 133

Multi-Company Variant135

Configuring the Multi-Company Variant 136Activating the Multi-Company

Variant . . . . . . . . . . . . . . . . . . . 136Configuring and Managing

Companies. . . . . . . . . . . . . . . . 137Assigning Users . . . . . . . . . . . . . . . 137Assigning Trunk Groups . . . . . . . . 138Allocating Routing Codes . . . . . . 138Configuring the Company

Exchange . . . . . . . . . . . . . . . . . 138

3

4

Working with the Multi-Company Variant 139Company Telephone Book . . . . . .139Making Calls Between

Companies . . . . . . . . . . . . . . . .140Billing Charges per Company. . . .140

Configuring the PC Software 141PC Offline Configuration 141

Setting up TAPI 143

Setting up NET CAPI 145

Using the Systray Display 146

Browser for OpenCTI and OpenHotel 147

Synchronising the PC Clock 148

Address Queries using LDAP 149

USB DECT Box on the OpenCom 510 150General Information . . . . . . . . . . .150Installation and Configuration. . .150Technical Data. . . . . . . . . . . . . . . . .151

Configuration Guide 152Overview 153

PBX Ports 154

Easy Access 155

ISP Settings 156

RAS Settings 157

LAN-to-LAN Settings 158

E-mail Function 159

E-mail Access 160

Frequently Asked Questions 161General/Hardware 161

Telephony 162

DECT 164

LAN 165

Internet 166

Technical Data 168

Index 170

FeaturesThe OpenCom 510 is a communica-tions system for integrated voice and data communication. The most sig-nificant feature of this communica-tions system is its modular structure. The OpenCom 510 is designed for in-stallation in a 19" frame. The frame itself can be installed in a 19" wall-mounted enclosure or in a 19" floor-standing cabinet.

The system provides a number of slots for the installation of modules. In a fully configured system, the fol-lowing modules will have been in-stalled (and all slots will be occu-pied): 2 power supply units, 1 control module, 12 interface cards. By combining different interface cards, it is possible to create configu-rations suited to the user’s specific communications requirements. If, for example, a user requests DECT-capable Upn interfaces or additional S0 or a/b interfaces, one or more in-terface cards can be integrated with-out 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 re-quirements.

The OpenCom 510 can be inte-grated into system environments

with structured cabling. All connec-tions to a structured cabling patch panel can be made with standard patch cables.

The OpenCom 510 supports the fol-lowing communications applica-tions:

■ Telephony with system tele-phones, ISDN telephones and analogue terminals, Internet/in-tranet data communication, CTI applications, sub-system opera-tion and system configuration using a standard web browser

■ Additional software packages for expanded telephony func-tions can be operated and for making telephone functions more comfortable, e.g. the dig-ital voicebox and voice portal systems OpenVoice and OpenAt-tendant.

■ The “DoorLine” intercom system can be operated.

TelephonyThe OpenCom 510 communications system is designed to be connected to an ISDN basic access interface us-ing the DSS1 protocol. Both multi-terminal access (point-to-multipoint) and system access (point-to-point) configurations are supported. The system can be con-

5Features

6

figured to run both types of access in parallel. S0 and S2M interface cards are available for connecting the sys-tem to the telecommunications net-work. An S0 interface card provides eight S0 ports (switchable to either internal or external connections). The S2M interface card provides one ISDN S2M interface for connecting the OpenCom 510 either to a pri-mary multiplex interface or to a sec-ond PBX (ISDN point-to-point con-nection). For an overview of interface cards, refer to Modules starting on page 52.

The OpenCom 510 firmware is de-signed for a maximum of 600 users. For information on system limita-tions, refer to Technical Data starting on page 168.

The following can be connected to the OpenCom 510:

■ Euro ISDN terminals

■ DeTeWe system telephones

■ OpenPhone 52 ISDN telephones (to the Upn port)

■ DeTeWe RFP 21 base stations

■ DECT handsets (with RFP 21 con-nected to DECT-capable Upn port of MS+UPN2-8 interface card)

■ analogue terminals

S0 interfaces must be operated with Euro ISDN terminals in accordance with the DSS1 protocol.

Upn ports are suitable for connecting the OpenPhone range of DeTeWe system telephones. Furthermore, the DECT-capable Upn ports of the MS+UPN2-8 interface card can be used to connect RFP 21 base sta-tions.

Analogue ports are suitable for con-necting standard analogue termi-nals.

If your network provider supports the CNIP (Calling Name Identifica-tion 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 en-try in the telephone book under the number of the caller, this entry will be displayed instead.

The OpenCom 510 can be inte-grated into an existing local area network (LAN) and used as an Inter-net 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.

Features

The OpenCom 510 can be pre-con-figured at the service centre and re-mote-configured for service pur-poses.

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 Te-lephony 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 inte-grated dialling wizard 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 FeaturesThe 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 commu-nication with the help of team func-tions 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 us-ing a number of individually config-urable filter criteria. For further in-formation, refer to the web console online help.

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 require-ments grow, the OpenCom 510 can be networked with other telecom-munications systems. The OpenCom 510 can then operate as a sub-system or as a DECT server. It is also possible to create a telecommu-nications system with several net-worked PBXs.

Internet AccessFor the purpose of providing Inter-net access, PCs can be connected to the OpenCom 510 by means of the internal S0 ports, and an entire LAN can be connected by means of the Ethernet port. If Internet access is al-ready available from an Internet

7Features

8

service provider, the OpenCom 510 can be configured accordingly. The OpenCom 510 can also be used for IP configuration if there is no IP-capa-ble 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 con-nected PCs to access the Internet us-ing a common IP address; only the common address will be visible out-side the LAN. Network address trans-lation (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 at-tacks from the Internet. The OpenCom 510 offers further protec-tion of the LAN in the form of cus-tomisable filter lists (firewall func-tion).

Note: Also observe the notes in Useful Information on Internet Access starting on page 97.

DECT Data CommunicationPCs that are not connected to the OpenCom 510 via the internal S0 ports or the Ethernet interface can access the Internet if used in combi-nation with a USB DECT Box or 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 by means of the supplied adapter. The Internet can be ac-cessed 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 Inter-net connection itself will be estab-lished 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 the OpenCom 510 and thus benefits from the security fea-tures of shared Internet access.

The optional USB DECT Box enables a PC to establish a wireless (DECT) ISDN data connection. The USB DECT Box and the PC are connected by means of the USB interface.

For detailed information on install-ing the required driver software and on the various configuration op-tions, refer to USB DECT Box on the OpenCom 510 starting on page 150 and to the “OpenPhone 27” user guide. For information on configur-ing the OpenPhone 27 data inter-face, please refer to the OpenCom 510 online help.

Features

E-MailThe OpenCom 510 offers an inte-grated 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 send-ers from the mail server at set inter-vals and forwards them to the user’s system terminal.

E-mail accounts for the sending e-mail can also can be configured for users. E-mails can then, for example, be sent directly from the OpenCTI 50 to other users. In addi-tion, users who have had a voicebox configured for themselves, can let themselves be notified of new voice-box 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 mes-sages) can be sent via e-mail.

Voice over IP (VoIP)The OpenCom 510 supports the con-nection of VoIP terminals and thereby allow telephony via the ex-isting company network infrastruc-ture. 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 vari-ations (OpenSoftphone). You will find further information in the chap-ter Voice over IP (VoIP) starting on page 100).

Further Network FeaturesYou 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 con-nect 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 func-tions.

9Features

10

Factory SettingsThe OpenCom 510 is delivered with the following basic settings and acti-vated features. We recommend that you configure the OpenCom 510 to meet your specific requirements be-fore putting it into operation (see Configuration starting on page 71).

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

Telephony Functions

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

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

■ Incoming external calls are sig-nalled at all corded terminals connected to the system.

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

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 allo-cated to these groups.

Three user groups are preset: “Ad-ministrators”, “Standard” and “Guests”. “Administrators” have ac-

cess to all functions of the OpenCom 510 and unrestricted con-figuration rights. Users in the “Guests” group cannot configure the OpenCom 510, are not able to make external calls, and have only re-stricted 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

Telephony Functions Factory Settings

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 user logs on to the web console. All terminals are then auto-matically allocated to the “Guests” group. For further information on configuring user groups and users, re-fer to the online help chapter “User Manager”.

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

■ External line access: Interna-tional 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 config-ured, users can make calls using selected call-by-call providers.

■ VIP call is activated.

■ Announcements to system ter-minals 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 acti-vated.

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

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

■ Function “Call queue” is deacti-vated.

■ Call forwarding to internal or ex-ternal numbers can be activated. Call forwarding after delay is ex-ecuted after 20 seconds. Door calls and MSN groups can be for-warded. Call forwarding for other users and call forwarding by other users are deactivated.

■ External calls can be transferred to an external subscriber.

11Factory Settings Authorisations

12

■ Three-party conferences can be set up.

■ Call protection can be activated, call-waiting protection, an-nouncement protection and pick-up protection can not be activated.

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

■ The telephone lock can be acti-vated. 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 acti-vated for the user groups. A spe-cial list with emergency tele-phone numbers is preset and activated.

■ Call lists on terminals list inter-nal calls, external calls, calls from the door and calls that the user received while they were tele-phoning.

■ Function keys can be pro-grammed on system tele-phones, no keys are locked.

■ The door opener can be oper-ated from all terminals. Door calls can be forwarded.

■ Connection data analysis is de-activated.

■ The cost multiplier is set to 100%, i.e. the costs are not mul-tiplied by any factor. There are no preset basic amounts for the charging of calls.

■ Speed dialling is possible, pro-vided it has been configured in the OpenCom 510 central tele-phone book.

■ Keypad dialling is possible.

■ Time control is not active as there are no time groups config-ured.

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

■ Call charges can be recorded, as-sociated with booking numbers and analysed.

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

■ Every user can change the con-figuration of the OpenCom 510.

Authorisations Factory Settings

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

■ Every user can read out the charges.

■ Applications requiring a license (e.g. OpenCount) can be used af-ter being activated.

■ Access via RAS is not allowed.

■ E-mail notification to system ter-minals is possible. There are no user accounts configured for the sending of e-mails, the authori-sation for sending e-mails is not deactivated.

■ The multi-company variant is not activated.

Internet Functions

■ RAS access (with or without call-back) can be configured for every OpenCom 510 user, pro-vided that RAS access is author-ised.

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

■ Every user with a system termi-nal 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 pre-set for network configuration:

■ Host name: host

■ IP address: 192.168.99.254

■ Network mask: 255.255.255.0

The following addresses are trans-mitted 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

13Factory Settings Internet Functions

14

You can change the IP settings in the Configurator. Consult the LAN’s net-work administrator if you wish to do so.

Internet Functions Factory Settings

Preliminary Information

Construction of the OpenCom 510

The OpenCom 510 is designed to be used in 19" rack systems. It com-prises 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 pro-vides 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 as-sembled. By contrast with other sys-tems, 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 In-stallation in a 19" Rack starting on page 21 and Installing Modules start-ing on page 22.

15Preliminary Information Construction of the OpenCom 510

16

Scope of DeliveryThe 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

–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. sec-ond power supply unit, interface cards and accompanying ca-bles) are included as per the cus-tomer’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 co-vering unused slots

■ 1 set of short user guides

■ 1 CD

Declarations of Conformity

The communications systems of the OpenCom 100 product family com-ply with the requirements of EU di-rective 99/5/EC.

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

Scope of Delivery Preliminary Information

Installation

Safety Precautions

The CE symbol on the product con-firms that it meets the requirements of the technical guidelines on user safety and electromagnetic compat-ibility valid at the time of approval.

General Instructions

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

DANGER! Hazardous volt-ages 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 re-pairs.

Always use the original packaging when packing OpenCom 510 com-ponents for transport or storage.

CAUTION!

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

Notes on the Mains Supply

The OpenCom 510 may be con-nected 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 pow-ered by two MPS+1-AC power sup-ply units, each of the two units must be plugged into its own mains

17Installation Safety Precautions

18

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 de-vice.

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

The mains socket’s protective earth conductor and the telephone earth line must be connected to one refer-ence point for potential equalisa-tion. This is normally the OpenCom 510 housing.

Earthing and PotentialFor the purpose of potential equali-sation, all conductive parts of the OpenCom 510 must be connected to the protective earth conductor (earth bus-bar of the building’s wir-ing system) by means of a solid or stranded wire of at least 2,5 mm2 (yellow/green).

Safety Precautions Installation

OpenCom 510: Earthing arrangement

The metal screens of the subscriber and trunk cables must be connected to the circuit common in the distrib-utor or the patch field. The protec-tive earth conductor of the 230 V mains cables is connected to the cir-cuit common and the telephone earth line.

All metal parts of the communica-tions system are mechanically and thus electrically coupled in order to provide protection through the pro-tective earth conductor and the tele-phone earth line.

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 dur-ing a thunderstorm. Do not connect or disconnect any cables during a thunderstorm.

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

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

ø 2,5 mm2

ø 2,5 mm2

19Installation Safety Precautions

20

Notes on Installing Terminals

Only devices that supply safety ex-tra-low voltage (SELV) may be con-nected 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 require-ments. For details, refer to a/b Ports starting on page 40.

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

Installation, Ambient Conditions

The ambient temperature for oper-ating the OpenCom 510 must be be-tween +5 °C and +40 °C.

To maintain a safe ambient tempera-ture, 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 de-vices such as transmitter and ra-diotherapy or similar apparatus.

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 con-nected to an IT system.

Installation, Ambient Conditions Installation

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:

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

B

A

C

1

2

C

Legend

1 Left mounting bracket

2 Right mounting bracket

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

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

C Left and right screw points for earthing wrist strap or circuit common connection between1-12 frame and 19" rack

Legend

21Installation Installation in a 19" Rack

22

Installing Modules

OpenCom 510: 1-12 frame slots

Slots

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

■ 2 power supply units

■ 1 control module

■ 12 interface cards (trunk or sub-scriber modules) split into 2 separate groups.

The following slots are provided for installing these modules:

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

A

D (7-12)

C (1-6)

0 B

Legend

A Slot for group 1 power supply unit

B Slot for group 2 power supply unit

0 Slot for central control module

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

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

Installing Modules Installation

power supply unit must therefore al-ways be installed.

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

Notes on Disconnecting the Mains Supply


The OpenCom 510 must be discon-nected 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-en-ergised by unplugging both mains cables.

DANGER! Always unplug the mains cables of both power sup-ply units when installing the cen-tral 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 opera-tional! 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 opera-tional. However, slots 7 - 12 (D) will still be supplied with operating volt-age. (Refer to the illustration OpenCom 510: 1-12 frame slots on page 22 to determine the location of the modules specified in parenthe-ses 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 52.

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:

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

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

23Installation Installing Modules

24

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

2. Wait until the LEDs of the in-stalled modules start flashing red.


3. Unplug all of the mains cables of the OpenCom 510 to disconnect the system from the mains sup-ply.

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

4. Remove the screws with which the central control module is se-cured in the 1-12 frame and pull the module out.

5. Unpack the central control mod-ule.

CAUTION!

Static charge can damage elec-tronic devices. Observe the regu-lations regarding electrostati-cally sensitive components.

6. Carefully push the central con-trol module into slot 0 (see also the illustration OpenCom 510: 1-12 frame slots on page 22). The printing on the front of the mod-ule should be at the top.

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

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

8. Plug the desired cables into the corresponding RJ45 sockets on the central control module. Re-fer to Modules starting on page 52 for information on pin assignment.

9. 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 22) with the mains sup-ply (if you are powering the


OpenCom 510 with two power supply units, reconnect the sec-ond unit as well).

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

10. Observe the module LEDs during start-up of the OpenCom 510. Information on indicators can be found in Modules starting on page 52.

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

Explanatory Note on Shutting Down the SystemIf the OpenCom 510 is disconnected from the mains supply, its main memory is deleted. The main mem-ory stores the current configuration data, which are regularly copied to the CompactFlash memory card. Re-starting the system causes it to copy the current configuration data from the main memory to the Compact-Flash card, which ensures that the most recent configuration is restored when the system is started up.

Installing Interface Cards

Interface cards can be installed or exchanged with the system powered up (“hot-plugging”). Proceed as fol-lows:

1. If you want to exchange an in-terface card, the slot for this card needs to be deactivated first.

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

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

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


26

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

CAUTION!


4. Carefully push the interface card into the corresponding slot. The printing on the front of the mod-ule should be at the top (see il-lustration in previous instruc-tion).

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

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

6. Plug the desired cables into the corresponding RJ45 sockets on the interface card. Refer to Mod-ules starting on page 52 for in-formation on the pin assign-ment for each interface card.

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

The dummy covers must be se-curely screwed to the frame!

8. If you have exchanged the inter-face card, you will need to reacti-vate the slot for this card.

Open the PBX Configuration: Ports: Slots page in the Config-urator again. In the table row listing the card that has been ex-changed, click on Start.

9. Observe the LEDs on the card. Information on indicators can be found in the chapter Modules starting on page 52.

Checking the Status of the Interface Cards via the Web ConsoleYou can also check the status of the interface cards via the Web console of the OpenCom 510.

1. Open the PBX Configuration: Ports: Slots page in the Config-urator.

S0 1

S0 2

MX+S01-8


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

Installing a Power Supply Unit

Depending on the number of in-stalled modules (interface cards), ei-ther one or two power supplies are required (see A and B in the illustra-tion OpenCom 510: 1-12 frame slots on page 22):

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

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

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

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

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

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

2. Wait until the LEDs of the in-stalled modules start flashing red.



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

4. Unpack the power supply unit.

CAUTION!



28

5. Carefully push the power supply unit into the corresponding slot (see also the illustration OpenCom 510: 1-12 frame slots on page 22). 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 se-curely plugged into the socket on the backplane.

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

7. Install further interface cards if required (see also Installing In-terface Cards starting on page 25).

8. Switch the OpenCom 510 on. To do so, reconnect the power sup-ply 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.

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

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 pro-vide 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 ar-ranged 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 con-nected 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 sys-tem serial number (etched into the backplane chip).

Backplane Installation

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



Refer to Notes on Disconnecting the Mains Supply starting on page 23.

2. Uninstall all modules and power supply units from the 1-12 frame (see Installing Modules starting on page 22).

3. Remove the screws on the back-plane (see arrows in the illustra-tion OpenCom 510: Backplane screws). Carefully remove the backplane from the 1-12 frame, pulling it out of the frame to-wards the front.

OpenCom 510: Backplane screws

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

5. Reinstall the modules in the des-ignated slots.

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

The dummy covers must be se-curely screwed to the frame!

7. Switch the OpenCom 510 on again. To do so, reconnect the power supply unit with the mains supply (if you are power-

29Installation Backplane

30

ing the OpenCom 510 with two power supply units, connect the second unit as well).

8. Observe the module LEDs during start-up of the OpenCom 510. Information on indicators can be found Modules starting on page 52.

If you were using software pack-ages 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 DeTeWe distribu-tor.

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

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 re-enter the PARK.

11. You can determine the new PARK in the System Info: Ver-sions menu in the Configurator.

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.

Uninterruptible Power Supply Installation

Power FailureIn 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 configu-rations, the OpenCom 510 provides an emergency service feature: In the event of a power failure, the S01 in-terface will be switched to the S08 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.

■ 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 S01 must be connected to an NTBA (multi-terminal access) and configured as an external connection.

■ Port S08 must be configured as an internal connection. An ISDN telephone with emergency serv-ice capability must be connected to this port.

Note: Emergency service is not pos-sible with system access configura-tions.

Testing the Power Failure CircuitYou can test the configuration as fol-lows:

1. Disconnect the OpenCom 510 from the mains supply (see in-structions in Installing the Cen-tral Control Module starting on page 23, steps 1 to 3).

2. Disconnect the NTBA from the mains supply.

3. It should now be possible to make external calls through the ISDN telephone connected to port S08.

31Installation Power Failure

32

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

S17/18 S19/20

12

ON

12

ON

Power Failure Installation

Interfaces and Connectible Terminals

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 re-quired. Patch panels can be con-

nected by means of standard patch cables.

For technical information on the in-terfaces, refer to Modules starting on page 52.

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

Overview: Interfaces and Interface Cards

Interface Card Properties Page

S0 MX+S01-8 8 S0 interfaces for either external or inter-

nal connections

62

S2M MT+S2M1-1 1 S2M interface for connecting to digital

networks (primary multiplex connections) or for cascading two PBXs

59

Upn MS+UPN1-8 8 Upn interfaces, Upn interfaces are not

DECT-capable

64

Upn MS+UPN2-8 8 Upn interfaces, Upn interfaces are DECT-

capable

64

a/b MS+A1-8 8 a/b interfaces 67

LAN MC+1-3 1 Ethernet port (10/100 Mbits/s)(on central control module)

57

COM / V.24 MC+1-3 2 V.24 ports (on central control module)

57

33Interfaces and Connectible Terminals Overview

34

S0 Ports

All of the eight S0 interfaces on the MX+S01-8 interface card are switch-able, i.e. they can be used either for external connections (ISDN basic ac-cess 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 S0 ports have been imple-mented as RJ45 sockets.

Pin Assignment

S0 interface pin assignment

The following table explains the S0 interface pin assignment.

Overview: Interfaces and Connectible Terminals

Interface Terminals/Systems Page

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

34

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

38

a/b Analogue terminals: telephones, G3 fax machines, (external or internal) mo-dems, external music-on-hold devices, external voice mail systems, external intercom systems

40

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

Connection of VoIP terminals 100

COM / V.24 Connection of a PC (for transmitting connection data) 44

1 2 3 4 5 6 7 8

+ + – –

S0 Ports Interfaces and Connectible Terminals

Termination

Each interface card has 16 DIP switches (S1 to S16, two per S0 inter-face). The DIP switches activate the required terminating resistors for the S0 buses (100 ohms per S0 bus). In the default setting, all terminat-ing 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 S0 interfaces.

Bus Configuration: OpenCom 510 at the End of an S0 BusIf a OpenCom 510 is connected at the end of an S0 bus, the terminating resistors of the relevant S0 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 S0 port; therefore, all ter-minating resistors of the interface card are activated in the default set-ting.

Pin Number Assignment

1 Not used

2 Not used

3 Send +

4 Receive +

5 Receive -

6 Send -

7 Not used

8 Not used

12

ON

35Interfaces and Connectible Terminals S0 Ports

36

MX+S01-8: Terminating resistors acti-vated

One end of the S0 bus is terminated by the OpenCom 510; the terminat-ing resistors must be activated (DIP switches set to “on”). IAE = ISDN socket (German: “ISDN Anschluß Einheit”) or ISDN terminal. TR = Terminating Resistor, the S0 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 inte-grated terminating resistors.

Bus Configuration: OpenCom 510 in the Middle of an S0 BusIf a OpenCom 510 is connected in the middle of an S0 bus, the termi-nating resistors of the relevant S0 in-terface cards must be deactivated.

1. Remove the interface card by following the instructions in In-stalling Interface Cards starting on page 25.

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

MX+S01-8: Terminating resistors de-activated

Both ends of the S0 bus are termi-nated by terminating resistors; the terminating resistors must be deac-tivated (DIP switches set to “1 2”).

12

ON

IAE IAETR

OpenCom 510

1a

1b

2a

2b

TR

TR

12

ON

IAETRTR

IAE

OpenCom 510

S0 Ports Interfaces and Connectible Terminals

External ISDN Ports (S0 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 exter-nal S0 ports, connect the RJ45 sock-ets of the systems by means of a crossed twisted-pair cable. The dis-tance between the two PBXs must not exceed 1000 metres (see also PBX Networking starting on page 116).

Wiring for direct connection

Internal S0 Ports

Up to eight ISDN terminals per bus can be connected to the internal S0 ports by means of four-wire cables. Three of these terminals can be sup-plied with power from the bus; any additional terminals will require their own power supply. The internal S0 buses can be used for point-to-multipoint connections in accord-ance with the DSS1 protocol (Euro ISDN).

ISDN terminals can be connected to internal S0 ports by means of a crossed ISDN cable. For the pin as-signment of crossed ISDN cables, re-fer to the illustration Wiring for direct connection on page 37. If the termi-nal did not come with a suitable ISDN cable, contact your dealer or DeTeWe distributor.

The length of an internal S0 bus ca-ble must not exceed 150 m. Each in-ternal S0 bus has a power feed of ap-prox. 3 W. The feed voltage is –42 V.

1 2 3 4 5 6 7 8

8 7 6 5 4 3 2 1

PBX 1, S0 ext

PBX 2, S0 ext(RJ-45 socket)

37Interfaces and Connectible Terminals S0 Ports

38

Upn Ports

Terminals Connected to Upn Ports

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

■ RFP 21 DECT base station

■ OpenPhone 61, OpenPhone 63 or OpenPhone 65 system tele-phone

■ OpenPhone 52 ISDN system ter-minal

The (corded) OpenPhone 63 and OpenPhone 65 system telephones can be cascaded by means of a Upn adapter, which enables you to con-nect two OpenPhones to one Upn port. For further information, refer to the “OpenPhone 61, 63, 65” user guide.

The RFP 21 DECT base station can be used to connect the OpenPhone 26 and OpenPhone 27 DECT handsets. The OpenPhone 27 has an USB inter-face for data transmissions and In-ternet access. Note that handsets such as the OpenPhone 26 can also be used in conjunction with base stations operating with the GAP/CAP standard.

Note on the MS+UPN2-8 Interface CardUpn 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 Upn interfaces.

Note on the MS+UPN1-8 Interface CardThe Upn interfaces of the MS+UPN1-8 interface card cannot be used to connect DECT base sta-tions.

Technical Information

The Upn ports have been imple-mented as RJ45 sockets.

Each of the devices listed above can be connected to the Upn interface by means of a two-wire 1:1 cable. Sys-tem terminals come with a suitable cable for connection to the RJ45 socket of the interface.

A two-wire cable connected to a Upn port can be up to 1000 m long, pro-vided it is a 0.6 mm twisted-pair ca-ble.

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

Upn Ports Interfaces and Connectible Terminals

DECT Base Station Connection Variants

A DECT base station can be con-nected to either one or two Upn in-terfaces:

■ If the DECT base station is con-nected to one Upn interface, four simultaneous calls or connec-tions can be made through the handsets.

■ If the DECT base station is con-nected to two Upn interfaces, eight simultaneous calls or con-nections can be made through the handsets.

Please note that it is not possible to establish more simultaneous exter-nal connections than there are ex-ternal B channels.

To connect a DECT base station to two Upn interfaces, you can combine two Upn ports on the MS+UPN2-8 interface card: Upn ports 1+2, 3+4, 5+6 or 7+8 (Upn port 2 is connected to Upn port 1, Upn port 4 to Upn port 3 etc.). Ports are combined by setting the DIP switches on the card accordingly. In this configuration, the DECT base station must be con-nected to the first Upn port of the pair by means of a 1:1 cable (system telephone cable).

Pin Assignment

Upn interface pin assignment

The following table explains the Upn interface pin assignment.

*) If the DIP switches are set accord-ingly, the conductors of the adjacent Upn port will be connected here; use only the first Upn port in this config-uration.

Setting DIP Switches

1. Remove the interface card by following the instructions in In-stalling Interface Cards starting on page 25.

2. The DIP switches are protected by a plastic foil. Use a pointed tool such as a screwdriver to slide the DIP switches to the


1 Not used

2 Not used

3 Upn a *)

4 Upn a

5 Upn b

6 Upn b *)

7 Not used

8 Not used

1 2 3 4 5 6 7 8

39Interfaces and Connectible Terminals Upn Ports

40

right (see arrow in the illustra-tion Location of the DIP switches on the MS+UPN2-8 interface card on page 40).

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

a/b Ports

Terminals Connected to a/b Ports

a/b ports can be used to connect an-alogue 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 follow-ing notes on connecting analogue terminals. Terminals that do not sat-isfy the technical requirements for connection with the OpenCom 510 may cause damage to the communi-cations system!

Analogue TelephonesIf analogue telephones are to be connected, we recommend devices that support dual-tone multi-fre-

1 2

ON

a/b Ports Interfaces and Connectible Terminals

quency (DTMF) dialling as it is not possible to use the additional fea-tures of the OpenCom 510 with pulse dialling telephones.

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

Music on HoldA suitable external device for music on hold is the Genius 2000, manu-factured 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 Configura-tion: Components menu of the Con-figurator. For further information, refer to the online help.

Please note: For external music on hold, use only devices with an in-put impedance of 600 ohms, floating connection. An incorrect input imped-ance can cause irreparable damage to the OpenCom 510!

Voice MailIf 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 rec-ommend the following Speech De-sign 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 S0 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 ac-tor for the door opener contact.

Observe the following when con-necting:

■ 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 Doorsta-tion 2-wire under Type. Activate the Actuator option, if you want 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 ac-tor 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

41Interfaces and Connectible Terminals a/b Ports

42

PBX Configuration: Ports: Doorbell menu in the Configu-rator.

■ You can call the “DoorLine” in-tercom 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 config-uring the “DoorLine” intercom sys-tem, refer to the product user guide.

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


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

A two-wire cable connected to ana/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

a/b interface pin assignment

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


1 Not used

2 Not used

3 Not used

4 Channel a

5 Channel b

6 Not used

7 Not used

8 Not used

1 2 3 4 5 6 7 8

a/b Ports Interfaces and Connectible Terminals

LAN PortThe 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 connec-tions.

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

A LAN cable (twisted-pair in accord-ance 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).

DSL Port

External DSL modems can be con-nected via the LAN port. This re-quires 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.

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

Network connection of the OpenCom 510 via ISDN and DSL

TAE

DSLSplitter

NTBA

Hub

DSL & Uk0

DSLModem

Uk0

TCP/IP &PPPoE

DSLS0

PC

Net

OpenCom

S0 Net

Crosslinked twisted pair cablePPPoE

TCP/IP

43Interfaces and Connectible Terminals LAN Port

44

Service PC

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

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 ana-lysed in detail with the connection data recording program OpenCount.

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

The V.24 interface uses a transmis-sion rate of 19.2 kbits/s.

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

Pin Assignment

V.24 interface pin assignment

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

1 2 3 4 5 6 7 8 9 10


1 GND (EED)

2 Not used

3 DTR

4 CTS

5 TXD

6 RTS

7 RXD

8 DSR

9 DCD

10 Not used

COM Port Interfaces and Connectible Terminals

Accessories and AdaptersThe OpenPhone 63 and OpenPhone 65 system telephones have one or two slots on the rear for various adapters and other accesso-ries. Further information on install-ing and operating these add-ons can be found in the “OpenPhone 61, 63, 65” user guide under “Add-ons (with & without an Adapter)”.

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

Upn Adapter

The Upn adapter is an adapter with a Upn port for connecting another OpenPhone 61, 63, 65 system tele-phone and a socket for an extra plug-in power supply.

Weight: 70 gDimensions: 73 x 60 x 30 mmPower consumption: max. 195 mWCable length: max. 30 m

Please note: The Upn adapter may be used only for connecting the system terminals listed above. The Upn extension cable must not exceed 30 m in length and must not be used outdoors.

Note: An extra plug-in power sup-ply is required to operate combina-tions of equipment with a power con-sumption that exceeds the power output of the Upn ports.

a/b Adapter

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

Connecting an a/b adapter will re-sult in exceeding the feed perform-ance of the Upn port, regardless of the range. Therefore a plug-in power supply must be additionally con-nected to the a/b adapter.

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

Weight: 70gDimensions: 73 x 60 x 30 mmPower consumption: max. 160 mWCable length: max. 3 m

45Installation Accessories and Adapters

46

Audio Adapter

The audio adapter is an adapter ex-tension with four different ports for external audio and signalling de-vices.

Weight: 70gDimensions: 73 x 60 x 30 mmPower consumption: max. 260 mW (with relay active).

Audio Adapter Pin Assignment

Port Used for Socket Assignment

1 Ear cap, second handset, headset, active speaker or mi-crophone

RJ-10(4-pinWestern socket)

1: microphone -

2: speaker +

3: speaker -

4: microphone +

2 Recording device; relay contact generates sig-nal for starting and stopping recording.

Stereo jack, 3.5 mm

1 (GND): recording signal, relay contact 1

2 (peak): recording signal +

3 (ring): relay contact 1

3 Not used on OpenCom 510

Round power socket(4 mm)

-

4 Door display RJ-11 or RJ-12(6-pinWestern socket)

4, 5: relay contact 2

1, 2, 3, 6: NC

Accessories and Adapters Installation

Electrical Data of Ports

Port Connection Values

Microphone, microphone of second handset, headset microphone

Electret microphoneTypical sensitivity: 10 mV/PaPower feed: I < 300 µA at 1.5 V

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

Typical impedance: 150 ± 30 ohmsTypical sensitivity: 94 dB/1 mW (0 dB = 20 µPa)

Active speaker Max. output voltage: 1 Vrms

at input impedance > 10 kohms

Recording device audio input Typical input sensitivity: 0.24 mV(microphone level)

Recording device start/stop(relay contact 1)

Max. switching voltage: 50 VDC/29 V ACMax. switching current: 1 ADC/0.7 A AC

Door display(relay contact 2)

Max. switching voltage: 50 VDC/29 V ACMax. switching current: 1 ADC/0.7 A AC


48

Approved Devices / Approved Accessories

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

Device Combinations

You can use the following power val-ues to calculate the power consump-tion of combined equipment:

■ Upn adapter: 195 mW

■ Audio adapter: 260 mW

■ a/b adapter: 160 mW (must be combined with a plug-in power supply!)

■ OpenPhone 61: 1,000 mW



■ Up to three add-on keypads: 330 mW

These symbols are used in the fol-lowing tables:

● This combination is possible.❍ Reduced tone ringing, open listen-ing and hands-free talking volume possible.

The following devices are recommended:

Type Manufacturer, Product Designation

Headset: GN-Netcom, Profile binaural (1869-00-03)

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

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

Second handset Siemens, L30351-F600-A366

Handset DeTeWe, OpenPhone 60

Microphone: Winfinity, 4511326 / H 282-18

Loudspeaker: Siemens, L30460-X1278-X

Recording device: No recommendation


Configurations without Plug-in Power Supply (Range up to 500 m)

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

Basic Unit: OpenPhone 63

Add-ons Second Terminal Power

Audio adapter Upn adapter Up to 3 keypad modules

– – – – 1025 mW

● – – – 1285 mW

– ● – OpenPhone 61 2220 mW

– ● – OpenPhone 63without adapter

2245 mW

– ● – OpenPhone 65 without adapter or keypad module

2360 mW




– – – – 1140 mW

– – ● – 1470 mW

● – ● – 1730 mW


50

Configurations without Plug-in Power Supply (Range 500 to 1000 m)

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

– ● – OpenPhone 61 2335 mW

– ● – OpenPhone 63without adapter

2360 mW

– ❍ – OpenPhone 65without adapter or keypad module

2475 mW




Basic Unit Add-ons Power

Audio adapter Upn adapter Up to 3keypad mod-ules

OpenPhone 63 ● – – 1285 mW

OpenPhone 65 – – ● 1470 mW

● – ● 1730 mW


Configurations with Plug-in Power Supplies

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


Add-ons: Second terminal

Up to 3 keypad modules

Audio adapter

Upn adapter

and plug-in power supply

OpenPhone 61 OpenPhone 63 without adapter

OpenPhone 65 without adapter and with 1 keypad module

● ●

● ●

● ●


Add-ons: Second terminal

Up to 3 keypad modules

Audio adapter

Upn adapter

and plug-in power sup-ply

OpenPhone 61 OpenPhone 63 without adapter

OpenPhone 65 without adapter and with 1 keypad module

● ● ●

● ● ●

● ● ●

● ● ● ●

● ● ● ●

● ● ● ●


52

ModulesThis chapter provides detailed tech-nical information on the modules which can be installed in the OpenCom 510. You will find informa-tion on their respective fields of ap-plication, along with technical and operational information and notes on indicators.

The modules fulfil the following tasks:

■ Power supply units (max. 2) pro-vide 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 con-nect the OpenCom 510 to the telecommunications network (or to another communications system) and to connect termi-nals. A number of interface cards are available for these tasks. De-pending on the interface card’s functions, it may also be referred to as a trunk module or as a sub-scriber module.

For detailed information on install-ing modules, refer to the chapter In-stalling Modules starting on page 22.

Please note: When installing modules, always observe the Safety Precautions starting on page 17!

Modules

Module Naming ConventionsModules are named according to a schema which enables the deduc-tion of the module’s type and func-tion:

Mx+y1-z

Abbr. Meaning

M Module

x Indicates the module type as follows:

C Control

S Subscriber

T Trunk

X Subscriber/Trunk

PS Power Supply

+ Character used to divide the product name

y Indicates the interface type as follows:

A Analogue interface

UPN Upn interface

S0 S0 interface

S2M S2M interface

1 Module generation

- Character used to divide the product name

z Number of interfaces

53Modules Module Naming Conventions

54

Overview of Available ModulesThe following table provides an overview of modules available for the OpenCom 510:

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

Name Description Page

MPS+1-AC Power supply with AC/DC transformer 55

MC+1-3 Central control module with three interfaces 57

MT+S2M1-1 Trunk module with one S2M interface for connecting to digital

networks or for cascading two PBXs

59

MX+S01-8 Trunk or subscriber module with eight S0 interfaces for either

external (trunk) or internal (subscriber) connections

62

MS+UPN1-8 Subscriber module with eight Upn interfaces for connecting

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

64

MS+UPN2-8 Subscriber module with eight Upn interfaces for connecting

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

65

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

67

MT+A1-4 Leitungsbaugruppe mit vier a/b-Schnittstellen für den Anschluss an analoge Netze

69

MT+A1-8 Leitungsbaugruppe mit acht a/b-Schnittstellen für den Anschluss an analoge Netze

69

MG+ETH1-1 Media Gateway module for VoIP 105

Overview of Available Modules Modules

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

MPS+1-AC

Field of ApplicationThe MPS+1-AC power supply unit supplies power to the first six slots (1 to 6) of the OpenCom 510. It con-verts 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.

MPS+1-AC: Front view

S0 1

S0 2

MX+S01-8

MPS+1-AC

55Modules MPS+1-AC

56

Technical DataThe following data refer to the sup-ply of power to the first six slots.

IndicatorsThere 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 con-stantly lit up green, the output voltage is –42 V.

The LEDs only indicate that the volt-age is present. They do not say any-thing about the voltage quality.

Operational InformationThe MPS+1-AC power supply unit will be ready for operation as soon as it has been plugged into the desig-nated slot (see Slots starting on page 22).

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

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

Input Voltage

Rated voltage 230 V via standard IEC connector

Voltage range 95 V to 275 V

Rated current 2.0 A at 115 V

1.0 A at 230 V

0.9 A at 275 V

Efficiency at rated load

> 80 %

+3.3 V Output Voltage

Rated voltage +3.3 V

Voltage range +3.2 V … +3.4 V

Rated current 10.0 A

Current limitation 12 A to 15 A

Short-circuit Continuous short-circuit protection

–42 V Output Voltage

Rated voltage –42 V

Voltage range –40 V … –44 V

Rated current 4.0 A

Current limitation 4.4 A to 5.5 A

Short-circuit Continuous short-circuit protection

MPS+1-AC Modules

MC+1-3

MC+1-3: Front view

Field of ApplicationThe 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 22).

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 Com-pactFlash slot interfaces.


■ 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) mem-ory.

Please note: This plug-in card must not be exchanged by service personnel. In the event of a malfunc-tion, the entire MC+1-3 central con-trol 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 fol-lowing data are stored on the CompactFlash card: the OpenCom 510 firmware, the sys-tem terminal software, the con-figuration data and all customer data such as audio files for the internal voice mail system.

Note: Only licensed cards may be used. These are currently (May 2004) special 256-Mbyte cards by SanDisk.

PCM

Ethernet

V.24-1

V.24-2

MC+1-3

57Modules MC+1-3

58

Contact your 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 in-terface pin assignment, refer to COM Port starting on page 44.

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

MC+1-3: LEDs

The LEDs indicate the following:

Operational InformationIf you need to exchange the central control module, shut down the sys-tem first! The OpenCom 510 must be disconnected from the mains supply (see Installing the Central Control Module starting on page 23).

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

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

MC+1-3

12

34

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

LED 2: Constantly green 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 The system is booting.

Constantly red System fault

LED 3: – Not used

LED 4: Constantly green An Ethernet connection has been established.

MC+1-3 Modules

■ 3 three-party conferences

■ 6 DTMF transmitters

■ 10 DTMF receivers

■ 1 Music On Hold

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

MT+S2M1-1

MT+S2M1-1: Front view

Field of ApplicationThe MT+S2M1-1 interface card pro-vides one ISDN S2M interface for con-necting the OpenCom 510 either to a primary rate access or to a second PBX (ISDN point-to-point connec-tion).

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


■ 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 config-ured 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

S2M

-42V

MT+S2M1-1

59Modules MT+S2M1-1

60

been installed it will automati-cally load the required software.

■ The maximum range is 300 m.

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

Pin AssignmentThe 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 59):

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 59):

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

MT+S2M1-1: LEDs



1 IN a

2 IN b

3 Not used

4 OUT a

5 OUT b

6 Not used

7 Not used

8 Not used


1 Not used

2 Not used

3 –42 V

4 0 V

5 0 V

6 –42 V

7 Not used

8 Not used

S2M

-42V

MT+S2M1-1

12

34

MT+S2M1-1 Modules

Operational InformationThe MT+S2M1-1 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deac-tivated in the Configurator in the web console (see Installing Interface Cards starting on page 25).

LED 1: Constantly yellow At least one connection established through the in-terface card is active.

LED 2: Constantly green The interface card is operational; the slot has been activated (flickering is normal).

Flashing yellow The interface card is ready, but the slot has not been activated or the interface card has not been config-ured yet.

Constantly red 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.

LED 3: Constantly green The interface card is providing the system clock sig-nal (indicated only in the master system and only on an interface card).

LED 4: – Not used

61Modules MT+S2M1-1

62

MX+S01-8

Field of ApplicationThe MX+S01-8 interface card pro-vides eight 8 S0 interfaces which can be used for either external connec-tions, i.e. to connect the OpenCom 510 to a digital network (PSTN, Public Switch Telephony Net-work), or internal connections, i.e. to connect digital terminals (ISDN tele-phones, 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 start-ing on page 22).


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

■ DIP switches S1 to S16 can be used to activate a 100-ohm ter-minal resistor (default: on).

For further information, refer to Termination starting on page 35.

■ 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 S0 interface with the eighth S0 interface in the event of a power failure; pro-vided the system has been con-

figured accordingly, external calls can be made using an emergency telephone.

For further information, refer to Power Failure starting on page 31.

■ All eight S0 interfaces can be configured either as subscriber (internal) interfaces or as trunk (external) interfaces.

For further information, refer to S0 Ports starting on page 34.

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

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

Pin AssignmentFor information on the S0 interface pin assignment, refer to S0 Ports starting on page 34.

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

MX+S01-8 Modules

MX+S01-8: LEDs


Operational InformationThe MX+S01-8 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deac-tivated in the Configurator in the web console (see Installing Interface Cards starting on page 25).

All three protocol layers can be indi-vidually configured as master or slave for each S0 interface.

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

S0 1

S0 2

MX+S01-8

12

34





LED 3: Constantly green The interface card is providing the system clock sig-nal (indicated only in the master system and only on an interface card).

LED 4: Constantly yellow The interface card is running a combination of sub-scriber and trunk connections, i.e. both internal and external S0 interfaces have been configured.

63Modules MX+S01-8

64

MS+UPN1-8

Field of ApplicationThe MS+UPN1-8 interface card pro-vides eight Upn interfaces for con-necting system terminals; however, it is not possible to connect DECT base stations.

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


■ 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 automati-cally load the required software.

Pin Assignment

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

MS+UPN1-8

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


1 Not used

2 Not used

3 Not used

4 Upn a

5 Upn b

6 Not used

7 Not used

8 Not used

UPN 1

UPN 2

MS+UPN1-8

12

34

MS+UPN1-8 Modules


Operational InformationThe MS+UPN1-8 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deac-tivated in the Configurator in the

web console (see Installing Interface Cards starting on page 25).

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

MS+UPN2-8

Field of ApplicationThe MS+UPN2-8 interface card pro-vides eight Upn interfaces for con-necting system terminals and DECT base stations.

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


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





LED 3: – Not used

LED 4: – Not used

65Modules MS+UPN2-8

66

■ In order to connect RFPs, Upn ports 1+2, 3+4, 5+6 or 7+8 can be combined by setting the DIP switches on the card accord-ingly.

For further information, refer to Upn Ports starting on page 38.

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

Pin AssignmentFor information on the Upn interface pin assignment, refer to Upn Ports starting on page 38.

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

MS+UPN2-8: LEDs


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

tivated in the Configurator in the web console (see Installing Interface Cards starting on page 25).

UPN 1

UPN 2

MS+UPN2-8

12

34





LED 3: – Not used

LED 4: – Not used

MS+UPN2-8 Modules

MS+A1-8

Field of ApplicationThe MS+A1-8 interface card pro-vides 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 start-ing on page 22).


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

■ The MS+A1-8 interface card supports pulse dialling as well as dual-tone multi-frequency (DTMF) dialling. The central re-ceivers of the MC+1-3 interface card are used for DTMF recogni-tion.

■ Calling line identification pres-entation (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 automati-cally load the required software.

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

Pin AssignmentFor information on the a/b interface pin assignment, refer to a/b Ports starting on page 40.

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

MS+A1-8: LEDs


a/b 1

a/b 2

MS+A1-8

12

34

67Modules MS+A1-8

68

Operational InformationThe MS+A1-8 interface card can be exchanged during operation, i.e. without powering down the system. However, the slot must first be deac-tivated in the Configurator in the web console (see Installing Interface Cards starting on page 25).





LED 3: – Not used

LED 4: – Not used

MS+A1-8 Modules

MS+A1-4 and MT+A1-8

Field of ApplicationDie Schnittstellenkarte MT+A1-4 stellt 4, die Schnittstellenkarte MT+A1-8 stellt 8 analoge Schnitt-stellen zum Anschluss analoger Netzanschlüsse (“analoge Amtslei-tungen”) zur Verfügung. Bis auf die Anzahl der Schnittstellen sind die Schnittstellenkarten baugleich.

The MT+A1-4/MT+A1-8 interface card can be installed in any of the slots (1 to 12) of the OpenCom 510 (see Slots starting on page 22).


■ The MT+A1-4/MT+A1-8 inter-face card can also be installed in a slave system.

■ The MT+A1-4/MT+A1-8 inter-face card supports pulse dialling as well as dual-tone multi-fre-quency (DTMF) dialling.

■ Die Ruferkennung funktioniert bei 16 2/3, 25 oder 50 Hz. Die analogen Netzanschlüsse sind galvanisch getrennt. Die länder-spezifische Anpassung der An-schlüsse erfolgt durch die Be-triebssoftware.

■ Die Anzeige der Rufnummer an-kommender Anrufe (CLIP), die Funktion Flash/Erdtaste und die

Erkennung eines Tarifimpulses werden nicht unterstützt.

■ The MT+A1-4/MT+A1-8 inter-face card runs on software ac-quired 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/MT+A1-8 inter-face card.

Pin AssignmentFor information on the a/b interface pin assignment, refer to a/b Ports starting on page 40.

IndicatorsThere are four LEDs on the front of the MT+A1-4/MT+A1-8 interface card.

MT+A1-4/MT+A1-8: LEDs

a/b

1a/

b 2

MT+A1-8

12

34

69Modules MS+A1-4 and MT+A1-8

70


Operational InformationThe MT+A1-4/MT+A1-8 interface card can be exchanged during oper-ation, i.e. without powering down the system. However, the slot must first be deactivated in the Configu-rator in the web console (see Install-ing Interface Cards starting on page 25).





LED 3: – Not used

LED 4: – Not used

MS+A1-4 and MT+A1-8 Modules

ConfigurationConfiguration and programming of the OpenCom 510 is performed by the Configurator, a special software application integrated into the sys-

tem. 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 configura-tion of the OpenCom 510,

■ configure users of the OpenCom 510 and authorise them to use certain system serv-ices,

■ carry out further system maintenance,

■ use PC-supported telephony functions,

■ read out call charge information,

■ access the OpenCom 510 tele-phone book.

The Web console has an integrated online help function that offers com-prehensive information on configu-ration and maintenance of the OpenCom 510 (see Loading the On-line Help starting on page 82).

Note: In order to use all the new system software functions, we recom-mend that you download the latest software from our Web site athttp://www.detewe.com.

71Configuration

72

For the initial configuration you can connect the PC to the OpenCom 510 via the Ethernet port. A COM port can also be used. The TCP/IP network protocol is used to set up a connec-tion via one of these ports. You can then open the Web console of the OpenCom 510 and call up the Con-figurator from there.

Note: This chapter describes initial configuration of the OpenCom 510. For day-to-day operation you can in-tegrate the OpenCom 510 into a LAN and start the Configurator from any PC. For information on how to do this, refer to the Configuration Examples starting on page 89.

Brief Guide to Initial Configuration

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

1. Turn off the PC. Remove all con-nected network cables.

2. Connect the PC network card to the LAN port. Use a cross-wired Ethernet cable to do this.

3. Restart the PC. If you manually deactivated the automatic con-figuration of the network card via DHCP, you must reactivate this and again restart the com-puter.

4. Start the Web browser. In the address field, enter “http://192.168.99.254/”.

The login page of the Web console will then open. For further details, please refer to Configuring the OpenCom 510 starting on page 80.

First Configuration via Serial Port

1. The serial port can also be used as alternative access for the first configuration.Additionally, you require a crossed serial line (“null modem”).Install the “oc-config” program from the prod-uct CD. To do this, you must log on as an administrator under Windows NT or Windows 2000/XP.

2. Shut down the PC. Remove all connected network leads. Con-nect the serial port of the PC to the COM port of the OpenCom 510.

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

Brief Guide to Initial Configuration Configuration

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

You will see the log-on page of the Web console. Continue reading un-der Configuring the OpenCom 510 starting on page 80.

System Requirements

Note: If no connection can be es-tablished by following the instruc-tions in the Brief Guide to Initial Con-figuration starting on page 72, refer to the more detailed explanations be-low.

A normal TCP/IP-capable PC with a Web browser is required for the ini-tial configuration. The PC should at least meet the following require-ments:

■ IBM-compatible 200 MHz PC

■ 32 MB RAM and 50 MB of free hard disk space

■ Microsoft Windows 95/98, Microsoft Windows 2000/XP or Microsoft Windows NT 4.0 oper-ating system

■ Microsoft Internet Explorer ver-sion 4.0 or higher, or Netscape Communicator version 4.5 or higher

Note: Microsoft Internet Explorer is already installed in current versions of the Microsoft Windows operating

system. If required, a Web browser can be installed from the product CD delivered with the OpenCom 510.

In addition, the selected type of con-nection requires further system components that you may have to install on your PC. The driver soft-ware is normally supplied with the hardware, and the appropriate ver-sion should be available for your op-erating system. You will find the sys-tem software on the installation CD of your operating system.

For connection on the V.24 port (COM port) you need:

■ Hardware: one free serial port (RS-232, V.24) and a serial cable (SUBD9). System software: se-rial port driver and TCP/IP proto-col software

■ Driver software: RAS adapter software for installation on the service PC (is included on the CD)

For connection by network card you need:

73Configuration System Requirements

74

■ Hardware: network card with 10BaseT port and RJ-45 network cable (crossover twisted pairs or connection via a hub)

■ Software: network card driver and TCP/IP protocol software

Configuration under Windows

Before beginning initial configura-tion, install the necessary hardware and matching driver software on the PC. Follow the installation instruc-tions supplied with the hardware. In many cases, the TCP/IP system soft-ware is installed together with the driver software for the hardware. When you have installed the driver software, proceed as follows:

Note: The following steps are not necessary under Windows 2000/XP. If possible, use a network card connec-tion as network cards are easier to configure and feature higher data transfer rates. For more information please read Connection by Network Card (LAN) starting on page 76

1. Open “Network Settings” in the Control Panel of your PC. To do this, you select the item “Set-tings > Control Panel” from the Start menu and double-click on the “Network” icon. Under Win-dows NT, select the “Protocols” tab.

2. Check the list of installed com-ponents to see whether the TCP/

IP protocol is present. If neces-sary, install TCP/IP by clicking on the “Add” button.

3. Select “TCP/IP” from the “Proto-col/Microsoft” folder and con-firm your entry with “OK”.

4. Then follow the installation in-structions displayed.

Depending on the type of connec-tion (network card or V.24) you se-lect, note the following when install-ing the driver and system software.

Connection on Serial Port (V.24)

The required components are nor-mally ready installed together with the operating system. In this case, you can easily configure the connec-tion to the OpenCom 510 by using the program “occonfig”:

Note: Under Windows NT or Win-dows 2000/XP you must log on as an administrator.

Configuration under Windows Configuration

1. Insert the product CD supplied along with the OpenCom 510.

The CD starts automatically if your PC is configured accord-ingly. Otherwise select “Run” in the Start menu. Use the “Browse” button to find the “cd_start.exe” program on the CD. Confirm your entry with “Open” and “OK”.

2. Select the “Software, installation program for RAS network link” option from the start mask. Click on “OK” to install the modem driver.

3. In the dialogue that follows, se-lect a serial port and confirm this with “OK”.

After restarting your computer, you will find an icon for the connection to the OpenCom 510 on your desk-top.

Note: If this procedure cannot be completed properly, refer to the sec-tion entitled Notes on Configuring the Serial Port on page 76.

Establishing a Remote Data Transfer Connection

1. Connect the serial port of the PC to the OpenCom 510 COM port. You will require a suitable con-nector cable.

2. Double-click on the OpenCom desktop icon created with the “occonfig” program.

3. In the dialogue which follows, enter the user name and pass-word valid for the OpenCom 510 user account being used. For the initial configuration, log on un-der the user name “Administra-tor” without giving a password. Clear any entries in the “Do-main” box and confirm this with “OK”.

When the connection is estab-lished, all necessary IP address parameters will be transmitted by the OpenCom 510 using the PPP protocol and automatically set for the direct PC link.

4. Once set-up of the connection is confirmed, you can continue with Testing the Setup starting on page 77.

Note: It is not possible to operate a network card and a remote data transfer connection for the same net-work address range simultaneously. For this reason you must temporarily deactivate the network card when you want to establish a remote data transfer connection. To do this, open the “System” icon in the Control Panel and deactivate the network card in the “Devices” tab. If the PC is config-ured via DHCP, you can instead also disconnect the PC from the LAN and reboot it.

75Configuration Configuration under Windows

76

Notes on Configuring the Serial Port

A serial port is automatically de-tected when the PC boots and the corresponding system software is in-stalled. The TCP/IP connection to the OpenCom 510 is established by means of additional system soft-ware: the RAS adapter software and the serial port driver.

Tip: The serial port that you use is operated with the parameters 57,600 baud, 8 data bits, 1 stop bit, no parity and no hardware data flow control.

Note: The RAS network is always installed under Windows 2000/XP and cannot be uninstalled. The fol-lowing section is only relevant for us-ers of old Windows versions.

Installing the RAS Network under Windows 95 or Windows 98

1. Open the Control Panel and dou-ble-click on the “Software” icon.

2. Click on the “Windows Setup” tab and double-click on the item “Communications”.

3. Tick the check box next to the component “RAS Network” and confirm your entry with “OK”.

Installing the RAS under Windows NT 4.0

1. Open the Control Panel and dou-ble-click on the “Network” icon.

2. Select the “Services” tab and click on the “Add” button.

3. Select “Remote Access Service” from the list and confirm with “OK”.

4. To conclude installation of the RAS, the RAS “Properties” dia-logue is displayed. Select the driver “OpenCom Modem” that was created on the first start of the program “occonfig” and con-firm this with “OK”.

5. Confirm the configuration with the “Continue” button and close the network settings.

Note: If you have installed an oper-ating system update earlier (Service Pack), install this again after installa-tion of the RAS.

Connection by Network Card (LAN)

First-time configuration of the OpenCom 510 is also possible by a network card, providing this is al-ready installed on the PC, of course.

When the driver software for a net-work card is installed, the necessary


system software for the TCP/IP pro-tocol is installed at the same time. During this process you should acti-vate the automatic assignment of IP addresses by the DHCP protocol.

If the PC has been operating in a net-work to date, you should activate the automatic assignment of an IP ad-dress.

1. To do this, you select “Settings > Control Panel” in the Start menu. Double-click on the “Net-work” icon. Under Windows NT select the “Protocols” tab. Un-der Windows 2000/XP right click on the “LAN Link” icon. Select “Properties”.

2. Double-click on the item “TCP/IP Protocol > Network card”. Acti-vate the option “Obtain an IP ad-dress from a DHCP server” in the “Properties” dialogue. Gateway or DNS entries must be deacti-vated.

Note: Changes to the Gateway and the DNS configuration are made by DHCP.

Establishing a Network Connection

1. Connect the PC network card to the OpenCom 510 network port. To do this, use either a crossover twisted-pair network cable or connect the OpenCom 510 via a hub.

Note: For initial configuration, it may be wise not to connect the OpenCom 510 to an existing LAN in order to eliminate conflicts with an existing DHCP server.

2. Restart your PC. During the sys-tem start, all necessary IP ad-dress parameters will be trans-mitted by OpenCom 510 via DHCP and automatically set for the network card.

Note: If the PC has been operating under Windows NT in a network with a Windows NT domain, you will not be able to log on to the domain. So log on to the PC domain as the local user “Administrator”.

3. Continue reading under Testing the Setup starting on page 77.

Testing the Setup

Subsequent to establishment, test the TCP/IP connection between the OpenCom 510 and the PC.

1. Select the item “Run” in the Start menu. Enter the command “ping host.domain” or “ping 192.168.99.254” in the “Open” box.

2. Confirm this with “OK”.

Tip: To find the IP address of the Web console, enter *182

on a connected system telephone.

77Configuration Configuration under Windows

78

*183 will also show you the network mask.

You can test the correct IP configura-tion under Windows 95 and Win-dows 98. Select the item “Run” in the Start menu. Enter the command “winipcfg” in the “Open” box. Con-firm this with “OK”. Select the net-work adapter used for connection to the OpenCom 510. The IP addresses assigned by the OpenCom 510 on es-tablishment of the connection will be displayed. Under Windows NT4, 2000 and XP you can check the IP configuration by entering the commands “ipconfig -all” or “route print” in the command prompt. The command “arp -a” pro-duces a list of assigned IP addresses for LAN links.

Starting the Browser

Start the installed Web browser.

When you start the Microsoft Inter-net Explorer for the first time, the In-ternet access wizard will automati-cally appear. Select the option “Use existing account” and confirm this with “OK”.

If the PC has been operating in a net-work or used for Internet access, it is possible that access may be config-ured indirect via a proxy server. De-activate access via a proxy server (“Direct connection”). To do this in the Internet Explorer, open the Inter-

net options in the menu “Tools > In-ternet Options”, then select the “Connections” tab. In Netscape Com-municator, you select the command “Edit > Settings” and then select the section “Extended > Proxies” under “Category”.

Note: Reset your browser’s options for the call-up of pages to their de-fault settings specified on initial in-stallation of the browser.


Configuration for Linux and MacOSAll modern operating systems sup-port the TCP/IP protocol. You can find detailed information on setting up hardware and software for the Windows operating systems under Configuration under Windows start-ing on page 74. In this section there are tips on integrating Linux and MacOS operating systems.

Linux

The Linux network configuration is usually performed by the set-up pro-gram with which you install a Linux distribution. After installation, you will see a series of “How To's”. In “Linux NET-3-HowTo” and “DHCP Mini-HowTo” you will find instruc-tions on TCP/IP configuration.

For the OpenCom 510 to configure the TCP/IP settings of a Linux system via DHCP, you must also install the “dhclient” package and activate con-figuration via DHCP in the Linux net-work configuration. To access the OpenCom 510 Configurator, you should also install Netscape Commu-nicator 4.5 (or higher).

MacOS

The TCP/IP protocol is already inte-grated in the new MacOS starting with version 7.6. For the OpenCom 510 to configure the TCP/IP settings of a MacOS system via DHCP, you must set the configura-tion method to “DHCP Server” in the menu “Control Panels TCP/IP”.

To access the OpenCom 510 Config-urator, you should also install Net-scape Communicator 4.5 (or higher) or Microsoft Internet Explorer 4.5 (or higher).

79Configuration Configuration for Linux and MacOS

80

Configuring the OpenCom 510

Preparing the Configuration

Before starting with the configura-tion, make sure you have the follow-ing documents at hand:

■ An overview of the ports

■ A list of the terminals to be con-nected

■ A list of the IPEIs, if you wish to log on DECT terminals in the se-cure 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 in-ternal call numbers you want to allocate to them

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

Data not available for first-time con-figuration can be updated or cor-rected at a later date.

Note: Use the Configuration Guide starting on page 152. This will assist you in making the settings in the cor-rect sequence.

Starting the Web Console

1. 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: Easy Access menu).

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

Configuring the OpenCom 510 Configuration

OpenCom 510: log-on dialogue box

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

- user name: “Administrator”- password: for the initial config-uration, leave this box blank.

4. Confirm this by clicking on OK. This puts all connected termi-nals into the “Guest” user group with restricted user rights. In this way you prevent interna-tional external calls from the ter-minals, for example, while you are configuring the OpenCom 510 and the users.

81Configuration Configuring the OpenCom 510

82

OpenCom 510: dialogue box for initial access

5. The software opens a dialogue for initial access. Determine an administrator password and en-ter it in this dialogue.

6. Confirm your input with Apply.

7. Click on the Configurator but-ton on the home page.

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

Loading the Online Help

The online help can now be loaded in the Configurator:

1. Go to the SYS Configuration: Components menu. Select the entry Online Help and click on Browse.

2. Look for one of the language-specific ZIP files in the OLH di-rectory of the product CD. Con-firm your choice by clicking on Open.

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

Please note: After completion of the loading operation, the system will


take a few minutes to analyse the transferred file.

Note: You can downed the latest version of the online help fromhttp://www.detewe.de/.

Finishing the Configuration

1. When you have completed all the settings in the Configurator, you must save the configuration (see also Saving and Loading the Configuration on page 86).

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

Preconfiguration

Configuration of the OpenCom 510 can be prepared at your DeTeWe Customer Service Centre or by an au-thorised DeTeWe dealer. For this pur-pose, a OpenCom 510 installed here is programmed with the customer data (e.g. user data, call distribution schemes, cord-bound terminals). This data is stored and then loaded into the OpenCom 510 at the cus-tomer’s site by a service technician.

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

For configuration of the OpenCom 510 Internet functions, first ask the responsible system ad-ministrator for details of the cus-tomer’s LAN prerequisites.

Offline Configurator

With the aid of the offline configura-tor a configuration for the system can be issued and created on a Win-dows PC. Thereby most of the con-figuration points are available. Each system type of the product family and firmware version release 7.0 or higher, has its own offline configura-tor; this is managed with the aid of a starter program. The starter pro-gram is included on the product CD. The operating systems Windows 2000 and XP are sup-ported.

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

Remote Configuration

The OpenCom 510 configuration can also be altered or updated remotely by a customer service centre or au-thorised dealer. This requires activa-tion of internal RAS access in the OpenCom 510 for the customer serv-ice centre/authorised dealer.


84

Note: If one or more MSNs are en-tered on the PBX Configuration: Sys-tem: Remote service menu page in the Configurator and the Status op-tion is activated, remote configura-tion access is then activated when a data call from one of the entered MSNs is registered.

The customer service centre/author-ised dealer can then log into the OpenCom 510 as an administrator:

■ User name: “Administrator”

■ Password: [administrator pass-word]

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

Use the following code digit proce-dure on a standard terminal or a sys-tem 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 can-celled 30 minutes after the last con-figuration activity.

Note: During remote configura-tion, 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 adminis-trator changes it to prevent undesira-ble remote maintenance.

Using remote configuration, all OpenCom 510 settings (with the ex-ception of the system PIN) can be edited or updated. New software versions of the OpenCom 510 and the software for the connected sys-tem 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 ad-dress conflicts). Refer to the chapter entitled Configuration Examples starting on page 89, where interac-tion between the OpenCom 510 and a LAN is explained.


Forced logoff of another user by the administratorThe configuration of the system can always only be edited by one user. Working on the configuration in par-allel is not possible. This ensures that no configuration conflicts arise.

If the user “Administrator” logs in and another user with administra-tion rights is already logged in, then the administrator can forcibly log the other user off in order to config-ure. This functionality, for example can be used, when configuring re-motely, when a user has forgotten to log out.

In order to forcibly log a user off:

1. The “Administrator” user logs-in with the administration pass-word.

2. They open the Configurator.

A message shows which user is currently configuring the sys-tem.

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

The other user can make no fur-ther modifications of the config-uration.

Codes for IP Configuration

The IP configuration of the OpenCom 510 is performed on the Web console in the Configurator, in the NET Configuration: Easy Access menu.

In the event that the IP configura-tion 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.

Ask your system administrator for the OpenCom 510 system PIN. The factory setting is “0000”.

Set IP addressH *182 Z (system PIN) * Z (www) * Z (xxx) * Z (yyy) * Z (zzz) #

Set NET maskH *183 Z (system PIN) * Z (www) * Z (xxx) * Z (yyy) * Z (zzz) #

RestartH * 1 8 5 Z (system PIN) #


86

Saving and Loading the Configuration

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

The following configuration and cus-tomer data can be saved and loaded again:

■ Telephony and network parame-ters

■ User data

■ Telephone book entries

■ LCR tables

For further information, refer to the online help documentation under the topic SYS Configuration: Data backup.

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 mes-sages) can be sent via e-mail.

In order not to notified every error, the administrator can define corre-sponding log filters (in the Configu-

rator, the LOG Configuration: LOG Filter menu). These filters de-fine which errors (category, severity, number per time interval) should be notified. The e-mails always include an internal event or error number, as well as an explanation of the mes-sage. Further, extra parameters (as for example the port number when a trunk line drops out) are also pro-vided.

The mail account for this service (Ac-count for LOG filter) is configured in the Configurator, NET Configuration: E-Mail Access.

Loading SW Updates

New versions of the system and ter-minal 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 Configu-ration: Firmware menu). For infor-mation on connecting a configura-tion PC, see Brief Guide to Initial Configuration on page 72.

The terminal software is part of the OpenCom 510 software and is auto-matically 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.

Resetting the System Data

You can restore the factory settings of the OpenCom 510 in the Configu-rator.

Please note: If this is done, all in-dividual settings and the user data are then lost. For this reason, you should back up your configuration regularly, the best time being after every change. For details, refer to the chapter entitled Saving and Loading the Configuration starting on page 86 and to the Web console online help.

Proceed as follows:

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

2. Click on Restart with Defaults.

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

Generating Your Own MoH Files

The OpenCom 510 comes with an in-ternal MoH file for Music on Hold. The OpenCom 510 product CD con-tains a number of MoH files with dif-ferent volume levels, which you can load at a later time as necessary.

The file format for non-resident Mu-sic 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 Re-corder” program to generate your own MoH file. This program is usu-ally located in the Windows direc-tory called “Multimedia”.

The MoH file must be coded with 8000 Hz, 8 bit mono in accordance with CCITT, A-Law. This coding is re-quired 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 al-lowable size for a MoH file is 256 KB (approx. 32 sec. play time). If a larger file is loaded then this will be “trun-cated” and thereby will also only be played for 32 seconds.

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


88

Load your MoH file in the Web con-sole's Configurator, in the SYS Con-figuration: 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

One of the outstanding features of the OpenCom 510 is the integration of telephony and computer net-works. 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 tele-phone functions can be used on a PC

■ the OpenCom 510 central tele-phone book and your personal telephone book as well as to the

company telephone book (if the multi-company variant is acti-vated).

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

The following LAN prerequisites are possible:

Server configuration in the LAN OpenCom 510 Functions

No IP server present OpenCom 510 functions automatically as DHCP and DNS server

IP server present

DHCP server present

OpenCom 510 functions automatically as DHCP client

System Administrator must assign IP address and DNS name for OpenCom 510

IP server present

No DHCP server present

Special case when integrating the OpenCom 510 in a LAN; settings in the NET Configuration: Easy Access menu must be coordinated with the respon-sible system administrator

89Configuration Examples OpenCom 510 in Computer Networks

90

Introduction to TCP/IPIn a single LAN it is possible to use various protocols for the transmis-sion of data. The connection be-tween a workstation computer and the OpenCom 510 runs via the TCP/IP protocol used on the Internet. TCP/IP can be used together with other protocols (e.g. NetBEUI, Apple-Talk or IPX/SPX) on the same net-work.

Every device participating in data transmission using TCP/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 net-works normally use IP addresses in which the first three numbers are the same and the last number is uniquely assigned to a specific de-vice in the LAN. On the Internet, unique addresses assigned by a spe-cial organisation created for this pur-pose are used. Within a LAN, you can use addresses which are not unique world-wide.

TCP/IP enables the establishment of connections via one or more inter-mediate stations. The decision whether to connect directly or indi-rectly 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 es-tablished 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) re-solves a plain text DNS name into an IP address. The DNS is a hierarchi-cally structured database, distrib-uted worldwide. A DNS server can supply information on the names and IP addresses for which it is re-sponsible. For all other information, a DNS server contacts other DNS servers. For the establishment of every connection from the worksta-tion, 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.

Introduction to TCP/IP Configuration Examples

OpenCom 510 in a Serverless LANIn a peer-to-peer network, the work-stations are connected to one an-other via network cables. In many networks, the cables run in the form of a star from a central hub. Such networks do not require special servers. This configuration example is also valid for a LAN with a server using a protocol other than TCP/IP (e.g. AppleTalk or IPX/SPX).

The OpenCom 510 in a serverless LAN

In a serverless LAN, the OpenCom 510 takes over the IP con-figuration of the connected worksta-tions. All TCP/IP settings necessary for the workstations are assigned by the OpenCom 510 via DHCP (dy-namic host configuration protocol). In this operating mode, an IP ad-dress space reserved for such net-works is used:

OpenCom(DHCP, RAS,

int. DNS, Internet)

S0 Net

PC 2

Net

ISP(DNS)

S0

Ext.PC

S0

PC 1

Net Hub

192.168.99.254 OpenCom 510 IP address

192.168.99.129 to 192.168.99.148 DHCP addresses: IP address space for work-stations

192.168.100.0 to 192.168.100.10 PPP addresses: IP address space for RASdialling

255.255.255.0 Network mask (class C network)

192.168.99.254 DNS server IP address

192.168.99.254 Default gateway IP address

91Configuration Examples OpenCom 510 in a Serverless LAN

92

Install the TCP/IP network protocol and a Web browser for every work-station which is to have access to the OpenCom 510 network features.

For notes on installing network cards, refer to Connection by Network Card (LAN) on page 76.

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 Con-figurator 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 worksta-tions by the OpenCom 510. The OpenCom 510 is not visible in the network environment.

Internet Access

If access to an ISP has been config-ured 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 In-ternet connection request to the OpenCom 510.

In almost all cases, the request will contain a DNS name which is un-known in the internal network. When you type a URL into your browser, the OpenCom 510 receives the request to find the correspond-ing IP address. If the name is un-known in the LAN, the request is for-warded to an ISP’s external DNS server.

Note: Workstation PCs automati-cally add a domain name to URLs without a dot. You specify this do-main 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 re-quest which does not lead to the es-tablishment of an Internet connec-tion. 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).

OpenCom 510 in a Serverless LAN Configuration Examples

RAS Access

You can establish a connection from an external computer with an ISDN card to the OpenCom 510. The nec-essary TCP/IP settings are transmit-ted by the OpenCom 510 on estab-lishment of the connection. The computer that has dialled in now has access to all services in the LAN capable of being used via TCP/IP. The authorisation for RAS access is set up in the Configurator via the User Manager: User Groups menu.

In a serverless LAN, Windows uses the NetBIOS protocol for accessing files and printers via the network en-

vironment. NetBIOS can use Net-BEUI, IPX/SPX or TCP/IP as the trans-port protocol. In the network environment, you can only access files and printers on workstations us-ing TCP/IP for NetBIOS.

Note: In a serverless LAN, the work-stations running decide independ-ently which one is to keep the list of names visible in the network environ-ment. This process is triggered by broadcasts, which can take some time on a RAS connection. You can shorten this period by activating the “Find > Computer” function in the Start menu and selecting the client computer.

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 responsi-ble 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.

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

OpenCom

S0 Net

PC 2

Net

S0 int

Server(DHCP, RAS,

int. DNS,Internet)

S0 Net

ISP(DNS)

S0

Ext.PC

S0

PC 1

Net Hub

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

94

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

In networks in which the TCP/IP set-tings are made manually, you have to enter the corresponding TCP/IP settings in the OpenCom 510 Con-figurator (NET Configuration: Easy Access menu). Here the OpenCom 510 acts as the DHCP server. A workstation requesting the TCP/IP settings via DHCP then re-ceives the settings you made in the Configurator.

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 in-formation, refer to the server docu-mentation.

Note: To access the OpenCom 510 under the same IP address after a re-start, 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 de-tails in the server documentation.

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 configura-tion so that the resolution of exter-nal DNS names is forwarded to the OpenCom 510.

In this example, the Internet connec-tion is established from a worksta-tion via the server, which in turn re-quests Internet access from the OpenCom 510.

There are two different ways of suit-ably 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 explana-tion, refer to the DNS server docu-mentation.

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

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

RAS Access

In a LAN with an IP-enabled server you can also enable external com-puters to dial in via the OpenCom 510. To do this, you should coordinate with the network admin-istrator the IP address space which can be assigned to an external com-puter dialling in, and enter it in the Configurator, NET Configuration: Easy Access menu, under PPP Ad-dresses.

The user account administered by the OpenCom 510, with which dial-ling in is permitted, only allows the establishment of direct and anony-mous 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 ac-

count and the same password for the network log-in, you have to en-ter this combination only once when dialling in.

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

Note: In a larger Windows network with several segments, the lists of computer names visible in the net-work 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. For this reason, you enter the address of a WINS server manually in the network settings of the workstation.

OpenCom(Internet)

S0 Net

PC 2

Net

S0 int

Server(DHCP, RAS,

int. DNS)

S0 Net

ISP(DNS)

S0

Ext.PC

S0

PC 1

Net Hub

OpenCom(RAS, Internet)

S0 Net

PC 2

Net

Server(DHCP,

int. DNS)

Net

ISP(DNS)

S0

Ext.PC

S0

PC 1

Net Hub

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

96

LAN-to-LAN LinkYou can use the OpenCom 510 to in-terlink 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 (subnet-works). For at least one of the OpenCom 510 systems, change the prescribed address range for the LAN.

The OpenCom 510 in a LAN-to-LAN link

In the Configurator, NET Configura-tion: LAN-LAN menu you can con-figure the dial-in settings. The OpenCom 510 will set up a connec-tion whenever a TCP/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 Win-dows network, you need an IP-ena-bled server that administers the name resolution for the Windows network.

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

OpenCom(IP=192.168.99.254,Net=192.168.99.0)

S0Net

PC 2

Net

PC 1

Net Hub

OpenCom(IP=192.168.11.254,Net=192.168.11.0)

S0 Net

PC 2

Net

PC 1

Net Hub

LAN-to-LAN Link Configuration Examples

Useful Information on Internet Access

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 transmit-ted.

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 Inter-net connection to be established, even if these programs are not strictly Internet-associated applica-tions.

Examples of such programs are the MicrosoftTM XPTM operating system, various multimedia programs such as RealplayerTM and anti-virus appli-cations that may establish an Inter-net connection for automatic up-dates (the so-called “phone home function”).

It is therefore highly advisable to limit ISP access by specifying the maximum monthly connection time under Connection time per month (maximal) in the NET Configura-tion: Connections: ISP menu on the web console.

Using the Web

A Web browser not only enables you to use the OpenCom 510 Configura-tor 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 re-spects:

■ When you request a Web page, dialling in results automatically. There is no display of dialogues with manual confirmation of di-alling 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, specifia-ble duration.

■ It is possible to call up Web pages simultaneously from sev-eral workstations.

■ The OpenCom 510 can block ac-cess to certain Web pages by means of filter lists.

97Configuration Examples Useful Information on Internet Access

98

E-mail

One of the most important services in the Internet is e-mail. E-mails are buffered in individual e-mail ac-counts 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 ac-counts 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 noti-fied of the new e-mail on his system terminal. OpenPhone 6x and OpenPhone 2x system terminals can also display information such as the sender or the subject of the e-mail.

NAT

Network address translation (NAT) is activated on accessing the Internet (ISP). You require this feature in or-der 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 TCP/IP connections trig-gered 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 Inter-net on a workstation.

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

■ TCP/IP addresses are trans-ported in the useful load, e.g. NetBIOS over TCP/IP.

■ The protocol requires an active, inward-directed connection es-tablishment, e.g. ICQ.

Useful Information on Internet Access Configuration Examples

■ The protocol will function with-out TCP/UDP port numbers, e.g. ICMP or IGMP.

The OpenCom 510 NAT has suitable processes for ensuring the functions of many important protocols af-fected by these rules. These are the protocols FTP (in “active” mode), Cu-SeeMe (“videoconferencing”), IRC (“chat”), ICMP errors (“traceroute”) and ICMP echo (“ping”).

Protocols which require inward-di-rected connection establishment can be configured in the Net Config-uration: Port Access menu. For fur-ther information, refer to the online help of this menu.

99Configuration Examples Useful Information on Internet Access

100

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

■ Telephony via Internet: Offers cheaper charge-models for te-lephony services. For telephony directly via Internet, only the costs for the data transmission are incurred. Various Gateway-Services provide, for a fee, cross-over into the PSTN (“Public Switched Telephone Network”). Besides standardised protocols such as SIP and H.323, proprie-tary protocols, for example Skype network, are utilised. The voice and service quality, via In-ternet, is often indeterminable as you are dependent on the routes, optimised for data com-munication, of various service providers.

■ Telephony via Intranet: Offers the joint usage of existing infra-structure for telephony and data communication. In particular the integration of two commu-nication networks into a single communications network opens considerable possibilities for savings. The OpenCom 510 im-plements several system teleph-ony features with the aid of an IP based protocol. The control of

the utilised data-lines makes it possible to define exactly the voice and service quality.

This chapter only explains the VoIP system telephony via Intranet. For VoIP via Internet, you can use suita-ble Gateway Products.

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

■ Operation of IP based system telephones connected to Cat5 Twisted-Pair-Ethernet lines

■ Operation of IP based system telephones also via VPN, RAS, LAN-LAN or WLAN connections

■ Using voice-data compression codecs, it is also possible to have multiple simultaneous IP based telephone calls via a 64 kilobit/s ISDN line

■ Operation of PC-supported sys-tem telephones (so-called “Soft-phones”) without extra hard-ware costs

■ TC-system-networking using Q.SIG-IP via VPN, RAS, LAN-LAN or WLAN connections (see also PBX Networking starting on page 116)

Voice over IP (VoIP)

The integration of voice and data communication within the Intranet makes savings possible and opens up new possibilities. However the joint usage of an existing network infrastructure also yields configura-tion possibilities, for example, for the IP address configuration via

DHCP (details below Start Procedure starting on page 110). Therefore al-ways plan the deployment of VoIP in the Intranet together with the net-work administrator. This chapter provides aids for you to avoid possi-ble problems.

Fundamentals

VoIP makes the transmission of voice and telephony signalling via IP (“In-ternet Protocol”) possible. After con-nection creation, voice data (PCM data) is collected by the terminal and is then sent, using an IP packet, to the receiver. Additionally the PCM data can be compressed in order to save bandwidth.

Propagation Delay and Bandwidth

IP based data networks are generally not capable of guaranteeing a spe-cific minimum bandwidth and a de-fined propagation delay. A synchro-nised 64 kilobit/s ISDN line guarantees a fixed data rate so-long-as the connection exists. In a IP based data network, the data rate and propagation delay can vary. Short-term bottle-necks or retrans-mission in case of errors can be the cause. Whereas when fetching a Web page an interruption of the

data flow of a matter of seconds is not noticeable, it is very bothersome during a telephone call.

A modern Intranet normally offers enough performance reserves and reliability to make VoIP telephony possible in very good quality. Spe-cific components can, potentially, be optimised; for example via the usage of a modern Switch which evaluates the TOS byte of an IP packet or via the replacement of unreliable con-nections.

Latency and Packet Length

There is always a technical-qualified delay (“latency”) between the re-cording of voice data via the micro-phone and the playback via the re-ceiver. In order to be able to send it in an IP packet, voice data is re-corded for a short timeframe. Addi-tionally the IP packet has a signal-

101Voice over IP (VoIP) Fundamentals

102

propagation-delay before the re-ceiver can be begin with playback. The extra time required for voice-data encoding and decoding can, for these considerations, be neglected.

An IP packet consists of protocol data and user data. Sending shorter voice-data packets causes the ratio between user data and protocol data to become unfavourable and the re-quired effective bandwidth rises. Sending longer voice-data packets causes the latency to rise.

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

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

Voice Quality

The achievable voice quality de-pends on various factors. With the proffered configuration settings it is possible to optimise the voice-data transmission for the existing net-

work. Potentially a measurement of the network quality can help.

The following comparison provides a guide for the voice quality with spe-cific quality levels:

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

Packet Length (ms)

G.711 (not compressed)

G.729A c. 6.3 kilobit/s

G.723.1 6.3 kilobit/s

G.723.1 6.3 kilobit/s

20 180.8 68.8

30 51.2 48.0 45.9

40 42.4

50 37.12

60 33.6 30.4 28.3

70 31.09

80 29.2

Fundamentals Voice over IP (VoIP)

During call creation the involved ter-minals negotiate the voice-data compression (“codec”) that will be used. This is the first factor that de-termines the achievable quality level:

■ G.711 A-Law (Level 1, uncom-pressed): The audio data of a PCM channel (64 kilobit/s) are adopted one-to-one. Every VoIP terminal must support this co-dec. 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.

It can be possible that the voice quality is reduced due to an unfa-vourable selection of the packet length. For this selection, the dura-

tion of the recording not the byte count of the data packet is relevant:

■ Duration <= 30 ms: optimal transmission

■ Duration 40 - 60 ms: one quality-level depreciation

■ Duration > 60 ms: two quality-levels depreciation

Additionally, the achievable voice quality depends on the packet prop-agation delay and the packet lose between the terminals involved. These parameters can be deter-mined with the “ping” programme.

Note: Measurements made with “ping” are round-trip propagation de-lays. Divide the maximum value dis-played by two.

Quality Levels for Voice Transmission with VoIP

Level Voice Comprehensibility Comparable to

1 Very Good ISDN

2 Good DECT

3 Satisfactory GSM

4 Limited Defective GSM

> 4 Unacceptable No Connection

103Voice over IP (VoIP) Fundamentals

104

Optimisation

If during the measurement you de-termine a large fluctuation in the propagation delay, then this can also cause a depreciation in the voice quality. This is potentially an indica-tion of a defective or overloaded line caused by bit-error or collision cor-rection resulting from retransmis-sion by the transmission-procedure.

It is possible that an existing star-to-pology ethernet-network uses an Hub as central distributor of ether-net packets. A Hub repeats on all connected lines all received ethernet packets. This can cause substantial collisions and thereby result in a

high fluctuation in the propagation delay.

In this case, deploy a modern Switch component. The selective forward-ing of ethernet packets (“Layer 2 Switching”) avoids collisions. Mod-ern Switch components, further-more, evaluate the TOS byte of an IP packet and thereby afford the opti-mal 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 re-quests “Minimise Delay” and “Maxim-ise Throughput” for IP packets marked with this value.

Packet Propagation Delay and Packet Loss

Value Quality Level Value Quality Level

Propagation delay< 50 ms

Optimal Loss < 1 % Optimal

Propagation delay 50-100 ms

0.5 level depreciation

Loss 1-2 % 0.5 level depreciation


1 level depreciation Loss 2-3 % 1 level depreciation





Propagation delay> 300 ms

4 level depreciation Loss > 6 % 4 level depreciation

Fundamentals Voice over IP (VoIP)

Media Gateway (MGW)The Media Gateway transforms VoIP voice data into PCM audio data. This functionality converts voice data be-tween VoIP telephones and all other terminal types. Without the Media Gateway, VoIP telephones can only exchange call data directly with other VoIP telephones. Even an ex-ternal telephone call with an VoIP telephone requires the Media Gate-way functionality. For a maximum of three VoIP terminals, one Media-Gateway channel should be availa-ble.

Using the OpenCom 510, the Media Gateway is accomplished with at least one MG+ETH1-1 interface card.

MG+ETH1-1

Field of ApplicationThe MG+ETH1-1 interface card pro-vides 16 Media Gateway channels for VoIP.

The MG+ETH1-1 interface card can be installed in any of the OpenCom 510’s slots (1 to 12, see also the chapter Slots starting on page 22). Up to four MG+ETH1-1 in-terface cards can be operated.

Technical Data

■ Via the ethernet port (10/100 Mbit/s) the OpenCom 510 can be connected to the LAN.

■ The interface card supports: all codecs used by VoIP telephones, silence detection, echo suppres-sion and DTMF tone detection.

■ The interface card can not be op-erated 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.

■ No settings need to be made on the interface card.

Pin AssignmentThe ethernet port’s pin-assignment is designed for a direct connection, via a RJ45 patch cable, to an ether-net Switch. For a connection to a PC, you will require a cross-link cable (“Cross-over Cable”).

IndicatorsThere are four LEDs visible on the front of the MG+ETH1-1 interface card.

105Voice over IP (VoIP) Media Gateway (MGW)

106

MG+ETH1-1: LEDs

The LEDs have the following mean-ing:

Operational InformationThe 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 in the Config-urator in the Web console (see also Installing Interface Cards starting on page 25).

Each MG+ETH1-1 interface card re-quires its own IP address. This can ei-ther be assigned statically or ob-tained via DHCP.

1. In the Configurator, open the PBX Configuration: Ports: Slots page.

2. Click on the slot number in the table row containing the desired interface card.

3. Enter the desired static IP ad-dress in the IP address config-ured field. Enter “0.0.0.0” to ob-tain an IP address via DHCP.

4. Confirm with Apply.

ETH

MG+ETH1-1

12

34

LED 1: Constantly yellow At least one call is being conducted via the interface card.


Flashing yellow The interface card is ready, but the slot has not been activated or the interface card has not yet been con-figured.

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

LED 3: – Not used.

LED 4: Constantly green An ethernet connection is available.

Media Gateway (MGW) Voice over IP (VoIP)

The configuration page displays the MG+ETH1-1 interface card’s MAC ad-dress. You will need this for the static

assignment of an IP address via a DHCP server.

VoIP System Telephones

For VoIP system telephony the fol-lowing telephones and software packages are available:

■ OpenPhone 63 IP: This is a VoIP capable edition of the OpenPhone 63 system tele-phone.

■ OpenPhone 65 IP: This is a VoIP capable edition of the OpenPhone 65 system tele-phone. This system telephone can be extended with up to three keypad modules.

■ OpenPhone IPC: This VoIP soft-ware offers the functionality of a system telephone using Windows 2000/XP executable software (see OpenPhone IPC starting on page 113). Further-more, this software offers local answering-machine functional-ity and integrability with CTI ap-plications.

Device Properties

The VoIP capable editions of the sys-tem telephones OpenPhone 63 IP and OpenPhone 65 IP offer the same features as the corresponding sys-tem telephones. Usage of the VoIP system telephones, therefore, does not differ from that of the standard system telephones. The following differences exist:

■ Two RJ45-connector ports are available for ethernet connec-tion. Both ports are connected to one another via the internal Switch of the telephone. The Switch supports 10 Mbit/s or 100 Mbit/s full-duplex with pri-ority on VoIP data transmission.

LAN Port: Allows the connection of the telephone to the LAN. Use a non cross-over RJ45 patch-ca-ble to connect to a Hub or Switch.

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

107Voice over IP (VoIP) VoIP System Telephones

108

■ The power supply of the VoIP system telephone is provided by an extra plug-in power supply. Optionally, it is also possible to provide the feed via PoE (“Power over Ethernet”). PoE requires special devices for power-infeed, as well as a completely wired RJ45 connection line.

■ Additionally VoIP system tele-phones offer the possibility of connecting a standard headset via two 3.5 mm sockets.

■ There is no slot for connecting miscellaneous adapter device-extensions or accessories.

■ VoIP system telephone’s audio signals are generated by the tel-ephone itself. DTMF dial tones and Music on Hold are realised by the Media Gateway function.

■ There is a quartz-based clock module present. Thereby the pe-riodically synchronisation of the time is dispensed with.

■ A VoIP system telephone can also be operated without a per-manent connection to the com-munication system, for example via an on-demand RAS connec-tion.

■ Signalling data for call control, call data during three-way con-ferences, connections to conven-tional terminals and external

connections are exchanged be-tween the VoIP system tele-phone and the communication system. During a call between two VoIP system telephones, call data is exchanged directly be-tween the two VoIP system tele-phones.

■ During the device’s start proce-dure, the IP address is config-ured and the device software is requested via the DHCP, BOOTP and TFTP network protocols.

VoIP System Telephone Configuration

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

The default behaviour of this proce-dure is to contact the OpenCom 510’s DHCP server so that the start procedure can be con-cluded without problems. Proceed as follows to register a new VoIP sys-tem telephone:

1. Temporarily remove the VoIP system telephone’s ethernet connection. Establish the VoIP system telephone’s power sup-

VoIP System Telephones Voice over IP (VoIP)

ply. Note the MAC address shown in the display, for in-stance “Ethernet: 00:30:42:00:00:00”. Remove the power supply.

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

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

4. Connect the ethernet connec-tion with the RJ45 connector of the VoIP system telephone. Es-tablish the power supply. Verify the correct start procedure by means of the display.

LAN DHCP Server

If the LAN already has a DHCP server deployed for the configuration of workplace computers, then there are various possibilities to correctly an-swer the DHCP, BOOTP and TFTP re-quests of the VoIP system tele-phones. A comparatively simple approach is described here.

1. Configure the LAN’s DHCP server so that DHCP requests from the VoIP system telephones are ig-nored. With a Linux DHCP server programme, you must, for ex-

ample, include the following lines in the system file “/etc/dh-cpd.conf”:

group {deny booting;host 192.168.11.12 {hardware ethernet

00:30:42:00:11:22;}

}

Every DHCP service-programme has similar options. You will pos-sibly need to reserve a free IP address for each VoIP system tel-ephone. You will find details in the online help or handbook of the deployed DHCP service-pro-gramme. The MAC address of all VoIP system telephones always begins with 00:30:42.

2. Configure a fixed IP address for the OpenCom 510. For this, in the Configurator, open the NET Configuration: Easy Ac-cess page. Click on the Change button.

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

4. Configure the OpenCom 510’s DHCP server to assign static IP addresses. For this, in the Con-figurator, open the


110

NET Configuration: DHCP Server page. Click on the Change button.

5. From Status, select the Static address assignment option. Confirm with Apply. The DHCP Server page is re-displayed.

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

7. Enter the VoIP system tele-phone’s IP address and MAC ad-dress. Enter the IP address re-served by the DHCP service-programme. Confirm with Apply.

Subsequently restart the OpenCom 510 and all connected VoIP system telephones.

Start Procedure

In specific cases in can be useful to be able to understand the start pro-cedure of a VoIP system telephone. Examples:

■ A complex DHCP address assign-ment prevents the operation of the OpenCom 510’s DHCP server within the LAN.

■ A VoIP system should be oper-ated with a non-broadcast-ca-pable IP connection. This can be

a RAS connection, a VPN connec-tion or another type of routed connection.

Generally it is possible that an exter-nal DHCP server controls the start procedure of a VoIP system tele-phone. For this, the system software matching the VoIP system tele-phone’s type must be transferred via TFTP.

Tip: You can obtain the system software file upon request from the Hotline. Optionally you can read-off the loading location from the display of a starting VoIP system telephone and via TFTP load the file from the OpenCom 510. For example, using Windows XP the command line is: “tftp -i 192.168.99.254 get /direc-tory/software.cnt”.

After the VoIP system telephone’s power supply has been established, the start procedure steps are as fol-lows:

1. The boot loader starts and shows the VoIP system tele-phone’s MAC address in the dis-play. Simultaneously a BOOTP request is sent via broadcast on the 255.255.255.255 broadcast address.

2. From the BOOTP server an IP ad-dress, network mask and the de-fault gateway for the start pro-cedure are communicated. Additionally via the “Next


server”-option, the BOOTP server provides the TFTP server’s IP address and the operations software’s file name. By means of the MAC address, the BOOTP server selects the operations-software file name correspond-ing to the device’s type. In many cases the DHCP service pro-gramme also answers BOOTP re-quests.

3. The boot loader loads the ap-proximately 700 KB operations-software file from the specified TFTP server. The TFTP server’s IP address and the file’s name are shown in the display. The loaded operations software is started.

4. The operations software sends a DHCP request on the broadcast address 255.255.255.255. From the DHCP server the VoIP system telephone now receives IP ad-dress, network mask and default gateway for operation. Addi-tionally, with the for this pur-pose reserved “Option 43”, the DHCP server provides the IP ad-dress of the communication sys-tem and port number 8100 for registration.

5. The VoIP system telephone cre-ates a TCP connection to the supplied IP-address/port-number combination and sends a registration query. The OpenCom 510 checks the MAC address sent with the registra-

tion and confirms the registra-tion request if the VoIP system telephone is contained in the PBX Configuration: Ports: VoIP Phones list. Additionally, the keep-alive time, the port number (8101) for telephony signalling and the value to use for the TOS byte are communi-cated in the registration answer.

6. The VoIP system telephone cre-ates a second TCP connection using the signalling port number 8101 and sends a regis-tration analogue to the Upn sys-tem telephones.

7. Extra connections are created using the IP protocol RTP (“Real-time 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) then it might be necessary to correspond-ingly configure an external DHCP server. Pay attention in the selection of the codec and the keep-alive time for RAS connections. This can be done via the selection of the default profile RAS in the PBX Configuration: Ports: VoIP Phones for the VoIP system tele-


112

phone. The via TFTP offered opera-tions software must match the de-vice’s type and communication system’s type. Potentially you will need to configure BOOTP, DHCP and TFTP servers for the VoIP system tel-ephone.

The following screenshot displays a functioning configuration for “dns-masq” Linux software (often used with wireless routers).

Configuration of an external DHCP server for VoIP system telephones

In particular the correct composition of the “Option 43” is for the func-tioning important. For this option, exactly 12 bytes must be transmit-ted.

Depending on the DHCP server-soft-ware, the option-value byte and length byte may also need to be pro-vided:

Composition of “Option 43”

Byte Value Purpose

00 43, 0x2b Options number

01 10, 0x0a Option length

02 4, 0x04 Identifier: Port no.

03 2, 0x02 Length: Port no.

03 31, 0x1f Upper and lower part of the port no. (8100)

05 164, 0xa4

06 3, 0x03 Identifier: IP ad-dress

07 4, 0x04 Length: IP address

08 192, 0xc0 4 bytes with the IP address of the com-munication sys-tem, e.g. 192.168.99.254

09 168, 0xa8

10 99, 0x63

11 254, 0xfe

Composition of “Option 43”

Byte Value Purpose


Tip: Load and install the network monitoring software “Ethereal” from the “http://www.ethereal.com/”

website. With this software you can exactly observe the start procedure.

OpenPhone IPC

Besides the hardware VoIP system telephones, PC software for VoIP te-lephony can also be deployed. This

software can be used with the oper-ating systems Windows 98 SE/ME and Windows 2000/XP.

Software VoIP system telephone OpenPhone 65 IPC with one keypad module

Besides VoIP system telephony via the workplace computer, the follow-ing features are offered by the OpenPhone IPC:

■ Usage via Mouse/PC-keyboard

■ “Drag & Drop”-selection of call numbers

■ Integrated answering machine / recording functionality

■ Terminal control for the sight-impaired

■ Selectable user interface (“Skins”)

■ Modification of display language

113Voice over IP (VoIP) OpenPhone IPC

114

For audio recording and playback, the workplace computer requires a full-duplex-capable sound card as well as a suitable headset.

The installation of OpenPhone IPC is not bound to a license. However you will require a license for the opera-tion with the OpenCom 510. There are several licenses available which make the operation of a specific number of OpenPhone IPC possible.

LicensesOpenSoftphone 102: 2 OpenPhone IPC

OpenSoftphone 104:4 OpenPhone IPC



The licenses are activated in the OpenCom 510 Configurator, in the SYS Configuration: Licenses menu. The system software contains one li-cense for a time-limited (60 days) demo-version. Please contact your dealer or your DeTeWe representa-tive if you wish to purchase a perma-nent license. The licenses can be combined; each license can only be activated once.

Installation

The installation takes place via a setup programme. The OpenPhone IPC can also be installed without an user interface. The pro-gramme can then be used via a CTI application (Net-TAPI or OpenCTI).

Start the installation programme from the OpenPhone IPC product CD and follow the installation assist-ant’s instructions.

Configuration

Analogue to the VoIP system tele-phones, the OpenPhone IPC creates multiple IP connections to the OpenCom 510. When you start the programme for the first time the Op-tions dialogue is automatically opened. Here you must configure the following values:

1. Enter in the VoIP IP Address field the OpenCom 510’s IP ad-dress.

2. Enter the selected MAC address’ six hexadecimal-digits into the Device ID field. This is config-ured in the Configurator, on the PBX Configuration: Ports: VoIP Phones page.

3. Confirm with OK.

OpenPhone IPC Voice over IP (VoIP)

NotesThe VoIP system telephony requires the active creation of an IP connec-tion to the workplace computer. If there is an firewall programme in-stalled on the workplace computer, you might need to explicitly grant this connection creation.

If you login on the workplace com-puter using a different user name, then you must reconfigure these val-ues.

For the device ID you can use any, not already in the LAN used, MAC ad-dress. Select a random device-ID/MAC-address to secure telephone usage. The device ID can only be read-off via the Web console.

The displayed menu texts and parts of the operations software are ele-ments of the OpenPhone IPC instal-lation, however, if required, are loaded from the OpenCom 510 via TFTP.

115Voice over IP (VoIP) OpenPhone IPC

116

PBX NetworkingOpenCom 510 provides all the fea-tures necessary for PBX networking. You need PBX networking in the fol-lowing 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 sys-tem.

■ To use flexible configuration possibilities of trunk lines for a OpenCom 510.

All settings that affect the configura-tion 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 corre-sponding help topics in the OpenCom 510 online help.

Note: If you do not need the fea-tures of PBX networking, the simpli-fied 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 preconfig-ured 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 precon-figured route if required, but you can-not delete them.

Connections

Networking two or more PBXs means interconnecting them. The OpenCom 510 allows you to use both trunk lines and point-to-point connections on external S0 ports or on the S2M port. Example of a PBX network

Point-to-pointconnection

Trunk line

PBX PBX PBXPBX

PBX

Connections PBX Networking

Various line types and transmission protocols can be used for point-to-point connections. The required net-work topology (distance, connec-tion capacity) determines which type of point-to-point connection is most suitable.

Protocol: Q.SIG or DSS1

The Q.SIG protocol, designed for ISDN point-to-point connections, is the preferable choice as the trans-mission protocol; alternatively, the DSS1 protocol, designed for ISDN dial-up connections in the Euro-ISDN, can be used. Certain PBX net-working features can only be used with the Q.SIG protocol, however. In particular, the identifier indicating whether a call is internal or external cannot be transmitted using DSS1.

Both protocols implement commu-nication on several protocol layers:

■ L1: Layer 1 defines the physical line properties and the electri-cal coding of signals.

■ L2: Layer 2 enables communica-tion via individual error-pro-tected channels that are inde-pendent of each other.

■ L3: Layer 3 defines the adminis-tration of the individual chan-nels and implements the fea-tures designed for ISDN.

Master/Slave

For an ISDN connection, it is possible to determine which PBX is the proto-col master and which the protocol slave. This relationship can be deter-mined for all three protocol layers in-dependently of one another.

For each protocol layer, the PBX at the other end always has to be suita-bly configured. If one PBX is the pro-tocol master for a layer, the other PBX must be the protocol slave for this same layer. Normally all three protocol layers are configured iden-tically. In the case of a trunk line, the network operator is the protocol master for all three layers.

Note: In the case of an S2M line, it is also possible to determine for each useful channel which end can admin-ister a channel (master = internally seized or slave = externally seized). On S0 lines this setting is determined by “L3 master” for both B-channels.

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

117PBX Networking Connections

118

the L1 clock propagates from a mas-ter via a number of PBXs.

Example: propagation of the L1 clock

If more than one port with the set-ting L1 Type = “Slave” is configured on an OpenCom 510 and the setting L1 sync possible has been activated, then one of the ports is automati-cally 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).

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 S2M interface of the type MT+S2M1-1 is installed, it will be selected as the preferred clock source.

Please note: Reciprocal or circu-lar 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 tempo-rarily.

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 ad-ditional trunk lines to one of the PBXs.

Types of Point-to-Point Connection

There are different types of connec-tion available for an ISDN point-to-point connection between two PBXs, depending on the distance between them.

Direct Connection

This type of point-to-point connec-tion joins the two systems directly to each other using a crossover twisted-pair cable. An S0 connection can be used for distances up to 1,000 metres, while an S2M connec-tion can span up to 250 meters. Nor-mally one PBX is the protocol master

PBX 3

PBX 2 Point-to-pointconnection

Trunk line

Networkoperator

PBX1M S

M

S

M

M

S

S

Types of Point-to-Point Connection PBX Networking

for all three layers, and the other PBX is the protocol slave for all three lay-ers.

Direct connection

■ Use the RJ45 jacks on one of the external S0 ports for an S0 con-nection between two OpenCom 510s.

Wiring of a direct connection

Connection via an Active Transmission System

For distances exceeding the range of a direct connection, an active trans-mission 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.

Connection by an active transmission system

Note: The active transmission sys-tem itself gets its L1 clock either from the network operator or from a clock generator connected by wire.

Connection via the Public Network

Point-to-point connections via the public network of a network opera-tor can be used for bridging dis-tances beyond 50 km. Due to the long distance involved, for technical reasons it is not possible to synchro-nise 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.

Point-to-point connection via a pub-lic network

PBX 1L1 masterL2 masterL3 master

PBX 2L1 slaveL2 slaveL3 slave

1 2 3 4 5 6 7 8

8 7 6 5 4 3 2 1

PBX 1, S0 ext

PBX 2, S0 ext(RJ-45 socket)

PBX 1L1 slave

L2 masterL3 master


TransmissionSystem

L1 master

PBX 1L1 slaveL2 slave

L3 master


Publicnetwork

L1 masterL2 master

119PBX Networking Types of Point-to-Point Connection

120

ConfigurationThe possible configurations de-scribed below can be set up in the Web console using the PBX Configu-ration: Trunks menu.

Trunk groups

This is a group of lines of the same type and direction. A line can only be assigned to one trunk group (bun-dle).

Example of a PBX network with trunk groups

In the above example, the following trunk groups are configured for PBX 1:

■ Two S0 lines in a multi-terminal configuration to the network operator which are assigned to the “A” trunk group.

■ Two S0 point-to-point connec-tions to PBX 2 which are as-signed to the “C” trunk group.

■ One S0 point-to-point connec-tion to PBX 3 which is assigned to the “E” trunk group.

Note: A line or a trunk group can-not be seized directly. It is always per-formed indirectly via a route.

Routes

A route is a group of trunk groups enabling a connection in one direc-tion. If the first trunk group of a route is fully utilized, the next trunk group is seized (“trunk group over-flow”). One trunk group can also be used for different routes.

In the above example, a route set up for PBX 1 allows a connection to PBX 2. Trunk groups “C,” “E” and “A” are assigned to this route. If a user connected to PBX 1 wants to reach a party in PBX 2, lines will be seized in the following order:

■ PBX 1 first searches for a free channel in the “C” trunk group.

■ If all the lines in trunk group “C” are busy, the system tries to set up a connection via trunk group “E”. PBX 3 switches the connec-tion through, provided it is ap-propriately configured (refer to Numbering starting on page 121).

■ If it was not possible to set up an indirect connection via PBX 3, the system tries again via trunk group “A”. The “prefix” neces-

A

B C

E

DBundle

PBX 1

PBX 2

PBX 3Networkoperator

Trunk line

Point-to-pointconnection

Configuration PBX Networking

sary for this can be configured with the route.

■ The user does not get a busy sig-nal 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 ran-domly selectable code digit for seiz-ing 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 evaluat-ing call data.

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 number-ing”, 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 con-figured in a numbering table con-taining up to 100 entries. You use this table to assign telephone num-bers and/or ranges of telephone numbers to a particular route.

A default entry in the numbering ta-ble makes it possible to seize a “de-fault route” for all remaining unas-signed numbers. In particular, this simplifies configuration of the OpenCom 510 as a subsidiary sys-tem: the only entry you assign to the default entry is the route to the host system

Example of closed numbering tables

The automatic switching of call re-quests (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.

PBX200-299

PBX500-599

PBX300-399

PBX100-199

PBX400-499

D: a

4: bD: c

3: e5: hD: d

3: iD: g

5: kD: fa

b

cd

ef

g

h

i

k

D:DefaultRoute

121PBX Networking Configuration

122

Technical DetailsA different PBX number must be set for each OpenCom 510 in a PBX net-work. This setting can be found in the Web console, in the menu PBX Configuration: System under the heading System linking. You can also set the maximum value for the transit counter there. This value de-pends on the topology of the PBX network and should allow the sys-tem to have the maximum number of further connections possible.

You can display the connection sta-tus 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 catego-ries 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 ap-propriate digit prefixes in the trunk

group configuration for the routes to be reseized.

Tip: If, for example, you are config-uring a route which can be seized us-ing routing code “5” and have se-lected 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.

Technical Details PBX Networking

Team Functions

Introduction

With the team functions you can manage your telephone communi-cation tasks by assigning lines with separate call numbers to the keys of different terminals. The terminal us-ers, or team members, can thus pick up one another’s calls or telephone each other using the configured keys.

Team functions can only be config-ured on the corded system tele-phones of the OpenPhone 6x prod-uct line because only these have the required features.

Explanation of Keys

The team functions are programmed on the call keys of the OpenPhone 6x telephones. Depending on the ter-minal, different numbers of call keys are available:

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 pro-grammed 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 sub-stitute function (with another team member acting as the sub-stitute). Calls for you are then signalled to the terminal of an-other team member. A trunk key also provides functions for man-aging calls. For example, you can configure call protection if you

Number of available call-keys

Telephone Number of keys

OpenPhone 61 One key with a dis-play, five keys with-out a display

OpenPhone 63 Three keys with a display, five keys without a display

OpenPhone 65 19 keys with a dis-play: nine on the tel-ephone itself and 10 on an add-on

123Team Functions Introduction

124

do not want to be disturbed, or call diversion to another tele-phone.

■ 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 an-other 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 ad-dition, it is possible to call the re-spective 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.

■ 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 sig-nalled to the destination termi-nal even if that terminal has been programmed with a sub-stitution function or call protec-tion. If the destination terminal has been configured for call di-version, the direct call is not di-verted.

Which key is suitable for which purpose?

■ Trunk keys can be assigned call numbers for managing central communication tasks, for exam-ple, customer support. If the call numbers of the support depart-ment are assigned to trunk keys on all of its terminals, then all members of the support depart-ment 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 mem-ber who is not busy. The team members can call each other by the team keys.

■ A busy key can be used to con-figure an attendant terminal

Introduction Team Functions

showing the status of the indi-vidual users. The attendant ter-minal sees the status of the us-ers 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 in order to call the secretary.

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 ad-ministrator.

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 func-tions, refer to the chapter “Manag-ing Calls in a Team” in the “Open-Phone 61, 63, 65” user guide.

Executive/Secretary Team

In this example, the executive/secre-tary team comprises two members: the executive and the secretary. The secretary has one OpenPhone 63 system telephone, and the executive has two, one of which is used as a parallel telephone in a sofa suite.

Example: executive/secretary team

Line SeizureThe 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: ex-ecutive’s office). He can also answer calls from his parallel telephone. In

11

10

12

Executive

Executive´s Parallel

SecretaryTrK 11: Secretary

TrK 10: Executive

DK 10: Executive

TrK 10: Executive

TrK 11: Secretary

TrK 12: Private

TrK 10: Executive

TrK 12: Private

125Team Functions Examples of Use

126

addition, a private line is configured for both of the executive’s tele-phones (trunk key TrK 12: private).

Call numbers 11 and 10 are both configured as a trunk key on the ex-ecutive’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 sub-stitute for the other.

The secretary’s terminal also has the executive’s call number configured as a direct call number (DK 10: exec-utive’s office). The secretary can therefore reach the executive and put through calls even if the execu-tive has programmed a substitute.

Line Busy IndicationIf a line is busy, e.g. TrK 11 secretary’s office, the other terminal will indi-cate this. The executive’s private calls via TrK 12 are not indicated on the secretary’s terminal since no appro-priate trunk key is configured on the latter’s telephone.

Call SignallingIn this configuration example, calls to one’s own call number are sig-nalled acoustically on the following telephones:

■ Call number 11 on the secre-tary’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 opti-cal 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 sec-retary’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 substi-tute function with the secretary as the substitute, calls for call number 10 will be indicated on the execu-tive’s telephone by an optical signal only, but signalled acoustically on the secretary’s telephone. The secre-tary 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 tele-phone.

Three-member Team

The three-member team described here is an example of a team config-uration within a project group, e.g. export sales.

Each team member has one Open-Phone 63 system telephone with all

Examples of Use Team Functions

call keys programmed as trunk and team keys.

Example: three-member team

Line SeizureEach team member’s call number, e.g. call number 10 for Miller, is pro-grammed as a trunk key on his tele-phone.

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 exam-ple, Miller can call number 12 by pressing TK 12; the call is then sig-nalled to Smith’s telephone on TrK 12.

Line Busy IndicationIf a line is busy, e.g. TrK 11 Johnson, the team keys 11 on Miller’s and Smith’s telephones will indicate this.

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

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. sup-port department).

Each team member has one Open-Phone 63 system telephone with all call keys programmed as trunk keys.

Example: unified team

10

11

12

JohnsonTrk 11: Johnson

TK 10: Miller

TK 12: Smith

SmithTrK 12: Smith

TK 10: Miller

TK 11: Johnson

MillerTrK 10: Miller

TK 11: Johnson

TK 12: Smith

10

11

12

MillerTrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

JohnsonTrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

SmithTrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3


128

Line SeizureCall numbers 10, 11 and 12 are pro-grammed 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.

Tip: In this team configuration it is useful to program one of the func-tion 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 informa-tion on function keys, refer to the “OpenPhone 61, 63, 65” user guide.

Line Busy IndicationIf a line is busy, e.g. TrK 11 Johnson, the trunk keys on the other team tel-ephones will indicate this.

Call SignallingIn this example, calls via all trunk keys are signalled acoustically.

Toggle Team

The toggle team described here il-lustrates how a large number of call numbers can be managed efficiently with the help of team functions.

Each team member has one OpenPhone 65 with all call keys pro-grammed as trunk and team keys.

Example: toggle team

Line SeizureEach team member is assigned seven call numbers, each pro-grammed as a trunk key (TrK 10 to TrK 16 and TrK 20 to TrK 26). For each member, these trunk keys are pro-grammed 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 tele-

10

Miller 14:22Mi.14.Feb.01

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

TrK 13: Support 4

TrK 14: Support 5

TrK 15: Hotline 1

TrK 16: Hotline 2

TK 20: Support 6

TK 25: Hotline 3

12

Johnson 14:22Mi.14.Feb.01

TrK 20: Support 6

TrK 21: Support 7

TrK 22: Support 8

TrK 23: Support 9

TrK 24: Support 10

TrK 25: Hotline 3

TrK 26: Hotline 4

TK 10: Support 1

TK 15: Hotline 1

11

131415

16

20

2221

23242526

Examples of Use Team Functions

phone, e.g. TrK 10 and TrK 15 on Miller’s telephone as TK 10 and TK 15 on Johnson’s telephone. The as-sumption here is that most calls will go to the respective first call num-bers, 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 individ-ual lines, e.g. TrK 10 and TrK 11, by pressing the appropriate key (tog-gling).

Every call on a trunk key can be transferred to any other party by means of the R key. For more infor-mation, refer to the chapter entitled “Consultation, Toggling, Transfer and Conference” in the “OpenPhone 61, 63, 65” user guide.

Line Busy IndicationIf a line is busy, e.g. TrK 10 on Miller’s telephone, the appropriate team key will indicate this, e.g. TK 10 on John-son’s telephone.

Call SignallingIn this example, calls via trunk keys are signalled acoustically. Calls via team keys are indicated by a visual signal (the team key LED flashes).


130

Call Queue

Introduction

A queue can be activated for the tel-ephone numbers of any type of tele-phone, 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 announce-ment (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 system tele-phone, 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 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, sen-sor 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, fur-ther callers hear a busy tone.

Only calls which have a “voice” serv-ice indicator are administered in a queue.

Introduction Call Queue

Note: As calling fax machines of-ten operate with the “voice” service indicator (e.g. on analogue ports), you should assign ports for fax ma-chines 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 or-der to configure an attendant termi-nal for an operator.

Activation of Queues

Queues can be activated on a per user group basis. On delivery the de-fault set, for all preset groups, is off.

When using queues, it often makes sense to activate call waiting protec-tion. For this purpose, “Call waiting protection” authorisation must be allocated to the user group, and call waiting protection must be acti-vated on the terminal.

Furthermore it is sensible to com-bine 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. Cen-tral welcoming texts can be recorded using the separately obtainable pro-gram package OpenVoice.

You should configure a new user group (e.g. “Operators”) and activate the authorisations “Call queue”, “Call waiting protection” and, if neces-sary, “Call forwarding”. If users be-long to this group, a queue will be activated automatically for all tele-phone numbers assigned to them.

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 forward-ing function is activated, these calls can only be accepted on the source terminal.

If a call is to be forwarded “After de-lay”, it enters the queue. If the call has not been answered before the delay period expires, it will be for-warded to the target terminal and can then be answered there.

Pickup

The functions “Pickup” (from a pickup group) and “Pickup selective” can be used together with queues.

131Call Queue Introduction

132

A user who accepts a call using “Pickup” or “Pickup selective” picks up the next call from the queue.

Hunt Groups

Hunt groups of the “parallel” type are usually used together with

queues, with the queues of each tel-ephone in the group being synchro-nised to each other. When a call to the number of the hunt group ar-rives, the call enters all parallel queues. If a call from one of the queues is answered, it is removed from all other parallel queues.

Examples of Use

Attendant Terminal for an Operator with Two System Telephones

The operator switches all incoming calls and can either work on the OpenPhone 65 or the mobile termi-nal, the OpenPhone 27.

Configuration

■ Configure the system access or access for multiple terminals un-der PBX Configuration: Ports: S0.

■ Configure the OpenPhone 65 and the RFP 21/23 under PBX Configuration: Ports: Upn.

■ Configure a trunk key for the OpenPhone 65 under PBX Con-figuration: System telephones.

■ Configure the OpenPhone 27 under PBX Configuration: Ports: DECT-PP and assign the OpenPhone 27 its own tele-phone number. Check in the OpenPhone 27.

■ Under PBX Configuration: Call Distribution: Incoming route all incoming calls to the number of the OpenPhone 65 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. As-sign this user to the “Operators” user group. Assign the tele-

Examples of Use Call Queue

phone numbers of the OpenPhone 65 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 which activates/deactivates a “call forwarding immediately” to the telephone number of the mobile OpenPhone 27 (in the menu Call forwarding: Di-vert phone: Immedi-ately).

UseIncoming calls are routed to the OpenPhone 65 manned by the oper-ator, who then puts the calls through. A queue is used so that call-ers do not get a busy signal. The dis-play on the OpenPhone 65 indicates how many calls there are in the queue.

If the operator wants to leave the workstation and take along the at-tendant terminal, call forwarding to the OpenPhone 27 is activated by pressing a function key. Calls which are in the OpenPhone 65 queue must still be answered on this tele-phone. New calls are signalled on the mobile OpenPhone 27 or enter its queue, allowing the

OpenPhone 27 to be used as a mo-bile attendant terminal.

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 sig-nalled on the OpenPhone 65 or en-ter its queue.

Group of Three Attendant Terminals

The attendant terminals switch all incoming calls. Incoming calls are administered in queues. Depending on the number of arriving calls, one to three attendant terminals in this group are manned. The attendant terminals are each equipped with an OpenPhone 65.

Configuration

■ Configure the system access or access for multiple terminals un-der PBX Configuration: Ports: S0.

■ Configure the three OpenPhone 65 telephones un-der PBX Configuration: Ports: Upn.

■ Configure a trunk key with its own telephone number for each of the OpenPhone 65 tele-

133Call Queue Examples of Use

134

phones under PBX Configura-tion: System telephones.

■ Configure a hunt group of the “parallel” type under PBX Con-figuration: Groups: Hunt Group, and include the three tel-ephone numbers of the trunk keys in this hunt group.

■ Under PBX Configuration: Call Distribution: Incoming route all incoming calls to the number of the hunt group.

■ In the Configurator, create a new group called “Operators” under User Manager: User groups. Activate “Call queue” and “Call waiting protection” for this group.

■ In the User Manager, configure a user for each of the three oper-ators and assign these settings to the user group called “Opera-tors”. 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 Protec-tion 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).

UseIncoming calls are signalled in paral-lel to all signed-on attendant termi-nals. If the attendant terminals are busy, the incoming call joins the queue on each of the terminals in the hunt group. If one of the attend-ant terminals accepts a call from the queue, the call is removed from the queues of all the other attendant terminals. The display on each at-tendant terminal (OpenPhone 65) indicates how full the queue is.

If attendants leave the terminal, 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 signed-on attendant terminals.

Note: The last attendant terminal remaining in the hunt group should not sign off, so that incoming calls can always be signalled to at least one terminal.

Examples of Use Call Queue

Multi-Company VariantCommunications systems are fre-quently shared by several compa-nies. 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 com-pletely independent of one another. This allows them to have their own trunk lines, which is useful for billing purposes. The OpenCom 510 hard-ware 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 fea-tures 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 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 ex-ample, it is possible to activate different routes with the code “0” for different companies. This enables separate charging for outgoing external calls, for ex-ample.

■ An individual exchange (“opera-tor”) can be set up for each com-pany.

■ Each company can maintain the communication data of its busi-ness partners in its own com-pany telephone book.

■ The charges can be billed indi-vidually for each company.

135Multi-Company Variant

136

Configuring the Multi-Company VariantThe multi-company variant can be commissioned and configured by the system administrator of the OpenCom 510 without any major ef-fort. In the multi-company variant, the communications system be-haves in exactly the same way as the single-company variant. This is par-ticularly of interest to users who want to expand their own system and at the same time operate it in a group.

The process in brief:

1. The feature must be activated (see Activating the Multi-Com-pany Variant starting on page 136).

2. The required companies must be set up (see Configuring and Man-aging Companies starting on page 137).

3. The users of the OpenCom 510 are assigned to the individual companies (see Assigning Users starting on page 137).

4. 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 starting on page 138).

5. In the case of outgoing external calls, the lines via which the members of a company can make a call must be defined (see Allocating Routing Codes starting on page 138).

6. 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 ex-change (see Configuring the Company Exchange starting on page 138).

Activating the Multi-Company Variant

To be able to configure several com-panies in the OpenCom 510, the “Multi-company variant” (OpenCompany 45) program pack-age must first be activated. This is done in the Configurator on the Web console in the SYS Configuration: Licences menu. The licence confirmation you re-ceived with the program package contains all the information you re-quire about how to proceed.

Only when this package has been ac-tivated are the fields required to configure the multi-company vari-ant available in the other menus of the Web console, for example in the User Manager: User groups menu

Configuring the Multi-Company Variant Multi-Company Variant

or in the PBX Configuration: Trunks menu.

Configuring and Managing Companies

Up to five companies can be config-ured in the OpenCom 510. By de-fault, one company with the name “Company 1” is predefined. All con-figuration settings, e.g. in the user groups or in the trunk group config-uration, apply to this predefined de-fault company if not other company has been selected.

Companies are set up and managed in the PBX Configuration: Compa-nies 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 com-mand 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 com-pany can be changed, but the default company itself cannot be deleted.

Assigning Users

For each user you must define the company to which they belong. This assignment determines, for exam-ple, 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 there-fore 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.

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 com-panies have been set up.

137Multi-Company Variant Configuring the Multi-Company Variant

138

Assigning Trunk Groups

Connections of the same type and in the same direction are arranged in a trunk group (e.g. S0 multi-terminal connections). To be able to correctly transfer incoming calls to the mem-bers 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 com-panies. This is necessary to be able to transfer incoming external calls to the correct company exchange in cases where the called internal sub-scriber cannot be reached (“Connec-tion to Operator”), for example.

The assignment of trunk groups to companies is done in the PBX Configuration: Trunks: Bundle menu.

For outgoing external calls which us-ers set up via the lines of their com-pany’s trunk group, the assignment of the trunk group to the company is irrelevant: the charges are assigned according to the “source” principle.

Charges are billed to the company to which the user belongs who set up the connection. The OpenCom 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 was seized. For more information, please see the following section.

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 predial-ling a code.

In the PBX Configuration: Trunks: Route menu, you can define which company can seize each route. An in-dividual code for the seizure is allo-cated per route for each company. The OpenCom 510 ensures that dur-ing 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.

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 exten-sions arriving at the exchange are routed to this number, for example, as are all external calls where the called subscriber (a user who be-longs to this company) cannot be reached, as in the case of a timeout.

Configuring the Multi-Company Variant Multi-Company Variant

A company exchange is set up in the PBX Configuration: System: Opera-tor menu. In this menu, you can specify an internal telephone number for each company and time group which then represents the ex-change for this company.

Working with the Multi-Company Variant

All the features of the OpenCom 510 which the users may already be fa-miliar 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.

Company Telephone Book

An individual company telephone book can be created for each com-pany. 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 as-signed to this company. You can also define whether the members of each user group may edit the com-pany 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.

Users can also use the telephone book of their company with the OpenCTI 50 Web applications and phone book, assuming they are au-thorised to use these applications.

In addition, it is also possible to as-sign a user group with the authorisa-tion to edit foreign company tele-

139Multi-Company Variant Working with the Multi-Company Variant

140

phone 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 Con-figurator 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 com-pany telephone books).

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 there-fore not subject to any restrictions.

Billing Charges per Company

In the Costs Web application you can output the charges for each com-pany.

Users who are authorised to use this application can view the charges for each company.

Working with the Multi-Company Variant Multi-Company Variant

Configuring the PC SoftwareFurther possibilities of use can be implemented on a workstation PC with the Windows operating system by installing drivers and pro-grammes. You can find the installa-tion programmes required for this on the product CD that comes with the OpenCom 510.

Proceed as follows to install extra software:

1. Log on under Windows NT or Windows 2000/XP as the admin-istrator.

2. Insert the product CD.

If your PC is suitably configured, the CD will start automatically. Otherwise select Run from the Start menu. Click on the Browse button to look for the pro-gramme “cd_start.exe” on the CD. Confirm this with Open and OK.

3. Select the required option from the start interface. Follow the programme instructions.

Further instructions for various op-tions that are available are given be-low.

PC Offline Configuration

The offline configurator is a reduced system software that is executable under the operating systems Micro-soft Windows 2000 or Microsoft Windows XP. With the offline config-urator it is possible to create system configurations for various TC-system types – without a connection to the live system. You configure a virtual system and later, aided by the data backup, transfer the configuration to the running system.

Installing the offline configurator

1. Display the product CD contents in Windows Explorer. Search the installation directory for the of-fline configurator.

2. Start the StartCenter installa-tion programme by double-clicking on “Setup.exe”. Follow-ing the installation assistant’s in-structions. Select the appropri-ate installation directory or apply the default.

141Configuring the PC Software PC Offline Configuration

142

3. On the product CD, in the offline configurator installation direc-tory, you will find ZIP archives for various TC-system types. Open the desired ZIP archive with a double-click and extract its contents to an appropriate sub-directory of the installation directory.

4. End the installation with a func-tion test. With a double-click on the newly created desktop icon, start the StartCenter pro-gramme. Select from the fold-down 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 com-mand window. Open a Web browser and in the address line enter: “http://localhost/”. Con-firm with enter.

5. Configure the virtual system as usual. Using the data backup, you can save the configuration.

6. Activate the command window. End the offline configurator with the key-combination [Ctrl] + [C].

To maintain multiple different installations, you can extract further offline configurators to new directories of your hard-drive. Change between the directories by

selecting the command Extras: Setup in the StartCenter programme. 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 config-urator. 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 programme packages requiring licenses in the offline configurator (in menu SYS Configuration: Licenses). The serial number can be ob-tained for the ITC-system’s Con-figurator 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 compu-ter is now ready-to-receiver re-quests for the offline configura-tor’s web-server service. You must permit the web-server service, for example by activat-ing the option For this program do not display this notification again.

PC Offline Configuration Configuring the PC Software

■ If there is an existing web-server service installed on the worksta-tion computer, then you must enter a new port number in the Setup dialogue of the pro-gramme StartCenter, for exam-ple 8080. In the Web browser, the address line input is then: “http://localhost:8080/”. When using different port numbers you can also start multiple of-fline configurators simultane-ously on one workstation com-puter.

■ If for the Web browser there is a proxy activated, then you might have to enter the computer name “localhost” into the excep-tions list (No proxy for …).

■ During deinstallation of the pro-gramme StartCenter, the entire installation directory with all its sub-directories is deleted. Backup the necessary offline configurators before uninstall-ing.

Setting up TAPI

With a TAPI (Telephony Application Programming Interface) you can op-erate a CTI application (computer te-lephony integration). Here, the CTI application uses the services of the OpenCom 510 with the help of the TAPI driver installed on a Windows PC.

RequirementsYou require an active IP network connection between the PC and the telephone system. Refer to the chap-ter entitled Configuration under Win-dows starting on page 74 if you have not yet established an IP network connection. CTI functions can be used only in conjunction with sys-tem telephones.

You must therefore have configured at least one user for a system tele-phone. In addition, you require a TAPI 2.1-compatible CTI application, for example the Phone Dialer in-cluded in the Windows operating system.

Installing the TAPI Driver

1. Call up the start mask from the product CD (see Configuring the PC Software on page 141).

2. Select Software: TAPI Service Provider from the start mask and follow the programme in-structions.

143Configuring the PC Software Setting up TAPI

144

Configuring the TAPI Connection

Note: Under Windows NT or Win-dows 2000/XP you should log on as the user for whom you want to con-figure the TAPI connection.

1. In the Start menu, select Set-tings: Control Panel. Double-click on the Telephony icon (Phone and Modem Options icon under Windows 2000/XP).

2. Change to the Telephony Driv-ers tab (Advanced Options tab under Windows 2000/XP).

3. From the list of installed driver software, select OpenCom 100 Service Provider and click on Configure.

4. In the following dialogue you will find a list with the config-ured connections for the user who is currently logged on. Click on New.

5. In the following dialogue you provide information for the new connection. In the Connection name box you can enter a de-scriptive name for the connec-tion. 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.

6. The new connection is now con-figured. Close the opened dia-logues with OK and Close.

Testing the TAPI Function

1. In the Start menu, select Pro-grams: Accessories: Communi-cation and then start the pro-gramme called Phone Dialer.

Under Windows XP the Phone Dialer is started indirect by us-ing the dialling function of the Address book (can be found in the start menu under Programs: Accessories). A manual start of the programme file “Dialer.exe” in the “C:\Program files\Win-dows NT” folder is possible also.

2. In the Tools menu, select the item Connect using... to select the system telephone that is to use the CTI application. Under Windows 2000/XP you select the item Options from the Edit menu. In the Lines tab you then select the system telephone from the Phone calls list.

3. Enter a telephone number in the Number box and confirm with Dial. Under Windows 2000/XP you first click on the Dial icon and in the subsequent dialogue activate Phone call.

Setting up TAPI Configuring the PC Software

4. The number you entered is dis-played on the selected system telephone. Lift the receiver to start dialling.

Note: This note is not relevant to Windows 2000/XP. If the “Phone Di-

aler” programme 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.

Setting up NET CAPI

With a CAPI driver (common applica-tion programming interface) Win-dows 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.

RequirementsYou require an active IP network connection between the PC and the telephone system. Refer to the chap-ter Configuration under Windows starting on page 74 if you have not yet established an IP network con-nection.

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


2. Select Software: NET CAPI Driver from the start mask and follow the programme instruc-tions.

Configuring the NET CAPI DriverThe NET CAPI driver requires an extra internal number so that the “virtual ISDN card” on the OpenCom 510 can be addressed:

1. Go to the Configurator, NET Configuration: Connections: CAPI menu. Click on Change.

2. Activate the Status check box. Enter at least one unassigned, internal number in the boxes under Parameters. Confirm your entry with Assign.

145Configuring the PC Software Setting up NET CAPI

146

3. Go to the Configurator, User Manager: User menu. Select one of the users shown. Enter the number just assigned in one of the boxes No. 1 to No. 10. Confirm your entry with Apply.

4. If it is to be possible to call the “virtual ISDN card” externally, or if external calls are to be possi-ble, the number must be in-cluded in call distribution (Con-figurator, PBX Configuration: Call Distribution menu).

5. After installing the NET CAPI driver, you will find an extra icon

on the right side of the Windows Start bar. Click on this icon with the right mouse key. Select the Log-on command from the menu.

Note: In the subsequent dialogue you must log on NET CAPI first with the user (user name and password) for which you configured the CAPI tel-ephone number in the User Man-ager (see Step 3).

You will find further information on the working of the NET CAPI driver and CAPI application programmes on the product CD.

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. This systray display constantly shows you whether an ISP, an RAS or a LAN-to-LAN connec-tion is active. It is also possible to display the current occupancy of the trunk lines.

RequirementsTo use the systray display, you must first install TAPI; see Setting up TAPI starting on page 143.

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

1. Call up the start mask of the product CD (see Configuring the PC Software on page 141).

2. From the start mask, select Soft-ware: Install Systray. Follow the programme instructions.

3. Start the programme with Start: Run and the configuration dia-logue is displayed. Select one of the entries displayed under Ex-

Using the Systray Display Configuring the PC Software

isting PBXs. Enter your user name and password in the boxes under Log-on.

4. If you activate the Autostart check box, you will see the systray display even after re-starting your PC.

5. Confirm the entries in the con-figuration dialogue with OK and

the systray display logs on for the OpenCom 510.

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

Browser for OpenCTI and OpenHotel

You can simplify the daily use of the OpenCTI and OpenHotel Web appli-cations using the Web browser espe-cially adapted for the OpenCom 510. Each time the workstation is re-started, this browser programme can automatically start and log you in. This means that the applications are always operational and can be accessed using the icon in the infor-mation area of the task bar.

Installing the browser for OpenCTI


2. From the start mask, select Soft-ware: Install browser for OpenCTI or Install browser for OpenHotel. Follow the pro-gramme instructions.

3. Follow the programme instruc-tions.

After installing the browser, there is a new menu entry in the Windows start menu under Programs: OpenCTI Browser respectively Pro-grams: Hotel Starter.

Further information can be found in the online help of the browser pro-gramme. To view this, click the top left corner in the OpenCTI-browser’s programme 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 programme.

Note: Both browser programmes can be used simultaneously.

147Configuring the PC Software Browser for OpenCTI and OpenHotel

148

Synchronising the PC ClockWith the network service SNTP (sim-ple network time protocol) it is pos-sible to synchronise the internal clock of a PC with the time of the OpenCom 510.

RequirementsYou 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) re-quired for SNTP:

1. Go to the Configurator, SYS Configuration: System menu. Click on Change.

2. Under Internet time (SNTP), en-ter the Time zone for which the time of the OpenCom 510 ap-plies and whether summer time is allowed for. Confirm this with Assign.

Configuring SNTPFor various operating systems, you can use one of the numerous SNTP programmes offered for download-ing on the Internet. Configure the OpenCom 510 as an SNTP server for such programmes.

SNTP with Windows 2000Here you configure the SNTP server as follows:

1. Log on as the administrator. Start the Command Prompt un-

der Start: Programs: Accesso-ries.

2. Enter the command line “net time /setsntp:192.168.99.254”. Confirm with the enter key. This command changes the setting for the SNTP server address in the system registry. Close the command line.

3. Open the Services dialogue un-der 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 synchro-nised with the time of the OpenCom 510.

Please note: In a Windows do-main network, the PDC server (pri-mary domain controller) should auto-matically assume the function of the timer.

SNTP with Windows XPHere 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.

Synchronising the PC Clock Configuring the PC Software

Address Queries using LDAPYou can search the data of the cen-tral telephone book of the OpenCom 510 from a workstation in the LAN using LDAP (Lightweight Di-rectory Access Protocol). When con-figuring an LDAP-enabled pro-gramme, specify the IP address of the OpenCom 510 as the address of the LDAP server.

LDAP with Outlook ExpressYou can configure and operate the LDAP directory service with Outlook ExpressTM, a MicrosoftTM e-mail pro-gramme, as follows:

1. Call up the Accounts command in the Tools menu.

The Internet Accounts dialogue box will then open.

2. Click on Add. Select the Direc-tory Service command from the pop-up menu.

The Internet Connection Wiz-ard dialogue box for Internet ac-cess will then open.

3. Under Internet directory (LDAP) server, enter the ad-dress of the OpenCom 510. It is not necessary to log in to the LDAP server. Click twice on Next. Then click on Finish.

4. Check the function. In the Edit menu, call up the Find: People command.

The Find: People dialogue box will then open.

5. In the Look in list, select the en-try with the OpenCom 510 ad-dress. Enter a user in the Name input field, Administrator for ex-ample. 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.

149Configuring the PC Software Address Queries using LDAP

150

USB DECT Box on the OpenCom 510

General Information

The USB DECT Box provides a PC with a wireless ISDN data connection (DECT). The Box is connected to the PC via the USB interface and uses the RFP 21/23 to create a connection to the OpenCom 510 and its network, to the telephone network and to the Internet.

Note: Up-to-date information on the USB DECT Box can be found at http://www.detewe.de/.

Installation and Configuration

1. Connect the RFP 21/23 to a free Upn interface on the OpenCom 510. Instructions on how to do this can be found in the section MS+UPN2-8 starting on page 65.

2. Configure the RFP 21/23 in the Configurator, using the PBX Configuration: Ports: Upn menu.

3. Install the software of the USB DECT Box and then connect the USB DECT Box to your PC. Fur-ther information on this can be found in the corresponding chapter of the “USB DECT Box”

manual (which is included with the USB DECT Box).

4. Create a new DECT device of the type USB DECT Box in the Con-figurator (menu PBX Configu-ration: Ports: DECT-PP) and as-sign a telephone number for the data port.

5. Check the USB DECT Box in. Fur-ther information on how to do this can be found in the corre-sponding chapter of the “USB DECT Box” manual and in the online help provided in the OpenCom 510.

6. Assign a user to the telephone numbers of the USB DECT Box in the Configurator (menu User Manager: User).

Tip: We recommend that you cre-ate the Internet access indirectly via the RAS access of the OpenCom 510.

If you wish to use the USB Box to dial up an Internet provider directly, fol-low the instructions in the corre-sponding chapter of the “USB DECT Box” manual. If you do this, you can omit the remaining steps.

Please note: The direct dial-up of an Internet provider offers no safety mechanisms, whereas access-ing the Internet via the OpenCom 510

USB DECT Box on the OpenCom 510 Configuring the PC Software

protects your network/PC by means of filter lists.

7. In the Configurator (menu User Manager: User), assign the user of the USB DECT Box to a user group which is allowed to use RAS access.

8. Configure the Internet access in the OpenCom 510 Configurator (menu NET Configuration: Con-nections: ISP). You can edit/cre-ate suitable filter lists for the In-ternet access in the NET Configuration: Safe Access menu.

9. Configure the RAS access in the NET Configuration: Connec-tions: RAS menu.

10. Configure the communication network. To do this, follow the instructions in the correspond-ing chapter of the “USB DECT Box” manual. Do not enter the provider data, though. Instead, use the internal number of the RAS access and the user name and password of the OpenCom 510 user.

Detailed information can be found in the Internet starting on page 166 section of the Frequently Asked Ques-tions chapter. The information con-cerning the Internet functionality of the OpenPhone 27 also applies to the USB DECT Box.

Technical Data

■ Data transmission with RAS access / Internet access via the OpenCom 510: Up to 64 kbit/s gross

■ Data transmission with direct dial-up of a provider: Up to 128 kbit/s gross

151Configuring the PC Software USB DECT Box on the OpenCom 510

152

Configuration GuideThe 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 set-tings. The individual charts are sum-marised below:

■ Overview: This chart gives you an overview of the initial config-uration of the OpenCom 510.

■ Configuring PBX Ports: This chart shows you the necessary steps for configuring ports and terminals.

■ Configuring Easy Access: This chart guides you through TCP/IP settings for the OpenCom 510.

■ Configuring ISP Settings: These instructions support you in con-figuring the Internet access.

■ Configuring RAS Settings: This chart guides you through the configuration of the RAS set-tings.

■ Configuring LAN-to-LAN Set-tings: This chart guides you through the configuration of the LAN-to-LAN settings.

■ Configuring E-Mail: This dia-gram tells you how to create the requirements needed for config-uring the OpenCom 510 e-mail access function.

■ Configuring E-Mail Access: This overview provides instructions on configuring the OpenCom 510 e-mail access server.

Configuration Guide

Overview

Flowchart: Overview

Yes

Finished

No

Ethernet network(LAN) exists?

Connect the OpenCom and theconfiguration PC to the network

Connect the configurationPC to the OpenCom COM port.

Generate the Dialup Networkingentry with “occonfig”.

Configure OpenComLeast Cost Routing function?

Configure OpenComnetwork functions?

Yes

No

Yes

Dial in (RAS)?

Connection (LAN)?

Internet?

E-mail?

Yes

Yes

Yes

Yes

No

Create the user groups and users.

Set the system data. Select the access type. Connectthe S

0, U

pn and analogue devices and configure them.

Configure the call distribution scheme.User Manager

PBX Configuration

Save data

E-Mail Configuration

ISP Configuration

LAN-LAN Configuration

RAS Configuration

Easy Access Configuration

LCR Configuration

Configure the Least Cost Routingfunction: zones, network providersand holidays.

No

No

No

No

Start the OpenCom configurationservice via your Web browser.

Enter the OpenCom address, forexample “http://192.168.99.254”.

Connect the configurationPC to the OpenCom LAN port.

Enable DHCP.

Cross-connected ethernetcable available?

No

Yes

153Configuration Guide Overview

154

PBX Ports

Flowchart: Configuring the PBX Ports

Finished

Enter the Upn interfacesand enter the internaltelephone numbers.

S0 terminals

Upn terminals

Analogue terminals

Sensor

COM

DECT terminals

Define the externalS

0 interfaces

Define the access type

Define the internal S0interfaces

Configure theUpn interfaces

Configure the DECTterminals

Configure thea/b interfaces

Configure the sensor

Configure the COMinterface

Yes

Yes

Yes

Yes

Yes

YesNo

No

No

No

No

No

Do you have ISDN terminalsthat you wish to operate onan S0 interface?

Do you want to operatesystem telephones orDECT terminals?

Do you want to operateanalogue terminals(e.g. a fax machine)?

Do you want to use asensor contact on theOpenCom (e.g. for adoor opener)?

Do you want to run theOpenCount program?

Set the external S0 interfaces and

enter the telephone numbersassigned by your network provider.

Set the access type (multiterminalaccess and/or system access).

Set the internal S0 interfacesand enter the internaltelephone numbers.

Do you want to operateDECT terminals on theOpenCom?

Check in the DECT terminalsand enter the internaltelephone numbers.

Set the analogue interfacesand enter the internaltelephone numbers.

Enter the internal telephonenumbers for the time groupsof the sensor.

Select the “connectiondata” option.

PBX Ports Configuration Guide

Easy Access

Flowchart: Configuring Easy Access

Finished

Assign a nameto the OpenCom.

Specify the IP address of the OpenComunder “Domain Name Server”. This istransferred as the DNS server to theclient computers via DHCP.

LAN

Host name

DHCP

DNS

OpenComDHCP server

IP addressNetwork mask

PPP addresses

Finished

Yes

No

Yes

OpenCom asDNS server

Register internal DNS

No

Yes

No

Do you have a DNS serverin your network?

Enter the Ethernet-IP confi-guration for the OpenCom.

Activate the OpenComDHCP server.

Do you have a DHCPserver in your network?

Do you have a computer network?

Enter the address rangefor the RAS accesses.

Gateway address

DHCP adresses

Domain name

Client computers are informed of thisgateway address via DHCP as a gateway.

Enter the address range of theclient computers in your network.

Enter the domain name. This name istransferred to the client computers asthe domain via DHCP.

Specify the IP address ofyour internal DNS serverunder “Domain NameServer”. This is transferred asthe DNS server to the clientcomputers via DHCP.

The OpenCom takesthe settings fromyour DHCP server

Ask your network administrator for theaddress range for the RAS accesses. Forthis purpose, your administrator mustreserve an IP address range for the RASaccesses.

155Configuration Guide Easy Access

156

ISP Settings

Flowchart: Configuring the ISP Settings

Select one of thedefault providers in“NET Configuration:Connections: ISP”.

“SYS Configuration: System:Country” = “German”?

Is your IP addressallocated by yourprovider?

Your own ISP

T-Online

DSL(PPPoE) LAN

ISP cannot be configured.

HDLCPPPNo No No

Provider-New: Provider,Telephone Number,

User Name and Password

Domain Name Server

Mail input server and mailoutput server

Maximum idle time

Activate the status andselect the provider

T-Online: Telephone number,Access identification, T-Online

number, Co-user numberand Password

Select a providerfrom the list

Dynamic

IP address

Network mask

Your own telephonenumber

Max. connection timeper month

Maximum idle time

Filter list IN

Filter list OUT

Finished

Gateway

Yes

No

No

Yes

No

Yes

Configure T-Online in “NET Configu-ration: Connections: ISP: Provider”.You will obtain the access data whenyou register.

Enter your provider'sdial-in data.

Do you want to configurea new Internet provider?

Specify the IP address ofthe DNS in the Internet.

Specify a standard POP serverand a standard SMTP server.

Specify the maximum time ofinactivity after which the connectionto the ISP is cleared down.

Configure the ISP in “NET Configu-ration: Connections: ISP”.

Enter the IP address and network maskyou wish to obtain from your provider.

Specify the gatewayfor the Internetconnection.

Specify the maximumconnection time for one month.

Specify the maximum time of inactivity afterwhich the connection to the ISP is cleared down.

Select the filter lists. Filter lists are createdin “NET Configuration: Safe Access”.

Yes

Yes YesYes

No

ISP Settings Configuration Guide

RAS Settings

Flowchart: Configuring the RAS Settings

LAN

Users

Status

Authorisation

Number of connections

Filter list IN

Filter list OUT

Add internal telephonenumber to the incomingcall distribution scheme.

Finished

Yes

No

No

Yes

Configure users thathave RAS access rights.

Have you created userswith RAS access rights?

Select the filter lists. Filterlists are created in “NETConfiguration: Safe Access”

Specify how many simultaneousconnections are possible via this access.

Select from PAP,CHAP and CLID.

Activate the RAS access.

Configure the network -settings for the OpenCom.

Have you made the networksettings for the OpenCom ?

Configure the RAS access of theOpenCom. “NET Configuration:Connections: RAS”

NET Configuration:Easy Access

User Manager: Usersand User Groups

Telephone numberSpecify the telephone number for whichthe RAS access should be configured.

157Configuration Guide RAS Settings

158

LAN-to-LAN Settings

Flowchart: Configuring the LAN-to-LAN Settings

Authorisation method of the localLAN: CLID, PAP or CHAP?

Authorisation method of the remoteLAN: CLID, PAP or CHAP?

LAN


Protocol

Telephone number local

IP address local

Network mask local

User name local

CLID

Password local

Telephone number remote

IP address remote

Network mask remote

CLID

User name remote

Password remote

Direction of connection

Maximum connectiontime per month

Maximum idle time

Add internal telephonenumber to the incoming call

distribution scheme.

Finished

No

Yes

No

No

Select between PPP and HDLC transparent.

Enter the internal telephone number.

Enter the local IP address.

Enter the local network mask.

Specify the user name with which theremote LAN can access a destination.

Specify the password with which theremote LAN can access a destination.

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.

Specify the user name with whichthe remote LAN can be accessed.

Specify the password with whichthe remote LAN can be accessed.

Select the direction of the connection.

Specify the maximum number of minutes per monththe connection to the remote LAN can be set up for.

Set the maximum idle time after which aconnection to the remote LAN is cleared down.

Have you made the networksettings for the OpenCom?

Configure the LAN-LANconnection. “NET Configuration:Connections: LAN-LAN”

Configure the network-settings for the OpenCom.

Yes

Yes

LAN-to-LAN Settings Configuration Guide

E-mail Function

Flowchart: Configuring the E-mail Function

LAN

Internet

LAN

Notification

Users

Finished

No e-mail use

Yes

No

No

No

Yes

Yes

Yes

No

Yes

No

Finished


NET Configuration:Connection: ISP

User Manager:Users, User Groupsand User Accounts

NET Configuration:E-Mail Access

Have you made the networksettings for the OpenCom?

Do you want to use e-mailfrom the Internet?

Has an internal e-mail serverbeen configured in your LAN?

Do you want to be notified ofe-mails on your system telephones?

Have you stored theusers to be notified?

Set the polling time periods.

Configure the network settingsfor the OpenCom.

Configure your Internet access.

Create the users and activatee-mail notification. Also enterthe users' e-mail addresses.

159Configuration Guide E-mail Function

160

E-mail Access

Flowchart: Configuring E-mail Access

Configuration of e-mailaccess settings

Mail server

User accounts

Finished

Maximum number of e-mailsper 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

NET Configuration: Easy Accessor Configure ISP

User Manager: User Accounts

No

No

Yes

Yes

Do you have access to a mail serverin your network or in the Internet?

Do you have created mail account pollsin the “User Manager: User accounts”?

Specify the time intervals in which theOpenCom is to poll all mail accountsfrom the standard POP server.

Define the time windows in which theOpenCom should check the mail accounts fornew messages in the time intervals that havebeen set. You can define two time windows foreach working day (Monday to Friday), and twoeach for Saturday and Sunday.

Configure your network/Internet access.

Set up user accounts inthe User Manager.

Specify the maximum no. of e-mails peruser account that should be temporarilystored by the OpenCom.

E-mail Access Configuration Guide

Frequently Asked QuestionsThis chapter provides tips and infor-mation on how to deal with any mal-functions or faults you may experi-ence 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:

Position of LEDs on the OpenCom 510

General/Hardware

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

Question: The mains plug is con-nected, the mains socket is supply-ing output, but the OpenCom 510 still does not function.

DANGER! This device con-tains hazardous voltages. To make the system dead, remove the power plug from the socket.

Is the +3,3V/-42V LED at the lit up? If not, contact your service centre or an authorised dealer. The AC adapter plug of the OpenCom 510 may be defective.

+3,3 VLED

-42 VLED

MPS+1-AC MC+1-3

Activity LED

LAN LED

161Frequently Asked Questions General/Hardware

162

Question: After restarting the OpenCom 510, nothing is indi-cated on the displays of any con-nected 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 52. 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 87).

Telephony

Question: 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 S0 ports are configured correctly (PBX Configuration: S0 menu).

Question: The OpenCom 510 is connected to an NTBA with a multi-terminal configuration. Why is it not possible to establish exter-nal connections?

With the original factory setting, an additional external S0 port is set for an NTBA in system configuration; this additional port will be used first to seize a trunk line.

Deactivate the corresponding S0 port in the Configurator (PBX Con-figuration: S0 menu).

Question: 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 Configura-tion: Ports menu).

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

Telephony Frequently Asked Questions

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 outgoing call distri-bution (Configurator, PBX Configu-ration: Call Distribution menu).

Question: One of the features (e.g. call diversion) on one of the telephones cannot be used even though the feature has been con-figured 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 fea-tures cannot be used until the sys-tem PIN is changed.

Question: Nothing is indicated on the display of one of the connected ISDN telephones.

You have connected the ISDN tele-phone to an external S0 port (RJ-45 socket). These ports are intended for connection to the NTBA only. Con-nect the telephone to an internal S0 port (pressure terminal).

Question: Calls can be made but not received with one of the ISDN telephones.

The internal call number that has been configured for this ISDN tele-phone in the Configurator (PBX Configuration: Ports: S0 menu) must also be configured as an MSN on the ISDN telephone itself. For fur-ther information, refer to the User Guide of your ISDN telephone.

Question: It is not possible to con-figure Call Distribution: Outgoing for multi-terminal access.

You have configured multi-terminal access and system access in parallel. All outgoing calls are therefore es-tablished via system access, and out-going call distribution can be config-ured for system access only (Configurator, Call Distribution: Outgoing menu).

A specific MSN can be seized for indi-vidual calls by means of a code number procedure. For further infor-mation, refer to the “OpenCom 100, Operation on Standard Termi-nals”user guide.

Question: 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

163Frequently Asked Questions Telephony

164

provider. An unclean L1 clock distri-bution and the introduced signalling jitter is overheard by the human ear. Nevertheless, data and fax transmis-sions may be disturbed by the jitter. Please check, which ISDN lines will

deliver the L1 clock. One of the in-stalled 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 117.

DECT

Question: The LED of the RFP 21/23 base station is flashing, but none of the DECT devices is func-tioning.

Make sure the terminal setting for the corresponding Upn port is set to RFP 21/23 (Configurator, PBX Configuration: Ports: Upn menu).

Question: The LED of the RFP 21/23 is continuously lit up, but one of the cordless DECT devices is indi-cating “No connection”.

You have not configured a port for this DECT device. Configure a port in the Configurator and start the en-rolment procedure (PBX Configura-tion: Ports: DECT-PP menu).

Question: Is it possible to increase the time for the enrolment proce-dure?

You must manually enter the IPEI of the DECT device in the Configurator. The enrolment time is then in-

creased to one hour (PBX Configura-tion: Ports: DECT-PP menu).

Question: Another manufac-turer’s DECT device is not function-ing.

Check whether the DECT device sup-ports the DECT GAP standard. In the Configurator, also make sure GAP is set for this DECT device (PBX Config-uration: Ports: DECT-PP menu).

Question: The startup procedure of the RFP 21/23 take a long time? What is the reason?

This behaviour may indicate a prob-lem with the reference clock. Refer also to What are some of the causes for problems when sending and/or re-ceiving faxes? starting on page 163.

DECT Frequently Asked Questions

LAN

Question: Why is it not possible to establish a network connection with the OpenCom 510?

Check whether the LEDs for the hub and the PC’s network card are indi-cating a connection.

Check the LEDs for the LAN functions of the OpenCom 510. The green LAN LED at the top indicates whether the network cable has been properly connected.

To check whether there is a network connection with your OpenCom 510, enter the “ping IP address” com-mand in “Run” in the Windows Start menu (e.g. ping 192.168.99.254).

Question: 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 con-nected system telephones.

The code-number procedure *183 also displays the net-work mask.

Question: The network connec-tion is functioning, but nothing is displayed in the browser.

Enter the complete IP address of the OpenCom 510 along with the proto-col identifier, for example http://192.168.99.254/.

Check whether the browser has been configured for connection through a proxy server. If so, deacti-vate the “Connect through proxy server” setting.

Question: You have just config-ured the OpenCom 510 via the net-work. Why is it not possible now to establish a remote data transfer network connection?

The network card and the communi-cation (remote data transfer) adapter cannot be run with the same routing setting. Deactivate the network card before connecting via the dial-up network.

Question: Our network has grown over time, with several segments connected by one central router. How can PCs from all segments be connected via the OpenCom 510?

In the Configurator, use the LAN setting in ISP to specify the central router as the default gateway. If nec-essary, deactivate any filter rules de-

165Frequently Asked Questions LAN

166

fined for the ISP (NET Configura-tion: Connections: ISP menu). If several routers are configured for your network in different segments, you can enter extra static routes in the NET Configuration: Easy Access: Routes menu.

Question: 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 assign-ment for these PCs. Make the appro-priate assignment entries in the Configurator (NET Configuration: DHCP menu). Activate “Dynamic and static address”. If you fix a name for these IP addresses in the NET Con-figuration: Easy Access: Hosts menu, you can address the server PCs quite easily by the DNS names.

Internet

Question: I cannot access our company Web site.

Outside your system, your company Web site is accessed at “www.firm.com”, but in the Config-urator 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 enter-ing the direct IP address. If required, change the domain setting in the NET Configuration: Easy Access menu.

Question: 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 pos-sible to establish incoming Internet connections with the PCs directly owing to the network address trans-lation process.

Question: It is not possible to access the Internet with the OpenPhone 27.

The requirement for this is that the set should be configured as Hand-set+data. The telephone number used by the OpenPhone 27 to estab-lish an Internet connection must also be specified in the respective user profile (Configurator, User Manager: User menu).

With the OpenPhone 27, the Inter-net can be accessed either directly

Internet Frequently Asked Questions

via the remote data transfer network or indirectly via RAS access on the OpenCom 510. For direct access you can directly dial any provider. Indi-rect access uses the routing function of the OpenCom 510, accompanied by the configured security features, for example.

Directly via remote data transfer networkIf the Internet is accessed directly via the remote data transfer network, make sure that

■ the remote data transfer net-work 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 Configura-tion: Call Distribution: Outgo-ing menu).

Indirectly via RAS accessIf the Internet is accessed indirectly via RAS, the system administrator should make sure that:

■ permission has been given for Internet access via RAS (Config-urator, Net Configuration: Safe Access menu),

■ an internal number is configured for RAS access (Configurator,

Net Configuration: Connec-tions: RAS menu),

■ your user group has been granted RAS access rights (Con-figurator, User Manager: User Groups menu).

For information on the installation of software and on configuring Inter-net access, refer to the “OpenPhone 26/27” user guide.

167Frequently Asked Questions Internet

168

Technical DataPlease observe the technical infor-mation regarding modules under Modules starting on page 52.

Component Page

1-12 frame of the OpenCom 510

– 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

28

– 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: 12 22

Modules

– MPS+1-AC power supply unit (with AC/DC converter) 55

– MC+1-3 central control module 57

– MT+S2M1-1 trunk module 59

– MX+S01-8 subscriber or trunk module 62

– MS+UPN1-8 subscriber module 64

– MS+UPN2-8 subscriber module 65

– MS+A1-8 subscriber module 67

Technical Data

The following table provides an overview of the configuration limits for the OpenCom 510. These limits result from the combination of dif-ferent interface cards.

Note: The online help provides an overview of the limits that should be observed when configuring the OpenCom 510.

OpenCom 510: system configuration limits

maximum number of ports …via module …

2 (1 x Ethernet, 1 x V.24) MC+1-3

4 x S2M MT+S2M1-1

24 x S0 (for internal or external use) MX+S01-8

24 x Upn MS+UPN1-8

24 x Upn MS+UPN2-8

24 x a/b MS+A1-8

System configuration limits in general

1 CompactFlash card

169Technical Data

170

IndexNumerics

1-12 frame 15, 2119" frame 15, 21

A

a/b adapter 45a/b ports 40Accessories 48Actor

See Intercom system 42Adapter

Audio 46Cables (RS-232 - RJ-45) 16Upn 45

Add-on 48Authorisations 10

B

Backplane 15Exchanging 28

Basic setting 87Bundles 120Busy key 124

C

Call keys 123Clock 148

Synchronising the PC (via SNTP) 148

COM port 44Configuration 71

Client 79Configuration with Windows 74Establishing a network

connection 77Initial configuration 71

Installing the remote data transfer network under Windows 9x 76

Loading software updates 86Network card setup 76Preconfiguration 83RAS service 76Remote configuration 83Resetting the system data 87Saving and loading the

configuration 86Serial port (V.24) 76Starting the browser 78System prerequisites 72V.24 port 76

Configuration examples 89Introduction to TCP/IP 90OpenCom 100 in a LAN with an IP-

enabled server 93OpenCom 100 in a serverless

LAN 91RAS 93

Configuration guideEasy Access 155E-mail access 160E-mail function 159ISP settings 156LAN-to-LAN settings 158Overview 153PBX ports 154RAS settings 157

ConfiguringPreparation 80Starting the Web console 80

Control module 5, 15Functional description 57Installation 23

D

DECT 8, 164DHCP 89Direct call key 124

Index

DNS 92, 94DSL 43DSL port 43DSS1 117

E

E-mail 9

F

Factory settings 10FAQs 161Features 5

Internet factory settings 13Telephony factory settings 10

H

Hardware 161

I

Installation 15, 17Control module 23Installation in a 19" rack 21Interfaces 25Mounting 20Power supply units 27Scope of delivery 16

Intercom System 41Interface cards 5, 15

Installation 25Interfaces

a/b 40LAN 43MG+ETH1-1 105MS+A1-8 67MS+UPN1-8 64MS+UPN2-8 65MT+A1-4 and MT+A1-8 69MX+S01-8 62Overview 33S0 34, 37

S2M 59Upn 38V.24 6

InternetAccess 7Factory settings 13

Internet access 97Costs 97E-mail 98NAT 98Web 97

L

LAN port 43LCR 121LDAP 149Linux 79Log-in procedure 147

M

MacOS 79MC+1-3

see Control module 57MG+ETH1-1 105MPS+1-AC

see Power supply units 55MS+A1-8 67MS+UPN1-8 64MS+UPN2-8 65MT+A1-4 69MT+A1-8 69MT+S2M1-1 59, 118Multi-terminal access 5, 116Music on Hold 41

External devices 41Generating own files 87

MX+S01-8 62

N

NET CAPI 145NTBA 162

171Index

172

NTBBA 43Numbering 121

O

Online help 82OpenCTI 147OpenHotel 147Outlook Express 149

P

PBX networking 116PBX number 122PC status display 146Pin assignment

a/b interface 42Audio adapter 46IAE 36S0 interfaces 34Upn interface 39V.24 interface 44

Point-to-point connections 118Ports (see Interfaces) 33Power failure 31Power supply units 5, 15

Functional description 55Installation 27

Q

Q.SIG 117

R

Remote configuration 83Resetting system data 87Routes 120

S

S0 port 163S0 ports 34

External 37

Internal 37S2M 117Safety precautions 17Saving and loading the

configuration 86Sensor

See Intercom system 42Slots 22SNTP 148Software updates, loading 86System access 5, 116System data, resetting 87Systray display 146

T

Team functionsExplanation of keys 123Introduction 123

Team key 124Telephony 162Telephony factory settings 10Terminals

Overview 33Three-member team 126Time

After a power failure 31Time zone 148Toggle team 128Troubleshooting 161Trunk key 123

U

Unified team 127Upn ports 38

V

Voice Mail 41

Index

In the UK: DeTeWe Ltd • 1 Frogmore Road • Hemel Hempstead • Herts, HP3 9TGwww.detewe.co.uk

Other countries: DeTeWe Systems GmbH • Zeughofstraße 1 • D-10997 Berlin • Germanywww.detewe.de

As of June 2005Subject to changes

OpenCom 510 - United Statespbxweb.aastra.com/extra/opencom/oc100/software/Montage... · Features 5...

Documents

Transcript of OpenCom 510 - United Statespbxweb.aastra.com/extra/opencom/oc100/software/Montage... · Features 5...