You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The response header to an SM contexts collection request {apiRoot}/nsmf-pdusession/{apiVersion}/sm-contexts
should include a location field with the URI of the newly created resource, according to the structure: {apiRoot}/nsmf-pdusession/{apiVersion}/sm-contexts/{smContextRef}
Currently the location field is filled with something like: urn:uuid:7a51fda4-2d05-45d0-9988-1eacfa378310 (this is only the smContextRef)
The other free5GC components are aware of that and build the correct URI themselfs, but one can not use the free5GC SMF with other standard compliant components as they can not handle the format free5GCs SMF is providing in the location field.
See 3GPP TS 29.502 -> Resource: SM contexts collection -> Headers supported by the 201 Response Code on this resource
The text was updated successfully, but these errors were encountered:
The response header to an SM contexts collection request
{apiRoot}/nsmf-pdusession/{apiVersion}/sm-contexts
should include a location field with the URI of the newly created resource, according to the structure:
{apiRoot}/nsmf-pdusession/{apiVersion}/sm-contexts/{smContextRef}
Currently the location field is filled with something like:
urn:uuid:7a51fda4-2d05-45d0-9988-1eacfa378310
(this is only the smContextRef)The other free5GC components are aware of that and build the correct URI themselfs, but one can not use the free5GC SMF with other standard compliant components as they can not handle the format free5GCs SMF is providing in the location field.
See 3GPP TS 29.502 -> Resource: SM contexts collection -> Headers supported by the 201 Response Code on this resource
The text was updated successfully, but these errors were encountered: