You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Call Termination Reason Codes

ID

Definition

Q.931 Standard (0-127)

0

INVALID DISCONNECT REASON

1

UNALLOCATED NUMBER
(Because the

Unable to show "metadata-from": No such page "_space_variables"
never generates this internally, this code originates at a switch downstream from this
Unable to show "metadata-from": No such page "_space_variables"
.)

2

NO ROUTE TO SPECIFIED NETWORK

3

NO ROUTE TO DESTINATION

[Sonus codes 138 and 139 are mapped to this ID. This mapping is performed before ISUP Release Message is sent. The "underlying" Sonus code is placed into accounting record.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if:

  • No routes are configured on PSX for this destination.
  • The PSX loses connectivity to Oracle DB server and hence is unable to perform routing)

4

SEND SPECIAL INFO TONE

5

MISDIALED TRUNK PREFIX

6

CHANNEL UNACCEPTABLE

7

CALL AWARDED

8

PREEMPTION

9

PREEMPTION - CIRCUIT RESERVED

12

VALUE NOT CODED

16

NORMAL ROUTE CLEARING
[ISUP codes 12, 32, and 36 are mapped to this ID]

17

USER BUSY

18

NO USER RESPONDING

(The SBC may release a call with this cause value if:

  • The CAS SSP that is executed on an egress call does not have WAIT ANSWER configured as the last step in the sequence. This token is typically configured to await an off hook at the Far-End. In this case, this token is performed by default with a 30 second timeout. If this timer expires then this code is returned.
  • ISDN User Part (ISUP) for an Egress Call releases a call because of an Address Complete Message (ACM) timeout from the SGX. In this case, the SGX forwards Q.931 code 31 (NORMAL UNSPECIFIED) to the PSTN switch.
  • In general, SBC times out waiting for an ISUP ACM or ALERTING or CON message after sending Initial Address Message (IAM) SETUP)

19

NO ANSWER FROM USER

(SBC may release a call with this cause value if ISUP for an egress call releases call because of ANM timeout from SGX. In this case, the SGX forwards Q.931 code 102 (RECOVERY ON TIMER EXPIRY) to PSTN switch)

20

SUBSCRIBER ABSENT

21

CALL REJECTED

22

NUMBER CHANGED

23

UNALLOCATED DESTINATION NUMBER

24

UNKNOWN BUSINESS GROUP

25

EXCHANGE ROUTING ERROR

26

MISROUTED CALL TO PORTED NUMBER
(The SBC may release a call with this cause value if:

  • An LNP translation produces a subscriber that is in a state of transition
  • An LNP translation produces a subscriber that is in a state of ported out
    This could occur either when the PSX initiates the LNP query to the SCP database, or when the PSX receives a policy request where the translation has been performed by a downstream switch.)

27

DESTINATION OUT OF ORDER

28

INVALID NUMBER FORMAT

(The SBC may release a call with this cause value if LNP translation is performed by a downstream switch and General Address Parameter digits sent to the PSX are in an incorrect format, that is, either too many digits or the number type is incorrect.)

29

FACILITY REJECTED

30

RESPONSE TO STATUS ENQUIRY

(ISUP specific and thus not applicable to ISDN, H323, or SIP calls.)

31

NORMAL UNSPECIFIED

[Sonus codes 133, 141, 144, and 145 are mapped to this ID. Mapping is performed before the ISUP Release Message is sent out. The "underlying" Sonus code is placed into the accounting record.]

[ISUP codes 6, 7, 24, and 25 are mapped to this ID]

(The SBC may release a call with this cause value if:

  • ISUP circuits were reset via CLI command, causing all calls on those circuits to be brought down.
  • ISDN circuits were reset via CLI command, causing all calls on those circuits to be brought down.
  • ISDN Channels were restarted by the Far-End switch bringing down all calls on those circuits.
  • CAS circuits were reset via CLI command, causing all calls on those circuits to be brought down.
  • Any other CLI command, such as a command to take a T1 or CNS out of service, causes all calls on those circuits to go down.
  • An ISUP Continuity Test timed out.
  • ISUP circuits were reset by the Far-End switch.
  • Calls were cleared by the SGX because of protocol time-outs.)

32

VALUE NOT CODED

34

NO CIRCUIT AVAILABLE

[Sonus codes 128, 140, and 142 are mapped to this ID. This mapping is performed before the ISUP Release Message is sent out. The "underlying" Sonus code is placed into the accounting record.]

The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if:

  • The
    Unable to show "metadata-from": No such page "_space_variables"
    attempts to initially route the call but none of the routes has any available circuits.
  • Unable to show "metadata-from": No such page "_space_variables"
    attempts to reroute call ("crankback"), but is out of routes or out of routes with available circuits. An attempt to reroute call may have various causes. When this is the result of an attempted reroute, the cause value triggering the reroute is placed into accounting record.
  • A
    Unable to show "metadata-from": No such page "_space_variables"
    software programming error occurred.

35

VALUE NOT CODED

36

VALUE NOT CODED

38

NETWORK OUT OF ORDER

The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if:

  • Gateway-to-Gateway Signaling Link to Far-End
    Unable to show "metadata-from": No such page "_space_variables"
    is lost due to network problems or CLI command. In either event, all calls to that
    Unable to show "metadata-from": No such page "_space_variables"
    are cleared with this disconnect reason.
  • Gateway-to-Gateway Signaling Link to Far-End
    Unable to show "metadata-from": No such page "_space_variables"
    went down and then back up. Afterwards, the
    Unable to show "metadata-from": No such page "_space_variables"
    s audit all calls between them. Any mismatched calls are brought down with this disconnect reason.

39

PERM FM CONNECTION OOS

40

PERM FM CONNECTION OPERATIONAL

41

TEMPORARY FAILURE

[Sonus codes 131, 132, and 136 are mapped to this ID. This mapping is performed before the ISUP Release Message is sent out. The "underlying" Sonus code is placed into the accounting record.]

The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if:

  • Communication between
    Unable to show "metadata-from": No such page "_space_variables"
    and PSX is broken and Policy Requests from the
    Unable to show "metadata-from": No such page "_space_variables"
    to the PSX time out.
  • A Policy Request issued from the
    Unable to show "metadata-from": No such page "_space_variables"
    to the PSX was rejected by the PSX because of corrupted data in the packet - an indication of possible network problems.
  • A
    Unable to show "metadata-from": No such page "_space_variables"
    software programming error occurred.
  • ISUP calls were brought down as a result of corrective action that was performed following a Circuit Query with a Far-End PSTN Switch.
  • Connectivity to SS7 Gateway is lost and all active SS7 Calls in the
    Unable to show "metadata-from": No such page "_space_variables"
    are brought down.
  • The
    Unable to show "metadata-from": No such page "_space_variables"
    received a UCIC ISUP Message from a Far-End PSTN Switch that contained a CIC of an active
    Unable to show "metadata-from": No such page "_space_variables"
    call.
  • Call admission on
    Unable to show "metadata-from": No such page "_space_variables"
    is suspended due to CNS Failure, switchover, standby card synchronization, no NTP time, or other issues. All new call admission requests from other
    Unable to show "metadata-from": No such page "_space_variables"
    s over Gateway-to-Gateway signaling are released to originating gateway with this code.
  • Catastrophic failure such as a CNS failure or a PNS failure occurs on a
    Unable to show "metadata-from": No such page "_space_variables"
    and all affected calls are released. The
    Unable to show "metadata-from": No such page "_space_variables"
    releases these calls back to the originating gateway over the gateway-to-gateway signaling link with this code.
  • T8 Timer expires in ISUP. This timer expires if
    Unable to show "metadata-from": No such page "_space_variables"
    does not receive a COT message from previous switch within T8 Timer duration, when the IAM indicates that a COT is being performed.
    In general when
    Unable to show "metadata-from": No such page "_space_variables"
    is not getting responses from PSX, this indicates IP network congestion or PSX overload. Both are transient conditions that will resolve themselves, hence the use of this code to indicate a temporary failure situation.

42

SWITCHINGEQUIP CONGESTION

43

ACCESS INFORMATION DISCARDED
(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if this code is returned before an ANM/CONNECT message.)

44

REQUESTED CIRCUIT NOT AVAILABLE

45

ANSI PREEMPTION

46

PRECEDENCE CALL BLOCKED

47

RESOURCE UNAVAILABLE UNSPECIFIED[ISUP codes 39, 40, and 45 are mapped to this ID.]

49

QUALITY OF SERVICE UNAVAILABLE

50

REQUESTED FACILITY NOT SUBSCRIBED

51

CALL TYPE INCOMPATIBLE WITH SEREVICE

53

OUTGOING CALL BARRED CUG

54

CALL BLOCKED GROUP RESTRICTIONS

55

INCOMING CALL BARRED CUG
(

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if this code is returned before an ANM/CONNECT message. CUG is CLOSED USER GROUP.)

57

BEARER CAPABILITY NOT AUTHORIZED

58

BEARER CAPABILITY PRESENTLY NOT AVAILABLE

62

INCONSISTENT OUTGOING SUBSCRIBER CLASS

63

SERVICE OR OPTION NOT AVAILABLE UNSPECIFIED

[Sonus code 137 is mapped to this ID. This mapping is performed before the ISUP Release Message is sent out. The "underlying" Sonus code is placed into the accounting record.]

[ISUP codes 49, 51, and 54 are mapped to this ID.]

65

BEARER CAPABILITY NOT IMPLEMENTED

66

CHANNEL TYPE NOT IMPLEMENTED

69

REQUESTED FACILITY NOT IMPLEMENTED

70

ONLY RESTRICTED DIGITAL INFO BEARER CAPABILITY AVAILABLE

79

SERVICE OR OPTION NOT IMPLEMENTED UNSPECIFIED[ISUP code 66 is mapped to this ID.]

80

VALUE NOT CODED

81

INVALID CALL REFERENCE

82

CHANNEL DOES NOT EXIST

83

SUSPENDED CALL NO IDENTITY

84

CALL IDENTITY IN USE

85

NO CALL SUSPENDED

86

CALL IDENTITY CLEARED

87

NOT MEMBER OF CUG

(

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if this code is returned before an ANM/CONNECT message. CUG is CLOSED USER GROUP.)

88

INCOMPATIBLE DESTINATION

90

NON-EXISTENT CUG

91

INVALID NETWORK SELECTION

95

INVALID MESSAGE UNSPECIFIED[ISUP codes 81, 82, 83, 84, 85, and 86 are mapped to this ID.]

96

MANDATORY INFORMATION ELEMENT MISSING

97

MESSAGE TYPE NON-EXISTENT OR NOT IMPLEMENTED

98

MSG TYPE NC NE OR NI(NC is NOT COMPATIBLE. NE is NON EXISTING. NI is NOT IMPLEMENTED. This code typically suggests an incompatibility in the network.)

99

IE NOT IMPLEMENTED

100

INVALID INFORMATION ELEMENT CONTENT

101

MSG NOT COMPATIBLE WITH STATE

102

RECOVERY ON TIMER EXPIRY(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if the internal
Unable to show "metadata-from": No such page "_space_variables"
Call Establishment Timer expires. This interval is 5 minutes.)

103

PARAMETER NOT IMPLEMENTED

110

UNRECOGNIZED PARAMETER

111

PROTOCOL ERROR UNSPECIFIED[ISUP codes 96, 98, 100, and 101 are mapped to this ID.]

[nttfcc ISUP code 102 is mapped to this ID.]

The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if:

  • The PSX could not find routes to a destination because they were filtered out due to protocol conformance errors, according to the conventions cited in GR-317/394.
  • A CAS Call Establishment error that is not configured to be handled in the SSP occurs, causing CAS to release the call with this code.
  • Another error in a CAS SSP/SCP configuration that is being used by a call causes the call to be released with this code.

127

INTERWORKING UNSPECIFIED

The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if:

  • Incoming CAS call goes on-hook while being established and event not configured on SSP.
  • Incoming CAS call goes on-hook after being established.
  • Outgoing CAS call goes on-hook after being established.
Sonus Extensions above 127:

128

RESOURCES ALLOCATION FAILURE[This Sonus code is mapped to Q.931 ID 34.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if:

  • No PSTN circuits are available to hunt.
  • The DSP call resources are exhausted.
  • Call admissions to system are suspended due to event such as switchover, CNS switchover, etc.
  • The
    Unable to show "metadata-from": No such page "_space_variables"
    memory resources are exhausted.)

129

CHANNEL COLLISION BACKOFF[This Sonus code is mapped to Q.931 ID 31.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if a call collision occurs on the selected egress circuit, resulting in backoff and reattempt of the call.)

130

INSUFFICIENT DESTINATION RESOURCES

[This 

Unable to show "metadata-from": No such page "_space_variables"
 code is mapped to Q.931 ID 34.]

(

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if insufficient resources are available on destination gateway and rerouting is invoked to reattempt the call via a different route on the originating gateway.)

131

RESOURCE FAILURE

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 41.]

(

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if a resource that was being used by the call fails and is no longer available. Taking a span out of service could cause this code.)

132

MODULE FAILURE

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 41.]

(

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if a catastrophic failure causes bulk teardown of all calls on the module, and those calls are disconnected. A module failure, a module switchover, a span failure, an SGX that is temporarily placed into "PAUSED" state while calls are active, a
Unable to show "metadata-from": No such page "_space_variables"
-to-SGX IP network failure resulting in loss of connectivity, etc. could cause this code.)

133

MEDIA GATEWAY SERVICE GROUP EGRESS DISCONNECT

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 31.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if an egress disconnect is indicated due to receipt of the MGCP DLCX message.)

134

CONTINUITY CHECK FAILED, BACKOFF

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 31.]

(The SBC may release a call with this cause value if a continuity check on an egress circuit fails, resulting in backoff and reattempt of the call on a different circuit.)

135

COLLISION REATTEMPT EXHAUSTED

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 41.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if two consecutive collisions occur on the egress ISUP/ISDN/CAS circuit. For PSTN-PSTN calls, after one reattempt, or two collisions, the call is released with this code. For PSTN-IP-IP-PSTN calls, the call is reattempted using the next route in the list.)

136

CONTINUITY REATTEMPT EXHAUSTED

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 31.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if two consecutive continuity tests on the selected egress circuits fail. After one reattempt, the call is released with this code.)

137

NO ROUTE FOR BEARER CAPABILITY

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 63.]

(

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if PSX routing lookup fails because no route with the Bearer Capability required for this call exists on PSX.)

138

NO ROUTE SIGNALING

[This Sonus code is mapped to Q.931 ID 3.]

(

Unable to show "metadata-from": No such page "_space_variables"
may release call with this cause value if PSX routing lookup fails because no route with signaling required for this call exists on PSX.)

139

NO ROUTE DIRECTION

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 3.]

(

Unable to show "metadata-from": No such page "_space_variables"
may release call with this cause value if PSX routing lookup fails because no route with direction required for this call exists on PSX.)

140

CIRCUIT ENDPOINT RESOURCE ALLOCATION FAILURE

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 34.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if the circuit is released after being selected. Events such as a NIF being placed out of service or a port going into alarm may cause this code.)

141

DISCONNECT WITH NEW DESTINATION

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 31.]

(The SBC may release a call with this cause value if the egress circuit is released while the ingress call is rerouted to a new destination, or the call is transferred.)

142

AUTOMATIC CONGESTION CONTROL PROCEDURE

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 34.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if Automatic Congestion Control (ACC) is configured, insufficient resources are detected at the far end, and the call is cancelled. When ACC is active, calls may be rerouted or cancelled, depending on:

  • current congestion level
  • Alternate Route versus Direct Route requirements
  • Percentage of calls to be rerouted versus cancelled
    This release code indicates that this call was cancelled, rather than rerouted.)

143

ACC ALTERNATE ROUTE

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 31.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if Automatic Congestion Control (ACC) is configured, insufficient resources are detected at the far end, and the call is rerouted. When ACC is active, calls may be rerouted or cancelled, depending on:

  • current congestion level
  • Alternate Route versus Direct Route requirements
  • Percentage of calls to be rerouted versus cancelled
    This release code indicates that this call was rerouted, or reattempted on an alternate route.)

144

PACKET LOSS EXCEEDS THRESHOLD

[This

Unable to show "metadata-from": No such page "_space_variables"
code is mapped to Q.931 ID 31.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if RTCP disconnects the call because the measured packet loss within a specified timeframe exceeds a configured threshold. This timeframe, the RTCP Sender Report interval, and the threshold value are specified in the PSX Packet Service Profile.)

145

NO RTP OR RTCP PACKETS

[This

Unable to show "metadata-from": No such page "_space_variables"
 code is mapped to Q.931 ID 31.]

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if RTCP disconnects the call because no RTP or RTCP packets were received within the specified timeframe. This timeframe is two RTCP Sender Report intervals, as specified in the PSX Packet Service Profile. This absence of packets for this timeframe is "loss of RTP bearer channel".)

146

HOP COUNTER EXHAUSTED

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value if the call was terminated because the ISUP hop counter was exhausted; not applicable to ISDN, H323, or SIP calls.)

147

CONVERSION FAILURE

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause value because the Gateway to Gateway Signaling protocol could not convert an MCS message.)

148

CPC_DISC_CONGESTION_REROUTE_NOT_PERMITTED

(The

Unable to show "metadata-from": No such page "_space_variables"
may release calls that utilize the BT-IUP service with this cause value.)

149

CPC_DISC_

Unable to show "metadata-from": No such page "_space_variables"
_INCOMPATIBLE_DESTINATION

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code if the
Unable to show "metadata-from": No such page "_space_variables"
version running on the destination Gateway is not compatible with the
Unable to show "metadata-from": No such page "_space_variables"
version running on the originating Gateway.)

150

CPC_DISC_NO_PSX_ROUTES

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code if a policy response from the PSX that contains routes is received with no routes.)

151

CPC_DISC_SETUP_REQ_TIMER_EXPIRY

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code if there is a timer expiry on a setup request, for example no response by the peer to a SIP INVITE message on the egress call leg. This reason code is in the default crankback profile, and will cause crankback on the next route returned by PSX for the destination.)

152

CPC_DISC_GW_CONGESTED

(The remote

Unable to show "metadata-from": No such page "_space_variables"
may release a gateway-to-gateway call with this cause code to indicate that gateway is congested. The local
Unable to show "metadata-from": No such page "_space_variables"
will then skip any additional routes in the route list for that call that go to the congested gateway.)

153

CPC_DISC_GLARE_OCCURRED

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code when GLARE prevents a call from setting up. Hence this cause code will populate the Call Disconnect Reason Field in an ATTEMPT record.)

154

CPC_DISC_NO_TERM_CIT_RCVD

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code if the "Terminating carrier information" or "Terminating CA" parameter in SIP message is not received before Answer state. Based on IP signaling control flag "Disconnect If Neither Terminating CA Nor CIC Received.")

155

CPC_DISC_BUSY_EVERYWHERE

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a High Probability of Completion (HPC) call with this cause code to indicate that all routes have failed.)

156

CPC_DISC_REASON_UNKNOWN_RESOURCE_PRIORITY

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a High Probability of Completion (HPC) call with this cause code when a bad resource priority header (RPH) is recieved in a SIP message.)

157

CPC_DISC_REASON_BAD_EXTENSION

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code when the required SIP Extension is not supported.)

158

CPC_DISC_REASON_QUEUE_TIMEOUT

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a queued High Probability of Completion (HPC) call with this cause code if a queue timeout has occurred.)

159

CPC_DISC_REASON_FORBIDDEN

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code if High Probability of Completion HPC treatment cannot be applied.)

161

CPC_DISC_REASON_QUEUEING_IMPOSSIBLE

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a High Probability of Completion (HPC) call with this cause code because there are no available circuits and the call cannot be queued because queuing limits will be exceeded, or because queuing is not enabled.)

166

CPC_DISC_PDD_TIMER_EXPIRED

(The

Unable to show "metadata-from": No such page "_space_variables"
may release a call with this cause code if disconnect happens due to PDD Timer expiry in the ATTEMPT Record.)

176

CPC_DISC_TG_AUTH_FAIL

(The

Unable to show "metadata-from": No such page "_space_variables"
may release the call with this error code, if the request with credentials is rejected with non 401/407. This cause code is mapped to SIP error cause code of 403. This cause code can be configured to map to any SIP error cause.)

177

CPC_DISC_TG_AUTH_FAIL_401_407

(If the request with credentials is rejected with non 401/407, the call is rejected with new internal cause code. This cause code can be mapped to any SIP error cause code. By default, it is mapped to SIP cause code 403. This cause code can be configured to map to any SIP error cause.)

  • No labels