What is it:
TwoToneDetect (TTD) detects two-tone and long-tone pages, sends a pre-alert, records dispatch audio and sends out the alert. It’s easy to set up and no CAD is needed.
IamResponding can send the PreAlert and Audio to you via Text, Email and/or the IaR App.
Where to find it:
TTD alerts can be seen in your IaR app, and on the IamResponding Website.
Setting up TTD is done on the user-side and is managed in the IamResponding Website by looking at:
Administrative Functions – TwoToneDetect Settings – Getting Started
Helpful links:
Related Video - Setting Up TwoToneDetect-for Windows
Related Video - Setting up TwoToneDetect-for Raspberry Pi
Related Guide - TTD a-z, for Windows OS, June 2024
Related Guide - TTD a-z, for Raspberry Pi, June 2024
Most Current version of TTD for Windows is 74i:
Current TTD Version for Windows (Win 10+ OS)
TTD Image File, and IaR AutoLauncher
TTD program Only
For individuals who prefer to install the TTD software on their own image rather than using the one we provide.
Related links:
Related Video - Redundancy is Good!
Related Video - Notifications
Related Guide - IaR App Help
Related Guide - Mobile Notifications
How-to:
TTD Set-up
TwoToneDetect is a function that requires permission to set up. If you are a current IaR Admin, look on your own profile and give yourself permission to Manage TwoToneDetect Settings. If you don’t see this option on your permission list, contact IaR Staff so that we can activate TTD for your agency.
See the Helpful Links: below.
-You will want to start by looking at the TTD a-z guide, and one of the provided Setting Up videos (Windows/Raspberry Pi). All the instructions you may need are provided here. If you get stuck, please reach out to IaR Staff. If you are following the guide or video, you can reference what step you are at, and we will know where you have hit an obstacle.
TTD Alerting
TTD alerting starts on your IamResponding Profile. Any App/device settings are secondary to what your Profile is set to do.
-Your profile is most readily accessible through our website, but also on your IaR App.
Go to: www.IamResponding.com from your computer of the Web Browser on your phone/tablet.
If you are new to an agency that already uses IaR, your fellow members will be a great resource to help you get set up. Find someone with a similar phone (Android/Apple) and try mirroring their settings.
Station Alerting
Playback during record (under Manage Pager Groups)
-A “1” in the 'playback during record' option is what makes the dispatcher audible during the recording process..
-A “0” turns this feature off.
-It will only play during record on the computer that is running TTD with the audio feed.
-On the GUI, under Edit Tone Info settings, there is an option for 'playback during record', that should be checked also.
Troubleshooting:
Static in the Recording
Your TTD audio will be as clear as TTD is ‘hearing’ it.
If you have static, start by looking at the reception that your pager/radio/scanner has.
Slight adjustments sometimes make a big difference.
Volume to quiet/loud
You can adjust the volume knob on your pager/radio/scanner to adjust the input volume that TTD is ‘hearing’ the recording.
-The audio going into TTD can be too loud. This can result in missed dispatches.
Feel free to reach out to IaR Staff for consultation.
If TTD was working and suddenly stopped
Fully reboot the computer
Restart TTD
Run a test and analyze the TTD DeBug test results. (IamResponding Staff can assist as needed)
If TTD is a brand-new setup and hasn’t worked yet
Have you watched our TTD Training Video? (See the Helpful Links: section above)
Have you followed the TTD a-z guide? (See the Helpful Links: section above)
Starting with the provided instructions (Video/Guide) is the best way for IaR Staff to assist persons.
-When you are going through the instructions Where do you get stuck?
Let us know what step you are at so that we can help with precision.
Questions to consider….
-What version of TTD is being used?
-What ‘listening device’ is being used?
-If using a Base Station (desktop) radio → Make sure that the Audio Out is not ‘amplified’.
Amplified Audio will likely cause TTD to hear static/white noise.
-Is the ‘listening device’ in a charging cradle/dock?
Charging cradles/docks will likely cause TTD to hear static/white noise.
-Are all cables/wires store bought?
Spliced/homemade wires and cables will likely cause TTD to hear static/white noise.
-Are all plugs/connections store bought?
Spliced/homemade plugs/connections will likely cause TTD to hear static/white noise.
Web Article about HUMs/STATIC:
Retrieving TTD DeBug Information
Obtaining CURRENT DeBug TTD log information.
Run a controlled TEST of the problematic Pager Group.
- Immediately prior to the TEST, on the TTD GUI screen, go to EDIT CONFIG INFO button. A Tab will open on your Browser called SETTINGS EDITOR. Just go to the Bottom and click SAVE, and then Close the SETTINGS EDITOR tab. The DeBug Info will have an entry with the Date/Time stamp and say, “window closed or reloaded…”. This process will help us all to easily locate the Test Data we are trying to analyze.
Anything after (below) the newly created Date/Time stamp, is the Test Data. (See image below, showing the Date/Time stamp created for easy reference).
- Quickly, after the TEST is completed, on the GUI Screen click on VIEW DEBUG INFO. This will capture/freeze the data we are looking for.
Scroll to the very bottom of that newly opened tab, and Highlight/Copy from the Bottom, Upwards to (and including) your recently created Date/Time stamp. (shown in the image above)
- Paste the Copied DeBug Info Data into the BODY of an email and send it to: Support@EmergencySMC.com.
- If you have multiple Pager Groups, in your email to IaR be sure to clearly identify what Pager Group you tested.
This process will help us to see what you and your TTD system are seeing/hearing when you utilize TTD to recognize any of your Pager Groups.
Obtaining PAST DeBug TTD log information.
Please provide IaR with the log data for the time-frame of the last incident that your agency missed.
-On the computer running your TTD program, open the TTD Folder
-Go to the file called 'logfiles'
(This is of course an example from one of our own computers)
Look at the FILE NAMES.
--The part underlined in Green is the DATE that the logfile starts.
--The part underlined in Red is the TIME (24-hr clock) that the logfile starts.
You want to pick the file that starts BEFORE the errant message (image shown below), without going over.
Reading the Logfile names:
log_2023-04-07_14_46_50_190783 = (April 7, 2023, at 14:46:50 hours (2:46pm)
log_2023-04-10_13_21_38_800451 = (April 10, 2023, at 13:21:28 hours (1:21pm)
-You are looking for the logfile that started BEFORE the missed dispatch for your agency, but that also encompasses the desired timeframe.
If you don't know which one to pick, send them all via email to: Support@EmergencySMC.com.
-When you send the logfile(s) back, we need to know the exact date/time of the missed dispatch.
-If you have multiple Pager Groups, in your email to IaR be sure to clearly identify what Pager Group we are looking for activity for.
Understanding DeBug Codes/Errors/Messages:
- The write operation timed out
-This is normally because the 13+ files in the TTD Zip File have not been properly unzipped and/or put into a separate folder on the desktop.
-Or that the write option is not allowed because of a permission on the computer or network.
Fun Tip:
-Using the IamResponding Website Station Alerting function, you can have your computer (at the station or at home) play the Dispatch Audio.
Do you have a fun tip, or a suggestion of something to add to this article?
Email us at: Support@EmergencySMC.com, Subject Line: Attention to Steve, ZD-Article