Create APIproposal_Voice OTP Call

[mbkhanhex]

The “Voice One Time Password Call” API is used to send short-lived one time passwords (OTP) to a phone number via voice call and validate it afterwards, in order to provide a proof of possession of the phone number.

What type of PR is this?

Add one of the following kinds:

• bug
• correction
• enhancement/feature
• cleanup
• documentation
• subproject management
• tests

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[mbkhanhex]

Please review and approve

[mbkhanhex]

Please review and approve

[mbkhanhex]

Hi @albertoramosmonagas Following your instructions, I have created API Proposal under documentation/API-proposals. Let me know about the next steps. Thanks

[albertoramosmonagas]

Hi @albertoramosmonagas Following your instructions, I have created API Proposal under documentation/API-proposals. Let me know about the next steps. Thanks

Hi, the file is empty and you need to upload also de ppt of your presentation.

The only point left is relation with Voice Verification Code (#233) - Herbert suggest if we can merge this with this issue. Can you review this proposal to see if there's any overlap?

Once all these points have been resolved, the backlog group will review it to see if there are any issues or objections, and if not, send it to the TSC.

[mbkhanhex]

Hi @albertoramosmonagas I have created new PR as per your request #265. Please help for the next steps. Regarding merger with other API use case, I am not exactly sure about it. Is it possible to consider this merger possibility at later stage?

[albertoramosmonagas]

Hi @mbkhanhex,

I think we're not quite understanding each other, or maybe I'm not explaining myself well.

There was already an issue for this API, which was #259. The problem we had was with the Pull Request (PR), not the issue. I'm attaching it here: https://github.com/camaraproject/APIBacklog/pull/263/files

As you can see, the file has been created, but it is empty. This is what needs to be modified.

So I would close this issue. The old one remains as the original, and all that needs to be done is to upload the changes from the API proposal to the pull request with the ppt that you have very kindly attached here.

Once this is done, the following point was raised in the latest backlogs:

The only point left is relation with Voice Verification Code (#233) - Herbert suggests if we can merge this with this issue. Can you review this proposal to see if there's any overlap?

Once all these points have been resolved, the backlog group will review it to see if there are any issues or objections, and if not, send it to the TSC.

Once everything is complete, the API will be discussed in the backlog session and, if there are no objections, it will be sent to the TSC.

[albertoramosmonagas]

Remember that it's not just a matter of copying and pasting; you have to follow the template format, just as you did in the old PR that had the wrong path.

[mbkhanhex]

@albertoramosmonagas apologies for confusion. I have just updated the PR, please check 2bd5b64.

[mbkhanhex]

@albertoramosmonagas changes are updated. Please check now and let me know in case of any modifications needed. Thanks for your kind support

[albertoramosmonagas]

The file is "APIproposal_Voice OTP Call" and need to be "API-proposal-voice-otp-call.md" without the final extension, it is simply a text file

[albertoramosmonagas]

This would go inside the API summary; these points are not part of the template.

[mbkhanhex]

@albertoramosmonagas moved to API summary, please check

[albertoramosmonagas]

And if you already have a YAML file from the API, you can upload it to this PR, but to the documentation/SupportingDocuments path with the API name.

[mbkhanhex]

@albertoramosmonagas I dont have the privileges to do so, please check the snapshot below

[albertoramosmonagas]

In this case, it is not “uploading a file” by attaching it to the pull request. In the “mbkhanhex:patch-3” branch you created, you would create a new file in the “documentation/SupportingDocuments” path for the YAML and another for the PPT associated with the proposal.

[albertoramosmonagas]

Specify if was a lab network or productive network

[mbkhanhex]

It is already mentioned as Lab environment, please check

[albertoramosmonagas]

I don't understand why my previous comment was resolved if the change wasn't applied. This isn't a section of the template. In any case, this has to be inside the “### API summary.” It has to be removed from here.

[mbkhanhex]

@albertoramosmonagas needful done

[albertoramosmonagas]

As with the other comment that has been resolved but not implemented, this point needs to be included. Please follow the template.

### Supporters in API Backlog Working Group  
List of supporters.  
*NOTE: That shall be added by the Working Group. Supporting an API proposal means that the supporting company must provide at least 1 (one) Maintainer at the time of the Sub Project creation.*

[albertoramosmonagas]

@mbkhanhex Please, review the comments, there are too many small changes to make, but I would appreciate it if you could be mindful of what you are modifying, as it is difficult to find the time to make these kinds of revisions.

Also, if possible, you have two duplicate issues, #259 (the first issue created for this API) and #265 . I would appreciate it if you could delete one of them.

Also, please note that your file path is “documentation/API proposals/APIproposal_Voice OTP Call” and should be “documentation/API proposals/APIproposal_Voice OTP Call.md.”

Another point, it would be good if you could upload the ppt you shared in the backlog to the path “documentation/SupportingDocuments” to the PR.

Finally, regarding the comment about reviewing and approving, the process would be:

• Apply all the changes I have described.
• Review Relation with Voice Verification Code (#233) - Herbert suggests if we can merge this with this issue.
• And the point I mentioned about the possible overlap with OTPValidation.

If you have any questions about these points, we can discuss them in the backlog sessions.

[mbkhanhex]

@albertoramosmonagas regarding your comment to upload the ppt to the path “documentation/SupportingDocuments” to the PR, I tried doing it however it seems that I dont have the privileges to do so. Please help.

[mbkhanhex]

@albertoramosmonagas regarding your suggestion to merge our issue proposal with #233, we have checked and it looks like that their use case works only for "IMS based audio codes" as explained in their API description which is not the case for our API. So we dont think that merging the two issues would be a good idea. If there is any further discussion needed on that, we can have a call to evaluate it.

[albertoramosmonagas]

Hi @mbkhanhex, I have been reviewing the PR and it is in better shape. Here are some points for reflection:

• There are inconsistencies (e.g., you talk about 2FA “via SMS” in a voice API).
• The “Commercial viability” section does not answer the question (you talk about the cloud instead of the market/business).
• Debatable statements: “fast and more secure than SMS” without nuance or evidence. Any demanding reviewer will tear that apart.

And don't forget to check the comments we've left. I'd like to submit this API to the next backlog (so it can be added to the session) to see if there are any objections from the other reviewers and we can send it to the next TSC.

[linux-foundation-easycla]

• ✅ login: mbkhanhex / name: mbkhanhex (03399a4, 03461b5, 03b1810, 0e99810, 1ea62cd, 2874f41, 2bd5b64, 30f744f, 369e172, 3f7c0de, 66e7e5b, 68a16e0, 85c677c, 92a07b1, 92d5b5b, 992df41, ae8875e, af8316a, c1da7c6, e98cc0e, e9cb367)
• ❌ The email address for the commit (76736f0) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[mbkhanhex]

Please review and approve

[mbkhanhex]

@albertoramosmonagas all suggested changes have been addressed and accordingly the API proposal for Voice OTP call has been updated accordingly. Please review and approve the suggested merging changes.

[mbkhanhex]

Submitted, please review and approve.

[albertoramosmonagas]

Hi @mbkhanhex,

Perhaps the problem with uploading files can be seen in this message that appears above:

❌ The email address for the commit (76736f0) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

Here you have the link of the comment. If I could fix it, that would be great.

After that, I don't know if there is any conclusion on this point: link. Also, I see that there is a commit that was not made by you, in which a new file “APIBacklog” is added with a message “Subproject commit ce57fee.” Could you delete it? Here is the 76736f0 diff-186da9b0f4176666e9d4d1e31e44c4910bb8cce178fbf939b781524263d8281a where it comes from.

Looking ahead to the next steps with this API, it would be great to discuss it in the next backlog session (January 8, 2026) and refresh the other participants' memories, as well as discuss the latest changes to the PR.

In the meantime, I would appreciate it if you could resolve the items we have discussed in this message.