The mechanism for Agent IC, Station IC, LQ IVC and IVC Directs, as well as V-Series IVC connections is based on the same technology and should function in a similar way.

If the same port on the same card with the same credentials can be accessed via another method (such as using an Android or iPhone, connecting via WiFi with a Station IC trial) please skip to Agent IC doesn't connect to an IVC-32 / E-IPA port | The port and network work, but an individual device or connection doesn’t:

Nothing I try allows Agent IC to connect

Check the version number of the IVC-32

Check the port type is correct (Virtual Client) and the user ID and password are set and are longer than three characters, that the configuration has been applied correctly, and that (if externally accessible) the port used for connections is seen as open from the public internet (use a port scanner such asPort Scanner Tool | What Is a Port Scanner? ).

If the ports are open, check firewalls for both TCP and UDP both directions on the same port. To see if a TCP connection is being made, use an invalid username to see if TCP roundtrip is working - it will show Invalid User on the client if TCP is working and then you can be sure that the issue is with the UDP traffic.

Make sure the Event Log is running to see any error messages from the matrix.

The port and network work, but an individual device or connection doesn’t:

As of July 2024, Agent IC does not fully support IPv6 and if the device and underlying network is doing IPv4 to IPv6 translation, errors can happen and packets can be lost.

Recently (2023) it has been discovered that instances when customers choose to use a different port other than 6001, T-Mobile has blocked a port such as port 6002. One work around solution has been to use a VPN on the mobile device.

Or try using a DNS name instead of IP address for the LQ host , see LQ: Accessing LQ via Domain Name using EasyDNS

For additional assistance, please contact Clear-Com Technical Support