webrtc Exception
SirZiWang opened this issue · 0 comments
exception info:
2024-03-22 08:39:48.566 - INFO: WorkingNode - pid: 11021
2024-03-22 08:39:48.568 - INFO: WorkingNode - Connecting to rabbitMQ server...
2024-03-22 08:39:48.657 - INFO: InternalConnectionFactory - QUIC is not enabled for internal IO
2024-03-22 08:39:48.664 - INFO: WorkingNode - webrtc-1132716084993ee59b80@172.18.0.10_13 as rpc server ready
2024-03-22 08:39:48.668 - INFO: WorkingNode - webrtc-1132716084993ee59b80@172.18.0.10_13 as monitor ready
2024-03-28 06:36:19,927 - WARN: LibNiceConnection - id: a07fd864660b4575aec3967c57f73b00, message: component failed, ice_config_.transport_name: video, componentId: 1
2024-03-28 06:36:19,927 - WARN: IceConnection - id: a07fd864660b4575aec3967c57f73b00, message: Ice Failed
2024-03-28 06:36:19,927 - ERROR: WebRtcConnection - id: a07fd864660b4575aec3967c57f73b00, message: Transport Failed, transportType: video
2024-03-28 06:36:19.927 - WARN: Connection - message: failed the ICE process, code: 502, id: a07fd864660b4575aec3967c57f73b00
2024-03-28 06:36:19.928 - WARN: WrtcConnection - ICE failed, 500 a07fd864660b4575aec3967c57f73b00
2024-03-28 06:36:21,909 - WARN: LibNiceConnection - id: ea9bf4d03ca64b488a701920408bba75, message: component failed, ice_config_.transport_name: video, componentId: 1
2024-03-28 06:36:21,909 - WARN: IceConnection - id: ea9bf4d03ca64b488a701920408bba75, message: Ice Failed
2024-03-28 06:36:21,909 - ERROR: WebRtcConnection - id: ea9bf4d03ca64b488a701920408bba75, message: Transport Failed, transportType: video
2024-03-28 06:36:21.909 - WARN: Connection - message: failed the ICE process, code: 502, id: ea9bf4d03ca64b488a701920408bba75
2024-03-28 06:36:21.909 - WARN: WrtcConnection - ICE failed, 500 ea9bf4d03ca64b488a701920408bba75
2024-04-07 06:55:28.981 - WARN: SdpInfo - Media 0 missing mid
The OWT service occasionally experiences a black screen after running for a period of time, and the log reports the error message as above. Restarting the OWT service resolves the issue and restores normal call functionality. What could be the cause of this?