help | 9 Profiles | Call Permissions | Call permission of a user | Example 3
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 (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!).
Last modified date: 01/24/2024