Closed venkateshcontus closed 2 months ago
I can see that your endpoints (both client and server) are generating A LOT of candidates of different types (v4, v6, tcp, relay etc.). Try to limit the interfaces / kinds and see if that helps with your iOS client.
Said that, ICE failures are almost always due to specific network scenarios and clients/server configuration. This is not an issue and should be discussed on the discourse group.
What version of Janus is this happening on? 1.2.3
Have you tested a more recent version of Janus too? Yes
Was this working before?
Is there a gdb or libasan trace of the issue? not sure
Additional context Users in Call :UserA(iOS Caller), UserB(Android),UserC(iOS), UserD(iOS) After UserA Initiated the call the rest of the users attended the call at the same time. UserA able to receives publisher list of rest of the users Meanwhile after sending candidates to Janus and adding candidates received from the janus server to own peerconnection After the ice checking state, ice failed trigger for the caller.
I have attached the logs.
Copy of iOS Trickle Logs.txt