Raven FlexGate 47800A-FLXG User manual

Last Updated on December 21, 2021
Rev 36
FlexGate User Guide
Copyright © 2021 RAVEN ELECTRONICS CORPORATION 4655 Longley Lane Reno #106, Nevada 89502

1/36
Table of Contents
1Initial Setup............................................................................................................................................................3
1.1 Package Contents ........................................................................................................................................3
1.2 Connecting the FlexGate Enterprise System................................................................................................3
2Creating Interfaces................................................................................................................................................6
2.1 How to add a new interface..........................................................................................................................6
2.2 Properties Common to all Interfaces.............................................................................................................7
2.3 The Action Plan Interface .............................................................................................................................8
2.4 The CAP Alert Handler Interface ..................................................................................................................9
2.5 The FXO (PSTN) Interface.........................................................................................................................10
2.6 The FXS (Phone/Station) Interface.............................................................................................................11
2.7 The HQi Client Interface.............................................................................................................................12
2.8 The IP Camera Interface ............................................................................................................................13
2.9 The IO Module Interface.............................................................................................................................14
2.10 The M4x Blade Audio Channel Interface....................................................................................................15
2.11 The NEXEDGE TRS Interface....................................................................................................................16
2.12 The Relay Module Interface........................................................................................................................17
2.13 The SIP Endpoint .......................................................................................................................................18
2.14 The SIP Conference Channel Interface......................................................................................................19
2.15 The RTP Unicast Interface .........................................................................................................................20
2.16 The Voter Interface.....................................................................................................................................21
2.17 The Zello Interface......................................................................................................................................22
3Creating Communication Patches.......................................................................................................................23
4Configuring ESChat.............................................................................................................................................24
5Using HQi............................................................................................................................................................25
5.1 HQi Introduction..........................................................................................................................................25
5.2 The User Interface......................................................................................................................................25
5.2.1 Interfaces ...............................................................................................................................................26
5.2.2 Patches and Multiselects........................................................................................................................26
5.2.3 SIP Controls...........................................................................................................................................27
5.2.4 The Lower Display Panel .......................................................................................................................27
5.2.5 The Options Menu..................................................................................................................................30
5.2.6 HQi System Settings Tab.......................................................................................................................31
5.3 SIP Functionality.........................................................................................................................................32
5.3.1 Making Operator to Operator SIP Calls..................................................................................................32
5.3.2 SIP Paging .............................................................................................................................................33
5.3.3 Controlling Interfaces with SIP Accounts................................................................................................33
6Creating and Using Action Plans.........................................................................................................................34
6.1 What are Action Plans?..............................................................................................................................34
6.2 Creating an Action Plan..............................................................................................................................34

2/36
6.2.1 Adding Action Items ...............................................................................................................................34
6.2.2 The Text-To-Speech action item............................................................................................................35
6.2.3 The IO action item..................................................................................................................................35
7Troubleshooting...................................................................................................................................................36
7.1 On the website, all of my interfaces are showing 0/0..................................................................................36
7.2 My HQi Client interface isn’t displaying any interfaces or patches..............................................................36
7.3 I created a new interface, but it isn’t displaying on my HQi Operator’s screen. ..........................................36

3/36
1 Initial Setup
1.1 Package Contents
•One FlexGate Enterprise System (47800A-FLXG)
•One Power Cable and Power Adapter
•Two Flanges and Mounting Screws
1.2 Connecting the FlexGate Enterprise System
To configure the FlexGate system for first use, access the FlexGate using a PC and the supplied Ethernet cable. This
direct-connection procedure only needs to be done once. After this procedure, accessing the FlexGate will be done
through the network and over any network port.
Figure 1-1: FlexGate Back Plane Diagram
1. Refer to Figure 1-1 to connect the power jack to the rear DC 12V power port and plug-in the FlexGate.
2. Press the power button on the front of the FlexGate to start the unit. Wait at least three minutes to ensure
the machine has completed booting.
3. Connect a CAT 5 Ethernet cable to the NIC0 port. Connect the other end to a Windows PC. When plugged
into NIC0, there should be a solid green LED and a blinking yellow LED.
4. On the PC used to configure to the FlexGate system, navigate to Control Panel > Network and Internet >
Network Connections. Choose the Ethernet adapter that you plugged into the machine and go to
Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties.
5. Configure your network adapter with the following parameters. Please take note of your current settings
so that you can revert them after FlexGate provisioning is finished.
IPv4 Address: 192.168.100.10
Subnet mask: 255.255.255.0
Default Gateway: [Leave Blank]
Preferred DNS server: [Leave Blank]
Secondary DNS server: [Leave Blank]

4/36
6. Open a web browser and type http://192.168.100.1 in the Address bar to access the FlexGate Web
Configuration.
Note: If you are unable to access the web page, verify that the Ethernet cable is plugged into
the NIC0 port on the FlexGate and/or attempt to access the FlexGate at address
http://192.168.100.2
7. Figure 1- shows the log in screen for the FlexGate Configuration webpage. Use the default username Admin
and password 123456 to login.
8. Click the Network link at the top right of the page.
Note: It is possible to reconfigure the default login credentials. You can do so by clicking on the
admin tab shown in the top right of the web interface after login.
Figure 1-2: Log in Screen

5/36
9. Enter the IP addressing for FlexGate in the form
provided (Figure 1-).
a. IP Address
Enter an IP address for NIC0 and NIC1.
This address is used to access the FlexGate
administrative interface. Once Commit
Changes is clicked,the old address no longer
accessible. Store this address for reference in
the future. Contact Raven Electronics if the IP
Address has been lost (775-858-2400).
b. Subnet Mask
Enter a Subnet address for NIC0 and NIC1. By
default, this address is 255.255.255.0.
c. Default Gateway
Enter a Default Gateway address for NIC0 and
NIC1
d. Primary DNS
Enter a primary DNS address for NIC0 and
NIC1.
e. Secondary DNS
(Optional) Enter a Secondary DNS address for
NIC0 and NIC1.
10. Click the Submit button. Disconnect the FlexGate from
your PC and connect the FlexGate unit to a local switch
or router using the NIC1 port. You should now be able to
access the FlexGate unit from any computer on the same
network by using a browser to navigate to the IP address
you supplied for NIC1.
11. Use another Ethernet cable to connect NIC0 to the
Internet.
12. If you need to access the FlexGate
from outside of a firewall, ensure that
the necessary ports are opened
and/or forwarded to allow the
FlexGate through. Refer to Figure
1- for the list of ports to forward.
Figure 1-3: Network Settings Webpage
Figure 1-4: The ports that must be forwarded to the FlexGate box
for proper functionality.

6/36
2 Creating Interfaces
2.1 How to add a new interface
You will be able to configure a variety of interfaces depending on the license you have purchased. You can see the
interfaces allotted to your system by examining the left-hand panel, as illustrated in Figure 2-1. You can create a new
interface by clicking on the name of it in the left-hand panel. Each interface represents a single endpoint to which audio
can be streamed to and from. Depending on the type of interface, this endpoint could, in turn, relay this audio to and
from numerous device (e.g. a SpectraLinkPtt interface relays to and from a multicast address).
Figure 2-1: Home screen for the FlexGate web configuration tool. The left side displays the different interfaces
that are available. The right side of the screen displays the interfaces that have already been created.
Note: If you don’t have any interfaces listed or they mistakenly show an incorrect number of
interfaces allotted, please refer to the troubleshooting section.
When traversing through interface configuration screens you will be provided with some descriptions of each individual
setup field as you click on them. Once an interface is configured, you will be able to enable or disable it at will from the
home page. Disabling an interface frees up a license for another interface of the same type, but also makes the interface
unable to transmit or receive audio.
The following sections illustrate the process for configuring specific interface types.

7/36
2.2 Properties Common to all Interfaces
Each interface has a set of fields that the user fills in to configure them. There are certain fields that are common to
many interfaces, which will be discussed in this section.
•Name
oThe label assigned to this interface.
•Transmit Gain
oThe amount of gain (volume) in dB to add to the audio that is going to the interface.
oAppropriate values are -20dB to +10dB.
oThe default value is 0.0dB.
•Receive Gain
oThe amount of gain (volume) in dB to add to the audio that is coming from the interface.
oAppropriate values are -20dB to +10dB.
oThe default value is 0.0dB.
•TX Audio Delay
oThe amount of time in milliseconds to buffer before sending the audio to the transmitter. This allows
the radio time to key up before transmitting.
oThe appropriate values are 0ms to 1000ms.
•Talk Group ID
oA numeric value associated to talk group number. If this interface is linked to a NEXEDGE TRS, the
value needs to be the same as the NEXEDGE TRS Interface, otherwise it can be any numeric value
to identify a talk group.

8/36
2.3 The Action Plan Interface
Uses
The Action Plan interface allows FlexGate to
perform various actions when the interface
is triggered by other interfaces, such as the
CAP Alert Handler interface.
Currently supported actions include:
•Generating and transmitting a
synthesized voice message to any
other interface within FlexGate
•Setting a pin on an IO module to
high (5v or 12v), to activate
external devices
For more information on the Action Plan
interface, see Chapter 6: Creating and Using
Action Plans.
Figure 2-1: The configuration screen for the Action Plan interface.

9/36
2.4 The CAP Alert Handler Interface
Uses
The CAP Alert Handler interface listens for traffic from GSS and
processes the Common Alert Protocol (CAP) messages that it
receives. Each box must be manually configured to receive these
messages from GSS—Creating a CAP Alert Handler interface
won’t ensure that the FlexGate receives alerts. Each handler can
be customized to trigger only when certain conditions are met. The
currently implemented handler only handles Earthquake
messages. If a CAP alert is received that matches the conditions
set, the specified Action Plan will be triggered. (See Chapter 6:
Creating and Using Action Plans for more information.)
Depending on the Alert Type selected, different fields will be
provided for the user to specify the conditions for activation.
For Earthquake Alerts, the box’s latitude and longitude must be
entered in the Admin page of the webconfig. These values are
used to determine the expected intensity and time until impact
(see Figure 2-3).
Figure 2-2: The configuration screen for a CAP
Alert Handler interface.
Figure 2-3: The latitude and longitude of the box setting in the admin page.

10/36
2.5 The FXO (PSTN) Interface
Uses
The FXO interface represents a traditional hardline phone.
Provided you have the correct module installed within your
FlexGate Blade, you can connect the phone into the blade and
use it to communicate with your other interfaces.
Explanation of Fields
•Blade Number
oThe number of the blade that this interface is
associated with. Blades are numbered from 1
to 11, starting with the top blade in a FlexGate
system.
oNote: If the blade is connected via USB to a
PC, use a blade number of 32.
•Channel
oWhich physical port on the blade the phone
line is connected to.
oPossible values are 1-8.
The remaining settings are for a SIP Account assigned to
the FXO. For information regarding the SIP settings, please
refer to Section 2.13.
Paging from a POTS Line
DTMF paging from a telephone system to a radio can be
accomplished by using the FXO module. First the paging tones
must be created in the admin page of the FlexGate web
configuration pages. A DTMF pattern must also be assigned to
each individual tone created. Now you will need to patch
together the FXO interface with the interface intended to receive
the page. This can be done using either HQi or in the tab labeled
patches on the FlexGate web configuration pages. Once this is
done dial the extension of the phoneline connected to FlexGate.
Then dial the DTMF pattern and the star key to initiate the tone
sequence.
Figure 2-4: The configuration screen for a FXO
interface.

11/36
2.6 The FXS (Phone/Station) Interface
Uses
The FXS interface represents a traditional phone line. Provided
you have the correct module installed within your FlexGate
Blade, you can connect the blade to the phone line. You will
need to use an HQi client to control the phone line.
Explanation of Fields
•Blade Number
oThe number of the blade that this interface is
associated with. Blades are numbered from 1
to 11, starting with the top blade in a FlexGate
system.
oNote: If the blade is connected via USB to a
PC, use a blade number of 32.
•Channel
oWhich physical port on the blade the phone
line is connected to.
oPossible values are 1-8.
•Switch Access DTMF Code
oThe dial code for accessing the switch
The remaining settings are for a SIP Account assigned to the
FXS. For information regarding the SIP settings, please refer to
Section 2.13.
Figure 2-5: The configuration screen for a FXS
interface.

12/36
2.7 The HQi Client Interface
Uses
The HQi Client provides dynamic control over the configuration and operation of the FlexGate system. While the
configuration website provides offline configuration of the FlexGate system, HQi allows operators to log into FlexGate
and modify patches, monitor traffic, or communicate directly with resources. Operators log into the FlexGate system
through a standalone HQi application, provided by Raven Electronics. For more information, see Chapter 5: Using HQi.
Explanation of Fields
•Username
oThe username that HQi operators will provide in order to log into the system to associate with this
interface.
•Password
oThe password that this HQi operator will provide to log into this specific interface.
•Available Interfaces
oIn the top box you will see all interfaces that this HQi Client does not already have the ability to
control. You can select multiple interfaces from the top box and then add them to the Controllable
Interfaces list. Interfaces that are not controllable will not be sent to the client.
•Available Patches
oThe top box holds a list of all patches that this HQi Client does not already have the ability to control.
If you want this HQi Client to be able to modify a patch, add it to the Controllable Patches box.
Note: If a controllable interface is in a non-controllable patch, the HQi client will still have the
ability to remove the interface from the patch. Please configure your HQi Clients
appropriately.
Figure 2-6: The Edit page of an HQi Client.

13/36
2.8 The IP Camera Interface
Uses
The IP Camera interface is used to provide HQi operators with
the ability to monitor local or remote IP cameras or other RTSP
video streams.
You can configure multiple IP Camera interfaces and then give
HQi clients the ability to view the streams. Clients will be able to
view multiple cameras at a time, as seen in Figure 2-8.
Explanation of Fields
•Name
oSomething to identify the Camera stream by.
•Camera Stream Address
oThe link to the camera’s RTSP or HTTP
stream.
•Username and Password
oIf the stream requires credentials, you can
enter them here or, if you know the proper
format for providing them in the URL, you can
provide it in the stream address.
Figure 2-7: The configuration screen for an IP
Camera interface.
Figure 2-8: Two IP Cameras as displayed in the
HQi client interface.

14/36
2.9 The IO Module Interface
Uses
The IO Module interface is a simple interface that allows you
to control an I/O module through Action Plans. These
interfaces can’t be controlled directly, but they are necessary
when you wish to have an IO action within an Action Plan.
(See Chapter 6: Creating and Using Action Plans for more
information.)
Each pin can be configured for input or output mode. Output
pins can be set to output either 5v or 12v in order to trigger
external devices. Input pins can be configured to trigger
Action Plans when their threshold voltage is received.
Figure 2-9: The configuration screen for an IO
Module interface.

15/36
2.10 The M4x Blade Audio Channel Interface
Uses
An M4x Blade Audio Channel interface corresponds to a FlexGate Blade
port that accepts 4-wire or 2-wire analog audio devices. The attached
device can range from a radio, an intercom, a handset, or a custom
device that matches the pinouts.
Explanation of Fields
•Blade Number
oBlades are numbered in order from 1 to a maximum of 11,
starting with the top blade in a FlexGate system. Enter the
blade number of the audio resource you want to utilize in this
interface.
oNote: If using a blade that is connected to a PC via USB, you
should enter 32 for the blade number.
•Channel
oChannels are physical ports on the blade. Enter the channel
(1-8) of the port you want to use in this interface.
•Trigger on COR
oIf the device attached to this channel provides a COR input,
select this checkbox.
•Use Default Tone Key
oThis will send a default tone key of 2175 Hz instead of PTT
•Transmission Mechanism
oSelect whether the connected device uses a 2-wire or 4-wire
transmission mechanism.
•Receive Impedance
oThis can be changed from the defaulted 600 Ohm to High
Impedance
•Enable DTMF Detection
oMakes it so the M4x channel can detect DTMF and use those
numbers to dial out or patch interfaces together
•PTT Hold On
oAmount of time PTT stays on after the call ended
•PTT Delay
oAmount of time before PTT is asserted after a call is started
•High Pass Filter
oFilters everything below 300Hz
•Allow Recording
oThis allows recording to occur with this channel. The
recordings will automatically be sent to the Recording folder
in the FlexGate directory.
•Is Voter Member
oThis indicates this channel is part of a voter and changes the
way the FlexGate handles the dB adjustments (hardware vs
software). Do not click unless it is a part of a voter.
•Green Light Trigger
oDetermines what triggers the green LED on this specific port
•Red Light Trigger
oDetermines what triggers the red LED on this specific port
The remaining fields in the red rectangle are for linking an interface with a SIP
server. For more details on these fields, see Section 2.13 The SIP Endpoint.
Figure 2-10: The configuration screen for the
M4x 2-wire/4-wire Module interface.

16/36
2.11 The NEXEDGE TRS Interface
This interface allows you to connect to a NEXEDGE repeater via IP.
Explanation of Fields
•Name
oThe name of the channel on FlexGate.
•Console ID
oThe console ID as configured in the NEXEDGE Trunked System.
•System Code
oThe system code as configured in the NEXEDGE Trunked System.
This is a unique ID assigned to each system (1 to 131070.
•Site Code
oThe site code, or “Home Site Number” as configured in the
NEXEDGE Trunked System.
•Station Type
oThis is used to distinguish between registering to a
talk group or an individual.
•Station Name
oSpecific name given to the station.
•Station ID
oSpecific Station ID number.
•Network Category
oThe network category as configured in the NEXEDGE System.
•Is Ultra Narrow
oWhen checked, the NEXEDGE system is configured for
ultra-narrow channel spacing. Otherwise, it is narrow band only.
•Radio System Address
oThe IP address of the home site and is usually associated with
the smallest channel number at a home site.
•Bind To Address
oThe IP address of the network adapter that is associated with
the NEXEDGE Trunked System.
•Jitter Buffer Depth
oFor advanced use only. Default value is 60.
•Reregister Time (min)
oThe reregister time prevents the NEXEDGE System from
deregistering for being idle.
•Emergency alert Relay
oThis will be the relay module that will associate with the radio when
the emergency alert is triggered.
•Emergency Alert Relay #
oThis will be the relay number associated with the relay when the
emergency alert is triggered.
•Emergency Alert Time to Hold
oThis is an adjustable amount of time from 1 second
to 5 minutes
to have the relay active during an emergency alert.
•Encryption Type
oIf encryption is enabled in the NXDN system change to scramble.
•Key ID
oKey ID must be set to the Key ID programmed in the NXDN system.
•Key Data
oKey data must be set to the same Key Data value as in the NXDN
system.
Figure 2-11: The configuration screen for the
NEXEDGE Module interface.

17/36
2.12 The Relay Module Interface
The Relay Module Interface can be controlled directly either from HQi or can be manipulated through the Action Plan
interface in order to trigger external devices. Each Relay Module Interface corresponds to one port on the two-port
Relay module. Each port typically has 4 available relays. When relay 1 is open, pins 1 and 2 are bridged.
See Chapter 6: Creating and Using Action Plans for more information on interfacing with the Relay Module interface.
Figure 2-12: The configuration screen for the Relay
Module interface.

18/36
2.13 The SIP Endpoint
Uses
This interface acts as a bridge between SIP endpoints and
other interfaces to transmit and receive audio. All audios
sent to the SIP Conference Channel is rebroadcasted to all
interfaces that are patched with the channel, as well as all
SIP devices that are in a call with the channel’s associated
SIP account.
Explanation of Fields
•Name
oThe name of the SIP endpoint. This is the
name that will show up under the webpage,
HQi, and the patch fields
•Bind To Address
oThis is the bind to address if your FlexGate
has more than one IP address
•Talk Group ID
oA numeric value associated to talk group
number. If this interface is linked to a
NEXEDGE TRS, the value needs to be the
same as the NEXEDGE TRS Interface, else
it can be any numeric value to identify a talk
group Sip Display Name
•SIP Display Name
oThis is the name that will be displayed on the
SIP devices connected with this endpoint
•Sip Registration User Name
oThis needs to match the username under
your SIP server.
•Sip Password
oThis needs to match the password under your
SIP server.
•Sip Domain or IP Address
oThe domain or IP Address of the SIP server.
Your binding IP address needs to be able to
reach this address
•Sip Port
oTCP port for the SIP signaling. This is usually
left at the default 5060.
•Notify Endpoint on Key or Dekey
oFlexgate will respond with a voice message
on confirmation of keying or dekeying of the
radio while in a SIP call.
•Auto Answer
oThis makes it so this SIP endpoint will
automatically connect when called
•Registration Expiration Time (sec)
oThe amount of time the SIP account will try to
connect to the SIP server before expiring
•Call Timeout (sec)
oThis is the amount of time the call will end if
there is no audio between calls
•Is Cybertel Server
oCheck this box if the SIP server is a Cybertel
server. This is needed because Cybertel
servers have a slightly different protocol.
Figure 2-13: The configuration screen for a SIP
interface.

19/36
2.14 The SIP Conference Channel Interface
Uses
This interface acts as a bridge between SIP endpoints and
other interfaces to transmit and receive audio. All audios
sent to the SIP Conference Channel is rebroadcasted to all
interfaces that are patched with the channel, as well as all
SIP devices that are in a call with the channel’s associated
SIP account.
Explanation of Fields
The fields for this interface are typical SIP settings. For
more information, see Section 2.13 The SIP Endpoint.
.
Figure 2-14: The configuration screen for the SIP
Conference Channel interface.