Hello, I have deployed the LiveKit server and SIP server on an AWS instance. After creating inbound and dispatch rules using the LiveKit CLI, I noticed that both rules are automatically removed after some time. Can anyone help me understand how to make these rules persistent? if you need any information , you can ask me

Thanks for reaching out, Satyam. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c6e1edd23f90 redis:7-alpine "docker-entrypoint.s…" 11 days ago Up 11 days 0.0.0.0:6379->6379/tcp, [:]6379->6379/tcp livekit-redis

It looks like your Redis instance is up and running smoothly—great start! To make sure everything connects properly and your rules stick around, let’s double-check a few things together: • First, please verify that the Redis configuration in your LiveKit SIP service is pointing to the right Redis instance. The

redis.address

field should match your Redis server and port (something like

localhost:6379

). • If your Redis setup requires authentication, double-check that the

username

and

password

fields are correctly filled out in your SIP service configuration. • For those using Docker, it’s important to confirm that Redis is set up to accept external connections. You might need to adjust the Redis config by commenting out

bind 127.0.0.1

and setting

protected-mode no

if that’s the case. • Take a peek at your SIP service logs for any Redis connectivity messages, like

ErrSIPNotConnected

. These can give us clues if something’s not quite connecting right. • Finally, you can run the CLI commands

lk sip inbound list

and

lk sip dispatch list

to see if your rules are being stored and fetched as expected. If you run into any specific errors or want a hand with any of these steps, just let me know—I’m here to help! Sources: README.md | redis/redis.go | pkg/service/redisstore_sip_test.go

this is my sip config api_key: devkey api_secret: secret ws_url: ws://localhost:7880 redis: address: localhost:6379 log_level: debug sip_port: 5060 rtp_port: 10000-20000 use_external_ip: true this is my server config # LiveKit Server Configuration for ai.billtrax.online # Server settings port: 7880 bind_addresses: ["0.0.0.0"] # API keys (these should match your SIP config) keys: devkey: secret # WebRTC settings rtc: tcp_port: 7881 port_range_start: 50000 port_range_end: 60000 use_external_ip: true # Redis configuration redis: address: localhost:6379 # Room settings room: max_participants: 100 empty_timeout: 300 departure_timeout: 20 # SSL/TLS Configuration turn: enabled: true tls_port: 443 # udp_port: 443 domain: ai.billtrax.online cert_file: /etc/ssl/certs/ai.billtrax.online.crt key_file: /etc/ssl/private/ai.billtrax.online.key # Logging log_level: debug # Development settings development: true

I don't have the answer you're looking for. You could also try asking your question: • in one of the other Slack channels or • to https://deepwiki.com/livekit/livekit_composite which is trained on all LiveKit source code If you find the answer, please post it here to help others!

These are my config file used to setup the server , are there any issue in this ?

Hey @lemon-address-29869, I’m having the same issue with inbound and dispatch rules disappearing after some time. Have you managed to find a solution for this? Thanks!