Subscriber ice restart ends with “ICE failed” error

[Vladislav]

Hi everyone,

I use videoroom plugin and I faced with problem — when subscriber peerconnection make ice restart, then Janus return error «ICE failed» in some tries. I make subscriber ice restart by command «configure» with extra parameter `"restart": true`. In this case janus.log contains errors:

[WARN] [4633725731189708] ICE restart detected

[WARN] [4633725731189708] Not video and not audio? dropping (SSRC 304710182)...

[WARN] [4633725731189708] Not video and not audio? dropping (SSRC 3565448127)...

[WARN] [4633725731189708] Not video and not audio? dropping (SSRC 2310333270)...

[WARN] [4633725731189708] Not video and not audio? dropping (SSRC 3657009250)...

[WARN] [4633725731189708] Not video and not audio? dropping (SSRC 2193060075)...

[WARN] [4633725731189708] ICE failed for component 1 in stream 1, but let's give it some time... (trickle received, answer received, alert not set)

[WARN] [4633725731189708] Not video and not audio? dropping (SSRC 2689878632)...

[WARN] [4633725731189708] ICE failed for component 1 in stream 1, but let's give it some time... (trickle received, answer received, alert not set)

[WARN] [4633725731189708] Not video and not audio? dropping (SSRC 2019008213)...

[WARN] [4633725731189708] ICE failed for component 1 in stream 1, but let's give it some time... (trickle received, answer received, alert not set)

[ERR] [ice.c:janus_ice_check_failed:1692] [4633725731189708] ICE failed for component 1 in stream 1...

I watched place in code, where janus write log «Not video and not audio» and I did saw that janus expect RTP packet from recvonly subscriber peerconnection. Is this behavior normal?

Also, I have logs of Admin API response, but I don't understand how to diagnose problem.