<h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.

Question

I am trying to make an outbound call using azure communication services but I'm getting this error I'm testing it using postman I've defined the access token in autorization to,form and callbackuri in body and content-type in header.

<h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.

Answer 1

Hi @Gurveer Singh ,

I'm glad your issue was resolve and thanks for posting the solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept " the answer.

Issue:

-You tried making an outbound call using azure communication services but got this error:
"Our services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."

-You tested it using postman and defined the access token in authorization to, form and callbackuri in body and content-type in header.

Solution:

"we cannot directly access the endpoint as a rest API endpoint there are extensions to it that we need to add so that we can reach the correct destination like in order to place a call using Azure communication services we need to use this endpoint.

{endpoint}/calling/callConnections?api-version=2021-08-30-preview

FYI this will not work until you provide the access token"

Thanks again for sharing your solution.

Best,

Grace

Answer 2

Hi,

I am getting the same issue, I made a CNAME DNS record so anyone type https://intranet.mydomian.com it will redirect him to https://mydomain.sharepoint.com ,, Did any one find a solution to this issue?

Answer 3

The answer to this is we cannot directly access the endpoint as a rest API endpoint there are extensions to it that we need to add so that we can reach the correct destination like in order to place a call using Azure communication services we need to use this endpoint.

{endpoint}/calling/callConnections?api-version=2021-08-30-preview

FYI this will not work until you provide the access token

Answer 4

Hi @Gurveer Singh ,

I am trying to use Azure Communication Services to create a user identity and then fetch relay configuration for network traversal. It was giving same error so i updated the code according to the solution but still get the same error. Here is the code:

const { CommunicationIdentityClient } = require("@azure/communication-identity");

const axios = require('axios');

const main = async () => {

  console.log("Azure Communication Services - Relay Token Quickstart");

  const connectionString = "CONNECTION STRING";

  // Extract endpoint and access key from the connection string

  const endpoint = connectionString.match(/endpoint=(.*?);/)[1];

  const accessKey = connectionString.match(/accesskey=(.*)/)[1];

  // Instantiate the identity client

  const identityClient = new CommunicationIdentityClient(connectionString);

  try {

    let identityResponse = await identityClient.createUser();

    console.log(`\nCreated an identity with ID: ${identityResponse.communicationUserId}`);

    // Issue an access token for the created user

    const tokenResponse = await identityClient.getToken(identityResponse, ["voip"]);

    const accessToken = tokenResponse.token;

    console.log(`\nIssued an access token: ${accessToken}`);

    // Construct the relay configuration request

    const relayConfigUrl = `${endpoint}/networkTraversal/:issueRelayConfiguration?api-version=2022-03-01-preview`;

    const response = await axios.post(relayConfigUrl, {

      id: identityResponse.communicationUserId

    }, {

      headers: {

        'Authorization': `Bearer ${accessToken}`,

        'Content-Type': 'application/json'

      }

    });

    console.log("RelayConfig", response.data);

    console.log("Printing entire thing ", response.data.iceServers);

  } catch (error) {

    console.log("Encountered an error");

    console.log(error.response ? error.response.data : error.message);

  }

};

main().catch((error) => {

  console.log("Encountered an error");

  console.log(error);

});

Still I get the same error.