kcarpenter
01-02-2008, 08:41 AM
In WAVE 3.0, Supernode links replace Multiplex Trunks and, to a large degree, Point-To-Point Trunks as well. While Point-To-Point trunks are really just simple point-to-point unicast UDP streams, Multiplex Trunks are essentially “version 0.1” of Supernode links – allowing multiple Point-To-Point Trunks to flow across a single multiplex stream. However, there are significant shortcomings in both trunking mechanisms when compared to Supernode links. These include:
1) Supernode links are inherently more secure providing for authentication, enhanced AES encryption, protection against “man in middle the attacks”, and dynamic corruption detection. Trunks do not provide any of these features except for individual stream-by-stream encryption.
2) Supernode links include support for server failover - allowing for multiple upstream servers to be defined – with automated server priority connections (aka “failback”) supported. Trunks can only exist to a single target machine. If that target is down, the trunk is inoperable.
3) Supernode links can be statically or dynamically established from Media Servers as well as client workstations running WAVE Desktop Communicator, WAVE Dispatch Communicator, or any application developed using the WAVE SDK. Trunks can only exist between two Media Servers.
4) Supernode links can (optionally) automatically transcode and reframe audio. Trunks cannot without manual configuration by an administrator.
5) Supernode links maintain control channel state across the link so that local network control channel heartbeats do not traverse the link (generally a WAN), resulting in greatly reduced WAN traffic. Trunks do not support this feature and therefore consume substantially more WAN bandwidth.
6) Supernode links include support for WAVE Asymmetric Media Tunneling (AMT) which automatically determines the best IP protocol to use for media streaming – TCP or UDP – allowing for firewall bypass, etc. Trunks do not support AMT.
7) Supernode links are very easy to setup using the WAVE 3.0 Management Server Zone management subsystem. Trunks must be manually configured with sessions defined for servers, etc.
While Multiplex Trunks have been replaced by Supernode links in WAVE 3.0, there is certainly still use for Point-To-Point trunks – especially when those trunks are for standard RTP only. For example: some vendors of VoIP applications and equipment support streaming of RTP audio to a unicast address and/or receipt of unicast RTP audio. In such a circumstance, a Point-To-Point WAVE trunk is the perfect solution.
1) Supernode links are inherently more secure providing for authentication, enhanced AES encryption, protection against “man in middle the attacks”, and dynamic corruption detection. Trunks do not provide any of these features except for individual stream-by-stream encryption.
2) Supernode links include support for server failover - allowing for multiple upstream servers to be defined – with automated server priority connections (aka “failback”) supported. Trunks can only exist to a single target machine. If that target is down, the trunk is inoperable.
3) Supernode links can be statically or dynamically established from Media Servers as well as client workstations running WAVE Desktop Communicator, WAVE Dispatch Communicator, or any application developed using the WAVE SDK. Trunks can only exist between two Media Servers.
4) Supernode links can (optionally) automatically transcode and reframe audio. Trunks cannot without manual configuration by an administrator.
5) Supernode links maintain control channel state across the link so that local network control channel heartbeats do not traverse the link (generally a WAN), resulting in greatly reduced WAN traffic. Trunks do not support this feature and therefore consume substantially more WAN bandwidth.
6) Supernode links include support for WAVE Asymmetric Media Tunneling (AMT) which automatically determines the best IP protocol to use for media streaming – TCP or UDP – allowing for firewall bypass, etc. Trunks do not support AMT.
7) Supernode links are very easy to setup using the WAVE 3.0 Management Server Zone management subsystem. Trunks must be manually configured with sessions defined for servers, etc.
While Multiplex Trunks have been replaced by Supernode links in WAVE 3.0, there is certainly still use for Point-To-Point trunks – especially when those trunks are for standard RTP only. For example: some vendors of VoIP applications and equipment support streaming of RTP audio to a unicast address and/or receipt of unicast RTP audio. In such a circumstance, a Point-To-Point WAVE trunk is the perfect solution.