You are here: CSP Developer’s Guide: Overview > 7 Configuring and Using Resources on the DSP Series 2 Cards > Creating a Child Conference

Creating a Child Conference

Feature Description

See Child Conference.

Dependencies and Considerations

• If a party is removed from the parent conference, it will also be removed from the child conference if it is part of any.

• A party can be in only one child conference at a time.

• Only parties that are connected 2-way in a parent conference can be moved into a child conference.

• A child conference inherits its conferencing features configuration from the parent conference at the time of its creation. You can modify the Conferencing Features configuration of the Child Conference with the Resource Modify 0x0125 message.

• The volume of parent conference getting recorded to a child conference is designed to be low. Playing the parent conference at a quieter volume allows monitoring of the main thread of conversation without it overwhelming the child conference.

Pre-requisites

You must already have a conference created (Parent Conference) from which to create the Child Conference.

Procedure

1. Create Child Conference

Use the Resource Create 0x0124 message to create the Child Conference.

- AIB:

Use the Child Conference AIB. In the AIB you indicate the Parent conference ID. The response to the Resource Create 0x0124 message will indicate the new Child Conference ID, which you then use when adding conferees to the Child Conference using the Resource Connect 0x0127 message.

- Mandatory TLV

0x0602 Resource Type: Child Conference (0x0107)

- Optional TLVs

Use optional TLVs to override default conference parameters if necessary.

See Conferencing Features TLVs

See Conferencing Options TLVs.

2. Add Conferees

Use the Resource Connect 0x0127 message to add conferees to a child conference.

Removing Party from the Child Conference

Use the Resource Disconnect 0x0128 message to move a channel from a child conference back into the parent conference. The Resource Disconnect message uses the Channel AIB (0x0D) and the Child Conference ID AIB (0x45).

Deleting a Child Conference

Use the Resource Delete 0x0126 message (0x0126) to delete a Child Conference. The Resource Delete message uses the Child Conference ID AIB (0x45) to address the child conference to be deleted.

The Resource Delete Indication message (0x0129) indicates that the Child Conference has been deleted.

• When a child conference is deleted forcibly, the channels connected to it are connected back to the parent conference and the child conference is immediately deleted.

• When a child conference is deleted gracefully, the CSP waits until all the parties connected to the child conference are either removed or reconnected back to the parent conference before deleting the child conference. The default behavior is graceful deletion.

• When a parent conference is deleted forcibly, all parties connected to the parent and the associated child conferences are removed, and the parent and all its child conferences are immediately deleted.

• When a parent conference is deleted gracefully, the CSP waits until all parties in the parent and the associated child conferences are removed. When all parties connected to a child conference have been removed or reconnected back to the parent conference, the child conference is deleted. When all the child conferences have been deleted and no parties are left in the parent conference, the parent conference is deleted.

See Address Information Block.
Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.