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

[dispatcher] DB versus MI correlation #140

Open
bogdan-iancu opened this issue Jan 13, 2022 · 0 comments
Open

[dispatcher] DB versus MI correlation #140

bogdan-iancu opened this issue Jan 13, 2022 · 0 comments
Labels

Comments

@bogdan-iancu
Copy link
Member

The dispatcher tool correlates the DB records of the Destinations with the MI records (of the same Destinations) using only the SIP URI. This is broken as the same SIP URI may exist in different dispatching set, leading the wrong matching, and wrong status displaying.

To make this even worst, the dispatcher modules (in OpenSIPS) does not provide any unique key for the Destinations, so it is rather impossible to precisely match DB versus MI and even more, to properly do ds_set_state on the right Destination.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant