Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
It's a little thing and I still have to use it, but Cisco Jabber is the most annoying piece of software I have ever used.
It should just boot up and make calls, right? Nope.
It constantly changes the audio output settings dynamically and I can't get it to stick to what I want. Oh, we using the desktop monitor speakers this time the laptop booted up?
It fails to keep credentials and I have to reset it at least once a week.
It does not have a user setting to make it stop taking over as the messaging app. We use Teams for that, which is also pretty crappy but not nearly as annoying as Jabber. Apparently there is a way to address this during installation, but our IT support can't get it to work so I have to manually start up Jabber before Teams because the last one takes over.
Plus all of that is for an occasional phone call that tends to be missed because Jabber decided to forget the credentials again. I have reset Jabber more times than I have received a phone call through Jabber.
I used to do support for a university that used Cisco Jabber internally, and can confirm that's exactly what it was like.
I helped a colleague recently with an issue where Jabber wasn’t playing audio. I had a hunch it was related to an issue that’s cropped up a few times.
So I checked system settings, which were fine. Checked system settings for the Jabber app, and those were fine. Stumped, I poked around in Jabber’s settings, where I discovered it had ignored both the system settings, and the system settings for it, to try to send audio to her speakerless computer monitor.
Oh god, a bunch of my coworkers "used" Jabber at my last job and I was told I could, too. After hearing them complain I said nah and got my own Google Voice number and a cheap headset to use when I was working from home. Jokes on me, though, it meant I didn't have any excuse to ignore client calls like everyone else.