The endpoint program uses network application programming interfaces, such as Sockets, for all of its communications. The endpoint dynamically configures its own programs, so you do not have to update the configuration files for your communications software. However, your communications software must be configured and running correctly. The following steps guide you through this verification process.
Determine the network addresses of the computers to be used in tests.
Select a service quality.
Verify the network connections.
The RTP, TCP, and UDP protocols use TCP/IP software for network communications. TCP/IP offers two forms of network addresses: IP addresses and domain names. An IP address is a 32-bit numeric address. It is represented in dotted notation, such as 126.96.36.199. As an alternative, use domain names, which are in a format that is easier to recognize and remember. To use domain names, you need either a Domain Name Server (DNS) set up in your network or an /etc/hosts file on each computer.
To determine the local IP address for a Windows computer, enter the following at a command prompt:
If your TCP/IP stack is configured correctly, your output will look like the following:
Windows IP Configuration Ethernet adapter Local Area Connection: IP Address. . . . . . . . . : 10.10.44.3 Subnet Mask . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . : 10.10.44.254
The local IP address is shown in the first row. In this example, it is 10.10.44.3.
To determine a the local hostname for a Windows computer, enter the following at a command prompt:
The current hostname is shown in the first row.
Ping is a simple utility program, included in all TCP/IP implementations. To check the connection from one computer to another, enter the following at a command prompt:
Replace the x’s with the IP address of the target computer. If Ping returns a message that says “Reply from xx.xx.xx.xx ...,” the Ping worked. If it says “Request timed out,” the Ping failed, and you have a configuration problem.
From your AppManager, Vivinet Assessor, or Vivinet Diagnostics console computers, ensure you can run Ping successfully to each computer serving as Endpoint 1, and between each pair of endpoints involved in a test, before starting your testing with TCP/IP.