Hi Team, LK Phone number when dialed, rings witho...
# telephony
d
Hi Team, LK Phone number when dialed, rings without answer ~ So i 1 - deployed an agent( CA_asypjecrYjSF ) to LK Cloud, 2 - procured a number from LK, 3 - created a dispatch rule and added the agent with agent name. ( with the same agent name defined in the code ) 4 - associated the dispatch rule with procured number. what am i missing ? or how can i can troubleshoot this further ? Any help or suggestions are highly appreciated. thank you
btw, @echoing-kitchen-90064 any suggestion here ? ( sorry , for the direct tag, just trying, in case you are around and have any insights) thanks!!
r
Do you have an example session that did not get an agent.
d
yes, RM_h5z2FjwKwEUd
r
I notice your agent is in pending state. Do you see anything in the agent logs?
Also I notice that the
agent_name
is not set up in the dispatch it is.
d
thanks, and here is a screenshot for agent logs. Also could you please elaborate more on the agnet_name ? When I check my dispatch rule it has agentName set.
I noticed that my agent name doesn't appear on the console, do you know the right way to setup agent name for this scenario ? again, thank you very much for looking into this.
r
Is it set in your agent code?
d
yes, like so : @breezy-insurance-66772.rtc_session(agent_name="ABC-Agent") async def entrypoint(ctx: JobContext):
r
Hmm, that is not the name I see in the dispatch
d
yeah, meant OBH
r
@loud-breakfast-60455 or @echoing-kitchen-90064 any idea why agent is not getting dispatched?
d
image.png
r
I am not sure why on your dashboard under that agent the agent name is blank.
d
I was wondering the same! searched through documentation to see if I am missing something like defining in livekit.toml file in addition to code for it show up in dashboard but couldn't find anything.
e
was there another failed build after this was deployed?
d
i don't think so but i am deploying an updated version using lk agent deploy currently. trying to add agent name in livekit toml file to see if it helps.
e
ah shoot, i may have broken that
i see the agent_name is
OBH-Agent
on our end
it takes a bit for the data to filter back to the dashboard
d
just deployed a newer version, the screen shows agent running now but still when i call it just rings and no answer.
image.png
e
can you run
lk a logs
it is erroring out
d
image.png
e
Copy code
INFO:livekit.agents:starting worker
{"level": "INFO", "name": "livekit.agents", "message": "starting worker", "version": "1.3.6", "rtc-version": "1.0.20", "timestamp": "2025-12-16T20:46:37.244544+00:00"}
INFO:livekit.agents:preloading plugins
{"level": "INFO", "name": "livekit.agents", "message": "preloading plugins", "packages": ["livekit.plugins.silero", "livekit.plugins.turn_detector", "av"], "timestamp": "2025-12-16T20:46:37.245113+00:00"}
INFO:livekit.agents:HTTP server listening on :8081
{"level": "INFO", "name": "livekit.agents", "message": "HTTP server listening on :8081", "timestamp": "2025-12-16T20:46:37.254569+00:00"}
INFO:livekit.agents:initializing process
{"level": "INFO", "name": "livekit.agents", "message": "initializing process", "pid": 75, "timestamp": "2025-12-16T20:46:39.212505+00:00"}
INFO:livekit.agents:initializing process
{"level": "INFO", "name": "livekit.agents", "message": "initializing process", "pid": 79, "timestamp": "2025-12-16T20:46:39.239298+00:00"}
INFO:livekit.agents:killing process
INFO:livekit.agents:sending SIGUSR1 signal to process
{"level": "INFO", "name": "livekit.agents", "message": "killing process", "pid": 75, "timestamp": "2025-12-16T20:46:49.235956+00:00"}
{"level": "INFO", "name": "livekit.agents", "message": "sending SIGUSR1 signal to process", "pid": 75, "timestamp": "2025-12-16T20:46:49.236154+00:00"}
INFO:livekit.agents:killing process
{"level": "INFO", "name": "livekit.agents", "message": "killing process", "pid": 79, "timestamp": "2025-12-16T20:46:49.283471+00:00"}
INFO:livekit.agents:sending SIGUSR1 signal to process
{"level": "INFO", "name": "livekit.agents", "message": "sending SIGUSR1 signal to process", "pid": 79, "timestamp": "2025-12-16T20:46:49.284300+00:00"}
ERROR:livekit.agents:process exited with non-zero exit code -10
{"level": "ERROR", "name": "livekit.agents", "message": "process exited with non-zero exit code -10", "pid": 75, "timestamp": "2025-12-16T20:46:49.309180+00:00"}
ERROR:livekit.agents:process exited with non-zero exit code -10
{"level": "ERROR", "name": "livekit.agents", "message": "process exited with non-zero exit code -10", "pid": 79, "timestamp": "2025-12-16T20:46:49.353831+00:00"}
ERROR:livekit.agents:error initializing process
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 507, in wait_for
    return await fut
           ^^^^^^^^^
  File "/app/.venv/lib/python3.13/site-packages/livekit/agents/ipc/channel.py", line 47, in arecv_message
    return _read_message(await dplx.recv_bytes(), messages)
                         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.13/site-packages/livekit/agents/utils/aio/duplex_unix.py", line 35, in recv_bytes
    len_bytes = await self._reader.readexactly(4)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/streams.py", line 769, in readexactly
    await self._wait_for_data('readexactly')
  File "/usr/local/lib/python3.13/asyncio/streams.py", line 539, in _wait_for_data
    await self._waiter
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/.venv/lib/python3.13/site-packages/livekit/agents/ipc/supervised_proc.py", line 210, in initialize
    init_res = await asyncio.wait_for(
               ^^^^^^^^^^^^^^^^^^^^^^^
    ...<2 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 506, in wait_for
    async with timeouts.timeout(timeout):
               ~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

During handling of the above exception, another exception occurred:
i haven't seen these errors before, my guess it it's trying to load a massive model and timing out. looks like your image size is ~9GB
d
hmm, what does the image size need to be or stay under ? I am using hugging face embedding model for RAG, maybe that is the issue ? thanks
e
there are resource constraints on our free tier, you may have better luck on one of the higher tiers
d
aahh ok. ugh. ( any chance of complimentary higher tier for limited time to test, before I buy one) thanks
even for a day or two, it will help us decide between LK or self-managed for agent deployment strategy.
e
let me check