Page 1 OpenCom 100 Mounting and Commissioning User Guide Communications systems OpenCom 130 OpenCom 131 OpenCom 150...
Page 2 Welcome to Aastra Thank you for choosing this Aastra product. Our product meets the strictest requirements with regard to quality and design. The following operating instructions will assist you in using your OpenCom 100 and answer most of the questions that may arise.
Page 3: Table Of Contents
Contents Features ............... . 9 Factory Settings on Delivery .
Page 4 To Install a Memory Card …..........65 Aastra 677x: Extensions and Accessories .
Page 5 Mounting the OpenCom 150 Rack InfoCom System ....75 Safety Precautions ............75 Technical Data.
Page 6 Aastra 277xip (OpenPhone 7x IPC)........
Page 7 ® DECT over IP ..............141 Properties .
Page 8 Configuring FMC Telephones ......... . .189 Configuring “Aastra Mobile Client” Software ......191 Team Functions .
Page 9 Call Queue ..............204 Introduction .
Page 10 SNMP Interface............228 Installing SNMP Agent .
Page 11: Features
Features Features The OpenCom 100 is a communications system for integrated voice and data commu- nication. 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, IP system telephones, ISDN terminals and analogue terminals.
Page 12 • analogue terminals • Euro-ISDN terminals • System telephones Aastra 6771 (OpenPhone 71), Aastra 6773 (OpenPhone 73), Aastra 6775 (OpenPhone 75) • System telephones OpenPhone 61, OpenPhone 63, OpenPhone 65 • Base stations and DECT handsets (on the DECT-enabled U...
Page 13 An S port can be used by Euro-ISDN terminals working in accordance with DSS1. A port is suitable for the Aastra 677x (OpenPhone) range of system telephones. RFP 22 / 24 base stations can also be connected to the DECT-enabled U ports on interface cards for an OpenCom 130 and an OpenCom 150.
Page 14 The installed memory card enables you to operate a digital voice memory and voice information system. A 1 GB memory card offers about 60 minutes of recording time. For more information, please refer to the user guides “OpenVoice / Aastra Voice 800” and “OpenAttendant / Aastra Attendant 800”.
Page 15 OpenCom 100 supports the connection of VoIP terminals, enabling the company’s existing internal network infrastructure (LAN with 100 MBit/s) to be used for telephony as well. Corded system terminals of the Aastra 6773ip (OpenPhone 73 IP) and Aastra 6775ip (OpenPhone 75 IP) as well as the VoIP system telephones OpenPhone 63 IP and OpenPhone 65 IP types are available for this purpose.
Page 16 Features • SIP (internal): You can operate SIP system phones Aastra 673xi/Aastra 675xi and standard SIP telephones. • SIP (external): You can use external SIP connections as “SIP trunk lines”. Setting up and using external SIP connections is completely transparent for telephone users, providing them with easy access to low-cost Internet telephony and a fallback to normal ISDN connections in case of error or busy lines.
Page 17 Features 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 18 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. You can query the internal phone book of the OpenCom 100 communications system via LDAP.
Page 19: 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 20: Opencom 150
Factory Settings on Delivery OpenCom 150 With the OpenCom 150 all ports (S and a/b ports) are realised by installing a spe- cific 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 50.
Page 21 Factory Settings on Delivery User group settings Function / Authorisation Standard Adminis- Guests trators Applications Configurator personal Expert View Costs Phone Book OpenCTI 50 Busy lamps OpenCount 100 OpenHotel 100 ISP application Courtesy Service Phone Book Use LDAP Use central Edit central Use own company Edit own company...
Page 22 Factory Settings on Delivery User group settings Function / Authorisation Standard Adminis- Guests trators Deactivate LCR LCR at call forwarding to extern. VIP call PIN dial Announcement Announcement accept Intercom Dialout for other phone Instant connection Callback on busy Multiple seizure at the parallel terminal s Switch authorization Display phone number off (intern)
Page 23 Factory Settings on Delivery User group settings Function / Authorisation Standard Adminis- Guests trators Reaction: connection will be disconnected display phone number off (intern) Call queue Call forwarding Call forwarding Call forwarding to extern Call forwarding of MSN groups Call forwarding door call Indicate call forwarding after time parallel Call forwarding for other user...
Page 24 Factory Settings on Delivery User group settings Function / Authorisation Standard Adminis- Guests trators Announcement protection Intercom protection Pickup protection Phone lock Intercept Lists Black lists empty empty empty White lists empty empty empty Special lists Call filter empty empty empty Manage intern call list Manage extern call list...
Page 25 Factory Settings on Delivery User group settings Function / Authorisation Standard Adminis- Guests trators Recording incoming connections Recording outgoing connection Number of suppressed digits Incoming basic amount 0,00 0,00 0,00 Outgoing basic amount 0,00 0,00 0,00 Cost factor 100% 100% 100% Create costs Network...
Page 26: Internet Functions
Factory Settings on Delivery *) These settings are shown only in the Expert view. The following important settings are active without further configuration: • External authorisation: International numbers can be dialled from all configured terminals. External lines must be seized by entering a preset code. •...
Page 27 Factory Settings on Delivery The following IP addresses are preset for the network configuration: • Host Name: host • Domain Name: domain • IP address: 192.168.99.254 • Network mask: 255.255.255.0 The following addresses are assigned to the client computers by DHCP or PPP: •...
Page 28: Update Notes
The release 10 is published at the same time for all members of the OpenCom 100 / Aastra 800 product family. If you are operating multiple communications systems, for example, on TC system networking, updating all communications systems at the same time is a good idea to ensure optimal compatibility.
Page 29: Technical Notes
• The firmware extensions contains software for the following terminal types: Type Model IP system phones Aastra 677xip (OP 7x IP) OpenPhone 6x IP SIP system phones Aastra 673xi Aastra 675xi DECT terminals...
Page 30: Updating
Update Notes Updating Updating is done in the following steps: Open the System: Firmware page in the Configurator. Click on the Save button to create a backup copy of the existing configuration. Then click on the Next button. Click on the Browse button. Select the firmware file. Click on the Load button. This process loads the firmware file to the communications system.
Page 31: Installation
Installation 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 32: Safety Precautions
Installation 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 spe- cially trained personnel. Always remove the power plug and the plug-in power supply from the mains socket before opening the housing cover and/or connecting devices to the OpenCom 100 ports.
Page 33: 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 Aastra Web site at http://www.aastra.de or http://www.aastra.com. Mounting Location The ambient temperature for operating the OpenCom 100 must be between +5 and +40°C.
Page 34: Wall Mounting
Installation Wall Mounting The OpenCom 100 is mounted on the wall with three screws as shown in this diagram: 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 35 Installation Open the housing cover of the OpenCom 130. In this case, carefully follow the Safety Precautions starting on page 30. The existing basic module is mounted in the left half of the housing. No compo- nents may be mounted in the right half of the housing. Place the expansion module in the intended mounting location in the right half of the housing.
Page 36 Installation Installing the power supply for the expansion module 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 ter- minals (“A”, “2”).
Page 37: Installing Interface Cards
Installation 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.
Page 38 Installation 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 dia- grams.
Page 39: Slots For Additional Interface Cards
Installation CAUTION! Static charges can damage electronic components. Pay attention to the regulations regarding the handling of electrostatically sensitive components. 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. Connect the required port cable to the corresponding pressure terminals or RJ45 jacks (see also Positions of the Ports starting on page 45).
Page 40 Installation • 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 47. 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: Turn off the OpenCom 100.
Page 41: Installing An M100-At4 Card
Installation 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. 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 45).
Page 42 Installation Configuring the slot Log in to the Configurator as a user with administrator rights. Switch to the Configurator’s Expert mode to obtain all required dialogues. 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 43 Installation Open the Telephony: Trunks: Route menu. On the status page, the list of previously configured routes is displayed. Click on the New button. Alternatively, click one of the route entries to assign the bundle to an existing route. Select the bundle you have configured from the Choice list and enter a route name in the Name field (only if you are configuring a new route).
Page 44: Available Ports
Installation Available Ports The OpenCom 100 has the following ports (see also Positions of the Ports starting on page 45): 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 addi- tional interface cards (see Installing an Expansion Set starting on page 32 and Installing Interface Cards starting on page 35).
Page 45: Opencom 131
Installation • 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. OpenCom 131 • One S port to connect to an external S bus (usually the NTBA), designed as an RJ45 jack (S...
Page 46: Opencom 150
Installation 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 35). •...
Page 47: Positions Of The Ports
Installation Positions of the Ports The following diagrams show the positions of the 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 Sensor Sensor...
Page 48 Installation Slot 1 Slot 2 Slot 3 Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot Slot LAN 1 LAN 2 LAN 0 Position of the ports on the expansion module (OpenCom 130) Default setting V.24 Slot 1 Slot 2...
Page 49: Interface Cards
Installation Interface Cards 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. OpenCom 130 (3 Slots) The following overview shows the available interface cards.
Page 50 Installation 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 2/7 U Ports: 8 x U Slot 1 Slot 2 Slot 3...
Page 51 Installation 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...
Page 52: Opencom 150 (5 Slots)
Installation 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: are DECT-enabled 4 x U M100-U8d: are DECT-enabled 8 x U M100-S2U6d: are DECT-enabled 2 x S are switchable internally/ 6 x U...
Page 53 Installation 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 Slot 2...
Page 54 Installation 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 55: Port Assignment, Termination, Cable Lengths
Installation Port Assignment, Termination, Cable Lengths Ports Whether you use the switchable S ports for internal or external communication depends on your communications requirements and the existing basic accesses. Note that the S bus requires a terminating resistor of 100 ohms at each end. In the case of the OpenCom 100, the S buses are terminated by software.
Page 56: U Pn Ports
RFP 22 / 24 DECT base station, an Aastra 6771 / 6773 / 6775 (OpenPhone 71 / 73 / 75) or an OpenPhone 61 / 63 / 65 tele- phone using a twin-wire cable.
Page 57: A/B Ports
Note Only the system telephones Aastra 6771 / 6773 / 6775 (OpenPhone 71 / 73 / 75) and OpenPhone 61 / 63 / 65 can be operated on the U ports of an OpenCom 131. Op- erating a DECT base station is not possible on these U ports.
Page 58: Actor/Sensor
Installation 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. Actor/Sensor In order to operate an entrance intercom and door opener, you need four twin-wire cables: •...
Page 59: Dsl Port
Installation 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). DSL Port External DSL modems can be connected via the LAN port.
Page 60: Power Failure
Installation Power Failure In the event of a power failure, all the contents in the memory (programme 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.
Page 61: Internal/External S
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 cascaded on...
Page 62: A/B Ports
Installation a/b Ports The a/b ports a/b1 to a/b4 can be used for connecting analogue terminals. These can be for voice or data communication, and use DTMF or pulse dialling, e.g. • analogue telephones • class 3 fax machines • analogue modems (external or internal) •...
Page 63 Installation 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 con- figured five-digit internal numbers. We recommend the following Speech Design products: Memo 200 / 300 / 400 or Memo 200-A / 300-A / 400-A.
Page 64: Actor/Sensor Ports
Installation Actor/Sensor Ports For the assignment of the ports, refer to the section Available Ports starting on page 42. The OpenCom 100 also functions together with a Freehand Entry-Phone manufactured by Siedle or Behnke. PVG 402-0 a/b1 Amplifier Relay Actor2 Siedle Actor1 Door opener...
Page 65: Com Port
Installation 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.
Page 66: Installing The Memory Card
“Microdrive” type memory cards may not be able to maintain the required access speed. Note If you use a memory card other than one recommended by Aastra, Aastra will not ac- cept any responsibility for the correct functioning. For further information, please contact your local dealer or the Aastra sales department.
Page 67: To Install A Memory Card
Installation To Install a Memory Card … Unplug the OpenCom 100. Open the OpenCom 100 housing cover. CAUTION! Make sure you protect yourself against electrostatic discharge. Static electricity can damage the memory card. To avoid such damage, the static elec- tricity must be earthed from your body.
Page 68: Aastra 677X: Extensions And Accessories
The power supply unit 4516000 (in Britain operate only the AC adapter with the part no. 4516001) is required in the following cases: • when connecting a key extension to an Aastra 6773 / 6775 (OpenPhone 7x) system telephone (see also the chapter Key Extensions starting on page 66) •...
Page 69 Aastra 677x: Extensions and Accessories Key extension … … with the features connectable to a system telephone Aastra M671 – 36 keys with LED indicator – Aastra 6773 (OpenPhone 73) – Labelling on label strips – Aastra 6773ip (OpenPhone 73 IP) –...
Page 70 Aastra 677x: Extensions and Accessories Configuration Needs Power Supply Unit system telephone system telephone with 1-3 key extensions IP system telephone IP system telephone with 1-3 key extensions IP system telephone with PoE (Power over Ethernet) IP system telephone with 1-3 key extensions and PoE A system telephone requires a power supply unit if a key extension is installed.
Page 71 Aastra 677x: Extensions and Accessories This symbol on the system telephone 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 72: Headset
Aastra 677x: Extensions and Accessories 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 tele- phones. 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 73: 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 sub- sidiary system or DECT server.
Page 74: Installation
Connector Module V.24 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Actuator 1+2 3+ 4 1+2 Sensor 3+4 Door Location of the S port on the OpenCom 150 Installation Please note: The module should only be installed by trained personnel. DANGER! The device contains hazardous voltages.
Page 75 Connector Module Insert the S module into the slots, making sure you insert the LED side of the module into the upper slot (B). LEDs slot (Underside of the module board) Position of the LEDs on the module Wire the S port of the connector module to the NT or the other PBX according to the following drawing.
Page 76: Configuration
Connector Module 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). If necessary, check to make sure that the NT is fed by its own power supply. Reconnect the OpenCom 130 / 150 to the power supply.
Page 77: Mounting The Opencom 150 Rack Infocom System
Mounting the OpenCom 150 Rack InfoCom System 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 78: Technical Data
Mounting the OpenCom 150 Rack InfoCom System Technical Data (differences to the wall-mounted OpenCom 150 only) 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 79: Pinning Of Rj 45 Jacks
Mounting the OpenCom 150 Rack InfoCom System 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) Pin 3-4 (A2) Pin 5-6 (A3) Pin 7-8 (A4)
Page 80: 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 81: Configuration
Configuration Configuration Configuration and programming of the OpenCom 100 is performed by the Configu- rator, a special software application integrated into the system. The Configurator is operated via the Web console, which can be run on any PC connected to the OpenCom 100.
Page 82: 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.de or http:// www.aastra.com. For the initial configuration you can connect the PC to the OpenCom 100 via the Eth- ernet port.
Page 83 Configuration The Web console’s log-on page will be displayed. Enter the user name “Administrator” without a password for the initial configuration. Note To support your next configuration steps, you should activate the Assistant mode on the entry page of the Configurator. Please also pay attention to the online help. Setting the IP address in Windows XP Tip: To find out the IP address of the Web console, enter the code...
Page 84: Configuring The Opencom 100
Configuration 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. Configuring the OpenCom 100 Preparing the Configuration Before starting with the configuration, make sure you have the following documents at hand:...
Page 85 Configuration OpenCom 100 (this screenshot: OpenCom 150): log-on dialogue box To commence configuration, you must first log on. For the initial configuration, enter your: user name: “Administrator” password: for the initial configuration, leave this box blank. Confirm this by clicking on OK. This puts all connected terminals into the “Guest” user group with restricted user rights.
Page 86: Loading The Online Help
Configuration Then the EULA (End User License Agreement) is displayed. Confirm the license agreement by clicking on Accept. Note If you do not confirm the EULA, the dialogue for loading the firmware page is opened. This is where you can download an older licensed firmware version once again.
Page 87: Finishing The Configuration
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 distribution schemes, cord-bound terminals).
Page 88: Offline Configurator
Configuration 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;...
Page 89 Configuration The manual activation of the remote configuration activates the DTMF evaluation for the next voice call. You can add additional phone numbers for remote configuration on the configurator’s Telephony: Extended: Remote service menu page. Activate the IP option for the desired phone numbers. Note You also need to activate the desired type of connection directly on the Telephony: Extended: Remote service.
Page 90: Codes For Ip Configuration
Configuration 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 91: Receiving System Messages As E-Mail
Configuration Set NET Mask H *183 Z (system PIN) (www) (xxx) (yyy) (zzz) Example H*182 Enter: 0000*192*168*99*254# If required, initiate a system restart with the following procedure: Trigger Restart H * 1 8 5 Z (system PIN) Use the PIN you entered in the dialogue box for initial access. The factory setting is “0000”.
Page 92: Resetting The System Data
Configuration Note If you are operating an PBX cascade, new system software is automatically trans- ferred to the slave system from the master system. For further information, refer to the online help documentation under the item System: Firmware. Resetting the System Data You can restore the factory settings of the OpenCom 100 in the Configurator.
Page 93: Generating Your Own Moh Files
Configuration CAUTION! Static charges can damage electronic devices. Observe the regulations regarding electrostatically sensitive components. 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 47. Press and hold the switch.
Page 94 Configuration 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 95: Configuration Examples
Configuration Examples Configuration Examples OpenCom 100 in Computer Networks One of the outstanding features of the OpenCom 100 is the integration of telephony and computer networks. Connect the OpenCom 100 via a computer network (LAN) with suitably configured workstations, and you can use its network features from these workstations.
Page 96: Introduction To Tcp/Ip
Configuration Examples Server configuration in the LAN OpenCom 100 Functions IP server present Special case when integrating the OpenCom 100 in a LAN; settings in the No DHCP server present Network: LAN menu must be coordinated with the responsible system administrator Introduction to TCP/IP In a single LAN it is possible to use various protocols for the transmission of data.
Page 97: Opencom 100 In A Serverless Lan
Configuration Examples 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.
Page 98: Dns Name Resolution
Configuration Examples 192.168.99.254 OpenCom 100 IP address 255.255.255.0 Network mask (class C network) 192.168.99.254 DNS server IP address 192.168.99.254 Default gateway IP address Install the IP network protocol and a Web browser for every workstation computer which is to have access to the OpenCom 100 network features. DNS Name Resolution In a serverless LAN, the internal DNS name resolution is performed by the OpenCom 100.
Page 99: Ras Access
Configuration Examples ternet 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). RAS Access You can establish a connection to the OpenCom 100 from an external PC via an ISDN card.
Page 100 Dynamic and static address assignment setting. 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 129).
Page 101: Dns Name Resolution
Configuration Examples DNS Name Resolution In a LAN with an IP-enabled server, the latter is also responsible for DNS name reso- lution. 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.
Page 102: Ras Access
Configuration Examples request without the DNS forwarder. For further explanation, refer to the DNS server documentation. 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 adminis- trator 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 103: Branch Link
Configuration Examples 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 104: Useful Information On Internet Access
Configuration Examples Useful Information on Internet Access Costs The OpenCom 100 uses a router function to access the Internet, which means that it automatically establishes an Internet connection when required and terminates the connection after a certain period of time if no data are being transmitted. Unfortunately, programmes 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 programmes are not...
Page 105: E-Mail
OpenCom 100 user account is notified of the new e-mail on his system terminal. Aastra 677x (OpenPhone 7x) and Aastra 610d / 620d / 630d system terminals can also display information such as the sender or the subject of the e-mail.
Page 106 Configuration Examples 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 Network: Port Access menu. For further information, refer to the online help of this menu.
Page 107: Voice Over Ip (Voip)
Voice over IP (VoIP) 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.
Page 108: Quick Start
Voice over IP (VoIP) • Use of PC-supported system telephones (so-called “Softphones”) without extra hardware costs • Operation of SIP-capable telephony software (see also SIP Telephony starting on page 120) • TC system networking using Q.SIG-IP via VPN connections (see also PBX Net- working starting on page 157) •...
Page 109: External Sip Line
Voice over IP (VoIP) Go to the page Telephony: Devices: VoIP Telephone and click on New. Enter the MAC Address printed on the underside of the IP system telephone. Select the Type and enter an internal Number. Option: enter an IP address from the OpenCom 100 IP network which is not being used.
Page 110 Voice over IP (VoIP) On the Telephony: Trunks: SIP Trunks page, click on New. Activate the Status and enter a name for the account under Name. Select the SIP Provider. Enter the relevant account information under User name, Password, Phone No. and SIP ID. Click on Apply.
Page 111: Internal Sip Telephony
Voice over IP (VoIP) Internal SIP Telephony SIP telephones connected via LAN or SIP telephony software on LAN workstation computers can also be operated with the OpenCom 130 / 150. Note The OpenCom 131 cannot be operated with a Media Gateway card. This is why SIP telephony is not supported.
Page 112: Fundamentals
Voice over IP (VoIP) licences, the available licences will be reassigned with the next incoming or out- going calls. A configuration dialogue of SIP telephony software Fundamentals VoIP makes the transmission of voice and telephony signalling via IP (“Internet Pro- tocol”) possible.
Page 113: Latency And Packet Length
Voice over IP (VoIP) A modern Intranet normally offers enough performance reserves and reliability to make good-quality VoIP telephony possible. Specific components can also be opti- mised; for example by using a modern switch which evaluates the TOS byte of IP packets, by replacing unreliable connections, or by using a separated VLAN for VoIP.
Page 114: Voice Quality
Voice over IP (VoIP) Required bandwidth (kbit/s) with respect to Packet Length and Codec Packet G.711 (not G.729A G.723.1 G.723.1 Length (ms) compressed) approx. 6.3 kbit/s 5.3 kbit/s 8 kbit/s 33.6 30.4 28.3 31.09 29.2 Note To ensure SIP compatibility, the older system telephones OpenPhone 63 IP and OpenPhone 65 IP do not support the G.723 codec any more.
Page 115 Voice over IP (VoIP) • G.711 A-Law or µ-Law (Level 1, uncompressed): The audio data of a PCM channel (64 kbit/s) is adopted one-to-one. Every VoIP terminal must support this codec. This codec can not be used with an ISDN data connection. •...
Page 116: Optimisation
Voice over IP (VoIP) Packet Propagation Delay and Packet Loss Value Quality Level Value Quality Level Propagation 4 level Loss > 6 % 4 level depreciation delay > 300 ms depreciation Optimisation If you detect a large fluctuation in the propagation delay during measurement, this may also cause the voice quality to deteriorate.
Page 117: Useful Services
Voice over IP (VoIP) 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.
Page 118 Voice over IP (VoIP) One of the SIP terminals sends of list of supported codecs. The second SIP terminal deletes the codecs from the list which are not supported and sends the shortened list back to the first SIP terminal. The exchanged codec lists can be filtered by the OpenCom 100 communications system, e.g.
Page 119 Note You can obtain the extended codec list as a description file from your local dealer or from the Aastra sales department. This file should not be edited which is why editing is not supported. Create a VoIP profile with extended codec entries with the following steps: Open the Telephony: Extended: VoIP profile page in the Configurator of the OpenCom 100 communications system.
Page 120: Voice Activity Detection (Vad)
SIP trunk and if you have set the G.711 codec. Note If you want to allocate the VoIP profile to an Aastra 675xi or Aastra 673xi SIP system telephone, the Voice Activity Detection option should be deactivated for all codecs.
Page 121: Mgw Interface Card
Voice over IP (VoIP) • 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. •...
Page 122: Sip Telephony
Voice over IP (VoIP) Enter the desired static IP address in the IP address configured field. Enter “0.0.0.0” to obtain an IP address via DHCP. Confirm with Apply. The configuration page displays the MGW interface card’s MAC address. You will need this for the static assignment of an IP address via a DHCP server.
Page 123: External Sip Connections
Voice over IP (VoIP) External SIP Connections The Telephony: Trunks: Route menu gives you the option to configure a bundle overflow, which automatically occupies a second line in case of a breakdown or over- occupancy of the SIP connection. You can also set up your system to route certain types of calls, such as international calls, to an SIP connection.
Page 124 Voice over IP (VoIP) • 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.
Page 125: Internal Sip Subscribers
Voice over IP (VoIP) internal subscribers is configured on the pages under Telephony: Call Distribution (Incoming DDI or Outgoing DDI). Please note the explanations on these pages in the online help. Furthermore, assigning extensions using placeholders (“wildcards”) is possible. The online help offers an explanation under the keyword Call Number Mapping.
Page 126 Voice over IP (VoIP) Technical Notes The names of settings for the various SIP telephones or SIP programmes are not uniform unfortunately. Please refer to the (Help) on the Telephony: Devices: VoIP Phones page and the following notes when configuring SIP subscribers: •...
Page 127 Voice over IP (VoIP) on the System Info: Codes page. Activate “SIP phones”. Please also note the corre- sponding information in the “OpenCom 100 / Aastra 800 – Operation on Standard Terminals User Guide” user guide. Alongside code number procedures, SIP subscribers can also use a series of functional features realized via the SIP protocol.
Page 128: Aastra 673Xi/675Xi Sip Telephones
Voice over IP (VoIP) Aastra 673xi/675xi SIP Telephones You can operate the SIP telephones of the Aastra 673xi and Aastra 675xi product fam- ilies at the OpenCom 100 communications system. The firmware of the communica- tions system already includes the matching firmware files (Firmware addons, “*_fwaddons_*.cnt”) for the following SIP telephones:...
Page 129 129). Note If you want to allocate the VoIP profile to an Aastra 675xi or Aastra 673xi SIP system telephone, the Voice Activity Detection option should be deactivated for all codecs. Under Telephony: Devices: System phones configure the common settings, the programmable keys and the softkeys for the Aastra 673xi/675xi (see Aastra 673xi/ 675xi Setup starting on page 128).
Page 130 Details about this can be found in the installation manual which is provided with the Aastra 673xi/675xi. If the Aastra 673xi/675xi has the factory default configuration, it will request an IP address configuration from the DHCP server of the OpenCom 100 communications system.
Page 131 Voice over IP (VoIP) – Topsoftkeys (Aastra 6757i only): You can label this function keys on the device display. You can switch between 2 layers of function keys using one of the function keys on the device. – Softkeys (Aastra 6755i /6757i only): You can label this function keys on the device display.
Page 132 Devices: VoIP Phone page by their shortened MAC address. 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.
Page 133: Voip System Telephones
The following telephones and software packages are available for VoIP system telephony: • Aastra 6773ip (OpenPhone 73 IP): This is a VoIP-enabled edition of the Aastra 6773 (OpenPhone 73) system telephone. This system telephone can be extended with up to three key extensions Aastra M671.
Page 134: Voip System Telephone Configuration
DHCP and TFTP network protocols. VoIP System Telephone Configuration The VoIP system telephones Aastra 6773ip (OpenPhone 73 IP) and Aastra 6775ip (OpenPhone 75 IP) obtain the required IP address configuration and operating software via the DHCP, BOOTP and TFTP IP protocols. After the power supply is assured, the device’s internal boot loader is started which controls the further start...
Page 135: Lan Dhcp Server
Voice over IP (VoIP) LAN DHCP Server If the LAN already uses a DHCP server to configure workstation computers, there are various options for correctly responding to VoIP system telephones’ DHCP, BOOTP and TFTP requests. A comparatively simple approach is described here. Configure the LAN’s DHCP server to ignore DHCP requests from the VoIP system telephones.
Page 136: Start Procedure
Telephone type OpenCom 130/131/150 Media Gateway card OpenPhone 63 IP opi63.cnt /ram/ip_tel/opi63.cnt OpenPhone 65 IP opi65.cnt /ram/ip_tel/opi65.cnt Aastra 6773ip opi7x.cnt /ram/ip_tel/opi7x.cnt (OpenPhone 73 IP) Aastra 6775ip (OpenPhone 75 IP) RFP 32 / 34 / 42 ip_rfp.cnt or /ram/ip_tel/ip_rfp.cnt or ng_ip_rfp32.cnt /ram/ip_tel/ng_ip_rfp32.cnt...
Page 137: 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...
Page 138 (JRE). This can be downloaded under the following web address: http://www.java.com/. The “IP Phone Configurator” can be started directly from the Product CD. Start Windows Explorer. Navigate to the Product CD. Double-click the “Aastra\IpPhone- Configurator.jar” file. The “IP Phone Configurator” dialogue opens. Select the desired language setting...
Page 139 Voice over IP (VoIP) Enter the network address of the VoIP system telephone. You have two connection types to choose from under Connection to IP Phone: – Deactivate the IP Phone address option to establish a broadcast connection via “UDP-Broadcast”. You have to select this type of connection if the VoIP system tel- ephone has not yet been assigned an IP address.
Page 140 Voice over IP (VoIP) IP parameter locally configured: Select the yes option to activate manual IP address configuration. Select the no option to activate automatic IP address configuration via BOOTP/DHCP. IP address and Netmask: Enter an available IP address and the network mask to be used by the VoIP system telephone.
Page 141: Aastra 277Xip (Openphone 7X Ipc)
The workstation computer requires a full-duplex-enabled sound card as well as a suitable headset for audio recording and playback. You will not need a licence to install 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 142: Installation
Licences. The system software includes a licence for a demo version for temporary use (60 days). Please contact your local dealer or Aastra sales department if you wish to purchase a permanent licence. Licences can be combined. Each licence can be acti- vated only once.
Page 143: Dect Over Ip
Administration of DECT terminals is done centrally via the OpenCom 100 Configurator in the Telephony: Devices: DECT Phones menu. Note DECT over IP® is a registered trademark of Aastra Telecom Schweiz AG. Properties DECT Base Stations DECT base stations can be connected to the OpenCom 100 via U accesses or via network (TCP/IP).
Page 144 ® DECT over IP IP-DECT • RFP 32: Access via shielded CAT5 Ethernet cable (STP cable, Shielded Twisted Pair cable) with up to 100 metres of cable from the last Ethernet switch, integrated antennas; 8 voice channels • RFP 34: like the RFP 32; mounted outside enclosed areas (IP55); external antennas •...
Page 145: Features
® DECT over IP 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.
Page 146: Configuration
® DECT over IP Configuration One of the DECT over IP base stations that is installed assumes coordination and con- figuration 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 147: Dual Operation
® DECT over IP Configurator: Telephony: Devices: DECT over IP User administration and set-up of DECT terminals is done in the Configurator of the OpenCom 100 as well. The DECT over IP Manager offers a separate web user interface to manage the set- tings of devices with WLAN functions.
Page 148: Synchronisation
® DECT over IP 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 simultane- ously. Synchronisation can be conducted via U access. It cannot be conducted via an Ethernet/IP connection.
Page 149 ® DECT over IP 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. The WLAN settings are then made as follows: Set up the existing DECT over IP base stations in theOpenCom 100’s Configurator.
Page 150 ® DECT over IP DECT over IP/OpenMobility Manager: WLAN Profiles Use the following settings for standard operations. General Settings • Select the desired WLAN Profile and activate the Profile Active option. • Enter a SSID (Service Set Identifier, wireless network identification) to identify a network.
Page 151 ® DECT over IP Security Settings On no account should you use Open System or Wired Equivalent Privacy (WEP) set- tings, whether out of convenience or in order to avoid configuration problems, unless of course you want to start up an Internet Cafe! •...
Page 152: Configuring For A Remote Location
Call up Windows explorer. Browse to the communications system’s product CD. In the “Aastra” directory, double-click the “OM_Configurator.jar” file. Note You need a Java runtime library to be able to run Java programmes. If you don’t have one installed, you can download the installation programme from the http:// www.java.com/ web site.
Page 153 ® DECT over IP To log in to the dialogue, you enter: User: “admin” Password: “Admin” Enter the MAC address of the DECT over IP base station. The MAC address will be printed on the label on the DECT over IP base station’s casing. Click on List config- uration.
Page 154: Pbx Cascading
PBX Cascading 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 loca- tions with different PBXs, this is possible by PBX Networking (see page 157).
Page 155: Functionality Of Pbx Cascading
PBX Cascading 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.
Page 156: Putting A Cascaded Pbx Into Operation
PBX Cascading Putting a Cascaded PBX into Operation Proceed as follows to put a cascaded PBX system into operation: 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.
Page 157: Notes
PBX Cascading Note Changes to the configuration while initialising the slave system may trigger error re- ports referring to the ongoing initialisation. You can see that the initialisation has been completed from the display on the system telephone connected to the slave system. Notes Observe the following when operating a cascaded PBX system: •...
Page 158: Licensing Information
In this case, new activation keys for the use of additional programme packages must be generated on the Aastra licence server. The licensing confirmation for the cascading contains all the information you need to carry out this procedure.
Page 159: Pbx Networking
PBX Networking 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. •...
Page 160: Point-To-Point Connection Technology
PBX Networking Note Networking via IP network connections requires a MGW interface card M100-IP. The OpenCom 131 does not offer networking via IP network connections. Trunk line Point-to-point connection Example of a PBX network Various line types and transmission protocols can be used for point-to-point connec- tions.
Page 161: Master/Slave
PBX Networking 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 pro- tocol 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.
Page 162: Point-To-Point Connection Lines
PBX Networking Example: In the above case you could reverse the L1 slave/master setting for the con- nection 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.
Page 163: Connection Via An Active Transmission System
PBX Networking 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 PBX 2, S...
Page 164: Connection Via The Public Network
TC system networking via network connections Feature Q.SIG-IP Q.SIG-IP OC100 / OC1000 tie line tie line Aastra OC100 / OC1000 / Aastra Aastra 5000 Establishing a call (“basic call”) with call- number transmission name information...
Page 165: Connection Via Q.sig.ip
PBX Networking TC system networking via network connections Feature Q.SIG-IP Q.SIG-IP OC100 / OC1000 tie line tie line Aastra OC100 / OC1000 / Aastra Aastra 5000 Presence (Messenger) VIP call announcement busy signalling automatic feature detection Tip: The following applies to connections to OpenCom 1000 systems: As opposed to line-connected Q.SIG, with Q.SIG-IP and SIP tie line...
Page 166: Connection Via Sip Tie Line
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 Aastra 800 and OpenCom systems.
Page 167 This means via SIP tie line you can only use connections between OpenCom 100, OpenCom 1000, Aastra 800 and Aastra 5000 systems. Two licences are required when networking two OpenCom 100 with a SIP tie line – a licence for each end point.
Page 168: Configuration
PBX Networking Configuration The possible configurations described below can be set up in the Web console using the Telephony: Trunks menu. Bundles A bundle is a group of lines of the same type and direction. A line can only be assigned to one bundle.
Page 169: Numbering
PBX Networking • PBX 1 first searches for a free channel in the “C” bundle. • If all the lines in bundle “C” are busy, the system tries to set up a connection via bundle “E”. PBX 3 switches the connection through, provided it is appropriately configured (refer to Numbering starting on page 167).
Page 170: Technical Details
PBX Networking 100-199 200-299 300-399 3: e 4: b 5: k 5: h D: c D: f D: d 400-499 500-599 3: i D:Default D: a D: g Route Example of closed numbering tables The automatic switching of call requests (i.e. routing) by means of bundle overflow or default numbering can lead to “circular switching”.
Page 171 PBX Networking Tip: If, for example, you are configuring a route which can be seized using routing code “5” and have selected one or more bundles for this route, change the Prefix for dest. call number at incom- ing internal setting to “5” for this bundle in order to enable the route to be reseized.
Page 172: Telephony
Telephony Telephony 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. The external call number can be either a local area code or a country area code.
Page 173 Telephony This step is optional as the country code is preallocated due to the Country setting under System: Common. Call the Telephony: Settings page. Click on the Change button. Enter the country code without a zero in front into the International area code field, e. g. “49” for Germany.
Page 174: 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 175: Further Information
Telephony Number dialled Number actually used +493061042007 2007 You can only enter the plus sign (after E.123) with a SIP telephone (see Internal SIP Subscribers starting on page 123). There is a “E.164 conversion” in this case also. 003061042007 03061042007 There is no “E.164 conversion”...
Page 176: Call Forwarding
Telephony Call Forwarding The current version of the OpenCom 100 communications system also offers configu- ration 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 177: Attributes
Telephony Call Forwarding Name Description Call forwarding by a system user Call forwarding via OpenAttendant(with the Connect to phone number and Connect to voicebox function) or via OpenVoice(with the secretarial function) Attributes A call forwarding chain can contain any call forwarding types and call forwarding users.
Page 178: Loop Detection
Telephony Loop Detection Loops can generally occur during a call forwarding chain, e. g. when the call for- warding destination refers back to the call forwarding source. This is why a forwarded call has a call forwarding history. When the next call forwarding destination is already included in the call forwarding history, a loop is detected and any further call for- warding is prevented.
Page 179: Hunt Groups
Telephony Hunt Groups A hunt group is an internal call number which can reach multiple users. An incoming call is signalled to all users of a hunt group. A hunt group is configured in the Config- urator in the Telephony: Groups: Hunt groups menu. Call signalling is independent of the Type setting in the hunt group: •...
Page 180: External Call Forwarding
Telephony 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 181: Busy Keys
Telephony • The “Show hunting group no. as via” option for hunt groups has been omitted. Instead, use the Display: Call forwarding via option in the User Manager: User groups menu. • The “Courtesy Service” function used to be for directly determining whether a user was currently busy or not and the corresponding announcement played.
Page 182: Pin Code Telephony
Q.SIG-ISDN, Q.SIG-IP and SIP-Tie-Line. The Protocol extension option has to be activated in the bundle configuration for Q.SIG-ISDN. • Busy keys only function between OpenCom 100 / Aastra 800 communications systems with the release 10 system software. • If there are multiple lines available in a bundle for PBX system networking, one of the lines is selected for busy-key signalling.
Page 183: Configuration
Telephony Configuration You can configure the “PIN Code Telephony” feature separately for each company. Configuration is done with the following steps: Call the OpenCom 100 communications system Configurator. On the intro- ductory page, change the Level option to Expert. Open the User Manager: User groups menu page. Click on the New button. Enter a designation into the Group name field and select an existing user group as a template.
Page 184: Switch Authorisation
Telephony The route configured for the “PIN Code Telephony” feature is used to make a call in that the seizure code for the standard route is also replaced by another seizure code if applicable. Furthermore, the authorisations are activated for the user group designated for the “PIN Code Telephony”...
Page 185: Implementation
Telephony Click on the user group for the user who is to execute the “Switch authorisation” feature. Activate the Switch authorisation option. Confirm with Apply. Open the Telephony: Extended: Companies menu page. Click on the header of the company desired (default: “Company 1”). Under the Switch authorisation header, select the User group temporarily active due to switching (e.
Page 186: Fixed Mobile Convergence
Fixed Mobile Convergence Fixed Mobile Convergence The “Fixed Mobile Convergence” (FMC) feature offers operation of mobile telephones on the OpenCom 100 communications system. Connections to and from the mobile telephone are directed via the communications system. This is done by the communi- cations system managing the mobile telephone as an internal terminal with its own internal call number.
Page 187 • There is special software available for a series of mobile telephones: “Aastra Mobile Client”. This software makes it convenient to use FMC telephony functions. •...
Page 188 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 189 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 190 Configuring FMC telephones on the OpenCom 100 communications system requires a licence. With this licence you can also install a corresponding number of FMC clients (“Aastra Mobile Client”). For more detailed information, please consult the licence confirmation you received. Documentation The following sections provide information on configuring the “Fixed Mobile Conver-...
Page 191: Configuring Fmc Telephones
The user can set important system features, e. g. enquiry, call diversion, or call pro- tection, by using code-number procedures. The code-number procedures are described in the “OpenCom 100 / Aastra 800: Operation on Standard Terminals” user guide. The documentation is available as a PDF file on the OpenCom 100 communications system product CD.
Page 192 FMC telephone. To create the new FMC telephone confirm with Apply. 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”...
Page 193: 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 features 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 194 Automatic start Provides automatic start of the software (Only in the Settings menu of the when the mobile telephone is switched “Aastra Mobile Client” software) Auto login Activate this when the CLIP Authentication option is being used. Deactivate when the DTMF login procedure (password procedure) is to be used.
Page 195 Both the configuration and licence SMS are automatically deleted after commissioning of the client. 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 196 Fixed Mobile Convergence Operating FMC functions via the software is described in the “Fixed Mobile Conver- gence – Using mobile telephones on the Aastra 800 / OpenCom 100 communications system” user guide. Note When you have configured the “Aastra Mobile Client” software for the DTMF log-in...
Page 197: Team Functions
Team functions can only be configured on the corded system telephones Aastra 677x (OpenPhone 7x) and their softphone variants because only these have the required features.
Page 198 Team Functions 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) Up to three of these key extensions can with an additional key extension...
Page 199: 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 200 Team Functions Secretary TrK 11: Secretary TrK 10: Executive DK 10: Executive Executive TrK 10: Executive TrK 11: Secretary TrK 12: Private Executive´s Parallel TrK 10: Executive TrK 12: Private Example: executive/secretary team Line Seizure The secretary can be reached on the call number 11 (trunk key TrK 11: secretary’s office).
Page 201: 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 202: 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 203: 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 Aastra 6775 (OpenPhone 75) system telephone with all call keys programmed as trunk and team keys.
Page 204 Team Functions 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 Mi.14.Feb.07...
Page 205 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. Line Busy Indication If a line is busy, e.g.
Page 206: Call Queue
Aastra 6775 (OpenPhone 75) / 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.
Page 207: Activation Of Queues
Call Queue Note As calling fax machines often operate with the “voice” service indicator (e.g. on ana- logue 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” func- tions, for example, in order to configure an enquiry station for an operator.
Page 208: Pickup
DECT base stations can be connected to operate cordless system ter- minals. 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) or the mobile terminal, the Aastra 610d / 620d / 630d. Configuration •...
Page 209 Calls which are in the Aastra 6775 (OpenPhone 75) queue must still be answered on this telephone. New calls are signalled on the mobile Aastra 610d / 620d / 630d or enter its queue, allowing the Aastra 610d / 620d / 630d to be used as a mobile enquiry station.
Page 210: Group Of Three Enquiry Stations
Configure the three Aastra 6775 (OpenPhone 75) telephones under Telephony: Devices. • Configure a trunk key with its own telephone number for each of the Aastra 6775 (OpenPhone 75) telephones under Telephony: Devices: System telephones. • Configure a hunt group of the parallel type under Telephony: Groups: Hunt Group, and include the three telephone numbers of the trunk keys in this hunt group.
Page 211 Call Queue If attendants leave the station, they sign off from the hunt group by means of a feature key. In contrast to Example 1, further calls do not have to be processed after the sign-off, as the calls are also registered in the queues of the other signed-on enquiry stations.
Page 212: Multi-Company Variant
Multi-Company Variant Multi-Company Variant Communications systems are frequently shared by several companies. These com- panies want to jointly use the existing infrastructure (e.g. the existing lines and fea- tures of the system), while at the same time they wish to organise and pay for their communication completely independently of one another.
Page 213: Configuring The Multi-Company Variant
Multi-Company Variant Configuring the Multi-Company Variant The multi-company variant can be commissioned and configured by the system administrator of the OpenCom 100 without any major effort. In the multi-company variant, the communications system behaves in exactly the same way as the single- company variant.
Page 214: Configuring And Managing Companies
Multi-Company Variant Configuring and Managing Companies Up to 5 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 215: Assigning A Bundle/Sip Trunk
Multi-Company Variant Assigning a Bundle/SIP Trunk Connections of the same type and in the same direction are arranged in a bundle (e.g. 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 bundle of the OpenCom 100, each of the available bundles must be assigned to one of the com- panies.
Page 216: Configuring The Company Exchange
Multi-Company Variant code is allocated for one of the configured companies, the route concerned cannot be seized by the members (user groups) of this company. Configuring the Company Exchange An internal telephone number must be set up for each company which represents the exchange, i.e.
Page 217: Making Calls Between Companies
Multi-Company Variant Users can also use the telephone book of their company with the OpenCTI 50 and Phone Book Web applications, assuming they are authorised to use these applica- tions. In addition, it is also possible to assign a user group with the authorisation to edit foreign company telephone books.
Page 218: Configuring The Pc Software
Configuring the PC Software Configuring the PC Software Further possibilities of use can be implemented on a workstation computer with the Windows operating system by installing drivers and programmes. You can find the installation programmes required for this on the product CD that comes with the OpenCom 100.
Page 219 Configuring the PC Software End the installation with a function test. With a double-click on the newly created desktop icon, start the StartCenter programme. Select from the fold-down selection the desired TC-system type. Available offline configurators are now dis- played as symbols. Double-click on a configurator symbol and select from the dia- logue Start with Factory settings.
Page 220: Browser For Opencti 50 And Openhotel 100
Configuring the PC Software • During deinstallation of the programme StartCenter, the entire installation directory with all its sub-directories is deleted. Backup the necessary offline con- figurators before uninstalling. Browser for OpenCTI 50 and OpenHotel 100 You can simplify the daily use of the OpenCTI 50 and OpenHotel 100 Web applica- tions using the Web browser especially adapted for the OpenCom 100.
Page 221: Synchronising The Pc Clock
Configuring the PC Software Synchronising the PC Clock With the network service SNTP (simple network time protocol) it is possible to syn- chronise the internal clock of a workstation computer 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: Go to the Configurator, System: Common menu.
Page 222: Application Interfaces
Application Interfaces Application Interfaces The OpenCom 100 communications system supports a series of application interfaces which are used by external systems to access functions of the communications system. Communication between the external system and the OpenCom 100 com- munications system is principally transported via the LAN connection or using the IP network protocol.
Page 223: Setting Up Tapi Interface
You can also develop your own CTI applications or adapt existing CTI applications for the CSTA interface. To do so, you need the CD-ROM, the developer documentation, library files and sample applications, available separately. Contact Aastra support if you need this CD-ROM.
Page 224 Phone and Modem Options icon. Change to the Advanced tab. From the list of installed driver software, select Aastra 800/OCX/OpenCom Service Provider and click on Configure. In the following dialogue you will find a list with the configured connections for the user who is currently logged on.
Page 225 Application Interfaces figured on the OpenCom 100. This user must be allocated a system terminal. Confirm your entry with OK. The new connection is now configured. Close the opened dialogues with OK and Close. Testing the TAPI Function In the Start menu, select Programs: Accessories: Communication and then start the programme called Phone Dialer.
Page 226: Ldap Interface
Application Interfaces LDAP Interface Directory information can be transferred using the LDAP protocol. A central service (LDAP server) manages a comprehensive, hierarchically organised directory which can be queried by an LDAP client via LDAP. The OpenCom 100 communications system supports two different LDAP applications: •...
Page 227: Querying External Ldap Server
Application Interfaces 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 tele- phone book.
Page 228 Phone book header. After configuration, the information queried via LDAP is available on authorised system telephone, DECT system terminals and Aastra SIP system telephones as well as in the applications “ OpenCTI 50” and “Aastra CTI Touch”. Information queried via LDAP is considered for telephone book searches and for displaying names during incoming calls in addition to the information from the internal telephone book.
Page 229 Application Interfaces • Each individual LDAP-queried record is reserved for a definable time in a OpenCom 100 communications system cache (setting: Delete cache in minutes, 50 cache entries per company each with a separate time counter per entry). You should shorten this time (e. g. to 10 minutes) if, for example, the assignment of guests and room telephones in a hotel is managed via the LDAP server.
Page 230: Snmp Interface
Use the Aastra Name program for more advanced LDAP configuration, for connecting additional data sources or for additional call number conversions. After authorisation via a license key, the Aastra Name program offers a LDAP service which can be queried by the OpenCom 100 communications system. The Aastra Name program provides you with the following features: •...
Page 231: Installing Snmp Agent
Enter the IP address of the OpenCom 100 communications system. Terminate the installation assistant with the Next, Install and Finish buttons. During installation a Windows service “Aastra Call Server Supervisor Service” is con- figured. This service starts the SNMP Agent. This means that the SNMP Agent is auto- matically started with Windows and runs in the background, even when no Windows user is logged on.
Page 232 Application Interfaces Telephony: Settings: SNMP Enter the IP address of the SNMP Manager into the SNMP Manager input field. Confirm with Apply. The IP address of the SNMP Manager is made available to the SNMP Agent in a config- uration file via the TFTP server of the OpenCom 100 communications system.
Page 233: Frequently Asked Questions
Frequently Asked Questions 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 qual- ified personnel.
Page 234: General/Hardware
Frequently Asked Questions Power Good LED AC adapter LAN LEDs Activity LED LAN LEDs (Ethernet-Switch) Position of LEDs on the OpenCom 150 With the OpenCom 150 Rack, the LEDs for LAN0 and LAN1 are placed on the front panel. General/Hardware The OpenCom 100 is not functioning.
Page 235: Telephony
Frequently Asked Questions 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 oper- ation.
Page 236 Configurator (Telephony: 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 – Operation on Standard Terminals User Guide” user guide.
Page 237: Pbx Networking
Frequently Asked Questions 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.
Page 238: Dect
Frequently Asked Questions DECT Note In the following explanations it is assumed that a U interface card has been in- stalled (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.
Page 239: Lan
Frequently Asked Questions 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 con- nection. 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.
Page 240: Internet
Frequently Asked Questions 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 (Network: Hosts menu).
Page 241: Technical Specifications
Technical Specifications 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: 1.9...
Page 242 Technical Specifications OpenCom 130 (Cont.) ports for system terminals and RFP 22 / 24 Basic module: 3 x to connect system ter- DECT base stations minals, DECT-enabled Add-on module: up to 16 x, all DECT-ena- bled; possible interface cards: – 4 x U –...
Page 243 Technical Specifications OpenCom 130 (Cont.) Doorstation equipment interface card for connection of doorstation equip- Basic module: 1 x (optional) ment Contact load of actor 1.5 A / 125 V – Voltage range = 5 V… 30 V ≈ Sensor Switched by low AC voltage –...
Page 244 Technical Specifications OpenCom 131 (Cont.) ports for system telephones Main module: 3 x to connect system ter- minals, DECT-enabled – Supply voltage 40 V ± 10% – Supply power 3 VA per U – Range 1,000 m a/b ports for analogue terminals with pulse or Main module: 8 x DTMF dialling, flash duration of 60 to 310 ms...
Page 245 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 246 Technical Specifications OpenCom 150 (Cont.) – Supply power 3 VA per U – Range 1,000 m a/b ports for analogue terminals with pulse or Possible interface cards: DTMF dialling, flash duration of 60 to – 4 x a/b 310 ms –...
Page 247: Notes On Disposal
Notes on Disposal Notes on Disposal In order to avoid any possible effects resulting from the disposal of electrical and elec- tronic 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 248: Index
Index Index Preconfiguration 85 Aastra 277xip (OpenPhone 7x IPC) 139 Preparation 82 Aastra 677x (OpenPhone 7x) 66 Remote configuration 86 Actor Resetting the system data 90 See Intercom system 61 Saving and loading the Actor/sensor port 56 configuration 85 Adapter (expansion module) 34...
Page 249 Index Doorstation equipment interface card 36 Installation 29, 128 DSL 57 Mounting location 31 DSL port 57 Ports 42 DSS1 158 Scope of delivery 29 DTMF 115 Wall mounting 32 Intercom system 61 Interface cards 35 E.123 124 Interface cards (installation) 38 E.164 conversion 170 Interface cards (overview) 47, 50 E-mail 15...
Page 250 Index LAN (basic module) 34, 42, 43, 44 Networking 13 LAN1 34 NTBA 233 LAN2 153 NTBBA 57 PCM 44 Numbering 167 Positions 45 S0 42, 43 S2M 71 Offline Configuration 216 Upn 42, 43 Online help 84 V.24 42, 43, 44, 63 OpenCTI 50 browser 218 Ports (see Interfaces) 53 OpenHotel 100 browser 218...
Page 251 Index SIP 115, 120 Aastra673xi/675xi 126 V.24 add-on card 42, 43, 44 External 107, 121 V.24 interface card 36 Internal 109, 123 VAD 118 SIP (external) 14 Virtual Call Numbers SIP (internal) 14 Call forwarding 176 SIP tie line 14, 164 Voice Activity Detection 118 SIP-DDI 122 Voice mail 61...
Page 252 Notes Notes...
Page 253 Notes Notes...
Page 254 Notes Notes...

This manual is also suitable for:

Opencom 130 Opencom 131 Opencom 150

Aastra OpenCom 100 Series Mounting And Commissioning User Manual

Features

Factory Settings on Delivery

Telephony Basic Settings

Authorisations

Internet Functions

Update Notes

Update Licence

Technical Notes

Updating

Installation

Scope of Delivery

Safety Precautions

Declarations of Conformity

Mounting Location

Wall Mounting

Installing an Expansion Set

Installing Interface Cards

Available Ports

Interface Cards

Port Assignment, Termination, Cable Lengths

Power Failure

Connectible Terminals

Installing the Memory Card

Aastra 677X: Extensions and Accessories

Power Supply Unit

Key Extensions

Headset

S 2M Connector Module

Installation

Configuration

Mounting the Opencom 150 Rack Infocom System

Safety Precautions

Technical Data

Pinning of RJ 45 Jacks

Scope of Delivery

Configuration

Brief Guide to Initial Configuration

Configuring the Opencom 100

Configuration Examples

Opencom 100 in Computer Networks

Introduction to TCP/IP

Opencom 100 in a Serverless LAN

Opencom 100 in a LAN with an IP-Enabled Server

Branch Link

Useful Information on Internet Access

Voice over IP (Voip)

Quick Start

Fundamentals

Media Gateway (MGW)

SIP Telephony

Voip System Telephones

Aastra 277Xip (Openphone 7X IPC)

DECT over IP

Properties

Configuration

PBX Cascading

Variants of PBX Cascading

Functionality of PBX Cascading

Putting a Cascaded PBX into Operation

Licensing Information

PBX Networking

Connections

Point-To-Point Connection Technology

Point-To-Point Connection Lines

IP Network Connections

Configuration

Technical Details

Telephony

E.164 Conversion

Call Forwarding

Busy Keys

PIN Code Telephony

Switch Authorisation

Fixed Mobile Convergence

Configuring FMC Telephones

Team Functions

Introduction

Examples of Use

Call Queue