Recording + RecordingExt entities, RecordingImagingService writes them

Featurekamo-shared-library
Shipped
April 27, 2026 at 6:31 AM UTC
Author
Kamo
Commit
515b49e

- New Recording entity (UUID id, IMG_ID, IS_MASTER, IS_VM, EXTENSION, MEMBER_ID, LENGTH, DATE_RECORDED, DATE_CREATED [DB-defaulted via @CreationTimestamp]). One row per finalized voicemail or call recording uploaded to imaging. - New RecordingExt entity (UUID id, RECORDING_ID, EXTENSION, MEMBER_ID, IS_MASTER). One row per channel that participated in the recording; the master leg is flagged IS_MASTER=true, every other leg false. - **************** now takes a RecordingMetadata bundle (phoneServerInstanceId, dateRecorded, lengthMs, participatingExtensions) and persists Recording + RecordingExt rows in the same transaction as the Img/ImgDat. memberId is resolved per leg via **************** on the originating VOIP instance (null when unassigned).

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing