Termination cause codes - Revision history

Luc Morissette: Added category FAQ

2023-01-11T14:34:19Z

Added category FAQ

← Older revision		Revision as of 10:34, 11 January 2023
Line 69:		Line 69:

	A SIP BYE does not include a cause code, so on a normal call terminations, TMedia will send a BYE on SIP, and internally, a 200 TOOLPACK_NORMAL (in the logs and the CDRs). When the call terminates unexpectedly, for example after a ACM, but before a ANM, Tmedia will still send a BYE on SIP, but internally, it will log a 603 Decline (REASON_CODE_603_DECLINE).		A SIP BYE does not include a cause code, so on a normal call terminations, TMedia will send a BYE on SIP, and internally, a 200 TOOLPACK_NORMAL (in the logs and the CDRs). When the call terminates unexpectedly, for example after a ACM, but before a ANM, Tmedia will still send a BYE on SIP, but internally, it will log a 603 Decline (REASON_CODE_603_DECLINE).

			[[category:FAQ]]

2018-10-10T13:57:34Z

Added the process to create reason cause codes following our standard way of working

@@ Line 28: / Line 28: @@
 For each redirection cause code, choose '''Process''' to let the routing scripts process the redirection. Choose '''Stop''' to drop calls when receiving a redirection and use the above table to specify if the redirection contents should be dropped.
-Starting from release 2.5.55 these cause codes can be modified with the Web portal in
-<pre>Profiles -&gt; Edit -&gt; Reason Cause Mapping </pre>
+'''To Modify a reason cause code:'''
-[[Image:Reason cause list 1.png|Test]]
 <br>

2018-10-10T13:38:17Z

2018-10-10T13:36:42Z

Moved information from https://docs.telcobridges.com/tbwiki/Toolpack:Protocol_Stack_Settings_A#Redirection here

← Older revision		Revision as of 09:36, 10 October 2018
Line 1:		Line 1:

			==General configuration===


			When configuring [[Termination_cause_codes\|termination cause codes]], use the following table as a guide. The ''Drop'' column represents codes to use when redirection contents should be dropped and the call should be terminated with the specified code. The ''Forward'' column represents codes to use when redirection contents should be forwarded to the incoming leg with the specified code. If the redirection requests must be processed, the codes are not used.
			{\| class="wikitable"
			\|-
			! rowspan="2" \| Code !! colspan="2" \| Drop !! colspan="2" \| Forward
			\|-
			! SS7 !! SIP !! SS7 !! SIP
			\|-
			\| 14 \|\| 21 \|\| 603 \|\| 14 \|\| 300
			\|-
			\| 22 \|\| 21 \|\| 410 \|\| 22 \|\| 301
			\|-
			\| 23 \|\| 21 \|\| 410 \|\| 23 \|\| 302
			\|-
			\| 300 \|\| 21 \|\| 603 \|\| 23 \|\| 300
			\|-
			\| 301 \|\| 21 \|\| 410 \|\| 22 \|\| 301
			\|-
			\| 302 \|\| 21 \|\| 410 \|\| 23 \|\| 302
			\|-
			\| 305 \|\| 21 \|\| 603 \|\| 23 \|\| 305
			\|-
			\| 380 \|\| 21 \|\| 603 \|\| 23 \|\| 380
			\|}
			For each redirection cause code, choose '''Process''' to let the routing scripts process the redirection. Choose '''Stop''' to drop calls when receiving a redirection and use the above table to specify if the redirection contents should be dropped.

	Starting from release 2.5.55 these cause codes can be modified with the Web portal in		Starting from release 2.5.55 these cause codes can be modified with the Web portal in
	<pre>Profiles -> Edit -> Reason Cause Mapping </pre>		<pre>Profiles -> Edit -> Reason Cause Mapping </pre>

2018-04-24T19:41:24Z

Case for the 603 DECLINE and 200 TOOLPACK NORMAL

← Older revision		Revision as of 15:41, 24 April 2018
Line 12:		Line 12:
	=== Case for the 603 DECLINE and 200 TOOLPACK NORMAL ===		=== Case for the 603 DECLINE and 200 TOOLPACK NORMAL ===

	The TOOLPACK_NORMAL reason code is mapped to the 603_DECLINE reason code. The reason is the following:		The TOOLPACK_NORMAL reason code is mapped to the 603_DECLINE reason code. The reason for this is the following:

	A SIP BYE does not include a cause code, so on normal call terminations, So TMedia will send a BYE on SIP, and internally, a 200 TOOLPACK_NORMAL (in the logs and the CDRs). ~~But when~~ the call terminates unexpectedly, for example after a ACM, but before a ANM, Tmedia will still send a BYE on SIP, but internally, it will log a 603 Decline (REASON_CODE_603_DECLINE).		A SIP BYE does not include a cause code, so on a normal call terminations, TMedia will send a BYE on SIP, and internally, a 200 TOOLPACK_NORMAL (in the logs and the CDRs). When the call terminates unexpectedly, for example after a ACM, but before a ANM, Tmedia will still send a BYE on SIP, but internally, it will log a 603 Decline (REASON_CODE_603_DECLINE).

	~~[[Category:Needs_revising]]~~

2014-01-31T17:05:13Z

@@ Line 5: / Line 5: @@
 <br>
-'''Complete list of Reason Cause mapping between the protocols:'''
+== Complete list of Reason Cause mapping between the protocols: ==
-[[File:Reason_Cause.xlsx]]
+[[Media:Reason_Cause.xlsx|Reason Cause list in csv]]
+=== Case for the 603 DECLINE and 200 TOOLPACK NORMAL  ===
 The TOOLPACK_NORMAL reason code is mapped to the 603_DECLINE reason code. The reason is the following:

2014-01-29T16:48:43Z

Added a link to a excel files with Reason Cause list

2013-02-01T14:28:19Z

New reason code

2011-09-27T17:02:33Z

SIP <-> ISDN/SS7 <-> Toolpack Mapping

2011-04-01T12:52:26Z

← Older revision		Revision as of 08:52, 1 April 2011
Line 1:		Line 1:
	~~DRAFT VERSION~~		Starting from release 2.5.55 these cause codes can be modified with the Web portal in

	~~This page needs to be cleaned up. For now, please use your browser's 'Find' function to locate the code you are looking for.~~

	Starting from release 2.5.55 these cause codes can be modified with the Web portal in
	<pre>Profiles -> Edit -> Reason Cause Mapping </pre>		<pre>Profiles -> Edit -> Reason Cause Mapping </pre>
	[[Image:~~Reason_cause_list_1~~.png]]		[[Image:Reason cause list 1.png]]


			<br>

	The source of this list is tbcmc_call.h<br>		The source of this list is tbcmc_call.h<br>