Release (ISUP)
Encyclopedia
Introduction to ISUP Release :
Release codes are usually used to identify and debug any events occurring in ISUP
signaling. Every event in ISUP signaling generates a release code number. Even for a normal ISUP call a release code is generated.There are lot of applications developed based on the release code from ISUP signaling. Similarly Telecom operators trace for Release codes to debug any call failures.
So the release code plays a very important role in Telecom signaling.
Following are the List of releases codes used
Number in Release Cause
Release only with number doesn’t define and it is possible to use them for proprietary solution.
Release codes are usually used to identify and debug any events occurring in ISUP
ISDN User Part
The ISDN User Part or ISUP is part of the Signaling System #7 which is used to set up telephone calls in Public Switched Telephone Networks...
signaling. Every event in ISUP signaling generates a release code number. Even for a normal ISUP call a release code is generated.There are lot of applications developed based on the release code from ISUP signaling. Similarly Telecom operators trace for Release codes to debug any call failures.
So the release code plays a very important role in Telecom signaling.
Following are the List of releases codes used
Number in Release Cause
- Unallocated (unassigned) number
- No route to specific transit network
- No route to destination
- Send special info tone
- Misdialed trunk prefixTrunk prefixA trunk prefix is the number to be dialed in a domestic telephone call, preceding any necessary area codes and subscriber numbers. When the number is called from overseas, the trunk prefix is omitted by the caller. In most countries, such as Australia, Germany and the United Kingdom, the trunk...
- Channel unacceptable
- Call awarded and being delivered in established channel
- Preemption
- Preemption - circuit reserved for reuse
- 10
- 11
- 12
- 13
- 14
- 15
- Normal call clearing
- User busy
- No user responding
- No answer from user (user alerted)
- Subscriber absent
- Call rejected
- Number changed
- 23
- 24
- Exchange routing error
- Non-selected user clearing
- Destination out of order
- Invalid number format
- Facility rejected
- Response to STATUS ENQUIRY
- Normal, unspecified
- 32
- 33
- No circuit/channel available
- 35
- 36
- 37
- Network out of order
- Permanent frame mode connection out of service
- Permanent frame mode connection operational
- Temporary failure
- Switching equipment congestion
- Access information discarded
- Requested channel/circuit not available
- 45
- Precedence call blocked
- Resources unavailable, unspecified
- 48
- Quality of serviceQuality of serviceThe quality of service refers to several related aspects of telephony and computer networks that allow the transport of traffic with special requirements...
unavailable - Requested facility not subscribed
- 51
- 52
- Outgoing calls barred within CUG
- 54
- Incoming calls barred within CUG
- 56
- Bearer capabilityBearer CapabilityBearer Capability is one of the Information Elements of the Q.931 SETUP message. It is used by the calling party to specify the kind of B channel that is being requested....
not authorized - Bearer capability not presently available
- 59
- 60
- 61
- Inconsistency in designed outg. access inf. and subscr. class
- Service or option not available, unspecified
- 64
- Bearer capability not implemented
- Channel type not implemented
- 67
- 68
- Requested facility not implemented
- Only restricted digital bearer cap. is available
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- Service or option not implemented, unspecified
- 80
- Invalid call reference value
- Identified channel does not exist
- A suspended call exists, but this call identity does not
- Call identity in use
- No call suspended
- Call having the requested call identity has been cleared
- User not member of CUG
- Incompatible destination
- 89
- Non-existing CUG
- Invalid transit network selection
- 92
- 93
- 94
- Invalid message, unspecified
- Mandatory information element is missing
- Message type non-existing or not implemented
- Message incompatible with call state or mesg type non-existent or not implemented
- Information element non-existent or not implemented
- Invalid information element contents
- Message not compatible with call state
- Recovery on timer expiry
- Parameter non-existent or not implemented - passed on
- 104
- 105
- 106
- 107
- 108
- 109
- Message with unrecognized parameter discarded
- Protocol error, unspecified
- 112
- 113
- 114
- 115
- 116
- 117
- 118
- 119
- 120
- 121
- 122
- 123
- 124
- 125
- 126
- Interworking, unspecified
Release only with number doesn’t define and it is possible to use them for proprietary solution.