BASE STATION NAME Searching: Base unit in the process of locating to a Master/slave as specified in DECT sync source Free Running: A locked Base unit that suddenly lost synchronization to the Master. Unknown: No current connection information from specific Base unit Assisted lock: Base has lost DECT sync. source and Ethernet is used for synchronization Sync. Lost: Handset has an active DECT connection with the base. But the base has lost DECT sync. source connection.
Screenshot: Example of part of DECT Chain tree with units in Base Group but not in tree by various reasons. When a base or repeater has not joined the tree, it will be shown with read background below the tree. RTX8660 -Rove B4 Mixed mode Rove B4 Base station can be added to existing systems using RTX8660 Base station. Even though the two base stations will be able to co-exist in the same Multi cell setup, the system will be set to some limitations.
5.13 LAN SYNC Apart from the DECT Over-the-air solution, the LAN SYNC provides an alternative option for base synchronization. The reason thereof is to allow a larger coverage of installations where the bases cannot see each other. This means that the LAN sync feature, specified by the IEEE1588 standard, will handle the synchronization over the network, instead of Over-the-Air. NOTE: To join 2 or more Base stations in a Multi Cell system you need to have one handset added to the system.
PARAMETERS IEEE1588 DEFAULT VALUES Disabled DESCRIPTION The initial port of the page provides the option to enable / disable the feature for the device Zone LAN sync setup This part of the page covers the global configuration of the synchronization zone. Description of Settings for Specific Base units is as follows: Screenshot: PARAMETERS MULTICAST IP ADDRESS DEFAULT VALUES 224.0.1.
NOTE: Must only be used for debug purpose and not enabled on a normal running system External LAN sync setup The “External LAN sync setup” covers the configuration of an external synchronization. This means that, in order to support more than 250 Base stations in a system, it is necessary to use multi-level synchronization. In multi-level synchronization, a primary zone is defined which is used by the other secondary zones in the system as synchronization source.
MULTICAST PORT 319 DOMAIN NUMBER 1 ALTERNATIVE DOMAIN NUMBER 65 To be compliant with IEEE1588, this port must be default value. Before setup, make sure no other devices are using the given IP. NOTE: This should only be changed in case other IEEE1588 equipment is on the network and using this specific IP address. Define the port which the system will listen for IEEE1588 PTP messages To be compliant with IEEE1588, this port must be default value.
CURRENT ROLE SYNC SOURCE ALT.
5.14 Repeaters Within this section we describe the repeater parameter, and how to operate the repeater. Add repeater Before registering a repeater to the system, the user first needs to add it. To do so, select Add Repeater from the repeater’s web menu and fill in the data defined by the table below Screenshot PARAMETERS NAME DECT SYNC MODE DESCRIPTION Repeater name.
Screenshot Good practice when adding repeaters to a Multi Cell system is to use manually registration, because then you can control which Base station the repeater(s) connect to. 5.14.1.2 Local Automatical Repeater controlled by auto detects best base signal and auto assign RPN. The RPN and DECT sync source are greyed out. Screenshot The repeater RPN is dynamic assigned in base RPN range. With local automatic mode repeater on repeater (chain) is not supported.
Repeaters list Screenshot The number of repeaters allowed on each Base station is defined on the Multi cell page. System combination: 50/3 – 127/1 -254/0 (please visit chapter 5.12.3 for more details). If the system combination is set to 127/1 or 254/0, you can still register more than one repeater, but it will not get a DECT Sync source and will have no function. Example: System combination 50/3: Base stations are named RPN00 – RPN04 – RPN08. Etc.
STATE FW INFO FWU PROGRESS Local Automatical: Repeater controlled by auto detects best base signal and auto assign RPN. Chaining Automatical: Base controlled by auto detects best base or repeater signal and auto assign RPN. This feature will be supported in a future version Present@unit means connected to unit with RPN yy Firmware version Possible FWU progress states: Off: Means sw version is specified to 0 = fwu is off Initializing: Means FWU is starting and progress is 0%.
ALARM SIGNAL STOP ALARM FROM HANDSET TRIGGER DELAY STOP PRE-ALARM FROM HANDSET PRE-ALARM DELAY HOWLING Alarm button RTX8830: Alarm button Man Down No Movement Running Pull Cord Emergency Button Disabled The way the alarm is signaled as it received on the handset. Message: A text message to an alarm server. Call: An outgoing call to the specified emergency number. Enable/Disable the possibility to stop/cancel the alarm from the handset.
alarm state, it could potentially be cancelled, and if the Emergency Button alarm was ignored in this case, no alarm would be sent. This is the reason alarms with no pre-alarm, are given higher priority than alarms in pre-alarm state. 5.16 Statistics The statistic feature is divided into four administrative web pages, which can be access from any base. 1. 2. 3. 4. 5.
DECT SOURCE CHANGED IEEE1588 SYNC LOST IEEE1588 PRIMARY LOST Number of time a base has changed sync source Connection is lost to all synchronized Base stations, connection will be lost. Connection is lost to one of the synchronized Base stations, in this case new primary will be selected automatically. Free Running explained First, state Free running NOT an error state, but is a simple trigger state, indicating that some changes have to be made to ensure continuous DECT synchronization.
The table is organized with headline row, data pr. base rows and with last row containing the sum of all base parameters.
PARAMETERS IDX/NAME OPERATION D-H:M:S BUSY BUSY DURATION D-H:M:S MAX ACTIVE SEARCHING RECOVERY DECT SOURCE CHANGED WIDE BAND NARROW BAND DESCRIPTION Base IP address and Base station name from management settings Total operation time for the repeater since last reboot or reset Duration is the time from data was cleared or system has been firmware upgraded. Busy Count is the number of times the repeater has been busy.
Call quality Data is organized in a table as shown in the below example. Screenshot PARAMETERS BASE STATION NAME TYPE CALL COUNT LOCAL/REMOTE SIDE JITTER[MS] ROUND TRIP LATENCY [MS] PACKET LOSS [%] R-VALUE DESCRIPTION Base IP address and base station name from management settings Call Relay conn Count the number of calls Local: Remote: Measures how the RTP packets are received, the lower the Jitter is the better Measures the time it takes for RTP packets to reach it destination.
5.17 Generic Statistics The statistic feature is divided into five sections, which can be access from any base. 1. DECT Statistics 2. DECT Synchronization statistics 3. RTP Statistics 4. IP Stack Statistics 5. System Statistics By pressing the “Expand all fields” you are able to see statistics hour by hour. “Reset all statistics” button all data in the full system is cleared.
TOTAL TIME SPEND IN MAX DLC INSTANCES IN USE AVERAGE FREQUENCY X USAGE THIS HOUR (MAX 100 PER SLOT) AVERAGE EVEN SLOT USAGE THIS HOUR (MAX 100 PER SLOT) AVERAGE ODD SLOT USAGE THIS HOUR (MAX 100 PER SLOT) PERCENTUAL TIME OF X SLOTS USED THIS HOUR TOTAL CHO SUCCESS Total number of forced PP moves The time we have spent in the highest concurrent number of instantiated DLC instances. The average use of frequency number X. The value is 100 if the frequency is fully used by a slot in the measured time frame.
TIME IN SYNCHRONISATION STATE: MASTER TIME IN SYNCHRONISATION STATE: LOCKED TIME IN SYNCHRONISATION STATE: FREE RUNNING TIME IN SYNCHRONISATION STATE: LOCKED ASSISTED TIME IN SYNCHRONISATION STATE: SYNC LOST TIME IN SYNCHRONISATION STATE: SEARCHING TIME IN SYNCHRONISATION STATE: UNKNOWN LAST REPORTED SYNC Time this hour where this Base station has had the state Master Time this hour where this Base station has had the state Locked Time this hour where this Base station has had the state Alien Free Runnin
CONNECTIONS IN USE CURRENT RTP CONNECTIONS (INCLUDING CONNECTION TYPE INFORMATION, E.G. EXTERNAL, RELAY, RECORDING) CURRENT BLACKFIN DSP STATUS The current count of instantiated RTP streams. Data only available if DSP module is installed SME VOIP SYSTEM GUIDE 1.
IP - Stack statistics IP - Stack statistics is related to this Base station only. Screenshot: PARAMETERS TOTAL CONNECTIONS OPEN MAX CONCURRENT CONNECTIONS OPEN CURRENT CONNECTIONS OPEN TOTAL NUMBER OF TX MESSAGES TOTAL NUMBER OF RX MESSAGES TOTAL NUMBER OF TX ERRORS DESCRIPTION The life time total count of used sockets. The life time highest concurrent count of used sockets. The current count of used sockets. The life time total count of transmitted IP packets.
5.18 Diagnostics This page provides information about the Ethernet connection to each Base station and Extension. Base stations Screenshot PARAMETERS BASE STATION NAME ACTIVE DECT EXT (MM/CISS/CCOUT/CCIN) ACTIVE DECT REP (MM/CISS/CCOUT/CCIN) ACTIVE RTP (LCL/RX BC) ACTIVE RELAY RTP (LCL/REMOTE) LATENCY [MS] (AVG.MIN/AVERAGE/AVG.MAX) DESCRIPTION Base IP address and Base station name from management settings Number of active DECT MAC connections to extensions in the different Base stations.
Logging The Diagnostics/Logging page allows you to collect system diagnostics information into a zip file. 5.18.3.1 RSX internal tracing RSX internal tracing can be either Enabled or Disabled. When the feature is enabled, the traced data is used by the RTX engineers which are the only ones that can debug the traces. 5.18.3.2 PCAP internal tracing This feature allows the user to choose which trace to investigate by selecting the desired parameter.
TRACE RECEIVED TCP/UDP PORT If selected, the user can select 3 received TCP/UDP ports to trace. 5.18.3.3 Info The section gives information about the traces and allows the user to “Save”, “Cancel” or “Reset traces”. 5.18.3.4 Download traces from The feature allows the user to choose from which Base stations to download the traces. If it is a Multi cell system, the data can be downloaded from all Base stations, else system diagnostics can be downloaded from the current machine.
5.20 Sys log This page shows live feed of system level messages of the current Base station. The messages the administrator see here depends on what is configured at the Management settings. The Debug logs can show only Boot Log or Everything that is all system logs including boot logs. The Debug log is saved in the file format b.log in a relevant location in the TFTP server as specified in the upload script.
6 How-To setup a Multi Cell System This chapter describes how to setup a multi cell system, add and synchronize one or multiple Base stations to the network. NOTE: It is possible to have RTX8660 and Rove B4 in the same chain, but the features of the system will be reduced to RTX8660. This means that if a user has a multi cell system with 50x Rove B4 and adds 1x RTX8660, the system will run on the RTX8660 features and exclude the extra ones from Rove B4. 6.
Country and Time Server Setup STEP 5 Navigate to the “Country” page and configure the country and time settings. Use the PC time feature or enter the relevant parameters on this page and press the Save and Reboot button. Make sure there is contact to the “Time server” otherwise the Multi-cell feature will not work. You can verify whether the Time server is reachable by rebooting the Base station and verifying that the correct Time Server IP address is still in place. Screenshot SME VOIP SYSTEM GUIDE 1.
SIP Server (or PBX Server) Setup STEP 6 Create the relevant SIP server (or PBX Server) information in the system. Each service provider/customer should refer SIP server vendor on how to setup SIP servers. a. Click the link Server at the left-hand column of home page. This is the place where you can add your SIP server for Base station use b. Next, from the Server page, click on the Add Server URL and enter the relevant SIP server information (an example is shown below). c.
Add an extension STEP 7 And an extension before you move to the Multi Cell page. Go to Extensions – Add Extension. Fill out the extension data, and press Save Screenshot You will now see the extension on the Extensions page. You do not need to fully register the extension Screenshot SME VOIP SYSTEM GUIDE 1.
STEP 8 Click on Multi Cell URL link from the left-handed menu to view the current Multi cell settings status of the current Base station. Brand new Base stations have Multi cell system feature disabled by default Screenshot STEP 9 Next, the system administrator needs to create and enable Multi cell Settings profile for the current Base station. On the Multi Cell settings Page, choose Enable option from the drop-down menu of the Multi cell system parameter.
Screenshot Click the Save button to keep modified changes of multi cell settings into the Base station. Screenshot NOTE: After you save, the System information changes status to “Unchained Allowed to Join as Primary” NOTE: The Multi Cell data synchronization ONLY works when the relevant Time Server is set in the system before Server/Subscriber profile is added or created. Refer to STEP 5. IMPORTANT: Base stations must be rebooted after the time server has been set.
IMPORTANT: It takes up to 5 minutes (synchronization time) to add a new Base station to a Multi Cell System. Screenshot STEP 14 To add more Base stations, repeat STEP 9-12. SME VOIP SYSTEM GUIDE 1.
7 Adding Extensions This section describes how to register the wireless handset to a Multi Cell system. NOTE: Minimum one server must be registered to the base (system), otherwise a handset cannot be registered to the system. Please see chapter 6.1.2. STEP 1 Login to a Base station. STEP 2 Select the Extensions menu and click Add extension STEP 3 Fill out the form and click Save.
STEP 4 In the handset and extensions list set a Check mark on the handset Idx, which you want to register and click Register handset (s). The base is now open (in ready state) for handset registrations for 5 minutes Screenshot STEP 5 Start the registration procedure on the handset by following step “a” to “d” below.
NOTE: The Access code (AC) is used to allow the handset to register to the base station. By default the value is 0000, but the user can change the AC to another numeric value. This can be done by editing the “AC” parameter, marked with green, on the Base screenshot from above. STEP 6 Confirm the registration from the unique handset IPEI which is displayed in column “IPEI” when the handset is successfully registered.
8 Firmware Upgrade Procedure This step-by-step chapter describes how to upgrade or downgrade Base station(s) and/or handset(s) / repeater (s) to the relevant firmware provided by RTX. 8.1 Network Dimensioning In principle, several hardware and software components should be available or be satisfied before Base station/handset update can be possible.
8.2 TFTP Configuration This section illustrates TFTP Server configuration using “SolarWinds” vendor TFTP Server. Create the following relevant folders as shown in the snap shots and choose defaults settings for the remaining options and save. NOTE: If TFTP server timeout settings are too short firmware upgrade might not complete. Recommended time out setting is more than 3 seconds. SME VOIP SYSTEM GUIDE 1.
8.3 Create Firmware Directories The admin from the service provider’s side must create the relevant firmware directory in the server where both old and new firmware(s) can be placed in it. (See the STEP above) Base: On the TFTP server root, create directory’s as in screenshot. Copy Base station firmware to the named directory. IMPORTANT: The 8663 directory name cannot be changed.
8.4 Handset Firmware Update Settings Scroll down and click on the Firmware Update URL link from the left-handed menu to view the Firmware Update Settings page. Screenshot Type IP address and firmware path followed by save. For Http download the firmware update server settings must be entered as follows: Screenshot 8.5 Handset(s) and Repeater Firmware Upgrade On the Firmware Update Settings page enter the relevant handset/repeater/Base station firmware for each device. Enter the required version (e.g.
NOTE: To disable handset/repeater/Base station firmware process, type version 0 in the required version field, followed by the Save/Start update button. It is recommended to use version 0 after all units are upgraded. NOTE: For handset TFTP/HTTP download only one handset type can be downloaded at the same time. In case two handset models are defined for fwu at the same time, fwu will fail.
8.6 Base station(s) Firmware Upgrade On the Firmware Update page, Base stations are updated in the same way as repeaters and handsets. After entering the required version and required branch, choose Save/Start update button and select OK from the dialog window to start the update/downgrade procedure. The relevant Base station(s) will automatically reboot and retrieve the firmware specified from the server and update itself accordingly.
[ FWU Downloading File tftp://10.1.24.103/FwuPath/8663/8663_v0440_b0001.fwu] [ Base FWU started] [ Base FWU ended with exit code 2101 (NE_FILE_TRANSFER_EOF): End of file] This is the path where the Base station expects to find the firmware: tftp://10.1.24.103/FwuPath/8663/8663_v0440_b0001.fwu If such lines can be seen on the output, please check if the path or firmware file is in the correct directory. 8.7 Upload startup/background picture to the handsets As mentioned in the previous chapter 5.
9 Multiline Feature This section describes how to register the wireless handsets to a system with active multiline feature. One handset will be able to support up to 4 lines (4 different SIP accounts) ... A handset only supports 2 call appearances. The limitation of maximum 1000 terminals in the system is maintained, and the maximum number of SIP registrations that one Base station can handle, is maintained. With 4 lines pr. extension maximum number of terminals registered in a system is 250.
When making call the user can chose which line to call from. Simply enter the number to call and press line. Select the desired line and hook off to place the call from this line. SME VOIP SYSTEM GUIDE 1.
10 Functionality Overview So far, a SME VoIP system has been set up. Next, in this chapter we list what features and functionalities are available in the system. The SME VOIP system supports all traditional and advanced features of most telephony networks. In addition, 3rd party components handle features like voice mail, call forward, conference calls, etc.
10.2 System security support details TLS 1.2 The base station supports TLS 1.
Mutual TLS authentication (mTLS) SIP via TLS with mutual authentication is supported. Mutual authentication towards FWU and Configuration https server is supported. 10.2.6.
SRTP WEB SERVER Will limit number of active calls pr. base when enabled. Embedded web server HTTP OTHER FEATURES QUALITY OF SERVICE IP QUALITY AUTOMATIC DST TONE SCHEME ETHERNET FEATURES SPEED DUPLEX VLAN DHCP SUPPORT STATIC IP TLS 1.2srtp TFTP HTTP HTTPS TCP/IP/UDP SNTP QUALITY OF SERVICE DHCP OPTION DNS SRV DECT DECT CAP CAT-IQ V1.0 GENERAL TELEPHONY HANDSET SUPPORT VOIP ACCOUNTS SIMULTANEOUS CALLS CALL FEATURES SME VOIP SYSTEM GUIDE 1.
CALL LOG PHONE BOOK DND CALL FORWARD SME VOIP SYSTEM GUIDE 1.1 Proprietary and Confidential Multiple calls Call identification Calling Name Identification Presentation (CNIP) Calling Line Identification Presentation (CLIP) Call Hold List of registered handsets 50 mixed between Incoming, outgoing, missed calls Common Phonebook with up to 3000 entries (Import via csv format) Common Phonebook LDAP V2.
Appendix 11 Appendix A: Basic Network Server(s) Configuration In this chapter, we describe how to setup the various server elements in the system. 11.1 Server setup In the network, the server environment is installed as a centralized system. The main server types hosted on the network include SIP, DNS/DHCP and HTTP/TFTP Servers. These servers can be hosted both in one or multiple windows and/or Linux Server environment. Management servers are normally installed to monitor and manage the network in detail.
11.4 DHCP Server Setup A DHCP Server allows diskless clients to connect to a network and automatically obtain an IP address. This server is capable of supplying each network client with an IP address, subnet mask, default gateway, an IP address for a WINS server, and an IP address for a DNS server. This is very often used in enterprise networks to reduce configuration efforts. All IP addresses of all computers/routers/bases are stored in a database that resides on a server machine.
Linux Platform: Troubleshooting DHCP, check the following: 1) Incorrect settings in the /etc/dhcpd.conf file such as not defining the networks for which the DHCP server is responsible; 2) NAT/Firewall rules that block the DHCP bootp protocol on UDP ports 67 and 68; 3) Routers failing to forward the bootp packets to the DHCP server when the clients reside on a separate network. Always check your /var/logs/messages file for dhcpd errors. 4) Finally restart the dhcpd service daemon 11.
Configure the relevant TFTP virtual folder in the server. The TFTP virtual folder is the file folder, visible for TFTP clients under a certain name. You can set security settings separately for every virtual TFTP folder. Next, set rights to access TFTP folders according to the relevant clients. Screenshot 11.6 SIP Server Setup SIP server is one of the main components of a network, dealing with the setup of all SIP calls in the network. A SIP server is also referred to as a SIP Proxy or a Registrar.
12 Appendix B: Using Base with VLAN Network In this chapter, we describe how to setup a typical VLAN in the network. 12.1 Introduction In this chapter, we describe how to setup VLAN to typical network. There are three main stages involved in this procedure: a) Configure a VLAN Aware Switch to a specific (un)tagged VLAN ID, so the system can process untagged frames forwarded to it. b) Setup the Time Server (NTP Server) and other relevant network servers.
12.2 Backbone/ VLAN Aware Switches To implement a VLAN in your network, you must use VLAN-aware switches. Before we continue, let consider two rules to remember regarding the functioning of a regular LAN switch: 1. When the switch receives a broadcast or multicast frame from a port, it floods (or broadcasts) the frame to all other ports on the switch. 2. When the switch receives a unicast frame, it forwards it only to the port to which it is addressed.
12.4 Implementation Cases Common types of usage scenarios for VLANs on typical VLAN switches: port-based VLANs, protocol-based VLANs, and IP subnet-based VLANs. Before figuring out which usage scenario suits your needs, you must understand what each type of usage scenario implies. Port-based VLAN: All frames transmitted by a NIC are tagged using only one VLAN ID. The NIC does not transmit or receive any untagged frames.
STEP 5 Create the relevant SIP server information in the system. Each service provider/customer should refer SIP server vendor on how to setup SIP servers. 12.6 Configure Time Server STEP 6 Navigate to the Time settings and configure it. Scroll on the left column and click on Time url link to Open the Time Settings Page. Enter the relevant parameters on this page and press the Save button. Screenshot SME VOIP SYSTEM GUIDE 1.
12.7 VLAN Setup: Base station STEP 7 Navigate to the Network url > On the network page enter the relevant settings in the VLAN section > VLAN Id should be the same as those configured into the backbone. Screenshot 13 Appendix C: Local Central directory file handling In this appendix, the Local Central Directory file format, import and configuration is described. 13.1 Central Directory Contact List Structure The structure of Contact List is simple.
Txt file limitations: Contact name must NOT be longer than 23 characters (name will be truncated) Contact name must NOT contain “,” Contact number must be limited to 21 digits (entry will be discarded, no warning) Contact number digits must be: +0123456789 Contact number does not support SIP-URI Spaces between name section “,” and number section is not supported 13.2 Central Directory Contact List Filename Format The Contact list is saved as file format: .txt .csv or .xml 13.
Screenshot The figure below shows the import procedure is in process. Screenshot 13.4 Central directory using server Alternative way to import a Contact List is to get it from a server. First click on Management url to get Management Settings page, then select the protocol of your server (TFTP/HTTP/HTTPS) in Management Transfer Protocol, then save the setting by clicking Save.
14 Appendix D: Provisioning. Before provisioning, you should be aware of the file size limit. The Rove B4 base station supports files with size up to 1M. 14.1 Provisioning approaches. There are three ways of configuring the system. 1. Manual configuration by use of the Web server in the base station. 2. By use of configuration files that are uploaded from a disk via the “Configuration” page on the Web server. 3. By use of configuration files which the base station download from a configuration server. 14.
STEP 1 Chose configuration file STEP 2 Press Load to load the file. The base station will now load the file and the settings will be as in the configuration file. 14.4 How to create a configuration file. To create a configuration file, you must use the web server interface and do a full setup, and set all settings as needed. When the base station is setup and ready, go to the configuration page. Screenshot Press Export and save the cfg file. NOTE: You must save the file as “Mac-address name.cfg” (e.
Find the needed setting in the configuration file %CONFIGURATION_DOWNLOAD_CTRL%:0x00 change to %CONFIGURATION_DOWNLOAD_CTRL%:0x01 And %NETWORK_DHCP_CLIENT_BOOT_SERVER %:0x02 change to (default=disabled) %NETWORK_DHCP_CLIENT_BOOT_SERVER %:0x00 = DHCP 66 %NETWORK_DHCP_CLIENT_BOOT_SERVER %:0x01 = Custom %NETWORK_DHCP_CLIENT_BOOT_SERVER %:0x03 = DHCP 66 + Custom Configuration for web server: A given base station is set up to use configurations files on the “Management Settings” page on the Web server.
FCC Warning This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.
by the ISEDC. For body worn operation, this model device has been tested and meets the ISEDC RF exposure guidelines when used with an accessory designated for this product or when used with an accessory that contains no metal. For Base This equipment complies with ISEDC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator & your body.
