From an existing telephone connection with two subscribers a conference is often to be established. The transfer conference does not realize such a conference device-controlled but via the conference portal of Telephony Application Server.
The transfer conference is available in the Media Server only if the Media Server is used under Telephony Application Server.
The following figures show how the transfer conference works.
The transfer conference mechanism starts with a simple telephone connection and two subscribers who are connected via Telephony Control Server. The SIP signaling of the phone connection is led via Telephony Control Server. The RTP-based payload is directly exchanged between the telephones.
In the depicted example, one of the two subscribers is an Lotus Sametime Unified Telephony user A who can control his/her telephone via a software client. The software client communicates via its CTI controller and the CSTA protocol with the BCom provider of the Lotus Sametime Unified Telephony server. The BCom provider also communicates via CSTA with Telephony Control Server and controls in particular the telephone of user A.
The second subscriber to the phone connection is e.g. an external subscriber.
Based on the existing phone connection and via the GUI of his/her software client user A can initiate an ad-hoc conference to integrate a new subscriber in the existing connection. The following happens:
- The BCom provider of the Lotus Sametime Unified Telephony server cuts the connection between the subscribers A and B in Lotus Sametime Unified Telephony and connects the two resulting connection fragments to a new transfer conference in the conference portal. To this, the BCom provider controls Lotus Sametime Unified Telephony via appropriate CTI commands.
- At the same time the BCom provider of the Lotus Sametime Unified Telephony server transfers all information about the rerouted connections and their subscribers to the CTI provider of the Media Server. The CTI provider then forwards the information to the conference portal. In this way the conference portal can determine which of the newly arriving calls are to be routed into a common transfer conference. Furthermore, the conference portal is thus enabled to suppress default greetings of the portal for the relevant users.
- Besides the subscribers A and B, also the new conference participant is added to the transfer conference.
Eventually, all users are in a common transfer conference of the conference portal. In this scenario the SIP signaling of the phone connection leads via Lotus Sametime Unified Telephony to the conference portal. The RTP-based payload is processed by a conference mixing unit of the Media Server.
After the users have been connected in the transfer conference of the conference portal, this conference can be controlled as usual via the Virtual Conference Controller (VC-Controller) of the software client.
The available information about the state of the different connections differ in the system components involved.
In Telephony Control Server the participating connections are registered as CONNECTED. In Telephony Control Server such connections are not known as conference connections.Parent topic: Media Services
In the CTI controller of the software client the connections are registered as CONFERENCED. The CTI controller receives the additional information about the conference state from the BCom provider of the Lotus Sametime Unified Telephony server, which has received it from the CTI provider of the Media Server.
In the Virtual Conference Controller of the software client all users are registered as subscribers to a common conference. The Virtual Conference Controller receives this comprehensive information directly from the Media Server conference portal.