Manual

93
To turn the encoder o, expand the prole you will be using in the  menu. Under each folder, both 
and , there is a  opon. By selecng this, you can then turn the transmit to O.
We’ll give two examples of mul-streaming scenarios. The rst is an environment where the user that is serving the
mul-stream iniates the calls, and in the second the serving user accepts all its incoming connecons.
In the “mul-streamer as caller” model, two dierent proles will be built on User A. The rst prole, labeled “Mul-
Duplex,” will be dened as a normal, full-duplex connecon. The encoder to be used will be selected in the
secon, and the stream desired in return will be dened in the  secon.
The second prole is called “Mul-Simplex, and in this prole ther is turned . Most other
selecons in this prole are irrelevant.
User A will dene remote connecons for users B, C, and D. He will assign the “Mul-Duplex” prole to User B, and “Mul-
Simplex” prole to the others. He will then establish a connecon with user B rst, followed by C and D.
In model number 2, where the serving user accepts all incoming connecons, all the proles are built on the
. User B will use a simple prole by dening the encoders in each direcon and assigning it to user A.
Users C and D will each dene a prole with their Local Encoders turned o. User B should connect rst. When C and D
connect, they will hear the same stream as B, regardless of how their remote encoders are set in their proles.
In a mul-streaming environment, the rst man wins. For example, the rst connecon made between units will
determine the encoders used for all others. Aer the rst full-duplex connecon is made, all other aempts at full-
duplex connecons to either end will be rejected.