Curious on how this works as currently you'd set a recording delay to not record the tones...
TwoToneDetect New TwoToneDetect in the works - Python based
- Thread starter aaknitt
- Start date
-
- Tags
- twotonedetect
I don't know how it works, but I can confirm it works really well. I have been using it for over a week.
there are a couple of quirks in the GUI.
The showlog tab works until midnight when the next new log file is created.
And the listAudio tab ; the first word is truncated from the file title and if you try to play the mp3 file the pathway is wrong and you get Not Found message
The showlog tab works until midnight when the next new log file is created.
And the listAudio tab ; the first word is truncated from the file title and if you try to play the mp3 file the pathway is wrong and you get Not Found message
It still waits for the recording delay time as it always has. But once that time has expired, it checks to see if the tone is still present and if so, waits for it to be done before checking for audio to record. It's an enhancement to work around the fact that a lot of people weren't setting the record delay parameter correctly, but it should still be reverse-compatible.
Thanks for the feedback, I'll try to get these addressed.
scannerowner
Member
Anyone else having issues with it sending texts to Verizon phones? Was working fine, but not now.
I've heard that many carriers are in the process of deprecating their SMTP to SMS/MMS gateways. Unsure on exact status of each carrier specifically.
scannerowner
Member
Gotcha. I just found this. I'll try it out.
support.google.com
Send and receive emails over text message - Google Fi Wireless Help
Receive texts via email gateway When you use Messages by Google as your default messaging app, you can get emails delivered as texts to your phone. Your email-to-text address is your 10 digit Go
support.google.com
Last edited:
bunangst
Member
It will be interesting to see if there are any developments of carrier supported or open source Email to RCS gateways. Quick search shows some options, but all paid commercials applications.
scannerowner
Member
That's what I saw too. I get texts sporadically, so it's confusing.
MikeOrlando02
Member
- Joined
- Oct 8, 2015
- Messages
- 98
- Reaction score
- 6
ATT is definitely done supporting email to text: Say Goodbye to Email-to-Text and Text-to-Email
I am using Pushover and been migrating users over from SMS/MMS to push.
That's unexpected. What's the tone that you have configured and what's it detecting as unknown? Are there any errors in the log file from when TTD starts up? I'm wondering if it's ignoring your old tone file due to an error of some type.
I'm trying to sort it out with IaR support currently but it's going in circles. They said nothing close to my tones appear in the log.
Tones are 368.5/330.5. Here is just a snippet of the log:
Code:
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:4410 - Checking if 3043.9024390243903Hz and NoneHz matches any configured tone set
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:5075 - Unknown long tone detected: UNKNOWN_LONG_3043Hz
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:4158 - Alert detected: UNKNOWN_LONG_3043Hz at 12:37:40 on 09/01/25
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:4301 - starting new alert at 1756741060.709077
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:3517 - Skipping email send for unknown tone detection
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:3792 - Opened PyAudio recording stream for alert: UNKNOWN_LONG_3043Hz with sample rate 16000Hz
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:3812 - Processing tone 'UNKNOWN_LONG_3043Hz' with recordSeconds=15
2025-09-01 12:37:40 - TwoToneDetect - INFO - TwoToneDetect.py:3813 - Recording parameters: record_seconds=15s, release_time=3.0s,Yeah that unknown tone that it's detecting is a 3043 hz long tone which is nowhere close to your actual tone set. If it's detecting that when your actual tones are sent, I would guess that it may be an audio level issue of some type or having the wrong audio input selected and it's detecting crosstalk or something.
That's strange because nothing changed in the setup besides upgrading to v75. I refreshed the audio devices and turned off unknown tone detection. We'll see what happens with the next page.
The way that TTD stores the input audio device changed a bit in v75 so make sure you have the correct input device selected and then save the settings and restart to make sure it's grabbing the correct device when you restart TTD up.
Likely covered in the thread but we're 232 pages deep so I'll ask...how do we adjust the configuration on the 75beta version? I copied a config and tones files from a previous version and put them in the 75beta folder and it's working but I see no way to edit them if I need to...? App runs in a Command Prompt window so...what am I missing?
Once it starts running there should be a TTD icon in the system tray that you can click on to open the GUI in a browser. You can use that to do your configuration, and then close the browser when you're done and let it run in the background. I don't recommend leaving the GUI open all the time - just when you need it.
I should have tried it before posting but I had to reboot. It was working, but the icon wasn't in the tray (and wasn't just hidden as mine is set to not hide any). Glitch on my computer's part, I guess. I see it now. Thanks.
