Skip to content

fix(calling): new method getDevices added#4684

Open
Kesari3008 wants to merge 5 commits intowebex:nextfrom
Kesari3008:CAI-7541
Open

fix(calling): new method getDevices added#4684
Kesari3008 wants to merge 5 commits intowebex:nextfrom
Kesari3008:CAI-7541

Conversation

@Kesari3008
Copy link
Contributor

@Kesari3008 Kesari3008 commented Feb 2, 2026

COMPLETES #https://jira-eng-sjc12.cisco.com/jira/browse/CAI-7541

This pull request addresses

Needed to fetch device list for a user if needed to be cleared during reload or refreshes.

by making the following changes

Added new API: getDevices() under CallingClient module to fetch list of registered devices for a user. It helps deleting registrations if not required or handle duplicate registration cases more gracefully.

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

Using SDK Kitchen Sink App tested it.
Screenshot 2026-02-04 at 9 46 37 PM
Network Logs are attached in the Jira

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

I certified that

  • I have read and followed contributing guidelines
  • I discussed changes with code owners prior to submitting this pull request
  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the documentation accordingly

Make sure to have followed the contributing guidelines before submitting.

@Kesari3008 Kesari3008 requested a review from a team as a code owner February 2, 2026 12:59
@Kesari3008 Kesari3008 added the validated If the pull request is validated for automation. label Feb 2, 2026
return activeMobiusUrl;
}

if (this.primaryMobiusUris.length) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

@Kesari3008 why do do these check , from what i read we have to get active mobius from all of the mobius server then do a delete

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated the approach now

/**
* Fetches the list of devices for a given user from Mobius.
*/
public async getDevices(userId: string): Promise<DeviceType[]> {
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need this param?
why not this.webex.internal.device.userId ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated it

@rsarika
Copy link
Contributor

rsarika commented Feb 3, 2026

Now If we have to de-register user/developer need to run through this list(DeviceType[]) and call de-register.

Why not give this as a simple one more method deRegisterAllDevices() ? just thinking it out loud.

@Kesari3008
Copy link
Contributor Author

Now If we have to de-register user/developer need to run through this list(DeviceType[]) and call de-register.

Why not give this as a simple one more method deRegisterAllDevices() ? just thinking it out loud.

This is somehting we can consider for future. At the moment, multiple devices are not supported for one user. But registration is also somehting not implemented so allowing to deregiter for multiple devices would be something not required

Copy link
Collaborator

@arun3528 arun3528 left a comment

Choose a reason for hiding this comment

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

@Kesari3008 @rsarika i am ok with this approach of saving the the url in local storage and then cleaning it up .

but if its active why not reclaim it , why do we have to delete it

my idea of the whole cleanup was that the user does not know which mobius they are active on so they wil have to do feat all then see if there is a active one available then do a delete on that , when we do automation local storage is not shared across PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

validated If the pull request is validated for automation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants