You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [ X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
Update code or Provide instructions on how to use the Calling Sample to call a Call Queue or AutoAttendant or any Phone Resource Account in Teams. These do not seem to have 8:org IDs. The non React demos allow for calling 8:echo123 for testing as well which is ACS Echo bot. The React sample blocks that
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Versions
Latest version as of 2024-10-17
Mention any other details that might be useful
Thanks! We'll be in touch soon.
The text was updated successfully, but these errors were encountered:
Hi @GauravES, sorry for slow response.
You can call call queue of auto attendant by entering the user id of the associated resource account. You can find out the user id of resource account using Microsoft Graph Explorer as described in our storybook page. In that documentation, we did forget to mention that resource accounts are prefixed by '28:orgid:' instead of '8:orgid:' so make sure to keep that in mind.
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Versions
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: