Comrex BRIC-Link - Page 51

If the primary remote is restored and BRIC-Link can detect a valid signal, it will automacally disconnect the backup
and revert back to the primary remote. To enable , click the “” opon in the 
prompt and select Yes ().

Once the remote connecon entry is completed in the Connecons Tab, highlight the remote and select Connect.
When a connecon is aempted, the State column in the connecon table will change to reect the progress of
the connecon (). If the connecon fails, the reason for the connecon failure will be shown in the State
column. When the remote connecon succeeds, the encoder and decoder mode will be reected in the Rx Status/
Tx Status column. To end a connecon, highlight the remote and select Disconnect.


Manual CrossLock connecons require special conguraon opons on both sides of the link. This primarily
involves programming the Switchboard ID for each unit (or primary Ethernet MAC address) into the outgoing
sengs on the codec on the opposite side of the link. This process for outgoing calls is described above. What isn’t
menoned is also important: the MAC/Switchboard ID of the outgoing unit must also be programmed into the unit
receiving the call.
Note that if connecng to an ACCESS MulRack, instances #2-5 have special Switchboard IDs consisng of the
primary Ethernet MAC followed by a “-x” sux (e.g. 00:01:0c:c0:78:19-4 for instance #4).
This is done by creang an outgoing connecon describing the far-end unit, even if it is never actually used for
outgoing calls. In the case of this “dummy” entry, it’s not actually important for the IP address eld of the far-end
unit to be correct. The entry must be enabled for CrossLock operaon and it must have the correct Switchboard ID/
MAC address of the far-end unit.
In the special circumstance where the default CrossLock port of UDP 9001 can not be used (e.g. several BRIC-Link
codecs sharing a single IP address), then manual CrossLock connecons get extra complex. For more informaon on
these sengs, refer to the Technote “Making CrossLock Connecons on Non-standard Ports”.
51