# NaturalAccess

Fusion gateway applications use the NaturalAccess development environment for performing voice and call processing operations on NaturalAccess boards. The following illustration shows an overview of NaturalAccess components:

This topic provides information about:

- NaturalAccess features

- Contexts and event queues

- NaturalAccess APIs

- NaturalAccess OAM API

## NaturalAccess features

NaturalAccess provides:

- A standard hardware-independent application programming interface.

- Sets of telephony functions grouped into logical services.

- An interface for accessing and changing service parameters.

- Error trapping features.

- An architecture that supports as-needed resource allocation.

- Support for both single-threaded and multi-threaded programming models to meet a variety of application program requirements.

- Multiple operating system support.

## Contexts and event queues

In the NaturalAccess development environment, a context organizes services and accompanying resources around a single processing context
. A context usually represents an application instance controlling a single telephone call.

An event queue is the communication path from a NaturalAccess service to an application. A NaturalAccess service generates events indicating certain conditions or state changes and sends them to applications through the event queue.

## NaturalAccess APIs

NaturalAccess APIs provide functions for establishing and maintaining network connections, determining call status, playing and recording voice messages, and generating and detecting DTMF and tones and controlling CT bus switching. Refer to the Dialogic® NaturalAccess™ Software Developer’s Manual for a list of available NaturalAccess APIs.

Fusion software includes the MSPP API for creating and controlling media connections between PSTNs and IP networks. For information about the MSPP API, refer to the Dialogic® NaturalAccess™ Media Stream Protocol Processing API Developer's Manual.

## NaturalAccess OAM API

The NaturalAccess OAM API provides a mechanism for applications to configure and manage board resources in gateway systems. Use the OAM API to configure and initialize the hardware in the chassis by managing:

- Hardware components, such as AG or CG Series boards.

- Software components, such as the Hot Swap process.

Using the OAM API, you can:

- Create, delete, and query the configuration of a board managed component.

- Start (boot), stop (shut down), and test a managed component.

- Receive notifications from managed components.

For more information, refer to the Dialogic® NaturalAccess™ OAM System Developer’s Manual and the Dialogic® NaturalAccess™ OAM API Developer's Manual.