Pau Espin 867b13025b DIAMETER: Split Gy and Gx messages to their own TS files ... Those interfaces reuse messages from other Diameter RFCs, but changing the contents of the messages, eg some Mandatory fields like Service-Context-Id which are mandatory in RFC5006, doesn't even appear in Gx CCR in TS 29.212. Keeping them well separated helps in avoiding confusion on users fo the messages. Change-Id: Ibe0d5f263813d5083e020c942283f214983162b4		2024-01-24 16:14:30 +01:00
..
PGW_Tests.cfg	pgw: Initial testsuite for a PGW (Packet Gateway in the EPC)	2020-04-21 22:57:31 +02:00
PGW_Tests.default	pgw: Initial testsuite for a PGW (Packet Gateway in the EPC)	2020-04-21 22:57:31 +02:00
PGW_Tests.ttcn	DIAMETER: Split Gy and Gx messages to their own TS files	2024-01-24 16:14:30 +01:00
expected-results.xml	update various expected-results.xml	2022-08-12 02:31:23 +00:00
gen_links.sh	DIAMETER: Split Gy and Gx messages to their own TS files	2024-01-24 16:14:30 +01:00
regen_makefile.sh	pgw: Improve checks around Gy messages	2022-05-19 14:13:10 +02:00