Comrex BRIC-Link II, Product Manual

Page: 82 / 104

MULTISTREAMING ARRANGEMENTS
The following includes two examples of Mul stream arrangements involving the BRIC-Link II. In the fi rst
environment, the BRIC-Link II that is serving the Mul stream ini ates calls; and in the second, the serving BRIC-Link
II accepts all of the incoming connec ons. Refer to the diagram in
Figure 70 to be er understand either scenario.
A MULTISTREAMING BRIC LINK II INITIATES THE CALL
In the “Mul streamer as caller” model, two di ff erent pro fi les will be used on Codec A (the mul streamer). The
fi rst pro fi le will be de fi ned as a standard, Duplex BRIC-Link II connec on. A factory pro fi le can be used for this. The
encoder to be used will be selected in the Local Encoder sec on (with Transmit “On”), and the stream desired in
return will be de fi ned in the Remote Encoder sec on (also with Transmit “On”).
The second pro fi le must be built as a Simplex connec on with the Remote Transmi er turned O ff . The user of
Codec A will de fi ne remote connec ons for Codecs B, C, and D. They will assign the Duplex pro fi le to Codec B, and
the Simplex pro fi le to the others. They will then establish a connec on with Codec B fi rst, followed by C and D.
As long as only one connec on is reques ng return audio, Codec A will not show the “Local Busy” message when
adding the second and third connec ons.
A MULTISTREAMING BRIC LINK II RECEIVES THE CALL
In the second model, where the serving BRIC-Link II accepts all incoming connec ons, all the pro fi les are built on
the Remote BRIC-Link IIs (Codecs B, C and D). Codec B will use a Duplex pro fi le by de fi ning the encoders in each
direc on, and assign it to Codec A (this can be a factory pro fi le). Then Codecs C and D will each de fi ne a Simplex
pro fi le with their Local Transmit turned O ff , and assign them to Codec A.
Codec B should connect fi rst. When Codecs C and D connect, they will hear the same stream as Codec B, regardless
of how their Remote Encoders are set in their pro fi les. As long as only one of the codecs is sending audio to Codec
A, they will not receive the “Remote Busy” message when ini a ng the second and third connec ons.
Note: In either scenario, the fi rst connec on made between units in a Mul stream will determine the encoders
used for all other connec ons. Similarly, a er the fi rst full-duplex connec on is made, all other a empts at full-
duplex connec ons to either end will be rejected.
USING CROSSLOCK WITH MULTISTREAM CONNECTIONS
CrossLock func onality brings increased connec on stability in Mul streaming environments. To use CrossLock in
a Mul stream, create the Manual CrossLock Remote entries (refer to page 48 ) and simply apply the appropriate
Simplex pro fi les to each Remote entry as described above.
If BRIC-Link II is using Switchboard (via the purchase of a Switchboard Traversal Server License), the Switchboard-
generated Remote entries will use CrossLock by default, and these entries must simply be edited to use the
appropriate Simplex pro
fi les as described above.