Version 4.56.1 | Platform Release Notes

Planned official release schedule and content:

Timing:

What's New?

CDR Correlation ID

We are pleased to announce the availability of CDR Correlation IDs. Correlation IDs aid in reconciling CDR records by providing a direct method to match up the multiple CDRs reported when a communication involves more than one subscriber.

By way of example, a call between two subscribers (John and Mary) generates a CDR for John calling Mary and a 2nd CDR for Mary receiving a call from John. Without Correlation IDs one would have to use "fuzzy logic" to examine timestamps, the parties involved, etc., to determine both CDRs were the same phone call.

With the optional Correlation ID field added to the CDRs, one simply finds all CDRs with the same 64-charager Correlation ID.

An added advantage is that the correlation process spans all Movius geographic regions. A message between a user in the US region and a user in the APAC region will have the same Correlation ID on the CDR reported in the US and on the corresponding CDR reported in APAC.

Some additional points:

• Calls and messages involving only one subscriber will have the Correlation ID field blank
• Movius must enable the creation of Correlation ID's for an Enterprise.
• In order to have the Correlation ID included in the output of the CDR REST API report, the request must include the optional input parameter include_corr_id=true
• When the feature is enabled and the Correlation ID is requested in the APi request, the field "corr_id" is included in the CDR
• The 64-character Correlation ID is of the form 7c42012e73e1dcbdbbfc988edcbbf1441af6f7a9dae0d2a5ad31f2d80553808e

CNAM Support for MS-Teams

This release will also provide an improved end user experience for Microsoft Teams calling. If the underlying carrier indicates the calling party's display name in the CNAM header, the CNAM will be included in the signaling to the called party. This applies to calls to and from the MS-team application.

CDR Exclusion APIs

This release will support new version of CDR APIs that can be used by customer admins to signal exclusion of specific type of CDR records from the capture reporting. This feature is enabled for a specific customer.

Version History