[svn-commits] kpfleming: trunk r137627 - in /trunk: ./ UPGRADE.txt Zaptel-to-DAHDI.txt
SVN commits to the Digium repositories
svn-commits at lists.digium.com
Wed Aug 13 17:33:33 CDT 2008
Author: kpfleming
Date: Wed Aug 13 17:33:32 2008
New Revision: 137627
URL: http://svn.digium.com/view/asterisk?view=rev&rev=137627
Log:
Merged revisions 137530 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r137530 | kpfleming | 2008-08-13 15:46:19 -0500 (Wed, 13 Aug 2008) | 1 line
add document describing what users will need to be aware of when upgrading to this version and using DAHDI
........
Added:
trunk/Zaptel-to-DAHDI.txt
- copied, changed from r137530, branches/1.4/Zaptel-to-DAHDI.txt
Modified:
trunk/ (props changed)
trunk/UPGRADE.txt
Propchange: trunk/
------------------------------------------------------------------------------
Binary property 'branch-1.4-merged' - no diff available.
Modified: trunk/UPGRADE.txt
URL: http://svn.digium.com/view/asterisk/trunk/UPGRADE.txt?view=diff&rev=137627&r1=137626&r2=137627
==============================================================================
--- trunk/UPGRADE.txt (original)
+++ trunk/UPGRADE.txt Wed Aug 13 17:33:32 2008
@@ -84,6 +84,7 @@
to make them more distinguishable from 'maxmsgs', which sets folder
size. The old variables will continue to work in this version, albeit
with a deprecation warning.
+
* If you use any interface for modifying voicemail aside from the built in
dialplan applications, then the option "pollmailboxes" *must* be set in
voicemail.conf for message waiting indication (MWI) to work properly. This
@@ -92,6 +93,7 @@
checking mailboxes for changes so that they can send MWI information to users.
Examples of situations that would require this option are web interfaces to
voicemail or an email client in the case of using IMAP storage.
+
* The externnotify script should accept an additional (last) parameter
containing the number of urgent messages in the INBOX.
@@ -104,17 +106,22 @@
been replaced with 'SUCCESS', and 'NOSUPPORT' has been replaced with
'UNSUPPORTED'). This change makes the SendImage application more consistent
with other applications.
+
* ChanIsAvail() now has a 't' option, which allows the specified device
to be queried for state without consulting the channel drivers. This
performs mostly a 'ChanExists' sort of function.
+
* ChannelRedirect() will not terminate the channel that fails to do a
channelredirect as it has done previously. Instead CHANNELREDIRECT_STATUS
will reflect if the attempt was successful of not.
+
* SetCallerPres() has been replaced with the CALLERPRES() dialplan function
and is now deprecated.
+
* DISA()'s fifth argument is now an options argument. If you have previously
used 'NOANSWER' in this argument, you'll need to convert that to the new
option 'n'.
+
* Macro() is now deprecated. If you need subroutines, you should use the
Gosub()/Return() applications. To replace MacroExclusive(), we have
introduced dialplan functions LOCK(), TRYLOCK(), and UNLOCK(). You may use
@@ -125,20 +132,28 @@
sake of backwards compatibility it will not be removed . It is also worth
noting that using both Macro() and GoSub() at the same time is _heavily_
discouraged.
+
* Read() now sets a READSTATUS variable on exit. It does NOT automatically
return -1 (and hangup) anymore on error. If you want to hangup on error,
you need to do so explicitly in your dialplan.
+
* Privacy() no longer uses privacy.conf, so any options must be specified
directly in the application arguments.
+
* MusicOnHold application now has duration parameter which allows specifying
timeout in seconds.
+
* WaitMusicOnHold application is now deprecated in favor of extended MusicOnHold.
+
* SetMusicOnHold is now deprecated. You should use Set(CHANNEL(musicclass)=...)
instead.
+
* While app_directory has always relied on having a voicemail.conf or users.conf file
correctly set up, it now is dependent on app_voicemail being compiled as well.
+
* The arguments in ExecIf changed a bit, to be more like other applications.
The syntax is now ExecIf(<cond>?appiftrue(args):appiffalse(args)).
+
* The behavior of the Set application now depends upon a compatibility option,
set in asterisk.conf. To use the old 1.4 behavior, which allowed Set to take
multiple key/value pairs, set app_set=1.4 in [compat] in asterisk.conf. To
@@ -188,15 +203,18 @@
file names and formats are all controlled via the normal mechanisms. If the
user has not configured the automon feature, the normal "415 Unsupported media type"
is returned, and nothing is done.
+
* SIP: The "call-limit" option is marked as deprecated. It still works in this version of
Asterisk, but will be removed in the following version. Please use the groupcount functions
in the dialplan to enforce call limits. The "limitonpeer" configuration option is
now renamed to "counteronpeer".
+
* SIP: The "username" option is now renamed to "defaultuser" to match "defaultip".
These are used only before registration to call a peer with the uri
sip:defaultuser at defaultip
The "username" setting still work, but is deprecated and will not work in
the next version of Asterisk.
+
* SIP: All of the functionality in SIPCHANINFO() has been implemented in CHANNEL(),
and you should start using that function instead for retrieving information about
the channel in a technology-agnostic way.
@@ -204,6 +222,7 @@
* chan_local.c: the comma delimiter inside the channel name has been changed to a
semicolon, in order to make the Local channel driver compatible with the comma
delimiter change in applications.
+
* H323: The "tos" setting has changed name to "tos_audio" and "cos" to "cos_audio"
to be compatible with settings in sip.conf. The "tos" and "cos" configuration
is deprecated and will stop working in the next release of Asterisk.
@@ -215,7 +234,12 @@
to modify modules.conf to add another "noload" line to ensure that only one of
these three modules gets loaded.
-* Zap: The "msdstrip" option has been deprecated, as it provides no value over
+* DAHDI: The chan_zap module that supported PSTN interfaces using
+ Zaptel has been renamed to chan_dahdi, and only supports the DAHDI
+ telephony driver package for PSTN interfaces. See the
+ Zaptel-to-DAHDI.txt file for more details on this transition.
+
+* DAHDI: The "msdstrip" option has been deprecated, as it provides no value over
the method of stripping digits in the dialplan using variable substring syntax.
Configuration:
Copied: trunk/Zaptel-to-DAHDI.txt (from r137530, branches/1.4/Zaptel-to-DAHDI.txt)
URL: http://svn.digium.com/view/asterisk/trunk/Zaptel-to-DAHDI.txt?view=diff&rev=137627&p1=branches/1.4/Zaptel-to-DAHDI.txt&r1=137530&p2=trunk/Zaptel-to-DAHDI.txt&r2=137627
==============================================================================
--- branches/1.4/Zaptel-to-DAHDI.txt (original)
+++ trunk/Zaptel-to-DAHDI.txt Wed Aug 13 17:33:32 2008
@@ -7,12 +7,11 @@
to accommodate the desires of the owner of the Zaptel trademark for
telephony purposes.
-This version of Asterisk can be built using either Zaptel or DAHDI,
-and has many changes to make the use of DAHDI as easy as possible for
-existing users with dialplans, CDR parsers, AMI applications, and
-others that expect Zaptel to be in use.
+This version of Asterisk can only be built using DAHDI, and as a
+result there are number of changes that will be visible to previous
+users of Asterisk with Zaptel.
-First, the modules that directly use services from Zaptel/DAHDI have been
+First, the modules that directly use services from DAHDI have been
renamed; the new names are:
chan_zap.so -> chan_dahdi.so
@@ -20,85 +19,34 @@
app_zapras.so -> app_dahdiras.so
app_zapscan.so -> app_dahdiscan.so
-However, in spite of the file name changes, the channels and
-applications provided by these modules can still be used with 'Zap'
-style names; see below for more information.
-
-Second, there are have been a number of efforts made to ensure that
-existing systems will not have to have any major configuration changes
-made solely because Asterisk was built against DAHDI instead of
-Zaptel. This includes:
+Second, the behavior of many modules has changed due to the switch to
+DAHDI; the changes are listed below.
chan_dahdi.so:
- This module will determine which channel name ('Zap' or 'DAHDI')
- should be used for incoming and outgoing channels based on the
- build-time choice of telephony drivers. However, if you wish to
- continue using the 'Zap' channel name even though you built Asterisk
- against the DAHDI drivers, you can add the following line to the
- [options] section of your /etc/asterisk/asterisk.conf file:
+ Incoming and outgoing channels managed by this module will be
+ 'DAHDI' channels instead of 'Zap' channels.
- dahdichanname = no
+ All CLI commands that began with 'zap' have been renamed to 'dahdi'
+ commands.
- All CLI commands that begin with 'zap' are now available as 'dahdi'
- commands as well; the 'zap' variants will report that they are
- deprecated the first time you use each one in an Asterisk instance,
- but they will otherwise operate just as they did in previous versions.
+ All Asterisk Manager Interface (AMI) actions that began with 'Zap'
+ have changed to 'DAHDI' prefixes.
- All Asterisk Manager Interface (AMI) actions that begin with 'Zap'
- are also available with 'DAHDI' prefixes.
-
- The ZapSendKeypadFacility dialplan application is now available as
- DAHDISendKeypadFacility as well; the Zap variant will report a deprecation
- warning but will otherwise operate as it did it in previous
- versions.
+ The ZapSendKeypadFacility dialplan application has been renamed to
+ DAHDISendKeypadFacility.
The configuration for the channel driver will be read from
- /etc/asterisk/chan_dahdi.conf unless 'dahdichanname' has been set to
- 'no' in asterisk.conf; if that is done, then the configuration will
- be read from /etc/asterisk/zapata.conf, just as it was in previous
- versions.
+ /etc/asterisk/chan_dahdi.conf instead of /etc/asterisk/zapata.conf.
app_dahdibarge.so:
- The ZapBarge application is now available as DAHDIBarge as well; the
- ZapBarge variant will report a deprecation warning when used, but
- will otherwise operate as it did in previous versions. Regardless of
- which application name is used, the application will restrict itself
- to channels of the proper type, based on the 'dahdichanname' setting
- in asterisk.conf.
+ The ZapBarge application has been renamed to DAHDIBarge.
app_dahdiras.so:
- The ZapRAS application is now available as DAHDIRAS as well; the
- ZapRAS variant will report a deprecation warning when used, but will
- otherwise operate as it did in previous versions. Regardless of
- which application name is used, the application will restrict itself
- to channels of the proper type, based on the 'dahdichanname' setting
- in asterisk.conf.
+ The ZapRAS application has been renamed to DAHDIRAS.
app_dahdiscan.so:
- The ZapScan application is now available as DAHDIScan as well; the
- ZapScan variant will report a deprecation warning when used, but will
- otherwise operate as it did in previous versions. Regardless of
- which application name is used, the application will restrict itself
- to channels of the proper type, based on the 'dahdichanname' setting
- in asterisk.conf.
-
-app_flash.so:
-
- This application has not had any name changes, but will report its
- usage (via 'show application flash') as being for either DAHDI or
- Zaptel channels based on the 'dahdichanname' setting in
- asterisk.conf.
-
-app_chanspy.so:
-
- This application will transparently create 'DAHDI' or 'Zap' channels
- as needed, based on the 'dahdichanname' setting in asterisk.conf.
-
-app_meetme.so:
-
- This application will transparently create 'DAHDI' or 'Zap' channels
- as needed, based on the 'dahdichanname' setting in asterisk.conf.
+ The ZapScan application has been renamed to DAHDIScan.
More information about the svn-commits
mailing list