hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.18.5.3 Notification of Statistic Conditional Reporting | This procedure may be used by the MG when condition for statistics reporting has been detected. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 134 Table 127: Message Contents - Notification of Statistic Conditional Reporting Detection of Statistic Conditional Reporting 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 scr/cr M si M val M Table 128: Message Contents - Notification of Statistic Conditional Reporting Ack Detection of Statistic Conditional Reporting 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 { scr/cr {si="nt/os",val=10000} } } } } 2 -----------------------------------------------------> MEGACO/3 <MGC> Reply = 12 { Context = 1234 { Notify = ip/23/1/424 } } Figure 29: H.248 Message Sequence Example - Notification of Statistic Conditional Reporting |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.18.6 Delete Session/Termination | 5.18.6.1 Delete Session/Termination This procedure may be used by the MGC when a session is terminated. The MGC may request all or none of the collected stream statistics to be returned in the response. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 135 Table 129: Message Contents - Delete Session/Termination Delete Session/Termination - Delete Termination H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Subtract Request (MGC to MG) Context ID=specified M Termination ID=specified or Termination ID=* M Audit O Table 130: Message Contents - Delete Session/Termination Ack Delete Session/Termination - Delete Termination Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Subtract 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 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.18.6.1.1 Delete Session/Termination - Examples | MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Subtract = ip/104/2/541 { Audit {} } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Subtract = ip/104/2/541 { } } } } Figure 30: H.248 Message Sequence Example - Delete Session/Termination - Delete Single Termination, Statistics Not Required ETSI ETSI TS 183 018 V3.5.2 (2010-01) 136 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Subtract = ip/104/2/541 { } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Subtract = ip/104/2/541 { Media { Stream = 1 { 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 } } Stream = 2 { Statistics { gm/dp=28, nt/or=60532, nt/os=60204, nt/dur=858624 rtp/pl=11, rtp/jit=13, rtp/delay=164, rtp/pr=1021, rtp/ps=1006 } } } } } } Figure 31: H.248 Message Sequence Example - Delete Session/Termination - Delete Single Termination, Statistics Required on all dependent streams ETSI ETSI TS 183 018 V3.5.2 (2010-01) 137 MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Subtract = * { } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Subtract = ip/104/2/541 { Media { Stream = 1 { 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 } } } }, Subtract = ip/38/1/112 { Media { Stream = 1 { 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 32: H.248 Message Sequence Example - Delete Session/Termination - Delete All Terminations in a Context, Statistics Required MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, Subtract = * { Audit {} } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Subtract = ip/104/2/541, Subtract = ip/38/1/112 } } Figure 33: H.248 Message Sequence Example - Delete Session/Termination - Delete All Terminations in a Context, Statistics Not Required ETSI ETSI TS 183 018 V3.5.2 (2010-01) 138 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.18.6.2 Delete Session/Termination - Wildcarded Reply | This procedure may be used by the MGC when session is terminated. The MGC requests a compact response. Table 131: Message Contents - Delete Session/Termination - Wildcarded Reply Delete Session/Termination - Delete Session H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Subtract Request (MGC to MG) Context ID=specified M Termination ID= * M See note Audit M NOTE: The Subtract Request will be wildcarded W. Table 132: Message Contents - Delete Session - Wildcarded Reply Ack Delete Session/Termination - Delete Session Ack H.248 Command Descriptor Descriptor Descriptor Properties, Events, Statistics, Signals Connection Point Address, IP address information and Bearer Information Support Notes Subtract Reply (MG to MGC) Context ID=specified M Termination ID=* M |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.18.6.2.1 Delete Session - Wildcarded Reply - Examples | MGC MG 1 -------------------------------------> MEGACO/3 [102.168.55.54] Transaction = 1 { Context = 38924 { Priority = 9, W-Subtract = * { Audit {} } } } 2 <------------------------------------- MEGACO/3 bs_MP_4/1 Reply = 1 { Context = 38924 { Subtract = * } } Figure 34: H.248 Message Sequence Example - Delete Session - Wildcarded Reply |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19 Non-Session Related Use Cases | The following clauses are based on clauses 10.1 to 10.19 from the 'TISPAN NGN Release 2; H.248 Non-Call Related Procedures and Management System Interaction' (TS 183 025 [i.2]). Not all of the Use Cases in this TR are used by this profile and some modifications and notes have been added in this profile. Table 133 denotes whether each of the Use Cases from the source document is Mandatory, Optional or Not Used. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 139 Table 133: Support of Use Cases from TS 183 025 [i.2] Use Case Support Enable MG (at MGC) Mandatory Enable MG (at MG): Cold Boot Mandatory Enable MG (at MG): Warm Boot Mandatory Enable MGC Optional Disable MG (Graceful) (MGC) Optional Disable MG (Graceful) (MG) Optional Disable MG (Immediate) (MGC) Mandatory Disable MG (Immediate) (MG) Mandatory Disable MGC Mandatory Enable Termination (MGC) Not Used (see note) Enable Termination (MG) Not Used (see note) Disable Termination (Graceful) (MGC) Not Used (see note) Disable Termination (Graceful) (MG) Not Used (see note) Disable Termination (Immediate) (MGC) Not Used (see note) Disable Termination (Immediate) (MG) Mandatory MG Failure and Recovery Mandatory MG Termination Failure and Recovery Mandatory MGC Failure and Recovery Mandatory User Plane Failure Mandatory MGC-MG Control Association Failure and Recovery Mandatory MG Overload Optional MGC Overload Not Used MGC Handoff Optional MGC Re-Direct Optional MG Failover Not Used Change of MG Resources Mandatory NOTE: For this profile, only ephemeral terminations are applicable. Each Use Case consists of a sequence of one or more procedures. The procedures may be mandatory or optional for each use case and must be executed in the sequence order shown in the use case. The procedure names are denoted by the use of UPPER CASE letters. The procedures are described in clause 5.20. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.1 Enable MG | This management primitive is applicable to both the MGC and MG. It is recommended that this primitive is initially sent to the MGC and subsequently to the MG. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.1.1 Enable MG (at MGC) | This use case is triggered by management action that results in a MG being enabled at the MGC. Table 134: Enable MG (at MGC) Seq. Num. Description Support 1 There are no H.248 procedures associated with this action. The MGC simply awaits a registration from the MG (see clause 5.19.1.2). Mandatory ETSI ETSI TS 183 018 V3.5.2 (2010-01) 140 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.1.2 Enable MG (at MG) | This use case is triggered by management action that results in a MG being brought into service. The MG will have been provisioned with the identity/address of one or more MGC(s). The H.248 procedures are dependent on whether the MG undergoes a cold or warm boot and are as follows: |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.1.2.1 Enable MG (at MG): Cold Boot | Table 135: Enable MG (at MG): MG Cold Boot Seq. Num. Description Support 1 The MG registers with one of its (pre-provisioned) MGCs using the MG REGISTRATION (COLD BOOT) procedure. This step enables the H.248 protocol version to be negotiated as well as the support of any H.248 profiles. Mandatory 2 In the event of there being no response to the registration request, the MG follow the procedures of section 11.5 of ITU-T Rec. H.248.1 [1]. Optional 3 On completion of the initial registration procedure, the MGC assumes that all physical terminations are in the NULL context and there are no existing ephemeral terminations. Thus no connection related audits are required to be performed (see note). Mandatory 4 The MGC may optionally perform a PACKAGES AUDIT procedure in order to determine the MG support of any optional packages in a mutually supported profile. Optional 5 The MGC may optionally audit ROOT properties (in any mandatory and optional packages) in the MG via the AUDIT ROOT PROPERTIES procedure. Optional 6 The MGC may optionally set properties and events (on any mandatory and optional packages in the profile) in the MG on ROOT level via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure. Optional 7 The MG may optionally inform the MGC of the state of its physical terminations via a MG TERMINATION AVAILABLE/MG TERMINATION UNAVAILABLE procedure. Not Used 8 The MGC may optionally Audit the state of the physical terminations if it cannot be assumed that the state is in-service or out-of-service via the AUDIT TERMINATION STATE procedure. Not Used 9 The MGC should not deblock associated circuits toward peer nodes before it has determined the true service state of the MG's circuits by one of the two procedures above. Not Used NOTE: For this profile, physical terminations are not applicable. MG Registration (Cold Boot) Ack MG Registration (Cold Boot) MGC MG Packages Audit Packages Audit Ack Set ROOT Term Events/Properties Set ROOT Term Events/Properties Ack (optional) (optional) Audit ROOT Properties Audit ROOT Properties Ack (optional) Figure 35: Procedures for Enable MG (Cold Boot) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 141 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.1.2.2 Enable MG (at MG): Warm Boot | Table 136: Enable MG (at MG): MG Warm Boot Seq. Num. Description Support 1 The MG registers with one of its (pre-provisioned) MGCs using the MG RESTORATION procedure This step enables the H.248 protocol version to be negotiated as well as the support of any H.248 profiles. Mandatory 2 In the event of there being no response to the registration request, the MG follow the procedures of section 11.5 of H.248.1. Optional 3 On completion of the re-registration procedure, the MGC does not assume that all physical terminations are in the NULL context and there may be existing ephemeral terminations (see note). Mandatory 4 The MGC may optionally perform a PACKAGES AUDIT procedure in order to determine the MG support of any optional packages in a mutually supported profile. Optional 5 The MGC may optionally audit ROOT properties (in any mandatory and optional packages) in the MG via the AUDIT ROOT PROPERTIES procedure. Optional 6 The MGC may optionally set properties and events (in any mandatory and optional packages in the profile) in the MG on ROOT level via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure. Optional 7 The MGC may optionally perform a CONTEXT AUDIT procedure to determine the active contexts and connected terminations on the MG. Mandatory 8 The MG may optionally inform the MGC of the state of its terminations via a MG TERMINATION AVAILABLE/MG TERMINATION UNAVAILABLE procedure. MG TERMINATION AVAILABLE: Not used, MG TERMINATION UNAVAILABLE: Optional 9 The MGC may optionally Audit the state of its terminations if it cannot be assumed that the state is in-service or out-of-service via the AUDIT TERMINATION STATE procedure. Not used 10 The MGC should not deblock associated circuits toward peer nodes before it has determined the true service state of the MG's circuits by one of the two procedures above. Not used NOTE: For this profile, physical terminations are not applicable. MG Restoration Ack MG Restoration MGC MG Packages Audit Packages Audit Ack Set ROOT Term Events/Properties Set ROOT Term Events/Properties Ack (optional) (optional) Context Audit Context Audit Ack MG Termination Unavailable MG Termination Unavailable Ack (optional) Audit ROOT Properties Audit ROOT Properties Ack (optional) Figure 36: Enable MG (at MG): MG Warm Boot ETSI ETSI TS 183 018 V3.5.2 (2010-01) 142 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.2 Enable MGC | This management primitive is applicable only to the MGC and results in a MGC being brought into service. The MGC will optionally have been provisioned with the identities H.248 message identifier (MID) and possibly the IP addresses of transport address of the H.248 control association of its MGs. Table 137: Enable MGC Seq. Num. Description Support 1 The MGC may optionally check on the availability of its MGs via the CHECK MG AVAILABILITY procedure. This is only possible if the MGC is aware of the pre-provisioned IP address of the MG and UDP transport is used. Optional 2 If the MG is available, the MGC may optionally request the MG to register via the MGC INITIATED SERVICE RESTORATION procedure which causes the MG to initiate the MG RE-REGISTRATION (RESTART) procedure. Optional 3 If the MG is available, the MGC may optionally audit ROOT properties in the MG via the AUDIT ROOT PROPERTIES procedure. Optional 4 If an MG is available, the MGC may optionally set properties and events in the MG on ROOT level via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure. Optional 5 If an MG is available, the MGC may optionally perform a CONTEXT AUDIT procedure to determine the active contexts and connected terminations on the MG. Optional 6 If an MG is available, the MGC may optionally clean up hanging contexts/terminations via a WILDCARDED SUBTRACT. Optional 7 If an MG is available, the MGC may optionally check on the service state of the physical terminations on the MG service via the AUDIT TERMINATION STATE procedure. Not used 8 The MGC should not deblock associated circuits toward peer nodes before it has determined the true service state of the MG's circuits. Not used |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.3 Disable MG (Graceful) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a MG being taken out of service gracefully. It is recommended that the network management system performs a Disable MG (Graceful) command to the MGC. The one scenario where a Disable MG (Graceful) command to the MG makes sense is for an Access Gateway in order to inhibit new calls being initiated toward the MGC during the graceful period - and even in this case a MGC would be able to reject any originating calls appropriately. In addition, the management primitive typically has no equivalent of the H.248 ServiceChangeDelay - rather the acceptable period during which all affected calls/connections ought to be removed is determined by the operator. Therefore when mapping into H.248, a default value for the ServiceChangeDelay period would need to be applied. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.3.1 Disable MG (Graceful) (at MGC) | Table 138: Disable MG (Graceful) (at MGC) Seq. Num. Description Support 1 The MGC inhibits any new calls/connections to the MG and allows existing calls/connections to expire naturally/normally. Optional 2 In the event of new calls originating from the MG (e.g. an AGW), the MGC would handle them appropriately via call related procedures (e.g. reject the call attempt and connect a failure indication). Not Used 3 When all calls have been released, the management system is informed. In this profile the MGC INITIATED SERVICE CANCELLATION procedure is not supported. Optional ETSI ETSI TS 183 018 V3.5.2 (2010-01) 143 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.3.2 Disable MG (Graceful) (at MG) | Table 139: Disable MG (Graceful) (at MG) Seq. Num. Description Support 1 The MG informs the MGC via the MG SERVICE CANCELLATION (GRACEFUL) procedure. This procedure enables the MG to specify a timer (the ServiceChangeDelay) during which it is anticipated that all existing calls/connections on that MG will expire normally. Mandatory 2 If applicable, the MG may prevent new originating calls being offered to the MGC. Not Used 3 The MGC inhibits any new calls/connections to the MG and allows existing calls/connections to expire naturally/normally. Mandatory 4 At the end of the ServiceChangeDelay period, any remaining connections are left hanging on the MG. Mandatory 5 At the end of the ServiceChangeDelay period, the MGC force releases any remaining calls that have not expired naturally (but does not signal to the MG since the control association is now assumed to be down). Optional Figure 37: Disable MG (Graceful) (at MG) |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.4 Disable MG (Immediate) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a MG being taken out of service immediately. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.4.1 Disable MG (Immediate) (at MGC) | Table 140: H.248 Procedures - Disable MG (Immediate) (at MGC) Seq. Num. Description Support 1 The MGC inhibits any new calls/connections to the MG and force releases existing calls/connections. Mandatory 2 In the event of new calls originating from the MG (e.g. an AGW), the MGC would handle them appropriately via call related procedures (e.g. reject the call attempt and connect a failure indication). Not Used 3 When all calls have been released, the management system is informed. In this profile the MGC INITIATED SERVICE CANCELLATION procedure is not supported. Mandatory MG Service Cancellation (Graceful) MGC MGW MG Service Cancellation ( Graceful) Ack (expiry of graceful timer) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 144 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.4.2 Disable MG (Immediate) (at MG) | Table 141: H.248 Procedures - Disable MG (Immediate) (at MG) Seq. Num. Description Support 1 The MG informs the MGC via the MG SERVICE CANCELLATION (IMMEDIATE) procedure. Mandatory 2 The MG responds to the management system (see note). Mandatory 3 On receipt of the MG SERVICE CANCELLATION (IMMEDIATE) message, the MGC force releases any calls/connections associated with that MG. However, the connections cannot be removed on the MG due to the control association being down. Mandatory NOTE: That existing connections are still hanging on the MG. Since connections may be left hanging, it is recommended that the DISABLE MG (Immediate) primitive is applied firstly at the MGC and then at the MG. Figure 38: H.248 Procedures - Disable MG (Immediate) (at MG) |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.5 Disable MGC | This primitive is sent to a MGC and results in a MGC being taken out of service. Table 142: H.248 Procedures - Disable MGC Seq. Num. Description Support 1 Prior to the MGC being disabled, it is recommended that the MGC inform its dependent MGs to move their control associations to an alternative MGC via the MGC HANDOFF procedure (clause 5.20.13) or that all dependent MGs are disabled prior to disabling the MGC (clause 5.19.4). Optional |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.6 Enable Termination | Void. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.7 Disable Termination (Graceful) | Void. MGC MG MG Service Cancellation (Immediate) MG Service Cancellation (Immediate) Ack ETSI ETSI TS 183 018 V3.5.2 (2010-01) 145 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.8 Disable Termination (Immediate) (at MG) | This use case is triggered by management action that results in a MG termination being taken out of service immediately. The following H.248 procedures are performed: Table 142b: H.248 Procedures - Disable Termination (Immediate) (at MG) Seq. Num. Description Support 1 The MG informs the MGC via the MG TERMINATION UNAVAILABLE procedure. Mandatory 2 The MGC acknowledges the message. The MGC will then proceed to force releases all affected calls/connections including subtracting appropriate terminations on the MG. (see note) Mandatory NOTE: In this profile, this may be a wildcarded subtract at the interface level. Figure 38a: H.248 Procedures - Disable Termination (Immediate) (at MG) |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.19.9 MG Failure and Recovery | This use case is triggered by a hardware/software failure on the MG. Table 143: H.248 Procedures - MG Failure and Recovery Seq. Num. Description Support Notes 1 If possible, the MG informs the MGC via the MG SERVICE CANCELLATION (IMMEDIATE) procedure. The MGC force releases all affected calls. Optional 2 On recovering, the MG restarts and informs the MGC. The procedures of clause 5.19.1.2 are applicable. Mandatory Figure 39: H.248 Procedures - MG Failure and Recovery MG Service Cancellation (Immediate) MGC MG MG Service Cancellation (Immediate) Ack (MG recovery) See 5.1 9.1.2 (optional) MGC MGW MG Termination Unavailable MG Termination Unavailable Ack ETSI ETSI TS 183 018 V3.5.2 (2010-01) 146 5.19.10 MG Termination Failure and Recovery This use case is triggered by a hardware/software failure on the MG termination (e.g. loss of synchronization on an E1). Table 144: H.248 Procedures - MG Termination Failure and Recovery Seq. Num. Description Support 1 The MG informs the MGC via the MG TERMINATION UNAVAILABLE procedure. The MGC force releases any affected calls (and subtracts related terminations on the MG). Mandatory 2 On the fault being cleared, the MG informs the MGC via the MG TERMINATION AVAILABLE procedure. Not Used MG Termination Unavailable MGC MG MG Termination Unavailable Ack Figure 40: H.248 Procedures - MG Termination Failure and Recovery 5.19.11 MGC Failure and Recovery This use case is triggered by a hardware/software failure on the MGC. Table 145: H.248 Procedures - MG Termination Failure and Recovery Seq. Num. Description Support Notes 1 During the outage, the procedures associated with the MG detecting the loss of the control link are applicable (see clause 5.19.13). Mandatory 2 When the MGC recovers, the procedures of clause 5.19.2 are applicable. Mandatory 5.19.12 User Plane Failure This use case is triggered by the MG detecting loss of RTP on an ephemeral termination. Table 146: H.248 Procedures - User Plane Failure Seq. Num. Description Support 1 During the establishment of the connection, the MGC is assumed to have armed the MG to report an appropriate ObservedEvent which would be associated with user plane failure. There are a number of events that could be used for this purpose (e.g. nt/netfail, nt/qalert (see annex E.11 of ITU-T Rec. H.248.1 [1]), g/cause (see annex E.1 of ITU-T Rec. H.248.1 [1], etc.). Mandatory 2 The MG detects loss of user plane data on one or more streams and notifies the MGC via the USER PLANE FAILURE procedure. The MG should avoid sending an avalanche of notifications where loss of user plane data is detected simultaneously across multiple ephemeral terminations. Mandatory 3 On being informed of user plane failure, the MGC would typically remove the affected stream(s) and/or force release the affected call and subtract the related terminations. Mandatory ETSI ETSI TS 183 018 V3.5.2 (2010-01) 147 MGC MG User Plane Failure User Plane Failure Ack Figure 41: H.248 Procedures - User Plane Failure 5.19.13 MGC-MG Control Association Failure and Recovery If UDP transport is used to convey the H.248 signalling, then the control association is monitored via the Inactivity Package (see ITU-T Recommendation H.248.14 [13]). In this case, it is assumed that the MGC has previously initiated the inactivity timer on the MG via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure (see clause 5.19.1). If SCTP transport is used, then the control association is monitored via SCTP procedures (which are out of scope of the present document) and the H.248 application layer is informed by the SCTP layer when the SCTP association goes down/comes up. Table 147: H.248 Procedures - MGC-MG Control Association Failure and Recovery Seq. Num. Description Support 1 For UDP transport, the MGC should endeavour to send at least one message to the MG during the period of the inactivity timer. If there are no call related messages, the MGC may use the CHECK MG AVAILABILITY procedure. If this procedure fails, the MGC shall periodically re-attempt the procedure to check if the control association is once more OK. Optional 2 For UDP transport, on expiry of the inactivity timer, if the MG has received a message (including an acknowledgment) from the MGC during the inactivity timer period, then the MG resets the inactivity timer. Optional 3 For UDP transport, on expiry of the inactivity timer, if the MG has not received a message (including an acknowledgment) from the MGC during the inactivity timer period, then the MG initiates the ROOT EVENT NOTIFICATION procedure to inform the MGC of the inactivity timer expiry. Optional 4 For UDP transport, if the ROOT EVENT NOTIFICATION procedure is successfully completed, then the MG resets the inactivity timer. Optional 5 For UDP transport, if no acknowledgement is received, then the control association is deemed to be down after normal H.248 retransmissions have occurred. Optional 6 For UDP transport, the MG now attempts to re-establish the lost control link via the MG LOST COMMUNICATION (DISCONNECTED) procedure. If no acknowledgement is received (and normal H.248 retransmissions have occurred), then the MG attempts to establish an alternative control association via the MG LOST COMMUNICATION (FAILOVER) procedure. Optional 7 For SCTP transport, on being informed by the SCTP layer that the SCTP association is now up, the MG re-establishes the H.248 control association via the MG LOST COMMUNICATION (DISCONNECTED) or MG LOST COMMUNICATION (FAILOVER) procedure dependent on whether the new SCTP association is to the same MGC as previous or not. Optional 8 When the control association is re-established, the MGC may optionally re-synchronize its data with the MG via the AUDIT ROOT PROPERTIES, CONTEXT AUDIT and AUDIT TERMINATION STATE procedures. Optional (see note 1) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 148 Seq. Num. Description Support 9 When the control association is re-established, the MG shall inform the MGC of the state of its terminations via the MG TERMINATION AVAILABLE / MG TERMINATION UNAVAILABLE procedure if any changes occurred which it was unable to report during the control association outage. Optional (see note 2) 10 When the control association is re-established, commands that were buffered during the outage period may be sent. Optional NOTE 1: The AUDIT TERMINATION STATE procedure shall not be used. NOTE 2: Only MG TERMINATION UNAVAILABLE is sent due to there being only ephemeral terminations. | Check MG Availability Ack Check MG Availability MGC MGW MG Lost Communication (Disconnected) Root Event Notification (Inactivity timer ) UDP transport (inactivity timer running) (timer expiry & reset) (timer expiry) MG Lost Communication (Failover) MG Lost Communication (Failover) Context Audit Context Audit Ack (start inactivity timer) MG Lost Communication (Disconnected) | Root Event Notification (Inactivity timer) Root Event Notification (Inactivity timer) MG Termination Unavailable MG Termination Unavailable Ack Audit Root Properties Audit Root Properties Ack ETSI ETSI TS 183 018 V3.5.2 (2010-01) 149 Figure 42: H.248 Procedures - MGC-MG Control Association Failure and Recovery 5.19.14 MG Overload This use case is triggered by the MG entering an overloaded state. It is assumed that the MGC has previously armed the MG for notification of overload via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure (see clause 5.19.1). Table 148: H.248 Procedures - MG Overload Notification Seq. Num. Description Support 1 The MG is pushed into overload by excessive session related activity. The MG informs the MGC of its overloaded condition via the ROOT EVENT NOTIFICATION (MG Overload) procedure. On receipt of the notification, the MGC takes appropriate action to reduce the offered load to the MG. Optional Figure 43: H.248 Procedures - MG Overload Notification Procedure 5.19.15 MGC Overload Void. WC – I’ve ad MGC MG W MG Lost Communication (Disconnected) or (Failover) MG Lost Communication (Disconnected) or (Failover) Ack STCP Transport (SCTP association failure) (SCTP association OK) Context Audit Context Audit Ack | MG Termination Unavailable MG Termination Unavailable Ack Audit Root Properties Audit Root Properties Ack MGC MGW ROOT Event Notification (MG Overload) ROOT Event Notification Ack ETSI ETSI TS 183 018 V3.5.2 (2010-01) 150 5.19.16 MGC Hand-Off This use case is triggered by management action that results in the MGC moving an existing control link association to an alternative MGC. This could be done as a load balancing exercise or as a pre-condition to taking a MGC out of service. Table 149: H.248 Procedures - MGC Handoff after MG Registration Seq. Num. Description Support 1 The MGC requests its MGs to move existing control associations to an alternative MGC via the MGC HANDOFF procedure. On receipt of this message, the MG then forms a new control association to the specified alternate MGC via the MG RE-REGISTRATION (HAND-OFF) procedure. Optional MGC Hand-Off MGC MG MGC Hand-Off Ack MG Re-Registration (Hand-Off) MG Re-Registration (Hand-Off) Ack Figure 44: H.248 Procedures - MGC Handoff after MG Registration 5.19.17 MGC Re-Direct This use case is triggered by an MGC rejecting a registration request from an MG and providing an alternative MGC address in the response. This could be done as a load balancing exercise. The following H.248 procedures are performed. Table 150: H.248 Procedures - MGC Re-Direct Seq. Num. Description Support 1 The MGC on receipt of a registration request, provides an alternative MGC identity/address in the registration response. This is shown in the REGISTRATION REDIRECT procedure. The MG subsequently repeats the original registration request to the alternate MGC. Optional MGC MG MG Registration Registration Re-Direct Figure 45: H.248 Procedures - MGC Re-Direct 5.19.18 MG Failover Void. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 151 5.19.19 Change of MG Resources This use case is triggered by management action that results in a change to MG resources on an In-Service MG such that the applied change does not result in a Service Change message, but does require the MGC to be notified of the applied change via a H248 NOTIFY message. The MGC has previously armed the necessary event via the SET ROOT EVENTS/PROPERTIES procedure (see clause 5.19.1). Table 150a: H.248 Procedures - Change of MG Resources Seq. Num. Description Support 1 The MG's resources are changed via Management Configuration and the MG has been previously armed to inform the MGC of the related change. The MG informs the MGC of the change in its resources via the ROOT EVENT NOTIFICATION procedure. Mandatory ROOT Event Notification MGC MG ROOT Event Notification Ack Figure 45a: Change to MG Resources Procedure |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20 Session Independent Procedures (Command Level Details) | Table 151: Call Independent Procedures - References Procedure Support Clause MG Registration (Cold Boot) (note) Mandatory 5.20.1 MG Restoration (see note) Mandatory 5.20.2 Packages Audit Optional 5.20.3 Context Audit Mandatory 5.20.4 MG Termination Available Not Used 5.20.5 MG Termination Unavailable Mandatory 5.20.6 Audit Termination State Not Used 5.20.7 Set ROOT Termination Events/Properties Optional 5.20.8 MGC Initiated Service Restoration Optional 5.20.9 Check MG Availability Optional 5.20.10 MG Service Cancellation (Graceful) Optional 5.20.11 MG Service Cancellation (Immediate) Mandatory 5.20.12 MGC Hand-Off Optional 5.20.13 MG Re-Registration (Hand-Off) (note) Optional 5.20.14 MG Termination OOS Graceful Not Used 5.20.15 MGC Overload Notification Not Used 5.20.16 Registration Redirect Optional 5.20.17 User Plane Failure Mandatory 5.20.18 ROOT Event Notification Optional 5.20.19 MG Lost Communication (Disconnected) Mandatory 5.20.20 MG Lost Communication (Failover) Optional 5.20.21 MG Redundant Takeover (Primary) Not Used 5.20.22 Void N/A 5.20.23 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 152 Procedure Support Clause MG Re-Registration (Restart) Optional 5.20.24 Wildcarded Subtract Mandatory 5.20.25 MG Redundant Takeover (Secondary) Not Used 5.20.26 MGC Initiated Service Cancellation Not Used 5.20.27 Audit Service State Not Used 5.20.28 Audit ROOT Properties Optional 5.20.29 NOTE: These procedures are initiated using H.248 version 1 and may be used to negotiate a higher protocol version. All other procedures are initiated using the negotiated protocol version. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.1 MG Registration (Cold Boot) | Table 152: Message Contents - MG Registration (Cold Boot) and MG Registration (Cold Boot) Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Registration (Cold Boot) MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to RESTART. Mandatory Reason This information element indicates the reason for service change. This is set to 901 - "Cold Boot". Mandatory Service Change Profile Indicates the name of a supported H.248 profile. For this profile this is set to 'ETSI_BGF/3'. Optional Protocol Version Indicates the highest H.248 version supported by the MG - if other than 1. For this profile this is set to version 3. Optional MG Registration (Cold Boot) Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory Protocol Version If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the protocol version proposed by the MG is supported by the MGC, this parameter may be included. Note that if the lowest protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). For this profile this is set to version 3. Optional Service Change Profile This information element indicates the profile (name and version) supported by the MGC if different to that proposed by the MG. For this profile this is set to 'ETSI_BGF/3'. Optional An example message exchange would be: • Transaction=1002{Context=- {ServiceChange=ROOT{Services{Method=Restart, Reason="901", Profile=ETSI_BGF/3, Version=3}}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 153 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.2 MG Restoration | Table 153: Message Contents - MG Restoration and MG Restoration Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Restoration MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to RESTART. Mandatory Reason This information element indicates the reason for service change. This is set to 900 ("Service Restored") or 902 ("Warm Boot). For this profile the reason values 916 ("Packages Change" ),917 ("Capabilities Change") and 918 "Cancel Graceful") are not supported. Mandatory Service Change Profile Indicates the name of a supported H.248 profile. For this profile this is set to 'ETSI_BGF/3'. Optional Protocol Version Indicates the highest H.248 version supported by the MG - if other than 1. For this profile this is set to version 3. Optional MG Restoration Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory Protocol Version If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the protocol version proposed by the MG is supported by the MGC, this parameter may be included. If the lowest protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). For this profile this is set to version 3. Optional Service Change Profile This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG. For this profile this is set to "ETSI_BGF/3". Optional An example message exchange would be: • Transaction=1002{Context=- {ServiceChange=ROOT{Services{Method=Restart, Reason="902", Profile=ETSI_BGF/3, Version=3}}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 154 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.3 Packages Audit | This procedure is typically performed against the ROOT termination, in which case the MG returns all supported packages. It is also possible for the MGC to request a packages audit against other than the ROOT termination (e.g. a circuit termination) in which case the MG returns the sub-set of the packages that are applicable to the termination type. However, it is recommended that a packages audit be performed on the ROOT termination since the MGC can be expected to know how the returned set of packages ought to be used in relation to its different termination types. Table 154: Message Contents - Packages Audit and Packages Audit Ack procedures Command/ Response Initiated Information Element Name Information Element Description Information element required Packages Audit MGC Context This information element indicates the H.248 context for the command. Set to NULL. M Command This is the H.248 Command. Set to AUDIT VALUE. M Termination This information element indicates the H.248 termination for the command. This is set to ROOT. M Audit packages This is the Audit Descriptor requesting "Packages". M Packages Audit Ack MG Context As received. M Command As received. M Termination As received. M Package List The list of supported packages. M An example message exchange would be: • Transaction=1002{Context=- { AuditValue=ROOT{ Audit{Packages}}}}. • Reply=1002{Context=-{AuditValue = ROOT {Packages { g-2,root-2, nt-1, …….etc.}}}}. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.4 Context Audit | This procedure is invoked by the MGC to check/determine the list of active contexts and related terminations on the MG. There are a number of variations to this audit dependent on the amount of information available to the MGC prior to the audit (e.g. context identity known or termination naming scheme known, etc.). A MGC may choose to use one or a combination of these variations dependent on its specific audit requirements. Table 155: Context Audit and Context Audit Ack procedure support Procedure Support Reference Termination ID known - Context known - Termination ID partly known M table 156 Context List - ETSI ETSI TS 183 018 V3.5.2 (2010-01) 155 Table 156: Message Contents - Context Audit and Context Audit Ack procedures (termination id partly known) Command/ Response Initiated Information Element Name Information Element Description Information element required Context Audit MGC Context This information element indicates the H.248 context for the command. Set to ALL or NULL. Mandatory (see note) Command This is the H.248 Command. Set to AUDIT VALUE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to a partially wildcarded termination, e.g. ip/0/*. Mandatory (see note) Audit Information This is the Audit Descriptor requesting the appropriate information to be returned. Not Used Context Audit Ack MG Context One or more active contexts associated with the wildcarded termination identity. Mandatory (see note) Command As received. Mandatory Termination(s) For each returned context, one or two matching terminations. Mandatory Audited Information The information requested. (per termination). Not Used NOTE: In the event of there a mismatch between the wildcarded termination and specified context, an error 431 would be returned. An example message exchange would be: • Transaction=1002{Context=* {AuditValue=ip/15/*{ Audit{ }}}}. • Reply=1002{Context=12{AuditValue = ip/15/1/204, AuditValue = ip/7/2/12}, Context=15{AuditValue= ip/15/2/5, AuditValue = ip/203/1/6}, Context=23{AuditValue= ip/15/1/17, AuditValue = ip/37/2/95}}. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.5 MG Termination Available | Void. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 156 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.6 MG Termination Unavailable | Table 157: Message Contents - MG Termination Unavailable and MG Termination Unavailable Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Termination Unavailable MG Context This information element indicates the H.248 context for the command. Set to specific or ALL. For this profile Context=NULL is not supported. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to a specific termination identity or a partially wildcarded identity (i.e. specifying the "interface" part of the termination ID and wildcarding the "group" and "Id" parts) or a wholly wildcarded identity (i.e. ip/*). Mandatory Method This information element indicates the method for service change. This is set to FORCED. Mandatory Reason This information element indicates the reason for service change. This is set to 904 ("Termination Malfunction") or 905 ("Termination Taken OOS") or 906 ("Loss of Lower Layer Connectivity"), or 907 ("Transmission Failure") or 910 ("Media Capability Failure") or 912 ("Mux Capability Failure") or 913 ("Signal Capability Failure") or 914 ("Event Capability Failure" or 915 ("State Loss"). Mandatory MG Termination Unavailable Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Transaction=1002{Context=12345 { ServiceChange=ip/15/1/204{ Services{Method=Forced, Reason="905"}}}}. • Reply=1002{Context=12345{ServiceChange = ip/15/1/204}}. OR • Transaction=1002{Context=* { W- ServiceChange=ip/*/1/*{ Services{Method=Forced, Reason="905"}}}}. • Reply=1002{Context=*{ServiceChange = ip/*/1/*}}. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.7 Audit Termination State | Not Used. Background: • This is related to MG warm boot (see clause 5.19.1.2.2) and MG restoration (see clause 5.20.2) respectively. Should a termination go out of service during the period the H.248 control association is down, then, after the H.248 control association is established again, this shall be reported according to use case (clause 5.19.10) following the procedure according to clause 5.20.6. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 157 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.8 Set ROOT Termination Events/Properties | Table 158: Message Contents - Set ROOT Termination Events/Properties and Set ROOT Termination Events/Properties Ack procedures Command/ Response Initiated Information Element Name Information Element Description Information Element Required Set ROOT Termination Events/Properties MGC Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to MODIFY. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory ROOT Properties These are the ROOT level properties - e.g. "Normal MGC Execution Time". Optional ROOT Events These are the ROOT level events - e.g. notification of expiry of inactivity timer, notification of overload, etc. Optional Set ROOT Termination Events/Properties Ack MG Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Transaction=1002{Context=- { Modify=ROOT{ Media {TerminationState { root/MGCProvisionalResponseTimerValue=700, root/MGCOriginatedPendingLimit=3, root/NormalMGCExecutionTime = 3000, root/MGProvisionalResponseTimerValue=3000, root/MGOriginatedPendingLimit=3, seg/MGCMaxPDUSize=1000, seg/MGCSegmentationTimerValue=20}}, Events{ocp/mg_overload, it/ito{mit=3000}, ipra/arc}}}}. • Reply=1002{Context=-{Modify = ROOT}}. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.20.9 MGC Initiated Service Restoration | Table 159: MGC Initiated Service Restoration and MGC Initiated Service Restoration Ack Command/ Response Initiated Information element name Information element required Information element description MGC Initiated Service Restoration MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for service change. This is set to RESTART. Reason M This information element indicates the reason for service change. This is set to 900 ("Service Restored") or 901 ("Cold Boot"). MGC Initiated Service Restoration Ack MG Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 158 An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason="901"}}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}}. 5.20.10 Check MG Availability Table 160: Message Contents - Check MG Availability and Check MG Availability Ack procedures Command/ Response Initiated Information Element Name Information Element Description Information Element Required Check MG Availability MGC Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to AUDIT VALUE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Check MG Availability Ack MG Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Transaction=1002{Context=- { AuditValue=ROOT{ Audit{}}}}. • Reply=1002{Context=-{AuditValue = ROOT}}. 5.20.11 MG Service Cancellation (Graceful) Table 161: Message Contents - MG Service Cancellation (Graceful) and MG Service Cancellation (Graceful) Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Service Cancellation (Graceful) MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to GRACEFUL. Mandatory Reason This information element indicates the reason for service change. This is set to 908 - "MG Impending Failure". For this profile reason value 905 "Termination OOS" is not supported. Mandatory Service Change Delay Indicates the period before which the MG will go out of service. Optional MG Service Cancellation (Graceful) Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory ETSI ETSI TS 183 018 V3.5.2 (2010-01) 159 An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Graceful, Reason="908", Delay=600}}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}. 5.20.12 MG Service Cancellation (Immediate) Table 162: Message Contents - MG Service Cancellation (Immediate) and MG Service Cancellation (Immediate) Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Service Cancellation (Immediate) MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to FORCED. Mandatory Reason This information element indicates the reason for service change. This is set to 905 - "Termination Taken OOS". Mandatory MG Service Cancellation (Immediate) Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Forced, Reason="905"}}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}. 5.20.13 MGC Hand-Off Table 163: Message Contents - MGC Hand-Off and MGC Hand-Off Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MGC Hand-Off MGC Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to HANDOFF. Mandatory Reason This information element indicates the reason for service change. This is set to 903 - "MGC Directed Change". Mandatory Alternate MGC Id This is the alternate MGC Identity to which the control association should be moved. Mandatory MG Hand- Off Ack MG Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory ETSI ETSI TS 183 018 V3.5.2 (2010-01) 160 An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Handoff, Reason="903", MgcIdToTry=1.2.3.4}}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}. 5.20.14 MG Re-Registration (Hand-Off) Table 164: Message Contents - MG Re-Registration(Hand-Off) and MGC Re-Registration (Hand-Off) Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Re- Registration (Hand-Off) MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to HANDOFF. Mandatory Reason This information element indicates the reason for service change. This is set to 903 - "MGC Directed Change". Mandatory Service Change Profile This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG For this profile this is 'ETSI_BGF/3'. Optional Protocol Version Indicates the highest common H.248 version supported by the MG - if other than 1. For this profile this is version 3. Optional MG Re- Registration (Hand-Off) Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory Service Change Profile This information element indicates the profile supported by the MGC. For this profile this is 'ETSI_BGF/3'. Optional Protocol Version If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the protocol version proposed by the MG is supported by the MGC, this parameter may be included. If the lowest protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). For this profile this is version 3. Optional An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Handoff, Reason="903", Profile=ETSI_BGF/3, Version=3}}}}. • Reply=1002{Context=-{ServiceChange = ROOT {Services { Version=3}}}}. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 161 5.20.15 MG Termination OOS Graceful Void. 5.20.16 MGC Overload Notification Void. 5.20.17 Registration Redirect Table 165: Message Contents - Registration Redirect Command/ Response Initiated Information Element Name Information Element Description Information Element Required Registration MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to any apart from FORCED/GRACEFUL. Mandatory Reason This information element indicates the reason for service change. This is set dependent on the METHOD. Mandatory Service Change Profile Indicates the name of a supported H.248 profile. For this profile this is 'ETSI_BGF/3'. Optional Protocol Version Indicates the highest H.248 version supported by the MG - if other than 1. For this profile this is version 3. Optional Registration Redirect MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory Protocol Version If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the protocol version proposed by the MG is supported by the MGC, this parameter may be included. If the lowest protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). For this profile this is version 3. Optional Service Change Profile This information element indicates the profile (name and version) supported by the MGC if different to that proposed by the MG. For this profile this is 'ETSI_BGF/3'. Optional Alternate MGC Id This element enables the MGC to inform the MG that it should re-direct its Service Change to an alternative address. The MG will now repeat the MG Registration (Cold Boot) procedure to this alternate address. Mandatory ETSI ETSI TS 183 018 V3.5.2 (2010-01) 162 An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason="901", Profile=ETSI_BGF/3, Version=3}}}}. • Reply=1002{Context=-{ServiceChange = ROOT {Services { Version=3, MGCIdToTry=1.2.3.4}}}}. 5.20.18 User Plane Failure Table 166: Message Contents User Plane Failure and User Plane Failure Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required User Plane Failure MG Context This information element indicates the H.248 context for the command. Set to a specific value. Mandatory Command This is the H.248 Command. Set to NOTIFY. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to a specific ephemeral termination identity or a partially wildcarded identity (i.e. specifying the "interface" part of the termination ID and wildcarding the "group" and "Id" parts) or a wholly wildcarded identity (i.e. ip/*). Mandatory User Plane Failure This information element indicates that a failure in the user plane has been detected (e.g. nt/netfail, g/cause, adid/ipstop, etc.). Mandatory User Plane Failure Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Transaction=1002{Context=1 { Notify=ip/15/3/2{ ObservedEvents{g/cause}}}}. • Reply=1002{Context=1 {Notify = ip/15/3l/2}}. OR • Transaction=1002{Context=* { W- Notify=ip/*/31/*{ ObservedEvents{g/cause}}}}. • Reply=1002{Context=1 {Notify = ip/*/3l/*}}. OR • Transaction=1002{Context=1 { Notify=ip/15/3/2{ ObservedEvents{nt/netfail}}}}. • Reply=1002{Context=1 {Notify = ip/15/3l/2}}. OR • Transaction=1002{Context=* { W- Notify=ip/*/31/*{ ObservedEvents{nt/netfail}}}}. • Reply=1002{Context=1 {Notify = ip/*/3l/*}}. OR • Transaction=1002{Context=1 { Notify=ip/15/3/2{ ObservedEvents{adid/ipstop}}}}. • Reply=1002{Context=1 {Notify = ip/15/3l/2}}. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 163 OR • Transaction=1002{Context=* { W- Notify=ip/*/31/*{ ObservedEvents{adid/ipstop}}}}. • Reply=1002{Context=1 {Notify = ip/*/3l/*}}. 5.20.19 ROOT Event Notification Table 167: Message Contents - ROOT Event Notification and ROOT Event Notification Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required ROOT Event Notification MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to NOTIFY. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Notified ROOT Event This information element indicates the detected ROOT event (e.g. inactivity timer expiry or MG Overload or Change of IP Realm Availability etc.). Mandatory ROOT Event Notification Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Notification of inactivity timeout from monitoring the availability of the Control Association and/or MGC: Transaction=1002{Context=- { Notify=ROOT{ ObservedEvents{it/ito}}}}. OR • Notification of MG overload: Transaction=1002{Context=- { Notify=ROOT{ ObservedEvents{ocp/mg_overload}}}}. OR • Notification of newly available realms, i.e. the list of IP realms that have become available (here two new realms with name "400" and "401"): Transaction=1002{Context=- { Notify=ROOT{ ObservedEvents{ipra/arc{nar=["400","401"]}}}}}. • Reply by MGC on above notification requests: Reply=1002{Context=-{Notify = ROOT }}. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 164 5.20.20 MG Lost Communication (Disconnected) Table 168: Message Contents - MG Lost Communication (Disconnected) and MG Lost Communication (Disconnected) Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Lost Communication (Disconnected) MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to DISCONNECTED. Mandatory Reason This information element indicates the reason for service change. This is set to 900 "Service Restored". Mandatory MG Lost Communication (Disconnected) Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Disconnected, Reason="900"}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}. 5.20.21 MG Lost Communication (Failover) The MG attempts to establish a new control association using its list of pre-provisioned MGC identities. The MG cycles though its list until a successful response is received. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 165 Table 169: Message Contents - MG Lost Communication (Failover) and MG Lost Communication (Failover) Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Lost Communication (Failover) MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to FAILOVER. Mandatory Reason This information element indicates the reason for service change. This is set to 909 - "MGC Impending Failure". Mandatory Service Change Profile Indicates the name of a supported H.248 profile. For this profile this is 'ETSI_BGF/3'. Optional Protocol Version Indicates the highest H.248 version supported by the MG - if other than 1. For this profile this is version 3. Optional MG Lost Communication (Failover) Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory Service Change Profile This information element indicates the profile (name and version) supported by the MGC if different to that proposed by the MG For this profile this is 'ETSI_BGF/3'. Optional Protocol Version If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the protocol version proposed by the MG is supported by the MGC, this parameter may be included. If the lowest protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). For this profile this is version 3. Optional An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Failover, Reason="909", Profile=ETSI_BGF/3, Version=3}}}}. • Reply=1002{Context=-{ServiceChange = ROOT {Services { Version=3}}}}. 5.20.22 MG Redundant Takeover (Primary) Void. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 166 5.20.23 Void 5.20.24 MG Re-Registration (Restart) Table 170: Message Contents - MG Re-Registration (Restart) and MG Re-Registration (Restart) Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required MG Re- Registration (Restart) MG Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to SERVICE CHANGE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Method This information element indicates the method for service change. This is set to RESTART. Mandatory Reason This information element indicates the reason for service change. This is set to the value received from the MGC during the MGC INITIATED SERVICE RESTORATION procedure - see clause 5.20.9. Mandatory MG Re- Registration (Restart) Ack MGC Context As received. Mandatory Command As received. Mandatory Termination As received. Mandatory An example message exchange would be: • Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason="901"}}}}. • Reply=1002{Context=-{ServiceChange = ROOT}}. 5.20.25 Wildcarded Subtract Table 171: Message Contents - Wildcarded Subtract and Wildcarded Subtract Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required Wildcarded Subtract MGC Context This information element indicates the H.248 context for the command. Set to ALL. Mandatory Command This is the H.248 Command. Set to SUBTRACT or W-SUBTRACT. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ALL or a partially wildcarded identity (e.g. ip/2/*). Mandatory Wildcarded Subtract Ack MG Context As received (if W prefix used), else a list of specific context IDs. Mandatory Command As received. Mandatory Termination As received (if W prefix used), else a list of specific IDs Mandatory An example message exchange would be: • Transaction=1002{Context=* { W-Subtract=*{ Audit{}}}}. • Reply=1002{Context=*{Subtract= *}}. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 167 An example with wildcarding at group level would be: • Transaction=1002{Context=* { W-Subtract=ip/5/*{ Audit{}}}}. • Reply=1002{Context=*{Subtract= ip/5/*}}. An example with wildcarding at interface level would be: • Transaction=1002{Context=* { W-Subtract=ip/*/5/*{ Audit{}}}}. • Reply=1002{Context=*{Subtract= ip/*/5/*}}. 5.20.26 MG Redundant Takeover (Secondary) Void. 5.20.27 MGC Initiated Service Cancellation Void. 5.20.28 Audit Service State Void. 5.20.29 Audit ROOT Properties Table 172: Message Contents - Audit ROOT Properties and Audit ROOT Properties Ack Command/ Response Initiated Information Element Name Information Element Description Information Element Required Audit ROOT Properties MGC Context This information element indicates the H.248 context for the command. Set to NULL. Mandatory Command This is the H.248 Command. Set to AUDIT VALUE. Mandatory Termination This information element indicates the H.248 termination for the command. This is set to ROOT. Mandatory Audit Properties This is the list of ROOT properties required to be audited by the MGC. Mandatory Audit ROOT Properties ACK MG Context As received Mandatory Command As received. Mandatory Termination As received Mandatory Root Properties The returned list of ROOT properties as requested by the MGC. Mandatory An example message exchange would be: • Audit Request Transaction=1002{Context=- { AuditValue=ROOT{ Audit{Media{TerminationState{root/*}, TerminationState{ipra/ar}, TerminationState{seg/*}}}}}}. • Audit Reply with realms named "20", "21", "22", "23", "24", and "100" available in the MG Reply=1002{Context=-{AuditValue = ROOT { Media{TerminationState {root/maxNumberOfContexts=1000, root/maxTerminationsPerContext=2, root/normalMGExecutionTime=2, root/normalMGCExecutionTime=2, root/MGProvisionalResponseTimerValue=5, root/MGCProvisionalResponseTimerValue=5, root/MGCOriginatedPendingLimit=10, root/MGOriginatedPendingLimit=10, seg/MGMaxPDUSize=1000, seg/MGSegmentationTimerValue=20, ipra/ar=["20","21","22","23","24","100"]}}}}}. OR ETSI ETSI TS 183 018 V3.5.2 (2010-01) 168 • Audit Reply with no realms available in the MG Reply=1002{Context=-{AuditValue = ROOT { Media{TerminationState {root/maxNumberOfContexts=1000, root/maxTerminationsPerContext=2, root/normalMGExecutionTime=2, root/normalMGCExecutionTime=2, root/MGProvisionalResponseTimerValue=5, root/MGCProvisionalResponseTimerValue=5, root/MGCOriginatedPendingLimit=10, root/MGOriginatedPendingLimit=10, seg/MGMaxPDUSize=1000, seg/MGSegmentationTimerValue=20, ipra/ar=[""]}}}}}. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 169 Annex A (informative): Void ETSI ETSI TS 183 018 V3.5.2 (2010-01) 170 Annex B (informative): Comparison between ES 283 018 V1.1.4 (Ia Profile Version 1) and TS 102 333 (GCP) B.1 General The H.248 Profile defined in ES 283 018 V1.1.4 [22] supports similar functionality than the Gate Control Profile defined in TS 102 333 [i.1]; however, it is important to note that the "H.248 Profile for the Ia Interface" is a new profile. This annex provides an overview of the main differences between them. B.2 Differences between TS 102 333 (GCP) and ES 283 018 V1.1.4 (Ia Profile Version 1) Table B.1 provides an overview of the differences between the Gate Control Protocol and the H.248 Profile Version 1 for the Ia Interface. Table B.1: Difference Between TS 102 333 [i.1] and ES 283 018 [22] (V1.1.4) Topic TS 102 333 [i.1] (Gate Control Protocol) ES 283 018 V1.1.4 [22] (Ia Profile Version 1) Required H.248 Version H.248 Version 2 H.248 Version 3 QoS monitoring Supported Not Supported Supported with "latching" capability only Hosted NAT traversal Supported with "relatching" capabilities Connection Model (see note) A gate is represented by an ephemeral termination. Hence, a bidirectional active session requires two open gates (one at each side of the border gateway) A gate is represented by a pair of ephemeral terminations (one at each side of the bolder gateway). A bidirectional active session requires two gates (one per direction) sharing the same pair of terminations Termination ID structure ip/<interface>/<id> ip/<group>/<interface>/<id> Transport mandates the support of SCTP, TCP or UDP Recommends SCTP, UDP as optional Encoding Text and Binary Text SDP Usage (s=, t=) Specifies how the s= and t= lines should be set Provides no guidance on this Security IPSec as an option Does not assume a security mechanism TimeStamps in ServiceChange and Notify commands Required Not required Transaction Timers Range is specified as being 100 ms and 5 s No range specified Packages Generic Package Version 1 Version 2 Root Package Version 1 Version 2 NAT traversal package Supported Not Supported IP NAPT traversal package Not Supported Supported Congestion Handling package Supported Not Supported Quality Alert Ceasing Optional Not Supported Overload Control Optional Not Supported EMP Package Optional Not Supported Gate Recovery Information Supported Not Supported MGC Information Package Not Supported Optional Segmentation Package Not Applicable Optional NOTE: This difference in modelling does not have any impact on the external behaviour of the border gateway. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 171 Annex C (informative): Comparison with Ia Profile Versions 1 and 2 C.1 General The H.248 Profile defined in the present document is the upversioned Profile as defined in ES 283 018 V2.7.1 [32]. This annex provides an overview of the main differences between the three profile versions. C.2 Differences between ES 283 018 V1.1.4 (Ia Profile Version 1) and ES 283 018 V2.7.1 (Ia Profile Version 2) Table C.1 provides an overview of the differences between both profiles. Table C.1: Difference between ES 283 018 [22] V1.1.4 (Ia Profile Version 1) and ES 283 018 [32] V2.7.1 (Ia Profile Version 2) Topic ES 283 018 [22] V1.1.4 (Ia Profile Version 1) ES 283 018 [32] V2.7.1 (Ia Profile Version 2) QoS monitoring Not Supported Basic support via H.248 statistics (see clause 5.17.1.6). TerminationID structure ip/<group>/<interface>/<id> ip/<group>/<interface>/<id> Field element "interface" is off-loaded from the semantic of "IP realm/domain" indication. SDP Usage: "s=", "t=" and "o=" lines Provides no guidance on this Guidance provided in clause 5.16. SDP Usage "b=" line The bandwidth-value value defines the required protocol layer 2 (e.g. Ethernet) bandwidth for the specific H.248 Stream The bandwidth-value value defines the IP layer bandwidth for the specific H.248 Stream. Semantic for ignoring SDP information. Usage of "ignore" Replacement of "ignore" by text describing the handling of received SDP at the BGF for both media aware and media agnostic cases. Packages RTP Package Not Supported Optional Version 1. IP Domain Connection Package Not Supported Version 1. Media Gateway Overload Control Package Not Supported Optional Version 1. Application Data Inactivity Package Not Supported Optional Version 1. Hanging Termination Package Not Supported Optional Version 1. Statistics Conditional Reporting Not Supported Optional Version 1. Procedures Session Independent Procedures (also known as Call Independent Procedures or Non-Call Related Procedures) Implicit (see note 1) link to TS 183 025 [i.2]. Explicit link to TS 183 025 [i.2] by clause 5.17.2. Additional details in clause 5.19. Call-independent procedures for ES 283 018 [22] 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. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 172 Topic ES 283 018 [22] V1.1.4 (Ia Profile Version 1) ES 283 018 [32] V2.7.1 (Ia Profile Version 2) IP Domain/Realm Indication Via semantical overloading of the TerminationID (see note 2). Explicit protocol element: via ipdc/realm property (H.248.41; see clause 5.17.1.10). BGF Resource Reservation One-stage mechanism Additional support of a two-stage resource reservation (see clause 5.17.1.11). RTCP Handling High-level description in clause 5.17.1.1. Additional information by clause 5.17.1.7. NOTE 1: The TR was still in work when Ia profile version 1 was published. NOTE 2: ITU-T Rec. H.248.41 [16] was still in work when Ia profile version 1 was published. C.3 Differences between ES 283 018 V2.7.1 (Ia Profile Version 2) and TS 183 018 V3.5.1 (Ia Profile Version 3) Table C.2 provides an overview of the differences between both profiles. Table C.2: Difference between ES 283 018 [32] V2.7.1 (Ia Profile Version 2) and the present document (Ia Profile Version 3) Topic ES 283 018 [32] V2.7.1 (Ia Profile Version 2) TS 183 018 V3.5.1 (Ia Profile Version 3) Packages IP Realm Availability Not Supported Optional Version 1 RTP Application Data Not Supported Optional Version 1 Latch Statistics Not Supported Optional Version 1 Statistic Conditional Reporting Version 1 only Optional Version 2 Differentiated Services Version 1 Version 2 Traffic Policing Statistics Not Supported Optional Version 2 Procedures Normalization of H.248.11- based overload control loop "Termination-level MG overload control": Event notification triggered by each incoming ADD.request command "Context-level MG overload control": Optional normalization: Event notification triggered only by first incoming ADD.request command per Context Termination name: field element <Group> identifier value range: 0 to 255 value range: 0 to 65,535 Transport-protocol aware mode yes additional values for SDP "m=" line "Transport Protocol" element (clause 5.15) Session Independent Procedures Based on TR 183 025 [i.22] v2.0.0 Based on TS 183 025 [i.2] v2.5.0 Topology hinding function yes yes, plus explicit description ETSI ETSI TS 183 018 V3.5.2 (2010-01) 173 Annex D (informative): Void ETSI ETSI TS 183 018 V3.5.2 (2010-01) 174 Annex E (informative): Void ETSI ETSI TS 183 018 V3.5.2 (2010-01) 175 Annex F (informative): Void ETSI ETSI TS 183 018 V3.5.2 (2010-01) 176 Annex G (informative): Void ETSI ETSI TS 183 018 V3.5.2 (2010-01) 177 Annex H (informative): Void ETSI ETSI TS 183 018 V3.5.2 (2010-01) 178 Annex I (informative): Bibliography • ITU-T Recommendation H.248.4 (2000): "Gateway control protocol: Transport over Stream Control Transmission Protocol (SCTP)". • ITU-T H.Sup6 (Supplement 6 to ITU-T H-series Recommendations) (2006): "Control load quantum for decomposed gateways". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 179 Annex J (informative): Change history Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 29-05-08 17bTD079r1 013 D WI-03145 H.248 Ia Profile Version 3 - Editorials 3.1.0 3.1.1 29-05-08 17bTD080r1 014 D WI-03145 H.248 Ia Profile Version 3 - § 2 References - Update 3.1.0 3.1.1 30-05-08 17bTD081r1 015 C WI-03145 H.248 Ia Profile Version 3 - Termination Name field <Group> - Range Extension 3.1.0 3.1.1 30-05-08 17bTD082r1 016 D WI-03145 H.248 Ia Profile Version 3 Illustration of BGF modes of operation - New annex proposed 3.1.0 3.1.1 30-05-08 17bTD083r2 017 D WI-03145 H.248 Ia Profile Version 3 - NA(P)T-less mode of operation - Update 3.1.0 3.1.1 30-05-08 17bTD186r3 018 B WI-03145 H.248 Ia Profile Version 3 New annex "Illustration of NAPT modes of operation" 3.1.0 3.1.1 30-05-08 17bTD084r1 019 C -03145 H.248 Ia Profile Version 3 H.248.11-based MG Overload Control - Event 3.1.0 3.1.1 30-05-08 17bTD085r2 020 F WI-03145 H.248 Ia Profile Version 3 annex F - Examples for Byterate Estimations 3.1.0 3.1.1 30-05-08 17bTD086r2 021 B WI-03145 H.248 Ia Profile Version 3 Optional Support of Application-level Statistics 3.1.0 3.1.1 30-05-08 17bTD087r2 022 B WI-03145 H.248 Ia Profile Version 3 Support Latch Statistics Package 3.1.0 3.1.1 30-05-08 17bTD088r1 023 D WI-03145 H.248 Ia Profile Version 3 RTCP Handling Package- Clarification of Package Usage Details 3.1.0 3.1.1 30-05-08 17bTD089r1 024 F WI-03145 H.248 Ia Profile Version 3 IP realm availability status - Update 3.1.0 3.1.1 30-05-08 17bTD090r1 025 D WI-03145 H.248 Ia Profile Version 3 Rules for mandatory and optional package elements - Update 3.1.0 3.1.1 30-05-08 17bTD219r1 026 F Alignment with Mandatory/Optional Clarification 3.1.0 3.1.1 30-05-08 17bTD091r1 027 F WI-03145 H.248 Ia Profile Version 3 Implicit Filtering due to Latching - Update / Comment: Additional editorial changes as agreed in WG3 session also applied. 3.1.0 3.1.1 30-05-08 17bTD185r1 028 F WI-03145 H.248 Ia Profile Version 3 Revision of annex D.2 'Aspects of filter interaction' 3.1.0 3.1.1 01-06-08 17bTD093r3 029 B WI-03145 H.248 Ia Profile Version 3 SDP "m=" line elements - Field "Transport Protocol" 3.1.0 3.1.1 30-05-08 17bTD094r1 030 D WI-03145 H.248 Ia Profile Version 3 5.17.1.9 Media Inactivity - Editorials 3.1.0 3.1.1 30-05-08 17bTD095r3 031 D WI-03145 H.248 Ia Profile Version 3 Profile Comparison - Update of annex C 3.1.0 3.1.1 29-05-08 17bTD137r2 032 D WI03145 - CR Sys Man Align 3.1.0 3.1.1 30-05-08 17bTD138r2 033 D Correction of introductory text in clause 5.19 3.1.0 3.1.1 29-05-08 17bTD139r2 034 D Errors in Clause 5.20.14 3.1.0 3.1.1 31-05-08 17bTD141r1 035 D Editorial corrections 3.1.0 3.1.1 31-05-08 17bTD142r1 036 F Address type included in command level details / Comment: Those changes are not displayed as "tracked changes" in output draft due to deficiency in MS Word. All ocurrances of c= lines with IP addresses in 5.20 now also include IP version. 3.1.0 3.1.1 31-05-08 17bTD145r2 037 B Replace H.248.47 by H.248.47 Revision 1 3.1.0 3.1.1 31-05-08 17bTD147r4 038 B media-path coupled QoS signalling from and to BGF 3.1.0 3.1.1 31-05-08 17bTD217r1 039 F Clarification of Definition of "Ignore" 3.1.0 3.1.1 02-07-08 18WTD067r2 040 F Clarification of Definition of "Ignore" (Continued) 3.1.1 3.1.2 02-07-08 18WTD068r1 041 F Clarification of RTCP Address 3.1.1 3.1.2 02-07-08 18WTD109r1 042 F Error in clauses 5.20.1, 5.20.2, 5.20.14, 5.20.17 and 5.20.21 3.1.1 3.1.2 03-07-08 18WTD215r2 043 F Updates for Title and Abbreviations 3.1.1 3.1.2 02-07-08 18WTD217r1 044 F Update of provisioned Property values 3.1.1 3.1.2 03-07-08 18WTD220r1 045 D Annex F.3 - Update 3.1.1 3.1.2 03-07-08 18WTD221r3 046 F Annex F.2 - Update 3.1.1 3.1.2 03-07-08 18WTD222r1 047 F Unsymmetrical Remote Network Addresses - Update of § 5.17.1.1.2 and Annex H.2.1 3.1.1 3.1.2 03-07-08 18WTD223r1 048 D Editorial update of § 5.17.1.5 Bandwidth control 3.1.1 3.1.2 03-07-08 18WTD224r1 049 D Update of § 5.17.2.1 Relation to TR 183 025 3.1.1 3.1.2 03-07-08 18WTD225r1 050 F Update of § 5.16 - Support of "a=ptime" 3.1.1 3.1.2 03-07-08 18WTD270r1 051 D SignalsDescriptor correction 3.1.1 3.1.2 02-07-08 18WTD279r2 052 F Update of § 5.20.6 3.1.1 3.1.2 07-08 TB approval of CRs 040 to 052 3.1.2 3.2.0 25-09-08 18bTD064r1 053 F WI-03145 H.248 Ia Profile Version 3 - Clause 2: Update of References 3.2.0 3.2.1 25-09-08 18bTD065r1 054 F WI-03145 H.248 Ia Profile Version 3 - Annex C: Editorial Updates 3.2.0 3.2.1 25-09-08 18bTD066r1 055 F WI-03145 H.248 Ia Profile Version 3 - Clause 5.14.2.11: Update of Inactivity Timer Package specification 3.2.0 3.2.1 25-09-08 18bTD068r1 056 F WI-03145 H.248 Ia Profile Version 3 - Support of DiffServ Package version 2 3.2.0 3.2.1 25-09-08 18bTD069r1 057 F WI-03145 H.248 Ia Profile Version 3 - Support of H.248 statistics for Traffic Policing (IP byte-rate policing) 3.2.0 3.2.1 25-09-08 18bTD070r2 058 A WI-03145 H.248 Ia Profile Version 3 Clause 5.14.2.9: Update of VLAN Package specification 3.2.0 3.2.1 25-09-08 18bTD146r2 059 A Correction to 5.20.7 3.2.0 3.2.1 25-09-08 18bTD150r2 060 A Editorial IPDC Realm 3.2.0 3.2.1 25-09-08 18bTD163r2 061 F WI-03145 H.248 Ia Profile Version 3 - Topology Hiding Function (THF) in IP Media-/Bearer-Path 3.2.0 3.2.1 25-09-08 18bTD164r2 062 F WI-03145 H.248 Ia Profile Version 3 - Analysis and taxonomy of NA(P)T modes and check against Ia profile capabilities 3.2.0 3.2.1 25-09-08 18bTD165r1 063 F WI-03145 H.248 Ia Profile Version 3 - More NA(P)T examples for Annex H 3.2.0 3.2.1 24-09-09 18bTD232r1 064 C Availability of Realms 3.2.0 3.2.1 24-09-08 18bTD233r1 065 D Editorial corrections 3.2.0 3.2.1 24-09-08 18bTD234r1 066 C Clarification of Transport aware and agnostic Behavior 3.2.0 3.2.1 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 180 Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 25-09-08 Table renumbering 3.2.1 3.2.2 17-11-08 CRs 053 to 066 TB approved at TISPAN#19 and clean-up by ETSI Secretariat 3.2.2 3.3.0 25-11-08 19bTD063r1 067 F Addition of GW Status Change to Non-Call Related Procedures 3.3.0 3.3.1 25-11-08 19bTD065r1 068 F Change to annex C.2 regarding SDP "ignore" and alignment of annex C.3 3.3.0 3.3.1 26-11-08 19bTD078r1 069 C Clarification of control of media aware and media agnostic modes 3.3.0 3.3.1 20-01-09 19tTD105r2 070 F Clarification of Table 89 3.3.1 3.3.2 19-01-09 19tTD106r2 071 D Clarification of reference to nt/os and nt/or 3.3.1 3.3.2 20-01-09 19tTD129r2 072 D Improvement to text in clause 5.17.1.7.1.3 3.3.1 3.3.2 20-01-09 19tTD130r2 073 D Inconsistency of format of heading titles 3.3.1 3.3.2 20-01-09 19tTD131r2 074 F Missing Refereces in Ia v3 3.3.1 3.3.2 20-01-09 19tTD132r2 075 F Error in table 49 3.3.1 3.3.2 20-01-09 19tTD133r2 076 F Change to table 62 3.3.1 3.3.2 20-01-09 19tTD134r2 077 D Error in table 79 3.3.1 3.3.2 20-01-09 19tTD135r3 078 F Error in table 80 3.3.1 3.3.2 21-01-09 19tTD136r2 079 D Removal of Informative Annexes 3.3.1 3.3.2 21-01-09 19tTD200r1 080 F Addition of procedture of Mid-Session Update - Remote Addr and Port Change 3.3.1 3.3.2 25-02-09 20WTD154r1 081 F Clarification of latching of streams with multiple flows 3.3.2 3.3.3 25-02-09 20WTD155r1 082 F Removal of RSVP package 3.3.2 3.3.3 25-02-09 20WTD204r1 083 F H.248 Ia Profile Version 3 - Corrections for Table 5 on Group/interface relationship 3.3.2 3.3.3 25-02-09 20WTD111r1 084 F Error in table 48 3.3.2 3.3.3 25-02-09 20WTD112r1 085 F Clarification in clause 5.19.2 3.3.2 3.3.3 25-02-09 20WTD113r2 086 F Clarification in clause 5.19.13 3.3.2 3.3.3 25-02-09 20WTD114r1 087 F Correction / clarification regarding wildcarded subtracts 3.3.2 3.3.3 25-02-09 20WTD133r1 088 F Correction ofd errors - mirror CR from Ia v2 3.3.2 3.3.3 25-02-09 20WTD160r1 089 F Editorial modification of procedure of Mid-Session Update 3.3.2 3.3.3 25-02-09 20WTD207r1 090 F H.248 Ia Profile Version 3 - Missing reference to Border Guideway guidelines 3.3.2 3.3.3 10-03-09 CRs 067 to 090 TB approved at TISPAN#20 3.3.3 3.4.0 17-03-09 20bTD039r1 091 D Resolving editor's note in 5.14.2.18 3.4.0 3.4.1 17-03-09 20bTD040r1 092 F Resolving editor's note in 5.6.1.1.1.1 3.4.0 3.4.1 17-03-09 20bTD041r1 093 F Resolving editor's notes AVPF and L4 agnostic mode 3.4.0 3.4.1 17-03-09 20bTD042r2 094 F Clarifciation of usage of session dependent procedures 3.4.0 3.4.1 18-03-09 20bTD043r1 095 F Clarification of descriptors used in Notify 3.4.0 3.4.1 18-03-09 20bTD044r1 096 D Resolving editor's note on differences to Ia v2 3.4.0 3.4.1 18-03-09 20bTD045r1 097 F Resolving editor's note on THF 3.4.0 3.4.1 18-03-09 20bTD046r1 098 F Resolving editor's note on NA(P)T-less mode 3.4.0 3.4.1 18-03-09 20bTD51r1 099 D Clarification of 1-stage resource reservation 3.4.0 3.4.1 18-03-09 20bTD079r1 100 F Error in clause 5.8.5 3.4.0 3.4.1 18-03-09 20bTD080r1 101 F Errors in clause 5.8.8 3.4.0 3.4.1 18-03-09 20bTD081r1 102 F Error in clause 5.17.1.6 3.4.0 3.4.1 18-03-09 20bTD082r2 103 F Errors in clause 5.18 3.4.0 3.4.1 18-03-09 20bTD083r1 104 F Errors in clause 5.18.1.1.1 3.4.0 3.4.1 18-03-09 20bTD084r1 105 F Errors in clause 5.19.4.2/5.19.9 3.4.0 3.4.1 18-03-09 20bTD085r1 106 F Error in clause 5.20.4 3.4.0 3.4.1 18-03-09 20bTD086r1 107 F Error in clause 5.20.29 3.4.0 3.4.1 18-03-09 20bTD087r1 108 F Corrections due to various packages being consented by ITU-T SG16 in Jan/Feb 2009. 3.4.0 3.4.1 18-03-09 20bTD088r1 109 F Error in table 49 3.4.0 3.4.1 18-03-09 20bTD089r1 110 F Errors in table 142 3.4.0 3.4.1 18-03-09 20bTD162r2 111 F New procedure in 5.18 to cover stream deletion during session establishment. 3.4.0 3.4.1 09-06-09 20WTD104r1 112 F Header caption alignments in clause 5.18. 3.4.1 3.4.2 09-06-09 21WTD105r1 113 F Error in table 5. 3.4.1 3.4.2 09-06-09 21WTD106r3 114 F Addition of SDP o/s/t lines to tables in clause 5.18 3.4.1 3.4.2 09-06-09 21WTD107r2 115 F Miscellaneoue correctioins. Typos corrected and changes applied to 5.18 and 5.20 to ensure that all package properties/events / signals / stats are cited. 3.4.1 3.4.2 09-06-09 21WTD108r1 116 F Editorial change to add AF to abbreviations. 3.4.1 3.4.2 09-06-09 21WTD109r1 117 F Audit related errors/omissions. 3.4.1 3.4.2 09-06-09 21WTD110r1 118 F Error in H248 syntax in clause 5.18.1.4.1. 3.4.1 3.4.2 Publication 3.4.2 3.5.1 Re-publication after editorial correction to table 5 and correct implementation of CR113 3.5.1 3.5.2 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 181 History Document history V3.5.1 July 2009 Publication V3.5.2 January 2010 Publication |
9c251a86380319ca5f337310fb41e781 | 183 017 | 1 Scope | The present document provides the stage 3 specification of the Gq' interface. The functional requirements and the stage 2 specifications of the Gq' interface are contained in ES 282 001 [1] and ES 282 003 [2]. The Gq' interface is the interface between the Application Function (AF) and the Service Policy Decision Function (SPDF) and is used for session based policy set-up information exchange between the SPDF and the AF. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
9c251a86380319ca5f337310fb41e781 | 183 017 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [3] IETF RFC 3588: "Diameter Base Protocol". [4] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209 Release 6)". [5] IETF RFC 4005: "Diameter Network Access Server Application". [6] ETSI TS 133 210: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); 3G security; Network Domain Security (NDS); IP network layer security (3GPP TS 33.210)". [7] ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified]". ETSI ETSI TS 183 017 V3.2.1 (2010-02) 7 [8] ETSI ES 283 018: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". [9] IETF RFC 4566 (2006): "SDP: Session Description Protocol". [10] IETF RFC 2960: "Stream Control Transmission Protocol". [11] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change". [12] ETSI TS 129 207: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Policy control over Go interface (3GPP TS 29.207 Release 6)". [13] ETSI ES 283 035: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e2 interface based on the DIAMETER protocol". [14] ETSI ES 283 026: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control; Protocol for QoS reservation information exchange between the Service Policy Decision Function (SPDF) and the Access- Resource and Admission Control Function (A-RACF) in the Resource and Protocol specification". [15] ETSI ES 283 034: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol". [16] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". [17] IETF RFC 3388: "Grouping of Media Lines in the Session Description Protocol (SDP)". [18] IETF RFC 3524: "Mapping of Media Streams to Resource Reservation Flows". [19] ETSI TS 129 214: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 Release 7)". [20] ETSI TS 183 063: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification". [21] ETSI TS 183 048: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control System (RACS); Protocol Signalling flows specification; RACS Stage 3". [22] IETF RFC 3264: "An Offer/Answer Model with Session Description Protocol (SDP)". |
9c251a86380319ca5f337310fb41e781 | 183 017 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 183 017 V3.2.1 (2010-02) 8 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.