Release 1.2.94

Modified on Tue, Feb 25 at 12:18 PM


Ooma Release Notes  

Version 1.2.94 (February 24, 2025)  


Overview:  

It’s been about a week since our last release, and we’re back with another update. The 1.2.94 version brings new features, bug fixes, performance enhancements, and some code cleanups.


New Features:  

  • IP Phone Provisional Enhancements:
    • New “Assign To:” Field (Nemo-2381): introduced a new field in the Device creation/editing process, enabling dynamic management of the new nested SIP device types.
    • Removed Default SIP Device Creation (Nemo-2380): adding new Seats will no longer automatically create a default SIP Device, giving users more control.
    • SIP Device Nested Structure (Nemo-2385): implemented a parent-child hierarchy where “SIP Device” is the parent, with nested device types:
      • New: takes users to the New SIP Device creation flow.
      • Unassigned: opens the “Select Unassigned Device” dialog

Additionally, devices can now be created without being assigned to a user.

  • SIP Device Nickname (Nemo-2383): if a user does not set a SIP device nickname, it will now default to the format: <make>_<model>_<last 6 digits of MAC address>.
  • Device Filtering (Nemo-2386): added a filtering feature to the Devices tab in the Phone System App, making it easier to locate devices.


Improvements:  

  • Seat Management Updates (Nemo-2389): added the auto-population of several fields during seat creation or editing:
    • Outbound Calls: caller ID Name and Number fields now inherit values from the account level unless manually populated.
    • In-House Calls: caller ID Name and Number fields inherit values from the account level unless already set.
  • Emergency Calls: caller ID Name and Number fields are no longer required, so the mandatory * has been removed.
  • Caller ID Field Validation (Nemo-2435): the field now accepts the E.164 format but allows input without +1, which is automatically added on the back end.
  • Codebase Improvement (Nemo-2374): schema objects in Models have been relocated to dedicated schema.ts files for better structure.
  • Developer Experience Enhancement (Nemo-2373): standardized API response imports for improved developer experience — now, using import { defaultAPIResponseSet } from ‘shared/utility/testing/mocks/dataset’;
  • Security Enhancement (Nemo-2427): yarn audit has been added to the pipeline for improved dependency security monitoring.


Fixes:  

  • API Error 503 for Devices (Nemo-2472): fixed an API error that caused some existing devices and device types to display “Error 503: Service Unavailable.”
  • SIP Trunk Parameter Copying Issue (Nemo-2455): fixed a bug in the SIP Trunking App where creating a new trunk copied parameters from a previously opened trunk.
  • Call Center App Crash (Nemo-2439): fixed an issue that caused the app to crash when clicking on queue cards.
  • CSV Report Data Mismatch (Nemo-2437): fixed inconsistencies in the Emergency Information Report (CSV), ensuring that Emergency Caller ID Name/Number and Emergency Address fields correctly reflect the actual data.
  • Checkboxes in Audio/Video Parameters (Nemo-2368): fixed an issue where checkboxes in the Audio Video parameters section of a device were non-functional.
  • Toast Message Fix (Nemo-2434): resolved an issue where toast messages were not appearing correctly when creating or editing a Seat.


Upgrades

  • eslint-plugin-import (Nemo-2418): upgraded from 2.26.0 to 2.31.0.
  • eslint-plugin-jsx-a11y (Nemo-2417): upgraded from 6.6.1 to 6.10.0.
  • i18next-parser (Nemo-2416): upgraded from 3.7.0 to 9.1.0 (requires Node.js 18).


Removals:

  • Storybook Cleanup (Nemo-2448): Removed the unused Storybook installation, including the library, configurations, and all stories.



This release is a testament to the hard work and dedication of our Development Team — huge thanks to them for delivering such a fast and impactful update!


And, of course, thank YOU for choosing our software! Your support and feedback inspire us to keep improving.  For support or additional information, please contact our Support Team. We’re here to help with any questions or clarifications regarding this release. 



Thank you for choosing Ooma! 


Vladimir Vitukhin

Technical Writer | ooma.com

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article