In some occasions, you can have an unwanted "rtp.p_type 97" packed in your video stream.
This "rtp.p_type 97" packed can cause on some decoder Brands (for example Barco) a memory leak.
This article describes the behavior of "rtp.p_type 97" for the following 2 platforms:
How to turn ON/OFF for CPP4 moving camera
Payload Type 97 - RCP+ command to disable/enable the generation and transmission of those packets:
RCP+ CONF_PIC_INFO
Tag Code | NumDes |
Message |
SNMP Support | |
0x0b8e | no | no | no | |
Data type | Access Level |
Description |
||
Read | t_octet | access_right_minimal |
enables/disables the generation of pic info packets |
|
Write | t_octet | access_right_service | enables/disables the generation of pic info packets (payload type 97) |
This RCP+ command was added and available since firmware version 5.80 and per the RCP+ documentation it is still applicable for CPP4 firmware version 7.10.
After sending this command, the “rtp.p_type 97" packet stops
Note:
How to turn ON/OFF for a CPP7.3 moving camera
When choosing the Video Authentication option "SHA-1" , "rtp.p_type 97" will be added to the video stream
But when you turn it OFF again "rtp.p_type 97" will remain ON and doesn't stop, until you have restarted the camera.
Despite the fact of disabling OSD, telemetry feedback, timestamp, and watermarking, the “rtp.p_type 97” continues:
A camera reboot is required when an Authentication other than Watermark is toggled ON and then OFF.
"rtp.p_type 97" can contains OSD information like for example:
Title OSD: Sector or Shot Title
Camera OSD: Digital Zoom, Iris open/close, Focus near/far
OSD User defined 1
OSD User defined 2
OSD User defined 3
Time Information
Hash / Signature Entry