This message was deleted.
# ask-ais
steep-balloon-41261
05/23/2026, 9:31 AMThis message was deleted.
✅ 1
t
tall-airline-16756
05/23/2026, 9:31 AMThanks for reaching out, Rajadurai. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
05/23/2026, 9:32 AMThanks — I’m sorry you’re seeing that. I’ll help troubleshoot why enabling
wait_until_answeredwait_until_answered=truewait_until_answered=truel
little-king-41579
05/23/2026, 9:37 AMLiveKit is sending a CANCEL.when
wait_until_answered=truet
tall-airline-16756
05/23/2026, 9:37 AMThanks — that’s a useful datapoint. I’ll help diagnose why LiveKit sends a CANCEL when
wait_until_answered=truewait_until_answered=falsel
little-king-41579
05/23/2026, 9:38 AMcommand to check the server
t
tall-airline-16756
05/23/2026, 9:39 AMThanks — I’ll help. Below are quick commands to check your LiveKit server status and collect logs so we can see why it sends a CANCEL when
wait_until_answered=true Copy code
systemctl status docker.livekit-server@v0.13.service Copy code
# If using the service above
journalctl -u docker.livekit-server@v0.13.service -n 200 --no-pager
# Or if running as a Docker container
docker ps --filter "name=livekit"
docker logs --tail 200 <container_id_or_name> Copy code
# If binary installed
livekit-server --version
# If container
docker exec -it <container_id_or_name> livekit-server --version Copy code
kubectl get pods -l app=livekit -n <namespace>
kubectl logs -l app=livekit -n <namespace> --tail=200l
little-king-41579
05/23/2026, 9:43 AMcommand to fet SIP server version running in docker container
t
tall-airline-16756
05/23/2026, 9:43 AMTo get the SIP server version from a Docker container, run one of these (depending on how the image exposes the binary):
1. If you know the container name or ID:
Copy code
docker exec -it <container_name_or_id> <sip_binary> --versionasteriskdocker exec -it <container> asterisk -Vasterisk --versionkamailiodocker exec -it <container> kamailio -vopensipsdocker exec -it <container> opensips -Vfreeswitchdocker exec -it <container> freeswitch --version Copy code
2. If you’re not sure which binary is present, open a shell and check:
```bash
docker exec -it <container_name_or_id> /bin/sh
# or
docker exec -it <container_name_or_id> /bin/bash
# then inside the container:
ps aux | grep -E 'asterisk|kamailio|opensips|freeswitch'
which asterisk || which kamailio || which opensips || which freeswitch Copy code
docker inspect --format='{{.Config.Image}}' <container_name_or_id>
docker images --filter=reference='<image_name>*'tall-airline-16756
05/23/2026, 9:52 AMThanks — good info. I’ll help narrow this down so we can find why LiveKit sends a CANCEL when
wait_until_answered=true Copy code
# increase logging level (if running as container)
docker exec -it <livekit_container> livekit-server --log-level debug
# collect recent logs
docker logs --tail 500 <livekit_container> > livekit_logs.txt Copy code
journalctl -u docker.livekit-server@v0.13.service --no-pager -n 500 > livekit_journal.txt
# or container logs
docker logs --tail 500 <livekit_container> > livekit_sip_logs.txt Copy code
# enter container
docker exec -it <sip_container> /bin/bash
# Asterisk real-time trace
asterisk -rvv
# then in asterisk CLI:
sip set debug on # (chan_sip) or
pjsip set logger on # (pjsip)
# Kamailio/OpenSIPS: enable pcap or siptrace module logs and export the trace around the call timestampwait_until_answered=false2 Views