ISUP RELEASE CAUSE
Jul 12, 2010 at 11:30 pm in SS7 by LT contributor
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
| ISUP RELEASE CAUSE | ||
| S.No | Rel Cause Value | ITU-T Description |
| 1 | 1 | Unallocated (unassigned) number |
| 2 | 3 | No route to destination |
| 3 | 5 | Misdialled trunk prefix (national use) |
| 4 | 16 | Normal call clearing |
| 5 | 17 | User busy |
| 6 | 18 | No user responding |
| 7 | 19 | No answer from user (user alerted) |
| 8 | 20 | Subscriber absent |
| 9 | 21 | Call rejected |
| 10 | 22 | Number changed |
| 11 | 27 | Destination out of order |
| 12 | 28 | Invalid number format (address incomplete) |
| 13 | 31 | Normal, unspecified |
| 14 | 34 | No circuit/channel available |
| 15 | 38 | Network out of order |
| 16 | 41 | Temporary failure |
| 17 | 42 | Switching equipment congestion |
| 18 | 44 | Requested circuit/channel not available |
| 19 | 47 | Resource unavailable, unspecified |
| 20 | 50 | Requested facility not subscribed |
| 21 | 57 | Bearer capability not authorized |
| 22 | 63 | Service or option not available, unspecified |
| 23 | 65 | Bearer capability not implemented |
| 24 | 69 | Requested facility not implemented |
| 25 | 88 | Incompatible destination |
| 26 | 95 | Invalid message, unspecified |
| 27 | 102 | Recovery on timer expiry |
| 28 | 111 | Protocol error, unspecified |
| 29 | 127 | Interworking, unspecified |
1) can you please brief on SS7 stack and ss7 call flow and also on sigtran.
2) GPRS call flow end to end.