We are doing hardware tests with recent dahdi-2.3.0.1 and both asterisk-1.4.33.1 and asterisk-1.6.2.8. Recently, we have noticed that whenever an ISDN port is in RED alarm (unsynchronized), we get a stream of warnings in /var/log/asterisk/full that look like this:
[Jun 30 17:38:41] WARNING[9637] chan_dahdi.c: No D-channels available! Using Primary channel 78 as D-channel anyway! [Jun 30 17:38:41] WARNING[9638] chan_dahdi.c: No D-channels available! Using Primary channel 109 as D-channel anyway! [Jun 30 17:38:45] WARNING[9637] chan_dahdi.c: No D-channels available! Using Primary channel 78 as D-channel anyway! [Jun 30 17:38:45] WARNING[9638] chan_dahdi.c: No D-channels available! Using Primary channel 109 as D-channel anyway! [Jun 30 17:38:49] WARNING[9637] chan_dahdi.c: No D-channels available! Using Primary channel 78 as D-channel anyway! [Jun 30 17:38:49] WARNING[9638] chan_dahdi.c: No D-channels available! Using Primary channel 109 as D-channel anyway! [Jun 30 17:38:50] VERBOSE[9626] asterisk.c: -- Remote UNIX connection [Jun 30 17:38:53] WARNING[9637] chan_dahdi.c: No D-channels available! Using Primary channel 78 as D-channel anyway! [Jun 30 17:38:53] WARNING[9638] chan_dahdi.c: No D-channels available! Using Primary channel 109 as D-channel anyway! [Jun 30 17:38:57] WARNING[9637] chan_dahdi.c: No D-channels available! Using Primary channel 78 as D-channel anyway! [Jun 30 17:38:57] WARNING[9638] chan_dahdi.c: No D-channels available! Using Primary channel 109 as D-channel anyway! This particular machine runs asterisk-1.6.2.8 with dahdi-2.3.0.1. The telephony hardware is an OpenVox PRI card with four E1 ports (driver is wct4xxp). On this system, I have configured port 1 as pri_net, and port 2 as pri_cpe, and connected the two with a crossover cable, leaving ports 3 and 4 disconnected. Therefore I have two synchronized ports (with each other) and two unsynchronized ports (RED). From what I see in /proc/dahdi/* , channels 78 and 109 are the two D channels of the two disconnected ports. I can route calls between the two connected ports, so that part appears to work OK. I have reproduced this stream of warnings on another machine with asterisk-1.4.33.1 and dahdi-2.3.0.1, and also with other card types (OpenVox with 1 E1 port, Sangoma with 2 T1 ports, Rhino with 2 T1 ports), so I do not think the particular driver is an issue. The question I have is this: is this warning message something to be expected from ports with RED alarms? Or is this message a symptom of a deeper misconfiguration? Since I am the package manager for the Elastix project (http://www.elastix.org), I am the one who can solve misconfigurations, if any. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
