I am able to create a call through my react application using graph API to a MS-Teams user in organization which is working fine call is being made to the graph API and it's dialing to the user in the organization but I don't think user can interact without any device setup i.e laptop speakers and all in order to listen and speak over the call.
API USED :
To make a call
https://graph.microsoft.com/beta/communications/calls
To get call summary
https://graph.microsoft.com/beta/communications/callRecords/{id}
I want to know how :
Do I need to create interface in my ReactJs App just in order to provide user all the facilities of calling? Right now I have only provided the Call button.
How can I handle the callback in the development phase and test things in my react app as callback are only sent to the https routes.
Note : I am using NestJs as backend.
Can anyone please provide a demo for this how to handle things properly as its now like a brain twister working with MS Graph APIs. I shall be highly obliged for the same as I am trying this thing first time.
Thanks in Advance.
To Create call You will need to register the calling bot. Which enables your bot to create a new outgoing peer-to-peer or group call, or join an existing meeting. Please go throgh this documentation and samples for more info.
I am trying to create a basic online radio streaming Alexa skill. I have written the code and deployed it in the AWS. Everything looks good but I am seeing an error as shown below in the logs when I try to open the skill.
AskSdk.GenericRequestDispatcher Error:
Unable to find a suitable request handler.
at Object.createAskSdkError (/var/task/node_modules/ask-sdk-runtime/dist/util/AskSdkUtils.js:22:17)
at GenericRequestDispatcher. (/var/task/node_modules/ask-sdk-runtime/dist/dispatcher/GenericRequestDispatcher.js:145:49).....
......
.....
Here is the link to the amazon developer forum where I posted the question in detail: https://forums.developer.amazon.com/questions/212539/asksdkgenericrequestdispatcher-error-unable-to-fin.html.
Please let me know what I am doing wrong.
Thanks,
Dev
I have recently started working on alexa serverless. I have followed the steps as mentioned in a serverless blog https://serverless.com/blog/how-to-manage-your-alexa-skills-with-serverless/
I have installed the serverless and created security profile and updated the Web settings with allowed return url i.e, https 127.0.0.1:9090
After this I ran the command sls alexa auth. From here I am getting error like this
I am unable to find whats happening behind the screens. whats with code. Required environment variables are set.Can somebody help me
Go to Amazon Developer Portal. Choose Login With Amazon > Security Profiles > Edit > Web Settings.
Make sure you have the Allowed URL field filled in with your IP.
I had a similar issue. I updated my Allowed Origin and Allowed Return URLS to the following and it worked. Here is a screenshot.
Link:
https://developer.amazon.com/settings/console/securityprofile/web-settings/update.html
Am new to Alexa development. When configuring alexa in amazon developer site am getting Error:
Error: Please make sure that "Alexa Skills Kit" is selected for the event source type of arn:aws:lambda:us-east-1:431036771207:function:HelloWorld?
What am missing here ?
Follow these steps:
Go to the AWS Lambda console
Open your lambda function
Add a trigger of the type Alexa Skills Kit and configure it
I am having trouble using Microsoft Face API. Below is my sample request:
curl -v -X POST "https://westus.api.cognitive.microsoft.com/face/v1.0/detect?returnFaceId=true&returnFaceLandmarks=false&returnFaceAttributes=age,gender" -H "Content-Type: application/json" -H "Ocp-Apim-Subscription-Key: 1xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxd" --data-ascii "{\"url\":\"http://www.mrbeantvseries.co.uk/bean3.jpg\"}"
I use the subscription id from my cognitive services account and I got below response:
{
"error": {
"code": "Unspecified",
"message": "Access denied due to invalid subscription key. Make sure you are subscribed to an API you are trying to call and provide the right key."
}
}
Not sure if I've missed out anything there. Can someone help me on this? Very much appreciated.
I ran into the same problem. I read the API documentation and it states the following.
You must use the same region in your REST API call as you used to obtain your subscription keys.
First, you must find the location of your subscription.
In order to find the location of your subscription region, you must go to Cognitive Services -> Properties under the Label Location, you will find your subscription region.
See below.
Second you must find the correct endpoint to make the call to.
For example, if I want to make a call to the Computer Vision API,
My location is East US, I will use either key 1 or 2, then I will use the following endpoint
East US - https://eastus.api.cognitive.microsoft.com/face/v1.0/detect
You will now be able to have access to the API.
It appears that you've entered your Azure subscription ID instead?
In the Azure portal, you can find the API key under 'Keys', shown below:
It will be a 32-digit hexadecimal number, no hyphens.
I had faced the same issue, it seems like there is some problem with the keys generated newly. To fix this you can actually add your endpoint as well, when you create the object for IFaceServiceClient. You can see the code below.
private readonly IFaceServiceClient faceServiceClient = new FaceServiceClient("your key", "Your endpoint");
CesarB is correct. You must create a Resource of Cognitive Service in Azure first and then get the subscription key from it.
the region is not always 'westus', it really depends on what region you select when you created the resource. You can also check it on the endpoint of overview of the Resource
I ran into a similar problem. I figure it might be helpful to some people, so I am posting it here. (btw Azure support points me to this post here)
I was trying to run through the sample file for ImageSearch of Azure. I was refering to these pages:
https://learn.microsoft.com/en-us/azure/cognitive-services/bing-image-search/quickstarts/csharp
https://learn.microsoft.com/en-us/azure/cognitive-services/bing-image-search/quickstarts/client-libraries?tabs=visualstudio&pivots=programming-language-csharp
https://github.com/Azure-Samples/cognitive-services-dotnet-sdk-samples/blob/master/BingSearchv7/BingImageSearch/quickstart/bing-image-search-quickstart-csharp.cs
I was receiving a mixture of 404 Not Found error & 401 unauthorized error when send requests to the Bing Search resource, using
Microsoft.Azure.CognitiveServices.Search.ImageSearch. I figure it must be something wrong with either my credentials or my endpoints.
After struggling with it for hours, reading through posts and talking to Azure support member, I finally find the problems:
The base Uri Endpoint I was assigned on the Azure Keys & Endpoints webpage is incomplete. (https://api.bing.microsoft.com/)
The base Uri Endpoint on the sample tutorial pages was outdated because of the 2020.10.30 transition between Cognitive Services to Bing Search Services. (https://api.cognitive.microsoft.com/bing/v7.0/images/search)
As of 2021.09.22, the correct global base Uri Endpoint for Bing Image Search is:
https://api.bing.microsoft.com/v7.0/images/search
Hope this would be helpful to anyone and save mankind some time.
Endpoint
https://westeurope.api.cognitive.microsoft.com/face/v1.0
Endpoint and the subscription key must be consistent.
look at Microsoft Overview for this info!