1 Information for Upgrading From Previous Asterisk Releases
2 =========================================================
6 * The Asterisk 1.2 source code now uses C language features
7 supported only by 'modern' C compilers. Generally, this means GCC
8 version 3.0 or higher, although some GCC 2.96 releases will also
9 work. Some non-GCC compilers that support C99 and the common GCC
10 extensions (including anonymous structures and unions) will also
11 work. All releases of GCC 2.95 do _not_ have the requisite feature
12 support; systems using that compiler will need to be upgraded to
13 a more recent compiler release.
17 * The dialplan expression parser (which handles $[ ... ] constructs)
18 has gone through a major upgrade, but has one incompatible change:
19 spaces are no longer required around expression operators, including
20 string comparisons. However, you can now use quoting to keep strings
21 together for comparison. For more details, please read the
22 doc/README.variables file, and check over your dialplan for possible
27 * The default for ackcall has been changed to "no" instead of "yes"
28 because of a bug which caused the "yes" behavior to generally act like
29 "no". You may need to adjust the value if your agents behave
30 differently than you expect with respect to acknowledgement.
32 * The AgentCallBackLogin application now requires a second '|' before
33 specifying an extension@context. This is to distinguish the options
34 string from the extension, so that they do not conflict. See
35 'show application AgentCallbackLogin' for more details.
39 * Parking behavior has changed slightly; when a parked call times out,
40 Asterisk will attempt to deliver the call back to the extension that
41 parked it, rather than the 's' extension. If that extension is busy
42 or unavailable, the parked call will be lost.
46 * The Caller*ID of the outbound leg is now the extension that was
47 called, rather than the Caller*ID of the inbound leg of the call. The
48 "o" flag for Dial can be used to restore the original behavior if
49 desired. Note that if you are looking for the originating callerid
50 from the manager event, there is a new manager event "Dial" which
51 provides the source and destination channels and callerid.
55 * The naming convention for IAX channels has changed in two ways:
56 1. The call number follows a "-" rather than a "/" character.
57 2. The name of the channel has been simplified to IAX2/peer-callno,
58 rather than IAX2/peer@peer-callno or even IAX2/peer@peer/callno.
62 * The global option "port" in 1.0.X that is used to set which port to
63 bind to has been changed to "bindport" to be more consistent with
64 the other channel drivers and to avoid confusion with the "port"
65 option for users/peers.
67 * The "Registry" event now uses "Username" rather than "User" for
72 * With the addition of dialplan functions (which operate similarly
73 to variables), the SetVar application has been renamed to Set.
75 * The CallerPres application has been removed. Use SetCallerPres
76 instead. It accepts both numeric and symbolic names.
78 * The applications GetGroupCount, GetGroupMatchCount, SetGroup, and
79 CheckGroup have been deprecated in favor of functions. Here is a
80 table of their replacements:
82 GetGroupCount([groupname][@category] GROUP_COUNT([groupname][@category]) Set(GROUPCOUNT=${GROUP_COUNT()})
83 GroupMatchCount(groupmatch[@category]) GROUP_MATCH_COUNT(groupmatch[@category]) Set(GROUPCOUNT=${GROUP_MATCH_COUNT(SIP/.*)})
84 SetGroup(groupname[@category]) GROUP([category])=groupname Set(GROUP()=test)
85 CheckGroup(max[@category]) N/A GotoIf($[ ${GROUP_COUNT()} > 5 ]?103)
87 Note that CheckGroup does not have a direct replacement. There is
88 also a new function called GROUP_LIST() which will return a space
89 separated list of all of the groups set on a channel. The GROUP()
90 function can also return the name of the group set on a channel when
91 used in a read environment.
93 * The applications DBGet and DBPut have been deprecated in favor of
94 functions. Here is a table of their replacements:
96 DBGet(foo=family/key) Set(foo=${DB(family/key)})
97 DBPut(family/key=${foo}) Set(DB(family/key)=${foo})
99 * The application SetLanguage has been deprecated in favor of the
102 SetLanguage(fr) Set(LANGUAGE()=fr)
104 The LANGUAGE function can also return the currently set language:
106 Set(MYLANG=${LANGUAGE()})
108 * The applications AbsoluteTimeout, DigitTimeout, and ResponseTimeout
109 have been deprecated in favor of the function TIMEOUT(timeouttype):
111 AbsoluteTimeout(300) Set(TIMEOUT(absolute)=300)
112 DigitTimeout(15) Set(TIMEOUT(digit)=15)
113 ResponseTimeout(15) Set(TIMEOUT(response)=15)
115 The TIMEOUT() function can also return the currently set timeouts:
117 Set(DTIMEOUT=${TIMEOUT(digit)})
119 * The applications SetCIDName, SetCIDNum, and SetRDNIS have been
120 deprecated in favor of the CALLERID(datatype) function:
122 SetCIDName(Joe Cool) Set(CALLERID(name)=Joe Cool)
123 SetCIDNum(2025551212) Set(CALLERID(number)=2025551212)
124 SetRDNIS(2024561414) Set(CALLERID(RDNIS)=2024561414)
126 * The application Record now uses the period to separate the filename
127 from the format, rather than the colon.
129 * The application VoiceMail now supports a 'temporary' greeting for each
130 mailbox. This greeting can be recorded by using option 4 in the
131 'mailbox options' menu, and 'change your password' option has been
134 * The application VoiceMailMain now only matches the 'default' context if
135 none is specified in the arguments. (This was the previously
136 documented behavior, however, we didn't follow that behavior.) The old
137 behavior can be restored by setting searchcontexts=yes in voicemail.conf.
141 * A queue is now considered empty not only if there are no members but if
142 none of the members are available (e.g. agents not logged on). To
143 restore the original behavior, use "leavewhenempty=strict" or
144 "joinwhenempty=strict" instead of "=yes" for those options.
146 * It is now possible to use multi-digit extensions in the exit context
147 for a queue (although you should not have overlapping extensions,
148 as there is no digit timeout). This means that the EXITWITHKEY event
149 in queue_log can now contain a key field with more than a single
154 * By default, there is a new option called "autofallthrough" in
155 extensions.conf that is set to yes. Asterisk 1.0 (and earlier)
156 behavior was to wait for an extension to be dialed after there were no
157 more extensions to execute. "autofallthrough" changes this behavior
158 so that the call will immediately be terminated with BUSY,
159 CONGESTION, or HANGUP based on Asterisk's best guess. If you are
160 writing an extension for IVR, you must use the WaitExten application
161 if "autofallthrough" is set to yes.
165 * AGI scripts did not always get SIGHUP at the end, previously. That
166 behavior has been fixed. If you do not want your script to terminate
167 at the end of AGI being called (e.g. on a hangup) then set SIGHUP to
168 be ignored within your application.
170 * CallerID is reported with agi_callerid and agi_calleridname instead
171 of a single parameter holding both.
175 * The preferred format for musiconhold.conf has changed; please see the
176 sample configuration file for the new format. The existing format
177 is still supported but will generate warnings when the module is loaded.
181 * All the chan_modem channel drivers (aopen, bestdata and i4l) are deprecated
182 in this release, and will be removed in the next major Asterisk release.
183 Please migrate to chan_misdn for ISDN interfaces; there is no upgrade
184 path for aopen and bestdata modem users.
188 * The conference application now allows users to increase/decrease their
189 speaking volume and listening volume (independently of each other and
190 other users); the 'admin' and 'user' menus have changed, and new sound
191 files are included with this release. However, if a user calling in
192 over a Zaptel channel that does NOT have hardware DTMF detection
193 increases their speaking volume, it is likely they will no longer be
194 able to enter/exit the menu or make any further adjustments, as the
195 software DTMF detector will not be able to recognize the DTMF coming
198 GetVar Manager Action:
200 * Previously, the behavior of the GetVar manager action reported the value
201 of a variable in the following manner:
203 This has been changed to a manner similar to the SetVar action and is now