Joining A Conference; Terminating A Conference - AudioCodes Mediant 1000 User Manual

SIP User's Manual
INVITE sip: conf100@audiocodes.com SIP/2.0
By default, a request to create a conference reserves three resources on the device. It is
possible to reserve a larger number of resources in advance by adding the number of
required participants to the User Part of the Request-URI. For example, '6conf100'
reserves six resources for the duration of the conference. If the device can allocate the
requested number of resources, it responds with a 200 OK.
The Conference Service Identifier can be set using the ini file (ConferenceID) or Web
interface (refer to ''Supplementary Services'' on page 176). By default, it is set to 'conf'.

10.1.1.3 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. Each conference
participant can use a different coder negotiated with the device using usual SIP
negotiation.
If more than the initially requested number of participants try to join the conference (i.e.,
four resources were reserved and a fifth INVITE is received) and the device has an
available resource, the request is granted.
If an INVITE to join an existing conference is received with a request to reserve a larger
number of participants than initially requested, it is granted if the device has available
resources. A request for a smaller number of participants is not granted as this may create
a situation where existing legs would need to be disconnected.
The maximal number of participants in a single conference is 60. The maximal number of
participants that actually participate in the mix at a given time is three (the loudest legs).
The Application Server can place a participant on Hold/Un-hold by sending the appropriate
SIP Re-INVITE on that participant dialog.

10.1.1.4 Terminating a Conference

The device never disconnects an existing conference leg. If a BYE is received on an
existing leg, it is disconnected, but the resource is still saved if the same leg (or a different
one) wants to re-join the conference. This logic occurs only for the initial number of
reserved legs.
For example:
1. INVITE reserves three legs.
2. A, B, and C join the conference.
3. A disconnects.
4. A joins (guaranteed).
5. D joins.
6. A disconnects.
7. A joins (not guaranteed).
Sending a BYE request to the device terminates the participant's SIP session and removes
it from the conference. The final BYE from the last participant ends the conference and
releases all conference resources.
Version 5.4 471
10. Media Server Capabilities
May 2008