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

All Activity

This stream auto-updates

  1. Last week
  2. 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)
  3. 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
  4. Earlier
  5. Looks like someone deleted the whole site
  6. @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
  7. 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.
  8. 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
  9. Checking on the site, shouldn't be down. Thanks for the alert
  10. 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?
  11. Hello , Any advise on this?
  12. 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.
  13. 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!
  14. 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!
  15. You're welcome! I'm glad I could assist you.
  16. So after running into issues in November 2023 trying to spin up a Kazoo, I eventually got around to successfully installing one yesterday in my home-lab on Proxmox 8.1 Centos 7 VM. Created two users, A & B assigned to extensions 101 & 102 respectively. Created devices (with auto generated usernames and passwords) and assigned these devices to A & B. Downloaded Microsip and successfully registered both users on separate instances of Microsip. I had also installed sngrep on Centos. I can see both extensions registered. But when I call 101 from 102 and vice versa, I just get routed to the unavailable voicemail greeting and dropped into voicemail of the called extension. Examining the pcap, I see a 503 - Maximum calls in progress error between Kazoo (freeswitch?) and the called party. Any advice or suggestions on what I am doing incorrectly? I have attached pcpa of the sample call. TIA airsay kazoo-test-call.pcap
  17. @Ramen thank you for taking time out to attend to this. Deeply appreciated.
  18. Hey @airsay just got information back from the Support Manager and, sorry to say, the Kazoo Technical Support role is only open to U.S. full-time employees at the moment.
  19. @airsay I'm not certain about the specifics for the Kazoo Technical Support role, especially regarding its status as a 1099 Independent Contractor position. Let me reach out to the Support Manager for more details/information.
  20. Hi Test @Gabriela 😅 welcome to the forums and community.
  21. @mc_ and anyone willing to advise. so I'm trying to "bury" this question which is why I'm asking here. Over here and here I see 2600Hz/Ooma are looking to hire a Kazoo Technical Support. I'm interested in this role as it allows me an opportunity for career growth. I was wondering or rather looking to find out if that role is exclusively a US FTE role. I'd be happy to work that role as a 1099 Independent Contractor if there's the possibility that 2600Hz would be remotely interested in that
  22. Check with Doodle kazoo app : sup kapps_controller start_app doodle.
  23. Good afternoon, I am using kazoo to host pbx in the cloud but I need to know if kazoo supports SIP messaging between internal devices. I enabled the message module in kamailio and the messages arrive but they are not routed, that is an example |msg|sending inbound message sms.inbound.onnet.1c683a699c8c40c497c59bf8f5364502 => {"Event-Category" : "sms", "Event-Name" : "inbound", "Call-ID" : "1c683a699c8c40c497c59bf8f5364502", "Message-ID" : "1c683a699c8c40c497c59bf8f5364502", "Route-Type" : "onnet", "Route-ID" : "kamailio%40prueba%2prueba%2Enet", "From" : "1000", "To" : "5000", "Body" : "aasasas", "Custom-SIP-Headers" : { "X-AUTH-IP" : "10.61.59.18" , "X-AUTH-PORT" : "61694" , "X-AUTH-Token" : "ba151056b5abc9d574792ca680782d73@abd575504fb9ff00681875bceee3ddb8" , "X-ecallmgr_Account-ID" : "abd575504fb9ff00681875bceee3ddb8" , "X-ecallmgr_Authorizing-Type" : "device" , "X-ecallmgr_Authorizing-ID" : "ba151056b5abc9d574792ca680782d73" , "X-ecallmgr_Username" : "1000" , "X-ecallmgr_Realm" : "prueba1.prueba.net" , "X-ecallmgr_Account-Realm" : "prueba1.prueba.net" , "X-ecallmgr_Account-Name" : "Prueba" , "X-ecallmgr_Presence-ID" : "1000@prueba1.prueba.net" , "X-ecallmgr_Owner-ID" : "a41652aff952a2e9f4e176cae3c84f96" }, "Msg-ID" : "507b581b-b6a4-4d5b-9acc-d0a8d9ee1bc3"}
  24. Hi all, A while ago I wrote an app for Kazoo 4.3 to view and play recordings. You can also manage some recordings settings there too. I wanted a recordings app that matched the look and feel of the rest of the Kazoo UI and that could paginate on the server instead of loading all the recordings then filtering client side. Anyway, I forgot all about it until recently. Please enjoy! https://github.com/bpbp-boop/monster-ui-recordings-community/blob/main/README.md
  25. Looking forward to both the new version and the marketplace. Happy to pay for apps for our customers.
  1. Load more activity
×
×
  • Create New...