Search results

Here is a script to remove stale calls if you are using SQLite Install sqlite3 apt install sqlite3 Create a cron job to run every 30 minutes. #!/usr/bin/env sh #default location sqlite3 /var/lib/freeswitch/db/core.db "delete from channels where strftime('%s','now') - created_epoch > 14400;"...

I found your issue. Calls with lower priority joined the queue later than those with priority 53. Here is how I figured it out Call 2a3aa62b-40d0-480f-b342-93e1acf0e8ef Score 5 system_epoch Thursday, June 6, 2024 11:55:16 AM joined_epoch Thursday, June 6, 2024 11:55:53 AM Call...

A screenshot of your queue settings

I'm happy to share some info here to help you out. If you need further assistance, feel free to DM me for more personalized support.

Yeah, I get that. Your only other option is to run a script every so often to remove the stale calls. It's not perfect, but it will work. Say you run a script every 30 minutes and delete calls older than 4 hours. You will have a BLF issue until the call is removed, but at least it's automated.

Can you downgrade to 1.10.7? I have customers who use this version in production, and they have no stale calls. I also heard that the bug was noticed all the way in 10.10.9 version. Freeswitch developers have had a ticket open for years; they are well aware but not doing much to fix it.

You can add streams to the dialplan

If you use Ringotel for your mobile apps there is a built-in feature now to flip calls between user apps.

It's possible to do for sure. However, it will require a lot of custom development.

How are you updating the status?

Have you restarted the sip profiles and/or FreeSWITCH after you set it all up. I've seen instances where the entire server needed to be rebooted after initial installation.

I have seen both statuses and never found any issues with any. My opinion Is it depends on the manufacturer of the device. I might be wrong though

I have used Ringotel for two years now. There are some issues sometimes, but they seem to fix them if you open a ticket. I've implemented SMS via integrations and API. Both have cons and pros. The price is cost-efficient, but if I find a true WebRTC replacement, I might go with it. Otherwise we...

I'm cautious with upgrades these days. I'm still on version 5.1.3 with some customizations. I can confirm that my version doesn't have this issue.

Restart is the only way I found that works 100%. Some stale calls cannot be killed easily. Are you on the 1.10.11 version?

Send screenshots of your set up

I'm curious if this happens when CDR upload via the HTTP server is not used. Does someone have CDR upload set up and still have stale calls?

It's broken in 5.1.3. I confirmed on my system

Hi All, I want to pick your brains. I have 2 redundant servers in active-passive mode. Ideally, when one goes offline, the other one should handle the calls. I use Polycom phones, and they have a dual registration setup. Most of the time, all of this works as expected until I reboot the main...

Is there an actual solution for this? Have the same issue.