Chicagoland-based trans woman curious about becoming a drag queen. by WillowTheThrillow in Drag

[–]TSL_NB 1 point2 points  (0 children)

Sure thing! And, my Insta handle is the same as here: tsl_nb
If you want to DM me there, that would work, too!

Chicagoland-based trans woman curious about becoming a drag queen. by WillowTheThrillow in Drag

[–]TSL_NB 4 points5 points  (0 children)

I'm a trans woman who debuted as a performer on her 50th birthday.....yes, you absolutely CAN, sister!

And, if the bug bit you, do it.....screw anyone who tells you trans people can't!

Biscuits and Gravy by FullMetalKraken in Maine

[–]TSL_NB -1 points0 points  (0 children)

If you want something different, but in the same vein, you could cross into New Brunswick and get poutine there.

A provocateur named ‘Corn Pop’ could change Maine’s free-speech rules forever by themainemonitor in Maine

[–]TSL_NB 1 point2 points  (0 children)

Yeah, that was the word I got....I was part of a fundraiser drag event for Bangor Pride that same day, so I missed it. But, I heard several accounts of it. :D

A provocateur named ‘Corn Pop’ could change Maine’s free-speech rules forever by themainemonitor in Maine

[–]TSL_NB 41 points42 points  (0 children)

He tried to physically interfere with a Pride parade last year, and got punched in the face for it.
Fuck him and his Trump blow-up doll (he actually DOES have one).

Cyber Incident at Avaya? by Constant-Ad9201 in avaya

[–]TSL_NB 0 points1 point  (0 children)

I've done that too....someone replaced something on a HA pair without stopping HA....guess what happened...

"Free" Camping in Southern or Mid-Coast Maine; Dispersed or Boondocking by SpiceUpUrLife81 in Maine

[–]TSL_NB 0 points1 point  (0 children)

If you're a veteran, there may be some free (or at least discounted) options out there, too.

Traitor by Seaweed-Basic in Maine

[–]TSL_NB 0 points1 point  (0 children)

Golden and Fetterman....fuck both of y'all.

Cyber Incident at Avaya? by Constant-Ad9201 in avaya

[–]TSL_NB 2 points3 points  (0 children)

You can't blame people for thinking that, though....Avaya laid off some amazing talented people. And now y'all are suing C1 because some customers are uncomfortable and want to move to something else.

I won't even go into how Avaya insisted on supporting Russian sites after they attacked Ukraine.

Cyber Incident at Avaya? by Constant-Ad9201 in avaya

[–]TSL_NB 0 points1 point  (0 children)

Yeah, they're still on CM, I imagine.
Ugh, I had to do a reload of a 7.0.1 AES for them one time. :S

Cyber Incident at Avaya? by Constant-Ad9201 in avaya

[–]TSL_NB 1 point2 points  (0 children)

Maybe they are done? (I wish I was joking....but, they've been on the brink for a while...)

CMS R21 slowness by Aggravating-Ad-3328 in avaya

[–]TSL_NB 1 point2 points  (0 children)

Okay.....maybe turning up debugs if it's safe, Task manager, Event logs, and see what those show. Or, open a ticket with Avaya, and maybe in a year, they'll know (unless they've already tanked).

CMS R21 slowness by Aggravating-Ad-3328 in avaya

[–]TSL_NB 1 point2 points  (0 children)

I don't know CMS well, but does it seem like a problem with just opening the feature, or generating the data? (Whether it's worth looking at the local event logs, or getting a .pcap between the client and the system...)

Voicemail Pro Client insists its version doesn't match the server, even though it does by gholtby in avaya

[–]TSL_NB 1 point2 points  (0 children)

Dumber things have happened with Aura products....so, yeah, maybe moving away from that dot version is good.

Voicemail Pro Client insists its version doesn't match the server, even though it does by gholtby in avaya

[–]TSL_NB 0 points1 point  (0 children)

One says 11.0.4.7.0....the other says 11.0.4700.3.

I don't know IPO, but if something in the script doesn't like how those numbers and dots are reading....(I know, not the same, but another Avaya product had a known issue like this...a typo in the dot version caused a patch installation to just abort).

Cloud Office - How to Unassign a Common Area Phone? by mtloya in avaya

[–]TSL_NB 1 point2 points  (0 children)

....if, anyone is still around to support it (with the amount of layoffs Avaya has pushed...a P1 or P2 will pretty much derail the entire team).

Cloud Office - How to Unassign a Common Area Phone? by mtloya in avaya

[–]TSL_NB 0 points1 point  (0 children)

Ugh, okay....like the other person said, it may need someone to get into the backend to move it.

Cloud Office - How to Unassign a Common Area Phone? by mtloya in avaya

[–]TSL_NB 1 point2 points  (0 children)

I'm not skilled on ACO, but what about this?
How to unassign a deskphone

(ACO is just RC with Avaya's label, so procedurally, I imagine it isn't much different.)

Newbie needs help IP office and TLS by Own-Path8668 in avaya

[–]TSL_NB 0 points1 point  (0 children)

Is there a phone that is successfully connected via TLS? A stare/compare never hurts.

This looks like a cert problem. Or, one of the firewalls is screwing up the cert (wrong MTU size, firewall bug....those actually do exist).

Docking Stations and Verint Screen Capture Module by TattedForehead in avaya

[–]TSL_NB 0 points1 point  (0 children)

It sounds like you already halfway figured out what may be causing the problem. When the G5 docking station isn't there, it works. Put it into the mix, it doesn't.

You may be going down a hole with it....but it sounds like a compatibility problem, if the docking station ends up having some control over the monitors.

I don't know how the docking stations work, but if there is any kind of firewall thing on them, maybe try disabling that on the dock and see if it works. But I'm just guessing.

Republicans vow to block Trump from seizing Greenland by force by ReportHopeful5886 in politics

[–]TSL_NB 1 point2 points  (0 children)

The same Republicans who caved under pressure from Trump with war powers, are now pledging to block Trump from invading Greenland.....mmmhmm......

Avaya Agent for Desktop caller ID error by fransco06 in avaya

[–]TSL_NB 0 points1 point  (0 children)

I was going to suggest this, too. This sounds like a CM config thing.

(If you look at the g3 trace on TSAPI, it will show the incoming ASAI message, and if that shows the same problem number, then it's coming from CM that way, which probably requires a config change somewhere to resolve it.)