How to send snapshot image via HTTP when intercom call button is pressed in intercom bell camera
CompletedI'm working with NetworkOptix VMS and trying to configure a camera rule that triggers when the intercom call button is pressed. I know I can set the event type to "Call Button Pressed" and use the "Do HTTP Request" action.
What I want to achieve is:
When the button is pressed, send a snapshot image from the camera via HTTP to an external endpoint.
My questions:
- Is it possible to include a snapshot image in the HTTP request triggered by the camera rule?
- If yes, how can I structure the HTTP request to include the image (e.g., as a URL, base64, or multipart)?
- Do I need to use the Nx REST API to first generate the snapshot and then send it separately?
Any guidance or examples would be greatly appreciated!
i am using AXIS I8116-E for testing
-
if possible if i know how to capture that input from camera event in the plugin code like getting the pushUncompressedVideoFrame metadata, that will be more helpful
0 -
Hi ,
Thanks for your question.
You mentioned the need to send a snapshot image from the camera via HTTP to an external endpoint.
This appears to be a camera-side function, and since you’re specifically referring to an image from the camera, it’s unclear what role you expect Nx Witness to play in this process. If you’re looking to achieve something beyond what the camera already provides, or if you’re referring to integration with Nx Witness in a different context.
If the camera already supports this feature, you may be able to configure it directly by logging into the camera’s web interface and checking its event or rule settings.

Thanks.
0 -
Thanks for your response.
To clarify, my requirement is specifically to send a snapshot image from the VMS (Nx Witness) itself—not directly from the camera. While some cameras may support HTTP push or event-based uploads, I’m looking for a solution that originates from Nx Witness, using any available method (API, event rules, plugins, etc.) when call button on the AXIS I8116-E is pressed. i can make it work in plugin if there is a way
0 -
i am using 5.1.3 sdk
0 -
Hi Subramanian
Thanks for your question, and it is good to know that you have been doing the integration with MetaSDK.
In fact, the Intercom event has no difference to the motion events. They are the same logic.
You will implement the device_agent for the intercom device, and you will listen to the event that generated by the device - It could be proprietary API of the device or other communication protocol..etc.Is it possible to detect a button press event from an intercom device using the Metadata SDK?
Yes, this is possible. The logic is the same as you detect the motion events.
If so, how can I receive that event in my plugin DLL?
As mentioned above, you will need to implement the logic in the device_agent for the intercom device, and you will listen to the event or signal that generated by the device - It could be proprietary API of the device or other communication protocol..etc. In short, you listen to the intercom events from devices.
Is there a specific metadata type or event packet I should be listening for from the VMS?
No, this is your custome event, you are able to define your own eventType. Please refer to the manifest.md and taxonomy.md in the MetaSDK. The STUB:events sample also gives the general idea to start with.

Hope this helps, thanks.
0 -
**What I’ve Tried:**
- Implemented a device_agent to listen to device signals.
- Injected EventMetadataPacket with custom eventType.
- Queried IEventMetadataPacket in plugin DLL.**Code Snippet:**
```cpp
for (int i = 0; i < metadataPacketCount; ++i)
{
const auto metadataPacket = metadataPacketList->at(i);const auto objectDetectedEventMetadataPacket = makePtr<EventMetadataPacket>();
const auto eventPacket = objectDetectedEventMetadataPacket->queryInterface < IEventMetadataPacket>();
if (eventPacket)
{
PLOG_INFO << "eventPacket Received";
return true;
}
}
Is this the correct approach to receive custom intercom events in the plugin DLL? Should I be listening for a specific metadata type?0
Please sign in to leave a comment.
Comments
6 comments