Le samedi 14 novembre 2009 à 20:44 +0100, Eric van der Vlist a écrit : > and playing with "udevadm test", I have noticed that the following rule: > > +++++++++++++++++++++++++++++++++++++++++++ > KERNEL=="[0-9]*", GOTO="xpp_usb_add_end" > +++++++++++++++++++++++++++++++++++++++++++ > > is always met and that if I comment it, the astribank get initialized. > > Is that safe to remove this rule or is there a better solution?
I am doing some more tests and that rule really seems to be doing the difference. I also notice that even when that rule is commented, plugging an uninitialized astribank after the server has been restarted doesn't seem to work: for whatever reason, when I try to load the dahdi module in asterisk I get this error message: asterisk*CLI> module load chan_dahdi.so Unable to load module chan_dahdi.so Command 'module load chan_dahdi.so' failed. [Nov 15 11:10:45] WARNING[2640]: pbx.c:5048 ast_register_application2: Already have an application 'DAHDISendKeypadFacility' == Parsing '/etc/asterisk/chan_dahdi.conf': == Found == Parsing '/etc/asterisk/dahdi-channels.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found [Nov 15 11:10:45] WARNING[2640]: chan_dahdi.c:2121 dahdi_open: Unable to specify channel 1: No such device or address [Nov 15 11:10:45] ERROR[2640]: chan_dahdi.c:10022 mkintf: Unable to open channel 1: No such device or address here = 0, tmp->channel = 1, channel = 1 [Nov 15 11:10:45] ERROR[2640]: chan_dahdi.c:15972 build_channels: Unable to register channel '1-2' This isn't a big deal since I won't be doing that so often on a production server, but that may be worth mentioning... Another weirdness is that dadhi tools keep complaining that /sys/bus/xpds/devices/00:0:0/timing_priority is missing: v...@asterisk:~$ sudo lsdahdi Use of uninitialized value $busnum in sprintf at /usr/local/share/perl/5.10.0/Dahdi/Hardware/USB.pm line 100. Use of uninitialized value $devnum in sprintf at /usr/local/share/perl/5.10.0/Dahdi/Hardware/USB.pm line 100. /usr/sbin/lsdahdi: warning - OLD DRIVER: missing '/sys/bus/xpds/devices/00:0:0/timing_priority'. Fall back to /proc ### Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: HRtimer) 1" (MASTER) ### Span 2: XBUS-00/XPD-00 "Xorcom XPD #00/00: BRI_NT" AMI/CCS 1 BRI_NT Clear (In use) (SWEC: MG2) 2 BRI_NT Clear (In use) (SWEC: MG2) 3 BRI_NT Hardware-assisted HDLC (In use) ### Span 3: XBUS-00/XPD-01 "Xorcom XPD #00/01: BRI_TE" AMI/CCS 4 BRI_TE Clear (In use) (SWEC: MG2) 5 BRI_TE Clear (In use) (SWEC: MG2) 6 BRI_TE Hardware-assisted HDLC (In use) ### Span 4: XBUS-00/XPD-02 "Xorcom XPD #00/02: BRI_NT" AMI/CCS 7 BRI_NT Clear (In use) (SWEC: MG2) 8 BRI_NT Clear (In use) (SWEC: MG2) 9 BRI_NT Hardware-assisted HDLC (In use) ### Span 5: XBUS-00/XPD-03 "Xorcom XPD #00/03: BRI_NT" AMI/CCS 10 BRI_NT Clear (In use) (SWEC: MG2) 11 BRI_NT Clear (In use) (SWEC: MG2) 12 BRI_NT Hardware-assisted HDLC (In use) And: v...@asterisk:~$ ls /sys/bus/xpds/devices/00:0:0 blink chipregs driver offhook power span subsystem type uevent Also, I have always wondered why dahdi sees 4 spans when my astribank only has 2 BRIs! Thanks for your help, I would really like to know at least how safe it is to comment that rule! Eric -- Eric van der Vlist <[email protected]> Dyomedea (http://dyomedea.com) _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
