white-glass-22386
05/12/2025, 1:31 PMtall-airline-16756
05/12/2025, 1:31 PMtall-airline-16756
05/12/2025, 1:31 PMaudio_enabled=False
in RoomOutputOptions
, the agent should publish text responses to the lk.transcription
text stream topic without audio output. This configuration is typically used in scenarios where audio is forwarded elsewhere or not required.
To troubleshoot the issue where text responses are not received on the front end, please verify the following:
• Ensure that the text_enabled
option in RoomInputOptions
is set to True
, as you have done.
• Check if the text responses are being published to the lk.transcription
text stream topic as expected.
• Confirm that your front-end is correctly subscribed to the lk.transcription
topic to receive the text responses.
• Ensure there are no errors or exceptions in the backend logs that might indicate issues with the text stream publishing.
If the issue persists, please let me know, and I can assist further or escalate the matter to a specialist.
Sources: Text and transcriptions | LiveKit Docswhite-glass-22386
05/12/2025, 1:35 PMtall-airline-16756
05/12/2025, 1:35 PMlk.transcription
topic. However, here are some general steps you can take to troubleshoot and confirm message delivery:
• Check the backend logs for any errors or confirmation messages related to the publishing of text responses to the lk.transcription
topic.
• Ensure that your front-end is correctly subscribed to the lk.transcription
topic and is capable of receiving and displaying the messages.
• Use debugging tools or logging within your application to confirm that the text responses are being generated and sent to the topic as expected.
If you need further assistance or if the issue persists, please let me know, and I can escalate this to a specialist for a more in-depth investigation.white-glass-22386
05/12/2025, 1:36 PMtall-airline-16756
05/12/2025, 1:37 PMsetLogExtension
function in the LiveKit JavaScript SDK to hook into the SDK’s logging system. This allows you to capture all log messages for troubleshooting. For example:
setLogExtension((level, msg, context) => {
// Capture all logs for troubleshooting
console.log(level, msg, context);
// Optionally send logs to a logging service
// yourLoggingService.send(level, msg, context);
});
1. The setLogExtension
function provides three parameters:
◦ `level`: The log level (e.g., debug, info, warning, error).
◦ `msg`: The log message text.
◦ `context`: An object containing additional context information.
1. For room-specific logs, you can access room information in the context object once a connection is established:
setLogExtension((lvl, logmsg, ctx) => {
if ('room' in ctx) {
// Room-specific context is available here
console.log(`Room ${ctx.room}: ${logmsg}`, ctx);
}
});
1. Enhance logs with additional information like timestamps if needed:
setLogExtension((level, msg, context) => {
const enhancedContext = { ...context, timeStamp: Date.now() };
if (level >= LogLevel.debug) {
console.log(level, msg, enhancedContext);
}
});
By implementing this, you should be able to capture and analyze all logs, including text logs, for troubleshooting purposes. If you need further assistance, feel free to ask!
Sources: How to Send Logs from the JavaScript SDK to Providers like Datadogwhite-glass-22386
05/12/2025, 1:45 PMwhite-glass-22386
05/12/2025, 1:45 PMtall-airline-16756
05/12/2025, 1:45 PMwhite-glass-22386
05/12/2025, 1:54 PM