Skip to content

AWS Connect and Kinesis Video Streams Voicemail Solution

0

I am following the guide for VMX3 found on github but due to security constraints I am having to build manually instead of deploying via cloud formation. My issue is specifically the construction of the audio file. The audio file constructed has half second pauses every half second so it's long and drawn out. The code is identical to the solution found in github and for additional context I have built a replica in a separate aws instance via the cloudformation template and it's working just fine.

Trouble shooting done so far:

  • Confirmed the settings in for Kinesis are the same.
  • Confirmed the code is identical
  • Rebuilt the lambda

As of right now I'm lost on what the root cause could be for this audio quality being so poor.

Some question that I have that might help:

  • Is the way the audio file sounds indicative of a networking issue or a construction issue?
  • What are some specific trouble spots I might be missing with data coming from Connect through Kinesis and finally to Lambda for construction?
1 Answer
1

Thank you for reaching out to us regarding the above query.

Is the way the audio file sounds indicative of a networking issue or a construction issue?

  • Generally, if there is a construction issue, the recording itself might not be getting populated. However, if the recording is there, it points more towards networking side. However, in the mentioned common issues over GitHub, one of the issue discussed is when the voicemail audio is garbled. You may refer to it over here for reference.

What are some specific trouble spots I might be missing with data coming from Connect through Kinesis and finally to Lambda for construction

  • Your understanding is indeed correct, as per the architecture the flow seems to be Connect >> Kinesis >> Lambda >> S3 Bucket. Further, it would be best to check lambda function logs to see if the lambda is processing the incoming triggers without any errors. You can also check the contact flow logs to track down the flow.

I hope that the above information is helpful to you. Having said that, in case you are still facing challenges, please feel free to open a support case with AWS using the following link which would allow us to check the resources internally.

AWS
SUPPORT ENGINEER
answered a year ago
EXPERT
reviewed a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.