Packet loss - what can i do ??

Wowza Streaming Engine
1

hi, guys

i use RTSP/RTP streaming.

sometimes i meet packet loss.

WARN server comment 2015-08-24 01:15:05 - - - - - 338263.513 - - - - - - - - RTPDePacketizerWrapperPacketSorter.packetLoss[live/definst/1000:trackID=0]: last:551 curr:1170

so, i check any method…

https://www.wowza.com/docs/how-to-turn-on-an-rtp-jitter-buffer-and-packet-loss-logging-rtp-and-mpeg-ts

https://www.wowza.com/docs/how-to-fix-udp-packet-loss-mpeg-ts-rtp

but, i still have same trouble.

what can i do another action?

2

Is it possible you have another encoder on the same network pushing packets for the same channels, which could be causing a conflict? This behavior makes it look like some streams are losing packets.

Do you see multiple errors like this:

server  WARN    200 - RTPDePacketizerWrapperPacketSorter.packetLoss\[live/_definst_/streamOne.sdp:trackID=2\]: last:13066 curr:25584    
server  WARN    200 - RTPDePacketizerWrapperPacketSorter.packetLoss\[live/_definst_/streamTwo.sdp:trackID=1\]: last:63732 curr:14634

Another troubleshooting tip: Note the big discrepancy between the last and current values. If RTP, the values should be similar. The packet sorter only works if the stream is RTP. We use a sequence number in the RTP header to do packet re-ordering. Because the numbers are so far apart, it most likely means that the stream in question isn’t RTP. Possibly the stream(s) that are causing these issues are MPEG-TS that aren’t RTP-wrapped.

Regards,

Salvadore

3

Hi,

If you have not done so, please do send a support request with a zip copy of your Wowza conf/logs, since as Salvadore pointed out, the last and current values in the RTPDePacketizer is pointing to an issue in how your encoder’s stream is being recognized in your Wowza server.

Michelle

4

Thanks, salvadore.

but I use only one stream and channel.

and I definitely use RTP.