微软 Teams Guest join 呼叫可能无法从 Google Meet 硬件设备连接
Issues轻微事件
受影响的组件
Connect for Google Rooms
- investigating
我们正在调查微软团队Guest Joint电话在从Google Meet硬件设备拨打时可能无法连接的报告.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
55 Pexip incidents · 2024年8月 — official updates, affected components, duration and resolution details.
我们正在调查微软团队Guest Joint电话在从Google Meet硬件设备拨打时可能无法连接的报告.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
Cisco 端点为: 已登记在出入境事务处,并更新为26.9或26.10 可能无法通过 Teams CVI 或 Google Meet Gateway 服务从远端接收到电话演示。 据报告,发送演示文稿是有效的,而且还解除了对即将收到的演示文稿的封锁。 我们建议你不要在调查时 把思科系统更新到26.9或26.10 请将任何受到影响的系统推回26.8,同时我们确定原因.
我们已经确定了与Cisco如何保持演示文稿频道活力有关的一个变化,并且正在计划更新以适应这些变化.
我们已把这一问题与新的RoomOS版本联系起来,并已开始推出一个固定方案。 推出期间可能会有轻微中断,少数电话可能会受到影响. 为此,将在各区域的工作时间之外展开.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
目前,Pexip服务(help.pexip.com)和Infinity(docs.pexip.com)的文档页间歇性停用。 对于一些用户来说,页面要么加载缓慢,要么没有响应.
我们的服务提供者正继续努力解决这一问题。 服务帮助页面 (帮助.pexip.com)已恢复,现可访问. 无穷文献网页(docs.pexip.com)仍然没有,我们正在积极监测一项解决办法.
这个问题已经解决,现在又可以查阅文件页.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个问题 分析 的Pexip控制中心。 可能没有使用数据.
我们的小组正在继续调查波西普控制中心影响分析的问题。 在工作进行期间,可能仍无法获得一些使用数据。 一旦掌握了更多信息,我们将提供进一步的最新资料.
一项措施已经执行,我们正在监测结果.
没有报告或观察到其他问题。 这一事件现在已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个没有从伙伴门户和控制中心发送电子邮件的问题.
问题已经查明并已解决.
这一事件已经得到解决.
自动翻译自官方事件更新。
Between Monday 8 June, 15:15 and Wednesday 10 June, 11:00 (UTC), users were unable to create One-Time Rooms (OTR) using the Pexip Service Outlook Add-In. Personal VMRs and previously scheduled One-Time Rooms were not affected. The issue has been resolved and scheduling of One-Time VMRs via the Outlook Add-In is now functioning normally. This incident is being logged retroactively after resolution.
We detected incoming SIP call failures in the Oregon Point of Presence (PoP) and are currently investigating the issue.
As a mitigation step, we have re-routed incoming SIP calls to an alternative location. This change is intended to resolve the impact while we continue investigating the issue in the Oregon PoP.
We have identified an issue with an unavailable infrastructure component that caused some SIP Teams CVI calls to fail in Oregon and are actively working to resolve the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Incoming SIP call handling has been restored to its normal operating configuration.
We are investigating an issue causing calls to appear with a delay on the Diagnostics Page in Pexip Control Center.
We have implemented a fix to address delayed call visibility on the Diagnostics Page in Pexip Control Center. Some delay may persist while the system clears existing backlog. We are actively monitoring.
Currently diagnostics are unavailable in PCC. We continue to work to bring this feature online.
We are continuing to monitor for any further issues.
The issue affecting the Diagnostics page has been resolved and we are monitoring system behavior. Some delay in data appearing on the Diagnostics page may persist while the system clears the existing backlog.
This incident has been resolved.
The issue can be seen on meetings where a Teams recorder bot is present. The unknown participant represents a new version of the Teams recording bot. We are working to block visibility of this new bot in the layout ASAP.
Further explanation: The unknown teams participant (in some layouts, shown as the "t8" participant avatar) can appear to the Video Conference (CVI) participant, when a "Teams Consumer" user joins the meeting. The "t8" participant represents the Teams Consumer meeting recording bot, and should not be visible to the Video Conference (CVI) participant. There is no impact on meetings when only Teams Enterprise / Commercial / Business users are present.
We've already seen a reduction in the Teams Consumer recorder bots being added to meetings, and therefore the "t8" unexpected user is now very rarely seen on screen. A fix will be applied to the service within the next few weeks.
This incident has been resolved.
We are investigating an issue where calls from the Pexip app for iOS to Pexip Service VMRs are ending prematurely. Affected customers should use the My Meeting Video (MMV) iOS app, now available for download at https://apps.apple.com/us/app/pexip-my-meeting-video/id1018923867
The issue has been identified and a mitigation is being deployed within the service.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
The issue is now resolved.
We are currently investigating an issue affecting some Microsoft Teams CVI connections, where calls may intermittently fail.
Errors from Microsoft Teams have been identified and are tied to Microsoft issue TM1286773. We are coordinating with Microsoft and are monitoring closely.
We have not observed any errors for the past few hours. We will continue to monitor the situation closely.
No further issues have been observed or reported. This incident has been resolved.
Pexip documentation web pages are currently unavailable due to an outage with a service provider. This outage affects both help.pexip.com and docs.pexip.com web sites. The provider is currently investigating the cause of this outage and working a fix.
Service has been restored for both help.pexip.com and docs.pexip.com documentation pages. We will continue to monitor service availability.
This incident has been resolved.
The team is currently investigating the issue.
A small number of Zoom Connect for Teams CVI calls in Europe might have failed to bypass the lobby. A fix has been implemented, and we're monitoring the results.
This incident is resolved.
We are investigating a packet loss issue occurring between Cisco Webex and Pexip that is affecting calls from Webex-registered endpoints located in India. Participants connecting from their Webex devices may experience degraded call quality in the direction from the device to Pexip.
The previously observed packet loss affecting calls between Webex-registered endpoints in India and Pexip is no longer occurring and has remained stable for a period of time. Based on available data, the issue appears to have been related to factors along the public internet path. We continue to monitor the situation to ensure call quality remains stable.
This incident has been resolved.
We are investigating an issue where some CVI calls in the US region are failing.
A fix has been applied and we are monitoring the results.
This incident has been resolved.
We have identified an issue affecting Pexip Android and iOS mobile app users. In some cases, users are unable to join Pexip hosted one-time Virtual Meeting Rooms (VMRs) directly from the in-app Calendar when the meeting is scheduled via the Pexip Service Outlook Plug-in. New mobile app versions are planned for release in the coming days to address this issue. In the meantime, users can join meetings by selecting the Address option in the app and manually entering [email protected] URI.
The Android app version 1.1.3 is now available and includes changes that address this issue. We are continuing work on the iOS version.
IOS app version 1.1.4 is now available and includes changes that address this issue.
This incident has been resolved.
We are currently investigating an issue where Teams SIP Guest Join calls fail to connect when using 15-digit meeting IDs. Users attempting to join these meetings from SIP devices, Zoom, or Google Rooms may fail to connect.
A fix has been implemented for the issue. Teams Guest Join calls with 15-digit meeting IDs should now connect successfully. Customers running the "Pexip Ad Hoc Join for Teams on Cisco endpoints" (https://help.pexip.com/macros/ad-hoc-join-teams.htm) need to update the msteams-macro-settings.js file to ensure the regex supports meeting IDs longer than 14 digits.
This incident has been resolved.
We have observed an issue where some Zoom Rooms might fail to bypass the Teams lobby. Out Team is looking into it.
We have found the issue and resolved it.
Between 12:01 and 12:04 UTC on March 17, some calls within the Pexip Service may have experienced failures. The issue has been resolved and the service is operating normally. We will continue to monitor.
We have observed a Cloud OTJ issue affecting some M365 mailboxes. Our Team is looking into it.
We have contacted Microsoft to investigate this issue together with them.
We have identified an issue affecting some Microsoft 365 tenants. The impact has been traced to a third-party application making mailbox queries through the Microsoft Graph API, which may result in degraded performance or unexpected behavior in Pexip Cloud OTJ. Customers experiencing issues with Cloud OTJ are advised to open a support ticket so our team can review their environment and provide additional details and guidance.
We have completed our investigation and found no issues within Pexip Cloud OTJ. Some Microsoft 365 tenants may experience degraded performance caused by mailbox activity from third party applications using the Microsoft Graph API. Customers still experiencing Cloud OTJ issues should contact support for further investigation and guidance.