I don't understand what you want to know.

@Mike-Ralston abbreviated a bit, but hit the basics.

Before you can do any routing, you define the trunk. Once you have that up, then you can worry about routing.

For Inbound routing, you have a few choices.

First you have to know if you need to even care about the DID the called dialed. If you do not, things get easy. You just create or edit the any/any inbound route and scroll to the bottom as noted to set the destination.

If you have to be more specific, then you need to first know how the number is being passed into your system. Using US dialing as an example, numbers come in the format NPANXXXXXX and the country code is 1.

Depending on the SIP carrier, the call may be presented to your PBX with or without the 1.
VoicePulse sends the DID with the 1 while VoIP.ms does not.

This can be important depending on how you want your routing to go.

You specify in the inbound route what inbound DID it will match on.
img

You can additionally specify the the route matches on the CID of the inbound caller if desired for very fine grained routing. Somehow that annoying person also seems to get routed to Time and Temp? What? 🙂

You have a few other choices to make on the way down the screen, then you pick the destination for the calls that match the above two criteria.
In this case an IVR.
img

Sure, but it would depend on your system in question. Which resource are you lacking? If you don't have enough CPU, then CPU will be your bottleneck. If you don't have enough RAM, then memory will be, etc.

PBXs handle whatever loads you design them to handle. With enough resources a PBX can handle millions of calls.

@johnhooks said:

@scottalanmiller said:

@johnhooks said:

I knew the workstation version was, I just didn't understand why they have a "server" version.

Server and workstation are just different sets of packages. Not different products. Server is the actual proving ground, the workstation isn't really a big deal since no one actually uses CentOS or RHEL as a desktop, that would be pretty silly in general. Fedora Workstation is the product that is actually used as a workstation. It is Fedora Server that is the actual proving ground for CentOS and RHEL.

I actually did use CentOS 7 as a desktop for a while, just to try it. It wasn't bad. I don't use anything strange, and was able to compile everything else I needed. Their gnome theme is pretty nice.

Thing is, if you used CentOS 7 that means that it was pretty new. But CentOS 7 will be one painfully old desktop by the time that CentOS 8 is getting close. Fedora updates every six to eight months, so their desktops are always current. So you are never looking at something outdated. CentOS 7 will be many years out of date when it is time to replace it.

RPi's are freaking awesome for learning linux or programming or electronics. When I see one my mind boggles at all the possibilities they contain. Like below, they're nothing special as far as a computer goes, but if they ignite your passion then I would consider that valuable and worth pursuing.

@Carnival-Boy said:

AFAIK all the registrars I've ever used have offered e-mail forwarding free of charge.

Good point, forgot about those. Most web hosting services do too (assuming that you have one already.)

I gave my friend the link hoping he'd post - I haven't spoken to him since last week. so I have no idea what they went with.

@Dashrender Darn.

How did they end up with a limitation like that? That seems crazy.

I had to hack the bios in a Lenovo T410 to change the wifi card.

What versions of .NET Framework do you have?
Also, something to try if you haven't already: dxdiag
Where did you install the graphics drivers from?

When you installed them, did you do a clean install or just paste over the top?

@Dashrender said:

If they are all on the same controller, why does rebooting affect the others? Isn't the controller suppose to managing that?

The point of auto is to have the AP detect what channels are in use around it and pick the best one. That will obviously be different each time any AP reboots. When the first one reboots, it will immediately affect the ones next to it as the signal drops and the unit around it detect a difference. Then once it powers back on, it has to detect what is around it and then determine what channel to use.

High density deployments are much different beasts than an office building with 3 or 4 AP scattered around for coverage.

There you go, that should do it!

If you ever feel like you are caught up... then you should worry, lol.

@dafyre said:

Not yet... I still haven't even figured out what the default desktop is... (It feels like Gnome 3 to me).

Whta is the KDE Connect?

Here's what the notifications look like:

KDE Connect

@JaredBusch said:

@DustinB3403 said:

Jared on this Host we aren't running Hyper-V but Xenserver, but yes vDISK would be the VHD/VHDX (in hyper-v) or OVA (in Xen)

I know you're using sin but I was using the term that @Dashrender was familiar with

Thanks! 🙂

Outlook/OWA - maybe simply because I've used them for so long. Familiarity doesn't always breed contempt.

SuperMicro is beginning to make the lines between Tier 1 and Tier 2 blurry as they increase their level of engineering on their products and begin to offer more and more enterprise class support for their products.

Great!

@PSX_Defector said:

@scottalanmiller said:

They don't treat the "business" that you work for as seriously as American or European (or Nicaraguan in my case)

That's the first time anyone ever referred to Latin America as "serious" in business. The work ethic of Latin America, besides the lowest level of worker, is horrible. It was like pulling teeth to get things done in Costa Rica when I was running Vegas Club Room. And then we start mentioning South, especially Brazil, holy f[moderated]!

Costa Rica has a reputation for work issues even in Central America, I would not use that as the standard. I've not seem similar issues in Panama, for example. Nicaragua I am still getting to know.