Configuring a Zaptel T1 Line
This webpage is about configuring a T1 line for Asterisk - it should work equally well for E1 cards. If you haven't at this time, read the pages on this website about Testing Zaptel Hardware. It'll give you an introduction into how the zaptel cards integrate with Linux and Asterisk - probably too much information!
Normally genzaptelconf automatically configures zaptel cards but it only does the FXS/FXO cards - it doesn't configure the T1 cards. They will have to be manually configured. Make sure that your T1 card is blacklisted as per the instructions at Testing Zaptel Hardware and that the card module is being loaded at /etc/sysconfig/zaptel as per the instructions at Zaptel Drivers
Once that is verified than you are ready to perform the configuration of the first file: /etc/zaptel. At this point you will need to know your service provider's T1 settings or if you are connecting to a channel bank, its T1 configuration. In this example, we will be connecting a TE110p card to an Adtran TSU600 channel bank with a T1 crossover cable using the following T1 configuration:
- Span 1
- TE110p card provides master clock
- Line build out is for 6 feet
- Framing is for T1 esf
- Coding is standard T1: b8zs
- No yellow alarms
A channel bank provides 24 channels of FXS or FXO ports (any combination of each) from a T1 line. It would be great to use as part of a VOIP gateway from the legacy telephone network to VOIP. Provide VOIP to 24 phone lines (FXO) or connect 24 phones set to the VOIP world, or use it with PiaF to replace an existing key system.
Configuring T1 Line
The following information will configure the T1 interface in /etc/zaptel:
span= <span num> ,<timing source>,<line build out (LBO)>,<framing>,<coding>[,yellow]
<span num>
Number of the T1 span. This begins at 1, and goes up one integer at a time. You may NOT have two spans with the same span number. Each telephony card counts as 1 span.
<timing source>
All T1/E1 spans generate a clock signal on their transmit side. The parameter determines whether the clock signal from the far end of the T1/E1 is used as the master source of clock timing.
0 = Local T1 card provides clock (master), far end is slave,
1 = First choice: far end T1 provides clock (master), local T1 card is slave
2, 3, … = Second choice: used by multiple T1 card setup. If first choice fails fallover to this one
<line build out (LBO)>
The line build-out (or LBO) is an integer, from the following table:
0: 0 db (CSU) / 0-133 feet (DSX-1)
1: 133-266 feet (DSX-1)
2: 266-399 feet (DSX-1)
3: 399-533 feet (DSX-1)
4: 533-655 feet (DSX-1)
5: -7.5db (CSU)
6: -15db (CSU)
7: -22.5db (CSU)
<framing>
The framing is one of "d4" or "esf" for T1 or "cas" or "ccs" for E1
Note: "d4" could be referred to as "sf" or "superframe"
<coding>
The coding is one of "ami" or "b8zs" for T1 or "ami" or "hdb3" for E1
E1's may have the additional keyword "crc4" to enable CRC4 checking
[,yellow]
If the keyword "yellow" follows, yellow alarm is transmitted when no channels are open.
Example configurations:
span=1,0,0,esf,b8zs
span=2,1,0,esf,b8zs
span=3,0,0,ccs,hdb3,crc4
Channel Bank Example
For the example setup of a T1 to a channel bank, our configuration would be:
span=1,0,0,esf,b8zs
- span=1 because it is the first card installed
- 0 because we are going to provide the master clock to the channel bank (1 if we were connecting to a service provider)
- 0 because we are going less than 133 feet from the PiaF server to the channel bank
- esf because Extended Super Frame is the industry standard and we configured the channel bank to use it
- b8zs because bipolar with eight-zero substitution (B8ZS) is the industry standard for T1 lines.
The next step in communicating with the channel bank is to configure the 24 T1 channels.
|