Actions
Bug #2633
closed'N@mgw' number translation uses base-16 which will break for decimal endpoint IDs near the number of reserved endpoints
Start date:
11/10/2017
Due date:
% Done:
100%
Spec Reference:
Description
osmo-mgw parses the endpoint IDs like
gw = strtoul(mgcp, &endptr, 16);
i.e. as base-16 numbers. But OsmoMSC and OsmoBSC pass in decimal endpoint numbers. The consequence is, for example:
- I configure 32 endpoints in osmo-mgw
- I tell OsmoBSC to use endpoint range 1-32
- At some point OsmoBSC may pass in, say, "30@mgw"
- "30" is parsed base-16 and ends up being endpoint index 48, instead of 32.
- OsmoMGW sees that 48 > number_endpoints and barfs.
Related issues
Updated by neels over 6 years ago
- Related to Feature #2631: allow arbitrary endpoint names, be more dynamic in allocation and iteration added
Updated by neels over 6 years ago
I'll change this to base-10, which is a single-character change, until #2631 might be implemented one day.
Updated by neels over 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
Updated by neels over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
merged
Actions