Call End Causes - Revision history

Monica at 09:25, 4 November 2013

2013-11-04T09:25:52Z

Dana at 13:06, 3 April 2013

2013-04-03T13:06:12Z

Dana: /* IAX specifics */

2012-11-19T10:04:48Z

‎IAX specifics

Dana at 10:02, 19 November 2012

2012-11-19T10:02:46Z

Dana: /* Call end causes and errors */

2012-10-04T15:02:04Z

‎Call end causes and errors

Dana at 15:00, 4 October 2012

2012-10-04T15:00:40Z

Dana: /* Call end causes and errors */

2012-10-04T14:57:10Z

‎Call end causes and errors

Dana: /* Call end causes and errors */

2012-10-04T14:51:49Z

‎Call end causes and errors

Dana: /* Call end causes and errors */

2012-10-04T14:50:55Z

‎Call end causes and errors

Dana: Created page with "== Call end causes and errors == A telephone call can fail or end abnormally. To express the cause of a call end each protocol has its own way of encoding it, usually by a pro..."

2012-10-04T14:50:00Z

Created page with "== Call end causes and errors == A telephone call can fail or end abnormally. To express the cause of a call end each protocol has its own way of encoding it, usually by a pro..."

New page

== Call end causes and errors ==
A telephone call can fail or end abnormally. To express the cause of a call end each protocol has its own way of encoding it, usually by a protocol spcific numeric value.

To provide protocol independence Yate translates these cause codes in keywords that attempt to be protocol agnostic. When the keyword is translated back into protocol specific codes hopefully an adequate translation is choosen.

Many of the cause codes are protocol specific and have no equivalent in other protocols. For telephony the most important encoding is [[http://www.itu.int/rec/T-REC-Q.850/e|Q.850]] defining cause and location codes for ISDN.

You should also note that some of these call termination codes are not errors but part of normal operation of one or another protocol. Some of these codes are also used for operations after the call is established.

||class="wikitable" border=1
||!Keyword||!SIP||!H.323||!IAX||!ISDN||!SS7||!Description||!Default Error in||
|| Call initiation ||||||||||||||||
||noroute ||404 ||3 ||? ||? ||? ||No route to destination could be found||routing||
||noconn ||503 ||34 ||? ||? ||? ||Could not connect to outgoing channel or network||call.execute||
||noauth ||401 ||21 ||? ||? ||? ||Caller is not authenticated|| ||
||nomedia ||415 ||65 ||? ||? ||? ||Failed to negotiate media channel|| ||
||noanswer ||487 ||19 ||? ||? ||? ||Called party did not answer|| ||
||busy ||486 ||17 ||? ||? ||? ||Called party is busy|| ||
||congestion ||480 ||42 ||? ||? ||? ||Temporary network congestion|| ||
||offline ||404 ||44 ||? ||? ||? ||Called party or network is offline|| ||
||rejected ||406 ||31 ||? ||? ||? ||Call rejected by called party or network|| ||
||forbidden ||403 ||47 ||? ||? ||? ||Call is not authorized|| ||
||incomplete ||484 ||1 ||? ||? ||? ||Called party number or address is incomplete|| ||
||looping ||483 ||98 ||? ||? ||? ||Call loop detected|| ||
||failure ||500 ||127||? ||? ||? ||Generic local server or interoperation failure|| ||
|| During the call |||||||||||||| ||
||timeout ||BYE ||102 ||? ||? ||? ||Call duration exceeded limit|| ||
||nocall ||481 ||100 ||? ||? ||? ||Referenced call could not be found on server|| ||
||pending ||491 ||111 ||? ||? ||? ||Another operation is in progress on the same call|| ||

== SIP specifics ==
After the INVITE completes successfully the codes are sent in the Reason: header of the BYE transaction.

== H.323 specifics ==
The H.323 protocol stack has several ways of sending codes at different layers. Not always a Q.850 code is available - for example if the TCP/IP communication cannot be established.

== IAX specifics ==
There are no cause cods in IAX, only textual messages sent with the REJECT or HANGUP packet.

← Older revision		Revision as of 09:25, 4 November 2013
Line 69:		Line 69:

	* [[Routing]]		* [[Routing]]
		+
		+	[[Category:SIP]] [[Category:H323]] [[Category:IAX]] [[Category:Change reason]]

← Older revision		Revision as of 13:06, 3 April 2013
Line 64:		Line 64:
	=== IAX specifics ===		=== IAX specifics ===
	There are no cause codes in IAX, only textual messages sent with the REJECT or HANGUP packet.		There are no cause codes in IAX, only textual messages sent with the REJECT or HANGUP packet.
		+
		+
		+	'''See also'''
		+
		+	* [[Routing]]

← Older revision		Revision as of 10:04, 19 November 2012
Line 63:		Line 63:

	=== IAX specifics ===		=== IAX specifics ===
−	There are no cause ~~cods~~ in IAX, only textual messages sent with the REJECT or HANGUP packet.	+	There are no cause codes in IAX, only textual messages sent with the REJECT or HANGUP packet.

@@ Line 1: / Line 1: @@
-== Call end causes and errors ==
+A telephone call can fail or end abnormally. To express the cause of a call end each protocol has its own way of encoding it, usually by a protocol specific numeric value.
-A telephone call can fail or end abnormally. To express the cause of a call end each protocol has its own way of encoding it, usually by a protocol spcific numeric value.
+=== Call end causes and errors ===
-To provide protocol independence Yate translates these cause codes in keywords that attempt to be protocol agnostic. When the keyword is translated back into protocol specific codes hopefully an adequate translation is choosen.
+To provide protocol independence Yate translates the cause codes in keywords that attempt to be protocol agnostic. When the keyword is translated back into protocol specific codes hopefully an adequate translation is choosen.
 Many of the cause codes are protocol specific and have no equivalent in other protocols. For telephony the most important encoding is [http://www.itu.int/rec/T-REC-Q.850/e Q.850] defining cause and location codes for ISDN.
@@ Line 56: / Line 56: @@
 |}
-== SIP specifics ==
+=== SIP specifics ===
 After the INVITE completes successfully the codes are sent in the Reason: header of the BYE transaction.
-== H.323 specifics ==
+=== H.323 specifics ===
 The H.323 protocol stack has several ways of sending codes at different layers. Not always a Q.850 code is available - for example if the TCP/IP communication cannot be established.
-== IAX specifics ==
+=== IAX specifics ===
 There are no cause cods in IAX, only textual messages sent with the REJECT or HANGUP packet.

@@ Line 5: / Line 5: @@
 To provide protocol independence Yate translates these cause codes in keywords that attempt to be protocol agnostic. When the keyword is translated back into protocol specific codes hopefully an adequate translation is choosen.
-Many of the cause codes are protocol specific and have no equivalent in other protocols. For telephony the most important encoding is [[http://www.itu.int/rec/T-REC-Q.850/e|Q.850]] defining cause and location codes for ISDN.
+Many of the cause codes are protocol specific and have no equivalent in other protocols. For telephony the most important encoding is [http://www.itu.int/rec/T-REC-Q.850/e Q.850] defining cause and location codes for ISDN.
 You should also note that some of these call termination codes are not errors but part of normal operation of one or another protocol. Some of these codes are also used for operations after the call is established.

@@ Line 1: / Line 1: @@
 == Call end causes and errors ==
 A telephone call can fail or end abnormally. To express the cause of a call end each protocol has its own way of encoding it, usually by a protocol spcific numeric value.
@@ Line 18: / Line 19: @@
 !Default Error in
 |-
-|align="left" colspan="8"|Call initiation
+|align="center" colspan="8"|Call initiation
 |-
 |noroute || 404 || 3 || ? || ? || ? || No route to destination could be found|| routing
@@ Line 24: / Line 25: @@
 |noconn || 503 || 34 || ? || ? || ? || Could not connect to outgoing channel or network || call.execute
 |-
-|noauth || 401 || 21 || ? || ? || ? || Caller is not authenticated || ||
+|noauth || 401 || 21 || ? || ? || ? || Caller is not authenticated
 |-
-|nomedia ||415 ||65 ||? ||? ||? ||Failed to negotiate media channel|| ||
+|nomedia ||415 ||65 ||? ||? ||? ||Failed to negotiate media channel
 |-
-|noanswer ||487 ||19 ||? ||? ||? ||Called party did not answer|| ||
+|noanswer ||487 ||19 ||? ||? ||? ||Called party did not answer
 |-
-||busy ||486 ||17 ||? ||? ||? ||Called party is busy|| ||
+||busy ||486 ||17 ||? ||? ||? ||Called party is busy
 |-
-|congestion ||480 ||42 ||? ||? ||? ||Temporary network congestion|| ||
+|congestion ||480 ||42 ||? ||? ||? ||Temporary network congestion
 |-
-|offline ||404 ||44 ||? ||? ||? ||Called party or network is offline|| ||
+|offline ||404 ||44 ||? ||? ||? ||Called party or network is offline
 |-
-|rejected ||406 ||31 ||? ||? ||? ||Call rejected by called party or network|| ||
+|rejected ||406 ||31 ||? ||? ||? ||Call rejected by called party or network
 |-
-|forbidden ||403 ||47 ||? ||? ||? ||Call is not authorized|| ||
+|forbidden ||403 ||47 ||? ||? ||? ||Call is not authorized
 |-
-|incomplete ||484 ||1 ||? ||? ||? ||Called party number or address is incomplete|| ||
+|incomplete ||484 ||1 ||? ||? ||? ||Called party number or address is incomplete
 |-
-|looping ||483 ||98 ||? ||? ||? ||Call loop detected|| ||
+|looping ||483 ||98 ||? ||? ||? ||Call loop detected
 |-
-|failure ||500 ||127||? ||? ||? ||Generic local server or interoperation failure|| ||
+|failure ||500 ||127||? ||? ||? ||Generic local server or interoperation failure
 |-
-|During the call |||||||||||||| ||
+|align="center" colspan="8"|During the call
 |-
-|timeout ||BYE ||102 ||? ||? ||? ||Call duration exceeded limit|| ||
+|timeout ||BYE ||102 ||? ||? ||? ||Call duration exceeded limit
 |-
-|nocall ||481 ||100 ||? ||? ||? ||Referenced call could not be found on server|| ||
+|nocall ||481 ||100 ||? ||? ||? ||Referenced call could not be found on server
 |-
-||pending ||491 ||111 ||? ||? ||? ||Another operation is in progress on the same call|| ||
+||pending ||491 ||111 ||? ||? ||? ||Another operation is in progress on the same call
 |}

@@ Line 9: / Line 9: @@
 {|class="wikitable" border=1
-!Keyword || !SIP || !H.323 || !IAX || !ISDN || !SS7 || !Description || !Default Error in ||
+!Keyword
-|| Call initiation ||||||||||||||||
+!SIP
-||noroute ||404 ||3 ||? ||? ||? ||No route to destination could be found||routing||
+!H.323
-||noconn ||503 ||34 ||? ||? ||? ||Could not connect to outgoing channel or network||call.execute||
+!IAX
-||noauth ||401 ||21 ||? ||? ||? ||Caller is not authenticated|| ||
+!ISDN
-||nomedia ||415 ||65 ||? ||? ||? ||Failed to negotiate media channel|| ||
+!SS7
-||noanswer ||487 ||19 ||? ||? ||? ||Called party did not answer|| ||
+!Description
 ||busy ||486 ||17 ||? ||? ||? ||Called party is busy|| ||
-||congestion ||480 ||42 ||? ||? ||? ||Temporary network congestion|| ||
+|-
-||offline ||404 ||44 ||? ||? ||? ||Called party or network is offline|| ||
+|congestion ||480 ||42 ||? ||? ||? ||Temporary network congestion|| ||
-||rejected ||406 ||31 ||? ||? ||? ||Call rejected by called party or network|| ||
+|-
-||forbidden ||403 ||47 ||? ||? ||? ||Call is not authorized|| ||
+|offline ||404 ||44 ||? ||? ||? ||Called party or network is offline|| ||
-||incomplete ||484 ||1 ||? ||? ||? ||Called party number or address is incomplete|| ||
+|-
-||looping ||483 ||98 ||? ||? ||? ||Call loop detected|| ||
+|rejected ||406 ||31 ||? ||? ||? ||Call rejected by called party or network|| ||
-||failure ||500 ||127||? ||? ||? ||Generic local server or interoperation failure|| ||
+|-
-|| During the call |||||||||||||| ||
+|forbidden ||403 ||47 ||? ||? ||? ||Call is not authorized|| ||
-||timeout ||BYE ||102 ||? ||? ||? ||Call duration exceeded limit|| ||
+|-
-||nocall ||481 ||100 ||? ||? ||? ||Referenced call could not be found on server|| ||
+|incomplete ||484 ||1 ||? ||? ||? ||Called party number or address is incomplete|| ||
 ||pending ||491 ||111 ||? ||? ||? ||Another operation is in progress on the same call|| ||
 |}