If SwyxConnect 6000 is used as a SIP gateway, all SwyxWare components and also SwyxConnect 6000 are usually in the same LAN of a company's central location (see Figure C-3).

In this example, SwyxConnect 6000 logs on to the currently active SwyxServer of the master/ standby pair via SIP REGISTER. SwyxConnect 6000 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 6000 logs on via SIP REGISTER to the SwyxServer. The master and the standby SwyxServer are configured within SwyxConnect 6000 in a proxy set.

SwyxConnect 6000 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 third-party SIP gateway trunks.

The example further shows the login of an ISDN telephone via Trunk3. In SwyxWare, the ISDN phone is logged on as a SIP user. Thus, the SIP log-in data is stored in the SwyxConnect 6000's Account Table for Trunk3, which is configured in NT mode. SwyxConnect 6000 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 6000. The SAS application is deactivated by default.