When using TeleFlow LineList for the line config, you can replicate the lines, so it doesn't take a great deal of effort to set up. (You don't have to set up each line individually, one at a time.)
What I described - configuring what apps to run on what ports before starting the server - is how TeleFlow works, so there isn't any way to dynamically instatiate ports. There really shouldn't be any other applications besides TeleFlow that would need access to the ports, and we would highly recommend against any form of port-sharing between TeleFlow and another telephony application.
If you want to have different TeleFlow applications run on the same ports, there are ways of handling that. With the Run TAP step, one TeleFlow Application can run another TeleFlow Application anytime. You could have one "high level" application, for example, that determines whether or not to call someone, which then calls, and when a caller answers, uses Run TAP to run the application that handles the call. (an application does not necessarily have to handle the task of getting a caller on the phone itself. It could assume that if it is run that a caller is already on the line. Alternatively, you can use a compare of the @HOOK_STATUS variable, which will be OFF-HOOK if there is a caller on the line, or ON-HOOK if not. This means your applications can be designed such that they can run either as standalone applications that handle the phone answering/calling out, or as applications that run after the caller is on the line. This is up to how you intend to use them. If you look at the template application "Inbound", you will see that is was designed such that it can be run as either a standalone application, or that it can be run by another TAP that has already handled answering the phone.)
Similarly, on an inbound application, you can have one application that answers all the calls, evaluates a given call's DNIS, and then uses Run TAP to run the application that provides the appropriate service to the caller based on the number they called.
|