Unable to create call #29

mwerghemmi · 2018-11-27T10:50:08Z

I am trying to make a call using the Graph API.
if i use a target as follow : calls to a tenant user is working perfect

{
      "identity": {
        "user": {
          "id": "550fae72-d251-43ec-868c-3737xxxxx",
          "tenantId": "72f988bf-86f1-41af-91ab-xxxxx",
          "displayName": "Sample NAme"
        }
      }
    }

but once i try to use a Phone number as target i am having the follwing message
"403: request authorization tenant mismatch "

body sent :

{
      "identity": {
        "phone": {
          "displayName": "+1234xxxxx",
          "id": "+1234xxxxx"
        }
      } 
}

Graph SDK (beta):

Thanks in advance !
Mefteh.

The text was updated successfully, but these errors were encountered:

kanchm-zz · 2018-11-29T17:52:51Z

Currently PSTN calling is disabled. We are working on a licensing/pricing model before this capability is enabled.

mwerghemmi · 2018-11-30T09:08:42Z

Thanks Kanchm 👍

mwerghemmi · 2019-02-20T10:04:27Z

Hi @kanchm , @vinaychandra ,
Do you know what is the target release of this feature ? (in 2019 ?; Q2, 3 ..)
or at least to assign a SIP URI to a Bot to be available in the address book.
Thx !

VinodRavichandran · 2019-02-20T17:48:16Z

Hi @mwerghemmi , PSTN Calling is planned for this year, potentially by Q3.

mwerghemmi · 2019-02-21T09:07:46Z

Thx !

rossbuggins · 2019-03-18T20:06:02Z

Is there any additional info regarding how this might work, inbound / outbound, direct routing and also if cli masking will be possible for inbound PSTN calls to a bot that forward to teams user?

mwerghemmi · 2019-03-22T13:43:57Z

Hello,

rossbuggins · 2019-03-22T13:57:48Z

Hi @mwerghemmi thanks for getting back to me. So to confirm, you're currently thinking that in a direct routing environment, we would be able to deliver a sip call from existing pbx gateway to a bot on teams, and it perform it "bot logic routing" to a teams user, and also showing to that chosen user the CLI of the caller that we received into our pbx gateway?

Also, for outbound call, do you think there may be an option for it to "go through" a user bot, even when they just dial out a pstn call? IE we would like to perform specific logic / events depending on who a user has called etc.

It would be good to chat in more detail, thanks, Ross

mwerghemmi · 2019-03-24T13:03:20Z

Sure.

rossbuggins · 2019-08-16T13:46:07Z

Hi, has there been any discussion regarding inbound PSTN calls from direct routing being delivered to a bot? Is it still looking like a Q3 feature? Cheers

VinodRavichandran · 2019-08-16T18:18:11Z

Development is done, this is currently being tested by TAP Program user. Will publish the documentation through Graph soon.

adnkai · 2019-09-26T11:55:24Z

Any news on this one? Any testing progress so far? ETA maybe?

HindoliyaYogesh · 2019-11-14T17:18:23Z

Hi,
Any update on the roll-out of this one? ETA on the release?

Or, any possible way, I can create an IVR bot for incoming Teams call through PSTN from outer-world to agents in the organisation?

Thanks,

mwerghemmi · 2019-12-30T11:36:59Z

Hi @VinodRavichandran ,

I am testing a multi-tenant Application but still having error when i call the the application instance PTN number.

Setup is :

Tenant A host aplication bot and users
When i call the pstn number of application instance in tenant A it works (bot answer the app)

Tenant B consent the app only and host somes user...
when i call the pstn number of instnce in tenant B i am receiving the follwing error

"code":"7505","message":"Mismatch between request authorization tenant and call tenant.","innerError":{"request-id":"ca3d9426-7b46-44cb-90ae-a560f32eb054","date":"2019-12-30T11:31:20"

Any idea please ?

Note: Token was requeted from /common endpoint for the application bot

Many thanks in Advance !

VinodRavichandran · 2020-01-01T03:02:45Z

@ananmishr

mwerghemmi · 2020-01-22T09:00:12Z

Hi @VinodRavichandran @ananmishr
Any feedback on this one please ?
Thx !

Voxxie · 2020-01-23T11:29:46Z

Any news about this topic ?

Thanks

mwerghemmi · 2020-01-23T16:07:58Z

Hi @ksikorsk,
May be ou can help here, it sound similar to this case

ksikorsk · 2020-01-23T17:38:53Z

I am not familiar with the PSTN scenarios. @xixian73?

xixian73 · 2020-01-23T18:24:08Z

@mwerghemmi, let me try understand what's happening here.

Succeed case:

Application A and application instance A are registered in tenant A
Service number from tenant A (Let's call it Service number A) attached to the registered application instance A
Tenant A consented Application A
Teams user A called Service number A --> success!

Failure case:

Tenant B consented Application A
Teams user B called Service number A --> exception

Are the above scenarios correct?

mwerghemmi · 2020-01-23T19:56:51Z

@xixian73
That is correct !
Just another info: the above is correct when i use the /tenant/ouate/v2/token endpoint to get the token for the graph client.
If i use /common i have falure in both scenarios.

xixian73 · 2020-01-24T19:26:31Z

One ambiguity I forgot to confirm, did you assign the Service Number A to Application Instance B? @mwerghemmi

mwerghemmi · 2020-01-24T19:37:54Z

@xixian73 , i guess you mean assign service number B to application A (just 1 app and multiple services number)
my answer is yes i did, and application receive notification, when i Call service B but /answer fails with the error i shared

xixian73 · 2020-01-24T19:56:48Z

@mwerghemmi , So there should be three things involved in this case.

Application A
Application Instance (A or B?)
Service Number B

Did you assign the phone number to Application Instance A or Application Instance B?

mwerghemmi · 2020-01-24T20:04:31Z

@xixian73,
Each instance has its number.
Instance À —> number A
Instance B —> number B

xixian73 · 2020-01-24T21:28:26Z

@mwerghemmi Interesting, then it should work in this case. Do you more details for the error? Error message, CFV, any logs?

mwerghemmi · 2020-01-24T22:20:40Z

@xixian73
here is the token of the application (contains all information about the app if needed )

here the error when application post to /answer

body:"{"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

here is the application instance in tenant B

Get-CsOnlineApplicationInstance output

RunspaceId : 385eb46e-20a6-4b0d-bc8f-92771d01411b
ObjectId : 9f4388f5-f15a-4e71-9a7b-b89790b598de
TenantId : 00355275-f688-4140-86cb-10cf43a4533b
UserPrincipalName : Test.XXXX@YYYYY.onmicrosoft.com
ApplicationId : 2ad91f01-bf93-4313-89f1-cb201229e7db
DisplayName : Test XXXX
PhoneNumber : tel:+41432163273

hope this helps... i can share other details if needed

xixian73 · 2020-02-01T01:39:56Z

@mwerghemmi
This is the tenant Id from the token of the application:
"tid":"de5e3c28-141c-4d3e-90ea-aa3326abe67d"

The error message ssaying "mismatch between request authorization tenant and call tenant." Can you check if your request tenant is the same as the one in the token?

mwerghemmi · 2020-02-01T16:49:32Z

Hi @xixian73,
The application is intended to be multi-tenant.
So the request tenant will be different from the application tenant. in our case here request tenant is 00355275-f688-4140-86cb-10cf43a4533b.
is that a supported model ?
that us what i understand from the blog here
@VinodRavichandran any advise here please ?
Many thanks already !

bijaykush · 2020-03-03T08:49:50Z

@VinodRavichandran
@mwerghemmi
Any update on making outbound calls to PSTN?

jackycys · 2020-04-08T14:53:12Z

@VinodRavichandran
@mwerghemmi
Any update on making outbound calls to PSTN?

ananmishr · 2020-04-08T16:05:32Z

Hi @jackycys and @bijaykush we will release outbound calls to PSTN this year. I'll post more updates soon.

@xixian73 for @mwerghemmi 's question above

sidatacom · 2020-07-19T08:30:02Z

any update for outbound calls ?

larraiz · 2020-08-10T07:32:24Z

Hi all, I’m trying to configure my bot to answer a PSTN inbound call, my bot already answer a direct teams call however it doesn’t answer when I try my PSTN call. Anyone can help me with ? Thanks in advance

scarja268 · 2020-09-08T14:41:22Z

Hi are outgoing PSTN calls available now?

Sayyed-Abbas · 2020-10-29T15:05:01Z

@ananmishr @VinodRavichandran - Any update for make an outbound call to PSTN using Graph API ?
Looks like - currently "Create Call" API is supported only for P2P calling.

tsvsj · 2020-11-11T12:36:42Z

@Sayyed-Abbas based on https://docs.microsoft.com/en-us/graph/changelog there is no change for outbound PSTN calls reported. I'm afraid that we still need to wait for this feature, even if I can't imagine why it takes almost 2 years to implement this feature (until now), although it was already on the roadmap.

mwerghemmi · 2020-12-18T15:00:54Z

Hi @VinodRavichandran @ananmishr,

Any news regarding the graph API capability to call PSTN number ?
i think this was planned for 2020

Thx in advance

lund76 · 2021-02-17T13:02:04Z

It should be implemented now. But I have difficulties making it work:
microsoftgraph/microsoft-graph-docs-contrib#690

mwerghemmi changed the title ~~/calls/Create error if target is Phone~~ Unable to create call '/calls/Create' if target is Phone Nov 27, 2018

kanchm-zz added the enhancement New feature or request label Nov 29, 2018

vinaychandra mentioned this issue Dec 16, 2018

Is it possible/planned to enable assigining a PSTN number to a teams bot? #32

Closed

mwerghemmi changed the title ~~Unable to create call '/calls/Create' if target is Phone~~ Unable to create call May 29, 2019

ksikorsk mentioned this issue Jul 5, 2019

Outgoing call fails #17

Closed

Unable to create call #29

Unable to create call #29

Comments

mwerghemmi commented Nov 27, 2018 • edited

kanchm-zz commented Nov 29, 2018

mwerghemmi commented Nov 30, 2018

mwerghemmi commented Feb 20, 2019

VinodRavichandran commented Feb 20, 2019

mwerghemmi commented Feb 21, 2019

rossbuggins commented Mar 18, 2019

mwerghemmi commented Mar 22, 2019 • edited

rossbuggins commented Mar 22, 2019

mwerghemmi commented Mar 24, 2019 • edited

rossbuggins commented Aug 16, 2019

VinodRavichandran commented Aug 16, 2019

adnkai commented Sep 26, 2019

HindoliyaYogesh commented Nov 14, 2019

mwerghemmi commented Dec 30, 2019 • edited

VinodRavichandran commented Jan 1, 2020

mwerghemmi commented Jan 22, 2020

Voxxie commented Jan 23, 2020

mwerghemmi commented Jan 23, 2020

ksikorsk commented Jan 23, 2020

xixian73 commented Jan 23, 2020

mwerghemmi commented Jan 23, 2020

xixian73 commented Jan 24, 2020 • edited

mwerghemmi commented Jan 24, 2020 • edited

xixian73 commented Jan 24, 2020

mwerghemmi commented Jan 24, 2020

xixian73 commented Jan 24, 2020

mwerghemmi commented Jan 24, 2020 • edited

xixian73 commented Feb 1, 2020

mwerghemmi commented Feb 1, 2020 • edited

bijaykush commented Mar 3, 2020

jackycys commented Apr 8, 2020

ananmishr commented Apr 8, 2020

sidatacom commented Jul 19, 2020

larraiz commented Aug 10, 2020

scarja268 commented Sep 8, 2020

Sayyed-Abbas commented Oct 29, 2020

tsvsj commented Nov 11, 2020

mwerghemmi commented Dec 18, 2020

lund76 commented Feb 17, 2021

mwerghemmi commented Nov 27, 2018 •

edited

mwerghemmi commented Mar 22, 2019 •

edited

mwerghemmi commented Mar 24, 2019 •

edited

mwerghemmi commented Dec 30, 2019 •

edited

xixian73 commented Jan 24, 2020 •

edited

mwerghemmi commented Jan 24, 2020 •

edited

mwerghemmi commented Jan 24, 2020 •

edited

mwerghemmi commented Feb 1, 2020 •

edited