Releases and project news
What is changing in TranslatorX, why it matters, and where to learn how each new capability works.
Announcement
July 11, 2026
The current TranslatorX beta is a complete rewrite of the original application, not a visual reskin. It uses modern frameworks while retaining the protocol detail and investigation workflows that made TranslatorX useful.
The rewrite provides a cleaner, maintainable cross-platform foundation so fixes can be delivered safely and new capabilities can be developed more rapidly. It also gives the project room to keep expanding protocol support, collection workflows, security controls, and interface refinements.
Public beta
Beta.4 focuses on SIP fidelity and call-flow clarity, with parser hardening for real-world packet captures and Unified CM normalization traces.
Changed messages now show a normalization indicator and an inbound or outbound comparison with before, after, and highlighted difference views. Unchanged normalization events stay out of the way.
SIP normalization documentationPCAP and PCAPNG handling is more tolerant of fragmented, retransmitted, out-of-order, and segmented SIP traffic, including message bodies split across packets.
Packet-capture documentationSDP offer and answer tracking now follows the terminal media endpoints across intermediary call-control legs and avoids inventing media streams to Unified CM.
Call Flow and media documentationCall bands use a restrained legacy-inspired order, media labels are easier to read, and signaling rows no longer alternate between light and dark variants within one call.
Call Flow documentationWhen a SIP BYE carries Reason or Warning headers, the Call Flow arrow includes that context. BYEs without either header retain the compact label.
Call Flow message-label documentationUpcoming stable release
This is the cumulative running list for the full 26.1.1 release. It records features that are new or substantially expanded since TranslatorX 15.0(3), and it will continue to grow as beta development proceeds. Every entry links to its current user documentation.
The legacy application has been completely rebuilt using modern frameworks, creating a maintainable cross-platform foundation for faster ongoing development.
Modern application documentationCall List, Call Flow, filters, source traces, CDR details, preferences, and inspectors open as reusable native desktop windows with platform menus and shortcuts.
Windows, menus, and shortcuts documentationThe interface can follow the operating system or use an explicit light or dark appearance while retaining protocol and call correlation colors.
Preferences documentationLarge folder imports, parsing, correlation, and call analysis remain responsive and report clear progress for each phase of the work.
Loading and progress documentationUniversal macOS and 64-bit Windows packages use platform signing, notarization or Authenticode verification, release checksums, and updater signatures.
Software update documentationChoose an update channel, check automatically or manually, and receive verified releases through the application’s signed updater.
Update-channel documentationOpen files, recursive folders, drag-and-drop selections, or clipboard text and choose whether new evidence appends to or replaces the current session.
Trace import documentationRead gzip logs, ZIP bundles, and ZIP files nested to a controlled depth while reporting unsupported or unsafe entries instead of silently skipping them.
Archive import documentationSupport common link layers, VLANs, IPv4 and IPv6 fragments, nanosecond timestamps, TCP reassembly, retransmissions, compact headers, and SIP bodies spanning packets.
Packet-capture documentationDecode current and legacy Unified CM, CUBE, Expressway, Webex, endpoint, CUSP, BroadWorks, IOS binary, H.323, Q.931, SCCP, MGCP, SIP, and SDP sources.
Supported data documentationRe-import source-neutral .txtrace evidence with normalized metadata instead of depending on the original vendor wrapper or source path.
Use Unified CM calllogs to fill missing events, then replace a matching summary with the full SDL message if richer evidence is loaded later.
Calllog documentationCompare time, endpoints, direction, protocol, message name, handles, tags, and call identifiers across vendor formats with resizable and content-aware columns.
Message workspace documentationRecognized headers and media fields provide plain-language explanations and standards references without altering the selectable message text.
Decoded content documentationReview wire, before, after, and highlighted semantic differences for changed inbound or outbound SIP normalization events without duplicate rows.
SIP normalization documentationCombine protocol, direction, endpoint, message, identifiers, correlation, text, and time criteria using AND within rows and OR across rows, then save them as .txf.
Search message content and independently hide protocol families or routine traffic without deleting evidence from the active session.
Search and display documentationJump from a decoded message or AI citation to exact raw lines with line numbers, horizontal scrolling, previous/next search, and matches-only mode.
Source viewer documentationNormalize to GMT using explicit zones, device identity, matching SIP messages, missing-year inference, sub-minute skew correction, evidence confidence, and user overrides.
Source-time documentationReview parsing warnings, collection status, inferred values, remote connection events, and cleanup results in one support-oriented window.
Event Log documentationEdit discovered device names once, use them throughout the workspace and diagrams, and import or export alias sets as JSON.
Device alias documentationSeparate Unified CM CDR records, trace-derived SIP calls, and explicitly correlated multi-leg SIP sessions instead of treating every investigation as one flat list.
Call List documentationConnect call legs through Session-ID, remote-cc, Cisco-Guid, and related identifiers without relying on phone-number or timing guesses.
SIP session documentationDistinguish connected, completed, cancelled, redirected, rejected, failed, and incomplete calls, then inspect route, legs, endpoint history, evidence, and key events chronologically.
Call analysis documentationKeep timestamps visible, suppress duplicate SIP retransmissions when desired, select any arrow for detail, and retain a dense chronological ladder.
Call Flow documentationReorder or combine lanes, apply persistent aliases, keep media-only endpoints adjacent, and use restrained per-call band colors without alternating row shades.
Call Flow lane documentationFollow SDP offer and answer endpoints across intermediary signaling legs and show audio, video, direction, hold, rejection, resume, port, and transport changes without duplicate streams.
Media stream documentationShow SIP Reason and Warning values directly on BYE arrows when present while leaving ordinary BYE labels compact.
Call Flow label documentationOpen standalone or embedded records, search grouped and raw fields, decode disconnect causes, create trace filters, and launch related Call Flow views.
CDR and CMR documentationDecode Q.931 and Q.SIG Facility information in the message where it occurred rather than requiring a separate developer utility.
Protocol support documentationManage and test Unified CM, CUBE, and Expressway connections once, then use the same profiles across historical, coordinated, troubleshooting, and live workflows.
Profile documentationKeep passwords and key passphrases in the operating system credential manager rather than serializing secrets into profile or settings files.
Credential storage documentationUse passwords, OpenSSH keys, hardware-backed FIDO2 keys, keyboard-interactive MFA, enable passwords, and independently authenticated jump hosts.
SSH authentication documentationRequire TLS 1.2+, review untrusted certificate identity before credentials are sent, pin accepted certificates by origin, review new SSH keys, and reject changed keys.
Connection trust documentationDiscover every node from a publisher profile and collect the requested SDL, SDI, calllog, CDR, or related timeframe across the cluster.
Unified CM collection documentationInspect trace state and coverage, offer to enable VoIP trace when privileges permit, collect bounded evidence, and interpret router clock information.
CUBE collection documentationCollect historical signaling, discover supported diagnostic operations, coordinate captures, and handle current and legacy Network Log formats.
Expressway collection documentationApply one absolute or relative timeframe to several products and open their independently collected evidence as one correlated timeline.
Multi-device collection documentationSelect participating systems, record the exact reproduction interval, coordinate Expressway capture state, stop cleanly, and collect one combined session.
Troubleshooting session documentationStream one or more CUBE and Expressway sources while filters, calls, sessions, and open diagrams update incrementally.
Live trace documentationEnable only the required signaling and transport debugs, strip shell noise safely, and report any stop or cleanup state that cannot be confirmed.
Live CUBE cleanup documentationConfigure Ollama, Anthropic, AWS Bedrock, or a compatible Anthropic Messages endpoint with validated model discovery and independently stored keys.
AI provider documentationStart analysis from a SIP call, correlated session, or filtered trace with deterministic observations and a bounded catalog of exact source ranges.
AI evidence documentationAllow the model to request validated literal or regular-expression searches and exact surrounding lines without granting arbitrary filesystem access.
Context retrieval documentationReview probable cause, confidence, findings, alternatives, recommendations, limitations, and citations that open the supporting message or source lines.
AI report documentationAlways remove credentials and SDP keys, anonymize telephone numbers, IP addresses, and hostnames by default, and keep local Ollama traffic on loopback.
AI privacy documentationAccumulate input, output, cache-read, and cache-write usage across context rounds when the selected provider reports it.
AI usage documentationExport the full session or only the current search, filter, protocol, and routine-traffic result as normalized readable text.
Readable export documentationShare a portable trace containing protocol content and structured analysis metadata without original local paths or vendor wrappers.
TranslatorX trace documentationSave the signaling and visible media diagram with its current labels and lane arrangement as a scalable vector image.
Call Flow export documentationPerform normal parsing, filtering, correlation, call analysis, diagram generation, and export locally without requiring a cloud service.
Security and privacy documentationProtect temporary trace data, limit archive and network content, validate remote destinations, and restrict sensitive application operations.
Application security documentationCheck every release for quality and dependency issues, sign the platform packages and updater files, and publish independent checksums.
Release integrity documentationGitHub retains versioned installers, checksums, updater manifests, and earlier release entries.
