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

Add MultiSIM section to info.description #291

Merged
merged 3 commits into from
Jan 23, 2025
Merged

Add MultiSIM section to info.description #291

merged 3 commits into from
Jan 23, 2025

Conversation

jlurien
Copy link
Collaborator

@jlurien jlurien commented Jan 23, 2025

What type of PR is this?

  • documentation

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

* Adding section for "Multi-SIM scenario handling" in info.description

@jlurien
Copy link
Collaborator Author

jlurien commented Jan 23, 2025

fyi @javier-carrocalabor

Copy link

github-actions bot commented Jan 23, 2025

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.02s
✅ OPENAPI spectral 3 0 4.91s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY secretlint yes no 0.84s
✅ YAML yamllint 3 0 0.79s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security


- 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.
Copy link
Collaborator

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adjusted

maxl2287
maxl2287 previously approved these changes Jan 23, 2025
Copy link
Contributor

@maxl2287 maxl2287 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@bigludo7 bigludo7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Thanks Jose !

@maxl2287 maxl2287 merged commit f4578bd into main Jan 23, 2025
2 checks passed
@maxl2287 maxl2287 deleted the info-multisim branch January 23, 2025 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support of Multi-SIM lines in DeviceLocation APIs
4 participants