Accédez à votre compte, entretenez-le et faites-le évoluer à partir d’ici.
Rechercher
Communiquez avec nous
Envoyer un cas
La façon la plus rapide d'entrer en contact avec le bon spécialiste pour votre problème. Vous obtiendrez une réponse en moins de 48 h.
Communiquez avec nous
Rechercher des ressources
Envoyer un cas
Communiquez avec nous
VENTES
SOUTIEN

Utilisez-vous la dernière version de RingCentral?
Mettez à jour votre application maintenant pour profiter de la dernière expérience utilisateur, d’une protection améliorée et d’une qualité d’appel optimale.

Release Notes > Highlights > October 2024

Release Notes

October 2024 Release Highlights

Looking for another product? Explore full release notes here.

RingEX Core

Version 24.4 (Release date: October 30, 2024 to December 11, 2024)

Admin

  • Admins can now bulk delete unassigned extensions in Service Web.
  • Admins and end customers (Service Web MyExtension users) now have the ability to set caller ID for all phones or features at once.
  • Identifies Bring-your-own Devices (BYOD) as “BYOD” instead of “Purchased” devices across different fields in Service Web
  • Admins can now view Beetexting licenses in their account and can assign these licenses to respective users in Service Web.
  • Admins can also purchase Beetexting licenses via Service Web, however by default this feature will be turned off, and will be enabled later.

Call Handling

  • Customers can now set Caller ID Name (CNAM) on a per-number, per-site, or company-wide basis.
  • Better guidance and tools to help CNAM registration with the Free Caller Registry
  • Disable the ability for call queue members to change "Accept queue calls" availability status
  • Ability for Avaya J100 series phone users to change call queue status from the phone
  • Customers may now configure phone numbers to receive incoming SMS text messages without TCR registration.

Hardware and Firmware

  • Update to the default behavior for Mitel phones to prevent incoming intercoms / pages from automatically placing an active call on hold on the receiving phone. When there is an active call, the phone treats an incoming intercom call like a normal call and plays the call warning tone

Version 24.3.35 (Release date: October 8, 2024 to October 28, 2024)

Call Handling

  • SMS TCR registration enhancements including:
    • Easier to View Business Brand and Campaign IDs
    • Change to Canadian Customers business entity number entry.
    • Two-Factor Email Verification for Publicly Traded Brands.
    • Customized sample messages
    • New Privacy Policy & Terms Fields.
    • New Embedded Link Requirements
    • Easier Management of Brands & Numbers.

RingCentral Phone Firmware

Q4 2024 (Release date: October 23, 2024)

Please refer to tables below for release notes for firmware updates for specific phone models.

* Dates subject to change.

Vendor Model Firmware version Release Notes Start firmware rollout * Firmware rollout completed *

Mitel 

6800, 6900, 6900W

6.4 sp2

6.4 sp2 release notes

Dec 02, 2024

Dec 19, 2024

Avaya

J100 series

4.1.5

4.1.5 release notes

Oct 10, 2024

Oct 23, 2024

Yealink

T34W

124.86.25.6

T3 firmware release notes

Oct 10, 2024

Oct 23, 2024

Poly

Edge series

8.2.2

8.2.2 release notes

Oct 10, 2024

Oct 23, 2024

RingCentral web app

Version 24.4.10 (Release date: October 2024)

  • Persistent live transcripts: Persistent post-call transcripts for users who have been enabled for live transcripts but do not have AI notes permission
  • New voicemail setting entry point: Added “Voicemail settings” entry point directly in the UI where the user can access Voicemail

RingCentral Rooms

Version 24.4.10 (Release date: October 16, 2024)

  • See active speaker more clearly on dual screens: On dual screens, admins can now show or hide the video of the room in full-screen mode when the active speaker is in the room. This gives attendees a better view of the speaker.
  • Support for iPadOS 18: Rooms now supports the iPadOS 18 operating system for iPad controllers

RingCentral Events

Release date: October 7, 2024

  • HubSpot Integration - Engagement Signals & Import Registrants: New enhancements to our HubSpot Integration:
    1. Registrants instead of invitees: Organizers that use HubSpot forms to register people to their RingCentral Events will now see those registrants pass through to RCE as Registrants, instead of Invitees. Registrants with no RingCentral Events account tied to the email will receive a confirmation email that an account has been created for them (which also includes the details of how to remove that account).
    2. Engagement signals: Organizers will start receiving data points about their attendee’s engagement. Customers can turn on or off syncing this data from the HubSpot App configuration window found in the RC Events Organizer Dashboard. With this launch, the option will be ON by default, so that data can start flowing on day one.

      Syncing affects all events and cannot be configured for each event individually. After enabling the option in the app configuration wizard, syncing will be turned on for all existing (ongoing or future) events, and will be applied to newly-created events as they appear. Note that for ongoing events data/activities will be synced only after the option has been turned on. Previous activity data is not synced. The same applies to events which had already ended.Turning the feature off after having it on will prevent timeline events from reaching HubSpot.

      Signals that will be available as Lead Timeline updates in HubSpot:
  • Attended event
  • Attended Virtual Area
  • Time spent in an event area
  • Attended Onsite Area
  • Clicked CTA
  • Chat message sent
  • Asked a question
  • Voted in a poll
  • Lead scan (for Onsite)
  • Booked a meeting
  • Clicked Expo Booth URL

The API should accept the following fields in the request body for partial updates:

  • firstName (Optional, string)
  • lastName (Optional, string)
  • headline (Optional, string)
  • ticketId (Optional, string)
  • externalBarcode (Optional, string)
  • answers (Optional, Array of Objects)

Response Codes:

  • 200 OK: Registration is successfully updated, returning the updated registration details.
  • 400 Bad Request: Returned if invalid data is provided in the request body.
  • 404 Not Found: Returned if the provided registrationId does not exist.
  • 422 Unprocessable Entity: Returned if syntactically correct data is semantically invalid (e.g., answers do not match expected questions).
  • 500 Internal Server Error: Returned in case of unexpected server errors.

RingSense

Q4 2024 (Release date: October 2024)

Introduced the following feature:

  • Revamped Filters and Saved Views UI: We've revamped our Filters and Saved Views features to make searching for calls that deserve your attention easier than ever:
    • Improved UI: A more intuitive and user-friendly interface for both features
    • New Pinning Feature: Keep your most important views front and center
    • A new ReviewedBy filter

See KB here.

  • Data Retention Policy: This new UI in Admin Settings gives you greater control over data management, helping you align with your organization's policies and compliance requirements. Administrators can now set preferred retention periods for:
    • Call recordings
    • Transcripts
    • Conversational intelligence data

See KB here.

  • Integrations
    • Zapier Integration: Leverage the power of RingSense data across your entire tech stack. Whether using our API directly or through Zapier, easily integrate conversational insights into your existing tools and processes. Access new trigger here
  • Access RingSense data through the new trigger in the RingCentral Zapier app.
  • Seamlessly connect with hundreds of apps through Zapier integration
  • Automate workflows and sync data without coding
  • Dynamics 2-ways Sync: The integration with Microsoft Dynamics is expanded: RingSense can write its data into the CRM.Write CRM integration from RingSense to Zendesk Sales, learn more about integrations in RingSense here.

RingCX

Release date: October 2024

RingCX

  • The IVA framework now supports SIP integration with third-party IVAs, including Cognigy.
  • RingCX now includes RingEX queue extensions in the corporate directory, allowing users to dial or transfer calls directly to queues.
  • Agents can send outbound chat messages directly from RingCX using APIs, making it easier to follow up on service issues, answer questions, and resolve problems.
  • Agents can preview multiple images and videos from emails, chats, and texts while composing a reply. Because images are available for preview, admins can now choose to restrict downloads on agents’ local devices.
  • Emoji widgets in RingCX have been upgraded to the same library used by RingEX, adding emoji search, skin tones, an expanded emoji library, and keyboard shortcuts.

Analytics

Reports

  • Agent Login Time Tracking Details: Shows agent first login time and last logout time per calendar day, along with durations of agent states.
  • Agent Speed of Answer: Shows the average speed of answer by agent and overall per contact center. 
  • DNIS Inbound Overview: Shows the number of inbound interactions per DNIS number. Interaction details include DNIS description and time averages.
  • Interactions Overview: Shows all incoming and outgoing interactions including their metrics and handling resources, for a holistic view and analysis of contact center activities.

Metrics

  • Agent SOA: Average time it takes agents to answer voice interactions.
  • A large set of trend and forecast related metrics have been introduced for inbound and outbound interactions.
  • New metrics have been added to track the numbers and durations of various base states for contact center agents.

Attributes

  • Agent Locale: Displays the locale setting of the agent interface showing the agent’s preferred language (reserved for internal use).
  • Brand ID: Partner’s brand ID used for billing and integration.
  • Brand Name: Partner’s brand name used for billing and integration.
  • Sub Brand ID: Partner’s brand division ID used for billing and integration.
  • Sub Brand Name: Partner’s brand division name used for billing and integration.
  • Connected Route Destination ID: Displays a phone number or SIP address of the agent’s login extension.
  • DNIS Description: Displays the DNIS description if defined in the phone number settings; helps to identify interactions with the same DNIS description and group them for reporting purposes.
Archives
Thanks!
We've sent you a link, please check your phone!
Please allow a full minute between phone number submissions.
There was an issue with SMS sending. Please try again. If the issue persists, please contact support.