Comments for Turn-key VoIP Systems - Sipwise

Comment on Cloud Telephony – A reality check by Jason Goecke

Jason Goecke — Thu, 05 May 2011 13:12:51 +0000

There are two ways to avoid telephony cloud lock-in. First, by only using standards based APIs, like VXML or CCXML. This ensures if you write an app, you may port it elsewhere. Proprietary APIs are what lock you into a particular vendor.

The second, which you have already pointed out, is open-source. We actually have several open-source projects released and more underway, including Tropo itself. We work to test compatibility of the projects with alternative open-source platforms such as Mobicents and Sailfin.

Some great points here. Your cloud provider must be transparent about their architecture, provide standards based APIs or as an alternative provide open-source APIs. That is what we like to call ‘Unlocked Communications’.

Comment on Cloud Telephony – A reality check by Sherman Boyd

Sherman Boyd — Thu, 05 May 2011 01:13:18 +0000

Right now my gripes with cloud telephony are not only the lack of transparency which you cover quite well, but also vendor lock in. What happens when your provider goes under, doesn’t have it together technically, or decides to raise prices, changes use policy, etc, ad infinitum.

One of the great things about open source telephony (like Asterisk) is how you can actually use multiple service providers at once. If one fails you can drop over to the other, or even use the cheapest one for the call context. It’s a nice efficient marketplace.

Comment on Cloud Telephony – A reality check by Jason Goecke

Jason Goecke — Thu, 05 May 2011 00:41:53 +0000

Great write up given the recent reality check that Amazon gave the world on cloud services. With Tropo, we are happy to answer architecture questions and will readily share these details with the development community and our users.

We don’t actually run our core services on Amazon EC2, we run our core media and SIP services in our own data centers. Of which there are three across the US for scale and redundancy. We do use some Amazon and Rackspace services for web applications, but are not ready to move core media services there.

Further, we make the engine that drives Tropo, Prism (http://voxeo.com/prism), available for a free developer download and available under license to customers. This means you have a choice, you may use our cloud services, use us in your own data centers or a combination therein. We already have significant service providers using private instances of Prism running in their own networks.

While we pride ourselves in a rock solid cloud offering, we know there are use cases and customers that want to have their own private instance or a hybrid for both.

So I agree. You must be transparent about your architecture. Ready to answer hard questions. And give your developers and customers choice about whether or not to use the cloud at all.

Comment on sip:providerCE 2.2 – a quick preview by Dejan

Dejan — Tue, 26 Apr 2011 23:59:49 +0000

The regexp routing is actually quite good thing to have once you get used to it.
Within few hours I have been able to set up the base system. Now it is the time for adding the features that couldn’t be added if I have had to develop the whole system from scratch. Great stuff you have here Andreas!!!

Comment on sip:providerCE – the first release of the open-source Class5 VoIP platform by Andreas Granig

Andreas Granig — Tue, 01 Feb 2011 11:05:23 +0000

@Ruben, glad you find it useful! We’re currently at release 2.1, and TLS is planned for 2.3 (in ~6months) to be integrated out-of-the-box. In the meanwhile, you can add it manually in /etc/ngcp-config/templates/etc/kamailio/kamailio.cfg.tt2, then run ngcpcfg apply. If it works for you, we’d be happy if you could contribute it back

Comment on sip:providerCE – the first release of the open-source Class5 VoIP platform by Ruben Linder

Ruben Linder — Mon, 31 Jan 2011 07:01:30 +0000

Really impressed by your your product! I see there is TCP transport support, what about TLS?

Comment on sip:providerCE 2.2 – a quick preview by Andreas Granig

Andreas Granig — Thu, 27 Jan 2011 15:34:31 +0000

If you’ve issues with the configuration, subscribing to http://lists.sipwise.com/listinfo/spce-user and asking for help there (describe what you’ve put where, what you expected and what the result was) will most likely solve your issue.

Comment on sip:providerCE 2.2 – a quick preview by Michael Magan

Michael Magan — Wed, 19 Jan 2011 03:40:02 +0000

Hopefully it will be more friendly with respect to making outbound calls. No registration to sip providers is possible and the way you call the ruling aspect of the system needs to be changed to a more understandable way. Callee is not something you would use it is simple outbound and inbound routes. For the life of me i can’t make and outbound call through any of my suppliers. They can be sip (asterisk) or digit sent authenticated. it is impossible. so if you cannot use the pstn what good is it for?. my 2 cents.

Comment on sip:providerCE – the first release of the open-source Class5 VoIP platform by Daniel Tiefnig

Daniel Tiefnig — Tue, 21 Dec 2010 09:01:03 +0000

We actually developed something like this (but tailored to a specific use-case) some time ago, and we were also thinking about a Sugar CRM integration. We might release something to the public in the future, but we are currently rather focused on communication features instead of customer management. One can always integrate the platform with external CRM tools via the SOAP and XML-RPC APIs.Feel free to discuss this on the Spce-user list, as we may adjust some of our priorities if there is popular demand for specific features.

Comment on sip:providerCE – the first release of the open-source Class5 VoIP platform by Tyrone Miles

Tyrone Miles — Mon, 20 Dec 2010 17:53:32 +0000

This is a very interesting product, and I will be installing it very soon. I have looked at other product as well, and noticed they have a customer signup portal. Will this be something in the near future or is there an api to another product to handle new customer signups?