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. Parts of this service have already been written and incorporated into sipxrelay. I propose we generalize this and export it to any sipx service ( in particular sipxconfig ) that wants to use it. The required functions will be exported using xml rpc. If there is agreement that this is a good idea, I can open a JIRA issue for it and can undertake to make the necessary extensions to sipxrelay to support it. Additional functionality that can be incorporated into this service: This service can be used for determination of public address of the box using STUN as this is also another piece of information that various services need. Thank you in advance for any comments. 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
