awslabs / amazon-kinesis-video-streams-webrtc-sdk-js

JS SDK for interfacing with the Amazon Kinesis Video Streams Signaling Service.
https://awslabs.github.io/amazon-kinesis-video-streams-webrtc-sdk-js/examples/index.html
Apache License 2.0
286 stars 141 forks source link

Create Channel always fails with ResourceNotFound Exception #246

Closed vikramdattu closed 1 year ago

vikramdattu commented 1 year ago

I can confirm that the credentials work with webrtc-sdk-c used with freertos example here.. It doesn't throw any error.

Below are the error logs from the test page.

[2023-07-25T10:18:41.906Z] [INFO] [CREATE_SIGNALING_CHANNEL] Attempting to create signaling channel with name ScaryTestChannel
[2023-07-25T10:18:42.866Z] [ERROR] [CREATE_SIGNALING_CHANNEL] Encountered error: {
  "message": "Not Found",
  "code": "ResourceNotFoundException",
  "time": "2023-07-25T10:18:42.865Z",
  "requestId": "0151c488-7c2a-1bb5-523f-b9e431f8eb4c",
  "statusCode": 404,
  "retryable": false,
  "retryDelay": 41.603751254851694
} 

Boot up logs from my ESP-WROVER-KIT, suggest that it is working as expected:

New certificate has been pre-generated and added to the queue
The expiration of ice config: 16902808965018250, ttl: 300
Signaling client state changed to 7 - 'Ready'
New certificate has been pre-generated and added to the queue
Signaling Client Connect Sync
Signaling client state changed to 8 - 'Connecting'
Connect to the signaling channel
Start connecting to the signaling server
Connect the wss
Create Wss client
Start the wss client
pthread:wss_client, size:10240 requires ram, totalSize:10664, spiSize:72, internalSize:10592
The number of threads: (3/3)
Signaling client state changed to 9 - 'Connected'
Wss client is up
The bootup time of webrtc is 23117 ms
wss ping ==>
(ping, pong): (1, 0)
<== wss pong
wss ping ==>
(ping, pong): (2, 1)
<== wss pong

Any help is appreciated.

vikramdattu commented 1 year ago

Okay, the issue isn't present anymore when Endpoint (optional) field is left empty.