Operation void terminateAndMap (), in Class ConnectionTerminationPoint

Documentation
Terminates and maps the CTP such that it will be able to support connections at lower (client) rates (actually, such that the CTP's contained (client) CTPs can be used for connections at their native (lower) rates). E.g., for an STS1 CTP, successfully terminating and mapping the CTP will allow for support of lower rate connections such as VT1.5 connections.
If the CTP is already terminated and mapped, the operation will succeed.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when CTP does not support termination and mapping.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. UNABLE_TO_COMPLY - Raised when CTP is involved in an existing, active cross connection at the CTP's
native rate (CTP's layerRate) (i.e., the CTP's "connectionState" attribute value is something other than
"NOT_CONNECTED"; the CTP is not in a valid state).
4. NE_COMM_LOSS - Raised when EMS is unable to communicate with NE.

Protocol |  | Qualification |
Exceptions |  | Size |
Time |  | Concurrency | Sequential
Export Control | PublicAccess |  |

Preconditions
The CTP has to be able to get terminated and mapped (i.e., needs to have mapping mode flexibility) but may be potential (i.e., is created by this operation).
Postconditions
1. The CTP can provide client layer capacity to its contained potential or actual CTPs, i.e. can act as a server layer CTP and
adapt and multiplex traffic to the client layer.
2. The server layer trail termination function is available.
3. Alarm reporting on the CTP is disabled unless the CTP existed before and had alarm reporting enabled.
Semantics