TesiraFORTÉ X will not relay a command string from the control port P1 through to P2-5; it does not function as a
control tunnel. TesiraFORTÉ X's control and media IP addresses must be in unique logical subnets or the device will not
function properly.
TesiraFORTÉ X uses the same TTP commands as all other Tesira hardware so control libraries remain
unchanged. TesiraFORTÉ X uses SSH by default, telnet may be enabled if desired.
Launch-configured devices do not support the use of TTP commands by 3rd party control systems.
One behavior unique to TesiraFORTÉ X is the VoIP X interface which now hosts 2 call instances rather than 6 as seen
in other Tesira devices. The TTP commands are unchanged, the difference is that the control system will never see a
call appearance on call instances 3, 4, 5 or 6. In practice we have found 6 call instances to be unwieldy for most
installations and 2 call instances mirrors the behavior of many phones, making it more intuitive for the everyday user.
Larger Forte X system considerations
TesiraFORTÉ X is similar to other Tesira AVB DSP devices but adds the new consideration of a built in AVB media
switch. The TesiraFORTÉ X, TC-5 and TC-5D network devices are designed for small to medium scale applications.
They are not a universal tool. Some applications require a high stream count and should leverage the power of
enterprise grade AVB switches and the Tesira Server-IO AVB or TesiraFORTÉ AVB endpoints which do not incorporate
a lightweight internal AVB switch.
A maximum of (3) TC-5 has been recommended with one TesiraFORTÉ X to ensure that stream counts and hop limits
are observed, with enterprise grade switches advised for larger systems. In larger systems with multiple
TesiraFORTÉ X, the additional TesiraFORTÉ X should be considered equivalent to TC-5 when considering network
device counts in the design.
While deployments exceeding this recommendation may work, the cost per port typically tips in favor of the enterprise
switch in this device count range. Additionally, on networks with more than the recommended number of units, users will
need to consider the position of each device in the network topology when applying firmware updates to ensure all
devices can receive the update without being blocked by a mid-span device updating simultaneously. This scenario may
require manually selecting a sub-set of devices for their firmware update, then manually selecting a second group once
the first has completed their updates.
• The Control ports (P1) of each TesiraFORTÉ X need to be on a common control network. (FW 4.0 and 4.1)
• The AVB ports (P2-P5) of the TesiraFORTÉ X need to be on a common AVB network to share media. (FW 4.0 and
4.1)
• The Tesira system limit of 128 devices needs to be observed as defined in the Tesira help files.
• TesiraFORTÉ X and/or TC-5 can be daisy-chained and will pass AVB and Dante to connected devices.
• The limit of 9 hops between the farthest 2 AVB endpoints in a system should be respected. A hop is counted as the
link between 2 AVB-capable network components.
• The TC-5 and TesiraFORTÉ X are expected to support up to 150 streams on the AVB network. Systems need to be
designed with this maximum stream count in mind. If more streams are needed enterprise grade switches and
Server-IO or Forte AVB (dedicated AVB endpoints) are recommended. The number of AVB endpoints on a network
https://support.biamp.com/Tesira/Miscellaneous/TesiraFORTE_X
Updated: Thu, 01 Dec 2022 17:48:44 GMT
Powered by
16
To Next Page
Loading...
