Hi @Peter,
Welcome to Q&A!
Before the troubleshooting, please kindly share more information here:
- When this issue start?
- Are there any related changes before this issue occurs? Such as the normalization rules, dial plans or anything else.
- Could you accept the call on your mobile even the caller id show as anonymous?
- How many users experience this kind of issue?
- Does this issue happens on both IOS or Android client?
- Is there any different setting between the affected user and non-affected users?
For this call forwarding issue, we have some suggestions as below for troubleshooting:
- If you're an administrator, please Run Diagnostic tool (https://aka.ms/TeamsCallForwardingDiag) to validate if your Teams account is configured correctly to forward calls received in Teams to a specific number.
The detailed steps to use the tool are documented in this article (Configure call forwarding and delegation settings - Microsoft Teams), the tests will return the best next steps to address any user settings or configurations to validate that the user is properly configured to forward calls to a specific number in Teams.
- Comparing the call forwarding related settings for both affected users and non-affected users and attempt to change the settings as the same as the non-affected users to see if it could resolve the issue.
Running this cmdlet could get the detailed settings for users: Get-CsUserCallingSettings -Identity "yourTeamsAccount"
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our [documentation]](https://aka.ms/msftqanotifications)) to enable e-mail notifications if you want to receive the related email notification for this thread.