Dear Sirs,
We are using Teams including Calling. We have a small team with Call Forwarding active, within 20 Seconds no Answer the call is forwarding to each Team Member.

Each Team Member will see the call during ringing with “forwarded by name of user” but in the history it looks like it was a direct personal call. The problem is that everyone is now trying to call back.

In the pictures there is how the call forwarding settings are, how the current history looks like and how a forwarded call look like when ringing. Although there is an idea how a forwarded call could look like when in history.

The Second part is that an answered forwarded call from a colleague wouldn’t be visible in the forwarder’s history, so didn’t sees that someone else picked the call and is now in charge.

Haven’t got an Idea yet how it could look like but maybe only instead of showing “missed call” something like “answered by name of user” could solve the issue.

Hope it will help us all.

Thanks a Lot

Best regards,
S. Calvert

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.

The updated calling experience GUI is not felxible enough to meet different requirements.Some secions ( see coloured squares in the screenshot) are to small, others takes a lot of space but probably not of interest. Since TEAMS provide no specific attendant console for calls, the switchboard have to use the provided one. But there it is not possible to have a quick view wich clients are in a call or present at all bfore transfering an incomming call. In the old GUI it was at least possible at the favorites but in the new one this section is so small. on the other hand, recent calls are not of interest for a attendant but this section takes a lot of space in the GUI. So please make this calling GUI more flexible for clients do decide themselves wich section contains wich informations.

After several months of troubleshooting, Microsoft have finally admitted that the issue of call drops and conference participant drops when muting, are by design. When a participant mutes their client (mobile, desktop, or web), the SIP traffic stops sending media, but doesn;t send any for of keepalive to appease Tier 1 carriers that implement NO RTP timers.

The science behind this is that there are Communications RFC’s from the IETF that all providers agree to. One of these suggests that in the event of no RTP being received from the far end, a timer will be set in order to prevent a stale call session. Some carriers implement a matter of minutes or hours, it’s entirely at their discretions. In the case of BT in the UK, they have their timers set to 120 seconds.

This post is to request that Microsoft amend their SIP signalling or Mute behaviour, in order to fall in line with other PBX vendors and carriers and follow the IETF RFC's on comms.

In light of this, our current workaround is that if clients have a compatible headset, they can retract the mic boom and the hardware will mute itself, or the noise cancelling is so effective that it’s as if you are on mute. For any other methods, the answer is to not use mute for longer than 2 minutes.

In the new Calls screen layout, the Call History section takes up a large amount of space that is blank for the most part (unless there is a message that you have a voicemail).

Because of the large Call History pane, the Speed Dial pane has been shrunk. Our users utilized the Speed Dial option for calling, especially for calling outside our org to people not in a Team.

Would it be possible to have a drag bar on the right hand side of the Call History Pane so that a user can decrease the size of the Call History Pane and increase the size of the Speed Dial pane.