Uplift to TS 26.512 V17.5.0 and Release 17 version of Open5GS #85
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…gssbi to the Open5GS binaries.
This was
linked to
issues
Jul 3, 2023
Closed
rjb1000
changed the title
rjb1000
approved these changes
Jul 3, 2023
rjb1000
changed the title
devbbc
approved these changes
Jul 3, 2023
rjb1000
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR pulls in some uplifts for:
Serverresponse header to match the change in specification.It also includes a modification to the 5GMS Application Function build system to automatically determine which OpenAPI model source codes have been generated, and include them in the compile, rather than the files having to be explicitly named in the build file.
Note also that a new configuration file variable,
msaf.m3Host, has been added so that the 5GMS AF can use an internal network to talk to the 5GMS AS via M3 rather than having to share the canonical hostname (which is used with M2). This allows the SSL/TLS certificate to be generated with the names of interfaces other than the one used by the internal M3 link. By default, if this new configuration variable is not given, the canonical hostname will be used for M3 as before.Closes: #60, #80, #81 and #82