
Field Description
External: Use Secure Connection Select Yes to enable HTTPS connections on the
primary Avaya 3100 Mobile Communicator Gateway
public interface using security certificates on the clients
on Avaya 3100 Mobile Communicator Gateway. Select
No to enable HTTP.
Use HTTPS when the clients use certificates to encrypt
communication with the Avaya 3100 Mobile
Communicator Gateway.
The Nokia and Windows Mobile devices, along with
BlackBerry devices that do not employ the enterprise-
hosted BlackBerry Enterprise Server (BES), can use
HTTPS and certificates.
Default: Yes
Internal: Address (IP/host:Port) Enter the address of the primary Avaya 3100 Mobile
Communicator Gateway private interface on the
network.
Configure this parameter if your Avaya 3100 Mobile
Communicator system implementation uses
BlackBerry devices that use the BES.
Internal: Use Secure Connection Select Yes to enable HTTPS connections on the
primary Avaya 3100 Mobile Communicator Gateway
private interface. Select No to enable HTTP.
Default: No
Secondary 3100MCG (all
configurations)
External: Address (IP/host:Port)
Enter the address of the secondary Avaya 3100 Mobile
Communicator Gateway public interface on the
Internet. Client application users connect to this
address when the primary Avaya 3100 Mobile
Communicator Gateway fails. Format: <IP address l
FQDN> :<port>
External: Use Secure Connection Select Yes to enable HTTPS connections on the
secondary Avaya 3100 Mobile Communicator Gateway
public interface using security certificates on the clients
on Avaya 3100 Mobile Communicator Gateway. Select
No to enable HTTP.
Use HTTPS when the clients use certificates to encrypt
communication with the secondary Avaya 3100 Mobile
Communicator Gateway.
The Nokia and Windows Mobile devices, along with
BlackBerry devices that do not employ the enterprise-
hosted BlackBerry Enterprise Server (BES), can use
HTTPS and certificates.
Default: Yes
Procedure job aid
Administration and Security October 2010 35
Kommentare zu diesen Handbüchern