2025 Q1 Release Notes

This topic will be updated throughout the quarter as we improve the product. For a complete overview of all Totogi releases, visit the Release Notes Archive.

Additionally, to stay ahead of future releases, check out Upcoming Changes . This topic provides detailed information on expected changes, helping you to plan and adapt your systems and integrations effectively.

New Functionality

• March 06, 2025 We have introduced Single Sign-On (SSO) support, allowing companies to enable authentication through their SAML2-compliant Identity Provider (IdP) instead of using passwords. This provides a seamless and secure login experience while meeting enterprise security requirements. 

With this update, SSO can be configured per tenant, offering an alternative authentication method. Plan Design now provides an SSO login option, where users enter their corporate email and are redirected to their Identity Provider (IdP) for authentication, ensuring a streamlined login process.

SSO setup requires configuration per tenant. Please contact Totogi Support for further assitance on how to set up SSO for your tenant. 

Coming next: Multi-tenant SSO support, allowing users to authenticate across multiple tenants with a single login.

• January 30, 2025 Totogi now supports accurate rating for MMS sent over both 4G and 5G networks, ensuring customers are correctly billed for sharing photos, videos, and other multimedia content.

In Plan Design, you can easily add and configure the MMS rating group with a single click in the "Network" settings and immediately start defining MMS plans. Our updated Voice-Text-Data and Roam Like Home templates now include a dedicated section for MMS.   

Important: In order to fully support MMS rating, a field mapping has to be configured; MMS originator and recipient addresses shall be mapped to IMS called party and IMS calling party addresses. Please contact Totogi Support to learn more about configuring MMS related field mapping for your tenant.

Changed Functionality

• February 4, 2025 In our ongoing efforts to streamline and enhance our API offerings, we removed several deprecated low-level Plan APIs that were originally designed for internal operational use and not intended for customer use. 

  Affected APIs and Fields:

  • getPlanServices
  • getRules
  • deletePlanService
  • copyPlanService
  • updatePlanService
  • createPlanService
  • copyPlan
  • ceatePlan
  • PlanVersion.planServices
  • FieldMapping.field

• These APIs and fields, especially PlanServices under PlanVersion, may appear in API payloads inadvertently. It’s important to review your integrations to determine if these are being utilized.

  Action Required:

  1. Verify Usage: Check if your scripts or integrations use the listed APIs or fields.
  2. Transition Guidance:
     • If you rely on PlanServices or its attributes, please transition to using InitialTemplateService, accessible under the template attribute in PlanVersion.
  3. Update Integrations: Remove any dependencies on these APIs and fields from your systems.

• Please refer to our latest API documentation for detailed information.

• February 4, 2025 The balanceValue attribute in AccountBalanceInfo, which previously duplicated the total attribute, is removed. Please update your integrations to utilize the sum of the Available and Reserved values instead.
• February 4, 2025 This update simplifies plan subscription management by unifying PlanID and PlanAlias functionality in the API. Customers can continue using PlanIDs for subscriptions ensuring that they launched Plans with activation time in Plan Design.

The key changes include:

• Unified PlanID and PlanAlias Functionality: Subscriptions created with a PlanID will now rely on the active alias of the plan. If no alias is active at the time of the API call, a PlanAliasNotFound error will be raised. This applies to both immediate and future-dated subscriptions.
• Enforcing Specific Plan Versions: To subscribe to a specific version of a plan, the PlanVersionID must be used instead of PlanID. Subscriptions using PlanVersionID will not support automated migrations to new versions.
• Indicator for Alias-Based Subscriptions: A new aliasEnabled flag in the SubscribedPlanVersion will indicate whether a subscription is alias-based or tied to a specific plan version.
• Subscriptions Created Before This Update: Subscriptions created with PlanID before this change will remain functional but will not transition automatically to new plan versions. To enable alias-based automated migrations, tenants must update these subscriptions via the updatePlanSubscription API or cancel and re-subscribe.
• Future-Dated Subscriptions: The system will validate the plan alias at the time of subscription for future-dated requests. If no active alias exists at that time, an error will be raised.

Important: To avoid errors, ensure your plans are launched with activation times in Plan Design and that an active alias exists when using PlanID for subscriptions.
For more details, refer to the updated API documentation.

🚀 Feature Availability: This update has been enabled for the majority of tenants. However, it remains disabled for tenants who explicitly requested additional time before adoption. If you believe the feature is not enabled for your tenant and would like to activate it, please contact Totogi Support.

Fixes and Improvements

• March 03, 2025 Previously, balances with long-running reservations could remain active beyond their renewal period if a session was still running, leading to inconsistencies in balance tracking and notifications. With this update, balance reservations now expire timely, even within long-running sessions, ensuring accurate tracking of available balances and preventing outdated reservations from persisting.

  Additionally, this update introduces the following improvements:

  • Consistent Usage Rounding: The total usage during a session is now consistently rounded. Each update request adjusts usage to ensure that the total usage reported in EDRs and Account balances matches the nearest rounded value.

  • Balance-Level Tracking in EDRs: EDRs now include balanceID in addition to balanceType, allowing multiple balances of the same type to be accurately reported in charges. Each session tracks charge statistics separately by balance type and balance instance, improving visibility and granularity.

• February 13, 2025 This change introduces an enhancement to the S3 ORC EDRs by including the providerdata structure. Previously, this information was only available through the getEventDataRecordbyDevice API. With this update, customers can now access key insights into the rating process directly from their EDRs stored in S3, improving visibility into multiple plans and roaming scenarios.
• January 13, 2025 This functionality builds on the existing denyOtherServices capability, which was previously available for Credit Control with Unit Reservation, and extends it to Event-Based Charging. The Charging Engine now denies SMS services under specific conditions, such as when a plan has no BalanceTypes, when available Balance is zero, or when the available Balance is insufficient to cover the required rate. These denials are triggered only when the denyOtherServices flag is enabled and the SMS destination matches the plan configuration. Any service denial caused by the denyOtherServices flag is logged in the respective session Event Data Records (EDRs) with the "resultCode : QUOTA_LIMIT_REACHED".

   

  In Plan Design, BNumber plans with “Deny” or “Rate” features always set this flag to true so that service is denied as desired.