>Are there some general guidelines ...
I think it comes down to clause 2.5.1.4/RFC4733, which describes such
general guidelines.
In case of DTMF digits, a single RFC 4733 packet carries a single DTMF
digit in my understanding. Triple redundancy is the basic means to target
RTP packet losses, i.e. the receiver must receive at least one out of
three.
The specific guidelines on leakage/latency are amongst other related to the
used transmission interval for redundant packets, which itself MAY depend
on the transmission interval between single DTMF digits within a series of
DTMF events. Another parameter is the "mean IPLR", which allows to estimate
an approximate probability for "loss of all three redundant packets" (i.e.,
the probability for unsuccessful RFC 4733 transport of a single event).
Albrecht
"Jackson, James"
<[EMAIL PROTECTED]> To:
<[email protected]>
Sent by: cc:
[EMAIL PROTECTED] Subject: [Sip-implementors]
RFC2833 Implementations - Inband Leakage vs. Latency ?
olumbia.edu
01.05.2007 23:42
This may be better suited for the AVT WG but I thought I'd try here
first. Are there some general guidelines that would dictate the
acceptable inband leakage when a Media Gateway uses RFC2833 for DTMF
(and suppresses inband tones) ? I assume there is a tradeoff between
leakage and latency resulting from additional buffering. I have seen
some implementations with leakage of 5ms and other implementations with
leakage of 50ms.
Thanks,
James
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
