Can anyone clarify the specific threshold logic governing SIP trunk registration timeouts as displayed in the Performance Dashboard for our EU-West BYOC environment.
The current configuration invokes a standard 30-second timeout for trunk registration checks, yet the dashboard frequently reports timeouts exceeding 45 seconds without correlating to actual call failures. This discrepancy complicates the analysis of telephony reliability metrics for executive reporting.
Environment Details:
- Region: EU-West BYOC
- Module: Telephony Performance Dashboard
- Metric: SIP Trunk Registration Timeout
- Expected Threshold: 30 seconds
- Observed Variance: 35-50 seconds
The underlying SIP trunks are functioning correctly, and no packet loss is detected via network monitoring tools. However, the Performance Dashboard continues to flag these intervals as critical errors. This creates a false negative in our service level agreement (SLA) compliance reports.
Is there a known caching delay or aggregation window within the Performance Dashboard that causes this latency in metric reporting? Alternatively, does the dashboard utilize a different timeout parameter than the one defined in the Telephony configuration settings? Understanding this variance is critical for accurate capacity planning and vendor accountability discussions.