2N NetStar Admin manual User Manual

Loading...

2N® NetStar

Communication System

Manual NS Admin

Version

3.1.0

www.2n.cz

The 2N TELEKOMUNIKACE joint-stock company is a Czech manufacturer and supplier of telecommunications equipment.

The product family developed by 2N TELEKOMUNIKACE a.s. includes GSM gateways, private branch exchanges (PBX), and door and lift communicators. 2N TELEKOMUNIKACE a.s. has been ranked among the Czech top companies for years and represented a symbol of stability and prosperity on the telecommunications market for almost two decades. At present, we export our products into over 120 countries worldwide and have exclusive distributors on all continents.

2N® is a registered trademark of 2N TELEKOMUNIKACE a.s.. Any product and/or other names mentioned herein are registered trademarks and/or trademarks or brands protected by law.

2N TELEKOMUNIKACE administers the FAQ database to help you quickly find information and to answer your questions about 2N products and services. On www.faq.2n.cz you can find information regarding products adjustment and instructions for optimum use and procedures „What to do if...“.

Declaration of Conformity

2N TELEKOMUNIKACE hereby declares that the 2N® NetStar product complies with all basic requirements and other relevant provisions of the 1999/5/EC directive. For the full wording of the Declaration of Conformity see the CD-ROM enclosed and at www.2n.cz.

The 2N TELEKOMUNIKACE company is the holder of the ISO 9001:2009 certificate. All development, production and distribution processes of the company are managed by this standard and guarantee a high quality, technical level and professional aspect of all our

Content

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1

About Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6

1.2

About Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7

1.3

Connecting to PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9

1.4

Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

1.5

PBX Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17

2. Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

26

2.1

Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

2.2

Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

29

2.3

Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

33

2.4

Board and Port List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34

3. Virtual Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35

3.1

BRI and PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36

3.2

Cornet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

43

3.3

ASL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

45

3.4 CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47

3.5 GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51

3.6

SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

57

3.7 SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

67

3.8

Virtual Port Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

69

4. SIM

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

78

4.1

SIM Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

79

5. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

80

5.1

Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

81

5.2

Service Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

82

5.3

Supervision Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

91

5.4

DB connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

101

6. Global Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

103

6.1

Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

104

6.2

Emergency Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

107

6.3

Localisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

108

6.4

Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110

6.5

Language Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113

6.6

Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

114

6.7

Conference Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

116

6.8

Progress Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

119

6.9

Ring Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

124

6.10

AutoClip Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

125

6.11

Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

127

6.12

Scheduled tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

131

6.13

Status Control parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

133

6.14 DTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

134

6.15

Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

135

6.16

Time Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

140

6.17

Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

145

7. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

148

7.1

Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

149

7.2

External Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

156

7.3

Complex Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

158

7.4

Switch Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

159

7.5

Routing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

162

7.6

Identification Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

197

7.7

AutoClip Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 

8. Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

203

8.1

Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

204

8.2

User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

215

8.3

Extension Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

217

8.4

Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

218

8.5

Phone Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

223

9. Setting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

9.1 Setting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

10. Billing and Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

243

10.1 Billing and Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

244

11. Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

11.1

Other Useful Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

247

11.2

Mobility Extension Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 

11.3

NetStar Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

263

1. Introduction

Here is what you can find in this chapter:

1.1 About Help

1.2

About Application

1.3

Connecting to PBX

1.4

Configuration Menu

1.5

PBX Activation

5

1.1 About Help

Document format

Document version: 3.1.0

This document serves as a Help and Manual for the configuration of the 2N NetStar communication system by the NSAdmin program. 2N reserves the right to modifications.

Conventions

The following fonts are used in the text:

#Hypertext

Hyperlink to another place in the document or outside the document.

#Document contents item

All page headings are listed in the table of content. Clicking an item in the table of content will display the respective part of the page.

Part

Headings of the individual page topics listed in the table of contents. You can click this heading and jump to the top (table of contents) of the page where other topics can be selected.

Important words

The text used in NSAdmin and important words in the text we want to emphasise are highlighted.

HW – Rack

This form is used instead of a verbal description of the location of an item in the TreeView (tree in the left-hand part of the NsAdmin window). It means that in the TreeView you need to click the HW item and then the Rack item in it.

6

1.2 About Application

About Application

NSAdmin is a configuration tool that helps configure the 2N® NetStar communication system, version 2. The application is designed for an x86 platform using the WINDOWS operating system connected with 2N® NetStar through a network. It is controlled by a mouse and, secondarily, a keyboard. NSAdmin uses the TCP connection or modem and communicates with 2N® NetStar basically via port 6992.

As a necessary condition for using this configuration tool under the Windows XP OS, a service pack 2 and Framework v.3. have been installed. The program does not work without these components.

Main menu of the configuration tool

Once the configuration tool has been started, a window is displayed helping to configure connections to PBXs, analyse traces and start up the Help. The main menu offers the following options:

Admin

Settings – here open a dialogue with the global configuration tool settings.

Language – here choose one of the supported languages.

Exit – push this key to exit the configuration tool.

Trace – operations with previously saved traces are only available here at the current stage.

Load trace from file

Add trace from file

Trace analyser – push to open a trace analysis window. Help – here start the Help in the chosen language.

Global settings of the configuration tool

This dialogue includes three tags with the following parameters:

XML script

Type of debugging – use this section to enable and define the range of displaying the xml trace in the configuration tool. The PBX trace cannot be set here.

Indent size – use this parameter to define the indent size for the xml trace.

View – this is an auxiliary function for trace analysis using database.

Show current window name – check this option to display the current window name in the right-hand bottom corner.

Show object IDs – check this option to display the current object Id in the right-hand bottom corner. This is an easy way how to know e.g. the

7

port Id and find the port in the trace.

General

Set colours of virtual ports – here define the colour for each virtual port or disable this function.

Set colours of tables – here define the background colours for tables or disable this function.

Set colours of logins – here define the colour for each user login or disable this function.

Set colours of extensions – define the colour for each extension (SIP, external, etc.) or disable this function.

Click on Default in each of the General subtags to set the default colours.

Advanced – Use the Ask before delete if object is used in configuration parameter to enable/disable warning display before removing the router or any of the routing objects from configuration.

Login

Copy devices structure from old version storage – Disable/enable copying of the the PBX structure(s) from earlier configuration tool versions. Once copied, the selected PBXs can be removed by deleting only (not by unselecting).

To confirm a configuration setting, use the OK button and to exit the dialogue without saving, push the Cancel button.

8

1.3 Connecting to PBX

Icons of connection section

The figure below presents all icons of this section.

Figure: View of PBX Login Icons

Connect to PBX – use this icon to connect the configuration tool to the PBX via a selected connection.Icon meanings from the left:

Create group – use this option to create a group of PBXs on the same level as the selected object or nested into the existing group.

Create PbX – use this option to create a PBX on the same level as the selected object or nested into the existing group.

Create connection – use this option to create a connection to the selected PBX.

Properties – here set or change the properties of a selected object. A name is only assigned to groups. For details on PBX and connection settings see below.

Delete – select this option to delete a group, PBX or connection.

Auto login – use this option to enable an automatic PBX connection via the current connection after starting the configuration tool. One automatic connection may only be active at a time. By selecting another setting you cancel the previous one.

Cancel auto login – use this option to cancel the automatic connection without specifying any object.

In addition, the following options are available in the context menu:

Import PBX structure – select this option to import a predefined PBX structure as described below.

Export PBX structure – select this option to export the current PBX structure for later PC connection use.

Import database – select this option to import the database of a selected PBX in the off-line mode only. In the on-line mode, the database is replaced with the PBX data.

Export database – select this option to export the database of a selected PBX in the off-line mode only.

Connection structure

In this menu you can create groups and subgroups (nested groups) and, subsequently, add PBXs to them. You can create PBXs without groups too, but this might be confusing if you use a higher number of PBXs. Then you can create connections for particular PBXs using the TCP/IP and modem protocols. The records are arranged alphabetically.

For easier administration of existing records, a record moving option using the mouse has been implemented on this screen, also designated as drag & drop.

9

Figure: View of Possible PBX Connection Structuret

To change the PBX connection settings use the Properties icon.

PBX properties

The dialogue shown in figure below helps you create a PBX or change the properties of an existing PBX. The parameter meanings are as follows:

Name – define the name of the PBX to be connected.

Folder – use this parameter to define the path to the folder for the configuration to be saved.

Autosave – use this option to enable automatic database saving in the off-line mode.

Autosave database after – here set the interval for automatic database backup. This function may only be used for the off-line mode.

Delete autosave item older than – here set the maximum time for keeping old database backups in the storage folder. This function can only be used in the off-line mode.

Autosynchronisation – If this selection is active, the tool tries to synchronise the data automatically with the PBX without inquiring. This function can only be used in the off-line mode. If this selection is active, 'Loading from PBX' is performed if the off-line database is empty. 'Display changes' is performed if the database has been synchronised, the identifier matches and 'Database from Autosave' has not been selected. Otherwise, the synchronisation type dialogue is invoked. If this selection is inactive, the dialogue is invoked in all cases.

10

Figure: View of PBX Property Settings

Connection properties

The dialogue shown in figure below helps you create a PBX connection or change the properties of an existing PBX connection. The parameter meanings are as follows:

Connection name – here enter the name of the selected connection.

Modes – use this parameter to define whether the connection will support the on-line, off-line or both modes.

Download trace – use this option to disable or restrict trace downloading from the PBX. Particularly useful for modem connections. *Any of the following modes can be selected:

Only new – Only the new trace is sent to the tool existent since the moment of PBX connection.

Never – No trace is sent to the tool (useful for trouble making modem connections).

Always – Approximately a 300kB – 1MB trace is read out of the PBX buffer upon connection and sent to the tool. Useful for sending the trace after the PBX start up.

Connection type – use this option to define the PBX connection type. Typically, the TCP/IP or modem connection is selected. Use the TCP/IP, enter the PBX CPU IP address and the port to be used (6992 by default). With a modem choose the one that supports the X.75 protocol.

If unsuccessful try again – define the time interval between the PBX connection attempts in case of failure (PBX switch-off or restart).

Connect as – here define the login and password data for a secured PBX access.

11

Figure: View of Connection Property Settings

Connecting to PBX

After an automatic or manual initiation of a PBX connection, the dialogue shown in figure below is displayed. It provides information on the PBX to be connected, the PBX firmware version (if detected), the last known connection error and, in the case of automatic connection attempts, also the remaining time to the next attempt. To connect immediately (before the timeout), push the Try again button. The Cancel but ton is used for leaving the dialogue.

12

Figure: View of Connection Course Dialogue

If you are unable to connect to your PBX, please check whether:

1.the PBX has been switched on;

2.the PBX has been connected to the network;

3.both sides have the same IP address and port;

4.the used communication port has been opened;

5.the appropriate firmware and configuration tool versions are used;

6.the used communication port is not blocked by your antivirus software.

13

1.4 Configuration Menu

Main menu

After a successful connection to the PBX, the configuration part of the application is displayed. The main menu of this view is shown in figure below and contains the following options:

Administrator

Logout PBX – use this option to logout the configuration tool from the PBX and return to the previous menu for another connection as described above.

Connect/Disconnect – use these options off-line to connect/disconnect the configuration tool to/from the PBX.

Save changes – here save all changes made since the last save.

Undo changes – here cancel all changes made since the last save in a menu.

Settings – use this option to invoke a global setting dialogue as described in Chapter 1.2 About Application.

Language – choose one of the supported languages.

Exit – use this option to exit the configuration tool.

Trace

Load trace from file – use this option to load a trace from the file, thus clearing the previous one.

Add trace from file – use this option to load a trace from the file and add it to the existing one. You can interconnect traces for easy analysis.

Save trace to file – use this option to save the current on-line trace to a file. The configuration tool always saves an entire trace independently of whether the filter is being applied or not.

Trace analyser – here open the trace analysis window.

PBX

Upgrade – select this option to display a firmware upgrade dialogue. Having been chosen, the firmware file is uploaded into the PBX and unpacked. After a restart, the new firmware is used.

Import logs from PBX – select this option to get an easy access to the PBX logs without using other applications. You can import All logs or selected logs only (Selectively).

All – after selecting a directory, the config.db and aoc.db files and the contents of the internal/log and /var/log directories are imported.

Selectively – select this item to display a dialogue for downloading selected logs from the PBX. The user can enter the files through a storage as defined in the Global Data – Storage Manager menu.

Restart PBX – use this option to initiate the PBX restart.

Restart ústředny – Volba umožňuje restart ústředny.

Restore factory settings – use this option to restore the factory default values. Choose one of the two options available in the dialogue window and press OK twice to confirm the selected action.

Wizards

Activation wizard – for details refer to the next chapter, 1.5 PBX Activation.

Import/export company structure – here invoke the company structure

14

import/export dialogue. The csv and xml files are supported.

Database import – click on this option to display the database importing window. Select From file or From PBX. If you choose From PBX, all the PBXs available for database import will be displayed. Use the Rule parameter to specify which of the original settings should not be overwritten by database import. The option is available in the off-line mode only.

Database export – click on this option to export the PBX database into an xml file. The option is available in the off-line mode only.

Help – select this option to start the help in the chosen language.

Figure: View of Configuration Tool Main Menu

Figure above also includes all configuration menu icons. Icon meanings from the left:

Logout PBX – use this icon to logout the configuration tool from the PBX and return to the previous menu for another connection as described above.

Connect/Disconnect – use these icons off-line to connect/disconnect the configuration tool to/from the PBX.

Save changes – use this icon to save all changes made since the last save.

Undo changes – use this icon to cancel all changes made since the last save in a menu.

Language – flags are used to mark the configuration tool language versions.

Windows

On the left-hand side of the configuration tool you can find the TreeView where you can choose a menu item to be configured. The selected menu then opens on the right-hand side and is mostly divided into two subwindows; one for selecting and the other for configuring an object. The configuration is divided into tags for easier orientation. All the above mentioned windows are shown in the figure below.

15

2N NetStar Admin manual User Manual

Figure: View of Configuration Tool Tags and Windows

The Trace and Database sections situated in the lower part of the screen above the status bar are important configuration tool components. Trace helps you monitor calls and analyse configuration errors if any. Database provides a direct view of the data stored (depending on the connection mode). We strongly recommend that you should not change the data in this view if you do not know how! This menu tag is governed by the read & write rights assigned to each login.

Status bar

The status bar is a lower task bar in the configuration tool. It provides two important pieces of information. The first one is the connection mode, which is either on-line or off-line. The other is the connected PBX name, which includes the PBX and connection data separated with a dash.

Figure: View of Configuration Tool Status Bar

16

1.5 PBX Activation

What you need

To activate and configure 2N® NetStar you need the 2N® NetStar system, a computer running the supported Windows version, a keyboard and a mouse. The PC and 2N® NetStar PBX have to be interconnected in a LAN. Furthermore, it is necessary to display the redirected standard PBX input and output on your PC console. To do this, you need a six–wire, crossed cable with a six-pin RJ-12 connector on one end and a serial connector on the other. This cable is supplied as standard equipment. You can use a 'Tera Term Pro' console or any other functional console. You can also work in the HyperTerminal mode, but longer lines are interlaced.

Step 1: IP address setting

Prior to starting configuration you need to set up the PBX IP address to establish network communication between the system and the computer. To do this, you can use a serial console or the default IP address 192.168.100.100. The 2N® NetStar – PC communication can be on-line or off-line. To configure the console use the table below.

Speed

115200

Bits

8

Parity

None

Stop bits

1

Flow control

None

If necessary, a serial port or modem may be used for PBX connection through the configuration tool, yet at a considerably lower bit rate.

17

Step 2: Hardware activation

After the first connection to the selected PBX according to the Connection to PBX chapter, a configuration wizard is displayed as shown in figure below. This wizard is displayed only if the PBX has a new empty database (has not been preconfigured according to your demands).

18

Figure: View of Hardware Configuration Wizard Dialogue

If the wizard is displayed, you can define the basic configuration settings of the virtual BRI ports. If you are not sure, you can push the Next button to proceed to the next configuration step because these settings may be changed any time later. Once you do that, the configuration tool (together with the PBX) starts to detect the hardware as shown in figure below.

19

Figure: View of Wizard's Hardware Detection Operations

The boards are detected both in the basic unit and extenders. Once some hardware is detected, activation takes place, which means that virtual ports are assigned to all the boards detected (except for VoIP boards). The terminals connected are detected in the last stage of the wizard hardware configuration. This should make the PBX ready for further configuration, which is signalled by green board LEDs. The GSM board is the only board without LED indicators and so its ready status is signalled by the port LEDs. The current firmware version is loaded into the PBX after the first start–up or every firmware upgrade and may cause a short delay in the GSM board activation.

Step 3: Localisation setting

Localisation setting is another important step of the 2N® NetStar configuration. In this step you can define the parameters shown in figure below and described in detail in the 6.3 Localisation chapter. In addition, you can add a language package of your own including texts and progress tones. Two language packages – Czech and English – are available in the PBX by default.

20

Figure: View of Wizard's Localisation Setting Operations

Step 4: Time setting

In this step, the wizard helps you set time, date and time zone. And also define the NTP server for automatic time synchronisation.

21

Figure: View of Configuration Wizard's Time Setting

Step 5: PBX function selection

In this step, choose one of the PBX modes. The setting is not final, it just defines the wizard's next configuration steps. The following options are available:

Private branch exchange

Virtual branch exchange

GSM gateway

Hotel

The offer of settings depends on the PBX mode selected. The lowest number of settings are available in the GSM gateway, where some steps are omitted and configuration starts as late as the SMTP. The settings are identical for the other modes except for step 1, which is always adapted to the particular version. The following steps are available in the Private branch exchange.

22

Step 6: Creation of groups, users and extensions

In this step, the configuration wizard enables an automatic creation of a group and its users and extensions. There are three types of extensions to be generated – analog, SIP and Cornet extensions. Analog extensions are used for the ASL virtual ports. SIP extensions are used for connecting SIP–supporting VoIP terminals and are assigned to the SIP proxy terminals. Cornet extensions are used for the StarPoint key (system) phones connected to the Cornet virtual ports. You can define the first extension number and count of extensions for each group (every other extension has a number increased by one). The extensions are then assigned to ports according to their types (if possible).

If you do not want to create extensions automatically, you can import the company structure from a pre–prepared file in the xml or csv format. In this way you can create a relatively complex company structure including user logins and multiple user extensions.

Three functions are added to this section, the first two of which are used for re–launching of the wizard.

Add new and remove deleted – The existing structure of extensions is compared with the selected file. New extensions are added and those which are present in the PBX yet undefined in the file are removed.

Add new only – The existing structure of extensions is compared with the selected file and new extensions are added only. Undefined extensions are retained in the configuration.

Assign ports randomly–– select this item to enable random assignment of extensions to ports.

If you neither want to automatically create extensions nor to import the company structure, you can push the Next button and select Don't create anything to proceed to the next step.

23

Figure: View of Wizard's Extension Creation or Intra–Plant Structure Import

Step 7: Settings for Assistant

This configuration step includes just two functions with the following meanings:

Launch web server – this item launches the internal PBX web server, to which you can log in by entering the CPU IP address from your web browser. Generate default logins – this item generates logins for the users created in the preceding step. With them, you can log in to the web server as a user.

Step 8: SIP domain setting

This step helps you define a specific SIP domain. If this option is not selected, the CPU IP address is used as the domain.

Step 9: SMTP setting

Within this step you can define the SMTP server to be used by the PBX. Port 25 and the CPU Ethernet interface are set automatically for the SMTP. No security is used by default.

24

Step 10: Creation of routers

The wizard's last step is creating PBX routers. Routers are used for call/SMS routing from one PBX port to another. The wizard offers several default sets of routers, which are sufficient for your basic call routing. For special routing demands, reconfigure the routers and add new ones. All new routers are automatically filled with services, extensions and users and linked with each other.

Step 11: Data saving

Changes are not automatically stored into the PBX during the Wizard process. To save the changes, use the Ctrl+S shortcut or the Save button after completing the Wizard. To cancel all new settings, push the Undo button.

25

2. Hardware

Here is what you can find in this chapter:

2.1

Basic

2.2

Boards

2.3

Synchronisation

2.4

Board and Port List

26

2.1 Basic

Service mode

The section helps you put the PBX in the service mode and back if necessary. The service mode is used for quick changes such as card replacement. The PBX start is much faster after the service mode than after the PBX power off.

OFF – a normal PBX running status. To reuse the PBX while in the service mode, select OFF and save the changes. Having returned from the service mode successfully, you can see in the section Detected rack in the column Status the state RUN.

ON – the PBX service mode. To switch the PBX into the service mode while it is in a normal running status, select ON and save the changes. Having transferred into the service mode successfully, you can see in the section

Detected rack in the column Status the state STOP.

Detected rack

The detected rack table gives you a clear overview of all parts of your PBX.

MAC address – MAC address of the detected rack.

Serial number – serial number of the detected CPU card.

State – current rack state. This may differ from the CPU card state (e.g. the CPU is ON while the rack if OFF in the service mode).

RUN – normal rack operation. The power supply is connected to the cards.

STOP – the rack is stopped. The power supply is disconnected from the cards. Typical for the service mode.

ERROR_LICENCE_EXPIRED – the rack is running, but the trial licence or time-limited main licence has expired. A new licence has to be requested.

1:Basic – indicates the basic unit state.

PRESENT – the basic unit is detected.

MISSING – the basic unit is not detected.

2-5:Extender – displays the extender state.

PRESENT – the extender is detected.

MISSING – the extender is not detected. Check the power supply connection and the switch card - extender CPU interconnection.

Hardware profile

To set the hardware profiles and improve your system efficiency use the HW – HW profiles menu. The menu contains five different hardware profiles. For their benefits and disadvantages see the table below.

Each VoIP card allocates 32 channels in hardware profile 0 and 64 channels in all the other profiles. The PRI card always allocates 32 bus channels.

HW profile number – since different hardware profiles use different bus frequencies, the new configuration saving system is switched into the service mode and back automatically to bring the bus frequency changes into effect. The bus clock can be 2, 4 or 8 MHz, which corresponds to 32, 64 nebo 128 extender channels respectively. The count of extender channels available for calls is always lower by 4 as one channel is normally occupied by signalling.

27

Profiles

0

1

2

3

4

5

6

7

8

Extenders

4

0

4

4

4

0

4

4

4

Extender channels

128

0

32

64

128

0

32

64

128

Trunk positions

128

256

224

192

128

224

192

160

96

Main case case – digital

128

64

64

64

64

64

64

64

64

Main case – analog

32

32

32

32

32

64

64

64

64

Detectors

32

64

64

64

64

64

64

64

64

Players

32

64

64

64

64

64

64

64

64

Table: Benefits and Disadvantages of Hardware Profiles

28

2.2 Boards

Arrangement of HW

Unfolding the HW – Rack menu you can see the rack fitting as shown in the figure below.

Figure: View of PBX Basic Unit Panel

Push the buttons on the left-hand side of the PBX to switch between the basic unit and extender views. Click on the right-hand mouse button in the basic unit or extender view to display the following options:

Add board – click on an empty (no-board) PBX position to use this option. Add a board that has been detected by the PBX (using the Detected option) or a board from the list of supported boards for this position.

Remove board – use this option to remove a selected board. If virtual ports or resources have been assigned to the board, you will be asked whether they should be removed or retained.

Migrate virtual port/resource – use only if the context menu has been displayed on a port to initiate a virtual port substitution dialogue.

Synchronise with detected – use this option to synchronise the current unit or extender with the detected PBX boards. Before a board is removed from the current configuration, you are asked to confirm the removal.

Expert menu – use this option to access the advanced unit, board or port configuration functions. For details see later.

Let us explain the terms "virtual port" and "physical port" and their difference for convenience. Basically, a virtual port is used for software setting of basic properties of a physical port. The advantage of this approach is the fact that the defined set of properties is attributed to a physical port only if the virtual port is assigned to it. Thus, you can esily move virtual ports between physical ports and change their functions as necessary.

Expert menu – Virtual port

Assign virtual port/resource – use this option to assign an existing virtual port to a physical port. Select a virtual port from the list of existing ports.

Create virtual port/resource – use this option only for physical ports without any assigned virtual port. The new virtual port is automatically assigned to this physical port.

Remove virtual port/resource – use this option to remove a virtual port

29

from a selected physical port without deleting it. This virtual port can be used later including all settings (routing, assigned extensions, etc.). Rename the virtual port from XXX to UnassignedXXX.

Delete virtual port/resource – use this option to remove and delete a virtual port once forever. You will not be able to use this port any more.

Regenerate name – use this option to rename a selected virtual port according to its physical port.

Expert menu – Board and Case

Create virtual ports/resources – use this option to create virtual ports (resources) for all of those physical board or unit ports at once that have not been assigned a virtual port.

Remove virtual ports/resources – use this option to remove all virtual board or unit ports at once without deleting them. These ports can be used later including their settings. Rename these virtual ports from XXX to UnassignedXXX.

Delete virtual ports/resources – use this option to delete all virtual board or unit ports once forever. You will not be able to use this port any longer.

Regenerate unchanged names – use this option to change all unchanged names of the virtual board or unit ports according to their physical ports.

Regenerate all names – use this option to change the names of all virtual board or unit ports according to their physical ports.

Board

The figure below shows all possible signalling statuses on the board ports.

Figure: View of Available Analog Board Signalling Statuses

Earphone

Cross

Green – signals a physical port with an assigned virtual port.

Yellow – signals a physical port with an assigned virtual port and active call (or call establishment).

Green – signals a physical port with an assigned virtual port and assigned extension.

Yellow – signals a physical port with an assigned virtual port, assigned extension and active call (or call establishment).

30

Exclamation mark

Yellow – signals a physical port without any assigned virtual port or physical port without detected status.

Red – signals a hardware error, e.g. a low signal level for a GSM, GSM port without SIM card, ISDN virtual port with deactivated L1 or L2 (adjustable), etc.

PBX HW configuration print

The buttons to the right of the basic unit/extender figure help you print out the current PBX hardware configuration. Click on one of the buttons to display the print setting options. Click on Print to display the preview and on the button in the left-hand upper corner to print out the configuration. The buttons in the right-hand upper corner display the extender configuration previews.

Print current view – print the view selected using the buttons to the left of the CPU board (basic unit or extender).

Print all – print the basic unit and extender configurations.

Boards

A two-part Boards tag is available under the PBX view. The upper part shows basic information on the selected board. The parameters mean the following:

Position – gives the board position number in the case as described below.

Type – gives the type of the board to be configured.

Enabled – disables the selected board. This option is useful, for example, while changing SIM cards without switching off the PBX.

State – provides the current board status including information on a mismatch of the board to be configured with the detected one.

Detected – shows the parameters of the board detected.

Type – type of the board detected on a selected position.

Serial number – serial number of the board detected on a selected position.

MAC address – MAC address of the board detected on a selected position.

A window showing the list of physical ports of the selected board is displayed under the above-mentioned part. The meaning of each list column is explained in the 2.4 Board and Port List chapter.

Tab Virtual port

The Virtual port tag helps you configure your virtual ports easily. You can set all parameters of the selected virtual ports and simultaneously see the panel layout. Use the Virtual port tag for an easy configuration of virtual ports. The tag includes all configuration settings for the selected virtual port while keeping the PBX view. Click on a card or its port to display the port assignment to a virtual port type in the left section of the screen. Use the drag&drop function to move a virtual port to another type. If you select the CPU card, all the virtual ports that use the card's LAN interface are displayed. Thus, you will see the SIP Proxy and SIP Gateway virtual ports as well as the SMTP and SMTPD virtual ports.

For details on the setting options associated with the parameters in the right-hand section of the tag refer to the User Manual chapters dedicated to particular virtual ports (especially 3. Virtual Ports).

31

Addressing

The position of each board is specified in the R : C : B format and the position of a port in the R : C : B : P format. The characters have the following meanings:

R – rack number;

C – rack unit number;

B – unit board number;

P – board port number.

Currently, R takes up the value of 0 and C ranges from 1 to 5, the basic unit being 1, the first extender 2 and so on up to the fourth extender with number 5. The board positions (B) in the basic unit are numbered 1 to 14 from the left. The extender positions are numbered similarly, from 1 to 12. The first basic unit and extender position is always reserved for the CPU board. The 1x/2x/4x ISDN PRI (with or without Zarlink) or Surf Ethernet boards can be mounted into positions 0:1:2 to 0:1:4 only. The position 0:1:5 is reserved for the Switch board, which contains the digital switching array.

32

2.3 Synchronisation

Upon connection to a public or private ISDN network, remember to configure one port for synchronisation at least. The PBX works in two modes at the same time: as a source of synchronisation (Master) and a device that receives synchronisation (Slave). There are two fields in the HW – Synchronisation menu. The left-hand one contains all digital virtual ports that can be selected for synchronisation, i.e. all PRI and BRI virtual ports in the TE mode. The other field contains a list of virtual ports that have been selected for synchronisation. All ports in the NT mode can be used as synchronisation sources.

Figure: View of Synchronisation Port Assigning and Priorities

Use the Up and Down buttons to move the selected synchronisation up or down for a higher or lower synchronisation priority respectively – the port listed first has the highest priority (255). Every other carrier has a priority lower by 1 (254, 253, ..). A newly assigned carrier is always placed last (the lowest priority). In the case of synchronisation loss, the following port in the list (with a lower priority) is selected automatically. Upon synchronisation restoration, the PBX returns automatically to the port with the highest priority.

Push the Right and Left buttons to transfer the virtual ports from one field to another and thus ensure the PBX synchronisation.

33

2.4 Board and Port List

The Hardware – Board list menu contains a list of boards that are physically present in the PBX. The board list has four columns with the following meanings:

Address – shows the physical board address within the PBX according to the Boards chapter.

Type – shows the board type.

Serial number – shows the factory-programmed board serial number.

MAC address – shows the board MAC address.

Module IMEI – shows IMEI of GSM module.

Virtual port – shows the complete name of the carrier or resource assigned to a physical port.

Stack – shows the general carrier / protocol stack (DSS1, ASL, CO, etc.).

Extension – shows the list of extensions assigned to a physical port carrier.

User – shows the users of extensions assigned to a physical port.

State – shows the current port state. Description – provides associated information.

The context menu under the right button offers the following two options:

Export to CSV – use this option to export the whole table into a *.CSV file. You can use this export for stocktaking purposes and/or for contacting the 2N® TELEKOMUNIKACE Technical Support if necessary.

Move to port – use this option to move quickly to the configuration of the virtual port on the selected row.

34

3. Virtual Ports

Here is what you can find in this chapter:

3.1 BRI and PRI

3.2 Cornet

3.3 ASL

3.4 CO

3.5 GSM

3.6 SIP

3.7 SMTP

3.8 Virtual Port Options

35

3.1 BRI and PRI

BRI

Refer to the Boards section for the meaning of the virtual port.

BRI virtual ports are assigned to physical ISDN ports for the Basic Rate Interface. For the hardware configuration of BRI virtual ports refer to the Virtual ports – BRI/PRI menu in the Stack tag. A list of all BRI virtual ports is displayed on the left and a window for the port parameter setting is available on the right. The configuration parameters are divided into logical parts.

Stack status

This field displays information on the stack and its current status including information on the L1 or L2 states, higher error rates or loss of synchronisation.

Digital interface parameters

Interface type – cannot be selected, only shows the type of interface including bit rate information.

Interface mode – use this parameter to switch between the NT (Network Termination) and TE (Terminal Equipment) modes. Some basic unit positions can only be used in the NT mode. Specifically, they are basic unit board positions 6, 9 and 12 if you follow addressing as described in Boards. A correct function requires a software–hardware matching and a proper jumper setting for each board port. Figure below may serve as a guide.

Do not remove the board from the PBX without prior PBX switching off or into the service mode to avoid the PBX damage.

Bus mode – use this parameter to switch between the MPT (point–to–multipoint) and PTP (point–to–point) modes. In the MPT mode you can connect up to eight terminals to one physical port. The PTP mode is mainly used for cross–connecting lines (trunks) between PBXs or for one terminal connection.

Enabled channels – use the checkboxes to activate the B–channels. If no channel is checked off, you cannot use this port for communication (it behaves as if busy).

Deactivate L1 at relax – use this parameter to deactivate the L1 layer on an inactive interface. The PBX automatically deactivates the layer after a timeout as defined in the Deactivation timeout item. Any incoming call automatically reactivates this layer.

Keep L1 active – check this option to make the PBX keep L1 active on this interface without any incoming call. This option cannot be combined with the

Deactivate L1 at relax option.

Inactive L1 as error – use this option to activate a caution about the first layer being inactive. This is indicated by a red exclamation mark on the port in the Hardware – Boards menu and a red text in the upper stack status field. This option may not combined with the Deactivate L1 at relax option.

Set SLIP – select Nonsynchronous as error to enable acceptable SLIP range parameters. Use this option in the TE mode only. If the SLIP rate gets over the

36

upper level, a red exclamation mark appears on the port in the Hardware – Boards menu and a red text is displayed in the upper stack status field. This error status gets changed after the SLIP rate falls below the lower level. The interval between these two values represents hysteresis.

Settings for BER – select BER as error to enable acceptable interface error parameters. If the BER rate gets over the upper level, a red exclamation mark appears on the port in the Hardware – Boards menu and a red text is displayed in the upper stack status field. This error status gets changed after the BER value falls below the lower level. The interval between these two values represents hysteresis. The BER values are entered in an exponential format (e.g. 3e–5 means 3 errors in 100,000 bits). In practice, the BER may occur on a virtual port close after the cable connection. In that case, this is not an error if the BER disappears in a few minutes.

Figure: View of ISDN BRI Board Jumper Configuration (The thick line represents the board front)

Specific interface parameters

Multiframe – is the first layer parameter of the So bus. For details refer to recommendation I.430.

Extended bus – use this parameter to activate an extended bus. With just one terminal and proper terminating impedance you can extend the PBX–terminal distance up to 1,000 metres. This parameter can be set for an NT port only.

Priority 10 – is the first layer parameter of the So bus. This parameter can be set for a TE port only.

37

DSS1 protocol parameters

Reverse NT/TE mode – this option refers to L3 signalling only. Check this option to make a TE port behave as an NT port (and vice versa).

Do not send time at NT – use this option to disable sending of the connection date and time information within the CONNECT message from an NT port to a TE port. Available for NT ports only.

Ignore unset explicit channel – use this option to enable call establishment without an explicitly set B–channel.

Always select B–channel – use this option to disable sending the channel identification information within the SETUP message together with channel signalling. Available for TE ports only.

Disconnect L2 if there is no call – use this option to disconnect the L2 layer on a inactive interface. The PBX automatically disconnects the layer after a timeout. An incoming call automatically reconnects the layer.

Keep L2 connected – check this option to make the PBX to keep L2 connected on this interface without any incoming call. This option may not be combined with the Disconnect L2 if no call option.

Disconnected L2 as error – use this option to activate a caution about the second layer being disconnected. This fact is indicated by a red exclamation mark on the port in the Hardware – Boards menu and a red text in the upper stack status field. This option may not be combined with the Disconnect L2 if no call option.

Terminals – is active for virtual MPT NT ports. Enter all connected ISDN terminals including their MSN numbers. Assign a extension to these terminals using the Extensions tag. The terminal shall then identify itself as the selected extension within the PBX.

2N® NetStar is able to process (i.e. resend to an interface other than ISDN) only G.711 A-law encoded calls on the ISDN interface. Calls encoded by G.711 µ-law can only be resent between the ISDN interfaces in the PBX.

Digital interface diagnostic

Line state – the parameter cannot be set. It only shows the state of the first interface layer.

Number of SLIPs per minute – this parameter gives the count of slips. A slip is caused by different clocks of the PBX and the active terminal. This value is updated every 6 seconds and represents a weighted average per minute.

Bit error rate per second – the BER parameter gives a count of incorrectly transferred bits during transmission. The value is updated every 6 seconds and represents a weighted average per minute.

If the SNMP port supervision is used, enable some or all of the following parameters:

Inactive L1 as error, Disconnected L2 as error, Nonsynchronous L1 as error,

BER as error. If not, the port error will not be detected and the PBX will be unable to send a warning.

38

Tab Expert

Cause mapping – is an additional function for modification of outgoing causes for a selected virtual port. It may be useful while adapting NetStar causes to the specific conditions of your network. You can choose a particular internal NetStar cause in the left–hand column and assign a cause to it to be sent to your network in the right–hand column.

PRI

Refer to the Boards section for the meaning of the virtual port.

PRI virtual ports are assigned to physical ISDN ports for the Primary Rate Interface. For the hardware configuration of the PRI virtual ports refer to the Virtual ports – BRI/PRI menu in the Stack tag. A list of all available PRI virtual ports is displayed on the left and a window for the port parameter settings is on the right. The configuration parameters are divided into logical parts.

Stack status

This field displays information on the stack and its current status including information on the L1 or L2 states, higher error rates or loss of synchronisation.

Digital interface parameters

Interface type – the parameter cannot be configured. It only shows the type of interface including bit rate information.

Interface mode – use this parameter to switch between the NT (Network Termination) and TE (Terminal Equipment) modes. A correct function requires a software–hardware matching and a proper jumper setting for each ISDN board port. Figure below may serve as a guide.

Do not remove the board from the PBX without prior PBX switching off or into the service mode to avoid the PBX damage.

Enabled channels – use the checkboxes to activate the B–channels. If no channel is checked off, you cannot use this port for communication or data transmission (it behaves as if busy). B–channels 0 and 16 cannot be used for call or data transmission under normal circumstances since they are blank. In PCMs of the 1st order are used for frame synchronisation and signalling transmission.

Deactivate L1 at relax – use this parameter to deactivate the L1 layer on an inactive interface. The PBX automatically deactivates the layer after a timeout as defined in the Deactivation timeout item. Any incoming call automatically reactivates this layer.

Keep L1 active – check this option to make the PBX keep L1 active on this interface without any incoming call. This option cannot be combined with the

Deactivate L1 at relax option.

Inactive L1 as error – use this option to activate a caution about the first layer being inactive. This is indicated by a red exclamation mark on the port in the Hardware – Boards menu and a red text in the upper stack status field. This option may not combined with the Deactivate L1 at relax option.

Settings for SLIP – select Nonsynchronous as error to enable acceptable

39

SLIP range parameters. Use this option in the TE mode only. If the SLIP rate gets over the upper level, a red exclamation mark appears on the port in the Hardware – Boards menu and a red text is displayed in the upper stack status field. This error status gets changed after the SLIP rate falls below the lower level. The interval between these two values represents hysteresis.

Settings for BER – select BER as error to enable acceptable BER range parameters. If the BER rate gets over the upper level, a red exclamation mark appears on the port in the Hardware – Boards menu and a red text is displayed in the upper stack status field. This error status gets changed after the BER rate value falls below the lower level. The interval between these two values represents hysteresis. The BER values are entered in an exponential format (e.g. 3e–5 means 3 errors in 100,000 bits). In practice, the BER may occur on a virtual port close after the cable connection. In that case, this is not an error if the BER disappears in a few minutes.

Figure: View of ISDN PRI Board Jumper Configuration (The thick line represents the board front)

Specific interface parameters

Prefer CRC – use this option to enable preferring communication with the Cyclic Redundancy Check. In this mode, the PBX tries to establish connection with the CRC at first and, having failed, attempts to establish connection without the CRC. Long haul – use this parameter to activate an extended bus called the Long Haul. With just one terminal and holding impedance, you can extend the distance up to 1,000 metres. This parameter can be set only on an NT port.

40

DSS1 protocol parameters

Reverse mode NT/TE – this option refers to L3 signalling only. Check this option to make a TE port behave as an NT port (and vice versa).

Do not send time at NT – use this option to disable sending of the connection date and time information within the CONNECT message from an NT port to a TE port. Available for NT ports only.

Ignore unset explicit channel – use this option to enable call establishment without an explicitly set B–channel.

Always select B–channel – use this option to disable sending the Channel identification information within the SETUP message with channel signalling. Available for TE ports only.

Disconnect L2 if no call – use to disconnect the L2 layer on an inactive interface. The PBX automatically disconnects the layer after a timeout. An incoming call automatically reconnects the layer.

Keep L2 connected – check this option to make the PBX keep the L2 layer connected on this interface without any incoming call. This option may not be combined with the Disconnect L2 if no call option.

Disconnected L2 as error – use this option to activate a caution about the second layer being disconnected. This fact is indicated by a red exclamation mark on the port in the Hardware – Boards menu and a red text in the upper stack status field. This option may not be combined with the Disconnect L2 if no call option.

Terminals – not applied for PRI ports.

2N® NetStar is able to process (i.e. resend to an interface other than ISDN) only G.711 A-law encoded calls on the ISDN interface. Calls encoded by G.711 µ-law can only be resent between the ISDN interfaces in the PBX.

Digital interface diagnostic

Line state – the parameter cannot be set. It only shows the state of the first interface layer.

Number of SLIPs per minute – this parameter gives the count of slips. A slip is caused by different clocks of the PBX and the active terminal. This value is updated every 6 seconds and represents a weighted average per minute.

Bit error rate per second – the BER parameter gives a count of incorrectly transferred bits during transmission. The value is updated every 6 seconds and represents a weighted average per minute.

If the SNMP port supervision is used, enable some or all of the following parameters:

Inactive L1 as error, Disconnected L2 as error, Nonsynchronous L1 as error,

BER as error. If not, the port error will not be detected and the PBX will be unable to send a warning.

41

Expert tab

Cause mapping – is an additional function for modification of outgoing causes for a selected virtual port. It may be useful while adapting NetStar causes to the specific conditions of your network. You can choose a particular internal NetStar cause in the left–hand column and assign a cause to it to be sent to your network in the right–hand column.

42

3.2 Cornet

Cornet is a digital virtual port for the StarPoint key phones with proprietary signalling (UPN interface). The Stack tag provides limited configuration capacities only. The parameters are divided into logical sections according to their respective functions. For the StarPoint configuration parameters refer to the Softphone subtag of the Properties tag. For more details on Softphone extensions refer to Chapter Setting Properties.

Virtual port status

The upper menu field displays information on the stack type and its current status including information on the L1 and L2 states, increased bit error rate or nonsynchronous L1.

Digital interface parameters

Interface type – the parameter cannot be configured. It only shows the type of interface.

Interface mode – this parameter is set to NT and cannot be reconfigured. Thus, cross–connecting lines cannot be made using these ports.

Bus mode – this parameter is always set to PTP and cannot be reconfigured. This port is used for one terminal only.

Enabled channels – use this parameter to enable selected interface channels. If none is enabled, the interface cannot be used and behaves as if it was busy.

Keep L1 active – check this option to make the PBX keep the interface active automatically.

Inactive L1 as error – use this option to activate a caution about the first layer being inactive. This is indicated by a red exclamation mark on the port in the Hardware – Boards menu and a red text in the upper stack status field.

Set BER – select BER as error to enable acceptable BER range parameters. If the BER rate gets over the BER error level, a red exclamation mark appears on the port in the Hardware – Boards menu and a red text is displayed in the port status field. This error status gets changed after the BER value falls below the BER OK level. The interval between these two values represents hysteresis. The BER values are entered in an exponential format (e.g. 3e–5 means 3 errors in 100,000 bits).

Master terminal

Type – shows the type of the StarPoint terminal connected.

Firmware – shows the current firmware version of the terminal connected. Extenders – shows information on the active extenders of the terminal connected.

Slave terminal

Type – shows the type of the StarPoint terminal connected.

Firmware – shows the current firmware version of the terminal connected. Extenders – shows information on the active extenders of the terminal connected.

43

Digital interface diagnostic

Line state – the parameter cannot be configured. It only shows the state of the first interface layer.

Number of SLIPs per minute – shows the count of SLIPs. A SLIP is caused by different clocks on the PBX and the terminal. This value is updated every 6 seconds and represents a weighted average per minute.

BER per second – the Bit Error Rate shows the count of incorrectly transferred bits on the interface during transmission. The value is updated every 6 seconds and represents a weighted average per minute.

Supported terminals

44

3.3 ASL

The ASL virtual port is used for connecting common analogue telephones or fax machines. This virtual port enables DTMF and pulse dialling detection and as well as DTMF or FSK using CLIP transmission. The parameters are divided into logical sections.

Stack status

This field displays information on the stack and its current status. With an ASL virtual port you can see the following statuses:

null

config

on_hook

off_hook

error_stop error_start_req

Figure: View of ASL Virtual Port Hardware Configuration

Line parameters

Impedance – this parameter determines the impedance of the hybrid circuit according to preset models (User, ETSI 600, Germany and Real 600).

Line model – this parameter provides further hybrid circuit parameters according to preset models EIA0 to EIA7 (e.g. EIA0 represents a 100m long line model).

Signalling type – shows the type of active state signalling. Choose from

Reverse polarity, Tariff pulse or Simple.

Tariff pulse type – defines the tariff pulse sending source. Select 12 kHz, 16 kHz or none.

45

Incoming parameters (phone is dialling)

Call type – determines the preferred type of communication on this port. Choose one of the Voice, FAX, A3.1kHz Audio and 56kb Modem options.

DTMF dial enabled – check this item to make the carrier detect DTMF dialling from an analogue phone.

Pulse dial enabled – check this item to make the carrier detect pulse dialling from an analogue phone.

FLASH length [ms] – the parameter sets the maximum time of the FLASH signal transmitted from a local phone to the PBX. The default value is 150 ms and the minimum value is 80 ms.

Disable port DTMF detection – use this parameter to disable/enable DTMF detection using a detector on the board in order to save the internal PBX detectors.

Outgoing parameters (phone is ringing)

CLI broadcasting mode – the parameter defines the preferred CLIP (Calling Line Identification Presentation) transmission type. The selections are DTMF,

FSK and none.

46

3.4 CO

The CO virtual port is an analogue virtual port for connection of a CO (central exchange) analogue line. Since it has only a DTMF transmitter, it is unable to detect the DTMF. Therefore, route an incoming call directly to the final destination, or assign the DISA function to the virtual port to detect the DTMF symbols and route the call to the required destination. The parameters are divided into logical sections.

Basic

Stack status

This field displays information on the stack and its current status. With a CO virtual port you can see the following statuses:

null

config

on_hook

off_hook

error_stop error_start_req

Figure: View of CO Virtual Port Hardware Configuration

47

Line parameters

Impedance – determines the impedance of the hybrid coil according to preset models (User, ETSI 600, Germany and Real 600).

Line model – determines further hybrid coil parameters according to preset models EIA0 to EIA7 (e.g. EIA0 represents a 100m long line model).

Signalling type – shows the type of active state signalling. Choose one of the

Reverse polarity, Tariff pulse or Simple options.

Tariff pulse type – defines the tariff pulse sending source. Choose 12 kHz, 16 kHz or none.

Dial tone –

Congestion tone – this setting becomes available when you tick off the Check congestion tone parameter. Select the congestion tone mask for testing purposes.

Check congestion tone – tick off the option to check the presence of the congestion tone. If the congestion tone is detected, the virtual port will pass into the On-hook mode.

Outbound way parameters (from PBX)

Current detection timeout [ms] – here set the time for current detection on the picked-up carrier. If no current is detected within this timeout, a failure is reported.

Dial tone timeout [ms] – here set the waiting time for dialling numbers to the carrier. Select the Check dial tone option to test the dial tone presence during this time.

Dial to connect timeout [ms] – here set the maximum delay time for CO line dialling. Time monitoring is renewed after every digit entered. If no digit is detected within this timeout, the connection will be regarded as terminated and a new connection attempt will be made.

Check dial tone – select this option to enable dial tone testing on the carrier for a period of time set in the Dial tone wait timeout parameter.

DTMF dial enabled – tick off the option to enable DTMF dialling for the virtual port

Pulse dial enabled – tick off the option to enable pulse dialling for the virtual port

FLASH length [ms] – here set the maximum time of the FLASH transmitted from a local phone to the PBX. The default value is 150 ms and the minimum value is 80 ms.

48

Inbound way parameters (to PBX)

Ring pulse time [ms] – this parameter sets the minimum time of the ring signal presence needed for ring detection. If the ring time is shorter than the preset value, ringing will be ignored.

Ring pulse treshold [V] – this parameter sets the minimum ring voltage level needed for ring detection. If the ring voltage level is lower than the preset value, ringing will be ignored.

Ring pattern time [ms] – this parameter sets the minimum period of time for alerting detection.

CLI reception mode – the parameter defines the preferred CLIP (Calling Line Identification Presentation) reception type. Choose DTMF, FSK or none.

CLI reception timeout [ms] – the parameter sets the CLI detection timeout as counted from the end of the first ring. This option is active only if the DTMF or FSK reception mode has been selected.

Polarity timeout [ms] – the parameter sets the reverse polarity timeout. This option is active only if the Reverse polarity item has been selected for this virtual port.

Call reject timeout [ms] – if the PBX needs to reject an incoming CO call, it has to pick up and hang up. Use this parameter to define the timeout for this action. If the action is too short, the other party will not recognise termination.

Expert

Chipset

Chipset Type – this parameters determines the type of the chipset used. The SILABS_SI350 chipset is only supported at present.

Chipset Config – activates one of the chipset configurations created.

New config – helps create a new configuration for the selected chipset type.

Specific Chipset Config

Name – sets the chipset type whose configuration is being set in the section.

Do not change the above mentioned parameters unless absolutely necessary.

DCTerm – sets the DC termination parameters (ringing voltage, minimum current, impedance). Hexadecimal values are used.

DAA Ctrl 5 – sets further parameters for analogue line matching (on/off-hook rate, low pass filter). Hexadecimal values are used.

ACIM – helps set the proper impedance. Hexadecimal values are used.

Tx Gain – sets the transmit gain. Rx Gain – sets the receive gain.

Refer to pages 78 to 81 of the User Manual for more details on the parameters.

The table below includes the ACIM settings including meanings.

49

ACIM

Set

AC termination

[3:0]

 

 

 

0000

00

600

Ohm

0001

01

900

Ohm

0010

02

270

Ohm + (750 Ohm || 150 nF) and 275 Ohm + (780 Ohm ||

150 nF)

 

 

0011

03

220

Ohm + (820 Ohm || 120 nF) and 220 Ohm + (820 Ohm ||

115 nF)

 

 

0100

04

370

Ohm + (620 Ohm || 310 nF)

0101

05

320

Ohm + (1050 Ohm || 230 nF)

0110

06

370

Ohm + (820 Ohm || 110 nF)

0111

07

275

Ohm + (780 Ohm || 150 nF)

1000

08

120

Ohm + (820 Ohm || 110 nF)

1001

09

350

Ohm + (1000 Ohm || 210 nF)

1010

0A

0 Ohm + (900 Ohm || 30 nF)

1011

0B

600

Ohm + 2.16 µF

1100

0C

900

Ohm + 1 µF

1101

0D

900

Ohm + 2.16 µF

1110

0E

600

Ohm + 1 µF

1111

0F

Global complex impedance

50

+ 232 hidden pages