[asterisk-dev] [Code Review] Fax Gateway Implementation T30<->T38

[Klaus Darilion]

Am 31.03.2011 21:25, schrieb Kevin Fleming:
> The second is detection of a *called* FAX terminal which is
> indicating that it is ready to initiate a FAX transaction (receiving,
> or being polled to send). This is done by detecting the V.21 preamble
> at the beginning of the called FAX terminal's first message after
> CED. When this is detected by the T.38 gateway code (*NOT* the
> channel driver), then T.38 negotiation should be initiated to the
> calling channel, and if it succeeds, a T.38 gateway session would be

Just a question: Asterisk is responsible to switch the incoming channel
to T.38, and the outgoing channel may be switched to T.38 by the callee?

> One more note: the faxdetect code (triggered by CNG) does *NOT*
> disable echo cancellation. Echo cancellers that are G.168 compliant
> detect CED tones generated by *called* FAX terminals and take action
> themselves to reconfigure properly so as to not interfere with a FAX
> transaction.

What about the software echo cancellers in DAHDI, are they G.168 compliant?

regards
Klaus