# NaturalAccess environment

This topic provides background information about NaturalAccess and summarizes the main elements of the NaturalAccess environment. You must have NaturalAccess installed on your system to build applications using Fusion MSPP functions.

For detailed information about NaturalAccess, refer to the Dialogic® NaturalAccess™ Software Developer's Manual.

This topic discusses:

- Synchronous and asynchronous functions

- NaturalAccess OAM API

## Synchronous and asynchronous functions

NaturalAccess employs an asynchronous programming model to take advantage of concurrent processing. When called, most functions return immediately indicating the operation was initiated. The application can then perform other functions while NaturalAccess is processing the command.

There are two types of functions in NaturalAccess: synchronous and asynchronous.

- Synchronous functions are complete when the return value is received. The return value may be either SUCCESS or an error code.

- Asynchronous functions return events that indicate the success or failure of the operation, and if the operation fails, may return the reason for this failure (in the value field of the event).

As shown in the following illustration, for asynchronous functions, NaturalAccess sends a command to the service that sends a command to a telephony board. The board performs the requested functions and sends events to the service indicating its state (for example, the function was started or the function is complete). The service sends events to NaturalAccess, which makes them available to the application.

## NaturalAccess OAM API

The NaturalAccess OAM API provides an API for the OAM software. The OAM API provides tools that applications can use to monitor and manage telephony resources in a system. Use the OAM API to configure and initialize the Dialogic hardware in your chassis. The OAM API can manage:

- Hardware components, such as CG boards.

- Software components, such as the Dialogic Hot Swap process.

Using the OAM API, you can:

- Create, delete, and query a board configuration.

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

- Receive notifications from managed components.

Software processes supported by the OAM API include:

- Hot Swap: the ability to insert and extract CompactPCI boards without powering down the system.

- Clock management: the ability to configure the CT bus clock across all boards in an H.110 system.

For general information about OAM API, refer to the Dialogic® NaturalAccess™ OAM System Developer's Manual. For information about the OAM API, refer to the Dialogic® NaturalAccess™ OAM API Developer's Manual.