DailyTransport
server-side implementation.
true
, the transport will buffer local audio until the bot is ready. This is useful for ensuring that bot gets any audio from the user that started before the bot is ready to process it.DailyTransportConstructorOptions
extends the DailyFactoryOptions
type that is accepted by the underlying Daily instance. These options are passed directly through to the Daily constructor. See the Daily API Reference for a complete list of options.connect()
. See below.connect()
, the DailyTransport
optionally takes a set of DailyCallOptions
to connect to a Daily room. This can be provided directly or via a connection endpoint passed to the PipecatClient
’s connect method. If using an endpoint, your endpoint should return a JSON object matching the DailyCallOptions
type. See the client connect() documentation for more information.
PipecatClient
and should be called from the PipecatClient
. However, there are a few transport-specific methods that you may need to call directly. When doing so, be sure to access your transport via the transport
property of the PipecatClient
instance.
preAuth()
This is the one method meant to be called directly, which is used to allow you to gather information about the Daily room prior to connecting. As a Daily-specific action, it is not exposed through the PipecatClient
. This method must be called prior to connect()
and use the same room_url
and token
(optional) as what will be returned by your connection endpoint/eventually used on connect()
.
PipecatClient
event handlers. For Daily-specific events, you can attach listeners to the underlying Daily call client. For a list of available events, see the Daily API Reference.
dailyCallClient
property.
PipecatClient
to perform the equivalent
action.@pipecat-ai/daily-transport