SwyxConnect basically consists of two functional units (applications):

The first application is the gateway. The gateway provides the functionality to make ISDN and analog calls, and serves, at the same time, as a bridge into the SIP network. Thus, calls can be forwarded per SIP from the IP network to the ISDN or analog network, and the other way around. This function is comparable to the SwyxGate. The gateway application is always active.

The second application is the SAS application (Stand Alone Survivability). It can optionally be activated and must be separately licensed. The SAS application is comparable to a SIP proxy. Provided that SwyxConnect is connected to Swyx via IP, the SAS application will act solely as a proxy that transparently forwards all SIP messages between the SIP endpoints. This ensures that all additional functions used by SIP endpoints with Swyx are retained (e.g., SIP Subscribe for name button statuses, MWI for voice mailbox display, etc.). In the event that the IP connection (e.g., VPN connection) between Swyx and SwyxConnect fails, the SAS application can automatically take over the switching function between the SIP endpoints. In other words, SwyxConnect can provide full PBX functionality in this case and route calls between the PSTN gateway, the SIP endpoints, and the ISDN or analog phones registered via SIP.

As SwyxConnect is separated into two functional units, two TCP/UDP ports have to be used (one port per application).