Steve,
I'm pretty sure we don't drop anything. We more or less try to SEND with a policy as close to the RFC we can.
on RECV, we pretty much allow for as many mistakes as possible within reason.
The big issue tends to come from situations where we are being a b2bua and passing through audio and dtmf.
We have various settings in the system to choose to pass the RFCXXXX packets transparently or to parse them as they are encountered depending on the situation.
Also setting proxy_media=true will turn on full transparent proxy mode which will most likely work as well.
UV,
Matt, (hmmhesays on irc) was doing a lot of playing around with this so he would be a good guy to ask.
Apparently, not only MS do not comply with RFC4733 but also SJphone, Xlite
(eyebeam) and Cisco (Call manager, IP phones, etc) amongst others.
Is there anyway I can make FS's Duration to start from 0? I'm happy to
change the code myself with a little guidance.
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Steve
Underwood
Sent: Sunday, June 29, 2008 3:42 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Exchange 2007 UM - DTMF problem
Hi,
Brian West wrote:
> So if you can tell me where this is wrong as per 2833 and the
> clarification via 4733 ?
>
> rfc4733 obsoletes rfc2833 and says this:
> The special duration value of zero is reserved to indicate that the
> event lasts "forever", i.e., is a state and is considered to be
> effective until updated. A sender MUST NOT transmit a zero duration
> for events other than those defined as states. The receiver SHOULD
> ignore an event report with zero duration if the event is not a
> state.
> /b
> PS: http://www.rfc-editor.org/rfc/rfc4733.txt
>
As well as that definition in RFC4733, they also have an example working
in the way the text describes. They send DTMF with a packet rate of one
every 50ms. The first packet of the DTMF sequence contains a duration of
400.
What does FS actually do when a sequence starts at 0? Does it just drop
the first packet, or the whole sequence? If it just drops the first
packet, and the far end cares, that's seriously broken on their part. It
means a single lost packet screws up the whole sequence. Not good. If FS
drops the whole sequence, that might be a little too aggressive.
Some will argue that a gateway should be totally transparent in these
situations, but total transparency is only workable in simplistic cases.
In the end, if MS are doing this you can be sure it will not be fixed,
and must be tolerated.
Regards,
Steve
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
No virus found in this incoming message.Version: 8.0.101 / Virus Database: 270.4.3/1524 - Release Date: 28/06/2008
Checked by AVG.
19:42
No virus found in this outgoing message.
Checked by AVG.
Version: 8.0.101 / Virus Database: 270.4.3/1524 - Release Date: 28/06/2008
19:42
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org