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 /configs/mgcp.conf.sample | |
| 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 'configs/mgcp.conf.sample')
| -rw-r--r-- | configs/mgcp.conf.sample | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/configs/mgcp.conf.sample b/configs/mgcp.conf.sample index 116b66cd0..fde0a4fc6 100644 --- a/configs/mgcp.conf.sample +++ b/configs/mgcp.conf.sample @@ -41,7 +41,7 @@ ;[dlinkgw] ;host = 192.168.0.64 ;context = default -;canreinvite = no +;directmedia = no ;line => aaln/2 ;line => aaln/1 @@ -96,7 +96,7 @@ ;callwaiting = no ;callreturn = yes ;cancallforward = yes -;canreinvite = no +;directmedia = no ;transfer = no ;dtmfmode = inband ;line => aaln/1 ; now lets save this config to line1 aka aaln/1 @@ -104,7 +104,7 @@ ;callwaiting = no ;callreturn = yes ;cancallforward = yes -;canreinvite = no +;directmedia = no ;transfer = no ;dtmfmode = inband ;line => aaln/2 ; now lets save this config to line2 aka aaln/2 |