(Page 1 of 1 in this chapter) Version

Appendix D

Status Indications

Error
Reattempt
Continuity Check
Continuity Report
Stop Continuity
Loop Back Acknowledgment
Confusion Indication
Circuit Reservation Request
Circuit Reservation Acknowledgment
Circuit Group Query Response
Circuit Block Request
Circuit Block Response
Circuit Unblock Request
Circuit Unblock Response
Circuit Reset Request
Circuit Group Block Request
Circuit Group Block Response
Circuit Group Unblock Request
Circuit Group Unblock Response
Circuit Unequipped
MTP Pause Indication
MTP Resume Indication
Remote User Unavailable Indication
Remote User Available Indication
MTP Congestion Indication
MTP Stop Congestion Indication

Error

For ERROR status indications, the cause token of the cause diagnostic (causDgn) information element with one of the following values.
Cause Value

 Meaning

CCNORTTOTSFNET

 The ISUP layer could not find a route matching the transient network ID supplied in the request. Not generated if application performs circuit selection.

CCNORTTODEST

 The ISUP layer could not find a route matching the called party address supplied in the request, or neither transient network ID or called party address were supplied. Not generated if application performs circuit selection.

CCNOCIRCUIT

 The ISUP layer could not find a circuit matching the transmission medium and/or ISDN user profiles supplied in the request. Not generated if application performs circuit selection.

CCINVALCALLREF

 The values supplied for service provider instance ID and/or service provider instance ID are invalid.

CCSWTCHCONG

 No call references were available to satisfy the request, or the requested circuit is busy.

CCRESCUNAVAIL

 There is insufficient memory for the ISUP layer to satisfy the request.

CCREQUNAVAIL

 The requested circuit is not configured.

CCDESTOUTORD

 The requested circuit has been marked unavailable due to receipt of a pause or user part unavailable status indication from MTP.

CCPROTERR

 The circuit ID supplied is invalid for the supplied service provider instance ID, the request is invalid for the configured switch type, or the request is invalid for the current circuit or group state.

CCINVALPARAMCONT

 The value specified in an IE is invalid.

CCINFOELMSSG

 A mandatory IE was not supplied.

Reattempt

The following are the cause values associated with reattempt status indications.
Cause value

 Meaning

CCREQUNAVAIL

 If the application selected the circuit, this value indicates that the requested circuit is not configured. If ISUP is performing circuit selection, this value indicates that no circuit is available.

CCSWTCHCONG

 An overload message was received from the network, or the requested circuit is busy or reserved

CCRESCUNAVAIL

 The outbound call lost a glare situation and should be retried on another circuit. The inbound call indication will follow this event.

Continuity Check

A continuity check (CONTCHK) status indication is delivered to the application when the ISUP layer receives a continuity check request message (CCR) from the far exchange. Upon receipt of this indication, the application should take the necessary steps to connect a continuity check loop to the referenced circuit. The application then indicates the loop is in place by sending a loopback acknowledgment using the ISUPStatusReq primitive.

Continuity Report

A continuity report (CONTREP) status indication is delivered to the application when the ISUP layer receives a continuity report message (COT) from the far exchange. Upon receipt of this indication, the application should take the necessary steps to remove the continuity check loop from the referenced circuit.

Stop Continuity

A stop continuity (STPCONTIN) status indication is delivered to the application when the ISUP layer receives a release message (REL) from the far exchange during continuity testing. Upon receipt of this indication, the application should take the necessary steps to remove the continuity check loop/tone from the referenced circuit.

Loop Back Acknowledgment

A loop back acknowledgment (LOOPBCKACK) status indication is delivered to the application when the ISUP layer receives a loop back acknowledgment message (LPA) from the far exchange. Upon receipt of this indication, the application should take the necessary steps to check the transmission path of the referenced circuit. The application then indicates the completion of the continuity check by sending a continuity report message using the ISUPStatusReq primitive.

Confusion Indication

A confusion (CONFUSION) status indication is delivered to the application when the ISUP layer receives a confusion message (CFN) from the far exchange.

Circuit Reservation Request

A circuit reservation (CIRRESERVE) indication is delivered to the application when the ISUP layer receives a circuit reservation message (CRM) from the far exchange. Upon receipt of this indication, the application should consider the referenced circuit to be busy. The application then indicates the receipt of the circuit reservation message by sending a circuit reservation acknowledgment message using the ISUPStatusReq primitive.

Circuit Reservation Acknowledgment

A circuit reservation acknowledgment (CIRRESERVEACK) indication is delivered to the application when the ISUP layer receives a circuit reservation acknowledgment message (CRA) from the far exchange. The application should then initiate a connection on the referenced circuit before the far exchange times out.

Circuit Group Query Response

A circuit group query response (CIRGRPQRYRSP) indication is delivered to the application when the ISUP layer receives a circuit group query response message (CQR) from the far exchange. The rangStat and cirStateInd members of the status event (SiStaEvnt) structure will be populated when CIRGRPQRYRSP indications are delivered to the application.

Circuit Block Request

A circuit block request (CIRBLKREQ) indication is delivered to the application when the ISUP layer receives a blocking message (BLO) from the far exchange. The application should consider the referenced circuit to be remotely blocked. The application should then acknowledge the blocking message by sending a blocking acknowledgement message using the ISUPStatusReq primitive.

Circuit Block Response

A circuit block response (CIRBLKRSP) indication is delivered to the application when the ISUP layer receives a blocking acknowledgment message (BLA) from the far exchange. The application should consider the referenced circuit to be locally blocked.

Circuit Unblock Request

A circuit unblock request (CIRUNBLKREQ) indication is delivered to the application when the ISUP layer receives an unblocking message (UBL) from the far exchange. The application should consider the referenced circuit to be remotely unblocked. The application should then acknowledge the unblocking message by sending an unblocking acknowledgement message using the ISUPStatusReq primitive.

Circuit Unblock Response

A circuit unblock response (CIRUNBLKRSP) indication is delivered to the application when the ISUP layer receives an unblocking acknowledgment message (UBA) from the far exchange. The application should consider the referenced circuit to be locally unblocked.

Circuit Reset Request

A circuit reset (CIRRESREQ) indication is delivered to the application when the ISUP layer receives a reset message (UBL) from the far exchange, or a reset was initiated by the management API. The application should consider the referenced circuit to be idle.

Circuit Group Block Request

A circuit group block request (CIRGRPBLKREQ) indication is delivered to the application when the ISUP layer receives a circuit group blocking message (CGB) from the far exchange. The application should consider the referenced circuits to be remotely blocked. The application should then acknowledge the circuit group blocking message by sending a circuit group blocking acknowledgement message using the ISUPStatusReq primitive. The rangStat member of the status event (SiStaEvnt) structure will be populated when CIRGRPBLKREQ indications are delivered to the application.

Circuit Group Block Response

A circuit group block response (CIRGRPBLKRSP) indication is delivered to the application when the ISUP layer receives a circuit group blocking acknowledgment message (CGBA) from the far exchange. The application should consider the referenced circuits to be locally blocked. The rangStat member of the status event (SiStaEvnt) structure will be populated when CIRGRPBLKRSP indications are delivered to the application.

Circuit Group Unblock Request

A circuit group unblock request (CIRGRPUNBLKREQ) indication is delivered to the application when the ISUP layer receives a circuit group unblocking message (CGU) from the far exchange. The application should consider the referenced circuits to be remotely unblocked. The application should then acknowledge the circuit group unblocking message by sending a circuit group unblocking acknowledgement message using the ISUPStatusReq primitive. The rangStat member of the status event (SiStaEvnt) structure will be populated when CIRGRPUNBLKREQ indications are delivered to the application.

Circuit Group Unblock Response

A circuit group unblock response (CIRGRPUNBLKRSP) indication is delivered to the application when the ISUP layer receives a circuit group unblocking acknowledgment message (CGUA) from the far exchange. The application should consider the referenced circuits to be locally unblocked. The rangStat member of the status event (SiStaEvnt) structure will be populated when CIRGRPUNBLKRSP indications are delivered to the application.

Circuit Unequipped

A circuit unequipped (CIRUNEQPD) status indication is delivered to the application when the ISUP layer receives a unequipped CIC message (UCIC) from the far exchange.

MTP Pause Indication

One or more MTP pause (MTPPAUSE) indications are delivered to the application when the ISUP layer receives a pause indication from the MTP 3 layer. The rangStat member of the status event structure (SiStaEvnt) will be populated when MTPPAUSE indications are delivered to the application. The range value will indicate the number of affected circuits minus one. The circuit member of the IsupRcvInfoBlk will indicate the first affected circuit. Affected circuits should be considered to be out of service.

MTP Resume Indication

One or more MTP resume (MTPRESUME) indications are delivered to the application when the ISUP layer receives a resume indication from the MTP3 layer. The rangStat member of the status event structure (SiStaEvnt) will be populated when MTPRESUME indications are delivered to the application. The range value will indicate the number of affected circuits minus one. The circuit member of the IsupRcvInfoBlk will indicate the first affected circuit. Affected circuits should be considered to be idle.

Remote User Unavailable Indication

One or more remote user unavailable (RMTUSRUNAVAIL) indications are delivered to the application when the ISUP layer receives a remote user unavailable indication from the MTP 3 layer. The rangStat member of the status event structure (SiStaEvnt) will be populated when RMTUSRUNAVAIL indications are delivered to the application. The range value will indicate the number of affected circuits minus one. The circuit member of the IsupRcvInfoBlk will indicate the first affected circuit. Affected circuits should be considered to be out of service.

Remote User Available Indication

One or more remote user available (RMTUSRAVAIL) indications are delivered to the application when the ISUP layer detects that the remote user is available. The rangStat member of the status event structure (SiStaEvnt) will be populated when RMTUSRAVAIL indications are delivered to the application. The range value will indicate the number of affected circuits minus one. The circuit member of the IsupRcvInfoBlk will indicate the first affected circuit. Affected circuits should be considered to be idle.

MTP Congestion Indication

One or more MTP congestion (MTPCONGEST) indications are delivered to the application when the ISUP layer receives a congestion indication from the MTP 3 layer. The rangStat member of the status event structure (SiStaEvnt) will be populated when MTPCONGEST indications are delivered to the application. The range value will indicate the number of affected circuits minus one. The circuit member of the IsupRcvInfoBlk will indicate the first affected circuit. The application should avoid using affected circuits until an MTP stop congestion (MTPSTOPCONGEST) is received.

MTP Stop Congestion Indication

One or more MTP stop congestion (MTPSTOPCONGEST) indications are delivered to the application when the ISUP layer receives a stop congestion indication from the MTP 3 layer. The rangStat member of the status event structure (SiStaEvnt) will be populated when MTPSTOPCONGEST indications are delivered to the application. The range value will indicate the number of affected circuits minus one. The circuit member of the IsupRcvInfoBlk will indicate the first affected circuit.


(Page 1 of 1 in this chapter) Version

tech_support@nmss.com
Copyright © 2000, Natural MicroSystems, Inc. All rights reserved.