All Activity

I did some research on this a while back and it seems like there is some FreeSwitch config that needs to be added or changed but I ran out of time and haven't gone back to this yet.

I did ctrl+f to find "mos" and it didn't find it. But if you find this area and expand "inbound" and or "outbound" it will have MOS score in there.

If a user has several devices assigned to it, for example a hotel, a room can have more than one device all associated with the same user who has an extension assigned to them, which is what they call. Each device is registered with a username and a password and as a The guest calls internationally and is billed later. But for example, now with a sophone on my cell phone and a hotel Wi-Fi, I know the credentials of that device, I can register and make a call. What I want to avoid is that for security there is only one device registered and if it can be limited by IP or by Mac, much better. In the part of the callflow where it says device there is the mac option and in the SIP part authentication by IP but it doesn't work for me

depends on your use case I guess, clients can have mobile devices with SIP clients on them, or softphones on their laptops as they travel.

Yes, check that but there is no way that if you are already registered and someone else tries to register you will get an error or limit the registration to an IP or Mac of the device. I am asking to avoid identity theft because if you know the username and password you can register and use the permissions it has to call

KAZOO only tracks the latest registration for a given credential, so the most recent one will be used for call routing.

How to limit multiple device registration in kazoo with the same device or limit device registration by IP or by Mac

thanks

Good afternoon, I am trying to limit the amount of registration to a device to avoid fraud in kamailio, enable these ACL-ROLE roles RATE_LIMITER-ROLE When I try to register a device I get this logs in kamailio REGISTER:sec:2024/04/09_07_59_01 rate limits: 1 > -1)

Welcome, @Irshad! Excited to have you in our Kazoo community.

I am Irshad Rangari, working as a IVR developer in ALOHA Technology. New in Kazoo environment. Looking forward to dive deep into kazoo

Welcome aboard!

Hiya! Happy to see you here!

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.

Hello, This is Shane from ITVantix. We are new to the 2600Hrz community. We look forward to working with you guys.

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.

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.

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).

Welcome to the community @Alexis_Hover and we're thrilled to have you explore KAZOO as a potential second switch option.

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/

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.

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.

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)