Matt Florell

@AxelHuizinga @OmidMohajerani We've done some basic testing with Asterisk 20 and had no issues, but no robust testing at this point like we've done with Asterisk 18. For Asterisk 22, we needed to have ConfBridge, PJSIP and full MixMonitor use, and we have completed all 3 of these projects, so it should work.

@vicidial_dev @OmidMohajerani How is the current compatibility status - can we use vicidial with Asterisk 22 now?

The end of the Meetme era is at hand. One of the most stable modules in Asterisk's history will be gone soon ☹️

Today is Tuesday, August 5th 2025. I just got a robo-call from an "AI Agent". I asked it what day of the week it was, and it confidently told me it was Friday. This is supposed to be the future?

Open source fights back: 'We won't get patent-trolled again' Businesses using open-source projects like Kubernetes are being targeted more often by patent trolls. Now the open source community is launching a counter-offensive and looking for volunteers. zdnet.com/article/open-s…

We rewrote our STIR/SHAKEN implementation in #Asterisk! Read more at asterisk.org/asterisk-stir-…

Check out the latest article from HostingAdvice.com about #VICIdial and the latest features that we've added to it! hostingadvice.com/blog/vicidial-…

Join us Tuesday, August 15th @ 11am EDT for a webinar about VICIdial's integration with the @khomptechnology Khomp Analytics AMD solution: conteudo.khomp.com/web-amd-vicidi…

ViciBox v.11.0.1 released Aug 6th 2023, vicidial.org/VICIDIALforum/… Includes fixes to previous version and documentation updates.

@onegreenparker #2: It's pronounced "Vee Chee Dial" But, we've heard them all, and it's a pretty unique name so the pronunciation doesn't matter that much :)

@vicidial_dev Please help settle an argument in our office; the correct pronunciation of VICIdial: 1) Vee See Dial 2) Vee Chee Dial 3) Vicky Dial 😳

New VICIbox 11.0 ISO installer released! (Based on OpenSuSE Leap 15.5) Now with better documentation website! vicidial.org/VICIDIALforum/…

We've also added a new VICIbox documentation website that is easier to browse and update, vicibox.com/docs/

Here's the roadmap for VICIbox 11 development, some key elements: - Based on OpenSuSE 15.5 - Defaults to Asterisk 16.30.0 - Many package updates and changes vicidial.org/VICIDIALforum/…

For all the beta-testers out there, VICIbox 11.0 beta is released! vicidial.org/VICIDIALforum/…

@CarpeNox2 There was an issue in svn/trunk 3731 with this, it was resolved in 3732 committed last night.

@vicidial_dev I'm on SVN 3731 and I don't see this option available to select

Added List Weekday Resets, allowing for automatic list resets scheduled by day-of-the-week on a per-list basis.

Added "Inbound Calls Credits" function, allowing per-User setting of a number of inbound calls that can be handled, until reset by a manager. Also add User Inbound Calls Today page to show current inbound calls/limits/credits for users.

Added "Demographic Quotas" features, used for surveys/polls to efficiently meet goals for contacting people by specific demographic parameters(age-group, gender, location, etc...) vicidial.org/docs/DEMOGRAPH…

For more information on how Agent Latency logging and the new Latency Gaps functions work, take a look at the Agent Screen Logging document, vicidial.org/docs/AGENT_SCR…

Added Agent Latency Report with zoomable graphs, as well as a new Agent Latency Gaps report. Latency Gaps can also send immediate and day-end emails when Agent Screen connection gaps occur.

@geilt Very interesting! We'll have to look into changing that in the codebase going forward after doing some more testing. Could you please post your changes to the Issue Tracker? :)

We found an issue where IAX would randomly fail on larger clusters and the solution was to fix the IP instead of dynamic. It would even lose connection to ASTPlay over local. With dynamic the IP would show null IP as a peer and only fix was restart asterisk. However if you fixed IP and reloaded iax2 you could recover without losing calls. It would cause audio issues and drop calls when this happened. So on an 8 server cluster 7 couldn’t see 1 but 1 could see all 7 when this happened almost like an internal asterisk issue. Ping and trace route all still worked. Modified keep alive script to auto insert the local IP of the server. Also hard coded ASTPlay loop and monitor to 127.0.0.1 for further stability as it would randomly ping 500ms then back to 3. Now everything is at 1ms or lower and the audio issues stopped. Nightmare to debug. It’s asterisk 13 though so may not be an issue on 16.

@vicidial_dev Would you happen to know why ASTplay, blind and loop often have higher IAX Peer latency than cluster servers on different machines in the network, considering they are localhost essentially?