Note: the referred text relates to an
Appendix ( = informativ), not to an Annex (= normativ). Thus, just examples, not
mandatory.
Replies:
there are H.248 profile specifications with
support support of monorate emulation, see
e.g.
ETSI ES 283 024, Trunking
Gateway
5.15.1.4
Clearmode codec
On IMS/NGN Terminations, Clearmode codec is transported
according to RFC 4040 [15].
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.
The behaviour of the TMGW shall then conform
to RFC 4040 [15]. All voice and signal processing functions such as silence
suppression, comfort noise insertion and gain adjustment shall be automatically
turned off. The MG shall inherit the same QoS objectives as the ISDN bearer
service.
However, there was never any H.248
Profile standardized with multirate support, at least
to my knowledge.
-Albrecht
__
Y.2262 PSTN/ISDN emulation and
simulation, Appendix IV
Examples of emulation of PSTN and N-ISDN bearer
services
(This appendix does not form an integral part of this
Recommendation)
Examples for the emulation of PSTN and N-ISDN bearer
services are provided:
1) Monorate bearer services (= 1 × 64-kbit/s
digital bearer in PSTN/ISDN)
ITU-T Recommendations I.231.2 and I.231.3 may
be emulated by a single RTP
session, with or without RTP control protocol
(RTCP), using an RTP profile according
to IETF RFC 3551.
ITU-T
Recommendation I.231.1 may be emulated by a single RTP session, with
or
without RTCP, using RTP clearmode according to IETF RFC 4040.
2)
Multirate bearer services (= N × 64-kbit/s digital bearer in PSTN/ISDN; N
greater than one)
ITU-T Recommendations I.231.4 to I.231.10 may be emulated
by TDMoIP described
in ITU-T Recommendation
Y.1453.
> -----Original Message-----
> From:
megaco-bounces <at> ietf.org
> [
mailto:megaco-bounces <at> ietf.org] On
Behalf Of Javi
> Sent: Samstag, 29. Januar 2011 02:13
> To:
megaco <at> ietf.org
> Subject: [Megaco] TDMPW and MeGaCo/SDP
>
>
Assuming the next situation:
>
> ISDN Terminal 1 -
MG1 - [IP network] - MG2 - ISDN Terminal
2
>
> where the MGs (Media Gateway) are controlled by a MGC (Media
Gateway
> Controller) via MeGaCo[H.248.1].
>
> [ITU-T Y.2262 /
Annex IV] proposses that MGs may transport
> ISDN B-channels over the IP
network:
>
> + By a single RTP session (when monochannels ISDN
services)
>
> + Or by TDMoIP (= UDP TDMPWs), when multichannels ISDN
services.
>
>
> How may MGC indicate to the MG that it uses
PWs at the IP termination?
>
> It may be done by MeGaCo, using
SDP[RFC4566] at Local/Remote
> descriptors. However, how may be that SDP
description of TDMPWs?
>
> Thanks,
>
> Javier
Muñoz
>
>
>
_______________________________________________
> Megaco mailing
list
> Megaco <at> ietf.org
>
https://www.ietf.org/mailman/listinfo/megaco>