Reference: Q.850 Cause Code for Cisco VVB

From DocWiki

Jump to: navigation, search

Q.850 Cause Code for Cisco VVB

Q.850 Cause Code for Cisco VVB
Q.850 Cause Code
Standard Category
Description
1
Un-allocated
(unassigned)
number
Calling user cannot reach the requested destination as number is unassigned.
The following are the typical scenarios:
  • Trigger does not exist.
16
Normal Call Clearing
One of the users in the conversation hung up the call.
The following are the typical scenarios:
  • A call participant hung up.
17
User Busy

The called party is unable to accept another call because the user busy condition has been encountered. The called user or the network generates this cause value. In case of user determined user busy, it is noted that the user equipment is compatible with the call.

The following are the typical scenarios:

  • User is on a call.
  • Unable to get port or license or calls/trigger already reached.
21
Call Rejected

The equipment sending this cause code does not wish to accept the call, although it could have accepted the call because the equipment sending the cause is either busy or incompatible.

Might also be generated by the network indicating that the call was cleared because of a supplementary service constraint. The diagnostic field might contain additional information about the supplementary service and reason for rejection.

The following are the typical scenarios:

  • Subscriber has a service constraint that does not accept this call.
  • Due to port issues.
25
Exchange Routing Error

The destination indicated by the user cannot be reached because an intermediate exchange has released the call due to reaching a limit in executing the hop counter procedure.

The following are the typical scenarios:

  • Network is overloaded
  • Port limit reached
38
Network Out-of-order

The network is not functioning correctly and the condition is likely to last for an extended period.

The following are the typical scenarios:

  • Network failure
  • Whisper file not found (wrong URL)
63
Service or option not available, unspecified

The following are the typical scenarios:

  • Service not available.
  • VB Application does not exist.
65
Media Negotiation Failure

CC_CAUSE_BEARER_CAPABILITY_ NOT_IMPLEMENTED - Indicates that the equipment sending this cause does not support the bearer capability requested.

The following are the typical scenarios:

  • No codec match occurred.
87
User is not a member of CUG

The called user for the incoming Closed User Group (CUG) call is not a member of the specified CUG.

The following are the typical scenarios:

  • Caller is not authorized.
95
Invalid message received error

CC_CAUSE_INVALID_MESSAGE – Indicates an invalid message event.

The following are the typical scenarios:

  • An invalid message was received
  • SIP URL is incorrect
96
Mandatory IE missing error

CC_CAUSE_MANDATORY_IE_ MISSING - Indicates that the equipment sending this cause code has received a message that is missing an information element (IE). This IE must be present in the message before the message can be processed.

The following are the typical scenarios:

  • Mandatory Contact field missing in SIP message
  • Session Description Protocol (SDP) body is missing
97
Message type does not exist or not implemented

The equipment sending this cause has received a message which is missing an information element that must be present in the message before the message can be processed.

The following are the typical scenarios:

  • Message type information is missing.
  • The SIP method is not implemented.
99
IE or parameter unrecognized

The equipment sending this cause has received a message that includes information elements or parameters names not recognized or defined, or are defined but not implemented by the equipment.

The following are the typical scenarios:

  • Element mismatch
  • Caller sends "Requires" tag, which VVB does not support.
102
Call setup timeout failure

CC_CAUSE_RECOVERY_ON_ TIMER_EXPIRY - Indicates that a procedure has been initiated by the expiration of a timer in association with error handling procedures.

The following are the typical scenarios:

  • ACK not received in 5sec




Rating: 0.0/5 (0 votes cast)

Personal tools