On Thu, Oct 9, 2008 at 2:02 PM, Dale Worley <[EMAIL PROTECTED]> wrote: > On Thu, 2008-10-09 at 12:01 -0400, M. Ranganathan wrote: >> Problem: >> Currently there are no checks on port allocation and there is no >> allocation service that works across all the different services that >> need to use ports on a given sipx. It is easily possible to allocate >> conflicting port ranges in generating configuration files. > > I thought that we used a static configuration strategy. There should be > a doc file that lists all the allocations. That is, I think that you've > been running into a problem in practice that I haven't heard about. > > Dale > > >
There are various port ranges that can be dynamically configured at the moment. For example, consider the port range for NAT traversal. There are also ports for SBCs, etc. I am trying to address these dynamic ports that can be wrongly configured. Of course the service will refuse to start and the admin will go examine the logs but why not discover the problem before that. Thanks for commenting Ranga -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
