We received a request from a customer using Teams.
This customer only wants to use 3CX for additional call analytics via the API and otherwise remain entirely on Teams for telephony.
We’ve set this up so far, and it’s working.
However, the following issue remains unresolved:
An incoming call via a trunk to 3CX should be routed to a Teams resource account and then into a call queue.
Is there a workaround that supports this scenario?
What has worked so far is:
- Enable M365 resource account sign-in and synchronize users
What doesn’t work:
- The user isn’t displayed as “Teams” in 3CX and is therefore not included in the export script; additionally, when an incoming call arrives, the system attempts to connect to the Teams resource account
Does anyone here have a suggestion or a solution
This customer only wants to use 3CX for additional call analytics via the API and otherwise remain entirely on Teams for telephony.
We’ve set this up so far, and it’s working.
However, the following issue remains unresolved:
An incoming call via a trunk to 3CX should be routed to a Teams resource account and then into a call queue.
Is there a workaround that supports this scenario?
What has worked so far is:
- Enable M365 resource account sign-in and synchronize users
What doesn’t work:
- The user isn’t displayed as “Teams” in 3CX and is therefore not included in the export script; additionally, when an incoming call arrives, the system attempts to connect to the Teams resource account
Does anyone here have a suggestion or a solution
