The most basic communications type simply invites the user to an instant message conversation. So even if there are only two participants remaining in the conference call and audio is the only modality left in use the call remains hosted on the MCU. Regardless of how many other participants or modalities are added to the call removing all of these will never trigger any sort of de-escalation back to a P2P session. From this point on the addition of any more participants or MCU-only modalities are seamless as the session has already been moved to the MCU.
This escalation can happen only once per session and is permanent. The act of enabling the Whiteboard modality will automatically escalate the audio call to a conference call and at this time the P2P media payload session will be stopped and both Lync clients will then negotiate media paths directly to the MCU on the Lync Front End server.
Then one of Lync users decides to add whiteboarding to the session, which requires the MCU as it is not a modality that is supported directly between the Lync clients. Escalationįor example say that a basic audio call has been established between two Lync clients which utilizes the P2P model by default. Modalities which only support the MCU model will trigger an immediate escalation from an existing P2P session up to an MCU session when selected. For the purposes of simplicity media traversal through and Edge Server is not included here but regardless of the model the Edge server may be involved in transparently proxying one or both of the two data streams.Īs noted some only support a single model while other can work in either model depending on the type of session currently in use when the specific modality is added. The following table can be used to quickly reference which types of modalities support which of the two communications models. Using these constants the various ways that sessions can be initiated and how the different modalities are utilized can all be defined to understand exactly what is sending network data to where, and what actions trigger changes in these paths. While most modalities can leverage either model depending on the type of call in session, some of them only support a single model and will always communicate in that fashion. Again the primary signaling path is always handled by the Lync Server as previously defined, but the payload can take different routes depending the scenario.
Lync clients do not and cannot send signaling messages directly to each other. For signaling data Lync clients will always be connected to a Lync Server and this traffic will always go from client to server to client.All communication data can be categorized as either Signaling data where the session setup and handling is performed, or as Payload which would be be the actual content itself (e.g.In Lync, and going all the way back to Office Communications Server, there are a few constants that can be defined. The path that each takes depends primarily on the type of communication involved and is also influenced by the number of parties involved. These various options can utilize a few different network paths to reach the intended destination(s). There are multiple ways to initiate communications sessions in Lync across different modalities and features.
0 kommentar(er)
