Microsoft Teams Guest Join 통화는 Google Meet 하드웨어 장치에서 연결할 수 없습니다
- investigating
우리는 Microsoft Teams Guest Join 통화가 Google Meet 하드웨어 장치에서 다이얼을 때 연결할 수 없다는 조사 보고서입니다.
- monitoring
수정이 구현되어 결과를 모니터링하고 있습니다.
- resolved
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
55 Pexip incidents · 2024년 8월 — official updates, affected components, duration and resolution details.
우리는 Microsoft Teams Guest Join 통화가 Google Meet 하드웨어 장치에서 다이얼을 때 연결할 수 없다는 조사 보고서입니다.
수정이 구현되어 결과를 모니터링하고 있습니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
Cisco 엔드포인트: Pexip 서비스에 등록하고 26.9 또는 26.10로 업데이트되었습니다. 5월 팀 CVI 또는 Google Meet Gateway 서비스를 통해 통화로 먼 끝에서 프레젠테이션을받지 못했습니다. 발표를 전송하는 것은 일하고, 또한 들어오는 발표를 막습니다. Cisco 시스템을 26.9 또는 26.10으로 업데이트하지 않는 것이 좋습니다. 우리는 원인을 설정하면서 26.8로 어떤 영향을받는 시스템을 구하십시오.
우리는 Cisco가 프리젠 테이션 채널을 살아가는 방법에 대한 변경을 확인했으며 변경 사항에 맞게 업데이트를 계획하고 있습니다.
우리는 새로운 RoomOS 버전으로 문제를 확인하고 수정을 시작했습니다. 민들레 붕괴는 롤아웃 중에 가능하며, 통화의 작은 수는 영향을 미칠 수 있습니다. 그 이유를 들어, 롤아웃은 각 지역의 영업 시간 밖에 수행됩니다.
수정이 구현되어 결과를 모니터링하고 있습니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
Pexip는 현재 서비스 (help.pexip.com) 및 Infinity (docs.pexip.com) 문서 페이지에 대한 간헐적 인 정전을 경험하고 있습니다. 페이지는 일부 사용자에 대한 로드 또는 응답으로 느립니다.
우리의 서비스 공급자는 이 문제점을 해결하기 위하여 계속됩니다. 서비스 도움말 페이지 (help.pexip.com)는 복구하고 이제 액세스 할 수 있습니다. Infinity Documentation 페이지(docs.pexip.com)는 사용할 수 없습니다.
문제는 해결되었습니다. 문서 페이지는 다시 접근 할 수 있습니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
현재 Pexip Control Center의 Analytics에 대한 문제점을 조사하고 있습니다. 몇몇 사용법 자료는 유효하지 않을지도 모릅니다.
우리의 팀은 Pexip Control Center의 Analytics에 영향을 미치는 문제를 조사하기 위해 계속됩니다. 일부 사용 데이터는 여전히 작동 중에 사용할 수 없습니다. 우리는 더 많은 정보를 한 번 더 업데이트 할 것입니다.
수정이 구현되어 결과를 모니터링하고 있습니다.
더 이상 문제가 보고되었거나 관찰되지 않았습니다. 이 사건은 이제 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
파트너 포털 및 Control Center에서 이메일이 전송되지 않는 문제가 있습니다.
문제가 식별되고 해결되었습니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
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.