BT SIP Trunking

BT SIP Trunking

SIP Trunking at BT

BT

BT’s 21st Century Network (21CN) initiative is well-known and regarded as being in the vanguard of strategic initiatives to implement an all-IP telephone network, and over the course of several years BT has implemented a national IP network and installed much equipment. In the meantime, however, BT has a business to run, with customers depending on continued services.

Today, businesses across the UK still use and depend on the primary rate ISDN service for call centres, offices and so on, to connect to the PSTN. The business premises are often distributed across multiple geographic sites, and often Customer Premises Equipment (CPE) installed that still need to be supported.

BT needed to respond to competitive substitution services based on Voice over IP (VoIP) technologies, and needed a solution that aligns with its 21CN strategy. The 21CN architecture includes a Network Open Application Server (NOAS): a highly scalable, highly available, low latency, in-network Telecom Application Server. BT had already concluded that SIP Servlet containers are inadequate and do not meet the exacting requirements for NOAS. In contrast, OpenCloud Rhino was evaluated exhaustively for this SIP Trunking service and chosen as the approved 21CN NOAS.

The SIP Trunking project delivers a SIP Trunk connection with an arbitrary number of IP-based voice “circuits” to each customer site and enables multiple SIP Trunks from different sites to be grouped together so that different premises for a customer may be linked and interconnected.

The solution delivers the necessary functionality which falls into two broad categories:

  1. Call control - Establishment and termination of inbound and outbound calls ("on net" and "off net"), DDI (Direct Dialling In), Geographic & non-geographic number support, Call Rejection, Call Routing, Call Barring and Call Diversion, Call Reject etc.
  2. Number translation/ manipulation - Forwarding, CLIP, CLIR (in accordance with UK code of practice), number presentation, Number Import / Export

OpenCloud Rhino was selected because it provided the high availability and protocol connectivity that was required on an open, extensible platform. The SIP Trunking applications were developed in-house as like-for-like replacements of their ISDN offerings.

Back to top ^