What Are You Doing Right Now
-
@RojoLoco you sure those aren't currants? LMAO
-
@RojoLoco said in What Are You Doing Right Now:
@ChrisL said in What Are You Doing Right Now:
Listening to Big Boi's new album "Boomiverse"
How is it? I haven't heard any of it yet.
Not as good as "Sir Luscious Leftfoot" but maaaaaybe above "Vicious Lies..."
-
@RojoLoco Mostly, I just want one giant RTJ + Big Boi album.
-
Just waiting this power outage
-
@scottalanmiller said in What Are You Doing Right Now:
@wirestyle22 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
There's no ethical grey area
A loophole can be grey, but I agree this is not a loophole.
I never said a loophole can't be grey. This isn't grey, because there is nothing like a loophole.
Right my point was very clear that this is not a loophole. It is a specifically allowed methodology.
But @dashrender still molested me in a chat about this, simply because he apparently refuses to acknowledge the definition of loophole.
Also, did we not just have a post earlier this morning about @dashrender attempting to redefine things?
-
@scottalanmiller said in What Are You Doing Right Now:
We had like a raft of new users, but then now it's been nearly a week without anyone. Weird how that happens.
And what is everyone up to today?
Was driving down to St Louis all afternoon.
-
-
Another successful test call with my FreePBX test.
-
-
@coliver said in What Are You Doing Right Now:
I was just reading that on a different site - scary shit now that they're after linux
-
@MattSpeller said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
I was just reading that on a different site - scary shit now that they're after linux
I need to read it fully. I'm sure this is a misconfiguration on the hosts end.
-
@coliver NO, they were running way outdated kernels and web hosting which was prone to vulnerabilities.
Maybe backups wasn't a priority nor updating.
-
@dbeato said in What Are You Doing Right Now:
@coliver NO, they werw running way outdate kernels and web hosting which was prone to vulnerabilities.
Maybe backups wasn't a priority nor updating.
Yep not keeping a production environment patched... Seems like they set themselves up for failure.
-
@coliver said in What Are You Doing Right Now:
@MattSpeller said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
I was just reading that on a different site - scary shit now that they're after linux
misconfiguration on the hosts end.
This is a safe assumption with anything not pwned by state level actors and even sometimes then too
-
Alas, now my calls are failing (despite making and receiving calls using the same phone numbers). Inbound receives a busy signal. Outbound receives "The number has not yet been assigned." Yay troubleshooting.
-
Looks like the issue was somehow my voip.ms was not showing as registered to a server (atlanta2).
-
@EddieJennings said in What Are You Doing Right Now:
Looks like the issue was somehow my voip.ms was showing as registered to a server (atlanta2).
Is that not your server?
-
@scottalanmiller Just edited it, as I realized my error. I've made a sub account now, and so far haven't been able to replicate the problem of it not longer being registered. I have an idea as to what happened, but I need to give this more time to potentially fail.
-
Bah, now the account shows as not registered again. Might be time to just take a break and pick back up tomorrow.
-
Following the advice here: http://wiki.voip.ms/article/Registration_issue Looks like the issue has been resolved by lowering the expiration (lowered to 120 as suggested in the article).
