Attention is currently required from: laforge.
1 comment:
Patchset:
In my opinion, if the code calls a function that has *tcap* in the name, and the caller passes somet […]
IMHO that function is tcap related (and allows it to quickly find it in tcap related routines files), but as its name indicates it receives a SCCP message and decides if it is TCAP-related, and if that's the case, does stuff with it.
I think it's fine to keep it this way, specially since finding out if it's tcap requires a previous step of decoding SCCP, so better have it in the same path.
To view, visit change 42210. To unsubscribe, or for help writing mail filters, visit settings.