summaryrefslogtreecommitdiff
path: root/UPGRADE.txt
diff options
context:
space:
mode:
authorKevin P. Fleming <kpfleming@digium.com>2008-08-06 22:11:29 +0000
committerKevin P. Fleming <kpfleming@digium.com>2008-08-06 22:11:29 +0000
commit4954332558f52b5d9876598a9b6b0d60c54e6be5 (patch)
tree0dcd0d96bfd3e57760c2db7c9ac555e541931c8d /UPGRADE.txt
parentbdc1755fdfc4dacb85a535434a5e0694ef16c3b2 (diff)
update to match dahdi-linux
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@4726 a0bf4364-ded3-4de4-8d8a-66a801d63aff
Diffstat (limited to 'UPGRADE.txt')
-rw-r--r--UPGRADE.txt26
1 files changed, 18 insertions, 8 deletions
diff --git a/UPGRADE.txt b/UPGRADE.txt
index 5fac438..9cf4d5b 100644
--- a/UPGRADE.txt
+++ b/UPGRADE.txt
@@ -16,13 +16,13 @@ Important notes about upgrading:
dahdi-linux: kernel modules
dahdi-tools: userspace tools
- In addition, there is a dahdi-complete package that contains both
+ In addition, there is a dahdi-linux-complete package that contains both
dahdi-linux and dahdi-tools for simplified installation.
Note: The dahdi-linux and dahdi-tools packages have *separate*
version numbers; they will not be released 'in sync', and it is
perfectly acceptable to use (for example) dahdi-tools 2.0.6 with
- dahdi-linux 2.0.11. The dahdi-complete package version number will
+ dahdi-linux 2.0.11. The dahdi-linux-complete package version number will
always include *both* of these version numbers so that you will know
what is included in it.
@@ -60,12 +60,13 @@ Notes about the dahdi-linux package:
Notes about the dahdi-tools package:
* Many tool names have changed:
- ztcfg -> dahdi_cfg
- ztmonitor -> dahdi_monitor
- ztscan -> dahdi_scan
- ztspeed -> dahdi_speed
- zttest -> dahdi_test
- zttool -> dahdi_tool
+ ztcfg -> dahdi_cfg
+ ztmonitor -> dahdi_monitor
+ ztscan -> dahdi_scan
+ ztspeed -> dahdi_speed
+ zttest -> dahdi_test
+ zttool -> dahdi_tool
+ zapconf -> dahdi_genconf (deprecates genzaptelconf)
* The system configuration file has moved from /etc/zaptel.conf to
/etc/dahdi/system.conf.
@@ -73,3 +74,12 @@ Notes about the dahdi-tools package:
* The dahdi_cfg tool can now be used to select an echo canceler on a
channel-by-channel basis in the system configuration file; see
system.conf.sample for examples of how to do this.
+
+* The configuration for XPP init_card_* scripts is done now
+ in /etc/dahdi/xpp.conf and uses a simple syntax (example included).
+ For PRI modules, the 'pri_protocol' setting, determines how
+ to configure it (E1/T1).
+
+* In Astribank PRI modules, the LED behaviour represents which ports
+ are *CLOCK MASTER* (red color) and which are *CLOCK SLAVE* (green color).
+ Usually (but not always), this corresponds to the NT/TE settings in Asterisk.