CAS
(formatting) |
(→CAS and TelcoBridges: some clean up) |
||
| Line 3: | Line 3: | ||
== CAS and TelcoBridges == | == CAS and TelcoBridges == | ||
| − | CAS signaling is supported at the basic API level but is not supported at the [[Toolpack]] / [[Web Portal]] level and is thus not accessible for more basic applications (i.e., that don`t require programming code). | + | CAS signaling is supported at the basic API level but is not supported at the [[Toolpack]] / [[Web Portal]] level and is thus not accessible for more basic applications (i.e., that don`t require programming code). As of June 2010, support for CAS R2 has been announced within the [[Web_Portal_Tutorial_Guide_v2.5|Toolpack Web Portal v2.5]]; this is slated to ship during the 3rd quarter of 2010. |
| Line 20: | Line 20: | ||
=== CAS R2 === | === CAS R2 === | ||
| − | The TelcoBridges CAS R2 stack features a scriptable register signaling engine | + | The TelcoBridges CAS R2 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 R2 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. |
==== Supported CAS R2 variants ==== | ==== Supported CAS R2 variants ==== | ||
| Line 26: | Line 26: | ||
*Brazil | *Brazil | ||
| − | Using Toolpack | + | Using Toolpack's script-based approach to the management of regional variants, variants supplied Toolpack can be adapted to address specific requirements and new variant scripts can be created from scratch. |
| − | + | ||
== References == | == References == | ||
Revision as of 08:18, 6 July 2010
Channel Associated Signaling is a signaling protocol for the set-up and tear-down of phone calls. It is different from other signaling protocols such as SS7 in that it is not message/packet-based but rather based on bit transition for state changing, and tone transmission for information and state information exchange. In many parts of the world, CAS was first replaced by ISDN and in many cases, was ultimately replaced by SS7. Today, CAS is often used with low density trunks.
Contents |
CAS and TelcoBridges
CAS signaling is supported at the basic API level but is not supported at the Toolpack / Web Portal level and is thus not accessible for more basic applications (i.e., that don`t require programming code). As of June 2010, support for CAS R2 has been announced within the Toolpack Web Portal v2.5; this is slated to ship during the 3rd quarter of 2010.
CAS
Supported RBS T1 variants
The following CAS variants are currently supported at the basic API level:
- Wink start
- FXS Ground start
- FXS Loop start
- FXO
- Taiwan R1
Please contact TelcoBridges regarding support for additional CAS variants.
CAS R2
The TelcoBridges CAS R2 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 R2 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.
Supported CAS R2 variants
- Generic (ITU spec base)
- Brazil
Using Toolpack's script-based approach to the management of regional variants, variants supplied Toolpack can be adapted to address specific requirements and new variant scripts can be created from scratch.
