Turn not working

[Alan5142]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

When using a TURN server, it should allow the communication between both peers.

Actual behavior (suspected bug)

I have tested the esp_peer component through IDF component manager. My peer is a custom desktop console app (built with webrtc.rs), and overall works fine when both of them specify peer_cfg.ice_trans_policy = ESP_PEER_ICE_TRANS_POLICY_ALL (RTCIceTransportPolicy::All in the rust side). However, when I specify ESP_PEER_ICE_TRANS_POLICY_RELAY or when any of them is in a different network, it no longer works.

I am using Cloudflare TURN service. I also tested with metered.ca TURN server

I attach part of the logs after I received a ESP_PEER_STATE_PAIRING signal. After that, I receive a ESP_PEER_STATE_CONNECT_FAILED event. I received tons of those logs before receiving the CONNECT FAILED event.

Error logs or terminal output

I (86007) AGENT: 0 Send binding request (cand:0) local:192.168.100.232:53554 remote:172.26.144.1:60995 id:6fe91e6c2322a8846df77827
I (86010) AGENT: 0 Send binding request (cand:0) local:192.168.100.232:53554 remote:192.168.177.1:51326 id:1e63da772a81f9c13740f7d1
I (86021) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:25248 id:621f7dc2473fade00ecfd396
I (86032) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:25148 id:45480065562666204bf4e964
I (86043) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:15130 id:57f7686d7936f3746ee7eb07
I (86055) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:15645 id:55ee4c0b44c1aa5d4f7df387
I (86066) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:25248 id:16dc99605368c1de0aa98cb7
I (86078) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:25148 id:314d8d5d5964648b6f641684
I (86089) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:15130 id:09f4ba361af7c2e06b1623bb
I (86101) AGENT: 0 Send binding request (cand:0) local:xxx.xxx.xxx.xxx:53554 remote:yyy.yyy.yyy.yyy:15645 id:127e9dbf19cb4497662fbe85
I (86112) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:51354 remote:104.30.150.84:22689 id:0945b15a232c184841d5cd1c
I (86123) AGENT: 0 send indication bind request

Steps to reproduce the behavior

1. Create a minimal setup of ESP_PEER with an external signal server.
2. Connect either the ESP32 or the peer to another network
3. Try to connect both of them

Project release version

v1.2.4

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Windows

Operating system version

Windows 11

Shell

PowerShell

Additional context

I am using a ESP32 S3

[TempoTian]

I test use TURN can work if set ESP_PEER_ICE_TRANS_POLICY_ALL, but failed if set ESP_PEER_ICE_TRANS_POLICY_RELAY . Is it same phenomenon as your part? Seems some regression with ESP_PEER_ICE_TRANS_POLICY_RELAY.

[Alan5142]

I test use TURN can work if set ESP_PEER_ICE_TRANS_POLICY_ALL, but failed if set ESP_PEER_ICE_TRANS_POLICY_RELAY . Is it same phenomenon as your part? Seems some regression with ESP_PEER_ICE_TRANS_POLICY_RELAY.

If both are in the same network, yes, it fails when any of the peers use that option. If both are in different networks (one of them being mobile network), it fails as they try to use the TURN server.

[TempoTian]

I have fixed the issue that I can reproduce local use doorbell_demo when set policy to relay only. The lib is as below, you can put it into managed__components/espressif__esp_peer/lib/esp32s3 to test doorbell_demo also. but from your log, I see no stun binding request is responsed. You can try to use wireshark to fetch network packets, I can help you to analysis it.

libpeer_default.zip

[Alan5142]

I have fixed the issue that I can reproduce local use doorbell_demo when set policy to relay only. The lib is as below, you can put it into managed__components/espressif__esp_peer/lib/esp32s3 to test doorbell_demo also. but from your log, I see no stun binding request is responsed. You can try to use wireshark to fetch network packets, I can help you to analysis it.

libpeer_default.zip

Sure, I'll try it and keep you posted. Thank you so much!

Edit:
I also see an error from the STUN side of things. I'm going to debug this as well to confirm that I am sending the correct credentials

[TempoTian]

Can you attach the matched log and remove sensitive info?

[Alan5142]

Yes, those are the full logs since the device connected to the signaling server (custom websocket server):

I (3162) wifi:set rx beacon pti, rx_bcn_pti: 0, bcn_timeout: 25000, mt_pti: 0, mt_time: 10000
I (3209) wifi:AP's beacon interval = 102400 us, DTIM period = 3
I (4234) esp_netif_handlers: sta ip: 192.168.137.140, mask: 255.255.255.0, gw: 192.168.137.1
I (4235) test: got ip:192.168.137.140
I (4236) test: IPv4 Address: 192.168.137.140
I (4246) test: connected to ap
W (4249) websocket_client: `reconnect_timeout_ms` is not set, or it is less than or equal to zero, using default time out 10000 (milliseconds)
W (4262) websocket_client: `network_timeout_ms` is not set, or it is less than or equal to zero, using default time out 10000 (milliseconds)
I (4274) test: Other event id:6
I (4277) test: WEBSOCKET_EVENT_BEFORE_CONNECT
I (4283) websocket_client: Started
I (4852) test: WEBSOCKET_EVENT_CONNECTED
I (34983) wifi:<ba-add>idx:0 (ifx:0, b2:dc:ef:91:09:d8), tid:0, ssn:12, winSize:64
I (46022) test: Received WS data event with op_code: 1
I (46023) test: Received WS data event fin: 1
I (46023) test: Handling CONNECTED event, sending REQICE
I (46637) test: Received WS data event with op_code: 1
I (46637) test: Received WS data event fin: 1
I (46638) test: ICE Server: URL=stun:stun.cloudflare.com:3478, User=, Credential=
I (46647) test: ICE Server: URL=stun:stun.cloudflare.com:53, User=, Credential=
I (46659) test: ICE Server: URL=turn:turn.cloudflare.com:3478?transport=udp, User=<TURN SERVER USER>, Credential=<TURN SERVER PASSWORD>
I (46683) test: ICE Server: URL=turn:turn.cloudflare.com:3478?transport=tcp, User=<TURN SERVER USER>, Credential=<TURN SERVER PASSWORD>
I (46707) test: ICE Server: URL=turns:turn.cloudflare.com:5349?transport=tcp, User=<TURN SERVER USER>, Credential=<TURN SERVER PASSWORD>
I (46731) test: ICE Server: URL=turn:turn.cloudflare.com:53?transport=udp, User=<TURN SERVER USER>, Credential=<TURN SERVER PASSWORD>
I (46755) test: ICE Server: URL=turn:turn.cloudflare.com:80?transport=tcp, User=<TURN SERVER USER>, Credential=<TURN SERVER PASSWORD>
I (46780) test: ICE Server: URL=turns:turn.cloudflare.com:443?transport=tcp, User=<TURN SERVER USER>, Credential=<TURN SERVER PASSWORD>
I (46804) DTLS: Init SRTP OK
W (47889) PEER_DEF: Create cache for RTP packets fail, resent logic is disabled
I (47890) test: Peer state changed: 2
I (47890) AGENT: Start agent as Controlling
I (47893) PEER_DEF: Start DTLS role as 1
I (47912) AGENT: Send STUN binding request
I (47920) AGENT: 0 Get candidate success user: psw:
I (47925) AGENT: Send STUN binding request
I (47992) AGENT: Send STUN binding request
I (47993) AGENT: Send allocate now
Got error code 401
I (48005) AGENT: Send allocate now
I (48007) AGENT: Send allocate now
I (48011) AGENT: 0 Get candidate success user:<TURN SERVER USER> psw:<TURN SERVER PASSWORD>
W (48017) AGENT: Skip TCP stun server turn:turn.cloudflare.com:3478?transport=tcp
W (48025) AGENT: Skip TCP stun server turns:turn.cloudflare.com:5349?transport=tcp
I (48032) AGENT: Skip TURN server turn:turn.cloudflare.com:53?transport=udp for only support one
W (48040) AGENT: Skip TCP stun server turn:turn.cloudflare.com:80?transport=tcp
W (48047) AGENT: Skip TCP stun server turns:turn.cloudflare.com:443?transport=tcp
I (48055) test: Peer message received: type=1, size=521
I (48060) test: Sending SDP: v=0
o=- 7801614086411001801 2 IN IP4 0.0.0.0
s=-
t=0 0
a=msid-semantic: esp-webrtc
a=group:BUNDLE 0
m=audio 9 UDP/TLS/RTP/SAVPF 8
c=IN IP4 0.0.0.0
a=mid:0
a=sendrecv
a=rtcp-mux
a=rtpmap:8 PCMA/8000
a=ssrc:4 cname:EspSSpbA0
a=inactive
a=fingerprint:sha-256 94:25:9F:B8:4D:4F:6E:DE:D8:BD:93:6A:98:45:63:70:6A:F7:E1:6D:B2:E7:9C:E6:0E:C5:F9:7C:11:77:DB:7E
a=setup:passive
a=ice-ufrag:WwUl
a=ice-pwd:Pd9ZwfQgpeN3WiStdYMx5Ru0
a=candidate:0 1 UDP 10151935 104.30.145.172 39655 typ relay raddr 0.0.0.0 rport 0

Got error code 437
I (48154) wifi:<ba-add>idx:1 (ifx:0, b2:dc:ef:91:09:d8), tid:5, ssn:5, winSize:64
I (56466) test: Received WS data event with op_code: 1
I (56466) test: Received WS data event fin: 1
I (56471) test: SDP received from peer
I (56472) PEER_DEF: Get peer role 0
I (58115) AGENT: 0 Add remote type:1 172.26.144.1:59765
I (58115) AGENT: 0 Add remote type:1 192.168.137.1:59766
I (58116) AGENT: 0 Add remote type:1 192.168.56.1:59767
I (58119) AGENT: 0 Add remote type:1 192.168.177.1:59768
I (58124) AGENT: 0 Add remote type:1 192.168.129.1:59769
I (58129) AGENT: 0 Add remote type:1 192.168.100.36:59770
I (58134) AGENT: 0 Add remote type:2 yyy.yyy.yyy.yyy:59774
I (58139) AGENT: 0 Add remote type:2 yyy.yyy.yyy.yyy:59783
I (58145) AGENT: 0 Add remote type:2 yyy.yyy.yyy.yyy:12912
I (58150) AGENT: 0 Add remote type:4 104.30.145.173:9824
E (58155) AGENT: 0 Remote candidate over limited 10
E (58159) AGENT: 0 Remote candidate over limited 10
E (58164) AGENT: 0 Remote candidate over limited 10
E (58168) AGENT: 0 Remote candidate over limited 10
E (58173) AGENT: 0 Remote candidate over limited 10
E (58178) AGENT: 0 Remote candidate over limited 10
E (58182) AGENT: 0 Remote candidate over limited 10
0 Sorted pair 0 type: 4 local:104.30.145.172:39655 Remote:104.30.145.173:9824
I (58194) test: Peer state changed: 3
I (58202) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:39655 remote:104.30.145.173:9824 id:4c598d93643bd7252b449456
I (58209) AGENT: 0 send indication bind request

I (58667) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:39655 remote:104.30.145.173:9824 id:6db505597d157d8d71dfed43
I (58668) AGENT: 0 send indication bind request

I (59127) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:39655 remote:104.30.145.173:9824 id:666d97166fd595896931589d
I (59128) AGENT: 0 send indication bind request

I (59587) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:39655 remote:104.30.145.173:9824 id:1dee132f3b3a772600f32298
I (59588) AGENT: 0 send indication bind request

I (60047) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:39655 remote:104.30.145.173:9824 id:1ae53a307c418dd42170b934
I (60048) AGENT: 0 send indication bind request

I (60356) test: Peer state changed: 7```

</details>

[TempoTian]

You can use wireshark to check the following stun binding details, I see esp32s3 send stun binding but peer not responsed, also not receive peer stun binding request also. Maybe peer not ready for connection?

[Alan5142]

The first picture is from the ESP32 S3 client.

The second picture is from the PC client

If needed, this is my esp_peer configuration:

esp_peer_default_cfg_t extra_peer_cfg = {};
extra_peer_cfg.data_ch_cfg.recv_cache_size = 1536;
extra_peer_cfg.data_ch_cfg.send_cache_size = 1536;
extra_peer_cfg.agent_recv_timeout = 10000;

esp_peer_cfg_t peer_cfg = {};
peer_cfg.server_lists = ice_servers.data();
peer_cfg.server_num = static_cast<uint8_t>(ice_servers.size());
peer_cfg.role = ESP_PEER_ROLE_CONTROLLING;
peer_cfg.ice_trans_policy = ESP_PEER_ICE_TRANS_POLICY_RELAY;
peer_cfg.audio_info.codec = ESP_PEER_AUDIO_CODEC_NONE;
peer_cfg.video_info.codec = ESP_PEER_VIDEO_CODEC_NONE;
peer_cfg.audio_dir = ESP_PEER_MEDIA_DIR_NONE;
peer_cfg.video_dir = ESP_PEER_MEDIA_DIR_NONE;
peer_cfg.enable_data_channel = true;
peer_cfg.ctx = this;
peer_cfg.on_state = state_callback;
peer_cfg.on_msg = msg_callback;
peer_cfg.on_data = data_callback;
peer_cfg.extra_cfg = &extra_peer_cfg;
peer_cfg.extra_size = sizeof(extra_peer_cfg);
peer_cfg.no_auto_reconnect = false;
peer_cfg.manual_ch_create = false;

[Alan5142]

As additional information, when the type is "All" it works when both are in the same network, and the logs are the following:

I (32132) AGENT: 0 Select pair192.168.137.1:64021
I (32134) AGENT: 0 Send binding request (cand:1) local:192.168.137.140:49735 remote:192.168.137.1:64021 id:55365135794f06e57091758f
I (32147) AGENT: 0 PeerBinding recv local:192.168.137.140:49735 remote:192.168.137.1:64021
I (32154) AGENT: 0 Send binding response local:192.168.137.140:49735 remote:192.168.137.1:64021
I (32163) AGENT: 0 PeerBinding recv local:192.168.137.140:49735 remote:192.168.137.1:64021
I (32170) AGENT: 0 Send binding response local:192.168.137.140:49735 remote:192.168.137.1:64021
E (32180) AGENT: 0 Not found for bind remote 192.168.137.1:64026
E (32185) AGENT: 0 Not found for bind remote 192.168.137.1:64030
E (32191) AGENT: 0 Not found for bind remote 192.168.137.1:64037
I (32197) AGENT: 0 PeerBinding recv local:192.168.137.140:49735 remote:192.168.100.36:64031
I (32205) AGENT: 0 PeerBinding recv local:192.168.137.140:49735 remote:192.168.137.1:64021
I (32212) AGENT: 0 Send binding response local:192.168.137.140:49735 remote:192.168.137.1:64021
E (32221) AGENT: 0 Not found for bind remote 192.168.137.1:64026
E (32227) AGENT: 0 Not found for bind remote 192.168.137.1:64030
E (32232) AGENT: 0 Not found for bind remote 192.168.137.1:64037
I (32238) AGENT: 0 PeerBinding recv local:192.168.137.140:49735 remote:192.168.100.36:64031
I (32247) AGENT: 0 Candidate responsed
I (32249) AGENT: 0 Connection OK 192.168.137.1:64021
I (32253) test: Peer state changed: 5
I (32257) test: Peer connecting
I (32260) DTLS: Start to do server handshake
I (32491) DTLS: SRTP connected OK
I (32495) DTLS: Server handshake success
I (32496) PEER_DEF: DTLS handshake success
I (32496) PEER_DEF: Sctp role as 0
I (32496) test: Peer state changed: 6
I (32498) test: Peer connected

[TempoTian]

When set with all policy, I see it use local candidate. And peer binding is sent, also responsed for binding request. I see one issue is that why server return 41076 for both client when use TURN server?

[Alan5142]

For the response code, I'm not sure why it returns 401. I tested with the credentials that the cloudflare API returns in WebRTC Trickle ICE sample and it successfully maps to an address port

Here's one of the responses from the cloudflare API:

{
    "iceServers": [
        {
            "urls": [
                "stun:stun.cloudflare.com:3478",
                "stun:stun.cloudflare.com:53"
            ]
        },
        {
            "urls": [
                "turn:turn.cloudflare.com:3478?transport=udp",
                "turn:turn.cloudflare.com:3478?transport=tcp",
                "turns:turn.cloudflare.com:5349?transport=tcp",
                "turn:turn.cloudflare.com:53?transport=udp",
                "turn:turn.cloudflare.com:80?transport=tcp",
                "turns:turn.cloudflare.com:443?transport=tcp"
            ],
            "username": "XXXXXXXXXXXXXXXXXXXXXX",
            "credential": "YYYYYYYYYYYYYYYYYYYYYYY"
        }
    ]
}

[TempoTian]

I think maybe webrtc.rs has bug, I see that its turn relay address is 41076, and esp32s3 relay address is 42542. When send indication and create permission it should use peer port instead of its own port 41076.

[Alan5142]

Thanks, I'll check with a web browser to confirm the behavior!

[TempoTian]

PS: For simple test you can also use 2 esp32s3 board to test, one configured as controlling one as controlled, it can easy verify.

[Alan5142]

Hello again!

Since I only have a pair of ESP32 C5 laying around, I have decided to test the doorbell local demo but specifying the TURN server.
Below are my modifications to the files:
webrtc_test.html:

const configuration = {
                iceServers: [
                    {
                        urls: [
                            'stun:stun.l.google.com:19302',
                            'stun:stun1.l.google.com:19302'
                        ]
                    },
                    {
                        urls: 'turn:turn.cloudflare.com:3478?transport=udp',
                        username: 'XXXX',
                        credential: 'YYYY'
                    }
                ],
                iceCandidatePoolSize: 10,
                bundlePolicy: 'max-bundle',
                rtcpMuxPolicy: 'require',
                sdpSemantics: 'unified-plan',
                iceTransportPolicy: 'relay' // Force use of TURN server
            };

And webrtc_http_server.c

esp_peer_signaling_ice_info_t ice_info = {
        .is_initiator = true,
        .server_info.stun_url = "stun:stun.l.google.com:19302",
    };
    // Notify for rule
    sig_cfg.on_ice_info(&ice_info, cfg->ctx);
    esp_peer_signaling_ice_info_t turn_info = {
        .is_initiator = true,
        .server_info.stun_url = "turn:turn.cloudflare.com:3478?transport=udp",
        .server_info.user = "XXX",
        .server_info.psw = "YYY",
    };
    sig_cfg.on_ice_info(&turn_info, cfg->ctx);

It produces the same result as my test . I have a question, is there a fixed size for the user and psw fields?, cloudflare returns a user and a credential with a length of 64 characters, so I don't know if this might generate an issue

I (2793) Webrtc_Test: Use browser to enter https://192.168.137.161/webrtc/test for test
I (2799) AV_RENDER: Adec got msg:Close
I (2800) AV_RENDER: Thread Adec exited
I (2800) AV_RENDER: Close done
I (10069) esp_https_server: performing session handshake
I (10564) wifi:<ba-add>idx:0 (ifx:0, b2:dc:ef:91:09:d8), tid:0, ssn:12, winSize:64
I (10878) esp_https_server: performing session handshake
Get post request
Request length 42
Get post {"type":"customized","data":"ACCEPT_CALL"}
I (25277) webrtc: Received customized data
I (25277) DOOR_BELL: Receive command ACCEPT_CALL
I (25290) DTLS: Init SRTP OK
I (26416) webrtc: peer_connection_task started
I (26416) webrtc: PeerConnectionState: 2
I (26418) AGENT: Start agent as Controlling
I (26419) PEER_DEF: Start DTLS role as 1
I (26450) AGENT: Send STUN binding request
I (26451) AGENT: Send allocate now
Got error code 401
I (26460) AGENT: Send allocate now
I (26462) AGENT: Send allocate now
I (26467) AGENT: 0 Get candidate success user:g0952d8c29d6011b448ad54fb5ae1f41b3b01fba768541f8e3685a1e963fa11e psw:0efb42a3c387809303faeb61a0e3e79b4ddd11c60a940fcac426d9bad027355d
Add audio codec 5 sample_rate 8000
E (26481) AV_RENDER: Video render not set, stream is skipped
E (26481) AV_RENDER: Fail to add video stream 262
I (26492) webrtc: Send client sdp: v=0
o=- 7801614086411001801 2 IN IP4 0.0.0.0
s=-
t=0 0
a=msid-semantic: esp-webrtc
a=group:BUNDLE 0 1 2
m=audio 9 UDP/TLS/RTP/SAVPF 8
c=IN IP4 0.0.0.0
a=mid:0
a=sendrecv
a=rtcp-mux
a=rtpmap:8 PCMA/8000
a=ssrc:4 cname:EspSSpbA0
a=fingerprint:sha-256 2E:8F:23:90:EF:02:76:35:99:26:A6:CD:D9:AF:79:93:A1:32:85:0D:5E:1D:94:27:B0:49:CB:F5:93:00:53:B2
a=setup:passive
a=ice-ufrag:WwUl
a=ice-pwd:Pd9ZwfQgpeN3WiStdYMx5Ru0
a=candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host
a=candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0
a=candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0
m=video 9 UDP/TLS/RTP/SAVPF 102 106
a=rtpmap:102 H264/90000
a=rtcp-fb:102 goog-remb
a=rtcp-fb:102 transport-cc
a=rtcp-fb:102 ccm fir
a=rtcp-fb:102 nack
a=rtcp-fb:102 nack pli
a=fmtp:102 level-asymmetry-allowed=1
a=rtpmap:106 H264/90000
a=rtcp-fb:106 goog-remb
a=rtcp-fb:106 transport-cc
a=rtcp-fb:106 ccm fir
a=rtcp-fb:106 nack
a=rtcp-fb:106 nack pli
a=fmtp:106 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=4d001f
a=ssrc:1 cname:webrtc-h264
a=sendrecv
a=mid:1
c=IN IP4 0.0.0.0
a=rtcp-mux
a=fingerprint:sha-256 2E:8F:23:90:EF:02:76:35:99:26:A6:CD:D9:AF:79:93:A1:32:85:0D:5E:1D:94:27:B0:49:CB:F5:93:00:53:B2
a=setup:passive
a=ice-ufrag:WwUl
a=ice-pwd:Pd9ZwfQgpeN3WiStdYMx5Ru0
a=candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host
a=candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0
a=candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0
m=application 50712 UDP/DTLS/SCTP webrtc-datachannel
a=mid:2
a=sctp-port:5000
c=IN IP4 0.0.0.0
a=max-message-size:262144
a=fingerprint:sha-256 2E:8F:23:90:EF:02:76:35:99:26:A6:CD:D9:AF:79:93:A1:32:85:0D:5E:1D:94:27:B0:49:CB:F5:93:00:53:B2
a=setup:passive
a=ice-ufrag:WwUl
a=ice-pwd:Pd9ZwfQgpeN3WiStdYMx5Ru0
a=candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host
a=candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0
a=candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0


Received {"type":"offer","sdp":"v=0\r\no=- 7801614086411001801 2 IN IP4 0.0.0.0\r\ns=-\r\nt=0 0\r\na=msid-semantic: esp-webrtc\r\na=group:BUNDLE 0 1 2\r\nm=audio 9 UDP/TLS/RTP/SAVPF 8\r\nc=IN IP4 0.0.0.0\r\na=mid:0\r\na=sendrecv\r\na=rtcp-mux\r\na=rtpmap:8 PCMA/8000\r\na=ssrc:4 cname:EspSSpbA0\r\na=fingerprint:sha-256 2E:8F:23:90:EF:02:76:35:99:26:A6:CD:D9:AF:79:93:A1:32:85:0D:5E:1D:94:27:B0:49:CB:F5:93:00:53:B2\r\na=setup:passive\r\na=ice-ufrag:WwUl\r\na=ice-pwd:Pd9ZwfQgpeN3WiStdYMx5Ru0\r\na=candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host\r\na=candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0\r\na=candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0\r\nm=video 9 UDP/TLS/RTP/SAVPF 102 106\r\na=rtpmap:102 H264/90000\r\na=rtcp-fb:102 goog-remb\r\na=rtcp-fb:102 transport-cc\r\na=rtcp-fb:102 ccm fir\r\na=rtcp-fb:102 nack\r\na=rtcp-fb:102 nack pli\r\na=fmtp:102 level-asymmetry-allowed=1\r\na=rtpmap:106 H264/90000\r\na=rtcp-fb:106 goog-remb\r\na=rtcp-fb:106 transport-cc\r\na=rtcp-fb:106 ccm fir\r\na=rtcp-fb:106 nack\r\na=rtcp-fb:106 nack pli\r\na=fmtp:106 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=4d001f\r\na=ssrc:1 cname:webrtc-h264\r\na=sendrecv\r\na=mid:1\r\nc=IN IP4 0.0.0.0\r\na=rtcp-mux\r\na=fingerprint:sha-256 2E:8F:23:90:EF:02:76:35:99:26:A6:CD:D9:AF:79:93:A1:32:85:0D:5E:1D:94:27:B0:49:CB:F5:93:00:53:B2\r\na=setup:passive\r\na=ice-ufrag:WwUl\r\na=ice-pwd:Pd9ZwfQgpeN3WiStdYMx5Ru0\r\na=candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host\r\na=candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0\r\na=candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0\r\nm=application 50712 UDP/DTLS/SCTP webrtc-datachannel\r\na=mid:2\r\na=sctp-port:5000\r\nc=IN IP4 0.0.0.0\r\na=max-message-size:262144\r\na=fingerprint:sha-256 2E:8F:23:90:EF:02:76:35:99:26:A6:CD:D9:AF:79:93:A1:32:85:0D:5E:1D:94:27:B0:49:CB:F5:93:00:53:B2\r\na=setup:passive\r\na=ice-ufrag:WwUl\r\na=ice-pwd:Pd9ZwfQgpeN3WiStdYMx5Ru0\r\na=candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host\r\na=candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0\r\na=candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0\r\n"}
Got error code 437
Received {"type":"candidate","candidate":"candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host"}
Received {"type":"candidate","candidate":"candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0"}
Received {"type":"candidate","candidate":"candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0"}
Received {"type":"candidate","candidate":"candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host"}
Get post request
Request length 1470
Get post {"type":"answer","sdp":"v=0\r\no=mozilla...THIS_IS_SDPARTA-99.0 7189392950720999208 0 IN IP4 0.0.0.0\r\ns=-\r\nt=0 0\r\na=fingerprint:sha-256 AB:7F:6E:D7:0F:7A:72:65:0A:72:B1:AF:0B:77:9D:2F:B5:47:22:A2:0F:40:B1:6D:7C:4D:1C:D0:D6:BC:66:97\r\na=group:BUNDLE 0 1 2\r\na=ice-options:trickle\r\na=msid-semantic:WMS *\r\nm=audio 9 UDP/TLS/RTP/SAVPF 8\r\nc=IN IP4 0.0.0.0\r\na=sendrecv\r\na=ice-pwd:62594fac3e8d80f6be03a9c22d06732e\r\na=ice-ufrag:1606d4ab\r\na=mid:0\r\na=msid:{763d30c7-375f-48f5-b4c7-5b966defc7b8} {467253f2-ef90-406f-9bd8-2af95cc7e794}\r\na=rtcp-mux\r\na=rtpmap:8 PCMA/8000\r\na=setup:active\r\na=ssrc:2947829102 cname:{d3c19287-f867-4d16-b0b7-d3eee33848f9}\r\nm=video 9 UDP/TLS/RTP/SAVPF 102\r\nc=IN IP4 0.0.0.0\r\na=sendrecv\r\na=fmtp:102 profile-level-id=42001f;level-asymmetry-allowed=1\r\na=ice-pwd:62594fac3e8d80f6be03a9c22d06732e\r\na=ice-ufrag:1606d4ab\r\na=mid:1\r\na=msid:{763d30c7-375f-48f5-b4c7-5b966defc7b8} {397685ef-1aa4-453d-ac57-33c7bf6ec6bb}\r\na=rtcp-fb:102 nack\r\na=rtcp-fb:102 nack pli\r\na=rtcp-fb:102 ccm fir\r\na=rtcp-fb:102 goog-remb\r\na=rtcp-fb:102 transport-cc\r\na=rtcp-mux\r\na=rtpmap:102 H264/90000\r\na=setup:active\r\na=ssrc:1571010988 cname:{d3c19287-f867-4d16-b0b7-d3eee33848f9}\r\nm=application 9 UDP/DTLS/SCTP webrtc-datachannel\r\nc=IN IP4 0.0.0.0\r\na=sendrecv\r\na=ice-pwd:62594fac3e8d80f6be03a9c22d06732e\r\na=ice-ufrag:1606d4ab\r\na=mid:2\r\na=setup:active\r\na=sctp-port:5000\r\na=max-message-size:1073741823\r\n"}
I (26964) wifi:<ba-add>idx:1 (ifx:0, b2:dc:ef:91:09:d8), tid:5, ssn:4, winSize:64
Received {"type":"candidate","candidate":"candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0"}
I (27063) PEER_DEF: Get peer role 0
Received {"type":"candidate","candidate":"candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0"}
I (27086) PEER_DEF: A SRC: 2947829102
I (27098) PEER_DEF: Select H264 102
Received {"type":"candidate","candidate":"candidate:0 1 UDP 2129656063 192.168.137.161 61432 typ host"}
I (27099) PEER_DEF: Get peer role 0
I (27111) PEER_DEF: V SRC: 1571010988
Received {"type":"candidate","candidate":"candidate:1 1 UDP 1693714687 XXX.XXX.XXX.XXX 62472 typ srflx raddr 0.0.0.0 rport 0"}
I (27111) PEER_DEF: Get peer role 0
Received {"type":"candidate","candidate":"candidate:2 1 UDP 12808959 104.30.145.172 50034 typ relay raddr 0.0.0.0 rport 0"}
SDP not contain candidate continue
I (27407) esp_https_server: performing session handshake
I (28003) esp_https_server: performing session handshake
Get post request
Request length 156
Get post {"type":"candidate","candidate":"candidate:0 1 UDP 92151807 104.30.145.172 59722 typ relay raddr 104.30.145.172 rport 59722","sdpMid":"0","sdpMLineIndex":0}
I (28935) AGENT: 0 Add remote type:4 104.30.145.172:59722
0 Sorted pair 0 type: 4 local:104.30.145.172:50034 Remote:104.30.145.172:59722
I (28937) webrtc: PeerConnectionState: 3
I (28951) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:50034 remote:104.30.145.172:59722 id:4c598d93643bd7252b449456
I (28953) AGENT: 0 send indication bind request

I (28957) esp_https_server: performing session handshake
I (29450) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:50034 remote:104.30.145.172:59722 id:6db505597d157d8d71dfed43
I (29451) AGENT: 0 send indication bind request

I (29558) esp_https_server: performing session handshake
I (29949) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:50034 remote:104.30.145.172:59722 id:666d97166fd595896931589d
I (29950) AGENT: 0 send indication bind request

Get post request
Request length 66
Get post {"type":"candidate","candidate":"","sdpMid":"0","sdpMLineIndex":0}
I (30447) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:50034 remote:104.30.145.172:59722 id:1dee132f3b3a772600f32298
I (30449) AGENT: 0 send indication bind request

I (30944) AGENT: 0 Send binding request (cand:0) local:104.30.145.172:50034 remote:104.30.145.172:59722 id:1ae53a307c418dd42170b934
I (30946) AGENT: 0 send indication bind request

I (31119) webrtc: PeerConnectionState: 7
Get post request
Request length 40
Get post {"type":"customized","data":"DENY_CALL"}
I (31949) webrtc: Received customized data
I (31950) DOOR_BELL: Receive command DENY_CALL
I (31961) AV_RENDER: Adec got msg:Close
I (31961) AV_RENDER: Thread Adec exited
I (31962) AV_RENDER: Close done
I (31973) webrtc: PeerConnectionState: 1
I (31973) AV_RENDER: Close done
I (31974) AGENT: agent_tDisconnected done