Don't offer MMR or JBIG transcoding during T.38 negotiation.
authorKevin P. Fleming <kpfleming@digium.com>
Tue, 9 Feb 2010 16:24:52 +0000 (16:24 +0000)
committerKevin P. Fleming <kpfleming@digium.com>
Tue, 9 Feb 2010 16:24:52 +0000 (16:24 +0000)
After further discussion with Steve Underwood, we should not (yet) be offering
to receive MMR or JBIG transcoded streams from T.38 endpoints. A future spandsp
release will support those features, and then they can be enabled during
negotiation

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@245680 65c4cc65-6c06-0410-ace0-fbb531ad65f3

apps/app_fax.c

index bef5ed5..ede2044 100644 (file)
@@ -373,8 +373,12 @@ static int transmit_audio(fax_session *s)
                                                             .rate = AST_T38_RATE_14400,
                                                             .rate_management = AST_T38_RATE_MANAGEMENT_TRANSFERRED_TCF,
                                                             .fill_bit_removal = 1,
-                                                            .transcoding_mmr = 1,
-                                                            .transcoding_jbig = 1,
+/*
+ * spandsp has API calls to support MMR and JBIG transcoding, but they aren't
+ * implemented quite yet... so don't offer them to the remote endpoint
+ *                                                          .transcoding_mmr = 1,
+ *                                                          .transcoding_jbig = 1,
+*/
        };
 
        /* if in called party mode, try to use T.38 */