Bria Softphone Support: Resolution Expectations & Time-Zone Constraints
Overview
When a Bria Softphone issue requires input from the upstream vendor (Bria / CounterPath), resolution timelines extend beyond our standard support response. This article explains why that is, what realistic timeframes look like, and how we communicate with you during vendor escalations.
Why time zones matter
Bria operates out of North America, which gives us a narrow overlap window with their engineering team (early AU morning / late US business day). In practice, any escalation that requires Bria's input typically incurs at least a one-business-day round-trip.
Realistic resolution timeframes when vendor input is required
For issues where we need vendor-side investigation, please expect resolution to take 1–3 business days longer than a purely Comms Channel-side issue.
Examples of issues that typically require vendor escalation
- Server-side problems (Bria-hosted services, login/authentication, push notification delivery)
- Version-specific bugs that we cannot reproduce on a clean configuration
- New iOS or Android OS compatibility issues following a major OS release
- Crashes that require analysis of a
.dmpfile by Bria engineering - Provisioning or licensing anomalies tied to Bria's backend
Issues outside this list — for example, account configuration, SIP credentials, dial plan changes, or call quality issues that trace to your local network — are usually resolved by our Voice team directly within our standard support response window.
How we communicate during vendor escalations
While we work with Bria on your behalf, we will keep the ticket updated as the back-and-forth happens. Importantly, this includes flagging when we're waiting on Bria so the silence isn't unexplained — you'll always know whether we're actively working the issue or waiting on a vendor response.
Key Notes
| Item | Details |
|---|---|
| Bria vendor location | North America |
| Overlap window | Early AU morning / late US business day |
| Vendor escalation round-trip | Minimum one business day |
| Additional resolution time when vendor input is required | 1–3 business days on top of standard turnaround |
| Status updates | Ticket will be updated as the back-and-forth happens, including flagging when we're waiting on Bria |
Related Articles
- Sending Bria Softphone Logs to Comms Channel Support — how to send logs and report issues when you encounter a problem.
- Bria Softphone App: Build & Release Process — timeline and direct download access for new Bria releases.
