IP-Concert: My IT department changed our network switches and our Concert Clients no longer connect
Question: Recently IT updated some of our network switches, and after the update computers on our house LAN are unable to access the Concert server. I was wondering if you could point me in the right direction to get these computers access to the intercom. Are there certain ports that need to be forwarded to the Concert server? Any help would be greatly appreciated.
Answer: If the issue is not being able to log in to Concert client users to the system while internally on the same network check the following:
• Open the Concert client and try to log in. If the log in fails click on the “Config” pull down menu and select “Server”
• In the server screen confirm that the IP address is correct
• Click on the “Advanced” button and check that the port setting is correct
Is the concert server IP setting the same IP address range / subnet?
If not you may have to ask your IP people if they have blocked access to this address or if it is going thru a router and getting its address dynamically changed and or if the port is being blocked.
If the clients were working prior to IT installing their changes then it’s likely they didn’t preserve some of the settings that Concert needs to see. Check with your IT department to confirm that ports for concert are open. These ports should be open in order for Concert to work:
Concert Network Configuration
EMS
The EMS receives Client Login requests on TCP port 6001, and IV-R connection request over UDP port 4569.
To enable client login from outside the fiewall, the firewall must be configure to redirect the TCP public address port 6001 to the EMS internal address TCP port 6001. For instance, if the EMS address is 192.168.0.1 and the public address is 208.17.183.164, than the firewall would need to forward TCP 208.17.183.164:6001 to 192.168.0.1:6001. All clients login will use the same port.
To enable remote IV-R connection to the EMS from outside the fiewall, the firewall must be configure to redirect the UDP public address port 4569 to the EMS internal address UDP port 4569. For instance, if the EMS address is 192.168.0.1 and the public address is 208.17.183.164, than the firewall would need to forward UDP 208.17.183.164:4569 to 192.168.0.1:4569. All remote IV-Rs will use the same port.
Answer: If the issue is not being able to log in to Concert client users to the system while internally on the same network check the following:
• Open the Concert client and try to log in. If the log in fails click on the “Config” pull down menu and select “Server”
• In the server screen confirm that the IP address is correct
• Click on the “Advanced” button and check that the port setting is correct
Is the concert server IP setting the same IP address range / subnet?
If not you may have to ask your IP people if they have blocked access to this address or if it is going thru a router and getting its address dynamically changed and or if the port is being blocked.
If the clients were working prior to IT installing their changes then it’s likely they didn’t preserve some of the settings that Concert needs to see. Check with your IT department to confirm that ports for concert are open. These ports should be open in order for Concert to work:
Concert Network Configuration
EMS
The EMS receives Client Login requests on TCP port 6001, and IV-R connection request over UDP port 4569.
To enable client login from outside the fiewall, the firewall must be configure to redirect the TCP public address port 6001 to the EMS internal address TCP port 6001. For instance, if the EMS address is 192.168.0.1 and the public address is 208.17.183.164, than the firewall would need to forward TCP 208.17.183.164:6001 to 192.168.0.1:6001. All clients login will use the same port.
To enable remote IV-R connection to the EMS from outside the fiewall, the firewall must be configure to redirect the UDP public address port 4569 to the EMS internal address UDP port 4569. For instance, if the EMS address is 192.168.0.1 and the public address is 208.17.183.164, than the firewall would need to forward UDP 208.17.183.164:4569 to 192.168.0.1:4569. All remote IV-Rs will use the same port.
CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT
This solution was provided to you by Clear-Com via a question submitted to us by customers like you. If your question wasn’t answered, you need help or you have a recommended solution for our database, please send us an email at support@clearcom.com
The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.