Terminating A Conference; Conference Call Flow Example - AudioCodes Mediant 1000 User Manual

Event notifications are sent in SIP INFO messages, as shown in the example below of XML
Response Generated for ASN:
<?xml version="1.0" encoding="utf-8"?>
<MediaServerControl version="1.0">
<notification>
<conference uniqueID="3331" numtalkers="1">
<activetalkers>
<talker callID="9814266171512000193619@10.8.27.118"/>
</activetalkers>
</conference>
</notification>
</MediaServerControl>

10.1.2.6 Terminating a Conference

To remove a leg from a conference, the Application Server issues a SIP BYE request on
the selected dialog representing the conference leg. The Application Server can terminate
all legs in a conference by issuing a SIP BYE request on the Control Leg. If one or more
participants are still in the conference when the gateway receives a SIP BYE request on
the Control Leg, the gateway issues SIP BYE requests on all of the remaining conference
legs to ensure a clean up of the legs.
Figure 10-5: Terminating a Conference -- SIP Call Flow

10.1.3 Conference Call Flow Example

The call flow, shown in the following figure, describes SIP messages exchanged between
the Mediant 1000 (10.8.58.4) and three conference participants (10.8.29.1, 10.8.58.6 and
10.8.58.8).
SIP User's Manual 456
Mediant 1000
Document #: LTRT-83302