You are currently watching the archived read-only Swyx Forum page.
Please click here to head over to the new page.
After 7 1/2 years it was time for Swyx Forum to get some new clothes, more fancy, more modern and more easy to use.
Please note that the content of the old forum wasn't moved, but instead became a read only archive for all times.
Also all existing user accounts were not moved. You would need to register yourself a new account on the new page.
The Call Routing Extensions project provides a set of useful extensions for SwyxWare's Extended Call Routing.
The list of available extensions will grow over the time. Check out the Extensions tab to get more details on the already existing extensions and their usage:
The aim of the Call Routing Extensions project is to provide functionality to ease every days life when designing call routing scripts as also to provide ready made scripts for every days usage.
All provided functionality is strictly open source and underlies a very open license.
When looking for call routing scripts you shouldn't miss to take a look into the SwyxPEDIA Wiki, Chapter SwyxWare Developement which also provides lots of links to ECR information.
If you want to share your tools or scripts into this project as well read the Get Involved ! information and afterwards get in touch with us.
Additionally if you like to build full featured installers for the extensions your are very welcome (!!!) and should get in touch with us immediately.
This page provides a list of all available extensions as also useful examples making use of the extensions.
This is a list of currently available extensions in the Call Routings Extensions project:
If you use variables in your script the content of these variables will be lost when the current call ends. Furthermore it is not possible to share the content of a variable with other simultaneously running scripts (same scripts, different scripts of the same or other user). There are lots of cases where you need to "remember" the content of a variable or simply share information between simultaneously running scripts.
Persistent Variables solve this problem. This extension provides an easy to use VBScript class (PersistenVariable) which stores it's content into a database and retrieves it from there.
The visibility, i.e. scope, of a persistent variable can be configured finely grained:
A variable with the scope User is accessable form all scripts of the current user. A user scope variable of another user with the same name does not interfere.
A variable with the scope Global is accessable from all scripts of all users.
A variable with the scope Namespace is accessable from any script (of any user) defining the same namespace. A variable being stored in another namespace but with the same name does not interfere.
The default scope is User, i.e. each user has his own set of persistent variables without need to worry to interfere with other user's scripts.
This is a list of currently available examples showing the usage of the existing extensions and are meant to be used as out of the box scripts:
Based upon the Persistent Variables extension this is an example on how to implement night switch functionality. There are two scripts included
The following is a list of requirements of Call Routing Extensions:
This is a Swyx Forum open source project. All support, enhancement and bug requests must be placed into the project's forums.No other support is available!
Each extension has it's own forum for your questions, suggestions and applause :-)
In regard of the license being provided there is neither a guaranteed response time for support requests nor a guaranteed solution.
Call Routing Extensions
This is a Swyx Forum Open Source Project.
Copyright (c) 2011 by Swyx Forum
Copyright (c) 2011 by Tom Wellige
All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANT-ABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SWYX FORUM © 2007-2014 Tom Wellige