XMedius Cloud Update • 2018-01-26

Administrator -

This article lists the changes of the XMedius Cloud platform and services as of 2018-01-26.

Account Administration

  • Users now receive an email notification when they are assigned a fax number. This notification is sent separately from the initial welcome email that users receive when their account is created. Administrators can enable or disable the sending of such email notifications for all users at the enterprise level (among enterprise account settings).
  • In Single Sign-On (SSO) configuration process involving AD FS integration, the certificate fingerprint string is now automatically sanitized to avoid a common issue that was observed from copying and pasting the intended value from the AD administration console.
  • The SSO mechanism has been improved to avoid potential authentication issues using MFP apps/connectors or local applications installed on user PCs.
  • Call Detail Records (CDR) now exclude External Numbers from the totalized count of numbers shown in Excel sheet tab in order to reflect the exact count of numbers that are actually invoiced.
  • The number porting request flow has been improved to properly display the current status of the numbers involved in a request.
  • Support of the upcoming XMediusFAX App for Toshiba MFPs.
  • Various other improvements and security fixes.


  • The SendSecure REST API v2 has been updated with the following:
    • Fixed an issue that sometimes returned a 403 error when submitting an attachment in multiple chunks.
    • Fixed an issue that would have allowed the creation of a SafeBox for a user having no SendSecure access (within an Enterprise Account having the SendSecure service enabled).
    • Fixed an issue that would sometimes return a 400 error when downloading a file.
    • Fixed a mismatch regarding the SafeBox Owner ID returned by the API.
    • Improved the response to the call listing the SafeBoxes by including the list of participants.
    • Added the support of Mark As Read/Unread for specific SafeBox messages.
  • The SafeBox access flow for Guest Participants using security code has been improved to avoid potential situations leading to 500 error page.
  • The file upload mechanism has been improved to avoid some situations preventing files to be uploaded.
  • Various other improvements and security fixes.
Have more questions? Submit a request


Powered by Zendesk