TieLink Traversal Server Support
TieLink Firmware Requirements
TieLink Traversal Server Requirements
To use the TieLink Traversal Server you will need to ensure that your Tieline codecs have at least Firmware v2.20.06 or above installed.
Each Tieline domain has unique administrator login credentials and codecs can be added to a TieServer Domain with TieLink or the TieServer Console. If you already have Report-IT Enterprise or the Cloud Codec Controller, the same domain can be used for TieLink. Following is a diagram showing the relationship between a TieServer Domain and Tieline’s software products; TieLink, the TieServer Console, and the Cloud Codec Controller.
It is critically important to remember that removing a codec from a domain removes it from:
- The TieServer Console: used to manage an organization’s codecs and Report-IT users.
- Report-IT user accounts: users authorized to connect to a particular codec will no longer be able to ‘see’ or connect to a codec after it is removed.
- The Cloud Codec Controller: used to manage an entire fleet of Tieline codecs and Report-IT Enterprise users remotely.
- TieLink Traversal Server: used to configure codec dialing groups and traverse firewalls and NAT more simply.
- In a web-browser navigate to https://tieserver.com/tielink and enter the TieLink Administrator credentials supplied by Tieline. Note: If you already have a TieServer domain, the same default administrator credentials for the Cloud Codec Controller and TieServer Console will automatically allow you to log in and access TieLink services.
- Click the Lost your password link to reset the administrator password.
If TieLink Does Not Connect:
- Ensure TieLink and at least one relevant interface is enabled and ‘stunned’ on both codecs; i.e. the STUN Status for the interface is Connected.
- Check STUN server settings.
If a TieLink Fuse-IP Connection Does Not Connect:
- Ensure Fuse-IP is enabled in the TieLink panel in Toolbox, or in the codec’s TieLink Settings screen, for both the dialing and answering codecs
- Check at least one interface has been added to the Fuse-IP configuration in the TieLink panel in Toolbox, or in the codec’s TieLink Settings screen, for both the dialing and answering codecs
- Verify that the STUN Status for at least one interface in the Fuse-IP configuration is Connected on both the answering and dialing codecs.
- Check that the answering codec is not already connected using TieLink Fuse-IP. Only one Fuse-IP connection is currently supported.
If SmartStream PLUS Connections do not connect:
- Based on the priority order of interfaces in the TieLink panel, a SmartStream PLUS connection may automatically use TieLink Fuse-IP as one of the connections if Fuse-IP is enabled at the dialing or answering codec. If TieLink Fuse-IP is chosen, then that connection will only succeed if the Fuse-IP stream is available at both ends. Disable Fuse-IP as an interface in TieLink to avoid Fuse-IP being selected in this scenario.
- When “Discrete once only” or “Discrete recurring” is selected, with TieLink Fuse-IP enabled, TieLink Fuse-IP may be selected to transmit one of the streams. In this situation, if the answering codec is already connected to another codec using TieLink Fuse-IP, then the connection will fail for this stream because only one Fuse-IP connection is supported using TieLink.
- When “First Available” is selected, TieLink Fuse-IP may be used if it is the first interface “ready” in the TieLink panel interface list. In this situation, the connection will fail if the answering codec is already connected to another codec using TieLink Fuse-IP.
Configuration Restrictions for TieLink
TieLink only supports one SmartStream PLUS redundant streaming connection on each audio stream. TieLink also does not support uncompressed PCM connections, or encoding using aptX Enhanced, G.711 or G.722.
By default TieLink is disabled in a codec and needs to be enabled before it is ‘available’ in the Traversal Server. To enable this on a codec using the ToolBox Web-GUI:
- Open the HTML5 Toolbox Web-GUI and click Transport in the Menu Bar, then click TieLink to open the TieLink panel.
- Click Edit and ensure Enable TieLink is On, then click to select On/Off buttons and enable required interfaces.
- Click Save.
When an audio stream is Offline it is unavailable within the TieLink Traversal Server Network. Possible reasons an audio stream may be offline include:
- The codec is offline.
- An audio stream is not advertised on TieLink.
- TieLink and/or TieLink interfaces are disabled in the codec.
Ports are not open.
- The Contact List panel in the Toolbox Web-GUI may need ‘refreshing’.
DNS – Not resolving the STUN server set in the TieLink panel. Note: If a codec has a statically configured IP address, ensure that DNS Server settings are also configured.
- DNS – Not resolving https://tieserver.com
- The codec firmware version is not compatible.
The default ports for TieLink connections are UDP ports 5100 – 5120. Most of the time Telcos will not block these ports, but it is possible they may in some regions. Ensure that any LAN or cellular network being used allows UDP traffic on these ports, or if the default ports are changed, the ports which have been configured for use.
When you reset factory defaults in a codec TieLink is disabled. This can be re-enabled using the codec front panel or the Toolbox HTML Web-GUI connected to a codec. See the codec user manual for more details.
First, verify the NAT Type on each codec for the interface/s being used for the connection. This is displayed in the TieLink panel in the Toolbox HTML Web-GUI for each codec. Some combinations of Symmetric and port restricted NATs may not be traversable. If this is the case, Tieline recommends connecting in a more traditional peer-to-peer manner using port forwarding techniques.
If Stream Members have been removed from a contact list, it is necessary to deselect the Members check-box for a codec and then reselect it to add all stream members back.
If a codec is shared with an external TieLink domain, and streams have been deselected, it is necessary to Remove the codec and then share it with the external TieLink domain again to re-enable all audio streams.
When you load a multistream answering program enabled for Tielink connections it must be locked in the codec so it cannot be unloaded by the first incoming call. TieLink may only show one available answering stream if a multistream program is not locked in the codec.To lock a program in the answering codec:
- Open the HTML5 Toolbox Web-GUI and click Settings at the top of the screen, then click Options to display the Options panel.
- Select System and click Edit.
- Click the Lock Loaded User Program check-box to lock or unlock a user program in the codec, then click Save.