Aastra OpenCom 100 Mounting And Commissioning User Manual
  1. Manuals
  2. Brands
  3. Aastra Manuals
  4. Conference System
  5. OpenCom 100
  6. Mounting and commissioning user manual

Aastra OpenCom 100 Mounting And Commissioning User Manual

Hide thumbs Also See for OpenCom 100:
Table of Contents

Advertisement

Quick Links

Download this manual
OpenCom 100
Mounting and Commissioning
User Guide
130
131
150

Advertisement

Table of Contents
loading

Related Manuals for Aastra OpenCom 100

Summary of Contents for Aastra OpenCom 100

  • Page 1 OpenCom 100 Mounting and Commissioning User Guide...
  • Page 2 OpenCom 130, OpenCom 131, OpenCom 150, OpenCom 510 and OpenCom X320 systems. If a reference is made in the text to the OpenCom 100, the description applies to all systems; if the individual characteristics are different, a special note is given.

  • Page 3: Table Of Contents

    Contentsj Features ........... 9 Factory Settings on Delivery .
  • Page 4 Brief Guide to Initial Configuration ....... 77 Configuring the OpenCom 100 ........79 7.2.1...
  • Page 5 Introduction to TCP/IP ......... . .91 OpenCom 100 in a Serverless LAN....... .92 8.3.1...
  • Page 6 Aastra 673xi/675xi Setup ........
  • Page 7 Configuring FMC Telephones ........181 14.2 Configuring “Aastra Mobile Client” Software ....183...
  • Page 8 Team Functions ......... . 187 15.1 Introduction .
  • Page 9 18.5 Setting up Video Telephony........214 18.6 Synchronising the PC Clock .

  • Page 11: Features

    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.
  • Page 12 OpenCom 150 (5 Slots) starting on page 46. The OpenCom 100 complies with the regulations for telecommunications equipment. The DSS1 protocol is implemented. The firmware of the OpenCom 100 is designed for configuring up to 300 users. You can connect the following devices to the OpenCom 100:...
  • Page 13 The OpenCom 100 supports the display of the name on system telephones. However, if you have created an entry in the tele- phone book of the OpenCom 100 under the number of the caller, this will be dis- played instead.
  • Page 14 The TAPI (Telephony Application Programming Interface) and CSTA (Services for Computer Supported Telecommunications Applications) standards are sup- ported for the purpose of integrating CTI applications. OpenCom 100 also features an integrated browser-based CTI application, the OpenCTI 50. The OpenCTI 50 allow users to call up and use telephone functions from their PCs.
  • Page 15 Internet Access It is possible to connect individual PCs to the OpenCom 100 via the internal S ports, or to connect an entire LAN to the OpenCom 100 via the Ethernet port. These PCs can access the Internet via the OpenCom 100. If Internet access is already available from an Internet service provider, this can be configured in the OpenCom 100.
  • Page 16 99. E-Mail The OpenCom 100 has an integrated e-mail function that is able to use the POP3, APOP or IMAP4 protocols to check the Internet service provider for incoming mail. When configuring the OpenCom 100, e-mail account query can be configured for every member of staff.
  • Page 17 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 ports must be DECT-capable.

  • Page 18: Factory Settings On Delivery

    1 port is configured as a multi-terminal connection, and the S 2 port as a system port. ■ Aastra 677x system telephones with the telephone numbers 30 to 32 are con- figured on the three U ports. ■ Analogue terminals with the telephone numbers 10 to 13 are configured on the four a/b ports.

  • Page 19: Opencom 150

    The system PIN, for example for remote-programmable call diversion, is set at “0000”. Authorisations The use of functions by a terminal on the OpenCom 100 is regulated by means of authorisations. Authorisation is configured by means of user groups to which the users with their terminals are then assigned.
  • Page 20 Factory Settings on Delivery Authorisations The following functions are delivered preset for user groups: User group settings Function / Authorisation Standard Adminis- Guests trators Applications Configurator personal Expert View Costs Phone Book ISP application Courtesy Service Phone Book Entries (personal) Edit central Dial in (outgoing) External...
  • Page 21 Factory Settings on Delivery Authorisations User group settings Function / Authorisation Standard Adminis- Guests trators Multiple seizure at the parallel terminal s Switch authorization Dial in (incoming) Pickup from group Pickup selective Take Call removal Calling suppression at the parallel terminal Reaction: connection will be disconnected...
  • Page 22 Factory Settings on Delivery Authorisations User group settings Function / Authorisation Standard Adminis- Guests trators MOH at external connections MOH at internal connections Protection Call protection ringing ringing tone tone Call waiting protection Announcement protection Intercom protection Pickup protection Display phone number off (intern) Display phone number off (extern) Display phone number off/on per connec- tion...
  • Page 23 Factory Settings on Delivery Authorisations User group settings Function / Authorisation Standard Adminis- Guests trators Programming function keys Menu and ABC keys DECT trunc keys Disconnect ISP connection Connection data Send incoming connections Send outcoming connections Number of suppressed digits Incoming basic amount 0,00 0,00...

  • Page 24: Internet Functions

    The multi-company version is not activated. 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.
  • Page 25 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).

  • Page 26: Installation

    Installation Scope of Delivery Installation 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 port ■...

  • Page 27: Safety Precautions

    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.

  • Page 28: Declarations Of Conformity

    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.

  • Page 29: Wall Mounting

    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 sus- pended from the screw at point A, so there must be a space of 3 mm between the screw and the wall.
  • Page 30 Installation Installing an Expansion Set 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.
  • Page 31 Installation Installing an Expansion Set expansion module using the Phillips screws provided in the expansion set (see “1” to “4” in the diagram). 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”).

  • Page 32: Installing Interface Cards

    OpenCom 131 is quipped with one large and two small slots for installing interface cards. Please note: Turn off the OpenCom 100. Unplug the plug-in power sup- ply 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.
  • Page 33 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. ■...

  • Page 34: Slots For Additional Interface Cards

    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 Telephony: Ports: Slots menu page. The Status column in the table displays a green tick beside the name of the interface card.
  • Page 35 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.

  • Page 36: Installing An M100-At4 Card

    41). 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.
  • Page 37 Installation Installing Interface Cards Configuring the slot 1. Log in to the Configurator as a user with administrator rights. Switch to the Configurator’s Expert mode to obtain all required dialogues. 2. Open the Telephony: Ports: Slots menu. Card type a/b Trunk is displayed in the inserted column for the selected Slot if the card is inserted into the slot.
  • Page 38 Installation Installing Interface Cards Assigning a route In order to allow the analogue lines of the M100-AT4 Interface Card to be used for outgoing calls, the bundle needs to be assigned to a route: 1. Open the Telephony: Trunks: Route menu. On the status page, the list of previously configured routes is displayed.

  • Page 39: Available Ports

    4. Click on the Apply button. 5. Repeat steps 2 to 4 until all allocations have been set in the call distribution. Available Ports The OpenCom 100 has the following ports (see also Positions of the Ports starting on page 41): 3.8.1 OpenCom 130 The listed interfaces and ports are located on the basic module of the OpenCom 130.

  • Page 40: Opencom 131

    These cards are necessary to operate the OpenVoice and Open- Attendant programme packages. Only use high speed memory cards which are recommended by Aastra. Other memory cards or “Microdrive” type memory cards may not be able to maintain the required access speed.

  • Page 41: Opencom 150

    These cards are necessary to operate the OpenVoice and Open- Attendant programme packages. Only use high speed memory cards which are recommended by Aastra. Other memory cards or “Microdrive” type memory cards may not be able to maintain the required access speed.
  • Page 42 These cards are necessary to operate the OpenVoice and Open- Attendant programme packages. Only use high speed memory cards which are recommended by Aastra. Other memory cards or “Microdrive” type memory cards may not be able to maintain the required access speed.

  • Page 43: Positions Of The Ports

    Installation Available Ports 3.8.4 Positions of the Ports The following diagrams show the positions of the ports: Default setting Sensor Sensor Actuator RJ45 RJ45 V.24 Position of the ports on the basic module (OpenCom 130) Slot 1 Slot 2 Slot 3 Slot Slot Slot...
  • Page 44 Installation Available Ports DC in Default setting Slot V.24 Slot 1 Slot Doorstation equipment Sensor Sensor 3 Slot 1 1- 4 1- 5 Actor V.24 Position of the ports on the OpenCom 131 Default setting V.24 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5...

  • Page 45: Interface Cards

    Installation Interface Cards 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.
  • Page 46 Installation Interface Cards Slot 1 Slot 2 Slot 3 Ports: 4 x S Slot 1 Slot 2 Slot 3 1/1 U 2/1 U 2/3 U Ports: 4 x U Slot 1 Slot 2 Slot 3 1/1 U 2/1 U 2/3 U 1/5 U 1/7 U 2/5 U...
  • Page 47 Installation Interface Cards Slot 1 Slot 2 Slot 3 1: S 1: S 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 1/5 ab 1/6 ab 2/5 ab 2/6 Ports: 2 x S and 6 x a/b Slot 1 Slot 2...

  • Page 48: Opencom 150 (5 Slots)

    Installation Interface Cards 3.9.3 OpenCom 150 (5 Slots) The following overview shows the available interface cards. Interface card Slots Special features ● ● ● M100-S4: 4 x S are switchable internally/ externally ● ● ● M100-U4d: 4 x are DECT-enabled ●...
  • Page 49 Installation Interface Cards Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Ports: 4 x U Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Ports: 8 x U Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Ports: 2 x S and 6 x U Slot 1...

  • Page 50: Port Assignment, Termination, Cable Lengths

    Installation Port Assignment, Termination, Cable Lengths Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Ports: 4 x a/b Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Ports: 8 x a/b Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 M100-AT4 Interface Card (4 analogue trunk lines)
  • Page 51 Ports on Interface Cards OpenCom The S bus is terminated at one end by the OpenCom 100. IAE = ISDN socket (German: “ISDN Anschluss Einheit”) or an ISDN terminal. TR = terminating resistor, the S termination. The TR must be at the termination of the line.

  • Page 52: Pn Ports

    Each of the U ports enable the connection of a RFP 22 / 24 DECT base station, an Aastra 6771 / 6773 / 6775 (OpenPhone 71 / 73 / 75) or an OpenPhone 61 / 63 / 65 telephone using a twin-wire cable.

  • Page 53: A/B Ports

    Installation Port Assignment, Termination, Cable Lengths The maximum permissible length of the twin-wire cable on a U port is 500 m. This line may only be laid inside buildings. The maximum permissible length of the twin-wire cable on a U 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).

  • Page 54: Actor/Sensor

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

  • Page 55: 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.

  • Page 56: Pcm Port

    Installation Power Failure 3.10.7 PCM Port The PCM port is used cascade two communications systems together (see PBX Cas- cading starting on page 148). 3.11 Power Failure In the event of a power failure, all the contents in the memory (programme and user data) are saved without change.

  • Page 57: Connectible Terminals

    Connectible Terminals 3.12 Connectible Terminals The OpenCom 100 ports already offer a large number of possibilities for con- necting terminals. By installing additional interface cards (in an OpenCom 130 / 150) the number of ports can be increased as required.

  • Page 58: Pn Ports

    A system terminal can be connected to every U port by a twin-wire cable. The Aastra 6771 / 6773 / 6775 (OpenPhone 71 / 73 / 75) and the OpenPhone 61 / 63 / 65 are cord-bound system terminals. The OpenPhones 63 and 65 can be cas-...
  • Page 59 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 System: Components menu.
  • Page 60 2-wire under Type. Deactivate 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.

  • Page 61: Actor/Sensor Ports

    Installation Connectible Terminals 3.12.4 Actor/Sensor Ports For the assignment of the ports, refer to the section Available Ports starting on page 37. The OpenCom 100 also functions together with a Freehand Entry-Phone manufactured by Siedle or Behnke. PVG 402-0 a/b1...

  • Page 62: Com Port

    The connection line for the COM port can be up to three me- tres 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 regis- tration programme OpenCount.

  • Page 63: Installing The Memory Card

    Only use high speed memory cards which are recommended by Aastra. Other memory cards or “Microdrive” type memory cards may not be able to maintain the required access speed.

  • Page 64: To Install A Memory Card

    3. Insert the memory card in the base on the upper edge of the module board. Inserting a Compact Flash card 4. Replace the housing cover. 5. Insert the mains plug. The OpenCom 100 is restarted. The configuration last loaded is reactivated.

  • Page 65: Aastra 677X: Extensions And Accessories

    Key Extensions Up to three key extensions can be connected to system telephones: either three key extensions of the model Aastra M671 or three key extensions of the model Aastra M676. A combination of these key extensions is, however, not possible.
  • Page 66 The number of key extensions connected to a system telephone (up to three) can be set in the Configurator of the OpenCom 100’s Web Console (in the menu Telephony: Ports: Upn or Telephony: Devices: VoIP Phones). Here the keys can also be programmed as call keys or assigned functions or destination call numbers.
  • Page 67 Use discharging underlays or antistatic mats where possible. Please note: Never attach a key extension to a system telephone that is already connected to OpenCom 100. Pull the telephone plug out of the socket before screwing the key extension onto it.
  • Page 68 Aastra 677x: Extensions and Accessories Key Extensions This symbol on the system tele- phone indicates the connector for the key extension. It is on the underside of the telephone. This symbol on the key extension indicates the connector for a further key extension.

  • Page 69: Headset

    Aastra 677x: Extensions and Accessories Headset Headset A headset can be connected to the Aastra 6771 / 6773 / 6775 (OpenPhone 7x) system telephones and to the Aastra 6773ip / 6775ip (OpenPhone 7x IP) IP system telephones. The headset must comply with the DHSG standard (connection via RJ45 jack). The manufacturers Plantronics and GN Netcom make devices suitable for this purpose.

  • Page 70: S 2M Connector Module

    Connector Module Connector Module The S 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 port to network two systems, e.g. in order to use the OpenCom 130 / 150 as a subsidiary system or DECT server.

  • Page 71: Installation

    Connector Module Installation 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 cover of the OpenCom 130 / 150. 3.
  • Page 72 Connector Module Installation LEDs slot (Underside of the module board) Position of the LEDs on the module 5. Wire the S port of the connector module to the NT or the other PBX according to the following drawing. Make sure the RX and TX lines are crossed over (connect the RX lines of the OpenCom 130 / 150 to the TX lines of the other PBX).

  • Page 73: Configuration

    Connector Module Configuration 7. Reconnect the OpenCom 130 / 150 to the power supply. 8. Configure the S module in the Configurator of the OpenCom 130 / 150 (refer to Configuration starting on page 76). Check the level 1 status with ref- erence to the LEDs on the module.

  • Page 74: Mounting The Opencom 150 Rack Infocom System

    Mounting the OpenCom 150 Rack InfoCom System Safety Precautions 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 Safety Precautions The system needs to be mounted in earthed cabinets or cases.

  • Page 75: Technical Data

    Mounting the OpenCom 150 Rack InfoCom System Technical Data 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 non- heating apparatus Connection of all ports via RJ 45 jacks on front panel...

  • Page 76: Pinning Of Rj 45 Jacks

    Mounting the OpenCom 150 Rack InfoCom System Pinning of RJ 45 Jacks Pinning of RJ 45 Jacks , a/b Pin 4-5 Intercom Pin 3-4 (Door 1) Pin 5-6 (Door 2) Sensor Pin 1-2 (S1) Pin 3-4 (S2) Pin 5-6 (S3) Pin 7-8 (S4) Actor Pin 1-2 (A1)

  • Page 77: 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 Aastra installer: Please download and install the latest released software from our Web site/ partnership area.

  • Page 78: Configuration

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

  • Page 79: Brief Guide To Initial Configuration

    For the initial configuration you can connect the PC to the OpenCom 100 via the Ethernet port. The TCP/IP network protocol is used to set up a connection via one of these ports. You can then open the Web console of the OpenCom 100 and call up the Configurator from there.
  • Page 80 Configuration Brief Guide to Initial Configuration Setting the IP address in Windows XP Tip: To find out the IP address of the Web console, enter the code *182 digit procedure on a connected system tele- phone. You can also view the net mask by entering the proce- *183 dure .

  • Page 81: Configuring The Opencom 100

    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.
  • Page 82 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.

  • Page 83: Loading The Online Help

    2. Then select the Log-off command in the upper menu bar. 7.2.5 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: ■...

  • Page 84: Preconfiguration

    7.2.6 Preconfiguration Configuration of the OpenCom 100 can be prepared at your Aastra Customer Service Centre or by an authorised Aastra dealer. For this purpose, a OpenCom 100 installed here is programmed with the customer data (e.g. user data, call distri- bution schemes, cord-bound terminals).
  • Page 85 During remote configuration, the OpenCom 100 is blocked for RAS access by any further users. If no RAS access has been configured in the OpenCom 100 Configurator, you can use a code procedure to release the internal RAS access for remote configuration, and then block it again.
  • Page 86 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 System: Firmware menu in the Configurator).

  • Page 87: Codes For Ip Configuration

    The IP configuration of the OpenCom 100 is performed on the Web console in the Configurator, in the Network: 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.

  • Page 88: Receiving System Messages As E-Mail

    Configuring the OpenCom 100 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.

  • Page 89: Resetting The System Data

    Configuration Configuring the OpenCom 100 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.

  • Page 90: Generating Your Own Moh Files

    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).
  • Page 91 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.

  • Page 92: Configuration Examples

    (if the multi-company variant is acti- vated). 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.

  • Page 93: 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.

  • Page 94: Opencom 100 In A Serverless Lan

    PC 2 The OpenCom 100 in a serverless LAN In a serverless LAN, the OpenCom 100 takes over the IP configuration of the con- nected workstations. All IP settings necessary for the workstations are assigned by the OpenCom 100 via DHCP (dynamic host configuration protocol). In this oper- ating mode, an IP address space reserved for such networks is used: 192.168.99.254...

  • Page 95: Dns Name Resolution

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

  • Page 96: Ras Access

    OpenCom 100 in a LAN with an IP-enabled Server 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.
  • Page 97 Dynamic and static address assignment setting. 3. In the Devices selection, change to the with configured MAC only setting. For SIP system telephones (Aastra 673xi and Aastra 675xi), it is also possible to omit the configuration of the MAC address (see Aastra 673xi/675xi DHCP starting on page 124).

  • Page 98: Dns Name Resolution

    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.

  • Page 99: 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, Network: RAS: ISDN menu, under Address Range.

  • Page 100: Branch Link

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

  • Page 101: Useful Information On Internet Access

    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.

  • Page 102: E-Mail

    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 con- figured for this function, the user specified in the OpenCom 100 user account is notified of the new e-mail on his system terminal.
  • Page 103 Configuration Examples Useful Information on Internet Access 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”).

  • Page 104: Voice Over Ip (Voip)

    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. Furthermore, the standardised SIP pro- tocol can also be used on the intranet.

  • Page 105: Quick Start

    Fundamentals starting on page 107. Quick Start 9.1.1 IP System Telephony VoIP system telephony can be quickly and easily set up using the OpenCom 100. 1. To increase performance, install an M100-IP Media Gateway card (not appli- cable to OpenCom 131).

  • Page 106: External Sip Line

    Voice over IP (VoIP) Quick Start an IP address from the OpenCom 100 IP network which is not being used, such as 192.168.99.253 under IP Address Configured. Click on Apply. 3. Install a memory card (MMC or MMCPlus). Call up the System: Components page.
  • Page 107 Voice over IP (VoIP) Quick Start 4. Call up the Configurator and go to the page Telephony: Trunks: SIP Provider. If your SIP provider is not listed, click on New. Otherwise select the precon- figured SIP provider. Enter the Name and Domain (DNS name of the SIP ID). Enter the SIP server’s IP address under Proxy/Registrar and an IP address under STUN Server and STUN Port where necessary.

  • Page 108: Internal Sip Telephony

    2. Call up the Configurator and go to the page Telephony: Ports: Slots. Click on the corresponding slot. Under Configured, select MGC VoIP. Optional: enter an IP address from the OpenCom 100 IP network which is not being used, such as 192.168.99.253 under IP Address Configured. Click on Apply.

  • Page 109: Fundamentals

    Voice over IP (VoIP) Fundamentals A configuration dialogue of SIP telephony software 7. You can only conduct a certain number of telephone calls simultaneously with internal SIP telephones. The number licenced can be viewed on the System: Licences page. The number of SIP telephones currently licenced can be deter- mined on the System Info: Telephony: SIP phones page.

  • Page 110: Propagation Delay And Bandwidth

    Voice over IP (VoIP) Fundamentals 9.2.1 Propagation Delay and Bandwidth IP-based data networks are generally not able to guarantee a specific minimum bandwidth and defined propagation delay. A synchronised 64 kbit/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.

  • Page 111: Voice Quality

    Voice over IP (VoIP) Fundamentals The following table provides an overview of the required bandwidth for a tele- phone connection with various parameter settings. The values apply to half- duplex ethernet; for full-duplex the values can be halved. Required bandwidth (kbit/s) with respect to Packet Length and Codec Packet G.711 (not G.729A...
  • Page 112 Voice over IP (VoIP) Fundamentals Quality Levels for Voice Transmission with VoIP Level Voice Comprehensibility Comparable to Satisfactory Limited Defective GSM > 4 Unacceptable 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: ■...

  • Page 113: Optimisation

    TOS byte of IP packets, thereby providing the optimal prerequi- sites 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...

  • Page 114: Call Set-Up

    Various IP-based protocols are used for system telephony via the Internet protocol (“IP”) (see also Start Procedure starting on page 129). Multiple TCP connections are made between an IP telephone and OpenCom 100 for the telephone’s start pro- cedure, registration and signalling. All voice data are directly exchanged between IP telephones using the RTP (“Realtime Transport Protocol”) protocol.

  • Page 115: Media Gateway (Mgw)

    8 external SIP connections possible. 9.3.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 auto- matically activated when no Media Gateway card is present.

  • Page 116: Mgw Interface Card

    Voice over IP (VoIP) Media Gateway (MGW) 9.3.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.

  • Page 117: Sip Telephony

    Voice over IP (VoIP) SIP Telephony 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.
  • Page 118 Firewall or NAT configuration of the Internet gateway product used. If you do not use the OpenCom 100 as the Internet gateway, the product should be compatible with SIP telephony. These products provide a...

  • Page 119: Internal Sip Subscribers

    SIP telephones connected via LAN or SIP pro- grammes installed on workstation computers can thus establish connections to all other devices or trunks connected to the OpenCom 100. For operation as a SIP server a MGW Interface Card is required.
  • Page 120 The text portion of the SIP-URI (“Display Name”) is not evaluated at log-on from the OpenCom 100. The series of characters before “@” is the “User Name” or “SIP Username”. The internal call number of the user must always be used here...
  • Page 121 Alongside code number procedures, SIP subscribers can also use a series of func- tional features realized via the SIP protocol. The OpenCom 100 is the ending for all SIP connections as opposed to what is usually the case on the Internet. This enables SIP subscribers to use OpenCom 100 features.

  • Page 122: Aastra 673Xi/675Xi Sip Telephones

    SIP software. 9.4.3 Aastra 673xi/675xi SIP Telephones You can operate the SIP telephones of the Aastra 673xi and Aastra 675xi product families at the OpenCom 100 communications system. The firmware of the com- munications system already includes the matching firmware files for the following...
  • Page 123 Aastra 673xi/675xi (see Aastra 673xi/675xi Setup starting on page 122). 5. Connect the Aastra 673xi/675xi to your network and plug in the power supply. Details about this can be found in the installation manual which is provided...

  • Page 124: Aastra 673Xi/675Xi Setup

    Now the Aastra 673xi/675xi reads in the configuration files from the TFTP server. This includes a generic configuration file (“aastra.cfg”) and a device specific config- uration file for the given MAC address. During this process the OpenCom 100 com- munications system transfers all settings and by this it configures the system telephony features for the Aastra 673xi/675xi.
  • Page 125 Select a function in the Type setting and optionally enter a label in the Labelling setting. Confirm the setting with Apply. 5. To transfer the settings to the Aastra 673xi/675xi, click the Apply button on the Telephony: Devices: System phone page.

  • Page 126: Aastra 673Xi/675Xi Dhcp

    Voice over IP (VoIP) SIP Telephony Function keys for Aastra 6730i / 6731i and Aastra 6753i / 6755i / 6757i Key type Parameter Function do not disturb Calling Switches call protection on or off; LED indica- internally / ex- tor indicates active function...

  • Page 127: Aastra 673Xi/675Xi Hot Desking

    DHCP server. For example, add an exception rule for all MAC addresses starting with 00:08:5D. The TFTP server of the OpenCom 100 communications system will serve up to 4 concurrent data transfers. To avoid overloading the TFTP server (e.g. after a power failure), additional devices may get an IP address from the DHCP server with a delay.

  • Page 128: Voip System Telephones

    Voice over IP (VoIP) VoIP System Telephones After restart, the logged out Aastra 673xi/675xi will show a login page. A user can enter his call number and his user PIN. If a device entry with this call number exists and has the same device type, the login procedure continues. If the device entry is currently active on another device, the associated remote Aastra 673xi/675xi will be logged out automatically and will show a login page on its part.

  • Page 129: Device Properties

    9.5.1 Device Properties The VoIP-enabled versions of the system telephones Aastra 6773ip (OpenPhone 73 IP) and Aastra 6775ip (OpenPhone 75 IP) offer the same features as the corresponding system telephones. Using VoIP system telephones is therefore not much different from using standard system telephones. The fol- lowing differences exist: ■...

  • Page 130: Voip System Telephone Configuration

    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.

  • Page 131: Start Procedure

    DHCP service programme’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 Con- figurator and open the Network: LAN page. Click on the Change button.
  • Page 132 The file name is determined by the telephone type. If a Media Gateway card is installed, you can also specify the TFTP server on the card which has a higher per- formance. Telephone type OpenCom 130/131/150 Media Gateway card Aastra 6773ip opi7x.cnt /ram/ip_tel/opi7x.cnt (OpenPhone 73 IP) Aastra 6775ip opi7x.cnt /ram/ip_tel/opi7x.cnt...
  • Page 133 5. The VoIP system telephone creates a TCP connection to the supplied IP- address/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 Telephony: Devices: VoIP Phones.

  • Page 134: Local Configuration

    9.5.5 Local Configuration In addition to automatic configuration via BOOTP/DHCP, it is possible to manually configure an Aastra 6773ip (OpenPhone 73 IP) or an Aastra 6775ip (OpenPhone 75 IP). This can make sense, for example, when you wish to connect a VoIP system telephone at a distant location via router.
  • Page 135 Voice over IP (VoIP) VoIP System Telephones The “IP Phone Configurator” dialogue opens. Select the desired language setting (“English” or “German”)from the drop-down menu. 2. Enter the network address of the VoIP system telephone. You have two con- nection types to choose from under Connection to IP Phone: –...
  • Page 136 130). Registration IP address and Registration port: This is where you usually enter the IP address of the OpenCom 100 and the port number 8100. Default gateway: Click on the Add parameter command to have this optional entry field displayed.

  • Page 137: Aastra 277Xip (Openphone 7X Ipc)

    This software can be used with the operating systems Windows XP and Vista. Software VoIP system telephone Aastra 2775ip (OpenPhone 75 IPC) with one key ex- tension As well as VoIP system telephony from workstation computers, the Aastra 277xip (OpenPhone 7x IPC) includes the following features: ■...

  • Page 138: Installation

    Voice over IP (VoIP) Aastra 277xip (OpenPhone 7x IPC) You will not need a licence to install Aastra 277xip (OpenPhone 7x 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 Aastra 277xip (OpenPhone 7x IPC)s, are available.
  • Page 139 Web console. The displayed menu texts and parts of the operations software are elements of the Aastra 277xip (OpenPhone 7x IPC) installation, but they can be loaded from the OpenCom 100 via TFTP where necessary.

  • Page 140: Dect Over Ip

    Note: DECT over IP® is a registered trademark of Aastra Tele- com Schweiz AG. 10.1 Properties 10.1.1 DECT Base Stations DECT base stations can be connected to the OpenCom 100 via U accesses or via network (TCP/IP). These DECT base stations are available for the type of access selected: ■...

  • Page 141: Features

    VoIP audio communication between the DECT over IP base station and the OpenCom 100 is made via the RTP/RTCP protocol. RTP voice data are directly con- verted into DECT voice data by the base station. The base stations support the fol-...

  • Page 142: Configuration

    One of the DECT over IP base stations that is installed assumes coordination and configuration of the DECT over IP functions (“DECT over IP Manager”, OMM). Select a base station that has a dependable data link to the OpenCom 100. Note: You can determine a second base station as additional DECT over IP Manager (“Standby Device”).

  • Page 143: Dual Operation

    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 dis- played 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 dif- ferent access technology.

  • Page 144: Synchronisation

    ® DECT over IP Configuration 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 simul- taneously.
  • Page 145 Telephony: Devices: DECT over IP and click on the WLAN Config. button. Log in under the User Name “Administrator” and enter the same password as for the OpenCom 100. DECT over IP/OpenMobility Managers Login Page The WLAN function and the function of the DECT over IP/OpenMobility Manager cannot be used simultaneously on the same DECT over IP base station, so you will always need at least two DECT over IP base stations.
  • Page 146 ® DECT over IP Configuration You can now use the WLAN function of your WLAN-enabled DECT over IP base sta- tions and set up the user terminals as required. Setting up a WLAN Profile The WLAN function of the RFP 42 DECT base station also includes such rarely- required features as networks for large company premises or airports.
  • Page 147 ® DECT over IP Configuration Tip: If you are using only modern WLAN cards with 802.11g, you can further speed up data transfer by configuring the setting 802.11b/g Mode to “802.11g only”. ■ You can prevent the transmission of wireless network identification (SSID) with the Hidden SSID Mode setting.

  • Page 148: Configuring For A Remote Location

    10.2.4 Configuring for a Remote Location If you are using a DECT over IP base station in the same LAN as the OpenCom 100, the IP address configuration and software loading procedure which are run when a DECT over IP base station is started are handled by the OpenCom 100 using the DHCP and TFTP protocols.
  • Page 149 (see MGW Interface Card starting on page 114). Leave the TFTP file name setting on the default setting (“/ram/ip_tel/ip_rfp.cnt”). 6. For a remote location, the OpenCom 100’s LAN will usually be accessed via a (VPN) router. Click on Router addresses: [+]. Enter the router’s IP address (“default gateway”).

  • Page 150: Pbx Cascading

    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 page 153).
  • Page 151 PBX Cascading Functionality of PBX Cascading 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. –...

  • Page 152: Putting A Cascaded Pbx Into Operation

    PBX Cascading Putting a Cascaded PBX into Operation 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.

  • Page 153: Notes

    PBX Cascading Putting a Cascaded PBX into Operation Note: Changes to the configuration while initialising the slave system may trigger error reports referring to the ongo- ing initialisation. You can see that the initialisation has been completed from the display on the system telephone connected to the slave system.

  • Page 154: Licensing Information

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

  • Page 155: Pbx Networking

    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.

  • Page 156: Connections

    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 ports or on the S port ■...

  • Page 157: Master/Slave

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

  • Page 158: 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).

  • Page 159: Connection Via An Active Transmission System

    PBX Networking Types of Point-to-Point Connections PBX 1, S OpenCom 130: PBX 1, S OpenCom 150: PBX 1, S 1 2 3 4 5 6 7 8 Rx+ Rx- Tx+ Tx- Rx+ Rx- Tx+ Tx- 8 7 6 5 4 3 2 1 Rx+ Rx- Tx+ Tx- Rx+ Rx- Tx+ Tx- PBX 2, S...

  • Page 160: 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.

  • Page 161: Configuration

    PBX Networking Configuration Note: Q.SIG-IP cannot be operated using a connection with NAT. For a Q.SIG-IP connection, a branch connection or an- other VPN connection is required. 12.3 Configuration The possible configurations described below can be set up in the Web console using the Telephony: Trunks menu.

  • Page 162: Numbering

    “closed numbering”, allowing the same telephone number to be used for reaching each user within the PBX network. With closed numbering, the OpenCom 100 determines which route to seize from the telephone number dialled. The information needed for routing a call can be configured in a numbering table containing up to 100 entries.

  • Page 163: 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 Telephony: Settings under the heading QSIG linking. You can also set the maximum value for the transit counter there.
  • Page 164 Owing to their hardware properties, not all S ports of the OpenCom 100 can be used for PBX networking without restrictions. Depending on the type of system, some ports can only operate in the L1 master mode or L1 slave mode. The external and S ports can be set according to the following table.

  • Page 165: Telephony

    13.1 E.164 conversion The OpenCom 100 communications system supports two different types of call numbers when dialling external call numbers. Usually you enter the code for a route, e. g. a “0” for the “external line” route. Then you enter an external call number.
  • Page 166 Telephony E.164 conversion 1. Call the OpenCom 100 communications system Configurator. On the intro- ductory page, change the Level option to Expert. 2. This step is optional as the country code is preallocated due to the Country setting under System: Common.

  • Page 167: Example

    Local area code (National Destination Code, NDC) (Berlin) Access call number 6104 (Subscriber Number, SN) (Aastra Berlin) Extension or internal call number 4666 (Direct Dialling, DDI) (Sales Support) Code for the “External trunk” route Various call numbers are now dialled from this terminal:...

  • Page 168: Further Information

    13.2 Call Forwarding The current version of the OpenCom 100 communications system also offers con- figuration of multi-level call forwarding. When you forward a call number that has already been forwarded, this results in a call forwarding chain. Call Forwarding Chain Multiple call forwarding is executed independent of the call forwarding type.

  • Page 169: Attributes

    Telephony Call Forwarding Call Forwarding Name Description Call forwarding immediately (CFU) Immediate and unconditional call for- warding Call forwarding on busy (CFB) Call is forwarded only if user is busy Call forwarding after time (CFNR) Call forwarding is only executed after a definable time interval Call Diversion (CD) Is manually executed upon an incom-...

  • Page 170: Loop Detection

    Telephony Call Forwarding warding user in a chain displayed. The “Via” call number is, however, only dis- played when the call number display is activated for the forwarding user. Note: When call forwarding to the OpenVoice voicebox programme, the “Via” call number is evaluated in order to determine the owner of a voicebox.

  • Page 171: Virtual Call Numbers

    Telephony Call Forwarding 13.2.3 Virtual Call Numbers A virtual call number is not assigned to any terminal. You always also enter an internal or an external destination call number directly when configuring a virtual call number. When the virtual call number is called this destination call number is signalled.

  • Page 172: External Call Forwarding

    Telephony Call Forwarding In addition, you can also configure call forwarding on busy (CFB) for hunt groups. This call forwarding can be used for an internal or external destination call number. In addition, you can enter a back-up destination for time-dependent hunt groups when they cannot be reached.

  • Page 173: Information On The Update

    Telephony PIN Code Telephony 13.2.6 Information on the Update It is possible to convert the configuration of an earlier firmware version to the current version within the context of an update. This happens automatically when you load a saved configuration after an update. Please note the following points: ■...

  • Page 174: Configuration

    You can configure the “PIN Code Telephony” feature separately for each company. Configuration is done with the following steps: 1. Call the OpenCom 100 communications system Configurator. On the intro- ductory page, change the Level option to Expert. 2. Open the User Manager: User groups menu page. Click on the New button.

  • Page 175: Implementation

    Telephony Switch authorisation 13.3.2 Implementation You would like to use the “PIN Code Telephony” feature from any telephone. To do so, the telephone belonging to another user is switched to your personal user account (“identity change”). Carry out the following steps: 1.

  • Page 176: Configuration

    You can configure the “Switch authorisation” feature separately for each company. Configuration is done with the following steps: 1. Call the OpenCom 100 communications system Configurator. On the intro- ductory page change the Level option to Expert. 2. Open the User Manager: User groups menu page. Click on the New button.
  • Page 177 Telephony Switch authorisation If the terminal to be switched is currently in the call state, the authorisation switch only takes place once the call is finished. 2. The next outgoing call on the switched terminal then is made with the changed authorisations.

  • Page 178: Fixed Mobile Convergence

    OpenCom 100 communications system is displayed, which can be used to reach the system telephone as well. It is possible to take an ongoing call from the mobile telephone on the system telephone (and vice versa).
  • Page 179 The mobile telephone user can now dial any internal or external call number and use system features. ■ There is special software available for a series of mobile telephones: “Aastra Mobile Client”. This software makes it convenient to use FMC telephony func- tions.
  • Page 180 Fixed Mobile Convergence External Intern Mobile phone System phone User: Peters User: Peters +49-170-45512345 +49-30-9999-1234 Internal party Communications system User: Miller +49-30-9999-xxxx +49-30-9999-5678 FMC-DDI: 8888 1234 ISDN system connection or SIP DDI trunk Incoming internal call Outgoing internal call: Call by an internal user from a mobile telephone...
  • Page 181 Fixed Mobile Convergence External Internal Mobile phone System telephone User: Peters User: Peters +49-170-45512345 +49-30-9999-1234 Communications system +49-30-9999-xxxx FMC-DDI: 8888 External party +41-1-7766554 +49-30-9999-1234 ISDN system connection or SIP DDI trunk Outgoing external call Outgoing external call: Call by an external user from a mobile telephone...
  • Page 182 The following sections provide information on configuring the “Fixed Mobile Con- vergence” (FMC) feature and on configuring FMC telephones. During configu- ration you can also use the online help of the OpenCom 100 communications system as a source of information.

  • Page 183: Configuring Fmc Telephones

    Fixed Mobile Convergence Configuring FMC Telephones gence – Using mobile telephones on the Aastra 800 / OpenCom 100 communica- tions system”. This manual is available as a PDF file on the OpenCom 100 commu- nications system product CD. 14.1 Configuring FMC Telephones...
  • Page 184 6. To create the new FMC telephone confirm with Apply. 7. If you also wish to use the “Aastra Mobile Client” software on the mobile tele- phone, you can manage this software on the configuration platform available on the internet (see Configuring “Aastra Mobile Client” Software starting on page 183).

  • Page 185: Configuring "Aastra Mobile Client" Software

    (FMC telephone) when you install the “Aastra Mobile Client” software on the device. Comparable to a system terminal, this makes many fea- tures available on the mobile telephone via a separate menu. The “Aastra Mobile Client” software runs under Symbian, a widespread operating system for mobile telephones.
  • Page 186 Fixed Mobile Convergence Configuring “Aastra Mobile Client” Software Setting Explanation Auto login Activate this when the CLIP Authenti- cation option is being used. Deactivate when the DTMF login proce- dure (password procedure) is to be used. User call number Internal call number of the FMC tele-...
  • Page 187 Both the configuration and licence SMS are automatically deleted after commissioning of the client. 6. You may configure a quick launch option for starting the “Aastra Mobile Client” software. Depending on the type of mobile telephone, you can configure a special key, a mode entry or a desktop link.
  • Page 188 Configuring “Aastra Mobile Client” Software Operating FMC functions via the software is described in the “Fixed Mobile Con- vergence – Using mobile telephones on the Aastra 800 / OpenCom 100 communi- cations system” user guide. Note: When you have configured the “Aastra Mobile Client”...

  • Page 189: Team Functions

    Aastra 677x (OpenPhone 7x) and their softphone variants because only these have the required features. 15.1.1 Explanation of Keys The team functions are programmed on the call keys of the Aastra 677x (OpenPhone 7x) telephones. Depending on the terminal, different numbers of call keys are available:...
  • Page 190 Number of available call keys Telephone Number of keys Aastra 6775 (OpenPhone 75) and 20 additional keys with a display Aastra 2775ip (OpenPhone 75 IPC) with Up to three of these key extensions can an additional key extension be used with an Aastra M676 Aastra 6775 (OpenPhone 75) and Aastra 2775ip (OpenPhone 75 IPC).

  • Page 191: Team Configuration

    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 “Aastra 6771 / 6773 / 6775 (OpenPhone 7x)” user guide.

  • Page 192: Executive/Secretary Team

    15.2.1 Executive/Secretary Team In this example, the executive/secretary team comprises two members: the exec- utive and the secretary. The secretary has one Aastra 6773 (OpenPhone 73) system telephone, and the executive has two, one of which is used as a parallel telephone in a sofa suite.

  • Page 193: 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 Aastra 6773 (OpenPhone 73) system telephone with all call keys programmed as trunk and team keys.
  • Page 194 Team Functions Examples of Use 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.

  • Page 195: Unified Team

    The unified team described here is an example of a team configuration within a department in which calls are to be managed quickly (e.g. support department). Each team member has one Aastra 6773 (OpenPhone 73) system telephone with all call keys programmed as trunk keys.

  • Page 196: Toggle Team

    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 “Aastra 6771 / 6773 / 6775 (OpenPhone 7x)” user guide.
  • Page 197 Team Functions Examples of Use Miller 14:22 Mi.14.Feb.07 TrK 10: Support 1 TrK 11: Support 2 TrK 12: Support 3 TrK 13: Support 4 TrK 14: Support 5 TrK 15: Hotline 1 TrK 16: Hotline 2 TK 20: Support 6 TK 25: Hotline 3 Johnson 14:22...

  • Page 198: Call Queue

    If more than one telephone number with a queue is configured on the tele- phone, the total number of entries are displayed. Calls in a queue are handled by the OpenCom 100 in the following order of pri- ority: instant connection, door calls, automatic recalls, VIP calls, then other internal and external calls.

  • Page 199: Activation Of Queues

    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 “call forwarding,” “pickup” and “hunt group”...

  • Page 200: Pickup

    16.2.1 Enquiry Station for an Operator with Two System Telephones The operator switches all incoming calls and can either work on the Aastra 6775 (OpenPhone 75 / OpenPhone 65 or the mobile terminal, the Aastra 610d / 620d / 630d. Configuration ■...
  • Page 201 A queue is used so that callers do not get a busy signal. The display on the Aastra 6775 (OpenPhone 75 / OpenPhone 65 indicates how many calls there are in the queue.

  • Page 202: Group Of Three Enquiry Stations

    Call Queue Examples of Use Aastra 610d / 620d / 630d or enter its queue, allowing the Aastra 610d / 620d / 630d to be used as a mobile enquiry station. On returning to the workstation, the operator deactivates call forwarding by pressing a feature key.
  • Page 203 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 (Aastra 6775 (OpenPhone 75 / OpenPhone 65) indi- cates how full the queue is.

  • Page 204: Multi-Company Variant

    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.

  • Page 205: Configuring The Multi-Company Variant

    (see Allocating Routing Codes starting on page 205). 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 206).

  • Page 206: Configuring And Managing Companies

    17.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 bundle configuration, apply to this predefined default company if not other company has been selected.

  • Page 207: Assigning A Bundle/Sip Trunk

    (the users) via the lines of a certain bundle of the OpenCom 100, each of the available bundles 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 sub- scriber cannot be reached (“Connection to Operator”), for example.

  • Page 208: Configuring The Company Exchange

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

  • Page 209: Making Calls Between Companies

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

  • Page 210: Configuring The Pc Software

    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 as the administrator.
  • Page 211 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 programme.

  • Page 212: 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, pick- up, call protection and call forwarding can be controlled using appropriate TAPI- compatible software.
  • Page 213 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.

  • Page 214: Setting Up Net Capi

    With a CAPI driver (Common Application Programming Interface) Windows pro- grammes 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 workstation computers in which no ISDN card is integrated.

  • Page 215: Browser For Opencti And Openhotel

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

  • Page 216: Setting Up Video Telephony

    Configuring the PC Software Setting up Video Telephony 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. Installing the Browser 1. Call up the start mask from the product CD (see Configuring the PC Software on page 208).

  • Page 217: Synchronising The Pc Clock

    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, System: Common menu. Click on Change.

  • Page 218: Address Queries Using Ldap

    4. Check the function. In the Edit menu, call up the Find: People command. The Find: People dialogue box will then open. 5. In the Look in list, select the entry with the OpenCom 100 address. Enter a user in the Name input field, Administrator for example. Then click on Find now.

  • Page 219: Frequently Asked Questions

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

  • Page 220: General/Hardware

    If not, contact your service centre or an authorised dealer. The AC adapter plug of the OpenCom 100 may be defective. Question: After restarting the OpenCom 100, nothing is indicated on the dis- plays of any connected terminals. It takes a short while for the OpenCom 100 to start up.

  • Page 221: Telephony

    Telephony After the restart, check whether the activity LED flashes at a rate of 10s / 1s. This flash cycle indicates that the OpenCom 100 has started up correctly and is ready for operation. If the OpenCom 100 has not restarted properly, reset the OpenCom 100 to its original factory setting (refer to the chapter entitled Resetting the System Data starting on page 87).
  • Page 222 Question: One of the features (e.g. call diversion) on one of the telephones cannot be used even though the feature has been configured in the Configu- rator 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).

  • Page 223: Pbx Networking

    Call Distribution menu). A specific MSN can be seized for individual calls by means of a code number pro- cedure. For further information, refer to the “OpenCom 100 / Aastra 800, Oper- ation on Standard Terminals” user guide. Question: What are some of the causes for problems when sending and/or...

  • Page 224: Dect

    Frequently Asked Questions DECT 19.4 DECT Note: In the following explanations it is assumed that a U interface card has been installed (in an OpenCom 130 or an OpenCom 150). Question: The LED of the RFP 22 / 24 base station is flashing, but none of the DECT devices is functioning.

  • Page 225: Lan

    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.

  • Page 226: Internet

    Question: A SIP connection only passes unidirectional voice. What is the rea- son? 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”...
  • Page 227 Frequently Asked Questions Internet Question: 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 pos- sible to tunnel a Q.SIG-IP connection through a VPN connection.

  • Page 228: Technical Specifications

    Technical Specifications 20. Technical Specifications OpenCom 130 System data Mains power supply 230 V ~ 50 Hz Rated power Basic module:25 VA Add-on module:80 VA Safety class Permissible temperatures, stationary, +5 °C to +40 °C weatherproofed Dimensions (W x H x D) 396 x 390 x 100 mm Weight Basic module and power supply unit:...
  • Page 229 Technical Specifications OpenCom 130 (Cont.) ports for system terminals and RFP 22 / 24 Basic module: 3 x to connect system DECT base stations terminals, not DECT-enabled Add-on module: up to 16 x, all DECT-enabled; possible interface cards: – 4 x U –...
  • Page 230 Technical Specifications OpenCom 130 (Cont.) Doorstation equipment interface card for connection of doorstation Basic module: 1 x (optional) equipment Contact load of actor 1.5 A / 125 V – Voltage range = 5 V… 30 V ≈ Sensor Switched by low AC voltage –...
  • Page 231 Technical Specifications OpenCom 131 System data Mains power supply 230 V ~ 50 Hz Rated power Main module: 25 VA Safety class Permissible temperatures, stationary, +5 °C to +40 °C weatherproofed Dimensions (W x H x D) 396 x 390 x 100 mm Weight (system only) 1.9 kg ports...
  • Page 232 Technical Specifications OpenCom 131 (Cont.) a/b ports for analogue terminals with pulse or Main module: 8 x DTMF dialling, flash duration of 60 to 310 ms – Supply voltage 40 V ± 10% – Supply power 1.2 VA – Feed current 25 mA –...
  • Page 233 Technical Specifications OpenCom 150 System data Mains power supply 230 V ~ 50 Hz Rated power 160 VA Safety class Permissible temperatures, stationary, +5 °C to +40 °C weatherproofed Dimensions Wall version: 396 x 390 x 100 mm (W x H x D) Rack version: –...
  • Page 234 – Voltage range = 5 V…30 V ≈ Sensor Switched by low AC voltage – Voltage range = 6 V…24 V Note: The online help provides an overview of the limits that should be observed when configuring the OpenCom 100.

  • Page 235: Notes On Disposal

    Notes on Disposal 21. Notes on Disposal In order to avoid any possible effects resulting from the disposal of electrical and electronic equipment containing substances damaging to the environment and human health, the European Parliament and Council directives ■ 2002/96/EC on waste electrical and electronic equipment (WEEE) and ■...

  • Page 236: Index

    Index Index Codec 109 CompactFlash 38, 39, 40 Conference 124 Aastra 277xip (OpenPhone 7x IPC) 135 Configuration 76 Aastra 677x (OpenPhone 7x) 63 Initial configuration 76 Actor Loading software updates 86 See Intercom system 58 Preconfiguration 82 Actor/sensor port 52...
  • Page 237 Index Diagnosis Call forwarding 171 Direct call key 188 Guest telephone 173 DNS 93, 96 Doorstation equipment add-on card 37, 39 Doorstation equipment interface Hardware 218 card 31 Hardware basic setting switch 87 DSL 53 Headset 67 DSL port 53 Hunt Groups DSS1 154 Call Forwarding 169...
  • Page 238 Index Local area code 163 Phone book 123 Log out 124 Phone lock 124 Pick-up 124 Pin assignment ISDN socket 49 PIN Code Telephony 171 Master system 149 Plug-in power supply 38, 39, 40 Media Gateway 113 Point-to-point connections 156 Memory card 38, 39, 40 Port assignment Messenger 123...
  • Page 239 Index Q.SIG 154 Take 124 Q.SIG-IP 103 TAPI 12, 163, 210 Team functions 187 Explanation of keys 187 Introduction 187 Team key 188 Radio fixed part (RFP, see Base Telephony 219 station) 138 Terminating resistor 49 Redial List 172 TFTP server 122 Remote configuration 82 Three-member team 191 Resetting system data 87...
  • Page 240 Index XML 124...
  • Page 241 Index Notes...
  • Page 242 Index Notes...
  • Page 244 As of 19.07.2009 Subject to changes...

This manual is also suitable for:

Opencom 130Opencom 131Opencom 150Opencom 510Opencom x320

Table of Contents