Binary Floor Control Protocol scenarios

Last Updated : Feb 04, 2020 |
Prolog information
Examples of scenarios in which BFCP is used and the offer and answer messages for each scenario.

Remote Worker XT-client calls XT-MCU

Sr No
Sender
Floor-ctrl
Setup attribute
Connection
BFCP application line
1
Remote Worker XT-client
c-only
actpass
new
Valid connection and port
2
Avaya SBC
c-only
passive
new
Valid connection and port
3
XT-MCU
s-only
active
new
Discarded port. For example, 9
4
Avaya SBC (responds to Remote Worker XT-client)
s-only
passive
new
Valid connection and port
The same parameters are exchanged when a Remote Worker XT-client calls Elite-MCU.

Remote Worker XT-MCU calls internal XT-client

Sr No
Sender
floor-ctrl
setup attribute
connection
BFCP application line
1
Remote Worker XT-MCU
c-s
actpass
new
Valid connection and port
2
Avaya SBC
c-s
passive
new
Valid connection and port
3
XT-client
c-only
active
new
Discarded port
4
Avaya SBC
c-only
passive
new
Valid connection and port

XT-MCU internal to enterprise dials out and calls XT-client, which is a remote worker

Sr. no
Sender
floor-ctrl
setup attribute
connection
BFCP application line
1
XT-MCU
c-s
actpass
new
Valid connection and port
2
Avaya SBC
c-only
passive
new
Valid connection and port
3
Remote worker XT-client
c-only
active
new
Discarded port
4
Avaya SBC responds to XT-MCU
c-only
passive
new
Valid connection and port

Elite-MCU Release 8.3 internal to enterprise dials out and calls XT-Client which is remote worker

Sr No.
Sender
floor-ctrl
setup attribute
connection
BFCP application line
1
Elite-MCU
s-only
passive
new
Valid connection and port
2
Avaya SBC
s-only
passive
new
Valid connection and port
3
Remote worker XT-client
c-only
active
new
Discarded port
4
Avaya SBC responds to Elite MCU
c-only
active
new
Valid connection and port
After Avaya SBC responds to Elite MCU, Avaya SBC does not start any TCP connection towards Elite MCU 8.3. Elite MCU 8.3 times out and tries to establish a TCP connection.

Failover or network outage

In a failover or network outage, an entity tries to reestablish a TCP connection on the existing connection. If the entity fails, Avaya Meetings Server does not set up the connection again.