hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.16 Optional support of SDP and annex C information elements
|
NOTE: "Annex C" relates to H.248.1 annex C "Tags for Media Stream Properties". Annex C information elements are not required in H.248 text encoding mode. Table 88 summarizes the "optional" SDP information elements, according their specific usage according clause 7.1.8 of ITU-T Recommendation H.248.1 [1]. Their usage may depend on the direction from MGC towards MG or vice versa. Details of which elements are included in each command are provided in clause 5.18. Table 88: Optional SDP Information Elements SDP Information Element Optional/mandatory Description Origin "o=" line Optional for MGC, Mandatory for MG The origin line consists of six fields (<username>, <sess-id>, <sess-version>, <nettype>, <addrtype> and <unicast-address>). The MGC is not required to supply this line but shall accept it (see clause 7.1.8 of ITU-T Recommendation H.248.1 [1]). The MG should populate this line as follows, e.g. o=- 0 0 IN IP4 11.9.19.65; or use the value received from the MGC. Session Name "s=" line Optional for MGC, Mandatory for MG The session name "s=" line contains a single field (<session name>). The MGC is not required to supply this line but shall accept it (see clause 7.1.8 in ITU-T Recommendation H.248.1 [1]). The MG should populate this line as follows, e.g. s=-; or use the value received from the MGC. Timing "t=" line Optional for MGC, Mandatory for MG The time "t=" line consists of two fields (<start time> and <stop time>). The MGC is not required to supply this line but shall accept it (see clause 7.1.8 in ITU-T Recommendation H.248.1 [1]). The MG should populate this line as follows, e.g. t=0 0; or use the value received from the MGC. Attribute "a=" line Optional for MGC, Recommended for MG 1) Application "RTCP transport address control": The attribute "a=rtcp" line may either contain (a=rtcp: <port>) or (a=rtcp: <port> <network type> <address type> <connection address>) when the "a=" line is used for RTCP transport port and optionally network address transmission. The MGC shall supply the "a=rtcp" line in the RD when non-default RTCP network address or transport port values are used by the peer media entity. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 48 SDP Information Element Optional/mandatory Description Optional for MGC, optional for MG 2) Application "Media-aware interworking (transcoding)": The "a=" line provides the complementary information for the "m=" line (see table 87) with regards to a specified media type/format (e.g. an optional SDP "a=ptime" line for a particular media format). For a dynamic RTP payload type, for each media information on the codec type shall be provided in a separate SDP "a=rtpmap"line and possibly additional SDP "a=fmtp"-line(s).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17 Overview of Procedures
|
Details of Session Dependent Procedures are provided in clauses 5.18. Details of Session Independent Procedures are provided in clauses 5.19 and 5.20.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1 Overview of Session Dependent Procedures
|
The general procedures are related to session-dependent (also known as H.248 call-dependent) procedures. There are procedures in following categories: • Address allocation and translation is in scope of clauses 5.17.1.2. The adaptation of addresses (latching) is the subject of clause 5.17.1.3. • Session-dependent policing is applicable to this profile. Different policing types are classified in Appendix I of ITU-T Recommendation Q.3303.2 [14]. The specific types of address policing and traffic policing are in scope of clauses 5.17.1.1 and 5.17.1.5 respectively. Media type policing is discussed in clause 5.17.1.8. • QoS support mechanisms are discussed in clause 5.17.1.4. • Measurement and reporting of statistics are discussed in clause 5.17.1.6. • RTCP handling (e.g. IP port allocation rules for RTCP) is discussed in clause 5.17.1.7. • Detection of inactive bearer connections is in scope of clause 5.17.1.9. • IP Realm/Domain Indication is discussed in clause 5.17.1.10. • Two-Stage BGF Resource Reservation is discussed in clause 5.17.1.11. • Detection of hanging H.248 Terminations is discussed in clause 5.17.1.12. • Real Time Statistics Reporting in clause 5.17.1.13. • Transcoding is discussed in clause 5.17.1.14. • Media-path coupled QoS signalling is discussed in clause 5.17.1.15. • VPN identification is discussed in clause 5.17.1.16. • Topology hiding is discussed in clause 5.17.1.17. NOTE: Annex D of [i.18] provides an example IP processing model for an H.248 (IP, IP) Context, indicating the IP packet processing functions behind above session-dependent procedures.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.1 Gate control
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.1.1 Streams, Terminations and Gates
|
The realization of a gate requires two ephemeral terminations. An ephemeral termination sources and/or sinks one or more media streams. Gates are direction and stream dependent. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 49 In this profile, RTP traffic shall be controlled through a single H.248 stream, representing both the RTP and RTCP flows, if the RTP Specific Behaviour property of the Gate Management package is set to ON. In such a case, when the MG is requested to allocate a port for an RTP flow, a consecutive port for the associated RTCP flow is automatically allocated (see also clause 5.17.1.7). In this case, monomedia sessions require one bidirectional H.248 stream on a termination, while a multi-media sessions (e.g. audio and video) would require multiple H.248 streams on a termination (one stream per media type).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.1.2 Assignment of L3 address and L4 port values
|
The H.248 base protocol enables the MGC to choose the IP address and port on which a termination will receive media flows. In addition, the Gate Management package enables the MGC to explicitly provide the following information: 1) expected IP source address and port of received packets; 2) IP source address and port of sent packets. The relationship between H.248 descriptors in this Profile and the addresses used in packets sent and received by the gate is indicated in table 89. Figure 2a illustrates the used naming conventions for the IP transport connection endpoints in the BGF and remote IP node. Table 89: Relation between Packet Direction, IP Address/Port and H.248 Descriptor/Information Packet direction IP Address/ L4 Port Source of Information for Transport Address values Received by termination Source: • RS(A) • RS(P) The source of information for the expected remote source transport address RS(A,P) value is dependent on the usage of remote source filtering and hosted NAP(T) traversal as per table 89a. Destination: • LD(A) • LD(P) Local destination transport address LD(A,P): Local Descriptor. Sent by termination Source: • LS(A) • LS(P) Local source transport address LS(A,P): 1. Availability of LS information due to explicit setting of local source transport address: LocalControl Descriptor/gate management/local source address + local source port; or, if not present: 2. Availability of LS information in H.248 Local Descriptor SDP: Source address not explicitly enforced/signalled via "gm" package. The source address is determined from the local SDP (which implies a symmetrical local network address, i.e. LD(A) = LS(A)). Destination: • RD(A) • RD(P) The source of information for the remote destination transport address RD(A,P) value is dependent on the usage of hosted NAP(T) traversal as per table 89b. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 50 Table 89a: Expected Remote Source Transport Address Expected remote source transport address RS(A,P): Hosted NA(P)T Traversal No Yes Filtering on Remote Source Address(es) No As no source filtering activated no specific RS(A,P) is expected. The BGF may determine actual RS(A) and RS(P) values by monitoring incoming IP packets. The expected remote source transport address is determined by the NAPT traversal process as described in [9]. Even if no filtering is ordered, the NAPT traversal process implies source filtering on the transport address after latching has occurred. Yes Alt 1. LocalControl Descriptor/gate management/remote source address mask AND/OR remote source port or remote source port range is used to determine the expected RS(A) and RS(P) values, which allows for the peer IP node to use asymmetric network address (RS(A) ≠ RD(A)). Alt 2. Combination of gate management and Remote Descriptor, which assumes symmetrical remote network address (RS(A) = RD(A)). 1st stage (before latching): Same as in cell to the left. 2nd stage (after latching): Same as in above cell. Table 89b: Source of Information for the Remote Destination Transport Address Remote destination transport address RD(A,P): Hosted NA(P)T Traversal No Yes Source of information The remote destination transport address is determined by the Remote Descriptor. The remote destination transport address is determined by the NAPT traversal process as described in [9]. This implies a symmetrical remote network address, i.e. RD(A) = RS(A). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 51 Bidirectional IP Transport Connection H.248 Media Gateway Peer Entity (e.g. IP host, IP next hop, H.248 MGC) Perspective DA IP Header SA DP SP L4 Header LD(A) LD(P) LS(A) LS(P) IP Transport Connection Endpoint RS(A) RS(P) RD(A) RD(P) Local Source Remote Destination Local Destination Remote Source IP Transport Connection Endpoint SA DA SP DP L4 Header IP Header LS(P) LS(A) … … RD(P) L4 RD(A) L3 … L2 … L1 LD(P) LD(A) … … LD(P) LD(A) … … RS(P) L4 RS(A) L3 … L2 … L1 LS(P) LS(A) … … Stream S1 Stream S1 Context C1 b) Protocol Layering a) Endpoint Naming Convention Legend for Names: LD Local Destination LS Local Source RD Remote Destination RS Remote Source Legend for Addresses: DA Destination Address DP Destination Port SA Source Address SP Source Port L3 Address L4 Port … Figure 2a: Naming conventions for IP transport connection endpoints (from BGF perspective; in line with H.248.1 conventions) NOTE: H.248.1 may in the future provide a general overview of IP transport connection endpoints similar to figure 2a. Figure 2a will be then replaced by a reference to H.248.1.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.1.3 Opening and closing of gates
|
Opening and closing gates is achieved by setting the Stream mode parameter of the associated termination(s) to the appropriate values. Subtracting a termination from a context also closes the gate for all H.248 streams in the termination. In the context of conversational services, an active session requires that the gates in both directions be opened (terminations in bi-directional mode).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.1.4 Filtering due to conditions on L3 address and/or L4 port values
|
Filtering on the IP source address and/or port might be implemented using the Gate Management package, or using the SDP information in the Remote Descriptor. In case the filtering is done based on the Remote Descriptor, the activation/deactivation of the filtering is configured in the MG. If the Gate Management package is used, it shall override the configured value in the MG. NOTE: It should be noticed that the IP source address and port may not always be available to the MGC. When SIP signalling is used, the session description does not contain this information (i.e. according to RFC 3264 [7], the IP address and port present in an SDP offer indicate nothing about the source IP address and source port of RTP and RTCP packets that will be sent by the offerer). Any other protocol that uses SDP as a session description mechanism (e.g. RTSP) has the same constraints. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 52 In such configurations, the Gate Management Package may be used as follows: • in an IPv6 environment, the Source Address Mask property contains the 64 bits prefix of the IP address that is set in the termination's Remote Descriptor; • in an IPv4 environment, the Source Address Mask property contains the IP address that is set in the termination's Remote Descriptor, except that a number of trailing digits may be wildcarded; • in both cases, Source Port Filtering should not be activated. The gate concept, together with H.248 Stream/Termination handling, is further illustrated in annex A of [i.18].
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.2 Allocation and translation of IP addresses, ports and versions (NAPT-PT)
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.2.1 Allocation methods
|
The procedures of this clause support the following NAPT-PT functionality: • NAPT-PT functionality with "double" addresses and ports translation (both source and destination addresses and ports are translated; example see clause 5.17.1.2.2); • or optional NAPT-PT functionality with "single" address and port translation (either source or destination address and port translation; (see also clause 5.17.1.2.3)) - applicable if the BGF has router functionality, or direct L2 connectivity with user terminals. The H.248 base protocol enables the MGC to either choose the addresses and ports associated with a termination or to request the MG to allocate these IP addresses and ports. NAPT control on destination addresses and ports is achieved by setting the Local and Remote Descriptors according to the following principles: • The IP and port address in the Remote Descriptors are set by the MGC according to the information received in call/session signalling (e.g. SDP in SIP INVITE and 200 OK). • The address and port in the Local Descriptor are selected by the MG within the indicated IP address realm from MGC side (see also below). If the BGF has router functionality, or direct L2 connectivity with the user terminals, the address and port of the Local Descriptor towards the private network may optionally be set according to the following principles: • The IP and port address in the Local Descriptor towards the private network is provided by the MGC (instead of being selected by the MG). The MGC shall copy the Remote Descriptor of the public network into the Local Descriptor towards the private network (see also clause 5.17.1.2.4.1). The MGC has the ability to choose the address space in which the MG allocates an IP address. This is achieved by setting the IP realm identifier in the IP Domain Connection package to the appropriate value (see clause 5.17.1.10). The association of dedicated "IP address spaces" (also known as "IP address realms" or briefly "IP realms", see RFC 2663 [8]) with the IP realm identifier requires a mutual agreement between MGC and MG. This is realized via provisioning, thus beyond the scope of this Profile.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.2.2 "Double" NA(P)T
|
The term "double" NA(P)T relates to the translation of source and destination address information: • "double" NAT = translation of 2-tuple (DA, SA) is not supported by this profile (because it would require the L4-port agnostic mode); • "double" NAPT = translation of 4-tuple (DA, SA, DP, SP), i.e. L4-port aware mode. EXAMPLE: (here "double" NAPT): Figure 3 provides an example of "double" network address and port translation, where a session is to be established between IPv4 addresses 10.140.120.10 (private address) and 156.106.192.33 (public address). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 53 H.248 IP-to-IP Context C1 T1(S1) T2(S1) Stream Descriptor for T1 LS(P) LS(A) … … RD(P) L4 RD(A) L3 … L2 … L1 LD(P) LD(A) … … RS(P) RS(A) … … LD(P) LD(A) … … RS(P) L4 RS(A) L3 … L2 … L1 LS(P) LS(A) … … RD(P) RD(A) … … Stream S1 Stream S1 Context C1 a) H.248 Context model Local Descriptor: LD(A) = 10.200.30.20 LD(P) = 334 Remote Descriptor: RD(A) = 10.140.120.10 RD(P) = 222 c) Protocol Layering Stream Descriptor for T2 Local Descriptor: LD(A) = 139.100.0.121 LD(P) = 334 Remote Descriptor: RD(A) = 156.106.192.33 RD(P) = 556 b) Stream Descriptors NOTE: There is only one H.248 Stream (S1) per Termination in this example. Figure 3: Network Address and Port Translation (NAPT) - Example for bidirectional ("double") translation
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.2.3 "Single" NA(P)T
|
The term "single" NA(P)T relates to the translation of either source-only or destination-only address information: • "single" NAT = translation of 1-tuple (SA) or (DA) is not supported by this profile (because it would require the L4-port agnostic mode); • "single" NAPT = translation of 2-tuple (SA, SP) or (DA, DP), i.e. L4-port aware mode. Example (here "single" NAPT on (DA, DP)-tuple elements): For "single" network address and port translation applications, the T1 Local Descriptor address and port in figure 3 has to be changed to 156.106.192.33:556 (equal to the T2 Remote Descriptor address and port). T1-to-T2 IP flow direction: • The (DA, DP)-tuple values will be then not changed (called "destination NAPT-less"), whereas the (SA, SP)-tuple values are translated ("source NAPT-full" mode). = single NAPT. T2-to-T1 IP flow direction: • The (DA, DP)-tuple values and the (SA, SP)-tuple values are both translated ("source and destination NAPT-full" mode). = double NAPT. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 54
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.2.4 NA(P)T-less case
|
See also clause H.3 of [i.18]. 5.17.1.2.4.1 NA(P)T-less B2BIH mode For NA(P)T-less applications, the T1 Local Descriptor address and port in figure 3 has to be changed to 156.106.192.33: 556 (equal to the T2 Remote Descriptor address and port) and the T2 Local Descriptor address and port in figure 3 has to be changed to 10.140.120.10: 222 (equal to the T1 Remote Descriptor address and port). Further aspects from H.248 control perspective: • There is either a "source and destination NAT-less" mode (briefly NAT-less). • Or a "source and destination NAPT-less" mode (briefly NAPT-less). • All other combinations may be mapped on NA(P)T-full scenarios (e.g. L3 NAT-less but L4 port translation). • The NAT-less B2BIH and NAPT-less B2BIH mode using both the same H.248 control method, i.e. the RD(A,P) address value from the H.248 RD is copied by the MGC in the LD(A,P) value of the H.248 LD of the other H.248 IP Termination. This can only be done once the RD of both terminations are known to the MGC and the profile thus allows for a LD to be absent in the ADD request command. 5.17.1.2.4.2 NA(P)T-less IPR mode See annex H of [i.18], not supported by this profile.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.2.5 NA(P)T and explicit Local Source Transport Address settings
|
NAPT control on source addresses and ports (i.e. source NAPT) is achieved by setting the local source address and local source port properties defined in the Gate Management package to a value that differs from the actual source address of the packets received from the remote entity. The gm package capabilities may be also used for source NAT control only, i.e. without explicit L4 port settings. The explicit local source setting capabilities will lead to an overall: • "single NA(P)T" mode in case of a destination NA(P)T-less mode; or • "double NA(P)T" mode in case of a destination NA(P)T-full mode.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.2.6 Protocol Translation (V4 to V6)
|
Protocol Translation (NAPT-PT) can be controlled by the MGC by adding to the same H.248 context, two terminations whose media descriptors have different address-type values in the "c=" line. NOTE: It is recommended that the MGC takes precaution if setting up streams with both fully specified and under specified address and/or port towards the same realm in a MG, as this could otherwise lead to conflicting address or port assignments. The exact mechanism for how clashes is avoided is beyond the scope of this profile. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 55
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.3 Support of Hosted NAT Traversal
|
"Hosted NAT Traversal" relates to "assisting remote NAT/NAPT traversal" for the remote (peer) IP connection endpoints from BGF/SPDF point of view. This relates to an interim NA(P)T device from BGW perspective. The remote IP address information cannot be retrieved from the Remote Descriptor. The "Hosted NAT Traversal" function is controlled by the MGC using the IP NAPT Traversal package (ipnapt). Using the napt package, the MG is requested to perform media latching, i.e. listen for incoming media and latch to the remote address information of that media. When Hosted NAT Traversal is applied to a stream associated with multiple flows (for example RTP and RTCP), the MG shall perform individual latching and/or re-latching on the various flows. This means that an RTP and an RTCP flow of a single stream can be latched to different remote addresses and/or ports.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.4 QoS marking
|
The Differentiated Services package enables the MGC to control the setting of the DSCP value for all packets leaving the MG.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.4.1 Copying DSCP/ToS values from the ingress to egress
|
The copy mechanism is specified in Amendment 1 to H.248.52 [17].
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.4.2 Auditing the "Per-Hop Behaviour"
|
The Per-Hop Behaviour (PHB) concerning "MGC-signalled QoS marking" versus "copying of QoS values" may be explicitly controlled (and audited) using Differentiated Services package version 2, see Amendment 1 to H.248.52 [17]. The Differentiated Services package version 1 does not allow to audit the behaviour, see the note at the end of clause 7.6.1.3 in Amendment 1 to H.248.52 [17].
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.5 Bandwidth control - Reservation, Allocation and Policing
|
Resources are reserved independently per gate. For each gate, reservation of local resources for handling incoming and outgoing traffic is achieved by setting the appropriate properties in the Local and Remote Descriptors. Only one session description shall be included in each Stream Descriptor. Hence, the ReserveValue and ReserveGroup properties should not be used. The function of bandwidth control (which relates to bit- and byterate control in this profile) is structured in following clauses: • admission control (AC; clause 5.17.1.5.1); • traffic descriptor (clause 5.17.1.5.2); • traffic reservation and allocation (clause 5.17.1.5.3); and • traffic policing (clause 5.17.1.5.4).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.5.1 Admission Control
|
Admission Control is defined in RACS for the BGF (MG role) level. There is no concept of a call in H.248 MGs due to the separation of call and bearers in the H.248 model, which means that AC translates in a Context Admission Control (CoAC; see also ITU-T H.Sup6) and Stream Admission Control (StAC) on MG side. The StAC and CoAC is triggered with the first incoming ADD.request Command. At that point a decision is taken whether the new context can be established or not. The StAC is triggered whenever a modification of an existing H.248 context, e.g. in terms of traffic descriptor, is requested. At that point a decision is taken whether the context modification can be accepted or not. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 56 5.17.1.5.1.1 Admission Control in this Profile The BGF AC is based on the requested H.248 stream level usage parameters and already established Contexts. The stream level usage parameters are given by the H.248 Media Descriptor in the ADD.request (and MODIFY.request) commands. The "usage parameters" as input for the AC of this Profile are mainly related to "bandwidth" information (see next clause on "traffic descriptor"). Specific AC algorithms could principally follow a deterministically or a statistically based multiplexing model. Concrete algorithms are implementation specific, thus out of scope of this profile. The result of an admission control (here CoAC or StAC) is either an accept or reject decision. NOTE: Step 2 in figure 4 shows an accept decision, which is implicitly given by the command reply on the ADD.request for the IP termination. A reject decision would be indicated by an appropriate H.248.8 [30] error code in the reply.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.5.2 Traffic Descriptor
|
A traffic descriptor is the set of traffic parameters that is used to capture the traffic characteristics of an IP flow (see clause 3.2.10/ITU-T Recommendation Y.1221 [i.10]). The traffic parameters for an H.248 Stream of an H.248 IP Termination are direction-independent and given by either: 1) an explicit specification via: - the "b=" line in the SDP description of the Local Descriptor and Remote Descriptor; or - the properties of the Traffic Management package; or 2) an implicit specification via: - the "m=" line in the SDP description of the Local Descriptor and Remote Descriptor (e.g. traffic usage estimate based on SDP media type and further mode of operation information). NOTE: There is no concept of a traffic contract explicitly used in the scope of this Profile version, because specific QoS classes (see ITU-T Recommendation Y.1541 [i.11]) are not signalled per termination. Nevertheless, the "QoS marking" information (see clause 5.17.1.4) could be used for QoS class indications, but such concepts are orthogonal to profile specifications, therefore out of scope of the present document.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.5.3 Bandwidth reservation and allocation
|
5.17.1.5.3.1 SDP "b=" line for constant bitrate traffic The amount of required bandwidth for sending packets is expressed using the "b=" line of the SDP description contained in the Remote Descriptors. The amount of required bandwidth for receiving packets is expressed using the "b=" line of SDP description contained in the Local Descriptors or using one of the properties (tman/pdr or tman/sdr) of the traffic management package. 5.17.1.5.3.2 Properties of the Traffic Management package for variable bitrate traffic The Traffic Management package (tman) should be used in case of variable bit rate traffic. There are then two semantics for some tman properties. All properties may be applied for bandwidth policing. The two properties tman/pdr and tman/sdr would be used additionally for bandwidth reservation (see note). NOTE: The property tman/pol indicates whether just reservation is applied ('OFF'), or whether both semantics are in use ('ON'). The semantic for 'OFF' is going beyond the property definition in tman version 1 package. This should be non-controversial because these tman properties may be considered as elements of a traffic descriptor, i.e. information elements used for admission control (besides policing). 5.17.1.5.3.3 Examples for bandwidth reservation See informative annex F of [i.18]. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 57
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.5.4 Bandwidth policing
|
Policing of incoming traffic can be enabled using the Traffic Management package. Policing on incoming traffic can be set independently for each gate. The properties of the Traffic Management package shall be set to values that are compatible (see note) with the "b=" line value of the Local Descriptor. NOTE: The term "compatible" means that the b-line and the traffic management represent identical bandwidth value with respect to the protocol layer they are defined upon: - Constant bit rate: "b=" line = tman/pdr = tman/sdr. - Variable bit rate: "b=" line = tman/pdr. 5.17.1.5.4.1 Statistics for bandwidth policing Policing of incoming traffic is related to policy rules based on the following: • policy conditions on: - "IP byte-rate" parameter(s) (peak-rate and/or sustainable-rate); and/or - "IP packet size" parameter(s) (see H.248.53 [19]; signalling method not supported by this profile); and • policy actions: - accept conforming IP packet; or - silently discard non-conforming IP packet (in case that profile is not supporting the tmanr package); or - discard non-conforming IP packet and record event by tmanr statistics (see clause 5.17.1.6.3.3). The policy actions are executed per IP packet.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.5.5 Non-specification of tman properties
|
If no properties of the Traffic Management package are provided, the MG will not perform traffic policing. If only the tman/pol property set to ON is present, traffic policing shall not be done based on the b-line value, i.e. the policing function cannot be activated at this stage. Summary on bandwidth control actions: Table 89ba: Bandwidth control actions in relationship to tman version 1 properties H.248 property usage Semantic tman/pol tman/pdr tman/dvt tman/sdr tman/mbs Bandwidth control actions ON Not sent Not sent (use default) Not sent Not sent (use default) No traffic management. OFF OR not sent (default=OFF) Not sent Sent OR not sent (use default) Not sent Sent OR not sent (use default) No traffic management. OFF OR not sent (default=OFF) Sent Sent OR not sent (use default) Not sent Sent OR not sent (use default) No traffic management The property tman/pdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. OFF OR not sent (default=OFF) Not sent Sent OR not sent (use default) Sent Sent OR not sent (use default) No traffic management The property tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 58 H.248 property usage Semantic tman/pol tman/pdr tman/dvt tman/sdr tman/mbs Bandwidth control actions OFF OR not sent (default=OFF) Sent Sent OR not sent (use default) Sent Sent OR not sent (use default) No traffic management The property tman/pdr or tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ON OR not sent (default=ON) Sent Sent OR not sent (use default) Not sent Sent OR not sent (use default) Single stage policer (pdr, dvt) The property tman/pdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ON OR not sent (default=ON) Not sent Sent OR not sent (use default) Sent Sent OR not sent (use default) Single stage policer (sdr, mbs) The property tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ON OR not sent (default=ON) Sent Sent OR not sent (use default) Sent Sent OR not sent (use default) Dual stage policer ((pdr, dvt); (sdr, mbs)) The property tman/pdr or tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.6 Usage metering and statistics reporting
|
Usage metering is supported by the statistics defined in the network and other packages. Such statistics may be notified to MGC when a stream is removed (and stats explicitly requested by the MGC) or a termination is subtracted from a context (e.g. at the end of a session). They provide information about: 1) information about resource usage, e.g.: - the duration of the time a termination has been in a context; - the traffic volume, e.g. number of octets sent and received; 2) information about Grade of Service (GoS)/Quality of Service (QoS), e.g.: - the packet delay variation or packet transfer delay. The "number of octets" for the case of nt package based measurement is calculated as defined in clause E.11.4 in ITU-T Recommendation H.248.1 [1]). The number of discarded packets due to H.248.43-based, explicit source filtering may be reported on basis of the gm/dp statistic. The number of discarded packets due to H.248.37-based, implicit source filtering may be reported on basis of the lstat/dp statistic. The number of discarded packets and octets due to H.248.53-based, explicit traffic filtering may be reported on basis by the tmanr statistics.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.6.1 Statistics for Media/Transport-agnostic IP packets
|
The available statistics for the IP streams and terminations of a dedicated context are dependent of the IP-to-IP interworking mode (see clause 3.1).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.6.2 Traffic Volume related Statistics
|
Figure 3a provides an overview of different traffic volume related statistics, which might be useful for the various IP-to-IP interworking modes (e.g. media-agnostic, media-aware, transport-protocol agnostic). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 59 5.17.1.6.2.1 General Case The general case relates to Ia profile version 1, i.e. media-agnostic IP-to-IP interworking. Traffic volume related statistics are only accessible by the nt package in profile version 1, and by the nt and rtp package in profile version 2. Profile version 3 provides additional metrics. Application Level Framing Protocol RTP, UDPTL, … L3: IP L2 L4: UDP, TCP, … L1 e.g. audio codec Transport Protocol Network Protocol Application Data Principle protocol stack for H.248 IP Terminations transport overhead reported traffic volume b c d a e rtpad nt & rtp ipocs Figure 3a: Overview of supported statistics - Traffic volume related statistics on different protocol layers 5.17.1.6.2.2 RTP Case (general) "Media-aware" IP terminations with RTP as application level framing protocol may use traffic volume based statistics via the RTP package: • packet granularity: RTP packets sent and/or received. NOTE: Packet level statistics could already provide useful volume measurements in case of RTP packets with constant length. • octet granularity: RTP octets send/received statistics are coupled with nt package statistics, i.e. these statistics are also including RTP padding, RTP header information and UDP transport overheads. Such overhead is excluded in the RTP application data specific statistics (see clause 5.17.1.6.2.3). 5.17.1.6.2.3 RTP Case: application data The RTP Application Data package provides support for explicit octet count statistics concerning media traffic, i.e. the RTP payload volume.5.17.1.6.2.4 IP Case: network layer data The IP layer octets count statistics package provides traffic volume statistics on IP layer for IP version 4 or 6. The H.248 ipocs package (see indication in above Figure 3a) is not supported by this profile version. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 60
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.6.3 Statistics for packet filtering
|
5.17.1.6.3.1 Address policing: explicit remote source transport address filtering Filter conditions based on source transport address information for remote IP endpoints may be enabled with Gate Management properties (see also clause 5.17.1.1). The number of discarded packets due to remote source filtering may be reported on basis of the gm/dp statistic. 5.17.1.6.3.2 Address policing: implicit remote transport address filtering due to latching The lstat/dp statistic is used for recording the number of discard packets due to implicit filtering of the latching function. See also clauses 1.3 and 6.6.7.2 in ITU-T Recommendation H.248.37 [9]. 5.17.1.6.3.3 Traffic policing: byte-rate policing See clause 7.4 in ITU-T Recommendation H.248.53 [19]. 5.17.1.6.3.4 Traffic policing: packet-size policing Not supported by this profile specification.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.7 RTCP Handling
|
Handling of RTCP is already partially addressed by clause 5.17.1.1. This clause defines further procedures for RTCP.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.7.1 RTCP Transport Address Allocation
|
5.17.1.7.1.1 Local RTCP IP Transport Address Allocation In line with the recommendations of RFC 3605 [31], separate address or non-contiguous RTCP port numbers (identified via the "a=rtcp" media attribute) shall not be used by the BGF in its LD. Local ports for RTCP are implicitly allocated by the MG whenever instructed to do so by the MGC via the gm/rsb=ON property. The MG must follow the port allocation rules as defined in clause 11 of RFC 3550 [i.8], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream. If the gm/rsb property is set to OFF, then no RTCP port is allocated in conjunction with an RTP stream. This behaviour is irrespective of the presence of the "a=rtcp" attribute in the related RD. 5.17.1.7.1.2 Remote RTCP Transport Address Representation/Usage, Implicit Allocation of IP Transport Addresses for RTCP RTCP ports are allocated either implicitly or explicitly when support of RTCP is required. RTCP support and RTCP address and port allocation is controlled as by the gm/rsb property and the "a=rtcp" media attribute line in the Remote Descriptor. If RTCP is sent within the same stream as RTP then RTCP port allocation is handled as follows: • gm/rsb=OFF or gm/rsb omitted. - RTCP support is not required. No pinhole is opened for received RTCP packets. No RTCP packets are sent and any received RTCP packets are silently discarded. This is irrespective of whether the "a=rtcp" attribute is present in the Remote Descriptor. • gm/rsb=ON and "a=rtcp" media attribute line not present. - RTCP support is required. A pinhole is opened for received RTCP packets. The MG must follow the port allocation rules as defined in clause 11 of RFC 3550 [i.8], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream in the Local Descriptor (see clause 5.17.1.7.1.1). RTCP packets are sent to the same address and contiguous port number to the RTP port as specified in the Remote Descriptor. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 61 • gm/rsb=ON and "a=rtcp" media attribute line present. - RTCP support is required. A pinhole is opened for received RTCP packets. The RTCP port and optionally address are explicitly identified by the included "a=rtcp" media attribute line. The MG must follow the port allocation rules as defined in clause 11 of RFC 3550 [i.8], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream in the Local Descriptor (see clause 5.17.1.7.1.1). If the "a=rtcp" media attribute line in the Remote Descriptor contains an address it is used as destination when sending RTCP packets. The destination port for RTCP packets is always explicitly identified via the "a=rtcp" media attribute line in the Remote Descriptor. 5.17.1.7.1.3 Unsuccessful transport address allocation In line with clause 5.17.1.7.1.1, neither a fully specified RTCP port nor RTCP address are ever used by the MGC in the Local Descriptor. Therefore, unsuccessful port/address allocation can only occur due to there being insufficient resources on the MG to allocate the (contiguous) RTCP port. Unsuccessful scenarios result in the MG responding with H.248 error code #510 ("Insufficient Resources").
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.7.2 RTP/RTCP to-H.248 Stream Mapping
|
In line with clause 5.17.1.7.1.1, a single common H.248 stream is always used for RTP and its associated RTCP flow.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.8 RTCP Forwarding
|
Every RTP session may be accompanied by RTCP control flows. Blocking (by the BGF) of such RTCP packets may violate the end-to-end RTP/RTCP protocol and/or the served applications. However, security threats or specific RTCP reports types may request for dedicated RTCP packet policing rules.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.8.1 Conditions for RTCP packet policing
|
Conditions for RTCP packet policing are typically based on following n-tupel elements: • IP port for RTCP flow; • RTCP packet type codepoint; • RTCP SSRC codepoint; • RTCP source description information element (e.g. CNAME codepoint); or/and • RTCP block type codepoint in case of RTCP extension reports (XR, HR).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.8.2 Forwarding of regular RTCP traffic
|
"Regular" RTCP packets shall be understood in the scope of the present document as packet units with a packet type value equal to a value from the range of {192, 193, 200 to 206}. Thus, regular traffic excludes XR and HR RTCP packets. Regular RTCP packets must be basically forwarded towards the RTP endpoint. Regular RTCP packets are be unambiguously identified by the 3-tupel of {packet type, SSRC, CNAME}. Thus, RTCP packets with e.g. an incorrect {SSRC, CNAME} combination may be blocked.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.8.3 Handling of RTCP XR/HR traffic
|
Extension reports (XR) and XR-based high resolution reports, - i.e. RTCP reports with a packet type value equal to 207 - carry measurement data from Measurement Points (MP) to Reporting Points (RP). Such measurement reports do not have necessarily an end-to-end significance, their scope may be e.g. limited to a single IP domain or "RTP network segment". The BGF may have to apply dedicated forwarding policy rules for such RTCP packets. Concrete policy rules are for further studies. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 62
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.9 Media Inactivity
|
Application data inactivity detection (also known as media inactivity detection) may have multiple, different use cases as cited in ITU-T Recommendation H.248.40 [12] e.g.: • detection of interrupted IP routes; • detection of released RTP endpoints; • detection of hanging SIP/RTP sessions (see note); or • detection of deadlocks in IP latching scenarios. NOTE: The notation of "SIP/RTP session" relates to a SIP-controlled RTP session, which implies a RTP session on MG level and a SIP session on MGC level. There might be a hanging RTP session (leg) or a SIP session (leg). The application of H.248.40 is able to address both failure scenarios. In all use cases, the adid v1 package (with possible different timing and/or direction configurations of the detection logic) is used to report the detected inactivity. The adid/ipstop event is enabled on a per H.248 IP termination basis, i.e. not on H.248 stream level. The BGF monitors all (IP) transport ports associated with the termination.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.10 IP Realm/Domain Indication
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.10.1 Codepoint and format/encoding
|
The IP realm identifier (i.e. H.248 property ipdc/realm) may be sent to the BGF in order to indicate the IP domain/realm of the H.248 IP termination. The IP realm identifier is a flexible string and may convey a numerical IP address, domain name or mutually understood name (e.g. "in"and "out", "1" and "2", etc.) (see note). The ephemeral termination string layout ("ip/<group>/<interface>/<id>") is still used in this version of the profile but the "interface" field is always set to CHOOSE by the MGC in an Add request command and is assigned by the MG. The MG may use the "interface" field to denote a physical or logical interface on the MG. NOTE: The usage of the IP realm identifier in this version of the profile is generalized and goes somewhat beyond the original definition (by ITU-T Recommendation H.248.41 [16]) of the identifier. This is due to the following reasons: a) syntax: backward compatibility with Ia profile version 1 (format/encoding syntax by field "Interface" in TerminationID); and b) semantic: generic "domain identifier" for "domain concepts" beyond IP address spaces. Such "domain concepts" could be related to specific technologies, specific protocol layers, virtual private network types, etc.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.10.2 Unsuccessful indication
|
If the value of the IP realm identifier sent by the MGC within the ITU-T Recommendation H.248.41 [16] package property cannot be recognized by the BGF, the BGF will fail to create the IP based H.248 termination and replies with an error descriptor using the error code 449 (Unsupported or Unknown Parameter or Property Value).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.10.3 Fix assignment per termination lifetime
|
The MGC may or may not choose to assign IP realm identifier when communicating with the MG e.g. not sent if IP Realm configured on the MG. If the MGC assigns IP Realm then this must be communicated at termination seizure (Add). The value of IP Realm shall be applied to all streams associated with the termination. The IP Realm identifier indicates the IP domain/realm of the H.248 termination and cannot therefore be changed after the initial assignment at Add. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 63 The IP Realm identifier cannot be subsequently changed in a Modify command once assigned to a termination. Only an identical/unchanged setting of IP realm identifier may be sent in a Modify command. If the MGC attempts to change the IP realm on an existing termination via a Modify command, the BGF will reply with an error descriptor using the error code 501 ("Not Implemented").
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.10.4 Number of IP Realms/Domains
|
The BGF supports typically multiple logical IP interfaces, which may belong to different IP address realms. Following principal use cases may be distinguished: 1) Single realm: - All IP interfaces of the BGF, and therefore all created H.248 IP terminations, belong to the same IP address space. 2) Multiple realms (N private realms and M public realms with N + M greater or equal to two): - The two H.248 IP terminations of an H.248 context may belong to the same IP address space or different realms. - The BGF may be principally connected to many IP address realms. For instance, N private domains, or one public and M private domains. Furthermore there could be overlapping address spaces between multiple private domains (see note). The H.248.41 [16] package property is used to indicate each realm. In general, if the ITU-T Recommendation H.248.41 [16] property is omitted, according to the H.248.41 [16] procedures the configured default IP realm is applied by the MG. NOTE: Overlapping IP address spaces could be discriminated by separation e.g. via physical (IP) interfaces, via a L3VPN technology (e.g. IPsec in tunnel mode), or via a L2VPN technology (e.g. VLANs). All above use cases are related to specific BGF deployment scenarios due to the static nature of a connection of a particular IP domain with the BGF.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.11 One-Stage and Two-Stage BGF Resource Reservation
|
The SDP offer/answer model (RFC 3264 [7]) allows offers and answers to be generated with or without "m=" and "b=" lines. The normal case is when both information contained in SDP "c=" and "m=" lines is available to the MGC at the time it requests the MG to create a termination is referred to as one-stage reservation. This means both "c=" and "m=" line information can be passed to the MG in a single step. If information contained in SDP "c=" line, but not "m=" and "b=" lines is available to the MGC at the time it requests the MG to create a termination, the MGC refrains from sending "m=" and "b=" lines to the MG. In order for media plane communication to take place through the MG, the MGC must at a later stage come back with at least "m=" lines to the MG. This would typical happen at a subsequent offer/answer exchange on the SIP plane. Such a reservation procedure is referred to as two-stage reservation. These actions at the Ia interface can be described with the following two-stage BGF resource reservation procedure: 1) MGC requests the MG to reserve an IP address (via the LD) in accordance to the specified IP realm and may also optionally reserve an IP port. In the former case, the SDP in local and/or remote descriptors does not contain "m=" nor "b=" lines. In the latter case, the SDP in local and/or remote descriptors does contain an underspecified "m=" line. The MGC does not request the MG to open any pinhole at this stage. 2) MGC requests the MG, in addition to the previously assigned IP address, to also allocate port(s) (if not done at stage 1) and optionally bandwidth or to optionally further specify the previously allocated port together with an optional bandwidth. The SDP in local and/or remote descriptors does contain "m=" and optionally "b=" lines. The MGC may request the MG to open pinholes at this stage. The command level details of one-stage and two-stage reservation procedures are specified in clauses 5.18.1 and 5.18.2, where one-stage is considered the default scenario and thus only the specifics of two-stage reservation are called out. Both stages in two-stage reservation are part of the overall session establishment phase. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 64
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.12 Hanging Termination Detection
|
For the correct operation of a BGF, synchronization of termination information between the SPDF and BGF is essential for traffic, maintenance and charging purposes. In some cases, the SPDF may have lost a record of a termination but the termination is not subtracted on BGF. The hangterm/ thb event defined in ITU-T Recommendation H.248.36 [24] may be used to solve this problem. After a period of message inactivity the BGF may issue a periodic Notify command on the concerned termination and the SPDF may use this to check if it has a record of the termination or not. The time period for this Notify may be parameter driven. Optionally the hangterm/thb event may result in an audit of MGCinfo/db property in order to determine the MGC information string.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.13 Real Time Statistics Reporting
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.13.1 Overview of conditional reporting
|
Normally a SPDF obtains bearer related statistics through periodic auditing of the H.248 statistic descriptor or at the time of deletion of a stream or subtraction of a termination. However, in both cases, there is a time delay from when a reporting condition occurs on a BGF (e.g. a statistic threshold being passed) and the SPDF learning of the statistic. In many cases, such a delay is of no consequence. However, in some cases, the SPDF may require to be immediately informed of a given statistical threshold condition occurring. In this case, the SPDF must use the H.248.47 Revision 1 [25] Statistic Conditional Reporting package. This package may be applied to multiple Statistics. The SPDF should set the reporting thresholds and ranges as appropriate and must specify at least one "condition" for conditional reporting (i.e. the SPDF must signal at least one condition per requested packageID/statisticID item). The exact Statistics and reporting conditions are determined by Operator configuration based on the application/service required.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.13.2 Basic conditional reporting
|
Basic conditional reporting uses the protocol elements of the Statistic Conditional Reporting package version 1. This allows the definition of many, but limited reporting conditions.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.13.3 Extended conditional reporting
|
Extended conditional reporting uses the protocol elements of the Statistic Conditional Reporting package version 2. This package allows in addition • to control whether a timestamp is reported with the detection of the (conditional reporting) events; and • extends the reporting conditions with value-based metric conditions.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.14 Transcoding
|
Definition see clause 3.1.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.14.1 Media types and formats (Codecs)
|
TS 181 005 [i.12] defines the codec services for TISPAN NGNs. There are codec recommendations in TS 181 005 [i.12] for narrowband audio, wideband audio and video media.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.14.2 Decision for transcoding
|
The decision for transcoding may be principally reached at the beginning or later during the lifetime of a call/session. The correspondent triggers (for transcoding decisions) from BGF side would be either related to ADD or MODIFY request commands. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 65 5.17.1.14.2.1 Decision at Stream/Termination creation The first ADD.request (of a new Context) for a new Stream/Termination provides either a full specification (by the SPDF) of the media type and format, or an under specification, which is then completed by the BGF. The subsequent request for the peer Stream/Termination (within this Context) is then leading to a possible transcoding decision. The BGF is comparing the SDP information elements for media description of the two H.248 Stream Descriptors: • In case of identical media type and formats then there will be no transcoding. The BGF may even handle this Stream in media-agnostic mode. • In case of different media type or/and formats then the BGF may decide for transcoding support or reject the request with an appropriate H.248.8 [30] error code (e.g. due to temporarily lacking resources for transcoding). 5.17.1.14.2.2 Decision at Stream/Termination modification MODIFY.request commands for existing Streams/Terminations may lead to a decision for transcoding.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.15 Void
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.16 VPN identification
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.16.1 VLAN marking
|
The BGF VLAN tagging behaviour is summarized in the following table: Table 89c: VLAN marking using vlan version 1 package H.248 property usage Semantic vlan/pri vlan/tags Action Sent Value smaller than "4 096" sent Apply VLAN tagging accordingly Sent Not sent (use provisioned default value) Apply VLAN tagging accordingly Not sent (use provisioned default value) Value smaller than "4 096" sent Apply VLAN tagging accordingly Not sent Not sent Do not apply VLAN tagging Sent or not sent Value "4 096" sent Do not apply VLAN tagging
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.17 Topology Hiding Function
|
Topology hiding may basically be related to the: a) hiding of "remote topology information", i.e. the BGF provides local support for topology hiding to network elements "behind" the BGF; b) hiding of "local topology information", i.e. the BGF provides local support for topology hiding of the BGF itself in one-way direction for the egress media-path. Topology hiding functions (THF) are required on SPDF (MGC) level for the IP signalling-path and on BGF (MG) level for the IP media-path, see [37] NOTE 1: THF relates basically to the hiding of (network element) local address information ("network topology hiding"). Address information is primarily related to L3 addresses, which are used on IP layer and by IP application protocols (like SIP). NOTE 2: BGF related THF scenarios are e.g. outlined by clause A.2 in [37]. For instance, the so-called Topology Hiding Gateway (THIG) function relates to a THF on IBCF (MGC) level for the IP signalling-path and on I-BGF (MG) level for the IP media-path in the IMS interconnect scenario (figure A.6 in [37]).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.17.1 THF for the IP signalling path
|
The assumption by this H.248 profile specification (and decomposed gateway architecture) is a media-path decoupled signalling path. Any THF for the IP signalling-path is thus out of scope of the present document. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 66
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.1.17.2 THF for the IP media /bearer path
|
5.17.1.17.2.1 THF on IP network protocol layer (L3) 5.17.1.17.2.1.1 THF on IP address information elements THF in the IP media-path may be basically achieved by NAT within the end-to-end IP connection. Remote NAT devices may support the hiding of MG local IP addresses, i.e. LS(A) and LD(A) information (see also figure 2a). MG-local THF support: • hiding of "remote topology information" via MG-local NA(P)T (see clause 5.17.1.2) may used for hiding of remote IP address information (i.e. RS(A) or/and RD(A) information); • hiding of "local topology information" via explicit source address setting capability (via gm package properties, see e.g. clause 5.18.1.1.3) with regards to the LS(A) value. NOTE: Properties gm/esas and gm/lsa for LS(A) control, and gm/esps and gm/lsp for LS(P) control. 5.17.1.17.2.1.2 THF on other IP PCI elements and ICMP THF on L3 is furthermore supported by: • IP TTL value reset in B2BIH mode. NOTE: Not in IPR mode. • ICMP: there is an ICMP traffic flow for each IP interface, however, the ICMP flow does not appear as a flow component within H.248 IP Streams (because ICMP is an IP layer service, out of control of H.248). 5.17.1.17.2.2 THF above the IP layer IP address information may be carried by media-path protocols above the IP layer. 5.17.1.17.2.2.1 THF for RTP as application level framing protocol RTP packets may be forwarded transparently (e.g. in transport-protocol agnostic mode, see clause G.2 of [i.18]) or terminated like in media-aware BGF mode. Termination implies a Back-to-Back RTP Endsystem (B2BRE mode) because each H.248 IP termination provides an IP host and RTP endsystem function. Thus, RTCP packets are sourced/sinked by the BGF in that mode. The Source Description (SDES) RTCP packet is mandatory, as well as the SDES item 'CNAME' (Canonical End-Point Identifier). RFC 3550 [i.8] recommends that: "The CNAME item SHOULD have the format "user@host", or "host" if a user name is not available as on single-user systems. For both formats, "host" is either the fully qualified domain name of the host from which the real-time data originates … or the standard ASCII representation of the host's numeric address on the interface used for the RTP communication." Such a CNAME format would advertise topology information via RTCP. THF for RTP/RTCP could be achieved e.g. either via SRTP (RFC 3711 [i.20]) or by just encrypting the SDES CNAME item (see clause 9.1 of RFC 3550 [i.8]). 5.17.1.17.2.2.2 Void ETSI ETSI TS 183 018 V3.5.2 (2010-01) 67
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.2 Overview of Session Independent Procedures
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.2.1 Introduction - Relation to TS 183 025
|
Session-independent procedures for this profile specification are defined in a separate document (TS 183 025 [i.2]), which is an overall description for all ETSI defined H.248 profile specifications, i.e. TS 183 025 [i.2] complements each profile specification. The set of profile-applicable call-independent procedures is primarily given by the supported H.248 Command API capabilities for AuditValue (see clause 5.8.5), AuditCapabilities (see clause 5.8.6) and ServiceChange (see clause 5.8.8), and supported packages (e.g. for overload control), by each profile.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.2.2 Session-independent procedures
|
Session-independent procedures are described in clauses 5.19 and 5.20.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.17.2.3 MG Overload Control: Rate limitation of H.248 Messages from MGC-to-MG
|
The H.248.11 [15] package (see clause 5.14.2.16) may be used for controlling MG overload, by throttling and limiting the rate of H.248 messages from MGC to MG. See clause 5.19.14 for the procedure and clause 5.20.23 for the command level details.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18 Session Dependent Procedures (Command Level Details)
|
The following clauses contain procedures which may be used to provide session handling within the MG. Within the present document a procedure constitutes a message sequence containing a Command Request and a Command Reply. Multiple procedures may be combined within a single action e.g. one action may contain an "Add Termination - Remote Addr and Port Known, Select Local Addr and Port" procedure and an "Add Termination - Select Local Addr and Port" procedure in order to seize two IP terminations and an associated context. NOTE: That the Local Address and Port in these procedures may be selected by the MG or the MGC (e.g. NA(P)T less mode). A procedure can be applied to a single stream or multiple streams within a single command. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 68 Table 90: Session Dependant Procedures - References Procedure Support Initiated By Clause Add Termination - Remote Addr and Port Known, Select Local Addr and Port (see note) M MGC 5.18.1.1 Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port (see note ) M MGC 5.18.1.2 Add Termination - Remote Addr Known, Select Local Addr (see note) M MGC 5.18.1.3 Add Termination - Remote Addr Unknown, Select Local Addr (see note) O MGC 5.18.1.4 Add Termination - Remote Addr Known and Port Possibly Known, no Local Addr and Port (see note) O MGC 5.18.1.5 Session Establishment Update - Remote Addr and Port Known M MGC 5.18.2.1 Session Establishment Update - Remote Addr Known M MGC 5.18.2.2 Session Establishment Update - Through Connect M MGC 5.18.2.3 Session Establishment Update - Remote Port Unknown, Select Local Port O MGC 5.18.2.4 Session Establishment Update - Bandwidth Change O MGC 5.18.2.5 Session Establishment Update - Delete Stream O MGC 5.18.2.6 Mid-Session Update - Bandwidth Change O MGC 5.18.3.1 Mid-Session Update - Media Change O MGC 5.18.3.2 Mid-Session Update - Remote Addr / Port Change O MGC 5.18.3.3 Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port O MGC 5.18.3.4 Mid-Session Update - Add Stream, Remote Addr and Port Unknown, Select Local Addr and Port O MGC 5.18.3.5 Mid-Session Update - Delete Stream O MGC 5.18.3.6 Mid-Session Update - Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port O MGC 5.18.3.7 Mid-Session Statistics Audit O MGC 5.18.4.1 Mid-Session MGC Info Audit O MGC 5.18.4.2 Notification of IP Media Stop O MG 5.18.5.1 Notification of Hanging Termination O MG 5.18.5.2 Notification of Statistic Conditional Reporting O MG 5.18.5.3 Delete Session/Termination M MGC
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.6.1 Delete Session/Termination
|
- Wildcarded Reply O MGC 5.18.6.2 NOTE: The IP real/domain indication may be implicit part of this procedure.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1 Add Termination
|
Within the Add Termination procedures the examples are shown as single commands operating on single terminations. The commands can be combined with other Add Termination commands within a single action. All of the Add Termination procedures can be applied to multiple streams within a single command. The Termination Group within the Termination Name is assigned by the MGC using some local policy and this policy is out of scope for this profile. It is, however, recommended that all Terminations within a Context are assigned to the same Termination Group. The Termination Group concept is useful to avoid excessively large H.248 messages and consequential processing implications when recovery after a failover occurs i.e. at Audit of active Contexts. When performing an Add after a failover the MGC will only use Termination Groups that have been audited. The IP Realm may be specified by the MGC using the ipdc package. If this property is not specified by the MGC, the MG shall assign a default IP Realm (see clause 5.18.1.1.2). The Interface field of the termination ID (see clause 5.6.1.1.1) shall be assigned by the MG. The allocation algorithm is out of scope of the present document but shall be related to the corresponding IP Realm.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1.1 Add Termination - Remote Addr and Port Known, Select Local Addr and Port
|
This procedure may be used by the MGC when the address and port of the remote end are known to the MGC. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 69 Table 91: Message Contents - Add Termination - Remote Addr and Port Known, Select Local Addr and Port Add Termination - Remote Addr and Port Known, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Request (MGC to MG) Context ID = $ M Termination ID = ip/group/$/$ M Media M Stream O Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Statistics O See note Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address = ($ or specific) M Address Information Port = ($ or specific) M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth O Remote SDP Information Version O SDP Information Session Name O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 70 Add Termination - Remote Addr and Port Known, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Attribute Information RTCP O Bearer Information Bandwidth O Signals O ipnapt/latch O napt O Events O g/cause O adid/ipstop O dt O dir O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O NOTE: The MGC may request any statistic within those supported. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 71 Table 92: Message Contents - Add Termination - Remote Addr and Port Known, Select Local Addr and Port Ack Add Termination - Remote Addr and Port Known, Select Local Addr and Port Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream O Local SDP Information Version M SDP Information Session Name M SDP Information Origin M SDP Information Timing M Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M Bearer Information Media format and type O Bearer Information Bandwidth O
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1.1.1 Conditions for Address Policing: SAF, SPF, SAM, SPR, SPRR
|
Two alternative procedures are permitted depending on the source information for address and port filtering. Procedure 1 Source Address and Port Determined from Gate Management Package properties (SAM, SPR, SPRR) If port and address filtering are required then SAF and SPF will both be included and set to ON. If only address filtering is required then SAF is set to ON and SPF set to OFF or omitted. The combination of SAF set to OFF and SPF set to ON is not allowed. If Remote Source Address Filtering is required (SAF=ON) then the Remote Source Address Mask must be included. If Remote Source Port Filtering is required (SPF=ON) then the Remote Source Port and/or Remote Source Port Range must be included. In case multiple flows are associated with a stream (for example RTP and RTCP), the settings of the SAF, SPF, SAM, SPR, and SPRR properties apply to all flows of the stream. The latching/re-latching capability (according ipnapt version 1 package) might be enabled for NAT traversal support. When latching/re-latching is requested, only incoming media packets passing the source address and port filter criteria (range or specific values) shall be considered for latching. When latching/re-latching occurs, the MG will implicitly filter incoming packets based on the result of the (re)latching process, i.e. in alignment with ITU-T Recommendation H.248.37 [9] Revision 1 procedures the latching/re-latching does not change the explicit filter criteria as defined by the gm package properties. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 72 EXAMPLE 1: The MGC sets SAF=ON, SAM=123.123.123.123, SPF=ON, no SPR, SPRR=1 024 to 65 535 and requests latching for a stream containing both RTP and RTCP. The MG will latch to first incoming RTP packet from source address 123.123.123.123 which is using a source port in the range of 1 024 to 65 535. In addition the MG will then apply implicit source filtering to the RTP flow using address 123.123.123.123 and the source port of the latched RTP packet. At first incoming RTCP packet from source address 123.123.123.123 which is using a source port in the range of 1 024 to 65 535, the MG will do a separate latch for the RTCP flow. The MG will then apply implicit source filtering to the RTCP flow using address 123.123.123.123 and the source port of the latched RTCP packet. Procedure 2 Source Address and Port Determined from RemoteDescriptor (SDP information) If port and address filtering are required then SAF and SPF should both be included and set to ON. If only address filtering is required then SAF must be set to ON and SPF set to OFF or omitted. The combination of SAF set to OFF and SPF set to ON is not allowed. In case multiple flows are associated with a stream (for example RTP and RTCP), the settings of the SAF and SPF properties apply to all flows of the stream. SAM, SPR, and SPRR are not used. The source address and source port filter values shall be determined from the received RemoteDescriptor (SDP information) or from a received packet (source address and source port) if latching/re-latching has been completed. Using remote SDP (i.e. SDP information from H.248 RD) for filtering assumes symmetrical address and port allocation at peer media plane entity. Thus, such a filter may be ineffective, or even discard correct packets, in the case of that the peer IP endpoint is using different IP interfaces for each traffic direction (i.e. asymmetrical IP addresses). The latching/re-latching capability (according ipnapt version 1 package) might be enabled for NAT traversal support. When latching/re-latching is requested SAF must be set to ON and SPF set to OFF or omitted (if SPF would be set to ON the MG could not latch to a different port as the explicit filters are applied before latching/re-latching). After latching/re-latching has been completed the MG will implicitly filter incoming packets based on the result of the latching/re-latching process in addition to the explicit filter criteria as defined by the gm package properties. EXAMPLE 2: For a stream containing both RTP and RTCP flows, the MGC sets SAF=ON, no SAM, SPF=OFF, no SPR, no SPRR, address in Remote Descriptor c= line 123.123.123.123, address in Remote Descriptor a=rtcp line 123.123.123.124 and requests latching. The MG will then latch to first incoming RTP packet from source address 123.123.123.123, independently of source port and in addition apply implicit source filtering using address 123.123.123.123 and the source port of the latched RTP packet. At first incoming RTCP packet from source address 123.123.123.124 the MG will do a separate latch for the RTCP flow. The MG will then apply implicit source filtering to the RTCP flow using address 123.123.123.124 and the source port of the latched RTCP packet. See also clause D.2 in [i.18] concerning a possible interaction.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1.1.2 Assigning IP Domain/Realm to Termination
|
The IP domain/realm of the termination is indicated through the ipdc/realm property. A default domain/realm may be provisioned and then the ipdc/realm property does not have to be specified. The <Interface> part of the termination ID is not used to indicate IP domain/realm. The IP Realm cannot be subsequently changed in a Modify command once assigned to a termination (via the Add command). Only an identical/unchanged setting of IP realm identifier may be sent in a Modify command. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 73 5.18.1.1.3 Add Termination - Remote Addr and Port Known, Select Local Addr and Port - Examples MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = $ { Priority = 6, Add = ip/104/$/$ { Media { Stream = 1 { LocalControl { Mode=Inactive, ds/dscp = 1D, gm/saf = ON, gm/spf = ON, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 c=IN IP4 $ m=- $ RTP/AVP - b=AS:128 }, Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:128 } } }, Events = 1235 { g/cause, adid/ipstop, nt/netfail, nt/qualert, scr/cr{si="nt/os",max=10000}, hangterm/thb {timerx =600} } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Add = ip/104/2/541 { Media { Stream = 1 { Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 74 MGC MG c=IN IP4 16.128.45.10 m=- 21609 RTP/AVP - b=AS:128 } } } } } Figure 4: H.248 Message Sequence Example - Add Termination - Remote Addr and Port Known, Select Local Addr and Port 5.18.1.2 Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port This procedure may be used by the MGC when the address and port of the remote end are not known to the MGC. Table 93: Message Contents - Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Request (MGC to MG) Context ID = $ M Termination ID = ip/group/$/$ M Media M Stream O Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Statistics O See note Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 75 Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Address Type IP4 or IP6 M Address Information IP Address = ($ or specific) M Address Information Port = ($ or specific) M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth O Signals O ipnapt/latch O napt O Events O g/cause O adid/ipstop O dt O dir O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O NOTE: The MGC may request any statistic within those supported. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 76 Table 94: Message Contents - Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port Ack Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream O Local SDP Information Version M SDP Information Session Name M SDP Information Origin M SDP Information Timing M Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M Bearer Information Media format and type O Bearer Information Bandwidth M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 77 5.18.1.2.1 Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port - Examples MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = $ { Priority = 6, Add = ip/104/$/$ { Media { Stream = 1 { LocalControl { Mode=Inactive, ds/dscp = 1D, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000, tman/pol = ON, ipdc/realm = "2" }, Local { v=0 c=IN IP4 $ m=- $ RTP/AVP - b=AS:128 } } }, Events = 1235 { g/cause, nt/netfail, nt/qualert, scr/cr{si="nt/os",max=10000}, hangterm/thb {timerx=600} } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Add = ip/104/2/541 { Media { Stream = 1 { Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 21609 RTP/AVP - b=AS:128 } } } } } Figure 5: H.248 Message Sequence Example - Add Termination - Remote Addr and Port Unknown, Select Local Addr and Port ETSI ETSI TS 183 018 V3.5.2 (2010-01) 78
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1.3 Add Termination - Remote Addr Known, Select Local Addr
|
This procedure may be used by the MGC when the address but not port of the remote end is known to the MGC. This is part of the first stage of a two-stage reservation. Table 95: Message Contents - Add Termination - Remote Addr Known, Select Local Addr Add Termination - Remote Addr Known, Select Local Addr H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Request (MGC to MG) Context ID = $ M Termination ID = ip/group/$/$ M Media M Stream O Local Control O ipdc/realm O Statistics O See note Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address = ($ or specific) M Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M NOTE: The MGC may request any statistic within those supported. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 79 Table 96: Message Contents - Add Termination - Remote Port Known, Select Local Addr Ack Add Termination - Remote Addr Known, Select Local Addr Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream O Local SDP Information Version M SDP Information Session Name M SDP Information Origin M SDP Information Timing M Address Type IP4 or IP6 M Address Information IP Address M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 80
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1.3.1 Add Termination - Remote Addr Known, Select Local Addr - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = $ { Priority = 6, Add = ip/104/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "1" }, Local { v=0 c=IN IP4 $ }, Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Add = ip/104/1/37 { Media { Stream = 1 { Local { v=0 o=- 0 0 IN IP4 129.192.57.2 s=- t=0 0 c=IN IP4 129.192.57.2 } } } } } Figure 6: H.248 Message Sequence Example - Add Termination - Remote Addr Known, Select Local Addr
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1.4 Add Termination - Remote Addr Unknown, Select Local Addr
|
This procedure may be used by the MGC when the address and port of the remote end are not known to the MGC, and two-stage reservation is applied. This is part of the first stage of the two-stage reservation. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 81 Table 97: Message Contents - Add Termination - Remote Addr Unknown, Select Local Addr Add Termination - Remote Addr Uknown, Select Local Addr H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Add Request (MGC to MG) Context ID = $ M Termination ID = ip/group/$/$ M Media M Stream O Local Control O ipdc/realm O Statistics O See note Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address = ($ or specific) M NOTE: The MGC may request any statistic within those supported. Table 98: Message Contents - Add Termination - Remote Addr Unknown, Select Local Addr Ack Add Termination - Remote Addr Uknown, Select Local Addr Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream O Local SDP Information Version M SDP Information Session Name M SDP Information Origin M SDP Information Timing M Address Type IP4 or IP6 M Address Information IP Address M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 82
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.1.4.1 Add Termination - Remote Addr Uknown, Select Local Addr - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = $ { Priority = 6, Add = ip/104/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "2"}, Local { v=0 c=IN IP4 $ } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Add = ip/104/1/37 { Media { Stream = 1 { Local { v=0 o=- 0 0 IN IP4 129.192.57.2 s=- t=0 0 c=IN IP4 129.192.57.2 } } } } } Figure 7: H.248 Message Sequence Example - Add Termination - Remote Addr Uknown, Select Local Addr 5.18.1.5 Add Termination - Remote Addr Known and Port Possibly Known, no Local Addr and Port This procedure may be used by the MGC when the address and possibly the port of the remote end is known to the MGC, but the local address and port cannot be assigned due to that the MG shall operate in NA(P)T-less B2BIH mode (see clause 5.17.1.2.4.1). This procedure may be part of the first stage of a two-stage reservation. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 83 Table 98a: Message Contents - Add Termination - Remote Addr Known and Port Possibly Known, no Local Addr and Port Add Termination - Remote Addr Known and Port Possibly Known, no Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Request (MGC to MG) Context ID = $ M Termination ID = ip/group/$/$ M Media M Stream O Local Control O ipdc/realm O 5.18.1.1.2 Statistics O See note Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port O Bearer Information Transport O See note 2 of table 87 Bearer Information Media format and type O Attribute Information RTCP O Bearer Information Bandwidth O Events O hangterm/thb O timerx O NOTE: The MGC may request any statistic within those supported. Table 98b: Message Contents - Add Termination - Remote Addr Known and Port Possibly Known, no Local Addr and Port Ack Add Termination - Remote Addr Known and Port Possibly Known, no Local Addr and Port Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Add Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 84 5.18.1.5.1 Add Termination - Remote Addr Known and Port Possibly Known, Selectno Local Addr and Port - Examples MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = $ { Priority = 6, Add = ip/104/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "1" }, Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:128 } } }, Events = 1235 { hangterm/thb {timerx =600} } } } } Figure 7a: H.248 Message Sequence Example - Add Termination - Remote Addr Known and Port Possibly Known, no Local Addr and Port
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2 Session Establishment Update
|
During session establishment additional information may be required by the MG terminations in order to establish the path. Examples of these changes are the remote address and port, through connection status and change of bandwidth allocation.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.1 Session Establishment Update - Remote Addr and Port Known
|
This procedure may be used by the MGC when the address and port of the remote end become known to the MGC. Table 99: Message Contents - Session Establishment Update - Remote Addr and Port Known Session Establishment Update - Remote Addr and Port Known H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream O Local Control O mode O ds/dscp O ds/tb O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 85 Session Establishment Update - Remote Addr and Port Known H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local O SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 86 Session Establishment Update - Remote Addr and Port Known H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Attribute Information RTCP O Signals O ipnapt/latch O napt O Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 87 Table 100: Message Contents - Session Establishment Update - Remote Addr and Port Known Ack Session Establishment Update - Remote Addr and Port Known, Through Connect, Bandwidth Change Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.1.1 Session Establishment Update - Remote Addr and Port Known - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:128 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 8: H.248 Message Sequence Example - Session Establishment Update - Remote Addr and Port Known ETSI ETSI TS 183 018 V3.5.2 (2010-01) 88 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/saf = ON, gm/spf = ON, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000, tman/pol = ON, ipdc/realm = "2" }, Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:128 } } }, Signals { ipnapt/latch{ napt=LATCH, stream=1 } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 9: H.248 Message Sequence Example - Session Establishment Update - Remote Addr and Port Known, Through Connect and Latch ETSI ETSI TS 183 018 V3.5.2 (2010-01) 89 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 13, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/saf = ON, gm/spf = ON, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 1875, tman/pol = ON, ipdc/realm = "2" }, Local { v=0 o=- 0 0 IN IP4 129.192.57.2 s=- t=0 0 c=IN IP4 129.192.57.2 m=- 56790 RTP/AVP - b=AS:15 }, Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:15 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 10: H.248 Message Sequence Example - Session Establishment Update - Remote Addr and Port Known, Through Connect, Bandwidth Change ETSI ETSI TS 183 018 V3.5.2 (2010-01) 90
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.2 Session Establishment Update - Remote Addr Known
|
This procedure may be used by the MGC when the address of the remote end becomes known to the MGC. This is a part of the first stage of a two-stage reservation. Table 101: Message Contents - Session Establishment Update - Remote Addr Known Session Establishment Update - Remote Addr Known H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream O Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Table 102: Message Contents - Session Establishment Update - Remote Addr Known Ack Session Establishment Update - Remote Addr Known Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 91
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.2.1 Session Establishment Update - Remote Addr Known - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 11: H.248 Message Sequence Example - Session Establishment Update - Remote Addr Known
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.3 Session Establishment Update - Through Connect
|
This procedure may be used by the MGC when media plane through connect occurs and remote end address and port have already been shared with MG. Table 103: Message Contents - Session Establishment Update - Through Connect Session Establishment Update - Through Connect H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream O Local Control M mode M ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 92 Session Establishment Update - Through Connect H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local O SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Remote O SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Signals O ipnapt/latch O napt O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 93 Session Establishment Update - Through Connect H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O Table 104: Message Contents - Session Establishment Update - Through Connect Ack Session Establishment Update - Through Connect Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 94
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.3.1 Session Establishment Update - Through Connect - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/saf = ON, gm/spf = ON, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000, tman/pol = ON, ipdc/realm = "1" } } }, Signals { ipnapt/latch{ napt=LATCH, stream = 1 } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 12: H.248 Message Sequence Example - Session Establishment Update - Through Connect ETSI ETSI TS 183 018 V3.5.2 (2010-01) 95 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/saf = ON, gm/spf = ON, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 o=- 0 0 IN IP4 129.192.57.2 s=- t=0 0 c=IN IP4 129.192.57.2 m=- 56790 RTP/AVP - b=AS:15 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 13: H.248 Message Sequence Example - Session Establishment Update - Through Connect, Bandwidth Change
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.4 Session Establishment Update - Remote Port Unknown, Select Local Port
|
This procedure may be used by the MGC to allocate a local port when the remote port is still unknown. This is the second stage of a two-stage reservation. Table 105: Message Contents - Session Establishment Update - Remote Port Unknown, Select Local Port Session Establishment Update - Remote Port Unknown, Select Local Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream O Local Control O mode O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 96 Session Establishment Update - Remote Port Unknown, Select Local Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port = ($ or specific) M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Signals O ipnapt/latch O napt O Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O hangterm/thb O timerx O scr/cr O si O dur O per O max O min O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 97 Session Establishment Update - Remote Port Unknown, Select Local Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes nor O rt O typ O val O dev O com O dir O Table 106: Message Contents - Session Establishment Update - Remote Port Unknown, Select Local Port Ack Session Establishment Update - Remote Port Unknown, Select Local Port Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream O Local M SDP Information Version M SDP Information Session Name M SDP Information Origin M SDP Information Timing M Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M Bearer Information Media format and type O Bearer Information Bandwidth M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 98 5.18.2.4.1 Session Establishment Update - Remote Port Unknown, Select Local Port - Examples MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= Inactive, ds/dscp = 1D, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 1875, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- $ RTP/AVP - b=AS:15 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { Media { Stream = 1 { Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 21609 RTP/AVP - b=AS:15 } } } } } } Figure 14: H.248 Message Sequence Example - Session Establishment Update - Remote Port Unknown, Select Local Port ETSI ETSI TS 183 018 V3.5.2 (2010-01) 99
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.5 Session Establishment Update - Bandwidth Change
|
This procedure may be used by the MGC when the media plane bandwidth is changed during session establishment. Table 107: Message Contents - Session Establishment Update - Bandwidth Change Session Establishment Update - Bandwidth Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream M Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O gm/sam O gm/spr O gm/sprr O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 100 Session Establishment Update - Bandwidth Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O hangterm/thb O timerX O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O Table 108: Message Contents - Session Establishment Update - Bandwidth Change Ack Session Establishment Update - Bandwidth Change Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 101
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.5.1 Session Establishment Update - Bandwidth Change - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 1875, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 21608 tcp - b=AS:15 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 15: H.248 Message Sequence Example - Session Establishment Update - Bandwidth Change 5.18.2.6 Session Establishment Update - Delete Stream This procedure is used when remote end SDP indicates that a sub-set of requested streams have been accepted and the remaining streams rejected. This procedure thus applies to both the accepted and rejected streams. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 102 Table 108a: Message Contents - Session Establishment Update - Delete Stream Session Establishment Update - Remote Addr and Port Known H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream M See note 1 Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local M See note 2 SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 O Address Information IP Address O Address Information Port O Bearer Information Transport O See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth O Remote M See note 3 SDP Information Version O SDP Information Session Name O SDP Information Origin O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 103 Session Establishment Update - Remote Addr and Port Known H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes SDP Information Timing O Address Type IP4 or IP6 O Address Information IP Address O Address Information Port O Bearer Information Transport O See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth O Attribute Information RTCP O Signals O Ipnapt/latch O napt O Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O NOTE 1: There will multiple instances of this descriptor. NOTE 2: This descriptor must be present for rejected streams and optionally present for accepted streams. In the former case, the descriptor is empty (see clause 5.18.2.6.1). NOTE 3: Multiple instances of this descriptor are present - one per stream. In the case of a rejected stream, the descriptor is empty (see clause 5.18.2.6.1). Table 108b: Message Contents - Session Establishment Update - Delete Stream Ack Session Establishment Update - Remote Addr and Port Known, Through Connect, Bandwidth Change Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 104
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.2.6.1 Session Establishment Update - Delete Stream - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:128 } }, Stream = 2 { Local {}, Remote {} } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 15a: H.248 Message Sequence Example - Session Establishment Update - Delete Stream
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3 Mid-Session Update
|
During an established session changes can be performed on existing connections. Examples of these changes are changes in the remote port, changes in the remote address and port, and changes in bandwidth allocation due to changed codec.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.1 Mid-Session Update - Bandwidth Change
|
This procedure may be used by the MGC when the media plane bandwidth of an established session is modified. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 105 Table 109: Message Contents - Mid-Session Update - Bandwidth Change Mid-Session Update - Bandwidth Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream O Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local O SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 106 Mid-Session Update - Bandwidth Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Bearer Information Media format and type O Bearer Information Bandwidth M Remote O SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Attribute Information RTCP O Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O Table 110: Message Contents - Mid-Session Update - Bandwidth Change Ack Mid-Session Update - Bandwidth Change Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 107
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.1.1 Mid-Session Update - Bandwidth Change - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 1875, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 21608 tcp - b=AS:15 }, Remote { v=0 o=- 0 0 IN IP4 12.34.56.82 s=- t=0 0 c=IN IP4 12.34.56.82 m=- 20032 tcp - b=AS:15 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 16: H.248 Message Sequence Example - Mid-Session Update - Bandwidth Change
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.2 Mid-Session Update - Media Change
|
This procedure may be used by the MGC when the transport and/or media format and/or media type of an established session is modified. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 108 Table 111: Message Contents - Mid-Session Update - Media Change Mid-Session Update - Media Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream O Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 109 Mid-Session Update - Media Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Attribute Information RTCP O Signals O ipnapt/latch O napt O Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O Table 112: Message Contents - Mid-Session Update - Media Change Ack Mid-Session Update - Media Change Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 110
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.2.1 Mid-Session Update - Media Change - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 1875, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 21608 tcp - b=AS:15 }, Remote { v=0 o=- 0 0 IN IP4 12.34.56.82 s=- t=0 0 c=IN IP4 12.34.56.82 m=- 20032 tcp - b=AS:15 } } }, Signals { ipnapt/latch{ napt=RELATCH, stream = 1 } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 17: H.248 Message Sequence Example - Mid-Session Update - Media Change ETSI ETSI TS 183 018 V3.5.2 (2010-01) 111 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { Local { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 21608 tcp - b=AS:15 }, Remote { v=0 o=- 0 0 IN IP4 12.34.56.82 s=- t=0 0 c=IN IP4 12.34.56.82 m=- 20032 tcp - b=AS:15 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 18: H.248 Message Sequence Example - Mid-Session Update - Media Change, No NAT, No change of through connection or policing (sdr)
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.3 Mid-Session Update - Remote Addr/Port Change
|
This procedure may be used by the MGC when the address and/or port of the remote end is modified in an established session. Table 113: Message Contents - Mid-Session Update - Remote Addr/Port Change Mid-Session Update - Remote Addr/Port Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream O Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 112 Mid-Session Update - Remote Addr/Port Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/sam O 5.18.1.1.1 gm/spr O 5.18.1.1.1 gm/sprr O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Local O SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 113 Mid-Session Update - Remote Addr/Port Change H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Attribute Information RTCP O Signals O ipnapt/latch O napt O Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O Table 114: Message Contents - Mid-Session Update - Remote Addr/Port Change Ack Mid-Session Update - Remote Addr/Port Change Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 114
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.3.1 Mid-Session Update - Remote Addr/Port Change - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { LocalControl { mode= SendReceive, ds/dscp = 1D, gm/saf = ON, gm/spf = ON, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000 tman/pol = ON, ipdc/realm = "1" }, Remote { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 20016 RTP/AVP - b=AS:64 } } }, Signals { ipnapt/latch{ napt=RELATCH, stream = 1 } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 19: H.248 Message Sequence Example - Mid-Session Update - Remote Addr/Port Change ETSI ETSI TS 183 018 V3.5.2 (2010-01) 115 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 1 { Remote { v=0 o=- 0 0 IN IP4 16.128.45.10 s=- t=0 0 c=IN IP4 16.128.45.10 m=- 20016 RTP/AVP - b=AS:64 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } Figure 20: H.248 Message Sequence Example - Mid-Session Update - Remote Addr/Port Change, No NAT, No Bandwidth Change 5.18.3.4 Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port This procedure may be used by the MGC when the address and port of the remote end to be used for the added stream are known to the MGC. Table 115: Message Contents - Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream M Local Control M mode M ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 116 Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes gm/esps O gm/lsp O gm/sam O gsm/spr O gsm/sprr O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Statistics O See note Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address= ($ or specific) M Address Information Port=($ or specific) M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Attribute Information RTCP O Signals O ipnapt/latch O napt O Events O adid/ipstop O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 117 Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O NOTE: The MGC may request any statistic within those supported. Table 116: Message Contents - Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port Ack Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream M Local SDP Information Version M SDP Information Session Name M SDP Information Origin M SDP Information Timing M Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M Bearer Information Media format and type O Bearer Information Bandwidth M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 118 5.18.3.4.1 Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port - Examples MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 2 { LocalControl { mode= Inactive, ds/dscp = 1D, gm/saf = ON, gm/spf = ON, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 c=IN IP4 $ m=- $ RTP/AVP - b=AS:128 }, Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:128 } } }, Signals { ipnapt/latch{ napt=LATCH, stream = 2 } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { Media { Stream = 2 { Local { v=0 o=- 0 0 IN IP4 129.192.57.2 s=- t=0 0 c=IN IP4 129.192.57.2 m=- 56858 RTP/AVP - b=AS:128 } } ETSI ETSI TS 183 018 V3.5.2 (2010-01) 119 MGC MG } } } Figure 21: H.248 Message Sequence Example - Mid-Session Update - Add Stream, Remote Addr and Port Known, Select Local Addr and Port 5.18.3.5 Mid-Session Update - Add Stream, Remote Addr and Port Unknown, Select Local Addr and Port This procedure may be used by the MGC when the address and port of the remote end to be used for the added stream are not known to the MGC. Table 117: Message Contents - Mid-Session Update - Add Stream, Remote Addr and Port Unknown, Select Local Addr and Port Mid-Session Update - Add Stream, Remote Addr and Port Unknown, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream M Local Control O mode O ds/dscp O ds/tb O nt/jit O mpls/stack O vlan/tags O vlan/pri O gm/saf O 5.18.1.1.1 gm/spf O 5.18.1.1.1 gm/rsb O gm/esas O gm/lsa O gm/esps O gm/lsp O gm/sam O gsm/spr O gsm/sprr O mgcinfo/db O tman/pdr O tman/mbs O tman/dvt O tman/sdr O tman/pol O ipdc/realm O 5.18.1.1.2 Statistics O See note ETSI ETSI TS 183 018 V3.5.2 (2010-01) 120 Mid-Session Update - Add Stream, Remote Addr and Port Unknown, Select Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Local SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address= ($ or specific) M Address Information Port=($ or specific) M Bearer Information Transport M See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth M Signals O ipnapt/latch O napt O Events O adid/ipstop O dt O dir O g/cause O nt/netfail O nt/qualert O scr/cr O si O dur O per O max O min O nor O rt O typ O val O dev O com O dir O hangterm/thb O timerx O NOTE: The MGC may request any statistic within those supported. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 121 Table 118: Message Contents - Mid-Session Update - Add Stream, Remote Addr and Port Unknown, Select Local Addr and Port Ack Mid-Session Update - Add Stream, Remote Addr and Port Unknown, Select Local and Addr Port Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream M Local SDP Information Version M SDP Information Session Name M SDP Information Origin M SDP Information Timing M Address Type IP4 or IP6 M Address Information IP Address M Address Information Port M Bearer Information Transport M Bearer Information Media format and type O Bearer Information Bandwidth M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 122
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.5.1 Mid-Session Update - Add Stream - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 2 { LocalControl { mode= Inactive, ds/dscp = 1D, gm/rsb = ON, gm/esas = ON, gm/lsa = "[192.10.33.158]", gm/esps = ON, gm/lsp = 3624, mgcinfo/db = 16547/67, tman/pdr = 17500, tman/mbs = 1500, tman/dvt = 300, tman/sdr = 16000, tman/pol = ON, ipdc/realm = "1" }, Local { v=0 c=IN IP4 $ m=- $ RTP/AVP - b=AS:128 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { Media { Stream = 2 { Local { v=0 o=- 0 0 IN IP4 129.192.57.2 s=- t=0 0 c=IN IP4 129.192.57.2 m=- 56858 RTP/AVP - b=AS:128 } } } } } Figure 22: H.248 Message Sequence Example - Mid-Session Update - Add Stream ETSI ETSI TS 183 018 V3.5.2 (2010-01) 123
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.6 Mid-Session Update - Delete Stream
|
This procedure may be used by the MGC when a stream is removed from an established session. Table 119: Message Contents - Mid-Session Update - Delete Stream Mid-Session Update - Delete Stream H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified or Termination ID=* M Media M Stream M Local M Remote M Audit O Media O Stream O Statistics */* O Table 120: Message Contents - Mid-Session Update - Delete Stream Ack Mid-Session Update - Delete Stream Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media O Stream O Statistics O gm/dp O nt/* O rtp/* O rtpad/* O lstat/* O tman/* O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 124
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.3.6.1 Mid-Session Update - Delete Stream - Examples
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = * { Media { Stream = 2 { Local {}, Remote {} } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37, Modify = ip/104/2/541 } } Figure 23: H.248 Message Sequence Example - Mid-Session Update - Delete Stream, No Statistics Required ETSI ETSI TS 183 018 V3.5.2 (2010-01) 125 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = * { Media { Stream = 2 { Local {}, Remote {} } } }, Audit { Media { Stream = 2 { Statistics {*/*} } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { Media { Stream = 2 { Statistics { gm/dp=12, nt/or=80204, nt/os=80204, rtp/pr=1026, rtp/ps=1121 } } } }, Modify = ip/104/2/541 { Media { Stream = 2 { Statistics { gm/dp=38, nt/or=80532, nt/os=80204, nt/dur=958624 rtp/pl=21, rtp/jit=23, rtp/delay=184, rtp/pr=1121, rtp/ps=1026 } } } } } } Figure 24: H.248 Message Sequence Example - Mid-Session Update - Delete Stream, Statistics Required ETSI ETSI TS 183 018 V3.5.2 (2010-01) 126 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 2 { Local {}, Remote {} } } }, Audit { Media { Stream = 2 { Statistics {*/*} } } } }, Modify = ip/104/2/541 { Media { Stream = 2 { Local {}, Remote {} } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { Media { Stream = 2 { Statistics { gm/dp=12, nt/or=80204, nt/os=80204, nt/dur=958624 rtp/pl=21, rtp/jit=23, rtp/delay=184, rtp/pr=1026, rtp/ps=1121 } } } }, Modify = ip/104/2/541 } } Figure 25: H.248 Message Sequence Example - Mid-Session Update - Delete Stream, Statistics Required on one Termination 5.18.3.7 Mid-Session Update - Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port This procedure may be used by the MGC when the address and possibly the port of the remote end is known to the MGC, but the local address and port cannot be assigned due to that the MG shall operate in NA(P)T-less B2BIH mode (see clause 5.17.1.2.4.1). This procedure may be part of the first stage of a two-stage reservation. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 127 Table 120a: Message Contents - Mid-Session Update - Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port Mid-Session Update - Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Request (MGC to MG) Context ID=specified M Termination ID=specified M Media M Stream M Local Control M ipdc/realm O 5.18.1.1.2 Statistics O See note Remote SDP Information Version O SDP Information Session Name O SDP Information Origin O SDP Information Timing O Address Type IP4 or IP6 M Address Information IP Address M Address Information Port O Bearer Information Transport O See note 2 of table 87 Bearer Information Media format and type O Bearer Information Bandwidth O Attribute Information RTCP O Events O hangterm/thb O timerx O NOTE: The MGC may request any statistic within those supported. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 128 Table 120b: Message Contents - Mid-Session Update - Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port Ack Mid-Session Update - Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Modify Reply (MG to MGC) Context ID=specified M Termination ID=specified M 5.18.3.7.1 Mid-Session Update - Add Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port - Examples MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Modify = ip/104/1/37 { Media { Stream = 2 { LocalControl { ipdc/realm = "1" }, Remote { v=0 o=- 0 0 IN IP4 25.196.80.72 s=- t=0 0 c=IN IP4 25.196.80.72 m=- 20000 RTP/AVP - b=AS:128 } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Modify = ip/104/1/37 { } } } Figure 25a: H.248 Message Sequence Example - Add Stream, Remote Addr Known and Port Possibly Known, no Local Addr and Port ETSI ETSI TS 183 018 V3.5.2 (2010-01) 129
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.4 Auditing
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.4.1 Mid-Session Statistics Audit
|
This procedure may be used by the MGC when statistics are audited during an established session. Table 121: Message Contents - Mid-Session Statistics Audit Mid-Session Statistics Audit H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes AuditValue Request (MGC to MG) Context ID=specified M Termination ID=specified or Termination ID=* M Audit M Media M Stream M Statistics */* M Table 122: Message Contents - Mid-Session Statistics Audit Ack Mid-Session Statistics Audit Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes AuditValue Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream M Statistics M gm/dp O nt/* O rtp/* O rtpad/* O lstat/* O tman/* O ETSI ETSI TS 183 018 V3.5.2 (2010-01) 130
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.4.1.1 Mid-Session Statistics Audit - Example
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, AuditValue = * { Audit { Media { Stream = 2 { Statistics {*/*} } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { AuditValue = ip/104/1/37 { Media { Stream = 2 { Statistics { gm/dp=12, nt/or=80204, nt/os=80204, rtp/pr=1026, rtp/ps=1121, } } } }, AuditValue = ip/104/2/541 { Media { Stream = 2 { Statistics { gm/dp=38, nt/or=80532, nt/os=80204, nt/dur=958624 rtp/pl=21, rtp/jit=23, rtp/delay=184, rtp/pr=1121, rtp/ps=1026, } } } } } } Figure 26: H.248 Message Sequence Example - Mid-Session Statistics Audit
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.4.2 Mid-Session MGC Info Audit
|
This procedure may be used by the MGC when the MGC Info is audited during an established session. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 131 Table 122a: Message Contents - Mid-Session MGC Info Audit Mid-Session Statistics Audit H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes AuditValue Request (MGC to MG) Context ID=specified M Termination ID=specified M Audit M Media M Stream M Local Control M mgcinfo/db M Table 122b: Message Contents - Mid-Session MGC Info Audit Ack Mid-Session Statistics Audit Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes AuditValue Reply (MG to MGC) Context ID=specified M Termination ID=specified M Media M Stream M Local Control M mgcinfo/db M
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.4.2.1 Mid-Session MGC Info Audit - Example
|
MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { AuditValue = ip/104/2/541 { Audit { Media { Stream = 2 { LocalControl {mgcinfo/db} } } } } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { AuditValue = ip/104/2/541 { Media { Stream = 2 { LocalControl { mgcinfo/db=12345678 } } } } } } Figure 26a: H.248 Message Sequence Example - Mid-Session MGC Info Audit ETSI ETSI TS 183 018 V3.5.2 (2010-01) 132
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.5 Notification of MG Events
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.5.1 Notification of IP Media Stop
|
This procedure may be used by the MG when IP media stop has been detected. Table 123: Message Contents - Notification of IP Media Stop Detection of IP Media Stop H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Notify Request (MG to MGC) Context ID=specified M Termination ID=specified M Observed Events M adid/ipstop M Table 124: Message Contents - Notification of IP Media Stop Ack Detection of IP Media Stop Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Notify Reply (MGC to MG) Context ID=specified M Termination ID=specified M MGC MG 1 <----------------------------------------------------- MEGACO/3 <MG> Transaction = 12 { Context = 1234 { Notify = ip/23/1/424 { ObservedEvents = 3276 { adid/ipstop } } } } 2 -----------------------------------------------------> MEGACO/3 <MGC> Reply = 12 { Context = 1234 { Notify = ip/23/1/424 } } Figure 27: H.248 Message Sequence Example - Notification of IP Media Stop ETSI ETSI TS 183 018 V3.5.2 (2010-01) 133
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.18.5.2 Notification of Hanging Termination
|
This procedure may be used by the MG when hanging termination has been detected. Table 125: Message Contents - Notification of Hanging Termination Detection of Hanging Termination H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Notify Request (MG to MGC) Context ID=specified M Termination ID=specified M Observed Events M hangterm/thb M Table 126: Message Contents - Notification of Hanging Termination Ack Detection of Hanging Termination p Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Notify Reply (MGC to MG) Context ID=specified M Termination ID=specified M MGC MG 1 <----------------------------------------------------- MEGACO/3 <MG> Transaction = 12 { Context = 1234 { Notify = ip/23/1/424 { ObservedEvents = 3276 { hangterm/thb } } } } 2 -----------------------------------------------------> MEGACO/3 <MGC> Reply = 12 { Context = 1234 { Notify = ip/23/1/424 } } Figure 28: H.248 Message Sequence Example - Notification of Hanging Termination
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.