TANDBERG Border Controller User Manual
xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Mode xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Limit
Pipes may be shared between one or more links. This is used to model the situation where a site communicates with several other sites over the same broadband connection to the Internet. Each link may have up to two pipes associated with it. This is useful for modeling two sites, each with their own broadband connection to the Internet backbone. Calls between zones or subzones consume bandwidth from each zone and any pipes on the link between them.
When a Border Controller is neighbored with another Gatekeeper or a Border Controller, the neighbor is placed in its own zone. This allows you to control the bandwidth used by calls to and from endpoints controlled by the other Gatekeeper. Sometimes you may place and receive calls to Gatekeepers you are not neighbored with (See section 6). These Gatekeepers, and any unregistered endpoints reached by dialing their IP address, are placed in the Default Zone.
If bandwidth control is in use, there are two possible behaviors when a call cannot be placed at the bandwidth requested. By default the call will be connected at a reduced bandwidth
Figure 7: Configuring down-speeding options
xConfiguration Gatekeeper Downspeed PerCall Mode: <On/Off>
xConfiguration Gatekeeper Downspeed Total Mode: <On/Off>
4.1Bandwidth Control and Firewall Traversal
When a Border Controller and Gatekeeper are being used to traverse a firewall, an additional zone and subzone come into use.
The traversal zone is used to represent the zone containing the Gatekeeper Controller this Border Controller is paired with. This zone is automatically added for you. The traversal subzone represents the Border Controller itself. The traversal subzone allows you to control total and per call bandwidths passing through the Border Controller. Unlike other subzones, no endpoints will ever be registered in this subzone.
16