與商務用 Skype 共存Coexistence with Skype for Business

商務用 Skype 與團隊用戶端與使用者之間的共存與互通性是由 TeamsUpgrade 模式所定義,且 與商務用 Skype 搭配使用團隊之組織的遷移和互通性指南中所述。Coexistence and interoperability between Skype for Business and Teams clients and users is defined by TeamsUpgrade modes, described in Migration and interoperability guidance for organizations using Teams together with Skype for Business.

任何指定的使用者,都會依預設或由系統管理員明確指派 TeamsUpgrade 模式。Any given user will always be assigned a TeamsUpgrade mode, either by default or explicitly by the administrator. 預設值為 [ 孤島]。The default value is Islands. 已升級至團隊的使用者具有 TeamsOnly模式。Users upgraded to Teams have the mode of TeamsOnly. SfBOnlySfBWithTeamsCollabSfBWithTeamsCollabAndMeetings 也是可能的模式。SfBOnly, SfBWithTeamsCollab, and SfBWithTeamsCollabAndMeetings are also possible modes.

路由參數Routing parameters

收件者的 TeamsUpgrade 模式是在租使用者內和同盟租使用者之間,決定聊天、通話和目前狀態的行為的關鍵。The TeamsUpgrade mode of the recipient is key in determining the behavior of chats, calls, and presence, both within a tenant and across federated tenants.

如果寄件者是使用小組,則在建立新的交談線索時會進行路由決定。If the sender is using Teams, the routing decision is made when creating a new conversation thread. 團隊中的現有交談執行緒總是保留在建立執行緒時所決定的路由方法:團隊支援持久性執行緒。Existing conversation threads in Teams always retain the routing method determined when the thread was created: Teams supports persistent threads.

執行緒路由方法包括:Thread routing methods are:

  • 團隊在租使用者中的原生小組交談native for a Teams to Teams conversation in-tenant
  • 團隊在租使用者中進行商務用 Skype 交談的交互操作interop for a Teams to Skype for business conversation in-tenant
  • 針對租使用者進行聯盟交談 的同盟federated for a federated conversation across tenants

決定執行緒路由方法的參數如下:The parameters that determine the thread routing method are:

  • 收件者的 TeamsUpgrade 模式The TeamsUpgrade mode of the recipient
  • 寄件者所用的用戶端The client used by the sender
  • 交談為新的或現有的執行緒的一部分Whether the conversation is new, or part of an existing thread
  • 交談是否為租使用者或同盟Whether the conversation is in-tenant or federated
  • 是否可以進行交談Whether the conversation is possible
    • 在租 使用者互通性要求租使用者是純線上或商務用 Skype 混合式。In-tenant interoperability requires that the tenant is either pure online or Skype for Business hybrid. 純粹內部部署承租人不能有租使用者互通性。Purely on-premises tenants can't have in-tenant interoperability.
    • 跨租使用者同盟 總是需要正確的商務用 Skype 同盟設定,以及來自兩個承租人的正確團隊同盟設定。Cross-tenant federation always requires proper Skype for Business federation configuration as well as proper Teams federation configuration from both tenants. 任何一個租使用者都不需要商務用 Skype 混合式。Skype for Business hybrid isn't required of either tenant.
    • 如果始發者的商務用 Skype 帳戶是駐留在內部部署的,該使用者就無法使用 [團隊用戶端] 來進行租使用者互通性或同盟。If the Skype for Business account of the originator is homed on-premises, that user can't use the Teams client for in-tenant interoperability or for federation. 該使用者只能使用商務用 Skype 用戶端進行互通性與同盟。That user can only use the Skype for Business client for interoperability and federation.
    • 團隊若要在租使用者中進行團隊溝通,請務必這樣做。Teams to Teams communication is always possible in-tenant.

注意

如果收件者和寄件者都在 TeamsOnly 升級模式中,則交談將是一個固有的聊天體驗,包括所有豐富的訊息和呼叫功能。If the receiver and sender are both in TeamsOnly upgrade mode, the conversation will be a native chat experience which includes all the rich messaging and calling capabilities. 若要深入瞭解,請閱讀 團隊中的外部 (聯盟) 使用者的原生聊天體驗To learn more, read Native chat experience for external (federated) users in Teams. 如果其中一個交談參與者不在 TeamsOnly 升級模式中,則交談仍會有純文字訊息的交互操作體驗。If either of the conversation participants is NOT in TeamsOnly upgrade mode, the conversation remains an interop experience with text-only messages.

聊天和通話路由Chat and call routing

新聊天或通話的租使用者內路由In-tenant routing for new chats or calls

下表會捕獲受租使用者的聊天和通話的路由,而且對於不是從預先存在的執行緒開始的新通話或聊天而言,都是有效的。The tables below capture routing of in-tenant chat and calls, and are valid for new calls or chats that are not started from a pre-existing thread. 它描述哪個用戶端會收到新的通話或聊天(如果左側的使用者產生)至右側的租使用者收件者。It describes which client will receive a new call or chat, if originated by a user on the left, to an in-tenant recipient user on the right.

傳送給 TeamsOnly 使用者的郵件將永遠會傳送給團隊。Messages sent to TeamsOnly users will always route to Teams. 傳送給 SfB * 使用者的郵件將會一直路由到商務用 Skype (如果有的話),如上述所述。Messages sent to SfB* users will always route to Skype for Business, if the conversation is possible as described above. 傳送給孤島使用者的訊息,永遠會傳送到傳送給他們的同一個用戶端。Messages sent to Islands users will always route to the same client from which they were sent.

下表顯示在指定模式中,哪個用戶端會收到來自發信方 (三個最左邊的欄) ,視始發者的模式、用戶端,以及其商務用 Skype 用戶端 (在內部部署或線上) 所駐留的位置。The tables below show which client in a given mode will receive a call from the originator (three leftmost columns), depending on the originator's mode, client chosen, and where their Skype for Business client is homed (on-prem or online).

在下列資料表中:In the tables that follow:

  • **SfB * *_ 代表下列任何一種模式: SfBOnly *、 SfBWithTeamsCollabSfBWithTeamsCollabAndMeetings*SfB* represents any of the following modes: _SfBOnly*, SfBWithTeamsCollab, SfBWithTeamsCollabAndMeetings.

  • 斜體文字 會醒目提示交互操作交談。Italic text highlights an interop conversation.

  • 無法 代表無法進行聊天或通話的情況。Not Possible represents a situation in which the chat or call is not possible. 發信方必須使用商務用 Skype,而不是在這些情況下。The originator must use Skype for Business instead in these cases. 這是 Microsoft 對內部部署/混合式客戶的說明性指導方針的其中一個原因,就是使用孤島以外的模式 (通常是 SfBWithTeamsCollab) 做為團隊升級歷程的起點。This is one of the reasons why Microsoft's prescriptive guidance to on-prem/hybrid customers is to use a mode other than Islands (typically SfBWithTeamsCollab) as the starting point of their upgrade journey to Teams.

資料表1a:租使用者新聊天或呼叫路由至孤島模式收件者Table 1a: in-tenant new chat or call routing to an islands mode recipient



Mode
觸發器Originator

用戶端Client


SfB   宿主SfB homed


Route-->Route-->
Recipient

離島Islands
離島Islands TeamsTeams
商務用 SkypeSkype for Business
TeamsTeams
商務用 SkypeSkype for Business
OnlineOnline
OnlineOnline
內部部署On-prem
內部部署On-prem



TeamsTeams
商務用 SkypeSkype for Business
TeamsTeams
商務用 SkypeSkype for Business
SfB*SfB*
商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
OnlineOnline
內部部署On-prem

商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
TeamsOnlyTeamsOnly TeamsTeams OnlineOnline

TeamsTeams

資料表1b:在租使用者的新聊天中,或以 SfB 模式呼叫路由至收件者 *Table 1b: in-tenant new chat or call routing to a recipient in an SfB* mode



Mode
觸發器Originator

用戶端Client


SfB   宿主SfB homed


Route-->Route-->
Recipient

SfB*SfB*
離島Islands TeamsTeams
商務用 SkypeSkype for Business
TeamsTeams
商務用 SkypeSkype for Business
OnlineOnline
OnlineOnline
內部部署On-prem
內部部署On-prem




商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
無法進行Not Possible
商務用 SkypeSkype for Business
SfB*SfB*
商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
OnlineOnline
內部部署On-prem

商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
TeamsOnlyTeamsOnly TeamsTeams OnlineOnline

商務用 SkypeSkype for Business

資料表1c:租使用者新聊天或呼叫路由至 TeamsOnly 模式收件者Table 1c: in-tenant new chat or call routing to a TeamsOnly mode recipient



Mode
觸發器Originator

用戶端Client


SfB   宿主SfB homed


Route-->Route-->
Recipient

TeamsOnlyTeamsOnly
離島Islands TeamsTeams
商務用 SkypeSkype for Business
TeamsTeams
商務用 SkypeSkype for Business
OnlineOnline
OnlineOnline
內部部署On-prem
內部部署On-prem



TeamsTeams
團隊Teams
TeamsTeams
團隊Teams
SfB*SfB* 商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
OnlineOnline
內部部署On-prem

團隊Teams
團隊Teams
TeamsOnlyTeamsOnly TeamsTeams OnlineOnline TeamsTeams

新聊天或通話的聯盟路由Federated routing for new chats or calls

下表會捕獲同盟通話與聊天的路由,且適用于新的通話或聊天。The tables below capture routing of federated calls and chats, and are valid for new calls or chats. 它們說明哪個用戶端會收到新的通話或聊天(如果是由左邊的使用者發起)到右側的聯盟目標使用者。They describe which client will receive a new call or chat, if originated by a user on the left, to a federated target user on the right.

在摘要中,如果可以如上所述進行交談,傳送給 TeamsOnly 使用者的訊息將永遠位於小組中;傳送給 SfB 使用者的郵件 * 將永遠位於商務用 skype 中; 傳送給孤島使用者的訊息,無論傳送給您的客戶,都將永遠居住在商務用 skype 中。In summary, if the conversation is possible as described above, messages sent to TeamsOnly users will always land in Teams; messages sent to SfB* users will always land in Skype for Business; messages sent to Islands users will always land in Skype for Business regardless of the client from which they were sent. 聯盟聊天和通話的路由與在該孤島中的租使用者內路由不同,在商務用 Skype 中,將永遠會收到聯盟通訊。Routing for federated chats and calls differs from in-tenant routing in that Islands users will always receive a federated communication in Skype for Business.

這是因為我們無法假設聯合商務用 Skype 合作夥伴已在使用孤島模式時使用團隊。This is because we cannot assume that a federated Skype for Business partner already uses Teams if they are in Islands mode. [孤島] 是預設模式,但我們無法假設所有孤島使用者都執行團隊。Islands is the default mode, however we can't assume all Islands users run Teams. 透過傳送到商務用 Skype,我們可以確保沒有孤島的通訊失敗。By routing to Skype for Business we ensure that no communication to an Islands user fails. 如果我們路由至團隊,如果目標不是使用小組,就可能會錯過該通訊。If we routed to Teams, that communication could be missed if the target did not use Teams. [路由到商務用 Skype] 可確保郵件永遠收到。Routing to Skype for Business ensures the message will always be received.

注意

目前的團隊同盟實現是以商務用 Skype 同盟為基礎,因此它利用互通性基礎結構 (,要求始發者的租使用者是純線上或商務用 Skype 混合式) ,並提供與原生執行緒相比的一組精簡的功能。Current implementation of Teams federation is based upon Skype for Business federation, therefore it leverages the interoperability infrastructure (which requires the tenant of the originator to be either pure online or Skype for Business hybrid) and provides a reduced set of capabilities compared to a native thread. 我們預期會在將來為團隊同盟提供原生團隊,此時,該執行緒就會成為原生,並提供完整功能。We expect to provide native Teams to Teams federation in the future, at which point the thread will be native and provide full capabilities.

下表說明哪個用戶端會從始發者 (三個最左邊的欄) ,視始發者的模式、用戶端,以及其商務用 Skype 用戶端 (在內部部署或線上) 的位置而定。The tables below describe which client will receive a call from the originator (three leftmost columns), depending on the originator's mode, client chosen, and where their Skype for Business client is homed (on-prem or online).

表格2a:同盟新聊天或通話路由至孤島收件者Table 2a: federated new chat or call routing to an Islands recipient



Mode
觸發器Originator

用戶端Client


SfB 宿主SfB homed


Route-->Route-->
Recipient

離島Islands
離島Islands TeamsTeams
商務用 SkypeSkype for Business
TeamsTeams
商務用 SkypeSkype for Business
OnlineOnline
OnlineOnline
內部部署On-prem
內部部署On-prem




商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
無法進行Not Possible
商務用 SkypeSkype for Business
SfB*SfB* 商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
OnlineOnline
內部部署On-prem

商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
TeamsOnlyTeamsOnly TeamsTeams OnlineOnline 商務用 SkypeSkype for Business

表格2b:同盟新聊天或通話以 SfB 模式傳送給收件者 *Table 2b: federated new chat or call routing to a recipient in an SfB* mode



Mode
觸發器Originator

用戶端Client


SfB 宿主SfB homed


Route-->Route-->
Recipient

SfB*SfB*
離島Islands TeamsTeams
商務用 SkypeSkype for Business
TeamsTeams
商務用 SkypeSkype for Business
OnlineOnline
OnlineOnline
內部部署On-prem
內部部署On-prem




商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
無法進行Not Possible
商務用 SkypeSkype for Business
SfB*SfB* 商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
OnlineOnline
內部部署On-prem

商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
TeamsOnlyTeamsOnly TeamsTeams OnlineOnline 商務用 SkypeSkype for Business

表格2c:同盟新聊天或呼叫路由至 TeamsOnly 模式收件者Table 2c: federated new chat or call routing to a TeamsOnly mode recipient



Mode
觸發器Originator

用戶端Client


SfB 宿主SfB homed


Route-->Route-->
Recipient

TeamsOnlyTeamsOnly
離島Islands TeamsTeams
商務用 SkypeSkype for Business
TeamsTeams
商務用 SkypeSkype for Business
OnlineOnline
OnlineOnline
內部部署On-prem
內部部署On-prem



TeamsTeams
團隊Teams
無法進行Not Possible
團隊Teams
SfB*SfB* 商務用 SkypeSkype for Business
商務用 SkypeSkype for Business
OnlineOnline
內部部署On-prem

團隊Teams
團隊Teams
TeamsOnlyTeamsOnly TeamsTeams OnlineOnline TeamsTeams

來自預先存在的執行緒的聊天與通話Chats and calls from pre-existing threads

從團隊From Teams

在小組中預先存在的持久性執行緒開始的通話或聊天,會以與該執行緒相同的方式進行路由(如果該 [路由] 選項仍可使用)。Calls or chats started from a pre-existing persistent thread in Teams will be routed in the same manner as that thread, if that routing option is still available.

如果在小組中預先存在的持久性執行緒是原生執行緒 (亦即路由至團隊) ,則其他聊天訊息和來自該執行緒的呼叫都會移至團隊。If the pre-existing persistent thread in Teams was a native thread (i.e. routed to Teams), additional chat messages and calls from that thread will go to Teams. 如果它是交互操作執行緒 ((例如路由到商務用 Skype) ),則其他聊天訊息和通話會移至商務用 Skype (再次假設路由選項可供使用) 。If it was an interop thread (i.e. routed to Skype for Business), additional chat messages and calls will go to Skype for Business (again assuming routing options are available).

注意

小組中的預先存在的執行緒可能無法再進行路由,例如當執行緒是交互操作執行緒給現在已升級至團隊的使用者時。It's possible for pre-existing threads in Teams to no longer be routable, such as when the thread was an interop thread to a user that is now upgraded to Teams. 由於它是以交互操作執行緒的方式建立,所以該執行緒會傳送到商務用 skype,但該使用者不再可以使用商務用 Skype 聊天和通話。Since it was created as an interop thread, the thread would route to Skype for Business, but that user no longer can use Skype for Business for chat and calling. 在這種情況下,該執行緒將停用,而不會允許進一步的通訊。In that case, the thread will be disabled and not permit further communication.

從商務用 SkypeFrom Skype for Business

商務用 Skype 執行緒不會保留在10分鐘的 SIP 會話超時以外。Skype for Business threads do not persist beyond the 10 min. SIP session timeout. 在 SIP 會話到期前,在商務用 Skype 中,來自現有線程的聊天和呼叫將會以與執行緒相同的方式進行路由。Chats and calls from an existing thread in Skype for Business prior to expiration of the SIP session will be routed in the same manner as the thread. 除了 SIP 會話超時之外,在商務用 Skype 中,來自現有的執行緒的通話和聊天,都將路由到遠端參與方的商務用 Skype,不論原始執行緒是來自其他人的那一方。Calls and chats from an existing thread in Skype for Business beyond the SIP session timeout will be routed to the remote party's Skype for Business, regardless of which client the original thread came from on the other party's side.

供應Availability

上述所述的租使用者與同盟行為都提供,且有下列限制:Both the in-tenant and federated behaviors described above are available, with the following limitations:

  • 租使用者位於不同 GoLocal 部署或地理位置的外部參與者在「同盟」會議中不會看到 IM 聊天External attendees whose tenants reside in a different GoLocal deployment or geography won't see IM chat while in a "federated" meeting
  • 不支援多租戶 O365 與主權雲彩之間的同盟與互通性Federation and interop between Multitenant O365 and Sovereign Clouds is not supported

目前狀態Presence

當您有部分使用者使用團隊用戶端,而其他使用者仍在使用商務用 Skype 用戶端時,您可能會有許多使用這兩個用戶端的使用者。When you have a situation where some of your users are using the Teams client and others are still using the Skype for Business client, you may have a number of users who are using both clients. 您仍想要與所有使用者共用目前狀態狀態,而不需考慮個別使用者所擁有的用戶端。You still want presence states to be shared with all users without regard to what client an individual user has. 在組織中共用這種情況時,使用者可以更好地判斷是否適合啟動聊天或撥打通話。When this is shared across the organization, users can better determine whether it's appropriate to initiate a chat or make a call.

例如,如果始發者的聊天或通話應該位於目標的商務用 Skype 用戶端上,那麼就是商務用 Skype 用戶端的目前狀態,應該顯示給始發者。For example, if an originator's chat or call should land on the target's Skype for Business client, then it's the Skype for Business client's presence that should be shown to the originator. 如果它應該位於目標的團隊用戶端,則是團隊用戶端的目前狀態。If it should land on the target's Teams client, then it's the Teams client's presence that should be shown.

若要瞭解預期的行為,您必須瞭解目前狀態是根據使用者的共存模式進行共用:In order to know what behavior to expect, you'll need to understand that Presence is shared based on a user's coexistence mode:

  • 如果使用者處於 TeamsOnly 模式,則任何其他使用者 (無論是在團隊或商務用 Skype) 中,都可以看到 TeamsOnly 使用者的小組目前狀態If a user is in TeamsOnly mode, then any other user (whether in Teams or Skype for Business) will see that TeamsOnly user's Teams presence
  • 如果使用者處於任何 SfB * 模式 (SfbOnly、SfbWithTeamsCollab、SfbWithTeamsCollabAndMeetings) ,然後任何其他使用者 (無論是在團隊或商務用 skype 中) ,都能看到 SfB * 使用者的商務用 skype 目前狀態If a user is in any of the SfB* modes (SfbOnly, SfbWithTeamsCollab, SfbWithTeamsCollabAndMeetings), then any other user (whether in Teams or Skype for Business) will see that SfB* user's Skype for Business presence
  • 如果使用者使用的是孤島 (或舊版) 模式,則團隊中的目前狀態與商務用 Skype 中的目前狀態是獨立的 (值不需要符合) ,其他使用者就會看到一或多個孤島使用者的狀態,這取決於它們是位於相同的租使用者中,還是在聯盟租使用者中使用的用戶端。If a user is in Islands (or Legacy) mode, presence in Teams and presence in Skype for Business are independent (the values need not match) and other users will see one or the other presence of the Islands user, depending on whether they are in the same tenant or in a federated tenant and which client they use
    • 從團隊來看,同一租使用者中的任何其他使用者都會看到孤島使用者的小組目前狀態。這與上述的租使用者路由表對齊From Teams, any other user within the same tenant will see the Islands user's Teams presence; this is aligned with the in-tenant routing table above
    • 從團隊來看,同盟租使用者中的任何其他使用者都會看到孤島使用者的商務用 Skype 目前狀態;這與上述聯盟路由表對齊From Teams, any other user in a federated tenant will see the Islands user's Skype for Business presence; this is aligned with the federated routing table above
    • 在商務用 Skype 中,任何其他使用者都會看到孤島使用者的商務用 Skype 目前狀態 (在租使用者與同盟) 中;這與上述路由表對齊From Skype for Business, any other user will see the Islands user's Skype for Business presence (both in-tenant and federated); this is aligned with the routing tables above

租使用者狀態In-tenant presence

傳送給 TeamsOnly 使用者的郵件將永遠位於小組中。Messages sent to TeamsOnly users will always land in Teams. 傳送給 SfB * 使用者的郵件永遠會在商務用 Skype 中保持居住,如果可以進行交談,如上述所述。Messages sent to SfB* users will always land in Skype for Business, if the conversation is possible as described above. 傳送給孤島使用者的訊息將永遠位於其起源的用戶端。Messages sent to Islands users will always land in the client from which they were originated.

此表格說明發行商將會看到的發行者目前狀態,視發行者的模式和新執行緒) 的 [觀察程式] (之用戶端而定。The table describes the Publisher's presence that will be seen by a Watcher, depending on the mode of the Publisher and the client of the Watcher (for a new thread).

**資料表3: (新執行緒) 的租使用者狀態 **Table 3: in-tenant presence (new thread)

監視器Watcher

用戶端Client


Route-->Route-->


離島Islands
PublisherPublisher

SfB*SfB*

僅限團隊Teams Only
商務用 SkypeSkype for Business 商務用 SkypeSkype for Business 商務用 SkypeSkype for Business TeamsTeams
TeamsTeams TeamsTeams 商務用 SkypeSkype for Business TeamsTeams

同盟目前狀態Federated presence

同盟目前狀態是以表格2所示的同盟可存取性為基礎。Federated presence is based upon the federated reachability shown in table 2.

下表說明發行者會看到的發行商目前狀態,視發行者的模式和新執行緒) 的 [觀察程式] (之用戶端而定。The table below describes the Publisher's presence that will be seen by a Watcher, depending on the mode of the Publisher and the client of the Watcher (for a new thread). 在實踐中,觀察程式的用戶端在此階段不會有任何不同之處。In practice the client of the Watcher makes no difference in federation at this stage.

**資料表4:同盟存在 (新執行緒) **Table 4: federated presence (new thread)

監視器Watcher

用戶端Client


Route-->Route-->


離島Islands
PublisherPublisher

SfB*SfB*


僅限團隊Teams Only
商務用 SkypeSkype for Business 商務用 SkypeSkype for Business 商務用 SkypeSkype for Business TeamsTeams
TeamsTeams 商務用 SkypeSkype for Business 商務用 SkypeSkype for Business TeamsTeams

在預先存在的執行緒中的目前狀態Presence in pre-existing threads

為了在預先存在的執行緒中對齊目前狀態和可存取性,該執行緒中公開的目前狀態必須與執行緒路由(假設路由可能)對齊。In order to align presence and reachability in pre-existing threads, the target's presence exposed in that thread needs to be aligned with the routing of the thread, assuming routing is possible.

特別是,如果收件者先前已升級至團隊的持續性互通性交談執行緒,該執行緒就不會再反映精確的目前狀態,而且將無法再進行路由。In particular, if a recipient you previously had a persistent interop conversation thread with was upgraded to Teams, that thread will no longer reflect accurate presence and will no longer be routable. 您應該開始新的執行緒。You should start a new thread.

與商務用 Skype 搭配使用團隊之組織的遷移和互通性指南Migration and interoperability guidance for organizations using Teams together with Skype for Business

影片:管理 SfB 與團隊之間的共存與互通性Video: Manage Coexistence and Interoperability between SfB and Teams