-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add MultiSIM section to info.description #291
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
|
||
- Using preferably the authorisation code flow to obtain an access token, which will automatically identify the intended device. | ||
- Identifying the intended device from a unique identifier for that device, such as its source IP address and port. | ||
- Check with the SIM provider whether a unique "secondary" phone number is already associated with each device and use the secondary phone number to identify the intended device if available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In line 74 we use the term API provider, but here we use SIM provider. Could we use a common term like service provider or opco ? Thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adjusted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks Jose !
What type of PR is this?
What this PR does / why we need it:
Current documentation omits the potential problem with phone numbers identifying a MultiSIM group. As there is no a single behaviour agreed in CAMARA yet, the proposed enhancement presents the problem and gives some hints to mitigate it
Which issue(s) this PR fixes:
Fixes #257
Special notes for reviewers:
Changelog input