Microsoft Teams - Call forward to external, different behavior between webbrowser and teams client

Dennis Backx 116 Reputation points
2021-11-10T14:52:28.743+00:00

English:
We have setup a working Microsoft 365 Teams direct routing environment using KPN as telecom operator. All users have sufficient licenses (E5, including phone system) and the trunk is working fine. The issue appears when the following situation is created:

English:
A number call to B number (teams user with direct routing)
B number preforms consultation call to C a teams colleague user (teams using with direct routing).
When C has no forward setup the calls get connected, when C user has setup a external forward to for example +316***** the call gets dropped.
This occurs using specifique the Teams desktop client. When using the webbrowsers teams client the call gets connected.

Dutch:
We hebben een Microsoft 365 direct routing omgeving opgezet met KPN, dit werkt naar behoren. Alle gebruikers in de test beschikken over de juiste licenties (E5 dus inclusief phone system).
Het issue ontstaan zoals hieronder beschreven.

Dutch:
A nummer belt B nummer.
B nummer voert ruggespraak met zijn collega via een sip call (peer-to-peer) om aan te geven dat hij iemand aan de lijn heeft (A nummer).
B kiest ervoor om het ruggespraak gesprek door te verbinden (a naar c dus) .
Wanneer B zijn desktop client teams gebruikt met een doorschakeling naar extern +316**** wordt het gesprek gedropped. (kan niet doorverbinden) , wanneer B de webversie van Teams gebruikt wordt het gesprek netjes doorverbonden naar de forward call +316***.

Iemand hier ook ervaringen mee en hoe heb je dit opgelost? / Anyone else experience this and how did you resolve it?

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
10,829 questions
{count} votes

Accepted answer
  1. Dennis Backx 116 Reputation points
    2021-11-16T10:33:31.717+00:00

    @JimmyYang-MSFT , we have tried this via a ticket at Microsoft. The problem in this case is that PSTN provider points responsibility to Microsoft and Microsoft points responsibily to KPN.
    Will submit a new ticket with new found information and hopes this is sufficient to resolve the issue.

    tnx

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.