USB interface break-out-box for CONVERGE family products using USB audio. Provides USB audio In/Out between desktops/laptops and CONVERGE units; Plug-and-play peripheral connects desktops/laptops with professional audio for ClearOne COLLABORATE ® Desktop and other popular UC applications such as Skype ™, Microsoft ® Lync ®, and Google Talk.
CONVERGE 速 USB Now Shipping! The CONVERGE USB peripheral provides plug-and-play USB connectivity between popular desktop and laptop UC applications and CONVERGE Pro for full, rich, professional sound — without any firmware or software upgrades. Features:. Provides USB audio In/Out between desktops/laptops and CONVERGE units.
Plug-and-play peripheral connects desktops/laptops with professional audio for ClearOne COLLABORATE ® Desktop and other popular UC applications such as Skype ™, Microsoft ®Lync ®, and Google Talk ™. Easily connects with ClearOne COLLABORATE Room video conferencing system for best-in-class audio. Used as Expansion bus extender by extending the distance to another 200 feet per unit, by using expansion bus (G-Link) In & Out ports. Connects to CONVERGE units through G-link expansion bus. CONVERGE Pro units require version 4.0 and above firmware and software.
Works with all existing CONVERGE Pro and SR products. Powered through external power supply. GPIO pin controls the expansion bus selection.
Volume controlled through desktop/laptop WARRANTY: 2 years, From date of purchase.
I have had a sucession of problems connecting my computer to ConvergePro products in the field. Some of these problems are of my own doing, but I would like to mention some problems that could be avoided in the future if the documentation that ClearOne provides could be made clearer: 1. No 64-Bit Support: Yes, I know (NOW!) that you mention it in your Tech Note 'Converge Pro, Converge Console, and Firmware Version & Compatibility', but it's not in the main documentation for the CP products, and this lack of support doesn't manifest itself until the tech is in the field, trying to connect to a CP device. Converge Console 2.0.30 software will INSTALL on a 64-bit machine without any warnings, and someone who doesn't know to look in that Tech Note will be in for a rude surprise come commissioning time, when all he's got with him is his 64-bit machine. Issues with connecting to a site: The instructions for setting the computer's IP settings need to be made a lot clearer than they are in the Converge Pro documentation. Knowing in advance that the computer's IP address, Subnet mask and Default Gateway must be manually set to match the range of the CP product would save a lot of time and calls to C1 support, as would knowing that the Windows Firewall on the host computer must be turned off. I have tried to locate this information in the CP documentation, but the closest I can come it is a reference on page 53 to see 'Unit Communication (IP) Settings' elsewhere in the manual.
I did a search on that term in the.pdf version of the CP documentation, and the only time that phrase comes up is right there, on page 53. Port 23: After making all IP settings and turning off Windows Firewall, I still can't connect to a CP device, apparently because something in my computer is blocking 'Port 23'. If I knew what Port 23 was, I would do my best to un-block it, but right now, I've got nothing to go on. We're A/V guys, not IT guys. Time is money, and time in the field is worth a LOT of money.
Sometimes, it's difference between profitablitability or not on a project. With respect, guys, I know YOU know this stuff, but please make it easier for those of us who have to deal with issues other than internet protocol for a living. While I am aware of the 64 bit issue and have mentioned it here before, I have never had an issue connecting via IP to a clearone converge.
I had problems with the old XAP net. Having to turn off firewall seems very strange I have never had to do that. I recommend a 100' cat5 crossover cable so no you can do a direct connect from the laptop to the converge. Then just setting static IP on the clearone and your laptop will make your life much easier. quote='patriquem'I have had a sucession of problems connecting my computer to ConvergePro products in the field. Some of these problems are of my own doing, but I would like to mention some problems that could be avoided in the future if the documentation that ClearOne provides could be made clearer: 1. No 64-Bit Support: Yes, I know (NOW!) that you mention it in your Tech Note 'Converge Pro, Converge Console, and Firmware Version & Compatibility', but it's not in the main documentation for the CP products, and this lack of support doesn't manifest itself until the tech is in the field, trying to connect to a CP device.
Converge Console 2.0.30 software will INSTALL on a 64-bit machine without any warnings, and someone who doesn't know to look in that Tech Note will be in for a rude surprise come commissioning time, when all he's got with him is his 64-bit machine. Issues with connecting to a site: The instructions for setting the computer's IP settings need to be made a lot clearer than they are in the Converge Pro documentation. Knowing in advance that the computer's IP address, Subnet mask and Default Gateway must be manually set to match the range of the CP product would save a lot of time and calls to C1 support, as would knowing that the Windows Firewall on the host computer must be turned off. I have tried to locate this information in the CP documentation, but the closest I can come it is a reference on page 53 to see 'Unit Communication (IP) Settings' elsewhere in the manual. I did a search on that term in the.pdf version of the CP documentation, and the only time that phrase comes up is right there, on page 53. Port 23: After making all IP settings and turning off Windows Firewall, I still can't connect to a CP device, apparently because something in my computer is blocking 'Port 23'.
If I knew what Port 23 was, I would do my best to un-block it, but right now, I've got nothing to go on. We're A/V guys, not IT guys.
Time is money, and time in the field is worth a LOT of money. Sometimes, it's difference between profitablitability or not on a project. With respect, guys, I know YOU know this stuff, but please make it easier for those of us who have to deal with issues other than internet protocol for a living.
Hi Pat, Sorry to hear you've had a 'perfect storm' of issues. I can shed some light on the USB/Firewall connection. The USB driver used to connect to the Converge Pro is actually considered a network interface by the O.S. Creative labs ct4750 driver download windows 7.
There is even a DHCP assignment done in the back ground. If you perform an 'IPconfig' while connected to a CP, you'll see the connection just as you would see your LAN. If you open telnet to one number greater than the CP's IP you have a USB telnet connection! As video suggested, a cross-over cable is great to have in the bag. Also, I travel with a small Linksys WAP/router. This allows me to plug into any CP, assign a DHCP and connect wirelessly. I'll talk to our Apps guys regarding the 64 bit surprise, that is great info and we should have an error message for that situation.