Sharing a Softswitch

I see a lot of companies buying softswitches and it makes me wonder if it might not be a better economic idea to share a switch with somebody else. There is so much potential for savings that anybody thinking of installing one should consider it. In the following I will discuss what it means to share a softswitch and look at the pros and cons.

The Basic Requirements. Sharing requires that somebody already owns a softswitch that can control geographically separated gateways. Such a switch must be able to share both the inter-machine trunking gateways, which facilitate PSTN interconnection and the media gateways which facilitate interconnection to customers. Sharing is also going to require interconnection between the two sharing parties. This means there must be some sort of trunking established between the two parties that can be either traditional TDM trunks or IP trunks.

What Would be Shared. The following elements are the components of a softswitch that can be shared, meaning that only one of each of these needs to be purchased:

  • Core softswitch – the device that contains subscriber and routing information;
  • Feature Server – the device that facilitates phone features;
  • Session Border Controller – the device that provides security between the softswitch and the gateways, some CPE and other networks;
  • Signaling Gateway – the device that interface with the SS7 network;
  • Unified Messaging or Unified Communications server – the device that stores, controls and converts data used in unified communications services like voice mail, email notifications, voice to text and text to voice, etc.

What the Second Company Needs to Buy. If you are going to share somebody another softswitch you only need to buy a few components. These are referred to as the distributed elements in a softswitch network. The two elements that you must buy are:

  • Inter-machine Trunking Gateway – for local interconnection to the PSTN. This lets the lessee still connect to the world using the same connections in place your legacy switch;
  • Media Gateway – for local connection to local distribution network and/or CPE.

Data connections required. As mentioned, there must be a data connection established between the softswitch and the new location that allows communications between the shared elements housed at the core softswitch and the distributed elements found at the new location. The size of the data pipe/connection required depends on the amount of data required between the shared and distributed elements. It only requires a few megabits per second to transmit voice traffic. You’ll need a connection in the tens of megabits per second if you are using a lot of features like voice mail & unified communications or a lot security invocation.

Partitioning. The owner of the shared elements will have to ‘partition’ the shared elements in order to ensure that subscribers of the sharing company can’t be seen or manipulated by other sharing companies; Partitioning will also hide the call detail records, routing control and will make sure that the shared elements can communicate through to the multiple networks operated by the sharing companies.

How to Determine if Sharing is the Right Idea. The big benefit is the savings, but there are other considerations:

  • It is inexpensive to buy only the distributed elements. Depending on how large you are, the distributed elements could cost anywhere between $25k and $200k which is far less than buying a new softswitch.
  • What is the cost of the data connection needed to connect the two locations? Generally companies make these connections using establish Internet backbone and this typically adds nothing to that cost.
  • How much does the switch owner want to charge for using the softswitch core? There are many ways to charge for this service. It could be done on a flat rate monthly lease, a connection fee per telephone number.
  • Reliability. How good is the Internet connection between the two companies? If that connection is lost then voice processes will stop. Ideally the connection ought to be on a ring or have redundant routing.
  • Control. I often hear a company thinking of leasing say that they feel like they don’t have enough control in a shared switch. But you can get access to all important switch functions remotely.

When I look at the numbers I find that it is almost always better to share a switch rather than to buy a whole new switch. However, the one factor that still often drives the decision to buy a new switch rather than share is the reliability of the data connection between the two parties. But this is generally about the same reliability as connecting remote switches in your own network to a host switch.

If you want to consider sharing a softswitch call CCG and we can help you work though this decision.

Unified Communications

One of the most powerful feature sets available today is unified communications. Yet very few of my clients are selling it today. But if your customer base includes businesses or a lot of residential power users then you need to include unified communications in your product portfolio, and you need to sell it.

What is unified communications (UC)? UC is the integration of real-time communication services with non-real time services. Real time services include such things as voice telephony and VoIP, instant messaging, speech recognition, data sharing, collaboration and video conferencing. Non-real time communication services are often packaged under the name of unified messaging and include such features as voicemail, email, SMS and faxes.

There is no standard set of features that are included in a UC package and it seems that every company that offers it does it a little differently. So a carrier must typically build this product by tying together all of the components and features you already have available into a bundled product. Most carriers who own a softswitch and a voice mail server are capable of creating a basic unified communications product.

There are numerous value propositions that UC offers to end user customers:

  • Brings the ability to delivery any communications medium to any device, anywhere.
  • Extends the corporate network so that mobile customers can be productive from anywhere.
  • Gives the freedom to each individual UC user to tailor the product for the way they can best use it.
  • Can add telepresence technologies to let a UC user check the availability of other resources in his network. For instance a user can see if somebody is available to talk before they try to call them, eliminating the voicemail chain.
  • Can add collaboration and data sharing components which will make employees far more productive. Good collaboration software gives users the ability to share and work together on any document from any software platform simultaneously.

The value to a customer of UC is that it allows the customer to send a message on one medium and receive the same communication in another medium. This frees a customer from any restraints imposed by location or device and the perfect UC product will deliver any communications path to any device anywhere.

For example, a customer can receive an email on any device of his choice and also has the option to have the email content delivered as a standard email, or as a voicemail or text. Normally the customer can receive the medium, in this case an email, live in the medium for which it was intended, but can also opt to receive or store the email on a non-real time basis in any other medium.

The control for making the desired choices is given to the customer. To continue with this example, the customer can set up his UC to always receive emails in a certain format, for example, as a voice mail he listens to on his cellphone, or he can change his options on the fly during the day.

UC is a very powerful product for customers who grasp it and use it. It can make a customer sticky to your network if you give them the freedom to have complete control over their communications.

How do you create a UC product for your network? The first step is to decide what you want to offer. Not every UC system tries to deliver every communications product to every device. Many UC products instead are crafted to satisfy specific customer applications. If you own a softswitch you probably already own many of the components needed to build a simple UC product. For example, there are various features built into the feature packages on a Metaswitch that can be combined to create a decent UC product. And if you only have a few business customers who will be interested in UC, this might be sufficient.

The other alternative is to buy a UC product from somebody else’s platform. Today there are numerous companies who have assembled UC products that function on their own platforms. As a carrier you can access these platforms on a wholesale basis and buy ready-made UC products for your customers rather than build your own UC products from scratch.

There has been a lot of industry activity in developing UC products in recent years. Since March 2008 there have been several open source UC projects based on Asterisk that has led to the creation of open source UC product lines. In May 2010, the Unified Communications Interoperability Forum (UCIF) was created to develop standards between technology companies for UC and to create interoperability profiles, implementation guidelines, and best UC practices. The original founding members were HP, Juniper Networks, Logitech, Microsoft and Polycom.

Because UC can be done in many different ways and can include numerous product components you can save a lot of time before trying to create a UC product by talking to CCG.