CallingCommunicationError: Failed to initialize CallClient

Question

CallingCommunicationError: Failed to initialize CallClient

Chantal Kendall 0

Getting Error:- CallingCommunicationError: Failed to initialize CallClient

 let callClient = new CallClient();
 let callAgent = await callClient.createCallAgent(new AzureCommunicationTokenCredential(userAccessToken));

Ajay Kumar N 28,266 Reputation points Microsoft Employee Moderator

2023-06-12T14:19:30.89+00:00

@Chantal Kendall , Apologies for the delay from over the weekend.

Typically, the error "CallingCommunicationError: Failed to initialize CallClient" occurs when the CallClient is not initialized properly.

Kindy ensure that you have installed the "@azure/communication-calling" package and have latest version of ACS SDK installed. Also, ensure that you have provided the correct userAccessToken.

You may take a look the the example of how to initialize the CallClient with the AzureCommunicationTokenCredential in the doc here ( If you haven't done already).

You may enable and access call logs to fetch more info.

Kindly let us know how it goes, I'll follow-up with you further.

Chantal Kendall 0

 "@azure/communication-calling": "^1.13.1",
    "@azure/communication-chat": "^1.3.1",
    "@azure/communication-common": "^2.2.0",
    "@azure/communication-identity": "^1.2.0",
    "@azure/communication-signaling": "^1.0.0-beta.18",
    "@azure/core-asynciterator-polyfill": "^1.0.2",

Chantal Kendall 0

 "@azure/communication-calling": "^1.13.1",
    "@azure/communication-chat": "^1.3.1",
    "@azure/communication-common": "^2.2.0",
    "@azure/communication-identity": "^1.2.0",
    "@azure/communication-signaling": "^1.0.0-beta.18",
    "@azure/core-asynciterator-polyfill": "^1.0.2",

Yes Followed same instructions provided in docs,
Using valid user access token
Still getting same error

But able to send/receive messages using chat SDK

Ajay Kumar N 28,266 Reputation points Microsoft Employee Moderator

2023-06-13T19:22:14.62+00:00

Chantal, Thanks for the follow-up and additional info.
Apologies for the delayed response from over the weekend. I'm checking on this and will get back to you shortly.
Ajay Kumar N 28,266 Reputation points Microsoft Employee Moderator

2023-06-19T10:03:12.3433333+00:00

@Chantal Kendall , Just checking in to see if you had got a chance to see the previous response. Please share the requested/more info to help you better.

If the answer helped (pointed, you in the right direction) > please click Accept Answer

1 answer

Your answer

Ajay Kumar N 28,266 Reputation points Microsoft Employee Moderator

2023-06-12T14:19:30.89+00:00

@Chantal Kendall , Apologies for the delay from over the weekend.

Typically, the error "CallingCommunicationError: Failed to initialize CallClient" occurs when the CallClient is not initialized properly.

Kindy ensure that you have installed the "@azure/communication-calling" package and have latest version of ACS SDK installed. Also, ensure that you have provided the correct userAccessToken.

You may take a look the the example of how to initialize the CallClient with the AzureCommunicationTokenCredential in the doc here ( If you haven't done already).

You may enable and access call logs to fetch more info.

Kindly let us know how it goes, I'll follow-up with you further.
Chantal Kendall 0 Reputation points

2023-06-12T17:11:56.6466667+00:00

"@azure/communication-calling": "^1.13.1", "@azure/communication-chat": "^1.3.1", "@azure/communication-common": "^2.2.0", "@azure/communication-identity": "^1.2.0", "@azure/communication-signaling": "^1.0.0-beta.18", "@azure/core-asynciterator-polyfill": "^1.0.2",
Chantal Kendall 0 Reputation points

2023-06-12T17:13:08.5233333+00:00

"@azure/communication-calling": "^1.13.1", "@azure/communication-chat": "^1.3.1", "@azure/communication-common": "^2.2.0", "@azure/communication-identity": "^1.2.0", "@azure/communication-signaling": "^1.0.0-beta.18", "@azure/core-asynciterator-polyfill": "^1.0.2",

Yes Followed same instructions provided in docs,
Using valid user access token
Still getting same error

But able to send/receive messages using chat SDK
Ajay Kumar N 28,266 Reputation points Microsoft Employee Moderator

2023-06-13T19:22:14.62+00:00

Chantal, Thanks for the follow-up and additional info.
Apologies for the delayed response from over the weekend. I'm checking on this and will get back to you shortly.
Ajay Kumar N 28,266 Reputation points Microsoft Employee Moderator

2023-06-19T10:03:12.3433333+00:00

@Chantal Kendall , Just checking in to see if you had got a chance to see the previous response. Please share the requested/more info to help you better.

If the answer helped (pointed, you in the right direction) > please click Accept Answer

Answer 1

Ajay Kumar N 28,266 Microsoft Employee Moderator

While I'm checking on this, the same versions of Calling and Common SDKs works fine me, not experiencing issues to initialize callClient nor callAgent.

 "dependencies": {

    "@azure/communication-calling": "^1.13.1",	

    "@azure/communication-common": "^2.2.0"

Also, for chat, with a valid access token ('chat' scope), able to send/receive messages according to Azure doc. I'll follow-up with you shortly. Thanks for your patience!

Ajay Kumar N 28,266 Reputation points Microsoft Employee Moderator

2023-06-15T19:45:03.72+00:00

@Chantal Kendall, Kindly ensure (to isolate) that you’re not trying to create 2 active callAgent instances in the same process using this identity.

Also, review full console log or an exception call stack to fetch more details about the issue: Troubleshooting in Azure Communication Services

Share via

CallingCommunicationError: Failed to initialize CallClient

1 answer

Your answer