OID repository
OID Repository
https://oid-base.com
Display OID:
 
Action itemitu-t(0) Action itemrecommendation(0) Action itemm(13) Action itemm3100(3100) Action iteminformationModel(0) Action itemaction(9)   Navigating the OID tree
connect(4)
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

connect ACTION
BEHAVIOUR
connectBehaviour BEHAVIOUR
DEFINED AS
"This action is used to establish a connection between termination points or GTPs. The termination points to be connected can be specified in one of two ways:
1) by explicitly identifying the two termination points or GTPs;
2) by specifying one termination point or GTP, and specifying a tpPool from which any idle termination point/GTP may be used. The result, if successful, always returns an explicit list of termination points or GTP.
There are two basic forms of cross-connection arrangement: point-to-point and point to multi-point (broadcast). A single cross-connection is created if either the explicitPtoP or ptoTpPool option is selected in this action. This cross-connection object points to the termination points or GTPs involved in the cross-connection. Connections are indicated in termination points by the connectivityPointer attribute. If the administrativeState in the crossConnection object is unlocked, this attribute is set, as a result of this action, to the local name of the termination point to which it is connected. Also, the crossConnectionObjectPointer in the termination points or GTPs points to the cross-connection object.
For point to multi-point cross-connection (indicated by choosing the explicitPtoMp or ptoMPools option), one multi-point cross-connection object will be created containing one crossConnection object for each termination point specified in the toTps parameter. In the source TP the crossConnectionObjectPointer will point at the newly created Multi-point cross-connect object. In each Tp named in the toTPs list (possibly selected from a specified tpPool), the CrossConnectionObject pointer will point at the corresponding cross-connection object. The connectivity pointers in the connected termination points will be updated to reflect the new connectivity.
The idleTPcount and the connectedTPcount attributes in the tpPool object (if any) are updated as a result of the action. If a GTP is implicitly defined by specifying several termination points to be connected together, the GTP object will be automatically created and its id will be returned in the action reply.
If an Indirect Adaptor is specified, a GTP representing the CTPs contained from the Indirect Adaptor will be created and it will be connected.
The administrative state of the created cross-connection or multi-point cross-connection objects is specified as an optional parameter of this action. If this parameter is omitted, the administrative state will be set to unlocked (unless the addLegs parameter is specified). This action will fail if any of the termination points specified is already involved in a cross-connection or if part of an existing GTP is specified.
If the addLeg parameter is specified, one or more Legs will be added to an existing multi-point cross-connection arrangement. Selected termination points or GTPs must support a similar signal type to that of the termination points already connected to the arrangement. The result, if successful, always returns the termination points or GTPs involved in the multi-point cross-connection. A cross-connection object is created as a result of this action. This object will be named from the specified mpCrossConnection object instance. The administrative state of the created cross-connection object will be the same as that of the containing multi-point cross-connection object unless otherwise specified in the action parameters.";;
MODE CONFIRMED;
WITH INFORMATION SYNTAX ASN1DefinedTypesModule.ConnectInformation;
WITH REPLY SYNTAX ASN1DefinedTypesModule.ConnectResult;



Information:

Automatically extracted from Rec. ITU-T M.3100

 
Short URL for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2024
Parent OID: action(9) First sibling OID: addTpsToGTP(1) Previous sibling OID: allowAudibleVisualLocalAlarm(3) Next sibling OID: disconnect(5) Last sibling OID: switchOver(9)
Separation line
OID helper Webmaster Bullet 11 Sep 2008 Bullet Page top