Three-Way Conferencing Parameters

'Enable 3-Way Conference'

configure voip > gateway dtmf-supp-service supp-service-settings > enable-3w-conf

[Enable3WayConference]

Enables the 3-Way Conference feature.

■

[0] Disable (default)

■

[1] Enable

Note: For the parameter to take effect, a device restart is required.

'3-Way Conference Mode'

configure voip > gateway dtmf-supp-service supp-service-settings > 3w-conf-mode

[3WayConferenceMode]

Defines the mode of operation for three-way conferencing.

■

[0] AudioCodes Media Server = (Default) The conference-initiating INVITE sent by the device, uses the ConferenceID concatenated with a unique identifier as the Request-URI. This same Request-URI is set as the Refer-To header value in the REFER messages that are sent to the two remote parties. This conference mode is used when operating with AudioCodes IPMedia conferencing server.

■

[1] Non-AudioCodes Media Server = The conference-initiating INVITE sent by the device, uses only the ConferenceID as the Request-URI. The Conference server sets the Contact header of the 200 OK response to the actual unique identifier (Conference URI) to be used by the participants. This Conference URI is then included by the device in the Refer-To header value in the REFER messages sent by the device to the remote parties. The remote parties join the conference by sending INVITE messages to the conference using this conference URI.

■

[2] On Board = On-board, three-way conference. The conference is established on the device without the need of an external Conference server. You can limit the number of simultaneous, on-board 3-way conference calls, by using the [MaxInBoardConferenceCalls] parameter. The device utilizes resources from idle ports to establish the conference call. You can designate ports that you do not want to use as resources for on-board, conference calls initiated by other ports. This is configured using the [3WayConfNoneAllocateablePorts] parameter.

■

[3] Huawei Media Server = The conference is managed by an external, third-party Conferencing server. The conference-initiating INVITE sent by the device, uses only the ConferenceID as the Request-URI. The Conferencing server sets the Contact header of the 200 OK response to the actual unique identifier (Conference URI) to be used by the participants. The Conference URI is included in the URI of the REFER with a Replaces header sent by the device to the Conferencing server. The Conferencing server then sends an INVITE with a Replaces header to the remote participants.

Note:

■

The parameter is applicable only to FXS interfaces.

■

When using an external Conferencing server, a conference call with up to six participants can be established.

'Max. 3-Way Conference'

configure voip > gateway dtmf-supp-service supp-service-settings > mx-3w-conf-onboard

[MaxInBoardConferenceCalls]

Defines the maximum number of simultaneous, on-board three-way conference calls.

The valid range is 0 to 24 (6 per FXS blade). The default is 2.

Note:

■

For enabling on-board, three-way conferencing, use the [3WayConferenceMode] parameter.

■

For more information on on-board three-way conferencing, see Three-Way Conferencing.

■

The parameter is applicable only to FXS interfaces.

'Non Allocatable Ports'

[3WayConfNoneAllocateablePort s]

Defines the ports that are not allocated as resources for on-board three-way conference calls that are initiated by other ports. Ports that are not configured with this parameter (and that are idle) are used by the device as a resources for establishing these type of conference calls if there are no DSP resources available.

The valid range is up to 8 ports. To add multiple ports, use the comma separator. For example, for not allowing the use of ports 2, 4 and 6 as resources, configure the parameter to "2,4,6" (without quotation marks). The order of the entered values is not relevant (i.e., the example above can be entered as 6,2,4). The default is 0.

Notes:

■

To enable on-board, three-way conferencing, use the 3WayConferenceMode and MaxInBoardConferenceCalls parameters.

■

This parameter is applicable only to FXS interfaces.

'Establish Conference Code'

configure voip > gateway dtmf-supp-service supp-service-settings > estb-conf-code

[ConferenceCode]

Defines the DTMF digit pattern, which upon detection generates the conference call when three-way conferencing is enabled (Enable3WayConference is set to 1).

The valid range is a 25-character string. The default is “!” (Hook-Flash).

Note: If the FlashKeysSequenceStyle parameter is set to 1 or 2, the setting of the ConferenceCode parameter is overridden.

'Conference ID'

configure voip > gateway dtmf-supp-service supp-service-settings > conf-id

[ConferenceID]

Defines the Conference Identification string.

The valid value is a string of up to 16 characters. The default is "conf".

The device uses this identifier in the Conference-initiating INVITE that is sent to the media server when the Enable3WayConference parameter is set to 1.

'Use Different RTP port After Hold'

configure voip > sip-definition settings > dfrnt-port-after-hold

[UseDifferentRTPportAfterHold]

Enables the use of different RTP ports for the two calls involved in a three-way conference call made by the FXS endpoint in the initial outgoing INVITE requests.

■

[0] Disable = (Default) The FXS endpoint makes the first and second calls on the same RTP port in the initial outgoing INVITE request. If a three-way conference is then made, the device sends a re-INVITE to the held call to retrieve it and to change the RTP port to a different port number.

For example: A first calls B on port 6000 and places B on hold. A then calls C, also on port 6000. The device sends a re-INVITE to the held call to retrieve it and changes the port to 6010.

■

[1] Enable = The FXS endpoint makes the first and second calls on different RTP ports in the initial outgoing INVITE request. If a three-way conference is then made, the device sends a re-INVITE to the held call to retrieve it, without changing the port of the held call.

For example: A first calls B on port 6000 and places B on hold. A then calls C on port 6010. The device sends a re-INVITE to the held call to retrieve it (without changing the port, i.e., remains 6010).

Note:

■

When this feature is enabled and only one RTP port is available, only one call can be made by the FXS endpoint, as there is no free RTP port for a second call.

■

When this feature is enabled and you are using the Call Forking feature, every forked call is sent with a different RTP port. As the device can fork a call to up to 10 destinations, the device requires at least 10 free RTP ports.

■

The parameter is applicable only to FXS interfaces.