Toolpack:Create CAS R2 stack E - Revision history

Allyntree at 17:46, 24 June 2024

2024-06-24T17:46:27Z

← Older revision		Revision as of 13:46, 24 June 2024
Line 7:		Line 7:
	\|-		\|-
	\|Tmedia		\|Tmedia
	\|3.0, 3.2		\|3.0, 3.2, 3.3
	\|}		\|}

Allyntree at 18:25, 25 November 2020

2020-11-25T18:25:14Z

← Older revision		Revision as of 14:25, 25 November 2020
Line 1:		Line 1:
	~~=== '''''Applies to version(s): v3.0''''' ===~~
	{{DISPLAYTITLE:Create CAS Stack}}		{{DISPLAYTITLE:Create CAS Stack}}
			{\| class="wikitable"
			\|-
			\|rowspan="3"\|This article applies to:
			\|'''Product'''
			\|'''Version'''
			\|-
			\|Tmedia
			\|3.0, 3.2
			\|}

	Once the necessary underlying CAS structures have been configured, you must create a new CAS R2 stack.		Once the necessary underlying CAS structures have been configured, you must create a new CAS R2 stack.

Allyntree: /* Applies to version(s): v3.0 */

2017-11-21T16:23:27Z

Applies to version(s): v3.0

← Older revision		Revision as of 12:23, 21 November 2017
Line 32:		Line 32:

	[[Image:CASR2_3_B.png]]		[[Image:CASR2_3_B.png]]


	~~<div class="mw-collapsible mw-collapsed" data-collapsetext="Northbound Interface" data-expandtext="Northbound Interface" style="width: 400px;">~~

	~~'''Path'''~~
	~~<pre>~~
	~~/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]~~
	~~</pre>~~

	~~'''Parameters (text)'''~~
	~~<pre>~~
	~~/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]~~
	~~enabled = true~~
	~~line_service = "@[line_service_name]"~~
	~~name = "@[casStack_name]"~~
	~~script = "@[script_name]"~~

	~~/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]/state~~
	~~all_cics_forced_blocked = false~~
	~~all_cics_forced_unblocked = false~~
	~~circuits_blocked_mask = 0x0~~
	~~circuits_unblocked_mask = 0x0~~

	~~/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]/script_variables~~
	~~</pre>~~

	~~'''Parameters (json)'''~~
	~~<pre>~~
	{
	~~"enabled" : true,~~
	~~"line_service" : "@[line_service_name]",~~
	~~"name" : "@[casStack_name]",~~
	~~"script" : "[script_name]",~~
	~~"state" : {~~
	~~"all_cics_forced_blocked" : false,~~
	~~"all_cics_forced_unblocked" : false,~~
	~~"circuits_blocked_mask" : 0,~~
	~~"circuits_unblocked_mask" : 0~~
	},
	~~"script_variables" : {~~
	}
	}
	~~</pre>~~
	~~</div>~~


	==List of Parameters==		==List of Parameters==

Allyntree: New page for 3.0 because of Variant Script Variables link and live states link changed to States.

2017-11-21T16:21:29Z

New page for 3.0 because of Variant Script Variables link and live states link changed to States.

New page

=== '''''Applies to version(s): v3.0''''' ===
{{DISPLAYTITLE:Create CAS Stack}}
Once the necessary underlying CAS structures have been configured, you must create a new CAS R2 stack.

The TelcoBridges CAS stack features a scriptable register signaling engine that, in practice, allows the complete customization of communication processes using tones. More specifically, it is possible to modify the timing(s) of the tone exchanges, change the meaning(s) of each tone and dynamically specify the sequence in which the tones are played. The CAS stack also provides integrated interoperability between variants and between other signaling types. For instance, the calling party category can be converted between variants and propagated to a SS7 call leg.

To create a CAS stack:

1- Click '''CAS''' in the navigation panel

[[Image:CASR2_0_A.png]]

2- Click '''Create New CAS Stack'''

[[Image:CASR2_1_B.png]]

3- Configure the new CAS stack:

* Make sure the '''Enabled''' box is checked
* Enter a '''name''' for the stack
* Select a '''line service'''
* Select a '''variant script'''
* Click '''Create'''

[[Image:CASR2_2_C.png]]

4- Verify that the '''"CAS stack was successfully created"''' message is displayed.

[[Image:CASR2_3_B.png]]

<div class="mw-collapsible mw-collapsed" data-collapsetext="Northbound Interface" data-expandtext="Northbound Interface" style="width: 400px;">

'''Path'''
<pre>
/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]
</pre>

'''Parameters (text)'''
<pre>
/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]
enabled = true
line_service = "@[line_service_name]"
name = "@[casStack_name]"
script = "@[script_name]"

/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]/state
all_cics_forced_blocked = false
all_cics_forced_unblocked = false
circuits_blocked_mask = 0x0
circuits_unblocked_mask = 0x0

/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]/script_variables
</pre>

'''Parameters (json)'''
<pre>
{
"enabled" : true,
"line_service" : "@[line_service_name]",
"name" : "@[casStack_name]",
"script" : "[script_name]",
"state" : {
"all_cics_forced_blocked" : false,
"all_cics_forced_unblocked" : false,
"circuits_blocked_mask" : 0,
"circuits_unblocked_mask" : 0
},
"script_variables" : {
}
}
</pre>
</div>

==List of Parameters==

* [[Parameter: Enabled|Enabled]]
* [[Parameter: Name|Name]]
* [[Parameter: Line Service|Line Service]]
* [[Parameter: Variant Script|Variant Script]]