VoIP

From TCBWiki

All of the TCB (Tactical Communications Bridge) products with network interfaces support VoIP (Voice over IP). The TCB2, TCB3 Family, and TCB4 Family can all exchange VoIP traffic with a computer running RCI (the included Remote Control Interface software) or with each other (using VoIP as a link between TCB units). They are limited to a single VoIP stream, though it can be sent to up to four destinations.

The TCB-IP2 and MSAT-IP also support VoIP communications with RCI, and additionally support unlimited VoIP connections with computers running the LinkTDS dispatch software and multiple links to other units.

For more information, see the following:

• To set up VoIP between a computer running RCI and a TCB, see RCI, VoIP and Firewalls.
• To set up a VoIP link between TCB units, see one of the following:
  • For the TCB2, TCB3 or TCB4 units, see How do I use VoIP to link two TCBs?.
  • For the IP2 and MSAT-IP, see Linking gateways using VoIP.
• The IP2 and MSAT-IP VoIP settings can be adjusted to at least partially compensate for imperfect network connections. See VoIP and Imperfect Networks.
• The IP2 and MSAT-IP can communicate via VoIP through the Internet without manual configuration using the VTrunk cloud-based service.. See Using VTrunk.
• The IP2 and MSAT-IP support two SIP (VoIP) connections per unit. See Configuring SIP.
• The IP2 and MSAT-IP can communicate among themselves and with LinkTDS using IP Multicast. See Multicast Addressing.
• The IP2 and MSAT-IP by default cannot generate tones on the virtual ports used for VoIP links, though they will pass any pass any audio including tones. To change that, see Tone Generation on Virtual Ports.
• The MSAT-IP can be used to "remote" the G2's handset over an IP network. See MSAT-IP Remote Handset.
• The LinkTDS software has a "virtual" handset that can be used to communicate over a G2 radio. See MSAT-IP Virtual Handset using LinkTDS.
• The LinkTDS software is sometimes prevented from working correctly by the Windows(tm) firewall. If causing a widget to transmit allows it to receive for a few seconds, this is likely the cause. See LinkTDS and the Windows Firewall.