hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.7 Granted-Delegated-Bandwidth-DL AVP
|
The Granted-Delegated-Bandwidth-DL AVP (AVP code 656) is type Unsigned32, and it indicates the granted delegated bandwidth in kbits per second in the downlink direction.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.8 Total-Bandwidth-UL AVP
|
The Total-Bandwidth-UL AVP (AVP code 657) is type Unsigned32, and it indicates the total bandwidth in kbits per second in the uplink direction.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.9 Total-Bandwidth-DL AVP
|
The Total-Bandwidth-DL AVP (AVP code 658) is type Unsigned32, and it indicates the total bandwidth in kbits per second in the downlink direction.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.10 Reservation-priority AVP
|
The Reservation-Priority AVP (AVP code 458) is of type Enumerated. The following values are specified. DEFAULT (0): This is the lowest level of priority. If no Reservation-Priority AVP is specified in the AA-Request, this is the priority associated with the reservation. • PRIORITY-ONE (1). • PRIORITY-TWO (2). • PRIORITY-THREE (3). • PRIORITY-FOUR (4). • PRIORITY-FIVE (5). • PRIORITY-SIX (6). ETSI ETSI TS 183 071 V3.1.1 (2010-02) 43 • PRIORITY-SEVEN (7). • PRIORITY-EIGHT (8). • PRIORITY-NINE (9). • PRIORITY-TEN (10). • PRIORITY-ELEVEN (11). • PRIORITY-TWELVE (12). • PRIORITY-THIRTEEN (13). • PRIORITY-FOURTEEN (14). • PRIORITY-FIFTEEN (15).
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.11 Authorization-Package-Id AVP
|
The Authorization-Package-Id AVP (AVP code 461) is of type UTF8String, and it identifies an authorization context requested by the AF for the session and passed transparently through Rq. This information is used by the delegated x-RACF to derive the policy to be passed to an RCEF through the Re reference point for the session.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.12 Abort-Cause AVP
|
The Abort-Cause AVP (AVP code 500) is of type Enumerated, and it determines the cause of an ASR. The following values defined in TS 129 209 [7] are used: • INSUFFICIENT_SERVER_RESOURCES (1): - This value is used to indicate that the x-RACF is overloaded. • INSUFFICIENT_BEARER_RESOURCES (2): - This value is used when the bearer has been deactivated due to insufficient bearer resources at a transport gateway (e.g. RCEF for xDSL).
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.13 Flow-Description AVP
|
The Flow-Description AVP (AVP code 507) is of type IPFilterRule, and defines a packet filter for an IP flow with the following information: • Direction (in or out). • Source and destination IP address (possibly masked). • Protocol. • Source and destination port (list or ranges). The b type shall be used with the following restrictions: • Only the Action "permit" shall be used. • No "options" shall be used. • The invert modifier "!" for addresses shall not be used. • The keyword "assigned" shall not be used. The direction "in" refers to uplink IP flows, and the direction "out" refers to downlink IP flows. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 44
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.14 Specific-Action AVP
|
The Specific-Action AVP (AVP code 513) is of type Enumerated. The following event from TS 129 209 [7] is supported: • INDICATION_OF_RELEASE_OF_BEARER (4): - Within a RAR, this value shall be used when the delegated x-RACF reports to the delegating x-RACF the release of a bearer (e.g. RCEF policies being removed). In case of failure of a multicast request, the RAR message includes the address of the UE that requested the multicast flow and the flow description of the flow. - Within a CCR, this value shall be used when the delegating x-RACF reports to the delegated x-RACF the release of a bearer (e.g. RCEF policies being removed). In case of failure of a multicast request, the CCR message includes the address of the UE that requested the multicast flow and the flow description of the flow. In addition, the present document defines two new events: • INDICATION_OF_SUBSCRIBER_DETACHMENT (6): - Within a RAR, this value shall be used when the delegated x-RACF reports to the delegating x-RACF that a subscriber has been detached. - Within a CCR, this value shall be used when the delegating x-RACF reports to the delegated x-RACF that a subscriber has been detached. • INDICATION_OF_RESERVATION_EXPIRATION (7): - Within a RAR, this value shall be used when the delegated x-RACF reports to the delegating x-RACF that a reservation is about to expire. - Within a CCR, this value shall be used when the delegating x-RACF reports to the delegated x-RACF that a reservation is about to expire. Other events but the above-listed ones defined by TS 129 209 [7] are not relevant at the Rr interface and are not supported.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.15 Globally-Unique-Address AVP
|
The Globally-Unique-Address AVP (AVP code 300) is of type Grouped. AVP Format: Globally-Unique-Address ::= < AVP Header: 300 13019 > [Framed-IP-Address] [Framed-IPv6-Prefix] [Address-Realm]
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.16 Address-Realm AVP
|
The Address-Realm AVP (AVP code 301) is of type OctetString and contains an address realm in the form of a FQDN.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.17 Logical-Access-ID AVP
|
The Logical-Access-ID AVP (AVP code 302 13019) is of type OctetString. It is defined in ES 283 034 [4].
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.18 Framed-IP-Address AVP
|
The Framed-IP-Address AVP (AVP Code 8) is of type OctetString and contains an IPv4 address of the type specified in the attribute value to be configured for the user. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 45
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
7.5.19 Framed-IPv6-Prefix AVP
|
The Framed-IPv6-Prefix AVP (AVP Code 97) is of type OctetString and contains the IPv6 prefix to be configured for the user. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 46 History Document history V3.1.1 February 2010 Publication
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
1 Scope
|
The present document defines a profile of the Gateway Control Protocol (H.248.1 [15]), for controlling access and residential gateways connecting analog lines and ISDN primary and basic accesses, in order to emulate PSTN/ISDN services over IP. 1.1 Differences between H.248 ARGW Profiles Version 1 and Version 2 The differences between both H.248 profile versions are detailed in annex A. Summary list of differences: 1) Package usage details (see clause 5.14.2). 2) IUA/SCTP encapsulation for Q.921 p-/f-type frames in IP domain (see clause 7.3.2). 3) Additional V5 support (see clause 7.4). 4) Adaptive-rate based MGC overload control (see clause 8.1.2). 5) Real time statistics reporting (see clause 8.4). 1.2 Differences between H.248 ARGW Profiles Version 2 and Version 3 The differences between both H.248 profile versions are detailed in annex A. Summary list of differences: 1) traffic volume related statistics on application data level (see clause 8.5); 2) V.152 compliant VBDoIP service (see clause 6.2); 3) addition of Digit Dialling Method Information for Extended Digit Maps Package; and 4) a keep pinhole open method for NAT traversal support (see clause 6.9).
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
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. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 8
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
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 Release 1". [2] ETSI ES 282 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [3] ETSI ES 201 970: "Access and Terminals (AT); Public Switched Telephone Network (PSTN); Harmonized specification of physical and electrical characteristics at a 2-wire analogue presented Network Termination Point (NTP)". [4] ETSI EN 300 659-1: "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1: On-hook data transmission". [5] ETSI EN 300 659-2: "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 2: Off-hook data transmission". [6] ETSI ETS 300 099: "Integrated Services Digital Network (ISDN); Specification of the Packet Handler access point Interface (PHI)". [7] ETSI EN 301 141-1: "Integrated Services Digital Network (ISDN); Narrowband Multi-service Delivery System (NMDS); Part 1: NMDS interface specification". [8] ETSI ETS 300 402-2: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 2: General protocol specification [ITU-T Recommendation Q.921 (1993), modified]". [9] ETSI EN 300 367: "Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Service description". [10] ETSI TS 102 333: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Gate control protocol". [11] ITU-T Recommendation H.248.45: "Gateway control protocol: MGC information package". [12] IETF RFC 4233 (2006-01): "Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer". [13] ETSI TBR 003: "Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access". [14] ETSI TBR 004: "Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN primary rate access". [15] ITU-T Recommendation H.248.1 + Corrigendum 1: "Gateway control protocol: Version 2". [16] ITU-T Recommendation H.248.2: "Gateway control protocol: Facsimile, text conversation and call discrimination packages". [17] ITU-T Recommendation H.248.4 + Corrigendum 1: "Gateway control protocol: Transport over Stream Control Transmission Protocol (SCTP)". [18] ITU-T Recommendation H.248.7: "Gateway control protocol: Generic Announcement package". [19] ITU-T Recommendation H.248.11: "Gateway control protocol: Media gateway overload control package". [20] ITU-T Recommendation H.248.13: "Gateway control protocol: Quality Alert Ceasing package". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 9 [21] ITU-T Recommendation H.248.14: "Gateway control protocol: Inactivity timer package". [22] ITU-T Recommendation H.248.16 + Corrigendum 1: "Gateway control protocol: Enhanced digit collection packages and procedures". [23] ITU-T Recommendation H.248.23: "Gateway control protocol: Enhanced Alerting packages". [24] ITU-T Recommendation H.248.26 + Amendment 1: "Gateway control protocol: Enhanced analog lines packages". [25] ITU-T Recommendation H.248.34: "Gateway control protocol: Stimulus analogue lines package". [26] ITU-T Recommendation Q.1950: "Bearer independent call bearer control protocol". [27] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". [28] ITU-T Recommendation G.711 Appendix I: "A high quality low-complexity algorithm for packet loss concealment with G.711". [29] ITU-T Recommendation G.711 Appendix II: "A comfort noise payload definition for ITU-T G.711 use in packet-based multimedia communication systems". [30] ITU-T Recommendation T.38: "Procedures for real-time Group 3 facsimile communication over IP networks". [31] ITU-T Recommendation V.150.1: "Modem-over-IP networks: Procedures for the end-to-end connection of V-series DCEs". [32] ITU-T Recommendation V.152 + Corrigendum 1 + Corrigendum 2: "Procedures for supporting voice-band data over IP networks". [33] ITU-T Recommendation E.180: "Technical characteristics of tones for the telephone service". [34] IETF RFC 2327: "SDP: Session Description Protocol". [35] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". [36] IETF RFC 4301: "Security Architecture for the Internet Protocol". [37] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". [38] IETF RFC 2784: "Generic Routing Encapsulation (GRE)". [39] IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call". [40] IETF RFC 4855: "Media Type Registration of RTP Payload Formats". [41] ITU-T Recommendation G.168: "Digital network echo cancellers". [42] IETF RFC 2733: "An RTP Payload Format for Generic Forward Error Correction". [43] IETF RFC 2198: "RTP Payload for Redundant Audio Data". [44] ITU-T Recommendation Q.115.0: "Protocols for the control of signal processing network elements and functions". [45] ITU-T Recommendation Q.115.1: "Logic for the control of echo control devices and functions". [46] ITU-T Recommendation Q.921: "ISDN user-network interface - Data link layer specification". [47] ETSI ETS 300 297: "Integrated Services Digital Network (ISDN); Access digital section for ISDN basic access". [48] ETSI ETS 300 233: "Integrated Services Digital Network (ISDN); Access digital section for ISDN primary rate". [49] ITU-T Recommendation H.248.17: "Gateway control protocol: Line test packages". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 10 [50] ETSI ES 201 235-3: "Access and Terminals (AT); Specification of Dual-Tone Multi-Frequency (DTMF) Transmitters and Receivers; Part 3: Receivers". [51] IETF RFC 3389: "Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)". [52] ETSI ES 283 002 (V1.1.3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Release 1 H.248 Profile for controlling Access and Residential Gateways". [53] IETF RFC 3807 (2004): "V5.2-User Adaptation Layer (V5UA)". [54] ETSI EN 300 324-1: "V interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 1: V5.1 interface specification". [55] ETSI EN 300 347-1: "V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 1: V5.2 interface specification". [56] ITU-T Recommendation H.248.47+Revision 1 (2008-07): "Gateway control protocol: Statistic conditional reporting package". [57] ETSI ES 283 039-4 (V2.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Overload Control Architecture; Part 4: Adaptative Control for the MGC". [58] IETF RFC 2960: "Stream Control Transmission Protocol". [59] ETSI TS 102 144: "Services and Protocols for Advanced Networks (SPAN); MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP); Stream Control Transmission Protocol (SCTP) [Endorsement of RFC 2960 and RFC 3309, modified]". [60] ITU-T Recommendation H.248.58 (06/2008): "Gateway Control Protocol: Packages for application level H.248 Statistics". [61] ITU-T Recommendation H.248.52 (2008): "Gateway control protocol: QoS Support Packages". [62] ETSI ES 283 002 (V2.1.0): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Profile for controlling Access and Residential Gateways". [63] Void. [64] ITU-T Recommendation H.248.70 (2009): "Gateway control protocol: Dialling method information packages". [65] IETF RFC 5109: "RTP Payload Format for Generic Forward Error Correction". [66] IETF RFC 4734: "Definition of Events for Modem, Fax, and Text Telephony Signals".
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
2.2 Informative references
|
[i.1] ETSI TR 183 025 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-call related procedures and management system interaction". [i.2] ETSI TR 183 040 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 POTS Message Flows based on the H.248 Profile for controlling Access and Residential Gateways". [i.3] ITU-T Recommendation H.248.1 (Version 3) Amendment 1: "Gateway control protocol". [i.4] Draft ITU-T Recommendation H.248.50: "Gateway control protocol: NAT Traversal Toolkit Packages". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 11
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
3 Definitions and abbreviations
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
3.1 Definitions
|
For the purposes of the present document the terms and definitions given in ITU-T Recommendation H.248.1 [15] and the following apply: Access GateWay (AGW): Media GateWay (MGW) that interworks a significant number of analogue lines to a packet network and is located at the operator's premises NOTE: See also clause 3.1of ITU-T Recommendation H.248.1 [15]. IP Port: source and destination port numbers for UDP, SCTP and TCP traffic Media GateWay (MGW): refers both to Access Media GateWays (AMGs) and to Residential Media Gateways (RMGs) NOTE: See ITU-T Recommendation H.248.1 [15]. MG Port: single physical access interface at a Media GateWay. This is always a circuit oriented interface in the scope of this H.248 Profile NOTE: There are therefore three port types: analog port, ISDN Basic Rate Access port and Primary Rate Access Port. originating Media GateWay (MGW): Media GateWay (MGW) to which the calling party's physical termination is connected Residential GateWay (RGW): Media GateWay MGW) that interworks a small number of analogue lines NOTE: A Residential Media Gateway (RMG) typically contains one or two analogue lines and is located at the customer premises. See also clause 3.6 of ITU-T Recommendation H.248.1 [15]. terminating Media GateWay (MGW): Media GateWay (MGW) to which the called party's physical termination is connected
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACO Address COmplete message AGCF Access Gateway Control Function AGW Access GateWay ALN Analog Line AMG Access Media Gateway A-MGF Access-MGF AN Access Network AOC Advice of Charge ARGW Access Residential media GateWay BA Basic Access BGF Border Gatweay Function CDR Call Detail Record CN Comfort Noise CRC Cyclic Redundancy Check DLCI Data Link Connection endpoint Identifier DNS Domain Name System DTMF Dual Tone Multi Frequency ECD Echo Control Device FEC Forward Error Correction FECD Full ECD FH Frame Handler ETSI ETSI TS 183 002 V3.3.1 (2009-08) 12 GRE Generic Routing Encapsulation HECD Half-way ECD IECD Incoming ECD IID IUA Interface Identifier IP Internet Protocol IPsec IP security ISDN Integrated Services Digital Network ISUP ISDN User Part IUA ISDN Q.921-User Adaptation LD Local Descriptor MGC Media Gateway Controller MGF Media Gateway Function MGW Media GateWay MID Message Identifier MRFP Media Resource Function Processor NAT Network Address Translation NMDS Narrowband Multi-service Delivery System NT1 Network Termination (type 1) NTN Network Terminating Node NTP Network Termination Point OAM Operation, Administration and Maintenance OECD Outgoing ECD PBX Private Branch eXchange PES PSTN/ISDN Emulation Subsystem PH Packet Handler PLC Packet Loss Concealment PLP Packet Layer Procedures PRA Primary Rate Access PT Payload Type QoS Quality of Service RD Remote Descriptor RFC Request For Comments (IETF) RGW Residential GateWay RMG Residential Media Gateway RMGC Resdiential Media Gateway Controller R-MGF Residential-MGF RTP Real-time Transport Protocol SAPI Service Access Point Identifier SCTP Stream Control Transmission Protocol SDP Session Description Protocol SPNE Signal Processing Network Equipment SRV SeRVer SSRC Synchronization SouRCe TAS Terminal Alerting Signal TCP Transmission Control Protocol TDW Time Division Multiplexing TE Terminal Equipment TEI TE Identifier TLS Transport Layer Security TMGW Trunking Media GateWay TTL Time To Live UDP User Datagram Protocol V5UA V5.2 - User Adaptation Layer VBD VoiceBand Data VoIP Voice over IP ETSI ETSI TS 183 002 V3.3.1 (2009-08) 13
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
4 Applicability
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
4.1 Architecture
|
Figure 1 illustrates the architecture assumed in the present document. The Media Gateway Controller (MGC) resides in a control subsystem and may be implemented as a stand-alone piece of equipment or as a component of a call server. Access to the IP network is provided to analog terminals, ISDN terminals, analog and ISDN Private Branch Exchanges (PBX), V5.1 and V5.2 Access Networks (AN) through Residential GateWays (RGWs) or Access GateWays (AGWs), which support one or more of the following reference points: • The Z reference point for analogue terminations. • The T reference point for Primary Rate Access. • The S/T reference point for Basic Rate Access. • The T* reference point for NMDS Access, as defined in EN 301 141-1 [7]. • The V5.1 reference point for V5.1 Access, as defined in EN 300 324-1 [54]. • The V5.2 reference point for V5.2 Access, as defined in EN 300 347-1 [55]. AGW IP Transport (Access and Core Network) Legacy User Equipment (terminals, PBXs) RGW Customer’s Premises Operator’s Premises Control Subsystem Scope of this specification NOTE: V5 interfaces are supported by this profile, but not indicated in this drawing. The V5 access networks would be located in the operator's premises, in front of the AGW. Figure 1: Reference architecture The present document does not make any assumption on the structure of the control subsystem hosting the MGC functionality. In the context of the TISPAN NGN Architecture (see ES 282 001 [1]), the control subsystem is the PSTN/ISDN Emulation Subsystem (PES) (see ES 282 002 [2]). Within this subsystem, the AGCF plays the MGC role. The RGW and the AGW implement the R-MGF and A-MGF functional entities (respectively). The area shown within the dashed lines, including part of the equipment placed on customer premises as a RGW, is considered to be under the control of a single operator. The use of IPSec (see RFC 4301 [36] or other security measures to create such a control area is outside the scope of the present document. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 14
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
4.2 Functional requirements
|
Support of the packages identified in the profile definition implies support of the underlying functionalities. This clause identifies additional functional requirements that Media GateWays (MGWs) conforming to the present document shall comply with: • Media GateWays (MGWs) shall support IPv4 and may support IPv6. • Media GateWays (MGWs) shall support for ITU-T Recommendation G.711 [27] A-law voice codec and may support other codecs. NOTE: Other mandatory codecs may also be required depending on the architecture in which Media GateWays (MGWs) are used. • Media GateWays (MGWs) shall support autonomous transition from Audio Mode to ITU-T Recommendation G.711 [27]-based VBD Mode (according to ITU-T Recommendation V.152 [32]) upon detection of fax modem, text modem or data modem traffic. • Media GateWays (MGWs) supporting other codecs than ITU-T Recommendation G.711 [27] shall also support the procedures defined in RFC 4733 [37] to generate, detect and forward DTMF digits. DTMF shall be identified by name (see mode "Named Telephone Events" in clause 3/RFC 4733 [37]), as opposed to their waveform properties. • All properties of tones requested by the MGC shall be provisioned in the Media GateWay (MG). The MGC is not required to send the physical characteristics of tones to Media GateWays (MGWs). • Where a RGW also provides customer access via a Network Address Translation (NAT) device, the design of the NAT function shall be such that it does not interfere with, and explicitly takes account of, the operation of the H.248 gateway function in the RGW.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5 Profile description
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.1 Profile identification
|
Table 1 provides the name and version of the profile that is sent in the service change command. Table 1 Profile name: ETSI_ARGW Version: 3
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.2 Summary
|
The profile defined in the present document enables the control of residential and access media gateways connecting analog and ISDN lines to an IP transport domain, in order to emulate PSTN/ISDN services.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.3 Gateway control protocol version
|
Version 2 shall be the minimum version supported. Support of this version implies conformance to ITU-T Recommendation H.248.1 Version 2 and Corrigendum 1 [15] to this Recommendation, and implementation of the corrections available in the latest version of the H.248 Implementors' Guide. Version 3 may be required if automatic metering requires iteration notification and/or if the "one way external" topology configuration is supported. Support of this version implies conformance to ITU-T Recommendation H.248.1 Version 3 [i.3]. However, only "onIteration" in the NotifyComplete flag, "oneWayExternal" in the Topology Descriptor and "neverNotify" of the NotifyBehaviour parameter are required from this Recommendation. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 15
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.4 Connection model
|
Media GateWays (MGWs) shall support ephemeral terminations that sink and source RTP traffic. This type of H.248 termination is denoted RTP in the following clauses. Media GateWays (MGWs) shall also support at least one of the following types of physical terminations: • ANALOG: H.248 terminations representing analogue lines where the Network Termination Point (NTP) at the customer premises conform to ES 201 970 [3]. • ISDN: H.248 terminations representing ISDN B-Channels of ISDN Primary and Basic Access (BA) that conform to TBR 003 [13] and TBR 004 [14]. • V5: Support of V5.1 and V5.2 is according to EN 300 324-1 [54] and EN 300 347-1 [55]. Support of NMDS is achieved using ISDN terminations, according to EN 301 141-1 [7]. Table 2 Maximum number of contexts: Provisioned (see note 1) Maximum number of terminations per context: 2 (see note 2), 3 (see note 3), (see note 4), more than 3 (see note 4) (see note 5) Allowed terminations type combinations in a context: Media GateWays (MGWs) shall provide support for creating contexts containing two terminations of the same or different types, i.e. Context[a](ANALOG, ANALOG), Context[b](ANALOG, ISDN), Context[c](ISDN, ISDN), Context[d](ANALOG, RTP), Context[e](ISDN, RTP), Context[f](RTP, RTP). (See note 6) Support for more than two terminations of the same or different types may also be provided for 3-party calls, lawful intercept or both. NOTE 1: The actual number of supported contexts can be audited by the MGC using the MaxNrOfContexts property defined in the Base Root Package. NOTE 2: Support of 2 terminations in a context is the basic requirement in the MG. There are two levels of compliance to this basic requirement: a "basic support" and an "advanced support" of the connection model. Basic Support: This combination only allows Context [d] and Context [e]. It should be noted that in this case an ephemeral termination is never added to a context without the presence of a physical termination within this context. Advanced Support: Any combination of two termination types in contexts is allowed. There is no restriction as to whether an ephemeral termination can be added to a context other than NULL prior a physical termination also being present in this context. The distinction between basic and advanced support is configurable in the MGC on a per MG basis. NOTE 3: Support of 3 terminations in a context is required if the MG supports 3-party conference calls. The combination of terminations types may differ for a basic or advanced support of the connection model. Basic Support: This level of support allows for one physical termination of type ANALOG or ISDN and two ephemeral terminations. Advanced Support: Any combination of terminations is allowed of type ANALOG, ISDN and RTP. NOTE 4: Support of more than 2 terminations in a context is required if the MG supports lawful intercept. NOTE 5: The actual number of supported terminations can be audited by the MGC using the maxTerminationsPerContext property defined in the Base Root Package. NOTE 6: Certain actions performed by the MGC may result in a context having one or more ephemeral terminations without any associated physical termination. This occurs for example while an ISDN subscriber has two active calls, each of which associated with two different contexts in the media gateway. Based on a subscriber's decision, the MGC may subtract the physical terminations from their respective contexts and reconnect the ephemeral terminations into a single context, thereby creating a context with two ephemeral terminations (RTP-to-RTP interworking). There are several services that can invoke a similar procedure, one of which is the Explicit Call Transfer service (see EN 300 367 [9]). ETSI ETSI TS 183 002 V3.3.1 (2009-08) 16
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.5 Context attributes
|
Table 3 Context attribute Supported Values supported Topology Yes See clause 5.7.8 Priority Indicator Yes 1 to 15 Emergency Indicator Yes Not Applicable
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.6 Terminations
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.6.1 Termination names
|
The termination ID structure is provisioned in the MGC and MG and is known by the MG and the MGC at or before start up. A hierarchical naming structure is recommended for physical and ephemeral terminations.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.6.1.1 Physical terminations
|
For example, the naming convention for physical terminations representing analog lines could be defined as follows: al/<subrack>/<card>/<port> Where, "al/" is a fixed prefix, <subrack>, <card> and <port> are non-zero integer values. According to this naming scheme, an analog line connected on port 2 of card 1 in subrack 22 would be referred to as al/22/1/2. A similar structure may also be used for ISDN Basic Access (BA)and Primary Rate Access (PRA), using different prefixes: "ba/" for Basic Access and "pra/" for Primary Rate Access. In such cases, the naming structure shall end with a component identifying a B channel. For example the naming convention for physical terminations representing ISDN Basic Accesses may be defined as follows: ba/<subrack>/<card>/<port>/<channel> Where, "ba/" is a fixed prefix, <subrack>, <card> and <port> are non-zero integer values and <channel> shall uniquely identify each of the 2 B channels. According to this naming scheme, an ISDN Basic Access B channel number 1 connected on port 7 of card 3 in subrack 15 would be referred to as ba/15/3/7/1. Similarly the naming convention for physical terminations representing ISDN Primary Rate Accesses and V5 access may be defined as follows: pra/<subrack>/<card>/<port>/<channel> Where, "pra/" is a fixed prefix, <subrack>, <card> and <port> are non-zero integer values and <channel> shall uniquely identify each of the ISDN-PRA B channels. The channel number shall be in the range 1 to 15 or 17 to 31 which identifies the time slot on the E1 used for transporting the "B" channel. According to this naming scheme, an ISDN Primary Rate Access B channel carried in Time Slot 20 connected on port 3 of card 9 in subrack 5 would be referred to as pra/5/9/3/20.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.6.1.2 Ephemeral terminations
|
For example the naming convention for ephemeral terminations may be defined as follows: ephemeral/<string of alphanumeric characters or "/"> e.g. Ephemeral/1/0/40000. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 17
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.6.2 Multiplexed terminations
|
Table 4 Multiplex terminations supported? NO NOTE: The MG is not required to support bonding of multiple ISDN B-channels, e.g. for support of ISDN multimedia conferencing. If there are such applications and ISDN teleservices, the MG will handle each B-channel individually. Therefore, this profile is not required to support the multiplex descriptor.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7 Descriptors
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.1 Stream descriptor
|
Table 5 Maximum number of streams per termination type RTP, ANALOG, ISDN 1
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.1.1 LocalControl Descriptor
|
The following tables specify the level of support required with regard to the properties in the local control descriptor. Table 6 Termination type Stream type Reserve group used: Yes RTP Not Applicable Reserve value used: Yes RTP Not Applicable ReserveGroup: The MGC shall set the "ReserveGroup" property to "true" in the case multiple session descriptor blocks are used for specifying multiple "m=" lines and resources are required to be reserved in the MG for the multiple session descriptor blocks. This situation can occur for example where the first session block descriptor contains a "m=" line indicating audio, while the second session descriptor contains a "m=" line indicating T.38 (fax/modem relay). Alternatively, if the MGC when it specifies multiple session descriptor blocks requires the MG to select one of the session descriptor blocks, then it shall set the "ReserveGroup" property to "false". Another example of where multiple "m=" lines may be specified is where different packetization periods are required for the different audio codecs. In the situation where the MGC specifies a single session descriptor block, then the "ReserveGroup" property may be omitted or set to "false". ReserveValue: The MGC shall set the "ReserveValue" property to "true" when multiple codecs are specified within a single "m=" line of a session descriptor block and resources are required to be reserved in the MG for the multiple codecs. This situation occurs for example for audio calls where a low bit rate codec is specified for transporting voice and a G.711 codec (see ITU-T Recommendation G.711 [27]) is used for fallback (see ITU-T Recommendation V.152 [32]) in case a fax/modem is detected. Alternatively, if the MGC when it specifies multiple codecs requires the MG to select one of the codecs, then it shall set the "ReserveValue" property to "false". In the situation where the MGC species a single codec within a "m line", then the ReserveValue property shall be omitted or set to "false". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 18 StreamMode: Table 7 Termination type Stream type Allowed StreamMode values ALL except ROOT Not Applicable Send, Receive, Send and Receive, Loopback, Inactive Table 8 Properties associated with Local Control Descriptor supported: Yes If yes Property IDs reported Termination type Stream type nt/jit RTP Not Applicable tdmc/ec tdmc/gain ANALOG, ISDN ANALOG Not Applicable mgcinfo/db ALL Not Applicable dscp/* RTP Not Applicable
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.2 Events descriptor
|
Table 9 Events settable on termination types and stream types: Yes If yes Event ID Termination type Stream type g/* ALL Not Applicable ocp/* ROOT Not Applicable nt/netfail nt/qualert ALL except ROOT RTP Not Applicable rtp/* RTP Not Applicable xdd/xce, dd/[d0-d9], dd/da, dd/db, dd/dc, dd/dd, dd/do, dd/ds ANALOG, ISDN (see note) Not Applicable xal/* ANALOG Not Applicable stimal/* ANALOG Not Applicable qac/* RTP Not Applicable it/* ROOT Not Applicable ctyp/* ANALOG, ISDN Not Applicable amet/* ANALOG Not Applicable NOTE: Support of the xdd package on ISDN terminations is required by certain types of ISDN-to-analog adaptors that cannot transport DTMF signals in ISDN signalling messages. Table 10 Event buffer control used: No Table 11 Keepactive used on events: Yes Table 12 Embedded events in an event descriptor: Yes Embedded signals in an event descriptor: Yes ETSI ETSI TS 183 002 V3.3.1 (2009-08) 19 Table 13 NotifyBehaviour used on events: Yes If yes Supported values NeverNotify
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.3 EventBuffer descriptor
|
Table 14 Event buffer descriptor used: No If yes Event IDs Not Applicable
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.4 Signals descriptor
|
Table 15 Signals settable dependant on termination or streams types: Yes If yes Signal ID Termination type Stream type/ID cg/* ALL except ROOT Not Applicable srvtn/* ALL except ROOT Not Applicable xcg/* ALL except ROOT Not Applicable andisp/* ANALOG Not Applicable an/* ALL except ROOT Not Applicable xal/* ANALOG Not Applicable int/* ALL except ROOT Not Applicable biztn/* ALL except ROOT Not Applicable stimal/* ANALOG Not Applicable alert/* ANALOG Not Applicable amet/* ANALOG Not Applicable ctyp/* ANALOG or ISDN Not Applicable Table 16 Signals lists supported: Yes If yes Termination type supporting lists ALL Stream type supporting lists ALL Maximum number of signals per signal list 5 Table 17 Signal type and duration supported: Yes If yes Signal ID Type or duration override ALL Both Table 18 Signal direction supported: No Table 19 Notify completion supported: Yes If yes Signal ID Type of completion supported ALL ALL ETSI ETSI TS 183 002 V3.3.1 (2009-08) 20 Table 20 RequestID parameter supported: Yes Table 21 Signals played simultaneously: Yes If yes Signal Ids that can be played simultaneously: ALL Table 22 Keepactive used on signals: Yes
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.5 DigitMap descriptor
|
Media GateWays (MGWs) conforming to this profile shall support at least one DigitMap. Table 23 DigitMaps supported: Yes If yes DigitMap name Structure Timers It is recommended that the default initial digit map (i.e. first digit map used for collecting dialled numbers from ordinary subscriber lines) be named InitDM0. Network operator dependent. Network operator dependent.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.6 Statistics descriptor
|
Table 24 Statistics supported on: Termination Table 25 Statistics supported on subtract: Yes If yes Statistic IDs reported Termination type Stream type nt/dur nt/os nt/or ALL RTP RTP Not Applicable rtp/* RTP amet/* ANALOG
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.7 ObservedEvents descriptor
|
When the event is provisioned in the media gateway, the Request Id is set to FFFFFFFF'H. Table 26 Event detection time supported: Yes ETSI ETSI TS 183 002 V3.3.1 (2009-08) 21
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.8 Topology descriptor
|
Support of the topology descriptor is optional. Table 27 Allowed triples: ALL values defined in ITU-T Recommendation H.248.1 [15] Version 3 [i.3] shall be supported.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.7.9 Error descriptor
|
MGC supported: Table 28 Supported H.248.8 error codes: ALL Supported error codes defined in packages: All error codes defined in supported packages need to be supported. MG supported: Table 29 Supported H.248.8 error codes: ALL Supported error codes defined in packages: All error codes defined in supported packages need to be supported.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8 Command API
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.1 Add
|
Table 30 Descriptors used by Add request: ALL except Mux Table 31 Descriptors used by Add reply: ALL except Mux
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.2 Modify
|
Table 32 Descriptors used by Modify request: ALL except Mux Table 33 Descriptors used by Modify reply: ALL except Mux ETSI ETSI TS 183 002 V3.3.1 (2009-08) 22
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.3 Subtract
|
Table 34 Descriptors used by subtract: Audit Table 35 Descriptors used by subtract: Statistics
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.4 Move
|
Table 36 Move command used: Yes Table 37 Descriptors used by Move Request: ALL except Mux Descriptors used by Move Reply: ALL except Mux
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.5 AuditValue
|
Table 38 Audited properties: ALL properties in ALL descriptors Audited statistics: ALL Audited signals: ALL Audited events: ALL Package audit possible? YES
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.6 AuditCapabilities
|
Table 39 Audited properties: ALL properties in ALL descriptors Audited statistics: ALL Audited signals: ALL Audited events: ALL
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.7 ServiceChange
|
Table 40 MGC supported: ServiceChange methods supported: ServiceChange reasons supported: ALL 900 to 920 ETSI ETSI TS 183 002 V3.3.1 (2009-08) 23 Table 41 MG supported: ServiceChange methods supported: ServiceChange reasons supported: ALL 900 to 920 Table 42 ServiceChangeAddress used: No Table 43 ServiceChangeDelay used: Yes If yes Valid time period: Provisioned Table 44 ServiceChange incomplete flag used: No Table 45 Version used in ServiceChangeVersion: ITU-T Recommendation H.248.1 Version 2 [15] shall be the minimum version used in ServiceChangeVersion. ITU-T Recommendation H.248.1 Version 3 [i.3] may also be reported by media gateway that support automatic metering with iteration notification and/or the "oneWayExternal" configuration of the topology descriptor and/or setting of notifyBehaviour. Table 46 Profile negotiation as per H.248.18: No
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.8.8 Manipulating and auditing context attributes
|
Table 47 Context attributes manipulated: ALL supported attributes (see table 3) Context attributes audited: ALL supported attributes (see table 3)
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.9 Generic command syntax and encoding
|
Table 48 Supported encodings: Text encoding shall be supported by both the MG and the MGC. Both the long and short form of text encoding shall be supported at the receiving side. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 24
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.10 Transactions
|
Table 49 Maximum number of transaction requests/replies/TransResponseAcks/segment replies per message: 2 NOTE: When two elements are conveyed in one message, it is recommended that this message comprises a transaction request/transaction reply/transaction pending plus a transaction response ACK. Table 50 Segmentation supported: UDP: No SCTP: Inherent in transport NOTE: The H.248 segmentation package according annex E.14 of ITU-T Recommendation H.248.1 Version 3 [i.3] is intended for H.248 transport technologies without the capability of automatic message segmentation. This method is not required for UDP- or SCTP-based H.248 signalling transport in this Profile. Table 51 Maximum number of commands per transaction request: 3 Table 52 Maximum number of commands per transaction reply: 3 Table 53 Commands able to be marked "Optional": AUDITVALUE, AUDITCAPABILITY Table 54 Transaction timer: Value normalMGExecutionTime Provisioned in the MG normalMGCExecutionTime Provisioned in the MG MGOriginatedPendingLimit Provisioned in the MG MGCOriginatedPendingLimit Provisioned in the MG MGProvisionalResponseTimerValue Provisioned in the MG MGCProvisionalResponseTimerValue Provisioned in the MG Transaction timers (as defined in the properties of the Base Root package) shall be in a range between 100 ms and 5 s. The MGC may overwrite the provisioned values.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.11 Messages
|
It is recommended that MG and MGC names are in the form of fully qualified domain name. 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 MG and MGC as part of the "Message Identifier" (MID) in the H.248 messages which identifies the originator of the message. The MGC domain name is provisioned in the MG or retrieved from the DNS using SRV records. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 25 The use of a domain name provides the following benefits: • MGs and MGCs are identified by their domain name, not their network addresses. Several addresses can be associated with a domain name. If a command cannot be forwarded to one of the network addresses, implementations shall retry the transmission using another address. • MGs and MGCs may move to another platform. The association between a logical name (domain name) and the actual platform are kept in the Domain Name Service (DNS). MG and MGC shall keep track of the record's time-to-live read from the DNS. They shall query the DNS to refresh the information if the time-to-live has expired. • The domain name may be used by MGC/MG for authentication purposes. • Can assist in trouble shooting.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.12 Transport
|
Table 55 Supported transports: Transport over UDP shall be supported. Support of SCTP is optional and shall conform to ITU-T Rec. H.248.4 [17]. Choosing one option or the other is a network operator's decision, based on the network configuration. For UDP transport the destination IP addresses to be used for delivering the H.248 messages are retrieved through the following means: • The MGC will store the source IP address retrieved from the message carrying first ServiceChange command. All subsequent messages delivered to the MG will use this IP address. • The MG will store the source IP address retrieved from the message carrying the reply to the ServiceChange command. All subsequent messages delivered to the MGC will use this IP address. NOTE: The MG will use the DNS lookup in order to retrieve the initial IP address to send the first ServiceChange command. This IP address may be different than the IP address returned in the reply to ServiceChange command. Table 56 Control association monitoring supported: UDP: AuditValue on Root and ITU-T Rec.H.248.14 [21] SCTP: Inherent in Transport,
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.13 Security
|
Table 57 Supported security: For the purpose of the present document the control protocols are considered to be inside the secured zone of a single operator as shown in figure 1. The specified H.248 security options should not be used, as these interfaces are considered to be within a secured zone. In clause 7 of the present document protocols other than H.248 are specified and the security issues are dealt with here. No security measures, either IPsec or TLS, shall be used on the IUA and V5UA interfaces since they too are considered to be within a secured zone. Finally no countermeasures shall be applied to the GRE interface carrying packet data. It is important to note that the context of this clause, and the recommendations in it, only apply to the case where the interfaces, H.248, IUA, V5UA and GRE specified by the present document all fall within the secure zone shown in figure 1. In any other case a different risk may apply and appropriate countermeasures may be needed. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 26
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14 Packages
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.1 Overview
|
Table 58 Mandatory packages Package name/reference PackageID Version Generic (ITU-T Rec. H.248.1 [15]) g 1 or 2 - Base Root (ITU-T Rec. H.248.1 [15]) root 2 Call Progress Tones Generator (ITU-T Rec. H.248.1 [15]) cg 1or 2 - Overload Control Package (ITU-T Rec. H.248.11 [19]) ocp 1 Network (ITU-T Rec. H.248.1 [15]) nt 1 TDM Circuit (ITU-T Rec. H.248.1 [15]) tdmc 1 RTP (ITU-T Rec. H.248.1 [15]) rtp 1 Extended DTMF Detection (ITU-T Rec. H.248.16 [22]) xdd 1 Table 59 Optional packages (see note 1) Package name/reference PackageID Version Support dependent on: Basic Services Tones Generator (IITU-T Rec. Q.1950 [26]) srvtn 1 This package shall be supported if terminations representing analog lines are supported by the MG. Expanded Call Progress Tones Generator (ITU-T Rec. Q.1950 [26]) xcg 1 This package shall be supported if terminations representing analog lines are supported by the MG. Enhanced Alerting (ITU-T Rec. H.248.23 [23]) (see note 2) alert 2 This package shall be supported if terminations representing analog lines are supported by the MG. Analog Display Signalling (ITU-T Rec. H.248.23 [23]) andisp 2 This package shall be supported if terminations representing analog lines are supported by the MG. Generic Announcement (ITU-T Rec. H.248.7 [18]) an 1 Support becomes mandatory if local announcements are available. Analog Line Supervision (ITU-T Recommendation H.248.1 [15]) (see note 3) al 1 This package shall be supported by the MG if terminations representing analog lines are supported and the Stimal package is not supported. Extended Analog Line Supervision (ITU-T Rec. H.248.26 [24]) (see note 3) xal 2 This package shall be supported by the MG if terminations representing analog lines are supported AND control of polarity reversal is required by the operator AND the Stimal package is not supported. Automatic Metering (ITU-T Rec. H.248.26 [24]) amet 2 Support of Advice of Charge using pulse metering on analog lines. Intrusion Tones Generation (ITU-T Rec. Q.1950 [26]) Int 1 Special types of access gateways (e.g. connecting private networks) or network operator option. Business Tones Generation (ITU-T Rec. Q.1950 [26]) biztn 1 Special types of access gateways (e.g. connecting private networks) or network operator option. DiffServ (ITU-T Rec. H.248.52 [61]) ds 1 Operator option. The Differentiated Services package may be used for QoS marking of IPv4 or IPv6 packets of the H.248 RTP stream/termination. Quality Alert Ceasing (ITU-T Rec. H.248.13 [20]) qac 1 Quality of Service Monitoring is enabled. Inactivity Timer (ITU-T Rec. H.248.14 [21]) it 1 UDP transport is enabled. Call Type Discrimination (ITU-T Rec. H.248.2 [16]) ctyp 1 Used by the MG in situations where it is necessary to inform the MGC of the detected voice-band tone so that the MGC for example can inform non ITU-T Rec. G.168 [41] compliant MGs to remove any echo cancellers (see note 4). Stimulus Analog Line (ITU-T Rec. H.248.34 [25]) (see note 3) stimal 1 This package shall be supported by terminations representing analog lines are supported AND the Analog Line Supervision package is not supported. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 27 Optional packages (see note 1) Package name/reference PackageID Version Support dependent on: MGC Information (ITU-T Rec. H.248.45 [11]) MGCInfo 1 This package may be supported as an operator option. For this profile the information string shall be limited to 32 octets in length. Statistic Conditional Reporting (ITU-T Rec. H.248.47 [56]) scr 2 Support of real-time reporting of specific statistics based on a particular condition. This package may be supported as an operator option. ETSI Notification Rate (ES 283 039-4 [57]) etsi_nr 1 This package may be supported as a network operator option in order to protect the MGC under overload conditions. RTP Application Data (ITU-T Rec.H.248.58 [60]) rtpad 1 Support of usage metering and statistics reporting. Scope on traffic-volume based measurement of RTP application data (i.e. the media stream). Keepalive Request (ITU-T Rec. H.248.50 [i.4]) kar 1 This package may be supported by RGW to send keep-alive packets for the purposes of NAT traversal and to keep alive a NAT binding. This package is not necessary for AGW. Digit Dialling Method Information for Extended Digitmap Detection (ITU-T Rec. H.248.70 [64]) xdmi 1 If digit detection method is required to be conveyed to the MGC. NOTE 1: Unless stated otherwise, version 1 of each package shall be supported. NOTE 2: This package overlaps with the Stimulus Analog Line package (see table 60). If the Stimulus Analog Line package is implemented, support of the ringsplash signal of the Enhanced Alerting package is optional. NOTE 3: Table 60 provides an overview of the overlap between the Stimulus Analog Line package and other packages. NOTE 4: The Media GateWays (MGWs) using this profile are required to support ITU-T Rec. G.168 [41]. Table 60 reflects the overlap between al, alert, xal and amet packages against stimal package. If the stimal package is supported by the Media GateWay (MGW) then only the alert package (ring and call waiting signals) and automatic metering package (enable metering signal) are to be supported while the al and xal packages are not used. Table 60: Overlap between the stimal package and other packages Package name Package ID Comment on overlapping Analog Line Supervision al offhook = steady-signal, Off hook (loop closed) onhook = steady-signal, On hook flashhook = pulsed signal, Register recall Enhanced Alerting package alert ring = (no overlap) ringsplash = pulsed signal, Initial Ring call waiting = (no overlap) Extended analog line supervision package xal Line-side answer supervision (las) = steady signal, Reversed Polarity Network Disconnect (nd) = pulsed signal, Pulsed No Battery Automatic Metering package amet Enable metering = (no overlap) Metering pulse burst = pulsed signal, Meter Pulse ETSI ETSI TS 183 002 V3.3.1 (2009-08) 28
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2 Package usage information
|
Table 61 Package usage information Package name Support of properties, parameters, signals, events, statistics, error codes Package usage/provisioned value Generic ALL Base Root ALL Call Progress Tones Generator ALL If used, the release tone shall be identical to the congestion tone. Levels, cadences and frequencies of signals shall conform to national specifications. In the absence of such specification, the following rules shall be used. Levels, cadences and frequencies of the following signals shall conform to ES 201 970 [3]: - Dial Tone - Ringing Tone (also known as ringback tone) - Busy Tone - Call Waiting Tone The characteristics of other signals shall conform to ITU-T Rec. E.180 [33]. Basic Services Tones Generator ALL Unless specified otherwise in national specifications, the characteristics of the Message Waiting Tone signal shall be those defined in ES 201 970 [3] for the Special Dial Tone. Expanded Call Progress Tones Generator ALL Unless specified otherwise in national specifications, the characteristics of the Special Condition Dial Tone (spec) shall be those of the Special Dial Tone defined in ES 201 970 [3]. Analog Line Supervision The ring signal shall not be used. Ringing shall be controlled using the ring signal of the Enhanced Alerting package. The on-hook and off-hook signals shall respectively conform to the Clear and Seize signals defined in ES 201 970 [3]. The hook-flash signal shall conform to the Register Recall signal defined in ES 201 970 [3]. Enhanced Alerting ALL Unless specified otherwise in national specifications, the default ring signal shall conform to ES 201 970 [3]. A minimum of 5 different ring patterns shall be provisioned in the MG. The pattern number 1 shall be the default pattern, used for normal ringing. Analog Display Signalling ALL See clause 7.2.4. Automatic Metering ALL 12 kHz or 16 kHz signals shall be supported by the MG. The frequency shall be provisioned on a per MG basis. If acknowledgement of individual pulses is required, this profile shall use H.248 Version 3 rather than H.248 version 2. Extended DTMF Detection ALL DTMF detection shall conform to ES 201 235-3 [50]. Recommended default values of the timers defined in ITU-T Rec. H.248.1 [15] for an initial digit map are: - T = 20 seconds - S = 5 seconds - L = 10 seconds. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 29 Package usage information Package name Support of properties, parameters, signals, events, statistics, error codes Package usage/provisioned value Extended Analog Line Supervision ALL The Line-side answer supervision (xal/las) shall result in the MG applying a reverse polarity. The Network Disconnect (xal/nd) signals shall, as a network option, result in either the MG applying normal polarity or disconnecting the power feed for a short duration. Overload Control ALL Network ALL The MGC should not set the Maximum Jitter Buffer property. Media GateWays (MGWs) shall ignore this property if received from a MGC. TDM Circuit ALL Default value for the Echo Control property is "on". RTP ALL Generic Announcement ALL Intrusion Tones Generator ALL Business Tones Generator ALL DiffServ ALL Quality Alert Ceasing ALL Inactivity Timer ALL Call Type Discrimination ALL Stimulus Analog Line ALL MGC Information ALL Keepalive Request ALL See clause 5.14.2.28 RTP Application Data ALL See clause 5.14.2.27 Digit Dialling Method Information for Extended Digit Maps Package ALL See clause 5.14.2.29
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.1 Generic (g)
|
Table 62: 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: - - - - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 30 Events Mandatory/ Optional Used in command: Cause (g/cause) M NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: General cause (Generalcause) M ALL Not Applicable Failure cause (Failurecause) M ALL Not Applicable Signal Completion (g/sc) M NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Signal Identity (SigID) M ALL Not Applicable Termination Method (Meth) M ALL Not Applicable Signal List ID (SLID) O ALL Not Applicable Request ID (RID) O ALL Not Applicable Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 31
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.2 Base root (root)
|
Table 63: Base root package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: Maximum Number of Contexts (root/maxNumberOfContexts) O AUDITVALUE ALL YES Maximum Terminations Per Context (root/maxTerminationsPerContext) O AUDITVALUE ALL YES Normal MG Execution Time (root/normalMGExecutionTime) O MODIFY, AUDITVALUE ALL YES Normal MGC Execution Time (root/normalMGCExecutionTime) O MODIFY, AUDITVALUE ALL YES MG Provisional Response Timer Value (root/MGProvisionalResponseTimerValue) O MODIFY, AUDITVALUE ALL YES MGC Provisional Response Timer Value (root/MGCProvisionalResponseTimerValue) O MODIFY, AUDITVALUE ALL YES MGC Originated Pending Limit (root/MGCOriginatedPendingLimit) O MODIFY, AUDITVALUE ALL YES MG Originated Pending Limit (root/MGOriginatedPendingLimit) O MODIFY, AUDITVALUE ALL YES 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: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 32
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.3 Call progress tones generator (cg)
|
Table 64: Call progress tones package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Dial Tone (cg/dt) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Ringing Tone (cg/rt) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Busy Tone (cg/bt) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Congestion Tone (cg/ct) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Special Information Tone (cg/sit) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - (Recording) Warning Tone (cg/wt) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Payphone Recognition Tone (cg/prt) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Call Waiting Tone (cg/cw) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Caller Waiting Tone (cg/cr) M ADD, MODIFY Yes Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 33 Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Event Parameters - - - ObservedEvent Parameters Mandatory/ Optional ObservedEvent Parameters - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None -
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.4 Media GateWay (MGW) overload control (ocp)
|
Table 65: Media GateWay (MGW) 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 Mandatory/ Optional Used in command: MG_Overload ocp/mg_overload M MOD, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 34
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.5 Network (nt)
|
Table 66: Network Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: Maximum Jitter Buffer (nt/jit) - - - - 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: Network Failure (nt/netfail) (see note 1) M MOD, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Cause - - - Quality Alert (nt/qualert) O ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Threshold (th) O ALL Yes ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Threshold (th) O ALL Yes Statistics Mandatory/ Optional Used in command: Supported Values: Duration (nt/dur) M AUDITVALUE, SUBTRACT ALL Octets Sent (nt/os) (see note 2) M AUDITVALUE, SUBTRACT ALL Octets Received (nt/or) (see note 2) M AUDITVALUE, SUBTRACT ALL Error Codes Mandatory/Optional None - NOTE 1: This event may be semantically overloaded if there are multiple failure causes (see ITU-T Rec. H.248.1 Version 3 [i.3], clause E.11.5.1.2). An unambiguous distinction between the MGC and MG sides implies mutually agreed cause code points. This is a provisioning activity. NOTE 2: The semantic of these statistics was clarified in ITU-T Rec. H.248.1 Version 3 Amendment 1 [i.3]. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 35
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.6 TDM circuit (tdmc)
|
Table 67: TDM Circuit package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: Echo Cancellation (tdmc/ec) M ADD, MODIFY ALL "True" (note) Gain Control (tdmc/gain) O ADD, MODIFY ALL - 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: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - NOTE: This value would be justified in case that "speech telephony" is the dominating service and an estimated end-to-end delay of more than 25 ms (which could be already the case for RTP packetization times of 20 ms). It has to be noted that the physical termination represents the "cancelled end" from perspective of a half-way echo canceller. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 36
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.7 RTP (rtp)
|
Table 68: RTP Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Events Mandatory/ Optional Used in command: Payload Transition (rtp/pltrans) O MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: RTP Payload Type (=rtppltype M - - Statistics Mandatory/ Optional Used in command: Supported Values: Packets Sent (rtp/ps) M AUDITVALUE, SUBTRACT ALL Packets Received (rtp/pr) M AUDITVALUE, SUBTRACT ALL Packet Loss (rtp/pl) M AUDITVALUE, SUBTRACT ALL Packets Jitter (rtp/jit) M AUDITVALUE, SUBTRACT ALL Packet Delay (rtp/delay) M AUDITVALUE, SUBTRACT ALL Octets Sent (rtp/os) note M AUDITVALUE, SUBTRACT ALL Octets Received (rtp/or) note M AUDITVALUE, SUBTRACT ALL Error Codes Mandatory/Optional None - NOTE: The values of these statistics must be identical with the nt package. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 37
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.8 Extended DTMF detection (xdd)
|
Table 69: Extended DTMF Detection package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Events Mandatory/ Optional Used in command: Extended DigitMap Completion, xdd/xce M ADD, MOD, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Buffer control, bc M Integer - Extra digit disposition, xdd O ON, OFF - Match procedure, mp M base, enhanced - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Digit string, ds M ALL - Termination method, meth M "UM", "PM", "FM" - Unmatched event, extra M String - Events Mandatory/ Optional Used in command: DTMF digits, xdd/* M ADD, MOD, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 38
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.9 Basic services tones generator (srvtn)
|
Table 70: Basic Service Tones Generator package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Recall Dial Tone, srvtn/rdt M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Confirmation Tone, srvtn/conf M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Held Tone, srvtn/ht M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Message Waiting Tone, srvtn/mwt M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 39
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.10 Expanded call progress tones generator (xcg)
|
Table 71: Expanded Call Progress Tones Generator package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Comfort Tone, xcg/cmft O ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Off-hook Warning Tone, xcg/roh M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Vacant Number Tone, xcg/vac M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Special Conditions Dial Tone, xcg/spec M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Negative Acknowledgement Tone, xcg/nack O ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 40
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.11 Enhanced alerting (alert)
|
Table 72: Enhanced Alerting package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Power Ring, alert/ri M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Pattern, pattern M ALL 1 Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Call Waiting, alert/cw M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Pattern, pattern M ALL 1 Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Ring Splash alert/ri O ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: Tone direction, btd O External External Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 41
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.12 Analog display signalling (andisp)
|
Table 73: Analogue Display package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Display with Alerting, andisp/dwa M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Display Data Block, ddb M ALL Default: "" Pattern, pattern M ALL 1 Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Generic Data signalling, andisp/data M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Data Block, db YES ALL Default: "" Terminal Alert Signal, tas YES ALL Yes Tone direction, btd YES External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Error Tone, andisp/err O ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: Tone direction, btd O External External Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 42
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.13 Generic announcement (an)
|
Table 74: Generic Announcement package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Fixed Announcement Play, an/apf M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Announcement Name, an M ALL Yes Announcement Cycles, noc O - 1 Announcement Variant, av O - Yes Announcement direction, di O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Variable Announcement Play, an/apv O ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Announcement Name, an M ALL Yes Announcement Cycles, noc O - 1 Announcement Variant, av O - Yes Announcement direction, di O External External Specific Parameter Interpretation, spi O - Yes Specific Parameters, sp O - Yes Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 43
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.14 Analog line supervision (al)
|
Table 75: Analogue Line Supervision package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Ring, al/ri M ADD, MOD. AUDIT VALUE Timepout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Cadence, Cad O - Yes Frequency, Freq O - Yes Events Mandatory/ Optional Used in command: On-Hook, al/on M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: strict M ALL - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: init M ALL - Off-Hook, al/of M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: strict M ALL - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: init M ALL - Hook-Flash, al/fl M MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: mindur O - Yes maxdur O - Yes ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional 540 M ETSI ETSI TS 183 002 V3.3.1 (2009-08) 44
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.15 Extended analog line supervision (xal)
|
This package extends al. The additional parts are shown below. Table 76: Analogue Line Supervision package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Line Side Answer, xal/las M MOD. AUDIT VALUE On/Off Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Network Disconnect, xal/nd M MOD. AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 45
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.16 Automatic metering (amet)
|
Table 77: Automatic Metering package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Enable Metering, amet/em M ADD, MOD. AUDIT VALUE On/Off Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Pulse Count, pc O ALL - Pulse Repetition Interval, pri M ALL - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Metering Pulse Burst, amet/mpb M ADD, MOD. AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Burst Pulse Count, bpc O ALL - Pulse Repetition Interval, pri O ALL - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Phased Metering, amet/phsm O ADD, MOD. AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Pulse Repetition Interval, pri M ALL - Max PCCI, pcx M ALL - Repetitions of Max PCCI, repx M ALL - Min PCCI, pcn M ALL - Repetitions of Min PCCI, repn M ALL - Charge Interval, ci M ALL - Phase Duration, pd M ALL - Events Mandatory/ Optional Used in command: Periodic Report, amet/pr M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Report Period, rp M ALL - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Statistics Mandatory/ Optional Used in command: Supported Values: Current Pulse Count, amet/cpc M AUDIT VALUE, SUBTRACT, MODIFY ALL Pulse Count Since Last Report, amet/pcslr M AUDIT VALUE, SUBTRACT, MODIFY ALL Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 46
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.17 Intrusion tones generation (int)
|
Table 78: Intrusion Tones Generation package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Intrusion Pending Tone, int/pend M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Intrusion Tone, int/int M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Intrusion Reminder Tone, int/rem M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Toll Break In Tone, int/tbi M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Intrusion Queue Tone, int/que M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Busy Verification Tone, int/bv M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 47
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.18 Business tones generation (biztn)
|
Table 79: Business Tones Generation package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Off-Hook Queuing Tone, biztn/ofque M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Expensive Route Warning Tone, biztn/erwt M ADD, MOD, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Distinctive Dial Tone, biztn/ddt M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Internal Dial Tone, biztn/idt M ADD, MOD, AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone direction, btd O External External Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 48
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.19 Differentiated Services (ds)
|
Table 80: Differentiated Services package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: ds/dscp M ADD, MODIFY ALL Not Applicable 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: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None -
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.20 Quality alert ceasing (qac)
|
Table 81: Quality Alert Ceasing 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: Provisioned Value: - - - - Events Mandatory/ Optional Used in command: Quality Alert Ceasing, qac/qualertcease M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Threshold, th O ALL Yes ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 49
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.21 Inactivity timer (it)
|
Table 82: 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: Inactivity Timeout, it/ito M MOD, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Maximum Inactivity Time, mit O Any integer Unspecified ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None -
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.22 Call type discrimination (ctyp)
|
Table 83: Call Type Discrimination package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: Call Types, ctyp/calltyp O MOD, AUDIT VALUE - - Text Call Types, ctyp/ttyp O MOD, AUDIT VALUE - - Phase Reversal Detect, ctyp/V8bsup O MOD, AUDIT VALUE - - Probe Message, ctyp/probemsg O MOD, AUDIT VALUE - - Probe Order, ctyp/probeorder O MOD, AUDIT VALUE - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: V8 Signal, ctyp/v8sig O ADD, MOD. AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: V8 Signal Type, v8styp O ALL Yes V8 Signal Content, v8scont O ALL Empty String V18 XCI Enable, v18xcien O ALL True ETSI ETSI TS 183 002 V3.3.1 (2009-08) 50 Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Answer Signal, ctyp/ans O ADD, MOD. AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Answer Type, AnsType O ALL Yes Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Calling Signal, ctyp/callsig O ADD, MOD. AUDIT VALUE Timeout Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Calling Signal Name, cSn O ALL Yes Signals Mandatory/ Optional Used in command: Duration Provisioned Value: V8bis Signal ctyp/v8bis O ADD, MOD. AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Signal Name, v8bsn O ALL Yes Signal Contents, v8bcont O ALL Empty String Signals Mandatory/ Optional Used in command: Duration Provisioned Value: V18 Probe, ctyp/v18prob O ADD, MOD. AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - Events Mandatory/ Optional Used in command: Detected Discrimination Tone, ctyp/dtone M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Tone Type, dtt M ALL - Tone Value, dtvalue O ALL - V8bis Type, v8bist O ALL - Events Mandatory/ Optional Used in command: Call Type Discrimination Result, ctyp/calldisres O ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Discriminated call Type, dct M ALL - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 51
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.23 Stimulus analog line (stimal)
|
Table 84: Stimulus analog line package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Pulsed Signal (stimal/pulsedsig) M ADD, MODIFY, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Signal (sig) M ALL Duration provisioned in the AGW. Number of Pulses (numofpulses) O - 1 Steady Signal (stimal/stedsig) M ADD, MODIFY, AUDIT VALUE On/Off Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Signal (sig) M ALL - Digits (stimal/digits) O MODIFY, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: Digits (digit) M ALL Not applicable. Autonomous Signalling Sequence (stimal/autosigseq) O MODIFY, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: Sequence Type (seqtype) M ALL Not applicable. Call Finished (stimal/cfin) O MODIFY, AUDIT VALUE Brief Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: None. - - - Events Mandatory/ Optional Used in command: Steady Signal (stimal/stedsig) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Signal to Detect (detectsig) M ALL Recognition Time (rectime) O provisioned default for each steady signal ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Detected Signal (sig) M ALL Line Information (lineinfo) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Line Information (info) M ALL ETSI ETSI TS 183 002 V3.3.1 (2009-08) 52 Pulsed Signal (pulsedsig) M ADD. MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Signal to Detect (detectsig) M ALL Recognition Time (rectime) O - provisioned per pulsed signal ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Detected Signal (sig) M ALL Autonomous Signalling Sequence Response (autosigseqresp) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: None ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Sequence Response Type (seqresptype) M ALL Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None -
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.24 MGC information (MGCInfo)
|
Table 85: MGC Information Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: Data Block (MGCInfo/db) M ADD, MODIFY, AUDITVALUE A range of 0 to 32 octets An empty string 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: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 53
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.25 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 Mandatory/ Optional Used in command: Conditional Reporting, scr/cr M ADD, MODIFY, MOVE, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Statistic Identifier, si M ALL YES Duration, dur O ALL YES Period, per O ALL YES Maximum, max O ALL YES Minimum, min O ALL YES Normal, nor O On, Off YES Request timestamp, rt O ALL YES Value type, typ O ALL YES Target value, val O ALL YES Deviation, dev O ALL None Compliance, com O ALL None Direction, dir O ALL YES ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Statistic Identifier, si M ALL - Value, val M ALL - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 54
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.26 ETSI Notification Rate Package (etsi_nr)
|
Table 87: ETSI Notification Rate Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: Notification Rate (etsi_nr/notrat) M ADD, MODIFY, AUDITVALUE A range of 1 to 8 octets - Off-hook Notification (etsi_nr/offHookNot) M ADD, MODIFY, AUDITVALUE All YES 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: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None -
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.27 RTP Application Data Package (rtpad)
|
Table 88: 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 Mandatory/ Optional Used in command: None Statistics Mandatory/ Optional Used in command: Supported Values: RTP payload octets sent, (rtpad/payloados) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY RTP payload octets received, (rtpad/payloador) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 55
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.28 Keepalive Request (kar)
|
Table 89: Keepalive Request Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: Send Keepalive Packet (kar/skap) M ADD, MODIFY NA Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: fa M ALL - rti O ALL 1500 kast O ALL no (0x0004) RTP Packet with No-Op Payload Events Mandatory/ Optional Used in command: None - - Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 002 V3.3.1 (2009-08) 56
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.14.2.29 Digit Dialling Method Information for Extended Digit Map Detection (xdmi)
|
Table 90: Digit Dialling Method Information for Extended Digit Map Detection package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Provisioned Value: - - - - Events Mandatory/ Optional Used in command: Extended DigitMap Completion, xdmi/xce M ADD, MOD, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Buffer control, bc M Integer - Extra digit disposition, xdd O ON, OFF - Match procedure, mp M base, enhanced - Dial Method Required, dmr O ON, OFF OFF ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Digit string, ds M ALL - Termination method, meth M "UM", "PM", "FM" - Unmatched event, extra M String - Dialling Method, dm O "LD", "DTMF" - Events Mandatory/ Optional Used in command: DTMF digits, xdmi/* M ADD, MOD, NOTIFY Event Parameters Mandatory/ Optional Supported Values: Provisioned Value: Dial Method Required, dmr O ON, OFF OFF ObservedEvent Parameters Mandatory/ Optional Supported Values: Provisioned Value: Dialling Method, dm O "LD", "DTMF" - Statistics Mandatory/ Optional Used in command: Supported Values: None - - - Error Codes Mandatory/Optional None - 5.15 Mandatory support of SDP and annex C information elements The v=, o=, s=, m=, c=, t=, a= and b= lines of the SDP (see RFC 2327 [34]) syntax shall be supported. All other lines should be ignored if received. NOTE: "Annex C" relates to H.248.1 Annex C "Tags for Media Stream Properties". ETSI ETSI TS 183 002 V3.3.1 (2009-08) 57 Table 91: Supported SDP Information Elements Supported annex C and SDP information elements Information element Annex C support SDP support Protocol version (v=) Not Supported The protocol version (v=) line contains a single field: v= <version> and shall be used in accordance with RFC 2327 [34] (i.e. v=0). Origin (o=) Not Supported The origin line consists of 6 fields: o= <user name> <session ID> <version> <network type> <address type> <address>. The MGC is not required to supply this line but shall accept it. The MG should populate this line as follows or use the value received from the MGC: - <user name> should contain a hyphen. - <session ID> and <version> should contain one or more digits as described in RFC 2327 [34]. - <network type> shall be set to IN. - <address type> shall be set to IP4 or IP6 The Address Type shall be set to "IP4" or "IP6" depending on the addressing scheme used by the network to which the MG is connected. - <address> should contain the fully qualified domain name of the gateway. Session Name (s=) Not Supported The session name (s=) line contains a single field: s= <session-name>. The MGC is not required to supply a session name but shall accept one. This line may be used to convey correlation information for use in CDRs. The MG shall use a hyphen "-" as a session name or the value received from the MGC. Connection data (c=) Not Supported The connection data line consists of 3 fields: c= <network-type> <address-type> <connection-address> - The <network-type> shall be set to "IN". - The <address-type> shall be set to "IP4" or "IP6" depending on the addressing scheme used by the network to which the MG is connected. - The <connection-address> sent by the MGC in the remote descriptor is the address to which the MG shall send the media flows. - The <connection-address> sent by the MGC in local descriptors may be a unicast IPv4 or IPv6 address or it may be wildcarded to allow the MG to choose an address. In the second case, MGs shall fill this field with a unicast IP address at which they will receive the media stream. Thus a TTL value shall not be present and a "number of addresses" value shall not be present. The field shall not be filled with a fully-qualified domain name instead of an IP address. When the <connection address> is wildcarded (i.e. choose wildcard) by the MGC, the MG allocates an IP address based on the address type. The addressing space for which this address is taken may depend on the termination ID supplied by the MGC. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 58 Supported annex C and SDP information elements Information element Annex C support SDP support Media announcements (m=) Not Supported Media Announcements (m=) lines consist of 3 fields: m= <media> <port> <transport> <format> - The <media> field shall be set to "audio", except in case of T.38 fax transmission where it shall be set to "image". - The <port> field in remote descriptors is provided by the MGC and represents the port to which the MG shall send the media flows. - The <port> field in local descriptors may be provided by the MGC or wildcarded (i.e. choose wildcard) to allow the MG to choose a value for the port on which it wishes to receive the media stream. - The <transport> field shall be set to "RTP/AVP" except in case of T.38 Fax relay and V.150.1 Modem relay, where it shall be set to "udptl" or "udpsprt" (respectively). - The <format> field may be explicitly supplied by the MGC, wildcarded or overspecified. If the MGC wishes to request the MG to choose which media formats it wishes to use for the call then the MGC shall provide a "$" wildcard. If the MGC wishes to suggest that the MG selects a media format from a list of possible media formats then it shall provide a list of appropriate media types in accordance with SDP. All conforming gateways shall support at least format "8" for RTP/AVP (i.e. ITU-T Recommendation G.711 [27] A-Law). Dynamic payloads shall not be used when a static RTP/AVP payload value is defined in RFC 3551 [35]. Bandwidth (b=) Not Supported The Bandwidth (b=) line consists of 2 fields: b= <modifier>: <bandwidth-value> Bandwidth information shall be supplied by the MGC if the required bandwidth cannot be immediately derived from the information contained in the m= line. If absent, the MG shall assume a reasonable default bandwidth value for well-known codecs and shall provide this value in the response sent to the MGC. The Modifier field shall be set to "AS". The Bandwidth Value field shall be set to the maximum bandwidth requirement of the media stream in kbit/s. The bandwidth value shall take into account all headers down to the IP layer, including a 5 % bandwidth for RTCP packets. Time (t=) Not Supported The time (t=) line consists of two fields: t= <start-time> <stop-time>. This line is ignored by both the MGC and the MG if received in local and remote descriptors. The MGC is not required to supply a time description but shall accept one. When supplied, this line shall be set to 0 0. Attributes (a=) Not Supported Attributes (a=) lines consist of two fields: a= <attribute>: <value> One or more of the "a" attribute lines specified below may be included, depending on the payload type. An attribute line not specified below should not be used. Only the following attributes are understood by the MG. Other attributes are ignored. a= rtpmap: <payload type> <encoding name>/<clock rate> [/<encoding parameters>] a= fmtp:<format> <format specific parameters> a= ptime: <time> ETSI ETSI TS 183 002 V3.3.1 (2009-08) 59
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
5.16 Procedures
|
Procedures for ephemeral H.248 terminations (here IP only) are described in clause 6. Procedures for physical H.248 terminations are described in clauses 7.2 and 7.3 providing the specifics of ANALOG and ISDN H.248 terminations respectively.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6 Procedures at the IP side
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6.1 General procedures
|
Media GateWays (MGWs) shall discard packets with RTP Payload Types (PT) that do not match the Local Descriptor contents. NOTE 1: Besides an incorrect RTP PT field might be also other reasons for discarding packets (invalid SSRC field, invalid CRC, etc.). NOTE 2: The MG has the option to collate statistics on discarded packets. When sending packets from a termination, Media GateWays (MGWs) shall use the address and port in the Local Descriptor as a source address and port.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6.2 Voiceband Data (VBD)
| |
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6.2.1 General
|
Voiceband data refers to traffic from facsimile/modem, data/modem or text/modem telephony applications. NOTE 1: The term "fax/modem" denotes traffic from so called Group 3 Fax Equipment (G3FE), which uses a suite of modem protocols for transport of image data and T.30/T.4 control data. There are also modem-less fax terminals like G4FE types ("ISDN fax"), using ITU-T I.231.1 as bearer service in the ISDN domain and RFC 4040 as bearer service emulation in the IP domain. Upon detection of voiceband data traffic, the Media GateWay (MGW) shall autonomously switch from Audio mode to VBD mode with G.711 codec (as V.152 VBD codec) if the H.248 Remote Descriptor indicates that ITU-T Recommendation G.711 [27] is supported by the peer entity. The VBD codec can be derived at start of the audio call by one of the following methods: • the corresponding signalled ITU-T Recommendation V.152 [32] SDP elements; or • if V.152 SDP elements are not signalled (in case of v1/v2 ARGWs), derived from the Remote Descriptor carrying G.711 codec (with RTP payload type 0 or 8); or • if V.152 SDP elements are not used and the Remote Descriptor does not carry G.711 codec, known because this profile defines G.711 with RTP payload type '8' as default VBD codec. The default VBD codec can be overwritten through management plane (e.g. changing from G.711 PT = 8 to G.711 PT = 0): - This behaviour shall be only applied for PES scenarios, i.e. PSTN-to-PES-to-PSTN (which includes PSTN-to-IMS-to-PSTN) network configurations. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 60 - This behaviour shall be not applied if any of the following scenarios are true: When the ARGW is directly peering an IMS user equipment, i.e. a PSTN-to-IMS or IMS-to-PSTN scenario (because an IMS end point may have no use for VBD at all and may not demand G.711 as a voice codec). The MGC is not able to discriminate whether the incoming call is from an IMS UE or going via a remote PSTN gateway, e.g. due to number portability; Multiple network domains are interconnected via border gateways. For scenarios where the VBD codec cannot be derived as described above at the start of an audio call, the MGC should apply MGC controlled VBD transitioning by means of: • subscribe for VBD event detection via H.248.2 event subscription as described in clause 6.2.4; • upon receiving notification of a VBD stimuli event, the MGC should modify the MG connection to swap over to G.711 codec as described in clause 6.2.4. MGC controlled VBD transitioning shall not be applied for PES scenarios, i.e. PSTN to PES to PSTN. When the PES domain shall support T.38 FoIP in addition to V.152, then the MGC may request T.38 support by subscription to a facsimile specific VBD event (like e.g. CNG, V.21 flags). NOTE 2: This means that ITU-T Recommendation G.711 [27] may be used for audio mode and is used for the VBD mode. Using PCMA (or PCMU) for VBD mode but not for audio (e.g. because G.729 is used for voice) allows the usage of the static RTP PT value for the VBD codec. Using PCMA (or PCMU) for audio and VBD mode implies a dynamic RTP PT value for the VBD codec in order to be able in discriminating RTP packets for each mode. NOTE 3: If G.711 is not present in the H.248 Remote Descriptor and the ARGW does not support a default VBD codec via the management plane, the connection is modified under MGC control to include the G.711 codec - see clause 6.2.4. Transitioning between Audio mode and VBD mode is possible in both directions. The procedures for transitioning between these two operation modes are described in clause 10 of ITU-T Recommendation V.152 [32]. Any state transition requires the detection of a "VBD stimuli" (see clause 9 of ITU-T Recommendation V.152 [32]). The relevant stimuli for this H.248 Profile are summarized in table 92. Autonomous state transitioning means that the MGC is not controlling the operation mode changes in the MG. The MG is detecting potential trigger events and deciding itself state transitioning according to ITU-T Recommendation V.152 [32] rules. The MG autonomous mode does not preclude a notification of the MGC by the MG. The VBD mode of operation shall be implemented as defined in ITU- T Recommendation V.152 [32], which involves: • disabling Voice Activity Detection and Comfort Noise Generation if any of these had been activated; • ensuring end-to-end constant latency; • ensuring that voice packet loss concealment techniques and algorithms that may be employed are suitable for modem and facsimile modulations; and • disabling any DC removal filters that may be integral with the speech encoder used. The use of echo cancellers shall be as per ITU-T Recommendation G.168 [41]. No explicit negotiation of the VBD mode is required, beyond the support of ITU-T Recommendation G.711 [27], in case of provisioned RTP PT values, in all V.152 gateways of the IP network, for the VBD codec. ITU-T Recommendation V.152 [32] procedures are applied when provisioning is not supported or done. Voiceband data traffic shall be detected by monitoring the VBD stimuli according clause 9 of ITU-T Recommendation V.152 [32] and the tones described in table 92. NOTE 4: There is some overlapping between both event lists. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 61 Table 92: VBD mode triggering events "Tone" Description CNG a T.30 fax calling V.21flag a V.21 tone and flags CIV18 a V.8 CI with V.18 call function XCI a V.18 XCI V18txp a V.18 "txp" Belltone a Bell 103 carrier, either the high or the low frequency channel (as defined in V.18) Baudot a Baudot initial tone and character (as defined in V.18) Edt an EDT initial tone and character (as defined in V.18) CIdata a V.8 CI with any data call function CT a V.25 calling tone CIfax a V.8 CI with facsimile call function V21tone a V.21 carrier, either the high or the low frequency channel V23tone a V.23 carrier, either the high or the low frequency channel V8bis a V.8bis modem handshaking signal ANS (see note) V.25 ANS, equivalent to T.30 CED from answering terminal ANSAM (see note) V.8 ANSam NOTE: Including both the absence and the presence of phase reversal. Payload transitions may be notified to the MGC using the Payload Transition event defined in the RTP package (rtp/pltrans, see clause E.12.2.1/H.248.1). The Media GateWays (MGWs) may also report the above to the MGC using the Discrimination tone event in the Call Type Discrimination package. Automatic switch over to VBD mode does not preclude the gateways from negotiating support of other mechanisms such as Forward Error Correction (FEC) (e.g. RFC 2733 [42]) or other forms of Redundancy (e.g. RFC 2198 [43]). Media GateWays (MGWs) may also support relay mode for fax and modem, based on the procedures described in ITU-T Recommendations T.38 [30] and V.150.1 [31]. Autonomous switch over to such payload types shall only occur if successfully negotiated with the remote side.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6.2.2 Interworking between V.152-compliant GWs
|
A ARGW implementation according to this profile version provides a V.152-compliant GW function (see clause 6.2.1). For a connection between two such GWs, the media capability and bearer capability negotiation procedures are defined by ITU-T Recommendation V.152 [32]. As stated in ITU-T Recommendation V.152 [32], VBD may be handled in either assured or non-assured mode. The distinction between these modes is defined by the mandatory capabilities of V.152, i.e. with/without RTP transport redundancy (according RFC 2198 [43]) and forward error correction of RTP packets (according to RFC 5109 [65]) for assured/non-assured mode. In TISPAN networks, it is expected that the non-assured VBD mode should be sufficient. In either mode, modem signals may either be transported with/without RTP payload format for telephony events (according to RFC 4733 [37] and RFC 4734 [66]).
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6.2.3 Interworking between V.152-compliant and non-V.152 GWs
|
This clause describes the inter-working between V.152 compliant and non-V152 compliant ARGWs. The essential difference between these ARGWs is in their support of a separate dynamic RTP payload for VBD handling (as described in ITU-T Recommendation V.152 [32]). All other aspects of VBD handling (e.g. silence suppression, echo control, jitter buffer freezing etc.) are common between V.152 compliant and non-V152 compliant ARGWs. The following clauses deal with inter-working between a V.152 compliant and non-V152 compliant ARGW and vice-versa. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 62 6.2.3.1 Call/Session Originating on non-V.152 Compliant ARGW and Terminating on a V.152 Compliant ARGW The following steps are carried out on the H.248 interface: 1) The MGC requests a LD from the originating non-V.152 compliant ARGW. The LD passed to the ARGW in the H.248 Command contains payload type 8 (A-law) and MAY also contain a dynamic payload type for VBD, as described in ITU-T Recommendation V.152 [32]. The ARGW returns a LD to the MGC containing payload 8. 2) The MGC requests the terminating V.152 compliant ARGW to create an ephemeral termination and passes down a LD containing payload 8 and optionally a dynamic payload for VBD (in line with V.152). Note that the dynamic payload may be omitted based on the fact that it is absent from the in-hand RD (which is also passed down to the terminating ARGW). In either case, the terminating ARGW shall return only payload 8 (i.e. even if the MGC requests a separate dynamic payload for VBD, there is no point in allocating the additional payload due to its absence in the in-hand RD). 3) The MGC passes the RD down to the originating ARGW. The result of this negotiation is that payload 8 has been agreed for the connection between the ARGWs. On detection of VBD stimuli, both ARGWs will transition into VBD mode but the same payload number (8) shall be used for both VBD and audio. This is illustrated in the example below: ETSI ETSI TS 183 002 V3.3.1 (2009-08) 63 Table 92a: Example H.248 Stream Descriptor - Originating ARGW (non V.152-compliant) side: step 1 H.248 encoding (shortened command) Comments 1) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Add = al/3/2/78 { ; Analog Line Termination Media { Stream = 1 { LocalControl{ tdmc/gain=7, ; in dB tdmc/ec=on ; in dB }, … } Add = ephemeral/2/3/$ { ; Ephemeral Termination Media { Stream = 1 { LocalControl{ Mode=SendReceive, ReservedGroup = OFF, ReservedValue = OFF ; because just a single }, ; audio codec Local{ v=0 c=IN IP4 $ m=audio $ RTP/AVP 8 101 111 a=maxmptime:20 - 30 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 a=rtpmap:111 PCMA/8000 ; ITU-T V.152 a=gpmd:111 vbd=yes } }}} Physical termination: The MGC enforces gain control and enables EC on the physical termination. IP termination: In this example, the MGC requests (from the local MG) an PCMA audio codec with telephone-events and a PCMA VBD codec. The Reserve property values are false due to single group and single "media format" for Stream 1 (see note). Local Descriptor: The MGC selects RTP PT equals to 111 for the VBD codec due to MGC provisioning. Ditto for RFC 4733 [37] and RFC 4734 [66] codec. The maxptime attribute is used in this example due to different packetization times in each state. Remote Descriptor: Not present. 2) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Add = al/3/2/78 { … } Add = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 } }}} IP termination: The audio codec is accepted and allocated. The V.152 and RFC 4733 [37] and RFC 4734 [66] SDP elements are removed because neither understood nor supported by the originating MG.. VBD: The MG must emulate a VBD behaviour according clause 6/V.152, i.e. shall disable (if required) the adaptive jitter buffer behaviour, disable voice activity detection, disable CNG and disable DC removal filters. NOTE: RFC 4733 [37] and RFC 4734 [66] and V.152 are supplementary media formats with regards to the audio format, see clause 7.1.7.1.3/H.248.1. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 64 Table 92b: Example H.248 Stream Descriptor - Terminating ARGW (V.152-compliant) side: step 2 H.248 encoding (shortened command) Comments 1) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Add = al/3/2/77 { ; Analog Line Termination Media { Stream = 1 { LocalControl{ tdmc/gain=7, ; in dB tdmc/ec=on ; in dB }, … } Add = ephemeral/2/3/$ { ; Ephemeral Termination Media { Stream = 1 { LocalControl{ Mode=SendReceive, ReservedGroup = OFF, ReservedValue = OFF ; because just a single }, ; audio codec Local{ v=0 c=IN IP4 $ m=audio $ RTP/AVP 8 101 111 a=maxmptime:20 - 30 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 a=rtpmap:111 PCMA/8000 ; ITU-T V.152 a=gpmd:111 vbd=yes }, Remote{ v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 } }}} Physical termination: The MGC enforces gain control and enables EC on the physical termination. Ephemeral termination: In this example, the MGC requests an PCMA audio codec with telephone-events and (optionally) a PCMA VBD codec. The Reserve property values are false due to single group and single "media format" for Stream 1 (see note). Local Descriptor: The MGC selects RTP PT equals to 111 for the VBD codec due to MGC provisioning. Ditto for RFC 4733 [37] and RFC 4734 [66] codec. The maxptime attribute is used in this example due to different packetization times in each state. Remote Descriptor: The MGC is just forwarding the remote media description, without checking the media capabilities. 2) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Add = al/3/2/77 { … } Add = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 }, Remote{ ; returning the RD is optional v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 } }}} Ephemeral termination: The MG must compare and correlate LD and RD information. As the originating MG is not supporting V.152, it removes all related V.152 SDP from the local descriptor. Furthermore as the originating MG doesn't support RFC 4733 [37] and RFC 4734 [66] the corresponding lines are removed from the replied LD as well. Physical termination: When being in the VBD state, the MG is thus "ignoring" the requested gain control and echo control settings. E.g. the MG must autonomously enable/disable EC according G.168/V.152 concerning modem protocol handling. VBD: The MG must emulate a VBD behaviour according clause 6/V.152, i.e. shall disable (if required) the adaptive jitter buffer behaviour, disable voice activity detection, disable CNG and disable DC removal filters. NOTE: RFC 4733 [37] and RFC 4734 [66] and V.152 are supplementary media formats with regards to the audio format, see clause 7.1.7.1.3/H.248.1. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 65 Table 92c: Example H.248 Stream Descriptor - Originating ARGW (non V.152-compliant) side: step 3 H.248 encoding (shortened command) Comments 1) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Modify = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { Remote{ v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 } }}} Ephemeral termination: The MGC forwards the received LD from the terminating MG as RD to the originating MG. 2) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Modify = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Remote{ ; returning the RD is optional v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 } }}} IP termination: The MG must compare and correlate LD and RD information. Conclusion by MG: peer node is neither supporting RFC 4733 [37] and RFC 4734 [66] nor V.152. LD doesn't need to be updated. 6.2.3.2 Call/Session Originating on V.152 Compliant ARGW and Terminating on a non-V.152 Compliant ARGW The following steps are carried out on the H.248 interface: 1) The MGC requests a LD from the originating V.152 compliant ARGW. The LD passed to the ARGW in the H.248 Command contains both payload type 8 (A-law) and also a dynamic payload type for VBD, as described in ITU-T Recommendation V.152 [32]. The V3 ARGW returns a LD to the MGC containing both payload 8 and the dynamic VBD payload. 2) The MGC requests the terminating non-V.152 complaint ARGW to create an ephemeral termination and passes down a LD containing payload 8 and a dynamic payload for VBD (in line with V.152). The RD (containing the originating ARGW SDP) is also passed down to the terminating ARGW. The terminating ARGW returns only payload 8 in the returned LD to the MGC since it did not understand the V.152 related SDP. 3) The MGC passes the terminating ARGW SDP as the RD to the originating ARGW. The originating ARGW notes that there is no dynamic VBD codec in the RD. The originating ARGW may return a modified LD in the command response to the MGC (i.e. having removed the dynamic V.152 payload). ETSI ETSI TS 183 002 V3.3.1 (2009-08) 66 The result of this negotiation is that only payload 8 has been agreed for the connection between the ARGWs. On detection of VBD stimuli, both ARGWs will transition into VBD mode but the same payload number (8) shall be used for both VBD and audio. This is illustrated in the example below: Table 92d: Example H.248 Stream Descriptor - Originating ARGW (V.152-compliant) side: step 1 H.248 encoding (shortened command) Comments 1) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Add = al/3/2/78 { ; Analog Line Termination Media { Stream = 1 { LocalControl{ tdmc/gain=7, ; in dB tdmc/ec=on ; in dB }, … } Add = ephemeral/2/3/$ { ; Ephemeral Termination Media { Stream = 1 { LocalControl{ Mode=SendReceive, ReservedGroup = OFF, ReservedValue = OFF ; because just a single }, ; audio codec Local{ v=0 c=IN IP4 $ m=audio $ RTP/AVP 8 101 111 a=maxmptime:20 - 30 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 a=rtpmap:111 PCMA/8000 ; ITU-T V.152 a=gpmd:111 vbd=yes } }}} Physical termination: The MGC enforces gain control and enables EC on the physical termination. IP termination: In this example, the MGC requests (from the local MG) an PCMA audio codec with telephone-events and a PCMA VBD codec. The Reserve property values are false due to single group and single "media format" for Stream 1 (see note). Local Descriptor: The MGC selects RTP PT equals to 111 for the VBD codec due to MGC provisioning. Ditto for RFC 4733 [37] and RFC 4734 [66]4 codec. The maxptime attribute is used in this example due to different packetization times in each state. Remote Descriptor: Not present. 2) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Add = al/3/2/78 { … } Add = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 101 111 a=maxmptime:20 - 30 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 a=rtpmap:111 PCMA/8000 ; ITU-T V.152 a=gpmd:111 vbd=yes } }}} IP termination: The audio codec is accepted and allocated and the V.152 and RFC 4733 [37] and RFC 4734 [66] SDP elements are kept. VBD: The MG support V.152 compliant VBD behaviour NOTE: RFC 4733 [37] and RFC 4734 [66] and V.152 are supplementary media formats with regards to the audio format, see clause 7.1.7.1.3/H.248.1. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 67 Table 92e: Example H.248 Stream Descriptor - Terminating ARGW (non-V.152-compliant) side: step 2 H.248 encoding (shortened command) Comments 1) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Add = al/3/2/77 { ; Analog Line Termination Media { Stream = 1 { LocalControl{ tdmc/gain=7, ; in dB tdmc/ec=on ; in dB }, … } Add = ephemeral/2/3/$ { ; Ephemeral Termination Media { Stream = 1 { LocalControl{ Mode=SendReceive, ReservedGroup = OFF, ReservedValue = OFF ; because just a single }, ; audio codec Local{ v=0 c=IN IP4 $ m=audio $ RTP/AVP 8 101 111 a=maxmptime:20 - 30 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 a=rtpmap:111 PCMA/8000 ; ITU-T V.152 a=gpmd:111 vbd=yes }, Remote{ v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 101 111 a=maxmptime:20 - 30 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 a=rtpmap:111 PCMA/8000 ; ITU-T V.152 a=gpmd:111 vbd=yes } }}} Physical termination: The MGC enforces gain control and enables EC on the physical termination. Ephemeral termination: In this example, the MGC requests an PCMA audio codec with telephone-events and (optionally) a PCMA VBD codec. The Reserve property values are false due to single group and single "media format" for Stream 1 (see note). Local Descriptor: The MGC selects RTP PT equals to 111 for the VBD codec due to MGC provisioning. Ditto for RFC 4733 [37] and RFC 4734 [66] codec. The maxptime attribute is used in this example due to different packetization times in each state. Remote Descriptor: The MGC is just forwarding the remote media description, without checking the media capabilities. 2) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Add = al/3/2/77 { … } Add = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 101 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 }, Remote{ ; returning the RD is optional v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 101 111 a=maxmptime:20 - 30 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 a=rtpmap:111 PCMA/8000 ; ITU-T V.152 a=gpmd:111 vbd=yes } }}} Ephemeral termination: The MG must compare and correlate LD and RD information. As the terminating MG is not supporting V.152, it removes all related V.152 SDP from the local descriptor. However, as the terminating MG does support RFC 4733 [37] and RFC 4734 [66] the corresponding lines are kept within the LD. Physical termination: When being in the VBD state, the MG is thus "ignoring" the requested gain control and echo control settings. E.g. the MG must autonomously enable/disable EC according G.168/V.152 concerning modem protocol handling. VBD: The MG must emulate a VBD behaviour according clause 6/V.152, i.e. shall disable (if required) the adaptive jitter buffer behaviour, disable voice activity detection, disable CNG and disable DC removal filters. NOTE: RFC 4733 [37] and RFC 4734 [66] and V.152 are supplementary media formats with regards to the audio format, see clause 7.1.7.1.3/H.248.1. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 68 Table 92f Example H.248 Stream Descriptor - Originating ARGW (V.152-compliant) side: step 3 H.248 encoding (shortened command) Comments 1) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Modify = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { Remote{ v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 101 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 } }}} Ephemeral termination: The MGC forwards the received LD from the terminating MG as a RD to the originating MG. 2) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Modify = ephemeral/2/3/99 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 101 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 }, Remote{ ; returning the RD is optional v=0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 101 a=rtpmap:101 telephone-event/8000 ; RFC 4733/4 } }}} IP termination: The MG must compare and correlate LD and RD information. Conclusion by MG: peer node is not supporting V.152, but supports RFC 4733 [37] and RFC 4734 [66]. Thus, just the LD is updated accordingly and returned to the MGC. VBD: The MG must emulate a VBD behaviour according clause 6/V.152, i.e. shall disable (if required) the adaptive jitter buffer behaviour, disable voice activity detection, disable CNG and disable DC removal filters.
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6.2.4 VBD Transition - Change to G.711 Codec under MGC Control
|
This clause describes the transition from audio to VBD mode at a ARGW when the G.711 codec is not present n the H.248 Remote Descriptor and the current call scenario does not allow the use of a default VBD codec defined via the management plane (see clause 6.2.1). It is expected that this situation would occur for calls/sessions originating in a non-TISPAN network and terminating on a ARGW. NOTE: It is strongly recommended that, for calls/sessions originating on a TISPAN compliant ARGW, the G.711 codec always be initially present in the Local Descriptor of the originating ARGW and conveyed to the far end media end point. Note that this behaviour implies that property ReserveValue is equal to ON. Upon detection of VBD triggering event, the Media GateWay (MGW) shall report the detected event to the MGC (i.e. it is assumed that that the MGC had previously armed the ctyp/dtone event (see clause 5.14.2.22). In addition, the Media GateWay (MGW) may optionally freeze its jitter buffer, disable silence suppression and comfort noise generation and modify its echo canceller as per ITU-T Recommendation G.168 [41] prior to the VBD codec negotiation. On being informed of the ctyp/dtone event, the MGC shall modify the MG connection to swap over to the G.711 codec via the following steps on the H.248 interface: 1) The MGC requests the ARGW to modify its LD to include the G.711 codec. The LD passed to the ARGW in the H.248 Command shall contain RTP payload type 8 (A-law), may contain payload type 0 (Mu-law) and shall also contain the current/existing compressing audio codec. For a V3 ARGW, the MGC shall also include the V.152 media attribute line to indicate that the G.711 codec is a VBD codec. For a V2 ARGW, the MGC may include the V.152 media attribute line to indicate that the G.711 codec is a VBD codec. The inclusion of payload type 0 shall be a network option (optionally inclusive of the VBD media attribute line as in the case of payload type 8). ETSI ETSI TS 183 002 V3.3.1 (2009-08) 69 The ARGW returns a LD to the MGC containing RTP payload type '8', the existing compressing codec and optionally payload type '0' (if requested by MGC). The VBD media attribute shall be returned from a V3 ARGW and may be returned from a V2 ARGW. 2) The MGC passes the modified LD to the far end media endpoint (e.g. via a new SDP OFFER/ANSWER exchange via a SIP RE-INVITE / UDPDATE). The MGC may choose to omit the previously negotiated audio codec at this point. 3) The MGC receives modified SDP (containing the G.711 codec (optionally with the VBD media attribute) and optionally the previously negotiated audio codec from the far end media end point (e.g. in a SDP ANSWER) and passes the required SDP media description to the ARGW as a new Remote Descriptor. If the SDP ANSWER does not contain the previously negotiated audio codec, then the LD is also changed to include only G.711. The result of this negotiation is that the media connection has been modified to use the G.711 codec as VBD codec. At this point, the MG has transitioned into VBD mode (as described in clause 6 of ITU-T Recommendation V.152 [32]). This sequence is illustrated in table 92g. Note that if G.711 is not contained in the SDP ANSWER, then the MGC shall initiate appropriate exception handling (e.g. apply an announcement and/or release the call). Such exception handling is out of scope of this profile. Table 92g: Example H.248 Stream Descriptor - Terminating ARGW H.248 encoding (shortened command) Comments Initial Conditions: Assume that the ARGW has in in-hand LD & RD containing a common compressing codec (e.g. G.729), and that the physical termination has been armed to notify the MGC of detection of fax / modem tones. 1) Notification (MG to MGC): MEGACO/2 [11.9.19.65]… … Notify = al/3/2/78 { ; Analog Line Events=1234{ctype/dtone{dtt=ANS} } } The MG detects a modem answer tone on its physical termination and notifies the MGC via the ctyp/dtone event. 2) Reply (MGC to MG): MEGACO/2 [11.9.19.65] … Notify = al/3/2/78 } The MGC acknowledges the notification. The MGC determines that the G.711 codec must be used on this connection to support the modem call. 3) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Modify = ephemeral/2/3/1 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{ Mode= Sendrecv, ReservedGroup = OFF, ReservedValue = ON ; because > 1 }, ; audio codec Local{ v=0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 18 a=gpmd:vbd=yes } }}} The MGC requests the MG to modify the ephemeral termination to use the G.711 codec. The VBD media attribute line is included in the LD. 4) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Add = ephemeral/2/3/1 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 The MG modifies its LD (containing the VBD media attribute line) and replies to the MGC. The RD is optional in this message. In this flow, it is assumed that the MGC sends a SDP OFFER containing only the G.711 codec. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 70 H.248 encoding (shortened command) Comments m=audio 33906 RTP/AVP 8 18 a=gpmd:vbd=yes }, Remote{ ; returning the RD is optional v=0 o=- 0 0 IN IP4 another.domain s=H.248 Context t=0 0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 18 } }}} 5) Request (MGC to MG): MEGACO/2 [11.9.19.65] … Modify = ephemeral/2/3/1 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{ Mode=Sendrecv ReservedGroup = OFF, ReservedValue = OFF ; because just a single }, ; audio codec Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 a=gpmd:vbd=yes }, Remote{ v=0 o=- 0 0 IN IP4 another.domain s=H.248 Context t=0 0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 } }}} The SDP ANSWER confirms that SDP of the far end point is changed to contain the G.711 codec (without the VBD media attribute line). The MGC requests the MG to modify the ephemeral termination with a new RD. The LD is also modified to dispense with the compressing audio codec. 5) Reply (MG to MGC): MEGACO/2 [11.9.19.65] … Modify = ephemeral/2/3/1 { ; Ephemeral Termination Media { Stream = 1 { LocalControl{…}, Local{ v=0 o=- 0 0 IN IP4 blabla.domain s=H.248 Context t=0 0 c=IN IP4 11.9.20.01 m=audio 33906 RTP/AVP 8 a=gpmd:vbd=yes }, Remote{ ; returning the RD is optional v=0 o=- 0 0 IN IP4 another.domain s=H.248 Context t=0 0 c=IN IP4 19.70.3.2 m=audio 44038 RTP/AVP 8 } }}} The MG modifies its LD and RD and replies to the MGC. The connection is now using the G.711 codec (Tx direction), ETSI ETSI TS 183 002 V3.3.1 (2009-08) 71
|
dde9e2552d661348f67d747426d8c5c3
|
183 002
|
6.3 Support of ISDN unrestricted 64 kbit/s
|
When the MGC determines that a 64 kbit/s unrestricted bearer service is requested, the clearmode codec shall be used. A Dynamic Payload type with CLEARMODE as encoding name shall be included in both the local and remote descriptor. EXAMPLE: v= 0 c= IN <address type> <connection address> m= audio <port number> RTP/AVP 99 a= rtpmap: 99 CLEARMODE/80000 a= ptime: 10 The behaviour of the MG shall then conform to RFC 4040 [39]. All voice and signal processing functions such as echo cancellation, silence suppression, comfort noise insertion and gain adjustment shall be automatically turned off. The MG shall inherit the same QoS objectives than the ISDN bearer service.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.