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

Creating a Monitor Conference

Feature Description

See Monitor Conference.

Pre-requisites

You must have a DSP Chip configured for Monitor Conference.

Considerations

• Channels can be connected to the conference after call setup. It is not necessary to know at setup time all of the callers that will eventually connect to the conference.

• The call processing states of the source channels added to a monitor session are irrelevant. A source channel can be added to a monitor session with no effect on its current connection state. Subsequent state transitions of the channel have no effect on its association with the monitor conference.

• The source channels connected to a monitor conference do not have to be associated with one another in any way.

Procedure

1. Create the Conference

Use the Resource Create 0x0124 message to create the conference.

- Mandatory TLVs

0x0602 Resource Type: 0x0100 - Conference

0x0603 Channel/DSP Pool: Select desired option.

0x0606 Monitor Conference Enable: 0x0001 - Enable

- Optional TLS

Use optional TLVs to configure conference parameters.

See Conferencing Features TLVs

See Conferencing Options TLVs.

2. Add Conferees

Add Conferees using the Resource Connect 0x0127 message.

When adding the monitor channel, use the 0x0612 Connection Type TLV to indicate a one-way connection (0x01).

Multiple Sessions

To create multiple sessions, you can use the source ports on a DSP resource, in any combination.

For example, a DSP chip that is configured for the Monitor Conference function can provide the following:

• Three 9-port sessions and one 7-port session

• Six 5-port sessions and one 4-port session

• 17 two-port sessions

Deleting a Monitor Conference

You can delete a Monitor Conference by sending a Resource Delete 0x0126 message. Deletion can be either Forced or Graceful:

Forced Deletion

To release all channels in the conference and delete the conference using the Resource Delete 0x0126 message with the Forced Flag byte set to 0x01.

Graceful Deletion

To gracefully delete a Monitor Conference, release all monitor channels in the conference using the Release Channel message and then delete the conference using the Resource Delete 0x0126 message with the Forced Flag byte set to 0x00. All source channels are then automatically removed from the conference and the conference is gracefully deleted.

If you remove only the source channels from the Monitor Conference, the conference is not deleted. The conference retains its Conference ID and can be re-used.

Reconfiguring a Monitor Conference

To reconfigure an existing conference with new source channels, park the monitor channels using the Park Channel 0x00BF message. Removing the monitor channels from the conference (either by parking or releasing) automatically removes all of the source channels.

If a Resource Delete 0x0126 message that specifies graceful deletion has been sent, removing the monitor channels from the conference deletes the conference. When the source channels are removed, the monitor channels can then be reconnected to the conference, and new source channels connected using the same Conference ID number.

Digital Signal Processor
Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.
Message delimiter (SS7 bit pattern - 01111110)