Full Teams Client API including Call Control
Microsoft Teams should have completed Client APIs so that third party apps can be created to fill specific needs.
This API should allow call control of the Microsoft Teams application. Necessary call control features include:
• dial/call
• call answer
• hang-up
• hold/off hold
• call transfer (all types: blind, consult, safe)
• add participant
• mute/unmute
• park/unpark
• call as a delegate
Some general features include:
• search contacts
• get contact presence
• get contact list folders/contacts
• setup contact list folders/contacts
• get/set my presence
• get/set my note
• get/set my delegates
• get/set my Calling Groups
• Get/set my call forwarding
• get/set audio device
• get/set voicemail settings
Messaging
• get/send chat messages
• get/send voice/audio message
The above lists are not comprehensive but are to give an idea of the necessary features.
Also
The Teams Client API should be able to be used inside the Microsoft Teams client canvas or from a standalone application. Ideally, the application developer could decide if they want to access the above functionality by controlling the Microsoft Teams application, with the Teams app running alongside, or as a standalone application, without the Microsoft Teams application running.
We see this as part of achieving Skype for Business parity so ISV's can write applications like Attendant Consoles so organizations can move to Microsoft Teams.
Matt Landis
shared this idea
The team is reviewing possibilities in this space but does not yet have a date on this. We will update when there is news to share.
136 comments
-
Austin
commented
Would like to go the Teams route but have to go to Nextiva because there is no API for third parties to make a Salesforce screen pop when a caller calls. Landis Technology has this in there call center but it has other features that drive the price beyond what we are looking for.
-
Anonymous
commented
Well i tried to put it off, going to ringcentral, they have a great and well thought out API, shame microsoft that this wasn't considered sooner
-
JT
commented
A solution already exists. Run one system for attendant and reception and MS Teams for internal communication.
-
Wim Allegaert
commented
We had to block our migration to Teams-Only just because of this. Our reception staff is using Landis Attendant PRO. We can't take this tool away from them.
Don't say things like 'we are reviewing possibilities'. Say: we will fix this right away.
-
Anonymous
commented
Please give an update on this, this should have already been developed by now, not under review.
-
Anonymous
commented
Hi Microsoft. This is a Tremendous requirement. Everyone is saying it. Probably the biggest teams requirement of all time.
Can we have an upate?
-
DR Paquette
commented
In addition to the above. I would suggest the ability to have a video play in background in looped media or even an active stream capability.
Example (simulate meeting at work around a display that is two way com as well as picture in picture).
Also have the MS Teams application work/integrate better with other Microsoft apps. More often than not it hangs
-
Wilbert Zapata
commented
At Scantalk, we are selling more Attendant Console on traditional environments than our Operator Express for Skype4B as Customers must keep their old PBX to support non-Teams applications. Please release the API so we can assure a complete Teams migration.
-
Sean Stoller
commented
We are still waiting for these API's to move forward with MS Teams. My Salesforce rep tells me they are waiting on MS to make it happen.
-
Andreas Isengaard
commented
any updates in regards of this? We are experiencing a growing need for this as well.
-
Anonymous
commented
Anonymous below, (The missing API is becoming show stopper for big projects moving to MS Teams.) We are hearing this more and more. 10s of thousands if not hundreds of thousands of users that we know of are affected by this. Hopefully we are getting there soon.
-
Anonymous
commented
The missing API is becoming show stopper for big projects moving to MS Teams.
-
Pascal
commented
Please MS make this API possible asap. - we don`t want to go back to 3CX Phone.
-
Peter Schaunitzer
commented
Anything new on that? We would have to get/set the audio device settings in our standard environment to support VIP-Users
-
Timothy Meredith commented
Also to anonymous below, you can't "answer" all calls with Graphs, you can only answer calls for a number assigned to a bot. This is very cumbersome and restrictive to work around. You should be able to just have a simple user phone number with a simple API that allows basic CTI integrations (as all other phone systems have, even SfB has)
-
And another 2 months have gone by with no more response from MS..
-
Anonymous
commented
....and while you're at it, also implement so that we can set it through PowerShell and/or the Graph API from an Administrator's point of view.
-
Anonymous
commented
Hi. When will the api for Landis Attendant Pro be available. We are running expensive Skype hardware to cater for one person (our reception) who have to remain on Skype due to this.
-
Anonymous
commented
Hey Berta, Using Microsoft Graph Beta you can, answer, reject, etc, incoming calls, see link below. What Teams ultimately needs to compete is a friendly API with all Call controls, and not just to people in teams but specifically outside phone numbers if you have a calling plan. RingCentral has a great API but i want to be able to do everything in Teams including making outside calls, i just wish they would get on this so i can have one communication hub.
https://docs.microsoft.com/en-us/graph/api/resources/call?view=graph-rest-beta
-
Berta
commented
Hi anonym, you commented "... you can handle incoming calls now ...". Could you give a hint how to handle incoming calls now? What was changed? Is there a kind of event which is triggered now when a call comes in using the MS Teams application?