SIP User's Manual 416 Document #: LTRT-83310
Mediant 600 & Mediant 1000
20.1.1.2.2 Joining a Conference
To join an existing conference, the Application Server sends a SIP INVITE message with
the same Request-URI as the one that created the conference. The INVITE message may
include a <configure_leg> MSCML request body. If not included, defaults are used for that
leg attributes.
The <configure_leg> can include the following attributes:
Id: identification number of the MSCML request. This is used to correlate between
MSCML requests and responses.
Type: Talker / Listener. If set to Listener, the incoming RTP from that leg does not
participate in the conference mix. The default is Talker.
Mixmode:
• Full: RTP from this leg participates in the mix (default).
• Mute: RTP from this leg is not participating in the mix.
• Private: RTP from this leg can only hear participants within a conference team
(<teammate> ) to which it belongs (see below).
The <configure_team> element enables clients to create personalized mixes for scenarios
where the standard mixmode settings do not provide sufficient control. The
<configure_team> element is a child of <configure_leg>. The <configure_team> element,
containing one or more <teammate> elements, specifies those participants that should be
present in this participant’s personalized mix. The <configure_team> element supports
several commands: set, add, remove, and query.
The participants are identified in the <teammate> elements by their IDs that are assigned
in their <configure_leg> element. The team configuration is implicitly symmetric, i.e. if
participant A defines participant B as its team member, implicitly participant B defines
participant A as its team member.
A “coaching” example:
To Next Page
Loading...
