microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Mutli-tenant Calling bot with PSTN numbers
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
We are trying to setup a calling bot as a multi tenant application
where "customer" tenant need simply to create an application instance via resource account and assign a PSTN number. as described here
The issue zwe are facing is that the bot /application is not able to answer the call
The error i am getting is the following
{"code":"7505","message":"Mismatch between request authorization tenant and call tenant.","innerError":{"request-id":"b2b70403-4538-4e0e-8a13-0422545c41bc","date":"2020-01-24T22:11:49"}}"
code:"7505"
date:Fri Jan 24 2020 22:11:49 GMT+0100 (Central European Standard Time) {}
message:"Mismatch between request authorization tenant and call tenant."
requestId:"b2b70403-4538-4e0e-8a13-0422545c41bc"
statusCode:403
any one face this already ?
Any one was able to achieve the described setup ?
Thx in advance !
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Microsoft Graph cloud communications phone-number documentation and the reported 7505 authorization-tenant error. Trace the resource-account, PSTN-number, and call-answering setup for the multi-tenant arrangement; done means identifying a supported configuration or a documented resolution for calls being rejected.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100