https://livekit.io logo
Join Slack
Powered by
is sip call status changıng dynamıcally or we nee...
# ask-ai
m
is sip call status changıng dynamıcally or we need to check ıt ? @millions-hair-24956
g
The SIP call status can change dynamically, and you can monitor these changes by listening to specific events. According to LiveKit documentation, the 
sip.callStatus
attribute reflects the current status of a SIP call, with possible values such as 
active
, 
dialing
, 
ringing
, and 
hangup
. To track these changes, you can listen to the 
participant_attributes_changed
event, which notifies you when participant attributes, including 
sip.callStatus
, are updated. Would you like more details on how to implement this monitoring? Sources: - SIP participant | LiveKit Docs - LiveKit Slack Discussion 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
m
20-3-egress | File "/usr/local/lib/python3.11/site-packages/livekit/rtc/event_emitter.py", line 58, in emit 20-3-egress | callback(*callback_args) 20-3-egress | File "/app/agent.py", line 174, in on_participant_attributes_changed 20-3-egress | if participant.identity == user_identity: 20-3-egress | ^^^^^^^^^^^^^^^^^^^^ 20-3-egress | AttributeError: 'dict' object has no attribute 'identity' @millions-hair-24956
g
The error you're encountering indicates that the 
participant
object is being treated as a dictionary, but you're trying to access it as if it were an object with an 
identity
attribute. This typically happens when the event handler for 
participant_attributes_changed
is not correctly set up to handle the participant object. To resolve this, ensure that the 
participant
parameter in your 
on_participant_attributes_changed
function is indeed an instance of the 
Participant
class, not a dictionary. You might need to adjust how you're retrieving or passing the participant object in your event handler. Would you like more detailed guidance on how to handle this issue? Sources: - LiveKit Python SDK Documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
It seems likely that the errors you're encountering with the LiveKit egress service are related to missing libraries and configuration issues. Here's a breakdown of the key issues and potential solutions: 1. CUDA Library Warning: The warning about 
libcuda.so.1
indicates that the CUDA library is not found. If you are not using GPU acceleration, you can ignore this warning. Otherwise, ensure that the CUDA toolkit is installed and the library path is correctly set. 2. Xvfb Warnings: The warnings related to 
xkbcomp
and unresolved keysyms are generally not critical and can be ignored unless they are causing functional issues. These warnings are related to the virtual framebuffer (Xvfb) used for headless operation. 3. GStreamer Warnings: The warnings about unmapped audio formats suggest that certain GStreamer plugins or elements are not available. Ensure that all necessary GStreamer plugins are installed, especially those required for your specific media processing needs. 4. GLib-GObject Critical Error: The error about the 
bitrate
being out of range suggests a configuration issue. Check your egress configuration to ensure that the bitrate is set within a valid range for the media being processed. Would you like more detailed guidance on any specific part of this setup? Sources: - https://docs.livekit.io/home/self-hosting/ingress/#Configuration - https://livekit-users.slack.com/archives/C07FVFARRK7/p1730731323.248749 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
If you're looking for further help, please follow-up on one of the other channels available for community support!
Open in Slack
PreviousNext
Powered by