IP Notify Profiles

In the IP Notify Profiles dialog, you can configure the network messages that the camera uses in case of an alarm to send text messages to the TCP port of a computer or camera and, thus, trigger e.g. other events (observation chain).

Open the Messaging dialog to link the profiles created here with the respective events.

Notes:

Instead of the IP addresses used here, you can also use the DNS names of cameras or computers (e.g. cam1.myintranet.net or myserver.myintranet.net) if these names have been defined in the DNS servers (Ethernet Interface dialog).
Click on the More button at the bottom of the dialog to display all options for all profiles.

Profiles & Options

For each profile, set the following parameters in the IP Notify Profiles dialog:

Option Parameter

IP Notify Profile n

Enter a unique profile name. Valid characters for profile names are letters, digits, hyphen, dot and underscore.

IP Notify Type

Predefined Configuration can have the following values:

MxCC Alarm: Simple
This type sends a predefined IP notify (network) message to the alarm list of the computer running MxControlCenter.
MxCC Alarm: acknowledge required
This type also sends a predefined IP notify (network) message to the alarm list of the computer running MxControlCenter, but the user needs to acknowledge every new alarm by clicking onto the corresponding alarm in the alarm list. If the alarm is not acknowledged within 60 seconds, the camera signals a transmission error.
Custom Configuration
Displays the additional Data Protocol and Data Type sections so the camera can send special network messages. (Please also see the explanation of the Sample Profiles.)

Destination Address

Enter the IP address(es) and the port(s) (separated by a colon) to which the camera is supposed to send the network message in the Destination Address field.

Example:	`192.155.13.22:8000` `alertcenter1.mycompany.net:8701`

Remarks:

If you would like to send the message to several computers, enter each IP address in a separate line.
If the IP message could not be transmitted, the camera will issue an error message as described in the Errors When Sending IP Messages section.
It is also possible to use symbolic names. In order to do so, you need to enter a DNS server in the Ethernet Interface dialog.

Set the Send Order for sending the IP message:

Parallel send to all (default): The camera tries to send the message to all Destination Addresses simultaneously.
Sequential send to all: The camera tries to send the message to all Destination Addresses one after another.
Send to next on error: The camera stops after the first successful transmission or will try the next IP address if the current transmission has failed.

Data Protocol

Set the transfer protocol to use in the Data Protocol selection box:

Raw TCP/IP: Sends the raw data in TCP packets. Use this protocol if you would like to transmit data only (e.g. for triggering other cameras).
HTTP/1.0 Request: Sends the data as an HTTP request to the receiving computer (a MOBOTIX camera or a web server).
HTTP/1.0 Request + Acknowledge: Sends the data as an HTTP request to the receiving computer (a MOBOTIX camera or a web server). The camera will only consider the IP Notify message as successfully sent, if the receiving computer returns a confirmation message.

Transfer Protocol:
Raw TCP/IP

If Transfer Protocol has been set to Raw TCP/IP, the following options appear:

Separator for Raw TCP/IP: This string is inserted between the individual parts of a message (e.g. images) in order to allow separating them at the receiving end. Enter a unique string (default: --next-image--) that is not used otherwise in the transmitted data.

Transfer Protocol:
HTTP/1.0 Request,
HTTP/1.0 Request + Acknowledge

If Transfer Protocol has been set to HTTP/1.0 Request, the following options appear:

CGI Path: Enter the absolute path (has to start with "/") of the script on the target computer that will process the request, (e.g. /cgi-bin/newmessage.cgi).
HTTP Authentication: Enter the user name and password information (user:password) in this field that are required to log onto the destination computer.

Data Type

Select the Notification Data you would like to send to the destination computer:

Plain text: Transmits raw text data only.
MxPEG or JPEG clip: Transfers image data as MxPEG clip with audio or JPEG files.
Image information (JPEG comment): Transmits the image information of the current live image as it is written into the header of the JPEG image.
System messages: Transmits the system messages of the sending camera.
Web Server Log: Transfers the Web Server Logfile of the camera.

Notification Data:
Plain text

Enter the text to send in the Message field. This text can be a simple text message for triggering the IP Receive (RC) event in the receiving camera (see the SimpleNotify example profile) or a command passed to a CGI script (see the HttpRequest example profile).

You can enter any text and use predefined variables. For a complete list of variables, see the Variables help page.

Notification Data:
MxPEG or JPEG clip

Select the file format of the image files:

MxPEG clip file: Transmits the image data as MxPEG clips with audio.
Clip as JPEG file(s): Transmits the image data as single JPEG files.

Set the desired Clip Frame Rate and the time to include before and after the event(Time Before and Time After).

Note:	The frame rate set in these boxes depends on a number of factors (e.g. the processor load at the time of the event) and may not reach the set frame rate.

Notification Data:
System Messages

Select the System Message Scope to include the desired range of system messages.

Send Port

When using a firewall, you can set a different send port for your camera. In order to do this, click on the More button and enter the port of your choice in the Send Port field.
The factory default setting for the send port is 0 (automatic).

Note:	This feature is not available for Web and Basic models.

Errors When Sending IP Messages

In order to ensure the successful transmission of a network message, the receiving computer has to acknowledge the message. If a network message cannot be transmitted successfully (broken connection, computer down, ...), this will result in an error that is logged in the camera's System Messages dialog with an IPMSG Service tag and the profile name in the ID column.

Testing Profiles

If you have created or modified one or more profiles, you should test the profiles (after you have closed the dialog using the Set and Close buttons and you have stored the configuration permanently). Open the Test Current Network Configuration dialog for testing. Click on the Send button behind the corresponding profile and monitor the output on the Network Test Log window. For additional information on this topic, see the Test Network Current Configuration help page.

Deleting Profiles

In order to delete a profile, check the Delete option in the top right corner of the profile. The profile will be deleted as soon as you click on the Set button in the lower part of the dialog.

Example Profiles

Profile	Explanation
`MxCC-Alarm`	This profile sends a predefined IP notify (network) message to the alarm list of the computer with the IP address `10.0.0.42` (port `8000`), which is running MxControlCenter. If Predefined Configuration has been set to MxCC Alarm: acknowledge required instead of MxCC Alarm: simple, the user needs to acknowledge every new alarm by clicking onto the corresponding alarm in the MxControlCenter alarm list.
`MxGuard-PopUp`	This profile sends a simple text message to port `81` of the computer with the IP address `10.0.0.42`. If MxGuard is running on this computer, the application will display the corresponding alarm image. The message contains the camera name `$(ID.NAM)` and the event number as variables `$(FPR.ENO)`.
`SimpleNotify`	This profile sends a simple text message to port `8000` of the IP address `10.0.0.42`. The message contains the camera name `$(ID.NAM)` and the event number as variables `$(FPR.ENO)`.
`MultipleNotify`	This profile also sends a simple text message, but this time simultaneously to port `8000` of the IP addresses `10.0.0.42` and `10.1.0.94`. The message is the same as in `SimpleNotify` as it contains the camera name `$(ID.NAM)` and the event number as variables `$(FPR.ENO)`.
`HttpRequest`	This profile sends a command to the default HTTP port `80` of the camera's web server (`localhost`). The camera will pass the command `action=ledson&leds=BBBBBB&time=5` to the script `/control/rcontrol`, which will prompt the camera LEDs to blink for five seconds. For additional information on camera commands, see the following help pages: `/control/control`: Changing settings of the Setup Menu. `/control/rcontrol`: Executing camera functions.

Storing the Configuration

Click on the Set button to activate your settings and to save them until the next reboot of the camera.

Click on the Close button to close the dialog. While closing the dialog, the system checks the entire configuration for changes. If changes are detected, you will be asked if you would like to store the entire configuration permanently.

de, en