- Alarms and Relays
- Video Analytics
- Web Service Specific Issues
- Audio Stream
- API Access Blocked
- Live Stream Web Page No Longer Accessible
- Internet Explorer (IE)
- TCP JPEG Streaming
- MotionDetection ClearMDRegions
- Default Key Frame Interval
Alarms and Relays
Relays Are Not Fully Operational
In Sarix devices with firmware older than 1.7, relays do not seem to be fully operational; only "pulse" and the ON/OFF/TOGGLE modes seemed to work. To resolve this issue, please upgrade your Sarix device's firmware to 1.7 or above.
Sarix's D-Bus interface, for alarm configuration, exposes a single boolean parameter called active_low. The active_low parameter helps users determine which of the (non-supervised) alarm states should be considered _triggered_. There are two states for non-supervised alarms:
- The first state is when the alarm's circuit is complete, or closed. When the circuit is closed, the voltage is said to be high.
- The second state is when the alarm's circuit is not complete, or open. When the circuit is open, and the voltage is said to be low.
When the active_low parameter is true, it means that:
- When the alarm's voltage is low (i.e. when the circuit is incomplete, or open), then the alarm is considered to be _triggered_
- When the alarm's voltage is high (i.e. when the circuit is complete, or closed) then the alarm is considered to be _normal_.
Alarm and Relay base64 Encoding
Sarix base64 encoding for alarm and relay arrays mostly adheres to the standard. However it diverves from the standard in that it will always append an equal sign (=) regardless of whether or not it was necessary.
When a Sarix based IP camera renews its DHCP lease, it is requests a new IP address and lease; instead of renewing its previous IP address. This only affects Sarix IP cameras on firmware version 1.6 and below.
Sarix cameras, including IP cameras like Spectra HD which uses the Sarix platform, cannot have a GOP setting of less than 4. The reason for this is that IBP encoding requires multiple of 4.
Not all Sarix IP cameras support Pelco Analytics (the VideoAnalytics service). Refer to your camera specification sheet for details.
Web Service Specific Issues
For issues that are specific to a particular web service such as StreamConfiguration, StreamDiscovery, or other Sarix supported Pelco web services. Refer to their respective issues pages for details on issues such as deprecated actions.
Sarix IP cameras have non-standard RTP audio stream. It uses G.711, supporting only u-law coding. Only the first 400 bytes are valid encoded u-law which results in having an RTP payload type of '96'.
API Access Blocked
If your Sarix IP camera has denied API access, then change the Public View Access Level (within the Sarix web application) to _Viewers_ and the Sarix API will be accessible again.
Live Stream Web Page No Longer Accessible
If you are experiencing an issue where only users who are logged into the Sarix IP camera web application, can view its live streams; then change the(within the Sarix web application) to and the live stream web page will be accessible again.
While it is possible to display video using the Pelco API's VideoInput service, this is no longer the preferred method for displaying video. RTSP streaming's wide industry acceptance, ease of use, along with Sarix's support; make RTSP the preferred approach for video display.
Current options include (but are not limited to) the following:
- VLC --- an open source media player that is cross platform
- live555 --- a set of open source C\+\+ RTSP libraries
- PelcoAPIViewer--- Pelco's video client reference implementation
Download and install an RTSP client or library that caters to your organization's needs.
H.264 compliant decoders should not have any issues with this change. However problems may arise for applications only searching for non-IDR I frames. Specifically applications parsing video streams should now search a nal_unit_type of either Non-IDR (0x1) or an IDR (0x5). An I-slice should be followed by these nal_unit_types.
Internet Explorer (IE)
TCP JPEG Streaming
Sarix cameras currently do not support the "server push" model for retrieving JPEGs. Clients must make a separate request for each JPEG.
To see the MotionDetection service through UPnP and use it, the MotionDetection service must be enabled using either the CameraConfiguration Web Service (specifically the CameraConfiguration element) or Workstation.
Please refer to the ClearMDRegions entry in the MotionDetection Issues section.
Hue configuration is currently not supported. Any related calls to the Endura API will not change hue values.
Default Key Frame Interval
The default Key Frame Interval is 0.50 seconds when the camera is configured for 30 FPS.
The default Key Frame Interval is configurable using the StreamConfiguration Web Service, through the GOP and framerate values. Simply divide the framerate with the GOP to get the number of Key Frames per second. For example, if the camera is configured for 30 FPS with a GOP of 15, then there are 2 Key Frames per second.