We are currently using livekit cloud but self hosting the livekit agents on aws. We use Telnyx for telephony. Our agent has to talk to our app’s backend server a lot. We do it by establising a websocket connection with our backend server. We use python-socketio for websocket on both backend server and self-hosted livekit agent.
I am investigating migrating the self-hosted livekit agent to livekit cloud. We are not considering livekit telephony as it does not support outbound calls and onlyy supports US local numbers.
- Has anyone taken a similar journey? What are some gotchas/surprises we need to be aware of?
- Does livekit cloud agent allow us to use websocket connections to our backend server? Can we continue using python-socketio?
- Does it support both incoming calls and outgoing calls?
Hi Vinod, you should find LiveKit agents hosted on LiveKit cloud to be functionality identical to self-hosted agents. You do get a free LiveKit cloud agent deployment on the build tier, so feel free to spin up a separate project and test it out to validate if there are any issues.
Does livekit cloud agent allow us to use websocket connections to our backend server? Can we continue using python-socketio?
Yes, you can continue using your existing networking code. The only caveat is your agents will run from within LiveKit cloud, so they will have a different IP address and exist outside of your network infrastructure.
Does it support both incoming calls and outgoing calls?
Yes, your dispatch rules will remain unchanged (you will need to update the agent name if you have renamed your agent)
Has anyone taken a similar journey? What are some gotchas/surprises we need to be aware of?
I’ll let others speak to that, but many have made this transition since we introduced self-hosted agents prior to LiveKit cloud hosting.
2 Likes
Is there an UI for secrets managements? Or is it only CLI?
Currently it is only through the CLI