The signaling platform is external to the network equipment, and provides the execution environment for the signaling component. This platform could be a standard OS such as Linux or Unix; or, it could be a real-time OS such as Embedded Linux or VxWorks. The OIF UNI-C signaling functionality is implemented in the signaling software component. It provides an interface (for example, a command line interface) to let the user set configuration parameters, to invoke OIF signaling actions, and displays the results of actions invoked. An example of a configuration parameter is the manual assignment of IPCC (IP control channel) signaling address; examples of signaling actions that the user may invoke are creation and deletion of optical trails terminating at this equipment; and, the results of these actions are displayed at the interface. The proxy agent component integrates the equipment operation with the signaling module, and runs on the same OS as the signaling component. It is responsible for converting messages between the OIF format and the proprietary commands used by the customer equipment, thereby decoupling the proprietary commands from the standard OIF UNI messages. This component is developed by MindTree with information and inputs from the customer.

The use of the signaling proxy approach leaves the customer free to innovate on the equipment. For instance, new hardware capabilities could be added, and corresponding proprietary control commands may be defined. To maintain OIF UNI-C compatibility, changes are required only in the proxy agent software. External equipment (such as a device capable of OIF UNI-N signaling) continues to use the same OIF UNI signaling to work with the customer device.

	OIF 2000.125
	OIF 2001.152