xpp: a massive backport from DAHDI. From Xorcom branch-rel-6839-r6908 .

Sun Mar  1 2009 Oron Peled <oron@actcom.co.il> - xpp.r6795
  * Fix cases where the command_queue overflowed during initialization.
    - Also add a 'command_queue_length' parameter to xpp.ko
  * More migrations to sysfs:
    - Add a 'transport' attribute to our astribank devices which
      points to the usb device we use. E.g:
       /sys/bus/astribanks/devices/xbus-00/transport is symlinked to
       ../../../../../../devices/pci0000:00/0000:00:10.4/usb5/5-4
    - Move /proc/xpp/XBUS-??/XPD-??/span to
      /sys/bus/xpds/devices/??:?:?/span
    - Migrate from /proc/xpp/sync to:
      /sys/bus/astribanks/drivers/xppdrv/sync
    - New 'offhook' attribute in:
      /sys/bus/xpds/devices/??:?:?/offhook
  * PRI: change the "timing" priority to match the convention used by
         other PRI cards -- I.e: lower numbers (not 0) have higher
	 priority.
  * FXO: 
    - Power denial: create two module parameters instead of hard-coded
      constants (power_denial_safezone, power_denial_minlen).
      For sites that get non-standard power-denial signals from central
      office on offhook.
    - Don't hangup on power-denial, just notify Dahdi and wait for
    - Fix caller-id detection for the case central office sends it before
      first ring without any indication before.
      Asterisk's desicion.
Mon, Dec  8 2008 Oron Peled <oron@actcom.co.il> - xpp.r6430
  * PRI:
    - Match our span clocking priorities (in system.conf)
      to Digium -- this is a reversal of the previous state.
      Now lower numbers (greater than 0) are better.
    - Synchronization fixes for PRI ports other than 0.
    - Fix T1 CRC for some countries (e.g: China).
  * FXS: fix bug in VMWI detection if using old asterisk
    which does not provide ZT_VMWI ioctl().
  * FXO:
    - Improve caller_id_style module parameter. This provide a workaround
      for countries that send this information without any notification
      (reverse polarity, ring, etc.)
    - Don't force on-hook upon power-denial. So, loopstart devices
      would ignore these as expected.
  * Implement a flow-control to prevent user space (init_card_* scripts)
    from pressuring our command queue.


git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@4631 5390a7c7-147a-4af0-8ec9-7488f05a26cb

1 files changed, 114 insertions, 0 deletions

diff --git a/kernel/xpp/utils/genconf_parameters b/kernel/xpp/utils/genconf_parameters
new file mode 100644
index 0000000..d1b8f62
--- /dev/null
+++ b/kernel/xpp/utils/genconf_parameters
@@ -0,0 +1,114 @@
+#
+# /etc/dahdi/genconf_parameters
+#
+# This file contains parameters that affect the
+# dahdi_genconf configurator generator.
+#
+# Syntax:
+# 	* A comment from '#' to end of line
+# 	* Blank lines ignored
+# 	* Whitespace at end of line trimmed
+# 	* Single valued items:
+# 	     key <whitespaces...> value
+# 	* List valued items:
+# 	     key
+# 	     <whitespaces...>value1
+# 	     <whitespaces...>value2
+# 	     ...
+#
+
+# When generating extensions for zapata.conf or users.conf etc: the 
+# extension number will be channel_number+base_exten . The default is:
+#base_exten		4000
+#
+# Make FXS (analog phones) extentions answer immediately (sets
+# 'immediate = yes' for them in zapata.conf). Don't enable this before 
+# you're read documentation about this option.
+#fxs_immediate		yes
+#
+# For FXS (analog phones) - use KS or LS? ks is the only method for
+# Asterisk to provide disconnect supervision and thus it would normally
+# be preffered and is the default.
+#fxs_default_start	ls
+#
+# For FXO (analog lines) - use KS or LS? KS is the default and is
+# normally the better choice as it allows detecting handups on many
+# lines.
+#fxo_default_start	ls
+
+# Set tone zone values. This is used for playing tones (busy, dialtone
+# and such). The default is 'us'. This sets the value for both loadzone
+# and defaultzone in zaptel.conf .
+#lc_country		il
+
+# The dialplan contenxt into which to send trunks in zapata.conf or
+# users.conf. The default value is:
+#context_lines		from-pstn
+#
+# The dialplan context into which to send extensions in zapata.conf or
+# users.conf. The default value is:
+#context_phones		from-internal
+#
+# Two extea contexts for the input ports and output ports of an
+# Astribank. Default values are:
+#context_input		astbank-input
+#context_output		astbank-output
+
+# A group to put all analog phones in. By default 0, so you can dial to
+# the 'first phone available' using Zap/g5 .
+#group_phones		5
+#
+# A group in which to put all the channels belonging to some trunk.
+# Thus you can dial through "some trunk" using Zap/G0/NUMBER
+#group_lines		0
+
+# Channels of digital trunk of span N are also added to group 10+N (that 
+# is: 14 for channels of span 4).
+
+# Do we want to use PtP ('bri') or PtMP ('bri_ptmp') for BRI? PtMP 
+# allows connecting several CPE devices on the same network device 
+# (several BRI phones on the same line, kind of like several analog 
+# phones on the same analog line). However it is generally brings 
+# unnecessary complexity for a pbx-pbx connection. It is still the 
+# default as this is normally what you get for a BRI PSTN connection.
+#bri_sig_style		bri
+#
+# If this option is set (that is: not remmed-out), BRI NT ports will 
+# also be set as overlap. This is useful if you want to connect ISDN 
+# phones.
+#brint_overlap
+
+# bri_hardhdlc: If this parameter is set to 'yes', in the entries for
+# BRI cards 'hardhdlc' will be used instead of 'dchan' (an alias for
+# 'fcshdlc').
+#bri_hardhdlc		yes
+
+# For MFC/R2 Support: 'R2' will make E1 spans CAS and with the
+# 'r2_idle_bits' bit in zaptel.conf . It will also make zapconf default
+# to generating the channels of this card in unicall.conf rather than in
+# zapata.conf . The meaning of this may be extended somehow to support
+# R2 through openr2/chan_dahdi later on.
+#pri_connection_type	R2
+#r2_idle_bits		1101
+
+# pri_termtype contains a list of settings:
+# Currently the only setting is for TE or NT (the default is TE). This
+# sets two different but normally related configuration items:
+# 
+# A TE span will have *_cpe signalling in Asterisk and will also get
+# timing from the remote party.
+# 
+# A NT span will have *_new signalling in Asterisk and will provide
+# timing to the remote party.
+#
+# pri_termtype is a list if span specs and configuration (TE/NT) for
+# them. The first spec that matches is used. The matching is of perl
+# regular expressions, but with '*' and '?' have their meaning from
+# basic regular expressions.
+#pri_termtype
+#	SPAN/2		NT
+#	SPAN/4		NT
+#
+#pri_termtype
+#	SPAN/*		NT
+#