Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/17/2017 in all areas

  1. 2 points
    Excellent job organizing and executing this event. It was worth the time to attend! We learned a lot and made some excellent contacts within the Kazoo community. Will the presentation material be made available to the attendees? There was a lot of good information presented and some of it came faster than my note taking skills could capture.
  2. 2 points
    Hi"! Well as i am a captain by profession and do this to learn it sometimes goes over my head )) meaning that if a problem becomes more complex, and lets say has mmore then three or four levels, i get lost. I cant see the big picture anymore. So thats why im a good fir for writing simple docs, but in a workflow kind a way. Per example: Here is how to acieve this step: 1. do this 2. and that because of this or that 3. etc U can see the style in here, here, here and here. I remember that one of the sad things was, that at that time the idea of dealing with docs in a different way was new and just being pushed a bit. But for some things i needed help, and it was not available. of course, being naive and enthausiastic u want to move more fast then what is posible sometimes. And expected a bit too much from 2600hz perhaps, but... now i see this new forum, a lot of new faces and feel some more energy here )).
  3. 1 point
    Cool! Is it possible to add the intercom key type option to SmartPBX as well?
  4. 1 point
    Hi All, Is it possible to use Kazoo as an Application Server for IP-Multimedia Subsystem (IMS) environment? Maybe someone has some experience/references of integration Kazoo/Kamalio/Freeswitch with IMS core? Regards, Mikhail
  5. 1 point
  6. 1 point
    Super duper admin is the primary account you create and all it's users, by default. It gets created with your first account automatically. For bulk import of numbers, you can bulk import numbers with the CSV Jobs app I believe. For "No, I don't think so? What I mean is a simple sip account, i.e. a telephone number user/pass with a credit limit. so that an end user i.e. Joe Homeuser can purchase a phone and a $10 monthly service, but has no PBX attached from his perspective. " I think what you're saying is you want to create accounts with just one phone/user in them and then have limits in them, like a calling card service or home phone service. This is possible but there's no "one button push" to do it. Everything is API based though so you could make your own app to do it.
  7. 1 point
    Hi there! Thanks for trying out Kazoo! Lots of questions indeed. Let me try to answer each, below... We are looking for assistance on the documentation side, if you are interested in helping out, please let us know! So actually the rating stuff is kind of generic and you can use any currency you like, but we hardcoded US in the UI for now. So you would just have to change that. We don't deal with tax right now, and the billing engine is kind of archaic and is due a re-write. I would recommend using only the limits and per-minute rate tracking features and overriding the UI to put in your own currency. We would welcome contributions to make the currency dynamic, we just haven't had the time to do it. Like a single install? Just remove accounts manager from the apps list and it's a standalone PBX if that's what you mean. We have some more open-source apps coming out soon but not yet. The provisioner / carrier manager / dialplan apps are currently closed source. Please contact sales@2600hz.com for those. There is a blacklist application that I believe is released open-source. You can use that. Thanks! Go into the Futon database and go into the accounts DB. Delete the bogus account. Also, drop the databases for the bogus account as well. Then you should be good to go.
  8. 1 point
    Hello everyone, Today at 4:00 PM we ran into configuration issues with our forum software that resulted in data loss. The good news is that we're up and running. The bad news is that we had to restore from backups which were around 20 hours old. We meant to put kittens in your Holiday Stockings, but we accidentally left you coal. We are so embarrassed. Our community is extremely important to us and we're very sorry if you lost any postings or private messages due to this outage. This was entirely our fault, and we'll review our processes to see if there are additional safeguards or protocols that we can take to prevent this from happening again in the future. If you have any questions, please reach out to us on the forums or at community@2600hz.com. Regards, Bret Truchan Internal Systems Engineer
  9. 1 point
    The old posts are too hard to merge back into the restored community, so they are lost. You will need to re-post your content if you still have an open question/comment I'm afraid.
  10. 1 point
    Kazoo does the same thing as the carriers. If you try create an IP auth device in callflow and then try create another IP auth device with the same IP (even if it is in a different account), Kazoo will give you a "SIP IP already in use" error. Kazoo does not care about inbound IP from carriers as long as the IP is added to the ACL. It knows which account to route the call to based on the DID number. So again, that is the same as what most carriers seem to do.
  11. 1 point
    Thats true, one could sent a 1. specific header (or how we call that, flag?), depending if the carrier allows it of course. 2. Add an ip to your system and ask a Kazoo guru to explain how to force that ip to be used for this specific account. Inbound is no issue, but if Kazoo allows IP auth, and customers can bring their own carrier, then the risk is rather high to have duplicate ip adresses. If not 100% guarunteed. If u have 1000 clients, this problem will exist. U could do smth with outbound CLI but that also depends on the provider and could be spoofed. I dont know how Kazoo handles this, but my brain does not see a solution other then stated
  12. 1 point
    Thank you Bobby for the referral for Judy at Telecom Professionals, Inc.
  13. 1 point
    @mc_ - you beat me to it! Based on conversations I've had about our own scalability, Kamailio servers support between 25-50K devices per box. This number varies based on BLF subscriptions and SIP timers such as keep-alive OPTION messages, REGISTERs, and general call volume. Kamailio is cluster-able, so with the use of SRV records, you can spread the devices out across many servers. I suggest doing N+1 to ensure that if a single server or zone goes down, the remaining infrastructure can take on the rest of the load. FreeSWITCH scaling is more reliant on usage data in calls per second, and whether certain features are turned on like video, encryption, etc. I'm not sure I agree with James on the 'lots' of growing pains, but as mentioned, in every deployment there are different use-cases and potential ceilings that have never been hit before. The one thing I can say is that 2600 has addressed every issue we're ever had with scaling very professionally and prioritized based on any customer impact.
  14. 1 point
    Hi, we're a small startup hosting PBX for our clients and we are looking into Kazoo for our VOIP needs. So, what we need to know is: 1- Will a self hosted Kazoo install have the same benefits of your SaaS? 2- Does Kazoo do LCR, Rating, Billing, Accounting in one or more of it's apps? If not, how hard could it be to implement these functions on Monster UI or externally? 3- Is it possible to acquire the closed/non-public apps on our self hosted installation? 4- What is needed to localize Monster UI and the dial prompts to our language? In any case, we could PR back our changes to 2600hz. Thanks.
  15. 1 point
  16. 1 point

    until

    Too bad it's going to be fully online, I was looking forward to meeting other users face to face and shaking hands...
×