[svn-commits] mattf: trunk r210 - /trunk/README

Sat Sep 6 11:15:54 CDT 2008

Author: mattf
Date: Sat Sep  6 11:15:53 2008
New Revision: 210

URL: http://svn.digium.com/view/libss7?view=rev&rev=210
Log:
Give the default README an 1.6.0 and DAHDI an overhaul, add 56k documentation, as well as a section on SS7 related Asterisk variables.

Modified:
    trunk/README

Modified: trunk/README
URL: http://svn.digium.com/view/libss7/trunk/README?view=diff&rev=210&r1=209&r2=210
==============================================================================

--- trunk/README (original)
+++ trunk/README Sat Sep  6 11:15:53 2008
@@ -40,32 +40,36 @@
 
 To Use:
 =======
-In order to use libss7, you must get at least the following versions of Zaptel and Asterisk:
-Zaptel: 1.4.x
-libss7: trunk (currently, there *only* is a trunk release).
-Asterisk: trunk
+In order to use libss7, you must get at least the following versions of DAHDI and Asterisk:
+DAHDI: 2.0.x
+libss7: 1.0.x or trunk
+Asterisk: 1.6.x
 
 You must then do a `make; make install` in each of the directories that you installed
-in the given order (Zaptel first, libss7 second, and Asterisk last).
+in the given order (DAHDI first, libss7 second, and Asterisk last).
 
 NOTE: In order to check out the code, you must have the subversion client installed.  This
 is how to check them out from the public subversion server.
 
 These are the commands you would type to install them:
 
-`svn co http://svn.digium.com/svn/zaptel/branches/1.4 zaptel-1.4`
-`cd zaptel-1.4`
+`svn co http://svn.digium.com/svn/dahdi/linux/trunk dahdi-trunk`
+`cd dahdi-trunk`
 `make; make install`
+
+`svn co http://svn.digium.com/svn/dahdi/tools/trunk dahdi-tools`
+`cd dahdi-tools`
+`./configure; make; make install`
 
 `svn co http://svn.digium.com/svn/libss7/trunk libss7-trunk`
 `cd libss7-trunk`
 `make; make install`
 
-`svn co http://svn.digium.com/svn/asterisk/trunk asterisk-trunk`
-`cd asterisk-trunk`
+`svn co http://svn.digium.com/svn/asterisk/branches/1.6.0 asterisk-1.6.0`
+`cd asterisk-1.6.0`
 `./configure; make; make install;`
 
-This should build Zaptel, libss7, and Asterisk with SS7 support.
+This should build DAHDI, libss7, and Asterisk with SS7 support.
 
 In the past, there was a special asterisk-ss7 branch to use which contained the SS7 code.
 That code has been merged back into the trunk version of Asterisk, and the old asterisk-ss7
@@ -74,30 +78,35 @@
 instead.
 
 CONFIGURATION:
-In zaptel.conf, your signalling channel(s) should be a "mtp2" and your bearers should
-be set as "bchan".  If you have an older version of Zaptel (pre 1.4.11) that does not
-support the mtp2 channel type, it is strongly recommended that you update to a version that
-supports it.  If you cannot, or your card does not support the "mtp2" channel type, you
-can use "dchan" instead for your signalling link.  See NEWS-05-30-2008 for more details
-about the mtp2 channel type.
-
-zaptel.conf:
-============
-# For signalling link on Zap/24 and bearers on Zap/1-23
+In /etc/dahdi/system.conf, your signalling channel(s) should be a "mtp2" (or "dchan" with a
+non Digium card) and your bearers should be set as "bchan".
+
+For example:
+span=1,1,0,esf,b8zs
+bchan=1-15,17-31
+mtp2=16
+#dchan=16 for non Digium cards
+
+NOTE: For 56k ANSI links, you must additionally set in /etc/dahdi/system.conf "56k=[channel number]"
+where 56k is like a flag for the mtp2 or dchan.
+
+For example:
+span=1,1,0,esf,b8zs
+bchan=1-23
 mtp2=24
-bchan=1-23
-
-In the asterisk-ss7 branch, there is a sample zapata.conf that is installed which
-contains sample configuration for setting up an E1 link.
+56k=24
+
+In the sample config file in Asterisk-1.6, there is a sample SS7 setup which you can
+use to configured your link.
 
 In brief, here is a simple ss7 linkset setup:
 
-zapata.conf
+chan_dahdi.conf
 ===========
 signalling = ss7
 ss7type = itu 		; or ansi if you are using an ANSI link
 
-linkset = 1		; Pick a number for your linkset identifier in zapata.conf
+linkset = 1		; Pick a number for your linkset identifier in chan_dahdi.conf
 
 pointcode = 28		; The decimal form of your point code.  If you are using an
 			; ANSI linkset, you can use the xxx-xxx-xxx notation for
@@ -110,34 +119,57 @@
 
 ; Now we configure our Bearer channels (CICs)
 
-cicbeginswith = 1	; Number to start counting the CICs from.  So if Zap/1 to
-			; Zap/15 are CICs 1-15, you would set this to 1 before you
+cicbeginswith = 1	; Number to start counting the CICs from.  So if DAHDI/1 to
+			; DAHDI/15 are CICs 1-15, you would set this to 1 before you
 			; declare channel=1-15
 
-channel=1-15		; Use Zap/1-15 and assign them to CICs 1-15
-
-cicbeginswith = 17	; Now for Zap/17 to Zap/31, they are CICs 17-31 so we initialize
+channel=1-15		; Use DAHDI/1-15 and assign them to CICs 1-15
+
+cicbeginswith = 17	; Now for DAHDI/17 to DAHDI/31, they are CICs 17-31 so we initialize
 			; cicbeginswith to 17 before we declare those channels
 
 channel = 17-31		; This assigns CICs 17-31 to channels 17-31
 
-sigchan = 16		; This is where you declare which Zap channel is your signalling
-			; channel.  In our case it is Zap/16.  You can add redundant
+sigchan = 16		; This is where you declare which DAHDI channel is your signalling
+			; channel.  In our case it is DAHDI/16.  You can add redundant
 			; signalling channels by adding additional sigchan= lines.
 			
 ; If we want an alternate redundant signalling channel add this
 
 sigchan = 48		; This would put two signalling channels in our linkset, one at
-			; Zap/16 and one at Zap/48 which both would be used to send/receive
+			; DAHDI/16 and one at DAHDI/48 which both would be used to send/receive
 			; ISUP traffic.
 
-; End of zapata.conf
-
-This is how a basic linkset is setup.  For more detailed zapata.conf SS7 config information
-as well as other options available for that file, see the default zapata.conf that comes
+; End of chan_dahdi.conf
+
+This is how a basic linkset is setup.  For more detailed chan_dahdi.conf SS7 config information
+as well as other options available for that file, see the default chan_dahdi.conf that comes
 with the samples in asterisk.  If you would like, you can do a `make samples` in your
-asterisk-trunk directory and it will install a sample zapata.conf for you that contains
+asterisk directory and it will install a sample chan_dahdi.conf for you that contains
 more information about SS7 setup.
+
+Asterisk channel variables which map to SS7 parameters:
+=======================================================
+SS7_CHARGE_NUMBER
+SS7_GENERIC_ADDRESS
+SS7_JIP
+SS7_GENERIC_DIGITS
+SS7_GENERIC_DIGTYPE  (type of generic digits)
+SS7_GENERIC_DIGSCHEME
+SS7_ORIG_CALLED_NUM
+
+SS7_LSPI_IDENT (these three are used for RLT support on DMS switches)
+SS7_CALLREF_IDENT
+SS7_CALLREF_PC
+
+SS7_CALLING_PARTY_CATEGORY
+SS7_REDIRECTING_NUMBER
+SS7_GENERIC_NAME
+
+Most are fairly self explanatory as far as what they contain.  It is also possible to set 
+many of these parameters on outbound calls as well by prefixing the variable with an '_' 
+when you set it.
+
 
 Completed:
 ==========


