To locate code stream problems, you need to specify the callID of the call.
Find the callID of the call based on the previous signaling or log analysis.
Search for callID to find the following log. In this example, the value of callID is ZjE0NjVhNDk1ZWIzMzEwMjMzMTZhZTNkOGFjNjEzZWI.
If the call is a SIP call, use the session field in callID to search for the call. If the call is an H.323 call, search the callID file for the log.
Then, you can find the session field that is the same as that of SIP in the next log of the log.
Search for the keyword 65556 in the session field.
After the preceding information is found, you can obtain the local media address, port number, and remote media address and port of the SC.
mediaType<0> is a video, <1> audio, <2> data, and <3> presentation.
If there is no stream, check whether the SC receives the stream. If the SC does not receive the stream, the receiver of the stream cannot receive the stream.
Search for the ID<1> field in the preceding figure. The keyword is FlowID<1>. Pay attention to the alignment time to ensure that the same route is displayed.
ID<1> indicates the video address and port used by the SC to communicate with the 192.168.3.94. ID<7> indicates the video address and port used by the SC to communicate with the 192.168.3.7.
Run the FlowID<7> command to view the video address and port number for interworking with the 192.168.3.7.
Pay attention to the alignment time to ensure that the call is a call. If such a log is displayed, it indicates that the video code stream of 192.168.3.7 is received. If no log about the code stream of the peer end is recorded at this time point, no code stream problem occurs because the SC does not receive the code stream from the peer end.
Check the network and check whether the code stream ports are open.
In the new version, whether there are clear log records of receiving and sending code streams is added.
