On Thu, 2008-10-09 at 12:01 -0400, M. Ranganathan wrote: > Hello, > > Continuing from this morning's discussion on #sipx > > 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. > > Proposed solution: > - We will introduce a range check / port range allocation service. > There will be one per sipx proxy server and it will be co located with > the proxy server. Before a port or port range is allocated, the port > range service is consulted. The port allocation service will > bind/unbind to that range of ports. If the port has been allocated or > if there is a clash with an existing allocation, an error is returned. > If there is no error, then the specified range of ports is allocated > and recorded. The port allocation service will also be able to return > an "ephemeral port" for services that need such ports.
I think this is over-engineering. sipXconfig could just as easily keep a table of all ports for all services on all hosts and check for overlaps. Doing a dynamic test is not only cumbersome, but it only tells you whether or not the port was in use at the instant you tried it - not 1 second after the test releases it again. The kernel won't let two services open the same port, and I think this is the only interlock we should use (other than perhaps a static check in sipXconfig). Failure to open a configured port would be an excellent candidate for an alarm, which will quickly bring the configuration problem to the attention of the administrator. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
