- Joined
- Feb 28, 2022
- Messages
- 11
- Reaction score
- 1
Hello,
With the v18 Teams integration, I'm seeing an inconsistency when it comes to the call log: Teams will regularly mention a call as missed even though it got accepted.
After reading this: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-call-notifications - I wonder if the "REASON: SIP; cause=200;text”Call completed elsewhere”" message is properly implemented, or if this requires additional configuration on my side in either Teams or 3CX.
Out situation:
- We have a 3CX instance hosted by a 3CX partner
- We have a local SBC in the serverroom.
- We have on-premise phones which use said SBC.
- Teams is configured using the Direct Routing pointed at the PBX instance by the 3CX partner.
All this works great and we are really happy with it. But the missed calls that aren't missed calls bother me. In the above link it is explained this could happen if the 3rd party SBC (aka: 3CX according to Microsoft) accepts the call, but doesn't sent the right SIP message. However, I have disabled access to the 3CX clients for all users, so none is able to call outside of Teams except for the handful of on-premise phones, which I can see in the logs were not used. So I don't feel this is relevant to the problem...
What am I missing?
With the v18 Teams integration, I'm seeing an inconsistency when it comes to the call log: Teams will regularly mention a call as missed even though it got accepted.
After reading this: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-call-notifications - I wonder if the "REASON: SIP; cause=200;text”Call completed elsewhere”" message is properly implemented, or if this requires additional configuration on my side in either Teams or 3CX.
Out situation:
- We have a 3CX instance hosted by a 3CX partner
- We have a local SBC in the serverroom.
- We have on-premise phones which use said SBC.
- Teams is configured using the Direct Routing pointed at the PBX instance by the 3CX partner.
All this works great and we are really happy with it. But the missed calls that aren't missed calls bother me. In the above link it is explained this could happen if the 3rd party SBC (aka: 3CX according to Microsoft) accepts the call, but doesn't sent the right SIP message. However, I have disabled access to the 3CX clients for all users, so none is able to call outside of Teams except for the handful of on-premise phones, which I can see in the logs were not used. So I don't feel this is relevant to the problem...
What am I missing?




