endpoint.destroy() never returns if aws transcription is active about drachtio-fsmrf HOT 12 OPEN

I rather doubt it, because I use google all the time and would have seen this

from drachtio-fsmrf.

Just verified. Same issue does not exist with google transcribe.

from drachtio-fsmrf.

I will look at building that today

from drachtio-fsmrf.

I think this will be an issue here in mod_aws_transcribe. I can get this recreated locally tonight, and see what I can find.

from drachtio-fsmrf.

curious if you think this could be an issue with Google transcribe as well? Reason I ask is because we switched to aws transcribe after we started experiencing long delays before Google would return any transcription result. Seemed to happen more frequently after the server had been running a while, and I suspect its because there were tons of hung calls with transcribe still active on the FS box.

from drachtio-fsmrf.

I was able to recreate this issue. I created an issue on the drachtio-freeswitch-module repo where I will work on a fix.

from drachtio-fsmrf.

cool! let me know if there’s any way I can help you 🍻

from drachtio-fsmrf.

My fix for this got added in v0.8.4 of drachtio-freeswitch-modules. Can you verify it works for you?

from drachtio-fsmrf.

howdy! apologies for the slow response here. I'll give it a shot today.

from drachtio-fsmrf.

hmm...not sure how I can test this in our setup. we use docker-drachtio-freeswitch-mrf in our dev and prod so until it gets in there I'm stuck.

from drachtio-fsmrf.

Sorry for the late reply. If you build using drachtio/drachtio-freeswitch-base:latest in the docker-drachtio-freeswitch-mrf Dockerfile, it will have this fix. But, there isn't a new docker-drachtio-freeswitch-mrf version yet to use.

from drachtio-fsmrf.

@lylepratt, you should be able to use the latest docker-drachtio-freeswitch-mrf now.

from drachtio-fsmrf.