TASSTA Documentation Center TASSTA Documentation Center More products
Hide table of contents Hide details Search My account


Most of the latency in communications is network-related, as described in What impedes communications performance. We have the following suggestions for customers who are seeking to alleviate latency issues:

  • Tweak your network topology if possible
    This is not always feasible but can improve performance dramatically.
  • Use buffering for your data
    This is a realistic measure that has the tradeoff of introducing a general predictable delay in your communications.

Network topology revision

Each network is unique, so no concrete actions can be recommended for everyone. Conceptually, analyze your network to find out where the number of intermediate links can be reduced, and make the route as direct as possible under your circumstances. Make sure all the hardware and software on the network nodes that you control is up to the task performance-wise.

If your system combines TASSTA technology and PMR, consider phasing out radio terminals in favor of TASSTA clients running on mobile devices (if the form factor matters, you can go with Android-based radio terminal workalikes). This eliminates an entire compatibility layer from your network, bringing performance benefits, behavior consistency and additional client-side features.


In the TASSTA framework, a jitter buffer is a shared data area where media packets can be collected, stored, and sent for processing in evenly spaced intervals. Jitter, meaning variations in packet arrival time, can occur because of network congestion, timing drift, or route changes. The jitter buffer, which is located at the receiving end of the connection, intentionally delays the arriving packets so that the end user experiences a clear connection with very little sound distortion.

Jitter buffering is configured in T.Commander on a per-server basis. Experiment with the settings to find the optimal configuration for your network.

If your TASSTA deployment is bridged with a PMR system, find out if that system has buffering features analogous to the TASSTA jitter buffer, and configure them if it does.