Sorry, I don't know if it's possible to configure a max-conn number that is cumulative for a set of dial-peers.
However, I would like, for the sake of curiosity, try to understand why not having this would be a problem.
First, it would seem at first that you can do with a single dial-peer, unless the destination-pattern is very complex (that is, you need a "more specific" routing toward other dial-peers).
Then, even if the above multiple dial-peers are necessary, if the provider only allow a single call at once, subsequent calls will fail anyway, only will fail at the provider instead than locally on the router.
All in all, this should not be a problem.
Just guessing, thank you if you can let us know more about this case.
There are a couple of reasons I'd like to keep seperate dial peers. One is for class of restrictions and the other is so that I can put a preference on each dial peer.
With the perferences it allows me to have two dial peers to the same destination - one via PSTN and one via the VoIP Provider. This means that I can selectively choose to send calls via VoIP or PSTN on a per destination basis.
The reason for the max-conn is that once the voip channel has been used, all subsequent calls should then be routed via PSTN. The problem I think (and I haven't tried this) is that once the first call goes through, subsequent calls will fail, rather than being routed via the next preference dial peer.
I need to test this out. However a max-conn type command in the SIP-UA configuration section would be ideal.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.