This manual explains how to configure your company's UFTP settings for participation in Capacity Steering Contracts (CSC) and Alternative Transport Rights (ATR).
For more information about working with UFTP messages, please refer to one of the following manuals:
Use own UFTP implementation for handling CSC and ATR calls – for companies using their own UFTP implementation.
Receiving and processing CSC activations via the GOPACS platform – for companies using the GOPACS platform.
Handling CSC activations via the GOPACS Pull API – for companies using the GOPACS Pull API.
The steps in the instruction manual are described in table form to clearly define the steps. The following columns are defined.
Column | Definition |
|---|---|
Step | Order in which the steps are needed to be executed. |
Description | Describes in detail what happens in the step. |
Is a term unclear? You’ll likely find its definition in our Glossary.
The English the glossary is located here: Glossary - GOPACS
De Nederlandse begrippenlijst vind je hier: Begrippenlijst - GOPACS
More manuals can be found here: Manuals
If you need help or have questions, you can find our details here: Contact
Step | Description |
|---|---|
1 | Open the UFTP Details page Navigate to your company details page in the appropriate environment: Acceptance (ACC) Production (PROD) |
2 | Select the method for handling CSC conversations Choose how your company will handle CSC communication.  Using the GOPACS platformIf you want to use the GOPACS platform for CSC activations, select ‘Use the GOPACS UI’ and click ‘Save Changes’. No further configuration is required. Using the GOPACS Pull API If you want to use the GOPACS Pull API for CSC activations, select ‘Use the GOPACS Pull API’, authorise GOPACS to handle message exchange with the TC on your behalf. and click ‘Save Changes’. No further configuration is required. Using your own UFTP implementationIf you want to use your own UFTP implementation for CSC activations, select ‘Use own UFTP-implementation’ and continue with Step 3. |
3 | Configure the UFTP settings Complete the following fields: UFTP DomainA unique identifier used for UFTP communication. The value has no functional purpose other than identifying your organisation within the UFTP network. UFTP EndpointThe endpoint to which the GOPACS UFTP Message Broker sends messages intended for your organisation. Only HTTPS endpoints are supported. The URL must therefore start with:
UFTP Public KeyThe public key used by recipients of your messages to decrypt the encrypted content. For more information about these fields, please refer to the manual Use own UFTP implementation for handling CSC and ATR calls.  |
4 | Configure OAuth 2.0 (Optional) Optionally, you can require the GOPACS UFTP Message Broker to authenticate itself when delivering messages to the endpoint configured in Step 3. Note: This authentication mechanism is separate from the OAuth2 credentials used to access the GOPACS APIs or communicate with the Message Broker. If you enable OAuth2 authentication, provide the following information:
Note: The Client Secret is displayed only once and cannot be viewed again after saving.  |
5 | Save your changes After completing the configuration, click ‘Save Changes’. |
