Adding More Observability to AWS Chime Voice Connector with Call Analytics Voice Recording

Question

We have a voice connector with the following work flow (somewhat simplified).

tl;dr We are doing termination only, voice only Chime Voice Recordings

[Amazon Chime SDK Voice Connector] 
                   |
                   v
       [Amazon Kinesis Video Streams]
                   |
                   v
      [Amazon Call Analytics - Recording]
                   |
                   v
      [Amazon Kinesis Data Streams]
                   |
                   v
   [Amazon S3 Call Recording Bucket]

This is a no-code cloud solution we are using for call recording.

Now this works most of the time but sometimes Calls do not make it into the S3 bucket and the CloudWatch logs don't have any tracing data that helps us identify where and why the call recordings are dropping.

How can we figure out what is happening in this black box?

Doug · Answer

You didn't say if SIP logging was enabled on your Voice Connector. If not, that's definitely where I'd start.

The SIP logs are off by default but you can opt to receive SIP message logs for your Amazon Chime SDK Voice Connector. When you do, the Amazon Chime SDK captures inbound and outbound SIP messages and sends them to a CloudWatch Logs log group that is created for you. The log group name is /aws/ChimeVoiceConnectorSipMessages/${VoiceConnectorID}.

- Voice Connect logging settings: https://docs.aws.amazon.com/chime-sdk/latest/ag/edit-voicecon.html

Adding More Observability to AWS Chime Voice Connector with Call Analytics Voice Recording

Add your answer

Relevant content