Anyone working with in-vehicle voice and communication modules knows ITU-T. P.1140 super-wideband voice, P.1110 vehicle hands-free, P.1100 series narrowband voice — these are the standards OEMs hard-require when sourcing Tier-1 communication modules. But many manufacturers don't understand a fundamental point: ITU-T itself only publishes Recommendations. It doesn't issue conformity certificates for products. There is no official certification issuance process.

SG12 working group only handles drafting and revising standard texts. They hold quarterly online meetings to discuss technical content but don't make conformity judgments on specific products. After third-party testing is completed, an ISO-17025 lab with ILAC-MRA accreditation can enter the report into the ITU-T Product Conformity Database. That's the final step. As for the ITU-T Logo — you need written approval from the ITU Secretary-General to use it, which commercial products almost never receive.

In practice, there are only two paths. German and Japanese automakers want different things. This article breaks down the timelines.

I. Two ITU-T Certification Paths and Their Timeline Differences

Path 1: Third-party lab test report only. Find an ILAC-MRA-accredited lab to run the full P-series test suite. From sample submission to formal report, counting scheduling, four to eight weeks is typical. German automakers generally require reports from ILAC-accredited labs. European second-tier OEMs sometimes accept any third-party report without requiring database entry.

Path 2: Lab submits report for ITU-T database entry. After obtaining the accredited lab report, the lab or an ISO-17065-accredited body submits it to ITU-T for Product Conformity Database registration. German automakers universally require this layer. Report plus database entry takes one to two weeks more than just getting the report alone. There is no third path — no official ITU-T certification, no SG12 product review panel, no ITU-T mark on products. Some manufacturers hear "full certification takes six to eight months" — they're waiting for a process that doesn't exist.

Manufacturer self-test reports cannot be used for ITU-T database entry. Company-internal test data is for internal reference only. German automakers only accept accredited lab reports — they won't take self-test materials.

  II. Testing Timeline by ITU-T Standard

P.1140 super-wideband voice testing is the heaviest. Over fifty background noise environments, dual-talk, single-talk, and silence scenarios each run multiple rounds for averaging. Pure testing takes three weeks. Super-wideband frequency response extends to 20kHz, making high-frequency noise interference complex. Algorithm iteration rounds are significantly more than in the narrowband era.

P.1110 vehicle hands-free must be tested in a real vehicle environment — not in an anechoic chamber. Body vibration noise, HVAC air noise, engine idle noise all serve as real noise sources. From environment setup to test completion, one to two weeks. If the microphone array, DSP algorithm, and hardware circuitry are completely unchanged and only the vehicle body shell is different, an accredited lab evaluation may exempt certain items — not a full retest. Only when microphone installation position or in-vehicle acoustic space changes is a full retest required. It's not a blanket rule that changing vehicle models means full retesting.

The 2026 SG12 revision added multi-source interference scenarios, but P.1110 still focuses primarily on the driver's position. Calls between front passenger and rear passengers fall under P.1150 — that's not P.1110's test scope. Don't confuse the two standards. Electric vehicle motor high-frequency electromagnetic noise significantly impacts beamforming — many products fail at this hurdle.

P.863 POLQA voice quality assessment is relatively fast. Uses standard voice sample libraries for comparative scoring. Results in one week. POLQA algorithm licensing is managed by OPTICOM. Lab equipment purchases typically come with one-time licensing — no annual fees. Only enterprise monitoring platform versions charge annual fees. You can't blanket-statement that it costs tens of thousands per year. P.1100 narrowband testing takes half the time of wideband due to fewer test conditions and smaller noise libraries.

  III. Ways to Accelerate ITU-T Certification

1. Pre-testing for baseline assessment. Before formal testing, run a complete internal round or use a facility with equipment to do a full preliminary check. First-pass success rate goes from 50-60% to over 80%. Saving one rectification round saves one to two weeks. Pre-test stage allows parameter adjustment. Formal testing requires frozen parameters.

2. Lock in scheduling early. Year-end and around auto shows, lab schedules are full. Pay a deposit two months ahead to secure the slot. Saves three to four weeks of queue time.

3. Bring enough samples. The most common P.1110 real-vehicle testing failure cause is burned-out samples or loose connectors. Have multiple sets on hand for on-site replacement. Industry convention is three sets, but this number isn't an ITU-T official hard requirement. Microphone arrays should be randomly sampled from production batches. Excessive variation between production consistency and test samples causes measurement deviation.

4. Documents first. ITU-T database entry frequently gets stuck on incorrect technical document formatting or unclear test method descriptions. Have someone experienced review everything against ITU-T templates beforehand. Normal parameter-adjustment rectification takes one to two weeks. Only large-scale algorithmic logic changes drag beyond three months.

For ITU-T certification timeline and related inquiries, contact BlueAsia Technology Testing & Certification consultant at 13534225140 (Benson).