Conference Service Configuration
From SIPfoundry sipXecs IP PBX, The Open Source SIP PBX for Linux - Calivia
| Important note: The Conference Server has been removed from the 3.1/3.2 release and deferred to a later release. The functionality described here is still available in ConfigServer but has been temporarily disabled until we are able to pick this project back up. If someone is interested to work on this, please say so on the sipx-dev list. |
Contents |
Introduction
The "Boston Bridge" project is a failry new effort that started as a joint coding party between the reSIProcate and sipX teams after Fall VON 2005 in Boston. The project's objective is to build a high quality and fully managed SIP conference bridge that can either be used as a standalone application or integrated into the sipX IP PBX.
The Boston Bridge solution is plug & play managed by the sipX Configuration Server. The current developers revision 3.1 includes a first version of the conference server management portal. Alternatively, the Boston Bridge applicaiton can be managed using configuration files:
Architecturaly we went a new path: The Boston Bridge, for the first time, is built using a combination of the reSIProcate SIP stack, the reSIProcate DUM layer, the sipXtapi media framework, as well as the sipX Configuration Server.
Configuration of the Conference Server
The conference server is an independent application that can run on the same server as the rest of the sipx system or on separate HW. The conference server communicates using the SIP protocol. It is configured through the sipX Configuration Server that remotely configures the conference server using the XML RPC protocol. In the context of the High Availability (HA) architecture of sipX release 3.2, all the different components will communicate with the sipX Configuration Server over XML RPC so that Configuration Server can be remote and run on different HW. Please refer to the High Availability Architecture Specification.
The following allows the configuration of the configuration server:
Setup of Individual Conference Bridge Entities
Once the Conference Server is setup and configured, individual bridge entities can be created. Dependent on your needs and policy you can create as many bridge entities as you want. It is possible to create an individual bridge entity per user of the sipX system, or a certain number of shared bridge entities can be setup. Every bridge entity has an extension number. For external accessibility this extension number could correspond with a DID prefix. In addition every conference bridge entity has an organizer access code and a participant access code.
Source Code
Source code access is through the sipX Subversion repository as usual. The conference server is not yet included in the nighly builds of the development release 3.1, but you could expect it to show up within the next few weeks. The Configuration Server management portal is included and ready to use as soon as the conference bridge server is ready to go.
