Inspect connection info outside of logs

[deldering]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate.
• Described the feature in detail and justified the reason for the request.
• Provided specific use cases and examples.

Feature description

Hi there,

currently only the ESP_LOG statements can be used to determine what IP addresses are used to establish the connection. Is there a way to look at the candidate pairs via code and whether that is a direct p2p connection or that it is relayed via a turn server? Maybe this data can be added to the ESP_WEBRTC_EVENT_CONNECTED and ESP_WEBRTC_EVENT_CONNECT_FAILED?

Use cases

For remote monitoring I want to know what candidate pairs were generated and which one was chosen in the end to establish the connection.

Alternatives

No response

Additional context

No response

[TempoTian]

Get all pairing address seems not so easy for it is pairing gradually, if use trickle-ice. I can provide an API to get final selected one. It is avail when receive ESP_PEER_STATE_PAIRED, is it OK for you?

[deldering]

That would already be very helpful yes :)

[TempoTian]

OK， I will release one version these 2 days, when finished I will notify to you the usage.

[deldering]

Any update on this? I'd love to incorporate this into my project

[TempoTian]

I have commit the code in 62f1e45#diff-5322c1f2304e3d0c72971cafaac2bbfc6e78781e0340a5c5c78cc496719b5d43

You can get the addr in:

    } else if (event->type == ESP_WEBRTC_EVENT_PAIRED) {
        esp_peer_handle_t peer_handle = NULL;
        esp_webrtc_get_peer_connection(webrtc, &peer_handle);
        setup_rtp_transformers(peer_handle);
        esp_peer_addr_t addr = {};
        esp_peer_get_paired_addr(peer_handle, &addr);
        ESP_LOGI(TAG, "Paired with %d.%d.%d.%d:%d", addr.ipv4[0], addr.ipv4[1], addr.ipv4[2], addr.ipv4[3], addr.port);