When SwyxConnect is used as a SIP gateway, all Swyx components—including SwyxConnect —are typically located on the same LAN as a company’s main office; see 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 Swyx as two SIP gateway trunks.

The example further shows the login of an ISDN telephone via Trunk3. The ISDN phone is registered as a SIP user in Swyx. 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 these SIP login credentials to log in as a SIP Swyx user.

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