9.1 Call Permissions
Call rights are defined within SwyxWare for users and trunk groups.
For each user, these rights define
where a call may be made to (e.g. local),with what public line access (e.g. private or business) andvia which trunk group this call may go out.The call permissions are defined using so-called profiles, which are then assigned to individual users or trunk groups.
Such a profile can be composed of several individual permissions. But each user and each trunk group has only precisely one call permission.
Various simple call permissions are offered in the standard installation (9.1.1 Call permissions in the standard installation.).
If there are special requirements for call permissions, which the standard profiles do not satisfy, the SwyxWare administrator can define his own call permissions, customized specifically for the needs of the installation.
To define call permissions in detail, see 9.1.2 Create Call Permission.
Call Permissions and Routing
The call permissions are independent of the routing (14 Routing). Routings define how a call leaves the system, i.e. how it can be forwarded depending on the trunk group and the time conditions. Routes are a property of the SwyxServer.
Call permissions are user and/or trunk group characteristics. They define which rights are granted to an incoming call, i.e. if and how a call will be transmitted.
Call permission of a user
A user's call permission states what calling rights this user has within SwyxWare. For example, he can have the right to make national calls, but not international ones. If a SwyxWare user forwards a call (e.g. with a script), the forwarded call receives the user's rights.
Example:
There is a SwyxWare installation with two servers, one in Liverpool and one in Liverpool. The two SwyxServers are connected to each other over a SwyxLink.
The called user in London has the right to telephone via ISDN within London (locally), but not nationally:
Entry in the user's call permission:
Allow call +4420*; Trunk group "ISDN London"
The called user in London also has the right to make calls to Liverpool via a SwyxLink trunk "SwyxLink London-Liverpool":
Entry in the user's call permission:
Allow call +44151*; Trunk group "SwyxLinkLondon-Liverpool"
In its call permission, the trunk group "SwyxLink London-Liverpool" allows local calls via ISDN. (This is configured on the Liverpool side!):
Entry in the call permissions of the trunk group "SwyxLink London-Liverpool" on the Liverpool side:
Allow call +44151*; Trunk group "ISDN Liverpool"
If the SwyxWare user is called and if a route to the Liverpool local public network is set up, then a caller calling in London is routed via the SwyxLink trunk to Liverpool and there into the Liverpool local public network.
Call permission of a trunk group
A call permission is assigned to each trunk group. All calls that come in via a trunk group inherit the call permission of this trunk group.
Thus, if an incoming call cannot be assigned to any user within the SwyxWare system, it must leave this system (e.g. via another trunk group). For this forwarding, it receives the call permission of the trunk group via which it came into this system.
Example 1
There is a SwyxWare installation with two servers, one in Liverpool and one in Liverpool. The two SwyxServers are connected to each other over a SIP trunk.
A call comes in from the public network via the ISDN trunk group to the London number 020 23456-888. This number is not assigned to a user within SwyxWare, but there is forwarding for the number range 020 234567-88* via a SIP trunk group. In order for this call to be forwarded via this SIP trunk group, the corresponding permission must exist in the ISDN trunk group, which has received the call, i.e. the call that has been received by the trunk group must have the permission to leave the system via the SIP trunk:
Entry in the call permission of the ISDN trunk group:
Allow call +4420 23456-88*; Trunk group "SIP"
Example 2
There is a SwyxWare installation with two SwyxServers, one in London and one in Liverpool. The two SwyxServers are connected to each other over a SwyxLink.
In order that calls to Liverpool can in principle go via this SwyxLink, a routing record must be set up on the server in London to forward all calls to Liverpool via the SwyxLink to Liverpool.
Routing record in London:
Allow call +44 151*; Trunk group "SwyxLink London-Liverpool"; Priority 900
A user has the location London (prefix: 020). In the first place he can make local calls in London via ISDN:
Entry in the user's call permission:
Allow call +44,20*; Trunk group "ISDN London"
He also has the right to make calls to Liverpool via a SwyxLink trunk "SwyxLink London-Liverpool":
Entry in the user's call permission:
Allow call +44151*; Trunk group "SwyxLinkLondon-Liverpool"
In its call permission, the trunk group "SwyxLink London-Liverpool" allows local calls via ISDN into the Liverpool local public network. (This is configured on the Liverpool side!):
Entry in the call permissions of the trunk group "SwyxLink London-Liverpool" on the Liverpool side:
Allow call +44 151*; Trunk group "ISDN Liverpool"
The user in London can thus call Liverpool via the SwyxLink, and there telephone locally via ISDN into the public telephone network.
Example 3:
There is a SwyxWare installation with two SwyxServers, one in Liverpool and one in Germany. The two SwyxServers are connected to each other over a SwyxLink.
To be able to make calls to England via this SwyxLink, a routing record must be set up on the server in Liverpool to forward all calls to Germany (prefix +49) via the SwyxLink to Germany.
Routing record in Liverpool:
Allow call +49*; Trunk group "SwyxLink DE"; Priority 900
The user has the right at his Liverpool location to telephone internally.
Entry in the user's call permission:
Deny call +*; Trunk group "All"
Allow call *; Trunk group "All"
But he has the right to phone Germany (prefix 49) via SwyxLink:
Entry in the user's call permission:
Allow call +49*; Trunk group "SwyxLink DE"
In Germany the "SwyxLink DE" is configured in such a way that calls coming in via this trunk group have the right to initiate national calls via ISDN into the public network:
Entry in the call permission for SwyxLink DE in Germany:
Allow call +49*; Trunk group "ISDN DE"
The user in Liverpool is now able to call Germany via SwyxLink, and there to make calls into the entire national telephone network; but he cannot call locally in Liverpool.
Such a constellation could e. g. make sense for a support employee, who only makes phone calls to Germany.
For private calls, a further permission can be set up with a public line access for private calls. e. g.
Entry in the user's call permission:
Allow call +44151*; Trunk group "ISDN Liverpool"; Public line access 8 (private)
Call permission for SwyxLink trunk groups
SwyxLink trunk groups represent the connection between two SwyxWare installations. Every SwyxLink trunk is configured on both sides, on one side locally and on the other side remotely (16 SIP Links).
A call that takes place over this connection inherits the call permission of the side on which it leaves this trunk; or, to put it another way, it receives the call permission of the trunk group which routes this call into SwyxWare.
Example:
There are two SwyxWare installations in London and Liverpool, which are connected to a SwyxLink "London-Liverpool".
The SwyxLink "London-Liverpool" is managed locally in London and remotely in Liverpool.
In London there is a call permission for the relevant trunk group, allowing only internal calls:
Entry in the call permission of SwyxLink "London-Liverpool" in London:
Allow call *; Trunk group "All"
Deny call +*; Trunk group "All"
In Liverpool a profile was set up for the assigned trunk group, allowing calls via ISDN into the local network in Liverpool.
Entry in the call permission of SwyxLink "London-Liverpool" in Liverpool:
Allow call +44151*; Trunk group "ISDN Liverpool"
If a user from London now calls Liverpool via the SwyxLink "London-Liverpool", his call can be forwarded there into the Liverpool local network (call permission on the Liverpool side!).
On the other hand, if a user from Liverpool now calls London via the SwyxLink "London-Liverpool", his call can only be forwarded to an internal employee, and not into the Liverpool local network (call permission on the Liverpool side!).