Re: [Freeswitch-users] G729B and mod_com_g729
Hey Brian, Thanks for coming back to me so fast. For the sake of records, I found out that you are perfectly right, G729B is not standard and it is a proprietary method of Teles UA for G729 handling. Have a good one! DanB
Brian, just out of curiosity (and I know this is bad bad bad bad) why not have a compatibility setting so that codecs identified by static IANA-assigned numbers (his example uses G729's assigned 18) can still function. Or are there any broken devices that use the wrong numbers that that might cause even problems with? *ducks* -Steve On 10 December 2010 16:51, Dan-Cristian Bogos <danb.lists@googlemail.com> wrote:
Hey Brian,
Thanks for coming back to me so fast.
For the sake of records, I found out that you are perfectly right, G729B is not standard and it is a proprietary method of Teles UA for G729 handling.
Have a good one!
DanB
_______________________________________________ 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
s/even problems/even more problems/ On 10 December 2010 17:29, Steven Ayre <steveayre@gmail.com> wrote:
Brian, just out of curiosity (and I know this is bad bad bad bad) why not have a compatibility setting so that codecs identified by static IANA-assigned numbers (his example uses G729's assigned 18) can still function. Or are there any broken devices that use the wrong numbers that that might cause even problems with?
*ducks*
-Steve
On 10 December 2010 16:51, Dan-Cristian Bogos <danb.lists@googlemail.com> wrote:
Hey Brian,
Thanks for coming back to me so fast.
For the sake of records, I found out that you are perfectly right, G729B is not standard and it is a proprietary method of Teles UA for G729 handling.
Have a good one!
DanB
_______________________________________________ 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
NDLB-allow-bad-iananame is the option you want on the profile. The issue with the continued acceptance of broken things is what keeps getting us into this hole that we will never climb out of if we don't STOP IT. If its wrong do NOT accept it and make the vendor fix their non-compliant crap otherwise this is only going to continue to get worse! /b On Dec 10, 2010, at 11:29 AM, Steven Ayre wrote:
Brian, just out of curiosity (and I know this is bad bad bad bad) why not have a compatibility setting so that codecs identified by static IANA-assigned numbers (his example uses G729's assigned 18) can still function. Or are there any broken devices that use the wrong numbers that that might cause even problems with?
*ducks*
-Steve
Amen, brothah! On Fri, Dec 10, 2010 at 9:38 AM, Brian West <brian@freeswitch.org> wrote:
NDLB-allow-bad-iananame is the option you want on the profile.
The issue with the continued acceptance of broken things is what keeps getting us into this hole that we will never climb out of if we don't STOP IT. If its wrong do NOT accept it and make the vendor fix their non-compliant crap otherwise this is only going to continue to get worse!
/b
On Dec 10, 2010, at 11:29 AM, Steven Ayre wrote:
Brian, just out of curiosity (and I know this is bad bad bad bad) why not have a compatibility setting so that codecs identified by static IANA-assigned numbers (his example uses G729's assigned 18) can still function. Or are there any broken devices that use the wrong numbers that that might cause even problems with?
*ducks*
-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
Cool. That's why I was asking about a parameter. I was never suggesting making it default behaviour. Steve on iPhone On 10 Dec 2010, at 17:38, Brian West <brian@freeswitch.org> wrote:
NDLB-allow-bad-iananame is the option you want on the profile.
The issue with the continued acceptance of broken things is what keeps getting us into this hole that we will never climb out of if we don't STOP IT. If its wrong do NOT accept it and make the vendor fix their non-compliant crap otherwise this is only going to continue to get worse!
/b
On Dec 10, 2010, at 11:29 AM, Steven Ayre wrote:
Brian, just out of curiosity (and I know this is bad bad bad bad) why not have a compatibility setting so that codecs identified by static IANA-assigned numbers (his example uses G729's assigned 18) can still function. Or are there any broken devices that use the wrong numbers that that might cause even problems with?
*ducks*
-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
It is worth looking at Internet Explorer as an example of the sad consequences of tolerance. Microsoft made it so tolerant of wrongly tagged languages, file types, etc. that it now practically ignores all the tagging, even when the tagging is right. Perfectly good web pages get misinterpreted very frequently. The tolerance of IE has made web page designers so sloppy that about 90% of the world's Chinese language web pages only display correctly if you set your locale to the appropriate type of Chinese (traditional or simplified), or manually force each page you visit. The designer has their locale set to Chinese, and never bothers checking beyond that. If you have worked with things like webmail, you will know that the handling of files, like attached voice mails, in the displayed mail is very quirky in IE. By trying to be super tolerant it ends up with near random behaviour. So, a short term move in the 90s by MS, which must have made people greatly thank them in the short term, has turned out to be a HUGE PITA. Steve On 12/11/2010 01:38 AM, Brian West wrote:
NDLB-allow-bad-iananame is the option you want on the profile.
The issue with the continued acceptance of broken things is what keeps getting us into this hole that we will never climb out of if we don't STOP IT. If its wrong do NOT accept it and make the vendor fix their non-compliant crap otherwise this is only going to continue to get worse!
/b
On Dec 10, 2010, at 11:29 AM, Steven Ayre wrote:
Brian, just out of curiosity (and I know this is bad bad bad bad) why not have a compatibility setting so that codecs identified by static IANA-assigned numbers (his example uses G729's assigned 18) can still function. Or are there any broken devices that use the wrong numbers that that might cause even problems with?
*ducks*
-Steve
participants (5)
-
Brian West
-
Dan-Cristian Bogos
-
Michael Collins
-
Steve Underwood
-
Steven Ayre