TwoToneDetect New TwoToneDetect in the works - Python based

[NNJIPScan]

Thanks for the feedback! Two adjustments made last night, one or both fixed the issue:

1. Power cycled the radio. A Motorola Radius mobile, pretty sure its been on for 10 straight years
2. Changed the input on the computer from Mic to Line-In

 

[dwgelle]

Looks like AT&T will not be supporting email to text. I'm getting these emails after Two Tone detect sends out pages.

Hi, it’s AT&T. On 6/17/2025, we’ll stop supporting email-to-text messages. That means you won’t be able to send a text message to an AT&T customer from an email address. You can still get in touch with AT&T customers using SMS (text), MMS, and standard email services. For more info, go to www.att.com/StopEmail2Text

 

[slingshot202]

Looks like AT&T will not be supporting email to text. I'm getting these emails after Two Tone detect sends out pages.

Hi, it’s AT&T. On 6/17/2025, we’ll stop supporting email-to-text messages. That means you won’t be able to send a text message to an AT&T customer from an email address. You can still get in touch with AT&T customers using SMS (text), MMS, and standard email services. For more info, go to www.att.com/StopEmail2Text

They all have blocked my two-tone stuff and I have no moved over to Pushover for the receiving app.

 

[jhsands]

Looks like AT&T will not be supporting email to text. I'm getting these emails after Two Tone detect sends out pages.

Hi, it’s AT&T. On 6/17/2025, we’ll stop supporting email-to-text messages. That means you won’t be able to send a text message to an AT&T customer from an email address. You can still get in touch with AT&T customers using SMS (text), MMS, and standard email services. For more info, go to www.att.com/StopEmail2Text

Verizon offers free delivery to Verizon handsets via EMAG. Other will just have to go to a monitored email on their phone or use ClickSMS.

 

[KC1IMD]

Verizon offers free delivery to Verizon handsets via EMAG. Other will just have to go to a monitored email on their phone or use ClickSMS.

View attachment 181131

Could someone please explain what EMAG is? We are having delivery issues as well. Thanks.

 

[jhsands]

Could someone please explain what EMAG is? We are having delivery issues as well.

I already set you up on EMAG, but you did not want EMAG because EMAG cannot attach the MP3.

 

[KC1IMD]

I see. Thank you

 

[jhsands]

Looks like AT&T will not be supporting email to text. I'm getting these emails after Two Tone detect sends out pages.

Hi, it’s AT&T. On 6/17/2025, we’ll stop supporting email-to-text messages. That means you won’t be able to send a text message to an AT&T customer from an email address. You can still get in touch with AT&T customers using SMS (text), MMS, and standard email services. For more info, go to www.att.com/StopEmail2Text

AT&T texting dilemma & solution: AT&T has built-in support for moving from the SMS/MMS to messaging that is compatible with TTD. This service supports MP3.

What you need to do:
Contact your FirstNet/AT&T rep for your *agency*.
Product development (Steven H) will engage GEM Mobility team.
GEM team will create a "zero biller" line.
Provide your AT&T/FirstNet phone numbers you are texting to.
Product development will engage external vendor.
Product development will create a FNADMN account with X license seats and provide the proprietary API code to external vendor.
Product development will provide necessary SMTP details.
Log into https://messaging.firstnet.com/ and follow other instructions listed in the email.

 

[jhsands]

T-Mobile SMS/MMS issues:

Anderson, Lylah <@t-mobile.com> wrote:

The fix for these end-users would be 1. Call into CARE and request enterprise messaging added to the line or 2. For self-service option the user can go to the T-Life application , login to their T-Mobile account, go to manage tab at the bottom right, select see plans (top right), scroll down to phone plan and select manage add-ons, scroll down to line level services and select enterprise messaging ($0.00 cost). See images below:

 

[hiya]

can someone explain how they use pushover to replace at@t email to mms please. I get a notification but no file. If its not possible does anyone have a workaround. Im not with a agency so it is for private use.

 

[DC31]

you cannot send an audio file attachment with pushover. you need to set up a web server, have ttd upload the audio file there, and then send the url for that file on the web server with the pushover alert. the recipient then opens that file on the web server by clicking on the link and voila!, the audio plays. this can all be done with a relatively simple python script that is fired by ttd.

 

[hiya]

I was afraid of that answer. Could you point me in the right direction of creating a web server.
Also my ip changes sometimes will that affect the webserver?

 

[Firebuff880]

AT&T texting dilemma & solution: AT&T has built-in support for moving from the SMS/MMS to messaging that is compatible with TTD. This service supports MP3.

What you need to do:
Contact your FirstNet/AT&T rep for your *agency*.
Product development (Steven H) will engage GEM Mobility team.
GEM team will create a "zero biller" line.
Provide your AT&T/FirstNet phone numbers you are texting to.
Product development will engage external vendor.
Product development will create a FNADMN account with X license seats and provide the proprietary API code to external vendor.
Product development will provide necessary SMTP details.
Log into https://messaging.firstnet.com/ and follow other instructions listed in the email.

Please be careful, they are sending you to a third party out of Tampa called Syniverse.

https://www.nslookup.io/domains/messaging.firstnet.com/dns-records/

 

[aaknitt]

v75beta available for testing

Hi everyone. There is a v75 of TwoToneDetect in the works with some fairly significant changes, so I'm looking for some guinea pigs to give it a test drive before it becomes "official".

Tentative release notes:

• Adds support for UDP audio input to allow easier ingest of audio from SDR applications (trunk-recorder [tested], rtl_airband [not yet tested]), etc.
• Allows tones.cfg settings that aren't set in the IamResponding back end to be configured locally without being overwritten
  • for example, the mp3_emails setting
  • enables a single instance of TTD to send to both IaR and via email
• Many updates to core architecture to deprecate unsupported libraries, etc.
• Better support for multiple USB audio devices in Linux / pulseaudio
  • each device should not populate in the dropdown, eliminating the need to set environment variables when starting TTD
• Audio devices are now saved by name instead of index to better handle audio device changes in Windows
• Improved logging output
• Deprecate support for AMR files to allow use of standard ffmpeg without needing to build from source
  • any email addresses in the amr_emails field will now get mp3 attachments instead of AMR
• Automatic removal of tones prior to recording
• Automatic detection of unknown tone sets (still being tested & refined - this may be buggy)
• Added max_vox_extend time parameter to config.cfg file to limit max recording time. If missing, defaults to 60 seconds (prior hard-coded value).
• GUI facelift

There's not much in the way of support documentation yet so it's use at your own risk for now. Feedback welcome.

Windows
RasPi OS 64 bit (this is the binary only without any other files)

 

[jschmall]

v75beta available for testing

Hi everyone. There is a v75 of TwoToneDetect in the works with some fairly significant changes, so I'm looking for some guinea pigs to give it a test drive before it becomes "official".

Tentative release notes:

• Adds support for UDP audio input to allow easier ingest of audio from SDR applications (trunk-recorder [tested], rtl_airband [not yet tested]), etc.
• Allows tones.cfg settings that aren't set in the IamResponding back end to be configured locally without being overwritten
  • for example, the mp3_emails setting
  • enables a single instance of TTD to send to both IaR and via email
• Many updates to core architecture to deprecate unsupported libraries, etc.
• Better support for multiple USB audio devices in Linux / pulseaudio
  • each device should not populate in the dropdown, eliminating the need to set environment variables when starting TTD
• Audio devices are now saved by name instead of index to better handle audio device changes in Windows
• Improved logging output
• Deprecate support for AMR files to allow use of standard ffmpeg without needing to build from source
  • any email addresses in the amr_emails field will now get mp3 attachments instead of AMR
• Automatic removal of tones prior to recording
• Automatic detection of unknown tone sets (still being tested & refined - this may be buggy)
• Added max_vox_extend time parameter to config.cfg file to limit max recording time. If missing, defaults to 60 seconds (prior hard-coded value).
• GUI facelift

There's not much in the way of support documentation yet so it's use at your own risk for now. Feedback welcome.

Windows
RasPi OS 64 bit (this is the binary only without any other files)

View attachment 187070

Do you have a beta binary for Ubuntu? I’d love to test out the new changes. Currently using the latest version of v74.

 

[webstar22]

v75beta available for testing

Hi everyone. There is a v75 of TwoToneDetect in the works with some fairly significant changes, so I'm looking for some guinea pigs to give it a test drive before it becomes "official".

Tentative release notes:

• Adds support for UDP audio input to allow easier ingest of audio from SDR applications (trunk-recorder [tested], rtl_airband [not yet tested]), etc.
• Allows tones.cfg settings that aren't set in the IamResponding back end to be configured locally without being overwritten
  • for example, the mp3_emails setting
  • enables a single instance of TTD to send to both IaR and via email
• Many updates to core architecture to deprecate unsupported libraries, etc.
• Better support for multiple USB audio devices in Linux / pulseaudio
  • each device should not populate in the dropdown, eliminating the need to set environment variables when starting TTD
• Audio devices are now saved by name instead of index to better handle audio device changes in Windows
• Improved logging output
• Deprecate support for AMR files to allow use of standard ffmpeg without needing to build from source
  • any email addresses in the amr_emails field will now get mp3 attachments instead of AMR
• Automatic removal of tones prior to recording
• Automatic detection of unknown tone sets (still being tested & refined - this may be buggy)
• Added max_vox_extend time parameter to config.cfg file to limit max recording time. If missing, defaults to 60 seconds (prior hard-coded value).
• GUI facelift

There's not much in the way of support documentation yet so it's use at your own risk for now. Feedback welcome.

Windows
RasPi OS 64 bit (this is the binary only without any other files)

View attachment 187070

Will it do a webhook trigger by chance?

 

[aaknitt]

Will it do a webhook trigger by chance?

You can set that up using an external script with the alert_command and/or post_email_command triggers/parameters.

 

[aaknitt]

Do you have a beta binary for Ubuntu? I’d love to test out the new changes. Currently using the latest version of v74.

Not yet. I'll see if I can find time to get one built next week, but no promises.