[Call Forwarding Signal] unconditional-call-forwardings endpoint rationale

[marta-ramirez]

Hello community,

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?

While the use of each endpoint is very clear, it seems the result provided by unconditional-call-forwardings can be easily derived from the response given by call-forwardings, and even if the CSP/supplier would not return all active CFW types, it could still perform by returning "Inactive" and "Unconditional".

Would it be possible to have some more clarity on why the unconditional-call-forwardings endpoint is required?

Thanks!

[FabrizioMoggio]

Dear @marta-ramirez, sorry for the late answer, I completely missed you comment.

I totally get you point, we indeed had many discussions on having just one endpoint covering all the use cases or two endpoints, one to cover frauds related uses cases (UseCase-1: Bank Frauds: #3 (comment)) and one to cover more generic use cases (UseCase-3: Call FWD Verification: #3 (comment))

We decided to have keep the unconditional-call-forwardings endpoint to cover what was perceived by the group as the more relevant use case that was fraud related (https://www.gsma.com/solutions-and-impact/gsma-open-gateway/gsma-open-gateway-api-descriptions/). This endpoint, specifically targets what, according to our discussion, is the type of call forwarding that is used in frauds scenarios.

Please have a look to this discussion: #8

And its conclusion: #8 (comment)