<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: SIP Options Ping Sensor

.NET 4.7.2 or later

This sensor requires .NET 4.7.2 or later from Microsoft on the probe system. In a cluster, install it on every cluster node.

If the framework is missing, you cannot create this sensor.

For more information, see the Knowledge Base: Which .NET version does PRTG require?

IPv6

This sensor supports IPv6.

Performance impact

This sensor has a low performance impact.

Lookups

This sensor uses lookups to determine the status values of one or more channels.

Error message

An SIP server might return the error '480 Service temporarily unavailable' until at least one reachable SIP client is connected to the server.

Port

Enter the number of the port to which this sensor connects. Enter an integer. The default User Datagram Protocol (UDP) port is 5060.

User Name

Enter the user name of the SIP user account that this sensor logs in to after a successful connection to the SIP server. Enter a string.

Password

Enter the password of the SIP user account that this sensor logs in to after a successful connection to the SIP server. Enter a string.

Timeout (Sec.)

Enter the timeout for the connection to the SIP server. Enter an integer. The maximum timeout value is 300 seconds (5 minutes).

Retry Count

If the connection to the SIP server fails, the sensor tries to connect again. Enter the maximum number of retries. After the sensor reaches the maximum count, it shows the Down status. Enter an integer.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.
• Store result: Store the sensor result and the last response in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status.

Response Code

The response code

You can individually define the status for each individual response code by editing the lookup file prtg.standardlookups.sip.statuscode.

This channel is the primary channel by default.

Response Time

The response time