Re: [Freeswitch-users] Voicemail on AWS
On 2019-09-23 20:10 (CEST), H Yavari via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org> wrote:
Date: Sun, 22 Sep 2019 09:32:56 +0000 (UTC) From: H Yavari <hyavari@rocketmail.com> To: "freeswitch-users@lists.freeswitch.org" <freeswitch-users@lists.freeswitch.org> Subject: Voicemail on AWS X-Mailer: WebService/1.1.14303 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.75 Safari/537.36
I am looking for some hints how we can make an voicemail server for our company users to have their own voicemail box, then we save all voice files on AWS S3. I see mod_http_cache, but afraid of it's only solution or there is better one.
Hi, we used to run on S3, where we mounted the recordings with s3fs-fuse[1] which we ran successfully on 1.6.20. HOWEVER, when we updated to 1.8.5 we ran into problems with the wave files, the media stream was not saved and we ended up with empty media containers, with only some meta data of around 250 bytes ended up being saved. This issue affected about half of all recordings, and we found no correlation in regards to codecs used etc. If this was an issue with configuration, s3fs-fuse or Freeswitch we didn't investigate. We solved this by moving the storage from S3 to EFS, and are currently running it in production without issues in that regard. [1]: https://github.com/s3fs-fuse/s3fs-fuse -- Per Modin Software Engineer Working Group Two m: +46724452037 w: https://wgtwo.com e: per@wgtwo.com
On Tue, Sep 24, 2019 at 2:30 PM Per Modin <per@wgtwo.com> wrote:
we used to run on S3, where we mounted the recordings with s3fs-fuse[1] which we ran successfully on 1.6.20.
HOWEVER, when we updated to 1.8.5 we ran into problems with the wave files, the media stream was not saved and we ended up with empty media containers, with only some meta data of around 250 bytes ended up being saved. This issue affected about half of all recordings, and we found no correlation in regards to codecs used etc. If this was an issue with configuration, s3fs-fuse or Freeswitch we didn't investigate.
We solved this by moving the storage from S3 to EFS, and are currently running it in production without issues in that regard.
That is an option, but you also can get around the stream issue with and audio_spool_path: <X-PRE-PROCESS cmd="set" data="audio_spool_path=/tmp"/> -Nathan
Hi Per, Thank for your hint.So you didn't use http_cache right. Do you have the HA for your system also? is it ok with this structure? Regards,H.Yavari On Tuesday, September 24, 2019, 09:52:57 PM GMT+3:30, Per Modin <per@wgtwo.com> wrote: On 2019-09-23 20:10 (CEST), H Yavari via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org> wrote:
Date: Sun, 22 Sep 2019 09:32:56 +0000 (UTC) From: H Yavari <hyavari@rocketmail.com> To: "freeswitch-users@lists.freeswitch.org" <freeswitch-users@lists.freeswitch.org> Subject: Voicemail on AWS X-Mailer: WebService/1.1.14303 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.75 Safari/537.36
I am looking for some hints how we can make an voicemail server for our company users to have their own voicemail box, then we save all voice files on AWS S3. I see mod_http_cache, but afraid of it's only solution or there is better one.
Hi, we used to run on S3, where we mounted the recordings with s3fs-fuse[1] which we ran successfully on 1.6.20. HOWEVER, when we updated to 1.8.5 we ran into problems with the wave files, the media stream was not saved and we ended up with empty media containers, with only some meta data of around 250 bytes ended up being saved. This issue affected about half of all recordings, and we found no correlation in regards to codecs used etc. If this was an issue with configuration, s3fs-fuse or Freeswitch we didn't investigate. We solved this by moving the storage from S3 to EFS, and are currently running it in production without issues in that regard. [1]: https://github.com/s3fs-fuse/s3fs-fuse -- Per Modin Software Engineer Working Group Two m: +46724452037 w: https://wgtwo.com e: per@wgtwo.com_________________________________________________________________________ The FreeSWITCH project is sponsored by SignalWire https://signalwire.com Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. Build your next product on our scalable cloud platform. Join our online community to chat in real time https://signalwire.community Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
As @Per said, there is problem with wave files.I know that S3 doesn't support appending to file, so I think FS makes some headers for wave file and then write to it, and on S3 we have just wave headers. If someone has any idea, please share. Regards,HY On Wednesday, September 25, 2019, 10:21:59 AM GMT+3:30, H Yavari <hyavari@rocketmail.com> wrote: Hi Per, Thank for your hint.So you didn't use http_cache right. Do you have the HA for your system also? is it ok with this structure? Regards,H.Yavari On Tuesday, September 24, 2019, 09:52:57 PM GMT+3:30, Per Modin <per@wgtwo.com> wrote: On 2019-09-23 20:10 (CEST), H Yavari via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org> wrote:
Date: Sun, 22 Sep 2019 09:32:56 +0000 (UTC) From: H Yavari <hyavari@rocketmail.com> To: "freeswitch-users@lists.freeswitch.org" <freeswitch-users@lists.freeswitch.org> Subject: Voicemail on AWS X-Mailer: WebService/1.1.14303 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.75 Safari/537.36
I am looking for some hints how we can make an voicemail server for our company users to have their own voicemail box, then we save all voice files on AWS S3. I see mod_http_cache, but afraid of it's only solution or there is better one.
Hi, we used to run on S3, where we mounted the recordings with s3fs-fuse[1] which we ran successfully on 1.6.20. HOWEVER, when we updated to 1.8.5 we ran into problems with the wave files, the media stream was not saved and we ended up with empty media containers, with only some meta data of around 250 bytes ended up being saved. This issue affected about half of all recordings, and we found no correlation in regards to codecs used etc. If this was an issue with configuration, s3fs-fuse or Freeswitch we didn't investigate. We solved this by moving the storage from S3 to EFS, and are currently running it in production without issues in that regard. [1]: https://github.com/s3fs-fuse/s3fs-fuse -- Per Modin Software Engineer Working Group Two m: +46724452037 w: https://wgtwo.com e: per@wgtwo.com_________________________________________________________________________ The FreeSWITCH project is sponsored by SignalWire https://signalwire.com Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. Build your next product on our scalable cloud platform. Join our online community to chat in real time https://signalwire.community Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
participants (3)
-
H Yavari
-
Nathan Stratton
-
Per Modin