You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: