Modifying A Conference; Applying Media Services On A Conference - AudioCodes Mediant 1000 User Manual

10.1.2.3 Modifying a Conference

To modify an existing conference, INFO messages are used. Each INFO message carries
an MSCML request. The MSCML response is included in an INFO message back from the
gateway to the Application Server. It is possible to modify an entire conference (by issuing
requests on the Control Leg) or only a certain participant (by issuing requests on that
specific leg).
To modify the entire conference, a <configure_conference> MSCML request body is sent
in an INFO message on the Control Leg SIP dialog. Using this request, the Application
Server can modify the following attributes:
Reservedtalkers: If the Application Server sets a number that is lower than the initial
number requested in the INVITE, then the request is not granted. If the number is
higher than the initial number, the gateway sends a success response in the response
INFO.
Reserveconfmedia: If the necessary resources for applying Media Services on the
entire conference were reserved in advance, then by setting reserveconfmedia to Yes,
it is reserved. If set to No, the gateway can free the resource.
To modify a certain Participant Leg, a <configure_leg> MSCML request body is sent in an
INFO message on that leg SIP dialog. Using this request, the Application Server can
modify any of the attributes defined for the <configure_leg> request.

10.1.2.4 Applying Media Services on a Conference

The Application Server can issue a Media Service request (<play>, <playcollect>, or
<playrecord>) on either the Control Leg or a specific Participant Leg. For a Participant Leg,
all three requests are applicable. For the Control Leg, the <playcollect> is not applicable as
there is no way to collect digits from the whole conference.
SIP User's Manual
Figure 10-3: Modifying a Conference - SIP Call Flow
454
Mediant 1000
Document #: LTRT-83302