Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

State terminology not user friendly #111

Closed
FabrizioMoggio opened this issue Dec 3, 2024 · 3 comments
Closed

State terminology not user friendly #111

FabrizioMoggio opened this issue Dec 3, 2024 · 3 comments
Labels

Comments

@FabrizioMoggio
Copy link
Collaborator

Problem description
The terms used into the returned states of conditional call forwarding are not standard.

Expected behavior
from conditional_unavailable to conditional_not_reachable
from conditional_no_reply to conditional_no_answer

Alternative solution

Additional context
#110

@rartych
Copy link
Collaborator

rartych commented Dec 16, 2024

According to 3GPP TS 22.082 version 17.0.0 Release 17 standard names for these services are:

  • Call Forwarding on No Reply
  • Call Forwarding on Mobile Subscriber Not Reachable

But CAMARA should avoid telco specific terminology and should be developer friendly first.

For me conditional_not_reachable is the good choice.
I have no preference for conditional_no_reply or conditional_no_answer.

@FabrizioMoggio FabrizioMoggio changed the title State terminology not standard State terminology not user friendly Dec 17, 2024
FabrizioMoggio added a commit to FabrizioMoggio/CallForwardingSignal that referenced this issue Dec 17, 2024
State terminology not user friendly: camaraproject#111
@FabrizioMoggio
Copy link
Collaborator Author

Fixed with: #117

@FabrizioMoggio
Copy link
Collaborator Author

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants