Multinet Tools and Services (MTS)
by ASI Communications, Inc.
1042 E Guadalupe Rd
Tempe, AZ 85283
Table of Contents
Overview of MTS
Magnifying Glass - Search
Search Alarm History
1. Accounts Missing Data (Missing Information)
2. Ack-Delaying Radios
3. Inactive Radios
4. Most Active Radios
5. Most Active Repeaters
6. Unrestored Zones
7. System Trouble
8. Poor NetConn
9. Check In Interval
10. Radios of Interest
11. Radio Types
12. Message Queue
13. Link Level and Hops Summary
14. IP Link Event Summary
Admin Menu Options
Switch Business Unit
Switch Dealer #
1. User Administration
2. MTS Server Settings
3. Business Unit Administration
4. Dealer Administration
5. Global User Administration
6. Alert Administration
MTS Agent Install Instructions
Network Map Menu
Magnifying Glass Icon
Go To an Address
Plot a Radio Number
Show Dealer #
Show … Mile Radius
Show ALL Radios
Routes and Alarm History
Show En-Route (Usage)
Show Top Path
Show Top 3 Possible Paths
✓ Inactive Radios
✓ Ack-Delaying Radios
✓ Radios with Trouble Conditions
Go To Location
Radio Map Menu
Show Routes Taken (7 days)
Show Top 3 Possible Paths
Show Repeater Usage
Radio Details Menu
Paper Clip Icon
Peer (Routing Table) History
Monthly signal counts
Radio # xxxx:
Peers (Routing Table):
Option Flags (Mode Data):
Packet Life Settings (TTL):
Glossary of Terms
MTS is a web-based application which replicates a Multinet Receiver's data in real-time in order to generate real-time reports, lists and maps of your network data.
The MTS Web Site was developed with and is best view using a PC running Google’s Chrome browser and on an iPad using the built-in Safari browser.
Retrieve "favorite" accounts which are marked by using the star button on a Radio Detail page.
Brings you back to the main start page.
Open a Radio’s Detail page. You will be prompted for a Radio # which is always 4 digits (Hex 0001 through FFFE).
Display traffic data as it is being received by the Multinet receiver.
An overview of current network traffic and account statistics (based on the last 24 hours).
Radio Totals indicate how many radios are actively sending signals compared to the Total number of radios in the Business Unit (including those marked as Disabled).
Alarm History represents the total of ALL Signals received in the last 24 (does not include inbound/outbound messages or text messages). The Radio Test counter includes TEST events received from the Radio Only (does not include iTap signals).
The Last Signal date/time is the time of the last Alarm History event logged. The date/time will turn bold and red if more than 10 minutes have passed since the last signal time. If you know you have traffic, then there may be problem with the MTS Agent or MTS Server.
You should always see AGENT ACTIVE in Green in the top right corner indicating the MTS Server is actively connected to the Multinet Receiver’s MTS Agent. This will turn Red and show AGENT UNAVAILABLE if there is a problem with the connection between the Agent and MTS Server. If the Agent is not Active, the data is not being updated.
Routes/Minute provides an indicator for how many new Route data records the MTS Server has imported from the Multinet Receiver in the last 60 seconds.
Signals/Minute are the number of Alarm History events received on the network in the last 60 seconds.
ACK-DELAYs/Minute are the number of Ack-Delay signals received in the last 60 seconds.
Most ACK Delays in last 24 Hours: the top five radios logging the most Ack-Delay events in the last 24 hours. Click on this header to view the full list.
Most Signals in last 24 Hours: the top five radios with the most signals in the last 24 hours with a last-hour count as well. Click on this header to view the full list.
IP Links show you all the IP Links in the Business Unit including statistics regarding last time used, Top Peering, number of times used in the last 24 hours and what percentage of network traffic compared to all other IP Links in the Business Unit. Also includes the current status of the Modem, Check-In, RF Ping, and RF Jam flags based on the last Alarm History event received. Queue indicates the number of outbound messages waiting to be sent through that IP Link. RPM is the Routes record received in the last 60 seconds via this IP Link.
Consider an IP Link can handle approximately 20 signals per minute of continuous incoming Receive+Acknowledgements. If these were Alarm or TEST signals that contained Routing data with the packet, then the RPM of the IP Link would indicate such. A High RPM on IP LInks on a regular basis may be the indication of a saturated IP LInk..
Show all inbound and outbound messages and alarm history in real-time. This the the most comprehensive view of everything the Multinet receiver is sending and receiving on the network (known to MTS). Traffic can be filtered by the Type of traffic and for a single Radio by clicking on the List Options heading.
Display all alarm history events and routes on the map as they are received by the network. This is a live visual representation of inbound traffic from any radio on the network.
The Magnifying Glass is to search for Accounts and Alarm History.
All accounts can be listed simply by leaving all fields blank and clicking Search.
Restrict results to a specific Dealer #.
Choose a Search Field to search in:
Search For will look for the text anywhere in the Search Fields data.
Range Start and Range End will look for Search Field values between Range Start and Range End.
Check the boxes to show and hide radios marked as Disabled or ON-TEST.
Check the Show Radio Details to display more columns with current radio information:
Trbls - shows A/C, Battery, Etc. flags if radio has a pending trouble condition. RPTR means the Repeating function is disabled. ITAP means the IntelliTap reporting is disabled.
Test - current Periodic Test timer setting in the radio.
NAKs/Sigs - total number of Ack-Delay Signals / Total Signals in the last 24 hours.
Peers - Total of Good (+) peers : Total Peers and the last time the list of Peers has been received from the radio.
NC/LL - NetConn and Link Level of the radio and the last time it was received from the radio.
Model - the radios Model and Firmware Version.
Antenna - the type / location of the antenna; editable on the Radio Details page.
Last Route - the last known route a signal was received on with a counter of how many times it has used that route.
Display alarm history events based on periods of time and accounts and other criteria.
Dealer # and Account # will restrict results to just one Dealer #’s accounts or just one Account #.
Enter the Time Period you would like to include events from.
Check Just Statistics if you just want Total # of events. Choose Stats by Account or Status by Event from drop down to group statistic totals.
Signals can be filtered by Area, Code, Zone, or by text in the Description of the event. You can use SQL “LIKE” patterns:
A substitute for zero or more characters
A substitute for a single character
Sets and ranges of characters to match
[^charlist] or [!charlist]
Matches only a character NOT specified within the brackets
The Reports menu provides many reports used to identify problematic accounts, highly active accounts, and accounts with pending trouble conditions.
Each report has List Options:, a link that you can click on to include or exclude disabled accounts and accounts on-test.
All lists can be sorted by clicking on the column header.
Click on a row in a report to view the selected Radios Details.
Provides a list of accounts with a missing Name or Address or an address that could not be geocoded. The list also includes accounts that have not yet reported the following information: Model, Status, Peers, Mode, Timer, Zone, and TTL data. This information will be requested automatically by the MTS Server. Peers will also be requested automatically every 48 hours. You can request information manually at any time via the Request menu or the Get buttons on the Radio Detail page.
A list of radios that have reported one or more Ack-Delay signal in the last 24 hours. The DIstance displayed is the distance to it’s Top Peer (first hop). Peering ACK-Delays are the number of radios using this radio as a Top Peer and Ack-Delaying while trying.
A list of radios that have not sent any alarm history events in the last 24 hours.
A list of radios that have sent the most number of events in the past 24 hours and includes a count for the last one hour.
Identifies the radios on the network that have been used to repeat a signal for other radios. Due to the data necessary to compute this list, it could take a minute for results to return so please be patient.
Identifies radios that have sent an alarm or trouble condition on a zone where a matching restore has not been received yet.
Identifies accounts that have a pending radio low battery, trouble, ground fault, etc. condition.
A list of radios that have a NetConn of six or seven.
A list of radios ordered by the lowest average check in interval (based on last 24 hours of alarm history) and the values actually set in the radio. This report is used to identify radios that have unusually low checkin timers set or are reporting more frequently than expected.
Identifies accounts that may be causing problems for other radios on the network. This report is compiled using information such as distance, Ack-Delays, the number of radios using it as a top peer, how many of those are generating Ack-Delays, and the total Usage of the radio as a repeater. Radios used often as repeaters should ideally have short distances and should not be Ack-Delaying.
A list of the radio models and versions that have been detected on a network. Some of these models are known to have a chip version that needs to be upgraded to prevent the radio from reporting a NetConn six inadvertently when it should be a five.
A list of all of the messages sent and received by radios and the status of those messages. These messages may be text messages sent and received by technicians, data request messages or programming changes sent via the web interface.
Identifies the number of accounts reporting different Link Levels in comparison to the number of actual hops they are taking to arrive at the IP LInk. Link Level would imply that is how many Hops it will take under normal conditions.
All events logged by all IP links in the last seven days. These may include Check-In Failure and Restorals or RF Jam events, etc.
Options to show your entire network on the map. Shortcuts are included to show radios that are inactive, Ack-Delaying, and have radio trouble conditions. Radios can also be shown on a Google earth map color-coded by NetConn and Link Level.
Shows signal counters from ALARM history over a period of time on a line graph; different types of signals can be combined on one graph.
The first line shows who you are logged in as. Click on the current user to change your password.
The current business unit you are logged into is displayed.
If your login is assigned to Business unit #0, then you can Switch to another Business Unit from this menu. Click on “switch to business unit…” to change business units. The page you are currently on will refresh with data for the chosen Business Unit.
Your current Dealer # is displayed.
If your login is assigned to Dealer # 0, then you can Switch to another Dealer #. Click on Switch Dealers, if available, to change the dealer number that you are working with to restrict all reports and views to a single dealer. Dealer zero always includes all dealers accounts within the Business Unit.
Add, remove, and edit users, set their allowed Business Unit and Dealer # and whether or not they can administer other users.
A user in Business Unit zero is administered under the Global User Administration menu; users restricted to a specific Business Unit greater than 0 are maintained under User Administration.
A Dealer in business unit zero has the ability to switch between business units from the Admin menu.
A User in Dealer # zero has the ability to switch dealers within the current Business Unit they are currently in..
MTS Server Settings section allows you to set the monitoring center name and monitoring center phone number which is used on the certificates for the AHJ for fire radios. Remote MTS Agent IP is the IP address that the remote Multinet server is connecting from (this restricts access to the MTS Server to just Your Multinet Server). The IP Address can be left blank to allow connections from Any address. Only the First connection will be maintained by the MTS Server. The MTS Agent Port is the port number that the server will be listening on for the agent's connection.
Messenger Settings for Alerts is used to configure the outbound mail server for sending Alerts regarding system problems. The Messenger Service must be running on your MTS Server.
Database Statistics provides version, disk space, and record counters for the MTS Server. The table counters are of the records for the Business Unit you are currently viewing. The counters at the bottom (“Need_...”) indicate Model, Mode, Timers, Zones, TTL, or Peers data that has never been received or is outdated and needs to be requested from radios.
The Database Tools allows you to view and remove old backups of your database as well as perform an immediate backup if you prefer to keep a copy longer. Automatic backups are held for 30 days before automatically removed. Backups that do not have an “Automatic” description will be maintained indefinitely.
Maintain and create new Business Units to be handled by MTS.
Business Unit Name - The Name of the Business Unit which also appears at the heading of every page.
Business Unit DB Name on MultiNet - The Database Name of the Business Unit as defined by the Business Unit Name on the Multinet Receivers Admin pages. This is Case Sensitive and must match exactly for the Business Unit to be accessed.
Also enable and disable the MTS functions that are being performed in that business unit.
Enable Data Replication - Enables the MTS Server to continuously replicate all radio data for the Business Unit.
Enable Outbound Messages - Enables outbound data requests and text messages to be Sent to radios.
Enable Inbound Text-Messages - The MTS Server will check for inbound text-messages from the Business Unit. This feature requires SeriAll to be enabled on your Multinet Server.
Enable Auto-Request for Missing Data - The MTS Server will automatically queue up requets for data from radios that it has not received yet or is out-dated.
Database Utilities will be available for the Business Unit that you're currently logged into which is highlighted as red on the list of business units. Database Utilities are typically used after an initial replication of data on a Business unit.
Import Account Data - Provides you with instructions to upload a TAB-Delimited list of Account Information to update your radio details with valid address and dealer information.
Delete Accounts with No Routes - Removes accounts that do not have any route history data. This would imply the radio account was created at some point but never used or at least not in the last 30 days or so.
Delete Inactive Accounts (No Alarm History) - Removes accounts that do not have any Alarm History in the last 30 days.
Delete Business Unit - Removes the business unit and all accounts and data and users associated with it.
Assign names with dealer numbers. The Dealer Name will show up on the Radio Details based on the Dealer # assigned. All data can be filtered by Dealer #. Modifying or Deleting a dealer number does not affect any radio accounts related to that dealer. It is not necessary to populate the Dealer # table, you can still assign Dealer #’s to radios for filtering. The Dealer Name and Phone # are used when generating a Certificate for a Fire Radio.
Edit Users in Business Unit zero, which allows them access to All Business Units. A Global User can be restricted to an individual Dealer #, which allows them to switch Business Units but still only have access to an individual dealer within each Business Unit. By checking the Administrator checkbox the user will also have access to add, edit and remove users within the Business Unit and Dealer # they are currently restricted to.
Configure Alerts to be sent when IP Links have trouble conditions or the MTS agent is not checking in properly with the MTS server. Please contact technical support to configure Alerts.
Step-by-step instructions and videos to assist the Multinet Server administrators in the installation of the MTS Agent necessary to communicate with MTS server. Includes instructions to install an Agent on the Backup Multinet Server to replicate Alarm History events over to the Primary Server and instructions on how to enable SeriAll to enable inbound Text-Message retrieval.
Display contact information for MTS servers technical support team.
Launch an external site which we built to aid technicians and installers in finding phone numbers, web sites, and shortcuts to documentation. You can submit documents and links to firstname.lastname@example.org if you have something useful to add.
You can click the ? Icon in the menu to show on-screen help/hints for the page the you are on.
Clicking anywhere on the map will display the elevation of that location.
Options to enable the mapping of signals and routes in real-time.
Note: not All events contain route data and not all routes are for an event so it is not unusual to see events without routes (iTap events do not contain route data) as well as routes without events (status request may return a route and update status without generating an event).
Show radios on the map.
Enter an address to jump to on the map.
If you are on a Radio’s Map, the marker for the account will move to this new location. You can then move the marker to a more specific location and click “Save These Coordinates” button to update the Account (only the coordinates will be updated, Not the Address).
Enter a four digit radio number to jump to that radio on the map.
Check the box and enter a Dealer # to restrict the displayed radios to a Dealer #.
Show all Active Radios in the Business Unit within … miles of the center of your map. If Dealer # is checked then the list is restricted to just one Dealer's radios.
Show ALL radios in the Business Unit (marked Active and sending signalin the last 24 hours). All radios will be displayed, but Radio Account Names and Details are not available to Users who are not of the same Dealer # as the Radio’s Dealer # (unless the user is in Dealer 0 or the Radio is in Dealer 0 in which case All information is accessible).
If Dealer # is checked then the radios displayed are restricted to just one Dealer's radios.
Remove all radio icons shown on the map.
Remove all route and peer lines from the map, including Alarm History slider data.
Map Alarm History events and routes based on a period of time. Use the slider at the bottom of the screen to narrow the timeframe shown on the map and move through time.
RED= Long Route - when a route is more hops than the radios Link Level, the route line will be Red.
RED= Bad Hop - when a radio relays a signal to a radio that is not its Top Peer then just that hop of the route line will be Red.
Pick what you want to be displayed when clicking on a radio on the map.
Opens the Radio Details page.
Draws lines to the radios Peers. Red lines to peers that are not “GOOD”.
Draws lines of routes that passed through the radio.
Draw last seven days of routes used to deliver signals. Line colors are based on the RED= setting on the Routes and Alarm History search box.
Show lines to radios using the clicked radio as their Top peer. Red lines indicate a NOT “GOOD” signal strength.
Draw top path via first peer and all first-peers along the way.
Draw top three paths via first three peers and all subsequent top-peers along the way
Plots Radios that have not sent any signals in the last 24 hours (based on Alarm History events). The radios will refresh in real time if anything changes.
Plots Radios that have sent at least one Ack-Delay signal in the last 24 hours. Radios that have sent at least three in the last 24 hours will “bounce”. The radios will refresh in real time if anything changes.
Show radios that have a Radio System Trouble condition such as a Low Battery or Ground Fault condition. The radios will refresh in real time if anything changes.
Go to your default view and save your current view as the default.
The Map Legend will display the icon and line color legend for the map.
Click the Blue Marker icon on the map menu to jump to your current location.
If you are viewing a Radio’s Map then you can click on Save These Coordinates to update the markers' location for the radio without changing the radios Address.
The following options are available when viewing a Map of a specific Radio (accessed from the Map icon on the Radio Details menu).
Show all peers currently known for this radio.
Plot the routes used in the last seven days.
View all radios on the network that have this radio listed as their Top Peer.
Plot the routes based on the radios first three peers, using the Top Peer of all other radios in the route.
Plot all routes passing through this radio.
Jump to the Account on the map instead of your Default View.
Options to edit and import account information.
Importing is available when automation integration is available.
You can edit the name and address of the account for geocoding. Geocoding is required to be able to plot the radio on the map.
Leave the latitude and longitude with values of minus one (-1) to let the system automatically calculate the coordinates for the address entered. Once an account has a latitude and longitude, it will appear on the map. An address that can not be geocoded will have a latitude and longitude of 0 and 0 and will need to be manually updated.
You can also mark an account as Active or Disabled and On-Test or Off-Test. These settings do not affect a radio's operation, they simply allow you to filter accounts based on status.
When editing an account you can clear the radio data. This does not affect operation of the radio and does not clear any data in the Multinet Receiver.
You can also Delete a radio account, which will not affect the operation of the radio. The first time a signal is received, the account will be created automatically if it doesn't exist. No data is deleted from the Multinet Receiver.
You can not create a new account manually. A Signal MUST be received from a radio for it to show-up in MTS.
Launch the real-time traffic report, automatically filtered by this account number.
Launch the radio network map with options specific to the radio.
Attach images or documents to the account for access by all users who have access. These files are stored on your dedicated MTS Server and will be deleted upon discontinuance of service.
Options to request data from the radio. These are messages that are sent out to the radio. They should respond with the requested data. You will see these requests in the message queue and the radio detail page should refresh automatically when the data changes.
Make changes to the radio, if the radio will accept them. Newer fire radios (7788) will not except remote programming changes without a technician on-site. Burglary and older Fire radios will except remote programming changes at any time.
Various reports specific to this Radio.
Identifies all routes this radio has used to report a signal as well as routes that this radio was used in by other radios.
Past routing tables. Whenever a routing table or peers list as requested, the old list is stored for routing table history.
A a list of all the radios on the network that are using this radio as their Top Peer.
More Alarm history details with more search options.
All inbound and outbound messages for the radio.
A quick reference of how many signals the Radio has sent (Alarm History events) in current and prior months.
When you select a radio from a list or the Open icon, you will presented with all of the details for that radio on a single page. Here we describe each section.
You can collapse and expand sections by clicking on the section heading.
The date and time on the section headers indicate when the data for that section was last received by the radio. This may have been done automatically, or manually by clicking the get button.
The Radio # section includes the model, dealer, account information, antenna location, and provides options to Edit and Import the account name and address data. Clicking the Get button in the section will request Model details from the radio.
A Fire Radio with a NetConn of 5 or less will present a Certificate button which can be printed for your files or to submit to the AHJ as proof of compliance for radio connectivity.
The Activity button will present you with a dialog of recent Alarm History events. This list will refresh automatically so you can watch signals in real-time as they are received. Although, the Real-Time menu option is better for watching all activity.
The Messages button shows you history of inbound and outbound messages and allows you to send a Text Message to the radio.
The radio status section shows the NetConn, Link Level, number of signals in the last 24 hours, total Ack-Delay signals in the last 24 hours, and how many times the radio was has repeated a signal for another radio in the last 24 hours. You will also see the status of AC Power, Battery, ADC Failure, Charger Failure, Ground Fault, and Modem Fault conditions. Clicking the Get button will request the current status from the radio.
The Peers section (or Routing Table) is a list of the Peers last received by the radio as of the date indicated. The Peers are the radios this radio will attempt to talk through on its first hop out. A signal quality of “GOOD” indicates a passing received signal strength from the transmitting radio, “MARGINAL” indicates a less than good but not “POOR” radio. A “-” after good or marginal indicates slightly less than good or marginal but not quite marginal or poor. The distance is based on line-of-site to the latitude and longitude of the other radio.
The routes used section is a summary of the routes use in the last 30 days by this radio. Click the More button to view additional details regarding the routes used and how often this radio was used by other radios. The More button returns the same data that the route history/usage on the Reports menu.
Zone Status identifies zones that have reported an Alarm or Trouble signal and have not reported a Restore of the same zone.
Zone Types is a list of the zones as they are programmed in the radio. These are programmed on-site based on the devices being monitored.
The iTap section allows you to retrieve settings from an IntelliPro or FirePro module as well as changing some of the settings on those modules. Compatible with 7094 and 7794 modules.
The timer sections allows you to view as well as edit the timer settings on your radio.
Periodic Test - the interval at which a test signal is sent to the monitoring center.
Secondary Alarm Delay - the number of seconds the radio will wait before sending another signal over the air.
Contact Debounce - the amount of time a zone must be triggered before the radio detects it as being triggered.
Ack-Delay - the number of seconds a radio will wait for an acknowledgment before it will trigger the acknowledgment delay trouble output (J4 Relay on the 7788).
Options flags are settings in the radio to enable or disable various functionality. These can be sent via the control menu if the radio is accepting remote commands.
Packet life settings (Time To Live) are the amount of seconds a packet is allowed to bounce around on the network before it will expire and be dropped if undelivered.
Account - A Subscriber Radio and all data related to that radio.
ACK-Delay - Acknowledgement Delay. Some radios will report an ACK-DELAY event in Alarm History after it was unable to receive an Acknowledgement from it’s peer within the Ack-Delay Timer time period (typically 60 or 90 seconds). After the radio Does get an acknowledgement, it will send an ACK-DELAY event to let you know it had a delay in transmission due to lack of acknowledgement within a timely manner. There is no way to know how long the radio was unable to communicate, just that it is working again. Ack-Delays should be fixed, a normal radio installation should Never send an Ack-Delay.
Active - An Active Radio is considered a radio that has sent at least One signal (logged in Alarm History) in the last 24 hours AND Not marked as Disabled.
Active/Disabled - Marking a radio as Disabled does not affect the radio’s normal operations or reporting. This is a flag for your own convenience to prevent “disabled” radios from showing up in lists and maps and statistics. A disabled radio may still send signals, so this may be helpful to quickly identify radios that are communicating, but shouldn’t be.
Alarm History - when a radio sends a zone or system alarm or trouble event, the Multinet Receiver logs the signal in an "Alarm History" table. Also referred to as Activity.
Alarm Translations - Alarm Translations are configured via IPCtrl on the MultiNet Receiver. These allow the MultiNet Server to convert (Translate) incoming zone alarms and troubles to a different Event Type. Normally, an Alarm will report as a 140 General Alarm, but with Alarm Translations the MultiNet Server can convert the 140 to a 130 Burglary Alarm event (for example). Typically this is done in your Automation rather than maintaining two separate databases for signal interpretation.
Alerts - The Messenger Service can monitor IP Link failures and MTS Agent failures and report via e-mail.
Business Unit (BUID #) - The Multinet Receiver groups IP Links (and therefore Radios) by Business Unit. A Business Unit contains the IP Links and all Radios that communicate with those IP LInks (any Radios on the same Frequency and have the same Cypher Code as the IP Link).
Check-In Interval - The Interval at which the radio is sending a 602 - PERIODIC TEST event to the Monitoring Center.
Contact Debounce - The amount of time the radio will wait between the first and second reading of a zone input to prevent multiple alarms and restores on a zone being triggered by a “bouncy” switch.
Cypher Code - The Cypher Code is the “key” for radios on the same Frequency to be able to talk to each other. Radios on the same frequency but having different Cypher Codes will not relay each others signals. Both the Frequency and Cypher Code must be the same for all radios and IP Links on a network.
Dashboard - The Dashboard shows real-time counters and statistics. Most statistics are based on the last 24 hour period. Gauges are based on the last 1 Minute of data. The status of the MTS Agent is displayed in the top right corner.
Dealer - MTS adds a Dealer # to Radios to allow grouping of radios and restricting information to users based on their Dealer #.
Diagnostics Failure - This is generated by the MultiNet Receiver for 7788 Fire Radios when they report a NetConn 6 or 7. A Restoral event is generated by the Receiver when the radio returns to a NetConn 5. These radios should be updated to prevent a NetConn 6 or 7.
Diagnostic Module - A diagnostic unit that plugs into the AES Radio’s Programming Port and automatically interrogates the radios NetConn, Link Level, Peers, and System and Zones Status and displays all pertinent information on a screen in real-time.
En-Route - Route History can be used to show how often a radio is used by other radios to deliver messages. This radio would show up as En-Route if it is not the first or the last in the route.
Format (iTap) - The IntelliPro supports Contact ID (default), Pulse (4x2), and Modem II/III (which get converted to Contact ID by the IntelliPro before sending to the Radio). You can only set Contact ID or Pulse from the Radio Details page. (Hint) To stop a runaway dialer, change the format of the iTap so the dialer won’t get the expected handshake and therefore won’t send a signal.
Frequency - Radios communicate to an IP Link on a predetermined Frequency. Transceivers dictate the Frequency the radio will communicate on.
Geocoding - The translation from a Street Address, City, State to a Latitude/Longitude is referred to as Geocoding.
Global User - Global Users can switch between Business Units at any time. A Global User can edit regular users as well as Business Unit 0 (Global) users if Administrator is checked.
Inactive Radio - A radio is considered “inactive” when there have been NO Alarm History events in the last 24 hours.
Input Gain (iTap) - This determines how sensitive the IntelliPro is to received audio of the T and R line. The Input Gain can be adjusted to 20 for higher sensitivity when the IntelliPro does not respond (generate receiver handshake tones) to the Dialer after the phone number is dialed.
IntelliTap / FireTap - These are phone line + receiver simulators for alarm panels designed for POTS line communication. They provide dial tone, generate receiver handshake tones, generate the receiver kiss-off tones after a signal is heard, and then pass the signal to the AES Radio for transmission.
IntelliPro (iTap) - The 7094 IntelliPro can be queried and remotely programmed on the Radio Details page.
IntelliPro Fire (iTap) - The 7794 IntelliPro can be queried and remotely programmed on the Radio Details page.
Intercept # (iTap) - The Phone # that the IntelliPro will most quickly respond to. Any dialed digits should trigger the handshake tones, but if you dial the Intercept # (typically 555) then the IntelliPro will respond more quickly without waiting longer to see if more digits will follow.
iTap - A common reference to the IntelliTap / IntelliPro / IntelliPro Fire.
Link Level (LL) - Link Level is the number of radios this radio will repeat through to get to the IP Link. Link Level 0 is reserved for IP Links. All radios are looking for radios with a Link Level Less than their current link level which is calculated to be One higher than the First Peer on the list.
Messenger Server - The Messenger Service provides real-time notifications of IP Link and MTS Agent failures.
MTS Agent - The “mtsagent” must be running on the Primary Multinet Receiver to facilitate communications with an MTS Server.
MTS Server - An MTS Server communicates with a remote MTS Agent to continuously replicate the monitored Business Unit data and deliver outbound messages to radios.
Multinet Receiver - A Multinet Receiver refers to a Multinet Server and the radio network applications running on it. All IP Links connect to a Muiltinet Recievers applications to deliver messages to the Central Station. The IP Links relay signals to and from the radios on the network via a Multinet Receiver.
Multinet Server - Red Hat Linux based PC. The Multinet Receiver is a suite of applications running on a Multinet Server. You typically have a Primary and Backup server installed as Multinet Receivers. The MTS Server is talking to the Primary Multinet Server via an MTS Agent application running with the Multinet Receivers applications.
NetConn (NC) - Network Connectivity Level is calculated by the Radio and is based on the Peers it Hears. NetConn starts at 7 and is decremented for each peer that is heard with GOOD signal Strength and a NetConn of 5 or less. Newer radios do not go lower then a NetConn 5 where older radios may report a NetConn as low as 0. Anything 5 or Less is considered the same as a 5 by the network.
On/Off Test - This flag can be helpful to identify when a Technician is working on a radio so you don’t worry when it shows up on the Most Active Radio list.
Option Flags (Repeater, Line Cut, IntelliTap) - Repeater indicates if the repeater functionality of the radio is enabled or not (usually enabled). The Line Cut indicates whether the radio is monitoring the Line Cut input (usually disabled). The IntelliTap option will enable or disable the radios ability to receive messages from the IntelliTap module.
Packet Life (TTL) Settings - These timers determine the amount of time the different types of packets will survive on the network before being dropped due to non-delivery.
Peer / Peers List - The Peers List is a list of up to eight radios that a radio will maintain to use as a possible first-hop when sending a signal on the network. The radio will always start with the Top (#1) peer. The radio will attempt transmit seven times (if no acknowledgement is heard within the ACK Timeout timer period) before moving on to the next peer. When all peers have been exhausted with no reply, then the radio will send a “Radio Request Reply” packet asking anyone who hears it to reply. The Peers list is very dynamic, meaning it changes almost every time it hears a radio on the network. The radio will always try to put a radio it hears on its peer list in the proper order if it is better than any other on its list based on Signal Strength, NetConn, and Link Level. A Peers Distance is critical to know when troubleshooting a radios Ack-Delay problems.
Peering - A List of radios that have a specific radio on its Peer List. This helps you determine how Useful a radio is on the network. A radio that is Ack-Delaying and has a lot of Peering Radios should be fixed asap. These can be found on the Radios of Interest Report.
Periodic Test - The interval at which the radio is programmed to send a 602 - PERIODIC TEST event to the Monitoring Center. Also referred to as the Check-In Interval.
POTS Supervision (iTap) - Enable this if you are using a POTS line as your primary and would like the phone line voltage to be Supervised by the IntelliPro.
Programmer - An AES IntelliNet HandHeld Programer is used by an on-site Technician to program the radio and interrogate a radio’s status.
Radio - A Subscriber Radio and all data related to that radio. Also referred to as an Account.
Real-Time - As signals, routes and other radio data are received by the MultiNet Receiver, the MTS Server copies the data within seconds and presents that data immediately on the Dashboard, Traffic Lists, Radio Details, and Maps pages.
Reverse Geocoding - The translation from a Latitude/Longitude to a Street Address, City, and State is referred to as Reverse Geocoding.
Route (Path) - This is how your radio messages get to an IP Link and therefore can be used to send messages out to your Radio. Every Periodic Test event and some Alarm events will contain Route data in their packet. These Routes are logged and can be viewed on the Map to see how a radio’s signal is being delivered. The Route consists of two or more radios. The First radio is the originator of the message, the Last radio is the IP Link. To send a message back to a radio, the most recently received route is simply used in reverse (you can also manually define the outbound route, but inbound routes are always dynamic). A radio that uses Many different routes over a short period of time is probably an indication of some sort of RF Interference and is a sure sign of slow message delivery.
Route History - Every time route data is received in a packet, the route is stored in “history” just like Alarm History events. Route History can be “Played Back” on the Map to help analyze traffic patterns and points of congestion.
Routing Table - List of radios to be used as the first hop when delivering a signal to an IP Link. Also referred to as a Peers List.
Secondary Alarm Delay - A radio will delay between sending an Alarm and Restore to prevent flooding the frequency with traffic. This delay allows the signal to be relayed, and also gives other radios a chance to send a signal.
Text Message - Messages sent and received by a radio via the TEXT MESSAGE feature of the radio. Text Messages are typically used to query and program iTaps as well as to communicate with an on-site Technician who is using a handheld programmer or Hyperterminal connected to the radio to be able to receive and send Text Messages.
Top Peer - The first radio on a radios Peers List (Routing Table).
User - A User is assigned to a Business Unit (BUID#) and a Dealer #. Access to Radios is restricted to within the Dealer for the current Business Unit. All radios are visible on the Map but Names and Radio Details will not be available to any other dealers users. A user who belongs to Business Unit 0 is considered a Global User and can switch between Business Units at any time (but still restricted to assigned Dealer #). A user who belongs to Dealer 0 can see All Radios and Details and can change the working Dealer # at any time. An Administrator can edit and create users within their BUID/Dealer#.
Zone Types - Zone Types determine how the radio will report when a Zone is Shorted or Opened, whether or not an EOL Resistor is required, and indicates which zones will send Restorals. Fire zones will send Troubles when No Resistor is detected. Supervisory zones will send Alarms on an Open or Short. Enabling Restores is always recommended to be able to determine if a condition has returned to normal or not.
Copyright © 2014 ASI Communications, Inc. - email@example.com - 480-756-5444