amn

Are you logged in as the top (superduper) user in master account? You should see "+Add" option in Number Manager but I believe you only see that if you are superadmin or superduper. If it says invalid credentials then there is (obviously) something wrong with your credentials. Make sure you are generating a hash using the proper user/pass. That screen shot is not telling me anything. It looks like you are missing all the important bits at the beginning such as the generation of the user hash etc and then the actual curl command.

Not sure what you mean by not being able to add numbers. I just went to Number Manager > +Add and was able to add a number. To read about the API you can use these docs https://github.com/2600hz/kazoo/tree/master/applications/crossbar/doc Maybe start here for credentials https://docs.2600hz.com/sysadmin/doc/install/configure_kazoo/ https://github.com/2600hz/kazoo/blob/master/applications/crossbar/doc/basic_auth.md You will probably want to look at using PostMan which can automate a lot of the things such as using credentials. https://docs.2600hz.com/ui/docs/using-postman-as-a-crud/

Those wiki pages are still what come up to the top most often on Google. Not sure what the best solution is because I don't think github pages get the same SEO love from Google. That new documentation system you guys are using also does not seem to show up much on Google searches. Maybe it just needs a little SEO applied to it?

Is this a common feature on other VM systems?

Just FYI, 2600hz posted CouchDB config files. https://github.com/2600hz/kazoo-configs-couchdb

Does the number not show up in the GUI in Voicemail Manager? I realize that what you are asking for is a voice prompt but having it in the GUI should make that need less important.

/nodes is accessed via port 5986 (or 15986 if you are going through HAProxy). So from a web browser http://CouchDB_IP_Address:5986/nodes to access it via the Fauxton web interface. That is assuming Fauxton is configured to also access 5986 by default as it is 5984. I don't have an CouchDB install in front of me to check that. If it is locked down you will need to know the user/pass for access. I believe you can also do it from CURL similar to the examples they give for front end configuration.

Maybe DISA? https://2600hz.atlassian.net/wiki/spaces/docs/pages/11206689/DISA Only thing I am not sure about is if the system can be made aware of what extension you want to masquerading as. If you can masquerade as an extension, then you should be able to use feature codes. If you are using IVR there might be a way to do it through that as well. Call-Forward Update Call-Forward *56 Enable Call-Forward *72 Disable Call-Forward *73 Toggle Call-Forward *74

I would be interested in your configs that are different from bigcouch. Looks to be almost the same except for zones. There is just one comment by the developer with one example but not explained in much detail.

I think the VPN provider business probably got a boost.

I am trying to do something with http bookkeeper in combination with service plans and the API. If there is a completely generic solution coming I might have to wait and see what that is all about.

I believe you would go to Apps > App Exchange and set all apps to Admin only and set Voicemail Manager and Fax Manager apps to All users.

The billing stuff in Monster UI is designed for connecting to braintree and requires other things to be set up get that part working. Braintree module does not run by default and you also need to add your braintree API. I believe you also need to do things on the braintree end like create service plans. So most of those billing related things you see in Monster UI are there for use by 2600hz and anyone else who wants to set up all the braintree stuff with their own braintree account. If you are not going to use braintree you cannot use most of the billing things in Monster UI and need to develop those things yourself.

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.

If using IP authentication, the carrier is associating the IP with the customer account on their end. So on the carrier end, you cannot have more than one customer account with that carrier using the same IP. Otherwise the carrier would not know who to bill. That is for termination (outbound calls to the carrier). For origination (DID inbound) I am not sure if it would be a problem or not since the carrier knows which customers are using which DID's and should not care what IPs they are assigned to.

I am only talking about reseller accounts with their own carriers. Not offnet/global. Yes it's my own cluster.

Also number of cores used I think. Kazoo runs multiple beams (Erlang VMs) corresponding to the different applications and each beam can run on its own core. So Kazoo loves lots of cores. Even if half are hyperthreaded I think it still helps a lot.

How are people handling bring your own carriers? Some carriers only do IP authentication and as far as I can tell, IP authentication won't work for bring your own carrier because the carrier only allows the IP to be used once. Or am I missing something? Also, the carrier would need to be registered to each Freeswitch server used for outbound correct? How should I do that? I think for inbound I should just be able to add the Carrier IP to the ACL right? Any other gotcha's I need to be aware of for bring your own carrier?

Maybe I am giving most customers too much credit . I guess it kind of depends on what kind of customer you are going for . Be that as it may, restricting in the token will accomplish everything you need to. UI will probably just throw an error.

Keep in mind that removing the ability from the UI does not remove the ability from the API. Anyone who has access to the UI will also have full access to the API. So it is better to try restrict the API using token restrictions. Not sure if that is possible or not in token restrictions. https://github.com/2600hz/kazoo/blob/master/applications/crossbar/doc/token_restrictions.md

Verizon is a phone company. Comcast is also now a phone company. I think it's pretty safe to say that a phone company is going to want to target VoIP. I might be in favor of getting rid of neutrality rules if telecoms agreed to stop defending their monopolies. That is never going to happen. They have fought Google every step of the way during the rollout of Google Fiber. Sounds like Google has basically given up now.

Pretty sure most ISPs can do deep packet inspection. So they can determine the type of traffic without looking at ports. It would also be trivial to block or slow down traffic to certain IP's. So they could very easily block or de-prioritize all of 2600hz's hosted VoIP traffic, for example. The only possible workaround I can see is using VPN's. That comes with its own headaches and will degrade quality. ISP's can target those as well just like Netflix and other companies currently do. If you want to know more about what they can do, take a look at products they already own. https://www.sandvine.com/

I think it could be the death of VoIP as we know it. I am pretty sure Comcast already throttles VoIP traffic in some locations depending on how busy the internet is. At least for residential customers. They never admit it and I don't think their support people even know about it. They won't even bother asking for payment for a faster lane or anything like that because it competes directly with their services. So I think VoIP will be the worst case scenario when net neutrality goes away.

This post further up + the next post right after is what everyone needs to get started. That automates the important first step of creating the token. Can't do anything else until you do that and it's not very practical to try do it manually. Should be a sticky or added to the 2600hz documentation.

The most useful feature in PostMan is variables imo. I don't really like how they did it. Not very intuitive. But very powerful feature. Here is a blog post on PostMan variables. http://blog.getpostman.com/2014/02/20/using-variables-inside-postman-and-collection-runner/