Trunking
Last updated
Was this helpful?
Last updated
Was this helpful?
Trunking allows for an intelligent connection between multiple devices connected to Birch. Prior to allowing the system to dynamically manage these connections, they must be defined manual as the output of one device connected to the input of another device. The transport method is irrelevant to Birch; so long as the signal can get between the devices, Birch can use the trunkline to move a signal from one device to another.
Prior to making dynamic trunked routes, you must define the specific trunklines in the system. Any Admin may setup Trunklines in Settings > Trunklines.
Click Add Trunkline to define a new Trunkline.
The Trunkline is defined as an output from one device to the input of another:
Device A: Select the Device and Destination Port for the Trunkline.
Device B: Select the Device and Source for the Trunkline.
Default Source: Select a Default Source for Birch if the Trunkline is manually cleared.
Lockable: Choose if this Trunkline will be Lockable. If the Trunkline is lockable, the user will have the ability to lock the Trunkline, which will individually lock each step in the trunking path on each device. Additionally the Trunkline will display as locked in Birch.
In many routing systems, the router's Salvo or Preset will not change destinations that are currently locked (unless explicitly programmed to do so). Therefore, allowing a Trunkline to be lockable may impact the individual routing systems ability to change that destination via a Salvo or Preset. This detail needs to be carefully considered when using trunking from Devices there may be limited and critical paths that are controlled by Salvos or Presets.
When choosing a Source from one Device and a Destination from a different Device, Birch will automatically try to find an available Trunkline to complete the route. If a Trunkline is found, Birch will selected the best Trunkline to use and present that option to the user.
To make the route, simply click Take and Birch will make routes on all the necessary devices to connect the signal. You can override the Trunkline being used to make this route by clicking the on the circled numbers available on each of the Trunklines.
Once the route is complete, Birch reflects the status of each Trunkline.
There is no limit to the number of Devices that can be linked via Trunklines to make a single route. If there is a possible path, Birch can make the routes. If no routes between the Source and the Destination are available, Birch will provide an error.
Admin users can see status and manage Trunkline usage
The indicators provide feedback if there is an error in the Trunkline definition, if the Trunkline is in use, or is available, as well as if the Trunkline is lockable. Additionally an Admin can edit the Trunkline definition, or reset the trunkline back to its Default Source.
If the database of a Device is updated, Trunkline definitions will need to be updated as well. Birch does not assume that the index or name of a port on a Device still means it is configured as a Trunkline after a database update and requires manual Admin intervention to confirm or update the definitions. Birch will not put into use Trunklines that are current in error because of a database change.
