The function, core_trunks_gettrunkroutes, is suppose to return a hash which includes each route and the sequence number of that route as the value. This is currently only used to display the tool-tip on the trunk page of which routes are being used by a trunk.
The function is flawed in two ways:
- it has the indices reversed when returning the hash so the number of routes are not even always correct.
- it returns the priority of the call to dialout-trunk/enum/dundi from the old extensions table (which unfortunately is how routes are stored, sigh ... need to get this updated). As a result, the sequence number may not be right as the priority of the first call is not always 1.
This bug has been present since r3975 and thus effects all versions back to that era (which I believe is at least back to 2.3.
The effect is only visual, it does not effect functionality.
