ESP32 VoIP (ADF) Audio Path Failure: SIP Connected, But NO Mic/Speaker Audio (LyraT-mini v1.2)

[ghw5reta]

Hello,

I am developing a VoIP application using ESP-ADF (IDF v5.3.4) on the ESP32-LyraT-mini v1.2 board. We have successfully achieved SIP session connection, but are experiencing a critical failure where neither the microphone nor the speaker works during the call. The dialogue path is completely silent.

1. Development Environment Details
Hardware: Two ESP32-LyraT-mini v1.2 boards.

Frameworks: ESP-IDF v5.3.4 and ESP-ADF (Git Clone).

Application: SIP service based example.

Codec: ES8311 (Integrated on LyraT-mini v1.2).

2. Log Analysis & Problem Diagnosis
The attached log shows the successful start and normal end of the audio session, but previous logs frequently showed I2C NACK errors, suggesting a problem with codec initialization.

Observation from Attached Log (voip_log.txt): The log confirms a successful ESP_RTC_EVENT_AUDIO_SESSION_START followed shortly by ESP_RTC_EVENT_AUDIO_SESSION_END and normal task stopping (_audio_enc, _audio_dec).

The Issue: Despite the successful session setup, there was no audio input or output.

This strongly indicates that the ES8311 Audio Codec failed to initialize or its I2S configuration failed due to a communication issue, likely the I2C NACK errors previously observed.

[Please ensure you attach the log (voip_log.txt) here]

3. Specific Questions for the Community
I2C/Codec Initialization Fix (Priority Question):

Since we are using the ESP32-LyraT-mini v1.2 board, are there any known hardware revision-specific I2C issues or required workarounds (e.g., specific delays, power-up sequence fixes) needed to ensure stable communication with the ES8311?

What is the best way to robustly handle I2C NACK errors during the ES8311 initialization sequence within ADF to ensure the codec's registers are correctly set for Mic/Speaker operation?

Core Contention & Buffer (Secondary):

Although the current log doesn't show it, we previously had Core 0 contention problems (_rtp_audio_recv Prio 20 vs. wifi Prio 23). Could an expert provide the file path to the xTaskCreatePinnedToCore() call for _rtp_audio_recv so we can pin it to Core 1?

Walkie-Talkie Alternative:

Are there any successful example projects or recommended methods to achieve reliable, low-latency push-to-talk intercom communication between two ESP32-LyraT-mini boards, bypassing the current SIP issues?

Thank you for your expertise.