CIBER 2.0 to CIBER 2.5 Migration
Robin Thomas, Product Manager
March 3, 2006
1.1 Purpose and Requirements
The purpose of this document is to outline the position Syniverse
Technologies has taken in response to the sunsetting of the CIBER 2.0
record format on March 16, 2006, as proposed by Cibernet.
1.2 Definitions, Acronyms, and Abbreviations
Acronyms and Abbreviations Description
ACCESS Automated Clearinghouse Calls
Exchange Settlement System
ACCESS TWG ACCESS Technical Working Group
CIBER Cellular Intercarrier Billing Exchange
CIBER 2.0 Industry record format that includes
record types 10, 11, 20, 30, 40, 50 and
CIBER 2.5 Industry record format that includes
record types 22, 32, 42 and 52
1.3 Reference Documents
CIBER Manual – November 2005 Notice
Cibernet – CIBER 2.5 Migration Paper, February 2006
2.1 Sunset Date
In early 2005, an industry notice was sent by Cibernet to all of its members
letting the operators who utilize CIBER, clearinghouses and billing vendors
know that the CIBER 2.0 record format will be sunset on March 16, 2006. A
final notice was issued with the November 2005 monthly CIBER updates
reminding us of the upcoming sunset date. The records that will be sunset as
of March 16, 2006, are CIBER record types 10, 11, 20, 30, 40, 50 and 70.
2.2 After Sunset Date
After March 16, 2006, operators, clearinghouses and billing vendors will no
longer find any references to the CIBER 2.0 record format within the CIBER
Manual. This does not mean that Syniverse will no longer allow these records
to be used or exchanged.
All future CIBER enhancements will be for the CIBER 2.5 record format only,
which includes CIBER record types 22, 32, 42 and 52.
3 Syniverse CIBER 2.0 to CIBER 2.5 Migration Path
3.1 Use of CIBER 2.0 after March 16, 2005
Syniverse has done some analysis to see how many operators still send
CIBER 2.0 records. As of February 2006, there are thirty-six customers from
around the world who create and send the CIBER 2.0 record format to
Syniverse for clearing and settlement.
As your clearinghouse, Syniverse will allow both the CIBER 2.0 and 2.5
record formats to clear and settle. The March 16, 2006, date corresponding
with the sunsetting of the CIBER 2.0 records does not include any edit
conditions allowing Syniverse to reject these records.
We are aware that Cibernet is in the process of soliciting operator feedback
for a hard cut-off date. If a hard cut-off date is determined, Syniverse will
reject CIBER 2.0 records at the industry agreed date.
3.2 Syniverse Conversion Service
Syniverse does offer CIBER 2.0 to CIBER 2.5 conversion services.
3.3 Conversion Service Details
Our Conversion Service is at a company level for all CIBER 2.0 data sent to
Syniverse by the serve operator for clearing and settlement. The conversion
does not include going from CIBER 2.5 to CIBER 2.0. Once converted to
CIBER 2.5, data will remain in the CIBER 2.5 format when forwarded to the
other clearinghouses, billing vendors and operators’ billing systems.
3.4 Conversion Record Mapping
Syniverse has mapped the fields in the CIBER 2.0 to the fields in the CIBER
2.5 records. When applicable, the default values of zeros and blanks are used
for fields that are on the CIBER 2.5 records that were not on the CIBER 2.0
records. In addition, fields that are longer on the CIBER 2.5 records will be
padded with the appropriate zeros and spaces. Some examples of how
Syniverse will convert a few of the fields for a 22 record are listed below:
CIBER 2.0 Record CIBER 2.5 Record
ESN (Electronic Serial Number) pad with zeros
Original Cell Site pad with spaces
Caller ID Length If call-direction = “1”, use MDN length;
otherwise, use “00”
A complete listing of the conversions fields can be provided to operators who
use the conversion service.
3.5 Syniverse CIBER 2.5 Creation Service
Syniverse also offers CIBER 2.5 creation services. If you would like additional
information concerning our CIBER creation services, please contact your
Syniverse Account Manager.
4 Syniverse Contacts
To find out more about the sunsetting of the CIBER 2.0 records or
Syniverse’s CIBER 2.0 to CIBER 2.5 Record Conversion service, please
contact Robin Thomas, ACCESS product manager, at 813-273-3170 or