From 1e51f914672d005b91d0e6a4e983927a690e46dc Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 09:47:54 +0200
Subject: [PATCH 01/12] CFS into Call Forwarding Signal and typos

https://github.com/camaraproject/CallForwardingSignal/issues/193#issue-3238314818
---
 .../call-forwarding-signal.yaml               | 65 +++++++++++--------
 1 file changed, 37 insertions(+), 28 deletions(-)

diff --git a/code/API_definitions/call-forwarding-signal.yaml b/code/API_definitions/call-forwarding-signal.yaml
index adcb2a2..01f1a8c 100644
--- a/code/API_definitions/call-forwarding-signal.yaml
+++ b/code/API_definitions/call-forwarding-signal.yaml
@@ -7,20 +7,23 @@ info:
   title: Call Forwarding Signal
   description: |
     # Overview
-    The Call Forwarding Signal (CFS) API provides the API Consumer with
-    information about the status of the Call Forwading Service on a specific
-    phone number. The main scope of the CFS API is "anti Fraud" to avoid
-    fraudsters to use the Call Forwarding Service to carry on a scam. Other use
-    cases are anyway supported by the CFS API that also provides additional
-    endpoints to detect the general Call Forwarding Service settings.
+    The Call Forwarding Signal API provides the API Consumer with
+    information about the status of the Call Forwarding Service on a specific
+    phone number. The main scope of the Call Forwarding Signal API is "anti
+    Fraud" to avoid fraudsters to use the Call Forwarding Service to carry
+    on a scam. Other use cases are anyway supported by the Call Forwarding
+    Signal API that also
+    provides additional endpoints to detect the general Call Forwarding
+    Service settings.
     # Introduction
     The Call Forwarding Service is provided by the Network to a phone
     number. This service redirects the incoming call to that phone number
     to an alternative destination such as another phone number or a voice mail
     system. There are two main types of call forwarding settings:
     unconditional and conditional.
-    The CFS API can be invoked to detect if the unconditional
-    call forwarding service is active. The CSF API can also be invoked to
+    The Call Forwarding Signal API can be invoked to detect if the unconditional
+    call forwarding service is active. The Call Forwarding Signal API can also
+    be invoked to
     get the general status of the Call Forwarding Service (inactive,
     conditional, unconditional). If conditional call forwarding is active,
     the different type of settings are returned ('conditional_busy',
@@ -34,10 +37,11 @@ info:
     [**Alert Interception**](https://github.com/camaraproject/CallForwarding\
     Signal/discussions/3#discussioncomment-8701847)\
     \
-    [**Call Forwading Verification**](https://github.com/camaraproject/\
+    [**Call Forwarding Verification**](https://github.com/camaraproject/\
     CallForwarding\Signal/discussions/3#discussioncomment-8915595)
     # Quick Start
-    The CFS API is a REST API based on the CreateCallForwardingSignal resource.
+    The Call Forwarding Signal API is a REST API based on the
+    CreateCallForwardingSignal resource.
     This resource can be used, by the API Consumer, to specify the phone number
     on which the Call Forwarding Service status must be verified, in case of
     two-legged authentication. If three-legged authentication is used the phone
@@ -47,11 +51,12 @@ info:
     about the below specified details:\
     \
     **phoneNumber**
-    This is the end user phone number. The CFS API verifies if a call forwarding
+    This is the end user phone number. The Call Forwarding Signal API verifies
+    if a call forwarding
     service is active on this phone number. Note: this parameter must be
-    must be valorised only in case of two-legged authentication. In case of
-    three-legged authentication the phone number is retrived by the access
-    token.
+    must be provided/valued only in case of two-legged authentication.
+    In case of three-legged authentication the phone number is retrieved by
+    the access token.
     \
     \
     **CreateCallForwardingSignal**
@@ -68,14 +73,15 @@ info:
     about the general status of the Network Call Forwarding service for the
     specified phone number.\
     \
-    The CFS API provides two endpoints fulfilling the following intents:
+    The Call Forwarding Signal API provides two endpoints fulfilling the
+    following intents:
     - **unconditional-call-forwardings**: Is the unconditional call fwd service
     active on a specific phone number?
     - **call-forwardings**: Which is the status of the call forwarding for a
     specific phone number?
     # Authorization and authentication
-    The "Camara Security and Interoperability Profile" provides details on how
-    an API consumer requests an access token. Please refer to Identify and
+    The "Camara Security and Interoperability Profile" provides details of how
+    an API consumer requests an access token. Please refer to Identity and
     Consent Management
     (https://github.com/camaraproject/IdentityAndConsentManagement/)
     for the released version of the profile.\
@@ -121,8 +127,8 @@ info:
     this comparison.
     # API Documentation
     ## Details
-    The CFS API is invoked by an API Consumer after the Consent Management
-    flow.\
+    The Call Forwarding Signal API is invoked by an API Consumer after the
+    Consent Management flow.\
     The API Consumer can request the API Producer for the status of the
     Unconditional Call Forwarding service using the
     unconditional-call-forwardings POST method. A boolean, with the information
@@ -135,10 +141,12 @@ info:
     ## Additional CAMARA error responses
     The list of error codes in this API specification is not exhaustive.
     Therefore the API specification may not document some non-mandatory error
-    statuses as indicated in `CAMARA API Design Guidelines`.
+    statuses as indicated in `CAMARA API Design Guide`.
 
-    Please refer to [CAMARA_common.yaml]({link_to_release}/CAMARA_common.yaml)
-    for a complete list of error responses.
+    Please refer to the `CAMARA_common.yaml` of the Commonalities Release
+    associated to this API version for a complete list of error responses.
+    The applicable Commonalities Release can be identified in the
+    `API Readiness Checklist` document associated to this API version.
 
     As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible
     error response if it is explicitly documented in the API.
@@ -229,9 +237,9 @@ paths:
        service active on a phone number (PhoneNumber)
       description: This endpoint provides information about which type of
        call forwarding service is active. More than one service can be
-       active, e.g. conditional and unconditional. This endpoit exceeds
-       the main scope of the CFS API, for this reason an error code 501
-       can be returned.
+       active, e.g. conditional and unconditional. This endpoint exceeds
+       the main scope of the Call Forwarding Signal API, for this reason
+       an error code 501 can be returned.
       operationId: retrieveCallForwarding
       parameters:
         - $ref: '#/components/parameters/x-correlator'
@@ -331,9 +339,10 @@ components:
     ############################################################################
     CreateCallForwardingSignal:
       description: resource containing the phone number (PhoneNumber) regarding
-       which the Call Forwarding Service must be checked. To be valorised only
-       in case of two-legged authentication. If valorised with three-legged
-       authentication a 422-UNNECESSARY_IDENTIFIER error code is returned.
+       which the Call Forwarding Service must be checked. To be provided/valued
+       only in case of two-legged authentication. If provided/valued with
+       three-legged authentication a 422-UNNECESSARY_IDENTIFIER error code is
+       returned.
       type: object
       properties:
         phoneNumber:

From b810dc74d24ed7ffeac51e1c9b33afd7cf4bc228 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 14:11:41 +0200
Subject: [PATCH 02/12] Test file and operationId

https://github.com/camaraproject/CallForwardingSignal/issues/195
---
 .../call-forwarding-signal-every-forwarding.feature             | 2 +-
 .../call-forwarding-signal-unconditional.feature                | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/code/Test_definitions/call-forwarding-signal-every-forwarding.feature b/code/Test_definitions/call-forwarding-signal-every-forwarding.feature
index 22cc893..50a36b5 100644
--- a/code/Test_definitions/call-forwarding-signal-every-forwarding.feature
+++ b/code/Test_definitions/call-forwarding-signal-every-forwarding.feature
@@ -1,4 +1,4 @@
-Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation call-forwardings
+Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveCallForwarding
   # Input to be provided by the implementation to the tester
   #
   # Implementation indications:
diff --git a/code/Test_definitions/call-forwarding-signal-unconditional.feature b/code/Test_definitions/call-forwarding-signal-unconditional.feature
index 0e3b426..4ab3988 100644
--- a/code/Test_definitions/call-forwarding-signal-unconditional.feature
+++ b/code/Test_definitions/call-forwarding-signal-unconditional.feature
@@ -1,4 +1,4 @@
-Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation unconditional-call-forwarding
+Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveUnconditionalCallForwarding
   # Input to be provided by the implementation to the tester
   #
   # Implementation indications:

From 55aaa47869489616f7737eb8285ef3f3d55c23cd Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 14:13:13 +0200
Subject: [PATCH 03/12] Rename call-forwarding-signal-every-forwarding.feature
 to call-forwarding-signal-retrieveCallForwarding.feature

---
 ...re => call-forwarding-signal-retrieveCallForwarding.feature} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename code/Test_definitions/{call-forwarding-signal-every-forwarding.feature => call-forwarding-signal-retrieveCallForwarding.feature} (99%)

diff --git a/code/Test_definitions/call-forwarding-signal-every-forwarding.feature b/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
similarity index 99%
rename from code/Test_definitions/call-forwarding-signal-every-forwarding.feature
rename to code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
index 50a36b5..fdb6e58 100644
--- a/code/Test_definitions/call-forwarding-signal-every-forwarding.feature
+++ b/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
@@ -219,4 +219,4 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveCal
     Then the response status code is 501
     And the response property "$.status" is 501
     And the response property "$.code" is "NOT_IMPLEMENTED"
-    And the response property "$.message" contains a user friendly text
\ No newline at end of file
+    And the response property "$.message" contains a user friendly text

From b386360d5f669712f1460d885160b87d1c76d0b3 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 14:13:38 +0200
Subject: [PATCH 04/12] Rename call-forwarding-signal-unconditional.feature to
 call-forwarding-signal-retrieveUnconditionalCallForwardingfeature

---
 ...orwarding-signal-retrieveUnconditionalCallForwardingfeature} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename code/Test_definitions/{call-forwarding-signal-unconditional.feature => call-forwarding-signal-retrieveUnconditionalCallForwardingfeature} (99%)

diff --git a/code/Test_definitions/call-forwarding-signal-unconditional.feature b/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwardingfeature
similarity index 99%
rename from code/Test_definitions/call-forwarding-signal-unconditional.feature
rename to code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwardingfeature
index 4ab3988..7ad8262 100644
--- a/code/Test_definitions/call-forwarding-signal-unconditional.feature
+++ b/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwardingfeature
@@ -187,4 +187,4 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveUnc
       Then the response status code is 429
       And the response property "$.status" is 429
       And the response property "$.code" is "TOO_MANY_REQUESTS"
-      And the response property "$.message" contains a user friendly text
\ No newline at end of file
+      And the response property "$.message" contains a user friendly text

From 7a8f95a43898b16b4cb443e64ac700ef9baa74ec Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 14:13:58 +0200
Subject: [PATCH 05/12] Rename
 call-forwarding-signal-retrieveUnconditionalCallForwardingfeature to
 call-forwarding-signal-retrieveUnconditionalCallForwarding.feature

---
 ...forwarding-signal-retrieveUnconditionalCallForwarding.feature} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename code/Test_definitions/{call-forwarding-signal-retrieveUnconditionalCallForwardingfeature => call-forwarding-signal-retrieveUnconditionalCallForwarding.feature} (100%)

diff --git a/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwardingfeature b/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature
similarity index 100%
rename from code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwardingfeature
rename to code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature

From 0700a27a02ba4b4cfb96b4135760e6e59ec6ca01 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 14:21:01 +0200
Subject: [PATCH 06/12] Typo

https://github.com/camaraproject/CallForwardingSignal/issues/193#issuecomment-3082898621
---
 .../call-forwarding-signal-retrieveCallForwarding.feature   | 6 +++---
 ...rding-signal-retrieveUnconditionalCallForwarding.feature | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature b/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
index fdb6e58..3c7b74b 100644
--- a/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
+++ b/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
@@ -76,7 +76,7 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveCal
     And the response body is an array of strings with the possible values ["unconditional", "conditional_no_answer", "conditional_not_reachable", "conditional_busy"]
 
   #CFS active: phone number obtained from access token (3-legs authentication) and the CFS status for the phone number is known by the network. phoneNumber not set
-  @call_forwarding_signal_05_call_forwarding_check_active_acess_token
+  @call_forwarding_signal_05_call_forwarding_check_active_access_token
   Scenario: retrieve the call forwarding service settings for a given phone number with call forwarding configured. The endpoint is invoked without a value for phoneNumber and access token is used to obtain the phone number.
     Given the request body property "$.phoneNumber" is not set to a value
     And The header "Authorization" is set to a valid access token identifying a phone number
@@ -202,7 +202,7 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveCal
 
  @call_forwarding_signal_429.2_too_many_requests
   Scenario: The server is not able to handle a request because of a lack of resources
-    Given the number of endpoints calls from any APi Consumer is equal to the server limit
+    Given the number of endpoints calls from any API Consumer is equal to the server limit
     And the endpoint is invoked
     When the HTTP "POST" request is sent
     Then the response status code is 429
@@ -219,4 +219,4 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveCal
     Then the response status code is 501
     And the response property "$.status" is 501
     And the response property "$.code" is "NOT_IMPLEMENTED"
-    And the response property "$.message" contains a user friendly text
+    And the response property "$.message" contains a user friendly text
\ No newline at end of file
diff --git a/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature b/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature
index 7ad8262..b75681b 100644
--- a/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature
+++ b/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature
@@ -181,10 +181,10 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveUnc
 
   @call_forwarding_signal_429.2_too_many_requests
     Scenario: The server is not able to handle a request because of a lack of resources
-      Given the number of endpoints calls from any APi Consumer is equal to the server limit
+      Given the number of endpoints calls from any API Consumer is equal to the server limit
       And the endpoint is invoked
       When the HTTP "POST" request is sent
       Then the response status code is 429
       And the response property "$.status" is 429
       And the response property "$.code" is "TOO_MANY_REQUESTS"
-      And the response property "$.message" contains a user friendly text
+      And the response property "$.message" contains a user friendly text
\ No newline at end of file

From f4238b92eb2ab578c440a388938054596f6f77f7 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 14:53:28 +0200
Subject: [PATCH 07/12] Backslash

https://github.com/camaraproject/CallForwardingSignal/issues/194
---
 .../call-forwarding-signal.yaml               | 64 +++++++++----------
 1 file changed, 31 insertions(+), 33 deletions(-)

diff --git a/code/API_definitions/call-forwarding-signal.yaml b/code/API_definitions/call-forwarding-signal.yaml
index 01f1a8c..8d0435e 100644
--- a/code/API_definitions/call-forwarding-signal.yaml
+++ b/code/API_definitions/call-forwarding-signal.yaml
@@ -27,29 +27,26 @@ info:
     get the general status of the Call Forwarding Service (inactive,
     conditional, unconditional). If conditional call forwarding is active,
     the different type of settings are returned ('conditional_busy',
-    'conditional_not_reachable', 'conditional_no_answer').\
-    \
-    **Example use cases:**\
-    \
-    [**Bank Frauds**](https://github.com/camaraproject/CallForwardingSignal\
-    /discussions/3#discussioncomment-8694420)\
-    \
-    [**Alert Interception**](https://github.com/camaraproject/CallForwarding\
-    Signal/discussions/3#discussioncomment-8701847)\
-    \
-    [**Call Forwarding Verification**](https://github.com/camaraproject/\
-    CallForwarding\Signal/discussions/3#discussioncomment-8915595)
+    'conditional_not_reachable', 'conditional_no_answer').
+
+    **Example use cases:**
+
+    [**Bank Frauds**](https://github.com/camaraproject/CallForwardingSignal/discussions/3#discussioncomment-8694420)
+  
+    [**Alert Interception**](https://github.com/camaraproject/CallForwardingSignal/discussions/3#discussioncomment-8701847)\
+
+    [**Call Forwarding Verification**](https://github.com/camaraproject/CallForwarding\Signal/discussions/3#discussioncomment-8915595)
     # Quick Start
     The Call Forwarding Signal API is a REST API based on the
     CreateCallForwardingSignal resource.
     This resource can be used, by the API Consumer, to specify the phone number
     on which the Call Forwarding Service status must be verified, in case of
     two-legged authentication. If three-legged authentication is used the phone
-    number is instead detected, by the API Producer, from the access token.\
-    \
+    number is instead detected, by the API Producer, from the access token.
+
     Before starting to use the Call Forwarding API, the developer needs to know
-    about the below specified details:\
-    \
+    about the below specified details:
+
     **phoneNumber**
     This is the end user phone number. The Call Forwarding Signal API verifies
     if a call forwarding
@@ -57,22 +54,21 @@ info:
     must be provided/valued only in case of two-legged authentication.
     In case of three-legged authentication the phone number is retrieved by
     the access token.
-    \
-    \
+
     **CreateCallForwardingSignal**
     This is the resource the API Consumer uses to define the phone number to
-    be verified about the status of the Network Call Forwarding service.\
-    \
+    be verified about the status of the Network Call Forwarding service.
+
     **UnconditionalCallForwardingSignal**
     This is the resource the API Consumer gets back, containing the information
     about the Unconditional Call Forwarding Service status for the given phone
-    number (PhoneNumber).\
-    \
+    number (PhoneNumber).
+
     **CallForwardingSignal**
     This is the resource the API Consumer gets back, containing the information
     about the general status of the Network Call Forwarding service for the
-    specified phone number.\
-    \
+    specified phone number.
+
     The Call Forwarding Signal API provides two endpoints fulfilling the
     following intents:
     - **unconditional-call-forwardings**: Is the unconditional call fwd service
@@ -84,14 +80,14 @@ info:
     an API consumer requests an access token. Please refer to Identity and
     Consent Management
     (https://github.com/camaraproject/IdentityAndConsentManagement/)
-    for the released version of the profile.\
-    \
+    for the released version of the profile.
+
     The specific authorization flows to be used will be agreed upon during the
     onboarding process, happening between the API consumer and the API
     provider, taking into account the declared purpose for accessing the API,
     whilst also being subject to the prevailing legal framework dictated by
-    local legislation.\
-    \
+    local legislation.
+
     In cases where personal data is processed by the API and users can
     exercise their rights through mechanisms such as opt-in and/or opt-out,
     the use of three-legged access tokens is mandatory. This ensures that
@@ -128,16 +124,18 @@ info:
     # API Documentation
     ## Details
     The Call Forwarding Signal API is invoked by an API Consumer after the
-    Consent Management flow.\
+    Consent Management flow.
+
     The API Consumer can request the API Producer for the status of the
     Unconditional Call Forwarding service using the
     unconditional-call-forwardings POST method. A boolean, with the information
     about the activation status of the call forwarding service, will be
-    provided back via the UnconditionalCallForwardingSignal resource.\
+    provided back via the UnconditionalCallForwardingSignal resource.
+
     The API Consumer can also request the API Producer for the generic status of
     the Call Forwarding service using the call-forwardings POST method. An array
     of strings with the information of the type of active call forwarding
-    services will be provided back via the CallForwardingSignal resource.\
+    services will be provided back via the CallForwardingSignal resource.
     ## Additional CAMARA error responses
     The list of error codes in this API specification is not exhaustive.
     Therefore the API specification may not document some non-mandatory error
@@ -153,7 +151,7 @@ info:
     # FAQ's
     (FAQs will be added in a later version of the documentation)
 
-  version: 0.4.0-rc.1
+  version: wip
   license:
     name: Apache 2.0
     url: https://www.apache.org/licenses/LICENSE-2.0.html
@@ -165,7 +163,7 @@ externalDocs:
 #                                     Servers                              #
 ############################################################################
 servers:
-  - url: "{apiRoot}/call-forwarding-signal/v0.4rc1"
+  - url: "{apiRoot}/call-forwarding-signal/vwip"
     variables:
       apiRoot:
         default: http://localhost:9091

From 933c67ed735ee86c3a37a388a557751d43623a18 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 14:57:57 +0200
Subject: [PATCH 08/12] MegaLinter Fix

---
 code/API_definitions/call-forwarding-signal.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/code/API_definitions/call-forwarding-signal.yaml b/code/API_definitions/call-forwarding-signal.yaml
index 8d0435e..7578fa7 100644
--- a/code/API_definitions/call-forwarding-signal.yaml
+++ b/code/API_definitions/call-forwarding-signal.yaml
@@ -32,8 +32,8 @@ info:
     **Example use cases:**
 
     [**Bank Frauds**](https://github.com/camaraproject/CallForwardingSignal/discussions/3#discussioncomment-8694420)
-  
-    [**Alert Interception**](https://github.com/camaraproject/CallForwardingSignal/discussions/3#discussioncomment-8701847)\
+
+    [**Alert Interception**](https://github.com/camaraproject/CallForwardingSignal/discussions/3#discussioncomment-8701847)
 
     [**Call Forwarding Verification**](https://github.com/camaraproject/CallForwarding\Signal/discussions/3#discussioncomment-8915595)
     # Quick Start

From 1d0a8c3eb3b74647104265951d183d5fd9c69ba6 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Thu, 31 Jul 2025 16:14:49 +0200
Subject: [PATCH 09/12] typo

---
 code/API_definitions/call-forwarding-signal.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/code/API_definitions/call-forwarding-signal.yaml b/code/API_definitions/call-forwarding-signal.yaml
index 7578fa7..00c5398 100644
--- a/code/API_definitions/call-forwarding-signal.yaml
+++ b/code/API_definitions/call-forwarding-signal.yaml
@@ -136,7 +136,7 @@ info:
     the Call Forwarding service using the call-forwardings POST method. An array
     of strings with the information of the type of active call forwarding
     services will be provided back via the CallForwardingSignal resource.
-    ## Additional CAMARA error responses
+    # Additional CAMARA error responses
     The list of error codes in this API specification is not exhaustive.
     Therefore the API specification may not document some non-mandatory error
     statuses as indicated in `CAMARA API Design Guide`.

From fbd2a19fd3b97471c3b738608e36280802cecd84 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Fri, 1 Aug 2025 12:47:02 +0200
Subject: [PATCH 10/12] info.description reordering

https://github.com/camaraproject/CallForwardingSignal/issues/197
---
 .../call-forwarding-signal.yaml               | 30 +++++++++----------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/code/API_definitions/call-forwarding-signal.yaml b/code/API_definitions/call-forwarding-signal.yaml
index 00c5398..3fbcb67 100644
--- a/code/API_definitions/call-forwarding-signal.yaml
+++ b/code/API_definitions/call-forwarding-signal.yaml
@@ -75,6 +75,21 @@ info:
     active on a specific phone number?
     - **call-forwardings**: Which is the status of the call forwarding for a
     specific phone number?
+    # API Documentation
+    ## Details
+    The Call Forwarding Signal API is invoked by an API Consumer after the
+    Consent Management flow.
+
+    The API Consumer can request the API Producer for the status of the
+    Unconditional Call Forwarding service using the
+    unconditional-call-forwardings POST method. A boolean, with the information
+    about the activation status of the call forwarding service, will be
+    provided back via the UnconditionalCallForwardingSignal resource.
+
+    The API Consumer can also request the API Producer for the generic status of
+    the Call Forwarding service using the call-forwardings POST method. An array
+    of strings with the information of the type of active call forwarding
+    services will be provided back via the CallForwardingSignal resource.
     # Authorization and authentication
     The "Camara Security and Interoperability Profile" provides details of how
     an API consumer requests an access token. Please refer to Identity and
@@ -107,7 +122,6 @@ info:
     three-legged access token to invoke the API by relying on the
     information that is associated with the access token and was
     identified during the authentication process.
-
     ## Error handling:
 
     - If the subject cannot be identified from the access token and the
@@ -121,21 +135,7 @@ info:
     error code. This will be the case even if the same device is
     identified by these two methods, as the server is unable to make
     this comparison.
-    # API Documentation
-    ## Details
-    The Call Forwarding Signal API is invoked by an API Consumer after the
-    Consent Management flow.
 
-    The API Consumer can request the API Producer for the status of the
-    Unconditional Call Forwarding service using the
-    unconditional-call-forwardings POST method. A boolean, with the information
-    about the activation status of the call forwarding service, will be
-    provided back via the UnconditionalCallForwardingSignal resource.
-
-    The API Consumer can also request the API Producer for the generic status of
-    the Call Forwarding service using the call-forwardings POST method. An array
-    of strings with the information of the type of active call forwarding
-    services will be provided back via the CallForwardingSignal resource.
     # Additional CAMARA error responses
     The list of error codes in this API specification is not exhaustive.
     Therefore the API specification may not document some non-mandatory error

From c553aa7627dda24f045fbf786092108d95e64167 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Fri, 1 Aug 2025 13:32:04 +0200
Subject: [PATCH 11/12] Path in Background section

https://github.com/camaraproject/CallForwardingSignal/issues/198
---
 ...warding-signal-retrieveUnconditionalCallForwarding.feature | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature b/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature
index b75681b..cf6e25c 100644
--- a/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature
+++ b/code/Test_definitions/call-forwarding-signal-retrieveUnconditionalCallForwarding.feature
@@ -1,4 +1,4 @@
-Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveUnconditionalCallForwarding
+Feature: CAMARA Call Forwarding Signal  API, vwip - Operation retrieveUnconditionalCallForwarding
   # Input to be provided by the implementation to the tester
   #
   # Implementation indications:
@@ -8,7 +8,7 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveUnc
   # * A device object identified by a phone number for which unconditional call forwarding service (CFS) status could not be retrieved
   #
   Background: Common call-forwarding-signal setup
-    Given the path "/unconditional-call-forwardings"
+    Given the path "/call-forwarding-signal/vwip/unconditional-call-forwardings"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"

From c43d51b0c209f85fdcdc0150ab4753d51718c248 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Fri, 1 Aug 2025 14:43:31 +0200
Subject: [PATCH 12/12] Path in Background section

https://github.com/camaraproject/CallForwardingSignal/issues/198
---
 .../call-forwarding-signal-retrieveCallForwarding.feature     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature b/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
index 3c7b74b..a06e910 100644
--- a/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
+++ b/code/Test_definitions/call-forwarding-signal-retrieveCallForwarding.feature
@@ -1,4 +1,4 @@
-Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveCallForwarding
+Feature: CAMARA Call Forwarding Signal  API, vwip - Operation retrieveCallForwarding
   # Input to be provided by the implementation to the tester
   #
   # Implementation indications:
@@ -8,7 +8,7 @@ Feature: CAMARA Call Forwarding Signal  API, v0.4.0-rc.1 - Operation retrieveCal
   # * A device object identified by a phone number for which the call forwarding service status could not be retrieved
   #
   Background: Common call-forwarding-signal setup
-    Given the path "/call-forwardings"
+    Given the path "/call-forwarding-signal/vwip/call-forwardings"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"