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.
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.
cries in kbin
Knock it off, Microsoft. You’re not my buddy, you’re an OS. Your job is to sit down, shut up, and run the programs I choose. That’s it.
If I find a function that’s useful for more than a week, I might make a batch file for it. Until then, you’re spare code.