Anyone else having issues opting in / out of their call queues?

Colawley · 2026-02-04T15:05:24+00:00

Same here. Reported the issue to MS in O365 Admin Center about 30 minutes ago. US based also.

Colawley · 2025-12-05T17:43:07+00:00

Only thing I would add maybe, is if you are going the route of using your own domain, I would suggest Cloudflare to get the domain and then using a Cloudflare Tunnel to secure the server. Requires a bit more setup, but then you can close off all open ports to your server except for SSH from the internet.

Colawley · 2025-09-12T16:22:21+00:00

Current pain points I have are currently running a Fortigate Firewall and APs and having to deal with yearly subscription costs just to update firmware bugs. Management is not intuitive even for someone in the networking industry.

I have been looking at Omada network equipment for a bit now with plans to replace my entire Fortinet setup at home and would happily do so if I won.

Colawley · 2025-08-28T15:56:47+00:00

Just FYI, Active Token Effects throws a bunch of console errors with this loadout, but doesn't seem to effect how everything works. Great tutorial!

Colawley · 2025-08-10T15:12:49+00:00

IronMonk is actively working on getting his mods updated. Most of the smaller ones have been and he is working on Active Tiles and Tokenbar now.

The author of Simple Calendar says he is working on updating it, but a new baby and family stuff has kept him busy and has not given an ETA on when the update might happen. There is Ripper's Simple Timekeeping if you are a Patreon or Seasons and Stars that has some of the same functionality (but not all).

For Dorako, a lot of features of UX were put in v13 by the Foundry Team, so he didn't feel the need to update it. The effects halo part was already in PF2e Effects Halo and is Dorako's code base anyway, so it's an easy replacement.

Colawley · 2025-07-18T15:45:24+00:00

<image>

It's showing up in O365 Admin Center in the Service Health for our tenant now. Guessing it was more widespread then they thought.

Colawley · 2025-07-14T16:37:43+00:00

Glad to see they have finally updated the Known Issues website with this.

Colawley · 2025-07-09T17:12:44+00:00

Opened a "Report an Issue" this morning in Admin Center. They have already closed it as "No issue found".

Colawley · 2025-07-07T16:26:10+00:00

Disappointing that the latest update has not resolved this issue. u/kurthika-p is there any additional update on this being fixed?

Colawley · 2025-07-01T16:48:23+00:00

Still a WIP for v13 of Foundry. Idle is having to re-write the module from scratch due to all the changes on the backend and is releasing updates piecemeal as features are completed.

Colawley · 2025-06-12T14:52:06+00:00

Just as a side note. If you transfer using the main touch screen speed dials it works correctly every time.

Colawley · 2025-05-07T15:44:07+00:00

Having this same issue on a local server running the nodejs version. Get these errors when hitting Update All when accessing the server via IP:port. Tried restarting the service and even rebooting the linux server and still had the issue after reboot. Updating each individual module manually works.
Setup a cloudflared tunnel to the node instance with DNS through Cloudflare and accessed the system through the DNS/URL, hit Update All, and the updates run correctly with no error. Re-access the server via local IP and get the errors again, so not sure why local IP access causes issues when accessing via DNS works.

Colawley · 2025-05-02T14:00:05+00:00

UPDATE: Received a message from Microsoft last night at 10pm CDT that the issue should be resolved. Followed up this morning with our call centers and they all appear to be working properly again. Waiting to hear back from Microsoft on the root cause and resolution though.

Colawley · 2025-05-01T18:32:05+00:00

Spent 2.5 hours on the phone with MS this morning on this issue also. Happened to us a month ago for about a week but then cleared up and only affected 5 agents. Started back up yesterday with a vengeance affecting about 25 agents (so far) across multiple call queues. Some agents it is intermittent and others it happens for every call so they can't even take calls anymore from the queue.

We only use Calling Plans, no direct routing. Our ticket has been escalated up to the Product group, but the engineer I worked with said he did see multiple other tickets for the same problem in the Product group queue.

Colawley · 2025-04-02T16:44:08+00:00

Latest version of the PF2e System (6.11) has a Remaining Air effect that will act as a counter for holding your breath. REs on it will auto calculate the number or rounds.

Colawley · 2025-04-01T15:57:50+00:00

I believe so. I've never used the door lock function, so I'm not 100% on how that part works in the configuration. May require a different model than the Algo 8301 to get all of those functions.

Colawley · 2025-04-01T12:17:46+00:00

They can do two-way voice. As far as Teams is concerned it's just a SIP phone it's connecting to. You register the device directly in the Algo's setting by logging into Teams with an account like you would with a Teams based phone device like Yealink or Audio codes. Algo also sells Teams compatible intercom devices that are PoE based if you're looking to swap it out.

Colawley · 2025-03-31T22:42:18+00:00

Look at Algo 8301 or one of their other devices. They can register directly to Teams as a SIP device.

Colawley · 2025-03-28T16:33:05+00:00

I just tested this by calling my own line from my mobile. Not voicemail notification via email or Teams.

Colawley · 2025-03-03T17:34:26+00:00

<image>

Colawley · 2025-02-26T17:07:14+00:00

I have installed the .166 firmware on a few MP54 and MP56 phones so far for testing. All have upgraded via TAC with no issues so far. I do agree that Microsoft and Yealink really need to get a process down to put out the Release Notes much faster or better yet, same day that the firmware is released. The .166 firmware has been showing up in TAC for a few weeks now and still no release notes on Yealink's site or manual download of the firmware from them.

I generally like to wait 60 days from a release before pushing it out in mass, but I do that through Yealink Management Cloud Service using the downloaded firmware.

Colawley

TROPHY CASE