Free Trace Check
MCPTT · MCData · MCVideo

Find out where your MCX system departs from 3GPP before your customer does.

Clause-by-clause MCX conformance testing of Mission Critical Push-to-Talk (MCPTT), MCData and MCVideo servers and traffic against the 3GPP specifications, for MCX server vendors, network operators, integrators and test labs. Each verdict cites the clause, the specification version and the frame, and quotes the requirement.

Request a free Trace Check → Ask for a 20-minute call

Trace Check: one capture, one call flow. The five most important findings within three working days, and a 30-minute call.

FAIL · FRAME 1 · SAMPLE
TS 24.379 V19.6.0 §10.1.1.2.1.1 (5)
shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841
Observed: Accept-Contact is absent
263
rules with a verbatim requirement
81
clauses
7
specifications
3
services: MCPTT, MCData, MCVideo
State on 10 November 2026
Rules are taken from
TS 24.379MCPTT call control TS 24.380MCPTT floor control TS 24.281MCVideo signalling TS 24.581MCVideo transmission control TS 24.282MCData signalling TS 24.229IMS SIP TS 33.180MC security TS 103 564test descriptions
01 Products

MCX server testing and capture analysis.

An MCPTT client emulator that calls through your server, and a passive probe that reads your pcap captures.

Client AemulatedMCX serverunder testClient BemulatedREGISTERREGISTERaffiliationINVITE group call200 OKFAIL · TS 24.379 §6.3.2.1.5.2 · no Require: timerFloor RequestFloor GrantedFloor Takenspeech AMR-WBFloor ReleaseFloor Idle
Sample run, synthetic traffic · 1 FAIL · 94 PASS
Client emulator

Server Test

Two emulated clients use your server: an MCPTT or MCVideo group call, or an MCData short message. You get a list of where it behaves differently from the standard.

  • Login to the IdMS over OIDC, also through a browser when MFA or SSO is required
  • Configuration documents over XCAP, registration over TLS with service authorisation
  • Affiliation, prearranged group call or chat group call
  • MCPTT floor control and AMR-WB speech, MCVideo transmission control; the 8 ETSI TS 103 564 test descriptions in the catalogue as scripted runs

Emulator defects are reported separately and never counted against your server. MCPTT, MCData and MCVideo.

Sample capture · 3 FAIL · 1 WARN · 14 PASS
Passive probe

Capture Analysis

Captures you already have are enough. The probe can also run inside your network, so the captures never leave it.

  • Reads pcap and pcapng; rebuilds SIP dialogs, floor control and media
  • Follows the state machines and timers of the specifications
  • Names what it cannot see: encrypted streams, TCP gaps, truncated packets
  • Reports in HTML, JSON and JUnit; tested on captures up to 1 GB

It sends no traffic of its own and needs no connection to your systems. MCPTT, MCData and MCVideo.

02 Sample reports

Sample MCPTT, MCData and MCVideo test reports.

Complete reports, as you would receive them: one per service, each with a deviation and the clause it breaks. Generated from synthetic traffic.

First page of a sample MCPTT capture analysis report from the passive probe, synthetic traffic
Probe · capture analysis

Group call INVITE

A synthetic capture where every leg of the path is visible; a real probe rarely sees that much.

3 FAIL · 1 WARN · 14 PASS
Open the report →
First page of a sample MCPTT server test report from the client emulator
Emulator · MCPTT

MCPTT group call

One deviation: the 200 OK without Require: timer, TS 24.379 §6.3.2.1.5.2, and a floor control packet cut short.

1 FAIL · 2 message defects · 94 PASS
Open the report →
First page of a sample MCData server test report from the client emulator
Emulator · MCData

MCData short message

One deviation: the MESSAGE delivered to the recipient without P-Asserted-Service, TS 24.282 §9.2.2.3.2.

1 FAIL · 14 PASS
Open the report →
First page of a sample MCVideo server test report from the client emulator
Emulator · MCVideo

MCVideo group call

One deviation, three times: Receive Media responses without the Result field, TS 24.581 §6.3.6.3.6.

3 FAIL · 64 PASS
Open the report →
03 Coverage

3GPP rules covered for MCPTT, MCData and MCVideo.

What the conformance rules cover today: before you order, you can see which specifications a report covers and how many clauses.

263
rules with a verbatim requirement
81
clauses

A test covers selected procedures, and every report includes a matrix of what was checked and what was not.

The rule catalogue keeps growing. If your system needs a procedure we do not cover yet, we add the rules as part of the agreed scope, and they stay in the catalogue for later tests.

State on 10 November 2026. By service: MCPTT 147 rules, MCVideo 76, MCData 37, IMS 3. ETSI TS 103 564 test descriptions: 8 of 327, all 8 run by the emulator.

SpecificationSubjectRulesClauses
TS 24.379 V19.6.0MCPTT call control11222
TS 24.281 V19.5.0MCVideo signalling6315
TS 24.282 V19.6.0MCData signalling3710
TS 24.380 V19.1.0MCPTT floor control2916
TS 24.581 V19.1.0MCVideo transmission control1313
TS 24.229 V19.7.0IMS SIP52
TS 33.180 V20.0.0MC security43
Total26381
04 Services

MCX testing services, scope agreed in advance.

Four services: a free Trace Check, a Server Test, analysis of MCPTT interoperability disputes, and support during acceptance testing. Prices on request; invoiced after the report is delivered.

S1free

Trace Check

capture analysis

One capture, one call flow. The five most important findings within three working days, and a 30-minute call.

S2

Server Test

client emulator and probe

Emulator runs from an agreed list against your server, with the probe report on the recorded traffic. Duration agreed with the scope.

S3

Interop Dispute Analysis

capture analysis

For when two vendors' implementations do not work together and each points at the other: you send captures of up to three failing call flows, and we tell you which side departs from 3GPP, with the clause and the frame for each finding. Two to three working days.

S4

Acceptance Support

probe in your network

The probe in your network during acceptance testing, with a report per vendor. Booked by the day; duration agreed with the scope.

05 How it works

How we handle your captures.

YouUIMS01 20-minute callquestion and scope02 mutual NDAsigned before any capture03 one capturesecure channel, deleted 30 days after the report04 report + callclause, version and frame per finding
  1. A short call to agree the question and the scope.
  2. A mutual NDA, signed before any capture is shared.
  3. Captures over a secure channel, stored encrypted and deleted 30 days after the report. Or the probe runs in your network and only the report leaves it.
  4. The report and a call to go through it.
06 Limits

What a report does not claim.

It is not a certification.It is an assessment of selected 3GPP procedures and does not replace GCF or TCCA certification.
NOT-TESTABLE is not a pass.When the capture does not show enough to decide, the report says so.
Encrypted traffic is not decrypted.Captures where the signalling is in clear text, inside the SIP core, give the most coverage.
The probe does not control terminals.It reports what a terminal did in the capture.
Contact

Start with one capture.

Write a few words about your system and the call flow you want checked, or ask for a 20-minute call. We sign a mutual NDA, and then you send one capture.

What is it about?

Please do not attach or paste captures here. We sign a mutual NDA first.

We use these details only to reply to you. Privacy notice.

Prefer to write or call?

contact@uims.eu
+48 517 303 192
UIMS has spent years developing 3GPP MCX systems.