What do you dislike about Pexip?
During high peak webinar traffic, I've noticed occasional metadata drop-offs when forwarding logs to Splunk SIEM. Troubleshooting legacy H.323 endpoint glitches also lacks granular built-in diagnostic tools. I need to pull separate debug dumps manually, which adds extra labor, especially during busy HIPAA audit-prep cycles. Onboarding our fleet of older SIP/H.323 lab room endpoints required a lot of manual tuning, and configuring recording purge rules and Splunk SIEM log forwarding took careful work to get everything HIPAA-ready before our audits. Review collected by and hosted on G2.com.
Recommendations to others considering Pexip:
To enhance the user experience, consider implementing more robust diagnostic tools for legacy H.323 endpoints and improving metadata handling during peak traffic. Streamlining the onboarding process for older hardware and simplifying the configuration of recording purge rules could also be beneficial. Review collected by and hosted on G2.com.
What problems is Pexip solving and how is that benefiting you?
Pexip bridges our legacy video hardware with Microsoft Teams, unifying communication across campuses and simplifying audit prep with robust logging. It prevents costly hardware refreshes and eases regulatory compliance with flexible workflows for confidential meetings. Review collected by and hosted on G2.com.