TELEPHONY API'S

Telephony Application Programming Interfaces (API's) are pre-compiled and optimized C/C++ function libraries and/or Java class libraries (.jar files) tailored to a specific ASN.1 application. Objective Systems can either create a custom API for your application (see Services) or has the following packaged API's available.

Updated LTE/3GPP API's are now available on a separate web-page at http://www.obj-sys.com/lte_3gpp_apis.php.

The following API's are currently available:

What the Telephony API’s Include:

• a complete C/C++ or Java run-time for encoding or decoding messages
• sample programs for different message types defined within that standard
• documentation on how to use the API.
• 12 months of support which includes recompilation of the API (should specifications change

CSTA

APIs are available for ECMA CSTA Phase 1, 2, and 3 specifications. These APIs include the ROSE and ACSE layers and have been implemented in the C++, C#, and Java programming languages.

Extended sample versions of the CSTA Phase 1, 2, and 3 C/C++ API's are available for Windows. The phase 1 and 2 API's contains a test client progam for testing connectivity with compliant devices with a TCP/IP interface. The phase 3 API contains a Siemens PBX test client to test connectivity with these types of devices.

Extended sample programs require a working installation of ASN1C to be present before they can be used. To install, follow the C++ API installation instructions..

Click on one of the following links to download:

• CSTA All-phases .NET API for Windows

• CSTA Phase 1 C/C++ API for Windows

• CSTA Phase 2 C/C++ API for Windows

• CSTA Phase 2 Java API for Windows

• CSTA Phase 3 C/C++ API for Windows

If purchased, a stand-alone version of the API can be provided.

CSTA XML

The CSTA XML API's implement the 'ECMA-323 XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III' standard. Support is also provided for SOAP WSDL as published in ECMA-348. The code consists of a C or C++ API generated with our XBinder compiler. This is a standalone API - it is not necessary to have XBinder or ASN1C installed to use it.

Click on one of the following links to download:

• CSTA XML Phase 3 C API for Windows

• CSTA XML Phase 3 C API for Linux

• CSTA XML Phase 3 C++ API for Windows

• CSTA XML Phase 3 C++ API for Linux

H.323

H.323 frameworks for C or C++ are packaged as extended sample programs for use within an existing ASN1C distribution (licensed or evaluation). They provide makefiles, ASN.1 specifications, scripts, and configuration files required to compile H.323. You must first have ASN1C installed (Windows or Linux/UNIX version) before you can use the packages below.

For C, unpack the following distribution files in the 'c' subdirectory of your installation:

• H.323 C Encode/Decode API for Windows
   
• H.323 C Encode/Decode API for Linux/UNIX

For C++, unpack the following distribution files in the 'cpp' subdirectory of your installation:

• H.323 C++ Encode/Decode API for Windows
   
• H.323 C++ Encode/Decode API for Linux/UNIX

Follow the instructions in the README file for details on how to compile the specifications and run the sample programs.

NGTP

The Next Generation Telematics Protocol is a technology-neutral telematics protocol designed to bring greater flexibility and scalability to the automotive industry. This API is packaged as an extended sample program for use within an existing ASN1C installation (licensed or evaluation). To install, unzip the package in the <ASN1C>/cpp subdirectory and follow the directions in the README file contained within.

• NGTP C/C++ API for Windows

PKIX

PKIX is the IETF's implementation of the X.509 public key infrastructure standard. This distribution contains C++ software generated with ASN1C that may be used for DER encoding and decoding the various message types that comprise the standard. This API is based on the update of the IETF standard to use modern ASN.1 syntax:

http://datatracker.ietf.org/doc/rfc5912/

• PKIX C++ API for Windows

To install, follow the C++ API installation instructions.

QSIG

Q signaling (abbreviated QSIG) is a protocol that is used for signaling bewteen digital private branch exchanges (PBXs) in VoIP networks. The ASN.1 specifications used in this API are adapted from Ecma International Standard ECMA-212, 3rd edition (December 2001).

• QSIG C++ API for Windows

To install, follow the C++ API installation instructions.

TAP3

API's are available for the latest TAP3 standards. The following versions for C for Windows are available for evaluation download:

• TAP-0312 C/C++ API for Windows
• TAP-0311 C/C++ API for Windows

These are packaged as extended sample programs for use within an existing ASN1C distribution (either licensed or evaluation). To install, follow the C API installation instructions.

C ASN.1 API Installation Instructions

1. The ASN1C compiler must first be installed. An evaluation or licensed version may be used.
2. The API distribution file should be unzipped in one of the 'c' subdirectories under the ASN1C installation root directory. For example, to use the API with Visual Studion 2005, the API should be unzipped in the c_vs2005 subdirectory.
3. The API can now be build using either make, nmake, or the Visual Studio IDE (VS 2005 and higher). See the README.txt file for further details.

C++ ASN.1 API Installation Instructions

1. The ASN1C compiler must first be installed. An evaluation or licensed version may be used.
2. The API distribution file should be unzipped in one of the 'cpp' subdirectories under the ASN1C installation root directory. For example, to use the API with Visual Studion 2005, the API should be unzipped in the cpp_vs2005 subdirectory.
3. The API can now be build using either make, nmake, or the Visual Studio IDE (VS 2005 and higher). See the README.txt file for further details.

Contact Objective Systems for pricing and licensing options for any of these APIs