TS 102 232-5 v3.10.1 (2019-04-04) agreed at LI#50 (Dubai, 2019-02-05)

cbcd8db3 · canterburym · 4472aa2f · cbcd8db3 · cbcd8db3
Commit cbcd8db3 authored Jun 15, 2020 by canterburym
Hide whitespace changes
Inline Side-by-side

Showing with 336 additions and 160 deletions

102232-5/IPMultimediaPDU.asn 102232-5/IPMultimediaPDU.asn +168 -160

102232-5/portal/IPMultimediaPDU,ver11.txt 102232-5/portal/IPMultimediaPDU,ver11.txt +168 -0

No files found.
--- a/102232-5/IPMultimediaPDU.asn
+++ b/102232-5/IPMultimediaPDU.asn
-IPMultimediaPDU 
+-- ====================================
-{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version10(10)}
+-- Description of the IP Multimedia PDU
+-- ====================================
-DEFINITIONS IMPLICIT TAGS ::=
-BEGIN
+IPMultimediaPDU 
-IMPORTS
+{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version11(11)}
-	-- from TS 102 232-1 [2]
-    IPAddress,
+DEFINITIONS IMPLICIT TAGS ::=
-	Location
+BEGIN
-		FROM LI-PS-PDU
-		{itu-u(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version26(26)};
+IMPORTS
+	-- from ETSI TS 102 232-1 [2]
+    IPAddress,
+	Location
-- ============================
+		FROM LI-PS-PDU
-- Object Identifier Definition
+		{itu-u(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version26(26)};
-- ============================
-iPMMIRIObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version10(10) iRI(1)}
-iPMMCCObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version10(10) cC(2)}
+-- ============================
-	-- both definitions relative to: 
+-- Object Identifier Definition
-	-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2)}
+-- ============================
-- =====================================
+iPMMIRIObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version11(11) iRI(1)}
-- IP Multimedia Communications Contents
+iPMMCCObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version11(11) cC(2)}
-- =====================================
+	-- both definitions relative to: 
+	-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2)}
-IPMMCC ::= SEQUENCE
-{
+-- =====================================
-	iPMMCCObjId					[0] RELATIVE-OID,
+-- IP Multimedia Communications Contents
-	mMCCContents				[1] OCTET STRING,
+-- =====================================
-		-- Copy of the multimediastream, i.e. all related RTP/RTCP, UDPTL or MSRP packets
-		-- Each IPMMCC shall contain one intercepted packet
+IPMMCC ::= SEQUENCE
-		-- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter
+{
-		-- mMCCContents was called rTPCCContents in earlier versions until v2.3.2.
+	iPMMCCObjId					[0] RELATIVE-OID,
-	...,
+	mMCCContents				[1] OCTET STRING,
-	frameType					[2] FrameType OPTIONAL,
+		-- Copy of the multimediastream, i.e. all related RTP/RTCP, UDPTL or MSRP packets
-		-- The availability of header information shall be signalled with the frameType parameter
+		-- Each IPMMCC shall contain one intercepted packet
-		-- The module is defined as OPTIONAL because of backwards compatibility reasons
+		-- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter
-		-- For new implementations the module is MANDATORY to be used as defined in clause 5.5
+		-- mMCCContents was called rTPCCContents in earlier versions until v2.3.2.
-	streamIdentifier			[3] OCTET STRING OPTIONAL,
+	...,
-		-- Used to identify the media stream within the current CIN, typically in case of 
+	frameType					[2] FrameType OPTIONAL,
-		-- multiple media streams communications
+		-- The availability of header information shall be signalled with the frameType parameter
-		-- May be used to correlate each media stream with the relevant SDP media description of IRI
+		-- The module is defined as OPTIONAL because of backwards compatibility reasons
-		-- May contain c= and m= lines extracts for instance
+		-- For new implementations the module is MANDATORY to be used as defined in clause 5.5
-	mMCCprotocol				[4] MMCCprotocol OPTIONAL
+	streamIdentifier			[3] OCTET STRING OPTIONAL,
-		-- Used to identify the protocol of packets sent in MMCCContent (RTP, UDPTL, MSRP, etc.)
+		-- Used to identify the media stream within the current CIN, typically in case of 
-		-- Absence means mMCCContents contains RTP/RTCP packets
+		-- multiple media streams communications
-}
+		-- May be used to correlate each media stream with the relevant SDP media description of IRI
+		-- May contain c= and m= lines extracts for instance
-FrameType ::= ENUMERATED
+	mMCCprotocol				[4] MMCCprotocol OPTIONAL
-{
+		-- Used to identify the protocol of packets sent in MMCCContent (RTP, UDPTL, MSRP, etc.)
-	ipFrame(0),
+		-- Absence means mMCCContents contains RTP/RTCP packets
-		-- All headers are present
+}
-	udpFrame(1),
-		-- IP header is missing
+FrameType ::= ENUMERATED
-	rtpFrame(2),
+{
-		-- UDP and IP headers are missing
+	ipFrame(0),
-	audioFrame(3),
+		-- All headers are present
-		-- All headers are missing
+	udpFrame(1),
-	...,
+		-- IP header is missing
-	tcpFrame(4),
+	rtpFrame(2),
-		-- IP header is missing
+		-- UDP and IP headers are missing
-	artificialRtpFrame(5),
+	audioFrame(3),
-		-- UDP and IP headers are missing, artificial RTP frame has been added
+		-- All headers are missing
-	udptlFrame(6)
+	...,
-		-- UDP and IP headers are missing
+	tcpFrame(4),
-}
+		-- IP header is missing
+	artificialRtpFrame(5),
-MMCCprotocol ::= ENUMERATED
+		-- UDP and IP headers are missing, artificial RTP frame has been added
-{
+	udptlFrame(6),
-	rTP(0),
+		-- UDP and IP headers are missing
-		-- mMCCContents parameter contains RTP/RTCP packets
+	msrpFrame(7)
-	mSRP(1),
+		-- TCP and IP headers are missing
-		-- mMCCContents parameter contains MSRP packets
-	...,
+}
-	uDPTL(2)
-		-- mMCCContents parameter contains UDPTL packets
+MMCCprotocol ::= ENUMERATED
-}
+{
+	rTP(0),
-- ========================================================
+		-- mMCCContents parameter contains RTP/RTCP packets
-- Intercept-related information for IP Multimedia sessions
+	mSRP(1),
-- ========================================================
+		-- mMCCContents parameter contains MSRP packets
+	...,
-IPMMIRI ::= SEQUENCE
+	uDPTL(2)
-{
+		-- mMCCContents parameter contains UDPTL packets
-	iPMMIRIObjId				[0] RELATIVE-OID,
+}
-	iPMMIRIContents				[1] IPIRIContents,
-	...,
+-- ========================================================
-	targetLocation				[2] Location OPTIONAL,
+-- Intercept-related information for IP Multimedia sessions
-		-- This common parameter is defined in TS 102 232-1 [2], the use of this parameter is described in clause 5.2.3
+-- ========================================================
-	additionalSignalling		[3] SEQUENCE OF AdditionalSignalling OPTIONAL
-		-- The use of this parameter is defined in clause 5.2.5
+IPMMIRI ::= SEQUENCE
-}
+{
+	iPMMIRIObjId				[0] RELATIVE-OID,
-IPIRIContents ::= CHOICE
+	iPMMIRIContents				[1] IPIRIContents,
-{
+	...,
-	originalIPMMMessage			[0] OCTET STRING,
+	targetLocation				[2] Location OPTIONAL,
-		-- Copy of the IP MM signalling packet including the original IP and UDP/TCP headers
+		-- This common parameter is defined in TS 102 232-1 [2], the use of this parameter is described in clause 5.2.3
-	sIPMessage					[1] SIPMessage,
+	additionalSignalling		[3] SEQUENCE OF AdditionalSignalling OPTIONAL
-		-- Copy of the SIP content and the source and destination IP address
+		-- The use of this parameter is defined in clause 5.2.5
-	h323Message					[2] H323Message,
+}
-		-- Copy of the H.323 content and the source and destination IP address
-	...,
+IPIRIContents ::= CHOICE
-	nationalIPMMIRIParameters	[3] NationalIPMMIRIParameters,
+{
-		-- This parameter is used according to national regulations
+	originalIPMMMessage			[0] OCTET STRING,
-		-- This parameter shall be delivered as an IRI-Report-record	
+		-- Copy of the IP MM signalling packet including the original IP and UDP/TCP headers
-	xCAPMessage					[4] OCTET STRING		
+	sIPMessage					[1] SIPMessage,
-		-- Copy of the XCAP message including all HTTP headers and contents
+		-- Copy of the SIP content and the source and destination IP address
-}
+	h323Message					[2] H323Message,
+		-- Copy of the H.323 content and the source and destination IP address
-SIPMessage ::= SEQUENCE
+	...,
-{
+	nationalIPMMIRIParameters	[3] NationalIPMMIRIParameters,
-	iPSourceAddress				[0] IPAddress,
+		-- This parameter is used according to national regulations
-	iPDestinationAddress		[1] IPAddress,
+		-- This parameter shall be delivered as an IRI-Report-record	
-	sIPContent					[2] OCTET STRING,
+	xCAPMessage					[4] OCTET STRING		
-	...
+		-- Copy of the XCAP message including all HTTP headers and contents
 }
-H323Message ::= SEQUENCE
+SIPMessage ::= SEQUENCE
 {
 	iPSourceAddress				[0] IPAddress,
 	iPDestinationAddress		[1] IPAddress,
-	h323Content					[2] H323MessageContent,
+	sIPContent					[2] OCTET STRING,
 	...
 }
-H323MessageContent ::= CHOICE
+H323Message ::= SEQUENCE
 {
-	h225CSMessageContent		[0] OCTET STRING,
+	iPSourceAddress				[0] IPAddress,
-	h225RASMessageContent		[1] OCTET STRING,
+	iPDestinationAddress		[1] IPAddress,
-	h245MessageContent			[2] OCTET STRING,
+	h323Content					[2] H323MessageContent,
-	genericMessageContent		[3] OCTET STRING,
+	...
-	...
+}
-}
+H323MessageContent ::= CHOICE
-NationalIPMMIRIParameters ::= SEQUENCE
+{
-{
+	h225CSMessageContent		[0] OCTET STRING,
-	countryCode					[1] PrintableString (SIZE (2)),
+	h225RASMessageContent		[1] OCTET STRING,
-		-- Country Code according to ISO 3166-1 [16],
+	h245MessageContent			[2] OCTET STRING,
-		-- the country to which the parameters inserted after the extension marker apply.
+	genericMessageContent		[3] OCTET STRING,
 	...
-	-- In case a given country wants to use additional national parameters according to its law,
+}
-	-- these national parameters should be defined using the ASN.1 syntax and added after the
-	-- extension marker (...).
+NationalIPMMIRIParameters ::= SEQUENCE
-	-- It is recommended that "version parameter" and "vendor identification parameter" are
+{
-	-- included in the national parameters definition. Vendor identifications can be
+	countryCode					[1] PrintableString (SIZE (2)),
-	-- retrieved from the IANA web site (see Annex E Bibliography). Besides, it is recommended 
+		-- Country Code according to ISO 3166-1 [16],
-	-- to avoid using tags from 240 to 255 in a formal type definition.
+		-- the country to which the parameters inserted after the extension marker apply.
-}
+	...
+	-- In case a given country wants to use additional national parameters according to its law,
-AdditionalSignalling ::= CHOICE
+	-- these national parameters should be defined using the ASN.1 syntax and added after the
-{
+	-- extension marker (...).
-	sipHeaderLine				[0] OCTET STRING,
+	-- It is recommended that "version parameter" and "vendor identification parameter" are
-		-- A SIP header line, eg: "Contact: tel:+123456789".
+	-- included in the national parameters definition. Vendor identifications can be
-	...
+	-- retrieved from the IANA web site (see Annex E Bibliography). Besides, it is recommended 
-}
+	-- to avoid using tags from 240 to 255 in a formal type definition.
+}
-END -- end of IP Multimedia PDU
\ No newline at end of file
+AdditionalSignalling ::= CHOICE
+{
+	sipHeaderLine				[0] OCTET STRING,
+		-- A SIP header line, eg: "Contact: tel:+123456789".
+	...
+}
+END -- end of IPMultimediaPDU

--- a/102232-5/portal/IPMultimediaPDU,ver10.txt
+++ b/102232-5/portal/IPMultimediaPDU,ver10.txt
-IPMultimediaPDU 
+-- ====================================
-{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version10(10)}
+-- Description of the IP Multimedia PDU
+-- ====================================
-DEFINITIONS IMPLICIT TAGS ::=
-BEGIN
+IPMultimediaPDU 
-IMPORTS
+{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version11(11)}
-	-- from TS 102 232-1 [2]
-    IPAddress,
+DEFINITIONS IMPLICIT TAGS ::=
-	Location
+BEGIN
-		FROM LI-PS-PDU
-		{itu-u(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version26(26)};
+IMPORTS
+	-- from ETSI TS 102 232-1 [2]
+    IPAddress,
+	Location
-- ============================
+		FROM LI-PS-PDU
-- Object Identifier Definition
+		{itu-u(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version26(26)};
-- ============================
-iPMMIRIObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version10(10) iRI(1)}
-iPMMCCObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version10(10) cC(2)}
+-- ============================
-	-- both definitions relative to: 
+-- Object Identifier Definition
-	-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2)}
+-- ============================
-- =====================================
+iPMMIRIObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version11(11) iRI(1)}
-- IP Multimedia Communications Contents
+iPMMCCObjId RELATIVE-OID			::= {li-ps(5) iPMultimedia(5) version11(11) cC(2)}
-- =====================================
+	-- both definitions relative to: 
+	-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2)}
-IPMMCC ::= SEQUENCE
-{
+-- =====================================
-	iPMMCCObjId					[0] RELATIVE-OID,
+-- IP Multimedia Communications Contents
-	mMCCContents				[1] OCTET STRING,
+-- =====================================
-		-- Copy of the multimediastream, i.e. all related RTP/RTCP, UDPTL or MSRP packets
-		-- Each IPMMCC shall contain one intercepted packet
+IPMMCC ::= SEQUENCE
-		-- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter
+{
-		-- mMCCContents was called rTPCCContents in earlier versions until v2.3.2.
+	iPMMCCObjId					[0] RELATIVE-OID,
-	...,
+	mMCCContents				[1] OCTET STRING,
-	frameType					[2] FrameType OPTIONAL,
+		-- Copy of the multimediastream, i.e. all related RTP/RTCP, UDPTL or MSRP packets
-		-- The availability of header information shall be signalled with the frameType parameter
+		-- Each IPMMCC shall contain one intercepted packet
-		-- The module is defined as OPTIONAL because of backwards compatibility reasons
+		-- Protocol of the multimedia packets is indicated by means of mMCCprotocol parameter
-		-- For new implementations the module is MANDATORY to be used as defined in clause 5.5
+		-- mMCCContents was called rTPCCContents in earlier versions until v2.3.2.
-	streamIdentifier			[3] OCTET STRING OPTIONAL,
+	...,
-		-- Used to identify the media stream within the current CIN, typically in case of 
+	frameType					[2] FrameType OPTIONAL,
-		-- multiple media streams communications
+		-- The availability of header information shall be signalled with the frameType parameter
-		-- May be used to correlate each media stream with the relevant SDP media description of IRI
+		-- The module is defined as OPTIONAL because of backwards compatibility reasons
-		-- May contain c= and m= lines extracts for instance
+		-- For new implementations the module is MANDATORY to be used as defined in clause 5.5
-	mMCCprotocol				[4] MMCCprotocol OPTIONAL
+	streamIdentifier			[3] OCTET STRING OPTIONAL,
-		-- Used to identify the protocol of packets sent in MMCCContent (RTP, UDPTL, MSRP, etc.)
+		-- Used to identify the media stream within the current CIN, typically in case of 
-		-- Absence means mMCCContents contains RTP/RTCP packets
+		-- multiple media streams communications
-}
+		-- May be used to correlate each media stream with the relevant SDP media description of IRI
+		-- May contain c= and m= lines extracts for instance
-FrameType ::= ENUMERATED
+	mMCCprotocol				[4] MMCCprotocol OPTIONAL
-{
+		-- Used to identify the protocol of packets sent in MMCCContent (RTP, UDPTL, MSRP, etc.)
-	ipFrame(0),
+		-- Absence means mMCCContents contains RTP/RTCP packets
-		-- All headers are present
+}
-	udpFrame(1),
-		-- IP header is missing
+FrameType ::= ENUMERATED
-	rtpFrame(2),
+{
-		-- UDP and IP headers are missing
+	ipFrame(0),
-	audioFrame(3),
+		-- All headers are present
-		-- All headers are missing
+	udpFrame(1),
-	...,
+		-- IP header is missing
-	tcpFrame(4),
+	rtpFrame(2),
-		-- IP header is missing
+		-- UDP and IP headers are missing
-	artificialRtpFrame(5),
+	audioFrame(3),
-		-- UDP and IP headers are missing, artificial RTP frame has been added
+		-- All headers are missing
-	udptlFrame(6)
+	...,
-		-- UDP and IP headers are missing
+	tcpFrame(4),
-}
+		-- IP header is missing
+	artificialRtpFrame(5),
-MMCCprotocol ::= ENUMERATED
+		-- UDP and IP headers are missing, artificial RTP frame has been added
-{
+	udptlFrame(6),
-	rTP(0),
+		-- UDP and IP headers are missing
-		-- mMCCContents parameter contains RTP/RTCP packets
+	msrpFrame(7)
-	mSRP(1),
+		-- TCP and IP headers are missing
-		-- mMCCContents parameter contains MSRP packets
-	...,
+}
-	uDPTL(2)
-		-- mMCCContents parameter contains UDPTL packets
+MMCCprotocol ::= ENUMERATED
-}
+{
+	rTP(0),
-- ========================================================
+		-- mMCCContents parameter contains RTP/RTCP packets
-- Intercept-related information for IP Multimedia sessions
+	mSRP(1),
-- ========================================================
+		-- mMCCContents parameter contains MSRP packets
+	...,
-IPMMIRI ::= SEQUENCE
+	uDPTL(2)
-{
+		-- mMCCContents parameter contains UDPTL packets
-	iPMMIRIObjId				[0] RELATIVE-OID,
+}
-	iPMMIRIContents				[1] IPIRIContents,
-	...,
+-- ========================================================
-	targetLocation				[2] Location OPTIONAL,
+-- Intercept-related information for IP Multimedia sessions
-		-- This common parameter is defined in TS 102 232-1 [2], the use of this parameter is described in clause 5.2.3
+-- ========================================================
-	additionalSignalling		[3] SEQUENCE OF AdditionalSignalling OPTIONAL
-		-- The use of this parameter is defined in clause 5.2.5
+IPMMIRI ::= SEQUENCE
-}
+{
+	iPMMIRIObjId				[0] RELATIVE-OID,
-IPIRIContents ::= CHOICE
+	iPMMIRIContents				[1] IPIRIContents,
-{
+	...,
-	originalIPMMMessage			[0] OCTET STRING,
+	targetLocation				[2] Location OPTIONAL,
-		-- Copy of the IP MM signalling packet including the original IP and UDP/TCP headers
+		-- This common parameter is defined in TS 102 232-1 [2], the use of this parameter is described in clause 5.2.3
-	sIPMessage					[1] SIPMessage,
+	additionalSignalling		[3] SEQUENCE OF AdditionalSignalling OPTIONAL
-		-- Copy of the SIP content and the source and destination IP address
+		-- The use of this parameter is defined in clause 5.2.5
-	h323Message					[2] H323Message,
+}
-		-- Copy of the H.323 content and the source and destination IP address
-	...,
+IPIRIContents ::= CHOICE
-	nationalIPMMIRIParameters	[3] NationalIPMMIRIParameters,
+{
-		-- This parameter is used according to national regulations
+	originalIPMMMessage			[0] OCTET STRING,
-		-- This parameter shall be delivered as an IRI-Report-record	
+		-- Copy of the IP MM signalling packet including the original IP and UDP/TCP headers
-	xCAPMessage					[4] OCTET STRING		
+	sIPMessage					[1] SIPMessage,
-		-- Copy of the XCAP message including all HTTP headers and contents
+		-- Copy of the SIP content and the source and destination IP address
-}
+	h323Message					[2] H323Message,
+		-- Copy of the H.323 content and the source and destination IP address
-SIPMessage ::= SEQUENCE
+	...,
-{
+	nationalIPMMIRIParameters	[3] NationalIPMMIRIParameters,
-	iPSourceAddress				[0] IPAddress,
+		-- This parameter is used according to national regulations
-	iPDestinationAddress		[1] IPAddress,
+		-- This parameter shall be delivered as an IRI-Report-record	
-	sIPContent					[2] OCTET STRING,
+	xCAPMessage					[4] OCTET STRING		
-	...
+		-- Copy of the XCAP message including all HTTP headers and contents
 }
-H323Message ::= SEQUENCE
+SIPMessage ::= SEQUENCE
 {
 	iPSourceAddress				[0] IPAddress,
 	iPDestinationAddress		[1] IPAddress,
-	h323Content					[2] H323MessageContent,
+	sIPContent					[2] OCTET STRING,
 	...
 }
-H323MessageContent ::= CHOICE
+H323Message ::= SEQUENCE
 {
-	h225CSMessageContent		[0] OCTET STRING,
+	iPSourceAddress				[0] IPAddress,
-	h225RASMessageContent		[1] OCTET STRING,
+	iPDestinationAddress		[1] IPAddress,
-	h245MessageContent			[2] OCTET STRING,
+	h323Content					[2] H323MessageContent,
-	genericMessageContent		[3] OCTET STRING,
+	...
-	...
+}
-}
+H323MessageContent ::= CHOICE
-NationalIPMMIRIParameters ::= SEQUENCE
+{
-{
+	h225CSMessageContent		[0] OCTET STRING,
-	countryCode					[1] PrintableString (SIZE (2)),
+	h225RASMessageContent		[1] OCTET STRING,
-		-- Country Code according to ISO 3166-1 [16],
+	h245MessageContent			[2] OCTET STRING,
-		-- the country to which the parameters inserted after the extension marker apply.
+	genericMessageContent		[3] OCTET STRING,
 	...
-	-- In case a given country wants to use additional national parameters according to its law,
+}
-	-- these national parameters should be defined using the ASN.1 syntax and added after the
-	-- extension marker (...).
+NationalIPMMIRIParameters ::= SEQUENCE
-	-- It is recommended that "version parameter" and "vendor identification parameter" are
+{
-	-- included in the national parameters definition. Vendor identifications can be
+	countryCode					[1] PrintableString (SIZE (2)),
-	-- retrieved from the IANA web site (see Annex E Bibliography). Besides, it is recommended 
+		-- Country Code according to ISO 3166-1 [16],
-	-- to avoid using tags from 240 to 255 in a formal type definition.
+		-- the country to which the parameters inserted after the extension marker apply.
-}
+	...
+	-- In case a given country wants to use additional national parameters according to its law,
-AdditionalSignalling ::= CHOICE
+	-- these national parameters should be defined using the ASN.1 syntax and added after the
-{
+	-- extension marker (...).
-	sipHeaderLine				[0] OCTET STRING,
+	-- It is recommended that "version parameter" and "vendor identification parameter" are
-		-- A SIP header line, eg: "Contact: tel:+123456789".
+	-- included in the national parameters definition. Vendor identifications can be
-	...
+	-- retrieved from the IANA web site (see Annex E Bibliography). Besides, it is recommended 
-}
+	-- to avoid using tags from 240 to 255 in a formal type definition.
+}
-END -- end of IP Multimedia PDU
\ No newline at end of file
+AdditionalSignalling ::= CHOICE
+{
+	sipHeaderLine				[0] OCTET STRING,
+		-- A SIP header line, eg: "Contact: tel:+123456789".
+	...
+}
+END -- end of IPMultimediaPDU