Microsoft Teams 通话流程Microsoft Teams call flows

提示

观看此讲座,了解团队如何利用你的网络以及如何规划最佳网络连接:团队网络规划Watch this session to learn how Teams leverages your network and how to plan for optimal network connectivity: Teams Network Planning.

概述Overview

本文介绍团队如何使用各种拓扑中的 Microsoft 365 或 Office 365 调用流。This article describes how Teams uses Microsoft 365 or Office 365 call flows in various topologies. 此外,它还介绍了用于对等媒体通信的独特团队流。In addition, it describes unique Teams flows that are used for peer-to-peer media communication. 文档介绍这些流、其用途以及它们在网络上的来源和终止。The document describes these flows, their purpose, and their origin and termination on the network. 为此,请考虑以下事项:For purposes of this article, assume the following:

  • 流 X 由本地客户端用于与云中的 Microsoft 365 或 Office 365 服务进行通信。Flow X is used by the on-premises client to communicate with the Microsoft 365 or Office 365 service in the cloud. 它源于客户网络,并作为 Microsoft 365 或 Office 365 中的终结点终止。It originates from the customer network, and it terminates as an endpoint in Microsoft 365 or Office 365.

  • 流 Y 由本地客户端用于与 Microsoft 365 或 Office 365 依赖的 Internet 上的服务进行通信。Flow Y is used by the on-premises client to communicate with a service on the Internet that Microsoft 365 or Office 365 has a dependency on. 它源于客户网络,并作为 Internet 上的终结点终止。It originates from the customer network, and it terminates as an endpoint on the Internet.

本文介绍以下信息:This article covers the following information:

  • 背景Background. 提供背景信息,例如流可能遍历的网络、流量的类型、从客户网络到 Microsoft 365 或 Office 365 服务终结点的连接指南、与第三方组件的互操作性,以及团队用于选择媒体流的原则。Provides background information such as networks that the flows may traverse, types of traffic, connectivity guidance from the customer network to Microsoft 365 or Office 365 service endpoints, interoperability with third-party components, and principles that are used by Teams to select media flows.

  • 各种拓扑中的通话流Call flows in various topologies. 说明如何在各种拓扑中使用调用流。Illustrates the use of call flows in various topologies. 对于每个拓扑,该部分将枚举所有受支持的流,并阐释如何在多个使用案例中使用这些流。For each topology, the section enumerates all supported flows and illustrates how these flows are used in several use cases. 对于每个用例,它使用流图描述流的序列和选择。For each use case, it describes the sequence and selection of flows using a flow diagram.

  • 具有快速路线优化的团队Teams with Express Route optimization. 介绍了在部署快速路由以进行优化时如何使用这些流,使用简单拓扑进行图解。Describes how these flows are used when Express Route is deployed for optimization, illustrated using a simple topology.

背景Background

网络段Network segments

客户网络Customer network. 这是您控制和管理的网络段。This is the network segment that you control and manage. 这包括客户办公室中的所有客户连接,无论是有线还是无线、office 大楼之间的连接、本地数据中心的连接,还是与 Internet 提供商、快速路线或任何其他私人对等的连接。This includes all customer connections within customer offices, whether wired or wireless, connections between office buildings, connections to on-premises datacenters, and your connections to Internet providers, Express Route, or any other private peering.

通常情况下,客户网络具有多个具有防火墙和/或代理服务器的网络外围,这些服务器强制实施组织的安全策略,并且仅允许某些已设置和配置的网络流量。Typically, a customer network has several network perimeters with firewalls and/or proxy servers, which enforce your organization's security policies, and that only allow certain network traffic that you have set up and configured. 由于你管理此网络,你可以直接控制网络性能,我们建议你完成网络评估,以验证网络中的网站和你的网络与 Microsoft 365 或 Office 365 网络之间的性能。Because you manage this network, you have direct control over the performance of the network, and we recommend that you complete network assessments to validate performance both within sites in your network and from your network to the Microsoft 365 or Office 365 network.

互联网Internet. 这是您的整个网络的一部分,该网络段将由从客户网络外部连接到 Microsoft 365 或 Office 365 的用户使用。This is the network segment that is part of your overall network that will be used by users who are connecting to Microsoft 365 or Office 365 from outside of the customer network. 它还可由从客户网络到 Microsoft 365 或 Office 365 的某些流量使用。It is also used by some traffic from the customer network to Microsoft 365 or Office 365.

访问或来宾专用网络Visited or guest private network. 这是客户网络外部的网络段,而不是在公共 Internet 中,您的用户和他们的来宾可能会访问(例如,家庭专用网络或企业专用网络),不会部署团队,您的用户及其与团队服务之间的客户可能会驻留。This is the network segment outside your customer network, but not in the public Internet, that your users and their guests may visit (for example, a home private network or an enterprise private network, that does not deploy Teams, where your users and their customers that interact with Teams services may reside).

备注

与 Microsoft 365 或 Office 365 的连接也适用于这些网络。Connectivity to Microsoft 365 or Office 365 is also applicable to these networks.

Microsoft 365 或 Office 365Microsoft 365 or Office 365. 这是支持 Microsoft 365 或 Office 365 服务的网络段。This is the network segment that supports Microsoft 365 or Office 365 services. 在全球各地,全球各地都有与客户网络邻近的边缘。It is distributed worldwide with edges in proximity to the customer network in most locations. 函数包括传输中继、会议服务器和媒体处理器。Functions include Transport Relay, conferencing server, and Media Processor.

快速路线(可选)Express Route (optional). 这是您的整个网络的一部分,它将为您提供到 Microsoft 365 或 Office 365 网络的专用专用连接。This is the network segment that is part of your overall network that will give you a dedicated, private connection to the Microsoft 365 or Office 365 network.

流量类型Types of traffic

实时媒体Real-time media. 在支持音频、视频和屏幕共享工作负荷的实时传输协议(RTP)中封装的数据。Data encapsulated within Real-time Transport Protocol (RTP) that supports audio, video, and screen sharing workloads. 通常情况下,媒体流量很高的延迟,因此你希望此流量能够充分利用最直接的路径,并将 UDP 与 TCP 用作传输层协议,这是从质量角度来看交互式实时媒体的最佳传输。In general, media traffic is highly latency sensitive, so you would want this traffic to take the most direct path possible, and to use UDP versus TCP as the transport layer protocol, which is the best transport for interactive real time media from a quality perspective. (请注意,作为最后的手段,媒体可以使用 TCP/IP,也可以在 HTTP 协议中使用隧道,但不建议由于不良的质量影响。)使用 SRTP 保护 RTP 流,其中仅加密负载。(Note that as a last resort, media can use TCP/IP and also be tunneled within the HTTP protocol, but it is not recommended due to bad quality implications.) RTP flow is secured using SRTP, in which only the payload is encrypted.

信号Signaling. 客户端和服务器之间的通信链接,或用于控制活动的其他客户端(例如,启动呼叫时)和发送即时消息。The communication link between the client and server, or other clients that are used to control activities (for example, when a call is initiated), and deliver instant messages. 大多数信号流量使用基于 HTTPS 的 REST 接口,但在某些情况下(例如,Microsoft 365 或 Office 365 和会话边界控制器之间的连接),它将使用 SIP 协议。Most signaling traffic uses the HTTPS-based REST interfaces, though in some scenarios (for example, connection between Microsoft 365 or Office 365 and a Session Border Controller) it uses SIP protocol. 请务必了解此流量对延迟的敏感程度不太大,但如果终结点之间的延迟超过几秒,可能会导致服务中断或呼叫超时。It's important to understand that this traffic is much less sensitive to latency but may cause service outages or call timeouts if latency between the endpoints exceeds several seconds.

与 Microsoft 365 或 Office 365 的连接Connectivity to Microsoft 365 or Office 365

团队需要连接到 InternetTeams requires connectivity to the Internet. 团队终结点 Url 和 IP 地址范围在Office 365 url 和 ip 地址范围中列出。Teams endpoint URLs and IP address ranges are listed in Office 365 URLs and IP address ranges. (请注意,与 TCP 端口80和443的开放连接,以及到 UDP 端口3478到3481的连接。)此外,团队对 Skype for business Online 有依赖关系,该功能还必须连接到 Internet。(Note that open connectivity to TCP ports 80 and 443, and to UDP ports 3478 through 3481, is required.) Furthermore, Teams has a dependency on Skype for Business Online, which must also be connected to the Internet.

团队媒体流连接是使用标准的 IETF 交互式连接建立(ICE)过程实现的。Teams media flows connectivity is implemented using standard IETF Interactive Connectivity Establishment (ICE) procedures.

互操作性限制Interoperability restrictions

第三方媒体中继Third-party media relays. 团队媒体流(即,其中一个媒体终结点是团队)可能仅遍历团队或 Skype for business 本机媒体中继。A Teams media flow (that is, where one of the media endpoints is Teams) may traverse only Teams or Skype for Business native media relays. 不支持与第三方媒体中继的互操作。Interoperability with a third-party media relay is not supported. (请注意,具有 PSTN 的第三方 SBC 必须终止 RTP/RTCP 流,使用 SRTP 进行保护,而不是将其中继到下一跃点。)(Note that a third-party SBC on the boundary with PSTN must terminate RTP/RTCP stream, secured using SRTP, and not relay it to the next hop.)

第三方 SIP 代理服务器Third-party SIP proxy servers. 带有第三方 SBC 和/或网关的团队发来的 "SIP" 对话框可能会遍历团队或 Skype for business 本机 SIP 代理。A Teams signaling SIP dialog with a third-party SBC and/or gateway may traverse Teams or Skype for Business native SIP proxies. 不支持与第三方 SIP 代理的互操作。Interoperability with a third-party SIP proxy is not supported.

第三方 B2BUA (或 SBC)Third-party B2BUA (or SBC). 由第三方 SBC 终止来自 PSTN 的团队媒体流。A Teams media flow to and from the PSTN is terminated by a third-party SBC. 但是,不支持与团队网络中的第三方 SBC (第三方 SBC 调节两个团队或 Skype for business 终结点)之间的互操作性。However, interoperability with a third-party SBC within the Teams network (where a third-party SBC mediates two Teams or Skype for Business endpoints) is not supported.

VPN 网络VPN network. 不建议媒体流量(或流 2 ")。It is not recommended for media traffic (or flow 2'). VPN 客户端应使用分离的 VPN 和路由媒体流量(如任何外部非 VPN 用户),如使 Lync 媒体绕过 VPN 隧道指定的任何外部非 VPN 用户。The VPN client should use split VPN and route media traffic like any external non-VPN user, as specified in Enabling Lync media to bypass a VPN tunnel.

备注

尽管标题指示 Lync,但它也适用于团队。Although the title indicates Lync, it is applicable to Teams as well.

数据包 shapersPacket shapers. 不推荐任何类型的数据包 snippers、数据包检查或数据包整形设备,可能会显著降低质量。Any kind of packet snippers, packet inspection, or packet shaper devices are not recommended and may degrade quality significantly.

规则Principles

有四个一般原则可帮助你理解 Microsoft 团队的通话流:There are four general principles that help you understand call flows for Microsoft Teams:

  • Microsoft 团队会议由 Microsoft 365 或 Office 365 托管,位于第一个参与者加入的同一区域中。A Microsoft Teams conference is hosted by Microsoft 365 or Office 365 in the same region where the first participant joined. (请注意,如果某些拓扑中存在此规则的例外情况,将在本文档中对其进行介绍,并通过相应的通话流进行说明。)(Note that if there are exceptions to this rule in some topologies, they will be described in this document and illustrated by an appropriate call flow.)

  • Microsoft 365 或 Office 365 中的团队媒体终结点根据媒体处理需求使用,而不是基于呼叫类型。A Teams media endpoint in Microsoft 365 or Office 365 is used based on media processing needs and not based on call type. (例如,点到点呼叫可以使用云中的媒体终结点处理媒体进行操作或录制,而两个参与者的会议可能不会使用云中的任何媒体终结点。)但是,大多数会议会将媒体终结点用于混合和路由用途,分配了托管会议的位置。(For example, a point-to-point call may use a media endpoint in the cloud to process media for transcription or recording, while a conference with two participants may not use any media endpoint in the cloud.) However, most conferences will use a media endpoint for mixing and routing purposes, allocated where the conference is hosted. 从客户端发送到媒体终结点的媒体流量可以直接路由,或在 Microsoft 365 或 Office 365 中使用传输中继(如果由于客户网络防火墙限制而需要)。The media traffic sent from a client to the media endpoint may be routed directly or use a Transport Relay in Microsoft 365 or Office 365 if required due to customer network firewall restrictions.

  • 对等呼叫的媒体流量采用可用的最直接路线,假设该呼叫不会在云中强制使用媒体终结点(请参阅以前的原则)。Media traffic for peer-to-peer calls take the most direct route that is available, assuming that the call doesn't mandate a media endpoint in the cloud (see previous principle). 首选路由直接发送到远程对等(客户端),但如果该路由不可用,则一个或多个传输中继将中继流量。The preferred route is direct to the remote peer (client), but if that route isn't available, then one or more Transport Relays will relay traffic. 建议媒体流量不应遍历服务器(如数据包 shapers、VPN 服务器等),因为这将影响媒体质量。It is recommended that media traffic shall not transverse servers such as packet shapers, VPN servers, and so on, since this will impact the media quality.

  • 信号流量始终转到最接近于用户的服务器。Signaling traffic always goes to the closest server to the user.

若要了解有关所选媒体路径的详细信息,请参阅了解 Microsoft 团队中的媒体流-BRK4016To learn more about the details on the media path that is chosen, see Understanding Media Flows in Microsoft Teams - BRK4016.

各种拓扑中的呼叫流Call flows in various topologies

团队拓扑Teams topology

此拓扑由客户使用,它在没有任何本地部署(如 Skype for Business Server 或手机系统直接路由)的情况下利用来自云的团队服务。This topology is used by customers that leverage Teams services from the cloud without any on-premises deployment, such as Skype for Business Server or Phone System Direct Routing. 此外,在没有 Azure Express 路由的情况下,Microsoft 365 或 Office 365 的接口通过 Internet 完成。In addition, the interface to Microsoft 365 or Office 365 is done over the Internet without Azure Express Route.

Microsoft 团队在线通话流程图01Microsoft Teams Online Call Flows Figure 01

图 1-团队拓扑Figure 1 - Teams topology

请注意:Note that:

  • 上图中箭头的方向反映了在企业外围环境中影响连接的通信的初始方向。The direction of the arrows on the diagram above reflect the initiation direction of the communication that affects connectivity at the enterprise perimeters. 在 UDP for media 的情况下,第一个数据包可能沿相反方向流动,但这些数据包可能会被阻止,直到其他方向的数据包才会流动。In the case of UDP for media, the first packet(s) may flow in the reverse direction, but these packets may be blocked until packets in the other direction will flow.
  • 团队与 Skype for Business Online 并排部署,因此客户将显示为 "团队/SFB 用户"。Teams is deployed side by side with Skype for Business Online, hence clients are displayed as "Teams/SFB user."

有关详细信息,请查看本文后面的以下可选拓扑:You can find more information on the following optional topologies later in the article:

  • 团队混合拓扑中介绍了 Skype for business 内部部署。Skype for Business on-premises deployment is described in Teams hybrid topology.
  • 手机系统直接路由(适用于 PSTN 连接)在具有直接路由拓扑的团队中介绍。Phone System Direct Routing (for PSTN connectivity) is described in Teams with Direct Routing topology.
  • 快速路线在具有 Express 路线优化的团队中介绍。Express Route is described in Teams with Express Route optimization.

流说明Flow descriptions:

  • 流 2 -表示用户在客户网络上作为用户团队体验的一部分启动的流程。Flow 2 – Represents a flow initiated by a user on the customer network to the Internet as a part of the user's Teams experience. 这些流的示例是 DNS 和对等媒体。Examples of these flows are DNS and peer-to-peer media.
  • 流 2 " –表示由远程移动团队用户发起的流,其中包含指向客户网络的 VPN。Flow 2' – Represents a flow initiated by a remote mobile Teams user, with VPN to the customer network.
  • 流 3 -表示由远程移动团队用户发起的由 Microsoft 365 或 Office 365/团队终结点发起的流程。Flow 3 – Represents a flow initiated by a remote mobile Teams user to Microsoft 365 or Office 365/Teams endpoints.
  • 流 4 -表示用户在客户网络上由 Microsoft 365 或 Office 365/团队终结点发起的流程。Flow 4 – Represents a flow initiated by a user on the customer network to Microsoft 365 or Office 365/Teams endpoints.
  • 流 5 -表示团队用户与其他团队之间的对等媒体流,或客户网络中的 Skype for business 用户。Flow 5 – Represents a peer-to-peer media flow between a Teams user and another Teams or Skype for Business user within the customer network.
  • 流 6 -表示远程移动团队用户与其他远程移动团队或 Internet 上的 Skype for business 用户之间的对等媒体流。Flow 6 – Represents a peer-to-peer media flow between a remote mobile Teams user and another remote mobile Teams or Skype for Business user over the Internet.

使用案例:一对一Use case: One-to-one

一对一呼叫使用一个通用模型,在该模型中,呼叫者将获得一组候选项,其中包括本地、中继和自反(客户的公共 IP 地址,如中继)候选人。One-to-one calls use a common model in which the caller will obtain a set of candidates consisting of IP addresses/ports, including local, relay, and reflexive (public IP address of client as seen by the relay) candidates. 呼叫方将这些候选人发送给被呼叫方;被呼叫方还会获取一组类似的候选项,并将其发送给呼叫方。The caller sends these candidates to the called party; the called party also obtains a similar set of candidates and sends them to the caller. STUN 连接检查消息用于查找哪些呼叫方/被叫方媒体路径正常工作,并且选择了最佳工作路径。STUN connectivity check messages are used to find which caller/called party media paths work, and the best working path is selected. 然后,使用所选候选人对发送媒体(即使用 SRTP 的安全的 RTP/RTCP 数据包)。Media (that is, RTP/RTCP packets secured using SRTP) are then sent using the selected candidate pair. 传输中继作为 Microsoft 365 和 Office 365 的一部分进行部署。The Transport relay is deployed as part of Microsoft 365 and Office 365.

如果本地 IP 地址/端口候选或反身候选具有连接,则将为媒体选择客户端(或使用 NAT)之间的直接路径。If the local IP address/port candidates or the reflexive candidates have connectivity, then the direct path between the clients (or using a NAT) will be selected for media. 如果客户端位于客户网络上,则应选择直接路径。If the clients are both on the customer network, then the direct path should be selected. 这需要客户网络内的直接 UDP 连接。This requires direct UDP connectivity within the customer network. 如果客户端都是 nomadic 云用户,则根据 NAT/防火墙,媒体可能使用直接连接。If the clients are both nomadic cloud users, then depending on the NAT/firewall, media may use direct connectivity.

如果一个客户端是客户网络内部的客户端,而另一个客户端是外部客户端(例如,移动云用户),则本地或反身候选人之间的直接连接不太可能是正常工作。If one client is internal on the customer network and one client is external (for example, a mobile cloud user), then it is unlikely that direct connectivity between the local or reflexive candidates is working. 在这种情况下,选项是使用来自任何客户端的传输中继候选人之一(例如,内部客户从 Microsoft 365 或 Office 365 中的传输中继获得中继候选人; 外部客户端需要能够将 STUN/RTP/RTCP 数据包发送到传输中继)。In this case, an option is to use one of the Transport Relay candidates from either client (for example, the internal client obtained a relay candidate from the Transport relay in Microsoft 365 or Office 365; the external client needs to be able to send STUN/RTP/RTCP packets to the transport relay). 另一个选项是内部客户端发送到移动云客户端获取的中继候选人。Another option is the internal client sends to the relay candidate obtained by the mobile cloud client. 请注意,虽然强烈建议媒体的 UDP 连接,但支持 TCP。Note that, although UDP connectivity for media is highly recommended, TCP is supported.

高级别步骤High-level steps:

  1. 团队用户 A 使用流程2解析 URL 域名(DNS)。Teams User A resolves URL domain name (DNS) using flow 2.
  2. 团队用户 A 使用流4在团队传输中继上分配媒体中继端口。Teams User A allocates a media Relay port on Teams Transport Relay using flow 4.
  3. 团队用户 A 使用将流4到 Microsoft 365 或 Office 365 的 ICE 候选人发送 "邀请"。Teams User A sends "invite" with ICE candidates using flow 4 to Microsoft 365 or Office 365.
  4. Microsoft 365 或 Office 365 使用流4向团队用户 B 发送通知。Microsoft 365 or Office 365 sends notification to Teams User B using flow 4.
  5. 团队用户 B 使用流4在团队传输中继上分配媒体中继端口。Teams User B allocates a media Relay port on Teams Transport Relay using flow 4.
  6. 团队用户 B 使用流4向返回到团队用户 A 使用流4向其发送 "应答" 与 ICE 候选人。Teams User B sends "answer" with ICE candidates using flow 4, which is forwarded back to Teams User A using Flow 4.
  7. 团队用户 A 和团队用户 B 调用 ICE 连接测试,并选择最佳可用媒体路径(请参阅下面的各种使用案例的图表)。Teams User A and Teams User B invoke ICE connectivity tests and the best available media path is selected (see diagrams below for various use cases).
  8. 团队用户使用流4向 Microsoft 365 或 Office 365 发送遥测。Teams Users send telemetry to Microsoft 365 or Office 365 using flow 4.

在客户网络中:Within customer network:

Microsoft 团队在线通话流程图02Microsoft Teams Online Call Flows Figure 02

图 2-客户网络内部Figure 2 - Within customer network

在步骤7中,选择了 "对等媒体流 5"。In step 7, peer-to-peer media flow 5 is selected.

媒体为双向媒体。Media is bidirectional. 流5的方向表示,一方从连接的角度启动通信,与本文档中的所有流一致。The direction of flow 5 indicates that one side initiates the communication from a connectivity perspective, consistent with all the flows in this document. 在这种情况下,使用哪个方向无关紧要,因为这两个终结点位于客户网络内。In this case, it doesn't matter which direction is used because both endpoints are within the customer network.

向外部用户的客户网络(按团队传输中继的媒体中继):Customer network to external user (media relayed by Teams Transport Relay):

Microsoft 团队在线通话流程图03Microsoft Teams Online Call Flows Figure 03

图 3-向外部用户(按团队传输中继的媒体中继)的客户网络Figure 3 - Customer network to external user (media relayed by Teams Transport Relay)

在步骤7(从客户网络到 Microsoft 365 或 Office 365)和流程3(从 "远程移动团队" 用户到 Microsoft 365 或 Office 365)中,选择 "流程 4"。In step 7, flow 4, from customer network to Microsoft 365 or Office 365, and flow 3, from remote mobile Teams user to Microsoft 365 or Office 365, are selected. 这些流由 Microsoft 365 或 Office 365 中的团队传输中继进行中继。These flows are relayed by Teams Transport Relay within Microsoft 365 or Office 365.

媒体是双向的,其中,方向指示哪一侧从连接的角度开始通信。Media is bidirectional, where direction indicates which side initiates the communication from a connectivity perspective. 在这种情况下,这些流用于发送信号和媒体,使用不同的传输协议和地址。In this case, these flows are used for signaling and media, using different transport protocols and addresses.

向外部用户(直接媒体)的客户网络:Customer network to external user (direct media):

Microsoft 团队在线通话流程图04Microsoft Teams Online Call Flows Figure 04

图 4-外部用户(直接媒体)的客户网络Figure 4 - Customer network to external user (direct media)

在步骤 7 "流程 2" 中,选择 "从客户网络到 Internet (客户端对等)"。In step 7, flow 2, from customer network to the Internet (client's peer), is selected.

  • 带有远程移动用户(未通过 Microsoft 365 或 Office 365 中继)的直接媒体是可选的。Direct media with remote mobile user (not relayed through Microsoft 365 or Office 365) is optional. 换句话说,客户可能会阻止此路径通过 Microsoft 365 或 Office 365 中的传输中继强制执行媒体路径。In other words, customer may block this path to enforce a media path through Transport Relay in Microsoft 365 or Office 365.

  • 媒体为双向媒体。Media is bidirectional. 流2到远程移动用户的方向指示一方从连接的角度启动通信。The direction of flow 2 to remote mobile user indicates that one side initiates the communication from a connectivity perspective.

VPN 用户到内部用户(按团队传输中继的媒体中转)VPN user to internal user (media relayed by Teams Transport Relay)

Microsoft 团队在线通话流程图05Microsoft Teams Online Call Flows Figure 05

图 5-向内部用户(按团队传输中继的媒体中继)的 VPN 用户Figure 5 - VPN user to internal user (media relayed by Teams Transport Relay)

VPN 与客户网络之间的信号传输使用的是流2。Signaling between the VPN to the customer network is using flow 2'. 客户网络与 Microsoft 365 或 Office 365 之间的信号传输使用的是流4。Signaling between the customer network and Microsoft 365 or Office 365 is using flow 4. 但是,媒体绕过 VPN,并使用流3和4通过 Microsoft 365 或 Office 365 中的团队媒体中继进行路由。However, media bypasses the VPN and is routed using flows 3 and 4 through Teams media relay in Microsoft 365 or Office 365.

VPN 用户到内部用户(直接媒体)VPN user to internal user (direct media)

Microsoft 团队在线通话流程图06Microsoft Teams Online Call Flows Figure 06

图 6-向内部用户(直接媒体)的 VPN 用户Figure 6 - VPN user to internal user (direct media)

VPN 与客户网络之间的信号传输使用的是流2。Signaling between the VPN to the customer network is using flow 2'. 客户网络与 Microsoft 365 或 Office 365 之间的信号传输使用的是流4。Signaling between the customer network and Microsoft 365 or Office 365 is using flow 4. 但是,媒体将绕过 VPN,并使用从客户网络到 Internet 的流程2进行路由。However, media bypasses the VPN and is routed using flow 2 from the customer network to the Internet.

媒体为双向媒体。Media is bidirectional. 流2到远程移动用户的方向指示一方从连接的角度启动通信。The direction of flow 2 to the remote mobile user indicates that one side initiates the communication from a connectivity perspective.

向外部用户(直接媒体)的 VPN 用户VPN user to external user (direct media)

Microsoft 团队通话流程图07Microsoft Teams call flows Figure 07

图 7-向外部用户(直接媒体)的 VPN 用户Figure 7 - VPN user to external user (direct media)

VPN 用户与客户网络之间的信号传输使用的是流2,并使用流4到 Microsoft 365 或 Office 365。Signaling between the VPN user to the customer network is using flow 2' and using flow 4 to Microsoft 365 or Office 365. 但是,媒体绕过 VPN 并使用流6进行路由。However, media bypasses VPN and is routed using flow 6.

媒体为双向媒体。Media is bidirectional. 流6到远程移动用户的方向指示一方从连接的角度启动通信。The direction of flow 6 to the remote mobile user indicates that one side initiates the communication from a connectivity perspective.

使用案例:团队到 PSTN 通过 Microsoft 365 或 Office 365 主干Use Case: Teams to PSTN through Microsoft 365 or Office 365 Trunk

Microsoft 365 和 Office 365 有一个电话系统,允许从公共交换电话网络(PSTN)拨打和接听电话。Microsoft 365 and Office 365 have a Phone System that allows placing and receiving calls from the Public Switched Telephone Network (PSTN). 如果 PSTN 主干是使用电话系统呼叫计划连接的,则此使用情形没有特殊的连接要求。If the PSTN trunk is connected using the Phone System Calling Plan, then there are no special connectivity requirements for this use case. (如果要将自己的本地 PSTN 主干连接到 Microsoft 365 或 Office 365,则可以使用 "电话系统直接路由"。)(If you want to connect your own on-premises PSTN trunk to Microsoft 365 or Office 365, you can use Phone System Direct Routing.)

Microsoft 团队在线通话流程(见图08)Microsoft Teams Online Call Flows Figure 08

图 8-通过 Office 365 主干的团队到 PSTNFigure 8 - Teams to PSTN through Office 365 Trunk

使用案例:团队会议Use case: Teams meeting

音频/视频/屏幕共享(VBSS)会议服务器是 Microsoft 365 和 Office 365 的一部分。The audio/video/screen sharing (VBSS) conferencing server is part of Microsoft 365 and Office 365. 它具有必须可从客户网络访问且必须可从 Nomadic 云客户端访问的公共 IP 地址。It has a public IP address that must be reachable from the customer network and must be reachable from a Nomadic Cloud client. 每个客户端/终结点都需要能够连接到会议服务器。Each client/endpoint needs to be able to connect to the conferencing server.

内部客户将按照与一对一通话描述的相同方式获取本地、反身和中继候选人。Internal clients will obtain local, reflexive, and relay candidates in the same manner as described for one-to-one calls. 客户端会将这些候选人发送到邀请中的会议服务器。The clients will send these candidates to the conferencing server in an invite. 会议服务器不使用中继,因为它具有可公开访问的 IP 地址,因此它将通过其本地 IP 地址候选进行响应。The conferencing server does not use a relay since it has a publicly reachable IP address, so it responds with its local IP address candidate. 客户端和会议服务器将以与一对一呼叫描述的相同方式检查连接。The client and conferencing server will check connectivity in the same manner described for one-to-one calls.

请注意:Note that:

  • 团队客户端无法加入 Skype for Business 会议,并且 Skype for business 客户端无法加入团队会议。Teams clients cannot join Skype for Business meetings, and Skype for Business clients cannot join Teams meetings.

  • PSTN 用户(可选) "拨入" 或 "拨出",具体取决于会议的组织者 PSTN 呼叫和/或会议设置。A PSTN user optionally "Dials IN" or is "Dialed OUT", depending on the meeting's organizer PSTN Calling and/or conferencing provisioning.

  • 来宾用户或客户用户可以通过使用带有严格规则的 FW/NAT 进行保护的来宾专用网络加入。A guest user or a customer user may join from a guest private network, which is protected using FW/NAT with strict rules.

Microsoft 团队在线通话流程图09Microsoft Teams Online Call Flows Figure 09

图 9-团队会议Figure 9 - Teams Meeting

使用案例:使用 Skype for business 内部部署联盟Use case: Federation with Skype for Business on premises

按组在 Microsoft 365 或 Office 365 中传输中继的媒体中继Media relayed by Teams Transport Relay in Microsoft 365 or Office 365

Microsoft 团队在线通话流程图10Microsoft Teams Online Call Flows Figure 10

图 10-按组在 Office 365 中传输中继的媒体中继Figure 10 - Media relayed by Teams Transport Relay in Office 365

请注意:Note that:

  • 根据定义,联盟是两个租户之间的通信。Federation is, by definition, a communication between two tenants. 在这种情况下,租户 A 使用团队,federates 与租户 B 一起使用 Skype for Business 内部部署。In this case, tenant A, which uses Teams, federates with tenant B, which uses Skype for Business on premises. 如果租户 B 也使用 Microsoft 365 或 Office 365,则 Skype for Business 客户端将使用流3与 Microsoft 365 或 Office 365 连接。If tenant B is also using Microsoft 365 or Office 365, then the Skype for Business client would have used flow 3 to connect with Microsoft 365 or Office 365.

  • 来自联合 Skype for business 客户端到本地 Skype for Business 服务器的信号和媒体已超出本文档的范围。Signaling and media from the federated Skype for Business client to on-premises Skype for Business Server is out of scope of this document. 但是,此处对此进行了明确说明。However, it is illustrated here for clarity.

  • 团队和 Skype for business 之间的信号由网关桥接。Signaling between Teams and Skype for Business is bridged by a gateway.

  • 在此情况下,媒体将通过团队将中继传输到客户网络和使用流4的远程 Skype for Business 客户端进行中继。Media in this case is relayed by Teams Transport Relay to the customer network and remote Skype for Business client using flow 4.

联合租户中 Skype for business Media 中继的媒体中继Media relayed by Skype for Business Media Relay in federated tenant

Microsoft 团队在线通话流程图11Microsoft Teams Online Call Flows Figure 11

图 11-联合租户中 Skype for business Media 中继的媒体中继Figure 11 - Media relayed by Skype for Business Media Relay in federated tenant

请注意:Note that:

  • 从联合 Skype for business 客户端到本地 Skype for Business 服务器的信号和媒体已超出本文档的范围。Signaling and media from the federated Skype for Business client to an on-premises Skype for Business Server is out of scope of this document. 但是,此处对此进行了明确说明。However, it is illustrated here for clarity.

  • 团队和 Skype for business 之间的信号由网关桥接。Signaling between Teams and Skype for Business is bridged by a Gateway.

  • 在此情况下,媒体将由 Skype for business 本地媒体中继中继到使用流2的客户网络。Media in this case is relayed by Skype for Business on-premises Media Relay to the customer network using flow 2. (请注意,"媒体中继" 中来自团队用户到远程媒体中继的流量最初将由媒体中继阻止,直到流处于相反方向。(Note that traffic from Teams user to the remote Media Relay in the federated customer network will be initially blocked by the Media Relay until traffic in the reverse direction starts to flow. 但是,双向流将以两种方向打开连接。)However, the bidirectional flow will open connectivity in both directions.)

直接(对等)Direct (peer-to-peer)

Microsoft 团队在线通话流程图12Microsoft Teams Online Call Flows Figure 12

图 12-直接(对等)Figure 12 - Direct (peer-to-peer)

团队混合拓扑Teams hybrid topology

此拓扑包括具有 Skype for Business 内部部署的团队。This topology includes Teams with a Skype for Business on-premises deployment.

Microsoft 团队在线通话流程图13Microsoft Teams Online Call Flows Figure 13

图 13-团队混合拓扑Figure 13 - Teams hybrid topology

  • 上图中箭头的方向反映了在企业外围环境中影响连接的通信的初始方向。The direction of the arrows on the diagram above reflect the initiation direction of the communication that affects connectivity at the enterprise perimeters. 在 UDP for media 的情况下,第一个数据包可能沿相反方向流动,但这些数据包可能会被阻止,直到其他方向的数据包才会流动。In the case of UDP for media, the first packet(s) may flow in the reverse direction, but these packets may be blocked until packets in the other direction will flow.

  • 团队与 Skype for Business Online 并排部署,因此客户将显示为 "团队/SFB 用户"。Teams is deployed side by side with Skype for Business Online, hence clients are displayed as "Teams/SFB user."

其他流(在团队拓扑之上):Additional flow (on top of Teams topology):

  • 流 5a –表示客户网络中的团队用户之间的对等媒体流和客户网络边缘的 Skype for business 本地媒体中继。Flow 5A – Represents a peer-to-peer media flow between a Teams user within the customer network and a Skype for Business on-premises media relay at the customer network edge.

使用案例:团队到 Skype for business 一对一Use case: Teams to Skype for Business one-to-one

客户网络中的混合Hybrid within the customer network

Microsoft 团队在线通话流程图14Microsoft Teams Online Call Flows Figure 14

图 14-客户网络中的混合Figure 14 - Hybrid within customer network

团队和 Skype for business 之间的信号由网关桥接。Signaling between Teams and Skype for Business is bridged by a gateway. 但是,媒体在客户网络中使用流量5进行直接对等路由。However, media is routed directly peer-to-peer within the customer network using flow 5.

具有外部 Skype for Business 用户的混合客户网络-由 Microsoft 365 或 Office 365 中继Hybrid customer network with external Skype for Business user – relayed by Microsoft 365 or Office 365

Microsoft 团队在线通话流程图15Microsoft Teams Online Call Flows Figure 15

图 15-使用外部 Skype for Business 用户的混合客户网络-由 Office 365 进行中继Figure 15 - Hybrid customer network with external Skype for Business user - relayed by Office 365

请注意:Note that:

  • 从 Skype for business 客户端到本地 Skype for Business 服务器的信号和媒体已超出本文档的范围。Signaling and media from the Skype for Business client to an on-premises Skype for Business Server is out of scope of this document. 但是,此处对此进行了明确说明。However, it is illustrated here for clarity.

  • 团队和 Skype for business 之间的信号由网关桥接。Signaling between Teams and Skype for Business is bridged by a gateway.

  • 媒体通过团队将中继传输到客户网络,通过流4进行中继。Media is relayed through Teams Transport Relay to the customer network through flow 4.

具有外部 Skype for Business 用户的混合客户网络-通过本地边缘进行中继Hybrid customer network with external Skype for Business user – relayed by on-premises Edge

Microsoft 团队在线通话流程图16Microsoft Teams Online Call Flows Figure 16

图 16-具有外部 Skype for Business 用户的混合客户网络-通过本地边缘进行中继Figure 16 - Hybrid customer network with external Skype for Business user - relayed by on-premises Edge

请注意:Note that:

  • 从 Skype for business 客户端到本地 Skype for Business 服务器的信号和媒体已超出本文档的范围。Signaling and media from Skype for Business client to an on-premises Skype for Business Server is out of scope of this document. 但是,此处对此进行了明确说明。However, it is illustrated here for clarity.

  • 信号由网关桥接。Signaling is bridged by a gateway.

  • Skype for business Media 中继中的 skype for business Media 中继将媒体通过媒体流5A 与客户网络中的团队用户进行中继。Media is relayed by Skype for Business Media Relay within Skype for Business on-premises Edge to Teams user within the customer network using media flow 5A.

具有手机系统直接路由拓扑的团队Teams with Phone System Direct Routing topology

此拓扑包括具有手机系统直接路由的团队。This topology includes Teams with Phone System Direct Routing.

直接路由允许您通过将支持的本地客户拥有的会话边界控制器(SBC)硬件设备与 Microsoft 365 或 Office 365 相匹配,然后将电话服务主干连接到该设备,从而使用第三方公共交换电话网络(PSTN)服务提供商。Direct Routing enables you to use a third-party Public Switched Telephone Network (PSTN) service provider by pairing a supported on-premises customer-owned Session Border Controller (SBC) hardware device to Microsoft 365 or Office 365, and then connecting the telephony trunk to that device.

若要支持此方案,客户必须部署经认证的 SBC,以便直接从 Microsoft 认证合作伙伴之一进行路由。To support this scenario, the customer must deploy a certified SBC for Direct Routing from one of Microsoft's certified partners. SBC 必须按照供应商的建议进行配置,并可通过 Microsoft 365 或 Office 365 进行直接 UDP 流量的路由。The SBC must be configured as recommended by the vendor, and be routable from Microsoft 365 or Office 365 for direct UDP traffic. 媒体可能直接从团队和/或 Skype for business 客户端传递到 SBC (绕过团队网关)或遍历团队网关。The media may flow directly from Teams and/or the Skype for Business client to the SBC (bypassing the Teams gateway) or traverse through the Teams gateway. 当主干配置为绕过团队网关时,与 sbc 的连接是基于 ICE 的,其中 SBC 支持 ICE,而团队/Skype for Business media 终结点支持 ICE 完整形式。The connectivity with the SBC, when the trunk is configured to bypass the Teams gateway, is based on ICE, where SBC supports ICE-Lite, while the Teams/Skype for Business media endpoint supports ICE Full Form.

Microsoft 团队在线通话流程图17Microsoft Teams Online Call Flows Figure 17

* 图 17-具有手机系统直接路由拓扑的团队*Figure 17 - Teams with Phone System Direct Routing topology

请注意:Note that:

  • 上图中箭头的方向反映了在企业外围环境中影响连接的通信的初始方向。The direction of the arrows on the diagram above reflect the initiation direction of the communication that affects connectivity at the enterprise perimeters. 在 UDP for media 的情况下,第一个数据包可能沿相反方向流动,但这些数据包可能会被阻止,直到其他方向的数据包才会流动。In the case of UDP for media, the first packet(s) may flow in the reverse direction, but these packets may be blocked until packets in the other direction will flow.

  • 团队与 Skype for Business Online 并排部署,因此客户将显示为 "团队/SFB 用户"。Teams is deployed side by side with Skype for Business Online, hence clients are displayed as "Teams/SFB user."

其他流(位于团队联机拓扑的顶部):Additional flows (on top of Teams online topology):

  • 流 4 " -表示从 Microsoft 365 或 Office 365 到客户网络的流,用于在云中的团队媒体服务器与在本地使用 SBC 建立连接。Flow 4' - Represents a flow from Microsoft 365 or Office 365 to the customer network, used to establish a connection between the Teams media server in the cloud with the SBC on premises.
  • 流 5b -表示客户网络中的团队用户之间的媒体流,在旁路模式下直接路由 SBC。Flow 5B – Represents a media flow between the Teams user within the customer network with the Direct Routing SBC in bypass mode.
  • 流 5c -表示在 PSTN hairpin 呼叫旁路模式下直接路由 sbc 与另一个直接路由 sbc 之间的媒体流。Flow 5C – Represents a media flow between the Direct Routing SBC to another Direct Routing SBC in a PSTN hairpin call bypass mode.

具有直接路由的内部用户(按团队传输中继的媒体中转)Internal user with Direct Routing (media relayed by Teams Transport Relay)

Microsoft 团队在线通话流程图18Microsoft Teams Online Call Flows Figure 18

图 18-直接路由的内部用户(按团队传输中继的媒体中转)Figure 18 - Internal user with Direct Routing (media relayed by Teams Transport Relay)

请注意:Note that:

  • SBC 必须具有可通过 Microsoft 365 或 Office 365 路由的公共 IP 地址。The SBC must have a public IP address that is routable from Microsoft 365 or Office 365.

  • 从 SBC 到 Microsoft 365 或 Office 365 的信号和媒体,反之亦然,使用流程4和/或流4。Signaling and media from the SBC to Microsoft 365 or Office 365 and vice versa use flow 4 and/or flow 4'.

  • 从客户网络中的客户端到 Microsoft 365 或 Office 365 的信号和媒体使用流程4。Signaling and media from the client within the customer network to Microsoft 365 or Office 365 use flow 4.

具有直接路由的远程用户(通过媒体服务器(MP)路由媒体Remote user with Direct Routing (media is routed through a media server (MP))

Microsoft 团队在线通话流程图19Microsoft Teams Online Call Flows Figure 19

图 19-使用直接路由的远程用户(通过媒体服务器(MP)路由媒体Figure 19 - Remote user with Direct Routing (media is routed through a media server (MP))

请注意:Note that:

  • SBC 必须具有可通过 Microsoft 365 或 Office 365 路由的公共 IP 地址。The SBC must have a public IP address that is routable from Microsoft 365 or Office 365.

  • 从 SBC 到 Microsoft 365 或 Office 365 的信号和媒体,反之亦然,使用流程4和/或流4。Signaling and media from the SBC to Microsoft 365 or Office 365 and vice versa use flow 4 and/or flow 4'.

  • 从 Internet 上的客户端到 Microsoft 365 或 Office 365 的信号和媒体使用流程3。Signaling and media from the client on the Internet to Microsoft 365 or Office 365 use flow 3.

内部用户直接路由(媒体旁路)Internal user Direct Routing (media bypass)

Microsoft 团队在线通话流程图20Microsoft Teams Online Call Flows Figure 20

图 20-内部用户直接路由(媒体旁路)Figure 20 - Internal user Direct Routing (media bypass)

请注意:Note that:

  • SBC 必须具有可通过 Microsoft 365 或 Office 365 路由的公共 IP 地址。The SBC must have a public IP address that is routable from Microsoft 365 or Office 365.

  • 从 SBC 到 Microsoft 365 或 Office 365 的信号,反之亦然,使用流程4和/或流4。Signaling from SBC to Microsoft 365 or Office 365 and vice versa use flow 4 and/or flow 4'.

  • 从客户网络中的客户端发送到 Microsoft 365 或 Office 365 的信号使用流程4。Signaling from client within the customer network to Microsoft 365 or Office 365 use flow 4.

  • 从客户网络中的客户端到客户网络内的 SBC 的媒体使用流程5B。Media from client within the customer network to SBC within the customer network use flow 5B.

具有直接路由的远程用户(由团队传输中继的媒体旁路中继)Remote user with Direct Routing (media bypass relayed by Teams Transport Relay)

Microsoft 团队在线通话流程图21Microsoft Teams Online Call Flows Figure 21

图 21-具有直接路由的远程用户(由团队传输中继的媒体旁路中继)Figure 21 - Remote user with Direct Routing (media bypass relayed by Teams Transport Relay)

请注意:Note that:

  • SBC 必须具有可通过 Microsoft 365 或 Office 365 和 Internet 进行路由的公共 IP 地址。The SBC must have a public IP address that is routable from Microsoft 365 or Office 365 and Internet.

  • 从 SBC 到 Microsoft 365 或 Office 365 的信号,反之亦然,使用流4和/或流4。Signaling from the SBC to Microsoft 365 or Office 365 and vice versa uses flow 4 and/or flow 4'.

  • 从 Internet 上的客户端发送到 Microsoft 365 或 Office 365 的信号使用流程3。Signaling from the client on the Internet to Microsoft 365 or Office 365 uses flow 3.

  • 从 Internet 上的客户端到客户网络中 SBC 的媒体使用流3和4,按团队传输中继进行中继。Media from the client on the Internet to the SBC within the customer network uses flows 3 and 4, relayed by Teams Transport Relay.

远程用户直接路由(媒体旁路直接路由)Remote user Direct Routing (media bypass direct)

Microsoft 团队在线通话流程图22Microsoft Teams Online Call Flows Figure 22

图 22-远程用户直接路由(媒体旁路直接路由)Figure 22 - Remote user Direct Routing (media bypass direct)

请注意:Note that:

  • SBC 必须具有可通过 Microsoft 365 或 Office 365 和 Internet 进行路由的公共 IP 地址。The SBC must have a public IP address that is routable from Microsoft 365 or Office 365 and the Internet.

  • 从 SBC 到 Microsoft 365 或 Office 365 的信号,反之亦然,使用流4和/或流4。Signaling from the SBC to Microsoft 365 or Office 365 and vice versa uses flow 4 and/or flow 4'.

  • 从 Internet 上的客户端发送到 Microsoft 365 或 Office 365 的信号使用流程3。Signaling from the client on the Internet to Microsoft 365 or Office 365 uses flow 3.

  • 从 Internet 上的客户端到客户网络中的 SBC 的媒体使用流2。Media from the client on the Internet to the SBC within the customer network uses flow 2.

直接路由(媒体旁路)-PSTN hairpin 呼叫(由于呼叫转发/传输)Direct Routing (media bypass) – PSTN hairpin call (due to call forward/transfer)

Microsoft 团队在线通话流程图23Microsoft Teams Online Call Flows Figure 23

图 23-直接路由(媒体旁路)-PSTN hairpin 呼叫(由于呼叫转发/传输)Figure 23 - Direct Routing (media bypass) - PSTN hairpin call (due to call forward/transfer)

请注意:Note that:

  • SBC 必须具有可通过 Microsoft 365 或 Office 365 路由的公共 IP 地址。The SBC must have a public IP address that is routable from Microsoft 365 or Office 365.

  • 从 SBC 到 Microsoft 365 或 Office 365 的信号,反之亦然,使用流4和/或流4。Signaling from the SBC to Microsoft 365 or Office 365 and vice versa uses flow 4 and/or flow 4'.

  • 从 PSTN 到 PSTN hairpinned 呼叫后,客户端不会发出信号和媒体循环。The client is out of the signaling and media loop after the call is hairpinned from PSTN to PSTN.

  • 从客户网络内的 SBC 实例 A 到客户网络(其中 A 和 B 可以是同一实例)内的 sbc 实例 B 的媒体使用流程5C。Media from SBC instance A within the customer network to SBC instance B within the customer network (where, A and B can be the same instance) uses flow 5C.

直接路由(通过 Microsoft 365 或 Office 365 的媒体)-跨两个租户的 PSTN hairpin 呼叫Direct Routing (media through Microsoft 365 or Office 365) – PSTN hairpin call across two tenants

Microsoft 团队在线通话流程图24Microsoft Teams Online Call Flows Figure 24

图 24-直接路由(通过 Microsoft 365 或 Office 365 的媒体)-跨两个租户的 PSTN hairpin 呼叫Figure 24 - Direct Routing (media through Microsoft 365 or Office 365) – PSTN hairpin call across two tenants

请注意:Note that:

  • SBC 必须具有可通过 Microsoft 365 或 Office 365 路由的公共 IP 地址。The SBC must have a public IP address that is routable from Microsoft 365 or Office 365.

  • 从 SBC 到 Microsoft 365 或 Office 365 的信号,反之亦然,使用流4和/或流4。Signaling from the SBC to Microsoft 365 or Office 365 and vice versa uses flow 4 and/or flow 4'.

  • 从 PSTN 到 PSTN hairpinned 呼叫后,客户端不会发出信号和媒体循环。The client is out of the signaling and media loop after the call is hairpinned from PSTN to PSTN.

  • 来自 SBC 实例 A (从客户网络 X 到 SBC 实例 B)内部的媒体必须通过 Microsoft 365 或 Office 365 媒体服务器进行中继,并且无法使用绕过模式。Media from SBC instance A within the customer network X to SBC instance B must be relayed through the Microsoft 365 or Office 365 Media Server and can't use bypass mode.

具有快速路线优化的团队Teams with Express Route optimization

Microsoft 团队在线通话流程图25Microsoft Teams Online Call Flows Figure 25

图 25-具有快速路线优化的团队Figure 25 - Teams with Express Route optimization

在显示和部署快速路由的情况下,团队流可以从流4重新路由到流1,从流 4 "重新路由到流 1"。In the case that Express Route is justified and deployed, then Teams flows could be re-routed from flow 4 to flow 1 and from flow 4' to flow 1'. 但是,团队应用程序对通过 Internet 的其他 Microsoft 365 或 Office 365 进行了硬依赖,使用流4和 4 ";因此,不能阻止这些流程。However, the Teams application has a hard dependency on other Microsoft 365 or Office 365 flows over the Internet using flows 4 and 4'; hence these flows must not be blocked.

请注意,Skype for Business 混合边缘流量将路由到 Internet,而不是快速路由以与外部用户通信并与其他租户联盟。Note that Skype for Business hybrid Edge traffic is routed to the Internet and not to Express Route to communicate with external users and federate with other tenants.

若要防止非对称流,重新路由必须在两个方向上。To prevent asymmetrical flows, re-routing must be in both directions. 换句话说,客户网络中的地址通过 Internet 或快速路由进行路由,基于优化,但不能通过这两者进行路由。In other words, an address within the customer network is routable either through Internet or Express Route, based on optimization, but not through both.

向外部用户的客户网络(按团队传输中继的媒体中继):Customer network to external user (media relayed by Teams Transport Relay):

Microsoft 团队在线通话流程图26Microsoft Teams Online Call Flows Figure 26

图 26-向外部用户(按团队传输中继的媒体中继)的客户网络Figure 26 - Customer network to external user (media relayed by Teams Transport Relay)

高级别步骤:High Level Steps:

  1. 客户网络中的团队用户使用 flow2 解析 URL 域名(DNS)。Teams User within customer network resolves URL domain name (DNS) using flow2.
  2. 客户网络中的 "团队用户" 使用流1分配团队传输中继的媒体中继端口。Teams User within customer network allocates a media Relay port on Teams Transport Relay using flow 1.
  3. 客户网络内的团队用户通过使用流1到 Microsoft 365 或 Office 365 的冰候选人发送 "邀请"。Teams User within customer network sends "invite" with ICE candidates using flow 1 to Microsoft 365 or Office 365.
  4. Microsoft 365 或 Office 365 使用流程3向外部团队用户发送通知。Microsoft 365 or Office 365 sends notification to external Teams user using flow 3.
  5. 团队外部用户使用流3在团队传输中继上分配媒体中继端口。Teams external user allocates a media Relay port on Teams Transport Relay using flow 3.
  6. 团队外部用户通过使用流3向返回到团队用户 A 的 ICE 发送 "应答"。Teams external user sends "answer" with ICE candidates using flow 3, which is forwarded back to Teams user A using Flow 1.
  7. 团队用户 A 和团队用户 B 调用 ICE 连接测试,并选择流1和3(由团队传输中继进行中继)。Teams User A and Teams User B invoke ICE connectivity tests and selects flows 1 and 3, which are relayed by Teams Transport Relay.
  8. 团队用户使用流1和3向 Microsoft 365 或 Office 365 发送遥测。Teams Users send telemetry to Microsoft 365 or Office 365 using flows 1 and 3.

备注

必须启用流4以支持团队应用程序依赖于其他微服务的依赖关系4。Flow 4 must be enabled to support dependencies of Teams application on other micro-services that mandates flow 4.