osmo-mgw[master]: MGCP endpoints: parse as decimal, not hex

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

Holger Freyther gerrit-no-reply at lists.osmocom.org
Tue Nov 14 09:02:15 UTC 2017


Patch Set 1:

You notice that this has "always" been parsed as base 16? Sadly the MGCP RFC doesn't say what an endpoint number should be. In the RFC it is a "NameString" (some chars except /, $, *, 0-9 A-z). Sadly the openbsc tests only check for single digit calls.

I looked at some old traces and see 2E, B as endpoint names. From skimming the RFC we could use 1,2,..9,10,..32, but for compat with existing equipment should continue to use hex?


And a general comment:

For On-Waves I used things like round-robin allocation and placed N+5 calls to see how it would behave.

-- 
To view, visit https://gerrit.osmocom.org/4780
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ic18608ff23303c1564548a86d5f6bfa539fe555e
Gerrit-PatchSet: 1
Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Holger Freyther <holger at freyther.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-HasComments: No



More information about the gerrit-log mailing list