Content Comparison

...

Minutes

DeviceStatus

Open PRs

• #257 Remove INVALID_TOKEN_CONTEXT error-code based on Commonalities 0.5.0-rc.1

• #244 Prepare release r2.1

  • Ready for review

  • Some assets, needed for the public release, will be provided during the release candidate phase

    • Extended testcases for the 2 stable APIs

    • Use case descriptions for the 2 stable APIs

    • Test results for the 2 stable APIs

• #255 Add extended test cases for device-roaming-status and device-reachability-status + refactor *.feature-files

Open issues

• #256 Remove INVALID_TOKEN_CONTEXT based on Commonalities v0.5.0-rc.1

  • PR #257 is open

• #253 Create user story for device-roaming-status and device-reachability-status APIs

  • Managed in PR244

...

• #236 Create extended test cases for device-roaming-status and device-reachability-status

  • PR #255 is open

• #224 Scope for Spring25 release

  • Team decided to go for stable versions with device-roaming-status and device-reachability-status

• #212 Support of Multi-SIM lines in DeviceStatus APIs

  • Discussion still open in commonalities

  • Target release is Spring25, with a description how the APIs work in a multi-SIM setup#138 How to respond if queried device does not have an active session?

  • Request documentation enhancement

• #119 How can a provider inform the ASP/aggregator about not implemented features in advance of the API call

  • no update

• #115 /Connectivity API there is no indication for which particular subscriber event (DATA/SMS)

  • no update

...