On 23/07/2013 6:18 AM, Kevin Larsen wrote:
The a=T38MaxBitRate issue you refer to was one that was actually discovered at my company and submitted by a colleague. It was fixed in 11.3.0 and 1.8.21.0. However, I think that it wouldn't help based on the description below being that the parameter was missing altogether. I think if that parameter is missing, then the code would in fact default to 2400 as a safe value.
The Case Insensitive checking of the T.38 attributes was introduced in these versions.
Looking at the ITU-T T.38 Implementors' Guide (11 May 2012)in Table H.2, if the T38MaxBitRate attribute is omitted they suggest using the default value, they indicate a default value of 14400.
Larry. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
