Product Manual
BRIC-Link II Manual I. Introduction 11 Applications 11 Audio Coding 11 Transmission Modes and Delay 11 Switchboard Server 12 CrossLock 12 Additional Features 12 HTML5 12 II. Diagrams and Installation 13 Rear Panel Diagram and Descriptions 13 Front Panel Diagram and Descriptions 14 Mono vs. Stereo 14 Pinouts - Balanced Audio 14 Pinouts - AES3 15 Pinouts - Serial Port 16 Pinouts - Contact Closures 16 DIP Switch Settings 17 Reset to Factory Default 17 Iii.
More About Profiles 18 Using the Console 18 Making Switchboard Connections 19 Receiving Incoming Connections 19 iV. Using The Device Manager Program 20 Updating Firmware Using Device Manager 22 Network Recovery Mode 23 V.
Profile Settings: Local & Remote Encoders 32 Advanced Local & Remote Options 33 System Settings Tab 35 Security Settings 36 Connections 36 Contact Closures 36 Switchboard Server 36 CrossLock VPN Settings 37 System Clock 37 Alternate Modes 37 Advanced System Settings 38 Security 38 Auxiliary Serial 38 CrossLock VPN Settings 39 BRIC Normal Settings 39 HTTP Settings 40 Standard RTP Settings 40 EBU3326/SIP Settings 40 TCP Settings 41 Miscellaneous 42 Vi.
Ethernet Port Settings 43 Network Locations 44 3G/4G Connections 45 Advanced Ethernet Port Settings 46 ViIi. Making CrossLock Connections On BRIC-Link II 47 How CrossLock Works: A Brief Overview Multiple Network Setup CrossLock Connections to MultiRack 47 48 49 VIII. Making Connections Via Switchboard 50 IX. Making Manual Connections 52 Creating New Remotes 52 Backup Remote 53 Connecting and Disconnecting 54 Special Notes for Manual CrossLock Connections 54 X.
Shares 58 Managing Multiple Contact Lists 59 Bulk Actions for Contact Lists 61 Switchboard Theory and Concepts 64 XI. Operating BRIC-Link II In A 24/7 Environment 68 Always Connect To 68 Backup Remote 69 XiI. About The Algorithms 71 AAC 71 HE-AAC 71 HE-AACv2 71 Linear PCM* 71 FLAC* 72 G.722 72 Opus 72 Algorithm Codec Profiles Chart 73 XIII.
Using CrossLock with Multistream Connections XIV. IP Multicast 75 76 Multicast Profiles 76 Setting Up a Multicast Remote 77 Time-To-Live 77 Changing Port Numbers for Multicast 77 Xv. Streaming Server Function 78 Decoding A Stream 79 Simultaneously Connecting BRIC-Link IIs And Streaming 79 XVI.
SIP Troubleshooting 84 Outgoing Call Issues 84 Incoming Call Issues 84 Solutions 84 Stunning Success 85 Fix of Last Resort 85 XVII. License & Warranty Disclosures for BRIC-Link II 86 License 86 Warranty 87 XVIII. Switchboard Traversal Server Disclaimer Traversal Server Disclaimer 89 89 XIX.
APPENDIX C: Unidirectional Networks 99 Standard RTP Settings 99 Decode Side Settings Only 99 Encode Side Settings Only 99 Full-Time Or Triggered Connections 99 APPENDIX D: Information For IT Managers 100 Incoming Services 100 Outgoing Services 100 APPENDIX E: Connections To MultiRack 101 BRIC Normal Connections 101 Manual CrossLock Connections 101 Making Connections With Switchboard 102
ABOUT COMREX Comrex has been building reliable, high-quality broadcast equipment since 1961. Our products are used daily in every part of the world by networks, stations and program producers. Every product we manufacture has been carefully designed to function flawlessly, under the harshest conditions, over many years of use. Each unit we ship has been individually and thoroughly tested. Comrex stands behind its products.
I. INTRODUCTION The Comrex BRIC-Link II is a low-cost, high-performance solution for audio-to-IP conversion. Leveraging many of the core technical aspects of Comrex’s successful remote broadcast BRIC-Link product line, the BRIC-Link II provides for an elegant way of moving Linear or compressed audio with very low delay. BRIC-Link II may be used over a range of IP links, is very simple to use, and doesn’t require the expense of more full-featured codecs.
Switchboard Server Switchboard is a standard feature with BRIC-Link II that allows the codec to “sync” with Comrex’s cloud-based traversal server. Switchboard facilitates connections between codecs without any knowledge of IP addresses on either end of a link. Switchboard traversal server allows for monitoring presence and status information for all Comrex codecs in a user’s fleet, and assists with connections through routers and firewalls that might be difficult otherwise.
II. BRIC-Link II Diagrams and Installation 10 9 CARD L /AES3 1 INPUTS R L /AES3 R 2 3 4 OUTPUTS 5 CC SERIAL POWER 6 7 8 Figure 1 Rear Panel Diagram and Descriptions 1 Left Audio/AES3 Input - Accepts professional level, balanced analog audio, or if configured, AES3 stereo digital audio for input. 2 Right Audio Input - Accepts professional level, balanced analog audio.
L R READY RESET AUDIO LEVEL 11 12 13 14 15 16 17 Figure 2 Front Panel Diagram and Descriptions 11 Headphone Jack - 3.5 mm TRS output to monitor input audio or decoded audio (selectable via dip switch). 12 Headphone Level Control - Allows adjustment (Up/Down) of headphone output. 13 DIP Switches - 8 individual DIP switches allow selection of certain operational parameters (see DIP Switch Settings on page 17). 14 Left/Mono I/O Level Indicator - Tri-color LED shows left channel input or output level.
Pinouts - AES3 A nominal input level of 0 dBu (2.2 Vpp) is recommended. When configured via the DIP switches, the left input and output become AES3 digital ports. The jacks connectors are wired as follows: 1 Ground 2 AES3 + 3 AES3 - To use AES3, the front panel DIP switches must be set appropriately. AES3 input connections can be at 32, 44.1 or 48 kHz. The front panel DIP switches must be set appropriately. On the BRIC-Link II, the output audio sample rate automatically locks to the input sampling rate.
Pinouts - Serial Port The Serial Port is pinned to match serial connections on older Macintosh computers, so commercially available adapter cables should have the proper pinning. Pin # Function Direction 3 TX Data From BRIC-Link II 4 Ground 5 RX Data 1 2 To BRIC-Link II 6 7 8 Ground Pinouts - Contact Closures Contact closures are available via the 9-pin mini-DIN connector on the rear panel of the BRIC-Link II. Inputs are triggered by shorting the respective input to Pin 9.
DIP Switch Settings BRIC-Link II has a set of eight DIP switches used for audio and indicator configuration.
iii. QUICK START - MAKING CONNECTIONS WITH BRIC-LINK II This section skips over many of the details concerning the configuration of remote connections with BRIC-Link II, and focuses instead on the minimum information needed to establish a connection. BRIC-Link II connections with the use of the Switchboard server will be covered. MORE ABOUT PROFILES Refer to Page 31 for more information about creating profiles on BRIC-Link II.
a Green Gear icon are available for Switchboard connections. Highlight them and select the “Connect” button on the right side of the screen to initiate a connection. FIGURE 4 SWITCHBOARD CONNECTIONS ICONS RECEIVING INCOMING CONNECTIONS By default, BRIC-Link II is set to automatically answer incoming calls, whether or not Switchboard is used to make them. Incoming calls will appear in your connections list while they are active.
iV. USING THE DEVICE MANAGER PROGRAM Firmware updates for the BRIC-Link II should be handled using Comrex Device Manager, a Windows- and MAC OS-executable program that can be downloaded from the Comrex website. Device Manager can also be used for license installation and IP configuration. Please note: In order to configure a BRIC-Link II unit for the first time (without knowing the unit’s IP address), Device Manager must be run on a computer located on the same network (e.g.
Figure 7 Set up Ethernet And Wireless Generally, it is recommended to configure the Ethernet port of an BRIC-Link II for a static IP. This will facilitate access to the Web-based Interface with a browser and allow for easier configuration of routers or firewalls (if necessary). If the BRIC-Link II is to be installed on a managed LAN, Comrex recommends consulting with the IT services provider about obtaining a static IP address.
Figure 8 Network COnfiguration UPDATING FIRMWARE USING DEVICE MANAGER While Device Manager is open and synced to a codec, it’s a good time to check to see if an update is available for the product. To do this, select the Firmware tab, shown in Figure 9 below. The unit’s current firmware and the most recent version of firmware for the unit are listed at the top of the tab (1 in Figure 9).
1 2 3 Figure 9 Firmware tab NETWORK RECOVERY MODE Since the Ethernet settings are made with a web connection, keying in incorrect static IP information can result in losing access to the Network Manager interface entirely. If this happens, it is possible to be “locked out” of the unit (i.e., unable to log in). Device Manager has a network recovery tool to help with this: Network Recovery Mode.
Figure 10 network recovery mode 24
V. CONFIGURING THE BRIC-LINK II LOGIN Upon connection to the BRIC-Link II, a login screen will appear, Figure 11. Any username can be chosen and used with the default password: comrex. This will access the Main User Interface display. Figure 11 web interface Login INTERFACE PAGE SECTIONS There are two parts to the primary interface screen (Figure 12): • • Main Audio Meter (1): This meter displays audio levels for active connections to the BRIC-Link II.
CONNECTIONS TAB The Connections Tab is the first window in the configuration interface. This allows for monitoring device connectivity and controlling connections. In this tab the names and IP addresses of remote units can be saved. To add a new remote unit to the list, select the “+” icon on the right side of the list. A dialogue box will appear, asking for a name for the unit as well as its IP address. An algorithmic profile must be selected for the new codec unit.
1 2 4 3 5 Figure 13 Dashboard Tab 1. The audio level meters give a quick indication of send and receive levels. 2. The Contact Closure section gives a visual indication of the state of each input (local) and output closure (remote). The input closure boxes also function as buttons to trigger closures locally. 3. The Active Connections section gives an indication of any currently active connections. If more than one connection is active, they will display in a list here. 4.
Figure 15 jitter/packet error graph The left graph represents the work of the Jitter Buffer Manager. The area of most interest is the light blue area as shown in Figure 15, which illustrates a spread of jitter values (referenced to the current play out pointer) over the last second. If this area covers a large span, the relative jitter is high. If the light blue section of the graph is small or invisible over a time period, less jitter is present.
The CrossLock Stats are similar to the information available on the Active Connections graph, which shows streaming performance without regard to the CrossLock layer. The CrossLock Stats show finer details about network performance in both directions than can be obtained through the Active Connections graph. CrossLock stats are shown for both the data being transmitted from the local codec and the data being received by the local codec. All relevant stats are available for both directions.
CROSSLOCK SETTINGS Clicking the CrossLock Settings field during an active connection will display the CrossLock sliders. There is a slider available for transmit and receive operation. For most CrossLock connections, the sliders should be left at their default Automatic Delay Mode settings. But during connections on unusual networks, these sliders are designed to quickly adjust the current delay settings. The sliders will reset when a CrossLock connection ends.
provide stability. These “zones” scale, increase and decrease in size based on the history of jitter experienced by CrossLock on the network. In “Auto Delay” mode, the dark dot signifies the “Current Delay”, which is the best compromise value calculated by the system to balance stability and delay. By changing the “Automatic Delay Mode” switch to manual, the “Target Delay” indicator can be dragged left or right to override the automatic settings, and increase or decrease the delay.
BUILDING A PROFILE To build a new profile, select Add New Profile (1 in Figure 22), and a new profile will appear on the list labelled New Profile. Select it to populate a set of options, starting with the profile Name (2 in Figure 22). Here, the profile can be renamed to something easier to remember. Next is the Channel option (3 in Figure 22), which allows for selecting between a standard Comrex IP connection (BRIC normal) or one of the other connection modes offered by BRIC-Link II.
Encoder - It is unnecessary to define any decoder types when using Comrex codecs because they automatically adapt to the incoming stream. Using this menu, users can select the encoder used to send audio from this BRIC-Link II (local) as well as the encoder used to send audio to this BRIC-Link II (remote). The default value of the remote encoder is to follow the local encoder (i.e., it will send exactly the same codec mode it receives). This is defined as Follow Mode in the remote encoder selection table.
buffer size to compensate. Fixed Delay - This option simply sets the Delay Cushion and Delay Limit at a similar value, so that the delay buffer is defined to the chosen value and will not increase or decrease significantly. Delay Cushion - The jitter buffer manager works to keep absolute delay to a minimum. Some applications are not delay sensitive and rely less on the jitter buffer manager. The Delay Cushion setting is a way to instruct the manager not to attempt to drive the delay below a certain value.
automatically and with no audio interruption. Step down congestion avoidance is not enabled in the Linear PCM mode. UDP Reliability - UDP, the Internet protocol used by BRIC Normal connections, does not have any inherent error correction capability. UDP Reliability adds an intelligent algorithm that requests packet resends when appropriate above the base UDP level. This UDP Reliability is useful on some wireless connections that have unsatisfactory performance due to packet loss.
SECURITY SETTINGS Remote Control Password - This allows for a defined password for the web GUI and firmware updates. The default password is comrex (lowercase). CONNECTIONS Unit Name - Users are encouraged to name their codecs here. The default name of a codec is the unique Switchboard ID (MAC address) of the unit. By changing this to something familiar and unique (e.g., “Roving reporter”, “Weather guy:, etc.), you will see this name reflected in several places: 1.
Switchboard Address - IP address of the Switchboard server. Secure - Enables secure connections to Switchboard Server. This is enabled by default. Static Crosslock Peers - When using CrossLock without Switchboard, remote peers can be managed in this list. CROSSLOCK VPN Enable - This option enables the Crosslock VPN added reliability layer to connect to remote units. (See Making BRIC-Link II Connections Using Crosslock on Page 48 for more information on using the Crosslock VPN.
• • • • • Incoming Connection Profile - This allows users to select whether SIP calls will take place using a specific encoding algorithm. Note: If this option is chosen, only calls using the selected algorithm are allowed. Default is “None”. Use SIP Proxy - This option determines whether the SIP function is “registered” to a SIP cloud server. If this setting is enabled, then the address, user name, and password for the proxy must be added in the relevant fields.
CROSSLOCK VPN UDP Port - Sets the UDP port used for Crosslock VPN Connections. Default is set to UDP 9001. Permissive - Allows users to accept Crosslock connections from any unit. This is set to No by default. Authentication - Enables the authentication of connections. Default setting is No. Protection - Enables AES encryption and payload integrity protection to prevent tampering with or interception of the transmitted content. This option has a SIGNIFICANT system overhead. Default setting is No.
HTTP Accept Incoming Connections - Users can set BRIC-Link II to listen for and automatically answer any HTTP incoming calls. This option is set to No by default. IP Port - This option defines the incoming UDP port—the number to be used for incoming HTTP connections. The default is TCP 8000. Encoder - This defines the encoder used for HTTP streaming. Default is HE-AAC V2 Stereo 48 kB. User Agent Blacklist - List of SIP user agents that are not allowed to communicate.
User Agent Whitelist - List of SIP user agents that are allowed to communicate. Only SIP agents on this list can communicate with the BRIC-Link II. Note: This setting is not enabled when using a registered SIP proxy. User Agent Blacklist - List of SIP user agents that are not allowed to communicate. VIP QC Password - For legacy purposes with the VIP QC app, which has been deprecated. RTP IP Port - The port used for audio transfer during EBU3326/SIP mode.
Note: Warnings given above about changing port numbers also apply here—calls with mismatched port numbers will fail. MISCELLANEOUS Meter Demo Mode - This setting will put the front panel LED meters into a demonstration mode. This setting is set to No by default.
VI. NETWORK MANAGER NETWORK MANAGER Located in the three-line “hamburger menu” in the upper left hand side of the Web Based Interface, the Network Manager allows configuration to the network settings for BRIC-Link II. Selecting Network Manager will bring up the screen shown in Figure 24. The available networking connections from BRIC-Link II are presented on the left hand side of the screen in the Select Network Device section.
Figure 25 ethernet port default settings For users who wish to have a Static IP address for their units, this can be configured by editing the settings for the “Default” Active Network Location. First, select to expand the Default settings under Network Locations. Select IP Type to open a drop down selection screen. This will give users the option to change the “Default” Network Location to Static IP, DHCP, or Gateway IP types as shown in Figure 26.
Figure 27 ethernet port default settings Once a Network Location has been added, it can be easily implemented through the Active Network Location selection in the Adjust Device Settings. 3G/4G CONNECTIONS 4G Cellular connections can be made with BRIC-Link II by attaching a cellular modem with SIM over USB connection. Cellular based modems will appear as their model name. 4G connections generally populate automatically as Cellular connections are SIM specific.
Figure 28 4g Cellular modem settings Modem-Reported Indicator allows users to use the modem-reported value for the number of bars of signal strength indicated, which is generally more accurate. Use of this option may cause trouble with certain modems. Modem must be re-attached after changing this option.
VII. MAKING CROSSLOCK CONNECTIONS ON BRIC-LINK II Comrex first introduced CrossLock—its technology that creates an additional reliability layer to ensure quality broadcast connections—with version 4.0 firmware in 2016. As an increasing majority of users updated their units to CrossLock-capable firmware, connections made using CrossLock became the norm for Comrex codecs and are considered standard in BRIC-Link II and ACCESS Codec connections.
Figure 30 CrossLock VPN One limitation of CrossLock is that each codec that joins the CrossLock VPN must be familiar with the others. This process takes place automatically when Switchboard is used. As detailed in section IX, connections that don’t use Switchboard need special configuration. MULTIPLE NETWORK SETUP In the case of more than one network attached to a BRIC-Link II (e.g.
CrossLock Connections to MultiRack Without CrossLock active, a codec will make BRIC Normal connections to MultiRack instance #1 on port 9000. Instance #2 will connect on 9002 and instance #3 will connect on 9003. These are on the MultiRack side, and the remote codecs will all use their default ports of 9000. The CrossLock connection between the Comrex hardware happens over a single port (9001) but the BRIC Normal connections take place virtually on their usual legacy ports within that VPN.
VIII. MAKING SWITCHBOARD CONNECTIONS ON BRIC-LINK II This section describes the procedure of making and receiving connection on BRIC-Link II via the Comrex Switchboard server. This is the easiest, but not the only way to make BRIC-Link II connections. Before connections are made this way, you must set up and configure a Switchboard Account as described in Section X.
Once your Switchboard peers are configured, connecting to one is simple: 1. Select the desired Switchboard peer. 2. Make sure the “gear” icon is green. 3. Click “Connect” in the upper right corner. Switchboard connections can be ended on either end of the link, by choosing the active connection in the list and clicking “Disconnect”. Incoming connections will appear as new entries in the Switchboard peer list while they are active. They can be disconnected the same way.
IX. MAKING MANUAL CROSSLOCK CONNECTIONS Creating new Remotes When connections are added to the list manually, we call them “remote entries,” or “remotes” for short. To create a new remote connection, click on the “Plus Sign” on the right of the screen (1 in Figure 32) to Add A New Remote Connection. This will bring up a dialogue box where a new remote’s parameters may be defined (Figure 32). 1 Figure 32 Edit Remote Settings Choose a name for the remote (e.g.
Figure 33 Profile manager tab Back up remote BRIC-Link II features an ability to have an automatic backup to a designated remote connection. A specific backup connection (for when the primary fails) is designated when a new remote is created. As shown in Figure 34, selecting the backup option opens a menu allowing selection of other outgoing remotes that have been created.
If the primary remote is restored and BRIC-Link II can detect a valid signal, it will automatically disconnect the backup and revert back to the primary remote. To enable Fall Forward, click the “Fall Forward” option in the Edit Remote Settings prompt and select Yes (Figure 34). CONNECTING AND DISCONNECTING Once the remote connection entry is completed in the Connections Tab, highlight the remote and select Connect.
X. SETTING UP YOUR SWITCHBOARD ACCOUNT The Switchboard Traversal Server is a service built and maintained by Comrex on the public Internet that provides users a directory of other users, facilitating connections to devices that would normally have trouble accepting incoming IP connections. Use of Switchboard is free and comes activated from the factory. Use the instructions in the user interface chapters of this manual to configure Switchboard on the BRIC-Link II unit.
Note: MultiRack instances must be added to Switchboard individually. Instance 1 Switchboard ID is the same as the unit MAC Address, while Instances 2-5 use the same MAC address, with a suffix added to designate the instance Switchboard ID. As an example, if the primary Ethernet MAC address on a MultiRack is 00:01:40:c0:0d:15, that’s the ID input for MultiRack instance #1. Instance #2 is added as 00:01:40:c0:0d:15-2, instance #3 uses -3, etc.
By default, a master Contact List is created that contains all codecs in an account. Every codec in the fleet uses the master list by default. For users uninterested in segregating codes on their account, the default configuration will work fine. NOTE: Assigning a Contact List to a codec determines what gets displayed in its own list. It does not have any impact on how that codec is displayed on other devices. FOLLOWING contact lists Each unit also has the ability to Follow a Contact List.
Figure 42 follow cOntact list On the next screen, check the Contact List(s) that you want this codec to Follow, and press “Update Contact List” (Figure 42). One important point to remember: Following a Contact List on a codec only determines which units get displayed on that codec’s own list. It has no impact on how that codec itself is displayed on other devices.
Figure 44 share a device To create a Share, click the Sharing tab and then select “Add New Share” (Figure 43). The following screen then allows users to choose which codec(s) they want to include in a Share (Figure 44).
Figure 46 Sharing accounts Finally, while it is possible to delete Shares, Comrex recommends disabling them instead. This will stop the Share and won’t require any future work to recreate it. To disable a Share, simply click the orange Disable button on the bottom right of the Share edit page (Figure 47).
Figure 48 multiple contact lists If multiple Contact Lists have been designated as “Followed“ on a unit’s Switchboard interface, each Contact List will appear at the bottom of the Connections tab (Figure 48). To view and/or connect to the unit(s) within a list, select the list and press the Open Folder button on the upper right. Figure 49 viewing list devices While viewing the units in a list, the units will be displayed and the lists themselves will temporarily disappear from the screen.
Figure 50 bulk actions To do this, press the Bulk Action button in the bottom right corner of the Contact List tab (Figure 50). The three steps to create a Bulk Action are: 1. Choose the type of action to perform. 2. Select the codecs targeted with this change. 3. Identify the Contact List that will be impacted by the change. Step 1: Choose the Action Type First, select which of the four types of Bulk Actions to perform (Figure 51): • • • • ADD codecs to a Contact List. REMOVE codecs from a Contact List.
Figure 52 Bulk device selection After completing this step, specify whether to target the units that are a part of a Contact List or the units that are Following that list (i.e., the option in the yellow-outlined box on the middle-left of the above figure). Note: Bulk Actions can ONLY be performed on ENTIRE Contact Lists. They CANNOT be performed on individual codecs or on a portion of a Contact List.
Switchboard Theory and Concepts Switchboard is useful because it’s not always simple to connect two devices, which are essentially “peers”, over the Internet. There are two major reasons for this. First, to initiate a stream to a device over the Internet requires knowing its IP address. This is the number that gets applied to the destination field of the IP packet, so internet routers can determine how best to send it along its way. Every device that connects directly to the public Internet must have one.
The challenges of connecting codecs behind NAT routers will be addressed in more detail shortly. For now, remember that one of the problems NAT servers add is that private IP addresses delivered to codecs (and the only addresses of which the codecs are aware) have no bearing on the public addresses seen from the Internet.
This can work well for fixed installations, but it’s not always an easy task to obtain that kind of security access on corporate routers. Additionally, forwarding functions are implemented differently depending on the hardware. One can easily imagine the complications of obtaining or managing port forwarding on the LAN when arriving at a new remote venue. This would likely encounter a large amount of resistance or confusion on the part of local IT staff.
A good way to think of this is that an outgoing packet “punches a hole” in the router, through which authorized reply packets may be returned to the codec for a limited time (Figure 56). Figure 56 bidirectional communication Switchboard aids in breaking through these different types of routers for incoming calls. Because it is in constant contact with all subscribed codecs, it can send and receive test patterns to determine whether one or more NAT routers exist on a link and what type they are.
XI. OPERATING BRIC-LINK II IN A 24/7 ENVIRONMENT BRIC-Link II can be configured for “always on” operation. This allows for constant STL communication and operations requiring long-term connections. In BRIC Normal mode (the default mode of operation), BRIC-Link II transfers all its audio data via the UDP 9000 protocol. This is in contrast to most web-based connections like browsing and email, which use the bidirectional TCP protocol. UDP, unlike TCP, is not “connection oriented” (i.e.
Figure 57 always connect to setting Backup Remote BRIC-Link II has an additional option for constant connections. When building a remote entry, a field is available for backup options, and one of these options is “Keep Retrying This Remote” mode. In a similar fashion, using this mode will allow the unit to disregard the timeout value and keep a persistent connection attempt. The difference is that the Disconnect function still works and the connection will not be re-initiated on a power-up.
Additionally, there is a box in the Change Remote Settings tab labelled Automatically Fall Forward. If this box is checked, the system will constantly attempt to reconnect the primary remote while connected to the fallback remote. If connection is successful, the connection to the “Fallback” will be terminated.
XII. ABOUT THE ALGORITHMS When building profiles for BRIC-Link II and remote devices, there are several different audio encoder options to use for each direction of the link. Different audio encoder options each have advantages and disadvantages depending on the situation. The following is a refresher on audio codec algorithms to assist in making the best choice. AAC This algorithm is a highly regarded standard for compressing audio to critical listening standards.
FLAC* This encoder compresses audio data using a lossless algorithm. This means that the audio extracted from the decoder is identical to the audio input to the encoder, with no coding artifacts. FLAC typically removes 30-40% of the network data compared to Linear PCM, but the actual data rate is variable and is based on the complexity of the coded audio. Using FLAC over Linear PCM typically results in a slightly higher (5 ms) overall delay. G.
Algorithm Comparison Chart for ACCESS NX Rack AAC Required Bitrate Coding Delay Audio Bandwidth 64 kb/s 69 ms 20 kHz D1 Mono 96 kb/s 69 ms 20 kHz D2 Stereo 128 kb/s 69 ms 20 kHz D3 Dual Mono allows independent programming to be sent on both L&R channels 128 kb/s 69 ms 20 kHz D4 Stereo 128Kb 256 kb/s 69 ms 20 kHz D5 Dual Mono 256Kb allows independent programming to be sent on both L&R channels 56 kb/s 69 ms 20 kHz D6 Mono 56Kb 96 kb/s 69 ms 20 kHz D7 Mono 96Kb 160 kb/s 69 ms
XIII. MULTISTREAMING BRIC-Link II supports the ability to run one encoder per connection, but this single encoder stream may be sent to up to three destinations simultaneously. This capability is referred to as a Multistream, as the encoder creates a separate but identical outgoing stream to each decoder. (Note: A User’s Internet connection must be able to support these streams.
Multistreaming Arrangements The following includes two examples of Multistream arrangements involving the BRIC-Link II. In the first environment, the BRIC-Link II that is serving the Multistream initiates calls, and in the second, the serving BRIC-Link II accepts all of the incoming connections. BRIC-Link II initiates the call In the “Multistreamer as caller” model, two different profiles will be built on BRIC-Link II A.
XIV. IP MULTICAST IP Multicast is an efficient way of delivering BRIC-Link II digital audio streams to multiple locations. This involves relying on the network to distribute the stream to the locations that require it, rather than creating an independent stream for each user. Performing an IP Multicast requires the use of an IP Multicast-capable network. The commercial Internet, with few exceptions, is not capable of supporting IP Multicast. Some private LANs and WANs are IP Multicast capable.
The important settings for Multicast are: • • Sender/Receiver - Determines whether this particular BRIC-Link II is designed to generate and encode the IP Multicast stream (send) or decode one (receive). Encoder Type - Determines the algorithm format of stream to be used by the Multicast encoder—not relevant for decoders. In addition to the basic options for IP Multicast profiles, clicking the Advanced box will allow setting of the same Advanced Options available for Normal BRIC (Unicast) profiles.
Xv. STREAMING SERVER FUNCTION BRIC-Link II has the ability to act as a streaming server, delivering AAC and HE-AAC to compatible PC-based media players. Currently tested media players include WinAmp, VLC and Windows Media Player 12 and up. By default, streaming server functionality is turned off. To enable it, go to the System Settings tab of the User Interface and choose HTTP Settings option. Under the first option, set Accept Incoming Connections to Enabled (Figure 63).
The Genre, Info URL and Public options may be set for anything, or left alone. These options, if applied, will be embedded into the stream. Decoding a Stream To decode a stream, open one of the supported players and select the option to open a URL-based stream. In Winamp and VLC, input the address of the BRIC-Link II in the following format: http://192.168.0.75:8000 (using the actual IP address, and the actual port if not changed from default 8000) In Windows media, input the address like this: http://192.
XVI. MAKING EBU3326/SIP COMPATIBLE CONNECTIONS Comrex codecs (and many other brands) have a set of protocols that allow easy IP connections between units. In general, when connecting between Comrex hardware, it’s best to use these proprietary modes to take the most advantage of the features of the product. However, many users are concerned about getting “locked in” to a certain codec brand.
EBU3326/SIP Modes A function of placing a SIP-style call is the ability to register with a SIP server. This is a server that exists somewhere on the network, usually maintained by a service provider. Several free servers exist that can offer registration, like Onsip.com. The BRIC-Link II allows EBU3326/SIP calls to be placed or received with or without registration on a SIP server.
• The password on the SIP account. Figure 65 shows how this information can be applied: by enabling the Use SIP Proxy option under EBU 3326/SIP on the Systems Settings tab. Figure 65 EBU3326/SIP Settings Once this information is correctly entered, a new field appears in the “Registration Status” box located on the Connections tab (Figure 66). Figure 66 Sip status The status will reflect the progress of the registration process. When complete, this will display Online.
SIP registration can be very simple with some servers, and others can require more advanced settings, which are described in the Advanced Topics section on the following page. Making Registered SIP Calls When registered, calls made using an EBU3326/SIP profile behave differently than normal. The address field, regardless of whether it is a SIP URI or an IP address, is forwarded to the server. No connection attempt is made until the server responds.
• routers that have shorter or longer binding timings, i.e., the router may have a tendency to “forget” that the codec is ready to accept incoming calls and block them. SIP Domain: This only applies to Registered mode. It’s the name of the network controlled by the SIP server. This parameter must be passed by the codec to the server. Under most circumstances, this is the same as the server/proxy address, and if this field is not populated, that is the default.
In point-to-point connections this isn’t possible, and some hacks are required to make this work. The first place to look is the router, as many modern routers are aware of this issue and may be configured to ease connectivity. If a router supports the SIP Application Layer Gateway (ALG), enabling this option can fix the issue. The router will read the SIP handshake, find the outgoing address field, and replace it with the public IP. This is a valuable solution in environments where the router supports ALG.
XVII. LICENSE & WARRANTY DISCLOSURES FOR BRIC-LINK II Licenses MPEG-4 audio coding technology licensed by Fraunhofer IIS http://www.iis.fraunhofer.de/amm/ ACCESS uses proprietary and open-source software programs. Some of the open-source programs are licensed under the Gnu Public License (GPL). For more information on GPL see http://www.gnu.org. As per the GPL, source code for this software is available on request from Comrex on CD-ROM or other electronic format.
Further copyright notice for ncurses, dropbear PuTTY and libxml2 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copy
The next two paragraphs apply to all software contained in this product: WITH THE EXCEPTION OF THE WARRANTIES SET FORTH ABOVE, THE PRODUCT (MEANS COLLECTIVELY THE HARDWARE AND SOFTWARE COMPONENTS) IS PROVIDED STRICTLY “AS-IS.” COMREX CORPORATION AND ITS SUPPLIERS MAKE NO WARRANTY, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR WARRANTY AGAINST LATENT DEFECTS.
XVIII. SWITCHBOARD TRAVERSAL SERVER USE DISCLAIMER TRAVERSAL server disclaimer You have purchased a product from Comrex that uses the Switchboard TS (Traversal Server) to provide the ability to locate Comrex hardware via the Internet and to aid in the making of connections when certain types of NAT routers are involved in the link.
XIX.
EC Declaration of Conformity for R&TTE Directive We: Manufacturer’s Name: Comrex Corporation Manufacturer’s Address: 19 Pine Road Devens, MA 01434 hereby declare on our sole responsibility that the product: Comrex BRIC-Link II Digital Audio Codec to which this declaration relates is in conformity with the essential requirements and other relevant requirements of the R&TTE Directive (1999/5/EC).
U.S. and Canadian Regulatory Information for the BRIC-Link II This equipment complies with Part 68 of the FCC rules and the requirements adopted by the ACTA, as well as the applicable Industry Canada technical specifications. On the bottom of this equipment is a label that contains, among other information, a product identifier in the format US:DXDMD01BACCRK. If requested, this number must be provided to a U.S. telephone company.
APPENDIX A - HOTSWAP BRIC-Link II connections are able to utilize Hotswap, allowing users running CrossLock in “Dual Network” mode to designate a primary and secondary network. This secondary network (e.g. wireless 4G) serves as a backup to the primary in case of network failure. Hotswap is a System Setting in BRIC-Link II. Figure 67 Hotswap A typical usage scenario would be a codec that is active 24/7 providing a STL connection as shown in Figure 67.
Setup Setup for HotSwap is done entirely on the end of the link that has dual networks connected. On the BRIC-Link II, the best way to set up HotSwap is via the Network Manager page, accessible via the web based interface. Navigate to the three-line Main Menu icon in the upper left hand corner of the screen and select Network Manager. Before entering the Network Manager, the secondary network should be attached to the BRIC-Link II via USB.
Exit the Main Menu and navigate to the System Settings page. Under CrossLock VPN, locate the entry labeled “Redundant Transmission” (Figure 70). Change this from the default “Off” to “On”, and then click “Apply Changes”. Figure 70 CrossLock redundant transmission Finally, set one of the contact closures to sound an alert when the HotSwap function is engaged. Still in the CrossLock VPN settings, select “HotSwap CC unit”.
Figure 72 Hotswap CC indicator 96
APPENDIX B - IP COMPATIBILITY The BRIC-Link II is capable of encoding and decoding a choice of three different types of non-BRIC-Link II streams: Standard RTP, Luci Live, and Zephyr Xstream. The choice is exclusive—i.e., you must set the BRIC-Link II specifically for the type of stream you wish to be compatible with and you will remain incompatible with the other two types unless you change it. This setting has no effect on normal BRIC-Link II functions, which continue to operate as before. 1.
• Outgoing Connections - Build a profile using the Profile Manager on the BRIC-Link II and select a Channel Mode of Standard RTP. Then choose an Xstream-compatible encoder for the outgoing call. The Xstream will control what type of stream, if any, is returned to the BRIC-Link II. 3. Standard RTP - This mode is set to receive a basic, unformatted AAC stream within a standard RTP/UDP structure. At present, this mode does not offer compatibility with other industry devices.
Appendix C - BRIC-Link II on Unidirectional Networks Under most circumstances, BRIC-Link II requires an IP path in both directions for successful connections, even when audio is being sent only one-way. For networks that provide data only in one direction, it is possible to use Standard RTP mode to establish and maintain these links. This section describes how to set that up. The codec has several compatibility modes under the Standard RTP channel mode.
APPENDIX D - Information for IT Managers The purpose of this appendix is to describe all open ports and services available on the Comrex BRIC-Link II. The Comrex BRIC-Link II is a device designed to move real-time, wideband audio over IP networks. The main network interface is 1000BaseT-Ethernet. The device contains an optimized version of Linux kernel. The IP parameters are set by a computer on the local LAN using a proprietary broadcast UDP protocol.
APPENDIX E - CONNECTIONS TO MULTIRACK The purpose of this appendix is to describe how to make connections to Comrex ACCESS MultiRack. BRIC NORMAL CONNECTIONS The Comrex ACCESS MultiRack allows users to make up to 5 separate AES67 connections. This feature allows additional setup including the assignment of separate UDP ports for each MultiRack Instance. UDP 9000 is the default port for BRIC Normal connections. Instance #1 on MultiRack will use the UDP 9000 port by default.
MAking Connections With Switchboard In order to use Switchboard, users must first have an account with the server. This account can be obtained by contacting Comrex at 978-784-1776 / 800-237-1776, or by emailing techies@comrex.com / info@comrex.com. Only one account is required for each group of codecs. Once a user name and password is provided, navigate to switchboard.comrex.com in a web browser. When first accessing Switchboard, there will be a notice stating that no units have been added to the account.
