----- Original Message -----
Sent: Thursday, May 06, 2010 12:39
PM
Subject: Re: [Freeswitch-users] rfc2833
confusion
god, so many confusion for only an audio tone !
;)
anyway if I understand it's called inband by the fact that
it's in RTP flow onlly.
so the rfc2833 packet is only an event payload
...
----- Original Message -----
Sent: Thursday, May 06, 2010 11:52
AM
Subject: Re: [Freeswitch-users] rfc2833
confusion
both 2833 and actual tones in the audio stream are often
called in-band because the 2833 is just a transport for the inband tones
that is assumed to be reconstructed on the other side. Some people
refer to inband as the real tones and 2833 as not inband because it's not
the tones. So the one you have to look out for is people who call 2833
inband and do not clarify that it's inband packetized according the
RFC2833
The one that is not inband for sure is INFO (which has been dropped
from the standard in favor of some ridiculous SUBSCRIBE based xml
exchange)
Like all things in SIP and anything else that comes with an RFC even if
you know the answer you can't rely on trusting that answer because the real
world will do whatever it wants and invalidate you. =D
_______________________________________________
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