10,946 questions
Is there any solution?
We have some Users with tihs strange behavior.
Not possible to change call answering rules
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 12%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EI%3C/text%3E%3C/svg%3E)
IBN
4,476
Reputation points
Hello
Please I need your help on this issue.
We have a single Teams Voice user who can not change his call answering rules (forwarding to a colleague while on vacation for example). For every other Teams Voice user it works without problem.
It is also not possible to change the settings via Teams Admin Center. When trying to change the settings there is the error message "We can't load the call answering rules." displayed and you are not able to save changes.
It isn't even possible to look at the settings via PowerShell (Get-CsUsercallingsettings will just display "An error has occurred").
Microsoft Teams | Microsoft Teams for business | Other
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
JimmyYang-MSFT 58,646 Reputation points Microsoft External Staff2022-07-12T02:55:30.933+00:00 Hi @IBN
We will check it later.
-
JimmyYang-MSFT 58,646 Reputation points Microsoft External Staff
2022-07-12T09:18:13.513+00:00 Hi @IBN
According to your description, it looks like this issue is only occurred in this user only, To narrow down this issue, we want to make sure if the other settings such as Teams meeting policy could be applied for him? If the issue is also occurred, we recommend you try to disable this user and re-enable it to see if it can be fixed.
-
JimmyYang-MSFT 58,646 Reputation points Microsoft External Staff
2022-07-18T13:03:09.337+00:00 It has been a while, how is everything going?
If you have any update about this issue, please feel free to post back.
Sign in to comment
2 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 31%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWH%3C/text%3E%3C/svg%3E)
Weber Harald 0 Reputation points2023-01-19T12:25:42.12+00:00 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 86%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFS%3C/text%3E%3C/svg%3E)
Foran, Shaun 0 Reputation points2023-10-06T14:59:54.56+00:00 Doesn't look like it as i'm having the same issue
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 74%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
brettfe 0 Reputation points2024-07-11T00:14:05.9833333+00:00 A solution was found for us through MS ticket 2405200030001117 (May 2024)
Product team confirmed this was a BUG for SIP device. ETA for fix: 28th June 2024
We confirmed the broken accounts remain broken, but SIP handset forwarding was the cause, and it no longer breaks accounts when used.
Details: When user had a SIP device handset, and used the MS short-dial code to set their forwarding, it broke the call answering rules in Teams phone system. eg: on a Polycom VVX410 SIP device the user dialled: * 33 * <cellphone number> and heard two rings before the call hung up automatically.
This caused the issue. Confirmed in Teams Admin Center > user's account > Voice settings > "We can't load the call answering rules" popup warning appears.
Accounts that have experienced this issue ARE NOT FIXED by Microsoft's fix.
We opened new tickets to rectify accounts, but ultimately the accounts had to be recreated.
If your environment has no SIP devices (only Teams native handsets) this might not have been your issue.