Jump to content
KAZOOcon: hackathon signup and details here! ×

All Activity

This stream auto-updates

  1. Today
  2. Hiya! Happy to see you here!
  3. Hi, I'm a Software Developer at ServiceTitan. I've been a full stack developer for 10+ years and enjoy building end to end solutions with 3rd party providers. I'm excited to see what Kazoo has to offer for real time communication.
  4. Yesterday
  5. Hello, This is Shane from ITVantix. We are new to the 2600Hrz community. We look forward to working with you guys.
  6. Last week
  7. Welcome @Brisco Chris Excited to see your interest in our open-source evolution as well as paid support and for inquiries about paid options, please feel free to reach out to 2600Hz Sales at sales@2600Hz.com with any questions.
  8. I am here to see if the open source version continues to evolve as we would be interested in that with a paid support option for some of our clients.
  9. Earlier
  10. The situation was that marketing was done with Kazoocon and we didn't have official word that there'd be a 2024 Kazoocon, so they decommissioned the site. Word is, there will be a 2024 Kazoocon, so the site should be re-instated in the next day or two (whenever our ops team can turn it back up).
  11. Welcome to the community @Alexis_Hover and we're thrilled to have you explore KAZOO as a potential second switch option.
  12. Welcome to the community, @Paul M.! Your long experience with VoIP technologies will be a great asset as you navigate/explore to the world of Kazoo and for system administration, you can find a wealth of information over at 2600Hz documentation https://docs.2600hz.com/sysadmin/
  13. Hello, I am interested in KAZOO to see if it may be a fit to provide a second switch option for our customers with more product options.
  14. Hi, I'm Paul. I have worked with asterisk, freeswitch, kamailio, and opensips during my ten plus years in the VoIP industry. I'm currently looking for information on how to maintain, update, or even create new Kazoo clusters because I am currently working for a firm that currently has 2 different Kazoo cluster versions.
  15. I'm new to this product and would like to learn how to integrate additional apps like call center, CRM, and WS queue into my CentOS open-source installation. Could you provide guidance on this process?

    How can I install new applications on my CentOS 7 server?

    Do repositories exist for CentOS 9?

  16. Follow up on this. So I have Kazoo v4.3 installed on a Proxmox Home lab. Port forwarded necessary ports. Updated Freeswitch and Kamailio to advertise public IP. Successfully registered two extensions outside my network and established call between both. I'm however having issues registering from within my LAN. If I set outbound proxy to the Kazoo's internal IP address, phone registers successfully. Calls to that extension get sent to Voicemail immediately without ringing even though the phone is online. If I provide my public IP address (I've got a static public IP), the phone never registers. I don't see any register attempts from the phone. So my question is, is it possible to have a server where phones can register internally and externally and have both phones communicate? EDIT: So I may have spoken too early. Just did a test with one phone external to my LAN (A) calling a phone internal to my LAN (B). Calling B from A rings B. When I answer B, there's only one way audio from A to B. No Audio from B to A. A has outbound proxy set as my public IP, B has outbound proxy set as Kazoo's local internal IP. What should I be tweaking if any? I understand that in most production use case this isn't going to ever arise, but I've previously self-hosted 3CX where this did arise and was handled "flawlessly" by 3CX. Edit 2: Calling A from B and the call is getting hung up as soon as A answers. I see a BYE coming from Kaz.oo.Lan.IP:11000 to Phone A immediately A answers the call (+0.00503 seconds)
  17. ChatServ Messenger is excited to offer an exclusive opportunity for all 2600Hz service providers: Get a FREE ChatServ Messenger (SMS/MMS Texting) account for up to two (2) users. No purchase necessary. No credit card needed. Unlock advanced messaging features that perfectly integrate with 2600Hz. This free offer is a doorway to exploring how our platform can enhance your messaging strategies. It’s your chance to test drive our features and see if upgrading to a Channel Partner could be the game-changer you’ve been looking for! Rest assured, your account remains complimentary, with or without upgrading. Ready to Transform Your Messaging? We knew you would be! Reach out to our support team or click on the link below to apply for your free ChatServ Messenger account. Let’s embark on a journey to revolutionize your messaging practices together! 🔗 Need Help? Contact Support: support@fastdevice.net 📝 Sign Up Now: https://form.jotform.com/240713536303044 🕒 Limited Time Offer: Don’t miss out on this exclusive opportunity. Join the growing community of ChatServ users and upgrade your messaging today! We also support Private Cloud and "Bring Your Own Carrier." Contact our support email for more details. Best regards, ChatServ Messenger
  18. Looks like someone deleted the whole site
  19. @mc_ thanks for the response. Someone from here reached out to me and advised I check that hostname and realm are completely different. Followed that advice and I am now able to make extension to extension calls successfully. If I had to look at the Kazoo logs, where would they be located? TIA airsay
  20. You're correct that Kamailio interacts with KAZOO via AMQP, does not contact CouchDB, and does use sqlite for local storage stuff. Kamailio is part of the "cluster" because of the AMQP connection. I can't speak to the packaging issues though. The process to open sourcing Kazoo5 work continues to wind through the appropriate channels; should resolve so many of these issues. Apologies for the frustrations in the mean time.
  21. The KAZOO logs will probably be more helpful. Check that you're logging at debug level, place the call, then you can use the call ID to search the logs for what kazoo tried
  22. Checking on the site, shouldn't be down. Thanks for the alert
  23. The entire site is gone. It seems they are trying their best to kill off the 2600Hz / Kazoo brand. It's not a joke. All the KazooCon videos are all "unlisted" on YouTube, and that is why I referenced the site instead of all the videos shown on there. Why else would they keep all the videos unlisted, and kill the whole site? Or, it could be the site was compromised?
  24. Hello , Any advise on this?
  25. Hey there, I took a shot at getting this to work on the front end. I was able to create a call flow element using the documentation listed below. I was able to get the call to route to the ON_VOICE side but all faxes failed to detect the fax tone and routed to the voice side. After looking at the backend logs it failed to detect the fax.
  26. After a bit more research and digging into the kamailio-db-kazoo-5.0.4h-4.1.x86_64.rpm archive it appears that there is an executable /usr/bin/KazooDB which is just .. sqlite3? Maybe the question I really should be asking is what is the recommended configuration for the Kamailio database? In a cluster is this shared and potentially a single point of failure or can I set them up independently? I can't find any documentation on it, the cluster guide at https://docs.2600hz.com/sysadmin/doc/kazoo/cluster-guide/ doesn't mention it so I assume it's just using the sqlite3 database locally on each machine set up, is this correct? Sorry, for some reason I assumed the kazoo db connector was using couchdb for some reason, just trying to understand the pieces. If anyone can shed some light we'd appreciate it!
  27. We are working on building the last known good (4.3) branch with updated versions of dependencies (the last RPMs we can find for Kamailio from 2600hz are 5.0 from almost 7 years ago now). We've got almost everything running but we have run into a roadblock: the file in the kazoo-configs-kamailio project here: https://github.com/2600hz/kazoo-configs-kamailio/blob/4.3/kamailio/db_kazoo.cfg references a db_kazoo.so module (apparently to query Kazoo via AMQP?) We found an old thread from 2014 that talks about this module here: https://groups.google.com/g/2600hz-dev/c/c7gk5VTtWWM that references a repo https://github.com/2600hz/kazoo-kamailio that no longer exists but I found archives here: https://github.com/2600hz-archive/kazoo-kamailio. This appears to be the name of the original AMQP connector that was renamed but then from the RPMs it looks like there are two separate modules: https://packages.2600hz.com/centos/6/stable/kamailio-mirror/5.0.4h/ but we really need to be on a newer supported version of Kamailio (there have been numerous vulnerabilities reported in the published versions: https://www.cvedetails.com/vulnerability-list/vendor_id-15820/product_id-33634/Kamailio-Kamailio.html) There was another clue in this APK build script: https://github.com/lazedo/kamailio-docker-alpine/blob/master/APKBUILD but that points to https://github.com/2600hz/kamailio-db-kazoo/archive/0.1.2.tar.gz which is a project that no longer exists. This is where I currently am, wondering if this module is gone forever. Can anyone point me in the direction of the source for the db_kazoo.so module for Kamailio? I'm fine with it being a potentially outdated version that needs some love but I can't find anything as it stands. Thanks!
  28. You're welcome! I'm glad I could assist you.
  1. Load more activity
×
×
  • Create New...