Hanwha Wisenet WAVE Interface (ZCP)
From Zenitel Wiki
Hanwha Wisenet WAVE can interface to Zenitel Connect Pro using REST.
Introduction
A Node-RED flow is required to handle authentication updates of the bearer tokens for both ZCP and WAVE.
WAVE events can then be used to trigger events in ZCP using the REST interface.
Note: The process runs every 80 seconds, so additions and changes within WAVE may not work immediately, but will propagate over the next 80 seconds.
This can be sped up by restarting the Node-RED flow.
It's assumed that you have already created a Zenitel Link account in Zenitel Connect Pro for integration and you have a working Hanwha Wisenet WAVE VMS.
Node-RED flow
Download the ZCP-Hanwha-Wisenet-WAVE-Authentication-Interface Node-RED flow from the Zenitel Github.
Import the Node-RED flow into Node-RED. Edit the Setup Details node and update with the required settings
- Connect Pro IP Address
- Connect Pro Zenitel Link Username
- Connect Pro Zenitel Link Password
- WAVE IP Address
- WAVE Username
- WAVE Password
Deploy the flow and it will obtain the bearer tokens and begin scraping the WAVE Events for the word Zenitel anywhere in the Title.
Hanwha Wisenet WAVE
Create a new event against the Zenitel device by right clicking and selecting Rules
- Press the 'Add Rule' button.
- Set the 'Title or comment' to contain the word 'Zenitel'. This is the term that the Node-RED flow uses to locate ZCP events
- The title can contain other text, for example 'Zenitel TCIV-3+ Movement alarm'.
- Choose an event from the drop down box under "When Event"
- Set the "Do Action" drop down box to HTTPS request
- Add the URL to the ZCP Rest command you require (i.e. https://<IP_Address>/api/calls)
- Set the required method (i.e. POST)
- Add the required content according the Zenitel Link Schema
- Set the content type to "application/json"
- Set the Authentication type to Bearer
- Add any text to the Token as this will be overwritten every 80s by the Node-RED flow
The example shown will send a POST to the ZCP server at 192.168.10.1, and using the calls API will create an Audio Message Broadcast from 8191 to Group 85.
The code example is
{
"from_dirno" : "8191",
"to_dirno" : "85",
"action" : "setup",
"verbose" : true
}