bevenky

Yes we already support SRTP and TLS. I have no specific inputs about any specific providers but check out what makes us different here:

http://www2.plivo.com/zentrunk.html#quality

There is a form for beta access at the end of the page. Sign up there and we will get you setup.

Founder of Plivo here.

Zentrunk is our SIP Trunking service that provides you global coverage for making and receiving outbound and inbound voice calls using your current cloud or on-premise communications infrastructure (FreeSWITCH, Asterisk, Cisco Call manager, Microsoft Lync, Skype for Business etc.).

Whether you’re looking to add a high capacity carrier that can support your growth, or increase coverage and phone number inventory, Zentrunk can get you started instantly. No minimum spends, carrier negotiations or long-term contracts to maintain, Zentrunk lets you provision SIP Trunks instantly through our user interface or via our API. We are list pricing this very aggressively with further discounts at volume.

E.g (Prices in US start at)

$0.0062/min for outbound calls to local number $0.0030/min for inbound calls on a local $0.45 for a US local phone number

A simulated social experiment it is. This is pretty much how societies will need to be like. WIN - WIN - WIN!

This is applicable even for our existing countries - US, Canada & UK!

- Acquired Zopim in March 2014

Revenue - 2011: 15.6M, 2012: 38.2M, 2013: 72M

Losses - 2012: 24.4M, 2013: 22.6M

Seems like going IPO with losses is the new trend

Plivo also has an OSS offering which is based on FreeSWITCH. So it could work with that too.

Disclaimer: I am part of the Plivo team.

Would love to have you onboard with Plivo. Just for the record, we can port your existing short-codes from other providers at the same price points.

If that sounds interesting, feel free to reach me at venky@plivo.com

I hear you. We all hate SPAM!

In the US, short-codes are helpful for B2C SMS communication. US has many regulations on using a regular phone number for sending SMS via Applications and APIs.

For starters, a shortcode allows you to send 40 sms/second which is not allowed using a regular phone number.

We have tried to document some of the differences and cases when a shortcode is helpful: http://plivo.com/faq/shortcode/what-is-the-difference-betwee...

We have been using this in production for over 2 years at scale and just cross checked to have this enabled.

Totally agree, that this should be default False!

Try Chrome which will use HTML5, No-Flash!

This code is open source. Feel free to send a pull request with "who is talking"..

XML to use is here - http://plivo.com/docs/xml/conference/

Hint: use the floorevent param.

Plivo WebSDK (http://plivo.com/voip-sdk/) allows graceful fallback to Flash for non WebRTC browsers.

WebRTC alone won't run on all browsers!

Plivo has an open source framework too. Currently this App is built on the cloud, but feel free to port it to open source version!

http://plivo.com/open-source/

Back now in San Francisco!

Great to see a YC company raise the next round with an open source pivot. Would be interesting to see how this pans out.

Great job Solomon and team. I am all for you guys!

@sashaeslami We started Plivo with a simple vision of helping businesses move to the cloud, use simple APIs for building Apps and not having to pay markups from telecom carriers. Our focus has always been to solve the Infrastructure problem.

This is the primary reason we want to allow our customers to have access to the best pricing possible (without crazy markups).

In some cases we may not be able to offer the best price, and hence we have Bring Your Own Carrier Model [1]

[1] - http://plivo.com/byoc/

Thanks Glen for the kind words :)

@jessaustin, Let me try to explain a few more details here:

Inbound Phone Number existing Carrier

Lets assume, you have existing numbers you own with your existing carrier. Carriers usually allow forwarding to certain IP destination or hostnames like sbc.plivo.com, so what you will need to do on your carrier side is to just configure this one time for the numbers with them.

On the Plivo side, for us to be able to enable the carrier to pass through our firewall, you would whitelist the Carrier IPs using our APIs/UI and then add (not buy) the numbers in the system you own with the carrier. That we it allows us to be able to match the incoming calls from a certain carrier on a certain number to a customer app. (there are tons of edge cases here I am not covering, but we have taken care of that in the implementation)

Outbound Calls via your Carrier to phones

This is a bit more tricky and complex as users may want to use Carrier 1 for Country A, Carrier 2 for Country B etc.. so we allow customers to be able to configure this logic using our APIs and assign them with dedicated IPs which allows the carrier to distinguish where the call is coming from for them to bill/ account it.

It may sound simple here, but trust me, when you open up that kind of logic to every customer, it becomes a tough problem quickly and thats where architecture matters. I am not sure, I want to talk about how we architected the system, so will leave it for later discussion.

Regarding DoS or DDoS, IP spoofing is not so trivial, as first one needs to figure out carrier ip, then customers phone number and then all they can do is just trigger the app which can perform some business logic. So again not sure if there is any security risk with this.

Interesting. Do you want to drop us a note at hello@plivo.com and we discuss more about this.

DH tried answering this above, pasting it here..

Cloud telephony platform consists of 3 main components - 1. Technology, 2. Infra/Ops 3. Carriers. Until now we and other providers have offered APIs which bundled all three together. This is good for folks who are just getting started, as customers want to get the best pricing and direct access to carrier when they start to grow. Just like how one can get own merchant accounts with Payment gateways. Today's announcement means we basically allow you to use all 3 components from us, or just use us for Technology and Infra and bring your own carriers. Rest of the details in the post. let me know if you have any other questions :D

@thesis, thats a great question.

Answer: No its not just SIP trunking. We have always supported native SIP trunking (in, out & device registrations) from day 1 we publicly launched in July 2012.

With BYOC launch, we now allow/make it simpler for any developer, business to be able to use existing VoIP carriers and plug in our APIs to build powerful apps. Its completely plug and play. e.g. we offer a dedicated IP to authenticate with, for folks who want to plug in outbound carriers to terminate calls.

Absolutely. With IPv4 becoming scarce this is surely needed. However, we are working with select few carriers to see if we can have this done the right way!

Thanks Josh. We support IP based auth for now.

Followup to this post with some more details on our blog:

http://plivo.com/blog/plivo-launches-bring-your-own-carrier/

Thanks for your input. Are you looking at a PBX sought of use case?

Good to hear feedback from customers!

Thanks :)

This is awesome!

Not sure where you saw 8 cents. Its actually 0.8 cents and once you start scaling higher it gets cheaper.

http://plivo.com/pricing/