Toolpack:Create CAS R2 stack D
(Created page with "=== '''''Applies to version(s): v2.9.''''' === {{DISPLAYTITLE:Create CAS Stack}} Now that the necessary underlying structures have been configured, you must create a new CAS R...") |
(Northbound Interface Content) |
||
| Line 38: | Line 38: | ||
'''Path''' | '''Path''' | ||
<pre> | <pre> | ||
| + | /configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name] | ||
</pre> | </pre> | ||
'''Parameters (text)''' | '''Parameters (text)''' | ||
<pre> | <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> | </pre> | ||
'''Parameters (json)''' | '''Parameters (json)''' | ||
<pre> | <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> | </pre> | ||
</div> | </div> | ||
Revision as of 15:24, 22 December 2015
Applies to version(s): v2.9.
Now that the necessary underlying 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
2- Click Create New CAS Stack
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
4- Verify that the "CAS stack was successfully created" message is displayed.
Path
/configurations/@[configuration_name]/hardware_units/@[hardware_name]/cas_stacks/@[casStack_name]
Parameters (text)
/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
Parameters (json)
{
"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" : {
}
}
