2. Navigate to Device Specific Settings > DMZ Services > Relay Services > Reverse
Proxy.
3. Click Add.
4. In Service Name, enter a name for the profile.
5. Select the Enable check box to enable the reverse proxy profile.
6. In Listen IP, select the internal A1 interface and the Avaya SBCE external leg IP address.
7. In Listen Port, enter 443.
8. In Listen Protocol, select HTTPS.
9. In Listen TLS Profile, select the TLS server profile that you created.
An example of the TLS server profile name is webservicesTlsProfile.
10. In Connect IP, select the internal A1 interface and the Avaya SBCE internal leg IP
addresses.
11. In Server Protocol, select HTTPS.
12. In Server TLS Profile, select the TLS client profile that you created.
An example of the TLS client profile name is certificateAuthorityTLSProfile.
13. Select the Rewrite URL check box.
14. Click Add at the bottom of the page to create a set of rules and configure the rules as
described in
Internal traffic rules for a single FQDN deployment on page 116.
15. Click Finish.
Related links
Internal traffic rules for a single FQDN deployment on page 116
Reverse proxy configuration checklist for a single FQDN deployment on page 109
Internal traffic rules for a single FQDN deployment
Server Address
White list
URL
URL
replace
Description
<Equinox Management
FQDN>:443
/uwd/
rest
/uwd/
rest
Equinox Conference Control (UCCS) Equinox
Management FQDN resolves to the virtual IP of the
Equinox Management Server.
If you are using a standalone system, this FQDN
resolves to the virtual IP address. For example:
conferencing_management.company.com.
<Equinox Management
FQDN>:443
/uwd/ws /uwd/
rest
<WCS1 FQDN>: 443
/wcs1 /
Avaya Aura
®
Media Server. You must create one
entry per each Web Collaboration Services server.
The FQDN is the FQDN of each Avaya Aura
®
Media
Server, and it resolves to the corresponding Avaya
Aura
®
Media Server IP. For example:
<WCS2 FQDN>: 443
/wcs2 /
<WCSX FQDN>: 443
/wcsX /
Table continues…
Avaya Session Border Controller for Enterprise configuration
October 2018 Deploying the Avaya Aura
®
Web Gateway 116
Comments on this document? infodev@avaya.com
To Next Page
Loading...
