TeamHub V3.7.1 - Release Notes - January, 2025
Release Overview
This release delivers several usability upgrades and stability improvements across Operator Console, Talk, Contacts, Call Handling, and Call History. Highlights include a new ringer-silencing option, better Contacts behavior, more accurate Unattended Calls reporting, improved parked call visibility, and a series of transfer-related fixes. The updates enhance daily workflows and ensure a more consistent, reliable experience for both CommUnity and Business Voice platforms.
New Features:
| Business Voice | CommUnity |
|---|---|---|
Operator Console - Silence ringer on incoming call cards Operators can temporarily mute ringtones for incoming call cards while still keeping the call visible and answerable. | ||
Operator Console - Contacts default view preference Users can now set tiles or list as their preferred Contacts view, retained across sessions and devices. For more details on the Operator Console functionality and features, refer to the TeamHub Operator Console User Guide |
|
Key Improvements and Fixes:
| Business Voice | CommUnity |
|---|---|---|
Operator Console - Dialpad and UI polish
| ||
Talk and Operator Console - Improved settings reliability Talk Settings, including audio, load more consistently after network drops or app reloads. | ||
Operator Console - Unattended Calls and Call History
| ||
Operator Console - Attended transfers to virtual extensions More reliable behavior and no disappearing “Complete transfer” option. |
| |
Operator Console - Prevented early transfer completion The “Complete transfer” button is disabled until the destination answers. |
|
|
Operator Console - Corrected false missed calls on warm transfers Warm transfers to queues or virtual extensions that are eventually answered no longer generate missed or unattended entries. |
| |
Converted conferences – Mute controls Moderators can reliably use “Mute All” or mute individual users. | ||
New channel creation UI (Desktop) The “Create channel” dialog no longer shows nested or duplicated text fields. |
|
Return to Documentation Home | Sangoma Support