Boss/Secretary
Has anybody played with the (apparently) new Boss/Secretary option that is offered up now in extension management?
Has anybody played with the (apparently) new Boss/Secretary option that is offered up now in extension management?
Trying to perform a speedtest from the router but it seems Fortinet doesn't think this functionality is something that should be simple and easy (and requires some specific license).
What are people doing to perform a speedtest, (even from CLI) on a FortiGate device?
Edit/Update: Thanks for the suggestions I checked over
https://docs.fortinet.com/document/fortigate/8.0.0/cli-reference/244193505/execute-speed-test-custom
and
https://community.fortinet.com/fortigate-3/troubleshooting-tip-configure-fortigate-as-speed-test-iperf-server-119532
But could not get a single speedtest to return valid data, servers too busy, or flat out refused, or would do an upload test but not a download..
Has anyone got a working example of speed-test-custom?
We administer Remote Desktop Services environments. The public AccountRight PC Edition installer installs a complete 486 MB application into %LOCALAPPDATA%\Programs\MYOB\AccountRight for each user. The MSI installer is documented as supporting offline company files only after 3 August 2026.
Is anyone aware of a supported deployment method for AccountRight PC Edition in a multi-user RDS environment that avoids per-user application installations?
I'm not sure whether this is a 3CX issue, a Yealink issue, or some wonderful combination of the two, but I'd really appreciate a bit of consistency.
I recently deployed three brand-new, out-of-the-box Yealink T46S phones.
After about five minutes, only two of them appeared in the 3CX PnP list. No problem — I assigned both to their respective extensions.
One provisioned and registered perfectly.
The second one? Not a chance.
I could reach it over the network, so I rebooted it. No change. I removed it from PnP, deleted the phone from 3CX, manually updated the firmware, rebooted again, re-added it, and somehow it suddenly decided to provision correctly.
Meanwhile, the third phone finally made an appearance in the PnP list. Naturally, it refused to provision as well.
I repeated the exact same process that fixed the second phone. Still nothing. In the end, I had to log into the phone's web interface and manually enter the provisioning URL before it would finally register.
Now for the best part.
Today, there are still two devices showing in the PnP list despite already being assigned and working perfectly. The third device, the one that caused the most trouble, isn't listed at all.
All three phones are operational. Two appear in PnP when they arguably shouldn't. One doesn't appear when perhaps it should.
At this point I'm less interested in fixing the issue and more interested in understanding what sequence of events inside 3CX and Yealink firmware led to this particular outcome.
Has anyone else seen similar behaviour with T46S phones, or is this just one of those provisioning mysteries we're all expected to accept and move on from?
Such inconsistent behaviour
3 x T46U desktops on a 3cx pabx
Plugged into network and allowed to startup
All three turn up in PNP page, as expected. Programmed all three to pick up config.
1 of them configured with no issues, 2 of them didnt
of the 2 that didnt manually updated firmware, clicked a factory reset and it comfigured okay, the other didnt.
Remaining unit, updated firmware, remoted in and it insists on a password change before proceeding and doesnt configure.
3 devices purchased together, 3 different behaviours when introduced to same network.
rant over.
For reasons best left to them, my hosting provider required me to upgrade my hosting and as a result I now find myslef on v118 on a AlmaLinux 9.8 (previous was on CloudLinux 7.9), as a result the CCS (Calander and Contacts Server) has not carried over because it isnt supporte don that platform.
This is very annoying as I have now lost what I consider basic funtionality.
I'm curious as to why this software isnt compatible?
Is there an app of some sort that makes the gathering and checking of logs to determine the reason why an installation failed, it seems so tedious at the moment having to remotely mount an endpoints drive to then mine your way down to a log file and such, there must be an easier way.
I know this is probably going to get buried under “spam prevention” arguments, but 10DLC has become one of the biggest, anti-compettive rorts to happen to small business communications in years.
The original pitch sounded reasonable enough: reduce spam, make messaging more trustworthy, register businesses, etc. But in practice? It feels like a giant paywall and compliance maze that mainly benefits carriers and the companies selling “compliance services.”
A few things that really bother me about it:
And honestly, the most frustrating part is that SMS used to be one of the last relatively open communication channels. Now it feels like email all over again: gatekeepers everywhere, opaque filtering, and compliance bureaucracy piled on top of already expensive telecom services.
What bothers me most is the precedent this sets.
We’ve quietly accepted a system where a small number of carriers, aggregators, and compliance vendors effectively decide who can reliably communicate at scale, under what conditions, and at what cost.
That should concern people far beyond telecom nerds.
Because at some point we have to ask: who should hold the switch to a nation’s voice?
Right now the answer seems to be: whichever corporations can afford the compliance department.
I’m not defending spam. Nobody wants robocall-tier garbage flooding phones. But the current system feels massively over-engineered and tilted toward incumbents.
Curious whether other people in telecom/VoIP/MSP land are seeing the same thing or if I’m just becoming old and bitter.
I threw together a video and posted it here https://youtu.be/pEdcVMyJMUY