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.
Determine the network addresses of the computers to be used in tests.
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 199.72.46.202. 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.
Use one of the following methods to determine the IP address of the local computer you are using:
For the IBM System Management Interface Tool (SMIT), open the Communications Applications and Services menu, then the TCP/IP menu, and then the Minimum Configuration & Startup menu. Next, select the network interface used to reach other endpoints (for example, en0 or tr0). SMIT displays the network interface configuration. Your host IP address is in the Internet ADDRESS field.
Enter the following at a command prompt: netstat -in
You may have several network interfaces. If you are using a LAN network, for example, look at the output for the en0 interface. Your local IP address is shown in the “Address” column.
Ping is a simple utility program, included in all TCP/IP implementations. To test the connection from one computer to another, enter the following at a command prompt:
ping xx.xx.xx.xx 64 1
Replace the x’s with the IP address of the target computer. If Ping returns a message that says “1 packets transmitted, 1 packets received, 0% packet loss,” the Ping worked. Otherwise, there will be a delay, and then you will see the following message:
1 packets transmitted, 0 packets received, 100% packet loss
This error message indicates the Ping failed, and you cannot reach the target computer.
Ensure you can run Ping successfully from the AppManager console computer to each computer serving as Endpoint 1, and between each pair of endpoints involved in a test, before starting your testing with TCP/IP.
TCP/IP applications use their network address to decide which computer to connect to in a network. They use a Sockets port number to decide which application program to connect to within a computer.
The TCP/IP sockets port number for endpoints is 10115. This port number is used during the initialization of a test. During the actual running of the test, other port numbers are used.