Facing TCP connection closed by client (callback)

[Hemrajsinh Gharia]

Hello community,

We have WebRTC audio SFU app. And we are using Coturn. Following is my Coturn config file:

listening-port=443
external-ip=<public_ip>/<private_ip>

min-port=49152

max-port=65535

verbose

fingerprint
use-auth-secret
realm=my-app

Generating time bases credentials using shared auth secret from our app. But having random users complaining that they don't receive audio stream. So I assume they must be behind a restrictive network. When I checked Coturn logs, I found a lot of logs saying TCP connection closed by client (callback)

1262339: session 001000000000039061: new, realm=<bz-squawk>, username=<1591377197:R2syNB6G5XJWvHbBo+YK0u0UD/w=>, lifetime=600

1262339: session 001000000000039061: realm <bz-squawk> user <1591377197:R2syNB6G5XJWvHbBo+YK0u0UD/w=>: incoming packet ALLOCATE processed, success

1262383: session 001000000000039061: refreshed, realm=<bz-squawk>, username=<1591377197:R2syNB6G5XJWvHbBo+YK0u0UD/w=>, lifetime=0

1262383: session 001000000000039061: realm <bz-squawk> user <1591377197:R2syNB6G5XJWvHbBo+YK0u0UD/w=>: incoming packet REFRESH processed, success

1262383: session 001000000000039061: closed (2nd stage), user <1591377197:R2syNB6G5XJWvHbBo+YK0u0UD/w=> realm <bz-squawk> origin <>, local 10.0.1.10:443, remote 64.201.201.235:57912, reason: TCP connection closed by client (callback)

1262383: session 001000000000039061: delete: realm=<bz-squawk>, username=<1591377197:R2syNB6G5XJWvHbBo+YK0u0UD/w=>

Coturn config doesn't have any certificate file configured. We have FQDN setup which looks like turn:turn.ourcompany.com:443?transport=tcp. But I think I am missing something in Coturn config. 

Appreciate it if anyone can help here.

Note: I have tested ICE candidate gathering at https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/. It looks fine, just getting below error:

Note: errors from onicecandidateerror above are not neccessarily fatal. For example an IPv6 DNS lookup may fail but relay candidates can still be gathered via IPv4.

Thanks,

Hemraj

[Amit Kumar Pandey]

check you configuration is correct  using  static user in  turnserver.con file

https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

allow specify listening IP in conf file., if it AWS then ip will be private IP else Public IP

[Hemrajsinh Gharia]

Hey Amit, 

Thanks for the response. And yeah I tested it. Added the test result in my post. I get authenticated using dynamically generated credentials, no problem there. Should I test any specifics?

Thanks,

Hemraj

[Hemrajsinh Gharia]

Following was my results from testing at https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/. Does it sound problematic?

[Hemrajsinh Gharia]

Also tried with https://test.webrtc.org/ with adding our Coturn server details. And getting reflexive connectivity Timeout.

Anyone had any suggestions ho to fix this?

Thanks