diff options
author | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-08-03 20:48:48 +0000 |
---|---|---|
committer | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-08-03 20:48:48 +0000 |
commit | a73782aff532a1102239e23a66c86296dd52fe70 (patch) | |
tree | b60a24dd99f31bac080dce420ea3d9242799ab0e /configs/res_ldap.conf.sample | |
parent | e44258424c1bdaac0754970d268a9bd1c77b2f99 (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: http://svn.digium.com/svn/asterisk/trunk@210190 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs/res_ldap.conf.sample')
-rw-r--r-- | configs/res_ldap.conf.sample | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/configs/res_ldap.conf.sample b/configs/res_ldap.conf.sample index 0a442298d..b02045f15 100644 --- a/configs/res_ldap.conf.sample +++ b/configs/res_ldap.conf.sample @@ -60,7 +60,7 @@ name = cn amaflags = AstAccountAMAFlags callgroup = AstAccountCallGroup callerid = AstAccountCallerID -canreinvite = AstAccountCanReinvite +directmedia = AstAccountDirectMedia context = AstAccountContext dtmfmode = AstAccountDTMFMode fromuser = AstAccountFromUser @@ -131,7 +131,7 @@ additionalFilter=(objectClass=*) amaflags = AstAccountAMAFlags callgroup = AstAccountCallGroup callerid = AstAccountCallerID -canreinvite = AstAccountCanReinvite +directmedia = AstAccountDirectMedia context = AstAccountContext dtmfmode = AstAccountDTMFMode fromuser = AstAccountFromUser |