SIP UA [Server: CSCO/6] detected on 10.0.0.250:5060

This test identifies the encryption capabilities of the target host.The connection was refused during a communication with the target host which implies that the target host does not support SIPS.

If the organizational policy requires protection of the signaling messages, enable the TLS (SIPS) feature on the target host. TLS provides additional protection from various attacks including eavesdroping.

This check verifies the ability of the UA to authenticate REGISTER requests.

It appears that the target UA does not authenticate REGISTER requests using UDP. This configuration allows unauthorized users to generate malicious messages in order to hijack user registration and ultimately divert calls or perform other undesired functions. Change the configuration of the SIP component to require authentication of REGISTER requests.

This check verifies the ability of the UA to authenticate INVITE requests.

It appears that the target UA does not authenticate INVITE requests using UDP. This configuration allows unauthorized users to generate malicious messages. Change the configuration of the SIP component to require authentication of INVITE requests.

This check verifies the ability of the UA to handle 1000 occurrences of the -sip- tag in a SIP message, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 1000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 1000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 occurrences of the -sip- tag in a SIP message, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 3000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 3000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 occurrences of the -sip- tag in a SIP message, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 5000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 5000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 occurrences of the -sip- tag in a SIP message, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 500 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 500 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 occurrences of the -sip- tag in a SIP message, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 1000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 1000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 occurrences of the -sip- tag in a SIP message, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 5000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 5000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 occurrences of the -sip- tag in a SIP message, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 500 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 500 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 occurrences of the -sip- tag in a SIP message, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 1000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 1000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 occurrences of the -sip- tag in a SIP message, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 3000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 3000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 occurrences of the -sip- tag in a SIP message, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 5000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 5000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 occurrences of a malformed -sip- tag (e.g. sip:sip: ...) in a SIP message, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 3000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 3000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 occurrences of a malformed -sip- tag (e.g. sip:sip: ...) in a SIP message, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 5000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 5000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 occurrences of a malformed -sip- tag (e.g. sip:sip: ...) in a SIP message, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 3000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 3000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 occurrences of a malformed -sip- tag (e.g. sip:sip: ...) in a SIP message, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests with 5000 occurances of -sip- tag in a SIP message. Ensure that the UA can process requests that contain 5000 -sip- tags in a SIP message. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of null characters between the method field and the URI in a INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 5000 null characters between the INVITE method and the URI. Ensure that the UA can accept malicious requests that contain 5000 null characters between the INVITE method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of null characters between the method field and the URI in a OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 50 null characters between the OPTIONS method and the URI. Ensure that the UA can accept malicious requests that contain 50 null characters between the OPTIONS method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of null characters between the method field and the URI in a OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 100 null characters between the OPTIONS method and the URI. Ensure that the UA can accept malicious requests that contain 100 null characters between the OPTIONS method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of null characters between the method field and the URI in a OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 500 null characters between the OPTIONS method and the URI. Ensure that the UA can accept malicious requests that contain 500 null characters between the OPTIONS method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of null characters between the method field and the URI in a OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 1000 null characters between the OPTIONS method and the URI. Ensure that the UA can accept malicious requests that contain 1000 null characters between the OPTIONS method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of null characters between the method field and the URI in a OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 3000 null characters between the OPTIONS method and the URI. Ensure that the UA can accept malicious requests that contain 3000 null characters between the OPTIONS method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of null characters between the method field and the URI in a OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 5000 null characters between the OPTIONS method and the URI. Ensure that the UA can accept malicious requests that contain 5000 null characters between the OPTIONS method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of null characters between the method field and the URI in a REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 50 null characters between the REGISTER method and the URI. Ensure that the UA can accept malicious requests that contain 50 null characters between the REGISTER method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of null characters between the method field and the URI in a REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 1000 null characters between the REGISTER method and the URI. Ensure that the UA can accept malicious requests that contain 1000 null characters between the REGISTER method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of null characters between the method field and the URI in a REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 3000 null characters between the REGISTER method and the URI. Ensure that the UA can accept malicious requests that contain 3000 null characters between the REGISTER method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of null characters between the method field and the URI in a REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 5000 null characters between the REGISTER method and the URI. Ensure that the UA can accept malicious requests that contain 5000 null characters between the REGISTER method and the URI. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of null characters between the method field and the version in a SIP message, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 3000 null characters between the URI and the version in the URI of a SIP message. Ensure that the UA can accept malicious requests that contain 3000 null characters between the REGISTER URI and the version. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of null characters between the method field and the version in a SIP message, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests of 5000 null characters between the URI and the version in the URI of a SIP message. Ensure that the UA can accept malicious requests that contain 5000 null characters between the REGISTER URI and the version. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of null characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 50 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 50 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of null characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 100 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 100 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of null characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 5000 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 5000 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of null characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 50 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 50 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of null characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 100 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 100 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of null characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 500 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 500 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of null characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 1000 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 1000 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of null characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 3000 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 3000 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of null characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 5000 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 5000 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of null characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 50 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 50 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of null characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 100 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 100 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of null characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 500 null characters in the SIP message. Ensure that the UA can process such malicious requests that contain 500 null characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 50 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 50 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 100 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 100 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 500 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 500 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 1000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 1000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 3000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 3000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed characters in a SIP message with no additional headers, using INVITE request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 5000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 5000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 50 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 50 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 100 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 100 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 500 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 500 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 1000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 1000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 3000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 3000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed characters in a SIP message with no additional headers, using OPTIONS request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 5000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 5000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 50 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 50 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 100 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 100 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 500 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 500 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 1000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 1000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 3000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 3000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed characters in a SIP message with no additional headers, using REGISTER request over UDP.

It appears that the target UA could not handle SIP (over UDP) requests owith 5000 intermixed characters in the SIP message. Ensure that the UA can process such malicious requests that contain 5000 nintermixed characters. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 50 intermixed alphanumeric characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 50 as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 100 intermixed alphanumeric characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 100 as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 500 intermixed alphanumeric characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 500 as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 1000 intermixed alphanumeric characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 1000 as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 3000 intermixed alphanumeric characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 3000 as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 5000 intermixed alphanumeric characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 5000 as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 50 intermixed alphanumeric characters as the username in a URI using the REGISTER requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 50 as the username in the URI in a REGISTER request. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 100 intermixed alphanumeric characters as the username in a URI using the REGISTER requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 100 as the username in the URI in a REGISTER request. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 500 intermixed alphanumeric characters as the username in a URI using the REGISTER requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 500 as the username in the URI in a REGISTER request. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 1000 intermixed alphanumeric characters as the username in a URI using the REGISTER requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 1000 as the username in the URI in a REGISTER request. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 3000 intermixed alphanumeric characters as the username in a URI using the REGISTER requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 3000 as the username in the URI in a REGISTER request. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 5000 intermixed alphanumeric characters as the username in a URI using the REGISTER requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 5000 as the username in the URI in a REGISTER request. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 3000 control characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 3000 using control characters as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 3000 control characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle a string of 5000 control characters as the username in a URI using the OPTIONS requestover UDP.

It appears that the target UA could not handle SIP requests (over UDP) of 5000 using control characters as the username in the URI in a OPTIONS request. Ensure that the UA can accept malicious requests that contain 5000 control characters as the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the From field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 50 space characters in the From field. Ensure that the UA can accept malicious requests that contain 50 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the From field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 100 space characters in the From field. Ensure that the UA can accept malicious requests that contain 100 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the From field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 500 space characters in the From field. Ensure that the UA can accept malicious requests that contain 500 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the From field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the From field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the From field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the From field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 space characters in the From field. Ensure that the UA can accept malicious requests that contain 50 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the From field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 space characters in the From field. Ensure that the UA can accept malicious requests that contain 100 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the From field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 space characters in the From field. Ensure that the UA can accept malicious requests that contain 500 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the From field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the From field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the From field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the From field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 space characters in the From field. Ensure that the UA can accept malicious requests that contain 50 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the From field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 space characters in the From field. Ensure that the UA can accept malicious requests that contain 100 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the From field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 space characters in the From field. Ensure that the UA can accept malicious requests that contain 500 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the From field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the From field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the From field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 space characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the From field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the username in the From field. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using INVITE request over UDP.

It appears that the target UA could not handle requests of 50 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 50 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using INVITE request over UDP.

It appears that the target UA could not handle requests of 100 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 100 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using INVITE request over UDP.

It appears that the target UA could not handle requests of 500 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 500 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 50 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 100 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 500 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 50 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 100 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 500 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the user's sip address (e.g. alice@biloxi.com), and the tag field, (within a From header) using REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 space characters between the user's address and the "tag" field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the user name and the "tag" field. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests with strings consisting of 50 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests with strings consisting of 100 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests with strings consisting of 500 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests with strings consisting of 1000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests with strings consisting of 3000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests with strings consisting of 5000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests with strings consisting of 50 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests with strings consisting of 100 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests with strings consisting of 500 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests with strings consisting of 1000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests with strings consisting of 3000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests with strings consisting of 5000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests with strings consisting of 50 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 50 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests with strings consisting of 100 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 100 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests with strings consisting of 500 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 500 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests with strings consisting of 1000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 1000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests with strings consisting of 3000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 3000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of control characters as the display username, between the From field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests with strings consisting of 5000 control characters as the display name between the From field and the URI. Ensure that the UA can accept malicious requests that contain 5000 control characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 50 < characters in the From field. Ensure that the UA can accept malicious requests that contain 50 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 100 < characters in the From field. Ensure that the UA can accept malicious requests that contain 100 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 500 < characters in the From field. Ensure that the UA can accept malicious requests that contain 500 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 < characters in the From field. Ensure that the UA can accept malicious requests that contain 50 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 < characters in the From field. Ensure that the UA can accept malicious requests that contain 100 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 < characters in the From field. Ensure that the UA can accept malicious requests that contain 500 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 < characters in the From field. Ensure that the UA can accept malicious requests that contain 50 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 < characters in the From field. Ensure that the UA can accept malicious requests that contain 100 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 < characters in the From field. Ensure that the UA can accept malicious requests that contain 500 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 < characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 < characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 50 > characters in the From field. Ensure that the UA can accept malicious requests that contain 50 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 100 > characters in the From field. Ensure that the UA can accept malicious requests that contain 100 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 500 > characters in the From field. Ensure that the UA can accept malicious requests that contain 500 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of < characters before the URI in the From field using INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 > characters in the From field. Ensure that the UA can accept malicious requests that contain 50 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 > characters in the From field. Ensure that the UA can accept malicious requests that contain 100 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 > characters in the From field. Ensure that the UA can accept malicious requests that contain 500 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of < characters before the URI in the From field using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 > characters in the From field. Ensure that the UA can accept malicious requests that contain 50 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 > characters in the From field. Ensure that the UA can accept malicious requests that contain 100 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 > characters in the From field. Ensure that the UA can accept malicious requests that contain 500 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 1000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 3000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of < characters before the URI in the From field using REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 > characters in the From field. Ensure that the UA can accept malicious requests that contain 5000 > characters between the From header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the "To" field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 50 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 50 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the "To" field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 100 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 100 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the "To" field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 500 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 500 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the "To" field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the "To" field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the "To" field and the username in a INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the "To" field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 50 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the "To" field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 100 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the "To" field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 500 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the "To" field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the "To" field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the "To" field and the username in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of space characters between the "To" field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 50 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of space characters between the "To" field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 100 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of space characters between the "To" field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 500 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of space characters between the "To" field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 1000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of space characters between the "To" field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 3000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of space characters between the "To" field and the username in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 space characters in the "To" field. Ensure that the UA can accept malicious requests that contain 5000 space characters between the "To" header field and the username. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 50 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 100 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 500 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 1000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 3000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 5000 alphanumeric characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 50 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 100 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 500 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 1000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 3000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the display username, between the "To" field and the SIP URI (e.g. ), in a REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the display name between the "To" field and the URI. Ensure that the UA can accept malicious requests that contain 5000 intermixed characters as the user's display name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 50 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 100 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 500 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 1000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 3000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 5000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 50 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 100 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 500 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 1000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 3000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 5000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 50 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 50 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 100 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 100 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 500 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 500 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 1000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 1000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 3000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 3000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of alphanumeric characters as the username, in the SIP URI (e.g. ) within the "To" field, using REGISTER request over UDP.

It appears that the target UA could not handle requests of 5000 alphanumeric characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 5000 alphanumeric characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 50 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 100 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 500 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 1000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 3000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using INVITE request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 5000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 50 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 50 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 100 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 100 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 100 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 500 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 500 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 500 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 1000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 1000 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 1000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 3000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 3000 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 3000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 5000 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g. ) within the "To" field, using OPTIONS request over UDP.

It appears that the target UA could not handle requests of 5000 intermixed characters as the username in the "To" field. Ensure that the UA can handle malicious requests that contain 5000 intermixed characters as the user name. The remote host closed the network connection abruptly (no SIP response was received) during this test, but after verification the process is still running. This may be an indication of a buffer overflow which causes the server process to close the remote connection prematurely. Caused by Socket timedout

This check verifies the ability of the UA to handle 50 of intermixed (alphanumeric and special) characters as the username, in the SIP URI (e.g.