The New 2.2 release of OpsCenter has more specific messages to help us diagnose streaming errors
Pelco Video Management
Previous error messages were vague making it difficult to diagnose
Several new error messages have been added to OpsCenter for the VxE 2.1 release. In most of the cases where the previous OpsCenter release would have shown the generic message, “Cannot Connect,” the new version will provide a more specific error message. The goal is to help customers and tech support diagnose common field issues and thereby reduce support costs.
Errors that could be seen if a stream immediately fails to start:
Message: Low system memory available. Stream could not start.
Condition: Shown if the user attemps to start a new stream when there is not enough available system memory. This is currently set to disable new streams when the available system memorydrops below 1GB.
Message: Video source is offline
Condition: Shown when the selected source is known to be offline. In this case it should also be marked as offline in the source list.
Message: RTSP connection could not be established
Condition: Shown if the player couldn't communicate with the RTSP server at all (i.e. couldn't establish a TCP connection with the RTSP server). This would happen if, say, the RTSP server (e.g., MGW) is offline.
Message: RTSP connection failure
Condition: Shown if there is failure to send or receive a message to/from the RTSP server. This could happen if the RTSP server went offline during interaction with the client, after a TCP connection had been established.
Message: Unknown RTSP error
Condition: Shown when an unknown RTSP error occurs. This would happen if something really unexpected happened during the RTSP protocol and we didn't get any error code from the RTSP server.
Message: Could not start the stream. Camera may be offline.
Condition: Shown when a specific RTSP error (502) happens, indicating that our RTSP server believes the camera has gone offline.
Message: Streaming server reported an error.
Condition: Shown when the RTSP protocol (or HTTP in the case of JPEG sources) fails with an error code other than 502. This error includes an extra tooltip, which the user can hover over to get more information.
Possible tooltip strings are:
· RTSP error
· HTTP error
· No additional detail available.
Errors that could be seen if a stream can be started, but fails soon thereafter:
Message: No UDP packets received
Condition: Shown when no UDP packets are received for 5 seconds after successfully starting an RTSP session. This is N/A for playback, but for live streaming it could indicate a networking problem (e.g., multicast configuration), or it could indicate a performance problem with the RTSP server.
Message: Low network throughput between your computer and the source.
Condition: when packets are being received, but the bandwidth is insufficient to decode/display frames at the expected rate.
Message: Network connection to source is broken
Condition: Shown when the network connection to the source is broken. This would be seen if the decoder stopped receiving data after it had started.
Message: Source stream data corrupt
Condition: Shown when data within the stream is corrupt, malformed or does not conform to spec. This is a problem with the source content itself. Note that network data loss would not cause this error, as that's identified in other ways.
Message: Video player cannot stream due to limited hardware resources
Condition: Shown when client hardware resources (e.g., available DirectX session handles) have been exhausted. This message was added to handle the 8x8 layout, for which some PCs that we tested would start getting DirectX resource errors upon trying to launch more than 32 streams or so.
Message: Video player cannot stream due to unsupported graphics adapter
Condition: Shown when the graphics adapter doesn't have sufficient capabilities for the stream type. For example, the Optera and EVO SDKs require certain minimum OpenGL versions.
Other new error messages:
Message: Video player has failed
Condition: Shown when the video player fails (represents a critical internal error).
Message: Cell failed to load; try again.
Condition: Shown when a cell fails to load and requires user intervention to recover. This is an internal error in VxOps that should never occur but if for any reason the cell load process fails, this error will be shown rather than just an empty cell.
Message: Data source has no usable data interfaces
Condition: Shown when a data source is in a cell but it has no streaming end points. This can happen when a connected camera is configured to stream with no supported protocol or transport. It can also happen when a server-side error occurs that causes the list of data interfaces to be empty.