If SwyxConnect is used as a SIP gateway, all SwyxWare components and also SwyxConnect are usually in the same LAN of a company's central location (Fig. C-3: SwyxConnect 5000/8000 as SIP Gateway).

In this example, SwyxConnect logs on to the currently active SwyxServer of the master/ standby pair via SIP REGISTER. SwyxConnect automatically uses SIP OPTIONS to check, which SwyxServer is active. Only the active SwyxServer will reply to the SIP OPTIONS with 200 OK. After the active SwyxServer is detected, SwyxConnect logs in via SIP REGISTER to the SwyxServer. The master and the standby SwyxServer are configured within SwyxConnect in a proxy set.

SwyxConnect can be configured for various trunks. In the example, two trunks are connected to the PSTN in TE mode. These two trunks are configured in SwyxWare as two SIP gateway trunks.

The example further shows the login of an ISDN telephone via Trunk3. In SwyxWare, the ISDN phone is logged in as a SIP user. Thus, the SIP log-in data is stored in the SwyxConnect's Account Table for Trunk3, which is configured in NT mode. SwyxConnect will use this SIP log-in data to log in as a SIP SwyxWare user.

Please note that only the Gateway application is active on SwyxConnect. The SAS application is deactivated by default.