Step 19. Conference
Server conference
Case: Alice, Boris, and Varvara agreed to hold a telephone meeting. Alice picks up the handset, dials the conference room number, and joins the discussion where Boris and Varvara are talking. She greets everyone, and they greet her back.
This is how a server conference is organized. Conferences on the server are divided into rooms with arbitrary numbers. The number plan has a subscriber feature code "conference", for example assigned the number *95. Routing rules assume dialing numbers matching the mask *95XXX. Thus, by dialing *95123, a subscriber enters conference room number 123. If several subscribers of the domain call the same number, they all end up in the same conference room, that is, they can hear each other. A specific room can serve up to 250 participants. Even if the number plan has several numbers for the "conference" subscriber feature code, for example *95 and #7, calls to *95123 and #7123 lead domain users to the same conference room.
A conference room always belongs to the domain in which the subscriber feature code is configured and is served on one of the sites where that domain is served. A conference can also be joined from another domain if cross-domain calls are configured accordingly. A conference room is created by the call of the first participant. The site serving it becomes the site conventionally closest to the first participant. A second call to the same conference room finds it on the site where it was created. The conference is destroyed automatically when the last participant leaves. The conference has a lifetime limit of 2 hours, the same as all calls.
Such conferences are served by conference servers, the CONF role. It is made redundant and scaled in Active-Active mode. This role is a SIP-UA, that is, a user agent toward the call (B2B dialog). Communication of several subscribers with a conference room effectively implies the same number of independent calls (B2B dialogs). On a general basis, a conference can be transferred to a number or to another subscriber with replacement, and conversely, any subscriber can be transferred to a conference (also by number or with replacement).
A server conference has its own media context on one of the nearby media gateways. Generally, each call is served by a media gateway, and the conference itself is served by a media gateway. The media gateway serving the conference context is responsible for mixing audio traffic for each conference participant so that they hear everyone except themselves.
Three-party conference on the phone
Case: Alice is talking to Boris; Boris puts Alice on hold and makes a consultation call to Varvara. They decide to discuss the matter as a group. Boris presses CONF on the phone, and all three begin to hear each other.
Most telephone devices support this method of organizing a conference. Its peculiarity is that, from the server’s point of view, these are two independent calls; audio mixing is performed by the subscriber device on which the CONF button was pressed. The call log also shows two independent calls, but in the call recording, each of them contains the speech of all three subscribers in both channels.
| Term | Definition |
|---|---|
|
! |
|
! |
|
! |
|
! |
|
! |
|
! |
-
Next step: Step 20. IVR (Interactive Voice Response)
-
Previous step: Step 18. BLF (Busy Lamp Field)