Any question like this would technically be dependent on the PBX in question and could not be answered generically. That being said, I do not know of any system where this would cause a problem.

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.

@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