Honestly, Mike, you have lost me on this one! Can you post the logs showing the fire and ems decodes? Are fire and ems dispatched on different radio frequencies?
Just got my new laptop running for TTD 71c. I did see a few times "Failed to execute script", but it is only my first day. I am running two instances, one for EMS and other for Fire. I was not aware that you could run two instances on different channels using the same sound card. We have always used the on-board sound card and then a USB sound card to make that work. Both of mine are set to left, but they are on separate devices. Could this be my issue? I had a MVC and fire and EMS were both paged and I got both recordings respectively.
The biggest issue I am seeing is that I seem to only be capturing the first page in some circumstances. I thought it might be the case of two strung together as one recording, but it is only the one page. The MVC example above, both first and EMS only had one page recorded each. Any suggestions? Adjust tone tolerance?
I just watched this again. It started recording on the first page and then the second paged ended up being recorded all as one long file, but still didn't detect the second tone set and create a second file just with the second dispatch like previous version did.
(
Does anyone have any information on how to host audio and make it available through the ftp capabilities of this program. I have a website and I can upload ftp to it but I cant access the files via http. I would like to be able to send txt messages with a link to audio instead of MMS messages in Hope's to improve delivery of messages. I know this is more on web design than ttd. But was hoping someone had done it or had an article saved on how its done. Thanks for the help.
Bell support indicates that SMS messaging should workAndy has yourself or anyone else here been able to figure out how to get TTD to work with Bell/Virgin in Canada?
I cannot for the life of me find an MMS Address for Bell. The only public one I can find is @txt.bell.ca and everything bounces back as undeliverables.
I thought maybe v71c was the answer with the Audio Hosting so I added those addresses to the Text Only section, assuming they would just get the text with the URL Link... but no dice. Still bounces back.
Does anyone have any ideas for Bell in Canada?
Andy has yourself or anyone else here been able to figure out how to get TTD to work with Bell/Virgin in Canada?
I cannot for the life of me find an MMS Address for Bell. The only public one I can find is @txt.bell.ca and everything bounces back as undeliverables.
I thought maybe v71c was the answer with the Audio Hosting so I added those addresses to the Text Only section, assuming they would just get the text with the URL Link... but no dice. Still bounces back.
Does anyone have any ideas for Bell in Canada?
If you send to a single phone number via that gateway address manually using your normal email service/account does it work?
In many cases the phone carriers convert messages sent to multiple recipients to MMS messages. If that's occurring, you may need to use the "BCC" option in TwoToneDetect, as that usually ensures that they messages get sent as SMS rather than MMS.
Andy
you two screen shots from above seem to show the leading 1 on the phone number. Have you tried it with only the ten digits without the 1?
Thank you for your helpDC31 is correct. You can upload files to the free TTD hosting service and not need to use FTP or your server at all. You can also upload files to your own web/FTP server if you'd like, just make sure you're uploading them to a location that's accessible via HTTP (typically a subdirectory of the "public_html" folder on your web server).
Andy
Will the download page be up again soon. It says it's being worked on. Our older version is messed up somehow and we are looking to try the newer programHello everyone. I've posted v71 of TwoToneDetect on the website. Instructions for downloading a version for the Pi can be found on that page. Some pretty big changes with this version, so please test thoroughly before deploying for regular use and please provide feedback. Many thanks to DC31 for helping extensively with testing. I'm sure we haven't caught all bugs yet though. Here's a summary of the changes:
The new audio file hosting service is a "we'll see how it goes" thing right now. If it performs well, I may look into offering things like push notifications through a TTD mobile app or something similar at some point in the future. The portion of the web site to create a username and API key is functional but ugly. Hopefully it'll improve over time. Many ideas, not much free time.
- Changed GUI to be HTML based. TwoToneDetect acts as a web server to display the GUI.
- Tones Editor functionality is built into the main program GUI and is no longer a standalone program.
- Remote access to the TwoToneDetect GUI via web browser on a LAN is supported, including on “headless” devices such as a Raspberry Pi running a non-GUI operating system (“Lite” OS).
- The default port for remote access via web browser is 8080 but this can be changed in the configuration settings.
- The option to start minimized (start_minimized) has been replaced with an option to start headless (start_headless). When TwoToneDetect is started in “headless mode”, the GUI will not be visible on the desktop but the program will be running and the GUI can be accessed via web browser by browsing to index.html at the IP address of the computer that TwoToneDetect is running on and the appropriate port. For example: http://192.168.1.13:8080/index.html
- Added ability to use twotonedetect.net for audio file hosting. A hyperlink to the file in the body of the message can be used with SMS notifications (to avoid MMS), push notifications, or email.
- Variable substitution added to alert_command in addition to post_email_command for [mp3], [amr], [wav] and [t] tags ([d] tag had already been implemented)
- Push notifications will be sent with the text from the “Email Body” in the message
- /log/heartbeat.log file is written with an updated timestamp once per minute to allow external scripts to check responsiveness.
- Added option to send a copy of the email to the sending address when using the BCC option. Some users have said that this reduces blockage by spam filters.
- Changed behavior of ignore_after parameter to start timer after recording has stopped. Duplicate tones will always be ignored while a recording for that tone is active regardless of the ignore_after setting.
- Changed processing of stacked tones so that only a single audio recording thread is used to reduce processor load. Recording time is now automatically extended during stacked tones. Audio files are copied for each tone in the stacked page after recording.
- Changed FTP file upload for stacked tones so that a single FTP connection is used to upload all files in the stacked sequence.
- Added ability to specify a path on the FTP server to upload to (using the upload_ftp_remote_path parameter in config.cfg) rather than being limited to the root directory that is logged into. For example, use /audio/ to upload to an audio subdirectory.
- Program automatically removes audio files older than 15 days old to reduce storage
- “dummy” ffmpeg file no longer needed when running on Raspi
As always, let me me know of any problems.
Thanks,
Andy