Using Microsoft’s™ “Web Services” standards, can give internal corporate developers the ability to directly attach and use Connect services with corporate Intranet/Extranet facilities or any internally developed program interface. Obvious uses for this are integration into a corporate telephone directory on an Intranet or Extranet.

The beauty of this solution is that it utilises Web Services as they were intended, as links to a commodity item – in this case telephony. This makes the whole Computer Telephony Integration (CTI) painless and without overheads. You don’t need to wrestle with interconnectivity, telecoms protocols, physical connections to handsets or PBX so you communicate through a standard software layer using your existing user authentication and letting us do all the work for you.

If you use an IP-based PBX, such as switches manufactured by Mitel, Lucent, Alcatel or Cisco, you can now direct calls over the low-cost network using outward bound VoIP to terminate as opposed to using a local carrier. In particular, we are working with Cisco on full integration with their Call Manager product.

There are two choices of usage for this product. The first is to create VoIP at your IP-PBX and connect to our voice network over a data channel. The second is to keep VoIP within the control of your organisation and use the intelligence of your IP-PBX to generate a request to open up a PSTN channel through your normal telephony trunks, but with our exceptional call costs.

As a by-product, the entire system acts as an interface to our other services. For instance, it will act as a ‘Call Accountant’ since all calls will be registered as they pass through the routing process, and then be available online within the central system. We can add features such as accounting codes, user PIN numbers and even recording through this interface.

Designed specifically for integration of CallKey facilities into third party products, such as CRM applications, developers can now replicate all of CallKey’s features and services into custom applications through an API interface layer.

A variety of connection methods are available to suit the level of connection required. From simple encoded url strings to industry standard Web Services and SOAP interfaces right down to integration using a version of the Standard TAPI protocol driver.