Earlier quoted context omitted.
It probably also depends what you are used to. Younger people have only ever used bloated laggy stuff like teams and don't know any better. I miss the days of just having a dedicated desk phone - it rings, you answer, and talk instantly. Teams in comparison pops up a call dialogue box, have to navigate the mouse to answer (because the answer hotkey doesn't work most of the time), wait for it to connect, fuck around f…
> I miss the days of just having a dedicated desk phone I don't really. It tied me to my desk. Now my extension is wherever I want to work, not just at my desk. Its on my cell phone, its on my work laptop, its wherever I am. Loads of desk phones didn't have any Bluetooth support so using a headset meant getting a probably expensive maybe proprietary thing with EHS support (or a mechanical handset lifter!!!). When I w…
I had an pre-voip Avaya phone with 24 speed dials - for each contact it had a red/green LED next to the speed dial button that showed if they were busy. If it was green you could just press it and call. It had a proper headset port so no ghetto lifter :)
Teams has available status also, but I find its pretty much useless as people either fake their status to avoid being hassled, or its synced to their outlook calendar that has so much junk in it that they show as busy all day.
Roaming around wasn't much of an issue either, I just had forward to cell phone if it wasn't answered after a certain number of rings.
We also had integration with windows so tel: links and dialling from contacts worked as expected.
In the end I've learnt to live with teams, I made a small "chat" script that uses a teams url [0] to open a chat with a person from the command line vs hunting through the awful laggy ui, another AHK script to make a global mute hotkey based on a library I found on github, and another script I wrote to fix the audio device.