4.4.2 Migration Scenarios
Here we have an existing telecommunication system which is used together with SwyxWare.
The aim is to assign telephone numbers of the same length from within a possible range of numbers to all internal subscribers, regardless of whether they are connected to a traditional private branch exchange (PBX) or they use SwyxWare to place telephone calls. Moreover, all users should be able to dial an external line using the same procedure (e.g. "0" for public line access, followed by the destination number in the public network). For more details on the configuration of the SwyxGate settings mentioned below and on the configuration of its lines, please read
The "ISDN Ports" Tab.
Example 1:SwyxWare as sub-telecommunication system
SwyxGate is connected to the traditional private branch exchange (PBX) using one line. Calls to A and B will be put through directly by the PBX. Calls from the public telephone network to C, D and E are forwarded to SwyxServer by the PBX and delivered from there. Calls from the SwyxWare users C, D and E into the public network are first forwarded to the PBX. The PBX then forwards these calls to the public network. Internal calls between A or B and C, D or E stay within the company.
Fig. 4-3: SwyxGate connected to PBX
Example 2:SwyxWare in addition to a telecommunications system
SwyxGate is connected via one line to the traditional private branch exchange (PBX) and to the public network with a second line.
Fig. 4-4: SwyxGate to PBX and PSTN
This scenario is useful when you are migrating an old PBX over to SwyxWare in order to improve the availability of external lines for SwyxWare users without having to add more modules to the existing PBX.
Example 3: SwyxWare with a sub-telecommunication system
A SwyxGate is installed between the public network (PSTN) and the private branch exchange (PBX):
Fig. 4-5: SwyxGate connected between PBX and PSTN