Operation void unTerminateAndUnmap (), in Class ConnectionTerminationPoint

Documentation
Unterminates and unmaps the CTP such that it will be able to support connections at its native rate (i.e., its native layerRate). E.g., for an STS1 CTP, successfully unterminating and unmapping the CTP will allow for support of connections at the STS1 rate.
If it is already neither terminated nor available for mapping, the operation will succeed.
Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when CTP does not support untermination and unmapping.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. NABLE_TO_COMPLY - Raised when CTP is supporting (containing) one or more lower order (client) CTPs that
are involved in existing, active cross connections at the lower order CTP rates (i.e., the "connectionState"
attribute value for all lower order (client, or contained) CTPs must be "NOT_CONNECTED" to avoid this exception).
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 unterminated and unmapped (i.e., needs to have mapping mode flexibility).
Postconditions
1. The CTP can no longer provide client layer capacity to its contained potential CTPs, i.e. can not act as a server layer CTP and can not adapt and multiplex traffic to the client layer.
2. The server layer trail termination function is unavailable.
3. The CTP is available for cross-connection at its connectable layer rate.
4. The alarm reporting state of the CTP is unchanged.
5. The CTP may be deleted, i.e. become potential, on discretion of the EMS.
Semantics