I've developed a new WebSocket server called WAVStream that works with mod_audio_stream.
It's written in Go and designed to simplify the process of recording calls and automatically uploading them to S3-compatible storage.
You can find the project here: https://github.com/ynigun/wavstream
Key Features:
Receives both text and audio data from mod_audio_stream
Creates WAV files in real-time
Automatically uploads completed recordings to S3-compatible storage
Supports changing the recording file mid-call, creating separate files
When changing the filename mid-call, WAVStream will create two separate files. The first file will be closed, uploaded to S3, and a new file with the new name will be started. This allows for segmenting long calls into multiple files or changing file naming conventions mid-call if needed.
Development Status:
Please note that WAVStream is still in development. There are several areas that need further work and customization:
Temporary File Location: Currently, the location for temporary files is not configurable. This needs to be added as an option.
S3 Upload Options: The current version sets all uploaded files to be public. We need to add more flexible options for S3 uploads, including privacy settings.
Additional Configurations: We're working on adding more configuration options to make the server more versatile for different use cases.
Contributions and feedback are welcome! If you try it out or have any suggestions, please let me know by opening an issue or submitting a pull request on the WAVStream GitHub repository.
This server aims to enhance the functionality of mod_audio_stream and simplify the process of handling recordings. I hope it proves useful to the community!
Beautiful! Really interesting project, a star came straight away!! I'll leave this info here for the community to visit, try and use. Thanks for the project.
I've developed a new WebSocket server called WAVStream that works with
mod_audio_stream
. It's written in Go and designed to simplify the process of recording calls and automatically uploading them to S3-compatible storage. You can find the project here: https://github.com/ynigun/wavstreamKey Features:
mod_audio_stream
Usage:
To start a recording:
To stop and upload:
To change the recording file:
When changing the filename mid-call, WAVStream will create two separate files. The first file will be closed, uploaded to S3, and a new file with the new name will be started. This allows for segmenting long calls into multiple files or changing file naming conventions mid-call if needed.
Development Status:
Please note that WAVStream is still in development. There are several areas that need further work and customization:
Temporary File Location: Currently, the location for temporary files is not configurable. This needs to be added as an option.
S3 Upload Options: The current version sets all uploaded files to be public. We need to add more flexible options for S3 uploads, including privacy settings.
Additional Configurations: We're working on adding more configuration options to make the server more versatile for different use cases.
Contributions and feedback are welcome! If you try it out or have any suggestions, please let me know by opening an issue or submitting a pull request on the WAVStream GitHub repository.
This server aims to enhance the functionality of
mod_audio_stream
and simplify the process of handling recordings. I hope it proves useful to the community!