How to Create Devices and Targets

How It Works

VoIP/SIP monitoring tasks create monitoring agents that connect to a specified VoIP server using the supplied credentials to ensure that the service is available.  To accomplish this, SIP monitoring is provisioned as either an extension or a client on the VoIP system and configured to call a specific number using a specified SIP server with certain parameters. The expected result of the call is set up as “Answer,” “No Answer,” “Busy,” or an error condition (if there is an unexpected result).

Creating a Target

Hostname

Enter the domain address or an IP address of a PBX or VoIP Service provider.

Port

Enter the port number of the service you wish to check.

User Name

This field contains a SIP username in a source domain.

Time Validation Threshold (in seconds)

Enter the number of seconds the task should wait for a response from the web page before ending the task and returning an error. If this is left blank the default timeout for a task is 120 seconds.

Use TLS

Specify whether the incoming server requires a secure connection using SSL or TLS.

Perform Register

The registration process creates the binding between caller ID (SIP URL like “username@domain.com”) and its address. Please see RFC 3261 paragraph 10 for more information.

Authorization

Contains name used for an authentication session, it may match the username.

Password

Contains a password for SIP authentication if it is required.

Display Name

The name that will be displayed on the interface (according to RFC 3261).

Perform a Call

When enabled a call will be performed.

Number 

Contains the destination phone number. If the number is located in another domain (belongs to another PBX) you may have to specify a number (name) and domain name in the following format: number(name)@destination_domain.com. Domains can be specified directly by their IP addresses.

Otherwise, you can enter the number directly as 15554441234.

Expected Call Result

 This field contains the designation for the expected behavior of the called party.

Use SRTP

SRTP is a security profile for RTP that adds confidentiality, message authentication, and replay protection to that protocol. It is specified in RFC 3711.
Note that you must at least perform a register or perform a call and you can perform both in the same task (as some systems may require you to register in order to perform a call).

DNS Options

The DNS Options feature allows users to choose how domain name server (DNS) requests are conducted during a monitoring task.

To specify the mode of resolving hostnames, in the DNS Resolve Mode section, select one of the available modes. For more details on the feature configuration, see DNS Mode Options.

The Custom DNS Hosts section allows to set up the mapping of IP addresses to hostnames. IPv6 and IPv4 DNS resolution is supported.

To specify the mapping, enter the IP address and the hostname in the corresponding fields.

Examples:

192.168.107.246   example.com user.example.com userauth.example.com tools.example.com
192.168.107.246   example.com
192.168.107.246   user.example.com
192.168.107.246   userauth.example.com

See also: DNS Mode Options.

Error Filter

You can set a filter to ignore specific error types and codes. In the Error Filter section, you can filter out certain user-configurable errors. For example, DNS errors could be filtered out based on who is responsible for DNS server operations. You can create filters that will ignore specific errors that you know may occur and are not relevant to the goal of a specific device.

In addition, you can set up the system to ignore a range of error codes using a dash, or multiple error codes using semicolons as a separator.

For example, if on one particular device, you do not care about 404 errors, you can filter them out so that you do not receive alerts when they are detected.

Note that if an error matches the filter conditions, the error will not be reflected on the reports and can’t be tracked down.