cellular-infrastructure
/
osmo-mgw
mirror of https://gerrit.osmocom.org/osmo-mgw
10
0
Fork 0
Code Issues Releases Wiki Activity
osmo-mgw/src/libosmo-mgcp
History
Philipp Maier 01d24a3281 MGCP: Connection Identifiers are hex strings 
The MGCP spec in RFC3435 is quite clear: Connection Identifiers are
hexadecimal strings of up to 32 characters. We should not print and
parse them as integers on either client or server.

Change the internal uint32_t representation of connection identifiers
to a string representation in the client and also in the server.

Closes: OS#2649
Change-Id: I0531a1b670d00cec50078423a2868207135b2436
 		2017-12-01 11:58:23 +00:00
..
Makefile.am Tag/Release Version 1.2.0 2017-11-10 11:21:40 +09:00
g711common.h create libosmo-mgcp and osmo-mgw by copying legacy code 2017-10-05 01:40:43 +00:00
mgcp_conn.c MGCP: Connection Identifiers are hex strings 2017-12-01 11:58:23 +00:00
mgcp_ep.c Initially implement the new osmo-mgw and libosmo-mgcp 2017-10-05 01:40:43 +00:00
mgcp_msg.c MGCP: Connection Identifiers are hex strings 2017-12-01 11:58:23 +00:00
mgcp_network.c MGCP: Connection Identifiers are hex strings 2017-12-01 11:58:23 +00:00
mgcp_osmux.c MGCP: Connection Identifiers are hex strings 2017-12-01 11:58:23 +00:00
mgcp_protocol.c MGCP: Connection Identifiers are hex strings 2017-12-01 11:58:23 +00:00
mgcp_sdp.c MGCP: Connection Identifiers are hex strings 2017-12-01 11:58:23 +00:00
mgcp_stat.c Initially implement the new osmo-mgw and libosmo-mgcp 2017-10-05 01:40:43 +00:00
mgcp_vty.c MGCP: Connection Identifiers are hex strings 2017-12-01 11:58:23 +00:00