hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.2 Summary | This profile supports the control of the following functionality in IP-to-IP Media Gateways: • opening and closing gates (i.e. packets filtering depending on "IP address/port"); • allocation and translation of IP addresses and port numbers (NAPT): - IP realm/domain indication (via H.248.41 amendment 1); - RTCP handling... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.3 Gateway Control Protocol Version | ITU-T Recommendation H.248.1 [1] Version 3. NOTE: Version 3 of the H.248 protocol is needed, due to the possible usage of stream statistics. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.4 Connection model | Table 2: Connection model Maximum number of contexts: Provisioned Maximum number of terminations per context: 2 Allowed terminations type combinations: (IP,IP) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 17 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.5 Context attributes | Table 3: Context attributes Context attribute Supported Values supported Topology No Not Applicable Priority Indicator Yes 0 to15 Emergency Indicator Yes ON/OFF IEPS Indicator No Not Applicable ContextAttribute Descriptor No Not Applicable ContextIdList Parameter No Not Applicable AND/OR Context Attribute No Not Applic... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6 Terminations | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1 Termination names | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1.1 IP Termination | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1.1.1 Overview and prose specification | The Termination ID structure shall follow the guidelines of H.248 and shall be based on four fields: • "ip/<group>/<interface>/<id>". The individual fields are described and defined in table 4. Table 4: IP Termination Fields Name Description Values CHOOSE Wildcard ALL Wildcard ip "ip" is a fixed prefix identifying the ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1.1.2 Syntactical Specification | 5.6.1.1.2.1 ABNF Grammar for H.248 Text Encoding Mode ABNF (RFC 5234 [6]) is used for the syntax specification. The ABNF for TerminationID and relation to pathNAME is defined in annex B.2 of ITU-T Recommendation H.248.1 [1]. ABNF coding: pathNAME = EphToken SLASH EPHsystem EphToken = "ip" ; prefix EPHsystem = WildcardA... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.2 Multiplexed terminations | Table 6: Multiplexed terminations MultiplexTerminations Supported? No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7 Descriptors | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.1 TerminationState descriptor | Table 7: ServiceState property ServiceState property used: No NOTE: All H.248 Terminations have a ServiceState property according to H.248.1, but explicit usage of the TerminationState Descriptor ServiceState property is not required by this Profile. ServiceState changes can still occur, however, and be indicated in Se... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.2 Stream descriptor | Table 9: Stream descriptor Maximum number of streams per termination type: IP 5 Table 10: Stream configuration Stream Configuration: ALL configurations are allowed |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.2.1 LocalControl descriptor | Table 11: LocalControl descriptor If not generic list appropriate termination and stream types Termination Type Stream Type ReserveGroup used: No ReserveValue used: No Table 12: Termination type Termination Type Stream Type Allowed StreamMode Values IP RTP/AVP SendOnly, RecvOnly, SendRecv, Inactive tcp SendRecv, Inacti... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.3 Events descriptor | Table 13: Events descriptor Events settable on termination types and stream types Yes If yes Event ID Termination Type Stream Type See clause 5.14.2.1 • g/cause ALL except ROOT ANY See clause 5.14.2.3 • nt/netfail • nt/qualert ALL except ROOT ANY See clause 5.14.2.11 • it/ito only ROOT Not applicable See clause 5.14.2.... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.4 EventBuffer descriptor | Table 20: EventBuffer descriptor EventBuffer Descriptor used: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.5 Signals descriptor | Table 21: Signals descriptor Signals settable dependant on termination or streams types Yes If yes Signal ID Termination Type Stream Type / ID ipnapt/* ALL except ROOT ANY Table 22: Signals lists Signals Lists supported: No Table 23: Signals type and duration Signal type and duration supported: No ETSI ETSI TS 183 018 ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.6 DigitMap descriptor | Table 28: DigitMap descriptor DigitMaps supported: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.7 Statistics descriptor | Table 29: Statistics Descriptor Statistics supported on: Stream Table 30: Statistics Reported On Subtract Statistics reported on Subtract: Yes If yes Statistic IDs reported: ALL (See clause 5.14 for details) |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.8 ObservedEvents descriptor | Table 31: ObservedEvents descriptor Event detection time supported: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.9 Topology descriptor | Table 32: Topology descriptor Allowed triples: Not Applicable ETSI ETSI TS 183 018 V3.5.2 (2010-01) 24 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.10 Error descriptor | Table 33: Error Codes sent by MGC Supported H.248.8 [30] Error Codes: ALL Supported Error Codes defined in packages: All error codes defined in supported packages need to be supported Table 34: Error Codes sent by MG Supported H.248.8 [30] Error Codes: ALL with exception of #514 "Media Gateway cannot send the specified... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8 Command API | Table 35 shows in which direction commands are sent, which terminations they can be associated with, and which wildcard options are supported for the specific command. Table 35: Commands and terminations Command Sent By Used on Termination Type Wildcard Support IP ROOT W- O- Add SPDF Yes No No No AuditCapabilities - - ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.1 Add | Table 38: Descriptors used by Add Request Descriptors used by Add request: Media (Stream(LocalControl, Statistics, Local, Remote)), Event, Signals NOTE: Statistics are enabled as default. The MGC may explicitly request or suppress statistics generation for individual streams by inclusion of the Statistics descriptor in... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.2 Modify | Table 40: Descriptors used by Modify Request Descriptors used by Modify request: Media (TerminationState, Stream (LocalControl, Statistics, Local, Remote)), Audit (Media (Stream (Statistics)), Signals, Event Table 41: Descriptors used by Modify Reply Descriptors used by Modify reply: Media (Stream(Local, Statistics)) E... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.3 Subtract | Table 42: Descriptors used by Subtract Request Descriptors used by Subtract request: Audit() OR NONE NOTE: This profile version supports reporting of statistics on all streams or none of the streams. Reporting and disabling of statistics from a subset of the streams in case of multiple streams is not supported by this ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.4 Move | Table 44: Descriptors used by Move Command Move command used: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.5 AuditValue | Table 45: AuditValue Audited Properties: Media(TerminationState) (see note 1) Media(Stream(LocalControl)) (see note 2) Audited Statistics: ALL Audited Signals: None Audited Events: None Packages Audit possible: Yes NOTE 1: These are the root/*, seg/* and ipra/* properties. NOTE 2: This is the mgcinfo/db property. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.6 AuditCapabilities | Table 46: Descriptors used by AuditCapabilities Command AuditCapabilities command used: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.7 Notify | Table 47: Descriptors used by Notify Request Descriptors used by Notify Request: ObservedEvents Table 47a: Descriptors used by Notify Reply Descriptors used by Notify Reply: None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 27 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.8 ServiceChange | Table 48: ServiceChangeMethods and ServiceChangeReasons sent by MGC Service Change Methods Supported ServiceChange Reasons supported Restart 900, 901 Handoff 903 Table 49: ServiceChangeMethods and ServiceChangeReasons sent by MG Service Change Methods Supported ServiceChange Reasons supported Disconnected 900 Forced 90... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.9 Manipulating and auditing context attributes | Table 55: Context Attributes Manipulation and Auditing Context Attributes Manipulated: Emergency, Priority Context Attributes Audited: None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 28 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.9 Generic command syntax and encoding | Table 56: Command Encoding Supported Encodings: Text (see notes 1 and 2) NOTE 1: The receiver shall be capable of receiving both Short Token Notation and Long Token Notation on an H.248 control association. NOTE 2: The transmitter may select between long and short token forms per H.248 control association. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.10 Transactions | Table 57: Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Replies per message: 1 Table 58: Maximum number of Commands per Transaction Request Maximum number of commands per Transaction request: 2 Table 59: Maximum number o... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.11 Messages | It is recommended that MGC and MG names are in the form of fully qualified domain names. For example the domain name of the MGC may be of the form mgc1.whatever.net and the name of the MG may be of the form mg1.whatever.net. The fully qualified domain name will be used by the MGC and MG as part of the "Message Identifi... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.12 Transport | Table 63: Transport Supported Transports: SCTP (Recommended) UDP (Optional) Table 64: Segmentation Segmentation Supported: SCTP: Inherent in Transport UDP: Optional (dependent on support of Segmentation Package, see clause 5.14.2.12) Table 65: Control Association Control Association Monitoring Supported: Monitoring mec... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.13 Security | Table 66: Security Supported Security: None |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14 Packages | This clause includes details of the mandatory and optional H.248 packages that are included in this profile. The meaning of mandatory and optional packages and their properties, signals, events, and statistics is defined in ITU-T Recommendation H.248 Sub-series Implementers' Guide [33]. ETSI ETSI TS 183 018 V3.5.2 (201... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.1 Overview | Table 67: Mandatory Packages Mandatory Packages Package Name Package ID Version Generic (ITU-T Rec. H.248.1 [1], annex E.1) g 2 Base root (ITU-T Rec. H.248.1 [1], annex E.2) root 2 Network (ITU-T Rec. H.248.1 [1], annex E.11) nt 1 Diffserv (ITU-T Rec. H.248.52 [17]) ds 2 Gate management (ITU-T Rec. H.248.43 [18], Appen... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2 Package usage information | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.1 Generic (g) | Table 69: Generic package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command Cause (g/c... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.2 Base root (root) | Table 70: Base root package Properties Mandatory/Optional Used in command Supported Values Provisioned Value MaxNrOfContexts (root/maxNumberOfContexts) O AUDITVALUE ALL YES MaxTerminationsPerContext (root/maxTerminationPerContext) O AUDITVALUE ALL YES normalMGExecutionTime (root/normalMGExecutionTime) O MODIFY, AUDITVA... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.3 Network (nt) | Table 71: Network package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Maximum jitter buffer (nt/jit) O ADD, MODIFY ALL YES Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Even... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.4 Differentiated Services (ds) | Table 72: Differentiated Services package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Differentiated Services Code Point (ds/dscp) M ADD, MODIFY ALL Yes Tagging Behaviour (ds/tb) O ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.5 Gate Management (gm) | Table 73: Gate Management Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Remote Source Address Filtering (gm/saf) M ADD, MODIFY ALL Not Applicable (see note 1) Remote Source Address Mask (gm/sam) O ADD, MODIFY ALL Not Applicable Remote Source Port Filtering (gm/spf) M ADD, MODI... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.6 Traffic management (tman) | Table 74: Traffic Management Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value tman/pol M ADD, MODIFY ALL Yes tman/pdr M ADD, MODIFY ALL Not Applicable tman/dvt M ADD, MODIFY ALL Yes tman/sdr M ADD, MODIFY ALL Not Applicable tman/mbs M ADD, MODIFY ALL Yes Signals Mandatory/Optiona... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.7 IP NAPT Traversal (ipnapt) | Table 75: IP NAPT Traversal Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value Latching (ipnapt/latch) M ADD, MODIFY Not Applicable Signal Parameters Mandatory/Optional Supported Values Duration Provisioned ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.8 MPLS (mpls) | Table 76: MPLS Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value mpls/stack M ADD, MODIFY ALL Not Applicable (see note) Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Event... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.9 VLAN (vlan) | Table 77: VLAN Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value VLAN tags (vlan/tags) O ADD, MODIFY ALL (see note) Yes Ethernet priority (vlan/pri) O ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optiona... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.10 MGC Information (mgcinfo) | Table 78: MGC Information Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value ALL M ADD, MODIFY, AUDITVALUE ALL Not Applicable Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.11 Inactivity Timer (it) | Table 79: Inactivity Timer Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command I... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.12 Segmentation (seg) | Table 80: Segmentation Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value MGSegmentation TimerValue (seg/ MGSegmentationTimerValue) M AUDITVALUE, MODIFY ALL YES MGCSegmentation TimerValue (seg/ MGCSegmentationTimerValue) M AUDITVALUE, MODIFY ALL YES MGMaxPDUSize (seg/ MGMaxPDUSize)... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.13 RTP (rtp) | Table 81: RTP Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.14 Application Data Inactivity Detection (adid) | Table 82: Application Data Inactivity Detection Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optio... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.15 IP Domain Connection (ipdc) | Table 83: IP domain connection package Properties Mandatory/Optional Used in command Supported Values Provisioned Value IP Realm Identifier (iIpdc/realm) M ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.16 Media Gateway Overload Control (ocp) | Table 84: Media Gateway Overload Control Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.17 Hanging Termination Detection (hangterm) | Table 85: Hanging Termination Detection Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events M... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.18 Statistic Conditional Reporting (scr) | Table 86: Statistic Conditional Reporting Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.19 IP Realm Availability (ipra) | Table 86a: IP Realm Availability Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Available Realms, (ipra/ar) M AUDITVALUE ALL Not Applicable Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Dur... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.20 RTP Application Data (rtpad) | Table 86b: RTP Application Data Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.21 Latch Statistics (lstat) | Table 86c: Latch Statistics Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events Man... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.22 Void | Table 86d: Void |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.23 Traffic Policing Statistics (tmanr) | Table 86e: Traffic Policing Statistics Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - -... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.16 Optional support of SDP and annex C information elements | NOTE: "Annex C" relates to H.248.1 annex C "Tags for Media Stream Properties". Annex C information elements are not required in H.248 text encoding mode. Table 88 summarizes the "optional" SDP information elements, according their specific usage according clause 7.1.8 of ITU-T Recommendation H.248.1 [1]. Their usage ma... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17 Overview of Procedures | Details of Session Dependent Procedures are provided in clauses 5.18. Details of Session Independent Procedures are provided in clauses 5.19 and 5.20. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1 Overview of Session Dependent Procedures | The general procedures are related to session-dependent (also known as H.248 call-dependent) procedures. There are procedures in following categories: • Address allocation and translation is in scope of clauses 5.17.1.2. The adaptation of addresses (latching) is the subject of clause 5.17.1.3. • Session-dependent polic... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1 Gate control | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.1 Streams, Terminations and Gates | The realization of a gate requires two ephemeral terminations. An ephemeral termination sources and/or sinks one or more media streams. Gates are direction and stream dependent. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 49 In this profile, RTP traffic shall be controlled through a single H.248 stream, representing both the... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.2 Assignment of L3 address and L4 port values | The H.248 base protocol enables the MGC to choose the IP address and port on which a termination will receive media flows. In addition, the Gate Management package enables the MGC to explicitly provide the following information: 1) expected IP source address and port of received packets; 2) IP source address and port o... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.3 Opening and closing of gates | Opening and closing gates is achieved by setting the Stream mode parameter of the associated termination(s) to the appropriate values. Subtracting a termination from a context also closes the gate for all H.248 streams in the termination. In the context of conversational services, an active session requires that the ga... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.4 Filtering due to conditions on L3 address and/or L4 port values | Filtering on the IP source address and/or port might be implemented using the Gate Management package, or using the SDP information in the Remote Descriptor. In case the filtering is done based on the Remote Descriptor, the activation/deactivation of the filtering is configured in the MG. If the Gate Management package... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2 Allocation and translation of IP addresses, ports and versions (NAPT-PT) | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.1 Allocation methods | The procedures of this clause support the following NAPT-PT functionality: • NAPT-PT functionality with "double" addresses and ports translation (both source and destination addresses and ports are translated; example see clause 5.17.1.2.2); • or optional NAPT-PT functionality with "single" address and port translation... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.2 "Double" NA(P)T | The term "double" NA(P)T relates to the translation of source and destination address information: • "double" NAT = translation of 2-tuple (DA, SA) is not supported by this profile (because it would require the L4-port agnostic mode); • "double" NAPT = translation of 4-tuple (DA, SA, DP, SP), i.e. L4-port aware mode. E... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.3 "Single" NA(P)T | The term "single" NA(P)T relates to the translation of either source-only or destination-only address information: • "single" NAT = translation of 1-tuple (SA) or (DA) is not supported by this profile (because it would require the L4-port agnostic mode); • "single" NAPT = translation of 2-tuple (SA, SP) or (DA, DP), i.... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.4 NA(P)T-less case | See also clause H.3 of [i.18]. 5.17.1.2.4.1 NA(P)T-less B2BIH mode For NA(P)T-less applications, the T1 Local Descriptor address and port in figure 3 has to be changed to 156.106.192.33: 556 (equal to the T2 Remote Descriptor address and port) and the T2 Local Descriptor address and port in figure 3 has to be changed t... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.5 NA(P)T and explicit Local Source Transport Address settings | NAPT control on source addresses and ports (i.e. source NAPT) is achieved by setting the local source address and local source port properties defined in the Gate Management package to a value that differs from the actual source address of the packets received from the remote entity. The gm package capabilities may be ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.6 Protocol Translation (V4 to V6) | Protocol Translation (NAPT-PT) can be controlled by the MGC by adding to the same H.248 context, two terminations whose media descriptors have different address-type values in the "c=" line. NOTE: It is recommended that the MGC takes precaution if setting up streams with both fully specified and under specified address... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.3 Support of Hosted NAT Traversal | "Hosted NAT Traversal" relates to "assisting remote NAT/NAPT traversal" for the remote (peer) IP connection endpoints from BGF/SPDF point of view. This relates to an interim NA(P)T device from BGW perspective. The remote IP address information cannot be retrieved from the Remote Descriptor. The "Hosted NAT Traversal" f... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.4 QoS marking | The Differentiated Services package enables the MGC to control the setting of the DSCP value for all packets leaving the MG. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.4.1 Copying DSCP/ToS values from the ingress to egress | The copy mechanism is specified in Amendment 1 to H.248.52 [17]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.4.2 Auditing the "Per-Hop Behaviour" | The Per-Hop Behaviour (PHB) concerning "MGC-signalled QoS marking" versus "copying of QoS values" may be explicitly controlled (and audited) using Differentiated Services package version 2, see Amendment 1 to H.248.52 [17]. The Differentiated Services package version 1 does not allow to audit the behaviour, see the not... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5 Bandwidth control - Reservation, Allocation and Policing | Resources are reserved independently per gate. For each gate, reservation of local resources for handling incoming and outgoing traffic is achieved by setting the appropriate properties in the Local and Remote Descriptors. Only one session description shall be included in each Stream Descriptor. Hence, the ReserveValue... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.1 Admission Control | Admission Control is defined in RACS for the BGF (MG role) level. There is no concept of a call in H.248 MGs due to the separation of call and bearers in the H.248 model, which means that AC translates in a Context Admission Control (CoAC; see also ITU-T H.Sup6) and Stream Admission Control (StAC) on MG side. The StAC ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.2 Traffic Descriptor | A traffic descriptor is the set of traffic parameters that is used to capture the traffic characteristics of an IP flow (see clause 3.2.10/ITU-T Recommendation Y.1221 [i.10]). The traffic parameters for an H.248 Stream of an H.248 IP Termination are direction-independent and given by either: 1) an explicit specificatio... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.3 Bandwidth reservation and allocation | 5.17.1.5.3.1 SDP "b=" line for constant bitrate traffic The amount of required bandwidth for sending packets is expressed using the "b=" line of the SDP description contained in the Remote Descriptors. The amount of required bandwidth for receiving packets is expressed using the "b=" line of SDP description contained i... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.4 Bandwidth policing | Policing of incoming traffic can be enabled using the Traffic Management package. Policing on incoming traffic can be set independently for each gate. The properties of the Traffic Management package shall be set to values that are compatible (see note) with the "b=" line value of the Local Descriptor. NOTE: The term "... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.5 Non-specification of tman properties | If no properties of the Traffic Management package are provided, the MG will not perform traffic policing. If only the tman/pol property set to ON is present, traffic policing shall not be done based on the b-line value, i.e. the policing function cannot be activated at this stage. Summary on bandwidth control actions:... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6 Usage metering and statistics reporting | Usage metering is supported by the statistics defined in the network and other packages. Such statistics may be notified to MGC when a stream is removed (and stats explicitly requested by the MGC) or a termination is subtracted from a context (e.g. at the end of a session). They provide information about: 1) informatio... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6.1 Statistics for Media/Transport-agnostic IP packets | The available statistics for the IP streams and terminations of a dedicated context are dependent of the IP-to-IP interworking mode (see clause 3.1). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6.2 Traffic Volume related Statistics | Figure 3a provides an overview of different traffic volume related statistics, which might be useful for the various IP-to-IP interworking modes (e.g. media-agnostic, media-aware, transport-protocol agnostic). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 59 5.17.1.6.2.1 General Case The general case relates to Ia profile vers... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6.3 Statistics for packet filtering | 5.17.1.6.3.1 Address policing: explicit remote source transport address filtering Filter conditions based on source transport address information for remote IP endpoints may be enabled with Gate Management properties (see also clause 5.17.1.1). The number of discarded packets due to remote source filtering may be repor... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.7 RTCP Handling | Handling of RTCP is already partially addressed by clause 5.17.1.1. This clause defines further procedures for RTCP. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.7.1 RTCP Transport Address Allocation | 5.17.1.7.1.1 Local RTCP IP Transport Address Allocation In line with the recommendations of RFC 3605 [31], separate address or non-contiguous RTCP port numbers (identified via the "a=rtcp" media attribute) shall not be used by the BGF in its LD. Local ports for RTCP are implicitly allocated by the MG whenever instructe... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.7.2 RTP/RTCP to-H.248 Stream Mapping | In line with clause 5.17.1.7.1.1, a single common H.248 stream is always used for RTP and its associated RTCP flow. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8 RTCP Forwarding | Every RTP session may be accompanied by RTCP control flows. Blocking (by the BGF) of such RTCP packets may violate the end-to-end RTP/RTCP protocol and/or the served applications. However, security threats or specific RTCP reports types may request for dedicated RTCP packet policing rules. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8.1 Conditions for RTCP packet policing | Conditions for RTCP packet policing are typically based on following n-tupel elements: • IP port for RTCP flow; • RTCP packet type codepoint; • RTCP SSRC codepoint; • RTCP source description information element (e.g. CNAME codepoint); or/and • RTCP block type codepoint in case of RTCP extension reports (XR, HR). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8.2 Forwarding of regular RTCP traffic | "Regular" RTCP packets shall be understood in the scope of the present document as packet units with a packet type value equal to a value from the range of {192, 193, 200 to 206}. Thus, regular traffic excludes XR and HR RTCP packets. Regular RTCP packets must be basically forwarded towards the RTP endpoint. Regular RT... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8.3 Handling of RTCP XR/HR traffic | Extension reports (XR) and XR-based high resolution reports, - i.e. RTCP reports with a packet type value equal to 207 - carry measurement data from Measurement Points (MP) to Reporting Points (RP). Such measurement reports do not have necessarily an end-to-end significance, their scope may be e.g. limited to a single ... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.9 Media Inactivity | Application data inactivity detection (also known as media inactivity detection) may have multiple, different use cases as cited in ITU-T Recommendation H.248.40 [12] e.g.: • detection of interrupted IP routes; • detection of released RTP endpoints; • detection of hanging SIP/RTP sessions (see note); or • detection of ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.