startStreamingAudioStatus Failed

[laimonassutkus]

A freshly deployed stack tested on chrome 81 (Version 81.0.4044.113 (Official Build) (64-bit)).

When getting a call in console these errors can be seen:

Wed Apr 22 2020 08:50:00 GMT+0300 (Eastern European Summer Time) " Message received from WS"
4lily-rtc.6f6f9376.js:9999 Uncaught Error: Failed to extract MediaRtpStats from RTCStatsReport for stream type audio_input
    at lily-rtc.6f6f9376.js:9999
(anonymous) @ lily-rtc.6f6f9376.js:9999
(index):517 contact refreshed
32lily-rtc.6f6f9376.js:9999 Uncaught Error: Failed to extract MediaRtpStats from RTCStatsReport for stream type audio_input
    at lily-rtc.6f6f9376.js:9999

Also, sample UI shows this status:

customerSentiment   Neutral
customerSentimentScore  0.ee9c92
languageCode    en-US
saveCallRecording   true
startStreamingAudioStatus   Failed
transcribeCall  true

In S3 audio bucket I can see empty transcriptions and non of the audio files. It is because the startStreamingAudio has failed. Any suggestions how to fix that?

More context: Stack deployed to Frankfurt (eu-central-1). Phone number picked from Lithuania pool. Making a call from Lithuania.

[efh365]

Hi. This is failing because realtime streaming is not available in Frankfurt. You can check out the region availability here: https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/

[laimonassutkus]

Thank you. I have deployed it to N. Virginia. However I am experiencing other errors nows. Even though I have followed the tutorial exactly.

[2020-04-24T05:53:54.005Z] [INFO]:  267b86cc-2541-4918-b472-e53ad144e747 SIGNALING PendingInviteState => PendingAnswerState
(index):662 WebSocket connection to 'wss://ffkfk7u5b9.execute-api.us-east-1.amazonaws.com/Prod?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAXB6NM4E6JG6JIS7C%2F20200424%2Fus-east-1%2Fexecute-api%2Faws4_request&X-Amz-Date=20200424T055353Z&X-Amz-Security-Token=FwoGZXIvYXdzEFcaDA2FJeHHBUi26AvUySLIAYoF7k5t6VjuSMKUdSOJUkiebLBb0FM9Dsrht1TwGBes7t7ygvOtDnge0%2FSuxznP5LC1fBNgeehpiFpbUVx4X1rBcq0J4PaSc6PnTR%2FAY3D3OjygExpTsmQXUa8HiEccTPZIu0jUplhmquwumQkGpBEhBWO9Uo3ByY1Gwc%2FwepDUTHz1yWvR1VmZLyEJdAePF7o7eW44vp6Z4gYe5dIqzVavN83Y7R%2FkNUdv7e%2BtIU%2F%2BS5us7c9wd621uQVSrFlFvGAxdXxC7sJ6KOv9ifUFMi3ieS8UiKJ7Mccjgdg7cEJzYlN0rrCKgDPBRD8NxiZf%2BxIOJXeDSzueZvWU%2BjI%3D&X-Amz-SignedHeaders=host&X-Amz-Signature=8e749486541d7f3ae0e9747bc95869c9cc3c1b0e1a96039e552c84be79e6f6e4' failed: Error during WebSocket handshake: Unexpected response code: 403
WebSocketTest @ (index):662
(index):695 Connection is closed... CloseEvent
(index):696 Onclose called, code is :  1006  reason is    wasClean  is false
(index):698 Connection is closed due to connectivity issue

And after that this:

18lily-rtc.js:9928 Uncaught Error: Failed to extract MediaRtpStats from RTCStatsReport for stream type audio_input
    at lily-rtc.js:9928
(index):517 contact refreshed
2lily-rtc.js:9928 Uncaught Error: Failed to extract MediaRtpStats from RTCStatsReport for stream type audio_input
    at lily-rtc.js:9928
(index):522 the contact is connected! [object Object]
(index):755 sending new connection id
(index):759 Object
(index):761 {"action":"sendmessage","data":"conndId@undefined|contactId@267b86cc-2541-4918-b472-e53ad144e747"}
(index):762 WebSocket is already in CLOSING or CLOSED state.

But deploying stack to a supported region indeed helped!

Metatags for connect client show streaming success:

kvsTriggerLambdaResult | Success
-- | --
languageCode | en-US
saveCallRecording | true
startStreamingAudioStatus | Success
transcribeCall | true

[efh365]

It seems like those errors are from the agent UX, right? Sometimes there are errors in the console that don't actually cause any failures. What are you seeing from the agent perspective? What isn't working?

[Benkracker]

Ensure that you've enabled Live Media Streaming for your Amazon Connect instance.

[efh365]

is this still an issue?

[laimonassutkus]

Closing.

[tonix-tuft]

@laimonassutkus Sorry, what was your solution to this error? And which tutorial did you follow? Thank you!

[laimonassutkus]

I just followed EXACTLY word by word documentation. Delete everything previously.