Or the XCOM games.
shininghero
joined 2 years ago
SIP providers usually sell numbers in contiguous series for businesses. For example, if your company buys a block of 50 numbers, the SIP provider then allocates XXX-5100 to XXX-5150.
But since you're keeping this strictly internal, you don't have to worry about that.
Step 3: unfuck the SIP settings, then email both HR and their supervisor to throw them under the bus. Also covers your ass for step 4.
Step 4: Route the manager's calls to a disconnected number. When they come knocking about their phone not working, tell them, "No, you should be able to dial out, unless someone changed the SIP trunk settings and didn't tell me."
Assuming you already have the IP phones, you need two things. A PBX server (for the VoIP stuff), and a SIP trunk with a block of external phone numbers.
Start with the PBX server software, there's several free/open-source implementations. Once you're comfortable with it and have internal calling good to go, then you can spend on the SIP trunk and number blocks.
I don't know of any exclusivity deals for apps. Haven't heard of that being a thing.
It's more likely an android versioning issue, where the app is too old to run on the TV.
Aaand that search query got me some files with the top secret flag. Fortunately, they seem to be internal memos on things that are already known to the public, so nothing too immediately dangerous.
My big question is, why in the ever-loving fuck are these files outside of SIPRNET?
Is this one of those vanilla memes that I'm too ReVanced to understand?
Counterpoint: Having those questions posited here does mean we can start getting fediverse traction in Google. Even if it's a tiny amount.
There's also a limited federation mode that server admins can use. Users and posts are still searchable, but they do not show on the public federated feed.
Useful for this exact case where a server may have beneficial accounts, but the rest should be hidden for moderation reasons.
Still would prefer it being on a proper mastodon server, but I can live with this. Whatever server ends up hosting a President's account now has to deal with record preservation laws for their posts. Let's leave that bureaucratic stuff to threads.
I had to check the proposal at its source to make sure it wasn't an April Fools joke.
Having managed an exchange instance for my old job, I can safely say that DKIM and DMARC are just some extra DNS entries for out-of-band verification. They can be boiled down to a pair of checkboxes on a compliance sheet.
I can also say that most of the companies we got emails from didn't have DKIM, and even fewer had DMARC. Or worse, they had DMARC set to p=ignore. Which is honestly even more infuriating.
Most people are under the impression that the cow is dead before it hits the ground, and way before it even goes in the grinder for processing.