IPR Channel VoIP Interface. Product Manual

Transcription

1 IPR400 4-Channel VoIP Interface Product Manual

2 IPR400 4-Channel VoIP Interface Product Manual Omnitronics Pty Ltd. All rights reserved. (ABN: ) Product Notice No part of the contents of this publication may be reproduced or transmitted in any form or by any means without the prior written consent of Omnitronics. Information contained in this document is provided solely to enable use of Omnitronics products. Omnitronics assumes no liability whatsoever for neither technical or editorial errors that may appear in this document nor does it make a commitment to update the information contained herein. Omnitronics retains the right to make changes to this information at any time, without notice. This manual describes features that are common to most installations as well as optional features available separately. Some features may not be available on your installation. Trademarks Microsoft and Windows are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. NGT is a registered trademark of Codan Limited. Freescale and Coldfire are either trademarks or registered trademarks of Freescale Semiconductor. Motorola and SMARTNET are registered trademarks of Motorola, Inc. DX-Altus, IPR400, IPRMon, and RediTALK-Flex are trademarks of Omnitronics Pty Ltd. Technical Support If you require additional information or assistance with installation or configuration of this product, please contact our technical support at the appropriate contact details shown below. When contacting Omnitronics for support, please have your Omnitronics product serial number, system hardware, and system software versions available. Australia (Head Office): Omnitronics Pty Ltd 27 Sarich Court Osborne Park, WA 6017 Australia P: F: support@omnitronics.com.au Documentation Feedback Australia (East Coast): Omnitronics Pty Ltd 301 Coronation Drive Milton, QLD 4064 Australia P: F: support@omnitronics.com.au North America (USA): Omnitronics, Inc S. Harbor City Blvd, Ste #328 Melbourne, FL USA P: +1 (904) F: +1 (904) servicedesk@omnitronicsworld.com Omnitronics welcomes your comments and suggestions. To provide suggestions for improving the Omnitronics documentation, please your comments to documentation@omnitronics.com.au. Please include the Omnitronics product name and version with your correspondence. Omnitronics will carefully consider all feedback for future improvements to Omnitronics documentation and software. Date: December 2018 Document Number: MNL ii

3 Document Revision History Rev Date Description /2010 Original publication /2010 Updated section Feastures Added sections Audible Link Status Alarm and Physical Link Status Alarm. Added list of compatible web browsers to section Connecting to the Network. Updated Resetting to Factory Default Settings. Updated System Version Information /2010 Updated Session Initiation Protocol (SIP) Settings. Added new application examples. Updated Sound to Play setting. Added section VoIP/RTP Group and updated section Session Initiaition Protocol (SIP). Added two examples of radio linking. Corrected cross reference in section Network Address Translation (NAT). Added section Frequently Asked Questions /2010 Updated USA fax number on cover page /2010 Updated Connecting to the Network. Added Connecting with Windows 7. Updated Radio Dispatch Using SIP Connections from IPRdispatch. Added Overview of the IPR400. Updated Viewing the System Status. Added Dynamic DNS. Added Dynamic Domain Name System (Dyanic DNS). Updated Troubleshooting /2011 Updated Connecting with Windows 7. Updated Serial Pas-Trhouhg Mode. Updated "VAD hold/hang time /2011 Updated list of supported radios in Serial Channel-Change Mode /2011 Updated Connecting the IPR400. Updated Hardware Setup. Updated Using the Configuration Interface. Updated Confiuring the Network Settings. Updated Backing Up and Restoring the Configuration. Updated VoIP Conference Mode. Updated Conference Mode Configurations. Added Diagnostics and Upgrading the Firmware. Updated Application Examples. Updated Technical Reference. Updated Trooubleshooting and FAQ. Added Simple Network Management Protocol (SNMP) /2011 Updated Selcall and DTMF Settings /2012 Updated Figure /2012 Updated SNMP Functions Common to all Omnitronics SNMP-Enabled Devices. iii

4 Rev Date Description /2013 Updated Figure 40. Added RTP Mute/PTT Period send disable in VoIP/RTP Settings. Added RTP transmit packet size in VoIP/RTP Settings. Updated the list of supported radios in section Serial Channel-Change Mode /2013 Updated section Serial Channel-Change Mode /2013 Updated Radio Settings. Updated VoIP/RTP Settings. Updated VoIP Conference Mode. Updated Factory Default Addresses. Updated DTMF. Updated Serial Channel-Change Mode. Updated Typical Configuration. Updated Channel Statistics /2014 Added Omnitronics Communication API. Added ATIS Status Information. Updated Simple Network Management Protocol. Updated Radio Settings. Added Capabilities Configuration. Updated SNMP Functions Common to all Omnitronincs SNMP-Enabled Devices /2015 Updated section Session Intiation Protocol (SIP) /2016 Added "IPR400 Audio Inputs". Updated VoIP/RTP Configuration Updated "Serial Monitor". Updated "Resetting to Factory Default Settings". Updated Bandwidth Usage. Updated Specifications. Updated Frequently Asked Questions /2016 Updated Serial Channel-Change Mode. Added Connections. Updated Bandwidth Usage. Updated Specifications /2017 Updated VoIP/RTP Settings. Updated Session Initiation protocol (SIP). Updated Local Linking. Updated Communicating with a DX-Altus Radio Displatch System. Updated Radio Dispatch Using SIP Connections from RediTALK. Updated Network Requirements /2017 Updated Network Settings. Updated "SNMP Functions Common to all Omnitronics SNMP-Enabled Devices". iv

5 Rev Date Description /2018 Updated Viewing the System Status. Updated VoIP/RTP Configuration. Updated Selcall (Selective Calling). Updated Serial Channel-Change Mode. Updated Communicating via Multicasting. Updated SNMP Functions Common to all Omnitronics SNMP-Enabled Devices /2018 Updated What is the IPR400?. Updated Features. Updated Multi-Function LCD. Updated Modes of Operation. Updated Upgrading the Firmware. Updated IPR400 Board Layout and Link Settings. Updated E&M Configuration. Updated Radio/Audio Channel Settings. Updated VoIP/RTP Settings. Updated CTCSS Settings. Updated Technical Reference. Please report any errors or omissions in this document to Omnitronics so that such errors or omissions may be corrected in later issues (see Documentation Feedback on inside front-cover). v

6

7 Contents Introduction 1 What is the IPR400?... 1 IPR IPR400 Series Features... 3 Remote Radio Access... 4 VHF/UHF Link Replacement... 4 Leased Line Replacement... 4 Related Documentation... 5 Documentation Conventions... 5 Using the Built-In Menu System 7 Multi-Function LCD... 7 Using the Menu and Function Buttons... 8 Multi-Level Menu System... 8 Modes of Operation Normal Mode Menu Mode Edit Mode and Changing Settings Resetting to Factory Default Settings Upgrading the Firmware Getting Started 21 IPR400 Audio Inputs IPR400 Board Layout and Link Settings Data Port Connectors Contents vii

8 Radio Port Connectors AUX Connector E&M Configuration M-Lead (PTT) Output Options (using relays) M-Lead (PTT) Output Options (using circuitry) E-Lead (Busy) Input Configuration (using contacts) E-Lead (Busy) Input Configuration (using circuitry) Connecting to the Network Using Windows to Connect Using Mac OS X or Linux to Connect Configuring the IPR What is the Configuration Interface? Using the Configuration Interface Logging On Exiting the Configuration Interface Configuration Interface Configuration Status Saving the Configuration Restarting the IPR400 after Saving the Configuration Resetting the Configuration to Default Settings System Status System Version Information Current Status VoIP Group Status Radio Status SIP Connection Status Dynamic DNS Status Channel Change Status Omnitronics Communication API viii Contents

9 ATIS Status Information RSSI Information Network Configuration Network Settings Dynamic DNS Using a DHCP Server Saving Network Settings Simple Network Management Protocol Site Alarm Limits Radio-Specific Traps Changing the Password Backing up and Restoring the Configuration Backing up the Configuration to a File Restoring the Configuration from a File Radio Configuration Radio/Audio Channel Settings Trunked Radio Audio Delay Mode Audio Level Alignment Examples VoIP/RTP Configuration VoIP/RTP Settings Supported Codecs VoIP Conference Mode Conference Mode Configurations Audible Link Status Alarm Physical Link Status Alarm Remote Addressing Multicast Addressing Factory Default Addresses Internet Port Numbers Selcall and DTMF Settings Contents ix

10 General DTMF Selcall (Selective Calling) Tone Position and Type Example Selcall Configurations CTCSS Settings Tone Detection Local Keying and Tone Transmission Enabled Frequencies CTCSS Talk Off Timeout Serial Data Settings Serial Pass-Through Mode Serial Port Parameters Serial Channel-Change Mode Session Initiation Protocol (SIP) Settings Linking Radio and VoIP Channels Linking Radios with VoIP Linking Radios without VoIP Independent VoIP Access to Radios (No Linking) Independent VoIP Access to Radios (Linking) Shared VoIP Access to Radios (Linking) Local Linking Typical Configuration Capabilities Configuration Omnitronics Communication API Capabilities ATIS Vessel Information Diagnostics and Updating the Firmware 103 IPR400 and Radio Diagnostics x Contents

11 Fault Reporting Using the Diagnostic Report Feature VoIP/Group Diagnostics Connections Statistics Current Status VoIP Group Status Radio Status Channel Statistics Updating the Firmware Site Monitoring of Inputs and Outputs Digital I/O Analog Inputs Serial Monitor 115 About the Serial Monitor Serial Communications Setup Recovery Mode Using the Serial Monitor Resetting to Factory Default Settings Application Examples 121 Connecting Radios via ADSL and Internet Configuring the Network Connecting via ADSL and the Internet with Dynamic DNS Remote Radio Access Using Static Addressing (VPN or LAN) Line Replacement Using VOX Communicating with a DX-Altus Radio Dispatch System Radio Dispatch Using SIP Connections from 960SIP Radio Dispatch Using SIP Connections from RediTALK-Flex Communicating via Multicasting Communicating via Conferencing Contents xi

12 Radio Linked to One VoIP Group with Link Failure Radio Linked to Several VoIP Groups with Link Failure Technical Reference 147 Network Requirements Encryption IP Addressing Multicast Addressing Domain Name System (DNS) Multicast Domain Name System (mdns) Dynamic Addressing Dynamic DNS Implementation Compatibility Configuration Network Address Translation (NAT) VoIP Functionality Real Time Protocol (RTP) Signaling with RTP VoIP/RTP Group Session Initiation Protocol (SIP) SIP URI VoIP Channel Linking Simple Network Management Protocol (SNMP) About SNMP SNMP Functions Common to Omnitronics SNMP-Enabled Devices IPR400 Device-Specific SNMP Functions Other Useful SNMP Functions Specifications Notice of Compliance xii Contents

13 Troubleshooting and FAQ 171 General Problems Cannot Access the Configuration Interface IPR400 Continually Restarts VoIP Links Not Maintaining Connection Audio Problems Cannot Hear Audio from Other Devices Radio Does Not Transmit Audio is Echoed Back from the Remote End Frequently Asked Questions Glossary 177 Index 181 Contents xiii

14

15 Introduction This manual provides information about installing, configuring, and troubleshooting the IPR400 Four-Channel VoIP Interface product. What is the IPR400? The IPR400 product belongs to the Omnitronics IPR series of products, and is a full featured, flexible four-port Radio-Over-IP Gateway. It is designed to provide Voice- Over-IP extensions for analog radio equipment and to facilitate interoperability between disparate radio systems such as UHF, VHF, HF, and trunked radio systems. The IPR400 product supports up to four VoIP channels that can be mapped to multiple radio channels. This provides the means to link together groups of radios and VoIP channels in a myriad of combinations, making the device ideal for connecting repeater sites and accessing those sites from dispatch consoles. The IPR400 is designed to make efficient use of the IP bandwidth and to minimise the impact on corporate networks. It provides the following capabilities: Transport of RS-232 serial data Secure voice communications using encryption Site monitoring and error reporting via Simple Network Management Protocol (SNMP) Using the IPR400, system integrators can configure powerful and flexible interoperable radio networks. The product now comes in two versions: the standard version (IPR400) and the enhanced version (IPR400 Series-2). IPR400 Product Manual 1

16 IPR400 The front panel of the IPR400 provides a Link indicator, a back-lit LCD, menu buttons for navigating the display, an Ethernet connector for interfacing to the network, and an RS-232 serial port for debugging and local configuration. Ethernet connector Link indicator Down button Up button MENU button Serial Monitor Multi-function LCD The back panel of the IPR400 provides power connectors, connectors for data ports, connectors for 4-wire E&M ports, and an auxiliary connector. Power DCE 1 to DCE 4 RS232 data ports RADIO 1 to RADIO 4 4-wire E&M ports AUX IPR400 Series-2 The front panel of the IPR400 Series-2 provides status indicators, a back-lit multifunction LCD, a MENU rotary push-button (encoder) for navigating the display, an Ethernet connector for interfacing to the network, and a USB port for debugging and local configuration. Ethernet connector USB Serial LED VoIP Link LED Run LED MENU button Multi-function LCD The back panel of the IPR400 provides power connectors, connectors for data ports, connectors for 4-wire E&M ports, and an auxiliary connector. Power DCE 1 to DCE 4 RS232 data ports RADIO 1 to RADIO 4 4-wire E&M ports AUX 2 Introduction

17 Features A key feature of the IPR400 device is its ability to reliably transport ANI (automatic number identification) signalling schemes over IP using data compression techniques. Analog signalling schemes such as selcall (selective calling) and DTMF will not pass directly through a data network when audio is compressed below 64kbps. Compression algorithms tend to degrade audio tones resulting in poor decoding of the reconstructed signal. Additionally, lost packets (normally undetectable for voice) will also degrade tone reliability. The IPR400 overcomes these problems by directly decoding analog selcall and DTMF tones, encoding them into data messages, then transferring the messages across the IP network, and reconstructing the signalling scheme at the remote end. Each of the four radio ports provides an 8P8C modular connector for four-wire audio and E&M signalling. The ports are balanced with 600-ohm transformer coupling. This provides isolation between the IPR400 and a radio and virtually eliminates ground noise and induced signals. The E&M signalling provides isolation and can be configured for relay control or opto (voltage) input/output. Links (accessible from the rear panel) allow the PTT and COS signals to be configured to source or sink power. Radio audio is converted into digital data via a hardware codec and can be further compressed via software codecs an on-board DSP allows further compression down to 13kbps using a GSM-compliant algorithm. The audio is then transported over IP. The DSP also provides VAD (voice activity detection) and silence suppression. When used together, these features allow the IPR400 to make optimal use of the available IP bandwidth. With VAD and silence suppression, audio packets are generated only whilst a person is actually speaking. VAD is also useful when connecting to end equipment that does not provide a COS or Mute output such as HF radio where it performs a voice-operated keying function. The IPR400 provides the following features and benefits: Powered from a 12VDC plug pack 1A regulated) or 24V supply Easy to configure using built-in configuration interface or via the serial port Selcall (maximum of 20 tones) and DTMF signaling over highly compressed links and when using voice compression Multi-drop capability for operator handsets VoIP using multicasting and several codecs 10/100-BaseT Ethernet port via RJ-45 connector E&M signals with the same pin-out as Omnitronics 619 Audio Bridges Isolated PTT control using relay contacts Isolated COS input using an opto-coupler Voice Activity Detection (VAD) with silence suppression Software attenuation of radio port levels IPR400 Product Manual 3

18 Built-in selcall and DTMF transceivers Communicates with MPT (multiport) transceivers via RS-232 port Multi-function LCD on front panel displays activity and diagnostics Flash programmable over IP Static or dynamic IP address configuration Voice encryption 12 (IPR400) or 48 (IPR400 Series-2) simultaneous inbound SIP connections (from Omnitronics IPR devices) over four VoIP groups Radio channel change via RS232 Removes the need for expensive leased lines or radio links Interfaces to radios that do not provide a COS output IP bandwidth optimisation Provides secure communications Interfaces to Motorola SMARTNET analog trunked radios via audio delay Remote Radio Access An operator can control and monitor remote transceivers across a Local Area Network or a Wide Area Network. The transmit and receive audio, along with the PTT and Busy/COS signals, are transported over the link transparently using VoIP multicasting and unicasting techniques (which is actually the most common form). Selcall and DTMF are also transported reliably regardless of the level of compression. VHF/UHF Link Replacement The IPR400 allows you to connect transceivers back-to-back over an IP link. Typically, you can interconnect two repeater sites over a Wide Area Network. The IPR400 transports PTT and COS signals over the link as data messages. The IPR400 provides a configurable PTT output to a radio. It will also accept a configurable COS input from a radio. An active COS signal from a radio will enable the transmission of voice packets over the IP network and generate a PTT output at the opposite end. The IPR400 supports full duplex operation. Leased Line Replacement Audio devices, such as 4-wire audio bearers, can be connected back-to-back over an IP link. Since the communications equipment will not provide a COS output, a VOX function is implemented in the IPR400 using the VAD feature. When the IPR400 detects a voice signal at the radio port, it transmits an internal COS signal to the destination IPR400. This will also enable the transmission of voice packets over the IP network. A hang period is automatically applied to the VOX algorithm. Full-duplex operation is supported. 4 Introduction

19 Related Documentation In addition to this manual, the following documents define the relevant protocols implemented in the IPR400 product, which are all available in the form of RFC documents from the Internet Engineering Task Force (IETF): RFC RTP: A Transport Protocol for Real-Time Applications RFC RTP Profile for Audio and Video Conferences with Minimal Control RFC RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals RFC SIP: Session Initiation Protocol RFC Offer/Answer Model with Session Description Protocol (SDP) RFC SDP : Session Description Protocol The following books provide related information: Camarillo, Gonzalo. SIP Demystified. McGraw Hill, ISBN Perkins, Colin. RTP: Audio and Video for the Internet. Addison Wesley, ISBN Documentation Conventions The following documentation conventions are used in this manual. Convention Blue, underlined text: Bold text Italic text Italic narrow text Italic text in quotation marks: see What is the IPR400? on page 1 Monospace text Description Website addresses and addresses Keys presses, text typed into a UI element, such as a text box, UI elements clicked or selected, such as menu and list items, buttons, tabs, and check boxes. Text emphasis. File and directory names. Hyperlinked cross-references to other sections or paragraphs within the document. System output, configuration examples, commands and arguments. IPR400 Product Manual 5

20

21 Using the Built-In Menu System This chapter includes an overview of the IPR400, and includes the following sections: Multi-Function LCD Using the Menu and Function Buttons on page 8 Multi-Level Menu System on page 8 Modes of Operation on page 10 Resetting to Factory Default Settings on page 19 Upgrading the Firmware on page 19 Multi-Function LCD Located on the front panel of the IPR400 is the 2 by 16-character back-lit dot-matrix LCD. It displays the current status of the inputs and outputs, and allows you to access the multi-level menu system for displaying the configuration settings of the IPR400. The IPR400 Series-2 also allows you to change the settings. When power is applied, the IPR400 loads its configuration from Flash memory and performs various startup and initialization functions. At start-up, the IPR400 bootloader loads and runs the firmware, which in turn, loads the configuration settings from Flash memory. The firmware version of the loader is displayed for several seconds followed by the firmware version of the VoIP module, as shown in Figure 1. Figure 1. Messages shown on the LCD at startup When the IPR400 is ready for normal operation, the status of the Mute (Busy), PTT, and VoIP channels for each port is displayed on the LCD: this is the normal operational mode of the IPR400. You use Menu mode for displaying and editing the configuration settings. You can also transmit test tones for calibrating equipment. IPR400 Product Manual 7

22 Using the Menu and Function Buttons (IPR400 only) To navigate the menu system and change configuration settings on the IPR400, you use the MENU and FUNCTION push-buttons on the front panel. Menu & Function buttons Press Press Press Function In Normal mode, MENU button to enter Menu mode. In Menu mode, navigates up one level in the menu structure; or exits menu mode from the top-level menu. In Menu mode, navigates to the next menu item at the current level; or navigates back to the higher-level menu item when displaying a setting. In Normal mode, toggles the LCD backlight on or off. In Menu mode, navigates down one level or navigates up one level when displaying the value of a setting. (IPR400 Series-2 only) To navigate the menu system and change configuration settings on the IPR400 Series-2, you use the MENU rotary push-button encoder on the front panel. Menu button Press Press and hold for one second Rotate one-click clockwise Rotate one-click anticlockwise Function In Normal mode, enters Menu mode. In Menu mode, navigates down one level or selects Edit mode to change a configuration setting. In Menu mode, navigates up one level. In Edit mode, accepts the selected configuration setting. In Normal mode, turns LCD backlight on. In Menu mode, navigates to the menu item to the right at the current level. In Edit mode, increments the value of the selected setting. In Normal mode, turns LCD backlight off. In Menu mode, navigates to the menu item to the left at current level. In Edit mode, decrements the value of the selected setting. Multi-Level Menu System The IPR400 provides a sophisticated menu system with a multi-level structure, as depicted in Figure 2. At power up (A), the IPR400 displays the revision of firmware, and after about 2 seconds, the Mute, PTT, and VoIP ports will be displayed (B). The IPR400 is now in the Normal mode of operation. In this mode, when any of the Mute inputs or PTT outputs on a port changes state or VoIP activity changes on a port, it will appear on the display. This provides immediate visual indication of activity on the ports (channels). Pressing the MENU button enters Menu mode (see Menu Mode on page 11) and displays the Audio Functions menu (C). 8 Using the Built-In Menu System

23 IPR400 Product Manual 9 Figure 2. IPR400 multi-level menu structure

24 Figure 3 illustrates how to navigate the menu system. For the IPR400, you use the MENU and FUNCTION push-buttons, and for the IPR400 Series-2, you use MENU rotary push-button encoder (see Using the Menu and Function Buttons on page 8). You can configure most of the settings using the built-in menu system (excludes the advanced network functions, selcall parameters, and the VOX settings). Figure 3. Navigating the menu system Modes of Operation The IPR400 provides several modes of operation: Normal mode is for normal operation of the IPR400. It displays the operational status of the MUTE (busy) inputs, the PTT outputs, and the VoIP activity for each port (channel). The IPR400 operates in this mode for most of the time. Menu mode is for navigating the menu system and displaying the configuration settings. You can also transmit test tones in this mode. Change to this mode by pressing the MENU button. You use the FUNCTION push-buttons (IPR400 only) or the MENU rotary push-button (IPR400 Series-2 only) on the front panel to navigate the menu system (see Menu Mode on page 11). Edit mode (IPR400 Series-2 only) is for changing the value of a configuration setting (see Edit Mode and Changing Settings on page 18). Change to this mode by pressing the MENU button when displaying the value of a setting you want to change. Normal Mode In the normal mode, the LCD shows the state of each of the four ports for the (busy) input, the output, and the ports on which activity is present, as shown in Figure Using the Built-In Menu System

25 Figure 4. LCD in normal operation When a port is active, the digit is displayed; and when it is inactive, the digit is displayed for the corresponding port. In this example, a mute (busy) input is detected on port 2, a PTT is active on port3, and VoIP activity is present on ports 1 and 4. In this mode, you can use the backlight to illuminate the display to make it easier to read in low-light environments: (IPR400 only) Press the button to switch the LCD backlight on or off. (IPR400 Series-2 only) Rotate the MENU button one-click clockwise to switch the backlight on or rotate it one-click anticlockwise to turn it off. Alternatively, you can set the option to ON (backlight is permanently ON) or to AUTO (backlight turns OFF automatically after 5 seconds of non-use). Menu Mode Use Menu mode to navigate the menu system and display the configuration settings. Note Menu mode will timeout after 5 seconds of non-use and the LCD will then revert to Normal mode. To enter and exit menu mode 1 While in normal mode, press the MENU button to enter menu mode. is the first top-level menu displayed. 2 To display to the next menu at the same level, press the button (for the IPR400) or rotate the MENU button one-click clockwise (IPR400 Series-2). 3 (IPR400 Series-2 only) To display the previous menu at the same level, rotate the MENU button one-click anticlockwise. IPR400 Product Manual 11

26 The menu wraps-around so that if you press the button (IPR400 only) again, or rotate the MENU button in the same direction (IPR400 Series-2 only), the menu will move to the next menu (IPR400 only) or move in the direction of rotation (IPR400 Series-2 only). 4 To exit menu mode and return to normal mode, press the MENU button (IPR400 only), or press and hold the MENU button for about one second (IPR400 Series-2 only). Note You can exit menu mode and return to normal operation from the top-level menus only. Displaying the Receive Level of a Channel Figure 5 shows how to use the menu system to display the receive level for a particular channel. Figure 5. Displaying the receive level for a channel 12 Using the Built-In Menu System

27 To display the receive level for channel 1 While in Normal mode, press the MENU button to enter Menu mode. is the first top-level menu displayed. Note If you do not press a FUNCTION button (IPR400 only) within 5 seconds after pressing the MENU button, or while navigating the toplevel menus, the display will revert to normal mode. 2 Press the button (for the IPR400) or press the MENU button (IPR400 Series-2) to navigate down one level to the menu. 3 Press the button (IPR400), or press the MENU button (IPR400 Series-2), to navigate down one level to the item for. 4 Press the button (IPR400), or press the Menu button (IPR400 Series-2), to display the Receive Level for the selected channel. 5 To return to the top-level menu, press the MENU button three times (IPR400), or press and hold the MENU button three times (IPR400 Series-2). 6 To exit Menu mode, press the MENU button (IPR400) or press and hold the MENU button (IPR400 Series-2) once more to return to normal operation. IPR400 Product Manual 13

28 Displaying the Transmit Level of a Channel Figure 6 shows how to use the menu system to display the transmit level for a particular channel. Figure 6. Displaying the transmit level for a channel To display the transmit level for a channel 1 While in normal mode, press the MENU button to enter Menu mode. is the first top-level menu displayed. Note If you do not press a FUNCTION button (IPR400 only) within 5 seconds after pressing the MENU button, or while navigating the toplevel menus, the display will revert to normal mode. 2 Press the button (IPR400), or press the MENU button (IPR400 Series-2), to navigate down one level to the menu. 14 Using the Built-In Menu System

29 3 Press the button (IPR400) or rotate the MENU button one-click clockwise (IPR400 Series-2) to display the menu. 4 Press the button (IPR400), or press the MENU button (IPR400 Series-2), to navigate down one level to display the item for. 5 (Optional) Press the button (IPR400) one or more times, or rotate the MENU button one or more clicks clockwise (IPR400 Series-2), to select the channel you want to display. 6 Press the button (IPR400), or press the MENU button (IPR400 Series-2), to display the Transmit Level for the selected channel. 7 To return to the top-level menu, press the MENU button three times (IPR400), or press and hold the MENU button three times (IPR400 Series-2). 8 To exit Menu mode, press the MENU button (IPR400) or press and hold the MENU button (IPR400 Series-2). IPR400 Product Manual 15

30 Displaying the Network Settings of the IPR400 Figure 7 shows how to use the menu system to display the and other network settings. Figure 7. Displaying the IP Address To display the network settings 1 While in normal mode, press the MENU button to enter menu mode. is the first top-level menu displayed. Note If you do not press a FUNCTION button (IPR400 only) within 5 seconds after pressing the MENU button, or while navigating the toplevel menus, the display will revert to normal mode. 2 Press the button (IPR400) or rotate the MENU button one-click clockwise (IPR400 Series-2) to display the menu. 3 Press the button (IPR400), or press the MENU button (IPR400 Series-2), to navigate down one level to display the item. 16 Using the Built-In Menu System

31 4 Press the button (IPR400), or press the MENU button (IPR400 Series-2), to display. 5 To display the other network settings, press the MENU button (IPR400), or press and hold the MENU button for one second (IPR400 Series-2), to navigate up one level to the item. 6 Press the button (IPR400), or rotate the MENU button one-click clockwise (IPR400 Series-2), to display the next network setting. Note For the IPR400 Series-2, you can also rotate the MENU button anticlockwise to show the previous menu item. 7 Press the button (IPR400), or press the MENU button (IPR400 Series-2), to display the setting for the selected item. 8 To return to the top-level menu, press the MENU button two times (IPR400) or press and hold the MENU button two times (IPR400 Series-2). 9 To exit Menu mode, press the MENU button (IPR400) or press and hold the MENU button (IPR400 Series-2) once more to return to normal operation. IPR400 Product Manual 17

32 Edit Mode and Changing Settings Once you have selected the setting you want to change, press the MENU button to enter edit mode. In edit mode, the setting blinks to indicate you can change the value. Rotate the MENU button clockwise to increase the value or rotate it anticlockwise to decrease the value. Note Edit mode is supported only in the IPR400 Series-2. To change the settings in the IPR400, use the web-based configuration interface. To edit a setting 1 In menu mode, use the menu system to display the setting you want change. 2 Press the MENU button to enter edit mode. The setting blinks (shown in bold below) to indicate you can edit the value. 3 Do one of the following: Rotate the MENU button one or more clicks clockwise to increment the value. Rotate the MENU button one or more clicks anticlockwise to decrement the value. 4 To accept the new value, press and hold the MENU button for about one second. An asterisk (*) appears at the start of the second line to indicate that the setting has changed. If the setting comprises several editable values, such as an IP address, the edit point will move to the next value and it will start to blink (shown in bold below). 18 Using the Built-In Menu System

33 5 (Optional) To edit the remaining values of a multi-value setting (such as an IP address), repeat steps 3 and 4. 6 To save the setting, press and hold the MENU button for about one second. The value of the setting is saved to the configuration. Resetting to Factory Default Settings You can reset the IPR400 configuration to factory defaults. This is useful when it fails to start up properly due to a configuration error (e.g., inconsistent network settings). To reset the IPR400 to default settings 1 Disconnect the power to the IPR Wait for several seconds, and then press and hold the MENU button. 3 Continue to press and hold the MENU button and apply power to the IPR Continue to press and hold the MENU button for about 20 seconds while the IPR400 completes its start-up sequence. The IPR400 should display the following messages as the configuration is reset to factory default settings. Upgrading the Firmware Omnitronics periodically provides upgrades to the firmware to resolve issues or to provide enhancements and additional functionality. Using the built-in configuration interface, you can easily upgrade the firmware when a new version becomes available (see Updating the Firmware on page 111). Figure 8 shows the messages that appear on the LCD when upgrading the firmware using the configuration interface. Firmware update Firmware update IPR400 is restarting in progress (waiting for user to click Restart on Firmware Upgrade page) Figure 8. Messages shown on the LCD when updating the firmware IPR400 Product Manual 19

34

35 Getting Started This chapter discusses the hardware requirements of the IPR400 and includes the following sections: IPR400 Audio Inputs on page 21 IPR400 Board Layout and Link Settings on page 22 Data Port Connectors on page 26 Radio Port Connectors on page 26 AUX Connector on page 26 E&M Configuration on page 27 Connecting to the Network on page 32 IPR400 Audio Inputs The IPR400 hardware is designed for 600-ohm balanced audio inputs, but can be modified for high-impedance inputs by performing a simple hardware modification. Each audio channel operates independently of the other channels so you can have a combination of 600-ohm channels and high-impedance channels depending on the peripheral equipment attached to the inputs. Note The modification to support high-impedance audio inputs is only applicable to hardware revisions 1.60 onwards and should only be done by a qualified technician otherwise you may void the warranty. Modification of the hardware comprises cutting one or more of the audio-input solder links. Each link connects a 600-ohm resistor to the input transformer on that channel. Cutting the solder link removes the resistor from the circuit converting the input to a high-impedance input. These solder links are located on the top side of the PC board, as illustrated in Figure 9. SL17 Channel 1 SL18 Channel 2 SL19 Channel 3 SL20 Channel 4 Figure 9. Location of solder links on the top side of PC board IPR400 Product Manual 21

36 To convert an input to a high-impedance input, carefully cut the corresponding track between the two square solder-link pads. This removes the 600-ohm resistor from the audio input making it a high-impedance input. After cutting the track, you can test the input as follows: Send audio from the input to another VoIP device and check the output; or Use the Diagnostics Radio page to enable audio loop-back mode on the channel and check the audio is present at the output of the same channel. IPR400 Board Layout and Link Settings Figure 10 shows the IPR400 main board with an exploded view of the E&M links. Note The IPR400 Series-2 does not provide E&M links, as the operation of the E&M ports is configured using the configuration interface. Figure 10. IPR400 board layout with exploded view of links Figure 11 illustrates the location of pin1 on header links, solder links, and E&M links. Pin 1 on header links is labeled with 1 printed on the PCB and is located adjacent to the square pad. Pin 1 on solder links is identified by semicircle pad. The E&M link numbering is labelled on the rear panel Figure 11. Identifying pin 1 on headers, solder links, and E&M links 22 Getting Started

37 To access the E&M links (IPR400 only), remove the cover on the rear panel as shown in Figure 12 (use a 3mm Allen key to remove the three screws A, B, and C). Once you have configured the E&M links, secure the cover back in position with the three screws. A B C RADIO 1 RADIO 4 4-Wire E&M Radio Ports (Remove cover to access E&M links) Figure 12. Rear panel of IPR400 Table 1 lists the links for RADIO 1, RADIO 2, RADIO 3, and RADIO 4 located on the rear panel. These links provide the E&M connections for interfacing to external radio equipment. Factory default settings are shown in bold type. Table 1. IPR400 E&M link settings for RADIO 1 to RADIO 4 ports Link Setting Description A Out A voltage of +5V to +30V on pins 7 & 8 of the Radio Port connector B 1-2 will turn the radio port busy input on. A 1-2 A closed contact on pins 7 & 8 of the Radio Port connector will turn the B 2-3 radio port busy input on. A 1-2 An external switched ground on pin 8 of the Radio Port connector will B Out turn the radio port busy input on (pin 7 is left disconnected). A 2-3 An external switched voltage between +5V and +30V on pin 8 of the B Out Radio Port connector will turn the radio port busy input on (pin 7 is left disconnected). C 2-3 The Radio Port PTT output has voltage free contacts on pins 1 & 2 of D OUT the Radio Port connector. C 1-2 The Radio Port PTT output is a voltage output from IPR400 with +10 V on D 1-2 pin 1 and 0 V on pin 2 of the Radio Port connector. C 2-3 The radio port PTT output is a switched ground. An external voltage is D 1-2 connected to the 0 V of the IPR400 on pin 1 of the Radio Port connector. Pin 2 of the Radio Port connector must be left disconnected. C 1-2 The radio port PTT output is switched power. +10 V is supplied on pin 1 D OUT of the Radio Port connector. Pin 2 of the Radio Port connector must be left disconnected. The IPR400 provides two auxiliary relays (AUX 1 and AUX2) that can be configured via links to provide voltage-free contacts, switched ground, or switched power on the AUX connector located on the back panel. Table 2 and Table 3 show the link configurations for AUX 1 and AUX 2 relays. IPR400 Product Manual 23

38 Table 2. IPR400 link settings for AUX 1 relay Link Setting Description LK5 Out Auxiliary relay 1 supplies voltage free contacts between pins 3 and LK7 Out 15 of the Auxiliary DB25 connector. LK5 1-2 Auxiliary relay 1 outputs a switched ground. An external voltage is LK7 2-3 connected to the 0V of the IPR400. Either pin 3 or 15 of the Auxiliary DB25 connector can be used. LK5 Out Auxiliary relay 1 outputs switched power. +10V is supplied on pin 3 and LK of the Auxiliary DB25 connector. Table 3. IPR400 link settings for AUX 2 relay Link Setting Description LK3 Out Auxiliary relay 2 supplies voltage free contacts between pins 2 and LK4 Out 14 of the Auxiliary DB25 connector. LK3 1-2 Auxiliary relay 2 outputs a switched ground. An external voltage is LK4 2-3 connected to the 0V of the IPR400. Either pin 2 or 14 of the Auxiliary DB25 connector can be used. LK3 Out Auxiliary relay 2 outputs switched power. +10 V is supplied on pin 2 and LK of the Auxiliary DB25 connector. The opto-isolators 1 and 2 can be configured via links to be controlled by certain pins on the AUX connector located on the back panel. Table 4 and Table 5 show the link configurations for these opto-isolators. Table 4. IPR400 link settings for auxiliary optical isolator 1 Link Setting Description LK A voltage between +5 V and +30 V between pins 4 and 16 of the LK14 Out Auxiliary DB25 connector will turn the auxiliary optical isolator 1 input on. LK A closed contact between pins 4 and 16 of the Auxiliary DB25 LK connector will turn the auxiliary optical isolator 1 input on. LK13 Out An external switched ground on pin 4 of the Auxiliary DB25 connector LK will turn the auxiliary optical isolator 1 input on. Pin 16 is left open. LK13 Out An external switched voltage between +5 V and +30 V on pin 4 of the LK Auxiliary DB25 connector will turn the auxiliary optical isolator 1 input on. Pin 16 is left open. 24 Getting Started

39 Table 5. IPR400 link settings for auxiliary optical isolator 2 Link Setting Description LK A voltage between +5 V and +30 V between pins 5 and 17 of the LK12 Out Auxiliary DB25 connector will turn the auxiliary optical isolator 2 input on. LK A closed contact between pins 5 and 17 of the Auxiliary DB25 connector LK will turn the auxiliary optical isolator 2 input on. LK10 Out An external switched ground on pin 5 of the Auxiliary DB25 connector LK will turn the auxiliary optical isolator 2 input on. Pin 17 is left open. LK10 Out An external switched voltage between +5 V and +30 V on pin 5 of the LK Auxiliary DB25 connector will turn the auxiliary optical isolator 2 input on. Pin 17 is left open. The operation of the ADC can be configured via links. Table 6 shows the link configurations for the ADC. Table 6. IPR400 link settings for ADC Link Setting Description LK Connects the analog to digital converter processor interrupt line for normal operation. LK Connects the analog to digital converter processor interrupt line for programming. LK Connects the analog to digital converter processor clock line for normal operation. LK Connects the analog to digital converter processor clock line for programming. LK Connects the analog to digital converter input 1 line for normal operation. LK Connects the analog to digital converter input 1 line for programming. LK Connects the analog to digital converter input 2 line for normal operation. LK Connects the analog to digital converter input 2 line for programming. LK Connects the analog to digital converter input 3 line for normal operation. LK Connects the analog to digital converter input 3 line for programming. LK Connects the analog to digital converter input 4 line for normal operation. LK Connects the analog to digital converter input 4 line for programming. LK Selects voltage divider for analog to digital converter for 12V. LK Selects voltage divider for analog to digital converter for 24V. IPR400 Product Manual 25

40 Table 7 shows the links reserved for future enhancement. Table 7. IPR400 reserved link settings Link Setting Description LK31 Out Reserved for future enhancements LK32 Out Reserved for future enhancements LK33 Out 1.5V supply for processor emulator Data Port Connectors The pin numbering and assignment for the DB9 data connectors DCE 1 to DCE 4 located on the back panel of the enclosure is shown in Figure 13. Note that these connectors are wired as DCE GND TD RD DB9 (at rear of enclosure) RTS CTS Figure 13. Pin assignment of DCE serial data connectors Radio Port Connectors The pin assignment for the Radio Port connectors is shown in Figure Radio Ports (4 wire E & M) Pin 1 PTT 1a Pin 2 PTT 1b Pin 3 TX 1a Pin 4 RX 1a Pin 5 RX 1b Pin 6 TX 1b Pin 7 Mute 1a Pin 8 Mute 1b Figure 14. Pin assignment of the Radio Port connectors AUX Connector The pin numbering for the DB25 AUX male connector is shown in Figure 15. DB25 (AUX) Figure 15. DB25 AUX connector 26 Getting Started

41 The pin assignments of the AUX (DB25) connector located on the back panel and the corresponding pins on the on-board header CN1 are listed in Table 8. Table 8. DB25 connector (AUX) pin assignments AUX Connector Header CN1 Pin V Description 14 2 Auxiliary relay 2 contact Auxiliary relay 2 contact Auxiliary relay 1 contact Auxiliary relay 1 contact Auxiliary optical isolator 2 common input 4 7 Auxiliary optical isolator 2 DC input 17 8 Auxiliary optical isolator 1 common input 5 9 Auxiliary optical isolator 1 DC input Analog input Analog input Analog input Analog input Analog input Analog input Analog input Analog input CTCSS input CTCSS input CTCSS input CTCSS input CTCSS output CTCSS output CTCSS output CTCSS output 1 NA 26 Not connected E&M Configuration The following sections show how the E&M ports of the IPR400 can be interfaced to various types of equipment using relay contacts and typical circuitry. The examples shown on the following pages apply to Radio Channel 1. Note Hardware configuration of 4-wire E&M ports is only applicable to the standard IPR400: the IPR400 Series-2 uses software configuration of the 4-wire E&M ports. IPR400 Product Manual 27

42 M-Lead (PTT) Output Options (using relays) The link settings for the M-Lead (PTT) output options are configured using links C and D, as shown in Figure 16. Figure 16. M-Lead (PTT) output options using relays Warning! Incorrect link settings can connect the external supply to ground causing damage to the equipment. 28 Getting Started

43 M-Lead (PTT) Output Options (using circuitry) Figure 17 shows the typical circuitry used for the options available for the M-Lead (PTT) output. Figure 17. M-Lead (PTT) output options with typical circuitry Warning! Incorrect link settings can connect the external supply to ground causing damage to the equipment. IPR400 Product Manual 29

44 E-Lead (Busy) Input Configuration (using contacts) The options available for the E-Lead (Busy) inputs are configured using links A and B, as shown in Figure 18. Figure 18. E-Lead (Mute) configuration using contacts Warning! Incorrect link settings can connect the external supply to ground causing damage to the equipment. 30 Getting Started

45 E-Lead (Busy) Input Configuration (using circuitry) Figure 19 shows the typical circuitry used for the options available for the E-Lead (Busy) input. Figure 19. E-Lead (Mute) configuration options using typical circuitry Warning! Incorrect link settings can connect the external supply to ground causing damage to the equipment. IPR400 Product Manual 31

46 Connecting to the Network The IPR400 includes a built-in web server that provides a configuration and management interface called the configuration interface. However, before you can access this web-based interface, you need to ensure that your computer and the IPR400 product are both using compatible IP addresses. If the IP address of your computer does not have a similar address (e.g. the IP subnets are different), it will not be able to communicate with an IPR400 that is using the factory default address. IPR400 products leave the factory configured with one of two possible IP addresses: for devices with an even-numbered serial number for devices with an odd-numbered serial number If the IP address of your computer does not have a similar address (i.e., an IP address starting with xxx), you will need to temporarily change the IP address of your computer to a compatible address before it can connect to the IPR400 by following the steps in the procedure below that is applicable to your operating system. The recommended method of connecting the IPR400 and a computer via an Ethernet network is to use an Ethernet switch or router. However, for the purpose of connecting a factory default IPR400 for the first time, you can connect the computer directly to the IPR400 using an Ethernet network cable you do not need to use a cross-over cable as the Ethernet port is MDIX compatible and can auto-detect the line condition. You can then access the configuration interface and configure the network settings of the IPR400 to match your network. The Ethernet port is located on the front panel of the IPR400. When connecting the Ethernet cable from the IPR400 to the Ethernet switch or router, the Link indicator on the front panel will illuminate. If this indicator does not illuminate, it may be indicative of a problem with the network cable; and the computer will not be able to communicate with the IPR400 until you correct the problem. This indicator will blink whenever the IPR400 detects activity on the network. 32 Getting Started

47 Using Windows to Connect This section contains basic information to help get your IPR400 up and running quickly using Microsoft Windows. The screenshots are from Windows 7, but the same steps apply to Windows 8/8.1/10. All settings of the IPR400 can be set using the built-in web server, which provides a sophisticated and easy-to-use configuration interface. However, before you can access the configuration interface, you must ensure that your computer and the IPR400 device are both using compatible IP addresses. If the IP address of your computer does not have a compatible address (e.g. the IP subnets are different), it will not be able communicate with an IPR400 that is using the factory-default address. All IPR400 devices leave the factory configured with one of two possible IP addresses: for devices with an even-numbered serial number for devices with an odd-numbered serial number If the IP address of your computer does not have a compatible address (that is, an IP address starting with x), you will need to temporarily change the IP address of your computer before it can connect to the IPR400 by following the steps below. Note To change the IP address of your computer, you must be logged in with a user account that has administrator priviledges. Step 1: Determine the IP address of your computer You can determine the address of your computer by following the procedure below. To determine the IP address of your computer 1 On the Start menu, click Control Panel. 2 Click Network and Internet. IPR400 Product Manual 33

48 3 On the Network and Internet window, click Network and Sharing Center. 4 Under View your active networks, click Local Area Connection to open the Local Area Connection Status dialog. 5 Click Details to display the Network Connection Details dialog. 34 Getting Started

49 The Network Connection Details shows the various settings for the network. The settings of interest are the IPv4 IP Address, the IPv4 Subnet Mask and the IPv4 Default Gateway. 6 Record the details for IPv4 IP Address, IPv4 Subnet Mask, and IPv4 Default Gateway from the Network Connection Details, then and click Close. Step 2: Change the IP settings of your computer Before you can connect to the IPR400, you need to temporarily change the IP settings of your computer to match the IP settings of the IPR400. If the IPv4 Address of your computer (see Step 1: Determine the IP address of your computer on page 33) starts with the numbers and the IPv4 Subnet Mask is , your computer is using a compatible IP address and it will be able to communicate with the IPR400 without any changes to its IP settings. In this case, you can skip to Step 3: Connect the IPR400 to the computer on page 36. However, if the IPv4 Address of your computer does not start with the numbers , it will be necessary to temporarily change the IP address of your computer. Important Ensure you record the current IP settings so that you can restore your computer to its original configuration after you have finished configuring the IPR400 device. To configure the IP settings on your computer 1 In the Local Area Connection Status dialog, click Properties. IPR400 Product Manual 35

50 The Local Area Connection Properties dialog is displayed. 2 In the This connection uses the following items list, select Internet Protocol Version 4(TCP/IPv4), and then click Properties. The Internet Protocol Version 4 (TCP/IPv4) Properties dialog is displayed. 3 Under the General tab, select Use the following IP address and enter the following details: IP address is the static IP address you want to assign to your computer. Subnet mask is the subnet mask used by your router. Default gateway is the IP address of the default gateway. 4 Click OK. The changes will take effect immediately; it should not be necessary to restart your computer. Step 3: Connect the IPR400 to the computer This step connects the IPR400 to the computer via an Ethernet network. The recommended method of doing this is to use an Ethernet switch or router. However, if such a switch or router is not available, you may connect the computer directly to the IPR400 using an Ethernet network cable. 36 Getting Started

51 Important If you are using a direct connection, you do not need to use a cross-over cable as the Ethernet port is auto-mdix compatible. When connecting the Ethernet cable from the IPR400 to the Ethernet switch or router, the Link indicator will illuminate. If this indicator does not illuminate, you may have a problem with the network cable; and the computer will not be able to communicate with the IPR400 until you correct the problem. Step 4: Configure the IPR400 network settings This step uses the configuration interface to configure the network settings of the IPR400. To configure the IPR400 network settings 1 Start your web browser and type the IP address ( or ) of the IPR400 device in the address bar. Note IPR400 device is factory configured with an IPv4 address as follows: for devices with an even-numbered serial number for devices with an odd-numbered serial number. The login page should appear similar to the one shown below. 2 Configure the network settings of the IPR400 to match the network settings of your computer network. Note For details about how to configure the network settings of the IPR400, see Network Configuration on page 50. Step 5: Restore the network settings of the computer Once you have configured the network settings of the IPR400 device, you can restore the network settings of your computer back to the original settings. Note If you did not change the network settings of your computer, you do not need to perform this step. IPR400 Product Manual 37

52 Repeat Step 2: Change the IP settings of your computer on page 35 to restore the network settings of your computer back to its original settings that you recorded in Step 1: Determine the IP address of your computer on page 33. This time, however, you ll change the IPv4 address, IPv4 Subnet mask, and the IPv4 Default gateway to the original settings. Congratulations! You have now configured the IPR400 to communicate on your network, and you should now be able to connect to the IPR400 using the original network settings of your computer. Using Mac OS X or Linux to Connect For other operating systems, the same basic steps are necessary: change the computer s IP address to one in the same subnet as the IPR400, such as x, then access the IPR400 configuration interface to change its IP address, and then save the configuration and restart. 38 Getting Started

53 Configuring the IPR400 IPR400 provides a built-in configuration interface that you can use to configure it within a LAN or WAN environment with a web browser. This section includes the following topics: What is the Configuration Interface? on page 39 Using the Configuration Interface on page 40 System Status on page 43 Network Configuration on page 50 Simple Network Management Protocol on page 54 Changing the Password on page 58 Backing up and Restoring the Configuration on page 59 Radio Configuration on page 62 VoIP/RTP Configuration on page 65 Selcall and DTMF Settings on page 78 CTCSS Settings on page 81 Serial Data Settings on page 84 Session Initiation Protocol (SIP) Settings on page 89 Linking Radio and VoIP Channels on page 90 Capabilities Configuration on page 98 What is the Configuration Interface? The IPR400 includes a built-in web server that provides a configuration and management interface called the configuration interface. This uses standard HTML, and should be compatible with most web browsers. It consists of a series of web pages designed to help you configure and manage the operation of the IPR400. The configuration interface is compatible with the following web browsers: Internet Explorer 9 11; Edge 38 or later Firefox 38 or later Google Chrome 14 or later Safari 5 or later IPR400 Product Manual 39

54 Using the Configuration Interface All configuration of the IPR400 is done using the configuration interface. To use the configuration interface, you must first log on to the IPR400. You can then access the various configuration pages by clicking on the menus located on the left-hand panel: selecting a menu displays the corresponding page on the right-hand panel. Logging On To use the configuration interface, type the IP address of the IPR400 in your web browser either the factory default IP address or the IP address you configured (see Connecting to the Network on page 32) to access the configuration pages. For instance, when using the default IP address, type or in the address bar of the browser to display the Log On page, as shown in Figure 20. Figure 20. Web-based configuration interface To access the configuration pages used to setup the IPR400, you need to log on to the configuration interface by entering a user name and a password. When you click the Log On link, a password dialog similar to the one shown in Figure 21 is displayed the dialog shown here is from Microsoft Internet Explorer 9. Figure 21. Logging on to the configuration interface When you log on to IPR400 for the first time, or if you have not changed the password, you can use the user name of omni (lowercase) and the default password of ipr400 (lowercase) you cannot change the user name. Once you have logged on, you will see the System Status page, as shown in Figure 22 (see System Status on page 46). 40 Configuring the IPR400

55 Note Both the user name and password are case sensitive and should be typed in lowercase. To prevent unauthorized access to the IPR400 configuration settings, you can change the password (see Changing the Password on page 58). Exiting the Configuration Interface Once you have completed configuring the IPR400, it is recommended that you exit from the configuration interface by clicking the Exit menu item. This will log you out of the session and load the log-on page in your web browser. If you want to continue configuring the IPR400, you will need to type your user name and password again to log on to access the configuration interface (see to Logging On on page 40). Configuration Interface Figure 22 shows the basic user interface. The page shown here is the Network Configuration page that is displayed when you select the Network menu (see Network Configuration on page 50). Configuration page Name of configuration page Settings Displays the settings for the configuration page Menu system Selects menu items Configuration status Displays the status of the configuration settings Figure 22. Using the configuration interface IPR400 Product Manual 41

56 At the bottom of this page is the Configuration Status area, which shows the status of the configuration and whether you have made any changes to the settings. This area appears on all pages that have configuration settings that you can change, and displays various status messages. Note If you are using a version of a web browser that is not supported, the Configuration Status buttons may not be visible at the bottom of the browser window. This may happen with some older browsers, in which case, you can scroll to the bottom of the page to view the buttons. The left-hand side of the configuration interface provides the menu system, which shows a menu item for each of the available configuration pages. A configuration page is accessed by clicking on its corresponding menu item: the configuration page is shown on the right-hand side of the interface. Configuration Status On all of the configuration pages that provide settings you can change, a configuration status area is displayed along the lower edge of the page. This shows the status of the configuration settings for the current page, such as whether you have made any changes to the configuration, or the configuration has changed but you have not yet saved the changes you made. Figure 23 shows the Configuration Status area that is displayed when you have not made any changes to the configuration settings. Save button Saves the settings Figure 23. Configuration status area Undo button Discards any changes to the settings Reset to Defaults button Reloads default settings Restart button Restarts the device The Configuration Status area also shows several buttons that allow you to save or undo any changes you make to the configuration settings. You can also reset the IPR400 to its factory default settings (see Resetting the Configuration to Default Settings on page 45), and restart the IPR400 as required (see Restarting the IPR400 after Saving the Configuration on page 44). 42 Configuring the IPR400

57 The buttons in the Configuration Status area are described below: Save applies the changes you made to the settings on the configuration page. You must always save the configuration before navigating to another configuration page otherwise the changes will be discarded. Restart performs a restart of the IPR400 using configuration settings from Flash memory a restart is required after you save any the changes to the configuration. Reset to Defaults reloads the configuration with default values for settings on all configuration pages (not just the page displayed in the browser), but does not save the default settings to Flash memory. Undo discards any changes that you made to the settings on the configuration page displayed in the web browser, and reloads the configuration. This affects the settings on all configuration pages; not just the settings on the current page. Note If you are using a version of a web browser that is not supported, the Configuration Status buttons may not be visible at the bottom of the browser window. This may happen with some older browsers, in which case, you can scroll to the bottom of the page to view the buttons. The area immediately above the buttons is the Status Message area, which is where the various status messages are displayed, as described below. Status Configuration Unchanged Configuration has been saved. Restart required to take effect. Data is invalid: IT HAS NOT BEEN SAVED Configuration reset to defaults: NOT SAVED Configuration reset to saved values Description Indicates that the configuration settings on the page have not changed. Indicates that the configuration settings have been saved into Flash memory of the IPR400, but are not currently used. A restart is required before the new settings will take effect. Indicates that one (or more) of the settings entered was invalid and the configuration has not been saved. All configuration values on a page must be valid before any values will be saved. You must identify all incorrect configuration values and correct the errors. The Configuration Status area will show additional information about the incorrect value. Indicates that the ALL configuration settings have been reset to the default values; not just the settings on this page. However, you still need to save the changes to make the changes permanent. The configuration values on the configuration page have been restored to the values saved in the Flash memory. This is the result of clicking the Undo button. Note If you change the configuration settings on a page, you must save the changes before leaving that page otherwise the changes will be discarded. IPR400 Product Manual 43

58 Saving the Configuration When you make changes to the settings on a configuration page, or you restore the configuration from a backup file, you must save the changes to the IPR400; otherwise if you navigate to another configuration page, the changes will be discarded. Saving the configuration makes the settings permanent in the IPR400; however, the settings will not take effect until you restart the device. To save the configuration changes, click the Save button on the page. When you save the changes, the message displayed under Configuration Status changes to Configuration has been saved. Restart required to take effect, as shown in Figure 24. Figure 24. Saving the configuration changes This message advises you that the configuration has been permanently saved, however, you now need to restart the IPR400 so that the new settings can be loaded (see Restarting the IPR400 after Saving the Configuration below). Restarting the IPR400 after Saving the Configuration Once you have made changes to the configuration, or restored the configuration from a backup file, and saved the configuration, you must restart the IPR400 for the changes to take effect. To restart the IPR400, click the Restart button on the page. Warning! Do not disconnect power to the IPR400 while it is restarting; otherwise it may cause damage to the IPR400 or corrupt the firmware. While the IPR400 is restarting, the page will show Restart in Progress, as shown in Figure 25. After about 30 seconds, the IPR400 should restart and you will be redirected to the log-in page in your web browser. You will then need to log in again if you want to continue configuring the IPR400 (see Logging On on page 40). After restarting the IPR400, it is recommended that you back up the configuration to a file on your computer in case you need to restore the configuration later (see Backing up the Configuration to a File on page 59). 44 Configuring the IPR400

59 Figure 25. Restarting after saving the configuration settings If you can no longer use your web browser to communicate with the IPR400 after restarting the device, it is most likely that the IP address of your computer is now on a different subnet than the IPR400. If this is the case, you ll need to change it to the same as the IPR400 device before you can use your web browser. For further information on how to change the IP address of your computer, refer to Connecting to the Network on page 32. Note You may need to refresh your browser after restarting the IPR400. Resetting the Configuration to Default Settings Sometimes you may want to reset the configuration of the IPR400 to its factorydefault settings. This is especially useful when you want to change only a handful of settings as it provides a good starting point for configuring the device. In most cases, the default configuration will do for basic installations with only some minor changes. Figure 26 shows the three steps involved in resetting the IPR400 settings. Firstly, click the Reset to Defaults button. This resets the in-memory configuration to default settings, but it does not make the changes permanent. The default configuration is also useful when you need to troubleshoot a particular problem or the device is not operating as you expected. In this case, you can start with the default settings and carefully make changes as required to determine the cause of any problem. To make the changes permanent after resetting to defaults, you then need to save the default configuration to the IPR400 by clicking the Save button on the page. The final step in resetting to defaults involves restarting the device by clicking the Restart button on the page, so that the new settings can be loaded when the IPR400 restarts. IPR400 Product Manual 45

60 Reset to Defaults Reset the IPR400 to factory defaults Save Save the configuration Restart Restart the IPR400 Restart in progress IPR400 is restarting after resetting to defaults Figure 26. Resetting the configuration to default settings Note, however, that because the IPR400 is now reset to default settings, you may not be able to communicate with the device using the same IP address. This is because the IPR400 has reverted to its default IP address set at the factory. In this case, you may need to temporarily change the network settings of your computer in order to use your web browser to communicate with the device (see Connecting to the Network on page 32). System Status The System Status page shows several sections of information such as the hardware and firmware versions used in the IPR400, the current status of operation, the status of the VoIP Groups, and the Radio status. 46 Configuring the IPR400

61 The System Status menu displays System Status page similar to the one shown in Figure 27. All the values on this page are read-only: you cannot change any of the values on this page. Figure 27. System Status page System Version Information The System Version Information section displays the version information for the firmware that is currently loaded in the IPR400. The IPR400 uses two microprocessors: the Freescale Coldfire microprocessor performs all of the network and system functions; and a Digital Signal Processor (DSP) performs the audio processing such as encoding and decoding, voice activity detection, and tone detection. Also displayed here are the revision of the IPR400 hardware and the serial number of the IPR400. Current Status The Current Status section displays current status information about the operation of the IPR400 and includes the following: IP Address shows the local Internet Protocol (IP) Address of the IPR400. System up time or elapsed time since the IPR400 was last reset (displayed as days, hours, minutes and seconds). Ethernet MAC Address shows the unique Media Access Control (MAC) address of the IPR400. Free memory shows the unused memory (kbytes) in the IPR device. IPR400 Product Manual 47

62 VoIP Group Status The IPR400 supports 4 VoIP Groups or Channels. The VoIP Group Status table shows the current status of the link. The columns show the following information: Group shows the group or channel number. Enabled shows if the channel is configured (enabled) or not configured (disabled). Remote Devices shows the number of other IPR devices actively communicating with this device. For a simple point-to-point VoIP link, this will show 1 (if the system is working correctly). Radio Status The Radio Status displays the following detail for each of the four radio channels of the IPR400: Whether the Radio channel is enabled or disabled. The current Push-to-Talk (PTT) state. The current Busy (Mute) state. The last received and transmitted selcall (if any) provided that the selcall detection is enabled on the channel. The current CTCSS receive and transmit status provided that the CTCSS detection/transmission is enabled on the channel. SIP Connection Status The SIP Connection Status lists the number of current active SIP connections for each of the four VoIP groups provided that SIP is enabled on the device. Dynamic DNS Status The Dynamic DNS status shows the current public IP Address, previous public IP Address (if available), the number of consecutive No Change updates, and the last dynamic DNS update result (if available). The Dynamic DNS status is shown if Dynamic DNS is enabled (Network Configuration). Channel Change Status The Channel Change Status shows the status of the channels configured for channel change similar to the example shown in Figure 28 (see Serial Channel-Change Mode on page 86). 48 Configuring the IPR400

63 Figure 28. Channel Change Status Omnitronics Communication API Under the Omnitronics Communication API, the connections from the DX-Altus Server SCUs to each radio channel on the IPR400 are displayed as shown in Figure 29. Two connections are established per radio: one from the main SCU and the other from the standby SCU. Figure 29. Omnitronics Communication API ATIS Status Information The IPR400 sends requests to the ATIS server. The data comes back in XML format. The information extracted from the XML data appears under the ATIS Status Information, as shown in Figure 30. Figure 30. ATIS Status Information RSSI Information The RSSI Information (receive signal strength indication) is only available with the RSSI and Voting feature pack, which is licensed separately. Although the IPR400 displays the values, the DX-Altus Server will not publish these values to Alto. Figure 31. RSSI Information IPR400 Product Manual 49

64 Network Configuration Use the Network page shown in Figure 32 to configure basic network parameters, such as the IP address, network mask, and the gateway address of the IPR400, and to configure other features such as the syslog host and the dynamic DNS parameters. Figure 32. Network configuration page Network Settings The Network Settings area includes the following settings: Automatically obtain IP Address (using DHCP) option is used to allow the IPR400 to obtain an IP address automatically from a DHCP server. When DHCP is enabled, the static IP address, network gateway address, and the domain name server settings will be ignored as appropriate values will be provided by the DHCP server. When this option is selected, the other network settings will be disabled. The default setting is disabled. 50 Configuring the IPR400 Note The IPR400 will attempt to locate a DHCP server on your network at start up to get an IP address. If it cannot find a server, it will either use the Static IP Address if configured or automatically assign itself an address in the range x.x. Static IP Address is the IPv4 address of the IPR400, which consists of 32 bits expressed in a form consisting of four decimal octets separated by periods (dots), called dot-decimal notation. The default value is or (the default configuration is not to use DHCP).

65 Netmask is the subnet mask that determines what part of the IPv4 address is used to identify the subnet that the IPR400 is on. A valid IPv4 subnet mask consists of 32 bits: a sequence of ones (1) followed by a block of zeros (0), expressed in a form consisting of four decimal octets separated by periods (dot-decimal notation). The sequence of ones (1) designates that part as the network prefix (subnet) and the block of zeros (0) designates that part as the host identifier. The default value is Gateway Address is the IP address of the default network gateway. This would usually be the IP address of the router or network device that provides access to the WAN or internet. A valid IPv4 gateway address consists of 32 bits, expressed in a form consisting of four decimal octets separated by periods (dot-decimal notation). The default value is Domain Name System (DNS) Server 1 is the primary Domain Name Server (DNS). The DNS is how an Internet address, such as is resolved into a numeric address, like A valid IPv4 address consists of 32 bits, expressed in a form consisting of four decimal octets separated by periods (dot-decimal notation). A value of indicates that no DNS is used. The default is Note This setting is only required when the VoIP remote address is configured as a full Internet name instead of an IP Address. Consult with your ISP or network administrator to determine the correct address. In some cases, the DNS address is the same as the Gateway address. If the VoIP remote address is a numeric value or a local mdns address, you do not need to change this setting. Domain Name System (DNS) Server 2 is the backup DNS that is used in the event the primary DNS is not available. A valid DNS address is the same as described for the setting above. A value of indicates that no DNS is used. The default setting is (not used). Enable UPNP selects the Universal Plug and Play (UPnP) feature, which is a networking technology that allows devices to work together with fewer configurations. By enabling UPnP, the IPR400 will be displayed in the Network Neighborhood on a Microsoft Windows computer. The default setting is Enabled. Quality of Service: Differentiated Service Class allows the IPR400 to mark its VoIP packets as higher priority to ensure they receive preferential treatment when being routed. Consult with your ISP or network administrator for more information about the appropriate QOS settings. Allowed values: Default, Expedited Forwarding, Class selector 1 to Class selector 7, Assured Forwarding Class 1-1 to Assured Forwarding Class 4-3. The default setting is Default. Syslog host address is the address used for debugging and diagnosing faults with the IPR400, which can report debug and error information via a network protocol called SYSLOG. This setting is normally set to the default (not used). A valid IPv4 address consists of 32 bits, expressed in a form consisting of four decimal octets separated by periods (dot-decimal notation). A value of indicates that no SYSLOG messages are used. The default is (not used). IPR400 Product Manual 51

66 Telnet Enable option enables the Telnet protocol to be used for remote diagnostics. Bootloader network support option specifies whether the boot-loader or the main application firmware initializes the Ethernet interface on startup. Clearing this option may help to resolve startup issues under certain network conditions when the IPR400 fails to get out of boot-loader mode (and does not start the main application firmware) requiring a power reset. Dynamic DNS The Dynamic DNS area allows you to configure the DNS settings of the IPR400 and includes the following: Enable Dynamic DNS allows the device to track changes in its public IP address and to update the configured Dynamic DNS host accordingly. Additionally, it performs periodic Domain Name resolution of any configured remote domains and performs required adjustments when a remote end experiences a change in public IP address. Enabling this feature will decrease VoIP down-time when devices sit behind routers of which the IP address can change dynamically. The default is disabled. Note When enabling Dynamic DNS, ensure that the Domain Name System (DNS) Server 1 setting is configured to an actual DNS server. Public IP Service 1 is a URL to a web service that returns the current public IP address of the requester. It must start with and it is best to verify this in a browser before transferring the URL to this setting. Service 1 will act as the primary web IP lookup. Leaving this field blank will disable determining the IPR device s public IP address. The default is Not Configured. Public IP Service 2 is similar to Public IP Service 1 except that this will act as the secondary web IP lookup if configured. It will only be used if Service 1 fails. The default is Not Configured. Device Domain Name is the fully qualified domain name of the device. It is this name that is used in all dynamic DNS updates when the device detects a change in the current public IP address. The default is Not Configured. Dynamic DNS Host Domain Name is the fully qualified domain name of the server hosting the Dynamic Domain Name service. The server must be the authority with which the Device Domain Name is registered. The default is Not Configured. Dynamic DNS Host Port is the HTTP port (usually 80) of the server hosting the Dynamic Domain Name Service. If port 80 is blocked by a local firewall and if the Dynamic Domain Name Host allows updates via another port, set this accordingly. The default port is Configuring the IPR400

67 Dynamic DNS Host Authentication User Name is the user name required by the dynamic DNS Host for authentication in all updates. The default is Not Configured. Dynamic DNS Host Authentication Password is the password required by the dynamic DNS Host for authentication in all updates. The default is Not Configured. Use the Public IP address for SIP determines whether the public IP address of the device will be used in all SIP conversations. If this setting is not selected, the private IP address will be used. This setting is not selected by default. Using a DHCP Server Select Automatically obtain IP Address (using DHCP) to enable Dynamic Host Configuration Protocol (DHCP), which allows the IPR400 to obtain an IP address automatically from a DHCP server. When DHCP is enabled, the static IP address, network gateway address and domain name server settings will be ignored as appropriate values will be provided by the DHCP server; this is the default setting. If you want to assign a static IP address to the IPR400, it is recommended that you allocate an address in the range of to or to as these are especially reserved for private addresses. When using a DHCP server to automatically allocate an IP address to the IPR400, the other IP device will not be able to communicate with the IPR400 unless you use multicasting or local mdns as it will not know the IP address allocated by the DHCP server. Multicast Addressing is a protocol for efficiently sending data to multiple IPR400 devices at the same time over TCP/IP networks (see Multicast Addressing on page 76 for further details). Local mdns name allows you to connect to an IPR400 device by using a local name address instead of an IP address. Local addressing takes the form of name.local, where name is the RTP Location setting for a particular channel configured on the VoIP/RTP settings page (see VoIP/RTP Configuration on page 65, which shows the IPR400 has the Location Name of IPR400- A GROUP1.local for channel 1). IPR400 Product Manual 53

68 Saving Network Settings Once you make changes to the Network Settings on the Network Configuration page, you must save the changes to the IPR400; otherwise if you navigate to another configuration page, the changes will be discarded. To save the changes, click Save under Configuration Status. When you save the changes, the message displayed under Configuration Status changes to Configuration has been saved. Restart required to take effect advising you to restart the IPR400 so that the new settings can be used. Click Restart to restart the IPR400 with the new settings, as shown in Figure 33. Figure 33. Restarting the IPR400 Simple Network Management Protocol Figure 34 shows the SNMP Configuration page. Use this page to configure SNMP (Simple Network Management Protocol) settings. Figure 34. SNMP configuration page 54 Configuring the IPR400

69 The SNMP configuration consists of several groups of settings such as alarm thresholds for reporting to an SNMP server, and includes the following parameters: Enable SNMP selects the Simple Network Management Protocol (SNMP) feature. SNMP provides a means to extract status information from the IPR400 through a network management system. The IPR400 provides several standard network statistics as well as the site monitoring and control I/O of the IPR400. If SNMP is not being used, this setting should not be selected. For more information about SNMP, refer to Simple Network Management Protocol (SNMP) on page 162. Read Community is the SNMP authentication password needed to read (SNMP GET) values from the IPR400. The default community is "public". If left blank, the IPR400 will set this value to "public" when you save the configuration. It is important to note that in order to write (SNMP SET) values to the IPR400 (the digital outputs are the only values allowed), the community "omni" is required. The SET community cannot be changed. SNMP Trap Destination and SNMP Trap Destination 2 specify the IP address to which the IPR400 will send SNMP traps. This is also known as an SNMP trap sink address. Generally, it is the IP address of a machine that hosts network management software (NMS). The SNMP Trap destination can only be a valid static IP address. By default, the address is which disables SNMP traps. Enable SNMP VoIP Statistic Traps enables the VoIP SNMP Receive Statistic Reports section of the webpage, including the SNMP Statistics Interval parameter. Selecting this checkbox will enable the IPR400 to send a periodic SNMP trap (defined in the SNMP Statistics Interval) for a specific VoIP Group when either the number of defined RTP Sequence Errors is attained or the number of defined RTP Packets Too Late is attained. Note The counters for each of these conditions will reset when the SNMP statistics interval is reached. SNMP Statistics Interval specifies the interval for SNMP traps (in seconds) for a specific VoIP Group when either: the number of RTP Sequence Errors is attained or the number of RTP Packets Too Late is attained. Note The counters for each of these conditions will reset every time the SNMP statistics interval has been reached. The default value is 900 seconds (15 minutes). VoIP SNMP Receive Statistic Reports defines how many RTP sequence errors or RTP packets that arrive too late are permitted within the SNMP statistics interval for a particular VoIP group. Generally, RTP sequence errors and RTP packets that arrive too late may occur during bad network conditions including slow networks, networks with high packet loss, networks with high packet jitter, or networks with many routers/switches between devices. The default value for these fields is 0 (disabled). IPR400 Product Manual 55

70 Site Alarm Limits The IPR400 can trap site alarm limits as shown in Figure 35. These include the minimum and maximum alarm limits for the voltage on each of its eight analog inputs, operating temperature, and the supply voltage. Figure 35. SNMP configuration page showing Site Alarm Limits The settings under the Site Alarm Limits section include the following: Site Alarm Limits - Analog Input 1 to 8 specifies the minimum and maximum values (in millivolts) allowed for a particular analog input on the IPR400. If an analog input crosses one of these thresholds, a corresponding trap will be sent to the SNMP Trap destination(s). The default value is 0 (disabled). Note Analog Input traps are generated when an analog value goes out of range (higher than the high threshold or lower than the low threshold). No trap is generated when the value returns to the valid range. Only one trap is generated when an analog value goes out of the valid range. The analog value must return to the valid range before another out-of-range trap will be generated if it goes out of range again. The analog values are checked based on the configured SNMP statistics interval. Site Alarm Limits - Temperature specifies the minimum and maximum temperature values (in degrees Celsius) at which the IPR400 hardware is allowed to operate. If the operating temperature of the IPR400 hardware crosses one of these thresholds, a corresponding trap will be sent to the SNMP Trap destination(s). The default value is 0 (disabled). 56 Configuring the IPR400

71 Site Alarm Limits - Supply Voltage specifies the minimum and maximum voltage values (in millivolts DC) that the IPR400 hardware is allowed to receive from the connected power supply. If the IPR400 hardware crosses one of these thresholds, a corresponding trap will be sent to the SNMP Trap destination(s). The default value is 0 (disabled). Radio-Specific Traps The IPR400 monitors the LED and alarm status information sent by the MX800 radio and generates SNMP traps if it detects any changes. The parameters under Radio Specific Traps on the SNMP page can be used to select whether or not a particular radio channel can raise SNMP traps, as shown in Figure 36. The MIB file includes a change to the Radio Status Information table (see Table 27 on page 164). The table was expanded to include several new fields representing the LED and Alarm status. These fields are also tied to SNMP traps that may be raised by the IPR400 as required. The MIB file also includes more traps in the general information and notifications table (see Table 25 on page 163). Figure 36. SNMP configuration page showing Radio Specific Traps IPR400 Product Manual 57

72 Changing the Password Use the Change Password page shown in Figure 37 to change the password used to access the IPR400 configuration interface. Select this page from the Change Password menu. Figure 37. Changing the password of the configuration interface To change the password used to access the configuration interface, type the new password you want to use in the Enter password box, and then retype it in the Confirm password box. Make sure to save the new password by clicking on the Save button; otherwise your changes will not be saved. Note You cannot change the User Name using the configuration interface as this is factory preset to omni. The password may contain up to 10 characters in length and may include any character that can be typed using an English language compatible keyboard. 58 Configuring the IPR400

73 Backing up and Restoring the Configuration Use the Backup/Restore page shown in Figure 38 to backup or restore the IPR400 configuration as a file on the hard disk of your computer. It is recommended that you back up the configuration for safe-keeping, in case it needs to be restored later. Figure 38. Saving and restoring the configuration Backing up the Configuration to a File Once you have made changes to the configuration, it is recommended you back up the configuration file to your computer for safe-keeping. You will be prompted to select a location on your computer to store the file. The default file name is ipr400_cfg.bin, but you may rename the file if you wish. To back up the configuration 1 Click Backup to open the File Download dialog. IPR400 Product Manual 59

74 2 Click Save to save the configuration. You will be prompted for a folder and file name in the Save As dialog. 3 (Optional) If you want to use a different file name than the default (ipr400_cfg.bin), type the file name in the File name box. 4 Click Save to download and save the existing configuration to the specified file. When the download is complete, the Download Complete dialog is displayed. 5 Click Close. Restoring the Configuration from a File You can restore the configuration in the IPR400 to a previously saved configuration by restoring the configuration from a backup file on your computer. Once you have restored the configuration from the file, you will then need to restart the IPR400 for the changes to take effect. Note Restoring the configuration does not permanently save the settings to the IPR400; it only loads the settings into memory. You must save the configuration after you restore it to make the settings permanent. To restore the configuration 1 Click Browse to locate the backup file (e.g. ipr400_cfg.bin) on your computer. The full path and filename of the file you selected is shown in the Select Restore Configuration file box. 60 Configuring the IPR400

75 2 Click Restore to restore the configuration from the file on your hard disk. The Configuration Status changes to Configuration restore complete! (Configuration has not been saved). 3 Click Save to save the existing configuration to the IPR400. This saves the restored configuration to the IPR400, but the configuration will not take effect until you restart the IPR400. The Configuration Status changes to "Configuration has been saved. Restart required to take effect". 4 Click Restart to restart the IPR4. The Restart in Progress page is displayed whilst the IPR400 is restarting, after which time, the log-in page will be displayed in your web browser. For further information about restarting the IPR400, refer to Restarting the IPR400 after Saving the Configuration on page 44. IPR400 Product Manual 61

76 Radio Configuration Select Radio to configure the settings for the radio peripheral devices that you want to use, as shown in Figure 39 (settings inside the red border are specific to IPR400 Series-2 only). Figure 39. Radio configuration page Radio/Audio Channel Settings Configure the Radio/Audio settings as described below: Enable Channel selects this channel and allows the radio device associated with the channel to communicate with the IPR400. The default is enabled. Channel Name identifies the name assigned to this channel, which is usually the identity of the radio connected to this channel; it is displayed locally on the IPR400 and in the configuration. The default is blank. PTT Hold/Hang Time is the period (in milliseconds) that the local radio PTT output will remain active after a remote device stops requesting it. This will ensure that the local radio will not stop transmitting until all audio is sent. The allowed values are 0 to 5000 milliseconds. The default is 100 milliseconds. 62 Configuring the IPR400

77 Voice Activity Detection allows the IPR400 to detect when incoming audio is present on the channel. This option helps to minimise bandwidth usage by ensuring that the data is only sent over the network when there is voice data to transmit; also, it allows the IPR400 to generate a signal to drive the PTT relay at the remote end (see the VAD Hold/Hang Time setting). The default is enabled. VAD Hold/Hang Time is how long (in milliseconds) the IPR400 continues to transmit data or hold PTT active after it detects no voice activity on the channel. This is primarily used to ensure that the PTT remains active to keep the remote radio transmitting for this period. The allowed values are 100 to 5000 milliseconds. The default is 1000 milliseconds. Audio Output Level sets the gain of the audio output from the IPR400. The allowed values -10dB to +10dB. The default is 0dB. Audio Input Level sets the level of audio input to the IPR400. Set this to the gain of the expected signal input. The default setup for the IPR400 will result in an input signal of -10dBm, giving an output level of -10dBm (see Audio Level Alignment Examples on page 65 for examples on how to set up audio levels). The allowed values are -20dBm to +12dBm. The default is -10dBm. Output Boost (0dBm) (IPR400 Series 2 only) option boosts the output audio level to 0dBm. Input Attenuate (-10dB) (IPR400 Series 2 only) option attenuates the input audio by 10dB. Select this option when the audio sounds distorted even when the expected input level is set to the maximum. Radio input audio termination (IPR400 Series 2 only) selects the required audio input termination from the radio ( High Impedance or 600 ohm ). Radio Port Push To Talk Output Type (IPR400 Series 2 only) selects the type of output connected to the radio PTT output ( Contact, Voltage, Switched Ground, or Switched Power ). Radio Port Busy Input Type (IPR400 Series 2 only) selects the type of input connected to the radio Busy input ( Contact, Voltage, Switched Ground, or Switched Power ). Two-Wire Mode (IPR400 Series 2 only) option enables Two-Wire mode, which is a balanced transformer-isolated audio interface that operates in 2-wire simplex (not suitable for phone interfaces, which use 2-wire duplex). This mode uses only pin 4 (RX 1a) and pin 5 (RX 1b) of the 4-wire E&M connector. When PTT is active, transmit audio is routed to these two pins. When PTT is inactive, the device is in receive mode. This option is typically used when VAD is enabled (see Voice Activity Detection setting above) and Remote PTT is set to "Local- VAD". Note that PTT Out and Busy In signals are still functional. If the PTT and Busy (extra) lines are used, the busy state will be sent across the network and a PTT from a remote device can drive the IPR400 PTT output. In this way, an Omnitronics console could be used directly on the port without the need for the 936 interface. IPR400 Product Manual 63

78 Transmit without local Busy signal (IPR400 Series 2 only) allows the IPR400 to send audio as data when no control signal is present. This is designed for use with radios that do not provide a Mute/Busy signal. This mode is usually used with VAD. The allowed values are: Requires active radio Busy and Ignores state of radio Busy. The default is Requires active radio Busy. BUSY signal polarity inverted option enables polarity inversion of the Busy input signal. Normally with the opto in voltage mode, when the voltage on the input is from 3V to 30V, the opto switches on and the input is active. Similarly, in contact mode, when the contact on the input is closed, the input is active. When you select this option, the input is inverted so that a normally active signal will be interpreted as inactive. The most common use for this operation is when you have a radio that only has a 5V output that is active low. Normally, you would use contact mode for an active low signal, but the input is pulled up to 10V internally, and when the radio rises to 5V, it keeps the opto on. If you use voltage mode and invert the signal, there is no pullup resistor and the input will operate correctly. PTT Locked On Timeout sets the maximum duration (in seconds) that the PTT output on the channel will remain active. This is to prevent a radio from locking up in transmitting mode. The allowed values are 10 to 600 seconds. The default is 180 seconds. Disable PTT Timeout disables the PTT Locked On Timeout setting for the channel. If this option is selected, and the PTT is active on the channel, it will remain active. The default is not selected (PTT Locked On Timeout enabled). Repeater loopback enable (loopback audio and control) enables repeater loopback mode for this radio channel. When this mode is enabled, the IPR400 will loopback control and audio to the radio channel. The IPR400 will activate the PTT output when it detects that the channel is active or keyed on. If CTCSS detection is enabled for this radio channel, and a CTCSS keying mode is also active for this channel, then both the radio mute and the CTCSS receive tone will determine if the channel is active. The default setting is unselected (repeater loopback disabled). Repeater loopback exclusive (loopback audio overrides incoming audio) enables repeater loopback exclusive mode for this radio channel. When this mode is enabled, the IPR400 will loopback local audio overriding the network audio. The default is disabled. Enable Busy Validation option allows the IPR400 to validate the Busy input to ensure it is present for a configurable period of time. The default disabled. Busy Validation Time is the duration (in milliseconds) for mute validation: the input state of the mute will be ignored for this period, and no mute state or audio will be sent to the network. The allowed values are 0 to 1000 milliseconds. The default is 20 milliseconds. Enable audio delay option enables audio delay for trunked-radio support on this radio channel. The default is disabled. Audio delay time specifies the audio delay (in milliseconds) for this radio channel. The default is Configuring the IPR400

79 Trunked Radio Audio Delay Mode Each radio channel can be configured to provide delayed voice audio (with respect to PTT) to the radio. This is a key factor in allowing conventional radios to be linked with trunked radios: it allows the trunk call setup to take place without losing the first few syllables of speech. Enable audio delay imposes an audio delay on the radio channel. The default setting is deselected (no audio delay). Audio delay time (milliseconds) is the duration (in milliseconds) that the transmit voice audio is delayed prior to sending it to the radio. The allowed values are 0 to 4000ms. The default setting is 0. Audio Level Alignment Examples Example 1: For radio to radio, the input level from the radio is -10dBm and the desired output to the radio is -10dBm (this is the default configuration). Set the Receive Input Level to "Input Level -10 dbm", and the Transmit Gain to "Tx Gain 0 db". Example 2: For radio to radio, the input level from the radio is 0dBm and the desired output to the radio is 0dBm. Since the nominal input level is -10dBm, setting the input level to 0dBm introduces an attenuation of -10dB. To boost the output level back to 0dBm, a gain of +10dB is required. Set the Receive Input Level to "Input Level 0dBm", and the Transmit Gain to "Tx Gain 10dB". Example 3: For radio to radio, the input level from the radio is -20dBm and the desired output to the radio is -10dBm. As the nominal input level is usually -10dBm, setting the input level to -20dBm introduces a gain of 10dB. Set the output gain to 0dB, and set the Receive Input Level to -20dBm. VoIP/RTP Configuration In addition to the 12 SIP connections, there are 12 static destinations that can be configured. The IPR400 allows three unicast or multicast destination addresses per VoIP group and each VoIP group can be connected by the linker to one or more connected radios: 1 x primary address (unicast or multicast) 2 x conference addresses (unicast or multicast) Note You can configure up to 12 SIP connections and 12 static destinations simultaneously; however, there may be loading issues for such a configuration. The loading is determined by the number of VoIP streams received on a group and the codecs used. The IPR400 simultaneoulsy decodes audio from a maximum of 6 sources, but allows for more to be connected. IPR400 Product Manual 65

80 Select VoIP/RTP to configure the settings for VoIP and RTP, as shown in Figure 40. Figure 40. VoIP/RTP configuration settings VoIP/RTP Settings Under the basic settings, you can set the IP address of the remote IPR device and the port numbers used for sending and receiving data: VoIP Group Enable enables the VoIP group on this channel and allows the radio device associated with the channel to communicate with the IPR400. The default setting is Enabled. Remote IP Addressis the IP address of the remote IPR400 device: this can be either a unicast or multicast address. The allowed value is either a valid IP address in dot notation, which consists of four numbers in the range 0 to 255 with each separated by a period (dot), or a fully qualified domain name. The default value is the local address of a matching IPR device (see Factory Default Addresses on page 77 for further information). The default setting is or RTP Location is the name that identifies the audio source. This name appears on the statistics page of the remote IPR device (see Channel Statistics on page 110). The default setting is IPR400-<serialnumber>-GROUP1 for CH1, where <serial number> is the serial number of the IPR400. RTP Receive Port Number is the port number that is used for receiving audio and control messages. The allowed value is an even number between 1024 and The default setting is 5004, 5006, 5008 or 5010 (depending on the VoIP Channel/Group number). 66 Configuring the IPR400

81 RTP Transmit Port Number is the port number that is used for transmitting audio and control messages. The allowed value is an even number between 1025 and The default setting is 5004, 5006, 5008 or 5010 (depending on the VoIP Channel/Group number). IP Time To Live (TTL) determines the number of network routers that will forward data packets from this unit. Typically, when a router forwards a data packet, it will decrease the TTL value until it reaches zero at which time the packet will no longer get forwarded. When using multicasting, the value indicates the scope or range in which a packet can be forwarded. The allowable values are 1 to 255. The default value is 1. When configuring an IPR device to use multicasting, it is important to consult with your IT department that manages the network infrastructure to ensure an appropriate value is used. The following pre-defined values are used by convention: TTL = 0 TTL = 1 TTL = 32 TTL = 64 TTL = 128 TTL = 225 Restricted to the same host Restricted to the same subnet Restricted to the same site Restricted to the same region Restricted to the same continent Unrestricted Transmit Codec is the encoding scheme used to encode the audio data for transmission to the remote device. This setting only affects the audio sent. This IPR device will determine the type of codec used by the remote device and decode the audio even if a different codec is used. The following codecs are supported: G.711 PCMU (default), G.711 PCMA, G , or GSM (see Supported Codecs on page 70). Note Different versions of IPR devices and VoIP phones support different codecs. The IPR400 does not support G.729 or G RTCP Interval/Timeout specifies the how often (seconds) RTCP packets are sent. The VoIP link consists of voice data and control information. The control information is provided by the Real Time Control Protocol (RTCP) where packets are periodically sent to provide a heart-beat to maintain the VoIP connection. Decreasing this value will reduce the time to detect a link disconnection with the associated disadvantage of increasing the required Ethernet bandwidth. Alternatively, increasing this value reduces the required Ethernet bandwidth but increases the time to detect a link disconnection. An increased value may be useful in data-bandwidth-critical applications such as VoIP links through the 3G mobile phone network. The allowed values are 1 to 120 seconds. The default value is 5 seconds. Note This parameter must be set identically on both devices that have esatblished a VoIP link. If multicasting is used, all devices in the multicast group must have this parameter set identically. IPR400 Product Manual 67

82 RTP Mute/PTT Interval/Timeout specifies the period (in seconds) that the IPR400 sends the current state of the local mute/busy state of the radio to the remotely connected devices. This ensures that if a message is lost due to a network error or disconnection, the local PTT output will be set to the correct state. Reducing the value of this parameter has the effect of reducing the time in detecting an incorrect push-to-talk output state with the associated disadvantage of increasing the required Ethernet bandwidth. Alternatively, increasing the value of this parameter reduces the required Ethernet bandwidth, but increases the time to detect an incorrect push-to-talk state. An increased RTP Mute/PTT interval may be useful in a data-bandwidth-critical application such as a VoIP link through the 3G mobile phone network. The allowed values are 1 to 120 seconds. The default setting is 5 seconds. RTP Mute/PTT Period Send Disable option disables the periodic transmission of RTP MUTE/PTT information and the timeout of the setting above. Note If this setting is selected, it should be selected for both devices. This setting should not be selected for normal VoIP links. This option is only for situations where minimising data bandwidth is critical. RTP Transmit Packet Size determines the amount of audio in each transmitted packet. This option is for use with VoIP systems that require packets with a size of 20ms. Setting the value to 160ms will result is a small reduction in the audio delay. Possible values are 160ms or 320ms. The default value is 320ms. Note This setting is implemented in IPR400 firmware version 3.20 and later. Early versions of IPR and DX-Altus device firmware are not compatible with packet settings of 160 milliseconds. Please ensure you are using the current firmware versions if you enable packets of 160 milliseconds ( IPE v4.00 or later, IPR100 v5.00 or later, IPR400 v3.20 or later). Minimum Jitter Buffer Size sets the delay (in milliseconds) imposed on the received audio. If the IPR400 is used on a network in which variations in packet delay occur, increasing this value to match the maximum likely delay, should improve the quality of the audio. The larger this value is set, the more delay is imposed on the received audio. The allowed values are 20 to 1000 milliseconds. The default value is 20 milliseconds. Maximum Jitter Buffer Size sets the maximum acceptable audio delay (in milliseconds), for received audio. The IPR400 will automatically adjust the delay (depending on network conditions) to the smallest possible, thus reducing the received audio delay to the minimum that the network can support. The allowed values are: 100 to 2000 milliseconds. The default value is 500 milliseconds. Note The Maximum Jitter Buffer Size must be greater than or equal to the Minimum Jitter Buffer Size. 68 Configuring the IPR400

83 Remote PTT/Busy Control Mode determines how the PTT relay of the remote IPR device is activated; the options are described below: None Local-Mute Local-VAD Do not drive remote PTT Drive remote PTT from the local radio MUTE input (the default) Drive remote PTT from the voice activity detection (VAD) Enable encryption allows the IPR400 to encrypt the network data so that a third party is unable to intercept and listen in to conversations. Using an encryption algorithm allows the IPR400 to encrypt voice and control data. The IPR400 provides two algorithms: DES and AES (Australia models only). The DES algorithm is an older and less-secure with a secret key of 56 bits. The AES algorithm is a newer and more secure algorithm with a key of 128 bits. Due to export restrictions, only devices with DES encryption can be exported from Australia. As a result, international IPR devices support only the DES encryption standard. The allowed values are listed below: Encryption Disabled (default) Encryption Enabled AES 128 AES with 256 bit key Encryption Enabled DES Do not use data encryption Use AES 128-bit encryption Use AES 256-bit encryption Use DES 56-bit encryption Encryption key is the string that is used to encrypt the data. This ensures that no third party can decrypt the VoIP data. If this field is left blank, the default encryption is used; this ensures backward compatibility with earlier versions of IPR400 firmware. The encryption key is case sensitive. Important If encryption is enabled, then all communicating IPR devices must have encryption enabled and configured with the same encryption type and key; otherwise the IPR devices will not be able to communicate (the external VoIP indicator will not illuminate). Enable Half-Duplex Mode option enables the half-duplex mode of operation. In this mode, while the device is generating an active PTT output (sending audio to the radio), the Busy input signal and any received audio from the radio will be ignored. Furthermore, when the Busy input signal is active (receiving audio from the radio), PTT from the device will override the Busy input signal and audio from the radio. Use this mode when you want to force the VoIP link to be half-duplex. IPR400 Product Manual 69

84 Supported Codecs The codecs supported by the IPR400 device are listed below. Codec G.711 PCMU 8000Hz μ- law (often u-law, ulaw, or mu-law) G.711 PCMA 8000Hz A- law G ADPCM 8000Hz GSM 8000Hz Description ITU G.711 Pulse Coded Modulation μ-law. Bandwidth: 64 kbits per second. Use this Codec for tone signaling. Voice Quality: Best. Used in North America and Japan. ITU G.711 Pulse Coded Modulation A-law. Bandwidth: 64 kbits per second. Use this Codec for tone signaling. Voice Quality: Best. Used in Europe and rest of the world. Adaptive PCM: ITU G ADPCM 8000Hz: Adaptive PCM. Bandwidth: 32 k bits per second. Voice Quality: Good This is GSM Codec. Bandwidth: 13 k bits per second. Voice Quality: Good for Voice but distorts tones and DTMF signals. VoIP Conference Mode Under the Conference Mode settings, as shown in Figure 41, the IPR400 can connect multiple IP devices in conference mode. This allows several radios or consoles to be connected together in a conference. Figure 41. VoIP Conference Mode settings Various configurations are provided for linking the radios together depending on the network and the radio set up. The IPR400 can support up to 3 devices per VoIP channel (12 channels in total) connected together in conference mode. Other devices that can participate in the conference include the IPR100, IPR110+, IPR400, IPE, the 960SIP Console (960CC or 960CSD connected to an IPR120) or 960CSD Console connected to an IPR device. Conference Mode includes the following settings: Note Conference mode affects audio, DTMF, selcall, and CTCSS (subaudible) tones. Enable Conferencing enables the conferencing mode for the VoIP channel/group. The default is disabled. 70 Configuring the IPR400

85 Conference Mode selects the type of conference mode; it determines whether the audio is linked or retransmitted to the other devices in the conference. The default setting is Peer to peer: No central server. In conference mode, several radios or consoles can connect together in a conference so that when any radio or console in the conference receives audio, it is transmitted to all (or some) of the other devices in the conference. The following lists the available conference modes: Peer to Peer: No Central Server Bridge Server: Audio Linked Dispatch Server: Audio not Linked Multicast Gateway: Audio Linked All IPR devices communicate with all the other IPR devices (see Peer-to-Peer on page 72). All IPR devices communicate with this IPR400 which forwards the audio to all remote devices (see Bridge Server on page 72). All IPR devices communicate with this IPR400. This IPR400 does not forward any of the remote audio (see Dispatch Server on page 73. IPR devices communicate with this IPR400 that is connected to a gateway router or server. This IPR400 forwards audio to/from the remote connection (see Multicast Gateway on page 73). Note Conference mode does not affect the serial pass-through mode. Enable allows the associated IP address and port configuration for conferencemode transmissions. The default is disabled. IP Address is the IP address for this conference (i.e., the IP address of the remote IPR device). As for the VoIP remote address, this can be a numeric Internet address or a domain name. Allowed values are a valid remote VoIP address. The default is and Transmit Port is the port number that is used for transmitting audio and control messages for conference mode. As for the VoIP Transmit Port, two consecutive ports are used: the first port is for audio data and the second port is for control and status information. Allowed value is an even number from 1026 to The default port is 5004, 5104 (CH1); 5006, 5106 (CH2); 5008, 5108 (CH3); or 5010, 5110 (CH4) depending on conference and channel numbers. Conference Mode Configurations The IPR400 supports conference mode, which is a method of linking or forwarding audio between multiple IP devices: conference mode allows multiple Omnitronics IP devices to interconnect over an IP network. Figure 42 shows a block diagram of the conference mode configurations. IPR400 Product Manual 71

86 Figure 42. IPR400 Conference Mode block diagram Several different configurations of conference mode are available: Peer-to-Peer Bridge Server Dispatch Server Multicast Gateway The conference mode configurations are discussed in the following sections. Peer-to-Peer The Peer-to-Peer conference mode allows multiple IPR400 devices to communicate with all other connected Omnitronics IP devices within the conference. This is a simulated multicast mode. Each IPR400 in the conference is configured to send audio to all other Omnitronics IP devices. Operation: Audio received at any IPR400 in the conference group is transmitted to all other Omnitronics IP devices in the group. Effectively all the radios/consoles are linked together. Failure Mode: If any one IPR400 fails then only that IPR400 is affected. Configuration: It is the most difficult to configure since all IPR400 devices in the conference group need to be configured with the addresses of all the other Omnitronics IP devices in the group. Bridge Server The Bridge Server conference mode, shown in Figure 40, provides the same functionality as the Peer-to-Peer conference mode in a different configuration. In this approach all IPR400 devices are connected to a single IPR400 Bridge Server; any audio sent to the Bridge Server will be relayed to all connected Omnitronics IP devices. 72 Configuring the IPR400

87 Operation: Audio received at any IPR400 device in the conference group is output on all other Omnitronics IP devices in the group. Effectively all the radios/consoles are linked together. The server performs linking through VoIP. Failure Mode: If the server fails then all communications within the group will also fail. Configuration: This mode is easier to configure since it is only the server that needs to be configured in conference mode. All client IPR400 devices can be configured with a single destination: the server IP address. Dispatch Server The Dispatch Server conference mode is similar to the Bridge Server configuration. Operation: Audio received at any client IPR400 device in the conference group is transmitted to the server IPR400 device. Audio transmitted by the server IPR400 device is output to all client IPR400 devices. Failure Mode: If the server IPR400 device fails then the whole group will discontinue communicating. Configuration: This mode is easier to configure since it is only the server device that needs to be configured in conference mode. All client IPR400 devices can be configured with a single destination: the server IP address. This configuration will typically be used when the server is connected to a dispatch console. Multicast Gateway The Multicast Gateway conference mode is a configuration of IPR400 devices that is designed to provide a multicast gateway/bridge. Typically, this configuration may be used to bridge across the Internet. Operation: Audio received at the gateway IPR400 device is forwarded to all Omnitronics IP devices in the conference group. Failure Mode: If the gateway IPR400 devices should fail then there is no connection between multicast groups via the Internet, however the local multicast groups will still function. Configuration: This mode is easier to configure since only the server needs to be configured in conference mode. All client IPR400 devices can be configured with a single multicast destination: the server IP address. Audible Link Status Alarm Figure 43 shows the settings provided under Audible Link Status Alarm and an audio timing diagram. These settings allow you to configure the playback of audio files on the radio port when a VoIP link is not available. The timing diagram illustrates how the various settings affect the playback of the audio. IPR400 Product Manual 73

88 As shown in the timing diagram, when a VoIP link is currently unavailable (link failure), a busy (or mute) input from a linked radio will cause an audible link-unavailable announcement to play back on all linked radio channels, but only after the turnaround time elapses. The PTT output is then asserted and after the PTT lead-in time elapses, the selected audio file (sound to play) starts to play back. Once playback is completed, the PTT output drops after the PTT lead-out time elapses. While the link is still in a link-failure condition, the playback sequence shown in Figure 43 repeats according to the number of repeats set by the playback repeat count. However, short bursts of busy activity (less than the turnaround time) will not cause playback of the audio announcement. Playback occurs only after the turnaround time elapses, and ceases when either the playback repeat count is reached or the link recovers from the link failure (link becomes available). Figure 43. Audible Link Status Alarm settings and audio announcement timing The Audible Link Status Alarm configuration includes the following settings: Enable Audio feedback on VoIP link failure enables the feature to play the configured audio file to all linked radios after receiving an incoming busy from a radio if the VoIP Link is currently unavailable. Options: Enabled/Disabled. The default is disabled. Sound to Play selects the audio file (.au) to use for playback of pre-recorded warning announcements and sounds. Default is voip_link_unavailable.au. Options are listed below: 74 Configuring the IPR400

89 voip_link_unavailable.au nework_unavailable.au link_failure.au congestion.au busy.au Female voice (Australian accent) announcing VoIP Link Failure. Female voice (Australian accent) announcing Network Unavailable. Female synthesized voice (American accent) announcing Link Failure. Fast-passed cadenced tone (3 seconds duration). Cadenced tone (3.5 seconds duration). Turnaround Time (seconds) is the time the IPR400 waits before playing the warning sound (see the Sound to Play setting above). The turnaround time starts at the falling edge of the radio busy signal. If there is any activity on this VoIP channel, the sound is not played and the turnaround time restarts on the falling edge of the next radio busy signal. Activity that restarts the turnaround time is a busy signal from any radio linked to this VoIP channel or a Push-To- Talk request from any remote device connected to this VoIP channel. Allowed values: 1-20 seconds. The default value is 5 seconds. PTT Lead in Time (milliseconds) is the period that Push-To-Talk on all linked radios will be active before audio playback commences. This will ensure that linked radios are transmitting by the time audio is sent. Allowed values: milliseconds. The default value is 100 milliseconds. PTT Lead out Time (milliseconds) is the period that Push-To-Talk on all linked radios will remain active after audio playback completes. This will ensure that linked radios will not stop transmitting until all audio is sent. Allowed Values: milliseconds. The default value is 100 milliseconds. Playback Repeat Count is the number of times the IPR400 will play the warning sound after a link failure. Once this count is exceeded, the warning sound will not be played again. The count is reset when the VoIP link status returns to the good state. Allowed Values: The default value is 10. Override Audio feedback on VoIP link failure allows you to prevent the playback of an audio file (when a link failure occurs) by selecting a digital input to override playback; a logic high condition on the specified digital input prevents playback of the audio file. Options: Off, Digital Input 1, Digital Input 2. The default value is Off. Physical Link Status Alarm The Physical Link Status Alarm configuration shown in Figure 43 includes the following setting: Enable Off Normal indication on VoIP link failure allows a digital output to be associated with one or more VoIP Groups to serve as a physical indication of the link status. When all VoIP groups associated with the digital output have good links, the digital output switches ON (to form a closed circuit) signalling normal operation. If any of the associated VoIP Links fail, the digital output switches OFF (to form an open circuit) to signal an Off Normal condition. Options: Off, Digital Output 1, Digital Output 2. The default value is Off. IPR400 Product Manual 75

90 Remote Addressing The IPR400 supports three types of remote addresses, as discussed below: Numeric is an IPv4 address, which consists of 32 bits expressed in a form consisting of four decimal octets separated by periods (dots), called dot-decimal notation. This can be used on a LAN set up where all the addresses are allocated. Numeric addressing can also be used where a global Internet Address has been allocated and is known. On a local LAN, a common numeric address could be either or The special address disables transmission; there are applications where this may be useful. Fully Qualified Name is an internet address that uses a fully qualified domain name such as iprunit3.host.omnitronics.com.au. You can use a domain name only if the IPR400 has been configured to use a domain name server (DNS). In this case, the address of the remote IPR device will be allocated by a DNS. This could be the case for an IPR device that is connected to the Internet via an ADSL modem. Local Name is an address that includes the suffix.local, such as ipr a2156.local. The IPR400 uses a technology called mdns (Multicast DNS) to locally discover the addresses of other IPR devices on the local network. In this case a name can be used to work out the address of the remote device without requiring an external DNS. However, this can only work on networks that fully support multicasting, and is recommended for setting up a LAN that supports dynamic addressing. Multicast Addressing Multicast Addressing (multicasting) is an IP addressing scheme that provides an efficient method of sending audio to multiple destinations (a one-to-many transmission). Using multicast addressing, a single data packet is routed to multiple destinations; the network will only duplicate the packet if it needs to go to several different locations. For multicast addressing to work, all the network routers in the network must support multicast addressing and have multicasting enabled in their configurations. If your network does not support multicasting, the conference modes provide an alternate solution (see Conference Mode Configurations on page 71). Note Many routers on the Internet and most ADSL/DSL modems do not support multicasting. Audio received at any IPR400 in the multicast group is transmitted once and received by all the other IPR400 devices in the group. Effectively all the radios or consoles are linked together. If any one IPR400 device fails, only that IPR400 is affected. All the devices are configured to use a single multicast address as the remote address for their VoIP link. 76 Configuring the IPR400

91 Note Up to 32 Omnitronics gateways and consoles can communicate on a single multicast group; however, not all of these devices can transmit simultaneously. Only one device is meant to transmit at a time, which should suffice in a typical half-duplex radio communication environment where only occasionally more than one device will try to transmit at the same time. Omnitronics IPR devices provide a configuration setting to prevent more than one device to transmit on a multicast system. DRG100 and DRG200i devices still need dedicated TCP connections from each console (RediTALK-Flex or DX-Altus IPE) to the DRG100/DRG200i (as is the case for SIP and unicast connections). These TCP connections are used for data and control purposes and they do not use a lot of bandwidth compared to VoIP. If you need to connect more than 32 devices using multicast, please contact your Omnitronics representative. Factory Default Addresses IPR400 devices are factory configured to use a static IP address that is based on the serial number of the device. For even-numbered serial numbers, the default IP address is , and for odd-numbered serial numbers, the default IP address is The default mdns address also depends on the serial number of the device. If the serial number is even-numbered (e.g., 52A1212), its local mdns address is IPR400-52A1212.local, and if the serial number is odd-numbered (e.g., 52A1213), its local mdns address is IPR400-52A1213.local. Internet Port Numbers An Internet port number is part of the IP header and identifies the type of data received or transmitted. The port numbers 5004 and 5005 are allocated for the Real Time Protocol (RTP) and are normally used for VoIP and video data packets. However, the port number may need to be changed to pass through some types of network devices, particularly those that use Network Address Translation (NAT) or Port Forwarding. IPR400 Product Manual 77

92 Selcall and DTMF Settings Use the Selcall/DTMF page to view the configuration for the selcall and DTMF settings, as shown in Figure 44. The IPR400 supports selcall and DTMF by detecting the tone, encoding it as a data packet and sending it to a remote device. This enables selcall and DTMF to be sent on links with GSM or other compressing codec. Figure 44. Selcall and DTMF settings General The configuration settings under the General section include the following: Tone Transmit Level is the output gain setting for transmitting both SELCAL and DTMF tones to locally installed equipment. This level does not affect (nor is affected by) the audio transmit level. The allowed values are -10 to +10dB. The default setting is 0dB. Lead In Delayis the length of time (x10 milliseconds) that the IPR400 asserts the PTT before starting to transmit a SELCAL or DTMF tone. This is to ensure the radio is on and transmitting correctly before the tone is transmitted. The allowed values are 2 to 255 (20 to 2550 milliseconds). The default value is 100 (1 second). Lead Out Delay is the length of time (x10 milliseconds) that the IPR400 holds the PTT on after sending a DTMF or SELCAL tone. This is to ensure the radio does not turn off before the whole tone has been received. The allowed values are 2 to 255 (20 to 2550 milliseconds). The default value is 50 (500 milliseconds). 78 Configuring the IPR400

93 DTMF The configuration settings under the DTMF section include the following: DTMF Detection option enables local detection of DTMF and uses the value in DTMF Tone Period (in milliseconds. If this is selected, the IPR400 will locally listen for and decode DTMF tones. When it receives a valid DTMF tone, it will encode it as a data packet and send it to the remote IPR device. At the remote IPR device, when the data packet is received, it will generate a corresponding DTMF tone sequence. The default is disabled. DTMF Tone Period (in milliseconds) is the duration of the Tone and Silence periods for generated DTMF signals. The allowed values are 50 and 100 milliseconds. The default value is 100 milliseconds. Selcall (Selective Calling) The configuration settings under the Selcall (Selective Calling) section include the following: Selcall Detection option enables local detection of selcall. If this is selected, the IPR400 will locally look for and decode selcall tone sequences. When it receives a valid selcall sequence, it will encode it as a data packet and send it to the remote IPR device. At the remote IPR device, the data packet will be received and the remote IPR device will generate a selcall sequence with the same numbers. The default value is Disabled. Selcall Scheme specifies the type of selcall scheme in use. The supported selcall schemes are EEA, ZVEI1, ZVEI2, ZVEI3, PZVEI, CCIR, EIA and DZVEI. The default setting is CCIR. Number of Tones is the number of tones and gaps in a valid selcall sequence. The allowed values are 1 to 20. The default is 5. Selcall Tone Period (milliseconds) is the duration in milliseconds of each tone in the sequence. The allowed values are 20 to 100 milliseconds. The default is 20 milliseconds. Enable Status Gap enables a gap between the first part of the SELCALL sequence and the final status digit. The default setting is unselected (status gap disabled). Status Gap Length configures both the length of the gap and the length of the final digit of the SELCALL sequence. The length is either the same as the SELCALL period or twice the SELCALL period. The allowed values are: One-Tone or Two-Tones. The default setting is Two-Tone. IPR400 Product Manual 79

94 Tone Position and Type The settings on the Selcall/DTMF page available under the Tone Position and Tone Type headings include the following: Tone Position and Type shows the position of each configured tone and the how the tone is configured: the IPR400 can be configured to detect a particular tone or silence duration. When configuring these settings, several rules are applied to ensure the tone sequence is valid: Firstly, the first and last tone positions must be configured as a tone. Additionally, an extended tone period can only be configured in a position after a silence period. The following section provides some examples of how to configure the selcall settings. Tone: Normal Period Tone: Extended Period Silence: Normal Period Silence: Extended Period Specifies a tone that is equal in duration to the period of the configured tone. Specifies a tone that is twice the duration of the period of the configured tone. Specifies a period of silence that is equal in duration to the period of the configured tone. Specifies a period of silence that is twice the duration of the period of the configured tone. Example Selcall Configurations To use the selcall feature, you must first select the Selcall Enable option, which enables all of the selcall settings, as shown in Figure 45. In this example, the selcall tone scheme is set to CCIR, and five tones are configured each with a period of 20 milliseconds. Figure 45. Example of CCIR selcall configuration 80 Configuring the IPR400

95 In the next example shown in Figure 46, the selcall tone scheme is set to EIA with six tones configured each with a tone period set to 40 milliseconds. The first four tones are normal tones followed by a double-width gap then an extended status tone (i.e. a double-width status tone). Figure 46. Example of EIA selcall configuration CTCSS Settings Use the CTCSS page to configure the settings for the CTCSS (Continuous Tone Coded Squelch System), as shown in Figure 47. Figure 47. CTCSS configuration settings IPR400 Product Manual 81

96 Tone Detection The configuration settings available under Tone Detection include the following: Enable Tone Detection/Transmission option allows the IPR400 to detect CTCSS tones and transmit them to the network as data packets. The default setting is unselected (Tone Detection/Transmission disabled). CTCSS Signal Path (not available in IPR400 Series 2) determines the path of the CTCSS tones. The IPR400 voice circuitry includes a high-pass filter so that CTCSS tones will not be sent as audio data. The allowed values are CTCSS In-Band or CTCSS External. The default is CTCSS In-Band. Note An external CTCSS signal path is provided via the 25-way AUX (digital I/O) connector on the back panel of the IPR400. Enable high-pass filter for audio enables a high-pass filter in the DSP that will remove the CTCSS tones from the audio path. The default setting is unselected (High-pass audio filter disabled). Tone Detection Validation Time is the period (in milliseconds) that a frequency must be present and detected before it is considered a valid tone. Setting this time for a longer period will make the CTCSS tone detection more reliable but will increase the delay for propagating the CTCSS information. The allowed values are 10 to 1000 milliseconds. The default is 150 milliseconds. Local Keying and Tone Transmission The configuration settings available under Local Keying and Tone Transmission include the following: Transmit Level is the level of attenuation or gain applied to the locally generated CTCSS tone. It is independent of transmit audio and transmit SELCAL/DTMF levels. Allowed values: -10 to +10dB. The default setting is Tx Gain 0 db. PTT keying mode is the method by which the local PTT signal is controlled. The available modes are listed below: CTCSS Ignored (default) CTCSS Fast Key Mode Only the state of the Busy information from the network is used to drive the local PTT signal. When the remote Radio is active, the local PTT will be active regardless of the state of the CTCSS detection. The local PTT signal is asserted as soon as the remote PTT signal is detected. However, if a configured remote CTCSS tone is not received before the CTCSS lockout time, the local PTT will be dropped. This mode is used to minimise the time taken to key up a radio. 82 Configuring the IPR400

97 CTCSS Normal Key Mode CTCSS Only Mode The local PTT signal is asserted when both the remote PTT signal is detected and a valid remote CTCSS tone is detected. If the CTCSS tone is not detected before the CTCSS lockout time, then the local PTT signal will not be asserted even if a valid CTCSS tone is detected. The local PTT signal is asserted when a valid remote CTCSS tone is detected. The state of the remote PTT is ignored. CTCSS Lockout Time is the timeout period (in milliseconds) used in fast keying mode and normal keying mode. If a remote CTCSS is not detected within this period when the remote PTT signal is detected, the local PTT signal will not be activated. The default setting is Enabled Frequencies The IPR400 can detect up to 33 CTCSS frequencies simultaneously and generate one at a time. The frequencies that the IPR400 can detect and generate (in Hz) are listed below: 67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 167.9, 173.8, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, Note To enable a frequency, select the check box next to the frequency. If you attempt to enable more than 32 frequencies, an alert message is displayed. For a CTCSS tone to be correctly detected and transmitted, that frequency must be enabled on both IPR400 devices, i.e., on both the detecting and the transmitting IPR400. CTCSS Talk Off Timeout The IPR400 will hold the receive CTCSS frequency for a talk off time of 2000 milliseconds (the CTCSS frequency must be undetected for 2000 milliseconds before the indication is dropped). This is to stop the CTCSS indication being dropped during speech. However, when either CTCSS Fast Key Mode or CTCSS Normal Key Mode is used, if the radio mute becomes inactive, the CTCSS indication will be dropped immediately. IPR400 Product Manual 83

98 Serial Data Settings Use the Serial Data page to configure the settings for the serial data communications, as shown in Figure 48. This page provides the settings for configuring the serial ports (DCE-1 to DCE-4) on the IPR400 back panel. Figure 48. Serial Data configuration showing the Serial Pass-Through settings Each serial port supports two modes of operation; however, only one of these modes can be enabled on a channel at the same time: Serial pass-through mode provides a transparent link that can be used to connect RS232 devices over the Internet these settings are available on Pass- Through page. Serial channel-change mode provides the ability to control the channelchange functionality of radios with an RS232 serial control interface these settings are on the Channel Change page. Both modes of operation are discussed in the following sections. Serial Pass-Through Mode The IPR400 provides the ability to transmit and receive RS232 data between a pair of IPR400 devices. This uses a UDP connection between the two units to tunnel RS232 data over the network. The settings available on the Serial Pass-Through page are configured on a per channel basis. Note Each channel tab shows the configuration settings for each channel, which corresponds to a serial port number, and is not linked to any radio or VoIP channel. 84 Configuring the IPR400

99 The configuration settings under Parameters include the following: Enable Serial Pass Through Mode selects the serial data pass-through mode and disables the serial channel-change mode on the selected channel. The default is disabled. Note If Serial pass-through mode is enabled, the serial channelchange mode is disabled for the corresponding serial port. Remote IP Address is the IP address of the remote IPR400 to which the serial data will be sent. Like the remote VoIP address settings, this can be a 32-bit IPv4 address or a domain name. The default is Note The Remote Address does not need to be the same as the VoIP Remote Address, which means that the serial pass-through mode can be used to send serial data to any valid IP address. UDP Port Number specifies the TCP/IP port number that is used for sending the data, which must be set to the same value on both IPR400 devices. The allowed values are 1024 to The default setting is The compatibility of the serial pass-through mode between the IPR100/110+ and IPR400 is listed below. Serial Pass-Through Protocol IPR100 (Local/Int l) IPR110Plus (Local/Int l) IPR400 (Local/Int l) Original 4.14/ i 4.14/ i 3.06/ i New 5.00/ i 5.00/ i 3.07/ i The original serial pass-through protocol existed up to version 4.14/ i of the IPR100 and IPR110+ firmware and up to version 3.06/ i for the IPR400. The protocol had to change to support the multi-drop feature which was implemented in version 5.00/ i of the IPR100 and IPR110+ and version 3.07/ i for the IPR400. Therefore, the incompatibility to previous versions lies at version 5.00/ i (IPR100/110+) and version 3.07/3/07.02i (IPR400). Version 5.00/ i (IPR100/110+) and version 3.07/3/07.02i (IPR400) are compatible with each other. This change in protocol is hardware independent allowing units in the field to be updated to the latest firmware version and therefore support the latest serial protocol. IPR400 Product Manual 85

100 Serial Port Parameters The following settings must match the serial settings of the device connected to the serial port of the IPR400. Baud Rate is the serial data rate in bits per second. The allowed values are: 1200, 2400, 4800, 9600, 19200, and The default is Data Bits specifies the number of bits in the data. The allowed values are 7 or 8. The default is 8. Stop Bits specifies the number of bits used to designate the end of the data. The allowed values are 1 or 2. The default is 1. Parity is a basic error-detection scheme. The allowed values are: None, Odd or Even. The default is None. Flow Control specifies the method used to control the flow of data. The allowed values are None, Xon/Xoff or RTS/CTS. The default value is None. Inter character timeout controls how the RS232 data is collected and transmitted over the network. When the IPR400 starts receiving data, it will keep collecting data until it gets a time-out or the maximum message length is reached. The allowed values are 1 to 1000 milliseconds. The default is 100 milliseconds. Note If you set the value too long, the communication will be very slow. Maximum Message Length (bytes) is the largest block of data that will be sent over the network in a single packet. The allowed values are 4 to The default is Note If the number of bytes of data exceeds this value, the data will be broken up to several smaller packets. Serial Channel-Change Mode The IPR400 provides the ability to control the channel-change functionality of radios with an RS232 serial-control interface. This functionality is linked to a VoIP channel. That is, VoIP-Group Channel 1 controls the serial channel change connected to serial port 1. Figure 49 shows the configuration page for the Serial Data settings applicable to the Serial Channel Change mode. Configure the settings as required. 86 Configuring the IPR400

101 Figure 49. Serial Data configuration showing the Channel Change settings Enable serial radio channel change option enables the serial channel-change mode and disables serial pass-through mode for this serial port. The default setting is cleared (i.e., serial channel-change mode disabled). Enable Channel Change Lockout option enables the IPR400 to prevent channel-change operation while the radio is transmitting. The default setting is cleared. Radio Type is the type of radio that is under the control of the IPR400. For a list of allowed values, see Compatible Radios on page 88. The default setting is Codan NGT. Serial Baud Rate is the data transfer rate in bits per second of the serial port. The allowed values are 1200, 2400, 4800, 9600, 19200, and The default setting is Radio Device ID is the identity of the radio that is connected to the IPR400. If this value is set incorrectly, the radio will ignore commands from the IPR400 (Elman RTV-1124 only). Controller ID is the identity assigned to the IPR400 as the controller of the radio (Elman RTV-1124 only). Guard Timer Interval is the relay guard time in seconds during channelchange operation (Kenta KHF-2011 only). Copy Setting to Channel allows you to copy the settings for this channel to another channel to make it easier to configure the other channel. IPR400 Product Manual 87

102 Compatible Radios The serial channel-change mode of the IPR400 supports the following radios: Codan NGT series Spectra MX800 Simoco SRM9000 Tait CCDI-series Base Stations/Repeaters tested with TM8100, TM8110, TM8200, and TM9355 models Icom radios supporting the PC Command V2 protocol Elman DSC-1097 MF/HF DSC Receiver, Elman RTV-2095 VHF AM Airband Transceiver, and Elman RTV-1124 VHF FM Marine Band Transceiver Kenta KHF-2011 Channel Numbers The channel-change mode can be used with the DX-Altus Alto Operator Dispatch Console, RediTALK-Flex VoIP Radio Dispatch Console, or a 960CSD Console interfaced to an IPR device. The channels are allocated as follows: 1 to 899 available as standard channels. 900 to 903 report/control scanning and mute forcing on Codan radios only (supported on the obsolete DX64 system only: not supported on newer console systems at this time). Channels operate as follows: 900 Scanning and Mute are off 901 Scanning On, Mute Off 902 Scanning Off, Mute On 903 Scanning On, Mute On. 999 loss of communications with the radio. 904 to 998 reserved for future use. When a mute-force command is received, in addition to sending the command to the radio, the IPR400 will simulate a busy signal from the radio. Channel Configuration When the IPR400 instructs the radio to change channel, it issues a channel change command; the command may either specify a channel number or a channel name. The Codan radio is an example of a radio that requires a channel name whereas the Spectra MX800 requires a channel number. For radio types that require a channel name, such as the Codan NGT series and the Elman RTV-1124 transceivers, the channel-configuration table is used to associate a channel name to a channel number. For radios that do not require a channel name, such as the Spectra MX800, the channel-configuration table is not used. Elman uses ASCII characters in its channel number and the channel name that you add must include leading zeroes (e.g. 01B or 05 ). This table needs to match your channel-change set as defined on the SCU. The configuration settings for the channel table are described below: 88 Configuring the IPR400

103 Channel is the radio channel number that corresponds to the channel-change number sent by and reported to the Omnitronics Console. Setting this channel number to zero disables that particular entry in the table. The allowed values are 1 to 899 inclusive. The default setting is 0. Channel Name is the name configured for this channel in the radio. Leaving this setting blank means this entry will be ignored. The allowed value is an alphanumeric text containing no spaces. The default setting is blank. Session Initiation Protocol (SIP) Settings To display the configuration settings for the Session Initiation Protocol (SIP), select SIP on the menu as shown in Figure 50. SIP functionality is an option you can configure with this configuration interface. The IPR400 only supports inbound SIP connections from other Omnitronics radio gateways (IPR and DRG devices) and some Omnitronics Consoles (RediTALK-Flex and 960SIP ): it cannot initiate outbound SIP connections. The IPR400 can send/receive VoIP on connections established with SIP. It can terminate two-party (unicast) sessions only. For further information about SIP, refer to Session Initiation Protocol (SIP) on page 157. Figure 50. SIP configuration settings Enable SIP option enables SIP and allows the IPR400 to accept incoming connections from other Omnitronics radio gateways (IPR and DRG devices) and some Omnitronics Consoles (RediTALK-Flex and 960SIP). The default is disabled. SIP UDP Port is the port number used for SIP connections. The allowed values are 1025 to The default value of 5060 is the port assigned by the Internet standards body for SIP. IPR400 Product Manual 89

104 Note The port must match the one used by the device that will connect to the IPR400; and the value must be different to the port numbers used by the VoIP/RTP configuration. VoIP Group n, SIP User Name is the name used to validate an inbound SIP connection. If the SIP connection does not have the correct user name it will be rejected. A unique user name is assigned to each local VoIP Group. A valid user name may consist of alphanumeric characters (no spaces or punctuation characters allowed). The default name is group1. Disable changing transmit CODEC type option prevents the IPR400 from changing the codec type used to transmit audio when a SIP connection is received; the codec type used is specified on the VoIP/RTP configuration page. If this option is not selected, the IPR400 may change the codec type used to transmit audio when a SIP connection is received. Select this option in situations when the configured codec should not be changed, such as, when the GSM codec has been selected for the main VoIP link to reduce bandwidth usage; the IPR400 will still accept and decode received RTP audio packets that use a different codec type. Linking Radio and VoIP Channels Use the Linking Configuration page to configure the settings for Radio and VoIP linking settings. Figure 51 shows the default configuration settings. Figure 51. Linking configuration page Note Any changes to the link settings take effect immediately. 90 Configuring the IPR400

105 The settings on this page allow you to link groups of radios and VoIP channels together to configure powerful and flexible interoperable radio networks. Radios connected to an IPR400 can be linked with or without VoIP functionality. The IPR400 provides four VoIP channels that act independently of the four radio channels, and each VoIP channel can be linked to one or more of the radio channels. Linking Radios with VoIP When a VoIP channel is linked to two or more radio channels, those radio channels participate in a conference on the VoIP channel. Additionally, the radio channels can be linked to each other, thus creating an audio bridge with a VoIP connection. To link a radio channel with a VoIP Group, first select the VoIP Group Enable option on the VoIP/RTP configuration page for the particular channel. You then need to set up the VoIP/RTP settings for that channel accordingly. Finally, you can add the radio channel to the VoIP Group under Connect Radios: with VoIP, as shown in Figure 51. Linking Radios without VoIP The IPR400 can also link radios together without using VoIP groups: the IPR400 provides two local groups that can be used for this purpose. With the local groups, you can connect radio channels without transmitting audio over the network. Note The linker function using local groups is separate and independent from using either conference mode or multicast addressing. Independent VoIP Access to Radios (No Linking) In the example shown in Figure 52, the audio received on a configured VoIP channel is transmitted to the corresponding radio channel, while audio received on a radio channel is sent to the corresponding VoIP channel. The actual system operation (across the IP network) is dependent on the addressing mode that is chosen. Unicast addressing will create four independent radio links. A single multicast address would result in a unified radio network where each radio will link to every other radio. The example above assumes unicast addressing. Refer to the following pages for an example of multicast configuration. IPR400 Product Manual 91

106 Figure 52. Example of independent VoIP access to each radio (no linking) Independent VoIP Access to Radios (Linking) In the example shown in Figure 53, the configuration describes how each radio channel is accessed via its own VoIP connection (address). In addition, radios are linked in any combination using two link groups: Radio 1 and Radio 2 are in Local Group 1; Radio 3 and Radio 4 are in Local Group 2. In this example, audio will be transmitted between Radios 1 and Radio 2 of Local Group 1 and via VoIP devices 1 and 2, and the IP network to other connected IPR devices. Similarly, audio will be transmitted between Radio 3 and Radio 4 of Local Group 2 via VoIP devices 3 and 4 and the IP network to other connected IPR devices. 92 Configuring the IPR400

107 Figure 53. Example of Independent VoIP access with radio linking Shared VoIP Access to Radios (Linking) In the example shown in Figure 54, a number of radios are accessed via a common VoIP connection (address). The radios are also linked. This bridges the VoIP channel and the radio channels in to a single conference. Similar to the previous example, audio will be transmitted between linked Radio 1 and Radio 2 and via connected IPR devices, the IP network and VoIP device 1 to both Radio 1 and Radio 2. Similarly, audio will be transmitted between linked Radio 3 and Radio 4 and via connected IPR devices, the IP network and VoIP device 3 to both Radio 3 and Radio 4. IPR400 Product Manual 93

108 Figure 54. Example of Shared VoIP access with radio linking Local Linking In the example shown in Figure 55, the configuration describes two ways of connecting multiple local radios to an IPR400 and to a remote radio or console. The first two radio channels (Radio 1 and Radio 2) have local linking disabled and therefore can send and receive audio to and from the remote radio and console only. The second two radio channels (Radio 3 and Radio 4) have local linking enabled, and can therefore send audio to local Radio 3 and local Radio 4 as well as to a remote radio and console. 94 Configuring the IPR400

109 Note The IPR400 does not support local linking via voice activity detection (VAD). It can use the VAD to control the transmission (PTT) of the remote device; however, it cannot use VAD to control the local linking. Figure 55. Examples of Local linking enabled and disabled IPR400 Product Manual 95

110 Typical Configuration In the typical configuration shown in Figure 56, an IPR400 is used at a repeater site to provide interoperability between several disparate radio systems, including 800MHz trunk radio system. The system is configured so that the radios at the repeater site can be controlled and monitored from a remote destination over IP. ROUTER Figure 56. Typical configuration using an IPR400 to control linked radios The remote controller could be any number of devices including a radio link, a dispatch console or another repeater site. This example assumes that the remote device is required to control and monitor all of the channels on the IPR400 using a single unicast address. This effectively creates a bridge between the remote device and all four radios connected to the IPR400 allowing all devices to communicate with each other. Special Features TX audio delay on the 800MHz port to allow for channel setup VOX detection for a HF radio that does not provide a COS output Assumptions Remote controller address is IPR400 has a static IP address of and a subnet mask of This is a private IP address and therefore the IP network requires a router with a gateway address of connecting to the IPR400. The configuration for this application is shown in Figure 57, Figure 58, and Figure Configuring the IPR400

111 Figure 57. Network configuration Set CH1, 2, & 4 to Local-Mute Set CH3 to Local-VAD Figure 58. VoIP/RTP settings IPR400 Product Manual 97

112 Figure 59. Link configuration Capabilities Configuration Use the Capabilities page shown in Figure 61 to configure the radio capabilities for each channel. Display this page by selecting the Capabilities menu. Figure 60. Capabilities page 98 Configuring the IPR400

113 Omnitronics Communication API The Omnitronics Communication API shown in Figure 61 is used to communicate with the DX-Altus Server SCU. It sends the RSSI, ATIS, and capabilities information to the server. TCP/CCP Server enables or disables the Omnitronics Communication API used for connecting to the DX-Altus Server SCU. TCP Port Number specifies the port number used to connect to the SCU. This port must be unique for each IPR400 channel. Figure 61. Capabilities page showing the Omnitronics Communication API Capabilities The Capabilities section is a new section introduced in the IPR400 firmware (version 4.00 and later) as shown in Figure 62. The Capabilities section includes the following settings: Enable Channel Change enables or disables the use of the channel-change feature of the radio. Enable Selcall enables or disables the use of the selective calling (selcall) feature. Enable Alarm Tones enables or disables the use of tones to signal an audible alarm. IPR400 Product Manual 99

114 Enable Power Level enables or disables the ability to monitor and control the Elman RTV-1124 radio power level via Alto. This is done via the touch-and-hold menu or the toggle bar for the particular channel (see the Alto Dispatch Console User Manual ). Enable Radio Interface Status enables or disables the status messages to be sent from the Elman RTV-1124 radio to Alto. These messages include warnings such as low-power level, poor VSWR, and bad serial communications. These are displayed in Messages window in Alto. Figure 62. Capabilities page showing the Capabilities section ATIS Vessel Information The IPR400 can be configured to connect to an ATIS server. Information is provided in the form of an XML packet that is received and parsed by the IPR400 and then published to connected DX-Altus Server SCU devices. This is then forwarded to Alto and displayed on the channel button. Each radio channel is associated with a particular instance of an ATIS server. Several new parameters are included on the Capabilities channel pages under ATIS Vessel Information for each of the four radio channels to allow the user to set the ATIS configuration, as shown in Figure Configuring the IPR400

115 Figure 63. Capabilities page showing ATIS Vessel Information section The changes implemented in the ATIS include the following: Enable ATIS option enables or disables the ATIS functionality for this channel. ATIS IP address specifies the IPv4 address of the ATIS server. ATIS Port Number is the port number used to connect to the ATIS Server. If a radio channel is disabled or the port number is left at 0, the IPR400 will not attempt to make a connection to the ATIS server. Connection Check Time is used to periodically check whether the connection is up when no ATIS information is received for the specified interval (in seconds). Allowed values are 1 to 60 seconds with the default set to 20 seconds. The IPR400 System Status page will display the ATIS configuration for each radio. The connection status and also the current parameter values are extracted from XML data (see System Status on page 46). IPR400 Product Manual 101

116

117 Diagnostics and Updating the Firmware This chapter discusses the diagnostics tools and information provided on the various diagnostics pages and how to update the firmware in the IPR400 product, and includes the following sections: IPR400 and Radio Diagnostics Fault Reporting Using the Diagnostic Report Feature on page 105 VoIP/Group Diagnostics on page 107 Connections on page 108 Statistics on page 109 Updating the Firmware on page 111 Site Monitoring of Inputs and Outputs on page 113 IPR400 and Radio Diagnostics The IPR400 provides several diagnostics pages that can help you to diagnose and troubleshoot any problems that you may encounter using the IPR400 product. It also allows you to print and save diagnostic information, which will be required by Omnitronics support engineers to provide the best technical support possible. Figure 64 shows the radio Diagnostics page that is displayed when you select Radio under the Diagnostics menu. Figure 64. Viewing the Radio Diagnostics page IPR400 Product Manual 103

118 The Radio Diagnostics page is used to test the IPR400 Radio configuration and diagnose any problems. It includes the following diagnostic tools: Reset IPR400 restarts the IPR400. Print Configuration opens a new browser window that displays the existing configuration in a simple table format. You can print the configuration from this window. Diagnostic Report allows you to view and save diagnostic information that may assist you and Omnitronics technical support engineers in diagnosing and troubleshooting problems with the operation of the IPR400. Clicking on the Report button opens a new browser window that displays comprehensive diagnostic information about the operation of the IPR400. You can save the report to a file on your computer or print the report from this window. Note If you experience a problem with your IPR400, such as a particular channel is not operating as expected, please save the diagnostic report and it to Omnitronics technical support our technical support engineers will analyze the report and provide a solution to your problem (see Fault Reporting Using the Diagnostic Report Feature on page 105). Audio Loopback connects the local audio input to the local audio output for the channel; the loopback is done at the digital interface. To enable audio loopback, click the Enable button. Play test tone transmits a 1000Hz tone at the local audio outputs for the channel. To transmit a tone, click the Enable button. Local Push To Talk turns on the local output for the channel. To transmit, click the Turn ON button. DTMF/Selcall Transmit Sequence specifies a sequence of numbers to send via SELCAL or DTMF. Type the sequence of numbers in the box, and then click on DTMF or SELCALL button. Send DTMF sends the sequence of numbers in the DTMF/Selcall Transmit Sequence box to the local device as DTMF tones. To send the DTMF tones, click the DTMF button. Send selcall sends the sequence of numbers in the DTMF/Selcall Transmit Sequence box to the local device as a SELCAL sequence. When sending a Selcall, the sequence must have the same number of digits as the number of tones configured for Selcall. Click on the SELCALL button to send the selcall. The following diagnostics items will only be shown when the CTCSS functionality is enabled: CTCSS Transmit Frequency selects a CTCSS frequency to use for sending a test tone. Transmit CTCSS sends a CTCSS tone to a local radio/console when you click on the Enable button. 104 Diagnostics and Updating the Firmware

119 Fault Reporting Using the Diagnostic Report Feature If you are experiencing a fault or problems with your IPR400 product, it is highly recommended that you send a device diagnostic report, in addition to a detailed description of the fault, to Omnitronics Technical Support for further analysis (see Technical Support on page ii for further details). The following procedure provides step-by-step instructions for generating a diagnostic report for the IPR400. To generate a diagnostic report 1 Use your web browser to log in to the IPR400 (see Logging On on page 40). After logging in, the System Status page appears. 2 Under Diagnostics, click Radio to open the Radio Diagnostics page. Radio Diagnostics page Shows diagnostics tools and information Report button Opens the Diagnostic Report window 3 Click Report to open the Diagnostic Report window. Note If your browser uses a pop-up blocker (or in some cases, has the security settings set to the maximum), the diagnostic report may be blocked. In this case, you should disable your browser's pop-up blocker or reduce the security settings for your browser. IPR400 Product Manual 105

120 The Diagnostic Report provides detailed technical information about your IPR Click Save to save the diagnostic report. The generated report is saved in HTML format to the hard disk on your computer. Note You may need to use one of the alternate methods discussed in the side-bar Saving the Diagnostic Report below. Save button Saves the diagnostic report to your hard disk 5 Click Close to cose the Diagnostic Report window. 6 Create a new message addressed to support@omnitronics.com.au and attach the Diagnostic Report to the . Try to provide as much information as possible to assist Omnitronics support engineers in diagnosing and resolving the problem, including a description of the fault, how it occurs, when it occurs, and its effect. Saving the Diagnostic Report If your browser will not save the Diagnostic Report when you click the Save button, you can try the following alternate methods: right-click on the page and select Save Page As from the pop-up menu; or on the browser's File menu, select Save Page As. In the Save As window that opens, specify the location and file name of the Diagnostics Report you want to save (the default file name is report.asp.htm). If you still do not have any success in saving the Diagnostics Report, you can try the following: Highlight all the text on the web page using your mouse; or Right-click on the page and select Select All from the pop-up menu; or Select Select All from the Edit menu (you can also press Ctrl-A if you are using Microsoft Windows); and then right-click and select Copy from the pop-up menu (or press Ctrl-C if you are using Microsoft Windows) to copy the text to the clipboard. You can then open a text editor, such as Notepad or WordPad, and paste the text into a new document (you can also use a word processor such as Microsoft Word or OpenOffice Writer). After copying the text into the document, save the document to your computer in the default format with an appropriate file name. 106 Diagnostics and Updating the Firmware

121 VoIP/Group Diagnostics Figure 65 shows the VoIP/Group Diagnostics page that is displayed when you select VoIP/Group under the Diagnostics menu. Figure 65. Viewing the VoIP/Group diagnostics page The VoIP/Group Diagnostics page is used to test the IPR400 VoIP/Group configuration and diagnose any problems. It includes the following diagnostic tools: Select sound file selects a sound file (in.au format) from a list of sound files: busy.au, phone.au, ring.au, sample.wav, and start.au. Play sound (locally) plays the selected sound file to the local radio port on the IPR400. Transmit sound (send to network) sends the sound file to the network on the currently selected VoIP channels. Transmit Test Tone transmits a 1000 Hz test tone via the RTP link to a remote device. IPR400 Product Manual 107

122 Connections Figure 66 shows the Connections diagnostic page that is displayed when you select Connections under Diagnostics. Figure 66. Viewing the Connections diagnostics page This page allows you to view the active SIP connections and to manually disconnect connections for diagnostic purposes. 108 Diagnostics and Updating the Firmware

123 Statistics Figure 67 shows the Statistics diagnostics page that is displayed when you select Statistics under the Diagnostics menu. Figure 67. Viewing the Statistics diagnostics page Current Status Under Current Status on this page, you can view general information about the status of the IPR400 such as: IP Address is the current IP Address of the IPR400. System up time is the elapsed time since the IPR400 was last reset (displayed as days, hours, minutes & seconds). Free memory is the remaining unused memory (in bytes) in the IPR device. VoIP Group Status Under VoIP Group Status on this page, you can view the status of each VoIP group, which includes information such as: Group is the VoIP group number from 1 to 4 Enabled shows whether the group is enabled or disabled. IPR400 Product Manual 109

124 Remote Devices shows the number of remote IP devices connected in the group and communicating with the IPR400. This number includes connected IP devices that are not currently transmitting audio. Radio Status Under Radio Status, you can view the status of each radio connected to the IPR400, which includes information such as: Radio shows the radio port number from 1 to 4, which corresponds to one of the radio ports (RADIO-1 to RADIO-4) on the rear panel of the IPR400. Enabled shows whether the radio port is enabled or disabled. Push To Talk shows the current state of the PTT output of each radio port. Busy/Mute shows the status of the busy/mute input of each radio port. Selcall Received shows the last selcall received by this radio port (if the IPR400 device is configured for selcall). Selcall Transmitted shows the last selcall transmitted by this radio port (if the IPR400 device is configured for selcall). CTCSS Received shows the last CTCSS tone received by this radio port (if the IPR400 device is configured for CTCSS). CTCSS Transmitted shows the last CTCSS tone transmitted by this radio port (if the IPR400 device is configured for CTCSS). Note The transmit and receive status for the selcall and CTCSS will only appear on this page if the IPR400 is configured for selcall and for CTCSS. Channel Statistics Under Channel Statistics, you can view the details about the operation of the IPR400 such as the number of network packets sent and received by the IPR400 device, and the current transfer rate. As the IPR400 is capable of receiving audio from multiple devices, there may be multiple sources shown in this section, which includes the following parameters. Packets Sent is the number of complete network (UDP) VoIP packets sent. This does not include other packets such as web server data or SNMP packets. Bytes Sent is the total number of data bytes sent. This is the amount of UDP payload data, and does not include the overhead due to Ethernet protocol. Source Name is the name/address of other IPR/VoIP devices communicating with this IPR400, such as: IPR400:Group1@ Location is the location or name configured in the remote IPR400 device, such as: IPR400-52A1491-GROUP Diagnostics and Updating the Firmware

125 Source IP Address is the source IP address for this audio source, such as: Source UDP Port is the UDP Port for this audio source, such as: Received packets is the number of VoIP data packets received from the remote device. Duplicate packets is the number of packets that have been detected containing exactly the same data (network errors). Misordered packets is the number of packets that have arrived out of order, usually due to network delays. Packets arrived too late is the number of packets that have arrived after the point where they should have been played (network errors due to high latency). Current playout delay (ms) is how much audio the IPR400 device is currently holding in its jitter buffer. Current PTT State is the current state of the remote audio source requested for the local IPR400 PTT output. This will appear if the remote site currently has an active busy signal from a connected radio. Updating the Firmware The Firmware Upgrade page loads the latest firmware for the IPR400 device. Note that the device configuration settings may return to the factory default settings, so make sure you back up the configuration settings with the Backup/Restore menu (see Backing up and Restoring the Configuration on page 59) before updating the firmware. Figure 68 shows the Firmware Upgrade page. Figure 68. Updating the firmware To update the firmware in the IPR400 device 1 Click Browse to search for the firmware file on your computer (the firmware file is identified with a.bin.gz extension). IPR400 Product Manual 111

126 Important Do not decompress the.bin.gz file; the IPR400 uses the compressed binary image to save space in Flash memory. 2 Click Upgrade to commence the update process. Warning! Do not remove power to the device during the ugrade process, otherwise it may cause damage to the device or corrupt the firmware. While the firmware update is in progress, the page will display a progress indicator to keep you informed of the progress. Once the update process is complete, the page will display a message indicating that the firmware has been successfully verified and loaded into Flash memory. Important If the device fails to update the firmware, do not remove the power; try repeating the firmware update process again. 3 Click Restart to restart the IPR400 device. The IPR400 will not run the new firmware until the device is restarted. Once the IPR400 is restarted, you may need to log on to the configuration interface again if you want to check or change any of the configuration settings. 112 Diagnostics and Updating the Firmware

127 Site Monitoring of Inputs and Outputs Use the Site Monitoring menu to monitor the digital and analog I/O on the Site Monitoring diagnostics page, as shown in Figure 69. Figure 69. Diagnostics Site Monitoring page Digital I/O Using the Site Monitor page, you can monitor the state of the digital inputs and outputs. Clicking on a Digital Output button will activate the corresponding relay for that output in the IPR400. Analog Inputs All analog inputs (including board temperature and supply voltage) can be monitored here. The input range for the analog inputs is 0 to +5V. IPR400 Product Manual 113

128

129 Serial Monitor This chapter discusses how to use the built-in Serial Monitor with TeraTerm (serial communications software) via the RS-232 serial connector on the back panel of the device to perform basic configuration and troubleshooting, and includes the following sections: About the Serial Monitor Serial Communications Setup on page 116 Recovery Mode on page 117 Using the Serial Monitor on page 118 Resetting to Factory Default Settings on page 120 About the Serial Monitor The Serial Monitor is intended for technicians or Omnitronics support engineers to assist in diagnosing and troubleshooting problems. You should use the built-in configuration interface to configure the IPR400 device. Before using the IPR400 device for the first time, you will need to configure the basic network settings to suit your particular environment. The easiest way to do this is to use the Serial Monitor with serial communications software such as TeraTerm this popular serial communications software is freely downloadable from the Internet. You can use whatever serial communications software you like, however, the following section discusses how to set up TeraTerm to communicate with the Serial Monitor (see Serial Communications Setup on page 116). IPR400 Product Manual 115

130 Serial Communications Setup This section describes how to set up TeraTerm for use with the built-in Serial Monitor. The same steps should apply to other serial software. You can use the Serial Monitor to configure the basic network settings of the IPR400 device to establish network connectivity. You can then login to the configuration interface with your web browser to configure the IPR400. The Serial Monitor uses the RS-232 serial port on the back panel of the device to communicate with serial communications software, such as TeraTerm. The pin assignments of this connector are shown in Figure 70. Figure 70. RS232 serial connections If your computer does not provide any RS232 serial ports, you can use an RS232-to- USB adapter to connect to the IPR400. The port used for the adapter will appear as a virtual COM port in Windows. To connect to the Serial Monitor 1 Connect the serial cable from your computer to the device. 2 Apply power to the device. 3 Click Start, point to All Programs, point to Accessories, point to Communications, and then click TeraTerm. 4 On the Serial port setup dialog, select the port and then set the values as follows: Baud rate: 19200, Data: 8, Parity: None, Stop: 1 bit, and Flow Control: None. 5 Click OK to close the dialog. 6 Press Enter on the keyboard. You should now be connected to the Serial Monitor and see the IPR400 $ command prompt, as shown in the screenshot below. 116 Serial Monitor

131 You can now use the Serial Monitor to issue commands to the device, as discussed in the section Using the Serial Monitor on page 118. Note If the command prompt does not appear when you press the Enter key, it is possible that your IPR400 has Serial Pass-Through mode (or the Serial Channel-Change mode) enabled. In this case, you can enter the Serial Monitor through the back-door by following the procedure in the next section Using Recovery Mode with the Serial Monitor below. Recovery Mode This section discusses recovery mode and how to use it to recover the IPR400 when it is not responding in Serial Monitor mode (i.e. the command prompt does not appear when you press the Enter key). This will happen when either the Serial Pass- Through mode or the Serial Channel-Change mode is enabled preventing you from using the Serial Monitor. Using recovery mode, you can enter the Serial Monitor through the back-door and then use it to configure the basic network settings of the IPR400. The following procedure outlines the steps that you can take to recover the IPR device using TeraTerm (you can use some other serial communications program if you prefer). This procedure assumes that you have connected the IPR400 via the RS232 serial port to the computer. To recover the IPR400 1 Remove power to the IPR40. 2 Run TeraTerm if it is not already running. 3 In the TeraTerm window, while pressing the Ctrl-C keys at the same time, apply power to the IPR400. You should see the IPR400 start-up messages followed by the command prompt IPR400 $ similar to below: IPR400 Product Manual 117

132 You should now be able to use Serial Monitor to issue commands and configure the basic network settings, as discussed in the next section. Using the Serial Monitor The Serial Monitor is used to perform basic configuration and diagnostics of your IPR400. You can set the basic network settings, such as IP address, gateway address, and subnet mask to establish network connectivity with the device. You can also reset the IPR400 to factory-default settings (see Resetting to Factory Default Settings on page 120). The Serial Monitor is not intended for normal use: it is intended only for technicians or Omnitronics support engineers to assist in diagnosing problems and troubleshooting. It is recommended you use the configuration interface to configure the IPR400 all of the configuration commands provided by the Serial Monitor are available via the built-in configuration interface (see Configuring the IPR400 on page 39). Using the Serial Monitor, you can issue commands to: View the current configuration and change the basic network settings Reset to factory-default settings Send a network ping to test the network connectivity Perform diagnostic troubleshooting Before you can use the Serial Monitor, you should set up your serial communications software (see Serial Communications Setup on page 116). You can enter commands at the Serial Monitor command prompt by typing the command name followed by the command argument(s), and ending the command by pressing the Enter key some commands allow you to specify a command argument(s) to provide additional information for the command. 118 Serial Monitor

133 The common Serial Monitor commands used for basic configuration are listed below. Command aconfig defaults set ipaddress set dhcp ping reset Description Application Configuration command displays the current application configuration settings. Usage: aconfig <Enter> Resets all configuration values back to factor default settings. Usage: defaults <Enter> Sets the IP address. The format of the address is n.n.n.n where (n) can be any number between 0 and 255. Note: this will have no effect if the device is configured to use DHCP to automatically determine its IP address. Usage: set ipaddress <new address><enter> Enables or disabled dhcp mode. In DHCP mode the IP address of the device is automatically allocated by a server. Usage: set dhcp 0<Enter> to disable DHCP mode or set dhcp 1<Enter> to enable DHCP mode. Sends a special echo message to another machine on the network to test communications. Usage: ping <new address><enter> Causes the device to reset. Usage: reset<enter> To see a complete list of the available commands, enter help at the command prompt, as in the following example: IPR400 $ help <Enter> The Serial Monitor provides many commands in addition to those listed above. However, the additional commands are intended only for testing these are not intended for initial configuration or for use in a live radio network. Important If you set the IPR400 on a different IP network or subnet to the computer used to access it, you may not be able to access the configuration interface due to incompatible network settings. Note The Serial Monitor provides many more commands in addition to those listed in the table above. However, the additional commands are intended only for device testing and debugging, and are not intended for initial configuration or for use in a live radio network. IPR400 Product Manual 119

134 Resetting to Factory Default Settings You can use the Serial Monitor to restore the IPR400 to its factory-default settings by issuing the defaults command followed by the reset command. Note You might lose network connectivity with the IPR400 after restoring it to factory-default settings. In this case, you can use the Serial Monitor to set the basic network settings to match your network. The device is restored to the factory default settings listed below. Setting Default Device login Login URL (even serials) User name Login password (case-sensitive) (odd serials) omni ipr400 (lowercase) Local network (LAN) IP address (even serials) VoIP/RTP* (channel 1) SIP Subnet mask (network mask) (odd serials) Gateway address DHCP server Remote IP address Disabled RTP receive port (UDP) 5004 RTP transmit port (UDP) 5004 Session Initiation Protocol (SIP) * Note: VoIP/RTP channels 2, 3, and 4 are disabled by default (even serials) (odd serials) Disabled 120 Serial Monitor

135 Application Examples This chapter provides several examples of connecting radios to IPR400 devices in a network, and includes the following sections: Connecting Radios via ADSL and Internet Remote Radio Access Using Static Addressing (VPN or LAN) on page 128 Line Replacement Using VOX on page 131 Communicating with a DX-Altus Radio Dispatch System on page 133 Radio Dispatch Using SIP Connections from 960SIP12 on page 136 Radio Dispatch Using SIP Connections from RediTALK-Flex on page 139 Communicating via Multicasting on page 142 Communicating via Conferencing on page 143 Radio Linked to One VoIP Group with Link Failure on page 145 Radio Linked to Several VoIP Groups with Link Failure on page 146 Connecting Radios via ADSL and Internet Configuring networks is a complex issue, and there are many different ways that you can set up a network. The example presented in this section is just one way that you can use to connect two IPR400 devices on a network. Figure 71 shows the network configuration for this example, which consists of two sites A and B with each site containing an IPR400 device connected to a router in its own intranet; and each IPR400 device has four radios connected to it. Radio Radio Radio Radio IPR400 Site A (External Internet address) Router (IPR400) (Local LAN) IP Network (External Internet address) Radio Radio Radio Radio IPR400 Router (IPR400) (Local LAN) Site B Figure 71. Connecting IPR400 devices over the internet IPR400 Product Manual 121

136 In this example, the ADSL routers at the radio sites use Network Address Translation (NAT) and Port Forwarding to route data packets from an external class A IP address to an internal or local class C IP address (see Network Address Translation (NAT) on page 155). The external IP address of the router is mapped to two internal IP addresses: the IP address of the intranet gateway and the local IP address of the IPR400 device on the network. Table 9 lists the addresses used in this application. Note If you change the IP address and net mask of the IPR400, a situation may occur in which it is no longer possible to access the configuration interface from your computer. If this occurs, see Using the Serial Monitor on page 118 for information about how to change the IP address via the serial port of the IPR400. Table 9. IP Address details of routers and IPR400 devices Site A Site B IPR400: IPR400: Router external IP Address: Router external IP Address: Local LAN Gateway Address: Local LAN Gateway Address: Configuring the Network Site A comprises a small network of computers, operator work stations, and an IPR400 so the router is configured to use Network Address Translation and Port Forwarding to connect the IPR400 and the computers to the Internet. Site B comprises only an IPR400, so the router is configured to use NAT without port forwarding to connect the IPR400: in this configuration, the IPR400 is completely accessible from the Internet. Router Configuration for Site A The router at site A is configured to use port forwarding, which simply tells the router to which device (computer or IPR400) on the local area network to send the data. This allows the IPR400 at site B to reach ports on the IPR400 connected to the internal IP address (inside the LAN). The IPR400 uses Real Time Protocol (RTP) and Real Time Control Protocol (RTCP); for each RTP channel, two ports are required: the first is for the actual RTP voice data, and the second is used for RTCP control and status information. By default, the IPR400 uses the following ports: 5004 and 5005 for VoIP Channel and 5007 for VoIP Channel and 5009 for VoIP Channel and 5011 for VoIP Channel Application Examples

137 Hence, the router at site A will be configured to forward all UDP messages on ports 5004 to 5011 to the IP local address of the IPR400 device on the LAN. Table 10 lists the port forwarding required. Table 10. Port forwarding configuration for router at site A Protocol Remote Port External Address Local Port Local Address UDP UDP UDP UDP UDP UDP UDP UDP TCP The last configuration item, forwarding TCP remote port 8080 to local port 80 makes it possible to access the web server configuration of the IPR400 from the Internet. This is optional, but may be desirable for remote sites. IPR400 Configuration for Site A Once the router at site A is configured, the IPR400 at site A needs to be configured with the following network settings: IP Address: Network Mask: Gateway: Remote IP Address: The above network settings configure the IPR400 on the LAN network at IP address (you can use the configuration interface to change the network settings of the IPR400 to suit your environment). The combination of the network mask and gateway means that any IP address that starts with is a local address and will be sent via a local LAN. Furthermore, any IP address that starts with something other than is an external address. In this case, the IPR400 will direct the message to its gateway address (the ADSL router at ). The router will then forward the message to the Internet. However, because the router is using Network Address Translation, it will change the messages so that it looks like it has come from address Router Configuration for Site B The router at site B is configured to forward all messages to the IPR400. This is sometimes described as DMZ Host or Demilitarized Zone Host in the ADSL router documentation. Table 11 shows the IP address translation for the router at site B. IPR400 Product Manual 123

138 Table 11. IP network address translation for router at site B External Address Local Router Address Local DMZ Host Address This setup is still using Network Address Translation (NAT), so all messages from and to the IPR400 will appear to be going to the router s external IP address. In this configuration, all ports are automatically forwarded, so it will be possible to access the configuration web server over the Internet. IPR400 Configuration for Site B Once the router at site B is configured, the IPR400 at site B needs to be configured with the following network settings: Internet Address: Network Mask Gateway: Remote Address: The above network settings configure the IPR400 for IP address As with site A, any IP address that does not start with the local LAN address (10.0.0) will be sent to the gateway address of (the site B router). Connecting via ADSL and the Internet with Dynamic DNS Usually, internet service providers (ISP) assign dynamic public IP addresses to subscribers rather than fixed or static IP addresses; in this case, routers will experience a change in public IP address from time to time. This example shows you how to configure the IPR400 to use dynamic DNS to maintain communication even if the router s public IP address changes. With dynamic DNS, you configure the IPR400 devices to refer to each other by their fully qualified domain names this is assigned in the VoIP Remote IP address setting for the particular channel and enable Dynamic DNS with proper configuration on both. Use the information provided in Table 12 and Table 13 as a guide. In the event of a change in public IP address in either device, VoIP communication should be reestablished automatically. 124 Application Examples

139 Table 12. Configuration via ADSL with Dynamic IP for site A Config Page Setting Value Description Network Radio (Ch1/Ch2/Ch3/Ch4) Automatically obtain IP address Static IP Address Not selected Netmask Gateway Address Domain Name System (DNS) Server 1 Domain Name System (DNS) Server 2 Disables DHCP The is the local LAN address. To the outside world we appear at address Specify the IP address of one of your ISP DNS servers Specify the IP address of another of your ISP DNS servers or leave at Enable DNS Selected Enable the Dynamic DNS Client Public IP Service 1 Public IP Service 2 Device Domain Name Dynamic DNS Host Domain Name Dynamic DNS Host Port Dynamic DNS Host Authentication User Name Dynamic DNS Host Authentication Password Enable Channel om: com/automation/n asp homebase-klm.net members.dyndns.com Specify a URL to a web service that can confirm the public IP of the requester Specify a URL to a secondary web service that can confirm the public IP of the requester in case Service 1 fails Specify a previously registered fully qualified domain name for Site A Specify the domain name of your dynamic DNS update authority that manages the Device Domain Name currently 80 Make adjustments if port 80 is blocked by a local firewall and the service listens on another port dyndnsuser Specify the required user name required by the dynamic DNS host service for authentication purposes Specify the required password required by the dynamic DNS host service for authentication purposes All selected Ensure all four radio channels are enabled IPR400 Product Manual 125

140 VoIP/RTP (Ch1/Ch2/Ch3/Ch4) Enable Channel All selected Ensure all four VoIP groups are enabled Remote IP Address zone-xyz.net Specify the domain name of Site B for all four VoIP groups RTP Receive Port RTP Transmit Port 5004/5006/5008/5010 Ports for each of the four channels 5004/5006/5008/5010 Ports for each of the four channels Table 13. Configuration via ADSL with Dynamic IP for site B Config Page Setting Value Description Network Automatically obtain IP address Not selected Disables DHCP Static IP Address The is the local LAN address. To the outside world we appear at address Netmask Gateway Address Domain Name System (DNS) Server 1 Domain Name System (DNS) Server Specify the IP address of one of your ISP DNS servers Specify the IP address of another of your ISP DNS servers or leave at Enable DNS Selected Enable the Dynamic DNS Client Public IP Service 1 Public IP Service 2 Device Domain Name Dynamic DNS Host Domain Name Dynamic DNS Host Port com:8245/ p.com/automation/n asp zone-xyz.net members.dyndns.com Specify a URL to a web service that can confirm the public IP of the requester Specify a URL to a secondary web service that can confirm the public IP of the requester in case Service 1 fails Specify a previously registered fully qualified domain name for Site B Specify the domain name of your dynamic DNS update authority that manges the Device Domain Name currently 80 Make adjustments if port 80 is blocked by a local firewall and the service listens on another port 126 Application Examples

141 Radio (Ch1/Ch2/Ch3/Ch4) VoIP/RTP (Ch1/Ch2/Ch3/Ch4) Dynamic DNS Host Authentication User Name Dynamic DNS Host Authentication Password dyndnsuser Specify the user name required by the dynamic DNS host service for authentication purposes Specify the required password required by the dynamic DNS host service for authentication purposes Enable Channel All selected Ensure all four radio channels are enabled Enable Channel All selected Ensure all four VoIP groups are enabled Remote IP Address homebase-klm.net Specify the chosen domain name of Site A for all four VoIP groups RTP Receive Port 5004/5006/5008/5010 Ports for each of the four channels RTP Transmit Port 5004/5006/5008/5010 Ports for each of the four channels IPR400 Product Manual 127

142 Remote Radio Access Using Static Addressing (VPN or LAN) Figure 72 shows an IPR100 and IPR400 connected over a VPN or a LAN to control four radios using an Omnitronics Console or Handset. In this example, the devices use static IP addresses. Figure 72. Remote radio access using static addressing over a VPN or LAN Table 14 and Table 15 show the configuration values used at each site. Any configuration value not listed is left at the factory default setting. Table 14. Configuration of IPR100 at operator site with static IP addressing IPR100 Configuration Page Setting Value Description Network Location Name IPR100- Default (Basic) 52A1212 Automatically obtain IP address Unchecked No address server available. Manually configure all addresses Static IP Address Both the IPR100 and IPR400 must use the same first three octects (i.e ) Netmask Gateway Address Radio/Handset (Basic) Device Type Hand/Set Console Volume (output level) Tx Gain 0 db Expected audio input level Handset -10 dbm 128 Application Examples

143 VoIP/RTP (Basic) Remote IP Address IP address of the remote IPR400 RTP Receive Port Number RTP Transmit Port Number Table 15. Configuration of IPR400 at radio site with static IP addressing IPR400 Configuration Page Setting Value Description Network Linking* (with VoIP) Radio (Channel 1) Radio (Channel 2) Automatically obtain IP address Unchecked No address server available. Manually configure all addresses Static IP Address Both IPR100's must use the same first three numbers Netmask Gateway Address Radio1/ VoIP1/VoIP2/VoIP3/VoIP4 Checked Place Radios 1 to 4 in VoIP Group1 to enable the IPR100 to communicate with all four IPR400 radios at the same time. Radio2/VoIP2 Checked Place Radio2 in VoIP Group 2 Radio3/VoIP3 Checked Place Radio3 in VoIP Group 3 Radio4/VoIP4 Checked Place Radio4 in VoIP Group 4 Enable Channel Checked Enables channel 1 Volume (Output Level) Tx Gain 0dB Required output volume level Input Level Input Level - 10dBm Required output level from radio Enable Channel Checked Enables channel 2 Volume (Output Level) Tx Gain 0dB Required output volume level. Input Level Input Level - 10dBm Required output level from radio IPR400 Product Manual 129

144 Radio (Channel 3) Radio (Channel 4) VoIP/RTP (Channel 1) VoIP/RTP (Channel 2) VoIP/RTP (Channel 3) VoIP/RTP (Channel 4) Enable Channel Checked Enables channel 3 Volume (Output Level) Tx Gain 0dB Required output volume level Input Level Input Level - 10dBm Required output level from radio Enable Channel Checked Enables channel 4 Volume (Output Level) Tx Gain 0dB Required output volume level Input Level Input Level - 10dBm Required output level from radio VoIP Group Enable Checked Enables channel 1 VoIP Group Remote IP Address IP address of the IPR100 RTP Receive Port Number 5004 RTP transmit port number for IPR100 RTP Transmit Port Number 5004 RTP receive port number for IPR100 VoIP Group Enable Unchecked Disables VoIP Group 2 Remote IP Address Remote address disabled RTP Receive Port Number 5006 RTP transmit port number for VoIP Group 2 RTP Transmit Port Number 5006 RTP receive port number for VoIP Group 2 VoIP Group Enable Unchecked Disables VoIP Group 3 Remote IP Address Remote address disabled RTP Receive Port Number 5008 RTP transmit port number for VoIP Group 3 RTP Transmit Port Number 5008 RTP receive port number for VoIP Group 3 VoIP Group Enable Unchecked Disables VoIP Group 4 Remote IP Address Remote address disabled RTP Receive Port Number 5010 RTP transmit port number for VoIP Group 4 RTP Transmit Port Number 5010 RTP receive port number for VoIP Group 4 * Minimum requirement for linking configuration 130 Application Examples

145 Line Replacement Using VOX Figure 73 depicts the configuration for this example, which has 4-wire audio bearers linked via an IP link. As the communication equipment does not provide a COS output, it is necessary to implement a VOX function in the IPR100. The settings for this configuration are listed in Table 16 and Table 17. Figure 73. Line Replacement Using VOX Table 16. Configuration of IPR100 for line replacement using static IP addressing IPR100 Config Page Setting Value Description Network (Basic) Radio/Handset (Basic) Radio/Handset (Advanced) VoIP/RTP (Basic) Location Name IPR100-52A1213 Default Automatically obtain IP address Unchecked Static IP Address etmask Gateway Address No address server available. Manually configure all addresses Device Type Radio Input is via the 4-wire E&M Port Volume (output level) Tx Gain 0 db Required output volume Expected audio input level -10 dbm Nominal output level from radio. Voice Activity Detection Checked This enables to Voice Activity detection algorithm so that it can be used to trigger the VOX (default) VAD hold/hang time (milliseconds) Remote PTT/Busy Control Mode Transmit without Local BUSY/PTT signal 1000 Ensures the VOX does not turn off too quickly cutting off the end of the users audio (default) Local VAD The remote device (IPR400) is also using VAD to send audio Checked Enables the IPR100 to send audio without a local BUSY/PTT signal Remote IP Address IP address of the remote IPR400 RTP Receive Port 5004 Number RTP Transmit Port Number 5004 IPR400 Product Manual 131

146 Table 17. Configuration of IPR400 for line replacement using static IP addressing IPR400 Config Page Setting Value Description Network Automatically obtain IP address Unchecked Static IP Address Netmask Gateway Address No address server available. Manually configure all addresses Radio Radio Device Channel 1 In this example, the full-duplex radio is connected to channel 1 VoIP/RTP Channel 1 Enable Channel Checked Enables the radio channel Volume (output level) Tx Gain 0 db Required output volume Input level -10 dbm Nominal output level from radio Voice Activity Detection Enabled Enables the Voice Activity Detection algorithm so that it can be used to trigger the VOX (default) VAD hold/hang time (milliseconds) Transmit without local MUTE signal 1000 Set this to 1 second to ensure the VOX does not turn off too quickly cutting off the end of the users audio (default) Ignores state of radio MUTE Enables the IPR400 to send audio data without a local MUTE signal VoIP Group Enable Checked This enables the VoIP Group Remote IP Address IP address of the remote IPR400 RTP Receive Port 5004 Number RTP Transmit Port 5004 Number Remote PTT/Busy Control Mode Local VAD The remote device (IPR100) is also using VAD to send audio 132 Application Examples

147 Communicating with a DX-Altus Radio Dispatch System The IPR400 can be used to communicate with an Omnitronics DX-Altus Radio Dispatch System, as depicted in Figure 74. Each IPE in LIU (radio) mode installed in the DX-Altus sub-rack can support four VoIP channels, which can come from an IPR100, IPR110+, or other IPR400 devices. In this example, an IPR400 is connected to all four VoIP channels on the IPE. Both the IPE and the IPR400 use four pairs of consecutive port numbers for VoIP connections starting from 5004/5005 (for channel 1) to 5010/5011 (for channel 4). Figure 74. Communicating with a DX-Altus Radio Dispatch System Note The odd-numbered port numbers are used by RTCP and should not be used when configuring RTP ports. The settings for this configuration are listed in Table 18. Table 18. Configuration for use with Radio Dispatch System using static IP address Page Setting Value Description Network Automatically obtain IP address Unchecked No address server available. Manually configure all addresses Static IP Address Netmask Gateway Address Linking* Radio1/VoIP1 Checked Places Radio1 in VoIP Group1 Radio2/VoIP2 Checked Places Radio2 in VoIP Group2 Radio3/VoIP3 Checked Places Radio3 in VoIP Group3 Radio4/VoIP4 Checked Places Radio4 in VoIP Group4 IPR400 Product Manual 133

148 Radio (Channel 1) Radio (Channel 2) Radio (Channel 3) Radio (Channel 4) VoIP/RTP (Channel 1) VoIP/RTP (Channel 2) VoIP/RTP (Channel 3) VoIP/RTP (Channel 4) Enable Channel Checked Enables channel 1. Volume Tx Gain 0dB Set this value for the required output volume level. Input Level Input Level + 0dBm Set this value to the nominal output level from radio. Enable Channel Checked Enables channel 2. Volume Tx Gain 0dB Set this value for the required output volume level. Input Level Input Level + 0dBm Set this value to the nominal output level from radio. Enable Channel Checked Enables channel 3. Volume Tx Gain 0dB Set this value for the required output volume level. Input Level Input Level + 0dBm Set this value to the nominal output level from radio. Enable Channel Checked Enables channel 4. Volume (Output Level) Tx Gain 0dB Input Level Input Level + 0dBm Set this value for the required output volume level. Set this value to the nominal output level from radio. VoIP Group Enable Checked Enables channel 1 VoIP Group. Remote IP Address This is the IP address of the IPE. RTP Receive Port Number RTP Transmit Port Number 5004 RTP transmit port number for IPE channel RTP receive port number for IPE channel 1. VoIP Group Enable Checked Enables channel 2 VoIP Group. Remote IP Address IP address of the IPE. RTP Receive Port Number RTP Transmit Port Number 5006 RTP transmit port number for IPE channel RTP receive port number for IPE channel 2. VoIP Group Enable Checked Enables channel 3 VoIP Group. Remote IP Address IP address of the IPE. RTP Receive Port Number RTP Transmit Port Number 5008 RTP transmit port number for IPE channel RTP receive port number for IPE channel 3. VoIP Group Enable Checked Enables channel 4 VoIP Group. Remote IP Address IP address of the IPE. RTP Receive Port Number RTP Transmit Port Number * Minimum requirement for linking configuration 5010 RTP transmit port number for IPE channel RTP receive port number for IPE channel Application Examples

149 Use the DX-Altus Server main SCU to configure the IPE you must login to the main SCU to configure an IPE. Table 19 lists the configuration of the IPE used with an IPR400. It assumes the IPE is already installed in the sub-rack and added as a new LIU-mode IPE on the Settings > Devices > Local Devices page of the main SCU. Table 19. Configuring the IPE card to be used with an IPR400 Page Setting Value Description Network* VoIP** (Channel 1) VoIP** (Channel 2) VoIP** (Channel 3) VoIP** (Channel 4) Automatically obtain IP address Unchecked Manually configure IP address Static IP Address Static IP address for this IPE Netmask IP subnet mask Gateway IP gateway address VoIP Group Enable Checked Enables IPE VoIP Group 1 Remote IP Address IP address of the IPR400 RTP Receive Port Number RTP Trasnsmit Port Number 5004 RTP receive port of IPE channel 1 (must match the transmit port of channel 1 in the IPR400) 5004 RTP transmit port of IPE channel 1 (must match the receive port of channel 1 in the IPR400) VoIP Group Enable Checked Enables IPE VoIP Group 2 Remote IP Address IP address of the IPR400 RTP Receive Port Number RTP Trasnsmit Port Number 5006 RTP receive port of IPE channel 2 (must match the transmit port of channel 2 in the IPR400) 5006 RTP transmit port of IPE channel 2 (must match the receive port of channel 2 in the IPR400) VoIP Group Enable Checked Enables IPE VoIP Group 3 Remote IP Address IP address of the IPR400 RTP Receive Port Number RTP Trasnsmit Port Number 5008 RTP receive port of IPE channel 3 (must match the transmit port of channel 3 in the IPR400) 5008 RTP transmit port of IPE channel 3 (must match the receive port of channel 3 in the IPR400) VoIP Group Enable Checked Enables IPE VoIP Group 4 Remote IP Address IP address of the IPR400 RTP Receive Port Number RTP Trasnsmit Port Number 5010 RTP receive port of IPE channel 4 (must match the transmit port of channel 4 in IPR400) 5010 RTP transmit port of IPE channel 4 (must match the receive port of channel 4 in IPR400) * To select the Network page for the IPE, go to Settings > Devices, click the Local Devices tab, select the IPE in the list, click Edit, and then click the Network tab. ** To select the VoIP settings page for an IPE channel, go to Radios/Phones > Channels, select the IPE channel in the list, click Edit, and then click the VoIP tab. IPR400 Product Manual 135

150 Radio Dispatch Using SIP Connections from 960SIP12 The 960SIP12 can connect to a maximum of three IPR400 devices, as depicted in Figure 75, with each IPR400 providing four channels. The 960SIP12 uses the SIP protocol to make the connection and the network (or IPR400) configuration is performed in the IPR120. In an IPR400, each VoIP group can be independently set to accept incoming SIP connections. The IPR400 can accept a total of 12 simultaneous SIP connections amongst the four VoIP groups. An IPR120 will typically have four (of the available 12) SIP channels set aside for each IPR400 in the network, but this will depend on the network requirements. All that is necessary to set up the IPR400 is to enable incoming SIP connections, and to configure the SIP user names for each VoIP group. Figure 75. Radio dispatch using SIP connections from 960SIP12 The settings for this configuration are listed in Table 20 (for one IPR400 only). 136 Application Examples

151 Table 20. Configuration of IPR400 for radio dispatch system using SIP Config Page Setting Value Description Network Automatically obtain IP address Unchecked Static IP Address Netmask Gateway Address No address server available. Manually configure all addresses Linking* Radio1/VoIP1 Checked Places Radio1 in VoIP Group1 Radio (Channel 1) Radio (Channel 2) Radio (Channel 3) Radio (Channel 4) VoIP/RTP (Channel 1) Radio2/VoIP2 Checked Places Radio2 in VoIP Group2 Radio3/VoIP3 Checked Places Radio3 in VoIP Group3 Radio4/VoIP4 Checked Places Radio4 in VoIP Group4 Enable Channel Checked Enables channel 1. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level 0dBm Enable Channel Volume Checked Enables channel 2. Sets input levelto the nominal output level from radio. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level 0dBm Enable Channel Checked Enables channel 3. Sets input levelto the nominal output level from radio. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level 0dBm Enable Channel Checked Enables channel 4. Sets input levelto the nominal output level from radio. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level 0dBm Sets input levelto the nominal output level from radio. Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled). RTP Receive Port 5004 RTP transmit port number for channel 1. Number RTP Transmit Port Number 5004 RTP receive port number for channel 1. IPR400 Product Manual 137

152 VoIP/RTP (Channel 2) VoIP/RTP (Channel 3) VoIP/RTP (Channel 4) Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled). RTP Receive Port Number RTP Transmit Port Number 5006 This is the RTP transmit port number for channel This is the RTP receive port number for channel 2. Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled). RTP Receive Port Number RTP Transmit Port Number 5008 This is the RTP transmit port number for channel This is the RTP receive port number for channel 3. Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled). RTP Receive Port Number RTP Transmit Port Number 5010 This is the RTP transmit port number for channel This is the RTP receive port number for channel 4. Enable SIP Checked Enables SIP in the IPR400. SIP SIP UDP Port 5060 Uses the default setting (must match the configuration in the IPR120). VoIP Group 1, SIP user name group1 Uses the default setting (must match the configuration in the IPR120). VoIP Group 2, SIP user group2 name VoIP Group 3, SIP user group3 name VoIP Group 4, SIP user group4 name * Minimum requirement for linking configuration Uses the default setting (must match the configuration in the IPR120). Uses the default setting (must match the configuration in the IPR120). Uses the default setting (must match the configuration in the IPR120). Using the settings from Table 20 to configure the IPR400, the SIP URI address settings required for the IPR120 are listed in Table 21. For further information about how to configure the IPR120, refer to the IPR120 Product Manual. 138 Application Examples

153 Table 21. Configuration of IPR120 for radio dispatch system using SIP SIP URI Address Description IPR400 Channel 1 sip:group2@ IPR400 Channel 2 sip:group3@ IPR400 Channel 3 sip:group4@ IPR400 Channel 4 Radio Dispatch Using SIP Connections from RediTALK-Flex Omnitronics RediTALK-Flex can connect to a maximum of three IPR400 devices, as depicted in Figure 76, with each IPR400 providing four channels. Figure 76. Radio dispatch using SIP connections from RediTALK-Flex RediTALK-Flex uses SIP to make the connection and the network configuration is performed in the IPR400. In the IPR400, each VoIP group can be independently set to accept inbound SIP connections. The IPR400 can accept a total of 12 simultaneous SIP connections distributed over the four VoIP groups. RediTALK-Flex will typically have up to four (of the available 12) SIP channels set aside for each IPR400 in the network, but this will depend on the network requirements. All you need to do in order set up the IPR400 is to enable incoming SIP connections and configure the SIP user names for each VoIP group. Table 22 lists the settings in this configuration for one IPR400 only. IPR400 Product Manual 139

154 Table 22. Configuration of IPR400 for radio dispatch system using SIP Configuration Page Setting Value Description Network 140 Application Examples Automatically obtain IP address Unchecked Static IP Address Netmask Gateway Address No address server available. Manually configure all addresses Linking* Radio1/VoIP1 Checked Places Radio1 in VoIP Group1 Radio (Channel 1) Radio (Channel 2) Radio (Channel 3) Radio (Channel 4) VoIP/RTP (Channel 1) VoIP/RTP (Channel 2) Radio2/VoIP2 Checked Places Radio2 in VoIP Group2 Radio3/VoIP3 Checked Places Radio3 in VoIP Group3 Radio4/VoIP4 Checked Places Radio4 in VoIP Group4 Enable Channel Checked Enables channel 1. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level + 0dBm Enable Channel Volume Sets input levelto the nominal output level from radio. Checked Enables channel 2. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level + 0dBm Sets input levelto the nominal output level from radio. Enable Channel Checked Enables channel 3. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level + 0dBm Sets input levelto the nominal output level from radio. Enable Channel Checked Enables channel 4. Volume (Output Level) Tx Gain 0dB Sets the output level for the required volume. Input Level Input Level + 0dBm Sets input levelto the nominal output level from radio. Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled). RTP Receive Port Number RTP Transmit Port Number 5004 This is the RTP transmit port number for channel This is the RTP receive port number for channel 1. Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled).

155 VoIP/RTP (Channel 3) VoIP/RTP (Channel 4) RTP Receive Port Number RTP Transmit Port Number 5006 This is the RTP transmit port number for channel This is the RTP receive port number for channel 2. Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled). RTP Receive Port Number RTP Transmit Port Number 5008 This is the RTP transmit port number for channel This is the RTP receive port number for channel 3. Remote IP Address IP address of disables any static RTP connections on the VoIP group. The IPR400 will only accept dynamic RTP connections (established via SIP if enabled). RTP Receive Port Number RTP Transmit Port Number 5010 This is the RTP transmit port number for channel This is the RTP receive port number for channel 4. SIP Enable SIP Checked Enables SIP in the IPR400. SIP UDP Port 5060 The default setting (must match the configuration in RediTALK-Flex). VoIP Group 1, SIP user name group1 The default setting (must match the configuration in RediTALK-Flex). VoIP Group 2, SIP user name VoIP Group 3, SIP user name VoIP Group 4, SIP user name * Minimum requirement for linking configuration group2 group3 group4 The default setting (must match the configuration in RediTALK-Flex). The default setting (must match the configuration in RediTALK-Flex). The default setting (must match the configuration in RediTALK-Flex). Using Table 22 to configure the IPR400, the SIP URI address settings required for RediTALK-Flex are listed in Table 23. For further information about how to configure RediTALK-Flex, refer to the RediTALK-Flex User Manual (MNL-00196). Table 23. Configuration of RediTALK-Flex for radio dispatch system using SIP SIP URI Address Description sip:group1@ IPR400 Channel 1 sip:group2@ IPR400 Channel 2 sip:group3@ IPR400 Channel 3 sip:group4@ IPR400 Channel 4 IPR400 Product Manual 141

156 Communicating via Multicasting To link two or more IPR400 devices via multicasting, you need to configure the VoIP Remote Address to be a multicast address. The multicast address used will depend on the configuration of your network. Note If you are attempting to use multicasting via a large WAN or the Internet, all network routers between the IPR400 devices must support multicasting. Multicast addresses cannot normally be used on the Internet. Multicast Addressing is a protocol for efficiently sending data to multiple IPR400 devices at the same time over TCP/IP networks (see Remote Addressing on page 76 for further details). IP Addresses in the range of to are multicast address. Using any address from within this range will automatically put the IPR400 into multicast mode. Note Multicast addresses in the range to are reserved and should not be used. Multicast Addresses in the range of to are used for local addressing and should be used for multicast configurations where all IPR400s are on the same LAN, or are all configured on the same IP subnet. Multicast Addresses in the range of to are used for Internet-wide addressing. These addresses should be used for communicating over a WAN or over the Internet. In the example configuration depicted in Figure 77, three IPR400 devices are all on the same LAN/subnet, with IP addresses of , and Configure all Remote IP Addresses on all VoIP Channels as Leave the RTP receive and transmit port numbers as there defaults. These are: channel one: 5004/5004, channel two: 5006/5006, channel three 5008/5008 and channel four 5010/5010. Each VoIP channel on a VoIP group requires a different port number. If you use the same port number for two VoIP channels, both will be connected together and neither VoIP channel will operate correctly. The IPR400 has been used with multicast circuits with up to 32 devices on each VoIP group. This requires enabling the half-duplex mode to ensure only one IPR400 is transmitting at a time. It is recommended that only one destination address is enabled in such a configuration. 142 Application Examples

157 IPR Radio Radio Radio Radio Example of a Multicast Configuration CH-1 CH-2 CH-3 CH IPR Radio Radio Radio Radio CH-1 CH-2 CH-3 CH LAN IPR Radio Radio Radio Radio CH-1 CH-2 CH-3 CH Figure 77. Example of a multicast configuration Communicating via Conferencing Many networks, and some network devices, do not support multicasting. In this situation, it is still possible to achieve a multicast-like setup using the IPR400 conferencing mode. Note If you are attempting to use multicasting via a large WAN or the Internet, all network routers between the IPR400 devices must support multicasting. In the example configuration depicted in Figure 78, three IPR400 devices are all connected on the same LAN/subnet, with address , and IPR400 Product Manual 143

158 LAN Figure 78. Example of configuring the IPR400 for conferencing mode Each VoIP channel on a VoIP group requires a different port number. To link all the corresponding channels, the configuration values listed in Table 24 should be used. Important Do not use the same port number for two VoIP channels; otherwise, both channels will be connected together and neither VoIP channel will operate correctly. Table 24 shows the configuration of the VoIP parameters and conference destinations. The colour of the row in the table corresponds to the colour of the connection in the diagram. Table 24. Configuration of VoIP settings and destinations IPR400 Channel Remote Address Receive and Transmit Ports Conference Address 1 Conference Port Application Examples

159 Radio Linked to One VoIP Group with Link Failure In the example shown in Figure 79, both Radio 1 and Radio 2 are configured in the linker to be part of VoIP Group 1. A VoIP group will be deemed as operational if at least one network participant is connected. A VoIP group will be deemed as in a failure condition if no network participants are connected. IP Network Router Netw ork Interface VoIP Group 1 VoIP Group 2 VoIP Group 3 VoIP Group 4 Radio Interface 1 Radio Interface 2 Radio Interface 3 Linker Radio Interface 4 Figure 79. Example of radios linked to one VoIP group with VoIP link failure Participants using Radio 1 or Radio 2 can hear each other as both are linked together. However, if the group is in a link-failure condition, their voices will not be conveyed by VoIP group 1 to the network side. The Audible Link Status Alarm function (see Audible Link Status Alarm on page 73) of the IPR400 provides play back of an audio warning to linked radios when a VoIP link is unavailable (link-failure condition). If this function is enabled, and the VoIP group that is in failure experiences radio activity (mute or busy indication), audio play back of the selected audio file will commence after a configured turnaround time has elapsed. The turnaround time is the amount of time that must elapse after the last mute or busy indication has fallen away. Just prior to audio playback, the PTT output of each radio connected to the VoIP group that is in failure will turn on. On completion of audio playback, the PTT outputs will turn off. IPR400 Product Manual 145

160 Radio Linked to Several VoIP Groups with Link Failure In the example shown in Figure 80, Radio 1 is configured in the linker to be part of both VoIP Group 1 and VoIP Group 2. A VoIP group will be deemed as operational if at least one network participant is connected. A VoIP group will be deemed as in a link-failure condition if no network participants are connected. If VoIP Group 1 is in link failure but VoIP Group 2 is not a participant, communication via Radio 1 would be possible to devices in a conference on the network side of VoIP Group 2. If the Audible Link Status Alarm function is enabled on VoIP Group 1, the Radio 1 participant will hear the play back of the configured audio file as the VoIP groups function independently from each other. It is thus possible that Radio 1 participants may be listening to incoming audio received by the VoIP Group 2 whilst a VoIP link failure message gets mixed in. IP Network Router Netw ork Interface VoIP Group 1 VoIP Group 2 VoIP Group 3 VoIP Group 4 Radio Interface 1 Radio Interface 2 Radio Interface 3 Linker Radio Interface 4 Figure 80. Example of radios linked to several VoIP groups with VoIP link failure 146 Application Examples

161 Technical Reference This appendix provides specifications for the IPR400 and technical details about the protocols used by the IPR product family. It includes the following sections: Network Requirements on page 148 Encryption on page 149 IP Addressing on page 150 Multicast Addressing on page 151 Domain Name System (DNS) on page 151 Multicast Domain Name System (mdns) on page 152 Dynamic Addressing on page 152 Dynamic DNS on page 153 Network Address Translation (NAT) on page 155 VoIP Functionality on page 156 Real Time Protocol (RTP) on page 156 VoIP Functionality on page 156 Real Time Protocol (RTP) on page 156 VoIP/RTP Group on page 157 Session Initiation Protocol (SIP) on page 158 VoIP Channel Linking on page 159 Simple Network Management Protocol (SNMP) on page 162 Specifications on page 169 Notice of Compliance on page 170 IPR400 Product Manual 147

162 Network Requirements VoIP devices use the Real Time Protocol (RTP) for transferring audio across a network. Each VoIP audio channel requires a certain amount of bandwidth. This bandwidth depends on the compression used to encode the audio, which is determined by the codec used. Omnitronics VoIP devices support several standardized codecs with each one providing different levels of compression and audio quality. For a list of codecs supported by the IPR400, refer to Supported Codecs on page 70. You can use the following information to calculate the minimum Ethernet throughput requirements in kilobits per second (kbps) for a network between the DX-Altus Server sub-rack and IPR100, IPR110+, and IPR400 devices. Upstream/Downstream (to/from DX-Altus Server sub-rack) G kbps per radio channel (TX or RX) GSM 45kbps per radio channel (TX or RX) Other requirements for network connection between DX-Altus components: Dead time (periods of no network connection) must be less than 3 seconds Jitter must be less than 2 seconds as a worst-case scenario Service Availability is an operational requirement specified by the client Support is an operational requirement specified by the client The following discussion calculates the bandwidth usage of a single channel in one direction (note that this is a worst-case scenario as no channel should be on continuously). The IPR400 packetizes voice audio every 40 milliseconds and sends the packets at a rate of 25 packets per second. The IP/UDP/RTP overhead per packet is 320 bits. Hence, the overhead in kilobit per second (kbps) increases the bandwidth requirement for VoIP by about 8 kbps, as calculated below. Overhead (kbps) Bits per packet = 320 Packets per second = 25 Overhead per second = 320 * 25 = 8kbps (bits/packet * packets/second) The bandwidth requirement for each supported codec including the packet overhead is as follows: 148 Technical Reference

163 Codec Bandwidth (kbps) G = 72 G.726 ADPCM = 40 GSM = 22 Note The bandwidth calculation for each codec is the bandwidth consumed while transmitting on one half-duplex channel. As channels will only transmit when the radio is busy and/or VAD (Voice Activity Detection) is active, the actual bandwidth will be lower than the calculated values. In addition to voice packets, the IPR400 also sends RTCP (Real Time Control Protocol) packets; however, these are only sent once every 5 seconds. Hence, the amount of bandwidth used by these packets is negligible. No data is actually sent until a SIP connection is established. When multiple connections are active either from multiple SIP connections or from conferencing mode, each VoIP channel will consume the amount of bandwidth shown. If an IPR400 has 12 active SIP channels and is transmitting to all of them at the same time, the bandwidth used will be (as a worst-case scenario) 12 x 72kbps = 864kbps. Encryption The IPR400 can encrypt the network data so that a third party is unable to intercept and listen to conversations. Using an encryption algorithm, and enabling encryption, allows the IPR400 to encrypt all voice and control data. Encryption is the process of transforming information (referred to as plaintext) using an algorithm (called the cipher) to make it unreadable to anyone except those possessing special knowledge, usually referred to as a key. The encryption key is a text string that is user configurable. If the encryption key string is left blank, then a default string will be used. The IPR products support the following encryption standards: Data Encryption Standard (DES) is a block cipher with a key length of 56 bits. It is the least secure of the algorithms supported because it uses a short key. Advanced Encryption Standard (AES) is a more modern block cipher that can have a variable key length (Australia models only). The IPR400 supports both 128 bit and 256 bit key lengths. Note If encryption is enabled, all IPR400 devices must have encryption enabled and must be configured with the same encryption type and key. IPR400 Product Manual 149

164 IP Addressing The IPR product family currently does not support IPv6; only IPv4. Therefore, this section discusses IP addressing with respect to IPv4. All devices connected to the Internet or using IP for communication have an IP address. An IPv4 address consists of 32 bits expressed in a form consisting of four decimal octets separated by periods (dots), called dot-decimal notation. An example of an IPv4 address is The IPv4 address consists of two parts: the network address and the host address. The subnet mask determines what part of the IPv4 address is used to identify the subnet on which a device is located. A valid IPv4 subnet mask consists of 32 bits: a sequence of ones (1) followed by a block of zeros (0), expressed as dot-decimal notation. The sequence of ones (1) designates that part as the network address (subnet) and the block of zeros (0) designates that part as the host identifier. Not all IP addresses are created equal, and certain ranges of address have specific functions. Some addresses are allocated from the private address space for use as private networks while others are allocated for multicasting. Currently, three classes of IP addresses are commonly used: Class A (the largest) is identified by the first octet, which ranges from 1 to 126. Class B is identified by the first two octets, the first of which ranges from 128 to 191. Class C (the smallest) is identified by the first three octets, the first of which ranges from 192 to 223. The following shows the different classes and the range of addresses for an IPv4 Address. Class Range of First Octect Network Identity Host Identity Subnet Mask A a b.c.d B a.b c.d C a.b.c d Some first-octets have special meaning: First octet 127 represents the local computer, regardless of what network it is really in. This is mainly used for local loopback testing. First octet 224 and above are reserved for special purposes such as multicasting. Octets 0 and 255 are not acceptable values in some situations, but 0 can be used as the second and third octets (e.g ). 150 Technical Reference

165 Another type of private networking uses the link-local address range (in IPv4, the block x.x, which is also shown as /16, is reserved for this purpose). This address range allows a network device to auto-configure its IP address when Dynamic Host Configuration Protocol (DHCP) services are not available. If a host on an ethernet network cannot obtain a network address via DHCP, an address from to may be assigned pseudo randomly. The IP address space is controlled by the Internet Assigned Numbers Authority (IANA). Multicast Addressing Multicast addressing or multicasting is a method of implementing efficient one-tomany communications. The originating device sends a single packet and the network infrastructure will deliver the packet to all the devices that are listening to the multicast address. Any device that wishes to receive packets sent to a particular multicast address will need to join the multicast group. The protocol used to manage this process is the Internet Group Management Protocol (IGMP). The actual routing of multicast packets efficiently is complicated and is managed by the routers and switches that form the network infrastructure; this complexity is not visible to the end devices that simply have to join the group. The range of addresses from to is reserved for multicast addresses: using any address from within this range will automatically put the IPR400 into multicast mode. Note Addresses in the range of to are reserved multicast addresses and should not be used. Multicast Addresses in the range to are used for local addressing and should be used for multicast configurations where all IPR400s are on the same LAN, or are all configured on the same IP subnet. Multicast Addresses in the range to are used for Internetwide addressing. You should use these addresses for communicating over a WAN or over the Internet. Domain Name System (DNS) When accessing a web site or computer over the Internet, the address of the site or computer is usually expressed as a host name or a domain name such as These host names are actually converted into a numeric IP address using the Domain Name System (DNS), which is a naming system for computers, services, or any resource connected to the Internet or a private network. The DNS server provides the actual numeric IP address that corresponds to the host name. IPR400 Product Manual 151

166 A host name consists of two or more labels: the rightmost label is the top-level domain and will be something like com or au. Each label to the left specifies a subdomain of the higher domain on the right. Omnitronics IPR products include the support for sending requests to DNS servers and hence converting host names into numeric IPv4 addresses. Multicast Domain Name System (mdns) The Domain Name System converts hostnames into global IP addresses. For it to work, a host needs an allocated static global Internet Protocol address and access to a DNS server. On local networks, it is desirable to be able to address a device by name without either of these prerequisites. One technique to accomplish this is to use a protocol based on the Domain Name System that uses multicast messaging to resolve names without any central server. The mdns protocol is similar to the DNS protocol that is used for the Internet name resolution. Unfortunately Microsoft products do not support this protocol, so it is not possible to address IPR products by name from Windows. Devices that use mdns addresses use the special top-level domain of.local. This is a short cut to tell the software to use mdns rather than normal DNS to resolve the Internet Address. Note Devices that use an mdns address can cause difficulties if the network servers in an organisation are configured with an internal domain that uses.local as its identifier. Dynamic Addressing Most LANs allocate Internet Protocol addresses to computers and devices using a protocol called the Dynamic Host Configuration Protocol (DHCP). The network will have a DHCP server that provides all devices with their addresses. DHCP is also widely used for dial-up and broadband Interconnection. The DHCP assigns the IP address, IP subnet mask and default gateway. DHCP servers generally provide addresses with a lease on a particular address for a certain time. As long as the device is leased a particular address renews its lease, the address will remain allocated to that device. If the device does not renew the lease the address may be allocated to some other device or computer. If a device that is configured for DHCP cannot contact a DHCP server on start-up it will not have a valid Internet Protocol address. In this case a device can default to using addresses in the range Technical Reference

167 Dynamic DNS Dynamic DNS is a system for allowing an internet domain name to be assigned to a non-static public IP address. This makes it possible to remotely establish connections to network devices without the need of tracking their changing public IP addresses. Most internet service providers employ a technique of allocating IP addresses dynamically on demand unless clients desire a fixed IP address. As fixed IP addresses come at a premium, most internet users make do with dynamic IP addressing. Network devices that are hosting services behind routers with dynamically changing IP addresses will thus only be reachable by means of DNS lookup. For this to work, however, it is important that references to IP addresses are kept up-to-date. The onus of keeping the DNS server(s) up-to-date rests on either the router or at least one network device behind the router. Implementation The Dynamic DNS feature can be enabled on any IPR400 running firmware V3.07 or later. If this feature is enabled, the IPR400 will perform all dynamic DNS related operations; and it will be responsible for tracking changes in the public IP address by which the device will be reachable across the internet. As an IPR400 device will typically reside on the private side of a company's network (behind the public router), it will have a private IP address. In order for an IPR400 device to connect to a remote IPR400, it will need to know the public IP address of the router at the remote end. Furthermore, if the public IP address of the router changes, the Dynamic DNS feature will update its configured Dynamic DNS server. This involves an HTTP request to associate its fully qualified domain name to the new public IP address. Any subsequent name resolution requests should then resolve to the latest public IP address. The IPR400 configuration allows for all remote ends to refer to fully qualified domain names. This applies to the VoIP remote destination, conferenced remote destinations, and serial pass-through remote destination addresses. An additional feature of the Dynamic DNS is to perform periodic name resolution of these destination addresses provided they do not contain a raw IP address. If any of the configured remote devices experience a change in public IP address, the local IPR400 will perform the required housekeeping to re-establish the RTP, or the conferenced or pass-through communications. Additionally, any SIP conversation can also benefit by optionally forwarding the public IP address of the device to the remote side during SIP call establishment. IPR400 Product Manual 153

168 Compatibility The Dynamic DNS client is designed to be compatible with the DynDNS API as both DynDNS.com and No-IP adhere to this API standard. Minor modifications were made to the client to accommodate ChangeIP.com. The client may well be compatible with other Dynamic DNS host services if they adhere the the DynDNS API but this cannot be confirmed. The best approach will be to try your preferred dynamic DNS host service to see if the IPR400 is compatible with it. Configuration Figure 81 shows the different aspects of the dynamic DNS configuration. None of the Dynamic DNS features will work unless at least one DNS server field (see the blue frame) points to an actual DNS server that is reachable by the device. It affects the ability of the device to perform domain name resolution. A value of indicates that this setting is not in use. Ideally these DNS server fields should point to the IP addresses of the DNS servers of the ISP used to access the internet. Figure 81. Dynamic DNS configuration In order to log Dynamic DNS activity, configure the Syslog host address (green frame) to point to a network device running a Syslog daemon. Note Syslog does not exclusively log Dynamic DNS activity. The Public IP Service (settings in the yellow frame) should point to the URL of web servers that returns the public IP address of the requester. This public IP address should be available as a text string within the response in the IPv4 format (see IP Addressing on page 150). Examples of public IP servers are: 154 Technical Reference

169 It is best to use a public IP service with a concise text response. Dynamic DNS updates require at least one of these fields to point to an actual public IP service. It is best to have both configured for redundancy. The other Dynamic DNS settings (settings in the red frame) are required by the builtin dynamic DNS update client to keep the Dynamic DNS host informed about changes in the public IP address of the Device Domain Name. If any of these settings is left blank (not configured), dynamic DNS updates will not occur. Examples of Dynamic DNS Host Update domain names are: DynDNS.com uses members.dyndns.com no-ip uses dynupdate.no-ip.com ChangeIP.com uses nic.changeip.com The above examples are by no means endorsed by Omnitronics; however the product was tested with these and known to work perfectly at the time of publication of this document. The configured Device Domain Name must be registered with the authority configured in the Dynamic DNS Host Domain Name field. It may well be that the configured Device Domain Names are shared amongst a group of IPR devices because they sit behind the same router providing access to the internet, and they all form part of the same logical group. In such a case, ensure that Dynamic DNS is enabled on all devices, but only one of these devices has the Dynamic DNS Host Domain Name configured. The selected IPR400 device will thus be in charge of keeping the dynamic DNS host informed about a change in public IP address. All devices in the group will be in charge of their own dynamic name resolution activity and associated housekeeping. Network Address Translation (NAT) The process of Network Address Translation (NAT) involves a router replacing the source and destination addresses of IP packets as they pass through an ADSL router, as illustrated in Figure 82. Systems using NAT do so in order to enable multiple hosts on a private network to access the Internet using a single public IP address. As well as replacing the IP addresses, sometimes the IP port number can also be changed; this is sometimes called port forwarding. Figure 82. Using Network Address Translation (NAT) IPR400 Product Manual 155