David

Hi all.  As noted in the documentation there are instances where gaps or spaces may occur from the html.
Where can I use Markdown and HTML in Zendesk Support



So, if you “minify” your code this should work. Minifying basically means is you just squish it all together in one long string. 
So in the example from this posting, it would look like this instead:  (this should remove any line breaks)

问题

我已按照此文章中的说明进行了 Twilio 网络测试。但是，我不确定如何读取结果。如何使用 Twilio 网络测试对 Zendesk Talk 专员通话进行故障排除？

回答

大多数 Talk 或网络电话 (VOIP) 问题都与网络连接的速度、稳定性和质量有关。快速连接并不足以开启实时语音通信。数据包丢失或连接不稳定也会导致问题。

执行 Twilio 网络测试以了解您的连接是否正常。该测试可确保您的使用符合要求，例如网络正常、端口开放、浏览器支持通话，以及麦克风和扬声器功能正常。

Twilio 网络测试分为左右两栏：

• Twilio WebRTC 诊断
• 日志输出

Twilio WebRTC 诊断

对于上述所有测试，结果应显示绿色的通过消息。红色的失败消息表示可能存在网络问题，尤其是在遇到 UDP、TLS 或 TCP 错误时。

• 如果专员在办公环境中工作，则发生这些错误的原因可能是某些内容被阻止。确保您的网络团队遵循 Talk 网络要求，已打开端口并将 IP 地址和域名加入白名单。
• 如果这是专员的家庭网络，请确保其没有特殊设置或家庭路由器阻止端口，可能需要对其网络进行进一步调查。

日志输出

Twilio 网络测试的右栏包含日志输出。

以上屏幕截图引用了以下元素：

• 确保以下日志显示为绿色。红色表示故障。
  • A) 已在 ___ ms 内成功建立到 Twilio 的 UDP 连接
  • B) 已在 ___ ms 内成功建立到 Twilio 的 TCP 连接
  • C) 已在 ___ ms 内成功建立到 Twilio 的 TLS 连接
• D) 确保您即使可以成功通过带宽测试，结果也远高于上面的例子。其中，结果表示 Talk 可靠工作的最低阈值。
  注意：测试中的数字是 Talk 的最低阈值。
• E) 检查连接到审核的 Twilio 客户端，并确保连接的端点正确。虚拟专用网络 (VPN) 可能将您连接到错误的端点，例如您在德国，但日志显示您连接的是美国端点。连接到错误的端点会导致延迟。Twilio 应决定哪种路由为最佳路由，但 VPN 可能会隐藏专员的真实位置或区域。区域可以是以下之一：au1、br1、de1、ie1、jp1、sg1、us1。有关 Twilio 区域的最新信息，请参阅 Twilio 文章：旧版区域。
• F) RTT（往返时间）：理想情况下，RTT 应为 150ms 或更短。RTT 值越高，通话质量可能越差。
• G) 抖动：抖动审核不应超过 20ms。高抖动可能导致延迟。
• H) 丢包：数据包丢失表示连接不稳定，即使 1% 的数据包丢失也可能造成问题。

Hey all.  Just want to clarify the screenshot above  is not meant to be used as an exact benchmark.  I would say this is an ideal setup above.  If you run this test where it "passes" this is not necessarily indicative of what one would call a quality connection. For example at a minimum I would say for the above, you would want your "lowest" amounts for the above "Simultaneous connections" should be at least 10 or more.  Packet loss should be 0, jitter should be low, etc. If your getting packet loss, jitter and your lowest amount of simultaneous connections is 2, you may pass this test barely but your calls are likely to have a lot of problems.   

the graphic is just an illustration of what the test looks like and what to be aware of during the test.  As Jeff mentions above getting better results on your network connection has a wide variety of factors.  The best place to start is with our Talk troubleshooting guide below which has many suggestions like changing to a hard wired connection like Jeff mentioned or running network tests and working with your network admin.

https://support.zendesk.com/hc/en-us/articles/203661086-How-can-I-troubleshoot-Talk-issues- 

It's my opinion the majority of problems we see are related to VPN or VDI implementations.  Make sure you follow the advice in the networking requirements regarding VPN's.  I.E. make sure to exclude traffic for Twilio and Zendesk ips and domains:

In scenarios where using a proxy, MPLS, or VPN is unavoidable, it's crucial to exclude traffic intended for Zendesk and Twilio domains, including your FQDN subdomain.zendesk.com, and the specified IP addresses outlined in the accompanying documentation. This exclusion is critical to ensure the proper functionality of Talk within these network configurations.