Skip to content

5. Integration Scenarios with Wisenet Products

5.1 Direct Camera → IP Speaker (Independent Mode)

Use case:
a line crossing at a fence or restricted area plays a warning on the nearest horn speaker.

Flow:

  • Camera detects event (line crossing, analytics).
  • Camera’s handover / event rule triggers an HTTP request to the speaker (SUNAPI URL with Type=Play).
  • Independent-mode speaker plays the local audio file.

Figure 9 – Camera Handover Configuration for IP Speaker Trigger

5.2 Camera → Wisenet NVR → IPAS

Use case:
the NVR collects events from multiple cameras and triggers zone-based announcements.

Conceptual flow:

  • Cameras send video and event data (motion, AI, alarms) to the Wisenet NVR.
  • The NVR’s event/action rule activates an alarm output (relay contact) to the IPAS controller.
  • The IPAS controller maps that input to a preset (audio file + speaker zone assignment).
  • Target zones play the configured announcement.

Important Limitation:
HTTP/S (User Coding) commands from the NVR are not supported for IPAS activation.
Only Alarm Output Relay-based triggering is currently supported.

Figure 10 – NVR to IPAS Event Flow Architecture

5.3 Camera → Wisenet WAVE → IPAS

Use case:
Wisenet WAVE is the main alarm console and operators need both automatic audio deterrence and manual talk-down.

Automated playback (Independent Mode):

  • Add the IPAS device to WAVE as a device on the server.
  • Create Event Rules that use Play Sound to stream audio from WAVE to the IPAS device, or use Do HTTP(S) Request to call SUNAPI URLs on the controller or speakers.

Talk-down:
Operators select the camera/speaker layout and use the microphone button in WAVE to speak live through the associated IPAS speaker.

Figure 11 – WAVE Event Rule and Camera Interface for HTTP(S) Trigger and Talk-down functions

5.4 Camera → Wisenet SSM → IPAS

Use case:
Wisenet SSM is the central event engine and IPAS is triggered from camera events.

Controller Mode:

  • In SSM Configuration, define an Event Action for a specific camera event.
  • Select the IPAS controller and the desired speaker group and audio file exposed by the controller.
  • When the event occurs, the controller plays the selected file to the chosen group.

Independent Mode via CGI:

  • Configure the speaker in Independent Mode and upload the audio file.
  • Create an Event Action using CGI (HTTP URL Command) with a SUNAPI Play URL.

Note:
Wisenet SSM currently supports event-based audio triggering with IPAS.
2-way audio (live talk-down) support is planned for a future SSM release (target after the current release cycle).

Figure 12 – Wisenet SSM Event Action using SUNAPI HTTP Command (Independent Mode Example)

5.5 Camera > Milestone / Genetec > IPAS

Milestone XProtect:

  • Add IPAS devices under Hanwha Vision Plug-in > IP Audios.
  • For Controller Mode, configure presets mapping Source > Target (speaker / speaker group).
  • Create Rules with action Play through Hanwha Vision IP Audios and select the appropriate preset.

Genetec Security Center:

  • Add IPAS devices as Hanwha Vision External Devices using the Genetec plug-in.
  • Use Event-to-Action with Action = Play through Hanwha Vision IP Audios, and select the audio device, sound source and target (speaker/speaker group).

Figure 17 – Genetec Security Center Event-to-Action Configuration Figure 18 – Milestone XProtect Management Client Rule Setup

Direct VMS Integration (Without Hanwha Vision Plug-in):

  • IPAS can be integrated directly with Milestone XProtect and Genetec Security Center without using the Hanwha Vision plug-in.
  • VMS event rules trigger IPAS playback using HTTP(S) / API requests exposed by IPAS.
  • This method supports Independent Mode and Controller Mode, depending on the target speaker configuration.
  • Available in the latest IPAS version.

5.6 Integration with Other Systems (Access Control, Fire, BMS, SIP PBX)

IPAS can be integrated with other systems beyond CCTV:

  • HTTP/S / SUNAPI: any system that can send HTTP requests can call IPAS URLs to play or stop audio on specific speakers or zones.
  • Contact closures: buttons, door controllers, fire panels and other relay devices can be wired to IPAS contact inputs and mapped to presets.
  • SIP PBX: IP PBX integration allows SIP phones to page through IP speakers for phone-based paging.