Actions
Bug #4232
closedOsmoSTP re-orders M3UA fields of routed messages
Start date:
10/18/2019
Due date:
% Done:
0%
Spec Reference:
Description
When a M3UA DATA message with correct order of information elements (routing context, protocol data) is routed by OsmoSTP, the output message is re-ordered: (protocol data, routing context).
The reason for this is that the new routing context is added "after the fact" during the m3ua_tx_xua_as() function.... and it's added at the end of the list of IEs as xua_msg_add_u32() is using xua_msg_add_data() which in turn uses llist_add_tail().
Actions