CASr1 scripting - Revision history

Allyntree at 17:47, 24 June 2024

2024-06-24T17:47:19Z

← Older revision		Revision as of 13:47, 24 June 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:CASr1 scripting}}		{{DISPLAYTITLE:CASr1 scripting}}

			==Introduction==
	This page explains how CASr1 script are implemented. You can read, modify, or create CASR1 scripts to adapt to different variants, or implement new variants.		This page explains how CASr1 script are implemented. You can read, modify, or create CASR1 scripts to adapt to different variants, or implement new variants.

	~~== Summary ==~~

	Toolpack uses the LUA programming language to implement CAS scripts. The CAS scripts are interpreted by the TMG unit in order to handle calls.		Toolpack uses the LUA programming language to implement CAS scripts. The CAS scripts are interpreted by the TMG unit in order to handle calls.

2022-09-07T14:15:15Z

← Older revision		Revision as of 10:15, 7 September 2022
Line 1:		Line 1:
			{{DISPLAYTITLE:CASr1 scripting}}

	This page explains how CASr1 script are implemented. You can read, modify, or create CASR1 scripts to adapt to different variants, or implement new variants.		This page explains how CASr1 script are implemented. You can read, modify, or create CASR1 scripts to adapt to different variants, or implement new variants.

2017-12-20T16:54:33Z

← Older revision		Revision as of 12:54, 20 December 2017
Line 1:		Line 1:

	This page explains how CASr1 script are implemented~~, so the reader~~ can read, modify or create CASR1 scripts to adapt to different variants, or implement new variants.		This page explains how CASr1 script are implemented. You can read, modify, or create CASR1 scripts to adapt to different variants, or implement new variants.

	== Summary ==		== Summary ==

2014-12-12T15:26:44Z

Provided scripts

← Older revision		Revision as of 11:26, 12 December 2014
Line 49:		Line 49:
	CASR2 variants:		CASR2 variants:
	<ul>		<ul>
	~~<li>Generic (ITU spec base) </li>~~		[[CAS#Supported_CAS_R2_variants\|Supported CASR2 variants]]
	~~<li>Brazil </li>~~
	~~<li>Mexico </li>~~
	</ul>		</ul>
	</li>		</li>

2014-12-12T15:26:01Z

Provided scripts

← Older revision		Revision as of 11:26, 12 December 2014
Line 44:		Line 44:
	<ul>		<ul>
	[[CAS#Supported_CAS_R1_variants\|Supported CASR1 variants]]		[[CAS#Supported_CAS_R1_variants\|Supported CASR1 variants]]
	~~<li>[[CAS_R1_E%26M\|E&M ("wink start")]]</li>~~
	~~<li>[[CAS_R1_LOOPSTART_USER\|Loop start user side]]</li>~~
	~~<li>[[CAS_R1_LOOPSTART_NETWORK\|Loop start network side]]</li>~~
	</ul>		</ul>
	</li>		</li>

2014-12-12T15:25:36Z

Provided scripts

← Older revision		Revision as of 11:25, 12 December 2014
Line 43:		Line 43:
	CASR1 variants:		CASR1 variants:
	<ul>		<ul>
	[[CAS\|~~Supported_CAS_R1_variants~~]]		[[CAS#Supported_CAS_R1_variants\|Supported CASR1 variants]]
	<li>[[CAS_R1_E%26M\|E&M ("wink start")]]</li>		<li>[[CAS_R1_E%26M\|E&M ("wink start")]]</li>
	<li>[[CAS_R1_LOOPSTART_USER\|Loop start user side]]</li>		<li>[[CAS_R1_LOOPSTART_USER\|Loop start user side]]</li>

2014-12-12T15:23:38Z

Provided scripts

← Older revision		Revision as of 11:23, 12 December 2014
Line 43:		Line 43:
	CASR1 variants:		CASR1 variants:
	<ul>		<ul>
			[[CAS\|Supported_CAS_R1_variants]]
	<li>[[CAS_R1_E%26M\|E&M ("wink start")]]</li>		<li>[[CAS_R1_E%26M\|E&M ("wink start")]]</li>
	<li>[[CAS_R1_LOOPSTART_USER\|Loop start user side]]</li>		<li>[[CAS_R1_LOOPSTART_USER\|Loop start user side]]</li>

2013-11-27T15:44:32Z

← Older revision		Revision as of 11:44, 27 November 2013
Line 181:		Line 181:

	Default: No dial tone		Default: No dial tone

			<pre>
			TX_DIAL_TONE = "(350,440)" -- This is default US dial tone
			</pre>

			=== USE_FORCED_RELEASE ===
			Defines if "forced release" option must be used to terminate non-answered backward (incoming) calls.

			In most CASR1 variants, the CAS bits for a backward (incoming) calls remain "on-hook" until the call is answered (except for short "wink" periods).
			Because of that, it's not possible to indicate remote equipment that we want to terminate this incoming call, since bits are already "on hook".

			The solution to that is to quickly set the CAS bits to "off-hook" then "on-hook", to indicate to remote side that we want to terminate the call.

			This option should be used with care, because it may cause remote equipment to think the call has been answered for about 200ms. This could cause billing or statistics (ASR) calculation problems on the remote equipment if it does not expect that.

			Default: 0 (Don't use forced release)

	<pre>		<pre>

2013-11-22T20:42:05Z

ACTION_WAIT_ANI

← Older revision		Revision as of 16:42, 22 November 2013
Line 741:		Line 741:
	</ol>		</ol>

	More than one of the methods above can be used (~~but at least one~~ must be ~~used~~).		More than one of the methods above can be used.
			If none of these options are used, the script will consider that ANI is not used (won't be received, must not be sent).

	Once ANI has been considered complete by one of the 3 methods above, then [[#EVENT_ANI_RECEIVED\|EVENT_ANI_RECEIVED]] is reported to the script.		Once ANI has been considered complete by one of the 3 methods above, then [[#EVENT_ANI_RECEIVED\|EVENT_ANI_RECEIVED]] is reported to the script.

2013-09-03T03:22:46Z

TONE_VP_GROUP

@@ Line 173: / Line 173: @@
 <pre>
 TONE_VP_GROUP				= 1
 </pre>