...

The conferencing server also supports several codecs and is able to mix audio that arrives using different codecs from clients.

sipXecs & FreeSWITCH

The sipXecs & FreeSWITCH integration project is designed to create a plug & play distributed conferencing solution managed by the sipXecs Configuration Server. Ease of use has been one of the major design goals. In addition, FreeSWITCH has been fully integrated into the sipXecs build and installation process. FreeSWITCH installs like any other distributed component of the sipXecs solution. It is integrated into the sipXecs process management. Its configuration is auto-generated by sipXconfig.

...

The conference server and individual conferences are configured by selecting the Conferencing entry under the Features menu (see below). Several conferencing servers can be configured where each conferencing server can run on dedicated hardware. For each conferencing server the user interface shows how many conferences are currently active on that server.

Basic Settings

The basic bridge settings define information needed for sipXecs to communicate with the sipXecs-FreeSWITCH installation.

Image Removed

Advanced Settings

Select the "Show Advanced Settings" link to modify advanced conference bridge Navigate to Conference Server > Configuration tab to modify conference server settings. These settings are applied to all conferences on this bridgeconference server.

Image RemovedImage Added

...

Conference

...

Image Removed

Conference Settings

...

Settings

For adding a new conference navigate to Conference Server > Conferences tab and access Add new Conference link. Every conference has an extension number . For external accessibility this extension number could correspond with a DID prefixand can be assigned a DID Number (used for external accessibility). In addition every conference bridge entity has can have an owner and a participant access code.Image Removed

Image Added

If Auto-record is enabled for a conference bridge then the owner of that conference receives the recording of that conference call in a new "conference" mailbox. The conference bridge must have an owner or recording cannot be configured.
Conference call recording must be enabled before the call starts. The call is recorded from the time the first user joins the call until the time the last user leaves the call. Once the recording is complete the conference owner may log into their user portal and listen to the conference recording. They may also save the conference recording onto their desktop machine.

Note: Recorded conference calls do not light the user's MWI lamp since they are not messages for the user.

Dynamic Conference Controls

Image Added

Conference Chat Room

If Instant Messaging role is enabled every voice conference will have an associated chat room. The name of the chat room is the same as the name of the conference.

Image Added

Checking Status

Once configuration settings are applied, sipXconfig publishes this information to FreeSWITCH in about 1 minute. Select "Job Status" from the "Diagnostics" menu to view status:

Image Removed

You should see 4 completed operations (shown above).

File replication: conference_admission.xml

The admission dataset includes the conference declarations and PIN information. This is stored in /usr/local/freeswitch/conf/default_context.xml

File replication: conference_configuration.xml

The configuration dataset includes all of the DTMF sequences defined under the advance bridge settings and audio prompts (not yet configurable via sipXconfig) and is stored in /usr/local/freeswitch/conf/conference.conf.xml

Data replication: alias

Aliases are updated to include the conference extension to FreeSWITCH mapping.

Image Added

FreeSWITCH reload configuration

An XML-RPC call is made to FreeSWITCH, where FreeSWITCH is asked to reload the conference admission and configuration data.

Source, Build Instructions, and RPMs

Integration project page contains information on building sipXecs and locating RPMs.