[dahdi-commits] kpfleming: tools/trunk r4726 - /tools/trunk/UPGRADE.txt

[SVN commits to the DAHDI project]

Author: kpfleming
Date: Wed Aug  6 17:11:29 2008
New Revision: 4726

URL: http://svn.digium.com/view/dahdi?view=rev&rev=4726
Log:
update to match dahdi-linux

Modified:
    tools/trunk/UPGRADE.txt

Modified: tools/trunk/UPGRADE.txt
URL: http://svn.digium.com/view/dahdi/tools/trunk/UPGRADE.txt?view=diff&rev=4726&r1=4725&r2=4726
==============================================================================
--- tools/trunk/UPGRADE.txt (original)
+++ tools/trunk/UPGRADE.txt Wed Aug  6 17:11:29 2008
@@ -16,13 +16,13 @@
       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-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 @@
 * 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.