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

Can't get size on shared dialog profiles #94

Open
Alconqro opened this issue Jun 30, 2021 · 2 comments
Open

Can't get size on shared dialog profiles #94

Alconqro opened this issue Jun 30, 2021 · 2 comments
Assignees

Comments

@Alconqro
Copy link

When the dialog profiles are shared by clusterer module or a CacheDB backend the name of the profiles should include the /b or /s Flags but the dialog interface only use the name of the profile without the flags, this cause that we just get the "!!! Array" message when we request the size of the shared profiles (with or without values), but if we use the correct name with the /b or /s on the value of the select option it works fine and we get the correct number of dialogs and the list of dialogs on the profile.

This bug is because the response from the list_all_profiles mi command return the name without the flags.

Alconqro added a commit to Alconqro/opensips-cp that referenced this issue Jun 30, 2021
…s using a module config value to identify the correct name of the profile.
@bogdan-iancu bogdan-iancu self-assigned this Jul 1, 2021
@bogdan-iancu
Copy link
Member

That's a good catch @Alconqro . But I think the issue is in OpenSIPS and not in CP. As OpenSIPS is fetching the list of existing profiles via the list_all_profiles MI cmd - and this one should return the correct profile names with the \b or \s - basically these suffixes are part of the profile name (you use use the names with the flags everywhere in the opensips cfg - and from cfg perspective caller and caller\b are different profiles)

@Alconqro
Copy link
Author

Alconqro commented Jul 1, 2021

Right ! In the mean time the dialog module is updated with a permanent fix the CP fix do the work for me or anyone else that could have the same problem.
Thanks for addressing this issue.

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

No branches or pull requests

2 participants