Skip to main content

No Calls Are Starting

Check:
  • Current time is within CALL_HOURS_START and CALL_HOURS_END.
  • Current weekday is in CALL_ALLOWED_WEEKDAYS.
  • Lead status is new.
  • retry_after is empty or in the past.
  • MAX_CONCURRENT_CALLS is not blocked by stuck calling rows.
  • CALL_WHITELIST_NUMBERS is empty or includes the test number.
Useful SQL:

SIP Call Fails To Start

Check:
  • LIVEKIT_SIP_TRUNK_ID is set.
  • The ID is an outbound trunk ID, not inbound.
  • VOBIZ_SIP_DOMAIN, VOBIZ_SIP_USERNAME, and VOBIZ_SIP_PASSWORD are correct.
  • VOBIZ_PHONE_NUMBER is valid E.164.
  • Target phone normalizes to +91XXXXXXXXXX.
Run:

Invalid Phone Numbers

The scheduler rejects numbers that cannot safely become Indian E.164 mobile numbers. Accepted examples:
Rejected examples:

Calls Stuck In calling

The scheduler automatically fails stale calls older than:
Manual inspection:

Agent Does Not Join The Room

Check:
  • The correct agent process is running.
  • Room name starts with ignitech-lead-.
  • SIP participant identity starts with sip-lead-.
  • LiveKit credentials match the same project where SIP is configured.
  • The agent can connect to PostgreSQL using DATABASE_URL.

Talking Shops Push Fails

Check:
  • TALKINGSHOPS_API_URL
  • TALKINGSHOPS_API_KEY
  • TALKINGSHOPS_AUTH_HEADER
  • Optional TALKINGSHOPS_AUTH_PREFIX
  • Customer endpoint derivation or TALKINGSHOPS_CUSTOMERS_API_URL
For safe testing:
If you want failed pushes to retry later:

Database Connection Errors

Check:
  • DATABASE_URL is set.
  • PostgreSQL is running.
  • Docker uses host db, local runs usually use localhost.
  • The database user has permission to create tables and triggers.
Initialize:

LiveKit/WebRTC Runtime Panic

If a native WebRTC error appears after dependency or environment changes, recreate the virtual environment:
Then run with extra logs:

Qualification Is Empty

Likely causes:
  • Lead rejected or hung up before answering.
  • Audio did not reach the agent.
  • The call ended before extraction.
  • Model credentials are missing.
  • Transcript was too short.
Check the calls.failure_reason and agent logs.