VPIM Networking problems

Common causes of VPIM Networking problems include the following:

• VPIM Networking is disabled.

• Incoming VPIM messages from remote sites or desktop messaging and My CallPilot users are refused by CallPilot because of too many SMTP authentication failures.

• Networking information is not correct or is not complete.  

• Network devices are not configured correctly.

• CallPilot is not configured correctly.

• There are hardware problems.

TCP/IP troubleshooting

Problems with the TCP/IP data network affect the performance of VPIM Networking.

• Ensure that you can ping successfully.

• Ensure that you can establish a session with a host.

The ping utility measures the time that it takes for a packet of information to travel from one host to the next.

• Ping your IP address to verify that it was configured correctly.
  Note: If this step is unsuccessful, check the configuration in the Network program of the Control Panel.
  Check the following:
  - Address is entered correctly.
  - IP address is valid.
  - IP address follows addressing guidelines.

• Ping the IP address of the default gateway to verify that the gateway is functioning and configured correctly.
  Note: If this step is unsuccessful, check that the IP address is correct.

• Ping the IP address of a remote host to verify the connection to the data network.
  If this step is unsuccessful, do the following:
  - Ensure IP routing is enabled.
  - Verify that the IP address of the default gateway is correct.
  - Ensure the remote host is functional
  -Verify that the link between routers is operating.

For detailed instructions to help with various troubleshooting problems, see the following topics, as required:

• Messaging server sites and locations

• Dialing plans

• VPIM Networking connections

• SMTP authentication failures

• Viewing events

• Monitoring alarms

• Collecting report data

• Running reports