Remote Working

With the Remote Worker feature enabled, remote 9600 H.323 or SIP J100 IP Phones can connect to IP Office even if it is located behind a NAT router. The same applies to supported client applications, see supported SIP endpoints. The sets or applications are authenticated on IP Office in the same way as if in the private network. The IP Office determines that the user is located outside the private network and relays the VoIP RTP traffic to ensure it transverses the NAT router.

The following 9600 phones are supported:

• 9620, 9630, 9640, 9650

  Note:

  The H.323 signaling and the media traffic is not encrypted however the proprietary binary format adds a basic level of encryption.

• 9608, 9611, 9621, 9641

  Note:

  The H.323 signaling and media traffic may be encrypted using TLS and SRTP respectively.

The following SIP endpoints are supported:

• Avaya J100 Series IP Phones:

  • J129 (Standard SIP phone)

  • J139, J159,J169,J179, J189 (SIP Feature phones)

• Avaya Vantage™ 2.2 version: K165, K175 and K155

• Avaya Vantage™ 3.0 version and above: K175 and K155

• Avaya Workplace Client platforms:

  • Avaya Workplace Client for Windows

  • Avaya Workplace Client for Android

  • Avaya Workplace Client for Mac

  • Avaya Workplace Client for iOS

• B179

• B199

To reach the IP Office from the remote private network, remote IP phones or client applications need to be configured to point to the public IP address of the NAT router hosting IP Office. Configurable ports need to be forwarded to IP Office. IP Office requires a valid public IP address configured for the feature to function. The public IP address can be statically configured or dynamically discovered via a STUN server.

Administrators enable Remote Worker feature using IP Office Manager. To use the Remote Worker feature, you require the Essential Edition license. The Essential Edition license provides 4 remote workers.

Additional Remote Workers can be configured if those additional users are licensed and configured with either Teleworker or Power User user profiles

SIP phones using Avaya SBCE

The Avaya Session Border Controller for Enterprise (Avaya SBCE) sits on the edge of customer’s network with both internal and external IP interfaces. Using these IP interfaces, Avaya SBCE functions as the gateway for SIP traffic into and out of the network. When used internally, SIP clients register to the IP Office directly. When used externally, the SIP clients connect to the Avaya SBCE. This is achieved using Split DNS, which automatically resolves the FQDNs to the internal IP address of the IP Office or the public IP address of the Avaya SBCE depending on where the clients are currently located. Apart from acting as a gateway, Avaya SBCE also provides protection against any external SIP-based attacks. For privacy over the public internet, the public side of the Avaya SBCE facing the remote workers must be configured to use the recommended values of TLS for signaling and SRTP for media encryption, as long as they are supported by the endpoints.

The following endpoints are supported as IP Office Remote Workers with Avaya SBCE.

• Avaya J100 Series IP Phones:

  • J129 (Standard SIP phone)

  • J139, J159, J169, J179, J189 (SIP Feature phones)

• Avaya Vantage™ 2.2 version: K165, K175 and K155

  Avaya Vantage™ 3.0 version and above K175 and K155

• Avaya Workplace Client platforms:

  • Avaya Workplace Client for Windows

  • Avaya Workplace Client for Android

  • Avaya Workplace Client for Mac

  • Avaya Workplace Client for iOS