The "SMS-Information" AVP

The "SMS-Information" Diameter AVP, which is of type Grouped, is defined by 3GPP (vendor ID 10415) and uses the AVP code "2000".

It has the MANDATORY flag, the MAY-ENCRYPT flag.

It is part of the Service-Information grouped AVP.

It is a grouped AVP, which can hold the following nested AVPs:

AVP code	AVP name	AVP type	AVP requirement
2016	SMS-Node	Enumerated
2018	Client-Address	IPAddress
2008	Originator-SCCP-Address	IPAddress
2010	Recipient-SCCP-Address	IPAddress
2017	SMSC-Address	IPAddress
2001	Data-Coding-Scheme	Integer32
2002	Destination-Interface	Grouped
2012	SM-Discharge-Time	Time
2007	SM-Message-Type	Enumerated
2009	Originator-Interface	Grouped
2013	SM-Protocol-ID	OctetString
2011	Reply-Path-Requested	Enumerated
2014	SM-Status	OctetString
2015	SM-User-Data-Header	OctetString
2019	Number-of-Messages-Sent	Unsigned32
2026	Recipient-Info	Grouped
3408	SM-Sequence-Number	Unsigned32	Optional (up to 1)
2027	Originator-Received-Address	Grouped	Optional (up to 1)
2029	SM-Service-Type	Enumerated	Optional (up to 1)
3409	SMS-Result	Unsigned32	Optional (up to 1)
3407	SM-Device-Trigger-Indicator	Enumerated	Optional (up to 1)
3405	SM-Device-Trigger-Information	Grouped	Optional (up to 1)

Its AVP-header format definition is the following:

< SMS-Information > ::= < AVP-Header: 2000, 10415 > 
* [ SMS-Node ]
* [ Client-Address ]
* [ Originator-SCCP-Address ]
* [ Recipient-SCCP-Address ]
* [ SMSC-Address ]
* [ Data-Coding-Scheme ]
* [ Destination-Interface ]
* [ SM-Discharge-Time ]
* [ SM-Message-Type ]
* [ Originator-Interface ]
* [ SM-Protocol-ID ]
* [ Reply-Path-Requested ]
* [ SM-Status ]
* [ SM-User-Data-Header ]
* [ Number-of-Messages-Sent ]
* [ Recipient-Info ]
[ SM-Sequence-Number ]
[ Originator-Received-Address ]
[ SM-Service-Type ]
[ SMS-Result ]
[ SM-Device-Trigger-Indicator ]
[ SM-Device-Trigger-Information ]

Update source	Insertion date
Wireshark	2026-04-26 07:13
Diafuzzer	2026-04-26 07:14