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 n... |
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 V... |
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 I... |
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 pri... |
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. T... |
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 Reco... |
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) an... |
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 condit... |
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 Stre... |
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 according... |
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 direc... |
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 ... |
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 ... |
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 Te... |
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 Gro... |
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 ... |
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 ad... |
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 i... |
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 ... |
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 <------------... |
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, Sel... |
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 { Ad... |
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, S... |
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 <------------------------------------... |
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 Descri... |
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 = ... |
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 Prope... |
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 = 3... |
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 ... |
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, Signa... |
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... |
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 <--... |
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, Event... |
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... |
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... |
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... |
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, Statistic... |
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 = 3... |
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, t... |
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 info... |
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/5... |
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... |
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... |
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 Connec... |
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 ... |
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... |
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 ... |
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, ... |
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/Ter... |
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 Sequenc... |
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... |
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... |
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 denot... |
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 V... |
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 ther... |
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 res... |
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 ... |
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... |
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 ... |
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 normal... |
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 ... |
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 f... |
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... |
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 UNAV... |
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,... |
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 A... |
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... |
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... |
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 appl... |
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 ... |
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... |
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 acco... |
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 ind... |
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. S... |
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 Funct... |
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 accept... |
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 con... |
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) ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.