Actions

Difference between revisions of "ONVIF Settings"

From Zenitel Wiki

(Non-Video Intercoms)
(Video Intercoms)
 
(36 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
{{AEIS}}
 
{{AEIS}}
[[File:ONVIF overview.png|thumb|1000px]]
+
[[File:ONVIF overview.png|thumb|800px]]
 +
 
 +
 
 
ONVIF is an open industry forum that provides and promotes standardized interfaces for effective interoperability of IP-based physical security products.
 
ONVIF is an open industry forum that provides and promotes standardized interfaces for effective interoperability of IP-based physical security products.
  
 
ONVIF profiles make it easy to recognize how ONVIF conformant devices and clients are compatible with one another. An ONVIF profile has a fixed set of features that must be supported by a conformant device and client. It ensures that a client that conforms to Profile S, for example, will work with a device that also conforms to Profile S. There are also conditional features, which are features that shall be implemented by an ONVIF device or ONVIF client if it supports that feature in any way, including any proprietary way. Optional functionalities are also defined, they do not need to be implemented but can if it's chosen. Clients and devices can support more than one ONVIF profile.
 
ONVIF profiles make it easy to recognize how ONVIF conformant devices and clients are compatible with one another. An ONVIF profile has a fixed set of features that must be supported by a conformant device and client. It ensures that a client that conforms to Profile S, for example, will work with a device that also conforms to Profile S. There are also conditional features, which are features that shall be implemented by an ONVIF device or ONVIF client if it supports that feature in any way, including any proprietary way. Optional functionalities are also defined, they do not need to be implemented but can if it's chosen. Clients and devices can support more than one ONVIF profile.
  
New from version 6.4.3.0:
+
New from version 7.1.3.0:
* Supports bi-directional audio
+
 
* ONVIF features also available for Non-video Intercoms
+
*ONVIF over HTTPS is now supported, this also includes video over HTTPS tunneling.
 +
*Devices can now send SIP name as hardware model
  
 
__FORCETOC__
 
__FORCETOC__
  
== Video Intercoms ==
+
==Video Intercoms==
'''Supported devices'''
+
'''Supported video devices'''
* TCIV
+
 
* TCIV+/TKIV+
+
*TCIV
 +
*TCIV+/TKIV+
 +
*TMIV+
 +
*TEIV+
  
===ONVIF configuration ===
+
===ONVIF configuration===
Some ONVIF setting are available for configuration in station web.
+
Some ONVIF settings are available from the station web interface.
[[File:Onvif1.png|thumb|left|700px]]
+
[[File:ONVIF Settings Video station.PNG|thumb|left|700px|ONVIF settings in stations with camera]]
<br clear=all/>
+
<br clear="all" />
  
 
*'''Enable ONVIF Discovery Service''' - Enables UDP port 3702 on station firewall. Traffic to this port is used for WS-Discovery Service. If this setting is turned off, the station can not be discovered by any ONVIF client
 
*'''Enable ONVIF Discovery Service''' - Enables UDP port 3702 on station firewall. Traffic to this port is used for WS-Discovery Service. If this setting is turned off, the station can not be discovered by any ONVIF client
** '''ONVIF WS-Discovery Name''': Sets device name for WS-Discovery that will be shown in ONVIF client after the device is found  
+
**'''ONVIF WS-Discovery Name''': Sets device name for WS-Discovery that will be shown in ONVIF client after the device is found
** '''ONVIF WS-Discovery Location''': Sets device location for WS-Discovery that will be shown in ONVIF client after the device is found  
+
**'''ONVIF WS-Discovery Location''': Sets device location for WS-Discovery that will be shown in ONVIF client after the device is found
* '''Enable control of relay IDLE state'''- Some Security systems automatically force relay IDLE state = On, and it is not possible to configure it. If this is an undesirable scenario, this option can be disabled
+
*'''Enable control of relay IDLE state'''- Some Security systems automatically force relay IDLE state = On, and it is not possible to configure it. If this is an undesirable scenario, this option can be disabled
* '''Operate relay/outputs via ONVIF (ICX-AlphaCom mode only)''' - If enabled, Relay/Output can be controlled from both ICX-AlphaCom server and through ONVIF protocol so the user needs to pay attention for possible conflicts
+
*'''Operate relay/outputs via ONVIF (ICX-AlphaCom mode only)''' - If enabled, Relay/Output can be controlled from both ICX-AlphaCom server and through ONVIF protocol so the user needs to pay attention for possible conflicts
* '''Report DAK as Digital Input in ONVIF''': Call button pressed on a station is reported as Digital Input to a Video Management System.
+
*'''Report DAK as Digital Input in ONVIF''': Call button pressed on a station is reported as Digital Input to a Video Management System.
* '''Report Station call events as Digital Input in ONVIF''' (default Disabled): Send station call status as Digital Inputs to a Video Management System. Supported call states are:
+
*'''Report Station call events as Digital Input in ONVIF''' (default Disabled): Send station call status as Digital Inputs to a Video Management System. Supported call states are:
** In Conversation
+
**In Conversation
** Ringing
+
**Ringing
** In call queue (ICX-AlphaCom mode only)
+
**In call queue (ICX-AlphaCom mode only)
 +
*'''Send SIP name as hardware model''': Device is able to send custom name if default name is changed.
  
 
'''ONVIF Media Profiles'''
 
'''ONVIF Media Profiles'''
Line 36: Line 43:
  
 
In most cases, media profiles are configured directly from Video Management System software (ONVIF client) and in that case, it is not recommended to manually change values below. The maximum number of Media Profiles which can be created is 50.
 
In most cases, media profiles are configured directly from Video Management System software (ONVIF client) and in that case, it is not recommended to manually change values below. The maximum number of Media Profiles which can be created is 50.
* '''Choose profile to configure''' - contains list of all profiles (built-in profiles and profiles created by ONVIF clients) for configuration. Profiles can be added and deleted only by ONVIF clients.  
+
 
 +
*'''Choose profile to configure''' - contains list of all profiles (built-in profiles and profiles created by ONVIF clients) for configuration. Profiles can be added and deleted only by ONVIF clients.
 +
 
 
'''Encoder''' - each profile should be assigned with one ONVIF video encoder configuration. Possible options are '''Encoder 1''', '''Encoder 2''' or '''Encoder not set''' (This option is only used in situations when VMS creates media profile without video encoder and should never be manually selected).Encoder is defined with following parameters:
 
'''Encoder''' - each profile should be assigned with one ONVIF video encoder configuration. Possible options are '''Encoder 1''', '''Encoder 2''' or '''Encoder not set''' (This option is only used in situations when VMS creates media profile without video encoder and should never be manually selected).Encoder is defined with following parameters:
* '''Encoding''' - Defines which encoding type will be used:
+
 
** H264
+
*'''Encoding''' - Defines which encoding type will be used:
** JPEG
+
**H264
* '''Resolution''': Sets the pixel resolution:
+
**JPEG
** 1080P [H264 only]
+
*'''Resolution''': Sets the pixel resolution:
** 720P [H264 only]
+
**1080P [H264 only]
** 480P
+
**720P [H264 only]
** 240P
+
**480P
* '''Frames per second''': Sets the framerate per second:
+
**240P
** 5-30 for H264
+
*'''Frames per second''': Sets the framerate per second:
** 5-10 for JPEG
+
**5-30 for H264
* '''Bitrate''': Sets the bitrate which will be used in video stream (H264 only)
+
**5-10 for JPEG
* '''Quality''': Video quality parameter which is going to be used. It will have an effect for JPEG encoding only. Relative value for the quality of the video. A high value within supported quality range means higher quality
+
*'''Bitrate''': Sets the bitrate which will be used in video stream (H264 only)
* '''GovLength''': the interval in which the I-Frames will be coded. An entry of 2 indicates that every 2nd image is an I-Frame, and 3 only every 3rd frame, etc. The frames in between are coded as P or B Frames. Valid values are from 2 to 32767. Will have effect for H264 encoding only.
+
*'''Quality''': Video quality parameter which is going to be used. It will have an effect for JPEG encoding only. Relative value for the quality of the video. A high value within supported quality range means higher quality
 +
*'''GovLength''': the interval in which the I-Frames will be coded. An entry of 2 indicates that every 2nd image is an I-Frame, and 3 only every 3rd frame, etc. The frames in between are coded as P or B Frames. Valid values are from 2 to 32767. Will have effect for H264 encoding only.
  
 
{{note| The login credentials used for ONVIF are different from the login credentials used for the web interface. To change the ONVIF login credentials, [[TCIV/ONVIF_Troubleshooting_Guide#How_can_I_connect_to_TCIV_using_.22ONVIF_Device_Manager.22_tool.3F|ONVIF Device Manager]] should be used. }}
 
{{note| The login credentials used for ONVIF are different from the login credentials used for the web interface. To change the ONVIF login credentials, [[TCIV/ONVIF_Troubleshooting_Guide#How_can_I_connect_to_TCIV_using_.22ONVIF_Device_Manager.22_tool.3F|ONVIF Device Manager]] should be used. }}
  
== Non-Video Intercoms ==
+
==Non-Video Intercoms==
'''Supported devices'''
+
'''Supported non-video devices'''
* TCIS/TKIS
+
 
* TFIE/TKIE
+
*TCIS/TKIS
* TMIS
+
*TFIE/TKIE
* TFIX
+
*TMIS
* V2 Master Stations
+
*TFIX
 +
*V2 Master Stations
 +
*IP Speakers
  
 
===ONVIF configuration===
 
===ONVIF configuration===
Some ONVIF setting are available for configuration in station web.
+
Some ONVIF settings are available from the station web interface.  
[[File:ONVIF nonvideo.png|thumb|left|700px]]
+
[[File:ONVIF Settings Web.PNG|thumb|left|700px|ONVIF settings in stations without camera]]
<br clear=all/>
+
<br clear="all" />
  
 
*'''Enable ONVIF Discovery Service''' - Enables UDP port 3702 on station firewall. Traffic to this port is used for WS-Discovery Service. If this setting is turned off, the station can not be discovered by any ONVIF client
 
*'''Enable ONVIF Discovery Service''' - Enables UDP port 3702 on station firewall. Traffic to this port is used for WS-Discovery Service. If this setting is turned off, the station can not be discovered by any ONVIF client
** '''ONVIF WS-Discovery Name''': Sets device name for WS-Discovery that will be shown in ONVIF client after the device is found  
+
**'''ONVIF WS-Discovery Name''': Sets device name for WS-Discovery that will be shown in ONVIF client after the device is found
** '''ONVIF WS-Discovery Location''': Sets device location for WS-Discovery that will be shown in ONVIF client after the device is found  
+
**'''ONVIF WS-Discovery Location''': Sets device location for WS-Discovery that will be shown in ONVIF client after the device is found
* '''Enable control of relay IDLE state'''- Some Security systems automatically force relay IDLE state = On, and it is not possible to configure it. If this is an undesirable scenario, this option can be disabled
+
*'''Enable control of relay IDLE state'''- Some Security systems automatically force relay IDLE state = On, and it is not possible to configure it. If this is an undesirable scenario, this option can be disabled
* '''Operate relay/outputs via ONVIF (ICX-AlphaCom mode only)''' - If enabled, Relay/Output can be controlled from both ICX-AlphaCom server and through ONVIF protocol so the user needs to pay attention for possible conflicts
+
*'''Operate relay/outputs via ONVIF (ICX-AlphaCom mode only)''' - If enabled, Relay/Output can be controlled from both ICX-AlphaCom server and through ONVIF protocol so the user needs to pay attention for possible conflicts
* '''Report DAK as Digital Input in ONVIF''': Call button pressed on a station is reported as Digital Input to a Video Management System.
+
*'''Report DAK as Digital Input in ONVIF''': Call button pressed on a station is reported as Digital Input to a Video Management System.
** In Conversation
+
*'''Report Station call events as Digital Input in ONVIF''' (default Disabled): Send station call status as Digital Inputs to a Video Management System. Supported call states are:
** Ringing
+
**In Conversation
** In call queue (ICX-AlphaCom mode only)
+
**Ringing
 +
**In call queue (ICX-AlphaCom mode only)
 +
*'''Send SIP name as hardware model''': Device is able to send custom name if default name is changed.
  
 
{{note| The login credentials used for ONVIF are different from the login credentials used for the web interface. To change the ONVIF login credentials, [[TCIV/ONVIF_Troubleshooting_Guide#How_can_I_connect_to_TCIV_using_.22ONVIF_Device_Manager.22_tool.3F|ONVIF Device Manager]] should be used. }}
 
{{note| The login credentials used for ONVIF are different from the login credentials used for the web interface. To change the ONVIF login credentials, [[TCIV/ONVIF_Troubleshooting_Guide#How_can_I_connect_to_TCIV_using_.22ONVIF_Device_Manager.22_tool.3F|ONVIF Device Manager]] should be used. }}
  
== ONVIF Features ==
+
==Additional Information==
=== General ===
+
All Zenitel devices with a camera (TCIV and TCIV+) are certified to ONVIF Profile S. This allows the stations to be discovered by any ONVIF Profile S compliant VMS.
{| border=1
+
As from VS-IS software version 6.4.3.0, a number of additional capabilities have been added:
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
+
 
|rowspan="2" colspan="2" style="text-align: center; background-color: #ffd400;" | '''Profile'''
+
*Support for DeviceIO
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
+
*Audio Backchannel, meaning audio from VMS to the device
|colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
+
 
 +
In addition, some other major changes have been made:
 +
 
 +
*Audio only stations which can run VS-IS 6.4.3.0 are now able to generate a video stream, and are therefore compliant with ONVIF Profile S
 +
*As a further enhancement to DeviceIO, station modes are made available as a logical input to the VMS and can then trigger function in that VMS
 +
 
 +
====Non-Video Intercom stations as ONVIF Profile S compliant devices====
 +
The stations generate a video stream (a Zenitel logo) and can be discovered as any other camera. As with the TCIV and TCIV+, the microphone is also discovered as a camera capability.
 +
 
 +
====Audio backchannel====
 +
VMS's which support this ONVIF feature will also discover the presence of the station's loudspeaker. This then gives the possibility for the VMS operator to directly send a voice message to the station. This would normally be used when the same message needs to be broadcast to all cameras featuring a loudspeaker and which cannot be reached in the normal Zenitel way, as they are not part of an ICX-AlphaCom, IC-EDGE or SIP system.
 +
 
 +
====DeviceIO====
 +
VMS's which support this ONVIF feature will be able to discover the presence of all inputs and outputs on the station. Inputs can be used to trigger actions in the VMS event handler. Control of the outputs can be directly by the operator, or as an action from the VMS event handler.
 +
[[File:Support_for_ DeviceIO.png|thumb|left|700px|Support for DeviceIO]]
 +
<br clear="all" />
 +
=====Report DAK as Digital Input in ONVIF=====
 +
Other than the general purpose inputs which are available on the station, it is possible to have a Call-button (DAK) press reported as an input to the VMS. This can for instance be used as an additional way of signalling that there is somebody at the door, wanting to talk to the operator. (Turbine stations only, TCIS and TCIV+)
 +
 
 +
=====Report station call events as Digital Input in ONVIF=====
 +
Stations know the state they are in: in a call, ringing, in call requester mode. This state information is now available to the ONVIF module in the station software and can be used to provide a number of additional 'virtual' inputs. These inputs are discovered through DeviceIO, in the way any physical input is discovered. States that can be signaled to the VMS are:
 +
 
 +
*Call established - Call in progress input Activated
 +
*Call ended - Call in progress input Deactivated
 +
*Station in ringing mode - both for an outgoing (ringback) and incoming call - Call ringing input Activated
 +
*Station ringing mode ended - Call ringing input Deactivated
 +
*Station has made a call request or ringing group call (only when the station is in AlphaCom mode) - Call queued input Activated
 +
*Station leaves call request or ringing group call mode (only when the station is in AlphaCom mode) - Call queued input Deactivated
 +
 
 +
Use cases that can be solved by these inputs are:
 +
 
 +
*Switching a camera to a monitor pane at the start of a conversation
 +
*Starting and stopping video and/or audio recording
 +
*Adding an entry in a the log for audit trail purposes
 +
 
 +
=====The order of inputs being reported=====
 +
The following order, from first to last, is used to report the different inputs if enabled and available.
 +
 
 +
*Call Active
 +
*Call Queued
 +
*Call Ringing
 +
*DAK 1....n
 +
*Inputs 1....n
 +
 
 +
===== Input mapping =====
 +
 
 +
Click on the link below to select the server platform, then select which ONVIF options you have enabled in the Zenitel Device:
 +
 
 +
<div class="tabs" data-tab>
 +
  <li class="tab-title ">'''ICX-Alphacom Mode'''</li>
 +
  <li class="tab-title">'''IC-Edge/SIP'''</li>
 +
</div>
 +
<div class="tabs-content">
 +
  <div class="content" id="panel10">
 +
  <div class="row ">
 +
<div style="margin-left:10px">Select the tab that matches with the ONVIF options that are enabled</div>
 +
  </div>
 +
  <div class="row ">
 +
<div class="tabs" data-tab>
 +
<li class="tab-title ">'''Default settings'''</li>
 +
<li class="tab-title ">'''Only Call events enabled'''</li>
 +
<li class="tab-title ">'''Only Call Button events enabled'''</li>
 +
 +
</div>
 +
  </div>
 +
  <div class="tabs-content">
 +
<div class="content " id="panel20">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Default Settings(ICX-Alphacom mode) </td>
 +
</tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight:bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call button)</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold;border:1px solid #000000">TCIV+ (2 Call buttons)</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000"> Not supported</td>
 +
<td style="border:1px solid #000000"> Not supported</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
  </tr>
 +
 
 +
</table>
 +
</div>
 +
</div>
 +
<div class="content" id="panel21">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Only Call events enabled (ICX-Alphacom mode) </td>
 +
</tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call Button)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+ (2 Call Buttons)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000">Not enabled
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
  </tr>
 +
 
 +
</table>
 +
</div>
 +
</div>
 +
<div class="content " id="panel22">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Only Call Button events enabled(ICX-Alphacom mode) </td>
 +
</tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight:bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call Button)</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Input 1: Call Button 1</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold;border:1px solid #000000">TCIV+ (2 Call Buttons)</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Input 1: Call Button 1<br>Input 2: Call Button 2</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000"> Not supported</td>
 +
<td style="border:1px solid #000000"> Not supported</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
  </tr>
 +
 
 +
</table>
 +
</div>
 +
</div>
 +
<div class="content " id="panel23">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Call events and Call Button events enabled (ICX-Alphacom mode) </td>
 +
</tr>
 +
<tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
</tr>
 +
<tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call Button)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing</td>
 +
<td style="border:1px solid #000000">Input 4: Call Button 1</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
</tr>
 +
<tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+ (2 Call Buttons)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000">Input 4: Call Button 1<br>Input 5: Call Button 2
 +
</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
</tr>
 +
<tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
</tr>
 +
<tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
</tr>
 +
 
 +
</table>
 +
 
 +
</div>
 +
</div>
 +
</div>
 +
</div>
 +
<div class="content" id="panel11">
 +
  <div class="row ">
 +
<div style="margin-left:10px">Select the tab that mathces with the ONVIF options that are enabled</div>
 +
  </div>
 +
  <div class="row ">
 +
  <div class="tabs" data-tab>
 +
<li class="tab-title ">'''Default settings'''</li>
 +
<li class="tab-title ">'''Only Call events enabled'''</li>
 +
<li class="tab-title ">'''Only Call Button events enabled'''</li>
 +
 +
</div>
 +
  </div>
 +
<div class="tabs-content">
 +
<div class="content" id="panel30">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Default settings (IC-Edge/SIP mode) </td>
 +
</tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call Button)</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Input 1: I/O 1<br>Input 2: I/O 2<br>Input 3: I/O 3<br>Input 4: I/O 4<br>Input 5: I/O 5<br>Input 6: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+ (2 Call Buttons)</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Input 1: I/O 1<br>Input 2: I/O 2<br>Input 3: I/O 3<br>Input 4: I/O 4<br>Input 5: I/O 5<br>Input 6: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
<td style="border:1px solid #000000">Input 1: I/O 1<br>Input 2: I/O 2<br>Input 3: I/O 3<br>Input 4: I/O 4<br>Input 5: I/O 5<br>Input 6: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
<td style="border:1px solid #000000">Input 1: I/O 1<br>Input 2: I/O 2<br>Input 3: I/O 3<br>Input 4: I/O 4<br>Input 5: I/O 5<br>Input 6: I/O 6</td>
 +
  </tr>
 +
</table>
 +
</div>
 +
</div>
 +
<div class="content" id="panel31">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Only Call events enabled (IC-Edge/SIP mode) </td>
 +
</tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call Button)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Input 4: I/O 1<br>Input 5: I/O 2<br>Input 6: I/O 3<br>Input 7: I/O 4<br>Input 8: I/O 5<br>Input 9: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+ (2 Call Buttons)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing</td>
 +
<td style="border:1px solid #000000">Not enabled
 +
</td>
 +
<td style="border:1px solid #000000">Input 4: I/O 1<br>Input 5: I/O 2<br>Input 6: I/O 3<br>Input 7: I/O 4<br>Input 8: I/O 5<br>Input 9: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000">Input 4: I/O 1<br>Input 5: I/O 2<br>Input 6: I/O 3<br>Input 7: I/O 4<br>Input 8: I/O 5<br>Input 9: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000">Input 4: I/O 1<br>Input 5: I/O 2<br>Input 6: I/O 3</td>
 +
  </tr>
 +
</table>
 +
</div>
 +
</div>
 +
<div class="content" id="panel32">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Only Call Button events enabled (IC-Edge/SIP mode) </td>
 +
</tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call Button)</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Input 1: Call Button 1</td>
 +
<td style="border:1px solid #000000">Input 2: I/O 1<br>Input 3: I/O 2<br>Input 4: I/O 3<br>Input 5: I/O 4<br>Input 6: I/O 5<br>Input 7: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+ (2 Call Buttons)</td>
 +
<td style="border:1px solid #000000"><br>Not enabled</td>
 +
<td style="border:1px solid #000000">Input 1: Call Button 1<br>Input 2: Call Button 2</td>
 +
<td style="border:1px solid #000000">Input 3: I/O 1<br>Input 4: I/O 2<br>Input 5: I/O 3<br>Input 6: I/O 4<br>Input 7: I/O 5<br>Input 8: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
<td style="border:1px solid #000000">Input 1: I/O 1<br>Input 2: I/O 2<br>Input 3: I/O 3<br>Input 4: I/O 4<br>Input 5: I/O 5<br>Input 6: I/O 6</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Not enabled</td>
 +
<td style="border:1px solid #000000">Not supported</td>
 +
<td style="border:1px solid #000000">Input 1: I/O 1<br>Input 2: I/O 2<br>Input 3: I/O 3<br>Input 4: I/O 4<br>Input 5: I/O 5<br>Input 6: I/O 6</td>
 +
  </tr>
 +
</table>
 +
</div>
 +
</div>
 +
<div class="content " id="panel33">
 +
<div class="row ">
 +
<table style="width:80%; border-spacing:10px; margin-left:10px;">
 +
<tr style="border:1px solid #000000">
 +
<td colspan="4" style="border:1px solid #000000; background:#ffd400; text-align:center"> Call events and Call Button events enabled (IC-Edge/SIP mode) </td>
 +
</tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="border:1px solid #000000"></td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Call Button Events</td>
 +
<td style="font-weight: bold; border:1px solid #000000">Inputs</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+/TMIV+ (1 Call Button)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing</td>
 +
<td style="border:1px solid #000000">Input 4: Call Button 1</td>
 +
<td style="border:1px solid #000000">Input 5: I/O 1<br>Input 6: I/O 2<br>Input 7: I/O 3<br>Input 8: I/O 4<br>Input 9: I/O 5<br>Input 10: I/O 6
 +
</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIV+ (2 Call Buttons)</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000">Input 4: Call Button 1<br>Input 5: Call Button 2
 +
</td>
 +
<td style="border:1px solid #000000">Input 6: I/O 1<br>Input 7: I/O 2<br>Input 8: I/O 3<br>Input 9: I/O 4<br>Input 10: I/O 5<br>Input 11: I/O 6
 +
</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">TCIS/TMIS</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000">Input 4: I/O 1<br>Input 5: I/O 2<br>Input 6: I/O 3<br>Input 7: I/O 4<br>Input 8: I/O 5<br>Input 9: I/O 6
 +
</td>
 +
  </tr>
 +
  <tr style="border:1px solid #000000">
 +
<td style="font-weight: bold; border:1px solid #000000">IP Desk Master V2<br>IP Flush Master V2<br>IP-CROR</td>
 +
<td style="border:1px solid #000000">Input 1: Call Active<br>Input 2: Call Queued (only in ICX-Alphacom mode)<br>Input 3: Call Ringing
 +
</td>
 +
<td style="border:1px solid #000000"> Not supported </td>
 +
<td style="border:1px solid #000000">Input 4: I/O 1<br>Input 5: I/O 2<br>Input 6: I/O 3
 +
</td>
 +
  </tr>
 +
 
 +
</table>
 +
 
 +
</div>
 +
</div>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
<br>
 +
<br>
 +
 
 +
==ONVIF Features==
 +
===General===
 +
{| border="1"
 +
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
 +
| colspan="2" rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Profile'''
 +
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
 +
| colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
 
|-
 
|-
|style="text-align: center; background-color: #ffd400;" |'''Turbine'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine'''
|style="text-align: center; background-color: #ffd400;" |'''TCIV+'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine+'''
|style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
+
| style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
 
|-
 
|-
 
|Device Discovery
 
|Device Discovery
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|The ONVIF discovery name of a station shall be the name as known to it from its communication module (ICX-AlphaCom, IC-EDGE, SIP or the upcoming ICX-Next).
 
|The ONVIF discovery name of a station shall be the name as known to it from its communication module (ICX-AlphaCom, IC-EDGE, SIP or the upcoming ICX-Next).
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Network Configuration
 
|Network Configuration
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|Configuring network settings of the stations (DHCP, Static IP, Address, etc)
 
|Configuring network settings of the stations (DHCP, Static IP, Address, etc)
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Media Profile Configuration
 
|Media Profile Configuration
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|Configuration of media profiles in VMS
 
|Configuration of media profiles in VMS
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Media Transport
 
|Media Transport
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|Defines the network protocol for streaming either RTP/UDP, RTP/TCP, RTP/RTSP/TCP or RTP/RTSP/HTTP/TCP
 
|Defines the network protocol for streaming either RTP/UDP, RTP/TCP, RTP/RTSP/TCP or RTP/RTSP/HTTP/TCP
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|}
 
|}
  
=== Video ===
+
===Video===
{| border=1
+
{| border="1"
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
|rowspan="2" colspan="2" style="text-align: center; background-color: #ffd400;" | '''Profile'''
+
| colspan="2" rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Profile'''
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
|colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
+
| colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
 
|-
 
|-
|style="text-align: center; background-color: #ffd400;" |'''Turbine'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine'''
|style="text-align: center; background-color: #ffd400;" |'''TCIV+'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine+'''
|style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
+
| style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
 
|-
 
|-
 
|Video streaming MJPEG/MJPEG4
 
|Video streaming MJPEG/MJPEG4
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|Motion JPEG (M-JPEG or MJPEG) is a video compression format in which each video frame or interlaced field of a digital video sequence is compressed separately as a JPEG image.
 
|Motion JPEG (M-JPEG or MJPEG) is a video compression format in which each video frame or interlaced field of a digital video sequence is compressed separately as a JPEG image.
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Video streaming H.264
 
|Video streaming H.264
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|Also known as MPEG-4 Part 10 or Advanced Video Coding (MPEG-4 AVC), H.264 is defined as a block-oriented, compensation-based video compression standard that defines multiple profiles (tools) and levels (max bitrates and resolutions). A codec based on the H.264 standard compresses a digital video file (or stream) so that it only requires half of the storage space (or network bandwidth) of MPEG-2. Through this compression, the codec is able to maintain the same video quality despite using only half of the storage space.
 
|Also known as MPEG-4 Part 10 or Advanced Video Coding (MPEG-4 AVC), H.264 is defined as a block-oriented, compensation-based video compression standard that defines multiple profiles (tools) and levels (max bitrates and resolutions). A codec based on the H.264 standard compresses a digital video file (or stream) so that it only requires half of the storage space (or network bandwidth) of MPEG-2. Through this compression, the codec is able to maintain the same video quality despite using only half of the storage space.
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Video streaming RTSP/RTP
 
|Video streaming RTSP/RTP
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|The Real Time Streaming Protocol (RTSP) is a network control protocol used for establishing and controlling media sessions between endpoints. Clients of media servers issue commands such as play, record and pause, to facilitate real-time control of the media streaming from the server to a client (Video On Demand) or from a client to the server (Voice Recording).
 
|The Real Time Streaming Protocol (RTSP) is a network control protocol used for establishing and controlling media sessions between endpoints. Clients of media servers issue commands such as play, record and pause, to facilitate real-time control of the media streaming from the server to a client (Video On Demand) or from a client to the server (Voice Recording).
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Video Source Configuration
 
|Video Source Configuration
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|
 
|
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Media Profile for Streaming Ready out-of-the-box
 
|Media Profile for Streaming Ready out-of-the-box
|style="text-align: center; |  
+
| style="text-align: center; " |
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|Allows usage of camera, microphones and speakers out of the box
 
|Allows usage of camera, microphones and speakers out of the box
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Imaging Settings
 
|Imaging Settings
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|
 
|
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|}
 
|}
  
=== Audio ===
+
===Audio===
{| border=1
+
{| border="1"
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
|rowspan="2" colspan="2" style="text-align: center; background-color: #ffd400;" | '''Profile'''
+
| colspan="2" rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Profile'''
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
|colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
+
| colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
 
|-
 
|-
|style="text-align: center; background-color: #ffd400;" |'''Turbine'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine'''
|style="text-align: center; background-color: #ffd400;" |'''TCIV+'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine+'''
|style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
+
| style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
 
|-
 
|-
 
|Audio Streaming G.711 and AAC
 
|Audio Streaming G.711 and AAC
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|
 
|
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Audio Output Streaming G.711 and AAC
 
|Audio Output Streaming G.711 and AAC
|style="text-align: center; |  
+
| style="text-align: center; " |
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|
 
|
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
|Birectional audio
+
|Bidirectional audio
|style="text-align: center; |  
+
| style="text-align: center; " |
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|
 
|
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|}
 
|}
  
=== Events ===
+
===Events===
{| border=1
+
{| border="1"
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
|rowspan="2" colspan="2" style="text-align: center; background-color: #ffd400;" | '''Profile'''
+
| colspan="2" rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Profile'''
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
|colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
+
| colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
 
|-
 
|-
|style="text-align: center; background-color: #ffd400;" |'''Turbine'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine'''
|style="text-align: center; background-color: #ffd400;" |'''TCIV+'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine+'''
|style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
+
| style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
 
|-
 
|-
 
|Event Handling pull point
 
|Event Handling pull point
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
|Client creates a PullPoint subscription to the Event Service, allowing it to bypass firewall restrictions and WS-Endpoint provides PullMessages opration, wich is used by the client to retrieve notifications.
+
|Client creates a PullPoint subscription to the Event Service, allowing it to bypass firewall restrictions and WS-Endpoint provides PullMessages operation, which is used by the client to retrieve notifications.
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|Media Profile Configuration Events
 
|Media Profile Configuration Events
|style="text-align: center; |  
+
| style="text-align: center; " |
|style="text-align: center; | T  
+
| style="text-align: center; " |T
|Mostly used for audit trail, events are notifing that the Media profile configuration has been changed
+
|Mostly used for audit trail, events are notifying that the Media profile configuration has been changed
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 
|-
 
|-
 
|}
 
|}
  
=== Additional ===
+
===Additional===
{| border=1
+
{| border="1"
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Feature'''
|rowspan="2" colspan="2" style="text-align: center; background-color: #ffd400;" | '''Profile'''
+
| colspan="2" rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Profile'''
|rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
+
| rowspan="2" style="text-align: center; background-color: #ffd400;" |'''Additional info'''
|colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
+
| colspan="3" style="text-align: center; background-color: #ffd400;" |'''Supported from version'''
 
|-
 
|-
|style="text-align: center; background-color: #ffd400;" |'''Turbine'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine'''
|style="text-align: center; background-color: #ffd400;" |'''TCIV+'''
+
| style="text-align: center; background-color: #ffd400;" |'''Turbine+'''
|style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
+
| style="text-align: center; background-color: #ffd400;" |'''V2 Master stations'''
 
|-
 
|-
 
|Relay Outputs
 
|Relay Outputs
|style="text-align: center; | S
+
| style="text-align: center; " |S
|style="text-align: center; | T  
+
| style="text-align: center; " |T
 
|Enables you to open door by triggering the relay on the station
 
|Enables you to open door by triggering the relay on the station
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
|style="text-align: center; | 6.4.3.0
+
| style="text-align: center; " |6.4.3.0
 +
|-
 +
|Send SIP name as HW model
 +
| style="text-align: center; " |S
 +
| style="text-align: center; " |T
 +
|Device is able to send custom name if default name is changed.
 +
| style="text-align: center; " |7.1.3.0
 +
| style="text-align: center; " |7.1.3.0
 +
| style="text-align: center; " |7.1.3.0
 
|-
 
|-
 
|}
 
|}
  
==Additional Information==
+
[[Category:ONVIF]]
All Zenitel devices with a camera (TCIV and TCIV+) are certified to ONVIF Profile S. This allows the stations to be discovered by any ONVIF Profile S compliant VMS.
 
As from VS-IS software version 6.4.3.0, a number of additional capabilities have been added:
 
*Support for DeviceIO
 
*Audio Backchannel, meaning audio from VMS to the device
 
 
 
In addition, some other major changes have been made:
 
*Audio only stations which can run VS-IS 6.4.3.0 are now able to generate a video stream, and are therefore compliant with ONVIF Profile S
 
*As a further enhancement to DeviceIO, station modes are made available as a logical input to the VMS and can then trigger function in that VMS
 
 
 
====Non-Video Intercom stations as ONVIF Profile S compliant devices====
 
The stations generate a video stream (a Zenitel logo) and can be discovered as any other camera. As with the TCIV and TCIV+, the microphone is also discovered as a camera capability.
 
 
 
====Audio backchannel====
 
VMS's which support this ONVIF feature will also discover the presence of the station's loudspeaker. This then gives the possibility for the VMS operator to directly send a voice message to the station. This would normally be used when the same message needs to be broadcast to all cameras featuring a loudspeaker and which cannot be reached in the normal Zenitel way, as they are not part of an ICX-AlphaCom, IC-EDGE or SIP system.
 
 
 
====DeviceIO====
 
VMS's which support this ONVIF feature will be able to discover the presence of all inputs and outputs on the station. Inputs can be used to trigger actions in the VMS event handler. Control of the outputs can be directly by the operator, or as an action from the VMS event handler.
 
[[File:Support_for_ DeviceIO.png|thumb|left|700px|Support for DeviceIO]]
 
<br clear=all/>
 
=====Report DAK as Digital Input in ONVIF=====
 
Other than the general purpose inputs which are available on the station, it is possible to have a DAK-button press reported as an input to the VMS. This can for instance be used as an additional way of signalling that there is somebody at the door, wanting to talk to the operator. (Turbine stations only)
 
 
 
=====Report station call events as Digital Input in ONVIF=====
 
Stations know the state they are in: in a call, ringing, in call requester mode. This state information is now available to the ONVIF module in the station software and can be used to provide a number of additional 'virtual' inputs. These inputs are discovered through DeviceIO, in the way any physical input is discovered. States that can be signaled to the VMS are:
 
*Call established - Call in progress input Activated
 
*Call ended - Call in progress input Deactivated
 
*Station in ringing mode - both for an outgoing (ringback) and incoming call - Call ringing input Activated
 
*Station ringing mode ended - Call ringing input Deactivated
 
*Station has made a call request or ringing group call (only when the station is in AlphaCom mode) - Call queued input Activated
 
*Station leaves call request or ringing group call mode (only when the station is in AlphaCom mode) - Call queued input Deactivated
 
Use cases that can be solved by these inputs are:
 
*Switching a camera to a monitor pane at the start of a conversation
 
*Starting and stopping video and/or audio recording
 
*Adding an entry in a the log for audit trail purposes
 

Latest revision as of 16:18, 27 November 2023

AEIS.png
ONVIF overview.png


ONVIF is an open industry forum that provides and promotes standardized interfaces for effective interoperability of IP-based physical security products.

ONVIF profiles make it easy to recognize how ONVIF conformant devices and clients are compatible with one another. An ONVIF profile has a fixed set of features that must be supported by a conformant device and client. It ensures that a client that conforms to Profile S, for example, will work with a device that also conforms to Profile S. There are also conditional features, which are features that shall be implemented by an ONVIF device or ONVIF client if it supports that feature in any way, including any proprietary way. Optional functionalities are also defined, they do not need to be implemented but can if it's chosen. Clients and devices can support more than one ONVIF profile.

New from version 7.1.3.0:

  • ONVIF over HTTPS is now supported, this also includes video over HTTPS tunneling.
  • Devices can now send SIP name as hardware model


Video Intercoms

Supported video devices

  • TCIV
  • TCIV+/TKIV+
  • TMIV+
  • TEIV+

ONVIF configuration

Some ONVIF settings are available from the station web interface.

ONVIF settings in stations with camera


  • Enable ONVIF Discovery Service - Enables UDP port 3702 on station firewall. Traffic to this port is used for WS-Discovery Service. If this setting is turned off, the station can not be discovered by any ONVIF client
    • ONVIF WS-Discovery Name: Sets device name for WS-Discovery that will be shown in ONVIF client after the device is found
    • ONVIF WS-Discovery Location: Sets device location for WS-Discovery that will be shown in ONVIF client after the device is found
  • Enable control of relay IDLE state- Some Security systems automatically force relay IDLE state = On, and it is not possible to configure it. If this is an undesirable scenario, this option can be disabled
  • Operate relay/outputs via ONVIF (ICX-AlphaCom mode only) - If enabled, Relay/Output can be controlled from both ICX-AlphaCom server and through ONVIF protocol so the user needs to pay attention for possible conflicts
  • Report DAK as Digital Input in ONVIF: Call button pressed on a station is reported as Digital Input to a Video Management System.
  • Report Station call events as Digital Input in ONVIF (default Disabled): Send station call status as Digital Inputs to a Video Management System. Supported call states are:
    • In Conversation
    • Ringing
    • In call queue (ICX-AlphaCom mode only)
  • Send SIP name as hardware model: Device is able to send custom name if default name is changed.

ONVIF Media Profiles ONVIF Media profiles control real-time video and audio streaming configurations. A media profile maps a video and audio source to a video and an audio encoder, PTZ and analytics configurations. Video turbines support only video encoder configuration which is described below. Video and audio sources cannot be configured since the device contains only one camera and microphone.

In most cases, media profiles are configured directly from Video Management System software (ONVIF client) and in that case, it is not recommended to manually change values below. The maximum number of Media Profiles which can be created is 50.

  • Choose profile to configure - contains list of all profiles (built-in profiles and profiles created by ONVIF clients) for configuration. Profiles can be added and deleted only by ONVIF clients.

Encoder - each profile should be assigned with one ONVIF video encoder configuration. Possible options are Encoder 1, Encoder 2 or Encoder not set (This option is only used in situations when VMS creates media profile without video encoder and should never be manually selected).Encoder is defined with following parameters:

  • Encoding - Defines which encoding type will be used:
    • H264
    • JPEG
  • Resolution: Sets the pixel resolution:
    • 1080P [H264 only]
    • 720P [H264 only]
    • 480P
    • 240P
  • Frames per second: Sets the framerate per second:
    • 5-30 for H264
    • 5-10 for JPEG
  • Bitrate: Sets the bitrate which will be used in video stream (H264 only)
  • Quality: Video quality parameter which is going to be used. It will have an effect for JPEG encoding only. Relative value for the quality of the video. A high value within supported quality range means higher quality
  • GovLength: the interval in which the I-Frames will be coded. An entry of 2 indicates that every 2nd image is an I-Frame, and 3 only every 3rd frame, etc. The frames in between are coded as P or B Frames. Valid values are from 2 to 32767. Will have effect for H264 encoding only.
Note icon The login credentials used for ONVIF are different from the login credentials used for the web interface. To change the ONVIF login credentials, ONVIF Device Manager should be used.


Non-Video Intercoms

Supported non-video devices

  • TCIS/TKIS
  • TFIE/TKIE
  • TMIS
  • TFIX
  • V2 Master Stations
  • IP Speakers

ONVIF configuration

Some ONVIF settings are available from the station web interface.

ONVIF settings in stations without camera


  • Enable ONVIF Discovery Service - Enables UDP port 3702 on station firewall. Traffic to this port is used for WS-Discovery Service. If this setting is turned off, the station can not be discovered by any ONVIF client
    • ONVIF WS-Discovery Name: Sets device name for WS-Discovery that will be shown in ONVIF client after the device is found
    • ONVIF WS-Discovery Location: Sets device location for WS-Discovery that will be shown in ONVIF client after the device is found
  • Enable control of relay IDLE state- Some Security systems automatically force relay IDLE state = On, and it is not possible to configure it. If this is an undesirable scenario, this option can be disabled
  • Operate relay/outputs via ONVIF (ICX-AlphaCom mode only) - If enabled, Relay/Output can be controlled from both ICX-AlphaCom server and through ONVIF protocol so the user needs to pay attention for possible conflicts
  • Report DAK as Digital Input in ONVIF: Call button pressed on a station is reported as Digital Input to a Video Management System.
  • Report Station call events as Digital Input in ONVIF (default Disabled): Send station call status as Digital Inputs to a Video Management System. Supported call states are:
    • In Conversation
    • Ringing
    • In call queue (ICX-AlphaCom mode only)
  • Send SIP name as hardware model: Device is able to send custom name if default name is changed.
Note icon The login credentials used for ONVIF are different from the login credentials used for the web interface. To change the ONVIF login credentials, ONVIF Device Manager should be used.


Additional Information

All Zenitel devices with a camera (TCIV and TCIV+) are certified to ONVIF Profile S. This allows the stations to be discovered by any ONVIF Profile S compliant VMS. As from VS-IS software version 6.4.3.0, a number of additional capabilities have been added:

  • Support for DeviceIO
  • Audio Backchannel, meaning audio from VMS to the device

In addition, some other major changes have been made:

  • Audio only stations which can run VS-IS 6.4.3.0 are now able to generate a video stream, and are therefore compliant with ONVIF Profile S
  • As a further enhancement to DeviceIO, station modes are made available as a logical input to the VMS and can then trigger function in that VMS

Non-Video Intercom stations as ONVIF Profile S compliant devices

The stations generate a video stream (a Zenitel logo) and can be discovered as any other camera. As with the TCIV and TCIV+, the microphone is also discovered as a camera capability.

Audio backchannel

VMS's which support this ONVIF feature will also discover the presence of the station's loudspeaker. This then gives the possibility for the VMS operator to directly send a voice message to the station. This would normally be used when the same message needs to be broadcast to all cameras featuring a loudspeaker and which cannot be reached in the normal Zenitel way, as they are not part of an ICX-AlphaCom, IC-EDGE or SIP system.

DeviceIO

VMS's which support this ONVIF feature will be able to discover the presence of all inputs and outputs on the station. Inputs can be used to trigger actions in the VMS event handler. Control of the outputs can be directly by the operator, or as an action from the VMS event handler.

Support for DeviceIO


Report DAK as Digital Input in ONVIF

Other than the general purpose inputs which are available on the station, it is possible to have a Call-button (DAK) press reported as an input to the VMS. This can for instance be used as an additional way of signalling that there is somebody at the door, wanting to talk to the operator. (Turbine stations only, TCIS and TCIV+)

Report station call events as Digital Input in ONVIF

Stations know the state they are in: in a call, ringing, in call requester mode. This state information is now available to the ONVIF module in the station software and can be used to provide a number of additional 'virtual' inputs. These inputs are discovered through DeviceIO, in the way any physical input is discovered. States that can be signaled to the VMS are:

  • Call established - Call in progress input Activated
  • Call ended - Call in progress input Deactivated
  • Station in ringing mode - both for an outgoing (ringback) and incoming call - Call ringing input Activated
  • Station ringing mode ended - Call ringing input Deactivated
  • Station has made a call request or ringing group call (only when the station is in AlphaCom mode) - Call queued input Activated
  • Station leaves call request or ringing group call mode (only when the station is in AlphaCom mode) - Call queued input Deactivated

Use cases that can be solved by these inputs are:

  • Switching a camera to a monitor pane at the start of a conversation
  • Starting and stopping video and/or audio recording
  • Adding an entry in a the log for audit trail purposes
The order of inputs being reported

The following order, from first to last, is used to report the different inputs if enabled and available.

  • Call Active
  • Call Queued
  • Call Ringing
  • DAK 1....n
  • Inputs 1....n
Input mapping

Click on the link below to select the server platform, then select which ONVIF options you have enabled in the Zenitel Device:

Select the tab that matches with the ONVIF options that are enabled
Default Settings(ICX-Alphacom mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call button) Not enabled Not enabled Not supported
TCIV+ (2 Call buttons) Not enabled Not enabled Not supported
TCIS/TMIS Not enabled Not supported Not supported
IP Desk Master V2
IP Flush Master V2
IP-CROR
Not enabled Not supported Not supported
Only Call events enabled (ICX-Alphacom mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call Button) Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Not enabled Not supported
TCIV+ (2 Call Buttons) Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Not enabled Not supported
TCIS/TMIS Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Not supported Not supported
IP Desk Master V2
IP Flush Master V2
IP-CROR
Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Not supported Not supported
Only Call Button events enabled(ICX-Alphacom mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call Button) Not enabled Input 1: Call Button 1 Not supported
TCIV+ (2 Call Buttons) Not enabled Input 1: Call Button 1
Input 2: Call Button 2
Not supported
TCIS/TMIS Not enabled Not supported Not supported
IP Desk Master V2
IP Flush Master V2
IP-CROR
Not enabled Not supported Not supported
Call events and Call Button events enabled (ICX-Alphacom mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call Button) Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Input 4: Call Button 1 Not supported
TCIV+ (2 Call Buttons) Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Input 4: Call Button 1
Input 5: Call Button 2
Not supported
TCIS/TMIS Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Not supported Not supported
IP Desk Master V2
IP Flush Master V2
IP-CROR
Input 1: Call Active
Input 2: Call Queued
Input 3: Call Ringing
Not supported Not supported
Select the tab that mathces with the ONVIF options that are enabled
Default settings (IC-Edge/SIP mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call Button) Not enabled Not enabled Input 1: I/O 1
Input 2: I/O 2
Input 3: I/O 3
Input 4: I/O 4
Input 5: I/O 5
Input 6: I/O 6
TCIV+ (2 Call Buttons) Not enabled Not enabled Input 1: I/O 1
Input 2: I/O 2
Input 3: I/O 3
Input 4: I/O 4
Input 5: I/O 5
Input 6: I/O 6
TCIS/TMIS Not enabled Not supported Input 1: I/O 1
Input 2: I/O 2
Input 3: I/O 3
Input 4: I/O 4
Input 5: I/O 5
Input 6: I/O 6
IP Desk Master V2
IP Flush Master V2
IP-CROR
Not enabled Not supported Input 1: I/O 1
Input 2: I/O 2
Input 3: I/O 3
Input 4: I/O 4
Input 5: I/O 5
Input 6: I/O 6
Only Call events enabled (IC-Edge/SIP mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call Button) Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Not enabled Input 4: I/O 1
Input 5: I/O 2
Input 6: I/O 3
Input 7: I/O 4
Input 8: I/O 5
Input 9: I/O 6
TCIV+ (2 Call Buttons) Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Not enabled Input 4: I/O 1
Input 5: I/O 2
Input 6: I/O 3
Input 7: I/O 4
Input 8: I/O 5
Input 9: I/O 6
TCIS/TMIS Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Not supported Input 4: I/O 1
Input 5: I/O 2
Input 6: I/O 3
Input 7: I/O 4
Input 8: I/O 5
Input 9: I/O 6
IP Desk Master V2
IP Flush Master V2
IP-CROR
Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Not supported Input 4: I/O 1
Input 5: I/O 2
Input 6: I/O 3
Only Call Button events enabled (IC-Edge/SIP mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call Button) Not enabled Input 1: Call Button 1 Input 2: I/O 1
Input 3: I/O 2
Input 4: I/O 3
Input 5: I/O 4
Input 6: I/O 5
Input 7: I/O 6
TCIV+ (2 Call Buttons)
Not enabled
Input 1: Call Button 1
Input 2: Call Button 2
Input 3: I/O 1
Input 4: I/O 2
Input 5: I/O 3
Input 6: I/O 4
Input 7: I/O 5
Input 8: I/O 6
TCIS/TMIS Not enabled Not supported Input 1: I/O 1
Input 2: I/O 2
Input 3: I/O 3
Input 4: I/O 4
Input 5: I/O 5
Input 6: I/O 6
IP Desk Master V2
IP Flush Master V2
IP-CROR
Not enabled Not supported Input 1: I/O 1
Input 2: I/O 2
Input 3: I/O 3
Input 4: I/O 4
Input 5: I/O 5
Input 6: I/O 6
Call events and Call Button events enabled (IC-Edge/SIP mode)
Call Events Call Button Events Inputs
TCIV+/TMIV+ (1 Call Button) Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Input 4: Call Button 1 Input 5: I/O 1
Input 6: I/O 2
Input 7: I/O 3
Input 8: I/O 4
Input 9: I/O 5
Input 10: I/O 6
TCIV+ (2 Call Buttons) Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Input 4: Call Button 1
Input 5: Call Button 2
Input 6: I/O 1
Input 7: I/O 2
Input 8: I/O 3
Input 9: I/O 4
Input 10: I/O 5
Input 11: I/O 6
TCIS/TMIS Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Not supported Input 4: I/O 1
Input 5: I/O 2
Input 6: I/O 3
Input 7: I/O 4
Input 8: I/O 5
Input 9: I/O 6
IP Desk Master V2
IP Flush Master V2
IP-CROR
Input 1: Call Active
Input 2: Call Queued (only in ICX-Alphacom mode)
Input 3: Call Ringing
Not supported Input 4: I/O 1
Input 5: I/O 2
Input 6: I/O 3



ONVIF Features

General

Feature Profile Additional info Supported from version
Turbine Turbine+ V2 Master stations
Device Discovery S T The ONVIF discovery name of a station shall be the name as known to it from its communication module (ICX-AlphaCom, IC-EDGE, SIP or the upcoming ICX-Next). 6.4.3.0 6.4.3.0 6.4.3.0
Network Configuration S T Configuring network settings of the stations (DHCP, Static IP, Address, etc) 6.4.3.0 6.4.3.0 6.4.3.0
Media Profile Configuration S T Configuration of media profiles in VMS 6.4.3.0 6.4.3.0 6.4.3.0
Media Transport S T Defines the network protocol for streaming either RTP/UDP, RTP/TCP, RTP/RTSP/TCP or RTP/RTSP/HTTP/TCP 6.4.3.0 6.4.3.0 6.4.3.0

Video

Feature Profile Additional info Supported from version
Turbine Turbine+ V2 Master stations
Video streaming MJPEG/MJPEG4 S T Motion JPEG (M-JPEG or MJPEG) is a video compression format in which each video frame or interlaced field of a digital video sequence is compressed separately as a JPEG image. 6.4.3.0 6.4.3.0 6.4.3.0
Video streaming H.264 S T Also known as MPEG-4 Part 10 or Advanced Video Coding (MPEG-4 AVC), H.264 is defined as a block-oriented, compensation-based video compression standard that defines multiple profiles (tools) and levels (max bitrates and resolutions). A codec based on the H.264 standard compresses a digital video file (or stream) so that it only requires half of the storage space (or network bandwidth) of MPEG-2. Through this compression, the codec is able to maintain the same video quality despite using only half of the storage space. 6.4.3.0 6.4.3.0 6.4.3.0
Video streaming RTSP/RTP S T The Real Time Streaming Protocol (RTSP) is a network control protocol used for establishing and controlling media sessions between endpoints. Clients of media servers issue commands such as play, record and pause, to facilitate real-time control of the media streaming from the server to a client (Video On Demand) or from a client to the server (Voice Recording). 6.4.3.0 6.4.3.0 6.4.3.0
Video Source Configuration S T 6.4.3.0 6.4.3.0 6.4.3.0
Media Profile for Streaming Ready out-of-the-box T Allows usage of camera, microphones and speakers out of the box 6.4.3.0 6.4.3.0 6.4.3.0
Imaging Settings S T 6.4.3.0 6.4.3.0 6.4.3.0

Audio

Feature Profile Additional info Supported from version
Turbine Turbine+ V2 Master stations
Audio Streaming G.711 and AAC S T 6.4.3.0 6.4.3.0 6.4.3.0
Audio Output Streaming G.711 and AAC T 6.4.3.0 6.4.3.0 6.4.3.0
Bidirectional audio T 6.4.3.0 6.4.3.0 6.4.3.0

Events

Feature Profile Additional info Supported from version
Turbine Turbine+ V2 Master stations
Event Handling pull point S T Client creates a PullPoint subscription to the Event Service, allowing it to bypass firewall restrictions and WS-Endpoint provides PullMessages operation, which is used by the client to retrieve notifications. 6.4.3.0 6.4.3.0 6.4.3.0
Media Profile Configuration Events T Mostly used for audit trail, events are notifying that the Media profile configuration has been changed 6.4.3.0 6.4.3.0 6.4.3.0

Additional

Feature Profile Additional info Supported from version
Turbine Turbine+ V2 Master stations
Relay Outputs S T Enables you to open door by triggering the relay on the station 6.4.3.0 6.4.3.0 6.4.3.0
Send SIP name as HW model S T Device is able to send custom name if default name is changed. 7.1.3.0 7.1.3.0 7.1.3.0