Help with SIP Options Ping

When running the Sip Options Ping sensor, PRTG starts an Application, that creates UPD packets and sends them to the device to the configured port. Then it waits for a response from the device. If the Application doesn't return anything within the given timeout, PRTG kills the task and returns a timeout error.

I assume the sensor picks up the IP address of its parent device then?

I cannot see why it is not working then. How should I go about debugging this? The phone system is asterisk based and I have simply entered details of an existing extension I know will work.

Yes it does. In the PRTG directory, you can find a subdirectory called "Sensor System". In this directory, you can find a file called "SipOptionsPingSensor.exe". You can run this application with the following parameters: -ip=<IPAddress> -port=<Portnumber> -user=<Username> -pw=<password> [-timeout=<Timeout in Seconds>] [-retry=<Number of retrys>]

The programm will exit afterwards, so either use a command shell or redirect the output to a textfile.

If you need further assistance with debugging, we need to know the output of this Application. If it takes a minute or longer, please kill the application and let us know. We will think of something to help you, then.

Have tried running with the command line as follows:

C:\Program Files (x86)\PRTG Network Monitor\Sensor System>sipoptionspingsensor - ip=192.168.0.250 -port=5060 -user=6039 -pw=<password> -timeout=60

I get no output at all and it just sits there without completing!

I have disabled my local firewall also but this has not helped.

I am having the same issue however running the "sipoptionspingsensor.exe" does nothing and produces no output.

We could not recreate this behavior so far.

It would help a lot, if you answered the following questions:

• Which SIP server/service are you using?
• What versions of the dotNet framework do you use on the system, your PRTG is running on?
• If you use a remote probe, what versions of dotNet are used there If there is more than 1 version installed on one of the system, please give us a list of all versions.

We'll continue searching for the problem and try to fix this as soon as possible.

We spend a lot of time searching for this error, but we weren't able to recreate it in our test environment. We're very sorry, but we will not be able to provide a fix for this problem.

Fantastic, could you confirm when it will be released?

Sorry, we can't give an exact ETA, but the fix should arrive in the stable channel at latest within the next 4 weeks. Please bear with us.