You can configure Call Home to use a proxy server for outbound connectivity to IBM Support.
About this task
Call Home supports both HTTP and HTTPS proxies, including HTTP, HTTPS (TLS), and HTTPS with mutual TLS (mTLS). Select the connection type based on your environment's ability to allow outbound internet access.
Call Home supports direct connectivity and different proxy configurations to align with common
enterprise network and security models.
Important: The Proxy host field must include the protocol:
http:// or https://. A hostname without the protocol prefix is not
accepted. For example: http://proxy.example.com or
https://proxy.example.com.
Procedure
- In the IBM Fusion user interface, go
to
.
- Review and complete the contact information.
- In the Call Home section, click
Edit.
- Select a connection type.
Choose the appropriate connection type based on your network configuration:
- Direct connection
- Use a direct connection when the system can reach IBM Support endpoints directly without routing
through a proxy. No additional fields are required for this option.
- Open proxy
- Use an open proxy when outbound traffic must pass through a proxy that does not require
authentication. This option supports both HTTP and HTTPS proxies. Provide a Certificate Authority
(CA) certificate only if the proxy uses a non-public CA.
- Basic authentication
- Use basic authentication when the proxy requires a username and password for access. This option
supports HTTP and HTTPS proxies. If HTTPS is used and a private CA issues the proxy certificate, a
CA certificate must be provided.
- Certificate authentication
- Use Certificate authentication when the proxy uses certificate-based security. This option
supports TLS and mutual TLS (mTLS), allowing configuration of the CA certificate for server
validation and, when required, a client certificate and private key. It is typically used in
environments with stricter security or compliance requirements. If required by the proxy, username
and password can also be provided.
- Configure the proxy details as required.
The following fields apply whenever a proxy is configured, regardless of authentication type:
| Field |
Required |
Description |
| Proxy host |
Yes (for proxy connections) |
Fully qualified proxy URL. It must start with http:// or
https://. |
| Port |
Yes (for proxy connections) |
Network port on which the proxy listens (for example, 8080 or 3128). |
| Username |
Optional |
Proxy username, if required by the proxy configuration. |
| Password |
Optional |
Proxy password, if required by the proxy configuration. |
| CA certificate |
Conditional |
Certificate Authority (CA) is used to validate the proxy server certificate. Required when
the proxy uses HTTPS (TLS or mTLS) with a private or internal CA. Supported formats:
.crt, .cer, .cert, .ca |
| Client certificate |
Conditional |
A client certificate is presented to the proxy during mutual TLS (mTLS). Required only when
the proxy enforces client certificate authentication. Supported formats: .crt,
.cer, .cert, .ca |
| Client key |
Conditional |
Private key corresponding to the client certificate. Required only for mTLS authentication.
Supported formats: .pem, .key, .crt,
.cer, .cert, .ca |
-
Save and test the configuration.
- Click Save to apply the configuration.
- Click Test connection to validate the configuration.
- If the test succeeds, a success confirmation is displayed and Call Home is configured with the
proxy settings.
- If the test fails, an error message explains the issue. Verify the proxy configuration and test
again.