Arbinet’s CLNTM Servers permit globally distributed CLNs to share information. For service providers, the CLN Server acts as a unified source of customer account information and enables remote verification of accounts. Remote verification in turn allows end-users global roaming access (the ability to utilize CLNs outside of their “home” CLN’s calling region). Therefore, service providers may install CLNs in numerous countries/regions establishing a global network of CLNs and may follow their customers worldwide.

The CLN Server Family

The CLN Global Server

The CLN Global Server, a Microsoft SQL Server with an NT operating system, services up to fifty fully loaded CLNs.

The CLN Mega – Server

The CLN Server, a Sun HPC Server, connects more than one thousand fully loaded CLNs.

CLN Server Remote Verification Options:

Option 1. Verification within a Service Provider’s Privately Owned CLN Network

This verification process is as follows: A user dials into a CLN (the origination CLN) other than their “home” CLN. The origination CLN sends a request for verification to the CLNTM Server. The CLN server then searches the CLN Server Database (a local database, see below) for account verification and determines which services, language of prompts etc. to make available to the user. Verification is then sent to the origination CLNTM.

This configuration offers service providers and end-users the speediest remote verification of accounts and thus the quickest connect times.

Option 2. Verification across CLNs Independently Owned and Operated by Numerous Service Providers

This verification process works as follows: A caller dials into a CLN (the origination CLN) other than their “home” CLN. The origination CLN sends a request for verification to the CLN Server. The CLN Server then requests verification from the user’s home CLN. The home CLN looks-up the customer’s account profile (services, language of prompts, etc.) and sends verification along with user preferences to the originating CLN via the CLN Server.

This configuration enables service providers to transparently exchange international traffic with no security risks.

CLN Server Functions

Unified CLN Database

In applications where verification is performed entirely on the CLN Server, the CLN Server Database contains account data, cost tables and service information from every networked CLN. The CLN Server Database also contains information related to individual CLNs capabilities (services available on each CLN in the network). The CLN Server database may be updated in batches or real time by authorized administrators.

Authorization Server

Requests for both account verification, and service authorization (services available on the origination CLN and re-origination CLN, and services to be made available to the end-user) are processed by the CLN Server. As an authorization server, the CLN Server also monitors the status of existing CLNs (receiving upgrade updates), installation of new CLNs and reconciles events between CLNs.

CLNTM Administration Server

The CLNTM Server Administration Function:

• Maintains and broadcasts updated cost tables for every networked CLNTM
• Maintains country/state specific regulatory information to ensure compliance with local laws
• Generates reports including: CLN status report, CLN billing report, CLN traffic report and a number of statistical reports
• Performs traffic analysis – If the server detects heavy traffic to a region without a CLN, a report is generated for the administrator