The shipped RealtimeBridgeContext carries no first-class Direction field (it is a meeting-
shaped contract), so the bridge-server engine forwards the session's Direction into the driver's
Configuration under this key. Telephony drivers and tests set Configuration[DIRECTION_CONFIG_KEY]
to 'Inbound' / 'Outbound'; the default when absent is 'Outbound' (the agent placed the call).
The well-known key under which BaseTelephonyBridge.Connect reads the call BridgeConnectDirection from RealtimeBridgeContext.Configuration.
The shipped RealtimeBridgeContext carries no first-class
Directionfield (it is a meeting- shaped contract), so the bridge-server engine forwards the session'sDirectioninto the driver'sConfigurationunder this key. Telephony drivers and tests setConfiguration[DIRECTION_CONFIG_KEY]to'Inbound'/'Outbound'; the default when absent is'Outbound'(the agent placed the call).