Specifications

Tip: Problems with timing manifest themselves in different ways - with static, pops, and channels or calls
regularly dropping.
LBO:
Line Build Out (LBO) is taken from the table below.
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:
For T1 - Framing is either d4 or esf. Coding is either ami or b8zs.
For E1 – Framing is either cas or ccs. Coding is either ami or hdb3. E1’s spans may also need to
enable crc checking.
T1 span configuration used to connect to a Rhino CB24:
span=1,0,0,esf,b8zs
A common E1 span configuration:
span=1,0,0,cas,ami,crc4
Leave off the ‘,crc4’ if crc checking should not be enabled.
3.e Rhino OST T1/E1 PCI card Channel configurations
Rule of Thumb: Have you ever heard someone say “Opposites attract”? The same is true when
configuring zaptel and Zapata for your Rhino OST PCI card. When configuring the signaling for
your interface channels remember that physical FXO channels require FXS signaling and physical
FXS channels require FXO signaling.
When you are configuring your Rhino OST PCI T1 card to work with a Rhino CB24 please use the
following signaling:
(CB24-FXO) signaling = fxsks(zaptel.conf) fxs_ks(zapata.conf)
(CB24-FXS) signaling = fxols(zaptel.conf) fxo_ls(zapata.conf)
For CB24-MOD signaling see the example below
Rhino Equipment Corp. • 8240 S. Kyrene Rd. • Suite 107 • Tempe, AZ 85284 • [phone]
20