Attention is currently required from: laforge, dexter.
1 comment:
File src/libosmo-mgcp/mgcp_protocol.c:
one option might be to turn the null endpoint into a real endpoint, one that just drops all data it […]
The main discussion to start with would be: Do we still want the null endpoint to be per-trunk? That would mean it ends up like "rtpbridge/null@mgw", instead of "null@mgw" we have now.
This means we would have a trunk pointer available in the handlers, which may be handy and maybe allow having less specific code paths.
On the other hand, that means the user has to figure out which trunk to use.
Regarding acceptance of any data: That would mean we need to still create a separate endpoint object internally in osmo-mgw. Since we don't really need that right now, I really preferred skipping it since it may take some effort, since special cases may need to be checked all along where "endp" objects are being used.
To view, visit change 33312. To unsubscribe, or for help writing mail filters, visit settings.