The VersaLex application contains an Odette FTP (OFTP) server which can host either ISDN (Windows users only) or TCP/IP OFTP sessions.
- Click the Local Listener in the tree pane, and then click the OFTP tab.
- Specify parameter values as appropriate.
See OFTP Local Listener reference for information about the parameters available.
- Click Apply.
OFTP Local Listener reference
- Listen for incoming ISDN connections. ISDN equipment must already be installed and must support the Common ISDN API (CAPI) interface, version 2.0.
- My OFTP ISDN Address(es)
- If you select ISDN, specify which of your ISDN Address(es) you want to use for OFTP. When filling in your ISDN OFTP phone number(s), only specify the local number. Do not include your area code, country code, or any other prefixes. The phone numbers configured are only used for screening incoming calls. Outgoing calls are automatically referenced by the ISDN layer to your calling number.
- Log ignored incoming ISDN calls
- Toggles making entries in the system log whenever an incoming ISDN call is ignored.
- Listen for incoming TCP/IP connections.
- Specify a Port number. By default, the VersaLex application will listen on standard OFTP port 3305, but any port number can be specified.
- You can configure TCP/IP to listen on multiple ports by separating the field values with commas. For example, suppose you specified port 3305, but you have some trading partners who have outbound firewall restrictions and can only send to port 21. Specifying 3305,21 in the Port field allows the firewall-restricted trading partners to be able to send to your server while allowing you to continue to accept inbound messages from your other trading partners on port 3305.
- Secure TCP/IP
- Listen for incoming secure TCP/IP connections. This is for OFTP2 connections connection using Transport Layer Security (TLS).
- Specify a Port number. By default, the VersaLex application will listen on standard OFTP port 6619, but you can specify any other unused port value in the range of 1024 - 65535. Using non-standard ports in the range of 1 - 1023 might interfere with port numbers reserved by TCP/IP for other purposes.
- You can configure multiple ports by separating the field values with commas. For example, suppose you specified port 6619, but you have some trading partners who have outbound firewall restrictions and can only send to port 25. Specifying 6619,25 in the Port field allows the firewall-restricted trading partners to be able to send to your server while allowing you to continue to accept inbound messages from your other trading partners on port 6619.
- SSL Server Certificate
- If you select TCP/IP or Secure TCP/IP, select a valid SSL Server Certificate. Click Browse... to navigate to and select a certificate. Then, enter the Password for the SSL Server Certificate's private key.
- Authenticate Client
- Select Authenticate Client to require the SSL client to provide a valid certificate during SSL negotiation.
- Select Optional to request (but not require) the SSL client to provide a valid certificate during SSL negotiation.
- Verify Key Usage
- Select Verify Key Usage to validate that the SSL client certificate contains the "clientAuth" extended key usage setting.
- Authentication Certificates
- By default, all of the Certificate Manager Trusted CA and user certificates are accepted for client authentication. To change this, use the Authentication Certificates button to establish the list of accepted OFTP client authentication certificates, which can be:
- all or a subset of the trusted CA certificates and/or
- all or a subset of the user certificates.
- Exchange Certificates
- Click Exchange Certificates to send the SSL Server Certificate to your trading partner(s). See Exchanging certificates with your trading partner for further information.
Please sign in to leave a comment.