Is bvoip down?

We are aware of a Microsoft posted outage for Exchange online. You can see this is being reported in several places. https://www.bleepingcomputer.com/news/microsoft/microsoft-exchange-online-outage-causes-email-failures-auth-issues/ 1. If you are emailing 1Stream, it is likely your messages are not reaching us for sales, support, etc. Our systems are online but email is likely not being deliveed. 2. If you use M365 for outbound email from your 1Stream account for things like alerts, voicemail-to-email, etc it is likely that those messages are not being sent.

We are seeing delayed email starting to pour in from approx noon eastern time today when the Microsoft 365 / Exchange Online outage started. We will continue to monitor has all Microsoft services are back to 100%.

We were notified by several there were experiencing login loops when trying to sign-in within the last 30 minutes. We also received some reports that certain portal pages were not responding. We have refreshed all systems and all should be working properly. You may need to refresh your browser sessions CTRL + R.

This is a retroactive incident post. Our data center vendor in Los Angeles advised us there was a partial connectivity outage in Los Angeles has been since been resolved, The issue started at 11:34pm and resolved as 3:04 Los Angeles time. Total duration of the issue was 3 hours and 40 minutes. This is what was reported to us: The incident was caused by a hardware failure in one of the network devices serving the affected servers. The faulty component was replaced, and an additional software adjustment was required during the recovery process before normal operation could be restored.

We have received several reports from accounts using calling plans on siptrunk.com / flowroute / nexvortex. This is a carrier side issue and we have escalated to our tier 3 escalation path with bcmone. We are found that specifically for siptrunk.com these settings changes provide some help Changing the gateways in use from gw1.siptrunk & gw2.siptrunk to gw4 and gw5 respectively Disabling the trunk setting Option "PBX delivers audio"

Update from siptrunk.com Thank you for this information. I have further escalated the matter to our Development and Engineering teams, and they have advised that they are currently aware of internal issues that could potentially be impacting RTP audio traffic and preventing audio packets from passing correctly. Our teams are actively investigating the issue and reviewing whether the reported symptoms align with the behavior currently being observed internally. At this time, this appears to be the most likely area of focus based on the information available. We will continue to monitor the situation closely and coordinate with the appropriate teams. As soon as we receive additional findings or confirmation regarding the root cause and resolution, I will provide you with an update promptly. Thank you for your patience and cooperation while we work through this investigation.

Latest from siptrunk.com / bcmone Thank you for your patience while we worked through this intermittent audio issue. The root cause was particularly challenging to identify because the affected calls were traversing multiple gateways, making it difficult to isolate a common factor. After gathering additional call examples from other customers and escalating the matter to our Development team, we determined that the issue originated within our network. An internal loop was causing audio traffic to consume an excessive number of ports, which resulted in the audio disruptions being reported. Our Development team implemented corrective changes at 1:30 PM EDT, and since those updates were made, customers have reported noticeable improvements in call audio quality. At this time, we ask that you continue to monitor and retest your services and let us know if you experience any further issues so we can confirm the matter has been fully resolved.

Closing incident

We had a relatively quiet morning but we have had some new reports of inbound calling issues that point back to BCM one again. We have captured some examples and sent them back to their team for review.

Update from bcmone / siptrunk.com our Development Engineering team informed me that they have implemented an additional internal change intended to alleviate the inbound and outbound audio issues that have been occurring. At this time, please retest and continue to monitor your calls to confirm that audio is now passing properly in both directions and that the issue has been resolved. If you continue to experience any problems, please provide new call examples and we will be happy to investigate further.

We received some reports of users not being able to sign in via the control portal SSO with User Not Found. We have identified and remediating this issue.

All sign-in issue seem to be resolved at this time. Switching this incident to monitoring