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.
And we are expecting users to change these allocations... > 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. How do we handle servers that do not contain a proxy? I am thinking that it might be easier to put the allocation service in the config server and have it operate at config time, not run time. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
