dhfromkorea

Another interesting startup from the Nordic. Where can I see what positions the team is hiring for?

True, I think that's fair concern.

Hi chhl. With Plivo, you also need to get legitimate numbers to send SMS messages. (numbers purchased on Plivo or numbers ported to Plivo)

As you know, this is a preventive measure against spoofing; however there are some edge cases where allowing custom caller IDs might make sense. (e.g. when you want to have people you called get back to a certain number—custom phone line numbers at a large organization.)

Hi, you're correct that the RasPi functions as a quick dialer and is out of picture once the call is answered, as the original set-up doesn't have the ability to receive a call.

*this could be virtually any connected device; mobile, fixed phone or SIP phones. Also you could do a lot more fun stuff using conferencing or anything that's on our xml page: http://plivo.com/docs/xml/

Hi Kumarski, as Andy (author of the post) mentioned earlier, you can connect two (or normally a lot more people) using our conference API and XML and you could use something like cron to schedule the conference call. (if you'd use Python?)

Hi, it's DH from Plivo. Happy to answer any questions regarding Plivo. :D

That makes two of us. VoIP integration on Hipchat is something I'd like to see happen. (I don't work at Hipchat :D)

And obviously it looks like we're not the only ones on this. http://help.hipchat.com/forums/138883-suggestions/suggestion...

Hi, it's DH from Plivo here. More than happy to answer any questions you might have. :D

You're not alone. Here's an early variant of such a policy. SEMCO, a Brazilian company run by Ricardo Semler, has since 1980s had the policy where people could set their own salaries.

Some excerpts off his book on 37signals: http://37signals.com/svn/posts/945-excerpts-from-ricardo-sem...

His book: http://www.amazon.com/Maverick-Success-Behind-Unusual-Workpl...

True. And I think it would be even better if YOU are included in the PEOPLE. Essentially you would want to do justice to your inner desire.

Thank you @j_baker. I will bear your feedback in mind and try my best to make you not need me for some core questions like this next time. :D

Yes, it requires very different kind of architecture to be able to interop openly. However, we did design for it from day 1. It does not need anything from carriers and most of the VoIP carriers already support it. We will be pushing out more blogs/docs for specific carriers in coming weeks.

That's what we expose to our customers. There is a whole lot more on the backend. :D

Hi, I just added some comments above. Let me know if you have other questions. :D

Hi @j_baker tl;dr -> 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

Here's a related Forbes article: http://www.forbes.com/sites/tomiogeron/2013/08/14/plivo-targ...