diameter-db

The "Report-SM-Delivery-Status-Request" Diameter command code

The "Report-SM-Delivery-Status-Request" Diameter command uses the command code "8388649".

It has the REQ and PXY bits.

It is part of the 3GPP S6c, 3GPP SGd applications.

It is defined in the 3GPP TS 29.338: Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) specification.

It contains the following AVPs:

AVP code AVP name AVP type AVP requirement
263 Session-Id UTF8String Fixed (1)
301 DRMP Enumerated Optional (up to 1)
260 Vendor-Specific-Application-Id Grouped Optional (up to 1)
277 Auth-Session-State Enumerated Required (1)
264 Origin-Host DiameterIdentity Required (1)
296 Origin-Realm DiameterIdentity Required (1)
293 Destination-Host DiameterIdentity Optional (up to 1)
283 Destination-Realm DiameterIdentity Required (1)
628 Supported-Features Grouped Optional
3102 User-Identifier Grouped Required (1)
3324 SMSMI-Correlation-ID Grouped Optional (up to 1)
3300 SC-Address OctetString Required (1)
3316 SM-Delivery-Outcome Grouped Required (1)
3323 RDR-Flags Unsigned32 Optional (up to 1)
2401 Serving-Node Grouped Optional (up to 1)
2406 Additional-Serving-Node Grouped Optional (up to 1)
3344 SMSF-3GPP-Address Grouped Optional (up to 1)
3345 SMSF-Non-3GPP-Address Grouped Optional (up to 1)
284 Proxy-Info Grouped Optional
282 Route-Record DiameterIdentity Optional
Its CCF definition is the following:
< Report-SM-Delivery-Status-Request > ::= < Diameter-Header: 8388649, REQ, PXY > 
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
* [ Supported-Features ]
{ User-Identifier }
[ SMSMI-Correlation-ID ]
{ SC-Address }
{ SM-Delivery-Outcome }
[ RDR-Flags ]
[ Serving-Node ]
[ Additional-Serving-Node ]
[ SMSF-3GPP-Address ]
[ SMSF-Non-3GPP-Address ]
* [ Proxy-Info ]
* [ Route-Record ]





Update source Insertion date
3GPP 2026-04-26 07:12