Mensagens do ISUP

Address Complete Message (ACM)

A message sent in the backward direction indicating that all the address signals required for routeing the call to the called party have been received.

Answer message (ANM)

A message sent in the backward direction indicating that the call has been answered. In semi-automatic working, this message has a supervisory function. In automatic working, this message is used in conjunction with charging information in order to: start metering the charge to the calling subscriber (see Recommendation Q.28 [2]); and start measurement of call duration for international accounting purposes (see Recommendation E.260 [3]).

Application Transport message (APM)

A message sent in either direction to convey application information using the Application Transport mechanism.

Blocking message (BLO)

A message sent only for maintenance purposes to the exchange at the other end of a circuit, to cause an engaged condition of that circuit for subsequent calls outgoing from that exchange. When a circuit is used in the bothway mode of operation, an exchange receiving the blocking message must be capable of accepting incoming calls on the concerned circuit unless it has also sent a blocking message. Under certain conditions, a blocking message is also a proper response to a reset circuit message.

Blocking Acknowledgement message (BLA)

A message sent in response to a blocking message indicating that the circuit has been blocked.

Call Progress message (CPG)

A message, sent in either direction during the setup or active phase of the call, indicating that an event, which is of significance, and should be relayed to the originating or terminating access, has occurred.

Charge information message (CRG)

Information sent in either direction for accounting and/or call charging purposes.

Circuit Group Blocking message (CGB)

A message sent to the exchange at the other end of an identified group of circuits to cause an engaged condition of this group of circuits for subsequent calls outgoing from that exchange. An exchange receiving a circuit group blocking message must be able to accept incoming calls on the group of blocked circuits unless it has also sent a blocking message. Under certain conditions, a circuit group blocking message is also a proper response to a reset circuit message.

Circuit Group Blocking Acknowledgement message (CGBA)

A message sent in response to a circuit group blocking message to indicate that the requested group of circuits has been blocked.

circuit Group Reset message (GRS)

A message sent to release an identified group of circuits when, due to memory mutilation or other causes, it is unknown whether for example, a release or release complete message is appropriate for each of the circuits in the group. If at the receiving end a circuit is remotely blocked, reception of this message should cause that condition to be removed.

circuit Group Reset Acknowledgement message (GRA)

A message sent in response to a circuit group reset message and indicating that the requested group of circuits has been reset. The message also indicates the maintenance blocking state of each circuit.

Circuit Group Unblocking message (CGU)

A message sent to the exchange at the other end of an identified group of circuits to cause cancellation in that group of circuits of an engaged condition invoked earlier by a blocking or circuit group blocking message.

Circuit Group Unblocking Acknowledgement message (CGUA)

A message sent in response to a circuit group unblocking message to indicate that the requested group of circuits has been unblocked.

Circuit group Query Message (CQM)

A message sent on a routine or demand basis to request the far-end exchange to give the state of all circuits in a particular range.

Circuit group Query Response message (CQR)

A message sent in response to a circuit group query message to indicate the state of all circuits in a particular range.

Confusion message (CFN)

A message sent in response to any message (other than a confusion message) if the exchange does not recognize the message or detects a part of the message as being unrecognized.

Connect message (CON)

A message sent in the backward direction indicating that all the address signals required for routeing the call to the called party have been received and that the call has been answered.

Continuity message (COT)

A message sent in the forward direction indicating whether or not there is continuity on the preceding circuit(s) as well as of the selected circuit to the following exchange, including verification of the communication path across the exchange with the specified degree of reliability.

Continuity Check Request message (CCR)

A message sent by an exchange for a circuit on which a continuity check is to be performed, to the exchange at the other end of the circuit, requesting continuity checking equipment to be attached.

Facility Accepted message (FAA)

A message sent in response to a facility request message indicating that the requested facility has been invoked.

Facility message (FAC)

A message sent in either direction at any phase of the call to request an action at another exchange. The message is also used to carry the results, error or rejection of a previously requested action.

Facility Reject message (FRJ)

A message sent in response to a facility request message to indicate that the facility request has been rejected.

Facility Request message (FAR)

A message sent from an exchange to another exchange to request activation of a facility.

Forward Transfer message (FOT)

A message sent in the forward direction on semi-automatic calls when the outgoing international exchange operator wants the help of an operator at the incoming international exchange. The message will normally serve to bring an assistance operator (see Recommendation Q.101 [4]) into the circuit if the call is automatically set up at the exchange. When the call is completed via an operator (incoming or delay operator) at the incoming international exchange, the message should preferably cause this operator to be recalled.

Identification Request message (IDR)

A message sent in the backward direction to request action regarding the malicious call identification supplementary service.

Identification Response message (IRS)

A message sent in response to the identification request message.

Information message (INF)

A message sent to convey information in association with a call, which may have been requested in an information request message.

Information Request message (INR)

A message sent by an exchange to request information in association with a call.

Initial Address message (IAM): A message sent in the forward direction to initiate seizure of an outgoing circuit and to transmit number and other information relating to the routeing and handling of a call.

Loop back Acknowledgement message (LPA)

A message sent in the backward direction in response to a continuity check request message indicating that a loop (or transceiver in the case of a 2-wire circuit) has been connected.

Loop Prevention message (LOP)

A message sent to convey information required by the ECT supplementary service.

Network Resource Management message (NRM)

A message sent in order to modify network resources associated with a certain call. The message is sent along an established path in any direction in any phase of the call.

Overload Message (OLM)

A message sent in the backward direction, on non-priority calls in response to an IAM, to invoke temporary trunk blocking of the circuit concerned when the exchange generating the message is subject to load control.

Pass-Along Message (PAM)

A message that may be sent in either direction to transfer information between two signalling points along the same signalling path as that used to establish a physical connection between those two points.

Pre-release Information message (PRI)

A message to be used with the Release message for the transport of information where sending of that information in the Release message itself would cause compatibility problems with ISUP 1992 and subsequent versions of the ISUP protocol.

Release message (REL)

A message sent in either direction to indicate that the circuit is being released due to the reason (cause) supplied and is ready to be put into the idle state on receipt of the release complete message. Where the call is to be redirected the message will also carry the redirection number.

Release Complete message (RLC)

A message sent in either direction in response to the receipt of a release message, or if appropriate to a reset circuit message, when the circuit concerned has been brought into the idle condition.

Reset Circuit message (RSC)

A message sent to release a circuit when, due to memory mutilation or other causes, it is unknown whether for example, a release or a release complete message is appropriate. If, at the receiving end, the circuit is remotely blocked, reception of this message should cause that condition to be removed.

Resume message (RES)

A message sent in either direction indicating that the calling or called party, after having been suspended, is reconnected.

Segmentation Message (SGM)

A message sent in either direction to convey an additional segment of an overlength message.

Subsequent Directory Number message (SDM)

A message that may be sent in the forward direction following an Initial Address Message, to convey additional called party number information, when the called party number in the Initial Address Message was contained in the Called Directory Number parameter.

Subsequent Address Message (SAM)

A message that may be sent in the forward direction following an initial address message, to convey additional called party number information.

Suspend message (SUS)

A message sent in either direction indicating that the calling or called party has been temporarily disconnected.

Unblocking message (UBL)

A message sent to the exchange at the other end of a circuit to cancel, in that exchange, the engaged condition of the circuit caused by a previously sent blocking or circuit group blocking message.

Unblocking Acknowledgement Message (UBA)

A message sent in response to an unblocking message indicating that the circuit has been unblocked.

Unequipped Circuit Identification Code message (UCIC)

A message sent from one exchange to another when it receives an unequipped circuit identification code.

User Part Available message (UPA)

A message sent in either direction as a response to a user part test message, to indicate that the user part is available.

User Part Test message (UPT)

A message sent in either direction to test the status of a user part marked as unavailable for a signalling point.

User-to-user information message (USR)

A message to be used for the transport of user-to-user signalling independent of call control messages.