Question 1

2N Contact Centre Solution installation

Accepted Answer

1) First of all – you need to upgrade your NetStar to version 4.2.0 or higher ( how to upgrade NS find on: How to make a firmware upgrade of 2N NetStar) or use Netstar SW version 1.2.2 or higher. 2) Create User in your NetStar (in section User- Users & Groups). By this User will Contact Centre communicate with NetStar!  We created User: connect. Now we need to create login and password to this user. (In section Users – User rights.)    3) Install the 2N Contact Centre Solution. HW requirements are ( 64b processor, 4GB RAM, 100GB HDD). It can be Virtual macine, Server or PC in the same LAN Network as 2N NetStar is! Software is distributed with Cent Os 6.4 systém – which will be installed as well. If you are going to install Contact Center Solution on the virtual PC you need to enable virtualization (used as the hardware acceleration) on the BIOS. Below all the step of installation are described.   4) Select the first option or just wait. 5) Then the systém will request to select one of the options below.    6) Installation will take approximately 15 minutes. After the installation is complete you will be requested to reboot the system.    7) In Network section it is important setup Bridge Adapter.  8) Eject installation disk from CD-ROM. Enter login and password. By default login is admin, password is 2n. 9) Select language and proceed with settings.    10) Then enter IP address of CCS or its domain name       11) Select network interface for communication with Netstar and users (in the figure there is only one available Ethernet interface)      12) Enter IP address of Netstar      13) Enter TCP port for communication with Netstar, by the dafault it is 6543      14) Enter login/password to connect to Netstar (we have created user the Contact Center user with login - connect and password - connect. After the connection is established you will be requested to press any key.      15) In this menu you can modify basic parameters of CCS      16) Connect to CCS via your web browser (recommended: Mozilla Firefox, Chrome, IE v.10) Use login: superadmin, password: 2n      17) Upload the license which you received from Technical support department and create a company by clicking to “+Add” button      Now your CCS is ready to be configured.

Question 2

2N NetStar - Initial configuration - How to start?

Accepted Answer

In this document you will learn how to set the initial configuration of 2N NetStar. After having read this document you should be able to:  connect to the NetStar via COM port (serial cable is attached to each NetStar delivery)  configure network, time and system service parameters via COM port  set the basic parameters of the NetStar with the help of configuration wizard  explain the basic difference between online and offline database   Connection to the NetStar via COM Each 2N NetStar delivery includes a standard serial cable for the PC – 2N NetStar connection. It is a six-core telephone cable which has RJ11 connector on one side and RS-232 female connector on the other side. For connection from your PC to 2N NetStar you need to use HyperTerminal program or Putty. Set the Serial communication with these parameters:  Transmission speed: 115 200Bd  Data bits: 8  Stop bits: 1  Parity: None  Flow control: None  After connection to the 2N NetStar you have to enter the correct username and password in order to get access to the Main Menu of the configuration interface. The default Administrator settings are as follows:  Username: Admin  Password: 2n   In Main Menu you can see four options for settings and you can also see there the actual firmware version that is loaded in 2NNetStar. It is very important information for you because “Administration tool” which is used for next configuration needs to have the same version as firmware version uploaded in 2N NetStar.  Configuration menu – number "1" in Main Menu If you press number 1 in Main Menu you will go to Configuration menu. In this menu you can set network parameters, bridges and time. In bridges section you can open some ports (e.g. for CTI communication) and in time section you can set the actual time and date.  The most important part of this menu is Network settings. In this section you can set IP address of CPU, network mask and default gateway. You can also choose whether you want to use DHCP or if you set static IP. Default IP address is 192.168.100.100 (see next picture). Next parameters that can be set are DNS servers, host name of 2N NetStar and domain name.    System menu – number "2" in Main Menu If you press number 2 in Main Menu, you will go to System menu. In this menu you can turn the internal web server, telnet server and SSH server on or off. You can also restore factory settings here or reboot the 2N NetStar.     Connection to the NetStar – Administrator tool First of all you have to verify firmware version which is uploaded on NetStar. You can do it easily if you use Putty program for connection to 2N NetStar and on the top left corner you will see the actual firmware version – it is visible in the first picture where there is the actual firmware marked with a red frame. After this you have to install Administrator tool to your PC – you can find this tool on the www.2n.com.  Administration tool – connection parameters When you have successfully installed the tool, you can launch it – you will have an icon on the desktop of your PC if you checked off this option during the installation or you will find it in the folder that you have selected for installation. Now you have to set new connection in Admin tool:  Create new group – see the step 1 in the picture below. Click on the “Create group” icon and select “On the same level”. I have named this group 3.1.10.  Add new PBX to this group – step 2 in the figure below. Click on the “Create PBX” icon and select “To group”. Then enter the name of PBX (in the example is Test_PBX) and click the OK button (step 3).  Fill in the connection parameters – you have to fill in connection name, choose one of the modes option (on-line = only on-line connection to the 2N NetStar, off-line = only off-line configuration of database or both). Next you have to set a method how you want to connect to NetStar:  TCP/IP – you have to set IP address of CPU and IP port  Modem - you have to set phone number  COM port  It is also possible to set timeout between attempts if the connection was unsuccessful or you can preset username and password for this connection.   After this setting you will see your Test_PBX in group 3.1.10 and two connections for this PBX. Make a double click on the “Local – on-line” connection and you will be connected to the 2NNetStar. Hardware installation wizard begins automatically.   Administration tool – hardware installation wizard Now you will be briefly acquainted with the installation wizard and with the most relevant quick start settings. First of all 2N NetStar needs to make hardware detection. In this case you have to set BRI configuration – if there are some BRI cards in the NetStar, ports will be selected by default.  TE = terminal equipment (receives sync from the opposite side)  NT = network termination (gives sync to the opposite side)  PTP = point to point communication  MPT = point to multipoint communication   When you select one of these options, you should click on “Next” button and automatic hardware configuration will be finished (see the picture below).  After finishing the hardware detection, you should press “Next” button and next installation wizard will start. This wizard will guide you through configuration of basic parameters of 2N NetStar for the first start-up. There are 8 sections you will go through and you can see them on the figures below (images are arranged in the same order as in the wizard):  Localization – set the destination where the 2N NetStarwill be deployed. In Advanced settings you can fill in numbers and prefixes that will be used for localization of calling numbers (figure below - part 1)  Time settings – set the actual date and time. You can do it manually or you can synchronize time of NetStar with network time server (NTP server) or you can get time from your computer (figure below - part 2)  Working scheme – select the working scheme in which you want to use 2N NetStar. There are four options:  PBX - classic PBX with SIP, ASL, cornet extensions, mobility extensions, etc.  Virtual PBC - 2N NetStar is e.g. structured for more companies in one building (each company has its own numbering plan, routing, special services, etc.)  GSM gateway - 2N NetStar is set as a basic gateway to GSM network  Hotel    Extensions definition – choose one of the options for extension settings. You can choose automatic extension settings (create a group to which all created extensions will be added and then set the numbers for ASL, SIP and cornet extensions. If you create some SIP extensions then default SIP proxy will be also automatically created). You can also import numbering plan from your PC or you can skip this option and set the extension later in the Administration tool (figure below - part 4)  Assistant settings – if you plan to use Assistant server (web server for users), you can start this server right now from wizard and you can also generate default logins for users – these users were created in the previous step (figure below - part 5)    SIP domain - set the domain name for SIP communication (figure below - part 6). This option is available only if you set some SIP extensions in previous step.  SMTP settings – create the SMTP account for email sending. You can specify server address and also email address for this account (next figure - part 7)   Router settings – choose one of four options for router settings. Each option has different number of routers and also different type of routers. You can also add some more routers to each of these groups (next figure - part 8):  ROUTER_CZ: there are 32 routers which can be configured in order to meet your requirements. You can specify routers for emergency calls, for local calls, for calls to national networks and GSM networks, etc. If you choose this router type, you can specify prefixes for AUTHORIZE_LO and AUTHORIZE_LO+GSM router (figure below - part 9).  ROUTERS_DEFAULT: there are only 6 routers for this option. You can find there Default, Authorize, Internal, PSTN, Services and SMS Services routers.  ROUTERS_BASIC: there are 14 routers in this section. You can find there same routers as was in routers_default plus there are routers for ME, PSTN, SMS in and out, etc.  ROUTERS_SK: there are the same routers as in router_CZ group but there are some more prefixes predefined.        On-line and Off-line database On-line database – it is an actual database saved in 2N NetStar. If you want to make changes in this database, you need to have on-line connection to NetStar (via TCP/IP, COM port or modem). Changes are saved to NetStar after you click on the “Save changes” button on the top menu. Off-line database – this database is saved on your computer and you can find it here:C:\Documents and Settings\Administrator\App Data\2N TELEKOMUNIKACE\Netstar\Tools\PbxX. You can verify the destination folder in properties of PBX (see figure 5 – PBX parameters window). When you connect to the 2N NetStar in off-line mode, the database from this folder will be uploaded – the name of this file is Db.xml. You can make changes in this off-line database without any impact to the 2NNetStar configuration. From off-line database mode you can connect to the NetStar by click on the “Connect” button on the top menu. Then you can select one of three options you have (see the figure below):  Load from PBX – you will load configuration from NetStar to off-line mode (configuration from NetStar will be saved to file Db.xml in you PC).  Save to PBX – you will save your off-line configuration to the NetStar (this configuration will be saved there and will be active!)  Move changes – you will only move changes that have been made in off-line mode to NetStar on-line configuration (you need not save all configuration to NetStar but only the difference between off-line and on-line configuration).

Question 3

2N NetStar SW - How to install and license 2N NetStar SW

Accepted Answer

This FAQ describes how to install 2N® NetStar SW. The 2N® NetStar SW is a virtual PBX that works the same as 2N® NetStar and offers the same 2N® Netstar Admin Tool as the hardware version. It has similar functionalities. With 2N® NetStar SW you can connect Softphones, IP phones or other solution working with SIP protocol.  Mandatory Software and Used ports   For use of 2N® NetStar SW and it's configuration software 2N® SW NetStar Admin Tool you need to have installed and enabled following software  Microsoft Visual C++ 2013 Redistributable (x86)  Microsoft Visual C++ 2015-2019 Redistributable (x86)  .NET Framework 3.5  .NET Framework 4.7        System capacity dependence on used HW    Installation of 2N NetStar SW  It is necessary to install setup+sw_version.exe, that you can download here     Installation of 2N NetStar SW in VirtualBox In VirtualBox it is necessary to add a new virtual PC where will be 2N® NetStar SW installed.The whole process is not shown in pictures below, only mandatory ones as the virtual machine configuration may vary for everyone.    Go to Storage -> Add optical drive  Add the .iso file which is in the installation folder of SW NetStar Admin ToolC:\Program Files (x86)\2N TELEKOMUNIKACE\2N NetStar SW\2N NetStar SW Admin Tool version Software\ISO -> netstar-pbx_version.iso  The .iso file is succesfully added to the virtual machine  Change the Network Adapter so you can connect to your SW NetStarUsually we use setting shown in the picture below, it may vary depending on your network setup.         For the installation use classical option not the graphical one.Choose the localization for you country.  It is necessary to specify IP address, mask and default gateway and name server for 2N NetStar SW. After that press Continue to install 2N NetStar SW.In our example we have used following IP addresses, they may differ depending on your network.  IP Address which will be assigned to the SW NetStar - later used for connection via SW NetStar Admin Tool  Network mask  Network gateway  DNS IP address    With Ping function you can check that 2N NetStar SW is available and working. Default login to NetStar virtual machine is followinglogin: rootpassword: 2n    2N Netstar SW Admin Tool  Rights   If you are setting up NetStar in a restricted environment and possibly on a PC without admin rights. Please check whether you will have an acces to following folders after installation.   C:\Users\username\Documents\2N TELEKOMUNIKACE\Netstar\C:\ProgramData\2N TELEKOMUNIKACE\Netstar\ C:\Program Files (x86)\2N TELEKOMUNIKACE\2N NetStar SW\2N NetStar SW Admin Tool 1.3.1\NsSwAdmin\Xml - Installation folder(it may varry depending on what path you have chosen during installation process)      The 2N NetStar SW Admin Tool has the same interface as the hardware version. To configure 2N® Netstar SW Admin Tool it is necessary to create PBX, configure IP address and connect to the PBX.  Click on Groups -> On the same level -> Name your group  Right click on the Group -> Create PBX -> To groupName the group - hit OK  Name the connectionFill the IP address of SW Netstar virtual machine - we used 192.168.1.78Optionally you can fill the login credentials which in default arelogin: adminpassword: 2n          Licensing  Trial license   Unlike on Hardware version of NetStar the Software one does not have a 800h trial license.   To be able to use and work with a SW Netstar you need to add a license. The license key is based on license ID serial number. You need to order a license based on this ID number as there is not any trial time period. You can program it without a license but the license is mandatory for functionality Connect to 2N Netstar SW Admin tool in online mode! The ID serial number can be found in the section Global Data -> Licenses -> Serial number

Question 4

2N Records Manager installation

Accepted Answer

Requirements: NetStar firmware version 4.2.0 or higher    1. Create User in your NetStar (in section User- Users & Groups):  This user account of Records Manager will communicate with NetStarIn this case, we created user "connect"  Next, create a login and password to this user Section Users – User rights  2. Install the 2N Records Manager. HW requirements are 64bit processor, 2GB RAM, 100GB HDD, processor must support Virtualization technology. It can be Virtual machine, Server or PC in the same LAN Network as 2N NetStar is! Software is distributed with CentOs 6.4 system – which will be installed as well. If you are going to install Records Manager on the virtual PC you need to enable virtualization (used as the hardware acceleration) on the BIOS. Below all the step of installation are described.      3. Select the first option or just wait. 4. Then the system will request to select one of the options below (we recommend option "Use All Space")      5. Installation will take approximately 15 minutes. After the installation is complete you will be requested to reboot the system.      6. Eject installation disk from CD-ROM. Enter login and password. By default login is admin, password is 2n.   7. Select language and proceed with settings.    8. Type hostname. It can be any name    9. Select network interface      10. You can use IP address obtained from DHCP server or configure static    11. To access Records Manager you can use domain name or IP address. If you select domain name as the option, it is also necessary to update your local DNS server with new entry. Domain name must look like records.company.com    12. The wizard will create a storage folder where all the records will be saved. Wizard will request a password to access given directory from Netstar. After you enter the password you will be requested to enter name of folder where all the records will be stored:          13. After you finish system setup there will appear a window with the following options:    14. Now system is set. Run any web browser and type IP address/domain name of installed Records Manager. Default login is superadmin, password is 2n      15. Upload the license file which you got from Technical Support    16. Then add new NetStar to the system and fill in required information and add created folder for storing records   IMPORTANT!  The communication port is always 6543, Sys. user is the user which was created in NetStar in the beginning of this manual.   17. Now all the users of NetStar are visible in Records Manager. There are 3 roles available for given users  Admin - can manage all the users and managers. He is not able to configure NetStar in Records Manager.  Manager - can see all the records of his users. For example, it can be manager of department who has certain amount of employees.  Agent - employee. He can see and manage his own records.      All the users are able to access Records Manager via web browser using their credentials which can be set in NetStar      18. Configuration of Records Manager is completed. Now configure Storage Manager in NetStar. Create new LAN physical storage and fill in IP address of Records Manager, user name/password (it was set in point 13 of given manual, login is always admin) and storing folder

Question 5

2N Starpoint IP Phones - How to synchronize phonebook with 2N NetStar

Accepted Answer

Please download actual fw from ftp.2n.cz (at least 6.42.9.2)  Set up in the phone the IP address of NetStar: (NetStar provides a fttp server for the phone)   Set up in NetStar a group, in which the SIP phone belongs :   FW: 2  .6.x     Programming tool: 2.6.x

Question 6

Allwin (billing software) does not work

Accepted Answer

Please check following settings:  NsBridge.dll in Allwin folder does correspond with fw in NS  Port 6991 is opened on NS (Console - Bridges)  Make sure the Port 6991 is not blocked by an Antivirus software

Question 7

Audio files - Progress tones - Required format in 2N Netstar

Accepted Answer

Wav, 8kHz, 8bit, mono, A-law.

Question 8

Audio-relay card - How to set up jumpers on NetStar

Accepted Answer

Please check HW manual –  pages 25-26.

Question 9

AutoClip Routing on NetStar

Accepted Answer

AutoClip routing is used in the situation where you make an external call and there is no answer. If the recipient later notices the missed call and number, they may call back. Thanks to the AutoClip routing feature, their return call will be directed directly to your extension without the need to go through an IVR service or a receptionist. This also works when the outgoing call is routed through a GSM/UMTS gateway and the call recipient sees just the number of the SIM card used by the gateway.  Benefit to the customer  Customers calling back your company after a missed call are connected directly to the employee who made the original call.   What is the object of Autoclip router?  The AutoClip routers are used for automatic routing of incoming calls and SMS messages in case a match is found in the assigned AutoClip router. Records are added to the AutoClip routers while outgoing calls or SMS messages are passing through the carriers to which the AutoClip routers are assigned. All you need is to add a record on an SMS and send it. A record on an outgoing call can be added only if the call has been rejected or unanswered by the called party.    At first create Autoclip routerMake right click to the middle window and create your router (We created Autoclip router).  Do not forget to set Default destination. It is recommended to set here some DISA. An example how to set DISA you can find at the end of the document.Final destination - This column shows the calling party that created this AutoClip router record. The name is displayed for a PBX user and the CLI is displayed for an external user. Any incoming call or SMS are then routed to such user. (e.g. In case that NetStar is in gateway scenario).  Then assign autoclip router to GSM virtual port for outgoing direction.   It means that all outgoing rejected or unanswered calls will be saved in this router (regarding autoclip parameters) which will be able to forward recognized incoming calls to proper final destination.  Create Autoclip parametersMake right click to the middle window and create the Autoclip parameters.    These parameters have to be set for example on User group: User&Grous → Properties → Routing → Autoclip parameters for call.    Set routing on current GSM Virtual port for incoming traffic    Example How to set DISA:Make right click to the middle window and create your DISA

Question 10

Call recording - how to record marked calls on NetStar?

Accepted Answer

How to create external storage is described here, this FAQ will help create external storage for call recording placed somewhere in your network. How to install and configure Records manager is described here, this FAQ will help you install and configure Records Manager where you can easily manage your recorded calls.     In some situations it is necessary to record only internal/external calls or the calls to predefined user/phone number. It could be realized on Netstar with firmware 4.0.1 and higher. You will need Call recording and Advanced routing license. Let's imagine that we need to record outgoing calls to GSM network. Internal calls are not recorded. 1) First of all create a complex router and set it according to the picture:   All the calls going through this router are marked.   2) Now all the calls dialed to GSM must be routed over this complex router. For example- in Common router you have set outgoing calls to GSM. Select complex router as the destination:     3) And the last step is enabling call recording on the User group or certain users:

Question 11

Call transfer doesnt work and why?

Accepted Answer

Check "  ME regime  " in Global data- should not be used.

Question 12

CLIP is NOT displayed on analogue lines CO

Accepted Answer

If you use analogue CO lines for interconnection with PBX or PSTN and no CLIP is displayed on extension of Netstar, then check the following settings: 1) Method of CLIP transfer: FSK or DTMF 2) Timeout of CLI reception - by default the value is 3000 ms, increase on 5000 ms. All the settings are depicted below.

Question 13

Conference - How to create a conference call and conference room

Accepted Answer

Conference call can be done with 2 ways. 1) Dial "special combination" and then step by step dial the numbers of all participants. For example: there are extensions with numbers 100, 200, 300, 400 and external number 900 800 700. In order to create a conference call just dial *1#100*200*300*400&*0900800700#, where 0 is an extra prefix to access national and international phones. This prefix is taken as the example, it can differ on some systems. All the numbers are separated with “*” sign. 2) The second option is to create a conference room. Conference room contains predefined number of internal/external extensions. It is enough to dial ID number of the conference room and all the participants wll be called automatically. In order to create a conference call follow the instructions depicted in the figure below:   In this example the conference room can be dialed by the users enumerated in the table and by users who have right to "Dial others". On the figure there is only one user who can dial the conference room - user 432 SIP. If you want to dial someone who is not listed in Netstar database, just select "Address" parameter as the destination and enter his number. In this case preceed with the step 4 because it is necessary to specify the path for outgoing calls and SMS. When all the settings are done dial *2#1234#, where 1234 is the access code of given conference room. You can create different rooms, each room can contain predefined number of users.

Question 14

CTI Interface - How to set up_version 3.X.X

Accepted Answer

XML Bridge The mission of the XML Bridge is to secure encapsulation and mediation of PBX proprietary interface (message bridge). Secure in the sense that the user application does not work directly with binary structures from which the messages are composed, but is their XML image. It avoids undesirable behavior of the system in case that misspelled external application sends an incorrectly formatted message. XML Bridge also defines a set of messages that may be exchanged between external programs and NetStar. Model user application is schematically illustrated in the following figure.  Communication Model of NetStar User Utilities  Operator.exe – any application using NsBridge.dll for communication with NetStar PBX    Message-bridge – proprietary communication interface of NetStar PBX.    A program that connects to the PBX NetStar needs a dynamically linked library NsBridge.dll. It consists of a message-core including message-bridge from XML compiler and the session manager. Library must be initialized after its introduction by calling function InitNsBridge. This function must be called before you use any other library function. Function ExitNsBridge needs to be called before library release in order to do the correct release of non-allocated sources. Value definitions for the functions in NsBridge.dll are located in NsBridge.h.    TestNsBridge.exe  We will use the TestNsBridge.exe application for the connectivity test. This application can be used as a simulator of your application.  Check the version of NetStar PBX software (version NsBridge.dll must match the version of firmware in all 5 parts, for example: 3.1.4.99.20)  Check opened ports through NetStar Administrator or via console menu. In the console menu you can find it in: Configuration> Bridges> Display  Choose the port which will be used. For the first connection is recommended to use a port without authorization. This eliminates the need to enter the username and password. For our testing we could open port 6991 without authorization.  Then connect using TestNsBridge.exe with parameter IP address:portTestNsBridge.exe xxx.xxx.xxx.xxx: 6991 = where xxx.xxx.xxx.xxx is the IP address of the PBX and the 6991 port.  If you would like to use port with authorization, you need to enter username and password (see. Chapter 5)  You are now connected to the PBX NetStar and you can use all the commands that can be found in the document: Example.xml  All documents can be found in folderC:\Program Files\2N Telecommunications a.s\NETSTAR\Administrator X.X.X\CTI_Interface\. . .    Connecting with TestNsBridge.exe to port without required authorization Through NetStar Administrator or through console menu check opened ports and set one port, which does not require authorization. a) NetStar Administrator: In menu „Network“ – „Service settings“ – „TCP/IP Communication port“ add TCP port and uncheck field „Require authorization“  a) Console menu: In console menu „Configuration“ – „Bridges“ – „Open“ set port number to which you would like to connect (6991) and in the next step type „n“ to answer question „Has the bridge to require authorization“ You can see opened ports in menu „Configuration“ – „Bridges“ – „Display“  We left port 6991 opened without authorization requirement in this example. Now we can connect via TestNsBridge.exe with parameter IP address:port TestNsBridge.exe xxx.xxx.xxx.  xxx:6991  = where xxx.xxx.xxx.xxx is IP address of NetStar PBX and 6991 is port.  XML bridge connectivity to the target system is performed by BIND command. If the connection goes via unprotected channel, the connection is built and ready to use when this answer is received: .   Connecting with TestNsBridge.exe to port with required authorization Every NetStar PBX has port 6992 opened with authorization required by default. We can choose port 6992 to connect application TestNsBridge.exe or create new port with authorization required. In our case we will open port 6993 which will require authorization. Again there are two choices how to do it: a) NetStar Administrator : In menu „Network“ – „Service settings“ – „TCP/IP Communication port“ add TCP port and check field “Require authorization”    b) Console menu: In console menu „Configuration“ – „Bridges“ – „Open” set port number to which you would like to connect (6991) and in the next step type „n“ to answer question „Has the bridge to require authorization“ You can see opened ports in menu „Configuration“ – „Bridges“ – „Display“    In this example we left port 6993 opened with authorization requirement. Now we can connect via TestNsBridge.exe with parameter IP   address:port   TestNsBridge.exe xxx.xxx.xxx.  xxx:6993  = where xxx.xxx.xxx.xxx is IP address of NetStar PBX and 6993 is port.  The application is informed about the need for authentication by receiving of the authentication element. This element has no attributes but contains sub-element method. This is a list of supported types of authentication. If bridge supports SASL method then under the appropriate element there is a list of supported authentication mechanisms - elements mechanisms. All types of authentication are described in the manual: CTI doc_XML_bridge_1_22_cz.pdf We will now login to PBX using method LOGON which requires username and password. For our purposes we will create user „Test“ with password „Test“ using application NetStar Administrator. Then we can send instructions to application TestNsBridge.exe: ; And wait for answer: .  Connection is now built and ready to use.   CTI CTI module is primarily used for retrieving stations, users, monitoring of users and calls in PBX and last but not least to actively control the PBX and to receive and send messages. Examples of CTI functions use:

Question 15

Database backup - How to backup the database and how to capture a trace 2N NetStar SW

Accepted Answer

How to get the database  Go to Netstar Administrator and connect to Netstar in Off-line mode.  Click “Connect” icon.  Load the database from Netstar by clicking “Load from PBX”.  After the database is loaded, disconnect from the NS.  Go to Wizards -> Database export.  When the below window pops up, click “Yes” and choose a folder to which you want to save your database.    How to get a trace    Connect to the Netstar in On-line mode and move to “Trace” tab.  Click the right mouse button to desktop and from the shown menu choose “Clear log”.  Now make a call and catch the problematic situation to the trace.  If all necessary information is recorded, move to Trace -> Save trace to file and choose destination to which you want to save the file.

Question 16

Dialthru gateway - How to set 2N NetStar as a dialthru gateway

Accepted Answer

This „how to“ manual will help you to set up 2N NetStar as a dialthru PRI  GSM/UMTS gateway. Before you start programming the system, it is highly recommended to read the configuration manual.    Check your licence – you need at least 2 PRI ports licence (Global data -> Licence) . If you do not have it, please contact us at support2n.cz.    2. Set up both PRI ports.   Port connected to PSTN as TE, port connected to PBX as NT. (Set up the jumpers too!)  Set up TE port as Default OUT and NT port as Default IN - important for proper network tones transmission. (Virtual ports -> BRI/PRI -> Basic).   Set up TE port as a port used for synchronisation. (Hardware -> Synchronisation).  Delete all tones from Default IN (Properties -> Tones).   3: Set up GSM/UMTS ports   Create a bundle - GSM (Routing -> Routing objects -> Bundle) and use all GSM ports in this bundle. It is recommenced to use cyclical strategy.   If you want to have an overflow to PSTN network (in case all GSM/UMTS modules are busy), create another bundle - GSM overflow (linear strategy).         4. Create a router - From PSTN. (Routing -> Routers -> Called party number Router) - the purpose of this router is to route all traffic transparently from PSTN to the PBX. Check the format of the called party number, which is sent by the provider (DDI, national format) and set up the router. (If you do not know the format of the called party number use “?” as a prefix). Calls will be routed to NT port (to PBX).   5. Use router From PSTN as a from port router on the TE port. (Properties -> Routing)  ¨ 6. Create a router - From PBX. (Routing -> Routers -> Called party number Router) - the purpose of this router is to be a decision maker which will send GSM calls to GSM and all other calls to PSTN. (In our example the GSM prefix is 7 and GSM numbers are 9-digit long).   7. Use router From PBX as a from port router on the NT port. (Properties -> Routing)  8. Create router – From GSM. (Routing -> Routers -> Called party number Router) - the purpose of this router is to route all calls from GSM to a predefined extension in the PBX (in our example 111).   9. Use router From GSM as a from port router on Default OUT. (Properties -> Routing) 10. Switch off CLIP normalizing (Global Data -> Localisation) - in case you do not want NetStar to modify incoming CLI (e.g. strip international prefix)  Now you should be able to make inbound and outbound calls. In case you have any problem, do not hesitate to contact us at support.2n.cz. Many answers can be also found at faq.2n.cz.

Question 17

Do you hear some clicking during the call or the call is even disconnected?

Accepted Answer

Probably the port is not synchronized properly. Set up TE port for synchronization.

Question 18

Email to SMS - how to set it in 2N NetStar

Accepted Answer

Creating Outlook account On the following picture there you can find an example how to create Email account, from which all messages will be sent directly to SMTP NetStar. Procedure how to create a new account in Outlook is following : Tab Tools –> Account settings –> Icon New account –> Microsoft E-Mail ,POP3, IMAP, or HTTP –> check configure and settings server… –> Next –> Email settings –> fill the table regarding the picture below:   On the following picture you can see an example how to to send SMS directly from the Outlook. For this example you can see mobile number 606123456789 followed by @netstar.com. To the subject part type text of your SMS message.     NetStar Settings  SMTP At first it is necessary to create a new SMTP Virtual port. In our case the type will be Server. Do the settings according to the next picture. Click right mouse button in the middle section (group Default OUT) and choose Add – specify the name (it is Google in our example) and set type: SMTP Server. Then go to the section "Stack" and set Authorized group as "Not required" which means that incoming e-mail messages are accepted without authorization.     Create GSM bundle Now we have to create a new GSM bundle - group of GSM virtual ports which will be used for SMS sending (after email will be transported to SMS). Go to section "Routing –> Routing objects –> Bundles". Make a right click in the middle section and add new bundle for GSM ports as shown in the picture below.     From port routing Now we can set "From port routing" on SMTP virtual port. So let’s move to the section "Virtual ports –> SMTP –> Properties –> Message routing" and fill in the "From port" field as shown in the picture below. Also focus on "Parameters of unsuccessful sending".   In case you are going to send more SMS, focus also on the parameter "Relax interval between calls" in the section "Virtual ports –> GSM –> Stack –> Basic".   Note: Another choice can be the usage of MS Word – mass mailing cooperating with MS excel database. By usage of these two programs you can set mass mailing. Each email will have only one addressee and your message will be sent to all numbers from excel file. Note: In this case it is necessary to set in Outlook the account for messages purpose as Default account – because MS Word synchronizes automatically with default Outlook account.

Question 19

External storage - How to create an external storage

Accepted Answer

Any external storage which supports SAMBA protocol can be used as network storage. So even PC with Windows OS can be used. We have chosen such a PC as an example in this FAQ. Create a new folder on a hard drive of this PC - for example "Records". This folder has to be shared with other users. How to share this folder? In the menu properties click on "Share" and add "Everyone", also click on "Advanced Share" and make sure that "Share this folder" is checked. All voice files recorded in Netstar will be stored in this folder.  As a next step you have to add this external storage in Netstar configuration tool and map it to Netstar PBX (Global Data -> Storage manager -> Voice Record -> section Physical Storages -> right mouse click, choose „Add“ and write the name). The name of physical storage can be different from the name of folder in computer. It does not have to be Records - as it is in our case.   Change the type of storage to “Network” and in section "Access point" fill the path to folder on physical storage. In this case IP address is address of PC and folder is in Root (\192.168.50.11\Recording). Further you have to fill Login and Password. These are credentials to particular PC. It is neccesary that this login has admin rights - so it has to have rights for writing to this PC.   If you did everything right in previous steps, now you will see State "Ok" in Detected Storages.   In the last step right click on "Voice recording" and choose "Add physical storage mapping". Then use drag and drop and move storage created by you to first place. This will ensure that records will be stored to newly created storage and not to Nestar internal storage. If records will be stored in internal storage then there is a serious threat that this storage could be overloaded. It is recommanded to delete internal storage "DATA" from section "Voice recording".     Setting of parameters for external storage 1. You can set calls recording for user, group or directly for port always at fold "Properties - Recordings". At fold Quotas you can set other parameters. Like parameters quota usage, item size, item life and number of items. Further it is more then recommanded to set that after limit of quota is reached (any quota which is set on the particular line), the oldest records will be deleted - see picture below last column - Yes. Example: We will set quota for group of ten users and maximal Number of items will be ten. This parameter will be used for all 10 users in this group and for this group the quota will be 100. (10 users x 10 items=100 items) If quota is related to port or group, maximal number items is then applied to all subjects.    2. In combination with checked parameter "Keep files removed from records" the Netstar will deleted only path to file and not file itself. This file stays on shared network storage. That means that records wont be available for play for example by Netstar Assistant, but they still be stored on physical storage, where they will be available to play if needed.

Question 20

Factory reset - How to make a factory reset of 2N NetStar

Accepted Answer

To make a factory reset of 2N® NetStar is possible directly in the Netstar Administrator tool, in the menu PBX select an Restore factory setting option and confirm

Question 21

Factory reset - How to perform factory reset of 2N NetStar

Accepted Answer

To perform factory reset of 2N® NetStar is possible directly in the Netstar Administrator tool, in the menu PBX select an Restore factory setting option and confirm

Question 22

Failure of network storage manager

Accepted Answer

Make sure that you have set a parameter "Attempt connect in[s]" higher than 10. Parameter – 1 means that after the failure of network storage, NS will not try to restore the connection.

Question 23

Firmware downgrade - Is it possible to downgrade 2N NetStar?

Accepted Answer

No, downgrade is not the supported procedure.  If you made a downgrade by accident, please make a factory reset and upload a back–up database (suitable for the version to which you have downgraded).

Question 24

Firmware upgrade - How to make a firmware upgrade of 2N NetStar

Accepted Answer

Always if you upgrade Netstars firmware, you have to go through the last version of actual series. Preview of firmware's series together with lasts firmwares are in the table below.   ¹In 3.0.x series it is necessary to upgrade to 3.0.11 version first and then to 3.0.15. Example:  You have version 2.6.2 in your NS firmware and you would like to upgrade it to version 3.1.4.  Upgrade procedure:  Upgrade to fw 2.6.4. Update progress tones and router Services.  Upgrade to fw 3.0.11. Update progress tones and router Services.  Upgrade to fw 3.0.15. Update progress tones and router Services.  Upgrade to fw 3.1.4. Update progress tones and router Services.   Upgrade step by step  Go to www.2n.cz and download latest firmware for your 2N® NetStar.  Run "setup+firmware x.x.x" file and go through the installation process.   At the end of the installation a window appears with the path to the new firmware stored in computer - note the path!   Confirm finished installation.    Connect to 2N NetStar via the old config tool!  Go to PBX -> Upgrade.    Enter correct path to the firmware file (Default path is: C:\Program Files\2N TELEKOMUNIKACE\2N NetStar\NetStar Admin Tool x.x.x\Fw\x.x.x).  Click Upload and confirm reboot of the device.  Run the new (!) 2N Netstar Administrator and connect to 2N Netstar (IP address and settings of the network are not deleted due to the upgrade).  Go to Global data -> Progress tones and by clicking „Restore default progresses" update the progress tones.   Update in the same folder also the services.   As a last step move to Routing -> Routers and delete all records from router SERVICES. Then click the right mouse button on „SERVICES" and from given menu choose „Update router". In "Update router" window choose along „Services".

Question 25

Format of audio tones

Accepted Answer

In some situations it is necessary to upload own audio files to Netstar. It is important to have a correct format of audio files which must be 8kHz, 8bit, mono, Alaw, wav. No mp3 format is supported

Question 26

Forwarding call does not work. What should I check?

Accepted Answer

Check if there is FROM PORT routing set up on station, user or group.   For standard calls it is enough to set up routing at DEFAULT IN.

Question 27

Free minutes - How to set them on 2N NetStar

Accepted Answer

This feature must be set up on a virtual port or SIM card.   Set up a tariff in Billing and tariffs (from firmware version 3.0.0 and higher).Firstly specify operator (T-mobile, Vodafone...), then divide free minutes to e.g. fix line and GSM. For each „Credit list“ you can set up another time conditions and charged value.!!!! Important!!!! In case you call the number with prefix which is not included in the tariff setting, the call will be terminated.  2. Set free minutes/SMS in the tag Free Minutes/SMS on a virtual port or SIM card. Double click to the line open free minutes setting table. In case you  would like to use free minutes since now (not for next month), you have to check box „Set to this month“.   If you need to use the same free minutes for other virtual ports or SIM cards, you can copy already used free minutes. You get this option when you set free minutes.     3. Assign the GSM port to the bundle with Alocation strategy: „By credit“. The GSM port or SIM card with most free minutes will be used.      4. We highly recommend to check installation manual in NsAdmin before you start setting up the system.

Question 28

How to backup the database and how to capture a trace 2N NetStar

Accepted Answer

Go to Netstar Administrator and connect to Netstar in Off-line mode.  Click "Connect" icon.  Load the database from Netstar by clicking "Load from PBX".  After the database is loaded, disconnect from the NS.  Go to Wizards -> Database export.  When the below window pops up, click "Yes" and choose a folder to which you want to save your database.    How to capture/download Trace   Connect to the Netstar in On-line mode and  Move to "Trace" tab  Right click in the blank space  Choose Filter  Tick the checkbox for CC_MESS and CCR_MESS and hit "Use Filter"  Click the right mouse button to desktop and from the shown menu choose "Clear log".  Now make a call and catch the problematic situation to the trace.  If all necessary information is recorded, move to Trace -> Save trace to file and choose destination to which you want to save the file.

Question 29

How to install AoC reader with 2N NetStar

Accepted Answer

1) Start the installation of the AoC reader by double click on setup icon (NsAocRSetup_version.exe) and you will reach the Setup Wizard. After this set a few basic parameters as you can see in this short presentation. Make sure that your version is compatible (the same) as in your Netstar       Set up the IP address and login name and password for you Netstar CPU      Select the destination for AoC files (txt format)   Select a folder where would you like to install program AoC reader   After you start the program (nsAocR.exe), you will be able to captured the AoC records from your Netstar.      You can find the captured data in txt format, here is an example

Question 30

How to provide all information to effectively resolve a technical issue on 2N NetStar?

Accepted Answer

Dear customers, In case you have found some problems with the device, please report it to https://support.2n.com/. Reported issue should contain following information:   Please describe us your problem in detail, so that we will be able to replicate the behaviour based on that description.    Send us the current configuration of the device - in the pictures below there is shown how to do that.   How to backup the database and how to capture a trace 2N NetStar  Note: It is highly recommended to use always the newest FW version available on 2N web page (http://www.2n.com/en/) before you report us a technical issue!  Called party and calling party numbers (if relevant) and time of troubleshooted situation.  Send us the information about FW version and the serial number of used components such a CPU, rack, external CPU if used.Note: It is highly recommended to use always the newest FW version available on 2N web page (http://www.2n.com/en/) before you report us a technical issue!   Send us the description of the LAN topology, NATs, IP addresses, etc.   Network trace in case of a VoIP (RTP) problem.  Any information which you think might help us to solve the issue

Question 31

How to provide all information to effectively resolve a technical issue on 2N NetStar SW?

Accepted Answer

Dear customers, In case you have found some problems with the device, please report it to https://support.2n.com/. If you do not have access informations, contact your account manager. Reported issue should contain following information:   Please describe us your problem in detail, so that we will be able to replicate the behaviour based on that description.    Send us the current configuration of the device – in the pictures below there is shown how to do that.   Database backup - How to backup the database and how to capture a trace 2N NetStar SW  Note: It is highly recommended to use always the newest FW version available on 2N web page (http://www.2n.com/en/) before you report us a technical issue!  Send us the information about FW version and the serial number.   Send us the description of the LAN topology, NATs, IP addresses, etc.   ethereal trace in case of a VoIP (RTP) problem  called party and calling party numbers (if relevant)  any information which you think might help us to solve the issue

Question 32

How to upgrade Records Manager

Accepted Answer

1) First of all upload file netstar-package-trunk-x.x.x.x.x.zip to server by means of WinSCP software   The login/password is admin/2n     The file must be copied to /home/share directory. 2) Enter console mode (you can use PuTTY software, the connection can be done over SSH/Telnet protocol) and enter the following commands:  Unpack uploaded files  unzip netstar-package-trunk-x.x.x.x.x.zip   Back up configuration files -  backup config.js file - cd /var/www/netstarrm/js/config then sudo cp config.js config.bak  backup configuration.groovy file - cd /etc/netstar/ then sudo cp configuration.groovy configuration.bak  create dump of database - mysqldump netstar > /tmp/zalohadb.sql   Upgrade Records Manager  If you have connection to Internet enter sudo yum install netstar-rm-1.0.0.x-xx.noarch.rpm netstar-connector-1.0.0.x-xx.noarch.rpm  If there is no Internet connection enter sudo rpm -Uvh netstar-rm-1.0.0.x-xx .noarch.rpm netstar-connector-1.0.0.x-xx.noarch.rpm   Restar tomcat service  service tomcat restart

Question 33

ID Tables - How to set it in 2N NetStar

Accepted Answer

ID Tables - How to set it in 2N® NetStar   Identification tables The identification tables are used for changing the calling party number. To create and modify them go to section "Routing -> Identification tables". The setup menu consists of two main windows – Default setting window and Exceptions window.    Default setting window Parameters in this window help us to set identification parameters for all calling parties that have not been found in the Exceptions window.   Scheme - define whether the calling party identifies itself by a Phone number, URI or it uses the previous identification after passing through this row. Type - define the calling party number type before identification change. Choose one of the Unknown, Internal, Local, National, International and Preserve options. Use Unknown if you are not sure which type of number is used. Use Type only if the Scheme parameter is set to Phone number. Number/URI – specifying the number which will be used as a calling party identification. Replace from end - specifying the count of digits from number specified in Number/URI parameter which will be replaced by original internal number. If the original internal number is not transmitted, the resultant number will be same as set in the Number/URI parameter. Add to beginning - use this parameter to add specific digits to the beginning of the new number.     Exceptions window In exception window you can specify objects (users, virtual ports, etc.), for which different settings than the default one will be used.   Parameters in this window can be divided to three main groups  Calling party determination  it contains the first five column where is specified the calling object for which is the exception valid.  Destination type - in this column select a type of the calling party. Choose Any, Extension, Group, Type of extension, User, Virtual port or Virtual port type.  Destination - use this column to define a calling party of the selected type (ex. user).  Scheme - use this column to specify if the calling party identification should be presented as a Phone number, URI or Every (not specified).  Type - use this column to define the calling party number subtype before identification changing. Choose one of the Unknown, Internal, Local, National, International and Every options. Use Every if you are not sure which type of number is used. You can use Type parameter only if the Scheme parameter is set to Phone number.  CPN prefix (CPN – called party number) – by this parameter you can set that the same user (station, etc.) will identify itself differently depending on the called number. If you set this parameter to 420, this row will be valid only if the called number will be 420xxxxxx.   New calling party identification  it contains next five columns (six to ten). Set completely new calling party identification.  Scheme - define whether the calling party identify itself by a Phone number, URI or use the previous identification after passing through this row.  Type - define the calling party number type before identification change. Choose one of the Unknown, Internal, Local, National, International and Preserve options. Use Unknown if you are not sure which number type is used. Use Type only if the Scheme parameter is set to Phone number.  Number/URI - specifying the number which will be used as a calling party identification.   Time conditions  specify time intervals during which are the exception rules valid.      Example NetStar is connected to the PSTN via PRI line. All outgoing calls routed via this line must identify themselves as 261301xxx where xxx is an internal number of each user. The only exceptions are users "Director (600)" and "Secretary (601)". "Director (600)" will always identify himself by number 261301999 and "Secretary (601)" according to called number by numbers 261301777 (called prefix 7) and 261301888 (other called prefixes).  Open the NetStar administrator and go to menu Routing -> Identification tables. Here click the right mouse button and add new id table.   In new id table erase the default parameters and set them according to picture below. By this settings you specify that all calls which are not in exception table will identify themselves by number 261301000 where last three zeros will be replaced by user´s internal number.   When default setting is done, move to the exceptions table and insert one record for user "Director (601)" and two records for user "Secretary (600)". For director set parameter Number/URI to 261301999 which will secure us that the director will always identify himself by this number. In first record for secretary set parameter CPN prefix to 7 and Number/URI to 261301777. By this setting we specify that if secretary makes an outgoing call to number starting with prefix 7, she will identify herself by number 261301777. If she makes a call to number with any other prefix, she will be identified by number 261301888 (second record).    If you set everything properly, your id table should look like the table in the picture below.  If your setting corresponds with previous picture, you created id table successfully. Last thing you have to do for proper calling party identification change is to assign this table to PRI line. Go to "Virtual ports -> BRI/PRI", choose correct PRI port and in Identification table parameter choose previously created id table.

Question 34

incoming-call-drops-after-first-ring

Accepted Answer

Check incoming routing. Set up 0 digits after.

Question 35

ISDN - Basic principle of VOIP operation and ISDN synchronization

Accepted Answer

This section describes the basic principle of VOIP operation for better understanding of Netstar SIP settings. Netstar supports SIP (Session Initiation Protocol) only. Let us consider simplified network architecture of SIP:  Proxy server/Registrar is used to control all connections in the network. It monitors the state of User agents and their location according to IP address. User agent is simple IP extension/phone. It must be registered on Proxy server/Registrar. Each user agent periodically sends REGISTER messages to the Proxy server. The message contains user ID and its IP address. Server replies with OK message. This message informs User agent that he is registered successfully and is able to make and receive the calls. All signaling is managed by the Server. When connection is established User agents start sending/receiving voice packets using RTP (Reliable Transport Protocol). All RTP packets are sent directly among User agents. Proxy server does not pass and process RTP packets, it is used only for signaling. SIP messages have the format of HTTP protocol so the content of all messages can be captured and read in the network sniffer. What should be set on Netstar to enable SIP communication? For SIP communication Netstar uses CPU and VOIP cards. CPU card has the functions of Proxy server/Registrar, it controls SIP signaling. VOIP card is used only for RTP packets processing. Make sure that VOIP cards have assigned IP address. Otherwise the red LED will be shining on the front panel of VOIP card. Also make sure that you selected proper VOIP card and port range for RTP processing:  Netstar supports DTMF transfer in the following modes:  In-band (only for G.711 codec)  RFC-2833  SIP INFO (only receiving)   ISDN synchronization Hardware configuration of Netstar can have PRI or BRI ports. Netstar can be used in different scenarios. That is why it is very important to set ISDN synchronization. Netstar can work in both modes: Master and Slave. When Netstar is connected to PSTN, its port works as TE in Slave mode. All other ports which are connected to some PBX can be set as NT and Master. The ISDN port that receives a clock signal from PSTN can synchronize all other ISDN ports which are working as the Master. Netstar can have several sources of clock signal. In this case it is necessary to set priority of the sources. On the figure below the right side contains ISDN ports that receive clock signal and distribute it to the ports on the left side.

Question 36

IVR - How to set it in 2N Netstar

Accepted Answer

If you want to create IVR, first you have to prepare or imagine a tree which consists of Routers and DISA (Fig1). Let’s imagine that we want to make IVR for some company. DISA will have the following messages: Greeting-“Name of company. Good morning. Please, dial the number of one of the listed departments: 1-marketing, 2-technical support, and 3-HR”. When you dial one of mentioned number, you will be routed to the corresponding DISA. Each DISA can also ask you to dial number. For example, if you dial 1 in greeting message, you will be invited to dial number in order to be connected with some of salesmen. The similar is if you dial 2. In case number 3 is dialed, you will be connected with HR assistant. So for this case you need 4 DISA and 4 routers.    Fig.1  When you have drawn scheme of IVR, you need to record DISA messages. You can do it by means of telephone device connected to NetStar. In your configuration tool go to Global data → Progress tones → Own tones (Fig.2).    Fig.2  Right click in the field Progress List → Add, fill name and press OK. Then click back to tab Progress list. There in section Settings fill Number of your created tone. This number will be used in recording your messages. Save it! Now dial from some phone (connected to NS) *56. You will be asked to press number of record. Dial the number of your own progress and press #. Now you can record your message, then press # and again # to save it in NetStar. (With this procedure you will be led by NS voice automate – immediate after dial *56)   Remember! The numbers you set in the field “Number„ must be different from already existing tones.    When you have all necessary records, you need to create DISA and Routers. Go to Routing  Routers and create 3 routers: router 1, router 2, and router 3 (All of them will be type: Called number). Then go to Routing objects → DISA/IVR. Then right click → Add, fill name of your DISA. In the field “Tone” select the record you have done. Check DTMF box, set Timeout, Type → Router, ID → router 1.      In Routers for router 1 set the following settings: Prefix → 1, 2 and 3 (the numbers to be dialed), Destination type → DISA, Destination → Marketing, Technical support and HR. There are overall 3 rows. For router 2: Prefix → 1,2,3, Destination type → User, Destination → Salesman 1,2,3. For router 3: Prefix →1,2,3, Destination type →User, Destination → Engineer 1,2,3. For router 4: Prefix → 1,2, Destination type → User, Destination → Employee 1, 2. Now you need to assign Greeting DISA to defined virtual port. Let it be GSM.     Fig. 3  Go to hardware → Boards → select GSM board → Virtual port → Properties → Routing. From port: Destination type → DISA, ID → Greeting. Save it and that is all. When somebody calls on GSM, he will hear Greeting message first and he can select where to call.    Fig. 4

Question 37

LDAP - How to synchronise Phone book in 2N NetStar via LDAP protocol

Accepted Answer

The Lightweight Directory Access Protocol (LDAP), Directory service is an application running on the Directory server, which collects and provides information on the named and frequently accessed objects that seldom change. The information is stored in the form of tree-structured records on the directory server. The Lightweight Directory Access Protocol (LDAP), working on the client-server principle, is a convenient tool for storing and accessing data on the directory server. The LDAP also includes client authentication. LDAP in 2N NetStar, The Directory service menu consists of two main sections. A list of available directory servers is located to the left and server parameters are to the right. Click the context menu in the server list with the right-hand mouse button to create, rename or delete a server. The LDAP server configuration includes:   Settings  User – use this item for user authentication in server communication. Enter without the domain.  Password – enter the user password.  LDAP Address – enter the IP address or domain name of the LDAP server to which the PBX gets connected.  Domain – enter the whole domain including the highest order domain (tel-2n.cz, e.g.).  Port – enter the port number for directory server communication. The default port is 389.  Authentication – select one of the following three authentication protocols for user authentication in server communication:  Simple – user name (DN – Distinguished Name) and password based authentication.  KERBEROSv5 – Kerberos based authentication.  Address – set the KDC server (Key Distribution Centre) address for user authentication.  Port – set the KDC server port. The default value is 88.   NTLMv2     Partitions Use the context menu to add or remove an organisational unit – phone book.  Phonebook – set the PBX phone book (directory) to which the records obtained from the LDAP server shall be stored.  Suffix – define the search area or directory level from which synchronisation with the LDAP server shall be made. Start with the lowest level.  Example: Suppose there is a structure on the LDAP server (tel-2n.cz domain) including a group (2N) and subgroups (Development, Sales, etc.). Enter the suffix ou=Sales,ou=2N,dc=tel-2n,dc=cz to download the contacts of the Sales subgroup.  Phone type – define the type of the record with which synchronisation with the LDAP server shall be made.  Caution    The records that are not included in the LDAP server are deleted from the assigned phone book during synchronisation.    Synchronisation result Use the  Global data – Scheduled tasks  menu to schedule synchronisation. Add the LDAP synchronisation event and set the synchronisation time. View the synchronisation result in the lower part of the screen.

Question 38

Microsoft Outlook - How to integrate Microsoft Outlook with 2N Netstar

Accepted Answer

Netstar platform has a possibility of Microsoft Outlook integration. Outlook can keep the contacts of colleagues and customers. You can easy initiate a call with desired contact wihtout dialing his number on the physical extension. The steps of integration procedure are described below: 1) Install Application Server (Application server can be provided by Technical Support)   2) Upload activation and Outlook integration licenses on Application server (request our Technical Support)   3) Run Netstar Application Server panel. Fill in IP address of Netstar and upload communication library   4) Enable communication with TSP driver in Server panel     5) Install TSP driver (will be provided by Technical Support)   6) Fill in IP address of Application server and login credentials to Netstar   Press "Connect". If connection is successful you will see the list of all available extensions.   7) Install Outlook plugin. Now you are able to dial

Question 39

Mobility Extension - How to create ME in 2N NetStar or 2N NetStar SW

Accepted Answer

Mobility Extension - ME The Mobility Extension is an extension feature of the 2N Netstar PBX, which enables external extensions to make use of the features that are not normally available as well as practically all PBX services. The Mobility Extension is associated with the existence of external extensions. Before starting creating external extensions and configuring their routing rules, make sure that you have a valid licence and if so, for how many extensions the licence is valid. Verify this in the licence tables in the lower right-hand part of the  Global data – Licences  menu. In the row called Mobility Extension user you can see the count of licences owned (third column) as well as the count of licences required by the PBX (last column). The last column shows not only the external extensions created but also the Transfer parameter on the Properties tab on the extension and user levels. If you set this parameter to Yes, only one licence will be required for the extension, and the count of licences required for the user will be the same as the count of the user extensions (external extensions are counted only once).     External Extension Creation  In principle, an external extension can be created in three ways. First, you can create an external GSM/ PSTN extension while adding a user as shown in Figure 1. A conventional GSM extension (cellular phone) is configured in the GSM part and a normal fixed line of a public network subscriber is configured in the PSTN part. In the case of GSM external extensions, the GSM text is automatically added to the end of the name, and in the case of PSTN external extensions, the PSTN text is added. To forward SMS messages delivered to the user's cellular phone of an external extension, check the Resend SMS option. For the SMS routing configuration see below. Figure 1: Creating External Extension by Adding a User   The second way to create an external extension is to create an external extension and then assign it to a specific user (an external extension may not exist without its user). This can be done in the  Users – Extensions – External  menu. In the context menu, add an extension, enter the name and number, assign the extension to a user and, if necessary, enable the Resend SMS option. Finally, click OK for confirmation. The third and last way is to add an external extension over the given user. In the  Users – Users & Groups  menu select the user, display the context menu and click Add extension. Complete the extension name and number and enable the Resend SMS option if necessary. See Figure 2 above again.   Having added an external extension and saving the configuration, check the external extension for a valid licence on the Basic tab in the Required licences section on the extension level. Refer to the   Global data – Licences  menu for the total count of the Mobility Extension user licences.     Routing Incoming Calls with Mobility Extension What is necessary:  an external extension  From port routing  DISA direct inward dialling  permitted transmission for putting a call on hold  Routing of incoming calls from external extensions is associated with the recognition of these calls immediately after arrival at one of the 2N® NetStar ports. This recognition is based on CLIP (caller identification) compliance with its subtype. Further routing is then governed by the settings of the recognised external extension (Routing tab in the extension properties, see Figure 2). The From port item helps route the incoming calls. It consists of Normal and Services and held. The first item sets the destination for the initial routing of an incoming call. The other is used for holding of a call or dialling a service with no destination defined. For easier understanding, Annex 1 shows a flow chart of processing of an incoming call from an external extension.  Figure 2: View of External Extension Routing Tab   As shown in Fig. 3, incoming calls from an external extension are routed to the DISA dial-in. See Figure 3 for specific DISA settings. With this configuration, the incoming call is routed to the Default router. Then a 10-second dialling timeout follows, which is detected by the DTMF detector (to include it, check the DTMF option in the lower part). If the 10-second timeout expires without dialling detection, the call is routed to the Operator extension.  Figure 3: View of DISA Configuration for Mobility Extension The Default router usually gives the user a much broader scope of operation than the above-mentioned Internal router because it is one level higher in the hierarchical structure. It allows the user to call internal extensions, use the services and also call public networks. Restriction of calling international numbers can be achieved, for example, by including an authorisation router.   To distinguish the rights of different external extensions, just create multiple DISA dial-ins and routers and assign different routers to groups with identical rights in the DISA to specify the calling user rights. After the call has been made, it is possible to put it on hold any time. In order to access this function it is necessary to permit it at one of the hierarchical levels. Such permission is made in the ME tab in the Properties (Figure 4). Flash pattern is used for putting a call on hold and switching between active calls. Disconnect pattern helps terminate one of two active calls and return to the other one. The Pattern time interval specifies the possible delay between the entering of the characters of one pattern (time between pressing 7 and pressing *). If the delay is longer than the set value, the entered pattern will be evaluated as invalid.  Figure 4: Common ME Tab Configuration with Enabled Transmission of Dialling of External Extension     What Is Necessary for Routing Outgoing Calls with Mobility Extension  an external extension;  No port routing;  From port routing;  a bundle of ports;  permitted transmission for holding a call.  Routing of outgoing calls to an external extension mainly depends on the configuration of this extension and on the way it is called. In principle, an external extension can be called in two ways. The first is to call a number, which is then routed to the respective external extension. The second way is to call a user of this extension. In such case, it is necessary to uncheck the Do not ring when calling a user option on the Basic tab at the extension as shown in Figure 5.  Figure 5: Part of Configuration of External Extension with Number Used for Routing   The port via which the call is to be made determines the setup of the Without port routing on the Routing tab in the extension properties (or, as the case may be, the type of the extension when using mass configuration by the fall-down structure). Figure 2 shows a suitable routing solution for an outgoing call of an external extension. The inclusion of a bundle of GSM ports in the Without port routing reduces the probability of call rejection at the respective external extension when one GSM port is busy at the moment. One of the possible settings of the bundle is shown in Figure 6. The selected cyclic allocation strategy means that at the first attempt to call one of the external extensions with this bundle set in the Without port routing, the call is routed to the first row of the bundle, i.e. to port GSM 1. At the second call attempt it is routed to port GSM 2, subsequently to port GSM 3, and then to port GSM 1 again. In case the specific port is busy at the moment of routing, the next row is automatically used. To ensure this, check the Next row if caller busy option. In case all the ports are busy, the call can be routed to the Default destination, which is a back-up solution. By credit is another suitable bundle strategy for this case. This strategy is intended for credit-monitored bundles with virtual ports. An incoming call is routed to the virtual port of the bundle with the currently highest count of free minutes. If there are more rows with the same count of free minutes, the sequence of rows in the bundle is respected. If a row object is busy or unavailable, the call is routed to the next row or terminated.  Figure 6: Typical Configuration of GSM Port Bundle for Outgoing Routing to External Extension *** Verify also with a provider that allows to send outgoing CLIP in a certain format, it might be useful to set based on the providers request in the section Users - Properties - Customer - Facility to yes (enable/disable sending of the Facility or Redirecting number in signalling for the given level).   What Is necessary for SMS at No Answer  an external extension;  SMS at no answer setting in Properties.  These SMS messages are used for information on missed calls. To send them, configure the SMS at no answer item on the Properties tab on one of the hierarchical levels correctly. A typical configuration is shown in Figure 7. Here you can see that the configuration is divided into two parts. The first part represents configuration for the SMS sent by the PBX to the counter party when the call initiated by an internal or external extension of the PBX with these settings is not answered or is rejected. The second configuration part is used for notification on a missed/rejected call of the external extension from the PBX, which was initiated over the GSM network. You can enable/disable the SMS and set the Minimum alerting time after which the SMS shall be sent if the call is not answered by the counter party. Both the SMS configuration parts can be active at the same time as shown in Fig. 7. The SMS at no answer in the incoming direction (first part of configuration) has the priority in sending. The SMS is sent via the selected destination, typically a GSM port or a GSM port bundle. If you set Origin as the destination type, the SMS will be sent directly via the port (GSM) via which the unsuccessful call attempt was made. The possibility to use the strings %n and %c for caller identification is very useful: %c provides the caller's number (CLIP) and %n includes the name specified in the respective phone book.  Figure 7: Typical Settings for Sending SMS at No Answer     What Is Necessary for Routing Outgoing SMS to External Extension  an external extension;  No Port message routing  Routing of outgoing SMS in 2N® Netstar is governed by the message routing settings on the Properties tab on one of the hierarchical levels (typically Group, User or Extension). This tab, together with the typical settings, is shown in Figure 8. The part of configuration marked as No port is used for SMS routing or forwarding to an external extension. Here a specific port is set via which the SMS is sent to the routing number of the external extension, but it is also possible to set a bundle of ports.  Figure 8: View of Typical Settings for Message Routing to External Extension   To make SMS sending to an external extension work properly, check the Resend SMS option in the configuration. The flow chart for SMS sending to an external extension is included in Annex 3. The procedure of forwarding of SMS received by the external extension user is shown in Annex 4.     Appendix  Annex 1: Flow Chart Showing Processes for Incoming Call from External Extension   Annex 2: Flow Chart Showing Processes for Outgoing Call to External Extension   Annex 3: Flow Chart Showing Processes for Sending SMS to External Extension      Annex4: Flow Chart Showing Processes for Forwarding SMS to External Extension

Question 40

Netstar diagnostic tool pinout

Accepted Answer

RJ 12 connector  DB9 famale connector pin number  1  7  2  3  3  5  4  1  5  2  6  8

Question 41

NetStar unreachable from the programming tool

Accepted Answer

Check that fw version in NetStar corresponds to version of programming tool.  Check that port 6992 is not blocked by your firewall or antivirus.  If you have fw version 3.0.0 or higher do not forget the default password has been changed for 2n. (admin/2n)

Question 42

No card except of CPU is on after you switch on the NetStar?

Accepted Answer

Probably you use fw 2.4.0 or higher. It is not a bug – you must activate the HW in Admin tool.

Question 43

NS Admin Tool - Supported operating systems

Accepted Answer

Following Windows are supported:  Win 2000  XP  Vista  Windows 7  Windows 8  Windows 10  Server 2003  Server 2008  Win 7

Question 44

PBX booster - How to set 2N NetStar as a PBX booster

Accepted Answer

This „how to“ manual will help you to set up 2N NetStar as a PBX booster. NetStar is connected via PRI/BRI between the PSTN network and the PBX and brings new services like:   Mobility Extension  IVR  CallBack  AutoClip Routing  SMS   Before you start programming the system, it is highly recommended to read the configuration manual.   Check your licence – you need at least 2 PRI ports and Mobility Extension licence – according to number of ME extensions. (Global data -> Licence). If you do not have it, please contact  support@2n.cz  .       2. Set up both PRI ports.      Port connected to PSTN as TE, port connected to PBX as NT. (Set up jumpers too!)  Set up TE port as Default OUT and NT port as Default IN (important for proper network tones transmission).  Set up TE port as a port used for synchronisation. (Hardware -> Synchronisation).  Delete all tones from Default IN (Properties -> Tones).    3 . Set up GSM/UMTS ports    Create a bundle - GSM (Routing -> Routing objects -> Bundle) and use all GSM ports in this bundle. It is recommended to use cyclical strategy.  If you want to have an overflow to PSTN network (in case all GSM/UMTS modules are busy) fill in default destination - PRI port to PSTN.    4. If you want to make calls to VoIP provider:   Create a SIP trunk – SIP GW. (Virtual ports -> SIP -> SIP Gateway).Add RTP interfaceSelect codecsSet up IP address of the other peer and realm (in our example proxy1.test.com)   set up a VoIP card (Hardware -> Boards -> VoIP Board)   5. Create a Group – ME users 6. Create User and his extensions- each user has got 2 extensions:   ME (mobile phone)  DDI of the PBX (set up the number in the same format that does PBX expect!)  In our example User 100 has got ME 111 222 333 and DDI 100  7. Create a router - From PSTN. (Routing -> Routers -> Called party number Router).  - the purpose of this router is to capture particular DDI in incoming call from PSTN and split    the call to PBX (DDI) and GSM (Mobility Extension).  In our example number 100 is captured and split and the other calls are transparently resent to PBX.   8. Use router From PSTN as a from port router on the TE port. (Properties -> Routing)   9. Create a router - From PBX. (Routing -> Routers -> Called party number Router)  -the purpose of this router is to be a decision maker which will send GSM calls to GSM,   VoIP calls to VoIP trunk and all other calls to PSTN.  In our example the GSM prefix is 7 (9 digit long). Calls beginning with 0 (9 digits long) are sent to VoIP.   10. Use router From PBX as the from port router on the NT port. (Properties -> Routing)  11. Set up IVR a. Create Router To PBX (Routing -> Routers -> Called party number Router) -the purpose of this router is to route DDI numbers to PBX (in our example DDIs - 1xx)   b. Create DISA – IVR (Routing -> Routing Objects -> DISA) -  the purpose of DISA is to play announcement to the caller and to give the caller an   opportunity to dial DDI number to PBX.    12. Create AutoCLIP router – From GSM. (Routing ->AutoCLIP Routers)   -   the purpose of this router is to route all missed calls from GSM to particular extensions,   the outbound calls have been originally made. Any other incoming call will be sent to IVR.    13.   Use AutoCLIP router From GSM as a from port router on all GSM ports. (Properties ->   Routing) and (Virtual ports -> GSM -> Basic).      14. Create AutoClip parameters - AC (Global Data -> AutoClip parameters)    15. Use AutoClip parameters AC on Default IN. (Properties -> Routing)    16. Create router – ME out. (Routing -> Routers -> Called party number Router)   -   the purpose of this router is to route calls to ME extensions. (In our example GSM numbers   begins with 7)     17. Create DISA – ME in (Routing -> Routing Objects -> DISA)    18. Create router - ME in (Routing -> Routers -> By virtual port)   -   the purpose of this router is to provide a dial tone to ME extensions, so you can dial any DDI    of the PBX.     19.   Use router ME out as no port router and router ME in as from port router on all ME (GSM)   extensions. (Properties -> Routing)    20. Set up routing for DDI extensions (Properties -> Routing)    21. Set up SMS routing (Users & Groups -> Properties -> Messages routing)   -the purpose of this routing is to give you a possibility to send SMS from NS Assistant.    22. Set up Callback   a. Create a Callback object – CB (Routing -> Routing objects -> Callback objects)    b. Create router - SMS in (Routing -> Routers -> By text)     c.   Use router SMS in as a from port routing on ME extensions (Users & Groups -> Properties   -> Messages routing)    d. Activate Callback on all ME extensions – you need a licence!! (Basic)

Question 45

PC Operator and Application server - How to install it in 2N NetStar

Accepted Answer

Introduction Communication scheme for 2N NetStar, Application Server, PC Operator an PC Communicator:   As you can see on the scheme above, if you want to use PC Operator, you have to install Application server first!   How to install Application Server  Download the application server installer and run the installation.     Note the path of the folder to which will be the application server installed (PC Operator installation file will be here).      When the installation is complete, close it and run the application server.    When the Netstar Application Server Panel window appears, set the IP address of your 2N Netstar and upgrade the NsBridge.dll library. You can find it on your computer in C:\Program Files\2N TELEKOMUNIKACE\2N NetStar\NetStar Admin Tool 3.x.x\Bridge folder.     Then move to the "License" tab and click "Download licenses" button to get the licenses from 2N server. If you do not have the licenses yet, then get the serial number and send it together with the list of required licenses to 2N technical support.     Now is the installation and settings of Application server done and you can install the PC Operator!    How to install PC Operator Go to the path where the application server was installed and run the installation of PC Operator.   When the installation is done, run the PC Operator.  Click the "Connection Setting ..." button and specify the IP address of Application server.     When the IP address is set, insert the Username and Password of the user. This user must be created in 2N Netstar and it must have assigned password. PC Operator have two options how to assigned it to telephone station:  First option is CTI interface. If the user which you use for login has analog or digital station, you will be able to initiate and accept the calls via PC Operator. If you are connected this way, you can recognize it by parameter "Status" which will be set to connected (bottom right corner).     Second option is to register PC Operator as SIP station. In this case you need that a user whom you use for login to PC Operator has created SIP station. If this requirement is met, go to section "Setting -> Options" and in tab "SIP station" add new profile and fill all necessary parameters.    After this will PC Operator restart itself and in the bottom line you should see parameter "SIP station" online. Now is the CTI interface disabled and for calls SIP station will be used.     How to install NetStar Communicator Installation and setting procedure for Netstar Communicator is the same as for PC Operator, so please follow the steps above.

Question 46

PRI gateway - How to set 2N NetStar as a PRI gateway

Accepted Answer

This „how to“ manual will help you to set up 2N NetStar as a PRI  GSM/UMTS gateway. Before you start programming the system, it is highly recommended to read configuration manual.   Check your licence – you need at least 1 PRI port licence (Global data -> Licence) . If you do not have it, please contact support@2n.cz.  Set up PRI port (including jumpers).  We recommend to set up PRI port as NT. (PRI port of the PBX must be TE).  Set up PRI port as Default IN -important for proper network tones transmission. (Virtual ports -> BRI/PRI -> Basic).  Delete all tones from Default IN (Properties -> Tones)   Set up GSM/UMTS ports  .Create a bundle - GSM (Routing -> Routing objects -> Bundle) and use all GSM ports in this bundle. It is recommended to use cyclical strategy.   Create a router - From PBX. (Routing -> Routers -> Called party number Router)This router will send all calls to GSM. It is very important to specify length of the numbers. In our example GSM prefixes are 6 and 7 and numbers are 9-digit long.   Use router From PBX as a from port router on the PRI port. (Properties -> Routing).  Create router – From GSM. (Routing -> Routers -> Called party number Router)The purpose of this router is to route all calls from GSM to the predefined extension in the PBX (in our example 111).   Use router From GSM as a from port router on Default OUT. (Properties -> Routing).  Switch off CLIP normalizing (Global Data -> Localisation)in case you do not want NetStar to modify incoming CLI (e.g. strip international prefix)

Question 47

Problems with sending and receiving emails from NS

Accepted Answer

Check if DNS and default gateway parameters are correct in Network settings

Question 48

Recording - How to record the calls on VoIP trunk and PRI interface

Accepted Answer

This section of FAQ describes how to set call recording on trunk interfaces when Netstar is used as GSM Gateway/PBX Booster. All the records can be stored in internal memory of Netstar/MMC card/external storage. In this FAQ we will set call recording on internal memory of Netstar and MMC.  First of all it is necessary to upload valid license to enable call recording.    Important!  Netstar is able to record only 20 concurrent calls. The higher amount of concurrent calls can cause overload of CPU.   Then select PRI/SIP port, go to the section Properties --> Recording and set all the parameters according to the figure below:    Important!  The internal memory of Netstar has limited capacity. So it is necessary to set such parameters like Item life, Number of items, Delete oldest achieving quota.   In the Storage Manager you can define the storage for all the records:

Question 49

Services with your Linksys phones do not work

Accepted Answer

Characters * and # are used for services if you use 2N NetStar. But in SIP # is mostly used for dialing confirmation and it is not sent from the IP phone. Therefore the service does not work. There are 2 ways how to solve it:  In router SERVICES change all # for any other character (be careful with your internal numbering plan)  Set up the Dial plan on your Linksys in menu Extension. (#xx|*xx|*#|#*[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)

Question 50

SIP Provisioning - How to set it in 2N NetStar

Accepted Answer

IP Provisioning is a feature that allows an automatic and remote installation of IP terminals connected to the NetStar. It means that every IP terminal connected to the Netstar will get automatically all settings including IP address and Account settings. SIP provisioning is supported for following IP phones: (from NetStar firmware version 4.4.21)  2N StarPoint IP T20 – indicates a 2N® StarPoint IP type T20 IP phone.  2N StarPoint IP T22 – indicates a 2N® StarPoint IP type T22 IP phone.  2N StarPoint IP T26 – indicates a 2N® StarPoint IP type T26 IP phone.  2N StarPoint IP T28 – indicates a 2N® StarPoint IP type T28 IP phone.  2N StarPoint IP T32 – indicates a 2N® StarPoint IP type T32 IP phone.  2N StarPoint IP T38 – indicates a 2N® StarPoint IP type T38 IP phone.  Well VP-2009 – indicates a Well VP-2009 IP phone.  Well VP530 – indicates a Well VP530 IP phone.  Well YV2 – indicates a Well YV2 IP phone.  Well YV3 – indicates a Well YV3 IP phone.  Yealink T19P – indicates a Yealink T19P IP phone .  Yealink T21P – indicates a Yealink T21P E2 IP phone.  Yealink T23G – indicates a Yealink T23G IP phone.  Yealink T27P – indicates a Yealink T27P IP phone.  Yealink T29G– indicates a Yealink T29G IP phone.  Yealink T46G – indicates a Yealink T46G IP phone .  Yealink T48G – indicates a Yealink T48G IP phone.  Yealink W52P – indicates a Yealink W52P IP phone .  Cisco SPA 525G – indicates a Cisco SPA 525G  Cisco SPA 504G – indicates a Cisco SPA 504G  Grandstream GXP1625 – indicates a Grandstream GXP1625  Htek UC902 – indicates a Htek UC902  Htek UC903 – indicates a Htek UC903  Htek UC912 – indicates a Htek UC912  Htek UC923 – indicates a Htek UC923  Htek UC924 – indicates a Htek UC924  Htek UC926 – indicates a Htek UC926   2N® NetStar configuration  In order to user this feature, it is necessary to know in advance the MAC addresses of the IP terminals that will be connected to the 2N® NetStar.  Go to "Virtual ports -> SIP -> SIP Proxy" and fill in for each terminal its exact type and MAC address.     If 2N® NetStar will be used as the DCHP server, set the range of IP addresses which will be assigned to terminals.   Go to "Network -> Service settings -> DHCP server".     The terminal should have activated the DHCP client parameter, so once it is connected, it will get IP address and settings automatically from the 2N® NetStarDHCP server. Once all of the previous parameters are properly set, you only need to restart the terminal and it will be automatically configured and registered in the 2N® NetStar.   Note: It could happen that the terminal restarts itself several times during the procedure.    IP terminal configuration (only if you will not use the DHCP from 2N® NetStar) Open the web configuration of the IP terminal, go to the Upgrade menu and define the IP address of the TFTP server (NetStar PBX) for provisioning.    Run provisioning After the proper configuration of 2N® NetStar, the only thing you have to do is to restart the terminal (when you use the DHCP from NetStar PBX) or click on the "Auto provision" button from the terminal menu (when you use dedicated DHCP server; see picture above).  What is provisioning changing in the terminal configuration?  The admin password: 2n  Registration name: sipprovisioning, password: 2n  IP address, port and codecs of the SIP proxy  Account parameters:

Question 51

SIP Proxy - How to create it and add VoIP terminal

Accepted Answer

Creation of SIP Proxy  Go to Virtual ports ‐> SIP and add a new virtual port.   In the popped window specify the SIP Proxy name and choose in “Type“ parameter option “SIP Proxy“.  Then go to SIP Proxy and in bookmark “Stack” set parameters according to picture below.Realm (Domain) – IP address of NetStar CPURealm (Domain) – IP address of NetStar CPURTP interface – here make a right mouse button click and add RTP interfaceCodecs – transfer required codecs from “Supported” to “Selected”DTMF according to RFC‐2833 – check this option for proper transmission of DTMF    Creation of VoIP terminal  Go to SIP Proxy ‐> Stack ‐> Terminals and add new terminal.  Specify the terminal name – it has to correspond with SIP extension name! Then click to “OK” and the terminal is created.    Creation of SIP station  First of all you need to create user group. Go to Users ‐> Users & Groups and add new group.  When the group is created, add to it new user.  At the same time when you were creating a new user, you can create also the SIP extension. In example below both user and extension have the name and the number "100".     When the new user and extension are created, go to extension setting and assign this extension to previously created terminal 100.  Last thing you have to do is to assign the login to newly created extension. You can do it in section Users ‐> User rights.     Now is everything set properly and you can connect SIP station to sip proxy. Register information will be in this case:  Username: 100Password: 100

Question 52

SIP Proxy - How to register 2N IP Intercom to 2N Netstar or 2N Netstar SW

Accepted Answer

The steps in this article require using the web interface of a 2N device. Please follow this manual in case this is your first time using the web interface.  Explanation of IP Telephony Terms  SIP (Session Initiation Protocol) – is a phone call signalling transmission protocol used in IP telephony. It is primarily used for setting up, terminating and forwarding calls between two SIP devices (the intercom and another IP phone in this case). SIP devices can establish connections directly with each other (Direct SIP Call) or, typically, via one or more servers: SIP Proxy and SIP Registrar.  SIP Proxy – is an IP network server responsible for call routing (call transfer to another entity closer to the destination). There can be one or more SIP Proxy units between the users.  SIP Registrar – is an IP network server responsible for user registration in a certain network section. As a rule, SIP device registration is necessary for a user to be accessible to the others on a certain phone number. SIP Registrar and SIP Proxy are often installed on one and the same server.  RTP (Real-Time Transport Protocol) – is a protocol defining the standard packet format for audio and video transmission in IP networks. 2N Helios IP uses the RTP for audio and video stream transmission during a call. The stream parameters (port numbers, protocols and codecs) are defined and negotiated via the SDP (Session Description Protocol).  The 2N IP intercoms support three ways of SIP signalling:  via the User Datagram Protocol (UDP), which is the most frequently used unsecured signalling method  via the Transmission Control Protocol (TCP), which is less frequent, yet recommended unsecured signalling method  via the Transaction Layer Security (TLS) protocol, where SIP messages are secured against third party monitoring and modification.      SIP 1 and SIP 2 accounts  The 2N® IP intercoms allow two independent SIP accounts (SIP 1 and SIP 2 tabs) to be configured. Thus, the intercom can be registered under two phone numbers, with two different SIP exchanges and so on. Both the SIP accounts process incoming calls equivalently. Outgoing calls are primarily processed by account 1, or, if account 1 is not registered (due to SIP exchange error, e.g.),  by account 2. Select the account number for the phone numbers included in the phone directory to specify the account to be used for outgoing calls (example: 2568/1 - calls to number 2568 go via account 1, 1001/2 calls to sip uri via account 2).   The example below shows the SIP 1 account setting, Section Services - Phone - SIP 1, The HIP device is registered to the SIP Proxy (2N Netstar SW) 192.168.50.150, The phone number ID is 100, SIP Proxy and SIP proxy registrar Server is also 192.168.50.150 and there is used a default port 5060. The Authentication ID and password is in case also required from the Pbx.   It is possible to check the current registration status in the Section Status-Services - Registration state-REGISTERED   We can now create a new user in the section Directory-Users and assign User Phone numbers regarding to dialling plan of the SIP Proxy server.   The setting of the 2N® Netstar or 2N® Netstar SW can be done in few steps as described below: In the Section Users- Users and Groups create one or more users, in our case user 100 with the same User internal number and Login   Than in the section Virtual ports - SIP crate a new SIP Proxy server in the Group Default IN. The listening port in default value is 5060, Realm (Domain) is in our case 192.168.50.150. We also have to add a RTP interface for the RTP packets and select codecs.   Than in the same configuration part in the section Terminals create a new IP Terminal - In our case Terminal 100   Then we have to assign this Terminal 100 and our new SIP Proxy server to our User, again, in the Section Users, User and groups - Basic   You can again check out the registration status in the Section Virtual ports - SIP- SIP Proxy - Stack - Terminals

Question 53

SMS at no answer - How to set it in 2N NetStar

Accepted Answer

Use the SMS subtag to set parameters for the SMS at no answer function. An SMS at no answer is a message that is sent automatically to the called user if the following conditions are satisfied:  The outgoing call must go through GSM port  The called party rejects or does not answer the incoming call.  The SMS at no answer is activated on one of the levels of the fall-down hierarchy for the calling user.  The SMS at no answer is sent through the destination defined here. Type the SMS text which ought to be sent to the called users in the SMS subtag. You can also add information about the calling number (string %c) and the calling extension name (%n) to the SMS body.  SMS settings Send SMS at no answer – send this SMS as an SMS at no answer to the called extension. This setting has a higher priority than that for an external extension. Moreover, you can define the sending timeout. If you set this timeout to 20 s, the outgoing call has to alert the called extension for more than 20 s so that the SMS can be sent after the call end. The timeout is the fourth condition for SMS at no answer sending.

Question 54

SMS CallBack - How to set in 2N NetStar

Accepted Answer

1) Create an external (mobility) extension and Enable the CallBack object Menu Users-Users & groups   2) Create a new CallBack object for SMS Routing-Routing objects-SMS Callback object   3) Create a new Router: Type – By text for SMS CallBack, Menu Routing, Routers     4) Router setting: Prefix must be the same as the text in SMS message, for example „cb“ In section Replace use the pattern %sm(2,0), where „2“ is the number of letters which will be removed from the SMS. That means if you send the SMS with text cb123456789, the dialed number will be 123456789 As a Destination Type select CallBack object and than SMS CallBack as a destination that you have created in Step 3   5) Set the From port routing For the ME user go to Properties – Messages routing, than change From port Type from default to Router and select Id SMS CallBack that you have created earlier.  6) No port routing For selected ME go to Properties – Routing –No port routing and select Destination Type and Id for the callback to user.

Question 55

SMS reader - How to install it with 2N NetStar

Accepted Answer

SMS reader installation Create a new user in 2N Netstar PBX, menu Users, Users and Groups, than right click into middle section and Add user   Fill Name and create an extension, in our case Title 100 and Number/URI 100 and OK   After that create user rights for that user, Menu Users, User rights - right click on our User 100 and create login (for example User 100 has Login and password 100)   Start the program NsSmsRSetup.exe and follow the steps on the screen During your installation follow the same steps as in AoC reader installation. FAQ AoC reader installation - How to install it with 2N® NetStar Differences Specify Netstar PBX IP address, login name and password of the user that you have created in Netstar   Now you have to run program SMS reader as Administrator (spustit jako správce)   Example of the SMSreader records

Question 56

SMS to EMAIL - How to set it in 2N Netstar

Accepted Answer

The purpose of this document is to provide basic information and instruction how to resend SMS to email. This document does not describes specific business scenario. Document shall help you to understand the routing logic and SMTP client settings (Virtual ports – SMTP – SMTP client).   Scenario  Following scenario was chosen only because of its simplicity  Incoming SMS to GSM port will be routed directly to the current User. This User will have besides a standard station also Mobility Extension and Email station. He requests that SMS should be forwarded to all of his stations.  Note: It is also possible to insert Router (type: Text) into the route path. Then at the beginning of SMS insert for example the name of recipient or just his internal number. Router can then remove the name (or number) and forward this SMS to current User.   Users – Users&Group  User „TEST“ has three stations. On all of them was checked the parameter "resend SMS:. In case SMS will be routed to the particular User, system will resend this SMS to all his Stations.      Virtual Port – SMTP – Default IN  As a next step you have to create SMPT Virtual port. For SMS to email feature it is necessary to create SMTP client. Click by the right mouse button in the middle section and choose Add Virtual port – choose KLIENT. In our case we set server “SEZNAM” (Czech one). Bellow you can see SMTP client with all necessary filled parameters. So 2N® NetStar will log to this server with predefined account (jaroslav_lambert@seznam.cz) and SMS will be then sent from this account.  Note: In case of server SEZNAM it is good to use Authentication as Login. In case of other servers Authentication can be different.      Users – Uživatelé & skupiny  The last step is EMAIL station routing settings. On current station – tab Properties, then Message routing. Because Email station is not physically connected to NetStar (it is External station), we have to set NO port routing.

Question 57

SNMP - How to configure SNMP

Accepted Answer

For monitoring the state of Netstar you can enable SNMP protocol. In order to enable SNMP on Netstar follow the steps below. No license is required for SNMP operation.   1) Upload MIB table to Netstar. MIB table is stored in this directory c:\Program Files (x86)\2N TELEKOMUNIKACE\2N NetStar\NetStar Admin Tool 4.2.0\ Select "Internet" option and click right to add MIB table:       Now Netstar is able to send all the traps. 2) If you need to send only certain traps, add a new rule in the filter:     3) Select required trap from the list    Please note, that off check "Exception" field then Netstar will be sending all the traps but selected one.If this field is unchecked, Netstar will send only selected trap.   For example, you need to monitor operation of E1 port. Select OID 1.3.6.1.4.1.6530.3.3.10  In PRI stack set one of the parameters "Inactive L1 as error", "Disconnected L2 as error" (depends on which layer of DSS1 should be monitored)   4) Now we need to set IP address of the client who will send requests to Netstar.      5) Configure client IP address, type of SNMP protocol, filter and specify the user. By default there is one user "Public" with all the rights.       Description of of SNMP traps is given below:     Trap OID  Variable  Description        1.3.6.1.4.1.6530.3.6.1           The trap which informs about the state of ASL (CO) lines. If the state of any objects which are numbered as 1-7 has changed, the trap will be sent with actual information of new sate     1  nsPortFunctioning     State of port     2  nsPortMapRack     Gives number of rack. This number should be always 0. In future this number can have different values     3  nsPortMapCase     Gives number of case with defined port. Main case is 0     4  nsPortMapBoard     Gives number of card with defined port.     5  nsPortMapPort     Gives number of port on the card with defined port.     6  nsPortMapState     Gives actual state of port. Values - 0 -67. All the sates can be read from MIB table     7  nsPortMapStateAttr     Attribute of the port.The values 0 – 4. 0 – port is off, 1 – port is being configured, 2 – ready, 3 – error, 4 - active                 1.3.6.1.4.1.6530.3.6.2           Trap which informs about state change of CO (ASL) lines. If the state is changes, this trap will be sent .                 1.3.6.1.4.1.6530.3.6.3           Trap which sends information about GSM port.                 1.3.6.1.4.1.6530.3.6.4           Trap, which sends information about DSS1 ports- PRI or BRI.                 1.3.6.1.4.1.6530.3.6.5           Trap, which sends information about Cornet port.                 1.3.6.1.4.1.6530.3.6.6           Trap, which sends information about SIP port.

Question 58

Static IP address - How to set up static IP address for 2N NetStar

Accepted Answer

In the default setting has the CPU static IP address 192.168.100.100 There are two possibilities how you can change the static IP address  You can connect with a serial cable to a COM port on the CPU and use for example a Putty program to connect and change the IP address and other basic parameters. Communication speed is 115200 Bd  The  Network – Network Interfaces  menu helps you manage all network interfaces available in the PBX. In addition to the CPU interface, there are Ethernet interfaces of VoIP boards. The bit rate of all the interfaces is 10/100 Mbit/s. These interfaces are used for communication with the PBX and SMTP clients, for signalling and RTP streams of VoIP calls. Having been opened, the  Network – Network interfaces  menu displays a list of Ethernet interfaces of the PBX on the left and selected interface settings on the right. With the CPU interface, the options are as follows: Get IP address from DHCP server – enable obtaining IP settings from the DHCP server automatically. In this case the following sections are inactive.  Use following IP address – enable the following static IP address and DNS server setting sections.  IP address – define the static IP address for this interface.  Subnet mask – define the subnet bit mask.  Default gateway – define the IP address of the router or PC through which the PBX communicates outside the LAN.   DNS server addresses  Preferred server – define the IP address of the primary DNS server.  Spare server – define the IP address of the secondary DNS server.  DNS HostName – define the PBX Host Name.  DNS Domain – define the PBX Domain Name.   Description – this field is for information only.  Producer – this field is for information only.   Tip You will lose connection with the PBX whenever you change the IP address. We recommend you to change the IP address via the console menu on the serial interface - option 1

Question 59

Summer or Winter time does not change automatically

Accepted Answer

Set up a  time zone  in Console.

Question 60

There is none or only oneway audio on your VoIP calls

Accepted Answer

Please check whether the VoIP board is connected to your LAN.  Check your NAT and firewall settings.  Check NAT for RTP packets in NS.  Check that you use different RTP ports for all GWs and PROXIes  Check "allocate transcoder" setting in Advance settings.

Question 61

User Reservation - How to set it in 2N NetStar

Accepted Answer

User reservation is one of the new features that were implemented in 2N NetStar firmware version 4.0.1 and higher. This feature is very useful in the case when you call to the user who is busy or who does not pick up the phone during the specific timeout. In this case can the calling party make a user reservation on the called party and when the called party finishes his call or come back to his extension, he can automatically make a call back to the calling party. This feature can be used only by internal users who are configured in NetStar – you are not able to make a user reservation from external extension.  There are several parameters that need to be configured for the called party as well as for the calling party. These settings can be made for station, user or group and are made in section “Properties -> User reservation”.  Settings for calling party (user 101 in this example)First of all you need to click on “Create settings” in Settings for services field – in this section you will specify progress tones and reservation code for calling party.Warning: You have to specify progress tones for all services (at least for services that will be used). It means that you cannot leave these fields set as “Default”. It is because we do not have new progress tones for these services uploaded in 2N NetStar.Then you need to specify when this user can make the reservation – choose one (or more) of these options:  Enabled when busy – if the called party is busy, then calling user can make a reservation of the call (calling party will hear progress tone set in “Reserve when busy” field). Then you need to enter “Reservation code” – this code can be unique for each user. After called party finishes his/her current call and hangs up the phone, then the user 101 will start ringing immediately. He will pick up the phone and hear progress tone set in “Incoming call tone” field. After that the opposite site (called party who was busy at the beginning - user 102 in our example) will start ringing.  Enabled when no answer – you can specify “No answer timeout” for this option and if the called party will not pick up the phone until this timeout then you will hear progress tone specified in “Reserve when no answer” field and then you will enter the “Reservation code”. After the called party picks up the phone (he can make another call) and then hangs up. Then the call to the user who made the reservation will be established.  Enabled when queue – if the called party has enabled “Queue” then you can specify “Enabled when queue” for calling party. You can set “Queue timeout” – after this timeout calling party will hear “Reserve when queue” progress tone, enter reservation code and wait till the called party calls back.     Settings for called party (user 102 in this example)For called party you have to set that other users can make reservation on this user – set the field "Others can make reservation on this user" to “Yes”. Then you can specify timeout for how long will be the call reserved on this user. This is done by parameter “Maximum time of reservation”.

Question 62

VoiceMail Classic - How to set it in 2N NetStar

Accepted Answer

Before you start Check whether you have license for voicemail in your 2N Netstar!   Operating principle  Entry to voicemail Enter in your voicemail where you can listen or manage recorded messages (dial *37)   Example: Lift the user station handset and dial the service access code *37. The user will get access to voicemail management.   Authorized entry to voicemail Enter in your voicemail where you can listen or manage recorded messages. This service enables users to get access from an unknown station (dial *38)  Example: Lift the user station handset and dial the service access code *38. The user will be prompted to input user number and PIN code. After successful authentication the user will get access to voicemail management.   Voicemail structure      Settings In order to use classic voicemail features you have to create routers and DISA messages which will be used for this purpose. You can do it very simply just by going to "Wizards -> Voicemail wizard".  When the Voicemail wizard window appear, press button "Save" and all routers and DISA messages will be created automatically!   If you will go to section "Routing -> Routers", you can check that the routers have been created and new services *37 and *38 have been added to router SERVICES.     As a last step go to the user to whom you want to activate VoiceMail and in tab "VoiceMail" enable this service. Also specify if you want to forward a call to voicemail unconditionally or after some time.

Question 63

VoiceMail to Email - How to set it in 2N NetStar

Accepted Answer

Before you start  check if you have in your Netstar license for VoiceMail  check correct setting of DNS servers in your Netstar    Settings In order to use VoiceMail feature, you need to setup email extensions for user who is going to use this feature. In order to do that, it is necessary to create SMTP client port. Go to section "Virtual ports –> SMTP", make a right click on the "Default OUT" group and select "Add virtual port". Then there will be new pop-up window where you have to specify the name of the SMTP Klient.   Stay in the "Virtual ports –> SMTP" section and click on the new virtual port called "Client" and select "Stack" tab. You must fill the information of the email account from which all emails will be sent from Netstar to the user account.   After these steps add a new Email extension for given user (in our case its user 110). Make a right click on the user 110 and select "Add extension". You will see new pop-up window where you specify name, class and email address for this user - see pictures below:     Once the new email extension is created go to "Properties –> Messages routing" and set there "No port" parameters to previously created SMTP Client virtual port.   Now move to the user on whom you want to activate VoiceMail feature. Go to the Tab "VoiceMail" and set all parameters according to the picture below.  As a last step go to tab "Properties –> Forwarding" and specify there that you want to forward calls to VoiceMail if no one picks up the call within 5 second. For appropriate configuration see the picture below:    Now if you make a test call and you should be able to see email with recorded message in your email account.

Question 64

voip-card-led-is-solid-red

Accepted Answer

Probably IP address, mask or default gateway on this VoIP card is not set up.

Lista pytań