1. Overview

This document provides comprehensive instructions for configuring and debugging Genetec Virtual Encoders and Virtual Decoders with WINK Streaming solutions. It covers all recent versions of Omnicast and Security Center (5.2 through 5.12), focusing on the integration between WINK Forge and Genetec systems.

Purpose

The WINK Forge uses the Genetec Virtual Decoder interface for video ingress and egress. Supplemental features are made available via the WINK Streaming H263/H264/H265 Genetec SDK component. This guide covers:

• Virtual Decoder configuration for video ingress
• Virtual Encoder setup for video egress
• Transport mode configuration (UDP, Multicast, TCP)
• Integration with APIBridge.Metro for automated management
• SDK-based helper applications

Document Scope

This manual does not cover the SDK helper applications provided by WINK Streaming. Information about these SDK-based helper applications (including APIBridge.Metro and WINKSCData) can be found in their respective documentation.

2. Compatibility & Requirements

Supported Genetec Versions

System Requirements

Network Requirements

• Ports:
  • 8000-8031 (Default decoder ports)
  • 8100-8131 (Alternate decoder ports)
  • 5500 (Genetec SDK communication)
• Protocols: UDP (unicast/multicast), TCP (for SDK)
• Bandwidth: Varies by stream count and quality

Licensing

The WINK Forge can use the built-in virtual encoder and decoder licenses associated with your Genetec product. The total number of virtual decoder connections is constrained by the available monitor licenses.

3. Configuration

3.1 Virtual Decoder Setup

Virtual Decoders allow WINK Forge to receive video streams from Genetec Security Center. This is the primary method for integrating Genetec cameras with WINK streaming infrastructure.

Step-by-Step Configuration

Step 1: Add Virtual Decoder in Security Center

1. Open Genetec Config Tool
2. Navigate to the Video section
3. Right-click and select "Add Video Unit"
4. Choose "Virtual" as the unit type
5. Select "Genetec Protocol"
6. Enter the WINK Forge IP address and port

Figure 1: Adding a Virtual Video Unit in Config Tool

Step 2: Configure Decoder Properties

Transport Mode Configuration

Unicast UDP

For unicast UDP configuration:

1. Open the monitor interface in a view window
2. Drag a camera to the monitor interface
3. Load the WINK Forge logs and determine the assigned port
4. Create an input in the WINK Forge with the assigned unicast port

Multicast UDP

For multicast UDP configuration:

1. Open the monitor interface in a view window
2. Drag a camera to the monitor interface
3. Create an input in the WINK Forge with the camera's multicast address and port

3.2 Virtual Encoder Setup

Virtual Encoders allow WINK Forge to send video streams into Genetec Security Center, appearing as standard IP cameras.

Adding a Virtual Encoder

To add a virtual encoder, follow these steps:

1. Add Video Unit
   • In Config Tool, navigate to Video section
   • Right-click and select "Add Video Unit"
2. Select Genetec Protocol
   • Choose "Virtual" as unit type
   • Select "Genetec" as protocol
3. Configure Connection
   • Enter WINK Forge IP address
   • Specify the encoder port
   • Set appropriate credentials if required

From this point on, the Virtual Encoder should be treated as a camera within Security Center.

Figure 2: Virtual Encoder configuration in Security Center

Encoder Properties

3.3 Associating Cameras with Decoders

Once virtual decoders are configured, you need to associate cameras with them to establish video streams.

Manual Association

Using the Security Desk live viewer:

1. Open Security Desk
2. Navigate to the monitoring task
3. Drag a camera from the entity tree
4. Drop it on an open monitor interface

Automated Association with APIBridge.Metro

For large-scale deployments, use APIBridge.Metro to automate camera-monitor associations:

1. Connect APIBridge.Metro to Security Center
2. Navigate to "Associate Monitors Evenly"
3. Configure distribution settings
4. Apply associations in batch

Figure 3: Associating cameras with virtual decoders

4. WINK Forge Settings

Each WINK Forge offers additional settings related to the Genetec Protocol configuration. These settings can be found in the Variables page of the WINK Forge interface.

4.1 Encoder & Decoder Settings

Genetec Mode

Default: 0

Monitor Configuration

Default: 10

This value defines the default number of monitors per port. Configuration details:

• Default ports: 8000-8031
• Alternate ports: 8100-8131
• Maximum cameras per monitor: 10 (recommended)

Transport Protocol Settings

UDP

Default: Enabled

Enable or disable support to receive UDP Unicast. WINK Forges will be able to receive the video stream in UDP.

Multicast

Default: Enabled

Enable or disable support to receive UDP Multicast. This is the default transport type for Genetec products; however, it requires that the WINK Forge is in the same LAN or multicast region of the camera.

TCP

Default: Disabled

TCP transport mode is currently not supported for virtual decoders.

4.2 Decoder Specific Settings

Hold Time

Default: 20

Number of seconds to hold the current camera image in the event of disconnection. This helps prevent black screens during temporary network interruptions.

Generate Stop and Start

Default: Enabled

Enable or disable stop-start messages sent by Omnicast or Security Center.

Buffering

Default: 500ms

Amount of video buffering to maintain smooth playback. Adjust based on network conditions:

• LAN: 200-500ms
• WAN: 1000-2000ms
• Internet: 2000-5000ms

4.3 Encoder Specific Settings

HTTP Tunneling

Default: Enabled

Enable or disable tunneling over HTTP. This allows video streams to traverse firewalls and proxies that block standard protocols.

Inline Communication

Default: Disabled

Enable or disable RTP communication inline over the control channel. This reduces the number of ports required but may impact performance.

Always Available

Default: Disabled

Enable or disable sending an online state even when the camera is offline. Useful for maintaining consistent entity states in Security Center.

Force HTTP Tunnel

Default: Disabled

Enable or disable forcing all communication over HTTP tunnel. Only to be used for debugging or in restrictive network environments.

Absolute Path

Default: (empty)

Only to be used for debugging when coordinating with WINK Streaming technical support staff.

5. APIBridge.Metro Integration

APIBridge.Metro provides enhanced management capabilities for WINK-Genetec integrations, offering automated configuration and monitoring features.

5.1 SDK Components

The WINK Streaming H263/H264/H265 Genetec SDK component provides supplemental features beyond the basic virtual encoder/decoder functionality:

Key Features

• Automated Discovery: Finds all virtual decoders in the system
• Batch Configuration: Update multiple decoders simultaneously
• Association Management: Distribute cameras across monitors evenly
• Export Capabilities: Generate XML reports of configurations
• Real-time Monitoring: Track decoder status and connections

System Requirements for SDK Components

• Windows 2012 Server or Windows 8.1 or greater
• .NET Framework 4.5.1 or later (4.8 recommended)
• Genetec SDK 5.9 or later installed
• Administrative access to Security Center

Figure 4: APIBridge.Metro managing virtual decoders

5.2 Monitor Associations

APIBridge.Metro simplifies the process of associating cameras with virtual decoders, especially in large deployments.

Association Workflow

1. Connect to Security Center
   • Use SDK credentials with appropriate permissions
   • Verify connection status
2. List Decoders
   • View all virtual decoders
   • Check current associations
   • Identify unconnected monitors
3. Configure Associations
   • Use "Associate Monitors Evenly" feature
   • Preview distribution before applying
   • Apply naming conventions
4. Export Configuration
   • Generate XML documentation
   • Create association reports

Naming Conventions

APIBridge.Metro uses standardized naming to indicate associations:

• Format: [Camera Name] - [Monitor Prefix]-[UDP Port]
• Example: Front Entrance - WF301-8001

6. Configuration Screenshots

Add Video Unit

Figure 5: Add Video Unit dialog in Config Tool

Select Video Unit Type

Figure 6: Selecting Virtual as the unit type

Connection Type

Figure 7: Selecting Genetec protocol for connection

Add Camera - Step 1

Figure 8: First step of adding a camera to virtual encoder

Add Camera - Step 2

Figure 9: Second step - configuring camera properties

Add Camera - Step 3

Figure 10: Third step - network configuration

Additional Configuration Screenshots

Virtual Decoder Properties

Figure 11: Virtual decoder property configuration

Monitor Interface

Figure 12: Monitor interface in Security Desk

Camera Association

Figure 13: Dragging camera to monitor for association

WINK Forge Variables

Figure 14: WINK Forge variables page for Genetec settings

Log Output

Figure 15: WINK Forge log showing decoder connections

APIBridge.Metro Integration

Figure 16: APIBridge.Metro managing decoder associations

Export Configuration

Figure 17: XML export of decoder configuration

7. Troubleshooting

Common Issues and Solutions

Virtual Decoder Not Connecting

No Video Stream

Debug Mode Logging

To enable detailed logging:

1. Set Genetec Mode to 3 (Debug)
2. Reproduce the issue
3. Access logs via WINK Forge Support → ||| Logs
4. Look for connection attempts and error messages

APIBridge.Metro Issues

• Cannot see decoders: Verify SDK user has "View analog monitors" permission
• Cannot update names: Check "Modify analog monitor properties" permission
• Missing IP addresses: Enable "View video units" permission

8. Best Practices

Network Configuration

• Use dedicated VLANs for video traffic
• Enable QoS for video streams
• Configure multicast properly with IGMP snooping
• Monitor bandwidth usage regularly

Decoder Management

• Naming Convention: Use consistent naming like WF[Number]-[Port]
• Port Allocation: Document port assignments
• License Planning: Ensure sufficient monitor licenses
• Regular Testing: Verify decoder connections weekly

Performance Optimization

• Limit cameras per monitor to 10 or fewer
• Use appropriate buffer sizes based on network type
• Enable only required transport modes
• Monitor WINK Forge CPU and memory usage

Security Considerations

• Firewall Rules: Only open required ports
• Network Isolation: Separate video traffic from corporate network
• Access Control: Limit who can modify decoder configurations
• Regular Updates: Keep WINK Forge and Genetec updated

Documentation

• Maintain decoder mapping spreadsheet
• Document custom configurations
• Export configurations regularly using APIBridge.Metro
• Keep troubleshooting logs for pattern analysis

9. Appendix

Port Reference

Genetec Mode Reference

Contact Information

For technical support and assistance:

• WINK Streaming Support: tickets@wink.co

Related Documentation

• APIBridge.Metro Complete User Manual
• WINKSCData Console Application Guide
• Genetec Security Center Administrator Guide
• WINK Forge Installation Manual