|
Home Resources Products
Developers |
Main • CallEndCauses
Call end causes and errorsA 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 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.
SIP specificsAfter the INVITE completes successfully the codes are sent in the Reason: header of the BYE transaction. H.323 specificsThe 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 specificsThere are no cause cods in IAX, only textual messages sent with the REJECT or HANGUP packet. |
3 May 2010: 8 March 2010: 6-7 February 2010: 2 Nov 2009: 6 Aug 2008: 4 Aug 2008: 10 Jul 2008: Feb 2008: 21 Jan 2008: 3 September: 14 August: 16 April: 25 September: 25 September: 11 July 2006: 10 July 2006: June 1st 2006: |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||