Unable to create call

[mwerghemmi]

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.

[kanchm-zz]

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

[mwerghemmi]

Thanks Kanchm 👍

[mwerghemmi]

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]

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

[mwerghemmi]

Thx !

[rossbuggins]

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]

Hello,

[rossbuggins]

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]

Sure.

[rossbuggins]

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]

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

[adnkai]

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

[HindoliyaYogesh]

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]

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]

@ananmishr

[mwerghemmi]

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

[Voxxie]

Any news about this topic ?

Thanks

[mwerghemmi]

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

[ksikorsk]

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

[xixian73]

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

Succeed case:

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

Failure case:

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

Are the above scenarios correct?

[mwerghemmi]

@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]

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

[mwerghemmi]

@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]

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

1. Application A
2. Application Instance (A or B?)
3. Service Number B

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

[mwerghemmi]

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

[xixian73]

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

[mwerghemmi]

@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 : [email protected] ApplicationId : 2ad91f01-bf93-4313-89f1-cb201229e7db DisplayName : Test XXXX PhoneNumber : tel:+41432163273

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

[xixian73]

@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]

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]

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