If the CNIP (calling name identification presentation) feature is supported by your network provider, the latter will show you the name of callers in addition to their number for each incoming trunk call. The

OpenCom 100 supports the display of the name on system telephones.

However, if you have created an entry in the telephone book of the

OpenCom 100 under the number of the caller, this will be displayed instead.

The OpenCom 100 can be integrated into an existing network

(LAN) and be used by all workstations as an Internet access router and mail client.

Features

Configuration and programming of the OpenCom 100 is performed by means of a special Web browser

(known as the “Web console”), which can be run on a connected PC.

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

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

To connect the OpenCom 100 with the existing company hardware, there are two actor ports (output) and one sensor port (input) available. These can be used to operate a door opener and a doorbell via the system, for example (this requires additional equipment).

The OpenCom 100 allows you to use

CTI (computer telephony integration) applications made by other manufacturers. This requires installation of a TAPI driver (supplied on the system CD-ROM) on a Windows

PC. The OpenCom 100 also has an integrated dialling wizard, the

OpenCTI 50, with which users can call up and use telephone functions on PCs without first having to install a special TAPI driver.

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

Packet data in the D channel

Some business applications, for instance POS terminals, cash registers or creditcard terminals, require a permanent data connection over the

X.25 packet data network. Packet data transfer through the ISDN D channel (according to X.31 via SAPI

16) can also be established between several S

interfaces of the

OpenCom 100. Simultaneous connections are distinguished by means of a TEI (Terminal Endpoint Identifier).

X.31 packet data can be forwarded between two S

interfaces (for instance an internal and external S

interface). Equally, data can be forwarded (“routed”) over permanent

QSIG lines. Data can also be routed over an S

interface.

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

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

Internet Access

It is possible to connect individual

PCs to the OpenCom 100 via the internal S

ports, or to connect an entire LAN to the OpenCom 100 via the

Ethernet port. These PCs can access the Internet via the OpenCom 100.

For this purpose, several call-by-call providers are preset on the

Features

OpenCom 100 (only national setting

“Germany”). If Internet access is already available from an Internet service provider, this can be configured in the OpenCom 100. If the client network is not IP-capable, the

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

The OpenCom 100 enables Internet access for all connected PCs by means of a common IP address. Only this is externally visible. The local IP addresses of the client PCs are translated to the IP address of the

OpenCom 100 by network address translation (NAT). In this way the client PCs in the LAN cannot be reached directly from the Internet.

This protects them from direct external attack. The LAN is additionally protected by the OpenCom 100 filter lists, which can be customised individually (firewall function).

Note: We recommend you to read

through the explanations under Useful Information on Internet Access starting on page 70.

DECT Data Communication

A USB DECT Box or the

OpenPhone 25 DECT terminals enable PCs that are not connected to the

OpenCom 100 via the internal S

0 ports or the Ethernet interface to access the Internet. These PCs can make full use of all the Internet and e-mail features of the OpenCom 100.

Data is transmitted via the internal data interface of the OpenPhone 25, which must be connected to the serial port of the PC by means of the supplied adapter. The Internet can then be accessed directly via the remote data transfer (i.e. dial-up) network. The OpenPhone 25 sets up a data connection with the

OpenCom 100 via the DECT air interface. The remainder of the connection set-up is either direct - through an ISDN B-channel - or indirect - through the internal RAS access of the OpenCom 100. Indirect RAS access is preferable. This uses the routing function of the OpenCom 100 and thus also the security features of the shared Internet access.

Using the USB DECT Box obtainable as an add-on, it is possible for a PC to establish a wireless (DECT) ISDN data connection. This USB DECT Box is connected to the PC via the USB port.

For detailed information on the installation of the required driver software and the various types of con-

figuration, refer to USB DECT Box on

the OpenCom 100 starting on page 109 and to the user guide for

the OpenPhone 25.

For information on configuration of the OpenPhone 25 with a data interface, please refer to the online help

Features

documentation of the

OpenCom 100.

E-mail

The OpenCom 100 has an integrated e-mail function that is able to use the POP3, APOP or IMAP4 protocols to check the Internet service provider for incoming mail. A mail account query can be configured for every member of staff

(OpenCom 100 user). The

OpenCom 100 then fetches the incoming e-mail headers (subjects) and senders from the mail server at set intervals, and forwards them to users’ system telephones.

Further Network Features

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

RAS access.

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

OpenCom 100s can connect their

LANs by dial-in on demand.

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

PCs that do not possess a built-in

ISDN card.

Further Telephony Features

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

You can optimise your telephone communication by using the team

Features

functions and the call-queuing function.

You can also connect two

OpenCom 100s. This cascading of telecom systems is a simple way to increase the number of terminals that can be connected.

As your company’s requirements grow, the OpenCom 100 can be networked with other telecom systems.

The OpenCom 100 can then operate as a sub-system or DECT server. It is also possible to create a telecom system with several networked telecom installations.

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

Features

Factory Settings on Delivery

The following basic settings and features are active on delivery. We recommend that you configure the

OpenCom 100 to your individual requirements before putting it into

operation (see Configuration starting on page 45).

Telephony Functions

OpenCom 107/105

■

The S

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

2 port for system access.

■

The S

3 and S

4 ports are configured as internal S

buses with the call numbers 20 and 21.

■

The four U pn

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

■

The four a/b ports are configured for analogue devices with the call numbers 10 to 13.

OpenCom 110

■

The S

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

2 port for system access.

■

The S

3, S

4 and S

5 ports are configured as internal S

buses with the call numbers 20 to 22.

■

The eight U pn

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

■

The four a/b ports are configured for analogue devices with the call numbers 10 to 13.

OpenCom 120

■

The S

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

2 port for system access.

■

The S

3 to S

6 ports are configured as internal S

buses with the call numbers 20 to 23.

■

The 18 U pn

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

Telephony Functions Factory Settings on Delivery

■

The four a/b ports are configured for analogue devices with the call numbers 10 to 13.

All OpenCom 100

Communication Systems

■

The OpenCom 100 is configured ready for operation in Germany.

■

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

■

All cord-bound terminals connected ring when there are incoming external calls.

■

The system PIN, for example for remote-programmable call diversion, is set at “0000”.

Authorisations

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

Two user groups are preset: “Administrators” and “Guests”. “Administrators” have access to all functions of the OpenCom 100 and unrestricted configuration rights. Users in the

“Guests” group cannot configure the

OpenCom 100, are not able to make external calls, and have only restricted use of the terminal functions of the OpenCom 100.

Note: When the OpenCom 100 is

commissioned, all connected terminals are initially in the “Administrators” group until a user logs on to the

Web console. Subsequently, all terminals are automatically in the “Guests” group (see also the chapter entitled

Configuring the OpenCom 100 starting on page 54). For more details on

the configuration of user groups, refer to the online help in the chapter entitled “User Manager”.

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

■

External line access: international numbers can be dialled from all configured telephones.

External lines must be seized by entering a prefixed code.

■

Least cost routing is not active.

As soon as LCR is configured, users can make calls via individually selected call-by-call providers.

■

“VIP call” is activated.

Factory Settings on Delivery Authorisations

■

Announcements to system telephones are possible.

■

Baby calls can be set up.

■

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

■

“Pick-up” and “selective pickup” of calls from other telephones are activated. Pick-up protection is deactivated.

■

“Call seizure” is deactivated.

■

The “completion-of-calls to busy subscribers” feature can be activated.

■

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

■

The “call queue” function is deactivated.

■

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

■

Call forwarding to internal or external numbers can be activated.

Call forwarding on no reply is executed after 20 seconds. Doorway calls can be forwarded.

■

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

■

Three-party conferences can be set up.

■

Call protection, call-waiting protection and intercom protection are deactivated.

■

The transmission of one’s own phone number (MSN or system access number) to the display of the external party’s terminal is activated, but can be hidden.

■

The telephone lock can be activated. The terminal PIN is

“0000”.

■

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

■

Speed dialling is possible if this has been configured in the

OpenCom 100 central telephone book.

■

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

Authorisations Factory Settings on Delivery

■

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

■

Keypad dialling can be used.

■

Call diversion for SMS calls in the wired network is not activated.

■

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

■

The cost multiplier is set to

100%, i.e. the costs are not multiplied by any factor.

■

Every user can change the configuration of the OpenCom 100.

■

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

■

Every user can read out the charges.

■

Every user who has a workplace

PC can use the OpenCTI 50 to make calls, manage calls and messages, dial numbers from both the central and personal telephone books, and use the busy display of the OpenCTI 50.

■

The multi-company variant is not activated.

Internet Functions

Note: Settings for mail and ISP and

RAS access are only possible by acti-

vating the OpenCom 100 IP package

in the Web console’s Configurator in

the SYS Configuration: Licences

menu. Also refer to Information Regarding the Licensing of the IP Package for the OpenCom 100 on page 14.

■

RAS access (with or without callback) can be set up for every

OpenCom 100 user. RAS access requires activation of the RAS authorisation.

■

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

■

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

■

Users can disconnect existing Internet connections (via the

OpenCom 100 Web console and from a system terminal if the function has been configured on that terminal).

Factory Settings on Delivery Internet Functions

The following IP addresses are preset for the network configuration:

■

Host name: host

■

IP address: 192.168.99.254

■

Network mask: 255.255.255.0

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

■

Gateway address:

192.168.99.254

■

Domain name: domain

■

Domain name server:

192.168.99.254

■

PPP addresses: 192.168.100.0 to

192.168.100.10

■

DHCP addresses: 192.168.99.129 to 192.168.99.148

You can change the IP settings in the

Configurator. Check with the network administrator responsible for the LAN if you wish to do this.

Information Regarding the

Licensing of the IP Package for the OpenCom 100

In order to be able to use the IP package in your communications system, you need an activation key.

You can generate the activation key on the DeTeWe licence server

(http://lizenz.detewe.de).

The activation key is generated on the basis of the serial number of your OpenCom 100 and the transaction record (TAD). The licensing confirmation you received together with your IP package contains all the information you need to carry out this procedure plus your personal TAD.

To generate the activation key for the IP package of the

OpenCom 105, no TAD is required.

The serial number is all you need.

You have therefore not received a separate licence confirmation. Enter the serial number of your

OpenCom 105 in the corresponding field at http://lizenz.detewe.de.

You can read out the serial number on the Web console of the

OpenCom 100 in the Configurator

in the System info: Versions menu.

Please note that the serial number is case sensitive. Leave the field for the

TAD blank.

Note or print out the generated activation key.

Then release the IP package on the

Web console in the Configurator in

the SYS Configuration: Add-ons menu. Additional information can be found in the online help.

Internet Functions Factory Settings on Delivery

Installation

Scope of Delivery

The delivery consists of:

■

One OpenCom 100 communications system (OpenCom 107,

OpenCom 105, OpenCom 110 or

OpenCom 120)

■

Two connection cable for the

ISDN S

port

■

One V.24 connection cable

■

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

COM port of the OpenCom 107/

105)

■

One set of mounting screws and wall plugs

■

A 1.5 m power cable (OpenCom

105, OpenCom 110 or

OpenCom 120 only)

■

One plug-in power supply

(OpenCom 107 only)

■

One OpenPhone 52 quick user guide

■

One OpenPhone 61,63,65 quick user guide

■

One OpenPhone 21, 25 quick user guide

■

One CD

Installation Scope of Delivery

Safety Precautions

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

Please note: Installation and

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

CAUTION!

Static charges can damage the

OpenCom 100. Make sure you discharge yourself and your tools before and while installing electrical and electronic components of the OpenCom 100.

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

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

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

Only devices that deliver safety extra-low voltage (SELV) may be connected to the OpenCom 100. Proper use of authorised devices meets this requirement.

Only devices meeting the technical requirements may be connected to the analogue ports. For details, refer

to the section entitled a/b Ports starting on page 24.

Use a shielded Ethernet cable (STP cable, Shielded Twisted Pair cable) to connect the OpenCom 100 to a Local

Area Network (LAN).

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

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

Safety Precautions Installation

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

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

Declarations of Conformity

The OpenCom 107, OpenCom 105,

OpenCom 110 and OpenCom 120 systems conform to the requirements set down in the EU directive

99/5/EC.

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

Mounting Location

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

To maintain the prescribed ambient temperature, mount the

OpenCom 100 in a well-ventilated location, away from direct sources of heat.

Do not position the OpenCom 100

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

■ in direct sunlight,

■ behind curtains,

■ in small, unventilated, damp rooms,

■ on or near inflammable materials,

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

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

Installation Declarations of Conformity

Wall Mounting

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

To fasten the screws at points B and

C, remove the cover of the

OpenCom 100 and insert the screws in the holes provided for this purpose. The OpenCom 100 is suspended from the screw at point A, so there must be a space of 3 mm between the screw and the wall.

184

Mounting plan

332

134

Available Ports

The OpenCom 100 has the following

OpenCom 107

■

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

■

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

■

One S

port for connection to an external S

bus (usually the

NTBA), designed as an RJ45 socket (S

■

Two switchable S

ports (S

2 and S

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

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

RJ45 socket

■

One S

port for an internal S

0 bus, designed as a pressure terminal (S

4). S

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

OpenCom 100 communications systems in a Q.SIG trunk (also re-

fer to PBX Networking starting on page 73).

Wall Mounting Installation

■

Four U pn

ports, designed as pressure terminals (U pn

1 to

U pn

■

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

■

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

■

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

CAUTION! It is not allowed to operate the plug-in power supply inside the housing of the

OpenCom 107.

OpenCom 105

■

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

■

Two actor ports for connection to a door opener and entrance intercom system, designed as pressure terminals (Actor1 for activating a door opener and

Actor2 for activating an entrance intercom)

■

One sensor port for connection to the bell of an entrance intercom system, designed as a pressure terminal (sensor)

■

One PCM port for the connection of two systems, designed as an

RJ45 socket (PCM)

■

One S

port for connection to an external S

bus (usually the

NTBA), designed as an RJ45 socket (S

■

Two switchable S

ports (S

2 and S

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

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

RJ45 socket

■

One S

port for an internal S

0 bus, designed as a pressure terminal (S

4). S

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

OpenCom 100 communications systems in a Q.SIG trunk (also re-

fer to PBX Networking starting on page 73).

■

Four U pn

ports, designed as pressure terminals (U pn

1 to

U pn

■

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

■

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

Installation Available Ports

OpenCom 110

■

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

■

Two actor ports for connection to a door opener and entrance intercom system, designed as pressure terminals (Actor1 for activating a door opener and

Actor2 for activating an entrance intercom)

■

One sensor port for connection to the bell of an entrance intercom system, designed as a pressure terminal (sensor)

■

One PCM port for the connection of two systems, designed as an

RJ45 socket (PCM)

■

Two S

ports for connection to an external S

bus (usually the

NTBA), designed as RJ45 sockets

1 and S

■

Two switchable S

ports (S

2 and S

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

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

RJ45 socket

■

One S

port for an internal S

0 bus, designed as a pressure terminal (S

5). S

5 can also be wired externally (as a master) when networking two

OpenCom 100 communications systems in a Q.SIG trunk (also re-

fer to PBX Networking starting on page 73).

■

Eight U pn

ports, designed as pressure terminals (U pn

1 to

U pn

■

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

■

One sync port for synchronisation with another telecom system, designed as a pressure terminal (Sync)

■

One COM port for connection to a PC for configuration or transfer of call data, designed as a 9-pin submin D port (V.24)

OpenCom 120

■

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

■

Two actor ports for connection to a door opener and entrance intercom system, designed as pressure terminals (Actor1 for activating a door opener and

Actor2 for activating an entrance intercom)

■

One sensor port for connection to the bell of an entrance intercom system, designed as a pressure terminal (sensor)

Available Ports Installation

■

One PCM port for the connection of two systems, designed as an

RJ45 socket (PCM)

■

Six switchable S

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

bus.

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

■

18 U pn

ports, designed as pressure terminals (U pn

1 to U pn

18)

■

Two LAN ports (10BaseT), designed as RJ45 sockets. The second LAN port of the

OpenCom 120 is intended only for networking two

OpenCom 120/120 or 110/120 systems

■

One sync port for synchronisation with another telecom system, designed as a pressure terminal (Sync)

■

One COM port for connection to a PC for configuration or transfer of call data, designed as a 9-pin submin D plug (V.24)

Installation Available Ports

Positions of the Ports

The following diagrams show the positions of the ports on the

OpenCom 100 variants:

Default setting

LAN

COM S

0 ext

1 S

0 ext

2 S

0 ext

Position of ports on the OpenCom 107

2 int

3 int

4 int

U pn

1/2

U pn

3/4 a/b

1/2 a/b

3/4

Actuator

Default setting

Intercom/Relay

Intercom/Door opener

PCM LAN COM S

1 ext

2 ext

3 ext

Position of ports on the OpenCom 105

0 int

2 S

0 int

3 S

0 int

4 U pn

1/2

U pn

3/4 a/b

1/2 a/b

3/4

Actuator

1 + 2

Sensor

PCM LAN

Sync Sensor Default setting

Intercom/Door opener Intercom/Relay

1 ext

2 ext

3 ext

4 ext

0 int

3 S

0 int

Position of ports on the OpenCom 110

COM

0 int

5 Actuator

1 + 2

U pn

1/2

U pn

3/4

U pn

5/6

U pn

7/8 a/b

1/2 a/b

3/4

Available Ports Installation

PCM LAN 1 LAN 2

Sync Sensor Default setting

Intercom/Door opener Intercom/

Relay

U pn

9/10

U pn

11/12

U pn

13/14

U pn

15/16

U pn

17/18

1 ext

0 ext

1 int

2 int

3 int

4 int

Position of ports on the OpenCom 120

COM

0 ext

5 int

6 int

Actuator

1 + 2

U pn

1/2

U pn

3/4

U pn

5/6

U pn

7/8 a/b

1/2 a/b

3/4

Port Assignment, Termination,

Cable Lengths

S

Ports

Whether you use the switchable

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

Note that the S

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

OpenCom 110 and OpenCom 120 are marked with an “R” in the diagrams

Positions of the Ports on page 22 and

are implemented as switch hooks.

Open the switch if you do not wish to terminate the bus with the

OpenCom 100.

In the case of the OpenCom 107/

105, the S

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

0 port configuration in the Con-

figurator on the Web console.

You can connect up to eight terminals on every internal S

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

The length of the four-wire cable of an internal S

bus must not exceed

150 m. The power consumption of each internal S

bus is approx. 3 W.

Installation Port Assignment, Termination, Cable Lengths

OpenCom 110

OpenCom 120

IAE IAE

The S

bus is terminated at one end by

the OpenCom 100; the hook switch is

closed.

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

TR = terminating resistor, the S

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

OpenCom 110

OpenCom 120

TR TR

IAE

The S

bus is terminated by the TR at the ends; the hook switch is open.

Termination on an ISDN socket

U

Ports

Each of the U pn

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

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

port of an interface card is 1,000 m when

0.6 mm cable (with twisted pairs) is used. The power consumption of each U pn

port is approx. 3 W.

U pn

/RFP with 1 U pn

0 int

2a 2b 1a 1b

1 2 3 4 5 6 7 8

RFP with 2 U pn

1 2 3 4 5 6 7 8

Pin assignment of the S

and

U pn ports

a/b Ports

The a/b ports are for operating analogue devices (a fax machine, modem or telephone). The maximum permissible length of the cable is

1,000 m when twin-wire 0.6 mm cable (with twisted pairs) is used.

If an entrance intercom system is connected to a/b1, the switch

marked “E” on the diagram Positions

Port Assignment, Termination, Cable Lengths Installation

of the Ports starting on page 22 must

be open in order to isolate the low frequency voltage from the supply

(see also the following section enti-

tled Actor/Sensor on page 25).

Note: With the newer structure of

the communications system, the switch is electronic. For this reason, there is no “E” switch with this structure.

Actor/Sensor

In order to operate an entrance intercom and door opener, you need four twin-wire cables:

■ one cable between the entrance intercom and the a/b1 port,

■ one cable between the door opener and the Actor1 port

(marked Intercom/Door opener

in the diagram Positions of the

Ports starting on page 22),

■ one cable between the intercom input and the Actor2 port

(marked Intercom/Relay in the

diagram Positions of the Ports starting on page 22) to activate

the amplifier as well as

■ one cable between the doorbell and the sensor port.

Only use entrance intercoms and door openers complying with the

German FTZ Guideline no. 123D12.

LAN Port

The LAN port (OpenCom 120: LAN 1 port) enables integration of the

OpenCom 100 into an existing inhouse LAN by means of a 10 Mbit hub.

A LAN line (twisted-pair line in accordance with 10BaseTcan be up to

100 m long. Use a shielded Ethernet cable (STP cable, Shielded Twisted

Pair cable).

The second LAN port of the

OpenCom 120 is intended only for networking two OpenCom 120/105,

120/110 or 120/120 systems.

DSL Port

External DSL modems can be connected via the LAN port. In the case of the OpenCom 100, the output of the DSL modem (NTBBA) is led to the

LAN port of the OpenCom 100

(LAN 1 in the case of the

OpenCom 120) via an external switch or hub. The router subse-

quently converts the PPPoE protocol

to the TCP/IP protocol of the LAN.

Installation Port Assignment, Termination, Cable Lengths

OpenCom

TAE

DSL & Uk

Net

DSL

Splitter

TCP/IP &

PPPoE

DSL

NTBA S

Crosslinked twisted pair cable

PPPoE

TCP/IP

DSL

Modem

Hub

Connecting the OpenCom 100 to the network via ISDN and DSL

Net

Basic Setting Switch

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

“X”.

Using the basic setting switch, it is possible to reset the OpenCom 100 system to the factory configuration

(see Factory Settings on Delivery starting on page 10).

PCM Port

The position of the switch can be

seen in the diagram Positions of the

Ports starting on page 22.

The PCM port is used to connect two

OpenCom 120 systems, or an Open-

Com 110 with an OpenCom 120 system by a special transmission procedure called pulse code modulation.

The RJ45 cable used must not exceed 4 m in length.

Sync Port

The twin-wire Sync port is used when the OpenCom 100 serves as a subsidiary system for a main system that is a DECT system.

Please note: The current configu-

ration data is lost, the system is reset to the default configuration. For this reason you should back up your configuration regularly, the best time being after every change. For details, re-

fer to the chapter entitled Saving and

Loading the Configuration starting on page 59 and to the Web console on-

line help documentation.

Port Assignment, Termination, Cable Lengths Installation

Power Failure

In the event of a power failure, all the contents in the memory (program and user data) are saved without change. The internal clock continues to run for 24 hours. If the power failure lasts longer than

24 hours, the time and date are reset to the factory setting when power is switched on again. When the first external outgoing call is made, the time and date are set to the current value as given by the exchange.

On the multi-terminal access, the

OpenCom 105, the OpenCom 110 and the OpenCom 120 include an emergency service. In the event of a power failure, the external S

1 port is switched over to the internal S

5 port (in the OpenCom 105to the S

4 port) so that you can still use a connected telephone to make a call.

Emergency operation on a system access is not possible.

Connectible Devices

The OpenCom 100 ports offer a large number of possibilities for connecting devices. One of the many possible configurations is shown in the following diagram:

Hub

Intercom/Relay

Intercom/Door opener

LAN

Sensor

1 ext S

2 ext S

3 ext S

4 ext

R R R R

NTBA NTBA NTBA NTBA

COM

5 int

Actuator

1 + 2

U pn

1/2

U pn

3/4

U pn

5/6

U pn

7/8 a/b

1/2 a/b

3/4

Example of port assignment of the OpenCom 110 with terminals

Installation Power Failure

Internal/External

S

Ports

The S

0 ports

■

2 and S

3 (OpenCom 107/105)

■

3 and S

4 (OpenCom 110)

■

1 to S

6 (OpenCom 120) can either be connected externally

(i.e. to ISDN network terminators) or internally; simultaneous use of both is not possible.

The S

4 internal (OpenCom 107/105) or the S

5 internal (OpenCom 110) can also be wired externally (as a master) when networking two

OpenCom 100 communications systems in a Q.SIG trunk (also refer to

PBX Networking starting on page 73).

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

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

0 buses enable point-to-multi-point calls as per the DSS1 protocol (Euro-

ISDN).

U

Ports

A system terminal can be connected to every U pn

port by a twin-wire cable. The OpenPhone 61, OpenPhone

63 and OpenPhone 65 are cordbound system terminals. The Open-

Phones 63 and 65 can be cascaded on a U pn

adapter so that you can operate two OpenPhones on one U pn port. For further details, refer to the

“OpenPhone 61, 63, 65” user guide.

The RFP 21 base station is required for the use of cordless system telephones (e.g. OpenPhone 21 or

OpenPhone 25). The OpenPhone 25 features a V.24 port on which you can transfer data and surf on the Internet.

If this base station is connected to a

U pn

port, four simultaneous calls are possible with the mobile parts. If the base station is connected to two U pn ports, eight simultaneous calls are possible. However, note that only as many external connections are possible as there are connected B-channels available.

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

You can also operate the

OpenPhone 52 ISDN terminal on a

U pn

port.

Connectible Devices Installation

a/b Ports

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

■ analogue telephones

■ class 3 fax machines

■ analogue modems (external or internal)

■ external devices for music on hold

■ external voice mail systems.

Please note: Adhere to the fol-

lowing notes and recommendations regarding the connection of analogue devices. Devices not meeting the technical requirements of the

OpenCom 100 can cause damage to it.

Analogue Telephones

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

Modems

The maximum transmission rate for analogue modems is 33.6 kbit/s

(V.34+).

Music on Hold

A suitable external device for music on hold is the Genius 2000, manufactured by Speech Design. If you do not operate an external MoH device, the Access 5000 offers an internal

MoH, which you can load in the Web console Configurator, SYS Configu-

ration: Components menu. For details, refer to the online Help.

Please note: Use only devices

with an input impedance of

600 ohms, floating connection, for external music on hold. Incorrect input impedance can cause irreparable damage to the OpenCom 100.

Voice Mail

If you are using an external voice mail system, it must be capable of handling the number of digits used for internal telephone numbers, e.g. five digits if you have configured five-digit internal numbers. We recommend the following Speech Design products: Memo 200/300/400 or Memo 200-A/300-A/400-A.

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

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

* 6 8 resp. # 6 8 .

Installation Connectible Devices

Intercom System (for a/b)

The intercom systems “DoorLine

T01/02” and “DoorLine T03/04” of the german Telekom’s division

T-Com can be connected via the

“DoorLine M06” to any a/b port. The

“Doorline” module provides the actor for the door opener contact.

Observe the following for connection and use of the intercom system:

■

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 Doorline under Type. Activate the Actua-

tor option, if you want to use the actor port of the OpenCom 100 instead of the “DoorLine” relay.

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

■

The “Doorline” intercom system has a number of bell keys to which you can assign different call numbers in the

PBX Configuration: Ports:

Doorline menu in the Configurator.

■

You can call the “Doorline” intercom system by entering the code procedure * 1 0 2 .

■

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

OpenCom 100.

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

The intercom system should be installed by qualified personnel only as sensor/actor contacts will need to be connected for this procedure.

Connectible Devices Installation

Actor/Sensor Ports

For the assignment of the ports, re-

fer to the section Available Ports starting on page 18. The

OpenCom 100 also functions together with a Freehand Entry-Phone manufactured by Siedle or Behnke.

a/b1

Relay

Actor2

Actor1

Door opener

-T

Ts* b a

PVG 402-0

Amplifier

12 c1

Sensor

230 V ~

NG 402-02

Ac adapter b c

12 V ~

Connection of doorway equipment produced by Siedle

Note: The above diagram shows

the usage of the “PVG 402-0” module

(which merely serves as an example).

Other modules can also be operated, such as its successor, “PVG 602-01”.

Siedle

Door bell

Installation Connectible Devices

COM Port

Please note: The connection line

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

A PC for configuring the

OpenCom 100 or transmitting call data can be connected to the COM port. This call data can be evaluated in detail with the call charge registration program OpenCount.

LAN Port

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

The OpenCom 120 has a second LAN port for cascading your telecom system with another OpenCom 105,

OpenCom 110 or OpenCom 120 (see

PBX Cascading starting on page 73).

Connectible Devices Installation

Accessories and Adapters

The OpenPhone 63 and

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

65” user guide under “Add-ons (with

& without an Adapter)”.

Note: An extra plug-in power sup-

ply is required to operate combinations of equipment with a power consumption that exceeds the power output of the U pn

ports.

a/b Adapter

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

You can use an a/b adapter to connect analogue terminals to the

OpenPhone 63 and OpenPhone 65 system telephones.

U

Adapter

The U pn

adapter is an adapter with a

U pn

port for connecting another

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

Weight: 70 g

Dimensions: 73 x 60 x 30 mm

Power consumption: max. 195 mW

Cable length: max. 30 m

Please note: The U

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

U pn

extension cable must not exceed

30 m in length and must not be used outdoors.

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

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

Note: Please use the plug-in power

supply with the product code

4505759. The plug-in power supply for use in the UK has the product code

4510694.

Weight: 70g

Dimensions: 73 x 60 x 30 mm

Power consumption: max. 160 mW

Cable length: max. 3 m

Accessories and Adapters

Audio Adapter

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

Audio Adapter Pin Assignment

Port

Weight: 70g

Dimensions: 73 x 60 x 30 mm

Power consumption: max. 260 mW

(with relay active).

Used for

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

Socket

RJ-10

(4-pin

Western socket)

Assignment

1: microphone -

2: speaker +

3: speaker -

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

Not used on

OpenCom 100

Door display

Stereo jack,

3.5 mm

4: microphone +

1 (GND): recording signal, relay contact 1

2 (peak): recording signal +

3 (ring): relay contact 1

Round power socket

(4 mm)

RJ-11 or

RJ-12

(6-pin

Western socket)

4, 5: relay contact 2

1, 2, 3, 6: NC

Accessories and Adapters

Electrical Data of Ports

Port

Microphone, microphone of second handset, headset microphone

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

Active speaker

Recording device audio input

Recording device start/stop

(relay contact 1)

Door display

(relay contact 2)

Connection Values

Electret microphone

Typical sensitivity: 10 mV/Pa

Power feed: I < 300 µA at 1.5 V

Typical impedance: 150 ± 30 ohms

Typical sensitivity: 94 dB/1 mW

(0 dB = 20 µPa)

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

Typical input sensitivity: 0.24 mV

(microphone level)

Max. switching voltage: 50 VDC/29 V AC

Max. switching current: 1 ADC/0.7 A AC

Max. switching voltage: 50 VDC/29 V

Max. switching current: 1 ADC/0.7 A AC

Accessories and Adapters

Approved Devices /

Approved Accessories

Please note: Only the following,

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

The following devices are recommended:

Type

Headset:

Headset adapter cable:

Second handset

Handset

Microphone:

Loudspeaker:

Recording device:

Manufacturer, Product Designation

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

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

GN Netcom, QD cable (quick coupling), smooth,

Mod 4 (8800-00-01)

Siemens, L30351-F600-A366

DeTeWe, OpenPhone 60

Winfinity, 4511326 / H 282-18

Siemens, L30460-X1278-X

No recommendation

Accessories and Adapters

Device Combinations

These symbols are used in the following tables:

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

■

U pn

adapter: 195 mW

■

Audio adapter: 260 mW

■ a/b adapter: 160 mW

(must be combined with a plugin power supply!)

●

This combination is possible.

❍

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

Configurations without

Plug-in Power Supply

(Range up to 500 m)

■

OpenPhone 61: 1,000 mW

■

OpenPhone 63: 1,025 mW

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

■

OpenPhone 65: 1,140 mW

■

Up to three add-on keypads:

330 mW

Basic Unit: OpenPhone 63

–

●

Add-ons

Audio adapter U pn adapter Up to 3 keypad modules

– –

–

●

–

Second Terminal Power

–

OpenPhone 61

OpenPhone 63 without adapter

1025 mW

1285 mW

2220 mW

2245 mW

–

●

– 2360 mW OpenPhone 65 without adapter or keypad module

Accessories and Adapters

Basic Unit: OpenPhone 65

–

●

Add-ons

Audio adapter U pn

adapter Up to 3 keypad modules

– –

–

●

–

●

–

Second Terminal Power

–

OpenPhone 61

OpenPhone 63 without adapter

1140 mW

1470 mW

1730 mW

2335 mW

2360 mW

–

❍

– 2475 mW OpenPhone 65 without adapter or keypad module

Configurations without

Plug-in Power Supply

(Range 500 to 1000 m)

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

Basic Unit

OpenPhone 63

OpenPhone 65

Add-ons

–

●

Audio adapter U pn

adapter Up to 3 keypad modules

●

– –

–

●

Power

1285 mW

1470 mW

1730 mW

Accessories and Adapters

Configurations with

Plug-in Power Supplies

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

Basic Unit: OpenPhone 63

Add-ons:

Up to 3 keypad modules

Audio adapter

Second terminal

●

U pn

adapter and plug-in power supply

OpenPhone 61 OpenPhone 63 without adapter

OpenPhone 65 without adapter and with 1 keypad module

●

Basic Unit: OpenPhone 65

Add-ons:

Up to 3 keypad modules

Audio adapter

●

Second terminal

●

U pn

adapter and plug-in power supply

OpenPhone 61 OpenPhone 63 without adapter

OpenPhone 65 without adapter and with 1 keypad module

●

Accessories and Adapters

S

Connector Module

The S

connector module allows you to operate an OpenCom 120 on a primary rate access. This access provides up to 30 voice channels.

You can also use the S

port to network two systems, e.g. in order to use the OpenCom 120 as a subsidiary system or DECT server.

Note: The maximum cable attenu-

ation between the OpenCom 120 and the other system (NT or telephone exchange) must not exceed 6 dB. This corresponds to a length of approx.

150 to 200 m, depending on the type of cable used.

PCM LAN 1 LAN 2

Sync Sensor Default setting

Intercom/Door opener Intercom/

Relay

U pn

9/10

U pn

11/12

U pn

13/14

U pn

15/16

U pn

17/18

0 ext

COM

1 int

2 int

3 int

4 int

5 int

6 int

Actuator

1 + 2

U pn

1/2

U pn

3/4

U pn

5/6

Location of the S

port on the connector module of the OpenCom 120

U pn

7/8 a/b

1/2 a/b

3/4

Installation

Please note: The module should

only be installed by trained personnel.

DANGER! The device contains hazardous voltages.

2. Open the housing of the

OpenCom 120.

3. For some models of the

OpenCom 120 a separate module cover exists. Remove the cover of the module. To do this, push back the two locking levers, (1) and (2), and lift off the cover.

1. Pull out the mains plug of the

OpenCom 120.

Connector Module

1 2

LEDs

slot

(Underside of the module board)

Removing the module cover

4. On the module board, remove the protective covers of the two

slots (3) and (4).

slots

Activity LED

PCM LAN 1 LAN 2

Position of the S

slots on the module board

5. Insert the S

module into the slots, making sure you insert the

LED side of the module into the upper slot (4).

Position of the LEDs on the

module

6. Replace the module cover. To do this, insert the locking hooks at the lower end of the cover into the recesses on the connection module. Press the module cover until the upper locking levers engage.

7. Wire the S

port of the connector module to the NT or the other PBX according to the following drawing. Make sure the

RX and TX lines are crossed over

(connect the RX lines of the

OpenCom 120 to the TX lines of the other PBX).

Connector Module

PBX 1, S

Rx+ Rx- Tx+ Tx-

PBX 2, S

(Pressure clamps)

Example of the wiring of the S2M port

for two OpenCom 120s

8. If necessary, check to make sure that the NT is fed by its own power supply.

9. Reconnect the OpenCom 120 to the power supply.

10. Configure the S

module in the Configurator of the

OpenCom 120 (refer to Configu-

ration starting on page 45).

Check the level 1 status with reference to the LEDs on the module. None of the LEDs are illuminated before the S

module has been configured.

LED Displays

LED Meaning

1 (green) Synchronous (= ok)

2 (green) Blue alarm

3 (yellow) Remote alarm or out of sync

(yellow alarm)

4 (red) Loss of signal (red alarm)

11. Pull out the mains plug of the

OpenCom 120 again and close the housing.

12. Reconnect the OpenCom 120 to the power supply.

Configuration

The menu item S

appears in the

Configurator, menu PBX Configura-

tion: Ports after installation of the

module. Configure the port in the input mask of this menu item.

Further information on this can be found in the online help.

If the menu item S

is not displayed,

check whether or not the firmware has to be updated. You need software release 3.0 or higher. The current firmware version is given in the menu

System Info: Versions.

Connector Module

Mounting the OpenCom 110/

120 Rack InfoCom System

Safety Precautions

The system needs to be mounted in earthed cabinets or cases. Lines and cables connected to the system must only be laid inside buildings.

Use a shielded Ethernet cable (STP cable, Shielded Twisted Pair cable) to connect the OpenCom 100 to a Local

Area Network (LAN).

The ambient temperature of the

OpenCom 110/120 Rack infocom system should not exceed 55°C. If the device is installed together with other active components, it may be necessary to mount additional ventilation fans in the installation cabinet.

Patch cables have to be connected before connecting the system to the power supply. Installation of the system, and in particular connection to the power supply and protective earthing, should only be performed by skilled, qualified personnel. EN,

IEC regulations, along with other recognised technical rules regarding safety, must be observed.

Please note: Before opening the

device, pull out the plug.

Technical Data

(only if different from the

OpenCom 110/120)

Dimensions:

– Width: 19-inch panel with flange for mounting in installation cabinet

–Height: 3U

– Depth: approx. 340 mm

Weight:

approx. 5.2 kg

Connection of 230 VAC power supply on rear side via inlet connector for non-heating apparatus

Connection of all ports via RJ 45 jacks on front panel

Note: The ISDN S

ports on the front panel may only be switched in one direction (internal or external).

Use of the external port with a crossover (Rx-Tx) patch cable in parallel to the S

internal port (for two S

terminals on the same bus) may severely limit the range of the S

bus.

Mounting the OpenCom 110/120 Rack InfoCom System

Pinning of RJ 45 Jacks

U pn

, a/b, Sensor,

Actor

10Base-T

PIN 4-5

PIN 4-5, 3-6

PIN 4-5, 1-2

PIN 1-2, 3-6

Switches on Front Panel

■

The bus termination resistors for all the S

internal ports are switchable.

Please note: In the factory set-

ting on delivery, the switches are open, i.e. the termination resistors are not switched on.

■

The internal S

bus is terminated at one end (NT) by the

OpenCom 110/120 Rack with

100

Ω termination resistors; the

DIP switches below the respective RJ jacks are “on” (i.e. closed) in the upper position.

Please note: Both S

bus switches must be in the same position.

■

The S

bus is terminated at both ends with 100

Ω termination resistors; the DIP switches below the respective RJ jacks are “off”

(i.e. open) in the lower position.

■

The DIP switches on a/b port 1 are normally “on” (i.e. closed) in the upper position. If the device is set for the entrance intercom port, the switches must be in the lower position (“off”).

Scope of Delivery

■

Adapter cable RJ 45 - RS 232 for

V.24/COM interface

■

Screws for rack mounting

■

For complete installation the country-specific installation package is necessary. It contains the power cord, a complete set of manuals and a CD-ROM.

Note: Note for the DeTeWe in-

staller: Please download and install the latest released software from our

Web site/partnership area.

Mounting the OpenCom 110/120 Rack InfoCom System

Configuration

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

OpenCom 100.

The OpenCom 105 Web console

Using the Web console, you can:

■ perform the initial configuration of the OpenCom 100,

■ configure users of the

OpenCom 100 and authorise them to use certain system services,

■ carry out further system maintenance,

■ use PC-supported telephony functions,

■ read out call charge information,

■ access the OpenCom 100 telephone book.

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

OpenCom 100 (see Loading the On-

line Help starting on page 56).

Note: In order to use all the new

system software functions, we recommend that you download the latest software from our Web site at http://www.detewe.com.

For the initial configuration you can connect the PC to the OpenCom 100

Configuration

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

OpenCom 100 and call up the Con-

figurator from there.

Note: This chapter describes initial

configuration of the OpenCom 100.

For day-to-day operation you can integrate the OpenCom 100 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 62.

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 connected 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 configuration of the network card via DHCP, you must reactivate this and again restart the computer.

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 100 starting on page 54.

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 “occonfig” program from the system CD. To do this, you must log on as an administrator under

Windows NT or Windows 2000/

XP.

2. Shut down the PC. Remove all connected network leads. Connect the serial port of the PC to the COM port of the

OpenCom 100. Use the connecting cable that is supplied.

3. Restart the PC. Set up an RAS link with the icon configured on the desktop under step 1. Enter

“Administrator” without a password 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 100 starting on page 54.

System Requirements

Note: If no connection can be es-

tablished by following the instruc-

tions in the Brief Guide to Initial Configuration starting on page 46, refer

to the more detailed explanations below.

A normal TCP/IP-capable PC with a

Web browser is required for the initial configuration. The PC should at least meet the following requirements:

■

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 operating system

■

Microsoft Internet Explorer version 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 system CD delivered with the OpenCom 100.

In addition, the selected type of connection requires further system components that you may have to install on your PC. The driver software is normally supplied with the hardware, and the appropriate version should be available for your operating system. You will find the system 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). For configuration of the OpenCom 105, use the adapter cable supplied for connecting RS-232 to RJ-45.

■

System software: serial port driver and TCP/IP protocol software

■

Driver software: RAS adapter software for installation on the

Configuration System Requirements

service PC (is included on the

CD)

For connection by network card you need:

■

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

For connection on an S

port you need:

■

Hardware: (passive) ISDN card

■

Software: ISDN card driver, RAS adapter software and TCP/IP protocol software.

Configuration under Windows

Before beginning initial configuration, install the necessary hardware and matching driver software on the

PC. Follow the installation instructions supplied with the hardware. In many cases, the TCP/IP system software 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 connection 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 51

1. Open “Network Settings” in the

Control Panel of your PC. To do this, you select the item “Settings > Control Panel” from the

Start menu and double-click on the “Network” icon. Under Windows NT, select the “Protocols” tab.

2. Check the list of installed components to see whether the TCP/

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

3. Select “TCP/IP” from the “Protocol/Microsoft” folder and confirm your entry with “OK”.

4. Then follow the installation instructions displayed.

Depending on the type of connection (network card, S

port or V.24) you select, note the following when installing the driver and system software.

Configuration under Windows Configuration

Connection on Serial Port

(V.24)

The required components are normally ready installed together with the operating system. In this case, you can easily configure the connection to the OpenCom 100 by using the program “occonfig”:

Note: Under Windows NT or Win-

dows 2000/XP you must log on as an administrator.

1. Insert the system CD supplied along with the OpenCom 100.

The CD starts automatically if your PC is configured accordingly. 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, select a serial port and confirm this with “OK”.

After restarting your computer, you will find an icon for the connection to the OpenCom 100 on your desktop.

Note: If this procedure cannot be

completed properly, refer to the sec-

tion entitled Notes on Configuring the

Serial Port on page 50.

Establishing a Remote Data

Transfer Connection

1. Connect the serial port of the PC to the OpenCom 100 COM port.

Use the V.24 serial connector cable supplied with the

OpenCom 100 (for the

OpenCom 105 use the adapter cable for connecting RS-232 to

RJ-45).

2. Double-click on the OpenCom desktop icon created with the

“occonfig” program.

3. In the dialogue which follows, enter the user name and password valid for the OpenCom 100 user account being used. For the initial configuration, log on under the user name “Administrator” without giving a password.

Clear any entries in the “Domain” box and confirm this with

“OK”.

When the connection is established, all necessary IP address parameters will be transmitted by the OpenCom 100 using the

PPP protocol and automatically set for the direct PC link.

4. Once set-up of the connection is confirmed, you can continue

Configuration Configuration under Windows

with Testing the Setup starting on page 52.

Note: It is not possible to operate a

network card and a remote data transfer connection for the same network 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 configured via DHCP, you can instead also disconnect the PC from the LAN and reboot it.

Notes on Configuring the

Serial Port

A serial port is automatically detected when the PC boots and the corresponding system software is installed. The TCP/IP connection to the

OpenCom 100 is established by means of additional system software: 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 following section is only relevant for users of old Windows versions.

Installing the RAS Network under

Windows 95 or Windows 98

1. Open the Control Panel and double-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 double-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” dialogue is displayed. Select the driver “OpenCom Modem” that was created on the first start of the program “occonfig” and confirm this with “OK”.

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

Configuration under Windows Configuration

Note: If you have installed an oper-

ating system update earlier (Service

Pack), install this again after installation of the RAS.

Connection by Network

Card (LAN)

First-time configuration of the

OpenCom 100 is also possible by a network card, providing this is already installed on the PC, of course.

When the driver software for a network card is installed, the necessary system software for the TCP/IP protocol is installed at the same time.

During this process you should activate the automatic assignment of IP addresses by the DHCP protocol.

If the PC has been operating in a network to date, you should activate the automatic assignment of an IP address.

1. To do this, you select “Settings >

Control Panel” in the Start menu. Double-click on the “Network” icon. Under Windows NT select the “Protocols” tab. Under Windows 2000/XP right click on the “LAN Link” icon. Select

“Properties”.

2. Double-click on the item “TCP/IP

Protocol > Network card”. Activate the option “Obtain an IP address from a DHCP server” in the

“Properties” dialogue. Gateway or DNS entries must be deactivated.

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 100 network port.

To do this, use either a crossover twisted-pair network cable or connect the OpenCom 100 via a hub.

Note: For initial configuration, it

may be wise not to connect the

OpenCom 100 to an existing LAN in order to eliminate conflicts with an existing DHCP server.

2. Restart your PC. During the system start, all necessary IP address parameters will be transmitted by OpenCom 100 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 52.

Configuration Configuration under Windows

Connection via the

S

Port

First-time configuration of the

OpenCom 100 is also possible by way of an internal S

port. To do this, remote configuration must first have been enabled by a connected termi-

nal (see the section called Remote

Configuration starting on page 57).

1. Use the ISDN cable to connect a

PC, fitted with an ISDN card, to the internal S

port.

On delivery, the S

ports of the

OpenCom 100 are assigned as follows:

– OpenCom 105: S

3 and S

– OpenCom 110: S

3 to S

– OpenCom 120: S

3 to S

2. Set up an RAS connection to the

OpenCom 100 through the call number “398504”.Enter the user name “Administrator” and the arranged session key as the password.

Testing the Setup

Subsequent to establishment, test the TCP/IP connection between the

OpenCom 100 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 * 1 8 2 on a connected system telephone.

* 1 8 3 will also show you the network mask.

You can test the correct IP configuration under Windows 95 and Windows 98. Select the item “Run” in the Start menu. Enter the command

“winipcfg” in the “Open” box. Confirm this with “OK”. Select the network adapter used for connection to the OpenCom 100. The IP addresses assigned by the OpenCom 100 on establishment 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” produces a list of assigned IP addresses for LAN links.

Starting the Browser

Start the installed Web browser.

When you start the Microsoft Internet Explorer for the first time, the Internet access wizard will automatically appear. Select the option “Use existing account” and confirm this with “OK”.

Configuration under Windows Configuration

If the PC has been operating in a network or used for Internet access, it is possible that access may be configured indirect via a proxy server. Deactivate access via a proxy server

(“Direct connection”). To do this in the Internet Explorer, open the Internet options in the menu “Tools > Internet Options”, then select the

“Connections” tab. In Netscape Communicator, 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 default settings specified on initial installation of the browser.

Configuration for Linux and MacOS

All modern operating systems support the TCP/IP protocol. You can find detailed information on setting up hardware and software for the

Windows operating systems under

Configuration under Windows starting on page 48. In this section there

are tips on integrating Linux and

MacOS operating systems.

“dhclient” package and activate configuration via DHCP in the Linux network configuration. To access the

OpenCom 100 Configurator, you should also install Netscape Communicator 4.5 (or higher).

Linux

The Linux network configuration is usually performed by the set-up program 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 instructions on TCP/IP configuration.

For the OpenCom 100 to configure the TCP/IP settings of a Linux system via DHCP, you must also install the

MacOS

The TCP/IP protocol is already integrated in the new MacOS starting with version 7.6. For the

OpenCom 100 to configure the TCP/

IP settings of a MacOS system via

DHCP, you must set the configuration method to “DHCP Server” in the menu “Control Panels TCP/IP”.

To access the OpenCom 100 Config-

urator, you should also install Netscape Communicator 4.5 (or higher) or Microsoft Internet Explorer 4.5 (or higher).

Configuration Configuration for Linux and MacOS

Configuring the OpenCom 100

Preparing the

Configuration

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

■

An overview of the ports

■

A list of the terminals to be connected

■

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

■

A list of the users to be set up

(staff entitled to use the services of the OpenCom 100) with their names, departments, and the internal call numbers you want to allocate to them

■

For Internet access: the Internet service provider access data.

Data not available for first-time configuration can be updated or corrected at a later date.

Note: Use the Configuration Guide

starting on page 111. This will assist

you in making the settings in the correct sequence.

Starting the Web Console

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

If the configuration PC gets its IP address automatically from the

OpenCom 100 or if the

OpenCom 100 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 100 Web console is started. First set the country in which you are operating the

OpenCom 100, and in which language the Web console is to be displayed.

Configuring the OpenCom 100 Configuration

OpenCom 105: 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 configuration, leave this box blank.

4. Confirm this by clicking on OK.

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

Configuration Configuring the OpenCom 100

OpenCom 105: dialogue box for initial access

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

6. Confirm your input with Apply.

7. Click on the Configurator button 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 languagespecific ZIP files in the OLH directory of the set-up CD. Confirm your choice by clicking on Open.

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

Configuring the OpenCom 100 Configuration

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 from http://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 59).

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

Preconfiguration

Configuration of the OpenCom 100 can be prepared at your DeTeWe

Customer Service Centre or by an authorised DeTeWe dealer. For this purpose, a OpenCom 100 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 100 at the customer’s site by a service technician.

This prepared configuration must be completed at the customer’s site

(LAN configuration and DECT terminals).

For configuration of the

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

Remote Configuration

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

OpenCom 100 for the customer service centre/authorised dealer.

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 configuration access is then activated when a data call from one of the entered

MSNs is registered.

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

OpenCom 100 as an administrator:

■

User name: “Administrator”

■

Password: administrator password

Note: If you do not wish to let the

customer service centre/authorised dealer know the administrator password, you can define a temporary password for remote configuration with at least five digits.

Configuration Configuring the OpenCom 100

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

Remote configuration on (log-on with administrator password)

H * 1 9 *

Z (system PIN) #

Remote configuration on (log-on with temporary password)

H * 1 9 * Z (system PIN)

* Z (temporary password) #

Remote configuration off

H # 1 9 #

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

Note: During remote configura-

tion, the OpenCom 100 is blocked for

RAS access by any further users.

Please note: The system PIN is

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

Using remote configuration, all

OpenCom 100 settings with the exception of the system PIN can be edited or updated. New software versions of the OpenCom 100 and the software for the connected system terminals and base stations can also be installed (see the SYS Configura-

tion: Firmware menu in the Config-

urator).

For security reasons, settings in the

Configurator, Net Configuration should only be edited on site to avoid malfunctions or failures in the customer’s LAN (e.g. due to IP address conflicts). Refer to the chapter

entitled Configuration Examples starting on page 62, where interac-

tion between the OpenCom 100 and a LAN is explained.

Codes for IP

Configuration

The IP configuration of the

OpenCom 100 is performed on the

Web console in the Configurator, in the NET Configuration: Easy Access menu.

In the event that the IP configuration of the OpenCom 100 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 100 system PIN. The factory setting is “0000”.

Configuring the OpenCom 100 Configuration

Set IP address

H * 1 8 2 Z (system PIN)

* Z (www) * Z (xxx) *

Z (yyy) * Z (zzz) #

Set NET mask

H * 1 8 3 Z (system PIN)

* Z (www) * Z (xxx) *

Z (yyy) * Z (zzz) #

Restart

H * 1 8 5

Z (system PIN) #

Saving and Loading the

Configuration

Configurations are saved in a file archive and can be loaded to the

OpenCom 100 either locally from a connected configuration PC, or by remote configuration.

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

■

Telephony and network parameters

■

User data

■

Telephone book entries

■

LCR tables

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

backup.

Loading SW Updates

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

New software versions of the

OpenCom 100 are loaded from the configuration PC, which accesses the

Configurator (see the SYS Configu-

ration: Firmware menu). For information on connecting a configura-

tion PC, see Brief Guide to Initial

Configuration on page 46.

The terminal software is part of the

OpenCom 100 software and is automatically loaded into the terminals via the OpenCom 100 if the software version in the terminal is different from the terminal software stored in the OpenCom 100.

Note: If you are operating an PBX

cascade, new system software is automatically transferred to the slave system from the master system.

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

Firmware.

Configuration Configuring the OpenCom 100

Resetting the System

Data

You can restore the factory settings of the OpenCom 100 in the Configurator. Should this not be possible, re-

fer to the next section entitled Hard-

ware Basic Settings Switch.

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 59

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.

Hardware Basic Settings

Switch

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

Please note: If this is done, all

customer settings and user data will then be lost.

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

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

2. Remove the cover.

3. Press the basic settings switch.

– OpenCom 105: The basic settings switch is a key switch. You press the basic settings switch by inserting a pointed object in the opening on the cover. Hold the switch down.

– OpenCom 110/120: The basic settings switch is a hook switch.

Close the switch.

You can see the positions of the respective switches in the dia-

gram entitled Positions of the

Ports on page 22.

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

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

6. Open the key switch.

Configuring the OpenCom 100 Configuration

– OpenCom 105: Release the basic settings switch.

– OpenCom 110/120: Open the hook switch.

The system data is now reset.

7. Replace the power plug in the mains socket.

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

8. Log on to the Web console (see

Starting the Web Console on page 54). Configure the

OpenCom 100 (possibly by loading a saved configuration; see

Saving and Loading the Configu-

ration on page 59).

Generating Your Own

MoH Files

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

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

The file format for non-resident Music on Hold is *.wav. You can also save your own MoH in a *.wav file and load it into the OpenCom 100.

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

The MoH file must be coded with

8000 Hz, 8 bit mono in accordance with CCITT, A-Law. This coding is required for the OpenCom 100 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).

Note: If you don't have the Sound

Recorder program or the appropriate codec on your Windows operating system, you should install these components from your Windows CD.

Load your MoH file in the Web console's Configurator, in the SYS 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 100 can be used free of charge.

Configuration Configuring the OpenCom 100

Configuration Examples

OpenCom 100 in Computer Networks

One of the outstanding features of the OpenCom 100 is the integration of telephony and computer networks. Connect the OpenCom 100 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: company telephone book (if the multi-company variant is activated).

In addition, the OpenCom 100 can be used as an Internet access server.

RAS access can also be implemented using the OpenCom 100, which enables the integration of external staff in the LAN.

■ the OpenCom 100 Configurator

■ call charge administration

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

In this chapter you will find several examples of configurations showing integration of the OpenCom 100 in a

LAN. Which example applies to your situation depends on the size and properties of the existing or planned

LAN infrastructure.

■ the OpenCom 100 central telephone book and your personal telephone book as well as to the

The following LAN prerequisites are possible:

Server configuration in the LAN OpenCom 100 Functions

No IP server present OpenCom 100 functions automatically as DHCP and

DNS server

IP server present

DHCP server present

OpenCom 100 functions automatically as DHCP client

System Administrator must assign IP address and

DNS name for OpenCom 100

IP server present

No DHCP server present

Special case when integrating the OpenCom 100 in a LAN; settings in the

“NET Configuration: Easy

Access” menu

must be coordinated with the responsible system administrator

OpenCom 100 in Computer Networks Configuration Examples

Introduction to TCP/IP

In a single LAN it is possible to use various protocols for the transmission of data. The connection between a workstation computer and the OpenCom 100 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 network.

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 networks normally use IP addresses in which the first three numbers are the same and the last number is uniquely assigned to a specific device in the LAN. On the Internet, unique addresses assigned by a special organisation created for this purpose are used. Within a LAN, you can use addresses which are not unique world-wide.

network mask, the connection is established via the default gateway. If a device knows several data routes to different intermediate stations, one speaks of a router.

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

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

Note: For further explanations of

technical terms, refer to the Glossary on the CD-ROM supplied.

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

255.255.255.0. If the IP address of the partner device does not fit the

Configuration Examples Introduction to TCP/IP

OpenCom 100 in a Serverless LAN

In a peer-to-peer network, the workstations are connected to one another via network cables. In many networks, the cables run in the form of a star from a central hub. 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).

ISP

(DNS)

Ext.

OpenCom

(DHCP, RAS, int. DNS, Internet)

Net

PC 1 PC 2

Net Hub Net

The OpenCom 100 in a serverless LAN

192.168.99.254

192.168.99.129 to 192.168.99.148

192.168.100.0 to 192.168.100.10

255.255.255.0

192.168.99.254

In a serverless LAN, the

OpenCom 100 takes over the IP configuration of the connected workstations. All TCP/IP settings necessary for the workstations are assigned by the OpenCom 100 via DHCP (dynamic host configuration protocol).

In this operating mode, an IP address space reserved for such networks is used:

OpenCom 100 IP address

DHCP addresses: IP address space for workstations

PPP addresses: IP address space for RAS dialling

Network mask (class C network)

DNS server IP address

Default gateway IP address

OpenCom 100 in a Serverless LAN Configuration Examples

Install the TCP/IP network protocol and a Web browser for every workstation which is to have access to the

OpenCom 100 network features.

For notes on installing network

cards, refer to Connection by Network

Card (LAN) on page 51.

DNS Name Resolution

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

OpenCom 100. If you type the string

“host.domain” into your browser, a

DNS request is sent to the

OpenCom 100 IP address. The

OpenCom 100 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 workstations by the OpenCom 100. The

OpenCom 100 is not visible in the network environment.

Internet Access

If access to an ISP has been configured on the OpenCom 100, the

OpenCom 100 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 100 is configured as a DNS server and default gateway. The workstation therefore sends its Internet connection request to the

OpenCom 100.

In almost all cases, the request will contain a DNS name which is unknown in the internal network.

When you type a URL into your browser, the OpenCom 100 receives the request to find the corresponding IP address. If the name is unknown in the LAN, the request is forwarded to an ISP’s external DNS server.

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 request which does not lead to the establishment of an Internet connection. For this reason, you should choose a name which is not used in the Internet as the domain name

(“firm-opencom.co.uk” for example).

Configuration Examples OpenCom 100 in a Serverless LAN

RAS Access

You can establish a connection from an external computer with an ISDN card to the OpenCom 100. The necessary TCP/IP settings are transmitted by the OpenCom 100 on establishment 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 environment. NetBIOS can use Net-

BEUI, IPX/SPX or TCP/IP as the transport protocol. In the network environment, you can only access files and printers on workstations using TCP/IP for NetBIOS.

Note: In a serverless LAN, the work-

stations running decide independently which one is to keep the list of names visible in the network environment. 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 100 in a LAN with an IP-enabled Server

In a LAN with an IP-enabled server, you should coordinate integration of the OpenCom 100 with the responsible network administrator. You must decide on the IP address space to be used and which network services

(DHCP, DNS, RAS, Internet access) the OpenCom 100 is to handle in the

LAN.

ISP

(DNS)

Ext.

OpenCom

Net S

int

Server

(DHCP, RAS, int. DNS,

Internet)

Net

PC 1 PC 2

Net Hub Net

The OpenCom 100 in a LAN with an

IP-enabled server

In many cases, an IP-enabled server configures the TCP/IP settings via

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

DHCP for all workstations. On starting, the OpenCom 100 requests TCP/

IP settings via DHCP. If this request is responded to, the OpenCom 100 uses the TCP/IP settings received.

You can then use a workstation to access the OpenCom 100 Configura-

tor under the IP address assigned by the server.

In networks in which the TCP/IP settings are made manually, you have to enter the corresponding TCP/IP settings in the OpenCom 100 Con-

figurator (NET Configuration: Easy

Access menu). Here the

OpenCom 100 acts as the DHCP server. A workstation requesting the

TCP/IP settings via DHCP then receives 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 100. For further information, refer to the server documentation.

Note: To access the OpenCom 100

under the same IP address after a restart, you must specify this IP address permanently on a DHCP server. On a

DHCP server it is possible to link the

MAC address of a network card with a specific IP address. You will find details in the server documentation.

Internet Access

You can also use the OpenCom 100 as an Internet access server in a LAN with an IP-enabled server. To do this, you must enter the OpenCom 100 IP address on the server as the default gateway. In addition, you must edit the internal DNS server configuration so that the resolution of external DNS names is forwarded to the

OpenCom 100.

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

OpenCom 100.

There are two different ways of suitably configuring the internal DNS server. You can enter the

OpenCom 100 IP address as a DNS forwarder. If you require access to extended DNS information, you can also configure the DNS server for a recursive DNS request without the

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

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

ISP

(DNS)

OpenCom

(Internet)

Net S

int

Server

(DHCP, RAS, int. DNS)

Net

Ext.

PC 1 PC 2

Net Hub Net

The OpenCom 100 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 computers to dial in via the

OpenCom 100. To do this, you should coordinate with the network administrator the IP address space which can be assigned to an external computer dialling in, and enter it in the

Configurator, NET Configuration:

Easy Access menu, under PPP Ad-

dresses.

The user account administered by the OpenCom 100, with which dialling in is permitted, only allows the establishment of direct and anonymous TCP/IP connections such as

HTTP, FTP or SMTP connections. If you additionally want to allow file or printer access in the network, you must set up a suitable user account on the addressed server for network log-in. If you use the same log-in name for the OpenCom 100 user account and the same password for the network log-in, you have to enter this combination only once when dialling in.

ISP

(DNS)

OpenCom

(RAS, Internet)

Net

Server

(DHCP, int. DNS)

Net

Ext.

PC 1 PC 2

Net Hub Net

RAS access by the OpenCom 100 in a

LAN with an IP server

Note: In a larger Windows network

with several segments, the lists of computer names visible in the network environment can no longer be established by broadcasts. In this case you use a special WINS server whose address the OpenCom 100 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 100 in a LAN with an IP-enabled Server Configuration Examples

LAN-to-LAN Link

You can use the OpenCom 100 to interlink two LANs via ISDN. To do this, you configure two OpenCom 100 systems so that they can dial in to each other. In order for this to work, the two LANs must be configured for

OpenCom

(IP=192.168.99.254,

Net=192.168.99.0)

Net S

0 different IP address ranges (subnetworks). For at least one of the

OpenCom 100 systems, change the prescribed address range for the

LAN.

OpenCom

(IP=192.168.11.254,

Net=192.168.11.0)

Net

PC 1 PC 2 PC 1 PC 2

Net Hub Net

The OpenCom 100 in a LAN-to-LAN link

In the Configurator, NET Configura-

tion: LAN-LAN menu you can configure the dial-in settings. The

OpenCom 100 will set up a connection 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 Windows network, you need an IP-enabled server that administers the name resolution for the Windows network.

Net Hub Net

As the IP address range, you can select one of the 256 class C subnetworks designed for local LANs.

Select a class C sub-network in the range from 192.168.0.0 to

192.168.255.0.

Configuration Examples LAN-to-LAN Link

Useful Information on Internet Access

Costs

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

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

Examples of such programs are the

Microsoft

operating system, various multimedia programs such as Realplayer

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

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

(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 100 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 standalone PC via an online service differs from Internet access via the

OpenCom 100 in the following respects:

■

When you request a Web page, dialling in results automatically.

There is no display of dialogues with manual confirmation of dialling in or hanging up.

■

Requesting Web pages is not a connection-orientated service.

When the Web page has been loaded completely, the TCP/IP connection is cleared. If you do not request further Web pages, the OpenCom 100 automatically releases the connection to the

Internet after a certain, specifiable duration.

■

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

■

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

Useful Information on Internet Access Configuration Examples

E-mail

One of the most important services in the Internet is e-mail. E-mails are buffered in individual e-mail accounts on a mail server. Mail servers are operated by ISPs for example.

With the OpenCom 100 you can set up one or more e-mail accounts for every user account configured on the OpenCom 100. These e-mail accounts are then checked at regular intervals.

If there are new e-mails in an e-mail account, and the OpenCom 100 has been configured for this function, the user specified in the

OpenCom 100 user account is notified of the new e-mail on his system terminal. System telephones from the OpenPhone 6x and 2x product range 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 order to translate internal IP addresses to valid external IP addresses. This has three important consequences for Internet access:

■

Several workstations can share a single Internet access. You do not require a LAN access, only a single account with the Internet service provider.

■

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

■

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

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

■

TCP/IP addresses are transported in the useful load, e.g.

NetBIOS over TCP/IP.

■

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

Configuration Examples Useful Information on Internet Access

■

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

ICMP or IGMP.

The OpenCom 100 NAT has suitable processes for ensuring the functions of many important protocols affected 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-directed connection establishment can be configured in the Net Config-

uration: Port Access menu. For further information, refer to the online help of this menu.

Useful Information on Internet Access Configuration Examples

PBX Networking

As requirements grow, the

OpenCom 100 can be operated together with other PBX installations.

If you merely need a larger number of connections, it is easy to link a

second PBX (“PBX Cascading”). If you

want to operate the OpenCom 100 at several locations with different

PBXs, this is possible by PBX Net-

working.

PBX Cascading

You can combine two PBXs in order to increase the number of terminals that can be connected. A master PBX and a slave PBX are connected to one another by means of two cables.

The two PBXs essentially function

Master PBX

OpenCom 120 like a single PBX with a higher number of ports. The master PBX controls the slave PBX. The following

PBXs from the product family can be used for cascading:

Slave PBX

OpenCom 105, OpenCom 110,

OpenCom 120

Note: The OpenCom 107 is not

equipped with a PCM port. For this reason, PBX cascading is not possible with this PBX.

For the PBX Cascading you will need a license. The license agreement provides you with the necessary steps to activate this function

Functionality of PBX

Cascading

PBX cascading requires two twistedpair leads with RJ45 plugs between the PBXs:

■

Voice data: one lead with all eight pins wired 1 to 1. Connect this to the PCM ports of the

PBXs. The shielded CAT-5 lead may be up to three meters long.

■

Administration data: one CAT-5

Ethernet lead. You connect this

PBX Networking PBX Cascading

to the LAN2 port of the master system (host system) and to the

LAN1 port of the slave system

(add-on system).

PBX 1

(Master)

PBX 2

(Slave)

PCM LAN 2 LAN 1 PCM

CAT-5 Ethernet lead

Voice data lead (eight pins assigned, joined 1 to 1)

Cascaded PBX system

Putting a Cascaded PBX into Operation

Proceed as follows to put a cascaded

PBX system into operation:

1. Take the additional slave system out of its packaging and place it in immediate proximity to the master system. Connect a system telephone to the slave system for a later performance check. Use the U pn

1 press-fit terminal.

Please note: If you wish to use

an older PBX as the slave system, you must first load system software for it

(version 3.0 or higher).

2. Back up the master system data.

For further information, refer to the online help topic SYS Con-

figuration: Data Backup.

3. Switch off the master system if it is operating. Disconnect the module from the power supply by pulling out the mains plug.

4. Connect the two modules by means of two suitable cables as described above.

5. Power on the two PBXs. The order in which you do this does not matter.

6. Select the Type of slave system with the Configurator of the master system in the

SYS Configuration: System:

Slave dialogue box. Enter the

Ethernet card address of the slave system in the MAC address input field.

If a possible slave system was detected when the system was started, there is an additional entry in the Type field (“Online:

PBX type”). If you select this entry, the settings for Type and

MAC address are applied automatically.

Note: There are two versions of the

OpenCom 105. If you select the ap-

propriate entry under Type, the corre-

sponding module version will be dis-

played under PBX Configuration:

Ports.

Please note: If you change the

type of slave system later on, the port settings that have been made will be deleted.

PBX Cascading PBX Networking

The master system then initialises the slave system. This may involve transfer of firmware (operating software) from the master system to the slave system.

This can take a few minutes.

7. Configure the system telephone connected to the slave system for testing purposes in the Con-

figurator. In the

PBX Configuration: Ports: Upn dialogue, click on one of the additionally displayed entries of the type Upn 1/n (1: slave system, n: U pn

port number).

Note: Changes to the configura-

tion while initialising the slave system may trigger error reports referring to the ongoing initialisation.

You can see that the initialisation has been completed from the display on the system telephone connected to the slave system.

Notes

Observe the following when operating a cascaded PBX system:

■

All U pn

, S

and a/b ports of the slave system can be used with appropriate telephones. All features of system telephones on

U pn

ports are available without restriction.

■

The S

ports of the slave system can also be used for trunk lines

or for PBX networking (see PBX

Networking starting on page 76).

■

It is not possible to operate a

DECT base station on one of the

U pn

ports of the slave system.

■

The COM, actor/sensor and –if present– LAN2 ports of the slave system cannot be used.

■

The two communications systems must have a direct Ethernet connection or be connected via a hub in order to exchange data. They cannot be connected through a router.

■

The slave system cannot be addressed directly through a LAN.

For configuration, always use the Web console of the master system.

■

A memory card installed in the slave system (OpenVoice, Open-

Attendant) cannot be used.

■

To operate the slave system again normally, you must reset it to its factory settings (refer to

Resetting the System Data starting on page 60).

PBX Networking PBX Cascading

PBX Networking

In Release 3 of the system software,

OpenCom 100 provides all the features necessary for PBX networking.

You need PBX networking in the following cases:

■

To operate the OpenCom 100 as a subsidiary system on another

PBX. This will also allow you to use the OpenCom 100 as a DECT server, for example.

■

To network the OpenCom 100 with an OpenCom 1000. In this way you can use the

OpenCom 100 as a PBX for a branch office, for instance.

■

To network several

OpenCom 100s into a PBX system.

■

To use flexible configuration possibilities of trunk lines for a

OpenCom 100.

All settings that affect the configuration of PBX networking can be found in the Configurator menu

PBX Configuration: Trunks and in the PBX Configuration: System:

Settings dialogue under System

linking. Refer also refer to the corresponding help topics in the

OpenCom 100 online help.

Note: If you do not need the fea-

tures of PBX networking, the simplified configuration is sufficient in most cases. For this purpose, assign the

preconfigured trunk groups Multi-

terminal access or System access to

the ports. The preconfigured route

called External trunk now makes it

possible to seize an external line immediately or by first dialling the prefix “0”. You can rename the preconfigured bundle and the preconfigured route if required, but you cannot delete them.

Connections

Networking two or more PBXs means interconnecting them. The

OpenCom 100 allows you to use both trunk lines and point-to-point connections on external S

ports or on the S

port.

PBX PBX PBX PBX

PBX

Example of a PBX network

Trunk line

Point-to-point connection

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

PBX Networking PBX Networking

Protocol: Q.SIG or DSS1

The Q.SIG protocol, designed for

ISDN point-to-point connections, is the preferable choice as the transmission protocol; alternatively, the

DSS1 protocol, designed for ISDN dial-up connections in the Euro-

ISDN, can be used. Certain PBX networking features can only be used with the Q.SIG protocol, however. In particular, the identifier indicating whether a call is internal or external cannot be transmitted using DSS1.

Both protocols implement communication on several protocol layers:

■

L1: Layer 1 defines the physical line properties and the electrical coding of signals.

■

L2: Layer 2 enables communication via individual error-protected channels that are independent of each other.

■

L3: Layer 3 defines the administration of the individual channels and implements the features designed for ISDN.

Master/Slave

For an ISDN connection, it is possible to determine which PBX is the protocol master and which the protocol slave. This relationship can be determined for all three protocol layers independently of one another.

For each protocol layer, the PBX at the other end always has to be suitably configured. If one PBX is the protocol master for a layer, the other

PBX must be the protocol slave for this same layer. Normally all three protocol layers are configured identically. In the case of a trunk line, the network operator is the protocol master for all three layers.

Note: In the case of an S

line, it is also possible to determine for each useful channel which end can administer a channel (master = internally seized or slave = externally seized).

On S

lines this setting is determined by “L3 master” for both B-channels.

L1 Clock

To enable PBXs in the ISDN network to communicate with each other, they must be “clock-aligned”. The L1 protocol master sets the clock for layer 1, and the L1 protocol slave adopts (synchronises to) this clock.

When planning a PBX networking scheme, you must make sure that the L1 clock propagates from a master via a number of PBXs.

Network operator

M S

PBX1

PBX 3

PBX 2

Trunk line

Point-to-point connection

Example: propagation of the L1 clock

If more than one port with the setting L1 Type = “Slave” is configured on an OpenCom 100 and the setting

PBX Networking PBX Networking

L1 sync possible has been activated, then one of the ports is automatically defined as the L1 clock source.

The OpenCom 100 will automatically switch the clock source to another port configured as an L1 clock source

(if a line fails, for example).

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

When applying the L1 clock of trunk lines, you can assume that the public network is “clock-aligned”. So, in the above example, you can connect additional trunk lines to one of the

PBXs.

Types of Point-to-Point

Connection

There are different types of connection available for an ISDN point-topoint connection between two PBXs, depending on the distance between them.

Direct Connection

This type of point-to-point connection joins the two systems directly to each other using a crossover twisted-pair cable. An S

connection can be used for distances up to 1,000 metres, while an S

connection can span up to 250 meters. Normally one

PBX is the protocol master for all three layers, and the other PBX is the protocol slave for all three layers.

PBX 1

L1 master

L2 master

L3 master

Direct connection

PBX 2

L1 slave

L2 slave

L3 slave

■

Use the RJ45 jacks on one of the external S

ports for an S

connection between two

OpenCom 100s.

■

Use the pressure terminal of the

port for an S

connection between two OpenCom 120 systems.

PBX 1, S

ext

1 2 3 4 5 6 7 8

PBX 1, S

Rx+ Rx- Tx+ Tx-

8 7 6 5 4 3 2 1

PBX 2, S

ext

(RJ-45 socket)

Rx+ Rx- Tx+ Tx-

PBX 2, S

(Pressure clamps)

Wiring of a direct connection

PBX Networking PBX Networking

Connection via an Active

Transmission System

For distances exceeding the range of a direct connection, an active transmission system can increase the range to up to 50 km. Normally the

L1 master is the transmission system for the two connected PBXs. For the protocol layers L2 and L3, one PBX is normally the protocol master and the other PBX is the protocol slave.

PBX 1

L1 slave

L2 master

L3 master

Transmission

System

L1 master

PBX 2

L1 slave

L2 slave

L3 slave

Connection by an active transmission system

Note: The active transmission 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 operator can be used for bridging distances beyond 50 km. Due to the long distance involved, for technical reasons it is not possible to synchronise the L2 protocol. Consequently, the public network is normally the protocol master for protocol layers

L1 and L2. One PBX is therefore the

L3 master and the other PBX the L3 slave.

PBX 1

L1 slave

L2 slave

L3 master

Public network

L1 master

L2 master

PBX 2

L1 slave

L2 slave

L3 slave

Point-to-point connection via a public network

Configuration

The possible configurations described 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.

Network operator

PBX 1 PBX 3

A E

PBX 2

Bundle

Trunk line

Point-to-point connection

Example of a PBX network with trunk groups

In the above example, the following trunk groups are configured for

PBX 1:

■

Two S

lines in a multi-terminal configuration to the network operator which are assigned to the “A” trunk group.

■

Two S

point-to-point connections to PBX 2 which are assigned to the “C” trunk group.

PBX Networking PBX Networking

■

One S

point-to-point connection 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 performed indirectly via a route.

Routes

A route is a group of trunk groups enabling a connection in one direction. If the first trunk group of a route is fully utilized, the next trunk group is seized (“trunk group overflow”). One trunk group can also be used for different routes.

In the above example, a route set up for PBX 1 allows a connection to

PBX 2. Trunk groups “C,” “E” and “A” are assigned to this route. If a user connected to PBX 1 wants to reach a party in PBX 2, lines will be seized in the following order:

■

PBX 1 first searches for a free channel in the “C” trunk group.

■

If all the lines in trunk group “C” are busy, the system tries to set up a connection via trunk group

“E”. PBX 3 switches the connection through, provided it is appropriately configured (refer to

Numbering starting on page 80).

■

If it was not possible to set up an indirect connection via PBX 3, the system tries again via trunk group “A”. The “prefix” necessary for this can be configured with the route.

■

The user does not get a busy signal until the attempt to set up an indirect connection via the network operator has also failed.

Note: If an internal connection is

switched via a network operator, the call is signalled using the external number of the calling PBX.

For each route you can define a randomly selectable code digit for seizing the route. You can also configure whether a user is authorised to seize a particular route, whether LCR is to be used for one of the trunk groups and the criteria (business or private call, booking numbers) for evaluating call data.

Numbering

A user can seize a particular route by pre-dialling a specific code digit.

With this “open numbering”, a user must always dial this code digit and then the telephone number in order to reach a party in another PBX.

If none of the telephone numbers in your PBX network occur twice, you can also configure “closed numbering”, allowing the same telephone number to be used for reaching each user within the PBX network.

With closed numbering, the

OpenCom 100 determines which route to seize from the telephone

PBX Networking PBX Networking

number dialled. The information needed for routing a call can be configured in a numbering table containing up to 100 entries. You use this table to assign telephone numbers and/or ranges of telephone numbers to a particular route.

A default entry in the numbering table makes it possible to seize a “default route” for all remaining unassigned numbers. In particular, this simplifies configuration of the

OpenCom 100 as a subsidiary system: the only entry you assign to the

default entry is the route to the host system

PBX

100-199 c d a b

PBX

400-499

4: b

D: c

D: a

PBX

200-299 e g h

3: e

5: h

D: d f

PBX

500-599 i

PBX

300-399 k

3: i

D: g

5: k

D: f

D:Default

Route

Example of closed numbering tables

The automatic switching of call requests (i.e. routing) by means of trunk group overflow or default numbering can lead to “circular switching”.

To avoid this, a “transit” counter is incremented whenever a connection is switched through on Q.SIG lines.

When the configured maximum value is reached, further switching stops.

Technical Details

A different PBX number must be set for each OpenCom 100 in a PBX network. 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 depends on the topology of the PBX network and should allow the system to have the maximum number of further connections possible.

You can display the connection status of the lines at any time in the

Configurator menu System info:

PBX: Trunks. You should check this in particular after making changes to a configuration to see whether all the lines used for system networking are operable.

Some of the features possible in

Q.SIG are not supported by

OpenCom 100 with all their options, for example callback on busy within the Q.SIG network. The call categories defined in Q.SIG (e.g. Emergency

Call, Operator, Normal) and the Q.SIG name transmission feature (“user names”) are fully supported.

The code digits to be used for seizing a route with open numbering are not transmitted to the destination

PBX and thus cannot be evaluated by it. To reseize a route (for example for a callback), you must set the appropriate digit prefixes in the trunk

PBX Networking PBX Networking

group configuration for the routes to be reseized.

Tip: If, for example, you are configuring a route which can be seized using routing code “5” and have selected one or more bundles for this route, change the Prefix for dest.

call number at incoming internal setting to “5” for this bundle in order to enable the route to be reseized.

OpenCom 105

OpenCom 110

OpenCom 120

M/S

Owing to their hardware properties, not all S

ports of the OpenCom 100 can be used for PBX networking without restrictions. Depending on the type of system, some ports can only operate in the L1 master mode or L1 slave mode. The external S

0 and S

ports can be set according to the following table.

M/S

–

M/S

–

M/S

–

M/S

Legend

S = Slave

M/S = Master/Slave

M = Master

PBX Networking PBX Networking

Licensing Information

A licence is required for certain additional OpenCom 100 program packages, for example for the internal voice-mail system called OpenVoice.

The following information is for customers who have already obtained licences for an OpenCom 100 and would like to cascade or network their existing system with another

OpenCom 100.

In this case, new activation keys for the use of additional program packages must be generated on the

DeTeWe licence server

(http://lizenz.detewe.de).

The licensing confirmation for the cascading contains all the information you need to carry out this procedure.

PBX Networking

If you network two OpenCom 100 systems with each other, you needn't generate any new activation keys but can continue to use the corresponding functions on the existing

OpenCom 100. The “disadvantage” of this alternative is that you have to administer a separate configuration on each OpenCom 100.

Note: You will need the serial num-

bers of both infocom systems for

porting the activation keys. The se-

rial numbers can be found in the

Web console's Configurator, in the

System Info: Versions menu.

PBX Cascading

In the case of PBX cascading, the master system administers the overall configuration. For PBX cascading you need at least one OpenCom 120 as a master system, to which another OpenCom 100 can be connected as an interface expansion.

If you have already installed activation keys on an existing

OpenCom 100, they have to be ported to the master system

(OpenCom 120).

PBX Networking Licensing Information

Team Functions

Introduction

With the team functions you can manage your telephone communication tasks by assigning lines with separate call numbers to the keys of different terminals. The terminal users, or team members, can thus pick up one another’s calls or telephone each other using the configured keys.

Team functions can only be configured on the corded system telephones of the OpenPhone 6x product 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 terminal, different numbers of call keys are available:

Number of available call-keys

Telephone Number of keys

OpenPhone 61 One key with a display, five keys without a display

OpenPhone 63 Three keys with a display, five keys without a display

OpenPhone 65 19 keys with a display: nine on the telephone itself and 10 on an add-on

Note: Only one function or call

number can be programmed for each call key.

The following keys can be used:

■

Trunk key: Calls (for the programmed call number, e.g. 11) are signalled to this key, and you can make internal and external calls via this number. A trunk key can be programmed with a substitute function (with another team member acting as the substitute). Calls for you are then signalled to the terminal of another team member. A trunk key also provides functions for man-

Introduction Team Functions

aging calls. For example, you can configure call protection if you do not want to be disturbed, or call diversion to another telephone.

■

Team key: As with a trunk key, a team key can be used to receive or make calls. However, this key cannot be used to change the settings for managing calls; it is not possible, for example, to configure call diversion to another telephone. Calls made via a team key are signalled to all terminals with a trunk key that has been programmed with the same number. For example, the team key with the number 11 calls all trunk keys with the number 11.

■

Busy key: The purpose of a busy key is to make the busy status of other team members visible. An incoming call for a busy team member is signalled on the other team member's busy key.

That team member can take this call by pressing the busy key, which seizes his own terminal's trunk key. Calls taken via the busy key are not entered in the call list of the team member who was originally called. In addition, it is possible to call the respective team member via his busy key when his terminal is idle. You set up a call to this team member by pressing your own trunk key.

■

Direct call key: Only outgoing calls can be made with a direct call key; they are signalled to all terminals with the same number programmed to a trunk key.

Calls via a direct call key are signalled to the destination terminal even if that terminal has been programmed with a substitution function or call protection. If the destination terminal has been configured for call diversion, the direct call is not diverted.

Which key is suitable for which purpose?

■

Trunk keys can be assigned call numbers for managing central communication tasks, for example, customer support. If the call numbers of the support department are assigned to trunk keys on all of its terminals, then all members of the support department can receive and manage calls and use the substitute function.

■

Team keys, for example, can be used to create a project group within a department. Calls from customers of this group can then be answered by any team member who is not busy. The team members can call each other by the team keys.

■

A busy key can be used to configure an attendant terminal

Team Functions Introduction

showing the status of the individual users. The attendant terminal sees the status of the users and can put calls through by simply pressing the key.

■

Direct call keys, for example, can be configured at a terminal in a conference room in order to call the secretary.

Team Configuration

You can create teams and program call keys in the Configurator of the

OpenCom 100 (PBX Configuration:

Groups and Ports: Upn menu).

Call key 1 is preset as a trunk key on all system telephones. This setting can be changed by the system administrator.

Examples of Use

The following examples illustrate the various uses of teams and team functions.

For information on the display texts and how to use the individual functions, refer to the chapter “Managing Calls in a Team” in the “Open-

Phone 61, 63, 65” user guide.

Executive/Secretary

Team

In this example, the executive/secretary 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.

Secretary

TrK 11: Secretary

TrK 10: Executive

DK 10: Executive

Executive

TrK 10: Executive

TrK 11: Secretary

TrK 12: Private

Executive´s Parallel

TrK 10: Executive

TrK 12: Private

Example: executive/secretary team

Line Seizure

The secretary can be reached on the call number 11 (trunk key TrK 11: secretary’s office).

The executive can be reached on the call number 10 (trunk key TrK 10: executive’s office). He can also answer calls from his parallel telephone. In

Examples of Use Team Functions

addition, a private line is configured for both of the executive’s telephones (trunk key TrK 12: private).

Call numbers 11 and 10 are both configured as a trunk key on the executive’s and the secretary’s terminal respectively. Thus the executive and the secretary can use either call number (for answering as well as making calls). Each can act as a substitute for the other.

The secretary’s terminal also has the executive’s call number configured as a direct call number (DK 10: executive’s office). The secretary can therefore reach the executive and put through calls even if the executive has programmed a substitute.

Line Busy Indication

If a line is busy, e.g. TrK 11 secretary’s office, the other terminal will indicate this. The executive’s private calls via TrK 12 are not indicated on the secretary’s terminal since no appropriate trunk key is configured on the latter’s telephone.

Call Signalling

In this configuration example, calls to one’s own call number are signalled acoustically on the following telephones:

■

Call number 11 on the secretary’s telephone

■

Call numbers 10 and 12 on the executive’s telephone.

Calls for the other team member’s call number are indicated by an optical signal on one’s own telephone

(flashing trunk key LED).

The parallel telephone will indicate calls only by an optical signal.

Time-delayed acoustic signalling can be configured for TrK 10 on the secretary’s telephone. If the executive, for example, does not answer a call within 10 seconds, the secretary’s telephone will start to ring.

If the executive activates a substitute function with the secretary as the substitute, calls for call number

10 will be indicated on the executive’s telephone by an optical signal only, but signalled acoustically on the secretary’s telephone. The secretary can also activate a substitute function. Calls for call number 11 are then signalled acoustically on the executive’s telephone, and indicated by an optical signal on the parallel telephone and the secretary’s telephone.

Three-member Team

The three-member team described here is an example of a team configuration within a project group, e.g. export sales.

Each team member has one Open-

Phone 63 system telephone with all

Team Functions Examples of Use

call keys programmed as trunk and team keys.

Miller

TrK 10: Miller

TK 11: Johnson

TK 12: Smith

Johnson

Trk 11: Johnson

TK 10: Miller

TK 12: Smith

Smith

TrK 12: Smith

TK 10: Miller

TK 11: Johnson

Example: three-member team

Line Seizure

Each team member’s call number, e.g. call number 10 for Miller, is programmed as a trunk key on his telephone.

On the other telephones in the team, this call number is programmed as a team key (e.g. TK 10 on Johnson’s and Smith’s telephones). The team members can thus see which number a call is for and can answer it by pressing the appropriate team key.

The team members can call each other via the team keys. For example, Miller can call number 12 by pressing TK 12; the call is then signalled to Smith’s telephone on

TrK 12.

Line Busy Indication

If a line is busy, e.g. TrK 11 Johnson, the team keys 11 on Miller’s and

Smith’s telephones will indicate this.

Call Signalling

In this example, calls via the trunk keys are signalled acoustically. Calls via the team keys are indicated by a visual signal (the team key LED flashes).

Unified Team

The unified team described here is an example of a team configuration within a department in which calls are to be managed quickly (e.g. support department).

Each team member has one Open-

Phone 63 system telephone with all call keys programmed as trunk keys.

Miller

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

Johnson

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

Smith

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

Example: unified team

Examples of Use Team Functions

Line Seizure

Call numbers 10, 11 and 12 are programmed as trunk keys on each team member’s telephone (TrK 10 to TrK 12.

All team members can use these numbers for answering as well as making calls.

Tip: In this team configuration it is useful to program one of the function keys on each telephone with the

“Hold” function. A call, e.g. for

TrK 11, can then be put on hold by pressing the function key. If another team member then presses trunk key TrK 11 on his telephone, he can accept the call. For further information on function keys, refer to the

“OpenPhone 61, 63, 65” user guide.

Line Busy Indication

If a line is busy, e.g. TrK 11 Johnson, the trunk keys on the other team telephones will indicate this.

Call Signalling

In this example, calls via all trunk keys are signalled acoustically.

Toggle Team

The toggle team described here illustrates how a large number of call numbers can be managed efficiently with the help of team functions.

Each team member has one

OpenPhone 65 with all call keys programmed as trunk and team keys.

Miller 14:22

Mi .

14.Feb

TrK 10: Support 1

TrK 11: Support 2

TrK 12: Support 3

TrK 13: Support 4

TrK 14: Support 5

TrK 15: Hotline 1

TrK 16: Hotline 2

TK 20: Support 6

TK 25: Hotline 3

Johnson 14:22

Mi .

14.Feb

TrK 20: Support 6

TrK 21: Support 7

TrK 22: Support 8

TrK 23: Support 9

TrK 24: Support 10

TrK 25: Hotline 3

TrK 26: Hotline 4

TK 10: Support 1

TK 15: Hotline 1

Example: toggle team

Line Seizure

Each team member is assigned seven call numbers, each programmed as a trunk key (TrK 10 to

TrK 16 and TrK 20 to TrK 26). For each member, these trunk keys are programmed either as support numbers or hotline numbers.

The first support number and the first hotline number of each team member is programmed as a team key on the other member’s tele-

Team Functions Examples of Use

phone, e.g. TrK 10 and TrK 15 on

Miller’s telephone as TK 10 and TK 15 on Johnson’s telephone. The assumption here is that most calls will go to the respective first call numbers, and team members can thus help each other out by answering one another’s calls.

On each telephone it is possible to toggle between the calls on individual lines, e.g. TrK 10 and TrK 11, by pressing the appropriate key (toggling).

Every call on a trunk key can be transferred to any other party by means of the R key. For more information, refer to the chapter entitled

“Consultation, Toggling, Transfer and Conference” in the “OpenPhone

61, 63, 65” user guide.

Line Busy Indication

If a line is busy, e.g. TrK 10 on Miller’s telephone, the appropriate team key will indicate this, e.g. TK 10 on Johnson’s telephone.

Call Signalling

In this example, calls via trunk keys are signalled acoustically. Calls via team keys are indicated by a visual signal (the team key LED flashes).

Examples of Use Team Functions

Call Queue

Introduction

A queue can be activated for the telephone numbers of any type of telephone, i.e. for system, analogue,

ISDN and DECT telephones.

If a call number with a queue is busy, calls to this number enter the queue.

A caller in the queue hears an idle tone.

Calls which remain in the queue for too long are cleared from the queue.

The caller then gets a 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 telephone, additional calls are signalled by a brief tone in the loudspeaker and in the display. If calls are in the queue, a number at the beginning of the second line of the display on the

OpenPhone 65 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 100 in the following order of priority: instant connection, sensor calls, automatic recalls, VIP calls, then other internal and external calls. Sensor calls thus have priority over other calls, for example. Calls of the same priority level are switched in the order of their arrival.

The system administrator sets the number of calls that can be placed in a queue individually for each user group. The value can lie between “0” and “99”. The “0” value deactivates the ”Call queue” function for a user group. When the maximum number of calls in the queue is reached, further callers hear a busy tone.

Only calls which have a “voice” service indicator are administered in a queue.

Note: As calling fax machines of-

ten operate with the “voice” service indicator (e.g. on analogue ports), you should assign ports for fax machines on the OpenCom 100 to a user

group without a queue.

Call Queue Introduction

Queues can be combined with the

“forwarding,” “pickup” and “hunt group” functions, for example, in order to configure an attendant terminal for an operator.

Activation of Queues

Queues can be activated per user group. The default factory setting of queues for the preset groups “Administrators” and “Guests” is off.

When using queues, it often makes sense to activate call waiting protection. For this purpose, “Call waiting protection” authorisation must be allocated to the user group, and call waiting protection must be activated on the terminal.

You should configure a new user group (e.g. “Operators”) and activate the authorisations “Call queue”, “Call waiting protection” and, if necessary, “Call forwarding”. If users belong to this group, a queue will be activated automatically for all telephone numbers assigned to them.

Call Forwarding

Forwarded calls of the forwarding type “Immediately” and “On busy” have priority over queues. The queue of the forwarding telephone is not used for forwarding calls in this manner.

During the configuration of this type of call forwarding, the contents of the queue are not transferred to the target terminal. If there are still calls in the queue when the call forwarding function is activated, these calls can only be accepted on the source terminal.

If a call is to be forwarded “After delay”, it enters the queue. If the call has not been answered before the delay period expires, it will be forwarded to the target terminal and can then be answered there.

Pickup

The functions “Pickup” (from a pickup group) and “Pickup selective” can be used together with queues.

A user who accepts a call using

“Pickup” or “Pickup selective” picks up the next call from the queue.

Hunt Groups

Hunt groups of the “parallel” type are usually used together with queues, with the queues of each telephone in the group being synchronised to each other. When a call to the number of the hunt group arrives, the call enters all parallel queues. If a call from one of the queues is answered, it is removed from all other parallel queues.

Introduction Call Queue

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 terminal, the OpenPhone 25/27.

Configuration

■

Configure the system access or access for multiple terminals under PBX Configuration: Ports:

■

Configure the OpenPhone 65 and the RFP 21/23 under PBX

Configuration: Ports: U pn

■

Configure a trunk key for the

OpenPhone 65 under PBX Con-

figuration: System telephones.

■

Configure the OpenPhone 25/27 under PBX Configuration:

Ports: DECT-PP and assign the

OpenPhone 25/27 its own telephone number. Check in the

OpenPhone 25/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. Assign this user to the “Operators” user group. Assign the telephone numbers of the

OpenPhone 65 trunk key and the number of the mobile

OpenPhone 25/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 25/27 (in the menu

Call forwarding: Divert

phone: Immediately).

Use

Incoming calls are routed to the

OpenPhone 65 manned by the operator, who then puts the calls through. A queue is used so that callers do not get a busy signal. The display on the OpenPhone 65 indicates

Call Queue Examples of Use

how many calls there are in the queue.

If the operator wants to leave the workstation and take along the attendant terminal, call forwarding to the OpenPhone 25/27 is activated by pressing a function key. Calls which are in the OpenPhone 65 queue must still be answered on this telephone. New calls are signalled on the mobile OpenPhone 25/27 or enter its queue, allowing the

OpenPhone 25/27 to be used as a mobile 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 25/27. New calls are signalled on the OpenPhone 65 or enter 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 under PBX Configuration: Ports:

■

Configure the three

OpenPhone 65 telephones under PBX Configuration: Ports:

U pn

■

Configure a trunk key with its own telephone number for each of the OpenPhone 65 telephones 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 telephone 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 operators and assign these settings to the user group called “Opera-

Examples of Use Call Queue

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

Protection menu.

■

Program a function key with the function “Sign on/sign off from hunt group” on the three system telephones (in the menu

Calls: Hunt group).

Use

Incoming calls are signalled in parallel to all signed-on attendant terminals. 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 attendant terminals accepts a call from the queue, the call is removed from the queues of all the other attendant terminals. The display on each attendant 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 signoff, 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.

Call Queue Examples of Use

Multi-Company Variant

Communications systems are frequently shared by several companies. These companies want to jointly use the existing infrastructure

(e.g. the existing lines and features of the system), while at the same time they wish to organise and pay for their communication completely independently of one another.

This “multi-company variant” can be implemented using the

OpenCom 100 within a shared office, for example.

In the multi-company variant, the companies are essentially completely independent of one another.

This allows them to have their own trunk lines, which is useful for billing purposes. The OpenCom 100 hardware and software are used equally by all the companies, however. It is possible to configure the

OpenCom 100 for each company and define the extent to which the features of the system may be used.

In brief, the features of the multicompany variant are as follows:

■

Up to five companies can be configured at the same time.

■

Every user of the OpenCom 100 is assigned to a company.

■

Each available trunk group is uniquely assigned to a company so that incoming external calls can be transferred to the correct internal subscriber.

■

For each company, every route can have its own code. For example, it is possible to activate different routes with the code

“0” for different companies. This enables separate charging for outgoing external calls, for example.

■

An individual exchange (“operator”) can be set up for each company.

■

Each company can maintain the communication data of its business partners in its own company telephone book.

■

The charges can be billed individually for each company.

Multi-Company Variant

Configuring the Multi-Company Variant

The multi-company variant can be commissioned and configured by the system administrator of the

OpenCom 100 without any major effort. In the multi-company variant, the communications system behaves in exactly the same way as the single-company variant. This is particularly of interest to users who want to expand their own system and at the same time operate it in a group.

The process in brief:

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

6. An exchange must be set up for each company so that the

OpenCom 100 can correctly process statuses in which a call should be routed to the ex-

change (see Configuring the

Company Exchange starting on page 99).

1. The feature must be activated

(see Activating the Multi-Com-

pany Variant starting on page 97).

Activating the Multi-

Company Variant

2. The required companies must be

set up (see Configuring and Man-

aging Companies starting on page 98).

3. The users of the OpenCom 100 are assigned to the individual

companies (see Assigning Users starting on page 98).

4. In order that the OpenCom 100 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 99).

To be able to configure several companies in the OpenCom 100, the

“Multi-company variant”

(OpenCompany 45) program package must first be activated. This is done in the Configurator on the

Web console in the

SYS Configuration: Licences menu.

The licence confirmation you received with the program package contains all the information you require about how to proceed.

Only when this package has been activated are the fields required to configure the multi-company variant available in the other menus of the Web console, for example in the

User Manager: User groups menu

Multi-Company Variant Configuring the Multi-Company Variant

or in the PBX Configuration:

Trunks menu.

Configuring and Managing

Companies

Up to five companies can be configured in the OpenCom 100. By default, one company with the name

“Company 1” is predefined. All configuration settings, e.g. in the user groups or in the trunk group configuration, apply to this predefined default company if not other company has been selected.

Companies are set up and managed in the PBX Configuration: 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 command Delete. If a company is deleted which is still used at other places (in the user groups, for example), the respective configuration is changed to the default company.

■

The name of the default company can be changed, but the default company itself cannot be deleted.

Assigning Users

For each user you must define the company to which they belong. This assignment determines, for example, which company telephone book the user has access to and which company-specific configuration data apply to them.

As the OpenCom 100 manages users in groups, the assignment “user > company” is also established this way. The company to which each user group belongs must be defined for each group. A user group can only belong to one company, i.e. not to several. However, a company can have several user groups. It is therefore possible, in the same way as in the entire system, to allocate a range of authorisation rights for the use and configuration of features for each company.

When setting up a new user group

(in the User Manager menu), you will find that the default company is predefined; another company can be assigned as long as no other companies have been set up.

Configuring the Multi-Company Variant Multi-Company Variant

Assigning Trunk Groups

Connections of the same type and in the same direction are arranged in a trunk group (e.g. S

0 multi-terminal connections). To be able to correctly transfer incoming calls to the members of the configured companies

(the users) via the lines of a certain trunk group of the OpenCom 100, each of the available trunk groups must be assigned to one of the companies. This is necessary to be able to transfer incoming external calls to the correct company exchange in cases where the called internal subscriber cannot be reached (“Connection to Operator”), for example.

The assignment of trunk groups to companies is done in the

PBX Configuration: Trunks: Bundle

menu.

For outgoing external calls which users set up via the lines of their company’s trunk group, the assignment of the trunk group to the company is irrelevant: the charges are assigned according to the “source” principle.

Charges are billed to the company to which the user belongs who set up the connection. The OpenCom 100 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 predialling a code.

In the PBX Configuration: Trunks:

Route menu, you can define which company can seize each route. An individual code for the seizure is allocated per route for each company.

The OpenCom 100 ensures that during configuration no seizure code is allocated twice (for two different routes) for each company. If during configuration of a route no code is allocated for one of the configured companies, the route concerned cannot be seized by the members

(user groups) of this company.

Configuring the Company

Exchange

An internal telephone number must be set up for each company which represents the exchange, i.e. “the operator”. The calls to specific extensions arriving at the exchange are routed to this number, for example, as are all external calls where the called subscriber (a user who belongs to this company) cannot be reached, as in the case of a timeout.

Multi-Company Variant Configuring the 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 exchange for this company.

Working with the Multi-Company

Variant

All the features of the OpenCom 100 which the users may already be familiar with from the single-company variant are available in the multicompany 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 company. In addition to this, “personal” and “central” telephone books exist:

■

A personal telephone book is available for each user.

■

The central telephone book can be used across the companies by all users of the OpenCom 100.

The company telephone book is a central telephone book for the whole company. It is only available to the users/user groups who are assigned to this company. You can also define whether the members of each user group may edit the company telephone book or not.

The company telephone book is treated exactly the same way on the system terminals as the other types of telephone books. This means that the entries listed in the personal, central and company telephone books are displayed on the system phones at the same time.

Users can also use the telephone book of their company with the

OpenCTI 50 Web applications and

phone book, assuming they are authorised to use these applications.

In addition, it is also possible to assign a user group with the authorisation to edit foreign company tele-

100

Working with the Multi-Company Variant Multi-Company Variant

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 100 can manage up to

2,000 entries in all telephone books

(in the central, personal and company telephone books).

Making Calls Between

Companies

All users of the OpenCom 100 can make internal calls to one another, irrespective of which company they belong to. Calls between users from the different companies are therefore not subject to any restrictions.

Billing Charges per

Company

In the Costs Web application you can output the charges for each company.

Users who are authorised to use this application can view the charges for each company.

Multi-Company Variant Working with the Multi-Company Variant

101

Configuring the PC Software

Further possibilities of use can be implemented on a workstation PC with the Windows operating system by installing drivers and programs.

You can find the installation programs required for this on the system CD that comes with the

OpenCom 100.

Proceed as follows to install extra software:

1. Log on under Windows NT or

Windows 2000/XP as the administrator.

2. Insert the system CD.

If your PC is suitably configured, the CD will start automatically.

Otherwise select “Run” from the

Start menu. Click on the

“Browse” button to look for the program “cd_start.exe” on the

CD. Then confirm this with

“Open” and “OK”.

3. Choose the required option from the start mask and follow the program instructions.

Further instructions for various options that are available are given below.

Setting up TAPI

With a TAPI (Telephony Application

Programming Interface) you can operate a CTI application (computer telephony integration). Here, the CTI application uses the services of the

OpenCom 100 with the help of the

TAPI driver installed on a Windows

PC.

Requirements

You 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 48 if you have

not yet established an IP network connection. CTI functions can be used only in conjunction with system telephones.

You must therefore have configured at least one user for a system telephone. In addition, you require a

TAPI 2.1-compatible CTI application, for example the Phone Dialer included in the Windows operating system.

102

Setting up TAPI Configuring the PC Software

Installing the TAPI Driver

1. Call up the start mask from the

system CD (see Configuring the

PC Software on page 102).

2. Select “Software, TAPI Service

Provider” from the start mask and follow the program instructions.

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 configure the TAPI connection.

1. In the Start menu, select “Settings > Control Panel”. Doubleclick on the “Telephony” icon

(“Phone and Modem Options” icon under Windows 2000/XP).

2. Change to the “Telephony Drivers” tab (“Advanced Options” tab under Windows 2000/XP).

3. From the list of installed driver software, select “OpenCom 100

Service Provider” and click on

“Configure”.

4. In the following dialogue you will find a list with the configured connections for the user who is currently logged on. Click on “New”.

5. In the following dialogue you provide information for the new connection. In the “Connection name” box you can enter a descriptive name for the connection. In the “CTI server” box you must enter the DNS name or the

IP address of the OpenCom 100.

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 100. This user must be allocated a system telephone. Confirm your entry with

“OK”.

6. The new connection is now configured. Close the opened dialogues with “OK” and “Close”.

Testing the TAPI Function

1. In the Start menu, select “Programs > Accessories > Communication” and then start the program called “Phone Dialer”.

Under Windows XP the “Phone

Dialer” is started indirect by using the dialling function of the

“Address book” (can be found in the start menu under

“Programs >Accessories”). A manual start of the program file

“Dialer.exe” in the “C:\Program files\Windows NT” folder is possible also.

2. In the “Tools” menu, select the item “Connect using...” to select the system telephone that is to

Configuring the PC Software Setting up TAPI

103

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

4. The number you entered is displayed on the selected system telephone. Lift the receiver to start dialling.

Note: If the “Phone Dialer” pro-

gram 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 application programming interface) Windows programs are able to access services and functions of an ISDN card. With a network-based CAPI, the OpenCom 100 allows the use of

ISDN functions also by PCs in which no ISDN card is integrated.

Requirements

You require an active IP network connection between the PC and the telephone system. Refer to the chap-

ter Configuration under Windows starting on page 48 if you have not

yet established an IP network connection.

Please note: Before installing the

CAPI driver for the OpenCom 100, any existent ISDN card must be removed and any CAPI drivers on your PC must be de-installed.

Installing the NET CAPI driver

1. Call up the start mask from the

system CD (see Configuring the

PC Software on page 102).

2. Select “Software, NET CAPI

Driver” from the start mask and follow the program instructions.

Configuring the NET CAPI Driver

The NET CAPI driver requires an extra internal number so that the “virtual

ISDN card” on the OpenCom 100 can be addressed:

104

Setting up NET CAPI Configuring the PC Software

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.

3. Go to the Configurator, User

Manager: User menu. Select one of the users shown. Enter the number just assigned in one of the boxes No. 1 to No. 10.

Confirm your entry with Apply.

4. If it is to be possible to call the

“virtual ISDN card” externally, or if external calls are to be possible, the number must be included in call distribution (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 programs on the system CD.

Using the Systray Display

You can configure a systray display for the OpenCom 100 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 connection is active. It is also possible to display the current occupancy of the trunk lines.

Requirements

To use the systray display, you must

first install TAPI; see Setting up TAPI starting on page 102.

Please note: The systray display

requires a current version of TAPI. If you are using TAPI from an earlier version of the OpenCom 100, you must first install the newer version from the system CD.

Configuring the PC Software Using the Systray Display

105

Installing the systray display

1. Call up the start mask of the sys-

tem CD (see Configuring the PC

Software on page 102).

2. From the start mask, select

“Software, install systray”. Follow the program instructions.

3. Start the copied program by

“Start > Run” and the configuration dialogue is displayed. Select one of the entries displayed under Existing PBXs. Enter your user name and password in the boxes under Log-on.

4. If you activate the Autostart check box, you will see the systray display even after restarting your PC.

5. Confirm the entries in the configuration dialogue with OK and the systray display logs on for the OpenCom 100.

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

Browser for OpenCTI

You can simplify the daily use of the

OpenCTI using the Web browser especially adapted for the

OpenCom 100. Each time the workstation is restarted, this browser program can automatically start and log you in. This means the OpenCTI is always operational and can be accessed using the icon in the information area of the task bar.

Installing the browser for

OpenCTI

1. Call up the start mask from the

system CD (see Configuring the

PC Software on page 102).

2. From the start mask, select

“Software, Install browser for

OpenCTI”. Follow the program instructions.

3. Follow the program instructions.

106

Browser for OpenCTI Configuring the PC Software

After installing the browser, there is a new menu entry in the Windows start menu under Programs:

OpenCTI Browser.

Further information can be found in the online help of the browser program. To view this, click the top left corner of the program window on the system menu icon or on the icon in the information area of the task bar. Select the Readme command.

Synchronising the PC Clock

With the network service SNTP (simple network time protocol) it is possible to synchronise the internal clock of a PC with the time of the

OpenCom 100.

Requirements

You must enter the time zone so that the OpenCom 100 can calculate the time of the internal clock back to the

GMT (Greenwich Mean Time) required for SNTP:

1. Go to the Configurator, SYS

Configuration: System menu.

Click on Change.

2. Under Internet time (SNTP), enter the Time zone for which the time of the OpenCom 100 applies and whether summer time is allowed for. Confirm this with

Assign.

Configuring SNTP

For various operating systems, you can use one of the numerous SNTP programs offered for downloading on the Internet. Configure the

OpenCom 100 as an SNTP server for such programs.

SNTP with Windows 2000

Here you configure the SNTP server as follows:

1. Log on as the administrator.

Start the “Command Prompt” under “Start > Programs > Accessories”.

2. Enter the command line “net time /setsntp:192.168.99.254”.

Confirm with the enter key. This command changes the setting for the SNTP server address in the system registry. Close the command line.

3. Open the “Services” dialogue under “Start > Settings > Control Panel > Administration”. Set the autostart type of the “Windows Timer” service to “Automatic”. Start the service with

“Process > Start”. Every time the

Configuring the PC Software Synchronising the PC Clock

107

service starts, the PC clock is synchronised with the time of the OpenCom 100.

Please note: In a Windows do-

main network, the PDC server (primary domain controller) should automatically assume the function of the timer.

SNTP with Windows XP

Here you configure the SNTP server by double-clicking on the time in the

Start bar. Enter the OpenCom 100 as the “server” in the “Internet time” tab.

Address Queries using LDAP

You can search the data of the central telephone book of the

OpenCom 100 from a workstation in the LAN using LDAP (Lightweight Directory Access Protocol”). When configuring an LDAP-enabled program, specify the IP address of the

OpenCom 100 as the address of the

LDAP server.

LDAP with Outlook Express

You can configure and operate the

LDAP directory service with Outlook

Express

, a Microsoft

e-mail program, as follows:

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 access will then open.

3. Under Internet directory

(LDAP) server, enter the ad-

dress of the OpenCom 100. 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 entry with the OpenCom 100 address. Enter a user in the Name input field, Administrator for example. Then click on Find now.

108

Address Queries using LDAP Configuring the PC Software

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.

USB DECT Box on the OpenCom 100

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 100 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

U pn

interface on the

OpenCom 100. Instructions on how to do this can be found in

the section Upn Ports starting on page 24.

2. Configure the RFP 21/23 in the

Configurator, using the PBX

Configuration: Ports: U pn

menu.

3. Install the software of the USB

DECT Box and then connect the

USB DECT Box to your PC. Further 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 assign a telephone number for the data port.

5. Check the USB DECT Box in. Further information on how to do this can be found in the corresponding chapter of the “USB

DECT Box” manual and in the online help provided in the

OpenCom 100.

6. Assign a user to the telephone numbers of the USB DECT Box in the Configurator (menu User

Manager: User).

Configuring the PC Software USB DECT Box on the OpenCom 100

109

Tip: We recommend that you create the Internet access indirectly via the RAS access of the OpenCom 100.

If you wish to use the USB Box to dial up an Internet provider directly, follow the instructions in the corresponding 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 accessing the Internet via the OpenCom 100 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 100 Configurator

(menu NET Configuration: Con-

nections: ISP). You can edit/create suitable filter lists for the Internet 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 corresponding 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 100 user.

Detailed information can be found in

the Internet starting on page 125

section of the Frequently Asked Ques-

tions chapter. The information con-

cerning the Internet functionality of the OpenPhone 25/27 also applies to the USB DECT Box.

Technical Data for

Operation on the

OpenCom 100

■

Data transmission with RAS access / Internet access via the

OpenCom 100: Up to 64 kbit/s gross

■

Data transmission with direct dial-up of a provider: Up to 128 kbit/s gross

110

USB DECT Box on the OpenCom 100 Configuring the PC Software

Configuration Guide

The Configuration Guide contains a series of flowcharts that will help you to plan the configuration of the

OpenCom 100 and guide you through the necessary settings step by step, focusing on the network settings. The individual charts are summarised below:

Note: Settings for mail and ISP and

RAS access are only possible by re-

leasing the OpenCom 100 IP pack-

age on the Web console Configurator

in the SYS Configuration: Licences

menu.

■

Overview: This chart gives you an overview of the initial configuration of the OpenCom 100.

■

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

■

Configuring ISP Settings: These instructions support you in configuring the Internet access.

■

Configuring RAS Settings: This chart guides you through the configuration of the RAS settings.

■

Configuring LAN-to-LAN Set-

tings: This chart guides you through the configuration of the

LAN-to-LAN settings.

■

Configuring E-Mail: This diagram tells you how to create the requirements needed for configuring the OpenCom 100 e-mail access function.

■

Configuring E-Mail Access: This overview provides instructions on configuring the

OpenCom 100 e-mail access server.

Configuration Guide

111

Overview

Yes

Ethernet network

Connect the OpenCom 100 and the configuration PC to the network

(LAN) exists?

Yes

Cross-connected ethernet cable available?

Connect the configuration PC to the OpenCom 100 LAN port.

Enable DHCP.

Connect the configuration PC to the OpenCom 100 COM port.

Generate the Dialup Networking entry with “occonfig”.

Start the OpenCom 100 configuration service via your Web browser.

Enter the OpenCom 100 address, for example “http://192.168.99.254”.

User Manager

PBX Configuration

Yes

Create the user groups and users.

Set the system data. Select the access type. Connect the S

, U pn

and analogue devices and configure them.

Configure the call distribution scheme.

Configure the Least Cost Routing function: zones, network providers and holidays.

LCR Configuration

Configure OpenCom 100

Least Cost Routing function?

Configure OpenCom 100 network functions?

Yes

Enter the licence code for releasing the IP package in the “System

Configuration: Licences” menu.

Easy Access Configuration

Dial in (RAS)?

Connection (LAN)?

Internet?

E-mail?

Yes

RAS Configuration

LAN-LAN Configuration

ISP Configuration

E-Mail Configuration

Save data

Flowchart: Overview

Finished

112

Overview Configuration Guide

PBX Ports

Do you have ISDN terminals that you wish to operate on an S

interface?

Define the access type

Define the external

interfaces

Set the access type (multiterminal access and/or system access).

Set the external S

interfaces and enter the telephone numbers assigned by your network provider.

terminals Yes

Define the internal S

0 interfaces

Set the internal S

interfaces and enter the internal telephone numbers.

Do you want to operate system telephones or

DECT terminals?

U pn

terminals Yes

Configure the

U pn

interfaces

Enter the U pn

interfaces and enter the internal telephone numbers.

No No

DECT terminals

Yes

Configure the DECT terminals

Do you want to operate

DECT terminals on the

OpenCom 100?

Check in the DECT terminals and enter the internal telephone numbers.

Do you want to operate analogue terminals

(e.g. a fax machine)?

Analogue terminals Yes

Configure the a/b interfaces

Set the analogue interfaces and enter the internal telephone numbers.

Do you want to use a sensor contact on the

OpenCom 100 (e.g. for a door opener)?

Sensor Yes Configure the sensor

Enter the internal telephone numbers for the time groups of the sensor.

Do you want to run the

OpenCount program?

COM

Finished

Flowchart: Configuring the PBX Ports

Yes

Configure the COM interface

Select the “connection data” option.

Configuration Guide PBX Ports

113

Easy Access

Do you have a computer network?

LAN

Yes

Host name

Assign a name to the OpenCom 100.

Finished

Do you have a DHCP server in your network?

Activate the OpenCom 100

DHCP server.

Enter the Ethernet-IP configuration for the OpenCom 100.

Enter the address range of the client computers in your network.

Do you have a DNS server in your network?

Specify the IP address of the OpenCom 100 under “Domain Name Server”. This is transferred as the DNS server to the client computers via DHCP.

DHCP

OpenCom 100

DHCP server

Yes

The OpenCom 100 takes the settings from your DHCP server

Ask your network administrator for the address range for the RAS accesses. For this purpose, your administrator must reserve an IP address range for the RAS accesses.

IP address

Network mask

Gateway address

DHCP adresses

Domain name

Client computers are informed of this gateway address via DHCP as a gateway.

Enter the domain name. This name is transferred to the client computers as the domain via DHCP.

DNS

OpenCom 100 as

DNS server

Yes

Specify the IP address of your internal DNS server under “Domain Name

Server”. This is transferred as the DNS server to the client computers via DHCP.

Enter the address range for the RAS accesses.

PPP addresses

Flowchart: Configuring Easy Access

Finished

114

Easy Access Configuration Guide

ISP Settings

Do you want to configure a new Internet provider?

Enter your provider's dial-in data.

“SYS Configuration: System:

Country” = “German”?

Your own ISP

Yes

T-Online

Provider-New: Provider,

Telephone Number,

User Name and Password

Specify the IP address of the DNS in the Internet.

Specify a standard POP server and a standard SMTP server.

Specify the maximum time of inactivity after which the connection to the ISP is cleared down.

Yes

Select a provider from the list

Select one of the default providers in

“NET Configuration:

Connections: ISP”.

Domain Name Server

Mail input server and mail output server

Maximum idle time

T-Online: Telephone number,

Access identification, T-Online number, Co-user number and Password

Configure T-Online in “NET:

Configuration: Connections: ISP:

Provider”. You will obtain the access data when you register.

Activate the status and select the provider

Configure the ISP in “NET:

Configuration: Connections: ISP”.

DSL

(PPPoE)

Yes

Is your IP address allocated by your provider?

PPP

Yes

Dynamic

Yes

Enter the IP address and network mask you wish to obtain from your provider.

Your own telephone number

Max. connection time per month

Specify the maximum connection time for one month.

HDLC

Yes

No LAN

Yes

IP address

Network mask

Specify the gateway for the Internet connection.

Gateway

Maximum idle time

Specify the maximum time of inactivity after which the connection to the ISP is cleared down.

Select the filter lists. Filter lists are created in “NET Configuration: Safe Access”.

Filter list IN

Filter list OUT

Finished

Flowchart: Configuring the ISP Settings

ISP cannot be configured.

Configuration Guide ISP Settings

115

RAS Settings

Have you made the network settings for the OpenCom 100?

LAN No

NET Configuration:

Easy Access

Configure the network settings for the OpenCom 100.

Configure the RAS access of the

OpenCom 100. “NET Configuration:

Connections: RAS”

Yes

Select from PAP,

CHAP and CLID.

Status

Telephone number

Activate the RAS access.

Specify the telephone number for which the RAS access should be configured.

Authorisation

Number of connections

Specify how many simultaneous connections are possible via this access.

Select the filter lists. Filter lists are created in “NET

Configuration: Safe Access”

Filter list IN

Filter list OUT

Have you created users with RAS access rights?

Users No

Yes

User Manager: Users and

User Groups

Configure users that have RAS access rights.

Add internal telephone number to the incoming call distribution scheme.

Finished

Flowchart: Configuring the RAS Settings

116

RAS Settings Configuration Guide

LAN-to-LAN Settings

Have you made the network settings for the OpenCom 100?

LAN

Yes

Configure the LAN-LAN connection. “NET Configuration:

Connections: LAN-LAN”

Protocol

Telephone number local

IP address local

Network mask local

NET Configuration:

Easy Access

Configure the network settings for the OpenCom 100.

Select between PPP and HDLC transparent.

Enter the internal telephone number.

Enter the local IP address.

Enter the local network mask.

Yes CLID

User name local

Password local

Authorisation method of the local

LAN: CLID, PAP or CHAP?

Specify the user name with which the remote LAN can access a destination.

Specify the password with which the remote LAN can access a destination.

Telephone number remote

IP address remote

Network mask remote

Specify the telephone number of the remote LAN access.

Specify the IP address of the remote LAN.

Specify the network mask of the remote LAN.

Yes CLID

Authorisation method of the remote

LAN: CLID, PAP or CHAP?

User name remote

Password remote

Direction of connection

Maximum connection time per month

Maximum idle time

Add internal telephone number to the incoming call distribution scheme.

Specify the user name with which the remote LAN can be accessed.

Specify the password with which the remote LAN can be accessed.

Select the direction of the connection.

Specify the maximum number of minutes per month the connection to the remote LAN can be set up for.

Set the maximum idle time after which a connection to the remote LAN is cleared down.

Finished

Flowchart: Configuring the LAN-to-LAN Settings

Configuration Guide LAN-to-LAN Settings

117

E-mail Function

Have you made the network settings for the OpenCom 100?

LAN No

Configure the network settings for the OpenCom 100.

NET Configuration:

Easy Access

Yes

Do you want to use e-mail from the Internet?

Internet

Yes

Configure your Internet access.

NET Configuration:

Connection: ISP

Has an internal e-mail server been configured in your LAN?

Have you stored the users to be notified?

LAN

Yes

Do you want to be notified of e-mails on your system telephones?

Notification

Yes

Users

Yes

No e-mail use

Finished

Create the users and activate e-mail notification. Also enter the users' e-mail addresses.

User Manager:

Users, User Groups and User Accounts

Set the polling time periods.

NET Configuration:

E-Mail Access

Finished

Flowchart: Configuring the E-mail Function

118

E-mail Function Configuration Guide

E-mail Access

Do you have access to a mail server in your network or in the Internet?

Mail server No

Configure your network/

Internet access.

NET Configuration: Easy Access or Configure ISP

Yes

Do you have created mail account polls in the “User Manager: User accounts”?

User accounts No

Set up user accounts in the User Manager.

User Manager: User Accounts

Yes

Configuration of e-mail access settings

Specify the time intervals in which the OpenCom 100 is to poll all mail accounts from the standard POP server.

Maximum number of e-mails per user account

Enquiry interval

Start and end times:

Monday to Friday 1st starting time

Monday to Friday 1st ending time

Monday to Friday 2nd starting time

Monday to Friday 2nd ending time

Saturday 1st starting time

Saturday 1st ending time

Saturday 2nd starting time

Saturday 2nd ending time

Sunday 1st starting time

Sunday 1st ending time

Sunday 2nd starting time

Sunday 2nd ending time

Specify the maximum no. of e-mails per user account that should be temporarily stored by the OpenCom 100.

Define the time windows in which the

OpenCom 100 should check the mail accounts for new messages in the time intervals that have been set. You can define two time windows for each working day (Monday to

Friday), and two each for Saturday and Sunday.

Flowchart: Configuring E-mail Access

Finished

Configuration Guide E-mail Access

119

Frequently Asked Questions

This chapter provides tips and information on how to deal with any malfunctions or faults you may experience with the OpenCom 100.

Please note: Repairs to the

OpenCom 100 should only be carried out by qualified personnel.

The following LEDs indicate that the

OpenCom 100 is ready for operation:

Power Good LED

Activity LED

LAN LEDs

Interface module

AC adapter

Position of LEDs on the OpenCom 100

The LAN LEDs are only visible on the

OpenCom 110/120when the labelling strip is removed.

120

General/Hardware

Question: The OpenCom 100 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 connected, the mains socket is supplying output, but the OpenCom 100 still does not function.

General/Hardware

DANGER! High voltage inside the device. To make the system dead, remove the power plug from the socket!

Take the housing cover off. Is the

“Power Fine” LED at the top left lit up? If not, contact your service centre or an authorised dealer. The AC adapter plug of the OpenCom 100 may be defective.

Question: After restarting the

OpenCom 100, nothing is indicated on the displays of any connected terminals.

Frequently Asked Questions

It takes a short while for the

OpenCom 100 to start up. After the restart, check whether the activity

LED flashes at a rate of 10s / 1s. This flash cycle indicates that the

OpenCom 100 has started up correctly and is ready for operation. If the OpenCom 100 has not restarted properly, reset the OpenCom 100 to its original factory setting (refer to

the chapter entitled Resetting the

System Data starting on page 60).

Telephony

Question: It is not possible to make external calls.

Check the connection between the

NTBA and the OpenCom 100.

In the Configurator, check whether the external S

ports are configured correctly (PBX Configuration: S0 menu).

Question: The OpenCom 100 is connected to an NTBA with a multi-terminal configuration. Why is it not possible to establish external connections?

With the original factory setting, an additional external S

port is set for an NTBA in system configuration; this additional port will be used first to seize a trunk line.

Deactivate the second S

port in the

Configurator (PBX Configuration:

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.

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-

Frequently Asked Questions Telephony

121

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 configured in the Configurator of the

OpenCom 100.

Make sure the user configured for this telephone belongs to a user group that has access to this feature

(Configurator, User Manager: User and User groups menus). Some features cannot be used until the system PIN is changed.

Question: Nothing is indicated on the display of one of the connected

ISDN telephones.

You have connected the ISDN telephone to an external S

port (RJ-45 socket). These ports are intended for connection to the NTBA only. Connect the telephone to an internal S

0 port (pressure terminal).

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 telephone in the Configurator (PBX

Configuration: Ports: S0 menu) must also be configured as an MSN on the ISDN telephone itself. For further information, refer to the User

Guide of your ISDN telephone.

Question: It is not possible to configure Call Distribution: Outgoing for multi-terminal access.

You have configured multi-terminal access and system access in parallel.

All outgoing calls are therefore established via system access, and outgoing call distribution can be configured for system access only

(Configurator, Call Distribution:

Outgoing menu).

A specific MSN can be seized for individual calls by means of a code number procedure. For further information, refer to the “OpenCom 100,

Operation on Standard Terminals”user guide.

Question: Which reason may have problems with receiving faxes resp. sending faxes?

In frequent cases, the reason may be found in a problem with the ISDN-L1 reference clock distribution. The L1 clock is delivered from the network provider. An unclean L1 clock distribution and the introduced signalling jitter is overheard by the human ear.

Nevertheless, data and fax transmissions may be disturbed by the jitter.

Please check, which ISDN lines will deliver the L1 clock. Details can be

found under L1 Clock starting on page 77.

122

Telephony Frequently Asked Questions

DECT

Question: The LED of the RFP 21/

23is flashing, but none of the DECT devices is functioning.

Make sure the terminal setting for the corresponding U pn

port is set to

RFP 21/23 (Configurator, PBX Con-

figuration: Ports: U pn

menu).

Question: The LED of the RFP 21/

23 is continuously lit up, but one of the cordless DECT devices is indicating “No connection”.

You have not configured a port for this DECT device. Configure a port in the Configurator and start the enrolment procedure (PBX Configura-

tion: Ports: DECT-PP menu).

Question: Is it possible to increase the time for the enrolment procedure?

You must manually enter the IPEI of the DECT device in the Configurator.

The enrolment time is then increased to one hour (PBX Configura-

tion: Ports: DECT-PP menu).

Question: Another manufacturer’s DECT device is not functioning.

Check whether the DECT device supports the DECT GAP standard. In the

Configurator, also make sure GAP is set for this DECT device (PBX 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 problem with the reference clock. Refer

also to Which reason may have prob-

lems with receiving faxes resp. send-

ing faxes? starting on page 122.

Frequently Asked Questions DECT

123

LAN

Question: It is not possible to establish a network connection with the OpenCom 100.

Check whether the LEDs for the hub and the PC’s network card are indicating a connection.

Remove the labelling strip. Check the LEDs for the LAN functions of the

OpenCom 100. The upper green LAN

LED at the top indicates whether the network cable has been properly connected. The lower red LAN LED at the bottom indicates whether there is any network traffic on the line.

To check whether there is a network connection with your OpenCom 100, enter the “ping IP address” command 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 100?

To find out what the IP address is, enter the code number

* 1 8 2 on one of the connected system telephones.

The code-number procedure

* 1 8 3 also displays the network mask.

Question: The network connection is functioning, but nothing is displayed in the browser.

Enter the complete IP address of the

OpenCom 100 along with the protocol identifier, for example http://

192.168.99.254/.

Check whether the browser has been configured for connection through a proxy server. If so, deactivate the “Connect through proxy server” setting.

Question: You have just configured the OpenCom 100 via the network. Why is it not possible now to establish a remote data transfer network connection?

The network card and the communication (remote data transfer) adapter cannot be run with the same routing setting. Deactivate the network card before connecting via the dial-up network.

Question: Our network has grown over time, with several segments connected by one central router.

How can PCs from all segments be connected with the OpenCom 100?

In the Configurator, use the LAN setting in ISP to specify the central router as the default gateway. If necessary, deactivate any filter rules de-

124

LAN Frequently Asked Questions

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 100 dynamically issues the IP addresses by DHCP. Can I firmly assign the IP address for our internal server PCs (mail, Web)?

You need a static address assignment for these PCs. Make the appropriate 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 entering 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 possible to establish incoming Internet connections with the PCs directly owing to the network address translation process.

Question: It is not possible to access the Internet with the

OpenPhone 25/27.

The requirement for this is that the set should be configured as Hand-

set+data. The telephone number used by the OpenPhone 25/27 to establish an Internet connection must also be specified in the respective user profile (Configurator, User

Manager: User menu).

With the OpenPhone 25/27, the Internet can be accessed either di-

Frequently Asked Questions Internet

125

rectly via the remote data transfer network or indirectly via RAS access on the OpenCom 100. For direct access you can directly dial any provider. Indirect access uses the routing function of the OpenCom 100, accompanied by the configured security features, for example.

Directly via remote data transfer network

If the Internet is accessed directly via the remote data transfer network, make sure that

■ the remote data transfer network is properly installed on your PC and that the correct ISP access data is configured,

■ the internal number used by the

OpenPhone 25/27 to establish the data connection is configured for outgoing call distribution (Configurator, PBX Config-

uration: Call Distribution:

Outgoing menu).

Indirectly via RAS access

If the Internet is accessed indirectly via RAS, the system administrator should make sure that:

■ permission has been given for

Internet access via RAS (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 Internet access, refer to the

“OpenPhone 25” user guide or to the

“OpenPhone 27” user guide.

126

Internet Frequently Asked Questions

Technical Specifications

Mains power supply

Rated power

Safety class

Euro ISDN external for basic access, DSS1 protocol

230 V ~ 50 Hz

OpenCom 105:

80 VA

OpenCom 105:

OpenCom 110:

80 VA

OpenCom 110:

Euro ISDN internal for ISDN terminals, DSS1 protocol

OpenCom 105:

OpenCom 110:

– Supply voltage

– Supply power

– Range

Euro ISDN switchable for basic access, DSS1 protocol or for ISDN terminals, DSS1 protocol

– Supply voltage

– Supply power

40 V ± 10%

3 W

150 m

OpenCom 105:

OpenCom 110:

– Supply voltage

– Supply power

– Range

40 V ± 10%

3 W for internal

– Range 150 m internal

U pn

for system terminals and DECT base stations

OpenCom 105:

OpenCom 110:

40 V ± 10%

3 W per U pn

bus

1000 m a/b for analogue terminals with pulse or DTMF dialling, flash duration of 60 to 310 ms

OpenCom 105:

– Supply voltage 40 V ± 10%

OpenCom 110:

– Supply power

– Range

V.24 port (COM)

– Range

25 mA

1,000 m for connection of a PC

5 m

OpenCom 120:

130 VA

OpenCom 120:

—

OpenCom 120:

—

OpenCom 120:

18x

OpenCom 120:

Technical Specifications

127

Permissible temperatures stationary, weatherproofed

Dimensions (B x H x D)

Weight (only system)

Contact load actor 1

Contact load actor 2

– Voltage range

Sensor, switched by low AC voltage

– Voltage range

+5°C to +40°C

396 x 390 x 100 mm

OpenCom 105: about 2.8 kg

OpenCom 110: about 2.8 kg

10 A / 125 V

2 A / 125 V

≈

= 5 V … 30 V

OpenCom 120: about 3.2 kg

= 6 V … 24 V

Note: The online help provides an

overview of the limits that should be observed when configuring the

OpenCom 100.

128

Technical Specifications

Index

a/b adapter 33

Accessories 36

Actor

See Intercom system 30

Actor/sensor port 25

Adapter

Audio 34

Cable (RJ-232 - RJ-45) 15

Upn 33

Add-on 37

Analogue a/b ports 24

Authorisations 11

Basic setting 60

Basic setting switch 26

Synchronising the PC (via

SNTP) 107

Configuration 45

Client 53

Configuration with Windows 48

Establishing a network connection 51

Initial configuration 45

Installing the remote data transfer network under Windows 9x 50

Loading software updates 59

Network card setup 51

Preconfiguration 57

RAS service 50

Remote configuration 57

Resetting the system data 60

Saving and loading the configuration 59

Serial port (V.24) 50

Starting the browser 52

System prerequisites 46

V.24 port 50

via V.24 port 6

Configuration examples 62

Introduction to TCP/IP 63

OpenCom 100 in a LAN with an IPenabled server 66

OpenCom 100 in a serverless

Configuration guide

LAN-to-LAN settings 117

Configuring

Starting the Web console 54

Connection scheme

Actor/sensor ports 31

Analogue (a/b) ports 29

S0 ports 28

Upn ports 28

Index

129

130

Basic settings switch 26

Internet functions 13

Telephony functions 10

Hardware basic setting switch 60

Installation 15

Basic setting switch 26

Interfaces

Multi-terminal Access 27

Multi-terminal access 5, 76

Music on Hold 29

External devices 29

Generating own files 61

PC status display 105

PCM port 26

Index

Pin assignment

Audio adapter 34

ISDN socket 24

Plug-in power supply 19

Point-to-point connections 78

Port assignment

Actor/sensor port 25

Analogue a/b ports 24

DSL port 25

LAN 25

PCM 26

S0 port pin assignment 24

S0 ports 23

S0 terminating resistor 23

Ports

Analogue a/b 18, 19, 20

Ports (see Interfaces) 23

Power failure 27

Q.SIG 77

Remote configuration 57

Resetting system data 60

Routes 80

S0 port 122

S0 port pin assignment 24

Index

S0 ports 23

S2M 77

S2M Connector Module 40

S2M-Anschlüsse 82

Safety

Power failure 27

Safety Precautions 16, 43

Saving and loading the configuration 59

Sensor

See Intercom system 30

Sensor port 25

SNTP 107

Software updates, loading 59

Sync port 26

System access 5, 76

System data, resetting 60

Systray display 105

Team functions

Explanation of keys 84

Introduction 84

Team key 85

Telephony 121

Terminating resistor 23

Upn port pin assignment 24

Upn ports 24

Voice mail 29

131

Notes

132

Index

Configuration Example

OpenCom 110

RFP 21

OpenPhone 63

Upn

RFP 21

Upn

Analogue fax a/b

S0

ISDN telephone

Configuration example: OpenCom 110 with connected terminals

OpenPhone 21

In the UK:

DeTeWe Ltd

1 Frogmore Road, Hemel Hempstead,

Herts, HP3 9TG

WWW: http://www.detewe.co.uk/

Other countries:

DeTeWe AG & Co.

Zeughofstrasse 1, D-10997 Berlin,

Germany

WWW: http://www.detewe.de/

Subject to changes

As of 06.2004

નમસ્તે! હું એક AI ચેટબોટ છું જે ખાસ કરીને DETEWE opencom 100 Mounting And Commissioning Manual સાથે તમને સહાય કરવા માટે તાલીમ પામેલો છે. મેં દસ્તાવેજની સંપૂર્ણ સમીક્ષા કરી છે અને તમને જરૂરી ચોક્કસ માહિતી શોધવામાં અથવા સ્પષ્ટ અને સરળ શબ્દોમાં સામગ્રી સમજાવવામાં મદદ કરી શકું છું. પછી ભલે તમે ચોક્કસ સુવિધાઓ, મુશ્કેલીનિવારણ પગલાં અથવા સામાન્ય વપરાશ વિશે માર્ગદર્શન શોધી રહ્યા હોવ, તમારા પ્રશ્નો પૂછવા માટે નિઃસંકોચ રહો. તમે તમારી ચિંતાઓ અથવા જરૂરિયાતો વિશે જેટલી વધુ વિગતો પ્રદાન કરશો, તેટલી વધુ ચોક્કસ અને અસરકારક રીતે હું તમને સહાય કરી શકું છું!

સહાયક ટાઇપ કરી રહ્યા છે

સહાયક કીબોર્ડથી બહાર છે. કૃપા કરીને, પછીથી ફરી પ્રયાસ કરો.

સામગ્રીનું કોષ્ટક

એવું લાગે છે કે તમે એક એવા દસ્તાવેજ પર પહોંચી ગયા છો જે ઘણી ભાષાઓમાં લખાયેલ છે, જેમાં તમારી મૂળ ભાષા નથી. તમે તમારી પસંદગીની ભાષા વિનાના પૃષ્ઠોને અસ્થાયી રૂપે છુપાવવા માટે નીચેની લિંક્સનો ઉપયોગ કરી શકો છો.

જાહેરાત

OpenCom

OpenCom 105, 107, 110, 120:

Mounting and Commissioning

User Guide

Welcome to DeTeWe

OpenCom 100 Product

Family

Contents

Features

Factory Settings on Delivery

Telephony Functions

OpenCom 107/105

OpenCom 110

OpenCom 120

All OpenCom 100

Communication Systems

Authorisations

Internet Functions

Installation

Scope of Delivery

Safety Precautions

Declarations of Conformity

Mounting Location

Wall Mounting

Available Ports

OpenCom 107

OpenCom 105

OpenCom 110

OpenCom 120

Positions of the Ports

Port Assignment, Termination,

Cable Lengths

S

Ports

U

Ports

a/b Ports

Actor/Sensor

LAN Port

DSL Port

Basic Setting Switch

PCM Port

Sync Port

Power Failure

Connectible Devices

Internal/External

S

Ports

U

Ports

a/b Ports

Actor/Sensor Ports

COM Port

LAN Port

Accessories and Adapters

a/b Adapter

U

Adapter

Audio Adapter

Approved Devices /

Approved Accessories

Device Combinations

Configurations without

Plug-in Power Supply

(Range up to 500 m)

Configurations without

Plug-in Power Supply

(Range 500 to 1000 m)

Configurations with

Plug-in Power Supplies

S

Connector Module

Installation

Configuration

Mounting the OpenCom 110/

120 Rack InfoCom System

Safety Precautions

Technical Data

Pinning of RJ 45 Jacks

Switches on Front Panel