diff options
| author | Kevin P. Fleming <kpfleming@digium.com> | 2009-08-03 20:48:48 +0000 |
|---|---|---|
| committer | Kevin P. Fleming <kpfleming@digium.com> | 2009-08-03 20:48:48 +0000 |
| commit | e9d22f802e5a3cbda4bc7ed868388ac189a75785 (patch) | |
| tree | b60a24dd99f31bac080dce420ea3d9242799ab0e /doc/res_config_sqlite.txt | |
| parent | 070de85e5674e31000b332df63effb1251b9b65b (diff) | |
Rename 'canreinvite' option to 'directmedia', with backwards compatibility.
It is clear from multiple mailing list, forum, wiki and other sorts of posts
that users don't really understand the effects that the 'canreinvite' config
option actually has, and that in some cases they think that setting it to 'no'
will actually cause various other features (T.38, MOH, etc.) to not work properly,
when in fact this is not the case. This patch changes the proper name of the
option to what it should have been from the beginning ('directmedia'), but
preserves backwards compatibility for existing configurations.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@210190 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'doc/res_config_sqlite.txt')
| -rw-r--r-- | doc/res_config_sqlite.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/res_config_sqlite.txt b/doc/res_config_sqlite.txt index 39d31521a..95322cf10 100644 --- a/doc/res_config_sqlite.txt +++ b/doc/res_config_sqlite.txt @@ -70,7 +70,7 @@ CREATE TABLE ast_sip ( callgroup VARCHAR(10) DEFAULT NULL, callerid VARCHAR(80) DEFAULT NULL, cancallforward CHAR(3) DEFAULT 'yes', - canreinvite CHAR(3) DEFAULT 'yes', + directmedia CHAR(3) DEFAULT 'yes', context VARCHAR(80) DEFAULT NULL, defaultip VARCHAR(15) DEFAULT NULL, dtmfmode VARCHAR(7) DEFAULT NULL, |