there is a command available that specifies the order in which multiple dialer strings are used:
Basically, there are three options: sequential, round-robin, and last-successful.
Sequential - Always starts dialing the first dial string configured in a list of multiple strings, and continues to the next dial string when a call fails. This keyword allows dial string order to be prioritized, and is the default
round-robin - Always starts dialing using the dial string that follows the most recently used dial string. If no calls have previously been made, the dialer uses the first dial string. When a call fails, the dialer tries the next dial string until all dial strings have been tried. This keyword allows calls to be shared equally among the configured dial strings. However, if the dial strings are associated with multiple ISDN B channels on the same remote device, a call may be placed to bring up a second B channel without trying to call the number associated with the first B channel
last-successful - Always starts dialing using the most recently successful dial string, and continues to the next dial string in a list when a call fails. This keyword reduces the time needed to find a dial string that successfully completes a call when the dial strings are not likely to be equally successful
yes im using a single bri port, can you please show me an example config, including the backup number, route etc ?, i thought the load threshold was to bring up another line incase the other one is at a certain load of traffic ?
As mentioned by GP in his post your best bet would be round robin option which you can pick up and configure under your dialer interface.
do check few config samples which shows on how to add up a secondary dialer string as well as a brief config sample taken from cco.
dialer string 12345678
dialer string 12345679
dialer order round-robin
ip address 10.1.1.130 255.255.255.0
dialer pool 1
dialer string 1904
dialer string 1905
dialer string 1906
dialer string 1907
dialer order round-robin
As you have mentioned dialer load threshold option is to bring the second channel up when you want to make use of the other idle channel (based on your requirement) during load conditions which can add upto 128K(64+64).
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...