DAHDI-Linux 2.6.0 and DAHDI-Tools 2.6.0 Released

WARNING: this is an automatic post retrieved from the Asterisk-Users Mailing List, not an authored post Mailing-list Colector January 04, 2012 Asterisk-Users 1 Comment

Tags: decrease load time, isdn bri, linemode, minor additions, span card, wct, wcte, xpp

The Asterisk Development Team is pleased to announce the first
release of DAHDI-Linux 2.6.0 and DAHDI-Tools 2.6.0.

2.6.0 is a feature release which:

- Adds support for the TE820 8-span card to the wct4xxp driver.

- Decrease load time of analog cards supported by the wctdm24xxp
driver.

- Adds sysfs object model to facilitate persistent span numbering
and early loading of modules (NOTE: by default this release
still behaves like previous releases with regards to span
numbering assignment).

- dahdi_pcap tool is now included in DAHDI-tools but not compiled
by default since it depends on a currently unsupported interface
in DAHDI-Linux. It is intended that in future releases this will
be compiled by default.

Issues closed in this release:

DAHTOOL-49: adding pcap support to Dahdi
(Reported by: Torrey Searle)
DAHLIN-258: weird sound with a native bridged isdn-bri connection
(Reported by: Daniel)
DAHLIN-264: xpp: E1 CAS multiframe bits not properly set

DAHDI-Linux 2.6.0, DAHDI-Tools 2.6.0, and DAHDI-Linux-Complete
2.6.0+2.6.0 are available for immediate download at:

http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete

The DAHDI-Linux shortlog of changes that are not in 2.5.0.2:

Doug Bailey:
wctdm24xxp, wcte12xp: Update VPMOCT032 firmware to 1.12.0.

Tzafrir Cohen:
Avoid building PCI devices if kernel has no PCI
xpp: Allow up to 128 Astribanks on a system
xpp: increase command queue length to 1500
xpp: USB_FW rev 10085: fix regression from r10013
xpp: PIC_TYPE_1 rev 9841: followup to r10013
bugfix: off-by-one in span assignment
xpp: USB firmware r9964: minor bugfixes
xpp: bugfix: clear NOTOPEN span alarm on assign
xpp: bugfix — manage xpd refcount for EC module
xpp: Adaptations for E-Main-3
xpp: remove leftovers of old XPD_STATE method
README: Minor additions regarding pinned-spans
README: initial update for span assignments
dahdi: Add error messages in dahdi_ioctl_chanconfig.
xpp: fix FXS D DTMF detection (not zero)
xpp: fix bashism in xpp_debug
live_dahdi: optionally generate FreePBX DB entries

Matthew Fredrickson:
wct4xxp: Add support for TE820 and VPMOCT256.

Russ Meyerriecks:
wct4xxp: Remove vpm400 support.
wct4xxp: Revise vpm struct due to product name changes
wct4xxp: Handle incorrect vpm module/card pairings
wct4xxp: minor: Removed unnecessary instrumentation
wct4xxp: Expose serial number in dahdi_device and kernel log.
wct4xxp: Add field upgradable firmware support for TE820.
wcte12xp, wctdm24xxp: Remove frowny face from vpmoct032 error message

Oron Peled:
xpp: BRI: batch D-Channel packets to fix frag.
xpp: BRI: split multibyte functionality
xpp: BRI: remove trivial BRISTUFF wrappers
xpp: BRI: remove legacy BRISTUFF code
xpp: bad module_put() when too many Astribanks
DAHDI-linux: Fix “surprise removal” problems
xpp: BRI: fix timing priority calculation
xpp: FXS: mwi and search_fsk fixes
xpp: PRI: restore pri_protocol to R/W:
xpp: pri: fix RS1 init in E1 CAS mode
xpp: fxs: demote SETPOLARITY message to DBG()
xpp: silence some bad ioctl() reporting
xpp: restore backward compat dahdi_registration
Extra debugging aids and messages
xpp: cleanup some printk()’s
added ‘basechan’ and ‘channels’ attributes to spans
dahdi: Give userspace a chance to respond to surprise removal.
xpp: Remove dahdi_autoreg parameter:
xpp: more informative span description:
xpp: make unregistration safer (idempotent)
xpp: adapt to ‘location’ attribute removal:
xpp: PRI: use DAHDI new set_spantype() method
dahdi: Expose spans in sysfs.
dahdi: dahdi_is_analog_span() -> dahdi_is_digital_span()
dahdi: start handling “surprise device removal”.

Shaun Ruffell:
wctdm24xxp: Fix bug if hook state on FXS changes before channel configuration.
wct4xxp: Reduce time spent waiting for auth done bit on TE820.
wct4xxp: Fail startup if not generating interrupts.
dahdi: Return dahdi_span_ops.startup callback errors to userspace.
wctdm24xxp: Do not call voicebus_release() before wctdm_back_out_gracefully()
dahdi: #include in dahdi/kernel.h and GpakCust.h
wctc4xxp: Replace ‘ndo_set_multicast_list’ with ‘set_rx_mode’
wctdm24xxp: Wait for background threads to complete on failed load.
dahdi: Unregister dahdi_device from sysfs if we fail to auto assign spans.
dahdi: Fix typo in previous commit which forced some spans to always fail assignment.
dahdi: First span registered becomes master by default.
dahdi: Define POLLRDHUP on kernels < 2.6.17
wctdm24xxp, wcte12xp: Allow VPMADT032 commands more time to complete.
wct4xxp: Allow linemode (T1/E1/J1) to be changed via sysfs attribute.
wcte12xp: Allow linemode (T1/E1) to be changed via sysfs attribute.
dahdi: Allow ‘spantype’ to be changed before span assignement via sysfs.
dahdi: Remove dahdi_span.irq and move dahdi_span.irqmisses into dahdi_device.
dahdi: Expose dahdi devices in sysfs.
dahdi: Register devices instead of individual spans.
wct4xxp: Deprecate ‘t1e1override’ module parameter in favor of ‘default_linemode’.
wct4xxp: Refactor t4_serial_setup() to remove t4.globalconfig.
wct4xxp: Trivial. Use ARRAY_SIZE in free_wc() and __handle_leds().
wct4xxp: Atomically perform some read/modify/write operations
wct4xxp: Fix spelling
wct4xxp: Change t4_span.spantype to linemode.
wct4xxp: Trivial refactoring in t4_init_one().
wct4xxp: Add has_e1_span() helper.
wcte12xp: Deprecate ‘t1e1override’ module parameter in favor of ‘default_linemode’.
wct4xxp: Remove redundant ‘vpm’ from struct t4.
wct4xxp: Remove unused debugging code
wct4xxp: Turn off the fancy alarm LEDS.
wct4xxp: Hold a pointer to the devtype directly
wct4xxp: Remove unused fields from ‘struct t4′ and ‘struct t4_span’
wct4xxp: Remove prefetching support.
wct4xxp: Use in-hardirq version of dahdi_receive/transmit.
wct4xxp: __t4_framer_in and __t4_framer_out speedups.
wct4xxp: Remove ‘pedanticpci’ module parameter.
wct4xxp: Remove some debug information from the kernel logs.
wct4xxp: Slow down the rate we poll the framers in alarm.
wct4xxp: Move “hardware DTMF disabled” message from dev_notice -> dev_info
wctdm24xxp: Remove DEBOUNCING_RINGING_OFF from ring_detector_state enum.
wctdm24xxp: Setup all VPMADT032 channels on hybrid cards.
dahdi: Add functions for determining spantype (E1/T1) to include/dahdi/kernel.h
dahdi: Define pr_xxx macros if not already defined.
wcte12xp: Set uncollected performance counters to -1.
wct4xxp: Remove unused t4_span.psync and t4_span.redalarms.
wctdm24xxp: Remove fwringdetect module parameter.
wctdm24xxp: Use interval for debouncing FXO polarity detection.
wctdm24xxp: Use interval for debouncing FXO battery.
wctdm24xxp: Use time interval for debouncing FXO ring detect.
wctdm24xxp: Use interval for checking FXS on hook transfer timer.
wctdm24xxp: ‘oppending_ms’ shouldn’t assume being checked at 1ms intervals.
wctdm24xxp: Name the shadow registers for each modules.
wctdm24xxp: Change intcount to framecount.
wctdm24xxp: Use fact that handle_transmit/receive are called in hard-irq
wctdm24xxp: Protect creation / destruction of VPM instance.
wctdm24xxp: Reset the polarity debounce setting when battery is lost.
wctdm24xxp: Probe for and configure modules in parallel.
wctdm24xxp: Introduce bg_create/bg_join.
wcte12xp: Abort driver bind if read/write test fails.

The DAHDI-Linux diffstat from the 2.5.0.2 release:

The DAHDI-Tools short log from 2.5.0.2:

Tzafrir Cohen:
xpp: two extra product IDs: 1112, 1164
xpp: xpp_fxloader: regressions from r10348
DAHDI-perl: Fix PCI ID for Rhino R4T1 (0b0b:0305)
xpp: recovery firmware in xpp_fxloader
xpp: Serialized Parallel load; E-Main-3 firmware
xpp: astribank_hexload: we need more lines
Fix GCC 4.6 “set but not used” warnings
dahdi_cfg: add ‘-S ‘ and ‘-C ‘
dahdi_perl: Use $Dahdi::sys_base for sysfs pathes
xpp_order generator: ignore EC XPD
chandahdi gen: extens can have any num of digits
Typos in man pages: toolyou
Man page for dahdi_maint
Update the dahdi-monitor man page
fix typos in some xpp utils
dahdi-perl: Also get USB loaded driver from usbfs
dahdi-perl: Freepbxdb config generator

Russ Meyerriecks:
dahdi_pcap: Imported user space utility for managing pcap streams

Shaun Ruffell:
dahdi_genconf: Allow it to recognize the TE8xx 8-port cards.
dahdi_test: Enforce range from 0.0% – 100.0% for accuracy.
dahdi_maint: Print ‘unsupported’ warning if framing errors is -1.

Jira Issues: DAHTOOL-56, DAHTOOL-49

The DAHDI-Tools diffstat from the 2.5.0.2:

For a full list of changes in these releases, please see the ChangeLog at
http://svn.asterisk.org/svn/dahdi/linux/tags/2.6.0/ChangeLog and
http://svn.asterisk.org/svn/dahdi/tools/tags/2.6.0/ChangeLog .

Issues found in this release can be reported in the DAHDI-Linux [1] and
DAHDI-Tools [2] projects at https://issues.asterisk.org/jira

[1] https://issues.asterisk.org/jira/browse/DAHLIN
[2] https://issues.asterisk.org/jira/browse/DAHTOOL

Thank you for your continued support of Asterisk!

ISDN PRI configuration

WARNING: this is an automatic post retrieved from the Asterisk-Users Mailing List, not an authored post Mailing-list Colector December 07, 2011 Asterisk-Users 20 Comments

Tags: crc, isdn pri, optional line, PRI, red 19, status description, telco, wct

Hi,

A telco has recently installed a new line in our building and I need to connect it to my Asterisk server with a Digium PRI card.

It’s not the first time I set up and configure a PRI link but I’m failing to make this one work.

The only information I got from the telco is:
“
Line Coding [HDB3]
Framing [CRC4]
Encapsultation [hdlc
Isdn switch-type primary-[net5]
”

Is “crc4″ actually a “framing” parameter as stated by the telco, or is it just an “optional line coding parameter”?

I searched the web and not knowing exactly which parameters to use, I tried the following zaptel/dahdi config:

# TE120P (PRI):
span=1,1,0,ccs,hdb3,crc4
# as E1
bchan=1-15
dchan=16
bchan=17-31

switchtype = euroisdn
signalling = pri_cpe

However, the link doesn’t work and I get this:

*CLI show status:
Description Alarms IRQ bpviol CRC4
Wildcard TE120P Card 0 RED 1 0 0

# cat /proc/zaptel/1
Span 1: WCT1/0 “Wildcard TE120P Card 0″ (MASTER) HDB3/CCS/CRC4 RED
IRQ misses: 1

1 WCT1/0/1 Clear (In use) RED
2 WCT1/0/2 Clear (In use) RED
3 WCT1/0/3 Clear (In use) RED
4 WCT1/0/4 Clear (In use) RED
5 WCT1/0/5 Clear (In use) RED
6 WCT1/0/6 Clear (In use) RED
7 WCT1/0/7 Clear (In use) RED
8 WCT1/0/8 Clear (In use) RED
9 WCT1/0/9 Clear (In use) RED
10 WCT1/0/10 Clear (In use) RED
11 WCT1/0/11 Clear (In use) RED
12 WCT1/0/12 Clear (In use) RED
13 WCT1/0/13 Clear (In use) RED
14 WCT1/0/14 Clear (In use) RED
15 WCT1/0/15 Clear (In use) RED
16 WCT1/0/16 HDLCFCS (In use) RED
17 WCT1/0/17 Clear (In use) RED
18 WCT1/0/18 Clear (In use) RED
19 WCT1/0/19 Clear (In use) RED
20 WCT1/0/20 Clear (In use) RED
21 WCT1/0/21 Clear (In use) RED
22 WCT1/0/22 Clear (In use) RED
23 WCT1/0/23 Clear (In use) RED
24 WCT1/0/24 Clear (In use) RED
25 WCT1/0/25 Clear (In use) RED
26 WCT1/0/26 Clear (In use) RED
27 WCT1/0/27 Clear (In use) RED
28 WCT1/0/28 Clear (In use) RED
29 WCT1/0/29 Clear (In use) RED
30 WCT1/0/30 Clear (In use) RED
31 WCT1/0/31 Clear (In use) RED

Placing a call through the Zap/Dahdi trunk in Asterisk doesn’t work and I get the following message in the log:

chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
logger.c: — Attempting call on Zap/g1/999xxxxxx for 999xxxxxx@custom-TESTCALL:1 (Retry 1)
channel.c: Unable to request channel Zap/g1/999xxxxxx
pbx_spool.c: Call failed to go through, reason (8) Congestion (circuits busy)
chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!

Am I missing some information here?
I’m *supposing* it should be E1 (and that I can use 16 as dchan), euroisdn (not “national”), but my telco states “hdlc Isdn switch-type primary-[net5]” and I don’t know how to translate it to zaptel/dahdi…

Also, my telco hasn’t mentioned anything about ccs but I tried it anyway because I wouldn’t know what else to use.

I also tried
signalling = pri_net
but still got the same RED alerts.

Any suggestions?

Thanks

Vieri

Sporadic yellow alarms in dahdi_tool output

WARNING: this is an automatic post retrieved from the Asterisk-Users Mailing List, not an authored post Mailing-list Colector November 25, 2011 Asterisk-Users 1 Comment

Tags: configuration issue, issue, linux, linux kernel version, pri line, t1 e1, tool, wct

Hi all,

We have a telephony server in India which runs CentOS release 5.7 (Final)
version with four-span Digium Card, one of which has an E1 PRI line
terminating on the server.
$ dahdi_hardware
pci:0000:07:08.0 wct4xxp+ d161:1420 Wildcard TE420 (5th Gen)

Recently we’ve been observing the status of Span 1 as observed from
dahdi_tool output flaps between yellow and green. This happens a couple of
few a day.
While the span state is yellow, I observed that the
modules dahdi_echocan_mg2 and wct4xxp are not loaded.

After running sudo modprobe wct4xxp; sudo modprobe dahdi_echocan_mg2, the
span state changes to green.
The dahdi documentation has the following to say on yellow alarms:

(RAI — Remote Alarm Indication)

Your T1/E1 port will go into yellow alarm when it receives a signal from
the remote switch that the port on that remote switch is in red alarm. This
essentially means that the remote switch is not able to maintain sync with
you, or is not receiving your transmission.

As a newbie to asterisk, pointers will be very helpful. Here are some more
details on the installed versions of various packages/modules.

1. Linux Kernel Version : $ uname -a
Linux 022.exotel.in 2.6.18-274.3.1.el5 #1 SMP Tue Sep 6 20:13:52 EDT 2011
x86_64 x86_64 x86_64 GNU/Linux
2. Dahdi verison: dahdi-linux-complete-2.5.0.1+2.5.0.1
3. Asterisk verison: asterisk-1.8.6.0
4. libpri version: libpri-1.4.12

Is this a configuration issue, package version issue or an operator issue?
I’ll be glad to share the necessary dahdi configuration files if needed.

Thanks in advance.

Installing PRI card

WARNING: this is an automatic post retrieved from the Asterisk-Users Mailing List, not an authored post Mailing-list Colector September 29, 2011 Asterisk-Users 5 Comments

Tags: asterisk, cat, irq, PRI, red 13, red 19, remote server, server thanks, wct

Hi,

We have got a new PRI card at one of our Office locations and now I need to install the the device on a remote server. Is there any way to know if the device is loaded already.

When I give ” cat /proc/zaptel/* ” it returns the following.

# cat /proc/zaptel/*

Span 1: WCT1/0 “Wildcard TE122 Card 0″ (MASTER) B8ZS/ESF RED

IRQ misses: 2

1 WCT1/0/1 Clear (In use) RED

2 WCT1/0/2 Clear (In use) RED

3 WCT1/0/3 Clear (In use) RED

4 WCT1/0/4 Clear (In use) RED

5 WCT1/0/5 Clear (In use) RED

6 WCT1/0/6 Clear (In use) RED

7 WCT1/0/7 Clear (In use) RED

8 WCT1/0/8 Clear (In use) RED

9 WCT1/0/9 Clear (In use) RED

10 WCT1/0/10 Clear (In use) RED

11 WCT1/0/11 Clear (In use) RED

12 WCT1/0/12 Clear (In use) RED

13 WCT1/0/13 Clear (In use) RED

14 WCT1/0/14 Clear (In use) RED

15 WCT1/0/15 Clear (In use) RED

16 WCT1/0/16 Clear RED

17 WCT1/0/17 Clear (In use) RED

18 WCT1/0/18 Clear (In use) RED

19 WCT1/0/19 Clear (In use) RED

20 WCT1/0/20 Clear (In use) RED

21 WCT1/0/21 Clear (In use) RED

22 WCT1/0/22 Clear (In use) RED

23 WCT1/0/23 Clear (In use) RED

24 WCT1/0/24 HDLCFCS (In use) RED

But when I connect to the console, I am unable to give any ZAP related commands. Does this mean that my device is loaded and I just need to load the module. Or do I need to compile asterisk again?? Any help would be highly appreciated.

My asterisk version is Asterisk 1.4.19.2 and I am on a Fedora release 9
server.

Force Dahdi modules to load

WARNING: this is an automatic post retrieved from the Asterisk-Users Mailing List, not an authored post Mailing-list Colector January 21, 2011 Asterisk-Users Comments Off

Tags: asterisk, cards, Digium, Force, linux, PCI, PCI-e, spans, wct, ystdm

People,

I’m trying to force dahdi to load the modules I need to get spans working.

I have two cards, an Digium TE210E (PCI-e) and a Yeastar TDM1600 FXO (PCI)

Actually it is loading just the first of them, it is (wtc4xxp) for TE210E,
but doesn’t load
the second module as specified at /etc/dahdi/modules:

wct4xxp
ystdm16xx

I have to load it manually to get spans working.

modprobe ystdm16xx

I need to get around this, and force system to get both modules loaded at
startup.

I also have /etc/modprobe.d/dahdi.blacklist.conf :

blacklist wct4xxp —————–> Need this to load first
blacklist ystdm16xx ————-> Need this to load after
blacklist ystdm8xx
blacklist wcte12xp
blacklist wct1xxp
blacklist wcte11xp
blacklist wctdm24xxp
blacklist wcfxo
blacklist wctdm
blacklist wctc4xxp
blacklist wcb4xxp
blacklist netjet

Thanks.