Nokia Net Monitor description (DCT3)

MAIN PAGE

< PREVIOUS PAGE NEXT PAGE >

Test 39 – Reason for Last Call Release

Available in: 2100, 3330, 5110, 6150, 6210, 7110, 8210, 8250

Test screen Help screen
Test 39 Test 39 Help

CC: The reason for the last call release in the Call Control sub-layer.

MM: The reason for the last call release at the Mobility Management sub-layer.

RR: The reason for the last call release at the Radio Resource sub-layer.

This test allows the user to see in more detail the reason a particular call ended, and at which sub-layer of the layer 3 protocol it occurred in. The layers of the GSM system on the MS-BTS interface are described in GSM 04.04 (layer 1), GSM 04.05, GSM 04.06 (layer 2), GSM 04.07, GSM 04.08 (layer 3).

The individual cause values are described in Annex F (RR), Annex G (MM) and Annex H (CC) of GSM 04.08, however, the more common ones are summarized below:

Radio Resource:
  • 0 – Normal release of RR connection.
  • 1 – Abnormal release, reason not specified
  • 2 – Channel unacceptable
  • 3 – Timer expiry (one of the timers expired and the connection was released)
  • 4 – No activity on radio path (the BTS does not detect transmission when there is supposed to be)
  • 5 – Preemptive release
  • *8 – Handover impossible; timing advance (TA) out of range
  • *9 – Channel mode unacceptable (MS cannot support the channel configuration assigned by the network)
  • 65 – Call already cleared – the handover failed as the connection had already been released
Causes 95-111 are associated with protocol error
  • 95 – Semantically incorrect message
  • 96 – Invalid mandatory information
  • 97 – Message type non-existent or not implemented
  • 98 – Message type not compatible with protocol state
  • 100 – Conditional IE error
  • 101 – No cell allocation available
  • 111 – Protocol error unspecified
* These causes are sent to the network, otherwise the cause is sent by the network (in CHANNEL RELEASE message)


Mobility Management:
  • 2 – IMSI unknown in HLR – The IMSI is not known by the network
  • 3 – Illegal MS – the MS is refused service as the authentication failed
  • 4 – IMSI unknown in VLR
  • 5 – IMEI not accepted – network does not allow emergency calls using IMEI as identification
  • 6 – Illegal ME – sent when the network does not accept the IMEI, i.e. due to stolen phone blacklisting
  • 11 – PLMN not allowed – used when the MS attempts location updating and the network forbids it to
  • 12 – Location area not allowed – used when the MS attempts location updating in an area the network forbids it to
  • 13 – Roaming not allowed in this area – used when the MS attempts location updating in an area it is roaming and the network forbids it to.
  • 17 – Network failure – the network sends this if a fault has developed in the network
  • 22 – Congestion – the network sends this if the network has become too congested to proceed
  • 32 – Service option not supported – the network sends this in a CM SERVICE REJECT message when the MS requests an unsupported service in the CM SERVICE REQUEST message.
  • 33 – Service option not allowed due to subscription – the network sends this in a CM SERVICE REJECT message when the MS requests a service it does not have a subscription to (i.e. not enabled on the subscriber's account)
  • 34 – Service option temporarily not available – the network sends this in a CM SERVICE REJECT message when the MS requests a service that is temporarily unavailable due to technical failure
  • 38 – Call cannot be identified – This cause is sent when the MS attempts to re- establish an MM connection after a radio-link failure, however the network was unable to associate the request with the failed connection
Causes 95-111 are associated with protocol error
  • 95 – Semantically incorrect message
  • 96 – Invalid mandatory information
  • 97 – Message type non-existent or not implemented
  • 98 – Message type not compatible with protocol state
  • 100 – Conditional IE error
  • 101 – No cell allocation available
  • 111 – Protocol error unspecified



Call Control:

Normal causes:
  • 16 – Normal call clearing – the call was cleared because one of the users requested it to be cleared
  • 17 – User busy – the called user indicated he was unable to take the call (i.e. rejected the call)
  • 18 – No user responding – the called user’s equipment did not respond
  • 19 – No answer – the called user’s equipment responded, but the user failed to answer it
  • 21 – Call rejected – the call was rejected as the equipment was not technically able to receive the call
  • 22 – Number changed – the called number no longer exists. The new number may optionally be returned with this cause
  • 25 – Preemption – the network released the call in order to free resources for a call of higher priority
  • 27 – Destination out of order – The called party cannot be released because of a technical failure at the destination user’s end of the connection
  • 28 – Invalid number format – the phone number was not a valid format
  • 31 – Unspecified normal clearing (used when causes 1-28 do not apply)
Resource unavailable causes:
  • 34 – No circuit/channel available – phone displays ‘Network Busy’
  • 38 – Network out of order – A failure in the network stopped the call, and it is likely to last for a while, such as that re-attempting the call is not likely to work
  • 41 – Temporary failure – a failure in the network stopped the call, but it is likely to last only a short time, suggesting to re-attempt the call
  • 42 – Switching equipment congestion – congestion in the switching equipment stopped the call
  • 44 – Requested circuit/channel not available – no resources available to the remote user
  • 47 – Resource unavailable due to unspecified reason (used when causes 34-44 do not apply)
Service/option unavailable causes:
  • 49 – Quality of service not available
  • 55 – Incoming calls barred within Closed User Group – incoming calls are not allowed in this CUG
  • 57 – Bearer capability not authorized – the MS requested a bearer capability it is not authorized to use
  • 58 – Bearer capability not presently available – the MS requested a bearer capability that is not available at the time of request
  • 63 – Service or option not available due to unspecified reason (used when causes 49- 58 do not apply). I have noticed this when trying to make a call on Line 2, trying to make a data call on an account without data service, etc.
Service/option not implemented causes:
  • 65 – Bearer service not implemented – the equipment sending the cause does not support the bearer capability requested
  • 69 – Requested facility not implemented – the equipment sending the cause does not support the supplementary service requested
  • 70 – Only restricted digital information bearer capability is available – the equipment sending this cause only supports a restricted version of the requested (unrestricted) bearer capability
  • 79 – Service or option not implemented due to unspecified reason (used when causes 65-70 do not apply)
Invalid message causes:
  • 81 – Invalid Transaction Identifier (TI) – invalid transaction identifier received (a value in the layer 3 header which uniquely identifies a connection amongst the stream of data)
  • 87 – User not member of CUG (Closed User Group) – The called user for the CUG call is not a member of that CUG
  • 88 – Incompatible destination – the sender of this cause cannot meet the establishment requirements requested
  • 95 – Semantically incorrect message – the sender of this cause has received a message with semantically incorrect contents
Causes 96-111 are associated with protocol error
  • 96 – Invalid mandatory information
  • 97 – Message type non-existent or not implemented
  • 98 – Message type not compatible with protocol state
  • 100 – Conditional IE error
  • 101 – No cell allocation available
  • 111 – Protocol error unspecified



< PREVIOUS PAGE NEXT PAGE >



WAP-gateway IP: 79.186.132.242
Port: 9201

Русский
Powered by COMPPAG 0.50
2022-2024 © Compys S&N Systems