Type Alias RealtimeAvatarUnavailableReason
RealtimeAvatarUnavailableReason:
| "endpoint"
| "bridged"
| "phone"
| "custom-disabled"
| "unknown-avatar"
| "no-binding"
| "host"
| "browser"
| "decoder-missing"
| "decoder-failed"
| "publish-failed"
| "video-off"
Why a session that asked for an avatar runs audio-only:
'endpoint': the model, on the endpoint serving it, renders no avatar;'bridged': the session runs on the server (a meeting bot) and its host can't publish video into the room;'phone': the session is a phone call (a carrier call, or one that reaches a meeting room through SIP): the caller hears the agent and sees no video, so the session asks the model for no avatar;'custom-disabled': custom avatars are not enabled;'unknown-avatar': the request names no avatar the vendor knows;'no-binding': the persona has no avatar on this vendor;'host': the app showing the call shows no agent video: it told the mint so (the embeddable widgets and the mobile app have no channel that shows it), so the session asked the model for none, or the avatar was granted and the app asked for no agent video when it connected;'browser': the avatar was granted and the app asked for it, but the browser could not play it;'decoder-missing': the meeting host has no usable decoder (no ffmpeg, one too old, or one without the H.264 and AAC decoders), so the meeting session asked for audio;'decoder-failed': the meeting bot's decoders kept failing, so the avatar was taken down mid-meeting;'publish-failed': the meeting room refused the bot's video track;'video-off': the call picked an avatar (a voice that comes with one), and the voiced agent's own video setting is off, so the session asked the model for none.