Collapse AllExpand All

17.7. BCNE - B-channel negotiation for EDSS1 Previous topic Parent topic Child topic Next topic

Feature:

B-channel negotiation (Call Collision)

Function:

The BCNE parameter must be active both on the user side and in the network. The already existing B-channel collision resolution "preferred<->exclusive and exclusive<->preferred" is extended to include "exclusive<->exclusive and preferred<->preferred" scenarios.
3 scenarios are provided for:
A-Side preferred, B-Side preferred: The B-channel is recognized for the A-side. The B-side offers another channel, if available, or releases.
A-Side exclusive, B-Side exclusive: The B-channel is recognized for the A-side. The B-side releases.
A-Side exclusive, B-Side preferred or A-Side preferred, B-Side exclusive: The side of the B-channel marked "exclusive" is recognized as such. The other side offers another B-channel, if available, or releases.
IMPORTANT:
This only works if one side is set up as the network and the other is set up as the user (lines with PROTVAR EDSS1NET or EDSS1NETR are regarded as the network side, all other lines are regarded as the user side).

AMO Interrelationships:

TDCSU <B-channel negotiation BCNEG = Y/N>, < Call collision handling CCHDL= ASIDE/BSIDE/NONE >
B-channel negotiations are controlled with the BCNEG parameter. Connections that are set up with "exclusive" are not ready for negotiation. In contrast to this, there are lines that are set up with "preferred", ready for negotiation, and that give priority to exclusive connections.
The parameter BCNEG must be set inversely on the B-channel of the partner system. BCNEG is used to exclude conflict scenarios when a connection is set up. If "BCNEG" is entered, then the trunk is ready for negotiations through the use of another B channel; otherwise the trunk tries to impose the seizure of the B-channel

Device types:

Digital trunks

Protocol variants:

For example, ECMAV2, PSS1V2, EDSS1NET, EDSS1NETR