XConnect Alliance System

XConnect Network and Systems:

Interoperability Requirements
KYXC-005 Version 4.0.6 July 2006

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page 1 of 8

XCONNECT NETWORK AND SYSTEMS:

INTEROPERABILITY REQUIREMENTS
KYXC-005, VERSION 4.0.6, JULY 2006

TABLE OF CONTENTS
SCOPE ......................................................................................................................3 XCONNECT IP CONNECTIVITY ....................................................................................4 XCONNECT NETWORK INTEROPERABILITY REQUIREMENTS .........................................4
1. Signaling/Protocol Requirements ....................................................................... 4 2. Media Requirements............................................................................................. 5 3. ENUM / Number Routing ...................................................................................... 5 4. Billing Systems Requirements ............................................................................ 5 5. End-User Dial Plan Changes................................................................................ 5 6. Hardware Requirements for XConnect Local Directory Server........................ 6
6.1 6.2 6.3 Minimum Requirement Specification.......................................................................6 Recommended Requirement Specification .............................................................6 Non-Dedicated Configuration..................................................................................6

XCONNECT INTEROPERABILITY CERTIFICATION ..........................................................7

TABLES
Table 1: Related Documents............................................................................................. 3 Table 2: Minimum Hardware Requirements...................................................................... 6 Table 3: Recommended Hardware Requirements............................................................ 6

APPENDICES
CHANGE HISTORY VERSION ...................................................................................A-1

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page 2 of 8

Scope
This document specifies the hardware, software, and connectivity requirements for the VoBB. Fulfilling these requirements is necessary to ensure successful interoperability with the XConnect system. The Request for Comment (RFC) documents referenced in Table 1 can be found at http://www.ietf.org/rfc.html. The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet.
Table 1: Related Documents Document KYXC-007 RFC 2198 RFC 2246 RFC 2782 RFC 2833 RFC 3261 Title XConnect Alliance System, ENUM Queries to the XConnect System RTP Payload for Redundant Audio Data The TLS Protocol Version 1.0, T. Dierks, C. Allen, January 1999 A DNS RR for specifying the location of services (DNS SRV) A. Gulbrandsen, P. Vixie, L. Esibov, February 2000. RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals, H. Schulzrinne, S. Petrack, May 2000. "SIP: Session Initiation Protocol", Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, June 2002. Reliability of Provisional Responses in Session Initiation Protocol (SIP) J. Rosenberg, H. Schulzrinne, June 2002. Session Initiation Protocol (SIP): Locating SIP Servers, J. Rosenberg, H. Schulzrinne, June 2002 An Offer/Answer Model with Session Description Protocol (SDP), J. Rosenberg, H. Schulzrinne, June, 2002. A Privacy Mechanism for the Session Initiation Protocol (SIP), J. Peterson, November 2002. Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks The E.164 to Uniform Resource Identifiers (URI)Dynamic Delegation Discovery System (DDDS) Application (ENUM) Session Timers in the Session Initiation Protocol (SIP), S. Donovan, J. Rosenberg, April 2005.

RFC 3262 RFC 3263 RFC 3264 RFC 3323

RFC 3325 RFC 3761

RFC 4028

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page 3 of 8

XConnect IP Connectivity
All connectivity is currently provided via public internet to our nearest PoP locations: In Europe: London. In the USA: New York and West Virginia.

XConnect Network Interoperability Requirements

The following requirements are presented in this section: Signaling/protocol Media ENUM/number routing Billing systems End-user dial plan changes Hardware for the XConnect Local Directory Server (LDS)

1. Signaling/Protocol Requirements
The following requirements exist for signaling and communication protocol: 1. The XConnect member system shall support SIP [RFC 3261, 3262, 3263, 3264, 3323, 3325, 4028] or H323. 2. The XConnect member system shall support Transport Layer Security (TLS) [RFC 2246]. 3. The XConnect member system shall have a maximum of two IP domains (SRV supported) or IP addresses for RTP Signaling Ingress / Egress [RFC 2782].

In Phase 2:
4. The XConnect member system shall support CallerID, for all calls, including anonymous calls. 5. The CallerID must be a valid number. The number shall be formatted according to the e.164 convention and must be registered in the XConnect Alliance Registry. 6. The CallerID must appear in one of the four SIP message fields listed below: FROM. CONTACT. Remote_Party_ID (RPID) [RFC 3261]. P-ASSERTED-IDENTITY. [RFC 3325] This is the preferred location for the information. 7. For Anonymous Calls: The CallerID must appear in the RPID or P_ASSERTED_IDENTITY field, with the Privacy flag set [RFC 3323]. 8. When the privacy flag is set, the CallerID shall be removed by XConnect before the call is terminated to the destination operator.

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page 4 of 8

2. Media Requirements
The following requirements exist for media handling in the XConnect system: The XConnect member system shall: 1. Support codecs: G711A-Law/U-Law and either G729a/b or G723. iLBC. 2. Support T.38, for Fax over IP, or G711 auto detect. 3. Support DTMF in-band and out-of-band [RFC 2833]. Must support: DTMF in-band with G711 and Inband DTMF).

3. ENUM / Number Routing

1. The VOBB shall perform its own number manipulation, so that the number being looked up is always formatted as a full e.164 number. 2. The VoBB Proxy must support one of the following three requirements: a. ENUM RFC 3761 protocol, including the ability to: Configure the system with an alternative domain suffix (i.e., append xcrouting.net, instead of e164.arpa). Support a split-DNS in the local DNS configuration, to facilitate address resolution for local DNS queries. b. Send a SIP Redirect 302 (or 305), with fallback routing upon receiving the 404 Response Code. c. Send an INVITE with an e.164 formatted number to a SIP proxy server, for relaying to the next hop. For more information, see KYXC-007, ENUM Queries to the XConnect System.

4. Billing Systems Requirements

The VOBB Billing Software must be capable of rating a call based on the: 1. Destination number dialed, and 2. The Carrier route (e.g., XConnect Alliance), based on the domain name used in the route (e.g., telnumber@xcrouting.net), to ensure that a call routed via the XConnect Alliance can be zero-rated.

5. End-User Dial Plan Changes

The XConnect member shall: 1. Provide a facility for the end user to force a call to terminate via the PSTN, and not via the XConnect network (e.g., if there is a FAX incompatibility), using a designated short code e.g., *** 2. Support Private Plan dialing, (i.e., Private_Plan_Escape_Code + VOBB_Short_Code + Private Plan Number). The recommended Private_Plan_Escape_Code, is 000.

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page 5 of 8

6. Hardware Requirements for XConnect Local Directory Server

6.1 Minimum Requirement Specification
Capability: Up to 300 Queries / second, with 20 ms average latency. This is typically a two-unit server with options for expansion (recommended), which is intended for low volume (< 300 queries / second), or trial configurations. Future additional LDS functionality may be limited.

Table 2: Minimum Hardware Requirements Equipment Processors Memory Hard drives Operating system Additional software Description One Pentium dual core Xenon CPU (4MB L2 cache), upgradeable to Twin CPUs. 2 GB, upgradeable to 12 GB. Two 73 GB hard drives, 15 K RPM in RAID 1 (hot swap). RedHat Linux ES 3 update 7. SUN Java 1.42.

6.2 Recommended Requirement Specification

Capability: Up to 1000 Queries p / second, with 10ms average latency.
Table 3: Recommended Hardware Requirements Equipment Processors Memory Hard drives Operating system Additional software Description One Pentium dual core Xenon CPU (4MB L2 cache) upgradeable to Twin CPUs. 2 GB, upgradeable to 16 GB. Three 73 GB hard drives, 15 K RPM in RAID 5, which provides 140 GB. RedHat Linux ES 3 update 7 SUN Java 1.42.

6.3 Non-Dedicated Configuration

You may choose to run the LDS on a non-dedicated server, provided there is sufficient memory and processor power to handle all the applications running on the server.
Notes: A dual processor is recommended for the non-dedicated configuration option. The Latency Time and Maximum Queries p/second may be degraded if the LDS is run on a non-dedicated server.

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page 6 of 8

XConnect Interoperability Certification

XConnect shall perform joint interoperability testing with the VOBB to verify that the Technical Interconnect XConnect Network standards are met. On the completion of successful interoperability testing, an Interop certificate will be issued by XConnect. Recertification may be required each time the VOBB changes network elements that materially change the Signaling or Media of the Interconnect.

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page 7 of 8

Change History Version

Version V4.04 V4.0.3 V4.0.2 V4.0.1 Name CB, YB CB, YB DS KayoteEK ,CB , Date 07/2006 05/2006 16/03/2006 15/03/2006 Organization, formatting, and text changes Text review Text review following Operations review Comments

XConnect Network and Systems: Interoperability Requirements KYXC-005 Version 4.0.6

2006, XConnect Global Networks Ltd. In Commercial Confidence

July 2006 Page A-1