]> git.ipfire.org Git - thirdparty/asterisk.git/commit
res_fax: wrap v21 detected Asterisk initiated negotiation with config option
authorKevin Harwell <kharwell@digium.com>
Fri, 13 Dec 2019 19:46:17 +0000 (13:46 -0600)
committerKevin Harwell <kharwell@digium.com>
Fri, 13 Dec 2019 20:23:51 +0000 (14:23 -0600)
commit754fca9297276085722b621a90d8c97d7056d304
tree9dbcd36e4f0238b8318a873395a3252e3abdf332
parent51482dec75beeab283feb7f80e04feb37ac15431
res_fax: wrap v21 detected Asterisk initiated negotiation with config option

A previous patch:

Gerrit Change-Id: I73bb24799bfe1a48adae9c034a2edbae54cc2a39

made it so a T.38 Gateway tries to negotiate with both sides by sending T.38
negotiation request to both endpoints supported T.38 versus the previous
behavior of forwarding negotiation to the "other" channel once a preamble
was detected.

This had the unfortunate side effect of breaking some setups. Specifically
ones that set the max datagram option on an endpoint configuration (configured
max datagram was not propagated since Asterisk now initiates negotiations).

This patch adds a configuration option, "negotiate_both", that when enabled
makes it so Asterisk initiates the negotiation requests to both endpoints vs.
the previous behavior of waiting, and forwarding the request.

The default is disabled keeping with the old behavior.

ASTERISK-28660

Change-Id: I5deb875f3485e20bc75119ec743090655d864a1a
doc/CHANGES-staging/res_fax_negotiate_both [new file with mode: 0644]
include/asterisk/res_fax.h
res/res_fax.c