The Dialpad conferencing integration's URL regex only accepted
alphanumeric characters in the meeting room path ([a-zA-Z0-9]+),
causing valid personal meeting URLs containing hyphens, dots, or
underscores to fail validation.
For example, https://meetings.dialpad.com/mmit-russ is rejected
despite being a valid Dialpad personal meeting link. The sample URL
shown in the error message (alphanumeric only) passes, but
real-world room names commonly use hyphens and other characters.
Updated the urlRegExp character class from [a-zA-Z0-9] to
[a-zA-Z0-9._-] to match all valid Dialpad meeting room slugs.
Fixes issue introduced in #15444.
Co-authored-by: Sahitya Chandra <sahityajb@gmail.com>
* chore: Add Sentry perf tracing
* Just to build
* perf: Add Sentry perf tracing
* Removed the extra integrations tracing config
* Got spans working
* Now only tracing individual endpoints
* Removed check for booking event type
* Fixed types
* Added back for spans
* Consolidate sentry imports
* Added more traces
* Moved the start of the span
