DETEWE OpenCom 131 User manual
Reklam
Reklam
OpenCom 100
Mounting and Commissioning
User Guide
130
131
150
Welcome to DeTeWe
Thank you for choosing this DeTeWe product. Our product meets the strictest requirements with regard to quality and design.
The following instructions will guide you in the operation of your OpenCom 100 and answer most of the questions that may arise.
If you require further technical support or information about other DeTeWe products, please refer to our website at www.Aastra-Detewe.de. It provides additional notes and tips on the product.
OpenCom 100 Product Family
This user guide applies to the OpenCom 100 product family comprising the
OpenCom 107, OpenCom 130, OpenCom 131, OpenCom 150 and OpenCom 510 systems.
If a reference is made in the text to the OpenCom 100, the description applies to all systems; if the individual characteristics are different, a special note is given.
For members of the product family, the following manuals exist:
■ Manual for OpenCom 107
■ Manual for OpenCom 130, OpenCom 131 and OpenCom 150
■ Manual for OpenCom 510 (19" housing)
We hope you enjoy using the OpenCom 100.
Contents
Factory Settings on Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
V.24 and Doorstation Equipment Slots . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Slots for Additional Interface Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Port Assignment, Termination, Cable Lengths . . . . . . . . . . . . . . . . . . . .45
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
pn
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
1
2
0
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Accessories and Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Approved Devices / Approved Accessories . . . . . . . . . . . . . . . . . . . . . . .60
2M
Connector Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Mounting the OpenCom 150 Rack InfoCom System . . . . . . . . . . 69
Brief Guide to Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Configuring the OpenCom 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Saving and Loading the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Receiving System Messages as E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Basic Hardware Settings Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Generating Your Own MoH Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
OpenCom 100 in Computer Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
OpenCom 100 in a Serverless LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
OpenCom 100 in a LAN with an IP-enabled Server . . . . . . . . . . . . . . . .92
Useful Information on Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Propagation Delay and Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3
4
VoIP System Telephone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Functionality of PBX Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Putting a Cascaded PBX into Operation. . . . . . . . . . . . . . . . . . . . . . . . . 123
PBX Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Types of Point-to-Point Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Connection via an Active Transmission System . . . . . . . . . . . . . . . . . 131
Connection via the Public Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Enquiry Station for an Operator with Two System Telephones . . . 148
Group of Three Enquiry Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Configuring the Multi-Company Variant . . . . . . . . . . . . . . . . . . . . . . . . 153
Activating the Multi-Company Variant. . . . . . . . . . . . . . . . . . . . . . . . . . 153
Configuring and Managing Companies. . . . . . . . . . . . . . . . . . . . . . . . . 154
Assigning Trunk Groups/SIP Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5
Configuring the Company Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Working with the Multi-Company Variant. . . . . . . . . . . . . . . . . . . . . . . 156
Company Telephone Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Making Calls Between Companies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Billing Charges per Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Configuring the PC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Browser for OpenCTI and OpenHotel . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Address Queries using LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
6
Technical Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
7
8
Features
1.
Features
The OpenCom 100 is a communications system for integrated voice and data communication. The outstanding feature of this communications system is its modular structure:
■ The OpenCom 131 is equipped with all the necessary ports for connecting system telephones, ISDN devices and analogue devices. The system enables
Internet/intranet data communication, CTI applications and the system configuration with a standard web browser. Additionally, the OpenCom 131 is equipped with a slot for installing an “M100-AT” interface card. With this interface card, the OpenCom 131 can be connected to analogue trunk lines.
■ Even with the smallest OpenCom 130 version, it is possible to use all the most important communications applications. The basic module enables telephony with system telephones, ISDN telephones and analogue terminals, Internet / intranet data communication, CTI applications, sub-system operation and system configuration using a standard Web browser.
The expansion module of the OpenCom 130 provides three slots for further interface cards. Using different combinations of interface cards, the configuration of the OpenCom 130 can be tailored exactly to your communications requirements. The need for additional U pn
ports supporting DECT, further S
0 ports or more a/b ports can be met using one or more interface cards without changing the system.
■ OpenCom 150 is a system that can be tailored exactly to your communications requirements. Initially, the main module doesn’t carry any telephony interfaces.
They can be added by means of additional interface cards. The main module provides five slots for different combinations of interface cards. Unlike the
OpenCom 130, the main module of the OpenCom 150 is not divided into basic and expansion modules.
■ All named variations of the OpenCom 100 (OpenCom 130/131/150) offer additionally two special slots:
– One slot to incorporate a V.24 interface card. This card provides a serial port.
– One slot to incorporate doorstation equipment interface card.
9
Features
■ You can use an additional insertable memory card (CompactFlash) to operate further program packages, viz. the OpenVoice and OpenAttendant digital voice memory and voice information systems.
■ The special interface card M100-AT4 enables connecting analogue exchange lines. Additional information can be found in the user manual “M100-AT4
Interface Card”.
■ The additional S
2M
connector module allows you to operate an OpenCom 130/
150 on a primary rate access.
Cascading
Using the expansion module, the OpenCom 130 can be cascaded with a second
OpenCom 130 communications system. An Ethernet switch on the expansion module further enables applications featuring media convergence, such as the operation of a VoIP interface card M100-IP.
It is possible to cascade two OpenCom 150 (rack version) units. Two ports of the
Ethernet switch residing on the main module can be used externally. Two other ports are available for internal use with interface cards.
With the OpenCom 131 no PBX cascading with another system is possible.
However, PBX networking with a second infocom system is possible.
Further information regarding these configuration options can be found in the
chapters PBX Cascading starting on page 122 and PBX Networking starting on page 127.
Telephony
The OpenCom 100 communications system is designed to be connected to an
ISDN basic access using the DSS1 protocol. System access (point-to-point) and multi-terminal access (point-to-multipoint) are both supported. The two forms of access can be configured in parallel.
For this purpose
■ the OpenCom 131 includes two S
0
ports (one external one and one that can be switched between internal/external),
■ the OpenCom 130 basic module includes two S
0
ports (one external one and one that can be switched between internal/external),
10
Features
■ the OpenCom 130 expansion module with additional interface cards provides up to eight further S
0 ports (switchable between internal/external). An
overview of the available cards can be found under Interface Cards starting on page 40,
■ the OpenCom 150 with interface cards provides up to 12 S
0
ports (switchable between internal/external). An overview of all possible interface card combina-
tions can be found under OpenCom 150 (5 Slots) starting on page 43.
The firmware of the OpenCom 100 is designed for configuring up to 300 users.
You can connect the following devices to the OpenCom 100:
■ analogue terminals
■ Euro-ISDN terminals
■ ISDN telephones (on the U pn
port) OpenPhone 52
■ DeTeWe system telephones
■ DeTeWe RFP 22 and RFP 24 base stations and DECT handsets (via an RFP 22/24 base station on the U pn
port of an interface card)
Note: On an OpenCom 131 the U pn
ports are not DECT-enabled. This means, DECT base stations and DECT terminals cannot be operated on this communications system.
An S
0
port can be used by Euro-ISDN terminals working in accordance with DSS1.
A U pn
port is suitable for the OpenPhone range of DeTeWe system telephones.
RFP 22/24 base stations can also be connected to the DECT-enabled U pn
ports on interface cards for an OpenCom 130 and an OpenCom 150. An analogue port is used by standard analogue devices.
If the CNIP (calling name identification presentation) feature is supported by your network provider, the latter will show you the name of callers in addition to their number for each incoming trunk call. The OpenCom 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.
11
Features
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.
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 retrofitted V.24 interface card to the COM port for the purpose of configuring the system or transferring connection data.
To connect the OpenCom 100 to existing company hardware, “actor” ports
(output) and “sensor” ports (input) can be provided by retrofitting a doorstation interface card. For example, this can be used to operate a door opener and a doorbell via the system (this requires additional equipment).
There are two variants of doorstation equipment interface cards:
■ On an OpenCom 130 or an OpenCom 131 a “M100-TFE” interface card can be operated. This card provides two actor ports and three sensor ports to connect doorstation equipment.
■ On an OpenCom 150 a “M100-TFE-2” interface card can be operated. This card provides four actor ports and four sensor ports. This card enables to operate two entrance intercom systems, each providing two sensor ports for bell keys.
The OpenCom 100 allows you to use CTI (Computer Telephony Integration) applications made by other manufacturers. This requires installation of a TAPI driver on
a Windows PC (see Setting up TAPI starting on page 160). The OpenCom 100 also
has an integrated dialling wizard: the OpenCTI 50. Via the OpenCTI 50 users can call up and use telephone functions on PCs without first having to install a special
TAPI driver.
The OpenCom 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 credit card terminals, require a permanent data connection over the X.25 packet data network. Packet data transfer through the ISDN D channel (according to X.31 via
12
Features
SAPI 16) can also be established between several S
0
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
0
interfaces (for instance an internal and external S
0
interface). Equally, data can be forwarded (“routed”) over permanent QSIG lines. Data can also be routed over an S
2M
interface. It is possible to operate multiple terminals with the same TEI on different internal S
0
interfaces.
A TEI mapping table allows these X.31 connections to be routed to the same external S
0
interface.
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
0 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. 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 explanati-
ons under Useful Information on Internet Access starting on page 96.
13
Features
DECT Data Communication
Note: With an OpenCom 131 DECT Data Communication is not possible because the OpenCom 131 U pn
ports are not
DECT-enabled.
The OpenPhone 27 DECT terminals enable PCs that are not connected to the
OpenCom 100 via the internal S
0
ports or the Ethernet interface to access the
Internet. These PCs can make full use of all the Internet and e-mail features of the
OpenCom 100.
Data is transmitted via the internal data interface of the OpenPhone 27. For this the OpenPhone 27 is connected with the serial port of the PC. The Internet can then be accessed directly via the remote data transfer (i.e. dial-up) network. The
OpenPhone 27 sets up a data connection with the OpenCom 100 via the DECT air interface. The remainder of the connection set-up is either direct - through an
ISDN B-channel - or indirect - through the internal RAS access of the
OpenCom 100. Indirect RAS access is preferable. This uses the routing function of the OpenCom 100 and thus also the security features of the shared Internet access.
For detailed information on the installation of the required driver software and the various types of configuration, refer to the user guide for the OpenPhone 27.
For information on configuration of the OpenPhone 27 with a data interface, please refer to the online help documentation of the OpenCom 100.
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.
When configuring the OpenCom 100, e-mail account query can be configured for every member of staff. 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 terminal.
E-mail accounts for the sending e-mail can also can be configured for users. Emails can then, for example, be sent directly from the OpenCTI 50 to other users.
In addition, users who have had a voicebox configured for themselves, can let themselves be notified of new voicebox messages via e-mail.
Important events and errors are kept by the OpenCom 100 in an internal log book: the error store. To inform or alert the system administrators, entries in the log book
(system messages) can be sent via e-mail.
14
Features
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 functions and the call-queuing function.
With an additional licence, the web application “OpenCount” can be used. This web application enables you to register and store telephony connections and evaluate the connections with user defined filters. Further information can be found in the online help of the web console.
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. To operate the system as a DECT server the system’s U pn
ports must be DECT-capable. It is also possible to create a telecom system with several networked telecom installations.
Voice over IP (VoIP)
The OpenCom 100 supports the connection of VoIP terminals and thereby allow telephony via the existing company network infrastructure. For this purpose, corded system terminals of the type “OpenPhone IP” are available. These devices have the same functionality and support the same features as the non-IP enabled system terminals “OpenPhone”. For users who wish to use PC supported telephony, the IP system terminals are also available as separate licensable software
variations (OpenSoftphone). You will find further information in the chapter Voice
over IP (VoIP) starting on page 99).
Glossary
Refer to the explanations in the glossary (supplied as a PDF file on the system CD).
15
Factory Settings on Delivery Telephony Functions
2.
Factory Settings on Delivery
The following basic settings and features are active on delivery. We recommend that you configure the OpenCom 100 to your individual requirements before
putting it into operation (see Configuration starting on page 73).
The factory settings apply to smallest version of the OpenCom 131 and
OpenCom 130 (which only features the basic module). If an expansion module with interface cards exists, the additional interfaces are initially unconfigured. You must therefore first configure the slots of the expansion module to commission the interfaces.
Note: The OpenCom 150 generally requires the slots to be configured before any interface can be commissioned.
2.1
Telephony Functions
2.1.1 OpenCom 130
■ The S
0
1 port is configured as a multi-terminal connection, and the S
0
2 port as a system port.
■ OpenPhone 63 system telephones with the telephone numbers 30 to 32 are configured on the three U pn
ports.
■ Analogue terminals with the telephone numbers 10 to 13 are configured on the four a/b ports.
2.1.2 OpenCom 131
■ The S
0
1 port is configured as a multi-terminal connection, and the S
0
2 port as a system port.
■ OpenPhone 63 system telephones with the telephone numbers 30 to 32 are configured on the three U pn
ports.
■ Analogue terminals with the telephone numbers 10 to 17 are configured on the eight a/b ports.
16
Factory Settings on Delivery Authorisations
2.1.3 OpenCom 150
With the OpenCom 150 all ports (S
0
, U pn
and a/b ports) are realised by installing a specific combination of interface cards for this purpose. An overview of available interface cards can be found in the “Interface cards”chapter in the section
OpenCom 150 (5 Slots) starting on page 43.
■ The OpenCom 100 is configured ready for operation in Germany.
■ Analogue devices: The dialling mode (pulse dialling or DTMF) is automatically detected.
■ All corded terminals connected to the basic module ring when there are incoming external calls.
■ The system PIN, for example for remote-programmable call diversion, is set at
“0000”.
2.2
Authorisations
The use of functions by a terminal on the OpenCom 100 is regulated by means of authorisations. Authorisation is configured by means of user groups to which the users with their terminals are then assigned.
Three user groups are preset: “Administrators”, “Standard” and “Guests”. “Administrators” have access to all functions of the OpenCom 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. The “Standard” user group, because of its default settings, is well suited as a starting point for the creation of user groups for normal users of the system (e.g. the staff members of a company).
Note: When the OpenCom 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
groups, refer to the online help in the chapter entitled “User
Manager”.
17
Factory Settings on Delivery Authorisations
The following terminal functions are factory preset to the “Administrators” group:
■ External line access: international numbers can be dialled from all configured telephones. External lines must be seized by entering a prefixed code.
■ Least cost routing is not active. As soon as LCR is configured, users can make calls via individually selected call-by-call providers.
■ “VIP call” is activated.
■ Announcements to system telephones are possible.
■ Baby calls can be configured.
■ If a call key is configured for a user on more than one terminal, he can program this key for more than one outgoing call, i.e. he can use his various terminals to make parallel calls from this telephone number.
■ “Pick-up” and “Pick-up selective” of calls from other telephones are activated.
Pick-up protection is deactivated.
■ “Call removal” is deactivated.
■ Callback (on busy) can be activated.
■ If more than one terminal is configured for a user under the same number, they can suppress the signalling of calls on the parallel terminals.
■ Function “Reaction: Connection will be disconnected” is deactivated as callers trying to reach a terminal that cannot be reached or is busy will hear a busy signal.
■ The “call queue” function is deactivated.
■ Call forwarding to internal or external numbers can be activated. Call forwarding after delay is executed after 20 seconds. Door calls and MSN groups can be forwarded. Call forwarding for other users and call forwarding by other users are deactivated.
■ It is possible to transfer an external call to an external subscriber.
■ Three-party conferences can be set up.
18
Factory Settings on Delivery Authorisations
■ Connections can be parked.
■ Call protection can be activated, call-waiting protection, announcement protection and pick-up protection can not be activated.
■ Transmission of one’s own phone number (MSN or system access number) can be suppressed on a per-call basis.
■ The telephone lock can be activated. The terminal PIN is “0000”.
■ Interception of “malicious” callers is possible if this feature has been ordered from the network operator.
■ The white list, black list and call filters are not preconfigured and thus not active. If these lists are configured, they can be activated for the user groups. A special list with emergency telephone numbers is preset and activated.
■ Call lists on terminals list internal calls, external calls, calls from the door and calls that the user received while they were telephoning.
■ Function keys can be programmed on system telephones, no keys are locked.
■ The evaluation of connection data by external cost-recording programs is deactivated.
■ The cost multiplier is set to 100%, i.e. the costs are not multiplied by any factor.
There are no preset basic amounts for the charging of calls.
■ Speed dialling is possible if this has been configured in the OpenCom 100 central telephone book.
■ Keypad dialling can be used.
■ The door opener can be activated from all terminals. Door calls can be forwarded.
■ Time control is not active as there are no time groups configured.
■ Call diversion for SMS calls in the fixed-line network is not activated.
■ Calls can be marked with a booking number for the purpose of project based accounting.
19
Factory Settings on Delivery Internet Functions
■ Users can use the OpenCTI 50 to send short messages to other users.
■ 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.
■ Applications requiring a license (e.g. OpenCount) can be used after being activated.
■ Access via RAS is not allowed.
■ E-mail notification to system terminals is possible. There are no user accounts configured for the sending of e-mails, the authorisation for sending e-mails is not deactivated.
■ The multi-company variant is not activated.
2.3
Internet Functions
■ RAS access (with or without callback) can be set up for every OpenCom 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).
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
20
Factory Settings on Delivery Internet Functions
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.
21
Installation
3.
Installation
Scope of Delivery
3.1
Scope of Delivery
The delivery consists of:
■ One OpenCom 131 communications system (in a basic version) or
OpenCom 130 (in a basic version with a basic module) or OpenCom 150
■ One connection cable for the ISDN S
0
port
■ One set of mounting screws and wall plugs
■ One plug-in power supply (of the TR25240-E-01A13 type) to supply the basic module
With the OpenCom 130 this power supply is dimensioned to operate the basic module only. Installing the expansion module requires an additional power supply.
■ One set of short user guides
■ One CD including the complete documentation and software
The OpenCom 130 expansion set consists of:
■ One expansion module
■ One AC adapter with a connection cable to supply the expansion module with power
■ One mounting set with which to install the expansion module and the AC adapter in the OpenCom 130 housing
■ One (short) Ethernet connection cable with which to connect the basic module to the expansion module.
22
Installation Safety Precautions
3.2
Safety Precautions
The CE symbol on the product confirms that it meets the technical guidelines on user safety and electromagnetic compatibility valid at the time of approval.
Please note: Installation and maintenance should only be performed by specially trained personnel. Always remove the power plug and the plug-in power supply from the mains socket before connecting devices to the OpenCom 100 ports.
DANGER!
This device contains hazardous voltages. To make the system powerless, remove the power plug and the plug-in power supply 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 use the original plug-in power supply: No. 4512699 (TR25240-E-01A13 type) for an OpenCom 131 and for the basic module of an OpenCom 130.
The housing cover may only be opened by authorised personnel. Unauthorised opening of the housing cover and improper repair may damage the
OpenCom 100 and invalidate the warrantee.
CAUTIONT!
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.
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 ana-
logue ports. For details, refer to the section entitled a/b Ports starting on page 48.
23
Installation Declarations of Conformity
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.
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.
3.3
Declarations of Conformity
The OpenCom 130, OpenCom 131 and OpenCom 150 ITC 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.aastra-detewe.de.
3.4
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,
24
Installation Wall Mounting
■ on or near inflammable materials,
■ or near high-frequency devices such as transmitters, X-ray or similar apparatus.
Use a separate 230 V power circuit and install overvoltage protection.
3.5
Wall Mounting
The OpenCom 100 is mounted on the wall with three screws as shown in this diagram:
A
332
B C
184 134
D
Mounting plan
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.
25
Installation Installing an Expansion Set
3.6
Installing an Expansion Set
This chapter is addressed to customers operating an OpenCom 130 system and who wish to equip their infocom system with multiple interface cards for extra ports.
With the OpenCom 150 and OpenCom 131 infocom systems installing an expansion set is not necessary:
■ With the OpenCom 150, all functions reside on only one large module. For this reason, the installation of an expansion set is not necessary for the
OpenCom 150.
■ The OpenCom 131 is equipped with a single slot for installing an additional interface card. Installing an expansion set is not necessary.
The OpenCom 130 has two separate modules offering more flexibility for extending the system. You can either install the expansion module when you first assemble the system or later as part of a system upgrade. In both cases, follow the mounting sequence as described here:
1. Turn off the OpenCom 130. Unplug the plug-in power supply from the socket.
You should not install the expansion module or install or uninstall additional interface cards while the OpenCom 130 is turned on.
2. Open the housing cover of the OpenCom 130. In this case, carefully follow the
Safety Precautions starting on page 23.
The existing basic module is mounted in the left half of the housing. No components may be mounted in the right half of the housing.
3. Place the expansion module in the intended mounting location in the right half of the housing. Be sure to align the 96-pin connector properly to the socket on the basic module. Push the expansion module towards the basic module so that both modules are securely connected to one another via the
96-pin connector.
26
Installation
4
A
3
Installing an Expansion Set
Slot 1 Slot 2 Slot 3
2
1
B
Installing the expansion module
4. Carefully press the expansion module at the top and bottom right, pushing it into the locking hooks provided (see “A” and “B” in the diagram). Secure the expansion module using the Phillips screws provided in the expansion set (see
“1” to “4” in the diagram).
27
Installation
A
2.
1.
Installing an Expansion Set
Installing the power supply for the expansion module
5. Place the power supply to the right of the expansion module. Carefully press the power supply into the mounting recess provided (shown in the diagram as
“1”). Move the power supply forwards until it snaps into place in all six pressure terminals (“A”, “2”).
6. Connect the power supply output (flat conductor cable) to the appropriate jack of the expansion module. Insert the fully insulated connector of the mains supply in the power supply connection provided.
7. Establish an Ethernet connection between the LAN port of the basic module
the expansion set. The LAN0 port of the expansion module is intended for connection to a corporate LAN. You can connect an existing Ethernet connection cable to the LAN0 port of the expansion module.
You usually install at least one interface card on the expansion module. To do this, read the instructions in the following section.
Please note: Two power supplies are provided for the OpenCom 130 with an expansion module. Always turn on the power supply of the expansion module first and then plug in the plug-in power supply.
28
Installation Installing Interface Cards
3.7
Installing Interface Cards
The expansion module and the basic module of the OpenCom 130 resp. the main module of the OpenCom 150 can be expanded using interface cards. The main module of the OpenCom 131 is quipped with one large and two small slots for installing interface cards.
Please note: Turn off the OpenCom 100. Unplug both the plug-in power supply and (for an OpenCom 130/150) the main supply from the socket. You must not install or uninstall interface cards while the OpenCom 100 is turned on.
3.7.1 V.24 and Doorstation Equipment Slots
Doorstation equipment
V.24
OpenCom 130: V.24 and doorstation equipment slots
Doorstation equipment
V.24
OpenCom 131: V.24 and doorstation equipment slots
29
Installation Installing Interface Cards
V.24
Doorstation equipment
OpenCom 150: V.24 and doorstation equipment slots
The OpenCom 100 has two slots in which special interface cards can be operated
(V.24 and doorstation equipment). You can see the location of these slots in the diagrams.
■ The doorstation equipment interface card (also called “Door Phone” or “Door
Bell”) provides “actor” ports and “sensor” ports.
With the OpenCom 130 and the OpenCom 131 systems, an “M100-TFE” interface card can be used. For connecting a door station, this card type offers two actor and three sensor ports.
With the OpenCom 510 system, an “M100-TFE-2” interface card can be used.
This card type offers four actor and four sensor ports. With this card, two door stations can be connected with two call buttons for each door station.
■ The V.24 interface card provides a serial port.
Proceed as described below to install one or both of these interface cards:
1. Turn off the OpenCom 100. Open the housing cover.
2. Remove the slot card from the transport packaging. Check that it is the correct type of slot card. (There is a sticker with the type name on the connector.)
30
Installation
CAUTIONT!
Installing Interface Cards
Static charges can damage electronic components. Pay attention to the regulations regarding the handling of electrostatically sensitive components.
3. Carefully insert the interface card in the slot provided. The component side must face to the right.
Ensure the plug-in connection is sitting securely.
4. Connect the required port cable to the corresponding pressure terminals or
RJ45 jacks (see also Positions of the Ports starting on page 37).
5. Close the housing cover. Turn on the OpenCom 100.
You can query the status of the doorstation equipment interface card and the V.24 interface card in the Web console when the OpenCom 100 is operational again. To do this, call up the PBX Configuration: Ports: Slots menu page. The Status column in the table displays a green tick beside the name of the interface card.
3.7.2 Slots for Additional Interface Cards
The OpenCom 131 offers one large slot to operate an additional interface card. The interface card is connected with two port jacks.
The OpenCom 130 has three (the OpenCom 150 five) large slots in which you can operate interface cards. Each interface card is connected to the expansion module resp. to the main module via two port jacks. The following properties characterise the large slots of the OpenCom 130/150:
■ There is no prescribed order in which to use the jacks. You can, for example, therefore operate an interface card in slot 3 even though slot 2 is not occupied.
31
Installation Installing Interface Cards
■ Each of the slots is connected to a group of pressure terminals. Therefore there are also three pressure terminal groups on the expansion module of the
OpenCom 130 (five on the main module of an OpenCom 150). To be able to distinguish these, all the pressure terminals in a group are the same colour.
■ The slots are not of the same type. Therefore some of the available interface
cards may not be operated in all slots. Note the overview under Interface Cards starting on page 40.
Type (name) of interface card
OpenCom 130: Installing an interface card in an expansion module slot
Proceed as described below to install an interface card:
1. Turn off the OpenCom 100. Open the housing cover.
2. Remove the slot card from the transport packaging. Check that it is the correct slot card type. There is a sticker with the type name on the connector.
32
Installation
CAUTIONT!
Installing Interface Cards
Static charges can damage electronic components. Pay attention to the regulations regarding the handling of electrostatically sensitive components.
3. Carefully insert the interface card in the slot provided. The component side must face to the right.
Ensure the plug-in connection is sitting securely.
4. Connect the required port cable to the corresponding pressure terminals of
the relevant pressure terminal group (see also Positions of the Ports starting on page 37).
5. Close the housing cover and turn on the OpenCom 100 again.
The software of the OpenCom 100 can detect the type of interface card present.
The interface card must still be configured individually for commissioning.
You can query the status of the interface cards in the Web console when the
OpenCom 100 is operational again. To do this, call up the PBX Configuration:
Ports: Slots menu page. The Status column of the table displays a green tick beside the slot name (for an OpenCom 130 e.g. 0/1, 0/2 and 0/3). The column of the table must list the correct type of interface card.
33
Installation Available Ports
3.8
Available Ports
The OpenCom 100 has the following ports (see also Positions of the Ports starting on page 37):
3.8.1 OpenCom 130
The listed interfaces and ports are located on the basic module of the
OpenCom 130. Further interfaces and ports can be added by installing the
expansion set and additional interface cards (see Installing an Expansion Set
starting on page 26 and Installing Interface Cards starting on page 29).
■ One S
0
port to connect to an external S
0
bus (usually the NTBA), designed as an
RJ45 jack (S
0
1)
■ One switchable S
0
port (S
0
2), which can be connected as either an internal or external S
0
bus. The internal connection is via a pressure terminal and the external connection via an RJ45 jack.
■ Three U pn
ports, designed as pressure terminals (U pn
1 to U pn
3)
■ Four analogue a/b ports, designed as pressure terminals (a/b1 to a/b4)
■ One slot to incorporate a doorstation equipment interface card. The following ports can be used with such a card: two actor ports for connection to a door opener and the intercom of doorstation equipment. These are designed as pressure terminals (actor1 to activate a door opener and actor2 to activate doorstation equipment); three sensor ports for connection to the bell keys of doorstation equipment, designed as pressure terminals (sensor 1 to sensor 3)
■ One slot to incorporate a V.24 interface card. The following port can be used with the V.24 add-on card: one COM port to connect to a PC to configure and transmit connection data, designed as an RJ45 jack
■ One port to the LAN (10BaseT), designed as an RJ45 jack
34
Installation Available Ports
■ One CompactFlash “base” to incorporate a type I or type II CompactFlash memory card. These cards are necessary to operate the OpenVoice and Open-
Attendant program packages. Only use high speed memory cards which are recommended by DeTeWe. Other memory cards or “Microdrive” type memory cards may not be able to maintain the required access speed.
Tip: For the stored voice announcements and a recording time of one hour a memory card with 32 Mbyte is required.
■ One port jack to connect the plug-in power supply to power the basic module.
Only use the original OpenCom 130 plug-in power supply provided in the supply scope to power the basic module.
3.8.2 OpenCom 131
■ One S
0
port to connect to an external S
0
bus (usually the NTBA), designed as an
RJ45 jack (S
0
1)
■ One switchable S
0
port (S
0
2), which can be connected as either an internal or external S
0
bus. The internal connection is via a pressure terminal and the external connection via an RJ45 jack.
■ Three U pn
ports, designed as pressure terminals (U pn
1 to U pn
3)
■ Eight analogue a/b ports, designed as pressure terminals (a/b1 to a/b8)
■ One slot to incorporate a doorstation equipment interface card. The following ports can be used with such a card: two actor ports for connection to a door opener and the intercom of doorstation equipment. These are designed as pressure terminals (actor1 to activate a door opener and actor2 to activate doorstation equipment); three sensor ports for connection to the bell keys of doorstation equipment, designed as pressure terminals (sensor 1 to sensor 3)
■ One slot to incorporate a V.24 interface card. The following port can be used with the V.24 add-on card:
35
Installation Available Ports one COM port to connect to a PC to configure and transmit connection data, designed as an RJ45 jack
■ One port to the LAN (10BaseT), designed as an RJ45 jack
■ One CompactFlash “base” to incorporate a type I or type II CompactFlash memory card. These cards are necessary to operate the OpenVoice and Open-
Attendant program packages. Only use high speed memory cards which are recommended by DeTeWe. Other memory cards or “Microdrive” type memory cards may not be able to maintain the required access speed.
Tip: For the stored voice announcements and a recording time of one hour a memory card with 32 Mbyte is required.
■ One port jack to connect the plug-in power supply. Only use the original
OpenCom 131 plug-in power supply provided in the supply scope.
3.8.3 OpenCom 150
The listed interfaces and ports are located on the main module or on the connection module of the OpenCom 150. Further interfaces and ports can be added
by installing additional interface cards (see Installing Interface Cards starting on page 29).
■ One slot to incorporate a double doorstation equipment interface card. The following ports can be used with such a card:
Four actor ports for connection to a door opener and the intercom of doorstation equipment. These are designed as pressure terminals (actor1 and actor3 to activate door openers, actor2 and actor4 to activate doorstation equipment)
Four sensor ports for connection to the bell keys of doorstation equipment, designed as pressure terminals (sensor 1 to sensor 4)
■ One slot to incorporate a V.24 add-on card. The following port can be used with the V.24 add-on card: one COM port to connect to a PC to configure and transmit connection data, designed as an RJ45 jack
36
Installation Available Ports
■ Two PCM ports for the connection of up to three systems, designed as an RJ45 socket (PCM)
■ Two ports to the LAN (100BaseT), designed as RJ45 jacks
■ One CompactFlash “base” to incorporate a type I or type II CompactFlash memory card. These cards are necessary to operate the OpenVoice and Open-
Attendant program packages. Only use high speed memory cards which are recommended by DeTeWe. Other memory cards or “Microdrive” type memory cards may not be able to maintain the required access speed.
Tip: For the stored voice announcements and a recording time of one hour a memory card with 32 Mbyte is required.
■ One port jack to connect the plug-in power supply. Only use the original
OpenCom 150 plug-in power supply provided in the supply scope.
3.8.4 Positions of the Ports
The following diagrams show the positions of the ports:
Default setting
S
2M
U pn
1
U pn
2+3 S
0
2 a/b
3+4
Sensor
1+2
Sensor
3
RJ45
S
0
1
RJ45
S
0
2 a/b
1+2
LAN Actuator
1+2
DC in
V.24
Position of the ports on the basic module (OpenCom 130)
37
Installation
Slot 1 Slot 2 Slot 3
Slot
1-1
Slot
1-2
Slot
2-1
Slot
2-2
Slot
3-1
Slot
3-2
Slot
1-3
Slot
1-4
Slot
2-3
Slot
2-4
Slot
3-3
Slot
3-4
PCM LAN 1 LAN 2 LAN 0 Slot
1-5
Slot
2-5
Slot
3-5
Position of the ports on the expansion module (OpenCom 130)
Available Ports
Default setting
Slot
V.24
Slot
Doorstation equipment
1-1
1-2
1-3
U pn
1
U pn
2+3
S
0
2 int a/ b a/ b
Sensor
1+2
Sensor 3
Slot 1
1- 4 1- 5
S
0
1 ext
S
0
2 ext a/ b a/ b
Actor
1+2
V.24
LAN
Position of the ports on the OpenCom 131
Slot 1
DC in
38
Installation
Default setting
V.24
Actuator
1+2 3+ 4
Slot 1
S
0
1 S
0
2 1-1 1-2 S
0
1
Slot 2
2-1 2-2
Slot 3
3-1 3-2
Slot 4
4-1 4-2
Slot 5
5-1 5-2
1+2 Sensor 3+ 4 1-3 1- 4 2-3 2- 4
S
0
3 S
0
4 S
0
2
1-5 2-5
Door
1+2
S
2M
Position of the ports on the OpenCom 150
3-3 3- 4 4-3 4-4
3-5 4-5
5-3 5-4
5-5
Available Ports
39
Installation Interface Cards
3.9
Interface Cards
3.9.1 OpenCom 131 (1 Slot)
An interface card of type “M100-AT4” can be installed in the free large slot. With this interface card it is possible to connect the OpenCom 131 to analogue trunk lines.
3.9.2 OpenCom 130 (3 Slots)
The following overview shows the available interface cards.
Interface card
M100-S4: 4 x S
0
M100-U4d: 4 x U pn
M100-U8d: 8 x U pn
M100-S2U6d:
2 x S
0
and 6 x U pn
M100-S2A6:
2 x S
0
and 6 x a/b
M100-A4: 4 x a/b
M100- A8: 8 x a/b
M100-AT4
M100-IP
Slots
1 2
● ●
3
Special features
● ●
S
0
are switchable internally/externally
U pn
are DECT-enabled
U pn
are DECT-enabled ● ●
●
●
●
●
U pn
are DECT-enabled
S
0
are switchable internally/externally
S
0
are switchable internally/externally
● ● ●
● ● ●
● 4 analogue trunk lines
● Voice over IP
40
Installation
Slot 1 Slot 2
S
0
1/1 S
0
1/2 S
0
2/1 S
0
2/2
S
0
1/3 S
0
1/4 S
0
2/3 S
0
2/4
-
Ports: 4 x S
0
Slot 1 Slot 2
U pn
1/1 U pn
1/2 U pn
1/3 U pn
1/4 U pn
2/1 U pn
2/2 U pn
2/3 U pn
2/4
-
Slot 3
Slot 3
-
Ports: 4 x U pn
Slot 1 Slot 2
U pn
1/1 U pn
1/2 U pn
1/3 U pn
1/4 U pn
2/1 U pn
2/2 U pn
2/3 U pn
2/4
U pn
1/5 U pn
1/6 U pn
1/7 U pn
1/8 U pn
2/5 U pn
2/6 U pn
2/7 U pn
2/8
-
Ports: 8 x U pn
Slot 1
S
0
1/1 S
0
1/2
Slot 2
S
0
2/1 S
0
2/2
U pn
1/1 U pn
1/2 U pn
1/3 U pn
1/4 U pn
2/1 U pn
2/2 U pn
2/3 U pn
2/4
Ports: 2 x S
0
and 6 x U pn
U pn
1/5 U pn
1/6 U pn
2/5 U pn
2/6
Slot 3
Slot 3
Interface Cards
41
Installation
Slot 1 Slot 2
S
0
1/1 1: S
0
1/2 S
0
2/1 1: S
0
2/2 ab 1/1 ab 1/2 ab 1/3 ab 1/4 ab 2/1 ab 2/2 ab 2/3 ab 2/4
Slot 3
Ports: 2 x S
0
and 6 x a/b ab 1/5 ab 1/6 ab 2/5 ab 2/6
Slot 1 Slot 2 Slot 3 ab 1/1 ab 1/2 ab 1/3 ab 1/4 ab 2/1 ab 2/2 ab 2/3 ab 2/4 ab 3/1 ab 3/2 ab 3/3 ab 3/4
-
-
Ports: 4 x a/b
Slot 1 Slot 2 Slot 3 ab 1/1 ab 1/2 ab 1/3 ab 1/4 ab 2/1 ab 2/2 ab 2/3 ab 2/4 ab 3/1 ab 3/2 ab 3/3 ab 3/4 ab 1/5 ab 1/6 ab 1/7 ab 1/8 ab 2/5 ab 2/6 ab 2/7 ab 2/8 ab 3/5 ab 3/6 ab 3/7 ab 3/8
-
Ports: 8 x a/b
Slot 1 Slot 2 Slot 3
-
ab 3/1 ab 3/2 ab 3/3 ab 3/4
M100-AT4 Interface Card (4 analogue trunk lines)
42
Interface Cards
Installation Interface Cards
3.9.3 OpenCom 150 (5 Slots)
The following overview shows the available interface cards.
Interface card Slots
1 2 3
M100-S4: 4 x S
0
● ● ●
Special features
M100-S2A6:
2 x S
0
and 6 x a/b
M100-A4: 4 x a/b
M100-A8: 8 x a/b
S
0
are switchable internally/ externally
U pn
are DECT-enabled M100-U4d: 4 x
U pn
● ● ●
M100-U8d: 8 x
U pn
● ● ●
M100-S2U6d:
2 x S
0
and 6 x U pn
● ● ●
M100-AT4
M100-IP
U pn
are DECT-enabled
● ●
U pn
are DECT-enabled
S
0
are switchable internally/ externally
S
0
are switchable internally/ externally
● ● ● ●
● *) ● ● ● *) In case no doorstation equipment interface card is used
● ● ● 4 analogue trunk lines
● ● Voice over IP
Slot 4 Slot 5
S
0
1/1
S
0
1/3
Slot 1
S
0
1/2
S
0
1/4
-
Ports: 4 x S
0
S
0
2/1
S
0
2/3
Slot 2
S
0
2/2
S
0
2/4
-
S
0
3/1
S
0
3/3
Slot 3
S
0
3/2
S
0
3/4
-
43
Installation
Slot 1 Slot 2 Slot 3
U pn
1/1
U pn
1/2
U pn
1/3
U pn
1/4
U pn
2/1
U pn
2/2
U pn
2/3
U pn
2/4
U pn
3/1
U pn
3/2
U pn
3/3
U pn
3/4
-
-
Ports: 4 x U pn
-
Slot 1 Slot 2 Slot 3
U pn
1/1
U pn
1/2
U pn
1/3
U pn
1/4
U pn
2/1
U pn
2/2
U pn
2/3
U pn
2/4
U pn
3/1
U pn
3/2
U pn
3/3
U pn
3/4
U pn
1/5
U pn
1/6
U pn
1/7
U pn
1/8
U pn
2/5
U pn
2/6
U pn
2/7
U pn
2/8
U pn
3/5
U pn
3/6
U pn
3/7
U pn
3/8
-
Ports: 8 x U pn
-
Slot 1 Slot 2 Slot 3
S
0
1/1
S
0
1/2
S
0
2/1
S
0
2/2
S
0
3/1
S
0
3/2
U pn
1/1
U pn
1/2
U pn
1/3
U pn
1/4
U pn
2/1
U pn
2/2
U pn
2/3
U pn
2/4
U pn
3/1
U pn
3/2
U pn
3/3
U pn
3/4
U pn
1/5
U pn
1/6
U pn
2/5
U pn
2/6
Ports: 2 x S
0
and 6 x U pn
U pn
3/5
U pn
3/6
Slot 1 Slot 2 Slot 3
S
0
2/1
S
0
2/2
S
0
3/1
S
0
3/2 a/b
2/1 a/b
2/2 a/b
2/3 a/b
2/4 a/b
3/1 a/b
3/2 a/b
3/3 a/b
3/4 a/b
3/5 a/b
3/6
Ports: 2 x S
0
and 6 x a/b a/b
2/5 a/b
2/6
Slot 4
Slot 4
Slot 4
Slot 4
Slot 5
Slot 5
Slot 5
Slot 5
Interface Cards
44
Installation Port Assignment, Termination, Cable Lengths
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 a/b
2/1 a/b
2/2 a/b
2/3 a/b
2/4 a/b
3/1 a/b
3/2 a/b
3/3 a/b
3/4 a/b
4/1 a/b
4/2 a/b
4/3 a/b
4/4 a/b
5/1 a/b
5/2 a/b
5/3 a/b
5/4
-
-
Ports: 4 x a/b
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 a/b
2/1 a/b
2/2 a/b
2/3 a/b
2/4 a/b
3/1 a/b
3/2 a/b
3/3 a/b
3/4 a/b
4/1 a/b
4/2 a/b
4/3 a/b
4/4 a/b
5/1 a/b
5/2 a/b
5/3 a/b
5/4 a/b
2/5 a/b
2/6 a/b
2/7 a/b
2/8 a/b
3/5 a/b
3/6 a/b
3/7 a/b
3/8 a/b
4/5 a/b
4/6 a/b
4/7 a/b
4/8 a/b
5/5 a/b
5/6 a/b
5/7 a/b
5/8
-
Ports: 8 x a/b
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5
-
a/b
3/1 a/b
3/2
a/b
4/1 a/b
4/2
a/b
5/1 a/b
5/2 a/b
3/3 a/b
3/4
M100-AT4 Interface Card (4 analogue trunk lines) a/b
4/3 a/b
4/4 a/b
5/3 a/b
5/4
3.10
Port Assignment, Termination, Cable Lengths
3.10.1 S
0
Ports
Whether you use the switchable S
0 ports for internal or external communication depends on your communications requirements and the existing basic accesses.
Note that the S
0
bus requires a terminating resistor of 100 ohms at each end.
45
Installation Port Assignment, Termination, Cable Lengths
In the case of the OpenCom 100, the S
0
buses are terminated by software. You make this setting in the S
0 port configuration in the Configurator on the Web console.
You can connect up to eight terminals on every internal S
0
bus; up to three of the terminals can operate without an external power supply. The length of the fourwire cable of an internal S
0
bus must not exceed 150 m. The power consumption of each internal S
0
bus is approx. 2 W.
S
0
Ports on Interface Cards
OpenCom
R
TR
IAE IAE
The S
0
bus is terminated at one end by the OpenCom 100.
IAE = ISDN socket (German: “ISDN Anschluß Einheit”) or an ISDN terminal.
TR = terminating resistor, the S
0
termination. The TR must be at the termination of the line. This can also be done by an appropriately wired IAE.
OpenCom
R
TR TR
IAE IAE
The S
0
bus is terminated by the TR at the ends.
1a
1b
2a
TR
TR
2b
Termination on an ISDN socket
46
Installation Port Assignment, Termination, Cable Lengths
S
0 int S
0 ext
2a 2b 1a 1b 1a 1b 2a 2b
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Switchable S
0
port on a pressure terminal
You can add further S
0 ports to the OpenCom 13/150 by installing suitable interface cards in a slot. These S
0
ports can be switched between internal and external operation.
Annotation concerning an OpenCom 130:
In contrast to the basic module, the expansion module does not provide any additional RJ45 jacks for external S
0
ports. Therefore you can also use the pressure terminals of the expansion module for an external S
0
port. The port assignment of the pressure terminals is changed when the switch is made from internal to external operation. This can be seen in the diagram.
Tip: Let us say you have activated an IAE on an internal S
0
port, for example. If you switch this S
0
port to external operation, you require a crossed ISDN line to connect the IAE to an NTBA. The
assignment of a crossed line is described in the chapter PBX
Networking under Direct Connection starting on page 130.
3.10.2 U
pn
Ports
Each of the U pn
ports enable the connection of a RFP 22/24 DECT base station or an OpenPhone 61, 63 or 65 telephone using a twin-wire cable.
Note: DECT base stations cannot be operated on the U pn ports of the basic module of an OpenCom 130. This is only possible for U pn
ports on the interface cards of the expansion module.
Note: Only the system telephones OpenPhone 61, 63 and 65 and the ISDN telephone OpenPhone 52 can be operated on the U pn
ports of an OpenCom 131. Operating a DECT base station is not possible on these U pn
ports.
47
Installation Port Assignment, Termination, Cable Lengths
The maximum permissible length of the twin-wire cable on a U pn
port is 500 m.
This line may only be laid inside buildings.
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 (these interface cards are available for an OpenCom 130/150).
The power consumption of each U pn
port is approx. 3 W.
S
0 int
2a 2b 1a 1b
U pn
/RFP with 1 U pn
1 2 3 4 5 6 7 8
RFP with 2 U pn
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
Pin assignment of the S
0
and U pn ports
3.10.3 a/b Ports
The a/b ports are for operating analogue devices (e.g. a fax machine, modem or telephone). The maximum permissible length of the cable is 1,000 m when twinwire 0.6 mm cable (with twisted pairs) is used.
Doorstation equipment can be activated on an a/b1 port (OpenCom 130,
OpenCom 131). In this case, an electronic switch enables the low-frequency voltage to be separated from the feed.
Tip: It is possible to operate analogue trunk lines with an additional interface card. Further explanations regarding this interface card can be found in the “M100-AT4 Interface Card” manual.
48
Installation Port Assignment, Termination, Cable Lengths
3.10.4 Actor/Sensor
In order to operate an entrance intercom and door opener, you need four twinwire cables:
■ one cable between the entrance intercom and the a/b1 port,
■ one cable between the door opener and the Actor1 port,
■ one cable between the intercom input and the Actor2 port 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.
A door station of the type “DoorLine” can also be operated on the OpenCom 100.
This intercom is connected via a “DoorLine” module to one of a/b ports of the
OpenCom 100 (see Intercom System (for a/b) starting on page 55).
3.10.5 LAN Port
The LAN port of the OpenCom 131 and the LAN port on the basic module of the
OpenCom 130 enables integration of the OpenCom 100 into an existing in-house
LAN by means of a 10 Mbit hub.
LAN ports on the expansion module of the OpenCom 130
The LAN ports on the expansion module (LAN0, LAN1 and LAN2) lead to the
Ethernet switch of the expansion module. These LAN ports support 10 Mbit/s and
100 Mbit/s transmission speeds in half- or full-duplex operation. The change in transmission rate and mode of operation is automatic (“auto-sensing function”).
The switch is also automatic for connections which require a crossed LAN line. For this reason, you can also use an uncrossed LAN line for a connection to another hub or switch.
LAN ports of the OpenCom 150
The technical characteristics of the OpenCom 150 LAN ports (LAN0 and LAN1) are similar to the LAN ports of the OpenCom 130 described in the previous section.
49
Installation Port Assignment, Termination, Cable Lengths
A LAN line (twisted-pair line in accordance with 10BaseT or 100BaseTX) can be up to 100 m long. Secure operation with 100 Mbit/s requires the use of category 5 lines and line sockets. Use a shielded Ethernet cable (STP cable, Shielded Twisted
Pair cable).
3.10.6 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 via an external switch or hub. The router subsequently converts the
PPPoE protocol to the TCP/IP protocol of the LAN.
OpenCom
TAE
DSL & Uk
0
S
0
Net
DSL
Splitter
TCP/IP &
PPPoE
DSL
Uk
0
NTBA S
0
PC
Crosslinked twisted pair cable
PPPoE
TCP/IP
DSL
Modem Hub Net
Connecting the OpenCom 100 to the network via ISDN and DSL
Connection of the DSL modem is via a crossover twisted-pair line. You can also use a switchable port on the hub, which is usually indicated by an “X”.
Note: If an expansion module is installed in an
OpenCom 130, you can also use the unused LAN2 port to activate the DSL modem. Due to the “auto-crossover” function, you do not require a cross-wired line with a LAN port of the expansion module. If you are operating this
OpenCom 130 as a slave system in a cascaded PBX, the LAN0 port on the expansion module of the slave system can be
used instead (see PBX Cascading starting on page 122).
50
Installation Power Failure
3.10.7 PCM Port
The PCM port is used cascade two communications systems together (see PBX Cas-
3.11
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 130/150 include an emergency service. In the event of a power failure, the external S
0
1 port is switched over to the
S
0
2 port so that you can still use a connected telephone to make a call.
Emergency operation on a system access is not possible.
3.12
Connectible Devices
The OpenCom 100 ports already offer a large number of possibilities for connecting devices. By installing additional interface cards (in an OpenCom 130/150) the number of ports can be increased as required.
One of the many possible configurations is shown in the following diagram.
51
Installation Connectible Devices
Hub
LAN
S
0
1 ext
R
NTBA
Sensor 1
Intercom/Relay
Intercom/Door opener
COM
R
S
0
2 int Actuator
1 + 2
U pn
1/2
U pn
3/4 a/b
1/2 a/b
3/4
Example of port assignment of the OpenCom 130 with terminals
3.12.1 Internal/External S
0
Ports
All S
0
ports can be operated externally, i.e. on an ISDN network termination unit.
The S
0
2 port of an OpenCom 130 and an OpenCom 131 can also be connected internally. S
0 ports on interface cards (available for an OpenCom 130 and
OpenCom 150) can also be switched external/internal. It is not possible to use both assignments simultaneously.
Up to eight devices per bus (ISDN telephones, ISDN fax machines, ISDN base stations, ISDN cordless telephones, ISDN adapters for the PC among others) can be connected to the internal S
0
ports by twin-pair cables. The power for three of these devices can be supplied by the bus; if more devices are used, they then require their own power supplies. The internal S
0
buses enable point-to-multipoint calls as per the DSS1 protocol (Euro-ISDN).
52
Installation Connectible Devices
3.12.2 U
pn
Ports
A system terminal can be connected to every U pn
port by a twin-wire cable.
The OpenPhone 61, OpenPhone 63 and OpenPhone 65 are cord-bound system terminals. The OpenPhones 63 and 65 can be cascaded on a U pn
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.
You can also operate the OpenPhone 52 ISDN terminal on a U pn
port.
The RFP 22/24 base station is required for the use of cordless system telephones
(e.g. OpenPhone 26 or OpenPhone 27). The OpenPhone 27 features an USB port on which you can transfer data and surf on the Internet.
Note: You can only operate DECT base stations on the ports of U pn
interface cards. These cards are available for an
OpenCom 130 and an OpenCom 150.
If this base station is connected to a U pn
port of an interface card, four simultaneous calls are possible with the mobile parts. If the base station is connected to two U pn
ports, eight simultaneous calls are possible. However, note that only as many external connections are possible as there are externally connected Bchannels available.
If you use a cordless handset such as the OpenPhone 26, this can also be contacted by other base stations using the GAP/CAP standard.
3.12.3 a/b Ports
The a/b ports a/b1 to a/b4 can be used for connecting analogue terminals. These can be for voice or data communication, and use DTMF or pulse dialling, e.g.
■ analogue telephones
■ class 3 fax machines
■ analogue modems (external or internal)
■ external devices for music on hold
53
Installation Connectible Devices
■ external voice mail systems.
Additional a/b ports can be provided by installing interface cards (on an
OpenCom 130/150).
Please note: Adhere to the following 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 OpenCom 100 offers an internal MoH, which you can load in the Web console Configurator in the SYS Configuration: Components menu. For details, refer to the online Help.
Please note: Use only devices with an input impedance of 600 ohms, floating connection, for external music on hold. Incorrect input impedance can cause irreparable damage to the
OpenCom 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
0
ports. For both port types the voice mail system can activate the notification for system terminals with the code procedures *68 resp. #68 .
54
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 when connecting:
■ The intercom system and the “DoorLine” module should be set to their factory settings.
■ In the PBX Configuration: Ports: a/b: Change menu in the Configurator, select
Doorstation 2-wire under Type. Activate the Actuator option, if you want to use the actor port of the OpenCom 100 instead of the “DoorLine” relay. The
“DoorLine” actor can be operated only when the speech channel is open at the same time. The internal actor can be operated at any time.
■ The “DoorLine” intercom system has a number of bell keys to which you can assign different call numbers in the PBX Configuration: Ports: Doorbell menu in the Configurator.
■ You can call the “DoorLine” intercom system by entering the code procedure
*102 .
■ The “DoorLine” intercom system can be connected to any a/b port. However, you can use only one “DoorLine” with the OpenCom 100.
For details on installing and configuring the “DoorLine” intercom system, refer to the product user guide.
The intercom system should be installed by qualified personnel only as sensor/ actor contacts will need to be connected to the “DoorLine” module.
3.12.4 Actor/Sensor Ports
manufactured by Siedle or Behnke.
55
Installation Connectible Devices a/b1
Relay
Actor2
Actor1
Door opener
Ts* b a
To
Ts
-T
+T
To
PVG 402-0
Amplifier
11
9
+ c1
7
LW
1
12
9
+
11
12
Siedle
Sensor
Door bell
NG 402-02
Ac adapter
230 V ~ b c
+
9
-
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”.
3.12.5 COM Port
By installing the V.24 interface card a serial port on the COM interface is provided.
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.
56
Installation Connectible Devices
3.12.6 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.
LAN ports on the expansion module of the OpenCom 130
The LAN ports of the Ethernet switches on the expansion module process Ethernet data traffic with different degrees of priority. You should therefore assign the three
LAN ports on the expansion module as follows:
■ LAN2: Use this port if you cascade a second communications system as a slave
system (see PBX Cascading starting on page 122).
■ LAN1: Here connect the short Ethernet connection line to the basic module.
■ LAN0: You should use the port with the lowest priority to connect to your corporate network.
Both internal LAN ports of the Ethernet switch are reserved for usage on interface cards.
LAN ports of the OpenCom 150
■ LAN1: Use this port if you cascade a second communications system as a slave
system (see PBX Cascading starting on page 122).
■ LAN0: You should use the port with the lowest priority to connect to your corporate network.
57
Accessories and Adapters U pn
Adapter
4.
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)”.
In the following you will find technical details on the add-ons and a list of compatible accessories.
4.1
U
pn
Adapter
The U pn
adapter is an adapter with a U pn
port for connecting another
OpenPhone 61, 63, 65 system telephone and a socket for an extra plug-in power supply.
Weight: 70 g
Dimensions: 73 x 60 x 30 mm
Power consumption: max. 195 mW
Cable length: max. 30 m
Please note: The U pn
adapter may be used only for connecting the system terminals listed above. The U pn
extension cable must not exceed 30 m in length and must not be used outdoors.
Note: An extra plug-in power supply is required to operate combinations of equipment with a power consumption that exceeds the power output of the U pn
ports.
4.2
a/b Adapter
You can use an a/b adapter to connect analogue terminals to the OpenPhone 63 and OpenPhone 65 system telephones.
Connecting an a/b adapter will result in exceeding the feed performance of the
U pn
port, regardless of the range. Therefore a plug-in power supply must be additionally connected to the a/b adapter.
58
Accessories and Adapters Audio Adapter
Note: Please use the plug-in power supply with the product code 4505759. The plug-in power supply for use in the UK has the product code 4510694.
Weight: 70g
Dimensions: 73 x 60 x 30 mm
Power consumption: max. 160 mW
Cable length: max. 3 m
4.3
Audio Adapter
The audio adapter is an adapter extension with four different ports for external audio and signalling devices.
Weight: 70g
Dimensions: 73 x 60 x 30 mm
Power consumption: max. 260 mW (with relay active).
Audio Adapter Pin Assignment
Port
1
2
3
4
Used for Socket
Ear cap, second handset, headset, active speaker or microphone
RJ-10
(4-pin
Western socket)
Recording device; relay contact generates signal for starting and stopping recording.
Stereo jack,
3.5 mm
Not used on
OpenCom 100
Door display
Round power socket
(4 mm)
RJ-11 or
RJ-12
(6-pin
Western socket)
Assignment
1: microphone -
2: speaker +
3: speaker -
4: microphone +
1 (GND): recording signal, relay contact 1
2 (peak): recording signal +
3 (ring): relay contact 1
-
4, 5: relay contact 2
1, 2, 3, 6: NC
59
Accessories and Adapters Approved Devices / Approved Accessories
Electrical Data of Ports
Port
Microphone, microphone of second handset, headset microphone
Ear cap, loudspeaker of second handset, headset, headset loudspeaker
Active speaker
Recording device audio input
Recording device start/stop
(relay contact 1)
Door display
(relay contact 2)
Connection Values
Electret microphone
Typical sensitivity: 10 mV/Pa
Power feed: I < 300 µA at 1.5 V
Typical impedance: 150 ± 30 ohms
Typical sensitivity: 94 dB/1 mW
(0 dB = 20 µPa)
Max. output voltage: 1 V rms at input impedance > 10 kohms
Typical input sensitivity: 0.24 mV
(microphone level)
Max. switching voltage:
50 VDC/29 V AC
Max. switching current: 1 ADC/0.7 A AC
Max. switching voltage: 50 VDC/29 V AC
Max. switching current: 1 ADC/0.7 A AC
4.4
Approved Devices / Approved Accessories
Please note: Only the following, recommended accessories may be connected to the audio adapter. The cable to the door display must not be run outdoors.
The following devices are recommended:
Type
Headset:
Headset adapter cable:
Second handset
Handset
Manufacturer, Product Designation
GN-Netcom, Profile binaural
(1869-00-03)
GN-Netcom, Profile 3-in-1 (1866-00-04)
GN Netcom, QD cable (quick coupling), smooth, Mod 4 (8800-00-01)
Siemens, L30351-F600-A366
DeTeWe, OpenPhone 60
60
Accessories and Adapters Device Combinations
The following devices are recommended:
Type
Microphone:
Loudspeaker:
Recording device:
Manufacturer, Product Designation
Winfinity, 4511326 / H 282-18
Siemens, L30460-X1278-X
No recommendation
4.5
Device Combinations
You can use the following power values to calculate the power consumption of combined equipment:
■ U pn
adapter: 195 mW
■ Audio adapter: 260 mW
■ a/b adapter: 160 mW
(must be combined with a plug-in power supply!)
■ OpenPhone 61: 1,000 mW
■ OpenPhone 63: 1,025 mW
■ OpenPhone 65: 1,140 mW
■ Up to three add-on keypads: 330 mW
These symbols are used in the following tables:
● This combination is possible.
❍ Reduced tone ringing, open listening and hands-free talking volume possible.
61
Accessories and Adapters Device Combinations
Configurations without Plug-in Power Supply
(Range up to 500 m)
The following table shows examples of equipment combinations for which the maximum power consumption of 2.4 W is not exceeded.
Basic Unit: OpenPhone 63
–
–
–
●
Add-ons
Audio adapter
–
Second Terminal Power
–
●
●
U pn adapter Up to 3 keypad modules
– –
–
–
–
● –
–
–
OpenPhone 61
OpenPhone 63 without adapter
1025 mW
1285 mW
2220 mW
2245 mW
OpenPhone 65 without adapter or keypad module
2360 mW
Basic Unit: OpenPhone 65
–
–
–
●
Add-ons
Audio adapter
–
–
Second Terminal Power
–
●
●
–
–
U pn
adapter Up to 3 keypad modules
–
●
●
–
–
❍ –
–
–
–
OpenPhone 61
1140 mW
1470 mW
1730 mW
2335 mW
OpenPhone 63 without adapter
2360 mW
OpenPhone 65 without adapter or keypad module
2475 mW
62
Accessories and Adapters Device Combinations
Configurations without Plug-in Power Supply
(Range 500 to 1000 m)
The following table shows examples of equipment combinations for which the maximum power consumption of 2.2 W is not exceeded.
Basic Unit
OpenPhone 63
OpenPhone 65
Add-ons
–
●
Audio adapter
●
Power
–
–
U pn
adapter Up to 3 keypad modules
–
–
●
●
1285 mW
1470 mW
1730 mW
Configurations with Plug-in Power Supplies
The following table shows examples of equipment combinations operating with additional power from a plug-in power supply.
Basic Unit: OpenPhone 63
Add-ons:
Up to 3 keypad modules
Audio adapter
U pn
adapter and plug-in power supply
Second terminal (OpenPhone, OP)
OP 61 OP 63 without adapter
OP 65 without adapter and with 1 keypad module
●
●
●
●
●
●
63
Accessories and Adapters Device Combinations
●
●
●
●
●
●
Basic Unit: OpenPhone 65
Add-ons:
Up to 3 keypad modules
Audio adapter
U pn
adapter and plug-in power supply
Second terminal (OpenPhone, OP)
OP 61 OP 63 without adapter
OP 65 without adapter and with 1 keypad module
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
64
S
2M
Connector Module
5.
S
2M
Connector Module
The S
2M
connector module allows you to operate an OpenCom 130/150 on a primary rate access. This access provides up to 30 voice channels. You can also use the S
2M
port to network two systems, e.g. in order to use the OpenCom 130/150 as a subsidiary system or DECT server.
Note on DECT applications in conjunction with S
2M
If an S
2M
connector module is installed in the OpenCom 130/150, please consider the following restriction for DECT applications:
It is not sufficient, to install a U pn
interface card (e.g. “4 x U pn
”) into slot 2 (or into slot 3 with the OpenCom 150). In every case, you need to run a U pn
interface card
(“4 x U pn
”, “8 x U pn
” or “2 x S
0
and 6 x U pn
”) in slot 1 in order to operate DECT applications properly.
Note: The maximum cable attenuation between the
OpenCom 130/150 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.
Default setting
S
2M
U pn 1
U pn
2+3 S
0
2 a/b
3+4
Sensor
1+2
Sensor
3
RJ45
S
0
1
RJ45
S
0
2 a/b
1+2
LAN Actuator
1+2
DC in
V.24
Location of the S
2M
port on the basic module of the OpenCom 130
65
S
2M
Connector Module Installation
V.24
Actuator
1+2 3+ 4
Slot 1
S
0
1 S
0
2 1-1 1-2 S
0
1
Slot 2
2-1 2-2
Slot 3
3-1 3-2
Slot 4
4-1 4-2
Slot 5
5-1 5-2
1+2 Sensor 3+4
Door
1+2
S
2M
S
0
3 S
0
4
1-3 1- 4
1-5
S
0
2
2-3 2-4
2-5
3-3 3-4 4-3 4-4
3-5 4-5
5-3 5-4
5-5
Location of the S
2M
port on the OpenCom 150
5.1
Installation
Please note: The module should only be installed by trained personnel.
DANGER!
The device contains hazardous voltages.
1. Pull out the mains plug of the OpenCom 130/150.
2. Open the housing of the OpenCom 130/150.
3. On the module board, remove the protective covers of the two S
2M
slots (A) and (B).
S
2M
slots
B
A
Activity LED
PCM LAN 1 LAN 2
Position of the S
2M
slots on the module board
66
S
2M
Connector Module Installation
4. Insert the S
2M
module into the slots, making sure you insert the LED side of the module into the upper slot (B).
3 4
1 2
S
2M
LEDs
S
2M
slot
(Underside of the module board)
Position of the LEDs on the
S
2M
module
5. Wire the S
2M
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 130/150 to the TX lines of the other
PBX).
PBX 1, S
2M
Rx+ RxTx+ Tx-
Rx+ RxTx+ Tx-
PBX 2, S
2M
(Pressure clamps)
Example of the wiring of the S2M port for two OpenCom 130/150s
67
S
2M
Connector Module Configuration
On the OpenCom 150 the pressure terminal is a 5-pin connector. The additional terminal is used to connect the shielding of a shielded line. The shielding has to be stripped as short as possible (approx. 3 mm).
6. If necessary, check to make sure that the NT is fed by its own power supply.
7. Reconnect the OpenCom 130/150 to the power supply.
8. Configure the S
2M
module in the Configurator of the OpenCom 130/150 (refer
to Configuration starting on page 73). Check the level 1 status with reference to
the LEDs on the module. None of the LEDs are illuminated before the S
2M module has been configured.
LED
1 (green)
2 (green)
3 (yellow)
4 (red)
Meaning
Synchronous (= ok)
Blue alarm
Remote alarm or out of sync
(yellow alarm)
Loss of signal (red alarm)
9. Pull out the mains plug of the OpenCom 130/150 again and close the housing.
10.Reconnect the OpenCom 130/150 to the power supply.
5.2
Configuration
The menu item S
2M
appears in the Configurator, menu PBX Configuration: Ports after installation of the S
2M
module. Configure the port in the input mask of this menu item. Further information on this can be found in the online help.
68
Mounting the OpenCom 150 Rack InfoCom System Safety Precautions
6.
Mounting the OpenCom 150 Rack
InfoCom System
The OpenCom 150 is also available as rack version for mounting in a standard
19" EIA rackmount cabinet.
OpenCom 150 Rack Frame and Ports
6.1
Safety Precautions
The system needs to be mounted in earthed cabinets or cases. Lines and cables connected to the communications system must only be laid inside buildings.
Use a shielded Ethernet cable (STP cable, Shielded Twisted Pair cable) to connect the OpenCom 150 to a Local Area Network (LAN).
The ambient temperature of the OpenCom 150 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.
69
Mounting the OpenCom 150 Rack InfoCom System Technical Data
6.2
Technical Data
(only if different from the OpenCom 150)
Dimensions:
– Width: 19-inch panel with flange for mounting in installation cabinet
–Height: 3U
– Depth: approx. 340 mm
Weight: approx. 7.8 kg
Connection of 230 VAC power supply on rear side via inlet connector for nonheating apparatus
Connection of all ports via RJ 45 jacks on front panel
Note: The ISDN S
0
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
0
internal port (for two S
0
terminals on the same bus) may severely limit the range of the S
0
bus.
70
Mounting the OpenCom 150 Rack InfoCom System Pinning of RJ 45 Jacks
6.3
Pinning of RJ 45 Jacks
U pn
, a/b
Intercom
Sensor
Actor
S
0
S
2M
100 Base-T
Pin 4-5
Pin 3-4 (Door 1)
Pin 5-6 (Door 2)
Pin 1-2 (S1)
Pin 3-4 (S2)
Pin 5-6 (S3)
Pin 7-8 (S4)
Pin 1-2 (A1)
Pin 3-4 (A2)
Pin 5-6 (A3)
Pin 7-8 (A4)
Pin 4-5, 3-6
Pin 4-5, 1-2
Pin 1-2, 3-6
For each of the 5 slots, there is a corresponding port field with several RJ 45 sockets on the front panel. The port fields are labelled “SLOT 1” to “SLOT 5”.
Depending on the type of interface card used in a slot, the meaning of the corresponding RJ 45 sockets changes:
Label
S0 1..4
(Slot 1, 2 & 3)
SUBSCRIBER 1..8
(Slot 1, 2 & 3)
SUBSCRIBER 1..6
(Slot 1, 2 & 3)
Interface Card
2 x S
0
+ 6 x U pn
2 x S
0
+ 6 x a/b
4 x S
0
4 x U pn
8 x U pn
4 x a/b
8 x a/b
2 x S
0
+ 6 x U pn
2 x S
0
+ 6 x a/b
Ports
S
0
1, S
0
2
S
0
1, S
0
2
S
0
1 ... S
0
4
U pn
1 ... U pn
4
U pn
1 ... U pn
8 a/b1 ... a/b4 a/b1 ... a/b8
U pn
1 ... U pn
6 a/b1 ... a/b6
71
Mounting the OpenCom 150 Rack InfoCom System Scope of Delivery
Label
SUBSCRIBER 1..8
(Slot 4 & 5)
Interface Card
4 x a/b
8 x a/b
AT 1..4 (Slot 3, 4 & 5) M100-AT4
Ports a/b1 ... a/b4 a/b1 ... a/b8 a/b1 ... a/b4
An overview of the interface cards can be found under the heading OpenCom 150
(5 Slots) starting on page 43.
For each of the five slots, there is a LED on the front panel of the OpenCom 150.
These LEDs are labelled SLOT1..SLOT5. An LED will show a constant light, if an interface card is inserted into the corresponding slot and the operating software has detected an interface card. An LED will blink, if an error condition was detected.
6.4
Scope of Delivery
■ One communications system OpenCom 150 Rack
■ One AC adapter with connection cable
■ One set of short user guides
■ One CD
Note: Note for the DeTeWe installer: Please download and install the latest released software from our Web site/partnership area.
72
Configuration
7.
Configuration
Configuration and programming of the OpenCom 100 is performed by the Confi-
gurator, a special software application integrated into the system. The Configu-
rator is operated via the Web console, which can be run on any PC connected to the OpenCom 100.
The OpenCom 100 Web console (this screenshot: OpenCom 150)
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 Online Help starting on page 78).
73
Configuration Brief Guide to Initial Configuration
Note: In order to use all the new system software functions, we recommend that you download the latest software from our Web site at http://www.aastra-detewe.de.
For the initial configuration you can connect the PC to the OpenCom 100 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 Configurator from there.
Note: To avoid problems with existing network installations, the OpenCom 100’s DHCP server is designed for static address assignment in its factory settings. The
OpenCom 100’s IP address is always168.99.254 in its factory settings.
7.1
Brief Guide to Initial Configuration
Setting up a first connection is quite simple with a standard Windows PC:
1. Connect the PC’s network card with one of the OpenCom 100.’s LAN ports Use a cross-wired Ethernet cable to do this. You can also use an uncrossed Ethernet cable for a connection via a LAN port to the OpenCom 130’s expansion module.
2. Windows 2000/XP: log on as a user with “Administrator” rights.
3. You will find the IP settings in Windows 2000/XP under Start: Settings:
Network connections: Local Area Connection. Open the dialogue box Local
Area Connection Properties, and then the dialogue box Internet Protocol
TC/IP Properties (see figure: Setting the IP address in Windows XP on page 75).
4. Note down the existing settings so that you can restore them after completing the initial configuration.
5. Change the IP Address to 192.168.99.253. Change the subnet mask to
255.255.255.0, confirm with OK and Close.
6. Start a Web browser and in the address field enter “http://192.168.99.254/”.
The Web console’s log-on page will be displayed. Enter the user name “Administrator” without a password for the initial configuration. To support your next confi-
74
Configuration Brief Guide to Initial Configuration guration steps, you should activate the Assistant mode on the entry page of the
Configurator. Please also pay attention to the online help.
Setting the IP address in Windows XP
Tip: To find out the IP address of the Web console, enter the code digit procedure *182 on a connected system telephone. You can also view the net mask by entering the procedure *183 . The PC’s IP address must be in this network range.
Note: Deactivate any connection via a proxy server which has been configured. Open the Internet Explorer, go to the menu Extras and open the Internet options dialogue box.
Select the Connections register and deactivate the Proxy
Server.
75
Configuration Configuring the OpenCom 100
7.1.1 First Configuration via Serial Port
The serial port can also be used as alternative access for the first configuration. To do this, the V.24 interface card must be installed. Additionally, you require a crossed serial line with RJ45 plug (“null modem”).
1. Install the “occonfig” program from the product CD. To do this, you must log on as an administrator under Windows NT or Windows 2000/XP.
2. Shut down the PC. Remove all connected network leads. Connect the serial port of the PC to the COM port of the OpenCom 100.
3. Restart the PC. Set up a dial-up link with the icon configured on the desktop under step 1. Enter “Administrator” without a password as your user name.
4. Start the Web browser. Enter “http://192.168.99.254/” in the address box.
You will see the log-on page of the Web console. Enter the user name “Administrator” without a password for the initial configuration.
7.2
Configuring the OpenCom 100
7.2.1 Preparing the Configuration
Before starting with the configuration, make sure you have the following documents at hand:
■ An overview of the ports
■ A list of the terminals to be connected
■ A list of the IPEIs, if you wish to log on DECT terminals in the secure procedure
■ A list of the users to be set up (staff entitled to use the services of the
OpenCom 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.
76
Configuration Configuring the OpenCom 100
Data not available for initial configuration can be updated or corrected at a later date.
Note: Use the Configuration Guide starting on page 169. This
will assist you in making the settings in the correct sequence.
7.2.2 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 Confi-
guration: LAN 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.
OpenCom 100 (this screenshot: OpenCom 150): log-on dialogue box
3. To commence configuration, you must first log on. For the initial configuration, enter your:
77
Configuration Configuring the OpenCom 100
- 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 100 and the users.
OpenCom 100 (this screenshot: OpenCom 150): dialogue box for initial access
5. The software opens a dialogue for initial access. Determine an administrator password and enter it in this dialogue. Also fill in the other input fields.
6. Confirm your input with Apply.
7. Click on the Configurator button on the home page.
You will find notes on using the Configurator and in the online help. Click on Help in the menu bar or click on TOC to activate an overview of help topics.
7.2.3 Loading the Online Help
The online help can now be loaded in the Configurator:
1. Go to the SYS Configuration: Components menu. Select the entry Online
Help and click on Browse.
78
Configuration Configuring the OpenCom 100
2. Look for one of the language-specific ZIP files in the OLH directory of the product CD. Confirm your choice by clicking on Open.
3. Then click on Load to transfer the online help to the system.
Please note: After completion of the loading operation, the system will take a few minutes to analyse the transferred file.
Note: You can download the latest version of the online help from http://www.aastra-detewe.de/.
7.2.4 Finishing the Configuration
1. When you have completed all the settings in the Configurator, you must save
the configuration (see also Saving and Loading the Configuration on page 82).
2. Then select the Log-off command in the upper menu bar.
7.2.5 Preconfiguration
Configuration of the OpenCom 100100 can be prepared at your DeTeWe Customer
Service Centre or by an authorised DeTeWe dealer. For this purpose, a
OpenCom 100100 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 100100 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.
7.2.6 Offline Configurator
With the aid of the offline configurator a configuration for the system can be issued and created on a Windows PC. Thereby most of the configuration points are available. Each system type of the product family and firmware version release 7.0 or higher, has its own offline configurator; this is managed with the aid of a starter program. The starter program is included on the product CD. The operating systems Windows 2000 and XP are supported.
79
Configuration Configuring the OpenCom 100
You can find further information in the chapter PC Offline Configuration starting on page 158.
7.2.7 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 entered on the
PBX Configuration: System: Remote service menu page in the Configurator and the Status option is activated, remote configuration access is then activated when a data call from one of the entered MSNs is registered.
The customer service centre/authorised dealer can then log into the
OpenCom 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.
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 #
80
Configuration Configuring the OpenCom 100
Activation is automatically cancelled 30 minutes after the last configuration activity.
Note: During remote configuration, 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 Configuration: Firmware menu in the Configurator).
For security reasons, settings in the Configurator, Net Configuration should only be edited on site to avoid malfunctions or failures in the customer’s LAN (e.g. due
explained.
Forced logoff of another user by the administrator
The configuration of the system can always only be edited by one user. Working on the configuration in parallel is not possible. This ensures that no configuration conflicts arise.
If the user “Administrator” logs in and another user with administration rights is already logged in, then the administrator can forcibly log the other user off in order to configure. This functionality, for example can be used, when configuring remotely, when a user has forgotten to log out.
In order to forcibly log a user off:
1. The “Administrator” user logs on with the administration password.
2. They open the Configurator.
A message shows which user is currently configuring the system.
3. The administrator clicks on the Take over config rights button.
The other user can make no further modifications of the configuration.
81
Configuration Configuring the OpenCom 100
7.2.8 Codes for IP Configuration
The IP configuration of the OpenCom 100 is performed on the Web console in the
Configurator, in the NET Configuration: LAN menu.
In the event that the IP configuration of the OpenCom 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.
Set IP address
H *182 Z (system PIN) *
Z (www) * Z (xxx) * Z (yyy) * Z (zzz) #
Set NET mask
H *183 Z (system PIN) *
Z (www) * Z (xxx) * Z (yyy) * Z (zzz) #
Example
Enter: H*1830000*192*168
*99*254#
If required, initiate a system restart with this procedure:
H * 1 8 5 Z (system PIN) #
Use the PIN you entered in the dialogue box for initial access. The factory setting is
“0000”.
7.2.9 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
82
Configuration Configuring the OpenCom 100
■ Telephone book entries
■ LCR tables
For further information, refer to the online help documentation under the topic
SYS Configuration: Data backup.
7.2.10 Receiving System Messages as E-Mail
Important events and errors are kept by the OpenCom 100 in an internal log book: the error store. To inform or alert the system administrators, entries in the log book
(system messages) can be sent via e-mail.
In order not to notified of every error, the administrator can define corresponding log filters (in the Configurator, the LOG Configuration: LOG Filter menu). These filters define which errors (category, severity, number per time interval) should be notified. The e-mails always include an internal event or error number, as well as an explanation of the message. Further, extra parameters (such as the port number when a trunk line drops out) are also provided.
The mail account for this service (Account for LOG filter) is configured in the Con-
figurator, NET Configuration: E-Mail Access.
7.2.11 Loading SW Updates
New versions of the system and terminal software can be loaded to the system.
New software versions of the OpenCom 100 are loaded from the configuration PC, which accesses the Configurator (see the SYS Configuration: Firmware menu).
For information on connecting a configuration PC, see Brief Guide to Initial Configu-
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.
83
Configuration Configuring the OpenCom 100
For further information, refer to the online help documentation under the item
SYS Configuration: Firmware.
7.2.12 Resetting the System Data
You can restore the factory settings of the OpenCom 100 in the Configurator. If this
is not possible, refer to the next section entitled Basic Hardware Settings Switch.
Please note: If this is done, all individual settings and the user data are then lost. For this reason, you should back up your configuration regularly, the best time to do so being after every
change. For details, refer to the chapter entitled Saving and
Loading the Configuration starting on page 82 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.
7.2.13 Basic Hardware Settings Switch
The OpenCom 100 configuration can also be returned to the factory settings by means of the basic hardware settings switch.
Please note: If the factory settings are restored, all customer settings and user data will be lost.
To restore the OpenCom 100 basic settings, proceed as follows:
1. Switch off the OpenCom 100 by disconnecting the power plug and the plug-in power supply of the basic module (OpenCom 130).
2. Remove the cover.
84
Configuration
CAUTIONT!
Configuring the OpenCom 100
Static charges can damage electronic devices. Observe the regulations regarding electrostatically sensitive components.
3. The basic settings switch is designed as a key switch. The location of the switch
can be found in the chapter entitled Interface Cards starting on page 40. Press
and hold the switch.
4. Replace the power plug in the mains socket. Wait about 30 seconds until the indicator on the front of the OpenCom 100 constantly flashes.
5. Disconnect the power plug from the mains socket again.
6. Release the key switch.
The system data is now reset.
7. Replace the power plug in the mains socket.
The OpenCom 100 will now reboot 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 77). Con-
figure the OpenCom 100 (possibly by loading a saved configuration; see Saving
and Loading the Configuration on page 82).
7.2.14 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.
85
Configuration Configuring 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). The maximum allowable size for a MoH file is 256 KB
(approx. 32 sec. play time). If a larger file is loaded then this will be “truncated” and thereby will also only be played for 32 seconds. The MoH capacity can be subdivided in a maximum of 5 files. These files can be used for different companies or for internal and external calls.
Note: If you don't have the Sound Recorder program or the appropriate codec on your Windows operating system, you should install these components from your Windows CD.
Load your MoH file in the Web console's Configurator, in the SYS Configuration:
Components menu.
Note: When generating your own MoH file, you may incur a fee for the use of non-resident melodies (e.g. a GEMA fee in
Germany or MCPS fee in the UK). The MoH files that come with your OpenCom 100 can be used free of charge.
86
Configuration Examples OpenCom 100 in Computer Networks
8.
Configuration Examples
8.1
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:
■ the OpenCom 100 Configurator
■ call charge administration
■ the OpenCTI 50, with which telephone functions can be used on a PC
■ the OpenCom 100 central telephone book and your personal telephone book as well as to the company telephone book (if the multi-company variant is activated).
In addition, the OpenCom 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.
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.
Note: Several menu entries mentioned in this chapter are available only, if you switch on the Level: Expert in the top level dialogue of the Configurator.
87
Configuration Examples Introduction to TCP/IP
The following LAN prerequisites are possible:
Server configuration in the LAN
No IP server present
IP server present
DHCP server present
IP server present
No DHCP server present
OpenCom 100 Functions
OpenCom 100 functions automatically as DHCP and DNS server
OpenCom 100 functions automatically as DHCP client
System Administrator must assign IP address and DNS name for
OpenCom 100
Special case when integrating the
OpenCom 100 in a LAN; settings in the
NET Configuration: LAN menu must be coordinated with the responsible system administrator
8.2
Introduction to TCP/IP
In a single LAN it is possible to use various protocols for the transmission of data.
The connection between a workstation computer and the OpenCom 100 runs via the IP protocol (also named TCP/IP) used on the Internet. IP can be used together with other protocols (e.g. NetBEUI, AppleTalk or IPX/SPX) on the same network.
Every device participating in data transmission using IP requires a unique IP address. An IP address consists of four groups of digits from 0 to 255, each separated by a full stop. The supplementary protocols DHCP and PPP automatically assign IP addresses to devices. Class C networks normally use IP addresses in which the first three numbers are the same and the last number is uniquely assigned to a specific device in the LAN. On the Internet, unique addresses assigned by a special organisation created for this purpose are used. Within a LAN, you can use addresses which are not unique world-wide:
IP Range
192.168.0.0-
192.168.255.255
Common Netmask
255.255.255.0
172.16.0.0-172.31.255.255
255.240.0.0
10.0.0.0-10.255.255.255
255.0.0.0
Comment
256 smaller networks
1 medium network
1 large network
88
Configuration Examples OpenCom 100 in a Serverless LAN
IP enables the establishment of connections via one or more intermediate stations. The decision whether to connect directly or indirectly to the partner device depends on the network mask. The network mask for a class C network is
255.255.255.0. If the IP address of the partner device does not fit the network mask, the connection is established via the default gateway. If a device knows several data routes to different intermediate stations, one speaks of a router.
The domain name system (DNS) resolves a plain text DNS name into an IP address.
The DNS is a hierarchically structured database, distributed worldwide. A DNS server can supply information on the names and IP addresses for which it is responsible. For all other information, a DNS server contacts other DNS servers. For the establishment of every connection from the workstation, it is possible to give either an IP address, or a name that a DNS server resolves into an IP address.
Note: For further explanations of technical terms, refer to the Glossary on the CD supplied.
8.3
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 or switch. Such networks do not require special servers. This configuration example is also valid for a LAN with a server using a protocol other than IP
(e.g. AppleTalk or IPX/SPX).
ISP
(DNS)
S
0
OpenCom
(DHCP, RAS, int. DNS, Internet)
S
0
Net
Ext.
PC
PC 1 PC 2
S
0
Net Hub Net
The OpenCom 100 in a serverless LAN
In a serverless LAN, the OpenCom 100 takes over the IP configuration of the connected workstations. All IP settings necessary for the workstations are assigned by
89
Configuration Examples OpenCom 100 in a Serverless LAN the OpenCom 100 via DHCP (dynamic host configuration protocol). In this operating mode, an IP address space reserved for such networks is used:
192.168.99.254
255.255.255.0
192.168.99.254
192.168.99.254
OpenCom 100 IP address
Network mask (class C network)
DNS server IP address
Default gateway IP address
Install the IP network protocol and a Web browser for every workstation which is to have access to the OpenCom 100 network features.
8.3.1 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 Configurator home page can be called up.
In a peer-to-peer network (Windows network), the workstations each have a name which is displayed in the network environment. These NetBIOS names can differ from the DNS names assigned to the workstations by the OpenCom 100. The
OpenCom 100 is not visible in the network environment.
8.3.2 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.
90
Configuration Examples OpenCom 100 in a Serverless LAN
Note: Workstation PCs automatically add a domain name to
URLs without a dot. You specify this domain name in the
Configurator. For example, if you have configured
“firm.co.uk” as the domain name, an access request for
“www.firm.co.uk” will be interpreted as a local DNS request which does not lead to the establishment of an Internet connection. For this reason, you should choose a name which is not used in the Internet as the domain name (“firm-opencom.co.uk” for example).
8.3.3 RAS Access
You can establish a connection to the OpenCom 100 from an external PC via an
ISDN card.
The necessary IP settings are transmitted by the OpenCom 100 on establishment of the connection. The computer that has dialled in has access to all services in the
LAN that can be used via the IP protocol. The authorisation for RAS access is set up in the Configurator via the User Manager: User Groups menu.
The technical properties of the connection can be configured in the Configurator via the NET Configuration: RAS menu. Further information can be found in the online help of the web console.
In a serverless LAN, Windows uses the NetBIOS protocol for accessing files and printers via the network environment. NetBIOS can use NetBEUI, IPX/SPX or IP as the transport protocol. In the network environment, you can only access files and printers on workstations using IP for NetBIOS.
91
Configuration Examples OpenCom 100 in a LAN with an IP-enabled Server
8.4
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)
S
0
OpenCom
S
0
Net S
0
int
Server
(DHCP, RAS, int. DNS,
Internet)
S
0
Net
PC 1 PC 2 Ext.
PC
S
0
Net Hub Net
The OpenCom 100 in a LAN with an IP-enabled server
In many cases, an IP-enabled server configures the IP settings via DHCP for all workstations. On starting, the OpenCom 100 requests IP settings via DHCP. If this request is responded to, the OpenCom 100 uses the IP settings received. You can then use a workstation to access the OpenCom 100 Configurator under the IP address assigned by the server.
In networks in which the IP settings are made manually, you have to enter the corresponding IP settings in the OpenCom 100 Configurator (NET Configuration:
LAN menu). Here the OpenCom 100 acts as the DHCP server. A workstation requesting the IP settings via DHCP then receives the settings you made in the
Configurator.
8.4.1 DNS Name Resolution
In a LAN with an IP-enabled server, the latter is also responsible for DNS name resolution. If you want to start the Configurator by entering a DNS name, you must link this name on the server with the IP address used by the OpenCom 100.
For further information, refer to the server documentation.
92
Configuration Examples OpenCom 100 in a LAN with an IP-enabled Server
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.
8.4.2 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.
ISP
(DNS)
S
0
OpenCom
(Internet)
S
0
Net S
0
int
Server
(DHCP, RAS, int. DNS)
S
0
Net
Ext.
PC
PC 1 PC 2
S
0
Net Hub Net
The OpenCom 100 as a DNS server in a LAN with an IP server
93
Configuration Examples OpenCom 100 in a LAN with an IP-enabled Server
8.4.3 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: RAS: ISDN menu, under Address Range.
ISP
(DNS)
OpenCom
(RAS, Internet)
Server
(DHCP, int. DNS)
Net S
0
S
0
Net
Ext.
PC
PC 1 PC 2
S
0
Net Hub Net
RAS access by the OpenCom 100 in a LAN with an IP server
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.
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 with ISDN. For this reason, you enter the address of a WINS server manually in the network settings of the workstation.
94
Configuration Examples Branch Link
8.5
Branch 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 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.99.254,
Net=192.168.99.0)
Net S
0
OpenCom
(IP=192.168.11.254,
Net=192.168.11.0)
S
0
Net
PC 1 PC 2 PC 1 PC 2
Net Hub Net Net Hub Net
The OpenCom 100 in a LAN-to-LAN link
In the Configurator, NET Configuration: Branch menu you can configure the dial-in settings. The OpenCom 100 will set up a connection whenever a IP data transfer to the other LAN is requested.
Note that such a connection is only set up when specific requests are made. These can be for FTP file transfers, e-mails or downloading Web pages. Name resolution via broadcasts is not possible. If you wish to use the LAN-to-LAN link to access files and printers in the Windows network, you need an IP-enabled server that administers the name resolution for the Windows network.
As the IP address range, you can select one of the 256 class C subnetworks designed for local LANs. Select a class C sub-network in the range from 192.168.0.0 to 192.168.255.0.
95
Configuration Examples Useful Information on Internet Access
8.6
Useful Information on Internet Access
8.6.1 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
TM
XP
TM
operating system, various multimedia programs such as Realplayer
TM
and anti-virus applications that may establish an Internet connection for automatic updates (the so-called “phone home function”).
It is therefore highly advisable to limit ISP access by specifying the maximum monthly connection time under Connection time per month (maximal) in the
NET Configuration: WAN: [Provider] menu on the web console.
8.6.2 Using the Web
A Web browser not only enables you to use the OpenCom 100 Configurator from every workstation but also to obtain a wealth of information from the Internet.
Simply enter the desired URL in the address field of the browser. Access from a stand-alone PC via an online service differs from Internet access via the
OpenCom 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.
96
Configuration Examples Useful Information on Internet Access
■ The OpenCom 100 can block access to certain Web pages by means of filter lists.
8.6.3 E-mail
One of the most important services in the Internet is e-mail. E-mails are buffered in individual e-mail accounts on a mail server. Mail servers are operated by ISPs for example. With the OpenCom 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. OpenPhone 6x and
OpenPhone 2x system terminals can also display information such as the sender or the subject of the e-mail.
8.6.4 NAT
Network address translation (NAT) is activated on accessing the Internet (ISP). You require this feature in order to translate internal IP addresses to valid external IP addresses. This has three important consequences for Internet access:
■ Several workstations can share a single Internet access. You do not require a
LAN access, only a single account with the Internet service provider.
■ The IP addresses used in the LAN are translated into IP addresses valid worldwide. So you require no such addresses for your LAN.
■ Only IP connections triggered from a workstation can be established. Consequently, while you can call up Web pages from a workstation, you cannot install a Web server visible in the Internet on a workstation.
Certain protocols cannot be used when NAT is being used. This affects protocols with the following properties:
■ IP addresses are transported in the useful load, e.g. NetBIOS over IP or SIP.
■ The protocol requires an active, inward-directed connection establishment, e.g. ICQ.
97
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), CuSeeMe (“videoconferencing”), IRC (“chat”), ICMP errors (“traceroute”) and ICMP echo (“ping”).
Depending on the internet telephony protocol (VoIP, SIP) the required NAT extension (“Full Cone NAT”) or RTP-Proxy is activated on the Media Gateway Card.
Protocols which require inward-directed connection establishment can be configured in the Net Configuration: Port Access menu. For further information, refer to the online help of this menu.
98
Voice over IP (VoIP)
9.
Voice over IP (VoIP)
The term “Voice over IP” describes the usage of IP-based data networks for telephony. It is possible to distinguish between two different types of VoIP:
■ Telephony via Internet provides cheaper charge-models for telephone services.
For telephony directly via the Internet, only the cost of data transmission is incurred. Various Gateway providers can provide crossover into the PSTN
(“Public Switched Telephone Network”) for a fee. As well as standardised protocols such as SIP and H.323, proprietary protocols such as the Skype network, are used. optimised for data communication Voice and service quality via
Internet, is often indeterminable because you are dependent on the routes of various service providers. which have been optimised for data communication
■ Telephony via Intranet enables joint usage of existing infrastructure for telephony and for data communication. Integrating the two communication networks into a single communications network can provide considerable savings.
The OpenCom 100 gives users all the features of system telephony through its use of an IP-based protocol. The control of the data connections used makes it possible to define exactly the voice and service quality.
Telephony over the Internet using the OpenCom 100 provides you with the fol-
lowing options (see also SIP Telephony starting on page 107):
■ You can use low-cost “SIP trunk lines” with your existing Internet connection
■ You can use the services of a SIP gateway service provider to access the public telephone network (PSTN)
■ Automatic fallback (bundle overflow) to ISDN connections in case of the breakdown or over-occupancy of the SIP connection
■ With a M100-AT4 interface card (4 analogue trunk lines) you can also use the external IP Gateway 1 for SIP telephony
VoIP system telephony with the OpenCom 100 offers the following possibilities:
■ Use of IP-based system telephones connected to Cat5 twisted-pair ethernet cables
■ Use of IP-based system telephones via VPN, RAS, Branch or WLAN connections
99
Voice over IP (VoIP) Fundamentals
■ Using voice-data compression with compressing codecs, it is also possible to make multiple IP-based telephone calls simultaneously on a 64 kilobit/s ISDN line
■ Use of PC-supported system telephones (so-called “Softphones”) without extra hardware costs
■
TC system networking using Q.SIG-IP via VPN connections (see also PBX Net-
■ Setting up a “DECT over IP” network lets you use existing Ethernet cabling to set up a DECT network. The special DECT base stations designed for this
purpose, can be handled using OpenCom 100’s Web interface (see DECTnetIP starting on page 117).
Integrating voice and data communication within the Intranet can provide savings possible and a range of new possibilities. However joint usage of existing network infrastructure may also cause conflicts, with IP address configuration via DHCP for
example (for details see Start Procedure starting on page 112). You should
therefore always plan the use of VoIP in the Intranet together with your network administrator. This chapter will help you avoid possible problems.
9.1
Fundamentals
VoIP makes the transmission of voice and telephony signalling via IP (“Internet
Protocol”) possible. After a connection is established, the terminal collects voice data (PCM data), which is then sent to the receiver using an IP packet. PCM data can also be compressed to save bandwidth.
9.1.1 Propagation Delay and Bandwidth
IP-based data networks are generally not able to guarantee a specific minimum bandwidth and defined propagation delay. A synchronised 64 kilobit/s ISDN line guarantees a fixed data rate as long as the connection exists. In an IP-based data network, the data rate and propagation delay can vary. Short-term bottlenecks or retransmission due to errors may be the cause. A data flow interruption of a few seconds is barely noticeable when fetching a Web page, but it can be seriously interfere with a telephone call.
100
Voice over IP (VoIP) Fundamentals
A modern Intranet normally offers enough performance reserves and reliability to make good-quality VoIP telephony possible. Specific components can also be optimised; for example by using a modern switch which evaluates the TOS byte of
IP packets or by replacing unreliable connections.
9.1.2 Latency and Packet Length
For technical reasons, there is always a delay (“latency”) between the recording of voice data via the microphone and playback via the receiver. Voice data is recorded for a short period so that it can be sent in an IP packet. The IP packet also has a signal-propagation delay before the receiver can begin playback. For these reasons, the extra time required for voice-data encoding and decoding may be neglected.
An IP packet consists of protocol data and user data. Sending shorter voice-data packets causes the ratio between the user data and the protocol data to become unfavourable and increases the bandwidth required. Sending longer voice-data packets increases latency.
The length of the voice-data packets must therefore be adjusted to the requirements of the transmission medium. Shorter voice-data packets can be sent if a direct ethernet connection exists. If an 64 kilobit/s ISDN line is to be used for transmission, then longer voice-data packets should be used.
Longer voice data packages are generally used for SIP telephony over the Internet.
The following table provides an overview of the required bandwidth for a telephone connection with various parameter settings. The values apply to halfduplex ethernet; for full-duplex the values can be halved.
Required bandwidth (kilobit/s) with respect to Packet Length and Codec
Packet
Length (ms)
20
30
40
50
G.711 (not compressed)
180.8
G.729A c. 6.3 kilobit/s
68.8
51.2
42.4
37.12
G.723.1
6.3 kilobit/s
48.0
G.723.1
5.3 kilobit/s
45.9
101
Voice over IP (VoIP) Fundamentals
Required bandwidth (kilobit/s) with respect to Packet Length and Codec
Packet
Length (ms)
60
70
80
G.711 (not compressed)
G.729A c. 6.3 kilobit/s
33.6
31.09
29.2
G.723.1
6.3 kilobit/s
30.4
G.723.1
5.3 kilobit/s
28.3
Note: To ensure SIP compatiblility, the older system telephones OpenPhone 63 IP and OpenPhone 65 IP does not support the G.723 codec any more.
9.1.3 Voice Quality
The achievable voice quality depends on various factors. It is possible to optimise voice-data transmission on an existing network using the available configuration settings. Measuring the network quality may also help.
The following comparison provides a guide to voice quality with specific quality levels:
Quality Levels for Voice Transmission with VoIP
2
3
Level Voice Comprehensibility
1 Very Good
Good
Satisfactory
4
> 4
Limited
Unacceptable
Comparable to
ISDN
DECT
GSM
Defective GSM
No Connection
When a call is set up, the terminals involved negotiate the voice-data compression
(“codec”) that will be used. This is the first factor that determines the achievable quality level:
■ G.711 A-Law (Level 1, uncompressed): The audio data of a PCM channel
(64 kilobit/s) is adopted one-to-one. Every VoIP terminal must support this codec. This codec can not be used with an ISDN data connection.
102
Voice over IP (VoIP) Fundamentals
■ G.729A (Level 2): Reduction to approximately 8 kilobit/s.
■ G.723.1 6.3 (Level 3): Reduction to 6.3 kilobit/s.
■ G.723.1 5.3 (Level 3): Reduction to 5.3 kilobit/s.
Unfavourable packet length selection may reduce voice quality. The duration of the recording and not the data packet’s byte count is relevant in making this selection:
■ Duration <= 30 ms: optimal transmission
■ Duration 40 - 60 ms: one quality-level depreciation
■ Duration > 60 ms: two quality-levels depreciation
The achievable voice quality also depends on the packet propagation delay and the packet loss between the terminals involved. These parameters can be determined using the “ping” program.
Note: Measurements made with “ping” are round-trip propagation delays. Divide the maximum value displayed by two.
Packet Propagation Delay and Packet Loss
Value
Propagation delay
< 50 ms
Quality Level
Optimal
Propagation delay
50-100 ms
0.5 level depreciation
Propagation delay
100-150 ms
1 level depreciation
Propagation delay
150-200 ms
2 level depreciation
Propagation delay
200-300 ms
3 level depreciation
Propagation delay
> 300 ms
4 level depreciation
Value
Loss < 1 %
Loss 1-2 %
Loss 2-3 %
Loss 3-4 %
Loss 4-6 %
Loss > 6 %
Quality Level
Optimal
0.5 level depreciation
1 level depreciation
2 level depreciation
3 level depreciation
4 level depreciation
103
Voice over IP (VoIP) Fundamentals
9.1.4 Optimisation
If you detect a large fluctuation in the propagation delay during measurement, this may also cause the voice quality to deteriorate. This may indicate a defective or overloaded line caused by bit-error or collision correction resulting from retransmission by the transmission procedure.
An existing star-topology ethernet-network may uses a Hub as the central distributor of ethernet packets. A Hub repeats all ethernet packets received on all connected lines. This can cause substantial collisions and result in a high fluctuation in the propagation delay.
If this is the case, use a modern switch component. Selective forwarding of ethernet packets (“Layer 2 switching”) avoids collisions. Modern switch components also evaluate the TOS byte of IP packets, thereby providing the optimal prerequisites for VoIP telephony.
Note: The OpenCom 100 uses a TOS byte (“Type of Service”) value of 0xB8 for IP packets with VoIP data. This requests “Minimise Delay” and “Maximise Throughput” for IP packets marked with this value.
9.1.5 Call set-up
Various IP-based protocols are used for system telephony via the Internet protocol
(“IP”) (see also Start Procedure starting on page 112). Multiple TCP connections are
made between an IP telephone and OpenCom 100 for the telephone’s start procedure, registration and signalling.
Call data is directly exchanged between IP telephones using the RTP (“Realtime
Transport Protocol”) protocol.
Channels on a Media Gateway (MGW) are allocated for making a telephone con-
nection with an ordinary terminal or for dial tones. The MGW converts IP voice data into PCM data streams used with conventional telephony and vice versa. For this, IP voice data are exchanged between the IP telephone and the gateway.
Tip: Switching between voice data channels may cause a slight delay in some circumstances. For example: when accepting a call on an IP telephone, headset users should wait about one second before answering.
104
Voice over IP (VoIP) Media Gateway (MGW)
9.1.6 Useful services
The type of data compression used for VoIP prevents these types of connections from using certain services. Take these notes into account especially if you want to use connections made via Q.SIG-IP or SIP:
■ ISDN data services can not be used
■ Faxes can only be sent using the uncompressed G.711 codec
■ DTMF dial tones are only received by the other party if the uncompressed
G.711 codec is used
■ Analogue modems can not be used
Tip: Configure the actual usage for the a/b ports, e.g. set them to
Fax or Data (analogue). Connections from and to these a/b ports will then be made using uncompressed or ISDN connections where possible.
9.2
Media Gateway (MGW)
The Media Gateway transforms VoIP voice data into PCM audio data. This function converts voice data between VoIP telephones and all other terminal types.
Without the Media Gateway, VoIP telephones can only exchange call data directly with other VoIP telephones. Media Gateway functionality is also required for producing dial tones and making external phone calls with a VoIP telephone. A Media gateway card makes 8 channels available. One Media gateway channel should be available for a maximum of 3 VoIP terminals.
The Media Gateway also takes over the routing function for external SIP connections, making 8 external SIP connections possible.
9.2.1 Software MGW
The system software of the OpenCom 100 provides one limited Media Gateway function. Depending on system process utilisation and available system memory, up to four MGW channels are available. The software MGW function will be automatically activated when no Media Gateway card is present.
105
Voice over IP (VoIP) Media Gateway (MGW)
Using the OpenCom 131 no Media Gateway cards can be used. Here only the software MGW function can be used for VoIP.
The Media Gateway function implemented in system software has the following limitations:
■ Up to four channels can be used simultaneously.
■ The MGW channels are not compressed, so only the G.711 codec is available.
■ There is no echo suppression.
■ Voice quality may be reduced during high system utilisation.
For optimal call quality and high availability, you should consider using a MGW
interface card (see also MGW Interface Card starting on page 106).
9.2.2 MGW Interface Card
A Media Gateway card (M100-IP) is available for the OpenCom 130 and the
OpenCom 150. This interface card implements eight simultaneously usable Media
Gateway channels.
Technical Data
■ The MGW interface card is connected via the slot to the internal ethernet
Switch. There are no external ports via pressure terminals.
■ With an OpenCom 130 the MGW interface card can be operated in slot 2 or slot 3.
■ With an OpenCom 150 up to two MGW interface cards can be operated in slots 3 and 4.
■ The MGW interface card supports: all the codecs, as well as the silence detection, echo suppression and DTMF tone detection used by VoIP telephones.
■ The MGW interface card can not be operated in a slave system.
106
Voice over IP (VoIP) SIP Telephony
■ The MGW interface card contains the required software in its own Flash memory. This software is updated using a separate file in the Configurator via the SYS Configuration: Components.
Operational Information
The MGW interface card must be correctly inserted and configured (see also
Installing Interface Cards starting on page 29).
Each MGW interface card requires its own IP address. This can either be assigned statically or obtained via DHCP.
1. In the Configurator, open the PBX Configuration: Ports: Slots page.
2. Click on the slot number in the table column containing the desired interface card.
3. Enter the desired static IP address in the IP address configured field. Enter
“0.0.0.0” to obtain an IP address via DHCP.
4. Confirm with Apply.
The configuration page displays the MGW interface card’s MAC address. You will need this for the static assignment of an IP address via a DHCP server.
Note: During the commissioning of a MGW interface card, the software MGW function is automatically switched off.
9.3
SIP Telephony
The SIP Internet (Session Initiation Protocol) protocol provides you with a low-cost, standardised option for telephoning via the Internet. OpenCom 100 enables you to use external SIP telephone connections (SIP trunk lines). The PBX Configu-
ration: Trunks: Route menu gives you the option of making an SIP connection on a normal ISDN line in case of bundle overflow, breakdown or over-occupancy. You can also set up your system to route certain types of calls, such as international calls, to an SIP connection.
Note: You will need a Media Gateway card for SIP telephony.
You will also need a fast Internet connection such as DSL for SIP telephony.
107
Voice over IP (VoIP) SIP Telephony
You will also usually need the services of a SIP provider. A SIP provider operates a special server (the SIP Registrar) to handle connections. The SIP provider also operates a gateway to the ordinary telephone network which users pay to use and which enables the SIP provider to provide calls to the telephone network.A SIP connection can also accept incoming calls from the telephone network.
distinctive features:
■ Subscribers are identified through an e-mail-like “SIP ID” such as
[email protected] or [email protected].
■ SIP transmits dialling numbers always in a single data package (block dialling).
Dialling can therefore be concluded with the hash key # on the system terminal, or the end of the number will be indicated by a time-out. The value for this time-out can be defined for each SIP provider separately.
■ You must log on (“Login”) to the SIP registrar before you can use SIP telephony.
Use the OpenCom 100 to manage important information for the registration
(user name and password) of one or more SIP accounts. It is possible to make several calls simultaneously using a single SIP account.
■ A SIP connection causes constant Internet data traffic, so do not use SIP with
Internet access which is paid for according to the time used.
■ RTP call data is also exchanged directly between terminals for SIP telephony, so different codecs can be used for sending and for receiving. It is also possible to change codecs dynamically during a call. You should use every codec available in the VoIP profile at least once, because this will enable you to establish connections with as many SIP subscribers as possible.
■ Fairly large packet lengths are quite normal on the Internet. They compensate for the longer packet propagation delay.
■ A bidirectional RTP data stream with a dynamically-assigned UDP port number is used to set up calls between subscribers. For this reason, incomng RTP calls often fail to get past the Firewall or NAT configuration of the Internet gateway product used. Do not use OpenCom 100 as an Internet gateway if the product used is to be compatible with SIP telephony. These products provide a “Full
Cone NAT” setting for this application.
108
Voice over IP (VoIP) VoIP System Telephones
■ To enable the use of multiple devices on a single Internet connection, the IP addresses used in a LAN (often 192.168.x.x) are translated to a valid IP address using address translation (NAT - Network Address Translation), but no status information is available for NAT on an incoming RTP connection.To avoid this problem, the IP address of a workplace computer or telephone visible on the
Internet is determined using a STUN server (STUN: Simple Traversal of UDP over
NAT). You can ask your SIP provider for the STUN server.’s IP address and port number If you don’t need a STUN server, leave the SIP Provider field empty.
■ For direct SIP telephony using OpenCom 100, only SIP IDs consisting of numbers for identifying subscribers registered with the SIP provider specified can be addressed
■ For each SIP account you can create just one bundle. You can specify this bundle in routes as a connection option. You can use a network provider rule to specify the routing of numbers within a specific range to use SIP telephony
as a preference (see also PBX Networking, under Configuration starting on page 133).
You can configure SIP connections in the Configurator on the pages
PBX Configuration: SIP: Accounts and PBX Configuration: SIP: Provider. Enter the technical attributes of a specific SIP provider, such as the IP addresses for the registrar and the STUN server under Provider. Under Accounts enter the information for an existing SIP account, such as the user name, password, assigned call number and the maximum number of simultaneous calls possible.
9.4
VoIP System Telephones
The following telephones and software packages are available for VoIP system telephony:
■ OpenPhone 63 IP: This is a VoIP capable edition of the OpenPhone 63 system telephone.
■ OpenPhone 65 IP: This is a VoIP capable edition of the OpenPhone 65 system telephone. This system telephone can be extended with up to three keypad modules.
■ OpenPhone IPC: This VoIP software offers the functionality of a system tele-
phone using Windows 2000/XP executable software (see OpenPhone IPC
109
Voice over IP (VoIP) VoIP System Telephones
starting on page 114). Furthermore, this software offers local answering-
machine functionality and integrability with CTI applications.
9.4.1 Device Properties
The VoIP-enabled versions of the system telephones OpenPhone 63 IP and
OpenPhone 65 IP offer the same features as the corresponding system telephones. Using VoIP system telephones is therefore not much different from using standard system telephones. The following differences exist:
■ Two RJ45 connector ports are available for ethernet connection. The ports are connected to one another via the telephone’s internal switch. The switch supports 10 Mbit/s or 100 Mbit/s full-duplex with priority given to VoIP data transmission.
LAN Port: Allows the telephone to connected to the LAN. Use a non cross-over
RJ45 patch cable to connect to a Hub or Switch.
PC Port: Allows the telephone to be connected to a workplace computer. Use a non cross-over RJ45 patch cable to connect to the PC’s network port.
■ The VoIP system telephone’s power supply is provided by an extra plug-in power supply. It is also possible to provide a power feed via PoE (“Power over
Ethernet”). PoE requires special devices for power feeds, as well as a completely wired RJ45 connection line.
■ You can also connect a standard headset via RJ45 sockets (DHSG standard) to
VoIP system telephones.
■ VoIP system telephone’s audio signals are generated by the telephone itself.
DTMF dial tones and Music on Hold are produced by the Media Gateway function.
■ A VoIP system telephone can also be operated without a permanent connection to the communications system, for example via an on-demand RAS connection.
■ Signalling data for call control, call data during three-way conferences, connections to conventional terminals and external connections is exchanged between the VoIP system telephone and the communication system. During a
110
Voice over IP (VoIP) VoIP System Telephones call between two VoIP system telephones, call data is exchanged directly between the two VoIP system telephones.
■ During the device’s start procedure, the IP address is configured and the device software is requested via the DHCP and TFTP network protocols.
9.4.2 VoIP System Telephone Configuration
The VoIP system telephones OpenPhone 63 IP and OpenPhone 65 IP obtain the required IP address configuration and operating software via the DHCP, BOOTP and TFTP IP protocols. After the power supply is assured, the device’s internal boot loader is started which controls the further start procedure.
Standard operating procedure is to contact the OpenCom 100’s DHCP server so that the start procedure can be concluded without problems. To register a new
VoIP system telephone, proceed as follows:
1. Temporarily remove the VoIP system telephone’s ethernet connection. Switch on the VoIP system telephone’s power supply. Note the MAC address shown in the display, for instance “MAC: 00:30:42:00:00:00”. Switch off the power supply.
2. In the Configurator, open the PBX Configuration: Devices: VoIP Phones page. Click on the New button.
3. Select the VoIP system telephone’s Type and enter the previously noted MAC address. Assign a Name and Phone No. Confirm with Apply.
4. Connect the ethernet connection with the VoIP system telephone’s RJ45 connector. Switch on the power supply. Verify the correct start procedure on the display.
9.4.3 LAN DHCP Server
If the LAN already uses a DHCP server to configure workplace computers, there are various options for correctly responding to VoIP system telephones’ DHCP, BOOTP and TFTP requests. A comparatively simple approach is described here.
1. Configure the LAN’s DHCP server to ignore DHCP requests from the VoIP system telephones. With a Linux DHCP server program, you must, for example, include the following lines in the system file “/etc/dhcpd.conf”:
111
Voice over IP (VoIP) VoIP System Telephones
} group { deny booting;
} host 192.168.11.12 { hardware ethernet 00:30:42:00:11:22;
Every DHCP service program has similar options. You may need to reserve a free IP address for each VoIP system telephone. You will find more details in your DHCP service program’s online help or handbook. The MAC address of all
VoIP system telephones always begins with 00:30:42.
2. Configure a fixed IP address for the OpenCom 100. To do this, call up the Confi-
gurator and open the NET Configuration: LAN page. Click on the Change button.
3. Select from Get addresses from the DHCP server the option no. Enter the current IP address configuration in IP address and Network mask. Confirm with Apply.
4. Configure the OpenCom 100’s DHCP server to assign IP addresses. To do this, call up the Configurator and open the NET Configuration: LAN: DHCP
Server page. Click on the Change button.
5. From Status, select the address assignment option. Confirm with Apply. The
DHCP Server page is re-displayed.
6. Add the configured VoIP system telephones to the list of IP addresses. Click on the New button.
7. Enter the VoIP system telephone’s IP address and MAC address. Enter the IP address reserved by the DHCP service program. Confirm with Apply.
Restart the OpenCom 100 and all connected VoIP system telephones.
9.4.4 Start Procedure
It may sometimes be useful to understand a VoIP system telephone’s start procedure. Examples:
112
Voice over IP (VoIP) VoIP System Telephones
■ A complex DHCP address assignment prevents the operation of the
OpenCom 100’s DHCP server within the LAN.
■ A VoIP system should be operated with a non-broadcast-capable IP connection. This may be an RAS connection, a VPN connection or another type of routed connection.
An external DHCP server can also control a VoIP system telephone’s start procedure. In this case, system software matching the type of VoIP system telephone must be transferred via TFTP.
After the VoIP system telephone has been connected to the mains power supply, the start procedure is as follows:
1. The boot loader starts and shows the VoIP system telephone’s MAC address in the display. A DHCP request is sent simultaneously via broadcast on the
255.255.255.255 broadcast address.
2. An IP address, network mask and the default gateway for the start procedure are sent from the DHCP server. Via the “Next server” option, the DHCP server also provides the TFTP server’s IP address and the operations software’s file name. The DHCP server uses the MAC address to select the operations software file which matches the type of device.
3. The boot loader loads the operations software file from the specified TFTP server. The TFTP server’s IP address and the file’s name are shown in the display.
The loaded operations software is started.
4. The operations software sends a DHCP request on the broadcast address
255.255.255.255. The VoIP system telephone now receives an IP address, network mask and default gateway for operations from the DHCP server. Using
“Option 43”, which is reserved for this purpose, the DHCP server also provides the IP address of the communication system and port number 8100 for registration.
5. The VoIP system telephone creates a TCP connection to the supplied IPaddress/port-number combination and sends a registration query. The
OpenCom 100 checks the MAC address sent with the registration and confirms the registration request if the VoIP system telephone is listed in the menu
PBX Configuration: Devices: VoIP Phones. The keep-alive time, port number
(8101) for telephony signalling and the value to use for the TOS byte are also communicated in the registration answer.
113
Voice over IP (VoIP) OpenPhone IPC
6. The VoIP system telephone creates a second TCP connection using the signalling port number 8101 and sends a registration analogue to the U pn
system telephones.
7. Extra connections are created using the IP protocol RTP (“Realtime Transport
Protocol”) for call data when a call is created. For calls between two VoIP system telephones, port numbers above 8200 are used. For transmission to a Media
Gateway card, a port in the range 1024 – 1087 is used.
If you wish to operate a VoIP system telephone via a routed IP connection (for example VPN or RAS) it may be necessary to configure an external DHCP server accordingly. Please note the selection of the codec and keep-alive time for RAS connections. This can be done by selecting the default profile RAS in the
PBX Configuration: Devices: VoIP Phones for the VoIP system telephone. The operations software provided via TFTP must match the type of device and communication system. You may also need to configure BOOTP, DHCP and TFTP servers for the VoIP system telephone.
9.5
OpenPhone IPC
Besides the hardware VoIP system telephones, PC software for VoIP telephony can also be deployed. This software can be used with the operating systems
Windows 98 SE/ME and Windows 2000/XP.
Software VoIP system telephone OpenPhone 65 IPC with one keypad module
114
Voice over IP (VoIP) OpenPhone IPC
As well as VoIP system telephony from workplace computers, the OpenPhone IPC includes the following features:
■ Usage via Mouse/PC keyboard
■ “Drag & Drop” call number selection
■ Integrated answering machine / recording function
■ Terminal control for the sight-impaired
■ Selectable user interface (“Skins”)
■ Display language modification
The workplace computer requires a full-duplex-enabled sound card as well as a suitable headset for audio recording and playback.
You will not need a licence to install OpenPhone IPC but you will require a licence to operate it with the OpenCom 100. Unit licences, enabling the simultaneous operation of a certain number of OpenPhone IPCs, are available.
The licences are activated in the OpenCom 100’s Configurator in the Menu
SYS Configuration: Licences. The system software includes a licence for a demo version for temporary use (60 days). Please contact your local agent or DeTeWe representative if you wish to purchase a permanent licence. Licences can be combined. Each licence can be activated only once.
9.5.1 Installation
Installation is done using a setup program. The OpenPhone IPC can also be installed without a user interface. The program can then be used via a CTI application (Net-TAPI or OpenCTI).
Start the installation program from the OpenPhone IPC product CD and follow the installation assistant’s instructions.
115
Voice over IP (VoIP) OpenPhone IPC
9.5.2 Configuration
Analogue to the VoIP system telephones, the OpenPhone IPC creates multiple IP connections to the OpenCom 100. When you start the program for the first time, the Options dialogue is automatically opened. Here you must configure the following values:
1. Enter in the VoIP IP Address field the OpenCom 100’s IP address.
2. Enter six hexadecimal-digits into the Device ID field. This device ID is not a
MAC address, so overlapping with existent MAC addresses is possible. The device ID is configured in the Configurator, on the PBX Configuration:
Devices: VoIP Phones page.
3. Confirm with OK.
Notes
VoIP system telephony requires an active IP connection to a workplace computer.
If a Firewall is installed for your workplace computer, you may need to explicitly allow this connection.
If you log on to the workplace computer using a different user name, you must reconfigure these values.
You can use any arbitrary sequence of digits not already in use in the LAN for the device ID. Select a random device ID to secure telephone usage. The device ID can only be read on the Web console.
The displayed menu texts and parts of the operations software are elements of the
OpenPhone IPC installation, but they can be loaded from the OpenCom 100 via
TFTP. where necessary
116
DECTnetIP Properties
10. DECTnetIP
In order to achieve optimal network coverage, a DECT network with several DECT base stations can be operated. A DECT network is comprised of DECT terminals connected with the next respective base station (network cell). For users of a DECT terminal, the handover from DECT base station to base station is completely transparent. Even during a conversation, users are switched from one network cell to the next without any interruption. Administration of DECT terminals is done centrally via the OpenCom 100 Configurator in the PBX Configuration: Devices:
DECT Phones menu.
10.1
Properties
10.1.1 DECT base stations
DECT base stations can be connected to the OpenCom 100 via U pn
accesses or via network (TCP/IP). These DECT base stations are available for the type of access selected:
■ RFP 22: Access via U pn
with lines up to 1000 metres in length; integrated antennas; 4 voice channels (8 when using 2 U pn
accesses)
■ RFP 24: like the RFP 22; mounted outside enclosed areas (IP55); external antennas
Note: The newer DECT base stations RFP 22 and RFP 24 can be simultaneously operated with the older DECT base stations, RFP 21 and RFP 23. Fax transmissions (group 3 with ECM) and SARI (roaming with Secondary Access Rights Identification Broadcasts) can be done using the newer DECT base stations. Data transmission via DECT is not available with the newer DECT base stations.
■ RFP 31: Access via shielded CAT5 Ethernet cable (STP cable, Shielded Twisted
Pair cable) with up to 100 metres in length; integrated antennas; 8 voice channels
■ RFP 33: like the RFP 31; mounted outside enclosed areas (IP55); external antennas
117
DECTnetIP Properties
■ RFP 41: Access via shielded CAT5 Ethernet cable (STP cable, Shielded Twisted
Pair cable); offers simultaneous function of a WLAN Access Point conforming with the IEEE 802.11b/g protocol; external antennas; 8 voice channels
■ RFP 43: like the RFP 41; mounted outside enclosed areas (IP55); external antennas
Note: When started, the operating software for the DECTnetIP base stations is transmitted via TFTP protocol from the
OpenCom 100. The configuration for the start sequence is transmitted by the DHCP server of the OpenCom 100 to a
DECTnetIP base station for the start sequence. The operating software is saved on the Media Gateway Card. DECTnetIP base stations can only be operated with the OpenCom 130/
150 if a Media Gateway Card has been installed.
If VoIP telephony is already being used, Ethernet cable access makes good sense.
Transmission of telephony signalling and voice data via TCP/IP also offers usage of existing network infrastructure and an increase in range using suitable methods.
VPN connections, for example, can be used for data links to provide service to remote or hard-to-reach locations.
10.1.2 Features
All DECTnetIP base stations can be connected to a CAT5 Ethernet cable with a 10/
100 Base T. Power is supplied either via Power-over-LAN (IEEE 802.3af ) or via an additional power supply unit.
DECT terminals offer all system telephony features. DECT telephones supporting the GAP standard can also be operated. Transparent GAP device handovers are supported. DECT encryption can be deactivated if desired.
VoIP audio communication between the DECTnetIP base station and the
OpenCom 100 is via the RTP/RTCP protocol. RTP voice data are directly converted into DECT voice data by the base station. Base stations support VoIP voice data compression using the G.711, G.729 and G.723 codecs.
118
DECTnetIP Configuration
10.2
Configuration
One of the DECTnetIP base stations that is installed assumes coordination and configuration of the DECT-over-IP functions (DECTnetIP-Manager). Select a base station that has a dependable data link to the OpenCom 100. Go to the PBX Confi-
guration: Devices: DECTnetIP page in the Configurator. Enter the MAC address of the base station that you have selected to be the DECTnetIP Manager. The MAC address of the base station is located on its type label. Enter a fixed IP address for this base station. All other base stations can be operated using either a fixed IP address or an IP address assigned dynamically via DHCP. Configuration of the
DECTnetIP-Manager must work via a static DHCP entry. Please refer to the infor-
mation given in the chapter entitled LAN DHCP Server starting on page 111.
Note: A base station cannot be operated as a DECTnetIP Manager and a WLAN-Access Point simultaneously.
Create a separate entry for each DECTnetIP base station and for the DECTnetIP
Manager as well. You use these entries to determine the VoIP data compression
(Profile).
Configurator: PBX Configuration: Devices: DECTnetIP
User administration and set-up of DECT terminals is done in the Configurator of the OpenCom 100 as well.
The DECTnetIP Manager offers a separate web user interface to manage the settings of devices with WLAN functions. Therefore at least one WLAN-RFP has to be configured. If everthing is configured correctly, you will see the WLAN Config link.
Login as the user “Administrator” with the currently set administrator’s password of the OpenCom 100.
119
DECTnetIP Configuration
10.2.1 Dual operation
Simultaneous operation of base stations via U pn
access and base stations via
Ethernet access is possible with the OpenCom 100. Transparent handovers, for example, are only possible when between DECT base stations using the same access technology. When switching over to a DECT base station using different access technology, a DECT terminal automatically re-establishes a connection
(roaming).
Be sure to keep the PARK ID of your OpenCom 100 in mind. The PARK ID is displayed under System Info: Versions in the Configurator. If the PARK ID starts with
31, there may be an attempt at a handover between DECT base stations using different access technology. In this case, make sure that the signal areas of the DECT base stations using different access technology do not overlap. If the PARK ID starts with a different value (e. g. 30), prevention of unintentional handovers is effective.
10.2.2 Synchronisation
Transmissions of all DECT base stations at a single location must be synchronised in order that DECT terminals are able to receive multiple DECT base stations simultaneously. Synchronisation can be conducted via U pn
access. It cannot be conducted via an Ethernet/IP connection. DECTnetIP base stations are thus synchronised via wireless connection.
When planning a larger sized DECT network, it is advisable to take the following points into consideration:
■ All DECTnetIP base stations at a single location must be able to receive at least one neighbouring base station. Synchronisation requires less signal strength than a voice connection does.
■ Synchronisation range is increased using multiple base stations. To decrease the probability of a connection breakdown, base stations should not be arranged in chain formation. The signal should be distributed with a network that is as extensive as possible and where each base station is supported by multiple synchronisation partners.
■ To re-synchronise, first wait for all current connections to be terminated.
120
DECTnetIP Configuration
You can operate a DECT network consisting of several remote locations (a cluster).
These locations do not need to be synchronised because handovers between remote locations are not possible.
121
PBX Cascading Variants of PBX Cascading
11. PBX Cascading
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 Networking (see
Note: It is not possible to cascade an OpenCom 131 with another communications system.
11.1
Variants of PBX Cascading
You can combine two PBXs in order to increase the number of terminals that can be connected. A master PBX and a slave PBX are connected to one another by means of two cables. The two PBXs essentially function like a single PBX with a higher number of ports. The master PBX controls the slave PBX. The following PBXs from the product family can be used for cascading:
Master system
OpenCom 130
OpenCom 150 Rack
Slave system
OpenCom 130
OpenCom 150 Rack
For the PBX Cascading you will need a license. The license agreement provides you with the necessary steps to activate this function.
11.2
Functionality of PBX Cascading
PBX cascading requires two twisted-pair 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.
The PCM port is on the add-on module of the OpenCom 130. You must therefore install an add-on module in each of the two PBXs before they can be cascaded.
■ Administration data: one CAT-5 Ethernet lead.
122
PBX Cascading Putting a Cascaded PBX into Operation
– In the case of an OpenCom 130, connect the LAN2 port of the master system’s add-on module with a LAN2 port of the slave system’s add-on module.
– In the case of an OpenCom 150, connect the LAN1 port of the master system with a LAN1 port of the slave system.
Basic module
LAN
PBX 1
(Master)
Add-on module
PCM LAN1 LAN2 LAN0
Voice data lead
(eight pins assigned, joined 1 to 1) Hub/Switch
(in LAN of company)
Cascaded PBX system (OpenCom 130)
Basic module
LAN
PBX 2
(Slave)
Add-on module
PCM LAN1 LAN2 LAN0
CAT-5 Ethernet lead
PBX 1
(Master)
PBX 2
(Slave)
PCM1 PCM2 LAN0 LAN1 PCM1 PCM2 LAN0 LAN1
Voice data lead (eight pins assigned, joined 1 to 1)
CAT-5 Ethernet lead Hub/Switch
(in LAN of company)
Cascaded PBX system (OpenCom 150)
11.3
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 of the basic module (only OpenCom 130) or one of the U pn
ports of an interface card.
2. Back up the master system data. For further information, refer to the online help topic SYS Configuration: Data Backup.
123
PBX Cascading Putting a Cascaded PBX into Operation
3. Switch off the master system if it is operating. Disconnect the module from the power supply by pulling out the mains plug.
4. If necessary, install the add-on module for the master system. If you use an
OpenCom 130 as the slave system, you also have to install an add-on module.
5. Connect the two modules by means of two suitable cables as described above.
6. Power on the two PBXs. The order in which you do this does not matter.
7. In the PBX Configuration: Ports: Slots dialogue of the master system’s Configurator, click on Slave. Select the slave Type in the Slave: Change dialogue.
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.
Please note: If you change the type of slave system later on, the port settings that have been made will be deleted.
The master system then initialises the slave system. This may involve transfer of firmware (operating software) from the master system to the slave system. The transfer process is only executed for two OpenCom 130/150 PBXs. This can take a few minutes.
8. Configure the system telephone connected to the slave system for testing purposes in the Configurator. In the PBX Configuration: Ports: Upn dialogue, click on one of the additionally displayed entries of the type Upn 1/0/n
(1: slave system, n: U pn
port number).
Note: Changes to the configuration while initialising the slave system may trigger error reports referring to the ongoing initialisation.
You can see that the initialisation has been completed from the display on the system telephone connected to the slave system.
124
PBX Cascading Putting a Cascaded PBX into Operation
11.3.1 Notes
Observe the following when operating a cascaded PBX system:
■ All U pn
, S
0
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
0
ports of the slave system can also be used for trunk lines or for PBX net-
working (see PBX Networking starting on page 127).
■ 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 LAN ports of the slave system cannot be used. The
LAN ports on the add-on module of slave system can be used without restriction.
■ 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 OpenCom 150 is equipped with the PCM2 port in order to realize cascading of a third PBX with a future release. Use one of the two LAN0 ports, to connect the OpenCom 150 to the Local Area Network.
■ 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, OpenAttendant) cannot be used.
■ To operate the slave system again normally, you must reset it to its factory set-
tings (refer to Resetting the System Data starting on page 84).
125
PBX Cascading Licensing Information
11.4
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.
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.
PBX Cascading
In the case of PBX cascading, the master system administers the overall configuration.
If you have already installed activation keys on an existing OpenCom, they have to be ported to the master system.
In this case, new activation keys for the use of additional program packages must be generated on the DeTeWe licence server (http://lizenz.aastra-detewe.de). The licensing confirmation for the cascading contains all the information you need to carry out this procedure.
Note: You will need the serial numbers of both infocom systems for porting the activation keys. The serial numbers can be found in the Web console's Configurator, in the System
Info: Versions menu.
126
PBX Networking
12. PBX Networking
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.
You can use ISDN point-to-point connections (Q.SIG or DSS1 protocol) or IP connections (Q.SIG-IP protocol) for TK system networking.
Note: If you do not need the features of PBX networking, the simplified configuration is sufficient in most cases. For this purpose, assign the preconfigured trunk groups (bundles) Multi-terminal access or System access to the ports.
The preconfigured route called External trunk now makes it possible to seize an external line immediately or by first dialling the prefix “0”. You can rename the preconfigured bundle and the preconfigured route if required, but you cannot delete them.
127
PBX Networking Connections
12.1
Connections
Networking two or more TK systems means interconnecting them. The
OpenCom 100 allows you to use the following connections:
■ ISDN trunk lines
■ ISDN point-to-point connections (Q.SIG) on external S
0
ports or on the S
2M
port
■ IP network connections (Q.SIG-IP)
PBX PBX PBX PBX
PBX
Trunk line
Point-to-point connection
Example of a PBX network
Various line types and transmission protocols can be used for point-to-point connections. The required network topology (distance, connection capacity) determines which type of point-to-point connection is most suitable.
12.1.1 Protocol: Q.SIG or DSS1
The Q.SIG protocol, designed for ISDN point-to-point connections, is the preferable choice as the transmission protocol; alternatively, the DSS1 protocol, designed for ISDN dial-up connections in the Euro-ISDN, can be used. Certain PBX networking features can only be used with the Q.SIG/Q.SIG-IP protocol, however.
In particular, the identifier indicating whether a call is internal or external cannot be transmitted using DSS1.
Both protocols implement communication on several protocol layers:
■ L1: Layer 1 defines the physical line properties and the electrical coding of signals.
■ L2: Layer 2 enables communication via individual error-protected channels that are independent of each other.
■ L3: Layer 3 defines the administration of the individual channels and implements the features designed for ISDN.
128
PBX Networking Connections
Note: All layers of the Q.SIG-IP protocol are symmetrical. The following are unnecessary: a Master/Slave setting, clock and
synchronisation settings (please refer to Connection via
Q.SIG.IP starting on page 132).
12.1.2 Master/Slave
For an ISDN connection, it is possible to determine which PBX is the protocol master and which the protocol slave. This relationship can be determined for all three protocol layers independently of one another.
For each protocol layer, the PBX at the other end always has to be suitably configured. If one PBX is the protocol master for a layer, the other PBX must be the protocol slave for this same layer. Normally all three protocol layers are configured identically. In the case of a trunk line, the network operator is the protocol master for all three layers.
Note: In the case of an S
2M
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
0
lines this setting is determined by “L3 master” for both B-channels.
12.1.3 L1 Clock
To enable PBXs in the ISDN network to communicate with each other, they must be “clock-aligned”. The L1 protocol master sets the clock for layer 1, and the L1 protocol slave adopts (synchronises to) this clock.
When planning a PBX networking scheme, you must make sure that the L1 clock propagates from a master via a number of PBXs.
Network operator M S
PBX1
M
M S
PBX 3
S
S
PBX 2
M
Trunk line
Point-to-point connection
Example: propagation of the L1 clock
129
PBX Networking Types of Point-to-Point Connections
If more than one port with the setting L1 Type = “Slave” is configured on an
OpenCom 100 and the setting 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 circular application of the L1 clock is not allowed.
Example: In the above case you could reverse the L1 slave/master setting for the connection between PBX 1 and PBX 3. However, if you then activate the setting
L1 sync possible for the port of PBX 1, this may cause parts of the PBX network to stop functioning temporarily.
When applying the L1 clock of trunk lines, you can assume that the public network is “clock-aligned”. So, in the above example, you can connect additional trunk lines to one of the PBXs.
12.2
Types of Point-to-Point Connections
There are different types of connection available for an point-to-point connection between two PBXs, depending on the distance between them.
12.2.1 Direct Connection
This type of ISDN point-to-point connection joins the two systems directly to each other using a crossover twisted-pair cable. An S
0
connection can be used for distances up to 1,000 metres, while an S
2M
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
0
ports for an S
0
connection between two OpenCom 100s. You can use the corresponding pressure terminals for S
0 ports on interface cards.
130
PBX Networking
PBX 1, S
0
ext
1 2 3 4 5 6 7 8
PBX 1, S
2M
Rx+ RxTx+ Tx-
Types of Point-to-Point Connections
8 7 6 5 4 3 2 1
PBX 2, S
0
ext
(RJ-45 socket)
Rx+ RxTx+ Tx-
PBX 2, S
2M
(Pressure clamps)
Wiring of a direct connection
Note: If you use an S
0
port on an interface card (pressure terminal) and an S
0
port with an RJ45 jack for the direct connection, make sure you make the necessary changes to the
port assignment (see S0 Ports on Interface Cards starting on page 46).
12.2.2 Connection via an Active Transmission System
For distances exceeding the range of a direct connection, an active transmission system can increase the range to up to 50 km. Normally the L1 master is the transmission system for the two connected PBXs. For the protocol layers L2 and L3, one
PBX is normally the protocol master and the other PBX is the protocol slave.
PBX 1
L1 slave
L2 master
L3 master
Transmission
System
L1 master
PBX 2
L1 slave
L2 slave
L3 slave
Connection by an active transmission system
Note: The active transmission system itself gets its L1 clock either from the network operator or from a clock generator connected by wire.
12.2.3 Connection via the Public Network
Point-to-point connections via the public network of a network operator can be used for bridging distances beyond 50 km. Due to the long distance involved, for technical reasons it is not possible to synchronise the L2 protocol. Consequently, the public network is normally the protocol master for protocol layers L1 and L2.
One PBX is therefore the L3 master and the other PBX the L3 slave.
131
PBX Networking Types of Point-to-Point Connections
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
12.2.4 Connection via Q.SIG.IP
If you are operating a fast and continuous internet connection at two or more locations, you can establish the TK system networking via internet connection as well. The OpenCom 100 uses the Q.SIG protocol, for use with ISDN point-to-point connections and transports the protocol and voice data via IP connections.
The number of simultaneous conversations possible will depend on the capacity of the internet connection and the compression method used. A multiple S
2M point-to-point connection is simulated for each Q.SIG-IP bundle. This means that 5 virtual D channels and up to 120 voice channels are available. Both Media Gateway
Card channels and the Media Gateway software function can be used for Q.SIG-IP.
Q.SIG-IP connection data are subject to codec compression (please refer to Voice
over IP (VoIP) chapter regarding Fundamentals starting on page 100). Q.SIG-IP also
transfers the voice data directly from terminal to terminal via the RTP protocol. In certain cases, for example, when an incoming external call is placed via multiple TK systems, one or more RTP proxies may be used to forward the connection.
Currently, there are no standards for the necessary extensions to the Q.SIG protocol. This means that you can only use Q.SIG-IP between OpenCom 100 systems
(exception: OpenCom 1000).
Networking two OpenCom 100 systems using Q.SIG-IP requires 2 licenses – one license per system. The number of possible voice connections is not restricted by the license.
Go to the PBX Configuration: Trunks: Bundle page in the Configurator to set up a Q.SIG-IP connection. Create a new bundle and select the Access type “System
Access”. Select “Q.SIG-IP” under Protocol. Configure the IP address of the other system, the port numbers to be used, the number of possible voice connections and select a VoIP profile for the codec selection. Please refer to the relevant help topics in the Online Help for the OpenCom 100 as well.
132
PBX Networking Configuration
Note: Q.SIG-IP cannot be operated using a connection with
NAT.
12.3
Configuration
The possible configurations described below can be set up in the Web console using the PBX Configuration: Trunks menu.
12.3.1 Trunk groups
This is a group of lines of the same type and direction. A line can only be assigned to one trunk group (bundle).
Network operator
PBX 1 PBX 3
A E
C
B D
PBX 2
Bundle
Trunk line
Point-to-point connection
Example of a PBX network with trunk groups
In the above example, the following trunk groups are configured for PBX 1:
■ Two S
0
lines in a multi-terminal configuration to the network operator which are assigned to the “A” trunk group.
■ Two S
0
point-to-point connections to PBX 2 which are assigned to the “C” trunk group.
■ One S
0
point-to-point connection to PBX 3 which is assigned to the “E” trunk group.
Note: A line or a trunk group cannot be seized directly. It is always performed indirectly via a route.
133
PBX Networking Configuration
12.3.2 Routes
A route is a group of trunk groups enabling a connection in one direction. If the first trunk group of a route is fully utilized, the next trunk group is seized (“trunk group overflow”). One trunk group can also be used for different routes.
In the above example, a route set up for PBX 1 allows a connection to PBX 2. Trunk groups “C,” “E” and “A” are assigned to this route. If a user connected to PBX 1 wants to reach a party in PBX 2, lines will be seized in the following order:
■ PBX 1 first searches for a free channel in the “C” trunk group.
■ If all the lines in trunk group “C” are busy, the system tries to set up a connection via trunk group “E”. PBX 3 switches the connection through, provided
it is appropriately configured (refer to Numbering starting on page 134).
■ 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.
12.3.3 Numbering
A user can seize a particular route by pre-dialling a specific code digit. With this
“open numbering”, a user must always dial this code digit and then the telephone number in order to reach a party in another PBX.
If none of the telephone numbers in your PBX network occur twice, you can also configure “closed numbering”, allowing the same telephone number to be used for reaching each user within the PBX network.
134
PBX Networking Configuration
With closed numbering, the OpenCom 100 determines which route to seize from the telephone number dialled. The information needed for routing a call can be configured in a numbering table containing up to 100 entries. You use this table to assign telephone numbers and/or ranges of telephone numbers to a particular route.
A default entry in the numbering table makes it possible to seize a “default route” for all remaining unassigned numbers. In particular, this simplifies configuration of the OpenCom 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 4: b
D: c
PBX
200-299 e g h
3: e
5: h
D: d f
PBX
300-399 k 5: k
D: f
PBX
400-499
D: a
PBX
500-599 i
3: i
D: g
D:Default
Route
Example of closed numbering tables
The automatic switching of call requests (i.e. routing) by means of trunk group overflow or default numbering can lead to “circular switching”.
To avoid this, a “transit” counter is incremented whenever a connection is switched through on Q.SIG lines. When the configured maximum value is reached, further switching stops.
135
PBX Networking Technical Details
12.4
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: Settings under the heading System linking. You can also set the maximum value for the transit counter there. This value depends on the topology of the PBX network and should allow the system to have the maximum number of further connections possible.
You can display the connection status of the lines at any time in the Configurator menu System info: PBX: Trunks. You should check this in particular after making changes to a configuration to see whether all the lines used for system networking are operable.
Some of the features possible in Q.SIG are not supported by OpenCom 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 group configuration for the routes to be reseized.
Tip: If, for example, you are configuring a route which can be seized using routing code “5” and have selected one or more bundles for this route, change the Prefix for dest. call num-
ber at incoming internal setting to “5” for this bundle in order to enable the route to be reseized.
Owing to their hardware properties, not all S
0
ports of the OpenCom 100 can be used for PBX networking without restrictions. Depending on the type of system,
136
PBX Networking Technical Details some ports can only operate in the L1 master mode or L1 slave mode. The external
S
0
and S
2M
ports can be set according to the following table.
OpenCom 107
OpenCom 130
OpenCom 150
Legend
S = Slave
M/S = Master/Slave
M = Master
S
S
S
-
0
1 S
M/S
M/S
-
0
2 S
-
-
0
3
M/S
S
M
-
-
0
4 S
2M
–
M/S
M/S
Note: The S
0
ports on add-on cards can be operated in both
L1 master and L1 slave mode.
137
Team Functions
13. Team Functions
Introduction
13.1
Introduction
With the team functions you can manage your telephone communication tasks by assigning lines with separate call numbers to the keys of different terminals. The terminal users, or team members, can thus pick up one another’s calls or telephone each other using the configured keys.
Team functions can only be configured on the corded system telephones of the
OpenPhone 6x product line because only these have the required features.
13.1.1 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
OpenPhone 61
OpenPhone 63
OpenPhone 65
Number of keys
One key with a display, five keys without a display
Three keys with a display, five keys without a display
19 keys with a display: nine on the telephone itself and 10 on an add-on keypad module
Note: Only one function or call number can be programmed for each call key.
The following keys can be used:
■ Trunk key: Calls (for the programmed call number, e.g. 11) are signalled to this key, and you can make internal and external calls via this number. A trunk key can be programmed with a substitute function (with another team member acting as the substitute). Calls for you are then signalled to the terminal of another team member. A trunk key also provides functions for managing calls.
138
Team Functions Introduction
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 enquiry station showing the status of the individual users. The enquiry station sees the status of the users and can put calls through by simply pressing the key.
139
Team Functions Examples of Use
■ Direct call keys, for example, can be configured at a terminal in a conference room to call the secretary.
13.1.2 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.
13.2
Examples of Use
The following examples illustrate the various uses of teams and team functions.
For information on the display texts and how to use the individual functions, refer to the chapter “Managing Calls in a Team” in the “OpenPhone 61, 63, 65” user guide.
13.2.1 Executive/Secretary Team
In this example, the executive/secretary team comprises two members: the executive and the secretary. The secretary has one OpenPhone 63 system telephone, and the executive has two, one of which is used as a parallel telephone in a sofa suite.
Line Seizure
The secretary can be reached on the call number 11 (trunk key TrK 11: secretary’s office).
The executive can be reached on the call number 10 (trunk key TrK 10: executive’s office). He can also answer calls from his parallel telephone. In addition, a private line is configured for both of the executive’s telephones (trunk key TrK 12: private).
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.
140
Team Functions Examples of Use
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.
13.2.2 Three-member Team
The three-member team described here is an example of a team configuration within a project group, e.g. export sales.
Each team member has one OpenPhone 63 system telephone with all call keys programmed as trunk and team keys.
141
Team Functions Examples of Use
10
Miller
TrK 10: Miller
TK 11: Johnson
TK 12: Smith
11
Johnson
Trk 11: Johnson
TK 10: Miller
TK 12: Smith
12
Smith
TrK 12: Smith
TK 10: Miller
TK 11: Johnson
Example: three-member team
Line Seizure
Each team member’s call number, e.g. call number 10 for Miller, is programmed as a trunk key on his telephone.
On the other telephones in the team, this call number is programmed as a team key (e.g. TK 10 on Johnson’s and Smith’s telephones). The team members can thus see which number a call is for and can answer it by pressing the appropriate team key.
The team members can call each other via the team keys. For example, Miller can call number 12 by pressing TK 12; the call is then signalled to Smith’s telephone on
TrK 12.
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).
13.2.3 Unified Team
The unified team described here is an example of a team configuration within a department in which calls are to be managed quickly (e.g. support department).
142
Team Functions Examples of Use
Each team member has one OpenPhone 63 system telephone with all call keys programmed as trunk keys.
Miller
TrK 10: Support 1
TrK 11: Support 2
TrK 12: Support 3
10
11
Johnson
TrK 10: Support 1
TrK 11: Support 2
TrK 12: Support 3
12
Smith
TrK 10: Support 1
TrK 11: Support 2
TrK 12: Support 3
Example: unified team
Line Seizure
Call numbers 10, 11 and 12 are programmed as trunk keys on each team member’s telephone (TrK 10 to TrK 12.
All team members can use these numbers for answering as well as making calls.
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.
143
Team Functions Examples of Use
10
11
12
13
14
15
16
13.2.4 Toggle Team
The toggle team described here illustrates how a large number of call numbers can be managed efficiently with the help of team functions.
Each team member has one OpenPhone 65 system telephone with all call keys programmed as trunk and team keys.
Miller 14:22
Mi .
14.Feb
.
01
TrK 10: Support 1
TrK 11: Support 2
TrK 12: Support 3
TrK 13: Support 4
TrK 14: Support 5
TrK 15: Hotline 1
TrK 16: Hotline 2
TK 20: Support 6
TK 25: Hotline 3
20
21
22
23
24
25
26
Johnson 14:22
Mi .
14.Feb
.
01
TrK 20: Support 6
TrK 21: Support 7
TrK 22: Support 8
TrK 23: Support 9
TrK 24: Support 10
TrK 25: Hotline 3
TrK 26: Hotline 4
TK 10: Support 1
TK 15: Hotline 1
Example: toggle team
Line Seizure
Each team member is assigned seven call numbers, each programmed as a trunk key (TrK 10 to TrK 16 and TrK 20 to TrK 26). For each member, these trunk keys are programmed either as support numbers or hotline numbers.
The first support number and the first hotline number of each team member is programmed as a team key on the other member’s telephone, e.g. TrK 10 and
TrK 15 on Miller’s telephone as TK 10 and TK 15 on Johnson’s telephone. The assumption here is that most calls will go to the respective first call numbers, and team members can thus help each other out by answering one another’s calls.
144
Team Functions Examples of Use
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).
145
Call Queue
14. Call Queue
Introduction
14.1
Introduction
A queue can be activated for the telephone numbers of any type of telephone, i.e. for system, analogue, ISDN and DECT telephones.
If a call number with a queue is busy, calls to this number enter the queue. The caller first hears an announcement (if function “Announcer at busy” is configured) and then a dial tone.
Calls which remain in the queue for too long are cleared from the queue. The caller then gets a busy tone. If all the positions in the queue are taken then any further calls also hear the busy tone.
The time until an external call is cleared from a queue is defined by the network operator. In Germany this is usually two minutes and in other European countries usually three minutes.
If more than one telephone number (e.g. trunk or team keys) has been configured for a telephone, separate queues are used for each number.
On the OpenPhone 65 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, door calls, automatic recalls, VIP calls, then other internal and external calls. Sensor calls thus have priority over other calls, for example. Calls of the same priority level are switched in the order of their arrival.
The system administrator sets the number of calls that can be placed in a queue individually for each user group. The value can lie between “0” and “99”. The “0” value deactivates the ”Call queue” function for a user group. When the maximum number of calls in the queue is reached, further callers hear a busy tone.
Only calls which have a “voice” service indicator are administered in a queue.
146
Call Queue Introduction
Note: As calling fax machines often operate with the “voice” service indicator (e.g. on analogue ports), you should assign ports for fax machines on the OpenCom 100 to a user group
without a queue.
Queues can be combined with the “forwarding,” “pickup” and “hunt group” functions, for example, in order to configure an enquiry station for an operator.
14.1.1 Activation of Queues
Queues can be activated on a per user group basis. On delivery the default set, for all preset groups, is off.
When using queues, it often makes sense to activate call waiting protection. For this purpose, “Call waiting protection” authorisation must be allocated to the user group, and call waiting protection must be activated on the terminal.
Furthermore it is sensible to combine queues with the “Announcer at busy” function. When a caller calls a subscriber who is busy then they will hear a “central welcoming text”, for example, “Here is company XYZ. You will be immediately connected”. The function “Announcer at busy” can be set in the PBX Configuration:
Call Distribution: Incoming menu. Central welcoming texts can be recorded using the program package OpenVoice.
You should configure a new user group (e.g. “Operators”) and activate the authorisations “Call queue”, “Call waiting protection” and, if necessary, “Call forwarding”.
If users belong to this group, a queue will be activated automatically for all telephone numbers assigned to them.
14.1.2 Call Forwarding
Forwarded calls of the forwarding type “Immediately” and “On busy” have priority over queues. The queue of the forwarding telephone is not used for forwarding calls in this manner.
During the configuration of this type of call forwarding, the contents of the queue are not transferred to the target terminal. If there are still calls in the queue when the call forwarding function is activated, these calls can only be accepted on the source terminal.
147
Call Queue Examples of Use
If a call is to be forwarded “After delay”, it enters the queue. If the call has not been answered before the delay period expires, it will be forwarded to the target terminal and can then be answered there.
14.1.3 Pickup
The functions “Pickup” (from a pickup group) and “Pickup selective” can be used together with queues. A user who accepts a call using “Pickup” or “Pickup selective” picks up the next call from the queue.
14.1.4 Hunt Groups
Hunt groups of the “parallel” type are usually used together with queues, with the queues of each telephone in the group being synchronised to each other. When a call to the number of the hunt group arrives, the call enters all parallel queues. If a call from one of the queues is answered, it is removed from all other parallel queues.
14.2
Examples of Use
Note: In the following examples it is assumed that a U pn
interface card has been installed (in an OpenCom 130 or an
OpenCom 150). Ports on a U pn
interface card are DECT enabled, so that DECT base stations can be connected to operate cordless system terminals.
14.2.1 Enquiry Station for an Operator with Two
System Telephones
The operator switches all incoming calls and can either work on the
OpenPhone 65 or the mobile terminal, the OpenPhone 27.
Configuration
■ Configure the system access or access for multiple terminals under PBX Confi- guration: Ports: S
0
.
148
Call Queue Examples of Use
■ Configure the OpenPhone 65 and e.g. a RFP 22/24 under PBX Configuration:
Ports: U pn
.
■ Configure a trunk key for the OpenPhone 65 under PBX Configuration:
System telephones.
■ Configure the OpenPhone 27 under PBX Configuration: Ports: DECT-PP and assign the OpenPhone 27 its own telephone number. Check in the
OpenPhone 27.
■ Under PBX Configuration: Call Distribution: Incoming or PBX Configu-
ration: Call Distribution: Incoming PTP route all incoming calls to the number of the OpenPhone 65 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 27 to this user.
■ Activate
Call wait. prot.
(call waiting protection) on both terminals in the
Protection
menu.
■ Configure a function key on the OpenPhone 65 which activates/deactivates a
“call forwarding immediately” to the telephone number of the mobile
OpenPhone 27 (in the menu
Call diversion: 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 how many calls there are in the queue.
If the operator wants to leave the workstation and take along the enquiry station, call forwarding to the OpenPhone 27 is activated by pressing a function key. Calls which are in the OpenPhone 65 queue must still be answered on this telephone.
149
Call Queue Examples of Use
New calls are signalled on the mobile OpenPhone 27 or enter its queue, allowing the OpenPhone 27 to be used as a mobile enquiry station.
On returning to the workstation, the operator deactivates call forwarding by pressing a function key. Calls which are already in the queue are switched on the mobile OpenPhone 27. New calls are signalled on the OpenPhone 65 or enter its queue.
14.2.2 Group of Three Enquiry Stations
The enquiry stations switch all incoming calls. Incoming calls are administered in queues. Depending on the number of arriving calls, one to three enquiry stations in this group are manned. The enquiry stations are each equipped with an
OpenPhone 65.
Configuration
■ Configure the multi-terminal access or the system access under PBX Configu- ration: Ports: S
0
.
■ 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 Configuration: Devices: System tele-
phones.
■ Configure a hunt group of the “parallel” type under PBX Configuration:
Groups: Hunt Group, and include the three telephone numbers of the trunk keys in this hunt group.
■ Under PBX Configuration: Call Distribution: Incoming or PBX Configu-
ration: Call Distribution: Incoming PTP route all incoming calls to the number of the hunt group.
■ In the Configurator, create a new group called “Operators” under User
Manager: User groups. Activate “Call queue” and “Call waiting protection” for this group.
150
Call Queue Examples of Use
■ In the User Manager, configure a user for each of the three operators and assign these settings to the user group called “Operators”. Allocate each User the telephone number of the trunk key of their system telephone.
■ Activate
Call wait. prot.
(call waiting protection) on all three terminals in the
Protection
menu.
■ Program a function key with the function “Sign on/sign off from hunt group” on the three system telephones (in the menu
Calls: Hunt group
).
Use
Incoming calls are signalled in parallel to all signed-on enquiry stations. If the enquiry stations are busy, the incoming call joins the queue on each of the terminals in the hunt group. If one of the enquiry stations accepts a call from the queue, the call is removed from the queues of all the other enquiry stations. The display at each enquiry station (OpenPhone 65) indicates how full the queue is.
If attendants leave the station, they sign off from the hunt group by means of a function key. In contrast to Example 1, further calls do not have to be processed after the sign-off, as the calls are also registered in the queues of the other signedon enquiry stations.
Note: When the last enquiry station remaining in the hunt group signs off, further callers will hear the busy tone.
151
Multi-Company Variant
15. 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 multi-company 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 or SIP account is uniquely assigned to a company so that incoming external calls can be transferred to the correct internal subscriber.
■ For each company, every route can have its own code. For example, it is possible to activate different routes with the code “0” for different companies. This enables separate charging for outgoing external calls, for example.
■ An individual exchange (“operator”) can be set up for each company.
■ Each company can maintain the communication data of its business partners in its own company telephone book.
■ The charges can be billed individually for each company.
152
Multi-Company Variant Configuring the Multi-Company Variant
15.1
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 multicompany variant, the communications system behaves in exactly the same way as the single-company variant. This is particularly of interest to users who want to expand their own system and at the same time operate it in a group.
The process in brief:
1. The feature must be activated (see Activating the Multi-Company Variant starting on page 153).
2. The required companies must be set up (see Configuring and Managing Com-
3. The users of the OpenCom 100 are assigned to the individual companies (see
Assigning Users starting on page 154).
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 uni-
quely assigned to the companies (see Assigning Trunk Groups/SIP Accounts starting on page 155).
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 155).
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 exchange (see
Configuring the Company Exchange starting on page 156).
15.1.1 Activating the Multi-Company Variant
To be able to configure several companies in the OpenCom 100, the “Multicompany variant” (OpenCompany 45) program package must first be activated.
This is done in the Configurator on the Web console in the SYS Configuration:
Licences menu. The licence confirmation you received with the program package contains all the information you require about how to proceed.
153
Multi-Company Variant Configuring the Multi-Company Variant
Only when this package has been activated are the fields required to configure the multi-company variant available in the other menus of the Web console, for example in the User Manager: User groups menu or in the PBX Configuration:
Trunks menu.
15.1.2 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: Companies menu:
■ A new company is created in this menu using the command New. Each company can be given a name up to 20 characters long. This name is then displayed in all configuration dialogue boxes in which company-specific settings can be defined.
■ In this menu a company can be deleted again using the command Delete. If a company is deleted which is still used at other places (in the user groups, for example), the respective configuration is changed to the default company.
■ The name of the default company can be changed, but the default company itself cannot be deleted.
15.1.3 Assigning Users
For each user you must define the company to which they belong. This assignment determines, for example, which company telephone book the user has access to and which company-specific configuration data apply to them.
As the OpenCom 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.
154
Multi-Company Variant Configuring the Multi-Company Variant
When setting up a new User group (in the User Manager menu), you will find that the default company is predefined; another company can be assigned as long as no other companies have been set up.
15.1.4 Assigning Trunk Groups/SIP Accounts
Connections of the same type and in the same direction are arranged in a trunk group (e.g. S
0 multi-terminal connections). To be able to correctly transfer incoming calls to the members of the configured companies (the users) via the lines of a certain trunk group of the OpenCom 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. SIP accounts can also be assigned to a company.
The assignment of trunk groups to companies is done in the PBX Configuration:
Trunks: Bundle menu. The assignment of trunk groups to companies is done in the PBX Configuration: SIP: SIP accounts.
For outgoing external calls which users set up via the lines of their company’s trunk group/SIP account, the assignment of the trunk group to the company is irrelevant: the charges are assigned according to the “source” principle.
Charges are billed to the company to which the user belongs who set up the connection. The OpenCom 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/SIP account was seized. For more information, please see the following section.
15.1.5 Allocating Routing Codes
Routes are used for automatic and selective seizure of trunk groups or connections for external calls. It is possible to seize a route by predialling a code.
In the PBX Configuration: Trunks: Route menu, you can define which company can seize each route. An individual code for the seizure is allocated per route for each company. The OpenCom 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.
155
Multi-Company Variant Working with the Multi-Company Variant
15.1.6 Configuring the Company Exchange
An internal telephone number must be set up for each company which represents the exchange, i.e. “the operator”. The calls to specific extensions arriving at the exchange are routed to this number, for example, as are all external calls where the called subscriber (a user who belongs to this company) cannot be reached, as in the case of a timeout.
A company exchange is set up in the PBX Configuration: Operator menu. In this menu, you can specify an internal telephone number for each company and time group which then represents the exchange for this company.
15.2
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 multi-company variant. These features can be used to the same extent and can be used in exactly the same way.
The following section describes the features additionally available to the users in the multi-company variant.
15.2.1 Company Telephone Book
An individual company telephone book can be created for each company. In addition to this, “personal” and “central” telephone books exist:
■ A personal telephone book is available for each user.
■ The central telephone book can be used across the companies by all users of the OpenCom 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.
156
Multi-Company Variant Working with the Multi-Company Variant
Users can also use the telephone book of their company with the OpenCTI 50
Web applications and phone book, assuming they are authorised to use these applications.
In addition, it is also possible to assign a user group with the authorisation to edit foreign company telephone books. This authorisation is useful if members of this group - e.g. the “Administrators” - service the entire system. Foreign telephone books can only be edited in the Configurator in the Phone Book menu.
The number of entries in a company telephone book is unrestricted. The
OpenCom 100 can manage up to 2,000 entries in all telephone books (in the central, personal and company telephone books).
15.2.2 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.
15.2.3 Billing Charges per Company
In the Costs Web application you can output the charges for each company.
Users who are authorised to use this application can view the charges for each company.
157
Configuring the PC Software PC Offline Configuration
16. Configuring the PC Software
Further possibilities of use can be implemented on a workstation PC with the
Windows operating system by installing drivers and programmes. You can find the installation programmes required for this on the product CD that comes with the
OpenCom 100.
Proceed as follows to install extra software:
1. Log on under Windows NT or Windows 2000/XP as the administrator.
2. Insert the product CD.
If your PC is suitably configured, the CD will start automatically. Otherwise select Run from the Start menu. Click on the Browse button to look for the program “cd_start.exe” on the CD. Confirm this with Open and OK.
3. Select the required option from the start interface. Follow the program instructions.
Further instructions for various options that are available are given below.
16.1
PC Offline Configuration
The offline configurator is a reduced system software that is executable under the operating systems Microsoft Windows 2000 or Microsoft Windows XP. With the offline configurator it is possible to create system configurations for various TCsystem types – without a connection to the live system. You configure a virtual system and later, aided by the data backup, transfer the configuration to the running system.
Installing the offline configurator
1. Display the product CD contents in Windows Explorer. Search the “\OFC\” installation directory for the offline configurator.
2. Start the StartCenter installation program by double-clicking on “Setup.exe”.
Following the installation assistant’s instructions. Select the appropriate installation directory or apply the default.
158
Configuring the PC Software PC Offline Configuration
3. On the product CD, in the offline configurator installation directory, you will find ZIP archives for various TC-system types. Copy the desired ZIP archives to the installation directory.
4. End the installation with a function test. With a double-click on the newly created desktop icon, start the StartCenter program. Select from the folddown selection the desired TC-system type. Available offline configurators are now displayed as symbols. Double-click on a configurator symbol and select from the dialogue Start with Factory settings. The offline configurator starts with an command window. Open a Web browser and in the address line enter:
“http://localhost/”. Confirm with enter.
5. Configure the virtual system as usual. Using the data backup, you can save the configuration.
6. Activate the command window. End the offline configurator with the window’s menu command Close.
To maintain multiple different installations, you can copy further offline configurators to new directories of your hard-drive. Change between the directories by selecting the command Extras: Setup in the StartCenter program. Select the corresponding Working Directory in the Setup dialogue. You will find further explanations in the StartCenter online help.
Notes
■ The ITC-system serial number to which the configuration is later to be transferred is queried when starting the offline configurator. You will recognise this by the caution symbol in the left symbol-bar. Click on this symbol. Enter the serial number into the input field that opens.
The serial number is required to activate program packages requiring licenses in the offline configurator (in menu SYS Configuration: Licenses). The serial number can be obtained for the ITC-system’s Configurator in the System Info:
Versions menu.
■ If there is a firewall installed on the workstation computer, then a warning will be displayed. This warning shows that the computer is now ready-to-receiver requests for the offline configurator’s web-server service. You must permit the web-server service, for example by activating the option For this program do
not display this notification again.
159
Configuring the PC Software Setting up TAPI
■ If there is an existing web-server service installed on the workstation computer, then you must enter a new port number in the Setup dialogue of the program
StartCenter, for example 8080. In the Web browser, the address line input is then: “http://localhost:8080/”. When using different port numbers you can also start multiple offline configurators simultaneously on one workstation computer.
■ If for the Web browser there is a proxy activated, then you might have to enter the computer name “localhost” into the exceptions list (No proxy for …).
■ During deinstallation of the program StartCenter, the entire installation directory with all its sub-directories is deleted. Backup the necessary offline configurators before uninstalling.
16.2
Setting up TAPI
With a TAPI (Telephony Application Programming Interface) you can operate a CTI application (computer telephony integration). Here, the CTI application uses the services of the OpenCom 100 with the help of the TAPI driver installed on a
Windows PC.
Many telephony functions, such as enquiry, toggling, three-party conference, pickup, call protection and call forwarding can be controlled using appropriate TAPIcompatible software.
Requirements
You require an active IP network connection between the PC and the communication system. CTI functions can be used only in conjunction with system telephones.
You must therefore have configured at least one user for a system telephone. In addition, you require a TAPI 2.1-compatible CTI application, for example the
Phone Dialer included in the Windows operating system.
Installing the TAPI Driver
1. Call up the start mask from the product CD (see Configuring the PC Software on page 158).
2. Select Software: TAPI Service Provider from the start mask and follow the program instructions.
160
Configuring the PC Software Setting up TAPI
Configuring the TAPI Connection
Note: Under Windows NT or Windows 2000/XP you should log on as the user for whom you want to configure the TAPI connection.
1. In the Start menu, select Settings: Control Panel. Double-click on the Tele-
phony icon (Phone and Modem Options icon under Windows 2000/XP).
2. Change to the Telephony Drivers tab (Advanced Options tab under
Windows 2000/XP).
3. From the list of installed driver software, select OpenCom 100 Service Pro-
vider and click on Configure.
4. In the following dialogue you will find a list with the configured connections for the user who is currently logged on. Click on New.
5. In the following dialogue you provide information for the new connection. In the Connection name box you can enter a descriptive name for the connection. In the CTI server box you must enter the DNS name or the IP address of the OpenCom 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 Pro-
grams: Accessories). A manual start of the program file “Dialer.exe” in the
“C:\Program files\Windows NT” folder is possible also.
2. In the Tools menu, select the item Connect using... to select the system telephone that is to use the CTI application. Under Windows 2000/XP you select
161
Configuring the PC Software Setting up NET CAPI the item Options from the Edit menu. In the Lines tab you then select the system telephone from the Phone calls list.
3. Enter a telephone number in the Number box and confirm with Dial. Under
Windows 2000/XP you first click on the Dial icon and in the subsequent dialogue activate Phone call.
4. The number you entered is displayed on the selected system telephone. Lift the receiver to start dialling.
Note: This note is not relevant to Windows 2000/XP. If the
“Phone Dialer” program is not installed, you will have to install it. To do this, you open the Control Panel and click on
Software. In the Windows Setup tab you activate the Con-
nections component.
16.3
Setting up NET CAPI
With a CAPI driver (common application programming interface) Windows programmes are able to access services and functions of an ISDN card. With a network-based CAPI, the OpenCom 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.
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 product CD (see Configuring the PC Software on page 158).
2. Select Software: NET CAPI Driver from the start mask and follow the program instructions.
162
Configuring the PC Software Using the Systray Display
Configuring the NET CAPI Driver
The NET CAPI driver requires an extra internal number so that the “virtual ISDN card” on the OpenCom 100 can be addressed:
1. Go to the Configurator, PBX Configuration: Devices: CAPI-ISDN menu. Click on Change.
2. Activate the Status check box. Enter at least one unassigned, internal number in the boxes under Parameters. Confirm your entry with Assign.
3. Go to the Configurator, User Manager: User menu. Select one of the users shown. Enter the number just assigned in one of the boxes No. 1 to No. 10.
Confirm your entry with Apply.
4. If it is to be possible to call the “virtual ISDN card” externally, or if external calls are to be possible, the number must be included in call distribution (Configu-
rator, PBX Configuration: Call Distribution menu).
5. After installing the NET CAPI driver, you will find an extra icon on the right side of the Windows Start bar. Click on this icon with the right mouse key. Select the
Log-on command from the menu.
Note: In the subsequent dialogue you must log on NET CAPI first with the user (user name and password) for which you configured the CAPI telephone number in the User Manager
(see Step 3).
You will find further information on the working of the NET CAPI driver and CAPI application programmes on the product CD.
Note on sending faxes
The NET CAPI can not address an analogue Group-3 fax. Use a CAPI-compatible modem-simulation driver or connect an analogue modem or analogue modem card to one of the OpenCom 100’s internal a/b ports for sending faxes.
16.4
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 a WAN, a RAS or a Branch connection via ISDN is active. It is also possible to display the current occupancy of the trunk lines.
163
Configuring the PC Software Browser for OpenCTI and OpenHotel
Requirements
To use the systray display, you must first install TAPI; see Setting up TAPI starting on page 160.
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 product CD.
Installing the systray display
1. Call up the start mask of the product CD (see Configuring the PC Software on page 158).
2. From the start mask, select Software: Install Systray. Follow the program instructions.
3. Start the program with Start: Run and the configuration dialogue is displayed.
Select one of the entries displayed under Existing PBXs. Enter your user name and password in the boxes under Log-on.
4. If you activate the Autostart check box, you will see the systray display even after restarting your PC.
5. Confirm the entries in the configuration dialogue with OK and the systray display logs on for the OpenCom 100.
6. Right-click on the systray display in the Start bar. Select Configu-
ration to call up the configuration dialogue. Select Network Con-
nections or Trunk Lines to produce a status dialogue.
16.5
Browser for OpenCTI and OpenHotel
You can simplify the daily use of the OpenCTI and OpenHotel Web applications using the Web browser especially adapted for the OpenCom 100. Each time the workstation is restarted, this browser program can automatically start and log you in. This means that the applications are always operational and can be accessed using the icon in the information area of the task bar.
164
Configuring the PC Software Setting up Video Telephony
Installing the browser
1. Call up the start mask from the product CD (see Configuring the PC Software on page 158).
2. From the start mask, select Software: Install Browser for OpenCTI or
Software: Install Browser for OpenHotel. Follow the program instructions.
3. Follow the program instructions.
After installing the browser, there is a new menu entry in the Windows start menu under Programs: OpenCTI Browser respectively Programs: Hotel Starter.
Further information can be found in the online help of the browser program. To view this, click the top left corner in the OpenCTI-browser’s program window on the system menu symbol or on the symbol in the information area of the task bar.
Select the Readme command. You will find the OpenHotel’s readme in the installation directory of this browser program.
Note: Both browser programmes can be used simultaneously.
16.6
Setting up Video Telephony
You can use the OpenCTI to switch on the video function during an internal call.
To be able do this, the Microsoft NetMeeting 3.0 program must be installed and set up on all participating workplace computers.
Note: NetMeeting is already pre-installed on the Microsoft
Windows 2000 and XP operating systems.
Set up Microsoft NetMeeting 3.0
1. Connect a standard web cam to the workplace computer and install the driver.
2. In the Windows Start menu select Run and enter: “conf.exe”. Confirm your selection with OK.
3. Follow the instructions of the Install Wizard. Registration in an Internet directory is not necessary and is not recommended. Select the installed web cam and exit the Install Wizard.
165
Configuring the PC Software Synchronising the PC Clock
4. Run a functionality test. To do this, start the NetMeeting program. Click on the call button. Under Address enter the IP address or DNS host name of a external station. Confirm your selection with Call.
Note: If Firewall software is installed on the workplace computer, a warning will now appear. This shows that the computer is now ready to receive the NetMeeting. You must allow the NetMeeting, by activating the Do not show this
message for this program again option for example.
16.7
Synchronising the PC Clock
With the network service SNTP (simple network time protocol) it is possible to synchronise the internal clock of a PC with the time of the OpenCom 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 programmes offered for downloading on the Internet. Configure the OpenCom 100 as an SNTP server for such programmes.
SNTP with Windows 2000
Here you configure the SNTP server as follows:
1. Log on as the administrator. Start the Command Prompt under Start: Pro-
grams: Accessories.
2. Enter the command line “net time /setsntp:192.168.99.254”. Confirm with the enter key. This command changes the setting for the SNTP server address in the system registry. Close the command line.
166
Configuring the PC Software Address Queries using LDAP
3. Open the Services dialogue under Start: Settings: Control Panel: Administ-
ration. Set the autostart type of the Windows Timer service to Automatic.
Start the service with Process: Start. Every time the service starts, the PC clock is synchronised with the time of the OpenCom 100.
Please note: In a Windows domain network, the PDC server (primary domain controller) should automatically assume the function of the timer.
SNTP with Windows XP
Here you configure the SNTP server by double-clicking on the time in the Start bar.
Enter the OpenCom 100 as the Server in the Internet time tab.
16.8
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
TM
, a Microsoft
TM
e-mail program, as follows:
1. Call up the Accounts command in the Tools menu.
The Internet Accounts dialogue box will then open.
2. Click on Add. Select the Directory Service command from the pop-up menu.
The Internet Connection Wizard dialogue box for Internet access will then open.
3. Under Internet directory (LDAP) server, enter the address of the
OpenCom 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.
167
Configuring the PC Software Address Queries using LDAP
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.
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.
168
Configuration Guide
17. 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:
■ 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 Settings: This chart guides you through the configuration of the LAN-to-LAN settings.
■ Configuring E-Mail: This diagram tells you how to create the requirements needed for configuring the OpenCom 100 e-mail access function.
■ Configuring E-Mail Access: This overview provides instructions on configuring the OpenCom 100 e-mail access server.
169
Configuration Guide
17.1
Overview
Yes
Connect the OpenCom and the configuration PC to the network
Ethernet network
(LAN) exists?
Yes
No
Cross-connected ethernet cable available?
Connect the configuration
PC to the OpenCom LAN port.
Enable DHCP.
No
Connect the configuration
PC to the OpenCom COM port.
Generate the Dialup Networking entry with “occonfig”.
Start the OpenCom configuration service via your Web browser.
Enter the OpenCom address, for example “http://192.168.99.254”.
User Manager
PBX Configuration
Yes
Create the user groups and users.
Set the system data. Select the access type. Connect the S
0
, U pn
and analogue devices and configure them.
Configure the call distribution scheme.
Configure the Least Cost Routing function: zones, network providers and holidays.
LCR Configuration
Configure OpenCom
Least Cost Routing function?
No
Configure OpenCom network functions?
Yes
LAN Configuration
RAS Configuration
No
Save data
Flowchart: Overview
Dial in (RAS)?
No
Connection (LAN)?
No
Internet?
No
E-mail?
No
Yes
Yes
Yes
Yes
Branch Configuration
WAN Configuration
E-Mail Configuration
Finished
170
Overview
Configuration Guide
17.2
PBX Ports
Do you have ISDN terminals that you wish to operate on an S
0
interface?
Define the access type
Set the access type (multiterminal access and/or system access).
Define the external
S
0
interfaces
Set the external S
0
interfaces and enter the telephone numbers assigned by your network provider.
S
0
terminals Yes
Define the internal S
0 interfaces
Set the internal S
0
interfaces and enter the internal telephone numbers.
No
Do you want to operate system telephones or
DECT terminals?
U pn
terminals Yes
Configure the
U pn
interfaces
Enter the U pn
interfaces and enter the internal telephone numbers.
No No
DECT terminals
Do you want to operate
DECT terminals on the
OpenCom?
Yes
Configure the DECT terminals
Check in the DECT terminals and enter the internal telephone numbers.
Do you want to operate analogue terminals
(e.g. a fax machine)?
Analogue terminals Yes
Configure the a/b interfaces
Set the analogue interfaces and enter the internal telephone numbers.
No
Do you want to use a sensor contact on the
OpenCom (e.g. for a door opener)?
Sensor Yes Configure the sensor
Enter the internal telephone numbers for the time groups of the sensor.
No
Do you want to run the
OpenCount program?
COM Yes
No
Finished
Flowchart: Configuring the PBX Ports
Configure the COM interface
Select the “connection data” option.
PBX Ports
171
Configuration Guide
17.3
LAN
Do you have a computer network?
LAN
Yes
Host name
No
Assign a name to the OpenCom.
Finished
Do you have a DHCP server in your network?
Activate the OpenCom
DHCP server.
Enter the Ethernet-IP configuration for the OpenCom.
Enter the address range of the client computers in your network.
Do you have a DNS server in your network?
Specify the IP address of the OpenCom under “Domain Name Server”. This is transferred as the DNS server to the client computers via DHCP.
Enter the address range for the RAS accesses.
PPP addresses
Finished
Flowchart: Configuring Easy Access
DHCP
No
OpenCom
DHCP server
Yes
The OpenCom takes the settings from your DHCP server
Ask your network administrator for the address range for the RAS accesses. For this purpose, your administrator must reserve an IP address range for the RAS accesses.
IP address
Network mask
Gateway address
DHCP adresses
Domain name
Client computers are informed of this gateway address via DHCP as a gateway.
Enter the domain name. This name is transferred to the client computers as the domain via DHCP.
DNS
No
OpenCom as
DNS server
Yes
Specify the IP address of your internal DNS server under “Domain Name
Server”. This is transferred as the DNS server to the client computers via DHCP.
Register internal DNS
172
LAN
Configuration Guide
17.4
WAN Settings
Do you want to configure a new Internet provider?
Enter your provider's dial-in data.
“SYS Configuration: System:
Country” = “German”?
No
Your own ISP
Yes
T-Online
Provider-New: Provider,
Telephone Number,
User Name and Password
No
Yes
T-Online: Telephone number,
Access identification, T-Online number, Co-user number and Password
Select a provider from the list
Select one of the default providers in
“NET Configuration:
WAN”.
Specify the IP address of the DNS in the Internet.
Specify a standard POP server and a standard SMTP server.
Specify the maximum time of inactivity after which the connection to the ISP is cleared down.
Domain Name Server
Mail input server and mail output server
Maximum idle time
Configure T-Online in “NET Configuration: WAN: Provider”. You will obtain the access data when you register.
Activate the status and select the provider
Configure the ISP in “NET Configu-ration:
WAN: ProviderConnections: ISP”.
DSL
(PPPoE)
No
Yes
Is your IP address allocated by your provider?
PPP
Yes
Dynamic
Yes
Enter the IP address and network mask you wish to obtain from your provider.
Your own telephone number
Max. connection time per month
Specify the maximum connection time for one month.
No
No
HDLC
Yes
No LAN
Yes
IP address
Network mask
Specify the gateway for the Internet connection.
Gateway
No
Maximum idle time
Filter list IN
Filter list OUT
Specify the maximum time of inactivity after which the connection to the ISP is cleared down.
Select the filter lists. Filter lists are created in “NET Configuration: Firewall”.
Finished
Flowchart: Configuring the ISP Settings
ISP cannot be configured.
WAN Settings
173
Configuration Guide
17.5
RAS Settings
Have you made the network settings for the OpenCom ?
LAN No
NET Configuration:
LAN
Configure the network settings for the OpenCom.
Configure the RAS access of the
OpenCom. “NET Configuration: RAS”
Yes
RAS Settings
Select from PAP,
CHAP and CLID.
Status
Telephone number
Activate the RAS access.
Specify the telephone number for which the RAS access should be configured.
Authorisation
Number of connections
Specify how many simultaneous connections are possible via this access.
Select the filter lists. Filter lists are created in “NET
Configuration: Firewall”
Filter list IN
Filter list OUT
Have you created users with RAS access rights?
Users
Yes
No
User Manager: Users and User Groups
Configure users that have RAS access rights.
Add internal telephone number to the incoming call distribution scheme.
Finished
Flowchart: Configuring the RAS Settings
174
Configuration Guide
17.6
Branch Settings
Have you made the network settings for the OpenCom?
LAN No
NET Configuration:
LAN
Configure the networksettings for the OpenCom.
Yes
Configure the LAN-LAN connection.
“NET Configuration: Branch”
Protocol
Telephone number local
IP address local
Network mask local
Select between PPP and HDLC transparent.
Enter the internal telephone number.
Enter the local IP address.
Enter the local network mask.
Yes CLID
No
User name local
Password local
Authorisation method of the local
LAN: CLID, PAP or CHAP?
Specify the user name with which the remote LAN can access a destination.
Specify the password with which the remote LAN can access a destination.
Telephone number remote
IP address remote
Network mask remote
Specify the telephone number of the remote LAN access.
Specify the IP address of the remote LAN.
Specify the network mask of the remote LAN.
Yes CLID
Authorisation method of the remote
LAN: CLID, PAP or CHAP?
No
User name remote
Password remote
Direction of connection
Maximum connection time per month
Maximum idle time
Add internal telephone number to the incoming call distribution scheme.
Specify the user name with which the remote LAN can be accessed.
Specify the password with which the remote LAN can be accessed.
Select the direction of the connection.
Specify the maximum number of minutes per month the connection to the remote LAN can be set up for.
Set the maximum idle time after which a connection to the remote LAN is cleared down.
Finished
Flowchart: Configuring the LAN-to-LAN Settings
Branch Settings
175
Configuration Guide
17.7
E-mail Function
Have you made the network settings for the OpenCom?
LAN No
Configure the network settings for the OpenCom.
NET Configuration:
LAN
Yes
E-mail Function
Do you want to use e-mail from the Internet?
Internet
No
Yes
Configure your Internet access.
NET Configuration:
WAN
Has an internal e-mail server been configured in your LAN?
LAN No
No e-mail use
Have you stored the users to be notified?
Yes
Do you want to be notified of e-mails on your system telephones?
Notification
Yes
Users
No
No
Create the users and activate e-mail notification. Also enter the users' e-mail addresses.
User Manager:
Users, User Groups and User Accounts
Yes
Finished
Set the polling time periods.
NET Configuration:
E-Mail Access
Finished
Flowchart: Configuring the E-mail Function
176
Configuration Guide
17.8
E-mail Access
Do you have access to a mail server in your network or in the Internet?
Mail server No
Configure your network/
Internet access.
NET Configuration: LAN or WAN
Yes
E-mail Access
Do you have created mail account polls in the “User Manager: User accounts”?
User accounts No
Set up user accounts in the User Manager.
User Manager: User Accounts
Yes
Configuration of e-mail access settings
Specify the time intervals in which the
OpenCom is to poll all mail accounts from the standard POP server.
Maximum number of e-mails per user account
Enquiry interval
Start and end times:
Monday to Friday 1st starting time
Monday to Friday 1st ending time
Monday to Friday 2nd starting time
Monday to Friday 2nd ending time
Saturday 1st starting time
Saturday 1st ending time
Saturday 2nd starting time
Saturday 2nd ending time
Sunday 1st starting time
Sunday 1st ending time
Sunday 2nd starting time
Sunday 2nd ending time
Specify the maximum no. of e-mails per user account that should be temporarily stored by the OpenCom.
Define the time windows in which the
OpenCom should check the mail accounts for new messages in the time intervals that have been set. You can define two time windows for each working day (Monday to Friday), and two each for Saturday and Sunday.
Finished
Flowchart: Configuring E-mail Access
177
Frequently Asked Questions
18. 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
Power Good LED
LAN LEDs
(Ethernet switch)
AC adapter
LAN LEDs
Activity LED
Basic module Add-on module
Position of LEDs on the OpenCom 130
Power Good LED
LAN LEDs
Activity LED
Position of LEDs on the OpenCom 131
178
Frequently Asked Questions General/Hardware
Power Good LED
Activity LED
LAN LEDs
LAN LEDs (Ethernet-Switch)
AC adapter
Position of LEDs on the OpenCom 150
With the OpenCom 150 Rack, the LEDs for LAN0 and LAN1 are placed on the front panel.
18.1
General/Hardware
The OpenCom 100 is not functioning.
Check whether the plug-in power supply is properly connected (OpenCom 130). If an add-on module is installed: Make sure the mains plug is properly connected.
Plug another device into the mains socket to check whether there is any voltage.
The mains plug is connected, the mains socket is supplying output, but the
OpenCom 100 still does not function.
DANGER!
This device contains hazardous voltages. To make the system dead, remove the power plug and the plug-in power supply from the socket.
Take the housing cover off. Is the “Power Fine” LED illuminated?
If not, contact your service centre or an authorised dealer. The AC adapter plug of the OpenCom 100 may be defective.
179
Frequently Asked Questions Telephony
After restarting the OpenCom 100, nothing is indicated on the displays of any connected terminals.
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 ori-
ginal factory setting (refer to the chapter entitled Resetting the System Data starting on page 84).
18.2
Telephony
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
0
ports are configured correctly
(PBX Configuration: S0 menu):
– Configuration of System- / Multi-terminal access OK?
– Port is connected to the NTBA?
– Faultless Cabling?
– Terminating resistors properly configured?
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
0
port is set for an NTBA in the system configuration; this additional port will be used first to seize a trunk line.
Deactivate the corresponding S
0
port in the Configurator (PBX Configuration:
S0 menu).
180
Frequently Asked Questions Telephony
One of the telephones is not functioning at all.
Make sure the telephone has been properly connected. Please read the explanations under Port assignment, termination, cable length starting on page 56.
Check also whether the appropriate port has been configured correctly in the
Configurator (PBX Configuration: Ports menu).
It is not possible to make external calls with one of the telephones.
Check whether a user is configured for the telephone. Otherwise the settings of the Guests user group are valid for the telephone. To standard, this user group has no external call authorisation.
Make sure the user configured for this telephone belongs to a user group with external line access (Configurator, User Manager: User groups menu).
Check also whether the internal call number of this telephone has been configured for incoming call distribution (Configurator, PBX Configuration: Call Dis-
tribution menu).
One of the features (e.g. call diversion) on one of the telephones cannot be used even though the feature has been configured in the Configurator of the
OpenCom 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.
Nothing is indicated on the display of one of the connected ISDN telephones.
You have connected the ISDN telephone to an external S
0
port (RJ-45 socket).
These ports are intended for connection to the NTBA only. Connect the telephone to an internal S
0 port (pressure terminal).
Calls can be made but not received with one of the ISDN telephones.
The internal call number that has been configured for this ISDN telephone in the
Configurator (PBX Configuration: Ports: S0 menu) must also be configured as an MSN on the ISDN telephone itself. For further information, refer to the User
Guide of your ISDN telephone.
181
Frequently Asked Questions Telephony
An ISDN telephone always rings, if another telephone on the S
0
bus is being called.
This case also requires configuring the MSN on the ISDN telephone (see above answer).
It is not possible to configure Call Distribution: Outgoing for multi-terminal access.
You have configured multi-terminal access and system access in parallel. All outgoing calls are therefore established via system access, and outgoing call distribution can be configured for system access only (Configurator, Call Distribution menu).
A specific MSN can be seized for individual calls by means of a code number procedure. For further information, refer to the “OpenCom 100, Operation on
Standard Terminals”user guide.
What are some of the causes for problems when sending and/or receiving faxes?
In frequent cases, the reason may be found in a problem with the ISDN-L1 reference clock distribution. The L1 clock is delivered from the network provider. An unclean L1 clock distribution and the introduced signalling jitter is overheard by the human ear. Nevertheless, data and fax transmissions may be disturbed by the jitter. Please check, which ISDN lines will deliver the L1 clock. Details can be found
under L1 Clock starting on page 129.
The fax data transfer possibly is routed via a compressing VoIP connection. Please verify, if the a/b port is configured with the “Fax” setting. For the VoIP connection, select a VoIP profile which includes the non-compressing G.711 codec.
182
Frequently Asked Questions DECT
18.3
DECT
Note: In the following explanations it is assumed that a U pn interface card has been installed (in an OpenCom 130 or an
OpenCom 150).
The LED of the RFP 22/24 base station is flashing, but none of the DECT devices is functioning.
Make sure the terminal setting for the corresponding U pn
port is set to RFP 22/24
(Configurator, PBX Configuration: Ports: U pn
menu).
If multiple RFP 22/24 base stations are installed, the blinking LED indicates that synchronisation is not finished.
The LED of the RFP 22/24 is continuously lit up, but one of the cordless DECT devices is indicating “No connection”.
You have not registered this DECT device. Configure a port in the Configurator and start the enrolment procedure (PBX Configuration: Devices: DECT Phones menu).
Is it possible to increase the time for the enrolment procedure?
You must manually enter the IPEI of the DECT device in the Configurator. The enrolment time is then increased to one hour (PBX Configuration: Devices: DECT
Phones menu).
Another manufacturer’s DECT device is not functioning.
Check whether the DECT device supports the DECT GAP standard. In the Configu-
rator, also make sure GAP is set for this DECT device (PBX Configuration:
Devices: DECT Phones menu).
The startup procedure of the RFP 22/24 take a long time? What is the reason?
This behaviour may indicate a problem with the reference clock. Refer also to What
are some of the causes for problems when sending and/or receiving faxes? starting on page 182.
183
Frequently Asked Questions LAN
18.4
LAN
Why is it not possible to establish a network connection with the
OpenCom 100?
Check whether the LEDs for the switch and the PC’s network card are indicating a connection.
Check the LEDs for the LAN functions of the OpenCom 100. The green LAN LED at the top indicates whether the network cable has been properly connected. The red LAN LED indicates whether there is any network traffic on the line.
If you have installed an add-on module (in an OpenCom 130), also check the LAN
LEDs of the Ethernet switch. The Ethernet line between the basic module (LAN port) and the add-on module (LAN1 port) are properly connected if the centre LED lights up. The Ethernet line between the hub of the corporate network and the
LAN0 port is properly connected if the right-hand LED lights up.
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).
How can I determine the IP address of the OpenCom 100?
To find out what the IP address is, enter the code number *182 on one of the connected system telephones.
The code-number procedure *183 also displays the network mask.
The network connection is functioning, but nothing is displayed in the browser.
Enter the complete IP address of the OpenCom 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.
184
Frequently Asked Questions Internet
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.
Our network has grown over time, with several segments connected by one central router. How can PCs from all segments connect to the OpenCom 100?
If several routers are configured for your network in different segments, you can enter extra static routes in the NET Configuration: LAN: Routes menu.
In our network the OpenCom 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 host assignment entries in the Configurator (NET Configuration: LAN: Hosts menu).
Create a static DHCP entry for each host assignment in the NET Configuration:
LAN: DHCP Server menu. Activate “Dynamic and static address” for the DHCP server.
18.5
Internet
I cannot access our company Web site.
Outside your system, your company Web site is accessed at “www.firm.com”, but in the Configurator you have entered “firm.com” as the domain. Your company’s site URL thus counts as an internal URL and can only be accessed by entering the direct IP address. If required, change the domain setting in the NET Configu-
ration: LAN menu.
Why do some Internet services not work even though they can be used when dialling in directly via a modem?
Some Internet services require an active connection coming from the Internet. But the configured filter rules prevent this. Plus, it is not possible to establish incoming
Internet connections with the PCs directly owing to the network address translation process.
185
Frequently Asked Questions Internet
It is possible to redirect incoming connections in the Configurator, menu NET
Configuration: Port Forwarding. You should secure the redirection target (PC or server) with a suitable firewall software.
It is not possible to access the Internet with the OpenPhone 27.
The requirement for this is that the set should be configured as Handset+data.
The telephone number used by the OpenPhone 27 to establish an Internet connection must also be specified in the respective user profile (Configurator, User
Manager: User menu).
With the OpenPhone 27, the Internet can be accessed either directly via the remote data transfer network or indirectly via RAS access on the OpenCom 130/
150. For direct access you can directly dial any provider. Indirect access uses the routing function of the OpenCom 130/150, accompanied by the configured security features, for example.
Directly via remote data transfer network
If the Internet is accessed directly via the remote data transfer network, make sure that
■ the remote data transfer network is properly installed on your PC and that the correct ISP access data is configured,
■ the internal number used by the OpenPhone 27 to establish the data connection is configured for outgoing call distribution (Configurator, PBX Confi-
guration: Call Distribution: Outgoing menu).
Indirectly via RAS access
If the Internet is accessed indirectly via RAS, the system administrator should make sure that:
■ permission has been given for Internet access via RAS (Configurator, Net Con-
figuration: Firewall menu),
■ an internal number is configured for RAS access (Configurator, Net Configu-
ration: Connections: RAS menu),
■ your user group has been granted RAS access rights (Configurator, User
Manager: User Groups menu).
186
Frequently Asked Questions Internet
For information on the installation of software and on configuring Internet access, refer to the “OpenPhone 26/27” user guide.
A SIP connection only passes unidirectional voice. What is the reason?
You did not use the OpenCom 100 as internet router or the STUN server of the SIP provider is unavailable. You need to activate the SIP support at your internet router, such as “SIP-ALG” or “Full Cone NAT” functions. You can also use the
OpenCom 100 for internet access. Correct the STUN setting in the PBX Configu-
ration: SIP Provider menu.
Is it possible to use Q.SIG-IP connections via an Internet access with dynamic
IP address?
Q.SIG-IP connections require a fixed IP assignment for technical and security reasons. Therefore you need an Internet access with a fixed IP address. It is possible to tunnel a Q.SIG-IP connection through a VPN connection. A VPN connection offers the possibility to determine the peer’s IP address with a DynDNS service during connection setup. VPN and DynDNS can be realized with external servers or routers.
187
Technical Specifications
19. Technical Specifications
OpenCom 130
System data
Mains power supply
Rated power
Safety class
Permissible temperatures stationary, weatherproofed
Dimensions (W x H x D)
Weight
230 V ~ 50 Hz
Basic module:25 VA
Add-on module:80 VA
2
+5°C to +40°C
396 x 390 x 100 mm
Basic module and power supply unit:
1,900 g
Add-on module and power supply unit:
1,000 g
S
0
ports
Euro ISDN external (S
0
external) for basic access, DSS1 protocol
Euro ISDN switchable (S
0 external / S
0 internal) for basic access, DSS1 protocol, or for
ISDN terminals, DSS1 protocol
– Supply voltage
– Supply power
– Range
Basic module: 1x
Add-on module: –
Basic module:1x
Add-on module: up to 8 x; possible interface cards:
– 4 x S
0
– 2 x S
0
and 6 x U pn
– 2 x S
0
and 6 x a/b
40 V ± 10%
3 VA for internal
150 m internal
188
Technical Specifications
U pn
ports for system terminals and
RFP 22/24 DECT base stations
Basic module:3x to connect system terminals,
not DECT-enabled
Add-on moduleup to 16 x all DECT-enabled; possible interface cards:
– 4 x U pn
– 8 x U pn
– 2 x S
0
and 6 x U pn
40 V ± 10%
3 VA per U pn
bus
1,000 m
– Supply voltage
– Supply power
– Range a/b port for analogue terminals with pulse or DTMF dialling, flash duration of 60 to 310 ms
– Supply voltage
– Supply power
– Feed current
– Range
V.24 port (COM) for connection of a PC
– Range
Doorstation equipment interface card for connection of doorstation equipment
Contact load of actor
Basic module:4x
Add-on module: up to 24 x; possible interface cards:
– 4 x a/b
– 8 x a/b
– 2 x S
0
and 6 x a/b
40 V ± 10%
1.2 VA
25 mA
1,000 m
Basic module:1x (optional)
3 m
Basic module:1x (optional)
1,5 A / 125 V
189
Technical Specifications
– Voltage range
Sensor
– Voltage range
U
≈
= 5 V... 30 V
Switched by low AC voltage
U
~
= 6 V... 24 V
190
Technical Specifications
OpenCom 131
System data
Mains power supply
Rated power
Safety class
Permissible temperatures stationary, weatherproofed
Dimensions (W x H x D)
Weight (system only)
S
0
ports
Euro ISDN external (S
0
external) for basic access, DSS1 protocol
Euro ISDN switchable (S
0 external / S
0 internal) for basic access, DSS1 protocol, or for
ISDN terminals, DSS1 protocol
– Supply voltage
– Supply power
– Range
U pn
ports for system telephones
– Supply voltage
– Supply power
– Range a/b ports for analogue terminals with pulse or DTMF dialling, flash duration of 60 to 310 ms
230 V ~ 50 Hz
Main module:25 VA
2
+5 °C to +40 °C
396 x 390 x 100 mm
1900 g
Main module: 1x
Main module:1x
40 V ± 10%
2 VA for internal
150 m internal
Main module:3x to connect system terminals,
not DECT-enabled
40 V ± 10%
3 VA per U pn
-Bus
1000 m
Main module:8x
191
Technical Specifications
– Supply voltage
– Supply power
– Feed current
– Range
V.24 port (COM) for connection of a PC
– Range
Doorstation equipment interface card for connection of doorstation equipment
Contact load of actor
– Voltage range
Sensor
– Voltage range
40 V ± 10%
1,2 VA
25 mA
1000 m
1x (optional)
3 m
1x (optional)
1,5 A / 125 V
U
≈
= 5 V ... 30 V
Switched by low AC voltage
U
~
= 6 V ... 24 V
192
Technical Specifications
OpenCom 150
System data
Mains power supply
Rated power
Safety class
Permissible temperatures stationary, weatherproofed
Dimensions
230 V ~ 50 Hz
160 VA
2
+5 °C to +40 °C
Weight (system only)
Wall version:
396 x 390 x 100 mm (W x H x D)
Rack version:
– Width: 19-inch panel with flange for mounting in installation cabinet
–Height: 3U
– Depth: approx. 340 mm
Wall version: 3200 g
Rack version: 7800 g
S
0
ports
Euro ISDN switchable (S
0 external / S
0 internal) for basic access, DSS1 protocol, or for
ISDN terminals, DSS1 protocol
– Supply voltage
– Supply power
– Range
U pn
ports for system terminals and
RFP 22/24 DECT base stations
– Supply voltage
– Supply power
Possible interface cards:
– 4 x S
0
– 2 x S
0
and 6 x U pn
– 2 x S
0
and 6 x a/b
40 V ± 10%
2 VA for internal
150 m internal
Possible interface cards:
– 4 x U pn
– 8 x U pn
– 2 x S
0
and 6 x U pn
40 V ± 10%
3 VA per U pn
-Bus
193
Technical Specifications
– Range a/b ports for analogue terminals with pulse or DTMF dialling, flash duration of 60 to 310 ms
– Supply voltage
– Supply power
– Feed current
– Range
V.24 port (COM) for connection of a PC
– Range
Doorstation equipment interface card for connection of doorstation equipment
Contact load of actor
– Voltage range
Sensor
– Voltage range
1000 m
Possible interface cards:
– 4 x a/b
– 8 x a/b
– 2 x S
0
and 6 x a/b
40 V ± 10%
1,2 VA
25 mA
1000 m
1x (optional)
3 m
1x (optional)
1,5 A / 125 V
U ≈ = 5 V ... 30 V
Switched by low AC voltage
U
~
= 6 V ... 24 V
Note: The online help provides an overview of the limits that should be observed when configuring the
OpenCom 100.
194
Notes on disposal
20. Notes on disposal
In order to avoid any possible effects resulting from the disposal of electrical and electronic equipment containing substances damaging to the environment and human health, the European Parliament and Council directives
■ 2002/96/EC on waste electrical and electronic equipment (WEEE) and
■ 2002/95/EC on the restriction of the use of certain hazardous substances in electrical and electronic equipment (RoHS) have been transferred into national law in all EU member states.
The primary aim of the legislation is the prevention of waste electrical and electronic equipment, and also the recycling, material recovery and any other form of recovery of such waste in order to reduce the quantities of waste to be disposed of and the amount of hazardous substances from electrical and electronic equipment in waste.
The product that you have purchased was developed in line with the current state of the art in an environmentally friendly manner and with a view to recycling. It therefore meets the specifications of the European directives.
The product is labelled with the symbol illustrated above. If you wish to dispose of this product, this symbol obliges you to do so separately from unsorted domestic waste. Suitable facilities have been set up for the return of waste electrical and electronic equipment. Waste equipment can be handed in at these return centres free of charge. To find out where these return centres are located, please consult the information provided by the department of your local authority responsible for waste disposal.
Please note:
Electrical equipment does not belong in household waste.
Deposit it free of charge at a return centre.
195
Index
Index
A
Actor
Adapter
B
C
196
Saving and loading the configuration 82
OpenCom 100 in a LAN with an IPenabled server 92
Configuration guide
Configuring
Connection scheme
D
Index
Doorstation equipment interface card 30
E
F
H
Hardware basic setting switch 84
I
Interface cards (installation) 32
Interface cards (overview) 40, 43
Interfaces
L
M
N
O
197
Index
Q
P
Pin assignment
Plug-in power supply 35, 36, 37
Point-to-point connections 130
Port assignment
Ports
Doorstation equipment 34, 35, 36
LAN (basic module) 28, 34, 36, 37
R
S
Safety
Saving and loading the configuration 82
Sensor
T
Team functions
198
Index
U
V
199
Index
Notes
200
DeTeWe Systems GmbH • Zeughofstraße 1 • D-10997 Berlin • www.Aastra-DeTeWe.de
As of June 2006
Subject to changes
İndir
Herkese açık bağlantı güncellendi
Sohbetinize giden herkese açık bağlantı güncellendi. You may view and manage your chat links after registration here.
Belge herkese açık bağlantısı
Reklam
