hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.4 Comfort noise insertion and silence suppression | If a codec has built-in support for silence suppression and comfort noise insertion, the activation or deactivation of these features shall be indicated using the a= line according to RFC 3551 [35] and RFC 4855 [40]. If the selected codec does not have built in support for silence suppression and comfort noise (CN) insertion, the CN payload code (see RFC 3389 [51]) may be included in the media description. EXAMPLE: (for ITU-T Recommendation G.711 [27]): v= 0 c= IN <address type> <connection address> m= audio <port number> RTP/AVP 0 13 a= ptime: 10 If the CN payload is included in the Local Descriptor, the MG shall be prepared to receive CN packets during silence periods. If the CN payload is included in the Remote Descriptor, the MG shall send CN packets during silence periods. Comfort noise analysis, voice activity detection and discontinuous transmission algorithms are outside the scope of the present document. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.5 DTMF transmission | When a G.711 codec is used (see ITU-T Recommendation G.711 [27]), Media GateWays (MGWs) shall be able to generate, detect and forward DTMF tones inband. When other codecs are used, the MGC should request the use of the procedures defined in RFC 4733 [37] to send and receive DTMF tones: • If the Local Descriptor sent by the MGC includes the support for RFC 4733 [37], Media GateWays (MGWs) shall be prepared to receive DTMF tones in the form of named events and relay the appropriate audio signal to the physical terminations. • If the Remote Descriptor indicates that RFC 4733 [37] is supported, Media GateWays (MGWs) shall be prepared to relay in the form of named events, any DTMF tone received from the physical terminations. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 72 A Dynamic Payload type shall be used to indicate support of RFC 4733 [37] for DTMF relay. EXAMPLE: v= 0 c= IN <address type> <connection address> m= audio <port number> RTP/AVP 18 110 a= ptime: 10 a= rtpmap: 110 telephone-event/8000 a= fmtp: 110 0-15 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.6 Call progress tones | Call progress tones shall be sent in-band using a voice codec. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.7 Support of G.711 variants | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.7.1 G.711 encoding law | Media GateWays (MGWs) conforming to the present document are required to support ITU-T Recommendation G.711 [27] A-Law and may also support μ-Law in order to avoid call failure or transcoding in case the remote entity supports μ-Law only. How and where to perform transcoding in IP networks in case both terminals/gateways do not support the same variant is outside the scope of this profile. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.7.2 G.711 silence suppression mode | ITU-T Recommendation G.711 [27] -over-IP may be operated with or without silence suppression. In case of silence suppression, comfort noise generation shall be based on ITU-T Recommendation G.711 Appendix II [29]. These features may be enabled/disabled on a per session basis, using the procedure described in clause 6.4. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.7.3 G.711 packet loss concealment | ITU-T Recommendation G.711 [27] -over-IP may be operated with or without error loss concealment. Typically is that decision dependent on the IP packet loss rate conditions. ITU-T Recommendation G.711 [27] error loss concealment is based on RTP packet granularity, therefore called as packet loss concealment (PLC). ITU-T Recommendation G.711, Appendix I [28] provides a framework for ITU-T Recommendation G.711 [27] PLC mode. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.8 MG-Internal redirection of RTP traffic | There might be situations where both RTP session endpoints will be located in the same media gateway (e.g. for a local call). This is related to the case where the two corresponding H.248 RTP terminations, of a single RTP session, belong to two different H.248 Contexts. If RTP traffic turnaround is not supported by the edge routers, it is recommended that the MG try to redirect internally the corresponding RTP/RTCP bearer traffic. This function is related to routing and forwarding of IP packet traffic. The function is therefore also known as MG-embedded IP Router function (figure 2). ETSI ETSI TS 183 002 V3.3.1 (2009-08) 73 Control Subsystem AGW/RGW AGW/RGW Context1 Phy1 RTP1 Context2 Phy2 RTP2 IP Router Data Path IP Forwarding Engine IP Transport Media Gateway Controller Internal IP Router => must be capable of IP Packet Forwarding for IP Packets with identical source & destination IP@s Analogue/ISDN Analogue/ISDN Figure 2: Single RTP session - internal bearer redirection via embedded IP router The MGC may resolve such a two-Context configuration by appropriate H.248 Commands. This may be done in a very early stage, i.e. already during call/bearer establishment phase, or in a later stage during active call phase. 6.9 Residential Media Gateway (RMG) - Keep pinhole open mechanisms for signalling and media traffic in IP domain due to NAT Traversal support |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.9.1 Problem statement in general | This profile supports residential and access gateways (clause 4.1). The physical MG would be located as Residential Media Gateway (RMG) on customer premises, or as an Access Media Gateway (AMG) on public network side (see figure 1). The media traffic (e.g. RTP-over-IP) and signalling traffic (H.248-over-IP) is transported by the IP network and may face network address translators ("NAT devices"). Any NAT device is separating an IP network in two or more IP address realms (briefly "realm"). There are following network configurations (from H.248 perspective): 1) MG and MGC located in the same IP realm; and - MG and peer IP bearer node located in the same IP realm; or - MG and peer IP bearer node located in the different IP realms; or 2) MG and MGC located in different IP realms; and - MG and peer IP bearer node located in the same IP realm; or - MG and peer IP bearer node located in the different IP realms. Traversal of a NAT device, - so called NAT Traversal support function -, may be thus needed in the IP-based bearer plane and/or IP-based control plane. This clause focuses on the different realms scenarios. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 74 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 6.9.2 Problem statement for multiple IP realm network configurations | The different realm configuration is the general case for RGW deployments. Figure 3 illustrates a more detailed network model with a NAT/FW device located at the border between customer network and public network. The RMG is on customer side located, the controlling RMGC is located in the public network. The NAT function is leading to two IP realms (internal and external; or private and public). H.248 signalling is consequently going through the same NAT/FW device as the media traffic. The peering node of the RMG in the transport stratum might be likely a Border Gateway Function (BGF) or possibly other H.248 MG types (like e.g. a RMG, an AMG, TMGW, MRFP), a SIP UA, H.323 terminal, etc. H.248 Residential Media Gateway (RMG) PSTN/ISDN Phy Internal IP network External IP network NAT/FW Residential Media Gateway Controller (RMGC) H.248 Media Gateway (MG) H.248 RAGW Profile H.248 Profile IP Bearer connection (e.g. RTP) Gateway control (H.248) „Media Pinhole“ „Signalling Pinhole“ a) H.248 gateway control traffic b) PSTN call control signalling via H.248 c) ISDN call control signalling via IUA/SCTP/IP Figure 3: Network model - H.248 RMG and RMGC located in different IP realms (The peer IP bearer node might be an H.248 MG as indicated in this example.) There will be two pinholes, which may require keep pinhole open mechanisms (see clause 6.9.3) as NAT Traversal support function. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 75 6.9.3 Possible NAT Traversal support functions when MG and MGC located in different IP realms Figure 4 indicates possible solutions for each pinhole. The signalling pinhole related keep open mechanism is particularly required during the active call phase (i.e. between context creation and release phases). The media pinhole related keep open mechanism may be required in the call/bearer establishment phase, or e.g. in case of suppressed media traffic (e.g. muted microphone). H.248 Residential Media Gateway (RMG) PSTN/ISDN Phy Internal IP network External IP network NAT/FW Residential Media Gateway Controller (RMGC) H.248 Media Gateway (MG) H.248 RAGW Profile (this specification) H.248 Profile IP Bearer connection (e.g. RTP) Gateway control (H.248) „Media Pinhole“ „Signalling Pinhole“ Keep pinhole open mechanism: e.g. H.248 Inactivity Timer Package (it; H.248.14) Keep pinhole open mechanism: e.g. H.248 Keepalive Request Package (kar; H.248.50) Figure 4: Network model - Possible NAT Traversal support functions 6.9.4 Customer access via a Network Address Translation (NAT) using H.248.50 Clause 4.2 provides a functional requirement that where a RGW also provides customer access via a NAT device that "it does not interfere with, and explicitly takes account of, the operation of the H.248 gateway function in the RGW". However in some network architectures there may be an intermediate NAT/s placed between the RGW and the BGF. The address latching function supported by BGF for hosted NAT traversal requires that a BGF receives a RTP packet from the RGW to set the NAT binding. A RGW cannot receive media RTP packets as long as it has not sent at least one RTP packet to create a pinhole through any intermediate NATs. In order to create a pinhole and maintain a NAT binding, the MGC should request the RGW to transmit an RTP keep-alive packet. This is achieved via the H.248.50 "kar" package. If requested to send a keep alive the RGW shall follow the procedures of H.248.50 [i.4], section 9.2.6. The kar package is required for RGW but not necessary for AGW. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 76 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7 Procedures for Physical H.248 terminations | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.1 General procedures | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.1.1 Initial configuration | A default digit map shall be provisioned in the MG, so that it can be referred to by name rather than by value. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.1.2 DTMF detection | When a series of digit maps is used during called party's number dialling, it is recommended that the values of the timers defined in ITU-T Recommendation H.248.1 [15] be set in such a way that the T timer of the subsequent digit maps be set the same value than the L timer. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.1.3 Sending of tones | Signals shall be sent to the exterior of the gateway, according to the following principles: • When sending a tone to the calling party from the originating MG, the signal shall be applied to the physical termination. • When sending a tone to the calling party from the terminating MG, the signal shall be applied to the ephemeral termination. • When sending a tone to the called party from the terminating MG, the signal shall be applied to the physical termination. • When sending a tone to the called party from the originating MG, the signal shall be applied to the ephemeral termination. Table 93 summarizes where usual tones are generated. Table 93: Sending of tones Tone Generation side Perceived by Signal Dial tone Local Calling Party cg/dt Ring tone Local or Remote Calling Party cg/rt Busy tone Local Calling Party cg/bt Release tone Local Calling Party cg/ct Special Dial Tone Local Calling Party xcg/spec Special Information Tone Local or Remote Calling Party cg/sit Call Waiting tone Local Called Party cg/cw or alert/cw (see note) Congestion tone Local or Remote Calling Party cg/ct Caller Waiting Tone Remote Calling Party cg/cr Message Waiting Tone Local Calling Party srvtn/mwt Confirmation Tone Local Calling Party srvtn/conf Negative Acknowledgment Local Calling Party xcg/nack Off-Hook warning tone Local Both xcg/roh Vacant Tone (Number Unobtainable) Local Calling Party xcg/vac NOTE: The call waiting tone may also be embedded in the andisp/dwa signal if associated with display information. In an originating MG, the context topology and the termination modes shall be configured in such a way that in-band information can be received from the remote side before the called party's answer. This setting shall occur not later than the receipt of the ACO message (or an equivalent message from another signalling protocol that ISUP). ETSI ETSI TS 183 002 V3.3.1 (2009-08) 77 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.1.4 Sending of announcements | Residential Gateways are not required to store recorded announcements nor to support the generic announcement package. Access Gateways may be able to store recorded announcements and shall support the generic announcement package. However, Access Gateways are not required to support variable announcements. When the announcement to be delivered is not available in the gateway and cannot be autonomously retrieved by the gateway from a remote repository, the MGC shall initiate a connection to an external announcement machine, by temporarily adding a termination into the context. Instructions to play announcements are sent directly from the MGC to the server. The announcement server may itself be implemented as an MG, controlled using the H.248 protocol. However, this interface is outside the scope of the present document. In an originating MG, the context topology and the termination modes shall be configured in such a way that in-band information can be received from the remote side before the called party's answer. This setting shall occur not later than the receipt of the ACO message (or an equivalent message from another signalling protocol that ISUP). |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.1.5 Support of emergency calls | The MGC is responsible for detecting emergency calls and setting the Emergency Call context property when creating the associated context. Prior to the context being created the MG makes no assumption on the priority of the events that take place. The priority context property shall not be used for emergency calls. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.1.6 Echo control | Physical terminations are required to support echo cancellation. Echo cancellation is automatically activated on physical terminations by the MG and may be deactivated using the TDM Circuit package (see note 1). NOTE 1: H.248 TDM Circuit Package Version 1 (see ITU-T Recommendation H.248.1 [15], annex E.13) is providing the basic control capabilities for ECDs in H.248 MGs. The SPNE Control Package (see ITU-T Recommendation Q.115.0 [44], clause 7.2) is extending the tdmc Version 1 package by further ECD control possibilities. The SPNE Control Package is not required and is beyond the scope of this version of the profile. Deactivation by the MGC occurs on ISDN physical terminations in case of Unrestricted 64 kbit/s calls and on ANALOG terminations in case the PSTN subscriber line is marked as supporting data calls only. Echo cancellation may also be deactivated by the MG when entering the VBD mode. An Echo Control Device/Function (ECD; see ITU-T Recommendation Q.115.1 [45], clause 3.1) is therefore always associated with a physical H.248 termination (see notes 2 and 3). NOTE 2: A VoIP Media GateWay (MGW) defined by this H.248 Profile is a so-called "type 1 exchange/node" from ECD point of view (see ITU-T Recommendation Q.115.1 [45], clause A.2.4.3.1). NOTE 3: The configuration of the HECD (or ECD) in a media gateway is the "reverse associated" mode (see ITU-T Recommendation Q.115.1 [45], clause A.1.1, note 1 and figures A.2a, A.2b and A.3). An ECD is responsible for a single echo path, therefore also known as half-way ECD (HECD) (see notes 4 and 5). The ITU-T Recommendation G.168 [41] Digital Network ECD is required for the echo generated at "legacy terminal" side of the MG. This is the echo path on which the HECD is intended to operate, called as G.168 Cancelled End (or formerly as Near End). The required ECD tail length capacity is given by the echo path at the cancelled end. NOTE 4: A local call, resulting in a single H.248 Context with two physical H.248 terminations (Phy-to-Phy bearer interworking) may result in the allocation of two HECDs, one per direction. Such two complementary HECDs representing a full-way ECD (called full ECD (FECD), see ITU-T Recommendation Q.115.1 [45], clause 3.7). A FECD configuration for Phy-to-Phy H.248 Context types is not required and supported in this Profile version. It is rather anticipated from MG side, that the MGC is disabling the ECD resources for such a Context type, due to the small end-to-end propagation delay here. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 78 NOTE 5: More detailed ECD notation: In case of an outgoing call the ECD in the originating media gateway, responsible for the hybrid echo generated by the calling party, is playing the role of the outgoing ECD (OECD, see ITU-T Recommendation Q.115.1 [45], clause 3.12). In case of an incoming call the ECD in the terminating media gateway, responsible for the hybrid echo generated by the called party, is playing the role of the incoming ECD (IECD, see ITU-T Recommendation Q.115.1 [45], clause 3.11). |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.2 Specific procedures for analog lines | Example signalling flows for call-dependent procedures for analog line access are provided by TR 183 040 [i.2]. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.2.1 Autonomous actions | Normally the MG detects and applies analogue signals to the analogue line under the instructions of the MGC. However, a MG may be provisioned to perform the following time critical autonomous actions: • Apply normal power feed when the analogue line state changes from On-Hook to Off-Hook. • Apply idle voltage/current feed when the analogue line state changes from Off-Hook to On-Hook. • Apply reduced power feed when the analogue line continues to remain Off-Hook after a certain period of time without being associated to any connection. • Remove the ringing when the line goes Off-Hook. This action is performed irrespective of the setting of the keep active flag associated with the "off-hook" event. This action is intended to avoid causing an acoustic shock to the end user. • If a new outgoing call attempt is rejected by the MGC (e.g. due to congestion in MGC) by the return of an error code in response to a Notify command containing an "Off-Hook" observed event, then the RGW/AGW may as an option autonomously apply an appropriate tone or announcement. This will ensure that the end user is not subject to hearing prolonged silence and not knowing the progression of his call attempt. If a tone or announcement is autonomously applied, then the RGW/AGW will then be responsible for performing the subsequent autonomous call cleardown and without any interaction with the MGC. The detailed autonomous call treatment procedures are the same as those defined in ES 283 039-4 [57], for the case where a non emergency call is filtered by the AGW and not admitted to the MGC. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.2.2 Alerting | The signal to be used (andisp/dwa or alert/ri) depends on whether or not information need to be displayed to the terminal. See also clause 7.2.4. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.2.3 Automatic metering | The pulses in the automatic metering package have to be accurately reflected between the MGC and the MG. In order to achieve that accuracy the following procedures have to be followed. The MG stops the enable metering signal from the automatic metering package in the event of an H.248 control link failure. The MGC is aware that the enable metering signal was stopped if it determines that the H.248 control link is down or if ServiceChange on Root is received indicating disconnected method. The enable metering signals is not reinitiated if the H.248 control link is re-established. The MGC has then the option to reinitialize the enable metering signal and continue charging or not charge for the call anymore. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 79 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.2.4 Display service | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.2.4.1 On hook data transmission | If "data transmission during ringing or prior to ringing" as described in EN 300 659-1 [4] is required (e.g. for the calling number display service), then the MGC shall use the andisp/dwa signal without or with the "TAS" parameter. The andisp/dwa signal without "TAS" parameter is used when the default method (i.e. "during ringing" or "prior to ringing" and the corresponding TAS) provisioned (e.g. globally or on a termination-basis) within the MG is to be used. The andisp/dwa signal with a "TAS" parameter is used when the default method provisioned in the MG is to be overridden by the MGC. The indication of "nt" (no TAS) in the TAS parameter informs the MG to apply data transmission during ringing. If "data transmission not associated with ringing" (e.g. for visual message waiting indicator service) as described in EN 300 659-1 [4] is required, then the MGC shall use the andisp/data signal without or with the "TAS" parameter. The former mechanism is used when the default TAS provisioned within the MG is to be used. The latter mechanism is used when the default TAS signal provisioned in the MG is to be overridden by the MGC. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.2.4.2 Off hook data transmission: | For Off-Hook display the procedures for shall conform to EN 300 659-2 [5]. If data transmission is invoked after the initial Call Waiting Tone "Subscriber Alert Signal" (e.g. for the calling number display service), then the MGC shall use the andisp/dwa signal without or with the "TAS" parameter. The former mechanism is used when the default TAS provisioned within the MG is to be used. The latter mechanism is used when the default TAS signal provisioned in the MG is to be overridden by the MGC. If data transmission is invoked without the presence of a "Subscriber Alert Signal" (e.g. for the advice of charge service), then the MGC shall use the andisp/data signal without or with the "TAS" parameter. The former mechanism is used when the default TAS provisioned within the MG is to be used. The latter mechanism is used when the default TAS signal provisioned in the MG is to be overridden by the MGC. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3 Specific procedures for ISDN interfaces | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.1 General | Support of ISDN Basic Access, Primary Rate Access and NMDS requires the use of a backhaul mechanism in conjunction with H.248. In particular H.248 shall be used for handling the adaptation of the B channels to RTP media streams, for applying tones and announcements, and for inband DTMF digit collection. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.2 ISDN-BA signalling | An AGW or RGW shall support ISDN Q.921 (see ITU-T Recommendation Q.921 [46] User Adaptation (IUA) over SCTP as a backhaul mechanism for transporting D-channel (s-type frames) information to the MGC. It is recommended that the IUA interface identifier (IID) is mapped from the H.248 termination ID. An AGW or RGW shall support either SCTP and IUA (see RFC 2960 [58] and RFC 4233 [12]) or Raw Frame Relay over Generic Routing Encapsulation (see RFC 2784 [38]) as a backhaul mechanism for D-channel p-type frames to the required destination as defined in ETS 300 099 [6]. The Media GateWay (MGW) shall evaluate the DLCI field in the Q.921 message header. For SAPI=16, the Media GateWays (MGWs) shall send the SCTP/IUA messages to the required destination. NOTE 1: For SAPI=0, the Media GateWay (MGW) performs the procedure as described in the first paragraph of this clause. Media GateWays (MGWs) shall support either SCTP and IUA (see RFC 2960 [58] and RFC 4233 [12]) or Raw Frame Relay over Generic Routing Encapsulation (see RFC 2784 [38]) as a backhaul mechanism for D-channel f-type frames to a Frame Relay Gateway to the required destination as defined in ETS 300 099 [6]. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 80 The Media GateWay (MGW) shall evaluate the DLCI field and the Interface Id in the Q.921 message header. For SAPI=16, the Media GateWays (MGWs) shall send the SCTP/IUA messages to the destination, which is pre-provisioned in the MG. NOTE 2: For SAPI=0, the Media GateWay (MGW) performs the procedure as described in the first paragraph of this clause. The LAP-D state machine (including TEI assignment and management procedures) shall reside within the AGW or RGW and shall conform to ETS 300 402-2 [8]. Automatic TEI may only be requested by the terminal equipment (TE). Non-automatic TEI shall be autonomously assigned by the AGW or RGW upon activation of the layer 1 and these values can then be used by either the TE or the MGC. The range of automatic and non-automatic TEI is defined in ETS 300 402-2 [8]. The "point to point" or "point to multi-point" procedures are solely under the control of the MGC and have no impact on the AGW or RGW. The AGW or RGW shall support either permanent activation of the layer 1 or activation of layer 1 on a per call basis and this mode shall be configurable via a management interface. Activation of loop backs within the access digital section (e.g. loopback at the NT1) shall be under the control of the AGW or RGW. When a loopback is applied it will also be necessary for the AGW or RGW to inform the MGC that the ISDN access is unavailable for the presentation of incoming calls. This can be achieved by using the H.248 ServiceChange procedures. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.2.1 Discrimination of s-type frames (layer 2 call control signalling) | The discrimination of s-type frames is based on a SAPI value equals to zero. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.2.2 Discrimination of p-type frames | The Media GateWays (MGWs) shall evaluate the DLCI field. For the SAPI value equals to 16, the media gateway shall send the X.25 PLP messages over SCTP and IUA to the destination address, which is pre-provisioned for this SAPI value in the media gateway. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.2.3 Discrimination of f-type frames | The Media GateWay (MGW) shall evaluate the DLCI field. For the SAPI value range for 32 to 62 inclusive, the Media Gateway (MG) shall send the X.35/X.31 messages over SCTP and IUA to the destination address, which is pre-provisioned for this SAPI-values in the media gateway. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.2.4 SCTP Association establishment | The NGN-Packet Handler (NGN-PH) or Frame Handler (FH) plays the role of the Softswitch in a packet mode or frame mode configuration. Therefore, the SCTP association shall be established/re-established by the NGN PH or FH. For signalling (s-type frames) and packet/frame relay (f and p-type frames) two separate SCTP associations shall be used: - for s-type frames, the SCTP association is established between the MG and the Softswitch; - for p-type frames, the SCTP association is established between the MG and the NGN-PH; - for f-type frames, the SCTP association is established between the MG and the NGN-FH. Signalling traffic from one D-channel is transported over one bidirectional SCTP stream within one SCTP association. Signalling traffic from more than one D-channel may be transported over one bidirectional SCTP stream, within an SCTP association. The same may also apply for f- and p-type traffic. NOTE: If, for redundancy, the MG is connected to a secondary Softswitch, there may be also a secondary SCTP association established from the MG to the secondary Softswitch. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 81 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.2.4.1 IUA/SCTP for Q.931 call control signalling traffic | The H.248 registration/re-registration between the Media GateWay (MGW) and the Media Gateway Controller (MGC) shall trigger the initiation of the SCTP association between the Media GateWay (MGW) and the Media Gateway Controller (MGC) according to TISPAN TS 102 144 [59]. The H.248 de-registration between the Media GateWay (MGW) and the Media Gateway Controller (MGC) shall trigger the shutdown of the SCTP association between the Media GateWay (MGW) and the Media Gateway Controller (MGC) according to TISPAN TS 102 144 [59]. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.2.4.2 IUA/SCTP for X.25 or frame relay traffic | IUA shall be used asymmetrical as specified in RFC 4233 [12]. The X.25 endpoint, i.e. the NGN-PH shall be a standalone node. It is not the aim of the present document to have two X.25 terminals interconnected via two Access Gateways and an IP domain, but a X.25 terminal connected via an Access Gateway to the NGN-PH. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.3 ISDN-PRA signalling | The RGW and AGW requirements for ISDN-PRA are the same as for an ISDN-BA line as detailed above, with the following exceptions: • "Point to point" procedures are only applicable. • Relaying of p-type and f-type frames is not applicable. Unlike ISDN-BA, any OAM procedures related to the access digital section (e.g. Loopback at the NT1) are handled entirely within the AGW or RGW, where time slot "0" is terminated. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.4 NMDS | Where the AGW or RGW supports NMDS, there are specific behaviours for the ISDN Basic Access (BA) at both Layer 1 and Layer 2. At Layer 1 permanent activation shall be supported. At layer 2 the range of Automatic TEI values available to be requested by the Terminal Equipment (TE) and TEIs used for the signalling for PSTN ports shall be as defined in EN 301 141-1 [7]. TEIs used for the signalling for the PSTN ports associated with the Network Terminating Node (NTN) shall be operated using "point-to-point" procedures under the control of the MGC. Further details of these Layer 1 and Layer 2 procedures are defined in EN 301 141-1 [7]. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.3.5 ISDN management | The operation and maintenance of an ISDN-BA access digital section (as defined in ETS 300 297 [47]) and an ISDN-PRA access digital section (as defined in ETS 300 233 [48]) is performed by the MG. The MG controls the access digital section for the whole ISDN access and not individual "B" channels. Therefore the MG shall indicate failure or return to service of the ISDN access digital section to the MGC, via a H.248 ServiceChange. The ServiceChange shall have a TerminationID that specifies the affected ISDN port, but with a wildcarded identifier to indicate that the command applies to the entire ISDN Access. Upon receipt of this ServiceChange the MGC shall assume that the command applies to all the configured "B-channels", as well as the "D-channel", whose signalling is transported via IUA/SCTP. It should be noted that all other H.248 commands (e.g. Add, Modify, Move, Notify, Subtract) sent by the MG/MGC which are associated with the establishment of a bearer shall apply to an individual "B-channel". In addition it is possible to send a ServiceChange identifying a specific B-channel when for example a B-channel is taken in and out-of-service via the MG/MGC Element Management Systems. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 82 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.