Timecode of order

Hi! I have WowzaMS3 mountly license

120 live streams, customers looking cupertino streams, average connections is 800, and sometime in errorlog i got that message:

WARN server comment 2011-12-18 21:50:10 - - - - - 41898.892 - - - - - - - -CupertinoPacketHandler.handlePacket[live/definst/live1.stream]: Timecode out of order [audio]: 15:16777210

WARN server comment 2011-12-18 21:50:10 - - - - - 41898.892 - - - - - - - -SanJosePacketHandler.handlePacket[live/definst/live1.stream]: Timecode out of order [audio]: 15:16777210

WARN server comment 2011-12-18 21:50:10 - - - - - 41898.99 - - - - - - - -CupertinoPacketHandler.handlePacket[live/definst/live1.stream]: Timecode out of order [video]: 26:16777202

WARN server comment 2011-12-18 21:50:10 - - - - - 41898.99 - - - - - - - -SanJosePacketHandler.handlePacket[live/definst/live1.stream]: Timecode out of order [video]: 26:16777202

WARN server comment 2011-12-18 21:50:10 - - - - - 41899.105 - - - - - - - -CupertinoPacketHandler.resetStream[live/definst/live1.stream][11:5]: Timecodes jumped back in time.

WARN server comment 2011-12-18 21:50:10 - - - - - 41899.105 - - - - - - - -SanJosePacketHandler.resetStream[live/definst/live1.stream][11:5]: Timecodes jumped back in time.

What it can be?

Hi

There could are generally two reasons for this and they are

  1. your network is too busy and you are suffering from packed loss

  2. your sever is overworked and can’t process the packets in time.

An unlikely but still possible reason could be that your source stream is broken but I don’t think that it is in this case.

Jason

Hi

There could are generally two reasons for this and they are

  1. your network is too busy and you are suffering from packed loss

  2. your sever is overworked and can’t process the packets in time.

An unlikely but still possible reason could be that your source stream is broken but I don’t think that it is in this case.

Jason

How can I be sure what is the real problem?