@@ -2,7 +2,7 @@

 Source: open5gs

 Binary: open5gs-common, open5gs-mme, open5gs-sgwc, open5gs-smf, open5gs-amf, open5gs-sgwu, open5gs-upf, open5gs-hss, open5gs-pcrf, open5gs-nrf, open5gs-scp, open5gs-sepp, open5gs-ausf, open5gs-udm, open5gs-pcf, open5gs-nssf, open5gs-bsf, open5gs-udr, open5gs, open5gs-dbg

 Architecture: any

-Version: 2.7.3.4642.1d46.202503242026

+Version: 2.7.3.4643.7040.202503252026

 Maintainer: Harald Welte <laforge@gnumonks.org>

 Uploaders: Sukchan Lee <acetcom@gmail.com>

 Homepage: https://open5gs.org

@@ -32,8 +32,8 @@

  open5gs-udr deb net optional arch=any

  open5gs-upf deb net optional arch=any

 Checksums-Sha1:

- caff05e6eb25993eb01799f7f81c09ed42e55db4 14530324 open5gs_2.7.3.4642.1d46.202503242026.tar.xz

+ 44a58dbcbab5b40cc6eb082977d0b088c06a7e0c 14530092 open5gs_2.7.3.4643.7040.202503252026.tar.xz

 Checksums-Sha256:

- c05aa555d3dd5681d29df70998f6245cd1757f149c0a87a58230eddd1143c527 14530324 open5gs_2.7.3.4642.1d46.202503242026.tar.xz

+ 1a419a618b9a6fd321ee45a4502cecc862d0916ac9d8abc269dd1291c30acb60 14530092 open5gs_2.7.3.4643.7040.202503252026.tar.xz

 Files:

- 07b748513d67919375f2813605076fdd 14530324 open5gs_2.7.3.4642.1d46.202503242026.tar.xz

+ 5297b7f34fd147a15e0bf6819a259733 14530092 open5gs_2.7.3.4643.7040.202503252026.tar.xz

​

@@ -1 +1 @@

-2.7.3.4642-1d46.202503242026

+2.7.3.4643-7040.202503252026

​

@@ -1,8 +1,8 @@

-open5gs (2.7.3.4642.1d46.202503242026) unstable; urgency=medium

+open5gs (2.7.3.4643.7040.202503252026) unstable; urgency=medium

   * Automatically generated changelog entry for building the Osmocom nightly feed

- -- Osmocom OBS scripts <info@osmocom.org>  Mon, 24 Mar 2025 20:27:55 +0000

+ -- Osmocom OBS scripts <info@osmocom.org>  Tue, 25 Mar 2025 20:27:55 +0000

 open5gs (2.7.3) unstable; urgency=medium

​

@@ -411,6 +411,8 @@

     "N5g-ddnmf_Discovery_MonitorUpdateResult"

 #define OGS_SBI_CALLBACK_N5G_DDNMF_DISCOVERY_MATCH_INFORMATION \

     "N5g-ddnmf_Discovery_MatchInformation"

+#define OGS_SBI_CALLBACK_NAMF_COMMUNICATION_ONN1N2TRANSFERFAILURE \

+    "Namf_Communication_onN1N2TransferFailure"

 typedef struct ogs_sbi_header_s {

     char *method;

​

@@ -1458,9 +1458,6 @@

     message.SubscriptionData = SubscriptionData;

-    message.http.custom.callback =

-        (char *)OGS_SBI_CALLBACK_NNRF_NFMANAGEMENT_NF_STATUS_NOTIFY;

-

     request = ogs_sbi_build_request(&message);

     ogs_expect(request);

@@ -1549,9 +1546,6 @@

     message.h.method = (char *)OGS_SBI_HTTP_METHOD_DELETE;

     message.h.uri = subscription_data->resource_uri;

-    message.http.custom.callback =

-        (char *)OGS_SBI_CALLBACK_NNRF_NFMANAGEMENT_NF_STATUS_NOTIFY;

-

     request = ogs_sbi_build_request(&message);

     ogs_expect(request);

​

@@ -224,6 +224,15 @@

     message.http.accept = (char *)(OGS_SBI_CONTENT_JSON_TYPE ","

         OGS_SBI_CONTENT_NGAP_TYPE "," OGS_SBI_CONTENT_PROBLEM_TYPE);

+/*

+ * Callback Header Configuration

+ *

+ * The 3gpp-Sbi-Callback HTTP header (per 3GPP TS 29.500 v17.9.0) indicates that

+ * a message is an asynchronous notification or callback. This header should be

+ * included only in HTTP POST requests that are callbacks (e.g., event or

+ * notification messages) and must not be added to regular service requests,

+ * such as registration (HTTP PUT) or subscription requests.

+ */

     message.http.custom.callback =

         (char *)OGS_SBI_CALLBACK_NSMF_PDUSESSION_STATUS_NOTIFY;

@@ -529,6 +538,18 @@

     message.N1N2MsgTxfrFailureNotification = &N1N2MsgTxfrFailureNotification;

+/*

+ * Callback Header Configuration

+ *

+ * The 3gpp-Sbi-Callback HTTP header (per 3GPP TS 29.500 v17.9.0) indicates that

+ * a message is an asynchronous notification or callback. This header should be

+ * included only in HTTP POST requests that are callbacks (e.g., event or

+ * notification messages) and must not be added to regular service requests,

+ * such as registration (HTTP PUT) or subscription requests.

+ */

+    message.http.custom.callback =

+        (char *)OGS_SBI_CALLBACK_NAMF_COMMUNICATION_ONN1N2TRANSFERFAILURE;

+

     request = ogs_sbi_build_request(&message);

     ogs_expect(request);

​

@@ -85,9 +85,6 @@

     message.Amf3GppAccessRegistration = &Amf3GppAccessRegistration;

-    message.http.custom.callback =

-        (char *)OGS_SBI_CALLBACK_NUDM_UECM_DEREGISTRATION_NOTIFICATION;

-

     request = ogs_sbi_build_request(&message);

     ogs_expect(request);

@@ -243,9 +240,6 @@

     message.SDMSubscription = &SDMSubscription;

-    message.http.custom.callback =

-        (char *)OGS_SBI_CALLBACK_NUDM_SDM_NOTIFICATION;

-

     request = ogs_sbi_build_request(&message);

     ogs_expect(request);

​

@@ -81,6 +81,17 @@

             goto end;

         }

     }

+/*

+ * Callback Header Configuration

+ *

+ * The 3gpp-Sbi-Callback HTTP header (per 3GPP TS 29.500 v17.9.0) indicates that

+ * a message is an asynchronous notification or callback. This header should be

+ * included only in HTTP POST requests that are callbacks (e.g., event or

+ * notification messages) and must not be added to regular service requests,

+ * such as registration (HTTP PUT) or subscription requests.

+ */

+    message.http.custom.callback =

+        (char *)OGS_SBI_CALLBACK_NNRF_NFMANAGEMENT_NF_STATUS_NOTIFY;

     message.NotificationData = NotificationData;

​

@@ -236,9 +236,6 @@

     message.SDMSubscription = &SDMSubscription;

-    message.http.custom.callback =

-        (char *)OGS_SBI_CALLBACK_NUDM_SDM_NOTIFICATION;

-

     request = ogs_sbi_build_request(&message);

     ogs_expect(request);

​