Unable to access speaker #28
Comments
|
Hi , |
|
I have pushed a change that fixes most build issues and also adds a script chime-sdk-signaling-cpp/demo/cli/run_with_serverless_demo.sh that should bootstrap the demo better. You can try that branch as is or wait for it to reach My guess is that the configuration was not set up correctly. I will also see if I can updated the demo/SDK to fail faster and with a clearer message.
What is this in reference to? |
|
As per your suggestion we made the changes in Cmake file but we are facing errors related to Protobuf. For your reference I have added the error screenshot. |
|
Sorry for the possibly confusing suggestion. My changes/readme updates have been merged to mainline. Can you use those and try again? Additionally can you provide me the |
|
Now I am able to build using the latest readme file, but when running the demo application, I am getting an error related to the web socket. For your reference I have added the error screenshot. |
|
Have you uploaded a Serverless demo and set the |
|
Following the steps mentioned by you, I am able to overcome the WebSocket error, but the output window is not displaying for the same. For your reference I have added the error screenshot. |
|
Can you upload full logs to this ticket? A few of those logs imply that you are connected. By 'output window' i assume you mean that you have the browser demo open and joined to the same meeting. I assume you ensured that the |
|
when we are executing below command it is not displaying any media control for audio and video window. export SERVERLESS_DEMO_URL= # ... In our case SERVERLESS_DEMO_URL is deployed in AWS which is providing browser demo and server. |
|
we are expecting audio and video controller by following this command export SERVERLESS_DEMO_URL= # ... Please provide reference link of working C++ application which providing audio and video window. |
|
I just ran the steps in the CLI README and did not have any issue. It looks like WebRTC is failing to gather the TURN candidate. What platform are you using to build? Is this on AWS? Have you configured the network access properly? |
|
I am trying to build SDK again on a different system. getting error as mentioned below: -- Looking for HMAC_CTX_new -- Looking for HMAC_CTX_new—not found By following the below export command, even reflecting the above error. Can you suggest how to resolve the same export BORING_SSL_LIB=$CHIME_SDK_DEMO_DIRECTORY/webrtc-build/webrtc/out/Default/obj/libwebrtc.a export BORING_SSL_INCLUDE_DIR=$CHIME_SDK_DEMO_DIRECTORY/webrtc-build/webrtc/third_party/boringssl/src/include |
|
|
|
|
Here we need to initiate a call from the Ubuntu (Linux) and retrieve the call from the web application. How to check configured the network access ? |
Is not necessarily an indication of a failure unless you see other SSL issues down the line.
It depends on whether you are running on a local device or a cloud instance. This usually isn't relevant on a local device though. For the rest of the issues, I cannot assist, unless you provide the actual text of the failure. Please run a clean build and redirect the output to a log file (e.g. |
|
We are running the cloud instance. How to check the required configuration. |
|
Those are not errors, just optional features that don't exist in boring SSL. I will update README to not call them out as fatal Btw you can upload text files to github instead of copy pasting :). |
|
While I am executing the following command:. "/run_with_serverless_demo.sh --meeting 12 --attendee 2 --url $https://XXXXXX.execute-api.us-east-1.amazonaws.com/Prod/ " |
|
I may be misunderstanding the issue. Those logs show a successful connection. This is not a GUI application. You can navigate to https://xxxxxx.execute-api.us-east-1.amazonaws.com/Prod/, and enter the same meeting name, and you should be able to see the CLI client join. |
|
Can you please suggest how I can perform video call in Linux system using this same sdk? Can you please explain in brief the steps. |
|
This is a low level component and thus does not currently have information on how to make a linux GUI, which is not straightforward to do or maintain. You need to also be familiar with how to use a WebRTC implementation, which is not bundled with the SDK, though we use it in our example. Unfortunately i think you are asking for too much info outside the scope of this SDK. If you are a enterprise customer you can reach out to AWS premium support for more assistance. |
|
While i am running the below command getting error: |
|
You probably need to re-set |
While I am running the executable file getting error like Unable to access speaker and WebSocket. How to resolve this error can someone help me to resolve this error.
while trying to run demo application provide by aws chime
/my_cli --attendee_id=<ATTENDEE_ID> --audio_host_url=<AUDIO_HOST_URL> --external_meeting_id=<EXTERNAL_MEETINIG_ID> --external_user_id=<EXTERNAL_USER_ID> --join_token=<JOIN_TOKEN> --log_level=<LOG_LEVEL> --meeting_id=<MEETING_ID> --signaling_url=<SIGNALING_URL> --send_audio_file_name=<SEND_AUDIO_FILE>
Error Logs
attendee Name: aa
Attendee ID: xxxx
Meeting Name:
Meeting ID: aaaaaa
Audio Filename: k_16bit.pcm
Current Log Level: error
[INFO]: Creating DefaultSignalingClient
[INFO]: Creating WebsocketSignalingTransport
[ERROR]: (adm_helpers.cc:48): Unable to access speaker.
[ERROR]: (audio_device_generic.cc:18): BuiltInAECIsAvailable: Not supported on this platform
[ERROR]: (audio_device_generic.cc:28): BuiltInAGCIsAvailable: Not supported on this platform
[ERROR]: (audio_device_generic.cc:38): BuiltInNSIsAvailable: Not supported on this platform
Starting keypress handler
[2024/08/07 12:05:33:3666] E: Error while trying to connect the websocket: read failed
[ERROR]: Signaling has received error Error while trying to connect the websocket: read failed
The text was updated successfully, but these errors were encountered: