We can't control in what order the incoming calls will come in, but assuming you leave the PRI circuits plugged in the way they are now, where port 0 is first, then 1, 2, 3, then the incoming order should already be working as you described. Usually the PSTN side will start at the lowest channel and work their way up.
For the outbound calls, I believe the router (when in USER mode on the PRI) will start at the highest channel and work its way down... on each PRI. If you want the outbound calls to start on PRI 3, then 2, 1, 0, then configure the POTS dial-peers for outbound calls to the PSTN to be in that order.
If you need to change the ascending/descending order used by the router for bearer channel selection on outbound calls, you can use the isdn bchan-number-order command on the ISDN interface -- e.g. Serial0:23
I would like to know how to configure the pots dial-peers to contemplate more than one PRI.
Somewhere in the configuration of the dial-peers, we use "port 0:D" for the AS5300 to deliver the call to the first PRI. If we have more than one PRI, how can I "tell" the dial-peer to use the other PRI (like port 1:D) also?
The most common way to do this has been to configure multiple dial-peers with the same destination pattern. A quick example of this:
dial-peer voice 1 pots
dial-peer voice 2 pots
However in 12.1(3)T releases and later, there is the capability to define a trunk group, but as far as I know this is typically used when the router is acting as the ISDN network side as opposed to the user side, and is used with the cor feature as well. The first method I mentioned should work fine for you; if you want more info on the other features you can check out:
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...